Date: Tue, 30 Nov 2004 21:56:25 +0100 (MET)
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
cc: linux-kernel@vger.kernel.org
Subject: Re: Misleading error message
In-Reply-To: <001101c4d715$25a59470$af00a8c0@BEBEL>
Message-ID: <Pine.LNX.4.53.0411302151160.31175@yvahk01.tjqt.qr>
References: <001101c4d715$25a59470$af00a8c0@BEBEL>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
To: unlisted-recipients:; (no To-header on input)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1281
Lines: 45

>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" .
k

Linux Developers,

what would you think of say, a line added to modules' code that identifies
compiled-in components?
modprobe could then be adjusted to
1. try loading something.ko
2. looking for a component "something" within the compiled-in stuff

I'd imagine a module's init could look like:

int __init init_module(void) {
	...
	register_static_module("ip_tables");
	...
}

Or using some linker magic to generate a table/array full with strings to
indicate their presence. (I though of kstrtab, which is, to my knowledge, also
composed of multiple single symbols into one.)

Awaiting list feedback.


>A message like "Module ip_tables not needed; support already built in the
>kernel" would be much more helpfull, as I see it.

modprobe should just return 0 as is with the case for already-loaded modules.


Jan Engelhardt
-- 
ENOSPC
-
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/