From 3f6e3c0ff5c5c9389f2b98ca64b0a96f38c44bd7 Mon Sep 17 00:00:00 2001 From: joshuadfranklin Date: Wed, 23 Oct 2002 04:29:46 +0000 Subject: [PATCH] * ntsec.sgml: Correct some minor grammatical errors. --- winsup/doc/ChangeLog | 4 ++++ winsup/doc/ntsec.sgml | 21 +++++++++++---------- 2 files changed, 15 insertions(+), 10 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index abced3172c..abec5fe43a 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,5 +1,9 @@ 2002-10-22 Joshua Daniel Franklin + * ntsec.sgml: Correct some minor grammatical errors. + +2002-10-22 Joshua Daniel Franklin + * dll.sgml: Simplify dll build instructions. 2002-09-11 Corinna Vinschen diff --git a/winsup/doc/ntsec.sgml b/winsup/doc/ntsec.sgml index b6982335f0..54deaf16d3 100644 --- a/winsup/doc/ntsec.sgml +++ b/winsup/doc/ntsec.sgml @@ -130,8 +130,8 @@ set The two important types of ACEs are the `access allowed ACE' and the `access denied ACE'. The ntsec patch only used `access allowed ACEs' up -to Cygwin version 1.1.0. Later versions use `access denied ACEs' as well -to reflect the UNIX permissions as good as possible. +to Cygwin version 1.1.0. Later versions also use `access denied ACEs' +to reflect the UNIX permissions as well as possible. The possible permissions on objects are more detailed than in UNIX. For example, the permission to delete an object is different @@ -232,9 +232,9 @@ well known group with different naming in local systems and domains. Outside of domains the group is named 'None' (`Kein' in German, `Aucun' in French, etc.), in domains it is named 'Domain Users'. Unfortunately, the group `None' is never shown in the user admin tool outside of domains! -This is very confusing but it seems that this has no negativ influences. +This is very confusing but this seems to have no negative consequences. -To work correctly the ntsec patch depends on reasoned files +To work correctly the ntsec patch depends on the files /etc/passwd/ and /etc/group. In cygwin release 1.0 the names and the IDs must correspond to the appropriate NT IDs! The IDs used in cygwin are the RID of the NT SID, as @@ -257,7 +257,7 @@ have to change the primary group by hand if `None' as primary group is not what you want (and I'm sure, it's not what you want!) Look at the following examples, which were parts of my files before -storing SIDs in /etc/passwd and /etc/group has been introduced (See next +storing SIDs in /etc/passwd and /etc/group had been introduced (See next chapter for details). With the exception of my personal user entry, all entries are well known entries. @@ -286,15 +286,15 @@ powerusers::547: -As you can see, I've changed my primary group membership from 513 (None) -to 547 (powerusers). So all file I created inside of Cygwin were now owned +As you can see, I changed my primary group membership from 513 (None) +to 547 (powerusers). So all files I created inside of Cygwin were now owned by the powerusers group instead of None. This is the way I liked it. Groups may be mentioned in the passwd file, too. This has two advantages: Because NT assigns them to files as owners, a -ls -l is often better readable. +ls -l is often more readable. Moreover it's possible to assigned them to files as owners with cygwin's chown. @@ -593,11 +593,12 @@ permissions: "Increase quotas" -Note that administrators do not have all that user rights set by default. +Note that administrators do not have all these user rights set +by default. Two new Cygwin calls are introduced to support porting setuid applications with a minimum of effort. You only -have to care to give Cygwin the right access token and then you can call +give Cygwin the right access token and then you can call seteuid or setuid as usual in POSIX applications. The call to sexec is not needed anymore. Porting a setuid application is illustrated by -- 2.11.0