Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: dougg@torque.net
Cc: linux-scsi@vger.kernel.org
Subject: Re: /dev/hd* in sg_scan
Date: 29 Oct 2003 10:16:03 -0700	[thread overview]
Message-ID: <1067447763.13824.26.camel@patehci2> (raw)
In-Reply-To: <3F9F4393.5060602@torque.net>

> Sg3_utils' sg_map and sg_scan for lk 2.6 still have me
> thinking ... waiting ...
> sg .. to use cdevs (char ... sysfs ... > 256 minors)
> latest freeze ... scsi tape robots and enclosures ...

Prompt & cogent as usual, thank you.

> >http://tldp.org/HOWTO/SCSI-Generic-HOWTO/open.html
> > >... O_NONBLOCK ... ignored by ioctl(SG_IO)
> > 
> > As of 2.6, in fact we now need O_NONBLOCK if we want open O_RDONLY to
> > let us talk SG_IO to a DVD/CD with no disk present?  Also we discard the
> > history of passing thru less commands for O_RDONLY than for O_RDWR?

I guess, but I do not know.

> With either /dev/hd and /dev/sd ...

Thanks for hinting at /dev/sd$v or /dev/sd$v$n.

I see /dev/scd$n rejects SG_IO.

So far I have only seen /dev/hd$v and /dev/sg$n work.

> With either /dev/hd and /dev/sd you may soon want to find
> out (or probe) before making any assumptions:
>    - what protocol are you using (e.g. ATA, ATAPI, SCSI)
>    - what transport (e.g. pATA, sATA, SPI, FC, USB, SAS)

I see you hint darkly ... at what I do not know.

Why am I going to want to discover protocol & transport?

How will I do so?

> currently I'm rewriting sginfo).

Thank you.

I trust you won't let me slow you down with my ignorant questions.

Pat LaVarre



      reply	other threads:[~2003-10-29 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28  0:09 /dev/hd* in sg_scan Pat LaVarre
2003-10-29  4:35 ` Douglas Gilbert
2003-10-29 17:16   ` Pat LaVarre [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=1067447763.13824.26.camel@patehci2 \
    --to=p.lavarre@ieee.org \
    --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