vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I notice that kernel module autoloading takes place during the sysinit initialization stage. I have some kernel modules that I do not wish to load until a particular runlevel (in my case runlevel 3) is reached. Is there a way to achieve this or do I need to modify the startup scripts? Thanks in advance. Mark. -- Mark Hobley, 393 Quinton Road West, Quinton, BIRMINGHAM. B32 1QE. |
| |||
| Mark Hobley wrote: > I notice that kernel module autoloading takes place during the sysinit > initialization stage. I have some kernel modules that I do not wish to > load until a particular runlevel (in my case runlevel 3) is reached. Is > there a way to achieve this or do I need to modify the startup scripts? The only possibility I see is to add a startup script of your own, to be run as the last one, in which you use /modprobe/ or eventually /insmod/ to load the pertaining modules. Hope this helps... ;-) -- Aragorn (registered GNU/Linux user #223157) |
| ||||
| Aragorn wrote: > Mark Hobley wrote: > >> I notice that kernel module autoloading takes place during the sysinit >> initialization stage. I have some kernel modules that I do not wish to >> load until a particular runlevel (in my case runlevel 3) is reached. Is >> there a way to achieve this or do I need to modify the startup scripts? > > The only possibility I see is to add a startup script of your own, to be > run as the last one, in which you use /modprobe/ or eventually /insmod/ to > load the pertaining modules. This is what /etc/init.d/local is for. Just put the commands you need in /etc/conf.d/local.start and add local to the default runlevel (rc-update add local default). BTW, gentoo runlevels are best referred to using names, not numbers (default, boot, etc.). |