UPDATING revision 247814
1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4See end of file for further details. For commonly done items, please see the 5COMMON ITEMS: section later in the file. These instructions assume that you 6basically know what you are doing. If not, then please consult the FreeBSD 7handbook: 8 9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html 10 11Items affecting the ports and packages system can be found in 12/usr/ports/UPDATING. Please read that file before running portupgrade. 13 14NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW: 15 FreeBSD 10.x has many debugging features turned on, in both the kernel 16 and userland. These features attempt to detect incorrect use of 17 system primitives, and encourage loud failure through extra sanity 18 checking and fail stop semantics. They also substantially impact 19 system performance. If you want to do performance measurement, 20 benchmarking, and optimization, you'll want to turn them off. This 21 includes various WITNESS- related kernel options, INVARIANTS, malloc 22 debugging flags in userland, and various verbose features in the 23 kernel. Many developers choose to disable these features on build 24 machines to maximize performance. (To completely disable malloc 25 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely 26 disable the most expensive debugging functionality run 27 "ln -s 'abort:false,junk:false' /etc/malloc.conf".) 28 2920130304: 30 The ctl device has been re-enabled in GENERIC for i386 and amd64, 31 but does not initialize by default (because of the new CTL_DISABLE 32 option) to save memory. To re-enable it, remove the CTL_DISABLE 33 option from the kernel config file or set kern.cam.ctl.disable=0 34 in /boot/loader.conf. 35 3620130301: 37 The ctl device has been disabled in GENERIC for i386 and amd64. 38 This was done due to the extra memory being allocated at system 39 initialisation time by the ctl driver which was only used if 40 a CAM target device was created. This makes a FreeBSD system 41 unusable on 128MB or less of RAM. 42 4320130208: 44 A new compression method (lz4) has been merged to -HEAD. Please 45 refer to zpool-features(7) for more information. 46 47 Please refer to the "ZFS notes" section of this file for information 48 on upgrading boot ZFS pools. 49 5020130129: 51 A BSD-licensed patch(1) variant has been added and is installed 52 as bsdpatch, being the GNU version the default patch. 53 To inverse the logic and use the BSD-licensed one as default, 54 while having the GNU version installed as gnupatch, rebuild 55 and install world with the WITH_BSD_PATCH knob set. 56 5720130118: 58 The install(1) option -M has changed meaning and now takes an 59 argument that is a file or path to append logs to. In the 60 unlikely event that -M was the last option on the command line 61 and the command line contained at least two files and a target 62 directory the first file will have logs appended to it. The -M 63 option served little practical purpose in the last decade so its 64 use is expected to be extremely rare. 65 6620121223: 67 After switching to Clang as the default compiler some users of ZFS 68 on i386 systems started to experience stack overflow kernel panics. 69 Please consider using 'options KSTACK_PAGES=4' in such configurations. 70 7120121222: 72 GEOM_LABEL now mangles label names read from file system metadata. 73 Mangling affect labels containing spaces, non-printable characters, 74 '%' or '"'. Device names in /etc/fstab and other places may need to 75 be updated. 76 7720121217: 78 By default, only the 10 most recent kernel dumps will be saved. To 79 restore the previous behaviour (no limit on the number of kernel dumps 80 stored in the dump directory) add the following line to /etc/rc.conf: 81 82 savecore_flags="" 83 8420121201: 85 With the addition of auditdistd(8), a new auditdistd user is now 86 depended on during installworld. "mergemaster -p" can be used to add 87 the user prior to installworld, as documented in the handbook. 88 8920121117: 90 The sin6_scope_id member variable in struct sockaddr_in6 is now 91 filled by the kernel before passing the structure to the userland via 92 sysctl or routing socket. This means the KAME-specific embedded scope 93 id in sin6_addr.s6_addr[2] is always cleared in userland application. 94 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 95 __FreeBSD_version is bumped to 1000025. 96 9720121105: 98 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 99 This means that the world and kernel will be compiled with clang 100 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 101 and /usr/bin/cpp. To disable this behavior and revert to building 102 with gcc, compile with WITHOUT_CLANG_IS_CC. 103 10420121102: 105 The IPFIREWALL_FORWARD kernel option has been removed. Its 106 functionality now turned on by default. 107 10820121023: 109 The ZERO_COPY_SOCKET kernel option has been removed and 110 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 111 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 112 mechanism which is not safe and may result in kernel crashes. 113 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 114 driver supports disposeable external page sized mbuf storage. 115 Proper replacements for both zero-copy mechanisms are under 116 consideration and will eventually lead to complete removal 117 of the two kernel options. 118 11920121023: 120 The IPv4 network stack has been converted to network byte 121 order. The following modules need to be recompiled together 122 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 123 pf(4), ipfw(4), ng_ipfw(4), stf(4). 124 12520121022: 126 Support for non-MPSAFE filesystems was removed from VFS. The 127 VFS_VERSION was bumped, all filesystem modules shall be 128 recompiled. 129 13020121018: 131 All the non-MPSAFE filesystems have been disconnected from 132 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 133 portalfs, smbfs, xfs. 134 13520121016: 136 The interface cloning API and ABI has changed. The following 137 modules need to be recompiled together with kernel: 138 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 139 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 140 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 141 14220121015: 143 The sdhci driver was split in two parts: sdhci (generic SD Host 144 Controller logic) and sdhci_pci (actual hardware driver). 145 No kernel config modifications are required, but if you 146 load sdhc as a module you must switch to sdhci_pci instead. 147 14820121014: 149 Import the FUSE kernel and userland support into base system. 150 15120121013: 152 The GNU sort(1) program has been removed since the BSD-licensed 153 sort(1) has been the default for quite some time and no serious 154 problems have been reported. The corresponding WITH_GNU_SORT 155 knob has also gone. 156 15720121006: 158 The pfil(9) API/ABI for AF_INET family has been changed. Packet 159 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 160 with new kernel. 161 16220121001: 163 The net80211(4) ABI has been changed to allow for improved driver 164 PS-POLL and power-save support. All wireless drivers need to be 165 recompiled to work with the new kernel. 166 16720120913: 168 The random(4) support for the VIA hardware random number 169 generator (`PADLOCK') is no longer enabled unconditionally. 170 Add the PADLOCK_RNG option in the custom kernel config if 171 needed. The GENERIC kernels on i386 and amd64 do include the 172 option, so the change only affects the custom kernel 173 configurations. 174 17520120908: 176 The pf(4) packet filter ABI has been changed. pfctl(8) and 177 snmp_pf module need to be recompiled to work with new kernel. 178 17920120828: 180 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 181 to -HEAD. Pools that have empty_bpobj in active state can not be 182 imported read-write with ZFS implementations that do not support 183 this feature. For more information read the zpool-features(5) 184 manual page. 185 18620120727: 187 The sparc64 ZFS loader has been changed to no longer try to auto- 188 detect ZFS providers based on diskN aliases but now requires these 189 to be explicitly listed in the OFW boot-device environment variable. 190 19120120712: 192 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 193 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 194 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 195 19620120712: 197 The following sysctls and tunables have been renamed for consistency 198 with other variables: 199 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 200 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 201 20220120628: 203 The sort utility has been replaced with BSD sort. For now, GNU sort 204 is also available as "gnusort" or the default can be set back to 205 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 206 installed as "bsdsort". 207 20820120611: 209 A new version of ZFS (pool version 5000) has been merged to -HEAD. 210 Starting with this version the old system of ZFS pool versioning 211 is superseded by "feature flags". This concept enables forward 212 compatibility against certain future changes in functionality of ZFS 213 pools. The first read-only compatible "feature flag" for ZFS pools 214 is named "com.delphix:async_destroy". For more information 215 read the new zpool-features(5) manual page. 216 Please refer to the "ZFS notes" section of this file for information 217 on upgrading boot ZFS pools. 218 21920120417: 220 The malloc(3) implementation embedded in libc now uses sources imported 221 as contrib/jemalloc. The most disruptive API change is to 222 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 223 delete it prior to installworld, and optionally re-create it using the 224 new format after rebooting. See malloc.conf(5) for details 225 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 226 NAMESPACE section). 227 22820120328: 229 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 230 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 231 now spelled mips. This is to aid compatibility with third-party 232 software that expects this naming scheme in uname(3). Little-endian 233 settings are unchanged. 234 23520120306: 236 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 237 platforms. 238 23920120229: 240 Now unix domain sockets behave "as expected" on nullfs(5). Previously 241 nullfs(5) did not pass through all behaviours to the underlying layer, 242 as a result if we bound to a socket on the lower layer we could connect 243 only to the lower path; if we bound to the upper layer we could connect 244 only to the upper path. The new behavior is one can connect to both the 245 lower and the upper paths regardless what layer path one binds to. 246 24720120211: 248 The getifaddrs upgrade path broken with 20111215 has been restored. 249 If you have upgraded in between 20111215 and 20120209 you need to 250 recompile libc again with your kernel. You still need to recompile 251 world to be able to configure CARP but this restriction already 252 comes from 20111215. 253 25420120114: 255 The set_rcvar() function has been removed from /etc/rc.subr. All 256 base and ports rc.d scripts have been updated, so if you have a 257 port installed with a script in /usr/local/etc/rc.d you can either 258 hand-edit the rcvar= line, or reinstall the port. 259 260 An easy way to handle the mass-update of /etc/rc.d: 261 rm /etc/rc.d/* && mergemaster -i 262 26320120109: 264 panic(9) now stops other CPUs in the SMP systems, disables interrupts 265 on the current CPU and prevents other threads from running. 266 This behavior can be reverted using the kern.stop_scheduler_on_panic 267 tunable/sysctl. 268 The new behavior can be incompatible with kern.sync_on_panic. 269 27020111215: 271 The carp(4) facility has been changed significantly. Configuration 272 of the CARP protocol via ifconfig(8) has changed, as well as format 273 of CARP events submitted to devd(8) has changed. See manual pages 274 for more information. The arpbalance feature of carp(4) is currently 275 not supported anymore. 276 277 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 278 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 279 need to be recompiled. 280 28120111122: 282 The acpi_wmi(4) status device /dev/wmistat has been renamed to 283 /dev/wmistat0. 284 28520111108: 286 The option VFS_ALLOW_NONMPSAFE option has been added in order to 287 explicitely support non-MPSAFE filesystems. 288 It is on by default for all supported platform at this present 289 time. 290 29120111101: 292 The broken amd(4) driver has been replaced with esp(4) in the amd64, 293 i386 and pc98 GENERIC kernel configuration files. 294 29520110930: 296 sysinstall has been removed 297 29820110923: 299 The stable/9 branch created in subversion. This corresponds to the 300 RELENG_9 branch in CVS. 301 30220110913: 303 This commit modifies vfs_register() so that it uses a hash 304 calculation to set vfc_typenum, which is enabled by default. 305 The first time a system is booted after this change, the 306 vfc_typenum values will change for all file systems. The 307 main effect of this is a change to the NFS server file handles 308 for file systems that use vfc_typenum in their fsid, such as ZFS. 309 It will, however, prevent vfc_typenum from changing when file 310 systems are loaded in a different order for subsequent reboots. 311 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf 312 until you are ready to remount all NFS clients after a reboot. 313 31420110828: 315 Bump the shared library version numbers for libraries that 316 do not use symbol versioning, have changed the ABI compared 317 to stable/8 and which shared library version was not bumped. 318 Done as part of 9.0-RELEASE cycle. 319 32020110815: 321 During the merge of Capsicum features, the fget(9) KPI was modified. 322 This may require the rebuilding of out-of-tree device drivers -- 323 issues have been reported specifically with the nVidia device driver. 324 __FreeBSD_version is bumped to 900041. 325 326 Also, there is a period between 20110811 and 20110814 where the 327 special devices /dev/{stdin,stdout,stderr} did not work correctly. 328 Building world from a kernel during that window may not work. 329 33020110628: 331 The packet filter (pf) code has been updated to OpenBSD 4.5. 332 You need to update userland tools to be in sync with kernel. 333 This update breaks backward compatibility with earlier pfsync(4) 334 versions. Care must be taken when updating redundant firewall setups. 335 33620110608: 337 The following sysctls and tunables are retired on x86 platforms: 338 machdep.hlt_cpus 339 machdep.hlt_logical_cpus 340 The following sysctl is retired: 341 machdep.hyperthreading_allowed 342 The sysctls were supposed to provide a way to dynamically offline and 343 online selected CPUs on x86 platforms, but the implementation has not 344 been reliable especially with SCHED_ULE scheduler. 345 machdep.hyperthreading_allowed tunable is still available to ignore 346 hyperthreading CPUs at OS level. 347 Individual CPUs can be disabled using hint.lapic.X.disabled tunable, 348 where X is an APIC ID of a CPU. Be advised, though, that disabling 349 CPUs in non-uniform fashion will result in non-uniform topology and 350 may lead to sub-optimal system performance with SCHED_ULE, which is 351 a default scheduler. 352 35320110607: 354 cpumask_t type is retired and cpuset_t is used in order to describe 355 a mask of CPUs. 356 35720110531: 358 Changes to ifconfig(8) for dynamic address family detection mandate 359 that you are running a kernel of 20110525 or later. Make sure to 360 follow the update procedure to boot a new kernel before installing 361 world. 362 36320110513: 364 Support for sun4v architecture is officially dropped 365 36620110503: 367 Several KPI breaking changes have been committed to the mii(4) layer, 368 the PHY drivers and consequently some Ethernet drivers using mii(4). 369 This means that miibus.ko and the modules of the affected Ethernet 370 drivers need to be recompiled. 371 372 Note to kernel developers: Given that the OUI bit reversion problem 373 was fixed as part of these changes all mii(4) commits related to OUIs, 374 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific 375 handling, no longer can be merged verbatim to stable/8 and previous 376 branches. 377 37820110430: 379 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci' 380 into their kernel configurations along with 'device pci'. 381 38220110427: 383 The default NFS client is now the new NFS client, so fstype "newnfs" 384 is now "nfs" and the regular/old NFS client is now fstype "oldnfs". 385 Although mounts via fstype "nfs" will usually work without userland 386 changes, it is recommended that the mount(8) and mount_nfs(8) 387 commands be rebuilt from sources and that a link to mount_nfs called 388 mount_oldnfs be created. The new client is compiled into the 389 kernel with "options NFSCL" and this is needed for diskless root 390 file systems. The GENERIC kernel configs have been changed to use 391 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER. 392 To use the regular/old client, you can "mount -t oldnfs ...". For 393 a diskless root file system, you must also include a line like: 394 395 vfs.root.mountfrom="oldnfs:" 396 397 in the boot/loader.conf on the root fs on the NFS server to make 398 a diskless root fs use the old client. 399 40020110424: 401 The GENERIC kernels for all architectures now default to the new 402 CAM-based ATA stack. It means that all legacy ATA drivers were 403 removed and replaced by respective CAM drivers. If you are using 404 ATA device names in /etc/fstab or other places, make sure to update 405 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, 406 where 'Y's are the sequential numbers starting from zero for each type 407 in order of detection, unless configured otherwise with tunables, 408 see cam(4)). There will be symbolic links created in /dev/ to map 409 old adX devices to the respective adaY. They should provide basic 410 compatibility for file systems mounting in most cases, but they do 411 not support old user-level APIs and do not have respective providers 412 in GEOM. Consider using updated management tools with new device names. 413 414 It is possible to load devices ahci, ata, siis and mvs as modules, 415 but option ATA_CAM should remain in kernel configuration to make ata 416 module work as CAM driver supporting legacy ATA controllers. Device ata 417 still can be used in modular fashion (atacore + ...). Modules atadisk 418 and atapi* are not used and won't affect operation in ATA_CAM mode. 419 Note that to use CAM-based ATA kernel should include CAM devices 420 scbus, pass, da (or explicitly ada), cd and optionally others. All of 421 them are parts of the cam module. 422 423 ataraid(4) functionality is now supported by the RAID GEOM class. 424 To use it you can load geom_raid kernel module and use graid(8) tool 425 for management. Instead of /dev/arX device names, use /dev/raid/rX. 426 427 No kernel config options or code have been removed, so if a problem 428 arises, please report it and optionally revert to the old ATA stack. 429 In order to do it you can remove from the kernel config: 430 options ATA_CAM 431 device ahci 432 device mvs 433 device siis 434 , and instead add back: 435 device atadisk # ATA disk drives 436 device ataraid # ATA RAID drives 437 device atapicd # ATAPI CDROM drives 438 device atapifd # ATAPI floppy drives 439 device atapist # ATAPI tape drives 440 44120110423: 442 The default NFS server has been changed to the new server, which 443 was referred to as the experimental server. If you need to switch 444 back to the old NFS server, you must now put the "-o" option on 445 both the mountd and nfsd commands. This can be done using the 446 mountd_flags and nfs_server_flags rc.conf variables until an 447 update to the rc scripts is committed, which is coming soon. 448 44920110418: 450 The GNU Objective-C runtime library (libobjc), and other Objective-C 451 related components have been removed from the base system. If you 452 require an Objective-C library, please use one of the available ports. 453 45420110331: 455 ath(4) has been split into bus- and device- modules. if_ath contains 456 the HAL, the TX rate control and the network device code. if_ath_pci 457 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb 458 contains the AHB glue. Users need to load both if_ath_pci and if_ath 459 in order to use ath on everything else. 460 461 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only 462 need to load if_ath and if_ath_pci for ath(4) operation. 463 46420110314: 465 As part of the replacement of sysinstall, the process of building 466 release media has changed significantly. For details, please re-read 467 release(7), which has been updated to reflect the new build process. 468 46920110218: 470 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This 471 is the last available version under GPLv2. It brings a number of new 472 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE 473 4.1 and SSE 4.2), better support for powerpc64, a number of new 474 directives, and lots of other small improvements. See the ChangeLog 475 file in contrib/binutils for the full details. 476 47720110218: 478 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868 479 compliant, and will now use half of hash for authentication. 480 This will break interoperability with all stacks (including all 481 actual FreeBSD versions) who implement 482 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for 483 authentication). 484 The only workaround with such peers is to use another HMAC 485 algorithm for IPsec ("phase 2") authentication. 486 48720110207: 488 Remove the uio_yield prototype and symbol. This function has 489 been misnamed since it was introduced and should not be 490 globally exposed with this name. The equivalent functionality 491 is now available using kern_yield(curthread->td_user_pri). 492 The function remains undocumented. 493 49420110112: 495 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers, 496 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking 497 for scalar sysctls is defined but disabled. Code that needs 498 UQUAD to pass the type checking that must compile on older 499 systems where the define is not present can check against 500 __FreeBSD_version >= 900030. 501 502 The system dialog(1) has been replaced with a new version previously 503 in ports as devel/cdialog. dialog(1) is mostly command-line compatible 504 with the previous version, but the libdialog associated with it has 505 a largely incompatible API. As such, the original version of libdialog 506 will be kept temporarily as libodialog, until its base system consumers 507 are replaced or updated. Bump __FreeBSD_version to 900030. 508 50920110103: 510 If you are trying to run make universe on a -stable system, and you get 511 the following warning: 512 "Makefile", line 356: "Target architecture for i386/conf/GENERIC 513 unknown. config(8) likely too old." 514 or something similar to it, then you must upgrade your -stable system 515 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in 516 stable/8) or build the config from the latest stable/8 branch and 517 install it on your system. 518 519 Prior to this date, building a current universe on 8-stable system from 520 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing 521 error in the first kernel build phase. A new config on those old 522 systems will fix that problem for older versions of -current. 523 52420101228: 525 The TCP stack has been modified to allow Khelp modules to interact with 526 it via helper hook points and store per-connection data in the TCP 527 control block. Bump __FreeBSD_version to 900029. User space tools that 528 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to 529 be recompiled. 530 53120101114: 532 Generic IEEE 802.3 annex 31B full duplex flow control support has been 533 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along 534 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted 535 to take advantage of it instead of using custom implementations. This 536 means that these drivers now no longer unconditionally advertise 537 support for flow control but only do so if flow control is a selected 538 media option. This was implemented in the generic support that way in 539 order to allow flow control to be switched on and off via ifconfig(8) 540 with the PHY specific default to typically off in order to protect 541 from unwanted effects. Consequently, if you used flow control with 542 one of the above mentioned drivers you now need to explicitly enable 543 it, for example via: 544 ifconfig bge0 media auto mediaopt flowcontrol 545 546 Along with the above mentioned changes generic support for setting 547 1000baseT master mode also has been added and brgphy(4), ciphy(4), 548 e1000phy(4) as well as ip1000phy(4) have been converted to take 549 advantage of it. This means that these drivers now no longer take the 550 link0 parameter for selecting master mode but the master media option 551 has to be used instead, for example like in the following: 552 ifconfig bge0 media 1000baseT mediaopt full-duplex,master 553 554 Selection of master mode now is also available with all other PHY 555 drivers supporting 1000baseT. 556 55720101111: 558 The TCP stack has received a significant update to add support for 559 modularised congestion control and generally improve the clarity of 560 congestion control decisions. Bump __FreeBSD_version to 900025. User 561 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g. 562 sockstat) need to be recompiled. 563 56420101002: 565 The man(1) utility has been replaced by a new version that no longer 566 uses /etc/manpath.config. Please consult man.conf(5) for how to 567 migrate local entries to the new format. 568 56920100928: 570 The copyright strings printed by login(1) and sshd(8) at the time of a 571 new connection have been removed to follow other operating systems and 572 upstream sshd. 573 57420100915: 575 A workaround for a fixed ld bug has been removed in kernel code, 576 so make sure that your system ld is built from sources after 577 revision 210245 from 2010-07-19 (r211583 if building head kernel 578 on stable/8, r211584 for stable/7; both from 2010-08-21). 579 A symptom of incorrect ld version is different addresses for 580 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules. 581 58220100913: 583 The $ipv6_prefer variable in rc.conf(5) has been split into 584 $ip6addrctl_policy and $ipv6_activate_all_interfaces. 585 586 The $ip6addrctl_policy is a variable to choose a pre-defined 587 address selection policy set by ip6addrctl(8). A value 588 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The 589 default is "AUTO". 590 591 The $ipv6_activate_all_interfaces specifies whether IFDISABLED 592 flag (see an entry of 20090926) is set on an interface with no 593 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for 594 security reason. If you want IPv6 link-local address on all 595 interfaces by default, set this to "YES". 596 597 The old ipv6_prefer="YES" is equivalent to 598 ipv6_activate_all_interfaces="YES" and 599 ip6addrctl_policy="ipv6_prefer". 600 60120100913: 602 DTrace has grown support for userland tracing. Due to this, DTrace is 603 now i386 and amd64 only. 604 dtruss(1) is now installed by default on those systems and a new 605 kernel module is needed for userland tracing: fasttrap. 606 No changes to your kernel config file are necessary to enable 607 userland tracing, but you might consider adding 'STRIP=' and 608 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want 609 to have informative userland stack traces in DTrace (ustack). 610 61120100725: 612 The acpi_aiboost(4) driver has been removed in favor of the new 613 aibs(4) driver. You should update your kernel configuration file. 614 61520100722: 616 BSD grep has been imported to the base system and it is built by 617 default. It is completely BSD licensed, highly GNU-compatible, uses 618 less memory than its GNU counterpart and has a small codebase. 619 However, it is slower than its GNU counterpart, which is mostly 620 noticeable for larger searches, for smaller ones it is measurable 621 but not significant. The reason is complex, the most important factor 622 is that we lack a modern and efficient regex library and GNU 623 overcomes this by optimizing the searches internally. Future work 624 on improving the regex performance is planned, for the meantime, 625 users that need better performance, can build GNU grep instead by 626 setting the WITH_GNU_GREP knob. 627 62820100713: 629 Due to the import of powerpc64 support, all existing powerpc kernel 630 configuration files must be updated with a machine directive like this: 631 machine powerpc powerpc 632 633 In addition, an updated config(8) is required to build powerpc kernels 634 after this change. 635 63620100713: 637 A new version of ZFS (version 15) has been merged to -HEAD. 638 This version uses a python library for the following subcommands: 639 zfs allow, zfs unallow, zfs groupspace, zfs userspace. 640 For full functionality of these commands the following port must 641 be installed: sysutils/py-zfs 642 64320100429: 644 'vm_page's are now hashed by physical address to an array of mutexes. 645 Currently this is only used to serialize access to hold_count. Over 646 time the page queue mutex will be peeled away. This changes the size 647 of pmap on every architecture. And requires all callers of vm_page_hold 648 and vm_page_unhold to be updated. 649 65020100402: 651 WITH_CTF can now be specified in src.conf (not recommended, there 652 are some problems with static executables), make.conf (would also 653 affect ports which do not use GNU make and do not override the 654 compile targets) or in the kernel config (via "makeoptions 655 WITH_CTF=yes"). 656 When WITH_CTF was specified there before this was silently ignored, 657 so make sure that WITH_CTF is not used in places which could lead 658 to unwanted behavior. 659 66020100311: 661 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32 662 to allow 32-bit compatibility on non-x86 platforms. All kernel 663 configurations on amd64 and ia64 platforms using these options must 664 be modified accordingly. 665 66620100113: 667 The utmp user accounting database has been replaced with utmpx, 668 the user accounting interface standardized by POSIX. 669 Unfortunately the semantics of utmp and utmpx don't match, 670 making it practically impossible to support both interfaces. 671 The user accounting database is used by tools like finger(1), 672 last(1), talk(1), w(1) and ac(8). 673 674 All applications in the base system use utmpx. This means only 675 local binaries (e.g. from the ports tree) may still use these 676 utmp database files. These applications must be rebuilt to make 677 use of utmpx. 678 679 After the system has been upgraded, it is safe to remove the old 680 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*), 681 assuming their contents is of no importance anymore. Old wtmp 682 databases can only be used by last(1) and ac(8) after they have 683 been converted to the new format using wtmpcvt(1). 684 68520100108: 686 Introduce the kernel thread "deadlock resolver" (which can be enabled 687 via the DEADLKRES option, see NOTES for more details) and the 688 sleepq_type() function for sleepqueues. 689 69020091202: 691 The rc.firewall and rc.firewall6 were unified, and 692 rc.firewall6 and rc.d/ip6fw were removed. 693 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc 694 variables are obsoleted. Instead, the following new rc 695 variables are added to rc.d/ipfw: 696 697 firewall_client_net_ipv6, firewall_simple_iif_ipv6, 698 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6, 699 firewall_simple_onet_ipv6, firewall_trusted_ipv6 700 701 The meanings correspond to the relevant IPv4 variables. 702 70320091125: 704 8.0-RELEASE. 705 70620091113: 707 The default terminal emulation for syscons(4) has been changed 708 from cons25 to xterm on all platforms except pc98. This means 709 that the /etc/ttys file needs to be updated to ensure correct 710 operation of applications on the console. 711 712 The terminal emulation style can be toggled per window by using 713 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration 714 options can be used to change the compile-time default back to 715 cons25. 716 717 To prevent graphical artifacts, make sure the TERM environment 718 variable is set to match the terminal emulation that is being 719 performed by syscons(4). 720 72120091109: 722 The layout of the structure ieee80211req_scan_result has changed. 723 Applications that require wireless scan results (e.g. ifconfig(8)) 724 from net80211 need to be recompiled. 725 726 Applications such as wpa_supplicant(8) may require a full world 727 build without using NO_CLEAN in order to get synchronized with the 728 new structure. 729 73020091025: 731 The iwn(4) driver has been updated to support the 5000 and 5150 series. 732 There's one kernel module for each firmware. Adding "device iwnfw" 733 to the kernel configuration file means including all three firmware 734 images inside the kernel. If you want to include just the one for 735 your wireless card, use the devices iwn4965fw, iwn5000fw or 736 iwn5150fw. 737 73820090926: 739 The rc.d/network_ipv6, IPv6 configuration script has been integrated 740 into rc.d/netif. The changes are the following: 741 742 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF 743 for IPv4. For aliases, $ifconfig_IF_aliasN should be used. 744 Note that both variables need the "inet6" keyword at the head. 745 746 Do not set $ipv6_network_interfaces manually if you do not 747 understand what you are doing. It is not needed in most cases. 748 749 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but 750 they are obsolete. 751 752 2. $ipv6_enable is obsolete. Use $ipv6_prefer and 753 "inet6 accept_rtadv" keyword in ifconfig(8) instead. 754 755 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and 756 all configured interfaces have "inet6 accept_rtadv" in the 757 $ifconfig_IF_ipv6. These are for backward compatibility. 758 759 3. A new variable $ipv6_prefer has been added. If NO, IPv6 760 functionality of interfaces with no corresponding 761 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag, 762 and the default address selection policy of ip6addrctl(8) 763 is the IPv4-preferred one (see rc.d/ip6addrctl for more details). 764 Note that if you want to configure IPv6 functionality on the 765 disabled interfaces after boot, first you need to clear the flag by 766 using ifconfig(8) like: 767 768 ifconfig em0 inet6 -ifdisabled 769 770 If YES, the default address selection policy is set as 771 IPv6-preferred. 772 773 The default value of $ipv6_prefer is NO. 774 775 4. If your system need to receive Router Advertisement messages, 776 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8) 777 scripts automatically invoke rtsol(8) when the interface becomes 778 UP. The Router Advertisement messages are used for SLAAC 779 (State-Less Address AutoConfiguration). 780 78120090922: 782 802.11s D3.03 support was committed. This is incompatible with the 783 previous code, which was based on D3.0. 784 78520090912: 786 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value 787 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to 788 control whether accepting Router Advertisement messages or not. 789 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and 790 a sysctl variable net.inet6.ip6.auto_linklocal is its default value. 791 The ifconfig(8) utility now supports these flags. 792 79320090910: 794 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for 795 mount(8) and -a option for df(1) to see them. 796 79720090825: 798 The old tunable hw.bus.devctl_disable has been superseded by 799 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be 800 replaced by hw.bus.devctl_queue=0. The default for this new tunable 801 is 1000. 802 80320090813: 804 Remove the option STOP_NMI. The default action is now to use NMI only 805 for KDB via the newly introduced function stop_cpus_hard() and 806 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64. 807 80820090803: 809 The stable/8 branch created in subversion. This corresponds to the 810 RELENG_8 branch in CVS. 811 81220090719: 813 Bump the shared library version numbers for all libraries that do not 814 use symbol versioning as part of the 8.0-RELEASE cycle. Bump 815 __FreeBSD_version to 800105. 816 81720090714: 818 Due to changes in the implementation of virtual network stack support, 819 all network-related kernel modules must be recompiled. As this change 820 breaks the ABI, bump __FreeBSD_version to 800104. 821 82220090713: 823 The TOE interface to the TCP syncache has been modified to remove 824 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. 825 The cxgb driver is the only TOE consumer affected by this change, and 826 needs to be recompiled along with the kernel. As this change breaks 827 the ABI, bump __FreeBSD_version to 800103. 828 82920090712: 830 Padding has been added to struct tcpcb, sackhint and tcpstat in 831 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst 832 maintaining the ABI. However, this change breaks the ABI, so bump 833 __FreeBSD_version to 800102. User space tools that rely on the size of 834 any of these structs (e.g. sockstat) need to be recompiled. 835 83620090630: 837 The NFS_LEGACYRPC option has been removed along with the old kernel 838 RPC implementation that this option selected. Kernel configurations 839 may need to be adjusted. 840 84120090629: 842 The network interface device nodes at /dev/net/<interface> have been 843 removed. All ioctl operations can be performed the normal way using 844 routing sockets. The kqueue functionality can generally be replaced 845 with routing sockets. 846 84720090628: 848 The documentation from the FreeBSD Documentation Project (Handbook, 849 FAQ, etc.) is now installed via packages by sysinstall(8) and under 850 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc. 851 85220090624: 853 The ABI of various structures related to the SYSV IPC API have been 854 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel 855 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to 856 800100. 857 85820090622: 859 Layout of struct vnet has changed as routing related variables were 860 moved to their own Vimage module. Modules need to be recompiled. Bump 861 __FreeBSD_version to 800099. 862 86320090619: 864 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024 865 respectively. As long as no more than 16 groups per process are used, 866 no changes should be visible. When more than 16 groups are used, old 867 binaries may fail if they call getgroups() or getgrouplist() with 868 statically sized storage. Recompiling will work around this, but 869 applications should be modified to use dynamically allocated storage 870 for group arrays as POSIX.1-2008 does not cap an implementation's 871 number of supported groups at NGROUPS_MAX+1 as previous versions did. 872 873 NFS and portalfs mounts may also be affected as the list of groups is 874 truncated to 16. Users of NFS who use more than 16 groups, should 875 take care that negative group permissions are not used on the exported 876 file systems as they will not be reliable unless a GSSAPI based 877 authentication method is used. 878 87920090616: 880 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This 881 option compiles in the support for adaptive spinning for lockmgrs 882 which want to enable it. The lockinit() function now accepts the flag 883 LK_ADAPTIVE in order to make the lock object subject to adaptive 884 spinning when both held in write and read mode. 885 88620090613: 887 The layout of the structure returned by IEEE80211_IOC_STA_INFO has 888 changed. User applications that use this ioctl need to be rebuilt. 889 89020090611: 891 The layout of struct thread has changed. Kernel and modules need to 892 be rebuilt. 893 89420090608: 895 The layout of structs ifnet, domain, protosw and vnet_net has changed. 896 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097. 897 89820090602: 899 window(1) has been removed from the base system. It can now be 900 installed from ports. The port is called misc/window. 901 90220090601: 903 The way we are storing and accessing `routing table' entries has 904 changed. Programs reading the FIB, like netstat, need to be 905 re-compiled. 906 90720090601: 908 A new netisr implementation has been added for FreeBSD 8. Network 909 file system modules, such as igmp, ipdivert, and others, should be 910 rebuilt. 911 Bump __FreeBSD_version to 800096. 912 91320090530: 914 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no 915 more valid. 916 91720090530: 918 Add VOP_ACCESSX(9). File system modules need to be rebuilt. 919 Bump __FreeBSD_version to 800094. 920 92120090529: 922 Add mnt_xflag field to 'struct mount'. File system modules need to be 923 rebuilt. 924 Bump __FreeBSD_version to 800093. 925 92620090528: 927 The compiling option ADAPTIVE_SX has been retired while it has been 928 introduced the option NO_ADAPTIVE_SX which handles the reversed logic. 929 The KPI for sx_init_flags() changes as accepting flags: 930 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has 931 been introduced in order to handle the reversed logic. 932 Bump __FreeBSD_version to 800092. 933 93420090527: 935 Add support for hierarchical jails. Remove global securelevel. 936 Bump __FreeBSD_version to 800091. 937 93820090523: 939 The layout of struct vnet_net has changed, therefore modules 940 need to be rebuilt. 941 Bump __FreeBSD_version to 800090. 942 94320090523: 944 The newly imported zic(8) produces a new format in the output. Please 945 run tzsetup(8) to install the newly created data to /etc/localtime. 946 94720090520: 948 The sysctl tree for the usb stack has renamed from hw.usb2.* to 949 hw.usb.* and is now consistent again with previous releases. 950 95120090520: 952 802.11 monitor mode support was revised and driver api's were changed. 953 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead 954 of DLT_IEEE802_11. No user-visible data structures were changed but 955 applications that use DLT_IEEE802_11 may require changes. 956 Bump __FreeBSD_version to 800088. 957 95820090430: 959 The layout of the following structs has changed: sysctl_oid, 960 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet, 961 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or 962 panics may be experienced. World rebuild is required for 963 correctly checking networking state from userland. 964 Bump __FreeBSD_version to 800085. 965 96620090429: 967 MLDv2 and Source-Specific Multicast (SSM) have been merged 968 to the IPv6 stack. VIMAGE hooks are in but not yet used. 969 The implementation of SSM within FreeBSD's IPv6 stack closely 970 follows the IPv4 implementation. 971 972 For kernel developers: 973 974 * The most important changes are that the ip6_output() and 975 ip6_input() paths no longer take the IN6_MULTI_LOCK, 976 and this lock has been downgraded to a non-recursive mutex. 977 978 * As with the changes to the IPv4 stack to support SSM, filtering 979 of inbound multicast traffic must now be performed by transport 980 protocols within the IPv6 stack. This does not apply to TCP and 981 SCTP, however, it does apply to UDP in IPv6 and raw IPv6. 982 983 * The KPIs used by IPv6 multicast are similar to those used by 984 the IPv4 stack, with the following differences: 985 * im6o_mc_filter() is analogous to imo_multicast_filter(). 986 * The legacy KAME entry points in6_joingroup and in6_leavegroup() 987 are shimmed to in6_mc_join() and in6_mc_leave() respectively. 988 * IN6_LOOKUP_MULTI() has been deprecated and removed. 989 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs 990 for MLDv1 have an additional 'timer' argument which is used to 991 jitter the initial membership report for the solicited-node 992 multicast membership on-link. 993 * This is not strictly needed for MLDv2, which already jitters 994 its report transmissions. However, the 'timer' argument is 995 preserved in case MLDv1 is active on the interface. 996 997 * The KAME linked-list based IPv6 membership implementation has 998 been refactored to use a vector similar to that used by the IPv4 999 stack. 1000 Code which maintains a list of its own multicast memberships 1001 internally, e.g. carp, has been updated to reflect the new 1002 semantics. 1003 1004 * There is a known Lock Order Reversal (LOR) due to in6_setscope() 1005 acquiring the IF_AFDATA_LOCK and being called within ip6_output(). 1006 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an 1007 implementation constraint which needs to be addressed in HEAD. 1008 1009 For application developers: 1010 1011 * The changes are broadly similar to those made for the IPv4 1012 stack. 1013 1014 * The use of IPv4 and IPv6 multicast socket options on the same 1015 socket, using mapped addresses, HAS NOT been tested or supported. 1016 1017 * There are a number of issues with the implementation of various 1018 IPv6 multicast APIs which need to be resolved in the API surface 1019 before the implementation is fully compatible with KAME userland 1020 use, and these are mostly to do with interface index treatment. 1021 1022 * The literature available discusses the use of either the delta / ASM 1023 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API 1024 using setsourcefilter(3)/getsourcefilter(3). For more information 1025 please refer to RFC 3768, 'Socket Interface Extensions for 1026 Multicast Source Filters'. 1027 1028 * Applications which use the published RFC 3678 APIs should be fine. 1029 1030 For systems administrators: 1031 1032 * The mtest(8) utility has been refactored to support IPv6, in 1033 addition to IPv4. Interface addresses are no longer accepted 1034 as arguments, their names must be used instead. The utility 1035 will map the interface name to its first IPv4 address as 1036 returned by getifaddrs(3). 1037 1038 * The ifmcstat(8) utility has also been updated to print the MLDv2 1039 endpoint state and source filter lists via sysctl(3). 1040 1041 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable 1042 loopback of IPv6 multicast datagrams by default; it defaults to 1 1043 to preserve the existing behaviour. Disabling multicast loopback is 1044 recommended for optimal system performance. 1045 1046 * The IPv6 MROUTING code has been changed to examine this sysctl 1047 instead of attempting to perform a group lookup before looping 1048 back forwarded datagrams. 1049 1050 Bump __FreeBSD_version to 800084. 1051 105220090422: 1053 Implement low-level Bluetooth HCI API. 1054 Bump __FreeBSD_version to 800083. 1055 105620090419: 1057 The layout of struct malloc_type, used by modules to register new 1058 memory allocation types, has changed. Most modules will need to 1059 be rebuilt or panics may be experienced. 1060 Bump __FreeBSD_version to 800081. 1061 106220090415: 1063 Anticipate overflowing inp_flags - add inp_flags2. 1064 This changes most offsets in inpcb, so checking v4 connection 1065 state will require a world rebuild. 1066 Bump __FreeBSD_version to 800080. 1067 106820090415: 1069 Add an llentry to struct route and struct route_in6. Modules 1070 embedding a struct route will need to be recompiled. 1071 Bump __FreeBSD_version to 800079. 1072 107320090414: 1074 The size of rt_metrics_lite and by extension rtentry has changed. 1075 Networking administration apps will need to be recompiled. 1076 The route command now supports show as an alias for get, weighting 1077 of routes, sticky and nostick flags to alter the behavior of stateful 1078 load balancing. 1079 Bump __FreeBSD_version to 800078. 1080 108120090408: 1082 Do not use Giant for kbdmux(4) locking. This is wrong and 1083 apparently causing more problems than it solves. This will 1084 re-open the issue where interrupt handlers may race with 1085 kbdmux(4) in polling mode. Typical symptoms include (but 1086 not limited to) duplicated and/or missing characters when 1087 low level console functions (such as gets) are used while 1088 interrupts are enabled (for example geli password prompt, 1089 mountroot prompt etc.). Disabling kbdmux(4) may help. 1090 109120090407: 1092 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed; 1093 kernel modules referencing any of the above need to be recompiled. 1094 Bump __FreeBSD_version to 800075. 1095 109620090320: 1097 GEOM_PART has become the default partition slicer for storage devices, 1098 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It 1099 introduces some changes: 1100 1101 MSDOS/EBR: the devices created from MSDOS extended partition entries 1102 (EBR) can be named differently than with GEOM_MBR and are now symlinks 1103 to devices with offset-based names. fstabs may need to be modified. 1104 1105 BSD: the "geometry does not match label" warning is harmless in most 1106 cases but it points to problems in file system misalignment with 1107 disk geometry. The "c" partition is now implicit, covers the whole 1108 top-level drive and cannot be (mis)used by users. 1109 1110 General: Kernel dumps are now not allowed to be written to devices 1111 whose partition types indicate they are meant to be used for file 1112 systems (or, in case of MSDOS partitions, as something else than 1113 the "386BSD" type). 1114 1115 Most of these changes date approximately from 200812. 1116 111720090319: 1118 The uscanner(4) driver has been removed from the kernel. This follows 1119 Linux removing theirs in 2.6 and making libusb the default interface 1120 (supported by sane). 1121 112220090319: 1123 The multicast forwarding code has been cleaned up. netstat(1) 1124 only relies on KVM now for printing bandwidth upcall meters. 1125 The IPv4 and IPv6 modules are split into ip_mroute_mod and 1126 ip6_mroute_mod respectively. The config(5) options for statically 1127 compiling this code remain the same, i.e. 'options MROUTING'. 1128 112920090315: 1130 Support for the IFF_NEEDSGIANT network interface flag has been 1131 removed, which means that non-MPSAFE network device drivers are no 1132 longer supported. In particular, if_ar, if_sr, and network device 1133 drivers from the old (legacy) USB stack can no longer be built or 1134 used. 1135 113620090313: 1137 POSIX.1 Native Language Support (NLS) has been enabled in libc and 1138 a bunch of new language catalog files have also been added. 1139 This means that some common libc messages are now localized and 1140 they depend on the LC_MESSAGES environmental variable. 1141 114220090313: 1143 The k8temp(4) driver has been renamed to amdtemp(4) since 1144 support for Family 10 and Family 11 CPU families was added. 1145 114620090309: 1147 IGMPv3 and Source-Specific Multicast (SSM) have been merged 1148 to the IPv4 stack. VIMAGE hooks are in but not yet used. 1149 1150 For kernel developers, the most important changes are that the 1151 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(), 1152 and this lock has been downgraded to a non-recursive mutex. 1153 1154 Transport protocols (UDP, Raw IP) are now responsible for filtering 1155 inbound multicast traffic according to group membership and source 1156 filters. The imo_multicast_filter() KPI exists for this purpose. 1157 Transports which do not use multicast (SCTP, TCP) already reject 1158 multicast by default. Forwarding and receive performance may improve 1159 as a mutex acquisition is no longer needed in the ip_input() 1160 low-level input path. in_addmulti() and in_delmulti() are shimmed 1161 to new KPIs which exist to support SSM in-kernel. 1162 1163 For application developers, it is recommended that loopback of 1164 multicast datagrams be disabled for best performance, as this 1165 will still cause the lock to be taken for each looped-back 1166 datagram transmission. The net.inet.ip.mcast.loop sysctl may 1167 be tuned to 0 to disable loopback by default; it defaults to 1 1168 to preserve the existing behaviour. 1169 1170 For systems administrators, to obtain best performance with 1171 multicast reception and multiple groups, it is always recommended 1172 that a card with a suitably precise hash filter is used. Hash 1173 collisions will still result in the lock being taken within the 1174 transport protocol input path to check group membership. 1175 1176 If deploying FreeBSD in an environment with IGMP snooping switches, 1177 it is recommended that the net.inet.igmp.sendlocal sysctl remain 1178 enabled; this forces 224.0.0.0/24 group membership to be announced 1179 via IGMP. 1180 1181 The size of 'struct igmpstat' has changed; netstat needs to be 1182 recompiled to reflect this. 1183 Bump __FreeBSD_version to 800070. 1184 118520090309: 1186 libusb20.so.1 is now installed as libusb.so.1 and the ports system 1187 updated to use it. This requires a buildworld/installworld in order to 1188 update the library and dependencies (usbconfig, etc). Its advisable to 1189 rebuild all ports which uses libusb. More specific directions are given 1190 in the ports collection UPDATING file. Any /etc/libmap.conf entries for 1191 libusb are no longer required and can be removed. 1192 119320090302: 1194 A workaround is committed to allow the creation of System V shared 1195 memory segment of size > 2 GB on the 64-bit architectures. 1196 Due to a limitation of the existing ABI, the shm_segsz member 1197 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is 1198 wrong for large segments. Note that limits must be explicitly 1199 raised to allow such segments to be created. 1200 120120090301: 1202 The layout of struct ifnet has changed, requiring a rebuild of all 1203 network device driver modules. 1204 120520090227: 1206 The /dev handling for the new USB stack has changed, a 1207 buildworld/installworld is required for libusb20. 1208 120920090223: 1210 The new USB2 stack has now been permanently moved in and all kernel and 1211 module names reverted to their previous values (eg, usb, ehci, ohci, 1212 ums, ...). The old usb stack can be compiled in by prefixing the name 1213 with the letter 'o', the old usb modules have been removed. 1214 Updating entry 20090216 for xorg and 20090215 for libmap may still 1215 apply. 1216 121720090217: 1218 The rc.conf(5) option if_up_delay has been renamed to 1219 defaultroute_delay to better reflect its purpose. If you have 1220 customized this setting in /etc/rc.conf you need to update it to 1221 use the new name. 1222 122320090216: 1224 xorg 7.4 wants to configure its input devices via hald which does not 1225 yet work with USB2. If the keyboard/mouse does not work in xorg then 1226 add 1227 Option "AllowEmptyInput" "off" 1228 to your ServerLayout section. This will cause X to use the configured 1229 kbd and mouse sections from your xorg.conf. 1230 123120090215: 1232 The GENERIC kernels for all architectures now default to the new USB2 1233 stack. No kernel config options or code have been removed so if a 1234 problem arises please report it and optionally revert to the old USB 1235 stack. If you are loading USB kernel modules or have a custom kernel 1236 that includes GENERIC then ensure that usb names are also changed over, 1237 eg uftdi -> usb2_serial_ftdi. 1238 1239 Older programs linked against the ports libusb 0.1 need to be 1240 redirected to the new stack's libusb20. /etc/libmap.conf can 1241 be used for this: 1242 # Map old usb library to new one for usb2 stack 1243 libusb-0.1.so.8 libusb20.so.1 1244 124520090209: 1246 All USB ethernet devices now attach as interfaces under the name ueN 1247 (eg. ue0). This is to provide a predictable name as vendors often 1248 change usb chipsets in a product without notice. 1249 125020090203: 1251 The ichsmb(4) driver has been changed to require SMBus slave 1252 addresses be left-justified (xxxxxxx0b) rather than right-justified. 1253 All of the other SMBus controller drivers require left-justified 1254 slave addresses, so this change makes all the drivers provide the 1255 same interface. 1256 125720090201: 1258 INET6 statistics (struct ip6stat) was updated. 1259 netstat(1) needs to be recompiled. 1260 126120090119: 1262 NTFS has been removed from GENERIC kernel on amd64 to match 1263 GENERIC on i386. Should not cause any issues since mount_ntfs(8) 1264 will load ntfs.ko module automatically when NTFS support is 1265 actually needed, unless ntfs.ko is not installed or security 1266 level prohibits loading kernel modules. If either is the case, 1267 "options NTFS" has to be added into kernel config. 1268 126920090115: 1270 TCP Appropriate Byte Counting (RFC 3465) support added to kernel. 1271 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to 1272 800061. User space tools that rely on the size of struct tcpcb in 1273 tcp_var.h (e.g. sockstat) need to be recompiled. 1274 127520081225: 1276 ng_tty(4) module updated to match the new TTY subsystem. 1277 Due to API change, user-level applications must be updated. 1278 New API support added to mpd5 CVS and expected to be present 1279 in next mpd5.3 release. 1280 128120081219: 1282 With __FreeBSD_version 800060 the makefs tool is part of 1283 the base system (it was a port). 1284 128520081216: 1286 The afdata and ifnet locks have been changed from mutexes to 1287 rwlocks, network modules will need to be re-compiled. 1288 128920081214: 1290 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite. 1291 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated. 1292 The new code reduced struct rtentry{} by 16 bytes on 32-bit 1293 architecture and 40 bytes on 64-bit architecture. The userland 1294 applications "arp" and "ndp" have been updated accordingly. 1295 The output from "netstat -r" shows only routing entries and 1296 none of the L2 information. 1297 129820081130: 1299 __FreeBSD_version 800057 marks the switchover from the 1300 binary ath hal to source code. Users must add the line: 1301 1302 options AH_SUPPORT_AR5416 1303 1304 to their kernel config files when specifying: 1305 1306 device ath_hal 1307 1308 The ath_hal module no longer exists; the code is now compiled 1309 together with the driver in the ath module. It is now 1310 possible to tailor chip support (i.e. reduce the set of chips 1311 and thereby the code size); consult ath_hal(4) for details. 1312 131320081121: 1314 __FreeBSD_version 800054 adds memory barriers to 1315 <machine/atomic.h>, new interfaces to ifnet to facilitate 1316 multiple hardware transmit queues for cards that support 1317 them, and a lock-less ring-buffer implementation to 1318 enable drivers to more efficiently manage queueing of 1319 packets. 1320 132120081117: 1322 A new version of ZFS (version 13) has been merged to -HEAD. 1323 This version has zpool attribute "listsnapshots" off by 1324 default, which means "zfs list" does not show snapshots, 1325 and is the same as Solaris behavior. 1326 132720081028: 1328 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled. 1329 133020081009: 1331 The uhci, ohci, ehci and slhci USB Host controller drivers have 1332 been put into separate modules. If you load the usb module 1333 separately through loader.conf you will need to load the 1334 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0 1335 controller add the following to loader.conf: 1336 1337 uhci_load="YES" 1338 ehci_load="YES" 1339 134020081009: 1341 The ABI used by the PMC toolset has changed. Please keep 1342 userland (libpmc(3)) and the kernel module (hwpmc(4)) in 1343 sync. 1344 134520081009: 1346 atapci kernel module now includes only generic PCI ATA 1347 driver. AHCI driver moved to ataahci kernel module. 1348 All vendor-specific code moved into separate kernel modules: 1349 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek, 1350 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron, 1351 atamarvell, atamicron, atanational, atanetcell, atanvidia, 1352 atapromise, ataserverworks, atasiliconimage, atasis, atavia 1353 135420080820: 1355 The TTY subsystem of the kernel has been replaced by a new 1356 implementation, which provides better scalability and an 1357 improved driver model. Most common drivers have been migrated to 1358 the new TTY subsystem, while others have not. The following 1359 drivers have not yet been ported to the new TTY layer: 1360 1361 PCI/ISA: 1362 cy, digi, rc, rp, sio 1363 1364 USB: 1365 ubser, ucycom 1366 1367 Line disciplines: 1368 ng_h4, ng_tty, ppp, sl, snp 1369 1370 Adding these drivers to your kernel configuration file shall 1371 cause compilation to fail. 1372 137320080818: 1374 ntpd has been upgraded to 4.2.4p5. 1375 137620080801: 1377 OpenSSH has been upgraded to 5.1p1. 1378 1379 For many years, FreeBSD's version of OpenSSH preferred DSA 1380 over RSA for host and user authentication keys. With this 1381 upgrade, we've switched to the vendor's default of RSA over 1382 DSA. This may cause upgraded clients to warn about unknown 1383 host keys even for previously known hosts. Users should 1384 follow the usual procedure for verifying host keys before 1385 accepting the RSA key. 1386 1387 This can be circumvented by setting the "HostKeyAlgorithms" 1388 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh 1389 command line. 1390 1391 Please note that the sequence of keys offered for 1392 authentication has been changed as well. You may want to 1393 specify IdentityFile in a different order to revert this 1394 behavior. 1395 139620080713: 1397 The sio(4) driver has been removed from the i386 and amd64 1398 kernel configuration files. This means uart(4) is now the 1399 default serial port driver on those platforms as well. 1400 1401 To prevent collisions with the sio(4) driver, the uart(4) driver 1402 uses different names for its device nodes. This means the 1403 onboard serial port will now most likely be called "ttyu0" 1404 instead of "ttyd0". You may need to reconfigure applications to 1405 use the new device names. 1406 1407 When using the serial port as a boot console, be sure to update 1408 /boot/device.hints and /etc/ttys before booting the new kernel. 1409 If you forget to do so, you can still manually specify the hints 1410 at the loader prompt: 1411 1412 set hint.uart.0.at="isa" 1413 set hint.uart.0.port="0x3F8" 1414 set hint.uart.0.flags="0x10" 1415 set hint.uart.0.irq="4" 1416 boot -s 1417 141820080609: 1419 The gpt(8) utility has been removed. Use gpart(8) to partition 1420 disks instead. 1421 142220080603: 1423 The version that Linuxulator emulates was changed from 2.4.2 1424 to 2.6.16. If you experience any problems with Linux binaries 1425 please try to set sysctl compat.linux.osrelease to 2.4.2 and 1426 if it fixes the problem contact emulation mailing list. 1427 142820080525: 1429 ISDN4BSD (I4B) was removed from the src tree. You may need to 1430 update a your kernel configuration and remove relevant entries. 1431 143220080509: 1433 I have checked in code to support multiple routing tables. 1434 See the man pages setfib(1) and setfib(2). 1435 This is a hopefully backwards compatible version, 1436 but to make use of it you need to compile your kernel 1437 with options ROUTETABLES=2 (or more up to 16). 1438 143920080420: 1440 The 802.11 wireless support was redone to enable multi-bss 1441 operation on devices that are capable. The underlying device 1442 is no longer used directly but instead wlanX devices are 1443 cloned with ifconfig. This requires changes to rc.conf files. 1444 For example, change: 1445 ifconfig_ath0="WPA DHCP" 1446 to 1447 wlans_ath0=wlan0 1448 ifconfig_wlan0="WPA DHCP" 1449 see rc.conf(5) for more details. In addition, mergemaster of 1450 /etc/rc.d is highly recommended. Simultaneous update of userland 1451 and kernel wouldn't hurt either. 1452 1453 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta 1454 modules were merged into the base wlan module. All references 1455 to these modules (e.g. in kernel config files) must be removed. 1456 145720080408: 1458 psm(4) has gained write(2) support in native operation level. 1459 Arbitrary commands can be written to /dev/psm%d and status can 1460 be read back from it. Therefore, an application is responsible 1461 for status validation and error recovery. It is a no-op in 1462 other operation levels. 1463 146420080312: 1465 Support for KSE threading has been removed from the kernel. To 1466 run legacy applications linked against KSE libmap.conf may 1467 be used. The following libmap.conf may be used to ensure 1468 compatibility with any prior release: 1469 1470 libpthread.so.1 libthr.so.1 1471 libpthread.so.2 libthr.so.2 1472 libkse.so.3 libthr.so.3 1473 147420080301: 1475 The layout of struct vmspace has changed. This affects libkvm 1476 and any executables that link against libkvm and use the 1477 kvm_getprocs() function. In particular, but not exclusively, 1478 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1). 1479 The effects are minimal, but it's advisable to upgrade world 1480 nonetheless. 1481 148220080229: 1483 The latest em driver no longer has support in it for the 1484 82575 adapter, this is now moved to the igb driver. The 1485 split was done to make new features that are incompatible 1486 with older hardware easier to do. 1487 148820080220: 1489 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4), 1490 likewise the kernel option is now GEOM_LINUX_LVM. 1491 149220080211: 1493 The default NFS mount mode has changed from UDP to TCP for 1494 increased reliability. If you rely on (insecurely) NFS 1495 mounting across a firewall you may need to update your 1496 firewall rules. 1497 149820080208: 1499 Belatedly note the addition of m_collapse for compacting 1500 mbuf chains. 1501 150220080126: 1503 The fts(3) structures have been changed to use adequate 1504 integer types for their members and so to be able to cope 1505 with huge file trees. The old fts(3) ABI is preserved 1506 through symbol versioning in libc, so third-party binaries 1507 using fts(3) should still work, although they will not take 1508 advantage of the extended types. At the same time, some 1509 third-party software might fail to build after this change 1510 due to unportable assumptions made in its source code about 1511 fts(3) structure members. Such software should be fixed 1512 by its vendor or, in the worst case, in the ports tree. 1513 FreeBSD_version 800015 marks this change for the unlikely 1514 case that a portable fix is impossible. 1515 151620080123: 1517 To upgrade to -current after this date, you must be running 1518 FreeBSD not older than 6.0-RELEASE. Upgrading to -current 1519 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems. 1520 152120071128: 1522 The ADAPTIVE_GIANT kernel option has been retired because its 1523 functionality is the default now. 1524 152520071118: 1526 The AT keyboard emulation of sunkbd(4) has been turned on 1527 by default. In order to make the special symbols of the Sun 1528 keyboards driven by sunkbd(4) work under X these now have 1529 to be configured the same way as Sun USB keyboards driven 1530 by ukbd(4) (which also does AT keyboard emulation), f.e.: 1531 1532 Option "XkbLayout" "us" 1533 Option "XkbRules" "xorg" 1534 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us" 1535 153620071024: 1537 It has been decided that it is desirable to provide ABI 1538 backwards compatibility to the FreeBSD 4/5/6 versions of the 1539 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was 1540 broken with the introduction of PCI domain support (see the 1541 20070930 entry). Unfortunately, this required the ABI of 1542 PCIOCGETCONF to be broken again in order to be able to 1543 provide backwards compatibility to the old version of that 1544 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled 1545 again. As for prominent ports this affects neither pciutils 1546 nor xorg-server this time, the hal port needs to be rebuilt 1547 however. 1548 154920071020: 1550 The misnamed kthread_create() and friends have been renamed 1551 to kproc_create() etc. Many of the callers already 1552 used kproc_start().. 1553 I will return kthread_create() and friends in a while 1554 with implementations that actually create threads, not procs. 1555 Renaming corresponds with version 800002. 1556 155720071010: 1558 RELENG_7 branched. 1559 1560COMMON ITEMS: 1561 1562 General Notes 1563 ------------- 1564 Avoid using make -j when upgrading. While generally safe, there are 1565 sometimes problems using -j to upgrade. If your upgrade fails with 1566 -j, please try again without -j. From time to time in the past there 1567 have been problems using -j with buildworld and/or installworld. This 1568 is especially true when upgrading between "distant" versions (eg one 1569 that cross a major release boundary or several minor releases, or when 1570 several months have passed on the -current branch). 1571 1572 Sometimes, obscure build problems are the result of environment 1573 poisoning. This can happen because the make utility reads its 1574 environment when searching for values for global variables. To run 1575 your build attempts in an "environmental clean room", prefix all make 1576 commands with 'env -i '. See the env(1) manual page for more details. 1577 1578 When upgrading from one major version to another it is generally best 1579 to upgrade to the latest code in the currently installed branch first, 1580 then do an upgrade to the new branch. This is the best-tested upgrade 1581 path, and has the highest probability of being successful. Please try 1582 this approach before reporting problems with a major version upgrade. 1583 1584 ZFS notes 1585 --------- 1586 When upgrading the boot ZFS pool to a new version, always follow 1587 these two steps: 1588 1589 1.) recompile and reinstall the ZFS boot loader and boot block 1590 (this is part of "make buildworld" and "make installworld") 1591 1592 2.) update the ZFS boot block on your boot drive 1593 1594 The following example updates the ZFS boot block on the first 1595 partition (freebsd-boot) of a GPT partitioned drive ad0: 1596 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" 1597 1598 Non-boot pools do not need these updates. 1599 1600 To build a kernel 1601 ----------------- 1602 If you are updating from a prior version of FreeBSD (even one just 1603 a few days old), you should follow this procedure. It is the most 1604 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1605 1606 make kernel-toolchain 1607 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1608 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1609 1610 To test a kernel once 1611 --------------------- 1612 If you just want to boot a kernel once (because you are not sure 1613 if it works, or if you want to boot a known bad kernel to provide 1614 debugging information) run 1615 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1616 nextboot -k testkernel 1617 1618 To just build a kernel when you know that it won't mess you up 1619 -------------------------------------------------------------- 1620 This assumes you are already running a CURRENT system. Replace 1621 ${arch} with the architecture of your machine (e.g. "i386", 1622 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 1623 1624 cd src/sys/${arch}/conf 1625 config KERNEL_NAME_HERE 1626 cd ../compile/KERNEL_NAME_HERE 1627 make depend 1628 make 1629 make install 1630 1631 If this fails, go to the "To build a kernel" section. 1632 1633 To rebuild everything and install it on the current system. 1634 ----------------------------------------------------------- 1635 # Note: sometimes if you are running current you gotta do more than 1636 # is listed here if you are upgrading from a really old current. 1637 1638 <make sure you have good level 0 dumps> 1639 make buildworld 1640 make kernel KERNCONF=YOUR_KERNEL_HERE 1641 [1] 1642 <reboot in single user> [3] 1643 mergemaster -p [5] 1644 make installworld 1645 mergemaster -i [4] 1646 make delete-old [6] 1647 <reboot> 1648 1649 1650 To cross-install current onto a separate partition 1651 -------------------------------------------------- 1652 # In this approach we use a separate partition to hold 1653 # current's root, 'usr', and 'var' directories. A partition 1654 # holding "/", "/usr" and "/var" should be about 2GB in 1655 # size. 1656 1657 <make sure you have good level 0 dumps> 1658 <boot into -stable> 1659 make buildworld 1660 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1661 <maybe newfs current's root partition> 1662 <mount current's root partition on directory ${CURRENT_ROOT}> 1663 make installworld DESTDIR=${CURRENT_ROOT} 1664 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1665 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1666 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1667 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1668 <reboot into current> 1669 <do a "native" rebuild/install as described in the previous section> 1670 <maybe install compatibility libraries from ports/misc/compat*> 1671 <reboot> 1672 1673 1674 To upgrade in-place from stable to current 1675 ---------------------------------------------- 1676 <make sure you have good level 0 dumps> 1677 make buildworld [9] 1678 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1679 [1] 1680 <reboot in single user> [3] 1681 mergemaster -p [5] 1682 make installworld 1683 mergemaster -i [4] 1684 make delete-old [6] 1685 <reboot> 1686 1687 Make sure that you've read the UPDATING file to understand the 1688 tweaks to various things you need. At this point in the life 1689 cycle of current, things change often and you are on your own 1690 to cope. The defaults can also change, so please read ALL of 1691 the UPDATING entries. 1692 1693 Also, if you are tracking -current, you must be subscribed to 1694 freebsd-current@freebsd.org. Make sure that before you update 1695 your sources that you have read and understood all the recent 1696 messages there. If in doubt, please track -stable which has 1697 much fewer pitfalls. 1698 1699 [1] If you have third party modules, such as vmware, you 1700 should disable them at this point so they don't crash your 1701 system on reboot. 1702 1703 [3] From the bootblocks, boot -s, and then do 1704 fsck -p 1705 mount -u / 1706 mount -a 1707 cd src 1708 adjkerntz -i # if CMOS is wall time 1709 Also, when doing a major release upgrade, it is required that 1710 you boot into single user mode to do the installworld. 1711 1712 [4] Note: This step is non-optional. Failure to do this step 1713 can result in a significant reduction in the functionality of the 1714 system. Attempting to do it by hand is not recommended and those 1715 that pursue this avenue should read this file carefully, as well 1716 as the archives of freebsd-current and freebsd-hackers mailing lists 1717 for potential gotchas. The -U option is also useful to consider. 1718 See mergemaster(8) for more information. 1719 1720 [5] Usually this step is a noop. However, from time to time 1721 you may need to do this if you get unknown user in the following 1722 step. It never hurts to do it all the time. You may need to 1723 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1724 install) after the buildworld before this step if you last updated 1725 from current before 20020224 or from -stable before 20020408. 1726 1727 [6] This only deletes old files and directories. Old libraries 1728 can be deleted by "make delete-old-libs", but you have to make 1729 sure that no program is using those libraries anymore. 1730 1731 [8] In order to have a kernel that can run the 4.x binaries needed to 1732 do an installworld, you must include the COMPAT_FREEBSD4 option in 1733 your kernel. Failure to do so may leave you with a system that is 1734 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 1735 required to run the 5.x binaries on more recent kernels. And so on 1736 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 1737 1738 Make sure that you merge any new devices from GENERIC since the 1739 last time you updated your kernel config file. 1740 1741 [9] When checking out sources, you must include the -P flag to have 1742 cvs prune empty directories. 1743 1744 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1745 "?=" instead of the "=" assignment operator, so that buildworld can 1746 override the CPUTYPE if it needs to. 1747 1748 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1749 not on the command line, or in /etc/make.conf. buildworld will 1750 warn if it is improperly defined. 1751FORMAT: 1752 1753This file contains a list, in reverse chronological order, of major 1754breakages in tracking -current. It is not guaranteed to be a complete 1755list of such breakages, and only contains entries since October 10, 2007. 1756If you need to see UPDATING entries from before that date, you will need 1757to fetch an UPDATING file from an older FreeBSD release. 1758 1759Copyright information: 1760 1761Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1762 1763Redistribution, publication, translation and use, with or without 1764modification, in full or in part, in any form or format of this 1765document are permitted without further permission from the author. 1766 1767THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1768IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1769WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1770DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1771INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1772(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1773SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1774HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1775STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1776IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1777POSSIBILITY OF SUCH DAMAGE. 1778 1779Contact Warner Losh if you have any questions about your use of 1780this document. 1781 1782$FreeBSD: head/UPDATING 247814 2013-03-04 21:18:45Z ken $ 1783