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
