I'd like to point out i didn't write the script :-)
modprobe does seem a better idea.
On Mon, 23 Jun 2003
21:03:11+1200 Christopher Sawtell <[EMAIL PROTECTED]> wrote:
> On Mon, 23 Jun 2003 20:30, you wrote:
> > On Mon, Jun 23, 2003 at 05:42:44PM +1200, Nick Rout wrote:
> > > [start]
> > > for x in /lib/modules/*/kernel/drivers/net/*
> > > do
> > > y=${x##*/}
> > > y=${y%%.*}
> > > echo -ne " ${GOOD}*${NORMAL} Scanning for
> > > ${y}..." insmod -f ${x} > /dev/null 2>&1
> > > backup
> > > done
> > > [end]
> > >
> > > the uncertainty in my mind being that the e100.o driver is in a
> > > subdirectory of /lib/modules/*/kernel/drivers/net/*
> >
> > It won't load it successfully. You'd need to alter the for loop to
> > recursively walk the directory structure. Something like:
> >
> > for x in $(find /lib/modules/*/kernel/drivers/net/*)
> perhaps it might be better to say
> for x in $(find /lib/modules/`uname -r`/kernel/drivers/net/
> -type f)
>
> because you do not really want to try to install a directory as if it
> is a module.
>
> > I'm not sure how safe/sane it is to load every module you find, and
> > then to force load (i.e. insmod -f) it.
> I'd agree with those sentiments, perhaps it might be better to
> modprobe the module?
>
> --
> C. S.
>
>
--
