Live data from Hacker News

NetBSD 11.0

blog.netbsd.org

171–173 of 173 posts

Re: NetBSD 11.0

#171
post #106

Earlier quoted context omitted.

MirOS BSD is still around, too.

> MirOS BSD is still around, too. According to [1], - the most recent release was from March 16, 2008; 18 years ago - the most recent preview was from January 17, 2016; 10 years ago So, despite the fact that the MirOS website [2] has some small News updates from 2026, I would see the evidence on the side that MirBSD is dead, but I would love to be proven wrong on this point. --- [1] https://en.wikipedia.org/w/index.p…

The old fallacies of WWW site changes equals software changes, and unchanged code equals non-existence, and Wikipedia being gospel for computing topics, rear their ugly heads again.

I follow the FediVerse robot that announces MirBSD CVS updates, which is quite active. The last major change, apart from some doco, was a fix to rdate at the end of May 2026, just 2 months ago. And even if MirOS BSD were unchanged for longer than that, it would very much still be around.

Re: NetBSD 11.0

#172
post #132

Earlier quoted context omitted.

Does it have Bluetooth, because OpenBSD still doesn't.

“Still doesn’t”, is a weird way of saying “OpenBSD removed support for Bluetooth because Bluetooth is not secure”.

Regardless of the reason, it still doesn't have Bluetooth, so I still can't use it.

Re: NetBSD 11.0

#173

Earlier quoted context omitted.

I am tempted, how do you deal with the non journalized filesystem? This is the one "modern" comfort that makes me hesitant to try.

Nowadays, the journalized filesystems of Linux, and also NTFS of Windows are quite mature and many of their early bugs have been fixed. Many years ago that was not true. In the early years after 2000, I have witnessed a great number of computer crashes caused by power failures. All the HDDs using journalized filesystems were corrupted sooner or later, including NTFS, ext3, reiserfs, XFS. The only filesystem that was…

> In the early years after 2000, I have witnessed a great number of computer crashes caused by power failures.

Don't enable write cache without a power backup, or on an unstable machine.

> Therefore OpenBSD should be used with an UPS (or on a laptop).

NVMe with PLP is suffice.

The same helps me on my NAS as well, with ZFS and Linux. No need for OpenBSD.

Soft updates was very cool when I first used it, like 25 years ago. Linux didn't have Ext3FS yet, or just about got it. ZFS also worked very early on FreeBSD, but nowadays the standard is OpenZFS.

There's a couple of cool things coming from OpenBSD camp, most notably OpenSSH and PF.

Post reply on HN