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