GNOME Bugzilla – Bug 315068
use of -nopad for data tracks
Last modified: 2005-10-07 21:28:43 UTC
For data tracks (NAUTILUS_BURN_RECORDER_TRACK_TYPE_DATA) we use the -nopad option to cdrecord. It seems that in some cases this prevents a checksum verification of the resulting disc. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160191 http://www.sun.com/bigadmin/features/articles/burn_iso_images.html http://www.troubleshooters.com/linux/coasterless.htm https://bugzilla.ubuntu.com/show_bug.cgi?id=8499 Looks like it originates here: http://cvs.gnome.org/viewcvs/nautilus-cd-burner/cd-recorder.c?hideattic=0&r1=1.26&r2=1.27 Bastien, do you know why we are using -nopad?
Don't remember on top of my head, i must admit. Hence the "TODO" on that line.
Looks like Ross may have made the change. I've cc'ed him. Ross, will we break anything that you are aware of if we change the -nopad option?
-nopad is the default so it should Just Work. Adding random padding seems weird unless someone can produce a definitive reason why though.
Created attachment 51727 [details] [review] patch Seems that by default cdrecord writes in tao mode. We should be able to specify dao mode for all writes that start from the n-c-b frontend since we will always have an ISO or CUE. With this patch md5sums work reliably for me.
2005-10-07 William Jon McCann <mccann@jhu.edu> * nautilus-cd-burner.c (burn_cd): Always use NAUTILUS_BURN_RECORDER_WRITE_DISC_AT_ONCE for data written from burn:// the frontend since that can only be ISO and CUE files. Fixes #315068.