On Thu, Nov 17, 2005 at 02:39:41PM -0500, Andrew Conkling wrote: > On 11/17/05, Doug Jolley <[EMAIL PROTECTED]> wrote: > > Anyway, now that I'm more clear on how the Rolling Release System works > > (thanks to your response), maybe my real question is, "What is the best way > > to keep production systems secure and bug free without having to track > > Current and expose oneself to the risk that an update will break something? > > Probably not to use Arch, but to use something that does have a static > release cycle. I think you could do this by just syncing to the > Wombat repo, but as Jason mentioned, you won't see any updates. > > Maybe someone else has a better idea?
Certainly! Here's the thing - if you are concerned about security, you're going to have to install security updates every so often. In most situations, if there is a security issue with some app, a new version is released, and arch is upgraded. If you follow alot of the releases, this happens faster than most distros. Let's look at it this way: foobarbaz-1.1 has a security issue (ZOMGPANIX!). Debian updates to foobarbaz-1.1.1 or however they version those things. Arch updates to foobarbaz-1.1-2. Both updates happen in about the same period of time. Either way, you're going to have to be concerned with making sure config files are still good and making sure the updates didn't screw anything up. In addition, for server-type stuff you're really not going to have much updated that often - my server sits for a few weeks without an update - and I'm using packages from [unstable] and [community] too. I'd say give it a whirl on one machine, it'd be fun. There are many people that run business on Arch boxes. - phrak _______________________________________________ arch mailing list arch@archlinux.org http://www.archlinux.org/mailman/listinfo/arch
