Hello! On Wed, Jul 14, 2004 at 10:04:43AM +0200, Adrian 'Dagurashibanipal' von Bidder wrote: > On Tuesday 13 July 2004 18.31, Christer Solskogen wrote: > > Mostly kernel-image-2.6.7-1-686, and base-config. > > kernel-image: I guess dpkg *could* have code to check if it's the > currently running kernel and refuse to deinstall it if it is. But it > would have to deal with >10 different bootloaders (probably >20, I > don't know) So this would be very ugly to maintain... dpkg does check whether one wants to uninstall the currently running kernel: | # dpkg --purge kernel-image-2.4.26-ll | (Reading database ... 50766 files and directories currently installed.) | Removing kernel-image-2.4.26-ll ... | | You are running a kernel (version 2.4.26-ll) and attempting to remove | the same version. This is a potentially disastrous action. Not only | will /boot/vmlinuz-2.4.26-ll be removed, making it impossible to boot | it, (you will have to take action to change your boot loader to boot | a new kernel), it will also remove all modules under the directory | /lib/modules/2.4.26-ll. Just having a copy of the kernel image is not | enough, you will have to replace the modules too. | | I repeat, this is very dangerous. If at all in doubt, answer | no. If you know exactly what you are doing, and are prepared to | hose your system, then answer Yes. | Remove the running kernel image (not recommended) [No]? | dpkg: error processing kernel-image-2.4.26-ll (--purge): | subprocess pre-removal script returned error exit status 1 | Errors were encountered while processing: | kernel-image-2.4.26-ll Cheers, Flo
Attachment:
signature.asc
Description: Digital signature