From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Some notes on running UNIX v6 in 2015, using SimH and a healthy dose of documentation
Date: Thu, 3 Dec 2015 10:42:00 -0500 (EST) [thread overview]
Message-ID: <20151203154200.7F88B18C086@mercury.lcs.mit.edu> (raw)
> From: Will Senn <will.senn at gmail.com>
> a deeper read will require the reader to have knowledge beyond what is
> required of most modern software developers (PDP-11 architecture,
> assembly language, and UNIX are prerequisite).
Well, for pretty much any _operating system_ (as opposed to applications),
one will need to know something about the details of the machine it is
intended to run on; depending on which part of the OS one is looking at, it
will be more or less. E.g. switching processes probably requires a fair
amount, since one needs to know about internal CPU registers, etc; whereas
working on the file system, one probably doesn't need to know very much about
the machine.
> It will also require access to a lab where the ideas covered can be
> experimented with.
Actually, Lions/V6 was used in operating systems courses using simulated
machines; one at MIT, 6.828 "Operating Systems Engineering":
https://pdos.csail.mit.edu/6.828/
used it for a while before the students started complaining about being
forced to learn an obsolete machine. They thereupon wrote a V6 clone for the
x86 architecture, 'XV6' (see the top of that page), which is apparently now
used for similar courses at quite a few other universities.
> The v6 kernel ... packs in features that were either unavailable in
> larger more established systems or may have been present in some form,
> but were orders of magnitude more lines of code and attendant
> complexity. It was and remains an amazing operating system and worthy
> of contemporary study.
I don't think you will find too many people here who disagree! ;-)
> So, I was thinking that next up, I would write up notes to help the
> modern reader engage with v6 more easily in order to follow works like
> Lyons.
Check around online to see what exists, first; there has been stuff written
since Lions! ;-)
Noel
next reply other threads:[~2015-12-03 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 15:42 Noel Chiappa [this message]
2015-12-03 18:54 ` Will Senn
2015-12-04 0:52 ` Greg 'groggy' Lehey
2015-12-04 21:33 ` Win Treese
2015-12-04 22:00 ` John Cowan
-- strict thread matches above, loose matches on Subject: below --
2015-12-03 15:21 Noel Chiappa
2015-12-03 17:27 ` Random832
2015-12-03 18:46 ` Will Senn
2015-12-02 21:37 Will Senn
2015-12-03 0:20 ` Warren Toomey
2015-12-03 2:37 ` Will Senn
2015-12-03 4:11 ` Dave Horsfall
2015-12-03 4:18 ` Will Senn
2015-12-03 6:05 ` Peter Jeremy
2015-12-03 12:59 ` John Cowan
2015-12-04 6:22 ` Dave Horsfall
2015-12-04 6:38 ` Greg 'groggy' Lehey
2015-12-04 14:52 ` John Cowan
2015-12-04 18:17 ` Ronald Natalie
2015-12-04 18:33 ` Gregg Levine
2015-12-04 22:36 ` Greg 'groggy' Lehey
[not found] ` <CAKt831GfmmKQ75TRy1tCmmbnx4CGLmjy12zns6-c+_oJB+h2dA@mail.gmail.com>
2015-12-04 19:13 ` SZIGETI Szabolcs
2015-12-04 12:41 ` Peter Jeremy
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=20151203154200.7F88B18C086@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
/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).