These instructions describe a procedure for doing a binary upgrade from an older version of &os;. While the &os; upgrade procedure does its best to safeguard against accidental loss of data, it is still more than possible to wipe out your entire disk with this installation! Please do not accept the final confirmation request unless you have adequately backed up any important data files. These notes assume that you are using the version of &man.sysinstall.8; supplied with the version of &os; to which you intend to upgrade. Using a mismatched version of &man.sysinstall.8; is almost guaranteed to cause problems and has been known to leave systems in an unusable state. The most commonly made mistake in this regard is the use of an old copy of &man.sysinstall.8; from an existing installation to upgrade to a newer version of &os;. This is not recommended. The upgrade procedure replaces distributions selected by the user with those corresponding to the new &os; release. It preserves standard system configuration data, as well as user data, installed packages and other software. Administrators contemplating an upgrade are encouraged to study this section in its entirety before commencing an upgrade. Failure to do so may result in a failed upgrade or loss of data. Upgrading of a distribution is performed by extracting the new version of the component over the top of the previous version. Files belonging to the old distribution are not deleted. System configuration is preserved by retaining and restoring the previous version of the following files: Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map, crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, host.conf, hosts.equiv, hosts.lpd, inetd.conf, kerberosIV, localtime, login.access, login.conf, mail, mail.rc, make.conf, manpath.config, master.passwd, modems, motd, namedb, networks, newsyslog.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp, printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local, remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells, skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp The versions of these files which correspond to the new version are moved to /etc/upgrade/. The system administrator may peruse these new versions and merge components as desired. Note that many of these files are interdependent, and the best merge procedure is to copy all site-specific data from the current files into the new. During the upgrade procedure, the administrator is prompted for a location into which all files from /etc/ are saved. In the event that local modifications have been made to other files, they may be subsequently retrieved from this location. This section details the upgrade procedure. Particular attention is given to items which substantially differ from a normal installation. User data and system configuration should be backed up before upgrading. While the upgrade procedure does its best to prevent accidental mistakes, it is possible to partially or completely destroy data and configuration information. The disklabel editor is entered with the nominated disk's filesystem devices listed. Prior to commencing the upgrade, the administrator should make a note of the device names and corresponding mountpoints. These mountpoints should be entered here. Do notset the newfs flag for any filesystems, as this will cause data loss. When selecting distributions, there are no constraints on which must be selected. As a general rule, the bin distribution should be selected for an update, and the man distribution if manpages are already installed. Other distributions may be selected beyond those originally installed if the administrator wishes to add additional functionality. Once the installation procedure has completed, the administrator is prompted to examine the new configuration files. At this point, checks should be made to ensure that the system configuration is valid. In particular, the /etc/rc.conf and /etc/fstab files should be checked. Those interested in an upgrade method that allows more flexibility and sophistication should take a look at the Upgrading FreeBSD from source tutorial found at http://www.FreeBSD.org/docs.html. This method requires reliable network connectivity, extra disk space and spare time, but has advantages for networks and other more complex installations.