No. Such warnings would:
1) not be seen, since they would show on the terminal, which is typically
hidden during upgrades.
2) need to be a debconf dialog to be seen, but debconf should be used to ask
questions, not show warnings
3) we're past freeze.
Broken images, while they are very annoying
Yes, I had a debconf dialog in mind, but I didn't know what Ubuntu's
policies are for such warnings.
I accept your arguments. Thanks for considering the proposal.
I don't think that NM should write to /etc/resolv.conf if the standard
symlink isn't there. That *would* be the kind of disrespect
Hi Mathieu,
I haven't explained well enough.
You are right, NM doesn't handle /etc/resolv.conf differently in
Quantal. What has changed is the IP address that nm-dnsmasq listens on.
This change *will* have an impact on some machines. A machine that has
no file at /etc/resolv.conf, or an empty
This shouldn't be done in a postinst (because the state can change after
NM is installed), and is resolvconf's job to handle.
We can try to play nice and avoid trampling settings if /etc/resolv.conf
isn't a symlink though. Didn't we already discuss this and apply such a
patch? :)
** Changed in:
Hi Mathieu,
The idea is to do it when the new network-manager installed which
listens at 127.01.1 instead of at 127.0.0.1. The old NM worked with an
empty or absent /etc/resolv.conf; the new one doesn't.
Yes, it is resolvconf's job to do take care of /etc/resolv.conf, but the
sudden
I still don't follow. There were no significant changes to how NM
handles /etc/resolv.conf from the version in 12.04 to the version in
12.10; and certainly nothing that would cause things to be handled
differently if /etc/resolv.conf is not a symlink or is absent.
The IP address change has no
