UPDATING revision 146920
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. 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 2420050603: 25 The n_net of a struct netent was changed to an uint32_t, and 26 1st argument of getnetbyaddr() was changed to an uint32_t, to 27 conform to POSIX-2001. These changes broke an ABI 28 compatibility on 64 bit architecture. You have to recompile 29 userland programs that use getnetbyaddr(3), getnetbyname(3) 30 and/or getnetent(3) on 64 bit architecture. 31 3220050528: 33 Kernel parsing of extra options on '#!' first lines of shell 34 scripts has changed. Lines with multiple options likely will 35 fail after this date. For full details, please see 36 http://people.freebsd.org/~gad/Updating-20050528.txt 37 3820050503: 39 The packet filter (pf) code has been updated to OpenBSD 3.7 40 Please note the changed anchor syntax and the fact that 41 authpf(8) now needs a mounted fdescfs(5) to function. 42 4320050415: 44 The NO_MIXED_MODE kernel option has been removed from the i386 45 amd64 platforms as its use has been superceded by the new local 46 APIC timer code. Any kernel config files containing this option 47 should be updated. 48 4920050227: 50 The on-disk format of LC_CTYPE files was changed to be machine 51 independent. Please make sure NOT to use NO_CLEAN buildworld 52 when crossing this point. 53 5420050225: 55 The ifi_epoch member of struct if_data has been changed to 56 contain the uptime at which the interface was created or the 57 statistics zeroed rather then the wall clock time because 58 wallclock time may go backwards. This should have no impact 59 unless an snmp implementation is using this value (I know of 60 none at this point.) 61 6220050224: 63 The acpi_perf and acpi_throttle drivers are now part of the 64 acpi(4) main module. They are no longer built separately. 65 6620050223: 67 The layout of struct image_params has changed. You have to 68 recompile all compatibility modules (linux, svr4, etc) for use 69 with the new kernel. 70 7120050223: 72 The p4tcc driver has been merged into cpufreq(4). This makes 73 "options CPU_ENABLE_TCC" obsolete. Please load cpufreq.ko or 74 compile in "device cpufreq" to restore this functionality. 75 7620050220: 77 The responsibility of recomputing the file system summary of 78 a SoftUpdates-enabled dirty volume has been transferred to the 79 background fsck. A rebuild of fsck(8) utility is recommended 80 if you have updated the kernel. 81 82 To get the old behavior (recompute file system summary at mount 83 time), you can set vfs.ffs.compute_summary_at_mount=1 before 84 mounting the new volume. 85 8620050206: 87 The cpufreq import is complete. As part of this, the sysctls for 88 acpi(4) throttling have been removed. The power_profile script 89 has been updated, so you can use performance/economy_cpu_freq in 90 rc.conf(5) to set AC on/offline cpu frequencies. 91 9220050206: 93 NG_VERSION has been increased. Recompiling kernel (or ng_socket.ko) 94 requires recompiling libnetgraph and userland netgraph utilities. 95 9620050114: 97 Support for abbreviated forms of a number of ipfw options is 98 now deprecated. Warnings are printed to stderr indicating the 99 correct full form when a match occurs. Some abbreviations may 100 be supported at a later date based on user feedback. To be 101 considered for support, abbreviations must be in use prior to 102 this commit and unlikely to be confused with current key words. 103 10420041221: 105 By a popular demand, a lot of NOFOO options were renamed 106 to NO_FOO (see bsd.compat.mk for a full list). The old 107 spellings are still supported, but will cause annoying 108 warnings on stderr. Make sure you upgrade properly (see 109 the COMMON ITEMS: section later in this file). 110 11120041219: 112 Auto-loading of ancillary wlan modules such as wlan_wep has 113 been temporarily disabled; you need to statically configure 114 the modules you need into your kernel or explicitly load them 115 prior to use. Specifically, if you intend to use WEP encryption 116 with an 802.11 device load/configure wlan_wep; if you want to 117 use WPA with the ath driver load/configure wlan_tkip, wlan_ccmp, 118 and wlan_xauth as required. 119 12020041213: 121 The behaviour of ppp(8) has changed slightly. If lqr is enabled 122 (``enable lqr''), older versions would revert to LCP ECHO mode on 123 negotiation failure. Now, ``enable echo'' is required for this 124 behaviour. The ppp version number has been bumped to 3.4.2 to 125 reflect the change. 126 12720041201: 128 The wlan support has been updated to split the crypto support 129 into separate modules. For static WEP you must configure the 130 wlan_wep module in your system or build and install the module 131 in place where it can be loaded (the kernel will auto-load 132 the module when a wep key is configured). 133 13420041201: 135 The ath driver has been updated to split the tx rate control 136 algorithm into a separate module. You need to include either 137 ath_rate_onoe or ath_rate_amrr when configuring the kernel. 138 13920041116: 140 Support for systems with an 80386 CPU has been removed. Please 141 use FreeBSD 5.x or earlier on systems with an 80386. 142 14320041110: 144 We have had a hack which would mount the root filesystem 145 R/W if the device were named 'md*'. As part of the vnode 146 work I'm doing I have had to remove this hack. People 147 building systems which use preloaded MD root filesystems 148 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in 149 their /etc/rc scripts. 150 15120041104: 152 FreeBSD 5.3 shipped here. 153 15420041102: 155 The size of struct tcpcb has changed again due to the removal 156 of RFC1644 T/TCP. You have to recompile userland programs that 157 read kmem for tcp sockets directly (netstat, sockstat, etc.) 158 15920041022: 160 The size of struct tcpcb has changed. You have to recompile 161 userland programs that read kmem for tcp sockets directly 162 (netstat, sockstat, etc.) 163 16420041016: 165 RELENG_5 branched here. For older entries, please see updating 166 in the RELENG_5 branch. 167 168COMMON ITEMS: 169 170 General Notes 171 ------------- 172 Avoid using make -j when upgrading. From time to time in the 173 past there have been problems using -j with buildworld and/or 174 installworld. This is especially true when upgrading between 175 "distant" versions (eg one that cross a major release boundary 176 or several minor releases, or when several months have passed 177 on the -current branch). 178 179 Sometimes, obscure build problems are the result of environment 180 poisoning. This can happen because the make utility reads its 181 environment when searching for values for global variables. 182 To run your build attempts in an "environmental clean room", 183 prefix all make commands with 'env -i '. See the env(1) manual 184 page for more details. 185 186 To build a kernel 187 ----------------- 188 If you are updating from a prior version of FreeBSD (even one just 189 a few days old), you should follow this procedure. With a 190 /usr/obj tree with a fresh buildworld, 191 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 192 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 193 194 To test a kernel once 195 --------------------- 196 If you just want to boot a kernel once (because you are not sure 197 if it works, or if you want to boot a known bad kernel to provide 198 debugging information) run 199 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 200 nextboot -k testkernel 201 202 To just build a kernel when you know that it won't mess you up 203 -------------------------------------------------------------- 204 This assumes you are already running a 5.X system. Replace 205 ${arch} with the architecture of your machine (e.g. "i386", 206 "alpha", "amd64", "ia64", "pc98", "sparc64", etc). 207 208 cd src/sys/${arch}/conf 209 config KERNEL_NAME_HERE 210 cd ../compile/KERNEL_NAME_HERE 211 make depend 212 make 213 make install 214 215 If this fails, go to the "To build a kernel" section. 216 217 To rebuild everything and install it on the current system. 218 ----------------------------------------------------------- 219 # Note: sometimes if you are running current you gotta do more than 220 # is listed here if you are upgrading from a really old current. 221 222 <make sure you have good level 0 dumps> 223 make buildworld 224 make kernel KERNCONF=YOUR_KERNEL_HERE 225 [1] 226 <reboot in single user> [3] 227 mergemaster -p [5] 228 make installworld 229 mergemaster [4] 230 <reboot> 231 232 233 To cross-install current onto a separate partition 234 -------------------------------------------------- 235 # In this approach we use a separate partition to hold 236 # current's root, 'usr', and 'var' directories. A partition 237 # holding "/", "/usr" and "/var" should be about 2GB in 238 # size. 239 240 <make sure you have good level 0 dumps> 241 <boot into -stable> 242 make buildworld 243 make buildkernel KERNCONF=YOUR_KERNEL_HERE 244 <maybe newfs current's root partition> 245 <mount current's root partition on directory ${CURRENT_ROOT}> 246 make installworld DESTDIR=${CURRENT_ROOT} 247 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 248 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 249 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 250 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 251 <reboot into current> 252 <do a "native" rebuild/install as described in the previous section> 253 <maybe install compatibility libraries from src/lib/compat> 254 <reboot> 255 256 257 To upgrade in-place from 5.x-stable to current 258 ---------------------------------------------- 259 <make sure you have good level 0 dumps> 260 make buildworld [9] 261 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 262 [1] 263 <reboot in single user> [3] 264 mergemaster -p [5] 265 make installworld 266 mergemaster -i [4] 267 <reboot> 268 269 Make sure that you've read the UPDATING file to understand the 270 tweaks to various things you need. At this point in the life 271 cycle of current, things change often and you are on your own 272 to cope. The defaults can also change, so please read ALL of 273 the UPDATING entries. 274 275 Also, if you are tracking -current, you must be subscribed to 276 freebsd-current@freebsd.org. Make sure that before you update 277 your sources that you have read and understood all the recent 278 messages there. If in doubt, please track -stable which has 279 much fewer pitfalls. 280 281 [1] If you have third party modules, such as vmware, you 282 should disable them at this point so they don't crash your 283 system on reboot. 284 285 [3] From the bootblocks, boot -s, and then do 286 fsck -p 287 mount -u / 288 mount -a 289 cd src 290 adjkerntz -i # if CMOS is wall time 291 Also, when doing a major release upgrade, it is required that 292 you boot into single user mode to do the installworld. 293 294 [4] Note: This step is non-optional. Failure to do this step 295 can result in a significant reduction in the functionality of the 296 system. Attempting to do it by hand is not recommended and those 297 that pursue this avenue should read this file carefully, as well 298 as the archives of freebsd-current and freebsd-hackers mailing lists 299 for potential gotchas. 300 301 [5] Usually this step is a noop. However, from time to time 302 you may need to do this if you get unknown user in the following 303 step. It never hurts to do it all the time. You may need to 304 install a new mergemaster (cd src/usr.sbin/mergemaster && make 305 install) after the buildworld before this step if you last updated 306 from current before 20020224 or from -stable before 20020408. 307 308 [8] In order to have a kernel that can run the 4.x binaries 309 needed to do an installworld, you must include the COMPAT_FREEBSD4 310 option in your kernel. Failure to do so may leave you with a system 311 that is hard to boot to recover. 312 313 Make sure that you merge any new devices from GENERIC since the 314 last time you updated your kernel config file. 315 316 [9] When checking out sources, you must include the -P flag to have 317 cvs prune empty directories. 318 319 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 320 "?=" instead of the "=" assignment operator, so that buildworld can 321 override the CPUTYPE if it needs to. 322 323 MAKEOBJDIRPREFIX must be defined in an environment variable, and 324 not on the command line, or in /etc/make.conf. buildworld will 325 warn if it is improperly defined. 326FORMAT: 327 328This file contains a list, in reverse chronological order, of major 329breakages in tracking -current. Not all things will be listed here, 330and it only starts on October 16, 2004. Updating files can found in 331previous releases if your system is older than this. 332 333Copyright information: 334 335Copyright 1998-2005 M. Warner Losh. All Rights Reserved. 336 337Redistribution, publication, translation and use, with or without 338modification, in full or in part, in any form or format of this 339document are permitted without further permission from the author. 340 341THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 342IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 343WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 344DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 345INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 346(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 347SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 348HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 349STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 350IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 351POSSIBILITY OF SUCH DAMAGE. 352 353If you find this document useful, and you want to, you may buy the 354author a beer. 355 356Contact Warner Losh if you have any questions about your use of 357this document. 358 359$FreeBSD: head/UPDATING 146920 2005-06-03 09:15:17Z ume $ 360