UPDATING revision 212567
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 9Items affecting the ports and packages system can be found in 10/usr/ports/UPDATING. Please read that file before running portupgrade. 11 12NOTE TO PEOPLE WHO THINK THAT FreeBSD 9.x IS SLOW: 13 FreeBSD 9.x has many debugging features turned on, in both the kernel 14 and userland. These features attempt to detect incorrect use of 15 system primitives, and encourage loud failure through extra sanity 16 checking and fail stop semantics. They also substantially impact 17 system performance. If you want to do performance measurement, 18 benchmarking, and optimization, you'll want to turn them off. This 19 includes various WITNESS- related kernel options, INVARIANTS, malloc 20 debugging flags in userland, and various verbose features in the 21 kernel. Many developers choose to disable these features on build 22 machines to maximize performance. (To disable malloc debugging, run 23 ln -s aj /etc/malloc.conf.) 24 2520100913: 26 DTrace has grown support for userland tracing. Due to this, DTrace is 27 now i386 and amd64 only. 28 dtruss(1) is now installed by default on those systems and a new 29 kernel module is needed for userland tracing: fasttrap. 30 No changes to your kernel config file are necessary to enable 31 userland tracing, but you might consider adding 'STRIP=' and 32 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want 33 to have informative userland stack traces in DTrace (ustack). 34 3520100725: 36 The acpi_aiboost(4) driver has been removed in favor of the new 37 aibs(4) driver. You should update your kernel configuration file. 38 3920100722: 40 BSD grep has been imported to the base system and it is built by 41 default. It is completely BSD licensed, highly GNU-compatible, uses 42 less memory than its GNU counterpart and has a small codebase. 43 However, it is slower than its GNU counterpart, which is mostly 44 noticeable for larger searches, for smaller ones it is measurable 45 but not significant. The reason is complex, the most important factor 46 is that we lack a modern and efficient regex library and GNU 47 overcomes this by optimizing the searches internally. Future work 48 on improving the regex performance is planned, for the meantime, 49 users that need better performance, can build GNU grep instead by 50 setting the WITH_GNU_GREP knob. 51 5220100713: 53 Due to the import of powerpc64 support, all existing powerpc kernel 54 configuration files must be updated with a machine directive like this: 55 machine powerpc powerpc 56 57 In addition, an updated config(8) is required to build powerpc kernels 58 after this change. 59 6020100713: 61 A new version of ZFS (version 15) has been merged to -HEAD. 62 This version uses a python library for the following subcommands: 63 zfs allow, zfs unallow, zfs groupspace, zfs userspace. 64 For full functionality of these commands the following port must 65 be installed: sysutils/py-zfs 66 6720100429: 68 'vm_page's are now hashed by physical address to an array of mutexes. 69 Currently this is only used to serialize access to hold_count. Over 70 time the page queue mutex will be peeled away. This changes the size 71 of pmap on every architecture. And requires all callers of vm_page_hold 72 and vm_page_unhold to be updated. 73 7420100402: 75 WITH_CTF can now be specified in src.conf (not recommended, there 76 are some problems with static executables), make.conf (would also 77 affect ports which do not use GNU make and do not override the 78 compile targets) or in the kernel config (via "makeoptions 79 WITH_CTF=yes"). 80 When WITH_CTF was specified there before this was silently ignored, 81 so make sure that WITH_CTF is not used in places which could lead 82 to unwanted behavior. 83 8420100311: 85 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32 86 to allow 32-bit compatibility on non-x86 platforms. All kernel 87 configurations on amd64 and ia64 platforms using these options must 88 be modified accordingly. 89 9020100113: 91 The utmp user accounting database has been replaced with utmpx, 92 the user accounting interface standardized by POSIX. 93 Unfortunately the semantics of utmp and utmpx don't match, 94 making it practically impossible to support both interfaces. 95 The user accounting database is used by tools like finger(1), 96 last(1), talk(1), w(1) and ac(8). 97 98 All applications in the base system use utmpx. This means only 99 local binaries (e.g. from the ports tree) may still use these 100 utmp database files. These applications must be rebuilt to make 101 use of utmpx. 102 103 After the system has been upgraded, it is safe to remove the old 104 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*), 105 assuming their contents is of no importance anymore. Old wtmp 106 databases can only be used by last(1) and ac(8) after they have 107 been converted to the new format using wtmpcvt(1). 108 10920100108: 110 Introduce the kernel thread "deadlock resolver" (which can be enabled 111 via the DEADLKRES option, see NOTES for more details) and the 112 sleepq_type() function for sleepqueues. 113 11420091202: 115 The rc.firewall and rc.firewall6 were unified, and 116 rc.firewall6 and rc.d/ip6fw were removed. 117 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc 118 variables are obsoleted. Instead, the following new rc 119 variables are added to rc.d/ipfw: 120 121 firewall_client_net_ipv6, firewall_simple_iif_ipv6, 122 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6, 123 firewall_simple_onet_ipv6, firewall_trusted_ipv6 124 125 The meanings correspond to the relevant IPv4 variables. 126 12720091125: 128 8.0-RELEASE. 129 13020091113: 131 The default terminal emulation for syscons(4) has been changed 132 from cons25 to xterm on all platforms except pc98. This means 133 that the /etc/ttys file needs to be updated to ensure correct 134 operation of applications on the console. 135 136 The terminal emulation style can be toggled per window by using 137 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration 138 options can be used to change the compile-time default back to 139 cons25. 140 141 To prevent graphical artifacts, make sure the TERM environment 142 variable is set to match the terminal emulation that is being 143 performed by syscons(4). 144 14520091109: 146 The layout of the structure ieee80211req_scan_result has changed. 147 Applications that require wireless scan results (e.g. ifconfig(8)) 148 from net80211 need to be recompiled. 149 150 Applications such as wpa_supplicant(8) may require a full world 151 build without using NO_CLEAN in order to get synchronized with the 152 new structure. 153 15420091025: 155 The iwn(4) driver has been updated to support the 5000 and 5150 series. 156 There's one kernel module for each firmware. Adding "device iwnfw" 157 to the kernel configuration file means including all three firmware 158 images inside the kernel. If you want to include just the one for 159 your wireless card, use the the devices iwn4965fw, iwn5000fw or 160 iwn5150fw. 161 16220090926: 163 The rc.d/network_ipv6, IPv6 configuration script has been integrated 164 into rc.d/netif. The changes are the following: 165 166 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF 167 for IPv4. For aliases, $ifconfig_IF_aliasN should be used. 168 Note that both variables need the "inet6" keyword at the head. 169 170 Do not set $ipv6_network_interfaces manually if you do not 171 understand what you are doing. It is not needed in most cases. 172 173 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but 174 they are obsolete. 175 176 2. $ipv6_enable is obsolete. Use $ipv6_prefer and 177 "inet6 accept_rtadv" keyword in ifconfig(8) instead. 178 179 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and 180 all configured interfaces have "inet6 accept_rtadv" in the 181 $ifconfig_IF_ipv6. These are for backward compatibility. 182 183 3. A new variable $ipv6_prefer has been added. If NO, IPv6 184 functionality of interfaces with no corresponding 185 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag, 186 and the default address selection policy of ip6addrctl(8) 187 is the IPv4-preferred one (see rc.d/ip6addrctl for more details). 188 Note that if you want to configure IPv6 functionality on the 189 disabled interfaces after boot, first you need to clear the flag by 190 using ifconfig(8) like: 191 192 ifconfig em0 inet6 -ifdisabled 193 194 If YES, the default address selection policy is set as 195 IPv6-preferred. 196 197 The default value of $ipv6_prefer is NO. 198 199 4. If your system need to receive Router Advertisement messages, 200 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8) 201 scripts automatically invoke rtsol(8) when the interface becomes 202 UP. The Router Advertisement messages are used for SLAAC 203 (State-Less Address AutoConfiguration). 204 20520090922: 206 802.11s D3.03 support was committed. This is incompatible with the 207 previous code, which was based on D3.0. 208 20920090912: 210 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value 211 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to 212 control whether accepting Router Advertisement messages or not. 213 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and 214 a sysctl variable net.inet6.ip6.auto_linklocal is its default value. 215 The ifconfig(8) utility now supports these flags. 216 21720090910: 218 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for 219 mount(8) and -a option for df(1) to see them. 220 22120090825: 222 The old tunable hw.bus.devctl_disable has been superseded by 223 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be 224 replaced by hw.bus.devctl_queue=0. The default for this new tunable 225 is 1000. 226 22720090813: 228 Remove the option STOP_NMI. The default action is now to use NMI only 229 for KDB via the newly introduced function stop_cpus_hard() and 230 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64. 231 23220090803: 233 The stable/8 branch created in subversion. This corresponds to the 234 RELENG_8 branch in CVS. 235 23620090719: 237 Bump the shared library version numbers for all libraries that do not 238 use symbol versioning as part of the 8.0-RELEASE cycle. Bump 239 __FreeBSD_version to 800105. 240 24120090714: 242 Due to changes in the implementation of virtual network stack support, 243 all network-related kernel modules must be recompiled. As this change 244 breaks the ABI, bump __FreeBSD_version to 800104. 245 24620090713: 247 The TOE interface to the TCP syncache has been modified to remove 248 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. 249 The cxgb driver is the only TOE consumer affected by this change, and 250 needs to be recompiled along with the kernel. As this change breaks 251 the ABI, bump __FreeBSD_version to 800103. 252 25320090712: 254 Padding has been added to struct tcpcb, sackhint and tcpstat in 255 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst 256 maintaining the ABI. However, this change breaks the ABI, so bump 257 __FreeBSD_version to 800102. User space tools that rely on the size of 258 any of these structs (e.g. sockstat) need to be recompiled. 259 26020090630: 261 The NFS_LEGACYRPC option has been removed along with the old kernel 262 RPC implementation that this option selected. Kernel configurations 263 may need to be adjusted. 264 26520090629: 266 The network interface device nodes at /dev/net/<interface> have been 267 removed. All ioctl operations can be performed the normal way using 268 routing sockets. The kqueue functionality can generally be replaced 269 with routing sockets. 270 27120090628: 272 The documentation from the FreeBSD Documentation Project (Handbook, 273 FAQ, etc.) is now installed via packages by sysinstall(8) and under 274 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc. 275 27620090624: 277 The ABI of various structures related to the SYSV IPC API have been 278 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel 279 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to 280 800100. 281 28220090622: 283 Layout of struct vnet has changed as routing related variables were 284 moved to their own Vimage module. Modules need to be recompiled. Bump 285 __FreeBSD_version to 800099. 286 28720090619: 288 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024 289 respectively. As long as no more than 16 groups per process are used, 290 no changes should be visible. When more than 16 groups are used, old 291 binaries may fail if they call getgroups() or getgrouplist() with 292 statically sized storage. Recompiling will work around this, but 293 applications should be modified to use dynamically allocated storage 294 for group arrays as POSIX.1-2008 does not cap an implementation's 295 number of supported groups at NGROUPS_MAX+1 as previous versions did. 296 297 NFS and portalfs mounts may also be affected as the list of groups is 298 truncated to 16. Users of NFS who use more than 16 groups, should 299 take care that negative group permissions are not used on the exported 300 file systems as they will not be reliable unless a GSSAPI based 301 authentication method is used. 302 30320090616: 304 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This 305 option compiles in the support for adaptive spinning for lockmgrs 306 which want to enable it. The lockinit() function now accepts the flag 307 LK_ADAPTIVE in order to make the lock object subject to adaptive 308 spinning when both held in write and read mode. 309 31020090613: 311 The layout of the structure returned by IEEE80211_IOC_STA_INFO has 312 changed. User applications that use this ioctl need to be rebuilt. 313 31420090611: 315 The layout of struct thread has changed. Kernel and modules need to 316 be rebuilt. 317 31820090608: 319 The layout of structs ifnet, domain, protosw and vnet_net has changed. 320 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097. 321 32220090602: 323 window(1) has been removed from the base system. It can now be 324 installed from ports. The port is called misc/window. 325 32620090601: 327 The way we are storing and accessing `routing table' entries has 328 changed. Programs reading the FIB, like netstat, need to be 329 re-compiled. 330 33120090601: 332 A new netisr implementation has been added for FreeBSD 8. Network 333 file system modules, such as igmp, ipdivert, and others, should be 334 rebuilt. 335 Bump __FreeBSD_version to 800096. 336 33720090530: 338 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no 339 more valid. 340 34120090530: 342 Add VOP_ACCESSX(9). File system modules need to be rebuilt. 343 Bump __FreeBSD_version to 800094. 344 34520090529: 346 Add mnt_xflag field to 'struct mount'. File system modules need to be 347 rebuilt. 348 Bump __FreeBSD_version to 800093. 349 35020090528: 351 The compiling option ADAPTIVE_SX has been retired while it has been 352 introduced the option NO_ADAPTIVE_SX which handles the reversed logic. 353 The KPI for sx_init_flags() changes as accepting flags: 354 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has 355 been introduced in order to handle the reversed logic. 356 Bump __FreeBSD_version to 800092. 357 35820090527: 359 Add support for hierarchical jails. Remove global securelevel. 360 Bump __FreeBSD_version to 800091. 361 36220090523: 363 The layout of struct vnet_net has changed, therefore modules 364 need to be rebuilt. 365 Bump __FreeBSD_version to 800090. 366 36720090523: 368 The newly imported zic(8) produces a new format in the output. Please 369 run tzsetup(8) to install the newly created data to /etc/localtime. 370 37120090520: 372 The sysctl tree for the usb stack has renamed from hw.usb2.* to 373 hw.usb.* and is now consistent again with previous releases. 374 37520090520: 376 802.11 monitor mode support was revised and driver api's were changed. 377 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead 378 of DLT_IEEE802_11. No user-visible data structures were changed but 379 applications that use DLT_IEEE802_11 may require changes. 380 Bump __FreeBSD_version to 800088. 381 38220090430: 383 The layout of the following structs has changed: sysctl_oid, 384 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet, 385 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or 386 panics may be experienced. World rebuild is required for 387 correctly checking networking state from userland. 388 Bump __FreeBSD_version to 800085. 389 39020090429: 391 MLDv2 and Source-Specific Multicast (SSM) have been merged 392 to the IPv6 stack. VIMAGE hooks are in but not yet used. 393 The implementation of SSM within FreeBSD's IPv6 stack closely 394 follows the IPv4 implementation. 395 396 For kernel developers: 397 398 * The most important changes are that the ip6_output() and 399 ip6_input() paths no longer take the IN6_MULTI_LOCK, 400 and this lock has been downgraded to a non-recursive mutex. 401 402 * As with the changes to the IPv4 stack to support SSM, filtering 403 of inbound multicast traffic must now be performed by transport 404 protocols within the IPv6 stack. This does not apply to TCP and 405 SCTP, however, it does apply to UDP in IPv6 and raw IPv6. 406 407 * The KPIs used by IPv6 multicast are similar to those used by 408 the IPv4 stack, with the following differences: 409 * im6o_mc_filter() is analogous to imo_multicast_filter(). 410 * The legacy KAME entry points in6_joingroup and in6_leavegroup() 411 are shimmed to in6_mc_join() and in6_mc_leave() respectively. 412 * IN6_LOOKUP_MULTI() has been deprecated and removed. 413 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs 414 for MLDv1 have an additional 'timer' argument which is used to 415 jitter the initial membership report for the solicited-node 416 multicast membership on-link. 417 * This is not strictly needed for MLDv2, which already jitters 418 its report transmissions. However, the 'timer' argument is 419 preserved in case MLDv1 is active on the interface. 420 421 * The KAME linked-list based IPv6 membership implementation has 422 been refactored to use a vector similar to that used by the IPv4 423 stack. 424 Code which maintains a list of its own multicast memberships 425 internally, e.g. carp, has been updated to reflect the new 426 semantics. 427 428 * There is a known Lock Order Reversal (LOR) due to in6_setscope() 429 acquiring the IF_AFDATA_LOCK and being called within ip6_output(). 430 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an 431 implementation constraint which needs to be addressed in HEAD. 432 433 For application developers: 434 435 * The changes are broadly similar to those made for the IPv4 436 stack. 437 438 * The use of IPv4 and IPv6 multicast socket options on the same 439 socket, using mapped addresses, HAS NOT been tested or supported. 440 441 * There are a number of issues with the implementation of various 442 IPv6 multicast APIs which need to be resolved in the API surface 443 before the implementation is fully compatible with KAME userland 444 use, and these are mostly to do with interface index treatment. 445 446 * The literature available discusses the use of either the delta / ASM 447 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API 448 using setsourcefilter(3)/getsourcefilter(3). For more information 449 please refer to RFC 3768, 'Socket Interface Extensions for 450 Multicast Source Filters'. 451 452 * Applications which use the published RFC 3678 APIs should be fine. 453 454 For systems administrators: 455 456 * The mtest(8) utility has been refactored to support IPv6, in 457 addition to IPv4. Interface addresses are no longer accepted 458 as arguments, their names must be used instead. The utility 459 will map the interface name to its first IPv4 address as 460 returned by getifaddrs(3). 461 462 * The ifmcstat(8) utility has also been updated to print the MLDv2 463 endpoint state and source filter lists via sysctl(3). 464 465 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable 466 loopback of IPv6 multicast datagrams by default; it defaults to 1 467 to preserve the existing behaviour. Disabling multicast loopback is 468 recommended for optimal system performance. 469 470 * The IPv6 MROUTING code has been changed to examine this sysctl 471 instead of attempting to perform a group lookup before looping 472 back forwarded datagrams. 473 474 Bump __FreeBSD_version to 800084. 475 47620090422: 477 Implement low-level Bluetooth HCI API. 478 Bump __FreeBSD_version to 800083. 479 48020090419: 481 The layout of struct malloc_type, used by modules to register new 482 memory allocation types, has changed. Most modules will need to 483 be rebuilt or panics may be experienced. 484 Bump __FreeBSD_version to 800081. 485 48620090415: 487 Anticipate overflowing inp_flags - add inp_flags2. 488 This changes most offsets in inpcb, so checking v4 connection 489 state will require a world rebuild. 490 Bump __FreeBSD_version to 800080. 491 49220090415: 493 Add an llentry to struct route and struct route_in6. Modules 494 embedding a struct route will need to be recompiled. 495 Bump __FreeBSD_version to 800079. 496 49720090414: 498 The size of rt_metrics_lite and by extension rtentry has changed. 499 Networking administration apps will need to be recompiled. 500 The route command now supports show as an alias for get, weighting 501 of routes, sticky and nostick flags to alter the behavior of stateful 502 load balancing. 503 Bump __FreeBSD_version to 800078. 504 50520090408: 506 Do not use Giant for kbdmux(4) locking. This is wrong and 507 apparently causing more problems than it solves. This will 508 re-open the issue where interrupt handlers may race with 509 kbdmux(4) in polling mode. Typical symptoms include (but 510 not limited to) duplicated and/or missing characters when 511 low level console functions (such as gets) are used while 512 interrupts are enabled (for example geli password prompt, 513 mountroot prompt etc.). Disabling kbdmux(4) may help. 514 51520090407: 516 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed; 517 kernel modules referencing any of the above need to be recompiled. 518 Bump __FreeBSD_version to 800075. 519 52020090320: 521 GEOM_PART has become the default partition slicer for storage devices, 522 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It 523 introduces some changes: 524 525 MSDOS/EBR: the devices created from MSDOS extended partition entries 526 (EBR) can be named differently than with GEOM_MBR and are now symlinks 527 to devices with offset-based names. fstabs may need to be modified. 528 529 BSD: the "geometry does not match label" warning is harmless in most 530 cases but it points to problems in file system misalignment with 531 disk geometry. The "c" partition is now implicit, covers the whole 532 top-level drive and cannot be (mis)used by users. 533 534 General: Kernel dumps are now not allowed to be written to devices 535 whose partition types indicate they are meant to be used for file 536 systems (or, in case of MSDOS partitions, as something else than 537 the "386BSD" type). 538 539 Most of these changes date approximately from 200812. 540 54120090319: 542 The uscanner(4) driver has been removed from the kernel. This follows 543 Linux removing theirs in 2.6 and making libusb the default interface 544 (supported by sane). 545 54620090319: 547 The multicast forwarding code has been cleaned up. netstat(1) 548 only relies on KVM now for printing bandwidth upcall meters. 549 The IPv4 and IPv6 modules are split into ip_mroute_mod and 550 ip6_mroute_mod respectively. The config(5) options for statically 551 compiling this code remain the same, i.e. 'options MROUTING'. 552 55320090315: 554 Support for the IFF_NEEDSGIANT network interface flag has been 555 removed, which means that non-MPSAFE network device drivers are no 556 longer supported. In particular, if_ar, if_sr, and network device 557 drivers from the old (legacy) USB stack can no longer be built or 558 used. 559 56020090313: 561 POSIX.1 Native Language Support (NLS) has been enabled in libc and 562 a bunch of new language catalog files have also been added. 563 This means that some common libc messages are now localized and 564 they depend on the LC_MESSAGES environmental variable. 565 56620090313: 567 The k8temp(4) driver has been renamed to amdtemp(4) since 568 support for Family 10 and Family 11 CPU families was added. 569 57020090309: 571 IGMPv3 and Source-Specific Multicast (SSM) have been merged 572 to the IPv4 stack. VIMAGE hooks are in but not yet used. 573 574 For kernel developers, the most important changes are that the 575 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(), 576 and this lock has been downgraded to a non-recursive mutex. 577 578 Transport protocols (UDP, Raw IP) are now responsible for filtering 579 inbound multicast traffic according to group membership and source 580 filters. The imo_multicast_filter() KPI exists for this purpose. 581 Transports which do not use multicast (SCTP, TCP) already reject 582 multicast by default. Forwarding and receive performance may improve 583 as a mutex acquisition is no longer needed in the ip_input() 584 low-level input path. in_addmulti() and in_delmulti() are shimmed 585 to new KPIs which exist to support SSM in-kernel. 586 587 For application developers, it is recommended that loopback of 588 multicast datagrams be disabled for best performance, as this 589 will still cause the lock to be taken for each looped-back 590 datagram transmission. The net.inet.ip.mcast.loop sysctl may 591 be tuned to 0 to disable loopback by default; it defaults to 1 592 to preserve the existing behaviour. 593 594 For systems administrators, to obtain best performance with 595 multicast reception and multiple groups, it is always recommended 596 that a card with a suitably precise hash filter is used. Hash 597 collisions will still result in the lock being taken within the 598 transport protocol input path to check group membership. 599 600 If deploying FreeBSD in an environment with IGMP snooping switches, 601 it is recommended that the net.inet.igmp.sendlocal sysctl remain 602 enabled; this forces 224.0.0.0/24 group membership to be announced 603 via IGMP. 604 605 The size of 'struct igmpstat' has changed; netstat needs to be 606 recompiled to reflect this. 607 Bump __FreeBSD_version to 800070. 608 60920090309: 610 libusb20.so.1 is now installed as libusb.so.1 and the ports system 611 updated to use it. This requires a buildworld/installworld in order to 612 update the library and dependencies (usbconfig, etc). Its advisable to 613 rebuild all ports which uses libusb. More specific directions are given 614 in the ports collection UPDATING file. Any /etc/libmap.conf entries for 615 libusb are no longer required and can be removed. 616 61720090302: 618 A workaround is committed to allow the creation of System V shared 619 memory segment of size > 2 GB on the 64-bit architectures. 620 Due to a limitation of the existing ABI, the shm_segsz member 621 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is 622 wrong for large segments. Note that limits must be explicitly 623 raised to allow such segments to be created. 624 62520090301: 626 The layout of struct ifnet has changed, requiring a rebuild of all 627 network device driver modules. 628 62920090227: 630 The /dev handling for the new USB stack has changed, a 631 buildworld/installworld is required for libusb20. 632 63320090223: 634 The new USB2 stack has now been permanently moved in and all kernel and 635 module names reverted to their previous values (eg, usb, ehci, ohci, 636 ums, ...). The old usb stack can be compiled in by prefixing the name 637 with the letter 'o', the old usb modules have been removed. 638 Updating entry 20090216 for xorg and 20090215 for libmap may still 639 apply. 640 64120090217: 642 The rc.conf(5) option if_up_delay has been renamed to 643 defaultroute_delay to better reflect its purpose. If you have 644 customized this setting in /etc/rc.conf you need to update it to 645 use the new name. 646 64720090216: 648 xorg 7.4 wants to configure its input devices via hald which does not 649 yet work with USB2. If the keyboard/mouse does not work in xorg then 650 add 651 Option "AllowEmptyInput" "off" 652 to your ServerLayout section. This will cause X to use the configured 653 kbd and mouse sections from your xorg.conf. 654 65520090215: 656 The GENERIC kernels for all architectures now default to the new USB2 657 stack. No kernel config options or code have been removed so if a 658 problem arises please report it and optionally revert to the old USB 659 stack. If you are loading USB kernel modules or have a custom kernel 660 that includes GENERIC then ensure that usb names are also changed over, 661 eg uftdi -> usb2_serial_ftdi. 662 663 Older programs linked against the ports libusb 0.1 need to be 664 redirected to the new stack's libusb20. /etc/libmap.conf can 665 be used for this: 666 # Map old usb library to new one for usb2 stack 667 libusb-0.1.so.8 libusb20.so.1 668 66920090209: 670 All USB ethernet devices now attach as interfaces under the name ueN 671 (eg. ue0). This is to provide a predictable name as vendors often 672 change usb chipsets in a product without notice. 673 67420090203: 675 The ichsmb(4) driver has been changed to require SMBus slave 676 addresses be left-justified (xxxxxxx0b) rather than right-justified. 677 All of the other SMBus controller drivers require left-justified 678 slave addresses, so this change makes all the drivers provide the 679 same interface. 680 68120090201: 682 INET6 statistics (struct ip6stat) was updated. 683 netstat(1) needs to be recompiled. 684 68520090119: 686 NTFS has been removed from GENERIC kernel on amd64 to match 687 GENERIC on i386. Should not cause any issues since mount_ntfs(8) 688 will load ntfs.ko module automatically when NTFS support is 689 actually needed, unless ntfs.ko is not installed or security 690 level prohibits loading kernel modules. If either is the case, 691 "options NTFS" has to be added into kernel config. 692 69320090115: 694 TCP Appropriate Byte Counting (RFC 3465) support added to kernel. 695 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to 696 800061. User space tools that rely on the size of struct tcpcb in 697 tcp_var.h (e.g. sockstat) need to be recompiled. 698 69920081225: 700 ng_tty(4) module updated to match the new TTY subsystem. 701 Due to API change, user-level applications must be updated. 702 New API support added to mpd5 CVS and expected to be present 703 in next mpd5.3 release. 704 70520081219: 706 With __FreeBSD_version 800060 the makefs tool is part of 707 the base system (it was a port). 708 70920081216: 710 The afdata and ifnet locks have been changed from mutexes to 711 rwlocks, network modules will need to be re-compiled. 712 71320081214: 714 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite. 715 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated. 716 The new code reduced struct rtentry{} by 16 bytes on 32-bit 717 architecture and 40 bytes on 64-bit architecture. The userland 718 applications "arp" and "ndp" have been updated accordingly. 719 The output from "netstat -r" shows only routing entries and 720 none of the L2 information. 721 72220081130: 723 __FreeBSD_version 800057 marks the switchover from the 724 binary ath hal to source code. Users must add the line: 725 726 options AH_SUPPORT_AR5416 727 728 to their kernel config files when specifying: 729 730 device ath_hal 731 732 The ath_hal module no longer exists; the code is now compiled 733 together with the driver in the ath module. It is now 734 possible to tailor chip support (i.e. reduce the set of chips 735 and thereby the code size); consult ath_hal(4) for details. 736 73720081121: 738 __FreeBSD_version 800054 adds memory barriers to 739 <machine/atomic.h>, new interfaces to ifnet to facilitate 740 multiple hardware transmit queues for cards that support 741 them, and a lock-less ring-buffer implementation to 742 enable drivers to more efficiently manage queueing of 743 packets. 744 74520081117: 746 A new version of ZFS (version 13) has been merged to -HEAD. 747 This version has zpool attribute "listsnapshots" off by 748 default, which means "zfs list" does not show snapshots, 749 and is the same as Solaris behavior. 750 75120081028: 752 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled. 753 75420081009: 755 The uhci, ohci, ehci and slhci USB Host controller drivers have 756 been put into separate modules. If you load the usb module 757 separately through loader.conf you will need to load the 758 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0 759 controller add the following to loader.conf: 760 761 uhci_load="YES" 762 ehci_load="YES" 763 76420081009: 765 The ABI used by the PMC toolset has changed. Please keep 766 userland (libpmc(3)) and the kernel module (hwpmc(4)) in 767 sync. 768 76920081009: 770 atapci kernel module now includes only generic PCI ATA 771 driver. AHCI driver moved to ataahci kernel module. 772 All vendor-specific code moved into separate kernel modules: 773 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek, 774 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron, 775 atamarvell, atamicron, atanational, atanetcell, atanvidia, 776 atapromise, ataserverworks, atasiliconimage, atasis, atavia 777 77820080820: 779 The TTY subsystem of the kernel has been replaced by a new 780 implementation, which provides better scalability and an 781 improved driver model. Most common drivers have been migrated to 782 the new TTY subsystem, while others have not. The following 783 drivers have not yet been ported to the new TTY layer: 784 785 PCI/ISA: 786 cy, digi, rc, rp, sio 787 788 USB: 789 ubser, ucycom 790 791 Line disciplines: 792 ng_h4, ng_tty, ppp, sl, snp 793 794 Adding these drivers to your kernel configuration file shall 795 cause compilation to fail. 796 79720080818: 798 ntpd has been upgraded to 4.2.4p5. 799 80020080801: 801 OpenSSH has been upgraded to 5.1p1. 802 803 For many years, FreeBSD's version of OpenSSH preferred DSA 804 over RSA for host and user authentication keys. With this 805 upgrade, we've switched to the vendor's default of RSA over 806 DSA. This may cause upgraded clients to warn about unknown 807 host keys even for previously known hosts. Users should 808 follow the usual procedure for verifying host keys before 809 accepting the RSA key. 810 811 This can be circumvented by setting the "HostKeyAlgorithms" 812 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh 813 command line. 814 815 Please note that the sequence of keys offered for 816 authentication has been changed as well. You may want to 817 specify IdentityFile in a different order to revert this 818 behavior. 819 82020080713: 821 The sio(4) driver has been removed from the i386 and amd64 822 kernel configuration files. This means uart(4) is now the 823 default serial port driver on those platforms as well. 824 825 To prevent collisions with the sio(4) driver, the uart(4) driver 826 uses different names for its device nodes. This means the 827 onboard serial port will now most likely be called "ttyu0" 828 instead of "ttyd0". You may need to reconfigure applications to 829 use the new device names. 830 831 When using the serial port as a boot console, be sure to update 832 /boot/device.hints and /etc/ttys before booting the new kernel. 833 If you forget to do so, you can still manually specify the hints 834 at the loader prompt: 835 836 set hint.uart.0.at="isa" 837 set hint.uart.0.port="0x3F8" 838 set hint.uart.0.flags="0x10" 839 set hint.uart.0.irq="4" 840 boot -s 841 84220080609: 843 The gpt(8) utility has been removed. Use gpart(8) to partition 844 disks instead. 845 84620080603: 847 The version that Linuxulator emulates was changed from 2.4.2 848 to 2.6.16. If you experience any problems with Linux binaries 849 please try to set sysctl compat.linux.osrelease to 2.4.2 and 850 if it fixes the problem contact emulation mailing list. 851 85220080525: 853 ISDN4BSD (I4B) was removed from the src tree. You may need to 854 update a your kernel configuration and remove relevant entries. 855 85620080509: 857 I have checked in code to support multiple routing tables. 858 See the man pages setfib(1) and setfib(2). 859 This is a hopefully backwards compatible version, 860 but to make use of it you need to compile your kernel 861 with options ROUTETABLES=2 (or more up to 16). 862 86320080420: 864 The 802.11 wireless support was redone to enable multi-bss 865 operation on devices that are capable. The underlying device 866 is no longer used directly but instead wlanX devices are 867 cloned with ifconfig. This requires changes to rc.conf files. 868 For example, change: 869 ifconfig_ath0="WPA DHCP" 870 to 871 wlans_ath0=wlan0 872 ifconfig_wlan0="WPA DHCP" 873 see rc.conf(5) for more details. In addition, mergemaster of 874 /etc/rc.d is highly recommended. Simultaneous update of userland 875 and kernel wouldn't hurt either. 876 877 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta 878 modules were merged into the base wlan module. All references 879 to these modules (e.g. in kernel config files) must be removed. 880 88120080408: 882 psm(4) has gained write(2) support in native operation level. 883 Arbitrary commands can be written to /dev/psm%d and status can 884 be read back from it. Therefore, an application is responsible 885 for status validation and error recovery. It is a no-op in 886 other operation levels. 887 88820080312: 889 Support for KSE threading has been removed from the kernel. To 890 run legacy applications linked against KSE libmap.conf may 891 be used. The following libmap.conf may be used to ensure 892 compatibility with any prior release: 893 894 libpthread.so.1 libthr.so.1 895 libpthread.so.2 libthr.so.2 896 libkse.so.3 libthr.so.3 897 89820080301: 899 The layout of struct vmspace has changed. This affects libkvm 900 and any executables that link against libkvm and use the 901 kvm_getprocs() function. In particular, but not exclusively, 902 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1). 903 The effects are minimal, but it's advisable to upgrade world 904 nonetheless. 905 90620080229: 907 The latest em driver no longer has support in it for the 908 82575 adapter, this is now moved to the igb driver. The 909 split was done to make new features that are incompatible 910 with older hardware easier to do. 911 91220080220: 913 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4), 914 likewise the kernel option is now GEOM_LINUX_LVM. 915 91620080211: 917 The default NFS mount mode has changed from UDP to TCP for 918 increased reliability. If you rely on (insecurely) NFS 919 mounting across a firewall you may need to update your 920 firewall rules. 921 92220080208: 923 Belatedly note the addition of m_collapse for compacting 924 mbuf chains. 925 92620080126: 927 The fts(3) structures have been changed to use adequate 928 integer types for their members and so to be able to cope 929 with huge file trees. The old fts(3) ABI is preserved 930 through symbol versioning in libc, so third-party binaries 931 using fts(3) should still work, although they will not take 932 advantage of the extended types. At the same time, some 933 third-party software might fail to build after this change 934 due to unportable assumptions made in its source code about 935 fts(3) structure members. Such software should be fixed 936 by its vendor or, in the worst case, in the ports tree. 937 FreeBSD_version 800015 marks this change for the unlikely 938 case that a portable fix is impossible. 939 94020080123: 941 To upgrade to -current after this date, you must be running 942 FreeBSD not older than 6.0-RELEASE. Upgrading to -current 943 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems. 944 94520071128: 946 The ADAPTIVE_GIANT kernel option has been retired because its 947 functionality is the default now. 948 94920071118: 950 The AT keyboard emulation of sunkbd(4) has been turned on 951 by default. In order to make the special symbols of the Sun 952 keyboards driven by sunkbd(4) work under X these now have 953 to be configured the same way as Sun USB keyboards driven 954 by ukbd(4) (which also does AT keyboard emulation), f.e.: 955 956 Option "XkbLayout" "us" 957 Option "XkbRules" "xorg" 958 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us" 959 96020071024: 961 It has been decided that it is desirable to provide ABI 962 backwards compatibility to the FreeBSD 4/5/6 versions of the 963 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was 964 broken with the introduction of PCI domain support (see the 965 20070930 entry). Unfortunately, this required the ABI of 966 PCIOCGETCONF to be broken again in order to be able to 967 provide backwards compatibility to the old version of that 968 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled 969 again. As for prominent ports this affects neither pciutils 970 nor xorg-server this time, the hal port needs to be rebuilt 971 however. 972 97320071020: 974 The misnamed kthread_create() and friends have been renamed 975 to kproc_create() etc. Many of the callers already 976 used kproc_start().. 977 I will return kthread_create() and friends in a while 978 with implementations that actually create threads, not procs. 979 Renaming corresponds with version 800002. 980 98120071010: 982 RELENG_7 branched. 983 984COMMON ITEMS: 985 986 General Notes 987 ------------- 988 Avoid using make -j when upgrading. While generally safe, there are 989 sometimes problems using -j to upgrade. If your upgrade fails with 990 -j, please try again without -j. From time to time in the past there 991 have been problems using -j with buildworld and/or installworld. This 992 is especially true when upgrading between "distant" versions (eg one 993 that cross a major release boundary or several minor releases, or when 994 several months have passed on the -current branch). 995 996 Sometimes, obscure build problems are the result of environment 997 poisoning. This can happen because the make utility reads its 998 environment when searching for values for global variables. To run 999 your build attempts in an "environmental clean room", prefix all make 1000 commands with 'env -i '. See the env(1) manual page for more details. 1001 1002 When upgrading from one major version to another it is generally best 1003 to upgrade to the latest code in the currently installed branch first, 1004 then do an upgrade to the new branch. This is the best-tested upgrade 1005 path, and has the highest probability of being successful. Please try 1006 this approach before reporting problems with a major version upgrade. 1007 1008 ZFS notes 1009 --------- 1010 When upgrading the boot ZFS pool to a new version, always follow 1011 these two steps: 1012 1013 1.) recompile and reinstall the ZFS boot loader and boot block 1014 (this is part of "make buildworld" and "make installworld") 1015 1016 2.) update the ZFS boot block on your boot drive 1017 1018 The following example updates the ZFS boot block on the first 1019 partition (freebsd-boot) of a GPT partitioned drive ad0: 1020 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" 1021 1022 Non-boot pools do not need these updates. 1023 1024 To build a kernel 1025 ----------------- 1026 If you are updating from a prior version of FreeBSD (even one just 1027 a few days old), you should follow this procedure. It is the most 1028 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1029 1030 make kernel-toolchain 1031 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1032 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1033 1034 To test a kernel once 1035 --------------------- 1036 If you just want to boot a kernel once (because you are not sure 1037 if it works, or if you want to boot a known bad kernel to provide 1038 debugging information) run 1039 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1040 nextboot -k testkernel 1041 1042 To just build a kernel when you know that it won't mess you up 1043 -------------------------------------------------------------- 1044 This assumes you are already running a CURRENT system. Replace 1045 ${arch} with the architecture of your machine (e.g. "i386", 1046 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 1047 1048 cd src/sys/${arch}/conf 1049 config KERNEL_NAME_HERE 1050 cd ../compile/KERNEL_NAME_HERE 1051 make depend 1052 make 1053 make install 1054 1055 If this fails, go to the "To build a kernel" section. 1056 1057 To rebuild everything and install it on the current system. 1058 ----------------------------------------------------------- 1059 # Note: sometimes if you are running current you gotta do more than 1060 # is listed here if you are upgrading from a really old current. 1061 1062 <make sure you have good level 0 dumps> 1063 make buildworld 1064 make kernel KERNCONF=YOUR_KERNEL_HERE 1065 [1] 1066 <reboot in single user> [3] 1067 mergemaster -p [5] 1068 make installworld 1069 make delete-old 1070 mergemaster -i [4] 1071 <reboot> 1072 1073 1074 To cross-install current onto a separate partition 1075 -------------------------------------------------- 1076 # In this approach we use a separate partition to hold 1077 # current's root, 'usr', and 'var' directories. A partition 1078 # holding "/", "/usr" and "/var" should be about 2GB in 1079 # size. 1080 1081 <make sure you have good level 0 dumps> 1082 <boot into -stable> 1083 make buildworld 1084 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1085 <maybe newfs current's root partition> 1086 <mount current's root partition on directory ${CURRENT_ROOT}> 1087 make installworld DESTDIR=${CURRENT_ROOT} 1088 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1089 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1090 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1091 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1092 <reboot into current> 1093 <do a "native" rebuild/install as described in the previous section> 1094 <maybe install compatibility libraries from ports/misc/compat*> 1095 <reboot> 1096 1097 1098 To upgrade in-place from 8.x-stable to current 1099 ---------------------------------------------- 1100 <make sure you have good level 0 dumps> 1101 make buildworld [9] 1102 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1103 [1] 1104 <reboot in single user> [3] 1105 mergemaster -p [5] 1106 make installworld 1107 make delete-old 1108 mergemaster -i [4] 1109 <reboot> 1110 1111 Make sure that you've read the UPDATING file to understand the 1112 tweaks to various things you need. At this point in the life 1113 cycle of current, things change often and you are on your own 1114 to cope. The defaults can also change, so please read ALL of 1115 the UPDATING entries. 1116 1117 Also, if you are tracking -current, you must be subscribed to 1118 freebsd-current@freebsd.org. Make sure that before you update 1119 your sources that you have read and understood all the recent 1120 messages there. If in doubt, please track -stable which has 1121 much fewer pitfalls. 1122 1123 [1] If you have third party modules, such as vmware, you 1124 should disable them at this point so they don't crash your 1125 system on reboot. 1126 1127 [3] From the bootblocks, boot -s, and then do 1128 fsck -p 1129 mount -u / 1130 mount -a 1131 cd src 1132 adjkerntz -i # if CMOS is wall time 1133 Also, when doing a major release upgrade, it is required that 1134 you boot into single user mode to do the installworld. 1135 1136 [4] Note: This step is non-optional. Failure to do this step 1137 can result in a significant reduction in the functionality of the 1138 system. Attempting to do it by hand is not recommended and those 1139 that pursue this avenue should read this file carefully, as well 1140 as the archives of freebsd-current and freebsd-hackers mailing lists 1141 for potential gotchas. The -U option is also useful to consider. 1142 See mergemaster(8) for more information. 1143 1144 [5] Usually this step is a noop. However, from time to time 1145 you may need to do this if you get unknown user in the following 1146 step. It never hurts to do it all the time. You may need to 1147 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1148 install) after the buildworld before this step if you last updated 1149 from current before 20020224 or from -stable before 20020408. 1150 1151 [8] In order to have a kernel that can run the 4.x binaries needed to 1152 do an installworld, you must include the COMPAT_FREEBSD4 option in 1153 your kernel. Failure to do so may leave you with a system that is 1154 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 1155 required to run the 5.x binaries on more recent kernels. And so on 1156 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 1157 1158 Make sure that you merge any new devices from GENERIC since the 1159 last time you updated your kernel config file. 1160 1161 [9] When checking out sources, you must include the -P flag to have 1162 cvs prune empty directories. 1163 1164 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1165 "?=" instead of the "=" assignment operator, so that buildworld can 1166 override the CPUTYPE if it needs to. 1167 1168 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1169 not on the command line, or in /etc/make.conf. buildworld will 1170 warn if it is improperly defined. 1171FORMAT: 1172 1173This file contains a list, in reverse chronological order, of major 1174breakages in tracking -current. Not all things will be listed here, 1175and it only starts on October 16, 2004. Updating files can found in 1176previous releases if your system is older than this. 1177 1178Copyright information: 1179 1180Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1181 1182Redistribution, publication, translation and use, with or without 1183modification, in full or in part, in any form or format of this 1184document are permitted without further permission from the author. 1185 1186THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1187IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1188WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1189DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1190INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1191(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1192SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1193HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1194STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1195IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1196POSSIBILITY OF SUCH DAMAGE. 1197 1198Contact Warner Losh if you have any questions about your use of 1199this document. 1200 1201$FreeBSD: head/UPDATING 212567 2010-09-13 17:49:39Z rpaulo $ 1202