From: jmerkey@wolfmountaingroup.com
To: linux-kernel@vger.kernel.org
Cc: jmerkey@wolfmountaingroup.com
Subject: [ANNOUNCE] Forensic File System GUID Linux/Windows and patches
Date: Mon, 30 Jun 2008 16:39:48 -0600 (MDT) [thread overview]
Message-ID: <1929.69.2.248.210.1214865588.squirrel@webmail.wolfmountaingroup.com> (raw)
In-Reply-To: <48614755.5080001@zytor.com>
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 across it on Windows Vista, 2003, and 2008 systems running
ForenFS on Windows that may be using dual boot with Linux or vmware:
#define PARTITION_FORENFS_GUID \
EFI_GUID(0x83968a41, 0x5fe6, 0x4f9e, \
0x91, 0x11, 0x52, 0xcf, 0x82, 0x8c, 0x51, 0x0a)
As per Peter Anvin's suggestion, uuidgen -r was used to regenerate the
uuid value for the Forensic Filesystem and I have updated the Windows code
base to reflect this change. As per Lennart Sorensen's suggestion, the
FS name has been changed to "ForenFS" to avoid yet another driver named
"ffs".
The following patches, utilities, etc. are being posted to support Linux
accessing these partitions under EFI GPT.
ftp://ftp.wolfmountaingroup.org/pub/parted/parted-1.8.8-forenfs-06-30-08.patch
ftp://ftp.wolfmountaingroup.org/pub/parted/parted-1.8.8-forenfs.tar.gz
ftp://ftp.wolfmountaingroup.org/pub/parted/parted-1.8.8.tar.gz
EFI GPT changes to Linux to detect these partitions are in the attached patch
ftp://ftp.wolfmountaingroup.org/pub/forenfs/forenfs-2.6.18-el5-06-30-08.patch
Jeffrey Vernon Merkey
prev parent reply other threads:[~2008-06-30 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 19:22 Forensic File System GUID Linux/Windows 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
2008-06-30 22:39 ` jmerkey [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=1929.69.2.248.210.1214865588.squirrel@webmail.wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.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
all inboxes | Powered by JetHome®