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