mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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:55:07 -0700	[thread overview]
Message-ID: <44774F0B.8010805@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605261430370.8339@chaos.analogic.com>

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

linux-os (Dick Johnson) wrote:
> 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.

-- 
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2006-05-26 18:55 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 [this message]
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=44774F0B.8010805@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