From owner-freebsd-stable Fri Mar 13 13:05:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11348 for freebsd-stable-outgoing; Fri, 13 Mar 1998 13:05:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vs1.virtualisys.com ([207.137.172.173]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11294 for ; Fri, 13 Mar 1998 13:04:48 -0800 (PST) (envelope-from randyk@ccsales.com) Received: from ntrkcasa (pool46.hiper.net [207.137.172.46]) by vs1.virtualisys.com (8.8.8/8.8.8) with SMTP id NAA27041; Fri, 13 Mar 1998 13:03:50 -0800 (PST) Message-Id: <3.0.5.32.19980313130418.0360a100@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 13 Mar 1998 13:04:18 -0800 To: "Pedro F. Giffuni" From: "Randy A. Katz" Subject: Re: What is 2.2.6-BETA Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <3506E761.41C67EA6@asme.org> References: <3.0.5.32.19980311101007.0334f570@ccsales.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk Hello Pedro, Thanx. So if I want to keep stable what do I do:::? 1. Load the RELEASE and then patches? 2. Is there a straight forward, automated way of doing this? What I'm trying to do is to keep PRODUCTION servers up to date in terms of the binaries and security issues (LAND, F00F, etc...)... ...any suggestions? At 02:34 PM 3/11/98 -0500, you wrote: >It means that 2.2.6 will come out soon and we want this version tested >to the limit. Since the new release is not out yet, there is no >announcement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message