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