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]
