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
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? **Daniel
Rasberry Pi or Beagle Bone Black should be able to do all you need. You can
restrict things as much as you want in Linux. OK, power cycling crashed
Linux systems is not the best for file system integrity. On the other hand,
if you get rid of all unneccesary tasks, they ought to run for many months
at a time.
Tick, but a little more of a firewall setup challenge
No login should be neccessary,
? Not sure what you expect to move the windows if the user doesn't.
Mmm. possible but less simple. A watchdog script in a timer?
Mm. Some judicious use of read-only file systems may be indicated.
OR you might run it all in a virtual machine so that 'restore from
snapshot' is an option
Id personally go with Mint and probably Mate or XFCE as a staring point,
after deciding what partitions to create and whether or note read only
is the way to mount them
Then start to build up eh parts bit by bit.
I would imagine a startup script could be inserted into teh init.d
system to, after the window manager stars up launch what apps in what
window arrangements are desirable
It been a long time, but I think you can set command line options
somehow top preconfigure where and what size the windows ill be.
It may be, and I am way over my pay grade here, that you dont need a
window manager at all, but could just launch the apps into X-space.
That way there is no window manager to resolve etc etc.
Watchdog uses `ps` to ID what apps are running and restart them if they
"What do you think about Gay Marriage?"
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
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.
[email address is not usable -- followup in the newsgroup]
..but easy to check: run nmap from any other host that can see the screen
with the -pn option. When it sees nothing then you've got all ports
blocked from accepting outside connection requests.
... ish. Would be more reliable with the filing system on a hard drive or
an SSD than an SD card because both are somewhat harder to corrupt by
pulling the plug than an SD card is. Search previous history on this
newsgroup for threads about that. If you have a suitable 24x7 server you
can connect to and keep data on, that may be the best place to put the
flatscreen's filing system. You can use nfs or some other remote FS, e.g.
Samba, to mount it once the flatscreen device has booted off a local read-
only filing system.
Indeed, though if you want to put more than one full-screen window on the
display that could be problematic no matter what OS and applications you
run. Bit see my last point for more detail
Agreed, but it may combine with my next point.
Yes, that would work, and you could use frequently executed cron jobs to
detect that some application has fallen over and restart it, emailing yo
an alarm if it fails more than 'n' times in a row.
If you use a systemd based system, e.g. current Raspbian versions on a
RaspberryPi, then you can use a set of systemd services to (a) start
everything yo need at boot time and (b) to restart anything that fails
That may be simpler that using an rc.init script plus a set of cron
scripts, particularly as the old SystemVinit system is only present in
systemd installations to allow daemons that haven't yet been ported to
systemd to be run.
That will depend on the individual application and, to a lesser extent,
on whatever window manager you're using.
martin@ | Martin Gregorie
gregorie. | Essex, UK
On 2017 May 19 17:57:36, you wrote to Adrian Caspersz:
TP> Hardware aint the problem.
TP> Its the software config
especially considering that they're "thin clients" which effectively means that
they are loading into VMs which apparently lack administrative maintenance and
have been infested with PUPs and other unwanted nasties... sure, the hardware
is clean but that software image is ganked... it shouldn't be that hard to
clean them... no harder than cleaning a real machine with a real OS load...
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
... Ambition is a poor excuse for not having enough sense to be lazy.
Hmm. You are assuming it crashes in a way that will exit back to that?
When we did watchdogs in milspec stuff it tended to be within the app,
write a number that increments every time you write it, outside the app
(under timer interrupt) if the number doesnt get updated for n seconds,
destroy the process and recreate it. (or in many cases reboot the whole
That takes care of 'hung' processes as well
?it should be clear by now to everyone that activist environmentalism
(or environmental activism) is becoming a general ideology about humans,
I'm assuming the OP wants a fixed layout, eg browser window full height on
the left, then two terminal windows stacked on the right.
Something like that is doable without a window manager, but the problem then
becomes how to switch focus from one window to another. I don't think you
can do that without a window manager.
It's probably a case of carefully selecting a window manager that allows
launching of apps to particular sizes, and pinning of windows so they won't
move. Or one that has a 'tile windows' function that tiles them into
approximately the right layout.
we run around 12 PIs since more than 2 years 24/365. First with a normal
image, since last year with a ro rasbian. Have a copy of the sd card and a
problem with the card / FS is no problem. Before we use EEEPCs for this task.
The PIs are cups servers for printers and do a ssh with ssh_keys and get a
terminal programm for some information and for managing the print queues.
They are no thin clients.
When I was involved, it was.
Thin client boxes from the likes of HP are ridiculously expensive for
what they are. I pulled multiple 100's out of a nationwide office
deployment, these t5145 VIA Eden 500 MHz things had 512MB of ram and a
GPU that visibly couldn't move GUI drawn structures fast enough.
Scrolling was a joke, even on good network bandwidth.
The t5565 replacements built on Intel Atom something had better
graphics, 1GB of memory. Users complemented the better responsiveness,
But in the end we got fed up, and replaced them all with Windows 7 mini
PCs. Destroyed the Citrix terminal server farm, sat the PCs all on
authentication servers and migrated most of the office apps out on to
the google cloud.
Based on my experience looking at rendering speeds in a web browser, I
don't think the RPi (graphics/network) is fast enough to do a remote
desktop service, let alone anything more fancy.
Maybe it doesn't matter for the application, if not full desktop.
BTW I have 40 t5145 thin clients doing nothing, thought it would make a
nice linux standalone minimal feature machine with potential for
marketing to hobbyists. This guy had a similar evangelicalism.
Then someone went and launched the Raspberry Pi.....