1The upgrade to NetBSD 1.2 is a binary upgrade; it would be prohibitive 2to make users upgrade by compiling and installing the 1.2 sources, and 3it would be very difficult to even compile a set of instructions that 4allowed them to do so. Because of the various changes to the system, 5it is impractical to upgrade by recompiling from the sources and 6installing. 7 8To do the upgrade, you must have the NetBSD kernel on AmigaDOS and 9you must transfer the upgrade file system upgr-12.fs onto the swap 10partition of the NetBSD hard disk. You must also have at least the 11"base12" binary distribution set available, so that you can upgrade 12with it, using one of the upgrade methods described above. Finally, 13you must have sufficient disk space available to install the new 14binaries. Since the old binaries are being overwritten in place, 15you only need space for the new binaries, which weren't previously 16on the system. If you have a few megabytes free on each of your 17root and /usr partitions, you should have enough space. 18 19Since upgrading involves replacing the kernel, and most of the system 20binaries, it has the potential to cause data loss. You are strongly 21advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the 22NetBSD partition or on another operating system's partition, before 23beginning the upgrade process. 24 25To upgrade your system, follow the following instructions: 26 27 Transfer the upgrade miniroot file system onto the hard disk 28 partition used by NetBSD for swapping, as described in the 29 "Preparing your System for NetBSD Installation" section above. 30 31 Now boot up NetBSD using the 1.2 kernel using the loadbsd 32 command: 33 34 loadbsd -b netbsd 35 36 If you machine has a split memory space, like, e.g., DraCo 37 machines, use this instead: 38 39 loadbsd -bn2 netbsd 40 41 * Directly booting NetBSD, with boot blocks installed: 42 43 [This description is for V41 (OS 3.1) ROMs. For older ROMs, 44 there might be small differences. Check your AmigaOS documentation 45 to learn about the exact procedure.] 46 47 Reboot your machine, holding down both mouse buttons if you 48 have a 2-button mouse, the outer mouse buttons if you have 49 a 3-button mouse. On the DraCo, press the left mouse button 50 instead, when the boot screen prompts you for it. 51 52 From the boot menu, select "Boot Options". 53 Select the swap partition with the miniroot, and then "ok". 54 Select "Boot" now. The machine will boot the bootblock, which 55 will prompt your for a command line. You have a few seconds time 56 to change the default. Entering an empty line will accept the 57 default. 58 59 The bootblock uses command lines of the form: 60 61 file options 62 63 where file is the kernel file name on the partition where the 64 boot block is on, and options are the same as with loadbsd. 65 E.g., instead of "loadbsd -bsSn2 netbsd" use "netbsd -bsSn2". 66 67 * Once your kernel boots: 68 69 You should see the screen clear and some information about 70 your system as the kernel configures the hardware. Note which 71 hard disk device is configured that contains your root and 72 swap partition. When prompted for the root device, type 73 'sd0b' (replacing 0 with the disk number that NetBSD used for 74 your root/swap device). When you reach the prompt asking you 75 for a shell name, just hit return. 76 77 You will be presented with some information about the upgrade 78 process and a warning message, and will be asked if you wish 79 to proceed with the upgrade process. If you answer 80 negatively, the upgrade process will stop, and your disk will 81 not be modified. If you answer affirmatively, the upgrade 82 process will begin, and your disk will be modified. You may 83 hit Control-C to stop the upgrade process at any time. 84 However, if you hit it at an inopportune moment, your system 85 may be left in an inconsistent (and possibly unusable) state. 86 87 You will be asked if you wish to upgrade your file systems to 88 the new file system format. If you do, reply affirmatively. 89 If you don't have your file systems upgraded now, you should 90 probably do it manually after the install process is complete, 91 by using "fsck -c 2". Read the fsck(8) manual page for more 92 details. 93 94 The upgrade program will then check your root file system, 95 and, if you approved, will upgrade it to the new file system 96 format. It will then mount your root file system on /mnt. 97 98 If your file systems are being upgraded, the upgrade script 99 will copy the new fsck(8) program to your hard disk and 100 upgrade your remaining file systems. 101 102 The upgrade program will then mount all of your file systems 103 under /mnt. (In other words, your root partition will be 104 mounted on /mnt, your /usr partition on /mnt/usr, etc.) 105 106 If you don't already have the NetBSD distribution sets on your 107 disk, look in the installation section for information on how 108 to transfer them to your disk. 109 110 Once the distribution sets are transferred to your disk, 111 continue here. (Obviously, if the NetBSD distribution sets 112 are already on your disk, because you've transferred them 113 before starting the upgrade process, you don't need to 114 transfer them again now!) 115 116 After the software has been transferred to the machine (or 117 mounted, in the case of upgrading via NFS), change into the 118 directory containing the "base12" distribution set. Once you 119 are there, run the "Set_tmp_dir" command, and hit return at 120 the prompt to select the default answer for the temporary 121 directory's path name. (It should be the path name of the 122 directory that you're in.) 123 124 Run the command "Extract base12" to upgrade the base 125 distribution. 126 127 Repeat the above two steps for all of the sets you wish to 128 upgrade. (For each, change into the directory containing the 129 set, run "Set_tmp_dir" and accept the default path name, then 130 run the "Extract <setname>" command.) 131 132 If you were previously using the security distribution set, 133 you MUST upgrade to the new version, or you will not be able 134 to log in when the upgrade process is complete. Similarly, if 135 you were not previously using the security set, you must NOT 136 upgrade to the new version. 137 138 When you are done upgrading all of the distribution sets you 139 wish to upgrade, issue the command "Cleanup". It will clean 140 up the installation, by remaking some system databases, and 141 install the kernel and a bootblock onto the root partition. 142 When it is complete, you should use "halt" to halt the system. 143 144Your system has now been upgraded to NetBSD 1.2. 145 146 After a new kernel has been copied to your hard disk, your 147 machine is a complete NetBSD 1.2 system. However, that 148 doesn't mean that you're finished with the upgrade process. 149 There are several things that you should do, or might have to 150 do, to insure that the system works properly. 151 152 First, if you did not upgrade your file systems to the new 153 file system format during the upgrade process, you may want to 154 do so now, with "fsck -c 2". If you are unsure about the 155 process, it's suggested that you read the fsck(8) manual page. 156 157 Second, you will probably want to get the etc12 distribution, 158 extract it, and compare its contents with those in your /etc/ 159 directory. You will probably want to replace some of your 160 system configuration files, or incorporate some of the changes 161 in the new versions into yours. 162 163 Third, you will probably want to update the set of device 164 nodes you have in /dev. If you've changed the contents of 165 /dev by hand, you will need to be careful about this, but if 166 not, you can just cd into /dev, and run the command "sh 167 MAKEDEV all". 168 169 Fourth, you must deal with certain changes in the formats of 170 some of the configuration files. The most notable change is 171 that the "options" given to many of the file systems in 172 /etc/fstab or by hand have changed, and some of the file 173 systems have changed names. To find out what the new options 174 are, it's suggested that you read the manual page for the file 175 systems' mount commands, for example mount_nfs(8) for NFS. 176 (Note that the information for mounts of type "ffs", i.e. Fast 177 File Systems, are contained in the mount_ffs(8) man page.) 178 179 Finally, you will want to delete old binaries that were part 180 of the version of NetBSD that you upgraded from and have since 181 been removed from the NetBSD distribution. If upgrading from 182 a NetBSD version older than 1.0, you might also want to 183 recompile any locally-built binaries, to take advantage of the 184 shared libraries. (Note that any new binaries that you build 185 will be dynamically linked, and therefore take advantage of 186 the shared libraries, by default. For information on how to 187 make statically linked binaries, see the cc(1) and ld(1) 188 manual pages.) 189