Subject: Re: force insmod on 2.6
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Leisner, Martin" <Martin.Leisner@xerox.com>
Cc: linux-kernel@vger.kernel.org, leisner@rochester.rr.com
In-Reply-To: <556445368AFA1C438794ABDA8901891C034456F2@usa0300ms03.na.xerox.net>
References: <556445368AFA1C438794ABDA8901891C034456F2@usa0300ms03.na.xerox.net>
Content-Type: text/plain
Date: Sat, 10 Feb 2007 21:18:30 +1100
Message-Id: <1171102710.15356.26.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1075
Lines: 30

On Fri, 2007-02-09 at 12:27 -0500, Leisner, Martin wrote:
> I had modules which were compiled with another kernel version string
> (same kernel though).
> 
> In 2.4, you could do a force in the modules.conf files or in the insmod
> command line.
> 
> The current insmod doesn't have a force option.
> 
> Modprobe CAN force, but the modules has to be in the modules tree (i.e.
> not arbitrary places on the 
> file system)
> 
> Is there a way to force load a module at an arbitrary location?
> 
> This is very handy for development (not production).

Sure, you simply remove the information from the module, then the kernel
will load it.  To strip modversions, remove the __versions section.  To
strip the version magic, it's easiest to remove the entire .modinfo
section.  You can use objcopy for this...

Hope that helps!
Rusty.

-
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/