Fighting with the accursed NetworkManager
Not content with rewriting my /etc/hosts file so that my PCs FQDN is set to 127.0.0.1, it is also now setting the hostname to "localhost.localdomain". (This is with a wired eth0 port, for a PC that belongs to a local network connected to the Internet via a router.)
Does anyone know how to configure NetworkManager so that it stops messing around with settings that are none of its business, please? Short of uninstalling the **** thing, of course, although that is starting to sound like a very good idea.
Check out wicd, well worth it. I like it alot better than NetworkManager
Originally Posted by chrisr
edit: Heres a link to the sourceforge page.
Seconded. I keep hearing networkmanager has improved since the days it was just broken, but here it doesn't work as cleanly as wicd. Maybe it's the KDE version that sucks (I still don't get the difference between plasma-netkwork-manager and kde-network-manager). For what is worth, now there's also wicd-qt (or something) which supposedly integrates better into KDE, but alas it doesn't work : D The regular version works fine everywhere.
Originally Posted by duby229
I have wicd installed on ArchBang and it works flawlessly. Yes NetworkManager sucks and I prefer wicd as it puts me in control of my network connections and gets out of the way.
Originally Posted by evolution
Wake me up when wicd supports tethering, bluetooth, and other 3G networking support. As well as ad-hoc networking, temporary wireless access point, etc.
Originally Posted by DeepDayze
Network-manager-dispatcher FTW, btw, if your dealing with custom networking setups and VMs.
Network Manager does not control your hostname, btw. Not by default anyways.
What sort of horror of a operating system are you using that does not have it correctly setup for you to use right off the bat?
I'm not going to argue with you. Please just go read the entry in RedHat's bugzilla:
Originally Posted by drag