From: Michael Tokarev <mjt@tls.msk.ru>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Writing forward compatible applications using /proc
Date: Mon, 13 Aug 2001 23:44:02 +0400 [thread overview]
Message-ID: <3B782E02.B5DB2FC8@tls.msk.ru> (raw)
In-Reply-To: 20010813161301.B6466@uk.sistina.com
Alasdair G Kergon wrote:
>
[]
> In the 'experimental' branch each tool has been converted into a
> function and they have all been linked into a single 'lvm'
> binary. This binary takes lvm commands from standard input
> and processes them. Or it can be invoked with argv[0] set to
> the name of an existing tool (eg 'ln lvm pvcreate') and then it
> will behave as that tool. There are no plans to change existing
> command line arguments etc. However, in the interests of
> achieving consistency between the tools and making it easy to
> handle their output reliably, there are likely to be minor
> changes to the output formats, error codes, signal-handling etc.
Wow, great! No more tons of tiny executables! Wow! Looks
very good. Just like `cvs' now -- "cvs co", "cvs add" etc...
Well, ok, but one little question/suggestion: why not have
*some* tools instead of one (a step back? no): pvm for physycal
volumes, lvg for volume groups and lvm for logical volumes?
This seems to be logical...
Anyway, this is exactly a direction I always wanted to ask and/or
point to, but I remember some words somewhere on Sistina? Or
old LVM homepage (where it was?) ? that such mergeing will not
happen because of something. (It may be even lvm FAQ or HOWTO).
Unfortunately, I don't remember reasons behind that.
Regards,
Michael.
next prev parent reply other threads:[~2001-08-13 19:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 3:57 [linux-lvm] Writing forward compatible applications using /proc Jason Tackaberry
2001-08-12 13:54 ` José Luis Domingo López
2001-08-12 15:38 ` Jason Tackaberry
2001-08-12 18:39 ` José Luis Domingo López
2001-08-12 16:39 ` Steven Lembark
2001-08-13 1:55 ` Paul Jakma
2001-08-12 17:10 ` Eric M. Hopper
2001-08-12 22:21 ` José Luis Domingo López
2001-08-12 20:46 ` Ragnar Kjørstad
2001-08-12 22:35 ` Wichert Akkerman
2001-08-12 20:21 ` toon
2001-08-12 19:07 ` Joe Thornber
2001-08-12 19:13 ` Steven Lembark
2001-08-12 19:26 ` Joe Thornber
2001-08-12 19:51 ` Jason Tackaberry
2001-08-12 20:16 ` Ragnar Kjørstad
2001-08-13 9:08 ` Joe Thornber
2001-08-13 11:27 ` Wichert Akkerman
2001-08-13 12:48 ` Terje Kvernes
2001-08-13 23:49 ` Ragnar Kjørstad
2001-08-14 13:36 ` Heinz J . Mauelshagen
2001-08-14 0:31 ` Nathan Scott
2001-08-14 13:33 ` Heinz J . Mauelshagen
2001-08-13 15:13 ` Alasdair G Kergon
2001-08-13 17:58 ` Jason Tackaberry
2001-08-13 19:44 ` Michael Tokarev [this message]
2001-08-13 19:49 ` Wichert Akkerman
2001-08-13 20:18 ` Goetz Bock
2001-08-13 20:47 ` Joe Thornber
2001-08-13 20:31 ` Joe Thornber
2001-08-14 3:04 ` Mark van Walraven
2001-08-14 8:14 ` Joe Thornber
2001-08-14 17:50 ` Ragnar Kjørstad
2001-08-15 8:58 ` Heinz J . Mauelshagen
2001-08-13 9:10 ` Terje Kvernes
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=3B782E02.B5DB2FC8@tls.msk.ru \
--to=mjt@tls.msk.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.