public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] LVM reimplementation ready for beta testing
Date: Tue, 5 Feb 2002 11:18:37 +0100	[thread overview]
Message-ID: <20020205111837.A1571@sistina.com> (raw)
In-Reply-To: <20020201100303.A14415@sistina.com> <Pine.LNX.3.96.1020204171446.31056B-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1020204171446.31056B-100000@gatekeeper.tmr.com>; from davidsen@tmr.com on Mon, Feb 04, 2002 at 05:16:27PM -0500

On Mon, Feb 04, 2002 at 05:16:27PM -0500, Bill Davidsen wrote:
> On Fri, 1 Feb 2002, Heinz J . Mauelshagen wrote:
> 
> > The LVM2 sofware no longer uses a particular driver which is just
> > usable for its own purpose.
> > It rather accesses a different, so-called 'device-mapper' driver, which
> > implements a generic volume management service for the Linux kernel by
> > supporting arbitray mappings of address ranges to underlying block devices.
> > Because this is a generic service rather than an application within the kernel,
> > it is open to be used by multiple LVM implementations (for eg. EVMS could be
> > ported to use it :-)
> 
> Interesting concept, but something like the "smitZ" interface to RAID and
> sizing would be really nice to reduce training effort. Since IBM is
> pushing Linux, take this as a HINT.

Hint is to user interface only or to in kernel ones as well?

> 
> -- 
> bill davidsen <davidsen@tmr.com>
>   CTO, TMR Associates, Inc
> Doing interesting things with little computers since 1979.

-- 

Regards,
Heinz    -- The LVM Guy --

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-02-05 10:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-30 20:22 [ANNOUNCE] LVM reimplementation ready for beta testing Joe Thornber
2002-01-30 21:54 ` [lvm-devel] " Andreas Dilger
2002-01-30 22:03   ` Jim McDonald
2002-01-30 23:09   ` Joe Thornber
2002-01-31  1:01 ` christophe barbé
2002-01-31 12:45   ` Heinz J . Mauelshagen
2002-01-31 18:42     ` Jeff Garzik
2002-02-01  9:03       ` Heinz J . Mauelshagen
2002-02-04 22:16         ` Bill Davidsen
2002-02-05 10:18           ` Heinz J . Mauelshagen [this message]
2002-01-31  1:53 ` Daniel Phillips
  -- strict thread matches above, loose matches on Subject: below --
2002-01-31 19:52 [linux-lvm] Re: [lvm-devel] " Steve Pratt
2002-01-31 12:52 ` Joe Thornber
2002-02-01  9:55   ` [Evms-devel] " Arjan van de Ven
2002-01-31 13:09     ` Joe Thornber
2002-02-01 10:12       ` Arjan van de Ven
2002-01-31 13:35         ` Joe Thornber
2002-02-01 14:44         ` Alan Cox

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=20020205111837.A1571@sistina.com \
    --to=mauelshagen@sistina.com \
    --cc=davidsen@tmr.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