9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [explanations] MBR messed up on installation
Date: Tue, 29 May 2007 02:14:07 +0200	[thread overview]
Message-ID: <20070529001407.GB172@polynum.com> (raw)
In-Reply-To: <9f3897940705281631k58262cd6n5129282c8bbd6a1@mail.gmail.com>

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


      reply	other threads:[~2007-05-29  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 18:35 [9fans] " tlaronde
2007-05-24 12:55 ` erik quanstrom
2007-05-24 13:13   ` Paweł Lasek
2007-05-28 18:05 ` [9fans] Re: [explanations] " tlaronde
2007-05-28 23:31   ` Paweł Lasek
2007-05-29  0:14     ` tlaronde [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=20070529001407.GB172@polynum.com \
    --to=tlaronde@polynum.com \
    --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).