4 ms·
I wonder if a metapackage that always depends on kernel <= supported would resolve the issue by ensuring you don't need to pin a specific version manually.
by michaelmrose 3y ago
I wonder if a metapackage that always depends on kernel <= supported would resolve the issue by ensuring you don't need to pin a specific version manually.
- E39M5S62 3y agoThat's the way Void Linux does it. That ensures that the default kernel series always works with ZFS and NVidia modules. If you want to go off-reservation, you can do so but you're on your own, then.
- yjftsjthsd-h 3y agoYep, same on NixOS; just set boot.kernelPackages = config.boot.zfs.package.latestCompatibleLinuxPackages; And you're done.
- rincebrain 3y agoThe problem is that RHEL, for example, loves backporting breaking changes, so you can't know a priori that RHEL's "2.6.18" or whatever is going to keep working, and otherwise you need to push a new metapackage every time they ship an update.