From: Ulrich Drepper <drepper@redhat.com>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
serue@us.ibm.com, sam@vilain.net, clg@fr.ibm.com, dev@sw.ru
Subject: Re: [PATCH] POSIX-hostname up to 255 characters
Date: Fri, 26 May 2006 11:28:52 -0700 [thread overview]
Message-ID: <447748E4.4050908@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605261409300.8002@chaos.analogic.com>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
linux-os (Dick Johnson) wrote:
> MAXHOSTNAMELEN, defined by POSIX, is 64 bytes.
Where do you think this is written? The minimum maximum for the host
name length in POSIX is 255. This is the whole motivation of the patch.
Linux currently cannot conform because this is one of the things the
kernel gets wrong.
> You can't just
> change it to 255. If you did, all servers in the universe, all
> everything would have to be shutdown, recompiled, and rebooted
> simultaneously. You can't have a name-server returning a 255-byte
> string when a mail-server can only handle 64 bytes.
The hostname is a machine-local value. How the machine is represented
to the outside world is governed by services like DNS. DNS defines its
own limits on the length of the name and each component. So, if a host
name (without domain) exceeds 64 bytes you need a different external
name for the machine. But this doesn't stop anybody from locally using
a longer name.
Can there be programs which have problems? Certainly. But
gethostname() won't just overwrite memory. It'll return an error and
the programs with the wrong assumptions can be fix.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
next prev parent reply other threads:[~2006-05-26 18:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 3:45 Randy.Dunlap
2006-05-26 9:14 ` Eric W. Biederman
2006-05-26 14:42 ` Jan-Benedict Glaw
2006-05-26 17:28 ` Randy.Dunlap
2006-05-26 18:01 ` Jan-Benedict Glaw
2006-05-26 18:15 ` linux-os (Dick Johnson)
2006-05-26 18:28 ` Ulrich Drepper [this message]
2006-05-26 18:35 ` linux-os (Dick Johnson)
2006-05-26 18:55 ` Ulrich Drepper
2006-05-26 19:12 ` Jan Engelhardt
2006-05-26 21:31 ` Eric W. Biederman
2006-05-27 1:39 ` Randy.Dunlap
2006-05-27 7:36 ` Randy.Dunlap
2006-05-27 13:54 ` Eric W. Biederman
2006-05-28 18:32 ` Randy.Dunlap
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=447748E4.4050908@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=ebiederm@xmission.com \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=rdunlap@xenotime.net \
--cc=sam@vilain.net \
--cc=serue@us.ibm.com \
/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
Powered by JetHome