From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] XFS / IA64 system call conflict
Date: Tue, 24 Jul 2001 00:35:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005885@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005867@msgid-missing>
>>>>> On Tue, 24 Jul 2001 10:30:18 +1000, Keith Owens <kaos@melbourne.sgi.com> said:
Keith> Do you take care of glibc as well? That is where the problem
Keith> tends to occur.
glibc is a *user* of the kernel's system call numbers, so I don't see
how this could create a problem. Perhaps you're worried about the
name of the libc system call?
Keith> In any case the XFS syscalls are for the SGI version of ACLs.
Keith> There are other projects working on ACLs, until there is
Keith> agreement about the ACL syscall interface, the XFS numbers
Keith> cannot be considered to be permanent. So yes, we are on our
Keith> own for the moment.
Fine by me provided you make sure that the users of XFS understand
that. It does sound though that it would be premature to recommend
widespread use of XFS at this time.
--david
next prev parent reply other threads:[~2001-07-24 0:35 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
2001-07-24 0:35 ` David Mosberger [this message]
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-105590693005885@msgid-missing \
--to=davidm@hpl.hp.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