[EMAIL PROTECTED] wrote: > On Mon, 15 Oct 2007, Stefan Richter wrote: >> Low-level networking drivers suggest a default interface name (per >> interface or as a template like eth%d into which the networking core >> inserts a lowest spare number). ... >> Could low-level SCSI drivers provide similar name templates which give a >> hint on the transport involved? ... > one other option that could be considered (and I do realize I'm bringing > up flame-bait here) is that drivers that have fixed addresses could > offer up a device name that include that address. ...
That's already implemented. :-) Transport drivers expose transport specific information in sysfs; udev scripts examine it and create by-id and by-path symlinks to device files of HDDs. Not everybody agrees, but many think that it's sensible to implement just mechanism in kernel and leave policy to userspace. My suggestion and the default network interface names already violate this principle to a degree, but it can still be implemented in a transport independent way, and userspace can continue to create whatever names the user needs. -- Stefan Richter -=====-=-=== =-=- =---- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
