long time ago in 2008 josee gave advice on using burnbox/dvd but i'm unable to find that ancient post, hehe.

n e way, ty for reading..

Manual: http://hg.slitaz.org/slitaz-tools/raw-file/tip/doc/burnbox.html

I don't remember if burnbox on stable 2.0 have all these functionalities.
You may like to download the latest burnbox from hg repos.

Also, do remember to add yourself to "cdrom" group else you will have permission problems.

Hi, I'm from Spain.
Please, can you tell me what I'm doing wrong? I set device path as /dev/cdrom, then, added my user with 'addgroup myusername cdrom'(as root, with 'su'). After that, checked permissions for device and got: 'You dont have read write permission for /dev/cdrom; Add yourself to group cdrom: addgroup tux cdrom'. And if I try executing BBox as root, I have the permissions, but I still cannot burn or erase anyway

Please also post:

ls -l /dev/cdrom 

TOC Type: 1 = CD-ROM
scsidev: '/dev/cdrom'
devname: '/dev/cdrom'
scsibus: -2 target: -2 lun: -2
Error trying to open /dev/cdrom exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/cdrom exclusively (Device or resource busy)... retrying in 1 second.
Error trying to open /dev/cdrom exclusively (Device or resource busy)... retrying in 1 second......

Thats what I get when I try as root (su / burnbox)

Thanks in advance

sorry....

# ls -l /dev/cdrom
lrwxrwxrwx 1 root root 8 May 17 03:03 /dev/cdrom -> /dev/hdc

Hey Jozee, thank you very much, but I have to go out now, I come back here in 2 hours.

THANKS FOLK!!

Ok:
As root, I executed burnbox & changed /dev/cdrom by /dev/hdc. After that, I can erase and write(I try with a cd/rw).
now, the problem is about permissions running bbox as user; I get 'wodim: permission denied'
Well, I continue trying...

I had documented this on the old forum about the hw scan to find the current dev name.

I suggested that burnbox run the hw scan and offer available drives.

If not, at least add a sentence to explain the need to scan in xterm for changing dev names, since this is not obvious and guessing at dev names is like leaving the user to crack a password.

Instructing the user to use xterm partially defeats the purpose of having a gui.

The forum managers are still holding the old forum archive offline so I cannot check what I did about permissions.

Maybe I'd have to type:
# adduser -G cdrom user_name
instead of:
# adduser user_name cdrom

???

I'll try this evening... Thanks

On my system to add an existing user (tux) to an existing group (cdrom)is:
root@slitaz: addgroup tux cdrom works.
This is supposed to work root@slitaz: adduser -G cdrom tuxbut on my system outputs adduser: login 'tux' is in use and doesn't add tux to group cdrom

On my system to add an existing user (tux) to an existing group(cdrom)is:

root@slitaz: addgroup tux cdrom

works.

This is supposed to work

root@slitaz: adduser -G cdrom tux

but on my system outputs

adduser: login 'tux' is in use

and doesn't add tux to group cdrom

On my system to add an existing user (tux) to an existing group (cdrom)is:

root@slitaz: addgroup tux cdrom

works.

This is supposed to work

root@slitaz: adduser -G cdrom tux

but on my system outputs

adduser: login 'tux' is in use

and doesn't add tux to group cdrom