📄 current-stable.html
字号:
through as part of the upgrading process. Reading the <ahref="http://lists.FreeBSD.org/mailman/listinfo/freebsd-current"target="_top">FreeBSD-CURRENT mailing list</a> and <ttclass="FILENAME">/usr/src/UPDATING</tt> will keep you up-to-date on other bootstrappingprocedures that sometimes become necessary as we move toward the next release.</p></li><li><p>Be active! If you are running FreeBSD-CURRENT, we want to know what you have to sayabout it, especially if you have suggestions for enhancements or bug fixes. Suggestionswith accompanying code are received most enthusiastically!</p></li></ol></div></div><div class="SECT2"><h2 class="SECT2"><a id="STABLE" name="STABLE">19.2.2 Staying Stable withFreeBSD</a></h2><div class="SECT3"><h3 class="SECT3"><a id="AEN27313" name="AEN27313">19.2.2.1 What IsFreeBSD-STABLE?</a></h3><p>FreeBSD-STABLE is our development branch from which major releases are made. Changesgo into this branch at a different pace, and with the general assumption that they havefirst gone into FreeBSD-CURRENT for testing. This is <span class="emphasis"><iclass="EMPHASIS">still</i></span> a development branch, however, and this means that atany given time, the sources for FreeBSD-STABLE may or may not be suitable for anyparticular purpose. It is simply another engineering development track, not a resourcefor end-users.</p></div><div class="SECT3"><h3 class="SECT3"><a id="AEN27319" name="AEN27319">19.2.2.2 Who NeedsFreeBSD-STABLE?</a></h3><p>If you are interested in tracking or contributing to the FreeBSD development process,especially as it relates to the next ``point'' release of FreeBSD, then you shouldconsider following FreeBSD-STABLE.</p><p>While it is true that security fixes also go into the FreeBSD-STABLE branch, you donot <span class="emphasis"><i class="EMPHASIS">need</i></span> to track FreeBSD-STABLE todo this. Every security advisory for FreeBSD explains how to fix the problem for thereleases it affects <a id="AEN27325" name="AEN27325" href="#FTN.AEN27325"><spanclass="footnote">[1]</span></a> , and tracking an entire development branch just forsecurity reasons is likely to bring in a lot of unwanted changes as well.</p><p>Although we endeavor to ensure that the FreeBSD-STABLE branch compiles and runs at alltimes, this cannot be guaranteed. In addition, while code is developed in FreeBSD-CURRENTbefore including it in FreeBSD-STABLE, more people run FreeBSD-STABLE thanFreeBSD-CURRENT, so it is inevitable that bugs and corner cases will sometimes be foundin FreeBSD-STABLE that were not apparent in FreeBSD-CURRENT.</p><p>For these reasons, we do <span class="emphasis"><i class="EMPHASIS">not</i></span>recommend that you blindly track FreeBSD-STABLE, and it is particularly important thatyou do not update any production servers to FreeBSD-STABLE without first thoroughlytesting the code in your development environment.</p><p>If you do not have the resources to do this then we recommend that you run the mostrecent release of FreeBSD, and use the binary update mechanism to move from release torelease.</p></div><div class="SECT3"><h3 class="SECT3"><a id="AEN27332" name="AEN27332">19.2.2.3 Using FreeBSD-STABLE</a></h3><ol type="1"><li><p>Join the <a href="http://lists.FreeBSD.org/mailman/listinfo/freebsd-stable"target="_top">freebsd-stable</a> list. This will keep you informed of build-dependenciesthat may appear in FreeBSD-STABLE or any other issues requiring special attention.Developers will also make announcements in this mailing list when they are contemplatingsome controversial fix or update, giving the users a chance to respond if they have anyissues to raise concerning the proposed change.</p><p>The <a href="http://lists.FreeBSD.org/mailman/listinfo/cvs-all"target="_top">cvs-all</a> list will allow you to see the commit log entry for each changeas it is made along with any pertinent information on possible side-effects.</p><p>To join these lists, or one of the others available go to <ahref="http://lists.FreeBSD.org/mailman/listinfo"target="_top">http://lists.FreeBSD.org/mailman/listinfo</a> and click on the list thatyou wish to subscribe to. Instructions on the rest of the procedure are availablethere.</p></li><li><p>If you are installing a new system and want it to be as stable as possible, you cansimply grab the latest dated branch snapshot from <ahref="ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/"target="_top">ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/snapshots/</a> and install itlike any other release. Or you can install the most recent FreeBSD-STABLE release fromthe <a href="mirrors.html">mirror sites</a> and follow the instructions below to upgradeyour system to the most up to date FreeBSD-STABLE source code.</p><p>If you are already running a previous release of FreeBSD and wish to upgrade viasources then you can easily do so from FreeBSD <a href="mirrors.html">mirror site</a>.This can be done in one of two ways:</p><ol type="a"><li><p>Use the <a href="cvsup.html">cvsup</a> program with the <ttclass="FILENAME">supfile</tt> named <tt class="FILENAME">stable-supfile</tt> from thedirectory <tt class="FILENAME">/usr/share/examples/cvsup</tt>. This is the mostrecommended method, since it allows you to grab the entire collection once and then onlywhat has changed from then on. Many people run <tt class="COMMAND">cvsup</tt> from <ttclass="COMMAND">cron</tt> to keep their sources up-to-date automatically. You have tocustomize the sample <tt class="FILENAME">supfile</tt> above, and configure <ahref="cvsup.html">cvsup</a> for your environment.</p></li><li><p>Use the <b class="APPLICATION"><a href="ctm.html">CTM</a></b> facility. If you do nothave a fast and inexpensive connection to the Internet, this is the method you shouldconsider using.</p></li></ol></li><li><p>Essentially, if you need rapid on-demand access to the source and communicationsbandwidth is not a consideration, use <tt class="COMMAND">cvsup</tt> or <ttclass="COMMAND">ftp</tt>. Otherwise, use <b class="APPLICATION">CTM</b>.</p></li><li><p>Before compiling FreeBSD-STABLE, read the <tt class="FILENAME">Makefile</tt> in <ttclass="FILENAME">/usr/src</tt> carefully. You should at least <ahref="makeworld.html">install a new kernel and rebuild the world</a> the first timethrough as part of the upgrading process. Reading the <ahref="http://lists.FreeBSD.org/mailman/listinfo/freebsd-stable"target="_top">FreeBSD-STABLE mailing list</a> and <ttclass="FILENAME">/usr/src/UPDATING</tt> will keep you up-to-date on other bootstrappingprocedures that sometimes become necessary as we move toward the next release.</p></li></ol></div></div></div><h3 class="FOOTNOTES">Notes</h3><table border="0" class="FOOTNOTES" width="100%"><tr><td align="LEFT" valign="TOP" width="5%"><a id="FTN.AEN27325" name="FTN.AEN27325"href="current-stable.html#AEN27325"><span class="footnote">[1]</span></a></td><td align="LEFT" valign="TOP" width="95%"><p>That is not quite true. We can not continue to support old releases of FreeBSDforever, although we do support them for many years. For a complete description of thecurrent security policy for old releases of FreeBSD, please see <ahref="../../../../security/" target="_top">http://www.FreeBSD.org/security/</a>.</p></td></tr></table><div class="NAVFOOTER"><hr align="LEFT" width="100%" /><table summary="Footer navigation table" width="100%" border="0" cellpadding="0"cellspacing="0"><tr><td width="33%" align="left" valign="top"><a href="cutting-edge.html"accesskey="P">Prev</a></td><td width="34%" align="center" valign="top"><a href="index.html"accesskey="H">Home</a></td><td width="33%" align="right" valign="top"><a href="synching.html"accesskey="N">Next</a></td></tr><tr><td width="33%" align="left" valign="top">The Cutting Edge</td><td width="34%" align="center" valign="top"><a href="cutting-edge.html"accesskey="U">Up</a></td><td width="33%" align="right" valign="top">Synchronizing Your Source</td></tr></table></div><p align="center"><small>This, and other documents, can be downloaded from <ahref="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/">ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/</a>.</small></p><p align="center"><small>For questions about FreeBSD, read the <ahref="http://www.FreeBSD.org/docs.html">documentation</a> before contacting <<ahref="mailto:questions@FreeBSD.org">questions@FreeBSD.org</a>>.<br />For questions about this documentation, e-mail <<ahref="mailto:doc@FreeBSD.org">doc@FreeBSD.org</a>>.</small></p></body></html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -