From: Kim Shrier <kim@tinker.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] rio & acme & plan9
Date: Mon, 7 May 2007 13:00:02 -0600 [thread overview]
Message-ID: <038D1F1F-7497-495B-9735-7CC19E05FFBF@tinker.com> (raw)
In-Reply-To: <ffacae74ec753dc72a8b7c8871000d03@coraid.com>
On May 7, 2007, at 12:29 PM, erik quanstrom wrote:
> a cpu server is a shared service, assumed to be running all the time.
> a terminal is a personal machine that is not assumed to be up when
> the user is not logged in. you're supposed to be able to turn off
> your
> terminal when you go home.
>
Just to make sure I have this straight, a cpu server is not running
a terminal server as its console. The keyboard, mouse, and display
on the cpu server are not under the control of a terminal server.
> so the idea of running auth on a personal machine doesn't really make
> sense. and although you can run fossil on a terminal, this makes it
> harder to just turn the machine off.
>
That makes sense.
> so i think the minimum setup (outside of a stand alone laptop) needs
> at least a cpu/auth/file server and a terminal, or drawterm.
>
That is the setup I am going for (cpu/auth/file server and drawterm).
However, for someone who only has one machine, what is the preferred
setup and why?
I realize that the previous question could be an invitation to a holy
war. That is not my intent. I have been thinking about computers from
a UNIX perspective for a long time and I have a lot of inertia to
overcome. Explanations of motivation or why something is done the way it
is, is very instructive to me at my current state of non-understanding.
> i did run a standalone terminal+fossil for a while but with no
> authentication.
> not that it mattered -- there was no one to authenticate.
>
> - erik
>
Kim
next prev parent reply other threads:[~2007-05-07 19:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-04 20:08 Tom Simons
2007-05-04 20:13 ` erik quanstrom
2007-05-04 20:18 ` ron minnich
2007-05-05 2:17 ` Federico Benavento
2007-05-07 7:02 ` Wes
2007-05-07 17:57 ` Kim Shrier
2007-05-07 18:29 ` erik quanstrom
2007-05-07 19:00 ` Kim Shrier [this message]
2007-05-07 23:28 ` erik quanstrom
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=038D1F1F-7497-495B-9735-7CC19E05FFBF@tinker.com \
--to=kim@tinker.com \
--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).