Tim: >> When one uses features like "burnproof" so that the burning process can >> pad out buffer underruns, and keep on burning until more data comes >> through, instead of halting, is that transparent to the (later) reading >> of the disc, or a likely cause of this sort of problem? Andre Robatino: > Due to the linux readahead bug, which has never been fixed, padding is > a Good Thing (as long as there's a little extra space on the disc to > allow it). I was thinking of the schemes that will insert padding in the middle of a burn, so the burn process can just keep on going, instead of having to pause (which a DVD+ disc can do), or abort completely (for media that can't simply pause burning). Rather than thinking about the end of the disc padding, so that discs end up with a particular desired size, or padding so that they don't have random data past the end. If the burning process had to pad out the middle with say 60 megs of padding space, that could (a) affect checksumming, and (b) cause you problems if you expected to read 650 megs of data off a disc by reading only the *first* 650 megs worth of bits on it. This is presuming that padding in the middle isn't transparent (i.e. done in a way that isn't noticeable when the disc is, later on, read). -- [tim@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
