Red Hat Bugzilla – Full Text Bug Listing |
Summary: | No access to sgX device for DVD writer | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | André Johansen <andrejoh> |
Component: | udev | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-08 03:06:40 EDT | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- |
Description
André Johansen
2007-10-06 14:36:44 EDT
A normal user cannot be granted write access to /dev/sg*. This would enable a normal user to flash a new firmware and do similar bad things. What other solutions are there, then? Having to login as root to rip a CD is no good, suid is even worse. Searching on the net reveals that people do change permissions on the sgX device (not persistent with udev, but works). Some burning programs also seem to have problems with this, according to the search results. just use /dev/sr* On my Fedora 7/x86-64 (fresh install on new computer), there are no such devices. I do get various symlinks (like /dev/dvdrw-sr0), but they all point to /dev/scd0. And cdparanoia does not get anywhere further with that device: $ cdparanoia -vQ -d /dev/dvdwriter-sr0 cdparanoia III release 9.8 (March 23, 2001) (C) 2001 Monty <monty@xiph.org> and Xiphophorus Report bugs to paranoia@xiph.org http://www.xiph.org/paranoia/ Checking /dev/dvdwriter-sr0 for cdrom... Testing /dev/dvdwriter-sr0 for SCSI interface Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Error trying to open /dev/scd0 exclusively (Device or resource busy). retrying in 1 second. Could not access device /dev/scd0: Device or resource busy Testing /dev/dvdwriter-sr0 for cooked ioctl() interface /dev/scd0 is not a cooked ioctl CDROM. Uhm, until I tried it again just now, and something obviously has made the device available for cdparanoia. This is on a KDE desktop. Any ideas of what might have caused the "resource busy" problem (digressing from the initial bug report, but this might lead to another or a bug transformation)? (BTW, thanks for the help so far!) yes, kde automount is polling, and only one application should read from the device. |