From: Grant Grundler <grundler@parisc-linux.org>
To: Matthew Wilcox <willy@debian.org>, Christoph Hellwig <hch@lst.de>,
parisc-linux@lists.parisc-linux.org,
vserver@list.linux-vserver.org
Subject: Re: [Vserver] Re: [parisc-linux] syscall number for vserver
Date: Thu, 18 Dec 2003 12:55:35 -0700 [thread overview]
Message-ID: <20031218195535.GA12591@colo.lackof.org> (raw)
In-Reply-To: <20031218162809.GA2605@MAIL.13thfloor.at>
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
next prev parent reply other threads:[~2003-12-18 19:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 22:16 [parisc-linux] syscall number for vserver Herbert Poetzl
2003-12-18 7:25 ` Christoph Hellwig
2003-12-18 7:25 ` Christoph Hellwig
2003-12-18 15:01 ` [Vserver] " Herbert Poetzl
2003-12-18 15:01 ` Herbert Poetzl
2003-12-18 16:04 ` Matthew Wilcox
2003-12-18 16:28 ` Herbert Poetzl
2003-12-18 19:55 ` Grant Grundler [this message]
2003-12-19 1:00 ` Herbert Poetzl
2003-12-19 2:03 ` Grant Grundler
2003-12-19 2:03 ` Grant Grundler
2003-12-19 3:24 ` Herbert Poetzl
2003-12-19 16:11 ` Grant Grundler
2003-12-19 17:03 ` Herbert Poetzl
2003-12-19 17:03 ` Herbert Poetzl
2003-12-20 1:51 ` Grant Grundler
2003-12-20 1:54 ` Herbert Poetzl
2003-12-20 1:54 ` Herbert Poetzl
2003-12-20 1:51 ` Grant Grundler
2003-12-19 16:11 ` Grant Grundler
2003-12-19 3:24 ` Herbert Poetzl
2003-12-19 1:00 ` Herbert Poetzl
2003-12-18 19:55 ` Grant Grundler
2003-12-18 16:28 ` Herbert Poetzl
2003-12-18 16:04 ` Matthew Wilcox
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=20031218195535.GA12591@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=hch@lst.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=vserver@list.linux-vserver.org \
--cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.