Date: Mon, 13 May 2013 00:25:35 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Ed Schouten <ed@80386.nl> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Eitan Adler <eadler@freebsd.org>, Dmitry Morozovsky <marck@rinet.ru> Subject: Re: svn commit: r250565 - head/etc Message-ID: <20130513002535.GB32639@FreeBSD.org> In-Reply-To: <CAJOYFBCdCQsU5ssf2mnMxOKRLbyz%2BHCMRTTBC9rZA9ha1mjMBQ@mail.gmail.com> References: <201305121523.r4CFNxBR055568@svn.freebsd.org> <alpine.BSF.2.00.1305121952120.44610@woozle.rinet.ru> <CAJOYFBCdCQsU5ssf2mnMxOKRLbyz%2BHCMRTTBC9rZA9ha1mjMBQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, May 12, 2013 at 11:37:48PM +0200, Ed Schouten wrote: > In fact, I think that for embedded systems, using xz compression would > even be better. Many of those systems are often more storage space > constrained than CPU constrained (e.g. a 200 MHz wireless device with > only 8 MB of flash). Speaking of embedded systems, we here at $work said no for xz (for compressing anything from initrd images to custom packages) precisely because it being notoriously slow. Really constrained environments certainly call for specific approaches, but just arbitrarily turning on xz compression on something as general purpose as syslog files is not the best thing to help one save space. If fact, I really doubt there would be any syslog files on filesystem with 8 MB of flash. :-) ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130513002535.GB32639>