upgrade revision 1.8 1 1.6 ender The upgrade to NetBSD _VER is a binary upgrade; it would be prohibitive
2 1.6 ender to make users upgrade by compiling and installing the _VER sources, and
3 1.6 ender it would be very difficult to even compile a set of instructions that
4 1.6 ender allowed them to do so. Because of the many changes to the system, it
5 1.6 ender is difficult and impractical to upgrade by recompiling from the sources
6 1.6 ender and installing.
7 1.6 ender
8 1.7 scottr No automated upgrade procedure exists for upgrading to release _VER for the
9 1.7 scottr NetBSD/mac68k architecture. The current procedure is essentially to perform
10 1.5 ender a new install from scratch. It is hoped that there will be a good upgrade
11 1.5 ender procedure for future releases. Please feel free to volunteer to help
12 1.5 ender replace these installation tools.
13 1.5 ender
14 1.5 ender The following steps outline the current upgrade procedure. These steps
15 1.5 ender should help ease the upgrade process. Please read these instructions
16 1.5 ender carefully and completely before proceeding:
17 1.5 ender
18 1.5 ender 1) Since upgrading involves replacing the kernel and most of the system
19 1.5 ender binaries, it has the potential to cause data loss. You are strongly
20 1.5 ender advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
21 1.5 ender NetBSD partition or on another operating system's partition, before
22 1.5 ender beginning the upgrade process. Although the upgrade should not
23 1.5 ender damage your filesystem(s) in any way, you never know what may happen.
24 1.5 ender
25 1.8 ender 2) Download the distribution sets you want from the "mac68k/binary/sets"
26 1.5 ender subdirectory of the NetBSD _VER distribution. You will need the base
27 1.5 ender set and the kernel at a minimum. Be sure to download the files in
28 1.5 ender _binary_ mode. If you will be upgrading from within NetBSD, make sure
29 1.5 ender that you place the distribution sets on a filesystem you will be able to
30 1.5 ender reach from single-user mode.
31 1.5 ender
32 1.5 ender 3) Install the _VER kernel. You may either use the Installer utility
33 1.8 ender (included in the "installation/misc" subdirectory) or install from
34 1.8 ender within NetBSD (the latter is recommended for speed reasons). If you
35 1.8 ender choose the former, proceed as you normally would. If you choose to
36 1.8 ender install from within NetBSD, then boot (or shutdown) into single-user
37 1.8 ender mode and do the following:
38 1.5 ender
39 1.5 ender cd /
40 1.8 ender tar -zxvpf /path/to/kern.tgz
41 1.5 ender
42 1.5 ender There is no need to explicitly backup your old kernel since it will be
43 1.8 ender incapable of running many of the newer binaries you are about to
44 1.8 ender install (unless, of course, you have a backup copy of your older
45 1.8 ender binaries and want to revert to them for some reason).
46 1.5 ender
47 1.5 ender 4) If you are installing using the Installer, skip to step 5. Otherwise,
48 1.5 ender reboot into NetBSD in single-user mode. Run 'fsck -f' and then mount all
49 1.5 ender local partitions read/write. Usually 'mount -a -t nonfs' should do the
50 1.5 ender trick, but if you have several partitions on the same disk, take note of
51 1.5 ender the fact that a change in partition numbering may have moved a few of
52 1.5 ender your partitions around. You can do a 'disklabel sdX' (where X is a
53 1.5 ender drive on which you have NetBSD partitions) to see how the partitions are
54 1.5 ender currently layed out. It is likely that a partition has shifted into
55 1.8 ender 'sdXe', a slot that was often not available under previous releases of
56 1.8 ender NetBSD. If this is the case, you will need to manually mount your root
57 1.8 ender partition (via 'mount -w /') and edit your /etc/fstab file to reflect
58 1.8 ender the new partition layout. Unless you are familiar with 'ex' or 'ed',
59 1.8 ender the easiest way to fix your /etc/fstab file is probably to simply do a
60 1.8 ender 'cat > /etc/fstab' and type in the corrected file in its entirety.
61 1.5 ender
62 1.5 ender 5) Install the distribution sets. Keep in mind that the NetBSD _VER
63 1.8 ender distribution takes up a considerably larger amount of disk space than
64 1.8 ender did the 1.2 or 1.2.1 distributions. If you are using the Installer,
65 1.8 ender proceed normally (remember that you will need to mount non-root
66 1.8 ender partitions by hand using the MiniShell before installing). If you are
67 1.8 ender installing from within NetBSD, do the following:
68 1.5 ender
69 1.5 ender cd /
70 1.8 ender tar --unlink -zxvpf /path/to/base.tgz
71 1.5 ender
72 1.5 ender It is crucial that you use the '--unlink' flag when invoking tar or you
73 1.5 ender will fail to correctly overwrite some files. Keep in mind that there is
74 1.5 ender no going back once you have installed the base set short of a complete
75 1.8 ender re-install of an earlier distribution. Continue with the appropriate
76 1.8 ender command line for each of the other sets you wish to install except for
77 1.8 ender the etc set. If you are in the Installer, open up the Minishell and do
78 1.8 ender the following:
79 1.5 ender
80 1.5 ender cd /tmp
81 1.5 ender exit
82 1.5 ender
83 1.8 ender Now, use the Installer to install the etc set (it will install into
84 1.5 ender /tmp instead of the /etc/ directory).
85 1.5 ender
86 1.5 ender If you are in NetBSD, do the following instead:
87 1.5 ender
88 1.5 ender cd /tmp
89 1.8 ender tar --unlink -zxvpf /path/to/etc.tgz
90 1.5 ender
91 1.5 ender 6) If you are in the Installer, quit it and boot into NetBSD in single-user
92 1.5 ender mode. From there, 'cd' to the /tmp/etc directory and compare each file
93 1.5 ender there with your old files in /etc. You will probably want to replace
94 1.5 ender some of your system configuration files, or incorporate some of the
95 1.5 ender changes in the new versions into yours. You should take note of the
96 1.8 ender following when upgrading to the NetBSD _VER etc.tgz set:
97 1.5 ender
98 1.5 ender * The first file to pay attention to is /etc/rc.conf. This file did not
99 1.5 ender exist under NetBSD 1.2, but it is used to configure the rc scripts
100 1.8 ender under NetBSD _VER. Edit the file to your preferences, making sure
101 1.8 ender that you change the line that says:
102 1.5 ender
103 1.5 ender rc_configured=NO
104 1.5 ender
105 1.5 ender to read:
106 1.5 ender
107 1.5 ender rc_configured=YES
108 1.5 ender
109 1.5 ender This will enable all of the options you have configured in /etc/rc.conf.
110 1.5 ender
111 1.5 ender * The next important item to take note of is the new networking
112 1.5 ender configuration files. If you currently have an /etc/hostname.xxN file
113 1.8 ender (fill in the xx with either ae or sn and the X with a number), you will
114 1.8 ender need to convert it into an ifconfig.xxN file before networking
115 1.8 ender automatically works. The format for the new file is simply the
116 1.8 ender arguments which you would give to ifconfig on the command line. The
117 1.8 ender following is an example of the minimal ifconfig.xxN file:
118 1.5 ender
119 1.5 ender inet hostname.domain.dom netmask 0xffffff00
120 1.5 ender
121 1.5 ender Read the ifconfig(8) man page for more details on arguments to ifconfig.
122 1.5 ender Be sure to set
123 1.5 ender
124 1.5 ender auto_ifconfig=YES
125 1.5 ender
126 1.5 ender in /etc/rc.conf to ensure that your network interfaces will be brought
127 1.5 ender up automatically on boot.
128 1.5 ender
129 1.5 ender * Many of the options given to many of the file systems have changed,
130 1.5 ender and some of the file systems have changed names. IT IS IMPERATIVE THAT
131 1.5 ender YOU CHANGE ANY INSTANCES OF "ufs" IN /etc/fstab TO "ffs". To find out
132 1.5 ender more about different filesystem options, read the man page for the
133 1.5 ender associated mount command (e.g. mount_mfs(8) for MFS filesystems, note:
134 1.5 ender FFS type filesystems are documented in the mount(8) man page). If you
135 1.5 ender have not already done so, you may also need to correct /etc/fstab for
136 1.5 ender a shift in the partition numbering scheme. See step (4) above for more
137 1.5 ender details.
138 1.5 ender
139 1.5 ender * You will also probably want to upgrade your device nodes at this time
140 1.5 ender as well. Make sure you have installed the latest MAKEDEV script (it
141 1.5 ender should be included in the etc set) and perform the following commands:
142 1.5 ender
143 1.5 ender cd /dev
144 1.5 ender sh MAKEDEV all
145 1.5 ender
146 1.5 ender
147 1.5 ender 7) A number of binaries have changed their locations from NetBSD 1.2.1 to
148 1.5 ender NetBSD _VER (most of these have moved from /sbin to /usr/sbin). A few
149 1.5 ender binaries have been removed. It is probably best if you scan the
150 1.5 ender modification dates of the files in the /sbin directory. If there are
151 1.5 ender files in the directory which have newer counterparts in the /usr/sbin
152 1.5 ender directory, it is a very good idea to remove the older files (you will
153 1.5 ender probably run into difficulties later if you choose not to do this).
154 1.5 ender You should also check the /sbin, /bin, /usr/bin/, and /usr/sbin
155 1.5 ender directories for old binaries that are no longer part of the NetBSD
156 1.5 ender distribution and delete them as well. In general, all the files in a
157 1.5 ender particular distribution should have similar modification dates, so
158 1.5 ender looking at these is a good way of determining a file's age.
159 1.5 ender
160 1.5 ender 8) Run 'fsck -f' to make sure that your filesystem is still consistent. If
161 1.5 ender fsck reports any errors, fix them by answering 'y' to its suggested
162 1.5 ender solutions (note: if there are a large number of errors, you may wish
163 1.5 ender to stop and run 'fsck -fy' to automatically answer "yes" instead).
164 1.5 ender
165 1.5 ender 9) Exit from single-user mode and it should continue to boot into
166 1.5 ender multi-user mode.
167 1.5 ender
168 1.5 ender At this point you have successfully upgraded to NetBSD _VER.
169