9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@9front.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>,
	Anthony Sorace <a@9srv.net>
Subject: Re: [9fans] Maintenance of an auth server files vs a dns+dhcp+tftp	server
Date: Wed, 16 Nov 2016 10:31:51 -0500	[thread overview]
Message-ID: <6dc3a37f-461e-4388-9cf3-c8585f546722@email.android.com> (raw)
In-Reply-To: <35E88FD4-1AA6-49B2-8B27-4F07240B5FB2@9srv.net>

Anthony Sorace <a@9srv.net> wrote:

>I'm not sure there's a single "canonical" answer, but many
>installations have run the auth server off its own file system, as
>James originally described. It's been several years now so my memory
>could be fuzzy, but I believe this is what they did at the main Bell
>Labs installation. 
>
>> On Nov 15, 2016, at 14:05, Stanley Lieber <sl@9front.org> wrote:
>> 
>> "James A. Robinson" <jim.robinson@gmail.com> wrote:
>> 
>>> So in a canonical installation the auth server mounts its root from
>the
>>> file server?
>>> 
>>>> On Tue, Nov 15, 2016 at 10:47 AM Stanley Lieber <sl@9front.org>
>wrote:
>>>> 
>>>> 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).
>>>> 
>> 
>> Yes. You can arrange for hands-free booting by storing  the same
>authid/authdom/password in the nvram of both the file server and the
>auth server. I usually boot the auth server from a 9fat partition or a
>USB key, then tcp (actually, tls) mount the root file system from the
>file server.
>> 
>> sl
>> 

The reason I used the term "canonical" is because this was the arrangement described in the Plan 9 papers. The single file system was touted as one of the central features of the system, and one of its major benefits.

Example benefit: When a diskless system crashes, there is no danger of damage being done to the file system.

sl




      reply	other threads:[~2016-11-16 15:31 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
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 [this message]

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=6dc3a37f-461e-4388-9cf3-c8585f546722@email.android.com \
    --to=sl@9front.org \
    --cc=9fans@9fans.net \
    --cc=a@9srv.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).