-=[ ED'S LILO CONFIGURATION HELP FILE ]=- www.narced.com/linux Below is how to set up lilo for a computer with dos/win, 2 versions of linux, and Solaris. If you use this, be sure to delete all comments with the arrows ( <-- ). # LILO configuration file # Based loosely on Slackware's liloconfig # # Start LILO global section boot = /dev/hda <-- the drive you want to boot from message=/boot/message <-- the message to display at bootup #prompt #compact # faster, but won't work on all systems. delay = 50 <-- wait 5 seconds, then boot 1st entry vga = normal # force sane state # ramdisk = 0 # paranoia setting # End LILO global section # DOS bootable partition config begins other = /dev/hda1 <-- location of OS label = win95 <-- what you'll have to type to boot to it table = /dev/hda # DOS bootable partition config ends # Linux bootable partition config begins image = /boot/vmlinuz <-- location of linux kernel root = /dev/hda2 <-- drive linux is installed on label = linux <-- what you'll have to type to boot to it read-only # Non-UMSDOS filesystems should be mounted read-only for checking # Linux bootable partition config ends # Caldera bootable partition config begins image = /boot/vmlinuz <-- another linux root = /dev/hda4 <-- installed on another partition label = caldera <-- what you'll have to type to boot to it read-only # Non-UMSDOS filesystems should be mounted read-only for checking # Caldera bootable partition config ends # Boot Solaris here... other = /dev/hdb1 <-- drive it's on label = solaris <-- what you'll have to type to boot to it loader = /boot/chain.b unsafe # End of Solaris # End of /etc/lilo.conf Notes: The first line specifies where lilo should be installed to. To install to a floppy disk, make it say: boot = /dev/fd0 Otherwise, it is best to leave it as /dev/hda. The message line (message=/boot/message) simply specifies what text file to display after the "LILO" prompt. This is optional. The delay line can be set to any time you want (seems like 10 = 1 second). Mine is set to a 5 second wait before automatically booting into the first OS on the list (in this case, Windows 95). You can comment this line out if you want LILO to wait forever. If you have 2 different versions of linux with different kernels on the same physical drive, you will end up using the same kernel for booting up. Seems like lilo write part or all of the kernel somewhere on the MBR maybe. I have had different versions of linux boot different kernels when they were installed on separate drives. I also think is is possible to have 1 version of linux with multiple kernels (obviously, you'd only boot 1 of them). This can be tricky because you can run into trouble with the following files: /boot/System.map /boot/boot.b /boot/chain.b However, I saw in a magazine article that all you have to do is name the alternate kernel something else. For example: /boot/vmlinuz-2.2.10 /boot/vmlinuz-old Then, you just set up LILO like above but on the same partition. Be sure to run 'lilo' after making any changes so that your changes take effect!!