Les Mikesell wrote:
> On Wed, Jan 15, 2014 at 8:48 AM, <m.roth@xxxxxxxxx> wrote:
>>
>>>> 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.
<snip>
>>> 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?
>
> You have to do both. Link won't come up until you ifconfig up the
> device - which of course is difficult when you don't know its name...
I don't think so - pretty sure I was just using ethtool eth? the other
week, to try to figure out the name of the port that I'd plugged the patch
cord into. I *know* that the ones with nothing in them weren't up (and
yes, obviously, I was at the console).
mark
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
