Results 1 to 1 of 1
Hello. Thanks in advance for any help provided. hda has win2k (hda1) and VectorLinux (hda2-/, hda5-swap, hda6-/home) installed, using lilo to boot. It all works properly (kernel 2.4.xx). I decided ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 03-29-2005 #1
- Join Date
- Mar 2005
Dual-boot with 2 hard drives
hda has win2k (hda1) and VectorLinux (hda2-/, hda5-swap, hda6-/home) installed, using lilo to boot. It all works properly (kernel 2.4.xx).
I decided to try Arch on hdb1-/, hdb2-/home (reuse hda5-swap; kernel 2.6.xx) skipping the lilo install since I already had a working lilo. I installed the "base", and rebooted to Vector to add the proper info for Arch to lilo.conf. I added what *I thought* would be correct, but it didn't work....
So then I decided to redo the Arch install, and wanted to install lilo to the hdb-mbr at the end of install. Didn't work; ended up putting lilo on hda-mbr. I tried adding the correct info for Vector this time, and it didn't work....
Also, the two lilos (vector vs arch) use different drive location information within lilo.conf (i.e. /dev/hda2 vs /dev/discs/disc0/part2, respectively).
Here's my current lilo which is only booting Arch (hdb1) and Win2k (hda1):
# # /etc/lilo.conf # boot=/dev/discs/disc0/disc # This line often fixes L40 errors on bootup # disk=/dev/discs/disc0/disc bios=0x80 default=arch timeout=50 lba32 prompt image=/boot/vmlinuz26 label=arch root=/dev/discs/disc1/part1 read-only #image=/boot/vmlinuz # root=/dev/hda2 # label=vector # read-only other=/dev/hda1 label=win2k table=/dev/hda