From: damaen <damaen@rochester.rr.com>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] perl compile stuck on lib/io_sock (was: emerge aborting on linux-headers)
Date: Sat Oct 13 14:51:02 2001 [thread overview]
Message-ID: <20011013165130.C5427@magdelina> (raw)
In-Reply-To: <20011008073453.A30789@yde.flatmonk.org>; from agriffis@gentoo.org on Mon, Oct 08, 2001 at 12:34:53 +0000
On 2001.10.08 12:34 Aron Griffis wrote:
> Hi Woodchip,
>
> Woodchip wrote: [Mon Oct 08 2001, 05:24:12AM EST]
> > Note, it is *incorrect* to list localhost before
> > localhost.localdomain. The FQDN needs to be first, followed by any
> > aliases you want to use.
>
> Actually, I think you may be wrong in this case. You are correct about
> putting FQDN first, but in this case, "localhost" may be the
> fully-qualified domain, and "localhost.localdomain" may be the alias,
> since there is no actualy domain called "localdomain".
>
> If you list "localhost" first, then programs that resolve IP->name using
> /etc/hosts via the gethostby*() functions will resolve
> 127.0.0.1->localhost, which in my experience is desirable over
> 127.0.0.1->localhost.localdomain.
>
> Aron
I stand corrected from my previous post... :) Personally, I haven't really
found any issues with using localhost after localhost.localdomain. That's
just the way I've always done it.
next prev parent reply other threads:[~2001-10-13 20:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 4:26 [gentoo-dev] perl compile stuck on lib/io_sock (was: emerge aborting on linux-headers) Donny Davies
2001-10-08 6:35 ` Aron Griffis
2001-10-13 14:51 ` damaen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-06 22:57 Cliff Crawford
2001-10-06 23:52 ` Daniel Robbins
2001-10-07 0:37 ` jano
2001-10-07 17:04 ` Aron Griffis
2001-10-07 17:45 ` Chad Huneycutt
2001-10-07 18:23 ` Collins Richey
2001-10-07 19:01 ` Aron Griffis
2001-10-08 3:15 ` Holger Brueckner
2001-10-08 6:35 ` Aron Griffis
2001-10-13 14:20 ` damaen
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=20011013165130.C5427@magdelina \
--to=damaen@rochester.rr.com \
--cc=gentoo-dev@cvs.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