From owner-freebsd-stable Wed May 10 12:31: 2 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id ABA4437B8EA; Wed, 10 May 2000 12:30:55 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA00723; Wed, 10 May 2000 12:30:55 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 10 May 2000 12:30:54 -0700 (PDT) From: Kris Kennaway To: David Miller Cc: freebsd-stable@freebsd.org Subject: Re: Server Farms? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 10 May 2000, David Miller wrote: > I know this. That's why I use FreeBSD:) :-) > What I was asking for was an easy way to differentiate between kernel and > non-kernel changes. cvscommit-all is pretty high volume to look at daily > - I just want an easy way to tell when significant bugs which might affect > me get fixed. Changes under src/sys/ are the ones which affect the kernel (and those with "RELENG_[34]" are the only ones which affect [34].x) > I'm thinking of the way many commercial OS's release patches, like bsdi. Unfortunately FreeBSD doesnt do that - -stable is for this kind of thing. Basically the worst that is likely to happen with it is that you get a system that doesnt compile - serious breakages in stable are VERY rare, and I cant think of the last time one occurred. Perhaps the best thing to do might be to watch the -stable mailing list for signs that people have been experiencing trouble with a particular date, and if things are quiet, update to that date on your test machine, and if it works, do the rest. Kris ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message