From owner-freebsd-stable Tue Dec 17 07:29:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id HAA29298 for stable-outgoing; Tue, 17 Dec 1996 07:29:58 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id HAA29293 for ; Tue, 17 Dec 1996 07:29:55 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id IAA08893; Tue, 17 Dec 1996 08:29:47 -0700 (MST) Date: Tue, 17 Dec 1996 08:29:47 -0700 (MST) Message-Id: <199612171529.IAA08893@rocky.mt.sri.com> From: Nate Williams To: Marc Slemko Cc: Nate Williams , freebsd-stable@freebsd.org Subject: Re: why is -stable not secure? In-Reply-To: References: <199612170512.WAA07056@rocky.mt.sri.com> Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Fine. Provide the resources for someone to patch 2.1. > > Please elaborate on "resources". Do you not think it should be done in > the main CVS repository, or are you referring to the manpower required to > do the work? Manpower and/or incentives for manpower. In the past, I offered to integrate any/all changes to the -stable branch from the 'users', which include a large number of commercial folks who rely on FreeBSD for their business. I didn't receive *one* patch from anyone, and instead had to do all my own testing and such to bring in stability/security patches to stable that I felt were necessary. I thinks it's nice that everyone likes stable, but no-one was willing to do anything to keep it updated, so I withdrew my offer because of the obvious lack of interest in outside people doing work. I'm now focusing my energies on current. Nate