X-Spam-Check-By: sourceware.org
Date: Mon, 8 Jan 2007 15:12:08 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: NTSEC documentation
Message-ID: <20070108141208.GB23638@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20070108101835 DOT GA23069 AT calimero DOT vinschen DOT de> <023f01c73320$96617d50$a501a8c0 AT CAM DOT ARTIMI DOT COM> <20070108135330 DOT GA23638 AT calimero DOT vinschen DOT de> <20070108135925 DOT GA8766 AT trixie DOT casa DOT cgf DOT cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070108135925.GA8766@trixie.casa.cgf.cx>
User-Agent: Mutt/1.4.2.2i
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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

On Jan  8 08:59, Christopher Faylor wrote:
> On Mon, Jan 08, 2007 at 02:53:30PM +0100, Corinna Vinschen wrote:
> >On Jan  8 12:29, Dave Korn wrote:
> >> On 08 January 2007 10:19, Corinna Vinschen wrote:
> >> 
> >> > Is anybody here with a developer background, who likes writing
> >> > documentation?
> >> > 
> >> > If so, would this person be interested in revamping the NTSEC
> >> > documentation with my input?  It shows its age, my lacking knowledge of
> >> > the english language and it's also very strangly ordered.
> >> 
> >>   I've got some spare tuits coming up, I can do that.  Got some notes/to-dos?
> >
> >Oh cool, thanks!
> >
> >I have some vague notes for a start:
> >
> >- I wrote the NTSEC doc "going with the flow".  There are pointers to
> >  how things worked in 1.0 or changes made in Cygwin 1.1 or 1.3, which
> >  just don't make sense anymore.  One goal would be to rip these old
> >  version cruft out and give the document a structure more to the point
> >  how things actually work now, not how they worked 5 years ago.
> >
> >- Same for the artificial difference between the chapters "New setuid
> >  concept" and "Switching User Context" which just doesn't make sense
> >  anymore.  There are two ways to switch user context, with and without
> >  external token and that's what should be said.
> >
> >- Same for mentions of sexec which has been deprecated and ripped out
> >  five years ago.
> >
> >- There's a bug in the "File permissions" chapter, third paragraph.
> >  The write_sd function doesn't use BackupRead, it used to use
> >  BackupWrite and then again, it doesn't use this function anymore,
> >  but instead the native NT call NtSetSecurityObject.
> >
> >- The names of functions should be set as <command>func</command>,
> >  not by using single quotes.
> >
> >- You could fix some bad wording resp. bad usage of SGML as you see fit.
> >
> >Other than that, bug me in PM if you think something's maybe not correct
> >anymore.
> 
> Would this be a good use of the #cygwin-developers channel at freenode.net?

YES!


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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