On Wed, 27 Feb 2002, Joerg Schilling wrote: > You are using an outdated version on a broken Linux kernel! > > >http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/problems.html > > cdrecord cannot know in advance which bugs future Linux kernels will introduce....
Since the original note doesn't say what kernel he's using, I assume you're still claiming that all Linux kernels are broken, meaning they didn't use your code. This is your standard answer to every problem, from memory parity and bad cables to people trying to run cdrecord on ZIP drives. Not only don't you know what kernel he's running, I don't see anything which identifies which o/s he's running at all. Maybe it was actually your favorite irrelevant niche software, Solaris. I run cdrecord on three SCSI and five ATAPI burners, from Cyrix CPU running 2.2.6 to Athlon running day-old test kernels with hour-old patches, and it works. No fuss, no muss, can't find all these errors you keep warning people about, the only problem I find at all is readcd or sdd on ide-scsi trying to read beyond end of data (which may or may not be a kernel bug). As far as outdated software, have you every stopped calling anything any newer than what he's running production? Or do you expect people to run real systems on ALPHA or BETA releases? -- -bill davidsen ([EMAIL PROTECTED]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
