9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
	Bakul Shah <bakul@bitblocks.com>
Subject: Re: [9fans] Inferno on Plan9
Date: Fri, 29 Dec 2017 21:11:56 +0000	[thread overview]
Message-ID: <348140488.6702383.1514581916226@mail.yahoo.com> (raw)
In-Reply-To: <348140488.6702383.1514581916226.ref@mail.yahoo.com>

On Fri, 12/29/17, Bakul Shah <bakul@bitblocks.com> wrote:
> On Fri, 29 Dec 2017 19:11:22 +0000 "Brian L. Stuart" <blstuart@bellsouth.net> wrote:
>>  I'm at the same point I usually am when getting ready to teach my winter term OS
>> course.
>
> Why teach about Inferno? Just curious.

It works out to be the sweet spot where a lot of considerations come
together.  First, I like to teach OS from an internals point of view.  I
feel that one should understand how one's tools work before using
them.  Second, like a lot of people of my generation, the way I really
learned about operating systems was from Lions commentary on
6th Edition.  For years, I had been thinking about writing an OS text,
but had been teaching from Tanenbaum using MINIX.  It was getting
somewhat problematic in the days when no one was running VMs
for everything and students were getting to where they didn't know
how to partition drives and run other OSs.  Then when Vita Nuova
released the Inferno source, it was like all the pieces fell into place.
It's well-written and carries a lot of the same ideas as Plan 9.  Students
don't have to allocate any extra hardware or even configure a VM.
It's small and simple enough that we can cover all the major elements
of it as well as the general principles in one term.  But they're able
to get some exposure to the internals of a real system and not just
something created for illustrative purposes.

With the ubiquity of VMs these days, a good argument could be
made for using Plan 9 in a VM for the course.  Maybe someday
I'll look at adding Plan 9 chapters to the book, but at least for now,
I'm finding Inferno works quite well.

BLS



       reply	other threads:[~2017-12-29 21:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <348140488.6702383.1514581916226.ref@mail.yahoo.com>
2017-12-29 21:11 ` Brian L. Stuart [this message]
2017-12-30 11:37   ` Andre Wingor
2017-12-30 13:41     ` James A. Robinson
2017-12-30 16:59       ` Andre Wingor
2017-12-30 18:38       ` Rui Carmo
2017-12-30 19:57         ` Andre Wingor
     [not found] <1477623683.7350613.1514746208525.ref@mail.yahoo.com>
2017-12-31 18:50 ` Brian L. Stuart
     [not found] <2051690395.6631505.1514574682474.ref@mail.yahoo.com>
2017-12-29 19:11 ` Brian L. Stuart
2017-12-29 19:14   ` Bakul Shah
     [not found] <1551839886.6502293.1514557846735.ref@mail.yahoo.com>
2017-12-29 14:30 ` G B
     [not found] <254996213.6156537.1514492938456.ref@mail.yahoo.com>
2017-12-28 20:28 ` Brian L. Stuart
     [not found] <1100617170.6129986.1514490844113.ref@mail.yahoo.com>
2017-12-28 19:54 ` Brian L. Stuart
2017-12-28 20:11   ` Alexander Kapshuk
     [not found] <1500946834.4036010.1514049193160.ref@mail.yahoo.com>
2017-12-23 17:13 ` G B
2017-12-23 17:57   ` Alexander Kapshuk
2006-05-29 19:48 [9fans] inferno on plan9 mattmobile
2006-05-29 19:39 ` quanstro
2006-05-29 22:35   ` Gabriel Ivanes
2006-05-29 22:38     ` Charles Forsyth

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=348140488.6702383.1514581916226@mail.yahoo.com \
    --to=blstuart@bellsouth.net \
    --cc=9fans@9fans.net \
    --cc=bakul@bitblocks.com \
    /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).