[adrian_b]

It was not only the most stable, but for many applications, especially in networking, it was also the fastest single-threaded operating system, beating easily Linux and Windows XP or 2000.

Unfortunately for FreeBSD, the launch of the Intel Pentium 4 with hyper-threading in 2003, then of the AMD dual-core CPUs in 2005 have made quickly FreeBSD 4 completely obsolete.

The smaller FreeBSD team has required many years until achieving a decent implementation for multi-threaded CPUs and during that time they have remained long behind Linux and other operating systems.

Besides perfect stability (it was normal to not reboot FreeBSD 4 for years) and great networking performance, it also had a much more reliable file system than the competition.

Despite the fact that Windows XP used NTFS and Linux had at least 3 file systems with journaling at that time, where journaling was supposed to make the file systems crash-resistant, I have seen at that time (around 1999-2003) many cases of file system corruptions after power outages, on computers without UPSes which used NTFS or Linux file systems with journaling (on Linux EXT2 without journaling any power outage was very likely to require a complete reinstallation).

During the same power outages, the computers with FreeBSD that used the UFS file system with "soft updates" never experienced any file system corruption, despite the fact that UFS with "soft updates" was not a journaling file system, but only one where the disk write operations were carefully ordered in such a way as to prevent unrecoverable file system corruption in the case of a crash.

[retrac]

> required many years until achieving a decent implementation for multi-threaded CPUs and during that time they have remained long behind Linux and other operating systems

Many OSes at the time had hitches with SMP. BSD was one of them. FreeBSD had SMP in 4.x but almost everything in the kernel was single-threaded and the kernel thread was a major bottleneck.

FreeBSD wasn't alone in this. Linux suffered from a similar problem at the time, also because of the driver architecture. (The infamous "big kernel lock" wasn't fully eliminated until 2011: https://kernelnewbies.org/BigKernelLock)

This is an area where NT was much better, or VMS, or Solaris. And yes, the SMP issue, in hindsight, does partly explain why both Linux and BSD weren't as historically attractive as they otherwise looked, for large systems.

[throw0101d]

> This is an area where NT was much better, or VMS, or Solaris.

The SPARCcenter 2000 was able to have 20 CPUs/sockets in 1993:

* https://en.wikipedia.org/wiki/Sun4d#SPARCcenter_2000

* https://ieeexplore.ieee.org/document/289692

[SomeoneFromCA]

I recently booted old (Freebsd 12) VM and was surprised how _much_ more performant (vs debian) its tcp stack is, even when just browsing.

[dewey]

I somehow have a hard time believing that you can feel the performance of the tcp stack while browsing of all things in a VM, are you sure it can be attributed to that?

[SomeoneFromCA]

Yes, I also have same hard time believing in it, but internet felt snappier.

[anotherhue]

I had this experience recently and realised I had crippled my day to day system with a slow DNS resolver. Suddenly everything was snappy.

[patmorgan23]

Yeah, slow DNS can look like a slow connection, but there are some subtle differences. images/elements will pop differently than if it's just a slow connection.

Had a wicked issue where a firewall was inspecting DNS requests and causing them to take almost 10 seconds to complete. Was hell on the SIP phones, and browsing the Internet was... Interesting.

[SomeoneFromCA]

Huh...may need to check.

[dewey]

Sounds more likely that your OS just had less things going on and your browser not as many extensions running as your daily driver browser.

[SomeoneFromCA]

No, not really. I have many old Linux VMs too, with different degree of rot, and FreeBSD has noticeable smaller tcp connection establishment latency. Youtube opens way faster than on both older and newer linux vms.

[sjsdaiuasgdia]

The issue is that you're performing a test which involves a whole bunch of interconnected layers and then assigning one part of that interconnected system as where the benefits lie.

Why not the TLS implementation? The video drivers and their kernel interfaces? The OS' process scheduling? A dozen other things that might be responsible for the perceived performance difference to one degree or another?

It feels like gamers who blame 90% of multiplayer issues on "the netcode".

It'd be different with data looking specifically at TCP connection establishment timing without a bunch of other stuff involved.

[Sarkie]

It was the tcp stack. Only possible reason.

[hn8305823]

I've only ever lost data on Linux ext* filesystems, never on FreeBSD UFS or ZFS.

20 years ago it was unfortunately not unusual to experience the Linux "nuclear fsck" where it scrolls by so fast and for so long you know it's toast.

[mysteria]

I've 100% had issues with UFS, it's a simple filesystem and subsceptible to corruption. ZFS meanwhile is a different beast altogether which is designed to ensure data integrity at all costs.

[adrian_b]

UFS without soft updates is easily susceptible to corruption.

The "soft updates" option must be chosen when the disk is formatted for good reliability.

As I have said, 20 years ago "soft updates" in UFS worked better than journaling in the other contemporaneous file systems.

Nowadays it is likely that this is no longer true. I am still using FreeBSD in servers, but unlike 20 years ago I can afford UPSes so I no longer see often crashes due to power outages, even if I had one incident some time ago with a battery that had not been replaced yet after the UPS had warned that this is necessary, and when a power outage happened, the UPS worked for less than a minute and the power was cut before system shutdown. Even in this case there was no file system corruption on UFS.

Even with this good recent experience, today I would no longer trust UFS like 20 years ago, because it is said the current FreeBSD maintainers no longer understand the convoluted code that implements "soft updates" in UFS, and in any case most of their file system maintenance and development work is directed at ZFS now.

[throw0101d]

A journal(-like) mechanism was added to soft-upates by McKusick in the 2010 timeframe:

* https://www.youtube.com/watch?v=_NuhRkiInvA (BSDCan)

* https://www.mckusick.com/softdep/suj.pdf

Which also allows snapshots:

* https://freebsdfoundation.org/project/snapshots-on-filesyste...

See also "Journaling versus Soft Updates: Asynchronous Meta-data Protection in File Systems":

* https://www.seltzer.com/assets/publications/Journaling-versu...

[tiffanyh]

OpenBSD recently decided to turn OFF soft update, by default.

https://undeadly.org/cgi?action=article;sid=20230706044554

[ptx]

Although, according to the link, not because there's anything wrong with it, but because other changes they want to make to the filesystem code would risk breaking soft updates.

[sillywalk]

FTA:

Log message: Make softdep mounts a no-op

Softdep is a significant impediment to progressing in the vfs layer so we plan to get it out of the way. It is too clever for us to continue maintaining as it is.

[clausecker]

UFS on FreeBSD is still maintained bz Kirk McKusick, the inventor of soft updates. It's the other BSDs that have trouble as they can't rely on Kirk's expertise.

[hulitu]

ZFS had its own data corruption bug some months ago. TBH, this was a big minus. You really don't expect such things from a filesystem which is in production for years and whos aim is data integrity. Now, to its defence, it is only used by FreeBSD and some nishe linux distributions, so it does not get much testing.

[abrookewood]

Well maybe you missed the news about the bug in EXT4 ... https://news.ycombinator.com/item?id=38585189

[SomeoneFromCA]

Hell no. I worked in an ISP in late 90s. NTFS was absolutely rock reliable, then (much worse)ext2, then (slightly worse) UFS, and then FAT.

[yjftsjthsd-h]

20 years ago is 2004, not the 90s. I don't know, but it's certainly possible that one of them was in the lead in 1995, a different one in 2005, and a different one in 2015. This is especially plausible because Linux was only created in the mid 90s, so those first few years seem likely to have been disproportionately rough.

[adrian_b]

NTFS might have been rock reliable in Windows NT and perhaps also in Windows 2000.

When Windows XP has been launched, NTFS was certainly much less reliable. Even without being affected by any crashes or other anomalies, the free space on the NTFS partitions of early Windows XP computers would shrink steadily, without any apparent cause, requiring a reformatting/reinstallation after some time.

Early Windows XP was very buggy. While a computer with Windows XP did not require one or more reboots per day like one with Windows 98, failing to reboot it for more than a few days guaranteed a crash.

Only after installing several massive service packs in the following years, Windows XP has become reasonably stable.

[SomeoneFromCA]

I live in a developing country. We have constant power blackouts, like every day. Anything not journalling cannot survive that yteatment. Even crappiest XP was better than UFS which absolutely sucked in that respect.

[hulitu]

For me, in the 90s ext2 was much, much reliable than ntfs. After a power failure ext2 will just run fsck and fix the filesystem while ntfs will sometimes give up.

[dizhn]

I don't know if it was a file system related thing but you could bet on the Windows registry being borked beyond repair after just a handful of unexpected power cycles.

[SomeoneFromCA]

No. We had a NT4 server, handful FreeBSDs and one Linux. After several blackouts FreeBSD would lose file or two. NT4 workstation had no problems either, neither with registry nor FS.

[hulitu]

> ISP in late 90s. NTFS was absolutely rock reliable, then

Well, i stayed away from NTFS in the Win2000 era because crashes would make your system unusable.

[SomeoneFromCA]

In 90s it was NT4. Excellent OS.

[bombcar]

Windows 2000 was stable as a rock, NTFS included. Never had an issue with it.

Windows XP was more stable than 98SE, but it did crash more, because it was a general purpose OS used by people playing games. Still can't recall any major NTFS issues with it.

Windows 2000 with XP drivers (edit the INI file to allow it to install) was the way to go ;)

[toast0]

> Unfortunately for FreeBSD, the launch of the Intel Pentium 4 with hyper-threading in 2003, then of the AMD dual-core CPUs in 2005 have made quickly FreeBSD 4 completely obsolete.

FreeBSD 4 wasn't too bad on dual cpu systems, as I recall. Fine grained locking gets more important as cpu counts grow, of course, but at 2, the single Giant lock isn't unreasonable.

[hulitu]

> but for many applications, especially in networking, it was also the fastest single-threaded operating system

If it is single threaded, how does this relates to PS4 and PS5 ?

[Narishma]

It probably only uses one or two cores on consoles, the rest being reserved for the game running.

[hulitu]

Now i get it. I mixed it up with "windows type single threaded" where, even if you had a multiple processor machine, windows will run only on one processor.