all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Wed, 05 Oct 2016 22:17:14 +0200	[thread overview]
Message-ID: <87zimi5z5h.fsf@gnu.org> (raw)
In-Reply-To: <20161005183147.GA32276@jocasta.intra> (John Darrington's message of "Wed, 5 Oct 2016 20:31:47 +0200")

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?  Also,
shouldn’t we keep the same address for both names?

Like:

  127.0.0.1 localhost
  ::1       localhost
  127.0.0.1 gambrinus
  ::1       gambrinus

Or am I missing something?

> 2. We put some checks in guix system to ensure that the host-name field does not
>  exceed 63 bytes (not characters) and that it conforms to the format of RFC1034

Sure, makes sense.

> Any objections if I commit a patch to gnu/system.scm ??

Send it first.  :-)

Thanks,
Ludo’.

  reply	other threads:[~2016-10-05 20:17 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=87zimi5z5h.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.