All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: host name length
Date: Fri, 12 Mar 2004 12:16:38 -0800	[thread overview]
Message-ID: <40521AA6.7070308@redhat.com> (raw)

POSIX nowadays contains

  _POSIX_HOST_NAME_MAX
and
  HOST_NAME_MAX

for programs to use to learn about the maximum host name length which is
allowed.  _POSIX_HOST_NAME_MAX is the standard-required minimum maximum
and the value must be 256.

The problem is that HOST_NAME_MAX currently is defined as 64, as defined
by __NET_UTS_LEN in <linux/utsname.h>.  I.e., we have HOST_NAME_MAX as
smaller than the minimum maximum which is obviously not POSIX compliant.

Now, we can simply ignore the problem or do something about it and
introduce a third version of the utsname structure with sufficiently big
nodename field.

Many OSes used small values before but 256 was chosen as a minimum
maximum and some OSes were changed since host names longer than 64 chars
indeed do exist.  I wonder why this never has been brought to the
attention.  Or were people happy enough with truncated host names?


Anyway, is there interest in getting this changed?

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

             reply	other threads:[~2004-03-12 20:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 20:16 Ulrich Drepper [this message]
2004-12-04  0:05 ` host name length Randy.Dunlap
2004-12-05 19:47   ` Ulrich Drepper
2004-12-06  8:35   ` Jan Engelhardt
2004-12-06 16:45     ` Randy.Dunlap
2004-12-06 17:31       ` Andreas Steinmetz
2004-12-06 19:25         ` Ulrich Drepper
2004-12-06 19:28           ` Andreas Steinmetz
2004-12-08 20:29             ` Randy.Dunlap
2004-12-09  0:35               ` Ulrich Drepper

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=40521AA6.7070308@redhat.com \
    --to=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.