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

Annotation of www/stable.html, Revision 1.24

1.22      nick        1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1       jason       2: <html>
                      3: <head>
1.23      nick        4: <title>Following -stable</title>
1.22      nick        5: <link rev=made href="mailto:www@openbsd.org">
1.1       jason       6: <meta name="resource-type" content="document">
                      7: <meta name="description" content="stable">
                      8: <meta name="keywords" content="openbsd,anoncvs,updates,stable">
                      9: <meta name="distribution" content="global">
1.23      nick       10: <meta name="copyright" content="This document copyright 1996-2007 by OpenBSD.">
1.22      nick       11: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.1       jason      12: </head>
                     13:
1.22      nick       14: <body bgcolor="#ffffff" text="#000000">
                     15: <!-- Passes validator.w3.org, please keep it this way;
                     16: please, use a max of 72 chars per line -->
1.1       jason      17:
1.23      nick       18: <a href="index.html">
                     19: <img alt="[OpenBSD]" height=30 width=141 src="images/smalltitle.gif" border="0">
                     20: </a>
                     21:
1.1       jason      22: <p>
1.23      nick       23: <h1><font color="#e00000">Following <i>-stable</i> (the "Patch
                     24: branch")</font></h1>
1.22      nick       25: <hr>
1.1       jason      26:
1.23      nick       27: <h3>Table Of Contents</h3>
1.1       jason      28: <p>
1.22      nick       29: <ul>
1.23      nick       30: <li><a href="#whatis">What is the <i>-stable</i> (patch) branch?</a>
                     31: <li><a href="#getting">Getting <i>-stable</i> source code</a>
                     32: <li><a href="#building">Building OpenBSD <i>-stable</i></a>
1.1       jason      33: </ul>
                     34: <hr>
                     35:
                     36: <a name="whatis"></a>
1.24    ! steven     37: <h3><font color="#0000e0">What is the <i>-stable</i> (patch)
        !            38: branch?</font></h3>
1.1       jason      39:
                     40: <p>
1.19      nick       41: Starting with 2.7, OpenBSD provides a source tree that contains
                     42: important patches and fixes (i.e. those from the
                     43: <a href="errata.html">errata</a> plus others which are obvious and simple,
                     44: but do not deserve an errata entry)
1.23      nick       45: and makes it available via <a href="anoncvs.html">CVS</a>, in addition to the
                     46: <i>-current</i> source.  Thus, users can choose three options :<p>
1.4       deraadt    47: <ul>
1.19      nick       48: <li>Stick with our latest release and apply the patches by hand.
1.23      nick       49: <li>Use the <b>patch branch</b> which has those patches and some others
                     50: applied.
1.19      nick       51: <li>Use <b>current source</b> for all of the latest features.
1.4       deraadt    52: </ul>
                     53: <p>
1.19      nick       54: <!-- The <a href="plus.html">Daily Changelog</a> details (amoung other things)
                     55: which post-release changes have made it into the patch branch. -->
                     56: As a general principle, all
1.23      nick       57: <a href="errata.html">errata</a> entries will be merged into the patch
1.19      nick       58: branch within 48 hours of when an errata is published.  Other post release
                     59: patches may be merged in as well, subject to a number of conditions:
1.4       deraadt    60: <ul>
1.19      nick       61: <li>The patches must be simple, short, and obviously 100% correct.
                     62: <li>Errata entries are made for bugs which affect many people.  Other
                     63:     patches may be merged into the patch branch if they affect a few
                     64:     people in drastic ways.
                     65: <li>Please do not ask for large subsystems or patches to be merged.
                     66:     Maintaining the patch tree takes a lot of effort which could be
                     67:     better spent on making our next release better.
1.23      nick       68: <li>New or changed functionality, hardware support or APIs will
                     69:     <i>not</i> be merged.
                     70:     In general, if it requires a man page change, it will NOT be a
                     71:     candidate for the patch branch.
1.19      nick       72: <li>As an exception to the above rules, OpenSSH release versions will be
                     73:     merged into the patch branch.
1.4       deraadt    74: </ul>
                     75: <p>
1.1       jason      76:
1.23      nick       77: It is worth pointing out the name <i>-stable</i> refers ONLY to the API
                     78: and operations of OpenBSD not changing, not the overall reliability of
                     79: the system.
                     80: In fact, if things go as desired, the <i>-current</i>
                     81: <a href="faq/faq5.html#Flavors">flavor</a> of OpenBSD, on its way to
                     82: becoming the next <i>-release</i>, will be an improvement in
                     83: reliability, security and overall quality over the previous
                     84: <i>-release</i> and <i>-stable</i>.
                     85:
1.1       jason      86: <a name="getting"></a>
1.23      nick       87: <h3><font color="#0000e0">Getting <i>-stable</i> source code</font></h3>
1.1       jason      88:
                     89: <p>
1.19      nick       90: To obtain the patch branch for a particular release of OpenBSD, you
                     91: can update on top of a pre-existing source tree
                     92: (from <a href="ftp.html">FTP</a> or the <a href="orders.html">CD</a>)
                     93: or you can grab the source tree freshly from
                     94: an <a href="anoncvs.html">AnonCVS</a> server.
                     95: Instructions for getting the patch branch and staying up to date are
                     96: described in the <b>Getting Started</b> section of the
                     97: <a href="anoncvs.html#starting">AnonCVS documentation</a>.
                     98: Note that patch branches do not help to upgrade from one release of
1.21      steven     99: OpenBSD to another, e.g. to go from 3.9 to 4.0.  They only provide
1.19      nick      100: a means for staying up to date with the patches within a given release.
1.23      nick      101:
                    102: <p>
                    103: Do not attempt to go from one release to another via source.
                    104: Instead, please visit the <a href="faq/upgrade40.html">upgrade guide</a>.
1.19      nick      105: Also, you cannot go backwards, from -current back to -stable, because of
1.23      nick      106: library versioning problems and other changes.
1.1       jason     107:
                    108: <a name="building"></a>
1.23      nick      109: <h3><font color="#0000e0">Building OpenBSD <i>-stable</i></font></h3>
                    110: Full details on building from source are provided in
                    111: <a href="faq/faq5.html">FAQ 5 - Building the System from Source</a>.
                    112: This is a simplified summary.
                    113:
                    114: <p>
1.19      nick      115: Once you have obtained a source tree via <a href="anoncvs.html">anoncvs</a>,
                    116: you must rebuild the system.  The stages for doing so are:
1.1       jason     117:
                    118: <ul>
1.19      nick      119:  <li>Rebuild the kernel
                    120:  <li>Reboot with the new kernel
                    121:  <li>Rebuild the binaries
1.1       jason     122: </ul>
                    123:
1.22      nick      124: <h4><font color="#0000e0">Rebuilding the kernel</font></h4>
1.1       jason     125:
                    126: <p>
1.19      nick      127: To rebuild the default kernel from stable:
1.22      nick      128: <blockquote><pre>
1.3       ericj     129: # <strong>cd /usr/src/sys/arch/i386/conf</strong>
                    130: # <strong>/usr/sbin/config GENERIC</strong>
                    131: # <strong>cd /usr/src/sys/arch/i386/compile/GENERIC</strong>
                    132: # <strong>make clean &amp;&amp; make depend &amp;&amp; make</strong>
1.22      nick      133: </pre></blockquote>
1.1       jason     134:
                    135: <p>
1.19      nick      136: Replace <i>i386</i> with your architecture, e.g.
                    137: <i>sparc</i>, <i>alpha</i>, etc.
1.1       jason     138:
1.22      nick      139: <h4><font color="#0000e0">Rebooting with the new kernel</font></h4>
1.1       jason     140:
                    141: <p>
1.19      nick      142: To reboot with the newly compiled kernel:
1.22      nick      143: <blockquote><pre>
1.3       ericj     144: # <strong>cd /usr/src/sys/arch/i386/compile/GENERIC</strong>
1.23      nick      145: # <strong>make install</strong>          <i>(Safely install new kernel)</i>
1.3       ericj     146: # <strong>reboot</strong>
1.22      nick      147: </pre></blockquote>
1.1       jason     148:
                    149: <p>
1.19      nick      150: As above, substitute your architecture for <i>i386</i>.  If your system has
                    151: trouble booting the new kernel, you can easily go back and reboot from the
1.23      nick      152: old kernel, now called <i>obsd</i>.
1.1       jason     153:
1.22      nick      154: <h4><font color="#0000e0">Rebuilding the binaries</font></h4>
1.1       jason     155:
1.19      nick      156: <p> To rebuild the system binaries:
1.22      nick      157: <blockquote><pre>
1.16      steven    158: # <strong>rm -rf /usr/obj/*</strong>
1.3       ericj     159: # <strong>cd /usr/src</strong>
1.16      steven    160: # <strong>make obj</strong>
                    161: # <strong>cd /usr/src/etc &amp;&amp; env DESTDIR=/ make distrib-dirs</strong>
                    162: # <strong>cd /usr/src</strong>
                    163: # <strong>make build</strong>
1.22      nick      164: </pre></blockquote>
1.1       jason     165:
1.19      nick      166: <p>This will take awhile...
1.23      nick      167:
                    168: <p>
                    169: If you have a number of machines to keep at <i>-stable</i>, you may wish to
                    170: make a <a href="faq/faq5.html#Release">release</a>, creating the
                    171: standard install <a href="faq/faq4.html#FilesNeeded">file sets</a>,
                    172: which can then be quickly and easily installed on any machine of the
                    173: same <a href="plat.html">platform</a>.
                    174:
1.1       jason     175: <hr>
1.19      nick      176: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.22      nick      177: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.24    ! steven    178: <br><small>$OpenBSD: stable.html,v 1.23 2007/01/02 15:14:06 nick Exp $</small>
1.1       jason     179: </body>
                    180: </html>
1.19      nick      181: