[Pkg-virtualbox-devel] Bug#530773: virtualbox-ose pulls inn a module for another kernel than the current one

Sveinung Kvilhaugsvik sveinung84 at users.sourceforge.net
Wed May 27 17:23:52 UTC 2009


Package: virtualbox-ose
Version: 1.6.6-dfsg-3
Severity: wishlist

Hello

Today I installed virtualbox-ose on a Lenny system. It ran kernel
2.6.26-2-amd64. When I installed virtualbox-ose it installed the
kernel module for 2.6.26-1-amd64 (which I hadn't removed) instead of
the module for 2.6.26-2-amd64. Virtualbox worked when installing the
module for the running kernel. This works but could be made easier.

One way to make it easier is to create a module that uses dkms (for
example virtualbox-ose-source-dkms). Dkms will then rebuild the module
automatically when a new kernel is installed. This will let your users
upgrade their kernels without worrying about virtualbox-ose. If you
set it as the default (for example Recommends:
virtualbox-ose-source-dkms | virtualbox-ose-modules,) less advanced
users will get the easy behavior by default. Dkms is currently in sid
and in testing. Ubuntu uses it for their version of virtualbox-ose but
I don't know how much work will be required to use their changes in
Debian.

Sincerely
Sveinung





More information about the Pkg-virtualbox-devel mailing list