Date: Sun, 21 Mar 2021 12:06:33 -0400 From: Jerry <jerry@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re: OS to replace FreeBSD Message-ID: <20210321120633.00004136@seibercom.net> In-Reply-To: <CAGBxaXmV8Z7G=NCw3AX%2Brhn3QNjMvNAqKPVNOYEnTFMZEq9Pgg@mail.gmail.com> References: <20210320132339.00004d9a@seibercom.net> <38EDD406-3EC4-4F71-B990-DDD1E753D091@kreme.com> <20210321113403.00004056@seibercom.net> <CAGBxaXmV8Z7G=NCw3AX%2Brhn3QNjMvNAqKPVNOYEnTFMZEq9Pgg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/+p+C0k=j/GA0jgdi3xdJskN Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sun, 21 Mar 2021 11:47:11 -0400, Aryeh Friedman stated: >On Sun, Mar 21, 2021 at 11:34 AM Jerry <jerry@seibercom.net> wrote: > >> What really infuriates me is that FreeBSD will not at least post a >> warning on their site of the problem. Something like this: >> >> FreeBSD had been notified that the following systems are not >> compatible with versions >=3D 12.x [List of units not compatible]. We >> have no idea what the problem is and we are not going to invest in >> the time to figure it out, and if it is our problem, correct it. >> =20 > >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 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 Jerry --Sig_/+p+C0k=j/GA0jgdi3xdJskN Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQGzBAEBCAAdFiEELeCiu2K+9VmEYYgTgHBP8gv9FXcFAmBXbw8ACgkQgHBP8gv9 FXeqEgwAj7a5AbNbpqO10ect+CldK5kXx9rhjc9qIAOtMMrdvf4Hxowrdd0KCAG7 oqLJaQ1x2KWNwqkwB62vmhp0Q5c+4SXGcPIvSsdxSsTpq71xWavFY67CISBu5vjR luWhu17d93wdiXMM/j58AoNOBNthbUn5EYVU6jzMWcxiY0XUWWXY0K0jnGnNUnKg 5orWa+ulBCMdSboqN2Gjso25eNDmejFhzjLf7dkP1JMoevJk7hkjv+Os4bx76h0H ZcL2lVTugOQ/QkgsZVWjHyIF38mn3Qs3leu2SJgyNXR4XWFTbv/MlxJA6fa3Fpg2 aBCs383Hq+CjreaB316GOqLtEjiab9qijgH9GF/XzS0ZifOW9na6h5BtKV4rFcRf wTKdOlF5dZ+sZfSIXtLViB8hQl48X8vpB+Oww57BpNGr2kauu8ojvWU3Jnl578DB z7QTEVEqUIVww9/cGnlkhv6egwV7OjXUubn2wWVM9aUd6tzuuep4MsSJijEHsq0I mTNqXtas =j8qI -----END PGP SIGNATURE----- --Sig_/+p+C0k=j/GA0jgdi3xdJskN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210321120633.00004136>