Instead of disabling the check explicitly, the code could (and should) be modified so it doesn't do the check unless it's needed - i.e., CDR_FORCESPEED is not set, -force is not specified, and burnfree is not specified on the command line. As a general rule, hardware shouldn't be relied on to do any more than absolutely necessary, precisely to avoid this kind of problem with nonstandard behavior.
-- cdrecord hangs with kernel >= 2.6.10 and cyberdrive cdrw https://launchpad.net/bugs/28210 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
