k3b should fork on verify

[PatRiehecky]

Binary package hint: k3b

I clicked burn before letting the image auto md5, then when it came time to verify it calculated the image md5sum and then the one of my newly burned Feisty install DVD. It would be dramatically more efficient to calculate both in parallel if the image md5 is not done since disk IO is faster than optical IO the image is sure to complete before the disk will. Just seems silly to wait on the one and then the other when both can be done concurrently....

[Ralph Janke (txwikinger)]

Thanks for submitting this report.

Why would you want to do this in parallel. Wouldn't you first want to find out if the image that you want to burn is ok (through checking the MD5) and then burn. If the MD5 fails, you wouldn't want to burn it anyway?

Thanks

[PatRiehecky (jcpunk)]

Good question!

I had MD5'd the image after the download. I kicked off the download and md5 over night so that when I got up the next morning I could see how it went. I already knew the image was good, so I went right past K3Bs pre-burn MD5.

What you have said is true, but if I skip the auto MD5 because I know the image is good (via any external check) it would be nice for K3B to MD5 both the image and the disk in tandum so that whomever doesn't need to wait the additional time (In my case with the Feisty DVD it was almost 14 minutes to calculate the Image and about 23 to calculate the DVD... can't save all 14 minutes, but saving even 7 would be nice)

[Ralph Janke (txwikinger)]

I suggest that this is treated as an additional feature (i.e. set to wishlist), so I confirm it.

[Didi Kohen (kohen-d)]

Did anyone forward this upstream?