From: david@lang.hm
To: phillips@phunq.net
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [RFC] An alternative interface to device mapper
Date: Wed, 5 Mar 2008 18:31:00 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.1.00.0803051830290.14137@asgard.lang.hm> (raw)
forgive the lack of threading, I missed this yesterday and just found this via
the LWN article.
I like the general approach that you are taking of simplifying the interface,
however in your interest of making it easy to write C code for you are making
the new interface difficult to script for. is it really that painful to to make
everything file based so that it can be scripted as well?
frankly, most sysadmins do a lot of scripting and almost no C coding, so while
a nice C interface is useful for creating tools, a good scripting interface is
critical for good, flexible use by sysadmins.
David Lang
next reply other threads:[~2008-03-06 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 2:31 david [this message]
2008-03-06 4:49 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2008-03-05 9:29 Daniel Phillips
2008-03-05 16:39 ` Jonathan Corbet
2008-03-05 19:23 ` Daniel Phillips
2008-03-08 11:38 ` Pavel Machek
2008-03-08 12:06 ` Daniel Phillips
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=alpine.DEB.1.00.0803051830290.14137@asgard.lang.hm \
--to=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@phunq.net \
/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®