Re: [OT] Joerg Schilling flames Linux on his Blog

["Alexander E. Patrakov" <patrakov@ums.usu.ru>]

On Thursday 26 May 2005 05:31, Kyle Moffett wrote:

> Did you try submitting a list of important SCSI commands and their
> functions?
> I suspect that if you provide a clear, concise list of harmless
> commands,
> they would be included in the available command set.

That list would be device-dependent. See two examples below.

1) cdrecord uses some Sony proprietary commands instead of standard MMC ones 
if the drive seems to be made by Sony. What is the effect of those Sony 
commands on non-Sony drives?

2) I have the following DVD-ROM + CD-RW combo drive:

'PHILIPS ' 'CDD5301         ' 'P1.2'

Originally, I bought it with the 'B1.1' firmware revision. This drive with old 
firmware is a security hole by itself: if one calls cdrecord dev=/dev/hdd 
-dao some-image.iso, the drive will enter some strange mode at the end. In 
particular, it will flash its light randomly, will never give the CD back 
(waited 15 minutes), and will prevent communication with /dev/hdc until I 
power off the computer (pressing Reset is not enough). Burning CDs with -raw 
switch instead of -dao works. With newer firmware, -dao doesn't lock up the 
drive, but still results in damaged CDs.

Also this drive always silently produces CDs with a lot of wrong bits (but a 
useless and broken image can still be read with dd or readcd) when BurnFree 
is off.

So this filter, if it is in the kernel, should forbid commands specific to SAO 
burning for this drive _and_ also return a modified list of capabilities for 
this drive (i.e. say that this drive _cannot_ burn in SAO mode).

Isn't this too much knowledge for the kernel?

-- 
Alexander E. Patrakov
P.S. I know that the proper solution would be to replace the drive. I tried 
returning it to the shop, they said "no, it is in order because it works with 
Nero in Windows" and fined me for $25 for their "expertize".