9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] making yourself at home
Date: Tue, 12 Jun 2007 22:33:06 +0200	[thread overview]
Message-ID: <d255458ef5967a68ef1ec0bfeeb06675@proxima.alt.za> (raw)
In-Reply-To: <20070612201251.GB30133@mercurius.galaxy>

>> reboot.
>
> Ok, but it just sounds strange for someone who has only been using
> Unix-like systems for the last 10 years.
>
Strange, but harmless.  More practical and trustowrthy than Windows'
Ctrl-Alt-Del.

> Ok, so a terminal is really a single-user "terminal", unlike a
> "workstation".
>
You can see the additional security in that, can't you?

> Hmmm, ... I'm used to say that a machine should only be powered on
> once and that you should login only once ... so rebooting is not an
> option.
>
Things change...  Note that in Plan 9 terminals and their users are
not tightly coupled.  None of the terminals ought to be customised to
a user's requirements or, putting it a different way, all of them are.
So "logging off" leaves the terminal where someone else can make use
of it.  Windows has a complex system to provide this type of "roaming
profile" and it's a nightmare, Plan 9 has it built in right at the
grass-root level and it works faultlessy.

> The long term plan would be to setup an auth-, a CPU- and a
> file-server and to use thin clients as terminals. However, I don't
> know yet (a) if the AMD Geode based thin clients I have are supported
> and (b) how to configure the server(s) to let them boot via PXE.
>
I think Ron Minnich has done a lot of work with the Geode, he may be
able to guide you there.

> I'll start with the setup of an auth/CPU/fileserver and then a thin
> client to see how all of this works.
>
That would be my choice, too, except I chose to run AUTH separately a
long time ago and I still am not sure that it wasn't overkill.  I
regret believing that AUTH can run on a 386: it does, but it's not
wise, every time you run AWK on a machine without floating point
hardware you crash it.  That gets irritating.

++L



  parent reply	other threads:[~2007-06-12 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 21:50 Frank Lenaerts
2007-06-07 22:05 ` Gabriel Diaz
2007-06-12 19:54   ` Frank Lenaerts
2007-06-13  8:54     ` Richard Miller
2007-06-07 22:09 ` erik quanstrom
2007-06-12 20:12   ` Frank Lenaerts
2007-06-12 20:23     ` john
2007-06-12 20:33     ` lucio [this message]
2007-06-12 20:58       ` Charles Forsyth
2007-06-07 22:22 ` Kris Maglione
2007-06-07 23:07 ` Federico Benavento

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=d255458ef5967a68ef1ec0bfeeb06675@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).