The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Larry McVoy <lm@mcvoy.com>
To: Jon Steinhart <jon@fourwinds.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Macs and future unix derivatives
Date: Tue, 9 Feb 2021 17:41:23 -0800	[thread overview]
Message-ID: <20210210014123.GS13701@mcvoy.com> (raw)
In-Reply-To: <202102091900.119J0Gv9850825@darkstar.fourwinds.com>

On Tue, Feb 09, 2021 at 11:00:15AM -0800, Jon Steinhart wrote:
> While I use linux, it's no longer a system that I trust in any way.  It's
> huge, bloated, rats-nest undocumented code.  Yes, I know that a small
> percentage of people like Ted spend a lot of time on the code and therefore
> know it well.  But I find it an impenetrable mess.  When I first had a need
> to look at the UNIX kernel, it was easy to figure out what was going on.  Not
> so with linux.  Of course, I'm getting old and maybe not as good at this stuff
> as I used to be.

Jon, I think you might be old enough to have run v7, if not, like me, you
have read the Lions book and loved it.  That kernel didn't do much, it was
uniprocessor, block interrupts design, no networking, it was very basic.
Amazingly nice to read, but it didn't do a lot.

Which is part of the reason we liked it.  I loved SunOS 4.x but it was
also a uniprocessor kernel (Greg Limes tried to make it SMP but it was not
a kernel that wanted to be SMP).  I loved it because I could understand
it and it was a bit more complex than v7.

The problem space that kernels address these days include SMP, NUMA,
and all sorts of other stuff.  I'm not sure I could understand the Linux
kernel even if I were in my prime.  It's a harder space, you need to
know a lot more, be skilled at a lot more.

My take is we're old dudes yearning for the days when everything
was simple.  Remember when out of order wasn't a thing?  Yeah, me too,
I gave up on trying to debug kernels when kadb couldn't tell me what I
was looking at.

--lm

  reply	other threads:[~2021-02-10  1:41 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
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 [this message]
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=20210210014123.GS13701@mcvoy.com \
    --to=lm@mcvoy.com \
    --cc=jon@fourwinds.com \
    --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).