netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: csnook@redhat.com
Cc: thierry.bultel@wanadoo.fr, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Suggested patch: Sending the FQDN when booting via DHCP
Date: Wed, 10 Sep 2008 15:35:17 -0700 (PDT)	[thread overview]
Message-ID: <20080910.153517.23060861.davem@davemloft.net> (raw)
In-Reply-To: <48C73C15.2000103@redhat.com>

From: Chris Snook <csnook@redhat.com>
Date: Tue, 09 Sep 2008 23:16:37 -0400

> Thierry wrote:
> > [re-sent without HTML encoding, and to the right aliases ...]
> > Hi all,
> > the following patch can be useful, in order to let the DHCP server accordingly update the DNS, when booting via DHCP.
> > This can be useful for 2 reasons:
> > 1) on small systems, the embedded filesystem may even not have udhcpd
> > 2) when booting nfsroot, the nfs server does not like when udhcpd in invoked, even when requested the same IP address.
> > Here is the patch, for 2.6.27-rc5. (Notice that it is the very first time I deliver a patch for Linux, and I may
> > have missed some points on the procedure, if it is the case I apologize for that). What do you think about it ?
> > Any ideas or comments are welcome.
> 
> This should probably be a kernel command-line option, rather than a static config option.

Also:

1) The submitter's email client corrupted the patch making it unusable anyways,
   it munged tabs into spaces etc.

2) At this point in time ->nodename is going to be something like "(none)" and
   therefore not very useful.  This only gets set after userland has started
   up.

So really, the nodename would need to be specified as well as a command line
option for this to really be useful.

      reply	other threads:[~2008-09-10 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 17:35 Suggested patch: Sending the FQDN when booting via DHCP Thierry
2008-09-10  3:16 ` Chris Snook
2008-09-10 22:35   ` David Miller [this message]

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=20080910.153517.23060861.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=thierry.bultel@wanadoo.fr \
    /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).