[Resolvconf-devel] Bug#773749: Resolvconf vs wicd

[Thomas Hood]

On 14 January 2015 at 15:08, Vincent Lefevre <vincent at vinc17.net> wrote:
> On 2015-01-14 14:14:22 +0100, Thomas Hood wrote:
>> This is an allowed configuration (which is sometimes even useful). [...]
>
> OK, but this is a very atypical usage for users of wicd, whose goal
> is to make things work without needing to be root. So what about an
> option for /etc/default/resolvconf to force the link creation when
> using dhclient?


It's up to the admin to change things in /etc/. Programs that play
around with things in /etc/ at runtime are not well behaved by Debian
standards.


> Otherwise the user needs to modify
> /etc/dhcp/dhclient-enter-hooks.d/resolvconf to get this behavior.


Now I have the feeling I'm missing something. Is there some reason
that the symlink at /etc/resolv.conf has to be created at run time?
Why can't the administrator just do "ln -s /run/resolvconf/resolv.conf
/etc/resolv.conf" to restore the symlink?


>> When the resolvconf package is initially installed it optionally and
>> by default creates the symlink at /etc/resolv.conf,
>
> But the symlink got removed for some reason I ignore. I'm wondering
> whether wicd was the cause (with the code related to the backup file).


If so then there might be room for improvement in wicd or in its
maintainer scripts. Wicd should not touch a symlink at
/etc/resolv.conf.
-- 
Thomas