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