Newsgroups: comp.os.linux.misc,comp.os.linux.setup
The best practice is to install lilo into Linux' own partition. Then use just fdisk to active the Linux partition. So no other 3rd party boot manangers (bootstar, system commander, etc) are required. Use lilo alone to control everything. That's enough.
The original boot sequence was: dos, linux & linuxsimple.
To change it, rearrange the order of /etc/lilo.conf then run lilo to commit the change to the boot.
Newsgroups: comp.os.linux.misc,comp.os.linux.setup
> How to put LILO in 1st sector of boot partition ?
Edit the file /etc/lilo.conf, change the line boot=/dev/hda to point to your boot partition (/dev/hda0, or whatever), then run /sbin/lilo
Markku Kolkka
Taken from the Linux/NT HOWTO (http://www.linuxdoc.org/HOWTO/mini/Linux+NT-Loader-3.html):
"… If you have a IDE-harddisk and your partition is the second partition, your boot-entry in /etc/lilo.conf looks like:
boot=/dev/hda2"
I.E. for installing on first sector, specify the disk with partition number, rather than just the disk.
Lee.
> > I think once overwritten, the bootsector cannot be recovered unless you > > got a copy > >Lilo makes just such a copy. From the lilo man page: > > -u device-name > Uninstall lilo, by copying the saved boot sector > back. A time-stamp is checked.
Additionally, if Lilo is already on the MBR, you should be able to use your boot disk (you *do* have one, don't you) to get into DOS and do an fdisk /mbr to restore the MBR. this'll work for Win9x & win2000. If Linux is screwed such that you can't load it, pop in your CD and autoboot it (if possible): you will be able to subsequently mount your root partition and then edit /etc/lilo.conf or lilo -u etc…
Lee.
>Unless you delete something first, you won't get a table like this.
then can be changed by using the partition manager included with XOSL, called Ranish partition manager…. http://www.xosl.org
Newsgroups: comp.os.linux.setup Date: Sat, 30 Nov 2002 06:09:08 +0000 (UTC)
> I tried to boot another Linux with lilo, but so far only failure, no > success. If anyone can do it, would you post your lilo.conf please? > > The Linux that I want to boot is another distro, on another > partition *and* on another disk. I've been trying to solve it again > and again, but every time all that I can do is to bang my head on > the wall...
Simplest which allows modifying the other distro without having to rerun this LILO is to put LILO for the other distro on a partition on that drive (primary or extended, not logical partition). Then you simply point your main lilo.conf to the partition with the other LILO as other just like Win95/98/ME:
other=/dev/hdb1 label=otherlinux
Another method is to mount the /boot partition or / if that is where boot is and then use the mounted path for image in lilo.conf:
Assuming mount /dev/hdb1 /mnt
image=/mnt/boot/vmlinuz label=otherlinux root=/dev/hdb1
LILO keeps track of the physical disk location of the image, so it will be able to find it while booting even though it is not mounted there during boot.
David Efflandt
> I tried to boot another Linux with lilo, but so far only failure, no > success. If anyone can do it, would you post your lilo.conf please?
It might be a bit of a bodge, but the way I do it is to put the kernels for all the linuxes into the one /boot partition with names like vmlinuz-suse. The problem is, that when you run lilo, it looks at the kernel and maps its absolute location on the disk. So trying to get lilo to use other distros requires that the other kernels also be visible. (maybe you could mount the /boot or / partition of the other distribution and specify the kernels that way)
Either way, you then just need to say
image=/boot/vmlinuz.suse root=/dev/hda<whatever>
Of course, the all in one /boot partition option means you have to manage the lilo config from a single distro. I suppose if you used Grub, you could just add any new kernels you wanted and edit grub.conf by just mounting the /boot as say, /mnt/boot, copying the files over and editing /mnt/boot/grub/menu.lst
spike1
Newsgroups: alt.linux.redhat Date: 2002-04-27 07:06:16 PST
> Boom, my Dual Boot menu disappeared! My laptop now always boot > in Win2k! I know my RH7.2 is there? How do I install back lilo ONLY!!!
There is two ways to do this
The slow way: Take your RH7.2 CD, choose to make an update, this will in the end allow you to let to reinstall the lilo. Takes a long time on a slow computer as it will really try to update your RH7.2
The fast way: Take your RH7.2 CD, choose 'linux rescue', say yes to scan/mount your system. When you get the shell prompt, type 'chroot /mnt/sysimage' (can be that the path is wrong, you find it in /mnt), when the new prompt appears, just type '/sbin/lilo', when finished, just type 'exit' and then 'exit' and all you have to do is to remove the CD and you will reboot to lilo-menu.
J.O. Aho
You will have to boot into linux with a boot (rescue) floppy.. You made one right?? ;-)
At the lilo prompt from the floopy, type root=/dev/xxxxx where xxxxx is your Linux root drive. login as root at the console, and run lilo again
That will restore lilo to the MBR on the drive. You MAY want to check /etc/lilo.conf 1st tho, and make any changes that you need to, if you changed something in the Win2k partition.
Dave Rich
> 1st : Nop. I don't have a rescue disk for Linux.....I know I should have > made > one....So, how do I make one. > > 2nd : Initially I didn't have lilo installed on the MBR. I had it installed > on /tmp/hda2 which I made as a bootable disk. So, I guess my question is > shouldn't I have to put it back there again? > > Here's the topology for my laptop. It had Win2k+Linux RH7.2!!!! > > Bootable Flag > | > V > /tmp/hda1 4GB C: Win95/FAT32 <--- Primary > /tmp/hda2 * 16MB /boot Linux <-- Primary That's where I put LILO > initially!!!!) > /tmp/hda3 20GB D: HPFS/NTFS > /tmp/hda4 4.6GB Extended > /tmp/hda5 3.8GB Linux > /tmp/hda6 787MB SWAP
I have the same problem happened to me. I had to use DOS fdisk to change the Linux partition to active. After doing that, I am now boot to Linux boot menu, which let me choose to either boot to Windows 2000 or Linux.
Lee Vang
> I have the same problem happened to me. I had to use DOS fdisk to change > the Linux partition to active. After doing that, I am now boot to Linux
Lee, Thank You!!! I did it and I am back to my dual boot!!!
>Hello. I was wondering if anyone has made some more developments with the >lilo utility, such that it shows all the boot options with the default one >highlighted. (not that i am a msft advocate, but sort of like the feel win >NT boot up menu works like)
>reason is i have several kernel configurations on the same linux-only system, >and have given them stupid names, like linux-2.2.14, linux-2.2.15, >linux-2.3.99, etc, and frequently change between them
>i am looking for something where i don't have to press tab to bring up the >list, and type in the entire boot name, but just cursor to the image name and >hit enter. (yes i am lazy, but proud of it)
I use a simple menu on several machines; it doesn't require modifying LILO or anything and I like the way it works. ` In /etc/lilo.conf: delay = 5 timeout = 50 prompt message = /etc/boot.txt ` The file /etc/boot.txt contains the menu, something like: Select Boot: 1. Slackware Linux 7.0 from /dev/hda1 (default) 2. Previous kernel for /dev/hda1 … + Back in /etc/lilo.conf, use "label = 1", "label = 2", etc. for each boot image, corresponding to the menu items.
Now, when the system boots, it displays the menu. Hit the key (on the numeric pad) and Enter to make a choice, or let it default to default to 1 after 5 seconds. (Remember to run the Lilo installer after changing either lilo.conf or the menu boot.txt)
Newsgroups: comp.os.linux.help Date: 2002-09-03 10:51:19 PST
> I've asked this question before and got answers > on how to set up a dual boot system with > two partitions....only problem is, I don't have > two partitions I have two separate hard drives,
I've just recently setup a machine to do that, and I had the same question. It turns out that two drives is handled exactly like two partitions on the same drive, except the device names are different. Like, instead of /dev/hda1 and /dev/hda2 (2 partitions on one drive), they are something like /dev/hda1 and /dev/hdb1 (2 partitions on two different drives.)
So, you can follow all the instructions for two partitions on the same drive, but just change the partition names to reflect your second drive.
(The one catch I can think of—it you want the second drive to be the drive that booting happens on, you need to mess with your BIOS to do that.)
> one with Mandrake 8.1, one with Windows ME.
I did this with NT on the first drive and RedHat on the second, but it should be similar.
Duke
Newsgroups: comp.os.linux.setup, comp.os.linux.misc Date: 2001-02-13 03:12:02 PST
> I want to be able to dual-boot my linux box.. but with a twist. > > I want to run it with two versions of RedHat. >
Simple. Your first distribution installed (lets call it A) has LILOA in mbr and boots its kernel by default. Your second distribution B, usually finds the swap and will use it, should have its LILOB on the partition, configured to boot kernelB and initialise the whole distribution. LILOA should present a menu where you can choose to activate LILOB. The stanca should look like this:
other=/dev/sdxx partition where distribution B resides unsafe read man lilo and man lilo.conf
LILOB does not need waiting period or menu selections, although a message saying "Now booting distribution B" may be nice if useless.
Stanislaw.
Newsgroups: comp.os.linux.setup Date: 2002-05-19 10:18:02 PST
I have to win98 partitions. THey need to be hidden from each other. I can't get lilo to hide them though.
I can't get the partitions to activate and deactivate. I've looked for samples on how to hid and unhide partitions. i have the rewrite_tables on. Here's my lilo.conf. I get no errors when running lilo. I don't know what else I can do.
lba32
root=/dev/hda5
compact
install=/boot/boot-bmp.b bitmap=/boot/prison.bmp bmp-colors=0,1,3,1,2,3
map=/boot/map
prompt delay=100 timeout=200
vga=normal default=Linux2.4.18
image=/boot/vmlinuz-2.4.18
label=Linux2.4.18
read-only
image=/vmlinuz
label=Linux2.4.16
read-only
other=/dev/hda4
table=/dev/hda
label=Win98.whatevs
change
partition=/dev/hda1
deactivate
set=DOS16_big_hidden
partition=/dev/hda4
activate
set=DOS16_big_normal
other=/dev/hda1
table=/dev/hda
label=Guest
change
partition=/dev/hda1
activate
set=DOS16_big_normal
partition=/dev/hda4
deactivate
set=DOS16_big_hidden
Go here and get what you need…. http://www.xosl.org/
-red-
> I have to win98 partitions. THey need to be hidden from each other. I can't > get lilo to hide them though.
You should be able to do that with LILO. However, you might want to look at Air-Boot (has hide/unhide functions built in) at…
The features:
Colored Boot-Menu
Completly integrated, Award-styled, menu-driven SETUP including real help to every option
Very easy Installation/Repair via disc or CD-ROM
Localized to English/Dutch/German/French
Boot-Process completly configurable
Configurable Password protection
100% in MBR (does not need any real space on harddisc)
"Corrupt-MBR"-Protection (is able to restore MBR, if it gets corrupted)
Intelligent Partition Handling. Will not reset or act abnormal, if partitions are moved, changed, etc.
Hiding partitions support
Floppy-Boot
Finds (Stealth-)MBR and Bootrecord-Virii (and is able to remove most of them)
Repair-Mode, AiR-BOOT disc/CD-ROM is able to repair AiR-BOOT without resetting the configuration
MBR-Protection under Real-Mode
OS/2 LVM-aware
OS/2 Select-Your-Favourite-Boot-Letter-Feature
Linux Kernel Support (from FAT16-partition)
Includes Linux Boot-Commandline and automagically, but configurable root-partition
Ron Gibson ix.netcom.com
Newsgroups: comp.os.linux.setup > I'm trying to load Lilo on the > MBR of a partition that begins < 1024 but ends >.
get the new lilo from www.freshmeat.net It can handle partitions bigger than 1024.
> /dev/hda4 1405 2343 Extended
Another thing: To avoid trouble with Windows 95/98 you should change the ID of the extended partition from 05 to 0F (LBA extended), or better since you have only Linux partitions in the extended partition, change ID 05 to 85 (Linux extended).
This can be done using Linux fdisk. For some reason the ID is not in your output, but since the description is "Extended", the current ID (type) may be 05.
Svend Olaf