From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cagney To: Jason Molenda Cc: Jim Kingdon , DJ Delorie , overseers@sourceware.cygnus.com Subject: Re: ftp mirrors Date: Sat, 10 Jun 2000 04:19:00 -0000 Message-ID: <394223B7.A1A849E9@cygnus.com> References: <200006091545.LAA00938.cygnus.project.sourcemaster@envy.delorie.com> <3941CC03.B74B3373@cygnus.com> <20000610010132.A20997@shell17.ba.best.com> X-SW-Source: 2000-q2/msg00326.html Message-ID: <20000610041900.wktsniAE3LgetnkXcqJyPPGuqaASTZJ4arRQ1Dz0h50@z> Jason Molenda wrote: > We don't have the disk space for that. (try a df on sourceware and > imagine what the 3GB of ftp would expand to when uncompressed) > > More importantly, rsync has support for this problem already. > > dont compress > The "dont compress" option allows you to select > filenames based on wildcard patterns that should > not be compressed during transfer. Compression is > expensive in terms of CPU usage so it is usually > good to not try to compress files that won't com- > press well, such as already compressed files. > > The "dont compress" option takes a space separated > list of case-insensitive wildcard patterns. Any > source filename matching one of the patterns will > not be compressed during transfer. > > The default setting is > > *.gz *.tgz *.zip *.z *.rpm *.deb > > Looks like setting 'dont compress' to include .bz2 would be enough. That isn't what I'm thinking of. given a gzip file, rsync has effectivly random data. Given the file uncompressed and rsync can recognize internal sections. Tar balls, for instance change very little, however because they are compressed, rsync can't see that. Andrew