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 using Opensuse 13.1 KDE on desktop, and collecting information about that
For a datacenter, I think that any 'consumer' distro is not a good fit. I use openSUSE myself, and like it...yast is a good tool, and is similar to things found in RHEL/CentOS, but you can also manage the system through command-line.
That said, I wouldn't put a rapid-release distro on a server. Too many updates, too quick. Even with a long-term release, you'll be getting updates a LOT, on a production system. Changing things rapidly can cause problems, in my experience, that are difficult to diagnose. I'd stick with a SuSE Enterprise, CentOS, or similar 'server' distro. And I'd NOT run KDE (or ANY GUI) on it.
For a datacenter, I think that any 'consumer' distro is not a good fit. I use openSUSE myself, and like it...yast is a good tool, and is similar to things found in RHEL/CentOS, but you can also manage the system through command-line.
That said, I wouldn't put a rapid-release distro on a server. Too many updates, too quick. Even with a long-term release, you'll be getting updates a LOT, on a production system. Changing things rapidly can cause problems, in my experience, that are difficult to diagnose. I'd stick with a SuSE Enterprise, CentOS, or similar 'server' distro. And I'd NOT run KDE (or ANY GUI) on it.
It's popular here, too.
In this life, what can't you say that about?
What would make it better, in your opinion?
The loading screen is a bit tiring. And I often run several tools in the same time, but Yast2 wants us to do only one thing once. I hate to be interrupted...
I fell in love with the tty the day I was remoted into a machine, running a "top" and staring off into space and my boss walked up, looked at the terminal and said, " Oh, sorry, I didn't think you were busy" and walked away.
I fell in love with the tty the day I was remoted into a machine, running a "top" and staring off into space and my boss walked up, looked at the terminal and said, " Oh, sorry, I didn't think you were busy" and walked away.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.