[lkml]   [2006]   [Feb]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: CD writing in future Linux (stirring up a hornets' nest)
    On Monday 13 February 2006 05:40, Joerg Schilling wrote:
    > jerome lacoste <> wrote:
    > > On 2/10/06, Joerg Schilling <> wrote:
    > > > "D. Hazelton" <> wrote:
    > > > > And does cdrecord even need libscg anymore? From having actually gone
    > > > > through your code, Joerg, I can tell you that it does serve a larger
    > > > > purpose. But at this point I have to ask - besides cdrecord and a few
    > > > > other _COMPACT_ _DISC_ writing programs, does _ANYONE_ use libscg? Is
    > > > > it ever used to access any other devices that are either SCSI or use
    > > > > a SCSI command protocol (like ATAPI)? My point there is that you
    > > > > have a wonderful library, but despite your wishes, there is no proof
    > > > > that it is ever used for anything except writing/ripping CD's.
    > > >
    > > > Name a single program (not using libscg) that implements user space
    > > > SCSI and runs on as many platforms as cdrecord/libscg does.
    > >
    > > I have 2 technical questions, and I hope that you will take the time
    > > to answer them.
    > >
    > > 1) extract from the README of the latest stable cdrtools package:
    > >
    > > Linux driver design oddities
    > > ****************************************** Although cdrecord supports to
    > > use dev=/dev/sgc, it is not recommended and it is unsupported.
    > >
    > > The /dev/sg* device mapping in Linux is not stable! Using
    > > dev=/dev/sgc in a shell script may fail after a reboot because the device
    > > you want to talk to has moved to /dev/sgd. For the proper and OS
    > > independent dev=<bus>,<tgt>,<lun> syntax read the man page of cdrecord.
    > >
    > > My understanding of that is you say to not use dev=/dev/sgc because it
    > > isn't stable. Now that you've said that bus,tgt,lun is not stable on
    > > Linux (because of a "Linux bug") why is the b,t,l scheme preferred
    > > over the /dev/sg* one ?
    > b,t,l _is_ stable as long as the OS does a reasonable and orthogonal work.
    > This was true until ~ 2001, when Linux introduced unstable USB handling.
    > Note that this fact is not a failure from libscg but from Linux.

    Isn't that also when the USB system underwent a massive rewrite to fully
    support hotplugging and to fix a lot of bugs that were present in the
    original implementation?

    Still, the question I posed in my earlier post remains - why can't you have
    your program do the BTL mappings behind the scenes? You can easily allow it
    from the command line and also allow pointing to a /dev entry... If you want
    I'll actually put together a patch based on whatever version of cdrecord I
    have here on my system and send it to you.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2006-02-13 23:50    [W:0.023 / U:3.864 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site