upgrade revision 1.10 1 1.8 mhitch The upgrade to NetBSD _VER is a binary upgrade; it would be prohibitive
2 1.8 mhitch to make users upgrade by compiling and installing the _VER sources, and
3 1.2 chopps it would be very difficult to even compile a set of instructions that
4 1.2 chopps allowed them to do so. Because of the various changes to the system,
5 1.2 chopps it is impractical to upgrade by recompiling from the sources and
6 1.2 chopps installing.
7 1.2 chopps
8 1.3 jtc To do the upgrade, you must have the NetBSD kernel on AmigaDOS and
9 1.10 veego you must transfer the miniroot file system miniroot.fs onto the swap
10 1.3 jtc partition of the NetBSD hard disk. You must also have at least the
11 1.10 veego "base" binary distribution set available, so that you can upgrade
12 1.3 jtc with it, using one of the upgrade methods described above. Finally,
13 1.3 jtc you must have sufficient disk space available to install the new
14 1.3 jtc binaries. Since the old binaries are being overwritten in place,
15 1.3 jtc you only need space for the new binaries, which weren't previously
16 1.3 jtc on the system. If you have a few megabytes free on each of your
17 1.3 jtc root and /usr partitions, you should have enough space.
18 1.2 chopps
19 1.2 chopps Since upgrading involves replacing the kernel, and most of the system
20 1.2 chopps binaries, it has the potential to cause data loss. You are strongly
21 1.2 chopps advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
22 1.2 chopps NetBSD partition or on another operating system's partition, before
23 1.2 chopps beginning the upgrade process.
24 1.2 chopps
25 1.2 chopps To upgrade your system, follow the following instructions:
26 1.2 chopps
27 1.8 mhitch Transfer the miniroot file system onto the hard disk partition
28 1.8 mhitch used by NetBSD for swapping, as described in the "Preparing
29 1.8 mhitch your System for NetBSD Installation" section above.
30 1.3 jtc
31 1.8 mhitch Now boot up NetBSD using the _VER kernel using the loadbsd
32 1.3 jtc command:
33 1.3 jtc
34 1.3 jtc loadbsd -b netbsd
35 1.3 jtc
36 1.5 jtc If you machine has a split memory space, like, e.g., DraCo
37 1.4 chopps machines, use this instead:
38 1.4 chopps
39 1.4 chopps loadbsd -bn2 netbsd
40 1.4 chopps
41 1.6 is * Directly booting NetBSD, with boot blocks installed:
42 1.6 is
43 1.9 is [This description is for V40 (OS 3.1) ROMs. For older ROMs,
44 1.6 is there might be small differences. Check your AmigaOS documentation
45 1.6 is to learn about the exact procedure.]
46 1.6 is
47 1.8 mhitch [XXX another note about bootblock support?]
48 1.8 mhitch
49 1.6 is Reboot your machine, holding down both mouse buttons if you
50 1.6 is have a 2-button mouse, the outer mouse buttons if you have
51 1.6 is a 3-button mouse. On the DraCo, press the left mouse button
52 1.6 is instead, when the boot screen prompts you for it.
53 1.6 is
54 1.6 is From the boot menu, select "Boot Options".
55 1.6 is Select the swap partition with the miniroot, and then "ok".
56 1.6 is Select "Boot" now. The machine will boot the bootblock, which
57 1.6 is will prompt your for a command line. You have a few seconds time
58 1.6 is to change the default. Entering an empty line will accept the
59 1.6 is default.
60 1.6 is
61 1.6 is The bootblock uses command lines of the form:
62 1.6 is
63 1.6 is file options
64 1.6 is
65 1.6 is where file is the kernel file name on the partition where the
66 1.6 is boot block is on, and options are the same as with loadbsd.
67 1.6 is E.g., instead of "loadbsd -bsSn2 netbsd" use "netbsd -bsSn2".
68 1.6 is
69 1.6 is * Once your kernel boots:
70 1.6 is
71 1.3 jtc You should see the screen clear and some information about
72 1.3 jtc your system as the kernel configures the hardware. Note which
73 1.3 jtc hard disk device is configured that contains your root and
74 1.3 jtc swap partition. When prompted for the root device, type
75 1.7 is 'sd0b' (replacing 0 with the disk number that NetBSD used for
76 1.7 is your root/swap device). When you reach the prompt asking you
77 1.7 is for a shell name, just hit return.
78 1.2 chopps
79 1.2 chopps You will be presented with some information about the upgrade
80 1.2 chopps process and a warning message, and will be asked if you wish
81 1.2 chopps to proceed with the upgrade process. If you answer
82 1.2 chopps negatively, the upgrade process will stop, and your disk will
83 1.2 chopps not be modified. If you answer affirmatively, the upgrade
84 1.2 chopps process will begin, and your disk will be modified. You may
85 1.2 chopps hit Control-C to stop the upgrade process at any time.
86 1.2 chopps However, if you hit it at an inopportune moment, your system
87 1.2 chopps may be left in an inconsistent (and possibly unusable) state.
88 1.2 chopps
89 1.8 mhitch You will now be greeted and reminded of the fact that this is a
90 1.8 mhitch potential dangerous procedure and that you should not upgrade the
91 1.8 mhitch etc-set.
92 1.8 mhitch
93 1.8 mhitch When you decide to proceed, you will be prompted to enter
94 1.8 mhitch your root disk. After you've done this, it will be checked
95 1.8 mhitch automatically to make sure that the filesystem is in a sane
96 1.8 mhitch state before making any modifications. After this is done,
97 1.8 mhitch you will be asked if you want to configure your network.
98 1.8 mhitch
99 1.8 mhitch You are now allowed to edit your fstab. Normally you don't have
100 1.8 mhitch to. Note that the upgrade-kit uses it's own copy of the fstab.
101 1.8 mhitch Whatever you do here *won't* affect your actual fstab.
102 1.8 mhitch After you are satisfied with your fstab, the upgrade-kit will check
103 1.8 mhitch all filesystems mentioned in it. When they're ok, they will be
104 1.8 mhitch mounted.
105 1.8 mhitch
106 1.8 mhitch You will now be asked if your sets are stored on a normally
107 1.8 mhitch mounted filesystem. You should answer 'y' to this question if
108 1.8 mhitch you have the sets stored on a filesystem that was present in
109 1.8 mhitch the fstab. The actions you should take for the set extraction
110 1.8 mhitch are pretty logical (I think).
111 1.8 mhitch
112 1.8 mhitch After you have extracted the sets, the upgrade kit will proceed
113 1.8 mhitch with setting the timezone and installing the kernel and bootcode.
114 1.8 mhitch This is all exactly the same as described in the installation
115 1.8 mhitch section.
116 1.2 chopps
117 1.8 mhitch Your system has now been upgraded to NetBSD _VER.
118 1.2 chopps
119 1.4 chopps After a new kernel has been copied to your hard disk, your
120 1.8 mhitch machine is a complete NetBSD _VER system. However, that
121 1.2 chopps doesn't mean that you're finished with the upgrade process.
122 1.2 chopps There are several things that you should do, or might have to
123 1.2 chopps do, to insure that the system works properly.
124 1.2 chopps
125 1.10 veego You will probably want to get the etc distribution,
126 1.2 chopps extract it, and compare its contents with those in your /etc/
127 1.2 chopps directory. You will probably want to replace some of your
128 1.2 chopps system configuration files, or incorporate some of the changes
129 1.2 chopps in the new versions into yours.
130 1.2 chopps
131 1.8 mhitch You will want to delete old binaries that were part
132 1.2 chopps of the version of NetBSD that you upgraded from and have since
133 1.4 chopps been removed from the NetBSD distribution. If upgrading from
134 1.4 chopps a NetBSD version older than 1.0, you might also want to
135 1.4 chopps recompile any locally-built binaries, to take advantage of the
136 1.4 chopps shared libraries. (Note that any new binaries that you build
137 1.4 chopps will be dynamically linked, and therefore take advantage of
138 1.4 chopps the shared libraries, by default. For information on how to
139 1.4 chopps make statically linked binaries, see the cc(1) and ld(1)
140 1.4 chopps manual pages.)
141