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