From owner-svn-src-all@FreeBSD.ORG Tue Jun 16 04:58:02 2015 Return-Path: Delivered-To: svn-src-all@hub.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 2630C7D2; Tue, 16 Jun 2015 04:58:02 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CDDD9B1A; Tue, 16 Jun 2015 04:58:01 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by qcbfz6 with SMTP id fz6so1477220qcb.0; Mon, 15 Jun 2015 21:58:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=iq05hNOqySidNYjILJ2ioBphm8nN7onYl8e3uvH1J9w=; b=CNy6IQSW3xXNL3dLQ9fcOTjvCou7h19IAw0G66faVZSrds44Xw2+Dzf9+QoyOV9hfN fZVq0n2r5c4jRNw8eFZTtK0tVIeECnSaCOr6oW7gkXFLwgQFCD8Jhzed4uBb9q1IyKOB tkosdVNN3oxA7l1WsH0TMg2mVtmgSu77AfNEIs58Td7iDGIdUE6mczvYznX2s/Flt2T3 rCIZTzwjLJ8rGiNT7fppYlmsapGAExnq1Gh57ZXnoa8AwFWH4eR8iLvnnJdawYCC4ecw BRayJ5NwRd1JuWAPdpsROdfUUk12XQDFFjk64CHWzdY7VXBA6n+Hq/y+IgvWH5w4R6vf GmPQ== MIME-Version: 1.0 X-Received: by 10.140.91.23 with SMTP id y23mr1333921qgd.90.1434430680880; Mon, 15 Jun 2015 21:58:00 -0700 (PDT) Received: by 10.140.98.73 with HTTP; Mon, 15 Jun 2015 21:58:00 -0700 (PDT) In-Reply-To: <557F8001.4020401@freebsd.org> References: <201506100127.t5A1RdX6051959@svn.freebsd.org> <20150612204309.11dd3391@kan> <20150613024916.GA98218@troutmask.apl.washington.edu> <1434208622.1415.57.camel@freebsd.org> <557C661F.8080104@freebsd.org> <860017ED-D754-450C-865D-2D81A30C2212@xcllnt.net> <20150614002640.GA2746@troutmask.apl.washington.edu> <557E4C3D.5080602@freebsd.org> <2CFE8F01-98B8-403C-BE1F-57D6F2368BE3@gmail.com> <557F8001.4020401@freebsd.org> Date: Mon, 15 Jun 2015 21:58:00 -0700 Message-ID: Subject: Re: svn commit: r284198 - head/bin/ls From: NGie Cooper To: Julian Elischer Cc: Adrian Chadd , Craig Rodrigues , "src-committers@freebsd.org" , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" , Marcel Moolenaar Content-Type: text/plain; charset=UTF-8 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2015 04:58:02 -0000 On Mon, Jun 15, 2015 at 6:46 PM, Julian Elischer wrote: > On 6/15/15 1:34 PM, Garrett Cooper wrote: >> >> On Jun 14, 2015, at 20:53, Julian Elischer wrote: >> >>> On 6/14/15 10:48 AM, Adrian Chadd wrote: >>>> >>>> On 13 June 2015 at 18:22, Craig Rodrigues wrote: >>>>> >>>>> On Sat, Jun 13, 2015 at 6:00 PM, Adrian Chadd >>>>> wrote: >>>>>>> >>>>>>> I guarantee that no matter what you've worked on, there's >>>>>>> approximately five orders of magnitude of shipping devices whose >>>>>>> entire storage space can be measured in 1 digit megabytes. Each year. >>>>>> >>>>>> (And yes - there's an appreciable set of them for which freebsd boots, >>>>>> runs and keeps running on them.0 >>>>>> >>>>>> You can buy em too, some of them even under $60. >>>>> >>>>> Can FreeBSD now not run on these systems because of libxo? >>>> >>>> It's a tight squeeze as it is. Running in 8MB of flash (even if it's >>>> compressed) is still an exercise in "what can you cut out." >>>> >>>> My point isn't that it isn't running because of libxo; my point is >>>> that arguing about "embedded" involving "lots of storage" is woefully >>>> incorrect and will continue to be until those gigabytes of storage are >>>> available for a penny. Which yes, I'm guessing will happen in my >>>> career - but it's also quite likely code bloat will continue to chase >>>> that upward. >>> >>> do we have a WITHOUT_LIBXO option on sources? I believe we should.. >> >> +1. I would be more than happy to implement it by stubbing out the >> majority of the macros to something less invasive, but it might be a bit >> before I do that. >> Thanks, > > but that wouldn't remove the bloat within the apps.. just make it use null > calls. That was the idea. Make it like "libnxo" or something, a dummy library like libnetbsd with weak symbols that can be optimized away by the compiler...