Les Mikesell wrote: > On Wed, Jan 15, 2014 at 6:05 AM, Steve Clark <sclark at netwolves.com> wrote: >> On 01/14/2014 08:34 PM, Les Mikesell wrote: >> >> On Tue, Jan 14, 2014 at 7:17 PM, Warren Young <warren at etr-usa.com> >> wrote: >> >> I don't know about "less consistent", but I always considered it a >> feature in Linux vs the BSDs or big iron Unix that I could always count >> on the first network interface being "eth0". >> >> What does 'first' mean? And the same one isn't consistently first. <snip> >> The problem is when you clone a disk and ship it to a location with >> 'hands-on' support that doesn't know linux to install in a new chassis >> that will arrive there at the same time. Somehow you have to get >> someone to put the 4 network cables in the right NICs before anything >> can connect. With things tied to MAC addresses that you don't know >> ahead of time, nothing will work. When you clone a disk, you can't get the ifcfg-eth* and 70-persistant-net-rules from the old machine, or you don't have that info under version control, with all those systems? <snip> > If you insert the card yourself, you obviously know the slot. And you > can tell the position from the back just by looking at it. But > Centos6 will detect in random order, so knowing the name on one box > doesn't help with another. We have to go through contortions > plugging on cable in at a time, doing an 'ifconfig up' and checking > which interface shows link up. And the people doing that part wish > we used more windows instead of Linux. ifconfig up? Not ethtool eth? mark