From: jmerkey@wolfmountaingroup.com
To: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
Cc: jmerkey@wolfmountaingroup.com, linux-kernel@vger.kernel.org
Subject: Re: Forensic File System GUID Linux/Windows
Date: Mon, 23 Jun 2008 14:07:31 -0600 (MDT) [thread overview]
Message-ID: <1059.69.2.248.210.1214251651.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <20080623195054.GA31126@csclub.uwaterloo.ca>
> On Mon, Jun 23, 2008 at 01:22:26PM -0600, 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_ForenFS_GUID \
>> EFI_GUID( 0xBEEFCAFE, 0xFEED, 0x0000, \
>> 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01)
>>
>>
>> Patches to efi.h and efi.c in /fs/partitions will be posted after July
>> 2,
>> 2008 to www.wolfmountaingroup.org.
>
> So how many 'FFS' filesystems does that make now? Why not ForenFS or
> something more unique?
Done. I will leave the GUID numbers the same in the parted sources and
change the name to "ForenFS" in the source tree and efi.[ch]
Jeff
>
> --
> Len Sorensen
>
next prev parent reply other threads:[~2008-06-23 20:16 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 [this message]
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
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=1059.69.2.248.210.1214251651.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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
all inboxes | Powered by JetHome®