On Fri, Sep 28, 2001 at 08:04:03AM -0400, Chapman, Matt wrote: > Hi, > > I have made an attempt at doing a apt-get install kernel-image-2.4.9-686 > This is on a DELL PowerEdge 1400 > > It downloads just fine and starts the install. It then gives me this: > > The following NEW packages will be installed: > kernel-image-2.4.9-686 > 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. > 4 packages not fully installed or removed. > Need to get 0B/7919kB of archives. After unpacking 22.0MB will be used. > debconf: (not preconfiguring packages since apt-utils is not installed) > (Reading database ... 11164 files and directories currently installed.) > Unpacking kernel-image-2.4.9-686 (from .../ > kernel-image-2.4.9-686_2.4.9-1_i386.d > eb) ... > > You are attempting to install an initrd kernel image (version 2.4.9-686) > This will not work unless you have configured your boot loader to use > initrd. > As a reminder, in order to configure lilo, you need to > add an 'initrd=/boot/initrd' in your /etc/lilo.conf > To get rid of this message, put `do_initrd = Yes' in /etc/kernel-img.conf. > Do you want to stop now? [Y/n] > > > Is this as easy as it seems simply putting initrd=/boot/initrd in the lilo.conf Actually, yes, if you're running LILO and not grub or some other bootloader. However, /boot/initrd is a symlink, and I personally don't use them in my lilo.conf. Here's what my config looks like for kernel 2.4.9: image=/boot/vmlinuz-2.4.9-686 label=2.4.9-686 initrd=/boot/initrd-2.4.9-686 read-only # useful if your root filesystem is ext2 > > Also I do not have an /etc/kernel-img.conf Neither do I; in any case, the system works just fine without it. HTH, -- Mike Alborn <malborn@odoitau.dyn.dhs.org> # pgp keyid: C36DC30D He who hates vices hates mankind.
Attachment:
pgp4GQRzfe8ZF.pgp
Description: PGP signature