[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#266817: replies



>   (1) Are there any packages that provide resolvconf functionality?


I don't think so.


>   (2) This problem should be occured on other distributions.  Do you
>       know how to manage them?


Other distros that I have tried have very poor support for mobile
computing.  They don't have anything like resolvconf.


>   (3) If PPP package restarts /etc/resolv.conf after rewriting them,
>       the problem should be gone.


The ppp package does not restart nscd after it changes resolv.conf.  In
any case, the ppp package only handles ppp interfaces, not eth
interfaces, etc.  Nameserver addresses can be obtained via DHCP as well
as via PPP.


>       Why should nscd suggest only
>       resolvconf instead of them?  My concern is this point.  I don't
>       expect the situation that people would like to add other
>       packages (like resolvconf) which restart nscd.


I am not sure what you mean here.  Resolvconf enhances the function of
nscd by restarting it when it needs to be restarted so that nscd clients
can resolve names using nameservers that have just become available.


>   (4) Is nscd only "suggest: resolvconf" package?  If so, why?


There are a number of others.  apt-cache showpkg reveals:

    squid, postfix, whereami, vpnc, pump, pdnsd, dnsmasq, fetchmail,
    dhcp3-client, netscript-2.4, laptop-net


>   (5) IIRC, this issue was raised on debian-devel lists.  Did many
>       people agree with this resolvconf framework?


I don't recall exactly.  However, 484 popcon participants have it 
installed so it can't be all bad.  :)

I would like to point out that 'Suggests:' is a very weak relationship. 
I means no more than "you might want to take a look at this too:".  I
think that resolvconf is something that many people installing nscd
should look at too.

However, it's your call.  You can "wontfix" this report if I haven't
convinced you yet.

-- 
Thomas Hood




Reply to: