All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: cd burning, capabilities and available modes
Date: Thu, 02 Dec 2004 08:57:01 +0100	[thread overview]
Message-ID: <41AECACD.6030308@bio.ifi.lmu.de> (raw)
In-Reply-To: <1101908433l.8423l.0l@werewolf.able.es>

J.A. Magallon wrote

> werewolf:/store/tmp> cdrecord -dummy dev=ATAPI:1,0,0 *.iso

Why not use "dev=ATAPI:/dev/hdd" or whatever device in /dev/ is
your burner...?

> ...
> cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
> cdrecord: WARNING: This causes a high risk for buffer underruns.
> cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler
> cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
> cdrecord: WARNING: This causes a high risk for buffer underruns.
> scsidev: 'ATAPI:1,0,0'
> devname: 'ATAPI'
> scsibus: 1 target: 0 lun: 0
> Warning: Using ATA Packet interface.
> Warning: The related Linux kernel interface code seems to be unmaintained..
> Warning: There is absolutely NO DMA, operations thus are slow.
> WARNING ! Cannot gain SYS_RAWIO capability ! 
> : Operation not permitted

Sth. seems to be wrong here. When I do this as user I get
...
Use of ATA is preferred over ATAPI.
Warning: Using ATA Packet interface.
Warning: The related libscg interface code is in pre alpha.
Warning: There may be fatal problems.
Using libscg version 'schily-0.8'.
...

so it seems that your kernel is still blocking some command in the userland.
This might cause your problems, because I get the same write modes as user
that I get as root. I use 2.6.9 but have allowed some more commands for
users. You can add this in linux/drivers/block/scsi_ioctl.c to see if
some commands are blocked as user:

--- linux/drivers/block/scsi_ioctl.c.orig       2004-08-18 16:11:01.000000000 +0200
+++ linux/drivers/block/scsi_ioctl.c    2004-08-18 16:11:55.000000000 +0200
@@ -172,6 +228,12 @@
         /* And root can do any command.. */
         if (capable(CAP_SYS_RAWIO))
                 return 0;
+        /* Added for debugging*/
+
+       if(file->f_mode & FMODE_WRITE)
+         printk(KERN_WARNING "SCSI-CMD Filter: 0x%x not allowed with write-mode\n",cmd[0]);
+       else
+         printk(KERN_WARNING "SCSI-CMD Filter: 0x%x not allowed with read-mode\n",cmd[0]);

         /* Otherwise fail it with an "Operation not permitted" */
         return -EPERM;

cu,
Frank


-- 
Dipl.-Inform. Frank Steiner   Web:  http://www.bio.ifi.lmu.de/~steiner/
Lehrstuhl f. Bioinformatik    Mail: http://www.bio.ifi.lmu.de/~steiner/m/
LMU, Amalienstr. 17           Phone: +49 89 2180-4049
80333 Muenchen, Germany       Fax:   +49 89 2180-99-4049
* Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *


      parent reply	other threads:[~2004-12-02  7:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 13:40 cd burning, capabilities and available modes J.A. Magallon
2004-12-01 16:36 ` Daniel Drake
2004-12-01 15:00   ` J.A. Magallon
2004-12-01 17:05 ` Lee Revell
2004-12-01 22:38 ` Bill Davidsen
2004-12-01 22:58   ` J.A. Magallon
2004-12-02  7:57 ` Frank Steiner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41AECACD.6030308@bio.ifi.lmu.de \
    --to=fsteiner-mail@bio.ifi.lmu.de \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.