[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#421110: Upgrading linux-image-2.6.20-1-686-bigmem should never happen



Package: linux-image-2.6.20-1-686-bigmem
Version: 2.6.20-3
Severity: normal

When upgrading the package used by the currently running kernel,
the package installer give a big warning about how it's dangerous
and requires a prompt reboot.

In my case I'd much rather that such things simply *never* happen.

Maybe instead of upgrading linux-image-2.6.20-1-686-bigmem_2.6.20-2_i386.deb
to linux-image-2.6.20-1-686-bigmem_2.6.20-3_i386.deb, I'd rather
that it be an upgrade from
linux-image-2.6.20-2-686-bigmem_2.6.20-2_i386.deb to
linux-image-2.6.20-3-686-bigmem_2.6.20-3_i386.deb
I.e. it would require an explicit command on my part to install the newer
kernel.

But I think an even better solution would be as follows:

  at boot, copy /lib/modules/<kernvers> to /lib/modules/current
  and let modprobe only refer to /lib/modules/current after that.

This way, upgrading a running kernel won't require an immediate reboot
and will not prevent a subsequent hibernation either (provided we also
copy the running kernel to /boot/vmlinuz-current, etc...).


	Stefan


-- Package-specific info:

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.20-1-686-bigmem depends on:
ii  initramfs-tools [linux-initra 0.85g      tools for generating an initramfs
ii  module-init-tools             3.3-pre4-2 tools for managing Linux kernel mo

Versions of packages linux-image-2.6.20-1-686-bigmem recommends:
ii  libc6-i686                  2.3.6.ds1-13 GNU C Library: Shared libraries [i

-- debconf information excluded



Reply to: