This is a semantic quagmire, and the threads on what undefined behaviour is are interminable. But just note this time around that correctness is not the same as conformity.
What's the difference? There's no such thing as "incorrect C++, but still C++." A program is either correct/valid/conforming C++, or it's not. We can reasonably describe "not" as "incorrect," or "invalid," "nonconforming," or just "not C++."
A long time since I've looked into LFS on NetBSD. At the time reading up on it, out of curiosity, wanting to try it out, I got the impression that it is very experimental, and nobody was really using it in production/as a daily driver. Something about the cleaner-demon crashing over and over again. So I noped out.
Has that changed meanwhile, or is that just one of the things that are still advertised as somehow supported, while in reality that happened in a galaxy a long time sideways, in some Jedi hideout?
- 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.
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.
As someone who has used old BSDs, I can say from direct experience that it does not.
For starters, on the old BSDs there was no Almquist shell, unless you went to Usenet, grabbed the shar, and built it. The TENEX C shell was the hot new thing, as were BIND and Sendmail. And we got genuine Joy+Horton vi.
Whereas modern NetBSD does not have Sendmail any more, has nvi2, and supports access control lists. And of course under the covers has lots of things that the old BSDs didn't have, like UFS for TiB disc volumes and kqueue.
I've heard tell that they're even thinking of finally doing away with BIND in base.
IMO an operating system in 2026 that still has a command which, when run without any arguments ("ldconfig"), silently bricks your entire system without warning... is probably due for some changes.
The same command on other OSes does not cause such damage.
https://man.netbsd.org/ldconfig.8 states that it checks the contents of /etc/ld.so.conf - what is the default configuration of that file when it is installed? Is it empty?
If you're going to support the ADM-3A terminal up/down navigation characters k and j, also support the vi navigation characters Control+N and Control+P. And Control+S and Control+Q for pause/resume as well.
It's bad the other way, too. btop on a 50×232 terminal over an actual 57600 BPS serial line is unusable, even in 16-colour mode. It does not have even the most basic of full-screen TUI redraw optimizations, and outputs the entire screen again and again.
Well, unless one is using FreeBSD or OpenBSD, where the btop code is still using 32-bit integers to calculate 64-bit sizes, and falling prey to unsigned integer wraparound. htop's code calculates using size_t, which ends up as a 64-bit integer on 64-bit architectures.
Screws have been around for about 3 millennia at this point. They have patently failed to obviate the use of nails. So by this analogy we can expect the 'Only GPUs do the work.' believers to be still promising this, any day now, about three thousand years hence. (-:
