From: imp@bsdimp.com (Warner Losh)
Subject: [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split
Date: Thu, 2 Feb 2012 15:47:24 -0700 [thread overview]
Message-ID: <E5C6A964-1931-4EB9-9B62-303309FDDAA6@bsdimp.com> (raw)
In-Reply-To: <CAGSRWbiJesxtoC38_FEZM7_jMa3cvx=SUjT+nUoGd5irxr_ajg@mail.gmail.com>
On Feb 2, 2012, at 3:29 PM, Tim Newsham wrote:
>> Thankfully, most binaries are dynamic these days, which saves a ton of space on / (as a percentage of what's used).
>
> you're kidding, right? Disk space of binaries?
> (I still wish "du" had a "-$" flag that pulled info from a recent price
> database).
No. I'm not kidding.
Remember that these systems exist in more places than on monster-sized hard-disks. Embedded systems had limits of 4MB, 8MB or 16MB when these patches were done. While NAND has grown so that 64MB or 256MB parts are more common on boards, the savings is still rather substantial and allow for additional functionality. The space savings rivals 'crunchgened' binaries (think busybox). Savings between 32MB and 64MB is only a few $$$, but if you ship a million of something, the savings can be substantial.
In addition, having everything link in shared libraries makes doing security updates much easier.
Warner
next prev parent reply other threads:[~2012-02-02 22:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 19:16 A. P. Garcia
2012-01-31 19:27 ` Warner Losh
2012-02-01 11:12 ` Jose R. Valverde
2012-02-01 17:35 ` Warner Losh
2012-02-02 13:32 ` Random832
2012-02-02 17:24 ` Warner Losh
2012-02-02 17:36 ` John Cowan
2012-02-02 18:10 ` Warner Losh
2012-02-02 21:14 ` Dave Horsfall
2012-02-02 21:49 ` Warner Losh
2012-02-02 22:29 ` Tim Newsham
2012-02-02 22:47 ` Warner Losh [this message]
2012-02-02 22:59 ` Lyndon Nerenberg
2012-02-02 23:33 ` Warner Losh
2012-03-13 16:09 ` [TUHS] ASR 37 teletype desired by LCM / Vulcan.com John Foust
2012-02-02 22:53 ` [TUHS] Understanding the /bin, /sbin, /usr/bin, /usr/sbin Split Lyndon Nerenberg
2012-02-02 23:35 ` Warner Losh
2012-02-03 11:10 ` Tim Bradshaw
2012-02-03 15:22 ` Jose R. Valverde
2012-02-03 16:06 ` Ronald Natalie
2012-02-03 16:09 ` Steve Nickolas
2012-02-02 17:40 ` Warner Losh
2012-02-02 18:02 ` Tim Newsham
2012-02-02 13:45 ` Tim Bradshaw
2012-02-01 9:26 arnold
2012-02-02 13:35 ` Tim Bradshaw
2012-02-02 13:49 ` Larry McVoy
2012-02-02 23:16 Norman Wilson
2012-02-02 23:37 ` Carl Lowenstein
2012-02-02 23:58 ` John Cowan
2012-02-04 19:34 Pepe
2012-02-04 21:05 ` Lyndon Nerenberg
2012-02-05 8:38 Hendrik Jan Thomassen
2012-02-05 10:13 ` Jaap Akkerhuis
2012-02-05 17:15 ` Warner Losh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E5C6A964-1931-4EB9-9B62-303309FDDAA6@bsdimp.com \
--to=imp@bsdimp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).