OpenGrok

1.9.2.5  mycroft 	$NetBSD: upgrade,v 1.9.2.5 1998/05/29 03:42:10 mycroft Exp $
1.9.2.4  mycroft
1.9.2.4  mycroft The upgrade to NetBSD _VER is a binary upgrade; it can be quite difficult
1.9.2.4  mycroft to advance to a later version by recompiling from source due primarily
1.9.2.5  mycroft to interdependencies in the various components.
    1.1      cgd
1.9.2.1    perry To do the upgrade, you must have the boot floppy image (boot.fs)
1.9.2.1    perry available.  You must also have at least the "base" and "kern"
    1.7    perry binary distribution sets available, so that you can upgrade with it,
    1.7    perry using one of the upgrade methods described above.  Finally, you must
    1.7    perry have sufficient disk space available to install the new binaries.
    1.7    perry Since the old binaries are being overwritten in place, you only need
    1.7    perry space for the new binaries, which weren't previously on the system.
    1.7    perry If you have a few megabytes free on each of your root and /usr
    1.7    perry partitions, you should have enough space.
    1.1      cgd
    1.1      cgd Since upgrading involves replacing the boot blocks on your NetBSD
    1.1      cgd partition, the kernel, and most of the system binaries, it has the
    1.1      cgd potential to cause data loss.  You are strongly advised to BACK UP ANY
    1.1      cgd IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on
    1.1      cgd another operating system's partition, before beginning the upgrade
    1.1      cgd process.
    1.1      cgd
1.9.2.2    perry The upgrade procedure using the sysinst tool is basically the
1.9.2.3    perry same as an installation, but without the hard disk partitioning.
1.9.2.2    perry Another difference is that existing configuration files in /etc
1.9.2.2    perry are backed up, and merged with the new files. Getting the binary
1.9.2.2    perry sets is done in the same manner as the installation procedure;
1.9.2.2    perry refer to the installation part of the document, section 7 and 8,
1.9.2.2    perry on how to do this. Also, some sanity checks are done, i.e.
1.9.2.2    perry filesystems are checked before unpacking the sets.
1.9.2.2    perry
1.9.2.2    perry After a new kernel has been copied to your hard disk, your
1.9.2.2    perry machine is a complete NetBSD _VER system.  However, that
1.9.2.2    perry doesn't mean that you're finished with the upgrade process.
1.9.2.2    perry You will probably want to update the set of device
1.9.2.2    perry nodes you have in /dev.  If you've changed the contents of
1.9.2.2    perry /dev by hand, you will need to be careful about this, but if
1.9.2.2    perry not, you can just cd into /dev, and run the command "sh
1.9.2.2    perry MAKEDEV all".
1.9.2.2    perry
1.9.2.2    perry You must also deal with certain changes in the formats of
1.9.2.2    perry some of the configuration files.  The most notable change is
1.9.2.2    perry that the "options" given to many of the file systems in
1.9.2.2    perry /etc/fstab or by hand have changed, and some of the file
1.9.2.2    perry systems have changed names.  To find out what the new options
1.9.2.2    perry are, it's suggested that you read the manual page
1.9.2.2    perry for the file systems' mount commands, for example mount_nfs(8)
1.9.2.2    perry for NFS.
1.9.2.2    perry
1.9.2.2    perry Finally, you will want to delete old binaries that were part
1.9.2.2    perry of the version of NetBSD that you upgraded from and have since
1.9.2.2    perry been removed from the NetBSD distribution.