all burning apps will retry a few times if they get "busy"....
doesn't help, since hal doesn't just open it, but also issues an ioctl
that then goes to the device, and THAT is causing the damage. Not the
open itself.
if the user wants to destroy his own burning cd... then why is it the
kernels job to stop him?
oh I really want to have this ioctl cached, but more so that the kernel
can enforce a reasonable polling interval ;)
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.**--****.com/
Please read the FAQ at http://www.**--****.com/