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