From: Benoit SERRA <bs@infologic.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] nagging about the LVM usage survey
Date: Thu, 11 Jan 2001 15:56:54 +0100 [thread overview]
Message-ID: <3A5DC9B5.15B3C7DA@infologic.fr> (raw)
In-Reply-To: 20010111083114.A381363@brule.borg
Matthew O'Keefe a �crit :
>
> If more LVM users and developers fill these out and tell
> us what they are doing with LVM, and what their immediate needs are,
> we can better understand where to go in the future.
I think that the immediate needs of most of the people is a working
vgextend
It's the most important feature of LVM, and it doesn't work !
Great !
next prev parent reply other threads:[~2001-01-11 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 14:31 [linux-lvm] nagging about the LVM usage survey Matthew O'Keefe
2001-01-11 14:38 ` Christoph Hellwig
2001-01-11 15:14 ` Michael J. Declerck
2001-01-11 17:13 ` Heinz J. Mauelshagen
2001-01-11 16:21 ` Michael E Brown
2001-01-11 14:56 ` Benoit SERRA [this message]
2001-01-11 17:20 ` Heinz J. Mauelshagen
2001-01-12 7:15 ` Benoit SERRA
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 18:47 Daniel Mitzlaff
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=3A5DC9B5.15B3C7DA@infologic.fr \
--to=bs@infologic.fr \
--cc=linux-lvm@sistina.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