This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
doc:success-stories:debian-edu [2013/03/10 10:07] sunweaver [Deployment Story: Debian Edu / Skolelinux and X2Go (without TJENER)] |
doc:success-stories:debian-edu [2017/01/16 16:54] (current) stefanbaur ↷ Page moved from doc:deployment-stories:debian-edu to doc:success-stories:debian-edu |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Deployment Story: Debian Edu / Skolelinux and X2Go (without TJENER) ====== | ====== 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 | + | //Shared by: Mike Gabriel |
| - | However, those who feel overwhelmed by its grown complexity, please consider | + | 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' |
| + | |||
| + | However, those who feel overwhelmed by Debian Edu' | ||
| ===== Your Gateway ===== | ===== Your Gateway ===== | ||
| * Install ipFire as a Gateway on some minor hardware | * Install ipFire as a Gateway on some minor hardware | ||
| - | * Red + Green interface | + | * Red + Green interface |
| * let the Red interface connect you to the internet | * let the Red interface connect you to the internet | ||
| * Enable DHCP service on the Green interface | * Enable DHCP service on the Green interface | ||
| Line 19: | Line 21: | ||
| * two fast hard drives (SSD) | * two fast hard drives (SSD) | ||
| * 2 network cards | * 2 network cards | ||
| - | * Install a Debian Edu / Skolelinux Standalone system (no TJENER!) | + | * Install a Debian Edu / Skolelinux Standalone system (no TJENER!) |
| * Make sure that your Skolelinux system' | * Make sure that your Skolelinux system' | ||
| * Test local login, test DNS, install required (educational) software | * Test local login, test DNS, install required (educational) software | ||
| Line 26: | Line 28: | ||
| ===== Basic X2Go Installation ===== | ===== Basic X2Go Installation ===== | ||
| - | * Then proceed setting up X2Go Server on the Skolelinux system: | + | * Then proceed |
| * Add the X2Go archives for Debian to the Skolelinux system | * Add the X2Go archives for Debian to the Skolelinux system | ||
| * Install the packages '' | * Install the packages '' | ||
| - | * Test X2Go access to the Skolelinux system from another client machine that gets hooked up on the Green network interface of the ipFire system | + | * Test X2Go access to the Skolelinux system from another client machine that gets hooked up to the Green network interface of the ipFire system |
| ===== X2Go Thin Client Environment ===== | ===== X2Go Thin Client Environment ===== | ||
| - | * Then proceeed with setting up the X2Go Thin Client Environment on the Skolelinux system: | + | * Then proceeed with setting up an X2Go Thin Client Environment on the Skolelinux system: |
| - | * Install the package '' | + | * Install the package '' |
| * Follow the X2Go TCE documentation in this wiki to get the TCE up and running | * Follow the X2Go TCE documentation in this wiki to get the TCE up and running | ||
| - | * Make sure you serve the X2Go Thin Clients via the //second// network interface of the Skolelinux system | + | * During the X2Go TCE installation you will be guided to set up a DHCP+PXE server on the Skolelinux system. |
| + | * Connect minimal, power-saving systems (i.e. thin-client-like hardware) two the Skolelinux system' | ||
| ==== What you have at the end... ==== | ==== What you have at the end... ==== | ||