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