linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Cc: Jens Axboe <axboe@suse.de>
Subject: blktool git repo created
Date: Tue, 25 Oct 2005 15:25:00 -0400	[thread overview]
Message-ID: <435E868C.3010404@pobox.com> (raw)


After sitting around in a non-public subversion repo for far too long, 
I've stuffed the latest blktool source code into a git repository.  As 
soon as it finished mirroring, it will be available at

rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/blktool.git

The ostensible home page of blktool is 
http://sourceforge.net/projects/gkernel/


What is it?

blktool is a multi-purpose tool that aims to a common place to 
management common block concepts, across a wide variety of hardware.

For example, rather than having to learn and use different tools for ATA 
or SCSI or I2O for the concept of "suspend", in the future one will 
simply do "blktool /dev/foo suspend" and it will work, regardless of 
what type of device it is.

I'm hoping that, as high level patterns emerge in storage, that blktool 
can grow to meet these needs.  For example, I would love to see blktool 
grow support for the various hardware RAID controllers out there, so 
that the admin need not learn a new raid management util for each 
controller.  James Bottomley's scsi-independent RAID class should help 
in this endeavor, as it matures.

	Jeff




             reply	other threads:[~2005-10-25 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 19:25 Jeff Garzik [this message]
2005-10-26 15:37 ` blktool git repo created Velu Erwan

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=435E868C.3010404@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=axboe@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@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).