Date: Fri, 2 May 2003 19:24:46 +0200 From: Matthias Buelow <mkb@mukappabeta.de> To: Tim Robbins <tjr@FreeBSD.ORG> Cc: current@freebsd.org Subject: Re: HEADS UP: bzip2(1) compression for manpages, Groff and Texinfo docs Message-ID: <20030502172446.GA18677@moghedien.mukappabeta.net> In-Reply-To: <20030502153334.A70914@dilbert.robbins.dropbear.id.au> References: <20030502011307.GA82420@sunbay.com> <20030502153334.A70914@dilbert.robbins.dropbear.id.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Robbins writes: >I don't mean to sound rude, but what is the justification for this? I, of course being just an ignorant user, see no justification for replacing the default compression method for manpages; a block ordering compressor like bzip2 is only really useful for large data sets, surely not for a couple kilobytes of manpages. One should test whether (on a slower machine) bzip2 really slows down things much; I would think that reformatting the pages with nroff far outweighs the cost of uncompressing in any case, but still. IMHO using compress or gzip --fast would be fully sufficient and make decompression faster aswell. I mean, disks are getting larger every month, and I never had problems with manpage sizes when I was running on 250MB disks either in the past. My worst experience with bzip2 dates back several years, when I was using it to decompress a multi-megabyte file on an 8 meg machine... because of bzip2's much larger working set, the machine was trashing for hours, with the result of breaking the disk where swap was located on. Of course that is unlikely to happen with small manpages. -- Matthias Buelow home: mkb/at/mukappabeta.de uni: mkb/at/informatik.uni-wuerzburg.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030502172446.GA18677>