Re: enable XZ to compress updates?

Hello Gilles,


> That could only be done in two steps.
> First, add xz in installed files, then compress next update with xz

OK for that.


> Uncompressing kernel modules before tar.xz creation allow a better
> compression.
> I add before tar.xz creation
>   -find /tmp/lib/modules -name *.ko.gz -exec gzip -d {} \;
>
> and this result to
> ls -s1 ipcop-1.9.19-update.i486.tgz
> 8548 ipcop-1.9.19-update.i486.tgz
>
> Of course, we would need the reverse after installation to not require more
> space on disk, and that will cost another bit of time.
> find /lib/modules/ -name '*.ko' -a -type f -exec gzip -nf9 {} \;

I don't like that.
I would very much prefer to leave files 'as-is' after building, so one 
day we can post file hashes (md5, sha1) of all IPCop files and people 
could then (automatically) compare their installation.
That would be an easy system to detect tampering (unlikely) or disk 
trouble (more likely).

Surely recompression should give the same result, but I think it too 
much trouble with small advantage.


Olaf

------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb