9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jerry W Johnson jwjohn@ecst.csuchico.edu
Subject: Changes for cpuserver & pwd prompt?
Date: Tue, 15 Feb 1994 22:43:06 -0500	[thread overview]
Message-ID: <19940216034306.TBkTPaDlPQO-pQoMBG6vG1Ko4RQPK7thBNybQnsVKj4@z> (raw)

Hi,
is all that's required to bring up a machine as a cpuserver;
 	- enter "auth/adduser -h -p newmachinename" from an
	  authentication server.(then give newmachine a password)

	- enter the newmachine into cpurc

	- enter the changes of newmachine in /lib/ndb/local and
	  run mk again??

Anything else? (Hope I remembered all the changes. Keep getting
"authentication failed"). We've got an ipx that's been used as a terminal
fine, but has been fighting the idea of changing to a cpuserver. ;)
(The fs and other cpu/auth server are sparc2's).


AND, how might I get the pwd into my prompt? I know it's kind of
weenie, but I'm used to it! TIA. Regards, --Jerry





                 reply	other threads:[~1994-02-16  3:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19940216034306.TBkTPaDlPQO-pQoMBG6vG1Ko4RQPK7thBNybQnsVKj4@z \
    --to=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).