Re: cdrecord suddenly doesn't allow burning

2003-08-14 Thread [EMAIL PROTECTED]
Try cdrecord as root. This should tell you if it is a permission problem. On Wed, 2003-08-06 at 19:32, Joris Huizer wrote: > Hello everybody, > > I've got this problem, the cdrecord allways worked for > me but now suddenly there are permission problems > > [EMAIL PROTECTED]:~$ cdrecord -v -eject

Re: cdrecord suddenly doesn't allow burning

2003-08-14 Thread Andreas Janssen
Hello Joris Huizer (<[EMAIL PROTECTED]>) wrote: > I've got this problem, the cdrecord allways worked for > me but now suddenly there are permission problems > > [EMAIL PROTECTED]:~$ cdrecord -v -eject -force > blank=all speed=1 dev=0,0,0 cd_image > /usr/bin/cdrecord: /usr/bin/cdrecord: Permissio

Re: cdrecord suddenly doesn't allow burning

2003-08-14 Thread Danilo Raineri
Joris Huizer wrote: > /usr/bin/cdrecord: Permission denied It seems that /usr/bin/cdrecord has been replaced by a script, which calls the appropriate executable depending on the kernel version: AinSoph:~# cat /usr/bin/cdrecord #!/bin/sh VERS=`/sbin/kernelversion` case $VERS in 2.0|2.2) exe

cdrecord suddenly doesn't allow burning

2003-08-14 Thread Joris Huizer
Hello everybody, I've got this problem, the cdrecord allways worked for me but now suddenly there are permission problems [EMAIL PROTECTED]:~$ cdrecord -v -eject -force blank=all speed=1 dev=0,0,0 cd_image /usr/bin/cdrecord: /usr/bin/cdrecord: Permission denied [EMAIL PROTECTED]:~$ cdrecord -scan

Re: cdrecord suddenly doesn't allow burning

2003-08-14 Thread Andreas Janssen
Hello Joris Huizer (<[EMAIL PROTECTED]>) wrote: > Well that idea about cdrecord seems to be the case > indeed. However, I did > chown root:cdrom cdrecord.mmap > chown root:cdrom cdrecord.shm > > And ls -l /usr/bin/cdrecord* now gives me: > -rws--x---1 root cdrom 142 Jul 10 > 14:1

Re: cdrecord suddenly doesn't allow burning

2003-08-14 Thread Joris Huizer
--- Danilo Raineri <[EMAIL PROTECTED]> wrote: > Joris Huizer wrote: > > > /usr/bin/cdrecord: Permission denied > > It seems that /usr/bin/cdrecord has been replaced by > a script, which calls > the appropriate executable depending on the kernel > version: > > AinSoph:~# cat /usr/bin/cdrecord >

Solved Re: cdrecord suddenly doesn't allow burning

2003-08-14 Thread Pigeon
On Thu, Aug 07, 2003 at 09:36:11AM -0700, Joris Huizer wrote: > --- Pigeon <[EMAIL PROTECTED]> wrote: > > > > chmod 4710 /usr/bin/cdrecord.* > > chmod 755 /usr/bin/cdrecord > > Thanks, those two commands solved the problems :-) Cool. > I don't know the syntax chmod 4710 /usr/bin/cdrecord.*

Re: cdrecord suddenly doesn't allow burning

2003-08-10 Thread Danilo Raineri
Sridhar M.A. wrote: >> On my system, everything works if I chmod +r /usr/bin/cdrecord >> > Do it the debian way. Add yourself to the cdrom group. /dev/scd0 has > root.cdrom as owner. That will solve the OP's problem. Actually, I did it the Debian way with dpkg-statovveride. I am in the

Re: cdrecord suddenly doesn't allow burning

2003-08-10 Thread Sridhar M.A.
On Wed, Aug 06, 2003 at 11:43:14AM +, Danilo Raineri wrote: > Joris Huizer wrote: > > > /usr/bin/cdrecord: Permission denied > > It seems that /usr/bin/cdrecord has been replaced by a script, which calls > the appropriate executable depending on the kernel version: >

Re: cdrecord suddenly doesn't allow burning

2003-08-10 Thread Pigeon
On Wed, Aug 06, 2003 at 06:14:06PM +0200, Andreas Janssen wrote: > Hello > > Joris Huizer (<[EMAIL PROTECTED]>) wrote: > > > ?? now what should I do ? Should I change /dev/sg0 to > > the cdrom group too ? :-s > > Yes, you should change that Set them to cdrom group and make them > read-writable f

Re: cdrecord suddenly doesn't allow burning

2003-08-07 Thread Andreas Janssen
Hello Pigeon (<[EMAIL PROTECTED]>) wrote: > On Wed, Aug 06, 2003 at 06:14:06PM +0200, Andreas Janssen wrote: >> Hello >> >> Joris Huizer (<[EMAIL PROTECTED]>) wrote: >> >> > ?? now what should I do ? Should I change /dev/sg0 to >> > the cdrom group too ? :-s >> >> Yes, you should change that S