From: Vikram Dhillon <dhillonv10@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
"Robert P. J. Day" <rpjday@crashcourse.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: what's the purpose of MAXHOSTNAMELEN?
Date: Tue, 29 Dec 2009 16:00:35 -0500 [thread overview]
Message-ID: <ea6602020912291300x322ced07j4a6268cda7de4a06@mail.gmail.com> (raw)
In-Reply-To: <4B3A64A8.5040104@garzik.org>
I care about Hurd :D, but yah as it is mentioned before, would it
sometime in future be possible to remove this from the kernel ?
Regards,
Vikram Dhillon
~~~
There are lots of Linux users who don't care how the kernel works, but
only want to use it. That is a tribute to how good Linux is.
-- Linus Torvalds
On Tue, Dec 29, 2009 at 3:20 PM, Jeff Garzik <jeff@garzik.org> wrote:
> On 12/29/2009 02:56 PM, Samuel Thibault wrote:
>>
>> Jeff Garzik, le Tue 29 Dec 2009 14:40:05 -0500, a écrit :
>>>
>>> On 12/29/2009 02:19 PM, Robert P. J. Day wrote:
>>>>
>>>> arch/s390/include/asm/param.h:#define MAXHOSTNAMELEN 64 /* max
>>>> length of hostname */
>>>>
>>>> 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"
>>
>> That's for Internet networks. Other kinds of networks could implement
>> more. It could make sense to restrict ourself to Internet standards,
>> but we don't :)
>
> Er huh? That was a description of the origin of the limit.
>
> And as a point of fact, we do restrict ourself to that:
>
> #define __NEW_UTS_LEN 64
>
> struct new_utsname {
> char sysname[__NEW_UTS_LEN + 1];
> char nodename[__NEW_UTS_LEN + 1];
>
>
>
>>> What is it used for in userspace, and why is it export from the kernel?
>>
>> Gethostname, typically, but also all kinds of functions that provide a
>> hostname. It's also quite often completely badly used, for instance for
>> getnameinfo()...
>>
>> You have Debian's list on
>> http://unstable.buildd.net/buildd/hurd-i386_Failed.html
>
> No one cares about Hurd.
>
> Jeff
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-12-29 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 19:19 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 [this message]
2009-12-29 20:13 ` Robert P. J. Day
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=ea6602020912291300x322ced07j4a6268cda7de4a06@mail.gmail.com \
--to=dhillonv10@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
--cc=samuel.thibault@ens-lyon.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
all inboxes | Powered by JetHome®