From: Rob Landley <rob@landley.net>
To: dougg@torque.net
Cc: James Bottomley <James.Bottomley@steeleye.com>,
linux-scsi@vger.kernel.org
Subject: Re: Some quick scsi documentation questions:
Date: Thu, 2 Aug 2007 20:39:02 -0400 [thread overview]
Message-ID: <200708022039.02387.rob@landley.net> (raw)
In-Reply-To: <46B2256A.3070902@torque.net>
On Thursday 02 August 2007 2:41:46 pm Douglas Gilbert wrote:
> > I'm still trying to figure what the other options _are_.
> >
> >> James
> >
> > Rob
>
> Interesting discussion.
I'm trying to pull together documentation of the scsi layer and link it into
the index I'm trying to put up at http://kernel.org/doc, but I'm working
under the handicap of never having used scsi hardware.
Technically I still don't own any scsi hardware except a scanner I've never
gotten to work, but the scsi layer has now eaten my ide devices, it's
handling my new sata hard drive which makes sas look even more hilarious than
it did in 2005, and my vague impression is that the bsg patch turns my
intended-as-joke question to James at OLS (so when do ramdisks start going
through the scsi layer?) into a potential reality. (Not that I pretend to
understand the bsg code.)
I also didn't understand the rest of your message well enough to comment on
any of it (does my USB key have a LUN? The scsi layer grabbed it...)
> ** As noted above "all" is an overestimate. The pass-through
> only gets to map to devices that the sysfs/udev mess decides
> are relevant.
Don't get me started on udev. As far as I can tell, Greg KH disagrees with me
on every topic I've ever raised with him...
> Doug Gilbert
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
prev parent reply other threads:[~2007-08-03 0:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200707252328.28981.rob@landley.net>
[not found] ` <1185455711.3501.46.camel@localhost.localdomain>
2007-07-27 21:29 ` Some quick scsi documentation questions: Rob Landley
2007-08-02 18:41 ` Douglas Gilbert
2007-08-02 21:19 ` Stefan Richter
2007-08-03 0:55 ` Rob Landley
2007-08-03 10:43 ` Stefan Richter
2007-08-03 21:11 ` Rob Landley
2007-08-04 0:08 ` Stefan Richter
2007-08-04 0:35 ` Stefan Richter
2007-08-05 16:50 ` Douglas Gilbert
2007-08-06 16:29 ` Rob Landley
2007-08-06 18:30 ` Stefan Richter
2007-08-02 21:39 ` Stefan Richter
2007-08-03 1:12 ` Rob Landley
2007-08-03 8:15 ` Stefan Richter
2007-08-03 19:07 ` Rob Landley
2007-08-03 19:37 ` Stefan Richter
2007-08-03 21:39 ` Rob Landley
2007-08-03 0:39 ` Rob Landley [this message]
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=200708022039.02387.rob@landley.net \
--to=rob@landley.net \
--cc=James.Bottomley@steeleye.com \
--cc=dougg@torque.net \
--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