OS to replace FreeBSD

freebsd at johnea.net freebsd at johnea.net
Fri Mar 19 21:10:18 UTC 2021

Wow! An amazing amount of distraction from the primary topic on this thread.

On 3/19/21 1:32 PM, Ralf Mardorf wrote:
> On Fri, 19 Mar 2021 11:16:33 -0700, freebsd at johnea.net wrote:
>> Void uses a runit init system with no systemd
> Hi,
> I suspect it's not a good idea to use Linux without systemd. For
> example, by upstream udev is part of systemd. Maintaining Linux without
> systemd is a bottomless pit.

Linux existed for many years prior to systemd. Even after systemd became common, a number of highly used distributions have chosen not to use it. Alternatives to udev, without the rest of systemd, are readily available and highly reliable.

Although as stated in the unquoted portion of the post: use the linux distro that's easiest for you.

The primary point being, confirming if this bug exists, or does not exist, on the exact same motherboard, for the linux kernel, as opposed to the FreeBSD kernel, would be a very valuable data point.

Arguing over linux distro benefits, or what's the best SMTP server s/w, or starting a systemd rant, are all off topic.

> On Fri, 19 Mar 2021 13:35:21 -0400, Aryeh Friedman wrote:
>> Recompiling the kernel is *TRIVIAL* if you refuse to do it then you
>> should not be using any Unix variant
> I dislike this tone of voice. However, I agree that compiling the kernel
> might be less effort, than migrating to another operating system. If you
> would e.g. migrate to Arch Linux, you need to get used to systemd.
> Getting used to systemd isn't pleasant. If you chose a Linux distro
> that doesn't use systemd, you likely will experience all kinds of
> trouble, if you want to customize your install.

I have to agree Ralf, it seems to be blaming the problem on the person experiencing it.

However, if you check the original bug report sited:


You'll see that:

1) quite a few kernels have been built in the effort to track down the cause of this issue.

2) numerous user's experienced this bug on different manufacturer's motherboards

3) this issue did not occur in the 11.x series, but it does occur in both 12.x and 13.x, on affected platforms

Jerry, I would still advocate trying _any_ linux OS on that motherboard just to see if it works. 

Windows is not as much of a test, as Microsoft does work with h/w vendors to make sure windows works on their upcoming hardware releases. However, if FreeBSD works in a virtual machine on the same hardware, that is also a valuable data point.


More information about the freebsd-questions mailing list