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 The code to start recording plug and play data into the modules has
36 been committed. While the old tools will properly build a new kernel,
37 a number of warnings about "unknown metadata record 4" will be produced
38 for an older kldxref. To avoid such warnings, make sure to rebuild
39 the kernel toolchain (or world). Make sure that you have r292078 or
40 later when trying to build 292077 or later before rebuilding.
43 Debug data files are now built by default with 'make buildworld' and
44 installed with 'make installworld'. This facilitates debugging but
45 requires more disk space both during the build and for the installed
46 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
50 r291527 changed the internal interface between the nfsd.ko and
51 nfscommon.ko modules. As such, they must both be upgraded to-gether.
52 __FreeBSD_version has been bumped because of this.
55 Add support for unicode collation strings leads to a change of
56 order of files listed by ls(1) for example. To get back to the old
57 behaviour, set LC_COLLATE environment variable to "C".
59 Databases administrators will need to reindex their databases given
60 collation results will be different.
62 Due to a bug in install(1) it is recommended to remove the ancient
63 locales before running make installworld.
65 rm -rf /usr/share/locale/*
68 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
69 libcrypto.so.7 or libssl.so.7 must be recompiled.
72 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
73 Kernel modules isp_2400_multi and isp_2500_multi were removed and
74 should be replaced with isp_2400 and isp_2500 modules respectively.
77 The build previously allowed using 'make -n' to not recurse into
78 sub-directories while showing what commands would be executed, and
79 'make -n -n' to recursively show commands. Now 'make -n' will recurse
80 and 'make -N' will not.
83 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
84 and etcupdate will now use this file. A custom sendmail.cf is now
85 updated via this mechanism rather than via installworld. If you had
86 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
87 want to remove the exclusion or change it to "always install".
88 /etc/mail/sendmail.cf is now managed the same way regardless of
89 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
90 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
93 Compatibility shims for legacy ATA device names have been removed.
94 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
95 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
96 environment variables, /dev/ad* and /dev/ar* symbolic links.
99 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
100 Please see the 20141231 entry below for information about prerequisites
101 and upgrading, if you are not already using clang 3.5.0 or higher.
104 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
105 and renamed from .symbols to .debug. This reduces the size requirements
106 on the boot partition or file system and provides consistency with
107 userland debug files.
109 When using the supported kernel installation method the
110 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
111 as is done with /boot/kernel.
113 Developers wishing to maintain the historical behavior of installing
114 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
117 The wireless drivers had undergone changes that remove the 'parent
118 interface' from the ifconfig -l output. The rc.d network scripts
119 used to check presence of a parent interface in the list, so old
120 scripts would fail to start wireless networking. Thus, etcupdate(3)
121 or mergemaster(8) run is required after kernel update, to update your
122 rc.d scripts in /etc.
125 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
126 These configurations are now automatically interpreted as
127 'scrub fragment reassemble'.
130 Kernel-loadable modules for the random(4) device are back. To use
131 them, the kernel must have
134 options RANDOM_LOADABLE
136 kldload(8) can then be used to load random_fortuna.ko
137 or random_yarrow.ko. Please note that due to the indirect
138 function calls that the loadable modules need to provide,
139 the build-in variants will be slightly more efficient.
141 The random(4) kernel option RANDOM_DUMMY has been retired due to
142 unpopularity. It was not all that useful anyway.
145 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
146 Control over building the ELF Tool Chain tools is now provided by
147 the WITHOUT_TOOLCHAIN knob.
150 The polarity of Pulse Per Second (PPS) capture events with the
151 uart(4) driver has been corrected. Prior to this change the PPS
152 "assert" event corresponded to the trailing edge of a positive PPS
153 pulse and the "clear" event was the leading edge of the next pulse.
155 As the width of a PPS pulse in a typical GPS receiver is on the
156 order of 1 millisecond, most users will not notice any significant
157 difference with this change.
159 Anyone who has compensated for the historical polarity reversal by
160 configuring a negative offset equal to the pulse width will need to
161 remove that workaround.
164 The default group assigned to /dev/dri entries has been changed
165 from 'wheel' to 'video' with the id of '44'. If you want to have
166 access to the dri devices please add yourself to the video group
169 # pw groupmod video -m $USER
172 The menu.rc and loader.rc files will now be replaced during
173 upgrades. Please migrate local changes to menu.rc.local and
174 loader.rc.local instead.
177 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
178 strings and strip have been removed. The src.conf(5) knob
179 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
182 As ZFS requires more kernel stack pages than is the default on some
183 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
184 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
186 Please consider using 'options KSTACK_PAGES=X' where X is greater
187 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
190 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
191 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
192 default, i.e., they will not contain "::". For example, instead
193 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
194 to have a more specific match, such as different map entries for
195 IPv6:0:0 vs IPv6:0. This change requires that configuration
196 data (including maps, files, classes, custom ruleset, etc.) must
197 use the same format, so make certain such configuration data is
198 upgrading. As a very simple check search for patterns like
199 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
200 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
201 the cf option UseCompressedIPv6Addresses.
204 The default kernel entropy-processing algorithm is now
205 Fortuna, replacing Yarrow.
207 Assuming you have 'device random' in your kernel config
208 file, the configurations allow a kernel option to override
209 this default. You may choose *ONE* of:
211 options RANDOM_YARROW # Legacy /dev/random algorithm.
212 options RANDOM_DUMMY # Blocking-only driver.
214 If you have neither, you get Fortuna. For most people,
215 read no further, Fortuna will give a /dev/random that works
216 like it always used to, and the difference will be irrelevant.
218 If you remove 'device random', you get *NO* kernel-processed
219 entropy at all. This may be acceptable to folks building
220 embedded systems, but has complications. Carry on reading,
221 and it is assumed you know what you need.
223 *PLEASE* read random(4) and random(9) if you are in the
224 habit of tweaking kernel configs, and/or if you are a member
225 of the embedded community, wanting specific and not-usual
226 behaviour from your security subsystems.
228 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
229 random', you will NOT have a functioning /dev/random, and
230 many cryptographic features will not work, including SSH.
231 You may also find strange behaviour from the random(3) set
232 of library functions, in particular sranddev(3), srandomdev(3)
233 and arc4random(3). The reason for this is that the KERN_ARND
234 sysctl only returns entropy if it thinks it has some to
235 share, and with RANDOM_DUMMY or no 'device random' this
239 An additional fix for the issue described in the 20150614 sendmail
240 entry below has been been committed in revision 284717.
243 FreeBSD's old make (fmake) has been removed from the system. It is
244 available as the devel/fmake port or via pkg install fmake.
247 The fix for the issue described in the 20150614 sendmail entry
248 below has been been committed in revision 284436. The work
249 around described in that entry is no longer needed unless the
250 default setting is overridden by a confDH_PARAMETERS configuration
251 setting of '5' or pointing to a 512 bit DH parameter file.
254 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
255 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
256 and devel/kyua to version 0.20+ and adjust any calling code to work
257 with Kyuafile and kyua.
260 The import of openssl to address the FreeBSD-SA-15:10.openssl
261 security advisory includes a change which rejects handshakes
262 with DH parameters below 768 bits. sendmail releases prior
263 to 8.15.2 (not yet released), defaulted to a 512 bit
264 DH parameter setting for client connections. To work around
265 this interoperability, sendmail can be configured to use a
266 2048 bit DH parameter by:
268 1. Edit /etc/mail/`hostname`.mc
269 2. If a setting for confDH_PARAMETERS does not exist or
270 exists and is set to a string beginning with '5',
272 3. If a setting for confDH_PARAMETERS exists and is set to
273 a file path, create a new file with:
274 openssl dhparam -out /path/to/file 2048
275 4. Rebuild the .cf file:
276 cd /etc/mail/; make; make install
278 cd /etc/mail/; make restart
280 A sendmail patch is coming, at which time this file will be
284 Generation of legacy formatted entries have been disabled by default
285 in pwd_mkdb(8), as all base system consumers of the legacy formatted
286 entries were converted to use the new format by default when the new,
287 machine independent format have been added and supported since FreeBSD
290 Please see the pwd_mkdb(8) manual page for further details.
293 Clang and llvm have been upgraded to 3.6.1 release. Please see the
294 20141231 entry below for information about prerequisites and upgrading,
295 if you are not already using 3.5.0 or higher.
298 TI platform code switched to using vendor DTS files and this update
299 may break existing systems running on Beaglebone, Beaglebone Black,
302 - dtb files should be regenerated/reinstalled. Filenames are the
303 same but content is different now
304 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
305 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
306 addressing scheme is now pin 25 on /dev/gpioc3.
307 - Pandaboard: /etc/ttys should be updated, serial console device is
308 now /dev/ttyu2, not /dev/ttyu0
311 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
312 If you need the GNU extension from groff soelim(1), install groff
313 from package: pkg install groff, or via ports: textproc/groff.
316 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
317 defined in symlink(7); previously symlinks were silently ignored.
320 The const qualifier has been removed from iconv(3) to comply with
321 POSIX. The ports tree is aware of this from r384038 onwards.
324 Libraries specified by LIBADD in Makefiles must have a corresponding
325 DPADD_<lib> variable to ensure correct dependencies. This is now
326 enforced in src.libnames.mk.
329 From legacy ata(4) driver was removed support for SATA controllers
330 supported by more functional drivers ahci(4), siis(4) and mvs(4).
331 Kernel modules ataahci and ataadaptec were removed completely,
332 replaced by ahci and mvs modules respectively.
335 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
336 the 20141231 entry below for information about prerequisites and
337 upgrading, if you are not already using 3.5.0 or higher.
340 The 32-bit PowerPC kernel has been changed to a position-independent
341 executable. This can only be booted with a version of loader(8)
342 newer than January 31, 2015, so make sure to update both world and
343 kernel before rebooting.
346 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
347 but before r278950, the RNG was not seeded properly. Immediately
348 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
349 ssh keys or openssl keys) that were generated w/ a kernel from that
350 range. This does not affect programs that directly used /dev/random
351 or /dev/urandom. All userland uses of arc4random(3) are affected.
354 The autofs(4) ABI was changed in order to restore binary compatibility
355 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
359 The powerpc64 kernel has been changed to a position-independent
360 executable. This can only be booted with a new version of loader(8),
361 so make sure to update both world and kernel before rebooting.
364 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
365 only release, no new features have been added. Please see the 20141231
366 entry below for information about prerequisites and upgrading, if you
367 are not already using 3.5.0.
370 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
371 taken from the ELF Tool Chain project rather than GNU binutils. They
372 should be drop-in replacements, with the addition of arm64 support.
373 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
374 binutils tools, if necessary. See 20150805 for updated information.
377 The default Unbound configuration now enables remote control
378 using a local socket. Users who have already enabled the
379 local_unbound service should regenerate their configuration
380 by running "service local_unbound setup" as root.
383 The GNU texinfo and GNU info pages have been removed.
384 To be able to view GNU info pages please install texinfo from ports.
387 Clang, llvm and lldb have been upgraded to 3.5.0 release.
389 As of this release, a prerequisite for building clang, llvm and lldb is
390 a C++11 capable compiler and C++11 standard library. This means that to
391 be able to successfully build the cross-tools stage of buildworld, with
392 clang as the bootstrap compiler, your system compiler or cross compiler
393 should either be clang 3.3 or later, or gcc 4.8 or later, and your
394 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
397 On any standard FreeBSD 10.x or 11.x installation, where clang and
398 libc++ are on by default (that is, on x86 or arm), this should work out
401 On 9.x installations where clang is enabled by default, e.g. on x86 and
402 powerpc, libc++ will not be enabled by default, so libc++ should be
403 built (with clang) and installed first. If both clang and libc++ are
404 missing, build clang first, then use it to build libc++.
406 On 8.x and earlier installations, upgrade to 9.x first, and then follow
407 the instructions for 9.x above.
409 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
410 default, and do not build clang.
412 Many embedded systems are resource constrained, and will not be able to
413 build clang in a reasonable time, or in some cases at all. In those
414 cases, cross building bootable systems on amd64 is a workaround.
416 This new version of clang introduces a number of new warnings, of which
417 the following are most likely to appear:
421 This warns in two cases, for both C and C++:
422 * When the code is trying to take the absolute value of an unsigned
423 quantity, which is effectively a no-op, and almost never what was
424 intended. The code should be fixed, if at all possible. If you are
425 sure that the unsigned quantity can be safely cast to signed, without
426 loss of information or undefined behavior, you can add an explicit
427 cast, or disable the warning.
429 * When the code is trying to take an absolute value, but the called
430 abs() variant is for the wrong type, which can lead to truncation.
431 If you want to disable the warning instead of fixing the code, please
432 make sure that truncation will not occur, or it might lead to unwanted
435 -Wtautological-undefined-compare and
436 -Wundefined-bool-conversion
438 These warn when C++ code is trying to compare 'this' against NULL, while
439 'this' should never be NULL in well-defined C++ code. However, there is
440 some legacy (pre C++11) code out there, which actively abuses this
441 feature, which was less strictly defined in previous C++ versions.
443 Squid and openjdk do this, for example. The warning can be turned off
444 for C++98 and earlier, but compiling the code in C++11 mode might result
445 in unexpected behavior; for example, the parts of the program that are
446 unreachable could be optimized away.
449 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
450 kernel sources have been removed. The .h files remain, since some
451 utilities include them. This will need to be fixed later.
452 If "mount -t oldnfs ..." is attempted, it will fail.
453 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
454 the utilities will report errors.
457 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
458 directories to top level SUBDIR variable when their parent
459 directory is included in LOCAL_DIRS. Users with build systems with
460 such hierarchies and without SUBDIR entries in the parent
461 directory Makefiles should add them or add the directories to
465 faith(4) and faithd(8) have been removed from the base system. Faith
466 has been obsolete for a very long time.
469 vt(4), the new console driver, is enabled by default. It brings
470 support for Unicode and double-width characters, as well as
471 support for UEFI and integration with the KMS kernel video
474 You may need to update your console settings in /etc/rc.conf,
475 most probably the keymap. During boot, /etc/rc.d/syscons will
476 indicate what you need to do.
478 vt(4) still has issues and lacks some features compared to
479 syscons(4). See the wiki for up-to-date information:
480 https://wiki.freebsd.org/Newcons
482 If you want to keep using syscons(4), you can do so by adding
483 the following line to /boot/loader.conf:
487 pjdfstest has been integrated into kyua as an opt-in test suite.
488 Please see share/doc/pjdfstest/README for more details on how to
492 gperf has been removed from the base system for architectures
493 that use clang. Ports that require gperf will obtain it from the
497 pjdfstest has been moved from tools/regression/pjdfstest to
501 At svn r271982, The default linux compat kernel ABI has been adjusted
502 to 2.6.18 in support of the linux-c6 compat ports infrastructure
503 update. If you wish to continue using the linux-f10 compat ports,
504 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
505 encouraged to update their linux-compat packages to linux-c6 during
506 their next update cycle.
509 The ofwfb driver, used to provide a graphics console on PowerPC when
510 using vt(4), no longer allows mmap() of all physical memory. This
511 will prevent Xorg on PowerPC with some ATI graphics cards from
512 initializing properly unless x11-servers/xorg-server is updated to
516 The xdev targets have been converted to using TARGET and
517 TARGET_ARCH instead of XDEV and XDEV_ARCH.
520 The default unbound configuration has been modified to address
521 issues with reverse lookups on networks that use private
522 address ranges. If you use the local_unbound service, run
523 "service local_unbound setup" as root to regenerate your
524 configuration, then "service local_unbound reload" to load the
528 The GNU texinfo and GNU info pages are not built and installed
529 anymore, WITH_INFO knob has been added to allow to built and install
531 UPDATE: see 20150102 entry on texinfo's removal
534 The GNU readline library is now an INTERNALLIB - that is, it is
535 statically linked into consumers (GDB and variants) in the base
536 system, and the shared library is no longer installed. The
537 devel/readline port is available for third party software that
541 The Itanium architecture (ia64) has been removed from the list of
542 known architectures. This is the first step in the removal of the
546 Commit r268115 has added NFSv4.1 server support, merged from
547 projects/nfsv4.1-server. Since this includes changes to the
548 internal interfaces between the NFS related modules, a full
549 build of the kernel and modules will be necessary.
550 __FreeBSD_version has been bumped.
553 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
554 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
555 which differs from the behaviour controlled by this knob.)
558 Maximal length of the serial number in CTL was increased from 16 to
559 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
560 and ctld, need to be rebuilt to work with a new kernel.
563 The libatf-c and libatf-c++ major versions were downgraded to 0 and
564 1 respectively to match the upstream numbers. They were out of
565 sync because, when they were originally added to FreeBSD, the
566 upstream versions were not respected. These libraries are private
567 and not yet built by default, so renumbering them should be a
568 non-issue. However, unclean source trees will yield broken test
569 programs once the operator executes "make delete-old-libs" after a
572 Additionally, the atf-sh binary was made private by moving it into
573 /usr/libexec/. Already-built shell test programs will keep the
574 path to the old binary so they will break after "make delete-old"
577 If you are using WITH_TESTS=yes (not the default), wipe the object
578 tree and rebuild from scratch to prevent spurious test failures.
579 This is only needed once: the misnumbered libraries and misplaced
580 binaries have been added to OptionalObsoleteFiles.inc so they will
581 be removed during a clean upgrade.
584 Clang and llvm have been upgraded to 3.4.1 release.
587 We bogusly installed src.opts.mk in /usr/share/mk. This file should
588 be removed to avoid issues in the future (and has been added to
592 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
593 past, it affected all builds that used the bsd.*.mk files. The old
594 behavior was a bug, but people may have relied upon it. To get this
595 behavior back, you can .include /etc/src.conf from /etc/make.conf
596 (which is still global and isn't changed). This also changes the
597 behavior of incremental builds inside the tree of individual
598 directories. Set MAKESYSPATH to ".../share/mk" to do that.
599 Although this has survived make universe and some upgrade scenarios,
600 other upgrade scenarios may have broken. At least one form of
601 temporary breakage was fixed with MAKESYSPATH settings for buildworld
602 as well... In cases where MAKESYSPATH isn't working with this
603 setting, you'll need to set it to the full path to your tree.
605 One side effect of all this cleaning up is that bsd.compiler.mk
606 is no longer implicitly included by bsd.own.mk. If you wish to
607 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
611 The lindev device has been removed since /dev/full has been made a
612 standard device. __FreeBSD_version has been bumped.
615 The knob WITHOUT_VI was added to the base system, which controls
616 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
617 in order to reorder files share/termcap and didn't build ex(1) as a
618 build tool, so building/installing with WITH_VI is highly advised for
619 build hosts for older releases.
621 This issue has been fixed in stable/9 and stable/10 in r277022 and
622 r276991, respectively.
625 The YES_HESIOD knob has been removed. It has been obsolete for
626 a decade. Please move to using WITH_HESIOD instead or your builds
627 will silently lack HESIOD.
630 The uart(4) driver has been changed with respect to its handling
631 of the low-level console. Previously the uart(4) driver prevented
632 any process from changing the baudrate or the CLOCAL and HUPCL
633 control flags. By removing the restrictions, operators can make
634 changes to the serial console port without having to reboot.
635 However, when getty(8) is started on the serial device that is
636 associated with the low-level console, a misconfigured terminal
637 line in /etc/ttys will now have a real impact.
638 Before upgrading the kernel, make sure that /etc/ttys has the
639 serial console device configured as 3wire without baudrate to
640 preserve the previous behaviour. E.g:
641 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
644 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
645 to improve performance. To re-enable it, if needed, run rpcbind
646 with command line option -W.
649 Switched back to the GPL dtc compiler due to updates in the upstream
650 dts files not being supported by the BSDL dtc compiler. You will need
651 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
652 may result while building dtb files during a kernel build if you fail
653 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
656 Clang and llvm have been upgraded to 3.4 release.
659 The nve(4) driver has been removed. Please use the nfe(4) driver
660 for NVIDIA nForce MCP Ethernet adapters instead.
663 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
664 This could cause certain C++ applications using shared libraries built
665 against the previous version of libc++ to crash. The incompatibility
666 has now been fixed, but any C++ applications or shared libraries built
667 between r261283 and r261801 should be recompiled.
670 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
671 capability mode support. Please note that enabling the feature in
672 kernel is still highly recommended.
675 OpenSSH is now built with sandbox support, and will use sandbox as
676 the default privilege separation method. This requires Capsicum
677 capability mode support in kernel.
680 The libelf and libdwarf libraries have been updated to newer
681 versions from upstream. Shared library version numbers for
682 these two libraries were bumped. Any ports or binaries
683 requiring these two libraries should be recompiled.
684 __FreeBSD_version is bumped to 1100006.
687 If a Makefile in a tests/ directory was auto-generating a Kyuafile
688 instead of providing an explicit one, this would prevent such
689 Makefile from providing its own Kyuafile in the future during
690 NO_CLEAN builds. This has been fixed in the Makefiles but manual
691 intervention is needed to clean an objdir if you use NO_CLEAN:
692 # find /usr/obj -name Kyuafile | xargs rm -f
695 The behavior of gss_pseudo_random() for the krb5 mechanism
696 has changed, for applications requesting a longer random string
697 than produced by the underlying enctype's pseudo-random() function.
698 In particular, the random string produced from a session key of
699 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
700 be different at the 17th octet and later, after this change.
701 The counter used in the PRF+ construction is now encoded as a
702 big-endian integer in accordance with RFC 4402.
703 __FreeBSD_version is bumped to 1100004.
706 The WITHOUT_ATF build knob has been removed and its functionality
707 has been subsumed into the more generic WITHOUT_TESTS. If you were
708 using the former to disable the build of the ATF libraries, you
709 should change your settings to use the latter.
712 The default version of mtree is nmtree which is obtained from
713 NetBSD. The output is generally the same, but may vary
714 slightly. If you found you need identical output adding
715 "-F freebsd9" to the command line should do the trick. For the
716 time being, the old mtree is available as fmtree.
719 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
720 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
721 1.1.4_8 and verify bsdyml not linked in, before running "make
723 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
725 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
728 The stable/10 branch has been created in subversion from head
732 The rc.d/jail script has been updated to support jail(8)
733 configuration file. The "jail_<jname>_*" rc.conf(5) variables
734 for per-jail configuration are automatically converted to
735 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
736 This is transparently backward compatible. See below about some
737 incompatibilities and rc.conf(5) manual page for more details.
739 These variables are now deprecated in favor of jail(8) configuration
740 file. One can use "rc.d/jail config <jname>" command to generate
741 a jail(8) configuration file in /var/run/jail.<jname>.conf without
742 running the jail(8) utility. The default pathname of the
743 configuration file is /etc/jail.conf and can be specified by
744 using $jail_conf or $jail_<jname>_conf variables.
746 Please note that jail_devfs_ruleset accepts an integer at
747 this moment. Please consider to rewrite the ruleset name
751 BIND has been removed from the base system. If all you need
752 is a local resolver, simply enable and start the local_unbound
753 service instead. Otherwise, several versions of BIND are
754 available in the ports tree. The dns/bind99 port is one example.
756 With this change, nslookup(1) and dig(1) are no longer in the base
757 system. Users should instead use host(1) and drill(1) which are
758 in the base system. Alternatively, nslookup and dig can
759 be obtained by installing the dns/bind-tools port.
762 With the addition of unbound(8), a new unbound user is now
763 required during installworld. "mergemaster -p" can be used to
764 add the user prior to installworld, as documented in the handbook.
767 OpenSSH is now built with DNSSEC support, and will by default
768 silently trust signed SSHFP records. This can be controlled with
769 the VerifyHostKeyDNS client configuration setting. DNSSEC support
770 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
773 The GNU Compiler Collection and C++ standard library (libstdc++)
774 are no longer built by default on platforms where clang is the system
775 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
779 The PROCDESC kernel option is now part of the GENERIC kernel
780 configuration and is required for the rwhod(8) to work.
781 If you are using custom kernel configuration, you should include
785 The API and ABI related to the Capsicum framework was modified
786 in backward incompatible way. The userland libraries and programs
787 have to be recompiled to work with the new kernel. This includes the
788 following libraries and programs, but the whole buildworld is
789 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
790 kdump, procstat, rwho, rwhod, uniq.
793 AES-NI intrinsic support has been added to gcc. The AES-NI module
794 has been updated to use this support. A new gcc is required to build
795 the aesni module on both i386 and amd64.
798 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
799 Thus "device padlock_rng" and "device rdrand_rng" should be
800 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
803 WITH_ICONV has been split into two feature sets. WITH_ICONV now
804 enables just the iconv* functionality and is now on by default.
805 WITH_LIBICONV_COMPAT enables the libiconv api and link time
806 compatability. Set WITHOUT_ICONV to build the old way.
807 If you have been using WITH_ICONV before, you will very likely
808 need to turn on WITH_LIBICONV_COMPAT.
811 INVARIANTS option now enables DEBUG for code with OpenSolaris and
812 Illumos origin, including ZFS. If you have INVARIANTS in your
813 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
815 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
816 locks if WITNESS option was set. Because that generated a lot of
817 witness(9) reports and all of them were believed to be false
818 positives, this is no longer done. New option OPENSOLARIS_WITNESS
819 can be used to achieve the previous behavior.
822 Timer values in IPv6 data structures now use time_uptime instead
823 of time_second. Although this is not a user-visible functional
824 change, userland utilities which directly use them---ndp(8),
825 rtadvd(8), and rtsold(8) in the base system---need to be updated
829 find -delete can now delete the pathnames given as arguments,
830 instead of only files found below them or if the pathname did
831 not contain any slashes. Formerly, the following error message
834 find: -delete: <path>: relative path potentially not safe
836 Deleting the pathnames given as arguments can be prevented
837 without error messages using -mindepth 1 or by changing
838 directory and passing "." as argument to find. This works in the
839 old as well as the new version of find.
842 Behavior of devfs rules path matching has been changed.
843 Pattern is now always matched against fully qualified devfs
844 path and slash characters must be explicitly matched by
845 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
846 subdirectories must be reviewed.
849 The default ARM ABI has changed to the ARM EABI. The old ABI is
850 incompatible with the ARM EABI and all programs and modules will
851 need to be rebuilt to work with a new kernel.
853 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
855 NOTE: Support for the old ABI will be removed in the future and
856 users are advised to upgrade.
859 pkg_install has been disconnected from the build if you really need it
860 you should add WITH_PKGTOOLS in your src.conf(5).
863 Most of network statistics structures were changed to be able
864 keep 64-bits counters. Thus all tools, that work with networking
865 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
868 Fix a bug that allowed a tracing process (e.g. gdb) to write
869 to a memory-mapped file in the traced process's address space
870 even if neither the traced process nor the tracing process had
871 write access to that file.
874 CVS has been removed from the base system. An exact copy
875 of the code is available from the devel/cvs port.
878 Some people report the following error after the switch to bmake:
880 make: illegal option -- J
881 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
883 *** [buildworld] Error code 2
885 this likely due to an old instance of make in
886 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
887 which src/Makefile will use that blindly, if it exists, so if
888 you see the above error:
890 rm -rf `make -V MAKEPATH`
895 Use bmake by default.
896 Whereas before one could choose to build with bmake via
897 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
898 make. The goal is to remove these knobs for 10-RELEASE.
900 It is worth noting that bmake (like gmake) treats the command
901 line as the unit of failure, rather than statements within the
902 command line. Thus '(cd some/where && dosomething)' is safer
903 than 'cd some/where; dosomething'. The '()' allows consistent
904 behavior in parallel build.
907 Fix a bug that allows NFS clients to issue READDIR on files.
910 The WITHOUT_IDEA option has been removed because
911 the IDEA patent expired.
914 The sysctl which controls TRIM support under ZFS has been renamed
915 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
919 The mergemaster command now uses the default MAKEOBJDIRPREFIX
920 rather than creating it's own in the temporary directory in
921 order allow access to bootstrapped versions of tools such as
922 install and mtree. When upgrading from version of FreeBSD where
923 the install command does not support -l, you will need to
924 install a new mergemaster command if mergemaster -p is required.
925 This can be accomplished with the command (cd src/usr.sbin/mergemaster
929 Legacy ATA stack, disabled and replaced by new CAM-based one since
930 FreeBSD 9.0, completely removed from the sources. Kernel modules
931 atadisk and atapi*, user-level tools atacontrol and burncd are
932 removed. Kernel option `options ATA_CAM` is now permanently enabled
936 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
937 and socketpair(2). Software, in particular Kerberos, may
938 automatically detect and use these during building. The resulting
939 binaries will not work on older kernels.
942 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
943 information, see the respective 20130304 entry).
946 Recent commits to callout(9) changed the size of struct callout,
947 so the KBI is probably heavily disturbed. Also, some functions
948 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
949 by macros. Every kernel module using it won't load, so rebuild
952 The ctl device has been re-enabled in GENERIC for i386 and amd64,
953 but does not initialize by default (because of the new CTL_DISABLE
954 option) to save memory. To re-enable it, remove the CTL_DISABLE
955 option from the kernel config file or set kern.cam.ctl.disable=0
956 in /boot/loader.conf.
959 The ctl device has been disabled in GENERIC for i386 and amd64.
960 This was done due to the extra memory being allocated at system
961 initialisation time by the ctl driver which was only used if
962 a CAM target device was created. This makes a FreeBSD system
963 unusable on 128MB or less of RAM.
966 A new compression method (lz4) has been merged to -HEAD. Please
967 refer to zpool-features(7) for more information.
969 Please refer to the "ZFS notes" section of this file for information
970 on upgrading boot ZFS pools.
973 A BSD-licensed patch(1) variant has been added and is installed
974 as bsdpatch, being the GNU version the default patch.
975 To inverse the logic and use the BSD-licensed one as default,
976 while having the GNU version installed as gnupatch, rebuild
977 and install world with the WITH_BSD_PATCH knob set.
980 Due to the use of the new -l option to install(1) during build
981 and install, you must take care not to directly set the INSTALL
982 make variable in your /etc/make.conf, /etc/src.conf, or on the
983 command line. If you wish to use the -C flag for all installs
984 you may be able to add INSTALL+=-C to /etc/make.conf or
988 The install(1) option -M has changed meaning and now takes an
989 argument that is a file or path to append logs to. In the
990 unlikely event that -M was the last option on the command line
991 and the command line contained at least two files and a target
992 directory the first file will have logs appended to it. The -M
993 option served little practical purpose in the last decade so its
994 use is expected to be extremely rare.
997 After switching to Clang as the default compiler some users of ZFS
998 on i386 systems started to experience stack overflow kernel panics.
999 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1002 GEOM_LABEL now mangles label names read from file system metadata.
1003 Mangling affect labels containing spaces, non-printable characters,
1004 '%' or '"'. Device names in /etc/fstab and other places may need to
1008 By default, only the 10 most recent kernel dumps will be saved. To
1009 restore the previous behaviour (no limit on the number of kernel dumps
1010 stored in the dump directory) add the following line to /etc/rc.conf:
1015 With the addition of auditdistd(8), a new auditdistd user is now
1016 required during installworld. "mergemaster -p" can be used to
1017 add the user prior to installworld, as documented in the handbook.
1020 The sin6_scope_id member variable in struct sockaddr_in6 is now
1021 filled by the kernel before passing the structure to the userland via
1022 sysctl or routing socket. This means the KAME-specific embedded scope
1023 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1024 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1025 __FreeBSD_version is bumped to 1000025.
1028 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1029 This means that the world and kernel will be compiled with clang
1030 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1031 and /usr/bin/cpp. To disable this behavior and revert to building
1032 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1033 of current may need to bootstrap WITHOUT_CLANG first if the clang
1034 build fails (its compatibility window doesn't extend to the 9 stable
1038 The IPFIREWALL_FORWARD kernel option has been removed. Its
1039 functionality now turned on by default.
1042 The ZERO_COPY_SOCKET kernel option has been removed and
1043 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1044 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1045 mechanism which is not safe and may result in kernel crashes.
1046 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1047 driver supports disposeable external page sized mbuf storage.
1048 Proper replacements for both zero-copy mechanisms are under
1049 consideration and will eventually lead to complete removal
1050 of the two kernel options.
1053 The IPv4 network stack has been converted to network byte
1054 order. The following modules need to be recompiled together
1055 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1056 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1059 Support for non-MPSAFE filesystems was removed from VFS. The
1060 VFS_VERSION was bumped, all filesystem modules shall be
1064 All the non-MPSAFE filesystems have been disconnected from
1065 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1066 portalfs, smbfs, xfs.
1069 The interface cloning API and ABI has changed. The following
1070 modules need to be recompiled together with kernel:
1071 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1072 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1073 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1076 The sdhci driver was split in two parts: sdhci (generic SD Host
1077 Controller logic) and sdhci_pci (actual hardware driver).
1078 No kernel config modifications are required, but if you
1079 load sdhc as a module you must switch to sdhci_pci instead.
1082 Import the FUSE kernel and userland support into base system.
1085 The GNU sort(1) program has been removed since the BSD-licensed
1086 sort(1) has been the default for quite some time and no serious
1087 problems have been reported. The corresponding WITH_GNU_SORT
1091 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1092 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1096 The net80211(4) ABI has been changed to allow for improved driver
1097 PS-POLL and power-save support. All wireless drivers need to be
1098 recompiled to work with the new kernel.
1101 The random(4) support for the VIA hardware random number
1102 generator (`PADLOCK') is no longer enabled unconditionally.
1103 Add the padlock_rng device in the custom kernel config if
1104 needed. The GENERIC kernels on i386 and amd64 do include the
1105 device, so the change only affects the custom kernel
1109 The pf(4) packet filter ABI has been changed. pfctl(8) and
1110 snmp_pf module need to be recompiled to work with new kernel.
1113 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1114 to -HEAD. Pools that have empty_bpobj in active state can not be
1115 imported read-write with ZFS implementations that do not support
1116 this feature. For more information read the zpool-features(5)
1120 The sparc64 ZFS loader has been changed to no longer try to auto-
1121 detect ZFS providers based on diskN aliases but now requires these
1122 to be explicitly listed in the OFW boot-device environment variable.
1125 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1126 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1127 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1130 The following sysctls and tunables have been renamed for consistency
1131 with other variables:
1132 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1133 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1136 The sort utility has been replaced with BSD sort. For now, GNU sort
1137 is also available as "gnusort" or the default can be set back to
1138 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1139 installed as "bsdsort".
1142 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1143 Starting with this version the old system of ZFS pool versioning
1144 is superseded by "feature flags". This concept enables forward
1145 compatibility against certain future changes in functionality of ZFS
1146 pools. The first read-only compatible "feature flag" for ZFS pools
1147 is named "com.delphix:async_destroy". For more information
1148 read the new zpool-features(5) manual page.
1149 Please refer to the "ZFS notes" section of this file for information
1150 on upgrading boot ZFS pools.
1153 The malloc(3) implementation embedded in libc now uses sources imported
1154 as contrib/jemalloc. The most disruptive API change is to
1155 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1156 delete it prior to installworld, and optionally re-create it using the
1157 new format after rebooting. See malloc.conf(5) for details
1158 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1162 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1163 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1164 now spelled mips. This is to aid compatibility with third-party
1165 software that expects this naming scheme in uname(3). Little-endian
1166 settings are unchanged. If you are updating a big-endian mips64 machine
1167 from before this change, you may need to set MACHINE_ARCH=mips64 in
1168 your environment before the new build system will recognize your machine.
1171 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1175 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1176 nullfs(5) did not pass through all behaviours to the underlying layer,
1177 as a result if we bound to a socket on the lower layer we could connect
1178 only to the lower path; if we bound to the upper layer we could connect
1179 only to the upper path. The new behavior is one can connect to both the
1180 lower and the upper paths regardless what layer path one binds to.
1183 The getifaddrs upgrade path broken with 20111215 has been restored.
1184 If you have upgraded in between 20111215 and 20120209 you need to
1185 recompile libc again with your kernel. You still need to recompile
1186 world to be able to configure CARP but this restriction already
1187 comes from 20111215.
1190 The set_rcvar() function has been removed from /etc/rc.subr. All
1191 base and ports rc.d scripts have been updated, so if you have a
1192 port installed with a script in /usr/local/etc/rc.d you can either
1193 hand-edit the rcvar= line, or reinstall the port.
1195 An easy way to handle the mass-update of /etc/rc.d:
1196 rm /etc/rc.d/* && mergemaster -i
1199 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1200 on the current CPU and prevents other threads from running.
1201 This behavior can be reverted using the kern.stop_scheduler_on_panic
1203 The new behavior can be incompatible with kern.sync_on_panic.
1206 The carp(4) facility has been changed significantly. Configuration
1207 of the CARP protocol via ifconfig(8) has changed, as well as format
1208 of CARP events submitted to devd(8) has changed. See manual pages
1209 for more information. The arpbalance feature of carp(4) is currently
1210 not supported anymore.
1212 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1213 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1214 need to be recompiled.
1217 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1221 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1222 explicitely support non-MPSAFE filesystems.
1223 It is on by default for all supported platform at this present
1227 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1228 i386 and pc98 GENERIC kernel configuration files.
1231 sysinstall has been removed
1234 The stable/9 branch created in subversion. This corresponds to the
1235 RELENG_9 branch in CVS.
1241 Avoid using make -j when upgrading. While generally safe, there are
1242 sometimes problems using -j to upgrade. If your upgrade fails with
1243 -j, please try again without -j. From time to time in the past there
1244 have been problems using -j with buildworld and/or installworld. This
1245 is especially true when upgrading between "distant" versions (eg one
1246 that cross a major release boundary or several minor releases, or when
1247 several months have passed on the -current branch).
1249 Sometimes, obscure build problems are the result of environment
1250 poisoning. This can happen because the make utility reads its
1251 environment when searching for values for global variables. To run
1252 your build attempts in an "environmental clean room", prefix all make
1253 commands with 'env -i '. See the env(1) manual page for more details.
1255 When upgrading from one major version to another it is generally best
1256 to upgrade to the latest code in the currently installed branch first,
1257 then do an upgrade to the new branch. This is the best-tested upgrade
1258 path, and has the highest probability of being successful. Please try
1259 this approach before reporting problems with a major version upgrade.
1261 When upgrading a live system, having a root shell around before
1262 installing anything can help undo problems. Not having a root shell
1263 around can lead to problems if pam has changed too much from your
1264 starting point to allow continued authentication after the upgrade.
1266 This file should be read as a log of events. When a later event changes
1267 information of a prior event, the prior event should not be deleted.
1268 Instead, a pointer to the entry with the new information should be
1269 placed in the old entry. Readers of this file should also sanity check
1270 older entries before relying on them blindly. Authors of new entries
1271 should write them with this in mind.
1275 When upgrading the boot ZFS pool to a new version, always follow
1278 1.) recompile and reinstall the ZFS boot loader and boot block
1279 (this is part of "make buildworld" and "make installworld")
1281 2.) update the ZFS boot block on your boot drive
1283 The following example updates the ZFS boot block on the first
1284 partition (freebsd-boot) of a GPT partitioned drive ada0:
1285 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1287 Non-boot pools do not need these updates.
1291 If you are updating from a prior version of FreeBSD (even one just
1292 a few days old), you should follow this procedure. It is the most
1293 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1295 make kernel-toolchain
1296 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1297 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1299 To test a kernel once
1300 ---------------------
1301 If you just want to boot a kernel once (because you are not sure
1302 if it works, or if you want to boot a known bad kernel to provide
1303 debugging information) run
1304 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1305 nextboot -k testkernel
1307 To just build a kernel when you know that it won't mess you up
1308 --------------------------------------------------------------
1309 This assumes you are already running a CURRENT system. Replace
1310 ${arch} with the architecture of your machine (e.g. "i386",
1311 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1313 cd src/sys/${arch}/conf
1314 config KERNEL_NAME_HERE
1315 cd ../compile/KERNEL_NAME_HERE
1320 If this fails, go to the "To build a kernel" section.
1322 To rebuild everything and install it on the current system.
1323 -----------------------------------------------------------
1324 # Note: sometimes if you are running current you gotta do more than
1325 # is listed here if you are upgrading from a really old current.
1327 <make sure you have good level 0 dumps>
1329 make kernel KERNCONF=YOUR_KERNEL_HERE
1331 <reboot in single user> [3]
1338 To cross-install current onto a separate partition
1339 --------------------------------------------------
1340 # In this approach we use a separate partition to hold
1341 # current's root, 'usr', and 'var' directories. A partition
1342 # holding "/", "/usr" and "/var" should be about 2GB in
1345 <make sure you have good level 0 dumps>
1348 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1349 <maybe newfs current's root partition>
1350 <mount current's root partition on directory ${CURRENT_ROOT}>
1351 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1352 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1353 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1354 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1355 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1356 <reboot into current>
1357 <do a "native" rebuild/install as described in the previous section>
1358 <maybe install compatibility libraries from ports/misc/compat*>
1362 To upgrade in-place from stable to current
1363 ----------------------------------------------
1364 <make sure you have good level 0 dumps>
1366 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1368 <reboot in single user> [3]
1375 Make sure that you've read the UPDATING file to understand the
1376 tweaks to various things you need. At this point in the life
1377 cycle of current, things change often and you are on your own
1378 to cope. The defaults can also change, so please read ALL of
1379 the UPDATING entries.
1381 Also, if you are tracking -current, you must be subscribed to
1382 freebsd-current@freebsd.org. Make sure that before you update
1383 your sources that you have read and understood all the recent
1384 messages there. If in doubt, please track -stable which has
1385 much fewer pitfalls.
1387 [1] If you have third party modules, such as vmware, you
1388 should disable them at this point so they don't crash your
1391 [3] From the bootblocks, boot -s, and then do
1396 adjkerntz -i # if CMOS is wall time
1397 Also, when doing a major release upgrade, it is required that
1398 you boot into single user mode to do the installworld.
1400 [4] Note: This step is non-optional. Failure to do this step
1401 can result in a significant reduction in the functionality of the
1402 system. Attempting to do it by hand is not recommended and those
1403 that pursue this avenue should read this file carefully, as well
1404 as the archives of freebsd-current and freebsd-hackers mailing lists
1405 for potential gotchas. The -U option is also useful to consider.
1406 See mergemaster(8) for more information.
1408 [5] Usually this step is a noop. However, from time to time
1409 you may need to do this if you get unknown user in the following
1410 step. It never hurts to do it all the time. You may need to
1411 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1412 install) after the buildworld before this step if you last updated
1413 from current before 20130425 or from -stable before 20130430.
1415 [6] This only deletes old files and directories. Old libraries
1416 can be deleted by "make delete-old-libs", but you have to make
1417 sure that no program is using those libraries anymore.
1419 [8] In order to have a kernel that can run the 4.x binaries needed to
1420 do an installworld, you must include the COMPAT_FREEBSD4 option in
1421 your kernel. Failure to do so may leave you with a system that is
1422 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1423 required to run the 5.x binaries on more recent kernels. And so on
1424 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1426 Make sure that you merge any new devices from GENERIC since the
1427 last time you updated your kernel config file.
1429 [9] When checking out sources, you must include the -P flag to have
1430 cvs prune empty directories.
1432 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1433 "?=" instead of the "=" assignment operator, so that buildworld can
1434 override the CPUTYPE if it needs to.
1436 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1437 not on the command line, or in /etc/make.conf. buildworld will
1438 warn if it is improperly defined.
1441 This file contains a list, in reverse chronological order, of major
1442 breakages in tracking -current. It is not guaranteed to be a complete
1443 list of such breakages, and only contains entries since September 23, 2011.
1444 If you need to see UPDATING entries from before that date, you will need
1445 to fetch an UPDATING file from an older FreeBSD release.
1447 Copyright information:
1449 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1451 Redistribution, publication, translation and use, with or without
1452 modification, in full or in part, in any form or format of this
1453 document are permitted without further permission from the author.
1455 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1456 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1457 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1458 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1459 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1460 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1461 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1462 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1463 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1464 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1465 POSSIBILITY OF SUCH DAMAGE.
1467 Contact Warner Losh if you have any questions about your use of