Hi Mike,
at http://wiki.x2go.org/installing_x2go_thin_client_environment_debian you highly recommend to set up a server of it's own. Where is the rationale behind this strong recommendation? Especially as I can see no major security risks running the server (you need root to set it up, of course). At least none you can solve by using an extra server. But there is quite a bit of overhead running the whole thing in a VM as it has mainly I/O. And if one already has a nfs running, I can really see no need for the extra overhead.
Cheers Morty
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
Hi Morty,
On Di 14 Jun 2011 11:20:53 CEST Moritz Struebe wrote:
Hi Mike,
at http://wiki.x2go.org/installing_x2go_thin_client_environment_debian
first note: this wiki page is in the middle of a process... ;-)
you highly recommend to set up a server of it's own. Where is the rationale behind this strong recommendation? Especially as I can see no major security risks running the server (you need root to set it up, of course). At least none you can solve by using an extra server. But there is quite a bit of overhead running the whole thing in a VM as it has mainly I/O. And if one already has a nfs running, I can really see no need for the extra overhead.
The reason why I recommend hosting of chroot images on a separate
machine (a machine that does nothing else, apart from being a PXE
server) is that when upgrading the chroot you may encounter service
restarts during package upgrades that might have an effect on other
system components.
The strategy has been adopted from a friend of mine who is a Linux
service provider for schools in Oslo (Debian Edu context). They mostly
roll out diskless workstations there (i.e. systems with NFS-roots) and
that originally is their experience.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 2011-06-14 13:42, Mike Gabriel wrote:
The reason why I recommend hosting of chroot images on a separate machine (a machine that does nothing else, apart from being a PXE server) is that when upgrading the chroot you may encounter service restarts during package upgrades that might have an effect on other system components.
Which components are you thinking of? Or just possible apt-get updates?
The strategy has been adopted from a friend of mine who is a Linux service provider for schools in Oslo (Debian Edu context). They mostly roll out diskless workstations there (i.e. systems with NFS-roots) and that originally is their experience.
While I see your poit, I think this solution might be a suggestions, but not in any way recommended. If you don't yet have the appropriate infrastructure using an extra server or VM might backfire badly, as it is yet another server to be taken care of.
Cheers Morty
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
Hi Morty,
On Di 14 Jun 2011 13:49:30 CEST Moritz Struebe wrote:
On 2011-06-14 13:42, Mike Gabriel wrote:
The reason why I recommend hosting of chroot images on a separate machine (a machine that does nothing else, apart from being a PXE server) is that when upgrading the chroot you may encounter service restarts during package upgrades that might have an effect on other system components.
Which components are you thinking of? Or just possible apt-get updates?
The strategy has been adopted from a friend of mine who is a Linux service provider for schools in Oslo (Debian Edu context). They mostly roll out diskless workstations there (i.e. systems with NFS-roots) and that originally is their experience.
While I see your poit, I think this solution might be a suggestions, but not in any way recommended. If you don't yet have the appropriate infrastructure using an extra server or VM might backfire badly, as it is yet another server to be taken care of.
Cheers Morty
Ok, I will take that into consideration and adapt the wiki page where needed.
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Mike Gabriel -
Moritz Struebe