NetBSD 2.0 Released

Quique writes "NetBSD 2.0 is the tenth major release of the NetBSD Operating System, and has just been released. It can be downloaded from one of the mirror sites. NetBSD is widely known as the most portable operating system in the world. It currently supports fifty four different system architectures, all from a single source tree, and is always being ported to more. NetBSD 2.0 continues the long tradition with major improvements in file system and memory management performance, major security enhancements, and support for many new platforms and peripherals." The release announcement is also available.

Comments

Re:What are NetBSD's strengths?

[ArbitraryConstant]

"It's just as secure as OpenBSD, not more."

No, it's not.

-a great deal less of the privsep stuff
-no propolice
-no W^X

A number of vulnerabilities common to NetBSD and OpenBSD were mitigated by ProPolice on OpenBSD. That was 1.6... but I didn't see anything about propolice on the 2.0 release page.

"I can't think of anything more secure then OpenBSD at the moment though."

There are special cases where other OSes can be more secure, IMO. For example, on a big system where you have to let people in with permissions to do something interesting, rather than a firewall or a server spewing pages, the FreeBSD jail facility can make it more secure in practical terms.

There's usually a better OpenBSD way to do it, but that way is sometimes enough of a PITA that it doesn'thappen. For example, you can give someone root in a FreeBSD jail and just let them do their thing rather than screwing around with systrace on an OpenBSD machine. Jails are a very blunt tool, but they're very effective.

Apart from localized advantages such as that, OpenBSD is the most secure. I just didn't want anyone to think I was a zealot blind to the advantages of other OSes. :)

Re:Hooray!!

[TCM]

With NetBSD's design I doubt they have a lot of headaches even with many archs. If there's a bug in a chipset driver probably all archs using it are affected and there's only one place to fix it.

The main advantage of having 48 archs is not to actually run NetBSD on each and every one of them productively. It's to abstract your code to such levels that a Realtek NIC is using the very same source on i386 as it does on alpha or sparc. A Realtek on an ISA bus is probably using the same source as one on PCI. And an equal PCI chipset on i386 and alpha is using the same source again. Everything is held together by well-designed glue APIs. Independent of 32bit, 64bit, big endian, little endian, etc. Try to compile your Linux app of the day on something else than 32bit i386..

Really, it's beatiful, you can compile the whole system natively or for a completely different arch by just specifying -m to the build.sh script. It boostraps a self-contained (cross-)compiler environment on any decent POSIXish system. And in the parts that are native to NetBSD you don't get a single compiler warning. The imported GNU utils on the other hand...

'nuff said, try NetBSD!