From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750797AbWDIRKf (ORCPT ); Sun, 9 Apr 2006 13:10:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750810AbWDIRKf (ORCPT ); Sun, 9 Apr 2006 13:10:35 -0400 Received: from herkules.vianova.fi ([194.100.28.129]:18323 "HELO mail.vianova.fi") by vger.kernel.org with SMTP id S1750797AbWDIRKe (ORCPT ); Sun, 9 Apr 2006 13:10:34 -0400 Date: Sun, 9 Apr 2006 20:10:28 +0300 From: Ville Herva To: Nix Cc: Patrick McHardy , linux-kernel@vger.kernel.org, netfilter@lists.netfilter.org Subject: Re: Linux 2.6.17-rc1: /sbin/iptables does not find kernel netfilter Message-ID: <20060409171028.GC15954@vianova.fi> Reply-To: vherva@vianova.fi References: <20060408200915.GN1686@vianova.fi> <44388908.6070602@trash.net> <20060409074313.GZ15954@vianova.fi> <20060409144416.GO1686@vianova.fi> <20060409144534.GN29797@vianova.fi> <87psjqg2nt.fsf@hades.wkstn.nix> <4439385B.6010908@trash.net> <87hd52g065.fsf@hades.wkstn.nix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87hd52g065.fsf@hades.wkstn.nix> X-Operating-System: Linux herkules.vianova.fi 2.4.32-rc1 User-Agent: Mutt/1.5.10i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 09, 2006 at 05:53:54PM +0100, you [Nix] wrote: > On Sun, 09 Apr 2006, Patrick McHardy murmured woefully: > >> I cetainly did. A simple `make oldconfig' ends up zapping pretty much > >> all the old iptables CONFIG_ options, so you end up with not much of > >> iptables or netfilter left. > > > > But it does show you all the new options. Admittedly, it would > > have been better to automatically select the new options when > > needed, but probably not worth changing it now, it has been > > like this for two releases I think. > > Oh, yes, it did, and I thought they were userspace-matching related and > left them off. The real problem is that oldconfig doesn't mention when > options you *had* enabled disappear. Likewise for me. Perhaps iptables could point to a document or a webpage (in case kernel is newer than the userspace iptables, and has introduced new requirements) that lists the kernel options that need to be enabled, instead of saying failed iptables v1.3.5: can't initialize iptables table filter: iptables who? (do you need to insmod?) Such verbosity might not be unixy, but during Old Unix times, thousands of people weren't following -rc kernels... -- v -- v@iki.fi