===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/29.html,v
retrieving revision 1.49
retrieving revision 1.50
diff -c -r1.49 -r1.50
*** www/29.html	2019/06/12 20:57:16	1.49
--- www/29.html	2019/06/13 05:33:57	1.50
***************
*** 23,35 ****
  Released June 1, 2001<br>
  Copyright 1997-2001, Theo de Raadt.<br>
  <cite class=isbn>ISBN 0-9683637-7-6</cite>
! <p>
  <ul>
  <li>See the information on <a href=ftp.html>The FTP page</a> for
  	a list of mirror machines
  <li>Go to the <code class=reldir>pub/OpenBSD/2.9/</code> directory on
  	one of the mirror sites
! <li>Have a look at <a href=errata29.html>The 2.9 Errata page</a> for a list
  	of bugs and workarounds.
  <li>See a <a href=plus29.html>detailed log of changes</a> between the
  	2.8 and 2.9 releases.
--- 23,35 ----
  Released June 1, 2001<br>
  Copyright 1997-2001, Theo de Raadt.<br>
  <cite class=isbn>ISBN 0-9683637-7-6</cite>
! 
  <ul>
  <li>See the information on <a href=ftp.html>The FTP page</a> for
  	a list of mirror machines
  <li>Go to the <code class=reldir>pub/OpenBSD/2.9/</code> directory on
  	one of the mirror sites
! <li>Have a look at <a href="errata29.html">The 2.9 Errata page</a> for a list
  	of bugs and workarounds.
  <li>See a <a href=plus29.html>detailed log of changes</a> between the
  	2.8 and 2.9 releases.
***************
*** 44,53 ****
  
  <section id=new>
  <h3>What's New</h3>
  This is a partial list of new features and systems included in OpenBSD 2.9.
  For a comprehensive list, see the <a href=plus29.html>changelog</a> leading
  to 2.9.
- <p>
  
  <ul>
  
--- 44,53 ----
  
  <section id=new>
  <h3>What's New</h3>
+ <p>
  This is a partial list of new features and systems included in OpenBSD 2.9.
  For a comprehensive list, see the <a href=plus29.html>changelog</a> leading
  to 2.9.
  
  <ul>
  
***************
*** 155,166 ****
  of) install are very similar; the CDROM instructions are left intact
  so that you can see how much easier it would have been if you had
  purchased a CDROM instead.
- <p>
  
  <hr>
  Please refer to the following files on the two CDROMs for extensive
  details on how to install OpenBSD 2.9 on your machine:
! <p>
  <ul>
  <li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/i386/INSTALL.i386">
  	.../OpenBSD/2.9/i386/INSTALL.i386 (on CD1)</a>
--- 155,165 ----
  of) install are very similar; the CDROM instructions are left intact
  so that you can see how much easier it would have been if you had
  purchased a CDROM instead.
  
  <hr>
  Please refer to the following files on the two CDROMs for extensive
  details on how to install OpenBSD 2.9 on your machine:
! 
  <ul>
  <li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/i386/INSTALL.i386">
  	.../OpenBSD/2.9/i386/INSTALL.i386 (on CD1)</a>
***************
*** 319,325 ****
  <h3>Ports Tree</h3>
  <p>
  A ports tree archive is also provided.  To extract:
- <p>
  <blockquote><pre>
  # <kbd>cd /usr</kbd>
  # <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
--- 318,323 ----
***************
*** 327,333 ****
  </pre></blockquote>
  <p>
  The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree.  Go
! read <a href=faq/faq15.html>http://www.OpenBSD.org/faq/faq15.html</a>
  if you know nothing about ports
  at this point.  This text is not a manual of how to use ports.
  Rather, it is a set of notes meant to kickstart the user on the
--- 325,331 ----
  </pre></blockquote>
  <p>
  The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree.  Go
! read <a href="faq/faq15.html">https://www.OpenBSD.org/faq/faq15.html</a>
  if you know nothing about ports
  at this point.  This text is not a manual of how to use ports.
  Rather, it is a set of notes meant to kickstart the user on the
***************
*** 339,352 ****
  on most architectures (over 1200 packages build on i386, for instance).
  <p>
  The <i>ports/</i> directory represents a CVS (see the manpage for
! <a href="https://man.openbsd.org/cvs.1">
! cvs(1)</a> if
  you aren't familiar with CVS) checkout of our ports.  As with our complete
  source tree, our ports tree is available via anoncvs.  So, in
  order to keep current with it, you must make the <i>ports/</i> tree
  available on a read-write medium and update the tree with a command
  like:
- <p>
  <blockquote><pre>
  # <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_2_9</kbd>
  </pre></blockquote>
--- 337,348 ----
  on most architectures (over 1200 packages build on i386, for instance).
  <p>
  The <i>ports/</i> directory represents a CVS (see the manpage for
! <a href="https://man.openbsd.org/cvs.1">cvs(1)</a> if
  you aren't familiar with CVS) checkout of our ports.  As with our complete
  source tree, our ports tree is available via anoncvs.  So, in
  order to keep current with it, you must make the <i>ports/</i> tree
  available on a read-write medium and update the tree with a command
  like:
  <blockquote><pre>
  # <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_2_9</kbd>
  </pre></blockquote>