Home | History | Annotate | Line # | Download | only in i386
upgrade revision 1.3
      1 The upgrade to NetBSD 1.0 is a binary upgrade; it would be prohibitive
      2 to make users upgrade by compiling and installing the 1.0 sources, and
      3 it would be very difficult to even compile a set of instructions that
      4 allowed them to do so.  Because of the various changes to the system,
      5 the largest being the 64-bit file size support and shared libraries,
      6 it is impractical to upgrade by recompiling from the sources and
      7 installing.
      8 
      9 To do the upgrade, you must have the appropriate kernel-copy floppy
     10 image on a disk, and the upgr-10.fs floppy image on another.  You must
     11 also have at least the "base10" binary distribution set available,
     12 so that you can upgrade with it, using one of the upgrade methods
     13 described above.  Finally, you must have sufficient disk space
     14 available to install the new binaries.  Since the old binaries are
     15 being overwritten in place, you only need space for the new binaries,
     16 which weren't previously on the system.  If you have a few megabytes
     17 free on each of your root and /usr partitions, you should have enough
     18 space.
     19 
     20 Since upgrading involves replacing the boot blocks on your NetBSD
     21 partition, the kernel, and most of the system binaries, it has the
     22 potential to cause data loss.  You are strongly advised to BACK UP ANY
     23 IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on
     24 another operating system's partition, before beginning the upgrade
     25 process.
     26 
     27 To upgrade your system, follow the following instructions:
     28 
     29 	Boot your machine using of the appropriate kernel-copy floppy.
     30 	When presented with the boot prompt (the prompt begins with
     31 	"Boot" and ends with ":-"), hit return.
     32 
     33 	You will be prompted to insert a file system floppy.  Remove
     34 	the kernel-copy floppy and insert the upgr-10 floppy, then hit
     35 	any key to continue booting.
     36 
     37 	While booting, you will probably see several warnings.  You
     38 	should be warned that no swap space is present, and that
     39 	init(8) cannot find /etc/rc.  Do not be alarmed, these are
     40 	completely normal.  When you reach the prompt asking you for a
     41 	shell name, just hit return.
     42 
     43 	You will be presented with some information about the upgrade
     44 	process and a warning message, and will be asked if you wish
     45 	to proceed with the upgrade process.  If you answer
     46 	negatively, the upgrade process will stop, and your disk will
     47 	not be modified.  If you answer affirmatively, the upgrade
     48 	process will begin, and your disk will be modified.  You may
     49 	hit Control-C to stop the upgrade process at any time.
     50 	However, if you hit it at an inopportune moment, your system
     51 	may be left in an inconsistent (and possibly unusable) state.
     52 
     53 	You will be asked if you wish to upgrade your file systems to
     54 	the new file system format.  If you do, reply affirmatively.
     55 	If you don't have your file systems upgraded now, you should
     56 	probably do it manually after the install process is complete,
     57 	by using "fsck -c 2". Read the fsck(8) manual page for more
     58 	details.
     59 
     60 	The upgrade program will then check your root file system,
     61 	and, if you approved, will upgrade it to the new file system
     62 	format.  It will then mount your root file system on /mnt.
     63 
     64 	If your file systems are being upgraded, the upgrade script
     65 	will copy the new fsck(8) program to your hard disk and
     66 	upgrade your remaining file systems.
     67 
     68 	The upgrade program will then automatically replace the boot
     69 	blocks on your disk with newer versions, and mount all of your
     70 	file systems under /mnt.  (In other words, your root partition
     71 	will be mounted on /mnt, your /usr partition on /mnt/usr, etc.)
     72 
     73 	If you don't already have the NetBSD distribution sets on your
     74 	disk, look in the installation section for information on how
     75 	to transfer them to your disk.
     76 
     77 	If you have only one floppy drive, and don't have the disk
     78 	space to copy all of the distribution onto the hard drive, you
     79 	can do the following:
     80 
     81 		Install a kernel on the hard drive as detailed a few
     82 		paragraphs below, then boot off the hard drive.  Now
     83 		you can copy and install distribution sets
     84 		incrementally from your lone floppy drive.
     85 
     86 	Once the distribution sets are transferred to your disk,
     87 	continue here.  (Obviously, if the NetBSD distribution sets
     88 	are already on your disk, because you've transferred them
     89 	before starting the upgrade process, you don't need to
     90 	transfer them again now!)
     91 
     92 	After the software has been transferred to the machine (or
     93 	mounted, in the case of upgrading via NFS), change into the
     94 	directory containing the "base10" distribution set.  Once you
     95 	are there, run the "Set_tmp_dir" command, and hit return at
     96 	the prompt to select the default answer for the temporary
     97 	directory's path name.  (It should be the path name of the
     98 	directory that you're in.)
     99 
    100 	Run the command "Extract base10" to upgrade the base
    101 	distribution.
    102 
    103 	Repeat the above two steps for all of the sets you wish to
    104 	upgrade.  (For each, change into the directory containing the
    105 	set, run "Set_tmp_dir" and accept the default path name, then
    106 	run the "Extract <setname>" command.)
    107 
    108 	If you were previously using the security distribution set,
    109 	you MUST upgrade to the new version, or you will not be able
    110 	to log in when the upgrade process is complete.  Similarly, if
    111 	you were not previously using the security set, you must NOT
    112 	upgrade to the new version.
    113 
    114 	When you are done upgrading all of the distribution sets you
    115 	wish to upgrade, issue the command "Cleanup".  It will clean
    116 	up the installation, by remaking some system databases.  When
    117 	it is complete, you should use "halt" to halt the system.
    118 
    119 	When the system is halted, remove the "upgr-10" floppy from
    120 	the floppy drive, and replace it with the NetBSD 1.0
    121 	kernel-copy floppy that you previously booted from. Reboot
    122 	with that floppy.
    123 
    124 	Once again, you will be prompted to insert a file system
    125 	floppy.  DO NOT replace the kernel-copy floppy, just hit any
    126 	key.
    127 
    128 	Again, While booting, you may see several warnings.  You may
    129 	be warned that no swap space is present, that init(8) cannot
    130 	find /etc/rc, and that one or more databases with names like
    131 	"pwd.db" cannot be found.  Do not be alarmed, as, again, these
    132 	are completely normal.  Hit return at the prompt asking you
    133 	for a shell name.
    134 
    135 	You will be presented with a shell prompt, at which you should
    136 	enter the "copy_kernel" command.  It will ask you what
    137 	partition to copy the kernel to, and you should reply with the
    138 	name of your root partition (e.g. sd0a or wd0a).
    139 
    140 	You will be asked if you are sure that you want to copy the
    141 	kernel.  Reply affirmatively, and it will check the file
    142 	system on your root partition, mount it, and copy the kernel.
    143 	Once the kernel is copied, you should use "halt" to halt the
    144 	system.
    145 
    146 	Once the system is halted, remove the kernel-copy floppy from
    147 	the floppy disk drive, and hit any key to reboot.
    148 
    149 Your system has now been upgraded to NetBSD 1.0.
    150 
    151 After a new kernel has been copied to your hard disk, your
    152 	machine is a complete NetBSD 1.0 system.  However, that
    153 	doesn't mean that you're finished with the upgrade process.
    154 	There are several things that you should do, or might have to
    155 	do, to insure that the system works properly.
    156 
    157 	First, if you did not upgrade your file systems to the new
    158 	file system format during the upgrade process, you may want to
    159 	do so now, with "fsck -c 2".  If you are unsure about the
    160 	process, it's suggested that you read the fsck(8) manual page.
    161 
    162 	Second, you will probably want to get the etc10 distribution,
    163 	extract it, and compare its contents with those in your /etc/
    164 	directory.  You will probably want to replace some of your
    165 	system configuration files, or incorporate some of the changes
    166 	in the new versions into yours.
    167 
    168 	Third, you will probably want to update the set of device
    169 	nodes you have in /dev.  If you've changed the contents of
    170 	/dev by hand, you will need to be careful about this, but if
    171 	not, you can just cd into /dev, and run the command "sh
    172 	MAKEDEV all".
    173 
    174 	Fourth, you must deal with certain changes in the formats of
    175 	some of the configuration files.  The most notable change is
    176 	that the "options" given to many of the file systems in
    177 	/etc/fstab or by hand have changed, and some of the file
    178 	systems have changed names.  To find out what the new options
    179 	are, it's suggested that you read the manual page for the
    180 	file systems' mount commands, for example mount_nfs(8) for
    181 	NFS.  (Note that the information for mounts of type "ufs",
    182 	i.e. Fast File Systems, are contained in the mount(8) man
    183 	page.)
    184 
    185 	Finally, you will want to delete old binaries that were part
    186 	of the version of NetBSD that you upgraded from and have since
    187 	been removed from the NetBSD distribution.  You might also
    188 	want to recompile any locally-built binaries, to take
    189 	advantage of the shared libraries.  (Note that any new
    190 	binaries that you build will be dynamically linked, and
    191 	therefore take advantage of the shared libraries, by default.
    192 	For information on how to make statically linked binaries,
    193 	see the cc(1) and ld(1) manual pages.)
    194