From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261349AbTDDVnV (for ); Fri, 4 Apr 2003 16:43:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261357AbTDDVnV (for ); Fri, 4 Apr 2003 16:43:21 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:17164 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id S261349AbTDDVnT (for ); Fri, 4 Apr 2003 16:43:19 -0500 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: Syscall numbers for BProc Date: 4 Apr 2003 13:54:18 -0800 Organization: Transmeta Corporation, Santa Clara CA Message-ID: References: <20030404193218.GD15620@lanl.gov> <20030404203531.A29501@infradead.org> <20030404204344.GF15620@lanl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2003 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: <20030404204344.GF15620@lanl.gov> By author: hendriks@lanl.gov In newsgroup: linux.dev.kernel > > > > Please explain why you need syscalls and the exact APIs. > [ ... ] OK, you've answered the first question, could you please answer the second one? Thanks, -hpa P.S. I'm in favour of this request, but we still need the answers... -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64