On Sun, 10 Apr 2005, Nick Hill wrote: > >which version of cdrecord or growisofs package are you using? > > Both are listed in both the Debian and kernel.org bug along with plenty > of other info. you don't seem to use the debian cdrecord package, try out, self compiled binaries are not supported by debian. debian's cdrecord -version shows an different input.
if it still doesn't work, please provide full debian version with $ dpkg -l <packge> for example dpkg -l cdrecord > > cant duplicate your problem with 2.6.11 and newer kernels. > > I have duplicated wthe bug with Debian 2.6.11-3 and Kernel.org 2.6.11.7. > The bug occurs every time. I hit reset, boot into 2.6.9 then it works OK. you might be using the wrong tools. unless you might prove the contrare i'll have to close your bug report. > >>Given the severity of the bug, I am surprised it has survived two kernel > >>versions. For me, 2,6.10 and 2.6.11 have incrementally added three > >>serious/ critical bugs, and only solved an ISO9660 file system issue > >>(where files >2Gb would confuse the driver). The field is open for > >>better systems of kernel development management than what we are seeing > >>with the official kernel. > > > > > >who are you to come up which such bad attitudes > >and to think you gonna go anywhere? > > Max, a world where people can't declare their opinions and observations > (where someone else may not agree with them) would be a bad place. This > is what distinguishes the mediaeval dark ages. > > I don't think anyone should fall into the thinking the current process > is perfect as that will block thinking of possible improvements. come on, don't divert the topic: free opinion != ranting especially bad if you expect to get help. nor did i see from you any improvements in the current dev process. -- maks kernel janitor http://janitor.kernelnewbies.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
