[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: eth0 or eth1



On Thu, 28 Jan 2010 17:29:54 -0500 (EST)
Stephen Powell <zlinuxman@wowway.com> wrote:

> On Thu, 28 Jan 2010 16:27:47 -0500, Celejar wrote:
> > No need to erase the whole file, or to shutdown / reboot (assuming the
> > relevant driver is built as a module). As I note here, just comment out
> > the relevant line, and then unload and reload the relevant kernel
> > module.
> 
> I figured there was probably a less disruptive way, but I knew that erase /
> reboot would work, assuming only one NIC.  But since we're on the subject,
> just what would the "relevant kernel module" be?  The device-specific
> driver for the NIC, such as xirc2ps_cs, for example?  Or a more general
> networking module?  What would be the exact procedure?  I'm guessing
> something like:
> 
> [edit rules file]
> ifdown eth1
> modprobe -r xirc2ps_cs
> modprobe xirc2ps_cs
> ifup eth0 [if needed]

I'm pretty sure this is right - I've done this sort of thing with my
wireless drivers (b43, ath5k).  The device nodes are created by the
chipset-specific drivers, so they're the ones relevant to the udev
system, IIUC.

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


Reply to: