upgrade revision 1.15 1 1.15 ross $NetBSD: upgrade,v 1.15 1998/05/12 00:00:19 ross Exp $
2 1.13 perry
3 1.14 ross The upgrade to NetBSD _VER is a binary upgrade; it can be quite difficult
4 1.14 ross to advance to a later version by recompiling from source due primarily
5 1.15 ross to interdependencies in the various components.
6 1.1 cgd
7 1.10 perry To do the upgrade, you must have the boot floppy image (boot.fs)
8 1.10 perry available. You must also have at least the "base" and "kern"
9 1.7 perry binary distribution sets available, so that you can upgrade with it,
10 1.7 perry using one of the upgrade methods described above. Finally, you must
11 1.7 perry have sufficient disk space available to install the new binaries.
12 1.7 perry Since the old binaries are being overwritten in place, you only need
13 1.7 perry space for the new binaries, which weren't previously on the system.
14 1.7 perry If you have a few megabytes free on each of your root and /usr
15 1.7 perry partitions, you should have enough space.
16 1.1 cgd
17 1.1 cgd Since upgrading involves replacing the boot blocks on your NetBSD
18 1.1 cgd partition, the kernel, and most of the system binaries, it has the
19 1.1 cgd potential to cause data loss. You are strongly advised to BACK UP ANY
20 1.1 cgd IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on
21 1.1 cgd another operating system's partition, before beginning the upgrade
22 1.1 cgd process.
23 1.1 cgd
24 1.11 fvdl The upgrade procedure using the sysinst tool is basically the
25 1.12 perry same as an installation, but without the hard disk partitioning.
26 1.11 fvdl Another difference is that existing configuration files in /etc
27 1.11 fvdl are backed up, and merged with the new files. Getting the binary
28 1.11 fvdl sets is done in the same manner as the installation procedure;
29 1.11 fvdl refer to the installation part of the document, section 7 and 8,
30 1.11 fvdl on how to do this. Also, some sanity checks are done, i.e.
31 1.11 fvdl filesystems are checked before unpacking the sets.
32 1.11 fvdl
33 1.11 fvdl After a new kernel has been copied to your hard disk, your
34 1.11 fvdl machine is a complete NetBSD _VER system. However, that
35 1.11 fvdl doesn't mean that you're finished with the upgrade process.
36 1.11 fvdl You will probably want to update the set of device
37 1.11 fvdl nodes you have in /dev. If you've changed the contents of
38 1.11 fvdl /dev by hand, you will need to be careful about this, but if
39 1.11 fvdl not, you can just cd into /dev, and run the command "sh
40 1.11 fvdl MAKEDEV all".
41 1.11 fvdl
42 1.11 fvdl You must also deal with certain changes in the formats of
43 1.11 fvdl some of the configuration files. The most notable change is
44 1.11 fvdl that the "options" given to many of the file systems in
45 1.11 fvdl /etc/fstab or by hand have changed, and some of the file
46 1.11 fvdl systems have changed names. To find out what the new options
47 1.11 fvdl are, it's suggested that you read the manual page
48 1.11 fvdl for the file systems' mount commands, for example mount_nfs(8)
49 1.11 fvdl for NFS.
50 1.11 fvdl
51 1.11 fvdl Finally, you will want to delete old binaries that were part
52 1.11 fvdl of the version of NetBSD that you upgraded from and have since
53 1.11 fvdl been removed from the NetBSD distribution.
54