1 Updating Information for FreeBSD current users.
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16 the tip of head, and then rebuild without this option. The bootstrap process
17 from older version of current across the gcc/clang cutover is a bit fragile.
19 NOTE 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".)
35 Debug data files are now built by default with 'make buildworld' and
36 installed with 'make installworld'. This facilitates debugging but
37 requires more disk space both during the build and for the installed
38 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
42 r291527 changed the internal interface between the nfsd.ko and
43 nfscommon.ko modules. As such, they must both be upgraded to-gether.
44 __FreeBSD_version has been bumped because of this.
47 Add support for unicode collation strings leads to a change of
48 order of files listed by ls(1) for example. To get back to the old
49 behaviour, set LC_COLLATE environment variable to "C".
51 Databases administrators will need to reindex their databases given
52 collation results will be different.
54 Due to a bug in install(1) it is recommended to remove the ancient
55 locales before running make installworld.
57 rm -rf /usr/share/locale/*
60 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
61 libcrypto.so.7 or libssl.so.7 must be recompiled.
64 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
65 Kernel modules isp_2400_multi and isp_2500_multi were removed and
66 should be replaced with isp_2400 and isp_2500 modules respectively.
69 The build previously allowed using 'make -n' to not recurse into
70 sub-directories while showing what commands would be executed, and
71 'make -n -n' to recursively show commands. Now 'make -n' will recurse
72 and 'make -N' will not.
75 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
76 and etcupdate will now use this file. A custom sendmail.cf is now
77 updated via this mechanism rather than via installworld. If you had
78 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
79 want to remove the exclusion or change it to "always install".
80 /etc/mail/sendmail.cf is now managed the same way regardless of
81 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
82 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
85 Compatibility shims for legacy ATA device names have been removed.
86 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
87 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
88 environment variables, /dev/ad* and /dev/ar* symbolic links.
91 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
92 Please see the 20141231 entry below for information about prerequisites
93 and upgrading, if you are not already using clang 3.5.0 or higher.
96 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
97 and renamed from .symbols to .debug. This reduces the size requirements
98 on the boot partition or file system and provides consistency with
101 When using the supported kernel installation method the
102 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
103 as is done with /boot/kernel.
105 Developers wishing to maintain the historical behavior of installing
106 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
109 The wireless drivers had undergone changes that remove the 'parent
110 interface' from the ifconfig -l output. The rc.d network scripts
111 used to check presence of a parent interface in the list, so old
112 scripts would fail to start wireless networking. Thus, etcupdate(3)
113 or mergemaster(8) run is required after kernel update, to update your
114 rc.d scripts in /etc.
117 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
118 These configurations are now automatically interpreted as
119 'scrub fragment reassemble'.
122 Kernel-loadable modules for the random(4) device are back. To use
123 them, the kernel must have
126 options RANDOM_LOADABLE
128 kldload(8) can then be used to load random_fortuna.ko
129 or random_yarrow.ko. Please note that due to the indirect
130 function calls that the loadable modules need to provide,
131 the build-in variants will be slightly more efficient.
133 The random(4) kernel option RANDOM_DUMMY has been retired due to
134 unpopularity. It was not all that useful anyway.
137 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
138 Control over building the ELF Tool Chain tools is now provided by
139 the WITHOUT_TOOLCHAIN knob.
142 The polarity of Pulse Per Second (PPS) capture events with the
143 uart(4) driver has been corrected. Prior to this change the PPS
144 "assert" event corresponded to the trailing edge of a positive PPS
145 pulse and the "clear" event was the leading edge of the next pulse.
147 As the width of a PPS pulse in a typical GPS receiver is on the
148 order of 1 millisecond, most users will not notice any significant
149 difference with this change.
151 Anyone who has compensated for the historical polarity reversal by
152 configuring a negative offset equal to the pulse width will need to
153 remove that workaround.
156 The default group assigned to /dev/dri entries has been changed
157 from 'wheel' to 'video' with the id of '44'. If you want to have
158 access to the dri devices please add yourself to the video group
161 # pw groupmod video -m $USER
164 The menu.rc and loader.rc files will now be replaced during
165 upgrades. Please migrate local changes to menu.rc.local and
166 loader.rc.local instead.
169 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
170 strings and strip have been removed. The src.conf(5) knob
171 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
174 As ZFS requires more kernel stack pages than is the default on some
175 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
176 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
178 Please consider using 'options KSTACK_PAGES=X' where X is greater
179 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
182 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
183 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
184 default, i.e., they will not contain "::". For example, instead
185 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
186 to have a more specific match, such as different map entries for
187 IPv6:0:0 vs IPv6:0. This change requires that configuration
188 data (including maps, files, classes, custom ruleset, etc.) must
189 use the same format, so make certain such configuration data is
190 upgrading. As a very simple check search for patterns like
191 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
192 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
193 the cf option UseCompressedIPv6Addresses.
196 The default kernel entropy-processing algorithm is now
197 Fortuna, replacing Yarrow.
199 Assuming you have 'device random' in your kernel config
200 file, the configurations allow a kernel option to override
201 this default. You may choose *ONE* of:
203 options RANDOM_YARROW # Legacy /dev/random algorithm.
204 options RANDOM_DUMMY # Blocking-only driver.
206 If you have neither, you get Fortuna. For most people,
207 read no further, Fortuna will give a /dev/random that works
208 like it always used to, and the difference will be irrelevant.
210 If you remove 'device random', you get *NO* kernel-processed
211 entropy at all. This may be acceptable to folks building
212 embedded systems, but has complications. Carry on reading,
213 and it is assumed you know what you need.
215 *PLEASE* read random(4) and random(9) if you are in the
216 habit of tweaking kernel configs, and/or if you are a member
217 of the embedded community, wanting specific and not-usual
218 behaviour from your security subsystems.
220 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
221 random', you will NOT have a functioning /dev/random, and
222 many cryptographic features will not work, including SSH.
223 You may also find strange behaviour from the random(3) set
224 of library functions, in particular sranddev(3), srandomdev(3)
225 and arc4random(3). The reason for this is that the KERN_ARND
226 sysctl only returns entropy if it thinks it has some to
227 share, and with RANDOM_DUMMY or no 'device random' this
231 An additional fix for the issue described in the 20150614 sendmail
232 entry below has been been committed in revision 284717.
235 FreeBSD's old make (fmake) has been removed from the system. It is
236 available as the devel/fmake port or via pkg install fmake.
239 The fix for the issue described in the 20150614 sendmail entry
240 below has been been committed in revision 284436. The work
241 around described in that entry is no longer needed unless the
242 default setting is overridden by a confDH_PARAMETERS configuration
243 setting of '5' or pointing to a 512 bit DH parameter file.
246 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
247 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
248 and devel/kyua to version 0.20+ and adjust any calling code to work
249 with Kyuafile and kyua.
252 The import of openssl to address the FreeBSD-SA-15:10.openssl
253 security advisory includes a change which rejects handshakes
254 with DH parameters below 768 bits. sendmail releases prior
255 to 8.15.2 (not yet released), defaulted to a 512 bit
256 DH parameter setting for client connections. To work around
257 this interoperability, sendmail can be configured to use a
258 2048 bit DH parameter by:
260 1. Edit /etc/mail/`hostname`.mc
261 2. If a setting for confDH_PARAMETERS does not exist or
262 exists and is set to a string beginning with '5',
264 3. If a setting for confDH_PARAMETERS exists and is set to
265 a file path, create a new file with:
266 openssl dhparam -out /path/to/file 2048
267 4. Rebuild the .cf file:
268 cd /etc/mail/; make; make install
270 cd /etc/mail/; make restart
272 A sendmail patch is coming, at which time this file will be
276 Generation of legacy formatted entries have been disabled by default
277 in pwd_mkdb(8), as all base system consumers of the legacy formatted
278 entries were converted to use the new format by default when the new,
279 machine independent format have been added and supported since FreeBSD
282 Please see the pwd_mkdb(8) manual page for further details.
285 Clang and llvm have been upgraded to 3.6.1 release. Please see the
286 20141231 entry below for information about prerequisites and upgrading,
287 if you are not already using 3.5.0 or higher.
290 TI platform code switched to using vendor DTS files and this update
291 may break existing systems running on Beaglebone, Beaglebone Black,
294 - dtb files should be regenerated/reinstalled. Filenames are the
295 same but content is different now
296 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
297 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
298 addressing scheme is now pin 25 on /dev/gpioc3.
299 - Pandaboard: /etc/ttys should be updated, serial console device is
300 now /dev/ttyu2, not /dev/ttyu0
303 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
304 If you need the GNU extension from groff soelim(1), install groff
305 from package: pkg install groff, or via ports: textproc/groff.
308 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
309 defined in symlink(7); previously symlinks were silently ignored.
312 The const qualifier has been removed from iconv(3) to comply with
313 POSIX. The ports tree is aware of this from r384038 onwards.
316 Libraries specified by LIBADD in Makefiles must have a corresponding
317 DPADD_<lib> variable to ensure correct dependencies. This is now
318 enforced in src.libnames.mk.
321 From legacy ata(4) driver was removed support for SATA controllers
322 supported by more functional drivers ahci(4), siis(4) and mvs(4).
323 Kernel modules ataahci and ataadaptec were removed completely,
324 replaced by ahci and mvs modules respectively.
327 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
328 the 20141231 entry below for information about prerequisites and
329 upgrading, if you are not already using 3.5.0 or higher.
332 The 32-bit PowerPC kernel has been changed to a position-independent
333 executable. This can only be booted with a version of loader(8)
334 newer than January 31, 2015, so make sure to update both world and
335 kernel before rebooting.
338 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
339 but before r278950, the RNG was not seeded properly. Immediately
340 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
341 ssh keys or openssl keys) that were generated w/ a kernel from that
342 range. This does not affect programs that directly used /dev/random
343 or /dev/urandom. All userland uses of arc4random(3) are affected.
346 The autofs(4) ABI was changed in order to restore binary compatibility
347 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
351 The powerpc64 kernel has been changed to a position-independent
352 executable. This can only be booted with a new version of loader(8),
353 so make sure to update both world and kernel before rebooting.
356 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
357 only release, no new features have been added. Please see the 20141231
358 entry below for information about prerequisites and upgrading, if you
359 are not already using 3.5.0.
362 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
363 taken from the ELF Tool Chain project rather than GNU binutils. They
364 should be drop-in replacements, with the addition of arm64 support.
365 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
366 binutils tools, if necessary. See 20150805 for updated information.
369 The default Unbound configuration now enables remote control
370 using a local socket. Users who have already enabled the
371 local_unbound service should regenerate their configuration
372 by running "service local_unbound setup" as root.
375 The GNU texinfo and GNU info pages have been removed.
376 To be able to view GNU info pages please install texinfo from ports.
379 Clang, llvm and lldb have been upgraded to 3.5.0 release.
381 As of this release, a prerequisite for building clang, llvm and lldb is
382 a C++11 capable compiler and C++11 standard library. This means that to
383 be able to successfully build the cross-tools stage of buildworld, with
384 clang as the bootstrap compiler, your system compiler or cross compiler
385 should either be clang 3.3 or later, or gcc 4.8 or later, and your
386 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
389 On any standard FreeBSD 10.x or 11.x installation, where clang and
390 libc++ are on by default (that is, on x86 or arm), this should work out
393 On 9.x installations where clang is enabled by default, e.g. on x86 and
394 powerpc, libc++ will not be enabled by default, so libc++ should be
395 built (with clang) and installed first. If both clang and libc++ are
396 missing, build clang first, then use it to build libc++.
398 On 8.x and earlier installations, upgrade to 9.x first, and then follow
399 the instructions for 9.x above.
401 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
402 default, and do not build clang.
404 Many embedded systems are resource constrained, and will not be able to
405 build clang in a reasonable time, or in some cases at all. In those
406 cases, cross building bootable systems on amd64 is a workaround.
408 This new version of clang introduces a number of new warnings, of which
409 the following are most likely to appear:
413 This warns in two cases, for both C and C++:
414 * When the code is trying to take the absolute value of an unsigned
415 quantity, which is effectively a no-op, and almost never what was
416 intended. The code should be fixed, if at all possible. If you are
417 sure that the unsigned quantity can be safely cast to signed, without
418 loss of information or undefined behavior, you can add an explicit
419 cast, or disable the warning.
421 * When the code is trying to take an absolute value, but the called
422 abs() variant is for the wrong type, which can lead to truncation.
423 If you want to disable the warning instead of fixing the code, please
424 make sure that truncation will not occur, or it might lead to unwanted
427 -Wtautological-undefined-compare and
428 -Wundefined-bool-conversion
430 These warn when C++ code is trying to compare 'this' against NULL, while
431 'this' should never be NULL in well-defined C++ code. However, there is
432 some legacy (pre C++11) code out there, which actively abuses this
433 feature, which was less strictly defined in previous C++ versions.
435 Squid and openjdk do this, for example. The warning can be turned off
436 for C++98 and earlier, but compiling the code in C++11 mode might result
437 in unexpected behavior; for example, the parts of the program that are
438 unreachable could be optimized away.
441 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
442 kernel sources have been removed. The .h files remain, since some
443 utilities include them. This will need to be fixed later.
444 If "mount -t oldnfs ..." is attempted, it will fail.
445 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
446 the utilities will report errors.
449 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
450 directories to top level SUBDIR variable when their parent
451 directory is included in LOCAL_DIRS. Users with build systems with
452 such hierarchies and without SUBDIR entries in the parent
453 directory Makefiles should add them or add the directories to
457 faith(4) and faithd(8) have been removed from the base system. Faith
458 has been obsolete for a very long time.
461 vt(4), the new console driver, is enabled by default. It brings
462 support for Unicode and double-width characters, as well as
463 support for UEFI and integration with the KMS kernel video
466 You may need to update your console settings in /etc/rc.conf,
467 most probably the keymap. During boot, /etc/rc.d/syscons will
468 indicate what you need to do.
470 vt(4) still has issues and lacks some features compared to
471 syscons(4). See the wiki for up-to-date information:
472 https://wiki.freebsd.org/Newcons
474 If you want to keep using syscons(4), you can do so by adding
475 the following line to /boot/loader.conf:
479 pjdfstest has been integrated into kyua as an opt-in test suite.
480 Please see share/doc/pjdfstest/README for more details on how to
484 gperf has been removed from the base system for architectures
485 that use clang. Ports that require gperf will obtain it from the
489 pjdfstest has been moved from tools/regression/pjdfstest to
493 At svn r271982, The default linux compat kernel ABI has been adjusted
494 to 2.6.18 in support of the linux-c6 compat ports infrastructure
495 update. If you wish to continue using the linux-f10 compat ports,
496 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
497 encouraged to update their linux-compat packages to linux-c6 during
498 their next update cycle.
501 The ofwfb driver, used to provide a graphics console on PowerPC when
502 using vt(4), no longer allows mmap() of all physical memory. This
503 will prevent Xorg on PowerPC with some ATI graphics cards from
504 initializing properly unless x11-servers/xorg-server is updated to
508 The xdev targets have been converted to using TARGET and
509 TARGET_ARCH instead of XDEV and XDEV_ARCH.
512 The default unbound configuration has been modified to address
513 issues with reverse lookups on networks that use private
514 address ranges. If you use the local_unbound service, run
515 "service local_unbound setup" as root to regenerate your
516 configuration, then "service local_unbound reload" to load the
520 The GNU texinfo and GNU info pages are not built and installed
521 anymore, WITH_INFO knob has been added to allow to built and install
523 UPDATE: see 20150102 entry on texinfo's removal
526 The GNU readline library is now an INTERNALLIB - that is, it is
527 statically linked into consumers (GDB and variants) in the base
528 system, and the shared library is no longer installed. The
529 devel/readline port is available for third party software that
533 The Itanium architecture (ia64) has been removed from the list of
534 known architectures. This is the first step in the removal of the
538 Commit r268115 has added NFSv4.1 server support, merged from
539 projects/nfsv4.1-server. Since this includes changes to the
540 internal interfaces between the NFS related modules, a full
541 build of the kernel and modules will be necessary.
542 __FreeBSD_version has been bumped.
545 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
546 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
547 which differs from the behaviour controlled by this knob.)
550 Maximal length of the serial number in CTL was increased from 16 to
551 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
552 and ctld, need to be rebuilt to work with a new kernel.
555 The libatf-c and libatf-c++ major versions were downgraded to 0 and
556 1 respectively to match the upstream numbers. They were out of
557 sync because, when they were originally added to FreeBSD, the
558 upstream versions were not respected. These libraries are private
559 and not yet built by default, so renumbering them should be a
560 non-issue. However, unclean source trees will yield broken test
561 programs once the operator executes "make delete-old-libs" after a
564 Additionally, the atf-sh binary was made private by moving it into
565 /usr/libexec/. Already-built shell test programs will keep the
566 path to the old binary so they will break after "make delete-old"
569 If you are using WITH_TESTS=yes (not the default), wipe the object
570 tree and rebuild from scratch to prevent spurious test failures.
571 This is only needed once: the misnumbered libraries and misplaced
572 binaries have been added to OptionalObsoleteFiles.inc so they will
573 be removed during a clean upgrade.
576 Clang and llvm have been upgraded to 3.4.1 release.
579 We bogusly installed src.opts.mk in /usr/share/mk. This file should
580 be removed to avoid issues in the future (and has been added to
584 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
585 past, it affected all builds that used the bsd.*.mk files. The old
586 behavior was a bug, but people may have relied upon it. To get this
587 behavior back, you can .include /etc/src.conf from /etc/make.conf
588 (which is still global and isn't changed). This also changes the
589 behavior of incremental builds inside the tree of individual
590 directories. Set MAKESYSPATH to ".../share/mk" to do that.
591 Although this has survived make universe and some upgrade scenarios,
592 other upgrade scenarios may have broken. At least one form of
593 temporary breakage was fixed with MAKESYSPATH settings for buildworld
594 as well... In cases where MAKESYSPATH isn't working with this
595 setting, you'll need to set it to the full path to your tree.
597 One side effect of all this cleaning up is that bsd.compiler.mk
598 is no longer implicitly included by bsd.own.mk. If you wish to
599 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
603 The lindev device has been removed since /dev/full has been made a
604 standard device. __FreeBSD_version has been bumped.
607 The knob WITHOUT_VI was added to the base system, which controls
608 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
609 in order to reorder files share/termcap and didn't build ex(1) as a
610 build tool, so building/installing with WITH_VI is highly advised for
611 build hosts for older releases.
613 This issue has been fixed in stable/9 and stable/10 in r277022 and
614 r276991, respectively.
617 The YES_HESIOD knob has been removed. It has been obsolete for
618 a decade. Please move to using WITH_HESIOD instead or your builds
619 will silently lack HESIOD.
622 The uart(4) driver has been changed with respect to its handling
623 of the low-level console. Previously the uart(4) driver prevented
624 any process from changing the baudrate or the CLOCAL and HUPCL
625 control flags. By removing the restrictions, operators can make
626 changes to the serial console port without having to reboot.
627 However, when getty(8) is started on the serial device that is
628 associated with the low-level console, a misconfigured terminal
629 line in /etc/ttys will now have a real impact.
630 Before upgrading the kernel, make sure that /etc/ttys has the
631 serial console device configured as 3wire without baudrate to
632 preserve the previous behaviour. E.g:
633 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
636 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
637 to improve performance. To re-enable it, if needed, run rpcbind
638 with command line option -W.
641 Switched back to the GPL dtc compiler due to updates in the upstream
642 dts files not being supported by the BSDL dtc compiler. You will need
643 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
644 may result while building dtb files during a kernel build if you fail
645 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
648 Clang and llvm have been upgraded to 3.4 release.
651 The nve(4) driver has been removed. Please use the nfe(4) driver
652 for NVIDIA nForce MCP Ethernet adapters instead.
655 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
656 This could cause certain C++ applications using shared libraries built
657 against the previous version of libc++ to crash. The incompatibility
658 has now been fixed, but any C++ applications or shared libraries built
659 between r261283 and r261801 should be recompiled.
662 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
663 capability mode support. Please note that enabling the feature in
664 kernel is still highly recommended.
667 OpenSSH is now built with sandbox support, and will use sandbox as
668 the default privilege separation method. This requires Capsicum
669 capability mode support in kernel.
672 The libelf and libdwarf libraries have been updated to newer
673 versions from upstream. Shared library version numbers for
674 these two libraries were bumped. Any ports or binaries
675 requiring these two libraries should be recompiled.
676 __FreeBSD_version is bumped to 1100006.
679 If a Makefile in a tests/ directory was auto-generating a Kyuafile
680 instead of providing an explicit one, this would prevent such
681 Makefile from providing its own Kyuafile in the future during
682 NO_CLEAN builds. This has been fixed in the Makefiles but manual
683 intervention is needed to clean an objdir if you use NO_CLEAN:
684 # find /usr/obj -name Kyuafile | xargs rm -f
687 The behavior of gss_pseudo_random() for the krb5 mechanism
688 has changed, for applications requesting a longer random string
689 than produced by the underlying enctype's pseudo-random() function.
690 In particular, the random string produced from a session key of
691 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
692 be different at the 17th octet and later, after this change.
693 The counter used in the PRF+ construction is now encoded as a
694 big-endian integer in accordance with RFC 4402.
695 __FreeBSD_version is bumped to 1100004.
698 The WITHOUT_ATF build knob has been removed and its functionality
699 has been subsumed into the more generic WITHOUT_TESTS. If you were
700 using the former to disable the build of the ATF libraries, you
701 should change your settings to use the latter.
704 The default version of mtree is nmtree which is obtained from
705 NetBSD. The output is generally the same, but may vary
706 slightly. If you found you need identical output adding
707 "-F freebsd9" to the command line should do the trick. For the
708 time being, the old mtree is available as fmtree.
711 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
712 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
713 1.1.4_8 and verify bsdyml not linked in, before running "make
715 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
717 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
720 The stable/10 branch has been created in subversion from head
724 The rc.d/jail script has been updated to support jail(8)
725 configuration file. The "jail_<jname>_*" rc.conf(5) variables
726 for per-jail configuration are automatically converted to
727 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
728 This is transparently backward compatible. See below about some
729 incompatibilities and rc.conf(5) manual page for more details.
731 These variables are now deprecated in favor of jail(8) configuration
732 file. One can use "rc.d/jail config <jname>" command to generate
733 a jail(8) configuration file in /var/run/jail.<jname>.conf without
734 running the jail(8) utility. The default pathname of the
735 configuration file is /etc/jail.conf and can be specified by
736 using $jail_conf or $jail_<jname>_conf variables.
738 Please note that jail_devfs_ruleset accepts an integer at
739 this moment. Please consider to rewrite the ruleset name
743 BIND has been removed from the base system. If all you need
744 is a local resolver, simply enable and start the local_unbound
745 service instead. Otherwise, several versions of BIND are
746 available in the ports tree. The dns/bind99 port is one example.
748 With this change, nslookup(1) and dig(1) are no longer in the base
749 system. Users should instead use host(1) and drill(1) which are
750 in the base system. Alternatively, nslookup and dig can
751 be obtained by installing the dns/bind-tools port.
754 With the addition of unbound(8), a new unbound user is now
755 required during installworld. "mergemaster -p" can be used to
756 add the user prior to installworld, as documented in the handbook.
759 OpenSSH is now built with DNSSEC support, and will by default
760 silently trust signed SSHFP records. This can be controlled with
761 the VerifyHostKeyDNS client configuration setting. DNSSEC support
762 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
765 The GNU Compiler Collection and C++ standard library (libstdc++)
766 are no longer built by default on platforms where clang is the system
767 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
771 The PROCDESC kernel option is now part of the GENERIC kernel
772 configuration and is required for the rwhod(8) to work.
773 If you are using custom kernel configuration, you should include
777 The API and ABI related to the Capsicum framework was modified
778 in backward incompatible way. The userland libraries and programs
779 have to be recompiled to work with the new kernel. This includes the
780 following libraries and programs, but the whole buildworld is
781 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
782 kdump, procstat, rwho, rwhod, uniq.
785 AES-NI intrinsic support has been added to gcc. The AES-NI module
786 has been updated to use this support. A new gcc is required to build
787 the aesni module on both i386 and amd64.
790 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
791 Thus "device padlock_rng" and "device rdrand_rng" should be
792 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
795 WITH_ICONV has been split into two feature sets. WITH_ICONV now
796 enables just the iconv* functionality and is now on by default.
797 WITH_LIBICONV_COMPAT enables the libiconv api and link time
798 compatability. Set WITHOUT_ICONV to build the old way.
799 If you have been using WITH_ICONV before, you will very likely
800 need to turn on WITH_LIBICONV_COMPAT.
803 INVARIANTS option now enables DEBUG for code with OpenSolaris and
804 Illumos origin, including ZFS. If you have INVARIANTS in your
805 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
807 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
808 locks if WITNESS option was set. Because that generated a lot of
809 witness(9) reports and all of them were believed to be false
810 positives, this is no longer done. New option OPENSOLARIS_WITNESS
811 can be used to achieve the previous behavior.
814 Timer values in IPv6 data structures now use time_uptime instead
815 of time_second. Although this is not a user-visible functional
816 change, userland utilities which directly use them---ndp(8),
817 rtadvd(8), and rtsold(8) in the base system---need to be updated
821 find -delete can now delete the pathnames given as arguments,
822 instead of only files found below them or if the pathname did
823 not contain any slashes. Formerly, the following error message
826 find: -delete: <path>: relative path potentially not safe
828 Deleting the pathnames given as arguments can be prevented
829 without error messages using -mindepth 1 or by changing
830 directory and passing "." as argument to find. This works in the
831 old as well as the new version of find.
834 Behavior of devfs rules path matching has been changed.
835 Pattern is now always matched against fully qualified devfs
836 path and slash characters must be explicitly matched by
837 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
838 subdirectories must be reviewed.
841 The default ARM ABI has changed to the ARM EABI. The old ABI is
842 incompatible with the ARM EABI and all programs and modules will
843 need to be rebuilt to work with a new kernel.
845 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
847 NOTE: Support for the old ABI will be removed in the future and
848 users are advised to upgrade.
851 pkg_install has been disconnected from the build if you really need it
852 you should add WITH_PKGTOOLS in your src.conf(5).
855 Most of network statistics structures were changed to be able
856 keep 64-bits counters. Thus all tools, that work with networking
857 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
860 Fix a bug that allowed a tracing process (e.g. gdb) to write
861 to a memory-mapped file in the traced process's address space
862 even if neither the traced process nor the tracing process had
863 write access to that file.
866 CVS has been removed from the base system. An exact copy
867 of the code is available from the devel/cvs port.
870 Some people report the following error after the switch to bmake:
872 make: illegal option -- J
873 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
875 *** [buildworld] Error code 2
877 this likely due to an old instance of make in
878 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
879 which src/Makefile will use that blindly, if it exists, so if
880 you see the above error:
882 rm -rf `make -V MAKEPATH`
887 Use bmake by default.
888 Whereas before one could choose to build with bmake via
889 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
890 make. The goal is to remove these knobs for 10-RELEASE.
892 It is worth noting that bmake (like gmake) treats the command
893 line as the unit of failure, rather than statements within the
894 command line. Thus '(cd some/where && dosomething)' is safer
895 than 'cd some/where; dosomething'. The '()' allows consistent
896 behavior in parallel build.
899 Fix a bug that allows NFS clients to issue READDIR on files.
902 The WITHOUT_IDEA option has been removed because
903 the IDEA patent expired.
906 The sysctl which controls TRIM support under ZFS has been renamed
907 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
911 The mergemaster command now uses the default MAKEOBJDIRPREFIX
912 rather than creating it's own in the temporary directory in
913 order allow access to bootstrapped versions of tools such as
914 install and mtree. When upgrading from version of FreeBSD where
915 the install command does not support -l, you will need to
916 install a new mergemaster command if mergemaster -p is required.
917 This can be accomplished with the command (cd src/usr.sbin/mergemaster
921 Legacy ATA stack, disabled and replaced by new CAM-based one since
922 FreeBSD 9.0, completely removed from the sources. Kernel modules
923 atadisk and atapi*, user-level tools atacontrol and burncd are
924 removed. Kernel option `options ATA_CAM` is now permanently enabled
928 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
929 and socketpair(2). Software, in particular Kerberos, may
930 automatically detect and use these during building. The resulting
931 binaries will not work on older kernels.
934 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
935 information, see the respective 20130304 entry).
938 Recent commits to callout(9) changed the size of struct callout,
939 so the KBI is probably heavily disturbed. Also, some functions
940 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
941 by macros. Every kernel module using it won't load, so rebuild
944 The ctl device has been re-enabled in GENERIC for i386 and amd64,
945 but does not initialize by default (because of the new CTL_DISABLE
946 option) to save memory. To re-enable it, remove the CTL_DISABLE
947 option from the kernel config file or set kern.cam.ctl.disable=0
948 in /boot/loader.conf.
951 The ctl device has been disabled in GENERIC for i386 and amd64.
952 This was done due to the extra memory being allocated at system
953 initialisation time by the ctl driver which was only used if
954 a CAM target device was created. This makes a FreeBSD system
955 unusable on 128MB or less of RAM.
958 A new compression method (lz4) has been merged to -HEAD. Please
959 refer to zpool-features(7) for more information.
961 Please refer to the "ZFS notes" section of this file for information
962 on upgrading boot ZFS pools.
965 A BSD-licensed patch(1) variant has been added and is installed
966 as bsdpatch, being the GNU version the default patch.
967 To inverse the logic and use the BSD-licensed one as default,
968 while having the GNU version installed as gnupatch, rebuild
969 and install world with the WITH_BSD_PATCH knob set.
972 Due to the use of the new -l option to install(1) during build
973 and install, you must take care not to directly set the INSTALL
974 make variable in your /etc/make.conf, /etc/src.conf, or on the
975 command line. If you wish to use the -C flag for all installs
976 you may be able to add INSTALL+=-C to /etc/make.conf or
980 The install(1) option -M has changed meaning and now takes an
981 argument that is a file or path to append logs to. In the
982 unlikely event that -M was the last option on the command line
983 and the command line contained at least two files and a target
984 directory the first file will have logs appended to it. The -M
985 option served little practical purpose in the last decade so its
986 use is expected to be extremely rare.
989 After switching to Clang as the default compiler some users of ZFS
990 on i386 systems started to experience stack overflow kernel panics.
991 Please consider using 'options KSTACK_PAGES=4' in such configurations.
994 GEOM_LABEL now mangles label names read from file system metadata.
995 Mangling affect labels containing spaces, non-printable characters,
996 '%' or '"'. Device names in /etc/fstab and other places may need to
1000 By default, only the 10 most recent kernel dumps will be saved. To
1001 restore the previous behaviour (no limit on the number of kernel dumps
1002 stored in the dump directory) add the following line to /etc/rc.conf:
1007 With the addition of auditdistd(8), a new auditdistd user is now
1008 required during installworld. "mergemaster -p" can be used to
1009 add the user prior to installworld, as documented in the handbook.
1012 The sin6_scope_id member variable in struct sockaddr_in6 is now
1013 filled by the kernel before passing the structure to the userland via
1014 sysctl or routing socket. This means the KAME-specific embedded scope
1015 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1016 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1017 __FreeBSD_version is bumped to 1000025.
1020 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1021 This means that the world and kernel will be compiled with clang
1022 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1023 and /usr/bin/cpp. To disable this behavior and revert to building
1024 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1025 of current may need to bootstrap WITHOUT_CLANG first if the clang
1026 build fails (its compatibility window doesn't extend to the 9 stable
1030 The IPFIREWALL_FORWARD kernel option has been removed. Its
1031 functionality now turned on by default.
1034 The ZERO_COPY_SOCKET kernel option has been removed and
1035 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1036 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1037 mechanism which is not safe and may result in kernel crashes.
1038 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1039 driver supports disposeable external page sized mbuf storage.
1040 Proper replacements for both zero-copy mechanisms are under
1041 consideration and will eventually lead to complete removal
1042 of the two kernel options.
1045 The IPv4 network stack has been converted to network byte
1046 order. The following modules need to be recompiled together
1047 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1048 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1051 Support for non-MPSAFE filesystems was removed from VFS. The
1052 VFS_VERSION was bumped, all filesystem modules shall be
1056 All the non-MPSAFE filesystems have been disconnected from
1057 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1058 portalfs, smbfs, xfs.
1061 The interface cloning API and ABI has changed. The following
1062 modules need to be recompiled together with kernel:
1063 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1064 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1065 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1068 The sdhci driver was split in two parts: sdhci (generic SD Host
1069 Controller logic) and sdhci_pci (actual hardware driver).
1070 No kernel config modifications are required, but if you
1071 load sdhc as a module you must switch to sdhci_pci instead.
1074 Import the FUSE kernel and userland support into base system.
1077 The GNU sort(1) program has been removed since the BSD-licensed
1078 sort(1) has been the default for quite some time and no serious
1079 problems have been reported. The corresponding WITH_GNU_SORT
1083 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1084 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1088 The net80211(4) ABI has been changed to allow for improved driver
1089 PS-POLL and power-save support. All wireless drivers need to be
1090 recompiled to work with the new kernel.
1093 The random(4) support for the VIA hardware random number
1094 generator (`PADLOCK') is no longer enabled unconditionally.
1095 Add the padlock_rng device in the custom kernel config if
1096 needed. The GENERIC kernels on i386 and amd64 do include the
1097 device, so the change only affects the custom kernel
1101 The pf(4) packet filter ABI has been changed. pfctl(8) and
1102 snmp_pf module need to be recompiled to work with new kernel.
1105 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1106 to -HEAD. Pools that have empty_bpobj in active state can not be
1107 imported read-write with ZFS implementations that do not support
1108 this feature. For more information read the zpool-features(5)
1112 The sparc64 ZFS loader has been changed to no longer try to auto-
1113 detect ZFS providers based on diskN aliases but now requires these
1114 to be explicitly listed in the OFW boot-device environment variable.
1117 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1118 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1119 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1122 The following sysctls and tunables have been renamed for consistency
1123 with other variables:
1124 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1125 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1128 The sort utility has been replaced with BSD sort. For now, GNU sort
1129 is also available as "gnusort" or the default can be set back to
1130 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1131 installed as "bsdsort".
1134 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1135 Starting with this version the old system of ZFS pool versioning
1136 is superseded by "feature flags". This concept enables forward
1137 compatibility against certain future changes in functionality of ZFS
1138 pools. The first read-only compatible "feature flag" for ZFS pools
1139 is named "com.delphix:async_destroy". For more information
1140 read the new zpool-features(5) manual page.
1141 Please refer to the "ZFS notes" section of this file for information
1142 on upgrading boot ZFS pools.
1145 The malloc(3) implementation embedded in libc now uses sources imported
1146 as contrib/jemalloc. The most disruptive API change is to
1147 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1148 delete it prior to installworld, and optionally re-create it using the
1149 new format after rebooting. See malloc.conf(5) for details
1150 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1154 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1155 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1156 now spelled mips. This is to aid compatibility with third-party
1157 software that expects this naming scheme in uname(3). Little-endian
1158 settings are unchanged. If you are updating a big-endian mips64 machine
1159 from before this change, you may need to set MACHINE_ARCH=mips64 in
1160 your environment before the new build system will recognize your machine.
1163 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1167 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1168 nullfs(5) did not pass through all behaviours to the underlying layer,
1169 as a result if we bound to a socket on the lower layer we could connect
1170 only to the lower path; if we bound to the upper layer we could connect
1171 only to the upper path. The new behavior is one can connect to both the
1172 lower and the upper paths regardless what layer path one binds to.
1175 The getifaddrs upgrade path broken with 20111215 has been restored.
1176 If you have upgraded in between 20111215 and 20120209 you need to
1177 recompile libc again with your kernel. You still need to recompile
1178 world to be able to configure CARP but this restriction already
1179 comes from 20111215.
1182 The set_rcvar() function has been removed from /etc/rc.subr. All
1183 base and ports rc.d scripts have been updated, so if you have a
1184 port installed with a script in /usr/local/etc/rc.d you can either
1185 hand-edit the rcvar= line, or reinstall the port.
1187 An easy way to handle the mass-update of /etc/rc.d:
1188 rm /etc/rc.d/* && mergemaster -i
1191 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1192 on the current CPU and prevents other threads from running.
1193 This behavior can be reverted using the kern.stop_scheduler_on_panic
1195 The new behavior can be incompatible with kern.sync_on_panic.
1198 The carp(4) facility has been changed significantly. Configuration
1199 of the CARP protocol via ifconfig(8) has changed, as well as format
1200 of CARP events submitted to devd(8) has changed. See manual pages
1201 for more information. The arpbalance feature of carp(4) is currently
1202 not supported anymore.
1204 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1205 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1206 need to be recompiled.
1209 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1213 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1214 explicitely support non-MPSAFE filesystems.
1215 It is on by default for all supported platform at this present
1219 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1220 i386 and pc98 GENERIC kernel configuration files.
1223 sysinstall has been removed
1226 The stable/9 branch created in subversion. This corresponds to the
1227 RELENG_9 branch in CVS.
1233 Avoid using make -j when upgrading. While generally safe, there are
1234 sometimes problems using -j to upgrade. If your upgrade fails with
1235 -j, please try again without -j. From time to time in the past there
1236 have been problems using -j with buildworld and/or installworld. This
1237 is especially true when upgrading between "distant" versions (eg one
1238 that cross a major release boundary or several minor releases, or when
1239 several months have passed on the -current branch).
1241 Sometimes, obscure build problems are the result of environment
1242 poisoning. This can happen because the make utility reads its
1243 environment when searching for values for global variables. To run
1244 your build attempts in an "environmental clean room", prefix all make
1245 commands with 'env -i '. See the env(1) manual page for more details.
1247 When upgrading from one major version to another it is generally best
1248 to upgrade to the latest code in the currently installed branch first,
1249 then do an upgrade to the new branch. This is the best-tested upgrade
1250 path, and has the highest probability of being successful. Please try
1251 this approach before reporting problems with a major version upgrade.
1253 When upgrading a live system, having a root shell around before
1254 installing anything can help undo problems. Not having a root shell
1255 around can lead to problems if pam has changed too much from your
1256 starting point to allow continued authentication after the upgrade.
1258 This file should be read as a log of events. When a later event changes
1259 information of a prior event, the prior event should not be deleted.
1260 Instead, a pointer to the entry with the new information should be
1261 placed in the old entry. Readers of this file should also sanity check
1262 older entries before relying on them blindly. Authors of new entries
1263 should write them with this in mind.
1267 When upgrading the boot ZFS pool to a new version, always follow
1270 1.) recompile and reinstall the ZFS boot loader and boot block
1271 (this is part of "make buildworld" and "make installworld")
1273 2.) update the ZFS boot block on your boot drive
1275 The following example updates the ZFS boot block on the first
1276 partition (freebsd-boot) of a GPT partitioned drive ada0:
1277 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1279 Non-boot pools do not need these updates.
1283 If you are updating from a prior version of FreeBSD (even one just
1284 a few days old), you should follow this procedure. It is the most
1285 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1287 make kernel-toolchain
1288 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1289 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1291 To test a kernel once
1292 ---------------------
1293 If you just want to boot a kernel once (because you are not sure
1294 if it works, or if you want to boot a known bad kernel to provide
1295 debugging information) run
1296 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1297 nextboot -k testkernel
1299 To just build a kernel when you know that it won't mess you up
1300 --------------------------------------------------------------
1301 This assumes you are already running a CURRENT system. Replace
1302 ${arch} with the architecture of your machine (e.g. "i386",
1303 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1305 cd src/sys/${arch}/conf
1306 config KERNEL_NAME_HERE
1307 cd ../compile/KERNEL_NAME_HERE
1312 If this fails, go to the "To build a kernel" section.
1314 To rebuild everything and install it on the current system.
1315 -----------------------------------------------------------
1316 # Note: sometimes if you are running current you gotta do more than
1317 # is listed here if you are upgrading from a really old current.
1319 <make sure you have good level 0 dumps>
1321 make kernel KERNCONF=YOUR_KERNEL_HERE
1323 <reboot in single user> [3]
1330 To cross-install current onto a separate partition
1331 --------------------------------------------------
1332 # In this approach we use a separate partition to hold
1333 # current's root, 'usr', and 'var' directories. A partition
1334 # holding "/", "/usr" and "/var" should be about 2GB in
1337 <make sure you have good level 0 dumps>
1340 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1341 <maybe newfs current's root partition>
1342 <mount current's root partition on directory ${CURRENT_ROOT}>
1343 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1344 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1345 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1346 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1347 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1348 <reboot into current>
1349 <do a "native" rebuild/install as described in the previous section>
1350 <maybe install compatibility libraries from ports/misc/compat*>
1354 To upgrade in-place from stable to current
1355 ----------------------------------------------
1356 <make sure you have good level 0 dumps>
1358 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1360 <reboot in single user> [3]
1367 Make sure that you've read the UPDATING file to understand the
1368 tweaks to various things you need. At this point in the life
1369 cycle of current, things change often and you are on your own
1370 to cope. The defaults can also change, so please read ALL of
1371 the UPDATING entries.
1373 Also, if you are tracking -current, you must be subscribed to
1374 freebsd-current@freebsd.org. Make sure that before you update
1375 your sources that you have read and understood all the recent
1376 messages there. If in doubt, please track -stable which has
1377 much fewer pitfalls.
1379 [1] If you have third party modules, such as vmware, you
1380 should disable them at this point so they don't crash your
1383 [3] From the bootblocks, boot -s, and then do
1388 adjkerntz -i # if CMOS is wall time
1389 Also, when doing a major release upgrade, it is required that
1390 you boot into single user mode to do the installworld.
1392 [4] Note: This step is non-optional. Failure to do this step
1393 can result in a significant reduction in the functionality of the
1394 system. Attempting to do it by hand is not recommended and those
1395 that pursue this avenue should read this file carefully, as well
1396 as the archives of freebsd-current and freebsd-hackers mailing lists
1397 for potential gotchas. The -U option is also useful to consider.
1398 See mergemaster(8) for more information.
1400 [5] Usually this step is a noop. However, from time to time
1401 you may need to do this if you get unknown user in the following
1402 step. It never hurts to do it all the time. You may need to
1403 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1404 install) after the buildworld before this step if you last updated
1405 from current before 20130425 or from -stable before 20130430.
1407 [6] This only deletes old files and directories. Old libraries
1408 can be deleted by "make delete-old-libs", but you have to make
1409 sure that no program is using those libraries anymore.
1411 [8] In order to have a kernel that can run the 4.x binaries needed to
1412 do an installworld, you must include the COMPAT_FREEBSD4 option in
1413 your kernel. Failure to do so may leave you with a system that is
1414 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1415 required to run the 5.x binaries on more recent kernels. And so on
1416 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1418 Make sure that you merge any new devices from GENERIC since the
1419 last time you updated your kernel config file.
1421 [9] When checking out sources, you must include the -P flag to have
1422 cvs prune empty directories.
1424 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1425 "?=" instead of the "=" assignment operator, so that buildworld can
1426 override the CPUTYPE if it needs to.
1428 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1429 not on the command line, or in /etc/make.conf. buildworld will
1430 warn if it is improperly defined.
1433 This file contains a list, in reverse chronological order, of major
1434 breakages in tracking -current. It is not guaranteed to be a complete
1435 list of such breakages, and only contains entries since September 23, 2011.
1436 If you need to see UPDATING entries from before that date, you will need
1437 to fetch an UPDATING file from an older FreeBSD release.
1439 Copyright information:
1441 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1443 Redistribution, publication, translation and use, with or without
1444 modification, in full or in part, in any form or format of this
1445 document are permitted without further permission from the author.
1447 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1448 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1449 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1450 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1451 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1452 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1453 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1454 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1455 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1456 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1457 POSSIBILITY OF SUCH DAMAGE.
1459 Contact Warner Losh if you have any questions about your use of