loading modules under 2.6.x

[John G. Heim]

Your   "mystartup"  concept is fine. I mean, not only does it work but it's 
not considered flakey or non-standard.

But there is a more elegant way to load a module. All you need to do is put 
it in /etc/modules. If you cat /etc/modules it will tell you how.

I would have a "mystartup"  script like yours and implement it theway you 
did it but not for loading a module. In mine, I configure iptables, for 
example.  A line in it is:

iptables-restore /etc/firewall.rules




At 01:37 PM 12/29/2005, you wrote:
>Greg,
>
>When I first switched to Debian I really missed not having an rc.local
>to put stuff like that in. So I created one. I called mine something
>like "mystartup" and placed it in /etc/init.d, then ran the command
>"update-rc.d" to create the symbolic links to execute it on entry to the
>desired run levels, using a high priority number such as 99 for
>instance.
>
>Maybe there's a more elegant way. Maybe someone will tell us.
>
>Chuck
>
>--
>The Moon is Waning Crescent (2% of Full)
>But you can still get downloads from http://www.mhcable.com/~chuckh
>
>_______________________________________________
>Speakup mailing list
>Speakup at braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

--
John G. Heim
jheim at math.wisc.edu
3-4189