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