Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 Mar 2021 16:18:09 -0400
From:      Jerry <jerry@seibercom.net>
To:        freebsd-questions@freebsd.org
Subject:   Re: OS to replace FreeBSD
Message-ID:  <20210321161809.00007226@seibercom.net>
In-Reply-To: <d65de129-1c2f-09b1-5e59-4e0fa66d5850@panix.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> <20210321142553.000046d6@seibercom.net> <d65de129-1c2f-09b1-5e59-4e0fa66d5850@panix.com>

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

On Sun, 21 Mar 2021 15:16:49 -0400, Kurt Hackenberg stated:
>On 2021/03/21 14:25, Jerry wrote:
>
>> [irritation] =20
>Jerry,
>
>35 years of unhappy experience has shown us that the only effective
>way to deal with Internet flamers is to ignore them. Don't even read
>their messages, and, ideally, make your reader software not even show
>you messages from them. Usenet readers added that automatic filtering
>long ago, for that reason. Some mail readers can also do something
>like that. I suggest that you ignore Mr. Friedman.
>
>You might also moderate your tone slightly, in one way: be less=20
>absolutist. You say FreeBSD is wrong and all other OSes are right. I
>get the impression that it's more like this: there's an obscure
>hardware error, and some OSes either don't trigger it or work around
>it, but FreeBSD currently has a problem with it. But nobody knows for
>sure.

The operational words there are "know for sure". I do know it worked in
versions prior to 12.x and I do know that nearly an entire version of
FreeBSD will have come and gone and nobody has debugged the situation.
Worse, it will be carried over to version 13. That is seriously not
acceptable.

I totally agree that it is an obscure problem, but that does not lessen
the intensity of the problem.

As I have stated before, I find it virtually impossible to believe
that every other OS has magically found a way to work with the
'ASM1142 USB 3.1 Host Controller', which is what the problem seems to
be, (unconfirmed) except FreeBSD. That leads to only two possible
conclusions, either they fixed something that was not broken or they
attempted to fix something that didn't need fixing.

>Now that somebody has volunteered to debug this, maybe it will get=20
>somewhere.

And maybe pigs will fly. One can only hope. Which reminds me, since
they think they have identified the controller that is giving them the
problem, I will be happy to buy a card with that chip and it and send
it to them. I don't know if that would be suitable, but I am willing to
do it. At the very least, it will be a tax deduction.

--=20
Jerry

--Sig_/fmQOdzPNayA2X8bTam1Wzm=
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQGzBAEBCAAdFiEELeCiu2K+9VmEYYgTgHBP8gv9FXcFAmBXqggACgkQgHBP8gv9
FXdHlwv9H1tDcwzaburoRUbXtcIyxMcxo/DqGRN+vgJiaf0e3s3qx6YO31wZZUKQ
2iRizyc7sjvYGDWrRCoWZX4zOteKUSSVJUYvenDbx3ZRN/NIglI0CSDsmetmH8vE
IrUiT5Feo9ck48RWNEKiao37g9ABbK2tKMjYwG+Xdon+dD4/jQR96jTqqE7ldZzf
by4vVhbO08VCykyw1+fSqvqtpyrGwesp0/dkXDpQEWYKdaqAxG3nO3ditFhZPHyM
KeBTXFNGwPpgAFrtXj7QDy7UMZshW3TUR4rcINergIGpurSSn+Qf3dhBEx3lknU+
47qK1rKpZM33yn66/Td22S9O6rCETRfQjp1uqnuRnAUqECAiTYtj1T5e4nyFy7gh
1X2S3xNRSmb6YoujRaqq2vr+q3zaM4veiDpbHLKa4rY7cuUhIyCmbRzzmV5Xu+pf
UZLi+JGdxa5sFODgECCNIS6K2rbaZGQCGlH9MXOpSkmmgfiywFnBI2pnluDnNatN
ZL3zoy4j
=E9oE
-----END PGP SIGNATURE-----

--Sig_/fmQOdzPNayA2X8bTam1Wzm=--



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