>> Tell me how to access a ATAPI tape drive via libscg. (I probably don't get that question.) The top of drivers/ide/ide-tape.c shows it gets /dev/ht%d (when used without scsi emulation I believe). And I pick a wild guess that it gets /dev/sg%d when used with scsi emu. Programs using libscg would only need to use S:I:L or ATA:/dev/ht0 (?) I presume? >It is *your* library, I have no interest in it as long as CD writing >works at the moment. Either do your research or ask the public, I'm not >going to answer or research this for you. > >It is not helpful that you are (1) talking about ATAPI tapes under the >CD subject and (2) claim you know better than Linux (or Jens, for that >matter) if you haven't researched this. I think you (Matthias) get it slightly skewed here. As far as I am able to slip through the flames, libscg is used by cdrecord just as libc is used by all apps to have "some sort" of OS abstraction (pick some function, like fork()). Therefore, libscg seems +not only+ about cd writing. However, if you want to have a working cdrecord, you need a working libscg, just like you need a working libc or your system is going bye-bye. 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 (stirring up a hornets' nest)
- From: Matthias Andree <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- References:
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <[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: Jens Axboe <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jens Axboe <[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)
- From: Matthias Andree <[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]>
- 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]>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- Prev by Date: Re: GPL V3 and Linux - Dead Copyright Holders
- Next by Date: Re: [PATCH 2/6] vfs: propagate mnt_flags into do_loopback/vfsmount
- Previous by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Next by thread: Re: CD writing in future Linux (stirring up a hornets' nest)
- Index(es):