A page in your DokuWiki was added or changed. Here are the details:
Date : 2016/12/16 19:53
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/events:start?rev=1481917961
New Revision: http://wiki.x2go.org/doku.php/events:start
Edit Summary: [2017]
User : stefanbaur
@@ -8,9 +8,9 @@
* X2Go: The Gathering 2017 - some time in May-June 2017, probably. Most likely at Linuxhotel. Around May 13th, maybe? (would allow for [[http://www.zollverein.de/angebote/vollmond-auf-zollverein|this]] tour)
* LITA 2017 - Date TBD
* TUEBIX 2017 - Date TBD
* Linux Expo Ulm 2017 - Date TBD (2017-05-06, maybe?)
- * Chemnitzer LinuxTage - 2017-03-11/2017-03-12
+ * Chemnitzer LinuxTage - 2017-03-11/2017-03-12 (Date confirmed, but no participation yet)
==== Another Radio Interview (in German),
Radio Free FM, Ulm (2017-02-12, 13:00h - 15:00h) ====
* this time more focused on X2Go
* with Stefan and h1 as guests
--
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 : 2016/12/16 19:52
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/events:start?rev=1481917949
New Revision: http://wiki.x2go.org/doku.php/events:start
Edit Summary: [//Another// Radio Interview (in German), Radio Free FM, Ulm (2017-02-12, 13:00h - 15:00h)]
User : stefanbaur
@@ -10,9 +10,9 @@
* TUEBIX 2017 - Date TBD
* Linux Expo Ulm 2017 - Date TBD (2017-05-06, maybe?)
* Chemnitzer LinuxTage - 2017-03-11/2017-03-12
- ==== //Another// Radio Interview (in German), Radio Free FM, Ulm (2017-02-12, 13:00h - 15:00h) ====
+ ==== Another Radio Interview (in German), Radio Free FM, Ulm (2017-02-12, 13:00h - 15:00h) ====
* this time more focused on X2Go
* with Stefan and h1 as guests
==== 2016 ====
--
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 : 2016/12/16 19:52
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/events:start?rev=1481917764
New Revision: http://wiki.x2go.org/doku.php/events:start
Edit Summary: [2017]
User : stefanbaur
@@ -10,9 +10,11 @@
* TUEBIX 2017 - Date TBD
* Linux Expo Ulm 2017 - Date TBD (2017-05-06, maybe?)
* Chemnitzer LinuxTage - 2017-03-11/2017-03-12
- //Another// Radio Interview @ Radio Free FM, this time more focused on X2Go, 2017-02-12
+ ==== //Another// Radio Interview (in German), Radio Free FM, Ulm (2017-02-12, 13:00h - 15:00h) ====
+ * this time more focused on X2Go
+ * with Stefan and h1 as guests
==== 2016 ====
That's all, folks! :-) See you in 2017!
--
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 : 2016/12/16 19:49
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/events:start?rev=1481576022
New Revision: http://wiki.x2go.org/doku.php/events:start
Edit Summary: [2017]
User : stefanbaur
@@ -9,10 +9,10 @@
* LITA 2017 - Date TBD
* TUEBIX 2017 - Date TBD
* Linux Expo Ulm 2017 - Date TBD (2017-05-06, maybe?)
* Chemnitzer LinuxTage - 2017-03-11/2017-03-12
- * //another// radio interview @ Radio Free FM, this time more focused on X2Go (probably January or February 2017)
-
+
+ //Another// Radio Interview @ Radio Free FM, this time more focused on X2Go, 2017-02-12
==== 2016 ====
That's all, folks! :-) See you in 2017!
--
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 : 2016/12/16 18:50
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481903029
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment]
User : stefanbaur
@@ -179,21 +179,22 @@
=== What options are available under FURTHER-OPTIONS-GO-HERE? ===
These two are mutually exclusive, i.e. never put both of them in the same config:
- * ''sessionsurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below for how to add this file to your HTTP or FTP server.
+ *
''sessionsurl=http://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below for how to add this file to your HTTP or FTP server.
* ''broker-url=ssh:<nowiki>//</nowiki>your-broker-address-here'' - this allows you to specify an X2Go Session Broker instead of a sessions file (not limited to an ssh-based broker, works with an http-based broker as well)
These are entirely optional:
- * ''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - //not yet implemented// this will allow you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.
* ''xorgconfurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf'' - when a client outright refuses to boot into the graphical X2Go login screen, but gets stuck at the console or a
black screen instead, yet you can get the GUI to work using a regular Linux on the same hardware, you can disable the X Server's autodetection and force it to use the xorg.conf specified here. Note that you should use a more descriptive name for the file, as described below.
* ''xorg-resolution=HRESxVRES'' - will force the horizontal resolution to HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'', useful if autodetection for the correct screen size fails, but you do get as far as seeing the X2Go GUI
- * ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen)
* ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this allows you to specify an LDAP server to authenticate against
* ''ldap1=ldap-backupserver-1.example.com:389'' - this
allows you to specify the first of up to two LDAP backup servers when using LDAP authentication
* ''ldap2=ldap-backupserver-2.example.com:389'' - this allows you to specify the second of up to two LDAP backup servers when using LDAP authentication
* ''updateurl=rsync|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - //not yet implemented//. Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used.
* ''bwlimit=nn%'' - //not yet implemented//. Will allow you to specify a bandwidth limit for the backgrounded update task.
+ * ''pubkey=tftp|http|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.authorized_keys'' - //not yet implemented// this will allow you to add an ssh public key
file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.
+ * ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen)
+
=== Required unless using the X2Go Session Broker: Adding the x2go-tce.sessions session configuration file to your HTTP or FTP Server ===
Again, this is assuming you already have an existing, working HTTP or FTP server setup.
* run X2GoClient on any computer you like, and configure a session the same way it should appear on the ThinClient <note tip>when using a Windows client, run x2goclient.exe --portable, or it will store the session information in the registry, rather than in a "sessions" file.</note>
* locate the "sessions" file you just created - it should
be at ~/.x2goclient/sessions
--
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 : 2016/12/16 15:43
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481901882
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment]
User : stefanbaur
@@ -190,9 +190,10 @@
* ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen)
* ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this allows you to specify an LDAP server to authenticate against
* ''ldap1=ldap-backupserver-1.example.com:389'' - this allows
you to specify the first of up to two LDAP backup servers when using LDAP authentication
* ''ldap2=ldap-backupserver-2.example.com:389'' - this allows you to specify the second of up to two LDAP backup servers when using LDAP authentication
-
+ * ''updateurl=rsync|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - //not yet implemented//. Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used.
+ * ''bwlimit=nn%'' - //not yet implemented//. Will allow you to specify a bandwidth limit for the backgrounded update task.
=== Required unless using the X2Go Session Broker: Adding the x2go-tce.sessions session configuration file to your HTTP or FTP Server ===
Again, this is assuming you already
have an existing, working HTTP or FTP server setup.
* run X2GoClient on any computer you like, and configure a session the same way it should appear on the ThinClient <note tip>when using a Windows client, run x2goclient.exe --portable, or it will store the session information in the registry, rather than in a "sessions" file.</note>
* locate the "sessions" file you just created - it should be at ~/.x2goclient/sessions
--
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 : 2016/12/16 15:24
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481852207
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Build system prerequisites for all variants]
User : stefanbaur
@@ -25,10 +25,13 @@
* We suggest leaving at least 4 GB of free disk space so the build won't abort due to insufficient disk space while packages are downloaded, unpacked and copied around.
* Make sure your package list is up to date by running: <code>sudo apt-get update </code>
* Install the required packages by running: <code>sudo apt-get install git-core live-build live-config-doc live-manual-html live-boot-doc</code>
* export the following variables:<code>
- # Point this
to the git repository you wish to use
+ # Select ONE of the following git reposities
+ # this one loosely corresponds to "stable"
export LBX2GO_CONFIG='git://code.x2go.org/live-build-x2go.git::feature/openbox'
+ # this one loosely corresponds to "heuler"
+ #export LBX2GO_CONFIG='https://github.com/LinuxHaus/live-build-x2go::feature/openbox'
# Select ONE of the following LBX2GO_ARCH lines and comment out the others
# (feel free to use long or short options)
# for 64-Bit builds, use:
--
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 : 2016/12/16 01:36
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481848055
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment]
User : stefanbaur
@@ -180,9 +180,9 @@
* ''sessionsurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below for how to add this file to your HTTP or FTP server.
* ''broker-url=ssh:<nowiki>//</nowiki>your-broker-address-here'' - this allows you to specify an X2Go Session Broker instead of a sessions file (not limited to an ssh-based broker, works with an http-based broker as well)
These are entirely optional:
- * ''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - this allows you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.
+ * ''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - //not yet implemented// this will allow you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.
* ''xorgconfurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf'' - when a client outright refuses to boot into the graphical X2Go login screen, but gets stuck at the console or a black screen instead, yet you can get the GUI to work using a regular Linux on the same hardware, you can disable the X Server's autodetection and force it to use the xorg.conf specified
here. Note that you should use a more descriptive name for the file, as described below.
* ''xorg-resolution=HRESxVRES'' - will force the horizontal resolution to HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'', useful if autodetection for the correct screen size fails, but you do get as far as seeing the X2Go GUI
* ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen)
* ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this allows you to specify an LDAP server to authenticate against
--
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 : 2016/12/16 00:27
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481848001
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment]
User : stefanbaur
@@ -204,8 +204,9 @@
* copy it to x2go-tce.authorized_keys
* using an editor of your choice, edit x2go-tce.authorized_keys so it contains only the keys you want to appear on the ThinClient, and none that might have been created for a different purpose.
* log on to your HTTP or FTP server and change to the x2go-tce directory in your webroot/ftproot.
* copy the x2go-tce.authorized_keys file with your desired configuration to this directory.
+ * make sure the file is
chmodded 644, not 600
=== Optional: Adding the x2go-tce.xorg.conf file to your HTTP or FTP Server ===
Again, this is assuming you already have an existing, working HTTP or FTP server setup.
--
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 : 2016/12/16 00:26
Browser : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
IP-Address : 78.43.90.159
Hostname : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481846869
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary:
User : stefanbaur
@@ -180,9 +180,9 @@
* ''sessionsurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below for how to add this file to your HTTP or FTP server.
* ''broker-url=ssh:<nowiki>//</nowiki>your-broker-address-here'' - this allows you to specify an X2Go Session Broker instead of a sessions file (not limited to an ssh-based broker, works with an http-based broker as well)
These are entirely optional:
- *
''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - this allows you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH
+ * ''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - this allows you to add an ssh public key file to the ThinClient, so your administrators can log in remotely using SSH. Note that this file needs to be chmodded 644, not 600, on the web server.
* ''xorgconfurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf'' - when a client outright refuses to boot into the graphical X2Go login screen, but gets stuck at the console or a black screen instead, yet you can get the GUI to work using a regular Linux on the same hardware, you can disable the X Server's autodetection and force it to use the xorg.conf specified here. Note that you should use a more descriptive name for the file, as described below.
* ''xorg-resolution=HRESxVRES'' - will force
the horizontal resolution to HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'', useful if autodetection for the correct screen size fails, but you do get as far as seeing the X2Go GUI
* ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow you to specify how multiple screens are handled (same-as clones the primary screen to all secondary screens, the other commands will cascade and thus expand the screen)
* ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this allows you to specify an LDAP server to authenticate against
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/