No, that defeats the searching scheme. What you want is:
- no driver: no directory
- driver loaded: directory with one entry per piece of hardware
- opendir ("/dev/ide/cd"): load driver.
Putting in symlinks like in your scheme requires a symlink for every
possible entry that might ever exist if you installed an array of
CD-ROMs. That gets us back to pre-devfs days.
> I really like the idea of solaris having this for scsi0 id0 lun0 partition0:
> /dev/dsk/c0t0d0s0 I just don't like the letters they used.
>
> Above where I said bus[0-9], forget it, it would be too hard to do that and
> it would be easier to have c0 and c1 being controller 0 bus 0 and controller
> 0 bus 1. Whoever thought of /dev/sdb being 2nd found scsi hard drive should
> be shot (IMO) I thought about running that user space thing, but I don't
> like the idea of it since the rootfs is mounted via /dev/sdx by the kernel.
> This is the exact reason I put my hard drives as close to id0 as possible
> and all my other drives as close to id6 as possible. if my cd changer goes
> out, my burner goes from scd5 to scd0.. ouch! I only have 1 tape drive in
> this machine so that I'm not TOO worried about. But I thought about this,
> if I ever get a wide card, there's no way I'm putting a wide hdd on an id
> less than 8. This leaves enough room for all my narrow drives
>
> Anyway, I don't feel it would be right to yank the /dev/sda out of the way
> for people who like it, but it would be a nice config option... Atleast
> that would suit the people who love /dev/s{cd,da,t} and for those who can't
> stand it.. Me I can live with it, but I don't like it... Where's my choise
> =)
Have you actually looked at the patch or at least the documentation?
The location-based naming scheme you want is implemented in devfs. And
the old names are still there. And there are boot option to give you
choice.
It's all done. A year ago.
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/