From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio & acme & plan9
Date: Mon, 7 May 2007 19:28:43 -0400 [thread overview]
Message-ID: <50ef2ef1ed9aa003480a105c5a9bea57@coraid.com> (raw)
In-Reply-To: <038D1F1F-7497-495B-9735-7CC19E05FFBF@tinker.com>
On Mon May 7 15:00:02 EDT 2007, kim@tinker.com wrote:
> 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.
yes. except in plan 9 a terminal is the opposite of a server so
they're generally refered to as terminals.
> 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 don't think anything is perferred about such a setup. however, i
ran a terminal with fossil only for about 6 months before i got a fs working.
this was acceptable for working on stuff.
> 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.
sounds like you're getting it. the papers in /sys/doc are still good, though
dated.
- erik
prev parent reply other threads:[~2007-05-07 23:28 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
2007-05-07 23:28 ` erik quanstrom [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=50ef2ef1ed9aa003480a105c5a9bea57@coraid.com \
--to=quanstro@coraid.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).