From: jmerkey@wolfmountaingroup.com
To: jmerkey@wolfmountaingroup.com
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Forensic File System GUID Linux/Windows
Date: Wed, 25 Jun 2008 08:53:24 -0600 (MDT) [thread overview]
Message-ID: <2740.69.2.248.210.1214405604.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <1861.69.2.248.210.1214405540.squirrel@webmail.wolfmountaingroup.com>
>> jmerkey@wolfmountaingroup.com wrote:
>>> The following GUID is being used in the Wolf Mountain Group, Inc.
>>> Forensic
>>> File System (FFS) for GPT intel EFI partitions. Since there is no
>>> central
>>> registry for EFI GUID's it is posted here for referece for folks who
>>> may
>>> run accross it on Windows Vista, 2003, and 2008 systems running FFS on
>>> Windows that may be using dual boot with Linux or vmware:
>>>
>>> #define PARTITION_FFS_GUID \
>>> EFI_GUID( 0xBEEFCAFE, 0xFEED, 0x0000, \
>>> 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01)
>>>
>>
>> You would have vastly less probability of accidental collision if you
>> generated a proper random GUID, for example:
>>
>> : tazenda 118 ; uuidgen -r
>> 33ae8a9c-441e-4d97-93a3-8561388ce905
>>
>> -hpa
>
Thanks. Good advice. What we really need is someone to maintain a
central registry for UUID generation for EFI and GPT based ID's. Since
drives are getting bigger and bigger, GPT is probably going to be the
standard 5 years from now, so sooner is better than later. I will
regenerate a new UUID using these tools and update the software.
Thanks for the help.
:-)
Jeff
>
>
>
next prev parent reply other threads:[~2008-06-25 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 19:22 jmerkey
2008-06-23 19:50 ` Lennart Sorensen
2008-06-23 20:07 ` jmerkey
2008-06-24 19:13 ` H. Peter Anvin
[not found] ` <1861.69.2.248.210.1214405540.squirrel@webmail.wolfmountaingroup.com>
2008-06-25 14:53 ` jmerkey [this message]
2008-06-30 22:39 ` [ANNOUNCE] Forensic File System GUID Linux/Windows and patches jmerkey
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=2740.69.2.248.210.1214405604.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@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
Powered by JetHome