On Thu, Oct 26, 2017 at 06:44:44AM -0400, Roberto C. Sánchez wrote:
On Wed, Oct 25, 2017 at 11:35:20PM -0400, Stefan Monnier wrote:> If Debian developers who are responsible for resolvconf are reading this, > and if they actually CARE about making things work correctly and sensibly, > then here is yet another proposal: give us a way to QUICKLY and EASILY > and RELIABLY tell resolvconf "never do anything". `resolvconf` only touches /etc/resolv.conf when it is installed/initialized. What it does to it is to replace it with a symlink. After that, it doesn't touch it any morel instead it only modifies the file that is the target of that symlink.Given that multiple packages potentially touch/change resolv.conf (at least resolvconf and the various DHCP clients), would be very useful is a directive that can be put inside of resolv.conf that informs all such packages that the file is not to be modified. That would allow the admin to avoid having to hunt down all the different packages and configure them individually to leave /etc/resolv.conf alone.
Actually, there's no need to duplicate the effort. As I understand it, resolvconf is basically an optional helper program. Software that automatically modifies /etc/resolv.conf should first test for the presence of resolvconf (whether that be checking for the configuration directory of resolvconf or checking that resolvconf is running or... however resolvconf desires to be detected). If resolvconf is available, the changes are co-ordinated through resolvconf, otherwise, /etc/resolv.conf is modified directly.
The problem is that I don't think that resolvconf can require packages to use it. This is similar to other higher-level APIs such as pulseaudio. If the software knows to use pulseaudio, then it can get mixed, rerouted etc by pulseaudio, but it's difficult to mandate that software stop sending audio directly to /dev/dsp (well, unless you're a distribution which applies patches to upstream software in order to harmonize the experience of its users).
Regards, -Roberto -- Roberto C. Sánchez
-- For more information, please reread.
Attachment:
signature.asc
Description: PGP signature