@Solomon: Linode tech support has told me that Linode intentionally
removed the /etc/resolv.conf symlink. By default, all of their
distribution templates use DHCP to obtain the IPv4 address on the first
boot; dhclient is configured to write out a valid resolv.conf file at
/etc/resolv.conf. That's it.
Was the only problem you had the fact that you got an error message? If
so then the problem is only the word "Error" which should have been
"Warning"; and this problem has already been fixed in Quantal.
In more detail: In Precise, /sbin/resolvconf aborted with an error
message
resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing
anything.
if /etc/resolv.conf was not a symlink. In Quantal /sbin/resolvconf
doesn't print that message and does not abort. However, unless you set
REPORT_ABSENT_SYMLINK=no
in /etc/default/resolvconf, the warning message
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a
symbolic link to /run/resolvconf/resolv.conf
gets printed by the resolvconf update script
/etc/resolvconf/update.d/libc. So an admin who wants to eliminate the
/etc/resolv.conf symlink and keep resolvconf installed will also have to
set REPORT_ABSENT_SYMLINK=no in order to silence the unwanted warning
message.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000244
Title:
/etc/resolv.conf symlink does not exist after initial installation of
resolvconf package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1000244/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
