On Thu, 4 Oct 2001, root wrote:
> ...
> My problem is that I wish to boot either drive using LILO. I have LILO
> all set up to boot the first hard drive; however I cannot get it to boot the
> second drive -- it seems to want to use Red Hat's kernel and map files; I
> cannot figure out how to make LILO see the files on the second hard drive!
>
> I *could* copy the SuSE kernel and necessary files over to the first
> drive, into the /boot directory -- but I don't want to.
> ...
> Here is my /etc/lilo.conf file (my attempts to boot the second hard
> drive with SuSE on it are commented out, because I couldn't get LILO to work
> unless I do this). The SuSE boot stanzas are made from the LILO.CONF file
> that is automatically created when you install SuSE:
> ----------
>
> boot = /dev/hda
> map = /boot/map
> install = /boot/boot.b
> read-only
> prompt
> timeout = 50
> message = /boot/message
> default = linux
>
> image = /boot/vmlinuz-2.4.2-2
> label = linux
> root = /dev/hda1
>
> # image = /boot/vmlinuz
> # label = suse
> # root = /dev/hdb3
> # initrd = /boot/initrd
>
> # image = /boot/vmlinuz.suse
> # label = suse.suse
> # root = /dev/hdb3
> # initrd = /boot/initrd.suse
>
> ----------
> ...
> Also, that "message" line in the LILO.CONF file, that is, I think, what
> causes that dopey red-colored "Red Hat Linux" boot screen appear. Can I just
> #comment# it out for the next time I run LILO, or do I have to "rebuild" the
> map file first (probably by deleting it)? I am uncertain if I understood
> this point properly in the manual page.
>
As I understand it, a line "image = /boot/vmlinuz", like the one you
commented out, says that the kernel for label=suse is in the file
/boot/vmlinuz. But when you got vmlinuz-2.4.2-2, the procedure may well
have made vmlinuz be a symbolic link to vmlinuz-2.4.2-2, and not the
kernel you want for SuSE. If you want the SuSE kernel to be what "lilo"
finds when it is installing the boot loader, you should be able to get it
to work by copying to /boot the kernel you want run for "label=suse", and
change lilo.conf so that image = /boot/<file you really want>. For the
"label=suse.suse" section, if there is no file /boot/vmlinuz.suse or there
is no file /boot/initrd.suse, you can expect the "lilo" command to fail.
The cure is to make sure they are there, and are what you want used.
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
