From: Stanley Lieber <sl@9front.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
"James A. Robinson" <jim.robinson@gmail.com>
Subject: Re: [9fans] Maintenance of an auth server files vs a dns+dhcp+tftp server
Date: Tue, 15 Nov 2016 13:47:23 -0500 [thread overview]
Message-ID: <814a9ee9-3cf7-453f-b6cb-0d3b10601100@email.android.com> (raw)
In-Reply-To: <CAPd04b6tULNjA5WA25Z0nSRemV38W9b4cVf2m0fFYAoH88Mkcw@mail.gmail.com>
"James A. Robinson" <jim.robinson@gmail.com> wrote:
>Folks,
>
>For a multi-machine network of Plan 9 services, would it be
>normal to have an authsrv machine that only runs that service,
>and uses a standalone local filesystem, and then have a separate
>server running dns+dhcp+tftp to PXE boot client machines. The
>latter would be backed by a 3rd machine that is the fileserver.
>
>I'm trying to figure out the optimal way to maintain the systems
>without duplicating work, and run now an auth+dns+dhcp+tftp
>server appears to require maintenance of two separate filesystems
>to manage the /lib/ndb/* and kernel files.
>
>
>Jim
The idea is that there is one file system shared by all the neighboring systems. The canonical Plan 9 installation comprises one disk file server and many diskless computing machines (auth servers, cpu servers, terminals).
sl
next prev parent reply other threads:[~2016-11-15 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 17:00 James A. Robinson
2016-11-15 17:10 ` Steve Simon
2016-11-16 0:21 ` cinap_lenrek
2016-11-16 0:24 ` James A. Robinson
2016-11-15 18:47 ` Stanley Lieber [this message]
2016-11-15 18:53 ` James A. Robinson
2016-11-15 19:05 ` Stanley Lieber
2016-11-15 19:22 ` James A. Robinson
2016-11-15 19:52 ` Ole-Hjalmar Kristensen
2016-11-15 20:06 ` Stanley Lieber
2016-11-15 20:12 ` cinap_lenrek
2016-11-16 13:21 ` Anthony Sorace
2016-11-16 15:31 ` Stanley Lieber
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=814a9ee9-3cf7-453f-b6cb-0d3b10601100@email.android.com \
--to=sl@9front.org \
--cc=9fans@9fans.net \
--cc=jim.robinson@gmail.com \
/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).