Re: CD writing in future Linux (stirring up a hornets' nest)

From: Bodo Eggert
Date: Sun Feb 12 2006 - 11:02:37 EST


Joerg Schilling <schilling@xxxxxxxxxxxxxxxxxxx> wrote:
> Matthias Andree <matthias.andree@xxxxxx> wrote:

>> > > Nonsense. The b,t,l addresses are NOT stable (at least for transports
>> >
>> > Dou you like to verify that you have no clue on SCSI?
>>
>> How does, for instance, libscg make sure that the b,t,l mappings are
>> hotplug invariant?
>>
>> How does libscg make sure that two external writers, say USB, retain
>> their b,t,l mappings if both are unplugged and then replugged in reverse
>> order, perhaps into different USB hubs?
>
> Well, this is a deficit of the Linux kernel - not libscg.
>
> If you are unhappy with Hot plug support on Linux, I recommend you to
> check Solaris.

I see only support for 16*16*8=2048 devices in scsi-sun.c. Therefore you need
at most 2049 devices to have no possibility for stable device<->b,t,l
relation. Asume 2048 devices had been plugged into USB, so that you have the
mapping 0,0,0 -> yellow burner .. 15,15,7 -> purple burner. If you reuse any
of these IDs, also plugging in the corresponding device would result in a
non-stable ID. (One broken device with serial number = `dd if=/dev/random`
will do the trick, too.)

So if you can't create a stable mapping using b,t,l, why should you bother
trying and mislead your users into asuming a stable mapping? And why should
you impose a btl mapping if it's possible to allow naming the device whatever
the user likes, causing the number of stable device names to be limited only
by it's lifetime?

The only things you need is a list of devices and a way to map a unique ID
to a device name. I posted scripts that will so that.

--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/