From mboxrd@z Thu Jan  1 00:00:00 1970
From: tlaronde@polynum.com
Date: Tue, 29 May 2007 02:14:07 +0200
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [explanations] MBR messed up on installation
Message-ID: <20070529001407.GB172@polynum.com>
References: <20070523183556.GA2037@polynum.com>
	<20070528180558.GA162@polynum.com>
	<9f3897940705281631k58262cd6n5129282c8bbd6a1@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9f3897940705281631k58262cd6n5129282c8bbd6a1@mail.gmail.com>
User-Agent: Mutt/1.4.2.2i
Topicbox-Message-UUID: 73e59478-ead2-11e9-9d60-3106f5b1d025

On Tue, May 29, 2007 at 01:31:48AM +0200, Pawe? Lasek wrote:
> 
> At the moment, fdisk also redefines partition numbers, rearranging
> them as it finds them on the disk (So if you have first partition
> number 3, then number 1, then number 2, it gets changed to 1-2-3).
> 
> It would be a fine thing if Plan 9's fdisk would rather follow the way
> of GNU/BSD fdisk and _NOT_ touch any partition it didn't modify. While
> the usage of plan 9 named partitions makes it irrevelant to p9, many
> people have other OS on their hard drive which don't add another layer
> (like disklabel or LVM) or aren't configured to do so.
> 
> Booting another OS just to run fdisk isn't a good thing. Pity that I
> don't have access to a Plan 9 machine (or time) to prepare a patch for
> this :-/

I will probably take the task.

Just, as usual, a matter of time: I have to tackle with business needs
just in order to have incomes ;)

But I will try to dedicate a slice of time in June for this.
-- 
Thierry Laronde (Alceste) <tlaronde +AT+ polynum +dot+ com>
                 http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C