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.
I'm planning to build a LAMP server running Slackware 11.0 as OS. There will be no X-window on the server avoiding risk hole. To overcome the difficulty on searching Internet in case of need I'm prepared to connect a workstation via ssh to remote administrate the server. I have following point unresolved.
If installing webmin, postixadmin, etc. for easy-configuration/administration I still need X-windown unless using command lines throughout configuration/administration. Personally I prefer using command lines but their tutorial not easy to find.
What are your suggestions? Installing X on the server but without it started on boot? Just evoke it when needed? As convenience concerned one PC to work is better than running 2 PCs to do the same job.
If I'm compelled to run X on the server I'll install Xfce4, the light-weight desktop.
Comments and recommendation will be appreciated. TIA
If you connect to the server from a workstation through SSH, you can use X forwarding so that your workstation's X server is used. You still need the X libraries on your server machine, but you never have to start the X server there.
If you connect to the server from a workstation through SSH, you can use X forwarding so that your workstation's X server is used. You still need the X libraries on your server machine, but you never have to start the X server there.
Whether I still need to install xorg and its lib?, similar to this server built for testing. xorg and xfce4, the light weight desktop have been installed but they won't start at boot. I only start them on browsing Internet. AFAIK webmin does not need X. I have no idea about postfixadmin. I'll find it out later. What packages on the server need X? TIA.
Edit:-
If I have full X installed on the server. What will be the advantage for me running remote installation and configuration via a workstation at the beginning, keeping 2 PCs running at the same time. I think I need remote adminstration only at the time when the server is on full production. At the beginning I can do normal installation and configuration on the server.
Of course you can start X on the server for configuration before you put it life. But it might just be as useful to get the habit to administer it remotely through SSH.
Just to set the vocab straight:
- from your perspective, you have a server which you want to administrate and a client workstation which you use for administration
- for X, it's the other way round: the graphical program that runs on your server is the X client and on your workstation you need an X server
so the packages you need to install on your server are the packages needed for an X client, and on your workstation you need a running X server. But if you don't start the X server on your server machine, I'd just install all of X and make sure it doesn't get started by default.
If installing webmin, postixadmin, etc. for easy-configuration/administration I still need X-windown unless using command lines throughout configuration/administration. Personally I prefer using command lines but their tutorial not easy to find.
Why you think you need X? Just point your browser from another box on your LAN to the server IP : port and that's it.
Why you think you need X? Just point your browser from another box on your LAN to the server IP : port and that's it.
At the beginning befor the server full configured and put to production, X on the server only helps me reading online documents and seeking for help. It avoids running 2 PCs at the same time doing a single job.
Power cable, ethernet cable, server is all you need! Just make sure the box boots without having to do anything.
Plug it in, turn it on, give about 3 minutes for startup, and then try to SSH from the local network.
And don't bother with X on a server. Webmin and things like that are website interfaces, they don't run on X. I would say don't install those either. Everything a server does can be done through SSH.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.