From: Cor <builder@bulky.ath.cx>
To: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: how to install 2 linux(es) on a PC?
Date: Mon, 10 Nov 2003 12:31:44 +0100 [thread overview]
Message-ID: <3FAF7720.6050201@bulky.ath.cx> (raw)
In-Reply-To: <1068134298.28593.110.camel@ruby.rub.belfastdata.com>
greg wrote:
> On Wed, 2003-11-05 at 21:17, jbrown105@speedymail.org wrote:
>
>>On Wed, 5 Nov 2003 00:00:59 -0800 (PST), "terry white" said:
>>
>>>on "11-4-2003" "Jim C. Brown" writ:
>>>: Which partitions are the 2 linuxes installed on? (I assume you installed them
>>>: on separate partitions, for obvious reasons they can't be installed onto the
>>>: same partition.)
>>>
>>>... i don't see why not. given 'one' partition, create two file systems,
>>
>>Also, AFAIK Lilo can only be made to select booting of PARTITIONS, so to
>>be able to boot the 2 linuxes with Lilo, they'd have to be on separate
>>partitions. If i'm wrong please correct me.
[snip]
> although i could imagine having more than one, if the bootup procedure
> somewhere executed a "chroot", thus delineating a filesystem within a
> filesystem. but it would be difficult to imagine wanting to bother to
> make such a setup actually work.
Although I prefer seperate partitions, this can be usefull if you only
have one partition to build for instance LFS on http://linuxfromscratch.org/
A hint describing the process can be found here
http://www.nl.linuxfromscratch.org/hints/downloads/files/one-partition-hint.txt
Greetz,
Cor Lem
prev parent reply other threads:[~2003-11-10 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 3:17 how to install 2 linux(es) on a PC? vick Julius
2003-11-04 15:30 ` Jim C. Brown
2003-11-05 8:00 ` terry white
2003-11-05 21:17 ` jbrown105
2003-11-06 13:28 ` terry white
2003-11-06 15:58 ` greg
2003-11-06 20:44 ` fewa
2003-11-10 11:31 ` Cor [this message]
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=3FAF7720.6050201@bulky.ath.cx \
--to=builder@bulky.ath.cx \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).