diff options
| -rw-r--r-- | winsup/doc/ChangeLog | 6 | ||||
| -rw-r--r-- | winsup/doc/faq-using.xml | 7 | ||||
| -rw-r--r-- | winsup/doc/faq-what.xml | 5 | ||||
| -rw-r--r-- | winsup/doc/new-features.sgml | 4 |
4 files changed, 15 insertions, 7 deletions
diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index a38216d69..b84c63fe8 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,9 @@ +2009-07-23 Corinna Vinschen <corinna@vinschen.de> + + * faq-using.xml (faq.using.ipv6): Try to clarify OS specific support. + * faq-what.xml (faq.what.supported): Add Windows 7 and 2008 R2. + * new-features.sgml: Add "and later" to rcmd news. + 2009-07-20 Corinna Vinschen <corinna@vinschen.de> * Makefile.in (all): Fix wrong target names. diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml index e3aad6dea..295adc156 100644 --- a/winsup/doc/faq-using.xml +++ b/winsup/doc/faq-using.xml @@ -1039,8 +1039,8 @@ elsewhere in this FAQ. <question><para>Why do I get "Address family not supported" errors when playing with IPv6?</para></question> <answer> -<para>IPv6 is fully supported and available right from the start with -Windows Vista and Windows Server 2008.</para> +<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" @@ -1048,7 +1048,8 @@ 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.</para> +error message. Note, however, that the IPv6 stack on these systems +don't fully support all features of IPv6.</para> <para>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 diff --git a/winsup/doc/faq-what.xml b/winsup/doc/faq-what.xml index 571ff3a7a..35bf9c2ca 100644 --- a/winsup/doc/faq-what.xml +++ b/winsup/doc/faq-what.xml @@ -29,8 +29,9 @@ sad reason. <para>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, Windows 2000, Windows XP, Windows Server -2003, Windows Vista, Windows Server 2008, as well as the WOW64 32 bit -environment on released 64 bit versions of Windows (XP/2003/Vista/2008). +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 8dbed99b4..d8ff414c7 100644 --- a/winsup/doc/new-features.sgml +++ b/winsup/doc/new-features.sgml @@ -145,8 +145,8 @@ this *is* the former libminires.a. - rcmd is now implemented inside of Cygwin, instead of calling the - WinSock function. This allows rsh(1) usage on Vista/2008, which - dropped this function from WinSock. + WinSock function. This allows rsh(1) usage on Vista/2008 and later, + which dropped this function from WinSock. - Define multicast structures in netinet/in.h. Note that fully conformant multicast support is only available beginning with Vista/2008. |