Re: jigdo-lite debian-6.0.5-i386-DVD-1.jigdo
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 22 May 2012 08:45:52 +0800
littlehead <littlehead@126.com> wrote:
> I jigdo-lite debian-6.0.5-i386-DVD-1.jigdo, but when it finished, the
> debian-6.0.5-i386-DVD-1.iso is 4.7GB,larger than one DVD-R. I wonder
> why, and how to resolve it.
>
>
This may have something to do between how filesystems report file size,
and the difference between GB and GiB. (see 'man units' for an idea)
I jigdo'd the amd64 DVD for wheezy the other day under the impression
that it would fit on my 4 GB usb stick; but USB's and hard drives'
capacities are rarely what are reported. Completely blank, it was
still ~3905512000 bytes available on the USB with ~3994091520 bytes
(3.8 gigs) of the DVD ISO.
Here's what I ended up doing: I mounted the DVD ISO and told jigdo-lite
to download CD1, CD2, CD3, and CD4 of the same release set. For each, I
pointed to the mounted DVD ISO directory as a source.
I think I hit some sort of bug though involving reading the template
files properly when pointing to a remote .jigdo with a local image to
read from, so I'd sincerely recommend downloading both the .jigdo
and .template files for each CD image *first* if you end up doing it
this way. But...
Concerning why it's bigger---are you sure it is? I used to have ~700MB
files reported as ~737MB on my filesystem. When you open up Brasero (or
whatever burn program you're using) and select the medium for burning
does it say that the file will fit? The reason I ask is because:
http://cdimage.debian.org/debian-cd/6.0.5/i386/iso-dvd/
Says it should be about 4.4 gigabytes. If the md5sum checks out it
should definitely be burnable (and fit). Because it's actually 4.4.
Somebody will probably chime in explaining the difference between GB
and GiB pretty soon. :P Good luck! Hope you find the answers.
- --
Aubrey
"There are two types of people in the world: those who
can extrapolate from incomplete data."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBAgAGBQJPuxIuAAoJEDqgFXa7UFQOOnQH/3zxM8pM91J9fpfO8igGGfOI
Azbl4Emt4wSn5FFiZeLt8daGD0bJDZezTFwl1A2gORnN++6+IRKHb3+IS/BDXX8I
sECw2asdUxIIf0OWr1vBbPkn0zlXDFAHUUsl7Vdc91gkQY0DLU/cmvnZ5cD2f2OA
VZzgR9gLpi3MA13UwEFfVQeWtUYhY9JdlrU1OiRYw7LGgLVHED6PfsFyL7mG0gag
Fi4y5280xb4yFhXXQFO+MG2p3XJeTPD20JBl8x4rTCqfnZTyBFO/22uhfV4siy6m
kjHWtaVnLvtBYlYdaFvPZkbYezTGPSoHdD8+Ig98nPMTIkqjDbmcLT1Oi3PFNdA=
=VvcC
-----END PGP SIGNATURE-----
Reply to: