From: Mark Fasheh <mark.fasheh@oracle.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: system call documentation
Date: Mon, 3 Feb 2003 10:42:04 -0800 [thread overview]
Message-ID: <20030203184204.GB19502@ca-server1.us.oracle.com> (raw)
In-Reply-To: <UTC200302011305.h11D5Jg24212.aeb@smtp.cwi.nl>
alloc_hugepages and free_hugepages no longer exist.
--Mark
On Sat, Feb 01, 2003 at 02:05:19PM +0100, Andries.Brouwer@cwi.nl wrote:
> 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
>
> alloc_hugepages,
> exit_group,
> fgetxattr,
> flistxattr,
> free_hugepages,
> fremovexattr,
> fsetxattr,
> getpmsg,
> get_thread_area,
> gettid,
> getxattr,
> io_cancel,
> io_destroy,
> io_getevents,
> io_setup,
> io_submit,
> lgetxattr,
> listxattr,
> llistxattr,
> lremovexattr,
> lsetxattr,
> madvise1,
> putpmsg,
> readahead,
> removexattr,
> rt_sigaction,
> rt_sigpending,
> rt_sigprocmask,
> rt_sigqueueinfo,
> rt_sigreturn,
> rt_sigsuspend,
> rt_sigtimedwait,
> security,
> set_thread_area,
> setxattr,
> tkill,
> ugetrlimit
>
> are undocumented so far. Contributed man pages are welcome.
>
> Andries
> aeb@cwi.nl
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Mark Fasheh
Software Developer, Oracle Corp
mark.fasheh@oracle.com
next prev parent reply other threads:[~2003-02-03 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 13:05 Andries.Brouwer
2003-02-01 13:22 ` Keith Owens
2003-02-03 18:42 ` Mark Fasheh [this message]
2003-02-01 16:45 Andries.Brouwer
2003-02-02 15:25 ` Stephen Lord
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=20030203184204.GB19502@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®