Post by @analog_feelings@tech.lgbt
Some #NetBSD questions that keep coming up.
We don't use modules for HW drivers in the default install. All baked into the kernel. If you're curious about desktop hardware, for x86 there are lists https://wiki.netbsd.org/laptops/ https://wiki.netbsd.org/gpus/ (and the pci/usb manual pages)
x86 virtual machines. https://www.netbsd.org/docs/guide/en/chap-virt.html#chap-virt-guest
For disk encryption there's different options, such as creating a small root with the installer, then adding encrypted partitions later (see man cgdconfig). Also: cgdroot.
Running commercial games? It is possible, but you'll probably have better luck with DRM-free indie games. https://washbear.neocities.org/valhalla
No audio output? It is possible your default device or output DAC needs to be changed, see the instructions on https://www.netbsd.org/docs/guide/en/chap-audio.html
WireGuard® VPNs? See the EXAMPLES section of https://man.netbsd.org/wg.4
ZFS? Yes, we are using it in production. No, it isn't the same branch as Linux or FreeBSD.
@netbsd I know very little about this area.
Does having all drivers in the kernel cause bloat, and limit device support? Is this likely to be changed?
@happyborg depends what you consider bloat.
$ du -h /netbsd
28M /netbsd
that's amd64. our biggest kernel.
there's certainly advantages to not loading networking drivers as modules (easier to fetch files over a network to recover a broken system)
but there are others who prefer the modular approach. or prefer not to use GENERIC, maybe because they have less than 64mb RAM.
i don't see how it would limit device support.
@netbsd @happyborg is there a mechanism to dynamically load modules?