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