From owner-freebsd-security Fri Aug 10 12:39: 4 2001 Delivered-To: freebsd-security@freebsd.org Received: from w2xo.pgh.pa.us (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by hub.freebsd.org (Postfix) with ESMTP id 462D137B403 for ; Fri, 10 Aug 2001 12:39:00 -0700 (PDT) (envelope-from durham@w2xo.pgh.pa.us) Received: from localhost (localhost [127.0.0.1]) by w2xo.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f7AJtIm95409; Fri, 10 Aug 2001 15:55:19 -0400 (EDT) (envelope-from durham@w2xo.pgh.pa.us) Date: Fri, 10 Aug 2001 15:55:18 -0400 (EDT) From: Jim Durham To: alexus Cc: erb , Josef Karthauser , Nuno Teixeira , freebsd-security@FreeBSD.ORG Subject: Re: RELEASE 4.3 -> RELENG_4_3: SUCCESSFULLY but ... In-Reply-To: <002501c1214d$07a5cf70$0100a8c0@alexus> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 9 Aug 2001, alexus wrote: > i'm more or less newbie here > > can you explain me why would you ever want to > > do cvsup+rebuild kernel every friday? what's wrong with your old kernel? > The tag "RELENG_4_3" means that cvsup only incorporates security fixes to the kernel. This is meant for "production servers", where you want to fool around with things the least amount possible. "If it ain't broke, don't fix it" . 8-) . This is about the only way to keep up with security fixes properly. There's a new exploit happening all the time. Actually, I watch this list for advisories and then do a cvsup. I don't do it on a schedule, but others do. As I said, I'm leery of updating a system running multi-user. I'm too old for the adrelelin rush -Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message