On Tue, May 22, 2012 at 4:57 PM, Charlie BRAVO <tech.cbkoncept@yahoo.com> wrote:
Hello to everybody,
This is our first post on x2go. Sorry if the question seems stupid or if we are not at the right place. We googled during days without finding a precise answer...
We have to use thin clients to connect to x2go-servers. Thus, we looked the "Installation of the X2Go TCE based on Debian" (http://wiki.x2go.org/doku.php/wiki:components:tce) That looks not bad :-) But we cannot use a PXE server. So, we need the "same" thing, but on a CD, or better, on an USB key.
We saw on archived posts (for example: http://www.mail-archive.com/x2go-dev@lists.berlios.de/msg02233.html) that this question was discussed, but not considered "making sense".
Well, that's not what was said. Mike pointed out that maintaining both does not make sense. The thing is, I'm quite sold on using the live-build infrastructure to create live images over the X2go TCE scripts, so I've hacked something together for our department's x2go environment.
The links which are given there (for example for "apt-get install x2go-rootfs") do not seem any more up to date... And the wiki "X2Go Live" (http://wiki.x2go.org/doku.php/wiki:components:x2golive) seems... empty.
The branch can be found here: https://code.launchpad.net/~siretart/x2go/x2go-live.oneiric
Note that this works for oneiric with the live-build packages that I have backported and put in my PPA.
I did not port this yet to precise, but I will eventually get to that.
For other reasons, we use a little "live-build" (http://live.debian.net/) but we are not experts.
Our first question:
After runnig "x2gothinclient_update" we have a "X2go TCE chroot" (under /opt/x2gothinclient/chroot/).
Is there a simple way to use this directory with live-build to build a binary image? That is, avoiding the "bootstrap" stage and the "chroot" stage, but starting directly with the "binary" stage?
I didn't see much point in doing that. The x2goclient, etc. packages are available form PPAs and installing .deb package with the live-build infrastructure are a much more straight-forward solution IMO.
Our second (more global) question:
It looks like the "X2go TCE chroot" (under /opt/x2gothinclient/chroot/) obtained with "x2gothinclient_create" is built in a similar way what live-build could do (are we wrong?).
AFAIUI, they have roughly the same goal, albeit live-build is much more generic and customizable.
As said previously (in the archive posts), it seems that the project x2go decided not to maintain both solutions: TCE and live-build.
But, *maybe* would-it be possible to maintain both results for a single effort? live-build can build different kinds of images (lb_config -b|--binary-images iso|iso-hybrid|net|tar|hdd) of which "net".
Instead of maintaining the "x2gothinclient_create" package, would it not be possible to just maintain the accurate options to be entered to "lb config", "lb build", etc... and the additional "includes" or "modified packages" or "hooks" and to let the user choose between the options "--binary-images" ("hdd" or "net")?
Thus both needs could be satisfied just with a single effort ;-)
If oneiric is OK for you, you can have a look at my oneiric branch. If you need precise, you can either forward-port it yourself (it will probably require some change due to a newer live-build version) or wait until I eventually find some spare time to do it.
Cheers, Reinhard.
-- regards, Reinhard