[X2Go-Commits] [[X2Go Wiki]] page changed: doc:howto:tce

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2016/12/15 03:19
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=1481771510
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Building your own netbootable X2Go-TCE image] 
User        : stefanbaur

@@ -179,9 +179,10 @@
  
  === What options are available under FURTHER-OPTIONS-GO-HERE? ===
    * ''sessionsurl=http://your-http-server-ip-here/x2go-demo/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below how to add this file to your HTTP or FTP server.
    * ''pubkey=http://192.168.1.1/x2go-tce/x2go-tce.authorized_keys'' - this allows you to add a ssh public key file to the ThinClient, so your administrators can log in
remotely using SSH
-   * ''xorg-resolution=HRESxVRES'' - will force the horizontal resolution to HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'', useful if autodetection fails
+   * ''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
    *
''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 
  
@@ -201,6 +202,13 @@
    * 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.
+ 
+ 
+ === 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.
+   * copy the xorg.conf file from the working system to x2go-tce.xorg.conf - actually, to something that lets you tell which hardware it is made for, like x2go-tce-old-P4-whitebox-with-crappy-VGA.xorg.conf
+   * log on to your HTTP or FTP server and change to the x2go-tce directory in your webroot/ftproot.
+   * copy the x2go-tce.xorg.conf file (or whatever you named it) with your desired configuration to this directory.
  
  


-- 
This mail was generated by DokuWiki at
http://wiki.x2go.org/