Based on the output from aptitude and my current
lilo.conf, do you think I need to do anything to lilo.conf?
Is aptitude going to put the new kernel
in /boot?
Will aptitude fix the link /vmlinuz ?
I ran aptitude and it did a lot of things and then said:

aptitude wrote:
Unpacking kernel-image-2.4.20-3-386 (from .../kernel-image-2.4.20-3-386_2.4.20-9_i386.deb) ...

You are attempting to install an initrd kernel image (version 2.4.20-3-386)
This will not work unless you have configured your boot loader to use
initrd. (An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting).
As a reminder, in order to configure lilo, you need to
add an 'initrd=/initrd.img' to the image=/vmlinuz
stanza of your /etc/lilo.conf
I repeat, You need to configure your boot loader. If you have already done
so, and you wish to get rid of this message, please put
  `do_initrd = Yes'
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
you'll continue to see this message whenever you install a kernel
image using initrd.
Do you want to stop now? [Y/n]


# more /etc/lilo.conf vga=791 # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt', or install a new kernel. The | # Support LBA for large hard disks. # lba32 # Overrides the default mapping between harddisk names and the BIOS' # harddisk order. Use with caution. #disk=/dev/hde # bios=0x81 #disk=/dev/sda # bios=0x80 # Specifies the boot device. This is where Lilo installs its boot # block. It can be either a partition, or the raw device, in which # case it installs in the MBR, and will overwrite the current MBR. # boot=/dev/hda # Specifies the device that should be mounted as root. (`/') # root=/dev/hda3 # Enable map compaction: # Tries to merge read requests for adjacent sectors into a single # read request. This drastically reduces load time and keeps the # map smaller. Using `compact' is especially recommended when # booting from a floppy disk. It is disabled here by default # because it doesn't always work. # # compact # Installs the specified file as the new boot sector # You have the choice between: bmp, compat, menu and text # Look in /boot/ and in lilo.conf(5) manpage for details # install=/boot/boot-menu.b # Specifies the location of the map file # map=/boot/map delay=20 # message=/boot/bootmess.txt prompt timeout=150 # prompt # single-key # delay=100 # timeout=100 # append="" append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce" default=Linux image=/boot/vmlinuz-2.4.20-xfs label=Linux initrd=/boot/initrd.gz read-only # restricted # alias=1 image=/vmlinuz.old label=LinuxOLD read-only optional # restricted # alias=2 # If you have another OS on this machine to boot, you can uncomment the # following lines, ... # other=/dev/hda4 # label=HURD # restricted # alias=3 other=/dev/hda1 label="Windows(hda1)"

ls -a /boot
. .. System.map System.map-2.4.20-xfs boot.0300 config-2.4.20-xfs initrd.gz map vmlinuz vmlinuz-2.4.20-xfs


# ls -ld /v*
drwxr-xr-x   16 root     root         4096 Jan 18  2003 /var
lrwxrwxrwx    1 root     root           23 May 21 12:23 /vmlinuz -> 
boot/vmlinuz-2.4.20-xfs



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




Reply via email to