On Wed, 2004-11-03 at 11:07 +0000, Timothy Murphy wrote: > On Wednesday 03 November 2004 05:42, Jason 'vanRijn' Kasper wrote: > Does this mean that system-config-network > and the entries to that in System Settings=>Network > and System Tools=>Network Device Control > are to go? I don't think so, not in the short term. NM is really only useful when you're using wireless connections, and not many servers that I know of do that :) These tools still have a use. > These applications don't work for me either; > but they seem nearer to what I want than NetworkManager, > which sounds much too clever for my purposes. What _do_ you want? Do you wish to manually bring/down your devices and manually set the ESSID and WEP key for every access point? That's basically what NM already does for you, it just needs a bit of settling down to deal with stuff like Open System/Shared Key. > Also, isn't there a convention to use lower-case in application names? Maybe in old-skool Linux land, but certainly not everywhere else. Other upstream Gnome projects, for example, like GConf, ORBit, etc have studly caps names. Besides, it doesn't kill people to reach for the shift key. Futhermore, who is _not_ using autocompletion in their shell? Even further, _why_ do you have to every type NetworkManager? Its installed as a server, and NMI should start automatically when you log in. Developers who don't want to type N once a month are plain lazy, no ifsandsbutsorors. Nobody has ever had a compelling reason to _not_ use studly caps besides "wahhh, I don't want to have to use shift, even though I use caps for other stuff in C." Dan