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