From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] cpu server/terminal combination
Date: Thu, 30 May 2002 14:13:25 -0400 [thread overview]
Message-ID: <c4f6724949cf1e6b49ae76791a17cff8@plan9.bell-labs.com> (raw)
If you are using a cpu server as a terminal,
then you should arrange for a new factotum to
be started before you run rio. By default the
factotum on cpu servers does not prompt for
keys, whereas the factotum on terminals does.
For example, wherever you run
plumber
upas/fs
rio
on startup, you could instead run
@{
rfork n
auth/factotum
plumber
upas/fs
rio
}
etc.
Russ
next reply other threads:[~2002-05-30 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 18:13 rsc [this message]
2002-06-05 10:03 ` Gabriel Diaz Lopez de la Llave
2002-05-30 18:24 rsc
2002-05-30 18:24 rog
2002-05-30 18:39 rsc
2002-05-30 18:40 rog
2002-05-30 18:57 rog
2002-06-05 12:18 presotto
2002-06-06 13:29 ` Gabriel Diaz Lopez de la Llave
2002-06-06 14:51 anothy
2002-06-06 17:23 presotto
2002-06-07 9:06 ` Gabriel Diaz Lopez de la Llave
2002-06-07 11:34 Fco.J.Ballesteros
2002-06-07 14:02 Russ Cox
2002-06-10 9:57 ` Gabriel Diaz Lopez de la Llave
2002-06-10 13:17 presotto
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=c4f6724949cf1e6b49ae76791a17cff8@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).