upgrade revision 1.5
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	You should see the screen clear and some information about
42	your system as the kernel configures the hardware.  Note which
43	hard disk device is configured that contains your root and
44	swap partition.  When prompted for the root device, type
45	'sd0*' (replacing 0 with the disk number that NetBSD used for
46	your root/swap device).  The '*' character indicates that the
47	root file system is contained on the swap partition.
48	When you reach the prompt asking you for a shell name, just
49	hit return.
50
51	You will be presented with some information about the upgrade
52	process and a warning message, and will be asked if you wish
53	to proceed with the upgrade process.  If you answer
54	negatively, the upgrade process will stop, and your disk will
55	not be modified.  If you answer affirmatively, the upgrade
56	process will begin, and your disk will be modified.  You may
57	hit Control-C to stop the upgrade process at any time.
58	However, if you hit it at an inopportune moment, your system
59	may be left in an inconsistent (and possibly unusable) state.
60
61	You will be asked if you wish to upgrade your file systems to
62	the new file system format.  If you do, reply affirmatively.
63	If you don't have your file systems upgraded now, you should
64	probably do it manually after the install process is complete,
65	by using "fsck -c 2". Read the fsck(8) manual page for more
66	details.
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 "base12" 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 base12" 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	
120Your system has now been upgraded to NetBSD 1.2.
121
122	After a new kernel has been copied to your hard disk, your
123	machine is a complete NetBSD 1.2 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 etc12 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 file
151	systems' mount commands, for example mount_nfs(8) for NFS.
152	(Note that the information for mounts of type "ffs", i.e. Fast
153	File Systems, are contained in the mount_ffs(8) man page.)
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.  If upgrading from
158	a NetBSD version older than 1.0, you might also want to
159	recompile any locally-built binaries, to take advantage of the
160	shared libraries.  (Note that any new binaries that you build
161	will be dynamically linked, and therefore take advantage of
162	the shared libraries, by default.  For information on how to
163	make statically linked binaries, see the cc(1) and ld(1)
164	manual pages.)
165