Re: MIDI

On Sun, 2006-11-12 at 06:54, Craig White wrote:

The issue is that a thin station or a Celeron type 3.0 GHz box with a
60Gb HD and 512Mb are about the same price and if we simply consider the
Celeron box as disposable if we can't re-install everything, we don't
have to purchase the big iron fat server for the thin clients. But LTSP
is there if we decide to change course.

I'd expect new thin stations to draw less power and have a longer
life than a cheap desktop box, but for immediate savings you
can use just about any old PC or mac you have or can buy used.

A nice side effect of setting up a server with k12ltsp is
that it is automatically also prepared to handle remote X
logins and start sessions on demand via vnc. I don't remember
if freenx is included in the base or an extra yum install but
it is also very nice for remote or cross platform work so
that you only have to manage the Linux version of some programs
and only in one place. You can do that without k12ltsp but
it does all the setup work for you.

--
Les Mikesell
lesmikesell@xxxxxxxxx


--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: The Desktop Strikes Back [was Re: Newbie FAQ #2: Wheres the GUI?]
    ... Hence, if we really want thin clients, than we really should ... while programs executed on a remote server. ... remote desktop client/web browser/whatever!" ...
    (comp.lang.lisp)
  • Connection ended on "thin clients"
    ... I have a remote office that connects to our corp office via Remote Desktop. ... The "regular computers" seem to login fine to the Terminal Server, however, ... the 3 HP thin clients appear to have trouble connecting. ...
    (microsoft.public.win2000.termserv.clients)
  • client could not connnect across WAN
    ... When Compaq thin clients connect to a Win2003 Terminal ... Remote connections might not be ... Error started when server was ...
    (microsoft.public.windows.terminal_services)