* faq-using.xml (faq.using.symlinkstoppedworking): Rename.

	(faq.using.ipv6): New IPv6 FAQ.
	* gdb.sgml: Remove incorrect statement about Insight.

3 files changed, 37 insertions, 11 deletions

diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog
index dd973d1..bf45cae 100644
--- a/winsup/doc/ChangeLog
+++ b/winsup/doc/ChangeLog
@@ -1,3 +1,9 @@
+2009-04-01  Corinna Vinschen  <corinna@vinschen.de>
+
+	* faq-using.xml (faq.using.symlinkstoppedworking): Rename.
+	(faq.using.ipv6): New IPv6 FAQ.
+	* gdb.sgml: Remove incorrect statement about Insight.
+
 2009-03-31  Corinna Vinschen  <corinna@vinschen.de>
 
 	* setup2.sgml (setup-locale-problems): Fix an incomplete sentence.
diff --git a/winsup/doc/faq-using.xml b/winsup/doc/faq-using.xml
index ad60438..64fee2a 100644
--- a/winsup/doc/faq-using.xml
+++ b/winsup/doc/faq-using.xml
@@ -967,7 +967,7 @@ Cygwin application providing a native GUI.
 </para>
 </answer></qandaentry>
 
-<qandaentry id="faq.api.symlinkstoppedworking">
+<qandaentry id="faq.using.symlinkstoppedworking">
 <question><para>Why do some of my old symlinks don't work anymore?</para></question>
 <answer>
 
@@ -1020,6 +1020,29 @@ Cygwin mounts or symbolic links.
 elsewhere in this FAQ.
 </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 fully supported and available right from the start 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.</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
+it.  Windows NT4 or older never saw IPv6 at all.</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">
 <question><para>What applications have been found to interfere with Cygwin?</para></question>
 <answer>
diff --git a/winsup/doc/gdb.sgml b/winsup/doc/gdb.sgml
index 2a13e2b..42d3128 100644
--- a/winsup/doc/gdb.sgml
+++ b/winsup/doc/gdb.sgml
@@ -32,17 +32,14 @@ information give your program enough information about the original
 sources so that the debugger can make debugging much easier for
 you.</para>
 
-<para>In Windows versions of GNUPro, GDB comes with a full-featured
-graphical interface.  In Cygwin Net distributions, GDB is only
-available as a command-line tool.  To invoke GDB, simply type
-<command>gdb myapp.exe</command> at the command prompt.  It will
-display some text telling you about itself, then
-<literal>(gdb)</literal> will appear to prompt you to enter commands.
-Whenever you see this prompt, it means that gdb is waiting for you to
-type in a command, like <command>run</command> or
+<para>To invoke GDB, simply type <command>gdb myapp.exe</command> at the
+command prompt.  It will display some text telling you about itself,
+then <literal>(gdb)</literal> will appear to prompt you to enter
+commands.  Whenever you see this prompt, it means that gdb is waiting
+for you to type in a command, like <command>run</command> or
 <command>help</command>.  Oh <literal>:-)</literal> type
-<command>help</command> to get help on the commands you can type in,
-or read the <citation>GDB User's Manual</citation> for a complete
+<command>help</command> to get help on the commands you can type in, or
+read the <citation>GDB User's Manual</citation> for a complete
 description of GDB and how to use it.</para>
 
 <para>If your program crashes and you're trying to figure out why it