For its excellent backward compatibility: NetBSD 6.1 is still able to run a.out binaries built for NetBSD 1.0
For its system-independant build system. Building NetBSD needs a POSIX system with a C compiler, which does not need to be NetBSD. It first builds the tools for the host, including the compiler itself, and then the target NetBSD system, which may be for another CPU.
For its machine-independant drivers. Have a fancy platform with an odd CPU? If NetBSD has a driver for a chip, it will work a
You dodged the most important question: What is it good for? If I just want to get a job done, is there any kind of "job" beside "having fun setting up a strange OS" where NetBSD would be the appropriate choice?
NetBSD has unmatched features for embedded: cross-building out of the box and machine-independant drivers help a lot here.
It is also very good as a server. The backward compatibility seems to be a detail, but when you think of it, that means easy upgrades: reboot with a newer kernel without upgrading userland, it works. Then drop to single user, unpack up-to-date userland without upgrading the packages, return to multiuser, it works. Install a package built for version n-1, it works.
Why NetBSD? (Score:5, Informative)
Why NetBSD?
That's all? (Score:1)
Re:That's all? (Score:2)
NetBSD has unmatched features for embedded: cross-building out of the box and machine-independant drivers help a lot here.
It is also very good as a server. The backward compatibility seems to be a detail, but when you think of it, that means easy upgrades: reboot with a newer kernel without upgrading userland, it works. Then drop to single user, unpack up-to-date userland without upgrading the packages, return to multiuser, it works. Install a package built for version n-1, it works.