Re: modprobe

[Ted Gervais <ve1drg av eastlink ca>]

On Monday 30 December 2002 08:03 am, Ted Gervais wrote:


I just fixed the problem.  I must have been a bit sleepy here.
What I did was to simply add the modprobe statements to the top of my script 
in /etc/init.d  and now when that script is called it first runs modprobe for 
those modules.  

Works real slick.  Possibly this might help others doing similar things..




> On Monday 30 December 2002 02:23 am, Yoink! wrote:
> > On Sun, 29 Dec 2002, Ted Gervais wrote:
> > > I have found that I need to run modprobe to get a couple of modules to
> > > come up and I have put these statements in my /etc/rc.d/rc.local file.
> > >
> > > While that works just fine in bringing up those modules the application
> > > that uses them, is brought up before these modules are called.
> > >
> > > My question is - how can I have those modules called earlier than
> > > through the ./rc.local file??
> >
> > Is modifying the application startup possible?
>
> Yes.  The start up of that application can be anywhere but right now I have
> it set up in a script in /etc/init.d  and I am able to start/stop it using
> chkconfig etc..  I would like to keep it that way.  But a way around the
> problem would be to stick the 'call' for the application, in the bottom of
> the /etc/rc.d/rc.local file.  Not very professional, but that will fix my
> problem.  However, I would like to stick  with the script if I can..
>
> > How about editing /etc/modules.conf? Look at the modules.conf manpage for
> > syntax.
>
> That was a thought too.  Can't find the syntax for these modules.  The two
> modules called are 'netrom and mkiss'.  Maybe someone out there might have
> a tip or two on the correct syntax for these modules..??

-- 
T.L.Gervais
Coldbrook, NS
Canada.