[NTLUG:Discuss] can not bring up all eth* on boot time?

George E. Lass George.Lass at osc.com
Thu Mar 29 12:02:28 CST 2001


m m wrote:
> 
> >
> >Assuming that you will be using your network quite often,
> >I would re-build the kernel with your NIC drivers included
> >(not as modules as you are doing now.)  Once you do that,
> >the mods to lilo.conf should work.
> >
> I agree with you. I did do so and post my problem/question here is because I
> think since it has load modules capability (and it suppose work fine), why
> not just take this advantage?

AFAIK the only advantage of using modules is that they don't take up
space in the kernel image on disk, and don't take up memory unless they
are needed.  Since you are doing an insmod during startup, they *are*
taking up memory space, so unless your kernel disk image is too large
to boot with the drivers complied in , there is really no advantage to
using modiues for your ethernet drivers.  Besides, you can't get them
to work as modules anyway.....

> 
> >
> >As for IP forwarding, are you sure that you have that configured
> >into your kernel?
> 
> The box has RH default package/kernal installation.
> I think that should be configured in the kernel. am I right?

You should be able to determine this by doing:

ls -l /proc/sys/net/ipv4/ip_forward

if it is a zero length file then I'd guess forwarding is configured.
if it a 1 byte file then I'd guess it was created when you did echo 1 >
........

George

-- 
... Unix IS a user friendly O/S ...
(It's just picky about its friends)



More information about the Discuss mailing list