Pouring thru the MYRIAD scripts SuSe/Yast uses, the MAC seems to be gotten from the /sys files dynamically.
Even tried using YAST to hard set the IP stuff up again, but that made matters worse. Perhaps it time to rip all that crap out and but in a real network start up script from my Slackware box .... sigh .. Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS, 39212 "Never attribute to malice, that which can be adequately explained by stupidity" - Hanlon's Razor > -------- Original Message -------- > Subject: Re: Issues with persistence of Drivers > From: David Boyes <dbo...@sinenomine.net> > Date: Tue, July 03, 2012 9:34 am > To: LINUX-390@VM.MARIST.EDU > > > > I do see reference to /etc/sysconfig/network/ifcfg-*id-$LLADDR", but our > > > auto deploy scripts setup the etho as ifcfg-eth0 ... > > > > Compare the MAC addresses on the actual interfaces. System-network-config (if > this is RHEL) writes the MAC address of the device *at the time it's > configured* into the interface definition files. Those will have changed on > the new machine, and you'll see exactly this kind of behavior -- the > interface definition files look at the MAC address to determine what > interface data to use for a specific device. If nothing matches, no network. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
