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