public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why do we add the local host name to the 127.0.0.1 / ::1 entry in the /etc/hosts file?
Date: Thu, 25 Feb 2021 02:37:55 +0000	[thread overview]
Message-ID: <5697102.lOV4Wx5bFT@peak> (raw)
In-Reply-To: <65049b74-842b-0211-bbfe-35607c279a75@spamtrap.tnetconsulting.net>

On Sunday, 21 February 2021 22:23:00 GMT Grant Taylor wrote:
> Hi,
> 
> I'm reading Kerberos - The Definitive Guide[1] and it makes the
> 
> following comment:
> > And to make matters worse, some Unix systems map their own hostname
> > to 127.0.0.1 (the loopback IP address).
> 
> This makes me think that the local host name /shouldn't/ be included in
> the 127.0.0.1 (or ::1) entry in the /etc/hosts file.
> 
> However, according to the Gentoo AMD64 Handbook[2], we are supposed to
> add the local host name to the 127.0.0.1 (and ::1) entry in the
> /etc/hosts file.
> 
> Will someone please explain why the Gentoo AMD64 Handbook ~> Gentoo (at
> large) says to add the local host name to the 127.0.0.1 (or ::1) entry
> in the /etc/hosts file?  What was the thought process behind that?
> 
> Incidentally, adding the local host name to the 127.0.0.1 (or ::1) entry
> in the /etc/hosts file causes "hostname -i" to return 127.0.0.1 instead
> of the IP address bound to the network interface.

Isn't it a matter of simple logic? The loopback address is just that: the 
machine talking to itself, with no reference to the outside world. Whereas, 
while talking to other machines on the network its address is that of the 
interface. There's no connection between those two.

-- 
Regards,
Peter.





  parent reply	other threads:[~2021-02-25  2:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 22:23 [gentoo-user] Why do we add the local host name to the 127.0.0.1 / ::1 entry in the /etc/hosts file? Grant Taylor
2021-02-22  6:20 ` Andrew Udvare
2021-02-25  2:37 ` Peter Humphrey [this message]
2021-02-25  2:50   ` Grant Taylor
2021-02-25  7:02     ` Arve Barsnes
2021-02-25  7:33       ` Grant Taylor
2021-03-10  5:09 ` Grant Taylor
2021-03-10 13:27   ` Mark Knecht
2021-03-10 15:25     ` Michael
2021-03-10 16:00       ` Mark Knecht
2021-03-10 16:38         ` Michael
2021-03-10 17:07           ` Grant Taylor
2021-03-10 17:01         ` Grant Taylor
2021-03-10 16:58       ` Grant Taylor
2021-03-11 13:38         ` Michael
2021-03-11 16:50           ` Grant Taylor
2021-03-12 19:04             ` Michael
2021-03-13 19:01               ` Grant Taylor
2021-03-16 12:16                 ` Michael
2021-03-16 12:33                   ` Peter Humphrey
2021-03-16 18:54                   ` Grant Taylor
2021-03-11 17:04           ` Grant Taylor
2021-03-10 16:44     ` Grant Taylor
2021-03-10 17:43       ` Mark Knecht
2021-03-10 18:37         ` Grant Taylor
2021-03-11 10:54           ` Wols Lists

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=5697102.lOV4Wx5bFT@peak \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.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