[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: How boot scripts?



On Tue, May 01, 2001 at 05:55:47PM +0100, David Wright wrote:
> Quoting V.Suresh (oizuamuqs@yahoo.com):
> > The module is for my modem, and if I put it in /etc/modules, will it be
> > loaded, since it needs '-f' for kernel version mismatch. Will that
> > be done during boot up, if I put it in /etc/modules?
> 
> No. /etc/init.d/modutils does not use the -f flag.
> 
> AFAICT (not having had to do this), you can add something like
> (i.e. one of) the following to your /etc/modutils/local file
> (create it if it doesn't exist):
> 

Good point. By the way, looking at /etc/modutils/serial, there is an example:

post-install serial /etc/init.d/setserial modload > /dev/null 2>/dev/null

Since post-install and install seems to have the same syntax, I will vote
for (Never done it through): 

install modulename insmod -f modulename

One needs to run update-modules before this gets converted to
/etc/modules.conf

> Writing scripts is just fine for something that Debian doesn't cater for,
> but you are making work for yourself by not playing the Debian way.
 
I agree.  Adding quick fix sometimes looks easier but will hurt us when
upgrading.  Reading /etc/init.d/modules should have answered all the
question original poster raised:-) init.d scripts are MUST read for
these issues.

Now I know what happens during boot process for modules :-)
-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ 
+  Osamu Aoki <debian@aokiconsulting.com>, GnuPG-key: 1024D/D5DE453D  +
+  My debian quick-reference, http://www.aokiconsulting.com/quick/    +



Reply to: