On Sat, 2009-01-17 at 19:44 -0700, Craig White wrote:
On Sat, 2009-01-17 at 19:20 -0700, Christopher A. Williams wrote:
On Sat, 2009-01-17 at 16:10 -0500, Tom Horsley wrote:
On Sat, 17 Jan 2009 11:10:07 -0700 Christopher A. Williams wrote:
The only solution I have found so far is to:
- properly re-create /etc/resolv.conf to what it should be
- set the immutable flag on it (chattr +i /etc/resolv.conf)
That works in fedora, but even better (as others have said) is disabling NetworkManager service and enabling network instead (i.e. go back to the old and unimproved days :-).
I understand that. The entire point of this exercise was:
- Not to go back to the old ways
I think you have a misunderstanding of the role of both 'network' and 'NetworkManager' services.
'network' service is clearly better for server usage as it is a true startup daemon that doesn't require any user interaction.
'NetworkManager' at present provides for userland control which means that it isn't all that useful until a user logs in.
No misunderstanding here at all.
Indeed, this was the _original_ intent for NetworkManager. But according to several pieces of information posted here and elsewhere (such as the NetworkManager To Do page at http://live.gnome.org/NetworkManagerToDo), it is morphing into being more. It could very well replace the old network service in due time.
I know I could have done things using system-config-network and the network service. I chose not to for a very specific set of reasons.
-- ==================================== "If you get to thinkin' you're a person of some influence, try orderin' someone else's dog around."
--Cowboy Wisdom