A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:36
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start?rev=1363300546
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start
Edit Summary: [X2Go & CipUX]
User : sunweaver
@@ -13,9 +13,9 @@
===== X2Go Printing Revisited =====
* [[wiki:advanced:multi-node:x2goserver-printing|Multi-Node Printing with X2Go]]
- ===== X2Go & CipUX =====
+ ===== X2Go Admin Center =====
* [[wiki:advanced:administration:cipux|Use X2Go Admin Center with CipUX]]
===== X2Go Thin Client Environment (TCE) =====
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:35
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start?rev=1363300513
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start
Edit Summary: [X2Go Printing Revisited]
User : sunweaver
@@ -12,10 +12,9 @@
===== X2Go Printing Revisited =====
- * [[wiki:advanced:multi-node:x2goserver-printing|Multi-Node Printing with X2Go|]]
-
+ * [[wiki:advanced:multi-node:x2goserver-printing|Multi-Node Printing with X2Go]]
===== X2Go & CipUX =====
* [[wiki:advanced:administration:cipux|Use X2Go Admin Center with CipUX]]
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:35
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: ---
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2goplugin
Edit Summary: created
User : sunweaver
====== X2Go Browser Plugin ======
FIXME FIXME FIXME FIXME
THE BELOW INFORMATION IS NOT UP-TO-DATE, IT HAS TO BE REWRITTEN!!!!
FIXME FIXME FIXME FIXME
[[wiki:components:x2goplugin-example|plugin example page]]
x2goplugin is a Firefox plugin.
//On supported systems//, this plugin acts as a web portal which can be used to access an x2go session via Firefox web browser instead of using one of the x2goclients. Note: the current plugin does not yet support Firefox 4.x.
===== Installation of x2goplugin =====
Please visit the webssite http://plugin.x2go.org. This website will offer
you a x2goplugin suitable for your operating system and system architecture.
Currently the x2goplugin is available for the following systems:
* Linux 32 bit
* Linux 64 bit
* Windows 32 bit
===== Inserting x2goplugin into a webpage =====
This is a short tutorial how to integrate the x2go plugin into a website.
==== building a minimal website ====
You'll need a Website to carry the plugin. Please feel free to use your own Website code. This is just a example which should be used to get started:
<code>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>x2go Plugin</title>
</head>
<body>
<div id="x2goplugin" style="width: auto; hight: auto;">
<--x2goplugin //-->
</div>
</body>
</html>
</code>
You can use either use a <div></div> container with the help of css to set the size of the plugin or with the help of the <option></option> tag. As the plugin and a connected x2go session can be resized inside a website,
we recommend using a <div></div> container for this purpose and to set the <option></option> with and height value to 100%.
==== inserting the <object></object> code ====
Please paste the following code inside your website between the <div></div> command:
<code>
<object src="location"
type="application/x2go"
pluginspage="http://plugin.x2go.org/index.html"
pluginurl="http://plugin.x2go.org/download/x2goplugin_linux32.xpi"
name="x2goplugin"
palette="background"
height="100%"
hspace="0"
vspace="0"
width="100%"
x2goconfig="
session=mysessionname
server=myserver.org
user=myusername
sshport=22
command=KDE
rootless=false
sound=true
exportfs=true
speed=adsl
compression=16m-jpeg
quality=9
dpi=120
kbdlayout=de
kbdtype=pc105/de
showtoolbar=true
showstatusbar=true
">
<--x2goplugin //-->
</object>
</code>
You can change the the value "session" to whatever you like - it is just the name of the session.
The value "server" should be the hostname
or the IP-address of the x2goserver which should be contacted by the plugin as your target "desktop server".
The value "user" can be left blank, otherwise this "username" will be used as login for the x2go session and the user will not be able to change that login ID.
The value "sshport" should be set to 22 - you should only change this if you've previously changed the SSH port number in the /etc/ssh/sshd_config file on the x2goserver.
You can choose the used Desktop Environment or application by changing the value "command".
* If you specify "KDE" or "GNOME" then x2go will present you __with__ an entire remote desktop.
* If you specify any application (such as: firefox) which is executable by the user then only that application will appear __without__ the entire remote desktop.
The value "rootless" should be set to false for use with a whole Desktop Environments and Window Manager.
If you plan to use single applications you can use this feature to use the local
running window manager.
If you intend to utilize the automatic update service (recommended), do not change the urls used in the values "pluginspage" and "pluginurl".
The value "name" is mandatory and should not be changed. If you don't want to use the <div></div> container, you should take care of reasonable height and width settings.
==== checking if the plugin is already installed (and offering it if not) ====
If you are visiting the created website, you'll only get a x2goplugin shown if it was previously installed by the user. If not, only a white space will appear. To check whether the plugin is installed or not, we'll need to add a javascript to the website. This too will offer the user the plugin if it wasn't installed before or inform him about the availability.
Inside the website's <head> </head> section you'll need to add the needed javascript.
You should use the plugin directly from our server to make sure that you'll get the latest version. The download url of
the x2goplugin can change, because we want to store it on the Mozilla Add On site in future. Of cause you can also download the script here (http://plugin.x2go.org/media/x2goplugin.js) but please make sure that you'll update it in case it was changed on our server:
<code>
<head>
<title>x2go Plugin</title>
<script src="http://plugin.x2go.org/media/x2goplugin.js" type="text/javascript"></script>
</head>
</code>
The javascript will need to be started, so you should add the the command "onLoad" to the <body></body> tag of the website:
<code>
<body onload="checkPlugin()">
</code>
==== a complete website example ====
Your whole Website should now look something like this (This site makes use of an already existing css file on our server. You can also use the <div id="x2goplugin" style="width: auto; hight: auto;"> settings as described before):
<code>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>x2go Plugin</title>
<link
rel="stylesheet" type="text/css" href="http://plugin.x2go.org/media/x2goplugin.css">
<script src="http://plugin.x2go.org/media/x2goplugin.js" type="text/javascript"></script>
</head>
<body onload="checkPlugin()">
<div id="x2goplugin">
<object src="location"
type="application/x2go"
pluginspage="http://plugin.x2go.org/index.html"
pluginurl="http://plugin.x2go.org/download/x2goplugin_linux32.xpi"
data="x2go.server"
hidden="false"
name="x2goplugin"
palette="background"
height="100%"
hspace="0"
vspace="0"
width="100%">
<!--x2goplugin //-->
</object>
</div>
<div id="description">
<h4>x2goplugin</h4>
<p>This website will offer you a plugin named "x2goplugin". With the installed
plugin you'll be able to start or recover a session running on a x2goserver.
The server needs to be preconfigured.
To get more information about what x2go is, please visit <a href="http://www.x2go.org">http://www.x2go.org</a>.
</p>
</div>
</body>
</html>
</code>
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:35
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start?rev=1363300474
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start
Edit Summary: [X2Go Browser Plugin]
User : sunweaver
@@ -3,9 +3,9 @@
===== X2Go Browser Plugin =====
X2Go Client is also available as a browser plugin. With this plugin your web browser can be turned into an X2Go Client very easily. The session configuration can be embedded into the HTML file initiating the plugin startup.
- Read more on how to [[wiki:components:x2goplugin|set up an X2Go web portal with X2Go Plugin]]...
+ Read more on how to [[wiki:advanced:x2goplugin|set up an X2Go web portal with X2Go Plugin]]...
===== X2Go + PostgreSQL =====
* [[wiki:advanced:multi-node:x2goserver-pgsql|X2Go Server with Postgres DB Backend]]
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:35
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:components:x2goplugin?rev=1362749499
New Revision: http://wiki.x2go.org/doku.php/wiki:components:x2goplugin
Edit Summary: removed
User : sunweaver
@@ -1,169 +1 @@
- ====== X2Go Browser Plugin ======
- FIXME FIXME FIXME FIXME
-
- THE BELOW INFORMATION IS NOT UP-TO-DATE, IT HAS TO BE REWRITTEN!!!!
-
- FIXME FIXME FIXME FIXME
-
- [[wiki:components:x2goplugin-example|plugin example page]]
-
- x2goplugin is a Firefox plugin.
-
- //On supported systems//, this plugin acts as a web portal which can be used to access an x2go session via Firefox web browser instead of using one of the x2goclients. Note: the current plugin does not yet support Firefox 4.x.
-
- ===== Installation of x2goplugin =====
-
- Please visit the webssite http://plugin.x2go.org. This website will offer you a x2goplugin suitable for your operating system and system architecture.
-
- Currently the x2goplugin is available for the following systems:
- * Linux 32 bit
- * Linux 64 bit
- * Windows 32 bit
-
-
- ===== Inserting x2goplugin into a webpage =====
-
- This is a short tutorial how to integrate the x2go plugin into a website.
-
-
- ==== building a minimal website ====
-
- You'll need a Website to carry the plugin. Please feel free to use your own Website code. This is just a example which should be used to get started:
-
- <code>
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
- <html>
- <head>
- <title>x2go Plugin</title>
- </head>
- <body>
- <div id="x2goplugin" style="width: auto; hight: auto;">
- <--x2goplugin //-->
- </div>
- </body>
- </html>
- </code>
-
- You can use either use a <div></div>
container with the help of css to set the size of the plugin or with the help of the <option></option> tag. As the plugin and a connected x2go session can be resized inside a website, we recommend using a <div></div> container for this purpose and to set the <option></option> with and height value to 100%.
-
- ==== inserting the <object></object> code ====
-
- Please paste the following code inside your website between the <div></div> command:
-
- <code>
- <object src="location"
- type="application/x2go"
- pluginspage="http://plugin.x2go.org/index.html"
- pluginurl="http://plugin.x2go.org/download/x2goplugin_linux32.xpi"
- name="x2goplugin"
- palette="background"
- height="100%"
- hspace="0"
- vspace="0"
- width="100%"
- x2goconfig="
- session=mysessionname
- server=myserver.org
- user=myusername
- sshport=22
- command=KDE
- rootless=false
- sound=true
- exportfs=true
- speed=adsl
- compression=16m-jpeg
- quality=9
- dpi=120
- kbdlayout=de
-
kbdtype=pc105/de
- showtoolbar=true
- showstatusbar=true
- ">
- <--x2goplugin //-->
- </object>
- </code>
-
-
- You can change the the value "session" to whatever you like - it is just the name of the session.
-
- The value "server" should be the hostname or the IP-address of the x2goserver which should be contacted by the plugin as your target "desktop server".
-
- The value "user" can be left blank, otherwise this "username" will be used as login for the x2go session and the user will not be able to change that login ID.
-
- The value "sshport" should be set to 22 - you should only change this if you've previously changed the SSH port number in the /etc/ssh/sshd_config file on the x2goserver.
-
- You can choose the used Desktop Environment or application by changing the value "command".
- * If you specify "KDE" or "GNOME" then x2go will present you __with__ an entire remote desktop.
- * If you specify any application (such as: firefox) which is
executable by the user then only that application will appear __without__ the entire remote desktop.
-
- The value "rootless" should be set to false for use with a whole Desktop Environments and Window Manager.
- If you plan to use single applications you can use this feature to use the local running window manager.
-
-
- If you intend to utilize the automatic update service (recommended), do not change the urls used in the values "pluginspage" and "pluginurl".
-
-
- The value "name" is mandatory and should not be changed. If you don't want to use the <div></div> container, you should take care of reasonable height and width settings.
-
- ==== checking if the plugin is already installed (and offering it if not) ====
-
- If you are visiting the created website, you'll only get a x2goplugin shown if it was previously installed by the user. If not, only a white space will appear. To check whether the plugin is installed or not, we'll need to add a javascript to the website.
This too will offer the user the plugin if it wasn't installed before or inform him about the availability.
-
- Inside the website's <head> </head> section you'll need to add the needed javascript.
-
- You should use the plugin directly from our server to make sure that you'll get the latest version. The download url of the x2goplugin can change, because we want to store it on the Mozilla Add On site in future. Of cause you can also download the script here (http://plugin.x2go.org/media/x2goplugin.js) but please make sure that you'll update it in case it was changed on our server:
-
- <code>
- <head>
- <title>x2go Plugin</title>
- <script src="http://plugin.x2go.org/media/x2goplugin.js" type="text/javascript"></script>
- </head>
- </code>
-
- The javascript will need to be started, so you should add the the command "onLoad" to the <body></body> tag of the website:
-
- <code>
- <body onload="checkPlugin()">
- </code>
-
- ==== a complete website example ====
-
-
Your whole Website should now look something like this (This site makes use of an already existing css file on our server. You can also use the <div id="x2goplugin" style="width: auto; hight: auto;"> settings as described before):
-
- <code>
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
- <html>
- <head>
- <title>x2go Plugin</title>
- <link rel="stylesheet" type="text/css" href="http://plugin.x2go.org/media/x2goplugin.css">
- <script src="http://plugin.x2go.org/media/x2goplugin.js" type="text/javascript"></script>
- </head>
- <body onload="checkPlugin()">
- <div id="x2goplugin">
- <object src="location"
- type="application/x2go"
- pluginspage="http://plugin.x2go.org/index.html"
- pluginurl="http://plugin.x2go.org/download/x2goplugin_linux32.xpi"
- data="x2go.server"
- hidden="false"
- name="x2goplugin"
- palette="background"
- height="100%"
- hspace="0"
- vspace="0"
- width="100%">
- <!--x2goplugin //-->
-
</object>
- </div>
- <div id="description">
- <h4>x2goplugin</h4>
- <p>This website will offer you a plugin named "x2goplugin". With the installed
- plugin you'll be able to start or recover a session running on a x2goserver.
- The server needs to be preconfigured.
- To get more information about what x2go is, please visit <a href="http://www.x2go.org">http://www.x2go.org</a>.
- </p>
- </div>
- </body>
- </html>
- </code>
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:34
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start?rev=1363300224
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start
Edit Summary: [LDAP-based load balancing]
User : sunweaver
@@ -9,11 +9,8 @@
===== X2Go + PostgreSQL =====
* [[wiki:advanced:multi-node:x2goserver-pgsql|X2Go Server with Postgres DB Backend]]
- ===== LDAP-based load balancing =====
-
- * [[wiki:advanced:multi-node:x2goserver-load-balancing|LDAP-based Load Balancing]]
===== X2Go Printing Revisited =====
* [[wiki:advanced:multi-node:x2goserver-printing|Multi-Node Printing with X2Go|]]
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:32
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/sidebar?rev=1363295089
New Revision: http://wiki.x2go.org/doku.php/sidebar
Edit Summary:
User : sunweaver
@@ -40,10 +40,10 @@
<wrap todo>
[[:wiki:start|Wiki]]
</wrap>
+ * [[wiki:development:roadmap|X2Go Development Roadmap]]
{{indexmenu>:wiki:#1|context}}
-
<wrap info>
[[:about:start|About]]
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:30
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: ---
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:tce:install
Edit Summary: created
User : sunweaver
====== Installation of the X2Go TCE based on Debian ======
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:
* X2Go Server: a GNU/Linux application server that users can connect to with the ''x2goclient'' software. X2Go servers can be situated in the LAN (local area network) or WAN (wide area network, i.e. the internet).
* X2Go Thin Client: a user workstation in your office that boots from the network with minimal software. Only purpose is to
start the ''x2goclient'' software and provide access to one (or more) X2Go Server(s).
* X2Go PXE Server: the server that serves chroot images to X2Go Thin Clients via PXE, TFTP and NFS to thin client boxes. The X2Go PXE Server has to be situated in your LAN. X2Go PXE Server and X2Go Server can be one machine, in production setups we recommend to separate these two functionalities onto two separate (virtual) servers.
<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>
===== Network setup =====
X2Go TCE requires a
local area network (LAN) that is at least switched at 100MB/s. The X2Go Thin Client chroot distribution is not designed to work over the internet or on low bandwidth connections, but the X2Go Thin Client can possibly give access to X2Go servers outside of your LAN infrastructure that is: X2Go Thin Clients can be used to work on X2Go servers on the WAN (e.g. on the internet, in a public cloud, etc.).
You can combine X2Go Server and X2Go PXE Server functionality on one system. However, for production setups we highly recommend that you dedicate a separate server as the PXE boot server for the X2Go TCE. If you have the chance of splitting these two functionalities up into two, this is a recommended way of setting up your X2Go Thin Client Environment.
<note important>Please refrain from installing the PXE boot environment for X2Go Thin Clients on your in-house production server, especially for testing X2Go TCE make it a separate system. Maybe you want to use virtualization (KVM, Xen,
etc.) for setting up a test X2Go infrastructure with X2Go Thin Clients on your LAN.
</note>
A normal/recommended setup for testing/deploying X2Go TCE then is:
* X2Go server (Debian, Ubuntu, etc.)
* optional: a separate X2Go PXE server (Debian or Ubuntu)
* 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 =====
<note>The current X2Go TCE is based and has been tested on Debian GNU/Linux (squeeze). Since June 2011 we have working packages available in our Debian repository on ''packages.X2Go.org''.</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 (squeeze) or Ubuntu GNU/Linux (lucid, maverick). 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 (squeeze) system by default.
:!: **Before you continue!**
> Please make sure that you have added the X2Go repository to your package management system (on X2Go server and on X2Go PXE server). The required steps are described [[wiki:x2go-repository-debian|here (Debian)]] and [[:wiki:x2go-repository-ubuntu|here (Ubuntu)]].
==== Installing X2Go server ====
The X2Go Server installation is described in detail on [[:wiki:components:x2goserver|this wiki page]]. Please follow instructions there first, then proceed below.
==== Installing X2Go PXE server ====
=== Summary ===
In a nutshell, you have to run the following commands from a terminal on the X2Go PXE Server (or X2Go Server if combining both systems in one):
<code>
$ sudo aptitude install x2gothinclientmanagement
# take a look at the X2Go TCE
config and modify to your needs
$ sudo editor /etc/x2go/x2gothinclient_settings
$ sudo x2gothinclient_create
# now you have to wait for some time, a lot of text will pass through your terminal window
$ sudo x2gothinclient_preptftpboot
# follow the instructions being shown at the end of the x2gothinclient_preptftpboot script run...
</code>
=== Basic installation of the X2go PXE server ===
Now a bit more in detail...
- Install a minimal Debian GNU/Linux (squeeze) or Ubuntu GNU/Linux Server (lucid, maverick) system from CD/DVD.
- Then add the X2go repository to your freshly installed X2go PXE server: [[:wiki:x2go-repository-debian|Debian]] / [[:wiki:x2go-repository-ubuntu|Ubuntu]]. On Debian GNU/Linux make sure that you install the ''x2go-keyring'' package first.
- The only X2go related package needed on the X2go PXE server is the ''x2gothinclientmanagement'' package.<code>
$ sudo aptitude install x2gothinclientmanagement
</code>The installation will drag in some other
required packages onto your system, please confirm with Yes, to start the installation.
=== Building the X2go Thin Client system (the so-called chroot environment) ===
- After installation of the ''x2gothinclientmanagement'' package (and required dependencies), please edit/introspect the following file with your favourite editor:<code>
$ sudo editor /etc/x2go/x2gothinclient_settings
</code> and apply changes required for your local site setup to the X2go TCE configuration.
- When done, start the creation of a fresh X2go Thin Client chroot environment:<code>
$ sudo x2gothinclient_create
</code>
- Now you will be able to observe a medium long installation process on your system. This installation process takes place in a chroot jail environment, it does not do anything to the X2go PXE server itself.
- During installation you will be asked to configure your thin client's default language and default keyboard settings. Please do so. Hint: make sure you use UTF-8 encoding in
your language selection (e.g. en_US.UTF-8, de_DE.UTF-8, etc.).
- After the X2go TCE installation of your X2go Thin Client (default location: ''/opt/x2gothinclient/chroot'') you will find a complete and minimal X2go TCE GNU/Linux system at the aforenamed chroot location.
- Next, you may take a look at the config files in the folder ''/opt/x2gothinclient/etc/'':
- ''**x2gothinclient_init**'': No customizations should be necessary for this file. Modify at your own risk... If a modification is necessary here, please report it as a bug/enhancement to the X2go developers.
- ''**x2gothinclient_start**'': This file is responsible for actually launching ''x2goclient'' as a login manager on your thin client. The default setting is to start in non-LDAP mode. In non-LDAP mode the ''x2gothinclient_sessions'' file contains the thin clients' list of available X2go session profiles. For LDAP mode there is a commented out stanza that shows possible LDAP options to pass on to the
''x2goclient'' application. //**Note:** If you edit this file, please make sure that all applications you call from this file are sent to background with the ampersand (»&«) operator, e.g.: '' x2goclient <options> &''//
- ''**x2gothinclient_sessions**'': This file contains a list of session profile configurations for your thin clients' ''x2goclient'' (running in non-LDAP logon manager mode). Surely, you can edit/customize the examplary session profiles file that comes with the ''x2gothinclientmanagement'' package in your favourite text editor. --- However, you can also use the ''x2goclient'' application on your local (GNU/Linux) computer to create a set of session profiles for your X2go Thin Client. Start ''x2goclient'' locally, create a set of session profiles and then copy your local ''x2goclient'' session profile configuration to the X2go PXE server:<code>
$ scp ~/.x2goclient/sessions root@<pxeserver.hostname.domain>:/opt/x2gothinclient/etc/x2gothinclient_sessions
</code>
- When done with all your customizations execute the ''x2gothinclient_update'' script. This script will incorporate your changes applied the ''/opt/x2gothinclient/etc/x2gothinclient_*'' files into the X2go Thin Clients' chroot environment. Whenever you customize anything in ''/opt/x2gothinclient/etc/'' make sure your run the update command:<code>
$ sudo x2gothinclient_update
</code>
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).
=== Boot environment for your X2go Thin Client system (PXE, TFTP) ===
With the ''x2gothinclient_preptftpboot'' script you can simply set up a PXE boot environment using the ''syslinux'' package. Please take a look at the ''/etc/x2go/x2gothinclient_settings'' configuration file for customization first, then run this script:
<code>
$ x2gothinclient_preptftpboot
</code>
If there already is a PXE boot environment installed at
the configured location, the script will abort with a warning. If you want to combine X2go PXE with other boot environments (e.g. LTSP), please customize your system manually. Templates for X2go PXE can be found at ''/usr/share/x2go/tce/tftpboot''.
Note: At the end of the ''x2gothinclient_preptftpboot'' script some further instructions (DHCP setup, NFS setup, etc.) of final configuration steps will be shown. Please follow these last steps to complete your X2go TCE setup.
=== Testing X2go TCE ===
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.
=== Purging X2go TCE ===
To get rid of all files related to X2go TCE, please run this script:
<code>
$ x2gothinclient_cleanup
</code>
===== Tweaking your X2go TCE
=====
==== Configuration of DHCPD ====
If you already have an DHCP server in your network, please make sure that you are able to setup an own range of IP addresses for the boot environment. Because of the conflict between devices that should access the boot environment and normal network nodes (MAC address binding), it is much easier to setup a separate network sub-LAN (in the example below: 192.168.0.0/24) for your thin client systems:
<code>
$ sudo editor /etc/dhcp3/dhcpd.conf
</code>
<file>
option domain-name "<your-localdomain.org>";
option domain-name-servers <ip-of-dns-server>;
# x2go thin client range/group
subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.100 192.168.0.199;
filename "/pxelinux.0";
next-server 192.168.0.250;
}
</file>
Restart the DHCPD server to apply the new configuration:
<code>
# /etc/init.d/dhcp3-server restart
</code>
==== Configuration of the NFS share ====
The root file system of the boot environment is mounted using NFSv3 (so
it can be accessed over the network). You'll need to export the needed directory by editing the NFS configuration file:
<code>
$ sudo editor /etc/exports
</code>
<file>
/opt/x2gothinclient/chroot 192.168.0.0/24(ro,async,no_root_squash)
</file>
Finally restart the NFS daemon:
<code>
$ sudo /etc/init.d/nfs-kernel-server restart
</code>
==== Configuration of x2goclient (display manager mode) ====
=== x2goclient 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:
<code>
$ editor /opt/x2gothinclient/etc/x2gothinclient_start
</code>
The below example uses LDAP-mode for ''x2goclient'':
<file>
x2goclient --pgp-card \
--ldap="192.168.1.1:389:dc=<domain>,dc=<tld>" \
--external-login=/ramdrive/logins \
--no-menu \
--maximize \
--thinclient \
--haltbt \
--link=lan \
--kbd-layout=de
\
--kbd-type=pc105/de \
--set-kbd=1 \
--geometry=fullscreen \
--add-to-known-hosts \
--read-exports-from=/ramdrive/export \
--add-to-known-hosts &
</file>
After modifying the ''x2gothinclient_start'' file, update the X2go Thin Client configuration:
<code>
$ x2gothinclient_update
</code>
=== x2goclient in non-LDAP mode ===
The Debian GNU/Linux (squeeze) X2go TCE uses non-LDAP mode as default. Edit the default sessions file in ''/opt/x2gothinclient/etc/x2gothinclient_sessions''.
There are two extra commandline arguments that you should be aware in the below configuration.
* ''--no-session-edit'' will deny any manipulation of the session by the user.
* ''--session="X2Go.EXAMPLE'' needs to be identical to the name inside the X2go session file.
<file>
x2goclient --no-session-edit \
--session="X2Go.EXAMPLE" \
--pgp-card \
--external-login=/ramdrive/logins \
--no-menu \
--maximize \
--thinclient \
--haltbt \
--link=lan \
--kbd-layout=de \
--kbd-type=pc105/de \
--set-kbd=1 \
--geometry=fullscreen \
--add-to-known-hosts \
--read-exports-from=/ramdrive/export \
--add-to-known-hosts &
</file>
After modifying the ''x2gothinclient_start'' file, update the X2go Thin Client configuration:
<code>
$ x2gothinclient_update
</code>
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:30
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start?rev=1363123001
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:start
Edit Summary: [TCE Hardware]
User : sunweaver
@@ -21,14 +21,15 @@
===== X2Go & CipUX =====
* [[wiki:advanced:administration:cipux|Use X2Go Admin Center with CipUX]]
- ===== TCE Hardware =====
+ ===== X2Go Thin Client Environment (TCE) =====
+ * [[wiki:advanced:tce:install|Installation of the X2Go TCE]]
* [[wiki:advanced:tce:tested-hardware|Experiences with Thin Client Hardware]]
===== Passwordless Authentication =====
* [[wiki:advanced:authentication:passwordless-ssh|Passwordless Authentication with SSH pub/priv key pairs]]
*
[[wiki:advanced:authentication:passwordless-gpg-card|Passwordless Authentication with GnuPG-Cards]]
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/14 22:29
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.39.109
Hostname : 109-39-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:components:tce?rev=1362749499
New Revision: http://wiki.x2go.org/doku.php/wiki:components:tce
Edit Summary: removed
User : sunweaver
@@ -1,233 +1 @@
- ====== Installation of the X2Go TCE based on Debian ======
-
- 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:
-
- * X2Go Server: a GNU/Linux application server that users can connect to with the ''x2goclient'' software. X2Go servers can be situated in the LAN (local area network) or WAN (wide area network, i.e. the internet).
- * X2Go Thin Client: a user workstation in
your office that boots from the network with minimal software. Only purpose is to start the ''x2goclient'' software and provide access to one (or more) X2Go Server(s).
- * X2Go PXE Server: the server that serves chroot images to X2Go Thin Clients via PXE, TFTP and NFS to thin client boxes. The X2Go PXE Server has to be situated in your LAN. X2Go PXE Server and X2Go Server can be one machine, in production setups we recommend to separate these two functionalities onto two separate (virtual) servers.
-
- <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>
-
- ===== Network setup =====
-
- X2Go TCE requires a local area network (LAN) that is at least switched at 100MB/s. The X2Go Thin Client chroot distribution is not designed to work over the internet or on low bandwidth connections, but the X2Go Thin Client can possibly give access to X2Go servers outside of your LAN infrastructure that is: X2Go Thin Clients can be used to work on X2Go servers on the WAN (e.g. on the internet, in a public cloud, etc.).
-
- You can combine X2Go Server and X2Go PXE Server functionality on one system. However, for production setups we highly recommend that you dedicate a separate server as the PXE boot server for the X2Go TCE. If you have the chance of splitting these two functionalities up into two, this is a recommended way of setting up your X2Go Thin Client Environment.
-
- <note important>Please refrain from installing the PXE boot environment for X2Go Thin Clients on your in-house production server,
especially for testing X2Go TCE make it a separate system. Maybe you want to use virtualization (KVM, Xen, etc.) for setting up a test X2Go infrastructure with X2Go Thin Clients on your LAN.
- </note>
-
- A normal/recommended setup for testing/deploying X2Go TCE then is:
-
- * X2Go server (Debian, Ubuntu, etc.)
- * optional: a separate X2Go PXE server (Debian or Ubuntu)
- * 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 =====
-
- <note>The current X2Go TCE is based and has been tested on Debian GNU/Linux (squeeze). Since June 2011 we have working packages available in our Debian repository on ''packages.X2Go.org''.</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 (squeeze) or Ubuntu GNU/Linux (lucid, maverick). 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 (squeeze) system by default.
-
- :!: **Before you continue!**
- > Please make sure that you have added the X2Go repository to your package management system (on X2Go server and on X2Go PXE server). The required steps are described [[wiki:x2go-repository-debian|here (Debian)]] and [[:wiki:x2go-repository-ubuntu|here (Ubuntu)]].
-
- ==== Installing X2Go server ====
-
- The X2Go Server installation is described in detail on [[:wiki:components:x2goserver|this wiki page]]. Please follow instructions there first, then proceed below.
-
-
- ==== Installing X2Go PXE server ====
-
- === Summary ===
-
- In a nutshell, you have to run the following commands from a
terminal on the X2Go PXE Server (or X2Go Server if combining both systems in one):
-
- <code>
- $ sudo aptitude install x2gothinclientmanagement
- # take a look at the X2Go TCE config and modify to your needs
- $ sudo editor /etc/x2go/x2gothinclient_settings
- $ sudo x2gothinclient_create
- # now you have to wait for some time, a lot of text will pass through your terminal window
- $ sudo x2gothinclient_preptftpboot
- # follow the instructions being shown at the end of the x2gothinclient_preptftpboot script run...
- </code>
-
- === Basic installation of the X2go PXE server ===
-
- Now a bit more in detail...
-
- - Install a minimal Debian GNU/Linux (squeeze) or Ubuntu GNU/Linux Server (lucid, maverick) system from CD/DVD.
- - Then add the X2go repository to your freshly installed X2go PXE server: [[:wiki:x2go-repository-debian|Debian]] / [[:wiki:x2go-repository-ubuntu|Ubuntu]]. On Debian GNU/Linux make sure that you install the ''x2go-keyring'' package first.
- - The
only X2go related package needed on the X2go PXE server is the ''x2gothinclientmanagement'' package.<code>
- $ sudo aptitude install x2gothinclientmanagement
- </code>The installation will drag in some other required packages onto your system, please confirm with Yes, to start the installation.
-
- === Building the X2go Thin Client system (the so-called chroot environment) ===
-
- - After installation of the ''x2gothinclientmanagement'' package (and required dependencies), please edit/introspect the following file with your favourite editor:<code>
- $ sudo editor /etc/x2go/x2gothinclient_settings
- </code> and apply changes required for your local site setup to the X2go TCE configuration.
- - When done, start the creation of a fresh X2go Thin Client chroot environment:<code>
- $ sudo x2gothinclient_create
- </code>
- - Now you will be able to observe a medium long installation process on your system. This installation process takes place in a chroot jail environment, it does
not do anything to the X2go PXE server itself.
- - During installation you will be asked to configure your thin client's default language and default keyboard settings. Please do so. Hint: make sure you use UTF-8 encoding in your language selection (e.g. en_US.UTF-8, de_DE.UTF-8, etc.).
- - After the X2go TCE installation of your X2go Thin Client (default location: ''/opt/x2gothinclient/chroot'') you will find a complete and minimal X2go TCE GNU/Linux system at the aforenamed chroot location.
- - Next, you may take a look at the config files in the folder ''/opt/x2gothinclient/etc/'':
- - ''**x2gothinclient_init**'': No customizations should be necessary for this file. Modify at your own risk... If a modification is necessary here, please report it as a bug/enhancement to the X2go developers.
- - ''**x2gothinclient_start**'': This file is responsible for actually launching ''x2goclient'' as a login manager on your thin client. The default setting is to start in non-LDAP
mode. In non-LDAP mode the ''x2gothinclient_sessions'' file contains the thin clients' list of available X2go session profiles. For LDAP mode there is a commented out stanza that shows possible LDAP options to pass on to the ''x2goclient'' application. //**Note:** If you edit this file, please make sure that all applications you call from this file are sent to background with the ampersand (»&«) operator, e.g.: '' x2goclient <options> &''//
- - ''**x2gothinclient_sessions**'': This file contains a list of session profile configurations for your thin clients' ''x2goclient'' (running in non-LDAP logon manager mode). Surely, you can edit/customize the examplary session profiles file that comes with the ''x2gothinclientmanagement'' package in your favourite text editor. --- However, you can also use the ''x2goclient'' application on your local (GNU/Linux) computer to create a set of session profiles for your X2go Thin Client. Start ''x2goclient'' locally, create a set of session
profiles and then copy your local ''x2goclient'' session profile configuration to the X2go PXE server:<code>
- $ scp ~/.x2goclient/sessions root@<pxeserver.hostname.domain>:/opt/x2gothinclient/etc/x2gothinclient_sessions
- </code>
- - When done with all your customizations execute the ''x2gothinclient_update'' script. This script will incorporate your changes applied the ''/opt/x2gothinclient/etc/x2gothinclient_*'' files into the X2go Thin Clients' chroot environment. Whenever you customize anything in ''/opt/x2gothinclient/etc/'' make sure your run the update command:<code>
- $ sudo x2gothinclient_update
- </code>
-
- 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).
-
- === Boot environment for your X2go Thin Client system (PXE, TFTP) ===
-
- With the ''x2gothinclient_preptftpboot'' script you can simply set up a PXE boot environment using the
''syslinux'' package. Please take a look at the ''/etc/x2go/x2gothinclient_settings'' configuration file for customization first, then run this script:
-
- <code>
- $ x2gothinclient_preptftpboot
- </code>
-
- If there already is a PXE boot environment installed at the configured location, the script will abort with a warning. If you want to combine X2go PXE with other boot environments (e.g. LTSP), please customize your system manually. Templates for X2go PXE can be found at ''/usr/share/x2go/tce/tftpboot''.
-
- Note: At the end of the ''x2gothinclient_preptftpboot'' script some further instructions (DHCP setup, NFS setup, etc.) of final configuration steps will be shown. Please follow these last steps to complete your X2go TCE setup.
-
- === Testing X2go TCE ===
-
- 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.
-
- === Purging X2go TCE ===
-
- To get rid of all files related to X2go TCE, please run this script:
-
- <code>
- $ x2gothinclient_cleanup
- </code>
-
- ===== Tweaking your X2go TCE =====
-
- ==== Configuration of DHCPD ====
-
- If you already have an DHCP server in your network, please make sure that you are able to setup an own range of IP addresses for the boot environment. Because of the conflict between devices that should access the boot environment and normal network nodes (MAC address binding), it is much easier to setup a separate network sub-LAN (in the example below: 192.168.0.0/24) for your thin client systems:
-
- <code>
- $ sudo editor /etc/dhcp3/dhcpd.conf
- </code>
-
- <file>
- option domain-name "<your-localdomain.org>";
- option domain-name-servers <ip-of-dns-server>;
-
- # x2go thin client range/group
- subnet 192.168.0.0 netmask 255.255.255.0 {
-
range 192.168.0.100 192.168.0.199;
- filename "/pxelinux.0";
- next-server 192.168.0.250;
- }
- </file>
-
- Restart the DHCPD server to apply the new configuration:
-
- <code>
- # /etc/init.d/dhcp3-server restart
- </code>
-
- ==== Configuration of the NFS share ====
-
- The root file system of the boot environment is mounted using NFSv3 (so it can be accessed over the network). You'll need to export the needed directory by editing the NFS configuration file:
-
- <code>
- $ sudo editor /etc/exports
- </code>
-
- <file>
- /opt/x2gothinclient/chroot 192.168.0.0/24(ro,async,no_root_squash)
- </file>
-
- Finally restart the NFS daemon:
-
- <code>
- $ sudo /etc/init.d/nfs-kernel-server restart
- </code>
-
-
- ==== Configuration of x2goclient (display manager mode) ====
-
- === x2goclient 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:
-
-
<code>
- $ editor /opt/x2gothinclient/etc/x2gothinclient_start
- </code>
-
- The below example uses LDAP-mode for ''x2goclient'':
-
- <file>
- x2goclient --pgp-card \
- --ldap="192.168.1.1:389:dc=<domain>,dc=<tld>" \
- --external-login=/ramdrive/logins \
- --no-menu \
- --maximize \
- --thinclient \
- --haltbt \
- --link=lan \
- --kbd-layout=de \
- --kbd-type=pc105/de \
- --set-kbd=1 \
- --geometry=fullscreen \
- --add-to-known-hosts \
- --read-exports-from=/ramdrive/export \
- --add-to-known-hosts &
- </file>
-
- After modifying the ''x2gothinclient_start'' file, update the X2go Thin Client configuration:
-
- <code>
- $ x2gothinclient_update
- </code>
-
- === x2goclient in non-LDAP mode ===
-
- The Debian GNU/Linux (squeeze) X2go TCE uses non-LDAP mode as default. Edit the default sessions file in
''/opt/x2gothinclient/etc/x2gothinclient_sessions''.
-
- There are two extra commandline arguments that you should be aware in the below configuration.
-
- * ''--no-session-edit'' will deny any manipulation of the session by the user.
- * ''--session="X2Go.EXAMPLE'' needs to be identical to the name inside the X2go session file.
-
- <file>
- x2goclient --no-session-edit \
- --session="X2Go.EXAMPLE" \
- --pgp-card \
- --external-login=/ramdrive/logins \
- --no-menu \
- --maximize \
- --thinclient \
- --haltbt \
- --link=lan \
- --kbd-layout=de \
- --kbd-type=pc105/de \
- --set-kbd=1 \
- --geometry=fullscreen \
- --add-to-known-hosts \
- --read-exports-from=/ramdrive/export \
- --add-to-known-hosts &
- </file>
-
- After modifying the ''x2gothinclient_start'' file, update the X2go Thin Client configuration:
-
-
<code>
- $ x2gothinclient_update
- </code>
-
-
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/