|
|
|
|
|
by danharaj
2657 days ago
|
|
That's entirely reasonable, and if you're in such a situation you probably don't want to ship a NixOS image. I've been in situations like that and I still prefer to use Nix (which is just the dependency manager) to build such images. I'd be curious if you could take a look and peruse this list of packages that are Kernel dependent and let me know which you think are unreasonably dependent: https://pastebin.com/njS40UzP |
|
The moment you try to live in a world where nix isn't controlling the kernel, most of those packages are unreasonable. Several provide both a kernel module and userspace tools. Wireguard, VirtualBox, OpenAFS are prime examples that jump out at me. It's totally reasonable to wish to install the userland portion of any of these packages without adding a kernel you cant even use to your system image.
My personal preference would be to see such packages split, with the kernel module package treated as an optional dependency for the userland package. Then the kmod can drag in the kernel and headers only when needed.