On 08/24/05 16:42, Patrick Mansfield wrote: >>And where does _it_ get it? > > > You can write a program to supply it :) Some of those would depend on the transport and I'd like _transport_ things to "die" at _transport_ layer. The transport layer would add as much as possible, then SCSI Core, then sd then the block layer, then whoever is on top. Eventually you'd have a bunch of strings, which are labels, with varied but ASCII contents. >>Hey Patrick, is there a point to this thread? > > > Yes, at this juncture a simplified explanation about udev rules. Please go ahead. >>If you have an idea, please go ahead and share and/or implement it. >>If you're unclear on something please ask it directly. > > I thought you were asking for details about udev ... your question was > rather ambiguous. Never did. I was at a much, _much_, lower level. Anyway, this is a rather important issue which vendors want to have. In fact it's very important for them. Let's take it up again in several days, Luben - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
