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
Date: Tue, 30 Nov 2004 14:27:13 -0800 [thread overview]
Message-ID: <20041130222713.GA8501@linuxace.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0411302328450.3635@dragon.hygekrogen.localhost>
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
next prev parent reply other threads:[~2004-11-30 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 19:45 PROBLEM: misleading error message Bebel
2004-11-30 20:56 ` Misleading " Jan Engelhardt
2004-11-30 23:36 ` Greg KH
2004-11-30 21:58 ` PROBLEM: misleading " Jesper Juhl
2004-11-30 22:10 ` [RFC] " Jan Engelhardt
2004-11-30 22:29 ` Jesper Juhl
2004-11-30 22:27 ` Phil Oester [this message]
2004-11-30 22:29 ` Lee Revell
2004-11-30 22:30 ` Jan Engelhardt
2004-12-02 12:33 ` David Ford
2004-12-02 23:40 ` Ken Moffat
2004-12-03 10:35 ` Jan Engelhardt
2004-12-05 0:32 ` Horst von Brand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041130222713.GA8501@linuxace.com \
--to=kernel@linuxace.com \
--cc=jengelh@linux01.gwdg.de \
--cc=juhl-lkml@dif.dk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.