This is the mail archive of the
cygwin-cvs@cygwin.com
mailing list for the Cygwin project.
[newlib-cygwin] Remove XP and Server 2003 from documentation
- From: Corinna Vinschen <corinna at sourceware dot org>
- To: cygwin-cvs at sourceware dot org
- Date: 24 Jun 2016 21:39:30 -0000
- Subject: [newlib-cygwin] Remove XP and Server 2003 from documentation
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=54c284caf2851666cc9431f2fd544d19148ac89a
commit 54c284caf2851666cc9431f2fd544d19148ac89a
Author: Corinna Vinschen <corinna@vinschen.de>
Date: Fri Jun 24 23:21:10 2016 +0200
Remove XP and Server 2003 from documentation
Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
Diff:
---
winsup/doc/cygwinenv.xml | 4 +---
winsup/doc/effectively.xml | 3 +--
winsup/doc/faq-setup.xml | 36 ++++++++++++++++++------------------
winsup/doc/faq-using.xml | 26 +++-----------------------
winsup/doc/faq-what.xml | 8 ++++----
winsup/doc/highlights.xml | 12 +++---------
winsup/doc/ntsec.xml | 39 ++++++++++++++++++---------------------
winsup/doc/setup-locale.xml | 19 ++++++++++++-------
winsup/doc/specialnames.xml | 8 ++++----
winsup/doc/utils.xml | 16 ++++++++--------
10 files changed, 72 insertions(+), 99 deletions(-)
diff --git a/winsup/doc/cygwinenv.xml b/winsup/doc/cygwinenv.xml
index 5fadaee..ec98414 100644
--- a/winsup/doc/cygwinenv.xml
+++ b/winsup/doc/cygwinenv.xml
@@ -95,9 +95,7 @@ the R/O attribute set.</para>
<para>If set to <literal>winsymlinks:native</literal> or
<literal>winsymlinks:nativestrict</literal>, Cygwin creates symlinks as
-native Windows symlinks on filesystems and OS versions supporting them.
-If the OS is known not to support native symlinks (Windows XP, Windows
-Server 2003), a warning message is produced once per session.</para>
+native Windows symlinks on filesystems and OS versions supporting them.</para>
<para>The difference between <literal>winsymlinks:native</literal> and
<literal>winsymlinks:nativestrict</literal> is this: If the filesystem
diff --git a/winsup/doc/effectively.xml b/winsup/doc/effectively.xml
index cb25628..f0d6547 100644
--- a/winsup/doc/effectively.xml
+++ b/winsup/doc/effectively.xml
@@ -22,8 +22,7 @@ support the <literal>/?</literal> switch to display usage information.
<para>
Unfortunately, no standard set of tools included with all versions of
Windows exists. Generally, the younger the Windows version, the more
-complete are the on-board tools. Microsoft also provides free downloads
-for Windows XP (the Windows Support Tools). Additionally, many independent
+complete are the on-board tools. Additionally, many independent
sites such as
<ulink url="http://download.com";>download.com</ulink>,
<ulink url="http://simtel.net";>simtel.net</ulink>,
diff --git a/winsup/doc/faq-setup.xml b/winsup/doc/faq-setup.xml
index 89ec00d..a790974 100644
--- a/winsup/doc/faq-setup.xml
+++ b/winsup/doc/faq-setup.xml
@@ -588,24 +588,24 @@ editing the registry and restoring
back to it's original value of <literal>msv1_0</literal>, and then rebooting.
</para>
</listitem>
-<listitem><para>Delete the Cygwin root folder and all subfolders. If you get an error
-that an object is in use, then ensure that you've stopped all services and
-closed all Cygwin programs. If you get a 'Permission Denied' error then you
-will need to modify the permissions and/or ownership of the files or folders
-that are causing the error. For example, sometimes files used by system
-services end up owned by the SYSTEM account and not writable by regular users.
-</para>
-<para>The quickest way to delete the entire tree if you run into this problem is to
-change the ownership of all files and folders to your account. To do this in
-Windows Explorer, right click on the root Cygwin folder, choose Properties, then
-the Security tab. If you are using Windows XP Home or Simple File Sharing,
-you will need to boot into Safe Mode to access the Security tab. Select
-Advanced, then go to the Owner tab and make sure your account is listed as
-the owner. Select the 'Replace owner on subcontainers and objects' checkbox
-and press Ok. After Explorer applies the changes you should be able to
-delete the entire tree in one operation. Note that you can also achieve
-this in Cygwin by typing <literal>chown -R user /</literal> or by using other
-tools such as <literal>CACLS.EXE</literal>.
+<listitem><para>Delete the Cygwin root folder and all subfolders. If you get
+an error that an object is in use, then ensure that you've stopped all services
+and closed all Cygwin programs. If you get a 'Permission Denied' error then
+you will need to modify the permissions and/or ownership of the files or
+folders that are causing the error. For example, sometimes files used by
+system services end up owned by the SYSTEM account and not writable by regular
+users.</para>
+<para>The quickest way to delete the entire tree if you run into this problem
+is to change the ownership of all files and folders to your account. To do
+this in Windows Explorer, right click on the root Cygwin folder, choose
+Properties, then the Security tab. If you are using Simple File Sharing, you
+will need to boot into Safe Mode to access the Security tab. Select Advanced,
+then go to the Owner tab and make sure your account is listed as the owner.
+Select the 'Replace owner on subcontainers and objects' checkbox and press Ok.
+After Explorer applies the changes you should be able to delete the entire tree
+in one operation. Note that you can also achieve this in Cygwin by typing
+<literal>chown -R user /</literal> or by using other tools such as
+<literal>icacls.exe</literal>.
</para>
</listitem>
<listitem><para>Delete the Cygwin shortcuts on the Desktop and Start Menu, and
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index 412dfbb..415b8a5 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -724,9 +724,9 @@ the following line to your .inputrc file:
<answer>
<para>We have had good reports about Kerio Personal Firewall, ZoneLabs
-Integrity Desktop, and the built-in firewall in Windows XP. Other
-well-known products including ZoneAlarm and Norton Internet Security have
-caused problems for some users but work fine for others. At last report,
+Integrity Desktop, and the Windows built-in firewall. Other well-known
+products including ZoneAlarm and Norton Internet Security have caused
+problems for some users but work fine for others. At last report,
Agnitum Outpost did not work with Cygwin. If you are having strange
connection-related problems, disabling the firewall is a good
troubleshooting step (as is closing or disabling all other running
@@ -1248,26 +1248,6 @@ includes an X server; please see the <ulink url="https://x.cygwin.com/docs/ug/cy
for installation and startup instructions.
</para></answer></qandaentry>
-<qandaentry id="faq.using.ipv6">
-<question><para>Why do I get "Address family not supported" errors when playing with IPv6?</para></question>
-<answer>
-
-<para>IPv6 is only fully supported and available right from the start
-beginning with Windows Vista and Windows Server 2008.</para>
-
-<para>The previous generation of Windows,
-Windows XP and Windows Server 2003, only support IPv6 on an "experimental"
-basis. On these Windows versions, the IPv6 TCP/IP stack is not installed
-automatically, rather the system administrator has to install it manually.
-Unless this has already been done on your machine, your machine is not
-IPv6-capable and that's why you see the "Address family not supported"
-error message. Note, however, that the IPv6 stack on these systems
-don't fully support all features of IPv6.</para>
-
-<para>For more information about IPv6 on Windows and how to install the
-IPv6 stack, see the <ulink url="http://www.microsoft.com/technet/network/ipv6/ipv6faq.mspx";>Microsoft TechNet IPv6 FAQ article</ulink>
-</para></answer></qandaentry>
-
<qandaentry id="faq.using.bloda" xreflabel="BLODA">
<question><para>What applications have been found to interfere with Cygwin?</para></question>
<answer>
diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml
index 393516a..e71cada 100644
--- a/winsup/doc/faq-what.xml
+++ b/winsup/doc/faq-what.xml
@@ -31,11 +31,11 @@ They can be used from one of the provided Unix shells like bash, tcsh or zsh.
<answer>
<para>Cygwin can be expected to run on all modern, released versions of Windows.
-State January 2015 this includes Windows XP SP3, Windows Server 2003/2003R2
-and all later versions of Windows up to Windows 8.1 and Windows Server 2012R2.
+State January 2016 this includes Windows Vista, Windows Server 2008 and all
+later versions of Windows up to Windows 10 and Windows Server 2016.
The 32 bit version of Cygwin also runs in the WOW64 32 bit environment on
-released 64 bit versions of Windows (XP SP3 up to 8.1/2012R2), the 64 bit
-version of course only on 64 bit Windows.
+released 64 bit versions of Windows, the 64 bit version of course only on
+64 bit Windows.
</para>
<para>Keep in mind that Cygwin can only do as much as the underlying OS
supports. Because of this, Cygwin will behave differently, and
diff --git a/winsup/doc/highlights.xml b/winsup/doc/highlights.xml
index 65407ab..05e6829 100644
--- a/winsup/doc/highlights.xml
+++ b/winsup/doc/highlights.xml
@@ -109,9 +109,9 @@ Instead, they can do the same path translations by executing the
<para>Win32 applications handle filenames in a case preserving, but case
insensitive manner. Cygwin supports case sensitivity on file systems
-supporting that. Since Windows XP, the OS only supports case
-sensitivity when a specific registry value is changed. Therefore, case
-sensitivity is not usually the default.</para>
+supporting that. Windows only supports case sensitivity when a specific
+registry value is changed. Therefore, case sensitivity is not usually the
+default.</para>
<para>Cygwin supports creating and reading symbolic links, even on Windows
filesystems and OS versions which don't support them.
@@ -346,12 +346,6 @@ completely transparent to the application. Cygwin's implementation also
supports the getpeereid BSD extension. However, Cygwin does not yet support
descriptor passing.</para>
-<para>IPv6 is supported. This support is dependent, however, on the
-availability of the Windows IPv6 stack. The IPv6 stack was "experimental",
-i.e. not feature complete in Windows 2003 and earlier. Full IPv6 support
-became only available starting with Windows Vista and Windows Server 2008.
-</para>
-
</sect2>
<sect2 id="ov-hi-select"><title>Select</title>
diff --git a/winsup/doc/ntsec.xml b/winsup/doc/ntsec.xml
index ae0a119..df1d549 100644
--- a/winsup/doc/ntsec.xml
+++ b/winsup/doc/ntsec.xml
@@ -1340,8 +1340,8 @@ schemata are the following:
<term><literal>unix</literal></term>
<listitem>Utilizes the posixAccount schema attributes per
<ulink url="https://tools.ietf.org/html/rfc2307";>RFC 2307</ulink>.
- The posixAccount schema is available by default since Windows
- Server 2003 R2, but typically only utilized when installing the
+ The posixAccount schema is available by default in Windows
+ Server, but typically only utilized when installing the
Active Directory "Server for NIS" feature (which is deprecated
since Server 2012 R2).
See also <xref linkend="ntsec-mapping-nsswitch-posix"></xref>.
@@ -1759,10 +1759,10 @@ The group attributes utilized by Cygwin are:
<para>
The <literal>unix</literal> schema utilizes the
<literal>posixAccount</literal> attribute extension. This is one of two
-schema extensions which are connected to AD accounts, available by default
-starting with Windows Server 2003 R2. They are usually
-<emphasis role='bold'>not set</emphasis>, unless used by the Active Directory
-<literal>Server for NIS</literal> feature (deprecated since Server 2012 R2).
+schema extensions which are connected to AD accounts, available by default.
+They are usually <emphasis role='bold'>not set</emphasis>, unless used by
+the Active Directory <literal>Server for NIS</literal> feature (deprecated
+since Server 2012 R2).
Two schemata are interesting for Cygwin, <literal>posixAccount</literal>,
connected to user accounts, and <literal>posixGroup</literal>, connected
@@ -2216,20 +2216,18 @@ GroupAllow: 001
OthersAllow: 110
</screen>
-<para>Again: This works on all existing versions of Windows NT, at the
-time of writing from at least Windows XP up to Server 2012 R2. Only
-the GUIs aren't able (or willing) to deal with that order.</para>
+<para>Again: This works on all supported versions of Windows. Only the GUIs
+aren't able (or willing) to deal with that order.</para>
</sect2>
<sect2 id="ntsec-setuid-overview"><title id="ntsec-setuid-overview.title">Switching the user context</title>
-<para>Since Windows XP, Windows users have been accustomed to the
-"Switch User" feature, which switches the entire desktop to another user
-while leaving the original user's desktop "suspended". Another Windows
-feature is the "Run as..." context menu entry, which allows you to start
-an application using another user account when right-clicking on applications
-and shortcuts.</para>
+<para>Windows users have been accustomed to the "Switch User" feature, which
+switches the entire desktop to another user while leaving the original user's
+desktop "suspended". Another Windows feature is the "Run as..." context menu
+entry, which allows you to start an application using another user account
+when right-clicking on applications and shortcuts.</para>
<para>On POSIX systems, this operation can be performed by processes
running under the privileged user accounts (usually the "root" user
@@ -2357,9 +2355,8 @@ the user context (<command>sshd</command>, <command>inetd</command>,
Unfortunately that's too simple. Using <command>NtCreateToken</command>
has a few drawbacks.</para>
-<para>First of all, beginning with Windows Server 2003,
-the permission "Create a token object" gets explicitly removed from
-the SYSTEM user's access token, when starting services under that
+<para>First of all, the permission "Create a token object" gets explicitly
+removed from the SYSTEM user's access token, when starting services under that
account. That requires us to create a new account with this specific
permission just to run this kind of services. But that's a minor
problem.</para>
@@ -2373,9 +2370,9 @@ identify the user domain and user name not by the SID of the access
token owner, but only by the logon session the process is running under.</para>
<para>This has the following unfortunate consequence. Consider a
-service started under the SYSTEM account (up to Windows XP) switches the
-user context to DOMAIN\my_user using a token created directly by calling
-the <command>NtCreateToken</command> function. A process running under
+service started under the SYSTEM account switches the user context to
+DOMAIN\my_user using a token created directly by calling the
+<command>NtCreateToken</command> function. A process running under
this new access token might want to know under which user account it's
running. The corresponding SID is returned correctly, for instance
S-1-5-21-1234-5678-9012-77777. However, if the same process asks the OS
diff --git a/winsup/doc/setup-locale.xml b/winsup/doc/setup-locale.xml
index ebde7a2..29502a2 100644
--- a/winsup/doc/setup-locale.xml
+++ b/winsup/doc/setup-locale.xml
@@ -305,13 +305,18 @@ environment, if it's different from the UTF-8 charset.</para>
consist of valid ASCII characters, and only of uppercase letters, digits, and
the underscore for maximum portability.</para></note>
-<para>Another problem you might encounter is that older versions of
-Windows did not install all charsets by default. If you are running
-Windows XP or 2003, you can open the "Regional and Language Options"
-portion of the Control Panel, select the "Advanced" tab, and select
-entries from the "Code page conversion tables" list. The following
-entries are useful to cygwin: 932/SJIS, 936/GBK, 949/EUC-KR, 950/Big5,
-20932/EUC-JP.</para>
+<para>Very old symbolic links may pose a problem when switching charsets on
+the fly. A symbolic link contains the filename of the target file the
+symlink points to. When a symlink had been created with versions of Cygwin
+prior to Cygwin 1.7, the current ANSI or OEM character set had been used to
+store the target filename, dependent on the old <envar>CYGWIN</envar>
+environment variable setting <envar>codepage</envar> (see <xref
+linkend="cygwinenv-removed-options"></xref>. If the target filename
+contains non-ASCII characters and you use another character set than
+your default ANSI/OEM charset, the target filename of the symlink is now
+potentially an invalid character sequence in the new character set.
+This behaviour is not different from the behaviour in other Operating
+Systems. Recreate the symlink if that happens to you.</para>
</sect2>
diff --git a/winsup/doc/specialnames.xml b/winsup/doc/specialnames.xml
index d67d484..0192fc2 100644
--- a/winsup/doc/specialnames.xml
+++ b/winsup/doc/specialnames.xml
@@ -153,10 +153,10 @@ characters.</para>
case-sensitive. You can't access two files in the same directory which
only differ by case, like <filename>Abc</filename> and
<filename>aBc</filename>. While NTFS (and some remote filesystems)
-support case-sensitivity, the NT kernel starting with Windows XP does
-not support it by default. Rather, you have to tweak a registry setting
-and reboot. For that reason, case-sensitivity can not be supported by Cygwin,
-unless you change that registry value.</para>
+support case-sensitivity, the NT kernel does not support it by default.
+Rather, you have to tweak a registry setting and reboot. For that reason,
+case-sensitivity can not be supported by Cygwin, unless you change that
+registry value.</para>
<para>If you really want case-sensitivity in Cygwin, you can switch it
on by setting the registry value</para>
diff --git a/winsup/doc/utils.xml b/winsup/doc/utils.xml
index 8c5a619..08a24f7 100644
--- a/winsup/doc/utils.xml
+++ b/winsup/doc/utils.xml
@@ -817,14 +817,14 @@ Other options:
command in scripts to set the POSIX locale variables.</para>
<para>The <literal>-u</literal> option prints the current user's Windows UI
- locale to stdout. In Windows Vista and Windows 7 this setting is called
- the "Display Language"; there was no corresponding user setting in
- Windows XP. The <literal>-s</literal> option prints the systems default
- instead. The <literal>-f</literal> option prints the user's setting for
- time, date, number and currency. That's equivalent to the setting in the
- "Formats" or "Regional Options" tab in the "Region and Language" or
- "Regional and Language Options" dialog. With the <literal>-U</literal>
- option <command>locale</command> appends a ".UTF-8".</para>
+ locale to stdout. In Windows this setting is called the
+ "Display Language". The <literal>-s</literal> option prints the systems
+ default instead. The <literal>-f</literal> option prints the user's
+ setting for time, date, number and currency. That's equivalent to the
+ setting in the "Formats" or "Regional Options" tab in the "Region and
+ Language" or "Regional and Language Options" dialog. With the
+ <literal>-U</literal> option <command>locale</command> appends a
+ ".UTF-8".</para>
<para>Usage example:</para>