From: ebiederm@xmission.com (Eric W. Biederman)
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Ulrich Drepper <drepper@redhat.com>,
"linux-os (Dick Johnson)" <linux-os@analogic.com>,
Jan-Benedict Glaw <jbglaw@lug-owl.de>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
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 15:31:25 -0600 [thread overview]
Message-ID: <m13bewa2xe.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605262111130.11445@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Fri, 26 May 2006 21:12:42 +0200 (MEST)")
Jan Engelhardt <jengelh@linux01.gwdg.de> writes:
>>> It is written (on so-called compatible machines like my Sun) as:
>>>
>>> #define MAXHOSTNAMELEN _POSIX_HOST_NAME_MAX
>>>
>>> Then in limits.h, I see:
>>>
>>> #define _POSIX_HOST_NAME_MAX 64
>>
>>That's wrong. The value must be 255, at least for the current spec.
>>You really should verify your statements before making them public. The
>>POSIX spec is available in HTML for for viewing for free from the
>>OpenGroup. What a specific implementation does is not authoritative.
>>
>
> Let's all be happy with it that some systens have the maximum hostname length
> at 64 or 255... thay way, applications do not tend to depend on it.
> (Cf. Linux and the 100->1000 Hz change which _did_ turn up something.)
For all of the kibitzers please reread Rolands original post, where he
included the urls of the appropriate pieces of the Posix spec.
Eric
next prev parent reply other threads:[~2006-05-26 21:34 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
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 [this message]
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=m13bewa2xe.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=drepper@redhat.com \
--cc=jbglaw@lug-owl.de \
--cc=jengelh@linux01.gwdg.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