From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Charles Forsyth on putting Unix on a diet.
Date: Fri, 27 Oct 2017 06:36:48 -0400 (EDT) [thread overview]
Message-ID: <20171027103648.4030118C08A@mercury.lcs.mit.edu> (raw)
> From: Steve Nickolas
> I personally believe a lot of code in modern operating systems is larger
> than the task requires.
The "operating" is superfluous.
Noel
next reply other threads:[~2017-10-27 10:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 10:36 Noel Chiappa [this message]
2017-10-27 13:03 ` Clem Cole
2017-10-27 13:23 ` Steve Nickolas
2017-10-27 21:51 ` Andy Kosela
2017-10-27 23:04 ` Larry McVoy
2017-10-27 23:15 ` Steve Simon
2017-10-27 23:39 ` Tim Bradshaw
2017-10-28 2:00 ` Bakul Shah
2017-10-28 2:34 ` Lyndon Nerenberg
2017-10-28 2:42 ` Lyndon Nerenberg
2017-10-28 6:38 ` Bakul Shah
2017-10-27 21:43 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2017-10-28 13:11 Norman Wilson
2017-10-27 21:30 Norman Wilson
2017-10-27 22:49 ` Chris Torek
2017-10-26 14:57 Doug McIlroy
2017-10-26 22:07 ` George Michaelson
2017-10-25 2:51 Dan Cross
2017-10-25 3:14 ` Larry McVoy
2017-10-26 17:27 ` Larry McVoy
2017-10-26 22:12 ` George Michaelson
2017-10-27 3:49 ` Steve Nickolas
2017-10-27 6:55 ` arnold
2017-10-27 7:30 ` Derek Fawcus
2017-10-27 9:44 ` David Arnold
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=20171027103648.4030118C08A@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).