From: "Bebel" <bebel@braila.astral.ro>
To: <linux-kernel@vger.kernel.org>
Subject: PROBLEM: misleading error message
Date: Tue, 30 Nov 2004 21:45:24 +0200 [thread overview]
Message-ID: <001101c4d715$25a59470$af00a8c0@BEBEL> (raw)
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" .
Please note that I am a Linux newbie and I think messages should help people
solve problems, but this particular message made me re-compile the kernel 2
more times ( stupid, huh ?) before I realized that iptables actually works,
though the message had me thinking it wasn't :))
The message was probably caused by modprobe trying to load ip_tables module
and not finding it, since support for it was built in the kernel (not as a
module).
So I find this message quite misleading, firstly because the error was in no
way "FATAL" (since iptables in fact WORKED) and secondly because it doesn't
tell the user that iptables was already supported by the kernel.
A message like "Module ip_tables not needed; support already built in the
kernel" would be much more helpfull, as I see it.
If it matters, I'm running Slackware 10.0 on a 500MHz Pentium 3 with 256MB
RAM and a basic iptables firewall, on which I did a kernel upgrade from
2.4.26 to 2.6.9 .
But this problem is common to many distros, as I could see on several
forums.
Best regards, Wussie .
next reply other threads:[~2004-11-30 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 19:45 Bebel [this message]
2004-11-30 20:56 ` Misleading error message 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
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='001101c4d715$25a59470$af00a8c0@BEBEL' \
--to=bebel@braila.astral.ro \
--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.