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