Trying to use gcombust to burn CDs in Linux last night… never made so many coasters in my life. Couldn’t figure out why, finally pulled the SCSI card and moved it to the Win machine, only to be beset by a ton of configuration and writing problems there as well (using Nero). Finally figured those out, but there are a dozen wasted CD blanks in the trash now. I don’t think I’ve ever made a blank in BeOS. Damn, Be got so much so right, made so much so easy.
Today found out that you pretty much have to change the priority level of the cd burning app in linux. One guy claims that
nice –15 gcombust &
will do the trick. That makes a certain amount of sense, but I’m not sure how to interpret this. Does it mean that:
A) The Linux scheduler is really dumb and can’t figure out anything for itself.
B) Linux is very coarsely multithreaded.
C) This is somehow “desired or expected behavior” and that a user so clueless that he didn’t know he had to do that to begin with has no business using Linux.