On Wed, 06 May 2009 09:26:13 -0700
Wolfgang S. Rupprecht wrote:
> BTW, this is the same catch-22 that one has for nfs-mounted home
> directories.
The whole problem was the presentation of NM as a "replacement"
for the old network stuff when in fact they have almost nothing
in common. The old network code was flawless with static
IPs and unchanging DHCP assigned network connections and just
absolutely dead horrible at wireless and portable computers
that hop around between networks.
The so-called replacement NM, is (by all accounts) finally wonderful
with wireless and wot-not, but in the process rendered fixed
and unchanging network addresses with perfectly valid reasons
to be activated at boot time completely broken. This is not
a replacement, it is something completely different that has
a tiny overlap because they both deal with networking in some way.
The problem was telling anaconda to always activate only NM.
Anaconda should have some radio buttons like:
o My primary network needs to be activated at boot and never changes
o My primary network changes all the time as I flit about from
one hotspot to another.
o I don't want to configure networking at this time.
Then it could setup either network or NM (or nothing) as the default.
Once upon a time anaconda did indeed ask you to make a choice, but
the question was something like:
Use NetworkManager to control your networking?
To which my reaction always was "What the $#@! is NetworkManager?"
Alternatively, they could really make NM be a viable replacement,
but they broke so many subtle little frills (like being utterly
incompatible with the old dhclient hook scripts), that I don't know
if NM could ever manage to be a useful replacement.
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
