bug-parted
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Bug#210584: parted should silently accept table revision 1.02]


From: Timshel Knoll
Subject: [Fwd: Bug#210584: parted should silently accept table revision 1.02]
Date: Sat, 13 Sep 2003 16:13:01 +1000

Here's a bug report I received regarding handling of EFI partition table
versions.

Cheers,

Timshel

-- 
Timshel Knoll
Debian GNU/Linux Developer      http://www.debian.org/
SPI Contributing Member         http://www.spi-inc.org/
GnuPG:          1024D/DE3E8AA7 Timshel Knoll <address@hidden>
Fingerprint:    6ABC 91A9 E274 ED67 0E32  8F0F 5DFA 9391 DE3E 8AA7
--- Begin Message --- Subject: Bug#210584: parted should silently accept table revision 1.02 Date: Fri, 12 Sep 2003 10:44:38 +0100 User-agent: Mutt/1.3.28i
package: parted
version: 1.6.5-3

  Running d-i on my i2000 here, and parted complains that the partition
table format is newer than it knows about.  Turns out that for some
versions of parted before 1.6.5 (including 1.4 in woody),
parted wrote a GPT partition table format of 1.02.  Since 1.6.5 it has
changed to write 1.00 "for compatibility reasons".

So, anyone trying parted on sarge, on a system with an efi partition
table written by woody will see:

        _("The format of the GPT partition table is newer "
                "than what Parted can recognise.  Please tell us!  "
                "address@hidden"))

followed by a 'cancel/ignore' prompt.

The "solution" is to toggle one of the partition flags on and
off, which causes parted to rewrite the table with the most recent
version it knows about.  Seems everyone is supposed to just know
that ;(

It would be nice if parted understood that tables with a revision of
1.02 were likely written by it, and silently accept that revision.  Of
course, if there was ever a significant spec change that required the
revision field be changed to 1.02, then we'd have a problem.  However,
maybe we can request that any new revision doesn't use 1.02, as it was a
spec ambiguity that caused the problem in the first place.

IMHO this needs fixing for sarge, to avoid much confusion (not to
mention lots of mails to bug-parted).

Richard





--- End Message ---

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]