From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Fri, 12 Jul 1996 00:07:31 -0400
From: Steve Kotsopoulos steve@ecf.toronto.edu
Subject: Installation problems...
Topicbox-Message-UUID: 48245f90-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19960712040731.BKKfqDbHhF5ZxsCf-u6qolPUsKeFdY0nzanKeCjCMs8@z>

Jack Culpepper <jack@muddcs.cs.hmc.edu> wrote:
> Well, it looks as though this list is dead,

not at all

> I get to the point at which the installation "guide" tells me to do a
> 
> auth/changeuser [authid]
> 
> on the authentication server.  Fine.  I do it.  This is what happens:

Note that there were some corrections to the install document made after
the books were published. Make sure you are reading the up-to-date
version at http://plan9.bell-labs.com/plan9/doc/install.html

> % auth/changeuser oslab
> Password:
> Confirm password:
> Expiration date (YYYYMMDD or never) [return = never]: never
> changeuser: can't set key: file does not exist

I'd guess that your probably aren't running keyfs, or you didn't run wrkey.

My installation notes are at 
http://www.ecf.toronto.edu/plan9/info/steve/plan9.install-guide

Here's the section on setting up authentication:

Boot your cpu server, then (on its console):

% auth/wrkey                    to set passwd, authid,  authdom
% auth/keyfs                    serves /mnt/keys, from /adm/keys & #r/nvram
% auth/changeuser bootes        to add bootes (authid)
% auth/changeuser upas          so that upas' crontab will work
% auth/changeuser steve         set passwd for steve, then do the same thing
                                for every other user you added to /adm/users

I've never tried using anything except 'bootes' as my authid.

> How do I fix this?

Read the manuals, web pages and source code to try to figure it out,
and post here if you are stumped.

> Is Bell Labs still supporting this OS?

>>From the preface to volume 1 of the Plan 9 manuals:

"Plan 9 is made available as is, without formal support"