[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Hi folks,I've come across an interesting and rather frustrating 'feature' or maybe bug in CentOS and I wondered if anyone else had seen it?
Basically I'm trying to install CentOS 6.5 in a VM on Xen. It seems to install via a text install (not a major issue, Debian seems to do okay with this) and then merrily reboots.
However, when it does reboot it doesn't enable eth0. Running ifup eth0 does enable the Ethernet interface and all is well, or so I thought. On the next boot it decides to not enable it again. After some Googling I found this on the CentOS FAQ (http://wiki.centos.org/FAQ/CentOS6#head-b67e85d98f0e9f1b599358105c551632c6ff7c90):
<quote> Why does my Ethernet not work unless I log in and explicitly enable it?. and why are the interface names all "messed up" compared to prior practice? This violates the Unix rule of "not breaking expectations".
Upstream has changed the default configuration to use NetworkManager and interfaces are (somewhat inexplicably in the case of Ethernet) not enabled by default. This can be worked around at install time where, after the installer asks for your language and keyboard and Basic or other storage devices, it runs "Examining Devices" then it presents a screen "Please name this computer..." On this screen is a button labeled "Configure Networking". Clicking that button will launch NetworkManager. Select the Ethernet connection which is probably listed as "System eth0" and edit the settings. If you select the check box by "Connect Automatically" networking will start on boot in the future. You can also make this change with NetworkManager (System; Preferences; Network Connections or right click on the little network icon in the notification area and Edit Connections...) after the installation is complete.
</quote>I don't know if it's just me being old fashioned, but this just seems downright stupid. The text install didn't give me the option to do what it suggests in setup (guess it must be on the GUI install).
Suffice to say when I read the words "Network Manager" I cringed, that's another thing I can't stand and try and burn with fire on any servers I have (it's caused me enough hassle on Ubuntu/Linux Mint running it's own copy of DNSMasq and pointing to OpenDNS with their annoying DNS hijacking and adverts).
/me goes to calm happy place...Anyway, so after changing the config file it now works on boot, although it's give me yet another reason why I prefer Debian based distros. Guess it's just what I'm used to, I'm sure there are probably Debian ways of doing things that make RedHat/CentOS sysadmins tear their hair out.... and it could be worse, it could be Windows Server 2012 R2 with it's god awful TIFKAM... seriously... why would they do that, sure screw with the users on the desktop, but on the server too? And why no 2012 R2 server tools on Windows 7???... we're not all Powershell experts!).
TL;DR - I much prefer the Debian way of doing things and find Windows Server 2012 R2's interface more than a little frustrating.
Anyone else come across this in CentOS? Rob -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq