From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] passwd
Date: Tue, 2 Jan 2001 20:40:51 -0500 [thread overview]
Message-ID: <20010103014053.7DA0A199E4@mail.cse.psu.edu> (raw)
What I couldn't do was set a password. Passwd returns "protocol
botch: cs: can't translate address(net!$auth!ticket)." I assume
this is because it is a stand alone system. The system has a
NIC that I hope to use for printing &c on my LAN. Any workaround or
suggestions?
If you don't want to connect to the system
remotely, don't worry about it -- booting
standalone the password is never used.
If you do want to connect to it remotely,
you'll want to set up a standalone cpu/auth
server. plan9.bell-labs.com/sys/doc/start.pdf
has some info on that near the end.
Russ
next reply other threads:[~2001-01-03 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 1:40 rsc [this message]
2001-01-09 9:39 ` Bob Solomon
-- strict thread matches above, loose matches on Subject: below --
2002-05-23 14:27 presotto
2002-05-23 14:00 forsyth
2002-05-23 13:43 presotto
2001-01-02 19:53 presotto
2001-01-02 17:48 Bob Solomon
2000-12-30 16:40 [9fans] cron Russ Cox
2001-01-02 17:48 ` [9fans] passwd Bob Solomon
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=20010103014053.7DA0A199E4@mail.cse.psu.edu \
--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).