The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: tuhs@tuhs.org, Doug McIlroy <doug@cs.dartmouth.edu>
Subject: Re: [TUHS] Lions book
Date: Fri, 17 Jan 2020 07:23:34 -0800	[thread overview]
Message-ID: <20200117152334.GJ28686@mcvoy.com> (raw)
In-Reply-To: <CAC20D2Ncjeo5xhC2nGEgAR_KnxytuanGHK-bj3yun7tc1q3-+w@mail.gmail.com>

On Fri, Jan 17, 2020 at 09:50:24AM -0500, Clem Cole wrote:
> 6th Edition is clear and if you want to understand what it takes and how it
> works, John's commentary it difficult to beat.

It's a good starting point but it's pretty outdated.  I like to go on and
on about how much I love the SunOS 4.x kernel but it is outdated as well.

I wish there was a v6/SunOS like kernel that was as clean but had good
support for SMP and NUMA and TCP offload (and probably a long list of
other useful stuff I've forgotten).

Teaching kids how a single threaded kernel works is cool but it's
also misleading, the world has gotten a lot more complex.  And while
the kernels of decades ago were clean and simple, I don't know of
a kernel to point people to that has the clean code that SunOS had.
Solaris isn't it, though it has some bright spots.  Linux is meh, it's
better than nothing by a lot but I would not point to it as "read this,
kid, you'll see the architecture".  It's not clear there is a good
answer.

  reply	other threads:[~2020-01-17 15:24 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
2020-01-17 15:23   ` Larry McVoy [this message]
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=20200117152334.GJ28686@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=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).