hotplug for network drivers

james.kingston_at_gmail.com
Date: 11/14/05 

Date: 14 Nov 2005 10:21:23 -0800

We have a snapshot image of FC2 that we use as the basis for testing
and deploying our software. This image is deployed in a number of
slightly different hardware platforms. Some use tulip network drivers,
some use e100, some use e1000. Ideally, I'd be able to yank the hard
drive from the dev team's tulip-box and put it in QA's e100 box, and be
able to slap it in a deployable e1000 before being sent to the field.
This process worked fine when I was moving a slackware image around.
It also works for all other hardware in the systems, or at least we
haven't found cause to edit modprobe.conf for anything other than
network drivers.

To this end, I have removed all hardware specific parts from ifcfg-eth*
(hardware models and mac addresses), disabled kudzu (the goal is that I
don't have to plug in a kbd/video when bringing up a system), and gone
into /etc/rc.d/init.d/network and comment out the 4 lines that disabled
hotplug during the network startup process:

87: # oldhotplug=`sysctl kernel.hotplug 2>/dev/null | \
88: # awk '{ print $3 }' 2>/dev/null`
89: # sysctl -w kernel.hotplug="/bin/true" > /dev/null 2>&1

152: # sysctl -w kernel.hotplug=$oldhotplug > /dev/null 2>&1

I've removed the alias eth* lines from /etc/modprobe.conf

Also, I've commented out the following from /etc/hotplug/net.agent:
    # Red Hat specific hack...
# if [ -f /etc/redhat-release ]; then
# # Don't do anything if the network is stopped
# if [ ! -f /var/lock/subsys/network ]; then
# exit 0
# fi
# fi

There has to be some other Fedoda/RH hack preventing network modules
from autoloading at boot time.

Also, how do I enable hotplug debugging? I've uncommented "DEBUG=yes;
export DEBUG" from /etc/hotplug/hotplug.functions and created
/var/log/hotplug, but I've seen nothing so far.

Relevant Pages

  • hotplug for network drivers
    ... and deploying our software. ... Some use tulip network drivers, ... It also works for all other hardware in the systems, ... There has to be some other Fedoda/RH hack preventing network modules ...
    (alt.os.linux.redhat)
  • Re: General
    ... Their goal is going to be to sell as much hardware as possible, ... It sounds to me like there is a problem with the ROM update for your ... stuff that interacts with network adapters on your PC. ...
    (microsoft.public.pocketpc.activesync)
  • Re: Your favorite 10 analog ICs
    ... > engineers were Ham radio guys and seemed to think that measuring 60 Hz ... nationwide buildout plan for Ricochet 2 -- they ran out of money. ... they spent way too much on network hardware. ...
    (sci.electronics.design)
  • Re: File Transfer conundrum
    ... A week later I would call them back and I would set up a schedule so in case of network issues I would have our hardware type there to look at the line to see what the issue was. ... The sysprog would think they were the expert and go off on their own and set up the JES2 parms or VTAM mode table. ... The "other" quite minor issue was the program that sent and received the the data was an IBM FDP. ...
    (bit.listserv.ibm-main)
  • Re: FC2 versus FC3 -- my own experiences
    ... >> (if not on a network) your ethernet card if you have one installed. ... or uses the wrong hardware drivers for your machine. ...
    (comp.os.linux)