9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Which thing was harder for u to grasp relating Plan 9?
Date: Tue, 11 Jul 2006 11:58:21 -0700	[thread overview]
Message-ID: <1152644301.12989.35.camel@linux.site> (raw)
In-Reply-To: <8ccc8ba40607111152p228bc378i7b34b5f24baa036f@mail.gmail.com>

On Tue, 2006-07-11 at 20:52 +0200, Francisco J Ballesteros wrote:
> I´m writing a book for the introductory course in OS at urjc, that
> we teach using Plan 9. Most of it is a a lot of generic introductory
> stuff about the system.
> 
> I´d love to know the top-10 of "hard-to-get" concepts about the system,
> specially for new comers,
> to try to cover them.

  If you mean implementation concepts, then my list would
definitely include:

   0. the fact that devmnt.c is just that -- another dev*
      and how it functions.
   1. waserror & co.
   2. devdraw and how it multiplex everything internally
      without much help from rio.

Thanks,
Roman.



  parent reply	other threads:[~2006-07-11 18:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 18:52 Francisco J Ballesteros
2006-07-11 18:55 ` Rob Pike
2006-07-11 19:03   ` jmk
2006-07-11 18:58 ` Roman Shaposhnik [this message]
2006-07-11 20:18   ` Sascha Retzki
2006-07-11 20:29     ` Corey
2006-07-11 20:40       ` Sascha Retzki
2006-07-12  3:49     ` Jack Johnson
2006-07-12 11:09       ` Francisco J Ballesteros
2006-07-12 14:40         ` Richard Bilson
2006-07-12 16:22         ` Skip Tavakkolian
2006-07-12 16:41         ` csant
2006-07-12 18:45           ` Ronald G Minnich
2006-07-13  4:14             ` Russ Cox
2006-07-13  5:30               ` andrey mirtchovski
2006-07-11 21:50 ` David Leimbach

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=1152644301.12989.35.camel@linux.site \
    --to=rvs@sun.com \
    --cc=9fans@cse.psu.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).