X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	RE: Looking for man pages
Date:	Thu, 28 Jun 2007 15:38:47 -0400
Message-ID:	<FF8482A96323694490C194BABEAC24A0011F1E57@Email.cbord.com>
In-Reply-To:	<46840973.BD68B5A4@dessent.net>
References:	<FF8482A96323694490C194BABEAC24A0011F1C40 AT Email DOT cbord DOT com> <20070628180239 DOT GJ30973 AT calimero DOT vinschen DOT de> <FF8482A96323694490C194BABEAC24A0011F1DFF AT Email DOT cbord DOT com> <46840973 DOT BD68B5A4 AT dessent DOT net>
From:	"Bob McConnell" <rvm AT CBORD DOT com>
To:	<cygwin AT cygwin DOT com>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id l5SJdVWo003136

> -----Original Message-----
> From: cygwin-owner AT cygwin DOT com 
> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Brian Dessent
> Sent: Thursday, June 28, 2007 3:18 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: Looking for man pages
> 
> Bob McConnell wrote:
> 
> > I can't find any links to anything other than one sample 
> man page. We
> > already have copies of that spec, although I have never had 
> any cause to
> > read it.
> 
> Wha?  The SUSv3 is extremely thorough, consisting of many hundreds of
> man pages:
> <http://www.opengroup.org/onlinepubs/009695399/functions/conte
> nts.html>.
> 
> > What steps are involved to convert those pages?
> 
> The problem with lifting man pages from Linux is that those man pages
> document ... Linux.  Not Cygwin.
> 
> There are a number of areas where either Cygwin doesn't implement some
> extension that glibc provides, or Cygwin implements something in a
> different way, or Cygwin doesn't support particular options of a given
> API.  Just transplanting these linux-specific docs would 
> utterly confuse
> people because they'd be incorrect.  So what really needs to happen is
> that someone who is familiar with the internals of Cygwin 
> needs to adapt
> the linux documentation so that it reflects the reality of Cygwin, and
> *that* is why it's not been done.  It's not just a matter of format
> conversion or packaging.
> 
> Brian

At least that gets me to the TOC for the interface documents. I couldn't
get there from the URL Corinna gave me, unless that was accessible after
registering. A set of man pages would be much easier to use.

But you are sending me to the SUS documentation, which is also missing
those differences? That seems rather counter productive.

Are there any documents available that explain those differences, or are
they only held in the programmers' heads at this point?

Thank you,

Bob McConnell

--
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/

- Raw text -