From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] building world using sh run in /usr/source in v6
Date: Mon, 31 Dec 2018 23:11:35 -0500 (EST) [thread overview]
Message-ID: <20190101041135.AC52818C073@mercury.lcs.mit.edu> (raw)
> From: Larry McVoy
> And cron is really 3246 bytes? And 2054 for init? Don't those seem too
> small? Linux's cron is 44472 and that's with shared libs
No, 3246 is the same as mine, and my init (which has a few changes from stock) is
2064.
I'm not surprised the later one is 44KB - that's in part due to the denseness
of PDP-11 binary (and the word-size is only 16 bits), but more broadly, I
expect that it goes to my complaint about later Unixes - they've lost, IMO,
the single most important thing about the PDP-11 Unixes, which is their
bang/buck ratio.
Noel
next reply other threads:[~2019-01-01 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 4:11 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-01 0:29 Will Senn
2019-01-01 0:39 ` Larry McVoy
2019-01-01 0:48 ` Will Senn
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=20190101041135.AC52818C073@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@minnie.tuhs.org \
/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).