According to Doin' the Bull Dance, Feelin' the Flow...: While burning my CPU.
>
> I just installed slackware 3.4 on my friend's computer...he has a 2nd HD
> that we put it on that should show up as hdc. His CD ROM shows up as hdb.
> We thought that was all fine and dandy.
>
> Well, I had put it onto the master boot record instead of like a superblock
> on the linux native partition. for some reason, even though his original HD
> was never booted, looked at, read or anything, it put LILO on the C: drive.
> We discovered the problem and fixed it by using a boot disk for now, and
> then we'll just put it on the linux native partition.
>
> So, my question is really one out of curiosity more than anything else. Why
> on earth did it do that????
Wierdness, i dont think its lilo being wierd, it sounds perfectly normal to
me, when installed on the MBR it installs itself as "THE" boot loader which
HAS to be on the first drive, in this case C:\
However the thing which makes it look wierd is the fact that slackware is a
little dubious on this point, its very esay to think lilo has been installed
when if fact you forgot to tell lilo to edit /etc/lilo.conf to point itself
to /dev/hdc to boot.
After booting with your bootdisk you can install lilo "after editing"
/etc/lilo.conf to something like the following.
boot=/dev/hdc
map=/boot/map
install=/boot/boot.b
prompt
timeout=300
# define which kernel to boot, up to 30 different entrys allowed.
image=/boot/vmlinuz-2.0.35
label=36
root=/dev/hdc1
read-only
other=/dev/hda1
label=dos
table=/dev/hda
The image= looks for the kernel image on /dev/hdc1 /boot/vmlinuz-2.0.35
to boot this kernel at bootime, at the LILO prompt, hit ALT then TAB keys,
you will then get a list of bootable kernels, type in 36 linux should now
start.
Or just wait for 30 seconds ("timeout=" is in 10th's of a second) lilo will
then boot "26" automaticly.
To boot dos after hitting the keys as above, just type dos.
To install lilo after editing /etc/lilo.conf just type lilo, you should see
a return of;
adding 36 *
adding dos
The * means default boot entry, the first entry in /etc/lilo.conf.
There are some draw backs to having Linux on the 3rd drive and possably
leading to the system not booting, the following is from
/usr/doc/lilo-?.?/README
The drive limit does not exist in every BIOS. Some modern motherboards and
disk controllers are equipped with a BIOS that supports more (typically
four) disk drives. When attempting to access the third, fourth, etc. drive,
LILO prints a warning message but continues. Unless the BIOS really
supports more than two drives, the system will _not_ be able to boot in
that case.*
Dont forget, even tho' linux see's more that 2 drives (even if the BIOS
doesent support more than 2) lilo will FAIL.
You bios MUST support more than 2 drives to use LILO.
Of course a bootdisk made from the system running on /dev/hdc will
automaticly boot the system.
>
> -Evan-
>
--
Regards Richard.
[EMAIL PROTECTED]
