UPDATING revision 277195
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 14NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping 15from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of 16stable/10, and then rebuild without this option. The bootstrap process from 17older version of current is a bit fragile. 18 1920150114: p4 FreeBSD-SA-15:01.openssl 20 Fix multiple vulnerabilities in OpenSSL. [SA-15:01] 21 2220141223: p3 FreeBSD-SA-14:31.ntp 23 FreeBSD-EN-14:13.freebsd-update 24 25 Fix multiple vulnerabilities in NTP suite. [SA-14:31] 26 Fix directory deletion issue in freebsd-update. [EN-14:13] 27 2820141217: p2 FreeBSD-SA-14:30.unbound 29 Fix unbound remote denial of service vulnerability. 30 3120141210: p1 FreeBSD-SA-14:27.stdio 32 FreeBSD-SA-14:28.file 33 34 Fix buffer overflow in stdio. [SA-14:27] 35 36 Fix multiple vulnerabilities in file(1) and libmagic(3). 37 [SA-14:28] 38 3920140904: 40 The ofwfb driver, used to provide a graphics console on PowerPC when 41 using vt(4), no longer allows mmap() of all of physical memory. This 42 will prevent Xorg on PowerPC with some ATI graphics cards from 43 initializing properly unless x11-servers/xorg-server is updated to 44 1.12.4_8 or newer. 45 4620140831: 47 The libatf-c and libatf-c++ major versions were downgraded to 0 and 48 1 respectively to match the upstream numbers. They were out of 49 sync because, when they were originally added to FreeBSD, the 50 upstream versions were not respected. These libraries are private 51 and not yet built by default, so renumbering them should be a 52 non-issue. However, unclean source trees will yield broken test 53 programs once the operator executes "make delete-old-libs" after a 54 "make installworld". 55 56 Additionally, the atf-sh binary was made private by moving it into 57 /usr/libexec/. Already-built shell test programs will keep the 58 path to the old binary so they will break after "make delete-old" 59 is run. 60 61 If you are using WITH_TESTS=yes (not the default), wipe the object 62 tree and rebuild from scratch to prevent spurious test failures. 63 This is only needed once: the misnumbered libraries and misplaced 64 binaries have been added to OptionalObsoleteFiles.inc so they will 65 be removed during a clean upgrade. 66 6720140814: 68 The ixgbe tunables now match their sysctl counterparts, for example: 69 hw.ixgbe.enable_aim => hw.ix.enable_aim 70 Anyone using ixgbe tunables should ensure they update /boot/loader.conf. 71 7220140801: 73 The NFSv4.1 server committed by r269398 changes the internal 74 function call interfaces used between the NFS and krpc modules. 75 As such, __FreeBSD_version was bumped. 76 7720140729: 78 The default unbound configuration has been modified to address 79 issues with reverse lookups on networks that use private 80 address ranges. If you use the local_unbound service, run 81 "service local_unbound setup" as root to regenerate your 82 configuration, then "service local_unbound reload" to load the 83 new configuration. 84 8520140717: 86 It is no longer necessary to include the dwarf version in your DEBUG 87 options in your kernel config file. The bug that required it to be 88 placed in the config file has bene fixed. DEBUG should now just 89 contain -g. The build system will automatically update things 90 to do the right thing. 91 9220140715: 93 Several ABI breaking changes were merged to CTL and new iSCSI code. 94 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and 95 iscsictl need to be rebuilt to work with a new kernel. 96 9720140708: 98 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 99 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 100 which differs from the behaviour controlled by this knob.) 101 10220140608: 103 On i386 and amd64 systems, the onifconsole flag is now set by default 104 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled 105 as a login TTY if it is set in the bootloader as an active kernel 106 console. No changes in behavior should result otherwise. To revert to 107 the previous behavior, set ttyu0 to "off" in /etc/ttys. 108 10920140512: 110 Clang and llvm have been upgraded to 3.4.1 release. 111 11220140321: 113 Clang and llvm have been upgraded to 3.4 release. 114 11520140306: 116 If a Makefile in a tests/ directory was auto-generating a Kyuafile 117 instead of providing an explicit one, this would prevent such 118 Makefile from providing its own Kyuafile in the future during 119 NO_CLEAN builds. This has been fixed in the Makefiles but manual 120 intervention is needed to clean an objdir if you use NO_CLEAN: 121 # find /usr/obj -name Kyuafile | xargs rm -f 122 12320140303: 124 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 125 capability mode support. Please note that enabling the feature in 126 kernel is still highly recommended. 127 12820140227: 129 OpenSSH is now built with sandbox support, and will use sandbox as 130 the default privilege separation method. This requires Capsicum 131 capability mode support in kernel. 132 13320140216: 134 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has 135 been deprecated and will not be part of FreeBSD 11.0 and later 136 releases. If you use this driver, please consider switching to 137 the nfe(4) driver instead. 138 13920140120: 140 10.0-RELEASE. 141 14220131216: 143 The behavior of gss_pseudo_random() for the krb5 mechanism 144 has changed, for applications requesting a longer random string 145 than produced by the underlying enctype's pseudo-random() function. 146 In particular, the random string produced from a session key of 147 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 148 be different at the 17th octet and later, after this change. 149 The counter used in the PRF+ construction is now encoded as a 150 big-endian integer in accordance with RFC 4402. 151 __FreeBSD_version is bumped to 1000701. 152 15320131108: 154 The WITHOUT_ATF build knob has been removed and its functionality 155 has been subsumed into the more generic WITHOUT_TESTS. If you were 156 using the former to disable the build of the ATF libraries, you 157 should change your settings to use the latter. 158 15920131031: 160 The default version of mtree is nmtree which is obtained from 161 NetBSD. The output is generally the same, but may vary 162 slightly. If you found you need identical output adding 163 "-F freebsd9" to the command line should do the trick. For the 164 time being, the old mtree is available as fmtree. 165 16620131014: 167 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 168 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 169 1.1.4_8 and verify bsdyml not linked in, before running "make 170 delete-old-libs": 171 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 172 or 173 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 174 17520131010: 176 The rc.d/jail script has been updated to support jail(8) 177 configuration file. The "jail_<jname>_*" rc.conf(5) variables 178 for per-jail configuration are automatically converted to 179 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 180 This is transparently backward compatible. See below about some 181 incompatibilities and rc.conf(5) manual page for more details. 182 183 These variables are now deprecated in favor of jail(8) configuration 184 file. One can use "rc.d/jail config <jname>" command to generate 185 a jail(8) configuration file in /var/run/jail.<jname>.conf without 186 running the jail(8) utility. The default pathname of the 187 configuration file is /etc/jail.conf and can be specified by 188 using $jail_conf or $jail_<jname>_conf variables. 189 190 Please note that jail_devfs_ruleset accepts an integer at 191 this moment. Please consider to rewrite the ruleset name 192 with an integer. 193 19420130930: 195 BIND has been removed from the base system. If all you need 196 is a local resolver, simply enable and start the local_unbound 197 service instead. Otherwise, several versions of BIND are 198 available in the ports tree. The dns/bind99 port is one example. 199 200 With this change, nslookup(1) and dig(1) are no longer in the base 201 system. Users should instead use host(1) and drill(1) which are 202 in the base system. Alternatively, nslookup and dig can 203 be obtained by installing the dns/bind-tools port. 204 20520130916: 206 With the addition of unbound(8), a new unbound user is now 207 required during installworld. "mergemaster -p" can be used to 208 add the user prior to installworld, as documented in the handbook. 209 21020130911: 211 OpenSSH is now built with DNSSEC support, and will by default 212 silently trust signed SSHFP records. This can be controlled with 213 the VerifyHostKeyDNS client configuration setting. DNSSEC support 214 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 215 21620130906: 217 The GNU Compiler Collection and C++ standard library (libstdc++) 218 are no longer built by default on platforms where clang is the system 219 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 220 options in src.conf. 221 22220130905: 223 The PROCDESC kernel option is now part of the GENERIC kernel 224 configuration and is required for the rwhod(8) to work. 225 If you are using custom kernel configuration, you should include 226 'options PROCDESC'. 227 22820130905: 229 The API and ABI related to the Capsicum framework was modified 230 in backward incompatible way. The userland libraries and programs 231 have to be recompiled to work with the new kernel. This includes the 232 following libraries and programs, but the whole buildworld is 233 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 234 kdump, procstat, rwho, rwhod, uniq. 235 23620130903: 237 AES-NI intrinsic support has been added to gcc. The AES-NI module 238 has been updated to use this support. A new gcc is required to build 239 the aesni module on both i386 and amd64. 240 24120130821: 242 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 243 Thus "device padlock_rng" and "device rdrand_rng" should be 244 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 245 24620130813: 247 WITH_ICONV has been split into two feature sets. WITH_ICONV now 248 enables just the iconv* functionality and is now on by default. 249 WITH_LIBICONV_COMPAT enables the libiconv api and link time 250 compatability. Set WITHOUT_ICONV to build the old way. 251 If you have been using WITH_ICONV before, you will very likely 252 need to turn on WITH_LIBICONV_COMPAT. 253 25420130806: 255 INVARIANTS option now enables DEBUG for code with OpenSolaris and 256 Illumos origin, including ZFS. If you have INVARIANTS in your 257 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 258 explicitly. 259 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 260 locks if WITNESS option was set. Because that generated a lot of 261 witness(9) reports and all of them were believed to be false 262 positives, this is no longer done. New option OPENSOLARIS_WITNESS 263 can be used to achieve the previous behavior. 264 26520130806: 266 Timer values in IPv6 data structures now use time_uptime instead 267 of time_second. Although this is not a user-visible functional 268 change, userland utilities which directly use them---ndp(8), 269 rtadvd(8), and rtsold(8) in the base system---need to be updated 270 to r253970 or later. 271 27220130802: 273 find -delete can now delete the pathnames given as arguments, 274 instead of only files found below them or if the pathname did 275 not contain any slashes. Formerly, the following error message 276 would result: 277 278 find: -delete: <path>: relative path potentially not safe 279 280 Deleting the pathnames given as arguments can be prevented 281 without error messages using -mindepth 1 or by changing 282 directory and passing "." as argument to find. This works in the 283 old as well as the new version of find. 284 28520130726: 286 Behavior of devfs rules path matching has been changed. 287 Pattern is now always matched against fully qualified devfs 288 path and slash characters must be explicitly matched by 289 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 290 subdirectories must be reviewed. 291 29220130716: 293 The default ARM ABI has changed to the ARM EABI. The old ABI is 294 incompatible with the ARM EABI and all programs and modules will 295 need to be rebuilt to work with a new kernel. 296 297 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 298 299 NOTE: Support for the old ABI will be removed in the future and 300 users are advised to upgrade. 301 30220130709: 303 pkg_install has been disconnected from the build if you really need it 304 you should add WITH_PKGTOOLS in your src.conf(5). 305 30620130709: 307 Most of network statistics structures were changed to be able 308 keep 64-bits counters. Thus all tools, that work with networking 309 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 310 31120130629: 312 Fix targets that run multiple make's to use && rather than ; 313 so that subsequent steps depend on success of previous. 314 315 NOTE: if building 'universe' with -j* on stable/8 or stable/9 316 it would be better to start the build using bmake, to avoid 317 overloading the machine. 318 31920130618: 320 Fix a bug that allowed a tracing process (e.g. gdb) to write 321 to a memory-mapped file in the traced process's address space 322 even if neither the traced process nor the tracing process had 323 write access to that file. 324 32520130615: 326 CVS has been removed from the base system. An exact copy 327 of the code is available from the devel/cvs port. 328 32920130613: 330 Some people report the following error after the switch to bmake: 331 332 make: illegal option -- J 333 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 334 ... 335 *** [buildworld] Error code 2 336 337 this likely due to an old instance of make in 338 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 339 which src/Makefile will use that blindly, if it exists, so if 340 you see the above error: 341 342 rm -rf `make -V MAKEPATH` 343 344 should resolve it. 345 34620130516: 347 Use bmake by default. 348 Whereas before one could choose to build with bmake via 349 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 350 make. The goal is to remove these knobs for 10-RELEASE. 351 352 It is worth noting that bmake (like gmake) treats the command 353 line as the unit of failure, rather than statements within the 354 command line. Thus '(cd some/where && dosomething)' is safer 355 than 'cd some/where; dosomething'. The '()' allows consistent 356 behavior in parallel build. 357 35820130429: 359 Fix a bug that allows NFS clients to issue READDIR on files. 360 36120130426: 362 The WITHOUT_IDEA option has been removed because 363 the IDEA patent expired. 364 36520130426: 366 The sysctl which controls TRIM support under ZFS has been renamed 367 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 368 enabled by default. 369 37020130425: 371 The mergemaster command now uses the default MAKEOBJDIRPREFIX 372 rather than creating it's own in the temporary directory in 373 order allow access to bootstrapped versions of tools such as 374 install and mtree. When upgrading from version of FreeBSD where 375 the install command does not support -l, you will need to 376 install a new mergemaster command if mergemaster -p is required. 377 This can be accomplished with the command (cd src/usr.sbin/mergemaster 378 && make install). 379 38020130404: 381 Legacy ATA stack, disabled and replaced by new CAM-based one since 382 FreeBSD 9.0, completely removed from the sources. Kernel modules 383 atadisk and atapi*, user-level tools atacontrol and burncd are 384 removed. Kernel option `options ATA_CAM` is now permanently enabled 385 and removed. 386 38720130319: 388 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 389 and socketpair(2). Software, in particular Kerberos, may 390 automatically detect and use these during building. The resulting 391 binaries will not work on older kernels. 392 39320130308: 394 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 395 information, see the respective 20130304 entry). 396 39720130304: 398 Recent commits to callout(9) changed the size of struct callout, 399 so the KBI is probably heavily disturbed. Also, some functions 400 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 401 by macros. Every kernel module using it won't load, so rebuild 402 is requested. 403 404 The ctl device has been re-enabled in GENERIC for i386 and amd64, 405 but does not initialize by default (because of the new CTL_DISABLE 406 option) to save memory. To re-enable it, remove the CTL_DISABLE 407 option from the kernel config file or set kern.cam.ctl.disable=0 408 in /boot/loader.conf. 409 41020130301: 411 The ctl device has been disabled in GENERIC for i386 and amd64. 412 This was done due to the extra memory being allocated at system 413 initialisation time by the ctl driver which was only used if 414 a CAM target device was created. This makes a FreeBSD system 415 unusable on 128MB or less of RAM. 416 41720130208: 418 A new compression method (lz4) has been merged to -HEAD. Please 419 refer to zpool-features(7) for more information. 420 421 Please refer to the "ZFS notes" section of this file for information 422 on upgrading boot ZFS pools. 423 42420130129: 425 A BSD-licensed patch(1) variant has been added and is installed 426 as bsdpatch, being the GNU version the default patch. 427 To inverse the logic and use the BSD-licensed one as default, 428 while having the GNU version installed as gnupatch, rebuild 429 and install world with the WITH_BSD_PATCH knob set. 430 43120130121: 432 Due to the use of the new -l option to install(1) during build 433 and install, you must take care not to directly set the INSTALL 434 make variable in your /etc/make.conf, /etc/src.conf, or on the 435 command line. If you wish to use the -C flag for all installs 436 you may be able to add INSTALL+=-C to /etc/make.conf or 437 /etc/src.conf. 438 43920130118: 440 The install(1) option -M has changed meaning and now takes an 441 argument that is a file or path to append logs to. In the 442 unlikely event that -M was the last option on the command line 443 and the command line contained at least two files and a target 444 directory the first file will have logs appended to it. The -M 445 option served little practical purpose in the last decade so its 446 use is expected to be extremely rare. 447 44820121223: 449 After switching to Clang as the default compiler some users of ZFS 450 on i386 systems started to experience stack overflow kernel panics. 451 Please consider using 'options KSTACK_PAGES=4' in such configurations. 452 45320121222: 454 GEOM_LABEL now mangles label names read from file system metadata. 455 Mangling affect labels containing spaces, non-printable characters, 456 '%' or '"'. Device names in /etc/fstab and other places may need to 457 be updated. 458 45920121217: 460 By default, only the 10 most recent kernel dumps will be saved. To 461 restore the previous behaviour (no limit on the number of kernel dumps 462 stored in the dump directory) add the following line to /etc/rc.conf: 463 464 savecore_flags="" 465 46620121201: 467 With the addition of auditdistd(8), a new auditdistd user is now 468 required during installworld. "mergemaster -p" can be used to 469 add the user prior to installworld, as documented in the handbook. 470 47120121117: 472 The sin6_scope_id member variable in struct sockaddr_in6 is now 473 filled by the kernel before passing the structure to the userland via 474 sysctl or routing socket. This means the KAME-specific embedded scope 475 id in sin6_addr.s6_addr[2] is always cleared in userland application. 476 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 477 __FreeBSD_version is bumped to 1000025. 478 47920121105: 480 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 481 This means that the world and kernel will be compiled with clang 482 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 483 and /usr/bin/cpp. To disable this behavior and revert to building 484 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 485 of current may need to bootstrap WITHOUT_CLANG first if the clang 486 build fails (its compatibility window doesn't extend to the 9 stable 487 branch point). 488 48920121102: 490 The IPFIREWALL_FORWARD kernel option has been removed. Its 491 functionality now turned on by default. 492 49320121023: 494 The ZERO_COPY_SOCKET kernel option has been removed and 495 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 496 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 497 mechanism which is not safe and may result in kernel crashes. 498 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 499 driver supports disposeable external page sized mbuf storage. 500 Proper replacements for both zero-copy mechanisms are under 501 consideration and will eventually lead to complete removal 502 of the two kernel options. 503 50420121023: 505 The IPv4 network stack has been converted to network byte 506 order. The following modules need to be recompiled together 507 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 508 pf(4), ipfw(4), ng_ipfw(4), stf(4). 509 51020121022: 511 Support for non-MPSAFE filesystems was removed from VFS. The 512 VFS_VERSION was bumped, all filesystem modules shall be 513 recompiled. 514 51520121018: 516 All the non-MPSAFE filesystems have been disconnected from 517 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 518 portalfs, smbfs, xfs. 519 52020121016: 521 The interface cloning API and ABI has changed. The following 522 modules need to be recompiled together with kernel: 523 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 524 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 525 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 526 52720121015: 528 The sdhci driver was split in two parts: sdhci (generic SD Host 529 Controller logic) and sdhci_pci (actual hardware driver). 530 No kernel config modifications are required, but if you 531 load sdhc as a module you must switch to sdhci_pci instead. 532 53320121014: 534 Import the FUSE kernel and userland support into base system. 535 53620121013: 537 The GNU sort(1) program has been removed since the BSD-licensed 538 sort(1) has been the default for quite some time and no serious 539 problems have been reported. The corresponding WITH_GNU_SORT 540 knob has also gone. 541 54220121006: 543 The pfil(9) API/ABI for AF_INET family has been changed. Packet 544 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 545 with new kernel. 546 54720121001: 548 The net80211(4) ABI has been changed to allow for improved driver 549 PS-POLL and power-save support. All wireless drivers need to be 550 recompiled to work with the new kernel. 551 55220120913: 553 The random(4) support for the VIA hardware random number 554 generator (`PADLOCK') is no longer enabled unconditionally. 555 Add the padlock_rng device in the custom kernel config if 556 needed. The GENERIC kernels on i386 and amd64 do include the 557 device, so the change only affects the custom kernel 558 configurations. 559 56020120908: 561 The pf(4) packet filter ABI has been changed. pfctl(8) and 562 snmp_pf module need to be recompiled to work with new kernel. 563 56420120828: 565 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 566 to -HEAD. Pools that have empty_bpobj in active state can not be 567 imported read-write with ZFS implementations that do not support 568 this feature. For more information read the zpool-features(5) 569 manual page. 570 57120120727: 572 The sparc64 ZFS loader has been changed to no longer try to auto- 573 detect ZFS providers based on diskN aliases but now requires these 574 to be explicitly listed in the OFW boot-device environment variable. 575 57620120712: 577 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 578 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 579 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 580 58120120712: 582 The following sysctls and tunables have been renamed for consistency 583 with other variables: 584 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 585 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 586 58720120628: 588 The sort utility has been replaced with BSD sort. For now, GNU sort 589 is also available as "gnusort" or the default can be set back to 590 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 591 installed as "bsdsort". 592 59320120611: 594 A new version of ZFS (pool version 5000) has been merged to -HEAD. 595 Starting with this version the old system of ZFS pool versioning 596 is superseded by "feature flags". This concept enables forward 597 compatibility against certain future changes in functionality of ZFS 598 pools. The first read-only compatible "feature flag" for ZFS pools 599 is named "com.delphix:async_destroy". For more information 600 read the new zpool-features(5) manual page. 601 Please refer to the "ZFS notes" section of this file for information 602 on upgrading boot ZFS pools. 603 60420120417: 605 The malloc(3) implementation embedded in libc now uses sources imported 606 as contrib/jemalloc. The most disruptive API change is to 607 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 608 delete it prior to installworld, and optionally re-create it using the 609 new format after rebooting. See malloc.conf(5) for details 610 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 611 NAMESPACE section). 612 61320120328: 614 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 615 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 616 now spelled mips. This is to aid compatibility with third-party 617 software that expects this naming scheme in uname(3). Little-endian 618 settings are unchanged. If you are updating a big-endian mips64 machine 619 from before this change, you may need to set MACHINE_ARCH=mips64 in 620 your environment before the new build system will recognize your machine. 621 62220120306: 623 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 624 platforms. 625 62620120229: 627 Now unix domain sockets behave "as expected" on nullfs(5). Previously 628 nullfs(5) did not pass through all behaviours to the underlying layer, 629 as a result if we bound to a socket on the lower layer we could connect 630 only to the lower path; if we bound to the upper layer we could connect 631 only to the upper path. The new behavior is one can connect to both the 632 lower and the upper paths regardless what layer path one binds to. 633 63420120211: 635 The getifaddrs upgrade path broken with 20111215 has been restored. 636 If you have upgraded in between 20111215 and 20120209 you need to 637 recompile libc again with your kernel. You still need to recompile 638 world to be able to configure CARP but this restriction already 639 comes from 20111215. 640 64120120114: 642 The set_rcvar() function has been removed from /etc/rc.subr. All 643 base and ports rc.d scripts have been updated, so if you have a 644 port installed with a script in /usr/local/etc/rc.d you can either 645 hand-edit the rcvar= line, or reinstall the port. 646 647 An easy way to handle the mass-update of /etc/rc.d: 648 rm /etc/rc.d/* && mergemaster -i 649 65020120109: 651 panic(9) now stops other CPUs in the SMP systems, disables interrupts 652 on the current CPU and prevents other threads from running. 653 This behavior can be reverted using the kern.stop_scheduler_on_panic 654 tunable/sysctl. 655 The new behavior can be incompatible with kern.sync_on_panic. 656 65720111215: 658 The carp(4) facility has been changed significantly. Configuration 659 of the CARP protocol via ifconfig(8) has changed, as well as format 660 of CARP events submitted to devd(8) has changed. See manual pages 661 for more information. The arpbalance feature of carp(4) is currently 662 not supported anymore. 663 664 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 665 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 666 need to be recompiled. 667 66820111122: 669 The acpi_wmi(4) status device /dev/wmistat has been renamed to 670 /dev/wmistat0. 671 67220111108: 673 The option VFS_ALLOW_NONMPSAFE option has been added in order to 674 explicitely support non-MPSAFE filesystems. 675 It is on by default for all supported platform at this present 676 time. 677 67820111101: 679 The broken amd(4) driver has been replaced with esp(4) in the amd64, 680 i386 and pc98 GENERIC kernel configuration files. 681 68220110930: 683 sysinstall has been removed 684 68520110923: 686 The stable/9 branch created in subversion. This corresponds to the 687 RELENG_9 branch in CVS. 688 68920110913: 690 This commit modifies vfs_register() so that it uses a hash 691 calculation to set vfc_typenum, which is enabled by default. 692 The first time a system is booted after this change, the 693 vfc_typenum values will change for all file systems. The 694 main effect of this is a change to the NFS server file handles 695 for file systems that use vfc_typenum in their fsid, such as ZFS. 696 It will, however, prevent vfc_typenum from changing when file 697 systems are loaded in a different order for subsequent reboots. 698 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf 699 until you are ready to remount all NFS clients after a reboot. 700 70120110828: 702 Bump the shared library version numbers for libraries that 703 do not use symbol versioning, have changed the ABI compared 704 to stable/8 and which shared library version was not bumped. 705 Done as part of 9.0-RELEASE cycle. 706 70720110815: 708 During the merge of Capsicum features, the fget(9) KPI was modified. 709 This may require the rebuilding of out-of-tree device drivers -- 710 issues have been reported specifically with the nVidia device driver. 711 __FreeBSD_version is bumped to 900041. 712 713 Also, there is a period between 20110811 and 20110814 where the 714 special devices /dev/{stdin,stdout,stderr} did not work correctly. 715 Building world from a kernel during that window may not work. 716 71720110628: 718 The packet filter (pf) code has been updated to OpenBSD 4.5. 719 You need to update userland tools to be in sync with kernel. 720 This update breaks backward compatibility with earlier pfsync(4) 721 versions. Care must be taken when updating redundant firewall setups. 722 72320110608: 724 The following sysctls and tunables are retired on x86 platforms: 725 machdep.hlt_cpus 726 machdep.hlt_logical_cpus 727 The following sysctl is retired: 728 machdep.hyperthreading_allowed 729 The sysctls were supposed to provide a way to dynamically offline and 730 online selected CPUs on x86 platforms, but the implementation has not 731 been reliable especially with SCHED_ULE scheduler. 732 machdep.hyperthreading_allowed tunable is still available to ignore 733 hyperthreading CPUs at OS level. 734 Individual CPUs can be disabled using hint.lapic.X.disabled tunable, 735 where X is an APIC ID of a CPU. Be advised, though, that disabling 736 CPUs in non-uniform fashion will result in non-uniform topology and 737 may lead to sub-optimal system performance with SCHED_ULE, which is 738 a default scheduler. 739 74020110607: 741 cpumask_t type is retired and cpuset_t is used in order to describe 742 a mask of CPUs. 743 74420110531: 745 Changes to ifconfig(8) for dynamic address family detection mandate 746 that you are running a kernel of 20110525 or later. Make sure to 747 follow the update procedure to boot a new kernel before installing 748 world. 749 75020110513: 751 Support for sun4v architecture is officially dropped 752 75320110503: 754 Several KPI breaking changes have been committed to the mii(4) layer, 755 the PHY drivers and consequently some Ethernet drivers using mii(4). 756 This means that miibus.ko and the modules of the affected Ethernet 757 drivers need to be recompiled. 758 759 Note to kernel developers: Given that the OUI bit reversion problem 760 was fixed as part of these changes all mii(4) commits related to OUIs, 761 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific 762 handling, no longer can be merged verbatim to stable/8 and previous 763 branches. 764 76520110430: 766 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci' 767 into their kernel configurations along with 'device pci'. 768 76920110427: 770 The default NFS client is now the new NFS client, so fstype "newnfs" 771 is now "nfs" and the regular/old NFS client is now fstype "oldnfs". 772 Although mounts via fstype "nfs" will usually work without userland 773 changes, it is recommended that the mount(8) and mount_nfs(8) 774 commands be rebuilt from sources and that a link to mount_nfs called 775 mount_oldnfs be created. The new client is compiled into the 776 kernel with "options NFSCL" and this is needed for diskless root 777 file systems. The GENERIC kernel configs have been changed to use 778 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER. 779 To use the regular/old client, you can "mount -t oldnfs ...". For 780 a diskless root file system, you must also include a line like: 781 782 vfs.root.mountfrom="oldnfs:" 783 784 in the boot/loader.conf on the root fs on the NFS server to make 785 a diskless root fs use the old client. 786 78720110424: 788 The GENERIC kernels for all architectures now default to the new 789 CAM-based ATA stack. It means that all legacy ATA drivers were 790 removed and replaced by respective CAM drivers. If you are using 791 ATA device names in /etc/fstab or other places, make sure to update 792 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY, 793 where 'Y's are the sequential numbers starting from zero for each type 794 in order of detection, unless configured otherwise with tunables, 795 see cam(4)). There will be symbolic links created in /dev/ to map 796 old adX devices to the respective adaY. They should provide basic 797 compatibility for file systems mounting in most cases, but they do 798 not support old user-level APIs and do not have respective providers 799 in GEOM. Consider using updated management tools with new device names. 800 801 It is possible to load devices ahci, ata, siis and mvs as modules, 802 but option ATA_CAM should remain in kernel configuration to make ata 803 module work as CAM driver supporting legacy ATA controllers. Device ata 804 still can be used in modular fashion (atacore + ...). Modules atadisk 805 and atapi* are not used and won't affect operation in ATA_CAM mode. 806 Note that to use CAM-based ATA kernel should include CAM devices 807 scbus, pass, da (or explicitly ada), cd and optionally others. All of 808 them are parts of the cam module. 809 810 ataraid(4) functionality is now supported by the RAID GEOM class. 811 To use it you can load geom_raid kernel module and use graid(8) tool 812 for management. Instead of /dev/arX device names, use /dev/raid/rX. 813 814 No kernel config options or code have been removed, so if a problem 815 arises, please report it and optionally revert to the old ATA stack. 816 In order to do it you can remove from the kernel config: 817 options ATA_CAM 818 device ahci 819 device mvs 820 device siis 821 , and instead add back: 822 device atadisk # ATA disk drives 823 device ataraid # ATA RAID drives 824 device atapicd # ATAPI CDROM drives 825 device atapifd # ATAPI floppy drives 826 device atapist # ATAPI tape drives 827 82820110423: 829 The default NFS server has been changed to the new server, which 830 was referred to as the experimental server. If you need to switch 831 back to the old NFS server, you must now put the "-o" option on 832 both the mountd and nfsd commands. This can be done using the 833 mountd_flags and nfs_server_flags rc.conf variables until an 834 update to the rc scripts is committed, which is coming soon. 835 83620110418: 837 The GNU Objective-C runtime library (libobjc), and other Objective-C 838 related components have been removed from the base system. If you 839 require an Objective-C library, please use one of the available ports. 840 84120110331: 842 ath(4) has been split into bus- and device- modules. if_ath contains 843 the HAL, the TX rate control and the network device code. if_ath_pci 844 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb 845 contains the AHB glue. Users need to load both if_ath_pci and if_ath 846 in order to use ath on everything else. 847 848 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only 849 need to load if_ath and if_ath_pci for ath(4) operation. 850 85120110314: 852 As part of the replacement of sysinstall, the process of building 853 release media has changed significantly. For details, please re-read 854 release(7), which has been updated to reflect the new build process. 855 85620110218: 857 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This 858 is the last available version under GPLv2. It brings a number of new 859 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE 860 4.1 and SSE 4.2), better support for powerpc64, a number of new 861 directives, and lots of other small improvements. See the ChangeLog 862 file in contrib/binutils for the full details. 863 86420110218: 865 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868 866 compliant, and will now use half of hash for authentication. 867 This will break interoperability with all stacks (including all 868 actual FreeBSD versions) who implement 869 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for 870 authentication). 871 The only workaround with such peers is to use another HMAC 872 algorithm for IPsec ("phase 2") authentication. 873 87420110207: 875 Remove the uio_yield prototype and symbol. This function has 876 been misnamed since it was introduced and should not be 877 globally exposed with this name. The equivalent functionality 878 is now available using kern_yield(curthread->td_user_pri). 879 The function remains undocumented. 880 88120110112: 882 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers, 883 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking 884 for scalar sysctls is defined but disabled. Code that needs 885 UQUAD to pass the type checking that must compile on older 886 systems where the define is not present can check against 887 __FreeBSD_version >= 900030. 888 889 The system dialog(1) has been replaced with a new version previously 890 in ports as devel/cdialog. dialog(1) is mostly command-line compatible 891 with the previous version, but the libdialog associated with it has 892 a largely incompatible API. As such, the original version of libdialog 893 will be kept temporarily as libodialog, until its base system consumers 894 are replaced or updated. Bump __FreeBSD_version to 900030. 895 89620110103: 897 If you are trying to run make universe on a -stable system, and you get 898 the following warning: 899 "Makefile", line 356: "Target architecture for i386/conf/GENERIC 900 unknown. config(8) likely too old." 901 or something similar to it, then you must upgrade your -stable system 902 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in 903 stable/8) or build the config from the latest stable/8 branch and 904 install it on your system. 905 906 Prior to this date, building a current universe on 8-stable system from 907 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing 908 error in the first kernel build phase. A new config on those old 909 systems will fix that problem for older versions of -current. 910 91120101228: 912 The TCP stack has been modified to allow Khelp modules to interact with 913 it via helper hook points and store per-connection data in the TCP 914 control block. Bump __FreeBSD_version to 900029. User space tools that 915 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to 916 be recompiled. 917 91820101114: 919 Generic IEEE 802.3 annex 31B full duplex flow control support has been 920 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along 921 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted 922 to take advantage of it instead of using custom implementations. This 923 means that these drivers now no longer unconditionally advertise 924 support for flow control but only do so if flow control is a selected 925 media option. This was implemented in the generic support that way in 926 order to allow flow control to be switched on and off via ifconfig(8) 927 with the PHY specific default to typically off in order to protect 928 from unwanted effects. Consequently, if you used flow control with 929 one of the above mentioned drivers you now need to explicitly enable 930 it, for example via: 931 ifconfig bge0 media auto mediaopt flowcontrol 932 933 Along with the above mentioned changes generic support for setting 934 1000baseT master mode also has been added and brgphy(4), ciphy(4), 935 e1000phy(4) as well as ip1000phy(4) have been converted to take 936 advantage of it. This means that these drivers now no longer take the 937 link0 parameter for selecting master mode but the master media option 938 has to be used instead, for example like in the following: 939 ifconfig bge0 media 1000baseT mediaopt full-duplex,master 940 941 Selection of master mode now is also available with all other PHY 942 drivers supporting 1000baseT. 943 94420101111: 945 The TCP stack has received a significant update to add support for 946 modularised congestion control and generally improve the clarity of 947 congestion control decisions. Bump __FreeBSD_version to 900025. User 948 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g. 949 sockstat) need to be recompiled. 950 95120101002: 952 The man(1) utility has been replaced by a new version that no longer 953 uses /etc/manpath.config. Please consult man.conf(5) for how to 954 migrate local entries to the new format. 955 95620100928: 957 The copyright strings printed by login(1) and sshd(8) at the time of a 958 new connection have been removed to follow other operating systems and 959 upstream sshd. 960 96120100915: 962 A workaround for a fixed ld bug has been removed in kernel code, 963 so make sure that your system ld is built from sources after 964 revision 210245 from 2010-07-19 (r211583 if building head kernel 965 on stable/8, r211584 for stable/7; both from 2010-08-21). 966 A symptom of incorrect ld version is different addresses for 967 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules. 968 96920100913: 970 The $ipv6_prefer variable in rc.conf(5) has been split into 971 $ip6addrctl_policy and $ipv6_activate_all_interfaces. 972 973 The $ip6addrctl_policy is a variable to choose a pre-defined 974 address selection policy set by ip6addrctl(8). A value 975 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The 976 default is "AUTO". 977 978 The $ipv6_activate_all_interfaces specifies whether IFDISABLED 979 flag (see an entry of 20090926) is set on an interface with no 980 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for 981 security reason. If you want IPv6 link-local address on all 982 interfaces by default, set this to "YES". 983 984 The old ipv6_prefer="YES" is equivalent to 985 ipv6_activate_all_interfaces="YES" and 986 ip6addrctl_policy="ipv6_prefer". 987 98820100913: 989 DTrace has grown support for userland tracing. Due to this, DTrace is 990 now i386 and amd64 only. 991 dtruss(1) is now installed by default on those systems and a new 992 kernel module is needed for userland tracing: fasttrap. 993 No changes to your kernel config file are necessary to enable 994 userland tracing, but you might consider adding 'STRIP=' and 995 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want 996 to have informative userland stack traces in DTrace (ustack). 997 99820100725: 999 The acpi_aiboost(4) driver has been removed in favor of the new 1000 aibs(4) driver. You should update your kernel configuration file. 1001 100220100722: 1003 BSD grep has been imported to the base system and it is built by 1004 default. It is completely BSD licensed, highly GNU-compatible, uses 1005 less memory than its GNU counterpart and has a small codebase. 1006 However, it is slower than its GNU counterpart, which is mostly 1007 noticeable for larger searches, for smaller ones it is measurable 1008 but not significant. The reason is complex, the most important factor 1009 is that we lack a modern and efficient regex library and GNU 1010 overcomes this by optimizing the searches internally. Future work 1011 on improving the regex performance is planned, for the meantime, 1012 users that need better performance, can build GNU grep instead by 1013 setting the WITH_GNU_GREP knob. 1014 101520100713: 1016 Due to the import of powerpc64 support, all existing powerpc kernel 1017 configuration files must be updated with a machine directive like this: 1018 machine powerpc powerpc 1019 1020 In addition, an updated config(8) is required to build powerpc kernels 1021 after this change. 1022 102320100713: 1024 A new version of ZFS (version 15) has been merged to -HEAD. 1025 This version uses a python library for the following subcommands: 1026 zfs allow, zfs unallow, zfs groupspace, zfs userspace. 1027 For full functionality of these commands the following port must 1028 be installed: sysutils/py-zfs 1029 103020100429: 1031 'vm_page's are now hashed by physical address to an array of mutexes. 1032 Currently this is only used to serialize access to hold_count. Over 1033 time the page queue mutex will be peeled away. This changes the size 1034 of pmap on every architecture. And requires all callers of vm_page_hold 1035 and vm_page_unhold to be updated. 1036 103720100402: 1038 WITH_CTF can now be specified in src.conf (not recommended, there 1039 are some problems with static executables), make.conf (would also 1040 affect ports which do not use GNU make and do not override the 1041 compile targets) or in the kernel config (via "makeoptions 1042 WITH_CTF=yes"). 1043 When WITH_CTF was specified there before this was silently ignored, 1044 so make sure that WITH_CTF is not used in places which could lead 1045 to unwanted behavior. 1046 104720100311: 1048 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32 1049 to allow 32-bit compatibility on non-x86 platforms. All kernel 1050 configurations on amd64 and ia64 platforms using these options must 1051 be modified accordingly. 1052 105320100113: 1054 The utmp user accounting database has been replaced with utmpx, 1055 the user accounting interface standardized by POSIX. 1056 Unfortunately the semantics of utmp and utmpx don't match, 1057 making it practically impossible to support both interfaces. 1058 The user accounting database is used by tools like finger(1), 1059 last(1), talk(1), w(1) and ac(8). 1060 1061 All applications in the base system use utmpx. This means only 1062 local binaries (e.g. from the ports tree) may still use these 1063 utmp database files. These applications must be rebuilt to make 1064 use of utmpx. 1065 1066 After the system has been upgraded, it is safe to remove the old 1067 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*), 1068 assuming their contents is of no importance anymore. Old wtmp 1069 databases can only be used by last(1) and ac(8) after they have 1070 been converted to the new format using wtmpcvt(1). 1071 107220100108: 1073 Introduce the kernel thread "deadlock resolver" (which can be enabled 1074 via the DEADLKRES option, see NOTES for more details) and the 1075 sleepq_type() function for sleepqueues. 1076 107720091202: 1078 The rc.firewall and rc.firewall6 were unified, and 1079 rc.firewall6 and rc.d/ip6fw were removed. 1080 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc 1081 variables are obsoleted. Instead, the following new rc 1082 variables are added to rc.d/ipfw: 1083 1084 firewall_client_net_ipv6, firewall_simple_iif_ipv6, 1085 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6, 1086 firewall_simple_onet_ipv6, firewall_trusted_ipv6 1087 1088 The meanings correspond to the relevant IPv4 variables. 1089 109020091125: 1091 8.0-RELEASE. 1092 109320091113: 1094 The default terminal emulation for syscons(4) has been changed 1095 from cons25 to xterm on all platforms except pc98. This means 1096 that the /etc/ttys file needs to be updated to ensure correct 1097 operation of applications on the console. 1098 1099 The terminal emulation style can be toggled per window by using 1100 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration 1101 options can be used to change the compile-time default back to 1102 cons25. 1103 1104 To prevent graphical artifacts, make sure the TERM environment 1105 variable is set to match the terminal emulation that is being 1106 performed by syscons(4). 1107 110820091109: 1109 The layout of the structure ieee80211req_scan_result has changed. 1110 Applications that require wireless scan results (e.g. ifconfig(8)) 1111 from net80211 need to be recompiled. 1112 1113 Applications such as wpa_supplicant(8) may require a full world 1114 build without using NO_CLEAN in order to get synchronized with the 1115 new structure. 1116 111720091025: 1118 The iwn(4) driver has been updated to support the 5000 and 5150 series. 1119 There's one kernel module for each firmware. Adding "device iwnfw" 1120 to the kernel configuration file means including all three firmware 1121 images inside the kernel. If you want to include just the one for 1122 your wireless card, use the devices iwn4965fw, iwn5000fw or 1123 iwn5150fw. 1124 112520090926: 1126 The rc.d/network_ipv6, IPv6 configuration script has been integrated 1127 into rc.d/netif. The changes are the following: 1128 1129 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF 1130 for IPv4. For aliases, $ifconfig_IF_aliasN should be used. 1131 Note that both variables need the "inet6" keyword at the head. 1132 1133 Do not set $ipv6_network_interfaces manually if you do not 1134 understand what you are doing. It is not needed in most cases. 1135 1136 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but 1137 they are obsolete. 1138 1139 2. $ipv6_enable is obsolete. Use $ipv6_prefer and 1140 "inet6 accept_rtadv" keyword in ifconfig(8) instead. 1141 1142 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and 1143 all configured interfaces have "inet6 accept_rtadv" in the 1144 $ifconfig_IF_ipv6. These are for backward compatibility. 1145 1146 3. A new variable $ipv6_prefer has been added. If NO, IPv6 1147 functionality of interfaces with no corresponding 1148 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag, 1149 and the default address selection policy of ip6addrctl(8) 1150 is the IPv4-preferred one (see rc.d/ip6addrctl for more details). 1151 Note that if you want to configure IPv6 functionality on the 1152 disabled interfaces after boot, first you need to clear the flag by 1153 using ifconfig(8) like: 1154 1155 ifconfig em0 inet6 -ifdisabled 1156 1157 If YES, the default address selection policy is set as 1158 IPv6-preferred. 1159 1160 The default value of $ipv6_prefer is NO. 1161 1162 4. If your system need to receive Router Advertisement messages, 1163 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8) 1164 scripts automatically invoke rtsol(8) when the interface becomes 1165 UP. The Router Advertisement messages are used for SLAAC 1166 (State-Less Address AutoConfiguration). 1167 116820090922: 1169 802.11s D3.03 support was committed. This is incompatible with the 1170 previous code, which was based on D3.0. 1171 117220090912: 1173 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value 1174 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to 1175 control whether accepting Router Advertisement messages or not. 1176 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and 1177 a sysctl variable net.inet6.ip6.auto_linklocal is its default value. 1178 The ifconfig(8) utility now supports these flags. 1179 118020090910: 1181 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for 1182 mount(8) and -a option for df(1) to see them. 1183 118420090825: 1185 The old tunable hw.bus.devctl_disable has been superseded by 1186 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be 1187 replaced by hw.bus.devctl_queue=0. The default for this new tunable 1188 is 1000. 1189 119020090813: 1191 Remove the option STOP_NMI. The default action is now to use NMI only 1192 for KDB via the newly introduced function stop_cpus_hard() and 1193 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64. 1194 119520090803: 1196 The stable/8 branch created in subversion. This corresponds to the 1197 RELENG_8 branch in CVS. 1198 119920090719: 1200 Bump the shared library version numbers for all libraries that do not 1201 use symbol versioning as part of the 8.0-RELEASE cycle. Bump 1202 __FreeBSD_version to 800105. 1203 120420090714: 1205 Due to changes in the implementation of virtual network stack support, 1206 all network-related kernel modules must be recompiled. As this change 1207 breaks the ABI, bump __FreeBSD_version to 800104. 1208 120920090713: 1210 The TOE interface to the TCP syncache has been modified to remove 1211 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack. 1212 The cxgb driver is the only TOE consumer affected by this change, and 1213 needs to be recompiled along with the kernel. As this change breaks 1214 the ABI, bump __FreeBSD_version to 800103. 1215 121620090712: 1217 Padding has been added to struct tcpcb, sackhint and tcpstat in 1218 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst 1219 maintaining the ABI. However, this change breaks the ABI, so bump 1220 __FreeBSD_version to 800102. User space tools that rely on the size of 1221 any of these structs (e.g. sockstat) need to be recompiled. 1222 122320090630: 1224 The NFS_LEGACYRPC option has been removed along with the old kernel 1225 RPC implementation that this option selected. Kernel configurations 1226 may need to be adjusted. 1227 122820090629: 1229 The network interface device nodes at /dev/net/<interface> have been 1230 removed. All ioctl operations can be performed the normal way using 1231 routing sockets. The kqueue functionality can generally be replaced 1232 with routing sockets. 1233 123420090628: 1235 The documentation from the FreeBSD Documentation Project (Handbook, 1236 FAQ, etc.) is now installed via packages by sysinstall(8) and under 1237 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc. 1238 123920090624: 1240 The ABI of various structures related to the SYSV IPC API have been 1241 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel 1242 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to 1243 800100. 1244 124520090622: 1246 Layout of struct vnet has changed as routing related variables were 1247 moved to their own Vimage module. Modules need to be recompiled. Bump 1248 __FreeBSD_version to 800099. 1249 125020090619: 1251 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024 1252 respectively. As long as no more than 16 groups per process are used, 1253 no changes should be visible. When more than 16 groups are used, old 1254 binaries may fail if they call getgroups() or getgrouplist() with 1255 statically sized storage. Recompiling will work around this, but 1256 applications should be modified to use dynamically allocated storage 1257 for group arrays as POSIX.1-2008 does not cap an implementation's 1258 number of supported groups at NGROUPS_MAX+1 as previous versions did. 1259 1260 NFS and portalfs mounts may also be affected as the list of groups is 1261 truncated to 16. Users of NFS who use more than 16 groups, should 1262 take care that negative group permissions are not used on the exported 1263 file systems as they will not be reliable unless a GSSAPI based 1264 authentication method is used. 1265 126620090616: 1267 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This 1268 option compiles in the support for adaptive spinning for lockmgrs 1269 which want to enable it. The lockinit() function now accepts the flag 1270 LK_ADAPTIVE in order to make the lock object subject to adaptive 1271 spinning when both held in write and read mode. 1272 127320090613: 1274 The layout of the structure returned by IEEE80211_IOC_STA_INFO has 1275 changed. User applications that use this ioctl need to be rebuilt. 1276 127720090611: 1278 The layout of struct thread has changed. Kernel and modules need to 1279 be rebuilt. 1280 128120090608: 1282 The layout of structs ifnet, domain, protosw and vnet_net has changed. 1283 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097. 1284 128520090602: 1286 window(1) has been removed from the base system. It can now be 1287 installed from ports. The port is called misc/window. 1288 128920090601: 1290 The way we are storing and accessing `routing table' entries has 1291 changed. Programs reading the FIB, like netstat, need to be 1292 re-compiled. 1293 129420090601: 1295 A new netisr implementation has been added for FreeBSD 8. Network 1296 file system modules, such as igmp, ipdivert, and others, should be 1297 rebuilt. 1298 Bump __FreeBSD_version to 800096. 1299 130020090530: 1301 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no 1302 more valid. 1303 130420090530: 1305 Add VOP_ACCESSX(9). File system modules need to be rebuilt. 1306 Bump __FreeBSD_version to 800094. 1307 130820090529: 1309 Add mnt_xflag field to 'struct mount'. File system modules need to be 1310 rebuilt. 1311 Bump __FreeBSD_version to 800093. 1312 131320090528: 1314 The compiling option ADAPTIVE_SX has been retired while it has been 1315 introduced the option NO_ADAPTIVE_SX which handles the reversed logic. 1316 The KPI for sx_init_flags() changes as accepting flags: 1317 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has 1318 been introduced in order to handle the reversed logic. 1319 Bump __FreeBSD_version to 800092. 1320 132120090527: 1322 Add support for hierarchical jails. Remove global securelevel. 1323 Bump __FreeBSD_version to 800091. 1324 132520090523: 1326 The layout of struct vnet_net has changed, therefore modules 1327 need to be rebuilt. 1328 Bump __FreeBSD_version to 800090. 1329 133020090523: 1331 The newly imported zic(8) produces a new format in the output. Please 1332 run tzsetup(8) to install the newly created data to /etc/localtime. 1333 133420090520: 1335 The sysctl tree for the usb stack has renamed from hw.usb2.* to 1336 hw.usb.* and is now consistent again with previous releases. 1337 133820090520: 1339 802.11 monitor mode support was revised and driver api's were changed. 1340 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead 1341 of DLT_IEEE802_11. No user-visible data structures were changed but 1342 applications that use DLT_IEEE802_11 may require changes. 1343 Bump __FreeBSD_version to 800088. 1344 134520090430: 1346 The layout of the following structs has changed: sysctl_oid, 1347 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet, 1348 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or 1349 panics may be experienced. World rebuild is required for 1350 correctly checking networking state from userland. 1351 Bump __FreeBSD_version to 800085. 1352 135320090429: 1354 MLDv2 and Source-Specific Multicast (SSM) have been merged 1355 to the IPv6 stack. VIMAGE hooks are in but not yet used. 1356 The implementation of SSM within FreeBSD's IPv6 stack closely 1357 follows the IPv4 implementation. 1358 1359 For kernel developers: 1360 1361 * The most important changes are that the ip6_output() and 1362 ip6_input() paths no longer take the IN6_MULTI_LOCK, 1363 and this lock has been downgraded to a non-recursive mutex. 1364 1365 * As with the changes to the IPv4 stack to support SSM, filtering 1366 of inbound multicast traffic must now be performed by transport 1367 protocols within the IPv6 stack. This does not apply to TCP and 1368 SCTP, however, it does apply to UDP in IPv6 and raw IPv6. 1369 1370 * The KPIs used by IPv6 multicast are similar to those used by 1371 the IPv4 stack, with the following differences: 1372 * im6o_mc_filter() is analogous to imo_multicast_filter(). 1373 * The legacy KAME entry points in6_joingroup and in6_leavegroup() 1374 are shimmed to in6_mc_join() and in6_mc_leave() respectively. 1375 * IN6_LOOKUP_MULTI() has been deprecated and removed. 1376 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs 1377 for MLDv1 have an additional 'timer' argument which is used to 1378 jitter the initial membership report for the solicited-node 1379 multicast membership on-link. 1380 * This is not strictly needed for MLDv2, which already jitters 1381 its report transmissions. However, the 'timer' argument is 1382 preserved in case MLDv1 is active on the interface. 1383 1384 * The KAME linked-list based IPv6 membership implementation has 1385 been refactored to use a vector similar to that used by the IPv4 1386 stack. 1387 Code which maintains a list of its own multicast memberships 1388 internally, e.g. carp, has been updated to reflect the new 1389 semantics. 1390 1391 * There is a known Lock Order Reversal (LOR) due to in6_setscope() 1392 acquiring the IF_AFDATA_LOCK and being called within ip6_output(). 1393 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an 1394 implementation constraint which needs to be addressed in HEAD. 1395 1396 For application developers: 1397 1398 * The changes are broadly similar to those made for the IPv4 1399 stack. 1400 1401 * The use of IPv4 and IPv6 multicast socket options on the same 1402 socket, using mapped addresses, HAS NOT been tested or supported. 1403 1404 * There are a number of issues with the implementation of various 1405 IPv6 multicast APIs which need to be resolved in the API surface 1406 before the implementation is fully compatible with KAME userland 1407 use, and these are mostly to do with interface index treatment. 1408 1409 * The literature available discusses the use of either the delta / ASM 1410 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API 1411 using setsourcefilter(3)/getsourcefilter(3). For more information 1412 please refer to RFC 3768, 'Socket Interface Extensions for 1413 Multicast Source Filters'. 1414 1415 * Applications which use the published RFC 3678 APIs should be fine. 1416 1417 For systems administrators: 1418 1419 * The mtest(8) utility has been refactored to support IPv6, in 1420 addition to IPv4. Interface addresses are no longer accepted 1421 as arguments, their names must be used instead. The utility 1422 will map the interface name to its first IPv4 address as 1423 returned by getifaddrs(3). 1424 1425 * The ifmcstat(8) utility has also been updated to print the MLDv2 1426 endpoint state and source filter lists via sysctl(3). 1427 1428 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable 1429 loopback of IPv6 multicast datagrams by default; it defaults to 1 1430 to preserve the existing behaviour. Disabling multicast loopback is 1431 recommended for optimal system performance. 1432 1433 * The IPv6 MROUTING code has been changed to examine this sysctl 1434 instead of attempting to perform a group lookup before looping 1435 back forwarded datagrams. 1436 1437 Bump __FreeBSD_version to 800084. 1438 143920090422: 1440 Implement low-level Bluetooth HCI API. 1441 Bump __FreeBSD_version to 800083. 1442 144320090419: 1444 The layout of struct malloc_type, used by modules to register new 1445 memory allocation types, has changed. Most modules will need to 1446 be rebuilt or panics may be experienced. 1447 Bump __FreeBSD_version to 800081. 1448 144920090415: 1450 Anticipate overflowing inp_flags - add inp_flags2. 1451 This changes most offsets in inpcb, so checking v4 connection 1452 state will require a world rebuild. 1453 Bump __FreeBSD_version to 800080. 1454 145520090415: 1456 Add an llentry to struct route and struct route_in6. Modules 1457 embedding a struct route will need to be recompiled. 1458 Bump __FreeBSD_version to 800079. 1459 146020090414: 1461 The size of rt_metrics_lite and by extension rtentry has changed. 1462 Networking administration apps will need to be recompiled. 1463 The route command now supports show as an alias for get, weighting 1464 of routes, sticky and nostick flags to alter the behavior of stateful 1465 load balancing. 1466 Bump __FreeBSD_version to 800078. 1467 146820090408: 1469 Do not use Giant for kbdmux(4) locking. This is wrong and 1470 apparently causing more problems than it solves. This will 1471 re-open the issue where interrupt handlers may race with 1472 kbdmux(4) in polling mode. Typical symptoms include (but 1473 not limited to) duplicated and/or missing characters when 1474 low level console functions (such as gets) are used while 1475 interrupts are enabled (for example geli password prompt, 1476 mountroot prompt etc.). Disabling kbdmux(4) may help. 1477 147820090407: 1479 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed; 1480 kernel modules referencing any of the above need to be recompiled. 1481 Bump __FreeBSD_version to 800075. 1482 148320090320: 1484 GEOM_PART has become the default partition slicer for storage devices, 1485 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It 1486 introduces some changes: 1487 1488 MSDOS/EBR: the devices created from MSDOS extended partition entries 1489 (EBR) can be named differently than with GEOM_MBR and are now symlinks 1490 to devices with offset-based names. fstabs may need to be modified. 1491 1492 BSD: the "geometry does not match label" warning is harmless in most 1493 cases but it points to problems in file system misalignment with 1494 disk geometry. The "c" partition is now implicit, covers the whole 1495 top-level drive and cannot be (mis)used by users. 1496 1497 General: Kernel dumps are now not allowed to be written to devices 1498 whose partition types indicate they are meant to be used for file 1499 systems (or, in case of MSDOS partitions, as something else than 1500 the "386BSD" type). 1501 1502 Most of these changes date approximately from 200812. 1503 150420090319: 1505 The uscanner(4) driver has been removed from the kernel. This follows 1506 Linux removing theirs in 2.6 and making libusb the default interface 1507 (supported by sane). 1508 150920090319: 1510 The multicast forwarding code has been cleaned up. netstat(1) 1511 only relies on KVM now for printing bandwidth upcall meters. 1512 The IPv4 and IPv6 modules are split into ip_mroute_mod and 1513 ip6_mroute_mod respectively. The config(5) options for statically 1514 compiling this code remain the same, i.e. 'options MROUTING'. 1515 151620090315: 1517 Support for the IFF_NEEDSGIANT network interface flag has been 1518 removed, which means that non-MPSAFE network device drivers are no 1519 longer supported. In particular, if_ar, if_sr, and network device 1520 drivers from the old (legacy) USB stack can no longer be built or 1521 used. 1522 152320090313: 1524 POSIX.1 Native Language Support (NLS) has been enabled in libc and 1525 a bunch of new language catalog files have also been added. 1526 This means that some common libc messages are now localized and 1527 they depend on the LC_MESSAGES environmental variable. 1528 152920090313: 1530 The k8temp(4) driver has been renamed to amdtemp(4) since 1531 support for Family 10 and Family 11 CPU families was added. 1532 153320090309: 1534 IGMPv3 and Source-Specific Multicast (SSM) have been merged 1535 to the IPv4 stack. VIMAGE hooks are in but not yet used. 1536 1537 For kernel developers, the most important changes are that the 1538 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(), 1539 and this lock has been downgraded to a non-recursive mutex. 1540 1541 Transport protocols (UDP, Raw IP) are now responsible for filtering 1542 inbound multicast traffic according to group membership and source 1543 filters. The imo_multicast_filter() KPI exists for this purpose. 1544 Transports which do not use multicast (SCTP, TCP) already reject 1545 multicast by default. Forwarding and receive performance may improve 1546 as a mutex acquisition is no longer needed in the ip_input() 1547 low-level input path. in_addmulti() and in_delmulti() are shimmed 1548 to new KPIs which exist to support SSM in-kernel. 1549 1550 For application developers, it is recommended that loopback of 1551 multicast datagrams be disabled for best performance, as this 1552 will still cause the lock to be taken for each looped-back 1553 datagram transmission. The net.inet.ip.mcast.loop sysctl may 1554 be tuned to 0 to disable loopback by default; it defaults to 1 1555 to preserve the existing behaviour. 1556 1557 For systems administrators, to obtain best performance with 1558 multicast reception and multiple groups, it is always recommended 1559 that a card with a suitably precise hash filter is used. Hash 1560 collisions will still result in the lock being taken within the 1561 transport protocol input path to check group membership. 1562 1563 If deploying FreeBSD in an environment with IGMP snooping switches, 1564 it is recommended that the net.inet.igmp.sendlocal sysctl remain 1565 enabled; this forces 224.0.0.0/24 group membership to be announced 1566 via IGMP. 1567 1568 The size of 'struct igmpstat' has changed; netstat needs to be 1569 recompiled to reflect this. 1570 Bump __FreeBSD_version to 800070. 1571 157220090309: 1573 libusb20.so.1 is now installed as libusb.so.1 and the ports system 1574 updated to use it. This requires a buildworld/installworld in order to 1575 update the library and dependencies (usbconfig, etc). Its advisable to 1576 rebuild all ports which uses libusb. More specific directions are given 1577 in the ports collection UPDATING file. Any /etc/libmap.conf entries for 1578 libusb are no longer required and can be removed. 1579 158020090302: 1581 A workaround is committed to allow the creation of System V shared 1582 memory segment of size > 2 GB on the 64-bit architectures. 1583 Due to a limitation of the existing ABI, the shm_segsz member 1584 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is 1585 wrong for large segments. Note that limits must be explicitly 1586 raised to allow such segments to be created. 1587 158820090301: 1589 The layout of struct ifnet has changed, requiring a rebuild of all 1590 network device driver modules. 1591 159220090227: 1593 The /dev handling for the new USB stack has changed, a 1594 buildworld/installworld is required for libusb20. 1595 159620090223: 1597 The new USB2 stack has now been permanently moved in and all kernel and 1598 module names reverted to their previous values (eg, usb, ehci, ohci, 1599 ums, ...). The old usb stack can be compiled in by prefixing the name 1600 with the letter 'o', the old usb modules have been removed. 1601 Updating entry 20090216 for xorg and 20090215 for libmap may still 1602 apply. 1603 160420090217: 1605 The rc.conf(5) option if_up_delay has been renamed to 1606 defaultroute_delay to better reflect its purpose. If you have 1607 customized this setting in /etc/rc.conf you need to update it to 1608 use the new name. 1609 161020090216: 1611 xorg 7.4 wants to configure its input devices via hald which does not 1612 yet work with USB2. If the keyboard/mouse does not work in xorg then 1613 add 1614 Option "AllowEmptyInput" "off" 1615 to your ServerLayout section. This will cause X to use the configured 1616 kbd and mouse sections from your xorg.conf. 1617 161820090215: 1619 The GENERIC kernels for all architectures now default to the new USB2 1620 stack. No kernel config options or code have been removed so if a 1621 problem arises please report it and optionally revert to the old USB 1622 stack. If you are loading USB kernel modules or have a custom kernel 1623 that includes GENERIC then ensure that usb names are also changed over, 1624 eg uftdi -> usb2_serial_ftdi. 1625 1626 Older programs linked against the ports libusb 0.1 need to be 1627 redirected to the new stack's libusb20. /etc/libmap.conf can 1628 be used for this: 1629 # Map old usb library to new one for usb2 stack 1630 libusb-0.1.so.8 libusb20.so.1 1631 163220090209: 1633 All USB ethernet devices now attach as interfaces under the name ueN 1634 (eg. ue0). This is to provide a predictable name as vendors often 1635 change usb chipsets in a product without notice. 1636 163720090203: 1638 The ichsmb(4) driver has been changed to require SMBus slave 1639 addresses be left-justified (xxxxxxx0b) rather than right-justified. 1640 All of the other SMBus controller drivers require left-justified 1641 slave addresses, so this change makes all the drivers provide the 1642 same interface. 1643 164420090201: 1645 INET6 statistics (struct ip6stat) was updated. 1646 netstat(1) needs to be recompiled. 1647 164820090119: 1649 NTFS has been removed from GENERIC kernel on amd64 to match 1650 GENERIC on i386. Should not cause any issues since mount_ntfs(8) 1651 will load ntfs.ko module automatically when NTFS support is 1652 actually needed, unless ntfs.ko is not installed or security 1653 level prohibits loading kernel modules. If either is the case, 1654 "options NTFS" has to be added into kernel config. 1655 165620090115: 1657 TCP Appropriate Byte Counting (RFC 3465) support added to kernel. 1658 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to 1659 800061. User space tools that rely on the size of struct tcpcb in 1660 tcp_var.h (e.g. sockstat) need to be recompiled. 1661 166220081225: 1663 ng_tty(4) module updated to match the new TTY subsystem. 1664 Due to API change, user-level applications must be updated. 1665 New API support added to mpd5 CVS and expected to be present 1666 in next mpd5.3 release. 1667 166820081219: 1669 With __FreeBSD_version 800060 the makefs tool is part of 1670 the base system (it was a port). 1671 167220081216: 1673 The afdata and ifnet locks have been changed from mutexes to 1674 rwlocks, network modules will need to be re-compiled. 1675 167620081214: 1677 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite. 1678 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated. 1679 The new code reduced struct rtentry{} by 16 bytes on 32-bit 1680 architecture and 40 bytes on 64-bit architecture. The userland 1681 applications "arp" and "ndp" have been updated accordingly. 1682 The output from "netstat -r" shows only routing entries and 1683 none of the L2 information. 1684 168520081130: 1686 __FreeBSD_version 800057 marks the switchover from the 1687 binary ath hal to source code. Users must add the line: 1688 1689 options AH_SUPPORT_AR5416 1690 1691 to their kernel config files when specifying: 1692 1693 device ath_hal 1694 1695 The ath_hal module no longer exists; the code is now compiled 1696 together with the driver in the ath module. It is now 1697 possible to tailor chip support (i.e. reduce the set of chips 1698 and thereby the code size); consult ath_hal(4) for details. 1699 170020081121: 1701 __FreeBSD_version 800054 adds memory barriers to 1702 <machine/atomic.h>, new interfaces to ifnet to facilitate 1703 multiple hardware transmit queues for cards that support 1704 them, and a lock-less ring-buffer implementation to 1705 enable drivers to more efficiently manage queueing of 1706 packets. 1707 170820081117: 1709 A new version of ZFS (version 13) has been merged to -HEAD. 1710 This version has zpool attribute "listsnapshots" off by 1711 default, which means "zfs list" does not show snapshots, 1712 and is the same as Solaris behavior. 1713 171420081028: 1715 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled. 1716 171720081009: 1718 The uhci, ohci, ehci and slhci USB Host controller drivers have 1719 been put into separate modules. If you load the usb module 1720 separately through loader.conf you will need to load the 1721 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0 1722 controller add the following to loader.conf: 1723 1724 uhci_load="YES" 1725 ehci_load="YES" 1726 172720081009: 1728 The ABI used by the PMC toolset has changed. Please keep 1729 userland (libpmc(3)) and the kernel module (hwpmc(4)) in 1730 sync. 1731 173220081009: 1733 atapci kernel module now includes only generic PCI ATA 1734 driver. AHCI driver moved to ataahci kernel module. 1735 All vendor-specific code moved into separate kernel modules: 1736 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek, 1737 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron, 1738 atamarvell, atamicron, atanational, atanetcell, atanvidia, 1739 atapromise, ataserverworks, atasiliconimage, atasis, atavia 1740 174120080820: 1742 The TTY subsystem of the kernel has been replaced by a new 1743 implementation, which provides better scalability and an 1744 improved driver model. Most common drivers have been migrated to 1745 the new TTY subsystem, while others have not. The following 1746 drivers have not yet been ported to the new TTY layer: 1747 1748 PCI/ISA: 1749 cy, digi, rc, rp, sio 1750 1751 USB: 1752 ubser, ucycom 1753 1754 Line disciplines: 1755 ng_h4, ng_tty, ppp, sl, snp 1756 1757 Adding these drivers to your kernel configuration file shall 1758 cause compilation to fail. 1759 176020080818: 1761 ntpd has been upgraded to 4.2.4p5. 1762 176320080801: 1764 OpenSSH has been upgraded to 5.1p1. 1765 1766 For many years, FreeBSD's version of OpenSSH preferred DSA 1767 over RSA for host and user authentication keys. With this 1768 upgrade, we've switched to the vendor's default of RSA over 1769 DSA. This may cause upgraded clients to warn about unknown 1770 host keys even for previously known hosts. Users should 1771 follow the usual procedure for verifying host keys before 1772 accepting the RSA key. 1773 1774 This can be circumvented by setting the "HostKeyAlgorithms" 1775 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh 1776 command line. 1777 1778 Please note that the sequence of keys offered for 1779 authentication has been changed as well. You may want to 1780 specify IdentityFile in a different order to revert this 1781 behavior. 1782 178320080713: 1784 The sio(4) driver has been removed from the i386 and amd64 1785 kernel configuration files. This means uart(4) is now the 1786 default serial port driver on those platforms as well. 1787 1788 To prevent collisions with the sio(4) driver, the uart(4) driver 1789 uses different names for its device nodes. This means the 1790 onboard serial port will now most likely be called "ttyu0" 1791 instead of "ttyd0". You may need to reconfigure applications to 1792 use the new device names. 1793 1794 When using the serial port as a boot console, be sure to update 1795 /boot/device.hints and /etc/ttys before booting the new kernel. 1796 If you forget to do so, you can still manually specify the hints 1797 at the loader prompt: 1798 1799 set hint.uart.0.at="isa" 1800 set hint.uart.0.port="0x3F8" 1801 set hint.uart.0.flags="0x10" 1802 set hint.uart.0.irq="4" 1803 boot -s 1804 180520080609: 1806 The gpt(8) utility has been removed. Use gpart(8) to partition 1807 disks instead. 1808 180920080603: 1810 The version that Linuxulator emulates was changed from 2.4.2 1811 to 2.6.16. If you experience any problems with Linux binaries 1812 please try to set sysctl compat.linux.osrelease to 2.4.2 and 1813 if it fixes the problem contact emulation mailing list. 1814 181520080525: 1816 ISDN4BSD (I4B) was removed from the src tree. You may need to 1817 update a your kernel configuration and remove relevant entries. 1818 181920080509: 1820 I have checked in code to support multiple routing tables. 1821 See the man pages setfib(1) and setfib(2). 1822 This is a hopefully backwards compatible version, 1823 but to make use of it you need to compile your kernel 1824 with options ROUTETABLES=2 (or more up to 16). 1825 182620080420: 1827 The 802.11 wireless support was redone to enable multi-bss 1828 operation on devices that are capable. The underlying device 1829 is no longer used directly but instead wlanX devices are 1830 cloned with ifconfig. This requires changes to rc.conf files. 1831 For example, change: 1832 ifconfig_ath0="WPA DHCP" 1833 to 1834 wlans_ath0=wlan0 1835 ifconfig_wlan0="WPA DHCP" 1836 see rc.conf(5) for more details. In addition, mergemaster of 1837 /etc/rc.d is highly recommended. Simultaneous update of userland 1838 and kernel wouldn't hurt either. 1839 1840 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta 1841 modules were merged into the base wlan module. All references 1842 to these modules (e.g. in kernel config files) must be removed. 1843 184420080408: 1845 psm(4) has gained write(2) support in native operation level. 1846 Arbitrary commands can be written to /dev/psm%d and status can 1847 be read back from it. Therefore, an application is responsible 1848 for status validation and error recovery. It is a no-op in 1849 other operation levels. 1850 185120080312: 1852 Support for KSE threading has been removed from the kernel. To 1853 run legacy applications linked against KSE libmap.conf may 1854 be used. The following libmap.conf may be used to ensure 1855 compatibility with any prior release: 1856 1857 libpthread.so.1 libthr.so.1 1858 libpthread.so.2 libthr.so.2 1859 libkse.so.3 libthr.so.3 1860 186120080301: 1862 The layout of struct vmspace has changed. This affects libkvm 1863 and any executables that link against libkvm and use the 1864 kvm_getprocs() function. In particular, but not exclusively, 1865 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1). 1866 The effects are minimal, but it's advisable to upgrade world 1867 nonetheless. 1868 186920080229: 1870 The latest em driver no longer has support in it for the 1871 82575 adapter, this is now moved to the igb driver. The 1872 split was done to make new features that are incompatible 1873 with older hardware easier to do. 1874 187520080220: 1876 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4), 1877 likewise the kernel option is now GEOM_LINUX_LVM. 1878 187920080211: 1880 The default NFS mount mode has changed from UDP to TCP for 1881 increased reliability. If you rely on (insecurely) NFS 1882 mounting across a firewall you may need to update your 1883 firewall rules. 1884 188520080208: 1886 Belatedly note the addition of m_collapse for compacting 1887 mbuf chains. 1888 188920080126: 1890 The fts(3) structures have been changed to use adequate 1891 integer types for their members and so to be able to cope 1892 with huge file trees. The old fts(3) ABI is preserved 1893 through symbol versioning in libc, so third-party binaries 1894 using fts(3) should still work, although they will not take 1895 advantage of the extended types. At the same time, some 1896 third-party software might fail to build after this change 1897 due to unportable assumptions made in its source code about 1898 fts(3) structure members. Such software should be fixed 1899 by its vendor or, in the worst case, in the ports tree. 1900 FreeBSD_version 800015 marks this change for the unlikely 1901 case that a portable fix is impossible. 1902 190320080123: 1904 To upgrade to -current after this date, you must be running 1905 FreeBSD not older than 6.0-RELEASE. Upgrading to -current 1906 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems. 1907 190820071128: 1909 The ADAPTIVE_GIANT kernel option has been retired because its 1910 functionality is the default now. 1911 191220071118: 1913 The AT keyboard emulation of sunkbd(4) has been turned on 1914 by default. In order to make the special symbols of the Sun 1915 keyboards driven by sunkbd(4) work under X these now have 1916 to be configured the same way as Sun USB keyboards driven 1917 by ukbd(4) (which also does AT keyboard emulation), f.e.: 1918 1919 Option "XkbLayout" "us" 1920 Option "XkbRules" "xorg" 1921 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us" 1922 192320071024: 1924 It has been decided that it is desirable to provide ABI 1925 backwards compatibility to the FreeBSD 4/5/6 versions of the 1926 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was 1927 broken with the introduction of PCI domain support (see the 1928 20070930 entry). Unfortunately, this required the ABI of 1929 PCIOCGETCONF to be broken again in order to be able to 1930 provide backwards compatibility to the old version of that 1931 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled 1932 again. As for prominent ports this affects neither pciutils 1933 nor xorg-server this time, the hal port needs to be rebuilt 1934 however. 1935 193620071020: 1937 The misnamed kthread_create() and friends have been renamed 1938 to kproc_create() etc. Many of the callers already 1939 used kproc_start().. 1940 I will return kthread_create() and friends in a while 1941 with implementations that actually create threads, not procs. 1942 Renaming corresponds with version 800002. 1943 194420071010: 1945 RELENG_7 branched. 1946 1947COMMON ITEMS: 1948 1949 General Notes 1950 ------------- 1951 Avoid using make -j when upgrading. While generally safe, there are 1952 sometimes problems using -j to upgrade. If your upgrade fails with 1953 -j, please try again without -j. From time to time in the past there 1954 have been problems using -j with buildworld and/or installworld. This 1955 is especially true when upgrading between "distant" versions (eg one 1956 that cross a major release boundary or several minor releases, or when 1957 several months have passed on the -current branch). 1958 1959 Sometimes, obscure build problems are the result of environment 1960 poisoning. This can happen because the make utility reads its 1961 environment when searching for values for global variables. To run 1962 your build attempts in an "environmental clean room", prefix all make 1963 commands with 'env -i '. See the env(1) manual page for more details. 1964 1965 When upgrading from one major version to another it is generally best 1966 to upgrade to the latest code in the currently installed branch first, 1967 then do an upgrade to the new branch. This is the best-tested upgrade 1968 path, and has the highest probability of being successful. Please try 1969 this approach before reporting problems with a major version upgrade. 1970 1971 When upgrading a live system, having a root shell around before 1972 installing anything can help undo problems. Not having a root shell 1973 around can lead to problems if pam has changed too much from your 1974 starting point to allow continued authentication after the upgrade. 1975 1976 ZFS notes 1977 --------- 1978 When upgrading the boot ZFS pool to a new version, always follow 1979 these two steps: 1980 1981 1.) recompile and reinstall the ZFS boot loader and boot block 1982 (this is part of "make buildworld" and "make installworld") 1983 1984 2.) update the ZFS boot block on your boot drive 1985 1986 The following example updates the ZFS boot block on the first 1987 partition (freebsd-boot) of a GPT partitioned drive ad0: 1988 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0" 1989 1990 Non-boot pools do not need these updates. 1991 1992 To build a kernel 1993 ----------------- 1994 If you are updating from a prior version of FreeBSD (even one just 1995 a few days old), you should follow this procedure. It is the most 1996 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1997 1998 make kernel-toolchain 1999 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 2000 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 2001 2002 To test a kernel once 2003 --------------------- 2004 If you just want to boot a kernel once (because you are not sure 2005 if it works, or if you want to boot a known bad kernel to provide 2006 debugging information) run 2007 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 2008 nextboot -k testkernel 2009 2010 To just build a kernel when you know that it won't mess you up 2011 -------------------------------------------------------------- 2012 This assumes you are already running a CURRENT system. Replace 2013 ${arch} with the architecture of your machine (e.g. "i386", 2014 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 2015 2016 cd src/sys/${arch}/conf 2017 config KERNEL_NAME_HERE 2018 cd ../compile/KERNEL_NAME_HERE 2019 make depend 2020 make 2021 make install 2022 2023 If this fails, go to the "To build a kernel" section. 2024 2025 To rebuild everything and install it on the current system. 2026 ----------------------------------------------------------- 2027 # Note: sometimes if you are running current you gotta do more than 2028 # is listed here if you are upgrading from a really old current. 2029 2030 <make sure you have good level 0 dumps> 2031 make buildworld 2032 make kernel KERNCONF=YOUR_KERNEL_HERE 2033 [1] 2034 <reboot in single user> [3] 2035 mergemaster -p [5] 2036 make installworld 2037 mergemaster -i [4] 2038 make delete-old [6] 2039 <reboot> 2040 2041 To cross-install current onto a separate partition 2042 -------------------------------------------------- 2043 # In this approach we use a separate partition to hold 2044 # current's root, 'usr', and 'var' directories. A partition 2045 # holding "/", "/usr" and "/var" should be about 2GB in 2046 # size. 2047 2048 <make sure you have good level 0 dumps> 2049 <boot into -stable> 2050 make buildworld 2051 make buildkernel KERNCONF=YOUR_KERNEL_HERE 2052 <maybe newfs current's root partition> 2053 <mount current's root partition on directory ${CURRENT_ROOT}> 2054 make installworld DESTDIR=${CURRENT_ROOT} 2055 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 2056 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 2057 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 2058 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 2059 <reboot into current> 2060 <do a "native" rebuild/install as described in the previous section> 2061 <maybe install compatibility libraries from ports/misc/compat*> 2062 <reboot> 2063 2064 2065 To upgrade in-place from stable to current 2066 ---------------------------------------------- 2067 <make sure you have good level 0 dumps> 2068 make buildworld [9] 2069 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 2070 [1] 2071 <reboot in single user> [3] 2072 mergemaster -p [5] 2073 make installworld 2074 mergemaster -i [4] 2075 make delete-old [6] 2076 <reboot> 2077 2078 Make sure that you've read the UPDATING file to understand the 2079 tweaks to various things you need. At this point in the life 2080 cycle of current, things change often and you are on your own 2081 to cope. The defaults can also change, so please read ALL of 2082 the UPDATING entries. 2083 2084 Also, if you are tracking -current, you must be subscribed to 2085 freebsd-current@freebsd.org. Make sure that before you update 2086 your sources that you have read and understood all the recent 2087 messages there. If in doubt, please track -stable which has 2088 much fewer pitfalls. 2089 2090 [1] If you have third party modules, such as vmware, you 2091 should disable them at this point so they don't crash your 2092 system on reboot. 2093 2094 [3] From the bootblocks, boot -s, and then do 2095 fsck -p 2096 mount -u / 2097 mount -a 2098 cd src 2099 adjkerntz -i # if CMOS is wall time 2100 Also, when doing a major release upgrade, it is required that 2101 you boot into single user mode to do the installworld. 2102 2103 [4] Note: This step is non-optional. Failure to do this step 2104 can result in a significant reduction in the functionality of the 2105 system. Attempting to do it by hand is not recommended and those 2106 that pursue this avenue should read this file carefully, as well 2107 as the archives of freebsd-current and freebsd-hackers mailing lists 2108 for potential gotchas. The -U option is also useful to consider. 2109 See mergemaster(8) for more information. 2110 2111 [5] Usually this step is a noop. However, from time to time 2112 you may need to do this if you get unknown user in the following 2113 step. It never hurts to do it all the time. You may need to 2114 install a new mergemaster (cd src/usr.sbin/mergemaster && make 2115 install) after the buildworld before this step if you last updated 2116 from current before 20130425 or from -stable before 20130430. 2117 2118 [6] This only deletes old files and directories. Old libraries 2119 can be deleted by "make delete-old-libs", but you have to make 2120 sure that no program is using those libraries anymore. 2121 2122 [8] In order to have a kernel that can run the 4.x binaries needed to 2123 do an installworld, you must include the COMPAT_FREEBSD4 option in 2124 your kernel. Failure to do so may leave you with a system that is 2125 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 2126 required to run the 5.x binaries on more recent kernels. And so on 2127 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 2128 2129 Make sure that you merge any new devices from GENERIC since the 2130 last time you updated your kernel config file. 2131 2132 [9] When checking out sources, you must include the -P flag to have 2133 cvs prune empty directories. 2134 2135 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 2136 "?=" instead of the "=" assignment operator, so that buildworld can 2137 override the CPUTYPE if it needs to. 2138 2139 MAKEOBJDIRPREFIX must be defined in an environment variable, and 2140 not on the command line, or in /etc/make.conf. buildworld will 2141 warn if it is improperly defined. 2142FORMAT: 2143 2144This file contains a list, in reverse chronological order, of major 2145breakages in tracking -current. It is not guaranteed to be a complete 2146list of such breakages, and only contains entries since October 10, 2007. 2147If you need to see UPDATING entries from before that date, you will need 2148to fetch an UPDATING file from an older FreeBSD release. 2149 2150Copyright information: 2151 2152Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 2153 2154Redistribution, publication, translation and use, with or without 2155modification, in full or in part, in any form or format of this 2156document are permitted without further permission from the author. 2157 2158THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 2159IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 2160WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 2161DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 2162INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 2163(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 2164SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 2165HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 2166STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 2167IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 2168POSSIBILITY OF SUCH DAMAGE. 2169 2170Contact Warner Losh if you have any questions about your use of 2171this document. 2172 2173$FreeBSD: releng/10.1/UPDATING 277195 2015-01-14 21:27:46Z delphij $ 2174