Comment 26 for bug 324233
Revision history for this message
| Kevin P. Fleming (k.p.fleming) wrote | #26 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I've been running with a patched version of nm-named-manager for a few months now; the patch just removes the ability for network-manager to directly write to /etc/resolv.conf completely, and it's been completely stable. Every single time I start up, resolvconf is still in use as expected.