Date: Tue, 30 Nov 2004 14:27:13 -0800
From: Phil Oester <kernel@linuxace.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] misleading error message
Message-ID: <20041130222713.GA8501@linuxace.com>
References: <001101c4d715$25a59470$af00a8c0@BEBEL> <Pine.LNX.4.61.0411302251180.3635@dragon.hygekrogen.localhost> <Pine.LNX.4.53.0411302310080.31695@yvahk01.tjqt.qr> <Pine.LNX.4.61.0411302328450.3635@dragon.hygekrogen.localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0411302328450.3635@dragon.hygekrogen.localhost>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1144
Lines: 29

On Tue, Nov 30, 2004 at 11:29:20PM +0100, Jesper Juhl wrote:
> On Tue, 30 Nov 2004, Jan Engelhardt wrote:
> 
> > >> This may be a BUG REPORT, as I see it, allthough more experienced Linux users
> > >> might think differently:
> > >>
> > >> I compiled built-in support for iptables in my new 2.6.9 kernel, but when my
> > >> legacy firewall does a "modprobe ip_tables" , I get the startling message:
> > >> "FATAL: module ip_tables not found" .
> > >
> > >In my oppinion the message is perfectly clear. You told modprobe to load a
> > >module, the file was not found so it is forced to give up - and that's
> > >exactely what it told you.
> > 
> > So how would you go about finding out whether something is compiled-in?
> > 
> Personally I'd just go check my kernels .config

Or adjust your (broken) firewall script to do something like:

[ -f /proc/net/ip_tables_names ] || modprobe ip_tables

Phil

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/