=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/stable.html,v retrieving revision 1.22 retrieving revision 1.23 diff -u -r1.22 -r1.23 --- www/stable.html 2007/01/02 01:00:02 1.22 +++ www/stable.html 2007/01/02 15:14:06 1.23 @@ -1,13 +1,13 @@ -OpenBSD Patch Branches +Following -stable - + @@ -15,17 +15,21 @@ -[OpenBSD] + +[OpenBSD] + +

-

Patch Branches

+

Following -stable (the "Patch +branch")

-

Table Of Contents

+

@@ -37,18 +41,19 @@ important patches and fixes (i.e. those from the errata plus others which are obvious and simple, but do not deserve an errata entry) -and makes it available via CVS in addition to the -current source. Thus, users can choose three options :

+and makes it available via CVS, in addition to the +-current source. Thus, users can choose three options :

As a general principle, all -Errata entries will be merged into the patch +errata entries will be merged into the patch branch within 48 hours of when an errata is published. Other post release patches may be merged in as well, subject to a number of conditions:

+It is worth pointing out the name -stable refers ONLY to the API +and operations of OpenBSD not changing, not the overall reliability of +the system. +In fact, if things go as desired, the -current +flavor of OpenBSD, on its way to +becoming the next -release, will be an improvement in +reliability, security and overall quality over the previous +-release and -stable. + -

Getting a stable branch

+

Getting -stable source code

To obtain the patch branch for a particular release of OpenBSD, you @@ -79,13 +97,20 @@ Note that patch branches do not help to upgrade from one release of OpenBSD to another, e.g. to go from 3.9 to 4.0. They only provide a means for staying up to date with the patches within a given release. -If you are trying to go from one release to another via source, please visit -the upgrade guide. + +

+Do not attempt to go from one release to another via source. +Instead, please visit the upgrade guide. Also, you cannot go backwards, from -current back to -stable, because of -library versioning problems. +library versioning problems and other changes. -

Building from an OpenBSD patch branch

+

Building OpenBSD -stable

+Full details on building from source are provided in +FAQ 5 - Building the System from Source. +This is a simplified summary. + +

Once you have obtained a source tree via anoncvs, you must rebuild the system. The stages for doing so are: @@ -116,15 +141,14 @@ To reboot with the newly compiled kernel: 

 # cd /usr/src/sys/arch/i386/compile/GENERIC
-# cp /bsd /bsd.old          (Save an old copy of your kernel)
-# cp bsd /bsd               (Copy the new kernel into place)
+# make install          (Safely install new kernel)
 # reboot

As above, substitute your architecture for i386. If your system has trouble booting the new kernel, you can easily go back and reboot from the -old kernel, now called bsd.old. +old kernel, now called obsd.

Rebuilding the binaries

@@ -139,10 +163,18 @@

This will take awhile... + +

+If you have a number of machines to keep at -stable, you may wish to +make a release, creating the +standard install file sets, +which can then be quickly and easily installed on any machine of the +same platform. +

OpenBSD www@openbsd.org -
$OpenBSD: stable.html,v 1.22 2007/01/02 01:00:02 nick Exp $ +
$OpenBSD: stable.html,v 1.23 2007/01/02 15:14:06 nick Exp $