cdrecord no workie after upgade to 2.6.10

[Kurt Wall]

On Fri, Dec 31, 2004 at 08:07:55PM -0700, Collins Richey took 92 lines to write:

[deletia]

> <just a little rant on>
> 1. I haven't tried 2.6.10 (and won't for a while after your reports).

No guts, no glory, Collins. ;-)

> 2. I had a hellacious time getting cdrecord to work at all on > 2.6.7.
> In my case, it turned out that cdrecord was not smart enough (that's
> an understatement! - totally hung system) to use DMA (is this the 21st
> century or what?). Once I turned off DMA for the recorder, problem
> solved.

That's odd.

> 3. I'm underwhelmed by Jorg's approach to kernel development, which
> seems to be "This old dog is not going to learn any new tricks." Don't
> expect me to adapt, just use some other operating system.

The argument here is that the kernel is setting policy rather than
enforcing policy set elsewhere. In this case, however, the issue is
that the SCSI command set can damage a system if deliberately and
maliciously misused. I'd prefer to have it a compile-time option to
enable mortal users to use the given SCSI commands.

> 4. Sigh, why aren't there any alternatives? If you want a browser,
> there's a plethora.

FreeBSD's burncd comes to mind, but I don't know if it runs on Linux.

Kurt
-- 
Speak softly and carry a +6 two-handed sword.