DragonFly BSD VS NetBSD

People are still actively working on Illumos. The last change was yesterday morning. * https://illumos.org People are still actively working on MirBSD. There's a CVS commit account that can be followed on the FediVerse. * http://www.mirbsd.org It's DragonFly BSD, not Dragon BSD, and the irony of that is that you missed FreeBSD, which is of course still going. * https://dragonflybsd.org * https://freebsd.org As... - Source: Hacker News / 11 months ago

Maybe people don’t recognize that DragonFly (https://dragonflybsd.org) is a BSD? That’s my guess. 🤷‍♀️. Source: over 2 years ago

The idea of config files is fine, it's the implementation I don't like. I was using NetBSD recently for my senior project and found it fine to use - all the documentation is in one place (well, two - the manpages and netbsd.org). It's when the documentation is nonexistent and you have to search through a million different websites and forum posts to find the one line you have to change - that's what gets me. Linus... Source: over 1 year ago

This is what most of the existing open source operating systems are and it is much easier to contribute to those or fork one that does most of what you want. If you are aiming at a POSIX system then there is a fair amount of work but you at least then get a huge amount of already written software that you can run (IIUC Redox is aiming for this but written in Rust). A structure like Qubes OS would make it easier... - Source: Hacker News / about 2 years ago

It looks like one of the vulnerabilities involves being able to sneak in a rogue ICMPv6 route advertisement, with rogue DNS entries. It also mentions doing this kind of stuff against NetBSD 7.1, but that's a couple of versions old, so I guess they were concerned about all the random managed access points floating around? Source: almost 3 years ago