drew
/
acadia-newlib
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* 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.
This commit is contained in:
Corinna Vinschen 2009-07-23 08:49:06 +00:00
parent 4a77fa092c
commit 07271a4b02
4 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
winsup/doc/ChangeLog
View File

@ -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.

7
winsup/doc/faq-using.xml
View File

@ -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

5
winsup/doc/faq-what.xml
View File

@ -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.

4
winsup/doc/new-features.sgml
View File

@ -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.