From: Christian Trefzer <ctrefzer@gmx.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Alistair John Strachan <s0348365@sms.ed.ac.uk>,
Linus Torvalds <torvalds@osdl.org>,
Kyle McMartin <kyle@mcmartin.ca>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...)
Date: Fri, 26 May 2006 23:11:40 +0200 [thread overview]
Message-ID: <20060526211140.GC16059@hermes.uziel.local> (raw)
In-Reply-To: <Pine.LNX.4.61.0605261354220.899@yvahk01.tjqt.qr>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi everyone,
On Fri, May 26, 2006 at 01:56:02PM +0200, Jan Engelhardt wrote:
> What a mess. I would prefer to see Linux distributions have
> 127.0.0.1 localhost
> in their /etc/hosts (to have the standard 127.0.0.1<->localhost mapping)
> and /etc/HOSTNAME contain the hostname, which is
> sethostname()d/setdomainname()d by init scripts and gethostname()d by apps.
Well I always thought that 127.0.0.1 is localhost, and _only_ localhost,
and the host's real name would rather be mapped to its IP on the real
NIC. Every interface (including local loopback) has a distinct IP;
hostnames are supposed to be resolved to one of these and need to be
somewhat unique on subnets, unless a fqdn is supplied. So here's what I
got, following that scheme:
127.0.0.1 localhost.localdomain localhost
192.168.x.y host.domain.tdl host
Major catch: it presumes you have at least one NIC actually in use. If
lo is the absolute sole interface, one might map every single hostname
to that one as well. Schizophrenia is fun, solitude is gone for good : )
Larger institutions would prefer dynamic stuff like DHCP and DNS anyway,
but for distros' installers intended for home users this might be a
viable solution - never experienced any strangeness with that one so
far.
Just my .02€, with kind regards
Chris
[-- Attachment #2: Type: application/pgp-signature, Size: 829 bytes --]
next prev parent reply other threads:[~2006-05-26 21:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 14:17 [PATCH] Well, Linus seems to like Lordi Kyle McMartin
2006-05-25 15:46 ` Linus Torvalds
2006-05-25 16:02 ` Steven Rostedt
2006-05-25 16:15 ` alan
2006-05-25 16:26 ` Linus Torvalds
2006-05-25 16:43 ` Jan Engelhardt
2006-05-26 23:47 ` Folkert van Heusden
2006-05-27 7:05 ` Oliver Neukum
2006-05-25 16:37 ` [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...) Jan Engelhardt
2006-05-25 16:48 ` Linus Torvalds
2006-05-25 18:40 ` Jan Engelhardt
2006-05-25 18:47 ` Linus Torvalds
2006-05-25 18:53 ` [PATCH] Add compile domain İsmail Dönmez
2006-05-25 18:59 ` Jan Engelhardt
2006-05-25 19:00 ` İsmail Dönmez
2006-05-25 18:54 ` [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...) Alistair John Strachan
2006-05-25 19:02 ` Jan Engelhardt
2006-05-25 21:14 ` [PATCH] Add compile domain Martin J. Bligh
2006-05-25 21:38 ` Alistair John Strachan
2006-05-25 22:12 ` Måns Rullgård
2006-05-25 21:43 ` Måns Rullgård
2006-05-25 19:06 ` [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...) Linus Torvalds
2006-05-25 20:29 ` Lennart Sorensen
2006-05-26 11:56 ` Jan Engelhardt
2006-05-26 21:11 ` Christian Trefzer [this message]
2006-05-27 2:14 ` [PATCH] Add compile domain Bernd Eckenfels
2006-05-29 12:25 ` [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...) Gabor Gombas
2006-05-29 23:13 ` [PATCH] Add compile domain Bernd Eckenfels
2006-05-30 13:54 ` Gabor Gombas
2006-05-27 2:13 ` Bernd Eckenfels
2006-05-25 19:43 ` [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...) bjdouma
2006-05-25 20:13 ` Lennart Sorensen
2006-05-25 20:34 ` H. Peter Anvin
2006-05-27 2:19 ` [PATCH] Add compile domain Bernd Eckenfels
2006-05-29 12:08 ` [PATCH] Add compile domain (was: Re: [PATCH] Well, Linus seems to like Lordi...) Gabor Gombas
2006-05-29 20:20 ` Linus Torvalds
2006-05-29 20:47 ` Joshua Hudson
2006-05-29 23:17 ` [PATCH] Add compile domain Bernd Eckenfels
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=20060526211140.GC16059@hermes.uziel.local \
--to=ctrefzer@gmx.de \
--cc=jengelh@linux01.gwdg.de \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=s0348365@sms.ed.ac.uk \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®