3 ms·
NetBSD is characterized above all by its support for many different hardware platforms (slogan: "Of course it rund NetBSD"). There are currently 57 - including
by doener 3y ago
NetBSD is characterized above all by its support for many different hardware platforms (slogan: "Of course it rund NetBSD"). There are currently 57 - including legacy systems such as Commodore Amiga: https://www.netbsd.org/ports/ https://www.netbsd.org/ports/
Support for all these platforms is based on a single source tree. This is organized into machine-dependent and machine-independent parts. The machine-dependent part contains the parts specific to a particular computer architecture, which establish the connection between the hardware and the independent parts.
This division, together with the central management of the source code, is the reason why newly developed solutions are immediately available on all platforms: The time-consuming backporting of new functions is not necessary. New functions and error corrections in the machine-independent code are immediately available on all supported architectures.
This also applies to the development of new device drivers. A PCI card therefore works on IA-32, DEC Alpha, PowerPC, Sun SPARC and other architectures with PCI support. An Ethernet chip that is included on various PCI, ISA and USB devices only requires a single driver, which is then connected via various bus attachments.
(Partly translated from German Wikipedia: https://de.wikipedia.org/wiki/NetBSD https://de.wikipedia.org/wiki/NetBSD)
- ianai 3y ago(Wild idea) I wonder whether NetBSD could be turned into something like device drivers or firmware? Ie it always provides the same interfaces to a hosting *BSD OS which reflects the hardware. It maybe actually runs on whatever device it’s accessing. Then have OpenBSD tackle system security areas, it’d be a hosting OS. Think minimal, loaded into ram, and maybe system paths mounted ro. Have FreeBSD handle the user interface, possibly somehow the user facing FS, too. It’s fun to dream ;)
- SubjectToChange 3y agoProjects like devicetree exist to help standardize device drivers. (Wild idea) I wonder whether NetBSD could be turned into something like device drivers or firmware? This is actually quite common. The Qualcomm modem in your phone is very likely running QuRT, Intel ME famously runs Minix, Apple apparently uses some version of the L4 micro-kernel family in their Secure Enclave IIRC.
- Avshalom 3y agoIt's not that wild of an idea. Some one has probably played around with using the net bad rump kernel in openbsd.
- LargoLasskhyfv 3y agohttps://en.wikipedia.org/wiki/Rump_kernel https://en.wikipedia.org/wiki/Rump_kernel