SEO

Hi,

I'm just trying to integrate K3B into XFCE... and discover that I have to
jump through burning loops to burn as a normal user.

Test: I'm taking some directory and making and ISO of it with mkisofs -J -
r -v -V "test" -o test.iso test/

And when I try to burn the thing like this as a normal user, I get this:

Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr).
Driver flags : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/
R96R
Drive buf size : 1895168 = 1850 KB
FIFO size : 4194304 = 4096 KB
Track 01: data 3 MB
Total size: 3 MB (00:22.48) = 1686 sectors
Lout start: 4 MB (00:24/36) = 1686 sectors
cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl

I googled for about an hour, and found endless discussions about suid
root and broken kernel interfaces. And my only reaction to this: Jesus.
Such an important tool as cdrecord, and it's left in an almost unusable
state. Do they want to compete with Vista's Unusability Experience?

Does someone have a *practical* suggestion to fix the burn-as-user
problem? By practical, I don't mean switching back to a 2.4 kernel or <=
2.6.9, log into XFCE as root or prefer Solaris to Slackware.

cheers,

Niki

On Sat, 06 Oct 2007 14:29:02 +0000, Niki Kovacs wrote:

> Such an important tool as cdrecord, and it's left in an almost unusable
> state. Do they want to compete with Vista's Unusability Experience?

Troll.

*Plonk*

Le Sat, 06 Oct 2007 14:56:55 +0000, Dave Uhring a écritÂ*:
>
> Troll.
>
> *Plonk*

Nazi.

*Plonk*

Niki Kovacs schreef:
> Hi,
>
> I'm just trying to integrate K3B into XFCE... and discover that I have to
> jump through burning loops to burn as a normal user.

I always burn as a normal user. But I let Krb fix the permissions for
me, and add myself to verious system groups that allow me access to my
system's hardware components (cdrom, audio, scanner, plugdev, power,
disk, floppy ... maybe more).

Eric

On Sat, 06 Oct 2007 14:56:55 +0000, Dave Uhring wrote:

> On Sat, 06 Oct 2007 14:29:02 +0000, Niki Kovacs wrote:
>
>> Such an important tool as cdrecord, and it's left in an almost unusable
>> state. Do they want to compete with Vista's Unusability Experience?
>
> Troll.
>
> *Plonk*

Pank.

*flush*

On Sat, 06 Oct 2007 14:29:02 +0000, Niki Kovacs wrote:

> Hi,
>
> I'm just trying to integrate K3B into XFCE... and discover that I have
> to jump through burning loops to burn as a normal user.
>
> Test: I'm taking some directory and making and ISO of it with mkisofs -J
> - r -v -V "test" -o test.iso test/
>
> And when I try to burn the thing like this as a normal user, I get this:
>
> Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags :
> MMC-3 SWABAUDIO BURNFREE FORCESPEED Supported modes: TAO PACKET SAO
> SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/ R96R
> Drive buf size : 1895168 = 1850 KB
> FIFO size : 4194304 = 4096 KB
> Track 01: data 3 MB
> Total size: 3 MB (00:22.48) = 1686 sectors Lout start: 4
> MB (00:24/36) = 1686 sectors cdrecord: Operation not permitted. Cannot
> send SCSI cmd via ioctl
>
> I googled for about an hour, and found endless discussions about suid
> root and broken kernel interfaces. And my only reaction to this: Jesus.
> Such an important tool as cdrecord, and it's left in an almost unusable
> state. Do they want to compete with Vista's Unusability Experience?
>
> Does someone have a *practical* suggestion to fix the burn-as-user
> problem? By practical, I don't mean switching back to a 2.4 kernel or <=
> 2.6.9, log into XFCE as root

add the user to the 'burning' group and send the good parole in cdrecord:
# chmod 2710 /usr/bin/cdrecord

You may have access/perf issues if you don't care of the correct
interface-device you should use, Joerg included precise tools to
check what could be the best bet:

# cdrecord -scanbus
# cdrecord dev=help

And you'll adore (obviously, put your correct dev ref in this command):
# cdrecord dev=1001,0,0 -checkdrive

> or prefer Solaris to Slackware.

Ggggolleez, switching to a b0rken Unix (alas) in order to cure a
semantic problem inherent to some members of the lkml is
a bit over the top )

On 2007-10-06, Niki Kovacs <mickey@mouse.com> wrote:
> Hi,
>
> I'm just trying to integrate K3B into XFCE... and discover that I have to
> jump through burning loops to burn as a normal user.
>
> And when I try to burn the thing like this as a normal user, I get this:
> cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl

What about udev? You can have permission to write for this device.

Never tried since i burn as root from console

this is from my device:
BUS=="scsi", KERNEL=="sr0", SYSFS{vendor}=="_NEC ", \
SYSFS{model}=="DVD_RW ND-4570A ", NAME="%k", SYMLINK+="usb/nec", \
RUN+="/bin/sh -c 'chgrp korging /dev/sr0'"

So, no suid and stuff
--
Please excuse my english writing!
Slackware 12
Knowledge report: One and 1/2 year, still plenty to learn

On Sat, 06 Oct 2007 16:32:05 +0000, korgman wrote:

> On 2007-10-06, Niki Kovacs <mickey@mouse.com> wrote:
>> Hi,
>>
>> I'm just trying to integrate K3B into XFCE... and discover that I have
>> to jump through burning loops to burn as a normal user.
>>
>> And when I try to burn the thing like this as a normal user, I get
>> this: cdrecord: Operation not permitted. Cannot send SCSI cmd via ioctl
>
> What about udev? You can have permission to write for this device.
>
> Never tried since i burn as root from console

So as if someone passing by dropped an alias and trixxxed
some stuff in usual functions? You're way much cooler
than I am although even Poutine had to tell me to stop
looking at him this way whle I just was having a flash of a nap ;->

>
> this is from my device:
> BUS=="scsi", KERNEL=="sr0", SYSFS{vendor}=="_NEC ", \
> SYSFS{model}=="DVD_RW ND-4570A ", NAME="%k", SYMLINK+="usb/nec", \
> RUN+="/bin/sh -c 'chgrp korging /dev/sr0'"
>
> So, no suid and stuff

That'd be OK for a single user set-up, but I soomehow doubt that's
what Niki wanted to configure!?

On Sat, 6 Oct 2007, Niki Kovacs wrote:


because of jorgs anti-linux traits, there are free breakaways of this
project that work just as well, and some say better, the debian team have
done one such project (and its in source for all to use), jorg believes
only in two things, scsi and solaris, because he only knows scsi
well, he tries tell linux develop team they are clueless because the
2.6 kernel doesnt use scsi hooks for it like 2.4 used to, youll get used
to jorgs rhetoric after a while, most just ignore and laugh at him.

cdrtools is not, never has been, and never will be, the only cd/dvd
burning software

--

Cheers
Res

Le Sun, 07 Oct 2007 06:04:05 +0000, Joseph H. Rosevear a écritÂ*:
> prep:
>
> #!/bin/sh
>
> # Do your exporting here.
> export temp_dir=$HOME/temp
> export cd_dev=1,0,0
> export cd_speed=4
>
> # This wipes file elusive and sets its permissions. echo "#" >
> $temp_dir/elusive
> chmod 644 $temp_dir/elusive
>
> # You may need something from your .bashrc. if [ -r $HOME/.bashrc ];
> then
> echo "source $HOME/.bashrc" >> $temp_dir/elusive
> fi
>
> # This puts prep's arguments in file elusive. echo "$*" >>
> $temp_dir/elusive
>
> bash -c "source $temp_dir/elusive"
>
>
> I hope this helps.

Well, yes and no. I got your point. But the thing is: this is for
building a nOOb-friendly desktop, one application per task, and if
possible, the most user-friendly application per task. Whereas I mainly
use plain mkisofs and cdrecord for burning, I can't expect my users here
(library and town hall employess, some of whom barely know how to handle
a mouse) to launch shell scripts.

cheers,

Niki