cdrecord suddenly doesn't allow burning

Ask a Question related to Debian, Design and Development.

  1. #1

    Default Re: cdrecord suddenly doesn't allow burning

    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
    >
    > jorishuizer@debian:~$ cdrecord -v -eject -force
    > blank=all speed=1 dev=0,0,0 cd_image
    > /usr/bin/cdrecord: /usr/bin/cdrecord: Permission
    > denied
    > jorishuizer@debian:~$ cdrecord -scanbus
    > /usr/bin/cdrecord:
    > /usr/bin/cdrecord: Permission denied
    >
    > I think this started after I installed SANE but I
    > don't have any idea why that could be related;
    >
    > It seems I'm in the right group for this:
    >
    > jorishuizer@debian:~$ ls -lh /usr/bin/cdrecord
    > -rws--x--- 1 root cdrom 142 Jul 10
    > 14:16 /usr/bin/cdrecord
    > jorishuizer@debian:~$ groups
    > jorishuizer cdrom audio src video
    >
    > Can anybody tell me what to do to make cd writing
    > possible again (for normal users) ?
    >
    > Thanks very much,
    >
    > Joris
    >
    > __________________________________
    > Do you Yahoo!?
    > Yahoo! SiteBuilder - Free, easy-to-use web site design software
    > [url]http://sitebuilder.yahoo.com[/url]
    >

    --
    To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
    maillist@bestworldweb.homelinux.com Guest

  2. Similar Questions and Discussions

    1. cdrecord bug?
      Hi group, with the cdrecord versions from testing and unstable (2.0) I am unable to work with an ATAPI CDROM. With the woody version (1.10) I can...
    2. cdrecord warning message
      I recently rebuilt my system. I didn't use to get this message: cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler cdrecord:...
    3. multisession cdrecord question
      # cdrecord -msinfo dev=1,1,0 RAW/R16 0,221691 # cdrecord -msinfo dev=1,1,0 RAW/R16 44317,51858 what can be implied by those 2 data? how can I...
    4. multiseesion of cdrecord question
      # cdrecord -msinfo dev=1,1,0 RAW/R16 0,221691 # cdrecord -msinfo dev=1,1,0 RAW/R16 44317,51858 what can be implied by those 2 data? how can I...
    5. Can cdrecord used for writing for CD-RW media
      ehab wrote: Yes . There is no special syntax other than that you will have to take into account that CD-RW media usually has a much lower...
  3. #2

    Default Re: cdrecord suddenly doesn't allow burning

    Hello

    Joris Huizer (<joris_huizer@yahoo.com>) wrote:
    > I've got this problem, the cdrecord allways worked for
    > me but now suddenly there are permission problems
    >
    > jorishuizer@debian:~$ cdrecord -v -eject -force
    > blank=all speed=1 dev=0,0,0 cd_image
    > /usr/bin/cdrecord: /usr/bin/cdrecord: Permission
    > denied
    > jorishuizer@debian:~$ cdrecord -scanbus
    > /usr/bin/cdrecord:
    > /usr/bin/cdrecord: Permission denied
    >
    > I think this started after I installed SANE but I
    > don't have any idea why that could be related;
    >
    > It seems I'm in the right group for this:
    >
    > jorishuizer@debian:~$ ls -lh /usr/bin/cdrecord
    > -rws--x--- 1 root cdrom 142 Jul 10
    > 14:16 /usr/bin/cdrecord
    > jorishuizer@debian:~$ groups
    > jorishuizer cdrom audio src video
    >
    > Can anybody tell me what to do to make cd writing
    > possible again (for normal users) ?
    Did you check the permissions for the device files /dev/scd* and
    /dev/sg*? They should be owned by root.cdrom and be read-writable by
    owner and group.

    best regards
    Andreas Janssen

    --
    Andreas Janssen
    [email]andreas.janssen@bigfoot.com[/email]
    PGP-Key-ID: 0xDC801674
    Registered Linux User #267976


    --
    To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
    Andreas Janssen Guest

  4. #3

    Default Re: cdrecord suddenly doesn't allow burning

    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)
    exec cdrecord.shm "$@"
    ;;
    2.4|*)
    exec cdrecord.mmap "$@"
    ;;
    esac

    You can fiddle with the permissions of cdrecord.*

    On my system, everything works if I chmod +r /usr/bin/cdrecord

    --
    Danilo Raineri, [email]danirain@tin.it[/email]


    --
    To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
    Danilo Raineri Guest

  5. #4

    Default Re: cdrecord suddenly doesn't allow burning

    On Wed, Aug 06, 2003 at 11:43:14AM +0000, 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:
    >
    > AinSoph:~# cat /usr/bin/cdrecord
    > #!/bin/sh
    > VERS=`/sbin/kernelversion`
    > case $VERS in
    > 2.0|2.2)
    > exec cdrecord.shm "$@"
    > ;;
    > 2.4|*)
    > exec cdrecord.mmap "$@"
    > ;;
    > esac
    >
    > You can fiddle with the permissions of cdrecord.*
    >
    > 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.

    Regards,

    --
    Sridhar M.A.

    One Bell System - it sometimes works.


    --
    To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
    Sridhar M.A. Guest

  6. #5

    Default Re: cdrecord suddenly doesn't allow burning


    --- Danilo Raineri <raidan77@tin.it> 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
    > #!/bin/sh
    > VERS=`/sbin/kernelversion`
    > case $VERS in
    > 2.0|2.2)
    > exec cdrecord.shm "$@"
    > ;;
    > 2.4|*)
    > exec cdrecord.mmap "$@"
    > ;;
    > esac
    >
    > You can fiddle with the permissions of cdrecord.*
    >
    > On my system, everything works if I chmod +r
    > /usr/bin/cdrecord
    >
    > --
    > Danilo Raineri, [email]danirain@tin.it[/email]
    >
    >
    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:16 /usr/bin/cdrecord
    -rwxr-xr-x 1 root cdrom 307K Jul 10
    14:16 /usr/bin/cdrecord.mmap
    -rwxr-xr-x 1 root cdrom 307K Jul 10
    14:16 /usr/bin/cdrecord.shm

    but before a cdmod +r cdrecord still replied,
    /usr/bin/cdrecord: /usr/bin/cdrecord: Permission
    denied

    The /dev/scd* "files" are all root.cdrom; the /dev/sg*
    "files" are all root.root

    I was allready in the cdrom group so I tried the
    following. I did chmod +r /usr/bin/cdrecord - and now
    running cdrecord results in:

    jorishuizer@debian:~$ cdrecord -v -eject -force -immed
    speed=1 dev=0,0,0 cd_image
    Cdrecord 2.01a16 (i686-pc-linux-gnu) Copyright (C)
    1995-2003 Jörg Schilling
    TOC Type: 1 = CD-ROM
    cdrecord.mmap: Operation not permitted. WARNING:
    Cannot do mlockall(2).
    cdrecord.mmap: WARNING: This causes a high risk for
    buffer underruns.
    cdrecord.mmap: Operation not permitted. WARNING:
    Cannot set RR-scheduler
    cdrecord.mmap: Permission denied. WARNING: Cannot set
    priority using setpriority().
    cdrecord.mmap: WARNING: This causes a high risk for
    buffer underruns.
    scsidev: '0,0,0'
    scsibus: 0 target: 0 lun: 0
    cdrecord.mmap: Permission denied. Cannot open
    '/dev/sg0'. Cannot open SCSI driver.
    cdrecord.mmap: For possible targets try 'cdrecord
    -scanbus'. Make sure you are root.
    cdrecord.mmap: For possible transport specifiers try
    'cdrecord dev=help'.
    cdrecord.mmap: Also make sure that you have loaded the
    sg driver and the driver for
    cdrecord.mmap: SCSI hardware, eg. ide-scsi if you run
    IDE/ATAPI drives over
    cdrecord.mmap: ide-scsi emulation. Read
    /usr/share/doc/cdrecord/README.ATAPI.setup!

    ?? now what should I do ? Should I change /dev/sg0 to
    the cdrom group too ? :-s

    By the way, why did cdrecord change to a script
    (without a warning it seems) ?

    Thanks very much for your help,

    Joris

    __________________________________
    Do you Yahoo!?
    Yahoo! SiteBuilder - Free, easy-to-use web site design software
    [url]http://sitebuilder.yahoo.com[/url]


    --
    To UNSUBSCRIBE, email to [email]debian-user-request@lists.debian.org[/email]
    with a subject of "unsubscribe". Trouble? Contact [email]listmaster@lists.debian.org[/email]
    Joris Huizer Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139