From: Dave Vehrs <davidv@aspsys.com>
To: linux-kernel@vger.kernel.org
Subject: Re: How to install two linux OSes on the same PC
Date: 05 Feb 2003 14:10:55 -0700 [thread overview]
Message-ID: <1044479456.1431.23.camel@DV-Laptop> (raw)
In-Reply-To: <3E418AD0.BC9F9765@npd.hcltech.com>
On Wed, 2003-02-05 at 15:06, Narsimha Reddy CHALLA wrote:
> I want to do two different linux installations rh 7.2 and rh
> 8.0 on the same pc with single hard disk. I installed the rh 7.2 in
> partitions say /dev/hda5 ( /) , /dev/hda6 (/home) , /dev/hda7 (
> /usr) ,/dev/hda8 ( /tmp),... /dev/hda11 etc.
>
> But how can I install the rh 8.0 in partitions say /dev/hda12
> ( as "/" ) ... etc ?? Since the installer won't allow as there
> already exists a "/" partition for the rh 7.2 and tries to override
> it with the root partition of rh 8.0. So I tried giving a different
> lable to the root partition of rh 8.0 say /root1 and other partitions
> as /root1/usr, /root1/home, /root1/tmp etc. But here also the installer
> is looking for the partition named "/" and without that the installation
> is not happening.
I believe the problem is related to Redhat's use of partition labels
by default on 7.x and 8.x. Makes it easy if the drives master/slave
changes but causes problems for other things like this.
For example, my /etc/fstab looks like:
LABEL=/ / ext3 defaults 1 1
LABEL=/boot /boot ext2 defaults 1 2
LABEL=/home /home ext3 defaults 1 2
/dev/hda3 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
Attempting to boot a system with two drives (or multiple partitions on
the same drive) configured like this will confuse the system. So the
first step would be to change the LABEL= lines to /dev/<device> (i.e.
/dev/hda1 /boot ......etc.)
Next issue is how you want to boot the two systems. One boot partition
or two? With one boot, make a copy of what is already there, then
install the new system, allowing it to overwrite the old. Then merge
the two boot partitions by hand. They will already be a different
kernels, etc. so it shouldn't be too hard.
Then I would recommend booting the second system or mounting its drives
in the first temporarily and making similar changes to its fstab that we
did to the first.
Then reboot and I believe it should work....
Good luck,
Dave V.
--
David E Vehrs, System Engineer Aspen Systems
davidv@aspsys.com 3900 Youngfield Street
Tel: +01 303 431 4606 Wheat Ridge CO 80033, USA
Fax: +01 303 431 7196 http://www.aspsys.com
next prev parent reply other threads:[~2003-02-05 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 22:06 Narsimha Reddy CHALLA
2003-02-05 9:24 ` Bryan Andersen
2003-02-05 21:10 ` Dave Vehrs [this message]
2003-02-07 8:08 ` Narsimha Reddy CH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1044479456.1431.23.camel@DV-Laptop \
--to=davidv@aspsys.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®