Package: kqemu-source
Version: 1.3.0~pre9-5
Severity: important
Removing a kqemu modules package removes /dev/kqemu even if there are
other kqemu packages installed. Here is a scenerio that shows this a
big problem:
1. Install kqemu-modules for some kernel, say, 2.6.17.
2. Sometime in the future, install a new kernel, say, 2.6.18.
3. Install kqemu-modules for the new kernel.
4. Reboot into the 2.6.18 kernel. So far so good.
5. Now, remove the 2.6.17 kernel & the matching kqemu modules.
6. Removal of the 2.6.17 version DELETES /dev/kqemu, even though it's
still be used by the currently active 2.6.18 kqemu modules!
I actually see a number of issues:
* /dev/kqemu should not be deleted on remove, but only on purge
* Even on purge, it should not be deleted if other kqemu-* packages
are still installed.
* /dev/kqemu should not be deleted anyway unless it was originally
created by the package (i.e. was not created by udev).
I think the cleanest way to fix this might be to introduce a
kqemu-common package that all kqemu-modules-* packages could depend on.
The common package could handle the /dev/kqemu stuff as well as any
potential module scripts (e.g. /etc/modprobe.d/*, /etc/modutils/*, or
/etc/udev/* stuff).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
