"Jim Crilly" <[email protected]> wrote: > All you've explained is that using SCSI ID for device names is the way > you want cdrecord to work, not why it's infinitely better than using real > device names like every other userland program on every OS in existance. I did many times, but people don't seem to listen. > The people replying here are your users, if you don't want to listen to > them pretty much any conversation with you will be a waste of time. Sorry, but from reading the mail from _real_ cdrecord users, it is obvious that the people here are either not my users or users with a stange way of thinking. Jörg -- EMail:[email protected] (home) Jörg Schilling D-13353 Berlin [email protected] (uni) [email protected] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily - 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: DervishD <[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: Keith Duthie <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Martin Mares <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: sean <[email protected]>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- References:
- Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <[email protected]>
- 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: Jan Engelhardt <[email protected]>
- 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]>
- Rationale for RLIMIT_MEMLOCK?
- Prev by Date: Re: libATA PATA status report, new patch
- Next by Date: Re: libata PATA status report on 2.6.16-rc1-mm5
- 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):