From: forsyth@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm vs Autentication Server
Date: Tue, 24 Apr 2001 11:15:55 +0100 [thread overview]
Message-ID: <20010424101529.94D51199FE@mail.cse.psu.edu> (raw)
>>If even the latter request is too hard to honor,
>>then at least I would like to ask Plan 9 code owners to provide for ability
>>to start "authentication server"
>>manually, thus allowing to fully upgrade from Plan 9 terminal to Plan 9 CPU
>>server "on the fly",
>>i.e. without reconfiguring and rebuilding the kernel.
i think you might be able to do that, by running auth/keyfs (see
keyfs(4)) and appropriate variants of aux/listen in a name space in
which you've previously run authfs(4) to provide suitably named
replacement authentication files to allow you to set your own keys.
next reply other threads:[~2001-04-24 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-24 10:15 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-24 12:32 presotto
2001-04-23 15:39 rsc
2001-04-24 9:00 ` Alexander Povolotsky
2001-04-23 9:54 Alexander Povolotsky
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=20010424101529.94D51199FE@mail.cse.psu.edu \
--to=forsyth@vitanuova.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).