Actually, I think Windows does the equivilant of this in user space. That is, it
internally numbers the devices as they appear just like Linux would, but then the
network code takes care of knowing which interface is supposed to have which
settings. So it's basically the same thing as this cool little hack.
Actually, I think Red Hat should fix their network scripts to do this. That is,
configure the card based on the MAC address and not the kernel number.
Very good idea.
-Dave
Jim Roland wrote:
> Thanks! That's exactly what I need. I just wish the kernel and init
> understood laptop docking and undocking like (no flames please) Winblows
> does. That's the only redeeming value to Winblows, IMHO.
>
> > The job of ifcfg-eth[01] is now to work out which card is being
> > accessed and to map the kernel identifier (eth[01]) to a user
> > identifier (eth-{docking,pcmcia}). This example ifcfg-eth0 script uses
> > MAC addresses, replace the sample MAC addresses with your own. If you
> > do not like using MAC to identify cards, find some other way to
> > identify which physical card is being configured. Replace both the
> > ifcfg-eth0 and ifcfg-eth1 files (make one a link to the other) with
> >
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Apr 15 2000 - 21:00:11 EST