The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Lions book
Date: Fri, 17 Jan 2020 09:50:24 -0500	[thread overview]
Message-ID: <CAC20D2Ncjeo5xhC2nGEgAR_KnxytuanGHK-bj3yun7tc1q3-+w@mail.gmail.com> (raw)
In-Reply-To: <202001171431.00HEV3gF020029@tahoe.cs.Dartmouth.EDU>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Indeed!!


FWIW I continue recommend it young hackers to read/examine/study before
they try to open something like the current Linux kernel.  The MIT xv6 work
 to put it on an Intel Architecture just adds to the value.

As the recent thread/argument on the merits/demerits of the use/abuse of
the preprocessor shows - simple and straightforward is easier to understand
regardless of the arguments wrt how helpful the macros can be.

6th Edition is clear and if you want to understand what it takes and how it
works, John's commentary it difficult to be.

On Fri, Jan 17, 2020 at 9:32 AM Doug McIlroy <doug@cs.dartmouth.edu> wrote:

> I learned from Marianne Lions that she's still receiving
> royalties from John's book. What a testimonial to both
> John and the system!
>
> Doug
>
-- 
Sent from a handheld expect more typos than usual

[-- Attachment #2: Type: text/html, Size: 1399 bytes --]

  reply	other threads:[~2020-01-17 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 14:31 Doug McIlroy
2020-01-17 14:50 ` Clem Cole [this message]
2020-01-17 15:23   ` Larry McVoy
2020-01-17 16:00     ` Warner Losh
2020-01-17 16:15       ` Clem Cole
2020-01-17 17:21     ` Adam Thornton
2020-01-18  3:35       ` G. Branden Robinson
2020-01-17 15:24   ` John P. Linderman

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=CAC20D2Ncjeo5xhC2nGEgAR_KnxytuanGHK-bj3yun7tc1q3-+w@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=doug@cs.dartmouth.edu \
    --cc=tuhs@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).