|
Lines 58-71
Link Here
|
| 58 |
<sect1 xml:id="updating-upgrading-synopsis"> |
58 |
<sect1 xml:id="updating-upgrading-synopsis"> |
| 59 |
<title>Synopsis</title> |
59 |
<title>Synopsis</title> |
| 60 |
|
60 |
|
|
|
61 |
<para>Applying security patches in a timely manner and upgrading |
| 62 |
to a newer release of an operating system are important aspects |
| 63 |
of ongoing system administration.</para> |
| 64 |
|
| 61 |
<para>&os; is under constant development between releases. Some |
65 |
<para>&os; is under constant development between releases. Some |
| 62 |
people prefer to use the officially released versions, while |
66 |
people prefer to use the officially released versions, while |
| 63 |
others prefer to keep in sync with the latest developments. |
67 |
others prefer to keep in sync with the latest developments. |
| 64 |
However, even official releases are often updated with security |
68 |
However, even official releases are often updated with security |
| 65 |
and other critical fixes. Regardless of the version used, &os; |
69 |
and other critical fixes.</para> |
|
|
70 |
|
| 71 |
<para>Regardless of the version used, &os; |
| 66 |
provides all the necessary tools to keep the system updated, and |
72 |
provides all the necessary tools to keep the system updated, and |
| 67 |
allows for easy upgrades between versions. This chapter |
73 |
allows for easy upgrades between versions. This chapter |
| 68 |
describes how to track the development system and the basic |
74 |
describes how to track the latest changes and the basic |
| 69 |
tools for keeping a &os; system up-to-date.</para> |
75 |
tools for keeping a &os; system up-to-date.</para> |
| 70 |
|
76 |
|
| 71 |
<para>After reading this chapter, you will know:</para> |
77 |
<para>After reading this chapter, you will know:</para> |
|
Lines 72-80
Link Here
|
| 72 |
|
78 |
|
| 73 |
<itemizedlist> |
79 |
<itemizedlist> |
| 74 |
<listitem> |
80 |
<listitem> |
|
|
81 |
<para>Which upgrade strategy is right for you: binary-only, |
| 82 |
or source-based?</para> |
| 83 |
</listitem> |
| 84 |
|
| 85 |
<listitem> |
| 75 |
<para>How to keep a &os; system up-to-date with |
86 |
<para>How to keep a &os; system up-to-date with |
| 76 |
<application>freebsd-update</application> or |
87 |
<application>freebsd-update</application> (binary-only) or |
| 77 |
<application>Subversion</application>.</para> |
88 |
<application>Subversion</application> (source-based).</para> |
| 78 |
</listitem> |
89 |
</listitem> |
| 79 |
|
90 |
|
| 80 |
<listitem> |
91 |
<listitem> |
|
Lines 89-101
Link Here
|
| 89 |
</listitem> |
100 |
</listitem> |
| 90 |
|
101 |
|
| 91 |
<listitem> |
102 |
<listitem> |
| 92 |
<para>The difference between the two development |
103 |
<para>The difference between the two source development |
| 93 |
branches: &os.stable; and &os.current;.</para> |
104 |
branches: &os.stable; and &os.current;.</para> |
| 94 |
</listitem> |
105 |
</listitem> |
| 95 |
|
106 |
|
| 96 |
<listitem> |
107 |
<listitem> |
| 97 |
<para>How to rebuild and reinstall the entire base |
108 |
<para>How to rebuild and reinstall the entire base |
| 98 |
system.</para> |
109 |
system from source.</para> |
| 99 |
</listitem> |
110 |
</listitem> |
| 100 |
</itemizedlist> |
111 |
</itemizedlist> |
| 101 |
|
112 |
|
|
Lines 121-126
Link Here
|
| 121 |
</note> |
132 |
</note> |
| 122 |
</sect1> |
133 |
</sect1> |
| 123 |
|
134 |
|
|
|
135 |
<sect1 xml:id="updating-upgrading-strategy"> |
| 136 |
<info> |
| 137 |
<title>Choosing a Strategy</title> |
| 138 |
|
| 139 |
<authorgroup> |
| 140 |
<author> |
| 141 |
<personname> |
| 142 |
<firstname>Mark</firstname> |
| 143 |
<surname>Linimon</surname> |
| 144 |
</personname> |
| 145 |
<contrib>Written by </contrib> |
| 146 |
</author> |
| 147 |
</authorgroup> |
| 148 |
</info> |
| 149 |
|
| 150 |
<indexterm> |
| 151 |
<primary>Updating and Upgrading</primary> |
| 152 |
</indexterm> |
| 153 |
<indexterm> |
| 154 |
<primary>updating strategy</primary> |
| 155 |
<see>updating-upgrading</see> |
| 156 |
</indexterm> |
| 157 |
|
| 158 |
<para>With respect to the base system, there are two major strategies |
| 159 |
to choose from: binary-only, or source-based.</para> |
| 160 |
|
| 161 |
<variablelist> |
| 162 |
<varlistentry> |
| 163 |
<term><varname>binary-only</varname></term> |
| 164 |
|
| 165 |
<listitem> |
| 166 |
<para><emphasis>binary-only</emphasis> is best suited for users |
| 167 |
who have installed from a formal &os; release; who neither |
| 168 |
need nor desire to make customizations to their base system; |
| 169 |
who are using standard x86-based hardware; and who do not plan |
| 170 |
to use code from any experimental branches (e.g. graphics |
| 171 |
drivers).</para> |
| 172 |
</listitem> |
| 173 |
</varlistentry> |
| 174 |
|
| 175 |
<varlistentry> |
| 176 |
<term><varname>source-based</varname></term> |
| 177 |
|
| 178 |
<listitem> |
| 179 |
<para><emphasis>source-based</emphasis> is best suited for |
| 180 |
users who either will be making customizations to their |
| 181 |
base system, doing development work, working with embedded |
| 182 |
systems, incorporating code from experimental branches, |
| 183 |
or working on the less-supported architectures.</para> |
| 184 |
</listitem> |
| 185 |
</varlistentry> |
| 186 |
</variablelist> |
| 187 |
|
| 188 |
<para>For binary-only installations, the recommended tool is |
| 189 |
<xref linkend="updating-upgrading-freebsdupdate"/>.</para> |
| 190 |
|
| 191 |
<para>Other sections of this chapter are applicable to |
| 192 |
source-based installations: |
| 193 |
<xref linkend="current-stable"/>, |
| 194 |
<xref linkend="synching"/>, |
| 195 |
<xref linkend="makeworld"/>, and |
| 196 |
<xref linkend="small-lan"/>. |
| 197 |
</para> |
| 198 |
|
| 199 |
<para>Your choice of strategy for the base system does not |
| 200 |
affect your similar choices for documentation or ports/ |
| 201 |
packages.</para> |
| 202 |
|
| 203 |
</sect1> |
| 204 |
|
| 124 |
<sect1 xml:id="updating-upgrading-freebsdupdate"> |
205 |
<sect1 xml:id="updating-upgrading-freebsdupdate"> |
| 125 |
<info> |
206 |
<info> |
| 126 |
<title>&os; Update</title> |
207 |
<title>&os; Update</title> |
|
Lines 154-164
Link Here
|
| 154 |
<see>updating-upgrading</see> |
235 |
<see>updating-upgrading</see> |
| 155 |
</indexterm> |
236 |
</indexterm> |
| 156 |
|
237 |
|
| 157 |
<para>Applying security patches in a timely manner and upgrading |
238 |
<para>&os; includes a utility |
| 158 |
to a newer release of an operating system are important aspects |
|
|
| 159 |
of ongoing system administration. &os; includes a utility |
| 160 |
called <command>freebsd-update</command> which can be used to |
239 |
called <command>freebsd-update</command> which can be used to |
| 161 |
perform both these tasks.</para> |
240 |
apply security patches in a timely manner and upgrade |
|
|
241 |
to a newer release of the operating system.</para> |
| 162 |
|
242 |
|
| 163 |
<para>This utility supports binary security and errata updates to |
243 |
<para>This utility supports binary security and errata updates to |
| 164 |
&os;, without the need to manually compile and install the patch |
244 |
&os;, without the need to manually compile and install the patch |
|
Lines 168-173
Link Here
|
| 168 |
end-of-life dates are listed at <uri |
248 |
end-of-life dates are listed at <uri |
| 169 |
xlink:href="http://www.FreeBSD.org/security/">http://www.FreeBSD.org/security/</uri>.</para> |
249 |
xlink:href="http://www.FreeBSD.org/security/">http://www.FreeBSD.org/security/</uri>.</para> |
| 170 |
|
250 |
|
|
|
251 |
<note> |
| 252 |
<para>The list of supported architectures is not yet shown on |
| 253 |
that page, but the list will always include the x86-based |
| 254 |
architectures.</para> |
| 255 |
</note> |
| 256 |
|
| 171 |
<para>This utility also supports operating system upgrades to |
257 |
<para>This utility also supports operating system upgrades to |
| 172 |
minor point releases as well as upgrades to another release |
258 |
minor point releases as well as upgrades to another release |
| 173 |
branch. Before upgrading to a new release, review its release |
259 |
branch. Before upgrading to a new release, review its release |
|
Lines 2110-2116
Link Here
|
| 2110 |
|
2196 |
|
| 2111 |
<sect1 xml:id="small-lan"> |
2197 |
<sect1 xml:id="small-lan"> |
| 2112 |
<info> |
2198 |
<info> |
| 2113 |
<title>Tracking for Multiple Machines</title> |
2199 |
<title>Tracking for Multiple Machines using NFS</title> |
| 2114 |
|
2200 |
|
| 2115 |
<authorgroup> |
2201 |
<authorgroup> |
| 2116 |
<author> |
2202 |
<author> |
|
Lines 2131-2137
Link Here
|
| 2131 |
<para>When multiple machines need to track the same source tree, |
2217 |
<para>When multiple machines need to track the same source tree, |
| 2132 |
it is a waste of disk space, network bandwidth, and |
2218 |
it is a waste of disk space, network bandwidth, and |
| 2133 |
<acronym>CPU</acronym> cycles to have each system download the |
2219 |
<acronym>CPU</acronym> cycles to have each system download the |
| 2134 |
sources and rebuild everything. The solution is to have one |
2220 |
sources and rebuild everything. One solution is to have one |
| 2135 |
machine do most of the work, while the rest of the machines |
2221 |
machine do most of the work, while the rest of the machines |
| 2136 |
mount that work via <acronym>NFS</acronym>. This section |
2222 |
mount that work via <acronym>NFS</acronym>. This section |
| 2137 |
outlines a method of doing so. For more information about using |
2223 |
outlines a method of doing so. For more information about using |