From owner-svn-src-head@FreeBSD.ORG Mon May 13 00:25:35 2013 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id A730EC65; Mon, 13 May 2013 00:25:35 +0000 (UTC) Date: Mon, 13 May 2013 00:25:35 +0000 From: Alexey Dokuchaev To: Ed Schouten Subject: Re: svn commit: r250565 - head/etc Message-ID: <20130513002535.GB32639@FreeBSD.org> References: <201305121523.r4CFNxBR055568@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, Eitan Adler , Dmitry Morozovsky X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 May 2013 00:25:35 -0000 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