In article ,
 Robert Latest  writes:
> Hello,
>
> we're looking to replace the expensive, virus-ridden, wall mounted "Thin
> Client" Windows computers with something cheap and safe. The tasks are:
>
> - IP address over DHCP
> - some terminal windows (to telnet into an ancient mainframe)
> - web browser
> - no network connections accepted from the outside
>
> After power up and afterwards, the predefined applications must come up
> automatically. No login should be neccessary, and no user action should be
> required to open or move any windows around. Web browser and terminal
> windows should restart and connect to predefined addresses if closed by
> accident.
>
> As this device will be running 24/7 in an industrial production environment,
> worst-case maintenance must be a single power cycle to bring a crashed
> system up again.
>
> I'm familiar with running a Debian/dwm desktop system.
>
> Any suggestions on how to go about this?

It's not clear to me if you are still wanting the Pi to be a
thin client or not.

There are several pre-canned raspberry pi thin client solutions,
some free, some charge a license fee.

One key issue is if you expect to play video. If so, you will
need a solution like citrix which traps the mpeg stream at the
server, and pipes that across for decoding in the hardware codecs
on the Pi.  If you can make do without video, then you have lots
more options.

If you want to run directly on the Pi, terminal windows are no
problem. Modern web browser is too big to run with any performance.
Some of the cut-down browsers will perform better, but will not
provide a modern experience, will not handle some web sites
properly, and will feel old.

--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]

--- SoupGate-Win32 v1.05