Mike Pfleger wrote:
> This "interfaces" file doesn't call modules on bootup, does it?
Correct.It it used to give the network settings after you have the
module.
Asd I noted on the page,for modules I use modconf .
> grabbed your file, and modified mine accordingly, to no avail. I looked
> at /etc/init.d/networking and there is the dreaded ifup call, used to
> check the viability of (I'm assuming) eth0.
> If interfaces is indeed
> used to insmod the module tulip.o (via its alias of eth0), is the fact
> that pci-scan.o is not aliased and called the problem? How does one
> alias pci-scan? What is it aliased to? Not eth0, I'd imagine.
Wrong assumption here.interfaces file is used to give the settings for
specific interfaces :-) .Now to have those interfaces you need certain
modules(drivers) .They are not related to each other in the way the
windows does .e.g. I can specify settings for any number of interfaces
which doesn't mean I do have them.yes it's a bit confusing compared to
windows where you can't give settings unless you have an interface.
Now the modules are beeing delt with in a separate way .As previously
said I use modconf(just type modconf as root) which is a
graphical(ncurses) console tool very intuitive IMHO.
If you want to go the hard way then take a look at /etc/modutils/
and read the man page for update-modules .
> Thanks in advance.
> Mike
>
--
The best way to escape from a problem is to solve it.
Alan Saporta
My waste of cyberspace=
http://deepblue.dyndns.org :-)
_______________________________________________
Stormlinux-users-list mailing list
[EMAIL PROTECTED]
http://www.stormix.com/community/lists/listinfo/stormlinux-users-list
