From mboxrd@z Thu Jan  1 00:00:00 1970
From: Xavier <xavier@reivax.org>
Subject: Re: hi
Date: Thu, 23 Jan 2003 19:05:40 +0100
Sender: linux-admin-owner@vger.kernel.org
Message-ID: <20030123180540.GB2500@reivax.org>
References: <8608421EC5CBD511B5090002A55C00480478E361@uswaumsx04medge.med.ge.com> <15918.60356.335204.681805@cerise.nosuchdomain.co.uk>
Mime-Version: 1.0
Return-path: <linux-admin-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <15918.60356.335204.681805@cerise.nosuchdomain.co.uk>
List-Id: <linux-admin.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-admin <linux-admin@vger.kernel.org>

On Wed, Jan 22, 2003 at 07:06:44PM +0000, Glynn Clements wrote:
> 
> Sadanapalli, Pradeep Kumar (MED, TCS) wrote:
> 
> (...)
> 
> If your module doesn't fit any known type, or you specifically want it
> to be loaded at boot rather than on demand, then the simplest solution
> is probably to just add a modprobe command to the rc.local script.
> 

Or add the name of the module to /etc/modules which should contain "the
names of kernel modules that are to be loaded at boot time" (at least in
debian - don't remember if this is debian specific, take a look at
your init.d modutils script to see if it reads modules names from this 
file)

Xavier