LIS shouldn't be pinned to specific kernel versions and should be distributed as a package via a repository
Much like VMWare, Xen, etc. LIS shouldn't be kernel version specific, ever. Also, LIS should be available for numerous distributions via packages (not tarballs with shell scripts). Finally, LIS should be distributed via repositories (not some random KB number). Adhere to Linux standards and best practices; it'd really help us like you guys more.
Chris Short
shared this idea
2 comments
-
Peter Cruijs
commented
I do agree with all above.
Also by using repositories they could keep their LIS better in-line and fine tuned with the distributions.
Other possible solution could be to hook onto the yum update process and if necessary perform automatic kernel re-compilation after the update are finished.
If this process fails a Linux Vm should still be able to fall back on the drivers ported in the distribution's kernel, but above solution could overcome this issue very easily.
-
Phil Hale
commented
kmods are a step in the right direction for RHEL and it's derivatives (CentOS, Scientific Linux, etc..) but if you need a rebuild each time the kernel updates, you need to look at akmod packages. See https://ask.fedoraproject.org/en/question/55663/how-do-akmod-packages-work/ for more details...