From: Shawn Starr <spstarr@sh0n.net>
To: Keith Owens <kaos@ocs.com.au>
Cc: Linux <linux-kernel@vger.kernel.org>
Subject: Re: uname reports 'unknown'
Date: 12 Mar 2002 17:59:53 -0500 [thread overview]
Message-ID: <1015973994.303.2.camel@coredump> (raw)
In-Reply-To: <6826.1015902879@kao2.melbourne.sgi.com>
In-Reply-To: <6826.1015902879@kao2.melbourne.sgi.com>
Perhaps it should display P54C which is my P200 processor type?
On Mon, 2002-03-11 at 22:14, Keith Owens wrote:
> On 11 Mar 2002 20:43:37 -0500,
> Shawn Starr <spstarr@sh0n.net> wrote:
> >Linux coredump 2.4.19-pre2-ac4-xfs-shawn10 #2 Mon Mar 11 03:36:35 EST
> >2002 i586 unknown
> >
> >
> >what should 'unknown' really be? I've never seen it different on Intel
> >systems.
>
> 'unknown' is the output from uname -p, host processor type. That field
> is not supported in the Linux kernel. uname.c in sh-utils has this
>
> #if defined (HAVE_SYSINFO) && defined (SI_ARCHITECTURE)
> if (sysinfo (SI_ARCHITECTURE, processor, sizeof (processor)) == -1)
> error (1, errno, _("cannot get processor type"));
> #else
> strcpy (processor, "unknown");
> #endif
>
> HAVE_SYSINFO is always false in sh-utils and SI_ARCHITECTURE is not
> defined in glibc so you always get unknown.
>
>
next prev parent reply other threads:[~2002-03-12 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 1:43 uname reports 'unknown' Shawn Starr
2002-03-12 3:14 ` Keith Owens
2002-03-12 22:59 ` Shawn Starr [this message]
2002-03-12 23:22 ` Keith Owens
2002-03-12 23:37 ` J Sloan
2002-03-13 0:46 ` Carlos E Gorges
2002-03-12 5:16 ` J Sloan
2002-03-13 19:26 ` David Ford
2002-03-13 21:10 ` J Sloan
2002-03-12 11:59 ` Davidovac Zoran
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=1015973994.303.2.camel@coredump \
--to=spstarr@sh0n.net \
--cc=kaos@ocs.com.au \
--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.