Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Jul 2005 16:41:14 +0200
From:      Tilman Linneweh <arved@arved.at>
To:        Giorgos Keramidas <keramida@freebsd.org>
Cc:        freebsd-doc@freebsd.org
Subject:   Re: Small diff to ipv6 chapter
Message-ID:  <20050715144114.GH19236@arved.at>
In-Reply-To: <20050714185739.GA1191@beatrix.daedalusnetworks.priv>
References:  <20050714170633.GE19236@arved.at> <20050714185739.GA1191@beatrix.daedalusnetworks.priv>

next in thread | previous in thread | raw e-mail | index | archive | help

--9zSXsLTf0vkW971A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello Giorgos,

Thanks for the review here is an updated patch, which should contain
your suggestions plus some additions.

* Giorgos Keramidas [2005-07-14 20:57]:
> When it makes sense, I prefer seeing commits that change <ulink>
> elements like this:
> 
> 	<ulink url="http://example.net/">example.net</ulink>;
> 
> to this:
> 
> 	<ulink url="http://example.net/"></ulink>;
> 
> This saves us typing, it's more difficult to get wrong (less duplication
> of text) and renders better in non-hypertext versions of the docs, where
> the link URL is not ``lost''.

[..]

regards
tilman

--9zSXsLTf0vkW971A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=patch-ipv6

Index: chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v
retrieving revision 1.366
diff -u -u -r1.366 chapter.sgml
--- chapter.sgml	14 Jul 2005 21:27:31 -0000	1.366
+++ chapter.sgml	15 Jul 2005 14:35:34 -0000
@@ -2308,8 +2308,8 @@
 	  <primary>Etherboot</primary>
 	</indexterm>
 
-	<para><ulink url="http://etherboot.sourceforge.net">Etherboot's Web
-	  site</ulink> contains
+	<para>Etherboot's Web site <ulink 
+	  url="http://etherboot.sourceforge.net/"></ulink>; contains
 	  <ulink url="http://etherboot.sourceforge.net/doc/html/userman/t1.html">;
 	  extensive documentation</ulink> mainly intended for Linux
 	  systems, but nonetheless containing useful information.  The
@@ -3648,15 +3648,16 @@
 
     <itemizedlist>
       <listitem>
-	<para>IPv6 overview at <ulink url="http://playground.sun.com/pub/ipng/html/ipng-main.html">playground.sun.com</ulink></para>;
+	<para>IPv6 overview at playground.sun.com <ulink
+	  url="http://playground.sun.com/pub/ipng/html/ipng-main.html"></ulink></para>;
       </listitem>
 
       <listitem>
-	<para><ulink url="http://www.kame.net">KAME.net</ulink></para>;
+	<para>KAME.net <ulink url="http://www.kame.net/"></ulink></para>;
       </listitem>
 
       <listitem>
-	<para><ulink url="http://www.6bone.net">6bone.net</ulink></para>;
+	<para>6bone.net <ulink url="http://www.6bone.net/"></ulink></para>;
       </listitem>
     </itemizedlist>
 
@@ -3825,7 +3826,7 @@
 	</listitem>
 
 	<listitem>
-	  <para>Tunnel via 6-to-4 (<ulink
+	  <para>Tunnel via the 6-to-4 tunnel interface &man.stf.4; (<ulink
 	    url="http://www.ietf.org/rfc/rfc3068.txt">RFC3068</ulink>)</para>;
 	</listitem>
 
@@ -3840,7 +3841,7 @@
       <para>First take a look at the <ulink url="http://www.6bone.net/">6bone</ulink>; site and find a 6bone connection nearest to
 	you.  Write to the responsible person and with a little bit of luck you
 	will be given instructions on how to set up your connection.  Usually this
-	involves setting up a GRE (gif) tunnel.</para>
+	involves setting up an IP tunnel.</para>
 
       <para>Here is a typical example on setting up a &man.gif.4; tunnel:</para>
 
@@ -3877,8 +3878,8 @@
      6  3ffe:1800:0:3:290:27ff:fe14:cdee  394.712 ms  397.19 ms  394.102 ms</screen>
 
       <para>This output will differ from machine to machine.  By now you should be
-	able to reach the IPv6 site <ulink url="http://www.kame.net">www.kame.net</ulink>;
-	and see the dancing tortoise &mdash; that is if you have a IPv6 enabled browser such as
+	able to reach the IPv6 site <ulink url="http://www.kame.net/"></ulink>;
+	and see the dancing tortoise &mdash; that is if you have an IPv6 enabled browser such as
 	<filename role="package">www/mozilla</filename>, <application>Konqueror</application>,
 	which is part of <filename role="package">x11/kdebase3</filename>,
 	or <filename role="package">www/epiphany</filename>.</para>
@@ -3888,8 +3889,8 @@
     <sect2>
       <title>DNS in the IPv6 World</title>
 
-      <para>There used to be two types of DNS records for IPv6.  The IETF
-	has declared A6 records obsolete.  AAAA records are the standard
+      <para>There used to be two types of DNS records for IPv6: A6 and AAAA.  The
+	IETF has declared A6 records obsolete.  AAAA records are the standard
 	now.</para>
 
       <para>Using AAAA records is straightforward.  Assign your hostname to the new
@@ -3963,7 +3964,7 @@
       </sect3>
 
       <sect3>
-	<title>IPv6 Tunnel Settings</title>
+	<title>IPv6 Router Settings</title>
 
 	<para>If the server is to route IPv6 between the rest of your network
 	  and the world, the following <filename>/etc/rc.conf</filename>
@@ -3998,15 +3999,15 @@
 	:addrs#1:addr="2001:471:1f11:246::":prefixlen#64:tc=ether:</programlisting>
 
       <para>Replace <devicename>fxp0</devicename> with the interface you
-	are going to be using.</para>
-
-      <para>Next, replace <hostid role="ip6addr">2001:471:1f11:246::</hostid>
-	with the prefix of your allocation.</para>
-
-      <para>If you are dedicated a <hostid role="netmask">/64</hostid> subnet
+	are going to be using.  Next, replace <hostid role="ip6addr">
+	2001:471:1f11:246::</hostid> with the prefix of your allocation.
+	If you are dedicated a <hostid role="netmask">/64</hostid> subnet
 	you will not need to change anything else.  Otherwise, you will need to
 	change the <literal>prefixlen#</literal> to the correct value.</para>
 
+      <para>The manual page &man.rtadvd.conf.5; describes the syntax of this
+	configuration file.</para>
+
    </sect2>
   </sect1>
 

--9zSXsLTf0vkW971A--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050715144114.GH19236>