Am 18.05.2018 um 10:50 schrieb Walid MOGHRABI:
If we're talking about the x2gothinclient-displaymanager package, this is not "NFS based or anything else" centric and it can be used for both modes. It just installs x2goclient and configures it to start at boot as a DM replacement.
This does not seem to integrate well with TCE-Live, if you look at how things are being started there ... so I don't see how it would bring any advantage to TCE-Live. Care to explain how you would use it? (i.e. which parts of TCE-Live would you ditch/change and pull in x2gothinclient-displaymanager instead)?
In my opinion, at first glance, we'd lose quite some functionality by replacing our TCE-Live start script with x2gothinclient-displaymanager.
I do agree that Live Build with no dependency to any network FS is the way to go. For what I can tell, a "full TCE" mode (which means booting to x2goclient, not mini desktop mode which highly depends on what you install in your image) can easily fit in a client with 1Gb memory, maybe less and this is far more reliable and faster.
The regular TCE-Live with the full-screen X2GoClient login will remain the standard TCE-Live for the time being. Minidesktop is for special use cases; we have a few commercial opportunities there that I would like to explore, that's why we're working on it in parallel. Also, a local browser is nice to have when you're doing web stuff that just won't work well over remote connections, say, Videoconferencing or anything that works fine in Firefox' new rendering engine when used locally, but sucks even with XRENDER enabled. Plus, Firefox has declared that XRENDER is going away soon, and not everybody wants to or can switch to the "Pale Moon" browser (which is going to stick with XRENDER for the foreseeable future).
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243