| 2008-06-11 23:16:08 |
Daniel Hahler |
description |
A lot of users break their system by installing the wrong flavor of the virtualbox-ose-modules package (kernel module for virtualbox-ose), e.g. virtualbox-ose-modules-386 on a linux-generic system.
This pulls in linux-image-$ABI-386, through the Depends of virtualbox-ose-modules-386.
After reboot, this new kernel image appears to get used, but it's missing the kernel modules etc.
Therefore, I'd like to change the Depends of virtualbox-ose-modules-$ABI-$FLAVOR to a Recommends instead. This way, installing the wrong virtualbox-ose-modules package would only make virtualbox-ose not work correctly (vboxdrv not available for the used kernel flavor), but won't install a kernel image that the user does not want (and causes him trouble). |
A lot of users break their system by installing the wrong flavor of the virtualbox-ose-modules package (kernel module for virtualbox-ose), e.g. virtualbox-ose-modules-386 on a linux-generic system.
This pulls in linux-image-$ABI-386, through the Depends of virtualbox-ose-modules-386.
After reboot, this new kernel image appears to get used, but it's missing the kernel modules etc.
Therefore, I'd like to change the Depends of virtualbox-ose-modules-$ABI-$FLAVOR to a Recommends instead. This way, installing the wrong virtualbox-ose-modules package would only make virtualbox-ose not work correctly (vboxdrv not available for the used kernel flavor), but won't install a kernel image that the user does not want (and causes him trouble).
Another option would be to depend on the kernel meta packages, e.g. linux-386, linux-generic etc. This way you may still pull in another kernel flavor accidentally, but it would not cause so much harm.
See also bug 188579, which is about apt selecting the most appropriate package automatically.
WORKAROUND / FIX FOR AFFECTED USERS:
In case you're affected by this bug, the following steps or a variation thereof might fix it:
1. Make sure you have two different kernel image flavors installed, e.g. linux-image-2.6.24-18-generic and linux-image-2.6.24-18-386
2. Check "uname -a" to see which one is installed
3. Make sure you can boot the correct one, which would be -generic in most cases - you can select the one to use during boot from the Grub menu
4. Once booted, install the v-o-m package for the correct kernel, e.g. "virtualbox-ose-modules-generic"
5. Remove the unnecessary kernel image package, e.g. linux-image-2.6.24-18-386, and the v-o-m package for it
6. Reboot
|
|
| 2009-10-20 13:12:53 |
Arthur |
description |
A lot of users break their system by installing the wrong flavor of the virtualbox-ose-modules package (kernel module for virtualbox-ose), e.g. virtualbox-ose-modules-386 on a linux-generic system.
This pulls in linux-image-$ABI-386, through the Depends of virtualbox-ose-modules-386.
After reboot, this new kernel image appears to get used, but it's missing the kernel modules etc.
Therefore, I'd like to change the Depends of virtualbox-ose-modules-$ABI-$FLAVOR to a Recommends instead. This way, installing the wrong virtualbox-ose-modules package would only make virtualbox-ose not work correctly (vboxdrv not available for the used kernel flavor), but won't install a kernel image that the user does not want (and causes him trouble).
Another option would be to depend on the kernel meta packages, e.g. linux-386, linux-generic etc. This way you may still pull in another kernel flavor accidentally, but it would not cause so much harm.
See also bug 188579, which is about apt selecting the most appropriate package automatically.
WORKAROUND / FIX FOR AFFECTED USERS:
In case you're affected by this bug, the following steps or a variation thereof might fix it:
1. Make sure you have two different kernel image flavors installed, e.g. linux-image-2.6.24-18-generic and linux-image-2.6.24-18-386
2. Check "uname -a" to see which one is installed
3. Make sure you can boot the correct one, which would be -generic in most cases - you can select the one to use during boot from the Grub menu
4. Once booted, install the v-o-m package for the correct kernel, e.g. "virtualbox-ose-modules-generic"
5. Remove the unnecessary kernel image package, e.g. linux-image-2.6.24-18-386, and the v-o-m package for it
6. Reboot
|
A lot of users break their system by installing the wrong flavor of the virtualbox-ose-modules package (kernel module for virtualbox-ose), e.g. virtualbox-ose-modules-386 on a linux-generic system.
This pulls in linux-image-$ABI-386, through the Depends of virtualbox-ose-modules-386.
After reboot, this new kernel image appears to get used, but it's missing the kernel modules etc.
Therefore, I'd like to change the Depends of virtualbox-ose-modules-$ABI-$FLAVOR to a Recommends instead. This way, installing the wrong virtualbox-ose-modules package would only make virtualbox-ose not work correctly (vboxdrv not available for the used kernel flavor), but won't install a kernel image that the user does not want (and causes him trouble).
Another option would be to depend on the kernel meta packages, e.g. linux-386, linux-generic etc. This way you may still pull in another kernel flavor accidentally, but it would not cause so much harm.
See also bug 188579, which is about apt selecting the most appropriate package automatically.
WORKAROUND / FIX FOR AFFECTED USERS:
In case you're affected by this bug, the following steps or a variation thereof might fix it:
1. Make sure you have two different kernel image flavors installed, e.g. linux-image-2.6.24-18-generic and linux-image-2.6.24-18-386
2. Check "uname -a" to see which one is installed
3. Make sure you can boot the correct one, which would be -generic in most cases - you can select the one to use during boot from the Grub menu
4. Once booted, install the v-o-m package for the correct kernel, e.g. "virtualbox-ose-modules-generic"
5. Remove the unnecessary kernel image package, e.g. linux-image-2.6.24-18-386, and the v-o-m package for it
6. Reboot
|
|
