From: Will Senn <will.senn@gmail.com>
To: M Douglas McIlroy <m.douglas.mcilroy@dartmouth.edu>,
tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Macs and future unix derivatives
Date: Mon, 8 Feb 2021 22:13:14 -0600 [thread overview]
Message-ID: <36a5b8f0-bfc0-120e-6226-bc107680e31e@gmail.com> (raw)
In-Reply-To: <CAKH6PiU4ZLEU25UHw=gryTFMBGeH40DLj333zG1WvBHO1BZsFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1285 bytes --]
On 2/8/21 9:58 PM, M Douglas McIlroy wrote:
>> Do they *really* want something which is just V7 Unix, with nothing else?
>> No TCP/IP, no hot-plug USB support? No web browsing?
>> Oh, you wanted more than that? Feature bloat! Feature bloat!
>> Feature bloat! Shame! Shame! Shame!
> % ls /usr/share/man/man2|wc
> 495 495 7230
> % ls /bin|wc
> 2809 2809 30468
>
> How many of roughly 500 system calls (to say nothing of uncounted
> ioctl's) do you think are necessary for writing those few crucial
> capabilities that distinguish Linux from v7? There is
> undeniably bloat, but only a sliver of it contributes to the
> distinctive utility of today's systems.
>
> Or consider this. Unix grew by about 39 system calls in its first
> decade, but an average of 40
> per decade ever since. Is this accelerated growth more symptomatic of
> maturity or of cancer?
>
> Doug
I couldn't have said it better. I was looking at 'man syscalls' and
shaking my head just a couple of days ago. I also just thought, hey,
wouldn't it be nice to get a printed copy of the latest manpages - uh,
that ain't gonna happen - 3000+ manpages, sheesh. Not sure I was
thinking 'man widget_toolbar' would provide me with any deep insights
anyway, maybe that's why its in mann.
Will
[-- Attachment #2: Type: text/html, Size: 1957 bytes --]
next prev parent reply other threads:[~2021-02-09 4:13 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 3:58 M Douglas McIlroy
2021-02-09 4:07 ` Adam Thornton
2021-02-09 4:13 ` Will Senn [this message]
2021-02-09 5:21 ` Andrew Warkentin
2021-02-09 5:29 ` Theodore Ts'o
2021-02-09 6:37 ` Andrew Warkentin
2021-02-09 16:13 ` Theodore Ts'o
2021-02-09 17:31 ` John Cowan
2021-02-09 19:06 ` Chet Ramey
2021-02-10 2:31 ` Andrew Warkentin
2021-02-09 19:00 ` Jon Steinhart
2021-02-10 1:41 ` Larry McVoy
2021-02-10 1:52 ` George Michaelson
2021-02-10 2:24 ` Larry McVoy
2021-02-10 2:44 ` Dan Cross
2021-02-10 3:10 ` Larry McVoy
2021-02-10 20:03 ` Kevin Bowling
2021-02-10 2:57 ` Warner Losh
2021-02-10 2:56 ` Warner Losh
2021-02-10 3:02 ` Larry McVoy
2021-02-10 3:53 ` Andrew Warkentin
2021-02-09 11:34 ` Thomas Paulsen
2021-02-09 18:29 ` Nemo Nusquam
-- strict thread matches above, loose matches on Subject: below --
2021-02-09 12:22 M Douglas McIlroy
2021-02-09 8:30 Bakul Shah
2021-02-08 18:11 Will Senn
2021-02-08 18:21 ` Larry McVoy
2021-02-08 18:32 ` Justin Coffey
2021-02-08 18:39 ` Larry McVoy
2021-02-09 1:59 ` Theodore Ts'o
2021-02-12 13:48 ` Angel M Alganza
2021-02-08 18:42 ` Henry Bent
2021-02-09 6:55 ` John Gilmore
2021-02-09 7:05 ` Michael Huff
2021-02-16 22:55 ` Greg A. Woods
2021-02-09 7:17 ` Will Senn
2021-02-09 19:02 ` Theodore Ts'o
2021-02-10 1:34 ` Larry McVoy
2021-02-09 22:59 ` Wesley Parish
2021-02-08 18:43 ` Dan Stromberg
2021-02-12 13:39 ` Angel M Alganza
2021-02-08 18:45 ` Thomas Paulsen
2021-02-25 22:45 ` Dave Horsfall
2021-02-08 20:07 ` Al Kossow
2021-02-09 5:10 ` Andrew Warkentin
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=36a5b8f0-bfc0-120e-6226-bc107680e31e@gmail.com \
--to=will.senn@gmail.com \
--cc=m.douglas.mcilroy@dartmouth.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).