On Thu, 20 Jan 2000, warren11 wrote about, Re: lilo for 2nd hd:
> On Wed, 19 Jan 2000, Richard Adams wrote:
>
> > On Wed, 19 Jan 2000, warren11 wrote about, lilo for 2nd hd:
> > > I have 2 HD's, Using RedHat 6.1. First and main drive is /dev/hda
> > > Second is /dev/hdb
> > > Here is copy of my /hda2/etc/fstab;
> > > /dev/hda2 / ext2 defaults 1 1
> > > /dev/hda1 /mnt/dos vfat defaults 0 0
> > > /dev/hdb1 /mnt/hdb1 ext2 defaults 1 2
> > > /dev/hdb2 /mnt/hdb2 ext2 defaults 1 2
> > > /dev/hdb3 swap swap defaults 0 0
> > > /dev/fd0 /mnt/floppy msdos owner,noauto 0 0
> > > /dev/cdrom /mnt/cdrom iso9660 owner,noauto,ro 0 0
> > > none /proc proc defaults 0 0
> > > none /dev/pts devpts gid=5,mode=620 0 0
> > > ------------------------
> Here is my new lilo.conf;
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> vga = ask
> timeout=50
> default=rh61-a
>
> image=/boot/vmlinuz-2.2.12-20
> label=linux
> initrd=/boot/initrd-2.2.12-20.img
> read-only
> root=/dev/hda2
>
> image=/boot/vmlinuz2
> label=linux2
> initrd=/boot/initrd2
> read-only
> root=/dev/hdb2
>
> other=/dev/hda1
> label=dos
>
> other=/dev/hdb
> label = linux2
>
> When I run lilo on this it says 'Added linux
> Added linux2
> Added dos
> Duplicat label "linux2"
>
> Of course it still wont boot to /dev/hdb when I enter at lilo prompt
> "linux2" and the tab key wont show it.
Then lilo has done nothing, it aborted because you have defined linux2
twice, you CANT have 2 of anything "exachtly" the same.
Firstly a few tips;
Lawson sent you a small piece of reading, like it says IF you understand
that you can do almost anything with lilo, obviously you dont understand.
Why not name all images as follows so you know which one is which.
You have /dev/hda and /dev/hdb so images destined for /dev/hda we will call
vmlinuza-2.x.x.-xx
vmlinuzb-2.x.x.-xx
A small note on the vga = statement.
why not define the mode you require at lilo install time, i belive Redhat
supplies kernels with framebuffer devices so we can define the video mode
via lilo. Here is a list, i suggest you use
vga = normal
UNTILL you have seen how lilo works.
##### Referance list;
# 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
The idea is you uncomment the desired mode, if the mode is invalid meaning
you monitor/video system can do the resolution defined, you will be
presented with a complete list of vaild modes at boottime.
Another note, in this example the first image is the default, if you want
another as default make it the first entry.
Another note, copy the System.map belonging to the image as well to /boot
and give it the same name extention as the image, take the first entry in
the sample below, you would then copy System.map to /boot as
System.map-a2.2.14
Now a sample lilo.conf.
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
vga = normal
timeout=100
image = /boot/vmlinuza-2.2.14
root = /dev/hda2
label = a2.2.14
read-only
image = /boot/vmlinuz-2.2.12-20
root = /dev/hdb2
label = b2.2.12-20
read-only
image = /boot/vmlinuz-2.2.13-1
root = /dev/hda2
label = a2.2.13-1
read-only
Add your other images and OS's here.
You can define up to 19 different image/OS entrys.
Run;
/sbin/lilo
If you get any output other than
Added a2.2.14 *
Added b2.2.12-20
Added a2.2.13-1
Added what you defined.
Then lilo would have failed and done nothing.
Note the * on the first Added line, thats lilo saying this is the default
image.
> > > Note that I can boot to second drive using the boot floppy but that is a
> > > bother and rather have it an altenate boot from regular lilo.
Then there should be no problem at all.
> I am about to give it up and just resort to booting using the floppy boot
> for the /hdb boot.
Dont be silly, i can assure you once lilo has been succsesfully installed
you will see what you were doing wrong and see just how simple it can be,
you can then start experimenting with lilo to do more complecated things,
just remember one IMPORTANT thing, make sure you have flopps to boot both
systems, if lilo wont boot the system thro'a wrong image type ie a kernel
made under /dev/hdb2 cannot simply be used for booting /dev/hda2, you need
to change the "root device" which is hard cored into the image with 'rdev'
rdev -help will show you some handy tips man rdev for full info.
Belive me i mentioned rdev now because in my experiance one trys to boot a
partition other then the one where the image was made, life's not that easy
;-)
Let me know how you get on.
> Warren
>
> * | Warren Hrach, San Diego, CA 92107 | *
> * | [EMAIL PROTECTED] Linux & BBBS on an AMD K5 | *
> * | BBS at (619}224-4878 | *
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
Happy New Year
