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/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2016/12/16 00:07
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=1481846680
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment]
User : stefanbaur
@@ -176,9 +176,9 @@
=== 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-demo/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-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
--
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/15 22:37
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=1481838206
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Build system prerequisites for all variants]
User : stefanbaur
@@ -23,9 +23,9 @@
* You need a Debian Jessie system to build the image. (Other distributions based on Debian might work, but this is untested.)
* We suggest using a 64-Bit system, however, it is possible to use a 32-Bit system if you don't want to build a 64-Bit ThinClient image.
* 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 lzma live-build live-config-doc live-manual-html live-boot-doc</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
export LBX2GO_CONFIG='git://code.x2go.org/live-build-x2go.git::feature/openbox'
--
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/15 21: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=1481836102
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Build system prerequisites for all variants]
User : stefanbaur
@@ -41,9 +41,9 @@
# These options are meant to reduce the image size.
# Feel free to adapt them after consulting "man lb_config"
export LBX2GO_SPACE='--checksums none --apt-indices none --cache false
--win32-loader false --memtest none
- --firmware-binary false --initramfs-compression bzip2'
+ --firmware-binary false'
# These are default values that should not require tuning
export LBX2GO_DEFAULTS='--initsystem
sysvinit --security true --updates true
--apt-recommends false --firmware-chroot true
--
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/15 21:08
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=1481835644
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [List of open ToDos/FIXMEs for this page]
User : stefanbaur
@@ -341,15 +341,18 @@
HDD images mean you might have to jiggle with syslinux or grub.
FIXME Some of the optional steps above could be moved to a separate subpage to reduce clutter.
- FIXME The steps for the build process could probably streamlined into an x2go-tce.deb Debian package
+ FIXME The steps for the build process could probably streamlined into an x2go-tcebuilder.deb Debian package
Ideas:
- * instead of the "exports" stuff, use a config file e.g. under
/etc/x2go/x2go-tce/config and source its contents
+ * instead of the "exports" stuff, use a config file e.g. under /etc/x2go/x2go-tcebuilder/config and source its contents
* instead of copy-pasting the build commands, turn most of it into a script as /usr/bin/x2go-tcebuilder or something (the remaining config parts in the copy-paste block would have to be moved into the config file)
* our config would be used as suggestion by linking to it; a user could create their own by replacing the link with a regular file (similar to how /etc/x2go/applications works)
* our additional live-scripts would be shipped inside the package and similar to how apache does it with sites-available and sites-active - not pulling in content from git each time
- * store the results somewhere under /var/x2go-tce/ or whatever the proper place according to FHS and Debian would be
+ * /etc/x2go/x2go-tcebuilder/scripts-active (dir with symlinks to all active scripts)
+ *
/etc/x2go/x2go-tcebuilder/scripts-available (dir with symlinks to our templates and with regular user-created files)
+ * /usr/share/x2go-tcebuilder/template-scripts (scripts we ship, with a big fat header that they should not be changed, but copied)
+ * store the results somewhere under /var/lib/x2go-tcebuilder/ or whatever the proper place according to FHS and Debian would be
* turning it into a package would mean we could add dependencies as well, so the manual apt-get install would not be neccessary
* additional scripts could be added that work "automagically" if there's no PXE/TFTP/HTTP/FTP server yet - maybe in a separate package x2go-tce-setup-aids.deb which then has dependencies on atftpd and apache|lighttpd, ...
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/