What I'm trying to solve is that static part of the configuration being mixed up with configuration generated runtime in a single file, which leads to a few inconveniences: - resolv.conf will show up in the diff between backups all the time even if nothing has really changed;Oh come on. Something happened. That is why the contents are different.
Yes something happened, but something which I imagine is not typically worth being backed up, yet it lives in the same file as things that are.
- when migrating the configuration to a different deployment, for example, one where IP address is statically assigned, resolvd will not overwrite the "stale" auto-configured lines, and the old nameserver info will linger unless manually removed.So what?
In cases where one doesn't want reveal what nameserver their other machines were using, a bit more error-prone I guess. I just don't see the reasoning behind removing resolv.conf.tail...
