From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Install Advice Requested.
Date: Sun, 30 Jun 2013 19:34:12 +0200 [thread overview]
Message-ID: <20130630173412.GA559@polynum.com> (raw)
In-Reply-To: <l4ld72fo6a573b5svbrlmaea.1372607434805@email.android.com>
On Sun, Jun 30, 2013 at 11:50:34AM -0400, Erik Quanstrom wrote:
> The wording might not be what was intended. Prep -p emits commands to build the sd(3) partition table in memory. Nothing is written to disk.
>
Nonetheless, if things haven't changed, Plan9 can not be installed on an
extended partition; and will probably not install on a disk split with
GPT (but in this case, if there are extended partitions, this is not
GPT).
It is wise to read the manpages before doing an install, and maybe
recommended to use another fdisk to allocate a Plan9 partition (slice)
and let, afterwards, Plan9 installation scripts organize the Plan9 slice
without touching other non Plan9 partitions or the MBR.
Once more: if things haven't changed since I wrote the howto---if
the fat partition is set in the Plan9 partition, the scripts assume
that the installation is done. This could lead, if the installation
is interrupted after this step is done but before the installation
completes, to the inability to proceed with the rest of the
installation. In this case (if nothing is really set in the Plan9
partition) erasing the first two blocks of the Plan9 partition
should allow the installation to complete.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2013-06-30 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 15:50 Erik Quanstrom
2013-06-30 17:34 ` tlaronde [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-30 15:35 Terry Wendt
2013-06-30 1:30 [9fans] Install Advice requested Terry Wendt
2013-06-30 5:26 ` Matthew Veety
2013-06-30 6:31 ` Terry Wendt
2013-06-30 8:06 ` tlaronde
2013-07-01 9:10 ` Artem Novikov
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=20130630173412.GA559@polynum.com \
--to=tlaronde@polynum.com \
--cc=9fans@9fans.net \
/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).