Bug 17163 – /etc/init.d/modules does not handle already loaded modules

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description nth 2003-03-09 13:51:53 UTC]

I'm using sys-apps/baselayout-1.8.6.3 and sys-apps/module-init-tools-0.9.10-r1 
 
  /etc/init.d/modules : 
 
    - should not report errors for /etc/modules.autoload* modules that have 
      been previously loaded (this shows an error at boot time but does not have 
      any further consequence, it just is not beautiful and not quite correct). 
 
    - does not support /etc/init.d/modules "restart" because it reports errors for 
      already loaded modules (i had to call "restart" for development purpose).

[Comment 1 nth 2003-03-09 13:53:06 UTC]

Created attachment 9175 [details, diff]
just use "modprobe -q" instead of "modprobe"


  This patch will modify /etc/init.d/modules.

[Comment 2 Martin Schlemmer (RETIRED) 2003-03-10 07:53:28 UTC]

I am fine with that, except for the fact that modprobe -q also do not biatch
if the driver is missing (this is for one from module-init-tools).  I am still
talking to Rusty in trying to get another switch/whatever going.

[Comment 3 nth 2003-03-10 11:33:48 UTC]

 
  /etc/init.d/modules is working anyway, it just reports errors that are not 
but its exit code is still ok ... 
 
  Ok, so it may be better to wait for a modified module-init-tools version and 
leave the bug opened :( 
 

[Comment 4 Martin Schlemmer (RETIRED) 2003-03-10 12:27:00 UTC]

Hey, don't worry about it .. it is needed.  Just that currently with -q it
will not show you if it failed, but that is my screwup.

[Comment 5 Martin Schlemmer (RETIRED) 2003-03-10 15:31:31 UTC]

Ok, module-init-tools-0.9.10-r3 should be ok.  Fixed /etc/init.d/modules
on CVS, thanks.