Re: [PATCH] resolv.conf updating
- From: Dan Williams <dcbw redhat com>
- To: Alexander Sack <asac jwsdot com>
- Cc: network manager <networkmanager-list gnome org>
- Subject: Re: [PATCH] resolv.conf updating
- Date: Mon, 11 Aug 2008 12:22:19 -0400
On Mon, 2008-08-11 at 17:06 +0200, Alexander Sack wrote:
> On Mon, Aug 11, 2008 at 01:28:19PM +0300, Tambet Ingo wrote:
> > Hey,
> >
> > There's been quite a few discussions on how to update resolv.conf on
> > debian. Now that opensuse is also moving to a script to update
> > resolv.conf, I wrote a patch for NM to allow distro specific methods
> > for updating. It defaults to writing out manually (all distros except
> > opensuse for now), but should give a good example how to add a debian
> > specific workaround.
>
> so the idea is to put the distro specific code directly into
> nm-named-manager.c ?
I guess... hopefully it won't be that much code per-distro.
> >
> > The other patch just removes the unused (and broken by design)
> > "should_update_resolv_conf".
>
> Good. With this removed and with distro specific system configuration
> things going into system-settings plugins, what use-cases are left for
> src/backends? Can we get rid of that completely?
>
> Distro specific configuration should definitly go into a
> system-settings plugins. What use-cases are left for src/backends
The backends should eventually die. Bits left:
1) kicking nscd (upstream nscd now detects changes automatically so this
is redundant going forward)
2) starting the loopback interface; probably best stuck into the
distro-specific NM initscripts anyway
3) hostname: will be folded into NM generically this week
Dan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]