network manager has gone crazy

[lee]

Tim <ignored_mailbox at yahoo.com.au> writes:

> Tim:
>> > If using Gnome, there's a desktop taskbar icon for NetworkManager, it
>> > lets you pick a network out of a list of available networks (if there
>> > are several to choose from), and there's an edit connections menu item
>> > to customise particular choices.  They could be fully automatic (the
>> > client is remotely set by a DHCP server), or you can choose to allow
>> > some things to be set by a DHCP server, other things to be manually set,
>> > or everything manually set.
>
> lee:
>> I'm not using gnome.  These so-called desktop-environments aren't doing
>> anything for me but getting in the way.
>
> Well, what are you using?  Command line, a light weight GUI, something
> else?  Letting us know will help you get better replies.

I'm running an X-session started with 'startx' and either fvwm or i3 as
window manager.

> There does appear to be some NetworkManager interface through the
> command line.  Dunno whether it's going to be of any use to you, though.

Hm I didn't find out what it is yet.

> As may have been pointed out in this thread, but definitely in the past,
> NetworkManager is probably not be suitable for servers.  It is geared
> towards having something else configure your network, usually a server
> is self-configured, or at least the central server is (the one
> everything else relies on).

It's a very strange idea that something else should configure the
network.

Anyway, I still want to know, even with networkmanager disabled.  It
doesn't hurt to learn something new :)

> I have to admit I'm intrigued to find out what would happen if you ran a
> DHCP server on a machine with NetworkManager handling the network
> interfaces.  But not sufficiently to try it out, at 2:30 in the morning.

It probably won't work because there won't be any network interfaces
configured the DHCP server could use to receive broadcasts and send
answers so that networkmanager could configure such interfaces.

> Regarding trying to find its configuration files, I would have tried
> something like:  locate -i networkmanager |grep etc

Of course I used tab comletion in the shell for /etc/network at first,
and that doesn't show up anything about networkmanager.  Like I said
before, it's just braindead to name it /etc/NetworkManager rather than
/etc/networkmanager.

I don't use 'locate' a lot because it's hard to say what it can possibly
find --- I made that experience a long time ago.  I did use find, and
I'd never have thought that someone would use capital letters when
naming the files.  I can't help it, I always underestimate peoples
stupidity.


-- 
Fedora 17