From: Jeff Garzik <jgarzik@pobox.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: new tool: blktool
Date: Sun, 15 Aug 2004 17:36:04 -0400 [thread overview]
Message-ID: <411FD744.2090308@pobox.com> (raw)
I just posted "blktool" on my SF page,
http://sourceforge.net/projects/gkernel/
and in BitKeeper at
bk://gkernel.bkbits.net/blktool
blktool aims to be an easier to use, and more generic version of the
existing utility 'hdparm'. For example,
$ hdparm -c1 /dev/hda
becomes
$ blktool /dev/hda pio-data 32-bit
and
$ hdparm -L0 /dev/hda
becomes
$ blktool /dev/hda media unlock
The utility is currently still fairly specific to IDE devices (as hdparm
is), but that will change in the coming weeks as SCSI, I2O, and possibly
some bits of hardware RAID control are added.
The audience for this application, like hdparm, is fairly narrow,
specific to people who tweak their storage devices and _know what they
are doing_. Improper use of this tool, like hdparm, can turn your disk
into a doorstop.
Jeff
next reply other threads:[~2004-08-15 21:36 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 21:36 Jeff Garzik [this message]
2004-08-15 20:55 ` new tool: blktool Alan Cox
2004-08-15 22:07 ` Jeff Garzik
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=411FD744.2090308@pobox.com \
--to=jgarzik@pobox.com \
--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).