From owner-freebsd-isp Thu Apr 15 8: 7:41 1999 Delivered-To: freebsd-isp@freebsd.org Received: from loki.intrepid.net (intrepid.net [204.71.127.3]) by hub.freebsd.org (Postfix) with ESMTP id 03D9114D24 for ; Thu, 15 Apr 1999 08:07:38 -0700 (PDT) (envelope-from mark@loki.intrepid.net) Received: (from mark@localhost) by loki.intrepid.net (8.8.5/8.8.5) id LAA18218 for freebsd-isp@FreeBSD.ORG; Thu, 15 Apr 1999 11:05:16 -0400 Message-ID: <19990415110515.D11117@intrepid.net> Date: Thu, 15 Apr 1999 11:05:15 -0400 From: Mark Conway Wirt To: freebsd-isp@FreeBSD.ORG Subject: CVSUP and Stability Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We're getting ready to put our first FreeBSD production machine in place (we've used Linux in the past), and I have a quick question about the strategies you all use for upgrading your machines. I have the machine synced to 3-stable, which is great, but I can't be "make worlding" every couple of days, as this *is* a production machine that needs to be up 24x7. How do you all handle upgrades/patches to production machines? 1) Do you cvsup often and only rebuild parts of the system that change? (if this is the case, how do you handle interactions between updated kernel files and utilities that interact with the kernel)? 2) Do you only patch for security and seriously broken things? 3) Do you put your machines up and forget about them? TIA! --Mark -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message