>> Granted, it might be nice if resolvconf had an easier way to configure
>> a static setup, but as it is now packages that need to access
>> resolv.conf should do this through resolvconf if it is available, so
>> installing and configuring it *is* the right way to handle this.
> I must argue against it, until as you say, resolvconf is given a well
> documented way to be told to leave a "static" system alone.
Why would that be a requirement? As this thread shows, the problem of
resolv.conf being modified occurs without resolvconf: it's not caused by
resolvconf, but rather by its lack.
Stefan
