Learned folks... Can someone shed some light for me on finding which kernel module is loaded/providing the eth0 interface?
Scenario: I have a several virtual machines in a test/developement environment on a Microsoft HyperV (don't ask - just...don't!) server. One box (dev) is built on CentOS and has eth0 working fine. Developers and corporate standards demand that additional boxes for UAT be built on SLES Trouble is, the SLES install doesn't seem to auto-detect the NIC provided by the HyperV server. Can anyone suggest how I can use the CentOS server to find which module is laoded to provide eth0 so I can force-load it in the SLES server and make the virtual NIC work? To stave off the howls about the M$ abomination - I know it, it's only for development, UAT, and the production servers will be either proper VMWare or more likely physical boxes with decent Linux installations on them. :-) Cheers. DaZZa -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
