Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 6 Jun 2005 12:03:29 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: reason for uname -p,-i returning "unkown"?
Message-ID: <20050606160329.GC3833@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <d81p45$7vs$1 AT sea DOT gmane DOT org> <20050606155527 DOT GK3268 AT calimero DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050606155527.GK3268@calimero.vinschen.de>
User-Agent: Mutt/1.5.8i

On Mon, Jun 06, 2005 at 05:55:27PM +0200, Corinna Vinschen wrote:
>On Jun  6 08:15, Hans Horn wrote:
>> Is there a particular reason for uname -p and uname -i returning "unknown"?
>> Looks like as if the info that should be returned is in /proc/cpuinfo:
>> 
>> 'vendor_id' --> uname -i
>> 'model name' --> uname -p
>
>Cygwin doesn't provide the system interfaces called by uname for this
>purpose.
>
>Hmm, I just found that Cygwin prints "amd64" as machine while Linux
>prints x86_64.  Is it worth to change this?

I think so, yes.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/