9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] sharing the ndb(6) database
Date: Mon,  6 Sep 2010 22:29:32 -0700	[thread overview]
Message-ID: <AANLkTikZzM51e0vCfwq9ZYmKVR0tTCXcjq7dL+UpWhP4@mail.gmail.com> (raw)

My new auth server is completely standalone:
it uses the kfs file system and boots off its own
(solid state) disk. The rest of the network, for
which it performs the authentication tasks, is
based on a separate file server node. The auth
server also runs dhcpd, tftpd, and a dns server.
As such, its /lib/ndb/local file contains a
description of the whole network, as well as
dns root stuff.

Now, the rest of the network also needs much
of the same info as the auth server, in order to
easily call each computer by sysname, etc..
This means that when a new node is added to
the Plan 9 network, changes will be needed
to be made in two places: the main network's
/lib/ndb/local and the auth server's /lib/ndb/local.
What's a better way to achieve this? Is there
some method by which the auth server can share
its ndb file(s) with the network? Or should it also
rely on the file server for the root filesystem, and
use local disks only for keyfs, secstore, etc.
databases?

Input and other suggestions welcome.


Thanks,
ak



             reply	other threads:[~2010-09-07  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07  5:29 Akshat Kumar [this message]
2010-09-07 13:58 ` erik quanstrom
     [not found] <000e0cd30b7cc254ed048fa5a30f@google.com>
2010-09-07  6:45 ` Akshat Kumar
2010-09-07  7:09   ` Lucio De Re
2010-09-07  7:13     ` Lucio De Re

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=AANLkTikZzM51e0vCfwq9ZYmKVR0tTCXcjq7dL+UpWhP4@mail.gmail.com \
    --to=akumar@mail.nanosouffle.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).