[X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

[Walid MOGHRABI]

Alex has a customer (I think) that wants to see TCE-NFS being kept alive
- so while someone is actively maintaining it, we can keep it.

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.
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.


Regards,
Walid Moghrabi

TRAVAUX.COM
BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403
13591 AIX EN PROVENCE CEDEX 3

----- Mail original -----

De: "Stefan Baur" <X2Go-ML-***@baur-itcs.de>
À: ***@gmx.de
Cc: x2go-***@lists.x2go.org
Envoyé: Vendredi 18 Mai 2018 10:14:58
Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE

Alex is working on the classic, NFS-based TCE, that so far does not come
with a Window Manager.
Juri and I are maintaining the Debian-Live based TCE, where OpenBox is
included, because we were annoyed by X2GoClient's popups being inaccessible.

Got it, thanks! Are there plans of mergeing the two? Or for dropping
one of them?

Alex has a customer (I think) that wants to see TCE-NFS being kept alive
- so while someone is actively maintaining it, we can keep it.

IMO, the Debian-Live based TCE is the way to go, though, as it only
requires a few startup scripts to be maintained as patches, and a build
script. The NFS-based solution seems to require a lot more manual work
and constant changes to keep it running and supported on newer Debian
releases, at least that's my opinion and why I started building TCE-Live.

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 [phone] | USt-IdNr.: DE268653243
_______________________________________________
x2go-dev mailing list
x2go-***@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev
---
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

[Stefan Baur]

Post by 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.

Post by Walid MOGHRABI
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