Henrique de Moraes Holschuh wrote:
> Because instead of doing this:
>
> 127.0.0.1 localost localhost.localdomain
>
> It was done like this:
>
> 127.0.0.1 localhost.localdomain localhost
>
> Thus changing the canonical name of the loopback interface. PLEASE do not
> do this unless you have *extremely* good reasons to do so. An untracked DNS
> timeout is definately not one. If you can still reproduce the problem, we
> can work on tracking that thing down without the localhost.localdomain.
FWIW, it was done as a result of bug #247734, which includes details on
how every possible choice seems to break something and the reasoning
that led to the current choice.
> Add a new loopback interface (say, 127.0.0.2) and name it however you want.
> That will not break anything at all, and it allows you to name your system
> in whatever way you might want. This is what d-i should be doing, it is the
> maximum compatibility path.
Already done:
netcfg (1.13) unstable; urgency=low
[ Thomas Hood ]
* If there is no permanent IP address with which the system hostname
(i.e., that which is returned by the "hostname" command) can be
associated in /etc/hosts then associate it with address 127.0.1.1
rather than 127.0.0.1. Associating the system hostname with the
latter had the unwanted effect of making 'localhost.localdomain'
the canonical hostname associated with the system hostname.
That is, 'hostname --fqdn' returned 'localhost.localdomain'.
(Closes: #316099)
Programs that access local services at the IP address obtained by
resolving the system hostname SHOULD NOT DO THIS, but those that
do so will not be disappointed: most services that listen locally
listen on all 127/8 addresses, not just on 127.0.0.1.
-- Frans Pop <fjp@debian.org> Fri, 19 Aug 2005 21:08:39 +0200
--
see shy jo
Attachment:
signature.asc
Description: Digital signature