network-manager main inclusion report

[Christian Bjälevik]

fre 2005-07-01 klockan 20:08 +0100 skrev Bastien Nocera:
> On Fri, 2005-07-01 at 18:04 +0200, Christian Bjälevik wrote:
> > fre 2005-07-01 klockan 09:52 +0100 skrev Bastien Nocera:
> > > On Fri, 2005-07-01 at 18:15 +1000, Jeff Waugh wrote:
> > > > <quote who="Bastien Nocera">
> > > > 
> > > > > > BIND is used because it's highly and dynamically reconfigurable, so it
> > > > > > copes well with rapidly changing networks, gateways, VPNs, and so on.
> > > > > > lwresd is an option, but doesn't have all the required functionality.
> > > > > > 
> > > > > > The configuration used for BIND by NetworkManager is minimal and secure,
> > > > > > so it's not a huge deal.
> > bind is already in main too. neither nscd or dnsmasq is :-).
> 
> This is split out from the glibc, it's not like it would be a huge
> program to bring in. Certainly less than BIND.
> 
Why bring in another program? BIND is already in main since warty (iirc)
and does the job real well.

> > > > > bind is huge for what you want to use it for, it's yet another network
> > > > > service. Use nscd, that's what it's there for... (The only drawback is
> > > > > that if you invalidate the cache during a lookup, that lookup will fail
> > > > > but the subsequent lookup will work, bit of an edge case).
> > > > 
> > > > afaik (and the reason why BIND was chosen by upstream), you can't configure
> > > > nscd at run time to the same degree you can with BIND.
> > > 
> > > Apart from a decent default config file, what is it you need exactly?
> > > It would certainly be nice to be able to switch host caching on easily
> > > without poking at the config file, but I don't see that as a real
> > > problem.
> > > 
> > > Dan Williams chose BIND, but it was nscd that was used in the end (after
> > > people kicked him for having a requires on bind).
> > > 
> > > ---
> > > Bastien Nocera <hadess at hadess.net> 
> > > You're either born crazy or born boring. -- Oliver Stone
> > 
> > The ability to switch forwarders on-the-fly? :-)
> 
> edit /etc/resolv.conf, and run "nscd -i hosts" and that's it. NM already
> does that for you.
> 
$ cat /etc/resolv.conf
; generated by NetworkManager, do not edit!
; Use a local caching nameserver controlled by NetworkManager
search magicalforest.se
nameserver 127.0.0.1

$ cat /var/lib/NetworkManager/NetworkManager-named.conf
// Named configuration, generated by NetworkManager

options {
        directory "/";
        query-source address * port *;
        forward only;
        forwarders {  192.168.0.1; };
        listen-on  { 127.0.0.1; };
        pid-file "/var/lib/NetworkManager/NetworkManager-pid-named";
};

// Disable rndc
controls { };


magicalforest.se and 192.168.0.1 picked up from my dhcp. Just works.
I'd say we stick with what we have. Why change stuff that already works?

> ---
> Bastien Nocera <hadess at hadess.net> 

Sincererly,
/Christian