Network Card Modules

[Slacker]

Hiya,

I was wondering if there is a reason you have opted to make the network drivers modules in the Debian kernel? Do you have one install that works on all the different types of servers you have; so the modules just make the kernel less bloated with code that won't get used? i.e. you have different ethernet cards in each type of machine you install it on.

ta,


Peter

[BlackNet]

Hello,

Generaly you want to make all your nic's as modules. that means great porability and flexibility. say you change nics and your looking at a new compile. with modular you just change the modules.conf file :)

Ed

[knightfoo]

We use the standard Debian kernel package (now), which builds just about everything as a module. Not only does it decrease the memory footprint of your kernel, but it does make it easier to install it on different hardware platforms. NIC modules are particularly bothersome because not all of the boards have the same NIC, so moving your drive to a different motherboard would entail a kernel rebuild if you weren't using modules.

Modules are also nice if you like to mess with experimental features that you don't want running in your kernel all the time, or may crash and need to be removed from the kernel to reset things.

-knightfoo

[Slacker]

:thanks:

[mcgroarty]

Originally posted by knightfoo
We use the standard Debian kernel package (now

One down, two to go!

If you'd do the standard thing and load the network module in /etc/modules instead of the pre-up line in /etc/network/interfaces, and if you'd make debs for webmin and the serverbeach ssh so people can cleanly uninstall those thorugh dpkg if they like, then you'd have something even the most anal retentive Debian folks could love. :)

[blackjudas]

Man this is the exact problem I'm having. The pre line in the interfaces file is causing me much pain ;).

I've had to reboot it twice now through a ticket :x.