From: Keith Owens <kaos@melbourne.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] XFS / IA64 system call conflict
Date: Tue, 24 Jul 2001 00:30:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005884@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005867@msgid-missing>
On Mon, 23 Jul 2001 17:19:36 -0700,
David Mosberger <davidm@hpl.hp.com> wrote:
>>>>>> On Tue, 24 Jul 2001 10:16:44 +1000, Keith Owens <kaos@melbourne.sgi.com> said:
>
> Keith> There is no 'official' source for syscall numbers.
>
>Yes, there is: you send me mail, I add the respective numbers to
>unistd.h, and that's it. Anyone who messes with that protocol is on
>his/her own.
Do you take care of glibc as well? That is where the problem tends to
occur.
In any case the XFS syscalls are for the SGI version of ACLs. There
are other projects working on ACLs, until there is agreement about the
ACL syscall interface, the XFS numbers cannot be considered to be
permanent. So yes, we are on our own for the moment.
next prev parent reply other threads:[~2001-07-24 0:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 13:53 [Linux-ia64] XFS / IA64 system call conflict Martin Wilck
2001-07-23 14:07 ` Nathan Straz
2001-07-23 14:09 ` Jes Sorensen
2001-07-23 14:16 ` Keith Owens
2001-07-23 14:24 ` Keith Owens
2001-07-23 16:49 ` David Mosberger
2001-07-23 18:51 ` David Mosberger
2001-07-24 0:16 ` Keith Owens
2001-07-24 0:19 ` David Mosberger
2001-07-24 0:30 ` Keith Owens [this message]
2001-07-24 0:35 ` David Mosberger
2001-07-24 1:04 ` Keith Owens
2001-07-25 15:45 ` Jes Sorensen
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=marc-linux-ia64-105590693005884@msgid-missing \
--to=kaos@melbourne.sgi.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox