A page in your DokuWiki was added or changed. Here are the details: Date : 2019/08/27 19:53 Browser : Mozilla/5.0 (X11; Linux x86_64; rv:60.9) Gecko/20100101 Goanna/4.3 Firefox/60.9 PaleMoon/28.6.1 IP-Address : 109.193.81.67 Hostname : HSI-KBW-109-193-081-067.hsi7.kabel-badenwuerttemberg.de Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1566935494 New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce Edit Summary: [History, Rationale, Outlook] - removed obsolete paragraph, updated list of Debian releases X2Go-TCE works with User : stefanbaur @@ -17,11 +17,10 @@ Besides, making changes to/updating the classic, NFS-based TCE (henceforth referred to as TCE-Classic) with the entire filesystem, not just its compressed image, spread out over the NFS share was rather finicky - with the current TCE-Live, you build and deploy a new image every time you make a change, and you can test it on a single client without interrupting your production environment. The //local storage// feature can also be used to create a portable version of both X2Go-TCE and X2goClient for Windows, sharing the same configuration, on CD/DVD/USB media. We've also received reports that TCE-Classic wouldn't work with Jessie, or at least it was very hard to get it to work. - Our TCE-Live works just fine with Jessie, and we expect it to work in Stretch and hopefully in Buster (Stretch+1) as well. - The one catch is that the live-build package in Debian/the Debian-Live project is currently looking for a new maintainer - so there is a slim chance that live-build might be removed from Debian Buster, especially if no new maintainer steps up and the live-build replacement that is currently in the works (called live-wrapper) contains all the required functionality of live-build by then. - + Our TCE-Live works just fine with Jessie, Stretch, and Buster as well. + ===== ThinClient prerequisites for all TCE-Live variants ===== * At least 1 GB of RAM //unless// you use non-NTFS local storage, in that case, 512MB or even 256MB might work - but would you really want to use a Client that has 4 Megabytes of free RAM (our test result with 256 MB RAM total) and no swapspace? * For clients with less than 1 GB of RAM and no local storage, you could also use ''httpfs='' or ''ftpfs='' instead of ''fetch='', or ''netboot=nfs nfsroot=ip-of-your-server-here:/path/to/x2go-tce-filesystem.squashfs'' when netbooting, but this will make you dependent on an uninterrupted network connection again * At least an i586-compatible CPU -- This mail was generated by DokuWiki at https://wiki.x2go.org/