1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh 4<imp@village.org>. See end of file for further details. For commonly 5done items, please see the COMMON ITEMS: section later in the file. 6 7Items affecting the ports and packages system can be found in 8/usr/ports/UPDATING. Please read that file before running 9portupgrade. Important recent entries: 20040724 (default X changes). 10 11NOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW: 12 FreeBSD 6.x has many debugging features turned on, in 13 both the kernel and userland. These features attempt to detect 14 incorrect use of system primitives, and encourage loud failure 15 through extra sanity checking and fail stop semantics. They 16 also substantially impact system performance. If you want to 17 do performance measurement, benchmarking, and optimization, 18 you'll want to turn them off. This includes various WITNESS- 19 related kernel options, INVARIANTS, malloc debugging flags 20 in userland, and various verbose features in the kernel. Many 21 developers choose to disable these features on build machines 22 to maximize performance. 23 2420050206: 25 The cpufreq import is complete. As part of this, the sysctls for 26 acpi(4) throttling have been removed. The power_profile(8) script 27 has been updated, so you can use performance/economy_cpu_freq in 28 rc.conf(5) to set AC on/offline cpu frequencies. The acpi 29 throttling support has been merged into acpi_perf(4). 30 3120050206: 32 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko) 33 requires recompiling libnetgraph and userland netgraph utilities. 34 3520050114: 36 Support for abbreviated forms of a number of ipfw options is 37 now deprecated. Warnings are printed to stderr indicating the 38 correct full form when a match occurs. Some abbreviations may 39 be supported at a later date based on user feedback. To be 40 considered for support, abbreviations must be in use prior to 41 this commit and unlikely to be confused with current key words. 42 4320041221: 44 By a popular demand, a lot of NOFOO options were renamed 45 to NO_FOO (see bsd.compat.mk for a full list). The old 46 spellings are still supported, but will cause annoying 47 warnings on stderr. Make sure you upgrade properly (see 48 the COMMON ITEMS: section later in this file). 49 5020041219: 51 Auto-loading of ancillary wlan modules such as wlan_wep has 52 been temporarily disabled; you need to statically configure 53 the modules you need into your kernel or explicitly load them 54 prior to use. Specifically, if you intend to use WEP encryption 55 with an 802.11 device load/configure wlan_wep; if you want to 56 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp, 57 and wlan_xauth as required. 58 5920041213: 60 The behaviour of ppp(8) has changed slightly. If lqr is enabled 61 (``enable lqr''), older versions would revert to LCP ECHO mode on 62 negotiation failure. Now, ``enable echo'' is required for this 63 behaviour. The ppp version number has been bumped to 3.4.2 to 64 reflect the change. 65 6620041201: 67 The wlan support has been updated to split the crypto support 68 into separate modules. For static WEP you must configure the 69 wlan_wep module in your system or build and install the module 70 in place where it can be loaded (the kernel will auto-load 71 the module when a wep key is configured). 72 7320041201: 74 The ath driver has been updated to split the tx rate control 75 algorithm into a separate module. You need to include either 76 ath_rate_onoe or ath_rate_amrr when configuring the kernel. 77 7820041116: 79 Support for systems with an 80386 CPU has been removed. Please 80 use FreeBSD 5.x or earlier on systems with an 80386. 81 8220041110: 83 We have had a hack which would mount the root filesystem 84 R/W if the device were named 'md*'. As part of the vnode 85 work I'm doing I have had to remove this hack. People 86 building systems which use preloaded MD root filesystems 87 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in 88 their /etc/rc scripts. 89 9020041104: 91 FreeBSD 5.3 shipped here. 92 9320041102: 94 The size of struct tcpcb has changed again due to the removal 95 of RFC1644 T/TCP. You have to recompile userland programs that 96 read kmem for tcp sockets directly (netstat, sockstat, etc.) 97 9820041022: 99 The size of struct tcpcb has changed. You have to recompile 100 userland programs that read kmem for tcp sockets directly 101 (netstat, sockstat, etc.) 102 10320041016: 104 RELENG_5 branched here. For older entries, please see updating 105 in the RELENG_5 branch. 106 107COMMON ITEMS: 108 109 # NOTE: 5.x below applies to 6.0-current as well, for the 110 # moment. 4.any -> 5.any upgrade support will remain in 111 # place for 6.0 current, but after 5.3 RELEASE, the 4.any -> 112 # 6.0-current upgrade path will require moving through 5.3 113 # RELEASE or newer. 114 115 General Notes 116 ------------- 117 Avoid using make -j when upgrading. From time to time in the 118 past there have been problems using -j with buildworld and/or 119 installworld. This is especially true when upgrading between 120 "distant" versions (eg one that cross a major release boundary 121 or several minor releases, or when several months have passed 122 on the -current branch). 123 124 Sometimes, obscure build problems are the result of environment 125 poisoning. This can happen because the make utility reads its 126 environment when searching for values for global variables. 127 To run your build attempts in an "environmental clean room", 128 prefix all make commands with 'env -i '. See the env(1) manual 129 page for more details. 130 131 To build a kernel 132 ----------------- 133 If you are updating from a prior version of FreeBSD (even one just 134 a few days old), you should follow this procedure. With a 135 /usr/obj tree with a fresh buildworld, 136 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 137 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 138 139 To just build a kernel when you know that it won't mess you up 140 -------------------------------------------------------------- 141 This assumes you are already running a 5.X system. Replace 142 ${arch} with the architecture of your machine (e.g. "i386", 143 "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 144 145 cd src/sys/${arch}/conf 146 config KERNEL_NAME_HERE 147 cd ../compile/KERNEL_NAME_HERE 148 make depend 149 make 150 make install 151 152 If this fails, go to the "To build a kernel" section. 153 154 To rebuild everything and install it on the current system. 155 ----------------------------------------------------------- 156 # Note: sometimes if you are running current you gotta do more than 157 # is listed here if you are upgrading from a really old current. 158 159 <make sure you have good level 0 dumps> 160 <maybe fix /etc/fstab> [7] 161 make buildworld 162 make kernel KERNCONF=YOUR_KERNEL_HERE 163 [1] 164 <reboot in single user> [3] 165 src/etc/rc.d/preseedrandom [10] 166 mergemaster -p [5] 167 make installworld 168 mergemaster [4] 169 <reboot> 170 171 172 To cross-install current onto a separate partition 173 -------------------------------------------------- 174 # In this approach we use a separate partition to hold 175 # current's root, 'usr', and 'var' directories. A partition 176 # holding "/", "/usr" and "/var" should be about 2GB in 177 # size. 178 179 <make sure you have good level 0 dumps> 180 <boot into -stable> 181 make buildworld 182 <maybe newfs current's root partition> 183 <mount current's root partition on directory ${CURRENT_ROOT}> 184 make installworld DESTDIR=${CURRENT_ROOT} 185 make buildkernel KERNCONF=YOUR_KERNEL_HERE 186 cp src/sys/${ARCH}/conf/GENERIC.hints \ 187 ${CURRENT_ROOT}/boot/device.hints # as needed 188 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 189 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 190 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 191 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 192 <reboot into current> 193 <do a "native" rebuild/install as described in the previous section> 194 <maybe install compatibility libraries from src/lib/compat> 195 <reboot> 196 197 198 To upgrade in-place from 4.x-stable to current 199 ---------------------------------------------- 200 # 5.x uses more space than 4.x. Also, the location of kernel 201 # modules has changed. If you are installing 5.x onto a 4.x 202 # system, you'll need about 30MB of free disk space on your / 203 # partition. If you have less than this, you may encounter difficult 204 # to back out of problems with this procedure. If /tmp is on 205 # the / partition, you may want to completely remove all its content 206 # before upgrading, as this can be a common source of shortage of 207 # space on /. 208 209 <make sure you have good level 0 dumps> 210 <maybe fix /etc/fstab> [7] 211 make buildworld [9] 212 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2] 213 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 214 cd sys/boot ; make STRIP="" install [6] 215 [1] 216 <reboot in single user> [3] 217 src/etc/rc.d/preseedrandom [10] 218 mergemaster -p [5] 219 rm -rf /usr/include/g++ 220 make installworld 221 mergemaster -i [4] 222 <reboot> 223 224 Make sure that you've read the UPDATING file to understand the 225 tweaks to various things you need. At this point in the life 226 cycle of current, things change often and you are on your own 227 to cope. The defaults can also change, so please read ALL of 228 the UPDATING entries. 229 230 Also, if you are tracking -current, you must be subscribed to 231 freebsd-current@freebsd.org. Make sure that before you update 232 your sources that you have read and understood all the recent 233 messages there. If in doubt, please track -stable which has 234 much fewer pitfalls. 235 236 [1] If you have third party modules, such as vmware, you 237 should disable them at this point so they don't crash your 238 system on reboot. 239 240 [2] If you have legacy ISA devices, you may need to create 241 your own device.hints to reflect your unique hardware 242 configuration. 243 244 [3] From the bootblocks, boot -s, and then do 245 fsck -p 246 mount -u / 247 mount -a 248 cd src 249 adjkerntz -i # if CMOS is wall time 250 Also, when doing a major release upgrade, it is required that 251 you boot into single user mode to do the installworld. 252 For the 4.x -> 5.x upgrade, you will also see many messages about 253 needing to recompile your userland. These are harmless and can 254 be ignored while you proceed to the next step. 255 256 [4] Note: This step is non-optional. Failure to do this step 257 can result in a significant reduction in the functionality of the 258 system. Attempting to do it by hand is not recommended and those 259 that pursue this avenue should read this file carefully, as well 260 as the archives of freebsd-current and freebsd-hackers mailing lists 261 for potential gotchas. 262 263 [5] Usually this step is a noop. However, from time to time 264 you may need to do this if you get unknown user in the following 265 step. It never hurts to do it all the time. You may need to 266 install a new mergemaster (cd src/usr.sbin/mergemaster && make 267 install) after the buildworld before this step if you last updated 268 from current before 20020224 or from -stable before 20020408. 269 270 [6] 4.x boot loader can be used to boot a 5.x system, however 271 it is difficult to do that at best. If you wish to try, then 272 you should interrupt the boot and at the ok prompt type: 273 ok unload 274 ok boot /boot/kernel/kernel 275 If this fails to work, you must install a new boot loader as 276 described here. 277 278 [7] Before you upgrade, please make sure that you are not using 279 compatibility slices. These are device names of the form /dev/ad0a 280 without the actual slice name. These will break with 5.x and newer. 281 You generally must update these entries to use the post FreeBSD 282 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha 283 is not. 284 285 [8] In order to have a kernel that can run the 4.x binaries 286 needed to do an installworld, you must include the COMPAT_FREEBSD4 287 option in your kernel. Failure to do so may leave you with a system 288 that is hard to boot to recover. 289 290 Make sure that you merge any new devices from GENERIC since the 291 last time you updated your kernel config file. 292 293 [9] When checking out sources, you must include the -P flag to have 294 cvs prune empty directories. 295 296 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 297 "?=" instead of the "=" assignment operator, so that buildworld can 298 override the CPUTYPE if it needs to. 299 300 MAKEOBJDIRPREFIX must be defined in an environment variable, and 301 not on the command line, or in /etc/make.conf. buildworld will 302 warn if it is improperly defined. 303 304 In case you would like to avoid installing new packages of everything, 305 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x 306 compatibility libraries are built which should allow you to continue 307 using your existing software for a while. Alternatively, you can 308 install the misc/compat4x port. 309 310 [10] In order to create temporary files, /dev/random must be 311 initialized by feeding data into it. src/etc/rc.d/preseedrandom 312 takes care of this. 313FORMAT: 314 315This file contains a list, in reverse chronological order, of major 316breakages in tracking -current. Not all things will be listed here, 317and it only starts on March 15, 2000. Updating files can found in 318previous releases if your system is older than this. 319 320Copyright information: 321 322Copyright 1998-2004 M. Warner Losh. All Rights Reserved. 323 324Redistribution, publication, translation and use, with or without 325modification, in full or in part, in any form or format of this 326document are permitted without further permission from the author. 327 328THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 329IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 330WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 331DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 332INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 333(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 334SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 335HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 336STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 337IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 338POSSIBILITY OF SUCH DAMAGE. 339 340If you find this document useful, and you want to, you may buy the 341author a beer. 342 343Contact Warner Losh if you have any questions about your use of 344this document. 345 346$FreeBSD$ 347