From owner-freebsd-stable Fri Aug 6 22: 0:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id B33C814CE5 for ; Fri, 6 Aug 1999 22:00:35 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-122.atl.bellsouth.net [209.214.65.122]) by mail0.atl.bellsouth.net (3.3.0/8.9.3) with ESMTP id AAA24843; Sat, 7 Aug 1999 00:53:37 -0400 (EDT) Received: from wghicks.bellsouth.net (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id AAA01918; Sat, 7 Aug 1999 00:57:48 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199908070457.AAA01918@bellsouth.net> To: "lweb Lightningweb" Cc: freebsd-stable@freebsd.org, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com, wghicks@wghicks.bellsouth.net Subject: Re: continued crashes with 3.1-Stable In-reply-to: Your message of "Fri, 06 Aug 1999 20:32:40 PDT." <19990807033241.17071.qmail@hotmail.com> Date: Sat, 07 Aug 1999 00:57:48 -0400 From: W Gerald Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh... If you are running 3.1 then you aren't "tracking stable". :-) I'd certainly recommend that as a prudent course for production systems. Some would argue that freezing on a particular snapshot is the best strategy for maintaining stability for "production systems". I believe that a complete strategy includes monitoring the activity on the stable mailing lists *and* watching the updates to software installed from the ports systems. It's nice to have a few spare machines for building and testing prior to production deployment. Larger installations can benefit by having a local FreeBSD mirror (CVSup/WWW/FTP). Good Luck, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message