From: Henry Baragar henry@instantiated.on.ca
Subject: Plan9 tutorial
Date: Thu, 14 Sep 1995 22:12:36 -0400 [thread overview]
Message-ID: <19950915021236.d5RDnjg4_QAX38yj-EtRxW3uVhFReJObyUwP9wbK8g0@z> (raw)
As an experienced Unix user, I am constantly surprised by utilities that seem
to be missing in Plan 9 (I know, Plan 9 is NOT Unix). That is, I need to
learn the Plan 9 way (and break a few Unix habits) in order to raise my level
of comfort with Plan 9. Although the Plan 9 documents provide plenty of
technical detail, they don't provide as much "common usage" as I would like.
Any way, I was wondering if some one from the Computing Science Research
Center at Bell Labs could put on a Plan 9 tutorial. From the activity on this
mailing list (and news group) I think that you could get a good turn out,
particularly if you held it at the up-coming Usenix conference in January.
Henry
henry@instantiated.on.ca
When you stay on the tracks, ignoring the facts, you can't blame
the wreck on the train.
-- from the song, "You Can't Blame . . "
reply other threads:[~1995-09-15 2:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19950915021236.d5RDnjg4_QAX38yj-EtRxW3uVhFReJObyUwP9wbK8g0@z \
--to=9fans@9fans.net \
/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).