[BACK]Return to 29.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/29.html between version 1.47 and 1.48

version 1.47, 2018/06/12 15:20:28 version 1.48, 2019/05/27 22:55:18
Line 1 
Line 1 
 <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">  <!doctype html>
 <html>  <html lang=en id=release>
 <head>  <meta charset=utf-8>
   
 <title>OpenBSD 2.9</title>  <title>OpenBSD 2.9</title>
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">  
 <meta name="description" content="OpenBSD 2.9">  <meta name="description" content="OpenBSD 2.9">
 <meta name="copyright" content="This document copyright 1999-2002 by OpenBSD.">  
 <meta name="viewport" content="width=device-width, initial-scale=1">  <meta name="viewport" content="width=device-width, initial-scale=1">
 <link rel="stylesheet" type="text/css" href="openbsd.css">  <link rel="stylesheet" type="text/css" href="openbsd.css">
 <link rel="canonical" href="https://www.openbsd.org/29.html">  <link rel="canonical" href="https://www.openbsd.org/29.html">
 </head>  <style>
   #sourcecode h3 {
           color: var(--red);
   }
   
 <body bgcolor="#ffffff" text="#000000" link="#24248e">  #sourcecode p {
           margin-left: 2.75em;
   }
   
 <h2>  #sourcecode blockquote {
           margin-left: 4.5em;
   }
   </style>
   
   <h2 id=OpenBSD>
 <a href="index.html">  <a href="index.html">
 <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>  <i>Open</i><b>BSD</b></a>
 <font color="#e00000">2.9</font>  2.9
 </h2>  </h2>
   
   <table>
   <tr>
   <td>
 <a href=images/Business.jpg>  <a href=images/Business.jpg>
 <img align=left hspace="24" src=images/Business.jpg></a>  <img src=images/Business.jpg alt="Business"></a>
 <p>  <td>
 Released June 1, 2001<br>  Released June 1, 2001<br>
 Copyright 1997-2001, Theo de Raadt.<br>  Copyright 1997-2001, Theo de Raadt.<br>
 <font color=#e00000>ISBN 0-9683637-7-6</font>  <cite class=isbn>ISBN 0-9683637-7-6</cite>
 <p>  <p>
 <ul>  <ul>
 <!--  <!--
Line 31 
Line 43 
 -->  -->
 <li>See the information on <a href=ftp.html>The FTP page</a> for  <li>See the information on <a href=ftp.html>The FTP page</a> for
         a list of mirror machines          a list of mirror machines
 <li>Go to the <font color=#e00000>pub/OpenBSD/2.9/</font> directory on  <li>Go to the <code class=reldir>pub/OpenBSD/2.9/</code> directory on
         one of the mirror sites          one of the mirror sites
 <li>Have a look at <a href=errata29.html>The 2.9 Errata page</a> for a list  <li>Have a look at <a href=errata29.html>The 2.9 Errata page</a> for a list
         of bugs and workarounds.          of bugs and workarounds.
Line 42 
Line 54 
 All applicable copyrights and credits are in the src.tar.gz,  All applicable copyrights and credits are in the src.tar.gz,
 sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in the  sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in the
 files fetched via ports.tar.gz.  files fetched via ports.tar.gz.
 <br clear="all">  </table>
   
 <hr>  <hr>
 <p>  
 <a name="new"></a>  <section id=new>
 <h3><font color=#0000e0>What's New</font></h3>  <h3>What's New</h3>
 <p>  
 This is a partial list of new features and systems included in OpenBSD 2.9.  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  For a comprehensive list, see the <a href=plus29.html>changelog</a> leading
 to 2.9.  to 2.9.
Line 136 
Line 148 
 <p>  <p>
 <ul>  <ul>
 <li>Long username support.  <li>Long username support.
 <li>Vastly improved Linux <a href="https://man.openbsd.org/?query=compat_linux&sektion=8">emulation</a> allowing many more applications to run.  <li>Vastly improved Linux <a href="https://man.openbsd.org/compat_linux.8">emulation</a> allowing many more applications to run.
 <li>802.1d spanning tree support for <a href="https://man.openbsd.org/?query=bridge&sektion=4">bridge(4)</a>.  <li>802.1d spanning tree support for <a href="https://man.openbsd.org/bridge.4">bridge(4)</a>.
 <li><a href="https://man.openbsd.org/?query=vlan&sektion=4">vlan(4)</a> bridging support allows for many more bridge possibilities (Now you can even use OpenBSD as an 802.1Q compatible switch)  <li><a href="https://man.openbsd.org/vlan.4">vlan(4)</a> bridging support allows for many more bridge possibilities (Now you can even use OpenBSD as an 802.1Q compatible switch)
 <li><a href="https://man.openbsd.org/?query=kqueue&sektion=2">kqueue(2)</a> kernel event notification mechanism.  <li><a href="https://man.openbsd.org/kqueue.2">kqueue(2)</a> kernel event notification mechanism.
 <li>Addition of the <a href="https://man.openbsd.org/?query=wscons&sektion=4">wscons(4)</a> machine-independent console driver.  <li>Addition of the <a href="https://man.openbsd.org/wscons.4">wscons(4)</a> machine-independent console driver.
 <li>Major enhancements to softupdates, including speed and stability fixes.  <li>Major enhancements to softupdates, including speed and stability fixes.
 <li>Bug-fixes and enhancements to the <a href="https://man.openbsd.org/?query=atapiscsi&sektion=4">atapiscsi(4)</a> and <a href="https://man.openbsd.org/?query=pciide&sektion=4">pciide(4)</a> drivers,  <li>Bug-fixes and enhancements to the <a href="https://man.openbsd.org/atapiscsi.4">atapiscsi(4)</a> and <a href="https://man.openbsd.org/pciide.4">pciide(4)</a> drivers,
 including UltraDMA/100 support for Intel, Promise, and Highpoint controllers.  including UltraDMA/100 support for Intel, Promise, and Highpoint controllers.
 </ul>  </ul>
 <p>  
   
 </ul>  </ul>
 <p>  </section>
   
 <a name=install></a>  
 <hr>  <hr>
   
   <section id=install>
   <h3>How to install</h3>
   
 <p>  <p>
 <h3><font color=#0000e0>How to install</font></h3>  
 <p>  
 Following this are the instructions which you would have on a piece of  Following this are the instructions which you would have on a piece of
 paper if you had purchased a CDROM set instead of doing an alternate  paper if you had purchased a CDROM set instead of doing an alternate
 form of install.  The instructions for doing an ftp (or other style  form of install.  The instructions for doing an ftp (or other style
Line 171 
Line 183 
 <li>    CD1:2.9/i386/INSTALL.i386  <li>    CD1:2.9/i386/INSTALL.i386
 <li>    CD1:2.9/powerpc/INSTALL.powerpc  <li>    CD1:2.9/powerpc/INSTALL.powerpc
 <li>    CD1:2.9/vax/INSTALL.vax  <li>    CD1:2.9/vax/INSTALL.vax
 <p>  </ul>
   <ul>
 <li>    CD2:2.9/sparc/INSTALL.sparc  <li>    CD2:2.9/sparc/INSTALL.sparc
 <li>    CD2:2.9/mvme68k/INSTALL.mvme68k  <li>    CD2:2.9/mvme68k/INSTALL.mvme68k
 <li>    CD2:2.9/amiga/INSTALL.amiga  <li>    CD2:2.9/amiga/INSTALL.amiga
 <li>    CD2:2.9/mac68k/INSTALL.mac68k  <li>    CD2:2.9/mac68k/INSTALL.mac68k
 <li>    CD2:2.9/hp300/INSTALL.hp300  <li>    CD2:2.9/hp300/INSTALL.hp300
 <li>    CD2:2.9/sun3/INSTALL.sun3  <li>    CD2:2.9/sun3/INSTALL.sun3
 <p>  </ul>
   <ul>
 <li>The alpha release is available on the ftp sites, but not on the CDs.  <li>The alpha release is available on the ftp sites, but not on the CDs.
 </ul>  </ul>
   
 <hr>  <hr>
   
   <section id=quickinstall>
   
 <p>  <p>
 Quick installer information for people familiar with OpenBSD, and the  Quick installer information for people familiar with OpenBSD, and the
 use of the "disklabel -E" command.  If you are at all confused when  use of the "disklabel -E" command.  If you are at all confused when
 installing OpenBSD, read the relevant INSTALL.* file as listed above!  installing OpenBSD, read the relevant INSTALL.* file as listed above!
 <p>  
   
 <h3><font color=#e00000>OpenBSD/i386:</font></h3>  <h3>OpenBSD/i386:</h3>
 <ul>  
 <p>  <p>
 Play with your BIOS options to enable booting from a CD. The OpenBSD/i386 release is on CD1. If your BIOS does not support booting from CD, you will need to create a boot floppy to install from. To create a boot floppy write <i>CD1:2.9/i386/floppy29.fs</i> to a floppy and boot via the floppy drive.  Play with your BIOS options to enable booting from a CD. The OpenBSD/i386 release is on CD1. If your BIOS does not support booting from CD, you will need to create a boot floppy to install from. To create a boot floppy write <i>CD1:2.9/i386/floppy29.fs</i> to a floppy and boot via the floppy drive.
   
Line 198 
Line 214 
 If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.  If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.
   
 <p>  <p>
 To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located at <i>CD:/2.9/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="https://man.openbsd.org/?query=dd&sektion=1">dd(1)</a> utility. The following is an example usage of <a href="https://man.openbsd.org/?query=dd&sektion=1">dd(1)</a>, where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or &quot;rfd0a&quot;.  To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located at <i>CD:/2.9/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="https://man.openbsd.org/dd.1">dd(1)</a> utility. The following is an example usage of <a href="https://man.openbsd.org/dd.1">dd(1)</a>, where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or &quot;rfd0a&quot;.
   
 <ul><pre>  <blockquote><pre>
 # <strong>dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k</strong>  # <strong>dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k</strong>
 </pre></ul>  </pre></blockquote>
   
 <p>  <p>
 Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to <a href="faq/faq4.html#4.1">FAQ4.1</a>.  Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to <a href="faq/faq4.html#4.1">FAQ4.1</a>.
 </ul>  
   
   <h3>OpenBSD/sparc:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>OpenBSD/sparc:</font></h3>  
 <ul>  
 <p>  
 The 2.9 release of OpenBSD/sparc is located on CD2. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM.  The 2.9 release of OpenBSD/sparc is located on CD2. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM.
   
 <ul><pre>  <blockquote><pre>
 > <strong>boot cdrom 2.9/sparc/bsd.rd</strong>  > <kbd>boot cdrom 2.9/sparc/bsd.rd</kbd>
 or  or
 > <strong>b sd(0,6,0)2.9/sparc/bsd.rd</strong>  > <kbd>b sd(0,6,0)2.9/sparc/bsd.rd</kbd>
 </pre></ul>  </pre></blockquote>
   
 <p>  <p>
 If your sparc does not have a CD drive, you can alternatively boot from floppy. To do so you need to write &quot;CD2:2.9/sparc/floppy29.fs&quot; to a floppy. For more information see <a href="faq/faq4.html#4.1">FAQ4.1</a>. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.  If your sparc does not have a CD drive, you can alternatively boot from floppy. To do so you need to write &quot;CD2:2.9/sparc/floppy29.fs&quot; to a floppy. For more information see <a href="faq/faq4.html#4.1">FAQ4.1</a>. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.
   
 <ul><pre>  <blockquote><pre>
 > <strong>boot floppy</strong>  > <kbd>boot floppy</kbd>
 or  or
 > <strong>boot fd()</strong>  > <strong>boot fd()</strong>
 </pre></ul>  </pre></blockquote>
   
 <p>  <p>
 Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.  Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.
Line 236 
Line 250 
 If your sparc doesn't have a floppy drive nor a CD drive, you can either  If your sparc doesn't have a floppy drive nor a CD drive, you can either
 setup a bootable tape, or install via network, as told in the  setup a bootable tape, or install via network, as told in the
 INSTALL.sparc file.  INSTALL.sparc file.
 </ul>  
   
   <h3>OpenBSD/amiga:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>OpenBSD/amiga:</font></h3>  
 <ul>  
 <p>  
 Create BSD partitions according to INSTALL.amiga's preparation section.  Create BSD partitions according to INSTALL.amiga's preparation section.
 Mount the CD2 under AmigaOS as device CD0: Next, execute the following  Mount the CD2 under AmigaOS as device CD0: Next, execute the following
 CLI command: "CD0:2.9/amiga/utils/loadbsd CD0:2.9/amiga/bsd.rd".  CLI command: "CD0:2.9/amiga/utils/loadbsd CD0:2.9/amiga/bsd.rd".
 </ul>  
   
   <h3>OpenBSD/hp300:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>OpenBSD/hp300:</font></h3>  
 <ul>  
 <p>  
 You can boot over the network by following the instructions in  You can boot over the network by following the instructions in
 INSTALL.hp300.  INSTALL.hp300.
 </ul>  
   
   <h3>OpenBSD/mac68k:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>OpenBSD/mac68k:</font></h3>  
 <ul>  
 <p>  
 Boot MacOS as normal and partition your disk with the appropriate A/UX  Boot MacOS as normal and partition your disk with the appropriate A/UX
 configurations.  Then, extract the Macside utilities from  configurations.  Then, extract the Macside utilities from
 CD2:2.9/mac68k/utils onto your hard disk.  Run Mkfs to create your  CD2:2.9/mac68k/utils onto your hard disk.  Run Mkfs to create your
Line 266 
Line 274 
 BSD/Mac68k Installer to copy all the sets in CD2:2.9/mac68k/ onto your  BSD/Mac68k Installer to copy all the sets in CD2:2.9/mac68k/ onto your
 partitions.  Finally, you will be ready to configure the BSD/Mac68k  partitions.  Finally, you will be ready to configure the BSD/Mac68k
 Booter with the location of your kernel and boot the system.  Booter with the location of your kernel and boot the system.
 </ul>  
   
   <h3>OpenBSD/sun3:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>OpenBSD/sun3:</font></h3>  
 <ul>  
 <p>  
 You can either setup a diskless boot or create an installation tape,  You can either setup a diskless boot or create an installation tape,
 as described in INSTALL.sun3.  as described in INSTALL.sun3.
 </ul>  
   
   <h3>OpenBSD/alpha:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>OpenBSD/alpha:</font></h3>  
 <ul>  
 <p>  
 Get the release via ftp. Then, you can either setup a diskless boot or boot via floppy as described in INSTALL.alpha.  Get the release via ftp. Then, you can either setup a diskless boot or boot via floppy as described in INSTALL.alpha.
 </p>  
 </ul>  
   
   </section>
   
   <section id=sourcecode>
   <h3>Notes about the source code:</h3>
   
 <p>  <p>
 <h3><font color=#e00000>Notes about the source code:</font></h3>  
 <ul>  
 <p>  
 src.tar.gz contains a source archive starting at /usr/src.  This file  src.tar.gz contains a source archive starting at /usr/src.  This file
 contains everything you need except for the kernel sources, which are  contains everything you need except for the kernel sources, which are
 in a separate archive.  To extract:  in a separate archive.  To extract:
   
   <blockquote><pre>
   # <kbd>mkdir -p /usr/src</kbd>
   # <kbd>cd /usr/src</kbd>
   # <kbd>tar xvfz /tmp/src.tar.gz</kbd>
   </pre></blockquote>
   
 <p>  <p>
 <ul><pre>  
 # <strong>mkdir -p /usr/src</strong>  
 # <strong>cd /usr/src</strong>  
 # <strong>tar xvfz /tmp/src.tar.gz</strong>  
 </pre></ul>  
 <p>  
 srcsys.tar.gz contains a source archive starting at /usr/src/sys.  srcsys.tar.gz contains a source archive starting at /usr/src/sys.
 This file contains all the kernel sources you need to rebuild kernels.  This file contains all the kernel sources you need to rebuild kernels.
 To extract:  To extract:
   
   <blockquote><pre>
   # <kbd>mkdir -p /usr/src/sys</kbd>
   # <kbd>cd /usr/src</kbd>
   # <kbd>tar xvfz /tmp/srcsys.tar.gz</kbd>
   </pre></blockquote>
   
 <p>  <p>
 <ul><pre>  
 # <strong>mkdir -p /usr/src/sys</strong>  
 # <strong>cd /usr/src</strong>  
 # <strong>tar xvfz /tmp/srcsys.tar.gz</strong>  
 </pre></ul>  
 <p>  
 Both of these trees are a regular CVS checkout.  Using these trees it  Both of these trees are a regular CVS checkout.  Using these trees it
 is possible to get a head-start on using the anoncvs servers as  is possible to get a head-start on using the anoncvs servers as
 described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.  described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
 Using these files  Using these files
 results in a much faster initial CVS update than you could expect from  results in a much faster initial CVS update than you could expect from
 a fresh checkout of the full OpenBSD source tree.  a fresh checkout of the full OpenBSD source tree.
 <p>  
 </ul>  </section>
 <a name=ports></a>  </section>
   
 <hr>  <hr>
   
   <section id=ports>
   <h3>Ports Tree</h3>
 <p>  <p>
 <h3><font color=#0000e0>Ports Tree</font></h3>  
 <p>  
 A ports tree archive is also provided.  To extract:  A ports tree archive is also provided.  To extract:
 <p>  <p>
 <ul><pre>  <blockquote><pre>
 # <strong>cd /usr</strong>  # <kbd>cd /usr</kbd>
 # <strong>tar xvfz /tmp/ports.tar.gz</strong>  # <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
 # <strong>cd ports</strong>  # <kbd>cd ports</kbd>
 </pre></ul>  </pre></blockquote>
 <p>  <p>
 The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree.  Go  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>  read <a href=faq/faq15.html>http://www.OpenBSD.org/faq/faq15.html</a>
Line 342 
Line 350 
 on most architectures (over 1200 packages build on i386, for instance).  on most architectures (over 1200 packages build on i386, for instance).
 <p>  <p>
 The <i>ports/</i> directory represents a CVS (see the manpage for  The <i>ports/</i> directory represents a CVS (see the manpage for
 <a href="https://man.openbsd.org/?query=cvs&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html">  <a href="https://man.openbsd.org/cvs.1">
 cvs(1)</a> if  cvs(1)</a> if
 you aren't familiar with CVS) checkout of our ports.  As with our complete  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  source tree, our ports tree is available via anoncvs.  So, in
Line 350 
Line 358 
 available on a read-write medium and update the tree with a command  available on a read-write medium and update the tree with a command
 like:  like:
 <p>  <p>
 <ul><pre>  <blockquote><pre>
 # <strong>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_2_9</strong>  # <strong>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_2_9</strong>
 </pre></ul>  </pre></blockquote>
 <p>  <p>
 [Of course, you must replace the local directory and server name here  [Of course, you must replace the local directory and server name here
 with the location of your ports collection and a nearby anoncvs  with the location of your ports collection and a nearby anoncvs
Line 364 
Line 372 
 If you're interested in seeing a port added, would like to help out, or just  If you're interested in seeing a port added, would like to help out, or just
 would like to know more, the mailing list ports@openbsd.org is a good  would like to know more, the mailing list ports@openbsd.org is a good
 place to know.  place to know.
 <p>  </section>
   
 </body>  
 </html>  

Legend:
Removed from v.1.47  
changed lines
  Added in v.1.48