OpeniBoot and iDroid – http://www.idroidproject.org/wiki/Installing_iDroid_(Windows)
Caveat – no GoogleApp store access so all app installs are to be done manually from .apk packages, see http://www.mascobz.com/3-places-to-download-android-apk/ for a few places to get those.
UbuntuLTSP (https://help.ubuntu.com/community/UbuntuLTSP) allows to boot thin clients via the network from a main Ubuntu LTSP server and run Ubuntu as if installed on the thin client. I tested this successfully using an HP Thin Client from a standard (as in not modified in any way after install) Ubuntu LTSP install (LTSP option available on the Ubuntu alternate install ISO). Pretty cool!
Took me a couple of internet searches to figure out but in order to boot a Thin Client from Ubuntu LTSP using PXE, here are the DNSMasq options required in DD WRT (ubuntu-ltsp and 192.168.1.78 are the name and IP address of the Ubuntu LTPS install). dhcp-no-override dhcp-boot=/ltsp/i386/pxelinux.0,ubuntu-ltsp,192.168.1.78
Well, I thought I would be clever by installing GUI tools to mount the drives (Device Storage Manager), luckyBackup (name is quite obvious) and Wake-On-Plan (to manage the computer going to sleep and waking up at specific times) but quickly found some issues (as a disclaimer, it is probably related to my set-up rather the tools themselves).
Device Storage Manager did mount my NFS drives fine but I couldn’t write to them until I edited /etc/fstab manually and added the UTF-8 option.
luckyBackup just kept giving my rsync errors (code 23 for what it is worth) in standard user mode and I couldn’t get it to run from the crontab as superuser so I ended up writing a 2-line rsync command myself and that seems to run fine (2.5 TB of data to go through so it is still running from this morning!)
Wake-On-Plan installed fine but the GUI just doesn’t open. I will try next to schedule a script with the rtcwake command and see how I get on.
The catch (and it took me a while to realize it) is that you can create everything through webmin APART from getting apache to listen to the new port if you are defining the host on a new port.
So you still need to edit /etc/apache2/ports.conf through Terminal and add a new line “Listen XXX” where XXX is your new port. Doh!