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-u...@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/
_______________________________________________
x2go-commits mailing list
x2go-commits@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-commits
