From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from colo.lackof.org (colo.lackof.org [198.49.126.79]) by dsl2.external.hp.com (Postfix) with ESMTP id A031D484B for ; Thu, 18 Dec 2003 12:55:36 -0700 (MST) Date: Thu, 18 Dec 2003 12:55:35 -0700 From: Grant Grundler To: Matthew Wilcox , Christoph Hellwig , parisc-linux@lists.parisc-linux.org, vserver@list.linux-vserver.org Subject: Re: [Vserver] Re: [parisc-linux] syscall number for vserver Message-ID: <20031218195535.GA12591@colo.lackof.org> References: <20031217221618.GC9313@MAIL.13thfloor.at> <20031218072506.GA8142@lst.de> <20031218150129.GA792@MAIL.13thfloor.at> <20031218160450.GJ15674@parcelfarce.linux.theplanet.co.uk> <20031218162809.GA2605@MAIL.13thfloor.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20031218162809.GA2605@MAIL.13thfloor.at> Cc: List-Id: parisc-linux developers list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, Dec 18, 2003 at 05:28:09PM +0100, Herbert Poetzl wrote: > personally, I believe that the whole syscall number > allocation per architecture is broken by design, No it's definitely not. Binary compatibility with other OS's is an arch specific problem. In our case, any chance of support for HPUX would require reserving HPUX syscall numbers and provide appropriate wrappers in the kernel to support it. And I don't see why the value of a syscall matters. Just use the right header files and it should work on any arch. grant