Differences

This shows you the differences between two versions of the page.

--- wiki:advanced:tce:install [2013/11/12 15:17]
sunweaver
+++ wiki:advanced:tce:install [2023/12/19 23:57] (current)
gratuxri
@@ Line 1: / Line 1: @@
-====== Installation of the X2Go TCE based on Debian ======
+====== Installation of the classic, NFS-filesystem-based X2Go TCE ======
 In the following article we will explain how to set up an X2Go Thin Client environment. In the following we will use three technical terms that we want to define/explain before we start:
@@ Line 8: / Line 8: @@
 <note>The X2Go TCE has been developed on/for Debian GNU/Linux. -- You can surely use any GNU/Linux distribution as X2Go Server (providing that the ''x2goserver'' package is available for the server's distro). The boot environment for the X2Go PXE Server has been developed on Debian GNU/Linux and also been tested on Ubuntu GNU/Linux. The X2Go Thin Client chroot can be configured to use Ubuntu GNU/Linux, but it is __highly recommended__ to leave the defaults and use Debian GNU/Linux for creating the X2Go TCE chroot.</note>
+<note>The Debian instructions should also hold for Raspbian, a Debian fork rebuilt on armhf.</note>
 ===== Network setup =====
@@ Line 24: / Line 26: @@
   * X2Go Thin Client hardware (can be everything from e.g. Pentium III, AMD Athlon upwards), main requirement is that the thin client hardware box contains a network card that is PXE/Etherboot capable
-===== X2Go TCE / Debian squeeze/wheezy/jessie =====
+===== X2Go TCE / Debian jessie/bullseye =====
-<note>The current X2Go TCE can be based on and has been tested against Debian GNU/Linux (squeeze, wheezy and jessie). Since June 2011 we have working packages available in our Debian repository on ''packages.x2go.org''. The latest test against Debian jessie have been performed around Nov 2013.</note>
+<note>The current X2Go TCE can be based on and has been tested against Debian GNU/Linux (jessie and bullseye). Since June 2011 we have working packages available in our Debian repository on ''packages.x2go.org''. The latest test against Debian jessie have been performed around Nov 2013.</note>
 In the following description we will describe a simple X2Go TCE installation, using two separate hosts as X2Go Server and X2Go PXE Server. The explanation presumes that you either install on Debian GNU/Linux or Ubuntu GNU/Linux. If you (for testing purposes) use the same machine as X2Go Server and X2Go PXE Server, please perform described steps for either of the machines on the same system.
-The resulting X2Go Thin Client chroot will be a Debian GNU/Linux (wheezy) system by default.
+The resulting X2Go Thin Client chroot will be a Debian GNU/Linux (bullseye) system by default.
 :!: **Before you continue!**
@@ Line 88: / Line 90: @@
 With this last step your X2Go Thin Client's chroot environment is basically ready for being booted. The last step, however, is to configure the PXE boot manager itself (PXE, TFTP).
+=== Provide firmware for certain hardware devices ===
+Debian does not ship so-called non-free firmware in its main package archive area. However, several network cards (and other TCE relevant devices) require the installation of a firmware package from Debian non-free.
+Run the command ''x2gothinclient_shell'' and edit ''/etc/apt/sources.list'' in your TCE chroot (nano, vim and mcedit should be installed in your TCE chroot):
+<file>
+deb http://ftp.debian.org/debian <distro-codename> main contrib non-free
+</file>
+Then run (in your X2Go TCE chroot):<code>
+$ apt-get update
+$ apt-get install firmware-linux-nonfree firmware-bnx2 firmware-bnx2x firmware-myricom firmware-netxen  firmware-qlogic  firmware-ralink firmware-realtek intel-microcode amd64-microcode
+</code>
+If this command fails, please check if packages have been removed from your Debian version or if they are not yet available for your version. Also scan for other firmware packages:<code>
+$ apt-cache search firmware
+</code>
+Also, there is a fine tool that you can run on normal Linux systems that helps with the package installation for several special hardware devices: [[http://packages.debian.org/unstable/main/isenkram|Isenkram by Petter Reinholdtsen]] from the Debian Edu team.
 === Boot environment for your X2Go Thin Client system (PXE, TFTP) ===
@@ Line 104: / Line 127: @@
 You should now be able to start your office PCs as X2Go Thin Clients. To do this, configure the computer's BIOS to boot via network (PXE, Etherboot). You will know that you setup has been successful, if a boot menu appears on your computer's screen that shows the X2GO banner that also appears when starting X2Go sessions.
+It is also possible to test the X2Go TCE in qemu. Read the [[http://code.x2go.org/gitweb?p=x2gothinclient.git;a=blob;f=README.qemu|documentation shipped with the X2Go TCE sources]].
 === Purging X2Go TCE ===
@@ Line 162: / Line 187: @@
 ==== Configuration of x2goclient (display manager mode) ====
-=== x2goclient in LDAP-mode ===
+=== X2Go Client in LDAP-mode ===
 Please feel free to customize the command line options used by the ''x2goclient''  running in display manager mode. For example you can enable LDAP mode:
@@ Line 175: / Line 200: @@
 x2goclient --pgp-card \
            --ldap="192.168.1.1:389:dc=<domain>,dc=<tld>" \
-           --external-login=/ramdrive/logins \
+           --external-login=~x2gothinclient/logins \
            --no-menu \
            --maximize \
@@ Line 181: / Line 206: @@
            --haltbt \
            --link=lan \
-           --kbd-layout=de \
+           --kbd-layout=us \
-           --kbd-type=pc105/de \
+           --kbd-type=pc105/us \
            --set-kbd=1 \
            --geometry=fullscreen \
-           --add-to-known-hosts \
+           --read-exports-from=~x2gothinclient/export \
-           --read-exports-from=/ramdrive/export \
            --add-to-known-hosts &
 </file>
@@ Line 196: / Line 220: @@
 </code>
-=== x2goclient in non-LDAP mode ===
+=== X2Go Client in broker mode ===
+Please feel free to customize the command line options used by the ''x2goclient''  running in display manager mode. For example you can enable LDAP mode:
+<code>
+$ editor /opt/x2gothinclient/etc/x2gothinclient_start
+</code>
+The below example uses LDAP-mode for ''x2goclient'':
+<file>
+x2goclient --pgp-card \
+           --broker-url=https://<broker-server>:<port>/plain/<backend> \
+           --broker-cacertfile=<path-to-your-self-signed-rootca-file>
+           --external-login=~x2gothinclient/logins \
+           --no-menu \
+           --maximize \
+           --thinclient \
+           --haltbt \
+           --link=lan \
+           --kbd-layout=us \
+           --kbd-type=pc105/us \
+           --set-kbd=1 \
+           --geometry=fullscreen \
+           --read-exports-from=~x2gothinclient/export \
+           --add-to-known-hosts &
+</file>
+After modifying the ''x2gothinclient_start'' file, update the X2Go Thin Client configuration:
+<code>
+$ x2gothinclient_update
+</code>
+=== X2Go Client in sessions file mode ===
 The Debian GNU/Linux X2Go TCE uses non-LDAP mode as default. Edit the default sessions file in ''/opt/x2gothinclient/etc/x2gothinclient_sessions''.
@@ Line 209: / Line 268: @@
            --session="X2Go.EXAMPLE" \
            --pgp-card \
-           --external-login=/ramdrive/logins \
+           --external-login=~x2gothinclient/logins \
            --no-menu \
            --maximize \
@@ Line 215: / Line 274: @@
            --haltbt \
            --link=lan \
-           --kbd-layout=de \
+           --kbd-layout=us \
-           --kbd-type=pc105/de \
+           --kbd-type=pc105/us \
            --set-kbd=1 \
            --geometry=fullscreen \
-           --add-to-known-hosts \
+           --read-exports-from=~x2gothinclient/export \
-           --read-exports-from=/ramdrive/export \
            --add-to-known-hosts &
 </file>

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools