util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Davidlohr Bueso <dave@gnu.org>
Cc: Petr Uzel <petr.uzel@suse.cz>, util-linux <util-linux@vger.kernel.org>
Subject: Re: [PATCH 2/3] fdisk: add GPT support
Date: Thu, 27 Sep 2012 14:03:14 +0200	[thread overview]
Message-ID: <20120927120314.GB18644@x2.net.home> (raw)
In-Reply-To: <1345550602.2664.6.camel@offbook>

On Tue, Aug 21, 2012 at 02:03:22PM +0200, Davidlohr Bueso wrote:
> This patch allows fdisk to handle GUID partition tables, based on
> the latest UEFI specifications version 2.3.1, from June 27th, 2012.

 Applied, with some changes (add string based list of partition
 types).

 TODO:

    - differentiate between number of allocated and used partitions in GPT,
      for example "Partition number (1-128):" dialog is strange if you have
      only one partition. [I'll fix it tomorrow]

    - add 'Device' column to GPT list_table output [I'll fix it tomorrow]

    - add 'g' to main menu to create a new empty GPT disklabel

    - LBA alignment, it necessary to use the same things we use for MBR;
      partitions has to be aligned according to I/O limits (sector
      size). [Important!]

    - move list_table() functions to fdisk_label drive struct

    - remove 'disklabel' from fdisk.c at all and keep fdisk.c
      independent on MBR

    - remove global label-specific variables (e.g. gpt ents[])

    - test GPT (specially 't' command) on big-endian machine
      (EFI UUIDs has been designed during LSD trip...)


less important things:

    - add '<something>' to fdisk menu to print details about selected
      partition (uuid, type uuid, type name, name, etc...)

    - add '<something>' to menu to print details about the partition
      table (header, backup header, locations, number of allocated
      entries, used entries, offset of entry table and offset and size
      of data area, etc.)

All should be implemented by drive specific functions, without
exceptions, fdisk.c has to be simple and readable :-)

Note I did not applied the man page yet. I think we can do that
later when the code will be stable.

> Note that when adding libblkid support for probing, some of the local probing functions will go.

 Yes, but this is not so important for now. We have to clean up before
 we start to implement new things.

 Thanks!

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2012-09-27 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 12:03 [PATCH 2/3] fdisk: add GPT support Davidlohr Bueso
2012-09-27 12:03 ` Karel Zak [this message]
2012-09-27 21:51   ` Davidlohr Bueso
2012-10-01  7:25     ` Karel Zak
2012-10-02  8:05       ` Petr Uzel

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=20120927120314.GB18644@x2.net.home \
    --to=kzak@redhat.com \
    --cc=dave@gnu.org \
    --cc=petr.uzel@suse.cz \
    --cc=util-linux@vger.kernel.org \
    /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).