From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: new tool: blktool
Date: Sun, 15 Aug 2004 18:07:37 -0400 [thread overview]
Message-ID: <411FDEA9.2010802@pobox.com> (raw)
In-Reply-To: <1092603321.18410.5.camel@localhost.localdomain>
Alan Cox wrote:
> On Sul, 2004-08-15 at 22:36, Jeff Garzik wrote:
>
>> $ hdparm -c1 /dev/hda
>> becomes
>> $ blktool /dev/hda pio-data 32-bit
>
>
> So you've replaced hdparm's weird but unixish command line with an
> even more demented non linuxish one that doesn't handle regexps for
> drive names ?
>
> Whatever happened to
>
> blktool /dev/hda --pio-data=32
Yep, it's more like ethtool(8) or cvs(1) in its syntax. There is big
difference in usability (for me anyway) between "command [options]..."
and an unordered list of --args. Especially as the list of commands
grows longer. It provides more structure.
Each command can have options, --foo-bar=baz if you like, I suppose.
Jeff
next prev parent reply other threads:[~2004-08-15 22:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 21:36 new tool: blktool Jeff Garzik
2004-08-15 20:55 ` Alan Cox
2004-08-15 22:07 ` Jeff Garzik [this message]
2004-08-15 22:18 ` David Ford
2004-08-15 22:22 ` Anton Starikov
2004-08-15 22:40 ` Jeff Garzik
2004-08-15 23:00 ` Anton Starikov
2004-08-15 23:27 ` Mark Lord
2004-08-15 23:34 ` Mark Lord
2004-08-15 23:44 ` Jeff Garzik
2004-08-15 23:36 ` Jeff Garzik
2004-08-16 2:36 ` Mark Lord
2004-08-16 16:53 ` Jeff Garzik
2004-08-19 15:03 ` Mark Lord
2004-08-19 15:51 ` Bartlomiej Zolnierkiewicz
2004-08-19 17:44 ` Mark Lord
2004-08-19 17:50 ` Jeff Garzik
2004-08-19 17:57 ` Jeff Garzik
2004-08-19 18:01 ` Mark Lord
2004-08-19 18:04 ` Mark Lord
2004-08-19 18:12 ` Jeff Garzik
2004-08-19 18:42 ` Mark Lord
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=411FDEA9.2010802@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).