From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sun, 30 Jun 2013 19:34:12 +0200 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130630173412.GA559@polynum.com> References: Mime-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.4.2.3i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [9fans] Install Advice Requested. Topicbox-Message-UUID: 69ed9db6-ead8-11e9-9d60-3106f5b1d025 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 http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C