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.3 2003/08/05 07:45:42 asmodai 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>localtime</filename>,
89 <filename>login.access</filename>,
90 <filename>login.conf</filename>,
91 <filename>mail</filename>,
92 <filename>mail.rc</filename>,
93 <filename>make.conf</filename>,
94 <filename>manpath.config</filename>,
95 <filename>master.passwd</filename>,
96 <filename>modems</filename>,
97 <filename>motd</filename>,
98 <filename>namedb</filename>,
99 <filename>networks</filename>,
100 <filename>newsyslog.conf</filename>,
101 <filename>nsmb.conf</filename>,
102 <filename>nsswitch.conf</filename>,
103 <filename>pam.conf</filename>,
104 <filename>passwd</filename>,
105 <filename>periodic</filename>,
106 <filename>ppp</filename>,
107 <filename>printcap</filename>,
108 <filename>profile</filename>,
109 <filename>pwd.db</filename>,
110 <filename>rc.conf</filename>,
111 <filename>rc.conf.local</filename>,
112 <filename>rc.firewall</filename>,
113 <filename>rc.local</filename>,
114 <filename>remote</filename>,
115 <filename>resolv.conf</filename>,
116 <filename>rmt</filename>,
117 <filename>sendmail.cf</filename>,
118 <filename>sendmail.cw</filename>,
119 <filename>services</filename>,
120 <filename>shells</filename>,
121 <filename>skeykeys</filename>,
122 <filename>spwd.db</filename>,
123 <filename>ssh</filename>,
124 <filename>syslog.conf</filename>,
125 <filename>ttys</filename>,
126 <filename>uucp</filename>
129 <para>The versions of these files which correspond to the new
130 version are moved to <filename>/etc/upgrade/</filename>. The
131 system administrator may peruse these new versions and merge
132 components as desired. Note that many of these files are
133 interdependent, and the best merge procedure is to copy all
134 site-specific data from the current files into the new.</para>
136 <para>During the upgrade procedure, the administrator is
137 prompted for a location into which all files from
138 <filename>/etc/</filename> are saved. In the event that local
139 modifications have been made to other files, they may be
140 subsequently retrieved from this location.</para>
146 <title>Procedure</title>
148 <para>This section details the upgrade procedure. Particular
149 attention is given to items which substantially differ from a
150 normal installation.</para>
153 <title>Backup</title>
155 <para>User data and system configuration should be backed up
156 before upgrading. While the upgrade procedure does its best
157 to prevent accidental mistakes, it is possible to partially or
158 completely destroy data and configuration information.</para>
162 <title>Mount Filesystems</title>
164 <para>The disklabel editor is entered with the nominated disk's
165 filesystem devices listed. Prior to commencing the upgrade, the
166 administrator should make a note of the device names and
167 corresponding mountpoints. These mountpoints should be entered
168 here. <emphasis>Do not</emphasis>set the <quote>newfs
169 flag</quote> for any filesystems, as this will cause data
174 <title>Select Distributions</title>
176 <para>When selecting distributions, there are no constraints
177 on which must be selected. As a general rule, the <literal>bin</literal>
178 distribution should be selected for an update, and the <literal>man</literal>
179 distribution if manpages are already installed. Other
180 distributions may be selected beyond those originally
181 installed if the administrator wishes to add additional
182 functionality.</para>
186 <title>After Installation</title>
188 <para>Once the installation procedure has completed, the
189 administrator is prompted to examine the new configuration
190 files. At this point, checks should be made to ensure that the
191 system configuration is valid. In particular, the
192 <filename>/etc/rc.conf</filename> and
193 <filename>/etc/fstab</filename> files should be checked.</para>
198 <title>Upgrading from Source Code</title>
200 <para>Those interested in an upgrade method that allows more
201 flexibility and sophistication should take a look at
203 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/cutting-edge.html">The
204 Cutting Edge</ulink> in the &os; Handbook. This procedure involves
205 rebuilding all of &os; from source code. It requires reliable
206 network connectivity, extra disk space, and time, but has
207 advantages for networks and other more complex
208 installations. This is roughly the same procedure as is used for
209 track the -STABLE or -CURRENT development branches.</para>
211 <para><filename>/usr/src/UPDATING</filename> contains important
212 information on updating a &os; system from source code. It lists
213 various issues resulting from changes in &os; that may affect an