[Fwd: Re: [expert] running 2 linuxes on a single machine]

[Chavdar Videff]

-------- Original Message --------

Subject:	Re: [expert] running 2 linuxes on a single machine
Date:	Mon, 03 Jun 2002 16:56:35 +0300
From:	Chavdar Videff <[EMAIL PROTECTED]>
Reply-To:	[EMAIL PROTECTED]
To:	[EMAIL PROTECTED]
References:	<[EMAIL PROTECTED]>

[EMAIL PROTECTED] wrote:

On Mon, 3 Jun 2002, Chavdar Videff wrote:

Hi
I tried and installed two different distributions of linux on the same 
machine in order to compare them, etc.

I put together a few notes at:
  http://www.digitalhermit.com/linux/dualboot.html

The first one was a Mandrake 8.1 and I use its lilo to boot all other 
OS. Everything was OK and worked smoothly.
However, I installed a SuSE 7.0 and during the installation process 
everything worked fine.
When I rebooted, the SuSE started to behave strangely. Modprobe could 
not find the eth0 for instance. I was not able to mount vfat partitions. 
I could not even makeconfig in order to recompile the kernel (I thought 
something got wrong with the NIC driver).

How are your partitions laid out? Which ones are shared between the two
installations? You need to keep /usr, /etc, /var, /bin, and /sbin
separate. The easiest way is to create two / partitions, one for each
OS, and share only /home and swap. For /home directories it's probably
best to use different users to avoid settings conflicts.

Th

The hard disk is 20GB

/dev/hda1 is for win98 - 3 GB
/dev/hda3 is the second physically and there is the Mandrake 8.1 - Imade it active and the lilo is installed there - I have left the mBR untouched so that windows crashes as it pleases
/dev/hda2 is the extended where I have a second vfat partition, four swap partitions and /dev/hda6 is the partition where I installed the suse
it looks as if the first /swap partitioin was the only shared resource
the suse is invoked by the lilo of the mandrake - it is configured to look for /boot/vmlinuz on /dev/hda6

This was at work.

Is it the LILO that messes up things?

Possible -- depending on how you have the images set up. Have you tried
re-running lilo after you install?

What do you mean?