You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue of automatically selecting the latest kernel where ZFS is supported came up during the 5.12 init, linux_latest bump and probably many times before.
A linux_latest_zfs package has been suggested but it has rightly been pointed out that this is not an ideal solution as it only covers one module, not the n! combinations of modules one could want to use.
An ideal solution to this issue would be a function which takes a list of modules and returns the newest linuxPackages where none of those modules are broken.
You could then use that for your boot.kernelPackages and, ideally, plug your boot.kernelModules into it.
Actually, if such a function existed, it might even make a good default in combination with new NixOS option to control whether non-lts kernels should be eligible for selection (off by default).
Needed for this are:
A set of all linuxPackages variants
All broken modules to be marked as such on the correct versions.
The text was updated successfully, but these errors were encountered:
This is not something we should have as it would require a SAT solver like a traditional package manager.
If you need OOT modules, you should use an LTS kernel anyways and do your research which one is supported by the modules you need.
If modules properly mark their supported version range, broken combinations should quickly abort eval which should make for a quick enough feedback cycle.
Issue description
The issue of automatically selecting the latest kernel where ZFS is supported came up during the 5.12 init, linux_latest bump and probably many times before.
A
linux_latest_zfs
package has been suggested but it has rightly been pointed out that this is not an ideal solution as it only covers one module, not the n! combinations of modules one could want to use.An ideal solution to this issue would be a function which takes a list of modules and returns the newest
linuxPackages
where none of those modules are broken.You could then use that for your
boot.kernelPackages
and, ideally, plug your boot.kernelModules into it.Actually, if such a function existed, it might even make a good default in combination with new NixOS option to control whether non-lts kernels should be eligible for selection (off by default).
Needed for this are:
The text was updated successfully, but these errors were encountered: