From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9fca1fb4e22eca6ddc267ad1ed10bb1f@orthanc.cc.titech.ac.jp>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9grid.us
From: YAMANASHI Takeshi <9.nashi@gmail.com>
Date: Wed, 25 May 2005 13:39:22 +0900
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 53263e38-ead0-11e9-9d60-3106f5b1d025

> The difference is that standalone doesn't authenticate to
> its own file server.  The file server trusts the local connection
> in order to bootstrap.

The file server means fossil alone?  Or does it include ken fs
and/or kfs?  Could you give me any pointers to the source where
this separation occurs?

> You need to add a factotum key for the file server.

Supposing the following case, what key should I add to which factoum?
Now a fileserver (fossil) has one (and only one) key:

	user=sauron dom=tip9ug.jp

and a diskless cpu server which boots from the
fileserver has the two keys respectively in their factotums:

	user=sauron dom=tip9ug.jp
	user=grid dom=9grid.jp

Now, one can login to the cpu server using either of the following keys:
	user=nashi dom=9grid.jp
	user=nashi dom=tip9ug.jp

However, one can't login with the "user=grid dom=9grid.jp" key.
Using this key, cpu just finishes without any error message;
	term% cpu -h cpuserver
	term%     <-- cpu just exits
except the "prompt: attach main as grid: unknown user 'grid'"
on the fossil console.

The only difference between nashi and grid is that nashi is
registered to the fossil while grid is not.
--