Return-Path: owner-linux-doc@vger.rutgers.edu
Received: from kantti.helsinki.fi (root@kantti.Helsinki.FI [128.214.4.16]) by keos.cs.Helsinki.FI (8.6.10/H46) with ESMTP id RAA22790 for <wirzeniu@cs.Helsinki.FI>; Sun, 23 Jul 1995 17:32:26 +0300
Received: from vger.rutgers.edu (majordomo@vger.rutgers.edu [128.6.190.2]) by kantti.helsinki.fi (8.6.12+Emil1.1/8.6.5) with SMTP id RAA07635 for <wirzeniu@cc.helsinki.fi>; Sun, 23 Jul 1995 17:32:24 +0300
Received: (from majordomo@localhost) by vger.rutgers.edu (8.6.12/8.6.12) id IAA21202 for linux-doc-outgoing; Sun, 23 Jul 1995 08:49:48 -0400
Date: Sun, 23 Jul 1995 07:47:48 -0500
From: Michael Elizabeth Chastain <mec@duracef.shout.net>
Message-Id: <199507231247.HAA10607@duracef.shout.net>
To: linux-doc@vger.rutgers.edu
Subject: Re: What man pages is missing from section 3?
Sender: owner-linux-doc@vger.rutgers.edu
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Length: 571
Status: RO
X-Status: 

Daniel Quinlan (quinlan@best.com) writes:

> Start writing pages for the undocumented system calls in section 2.
> Get version 1.6 of the Linux manual pages and check undocumented(2).

Andries Brouwer just released man pages 1.7, so go for that.

Also there are some old section 2 pages which do not match reality.
mmap(2) comes to mind.  I bet flock(2) has some discrepancies too, and
some of the sig*(2) pages.

Linux/alpha has some new system calls not present in Linux/i386.
Is there a documentation policy in place for them?

Michael Chastain
mec@duracef.shout.net


.