Computer Old Farts Forum
 help / color / mirror / Atom feed
From: david at kdbarto.org (David)
Subject: [COFF] Most folks here started their OS learning with Unix
Date: Thu, 10 Jan 2019 06:52:49 -0800	[thread overview]
Message-ID: <DAD6DC24-BEA9-489F-A27E-65CA9E913A17@kdbarto.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]

Myself it was v6 (most likely the typesetter version).

What I’d like to see discussed is how people today learn to write, enhance, design, and otherwise get involved with an OS.

When I was teaching at UCSD my class on Unix Internals used writing a device driver as the class project and covered an overview of the Unix OS using the Bach book. Even then (the late 80’s) it was hard to do a deep dive into the whole of the Unix system.

Today Linux is far too complex for someone to be able to sit down and make useful contributions to in a few weeks possibly even months, unlike v6, v7 or even 32v. By the time of BSD 4.1[a,b,c] and 4.2 those had progressed to the point that someone just picking up the OS source and trying to understand the whole thing (VM, scheduling, buffer cache, etc) would take weeks to months.

So what is happening today in the academic world to teach new people about OS internals?

	David


             reply	other threads:[~2019-01-10 14:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 14:52 david [this message]
2019-01-10 15:09 ` ralph
2019-01-10 15:23 ` clemc
2019-01-10 15:26   ` clemc
2019-01-10 15:39 ` crossd

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=DAD6DC24-BEA9-489F-A27E-65CA9E913A17@kdbarto.org \
    --to=coff@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).