From owner-freebsd-current@FreeBSD.ORG Tue Feb 28 22:15:14 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 1D03F1065673; Tue, 28 Feb 2012 22:15:14 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id B9EFC163578; Tue, 28 Feb 2012 22:14:35 +0000 (UTC) Message-ID: <4F4D51CB.2010508@FreeBSD.org> Date: Tue, 28 Feb 2012 14:14:35 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Arnaud Lacombe References: <20120221143537.Horde.deyFDZjmRSRPQ52pxBIpnLA@webmail.leidinger.net> <4F4BA707.5070608@wasikowski.net> <4F4C3FE7.3040802@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, current@freebsd.org, Steve Wills , =?UTF-8?B?xYF1a2FzeiBXxIVzaWtvd3NraQ==?= , "Bjoern A. Zeeb" , Alexander Leidinger Subject: Re: [CFT] modular kernel config X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2012 22:15:14 -0000 On 2/28/2012 10:48 AM, Arnaud Lacombe wrote: > You will sure go really far with this kind of "It is broken ? Let's > not fix it and disable it instead" mentality, even more when coming > from a committer. > > As long as there will be these kind of comments around here, FreeBSD > will deserve nothing but to keep dying piece by piece, and it will be > deserved. In general, I tend to agree with you, but in this case it's useful to know the history of the flowtable option. 1. It was introduced in -current 2. It received fairly good testing, was pronounced good and useful, and MFC'ed. 3. Several releases happened with flowtable. 4. Users started to report problems that were ultimately tracked down to flowtable. 5. Ultimately it was decided that flowtable was not a universal good. 6. The developer of the option agreed that it should be disabled by default until such time as it can be fixed. 7. The fixing hasn't happened yet. While generally fixing things is the right solution, if the fix is complex (or worse, unknown AND complex) then disabling by default is a reasonable answer. Doug -- It's always a long day; 86400 doesn't fit into a short. Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/