netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dlstevens@us.ibm.com
Cc: simon@fire.lp0.eu, cscott@laptop.org, netdev@vger.kernel.org,
	netdev-owner@vger.kernel.org
Subject: Re: [RFD] First draft of RDNSS-in-RA support for IPv6 DNS autoconfiguration
Date: Fri, 22 Jun 2007 22:12:29 -0700 (PDT)	[thread overview]
Message-ID: <20070622.221229.125566330.davem@davemloft.net> (raw)
In-Reply-To: <OFB5D50B53.A24A00A2-ON88257303.0017FE53-88257303.0018AD5D@us.ibm.com>

From: David Stevens <dlstevens@us.ibm.com>
Date: Fri, 22 Jun 2007 21:30:05 -0700

> netdev-owner@vger.kernel.org wrote on 06/22/2007 06:17:46 PM:
> 
> > On 23/06/07 02:04, David Stevens wrote:
> > >         Why not make the application that writes resolv.conf
> > > also listen on a raw ICMPv6 socket? I don't believe you'd need
> > > any kernel changes, then, and it seems pretty simple and
> > > straightforward.
> > 
> > Because then it requires yet another network daemon, RA in 
> > the kernel means there's no need for one to manage adding 
> > auto-configured IP addresses... what's wrong with doing the 
> > same for DNS?
> 
>         It's not yet another one, since you have to run something
> to get it in resolv.conf, anyway. That seems much better to me
> than having the kernel track data that can only be used at the
> application layer. The app itself looks like it'd be really simple.
>         Auto-configured addresses are used by the kernel. It has to
> have those addresses. But the kernel doesn't do DNS look-ups, or
> write resolv.conf; that's the difference, for me.

I totally agree with David, this stuff definitely does not belong
in the kernel.

  parent reply	other threads:[~2007-06-23  5:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-22 23:26 [RFD] First draft of RDNSS-in-RA support for IPv6 DNS autoconfiguration C. Scott Ananian
2007-06-22 23:39 ` Michael Buesch
2007-06-23  0:09   ` C. Scott Ananian
2007-06-23  2:11     ` Dan Williams
2007-06-23  9:07     ` Michael Buesch
2007-06-23 20:41       ` David Miller
2007-06-22 23:42 ` Michael Buesch
2007-06-23  1:04 ` David Stevens
2007-06-23  1:17   ` Simon Arlott
2007-06-23  4:30     ` David Stevens
2007-06-23  4:50       ` Simon Arlott
2007-06-23  5:12       ` David Miller [this message]
2007-06-23  8:23         ` Pierre Ynard
2007-06-24 19:05     ` Olaf Kirch
2007-06-23 13:25   ` Rémi Denis-Courmont
2007-06-23 14:47     ` C. Scott Ananian
2007-06-23 16:40       ` Simon Arlott
2007-06-23 16:48       ` David Stevens
2007-06-23 16:51         ` Rémi Denis-Courmont
2007-06-23 17:45           ` David Stevens
2007-06-23 18:13             ` Rémi Denis-Courmont
2007-06-23 18:51               ` David Stevens
2007-06-23 19:18                 ` Rémi Denis-Courmont
2007-06-23 20:27             ` Pierre Ynard
2007-06-25  2:17       ` Dan Williams
2007-06-25  2:53         ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070622.221229.125566330.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cscott@laptop.org \
    --cc=dlstevens@us.ibm.com \
    --cc=netdev-owner@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=simon@fire.lp0.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).