Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Mar 2021 14:25:53 -0400
From:      Jerry <jerry@seibercom.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: OS to replace FreeBSD
Message-ID:  <20210321142553.000046d6@seibercom.net>
In-Reply-To: <CAGBxaXm8VEGQH=QABJe1o83wDe_NP_U6KgprxgzcyXZdHqYm4g@mail.gmail.com>
References:  <20210320132339.00004d9a@seibercom.net> <38EDD406-3EC4-4F71-B990-DDD1E753D091@kreme.com> <20210321113403.00004056@seibercom.net> <CAGBxaXmV8Z7G=NCw3AX+rhn3QNjMvNAqKPVNOYEnTFMZEq9Pgg@mail.gmail.com> <20210321120633.00004136@seibercom.net> <CAGBxaXm8VEGQH=QABJe1o83wDe_NP_U6KgprxgzcyXZdHqYm4g@mail.gmail.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
--Sig_/0.1dktuT9X8j0UD+/j+eObY
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sun, 21 Mar 2021 12:14:07 -0400, Aryeh Friedman stated:
>On Sun, Mar 21, 2021 at 12:07 PM Jerry <jerry@seibercom.net> wrote:
>
>> >Why should they?!?!?
>> >
>> >The reasons for "why should they" are:
>> >1. There is an almost infinite number of combinations of hardware
>> >that one can find out there and most of them are like the person
>> >you are replying to edge cases that effect very few people (as
>> >witnessed by you can't find anyone with a close enough system that
>> >is willing to actually do the work to test any fixes on... so this
>> >leaves two options: a) you stop complaining and help actually fix
>> >the bug, b) you switch OS's.... either way stop publically whining
>> >about stuff you refuse to help with in an way and if you switch
>> >OS's this is the wrong forum to do it in -- in short STFU)
>> >
>> >2. They *DO* list hardware that is *KNOWN* to be 100% compatible and
>> >working with the base system if you are not using one of the listed
>> >components then you are venturing into unknown territory and any
>> >problems are on you to report and or help fix... if you decide to go
>> >this route then you have no one except yourself to blame when you
>> >run into "some assembly required" situations and likely you are one
>> >the few people that can help fix it... yet you refuse to... again
>> >STFU =20
>>
>> I have no problem with them listing every system they know to be 100%
>> companionable. However, logistically, I believe the to be a
>> impractical. I think the possibility of them actually testing every
>> possible controller, et cetera under every conceivable environment
>> to be absurd. All they really need to do is compile a list of known
>> units with incompatibility issues, post them and then keep them
>> updated.=20
>
>Again why should they if the issue is an open and actively being
>investigated bug report.   The purpose of such a list is for things the
>have decided not to support and any device that claims support for
>function X but does not quite meet the standard (as implemented in the
>kernel) is then by definition a bug that needs to be looked into.
>The bug you are complaining about *IS* being actively looked into and
>thus does not belong on the "we don't support list".
>
>So once again you are wasting your time and everyone else's time by
>barking up a tree that doesn't exist (and should not exist).   So
>either switch to another OS or help solve the issue your complaining
>about.   Neither option is really the territory of -questions@ so once
>again STFU.

You are a complete asshole. The simple fact the the controller in
question, and here I am assuming it is the controller, does not
function correctly under FreeBSD, versions >=3D 11.x, but apparently does
function under other OSs, is prima facie proof that it is not supported.

I have seen zero proof that anyone is actively working on this
phenomenon. The fact the the bug was first reported over a year ago
would seem to indicate that it is not attracting any attention. The
fact that it did work once under older versions reinforces my belief
that someone screwed up the code in the newer versions.

--=20
Jerry




--Sig_/0.1dktuT9X8j0UD+/j+eObY
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQGzBAEBCAAdFiEELeCiu2K+9VmEYYgTgHBP8gv9FXcFAmBXj7gACgkQgHBP8gv9
FXegLwv/fzJvTHjtk2pNykc2GVGAEUeMlodHC39w4m/GztklHVJJ9sFV0dpmV5wT
QZOpA219gxoiNsJl9gy/pAyeKPGntVHz1wRBbWxj66bZw9qkHRII0sSfhzZOY4uS
jgyh/I59LTPFfoweLLg1ez1Yhe25kZ9zIQ8PEY4eoULUnktaG3uMShp6UaoEr8jI
yyTzwC41/KTeS5+/2JYGpFwfoPSB2deVtocIwoZoBKD30BKV4YvUwOr9yRt/5OON
aMK0T3BdSDdqB6gCqvfTYsN/Cxpa72JaBgFV3FuhD9m4S0b8suvINxw9Z7rJ2AHW
7R4YEE5D8DLoc1KC8/XmFQr/5gLpxkS6FUBUo1Hcr1c4EFr/78Bm5JeqkZRut3Xn
7Ew5p5/lLEyzqq6mIFdNAI89mLgl1jRD0PBBpKqDiOyknmAyNaJA65F50AMbob1E
++EWXOjEjEDUQOTECMUF2lkdL1LcVIGbvTk3V0HCMTGv5IeGLocTjBuuZP5RXDCI
hHxTfMRG
=4FQD
-----END PGP SIGNATURE-----

--Sig_/0.1dktuT9X8j0UD+/j+eObY--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20210321142553.000046d6>