A page in your DokuWiki was added or changed. Here are the details:
Date : 2016/12/15 13:02
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=1481806823
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary:
User : stefanbaur
@@ -235,8 +235,10 @@
* After that, your ThinClient should boot the X2Go-TCE image.
* Note that it is possible to use partial matching, so a symlink starting with "01-AA-BB-CC" would match all ThinClients with a MAC address starting with "AA-BB-CC" and so on.
* For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value
and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce.
+ --------------------------------------------------------
+ ===== List of open ToDos/FIXMEs for this page =====
FIXME This page is missing a section/subpage that explains how to use the content of the tar file located in the build directory **if no PXE/TFTP/HTTP server is present** yet.
Basically, debian-live/live/filesystem.squashfs becomes (webroot)/x2go-tce/x2go-tce-filesystem.squashfs and everything from tftpboot/ goes into the TFTP root directory. After that, one should proceed as described above regarding creation of files and symlinks.
--
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 13:00
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=1481806797
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Final Steps to boot a ThinClient]
User : stefanbaur
@@ -236,9 +236,9 @@
* Note that it is possible to use partial matching, so a symlink starting with "01-AA-BB-CC" would match all ThinClients with a MAC address starting with "AA-BB-CC" and so on.
* For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink
name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce.
- FIXME This page is missing a section/subpage that explains how to use the content of the tar file located in the build directory if no PXE/TFTP/HTTP server is present yet.
+ FIXME This page is missing a section/subpage that explains how to use the content of the tar file located in the build directory **if no PXE/TFTP/HTTP server is present** yet.
Basically, debian-live/live/filesystem.squashfs becomes (webroot)/x2go-tce/x2go-tce-filesystem.squashfs and everything from tftpboot/ goes into the TFTP root directory. After that, one should proceed as described above regarding creation of files and symlinks.
Sample contents of live-image-i386.netboot.tar:
--
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 12:59
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=1481806505
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Final Steps to boot a ThinClient]
User : stefanbaur
@@ -237,9 +237,12 @@
* For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce.
FIXME This page is missing a section/subpage that explains how to use the content of the tar file located in the build
directory if no PXE/TFTP/HTTP server is present yet.
- Sample contents of live-image-i386.netboot.tar
+
+ Basically, debian-live/live/filesystem.squashfs becomes (webroot)/x2go-tce/x2go-tce-filesystem.squashfs and everything from tftpboot/ goes into the TFTP root directory. After that, one should proceed as described above regarding creation of files and symlinks.
+
+ Sample contents of live-image-i386.netboot.tar:
<code>
drwxr-xr-x root/root 0 2016-12-15 13:28 debian-live/
drwxr-xr-x root/root 0 2016-12-15 13:38 debian-live/live/
-rw-r--r-- root/root 240087040 2016-12-15 13:33 debian-live/live/filesystem.squashfs
--
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 12:55
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=1481803948
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Final Steps to boot a ThinClient]
User : stefanbaur
@@ -237,8 +237,34 @@
* For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce.
FIXME This page is missing a section/subpage that explains how to use the content of the tar file located in the build
directory if no PXE/TFTP/HTTP server is present yet.
+ Sample contents of live-image-i386.netboot.tar
+ <code>
+ drwxr-xr-x root/root 0 2016-12-15 13:28 debian-live/
+ drwxr-xr-x root/root 0 2016-12-15 13:38 debian-live/live/
+ -rw-r--r-- root/root 240087040 2016-12-15 13:33 debian-live/live/filesystem.squashfs
+ -rw-r--r-- root/root 11579 2016-12-15 13:37 debian-live/live/filesystem.packages
+ -rw-r--r-- root/root 74 2016-12-15 13:37 debian-live/live/filesystem.packages-remove
+ drwxr-xr-x root/root 0 2016-12-15 13:38 tftpboot/
+ drwxr-xr-x root/root 0 2016-12-15 13:38 tftpboot/live/
+ -rw-r--r-- root/root 23 2016-12-15 13:37 tftpboot/live/initrd.img
+ -rw-r--r-- root/root 2831760 2016-12-15 13:37 tftpboot/live/vmlinuz
+ drwxr-xr-x root/root 0 2015-04-28 14:01 tftpboot/pxelinux.cfg/
+ -rw-r--r-- root/root 57 2014-10-25 14:21 tftpboot/pxelinux.cfg/default
+ -rw-r--r-- root/root 351 2016-12-15 13:38
tftpboot/live.cfg
+ -rw-r--r-- root/root 116624 2015-08-19 15:17 tftpboot/ldlinux.c32
+ -rw-r--r-- root/root 270 2016-12-15 13:38 tftpboot/menu.cfg
+ -rw-r--r-- root/root 26188 2015-08-19 15:17 tftpboot/vesamenu.c32
+ -rw-r--r-- root/root 268 2016-12-15 13:38 tftpboot/install.cfg
+ -rw-r--r-- root/root 508 2016-12-15 13:38 tftpboot/stdmenu.cfg
+ -rw-r--r-- root/root 35159 2016-12-15 13:38 tftpboot/splash.png
+ -rw-r--r-- root/root 23480 2015-08-19 15:17 tftpboot/libutil.c32
+ -rw-r--r-- root/root 153 2016-12-15 13:38 tftpboot/advanced.cfg
+ -rw-r--r-- root/root 182552 2015-08-19 15:17 tftpboot/libcom32.c32
+ -rw-r--r-- root/root 42988 2015-08-19 15:17 tftpboot/pxelinux.0
+ -rw-r--r-- root/root 164096 2015-08-19 15:17 tftpboot/hdt.c32
+ </code>
FIXME This page is missing a section/subpage that explains how to speed up the netboot process using iPXE.
FIXME This page is missing a section/subpage that explains how to create
images for USB/CD/local storage.
--
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 12:12
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=1481803779
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Final Steps to boot a ThinClient]
User : stefanbaur
@@ -250,9 +250,9 @@
Ideas:
* instead of the "exports" stuff, use a config file e.g. under /etc/x2go/x2go-tce/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 similar to how apache does it with sites-available and sites-active
+ * 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
* 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/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2016/12/15 12:09
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=1481802678
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Final Steps to boot a ThinClient]
User : stefanbaur
@@ -237,8 +237,10 @@
* For further matching options (IP-based, for example), please consult the pxeboot documentation. In short, it should be possible (i.e. untested by us), but it a) requires you to assign static DHCP IPs and b) you need to translate the IP to its hexadecimal value and use that value as the symlink name, so e.g. 192.168.0.1 becomes C0A80001 -> x2go-tce.
FIXME This page is missing a section/subpage that explains how to use the content of the tar file located in the build
directory if no PXE/TFTP/HTTP server is present yet.
+
+ FIXME This page is missing a section/subpage that explains how to speed up the netboot process using iPXE.
FIXME This page is missing a section/subpage that explains how to create images for USB/CD/local storage.
FIXME Some of the optional steps above could be moved to a separate subpage to reduce clutter.
--
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 11: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/doc:howto:tce?rev=1481802515
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary:
User : stefanbaur
@@ -1,18 +1,8 @@
====== X2Go-ThinClientEditon (TCE, TCE-NG, TCE-New) ======
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
- FIXME The steps for the build process could probably streamlined into an x2go-tce.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
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 similar to how apache does it with sites-available and sites-active
- * store the results somewhere under /var/x2go-tce/ 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, ...
===== History,
Rationale, Outlook =====
During the time of Debian Wheezy being Debian's stable release, we started developing a new ThinClientEdition (TCE) - one that is based on Debian-Live and thus does no longer rely on NFS. Instead, the entire image is loaded into the RAM of the ThinClient machine.
@@ -251,4 +241,16 @@
FIXME This page is missing a section/subpage that explains how to create images for USB/CD/local storage.
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
+
+ Ideas:
+ * instead of the "exports" stuff, use a config file e.g. under /etc/x2go/x2go-tce/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 similar to how apache does it with sites-available and sites-active
+ * store the results somewhere under /var/x2go-tce/ 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/
A page in your DokuWiki was added or changed. Here are the details:
Date : 2016/12/15 11:48
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=1481802476
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [X2Go-ThinClientEditon (TCE, TCE-NG, TCE-New)]
User : stefanbaur
@@ -1,9 +1,9 @@
====== X2Go-ThinClientEditon (TCE, TCE-NG, TCE-New) ======
<note important>This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.</note>
- FIXME This whole build process could probably streamlined into an x2go-tce.deb
+ FIXME The steps for the build process could probably streamlined into an x2go-tce.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 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)
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/