netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: josh@joshtriplett.org, netdev@vger.kernel.org, serge@hallyn.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	kel@otaku42.de, pkg-sysvinit-devel@lists.alioth.debian.org
Subject: Re: [PATCH] uts: Make default hostname configurable, rather than always using "(none)"
Date: Tue, 31 May 2011 12:46:30 -0700 (PDT)	[thread overview]
Message-ID: <20110531.124630.449848946.davem@davemloft.net> (raw)
In-Reply-To: <BANLkTikgqkd0BckvTrFwAOmJQ0ObP4OOjg@mail.gmail.com>

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue, 31 May 2011 20:35:37 +0900

> On Tue, May 31, 2011 at 7:38 AM, Josh Triplett <josh@joshtriplett.org> wrote:
>>
>> The "hostname" tool falls back to setting the hostname to "localhost" if
>> /etc/hostname does not exist.  Distribution init scripts have the same
>> fallback.  However, if userspace never calls sethostname, such as when
>> booting with init=/bin/sh, or otherwise booting a minimal system without
>> the usual init scripts, the default hostname of "(none)" remains,
>> unhelpfully appearing in various places such as prompts
>> ("root@(none):~#") and logs.  Furthermore, "(none)" doesn't typically
>> resolve to anything useful.
> 
> Ok, I'm fine with this. So Ack as far as I'm concerned.
> 
> Does this make most sense through the networking tree, or what?

Linus, you can just apply this directly.

Thanks!

      reply	other threads:[~2011-05-31 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-30 22:38 [PATCH] uts: Make default hostname configurable, rather than always using "(none)" Josh Triplett
2011-05-31 11:35 ` Linus Torvalds
2011-05-31 19:46   ` 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=20110531.124630.449848946.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=josh@joshtriplett.org \
    --cc=kel@otaku42.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pkg-sysvinit-devel@lists.alioth.debian.org \
    --cc=serge@hallyn.com \
    --cc=torvalds@linux-foundation.org \
    /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).