From: Joshua Wood <josh@utopian.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] a small error in /rc/bin/cpurc
Date: Mon, 5 Nov 2007 04:59:06 -0800 [thread overview]
Message-ID: <1649E555-A012-4CE2-86CF-CDEEC70334BB@utopian.net> (raw)
> > why the resistance to putting your machine into /lib/ndb/local?
>
> I want to have (if possible) only 1 place where I define IP address
> assignment.
> (+ dns, router, and in case of Plan9 fs+auth server)
> So if i need to change something, I don't need to meditate where else
> should I go.
> But maybe in future I will find some reason to make my /lib/ndb/local
> more accurate.
Maybe you have found a reason. If you want to have only one place to
define your ip address assignments, DNS, etc, etc, a look at the man
pages for dns(8), dhcpd(8) and ndb(6) could bring you much happiness.
You can use plan 9 to provide those infrastructure services for your
network.
The centralization of network config through ndb was the second of
two qualities that got us investigating plan9 at my company, and I
haven't seen another system that approaches the completeness and
elegance of this approach. DNS without manually making PTR records
and incrementing serial numbers? PRICELESS.
--
Josh
next reply other threads:[~2007-11-05 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 12:59 Joshua Wood [this message]
2007-11-05 13:27 ` Antonin Vecera
2007-11-06 21:57 ` maht-9fans
-- strict thread matches above, loose matches on Subject: below --
2007-11-07 5:51 Joshua Wood
2007-11-07 3:02 Joshua Wood
2007-11-07 3:17 ` erik quanstrom
2007-11-05 14:51 Joshua Wood
2007-11-03 17:12 Antonin Vecera
2007-11-03 21:30 ` erik quanstrom
2007-11-04 11:18 ` Antonin Vecera
2007-11-04 16:48 ` erik quanstrom
2007-11-05 7:31 ` Antonin Vecera
2007-11-05 10:18 ` arisawa
2007-11-05 14:02 ` Antonin Vecera
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=1649E555-A012-4CE2-86CF-CDEEC70334BB@utopian.net \
--to=josh@utopian.net \
--cc=9fans@cse.psu.edu \
/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).