Comment 3 for bug 659817
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I can confirm the issue, but I'm still working on getting things clarified as to how exactly we should handle /etc/hosts. It's starting to be clear that the changes should be "as little as possible" and "only if it's not already set by the admin", but this still causes issues where, like here I assume, NetworkManager is expected to handle *everything* in the network connection, including setting the proper FQDN for the current connection it possibly gets from DHCP.
Note that with this feature complete, you could get into weird issues/weird domain names in /etc/hosts when you log on to public wireless access points, for example.