On Wed, 13 Jan 1999, Michael Johnson wrote:
> All you have to do is go into yast and edit kernel and boot configuration
> to your new config. Select kernel and boot configuration. Then select lilo
> configuration. Then select F4 for new config. Select configuration name (
> e.g RedHat ). Put the boot partition in. And select the path on that
> device to the linux kernel for the dist. SuSE will run lilo for you. You
> can do it by hand as well. I've booted different dists on many occasions
> as well as Solaris, BSD, Doze etc. using lilo. You, of course, do all this
> _after_ installing the dist.
>
> Note: you don't need to use two lilos, so when you install RH, when it
> asks you at the end if you want to install Lilo say 'no', and after
> installation boot S.u.S.E. and then put it manually in /etc/lilo.conf or
> use YaST. All you have to know to do it is the dev ( /dev/hda1 etc.) , the
> name you want to give it ( e.g. Redhat ) and the path location of the
> kernel for the dist on that dist partition ( e.g. /boot/vmlinuz on
> /dev/hda1 etc.)
>
> On your question about kernel compiles:
> Anytime you recompile your kernel on the other dist, you'll need to run
> lilo on whatever dist you are using to manage your partitions just like
> you do on the main dist or it won't boot properly. So if you use S.u.S.E.
> lilo and install say, a new kernel, on your RH paritition, then you need
> to reboot S.u.S.E. and then run lilo the same way you would if you built a
> new S.u.S.E. kernel. Lilo needs to be run after kernel compiles. This
> doesn't change cause you adding a dist.
This is not entirely correct. It is true that you have to run lilo after a
kernel compile, but if you just make sure that the lilo.conf of both
distributions are identical, it should not matter which of the distros
does the updating of lilo.
If you have your SuSE partition mounted in RH you could make RH's
lilo.conf a symlink to SuSE's. This way the two would always be
identical. (I haven't tested this, but it should work)
Good luck with the dual distro, and please report back whether my
suggestions work.
Regards
Ole
> On Wed, 13 Jan 1999, Michael Perry wrote:
> > I have a need to install a second linux distribution (redhat 5.2)
> > tomorrow for some stuff. I have suse installed to /dev/hda2 with lilo
> > in the bootsector as /dev/hda. Redhat will go to /dev/hdb1 which is
> > already formatted as a linux native partition.
> > How should I go about installing this partition's kernel and get lilo
> > to see this second linux distribution? I read the kernel and lilo
> > howto's but do not see a mention of multiple linux distributions on one
> > system. I did a test install of slackware tonite and moved the
> > slackware /vmlinuz to /dev/hda2 as /vmlinuz.slak. This booted slackware
> > fine with an entry in lilo.conf. What happens on the second
> > distribution when I compile a new kernel? Do I make dep, make clean,
> > make zImage as usual? How can I run lilo on the second distribution
> > and get the zImage to vmlinuz and then get it seen by the lilo that is
> > at /dev/hda? Do others mount the second hard disk with another distro
> > in their /etc/fstab or what?
> >
> > Thanks for any enlightenment.
> >
> > --
> > 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
>
-
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
