public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <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 10:43:44 -0700	[thread overview]
Message-ID: <CAK2H+edDexmJEVs=o1oB26_zZfTXrSg=+R=ytsU+CcNR+b_zgA@mail.gmail.com> (raw)
In-Reply-To: <e1d975b8-fc26-1282-56ed-c898834b766d@spamtrap.tnetconsulting.net>

[-- Attachment #1: Type: text/plain, Size: 3089 bytes --]

On Wed, Mar 10, 2021 at 9:44 AM Grant Taylor <
gtaylor@gentoo.tnetconsulting.net> wrote:
>
> 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.
>

OK, agreed, completely. localhost must be turned into an IP address.

I guess what I was thinking was DNS means Server. If it's a Service
then that's different. I think we're in agreement that if it can find the
name in /etc/hosts, either actively or cached somewhere in memory,
then it doesn't have to send anything over a cable to get the answer.

And cable is too generic as I understand that DNS might be on this
machine.

Point taken.

> 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.
>

Agreed but I suspect if I don't have it in /etc/hosts then I'm unlikely
to get results that make sense in real time, but that's case buy case.

Again, completely agreed.

> > 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.
>

<LOL> I'm approaching my 66th birthday. Deep dark times for me are
almost certainly more recent dates than for you. ;-)

> > 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.
>

I took it as simply a Kerberos setup/config warning. Whoever wrote that
had an opinion, experience or both and wanted you to know that. I
didn't read anything more into it. The author cannot change what
"some distros" do but wants to give you a fighting chance to get
Kerberos working in case you're using one. Makes no sense to mention
a specific distro because the list probably changes over time.

Basically "You'd be wise to look at your /etc/hosts file and fix this
silly configuration error that some distros do before trying to
setup Kerberos"

<SNIP>

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

I'm not a sys admin nor a Gentoo developer or documenter so I cannot
comment on the manual specifically.

As I no longer run Gentoo - I haven't for about 3 years other than one
remaining VM seldom used and seldom updated - I'm way out of
touch with the actual manual but interested in the subject.

Over and out.

- Mark

[-- Attachment #2: Type: text/html, Size: 4138 bytes --]

  reply	other threads:[~2021-03-10 17: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
2021-03-10 17:43       ` Mark Knecht [this message]
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='CAK2H+edDexmJEVs=o1oB26_zZfTXrSg=+R=ytsU+CcNR+b_zgA@mail.gmail.com' \
    --to=markknecht@gmail.com \
    --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