1Updating Information for FreeBSD current users. 2 3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4See end of file for further details. For commonly done items, please see the 5COMMON ITEMS: section later in the file. These instructions assume that you 6basically know what you are doing. If not, then please consult the FreeBSD 7handbook: 8 9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html 10 11Items affecting the ports and packages system can be found in 12/usr/ports/UPDATING. Please read that file before running portupgrade. 13 14NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping 15from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to 16the tip of head, and then rebuild without this option. The bootstrap process from 17older version of current across the gcc/clang cutover is a bit fragile. 18 19NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW: 20 FreeBSD 11.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 3420150210: 35 The autofs(4) ABI was changed in order to restore binary compatibility 36 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work 37 with the new kernel. 38 3920150131: 40 The powerpc64 kernel has been changed to a position-independent 41 executable. This can only be booted with a new version of loader(8), 42 so make sure to update both world and kernel before rebooting. 43 4420150118: 45 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix 46 only release, no new features have been added. Please see the 20141231 47 entry below for information about prerequisites and upgrading, if you 48 are not already using 3.5.0. 49 5020150107: 51 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now 52 taken from the ELF Tool Chain project rather than GNU binutils. They 53 should be drop-in replacements, with the addition of arm64 support. 54 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the 55 binutils tools, if necessary. 56 5720150105: 58 The default Unbound configuration now enables remote control 59 using a local socket. Users who have already enabled the 60 local_unbound service should regenerate their configuration 61 by running "service local_unbound setup" as root. 62 6320150102: 64 The GNU texinfo and GNU info pages have been removed. 65 To be able to view GNU info pages please install texinfo from ports. 66 6720141231: 68 Clang, llvm and lldb have been upgraded to 3.5.0 release. 69 70 As of this release, a prerequisite for building clang, llvm and lldb is 71 a C++11 capable compiler and C++11 standard library. This means that to 72 be able to successfully build the cross-tools stage of buildworld, with 73 clang as the bootstrap compiler, your system compiler or cross compiler 74 should either be clang 3.3 or later, or gcc 4.8 or later, and your 75 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or 76 later. 77 78 On any standard FreeBSD 10.x or 11.x installation, where clang and 79 libc++ are on by default (that is, on x86 or arm), this should work out 80 of the box. 81 82 On 9.x installations where clang is enabled by default, e.g. on x86 and 83 powerpc, libc++ will not be enabled by default, so libc++ should be 84 built (with clang) and installed first. If both clang and libc++ are 85 missing, build clang first, then use it to build libc++. 86 87 On 8.x and earlier installations, upgrade to 9.x first, and then follow 88 the instructions for 9.x above. 89 90 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by 91 default, and do not build clang. 92 93 Many embedded systems are resource constrained, and will not be able to 94 build clang in a reasonable time, or in some cases at all. In those 95 cases, cross building bootable systems on amd64 is a workaround. 96 97 This new version of clang introduces a number of new warnings, of which 98 the following are most likely to appear: 99 100 -Wabsolute-value 101 102 This warns in two cases, for both C and C++: 103 * When the code is trying to take the absolute value of an unsigned 104 quantity, which is effectively a no-op, and almost never what was 105 intended. The code should be fixed, if at all possible. If you are 106 sure that the unsigned quantity can be safely cast to signed, without 107 loss of information or undefined behavior, you can add an explicit 108 cast, or disable the warning. 109 110 * When the code is trying to take an absolute value, but the called 111 abs() variant is for the wrong type, which can lead to truncation. 112 If you want to disable the warning instead of fixing the code, please 113 make sure that truncation will not occur, or it might lead to unwanted 114 side-effects. 115 116 -Wtautological-undefined-compare and 117 -Wundefined-bool-conversion 118 119 These warn when C++ code is trying to compare 'this' against NULL, while 120 'this' should never be NULL in well-defined C++ code. However, there is 121 some legacy (pre C++11) code out there, which actively abuses this 122 feature, which was less strictly defined in previous C++ versions. 123 124 Squid and openjdk do this, for example. The warning can be turned off 125 for C++98 and earlier, but compiling the code in C++11 mode might result 126 in unexpected behavior; for example, the parts of the program that are 127 unreachable could be optimized away. 128 12920141222: 130 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER) 131 kernel sources have been removed. The .h files remain, since some 132 utilities include them. This will need to be fixed later. 133 If "mount -t oldnfs ..." is attempted, it will fail. 134 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used, 135 the utilities will report errors. 136 13720141121: 138 The handling of LOCAL_LIB_DIRS has been altered to skip addition of 139 directories to top level SUBDIR variable when their parent 140 directory is included in LOCAL_DIRS. Users with build systems with 141 such hierarchies and without SUBDIR entries in the parent 142 directory Makefiles should add them or add the directories to 143 LOCAL_DIRS. 144 14520141109: 146 faith(4) and faithd(8) have been removed from the base system. Faith 147 has been obsolete for a very long time. 148 14920141104: 150 vt(4), the new console driver, is enabled by default. It brings 151 support for Unicode and double-width characters, as well as 152 support for UEFI and integration with the KMS kernel video 153 drivers. 154 155 You may need to update your console settings in /etc/rc.conf, 156 most probably the keymap. During boot, /etc/rc.d/syscons will 157 indicate what you need to do. 158 159 vt(4) still has issues and lacks some features compared to 160 syscons(4). See the wiki for up-to-date information: 161 https://wiki.freebsd.org/Newcons 162 163 If you want to keep using syscons(4), you can do so by adding 164 the following line to /boot/loader.conf: 165 kern.vty=sc 166 16720141102: 168 pjdfstest has been integrated into kyua as an opt-in test suite. 169 Please see share/doc/pjdfstest/README for more details on how to 170 execute it. 171 17220141009: 173 gperf has been removed from the base system for architectures 174 that use clang. Ports that require gperf will obtain it from the 175 devel/gperf port. 176 17720140923: 178 pjdfstest has been moved from tools/regression/pjdfstest to 179 contrib/pjdfstest . 180 18120140922: 182 At svn r271982, The default linux compat kernel ABI has been adjusted 183 to 2.6.18 in support of the linux-c6 compat ports infrastructure 184 update. If you wish to continue using the linux-f10 compat ports, 185 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are 186 encouraged to update their linux-compat packages to linux-c6 during 187 their next update cycle. 188 18920140729: 190 The ofwfb driver, used to provide a graphics console on PowerPC when 191 using vt(4), no longer allows mmap() of all physical memory. This 192 will prevent Xorg on PowerPC with some ATI graphics cards from 193 initializing properly unless x11-servers/xorg-server is updated to 194 1.12.4_8 or newer. 195 19620140723: 197 The xdev targets have been converted to using TARGET and 198 TARGET_ARCH instead of XDEV and XDEV_ARCH. 199 20020140719: 201 The default unbound configuration has been modified to address 202 issues with reverse lookups on networks that use private 203 address ranges. If you use the local_unbound service, run 204 "service local_unbound setup" as root to regenerate your 205 configuration, then "service local_unbound reload" to load the 206 new configuration. 207 20820140709: 209 The GNU texinfo and GNU info pages are not built and installed 210 anymore, WITH_INFO knob has been added to allow to built and install 211 them again. 212 UPDATE: see 20150102 entry on texinfo's removal 213 21420140708: 215 The GNU readline library is now an INTERNALLIB - that is, it is 216 statically linked into consumers (GDB and variants) in the base 217 system, and the shared library is no longer installed. The 218 devel/readline port is available for third party software that 219 requires readline. 220 22120140702: 222 The Itanium architecture (ia64) has been removed from the list of 223 known architectures. This is the first step in the removal of the 224 architecture. 225 22620140701: 227 Commit r268115 has added NFSv4.1 server support, merged from 228 projects/nfsv4.1-server. Since this includes changes to the 229 internal interfaces between the NFS related modules, a full 230 build of the kernel and modules will be necessary. 231 __FreeBSD_version has been bumped. 232 23320140629: 234 The WITHOUT_VT_SUPPORT kernel config knob has been renamed 235 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning 236 which differs from the behaviour controlled by this knob.) 237 23820140619: 239 Maximal length of the serial number in CTL was increased from 16 to 240 64 chars, that breaks ABI. All CTL-related tools, such as ctladm 241 and ctld, need to be rebuilt to work with a new kernel. 242 24320140606: 244 The libatf-c and libatf-c++ major versions were downgraded to 0 and 245 1 respectively to match the upstream numbers. They were out of 246 sync because, when they were originally added to FreeBSD, the 247 upstream versions were not respected. These libraries are private 248 and not yet built by default, so renumbering them should be a 249 non-issue. However, unclean source trees will yield broken test 250 programs once the operator executes "make delete-old-libs" after a 251 "make installworld". 252 253 Additionally, the atf-sh binary was made private by moving it into 254 /usr/libexec/. Already-built shell test programs will keep the 255 path to the old binary so they will break after "make delete-old" 256 is run. 257 258 If you are using WITH_TESTS=yes (not the default), wipe the object 259 tree and rebuild from scratch to prevent spurious test failures. 260 This is only needed once: the misnumbered libraries and misplaced 261 binaries have been added to OptionalObsoleteFiles.inc so they will 262 be removed during a clean upgrade. 263 26420140512: 265 Clang and llvm have been upgraded to 3.4.1 release. 266 26720140508: 268 We bogusly installed src.opts.mk in /usr/share/mk. This file should 269 be removed to avoid issues in the future (and has been added to 270 ObsoleteFiles.inc). 271 27220140505: 273 /etc/src.conf now affects only builds of the FreeBSD src tree. In the 274 past, it affected all builds that used the bsd.*.mk files. The old 275 behavior was a bug, but people may have relied upon it. To get this 276 behavior back, you can .include /etc/src.conf from /etc/make.conf 277 (which is still global and isn't changed). This also changes the 278 behavior of incremental builds inside the tree of individual 279 directories. Set MAKESYSPATH to ".../share/mk" to do that. 280 Although this has survived make universe and some upgrade scenarios, 281 other upgrade scenarios may have broken. At least one form of 282 temporary breakage was fixed with MAKESYSPATH settings for buildworld 283 as well... In cases where MAKESYSPATH isn't working with this 284 setting, you'll need to set it to the full path to your tree. 285 286 One side effect of all this cleaning up is that bsd.compiler.mk 287 is no longer implicitly included by bsd.own.mk. If you wish to 288 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk 289 as well. 290 29120140430: 292 The lindev device has been removed since /dev/full has been made a 293 standard device. __FreeBSD_version has been bumped. 294 29520140418: 296 The YES_HESIOD knob has been removed. It has been obsolete for 297 a decade. Please move to using WITH_HESIOD instead or your builds 298 will silently lack HESIOD. 299 30020140405: 301 The uart(4) driver has been changed with respect to its handling 302 of the low-level console. Previously the uart(4) driver prevented 303 any process from changing the baudrate or the CLOCAL and HUPCL 304 control flags. By removing the restrictions, operators can make 305 changes to the serial console port without having to reboot. 306 However, when getty(8) is started on the serial device that is 307 associated with the low-level console, a misconfigured terminal 308 line in /etc/ttys will now have a real impact. 309 Before upgrading the kernel, make sure that /etc/ttys has the 310 serial console device configured as 3wire without baudrate to 311 preserve the previous behaviour. E.g: 312 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure 313 31420140306: 315 Support for libwrap (TCP wrappers) in rpcbind was disabled by default 316 to improve performance. To re-enable it, if needed, run rpcbind 317 with command line option -W. 318 31920140226: 320 Switched back to the GPL dtc compiler due to updates in the upstream 321 dts files not being supported by the BSDL dtc compiler. You will need 322 to rebuild your kernel toolchain to pick up the new compiler. Core dumps 323 may result while building dtb files during a kernel build if you fail 324 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler. 325 32620140216: 327 Clang and llvm have been upgraded to 3.4 release. 328 32920140216: 330 The nve(4) driver has been removed. Please use the nfe(4) driver 331 for NVIDIA nForce MCP Ethernet adapters instead. 332 33320140212: 334 An ABI incompatibility crept into the libc++ 3.4 import in r261283. 335 This could cause certain C++ applications using shared libraries built 336 against the previous version of libc++ to crash. The incompatibility 337 has now been fixed, but any C++ applications or shared libraries built 338 between r261283 and r261801 should be recompiled. 339 34020140204: 341 OpenSSH will now ignore errors caused by kernel lacking of Capsicum 342 capability mode support. Please note that enabling the feature in 343 kernel is still highly recommended. 344 34520140131: 346 OpenSSH is now built with sandbox support, and will use sandbox as 347 the default privilege separation method. This requires Capsicum 348 capability mode support in kernel. 349 35020140128: 351 The libelf and libdwarf libraries have been updated to newer 352 versions from upstream. Shared library version numbers for 353 these two libraries were bumped. Any ports or binaries 354 requiring these two libraries should be recompiled. 355 __FreeBSD_version is bumped to 1100006. 356 35720140110: 358 If a Makefile in a tests/ directory was auto-generating a Kyuafile 359 instead of providing an explicit one, this would prevent such 360 Makefile from providing its own Kyuafile in the future during 361 NO_CLEAN builds. This has been fixed in the Makefiles but manual 362 intervention is needed to clean an objdir if you use NO_CLEAN: 363 # find /usr/obj -name Kyuafile | xargs rm -f 364 36520131213: 366 The behavior of gss_pseudo_random() for the krb5 mechanism 367 has changed, for applications requesting a longer random string 368 than produced by the underlying enctype's pseudo-random() function. 369 In particular, the random string produced from a session key of 370 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will 371 be different at the 17th octet and later, after this change. 372 The counter used in the PRF+ construction is now encoded as a 373 big-endian integer in accordance with RFC 4402. 374 __FreeBSD_version is bumped to 1100004. 375 37620131108: 377 The WITHOUT_ATF build knob has been removed and its functionality 378 has been subsumed into the more generic WITHOUT_TESTS. If you were 379 using the former to disable the build of the ATF libraries, you 380 should change your settings to use the latter. 381 38220131025: 383 The default version of mtree is nmtree which is obtained from 384 NetBSD. The output is generally the same, but may vary 385 slightly. If you found you need identical output adding 386 "-F freebsd9" to the command line should do the trick. For the 387 time being, the old mtree is available as fmtree. 388 38920131014: 390 libbsdyml has been renamed to libyaml and moved to /usr/lib/private. 391 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg 392 1.1.4_8 and verify bsdyml not linked in, before running "make 393 delete-old-libs": 394 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean 395 or 396 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml 397 39820131010: 399 The rc.d/jail script has been updated to support jail(8) 400 configuration file. The "jail_<jname>_*" rc.conf(5) variables 401 for per-jail configuration are automatically converted to 402 /var/run/jail.<jname>.conf before the jail(8) utility is invoked. 403 This is transparently backward compatible. See below about some 404 incompatibilities and rc.conf(5) manual page for more details. 405 406 These variables are now deprecated in favor of jail(8) configuration 407 file. One can use "rc.d/jail config <jname>" command to generate 408 a jail(8) configuration file in /var/run/jail.<jname>.conf without 409 running the jail(8) utility. The default pathname of the 410 configuration file is /etc/jail.conf and can be specified by 411 using $jail_conf or $jail_<jname>_conf variables. 412 413 Please note that jail_devfs_ruleset accepts an integer at 414 this moment. Please consider to rewrite the ruleset name 415 with an integer. 416 41720130930: 418 BIND has been removed from the base system. If all you need 419 is a local resolver, simply enable and start the local_unbound 420 service instead. Otherwise, several versions of BIND are 421 available in the ports tree. The dns/bind99 port is one example. 422 423 With this change, nslookup(1) and dig(1) are no longer in the base 424 system. Users should instead use host(1) and drill(1) which are 425 in the base system. Alternatively, nslookup and dig can 426 be obtained by installing the dns/bind-tools port. 427 42820130916: 429 With the addition of unbound(8), a new unbound user is now 430 required during installworld. "mergemaster -p" can be used to 431 add the user prior to installworld, as documented in the handbook. 432 43320130911: 434 OpenSSH is now built with DNSSEC support, and will by default 435 silently trust signed SSHFP records. This can be controlled with 436 the VerifyHostKeyDNS client configuration setting. DNSSEC support 437 can be disabled entirely with the WITHOUT_LDNS option in src.conf. 438 43920130906: 440 The GNU Compiler Collection and C++ standard library (libstdc++) 441 are no longer built by default on platforms where clang is the system 442 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX 443 options in src.conf. 444 44520130905: 446 The PROCDESC kernel option is now part of the GENERIC kernel 447 configuration and is required for the rwhod(8) to work. 448 If you are using custom kernel configuration, you should include 449 'options PROCDESC'. 450 45120130905: 452 The API and ABI related to the Capsicum framework was modified 453 in backward incompatible way. The userland libraries and programs 454 have to be recompiled to work with the new kernel. This includes the 455 following libraries and programs, but the whole buildworld is 456 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl, 457 kdump, procstat, rwho, rwhod, uniq. 458 45920130903: 460 AES-NI intrinsic support has been added to gcc. The AES-NI module 461 has been updated to use this support. A new gcc is required to build 462 the aesni module on both i386 and amd64. 463 46420130821: 465 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices. 466 Thus "device padlock_rng" and "device rdrand_rng" should be 467 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG". 468 46920130813: 470 WITH_ICONV has been split into two feature sets. WITH_ICONV now 471 enables just the iconv* functionality and is now on by default. 472 WITH_LIBICONV_COMPAT enables the libiconv api and link time 473 compatability. Set WITHOUT_ICONV to build the old way. 474 If you have been using WITH_ICONV before, you will very likely 475 need to turn on WITH_LIBICONV_COMPAT. 476 47720130806: 478 INVARIANTS option now enables DEBUG for code with OpenSolaris and 479 Illumos origin, including ZFS. If you have INVARIANTS in your 480 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG 481 explicitly. 482 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS) 483 locks if WITNESS option was set. Because that generated a lot of 484 witness(9) reports and all of them were believed to be false 485 positives, this is no longer done. New option OPENSOLARIS_WITNESS 486 can be used to achieve the previous behavior. 487 48820130806: 489 Timer values in IPv6 data structures now use time_uptime instead 490 of time_second. Although this is not a user-visible functional 491 change, userland utilities which directly use them---ndp(8), 492 rtadvd(8), and rtsold(8) in the base system---need to be updated 493 to r253970 or later. 494 49520130802: 496 find -delete can now delete the pathnames given as arguments, 497 instead of only files found below them or if the pathname did 498 not contain any slashes. Formerly, the following error message 499 would result: 500 501 find: -delete: <path>: relative path potentially not safe 502 503 Deleting the pathnames given as arguments can be prevented 504 without error messages using -mindepth 1 or by changing 505 directory and passing "." as argument to find. This works in the 506 old as well as the new version of find. 507 50820130726: 509 Behavior of devfs rules path matching has been changed. 510 Pattern is now always matched against fully qualified devfs 511 path and slash characters must be explicitly matched by 512 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs 513 subdirectories must be reviewed. 514 51520130716: 516 The default ARM ABI has changed to the ARM EABI. The old ABI is 517 incompatible with the ARM EABI and all programs and modules will 518 need to be rebuilt to work with a new kernel. 519 520 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set. 521 522 NOTE: Support for the old ABI will be removed in the future and 523 users are advised to upgrade. 524 52520130709: 526 pkg_install has been disconnected from the build if you really need it 527 you should add WITH_PKGTOOLS in your src.conf(5). 528 52920130709: 530 Most of network statistics structures were changed to be able 531 keep 64-bits counters. Thus all tools, that work with networking 532 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.) 533 53420130629: 535 Fix targets that run multiple make's to use && rather than ; 536 so that subsequent steps depend on success of previous. 537 538 NOTE: if building 'universe' with -j* on stable/8 or stable/9 539 it would be better to start the build using bmake, to avoid 540 overloading the machine. 541 54220130618: 543 Fix a bug that allowed a tracing process (e.g. gdb) to write 544 to a memory-mapped file in the traced process's address space 545 even if neither the traced process nor the tracing process had 546 write access to that file. 547 54820130615: 549 CVS has been removed from the base system. An exact copy 550 of the code is available from the devel/cvs port. 551 55220130613: 553 Some people report the following error after the switch to bmake: 554 555 make: illegal option -- J 556 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable] 557 ... 558 *** [buildworld] Error code 2 559 560 this likely due to an old instance of make in 561 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE}) 562 which src/Makefile will use that blindly, if it exists, so if 563 you see the above error: 564 565 rm -rf `make -V MAKEPATH` 566 567 should resolve it. 568 56920130516: 570 Use bmake by default. 571 Whereas before one could choose to build with bmake via 572 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old 573 make. The goal is to remove these knobs for 10-RELEASE. 574 575 It is worth noting that bmake (like gmake) treats the command 576 line as the unit of failure, rather than statements within the 577 command line. Thus '(cd some/where && dosomething)' is safer 578 than 'cd some/where; dosomething'. The '()' allows consistent 579 behavior in parallel build. 580 58120130429: 582 Fix a bug that allows NFS clients to issue READDIR on files. 583 58420130426: 585 The WITHOUT_IDEA option has been removed because 586 the IDEA patent expired. 587 58820130426: 589 The sysctl which controls TRIM support under ZFS has been renamed 590 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been 591 enabled by default. 592 59320130425: 594 The mergemaster command now uses the default MAKEOBJDIRPREFIX 595 rather than creating it's own in the temporary directory in 596 order allow access to bootstrapped versions of tools such as 597 install and mtree. When upgrading from version of FreeBSD where 598 the install command does not support -l, you will need to 599 install a new mergemaster command if mergemaster -p is required. 600 This can be accomplished with the command (cd src/usr.sbin/mergemaster 601 && make install). 602 60320130404: 604 Legacy ATA stack, disabled and replaced by new CAM-based one since 605 FreeBSD 9.0, completely removed from the sources. Kernel modules 606 atadisk and atapi*, user-level tools atacontrol and burncd are 607 removed. Kernel option `options ATA_CAM` is now permanently enabled 608 and removed. 609 61020130319: 611 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2) 612 and socketpair(2). Software, in particular Kerberos, may 613 automatically detect and use these during building. The resulting 614 binaries will not work on older kernels. 615 61620130308: 617 CTL_DISABLE has also been added to the sparc64 GENERIC (for further 618 information, see the respective 20130304 entry). 619 62020130304: 621 Recent commits to callout(9) changed the size of struct callout, 622 so the KBI is probably heavily disturbed. Also, some functions 623 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced 624 by macros. Every kernel module using it won't load, so rebuild 625 is requested. 626 627 The ctl device has been re-enabled in GENERIC for i386 and amd64, 628 but does not initialize by default (because of the new CTL_DISABLE 629 option) to save memory. To re-enable it, remove the CTL_DISABLE 630 option from the kernel config file or set kern.cam.ctl.disable=0 631 in /boot/loader.conf. 632 63320130301: 634 The ctl device has been disabled in GENERIC for i386 and amd64. 635 This was done due to the extra memory being allocated at system 636 initialisation time by the ctl driver which was only used if 637 a CAM target device was created. This makes a FreeBSD system 638 unusable on 128MB or less of RAM. 639 64020130208: 641 A new compression method (lz4) has been merged to -HEAD. Please 642 refer to zpool-features(7) for more information. 643 644 Please refer to the "ZFS notes" section of this file for information 645 on upgrading boot ZFS pools. 646 64720130129: 648 A BSD-licensed patch(1) variant has been added and is installed 649 as bsdpatch, being the GNU version the default patch. 650 To inverse the logic and use the BSD-licensed one as default, 651 while having the GNU version installed as gnupatch, rebuild 652 and install world with the WITH_BSD_PATCH knob set. 653 65420130121: 655 Due to the use of the new -l option to install(1) during build 656 and install, you must take care not to directly set the INSTALL 657 make variable in your /etc/make.conf, /etc/src.conf, or on the 658 command line. If you wish to use the -C flag for all installs 659 you may be able to add INSTALL+=-C to /etc/make.conf or 660 /etc/src.conf. 661 66220130118: 663 The install(1) option -M has changed meaning and now takes an 664 argument that is a file or path to append logs to. In the 665 unlikely event that -M was the last option on the command line 666 and the command line contained at least two files and a target 667 directory the first file will have logs appended to it. The -M 668 option served little practical purpose in the last decade so its 669 use is expected to be extremely rare. 670 67120121223: 672 After switching to Clang as the default compiler some users of ZFS 673 on i386 systems started to experience stack overflow kernel panics. 674 Please consider using 'options KSTACK_PAGES=4' in such configurations. 675 67620121222: 677 GEOM_LABEL now mangles label names read from file system metadata. 678 Mangling affect labels containing spaces, non-printable characters, 679 '%' or '"'. Device names in /etc/fstab and other places may need to 680 be updated. 681 68220121217: 683 By default, only the 10 most recent kernel dumps will be saved. To 684 restore the previous behaviour (no limit on the number of kernel dumps 685 stored in the dump directory) add the following line to /etc/rc.conf: 686 687 savecore_flags="" 688 68920121201: 690 With the addition of auditdistd(8), a new auditdistd user is now 691 required during installworld. "mergemaster -p" can be used to 692 add the user prior to installworld, as documented in the handbook. 693 69420121117: 695 The sin6_scope_id member variable in struct sockaddr_in6 is now 696 filled by the kernel before passing the structure to the userland via 697 sysctl or routing socket. This means the KAME-specific embedded scope 698 id in sin6_addr.s6_addr[2] is always cleared in userland application. 699 This behavior can be controlled by net.inet6.ip6.deembed_scopeid. 700 __FreeBSD_version is bumped to 1000025. 701 70220121105: 703 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default. 704 This means that the world and kernel will be compiled with clang 705 and that clang will be installed as /usr/bin/cc, /usr/bin/c++, 706 and /usr/bin/cpp. To disable this behavior and revert to building 707 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions 708 of current may need to bootstrap WITHOUT_CLANG first if the clang 709 build fails (its compatibility window doesn't extend to the 9 stable 710 branch point). 711 71220121102: 713 The IPFIREWALL_FORWARD kernel option has been removed. Its 714 functionality now turned on by default. 715 71620121023: 717 The ZERO_COPY_SOCKET kernel option has been removed and 718 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP. 719 NB: SOCKET_SEND_COW uses the VM page based copy-on-write 720 mechanism which is not safe and may result in kernel crashes. 721 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current 722 driver supports disposeable external page sized mbuf storage. 723 Proper replacements for both zero-copy mechanisms are under 724 consideration and will eventually lead to complete removal 725 of the two kernel options. 726 72720121023: 728 The IPv4 network stack has been converted to network byte 729 order. The following modules need to be recompiled together 730 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4), 731 pf(4), ipfw(4), ng_ipfw(4), stf(4). 732 73320121022: 734 Support for non-MPSAFE filesystems was removed from VFS. The 735 VFS_VERSION was bumped, all filesystem modules shall be 736 recompiled. 737 73820121018: 739 All the non-MPSAFE filesystems have been disconnected from 740 the build. The full list includes: codafs, hpfs, ntfs, nwfs, 741 portalfs, smbfs, xfs. 742 74320121016: 744 The interface cloning API and ABI has changed. The following 745 modules need to be recompiled together with kernel: 746 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4), 747 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4), 748 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4). 749 75020121015: 751 The sdhci driver was split in two parts: sdhci (generic SD Host 752 Controller logic) and sdhci_pci (actual hardware driver). 753 No kernel config modifications are required, but if you 754 load sdhc as a module you must switch to sdhci_pci instead. 755 75620121014: 757 Import the FUSE kernel and userland support into base system. 758 75920121013: 760 The GNU sort(1) program has been removed since the BSD-licensed 761 sort(1) has been the default for quite some time and no serious 762 problems have been reported. The corresponding WITH_GNU_SORT 763 knob has also gone. 764 76520121006: 766 The pfil(9) API/ABI for AF_INET family has been changed. Packet 767 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled 768 with new kernel. 769 77020121001: 771 The net80211(4) ABI has been changed to allow for improved driver 772 PS-POLL and power-save support. All wireless drivers need to be 773 recompiled to work with the new kernel. 774 77520120913: 776 The random(4) support for the VIA hardware random number 777 generator (`PADLOCK') is no longer enabled unconditionally. 778 Add the padlock_rng device in the custom kernel config if 779 needed. The GENERIC kernels on i386 and amd64 do include the 780 device, so the change only affects the custom kernel 781 configurations. 782 78320120908: 784 The pf(4) packet filter ABI has been changed. pfctl(8) and 785 snmp_pf module need to be recompiled to work with new kernel. 786 78720120828: 788 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged 789 to -HEAD. Pools that have empty_bpobj in active state can not be 790 imported read-write with ZFS implementations that do not support 791 this feature. For more information read the zpool-features(5) 792 manual page. 793 79420120727: 795 The sparc64 ZFS loader has been changed to no longer try to auto- 796 detect ZFS providers based on diskN aliases but now requires these 797 to be explicitly listed in the OFW boot-device environment variable. 798 79920120712: 800 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring 801 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are 802 configuration changes. Make sure to merge /etc/ssl/openssl.cnf. 803 80420120712: 805 The following sysctls and tunables have been renamed for consistency 806 with other variables: 807 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered 808 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered 809 81020120628: 811 The sort utility has been replaced with BSD sort. For now, GNU sort 812 is also available as "gnusort" or the default can be set back to 813 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be 814 installed as "bsdsort". 815 81620120611: 817 A new version of ZFS (pool version 5000) has been merged to -HEAD. 818 Starting with this version the old system of ZFS pool versioning 819 is superseded by "feature flags". This concept enables forward 820 compatibility against certain future changes in functionality of ZFS 821 pools. The first read-only compatible "feature flag" for ZFS pools 822 is named "com.delphix:async_destroy". For more information 823 read the new zpool-features(5) manual page. 824 Please refer to the "ZFS notes" section of this file for information 825 on upgrading boot ZFS pools. 826 82720120417: 828 The malloc(3) implementation embedded in libc now uses sources imported 829 as contrib/jemalloc. The most disruptive API change is to 830 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf, 831 delete it prior to installworld, and optionally re-create it using the 832 new format after rebooting. See malloc.conf(5) for details 833 (specifically the TUNING section and the "opt.*" entries in the MALLCTL 834 NAMESPACE section). 835 83620120328: 837 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb 838 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is 839 now spelled mips. This is to aid compatibility with third-party 840 software that expects this naming scheme in uname(3). Little-endian 841 settings are unchanged. If you are updating a big-endian mips64 machine 842 from before this change, you may need to set MACHINE_ARCH=mips64 in 843 your environment before the new build system will recognize your machine. 844 84520120306: 846 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported 847 platforms. 848 84920120229: 850 Now unix domain sockets behave "as expected" on nullfs(5). Previously 851 nullfs(5) did not pass through all behaviours to the underlying layer, 852 as a result if we bound to a socket on the lower layer we could connect 853 only to the lower path; if we bound to the upper layer we could connect 854 only to the upper path. The new behavior is one can connect to both the 855 lower and the upper paths regardless what layer path one binds to. 856 85720120211: 858 The getifaddrs upgrade path broken with 20111215 has been restored. 859 If you have upgraded in between 20111215 and 20120209 you need to 860 recompile libc again with your kernel. You still need to recompile 861 world to be able to configure CARP but this restriction already 862 comes from 20111215. 863 86420120114: 865 The set_rcvar() function has been removed from /etc/rc.subr. All 866 base and ports rc.d scripts have been updated, so if you have a 867 port installed with a script in /usr/local/etc/rc.d you can either 868 hand-edit the rcvar= line, or reinstall the port. 869 870 An easy way to handle the mass-update of /etc/rc.d: 871 rm /etc/rc.d/* && mergemaster -i 872 87320120109: 874 panic(9) now stops other CPUs in the SMP systems, disables interrupts 875 on the current CPU and prevents other threads from running. 876 This behavior can be reverted using the kern.stop_scheduler_on_panic 877 tunable/sysctl. 878 The new behavior can be incompatible with kern.sync_on_panic. 879 88020111215: 881 The carp(4) facility has been changed significantly. Configuration 882 of the CARP protocol via ifconfig(8) has changed, as well as format 883 of CARP events submitted to devd(8) has changed. See manual pages 884 for more information. The arpbalance feature of carp(4) is currently 885 not supported anymore. 886 887 Size of struct in_aliasreq, struct in6_aliasreq has changed. User 888 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), 889 need to be recompiled. 890 89120111122: 892 The acpi_wmi(4) status device /dev/wmistat has been renamed to 893 /dev/wmistat0. 894 89520111108: 896 The option VFS_ALLOW_NONMPSAFE option has been added in order to 897 explicitely support non-MPSAFE filesystems. 898 It is on by default for all supported platform at this present 899 time. 900 90120111101: 902 The broken amd(4) driver has been replaced with esp(4) in the amd64, 903 i386 and pc98 GENERIC kernel configuration files. 904 90520110930: 906 sysinstall has been removed 907 90820110923: 909 The stable/9 branch created in subversion. This corresponds to the 910 RELENG_9 branch in CVS. 911 912COMMON ITEMS: 913 914 General Notes 915 ------------- 916 Avoid using make -j when upgrading. While generally safe, there are 917 sometimes problems using -j to upgrade. If your upgrade fails with 918 -j, please try again without -j. From time to time in the past there 919 have been problems using -j with buildworld and/or installworld. This 920 is especially true when upgrading between "distant" versions (eg one 921 that cross a major release boundary or several minor releases, or when 922 several months have passed on the -current branch). 923 924 Sometimes, obscure build problems are the result of environment 925 poisoning. This can happen because the make utility reads its 926 environment when searching for values for global variables. To run 927 your build attempts in an "environmental clean room", prefix all make 928 commands with 'env -i '. See the env(1) manual page for more details. 929 930 When upgrading from one major version to another it is generally best 931 to upgrade to the latest code in the currently installed branch first, 932 then do an upgrade to the new branch. This is the best-tested upgrade 933 path, and has the highest probability of being successful. Please try 934 this approach before reporting problems with a major version upgrade. 935 936 When upgrading a live system, having a root shell around before 937 installing anything can help undo problems. Not having a root shell 938 around can lead to problems if pam has changed too much from your 939 starting point to allow continued authentication after the upgrade. 940 941 ZFS notes 942 --------- 943 When upgrading the boot ZFS pool to a new version, always follow 944 these two steps: 945 946 1.) recompile and reinstall the ZFS boot loader and boot block 947 (this is part of "make buildworld" and "make installworld") 948 949 2.) update the ZFS boot block on your boot drive 950 951 The following example updates the ZFS boot block on the first 952 partition (freebsd-boot) of a GPT partitioned drive ada0: 953 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0" 954 955 Non-boot pools do not need these updates. 956 957 To build a kernel 958 ----------------- 959 If you are updating from a prior version of FreeBSD (even one just 960 a few days old), you should follow this procedure. It is the most 961 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld, 962 963 make kernel-toolchain 964 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE 965 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE 966 967 To test a kernel once 968 --------------------- 969 If you just want to boot a kernel once (because you are not sure 970 if it works, or if you want to boot a known bad kernel to provide 971 debugging information) run 972 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel 973 nextboot -k testkernel 974 975 To just build a kernel when you know that it won't mess you up 976 -------------------------------------------------------------- 977 This assumes you are already running a CURRENT system. Replace 978 ${arch} with the architecture of your machine (e.g. "i386", 979 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc). 980 981 cd src/sys/${arch}/conf 982 config KERNEL_NAME_HERE 983 cd ../compile/KERNEL_NAME_HERE 984 make depend 985 make 986 make install 987 988 If this fails, go to the "To build a kernel" section. 989 990 To rebuild everything and install it on the current system. 991 ----------------------------------------------------------- 992 # Note: sometimes if you are running current you gotta do more than 993 # is listed here if you are upgrading from a really old current. 994 995 <make sure you have good level 0 dumps> 996 make buildworld 997 make kernel KERNCONF=YOUR_KERNEL_HERE 998 [1] 999 <reboot in single user> [3] 1000 mergemaster -Fp [5] 1001 make installworld 1002 mergemaster -Fi [4] 1003 make delete-old [6] 1004 <reboot> 1005 1006 To cross-install current onto a separate partition 1007 -------------------------------------------------- 1008 # In this approach we use a separate partition to hold 1009 # current's root, 'usr', and 'var' directories. A partition 1010 # holding "/", "/usr" and "/var" should be about 2GB in 1011 # size. 1012 1013 <make sure you have good level 0 dumps> 1014 <boot into -stable> 1015 make buildworld 1016 make buildkernel KERNCONF=YOUR_KERNEL_HERE 1017 <maybe newfs current's root partition> 1018 <mount current's root partition on directory ${CURRENT_ROOT}> 1019 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC 1020 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd 1021 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT} 1022 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd 1023 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition> 1024 <reboot into current> 1025 <do a "native" rebuild/install as described in the previous section> 1026 <maybe install compatibility libraries from ports/misc/compat*> 1027 <reboot> 1028 1029 1030 To upgrade in-place from stable to current 1031 ---------------------------------------------- 1032 <make sure you have good level 0 dumps> 1033 make buildworld [9] 1034 make kernel KERNCONF=YOUR_KERNEL_HERE [8] 1035 [1] 1036 <reboot in single user> [3] 1037 mergemaster -Fp [5] 1038 make installworld 1039 mergemaster -Fi [4] 1040 make delete-old [6] 1041 <reboot> 1042 1043 Make sure that you've read the UPDATING file to understand the 1044 tweaks to various things you need. At this point in the life 1045 cycle of current, things change often and you are on your own 1046 to cope. The defaults can also change, so please read ALL of 1047 the UPDATING entries. 1048 1049 Also, if you are tracking -current, you must be subscribed to 1050 freebsd-current@freebsd.org. Make sure that before you update 1051 your sources that you have read and understood all the recent 1052 messages there. If in doubt, please track -stable which has 1053 much fewer pitfalls. 1054 1055 [1] If you have third party modules, such as vmware, you 1056 should disable them at this point so they don't crash your 1057 system on reboot. 1058 1059 [3] From the bootblocks, boot -s, and then do 1060 fsck -p 1061 mount -u / 1062 mount -a 1063 cd src 1064 adjkerntz -i # if CMOS is wall time 1065 Also, when doing a major release upgrade, it is required that 1066 you boot into single user mode to do the installworld. 1067 1068 [4] Note: This step is non-optional. Failure to do this step 1069 can result in a significant reduction in the functionality of the 1070 system. Attempting to do it by hand is not recommended and those 1071 that pursue this avenue should read this file carefully, as well 1072 as the archives of freebsd-current and freebsd-hackers mailing lists 1073 for potential gotchas. The -U option is also useful to consider. 1074 See mergemaster(8) for more information. 1075 1076 [5] Usually this step is a noop. However, from time to time 1077 you may need to do this if you get unknown user in the following 1078 step. It never hurts to do it all the time. You may need to 1079 install a new mergemaster (cd src/usr.sbin/mergemaster && make 1080 install) after the buildworld before this step if you last updated 1081 from current before 20130425 or from -stable before 20130430. 1082 1083 [6] This only deletes old files and directories. Old libraries 1084 can be deleted by "make delete-old-libs", but you have to make 1085 sure that no program is using those libraries anymore. 1086 1087 [8] In order to have a kernel that can run the 4.x binaries needed to 1088 do an installworld, you must include the COMPAT_FREEBSD4 option in 1089 your kernel. Failure to do so may leave you with a system that is 1090 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is 1091 required to run the 5.x binaries on more recent kernels. And so on 1092 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. 1093 1094 Make sure that you merge any new devices from GENERIC since the 1095 last time you updated your kernel config file. 1096 1097 [9] When checking out sources, you must include the -P flag to have 1098 cvs prune empty directories. 1099 1100 If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1101 "?=" instead of the "=" assignment operator, so that buildworld can 1102 override the CPUTYPE if it needs to. 1103 1104 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1105 not on the command line, or in /etc/make.conf. buildworld will 1106 warn if it is improperly defined. 1107FORMAT: 1108 1109This file contains a list, in reverse chronological order, of major 1110breakages in tracking -current. It is not guaranteed to be a complete 1111list of such breakages, and only contains entries since October 10, 2007. 1112If you need to see UPDATING entries from before that date, you will need 1113to fetch an UPDATING file from an older FreeBSD release. 1114 1115Copyright information: 1116 1117Copyright 1998-2009 M. Warner Losh. All Rights Reserved. 1118 1119Redistribution, publication, translation and use, with or without 1120modification, in full or in part, in any form or format of this 1121document are permitted without further permission from the author. 1122 1123THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR 1124IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED 1125WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 1126DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT, 1127INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES 1128(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 1129SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 1130HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, 1131STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING 1132IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 1133POSSIBILITY OF SUCH DAMAGE. 1134 1135Contact Warner Losh if you have any questions about your use of 1136this document. 1137 1138$FreeBSD$ 1139