[Bug 668153] Review Request: openresolv - Management framework for resolv.conf

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=668153

--- Comment #3 from Dan Williams <dcbw at redhat.com> 2011-01-11 14:22:22 EST ---
Second, the fact that all resolvconf implementations use the network interface
names as an ordering and tracking mechanism is completely wrong, since what you
want to do for priority here has nothing to do with the interface name, and
everything to do with the network you're connecting to, which is independent of
the interface name that's connecting to that network.  Plus interface names can
be anything.  Essentially, using a resolvconf framework does not play well with
an actual dynamic system.

Third, resolvconf simply cannot handle bad ordering, if a program crashes or
otherwise does not remove its configuration.

So I'm kind of curious what the motivations for this are, and what problems a
resolvconf implementation would actually solve?

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.