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