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