I just dist-upgraded dapper after a few days of not doing it. It installed a new kernel, asked whether to run lilo, and I replied in the affirmative, as always. lilo just hung. It's bene stuck for half an hour now.
Here's a copy/paste from the terminal window:
-----------------------------------------------------------------
A new kernel image has been installed at /boot/vmlinuz-2.6.15-22-686
(Size: 1470kB)
Symbolic links, unless otherwise specified, can be found in /
LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.
WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes]
Testing lilo.conf ...
-----------------------------------------------------------------
I just dist-upgraded dapper after a few days of not doing it. It installed a new kernel, asked whether to run lilo, and I replied in the affirmative, as always. lilo just hung. It's bene stuck for half an hour now.
Here's a copy/paste from the terminal window:
------- ------- ------- ------- ------- ------- ------- ------- ------- -- 2.6.15- 22-686
A new kernel image has been installed at /boot/vmlinuz-
(Size: 1470kB)
Initial rootdisk image: /boot/initrd. img-2.6. 15-22-686 (Size: 6600kB)
Symbolic links, unless otherwise specified, can be found in /
LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.
WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.
You already have a LILO configuration in /etc/lilo.conf ------- ------- ------- ------- ------- ------- ------- ------- --
Install a boot block using the existing /etc/lilo.conf? [Yes]
Testing lilo.conf ...
-------
These are the processes which are running:
------- ------- ------- ------- ------- ------- ------- ------- ------- -- manager3 libexo-0.3-0 xfce4-terminal xfce4-panel xfce4-mixer xfce4-mixer-alsa xfce4-systemloa d-plugin libhal1 libhal-storage1 libthunar-vfs-1 mousepad xfce4-xkb-plugin xfwm4 udev hal xfce4-session xfce4-mailwatch -plugin xfce4-mcs-manager xfce4-mcs-plugins orage xfce4-netload- plugin xfce4-taskmanager xfmedia xfce4-quicklaun cher-plugin xfce4-fsguard- plugin xfce4-utils thunar xfce4-clipman- plugin xfce4-weather- plugin xfce4-verve-plugin libcupsys2 xfprint4 xfce4-cpugraph- plugin xfdesktop4 xfce4-battery- plugin libhal-dev flex xserver-xorg alsa-utils ubuntu-minimal at ubuntu-standard abiword abiword-common abiword-plugins vbetool acpi-support libgstreamer- plugins- base0.10- 0 libnautilus- extension1 capplets-data gnome-control- center libtiff4 libtiffxx0c2 libtiff4-dev libcupsimage2 cupsys cupsys-client cupsys-bsd epiphany-browser ethereal-common ethereal evolution evolution-plugins gdb python2.4-apt python-apt gksu gdebi gstreamer0. 10-plugins- base gstreamer0.10-alsa gnome-media libpanel-applet2-0 gnome-panel-data gnome-panel gnome-power-manager gnome-session gnome-system- monitor gnome-utils gnome-volume- manager xutils gsfonts-x11 gstreamer0. 10-gnomevfs gstreamer0. 10-plugins- base-apps gstreamer0.10-x hal-device-manager hotkey-setup java-common libcupsys2-gnutls10 libglib2.0-cil libgconf2.0-cil libgtk2.0-cil libglade2.0-cil libgnome2.0-cil libgtksourcevie w-common w1.0-0 libsvn0 linux-image- 2.6.15- 22-686 linux-image-686 linux-restricte d-modules- common linux-restricte d-modules- 2.6.15- 22-686 linux-restricte d-modules- 686 linux-686 mozilla- firefox- locale- en-gb nautilus-data nautilus powernowd python2. 4-gnome2- extras python- gnome2- extras python- gnome2- extras- dev subversion tangerine- icon-theme ttf-gentium ubuntu-artwork ubuntu-base update-notifier xbase-clients x-window- system- core ubuntu-desktop unattended-upgrades valgrind dpkg/info/ linux-image- 2.6.15- 22-686. postinst configure lilo_log. 30194 2>&1 ------- ------- ------- ------- ------- ------- ------- ------- --
root 23286 4710 0 19:50 pts/0 00:00:01 apt-get dist-upgrade
root 26671 23286 0 20:17 pts/0 00:00:01 /usr/bin/dpkg --status-fd 11 --configure libx11-6 libx11-dev libxfce4util4 libxfcegui4-4 xfce4-appfinder libxfce4mcs-client3 libxfce4mcs-
libgtksourcevie
root 30194 26671 0 20:24 pts/0 00:00:00 /usr/bin/perl /var/lib/
root 32615 30194 0 20:26 pts/0 00:00:00 sh -c /sbin/lilo -t >/var/log/
root 32616 32615 0 20:26 pts/0 00:00:00 /bin/sh -e /sbin/lilo -t
root 32617 32616 0 20:26 pts/0 00:00:02 /sbin/lilo.real -t
-------
I'll attach lilo.conf, but I've not changed it for quite a while now.