[Lunar-bugs] [Lunar Linux 0000405]: kernel module loading in new init system

[noreply at bugs.lunar-linux.org]

The following bug has been CLOSED
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000405
=======================================================================
Reporter:                   huysmans
Handler:                    huysmans
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000405
Category:                   initscripts (boot system)
Reproducibility:            N/A
Severity:                   feature
Priority:                   none
Status:                     closed
=======================================================================
Date Submitted:             2003-11-10 09:15 GMT
Last Modified:              2004-01-20 20:56 GMT
=======================================================================
Summary:                    kernel module loading in new init system
Description: 
The 'old' lunar init system had a modultils init script in /etc/rcS.d to
load all modules in /etc/modules. The new system has no such thing.

The rc.sysinit file does load several modules (usb) that may be required
for proper startup.

I'd like to hear other people's opinion on what to do here. I can think of
a few scenarios:

1. use the modutils script and put it in all runlevels, probably with a
very low number.

This doesn't entirely feel right, since kernel module loading is system
initialization to me.

2. call the script from or incorporate the script in rc.sysinit without
changing anything else.

This is a better solution than (1) IMO. rc.sysinit already contains code
to run /etc/rc.modules for backwards compatibility (with old redhat
versions I presume).

3. Put the module loading using /etc/modules in rc.sysinit and remove all
other module loading. 

This puts the reposibility for putting the modules required for startup in
/etc/modules in the hands of the user/admin. This is not necessarily a bad
thing. We can display a message after kernel compilation to remind the
user to update their /etc/modules if necessary.

What do you think?
=======================================================================

-----------------------------------------------------------------------
 jbrocklin - 2003-11-10 17:03 GMT 
-----------------------------------------------------------------------
I don't think that users will want to have to worry about adding the module
init stuff to /etc/modules - just seems like one more thing that will send
people running to #lunar or the ML when stuff doesn't work.  I'm not sure
what the best way to handle this issue is - 2 sounds like it will work,
until backwards compatibility is removed somewhere down the line.  Just my
thoughts...since it asked for feedback...

--Joe

edited on: 11-10 17:03

-----------------------------------------------------------------------
 huysmans - 2004-01-20 20:56 GMT 
-----------------------------------------------------------------------
It does support loading modules from /etc/modules now, just like current
tools.