2 The FreeBSD Documentation Project
3 The FreeBSD French Documentation Project
8 This section contains the contents of the old UPGRADE.TXT
11 <sect1 xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="upgrading">
12 <title>***Non traduit ***Upgrading &os;</title>
14 <para>These instructions describe a procedure for doing a binary
15 upgrade from an older version of &os;.</para>
18 <para>While the &os; upgrade procedure does its best to
19 safeguard against accidental loss of data, it is still more than
20 possible to <emphasis>wipe out your entire disk</emphasis> with
21 this installation! Please do not accept the final confirmation
22 request unless you have adequately backed up any important data
27 <para>These notes assume that you are using the version of
28 &man.sysinstall.8; supplied with the version of &os; to which you
29 intend to upgrade. Using a mismatched version of &man.sysinstall.8; is
30 almost guaranteed to cause problems and has been known to leave
31 systems in an unusable state. The most commonly made mistake in
32 this regard is the use of an old copy of &man.sysinstall.8; from
33 an existing installation to upgrade to a newer version of
34 &os;. This is <emphasis>not</emphasis> recommended.</para>
38 <title>Introduction</title>
40 <para>The upgrade procedure replaces distributions selected by the
41 user with those corresponding to the new &os; release. It
42 preserves standard system configuration data, as well as user
43 data, installed packages and other software.</para>
45 <para>Administrators contemplating an upgrade are encouraged to
46 study this section in its entirety before commencing an upgrade.
47 Failure to do so may result in a failed upgrade or loss of data.</para>
50 <title>Upgrade Overview</title>
52 <para>Upgrading of a distribution is performed by extracting the
53 new version of the component over the top of the previous
54 version. Files belonging to the old distribution are not
57 <para>System configuration is preserved by retaining and
58 restoring the previous version of the following files:</para>
60 <para><filename>Xaccel.ini</filename>,
61 <filename>XF86Config</filename>,
62 <filename>adduser.conf</filename>,
63 <filename>aliases</filename>,
64 <filename>aliases.db</filename>,
65 <filename>amd.map</filename>,
66 <filename>crontab</filename>,
67 <filename>csh.cshrc</filename>,
68 <filename>csh.login</filename>,
69 <filename>csh.logout</filename>,
70 <filename>cvsupfile</filename>,
71 <filename>dhclient.conf</filename>,
72 <filename>disktab</filename>,
73 <filename>dm.conf</filename>,
74 <filename>dumpdates</filename>,
75 <filename>exports</filename>,
76 <filename>fbtab</filename>,
77 <filename>fstab</filename>,
78 <filename>ftpusers</filename>,
79 <filename>gettytab</filename>,
80 <filename>gnats</filename>,
81 <filename>group</filename>,
82 <filename>hosts</filename>,
83 <filename>hosts.allow</filename>,
84 <filename>hosts.equiv</filename>,
85 <filename>hosts.lpd</filename>,
86 <filename>inetd.conf</filename>,
87 <filename>localtime</filename>,
88 <filename>login.access</filename>,
89 <filename>login.conf</filename>,
90 <filename>mail</filename>,
91 <filename>mail.rc</filename>,
92 <filename>make.conf</filename>,
93 <filename>manpath.config</filename>,
94 <filename>master.passwd</filename>,
95 <filename>modems</filename>,
96 <filename>motd</filename>,
97 <filename>namedb</filename>,
98 <filename>networks</filename>,
99 <filename>newsyslog.conf</filename>,
100 <filename>nsmb.conf</filename>,
101 <filename>nsswitch.conf</filename>,
102 <filename>pam.conf</filename>,
103 <filename>passwd</filename>,
104 <filename>periodic</filename>,
105 <filename>ppp</filename>,
106 <filename>printcap</filename>,
107 <filename>profile</filename>,
108 <filename>pwd.db</filename>,
109 <filename>rc.conf</filename>,
110 <filename>rc.conf.local</filename>,
111 <filename>rc.firewall</filename>,
112 <filename>rc.local</filename>,
113 <filename>remote</filename>,
114 <filename>resolv.conf</filename>,
115 <filename>rmt</filename>,
116 <filename>sendmail.cf</filename>,
117 <filename>sendmail.cw</filename>,
118 <filename>services</filename>,
119 <filename>shells</filename>,
120 <filename>skeykeys</filename>,
121 <filename>spwd.db</filename>,
122 <filename>ssh</filename>,
123 <filename>syslog.conf</filename>,
124 <filename>ttys</filename>,
125 <filename>uucp</filename>
128 <para>The versions of these files which correspond to the new
129 version are moved to <filename>/etc/upgrade/</filename>. The
130 system administrator may peruse these new versions and merge
131 components as desired. Note that many of these files are
132 interdependent, and the best merge procedure is to copy all
133 site-specific data from the current files into the new.</para>
135 <para>During the upgrade procedure, the administrator is
136 prompted for a location into which all files from
137 <filename>/etc/</filename> are saved. In the event that local
138 modifications have been made to other files, they may be
139 subsequently retrieved from this location.</para>
145 <title>Procedure</title>
147 <para>This section details the upgrade procedure. Particular
148 attention is given to items which substantially differ from a
149 normal installation.</para>
152 <title>Backup</title>
154 <para>User data and system configuration should be backed up
155 before upgrading. While the upgrade procedure does its best
156 to prevent accidental mistakes, it is possible to partially or
157 completely destroy data and configuration information.</para>
161 <title>Mount Filesystems</title>
163 <para>The disklabel editor is entered with the nominated disk's
164 filesystem devices listed. Prior to commencing the upgrade, the
165 administrator should make a note of the device names and
166 corresponding mountpoints. These mountpoints should be entered
167 here. <emphasis>Do not</emphasis>set the <quote>newfs
168 flag</quote> for any filesystems, as this will cause data
173 <title>Select Distributions</title>
175 <para>When selecting distributions, there are no constraints
176 on which must be selected. As a general rule, the <literal>bin</literal>
177 distribution should be selected for an update, and the <literal>man</literal>
178 distribution if manpages are already installed. Other
179 distributions may be selected beyond those originally
180 installed if the administrator wishes to add additional
181 functionality.</para>
184 <sect3 xml:id="fstab">
185 <title>After Installation</title>
187 <para>Once the installation procedure has completed, the
188 administrator is prompted to examine the new configuration
189 files. At this point, checks should be made to ensure that the
190 system configuration is valid. In particular, the
191 <filename>/etc/rc.conf</filename> and
192 <filename>/etc/fstab</filename> files should be checked.</para>
197 <title>Upgrading from Source Code</title>
199 <para>Those interested in an upgrade method that allows more
200 flexibility and sophistication should take a look at
201 <link xlink:href="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html">The
202 Cutting Edge</link> in the &os; Handbook. This procedure involves
203 rebuilding all of &os; from source code. It requires reliable
204 network connectivity, extra disk space, and time, but has
205 advantages for networks and other more complex
206 installations. This is roughly the same procedure as is used for
207 track the -STABLE or -CURRENT development branches.</para>
209 <para><filename>/usr/src/UPDATING</filename> contains important
210 information on updating a &os; system from source code. It lists
211 various issues resulting from changes in &os; that may affect an