From: "James A. Robinson" <jim.robinson@gmail.com>
To: Stanley Lieber <sl@9front.org>,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Maintenance of an auth server files vs a dns+dhcp+tftp server
Date: Tue, 15 Nov 2016 19:22:57 +0000 [thread overview]
Message-ID: <CAPd04b4sChpfjuLfXqiPp7u6cZyvU0=9heHbds=3BYwuyzAjEw@mail.gmail.com> (raw)
In-Reply-To: <753998c8-7595-4f6a-bb94-e45c95dd9b42@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Ah, ok. I'll try that. Thank you!
On Tue, Nov 15, 2016 at 11:05 AM 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
>
>
[-- Attachment #2: Type: text/html, Size: 1768 bytes --]
next prev parent reply other threads:[~2016-11-15 19:22 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 [this message]
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='CAPd04b4sChpfjuLfXqiPp7u6cZyvU0=9heHbds=3BYwuyzAjEw@mail.gmail.com' \
--to=jim.robinson@gmail.com \
--cc=9fans@9fans.net \
--cc=sl@9front.org \
/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).