On Thu, Oct 20, 2011 at 08:53:16PM +0000, sophia.ort...@googlemail.com wrote: > Rogier Krieger <rkrie...@gmail.com> wrote: > > > you can use the 'script' parameter described in dhclient.conf > > Perhaps the best solution, not far from what I had in mind from > the beginning, but not a simple configuration for a simple task. > > > I do not see why you prefer editing resolv.conf over dhclient.conf, > > though, but I trust you have your reasons. > > I find the idea of bringing dhclient with tricks to write a > configuration file that I can type myself absurd. I didnt manage to > avoid that dhclient write a "search" option in resolv.conf.
If you are using dhclient, then /etc/resolv.conf is not really a configuration file. You are choosing to have your host dynamically configured by an outside agency and /etc/resolv.conf becomes a tool to implement that dynamic configuration. So, to me, the logical approach is to control the dynamic configuration process to produce the result you want, not artificially contrain the implementation mechanism available to the dynamic configuration you receive. Neither approach is perfect. .... Ken > > ?ukasz Czarniecki <l...@sanki.roteh.pl> wrote: > > > chflags uchg /etc/resolv.conf > > Thanks! But that sounds like brute force. :) > > Do you know why opaque flag disappeared in OpenBSD? I think it > can be usefull under circumstances. > > Regards > SO
