Disadvantages of administering a server with a WM as opposed to a pure TTY interface
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian for server, CrunchBang for everything that's not a server
Posts: 143
Rep:
Disadvantages of administering a server with a WM as opposed to a pure TTY interface
I am running a simple LAMP server from home. My distribution of choice for doing so is CrunchBang 10 (Statler), which is based on Debian's stable branch.
CrunchBang is an Openbox-focused distribution, and as such comes with Openbox laid on top of standard Debian Squeeze. I am happy with this arrangement, as I don't yet feel quite comfortable enough with the Linux command-line/TTY interface to rely on it exclusively. Openbox is my graphical "security blanket" for server administration.
My choice to run a WM on a machine being used in a server context has been met with many quizzical expressions. It seems that most Linux sysadmins prefer a pure command-line/TTY interface for administering a server. I can understand this from the perspective of pure resource-efficiency, but I'm not sure if there are some other reasons as well.
What are the potential disadvantages of running a windowmanager on a server, aside from that of disk space usage?
In my experience, none for what you are doing, unless you feel compelled to learn the command-line way.
Remember that most servers in data centers are headless, that is, they sit in racks and have no monitors or keyboards. Accordingly, sysadmins connect vis ssh and administer them through the terminal.
People have the notion that, because so-called "server" distros come with no GUI, that somehow a GUI on a server is inherently bad.
As far as I am concerned, that's just a notion. It's not inherently bad unless it soaks up resources the server otherwise needs. For a little home server, that's extremely unlikely. Use the tools that you feel comfortable using.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.