From 138f3e0cbdd1f2574963c2134f894a241fd1f348 Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Mon, 2 May 2011 11:56:36 +0000 Subject: [PATCH] Throughout remove NT4 from documentation. * new-features.sgml (ov-new1.7.10): Document change in passwd command. --- winsup/doc/ChangeLog | 6 ++++++ winsup/doc/effectively.sgml | 13 ++++++------- winsup/doc/faq-using.xml | 2 +- winsup/doc/faq-what.xml | 9 ++++----- winsup/doc/new-features.sgml | 5 +++++ winsup/doc/ntsec.sgml | 17 ++++++----------- winsup/doc/overview.sgml | 2 +- winsup/doc/pathnames.sgml | 11 +++++------ 8 files changed, 34 insertions(+), 31 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 7ea9dbf2c..3d823d65e 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,9 @@ +2011-05-02 Corinna Vinschen + + Throughout remove NT4 from documentation. + + * new-features.sgml (ov-new1.7.10): Document change in passwd command. + 2011-04-18 Corinna Vinschen * new-features.sgml (ov-new1.7.10): Document ppoll. diff --git a/winsup/doc/effectively.sgml b/winsup/doc/effectively.sgml index 73d9d2847..6f55266da 100644 --- a/winsup/doc/effectively.sgml +++ b/winsup/doc/effectively.sgml @@ -18,13 +18,12 @@ support the /? switch to display usage information. Unfortunately, no standard set of tools included with all versions of Windows exists. If you are unfamiliar with the tools available -on your system, here is a general guide. Windows NT 4.0 has only a basic -set of tools, which later versions of Windows expanded. -Microsoft also provides free downloads for Windows NT 4.0 (the Resource Kit -Support Tools), Windows 2000 (the Resource Kit Tools), and XP (the -Windows Support Tools). Generally, the younger the Windows version, the -more complete are the on-board tools. Additionally, many independent sites -such as +on your system, here is a general guide. Windows 2000 has only a basic +set of tools, which later versions of Windows expanded. Microsoft also +provides free downloads for Windows 2000 (the Resource Kit Tools), and XP +(the Windows Support Tools). Generally, the younger the Windows version, +the more complete are the on-board tools. Additionally, many independent +sites such as download.com, simtel.net, and Microsoft's own diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index f013703b0..b84fd0aad 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1093,7 +1093,7 @@ don't fully support all features of IPv6. There's also a very experimental IPv6 stack for Windows 2000, and Cygwin will try its best to support it, but it's not recommended to install -it. Windows NT4 or older never saw IPv6 at all. +it. For more information about IPv6 on Windows and how to install the IPv6 stack, see the Microsoft TechNet IPv6 FAQ article diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index 787062c7f..7ba231744 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -27,11 +27,10 @@ sad reason. Cygwin can be expected to run on all modern 32 bit versions of -Windows, except Windows CE and Windows 95/98/Me. This includes, as of the -time of writing this, Windows NT4 SP4 or later, Windows 2000, Windows XP, -Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, as well -as the WOW64 32 bit environment on released 64 bit versions of Windows -(XP/2003/Vista/2008/7/2008 R2). +Windows This includes, as of the time of writing this, Windows 2000, +Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, +Windows 7, as well as the WOW64 32 bit environment on released 64 bit +versions of Windows (XP/2003/Vista/2008/7/2008 R2). As far as we know no one is working on a native 64 bit version of Cygwin. Since Cygwin is a community-supported free software project, patches to provide support for other versions would be thoughtfully considered. diff --git a/winsup/doc/new-features.sgml b/winsup/doc/new-features.sgml index 4147ef981..aace03ca5 100644 --- a/winsup/doc/new-features.sgml +++ b/winsup/doc/new-features.sgml @@ -8,6 +8,11 @@ Drop support for Windows NT4. + +The passwd command now allows an administrator to use the -R command for +other user accounts: passwd -R username. + + Pthread spinlocks. New APIs: pthread_spin_destroy, pthread_spin_init, pthread_spin_lock, pthread_spin_trylock, pthread_spin_unlock. diff --git a/winsup/doc/ntsec.sgml b/winsup/doc/ntsec.sgml index 8484b9f51..0bacdb46e 100644 --- a/winsup/doc/ntsec.sgml +++ b/winsup/doc/ntsec.sgml @@ -436,11 +436,10 @@ deny ACEs. The second rule is not modified to get the ACEs in the preferred order. Unfortunately the security tab in the file properties dialog of -the Windows NT4 explorer is completely unable to deal with access denied ACEs -while the Windows 2000 and later properties dialog rearranges the order of the -ACEs to canonical order before you can read them. Thank God, the sort -order remains unchanged if one presses the Cancel button. But don't -even think of pressing OK... +the Windows Explorer insists to rearrange the order of the ACEs to +canonical order before you can read them. Thank God, the sort order +remains unchanged if one presses the Cancel button. But don't even +think of pressing OK... Canonical ACLs are unable to reflect each possible combination of POSIX permissions. Example: @@ -498,8 +497,8 @@ OthersAllow: 110 Again: This works on all existing versions of Windows NT, at the -time of writing from at least NT4 up to Server 2008 R2. Only the GUIs -aren't able (or willing) to deal with that order. +time of writing from at least Windows 2000 up to Server 2008 R2. Only +the GUIs aren't able (or willing) to deal with that order. @@ -703,10 +702,6 @@ bash$ grep foo //server/share/foofile Switching the user context without password, Method 2: LSA authentication package -Caveat: The method described in this chapter only works starting -with Windows 2000. Windows NT4 users have to use one of the other -methods described in this document. - We're looking for another way to switch the user context without having to provide the password. Another technique is to create an LSA authentication package. LSA is an acronym for "Local Security Authority" diff --git a/winsup/doc/overview.sgml b/winsup/doc/overview.sgml index 4f7ef3a3e..3dce16707 100644 --- a/winsup/doc/overview.sgml +++ b/winsup/doc/overview.sgml @@ -8,7 +8,7 @@ Cygwin is a Linux-like environment for Windows. It consists of a DLL providing substantial POSIX (Portable Operating System Interface) system call functionality, and a collection of tools, which provide a Linux look and feel. The Cygwin DLL -works with all x86 and AMD64 versions of Windows NT since Windows NT 4. +works with all x86 and AMD64 versions of Windows NT since Windows 2000. The API follows the Single Unix Specification as much as possible, and then Linux practice. diff --git a/winsup/doc/pathnames.sgml b/winsup/doc/pathnames.sgml index e282cfb35..3ad200b7c 100644 --- a/winsup/doc/pathnames.sgml +++ b/winsup/doc/pathnames.sgml @@ -630,12 +630,11 @@ HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitive to 0 and reboot the machine. For least surprise, Cygwin expects -this registry value also on Windows NT4 and Windows 2000, which usually -both don't know this registry key. If you want case-sensitivity on these -systems, create that registry value and set it to 0. On these systems -(and only on these systems) you don't have to reboot to bring it -into effect, rather stopping all Cygwin processes and then restarting them -is sufficient. +this registry value also on Windows 2000, which usually doesn't know this +registry key. If you want case-sensitivity on Windows 2000, just create +that registry value and set it to 0. Only +on Windows 2000 you don't have to reboot to bring it into effect, rather +stopping all Cygwin processes and then restarting them is sufficient.