Re: [Cooker] ISO images - is a binary diff file possible ??
> howabout > > xdelta delta -9 beta3.iso rc1.iso beta_2_rc1_upgrade.gz > How about: rsync -av remote.mirror.site::/path/to/iso /localpath/to/iso --partial --progress --stats this will do effectively what diff does, and only brings down what is required. ie if the file is the same in many places, this will only bring down the differences, and give you an identical copy of the remote file. it usually saves me 500MB on a 600 MB iso (one version to the next) some times even more, sometimes less.
Re: [Cooker] ISO images - is a binary diff file possible ??
Is it relevant as to how the two data streams are compressed, we are interested in compressing the difference stream. might be to a pure maths type person, bit beyond mine howabout xdelta delta -9 beta3.iso rc1.iso beta_2_rc1_upgrade.gz assuming xdelta can handle 640M files ;-) it's been trundling along upstairs for about 10hrs, but its a p2-233 128M so it could take awhile. perhaps someone else could take a crack at it as well i tried it yesterday with 100M off the front of each iso, but can't remember the size of the result file. i stopped it in order to go for delta'ing the lot. i wouldn't have done that if the size wasn't quite small, maybe 30M if you were tracking mandrake, had pulled the first beta, and had the choice of another 640M or 150M download and 'patching' ?? Stephen R Parkinson
Re: [Cooker] ISO images - is a binary diff file possible ??
Ron Stodden <[EMAIL PROTECTED]> writes: > 2a all RPMs come already compressed RPMs are cpio archive + a rpm header (requirements, what is providing, description, date, version, changelog and the like). They're not compressed. most SRPMs content is compressed.
Re: [Cooker] ISO images - is a binary diff file possible ??
stephen wrote: > > Having only just finished downloading Beta3, the air became > slightly colourful when as browsing email I saw RC1 mentioned, > closely followed by a 'here we go again' feeling, my computer > is definitely moving out of my bedroom. > > I should perhaps mention my modem, that's why I waited for > a slightly longer lasting beta than 1 & 2 ;-) > > Questions:: > 1. Would a binary difference file be possible ? yes, through xdelta, using xdelta delta RC1.iso RC3.iso RC3.xd and then rebuild xdelta patch RC3.xd RC1.iso RC3.iso > 2. Would it necessaryily be significantly smaller ? it's not said, but could be. We don't know unless we try, but depends on how many RPM packages are changed and how they are placed in the ISO image. Generally if you do an xdelta between two RPMs (whose files differs only in a few bytes) the size of the "delta" file is near the size of the original file (because the gzipped stream is totally different). I never did that on two "almost" near .ISO image files. > 2a. How would it compress ? xdelta files are already gzipped. Note also that 99% of the ISO image contents contains RPM files, which can't be furthermore packed. > 3. If it was say 20-50%, would you produce one for the mirrors ? > 4. Would it be similar for 'Extension' cdroms ? Bye. Giuseppe.
Re: [Cooker] ISO images - is a binary diff file possible ??
stephen wrote: > I should perhaps mention my modem, that's why I waited for > a slightly longer lasting beta than 1 & 2 ;-) > > Questions:: > 1. Would a binary difference file be possible ? > 2. Would it necessaryily be significantly smaller ? > 2a. How would it compress ? > 3. If it was say 20-50%, would you produce one for the mirrors ? > 4. Would it be similar for 'Extension' cdroms ? 1 yes 2 yes 2a all RPMs come already compressed 3 Visit my web page: http://members.optushome.com.au/ronst/ and download the fast rsync downloader (no_sync.pl and rsync_exclude) that does all this. 4 The above is based on tree downloading and hd.img install and does not waste time and money with iso images or CDROM installs. As downloaded, it is tailored for English English and US international keyboard only - the hundreds of megabytes of other locale stuff is not downloaded. -- Regards, Ron. [AU]
