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