From: Richard Miller <miller@hamnavoe.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] non-standard installs
Date: Thu, 21 Mar 2002 19:46:11 +0000 [thread overview]
Message-ID: <20020321194610.27E5719A89@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
> ... As someone else mentioned, Plan 9 has to be in a
> primary partition, so that bootstrap loaders can find it
No longer true - as of the 26 April 2001 update, 9load can find
plan 9 in an extended partition.
-- Richard Miller
[-- Attachment #2: Type: message/rfc822, Size: 2472 bytes --]
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] non-standard installs
Date: Thu, 21 Mar 2002 11:33:08 -0500
Message-ID: <d80755a8eef4aa1f2bebc11b3c4dfe34@plan9.bell-labs.com>
> I'm sure I'm just unlucky, but given my (recent) experience
> of installing Plan 9 for the first time, I'd stay well away from your
> "production" machine, even if it did have a clean partition.
>
> I found (repeatedly) that trying to put Plan 9 into a clean
> secondary partition corrupted the size of the enclosing primary
> partition. I was able to put it back, but thankfully the whole 40Gb
> was brand new at the time, and so this wasn't necessary (except as a
> vain attempt to keep the other partitions as the shop had left them).
> Thus, I eventually scrapped the whole partition table, and put Plan 9
> into a primary partition.
> Since then it's all gone fine.....
There were some serious bugs in the handling of secondary
partitions. They're fixed in the fdisk on the current boot disk,
as of January 13, 2002. As someone else mentioned, Plan 9 has to be in a
primary partition, so that bootstrap loaders can find it
(unlike, say, Linux swap, which has no right to be in a
valuable primary partition, but I digress).
Russ
next reply other threads:[~2002-03-21 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 19:46 Richard Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-21 16:33 Russ Cox
2002-03-21 8:36 forsyth
2002-03-21 13:34 ` Martin C.Atkins
2002-03-20 9:43 Andrew
2002-03-21 7:31 ` Martin C.Atkins
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=20020321194610.27E5719A89@mail.cse.psu.edu \
--to=miller@hamnavoe.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).