On Sat, May 14, 2011 at 08:10:01PM -0400, Greg Freemyer wrote:
On Sat, May 14, 2011 at 1:11 PM, jdd
wrote: Le 14/05/2011 18:48, Greg Freemyer a écrit :
I'm new to rolling updates, but if one of the eventual targets of Tumbleweed is servers, there needs to be way to roll a consistent set of updates to first a test server, and then to production servers.
I wouldn't use Tumblweed for servers, but evergreen (but may be I'm wrong)
From my understanding, a lot of people run Arch on servers because they prefer a slow continuous upgrade process instead of a big upgrade every year or two.
I don't know if the long term goal of Tumbleweed is to support that model or not.
Yes it is, and I use it that way, but again, using Arch you don't get a "consistant set of updates" either, just like Gentoo or Debian unstable. Although you can set up a test and roll-out method that creates this, just like you have to do for the other distros, it's not "built in" unlike the "enterprise" distros that are offered by SUSE and Red Hat. Again, different models for different usages and people. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org