From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Contents of /etc/hosts
Date: Tue, 11 Oct 2016 22:25:10 +0200 [thread overview]
Message-ID: <87lgxutyzd.fsf@gnu.org> (raw)
In-Reply-To: <20161006005710.GA2352@jocasta.intra> (John Darrington's message of "Thu, 6 Oct 2016 02:57:10 +0200")
Hello!
John Darrington <john@darrington.wattle.id.au> skribis:
> On Wed, Oct 05, 2016 at 10:17:14PM +0200, Ludovic Court??s wrote:
> Hi!
>
> John Darrington <john@darrington.wattle.id.au> skribis:
>
> > So ... my recommendations:
> >
> > 1. We change /etc/hosts to read
> >
> >
> > 127.0.0.1 localhost.localdomain localhost
> > ::1 localhost.localdomain localhost
> >
> > 127.0.0.2 gambrinus
>
> It???s not very useful to have ???localhost.localdomain???, is it?
>
> Try doing this: Put just a single line in your /etc/hosts:
> 127.0.0.1 localhost
> then run "hostname -d"
>
> You will get the answer "(none)"
Right.
But “localhost.localdomain” is kinda pointless no? I’ve checked a few
systems and I’ve never seen that. Typical desktop GNU/Linux installs
don’t have an FQDN and “hostname -d” doesn’t return one; that’s fine.
I think the current default is OK, but we should allow people to specify
an FQDN when there’s a meaningful one.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-10-11 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 18:31 Contents of /etc/hosts John Darrington
2016-10-05 20:17 ` Ludovic Courtès
2016-10-06 0:57 ` John Darrington
2016-10-06 10:07 ` Hartmut Goebel
2016-10-08 14:19 ` John Darrington
2016-10-11 20:25 ` Ludovic Courtès [this message]
2016-10-06 9:24 ` Hartmut Goebel
2016-10-08 14:08 ` John Darrington
2016-10-09 9:12 ` Hartmut Goebel
2016-10-09 9:56 ` John Darrington
2016-10-09 10:53 ` Hartmut Goebel
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgxutyzd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).