Re: FC3/x86_64 + cdrecord.(i386|x86_64): what gives?

["Bryan J. Smith" <b.j.smith@ieee.org>]

On Sat, 2005-05-07 at 12:37 -0500, Nathaniel Reindl wrote:
> I've exhausted everything I could think of.  Anyone have any advice?

Several things ...

1.  Are you running as root?

If not, verify your user has write access to the device.
On Fedora-based distros, you should be granted write access
under /etc/security/console.perms.
If you are not logging into a console (tty1-6 or tty7/X11 by default),
then you'll have some additional write access to grant.

2.  Is cdrecord set uid (suid) to root?

NOTE:  Fedora Core 2+ should _never_ exhibit this issue, only some other
kernel 2.6 distros.

As of kernel 2.6.8+, cdrecord will fail if suid as root and run as a
regular user.  Long story short, as of kernel 2.6.8+, Linux & co. now
differentiate memory and IOCTL access whether something is truly
executed as id=0 logged in or if suid=0.  If suid root, certain access
isn't granted for security reasons.

Jorg has yet to update cdrecord to look for Linux 2.6.8+ and not attempt
certain access.  As of right now, when it knows it's running as root
(not differentiating between id=0 and suid=0), it attempts certain
priority IOCTL control and memory access -- not just on Linux, but other
UNIX systems.  This fails on Linux 2.6.8+, so Jorg blindly does a
cdrecord fault.

3.  Drive/Media incompatibility, and firmware updates

As many people have pointed out elsewhere, sometimes there are always
issues with older drives handling newer media.  What is your drive and
its firmware revision?



-- 
Bryan J. Smith                                  b.j.smith@ieee.org 
------------------------------------------------------------------ 
Community software is all about choice, choice of technology.
Unfortunately, too many Linux advocates port over the so-called
"choice" from the commercial software world, brand name marketing.
The result is false assumptions, failure to focus on the real
technical similarities and loyalty to blind vendor alignments.



-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.