upgrade revision 1.6 1 The upgrade to NetBSD 1.2 is a binary upgrade; it would be prohibitive
2 to make users upgrade by compiling and installing the 1.2 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 it is impractical to upgrade by recompiling from the sources and
6 installing.
7
8 To do the upgrade, you must have the NetBSD kernel on AmigaDOS and
9 you must transfer the upgrade file system upgr-12.fs onto the swap
10 partition of the NetBSD hard disk. You must also have at least the
11 "base12" binary distribution set available, so that you can upgrade
12 with it, using one of the upgrade methods described above. Finally,
13 you must have sufficient disk space available to install the new
14 binaries. Since the old binaries are being overwritten in place,
15 you only need space for the new binaries, which weren't previously
16 on the system. If you have a few megabytes free on each of your
17 root and /usr partitions, you should have enough space.
18
19 Since upgrading involves replacing the kernel, and most of the system
20 binaries, it has the potential to cause data loss. You are strongly
21 advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
22 NetBSD partition or on another operating system's partition, before
23 beginning the upgrade process.
24
25 To 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 'sd0*' (replacing 0 with the disk number that NetBSD used for
74 your root/swap device). The '*' character indicates that the
75 root file system is contained on the swap partition.
76 When you reach the prompt asking you for a shell name, just
77 hit return.
78
79 You will be presented with some information about the upgrade
80 process and a warning message, and will be asked if you wish
81 to proceed with the upgrade process. If you answer
82 negatively, the upgrade process will stop, and your disk will
83 not be modified. If you answer affirmatively, the upgrade
84 process will begin, and your disk will be modified. You may
85 hit Control-C to stop the upgrade process at any time.
86 However, if you hit it at an inopportune moment, your system
87 may be left in an inconsistent (and possibly unusable) state.
88
89 You will be asked if you wish to upgrade your file systems to
90 the new file system format. If you do, reply affirmatively.
91 If you don't have your file systems upgraded now, you should
92 probably do it manually after the install process is complete,
93 by using "fsck -c 2". Read the fsck(8) manual page for more
94 details.
95
96 The upgrade program will then check your root file system,
97 and, if you approved, will upgrade it to the new file system
98 format. It will then mount your root file system on /mnt.
99
100 If your file systems are being upgraded, the upgrade script
101 will copy the new fsck(8) program to your hard disk and
102 upgrade your remaining file systems.
103
104 The upgrade program will then mount all of your file systems
105 under /mnt. (In other words, your root partition will be
106 mounted on /mnt, your /usr partition on /mnt/usr, etc.)
107
108 If you don't already have the NetBSD distribution sets on your
109 disk, look in the installation section for information on how
110 to transfer them to your disk.
111
112 Once the distribution sets are transferred to your disk,
113 continue here. (Obviously, if the NetBSD distribution sets
114 are already on your disk, because you've transferred them
115 before starting the upgrade process, you don't need to
116 transfer them again now!)
117
118 After the software has been transferred to the machine (or
119 mounted, in the case of upgrading via NFS), change into the
120 directory containing the "base12" distribution set. Once you
121 are there, run the "Set_tmp_dir" command, and hit return at
122 the prompt to select the default answer for the temporary
123 directory's path name. (It should be the path name of the
124 directory that you're in.)
125
126 Run the command "Extract base12" to upgrade the base
127 distribution.
128
129 Repeat the above two steps for all of the sets you wish to
130 upgrade. (For each, change into the directory containing the
131 set, run "Set_tmp_dir" and accept the default path name, then
132 run the "Extract <setname>" command.)
133
134 If you were previously using the security distribution set,
135 you MUST upgrade to the new version, or you will not be able
136 to log in when the upgrade process is complete. Similarly, if
137 you were not previously using the security set, you must NOT
138 upgrade to the new version.
139
140 When you are done upgrading all of the distribution sets you
141 wish to upgrade, issue the command "Cleanup". It will clean
142 up the installation, by remaking some system databases, and
143 install the kernel and a bootblock onto the root partition.
144 When it is complete, you should use "halt" to halt the system.
145
146 Your system has now been upgraded to NetBSD 1.2.
147
148 After a new kernel has been copied to your hard disk, your
149 machine is a complete NetBSD 1.2 system. However, that
150 doesn't mean that you're finished with the upgrade process.
151 There are several things that you should do, or might have to
152 do, to insure that the system works properly.
153
154 First, if you did not upgrade your file systems to the new
155 file system format during the upgrade process, you may want to
156 do so now, with "fsck -c 2". If you are unsure about the
157 process, it's suggested that you read the fsck(8) manual page.
158
159 Second, you will probably want to get the etc12 distribution,
160 extract it, and compare its contents with those in your /etc/
161 directory. You will probably want to replace some of your
162 system configuration files, or incorporate some of the changes
163 in the new versions into yours.
164
165 Third, you will probably want to update the set of device
166 nodes you have in /dev. If you've changed the contents of
167 /dev by hand, you will need to be careful about this, but if
168 not, you can just cd into /dev, and run the command "sh
169 MAKEDEV all".
170
171 Fourth, you must deal with certain changes in the formats of
172 some of the configuration files. The most notable change is
173 that the "options" given to many of the file systems in
174 /etc/fstab or by hand have changed, and some of the file
175 systems have changed names. To find out what the new options
176 are, it's suggested that you read the manual page for the file
177 systems' mount commands, for example mount_nfs(8) for NFS.
178 (Note that the information for mounts of type "ffs", i.e. Fast
179 File Systems, are contained in the mount_ffs(8) man page.)
180
181 Finally, you will want to delete old binaries that were part
182 of the version of NetBSD that you upgraded from and have since
183 been removed from the NetBSD distribution. If upgrading from
184 a NetBSD version older than 1.0, you might also want to
185 recompile any locally-built binaries, to take advantage of the
186 shared libraries. (Note that any new binaries that you build
187 will be dynamically linked, and therefore take advantage of
188 the shared libraries, by default. For information on how to
189 make statically linked binaries, see the cc(1) and ld(1)
190 manual pages.)
191