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