>>>>> "UM" == Ulrich Mueller <firstname.lastname@example.org> writes:
UM> If we take the second route, then maybe it should be a more general
UM> solution, i.e. exclude all tiny files (man page or not) from
First, from a user’s perspective, not compressing small files is a good
thing. Man pages perhaps most of all, given makewhatis, et al.
(Think of all the C₁₂ which won’t be un-sequestered quite so soon. ☺ ;^)
Ideally, there would be some way to configure, per filesystem and/or per
directory, what constitutes a small file. If the fs uses fixed-size
blocks then anything already smaller than one block needn’t be compressed.
OTOH, if the fs supports partial block file packing, then a smaller
threshold may be better.
Even for large files, if the compression fails to save any blocks then
it may be better to leave it uncompressed.
That said, some backup strategies may be better served by compressing
all but the smallest files.
Good heuristics for the default compress-or-don’t threshold should cover
most systems, but the ability to easily override the default is desirable.
James Cloos <cloos@...> OpenPGP: 1024D/ED7DAEA6