[X2go-Commits] page changed: doc:deployment-stories:debian-edu
wiki-admin at x2go.org
wiki-admin at x2go.org
Sun Mar 10 11:09:27 CET 2013
A page in your DokuWiki was added or changed. Here are the details:
Date : 2013/03/10 10:09
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address : 46.142.185.6
Hostname : 6-185-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/doc:deployment-stories:debian-edu?rev=1362910088
New Revision: http://wiki.x2go.org/doku.php/doc:deployment-stories:debian-edu
Edit Summary: [Deployment Story: Debian Edu / Skolelinux and X2Go (without TJENER)]
User : sunweaver
@@ -1,9 +1,9 @@
====== Deployment Story: Debian Edu / Skolelinux and X2Go (without TJENER) ======
- In Debian Edu contexts the main criticism since the release of Debian Edu / Skolelinux squeeze is: the whole Debian Edu system has become far to complex (LDAP, Kerberos, GOsa², Samba, LTSP, ...). The default Skolelinux system has become more complex, that is true indeed. If it has become too complex is another discussion.
+ In Debian Edu
contexts the main criticism since the release of Debian Edu / Skolelinux squeeze is: the whole Debian Edu system has become far to complex (LDAP, Kerberos, GOsa², Samba, LTSP, ...). The default Skolelinux system has become more complex, that is true indeed. If it has become too complex is another discussion. From the view point of a Debian Edu developer and IT service provider, the system is just as it has to be. From a teacher's perspective, I deeply get the criticism of to much complexity.
- However, those who feel overwhelmed by its grown complexity, please consider this approach:
+ However, those who feel overwhelmed by Debian Edu's grown complexity, please consider the approach described below.
===== Your Gateway =====
* Install ipFire as a Gateway on some minor hardware
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
More information about the x2go-commits
mailing list