[email protected] wrote: > > I am not sure about what problem you are trying to solve. Won't the > > lines added by resolvd be overwritten anyway the first time you use the > > backed up file? > > 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. > - 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? > For now resolv.conf is the only configuration file I know of that gets > mixed up with runtime info, and it's manageable; but imagine if many > more configuration files follow similar principles, the administrative > overhead can quickly become too much. Yes, we are going to do the same thing to lots of other configuration files. We are trying to keep up with systemd. Didn't you get the memo?
