From: Donny Davies <woodchip@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] perl compile stuck on lib/io_sock (was: emerge aborting on linux-headers)
Date: Mon Oct 8 04:26:01 2001 [thread overview]
Message-ID: <3BC17ECC.D6D0BDD3@gentoo.org> (raw)
> > Chad Huneycutt wrote: [Sun Oct 07 2001, 06:46:30PM EST]
> > > I have the entry
> > > 127.0.0.1 localhost localhost.localdomain
> > >
> > > in my /etc/hosts files, and a 'ping localhost' fails. I am pretty sure
> > > that syntax is correct. Anyone see the problem.
> >
> > Do you have the lo interface up? I think all you need to do is
> >
> > ifconfig lo up
>
> maybe your .localdomain is your problem ... do you have a nameserver
> for localdomain ?!? and it is not common to define localhost.localdomain.
>
> cya
>
> Holger
Note, it is *incorrect* to list localhost before localhost.localdomain. The
FQDN needs to be first, followed by any aliases you want to use.
Ie., this is wrong:
127.0.0.1 localhost localhost.localdomain
It must be done thusly:
127.0.0.1 localhost.localdomain localhost
Another common mistake is to list your real hostname in the 127.0.0.1
record. Ie, if your hostname is 'pluto', then dont do this!:
127.0.0.1 ..... pluto
Theres nothing wrong with defining localhost.localdomain though. In fact
its done a lot, mostly out of tradition, to serve as a placeholder. But the
order issue is important.
Cheers
--
Donny
next reply other threads:[~2001-10-08 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 4:26 Donny Davies [this message]
2001-10-08 6:35 ` [gentoo-dev] perl compile stuck on lib/io_sock (was: emerge aborting on linux-headers) Aron Griffis
2001-10-13 14:51 ` damaen
-- 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=3BC17ECC.D6D0BDD3@gentoo.org \
--to=woodchip@gentoo.org \
--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