public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
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: Wed, 10 Mar 2021 09:44:27 -0700	[thread overview]
Message-ID: <e1d975b8-fc26-1282-56ed-c898834b766d@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAK2H+edOhCjcokfLW=qF+HddMRqHNXMrd9gpvyn4NFHpyfObeQ@mail.gmail.com>

On 3/10/21 6:27 AM, Mark Knecht wrote:
> Caveat - not an expert, just my meager understanding:
> 
> 1) The name 'localhost' is historically for developers who want to 
> access their own machine _without_ using DNS.

Eh....

Using the /name/ "localhost" still uses name resolution.  It could use 
DNS or it may not.  It /typically/ means the /etc/hosts file.  But it 
could mean DNS or NIS(+) or LDAP or something more esoteric.

IMHO what's special about the "localhost" name in particular is that 
it's an agnostic / anycast method to say the local host that a given 
program is running on without regard to what the actual host name is.

> 2) By general practice sometime in the deep, dark times 127.0.0.1 was 
> accepted for this purpose. There's nothing special about the address.

Deep, dark times?  It's still used every single day across multiple 
platforms, Linux, Unix, Windows, z/OS, i/OS, you name it.

> 3) I read the original quoted comment in the Kerberos Guide as a warning 
> - 'to make matters worse, __SOME__"

What did the warning mean to you?  Because I took it as "be careful, 
your $OS /may/ do this incorrectly".  Where "this" is putting the FQDN 
on the same line as 127.0.0.1 and / or ::1.

> 4) In my /etc/hosts I do _NOT_ map my machine's name to the same address 
> as localhost, avoiding the Kerberos warning:

ACK

I'm grateful for corroboration, but unfortunately that doesn't speak to 
why the Gentoo handbook suggests what it does.



-- 
Grant. . . .
unix || die


  parent reply	other threads:[~2021-03-10 16:44 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
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 [this message]
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=e1d975b8-fc26-1282-56ed-c898834b766d@spamtrap.tnetconsulting.net \
    --to=gtaylor@gentoo.tnetconsulting.net \
    --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