From: Hendrik Visage <hvisage@envisage.co.za>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mike Diehl <mdiehl@dominion.dyndns.org>,
Kevin Corry <corryk@us.ibm.com>,
evms-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Evms-devel] Re: [Evms-announce] EVMS announcement
Date: Wed, 6 Nov 2002 11:34:49 +0200 [thread overview]
Message-ID: <20021106093449.GE465@hvs.envisage.co.za> (raw)
In-Reply-To: <1036542080.7386.24.camel@irongate.swansea.linux.org.uk>
On Wed, Nov 06, 2002 at 12:21:20AM +0000, Alan Cox wrote:
> On Tue, 2002-11-05 at 21:11, Mike Diehl wrote:
> > The biggest thing that EVMS had going for it was it's modular design. As I
> > understand it, EVMS could even be used to manage the current MD and LVM
> > drivers. I was looking forward to partition-level encryption, etc.
>
> Thats a seperate issue in the pile. You might want to do things like
>
> lvm2 volumes
Quick question Alan: Are you saying that EVMS can't do this ??
Hendrik
> |
> RAID-5
> / | \ \
> 4 encrypted volumes with different keys
> | | | |
> 4 NBD disk volumes over TCP
> (or 4 iSCSI volumes)
>
> 4 physical disks in different jurisdictions
>
>
> (and the physical disks or iscsi volumes might in fact be over lvm2 on
> the othe end - its all a lot more modular than just volume management at
> least at the kernel level - tools is different)
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Evms-devel mailing list
> Evms-devel@lists.sourceforge.net
> To subscribe/unsubscribe, please visit:
> https://lists.sourceforge.net/lists/listinfo/evms-devel
next prev parent reply other threads:[~2002-11-06 9:29 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 22:19 Kevin Corry
2002-11-05 21:00 ` [Evms-announce] " Mike Diehl
2002-11-05 21:11 ` Mike Diehl
2002-11-05 23:53 ` Rik van Riel
2002-11-06 0:21 ` Alan Cox
2002-11-06 9:34 ` Hendrik Visage [this message]
2002-11-06 13:55 ` [Evms-devel] " Alan Cox
2002-11-06 0:36 ` [Evms-devel] " Kevin Corry
2002-11-06 1:45 ` Mike Diehl
2002-11-06 4:48 ` Alexander Viro
2002-11-06 2:54 ` Mike Diehl
2002-11-06 13:47 ` Kevin Corry
2002-11-05 23:40 ` [Evms-announce] " Andres Salomon
2002-11-05 21:29 ` Mike Diehl
2002-11-06 0:18 ` Andrew Clausen
2002-11-06 21:33 ` Matthias Andree
2002-11-07 10:37 ` Joe Thornber
2002-11-05 23:37 ` Alan Cox
2002-11-06 0:03 ` [Evms-devel] " Eff Norwood
2002-11-06 1:13 ` Rik van Riel
2002-11-06 1:41 ` Eff Norwood
2002-11-06 1:57 ` Rik van Riel
2002-11-06 2:50 ` Alexander Viro
2002-11-06 0:05 ` James H. Cloos Jr.
2002-11-06 15:21 ` Kevin Corry
2002-11-06 0:16 ` [Evms-announce] " Lars Marowsky-Bree
2002-11-06 13:55 ` Alan Cox
2002-11-06 13:59 ` Arjan van de Ven
2002-11-06 14:24 ` Jens Axboe
2002-11-06 20:46 ` H. Peter Anvin
2002-11-06 21:21 ` Alan Cox
2002-11-06 21:58 ` H. Peter Anvin
2002-11-08 18:06 ` Alan Cox
2002-11-08 19:37 ` H. Peter Anvin
2002-11-06 15:08 ` Kevin Corry
2002-11-07 20:24 ` Christoph Hellwig
2002-11-06 1:55 [Evms-devel] Re: [Evms-announce] " Steve Pratt
2002-11-06 1:29 ` Mike Diehl
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=20021106093449.GE465@hvs.envisage.co.za \
--to=hvisage@envisage.co.za \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=corryk@us.ibm.com \
--cc=evms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mdiehl@dominion.dyndns.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
all inboxes | Powered by JetHome®