From owner-freebsd-stable Wed May 10 6:12:27 2000 Delivered-To: freebsd-stable@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id E3D5B37B5C7; Wed, 10 May 2000 06:12:24 -0700 (PDT) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id F3B34DC01; Wed, 10 May 2000 09:07:28 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with ESMTP id E397CDC00; Wed, 10 May 2000 09:07:28 -0400 (EDT) Date: Wed, 10 May 2000 09:07:28 -0400 (EDT) From: David Miller To: Kris Kennaway 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 Tue, 9 May 2000, Kris Kennaway wrote: > On Tue, 9 May 2000, David Miller wrote: > > > related patches and secondly stability related changes. It would be > > really nice to seperate them into those which require relinking/rebooting > > and those which don't. > > Well, basically the only time you need to reboot a FreeBSD box is to > install a new kernel. I know this. That's why I use FreeBSD:) > Anything else can be fixed online, although it might be easier for some > things just to reboot and let it happen by magic. 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. I'm thinking of the way many commercial OS's release patches, like bsdi. For a server farm I don't want to: a) automatically track -stable because every once in a while it has a problem, and because some of the changes are to the kernel which requires relinking and booting. b) do nothing c) spend an hour every day watching the cvscommit-all mailing list to make a judgement on whether a patch affects me enough to warrant supping. Alternatives welcome:) --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message