lsorense@csclub.uwaterloo.ca (Lennart Sorensen) wrote: > Hmm, perhaps what should be done is that someone needs to write and > maintain a patch that linux users can apply to cdrecord (since other OSs > are different and hence have no reason to use such a patch), to make it > behave in a manner which is sane on linux. It should of course be > clearly marked as having been changed in such a way. It should use udev > if available and HAL and whatever else is appropriate on a modern linux > system, and if on an old system it should at least not break the > interfaces that already worked on those systems in cdrecord. Unfortunately is it a matter oif facts that all known patches for cdrecord break more things than they claim to fix. 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: "Jim Crilly" <jim@why.dont.jablowme.net>
- 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: Matthias Andree <matthias.andree@gmx.de>
- 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 <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>
- 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: DervishD <lkml@dervishd.net>
- Re: CD writing in future Linux (stirring up a hornets' nest)
- From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
- Re: CD writing in future Linux (stirring up a hornets' nest) (was: Rationale for RLIMIT_MEMLOCK?)
- 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 (stirring up a hornets' nest)
- Index(es):
![]() |