From: segaloco via TUHS <tuhs@tuhs.org>
To: steve jenkin <sjenkin@canb.auug.org.au>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Has this been discussed on-list? How Unix changed Software.
Date: Wed, 07 Sep 2022 02:33:20 +0000 [thread overview]
Message-ID: <lDhsor5coJUX_NeGLXqMQ2Gn_9Q7n5GC6fyl33r272_n2pACV4xWHduzy95B19KYYsxbHOS8zaUHNSNfEyfUOSXZ50lPUzibKFM7ZBsYl9Y=@protonmail.com> (raw)
In-Reply-To: <DF4161CD-6FFC-4957-9946-AEA1190B3DFA@canb.auug.org.au>
> I’ve read that Ken wrote the kernel with an eye to it being a coding exemplar.
> Deliberately wrote consistent, high quality code.
From UNIX Implementation:
What is or is not implemented in the kernel represents both a great responsibility and a great power. It is a soap-box platform on "the way things should be done."
- Ken Thompson, 1977
This paper can be found in the BSTJ Vol. 57, No. 6 as well as various "Documents for UNIX" compilations such as the Version 7 manual Volume 2.
- Matt G.
next prev parent reply other threads:[~2022-09-07 2:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 15:07 Douglas McIlroy
2022-09-06 17:13 ` Larry McVoy
2022-09-07 1:40 ` steve jenkin
2022-09-07 2:33 ` segaloco via TUHS [this message]
2022-09-07 4:08 ` Steve Jenkin
2022-09-07 13:08 ` Steffen Nurpmeso
2022-09-07 14:56 ` Larry McVoy
2022-09-07 21:27 ` Steve Jenkin
2022-09-07 22:36 ` Larry McVoy
2022-09-08 14:42 ` Paul Winalski
2022-09-08 15:02 ` Larry McVoy
2022-09-08 15:04 ` ron minnich
2022-09-08 15:52 ` Warner Losh
2022-09-08 16:47 ` Paul Winalski
2022-09-08 16:50 ` segaloco via TUHS
2022-09-08 17:58 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2022-09-06 19:04 Douglas McIlroy
2022-09-05 23:48 [TUHS] " steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07 4:00 ` steve jenkin
2022-09-07 14:58 ` John Cowan
2022-09-07 17:13 ` Paul Winalski
2022-09-08 14:12 ` Paul Winalski
2022-09-07 5:15 ` steve jenkin
2022-09-07 13:20 ` Dan Cross
2022-09-07 13:52 ` Steve Nickolas
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='lDhsor5coJUX_NeGLXqMQ2Gn_9Q7n5GC6fyl33r272_n2pACV4xWHduzy95B19KYYsxbHOS8zaUHNSNfEyfUOSXZ50lPUzibKFM7ZBsYl9Y=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=segaloco@protonmail.com \
--cc=sjenkin@canb.auug.org.au \
/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).