From: Pat Barron <patbarron@acm.org>
To: tuhs@tuhs.org
Subject: Re: [TUHS] Paper discussing Unix boot process?
Date: Wed, 10 Apr 2019 21:06:56 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1904102046190.2402@booboo.lectroid.com> (raw)
The more I think about this, the more I'm sure I'm barking up the wrong
tree...
From bits and pieces I've been able to recall, the thing I am looking for
was not about Unix - it was about TOPS-20. It was a timeline of the
system bootstrap activities from power-on to the point where users could
log in. I still don't remember where I found it originally, but at least
now I'm pretty sure I've been looking in all the wrong places... I
believe it originated at CMU, but I don't know for sure that that's where
I originally located it.
The actual problem I'm trying to solve is, at this point in my
professional career, I'm starting to interact with a lot of people (even
experienced software developers) who just have no clue of what has to
happen to get a computer from the point of "power-on" to the point where
they can actually use it to do things. This makes me sad... So, I'm
looking for something that I can point these people to that could clue
them in... I think the whole bootstrap process is useful to understand
for a lot of reasons, partly because it makes you think about all the
little fiddly details that have to be attended to to make the computer do
what you want - when I was first learning about this, I remember being
particularly fascinated by what had to happen to prepare for that moment
at which you turn on the MMU, to make sure that the system continues
executing in a place you expect it to, in the right processor mode. I
know most people that I interact with are using Linux or Windows on
Intel-architecture machines, but the boot process for Unix on the PDP-10
or VAX (or even TOPS-20 on the PDP-10) I thought would be a much simpler
thing to understand. Though maybe that's the wrong thought process, maybe
I should just find something related to Linux that is comparable (even
though I think it's more complicated).
While searching, I also came across a decent presentation by a friend of
mine who teaches at CMU, and discusses hardware that people probably
actually work with right now, but I think it would be best consumed along
with the actual lecture that it goes with.
http://www.cs.cmu.edu/~410-f08/lectures/L20_Bootstrap.pdf
Maybe I'll find what I was originally looking for at some point, but after
spinning on this for most of the day, I don't think it's related to
Unix...
--Pat.
next reply other threads:[~2019-04-11 1:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 1:06 Pat Barron [this message]
2019-04-11 1:27 ` Charles Anthony
2019-04-11 2:26 ` Erik E. Fair
-- strict thread matches above, loose matches on Subject: below --
2019-04-17 5:35 Paul Ruizendaal
2019-04-17 18:26 ` Warner Losh
2019-04-16 12:52 Noel Chiappa
2019-04-13 18:35 Noel Chiappa
2019-04-10 18:02 Pat Barron
2019-04-10 18:14 ` Erik E. Fair
2019-04-10 18:28 ` Clem Cole
2019-04-10 19:05 ` Bakul Shah
2019-04-10 22:24 ` Clem Cole
2019-04-10 22:53 ` Warren Toomey
2019-04-11 1:45 ` Greg 'groggy' Lehey
2019-04-10 23:19 ` Bakul Shah
2019-04-11 4:52 ` Fabio Scotoni
2019-04-11 13:48 ` Clem Cole
2019-04-11 14:54 ` Dan Cross
2019-04-11 15:36 ` Clem Cole
2019-06-26 2:28 ` Peter Jeremy
2019-06-26 7:57 ` Bakul Shah
2019-04-10 16:51 Pat Barron
2019-04-10 17:20 ` Erik E. Fair
2019-04-10 17:57 ` Dan Cross
2019-04-19 22:31 ` Chris Hanson
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=alpine.LFD.2.21.1904102046190.2402@booboo.lectroid.com \
--to=patbarron@acm.org \
--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).