On Mon, Apr 09, 2012 at 12:44:42PM -0400, Lamar Owen wrote: > On Monday, April 09, 2012 12:31:39 PM Konstantin Olchanski wrote: > > On Mon, Apr 09, 2012 at 10:40:02AM -0400, Lamar Owen wrote: > > > > > > ... and the current NetworkManager doesn't handle many production server > > > networking tasks, > > > so upstream left the existing mechanism in place so choice is available. > > > > > > > No, they have not. In SL6, they have removed the old graphical > > system-config-network tool, > > so either use nm-connection-editor or vi. > > The 'existing mechanism' I refer to is the 'network' service and the older > ifcfg-ethX files. The assumption made in EL6 is that if you use a GUI you > will use NetworkManager.
That's right. Nm manager gui or vi. Our way or the highway. So you arrive to a remote location to fix broken network config and find that the mouse walked away, too, welcome to vi. As I say, people who come up with this stuff do not think beyound "it works on my laptop". > ... removed the HWADDR piece that binds to MAC address. Yes, obviously you want this for the unusual case where you have more than one network insterface and they all connect to different networks. For the more common case where there is only one network, the SL installer installs an unwelcome time bomb. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
