From owner-freebsd-current Wed Jun 5 9: 3:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 296D737B406 for ; Wed, 5 Jun 2002 09:03:18 -0700 (PDT) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.12.3/8.12.3) with ESMTP id g55G3HRs040316; Wed, 5 Jun 2002 09:03:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.12.3/8.12.3/Submit) id g55G3HBj040315; Wed, 5 Jun 2002 09:03:17 -0700 (PDT) Date: Wed, 5 Jun 2002 09:03:17 -0700 From: Steve Kargl To: Christopher Nehren Cc: current@FreeBSD.ORG Subject: Re: "Safe" to go to -CURRENT? Message-ID: <20020605090317.A40276@troutmask.apl.washington.edu> References: <1023266819.500.6.camel@prophecy.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1023266819.500.6.camel@prophecy.dyndns.org>; from apeiron@prophecy.dyndns.org on Wed, Jun 05, 2002 at 08:46:59AM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jun 05, 2002 at 08:46:59AM +0000, Christopher Nehren wrote: > I've been monitoring the -CURRENT mailing list for about a day or two, > and haven't seen anything that's really broken (except for GCC 3.x, > which I don't use anyway). So, is it "safe" to upgrade to -CURRENT yet? > TIA for the info, What do you do with the system? It is fairly difficult to make any recommendation without some info about what the system does. For example, is this a production box? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message