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
Have you considered lending the machine to a NetBSD developer? In order to have hardware supported, we need the conjunction of (access to hardware, skills, time). You may lack the second entry of the tuple, but someone else may just lack the first one.
NetBSD mailing lists (port-sgimips here) are the right place to discuss such an arrangement
Why NetBSD? (Score:5, Informative)
Why NetBSD?
Re: (Score:2)
The one system I really wanted to run NetBSD on isn't supported (SGI Octane). Ruined the whole "Of course it runs NetBSD" joke for me.
Re: (Score:5, Informative)
Have you considered lending the machine to a NetBSD developer? In order to have hardware supported, we need the conjunction of (access to hardware, skills, time). You may lack the second entry of the tuple, but someone else may just lack the first one.
NetBSD mailing lists (port-sgimips here) are the right place to discuss such an arrangement
Comment removed (Score:4, Informative)