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