From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what's the purpose of MAXHOSTNAMELEN?
Date: Tue, 29 Dec 2009 15:13:14 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912291507490.2610@localhost> (raw)
In-Reply-To: <4B3A5B15.5060807@garzik.org>
On Tue, 29 Dec 2009, Jeff Garzik wrote:
... snip ..
> > so lots of people define it but no one uses it. it *is*
> > exported to user space in /usr/include/asm/param.h, but i still
> > have no idea what it's for in user space. obsolete?
>
> According to RFC 1034, "Each node has a label, which is zero to 63
> octets in length"
>
> What is it used for in userspace, and why is it export from the
> kernel? Good question...
it's not clear what value that macro has in user space since (as
i've always understood it) the point of exporting a macro like that to
user space is so that user space apps can *agree* with kernel code
that employs the same macro.
but if absolutely *nothing* in the kernel uses that macro, then
there's nothing for user space to "agree" with. in other words, that
macro cannot *possibly* have any meaningful value in user space. does
that make sense?
my reaction at this point is to simply remove that macro definition
from include/asm-generic/param.h. anything in user space that's using
that macro is simply using a macro with a completely arbitrary value.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-12-29 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 19:19 what's the purpose of MAXHOSTNAMELEN? Robert P. J. Day
2009-12-29 19:28 ` Samuel Thibault
2009-12-29 19:40 ` Jeff Garzik
2009-12-29 19:56 ` Samuel Thibault
2009-12-29 20:20 ` Jeff Garzik
2009-12-29 20:26 ` Samuel Thibault
2009-12-29 21:00 ` Vikram Dhillon
2009-12-29 20:13 ` Robert P. J. Day [this message]
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=alpine.LFD.2.00.0912291507490.2610@localhost \
--to=rpjday@crashcourse.ca \
--cc=jeff@garzik.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox