From: Isaac Dupree <ml@isaac.cedarswampstudios.org>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [patch] search for partition using GPT GUID
Date: Thu, 11 Mar 2010 15:04:26 -0500 [thread overview]
Message-ID: <4B994CCA.4010908@isaac.cedarswampstudios.org> (raw)
In-Reply-To: <3c6a49541003110643y505bb8bdn187e1883c044e23f@mail.gmail.com>
On 03/11/10 09:43, KESHAV P.R. wrote:
> GPT GUID is one of the best FILESYSTEM-INDEPENDENT way of uniquely
> identifying a partition.
I am not sure if Linux supports gpt-uuids (I didn't find any hints of it
via google!), but this sounds like it could be great news for Linux
encrypted swap -- the current enc-swap recommendations destroy the
partition contents on every boot, with a new random encryption-key and
new `mkswap` inside it, so you have to refer to it like /dev/sda5. And
then "/dev/sda5" partition gets destroyed on every boot, so the failure
mode for wrong-partition is even worse than normal. But with a UUID
stored outside the partition, it would be more possible to uniquely
identify that partition. (Or a different encrypted-swap format, but no
one seems interested in doing that :-( )
> Maybe even the GPT Disk GUID can be used to reference a
> GPT disk (instead of confusion over whether it is (hd1) or (hd2) and
> so on.
oh, interesting, that could perhaps be nice for something
-Isaac
next prev parent reply other threads:[~2010-03-11 20:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 14:43 [patch] search for partition using GPT GUID KESHAV P.R.
2010-03-11 20:04 ` Isaac Dupree [this message]
2010-03-11 20:07 ` Seth Goldberg
-- strict thread matches above, loose matches on Subject: below --
2010-03-12 11:52 KESHAV P.R.
2010-03-12 11:44 KESHAV P.R.
2010-02-25 6:59 gburanov
2010-04-02 20:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-12 18:21 George Buranov
2010-02-18 7:13 ` gburanov
2010-02-20 11:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-21 12:32 ` Michal Suchanek
2010-02-21 13:27 ` Colin Watson
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=4B994CCA.4010908@isaac.cedarswampstudios.org \
--to=ml@isaac.cedarswampstudios.org \
--cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.