From: "Sandro Steger" <stegersandro@web.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM Specifications
Date: Sun, 7 Oct 2007 18:07:42 +0200 [thread overview]
Message-ID: <000001c808fc$31cfc560$02b2a8c0@sandropc> (raw)
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
I try to write a LVM driver for Windows, because I haven’t found a tool
which is able to mount LVM devices. Unfortunately, I haven’t found documents
with details on the binary structure of LVM devices, expected behaviour or
encoding. I admit I haven’t taken a look into the original source code.
That’s why I can’t estimate the effort writing a new driver (and if I have
to a document on its structure).
If someone has some useful information on its exact functionality please let
me know.
Best regards,
Sandro Steger
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.488 / Virus Database: 269.14.3/1054 - Release Date: 06.10.2007
19:12
[-- Attachment #2: Type: text/html, Size: 4685 bytes --]
next reply other threads:[~2007-10-07 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-07 16:07 Sandro Steger [this message]
2007-10-07 16:26 ` [linux-lvm] LVM Specifications Alasdair G Kergon
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='000001c808fc$31cfc560$02b2a8c0@sandropc' \
--to=stegersandro@web.de \
--cc=linux-lvm@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).