From: Keith Owens <kaos@ocs.com.au>
To: Thomas Dodd <ted@cypress.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modutils can't handle long kernel names
Date: Thu, 15 Nov 2001 09:25:39 +1100 [thread overview]
Message-ID: <28111.1005776739@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Wed, 14 Nov 2001 16:04:38 MDT." <3BF2EA76.6010702@cypress.com>
On Wed, 14 Nov 2001 16:04:38 -0600,
Thomas Dodd <ted@cypress.com> wrote:
>Keith Owens wrote:
>> +uts_len := 64
>> +uts_truncate := sed -e 's/\(.\{1,$(uts_len)\}\).*/\1/'
>
>Should this be a fixed length of 64?
>Or should it be grabbed form a header somewhere?
>So when/if SYS_NMLN/_UTSNAME_LENGTH is changed
>longer strings can be used? I check and Solaris 8
>defines SYS_NMLN as 257.
>
>Would this break cross-comiling badly?
>Are other libc headers needed in the build?
This is the kernel's idea of uts length, not glibc, it is independent
of where you are compiling. It could be extracted from the kernel
header,
uts_len := $(shell sed -ne 's/#define __NEW_UTS_LEN //p' include/linux/utsname.h)
but why bother? The value has been fixed at 64 since at least 2.0 and
is embedded in glibc so it is unlikely to change. Even if it does
change, it must be upwards so the worst case is fail safe.
prev parent reply other threads:[~2001-11-14 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-09 4:42 Modutils can't handle long kernel names Mike Fedyk
2001-11-09 5:23 ` Mike Fedyk
2001-11-09 5:40 ` Robert Love
2001-11-09 5:34 ` Keith Owens
2001-11-09 22:23 ` andersg
2001-11-10 4:29 ` Keith Owens
2001-11-14 22:04 ` Thomas Dodd
2001-11-14 22:25 ` Keith Owens [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=28111.1005776739@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ted@cypress.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