public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Dake <sdake@mvista.com>
To: devnetfs <devnetfs@yahoo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: dev nodes assignement ?
Date: Wed, 29 Jan 2003 09:46:59 -0700	[thread overview]
Message-ID: <3E380583.4090609@mvista.com> (raw)
In-Reply-To: <20030129110004.22210.qmail@web20421.mail.yahoo.com>

first come first serve.  devfs defines the device nodes using access 
path (host/channel/id/lun) which is a bit more usable for hotswap 
situtations, assuming your id's don't change.

Thanks
-steve

devnetfs wrote:

>Hello,
>
>Is /dev/sdX scsi dev node assignment based *only* on the pci-slot
>the HBA's are in? or also upon the order in which the LLDD is loaded?
>
>In other words does the mid-layer scan+make-a-list of all HBA's on
>the system (and thereby assigning the /dev name) and then when a LLDD
>is loaded, tells it the HBA-list? 
>OR
>Does each LLDD does a pci-scan and assign /dev name for HBA's that it
>can handle -- in which case the order of LLDD getting loaded is also
>important in deciding the /dev/sdX name.
>
>Please clarify, 
>Thanks in advance
>A.
>
>__________________________________________________
>Do you Yahoo!?
>Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
>http://mailplus.yahoo.com
>-
>To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>
>  
>


  reply	other threads:[~2003-01-29 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 11:00 dev nodes assignement ? devnetfs
2003-01-29 16:46 ` Steven Dake [this message]
2003-01-29 17:59 ` Bryan Henderson
2003-01-30  5:28   ` devnetfs

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=3E380583.4090609@mvista.com \
    --to=sdake@mvista.com \
    --cc=devnetfs@yahoo.com \
    --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