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