On Sun, Jul 02, 2006 at 09:43:56AM +0200, Florian Kulzer wrote: > On Sat, Jul 01, 2006 at 23:08:43 -0700, Andrew Sackville-West wrote: > > On Sat, Jul 01, 2006 at 04:00:09PM -0700, Willie Wonka wrote: > > [...] > > > > > > Is that line above showing me that after removing > > > > > kernel-image-2.6.8-3-686...that I'll then be either "upgraded to" or > > > > > "installed" or "running" kernel-image-2.6.8-16 ? Why on earth does it want > > > to > > > > > remove my working Kernel images? > > > > > > > because you've upgraded libc6 which the kernel-images indirectly > > > > depend on. > > > > > > I see - but does it not know that One _needs_ a Kernel-image ?? > > > > with great freedom comes great responsibility. the apt system has no > > way of knowing what your intentions are or whether you have another > > kernel floating around. Maybe there should be some sanity check if the > > running kernel is the same as one to be removed, but who knows. And I > > suppose, once you're running, you don't strictly NEED a kernel > > anymore, provided you don't reboot... > > There is a sanity check in the pre-removal script of the kernel image. > If you try to run > > sudo dpkg -r linux-image-$(uname -r) > > you will see a dialog with an clear warning about what is going to > happen if you don't abort this operation. The dialog defaults to the "I > want my mommy" option, but it will of course allow you to take the "real > men never need to reboot anyway" route. okay, so that probably doesn't show up when you do an apt-get [-s|--simulate|--just-print|--dry-run|...] which makes sense as the script is not actually executed. A
Attachment:
signature.asc
Description: Digital signature