From owner-freebsd-current@FreeBSD.ORG Wed Mar 4 03:29:48 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E02526EB; Wed, 4 Mar 2015 03:29:48 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B95CC8CB; Wed, 4 Mar 2015 03:29:48 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id t243TgAY092800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 Mar 2015 19:29:42 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id t243Tgxi092799; Tue, 3 Mar 2015 19:29:42 -0800 (PST) (envelope-from sgk) Date: Tue, 3 Mar 2015 19:29:41 -0800 From: Steve Kargl To: David Chisnall Subject: Re: Massive libxo-zation that breaks everything Message-ID: <20150304032941.GA92784@troutmask.apl.washington.edu> References: <54F34B6E.2040809@astrodoggroup.com> <54F35F29.4000603@astrodoggroup.com> <54F429EF.5050400@freebsd.org> <54F46536.8040607@mu.org> <54F4C03F.7030704@freebsd.org> <54F4FECB.90501@freebsd.org> <54F504EF.3030303@freebsd.org> <54F50F15.4050300@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-current@freebsd.org, Allan Jude X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Mar 2015 03:29:49 -0000 On Tue, Mar 03, 2015 at 09:09:43AM +0000, David Chisnall wrote: > > If your argument is about binary size, then it would be relatively > easy for us to add a version of libxo for static linking into the > versions in /rescue that only supported plain-text output, but > again, please quantify your objections: What is the size increase > that you're seeing and what kind of devices is this causing a problem for? > Well, since you asked, with libxo -rwxr-xr-x 1 root wheel - 20104 Mar 3 19:16 w* dynamic -rwxr-xr-x 1 root wheel - 1011688 Mar 3 19:17 w* static without libxo -rwxr-xr-x 1 root wheel - 16856 Mar 3 19:18 w* dynamic -rwxr-xr-x 1 root wheel - 974680 Mar 3 19:19 w* static 3.17 kB dynamic 36.14 kB static The output from w is fairly simple compared to what ifconfig or netstat or vmstat or ps or any number of other utilities generated. The use of libxo may have an impact on embedded systems with limited resources. Too bad the libxo supporters did not do the damage with a WITH_LIBXO knob. -- Steve