Mon Jan 8 13:53:00 GMT 2007
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
Thanks in advance, I really appreciate that!
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
More information about the Cygwin