On Sat, 2001-10-06 at 10:48, dman wrote: > On Sat, Oct 06, 2001 at 11:00:22AM +0100, Matthew Sackman wrote: > | On Fri, Oct 05, 2001 at 08:11:08PM -0400, Wayne Topa wrote: > | > Matthew Sackman([EMAIL PROTECTED]) is reported to have said: > | > > Weird! Both of you that replied talk of putting eth0 in /etc/modutils/ > | > > > | > > I've never done that at all - I just put in /etc/network/interfaces, > | > > and it gets loaded and works. Do you really need it in aliases? > | > > If so why? > | > > > | > > | > Only if you compiled the NIC driver as a module. You probably have it > | > compiled into the kernel. I (we) assumed he had 'not' compiled it > | > into the kernel. My only excuse for that is that is how I do it and > | > he didn't say which method he used. :-( I assumed again, darn it. > > Yeah, I figured he had a pre-packaged kernel which includes everything > as modules so as to minimize the _need_ for recompiling. > > | It's a module. The natsemi module. It loads fine without there being > | anything relating to eth0 anywhere under /etc/modutils. > | > | Weird - I simply never knew this should be there. In fact, come to > | think of it, on all the boxes I've set up I've never put eth0 in there > | and I've never had a problem. > | > | Any ideas? > > Maybe the kernel is better at identifying the module automagically? > If you run 'lsmod' does it show the natsemi module?
Just a guess, but perhaps the module is listed in /etc/modules to load at run time on other machine, therefore not needing an alias in the aliases file. Putting it in the aliases file allows it to be autoloaded when the net is needed IIRC. --mike