UPDATING revision 273438
1Updating Information for FreeBSD current users 2 3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4See end of file for further details. For commonly done items, please see the 5COMMON ITEMS: section later in the file. These instructions assume that you 6basically know what you are doing. If not, then please consult the FreeBSD 7handbook: 8 9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html 10 11Items affecting the ports and packages system can be found in 12/usr/ports/UPDATING. Please read that file before running portupgrade. 13 1420141022: p4 FreeBSD-EN-14:10.tzdata 15 FreeBSD-EN-14:11.crypt 16 17 Time zone data file update. [EN-14:10] 18 19 Change crypt(3) default hashing algorithm back to DES. [EN-14:11] 20 2120141021: p3 FreeBSD-SA-14:20.rtsold 22 FreeBSD-SA-14:21.routed 23 FreeBSD-SA-14:22.namei 24 FreeBSD-SA-14:23.openssl 25 26 Fix rtsold(8) remote buffer overflow vulnerability. [SA-14:20] 27 28 Fix routed(8) remote denial of service vulnerability. [SA-14:21] 29 30 Fix memory leak in sandboxed namei lookup. [SA-14:22] 31 32 Fix OpenSSL multiple vulnerabilities. [SA-14:23] 33 3420140916: p2 FreeBSD-SA-14:19.tcp 35 Fix Denial of Service in TCP packet processing. [SA-14:19] 36 3720140909: p1 FreeBSD-SA-14:18.openssl 38 Fix OpenSSL multiple vulnerabilities. [SA-14:18] 39 4020140716: 41 9.3-RELEASE. 42 4320140608: 44 On i386 and amd64 systems, the onifconsole flag is now set by default 45 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled 46 as a login TTY if it is set in the bootloader as an active kernel 47 console. No changes in behavior should result otherwise. To revert to 48 the previous behavior, set ttyu0 to "off" in /etc/ttys. 49 5020140512: 51 Clang and llvm have been upgraded to 3.4.1 release. 52 5320140321: 54 Clang and llvm have been upgraded to 3.4 release. 55 5620140216: 57 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has 58 been deprecated and will not be part of FreeBSD 11.0 and later 59 releases. If you use this driver, please consider switching to 60 the nfe(4) driver instead. 61 6220131216: 63 The behavior of gss_pseudo_random() for the krb5 mechanism 64 has changed, for applications requesting a longer random string 65 than produced by the underlying enctype's pseudo-random() function. 66 In particular, the random string produced from a session key of 67 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 68 be different at the 17th octet and later, after this change. 69 The counter used in the PRF+ construction is now encoded as a 70 big-endian integer in accordance with RFC 4402. 71 __FreeBSD_version is bumped to 902505. 72 7320130930: 74 9.2-RELEASE. 75 7620130823: 77 Behavior of devfs rules path matching has been changed. 78 Pattern is now always matched against fully qualified devfs 79 path and slash characters must be explicitly matched by 80 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 81 subdirectories must be reviewed. 82 8320130705: 84 hastctl(8)'s `status' command output changed to terse one-liner format. 85 Scripts using this should switch to `list' command or be rewritten. 86 8720130618: 88 Fix a bug that allowed a tracing process (e.g. gdb) to write 89 to a memory-mapped file in the traced process's address space 90 even if neither the traced process nor the tracing process had 91 write access to that file. 92 9320130605: 94 Added ZFS TRIM support which is enabled by default. To disable 95 ZFS TRIM support set vfs.zfs.trim.enabled=0 in loader.conf. 96 97 Creating new ZFS pools and adding new devices to existing pools 98 first performs a full device level TRIM which can take a significant 99 amount of time. The sysctl vfs.zfs.vdev.trim_on_init can be set to 0 100 to disable this behaviour. 101 102 ZFS TRIM requires the underlying device support BIO_DELETE which 103 is currently provided by methods such as ATA TRIM and SCSI UNMAP 104 via CAM, which are typically supported by SSD's. 105 106 Stats for ZFS TRIM can be monitored by looking at the sysctl's 107 under kstat.zfs.misc.zio_trim. 108 10920130524: 110 `list' command has been added to hastctl(8). For now, it is full 111 equivalent of `status' command. 112 WARNING: in the near future the output of hastctl's status command 113 will change to more terse format. If you use `hastctl status' 114 for parsing in your scripts, switch to `hastctl list'. 115 11620130430: 117 The mergemaster command now uses the default MAKEOBJDIRPREFIX 118 rather than creating it's own in the temporary directory in 119 order allow access to bootstrapped versions of tools such as 120 install and mtree. When upgrading from version of FreeBSD where 121 the install command does not support -l, you will need to 122 install a new mergemaster command if mergemaster -p is required. 123 This can be accomplished with the command (cd src/usr.sbin/mergemaster 124 && make install). 125 126 Due to the use of the new -l option to install(1) during build 127 and install, you must take care not to directly set the INSTALL 128 make variable in your /etc/make.conf, /etc/src.conf, or on the 129 command line. If you wish to use the -C flag for all installs 130 you may be able to add INSTALL+=-C to /etc/make.conf or 131 /etc/src.conf. 132 13320130429: 134 Fix a bug that allows NFS clients to issue READDIR on files. 135 13620130315: 137 The install(1) option -M has changed meaning and now takes an 138 argument that is a file or path to append logs to. In the 139 unlikely event that -M was the last option on the command line 140 and the command line contained at least two files and a target 141 directory the first file will have logs appended to it. The -M 142 option served little practical purpose in the last decade so it's 143 used expected to be extremely rare. 144 14520130225: 146 A new compression method (lz4) has been merged to. Please refer to 147 zpool-features(7) for more information. 148 149 Please refer to the "ZFS notes" section of this file for information 150 on upgrading boot ZFS pools. 151 15220121224: 153 The VFS KBI was changed with the merge of several nullfs 154 optimizations and fixes. All filesystem modules must be 155 recompiled. 156 15720121218: 158 With the addition of auditdistd(8), a new auditdistd user is now 159 depended on during installworld. "mergemaster -p" can be used to add 160 the user prior to installworld, as documented in the handbook. 161 16220121205: 163 9.1-RELEASE. 164 16520121129: 166 A new version of ZFS (pool version 5000) has been merged to 9-STABLE. 167 Starting with this version the old system of ZFS pool versioning 168 is superseded by "feature flags". This concept enables forward 169 compatibility against certain future changes in functionality of ZFS 170 pools. The first two read-only compatible "feature flags" for ZFS 171 pools are "com.delphix:async_destroy" and "com.delphix:empty_bpobj". 172 For more information read the new zpool-features(7) manual page. 173 Please refer to the "ZFS notes" section of this file for information 174 on upgrading boot ZFS pools. 175 17620121114: 177 The commit introducing bsd.compiler.mk breaks the traditional 178 building of kernels before this point. Add -m ${SRC}/share/mk 179 (for the right value of SRC) to your command lines to work 180 around; update your useland to a point after this; or use the 181 buildkernel/installkernel top-level targets. See also 20120829. 182 18320121102: 184 The IPFIREWALL_FORWARD kernel option has been removed. Its 185 functionality now turned on by default. 186 18720120913: 188 The random(4) support for the VIA hardware random number 189 generator (`PADLOCK') is no longer enabled unconditionally. 190 Add the PADLOCK_RNG option in the custom kernel config if 191 needed. The GENERIC kernels on i386 and amd64 do include the 192 option, so the change only affects the custom kernel 193 configurations. 194 19520120829: 196 The amd64 kernel now uses xsetbv, xrstor instructions. To compile with 197 the traditional method, you must update your system with an installworld 198 before the kernel will build. The documented make buildkernel/installkernel 199 interfaces (coupled with fresh make kernel-toolchain) continue to work. 200 20120120727: 202 The sparc64 ZFS loader has been changed to no longer try to auto- 203 detect ZFS providers based on diskN aliases but now requires these 204 to be explicitly listed in the OFW boot-device environment variable. 205 20620120422: 207 Now unix domain sockets behave "as expected" on nullfs(5). Previously 208 nullfs(5) did not pass through all behaviours to the underlying layer, 209 as a result if we bound to a socket on the lower layer we could connect 210 only to the lower path; if we bound to the upper layer we could connect 211 only to the upper path. The new behavior is one can connect to both the 212 lower and the upper paths regardless what layer path one binds to. 213 21420120109: 215 The acpi_wmi(4) status device /dev/wmistat has been renamed to 216 /dev/wmistat0. 217 21820120106: 219 A new VOP_ADVISE() was added to support posix_fadvise(2). All 220 filesystem modules must be recompiled. 221 22220120106: 223 The interface of the VOP_VPTOCNP(9) changed, now the returned 224 vnode shall be referenced, previously it was required to be 225 only held. All in-tree filesystems are converted. 226 22720120106: 228 9.0-RELEASE. 229 23020111101: 231 The broken amd(4) driver has been replaced with esp(4) in the amd64, 232 i386 and pc98 GENERIC kernel configuration files. 233 23420110913: 235 This commit modifies vfs_register() so that it uses a hash 236 calculation to set vfc_typenum, which is enabled by default. 237 The first time a system is booted after this change, the 238 vfc_typenum values will change for all file systems. The 239 main effect of this is a change to the NFS server file handles 240 for file systems that use vfc_typenum in their fsid, such as ZFS. 241 It will, however, prevent vfc_typenum from changing when file 242 systems are loaded in a different order for subsequent reboots. 243 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf 244 until you are ready to remount all NFS clients after a reboot. 245 24620110828: 247 Bump the shared library version numbers for libraries that 248 do not use symbol versioning, have changed the ABI compared 249 to stable/8 and which shared library version was not bumped. 250 Done as part of 9.0-RELEASE cycle. 251 25220110815: 253 During the merge of Capsicum features, the fget(9) KPI was modified. 254 This may require the rebuilding of out-of-tree device drivers -- 255 issues have been reported specifically with the nVidia device driver. 256 __FreeBSD_version is bumped to 900041. 257 258 Also, there is a period between 20110811 and 20110814 where the 259 special devices /dev/{stdin,stdout,stderr} did not work correctly. 260 Building world from a kernel during that window may not work. 261 26220110628: 263 The packet filter (pf) code has been updated to OpenBSD 4.5. 264 You need to update userland tools to be in sync with kernel. 265 This update breaks backward compatibility with earlier pfsync(4) 266 versions. Care must be taken when updating redundant firewall setups. 267 26820110608: 269 The following sysctls and tunables are retired on x86 platforms: 270 machdep.hlt_cpus 271 machdep.hlt_logical_cpus 272 The following sysctl is retired: 273 machdep.hyperthreading_allowed 274 The sysctls were supposed to provide a way to dynamically offline and 275 online selected CPUs on x86 platforms, but the implementation has not 276 been reliable especially with SCHED_ULE scheduler. 277 machdep.hyperthreading_allowed tunable is still available to ignore 278 hyperthreading CPUs at OS level. 279 Individual CPUs can be disabled using hint.lapic.X.disabled tunable, 280 where X is an APIC ID of a CPU. Be advised, though, that disabling 281 CPUs in non-uniform fashion will result in non-uniform topology and 282 may lead to sub-optimal system performance with SCHED_ULE, which is 283 a default scheduler. 284 28520110607: 286 cpumask_t type is retired and cpuset_t is used in order to describe 287 a mask of CPUs. 288 28920110531: 290 Changes to ifconfig(8) for dynamic address family detection mandate 291 that you are running a kernel of 20110525 or later. Make sure to 292 follow the update procedure to boot a new kernel before installing 293 world. 294 29520110513: 296 Support for sun4v architecture is officially dropped 297 29820110503: 299 Several KPI breaking changes have been committed to the mii(4) layer, 300 the PHY drivers and consequently some Ethernet drivers using mii(4). 301 This means that miibus.ko and the modules of the affected Ethernet 302 drivers need to be recompiled. 303 304 Note to kernel developers: Given that the OUI bit reversion problem 305 was fixed as part of these changes all mii(4) commits related to OUIs, 306 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific 307 handling, no longer can be merged verbatim to stable/8 and previous 308 branches. 309 31020110430: 311 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci' 312 into their kernel configurations along with 'device pci'. 313 31420110427: 315 The default NFS client is now the new NFS client, so fstype "newnfs" 316 is now "nfs" and the regular/old NFS client is now fstype "oldnfs". 317 Although mounts via fstype "nfs" will usually work without userland 318 changes, it is recommended that the mount(8) and mount_nfs(8) 319 commands be rebuilt from sources and that a link to mount_nfs called 320 mount_oldnfs be created. The new client is compiled into the 321 kernel with "options NFSCL" and this is needed for diskless root 322 file systems. The GENERIC kernel configs have been changed to use 323 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER. 324 To use the regular/old client, you can "mount -t oldnfs ...". For 325 a diskless root file system, you must also include a line like: 326 327 vfs.root.mountfrom="oldnfs:" 328 329 in the boot/loader.conf on the root fs on the NFS server to make 330 a diskless root fs use the old client. 331 33220110424: 333 The GENERIC kernels for all architectures now default to the new 334 CAM-based ATA stack. It means that all legacy ATA drivers were 335 removed and replaced by respective CAM drivers. If you are using 336 ATA device names in /etc/fstab or other places, make sure to update 337 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, 338 where 'Y's are the sequential numbers starting from zero for each type 339 in order of detection, unless configured otherwise with tunables, 340 see cam(4)). There will be symbolic links created in /dev/ to map 341 old adX devices to the respective adaY. They should provide basic 342 compatibility for file systems mounting in most cases, but they do 343 not support old user-level APIs and do not have respective providers 344 in GEOM. Consider using updated management tools with new device names. 345 346 It is possible to load devices ahci, ata, siis and mvs as modules, 347 but option ATA_CAM should remain in kernel configuration to make ata 348 module work as CAM driver supporting legacy ATA controllers. Device ata 349 still can be used in modular fashion (atacore + ...). Modules atadisk 350 and atapi* are not used and won't affect operation in ATA_CAM mode. 351 Note that to use CAM-based ATA kernel should include CAM devices 352 scbus, pass, da (or explicitly ada), cd and optionally others. All of 353 them are parts of the cam module. 354 355 ataraid(4) functionality is now supported by the RAID GEOM class. 356 To use it you can load geom_raid kernel module and use graid(8) tool 357 for management. Instead of /dev/arX device names, use /dev/raid/rX. 358 359 No kernel config options or code have been removed, so if a problem 360 arises, please report it and optionally revert to the old ATA stack. 361 In order to do it you can remove from the kernel config: 362 options ATA_CAM 363 device ahci 364 device mvs 365 device siis 366 , and instead add back: 367 device atadisk # ATA disk drives 368 device ataraid # ATA RAID drives 369 device atapicd # ATAPI CDROM drives 370 device atapifd # ATAPI floppy drives 371 device atapist # ATAPI tape drives 372 37320110423: 374 The default NFS server has been changed to the new server, which 375 was referred to as the experimental server. If you need to switch 376 back to the old NFS server, you must now put the "-o" option on 377 both the mountd and nfsd commands. This can be done using the 378 mountd_flags and nfs_server_flags rc.conf variables until an 379 update to the rc scripts is committed, which is coming soon. 380 38120110418: 382 The GNU Objective-C runtime library (libobjc), and other Objective-C 383 related components have been removed from the base system. If you 384 require an Objective-C library, please use one of the available ports. 385 38620110331: 387 ath(4) has been split into bus- and device- modules. if_ath contains 388 the HAL, the TX rate control and the network device code. if_ath_pci 389 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb 390 contains the AHB glue. Users need to load both if_ath_pci and if_ath 391 in order to use ath on everything else. 392 393 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only 394 need to load if_ath and if_ath_pci for ath(4) operation. 395 39620110314: 397 As part of the replacement of sysinstall, the process of building 398 release media has changed significantly. For details, please re-read 399 release(7), which has been updated to reflect the new build process. 400 40120110218: 402 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This 403 is the last available version under GPLv2. It brings a number of new 404 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE 405 4.1 and SSE 4.2), better support for powerpc64, a number of new 406 directives, and lots of other small improvements. See the ChangeLog 407 file in contrib/binutils for the full details. 408 40920110218: 410 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868 411 compliant, and will now use half of hash for authentication. 412 This will break interoperability with all stacks (including all 413 actual FreeBSD versions) who implement 414 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for 415 authentication). 416 The only workaround with such peers is to use another HMAC 417 algorithm for IPsec ("phase 2") authentication. 418 41920110207: 420 Remove the uio_yield prototype and symbol. This function has 421 been misnamed since it was introduced and should not be 422 globally exposed with this name. The equivalent functionality 423 is now available using kern_yield(curthread->td_user_pri). 424 The function remains undocumented. 425 42620110112: 427 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers, 428 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking 429 for scalar sysctls is defined but disabled. Code that needs 430 UQUAD to pass the type checking that must compile on older 431 systems where the define is not present can check against 432 __FreeBSD_version >= 900030. 433 434 The system dialog(1) has been replaced with a new version previously 435 in ports as devel/cdialog. dialog(1) is mostly command-line compatible 436 with the previous version, but the libdialog associated with it has 437 a largely incompatible API. As such, the original version of libdialog 438 will be kept temporarily as libodialog, until its base system consumers 439 are replaced or updated. Bump __FreeBSD_version to 900030. 440 44120110103: 442 If you are trying to run make universe on a -stable system, and you get 443 the following warning: 444 "Makefile", line 356: "Target architecture for i386/conf/GENERIC 445 unknown. config(8) likely too old." 446 or something similar to it, then you must upgrade your -stable system 447 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in 448 stable/8) or build the config from the latest stable/8 branch and 449 install it on your system. 450 451 Prior to this date, building a current universe on 8-stable system from 452 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing 453 error in the first kernel build phase. A new config on those old 454 systems will fix that problem for older versions of -current. 455 45620101228: 457 The TCP stack has been modified to allow Khelp modules to interact with 458 it via helper hook points and store per-connection data in the TCP 459 control block. Bump __FreeBSD_version to 900029. User space tools that 460 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to 461 be recompiled. 462 46320101114: 464 Generic IEEE 802.3 annex 31B full duplex flow control support has been 465 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along 466 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted 467 to take advantage of it instead of using custom implementations. This 468 means that these drivers now no longer unconditionally advertise 469 support for flow control but only do so if flow control is a selected 470 media option. This was implemented in the generic support that way in 471 order to allow flow control to be switched on and off via ifconfig(8) 472 with the PHY specific default to typically off in order to protect 473 from unwanted effects. Consequently, if you used flow control with 474 one of the above mentioned drivers you now need to explicitly enable 475 it, for example via: 476 ifconfig bge0 media auto mediaopt flowcontrol 477 478 Along with the above mentioned changes generic support for setting 479 1000baseT master mode also has been added and brgphy(4), ciphy(4), 480 e1000phy(4) as well as ip1000phy(4) have been converted to take 481 advantage of it. This means that these drivers now no longer take the 482 link0 parameter for selecting master mode but the master media option 483 has to be used instead, for example like in the following: 484 ifconfig bge0 media 1000baseT mediaopt full-duplex,master 485 486 Selection of master mode now is also available with all other PHY 487 drivers supporting 1000baseT. 488 48920101111: 490 The TCP stack has received a significant update to add support for 491 modularised congestion control and generally improve the clarity of 492 congestion control decisions. Bump __FreeBSD_version to 900025. User 493 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g. 494 sockstat) need to be recompiled. 495 49620101002: 497 The man(1) utility has been replaced by a new version that no longer 498 uses /etc/manpath.config. Please consult man.conf(5) for how to 499 migrate local entries to the new format. 500 50120100928: 502 The copyright strings printed by login(1) and sshd(8) at the time of a 503 new connection have been removed to follow other operating systems and 504 upstream sshd. 505 50620100915: 507 A workaround for a fixed ld bug has been removed in kernel code, 508 so make sure that your system ld is built from sources after 509 revision 210245 from 2010-07-19 (r211583 if building head kernel 510 on stable/8, r211584 for stable/7; both from 2010-08-21). 511 A symptom of incorrect ld version is different addresses for 512 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules. 513 51420100913: 515 The $ipv6_prefer variable in rc.conf(5) has been split into 516 $ip6addrctl_policy and $ipv6_activate_all_interfaces. 517 518 The $ip6addrctl_policy is a variable to choose a pre-defined 519 address selection policy set by ip6addrctl(8). A value 520 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The 521 default is "AUTO". 522 523 The $ipv6_activate_all_interfaces specifies whether IFDISABLED 524 flag (see an entry of 20090926) is set on an interface with no 525 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for 526 security reason. If you want IPv6 link-local address on all 527 interfaces by default, set this to "YES". 528 529 The old ipv6_prefer="YES" is equivalent to 530 ipv6_activate_all_interfaces="YES" and 531 ip6addrctl_policy="ipv6_prefer". 532 53320100913: 534 DTrace has grown support for userland tracing. Due to this, DTrace is 535 now i386 and amd64 only. 536 dtruss(1) is now installed by default on those systems and a new 537 kernel module is needed for userland tracing: fasttrap. 538 No changes to your kernel config file are necessary to enable 539 userland tracing, but you might consider adding 'STRIP=' and 540 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want 541 to have informative userland stack traces in DTrace (ustack). 542 54320100725: 544 The acpi_aiboost(4) driver has been removed in favor of the new 545 aibs(4) driver. You should update your kernel configuration file. 546 54720100722: 548 BSD grep has been imported to the base system and it is built by 549 default. It is completely BSD licensed, highly GNU-compatible, uses 550 less memory than its GNU counterpart and has a small codebase. 551 However, it is slower than its GNU counterpart, which is mostly 552 noticeable for larger searches, for smaller ones it is measurable 553 but not significant. The reason is complex, the most important factor 554 is that we lack a modern and efficient regex library and GNU 555 overcomes this by optimizing the searches internally. Future work 556 on improving the regex performance is planned, for the meantime, 557 users that need better performance, can build GNU grep instead by 558 setting the WITH_GNU_GREP knob. 559 56020100713: 561 Due to the import of powerpc64 support, all existing powerpc kernel 562 configuration files must be updated with a machine directive like this: 563 machine powerpc powerpc 564 565 In addition, an updated config(8) is required to build powerpc kernels 566 after this change. 567 56820100713: 569 A new version of ZFS (version 15) has been merged to -HEAD. 570 This version uses a python library for the following subcommands: 571 zfs allow, zfs unallow, zfs groupspace, zfs userspace. 572 For full functionality of these commands the following port must 573 be installed: sysutils/py-zfs 574 57520100429: 576 'vm_page's are now hashed by physical address to an array of mutexes. 577 Currently this is only used to serialize access to hold_count. Over 578 time the page queue mutex will be peeled away. This changes the size 579 of pmap on every architecture. And requires all callers of vm_page_hold 580 and vm_page_unhold to be updated. 581 58220100402: 583 WITH_CTF can now be specified in src.conf (not recommended, there 584 are some problems with static executables), make.conf (would also 585 affect ports which do not use GNU make and do not override the 586 compile targets) or in the kernel config (via "makeoptions 587 WITH_CTF=yes"). 588 When WITH_CTF was specified there before this was silently ignored, 589 so make sure that WITH_CTF is not used in places which could lead 590 to unwanted behavior. 591 59220100311: 593 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32 594 to allow 32-bit compatibility on non-x86 platforms. All kernel 595 configurations on amd64 and ia64 platforms using these options must 596 be modified accordingly. 597 59820100113: 599 The utmp user accounting database has been replaced with utmpx, 600 the user accounting interface standardized by POSIX. 601 Unfortunately the semantics of utmp and utmpx don't match, 602 making it practically impossible to support both interfaces. 603 The user accounting database is used by tools like finger(1), 604 last(1), talk(1), w(1) and ac(8). 605 606 All applications in the base system use utmpx. This means only 607 local binaries (e.g. from the ports tree) may still use these 608 utmp database files. These applications must be rebuilt to make 609 use of utmpx. 610 611 After the system has been upgraded, it is safe to remove the old 612 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*), 613 assuming their contents is of no importance anymore. Old wtmp 614 databases can only be used by last(1) and ac(8) after they have 615 been converted to the new format using wtmpcvt(1). 616 61720100108: 618 Introduce the kernel thread "deadlock resolver" (which can be enabled 619 via the DEADLKRES option, see NOTES for more details) and the 620 sleepq_type() function for sleepqueues. 621 62220091202: 623 The rc.firewall and rc.firewall6 were unified, and 624 rc.firewall6 and rc.d/ip6fw were removed. 625 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc 626 variables are obsoleted. Instead, the following new rc 627 variables are added to rc.d/ipfw: 628 629 firewall_client_net_ipv6, firewall_simple_iif_ipv6, 630 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6, 631 firewall_simple_onet_ipv6, firewall_trusted_ipv6 632 633 The meanings correspond to the relevant IPv4 variables. 634 63520091125: 636 8.0-RELEASE. 637 63820091113: 639 The default terminal emulation for syscons(4) has been changed 640 from cons25 to xterm on all platforms except pc98. This means 641 that the /etc/ttys file needs to be updated to ensure correct 642 operation of applications on the console. 643 644 The terminal emulation style can be toggled per window by using 645 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration 646 options can be used to change the compile-time default back to 647 cons25. 648 649 To prevent graphical artifacts, make sure the TERM environment 650 variable is set to match the terminal emulation that is being 651 performed by syscons(4). 652 65320091109: 654 The layout of the structure ieee80211req_scan_result has changed. 655 Applications that require wireless scan results (e.g. ifconfig(8)) 656 from net80211 need to be recompiled. 657 658 Applications such as wpa_supplicant(8) may require a full world 659 build without using NO_CLEAN in order to get synchronized with the 660 new structure. 661 66220091025: 663 The iwn(4) driver has been updated to support the 5000 and 5150 series. 664 There's one kernel module for each firmware. Adding "device iwnfw" 665 to the kernel configuration file means including all three firmware 666 images inside the kernel. If you want to include just the one for 667 your wireless card, use the devices iwn4965fw, iwn5000fw or 668 iwn5150fw. 669 67020090926: 671 The rc.d/network_ipv6, IPv6 configuration script has been integrated 672 into rc.d/netif. The changes are the following: 673 674 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF 675 for IPv4. For aliases, $ifconfig_IF_aliasN should be used. 676 Note that both variables need the "inet6" keyword at the head. 677 678 Do not set $ipv6_network_interfaces manually if you do not 679 understand what you are doing. It is not needed in most cases. 680 681 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but 682 they are obsolete. 683 684 2. $ipv6_enable is obsolete. Use $ipv6_prefer and 685 "inet6 accept_rtadv" keyword in ifconfig(8) instead. 686 687 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and 688 all configured interfaces have "inet6 accept_rtadv" in the 689 $ifconfig_IF_ipv6. These are for backward compatibility. 690 691 3. A new variable $ipv6_prefer has been added. If NO, IPv6 692 functionality of interfaces with no corresponding 693 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag, 694 and the default address selection policy of ip6addrctl(8) 695 is the IPv4-preferred one (see rc.d/ip6addrctl for more details). 696 Note that if you want to configure IPv6 functionality on the 697 disabled interfaces after boot, first you need to clear the flag by 698 using ifconfig(8) like: 699 700 ifconfig em0 inet6 -ifdisabled 701 702 If YES, the default address selection policy is set as 703 IPv6-preferred. 704 705 The default value of $ipv6_prefer is NO. 706 707 4. If your system need to receive Router Advertisement messages, 708 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8) 709 scripts automatically invoke rtsol(8) when the interface becomes 710 UP. The Router Advertisement messages are used for SLAAC 711 (State-Less Address AutoConfiguration). 712 71320090922: 714 802.11s D3.03 support was committed. This is incompatible with the 715 previous code, which was based on D3.0. 716 71720090912: 718 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value 719 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to 720 control whether accepting Router Advertisement messages or not. 721 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and 722 a sysctl variable net.inet6.ip6.auto_linklocal is its default value. 723 The ifconfig(8) utility now supports these flags. 724 72520090910: 726 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for 727 mount(8) and -a option for df(1) to see them. 728 72920090825: 730 The old tunable hw.bus.devctl_disable has been superseded by 731 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be 732 replaced by hw.bus.devctl_queue=0. The default for this new tunable 733 is 1000. 734 73520090813: 736 Remove the option STOP_NMI. The default action is now to use NMI only 737 for KDB via the newly introduced function stop_cpus_hard() and 738 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64. 739 74020090803: 741 The stable/8 branch created in subversion. This corresponds to the 742 RELENG_8 branch in CVS. 743 74420090719: 745 Bump the shared library version numbers for all libraries that do not 746 use symbol versioning as part of the 8.0-RELEASE cycle. Bump 747 __FreeBSD_version to 800105. 748 74920090714: 750 Due to changes in the implementation of virtual network stack support, 751 all network-related kernel modules must be recompiled. As this change 752 breaks the ABI, bump __FreeBSD_version to 800104. 753 75420090713: 755 The TOE interface to the TCP syncache has been modified to remove 756 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. 757 The cxgb driver is the only TOE consumer affected by this change, and 758 needs to be recompiled along with the kernel. As this change breaks 759 the ABI, bump __FreeBSD_version to 800103. 760 76120090712: 762 Padding has been added to struct tcpcb, sackhint and tcpstat in 763 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst 764 maintaining the ABI. However, this change breaks the ABI, so bump 765 __FreeBSD_version to 800102. User space tools that rely on the size of 766 any of these structs (e.g. sockstat) need to be recompiled. 767 76820090630: 769 The NFS_LEGACYRPC option has been removed along with the old kernel 770 RPC implementation that this option selected. Kernel configurations 771 may need to be adjusted. 772 77320090629: 774 The network interface device nodes at /dev/net/<interface> have been 775 removed. All ioctl operations can be performed the normal way using 776 routing sockets. The kqueue functionality can generally be replaced 777 with routing sockets. 778 77920090628: 780 The documentation from the FreeBSD Documentation Project (Handbook, 781 FAQ, etc.) is now installed via packages by sysinstall(8) and under 782 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc. 783 78420090624: 785 The ABI of various structures related to the SYSV IPC API have been 786 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel 787 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to 788 800100. 789 79020090622: 791 Layout of struct vnet has changed as routing related variables were 792 moved to their own Vimage module. Modules need to be recompiled. Bump 793 __FreeBSD_version to 800099. 794 79520090619: 796 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024 797 respectively. As long as no more than 16 groups per process are used, 798 no changes should be visible. When more than 16 groups are used, old 799 binaries may fail if they call getgroups() or getgrouplist() with 800 statically sized storage. Recompiling will work around this, but 801 applications should be modified to use dynamically allocated storage 802 for group arrays as POSIX.1-2008 does not cap an implementation's 803 number of supported groups at NGROUPS_MAX+1 as previous versions did. 804 805 NFS and portalfs mounts may also be affected as the list of groups is 806 truncated to 16. Users of NFS who use more than 16 groups, should 807 take care that negative group permissions are not used on the exported 808 file systems as they will not be reliable unless a GSSAPI based 809 authentication method is used. 810 81120090616: 812 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This 813 option compiles in the support for adaptive spinning for lockmgrs 814 which want to enable it. The lockinit() function now accepts the flag 815 LK_ADAPTIVE in order to make the lock object subject to adaptive 816 spinning when both held in write and read mode. 817 81820090613: 819 The layout of the structure returned by IEEE80211_IOC_STA_INFO has 820 changed. User applications that use this ioctl need to be rebuilt. 821 82220090611: 823 The layout of struct thread has changed. Kernel and modules need to 824 be rebuilt. 825 82620090608: 827 The layout of structs ifnet, domain, protosw and vnet_net has changed. 828 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097. 829 83020090602: 831 window(1) has been removed from the base system. It can now be 832 installed from ports. The port is called misc/window. 833 83420090601: 835 The way we are storing and accessing `routing table' entries has 836 changed. Programs reading the FIB, like netstat, need to be 837 re-compiled. 838 83920090601: 840 A new netisr implementation has been added for FreeBSD 8. Network 841 file system modules, such as igmp, ipdivert, and others, should be 842 rebuilt. 843 Bump __FreeBSD_version to 800096. 844 84520090530: 846 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no 847 more valid. 848 84920090530: 850 Add VOP_ACCESSX(9). File system modules need to be rebuilt. 851 Bump __FreeBSD_version to 800094. 852 85320090529: 854 Add mnt_xflag field to 'struct mount'. File system modules need to be 855 rebuilt. 856 Bump __FreeBSD_version to 800093. 857 85820090528: 859 The compiling option ADAPTIVE_SX has been retired while it has been 860 introduced the option NO_ADAPTIVE_SX which handles the reversed logic. 861 The KPI for sx_init_flags() changes as accepting flags: 862 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has 863 been introduced in order to handle the reversed logic. 864 Bump __FreeBSD_version to 800092. 865 86620090527: 867 Add support for hierarchical jails. Remove global securelevel. 868 Bump __FreeBSD_version to 800091. 869 87020090523: 871 The layout of struct vnet_net has changed, therefore modules 872 need to be rebuilt. 873 Bump __FreeBSD_version to 800090. 874 87520090523: 876 The newly imported zic(8) produces a new format in the output. Please 877 run tzsetup(8) to install the newly created data to /etc/localtime. 878 87920090520: 880 The sysctl tree for the usb stack has renamed from hw.usb2.* to 881 hw.usb.* and is now consistent again with previous releases. 882 88320090520: 884 802.11 monitor mode support was revised and driver api's were changed. 885 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead 886 of DLT_IEEE802_11. No user-visible data structures were changed but 887 applications that use DLT_IEEE802_11 may require changes. 888 Bump __FreeBSD_version to 800088. 889 89020090430: 891 The layout of the following structs has changed: sysctl_oid, 892 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet, 893 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or 894 panics may be experienced. World rebuild is required for 895 correctly checking networking state from userland. 896 Bump __FreeBSD_version to 800085. 897 89820090429: 899 MLDv2 and Source-Specific Multicast (SSM) have been merged 900 to the IPv6 stack. VIMAGE hooks are in but not yet used. 901 The implementation of SSM within FreeBSD's IPv6 stack closely 902 follows the IPv4 implementation. 903 904 For kernel developers: 905 906 * The most important changes are that the ip6_output() and 907 ip6_input() paths no longer take the IN6_MULTI_LOCK, 908 and this lock has been downgraded to a non-recursive mutex. 909 910 * As with the changes to the IPv4 stack to support SSM, filtering 911 of inbound multicast traffic must now be performed by transport 912 protocols within the IPv6 stack. This does not apply to TCP and 913 SCTP, however, it does apply to UDP in IPv6 and raw IPv6. 914 915 * The KPIs used by IPv6 multicast are similar to those used by 916 the IPv4 stack, with the following differences: 917 * im6o_mc_filter() is analogous to imo_multicast_filter(). 918 * The legacy KAME entry points in6_joingroup and in6_leavegroup() 919 are shimmed to in6_mc_join() and in6_mc_leave() respectively. 920 * IN6_LOOKUP_MULTI() has been deprecated and removed. 921 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs 922 for MLDv1 have an additional 'timer' argument which is used to 923 jitter the initial membership report for the solicited-node 924 multicast membership on-link. 925 * This is not strictly needed for MLDv2, which already jitters 926 its report transmissions. However, the 'timer' argument is 927 preserved in case MLDv1 is active on the interface. 928 929 * The KAME linked-list based IPv6 membership implementation has 930 been refactored to use a vector similar to that used by the IPv4 931 stack. 932 Code which maintains a list of its own multicast memberships 933 internally, e.g. carp, has been updated to reflect the new 934 semantics. 935 936 * There is a known Lock Order Reversal (LOR) due to in6_setscope() 937 acquiring the IF_AFDATA_LOCK and being called within ip6_output(). 938 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an 939 implementation constraint which needs to be addressed in HEAD. 940 941 For application developers: 942 943 * The changes are broadly similar to those made for the IPv4 944 stack. 945 946 * The use of IPv4 and IPv6 multicast socket options on the same 947 socket, using mapped addresses, HAS NOT been tested or supported. 948 949 * There are a number of issues with the implementation of various 950 IPv6 multicast APIs which need to be resolved in the API surface 951 before the implementation is fully compatible with KAME userland 952 use, and these are mostly to do with interface index treatment. 953 954 * The literature available discusses the use of either the delta / ASM 955 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API 956 using setsourcefilter(3)/getsourcefilter(3). For more information 957 please refer to RFC 3768, 'Socket Interface Extensions for 958 Multicast Source Filters'. 959 960 * Applications which use the published RFC 3678 APIs should be fine. 961 962 For systems administrators: 963 964 * The mtest(8) utility has been refactored to support IPv6, in 965 addition to IPv4. Interface addresses are no longer accepted 966 as arguments, their names must be used instead. The utility 967 will map the interface name to its first IPv4 address as 968 returned by getifaddrs(3). 969 970 * The ifmcstat(8) utility has also been updated to print the MLDv2 971 endpoint state and source filter lists via sysctl(3). 972 973 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable 974 loopback of IPv6 multicast datagrams by default; it defaults to 1 975 to preserve the existing behaviour. Disabling multicast loopback is 976 recommended for optimal system performance. 977 978 * The IPv6 MROUTING code has been changed to examine this sysctl 979 instead of attempting to perform a group lookup before looping 980 back forwarded datagrams. 981 982 Bump __FreeBSD_version to 800084. 983 98420090422: 985 Implement low-level Bluetooth HCI API. 986 Bump __FreeBSD_version to 800083. 987 98820090419: 989 The layout of struct malloc_type, used by modules to register new 990 memory allocation types, has changed. Most modules will need to 991 be rebuilt or panics may be experienced. 992 Bump __FreeBSD_version to 800081. 993 99420090415: 995 Anticipate overflowing inp_flags - add inp_flags2. 996 This changes most offsets in inpcb, so checking v4 connection 997 state will require a world rebuild. 998 Bump __FreeBSD_version to 800080. 999 100020090415: 1001 Add an llentry to struct route and struct route_in6. Modules 1002 embedding a struct route will need to be recompiled. 1003 Bump __FreeBSD_version to 800079. 1004 100520090414: 1006 The size of rt_metrics_lite and by extension rtentry has changed. 1007 Networking administration apps will need to be recompiled. 1008 The route command now supports show as an alias for get, weighting 1009 of routes, sticky and nostick flags to alter the behavior of stateful 1010 load balancing. 1011 Bump __FreeBSD_version to 800078. 1012 101320090408: 1014 Do not use Giant for kbdmux(4) locking. This is wrong and 1015 apparently causing more problems than it solves. This will 1016 re-open the issue where interrupt handlers may race with 1017 kbdmux(4) in polling mode. Typical symptoms include (but 1018 not limited to) duplicated and/or missing characters when 1019 low level console functions (such as gets) are used while 1020 interrupts are enabled (for example geli password prompt, 1021 mountroot prompt etc.). Disabling kbdmux(4) may help. 1022 102320090407: 1024 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed; 1025 kernel modules referencing any of the above need to be recompiled. 1026 Bump __FreeBSD_version to 800075. 1027 102820090320: 1029 GEOM_PART has become the default partition slicer for storage devices, 1030 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It 1031 introduces some changes: 1032 1033 MSDOS/EBR: the devices created from MSDOS extended partition entries 1034 (EBR) can be named differently than with GEOM_MBR and are now symlinks 1035 to devices with offset-based names. fstabs may need to be modified. 1036 1037 BSD: the "geometry does not match label" warning is harmless in most 1038 cases but it points to problems in file system misalignment with 1039 disk geometry. The "c" partition is now implicit, covers the whole 1040 top-level drive and cannot be (mis)used by users. 1041 1042 General: Kernel dumps are now not allowed to be written to devices 1043 whose partition types indicate they are meant to be used for file 1044 systems (or, in case of MSDOS partitions, as something else than 1045 the "386BSD" type). 1046 1047 Most of these changes date approximately from 200812. 1048 104920090319: 1050 The uscanner(4) driver has been removed from the kernel. This follows 1051 Linux removing theirs in 2.6 and making libusb the default interface 1052 (supported by sane). 1053 105420090319: 1055 The multicast forwarding code has been cleaned up. netstat(1) 1056 only relies on KVM now for printing bandwidth upcall meters. 1057 The IPv4 and IPv6 modules are split into ip_mroute_mod and 1058 ip6_mroute_mod respectively. The config(5) options for statically 1059 compiling this code remain the same, i.e. 'options MROUTING'. 1060 106120090315: 1062 Support for the IFF_NEEDSGIANT network interface flag has been 1063 removed, which means that non-MPSAFE network device drivers are no 1064 longer supported. In particular, if_ar, if_sr, and network device 1065 drivers from the old (legacy) USB stack can no longer be built or 1066 used. 1067 106820090313: 1069 POSIX.1 Native Language Support (NLS) has been enabled in libc and 1070 a bunch of new language catalog files have also been added. 1071 This means that some common libc messages are now localized and 1072 they depend on the LC_MESSAGES environmental variable. 1073 107420090313: 1075 The k8temp(4) driver has been renamed to amdtemp(4) since 1076 support for Family 10 and Family 11 CPU families was added. 1077 107820090309: 1079 IGMPv3 and Source-Specific Multicast (SSM) have been merged 1080 to the IPv4 stack. VIMAGE hooks are in but not yet used. 1081 1082 For kernel developers, the most important changes are that the 1083 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(), 1084 and this lock has been downgraded to a non-recursive mutex. 1085 1086 Transport protocols (UDP, Raw IP) are now responsible for filtering 1087 inbound multicast traffic according to group membership and source 1088 filters. The imo_multicast_filter() KPI exists for this purpose. 1089 Transports which do not use multicast (SCTP, TCP) already reject 1090 multicast by default. Forwarding and receive performance may improve 1091 as a mutex acquisition is no longer needed in the ip_input() 1092 low-level input path. in_addmulti() and in_delmulti() are shimmed 1093 to new KPIs which exist to support SSM in-kernel. 1094 1095 For application developers, it is recommended that loopback of 1096 multicast datagrams be disabled for best performance, as this 1097 will still cause the lock to be taken for each looped-back 1098 datagram transmission. The net.inet.ip.mcast.loop sysctl may 1099 be tuned to 0 to disable loopback by default; it defaults to 1 1100 to preserve the existing behaviour. 1101 1102 For systems administrators, to obtain best performance with 1103 multicast reception and multiple groups, it is always recommended 1104 that a card with a suitably precise hash filter is used. Hash 1105 collisions will still result in the lock being taken within the 1106 transport protocol input path to check group membership. 1107 1108 If deploying FreeBSD in an environment with IGMP snooping switches, 1109 it is recommended that the net.inet.igmp.sendlocal sysctl remain 1110 enabled; this forces 224.0.0.0/24 group membership to be announced 1111 via IGMP. 1112 1113 The size of 'struct igmpstat' has changed; netstat needs to be 1114 recompiled to reflect this. 1115 Bump __FreeBSD_version to 800070. 1116 111720090309: 1118 libusb20.so.1 is now installed as libusb.so.1 and the ports system 1119 updated to use it. This requires a buildworld/installworld in order to 1120 update the library and dependencies (usbconfig, etc). Its advisable to 1121 rebuild all ports which uses libusb. More specific directions are given 1122 in the ports collection UPDATING file. Any /etc/libmap.conf entries for 1123 libusb are no longer required and can be removed. 1124 112520090302: 1126 A workaround is committed to allow the creation of System V shared 1127 memory segment of size > 2 GB on the 64-bit architectures. 1128 Due to a limitation of the existing ABI, the shm_segsz member 1129 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is 1130 wrong for large segments. Note that limits must be explicitly 1131 raised to allow such segments to be created. 1132 113320090301: 1134 The layout of struct ifnet has changed, requiring a rebuild of all 1135 network device driver modules. 1136 113720090227: 1138 The /dev handling for the new USB stack has changed, a 1139 buildworld/installworld is required for libusb20. 1140 114120090223: 1142 The new USB2 stack has now been permanently moved in and all kernel and 1143 module names reverted to their previous values (eg, usb, ehci, ohci, 1144 ums, ...). The old usb stack can be compiled in by prefixing the name 1145 with the letter 'o', the old usb modules have been removed. 1146 Updating entry 20090216 for xorg and 20090215 for libmap may still 1147 apply. 1148 114920090217: 1150 The rc.conf(5) option if_up_delay has been renamed to 1151 defaultroute_delay to better reflect its purpose. If you have 1152 customized this setting in /etc/rc.conf you need to update it to 1153 use the new name. 1154 115520090216: 1156 xorg 7.4 wants to configure its input devices via hald which does not 1157 yet work with USB2. If the keyboard/mouse does not work in xorg then 1158 add 1159 Option "AllowEmptyInput" "off" 1160 to your ServerLayout section. This will cause X to use the configured 1161 kbd and mouse sections from your xorg.conf. 1162 116320090215: 1164 The GENERIC kernels for all architectures now default to the new USB2 1165 stack. No kernel config options or code have been removed so if a 1166 problem arises please report it and optionally revert to the old USB 1167 stack. If you are loading USB kernel modules or have a custom kernel 1168 that includes GENERIC then ensure that usb names are also changed over, 1169 eg uftdi -> usb2_serial_ftdi. 1170 1171 Older programs linked against the ports libusb 0.1 need to be 1172 redirected to the new stack's libusb20. /etc/libmap.conf can 1173 be used for this: 1174 # Map old usb library to new one for usb2 stack 1175 libusb-0.1.so.8 libusb20.so.1 1176 117720090209: 1178 All USB ethernet devices now attach as interfaces under the name ueN 1179 (eg. ue0). This is to provide a predictable name as vendors often 1180 change usb chipsets in a product without notice. 1181 118220090203: 1183 The ichsmb(4) driver has been changed to require SMBus slave 1184 addresses be left-justified (xxxxxxx0b) rather than right-justified. 1185 All of the other SMBus controller drivers require left-justified 1186 slave addresses, so this change makes all the drivers provide the 1187 same interface. 1188 118920090201: 1190 INET6 statistics (struct ip6stat) was updated. 1191 netstat(1) needs to be recompiled. 1192 119320090119: 1194 NTFS has been removed from GENERIC kernel on amd64 to match 1195 GENERIC on i386. Should not cause any issues since mount_ntfs(8) 1196 will load ntfs.ko module automatically when NTFS support is 1197 actually needed, unless ntfs.ko is not installed or security 1198 level prohibits loading kernel modules. If either is the case, 1199 "options NTFS" has to be added into kernel config. 1200 120120090115: 1202 TCP Appropriate Byte Counting (RFC 3465) support added to kernel. 1203 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to 1204 800061. User space tools that rely on the size of struct tcpcb in 1205 tcp_var.h (e.g. sockstat) need to be recompiled. 1206 120720081225: 1208 ng_tty(4) module updated to match the new TTY subsystem. 1209 Due to API change, user-level applications must be updated. 1210 New API support added to mpd5 CVS and expected to be present 1211 in next mpd5.3 release. 1212 121320081219: 1214 With __FreeBSD_version 800060 the makefs tool is part of 1215 the base system (it was a port). 1216 121720081216: 1218 The afdata and ifnet locks have been changed from mutexes to 1219 rwlocks, network modules will need to be re-compiled. 1220 122120081214: 1222 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite. 1223 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated. 1224 The new code reduced struct rtentry{} by 16 bytes on 32-bit 1225 architecture and 40 bytes on 64-bit architecture. The userland 1226 applications "arp" and "ndp" have been updated accordingly. 1227 The output from "netstat -r" shows only routing entries and 1228 none of the L2 information. 1229 123020081130: 1231 __FreeBSD_version 800057 marks the switchover from the 1232 binary ath hal to source code. Users must add the line: 1233 1234 options AH_SUPPORT_AR5416 1235 1236 to their kernel config files when specifying: 1237 1238 device ath_hal 1239 1240 The ath_hal module no longer exists; the code is now compiled 1241 together with the driver in the ath module. It is now 1242 possible to tailor chip support (i.e. reduce the set of chips 1243 and thereby the code size); consult ath_hal(4) for details. 1244 124520081121: 1246 __FreeBSD_version 800054 adds memory barriers to 1247 <machine/atomic.h>, new interfaces to ifnet to facilitate 1248 multiple hardware transmit queues for cards that support 1249 them, and a lock-less ring-buffer implementation to 1250 enable drivers to more efficiently manage queueing of 1251 packets. 1252 125320081117: 1254 A new version of ZFS (version 13) has been merged to -HEAD. 1255 This version has zpool attribute "listsnapshots" off by 1256 default, which means "zfs list" does not show snapshots, 1257 and is the same as Solaris behavior. 1258 125920081028: 1260 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled. 1261 126220081009: 1263 The uhci, ohci, ehci and slhci USB Host controller drivers have 1264 been put into separate modules. If you load the usb module 1265 separately through loader.conf you will need to load the 1266 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0 1267 controller add the following to loader.conf: 1268 1269 uhci_load="YES" 1270 ehci_load="YES" 1271 127220081009: 1273 The ABI used by the PMC toolset has changed. Please keep 1274 userland (libpmc(3)) and the kernel module (hwpmc(4)) in 1275 sync. 1276 127720081009: 1278 atapci kernel module now includes only generic PCI ATA 1279 driver. AHCI driver moved to ataahci kernel module. 1280 All vendor-specific code moved into separate kernel modules: 1281 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek, 1282 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron, 1283 atamarvell, atamicron, atanational, atanetcell, atanvidia, 1284 atapromise, ataserverworks, atasiliconimage, atasis, atavia 1285 128620080820: 1287 The TTY subsystem of the kernel has been replaced by a new 1288 implementation, which provides better scalability and an 1289 improved driver model. Most common drivers have been migrated to 1290 the new TTY subsystem, while others have not. The following 1291 drivers have not yet been ported to the new TTY layer: 1292 1293 PCI/ISA: 1294 cy, digi, rc, rp, sio 1295 1296 USB: 1297 ubser, ucycom 1298 1299 Line disciplines: 1300 ng_h4, ng_tty, ppp, sl, snp 1301 1302 Adding these drivers to your kernel configuration file shall 1303 cause compilation to fail. 1304 130520080818: 1306 ntpd has been upgraded to 4.2.4p5. 1307 130820080801: 1309 OpenSSH has been upgraded to 5.1p1. 1310 1311 For many years, FreeBSD's version of OpenSSH preferred DSA 1312 over RSA for host and user authentication keys. With this 1313 upgrade, we've switched to the vendor's default of RSA over 1314 DSA. This may cause upgraded clients to warn about unknown 1315 host keys even for previously known hosts. Users should 1316 follow the usual procedure for verifying host keys before 1317 accepting the RSA key. 1318 1319 This can be circumvented by setting the "HostKeyAlgorithms" 1320 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh 1321 command line. 1322 1323 Please note that the sequence of keys offered for 1324 authentication has been changed as well. You may want to 1325 specify IdentityFile in a different order to revert this 1326 behavior. 1327 132820080713: 1329 The sio(4) driver has been removed from the i386 and amd64 1330 kernel configuration files. This means uart(4) is now the 1331 default serial port driver on those platforms as well. 1332 1333 To prevent collisions with the sio(4) driver, the uart(4) driver 1334 uses different names for its device nodes. This means the 1335 onboard serial port will now most likely be called "ttyu0" 1336 instead of "ttyd0". You may need to reconfigure applications to 1337 use the new device names. 1338 1339 When using the serial port as a boot console, be sure to update 1340 /boot/device.hints and /etc/ttys before booting the new kernel. 1341 If you forget to do so, you can still manually specify the hints 1342 at the loader prompt: 1343 1344 set hint.uart.0.at="isa" 1345 set hint.uart.0.port="0x3F8" 1346 set hint.uart.0.flags="0x10" 1347 set hint.uart.0.irq="4" 1348 boot -s 1349 135020080609: 1351 The gpt(8) utility has been removed. Use gpart(8) to partition 1352 disks instead. 1353 135420080603: 1355 The version that Linuxulator emulates was changed from 2.4.2 1356 to 2.6.16. If you experience any problems with Linux binaries 1357 please try to set sysctl compat.linux.osrelease to 2.4.2 and 1358 if it fixes the problem contact emulation mailing list. 1359 136020080525: 1361 ISDN4BSD (I4B) was removed from the src tree. You may need to 1362 update a your kernel configuration and remove relevant entries. 1363 136420080509: 1365 I have checked in code to support multiple routing tables. 1366 See the man pages setfib(1) and setfib(2). 1367 This is a hopefully backwards compatible version, 1368 but to make use of it you need to compile your kernel 1369 with options ROUTETABLES=2 (or more up to 16). 1370 137120080420: 1372 The 802.11 wireless support was redone to enable multi-bss 1373 operation on devices that are capable. The underlying device 1374 is no longer used directly but instead wlanX devices are 1375 cloned with ifconfig. This requires changes to rc.conf files. 1376 For example, change: 1377 ifconfig_ath0="WPA DHCP" 1378 to 1379 wlans_ath0=wlan0 1380 ifconfig_wlan0="WPA DHCP" 1381 see rc.conf(5) for more details. In addition, mergemaster of 1382 /etc/rc.d is highly recommended. Simultaneous update of userland 1383 and kernel wouldn't hurt either. 1384 1385 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta 1386 modules were merged into the base wlan module. All references 1387 to these modules (e.g. in kernel config files) must be removed. 1388 138920080408: 1390 psm(4) has gained write(2) support in native operation level. 1391 Arbitrary commands can be written to /dev/psm%d and status can 1392 be read back from it. Therefore, an application is responsible 1393 for status validation and error recovery. It is a no-op in 1394 other operation levels. 1395 139620080312: 1397 Support for KSE threading has been removed from the kernel. To 1398 run legacy applications linked against KSE libmap.conf may 1399 be used. The following libmap.conf may be used to ensure 1400 compatibility with any prior release: 1401 1402 libpthread.so.1 libthr.so.1 1403 libpthread.so.2 libthr.so.2 1404 libkse.so.3 libthr.so.3 1405 140620080301: 1407 The layout of struct vmspace has changed. This affects libkvm 1408 and any executables that link against libkvm and use the 1409 kvm_getprocs() function. In particular, but not exclusively, 1410 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1). 1411 The effects are minimal, but it's advisable to upgrade world 1412 nonetheless. 1413 141420080229: 1415 The latest em driver no longer has support in it for the 1416 82575 adapter, this is now moved to the igb driver. The 1417 split was done to make new features that are incompatible 1418 with older hardware easier to do. 1419 142020080220: 1421 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4), 1422 likewise the kernel option is now GEOM_LINUX_LVM. 1423 142420080211: 1425 The default NFS mount mode has changed from UDP to TCP for 1426 increased reliability. If you rely on (insecurely) NFS 1427 mounting across a firewall you may need to update your 1428 firewall rules. 1429 143020080208: 1431 Belatedly note the addition of m_collapse for compacting 1432 mbuf chains. 1433 143420080126: 1435 The fts(3) structures have been changed to use adequate 1436 integer types for their members and so to be able to cope 1437 with huge file trees. The old fts(3) ABI is preserved 1438 through symbol versioning in libc, so third-party binaries 1439 using fts(3) should still work, although they will not take 1440 advantage of the extended types. At the same time, some 1441 third-party software might fail to build after this change 1442 due to unportable assumptions made in its source code about 1443 fts(3) structure members. Such software should be fixed 1444 by its vendor or, in the worst case, in the ports tree. 1445 FreeBSD_version 800015 marks this change for the unlikely 1446 case that a portable fix is impossible. 1447 144820080123: 1449 To upgrade to -current after this date, you must be running 1450 FreeBSD not older than 6.0-RELEASE. Upgrading to -current 1451 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems. 1452 145320071128: 1454 The ADAPTIVE_GIANT kernel option has been retired because its 1455 functionality is the default now. 1456 145720071118: 1458 The AT keyboard emulation of sunkbd(4) has been turned on 1459 by default. In order to make the special symbols of the Sun 1460 keyboards driven by sunkbd(4) work under X these now have 1461 to be configured the same way as Sun USB keyboards driven 1462 by ukbd(4) (which also does AT keyboard emulation), f.e.: 1463 1464 Option "XkbLayout" "us" 1465 Option "XkbRules" "xorg" 1466 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us" 1467 146820071024: 1469 It has been decided that it is desirable to provide ABI 1470 backwards compatibility to the FreeBSD 4/5/6 versions of the 1471 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was 1472 broken with the introduction of PCI domain support (see the 1473 20070930 entry). Unfortunately, this required the ABI of 1474 PCIOCGETCONF to be broken again in order to be able to 1475 provide backwards compatibility to the old version of that 1476 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled 1477 again. As for prominent ports this affects neither pciutils 1478 nor xorg-server this time, the hal port needs to be rebuilt 1479 however. 1480 148120071020: 1482 The misnamed kthread_create() and friends have been renamed 1483 to kproc_create() etc. Many of the callers already 1484 used kproc_start().. 1485 I will return kthread_create() and friends in a while 1486 with implementations that actually create threads, not procs. 1487 Renaming corresponds with version 800002. 1488 148920071010: 1490 RELENG_7 branched. 1491 1492COMMON ITEMS: 1493 1494 General Notes 1495 ------------- 1496 Avoid using make -j when upgrading. While generally safe, there are 1497 sometimes problems using -j to upgrade. If your upgrade fails with 1498 -j, please try again without -j. From time to time in the past there 1499 have been problems using -j with buildworld and/or installworld. This 1500 is especially true when upgrading between "distant" versions (eg one 1501 that cross a major release boundary or several minor releases, or when 1502 several months have passed on the -current branch). 1503 1504 Sometimes, obscure build problems are the result of environment 1505 poisoning. This can happen because the make utility reads its 1506 environment when searching for values for global variables. To run 1507 your build attempts in an "environmental clean room", prefix all make 1508 commands with 'env -i '. See the env(1) manual page for more details. 1509 1510 When upgrading from one major version to another it is generally best 1511 to upgrade to the latest code in the currently installed branch first, 1512 then do an upgrade to the new branch. This is the best-tested upgrade 1513 path, and has the highest probability of being successful. Please try 1514 this approach before reporting problems with a major version upgrade. 1515 1516 ZFS notes 1517 --------- 1518 When upgrading the boot ZFS pool to a new version, always follow 1519 these two steps: 1520 1521 1.) recompile and reinstall the ZFS boot loader and boot block 1522 (this is part of "make buildworld" and "make installworld") 1523 1524 2.) update the ZFS boot block on your boot drive 1525 1526 The following example updates the ZFS boot block on the first 1527 partition (freebsd-boot) of a GPT partitioned drive ad0: 1528 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" 1529 1530 Non-boot pools do not need these updates. 1531 1532 To build a kernel 1533 ----------------- 1534 If you are updating from a prior version of FreeBSD (even one just 1535 a few days old), you should follow this procedure. It is the most 1536 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1537 1538 make kernel-toolchain 1539 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1540 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1541 1542 To test a kernel once 1543 --------------------- 1544 If you just want to boot a kernel once (because you are not sure 1545 if it works, or if you want to boot a known bad kernel to provide 1546 debugging information) run 1547 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1548 nextboot -k testkernel 1549 1550 To just build a kernel when you know that it won't mess you up 1551 -------------------------------------------------------------- 1552 This assumes you are already running a CURRENT system. Replace 1553 ${arch} with the architecture of your machine (e.g. "i386", 1554 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 1555 1556 cd src/sys/${arch}/conf 1557 config KERNEL_NAME_HERE 1558 cd ../compile/KERNEL_NAME_HERE 1559 make depend 1560 make 1561 make install 1562 1563 If this fails, go to the "To build a kernel" section. 1564 1565 To rebuild everything and install it on the current system. 1566 ----------------------------------------------------------- 1567 # Note: sometimes if you are running current you gotta do more than 1568 # is listed here if you are upgrading from a really old current. 1569 1570 <make sure you have good level 0 dumps> 1571 make buildworld 1572 make kernel KERNCONF=YOUR_KERNEL_HERE 1573 [1] 1574 <reboot in single user> [3] 1575 mergemaster -p [5] 1576 make installworld 1577 mergemaster -i [4] 1578 make delete-old [6] 1579 <reboot> 1580 1581 1582 To cross-install current onto a separate partition 1583 -------------------------------------------------- 1584 # In this approach we use a separate partition to hold 1585 # current's root, 'usr', and 'var' directories. A partition 1586 # holding "/", "/usr" and "/var" should be about 2GB in 1587 # size. 1588 1589 <make sure you have good level 0 dumps> 1590 <boot into -stable> 1591 make buildworld 1592 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1593 <maybe newfs current's root partition> 1594 <mount current's root partition on directory ${CURRENT_ROOT}> 1595 make installworld DESTDIR=${CURRENT_ROOT} 1596 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1597 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1598 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1599 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1600 <reboot into current> 1601 <do a "native" rebuild/install as described in the previous section> 1602 <maybe install compatibility libraries from ports/misc/compat*> 1603 <reboot> 1604 1605 1606 To upgrade in-place from stable to current 1607 ---------------------------------------------- 1608 <make sure you have good level 0 dumps> 1609 make buildworld [9] 1610 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1611 [1] 1612 <reboot in single user> [3] 1613 mergemaster -p [5] 1614 make installworld 1615 mergemaster -i [4] 1616 make delete-old [6] 1617 <reboot> 1618 1619 Make sure that you've read the UPDATING file to understand the 1620 tweaks to various things you need. At this point in the life 1621 cycle of current, things change often and you are on your own 1622 to cope. The defaults can also change, so please read ALL of 1623 the UPDATING entries. 1624 1625 Also, if you are tracking -current, you must be subscribed to 1626 freebsd-current@freebsd.org. Make sure that before you update 1627 your sources that you have read and understood all the recent 1628 messages there. If in doubt, please track -stable which has 1629 much fewer pitfalls. 1630 1631 [1] If you have third party modules, such as vmware, you 1632 should disable them at this point so they don't crash your 1633 system on reboot. 1634 1635 [3] From the bootblocks, boot -s, and then do 1636 fsck -p 1637 mount -u / 1638 mount -a 1639 cd src 1640 adjkerntz -i # if CMOS is wall time 1641 Also, when doing a major release upgrade, it is required that 1642 you boot into single user mode to do the installworld. 1643 1644 [4] Note: This step is non-optional. Failure to do this step 1645 can result in a significant reduction in the functionality of the 1646 system. Attempting to do it by hand is not recommended and those 1647 that pursue this avenue should read this file carefully, as well 1648 as the archives of freebsd-current and freebsd-hackers mailing lists 1649 for potential gotchas. The -U option is also useful to consider. 1650 See mergemaster(8) for more information. 1651 1652 [5] Usually this step is a noop. However, from time to time 1653 you may need to do this if you get unknown user in the following 1654 step. It never hurts to do it all the time. You may need to 1655 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1656 install) after the buildworld before this step if you last updated 1657 from [78]-stable or 9-stable before 20130430. 1658 1659 [6] This only deletes old files and directories. Old libraries 1660 can be deleted by "make delete-old-libs", but you have to make 1661 sure that no program is using those libraries anymore. 1662 1663 [8] In order to have a kernel that can run the 4.x binaries needed to 1664 do an installworld, you must include the COMPAT_FREEBSD4 option in 1665 your kernel. Failure to do so may leave you with a system that is 1666 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 1667 required to run the 5.x binaries on more recent kernels. And so on 1668 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 1669 1670 Make sure that you merge any new devices from GENERIC since the 1671 last time you updated your kernel config file. 1672 1673 [9] When checking out sources, you must include the -P flag to have 1674 cvs prune empty directories. 1675 1676 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1677 "?=" instead of the "=" assignment operator, so that buildworld can 1678 override the CPUTYPE if it needs to. 1679 1680 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1681 not on the command line, or in /etc/make.conf. buildworld will 1682 warn if it is improperly defined. 1683FORMAT: 1684 1685This file contains a list, in reverse chronological order, of major 1686breakages in tracking -current. It is not guaranteed to be a complete 1687list of such breakages, and only contains entries since October 10, 2007. 1688If you need to see UPDATING entries from before that date, you will need 1689to fetch an UPDATING file from an older FreeBSD release. 1690 1691Copyright information: 1692 1693Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1694 1695Redistribution, publication, translation and use, with or without 1696modification, in full or in part, in any form or format of this 1697document are permitted without further permission from the author. 1698 1699THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1700IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1701WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1702DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1703INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1704(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1705SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1706HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1707STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1708IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1709POSSIBILITY OF SUCH DAMAGE. 1710 1711Contact Warner Losh if you have any questions about your use of 1712this document. 1713 1714$FreeBSD: releng/9.3/UPDATING 273438 2014-10-21 23:50:46Z delphij $ 1715