Results 1 to 6 of 6

Thread: Different LILO versions

  1. #1
    Senior Member
    Join Date
    Apr 2004
    Location
    Indiana?... We named the dog Indiana!
    Posts
    488

    Different LILO versions

    I know that we have a few Grub fans on the site, and after all this time I really should've had this figured out by now; but I'm trying to make LILO work, once and for all (no boot discs... Straight from the HD).

    A little history:

    It's a laptop with Windows, Knoppix, and VectorSOHO installed. All installs went well, except for getting the bootloader to recognize both Linux's... Only the Knoppix LILO installed on the MBR is working to boot WinXP and the various Knoppix kernels; the Vector LILO is installed on its own root partition.

    What's tripping me up is that there appears to be a different LILO verison for each Linux distro:

    Knoppix LILO.conf:
    Code:
    # /etc/lilo.conf - See: 'lilo(8)' and 'lilo.conf(5)', 
    # ---------------       'install-mbr(8)', '/usr/share/doc/lilo/', 
    #                       and '/usr/share/doc/mbr/'. 
      
    # +---------------------------------------------------------------+ 
    # |                        !! Reminder !!                         | 
    # |                                                               | 
    # | Don't forget to run 'lilo' after you make changes to this     | 
    # | conffile, '/boot/bootmess.txt', or install a new kernel.  The | 
    # | computer will most likely fail to boot if a kernel-image      | 
    # | post-install script or you don't remember to run 'lilo'.      | 
    # |                                                               | 
    # +---------------------------------------------------------------+ 
      
    # 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/hda2 
      
    # 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 
      
    # Default menu for Debian. (Using the images from debian-bootscreen) 
    # from Philipp Wolfer <phil@newswriter.org>. 
    bitmap=/usr/share/lilo/debianlilo.bmp 
    bmp-colors=1,,0,2,,0 
    bmp-table=120p,173p,1,15,17 
    bmp-timer=254p,432p,1,0,0 
      
    # Install the specified file as the new boot sector. 
    # LILO supports built in boot sectory, you only need 
    # to specify the type, choose one from 'text', 'menu' or 'bitmap'. 
    # new&#58; install=bmp      old&#58; install=/boot/boot-bmp.b 
    # new&#58; install=text     old&#58; install=/boot/boot-text.b 
    # new&#58; install=menu     old&#58; install=/boot/boot-menu.b or boot.b 
    # default&#58; 'menu' is default, unless you have a bitmap= line 
    # Note&#58; install=bmp must be used to see the bitmap menu. 
    # install=menu 
    # install=bmp 
    install=bmp 
      
    # Specifies the number of _tenths_ of a second LILO should 
    # wait before booting the first image.  LILO 
    # doesn't wait if DELAY is omitted or if DELAY is set to zero. 
      
    delay=20 
      
    # Prompt to use certaing image. If prompt is specified without timeout, 
    # boot will not take place unless you hit RETURN 
    prompt 
    timeout=50 
      
    # Specifies the location of the map file. If MAP is 
    # omitted, a file /boot/map is used. 
    map=/boot/map 
      
    # Specifies the VGA text mode that should be selected when 
    # booting. The following values are recognized &#40;case is ignored&#41;&#58; 
    #   NORMAL  select normal 80x25 text mode. 
    #   EXTENDED  select 80x50 text mode. The word EXTENDED can be 
    #     abbreviated to EXT. 
    #   ASK  stop and ask for user input &#40;at boot time&#41;. 
    #   <number>  use the corresponding text mode. A list of available 
    modes 
    #     can be obtained by booting with  vga=ask  and pressing &#91;Enter&#93;. 
    vga=791 
      
    # You can set a password here, and uncomment the 'restricted' lines 
    # in the image definitions below to make it so that a password must 
    # be typed to boot anything but a default configuration.  If a 
    # command line is given, other than one specified by an 'append' 
    # statement in 'lilo.conf', the password will be required, but a 
    # standard default boot will not require one. 
    # 
    # This will, for instance, prevent anyone with access to the 
    # console from booting with something like 'Linux init=/bin/sh', 
    # and thus becoming 'root' without proper authorization. 
    # 
    # Note that if you really need this type of security, you will 
    # likely also want to use 'install-mbr' to reconfigure the MBR 
    # program, as well as set up your BIOS to disallow booting from 
    # removable disk or CD-ROM, then put a password on getting into the 
    # BIOS configuration as well.  Please RTFM 'install-mbr&#40;8&#41;'. 
    # 
    # password=tatercounter2000 
      
    # You can put a customized boot message up if you like.  If you use 
    # 'prompt', and this computer may need to reboot unattended, you 
    # must specify a 'timeout', or it will sit there forever waiting 
    # for a keypress.  'single-key' goes with the 'alias' lines in the 
    # 'image' configurations below.  eg&#58; You can press '1' to boot 
    # 'Linux', '2' to boot 'LinuxOLD', if you uncomment the 'alias'. 
    # 
    # message=/boot/bootmess.txt 
    #       prompt 
    #       single-key 
    #       delay=100 
    #       timeout=100 
      
    # Kernel command line options that apply to all installed images go 
    # here.  See&#58; The 'boot-prompt-HOWO' and 'kernel-parameters.txt' in 
    # the Linux kernel 'Documentation' directory. 
    # 
    # append="" 
    # Boot up Linux by default. 
    # 
    default="Linux" 
      
    image=/boot/vmlinuz 
            label="Linux" 
            initrd=/boot/initrd.img 
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off 
    nomce" 
            read-only 
    image=/boot/vmlinuz-2.4.27 
            label="Linux&#40;2.4&#41;-1" 
            initrd=/boot/initrd.img-2.4.27 
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off 
    nomce" 
            read-only 
              
    image=/boot/vmlinuz-2.6.7 
            label="Linux&#40;2.6&#41;-2" 
            initrd=/boot/initrd.img-2.6.7 
            append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off 
    nomce" 
            read-only 
              
    # If you have another OS on this machine to boot, you can uncomment the 
    # following lines, changing the device name on the 'other' line to 
    # where your other OS' partition is. 
    # 
    # other=/dev/hda4 
    #       label=HURD 
    #       restricted 
    #       alias=3 
    other=/dev/hda1 
            label="WinXP/2K&#40;hda1&#41;"
    Vector LILO.conf:
    Code:
    # LILO configuration file 
    # generated by 'liloconfig' 
    # 
    # Start LILO global section 
    boot = /dev/hda 
    append = "hdc=ide-scsi" 
    message = /boot/boot_message.txt 
    prompt 
    timeout = 1200 
    # Override dangerous defaults that rewrite the partition table&#58; 
    change-rules 
    reset 
    # VESA framebuffer console @ 1024x768x256 
    vga = 773 
    # Normal VGA console 
    # vga = normal 
    # VESA framebuffer console @ 1024x768x64k 
    # vga=791 
    # VESA framebuffer console @ 1024x768x32k 
    # vga=790 
    # VESA framebuffer console @ 1024x768x256 
    # vga=773 
    # VESA framebuffer console @ 800x600x64k 
    # vga=788 
    # VESA framebuffer console @ 800x600x32k 
    # vga=787 
    # VESA framebuffer console @ 800x600x256 
    # vga=771 
    # VESA framebuffer console @ 640x480x64k 
    # vga=785 
    # VESA framebuffer console @ 640x480x32k 
    # vga=784 
    # VESA framebuffer console @ 640x480x256 
    # vga=769 
    # End LILO global section 
    # DOS bootable partition config begins 
    other = /dev/hda1 
    label = DOS 
    table = /dev/hda 
    # DOS bootable partition config ends 
    # Linux bootable partition config begins 
    image = /boot/vmlinuz 
    root = /dev/hda3 
    label = Linux 
    read-only 
    # Linux bootable partition config ends 
    # OS/2 bootable partition config begins 
    other = /dev/hda1 
    label = OS2 
    table = /dev/hda 
    # OS/2 bootable partition config ends Vector lilo.conf
    As you can see; there are lines that specify:


    image=
    root=
    label=
    read-only


    in the Vector LILO.conf, but there's a different conbination specified in the Knoppix LILO.conf:


    image=
    label=
    initrd=
    append=
    read-only


    Ultimately, I'd like to get the required parameters from the Vector LILO into the Knoppix LILO. How can I do that, when the parameter listings aren't the same? Am I thinking about this the wrong way, or what? Any help is very appeciated. TIA.
    Steve

  2. #2
    Senior Member
    Join Date
    Apr 2004
    Location
    Indiana?... We named the dog Indiana!
    Posts
    488
    Ok... I installed Grub instead, but I still can't get VectorSOHO to boot. I edited the Windows and Vector sections myself, but it won't boot the Vector partition (/dev/hda3) :

    Code:
    # menu.lst - See&#58; grub&#40;8&#41;, info grub, update-grub&#40;8&#41; 
    #            grub-install&#40;8&#41;, grub-floppy&#40;8&#41;, 
    #            grub-md5-crypt, /usr/share/doc/grub 
    #            and /usr/share/doc/grub-doc/. 
    
    ## default num 
    # Set the default entry to the entry number NUM. Numbering starts from 0, and 
    # the entry number 0 is the default if the command is not used. 
    # 
    # You can specify 'saved' instead of a number. In this case, the default entry 
    # is the entry saved with the command 'savedefault'.            
    default      0 
    
    ## timeout sec 
    # Set a timeout, in SEC seconds, before automatically booting the default entry 
    # &#40;normally the first entry defined&#41;. 
    timeout      3600 
    
    # Pretty colours 
    color cyan/blue white/blue 
    
    ## password &#91;'--md5'&#93; passwd 
    # If used in the first section of a menu file, disable all interactive editing 
    # control &#40;menu entry editor and command-line&#41;  and entries protected by the 
    # command 'lock' 
    # e.g. password topsecret 
    #      password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/ 
    # password topsecret 
    
    # 
    # examples 
    # 
    title      Windows XP 
    root      &#40;hd0,0&#41; 
    makeactive 
    chainloader   +1 
    # 
    title      Vector SOHO Linux 
    root      &#40;hd0,3&#41; 
    kernel   /vmlinuz root=/dev/hda3 ro 
    # 
    
    # 
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST 
    
    ### BEGIN AUTOMAGIC KERNELS LIST 
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified 
    ## by the debian update-grub script except for the default optons below 
    
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs 
    
    ## ## Start Default Options ## 
    ## default kernel options 
    ## default kernel options for automagic boot options 
    ## If you want special options for specifiv kernels use kopt_x_y_z 
    ## where x.y.z is kernel version. Minor versions can be omitted. 
    ## e.g. kopt=root=/dev/hda1 ro 
    # kopt=root=/dev/hda2 ro 
    
    ## default grub root device 
    ## e.g. groot=&#40;hd0,0&#41; 
    # groot=&#40;hd0,1&#41; 
    
    ## should update-grub create alternative automagic boot options 
    ## e.g. alternative=true 
    ##      alternative=false 
    # alternative=true 
    
    ## should update-grub lock alternative automagic boot options 
    ## e.g. lockalternative=true 
    ##      lockalternative=false 
    # lockalternative=false 
    
    ## altoption boot targets option 
    ## multiple altoptions lines are allowed 
    ## e.g. altoptions=&#40;extra menu suffix&#41; extra boot options 
    ##      altoptions=&#40;recovery mode&#41; single 
    # altoptions=&#40;recovery mode&#41; single 
    
    ## controls how many kernels should be put into the menu.lst 
    ## only counts the first occurence of a kernel, not the 
    ## alternative kernel options 
    ## e.g. howmany=all 
    ##      howmany=7 
    # howmany=all 
    
    ## ## End Default Options ## 
    
    title      Debian GNU/Linux, kernel  
    root      &#40;hd0,1&#41; 
    kernel      /boot/vmlinuz root=/dev/hda2 ro 
    initrd      /boot/initrd.img 
    savedefault 
    boot 
    
    title      Debian GNU/Linux, kernel  &#40;recovery mode&#41; 
    root      &#40;hd0,1&#41; 
    kernel      /boot/vmlinuz root=/dev/hda2 ro single 
    initrd      /boot/initrd.img 
    savedefault 
    boot 
    
    title      Debian GNU/Linux, kernel 2.6.7 
    root      &#40;hd0,1&#41; 
    kernel      /boot/vmlinuz-2.6.7 root=/dev/hda2 ro 
    initrd      /boot/initrd.img-2.6.7 
    savedefault 
    boot 
    
    title      Debian GNU/Linux, kernel 2.6.7 &#40;recovery mode&#41; 
    root      &#40;hd0,1&#41; 
    kernel      /boot/vmlinuz-2.6.7 root=/dev/hda2 ro single 
    initrd      /boot/initrd.img-2.6.7 
    savedefault 
    boot 
    
    title      Debian GNU/Linux, kernel 2.4.27 
    root      &#40;hd0,1&#41; 
    kernel      /boot/vmlinuz-2.4.27 root=/dev/hda2 ro 
    initrd      /boot/initrd.img-2.4.27 
    savedefault 
    boot 
    
    title      Debian GNU/Linux, kernel 2.4.27 &#40;recovery mode&#41; 
    root      &#40;hd0,1&#41; 
    kernel      /boot/vmlinuz-2.4.27 root=/dev/hda2 ro single 
    initrd      /boot/initrd.img-2.4.27 
    savedefault 
    boot 
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    I noticed the initrd lines for the other Linux entries (the ones that are working), but I booted Vector with the CD and checked the /boot directory... Seeing as Vector is a Slackware (BSD) distro, there is no initrd file in that directory. Any ideas?
    Steve

  3. #3
    Member
    Join Date
    Apr 2004
    Location
    Eugene, Oregon
    Posts
    207
    Normally, you don't have to have an initrd entry at all. You just need the title, root, and kernel parameters in /boot/grub/menu.list in order to boot a *nix operating system. Here's the end of mine:

    title linux
    root (hd0,1)
    kernel /boot/kernel_9-22-2004 root=/dev/hda2 ro acpi=force
    boot

    ### END DEBIAN AUTOMAGIC KERNELS LIST

    title windows
    rootnoverify (hd0,0)
    makeactive
    chainloader +1



    One thing I'd suggest is to scan the grub info page. When I was setting up dual boot with Windows for the first time (I had a weird partition setup on my old computer) a few years ago that really helped.

  4. #4
    Senior Member
    Join Date
    Apr 2004
    Location
    Indiana?... We named the dog Indiana!
    Posts
    488
    Thanks for the reply kungfu. I found this at the LDP, and will do some reading tonight.
    Steve

  5. #5
    Senior Member
    Join Date
    Apr 2004
    Location
    Indiana?... We named the dog Indiana!
    Posts
    488
    Ok... Got it all working now :mrgreen: .

    Kungfu's root line is what set me straight. It's referring to the device, not the partition (which the kernel line takes care of on its own, donchaknow ) .

    I'm stylin' on a pure-from-the-HD-triple-boot. :w00t:
    Steve

  6. #6
    Member
    Join Date
    Apr 2004
    Location
    Eugene, Oregon
    Posts
    207
    Sweet! Glad that worked! Happy triple booting! :mrgreen:

Similar Threads

  1. [Solved!] Linux versions
    By boshra in forum Redhat / Fedora
    Replies: 1
    Last Post: 05-05-2009, 10:18 AM
  2. New distro versions
    By cloverm in forum Linux - General Topics
    Replies: 17
    Last Post: 11-07-2002, 01:01 AM
  3. Which versions of g++ and gcc are better?
    By jmcook in forum Linux - Software, Applications & Programming
    Replies: 10
    Last Post: 10-02-2002, 03:20 AM
  4. So what are the different versions of linux?
    By iansl in forum Linux - General Topics
    Replies: 1
    Last Post: 05-14-2002, 04:09 AM
  5. Does anyone like the new versions of the imac?
    By noblestknight in forum Linux Distros
    Replies: 18
    Last Post: 02-27-2002, 03:07 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
  •