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: Thu, 25 Feb 2021 00:33:19 -0700 [thread overview]
Message-ID: <a4cbcaef-7b98-a584-fe69-6d08226c2767@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <CAJjrzcUO86zfSTs31T8YweFFA542RCYmKwSaVUCAXDQ=G0Z67w@mail.gmail.com>
On 2/25/21 12:02 AM, Arve Barsnes wrote:
> I don't think that was the question Peter sought to answer, but rather
> that 'hostname -i' returns the loopback address either way.
But 'hostname -i' /doesn't/ return the 127.0.0.1 or ::1 if the hostname
isn't on lines with 127.0.0.1 or ::1.
> Might still defy logic depending on the way you look at it, but that's
> a different question.
Hence why I'm seeking the logic behind what was done.
--
Grant. . . .
unix || die
next prev parent reply other threads:[~2021-02-25 7:33 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 [this message]
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=a4cbcaef-7b98-a584-fe69-6d08226c2767@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