Re: sg utils sg_io -i 0x24 -y "12 00:00:00 24 00"

[Pat LaVarre <p.lavarre@ieee.org>]

> > > Perhaps we should be looking at 
> > > implementing camcontrol in Linux.
> > 
> > Implementing, yes.  Copying, no.
> > I have a series of arguments, ...

Or maybe not so very many.  Mostly, I find camcontrol disappointingly
large.  

> > > Unix Man Page For 8 camcontrol
> > > http://www.svbug.com/cgi-bin/man.cgi?comd=8+camcontrol
> 
> I think arg parsing is an issue.
> 
> I see the camcontrol man page includes such off-putting ...

Personally I think even my own plscsi/ is too large.  I'm hoping gccscsi
by contrast is small enough to demo kernel trouble (and proposed plug 'n
play patches).

For example, offline recently I thought I saw someone report that a
cdb-unexpectedly-short doesn't pass thru 2.6.0 to usb mass.  Seeing
plscsi say that doesn't tell us the kernel has an issue there: we have
to ask, and we cannot easily answer, does plscsi have an issue there.

I care most here about transparency: easily establishing more confidence
that I know what I asked the kernel than if I had written an ad hoc test
program

I figure I can achieve transparency by remembering reuse proves my
general test program free of the simple errors I might make in an ad hoc
test program, but I have to keep my general test program small enough to
let me easily read over, step thru, maybe even copy-paste-edit out, just
the lines of code that I need.

Pat LaVarre