From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261459AbVFHR0F (ORCPT ); Wed, 8 Jun 2005 13:26:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261406AbVFHRXs (ORCPT ); Wed, 8 Jun 2005 13:23:48 -0400 Received: from fire.osdl.org ([65.172.181.4]:31714 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261452AbVFHRXL (ORCPT ); Wed, 8 Jun 2005 13:23:11 -0400 Date: Wed, 8 Jun 2005 10:24:59 -0700 (PDT) From: Linus Torvalds To: Paul Mackerras cc: akpm@osdl.org, anton@samba.org, linux-kernel@vger.kernel.org, jk@blackdown.de Subject: Re: [PATCH] ppc64: Fix PER_LINUX32 behaviour In-Reply-To: <17062.56723.535978.961340@cargo.ozlabs.ibm.com> Message-ID: References: <17062.56723.535978.961340@cargo.ozlabs.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 8 Jun 2005, Paul Mackerras wrote: > > * uname(2) doesn't respect PER_LINUX32, it returns 'ppc64' instead of 'ppc' I think this is a feature, not a bug, and I suspect you just broke compiling a 64-bit kernel by default on ppc64. Dammit, the system _is_ ppc64. The fact that the uname binary is not is neither here nor there. It's like x86 that reports i386/i486/.. depending on what the machine is. If uname wants to make it clear that uname has been compiled for 32-bit ppc, then it can damn well output "ppc" on its own without asking the kernel what the kernel is. Linus