From: Corey <corey@bitworthy.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 2nd draft of the Cpu/Auth Server howto online
Date: Thu, 13 Aug 2009 04:02:40 -0700 [thread overview]
Message-ID: <200908130402.40599.corey@bitworthy.net> (raw)
http://www.p9dp.org/plan9-cpu-auth-server-howto.html
This is likely to be the final draft; it has been optimized in various ways and
I have thoroughly tested it multiple times.
Sure would be terrific if a few folks of varying degrees of experience with
Plan 9 could actually take the document for a real spin and confirm that
it works as advertised.
For those who are willing to test it - and who can set up a cpu/auth server
with their eyes closed - please realize it is important that you go through
the steps verbatim in order to provide a reliable assessment (of course,
this should be obvious).
Thankyou!
next reply other threads:[~2009-08-13 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 11:02 Corey [this message]
2009-08-14 0:36 ` Fernan Bolando
2009-08-14 1:01 ` Corey
2009-08-14 1:14 ` Corey
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=200908130402.40599.corey@bitworthy.net \
--to=corey@bitworthy.net \
--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).