Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I dual boot redhat and suse. Redhat LILO is configured to launch SUSE
from the lilo menu.
If I launch SuSe from redhat lilo, I am unable to browse the net. During the
initialization, I see failure messag with dhcp. I also see eho0 as not
being available.
however, if I boot using SuSE boot diskette (with lilo), I am able to
browse the net. However, I still see some dhcp related failure message
during boot process.
1. I am curious to know why the way suse is launched makes difference?
2. How to fix issues related to dchp, eth0 in SuSE?
Originally posted by concoran I dual boot redhat and suse. Redhat LILO is configured to launch SUSE
from the lilo menu.
If I launch SuSe from redhat lilo, I am unable to browse the net.
How do you have the SuSE part of lilo setup? The way that I do it is to copy SuSE's vmlinuz into Redhat's /boot directory and name it something like SuSE.vmlinuz. Then use this in lilo.conf.
And if having the SuSE stuff over in the Redhat directory is causing problems, copy the RH boot stuff over to the SuSE side and run lilo from there.
FWIW, I have Win4Lin, SuSE, Mandrake, & Windows setup on lilo (with no apparent problems)
Quote:
During the
initialization, I see failure messag with dhcp. I also see eho0 as not
being available.
It's probably the eth0 (eho0?) failure that's hosing you, but I am network ignorant...
You are probably right, rootboy. I must copy the vmlinuz from suse partition and move it into redhat partition. In the lilo.conf above, i am curious to know what the 'image=/boot/vmlinuz for 'SuSE' refer to? Does it refer to the vmlinuz on suse or on the redhat root partition?
Let me try to copy the vmlinuz from both suse and caldera into redhat partitions and see if it brings up the dhcp.
Yeah, I got that to work.
As rootboy pointed out, I just copied the kernels (vmlinuz) from both suse and caldera partitions and placed them into the redhat's /boot folder under difference names, updated lilo.conf, installed lilo, and lo! it was all set.
Originally posted by concoran Yeah, I got that to work.
As rootboy pointed out, I just copied the kernels (vmlinuz) from both suse and caldera partitions and placed them into the redhat's /boot folder under difference names, updated lilo.conf, installed lilo, and lo! it was all set.
Cool
I just recently added SuSE 7.3 to my mix (now up to 4 OS'es) This time around, I left things where they came from and just added the absolute PATH to the lilo.conf statement.
In other words, on my box I have /dev/hdb6 formatted w/reiser and it contains Mandrake. To get to it from SuSE, I mount it as /Hdb6 (on my box, any external partition that is mounted has its first letter capitalized to clue my in to it being an external partition. And I like to keep things simple by naming it after the partition)
So, to add Mandrake to my lilo I:
a) have to be sure that /Hdb6 is mounted
b) include /Hdb6/boot/vmlinuz-Mandrake (or whatever it's called) into the Mandrake portion of my lilo.conf.
This keeps things separate and seems to work well.
Originally posted by concoran cool rootboy, great job.
Thanks
Quote:
I am curious to know if partitions from /etc/fstab are mounted prior to linux being loaded (rather, I am not sure how to formulate the question)?
If I understand your question correctly, you're asking if these various /boot directories that would be located on a different partitions (at least some of them) need to be mounted first (during the boot).
No, they only need to be mounted whenever you modify your bootloader (when you run lilo). After lilo successfully runs, you can umount these partition(s) unless you need them for some other reason.
And the obvious question would be why not use the absolute partition device (i.e. /dev/hdb6) rather than a mount point. You can, but you would still need to mount the partition, so it doesn't gain you anything (that I can see).
Quote:
Is lilo.conf read everytime linux starts? or is it important only at the LILO installation time?
I don't know, but I strongly doubt it. That's why you run lilo in the first place, to convert your "human-readable" parameters into the actual bootloader code.
Quote:
What exactly happens when you install LILO on the root partition?
# Added by NeTraverse for Win4Lin kernel
image = /boot/win4lin
label=win4lin
initrd = /boot/initrd
root=/dev/hda6
Notice the "Hda9" (etc...), that's my mount point for that particular partition. I had to mount these partitions so that lilo could find the vmlinuz's when it wrote the new bootloader.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.