OS to replace FreeBSD
dpchrist at holgerdanske.com
Fri Mar 19 17:51:03 UTC 2021
On 3/19/21 10:38 AM, Jerry wrote:
> On Fri, 19 Mar 2021 10:13:57 -0700, David Christensen stated:
>> On 3/19/21 7:10 AM, Jerry wrote:
>>> With the soon-to-be release of version 13 of FreeBSD and the EOL of
>>> FreeBSD 11.x, I will need to invest in a new OS. Due to FreeBSD’s
>>> unfortunate inability to squash bug
>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666, l am left
>>> with no choice but to seek out a new OS. I need a bare-bones system
>>> that can run a mail server, Postfix with Dovecot, and a few other
>> Looking at that link, I see:
>> Gerard Seibert 2021-02-25 21:01:04 UTC
>> # dmidecode 3.3
>> Handle 0x0001, DMI type 1, 27 bytes
>> System Information
>> Manufacturer: Dell Inc.
>> Product Name: XPS 8930
>> Version: 1.1.15
>> Serial Number: 19WS903
>> UUID: 4c4c4544-0039-5710-8053-b1c04f393033
>> Wake-up Type: Power Switch
>> SKU Number: 0859
>> Family: XPS
>> Dell says:
>> Operating system
>> With Windows 10 Home
>> So, Windows 10 Home is the only operating system supported by Dell on
>> that computer. Windows 10 Home should not exhibit the bug you have
>> Check if your software is supported on Windows 10 Home. If so,
>> install Windows 10 Home and install your software.
>> Alternatively, get another computer that is known to be compatible
>> with your OS and software of choice.
>> I am running 12.2-RELEASE-p4 GENERIC amd64 without any problems on:
>> * Dell PowerEdge T30 with Intel Xeon E3-1225 v5
>> * Intel S1200V3RPL with Intel Xeon E3-1225 v3
> You are incorrectly interpreting the data. Windows 10 Home is the base
> system. It also comes with Windows 10 Pro as an upgrade.
Blame Dell, not me.
> I have used
> both and FreeBSD 10 & 11 successfully on this unit.
> I will acknowledge that it was a fairly cheap system. I only needed it
> for a mail server and a few other odds and ends.
You got lucky.
> The problem is with FreeBSD's code change between versions 11 and 12.
> The fact that I am not the only one bitten by this bug, and the
> inability of FreeBSD to correct it, and it has been over a year, is
> certainly not encouraging.
That is a consequence of closed hardware, not open software.
> If I had purchased a
> top of the line, cutting edge system then I would certainly not have
> expected FreeBSD to support it. That is one of the reasons I didn't.
And you would be running an OS with paid support and a SLA.
More information about the freebsd-questions