So I got slack 3.6 installed (wow, what a lot of work - will take suse
any old day :). I followed the sage advice of folks here and have
found that as someone suggested you pretty much have to copy the
/vmlinuz from /dev/hdb1 to /dev/hda2 with another name or when lilo
boots it uses the /vmlinuz from /dev/hda2 which creates some
interesting problems with slack 3.6. Its more academic now since I am
awaiting delivery of redhat 5.2 at this point and I cannot seem to get
slack's obtuse setup program to see the atapi cd I have but yet it will
mount it fine at shell. As an interesting point, the cdrom works quite
well in suse and other stuff I have tossed at it. I think slack's gui
setup tool times out too quick. I watched it mounting and my cd light
does not even come on; yet when I manually mount it... ta da. Success.
So the 64 buck question is there is no lilo at /dev/hdb2 since I chose
to use the lilo at /dev/hda in the mbr. No point in two lilo's as Mr.
Johnson points out in his followup post. Now when I decide to compile
a kernel at /dev/hdb1 what do I do to get it seen? I have no lilo
there to run and the /vmlinuz.slak is copied from /dev/hdb1 to
/dev/hda2. If I run the /sbin/lilo on /dev/hda2 it will just see the
/vmlinuz.slak I placed there before.
This seems rather unusual for one operating system. Comments, other
ways of doing things, gratefully accepted. Using the Os/2 boot manager
I booted numerous copies of OS/2 warp at different spots with no
issues. Surely there is an elegant way of doing this.
--
Michael E. Perry
[EMAIL PROTECTED]
------------------
-
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
