From: Stephen Lord <lord@sgi.com>
To: Andries.Brouwer@cwi.nl
Cc: kaos@ocs.com.au, a.gruenbacher@computer.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com
Subject: Re: system call documentation
Date: 02 Feb 2003 09:25:21 -0600 [thread overview]
Message-ID: <1044199525.1372.8.camel@localhost.localdomain> (raw)
In-Reply-To: <UTC200302011645.h11GjTX02579.aeb@smtp.cwi.nl>
On Sat, 2003-02-01 at 10:45, Andries.Brouwer@cwi.nl wrote:
> From kaos@ocs.com.au Sat Feb 1 14:22:31 2003
>
> >Preparing the next man page release, I compared the list of
> >system calls for i386 in 2.4.20 with the list of documented
> >system calls. It looks like
> >
> >fgetxattr,
> > ...
> >are undocumented so far.
>
> *xattr* man pages are in the XFS tree and Andreas Gruenbacher's site,
> contents forwarded under separate copy.
>
> getxattr.2: getxattr, lgetxattr, fgetxattr2
> listxattr.2: listxattr, llistxattr, flistxattr
> removexattr.2: removexattr, lremovexattr, fremovexattr
> setxattr.2: setxattr, lsetxattr, fsetxattr
>
> Good. Thanks!
>
> However,
>
> .\" (C) Andreas Gruenbacher, February 2001
> .\" (C) Silicon Graphics Inc, September 2001
>
> there is no indication that redistribution (of possibly modified
> copies) is permitted.
>
> Andries
>
>
There should be no problem with redistribution, I can probably get
someone to update them soon. I presume Andreas will also have no
problems with this.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@sgi.com
next prev parent reply other threads:[~2003-02-02 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 16:45 system call documentation Andries.Brouwer
2003-02-02 15:25 ` Stephen Lord [this message]
2003-02-02 15:40 ` system call documentation [license question] Andreas Gruenbacher
-- strict thread matches above, loose matches on Subject: below --
2003-02-01 13:05 system call documentation Andries.Brouwer
2003-02-01 13:22 ` Keith Owens
2003-02-03 18:42 ` Mark Fasheh
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=1044199525.1372.8.camel@localhost.localdomain \
--to=lord@sgi.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=a.gruenbacher@computer.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/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