9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: Reading/understanding OS code (WAS: Re: [9front] !#&%&^#*@ RIO!!!)
Date: Thu, 20 Dec 2018 20:20:49 +0000	[thread overview]
Message-ID: <1545337249.2013749.1614857264.05E046AB@webmail.messagingengine.com> (raw)
In-Reply-To: <CAFSF3XNzuvs5aMmGzaP1hiGxR2pRgJCOu_L3LSe53OEWnjkc5g@mail.gmail.com>

On Wed, Dec 19, 2018, at 8:02 AM, hiro wrote:
> please note that there is a whole book of commentery
> http://lsub.org/who/nemo/9.intro.pdf

9.intro.pdf contains:
> It is important to note that this book is not a reference for using an
> operating system nor a reference for Plan 9 from Bell Labs.  The
> user’s manual that comes installed within the system is the proper
> reference to use.  These lecture notes just shows you how things work,
> by using them.  Once you have gone through the course, you are
> expected to search and use the user’s manual as a reference.

I ran into trouble when I needed a quick, authoritative reminder, 
not 400 pages of lecture notes.

-- 
Progress might have been all right once, but it has gone on too long -- Ogden Nash


  reply	other threads:[~2018-12-20 20:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-13 11:23 [9front] !#&%&^#*@ RIO!!! cinap_lenrek
2018-12-13 13:28 ` Ethan Gardener
2018-12-18 22:47   ` Reading/understanding OS code (WAS: Re: [9front] !#&%&^#*@ RIO!!!) magma698hfsp273p9f
2018-12-18 23:41     ` Julius Schmidt
2018-12-19  7:44       ` Steve Simon
2018-12-19  8:19         ` hiro
2018-12-19  8:02       ` hiro
2018-12-20 20:20         ` Ethan Gardener [this message]
2018-12-20 20:12       ` Ethan Gardener
2018-12-21  8:22     ` Reading/understanding OS code -- documentation Ethan Gardener

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=1545337249.2013749.1614857264.05E046AB@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --cc=9front@9front.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).