9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: [9fans] Which thing was harder for u to grasp relating Plan 9?
Date: Wed, 12 Jul 2006 13:09:34 +0200	[thread overview]
Message-ID: <8ccc8ba40607120409oa207237x1e944b906a9b3348@mail.gmail.com> (raw)
In-Reply-To: <6e35c0620607112049y49fd2963kb61f6f57c74c03a9@mail.gmail.com>

Thanks for your answers.

Just to clarify. The book is about using the system, not about internals.
I see that my mail did say other thing, sic.
Our introductory course to SO teachs them how to use the system, this
includes programming. Using both the shell and most of the system calls.
The reason is that I found that they only really understand the concepts when
they use them. I'm trying to teach the concepts in a practical way.

Going back to my question about the top-10, I remember that it was very
hard to me to understand why
bind / /
was there after I did a
bind -b whatever /

Now it seems clear and very simple, but it was not at all for me initially.

I'll save all your comments for another book that I plan to write
after I finish the
one on programming and using the system. So, thanks again.


  reply	other threads:[~2006-07-12 11:09 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
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 [this message]
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=8ccc8ba40607120409oa207237x1e944b906a9b3348@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).