Re: Linux not adhering to BIOS Drive boot order?

[Tim Fletcher <tim@parrswood.manchester.sch.uk>]

> > This is when devfs comes into its own, as the disks are refered to by
> > their device/controller id not by the /dev/sd{a,b,c,etc} numbering, hence
> > when one fails the others don't change. Also I think the kernel autodetect
> > code for scsi devices will deal with this case, but I'm not sure.
>
> 'would be great to use driver name, e.g. something like
> /dev/scsi/advansys/... (I don't remember devfs naming scheme)

Then you are back to the arguement about should the naming be based on the
function of the device (scsi0,1,2 / eth0,1,2) or based on the hardware
(aic7xxx0,1,2 advansys0,1,2 / tulip0,1,2 eepro0,1,2). *BSD uses this
naming scheme for its ethernet interfaces, not sure about its scsi thou.

I prefer the functional naming scheme (scsi0 / eth0) as I can change the
hardware in a machine and not change anything in the init scripts,
assuming the driver is in kernel or if not I only need to change the line
/etc/modules.conf.

-- 
   Tim Fletcher - Network manager   .~.
                                    /V\      L   I   N   U   X
     nightshade@solanum.net        // \\  >Don't fear the penguin<
tim@parrswood.manchester.sch.uk   /(   )\
 irc: Night-Shade on quakenet      ^^-^^

"I am Homer of Borg.  Prepare to Oooh! Doughnuts!"

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/