Date: Fri, 19 Mar 2021 11:16:33 -0700 From: freebsd@johnea.net To: freebsd-questions@freebsd.org Subject: Re: OS to replace FreeBSD Message-ID: <c9ca4862-199a-5c6b-1282-18cc32d3486f@johnea.net> In-Reply-To: <20210319140448.00007521@seibercom.net> References: <20210319101040.00005c35@seibercom.net> <CA%2BD9QhsjLtVui6exPDyG2CO5H8X-=YckFjCehHusG7eH_kk2sg@mail.gmail.com> <6054BE1B.50706@gmail.com> <20210319130249.000042a1@seibercom.net> <5a8cf0be-646a-a433-2428-9700a47c1bf0@att.net> <20210319140448.00007521@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/19/21 11:04 AM, Jerry wrote: > I had considered using a different flavor of BSD. I still might. > However, I also happen to have a spare HD that I could plug into the > system, install Windows 10 Pro and Hyper V and then see if FreeBSD 12.x > or newer works correctly. That would only take a short amount of time. > I just need to do it at night so I can take the system offline. > > It probably won't work, but if FreeBSD is isolated from the hardware, > it might be all that is needed in the short run. > > -- Jerry You should really consider trying some version of linux as well. Whatever you're most familiar with. Arch is considered "bleeding edge" and you'll get something very close to the latest version of kernel and applications. Void uses a runit init system with no systemd, and an architecture that is more similar than other linux distributions to the BSD way. Any linux distribution will still give you _the_ linux kernel, so which distribution is chosen probably doesn't matter that much. Use whatever is easiest for you. Also, this testing of linux USB3 on this particular problematic hardware could give additional insights into the problem on FreeBSD... johnea
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c9ca4862-199a-5c6b-1282-18cc32d3486f>