Professional Web Applications Themes

aptitude and /etc/lilo.conf - Debian

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 ...

  1. #1

    Default aptitude and /etc/lilo.conf

    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]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    J F Guest

  2. #2

    Default Re: aptitude and /etc/lilo.conf

    On Mon, Jul 28, 2003 at 06:42:47PM -0700, J F wrote:
    > Based on the output from aptitude and my current
    > lilo.conf, do you think I need to do anything to lilo.conf?
    aptitude is just a frontend. dpkg is doing the actual work of unpacking
    and installing the package.
    > Is aptitude going to put the new kernel
    > in /boot?
    dpkg will, yes.
    > Will aptitude fix the link /vmlinuz ?
    dpkg will. yes.
    > 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]
    > >
    > default=Linux
    > image=/boot/vmlinuz-2.4.20-xfs
    > label=Linux
    > initrd=/boot/initrd.gz
    > read-only
    > # restricted
    > # alias=1
    The kernel image will be unpacked into /boot as
    vmlinuz-<kernel-version>, and a symlink called /vmlinuz will be created
    pointing to it. This was in the default lilo.conf, but you deleted it.
    You'll need to recreate a stanza along the lines of:

    image=/vmlinuz
    label=debian-kernel
    initrd=/initrd.img
    read-only

    For kernels from kernel-image packages to work. You won't need to
    modify it again, though. You might want to make it the default.
    > # 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
    Oh, you have that link? Why did you modify your lilo.conf, then?

    --
    Rob Weir <rweirertius.org> | [email]mlspamertius.org[/email] | Do I look like I want aCC?
    Words of the day: argus Project Monarch csystems eavesdropping AUTODIN hackers

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.2 (GNU/Linux)

    iD8DBQE/K09uvQ+DhR5zt80RAsFIAJwLKqRMfAO0WIuTiAJEAI48Aioofw CfdG/7
    cv13ObzBG6fgGVI3BCoCtYA=
    =0ghx
    -----END PGP SIGNATURE-----

    Rob Weir Guest

  3. #3

    Default Re: aptitude and /etc/lilo.conf

    J F wrote:
    > Rob Weir wrote:
    >
    >> On Mon, Jul 28, 2003 at 06:42:47PM -0700, J F wrote:
    >>
    >>> Based on the output from aptitude and my current
    >>> lilo.conf, do you think I need to do anything to lilo.conf?
    >>
    >>
    >> aptitude is just a frontend. dpkg is doing the actual work of unpacking
    >> and installing the package.
    >>
    >>
    >>> Is aptitude going to put the new kernel
    >>> in /boot?
    >>
    >>
    >> dpkg will, yes.
    >>
    >>
    >>> Will aptitude fix the link /vmlinuz ?
    >>
    >>
    >> dpkg will. yes.
    >>
    >>
    >>> 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]
    >>>>
    >>>
    >>> default=Linux
    >>> image=/boot/vmlinuz-2.4.20-xfs
    >>> label=Linux
    >>> initrd=/boot/initrd.gz
    >>> read-only
    >>> # restricted
    >>> # alias=1
    >>
    >>
    >>
    >> The kernel image will be unpacked into /boot as
    >> vmlinuz-<kernel-version>, and a symlink called /vmlinuz will be created
    >> pointing to it. This was in the default lilo.conf, but you deleted it.
    >> You'll need to recreate a stanza along the lines of:
    >>
    >> image=/vmlinuz
    >> label=debian-kernel
    >> initrd=/initrd.img
    >> read-only
    >>
    >> For kernels from kernel-image packages to work. You won't need to
    >> modify it again, though. You might want to make it the default.
    >>
    >>
    >>> # 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
    >>
    >>
    >>
    >> Oh, you have that link? Why did you modify your lilo.conf, then?
    >
    >
    > Thanks for answering. I was beginning to think I would not
    > get an answer to that question.
    > I didn't modify lilo.conf or the /vmlinuz links.
    > I can only assume that either this is the default from the knoppix
    > hard disk install or it got downloaded when I did an apt-get upgrade.
    >
    > Thanks again,
    > I'll try to add that stanza and then lilo to get past this upgrade issue.
    > J F
    Your suggestion worked:

    roota1700xp:/etc# diff lilo.conf.orig lilo.conf
    1c1
    < vga=791
    ---
    > #vga=791
    107c107
    < image=/boot/vmlinuz-2.4.20-xfs
    ---
    > image=/vmlinuz
    109c109
    < initrd=/boot/initrd.gz
    ---
    > initrd=/initrd.img
    113a114,120
    > image=/boot/vmlinuz-2.4.20-xfs
    > label=L2.4.20x
    > initrd=/boot/initrd.gz
    > read-only
    > # restricted
    > # alias=2
    >
    119c126
    < # alias=2
    ---
    > # alias=3
    128c135
    < # alias=3
    ---
    > # alias=4
    The diff doesn't show it clearly but
    maybe this is clearer:
    default=Linux

    image=/vmlinuz
    label=Linux
    initrd=/initrd.img
    read-only
    # restricted
    # alias=1

    And make sure these links are here:
    # ls -l /v*
    lrwxrwxrwx 1 root root 25 Aug 3 12:32 /vmlinuz -> boot/vmlinuz-2.4.20-3-386
    lrwxrwxrwx 1 root root 23 May 21 12:23 /vmlinuz.old -> boot/vmlinuz-2.4.20-xfs
    ....

    Thanks to Rob Weir.


    --
    To UNSUBSCRIBE, email to [email]debian-user-requestlists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmasterlists.debian.org[/email]
    J F Guest

Similar Threads

  1. Bake grub.conf into MBR (like lilo)
    By Bill in forum Linux Setup, Configuration & Administration
    Replies: 3
    Last Post: August 15th, 01:53 PM
  2. Lilo Problems
    By Jefferson Cowart in forum Debian
    Replies: 7
    Last Post: August 12th, 05:10 AM
  3. aptitude upgrade - I don't want a select package(s)
    By Rodney D. Myers in forum Debian
    Replies: 2
    Last Post: August 5th, 10:30 AM
  4. running aptitude and apt-get from cron
    By Colin Watson in forum Debian
    Replies: 1
    Last Post: July 7th, 10:10 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139