[ale] Module handling at boot

[Joseph A Knapka]

Ken Nagorski wrote:
> 
> > If you have a module that needs to get loaded at boot time but you
> > forgot to include it when you ran menuconfig prior to compiling a
> > kernel, how do you fix it where it'll load at boot time?  In this case,
> >  it's the module for the NIC (RTL8139) and I assume (I haven't tried
> > it)  that if I booted it up and typed "insmod <module_name>" and then
> > "ifup  eth1" then my NIC would pop to life.  So I'm trying to make this
> > result  happen at boot time instead.
> >
> > - Jeff
> >
> >
> > ---
> > This message has been sent through the ALE general discussion list. See
> > http://www.ale.org/mailing-lists.shtml for more info. Problems should
> > be  sent to listmaster at ale dot org.
> 
> ----------------------------------------------
> But I don't want to go among mad people,
> Alice remarked.
> Oh, you can't help that, said the Cat:
> we're all mad here. I'm mad. You're mad.
> How do you know I'm mad? said Alice.
> You must be, said the Cat,
> or you wouldn't have come here.

While quoting Lewis Carrol at the machine would probably be
worth a try under Windows, we have more effective measures
available with Linux :-)

Depending on your distribution, there should be some
rc.* files somewhere under /etc. On Slackware, I'd
edit the file /etc/rc.d/rc.inet1, and add the appropriate
"modprobe" command for the network card to the top of
the file. I'm not sure how this works on Red Hat and
derivatives; I know their boot-script scheme is quite
different from Slack's though.

Cheers,

-- Joe
"I should like to close this book by sticking out any part of my neck
 which is not yet exposed, and making a few predictions about how the
 problem of quantum gravity will in the end be solved."
 --- Physicist Lee Smolin, "Three Roads to Quantum Gravity"

---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.