Am 21.02.2014 18:52, schrieb Jos: Hi all, Althoug this topic is some months old, I realy would like to ask Stephan if he could elaborate some more on the >>self updating setup in the background<< from his minimal distro. Is it perhaps similar as the concept used by CoreOS as mentioned under Technical Details on their page,http://coreos.com/using-coreos/updates/
Regards, Jos.
Am 21.02.2014 18:52, schrieb Jos:
Thanks for the answer, i am now installing the thinclient package on a kvm virtual machine. One thing that I noticed on the wiki is this writing: X2Go TCE requires a local area network (LAN) that is at least switched at 100MB/s. The X2Go Thin Client chroot distribution is not designed to work over the internet or on low bandwidth connections This would mean that the pxe server can only be operated on LAN?
It is possible to PXE/TFTP/HTTP-boot over the internet, using gPXE or iPXE, but expect it to boot really slow.
Me, I'm using a minimal distro that can either run as a static image from CD/USB or as a self-updating (it queries the server for a newer release, downloads it in the background if there is one, then switches the next reboot to the downloaded copy) image on writable media.
Ccurrently tested and known to work:
- ext2/3 (ext4 will most likely work too)
- vfat
- ntfs
-Stefan
Am 08.07.2014 12:14, schrieb Jos:
Am 21.02.2014 18:52, schrieb Jos: Hi all, Althoug this topic is some months old, I realy would like to ask Stephan if he could elaborate some more on the >>self updating setup in the background<< from his minimal distro. Is it perhaps similar as the concept used by CoreOS as mentioned under Technical Details on their page,http://coreos.com/using-coreos/updates/
Me, I'm using a minimal distro that can either run as a static image from CD/USB or as a self-updating (it queries the server for a newer release, downloads it in the background if there is one, then switches the next reboot to the downloaded copy) image on writable media.
CoreOS sounds pretty similar to my concept, yeah.
Only that I'm using a "classic" Debian Wheezy live image. I'm not using Chef, Puppet or etcd as it is one standard image for all machines - since we're talking about Thin Clients here.
In my setup, there's a background job that triggers after a random timer has expired (so that the clients don't hit the server at the same time). That background job can pull the image via wget or rsync, which allows you to limit the used bandwidth, so you don't slow down the user working on the client too much.
Once the download is complete, the boot manager entry is changed so that it will boot the other partition at the next reboot.
-Stefan
-
Jos -
Stefan Baur