From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Newbie looking for pointers
Date: Wed, 15 Oct 2008 11:22:14 +0100 [thread overview]
Message-ID: <c47cd1a935ea378fd499aa0ad002ddd3@quintile.net> (raw)
In-Reply-To: <b9800b70810150242w2b42bbc6v33651c35e8519a0@mail.gmail.com>
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
next prev parent reply other threads:[~2008-10-15 10:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 9:42 Martín Ferrari
2008-10-15 10:22 ` Steve Simon [this message]
2008-10-15 10:49 ` Martín Ferrari
2008-10-15 12:10 ` Charles Forsyth
2008-10-15 20:35 ` Pietro Gagliardi
2008-10-15 14:55 ` Steve Simon
2008-10-15 20:54 ` Martín Ferrari
2008-10-15 23:02 ` ron minnich
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=c47cd1a935ea378fd499aa0ad002ddd3@quintile.net \
--to=steve@quintile.net \
--cc=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).