[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: FC6 and cdburning

fre, 28 07 2006 kl. 21:13 -0400, skrev Jesse Keating:
> On Friday 28 July 2006 20:58, David Nielsen wrote:
> > It is an upstream change, that much is clear it is related to the SCSI
> > command change from a while back, that does not mean we shouldn't at
> > least propose a fix or ask the reporters for more information.. We know
> > it's broken, we've known for months. This is probably the single most
> > active bug I have ever had to deal with and all we've seen is users
> > saying "me too".
> >
> > I report bugs to Fedora, my life is to short to track down every single
> > projects bugzilla, create accounts and repeat the information. I use
> > Fedora, if the maintainer of the package feels the bug report needs to
> > go upstream he can ask me to do so. The bug has not been closed as
> > NOTOURBUG and it directly affects users of Fedora. It worked with FC4,
> > we lived with the regression in FC5.. please don't make us suffer in FC6
> > as well.
> DaveJ's comment still stands.  We need a way in upstream kernel to have a list 
> of safe commands per device.  This infrastructure doesn't exist right now.  
> The commands are sanitized at a different level.  We could suid cdrecord, but 
> that's a security flaw.  We could just allow all commands, but what might 
> be 'enable BURN-proof' on one drive may be 'flash firmware' on another.  I 
> seem to remember another distro had an issue that was perm damaging certain 
> cdrom drives, I wonder if this is related.  I'd much rather see a little 
> necessary work around rather than blown up drives.
> So we know what needs to be done, unfortunately our kernel team doesn't have 
> the bandwidth to deal with this rightnow.  Since this is in the kernel since 
> around 2.6.8, I wonder what other distributions are doing to resolve this 
> issue....

My guess is that any distro that doesn't suffer from this (I'm a full on
Fedora user so I haven't tested every single one out there) either
revert the security patch or suid cdrecord.

The other distro you were thinking of was Mandrake 8 that killed lite-on
drives, this was a hardware bug btw. I had one of those so I know that
bug intimately. One of the reasons I went out and bought a Plextor drive
was that for once I wanted a quality drive that didn't burn coasters and
wouldn't suffer from this kind of bug. Imagine my horror when a drive
that cost more than twice as much as a shoddy drive suddenly stopped
working. Lesson learned, Linux works best on shitty hardware.

- David

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]