What are your unsatisfied NetworkManager use cases?

Tom Horsley tom.horsley at att.net
Wed Oct 22 19:13:01 UTC 2008


> So please reply with a use case that you have that is not covered, I
> will attempt to collect clarify and log them on the wiki (just
> reactivated my account).

The most persistent and obvious bug is the refusal of NetworkManager
to activate the network at boot time. Lots of services depend on
a network existing. Things like ntp (if you have step-tickers defined
to set the clock at service startup), dhcp which needs an active network
to know what interfaces to listen on, etc.

The NetworkManager developers seem to live in some alternate universe
where they attribute all these problems to bugs in everything else,
but not NetworkManager (since obviously NetworkManager is the perfection
of all creation :-).

The fact that everything worked perfectly with the old network service
doesn't strike them as any kind of regression. They've ascended past
the need for any kind of server system - all computers are obviously
laptops being dragged from one Starbucks to another.




More information about the fedora-list mailing list