Live data from Hacker News

Running Raspberry Pis as Thin Clients with Ubuntu 14.04

uzerp.com

1–10 of 14 posts

Re: Running Raspberry Pis as Thin Clients with Ubuntu 14.04

#3

"Thin client" in this case means X Server.

In this case, the Raspberry Pi is an LDM client. More information is available on Wikipedia, and the LTSP wiki. Edubuntu also has good resources on LTSP, as it is integrated into the Distro!

Re: Running Raspberry Pis as Thin Clients with Ubuntu 14.04

#6
post #5

Just out of curiosity, HN seems like a good place to ask: Does anyone actually here use unix-likes in a multiseat fashion, like they were used 30-40 years ago? Like described here: https://en.wikipedia.org/wiki/Multiseat_configuration

Yes, I have been using Fedora this way for a couple years now (ever since systemd made this easy in Fedora 17). Two heads, one running MythTV (most of the time), the other is my workstation.

Re: Running Raspberry Pis as Thin Clients with Ubuntu 14.04

#7
post #5

Just out of curiosity, HN seems like a good place to ask: Does anyone actually here use unix-likes in a multiseat fashion, like they were used 30-40 years ago? Like described here: https://en.wikipedia.org/wiki/Multiseat_configuration

You will want this:

http://www.x.org/wiki/Development/Documentation/Multiseat/

And if you're on arch linux this is a good start:

https://wiki.archlinux.org/index.php/xorg_multiseat

Re: Running Raspberry Pis as Thin Clients with Ubuntu 14.04

#10

How's the screen refresh rate? I have an Arch distro on my Pi, used mostly for remoting purposes. RDesktop works really well, but the refresh rate is slow... 1-10 fps in most cases. I was hoping to bump it up to 50-60.

As long as you're using at least a 100Mb/s network (We use GbE), you should see a smooth experience. All works just as well as using a local machine, give or take some frames here and there. Just a forewarning, stay away from Google Chrome, and Chromium. They are awful to use with LTSP, you must deploy them as local apps as a fat-thin client solution, which isn't compatible with the Pi. The reasoning for this is that Chrome makes too many calls to the X server, and this causes horrible performance, you'll literally be watching chrome refresh, like loading an image over dialup.
Post reply on HN