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/current-stable.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 and WITH_GCC to bootstrap to 16the tip of head, and then rebuild without this option. The bootstrap process 17from older version of current across the gcc/clang cutover is a bit fragile. 18 19NOTE TO PEOPLE WHO THINK THAT FreeBSD 12.x IS SLOW: 20 FreeBSD 12.x has many debugging features turned on, in both the kernel 21 and userland. These features attempt to detect incorrect use of 22 system primitives, and encourage loud failure through extra sanity 23 checking and fail stop semantics. They also substantially impact 24 system performance. If you want to do performance measurement, 25 benchmarking, and optimization, you'll want to turn them off. This 26 includes various WITNESS- related kernel options, INVARIANTS, malloc 27 debugging flags in userland, and various verbose features in the 28 kernel. Many developers choose to disable these features on build 29 machines to maximize performance. (To completely disable malloc 30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely 31 disable the most expensive debugging functionality run 32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".) 33 34 35****************************** SPECIAL WARNING: ****************************** 36 37 Due to a bug in some versions of clang that's very hard to workaround in 38 the upgrade process, to upgrade to -current you must first upgrade 39 either stable/9 after r286035 or stable/10 after r286033 (including 40 10.3-RELEASE) or current after r286007 (including stable/11 and 41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so 42 you'll need to take the unusual step of upgrading to the tip of the 43 stable branch before moving to 11 or -current via a source upgrade. 44 stable/11 and 11.0-RELEASE have working newer compiler. This differs 45 from the historical situation where one could upgrade from anywhere on 46 the last couple of stable branches, so be careful. 47 48 If you're running a hybrid system on 9.x or 10.x with an updated clang 49 compiler or are using an supported external toolchain, the build system 50 will allow the upgrade. Otherwise it will print a reminder. 51 52****************************** SPECIAL WARNING: ****************************** 53 5420171028: 55 The native-xtools target no longer installs the files by default to the 56 OBJDIR. Use the native-xtools-install target with a DESTDIR to install 57 to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin. 58 5920171021: 60 As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT 61 options are changing from controlling the build if defined / undefined 62 to controlling the build with explicit 'yes' or 'no' values. They will 63 shift to WITH/WITHOUT options to match other options in the system. 64 6520171010: 66 libstand has turned into a private library for sys/boot use only. 67 It is no longer supported as a public interface outside of sys/boot. 68 6920171005: 70 The arm port has split armv6 into armv6 and armv7. armv7 is now 71 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system 72 and are running a kernel from before r324363, you will need to add 73 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build. 74 7520171003: 76 When building multiple kernels using KERNCONF, non-existent KERNCONF 77 files will produce an error and buildkernel will fail. Previously 78 missing KERNCONF files silently failed giving no indication as to 79 why, only to subsequently discover during installkernel that the 80 desired kernel was never built in the first place. 81 8220170912: 83 The default serial number format for CTL LUNs has changed. This will 84 affect users who use /dev/diskid/* device nodes, or whose FibreChannel 85 or iSCSI clients care about their LUNs' serial numbers. Users who 86 require serial number stability should hardcode serial numbers in 87 /etc/ctl.conf . 88 8920170912: 90 For 32-bit arm compiled for hard-float support, soft-floating point 91 binaries now always get their shared libraries from 92 LD_SOFT_LIBRARY_PATH (in the past, this was only used if 93 /usr/libsoft also existed). Only users with a hard-float ld.so, but 94 soft-float everything else should be affected. 95 9620170826: 97 The geli password typed at boot is now hidden. To restore the previous 98 behavior, see geli(8) for configuration options. 99 10020170825: 101 Move PMTUD blackhole counters to TCPSTATS and remove them from bare 102 sysctl values. Minor nit, but requires a rebuild of both world/kernel 103 to complete. 104 10520170814: 106 "make check" behavior (made in ^/head@r295380) has been changed to 107 execute from a limited sandbox, as opposed to executing from 108 ${TESTSDIR}. 109 110 Behavioral changes: 111 - The "beforecheck" and "aftercheck" targets are now specified. 112 - ${CHECKDIR} (added in commit noted above) has been removed. 113 - Legacy behavior can be enabled by setting 114 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment. 115 116 If the limited sandbox mode is enabled, "make check" will execute 117 "make distribution", then install, execute the tests, and clean up the 118 sandbox if successful. 119 120 The "make distribution" and "make install" targets are typically run as 121 root to set appropriate permissions and ownership at installation time. 122 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the 123 environment if executing "make check" with limited sandbox mode using 124 an unprivileged user. 125 12620170808: 127 Since the switch to GPT disk labels, fsck for UFS/FFS has been 128 unable to automatically find alternate superblocks. As of r322297, 129 the information needed to find alternate superblocks has been 130 moved to the end of the area reserved for the boot block. 131 Filesystems created with a newfs of this vintage or later 132 will create the recovery information. If you have a filesystem 133 created prior to this change and wish to have a recovery block 134 created for your filesystem, you can do so by running fsck in 135 forground mode (i.e., do not use the -p or -y options). As it 136 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS'' 137 to which you should answer yes. 138 13920170728: 140 As of r321665, an NFSv4 server configuration that services 141 Kerberos mounts or clients that do not support the uid/gid in 142 owner/owner_group string capability, must explicitly enable 143 the nfsuserd daemon by adding nfsuserd_enable="YES" to the 144 machine's /etc/rc.conf file. 145 14620170722: 147 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0. 148 Please see the 20141231 entry below for information about prerequisites 149 and upgrading, if you are not already using clang 3.5.0 or higher. 150 15120170701: 152 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the 153 r-commands (rlogin, rsh, etc.) to be built with the base system. 154 15520170625: 156 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is 157 a very major ABI incompatible change, so users of FreeBSD/powerpc must 158 be careful when performing source upgrades. It is best to run 159 'make installworld' from an alternate root system, either a live 160 CD/memory stick, or a temporary root partition. Additionally, all ports 161 must be recompiled. powerpc64 is largely unaffected, except in the case 162 of 32-bit compatibility. All 32-bit binaries will be affected. 163 16420170623: 165 Forward compatibility for the "ino64" project have been committed. This 166 will allow most new binaries to run on older kernels in a limited 167 fashion. This prevents many of the common foot-shooting actions in the 168 upgrade as well as the limited ability to roll back the kernel across 169 the ino64 upgrade. Complicated use cases may not work properly, though 170 enough simpler ones work to allow recovery in most situations. 171 17220170620: 173 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC 174 if you require the GPL compiler. 175 17620170618: 177 The internal ABI used for communication between the NFS kernel modules 178 was changed by r320085, so __FreeBSD_version was bumped to 179 ensure all the NFS related modules are updated together. 180 18120170617: 182 The ABI of struct event was changed by extending the data 183 member to 64bit and adding ext fields. For upgrade, same 184 precautions as for the entry 20170523 "ino64" must be 185 followed. 186 18720170531: 188 The GNU roff toolchain has been removed from base. To render manpages 189 which are not supported by mandoc(1), man(1) can fallback on GNU roff 190 from ports (and recommends to install it). 191 To render roff(7) documents, consider using GNU roff from ports or the 192 heirloom doctools roff toolchain from ports via pkg install groff or 193 via pkg install heirloom-doctools. 194 19520170524: 196 The ath(4) and ath_hal(4) modules now build piecemeal to allow for 197 smaller runtime footprint builds. This is useful for embedded systems 198 which only require one chipset support. 199 200 If you load it as a module, make sure this is in /boot/loader.conf: 201 202 if_ath_load="YES" 203 204 This will load the HAL, all chip/RF backends and if_ath_pci. 205 If you have if_ath_pci in /boot/loader.conf, ensure it is after 206 if_ath or it will not load any HAL chipset support. 207 208 If you want to selectively load things (eg on ye cheape ARM/MIPS 209 platforms where RAM is at a premium) you should: 210 211 * load ath_hal 212 * load the chip modules in question 213 * load ath_rate, ath_dfs 214 * load ath_main 215 * load if_ath_pci and/or if_ath_ahb depending upon your particular 216 bus bind type - this is where probe/attach is done. 217 218 For further comments/feedback, poke adrian@ . 219 22020170523: 221 The "ino64" 64-bit inode project has been committed, which extends 222 a number of types to 64 bits. Upgrading in place requires care and 223 adherence to the documented upgrade procedure. 224 225 If using a custom kernel configuration ensure that the 226 COMPAT_FREEBSD11 option is included (as during the upgrade the 227 system will be running the ino64 kernel with the existing world). 228 229 For the safest in-place upgrade begin by removing previous build 230 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the 231 full procedure documented below under the heading "To rebuild 232 everything and install it on the current system." Specifically, 233 a reboot is required after installing the new kernel before 234 installing world. 235 23620170424: 237 The NATM framework including the en(4), fatm(4), hatm(4), and 238 patm(4) devices has been removed. Consumers should plan a 239 migration before the end-of-life date for FreeBSD 11. 240 24120170420: 242 GNU diff has been replaced by a BSD licensed diff. Some features of GNU 243 diff has not been implemented, if those are needed a newer version of 244 GNU diff is available via the diffutils package under the gdiff name. 245 24620170413: 247 As of r316810 for ipfilter, keep frags is no longer assumed when 248 keep state is specified in a rule. r316810 aligns ipfilter with 249 documentation in man pages separating keep frags from keep state. 250 This allows keep state to be specified without forcing keep frags 251 and allows keep frags to be specified independently of keep state. 252 To maintain previous behaviour, also specify keep frags with 253 keep state (as documented in ipf.conf.5). 254 25520170407: 256 arm64 builds now use the base system LLD 4.0.0 linker by default, 257 instead of requiring that the aarch64-binutils port or package be 258 installed. To continue using aarch64-binutils, set 259 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin . 260 26120170405: 262 The UDP optimization in entry 20160818 that added the sysctl 263 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast 264 packets will no longer be treated as L3 broadcast packets. 265 26620170331: 267 Binds and sends to the loopback addresses, IPv6 and IPv4, will now 268 use any explicitly assigned loopback address available in the jail 269 instead of using the first assigned address of the jail. 270 27120170329: 272 The ctl.ko module no longer implements the iSCSI target frontend: 273 cfiscsi.ko does instead. 274 275 If building cfiscsi.ko as a kernel module, the module can be loaded 276 via one of the following methods: 277 - `cfiscsi_load="YES"` in loader.conf(5). 278 - Add `cfiscsi` to `$kld_list` in rc.conf(5). 279 - ctladm(8)/ctld(8), when compiled with iSCSI support 280 (`WITH_ISCSI=yes` in src.conf(5)) 281 282 Please see cfiscsi(4) for more details. 283 28420170316: 285 The mmcsd.ko module now additionally depends on geom_flashmap.ko. 286 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the 287 same source (previously, the dependency of mmcsd.ko on mmc.ko was 288 missing, but mmcsd.ko now will refuse to load if it is incompatible 289 with mmc.ko). 290 29120170315: 292 The syntax of ipfw(8) named states was changed to avoid ambiguity. 293 If you have used named states in the firewall rules, you need to modify 294 them after installworld and before rebooting. Now named states must 295 be prefixed with colon. 296 29720170311: 298 The old drm (sys/dev/drm/) drivers for i915 and radeon have been 299 removed as the userland we provide cannot use them. The KMS version 300 (sys/dev/drm2) supports the same hardware. 301 30220170302: 303 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0. 304 Please see the 20141231 entry below for information about prerequisites 305 and upgrading, if you are not already using clang 3.5.0 or higher. 306 30720170221: 308 The code that provides support for ZFS .zfs/ directory functionality 309 has been reimplemented. It's not possible now to create a snapshot 310 by mkdir under .zfs/snapshot/. That should be the only user visible 311 change. 312 31320170216: 314 EISA bus support has been removed. The WITH_EISA option is no longer 315 valid. 316 31720170215: 318 MCA bus support has been removed. 319 32020170127: 321 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed 322 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC. 323 32420170112: 325 The EM_MULTIQUEUE kernel configuration option is deprecated now that 326 the em(4) driver conforms to iflib specifications. 327 32820170109: 329 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via 330 IFLIB. If you have a custom kernel configuration that excludes em(4) 331 but you use igb(4), you need to re-add em(4) to your custom configuration. 332 33320161217: 334 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1. 335 Please see the 20141231 entry below for information about prerequisites 336 and upgrading, if you are not already using clang 3.5.0 or higher. 337 33820161124: 339 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0. 340 Please see the 20141231 entry below for information about prerequisites 341 and upgrading, if you are not already using clang 3.5.0 or higher. 342 34320161119: 344 The layout of the pmap structure has changed for powerpc to put the pmap 345 statistics at the front for all CPU variations. libkvm(3) and all tools 346 that link against it need to be recompiled. 347 34820161030: 349 isl(4) and cyapa(4) drivers now require a new driver, 350 chromebook_platform(4), to work properly on Chromebook-class hardware. 351 On other types of hardware the drivers may need to be configured using 352 device hints. Please see the corresponding manual pages for details. 353 35420161017: 355 The urtwn(4) driver was merged into rtwn(4) and now consists of 356 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific 357 parts. 358 Also, firmware for RTL8188CE was renamed due to possible name 359 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B)) 360 36120161015: 362 GNU rcs has been removed from base. It is available as packages: 363 - rcs: Latest GPLv3 GNU rcs version. 364 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was 365 removed from base. 366 36720161008: 368 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control 369 modules now requires that the kernel configuration contain the 370 TCP_HHOOK option. (This option is included in the GENERIC kernel.) 371 37220161003: 373 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired. 374 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy. 375 37620160924: 377 Relocatable object files with the extension of .So have been renamed 378 to use an extension of .pico instead. The purpose of this change is 379 to avoid a name clash with shared libraries on case-insensitive file 380 systems. On those file systems, foo.So is the same file as foo.so. 381 38220160918: 383 GNU rcs has been turned off by default. It can (temporarily) be built 384 again by adding WITH_RCS knob in src.conf. 385 Otherwise, GNU rcs is available from packages: 386 - rcs: Latest GPLv3 GNU rcs version. 387 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base. 388 38920160918: 390 The backup_uses_rcs functionality has been removed from rc.subr. 391 39220160908: 393 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into 394 two separate components, QUEUE_MACRO_DEBUG_TRACE and 395 QUEUE_MACRO_DEBUG_TRASH. Define both for the original 396 QUEUE_MACRO_DEBUG behavior. 397 39820160824: 399 r304787 changed some ioctl interfaces between the iSCSI userspace 400 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be 401 rebuilt to work with new kernels. __FreeBSD_version has been bumped 402 to 1200005. 403 40420160818: 405 The UDP receive code has been updated to only treat incoming UDP 406 packets that were addressed to an L2 broadcast address as L3 407 broadcast packets. It is not expected that this will affect any 408 standards-conforming UDP application. The new behaviour can be 409 disabled by setting the sysctl net.inet.udp.require_l2_bcast to 410 0. 411 41220160818: 413 Remove the openbsd_poll system call. 414 __FreeBSD_version has been bumped because of this. 415 41620160622: 417 The libc stub for the pipe(2) system call has been replaced with 418 a wrapper that calls the pipe2(2) system call and the pipe(2) 419 system call is now only implemented by the kernels that include 420 "options COMPAT_FREEBSD10" in their config file (this is the 421 default). Users should ensure that this option is enabled in 422 their kernel or upgrade userspace to r302092 before upgrading their 423 kernel. 424 42520160527: 426 CAM will now strip leading spaces from SCSI disks' serial numbers. 427 This will affect users who create UFS filesystems on SCSI disks using 428 those disk's diskid device nodes. For example, if /etc/fstab 429 previously contained a line like 430 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should 431 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom 432 transforms like gmirror may also be affected. ZFS users should 433 generally be fine. 434 43520160523: 436 The bitstring(3) API has been updated with new functionality and 437 improved performance. But it is binary-incompatible with the old API. 438 Objects built with the new headers may not be linked against objects 439 built with the old headers. 440 44120160520: 442 The brk and sbrk functions have been removed from libc on arm64. 443 Binutils from ports has been updated to not link to these 444 functions and should be updated to the latest version before 445 installing a new libc. 446 44720160517: 448 The armv6 port now defaults to hard float ABI. Limited support 449 for running both hardfloat and soft float on the same system 450 is available using the libraries installed with -DWITH_LIBSOFT. 451 This has only been tested as an upgrade path for installworld 452 and packages may fail or need manual intervention to run. New 453 packages will be needed. 454 455 To update an existing self-hosted armv6hf system, you must add 456 TARGET_ARCH=armv6 on the make command line for both the build 457 and the install steps. 458 45920160510: 460 Kernel modules compiled outside of a kernel build now default to 461 installing to /boot/modules instead of /boot/kernel. Many kernel 462 modules built this way (such as those in ports) already overrode 463 KMODDIR explicitly to install into /boot/modules. However, 464 manually building and installing a module from /sys/modules will 465 now install to /boot/modules instead of /boot/kernel. 466 46720160414: 468 The CAM I/O scheduler has been committed to the kernel. There should be 469 no user visible impact. This does enable NCQ Trim on ada SSDs. While the 470 list of known rogues that claim support for this but actually corrupt 471 data is believed to be complete, be on the lookout for data 472 corruption. The known rogue list is believed to be complete: 473 474 o Crucial MX100, M550 drives with MU01 firmware. 475 o Micron M510 and M550 drives with MU01 firmware. 476 o Micron M500 prior to MU07 firmware 477 o Samsung 830, 840, and 850 all firmwares 478 o FCCT M500 all firmwares 479 480 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware 481 with working NCQ TRIM. For Micron branded drives, see your sales rep for 482 updated firmware. Black listed drives will work correctly because these 483 drives work correctly so long as no NCQ TRIMs are sent to them. Given 484 this list is the same as found in Linux, it's believed there are no 485 other rogues in the market place. All other models from the above 486 vendors work. 487 488 To be safe, if you are at all concerned, you can quirk each of your 489 drives to prevent NCQ from being sent by setting: 490 kern.cam.ada.X.quirks="0x2" 491 in loader.conf. If the drive requires the 4k sector quirk, set the 492 quirks entry to 0x3. 493 49420160330: 495 The FAST_DEPEND build option has been removed and its functionality is 496 now the one true way. The old mkdep(1) style of 'make depend' has 497 been removed. See 20160311 for further details. 498 49920160317: 500 Resource range types have grown from unsigned long to uintmax_t. All 501 drivers, and anything using libdevinfo, need to be recompiled. 502 50320160311: 504 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree 505 builds. It no longer runs mkdep(1) during 'make depend', and the 506 'make depend' stage can safely be skipped now as it is auto ran 507 when building 'make all' and will generate all SRCS and DPSRCS before 508 building anything else. Dependencies are gathered at compile time with 509 -MF flags kept in separate .depend files per object file. Users should 510 run 'make cleandepend' once if using -DNO_CLEAN to clean out older 511 stale .depend files. 512 51320160306: 514 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into 515 kernel modules. Therefore, if you load any kernel modules at boot time, 516 please install the boot loaders after you install the kernel, but before 517 rebooting, e.g.: 518 519 make buildworld 520 make kernel KERNCONF=YOUR_KERNEL_HERE 521 make -C sys/boot install 522 <reboot in single user> 523 524 Then follow the usual steps, described in the General Notes section, 525 below. 526 52720160305: 528 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please 529 see the 20141231 entry below for information about prerequisites and 530 upgrading, if you are not already using clang 3.5.0 or higher. 531 53220160301: 533 The AIO subsystem is now a standard part of the kernel. The 534 VFS_AIO kernel option and aio.ko kernel module have been removed. 535 Due to stability concerns, asynchronous I/O requests are only 536 permitted on sockets and raw disks by default. To enable 537 asynchronous I/O requests on all file types, set the 538 vfs.aio.enable_unsafe sysctl to a non-zero value. 539 54020160226: 541 The ELF object manipulation tool objcopy is now provided by the 542 ELF Tool Chain project rather than by GNU binutils. It should be a 543 drop-in replacement, with the addition of arm64 support. The 544 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set 545 to obtain the GNU version if necessary. 546 54720160129: 548 Building ZFS pools on top of zvols is prohibited by default. That 549 feature has never worked safely; it's always been prone to deadlocks. 550 Using a zvol as the backing store for a VM guest's virtual disk will 551 still work, even if the guest is using ZFS. Legacy behavior can be 552 restored by setting vfs.zfs.vol.recursive=1. 553 55420160119: 555 The NONE and HPN patches has been removed from OpenSSH. They are 556 still available in the security/openssh-portable port. 557 55820160113: 559 With the addition of ypldap(8), a new _ypldap user is now required 560 during installworld. "mergemaster -p" can be used to add the user 561 prior to installworld, as documented in the handbook. 562 56320151216: 564 The tftp loader (pxeboot) now uses the option root-path directive. As a 565 consequence it no longer looks for a pxeboot.4th file on the tftp 566 server. Instead it uses the regular /boot infrastructure as with the 567 other loaders. 568 56920151211: 570 The code to start recording plug and play data into the modules has 571 been committed. While the old tools will properly build a new kernel, 572 a number of warnings about "unknown metadata record 4" will be produced 573 for an older kldxref. To avoid such warnings, make sure to rebuild 574 the kernel toolchain (or world). Make sure that you have r292078 or 575 later when trying to build 292077 or later before rebuilding. 576 57720151207: 578 Debug data files are now built by default with 'make buildworld' and 579 installed with 'make installworld'. This facilitates debugging but 580 requires more disk space both during the build and for the installed 581 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes 582 in src.conf(5). 583 58420151130: 585 r291527 changed the internal interface between the nfsd.ko and 586 nfscommon.ko modules. As such, they must both be upgraded to-gether. 587 __FreeBSD_version has been bumped because of this. 588 58920151108: 590 Add support for unicode collation strings leads to a change of 591 order of files listed by ls(1) for example. To get back to the old 592 behaviour, set LC_COLLATE environment variable to "C". 593 594 Databases administrators will need to reindex their databases given 595 collation results will be different. 596 597 Due to a bug in install(1) it is recommended to remove the ancient 598 locales before running make installworld. 599 600 rm -rf /usr/share/locale/* 601 60220151030: 603 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring 604 libcrypto.so.7 or libssl.so.7 must be recompiled. 605 60620151020: 607 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0. 608 Kernel modules isp_2400_multi and isp_2500_multi were removed and 609 should be replaced with isp_2400 and isp_2500 modules respectively. 610 61120151017: 612 The build previously allowed using 'make -n' to not recurse into 613 sub-directories while showing what commands would be executed, and 614 'make -n -n' to recursively show commands. Now 'make -n' will recurse 615 and 'make -N' will not. 616 61720151012: 618 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster 619 and etcupdate will now use this file. A custom sendmail.cf is now 620 updated via this mechanism rather than via installworld. If you had 621 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may 622 want to remove the exclusion or change it to "always install". 623 /etc/mail/sendmail.cf is now managed the same way regardless of 624 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using 625 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior. 626 62720151011: 628 Compatibility shims for legacy ATA device names have been removed. 629 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases 630 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.* 631 environment variables, /dev/ad* and /dev/ar* symbolic links. 632 63320151006: 634 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0. 635 Please see the 20141231 entry below for information about prerequisites 636 and upgrading, if you are not already using clang 3.5.0 or higher. 637 63820150924: 639 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/, 640 and renamed from .symbols to .debug. This reduces the size requirements 641 on the boot partition or file system and provides consistency with 642 userland debug files. 643 644 When using the supported kernel installation method the 645 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old) 646 as is done with /boot/kernel. 647 648 Developers wishing to maintain the historical behavior of installing 649 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5). 650 65120150827: 652 The wireless drivers had undergone changes that remove the 'parent 653 interface' from the ifconfig -l output. The rc.d network scripts 654 used to check presence of a parent interface in the list, so old 655 scripts would fail to start wireless networking. Thus, etcupdate(3) 656 or mergemaster(8) run is required after kernel update, to update your 657 rc.d scripts in /etc. 658 65920150827: 660 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl' 661 These configurations are now automatically interpreted as 662 'scrub fragment reassemble'. 663 66420150817: 665 Kernel-loadable modules for the random(4) device are back. To use 666 them, the kernel must have 667 668 device random 669 options RANDOM_LOADABLE 670 671 kldload(8) can then be used to load random_fortuna.ko 672 or random_yarrow.ko. Please note that due to the indirect 673 function calls that the loadable modules need to provide, 674 the build-in variants will be slightly more efficient. 675 676 The random(4) kernel option RANDOM_DUMMY has been retired due to 677 unpopularity. It was not all that useful anyway. 678 67920150813: 680 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired. 681 Control over building the ELF Tool Chain tools is now provided by 682 the WITHOUT_TOOLCHAIN knob. 683 68420150810: 685 The polarity of Pulse Per Second (PPS) capture events with the 686 uart(4) driver has been corrected. Prior to this change the PPS 687 "assert" event corresponded to the trailing edge of a positive PPS 688 pulse and the "clear" event was the leading edge of the next pulse. 689 690 As the width of a PPS pulse in a typical GPS receiver is on the 691 order of 1 millisecond, most users will not notice any significant 692 difference with this change. 693 694 Anyone who has compensated for the historical polarity reversal by 695 configuring a negative offset equal to the pulse width will need to 696 remove that workaround. 697 69820150809: 699 The default group assigned to /dev/dri entries has been changed 700 from 'wheel' to 'video' with the id of '44'. If you want to have 701 access to the dri devices please add yourself to the video group 702 with: 703 704 # pw groupmod video -m $USER 705 70620150806: 707 The menu.rc and loader.rc files will now be replaced during 708 upgrades. Please migrate local changes to menu.rc.local and 709 loader.rc.local instead. 710 71120150805: 712 GNU Binutils versions of addr2line, c++filt, nm, readelf, size, 713 strings and strip have been removed. The src.conf(5) knob 714 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools. 715 71620150728: 717 As ZFS requires more kernel stack pages than is the default on some 718 architectures e.g. i386, it now warns if KSTACK_PAGES is less than 719 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing). 720 721 Please consider using 'options KSTACK_PAGES=X' where X is greater 722 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations. 723 72420150706: 725 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0 726 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by 727 default, i.e., they will not contain "::". For example, instead 728 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet 729 to have a more specific match, such as different map entries for 730 IPv6:0:0 vs IPv6:0. This change requires that configuration 731 data (including maps, files, classes, custom ruleset, etc.) must 732 use the same format, so make certain such configuration data is 733 upgrading. As a very simple check search for patterns like 734 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old 735 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or 736 the cf option UseCompressedIPv6Addresses. 737 73820150630: 739 The default kernel entropy-processing algorithm is now 740 Fortuna, replacing Yarrow. 741 742 Assuming you have 'device random' in your kernel config 743 file, the configurations allow a kernel option to override 744 this default. You may choose *ONE* of: 745 746 options RANDOM_YARROW # Legacy /dev/random algorithm. 747 options RANDOM_DUMMY # Blocking-only driver. 748 749 If you have neither, you get Fortuna. For most people, 750 read no further, Fortuna will give a /dev/random that works 751 like it always used to, and the difference will be irrelevant. 752 753 If you remove 'device random', you get *NO* kernel-processed 754 entropy at all. This may be acceptable to folks building 755 embedded systems, but has complications. Carry on reading, 756 and it is assumed you know what you need. 757 758 *PLEASE* read random(4) and random(9) if you are in the 759 habit of tweaking kernel configs, and/or if you are a member 760 of the embedded community, wanting specific and not-usual 761 behaviour from your security subsystems. 762 763 NOTE!! If you use RANDOM_DUMMY and/or have no 'device 764 random', you will NOT have a functioning /dev/random, and 765 many cryptographic features will not work, including SSH. 766 You may also find strange behaviour from the random(3) set 767 of library functions, in particular sranddev(3), srandomdev(3) 768 and arc4random(3). The reason for this is that the KERN_ARND 769 sysctl only returns entropy if it thinks it has some to 770 share, and with RANDOM_DUMMY or no 'device random' this 771 will never happen. 772 77320150623: 774 An additional fix for the issue described in the 20150614 sendmail 775 entry below has been been committed in revision 284717. 776 77720150616: 778 FreeBSD's old make (fmake) has been removed from the system. It is 779 available as the devel/fmake port or via pkg install fmake. 780 78120150615: 782 The fix for the issue described in the 20150614 sendmail entry 783 below has been been committed in revision 284436. The work 784 around described in that entry is no longer needed unless the 785 default setting is overridden by a confDH_PARAMETERS configuration 786 setting of '5' or pointing to a 512 bit DH parameter file. 787 78820150614: 789 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from 790 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf 791 and devel/kyua to version 0.20+ and adjust any calling code to work 792 with Kyuafile and kyua. 793 79420150614: 795 The import of openssl to address the FreeBSD-SA-15:10.openssl 796 security advisory includes a change which rejects handshakes 797 with DH parameters below 768 bits. sendmail releases prior 798 to 8.15.2 (not yet released), defaulted to a 512 bit 799 DH parameter setting for client connections. To work around 800 this interoperability, sendmail can be configured to use a 801 2048 bit DH parameter by: 802 803 1. Edit /etc/mail/`hostname`.mc 804 2. If a setting for confDH_PARAMETERS does not exist or 805 exists and is set to a string beginning with '5', 806 replace it with '2'. 807 3. If a setting for confDH_PARAMETERS exists and is set to 808 a file path, create a new file with: 809 openssl dhparam -out /path/to/file 2048 810 4. Rebuild the .cf file: 811 cd /etc/mail/; make; make install 812 5. Restart sendmail: 813 cd /etc/mail/; make restart 814 815 A sendmail patch is coming, at which time this file will be 816 updated. 817 81820150604: 819 Generation of legacy formatted entries have been disabled by default 820 in pwd_mkdb(8), as all base system consumers of the legacy formatted 821 entries were converted to use the new format by default when the new, 822 machine independent format have been added and supported since FreeBSD 823 5.x. 824 825 Please see the pwd_mkdb(8) manual page for further details. 826 82720150525: 828 Clang and llvm have been upgraded to 3.6.1 release. Please see the 829 20141231 entry below for information about prerequisites and upgrading, 830 if you are not already using 3.5.0 or higher. 831 83220150521: 833 TI platform code switched to using vendor DTS files and this update 834 may break existing systems running on Beaglebone, Beaglebone Black, 835 and Pandaboard: 836 837 - dtb files should be regenerated/reinstalled. Filenames are the 838 same but content is different now 839 - GPIO addressing was changed, now each GPIO bank (32 pins per bank) 840 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old 841 addressing scheme is now pin 25 on /dev/gpioc3. 842 - Pandaboard: /etc/ttys should be updated, serial console device is 843 now /dev/ttyu2, not /dev/ttyu0 844 84520150501: 846 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim. 847 If you need the GNU extension from groff soelim(1), install groff 848 from package: pkg install groff, or via ports: textproc/groff. 849 85020150423: 851 chmod, chflags, chown and chgrp now affect symlinks in -R mode as 852 defined in symlink(7); previously symlinks were silently ignored. 853 85420150415: 855 The const qualifier has been removed from iconv(3) to comply with 856 POSIX. The ports tree is aware of this from r384038 onwards. 857 85820150416: 859 Libraries specified by LIBADD in Makefiles must have a corresponding 860 DPADD_<lib> variable to ensure correct dependencies. This is now 861 enforced in src.libnames.mk. 862 86320150324: 864 From legacy ata(4) driver was removed support for SATA controllers 865 supported by more functional drivers ahci(4), siis(4) and mvs(4). 866 Kernel modules ataahci and ataadaptec were removed completely, 867 replaced by ahci and mvs modules respectively. 868 86920150315: 870 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see 871 the 20141231 entry below for information about prerequisites and 872 upgrading, if you are not already using 3.5.0 or higher. 873 87420150307: 875 The 32-bit PowerPC kernel has been changed to a position-independent 876 executable. This can only be booted with a version of loader(8) 877 newer than January 31, 2015, so make sure to update both world and 878 kernel before rebooting. 879 88020150217: 881 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014), 882 but before r278950, the RNG was not seeded properly. Immediately 883 upgrade the kernel to r278950 or later and regenerate any keys (e.g. 884 ssh keys or openssl keys) that were generated w/ a kernel from that 885 range. This does not affect programs that directly used /dev/random 886 or /dev/urandom. All userland uses of arc4random(3) are affected. 887 88820150210: 889 The autofs(4) ABI was changed in order to restore binary compatibility 890 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work 891 with the new kernel. 892 89320150131: 894 The powerpc64 kernel has been changed to a position-independent 895 executable. This can only be booted with a new version of loader(8), 896 so make sure to update both world and kernel before rebooting. 897 89820150118: 899 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix 900 only release, no new features have been added. Please see the 20141231 901 entry below for information about prerequisites and upgrading, if you 902 are not already using 3.5.0. 903 90420150107: 905 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now 906 taken from the ELF Tool Chain project rather than GNU binutils. They 907 should be drop-in replacements, with the addition of arm64 support. 908 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the 909 binutils tools, if necessary. See 20150805 for updated information. 910 91120150105: 912 The default Unbound configuration now enables remote control 913 using a local socket. Users who have already enabled the 914 local_unbound service should regenerate their configuration 915 by running "service local_unbound setup" as root. 916 91720150102: 918 The GNU texinfo and GNU info pages have been removed. 919 To be able to view GNU info pages please install texinfo from ports. 920 92120141231: 922 Clang, llvm and lldb have been upgraded to 3.5.0 release. 923 924 As of this release, a prerequisite for building clang, llvm and lldb is 925 a C++11 capable compiler and C++11 standard library. This means that to 926 be able to successfully build the cross-tools stage of buildworld, with 927 clang as the bootstrap compiler, your system compiler or cross compiler 928 should either be clang 3.3 or later, or gcc 4.8 or later, and your 929 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or 930 later. 931 932 On any standard FreeBSD 10.x or 11.x installation, where clang and 933 libc++ are on by default (that is, on x86 or arm), this should work out 934 of the box. 935 936 On 9.x installations where clang is enabled by default, e.g. on x86 and 937 powerpc, libc++ will not be enabled by default, so libc++ should be 938 built (with clang) and installed first. If both clang and libc++ are 939 missing, build clang first, then use it to build libc++. 940 941 On 8.x and earlier installations, upgrade to 9.x first, and then follow 942 the instructions for 9.x above. 943 944 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by 945 default, and do not build clang. 946 947 Many embedded systems are resource constrained, and will not be able to 948 build clang in a reasonable time, or in some cases at all. In those 949 cases, cross building bootable systems on amd64 is a workaround. 950 951 This new version of clang introduces a number of new warnings, of which 952 the following are most likely to appear: 953 954 -Wabsolute-value 955 956 This warns in two cases, for both C and C++: 957 * When the code is trying to take the absolute value of an unsigned 958 quantity, which is effectively a no-op, and almost never what was 959 intended. The code should be fixed, if at all possible. If you are 960 sure that the unsigned quantity can be safely cast to signed, without 961 loss of information or undefined behavior, you can add an explicit 962 cast, or disable the warning. 963 964 * When the code is trying to take an absolute value, but the called 965 abs() variant is for the wrong type, which can lead to truncation. 966 If you want to disable the warning instead of fixing the code, please 967 make sure that truncation will not occur, or it might lead to unwanted 968 side-effects. 969 970 -Wtautological-undefined-compare and 971 -Wundefined-bool-conversion 972 973 These warn when C++ code is trying to compare 'this' against NULL, while 974 'this' should never be NULL in well-defined C++ code. However, there is 975 some legacy (pre C++11) code out there, which actively abuses this 976 feature, which was less strictly defined in previous C++ versions. 977 978 Squid and openjdk do this, for example. The warning can be turned off 979 for C++98 and earlier, but compiling the code in C++11 mode might result 980 in unexpected behavior; for example, the parts of the program that are 981 unreachable could be optimized away. 982 98320141222: 984 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER) 985 kernel sources have been removed. The .h files remain, since some 986 utilities include them. This will need to be fixed later. 987 If "mount -t oldnfs ..." is attempted, it will fail. 988 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used, 989 the utilities will report errors. 990 99120141121: 992 The handling of LOCAL_LIB_DIRS has been altered to skip addition of 993 directories to top level SUBDIR variable when their parent 994 directory is included in LOCAL_DIRS. Users with build systems with 995 such hierarchies and without SUBDIR entries in the parent 996 directory Makefiles should add them or add the directories to 997 LOCAL_DIRS. 998 99920141109: 1000 faith(4) and faithd(8) have been removed from the base system. Faith 1001 has been obsolete for a very long time. 1002 100320141104: 1004 vt(4), the new console driver, is enabled by default. It brings 1005 support for Unicode and double-width characters, as well as 1006 support for UEFI and integration with the KMS kernel video 1007 drivers. 1008 1009 You may need to update your console settings in /etc/rc.conf, 1010 most probably the keymap. During boot, /etc/rc.d/syscons will 1011 indicate what you need to do. 1012 1013 vt(4) still has issues and lacks some features compared to 1014 syscons(4). See the wiki for up-to-date information: 1015 https://wiki.freebsd.org/Newcons 1016 1017 If you want to keep using syscons(4), you can do so by adding 1018 the following line to /boot/loader.conf: 1019 kern.vty=sc 1020 102120141102: 1022 pjdfstest has been integrated into kyua as an opt-in test suite. 1023 Please see share/doc/pjdfstest/README for more details on how to 1024 execute it. 1025 102620141009: 1027 gperf has been removed from the base system for architectures 1028 that use clang. Ports that require gperf will obtain it from the 1029 devel/gperf port. 1030 103120140923: 1032 pjdfstest has been moved from tools/regression/pjdfstest to 1033 contrib/pjdfstest . 1034 103520140922: 1036 At svn r271982, The default linux compat kernel ABI has been adjusted 1037 to 2.6.18 in support of the linux-c6 compat ports infrastructure 1038 update. If you wish to continue using the linux-f10 compat ports, 1039 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are 1040 encouraged to update their linux-compat packages to linux-c6 during 1041 their next update cycle. 1042 104320140729: 1044 The ofwfb driver, used to provide a graphics console on PowerPC when 1045 using vt(4), no longer allows mmap() of all physical memory. This 1046 will prevent Xorg on PowerPC with some ATI graphics cards from 1047 initializing properly unless x11-servers/xorg-server is updated to 1048 1.12.4_8 or newer. 1049 105020140723: 1051 The xdev targets have been converted to using TARGET and 1052 TARGET_ARCH instead of XDEV and XDEV_ARCH. 1053 105420140719: 1055 The default unbound configuration has been modified to address 1056 issues with reverse lookups on networks that use private 1057 address ranges. If you use the local_unbound service, run 1058 "service local_unbound setup" as root to regenerate your 1059 configuration, then "service local_unbound reload" to load the 1060 new configuration. 1061 106220140709: 1063 The GNU texinfo and GNU info pages are not built and installed 1064 anymore, WITH_INFO knob has been added to allow to built and install 1065 them again. 1066 UPDATE: see 20150102 entry on texinfo's removal 1067 106820140708: 1069 The GNU readline library is now an INTERNALLIB - that is, it is 1070 statically linked into consumers (GDB and variants) in the base 1071 system, and the shared library is no longer installed. The 1072 devel/readline port is available for third party software that 1073 requires readline. 1074 107520140702: 1076 The Itanium architecture (ia64) has been removed from the list of 1077 known architectures. This is the first step in the removal of the 1078 architecture. 1079 108020140701: 1081 Commit r268115 has added NFSv4.1 server support, merged from 1082 projects/nfsv4.1-server. Since this includes changes to the 1083 internal interfaces between the NFS related modules, a full 1084 build of the kernel and modules will be necessary. 1085 __FreeBSD_version has been bumped. 1086 108720140629: 1088 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 1089 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 1090 which differs from the behaviour controlled by this knob.) 1091 109220140619: 1093 Maximal length of the serial number in CTL was increased from 16 to 1094 64 chars, that breaks ABI. All CTL-related tools, such as ctladm 1095 and ctld, need to be rebuilt to work with a new kernel. 1096 109720140606: 1098 The libatf-c and libatf-c++ major versions were downgraded to 0 and 1099 1 respectively to match the upstream numbers. They were out of 1100 sync because, when they were originally added to FreeBSD, the 1101 upstream versions were not respected. These libraries are private 1102 and not yet built by default, so renumbering them should be a 1103 non-issue. However, unclean source trees will yield broken test 1104 programs once the operator executes "make delete-old-libs" after a 1105 "make installworld". 1106 1107 Additionally, the atf-sh binary was made private by moving it into 1108 /usr/libexec/. Already-built shell test programs will keep the 1109 path to the old binary so they will break after "make delete-old" 1110 is run. 1111 1112 If you are using WITH_TESTS=yes (not the default), wipe the object 1113 tree and rebuild from scratch to prevent spurious test failures. 1114 This is only needed once: the misnumbered libraries and misplaced 1115 binaries have been added to OptionalObsoleteFiles.inc so they will 1116 be removed during a clean upgrade. 1117 111820140512: 1119 Clang and llvm have been upgraded to 3.4.1 release. 1120 112120140508: 1122 We bogusly installed src.opts.mk in /usr/share/mk. This file should 1123 be removed to avoid issues in the future (and has been added to 1124 ObsoleteFiles.inc). 1125 112620140505: 1127 /etc/src.conf now affects only builds of the FreeBSD src tree. In the 1128 past, it affected all builds that used the bsd.*.mk files. The old 1129 behavior was a bug, but people may have relied upon it. To get this 1130 behavior back, you can .include /etc/src.conf from /etc/make.conf 1131 (which is still global and isn't changed). This also changes the 1132 behavior of incremental builds inside the tree of individual 1133 directories. Set MAKESYSPATH to ".../share/mk" to do that. 1134 Although this has survived make universe and some upgrade scenarios, 1135 other upgrade scenarios may have broken. At least one form of 1136 temporary breakage was fixed with MAKESYSPATH settings for buildworld 1137 as well... In cases where MAKESYSPATH isn't working with this 1138 setting, you'll need to set it to the full path to your tree. 1139 1140 One side effect of all this cleaning up is that bsd.compiler.mk 1141 is no longer implicitly included by bsd.own.mk. If you wish to 1142 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk 1143 as well. 1144 114520140430: 1146 The lindev device has been removed since /dev/full has been made a 1147 standard device. __FreeBSD_version has been bumped. 1148 114920140424: 1150 The knob WITHOUT_VI was added to the base system, which controls 1151 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1) 1152 in order to reorder files share/termcap and didn't build ex(1) as a 1153 build tool, so building/installing with WITH_VI is highly advised for 1154 build hosts for older releases. 1155 1156 This issue has been fixed in stable/9 and stable/10 in r277022 and 1157 r276991, respectively. 1158 115920140418: 1160 The YES_HESIOD knob has been removed. It has been obsolete for 1161 a decade. Please move to using WITH_HESIOD instead or your builds 1162 will silently lack HESIOD. 1163 116420140405: 1165 The uart(4) driver has been changed with respect to its handling 1166 of the low-level console. Previously the uart(4) driver prevented 1167 any process from changing the baudrate or the CLOCAL and HUPCL 1168 control flags. By removing the restrictions, operators can make 1169 changes to the serial console port without having to reboot. 1170 However, when getty(8) is started on the serial device that is 1171 associated with the low-level console, a misconfigured terminal 1172 line in /etc/ttys will now have a real impact. 1173 Before upgrading the kernel, make sure that /etc/ttys has the 1174 serial console device configured as 3wire without baudrate to 1175 preserve the previous behaviour. E.g: 1176 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure 1177 117820140306: 1179 Support for libwrap (TCP wrappers) in rpcbind was disabled by default 1180 to improve performance. To re-enable it, if needed, run rpcbind 1181 with command line option -W. 1182 118320140226: 1184 Switched back to the GPL dtc compiler due to updates in the upstream 1185 dts files not being supported by the BSDL dtc compiler. You will need 1186 to rebuild your kernel toolchain to pick up the new compiler. Core dumps 1187 may result while building dtb files during a kernel build if you fail 1188 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler. 1189 119020140216: 1191 Clang and llvm have been upgraded to 3.4 release. 1192 119320140216: 1194 The nve(4) driver has been removed. Please use the nfe(4) driver 1195 for NVIDIA nForce MCP Ethernet adapters instead. 1196 119720140212: 1198 An ABI incompatibility crept into the libc++ 3.4 import in r261283. 1199 This could cause certain C++ applications using shared libraries built 1200 against the previous version of libc++ to crash. The incompatibility 1201 has now been fixed, but any C++ applications or shared libraries built 1202 between r261283 and r261801 should be recompiled. 1203 120420140204: 1205 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 1206 capability mode support. Please note that enabling the feature in 1207 kernel is still highly recommended. 1208 120920140131: 1210 OpenSSH is now built with sandbox support, and will use sandbox as 1211 the default privilege separation method. This requires Capsicum 1212 capability mode support in kernel. 1213 121420140128: 1215 The libelf and libdwarf libraries have been updated to newer 1216 versions from upstream. Shared library version numbers for 1217 these two libraries were bumped. Any ports or binaries 1218 requiring these two libraries should be recompiled. 1219 __FreeBSD_version is bumped to 1100006. 1220 122120140110: 1222 If a Makefile in a tests/ directory was auto-generating a Kyuafile 1223 instead of providing an explicit one, this would prevent such 1224 Makefile from providing its own Kyuafile in the future during 1225 NO_CLEAN builds. This has been fixed in the Makefiles but manual 1226 intervention is needed to clean an objdir if you use NO_CLEAN: 1227 # find /usr/obj -name Kyuafile | xargs rm -f 1228 122920131213: 1230 The behavior of gss_pseudo_random() for the krb5 mechanism 1231 has changed, for applications requesting a longer random string 1232 than produced by the underlying enctype's pseudo-random() function. 1233 In particular, the random string produced from a session key of 1234 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 1235 be different at the 17th octet and later, after this change. 1236 The counter used in the PRF+ construction is now encoded as a 1237 big-endian integer in accordance with RFC 4402. 1238 __FreeBSD_version is bumped to 1100004. 1239 124020131108: 1241 The WITHOUT_ATF build knob has been removed and its functionality 1242 has been subsumed into the more generic WITHOUT_TESTS. If you were 1243 using the former to disable the build of the ATF libraries, you 1244 should change your settings to use the latter. 1245 124620131025: 1247 The default version of mtree is nmtree which is obtained from 1248 NetBSD. The output is generally the same, but may vary 1249 slightly. If you found you need identical output adding 1250 "-F freebsd9" to the command line should do the trick. For the 1251 time being, the old mtree is available as fmtree. 1252 125320131014: 1254 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 1255 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 1256 1.1.4_8 and verify bsdyml not linked in, before running "make 1257 delete-old-libs": 1258 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 1259 or 1260 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 1261 126220131010: 1263 The stable/10 branch has been created in subversion from head 1264 revision r256279. 1265 126620131010: 1267 The rc.d/jail script has been updated to support jail(8) 1268 configuration file. The "jail_<jname>_*" rc.conf(5) variables 1269 for per-jail configuration are automatically converted to 1270 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 1271 This is transparently backward compatible. See below about some 1272 incompatibilities and rc.conf(5) manual page for more details. 1273 1274 These variables are now deprecated in favor of jail(8) configuration 1275 file. One can use "rc.d/jail config <jname>" command to generate 1276 a jail(8) configuration file in /var/run/jail.<jname>.conf without 1277 running the jail(8) utility. The default pathname of the 1278 configuration file is /etc/jail.conf and can be specified by 1279 using $jail_conf or $jail_<jname>_conf variables. 1280 1281 Please note that jail_devfs_ruleset accepts an integer at 1282 this moment. Please consider to rewrite the ruleset name 1283 with an integer. 1284 128520130930: 1286 BIND has been removed from the base system. If all you need 1287 is a local resolver, simply enable and start the local_unbound 1288 service instead. Otherwise, several versions of BIND are 1289 available in the ports tree. The dns/bind99 port is one example. 1290 1291 With this change, nslookup(1) and dig(1) are no longer in the base 1292 system. Users should instead use host(1) and drill(1) which are 1293 in the base system. Alternatively, nslookup and dig can 1294 be obtained by installing the dns/bind-tools port. 1295 129620130916: 1297 With the addition of unbound(8), a new unbound user is now 1298 required during installworld. "mergemaster -p" can be used to 1299 add the user prior to installworld, as documented in the handbook. 1300 130120130911: 1302 OpenSSH is now built with DNSSEC support, and will by default 1303 silently trust signed SSHFP records. This can be controlled with 1304 the VerifyHostKeyDNS client configuration setting. DNSSEC support 1305 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 1306 130720130906: 1308 The GNU Compiler Collection and C++ standard library (libstdc++) 1309 are no longer built by default on platforms where clang is the system 1310 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 1311 options in src.conf. 1312 131320130905: 1314 The PROCDESC kernel option is now part of the GENERIC kernel 1315 configuration and is required for the rwhod(8) to work. 1316 If you are using custom kernel configuration, you should include 1317 'options PROCDESC'. 1318 131920130905: 1320 The API and ABI related to the Capsicum framework was modified 1321 in backward incompatible way. The userland libraries and programs 1322 have to be recompiled to work with the new kernel. This includes the 1323 following libraries and programs, but the whole buildworld is 1324 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 1325 kdump, procstat, rwho, rwhod, uniq. 1326 132720130903: 1328 AES-NI intrinsic support has been added to gcc. The AES-NI module 1329 has been updated to use this support. A new gcc is required to build 1330 the aesni module on both i386 and amd64. 1331 133220130821: 1333 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 1334 Thus "device padlock_rng" and "device rdrand_rng" should be 1335 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 1336 133720130813: 1338 WITH_ICONV has been split into two feature sets. WITH_ICONV now 1339 enables just the iconv* functionality and is now on by default. 1340 WITH_LIBICONV_COMPAT enables the libiconv api and link time 1341 compatibility. Set WITHOUT_ICONV to build the old way. 1342 If you have been using WITH_ICONV before, you will very likely 1343 need to turn on WITH_LIBICONV_COMPAT. 1344 134520130806: 1346 INVARIANTS option now enables DEBUG for code with OpenSolaris and 1347 Illumos origin, including ZFS. If you have INVARIANTS in your 1348 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 1349 explicitly. 1350 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 1351 locks if WITNESS option was set. Because that generated a lot of 1352 witness(9) reports and all of them were believed to be false 1353 positives, this is no longer done. New option OPENSOLARIS_WITNESS 1354 can be used to achieve the previous behavior. 1355 135620130806: 1357 Timer values in IPv6 data structures now use time_uptime instead 1358 of time_second. Although this is not a user-visible functional 1359 change, userland utilities which directly use them---ndp(8), 1360 rtadvd(8), and rtsold(8) in the base system---need to be updated 1361 to r253970 or later. 1362 136320130802: 1364 find -delete can now delete the pathnames given as arguments, 1365 instead of only files found below them or if the pathname did 1366 not contain any slashes. Formerly, the following error message 1367 would result: 1368 1369 find: -delete: <path>: relative path potentially not safe 1370 1371 Deleting the pathnames given as arguments can be prevented 1372 without error messages using -mindepth 1 or by changing 1373 directory and passing "." as argument to find. This works in the 1374 old as well as the new version of find. 1375 137620130726: 1377 Behavior of devfs rules path matching has been changed. 1378 Pattern is now always matched against fully qualified devfs 1379 path and slash characters must be explicitly matched by 1380 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 1381 subdirectories must be reviewed. 1382 138320130716: 1384 The default ARM ABI has changed to the ARM EABI. The old ABI is 1385 incompatible with the ARM EABI and all programs and modules will 1386 need to be rebuilt to work with a new kernel. 1387 1388 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 1389 1390 NOTE: Support for the old ABI will be removed in the future and 1391 users are advised to upgrade. 1392 139320130709: 1394 pkg_install has been disconnected from the build if you really need it 1395 you should add WITH_PKGTOOLS in your src.conf(5). 1396 139720130709: 1398 Most of network statistics structures were changed to be able 1399 keep 64-bits counters. Thus all tools, that work with networking 1400 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 1401 140220130618: 1403 Fix a bug that allowed a tracing process (e.g. gdb) to write 1404 to a memory-mapped file in the traced process's address space 1405 even if neither the traced process nor the tracing process had 1406 write access to that file. 1407 140820130615: 1409 CVS has been removed from the base system. An exact copy 1410 of the code is available from the devel/cvs port. 1411 141220130613: 1413 Some people report the following error after the switch to bmake: 1414 1415 make: illegal option -- J 1416 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 1417 ... 1418 *** [buildworld] Error code 2 1419 1420 this likely due to an old instance of make in 1421 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 1422 which src/Makefile will use that blindly, if it exists, so if 1423 you see the above error: 1424 1425 rm -rf `make -V MAKEPATH` 1426 1427 should resolve it. 1428 142920130516: 1430 Use bmake by default. 1431 Whereas before one could choose to build with bmake via 1432 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 1433 make. The goal is to remove these knobs for 10-RELEASE. 1434 1435 It is worth noting that bmake (like gmake) treats the command 1436 line as the unit of failure, rather than statements within the 1437 command line. Thus '(cd some/where && dosomething)' is safer 1438 than 'cd some/where; dosomething'. The '()' allows consistent 1439 behavior in parallel build. 1440 144120130429: 1442 Fix a bug that allows NFS clients to issue READDIR on files. 1443 144420130426: 1445 The WITHOUT_IDEA option has been removed because 1446 the IDEA patent expired. 1447 144820130426: 1449 The sysctl which controls TRIM support under ZFS has been renamed 1450 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 1451 enabled by default. 1452 145320130425: 1454 The mergemaster command now uses the default MAKEOBJDIRPREFIX 1455 rather than creating it's own in the temporary directory in 1456 order allow access to bootstrapped versions of tools such as 1457 install and mtree. When upgrading from version of FreeBSD where 1458 the install command does not support -l, you will need to 1459 install a new mergemaster command if mergemaster -p is required. 1460 This can be accomplished with the command (cd src/usr.sbin/mergemaster 1461 && make install). 1462 146320130404: 1464 Legacy ATA stack, disabled and replaced by new CAM-based one since 1465 FreeBSD 9.0, completely removed from the sources. Kernel modules 1466 atadisk and atapi*, user-level tools atacontrol and burncd are 1467 removed. Kernel option `options ATA_CAM` is now permanently enabled 1468 and removed. 1469 147020130319: 1471 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 1472 and socketpair(2). Software, in particular Kerberos, may 1473 automatically detect and use these during building. The resulting 1474 binaries will not work on older kernels. 1475 147620130308: 1477 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 1478 information, see the respective 20130304 entry). 1479 148020130304: 1481 Recent commits to callout(9) changed the size of struct callout, 1482 so the KBI is probably heavily disturbed. Also, some functions 1483 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 1484 by macros. Every kernel module using it won't load, so rebuild 1485 is requested. 1486 1487 The ctl device has been re-enabled in GENERIC for i386 and amd64, 1488 but does not initialize by default (because of the new CTL_DISABLE 1489 option) to save memory. To re-enable it, remove the CTL_DISABLE 1490 option from the kernel config file or set kern.cam.ctl.disable=0 1491 in /boot/loader.conf. 1492 149320130301: 1494 The ctl device has been disabled in GENERIC for i386 and amd64. 1495 This was done due to the extra memory being allocated at system 1496 initialisation time by the ctl driver which was only used if 1497 a CAM target device was created. This makes a FreeBSD system 1498 unusable on 128MB or less of RAM. 1499 150020130208: 1501 A new compression method (lz4) has been merged to -HEAD. Please 1502 refer to zpool-features(7) for more information. 1503 1504 Please refer to the "ZFS notes" section of this file for information 1505 on upgrading boot ZFS pools. 1506 150720130129: 1508 A BSD-licensed patch(1) variant has been added and is installed 1509 as bsdpatch, being the GNU version the default patch. 1510 To inverse the logic and use the BSD-licensed one as default, 1511 while having the GNU version installed as gnupatch, rebuild 1512 and install world with the WITH_BSD_PATCH knob set. 1513 151420130121: 1515 Due to the use of the new -l option to install(1) during build 1516 and install, you must take care not to directly set the INSTALL 1517 make variable in your /etc/make.conf, /etc/src.conf, or on the 1518 command line. If you wish to use the -C flag for all installs 1519 you may be able to add INSTALL+=-C to /etc/make.conf or 1520 /etc/src.conf. 1521 152220130118: 1523 The install(1) option -M has changed meaning and now takes an 1524 argument that is a file or path to append logs to. In the 1525 unlikely event that -M was the last option on the command line 1526 and the command line contained at least two files and a target 1527 directory the first file will have logs appended to it. The -M 1528 option served little practical purpose in the last decade so its 1529 use is expected to be extremely rare. 1530 153120121223: 1532 After switching to Clang as the default compiler some users of ZFS 1533 on i386 systems started to experience stack overflow kernel panics. 1534 Please consider using 'options KSTACK_PAGES=4' in such configurations. 1535 153620121222: 1537 GEOM_LABEL now mangles label names read from file system metadata. 1538 Mangling affect labels containing spaces, non-printable characters, 1539 '%' or '"'. Device names in /etc/fstab and other places may need to 1540 be updated. 1541 154220121217: 1543 By default, only the 10 most recent kernel dumps will be saved. To 1544 restore the previous behaviour (no limit on the number of kernel dumps 1545 stored in the dump directory) add the following line to /etc/rc.conf: 1546 1547 savecore_flags="" 1548 154920121201: 1550 With the addition of auditdistd(8), a new auditdistd user is now 1551 required during installworld. "mergemaster -p" can be used to 1552 add the user prior to installworld, as documented in the handbook. 1553 155420121117: 1555 The sin6_scope_id member variable in struct sockaddr_in6 is now 1556 filled by the kernel before passing the structure to the userland via 1557 sysctl or routing socket. This means the KAME-specific embedded scope 1558 id in sin6_addr.s6_addr[2] is always cleared in userland application. 1559 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 1560 __FreeBSD_version is bumped to 1000025. 1561 156220121105: 1563 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 1564 This means that the world and kernel will be compiled with clang 1565 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 1566 and /usr/bin/cpp. To disable this behavior and revert to building 1567 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 1568 of current may need to bootstrap WITHOUT_CLANG first if the clang 1569 build fails (its compatibility window doesn't extend to the 9 stable 1570 branch point). 1571 157220121102: 1573 The IPFIREWALL_FORWARD kernel option has been removed. Its 1574 functionality now turned on by default. 1575 157620121023: 1577 The ZERO_COPY_SOCKET kernel option has been removed and 1578 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 1579 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 1580 mechanism which is not safe and may result in kernel crashes. 1581 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 1582 driver supports disposeable external page sized mbuf storage. 1583 Proper replacements for both zero-copy mechanisms are under 1584 consideration and will eventually lead to complete removal 1585 of the two kernel options. 1586 158720121023: 1588 The IPv4 network stack has been converted to network byte 1589 order. The following modules need to be recompiled together 1590 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 1591 pf(4), ipfw(4), ng_ipfw(4), stf(4). 1592 159320121022: 1594 Support for non-MPSAFE filesystems was removed from VFS. The 1595 VFS_VERSION was bumped, all filesystem modules shall be 1596 recompiled. 1597 159820121018: 1599 All the non-MPSAFE filesystems have been disconnected from 1600 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 1601 portalfs, smbfs, xfs. 1602 160320121016: 1604 The interface cloning API and ABI has changed. The following 1605 modules need to be recompiled together with kernel: 1606 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 1607 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 1608 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 1609 161020121015: 1611 The sdhci driver was split in two parts: sdhci (generic SD Host 1612 Controller logic) and sdhci_pci (actual hardware driver). 1613 No kernel config modifications are required, but if you 1614 load sdhc as a module you must switch to sdhci_pci instead. 1615 161620121014: 1617 Import the FUSE kernel and userland support into base system. 1618 161920121013: 1620 The GNU sort(1) program has been removed since the BSD-licensed 1621 sort(1) has been the default for quite some time and no serious 1622 problems have been reported. The corresponding WITH_GNU_SORT 1623 knob has also gone. 1624 162520121006: 1626 The pfil(9) API/ABI for AF_INET family has been changed. Packet 1627 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 1628 with new kernel. 1629 163020121001: 1631 The net80211(4) ABI has been changed to allow for improved driver 1632 PS-POLL and power-save support. All wireless drivers need to be 1633 recompiled to work with the new kernel. 1634 163520120913: 1636 The random(4) support for the VIA hardware random number 1637 generator (`PADLOCK') is no longer enabled unconditionally. 1638 Add the padlock_rng device in the custom kernel config if 1639 needed. The GENERIC kernels on i386 and amd64 do include the 1640 device, so the change only affects the custom kernel 1641 configurations. 1642 164320120908: 1644 The pf(4) packet filter ABI has been changed. pfctl(8) and 1645 snmp_pf module need to be recompiled to work with new kernel. 1646 164720120828: 1648 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 1649 to -HEAD. Pools that have empty_bpobj in active state can not be 1650 imported read-write with ZFS implementations that do not support 1651 this feature. For more information read the zpool-features(5) 1652 manual page. 1653 165420120727: 1655 The sparc64 ZFS loader has been changed to no longer try to auto- 1656 detect ZFS providers based on diskN aliases but now requires these 1657 to be explicitly listed in the OFW boot-device environment variable. 1658 165920120712: 1660 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 1661 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 1662 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 1663 166420120712: 1665 The following sysctls and tunables have been renamed for consistency 1666 with other variables: 1667 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 1668 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 1669 167020120628: 1671 The sort utility has been replaced with BSD sort. For now, GNU sort 1672 is also available as "gnusort" or the default can be set back to 1673 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 1674 installed as "bsdsort". 1675 167620120611: 1677 A new version of ZFS (pool version 5000) has been merged to -HEAD. 1678 Starting with this version the old system of ZFS pool versioning 1679 is superseded by "feature flags". This concept enables forward 1680 compatibility against certain future changes in functionality of ZFS 1681 pools. The first read-only compatible "feature flag" for ZFS pools 1682 is named "com.delphix:async_destroy". For more information 1683 read the new zpool-features(5) manual page. 1684 Please refer to the "ZFS notes" section of this file for information 1685 on upgrading boot ZFS pools. 1686 168720120417: 1688 The malloc(3) implementation embedded in libc now uses sources imported 1689 as contrib/jemalloc. The most disruptive API change is to 1690 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 1691 delete it prior to installworld, and optionally re-create it using the 1692 new format after rebooting. See malloc.conf(5) for details 1693 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 1694 NAMESPACE section). 1695 169620120328: 1697 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 1698 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 1699 now spelled mips. This is to aid compatibility with third-party 1700 software that expects this naming scheme in uname(3). Little-endian 1701 settings are unchanged. If you are updating a big-endian mips64 machine 1702 from before this change, you may need to set MACHINE_ARCH=mips64 in 1703 your environment before the new build system will recognize your machine. 1704 170520120306: 1706 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 1707 platforms. 1708 170920120229: 1710 Now unix domain sockets behave "as expected" on nullfs(5). Previously 1711 nullfs(5) did not pass through all behaviours to the underlying layer, 1712 as a result if we bound to a socket on the lower layer we could connect 1713 only to the lower path; if we bound to the upper layer we could connect 1714 only to the upper path. The new behavior is one can connect to both the 1715 lower and the upper paths regardless what layer path one binds to. 1716 171720120211: 1718 The getifaddrs upgrade path broken with 20111215 has been restored. 1719 If you have upgraded in between 20111215 and 20120209 you need to 1720 recompile libc again with your kernel. You still need to recompile 1721 world to be able to configure CARP but this restriction already 1722 comes from 20111215. 1723 172420120114: 1725 The set_rcvar() function has been removed from /etc/rc.subr. All 1726 base and ports rc.d scripts have been updated, so if you have a 1727 port installed with a script in /usr/local/etc/rc.d you can either 1728 hand-edit the rcvar= line, or reinstall the port. 1729 1730 An easy way to handle the mass-update of /etc/rc.d: 1731 rm /etc/rc.d/* && mergemaster -i 1732 173320120109: 1734 panic(9) now stops other CPUs in the SMP systems, disables interrupts 1735 on the current CPU and prevents other threads from running. 1736 This behavior can be reverted using the kern.stop_scheduler_on_panic 1737 tunable/sysctl. 1738 The new behavior can be incompatible with kern.sync_on_panic. 1739 174020111215: 1741 The carp(4) facility has been changed significantly. Configuration 1742 of the CARP protocol via ifconfig(8) has changed, as well as format 1743 of CARP events submitted to devd(8) has changed. See manual pages 1744 for more information. The arpbalance feature of carp(4) is currently 1745 not supported anymore. 1746 1747 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 1748 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 1749 need to be recompiled. 1750 175120111122: 1752 The acpi_wmi(4) status device /dev/wmistat has been renamed to 1753 /dev/wmistat0. 1754 175520111108: 1756 The option VFS_ALLOW_NONMPSAFE option has been added in order to 1757 explicitely support non-MPSAFE filesystems. 1758 It is on by default for all supported platform at this present 1759 time. 1760 176120111101: 1762 The broken amd(4) driver has been replaced with esp(4) in the amd64, 1763 i386 and pc98 GENERIC kernel configuration files. 1764 176520110930: 1766 sysinstall has been removed 1767 176820110923: 1769 The stable/9 branch created in subversion. This corresponds to the 1770 RELENG_9 branch in CVS. 1771 1772COMMON ITEMS: 1773 1774 General Notes 1775 ------------- 1776 Avoid using make -j when upgrading. While generally safe, there are 1777 sometimes problems using -j to upgrade. If your upgrade fails with 1778 -j, please try again without -j. From time to time in the past there 1779 have been problems using -j with buildworld and/or installworld. This 1780 is especially true when upgrading between "distant" versions (eg one 1781 that cross a major release boundary or several minor releases, or when 1782 several months have passed on the -current branch). 1783 1784 Sometimes, obscure build problems are the result of environment 1785 poisoning. This can happen because the make utility reads its 1786 environment when searching for values for global variables. To run 1787 your build attempts in an "environmental clean room", prefix all make 1788 commands with 'env -i '. See the env(1) manual page for more details. 1789 1790 When upgrading from one major version to another it is generally best to 1791 upgrade to the latest code in the currently installed branch first, then 1792 do an upgrade to the new branch. This is the best-tested upgrade path, 1793 and has the highest probability of being successful. Please try this 1794 approach if you encounter problems with a major version upgrade. Since 1795 the stable 4.x branch point, one has generally been able to upgade from 1796 anywhere in the most recent stable branch to head / current (or even the 1797 last couple of stable branches). See the top of this file when there's 1798 an exception. 1799 1800 When upgrading a live system, having a root shell around before 1801 installing anything can help undo problems. Not having a root shell 1802 around can lead to problems if pam has changed too much from your 1803 starting point to allow continued authentication after the upgrade. 1804 1805 This file should be read as a log of events. When a later event changes 1806 information of a prior event, the prior event should not be deleted. 1807 Instead, a pointer to the entry with the new information should be 1808 placed in the old entry. Readers of this file should also sanity check 1809 older entries before relying on them blindly. Authors of new entries 1810 should write them with this in mind. 1811 1812 ZFS notes 1813 --------- 1814 When upgrading the boot ZFS pool to a new version, always follow 1815 these two steps: 1816 1817 1.) recompile and reinstall the ZFS boot loader and boot block 1818 (this is part of "make buildworld" and "make installworld") 1819 1820 2.) update the ZFS boot block on your boot drive 1821 1822 The following example updates the ZFS boot block on the first 1823 partition (freebsd-boot) of a GPT partitioned drive ada0: 1824 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0" 1825 1826 Non-boot pools do not need these updates. 1827 1828 To build a kernel 1829 ----------------- 1830 If you are updating from a prior version of FreeBSD (even one just 1831 a few days old), you should follow this procedure. It is the most 1832 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1833 1834 make kernel-toolchain 1835 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1836 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1837 1838 To test a kernel once 1839 --------------------- 1840 If you just want to boot a kernel once (because you are not sure 1841 if it works, or if you want to boot a known bad kernel to provide 1842 debugging information) run 1843 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1844 nextboot -k testkernel 1845 1846 To rebuild everything and install it on the current system. 1847 ----------------------------------------------------------- 1848 # Note: sometimes if you are running current you gotta do more than 1849 # is listed here if you are upgrading from a really old current. 1850 1851 <make sure you have good level 0 dumps> 1852 make buildworld 1853 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1854 make installkernel KERNCONF=YOUR_KERNEL_HERE 1855 [1] 1856 <reboot in single user> [3] 1857 mergemaster -Fp [5] 1858 make installworld 1859 mergemaster -Fi [4] 1860 make delete-old [6] 1861 <reboot> 1862 1863 To cross-install current onto a separate partition 1864 -------------------------------------------------- 1865 # In this approach we use a separate partition to hold 1866 # current's root, 'usr', and 'var' directories. A partition 1867 # holding "/", "/usr" and "/var" should be about 2GB in 1868 # size. 1869 1870 <make sure you have good level 0 dumps> 1871 <boot into -stable> 1872 make buildworld 1873 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1874 <maybe newfs current's root partition> 1875 <mount current's root partition on directory ${CURRENT_ROOT}> 1876 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 1877 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1878 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1879 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1880 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1881 <reboot into current> 1882 <do a "native" rebuild/install as described in the previous section> 1883 <maybe install compatibility libraries from ports/misc/compat*> 1884 <reboot> 1885 1886 1887 To upgrade in-place from stable to current 1888 ---------------------------------------------- 1889 <make sure you have good level 0 dumps> 1890 make buildworld [9] 1891 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1892 [1] 1893 <reboot in single user> [3] 1894 mergemaster -Fp [5] 1895 make installworld 1896 mergemaster -Fi [4] 1897 make delete-old [6] 1898 <reboot> 1899 1900 Make sure that you've read the UPDATING file to understand the 1901 tweaks to various things you need. At this point in the life 1902 cycle of current, things change often and you are on your own 1903 to cope. The defaults can also change, so please read ALL of 1904 the UPDATING entries. 1905 1906 Also, if you are tracking -current, you must be subscribed to 1907 freebsd-current@freebsd.org. Make sure that before you update 1908 your sources that you have read and understood all the recent 1909 messages there. If in doubt, please track -stable which has 1910 much fewer pitfalls. 1911 1912 [1] If you have third party modules, such as vmware, you 1913 should disable them at this point so they don't crash your 1914 system on reboot. 1915 1916 [3] From the bootblocks, boot -s, and then do 1917 fsck -p 1918 mount -u / 1919 mount -a 1920 cd src 1921 adjkerntz -i # if CMOS is wall time 1922 Also, when doing a major release upgrade, it is required that 1923 you boot into single user mode to do the installworld. 1924 1925 [4] Note: This step is non-optional. Failure to do this step 1926 can result in a significant reduction in the functionality of the 1927 system. Attempting to do it by hand is not recommended and those 1928 that pursue this avenue should read this file carefully, as well 1929 as the archives of freebsd-current and freebsd-hackers mailing lists 1930 for potential gotchas. The -U option is also useful to consider. 1931 See mergemaster(8) for more information. 1932 1933 [5] Usually this step is a noop. However, from time to time 1934 you may need to do this if you get unknown user in the following 1935 step. It never hurts to do it all the time. You may need to 1936 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1937 install) after the buildworld before this step if you last updated 1938 from current before 20130425 or from -stable before 20130430. 1939 1940 [6] This only deletes old files and directories. Old libraries 1941 can be deleted by "make delete-old-libs", but you have to make 1942 sure that no program is using those libraries anymore. 1943 1944 [8] In order to have a kernel that can run the 4.x binaries needed to 1945 do an installworld, you must include the COMPAT_FREEBSD4 option in 1946 your kernel. Failure to do so may leave you with a system that is 1947 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 1948 required to run the 5.x binaries on more recent kernels. And so on 1949 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 1950 1951 Make sure that you merge any new devices from GENERIC since the 1952 last time you updated your kernel config file. 1953 1954 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1955 "?=" instead of the "=" assignment operator, so that buildworld can 1956 override the CPUTYPE if it needs to. 1957 1958 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1959 not on the command line, or in /etc/make.conf. buildworld will 1960 warn if it is improperly defined. 1961FORMAT: 1962 1963This file contains a list, in reverse chronological order, of major 1964breakages in tracking -current. It is not guaranteed to be a complete 1965list of such breakages, and only contains entries since September 23, 2011. 1966If you need to see UPDATING entries from before that date, you will need 1967to fetch an UPDATING file from an older FreeBSD release. 1968 1969Copyright information: 1970 1971Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1972 1973Redistribution, publication, translation and use, with or without 1974modification, in full or in part, in any form or format of this 1975document are permitted without further permission from the author. 1976 1977THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1978IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1979WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1980DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1981INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1982(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1983SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1984HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1985STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1986IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1987POSSIBILITY OF SUCH DAMAGE. 1988 1989Contact Warner Losh if you have any questions about your use of 1990this document. 1991 1992$FreeBSD$ 1993