public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <steve@gw.chygwyn.com>
To: adilger@turbolabs.com (Andreas Dilger)
Cc: hch@ns.caldera.de (Christoph Hellwig), linux-kernel@vger.kernel.org
Subject: Re: IBMs LVM?
Date: Thu, 20 Sep 2001 17:12:47 +0100 (BST)	[thread overview]
Message-ID: <200109201612.RAA14175@gw.chygwyn.com> (raw)
In-Reply-To: <20010920100557.Z14526@turbolinux.com> from "Andreas Dilger" at Sep 20, 2001 10:05:57 AM

Hi,

Just a quick update on whats going on with the new LVM stuff.... Joe had
announced a release a little while ago with some initial code which he
has been working on for a while. I've been continuing that (along with
various other Sistina people doing testing) to make the initial code more
robust and finalise the kernel/user interface.

I hope that by the end of next week we'll have the new filesystem based
interface finished and tested at which point we'll announce it again as
a suitable time for interested parties to have a look. Feel free to check
out the CVS in the mean time though :-)

In order for the driver to be useful, we need code to read metadata from
disks and write suitable tables to drive the device mapper. We are already
working on this next step but will focus more upon it when the driver is
finished.

Please send any comments or patches to the linux-lvm list,

Thanks,

Steve.

> 
> On Sep 20, 2001  13:57 +0200, Christoph Hellwig wrote:
> > Anyway, I will get my design for improved block device stacking and unified
> > partition discovery back from the attic and implement a protopy ontop of
> > the bio patchset.  I'll Cc my ennouncement to evms-devel, you're free to
> > layer ontop if you want.
> 
> Just FYI (in case you haven't seen it) the LVM folks are working on
> something like this in their "LVM2" repository.  I've been seeing
> the CVS commit messages, but have not actually taken a look at the
> code yet, so I can't comment on it but it may save you some effort.
> 
> Cheers, Andreas
> --
> Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
>                  \  would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2001-09-20 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200109142155.f8ELtVi03827@shay.ecn.purdue.edu>
2001-09-20 11:57 ` IBMs LVM? Christoph Hellwig
2001-09-20 16:05   ` Andreas Dilger
2001-09-20 16:12     ` Steven Whitehouse [this message]
2001-09-11 14:53 IBMs LVM ? David Balazic
2001-09-11 15:26 ` Christoph Hellwig
2001-09-11 17:57   ` Andreas Dilger
2001-09-11 18:06     ` Christoph Hellwig
2001-09-11 19:15       ` Andreas Dilger
2001-09-11 19:57         ` Christoph Hellwig
2001-09-27 19:36       ` Jes Sorensen
2001-09-27 23:03         ` 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=200109201612.RAA14175@gw.chygwyn.com \
    --to=steve@gw.chygwyn.com \
    --cc=Steve@ChyGwyn.com \
    --cc=adilger@turbolabs.com \
    --cc=hch@ns.caldera.de \
    --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