Your message dated Tue, 26 Aug 2008 04:28:00 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: always run bootloader no matter what
has caused the Debian Bug report #451331,
regarding please always run lilo, grub, etc. no matter what
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
451331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451331
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
X-Debbugs-No-Ack: please
Package: linux-image-2.6.22-3-686
Version: 2.6.22-6
Sorry if here we go again.
Upon upgrade to linux-image-2.6.22-3-686 I was told that as I am
installing a version of a running kernel, I should reboot soon, but
not now. So I waited for installation to complete, and rebooted, only
to be greeted by a lilo message "...kernel is big, overlaps lilo's
second stage".
The user is now locked out of his computer.
Unless he pulls the power cord and chooses an older kernel he has
wisely left in the lilo menu.
Then he can run lilo. And reboot. And choose linux-image-2.6.22-3-686
and all is well.
So why was lilo not run at the time I was given the message to reboot
soon? I don't know.
$ cat /etc/kernel-img.conf
# Do not create symbolic links in /
#do_symlinks = Yes
#jidanni:
do_symlinks = No
do_initrd = Yes
do_bootloader = Yes
Am I missing some parameter? Why do I need to mess with this file?
Who knows? One cannot find any info in /usr/share/doc/linux-imag*
And
$ dlocate /etc/kernel-img.conf
shows nobody owns it. Maybe it doesn't matter and is just cruft on my
system... well I did look in /var/lib/dpkg/info/linux* and found its
name... but all that is doing more digging than a user should. It
should all be mentioned in /usr/share/doc/linux-imag* and
/etc/kernel-img.conf should be listed by some program.
Yes you told me the answer before and yes I adjusted accordingly.
But as you don't document anything, one cannot find the answer so here
we go again. Whatever you told me last time didn't help.
Please put official instructions somewhere.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core)
Locale: LANG=zh_TW.utf8, LC_CTYPE=zh_TW.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6.22-3-686 depends on:
ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-24 Yet Another mkInitRD
Versions of packages linux-image-2.6.22-3-686 recommends:
ii libc6-i686 2.6.1-6 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.22-3-686/postinst/bootloader-test-error-2.6.22-3-686:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.22-3-686/preinst/lilo-initrd-2.6.22-3-686: true
linux-image-2.6.22-3-686/prerm/would-invalidate-boot-loader-2.6.22-3-686: true
linux-image-2.6.22-3-686/preinst/overwriting-modules-2.6.22-3-686: true
linux-image-2.6.22-3-686/preinst/elilo-initrd-2.6.22-3-686: true
linux-image-2.6.22-3-686/postinst/kimage-is-a-directory:
linux-image-2.6.22-3-686/preinst/lilo-has-ramdisk:
linux-image-2.6.22-3-686/preinst/initrd-2.6.22-3-686:
linux-image-2.6.22-3-686/postinst/old-initrd-link-2.6.22-3-686: true
linux-image-2.6.22-3-686/postinst/old-system-map-link-2.6.22-3-686: true
* linux-image-2.6.22-3-686/preinst/already-running-this-2.6.22-3-686:
linux-image-2.6.22-3-686/postinst/depmod-error-2.6.22-3-686: false
linux-image-2.6.22-3-686/postinst/bootloader-error-2.6.22-3-686:
linux-image-2.6.22-3-686/preinst/failed-to-move-modules-2.6.22-3-686:
linux-image-2.6.22-3-686/postinst/old-dir-initrd-link-2.6.22-3-686: true
linux-image-2.6.22-3-686/preinst/abort-install-2.6.22-3-686:
linux-image-2.6.22-3-686/preinst/abort-overwrite-2.6.22-3-686:
linux-image-2.6.22-3-686/postinst/depmod-error-initrd-2.6.22-3-686: false
linux-image-2.6.22-3-686/preinst/bootloader-initrd-2.6.22-3-686: true
linux-image-2.6.22-3-686/prerm/removing-running-kernel-2.6.22-3-686: true
linux-image-2.6.22-3-686/postinst/create-kimage-link-2.6.22-3-686: true
--- End Message ---
--- Begin Message ---
On Tue, 26 Aug 2008, [EMAIL PROTECTED] wrote:
> version 451331 2.6.26-3
> retitle 451331 please always run bootloader, no matter what
> thanks
>
> I have an idea: always run the bootloader, no matter what, on any even
> most tiniest dpkg adjustment of the kernel stuff. (With an override
> for experts behind several child safety locks.)
>
> I don't know what you are saving, by being so cautious trying to
> determine if you should run the bootloader or not, but your
> calculations often slip, with the result the user in very likely to be
> locked out of his machine next reboot.
>
> E.g., the most recent incident was upon my
> upgrade linux-image-2.6.26-1-686 2.6.26-2 2.6.26-3
>
> I had commented
> #kernel-img.conf.5.gz says do_bootloader defaults to yes, but then
> #why wasn't the /boot/map file updated? So:
> #test "$(find /boot -type f -cnewer /boot/map)" && lilo
> out in my shutdown script, but now am uncommenting it for life.
>
first of all lilo is *not* the default,
grub is much more handier.
second this is a user fault to comment,
don't do that if you have zero idea what you do.
--- End Message ---
