- Iso2god unable to locate default.xex update#
- Iso2god unable to locate default.xex portable#
- Iso2god unable to locate default.xex free#
#export LBX2GO_ARCH_MODEL='Pi4' # you can also set this to 'Pi3'. # export LBX2GO_ARCH='-architectures i386 -linux-flavours 586' # 32-Bit, smallest memory footprint - not available on buster # 32-Bit, larger memory footprint, but faster performance on i686 and newer
Iso2god unable to locate default.xex free#
# (feel free to use long or short options) # Select ONE of the following LBX2GO_ARCH lines and comment out the others # NOTE: As of, buster builds are only available via the github repo and for the feature/openbox-magic-pixel-workaround-buster and feature/mate-minidesktop-buster branches # NOTE: Add "-stretch" to the end of the LBX2GO_CONFIG string to create a stretch build, and "-buster" for a buster build # this one loosely corresponds to "heuler" # export LBX2GO_CONFIG='git:///live-build-x2go.git::feature/openbox-magic-pixel-workaround-buster' # this one loosely corresponds to "stable" # Select ONE of the following git reposities # bad idea with apt-cacher-ng, but will work with e.g. # we have a successful connect on port 3142, assume # simple check for apt-cacher-ng being active - if # NOTE: This file gets sourced by the actual buildscript - so place it in the same directory as the buildscript or adjust the path in the buildscript. ThinClient prerequisites for all TCE-Live variantsĬhange to a directory where you want to save your builds, and save the following file as x2go-tce-config: Our TCE-Live works just fine with Jessie, Stretch, and Buster as well. 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.
Iso2god unable to locate default.xex portable#
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.
Iso2god unable to locate default.xex update#
It is also possible to deploy the image to the ThinClient's local storage, if present, and have it update in the background.īesides, 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.
If you follow our advice of loading the entire image into the ThinClient's RAM, or using local storage, all you need is an HTTP (HTTPS optional for later stages) or FTP server with a dedicated IP, if you want to use netbooting. However, the huge advantage is that there no longer is a need for any high-availibility setup concerning NFS (nor HTTP/HTTPS/ FTP). Working with 256 MB is possible when you use local storage instead of netbooting (don't use the toram parameter, either), but not really recommended. The disadvantage is that your ThinClient now needs at least 512 MB to 1 GB of RAM (see below).
To avoid confusion, and because it has since left the “NG” state, we now call it TCE-Live. Instead, the entire image is loaded into the RAM of the ThinClient machine. During the time of Debian Wheezy being Debian's stable release, we started developing a new ThinClientEdition then called TCE-Next Generation, or TCE-NG for short - one that is based on Debian-Live and thus does no longer rely on NFS (though NFS can still be used to deploy the image - but we do not recommend that approach).
0 kommentar(er)
