SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Here's a RELATED question: I hadn't changed the permissions on cdrecord nor cdrdao since I read in the Slackware-current changelog (entry dated April 19, 2007) that, because k3b no longer "requires" cdrecord to be setuid root, it was moved into the main tree. But, I just tried to burn a CD-ROM ISO and it failed miserably. When I changed the permissions per k3b setup, it worked fine.
My non-privileged account is a member of the cdrom group, and the block devices /dev/hda (my dual-layer DVD burner) and /dev/hdc (my CD-burner/DVD-ROM drive) both have 660 permissions.
So here's the question: How come I've been able to burn DVD-ROMs left and right without such trouble? Isn't growisofs simply some kind of wrapper for makeisofs and cdrecord? Or am I misunderstanding the relationship between all these programs? Thanks for replies...
I am having the same issue with xfce and graveman. Could "The Kid" provide more info as to what permissions were changed. My system has a Via C3 cpu which is cool and efficient but no powerhouse so I would like to stay with a lightweight system ie no K3B and the KDE dependencies
I am having the same issue with xfce and graveman. Could "The Kid" provide more info as to what permissions were changed. My system has a Via C3 cpu which is cool and efficient but no powerhouse so I would like to stay with a lightweight system ie no K3B and the KDE dependencies
The settings I changed were in the K3B program, Settings menu -> Setup System Permissions. Also, adding yourself to the cdrom group is essential. Not sure how to fix it if you don't want to use K3B. Try searching for cdrecord and see what pops up, if that is what you plan on using.
Allegedly, the version of cdrecord in Slackware 12 no longer requires the suid bit, and I am aware of several *very* reputable individuals who can confirm that. However, my experience does not support that assertion, and I am aware of several other people with the same experience. Long story short - if you get those messages indicating that the SCSI ioctls can't be used, then set /usr/bin/cdrecord suid.
If you're not the paranoid type and/or you don't have any untrusted users on the box, the simplest thing to do is this:
Code:
chmod 4755 /usr/bin/cdrecord
If you don't want all users on the box to use the cdrecord executable (since it will be suid), then you can do this:
Here's a RELATED question: I hadn't changed the permissions on cdrecord nor cdrdao since I read in the Slackware-current changelog (entry dated April 19, 2007) that, because k3b no longer "requires" cdrecord to be setuid root, it was moved into the main tree. But, I just tried to burn a CD-ROM ISO and it failed miserably. When I changed the permissions per k3b setup, it worked fine.
My non-privileged account is a member of the cdrom group, and the block devices /dev/hda (my dual-layer DVD burner) and /dev/hdc (my CD-burner/DVD-ROM drive) both have 660 permissions.
So here's the question: How come I've been able to burn DVD-ROMs left and right without such trouble? Isn't growisofs simply some kind of wrapper for makeisofs and cdrecord? Or am I misunderstanding the relationship between all these programs? Thanks for replies...
That simple three layer access level, Owner, Group, World pretty much made the difference between what we know as Linux and what the world knows as... that other thing I used only to play games with.
You would *think* Vista would have come out with a similar security design, but apparently not...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.