9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] network PC boot
Date: Wed, 22 Apr 1998 10:34:07 +0100	[thread overview]
Message-ID: <19980422093407.Z0kTlpLcCEiK3nuUOyZO1xZ4YjJHBU7Ug2tlF4apT4w@z> (raw)

>>It is also mentioned that the authentication server PC needs a local
>>disk, so it presumably can't be the cpu/terminal server that I wanted
>>to boot to the u9fs file system.

any Plan 9 cpu server, on any architecture, can be an authentication server.
the local disc is possibly `required' for the pseudo-nvram (eg, '#H/hd0nvram')
to store the authentication data.  in fact, the system
will prompt for all you need if you have got neither nvram nor disc,
so you can run, and i do run, cpu servers without discs.
the disadvantage is that they require manual intervention on a reboot.
then again, you needn't reboot too often.

note that if you need a cpu server to act as authentication server for your
file server and also want to run a terminal, you'll need at least three machines
(file server, cpu/auth server, and terminal(s)).
in your case, you're apparently using a u9fs server as file server.  fortunately,
someone once posted to this list (a reference to) an implementation of an il/auth
server for unix-like systems.  you could run that to provide basic authentication
on the same machine that runs u9fs.  (as it stands, u9fs doesn't authenticate
fully, although i suppose it could be changed to do so.)
the unix il/auth server might be enough to get you going, though.
i haven't tried it.




             reply	other threads:[~1998-04-22  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-22  9:34 forsyth [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-04-22  9:38 forsyth
1998-04-22  9:25 Digby

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=19980422093407.Z0kTlpLcCEiK3nuUOyZO1xZ4YjJHBU7Ug2tlF4apT4w@z \
    --to=forsyth@caldo.demon.co.uk \
    /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).