Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-08-01 Thread Jonas Smedegaard
package initramfs-tools
severity 380292 serious
thanks

On Sat, 29 Jul 2006 10:29:12 +0200 maximilian attems wrote:

 On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote:
  
  I upgraded this image and the installation process re-ran lilo.
  This had the unfortunate effect of taking control of the boot back
  from grub, and of making my system unbootable.

 yes it seems to be an initramfs-tools trouble.
 lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst
 but a /etc/lilo.conf and lilo -t runs successfully


Debian policy, section 3.9.1, states the following:

 If a package has a vitally important piece of information to pass to
 the user (such as don't run me as I am, you must edit the following
 configuration files first or you risk your system emitting
 badly-formatted messages), it should display this in the `config' or
 `postinst' script and prompt the user to hit return to acknowledge
 the message.  Copyright messages do not count as vitally important
 (they belong in `/usr/share/doc/package/copyright'); neither do
 instructions on how to use a program (these should be in on-line
 documentation, where all the users can see them).

I consider it vital to be able to boot the machine.


Kind regards,

 - Jonas

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm


pgpZLsuxQqAKB.pgp
Description: PGP signature


Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread maximilian attems
reassign 380292 initramfs-tools
thanks


hello ross,

On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote:
 
 I upgraded this image and the installation process re-ran lilo.  This
 had the unfortunate effect of taking control of the boot back from
 grub, and of making my system unbootable.

blaeh
 
 I've reinstalled grub (i.e., I'm OK), but I thought lilo was no longer
 getting run by default.  I was so sure, I didn't even check before
 reboot :(.

try to install grub _and_ removing lilo as workaround.
 
 
 If this misbehavior belongs to some other package (e.g., initramfs)
 please reassign as appropriate.

yes it seems to be an initramfs-tools trouble.
lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst
but a /etc/lilo.conf and lilo -t runs successfully

 Here's the relevant part of my log:
 --
 Preparing to replace linux-image-2.6.16-2-k7-smp 2.6.16-15 (using 
 .../linux-image-2.6.16-2-k7-smp_2.6.16-17_i386.deb) ...
 The directory /lib/modules/2.6.16-2-k7-smp still exists. Continuing as 
 directed.
 Configuring linux-image-2.6.16-2-k7-smp
 ---
 
  The kernel version running is the same as the one being installed
 
 You are attempting to install a kernel version that is the same as the 
 version you are currently running (version
 2.6.16-2-k7-smp). The modules list is quite likely to have been changed, and 
 the modules dependency file
 /lib/modules/2.6.16-2-k7-smp/modules.dep needs to be re-built. It can not be 
 built correctly right now, since the module
 list for the running kernel are likely to be different from the kernel 
 installed. I am creating a new modules.dep file, but
 that may not be correct. It shall be regenerated correctly at next reboot.
 
 I repeat: you have to reboot in order for the modules file to be created 
 correctly. Until you reboot, it may be impossible
 to load some modules. Reboot as soon as this install is finished (Do not 
 reboot right now, since you may not be able to
 boot back up until installation is over, but boot immediately after). I can 
 not stress that too much. You need to reboot
 soon.
 
 Done.
 Unpacking replacement linux-image-2.6.16-2-k7-smp ...
 
 
 # and later
 
 Setting up linux-image-2.6.16-2-k7-smp (2.6.16-17) ...
 
  Hmm. The package shipped with a symbolic link 
 /lib/modules/2.6.16-2-k7-smp/source
  However, I can not read the target: No such file or directory
  Therefore, I am deleting /lib/modules/2.6.16-2-k7-smp/source
 
 Running depmod.
 Finding valid ramdisk creators.
 Using mkinitramfs-kpkg to build the ramdisk.
 Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
 Not updating initrd symbolic links since we are being updated/reinstalled
 (2.6.16-15 was configured last, according to dpkg)
 Not updating image symbolic links since we are being updated/reinstalled
 (2.6.16-15 was configured last, according to dpkg)
 You already have a LILO configuration in /etc/lilo.conf
 Testing lilo.conf ...
 Testing successful.
 Installing the partition boot sector...
 Running /sbin/lilo  ...
 Installation successful.
 -
 
 My system has both grub and lilo on it.  Originally I used lilo, but I
 switched to grub.

please post output
dpkg -l grub
( [ -x /sbin/grub ] || [ -e /boot/grub/menu.lst ] ) || echo no grub
does any of those file exist.
 
 P.S. reportbug gave me a bunch of messages about checksum mismatches
 with various files.  I suspect it took the checksum with the old
 kernel's files, and isn't happy now that the new ones are there.

those you can safely ignore.

 
regards

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread maximilian attems

On Sat, Jul 29, 2006 at 10:08:49AM -0700, Ross Boylan wrote:
 On Sat, Jul 29, 2006 at 10:29:12AM +0200, maximilian attems wrote:
  On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote:
 
  yes it seems to be an initramfs-tools trouble.
  lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst
 Is the statement lilo is only run if... about the basic kernel
 installation process?  And initramfs-tools doesn't follow this logic?

no this is current initramfs-tools logic.
 
  but a /etc/lilo.conf and lilo -t runs successfully
 
 
  please post output
  dpkg -l grub
 ii  grub  0.97-12 

looks fine.

  ( [ -x /sbin/grub ] || [ -e /boot/grub/menu.lst ] ) || echo no
  grub
 There is not output; both of the files in the tests exist.

ok cool, please post the output of 
dpkg-reconfigure linux-image-2.6.16-2-k7-smp

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread Ross Boylan
On Sat, Jul 29, 2006 at 10:29:12AM +0200, maximilian attems wrote:
 reassign 380292 initramfs-tools
 thanks
 
 
 hello ross,
 
 On Fri, Jul 28, 2006 at 06:56:29PM -0700, Ross Boylan wrote:

 yes it seems to be an initramfs-tools trouble.
 lilo is only run if there is no /sbin/grub or no /boot/grub/menu.lst
Is the statement lilo is only run if... about the basic kernel
installation process?  And initramfs-tools doesn't follow this logic?

 but a /etc/lilo.conf and lilo -t runs successfully


 please post output
 dpkg -l grub
ii  grub  0.97-12 
 ( [ -x /sbin/grub ] || [ -e /boot/grub/menu.lst ] ) || echo no
 grub
There is not output; both of the files in the tests exist.

 does any of those file exist.

Thanks.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread Ross Boylan
On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote:

 ok cool, please post the output of 
 dpkg-reconfigure linux-image-2.6.16-2-k7-smp
 
 --
 maks
Script started on Sat Jul 29 11:15:17 2006
iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp
Sat Jul 29 11:15:39 PDT 2006
Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Not updating initrd symbolic links since we are being updated/reinstalled 
(2.6.16-17 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled 
(2.6.16-17 was configured last, according to dpkg)
You already have a LILO configuration in /etc/lilo.conf
Testing lilo.conf ... 
Testing successful.
Installing the partition boot sector... 
Running /sbin/lilo  ... 
Installation successful.
iron:~# dpkg -S mkinitramfs-kpkg
initramfs-tools: /usr/sbin/mkinitramfs-kpkg
initramfs-tools: /usr/share/man/man8/mkinitramfs-kpkg.8.gz
iron:~# exit
exit

Script done on Sat Jul 29 11:16:49 2006


Ugh; looks like I've reinstalled lilo.  Unfortunately, grub can't
install from within my system when it's running; at least, I haven't
found a way (EVMS is confusing it).


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread Ross Boylan
On Sat, Jul 29, 2006 at 09:20:21PM +0200, maximilian attems wrote:
 reassign 380292 kernel-package
 stop
 
 On Sat, Jul 29, 2006 at 11:20:55AM -0700, Ross Boylan wrote:
  On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote:
  
   ok cool, please post the output of 
   dpkg-reconfigure linux-image-2.6.16-2-k7-smp
   
   --
   maks
  Script started on Sat Jul 29 11:15:17 2006
  iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp
  Sat Jul 29 11:15:39 PDT 2006
  Running depmod.
  Finding valid ramdisk creators.
  Using mkinitramfs-kpkg to build the ramdisk.
  Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
  Not updating initrd symbolic links since we are being updated/reinstalled 
  (2.6.16-17 was configured last, according to dpkg)
  Not updating image symbolic links since we are being updated/reinstalled 
  (2.6.16-17 was configured last, according to dpkg)
  You already have a LILO configuration in /etc/lilo.conf
  Testing lilo.conf ... 
  Testing successful.
  Installing the partition boot sector... 
  Running /sbin/lilo  ... 
  Installation successful.
  iron:~# dpkg -S mkinitramfs-kpkg
  initramfs-tools: /usr/sbin/mkinitramfs-kpkg
  initramfs-tools: /usr/share/man/man8/mkinitramfs-kpkg.8.gz
  iron:~# exit
  exit
  
  Script done on Sat Jul 29 11:16:49 2006
 
 aboves didn't run mkinitramfs-kpkg, so passing this to Manoj.
 he might need your make-kpkg settings, so please post
 cat /etc/kernel-img.conf 
  

# Kernel Image management overrides
# See kernel-img.conf(5) for details
do_symlinks = Yes
do_initrd = Yes

  
  Ugh; looks like I've reinstalled lilo.  Unfortunately, grub can't
  install from within my system when it's running; at least, I haven't
  found a way (EVMS is confusing it).
 
 try grub-install or if it fails the grub shell usally works
 - http://www.itp.tuwien.ac.at/~mattems/blog/2006/01/18#grub_install
 
Thanks for the  tips.

Ross


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread maximilian attems
reassign 380292 kernel-package
stop

On Sat, Jul 29, 2006 at 11:20:55AM -0700, Ross Boylan wrote:
 On Sat, Jul 29, 2006 at 07:29:21PM +0200, maximilian attems wrote:
 
  ok cool, please post the output of 
  dpkg-reconfigure linux-image-2.6.16-2-k7-smp
  
  --
  maks
 Script started on Sat Jul 29 11:15:17 2006
 iron:~# date; dpkg-reconfigure linux-image-2.6.16-2-k7-smp
 Sat Jul 29 11:15:39 PDT 2006
 Running depmod.
 Finding valid ramdisk creators.
 Using mkinitramfs-kpkg to build the ramdisk.
 Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
 Not updating initrd symbolic links since we are being updated/reinstalled 
 (2.6.16-17 was configured last, according to dpkg)
 Not updating image symbolic links since we are being updated/reinstalled 
 (2.6.16-17 was configured last, according to dpkg)
 You already have a LILO configuration in /etc/lilo.conf
 Testing lilo.conf ... 
 Testing successful.
 Installing the partition boot sector... 
 Running /sbin/lilo  ... 
 Installation successful.
 iron:~# dpkg -S mkinitramfs-kpkg
 initramfs-tools: /usr/sbin/mkinitramfs-kpkg
 initramfs-tools: /usr/share/man/man8/mkinitramfs-kpkg.8.gz
 iron:~# exit
 exit
 
 Script done on Sat Jul 29 11:16:49 2006

aboves didn't run mkinitramfs-kpkg, so passing this to Manoj.
he might need your make-kpkg settings, so please post
cat /etc/kernel-img.conf 
 
 
 Ugh; looks like I've reinstalled lilo.  Unfortunately, grub can't
 install from within my system when it's running; at least, I haven't
 found a way (EVMS is confusing it).

try grub-install or if it fails the grub shell usally works
- http://www.itp.tuwien.ac.at/~mattems/blog/2006/01/18#grub_install

all the best and thanks for your report.

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-29 Thread maximilian attems
On Sat, 29 Jul 2006, Ross Boylan wrote:

 # Kernel Image management overrides
 # See kernel-img.conf(5) for details
 do_symlinks = Yes
 do_initrd = Yes

current i386 default bootloader in kernel-package is still lilo,
so if lilo and /etc/lilo.conf is around than lilo gets installed.
you can set it explicitly off, add the following line to kernel-img.conf:
do_bootloader = No
 
there are thoughts of switching that default,
keeping your bug report as reminder.

best regards

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#380292: linux-image-2.6.16-2-k7-smp: upgrade re-ran lilo

2006-07-28 Thread Ross Boylan
Package: linux-image-2.6.16-2-k7-smp
Version: 2.6.16-17
Severity: normal

I upgraded this image and the installation process re-ran lilo.  This
had the unfortunate effect of taking control of the boot back from
grub, and of making my system unbootable.

I've reinstalled grub (i.e., I'm OK), but I thought lilo was no longer
getting run by default.  I was so sure, I didn't even check before
reboot :(.

If this is actually a feature, feel free to close (though I'd
appreciate knowing if there is a way to disable it).

If this misbehavior belongs to some other package (e.g., initramfs)
please reassign as appropriate.

Here's the relevant part of my log:
--
Preparing to replace linux-image-2.6.16-2-k7-smp 2.6.16-15 (using 
.../linux-image-2.6.16-2-k7-smp_2.6.16-17_i386.deb) ...
The directory /lib/modules/2.6.16-2-k7-smp still exists. Continuing as directed.
Configuring linux-image-2.6.16-2-k7-smp
---

 The kernel version running is the same as the one being installed

You are attempting to install a kernel version that is the same as the version 
you are currently running (version
2.6.16-2-k7-smp). The modules list is quite likely to have been changed, and 
the modules dependency file
/lib/modules/2.6.16-2-k7-smp/modules.dep needs to be re-built. It can not be 
built correctly right now, since the module
list for the running kernel are likely to be different from the kernel 
installed. I am creating a new modules.dep file, but
that may not be correct. It shall be regenerated correctly at next reboot.

I repeat: you have to reboot in order for the modules file to be created 
correctly. Until you reboot, it may be impossible
to load some modules. Reboot as soon as this install is finished (Do not reboot 
right now, since you may not be able to
boot back up until installation is over, but boot immediately after). I can not 
stress that too much. You need to reboot
soon.

Done.
Unpacking replacement linux-image-2.6.16-2-k7-smp ...


# and later

Setting up linux-image-2.6.16-2-k7-smp (2.6.16-17) ...

 Hmm. The package shipped with a symbolic link 
/lib/modules/2.6.16-2-k7-smp/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/2.6.16-2-k7-smp/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitramfs-kpkg to build the ramdisk.
Other valid candidates: mkinitramfs-kpkg mkinitrd.yaird
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.16-15 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.16-15 was configured last, according to dpkg)
You already have a LILO configuration in /etc/lilo.conf
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Running /sbin/lilo  ...
Installation successful.
-

My system has both grub and lilo on it.  Originally I used lilo, but I
switched to grub.

P.S. reportbug gave me a bunch of messages about checksum mismatches
with various files.  I suspect it took the checksum with the old
kernel's files, and isn't happy now that the new ones are there.



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-k7-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages linux-image-2.6.16-2-k7-smp depends on:
ii  initramfs-tools [linux-initra 0.69b  tools for generating an initramfs
ii  module-init-tools 3.2.2-3tools for managing Linux kernel mo
ii  yaird [linux-initramfs-tool]  0.0.12-15  Yet Another mkInitRD

Versions of packages linux-image-2.6.16-2-k7-smp recommends:
pn  libc6-i686none (no description available)

-- debconf information:
  linux-image-2.6.16-2-k7-smp/preinst/overwriting-modules-2.6.16-2-k7-smp: true
  linux-image-2.6.16-2-k7-smp/postinst/old-dir-initrd-link-2.6.16-2-k7-smp: true
* linux-image-2.6.16-2-k7-smp/preinst/already-running-this-2.6.16-2-k7-smp:
  linux-image-2.6.16-2-k7-smp/preinst/abort-overwrite-2.6.16-2-k7-smp:
  linux-image-2.6.16-2-k7-smp/preinst/initrd-2.6.16-2-k7-smp:
  linux-image-2.6.16-2-k7-smp/postinst/old-initrd-link-2.6.16-2-k7-smp: true
  linux-image-2.6.16-2-k7-smp/preinst/lilo-has-ramdisk:
  linux-image-2.6.16-2-k7-smp/postinst/create-kimage-link-2.6.16-2-k7-smp: true
  
linux-image-2.6.16-2-k7-smp/prerm/would-invalidate-boot-loader-2.6.16-2-k7-smp: 
true
  linux-image-2.6.16-2-k7-smp/preinst/abort-install-2.6.16-2-k7-smp:
  linux-image-2.6.16-2-k7-smp/postinst/kimage-is-a-directory:
  linux-image-2.6.16-2-k7-smp/prerm/removing-running-kernel-2.6.16-2-k7-smp: 
true
  linux-image-2.6.16-2-k7-smp/preinst/elilo-initrd-2.6.16-2-k7-smp: true