Linux LVM users
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: tayyeb.hagalwadi@patni.com,
	LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Regarding info about Device mapper.
Date: Tue, 08 Feb 2005 10:27:02 +1300	[thread overview]
Message-ID: <4207DD26.9050603@vilain.net> (raw)
In-Reply-To: <021301c51de4$4deeece0$7c051aac@pcp42078>

Tayyeb Hagalwadi(Patni) wrote:
>   This is regarding the information about Device mapper. Could you please
> provide documents, white papers or  related URL regarding the Device mapper
> for LVM2. And could u explain, what are the feature of device mapper in LVM
> 1, and what extra feature are we going to achieve  in LVM2.

Have a look at

http://www.google.com/search?q=device+mapper+lvm

-- 
Sam Vilain, sam /\T vilain |><>T net, PGP key ID: 0x05B52F13
(include my PGP key ID in personal replies to avoid spam filtering)

      reply	other threads:[~2005-02-07 21:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07  8:54 [linux-lvm] Regarding info about Device mapper Tayyeb Hagalwadi(Patni)
2005-02-07 21:27 ` Sam Vilain [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=4207DD26.9050603@vilain.net \
    --to=sam@vilain.net \
    --cc=linux-lvm@redhat.com \
    --cc=tayyeb.hagalwadi@patni.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