From: "Dave Korn" <dave.korn@artimi.com>
To: <cygwin@cygwin.com>
References: <47B3809B.80401@tlinx.org>
Subject: RE: "cygwin-os" & library man pages?
Date: Wed, 13 Feb 2008 23:52:26 -0000
Message-ID: <01e501c86e9b$7c741df0$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain; 	charset="utf-8"
In-Reply-To: <47B3809B.80401@tlinx.org>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On 13 February 2008 23:43, Linda Walsh wrote:

> I was trying to remember the syntax of some C functions but wasn't
> able to find man pages for things like 'exec' (and variations),
> fork (and variations)...etc.
> 
> I ended up relying on linux manpages which luckily worked, but I'd
> rather use the correct cygwin man pages so I know what calls are
> supported.
> 
> Am I missing some manpage package(s)?

  We don't really have them.  The linux manpages come from glibc, the C runtime which supplies all the functions.  We use newlib as the basic C runtime and implement the rest of POSIX in the cygwin source, and it isn't as well documented for manpower reasons.

  Having said that, of course, since our goal is to emulate a linux system, the linux manpages should be correct and any inaccuracy is more of a bug in cygwin for not matching the man page rather than an error in the man page for not describing what cygwin (rather than linux) does...


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/