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

>>>>
>>> But you need to open the correct /dev/sg[0-9] too, don't you?
>>> (otherwise cdrecord would set the jukebox on fire)
>> 
>> This is why the mapping engine is in the Linux adoption part of
>> libscg. It maps the non-stable device <-> /dev/sg* relation to a
>> stable b,t,l address.
>
>Well, the b,t,l mapping, judging from libscg code, is as stable as the
>ordering of the device nodes themselves, so it is not clear what the
>advantage would be other than getting a uniform and artificial b,t,l mapping.
>
>If hotplugging shuffles /dev/sg* between running $APPLICATION -scanbus and
>$APPLICATION -dowhatever, the b,t,l will change as well.
>

Don't interrupt my (trick) thread (as explained before in private).
Thank you.



Jan Engelhardt
-- 
-
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/

---

• Follow-Ups:
  • Re: CD writing in future Linux
    • From: Jan Engelhardt <[email protected]>

• References:
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Luke-Jr <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
    • From: Peter Read <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Matthias Andree <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: "Jim Crilly" <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: "Jim Crilly" <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: "Jim Crilly" <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: "Jim Crilly" <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Jan Engelhardt <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Jan Engelhardt <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Joerg Schilling <[email protected]>
  • Re: CD writing in future Linux (stirring up a hornets' nest)
    • From: Matthias Andree <[email protected]>

• Prev by Date: Re: CD writing in future Linux (stirring up a hornets' nest)
• Next by Date: Re: [PATCH] percpu data: only iterate over possible CPUs
• Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
• Next by thread: Re: CD writing in future Linux
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]