Just a reminder to people. The reason for the "cross reference tag" in the

kb entry is so that you can do this:

	href="../kb-show.php3?xref_tag=tiptunnel"

instead of:

	href="../kb-show.php3?idx=39"

The former makes it possible to export the KB without worrying about how
the remote DB loads the entries.

www/doc/pc3000.html

@@ -42,7 +42,7 @@ further support in the resource mapper.
 </p><p>
 All machines have serial console lines accessible from users.emulab.net via
 the "console" command or remotely via the
-<a href="http://www.emulab.net/kb-show.php3?idx=25">tiptunnel</a> interface.
+<a href="http://www.emulab.net/kb-show.php3?xref_tag=tiptunnel">tiptunnel</a> interface.
 
 </p><p>
 <a NAME="images"></a><h2>Images and Kernel Support</h2>
@@ -99,7 +99,7 @@ images.
      on these machines could be dramatically different.  That is, if your
      applications were CPU, memory, or disk intensive.  If you are
      interested in reproducing old results, you might want to
-     <a href="http://www.emulab.net/kb-show.php3?idx=39">
+     <a href="http://www.emulab.net/kb-show.php3?xref_tag=tb-set-hardware">
      limit your experiments to using only pc600 and pc850 nodes</a>.
 <li> <b>Hyperthreading is available, but SMP support is
      not currently compiled in to the stock Emulab images</b> (with the
@@ -117,6 +117,6 @@ images.
      The Intel Pro1000 cards used for the experimental interfaces in
      these machines default to using interrupt throttling.  This will
      add latency to packet delivery and reception.  See the
-     <a href="http://www.emulab.net/kb-show.php3?idx=75">
+     <a href="http://www.emulab.net/kb-show.php3?xref_tag=pc3000-latency">
      knowledge base entry</a> for how to change or disable this feature.
 </ul>