"Jim Crilly" <jim@why.dont.jablowme.net> 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:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) schilling@fokus.fraunhofer.de (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 majordomo@vger.kernel.org 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 <lkml@dervishd.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Keith Duthie <random@no.net.nz>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Martin Mares <mj@ucw.cz>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: sean <seanlkml@sympatico.ca>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- References:
- Rationale for RLIMIT_MEMLOCK?
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Luke-Jr <luke@dashjr.org>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Luke-Jr <luke@dashjr.org>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- From: Peter Read <peter.read@gmail.com>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Matthias Andree <matthias.andree@gmx.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: Joerg Schilling <schilling@fokus.fraunhofer.de>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: "Jim Crilly" <jim@why.dont.jablowme.net>
- 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):
![]() |