public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Jason <unleet@qwest.net>
To: speakup@braille.uwo.ca
Subject: Re: drive assignments
Date: Wed, 21 Nov 2001 15:47:42 -0700	[thread overview]
Message-ID: <01112115474200.02842@lightstar> (raw)
In-Reply-To: <Pine.WNT.4.40.0111210505140.-324691@steve.holmesgrown.com>

> /hdc is primary drive on the second IDE controler, /hdd would be the slave
> drive on the second controler. See the pattern? The same pattern would
> hold for SCSI drives however, I'm not sure if you would be limitted to two
> drives per SCSI controler. I don't have any SCSI hard drives here so not
> very familiar with SCSI protocols.
>
SCSI basically works the same way. The only difference is that the drives are 
"lettered" in the order they are detected, starting with controller 1, ID 0, 
LUN 0. So /dev/sda is the device with the lowest ID number on the first 
controller, regardless of the actual ID number. There is one caveat, the 
actual SCSI controller, while it has an ID number is not given a device node 
(though this may bi different if your kernel includes the "devfs" package.

Also, as a feature, there are /dev/scd? devices, for CDROM, CD-R(W) and DVD 
drives on your SCSI busses, these are numbered in the order detected starting 
with 0, otherwise the same way hard drives are. These are in addition to, not 
in place of, the /dev/sd? entries. There are also "SCSI Generics" available, 
these are listed as /dev/sg?, and again, numbered in the order detected, 
atarting with 0 (seeing a pattern here?). SCSI generics include things such 
as SCSI-based scanners, CD-R and CD-RW drives and things such as that (yes, 
this can mean that a single CD drive will be listed three times if it's 
recordable, or twice if not).

If anyone actually needed that information, I hope it helped, if not, I hope 
it was at least interesting ;-)






  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Glenn Ervin
 ` Steve Holmes
   ` Jason [this message]
   ` randy turner
     ` Gregory Nowak
     ` Amanda Lee
       ` Jason
       ` Thomas Ward
     [not found]     ` <Pine.BSF.4.42.0111231021140.46967-100000@server1.shellworl d.net>
       ` Tony Baechler

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=01112115474200.02842@lightstar \
    --to=unleet@qwest.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).