To view parent comment, click here.
To read all comments associated with this story, please click here.
actually, it is exactly because they don't want it. strange but true.
you set server into runlevel 3. and when you need some software you simply do this from remote machine:
ssh username@machine -Y whatever_command (like. firefox, system-config-network)
and graphic session runs on local machine not server. server is still in runlevel 3. and you never needed to go into runlevel 5 on server to configure something from gui.
i'm avid network X addict, but as long as wayland options me to run seamless remote session like one before while server is in runlevel 3... i'm all for it. seamless remoting shouldn't be hard to implement with any protocol,... while in runlevel 3? well, that i don't know
Edited 2010-11-13 17:10 UTC
What is it about runlevel 3 that makes you think it can't run X? Because Red Hat said so?
On my system runlevel 2 is normal and runlevel 3 starts up some optional stuff I don't need all the time. Runlevels 4 and 5 I don't even bother with.
Beware the fallacy of presuming that how you do things is the universal standard. That's bad in a Windowsy sort of way.
You don't need GUI - far from it, all you do need X libraries (inc/ tool-kits such as GTK/QT) and SSHD to run your favorite administration tool.
Better yet, add SSH compression (ssh -C) to the mix and you can actually run X application over a fairly slow DSL or cable line. (Though I would agree that remote X is not a speed daemon - especially when uplink is below 512KB)
- Gilboa




Member since:
2007-09-22
I've never understood why people would want a GUI on a server.