Annotation of www/stable.html, Revision 1.29
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.27 steven 10: <meta name="copyright" content="This document copyright 1996-2009 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.25 nick 49: <li>Use the <b>patch branch</b> which has those patches.
1.19 nick 50: <li>Use <b>current source</b> for all of the latest features.
1.4 deraadt 51: </ul>
52: <p>
1.19 nick 53: <!-- The <a href="plus.html">Daily Changelog</a> details (amoung other things)
54: which post-release changes have made it into the patch branch. -->
55: As a general principle, all
1.23 nick 56: <a href="errata.html">errata</a> entries will be merged into the patch
1.19 nick 57: branch within 48 hours of when an errata is published. Other post release
58: patches may be merged in as well, subject to a number of conditions:
1.4 deraadt 59: <ul>
1.19 nick 60: <li>The patches must be simple, short, and obviously 100% correct.
61: <li>Errata entries are made for bugs which affect many people. Other
62: patches may be merged into the patch branch if they affect a few
63: people in drastic ways.
64: <li>Please do not ask for large subsystems or patches to be merged.
65: Maintaining the patch tree takes a lot of effort which could be
66: better spent on making our next release better.
1.23 nick 67: <li>New or changed functionality, hardware support or APIs will
68: <i>not</i> be merged.
69: In general, if it requires a man page change, it will NOT be a
70: candidate for the patch branch.
1.19 nick 71: <li>As an exception to the above rules, OpenSSH release versions will be
72: merged into the patch branch.
1.4 deraadt 73: </ul>
74: <p>
1.1 jason 75:
1.23 nick 76: It is worth pointing out the name <i>-stable</i> refers ONLY to the API
77: and operations of OpenBSD not changing, not the overall reliability of
78: the system.
79: In fact, if things go as desired, the <i>-current</i>
80: <a href="faq/faq5.html#Flavors">flavor</a> of OpenBSD, on its way to
81: becoming the next <i>-release</i>, will be an improvement in
82: reliability, security and overall quality over the previous
83: <i>-release</i> and <i>-stable</i>.
84:
1.1 jason 85: <a name="getting"></a>
1.23 nick 86: <h3><font color="#0000e0">Getting <i>-stable</i> source code</font></h3>
1.1 jason 87:
88: <p>
1.19 nick 89: To obtain the patch branch for a particular release of OpenBSD, you
90: can update on top of a pre-existing source tree
91: (from <a href="ftp.html">FTP</a> or the <a href="orders.html">CD</a>)
92: or you can grab the source tree freshly from
93: an <a href="anoncvs.html">AnonCVS</a> server.
94: Instructions for getting the patch branch and staying up to date are
95: described in the <b>Getting Started</b> section of the
96: <a href="anoncvs.html#starting">AnonCVS documentation</a>.
97: Note that patch branches do not help to upgrade from one release of
1.29 ! sthen 98: OpenBSD to another, e.g. to go from 5.0 to 5.1. They only provide
1.19 nick 99: a means for staying up to date with the patches within a given release.
1.23 nick 100:
101: <p>
102: Do not attempt to go from one release to another via source.
1.29 ! sthen 103: Instead, please visit the <a href="faq/upgrade51.html">upgrade guide</a>.
1.19 nick 104: Also, you cannot go backwards, from -current back to -stable, because of
1.23 nick 105: library versioning problems and other changes.
1.1 jason 106:
107: <a name="building"></a>
1.23 nick 108: <h3><font color="#0000e0">Building OpenBSD <i>-stable</i></font></h3>
109: Full details on building from source are provided in
110: <a href="faq/faq5.html">FAQ 5 - Building the System from Source</a>.
111: This is a simplified summary.
112:
113: <p>
1.19 nick 114: Once you have obtained a source tree via <a href="anoncvs.html">anoncvs</a>,
115: you must rebuild the system. The stages for doing so are:
1.1 jason 116:
117: <ul>
1.19 nick 118: <li>Rebuild the kernel
119: <li>Reboot with the new kernel
120: <li>Rebuild the binaries
1.1 jason 121: </ul>
122:
1.22 nick 123: <h4><font color="#0000e0">Rebuilding the kernel</font></h4>
1.1 jason 124:
125: <p>
1.19 nick 126: To rebuild the default kernel from stable:
1.22 nick 127: <blockquote><pre>
1.3 ericj 128: # <strong>cd /usr/src/sys/arch/i386/conf</strong>
129: # <strong>/usr/sbin/config GENERIC</strong>
130: # <strong>cd /usr/src/sys/arch/i386/compile/GENERIC</strong>
131: # <strong>make clean && make depend && make</strong>
1.22 nick 132: </pre></blockquote>
1.1 jason 133:
134: <p>
1.19 nick 135: Replace <i>i386</i> with your architecture, e.g.
136: <i>sparc</i>, <i>alpha</i>, etc.
1.1 jason 137:
1.22 nick 138: <h4><font color="#0000e0">Rebooting with the new kernel</font></h4>
1.1 jason 139:
140: <p>
1.19 nick 141: To reboot with the newly compiled kernel:
1.22 nick 142: <blockquote><pre>
1.3 ericj 143: # <strong>cd /usr/src/sys/arch/i386/compile/GENERIC</strong>
1.23 nick 144: # <strong>make install</strong> <i>(Safely install new kernel)</i>
1.3 ericj 145: # <strong>reboot</strong>
1.22 nick 146: </pre></blockquote>
1.1 jason 147:
148: <p>
1.19 nick 149: As above, substitute your architecture for <i>i386</i>. If your system has
150: trouble booting the new kernel, you can easily go back and reboot from the
1.23 nick 151: old kernel, now called <i>obsd</i>.
1.1 jason 152:
1.22 nick 153: <h4><font color="#0000e0">Rebuilding the binaries</font></h4>
1.1 jason 154:
1.19 nick 155: <p> To rebuild the system binaries:
1.22 nick 156: <blockquote><pre>
1.16 steven 157: # <strong>rm -rf /usr/obj/*</strong>
1.3 ericj 158: # <strong>cd /usr/src</strong>
1.16 steven 159: # <strong>make obj</strong>
160: # <strong>cd /usr/src/etc && env DESTDIR=/ make distrib-dirs</strong>
161: # <strong>cd /usr/src</strong>
162: # <strong>make build</strong>
1.22 nick 163: </pre></blockquote>
1.1 jason 164:
1.19 nick 165: <p>This will take awhile...
1.23 nick 166:
167: <p>
168: If you have a number of machines to keep at <i>-stable</i>, you may wish to
169: make a <a href="faq/faq5.html#Release">release</a>, creating the
170: standard install <a href="faq/faq4.html#FilesNeeded">file sets</a>,
171: which can then be quickly and easily installed on any machine of the
172: same <a href="plat.html">platform</a>.
173:
1.1 jason 174: <hr>
1.19 nick 175: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.22 nick 176: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.29 ! sthen 177: <br><small>$OpenBSD: stable.html,v 1.28 2011/11/01 02:43:56 nick Exp $</small>
1.1 jason 178: </body>
179: </html>
1.19 nick 180:
![[BACK]](/icons/back.gif){kind=icon}
Return to stable.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www