Michael Johnson wrote:
>
> On Thu, 14 Jan 1999, zentara wrote:
> >
> > So if you do have trouble booting Redhat, remember to try this.
> > What happened with me, with the Redhat kernel on /dev/hdb,
> > my Suse kernel would boot with the Redhat root partition,
> > with an error saying the Redhat image could not be found.
> I dual booted RH and S.u.S.E. for a while. ( Just got rid of RH (again)).
>
> RedHat doesn't keep it's kernel in the / dir I don't think, it keeps in in
> a subdirectory so when I used lilo I added the path to the config and it
> found it. I never had to move the kernel over.
Redhat keeps it in /boot. And I think they like to do it that
way so on large harddrives, you can mount /boot as /dev/hda1,
as an option, and be certain that lilo will work.
Redhat mentions in it's manual that there are so many variables,
in lilo, disk geometry, etc; that they can't give any lilo
tech advise unless your /boot partition is under the 1024
cylinder limit.
That is what I've seen myself. What works for one setup, may not
work on another machine. So, just experiment until you get
a working setup on your system.
My setup is strange. I have a greater than 5 gig /dev/hda and
a 3 gig /dev/hdb.
I can install suse on /dev/hdb and run lilo in the mbr, and
it works.
If I try to put suse on /dev/hda, I need to use the "/boot in
/dev/hda1" trick, to get it to boot, and Redhat's image must be
on /dev/hda.
There are only a few variables involved, so guessing a good
setup for lilo, is easier than trying to learn the exact details
of why some geometries work, while others don't. It's a zen approach.
:-)
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
