From: Stuart Morrow <morrow.stuart@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Fsctotum per user instances?
Date: Mon, 8 Apr 2013 10:14:05 +0100 [thread overview]
Message-ID: <CABB-WO-8QUXvqUM7KWyuajyDCzhSZjX0xvFB6rh_NYbY-W7JjA@mail.gmail.com> (raw)
In-Reply-To: <CAG3N4d_c-r-_-QbGaX4tD+kB3TnFOP0RSm+hY7BommWQCPJsFA@mail.gmail.com>
Tip: Any time someone says read auth.ps, take it to mean read
nauth.pdf; auth.ps; nauth.pdf, where nauth.pdf is the slides at
swtch.com
In others words, read overview; details; summary.
I find the auth stuff to be some of the harder stuff to fully
understand, the existence of this thread corroborates that.
next prev parent reply other threads:[~2013-04-08 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 3:28 Rogelio Serrano
2013-04-07 5:25 ` a
2013-04-07 8:40 ` Charles Forsyth
2013-04-07 11:50 ` Rogelio Serrano
2013-04-08 8:52 ` Yaroslav
2013-04-08 9:14 ` Stuart Morrow [this message]
2013-04-08 9:19 ` Bence Fábián
2013-04-07 13:05 ` erik quanstrom
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=CABB-WO-8QUXvqUM7KWyuajyDCzhSZjX0xvFB6rh_NYbY-W7JjA@mail.gmail.com \
--to=morrow.stuart@gmail.com \
--cc=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).