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