-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wednesday 2007-10-17 at 01:42 +0100, David Bolt wrote:
Considering that a DVD+R holds 4483MB (without overburn),
4700 MB or 4.59 MiB.
Hum, I should have written 4.377 GiB, my thick fingers on the calculator :(
Capacity for a DVD+R is 4,700,372,992 bytes[0], 4,482.625MiB or
4.378GiB. A DVD+RDL has (quite) a bit less than double the +R capacity,
holding 8,547,991,552 bytes[0], 8152MB, or 7.961GiB.
Right.
<Snip>
It would also be possible to burn the tar file "raw", meaning
absolutely no directory overhead:
growisofs -Z /dev/dvd=sometarfile.tar -dvd-compat -speed=8
this way you can burn the 4700 MB.
There is just one slight problem. You can't verify the burn using md5sum
if tar uses the default block size. You need to set tar to use a 32KiB
block size so it matches the default block size growisofs uses.
Ah? Now, that's very interesting, it would explain a problem I had. But...
why would the internal organization of the image file matters? Do yo have
some doc or link on this?
It would mean that md5sum wouldn't read back the same bits that were
supposedly written, there is some thing else... padding?
Of course, reading it back needs a little trick (use dd, not mount).
Or even just use tar to do it:
tar xf /dev/dvd
tar xzf /dev/dvd
tar xjf /dev/dvd
expand a plain tar, gzipped or bzip2'd tar straight from then DVD.
Right.
[0] which the manufacturers round to 2 significant figures which ends up
being the familiar 4.7GB.
Ah... good to know.
[1] again, the manufacturers round to 2 significant figures which ends
up as 8.5GB.
I'll save this for future reference. When I wanted to know the exact size
of a dvd I found the 4.7 GB figure.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFHFWJ1tTMYHG2NR9URAkHeAJwP3ci6i8076J5ih2UL1leiUN3HgACeOAR6
ZIxMnaehkxiH9+6KDIGjZj4=
=XDhA
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
