From mboxrd@z Thu Jan  1 00:00:00 1970
From: Corey <corey@bitworthy.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Wed,  5 Aug 2009 19:20:10 -0700
User-Agent: KMail/1.11.4 (Linux/2.6.27-gentoo-r8; KDE/4.2.4; i686; ; )
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200908051920.10243.corey@bitworthy.net>
Subject: [9fans] a few Q's regarding cpu/auth server
Topicbox-Message-UUID: 39c0dc14-ead5-11e9-9d60-3106f5b1d025


Just some scattered random questions I've accrued after successfully
getting a cpu/auth server up and running:


* I'm seeing an error on boot:

"/sys/log/cron: rc (cpurc): can't open: 'sys/log/cron' is a directory"

... not quite sure what to make of that. I guess I might have done
something wrong at some point, maybe related to the next question:



* Could anyone explain or tell me where I can find more information
regarding what all is going on with the following:

   con -l /srv/fscons
   prompt: uname bootes bootes
   prompt: uname sys +bootes
   prompt: uname adm +bootes
   prompt: fsys main
main: create /active/cron/bootes bootes bootes d775
main: create /active/sys/log/cron bootes bootes a664

... I've read con(1), and I can fathom the obvious basic premise:
I'm creating a user and assigning it to groups. But what is '/srv/fscons',
and what is 'fsys main' doing, and where can I find what other commands
are available and what they do?



* At one point I created a new user with 'auth/changeuser' that I didn't
need/want. What's the suggested means of removing this user?



* Similarly to the question above, how should I delete a user created
with uname via fscons?



* I'm somewhat confused with a bit of the process involved when creating
a hostowner for the cpu/auth server, and the (seemingly) many different
passwords which are created.

- a password is prompted/created when using auth/keyfs

- a password and a secstore key (prompted or created?) on first
reboot after nvram has been invalidated

- a password prompted or created when running 'auth/changeuser bootes'
which is supposed to match the password provided above?

... I only have a very limited understanding of how these all work together
and why; based on the somewhat limited and scattered and semi-incomplete
docs floating around out there. It's very difficult to piece this all together
coherently using just man pages, so I'm hoping someone can help me out.


* I hope I don't get beat up on this one (well, I hope I don't get too beat up
on _any_ of these questions...), but it seems strange that something as
important as a cpu/auth server would just go and boot up right into the
hostowner... apparently this a non issue - so what am I not understanding?



Thanks!