Short version of my problem:
debian:/home/jkfisher# lilo Fatal: open /initrd.img: No such file or directory
How do I make one?
Now, for the long version, in case that isn't enough...
Long Version:
I used apt-get (actually wajig, but who's counting?) to update, which I've done many times before, but for the first time I've seen, LILO is throwing an error, and I'm afraid to restart, in case the comp doesn't come back up.
Preparing to replace kernel-image-2.6.8-1-686 2.6.8-5 (using .../kernel-image-2.6.8-1-686_2.6.8-9_i386.deb) ...
The directory /lib/modules/2.6.8-1-686 still exists. Continuing as directed.
Unpacking replacement kernel-image-2.6.8-1-686 ...
The link /initrd.img is a dangling link
Removing symbolic link /initrd.img
Unless you used the optional flag in lilo, you may need to re-run lilo
...
Setting up kernel-image-2.6.8-1-686 (2.6.8-9) ...
You are attempting to install a kernel version that is the same as
the version you are currently running (version 2.6.8-1-686). The modules
list is quite likely to have been changed, and the modules dependency
file /lib/modules/2.6.8-1-686/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.
Please Hit return to continue. Not touching initrd symlinks since we are being reinstalled (2.6.8-5) Not updating image symbolic links since we are being updated (2.6.8-5) A new kernel image has been installed, and usually that means that some action has to be taken to make sure that the new kernel image is used next time the machine boots. Usually, this entails running a ``bootloader'' like SILO, loadlin, LILO, ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy. (Some boot loader, like grub, for example, do not need to be run on each new image install, so please ignore this if you are using such a boot loader).
A new kernel image has been installed at /boot/vmlinuz-2.6.8-1-686 (Size: 1136kB)
Initial rootdisk image: /boot/initrd.img-2.6.8-1-686 (Size: 4540kB)
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 ... An error occurred while running lilo in test mode, a log is available in /var/log/lilo_log.17311. Please edit /etc/lilo.conf manually and re-run lilo, or make other arrangements to boot your machine. Please hit return to continue
...
debian:/home/jkfisher# cat /var/log/lilo_log.17311 Fatal: open /initrd.img: No such file or directory
debian:/home/jkfisher# lilo Fatal: open /initrd.img: No such file or directory
Thanks in advance.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
