From: gburanov@gmail.com
To: grub-devel@gnu.org
Subject: Re: Re: Search GPT partition in GRUB
Date: Thu, 11 Feb 2010 02:27:55 -0500 [thread overview]
Message-ID: <23794987.31265873275512.JavaMail.root@wombat> (raw)
In-Reply-To: <4B6C4B5B.2060809@gmail.com>
-- Vladimir 'φ-coder/phcoder' Serbinenko wrote :
Colin Watson wrote:
>> It would be ideal if we can search the GPT partition/disk by GUID -
>> that's what we got NTFS GUID for =)
>>
>
> That would be nice, and it might not be all that difficult to implement,
> but of course it would take up extra precious space in the core image.
> I don't think it's really necessary in this case.
>
>
> Implementing it isn't difficult but it's confusing to have two types of
> UUIDs. I'm not sure we need GPT UUIDs. grub-mkconfig will continue to
> use filesystem UUIDs, so GPT UUIDs will only be used in maual
> configuration. But in the latter case it's much easier to use filesystem
> labels when writing configuration manually. Probability of collision
> with n-partitions and k bits is lower than
> n^2*2^(-k-1)
> Even with 1024 partitions and 32-bit IDs it's under 1 over 8192.
> Fell free to detail usage cases when my logic is wrong (e.g. disk
> configuration, who writes config, external factors and so on)
As I said already (see upper), NTFS volume serial number (that's really UUID in NTFS) is not really unique, so that's not a good way of identification.
> Cheers,
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
--
This message was sent on behalf of gburanov@gmail.com at openSubscriber.com
http://www.opensubscriber.com/message/grub-devel@gnu.org/13383952.html
prev parent reply other threads:[~2010-02-11 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 11:26 Search GPT partition in GRUB gburanov
2010-02-04 18:31 ` Colin Watson
2010-02-05 14:19 ` gburanov
2010-02-05 16:46 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-02-11 7:27 ` gburanov [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=23794987.31265873275512.JavaMail.root@wombat \
--to=gburanov@gmail.com \
--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.