From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: "Steve Simon" Date: Wed, 15 Oct 2008 11:22:14 +0100 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Newbie looking for pointers Topicbox-Message-UUID: 1e84a058-ead4-11e9-9d60-3106f5b1d025 The system hangs together through an auth system which is distantly related to kerberos. the file servers and auth servers share a host ID and password, by convention the name is "bootes". the username and password is stored in a tiny partition on the disk (nvram partition). this allows them to communicate securely. the classic beginers mistake (I made) was the user "bootes" must exist on the system and the password bootes has in the auth server must be the same one as is stored in the nvram. many auth problems become obvious if you run auth/debug setting up auth is really more about getting your network database (man ndb) correctly rather than keyfs and secstore which are pretty simple. fossil will perform two functions, it will serve files to the kernel that boots it (this is implied in the way fossil is started by the kernel, rather than a feature of fossil) and, if told to in its config (in the config block at the start of the fossil partition) it will serve 9p network requests from remote hosts. -Steve