Op vrijdag 14 september 2018 02:14:35 CEST schreef David C. Rankin:
On 09/12/2018 05:39 AM, Liam Proven wrote:
Why Tumbleweed _as a server_?
For my servers, I want stability and low maintenance, with few updates.
Tumbleweed means daily updates and reboots.
If Tumbleweed is "rolling well", the there isn't any reason not to use it as a server -- you get the latest packages (with the latest security fixes) as they come out. HOWEVER, if there are any problems with updates OR a version update hits (e.g. apache 2.2-2.4, php5.6 to 7, etc.. where config changes are required) - you must be ready for them or a simple update can leave your server inoperable.
I have done servers both ways over the years. I've used Mandrake, SuSE/openSuSE and Archlinux for server installs, and there really is no difference other than the application versions. Recently (past 7-8 years) I've used rolling releases for servers -- but you have to know and be ready for version changes.
As far as distros, I've used pretty much all -- and have never had any leave me in an unbootable condition (at least to the maintenance shell -- which is fine unless you are remote admining the server)
The rolling verses release distinction between what to use for a server is pretty much a moot point.
It's not. A server that's supposed to be there 24/7 with as less downtime as possible does not benifit from a rolling release. Having said that, my own VPS run Tw. But I would never ever deliver a Tw based server to customers. Never.
Regardless whether you are getting new kernels as they come out, or getting kernel updates with backported patches -- the reboot is the same either way... A daily reboot or an occasional one can make a huge difference in selling services to customers.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org