I have used Suse and then opensuse on various PC’s for many years. Then went to a MacBook. However, I find myself with a Dell PowerEdge 2590 and considering installing Tumbleweed on it as server Any tips would be welcome. I am also planning to install Tumbleweed onto a PC soon Sean -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/09/2018 21:42, Sean Rima wrote:
I have used Suse and then opensuse on various PC’s for many years. Then went to a MacBook.
However, I find myself with a Dell PowerEdge 2590 and considering installing Tumbleweed on it as server
Why Tumbleweed _as a server_? For my servers, I want stability and low maintenance, with few updates. Tumbleweed means daily updates and reboots. It may fit what you want, but it sounds bad to me.
Any tips would be welcome. I am also planning to install Tumbleweed onto a PC soon
I think you should do that first and get to know it a little before you decide. :-) Me, I would go with Leap 15 for a server. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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. 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... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
On 09/13/2018 07:29 PM, Knurpht-openSUSE wrote:
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.
Granted, I should have been more clear -- for your own servers (for me I admin for my home and my office -- I don't do anything for customers -- that I leave to SuSE and RedHat) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
David C. Rankin -
Knurpht-openSUSE -
Liam Proven -
Sean Rima