BOUNCE rtl@rtlinux.org: Approval required: (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Sat Jun 23 02:17:52 2001
Received: from kanga.hofr.at (N735P031.adsl.highway.telekom.at [62.47.35.223])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f5N8Hpe22721
	for <rtl@rtlinux.org>; Sat, 23 Jun 2001 02:17:51 -0600
Received: (from hofrat@localhost)
	by kanga.hofr.at (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) id f5N8Bqt13124
	for rtl@rtlinux.org; Sat, 23 Jun 2001 10:11:52 +0200
From: Der Herr Hofrat <der.herr@hofr.at>
Message-Id: <200106230811.f5N8Bqt13124@kanga.hofr.at>
Subject: Re: starting kernel modules under RTLinux
To: rtl@rtlinux.org
Date: Sat, 23 Jun 2001 10:11:51 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL60 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> 
> In a RTLinux-based program I've written, I load a real-time kernel module:
> 
>     system("rtlinux start mymod.o");

insmod NAME.o only looks in ./ !

> 
> In order to allow access to this program anywhere on the system, I put the
> calling program and the kernel module in a directory that's listed in my $PATH.
> However, I've discovered that the kernel module won't load unless I run the
> calling program in the directory that the kernel module is found.
> 
> How can I have my real-time app accessible everywhere?
>

simply put them in the system wide modules location in 
/lib/modules/KERNEL_VERSION/misc/ and run depmod -a as
root. Most setups also allow to use the default location
/lib/modules/misc for such modules - but then its naturally
up to you to make shure that the kernel version is corect.

basically insmod checks the /lib/modules/`uname -r`/modules.dep to find
where the module is located, that is if you do insmod MODULE_NAME without
the .o extension - if you use the .o extension then it will accept the 
absolute path or take ./ by default.

hofrat 

----- End of forwarded message from owner-rtl@fsmlabs.com -----