UPDATING revision 346296
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/makeworld.html 10 11Items affecting the ports and packages system can be found in 12/usr/ports/UPDATING. Please read that file before running portupgrade. 13 14NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping 15from older versions of FreeBSD, try WITHOUT_CLANG 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 1920190416: 20 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 21 8.0.0. Please see the 20141231 entry below for information about 22 prerequisites and upgrading, if you are not already using clang 3.5.0 23 or higher. 24 2520190226: 26 geom_uzip(4) depends on the new module xz. If geom_uzip is statically 27 compiled into your custom kernel, add 'device xz' statement to the 28 kernel config. 29 3020190220: 31 Co-existance for Forth and Lua interpreters in bootloaders has now been 32 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented 33 in build(7), may be used to control which interpreter flavor is used in 34 the default loader to be installed. For systems where Lua and Forth 35 coexist, this switch can also be made on a running system by creating a 36 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather 37 than requiring a rebuild. 38 39 The default flavor in this branch will remain Forth. As indicated in 40 the 20190216 UPDATING entry, booting is a complex environment; it would 41 be prudent to assume that lualoader may not work for your setup and make 42 provisions for backup boot methods. 43 4420190220: 45 zfsloader's functionality has now been folded into loader. 46 zfsloader is no longer necesasary once you've updated your 47 boot blocks. For a transition period, we will install a 48 hardlink for zfsloader to loader to allow a smooth transition 49 until the boot blocks can be updated (hard link because old 50 zfs boot blocks don't understand symlinks). 51 5220190216: 53 Lualoader has been merged to facilitate testing on this branch. It's 54 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in 55 /etc/src.conf, but co-existance will come shortly. Booting is a complex 56 environment and test coverage for Lua-enabled loaders has been thin, so 57 it would be prudent to assume it might not work and make provisions for 58 backup boot methods. 59 6020190216: 61 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 62 7.0.1. Please see the 20141231 entry below for information about 63 prerequisites and upgrading, if you are not already using clang 3.5.0 64 or higher. 65 6620181228: 67 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport 68 in the same as it is applied to NFSv2 and 3. This implies that NFSv4 69 servers that have vfs.nfsd.nfs_privport set will only allow mounts 70 from clients using a reserved port#. Since both the FreeBSD and Linux 71 NFSv4 clients use reserved port#s by default, this should not affect 72 most NFSv4 mounts. 73 7420181107: 75 The '%I' format in the kern.corefile sysctl limits the number of 76 core files that a process can generate to the number stored in the 77 debug.ncores sysctl. The '%I' format is replaced by the single digit 78 index. Previously, if all indexes were taken the kernel would overwrite 79 only a core file with the highest index in a filename. 80 Currently the system will create a new core file if there is a free 81 index or if all slots are taken it will overwrite the oldest one. 82 8320180818: 84 WITH_OFED option now only enables the build for the OFED libraries 85 and some fundamental client utilities. OpenSM and rest of the 86 debugging tools are enabled by WITH_OFED_EXTRA build switch. 87 WITH_OFED is turned on by default on amd64. 88 8920180714: 90 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 91 6.0.1. Please see the 20141231 entry below for information about 92 prerequisites and upgrading, if you are not already using clang 3.5.0 93 or higher. 94 9520180601: 96 The releng/11.2 branch has been created from stable/11@r334458. 97 9820180504: 99 The tz database (tzdb) has been updated to 2018e. This version more 100 correctly models time stamps in time zones with negative DST such as 101 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and 102 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only 103 time zone abbreviations and the tm_isdst flag. 104 10520180409: 106 The use of RSS hash from the network card aka flowid has been 107 disabled by default for lagg(4) as it's currently incompatible with 108 the lacp and loadbalance protocols. 109 110 This can be re-enabled by setting the following in loader.conf: 111 net.link.lagg.default_use_flowid="1" 112 11320180331: 114 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to 115 6.0.0. Please see the 20141231 entry below for information about 116 prerequisites and upgrading, if you are not already using clang 3.5.0 117 or higher. 118 11920180211: 120 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to 121 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed 122 to WITH/OUT_LOADER_GELI. 123 12420180210: 125 The geli password typed at boot is now hidden. To restore the previous 126 behavior, see geli(8) for configuration options. 127 128 The SW_WATCHDOG option is no longer necessary to enable the 129 hardclock-based software watchdog if no hardware watchdog is 130 configured. As before, SW_WATCHDOG will cause the software 131 watchdog to be enabled even if a hardware watchdog is configured. 132 13320180108: 134 lint(1) binaries and library are no longer built by default. To 135 enable building them, define WITH_LINT in src.conf. If you are using 136 a FreeBSD 12 or later system to build 11-stable, you may need to 137 install a lint(1) binary to use WITH_LINT. 138 13920171003: 140 When building multiple kernels using KERNCONF, non-existent KERNCONF 141 files will produce an error and buildkernel will fail. Previously 142 missing KERNCONF files silently failed giving no indication as to 143 why, only to subsequently discover during installkernel that the 144 desired kernel was never built in the first place. 145 14620170926: 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 15120170822: 152 Since the switch to GPT disk labels, fsck for UFS/FFS has been 153 unable to automatically find alternate superblocks. As of r322806, 154 the information needed to find alternate superblocks has been 155 moved to the end of the area reserved for the boot block. 156 Filesystems created with a newfs of this vintage or later 157 will create the recovery information. If you have a filesystem 158 created prior to this change and wish to have a recovery block 159 created for your filesystem, you can do so by running fsck in 160 forground mode (i.e., do not use the -p or -y options). As it 161 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS'' 162 to which you should answer yes. 163 16420170629: 165 The releng/11.1 branch has been created from stable/11@r320475. 166 16720170518: 168 arm64 builds now use the base system LLD 4.0.0 linker by default, 169 instead of requiring that the aarch64-binutils port or package be 170 installed. To continue using aarch64-binutils, set 171 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin . 172 17320170529: 174 The ctl.ko module no longer implements the iSCSI target frontend: 175 cfiscsi.ko does instead. 176 177 If building cfiscsi.ko as a kernel module, the module can be loaded 178 via one of the following methods: 179 - `cfiscsi_load="YES"` in loader.conf(5). 180 - Add `cfiscsi` to `$kld_list` in rc.conf(5). 181 - ctladm(8)/ctld(8), when compiled with iSCSI support 182 (`WITH_ISCSI=yes` in src.conf(5)) 183 184 Please see cfiscsi(4) for more details. 185 18620170511: 187 The mmcsd.ko module now additionally depends on geom_flashmap.ko. 188 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the 189 same source (previously, the dependency of mmcsd.ko on mmc.ko was 190 missing, but mmcsd.ko now will refuse to load if it is incompatible 191 with mmc.ko). 192 19320170414: 194 Binds and sends to the loopback addresses, IPv6 and IPv4, will now 195 use any explicitly assigned loopback address available in the jail 196 instead of using the first assigned address of the jail. 197 19820170413: 199 As of r316810 for ipfilter, keep frags is no longer assumed when 200 keep state is specified in a rule. r316810 aligns ipfilter with 201 documentation in man pages separating keep frags from keep state. 202 This allows keep state to specified without forcing keep frags 203 and allows keep frags to be specified independently of keep state. 204 To maintain previous behaviour, also specify keep frags with 205 keep state (as documented in ipf.conf.5). 206 20720170402: 208 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0. 209 Please see the 20141231 entry below for information about prerequisites 210 and upgrading, if you are not already using clang 3.5.0 or higher. 211 21220170323: 213 The code that provides support for ZFS .zfs/ directory functionality 214 has been reimplemented. It's not possible now to create a snapshot 215 by mkdir under .zfs/snapshot/. That should be the only user visible 216 change. 217 21820170319: 219 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT 220 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of 221 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed, 222 and now NAT-T is supported by default. Security associations now use 223 the single namespace for SPI allocation, so if you use several manually 224 configured security associations with the same SPI, this configuration 225 needs modification. 226 22720161217: 228 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1. 229 Please see the 20141231 entry below for information about prerequisites 230 and upgrading, if you are not already using clang 3.5.0 or higher. 231 23220161124: 233 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0. 234 Please see the 20141231 entry below for information about prerequisites 235 and upgrading, if you are not already using clang 3.5.0 or higher. 236 23720161119: 238 The layout of the pmap structure has changed for powerpc to put the pmap 239 statistics at the front for all CPU variations. libkvm(3) and all tools 240 that link against it need to be recompiled. 241 24220161030: 243 isl(4) and cyapa(4) drivers now require a new driver, 244 chromebook_platform(4), to work properly on Chromebook-class hardware. 245 On other types of hardware the drivers may need to be configured using 246 device hints. Please see the corresponding manual pages for details. 247 24820161210: 249 Relocatable object files with the extension of .So have been renamed 250 to use an extension of .pico instead. The purpose of this change is 251 to avoid a name clash with shared libraries on case-insensitive file 252 systems. On those file systems, foo.So is the same file as foo.so. 253 25420160811: 255 The releng/11.0 branch has been created from stable/11@r303970. 256 25720160708: 258 The stable/11 branch has been created from head@r302406. 259 26020160622: 261 The libc stub for the pipe(2) system call has been replaced with 262 a wrapper that calls the pipe2(2) system call and the pipe(2) 263 system call is now only implemented by the kernels that include 264 "options COMPAT_FREEBSD10" in their config file (this is the 265 default). Users should ensure that this option is enabled in 266 their kernel or upgrade userspace to r302092 before upgrading their 267 kernel. 268 26920160527: 270 CAM will now strip leading spaces from SCSI disks' serial numbers. 271 This will effect users who create UFS filesystems on SCSI disks using 272 those disk's diskid device nodes. For example, if /etc/fstab 273 previously contained a line like 274 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should 275 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom 276 transforms like gmirror may also be affected. ZFS users should 277 generally be fine. 278 27920160523: 280 The bitstring(3) API has been updated with new functionality and 281 improved performance. But it is binary-incompatible with the old API. 282 Objects built with the new headers may not be linked against objects 283 built with the old headers. 284 28520160520: 286 The brk and sbrk functions have been removed from libc on arm64. 287 Binutils from ports has been updated to not link to these 288 functions and should be updated to the latest version before 289 installing a new libc. 290 29120160517: 292 The armv6 port now defaults to hard float ABI. Limited support 293 for running both hardfloat and soft float on the same system 294 is available using the libraries installed with -DWITH_LIBSOFT. 295 This has only been tested as an upgrade path for installworld 296 and packages may fail or need manual intervention to run. New 297 packages will be needed. 298 299 To update an existing self-hosted armv6hf system, you must add 300 TARGET_ARCH=armv6 on the make command line for both the build 301 and the install steps. 302 30320160510: 304 Kernel modules compiled outside of a kernel build now default to 305 installing to /boot/modules instead of /boot/kernel. Many kernel 306 modules built this way (such as those in ports) already overrode 307 KMODDIR explicitly to install into /boot/modules. However, 308 manually building and installing a module from /sys/modules will 309 now install to /boot/modules instead of /boot/kernel. 310 31120160414: 312 The CAM I/O scheduler has been committed to the kernel. There should be 313 no user visible impact. This does enable NCQ Trim on ada SSDs. While the 314 list of known rogues that claim support for this but actually corrupt 315 data is believed to be complete, be on the lookout for data 316 corruption. The known rogue list is believed to be complete: 317 318 o Crucial MX100, M550 drives with MU01 firmware. 319 o Micron M510 and M550 drives with MU01 firmware. 320 o Micron M500 prior to MU07 firmware 321 o Samsung 830, 840, and 850 all firmwares 322 o FCCT M500 all firmwares 323 324 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware 325 with working NCQ TRIM. For Micron branded drives, see your sales rep for 326 updated firmware. Black listed drives will work correctly because these 327 drives work correctly so long as no NCQ TRIMs are sent to them. Given 328 this list is the same as found in Linux, it's believed there are no 329 other rogues in the market place. All other models from the above 330 vendors work. 331 332 To be safe, if you are at all concerned, you can quirk each of your 333 drives to prevent NCQ from being sent by setting: 334 kern.cam.ada.X.quirks="0x2" 335 in loader.conf. If the drive requires the 4k sector quirk, set the 336 quirks entry to 0x3. 337 33820160330: 339 The FAST_DEPEND build option has been removed and its functionality is 340 now the one true way. The old mkdep(1) style of 'make depend' has 341 been removed. See 20160311 for further details. 342 34320160317: 344 Resource range types have grown from unsigned long to uintmax_t. All 345 drivers, and anything using libdevinfo, need to be recompiled. 346 34720160311: 348 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree 349 builds. It no longer runs mkdep(1) during 'make depend', and the 350 'make depend' stage can safely be skipped now as it is auto ran 351 when building 'make all' and will generate all SRCS and DPSRCS before 352 building anything else. Dependencies are gathered at compile time with 353 -MF flags kept in separate .depend files per object file. Users should 354 run 'make cleandepend' once if using -DNO_CLEAN to clean out older 355 stale .depend files. 356 35720160306: 358 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into 359 kernel modules. Therefore, if you load any kernel modules at boot time, 360 please install the boot loaders after you install the kernel, but before 361 rebooting, e.g.: 362 363 make buildworld 364 make kernel KERNCONF=YOUR_KERNEL_HERE 365 make -C sys/boot install 366 <reboot in single user> 367 368 Then follow the usual steps, described in the General Notes section, 369 below. 370 37120160305: 372 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please 373 see the 20141231 entry below for information about prerequisites and 374 upgrading, if you are not already using clang 3.5.0 or higher. 375 37620160301: 377 The AIO subsystem is now a standard part of the kernel. The 378 VFS_AIO kernel option and aio.ko kernel module have been removed. 379 Due to stability concerns, asynchronous I/O requests are only 380 permitted on sockets and raw disks by default. To enable 381 asynchronous I/O requests on all file types, set the 382 vfs.aio.enable_unsafe sysctl to a non-zero value. 383 38420160226: 385 The ELF object manipulation tool objcopy is now provided by the 386 ELF Tool Chain project rather than by GNU binutils. It should be a 387 drop-in replacement, with the addition of arm64 support. The 388 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set 389 to obtain the GNU version if necessary. 390 39120160129: 392 Building ZFS pools on top of zvols is prohibited by default. That 393 feature has never worked safely; it's always been prone to deadlocks. 394 Using a zvol as the backing store for a VM guest's virtual disk will 395 still work, even if the guest is using ZFS. Legacy behavior can be 396 restored by setting vfs.zfs.vol.recursive=1. 397 39820160119: 399 The NONE and HPN patches has been removed from OpenSSH. They are 400 still available in the security/openssh-portable port. 401 40220160113: 403 With the addition of ypldap(8), a new _ypldap user is now required 404 during installworld. "mergemaster -p" can be used to add the user 405 prior to installworld, as documented in the handbook. 406 40720151216: 408 The tftp loader (pxeboot) now uses the option root-path directive. As a 409 consequence it no longer looks for a pxeboot.4th file on the tftp 410 server. Instead it uses the regular /boot infrastructure as with the 411 other loaders. 412 41320151211: 414 The code to start recording plug and play data into the modules has 415 been committed. While the old tools will properly build a new kernel, 416 a number of warnings about "unknown metadata record 4" will be produced 417 for an older kldxref. To avoid such warnings, make sure to rebuild 418 the kernel toolchain (or world). Make sure that you have r292078 or 419 later when trying to build 292077 or later before rebuilding. 420 42120151207: 422 Debug data files are now built by default with 'make buildworld' and 423 installed with 'make installworld'. This facilitates debugging but 424 requires more disk space both during the build and for the installed 425 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes 426 in src.conf(5). 427 42820151130: 429 r291527 changed the internal interface between the nfsd.ko and 430 nfscommon.ko modules. As such, they must both be upgraded to-gether. 431 __FreeBSD_version has been bumped because of this. 432 43320151108: 434 Add support for unicode collation strings leads to a change of 435 order of files listed by ls(1) for example. To get back to the old 436 behaviour, set LC_COLLATE environment variable to "C". 437 438 Databases administrators will need to reindex their databases given 439 collation results will be different. 440 441 Due to a bug in install(1) it is recommended to remove the ancient 442 locales before running make installworld. 443 444 rm -rf /usr/share/locale/* 445 44620151030: 447 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring 448 libcrypto.so.7 or libssl.so.7 must be recompiled. 449 45020151020: 451 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0. 452 Kernel modules isp_2400_multi and isp_2500_multi were removed and 453 should be replaced with isp_2400 and isp_2500 modules respectively. 454 45520151017: 456 The build previously allowed using 'make -n' to not recurse into 457 sub-directories while showing what commands would be executed, and 458 'make -n -n' to recursively show commands. Now 'make -n' will recurse 459 and 'make -N' will not. 460 46120151012: 462 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster 463 and etcupdate will now use this file. A custom sendmail.cf is now 464 updated via this mechanism rather than via installworld. If you had 465 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may 466 want to remove the exclusion or change it to "always install". 467 /etc/mail/sendmail.cf is now managed the same way regardless of 468 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using 469 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior. 470 47120151011: 472 Compatibility shims for legacy ATA device names have been removed. 473 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases 474 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.* 475 environment variables, /dev/ad* and /dev/ar* symbolic links. 476 47720151006: 478 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0. 479 Please see the 20141231 entry below for information about prerequisites 480 and upgrading, if you are not already using clang 3.5.0 or higher. 481 48220150924: 483 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/, 484 and renamed from .symbols to .debug. This reduces the size requirements 485 on the boot partition or file system and provides consistency with 486 userland debug files. 487 488 When using the supported kernel installation method the 489 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old) 490 as is done with /boot/kernel. 491 492 Developers wishing to maintain the historical behavior of installing 493 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5). 494 49520150827: 496 The wireless drivers had undergone changes that remove the 'parent 497 interface' from the ifconfig -l output. The rc.d network scripts 498 used to check presence of a parent interface in the list, so old 499 scripts would fail to start wireless networking. Thus, etcupdate(3) 500 or mergemaster(8) run is required after kernel update, to update your 501 rc.d scripts in /etc. 502 50320150827: 504 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl' 505 These configurations are now automatically interpreted as 506 'scrub fragment reassemble'. 507 50820150817: 509 Kernel-loadable modules for the random(4) device are back. To use 510 them, the kernel must have 511 512 device random 513 options RANDOM_LOADABLE 514 515 kldload(8) can then be used to load random_fortuna.ko 516 or random_yarrow.ko. Please note that due to the indirect 517 function calls that the loadable modules need to provide, 518 the build-in variants will be slightly more efficient. 519 520 The random(4) kernel option RANDOM_DUMMY has been retired due to 521 unpopularity. It was not all that useful anyway. 522 52320150813: 524 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired. 525 Control over building the ELF Tool Chain tools is now provided by 526 the WITHOUT_TOOLCHAIN knob. 527 52820150810: 529 The polarity of Pulse Per Second (PPS) capture events with the 530 uart(4) driver has been corrected. Prior to this change the PPS 531 "assert" event corresponded to the trailing edge of a positive PPS 532 pulse and the "clear" event was the leading edge of the next pulse. 533 534 As the width of a PPS pulse in a typical GPS receiver is on the 535 order of 1 millisecond, most users will not notice any significant 536 difference with this change. 537 538 Anyone who has compensated for the historical polarity reversal by 539 configuring a negative offset equal to the pulse width will need to 540 remove that workaround. 541 54220150809: 543 The default group assigned to /dev/dri entries has been changed 544 from 'wheel' to 'video' with the id of '44'. If you want to have 545 access to the dri devices please add yourself to the video group 546 with: 547 548 # pw groupmod video -m $USER 549 55020150806: 551 The menu.rc and loader.rc files will now be replaced during 552 upgrades. Please migrate local changes to menu.rc.local and 553 loader.rc.local instead. 554 55520150805: 556 GNU Binutils versions of addr2line, c++filt, nm, readelf, size, 557 strings and strip have been removed. The src.conf(5) knob 558 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools. 559 56020150728: 561 As ZFS requires more kernel stack pages than is the default on some 562 architectures e.g. i386, it now warns if KSTACK_PAGES is less than 563 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing). 564 565 Please consider using 'options KSTACK_PAGES=X' where X is greater 566 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations. 567 56820150706: 569 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0 570 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by 571 default, i.e., they will not contain "::". For example, instead 572 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet 573 to have a more specific match, such as different map entries for 574 IPv6:0:0 vs IPv6:0. This change requires that configuration 575 data (including maps, files, classes, custom ruleset, etc.) must 576 use the same format, so make certain such configuration data is 577 upgrading. As a very simple check search for patterns like 578 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old 579 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or 580 the cf option UseCompressedIPv6Addresses. 581 58220150630: 583 The default kernel entropy-processing algorithm is now 584 Fortuna, replacing Yarrow. 585 586 Assuming you have 'device random' in your kernel config 587 file, the configurations allow a kernel option to override 588 this default. You may choose *ONE* of: 589 590 options RANDOM_YARROW # Legacy /dev/random algorithm. 591 options RANDOM_DUMMY # Blocking-only driver. 592 593 If you have neither, you get Fortuna. For most people, 594 read no further, Fortuna will give a /dev/random that works 595 like it always used to, and the difference will be irrelevant. 596 597 If you remove 'device random', you get *NO* kernel-processed 598 entropy at all. This may be acceptable to folks building 599 embedded systems, but has complications. Carry on reading, 600 and it is assumed you know what you need. 601 602 *PLEASE* read random(4) and random(9) if you are in the 603 habit of tweaking kernel configs, and/or if you are a member 604 of the embedded community, wanting specific and not-usual 605 behaviour from your security subsystems. 606 607 NOTE!! If you use RANDOM_DUMMY and/or have no 'device 608 random', you will NOT have a functioning /dev/random, and 609 many cryptographic features will not work, including SSH. 610 You may also find strange behaviour from the random(3) set 611 of library functions, in particular sranddev(3), srandomdev(3) 612 and arc4random(3). The reason for this is that the KERN_ARND 613 sysctl only returns entropy if it thinks it has some to 614 share, and with RANDOM_DUMMY or no 'device random' this 615 will never happen. 616 61720150623: 618 An additional fix for the issue described in the 20150614 sendmail 619 entry below has been been committed in revision 284717. 620 62120150616: 622 FreeBSD's old make (fmake) has been removed from the system. It is 623 available as the devel/fmake port or via pkg install fmake. 624 62520150615: 626 The fix for the issue described in the 20150614 sendmail entry 627 below has been been committed in revision 284436. The work 628 around described in that entry is no longer needed unless the 629 default setting is overridden by a confDH_PARAMETERS configuration 630 setting of '5' or pointing to a 512 bit DH parameter file. 631 63220150614: 633 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from 634 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf 635 and devel/kyua to version 0.20+ and adjust any calling code to work 636 with Kyuafile and kyua. 637 63820150614: 639 The import of openssl to address the FreeBSD-SA-15:10.openssl 640 security advisory includes a change which rejects handshakes 641 with DH parameters below 768 bits. sendmail releases prior 642 to 8.15.2 (not yet released), defaulted to a 512 bit 643 DH parameter setting for client connections. To work around 644 this interoperability, sendmail can be configured to use a 645 2048 bit DH parameter by: 646 647 1. Edit /etc/mail/`hostname`.mc 648 2. If a setting for confDH_PARAMETERS does not exist or 649 exists and is set to a string beginning with '5', 650 replace it with '2'. 651 3. If a setting for confDH_PARAMETERS exists and is set to 652 a file path, create a new file with: 653 openssl dhparam -out /path/to/file 2048 654 4. Rebuild the .cf file: 655 cd /etc/mail/; make; make install 656 5. Restart sendmail: 657 cd /etc/mail/; make restart 658 659 A sendmail patch is coming, at which time this file will be 660 updated. 661 66220150604: 663 Generation of legacy formatted entries have been disabled by default 664 in pwd_mkdb(8), as all base system consumers of the legacy formatted 665 entries were converted to use the new format by default when the new, 666 machine independent format have been added and supported since FreeBSD 667 5.x. 668 669 Please see the pwd_mkdb(8) manual page for further details. 670 67120150525: 672 Clang and llvm have been upgraded to 3.6.1 release. Please see the 673 20141231 entry below for information about prerequisites and upgrading, 674 if you are not already using 3.5.0 or higher. 675 67620150521: 677 TI platform code switched to using vendor DTS files and this update 678 may break existing systems running on Beaglebone, Beaglebone Black, 679 and Pandaboard: 680 681 - dtb files should be regenerated/reinstalled. Filenames are the 682 same but content is different now 683 - GPIO addressing was changed, now each GPIO bank (32 pins per bank) 684 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old 685 addressing scheme is now pin 25 on /dev/gpioc3. 686 - Pandaboard: /etc/ttys should be updated, serial console device is 687 now /dev/ttyu2, not /dev/ttyu0 688 68920150501: 690 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim. 691 If you need the GNU extension from groff soelim(1), install groff 692 from package: pkg install groff, or via ports: textproc/groff. 693 69420150423: 695 chmod, chflags, chown and chgrp now affect symlinks in -R mode as 696 defined in symlink(7); previously symlinks were silently ignored. 697 69820150415: 699 The const qualifier has been removed from iconv(3) to comply with 700 POSIX. The ports tree is aware of this from r384038 onwards. 701 70220150416: 703 Libraries specified by LIBADD in Makefiles must have a corresponding 704 DPADD_<lib> variable to ensure correct dependencies. This is now 705 enforced in src.libnames.mk. 706 70720150324: 708 From legacy ata(4) driver was removed support for SATA controllers 709 supported by more functional drivers ahci(4), siis(4) and mvs(4). 710 Kernel modules ataahci and ataadaptec were removed completely, 711 replaced by ahci and mvs modules respectively. 712 71320150315: 714 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see 715 the 20141231 entry below for information about prerequisites and 716 upgrading, if you are not already using 3.5.0 or higher. 717 71820150307: 719 The 32-bit PowerPC kernel has been changed to a position-independent 720 executable. This can only be booted with a version of loader(8) 721 newer than January 31, 2015, so make sure to update both world and 722 kernel before rebooting. 723 72420150217: 725 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014), 726 but before r278950, the RNG was not seeded properly. Immediately 727 upgrade the kernel to r278950 or later and regenerate any keys (e.g. 728 ssh keys or openssl keys) that were generated w/ a kernel from that 729 range. This does not affect programs that directly used /dev/random 730 or /dev/urandom. All userland uses of arc4random(3) are affected. 731 73220150210: 733 The autofs(4) ABI was changed in order to restore binary compatibility 734 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work 735 with the new kernel. 736 73720150131: 738 The powerpc64 kernel has been changed to a position-independent 739 executable. This can only be booted with a new version of loader(8), 740 so make sure to update both world and kernel before rebooting. 741 74220150118: 743 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix 744 only release, no new features have been added. Please see the 20141231 745 entry below for information about prerequisites and upgrading, if you 746 are not already using 3.5.0. 747 74820150107: 749 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now 750 taken from the ELF Tool Chain project rather than GNU binutils. They 751 should be drop-in replacements, with the addition of arm64 support. 752 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the 753 binutils tools, if necessary. See 20150805 for updated information. 754 75520150105: 756 The default Unbound configuration now enables remote control 757 using a local socket. Users who have already enabled the 758 local_unbound service should regenerate their configuration 759 by running "service local_unbound setup" as root. 760 76120150102: 762 The GNU texinfo and GNU info pages have been removed. 763 To be able to view GNU info pages please install texinfo from ports. 764 76520141231: 766 Clang, llvm and lldb have been upgraded to 3.5.0 release. 767 768 As of this release, a prerequisite for building clang, llvm and lldb is 769 a C++11 capable compiler and C++11 standard library. This means that to 770 be able to successfully build the cross-tools stage of buildworld, with 771 clang as the bootstrap compiler, your system compiler or cross compiler 772 should either be clang 3.3 or later, or gcc 4.8 or later, and your 773 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or 774 later. 775 776 On any standard FreeBSD 10.x or 11.x installation, where clang and 777 libc++ are on by default (that is, on x86 or arm), this should work out 778 of the box. 779 780 On 9.x installations where clang is enabled by default, e.g. on x86 and 781 powerpc, libc++ will not be enabled by default, so libc++ should be 782 built (with clang) and installed first. If both clang and libc++ are 783 missing, build clang first, then use it to build libc++. 784 785 On 8.x and earlier installations, upgrade to 9.x first, and then follow 786 the instructions for 9.x above. 787 788 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by 789 default, and do not build clang. 790 791 Many embedded systems are resource constrained, and will not be able to 792 build clang in a reasonable time, or in some cases at all. In those 793 cases, cross building bootable systems on amd64 is a workaround. 794 795 This new version of clang introduces a number of new warnings, of which 796 the following are most likely to appear: 797 798 -Wabsolute-value 799 800 This warns in two cases, for both C and C++: 801 * When the code is trying to take the absolute value of an unsigned 802 quantity, which is effectively a no-op, and almost never what was 803 intended. The code should be fixed, if at all possible. If you are 804 sure that the unsigned quantity can be safely cast to signed, without 805 loss of information or undefined behavior, you can add an explicit 806 cast, or disable the warning. 807 808 * When the code is trying to take an absolute value, but the called 809 abs() variant is for the wrong type, which can lead to truncation. 810 If you want to disable the warning instead of fixing the code, please 811 make sure that truncation will not occur, or it might lead to unwanted 812 side-effects. 813 814 -Wtautological-undefined-compare and 815 -Wundefined-bool-conversion 816 817 These warn when C++ code is trying to compare 'this' against NULL, while 818 'this' should never be NULL in well-defined C++ code. However, there is 819 some legacy (pre C++11) code out there, which actively abuses this 820 feature, which was less strictly defined in previous C++ versions. 821 822 Squid and openjdk do this, for example. The warning can be turned off 823 for C++98 and earlier, but compiling the code in C++11 mode might result 824 in unexpected behavior; for example, the parts of the program that are 825 unreachable could be optimized away. 826 82720141222: 828 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER) 829 kernel sources have been removed. The .h files remain, since some 830 utilities include them. This will need to be fixed later. 831 If "mount -t oldnfs ..." is attempted, it will fail. 832 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used, 833 the utilities will report errors. 834 83520141121: 836 The handling of LOCAL_LIB_DIRS has been altered to skip addition of 837 directories to top level SUBDIR variable when their parent 838 directory is included in LOCAL_DIRS. Users with build systems with 839 such hierarchies and without SUBDIR entries in the parent 840 directory Makefiles should add them or add the directories to 841 LOCAL_DIRS. 842 84320141109: 844 faith(4) and faithd(8) have been removed from the base system. Faith 845 has been obsolete for a very long time. 846 84720141104: 848 vt(4), the new console driver, is enabled by default. It brings 849 support for Unicode and double-width characters, as well as 850 support for UEFI and integration with the KMS kernel video 851 drivers. 852 853 You may need to update your console settings in /etc/rc.conf, 854 most probably the keymap. During boot, /etc/rc.d/syscons will 855 indicate what you need to do. 856 857 vt(4) still has issues and lacks some features compared to 858 syscons(4). See the wiki for up-to-date information: 859 https://wiki.freebsd.org/Newcons 860 861 If you want to keep using syscons(4), you can do so by adding 862 the following line to /boot/loader.conf: 863 kern.vty=sc 864 86520141102: 866 pjdfstest has been integrated into kyua as an opt-in test suite. 867 Please see share/doc/pjdfstest/README for more details on how to 868 execute it. 869 87020141009: 871 gperf has been removed from the base system for architectures 872 that use clang. Ports that require gperf will obtain it from the 873 devel/gperf port. 874 87520140923: 876 pjdfstest has been moved from tools/regression/pjdfstest to 877 contrib/pjdfstest . 878 87920140922: 880 At svn r271982, The default linux compat kernel ABI has been adjusted 881 to 2.6.18 in support of the linux-c6 compat ports infrastructure 882 update. If you wish to continue using the linux-f10 compat ports, 883 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are 884 encouraged to update their linux-compat packages to linux-c6 during 885 their next update cycle. 886 88720140729: 888 The ofwfb driver, used to provide a graphics console on PowerPC when 889 using vt(4), no longer allows mmap() of all physical memory. This 890 will prevent Xorg on PowerPC with some ATI graphics cards from 891 initializing properly unless x11-servers/xorg-server is updated to 892 1.12.4_8 or newer. 893 89420140723: 895 The xdev targets have been converted to using TARGET and 896 TARGET_ARCH instead of XDEV and XDEV_ARCH. 897 89820140719: 899 The default unbound configuration has been modified to address 900 issues with reverse lookups on networks that use private 901 address ranges. If you use the local_unbound service, run 902 "service local_unbound setup" as root to regenerate your 903 configuration, then "service local_unbound reload" to load the 904 new configuration. 905 90620140709: 907 The GNU texinfo and GNU info pages are not built and installed 908 anymore, WITH_INFO knob has been added to allow to built and install 909 them again. 910 UPDATE: see 20150102 entry on texinfo's removal 911 91220140708: 913 The GNU readline library is now an INTERNALLIB - that is, it is 914 statically linked into consumers (GDB and variants) in the base 915 system, and the shared library is no longer installed. The 916 devel/readline port is available for third party software that 917 requires readline. 918 91920140702: 920 The Itanium architecture (ia64) has been removed from the list of 921 known architectures. This is the first step in the removal of the 922 architecture. 923 92420140701: 925 Commit r268115 has added NFSv4.1 server support, merged from 926 projects/nfsv4.1-server. Since this includes changes to the 927 internal interfaces between the NFS related modules, a full 928 build of the kernel and modules will be necessary. 929 __FreeBSD_version has been bumped. 930 93120140629: 932 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 933 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 934 which differs from the behaviour controlled by this knob.) 935 93620140619: 937 Maximal length of the serial number in CTL was increased from 16 to 938 64 chars, that breaks ABI. All CTL-related tools, such as ctladm 939 and ctld, need to be rebuilt to work with a new kernel. 940 94120140606: 942 The libatf-c and libatf-c++ major versions were downgraded to 0 and 943 1 respectively to match the upstream numbers. They were out of 944 sync because, when they were originally added to FreeBSD, the 945 upstream versions were not respected. These libraries are private 946 and not yet built by default, so renumbering them should be a 947 non-issue. However, unclean source trees will yield broken test 948 programs once the operator executes "make delete-old-libs" after a 949 "make installworld". 950 951 Additionally, the atf-sh binary was made private by moving it into 952 /usr/libexec/. Already-built shell test programs will keep the 953 path to the old binary so they will break after "make delete-old" 954 is run. 955 956 If you are using WITH_TESTS=yes (not the default), wipe the object 957 tree and rebuild from scratch to prevent spurious test failures. 958 This is only needed once: the misnumbered libraries and misplaced 959 binaries have been added to OptionalObsoleteFiles.inc so they will 960 be removed during a clean upgrade. 961 96220140512: 963 Clang and llvm have been upgraded to 3.4.1 release. 964 96520140508: 966 We bogusly installed src.opts.mk in /usr/share/mk. This file should 967 be removed to avoid issues in the future (and has been added to 968 ObsoleteFiles.inc). 969 97020140505: 971 /etc/src.conf now affects only builds of the FreeBSD src tree. In the 972 past, it affected all builds that used the bsd.*.mk files. The old 973 behavior was a bug, but people may have relied upon it. To get this 974 behavior back, you can .include /etc/src.conf from /etc/make.conf 975 (which is still global and isn't changed). This also changes the 976 behavior of incremental builds inside the tree of individual 977 directories. Set MAKESYSPATH to ".../share/mk" to do that. 978 Although this has survived make universe and some upgrade scenarios, 979 other upgrade scenarios may have broken. At least one form of 980 temporary breakage was fixed with MAKESYSPATH settings for buildworld 981 as well... In cases where MAKESYSPATH isn't working with this 982 setting, you'll need to set it to the full path to your tree. 983 984 One side effect of all this cleaning up is that bsd.compiler.mk 985 is no longer implicitly included by bsd.own.mk. If you wish to 986 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk 987 as well. 988 98920140430: 990 The lindev device has been removed since /dev/full has been made a 991 standard device. __FreeBSD_version has been bumped. 992 99320140424: 994 The knob WITHOUT_VI was added to the base system, which controls 995 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1) 996 in order to reorder files share/termcap and didn't build ex(1) as a 997 build tool, so building/installing with WITH_VI is highly advised for 998 build hosts for older releases. 999 1000 This issue has been fixed in stable/9 and stable/10 in r277022 and 1001 r276991, respectively. 1002 100320140418: 1004 The YES_HESIOD knob has been removed. It has been obsolete for 1005 a decade. Please move to using WITH_HESIOD instead or your builds 1006 will silently lack HESIOD. 1007 100820140405: 1009 The uart(4) driver has been changed with respect to its handling 1010 of the low-level console. Previously the uart(4) driver prevented 1011 any process from changing the baudrate or the CLOCAL and HUPCL 1012 control flags. By removing the restrictions, operators can make 1013 changes to the serial console port without having to reboot. 1014 However, when getty(8) is started on the serial device that is 1015 associated with the low-level console, a misconfigured terminal 1016 line in /etc/ttys will now have a real impact. 1017 Before upgrading the kernel, make sure that /etc/ttys has the 1018 serial console device configured as 3wire without baudrate to 1019 preserve the previous behaviour. E.g: 1020 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure 1021 102220140306: 1023 Support for libwrap (TCP wrappers) in rpcbind was disabled by default 1024 to improve performance. To re-enable it, if needed, run rpcbind 1025 with command line option -W. 1026 102720140226: 1028 Switched back to the GPL dtc compiler due to updates in the upstream 1029 dts files not being supported by the BSDL dtc compiler. You will need 1030 to rebuild your kernel toolchain to pick up the new compiler. Core dumps 1031 may result while building dtb files during a kernel build if you fail 1032 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler. 1033 103420140216: 1035 Clang and llvm have been upgraded to 3.4 release. 1036 103720140216: 1038 The nve(4) driver has been removed. Please use the nfe(4) driver 1039 for NVIDIA nForce MCP Ethernet adapters instead. 1040 104120140212: 1042 An ABI incompatibility crept into the libc++ 3.4 import in r261283. 1043 This could cause certain C++ applications using shared libraries built 1044 against the previous version of libc++ to crash. The incompatibility 1045 has now been fixed, but any C++ applications or shared libraries built 1046 between r261283 and r261801 should be recompiled. 1047 104820140204: 1049 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 1050 capability mode support. Please note that enabling the feature in 1051 kernel is still highly recommended. 1052 105320140131: 1054 OpenSSH is now built with sandbox support, and will use sandbox as 1055 the default privilege separation method. This requires Capsicum 1056 capability mode support in kernel. 1057 105820140128: 1059 The libelf and libdwarf libraries have been updated to newer 1060 versions from upstream. Shared library version numbers for 1061 these two libraries were bumped. Any ports or binaries 1062 requiring these two libraries should be recompiled. 1063 __FreeBSD_version is bumped to 1100006. 1064 106520140110: 1066 If a Makefile in a tests/ directory was auto-generating a Kyuafile 1067 instead of providing an explicit one, this would prevent such 1068 Makefile from providing its own Kyuafile in the future during 1069 NO_CLEAN builds. This has been fixed in the Makefiles but manual 1070 intervention is needed to clean an objdir if you use NO_CLEAN: 1071 # find /usr/obj -name Kyuafile | xargs rm -f 1072 107320131213: 1074 The behavior of gss_pseudo_random() for the krb5 mechanism 1075 has changed, for applications requesting a longer random string 1076 than produced by the underlying enctype's pseudo-random() function. 1077 In particular, the random string produced from a session key of 1078 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 1079 be different at the 17th octet and later, after this change. 1080 The counter used in the PRF+ construction is now encoded as a 1081 big-endian integer in accordance with RFC 4402. 1082 __FreeBSD_version is bumped to 1100004. 1083 108420131108: 1085 The WITHOUT_ATF build knob has been removed and its functionality 1086 has been subsumed into the more generic WITHOUT_TESTS. If you were 1087 using the former to disable the build of the ATF libraries, you 1088 should change your settings to use the latter. 1089 109020131025: 1091 The default version of mtree is nmtree which is obtained from 1092 NetBSD. The output is generally the same, but may vary 1093 slightly. If you found you need identical output adding 1094 "-F freebsd9" to the command line should do the trick. For the 1095 time being, the old mtree is available as fmtree. 1096 109720131014: 1098 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 1099 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 1100 1.1.4_8 and verify bsdyml not linked in, before running "make 1101 delete-old-libs": 1102 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 1103 or 1104 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 1105 110620131010: 1107 The stable/10 branch has been created in subversion from head 1108 revision r256279. 1109 111020131010: 1111 The rc.d/jail script has been updated to support jail(8) 1112 configuration file. The "jail_<jname>_*" rc.conf(5) variables 1113 for per-jail configuration are automatically converted to 1114 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 1115 This is transparently backward compatible. See below about some 1116 incompatibilities and rc.conf(5) manual page for more details. 1117 1118 These variables are now deprecated in favor of jail(8) configuration 1119 file. One can use "rc.d/jail config <jname>" command to generate 1120 a jail(8) configuration file in /var/run/jail.<jname>.conf without 1121 running the jail(8) utility. The default pathname of the 1122 configuration file is /etc/jail.conf and can be specified by 1123 using $jail_conf or $jail_<jname>_conf variables. 1124 1125 Please note that jail_devfs_ruleset accepts an integer at 1126 this moment. Please consider to rewrite the ruleset name 1127 with an integer. 1128 112920130930: 1130 BIND has been removed from the base system. If all you need 1131 is a local resolver, simply enable and start the local_unbound 1132 service instead. Otherwise, several versions of BIND are 1133 available in the ports tree. The dns/bind99 port is one example. 1134 1135 With this change, nslookup(1) and dig(1) are no longer in the base 1136 system. Users should instead use host(1) and drill(1) which are 1137 in the base system. Alternatively, nslookup and dig can 1138 be obtained by installing the dns/bind-tools port. 1139 114020130916: 1141 With the addition of unbound(8), a new unbound user is now 1142 required during installworld. "mergemaster -p" can be used to 1143 add the user prior to installworld, as documented in the handbook. 1144 114520130911: 1146 OpenSSH is now built with DNSSEC support, and will by default 1147 silently trust signed SSHFP records. This can be controlled with 1148 the VerifyHostKeyDNS client configuration setting. DNSSEC support 1149 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 1150 115120130906: 1152 The GNU Compiler Collection and C++ standard library (libstdc++) 1153 are no longer built by default on platforms where clang is the system 1154 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 1155 options in src.conf. 1156 115720130905: 1158 The PROCDESC kernel option is now part of the GENERIC kernel 1159 configuration and is required for the rwhod(8) to work. 1160 If you are using custom kernel configuration, you should include 1161 'options PROCDESC'. 1162 116320130905: 1164 The API and ABI related to the Capsicum framework was modified 1165 in backward incompatible way. The userland libraries and programs 1166 have to be recompiled to work with the new kernel. This includes the 1167 following libraries and programs, but the whole buildworld is 1168 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 1169 kdump, procstat, rwho, rwhod, uniq. 1170 117120130903: 1172 AES-NI intrinsic support has been added to gcc. The AES-NI module 1173 has been updated to use this support. A new gcc is required to build 1174 the aesni module on both i386 and amd64. 1175 117620130821: 1177 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 1178 Thus "device padlock_rng" and "device rdrand_rng" should be 1179 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 1180 118120130813: 1182 WITH_ICONV has been split into two feature sets. WITH_ICONV now 1183 enables just the iconv* functionality and is now on by default. 1184 WITH_LIBICONV_COMPAT enables the libiconv api and link time 1185 compatibility. Set WITHOUT_ICONV to build the old way. 1186 If you have been using WITH_ICONV before, you will very likely 1187 need to turn on WITH_LIBICONV_COMPAT. 1188 118920130806: 1190 INVARIANTS option now enables DEBUG for code with OpenSolaris and 1191 Illumos origin, including ZFS. If you have INVARIANTS in your 1192 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 1193 explicitly. 1194 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 1195 locks if WITNESS option was set. Because that generated a lot of 1196 witness(9) reports and all of them were believed to be false 1197 positives, this is no longer done. New option OPENSOLARIS_WITNESS 1198 can be used to achieve the previous behavior. 1199 120020130806: 1201 Timer values in IPv6 data structures now use time_uptime instead 1202 of time_second. Although this is not a user-visible functional 1203 change, userland utilities which directly use them---ndp(8), 1204 rtadvd(8), and rtsold(8) in the base system---need to be updated 1205 to r253970 or later. 1206 120720130802: 1208 find -delete can now delete the pathnames given as arguments, 1209 instead of only files found below them or if the pathname did 1210 not contain any slashes. Formerly, the following error message 1211 would result: 1212 1213 find: -delete: <path>: relative path potentially not safe 1214 1215 Deleting the pathnames given as arguments can be prevented 1216 without error messages using -mindepth 1 or by changing 1217 directory and passing "." as argument to find. This works in the 1218 old as well as the new version of find. 1219 122020130726: 1221 Behavior of devfs rules path matching has been changed. 1222 Pattern is now always matched against fully qualified devfs 1223 path and slash characters must be explicitly matched by 1224 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 1225 subdirectories must be reviewed. 1226 122720130716: 1228 The default ARM ABI has changed to the ARM EABI. The old ABI is 1229 incompatible with the ARM EABI and all programs and modules will 1230 need to be rebuilt to work with a new kernel. 1231 1232 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 1233 1234 NOTE: Support for the old ABI will be removed in the future and 1235 users are advised to upgrade. 1236 123720130709: 1238 pkg_install has been disconnected from the build if you really need it 1239 you should add WITH_PKGTOOLS in your src.conf(5). 1240 124120130709: 1242 Most of network statistics structures were changed to be able 1243 keep 64-bits counters. Thus all tools, that work with networking 1244 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 1245 124620130618: 1247 Fix a bug that allowed a tracing process (e.g. gdb) to write 1248 to a memory-mapped file in the traced process's address space 1249 even if neither the traced process nor the tracing process had 1250 write access to that file. 1251 125220130615: 1253 CVS has been removed from the base system. An exact copy 1254 of the code is available from the devel/cvs port. 1255 125620130613: 1257 Some people report the following error after the switch to bmake: 1258 1259 make: illegal option -- J 1260 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 1261 ... 1262 *** [buildworld] Error code 2 1263 1264 this likely due to an old instance of make in 1265 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 1266 which src/Makefile will use that blindly, if it exists, so if 1267 you see the above error: 1268 1269 rm -rf `make -V MAKEPATH` 1270 1271 should resolve it. 1272 127320130516: 1274 Use bmake by default. 1275 Whereas before one could choose to build with bmake via 1276 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 1277 make. The goal is to remove these knobs for 10-RELEASE. 1278 1279 It is worth noting that bmake (like gmake) treats the command 1280 line as the unit of failure, rather than statements within the 1281 command line. Thus '(cd some/where && dosomething)' is safer 1282 than 'cd some/where; dosomething'. The '()' allows consistent 1283 behavior in parallel build. 1284 128520130429: 1286 Fix a bug that allows NFS clients to issue READDIR on files. 1287 128820130426: 1289 The WITHOUT_IDEA option has been removed because 1290 the IDEA patent expired. 1291 129220130426: 1293 The sysctl which controls TRIM support under ZFS has been renamed 1294 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 1295 enabled by default. 1296 129720130425: 1298 The mergemaster command now uses the default MAKEOBJDIRPREFIX 1299 rather than creating it's own in the temporary directory in 1300 order allow access to bootstrapped versions of tools such as 1301 install and mtree. When upgrading from version of FreeBSD where 1302 the install command does not support -l, you will need to 1303 install a new mergemaster command if mergemaster -p is required. 1304 This can be accomplished with the command (cd src/usr.sbin/mergemaster 1305 && make install). 1306 130720130404: 1308 Legacy ATA stack, disabled and replaced by new CAM-based one since 1309 FreeBSD 9.0, completely removed from the sources. Kernel modules 1310 atadisk and atapi*, user-level tools atacontrol and burncd are 1311 removed. Kernel option `options ATA_CAM` is now permanently enabled 1312 and removed. 1313 131420130319: 1315 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 1316 and socketpair(2). Software, in particular Kerberos, may 1317 automatically detect and use these during building. The resulting 1318 binaries will not work on older kernels. 1319 132020130308: 1321 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 1322 information, see the respective 20130304 entry). 1323 132420130304: 1325 Recent commits to callout(9) changed the size of struct callout, 1326 so the KBI is probably heavily disturbed. Also, some functions 1327 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 1328 by macros. Every kernel module using it won't load, so rebuild 1329 is requested. 1330 1331 The ctl device has been re-enabled in GENERIC for i386 and amd64, 1332 but does not initialize by default (because of the new CTL_DISABLE 1333 option) to save memory. To re-enable it, remove the CTL_DISABLE 1334 option from the kernel config file or set kern.cam.ctl.disable=0 1335 in /boot/loader.conf. 1336 133720130301: 1338 The ctl device has been disabled in GENERIC for i386 and amd64. 1339 This was done due to the extra memory being allocated at system 1340 initialisation time by the ctl driver which was only used if 1341 a CAM target device was created. This makes a FreeBSD system 1342 unusable on 128MB or less of RAM. 1343 134420130208: 1345 A new compression method (lz4) has been merged to -HEAD. Please 1346 refer to zpool-features(7) for more information. 1347 1348 Please refer to the "ZFS notes" section of this file for information 1349 on upgrading boot ZFS pools. 1350 135120130129: 1352 A BSD-licensed patch(1) variant has been added and is installed 1353 as bsdpatch, being the GNU version the default patch. 1354 To inverse the logic and use the BSD-licensed one as default, 1355 while having the GNU version installed as gnupatch, rebuild 1356 and install world with the WITH_BSD_PATCH knob set. 1357 135820130121: 1359 Due to the use of the new -l option to install(1) during build 1360 and install, you must take care not to directly set the INSTALL 1361 make variable in your /etc/make.conf, /etc/src.conf, or on the 1362 command line. If you wish to use the -C flag for all installs 1363 you may be able to add INSTALL+=-C to /etc/make.conf or 1364 /etc/src.conf. 1365 136620130118: 1367 The install(1) option -M has changed meaning and now takes an 1368 argument that is a file or path to append logs to. In the 1369 unlikely event that -M was the last option on the command line 1370 and the command line contained at least two files and a target 1371 directory the first file will have logs appended to it. The -M 1372 option served little practical purpose in the last decade so its 1373 use is expected to be extremely rare. 1374 137520121223: 1376 After switching to Clang as the default compiler some users of ZFS 1377 on i386 systems started to experience stack overflow kernel panics. 1378 Please consider using 'options KSTACK_PAGES=4' in such configurations. 1379 138020121222: 1381 GEOM_LABEL now mangles label names read from file system metadata. 1382 Mangling affect labels containing spaces, non-printable characters, 1383 '%' or '"'. Device names in /etc/fstab and other places may need to 1384 be updated. 1385 138620121217: 1387 By default, only the 10 most recent kernel dumps will be saved. To 1388 restore the previous behaviour (no limit on the number of kernel dumps 1389 stored in the dump directory) add the following line to /etc/rc.conf: 1390 1391 savecore_flags="" 1392 139320121201: 1394 With the addition of auditdistd(8), a new auditdistd user is now 1395 required during installworld. "mergemaster -p" can be used to 1396 add the user prior to installworld, as documented in the handbook. 1397 139820121117: 1399 The sin6_scope_id member variable in struct sockaddr_in6 is now 1400 filled by the kernel before passing the structure to the userland via 1401 sysctl or routing socket. This means the KAME-specific embedded scope 1402 id in sin6_addr.s6_addr[2] is always cleared in userland application. 1403 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 1404 __FreeBSD_version is bumped to 1000025. 1405 140620121105: 1407 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 1408 This means that the world and kernel will be compiled with clang 1409 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 1410 and /usr/bin/cpp. To disable this behavior and revert to building 1411 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 1412 of current may need to bootstrap WITHOUT_CLANG first if the clang 1413 build fails (its compatibility window doesn't extend to the 9 stable 1414 branch point). 1415 141620121102: 1417 The IPFIREWALL_FORWARD kernel option has been removed. Its 1418 functionality now turned on by default. 1419 142020121023: 1421 The ZERO_COPY_SOCKET kernel option has been removed and 1422 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 1423 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 1424 mechanism which is not safe and may result in kernel crashes. 1425 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 1426 driver supports disposeable external page sized mbuf storage. 1427 Proper replacements for both zero-copy mechanisms are under 1428 consideration and will eventually lead to complete removal 1429 of the two kernel options. 1430 143120121023: 1432 The IPv4 network stack has been converted to network byte 1433 order. The following modules need to be recompiled together 1434 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 1435 pf(4), ipfw(4), ng_ipfw(4), stf(4). 1436 143720121022: 1438 Support for non-MPSAFE filesystems was removed from VFS. The 1439 VFS_VERSION was bumped, all filesystem modules shall be 1440 recompiled. 1441 144220121018: 1443 All the non-MPSAFE filesystems have been disconnected from 1444 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 1445 portalfs, smbfs, xfs. 1446 144720121016: 1448 The interface cloning API and ABI has changed. The following 1449 modules need to be recompiled together with kernel: 1450 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 1451 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 1452 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 1453 145420121015: 1455 The sdhci driver was split in two parts: sdhci (generic SD Host 1456 Controller logic) and sdhci_pci (actual hardware driver). 1457 No kernel config modifications are required, but if you 1458 load sdhc as a module you must switch to sdhci_pci instead. 1459 146020121014: 1461 Import the FUSE kernel and userland support into base system. 1462 146320121013: 1464 The GNU sort(1) program has been removed since the BSD-licensed 1465 sort(1) has been the default for quite some time and no serious 1466 problems have been reported. The corresponding WITH_GNU_SORT 1467 knob has also gone. 1468 146920121006: 1470 The pfil(9) API/ABI for AF_INET family has been changed. Packet 1471 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 1472 with new kernel. 1473 147420121001: 1475 The net80211(4) ABI has been changed to allow for improved driver 1476 PS-POLL and power-save support. All wireless drivers need to be 1477 recompiled to work with the new kernel. 1478 147920120913: 1480 The random(4) support for the VIA hardware random number 1481 generator (`PADLOCK') is no longer enabled unconditionally. 1482 Add the padlock_rng device in the custom kernel config if 1483 needed. The GENERIC kernels on i386 and amd64 do include the 1484 device, so the change only affects the custom kernel 1485 configurations. 1486 148720120908: 1488 The pf(4) packet filter ABI has been changed. pfctl(8) and 1489 snmp_pf module need to be recompiled to work with new kernel. 1490 149120120828: 1492 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 1493 to -HEAD. Pools that have empty_bpobj in active state can not be 1494 imported read-write with ZFS implementations that do not support 1495 this feature. For more information read the zpool-features(5) 1496 manual page. 1497 149820120727: 1499 The sparc64 ZFS loader has been changed to no longer try to auto- 1500 detect ZFS providers based on diskN aliases but now requires these 1501 to be explicitly listed in the OFW boot-device environment variable. 1502 150320120712: 1504 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 1505 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 1506 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 1507 150820120712: 1509 The following sysctls and tunables have been renamed for consistency 1510 with other variables: 1511 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 1512 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 1513 151420120628: 1515 The sort utility has been replaced with BSD sort. For now, GNU sort 1516 is also available as "gnusort" or the default can be set back to 1517 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 1518 installed as "bsdsort". 1519 152020120611: 1521 A new version of ZFS (pool version 5000) has been merged to -HEAD. 1522 Starting with this version the old system of ZFS pool versioning 1523 is superseded by "feature flags". This concept enables forward 1524 compatibility against certain future changes in functionality of ZFS 1525 pools. The first read-only compatible "feature flag" for ZFS pools 1526 is named "com.delphix:async_destroy". For more information 1527 read the new zpool-features(5) manual page. 1528 Please refer to the "ZFS notes" section of this file for information 1529 on upgrading boot ZFS pools. 1530 153120120417: 1532 The malloc(3) implementation embedded in libc now uses sources imported 1533 as contrib/jemalloc. The most disruptive API change is to 1534 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 1535 delete it prior to installworld, and optionally re-create it using the 1536 new format after rebooting. See malloc.conf(5) for details 1537 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 1538 NAMESPACE section). 1539 154020120328: 1541 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 1542 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 1543 now spelled mips. This is to aid compatibility with third-party 1544 software that expects this naming scheme in uname(3). Little-endian 1545 settings are unchanged. If you are updating a big-endian mips64 machine 1546 from before this change, you may need to set MACHINE_ARCH=mips64 in 1547 your environment before the new build system will recognize your machine. 1548 154920120306: 1550 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 1551 platforms. 1552 155320120229: 1554 Now unix domain sockets behave "as expected" on nullfs(5). Previously 1555 nullfs(5) did not pass through all behaviours to the underlying layer, 1556 as a result if we bound to a socket on the lower layer we could connect 1557 only to the lower path; if we bound to the upper layer we could connect 1558 only to the upper path. The new behavior is one can connect to both the 1559 lower and the upper paths regardless what layer path one binds to. 1560 156120120211: 1562 The getifaddrs upgrade path broken with 20111215 has been restored. 1563 If you have upgraded in between 20111215 and 20120209 you need to 1564 recompile libc again with your kernel. You still need to recompile 1565 world to be able to configure CARP but this restriction already 1566 comes from 20111215. 1567 156820120114: 1569 The set_rcvar() function has been removed from /etc/rc.subr. All 1570 base and ports rc.d scripts have been updated, so if you have a 1571 port installed with a script in /usr/local/etc/rc.d you can either 1572 hand-edit the rcvar= line, or reinstall the port. 1573 1574 An easy way to handle the mass-update of /etc/rc.d: 1575 rm /etc/rc.d/* && mergemaster -i 1576 157720120109: 1578 panic(9) now stops other CPUs in the SMP systems, disables interrupts 1579 on the current CPU and prevents other threads from running. 1580 This behavior can be reverted using the kern.stop_scheduler_on_panic 1581 tunable/sysctl. 1582 The new behavior can be incompatible with kern.sync_on_panic. 1583 158420111215: 1585 The carp(4) facility has been changed significantly. Configuration 1586 of the CARP protocol via ifconfig(8) has changed, as well as format 1587 of CARP events submitted to devd(8) has changed. See manual pages 1588 for more information. The arpbalance feature of carp(4) is currently 1589 not supported anymore. 1590 1591 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 1592 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 1593 need to be recompiled. 1594 159520111122: 1596 The acpi_wmi(4) status device /dev/wmistat has been renamed to 1597 /dev/wmistat0. 1598 159920111108: 1600 The option VFS_ALLOW_NONMPSAFE option has been added in order to 1601 explicitely support non-MPSAFE filesystems. 1602 It is on by default for all supported platform at this present 1603 time. 1604 160520111101: 1606 The broken amd(4) driver has been replaced with esp(4) in the amd64, 1607 i386 and pc98 GENERIC kernel configuration files. 1608 160920110930: 1610 sysinstall has been removed 1611 161220110923: 1613 The stable/9 branch created in subversion. This corresponds to the 1614 RELENG_9 branch in CVS. 1615 1616COMMON ITEMS: 1617 1618 General Notes 1619 ------------- 1620 Avoid using make -j when upgrading. While generally safe, there are 1621 sometimes problems using -j to upgrade. If your upgrade fails with 1622 -j, please try again without -j. From time to time in the past there 1623 have been problems using -j with buildworld and/or installworld. This 1624 is especially true when upgrading between "distant" versions (eg one 1625 that cross a major release boundary or several minor releases, or when 1626 several months have passed on the -current branch). 1627 1628 Sometimes, obscure build problems are the result of environment 1629 poisoning. This can happen because the make utility reads its 1630 environment when searching for values for global variables. To run 1631 your build attempts in an "environmental clean room", prefix all make 1632 commands with 'env -i '. See the env(1) manual page for more details. 1633 1634 When upgrading from one major version to another it is generally best 1635 to upgrade to the latest code in the currently installed branch first, 1636 then do an upgrade to the new branch. This is the best-tested upgrade 1637 path, and has the highest probability of being successful. Please try 1638 this approach before reporting problems with a major version upgrade. 1639 1640 When upgrading a live system, having a root shell around before 1641 installing anything can help undo problems. Not having a root shell 1642 around can lead to problems if pam has changed too much from your 1643 starting point to allow continued authentication after the upgrade. 1644 1645 This file should be read as a log of events. When a later event changes 1646 information of a prior event, the prior event should not be deleted. 1647 Instead, a pointer to the entry with the new information should be 1648 placed in the old entry. Readers of this file should also sanity check 1649 older entries before relying on them blindly. Authors of new entries 1650 should write them with this in mind. 1651 1652 ZFS notes 1653 --------- 1654 When upgrading the boot ZFS pool to a new version, always follow 1655 these two steps: 1656 1657 1.) recompile and reinstall the ZFS boot loader and boot block 1658 (this is part of "make buildworld" and "make installworld") 1659 1660 2.) update the ZFS boot block on your boot drive 1661 1662 The following example updates the ZFS boot block on the first 1663 partition (freebsd-boot) of a GPT partitioned drive ada0: 1664 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0" 1665 1666 Non-boot pools do not need these updates. 1667 1668 To build a kernel 1669 ----------------- 1670 If you are updating from a prior version of FreeBSD (even one just 1671 a few days old), you should follow this procedure. It is the most 1672 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 1673 1674 make kernel-toolchain 1675 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 1676 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 1677 1678 To test a kernel once 1679 --------------------- 1680 If you just want to boot a kernel once (because you are not sure 1681 if it works, or if you want to boot a known bad kernel to provide 1682 debugging information) run 1683 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 1684 nextboot -k testkernel 1685 1686 To just build a kernel when you know that it won't mess you up 1687 -------------------------------------------------------------- 1688 This assumes you are already running a CURRENT system. Replace 1689 ${arch} with the architecture of your machine (e.g. "i386", 1690 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 1691 1692 cd src/sys/${arch}/conf 1693 config KERNEL_NAME_HERE 1694 cd ../compile/KERNEL_NAME_HERE 1695 make depend 1696 make 1697 make install 1698 1699 If this fails, go to the "To build a kernel" section. 1700 1701 To rebuild everything and install it on the current system. 1702 ----------------------------------------------------------- 1703 # Note: sometimes if you are running current you gotta do more than 1704 # is listed here if you are upgrading from a really old current. 1705 1706 <make sure you have good level 0 dumps> 1707 make buildworld 1708 make kernel KERNCONF=YOUR_KERNEL_HERE 1709 [1] 1710 <reboot in single user> [3] 1711 mergemaster -Fp [5] 1712 make installworld 1713 mergemaster -Fi [4] 1714 make delete-old [6] 1715 <reboot> 1716 1717 To cross-install current onto a separate partition 1718 -------------------------------------------------- 1719 # In this approach we use a separate partition to hold 1720 # current's root, 'usr', and 'var' directories. A partition 1721 # holding "/", "/usr" and "/var" should be about 2GB in 1722 # size. 1723 1724 <make sure you have good level 0 dumps> 1725 <boot into -stable> 1726 make buildworld 1727 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1728 <maybe newfs current's root partition> 1729 <mount current's root partition on directory ${CURRENT_ROOT}> 1730 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 1731 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1732 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1733 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1734 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1735 <reboot into current> 1736 <do a "native" rebuild/install as described in the previous section> 1737 <maybe install compatibility libraries from ports/misc/compat*> 1738 <reboot> 1739 1740 1741 To upgrade in-place from stable to current 1742 ---------------------------------------------- 1743 <make sure you have good level 0 dumps> 1744 make buildworld [9] 1745 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1746 [1] 1747 <reboot in single user> [3] 1748 mergemaster -Fp [5] 1749 make installworld 1750 mergemaster -Fi [4] 1751 make delete-old [6] 1752 <reboot> 1753 1754 Make sure that you've read the UPDATING file to understand the 1755 tweaks to various things you need. At this point in the life 1756 cycle of current, things change often and you are on your own 1757 to cope. The defaults can also change, so please read ALL of 1758 the UPDATING entries. 1759 1760 Also, if you are tracking -current, you must be subscribed to 1761 freebsd-current@freebsd.org. Make sure that before you update 1762 your sources that you have read and understood all the recent 1763 messages there. If in doubt, please track -stable which has 1764 much fewer pitfalls. 1765 1766 [1] If you have third party modules, such as vmware, you 1767 should disable them at this point so they don't crash your 1768 system on reboot. 1769 1770 [3] From the bootblocks, boot -s, and then do 1771 fsck -p 1772 mount -u / 1773 mount -a 1774 cd src 1775 adjkerntz -i # if CMOS is wall time 1776 Also, when doing a major release upgrade, it is required that 1777 you boot into single user mode to do the installworld. 1778 1779 [4] Note: This step is non-optional. Failure to do this step 1780 can result in a significant reduction in the functionality of the 1781 system. Attempting to do it by hand is not recommended and those 1782 that pursue this avenue should read this file carefully, as well 1783 as the archives of freebsd-current and freebsd-hackers mailing lists 1784 for potential gotchas. The -U option is also useful to consider. 1785 See mergemaster(8) for more information. 1786 1787 [5] Usually this step is a noop. However, from time to time 1788 you may need to do this if you get unknown user in the following 1789 step. It never hurts to do it all the time. You may need to 1790 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1791 install) after the buildworld before this step if you last updated 1792 from current before 20130425 or from -stable before 20130430. 1793 1794 [6] This only deletes old files and directories. Old libraries 1795 can be deleted by "make delete-old-libs", but you have to make 1796 sure that no program is using those libraries anymore. 1797 1798 [8] The new kernel must be able to run existing binaries used by 1799 an installworld. When upgrading across major versions, the new 1800 kernel's configuration must include the correct COMPAT_FREEBSD<n> 1801 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x 1802 binaries). Failure to do so may leave you with a system that is 1803 hard to boot to recover. A GENERIC kernel will include suitable 1804 compatibility options to run binaries from older branches. 1805 1806 Make sure that you merge any new devices from GENERIC since the 1807 last time you updated your kernel config file. 1808 1809 [9] When checking out sources, you must include the -P flag to have 1810 cvs prune empty directories. 1811 1812 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1813 "?=" instead of the "=" assignment operator, so that buildworld can 1814 override the CPUTYPE if it needs to. 1815 1816 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1817 not on the command line, or in /etc/make.conf. buildworld will 1818 warn if it is improperly defined. 1819FORMAT: 1820 1821This file contains a list, in reverse chronological order, of major 1822breakages in tracking -current. It is not guaranteed to be a complete 1823list of such breakages, and only contains entries since September 23, 2011. 1824If you need to see UPDATING entries from before that date, you will need 1825to fetch an UPDATING file from an older FreeBSD release. 1826 1827Copyright information: 1828 1829Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1830 1831Redistribution, publication, translation and use, with or without 1832modification, in full or in part, in any form or format of this 1833document are permitted without further permission from the author. 1834 1835THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1836IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1837WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1838DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1839INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1840(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1841SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1842HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1843STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1844IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1845POSSIBILITY OF SUCH DAMAGE. 1846 1847Contact Warner Losh if you have any questions about your use of 1848this document. 1849 1850$FreeBSD: stable/11/UPDATING 346296 2019-04-16 20:05:24Z dim $ 1851