public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: <god@yinyang.hjsoft.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: "uname -p" prints unknown for Athlon K7 optimized kernel?
Date: 15 Apr 2001 19:43:10 +0200	[thread overview]
Message-ID: <jed7ae83f5.fsf@hawking.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.31.0104151152400.26676-100000@yinyang.hjsoft.com>
In-Reply-To: <Pine.LNX.4.31.0104151152400.26676-100000@yinyang.hjsoft.com> ("Mr. Shannon Aldinger"'s message of "Sun, 15 Apr 2001 11:55:49 -0400 (EDT)")

"Mr. Shannon Aldinger" <god@yinyang.hjsoft.com> writes:

|> On Sun, 15 Apr 2001, it was written:
|> 
|> > elfie:~ # uname -p
|> > unknown
|> >
|> > elfie:~ # uname -a
|> > Linux elfie 2.4.3 #1 Fri Apr 13 21:08:29 CEST 2001 i586 unknown
|> >
|> I get the same on my Sun Ultra 1, and various x86 boxes. I'm sure this is
|> normal, I'm just not sure how you would change that label. I know gcc
|> compiles everything with a target of gcc-linux-unkown on my machines, so
|> the uknown may be coming from there...

The two things are completely unrelated.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5

  reply	other threads:[~2001-04-15 17:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-15  5:10 "uname -p" prints unknown for Athlon K7 optimized kernel? Ishikawa
2001-04-14 20:20 ` Bart Trojanowski
2001-04-15  5:38 ` joker
2001-04-15 13:57   ` Heinz Diehl
2001-04-15 15:55     ` Mr. Shannon Aldinger
2001-04-15 17:43       ` Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-14 21:04 xcp

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=jed7ae83f5.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=god@yinyang.hjsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox