Should ship new kernel modules at same time as new kernel
Bug #253831 reported by
Pascal d'Hermilly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Wishlist
|
Unassigned | ||
linux-meta (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
virtualbox-ose-modules (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: linux-image-
I use virtualbox, and everytime I get a kernel upgrade, e.g. from 2.6.24-19 to 2.6.24-20, my virtualization breaks for several days. It renders the whole virtualization option useless as I can not depend on it.
Anyway, there should be a procedure to make certain that the kernel modules for the new kernel are shipped at the same time as the new kernel.
Otherwise people will stop updating as their computer is often rendered useless at certain tasks for several days after.
//Pascal
Changed in linux: | |
importance: | Undecided → Wishlist |
Changed in linux: | |
status: | Confirmed → Invalid |
To post a comment you must log in.
This could be solved by modifying each module metapackage to depend on an exact version of the corresponding linux-image metapackage. For example:
Package: virtualbox- ose-modules- generic ose-modules- 2.6.26- 5-generic, linux-image-generic (= 2.6.26.5.7)
Depends: virtualbox-
Then kernel upgrades would be held back by default until all the wanted modules are available for the new kernel.