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 https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-src.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 12.x IS SLOW:
20 FreeBSD 12.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 ****************************** SPECIAL WARNING: ******************************
37 Due to a bug in some versions of clang that's very hard to workaround in
38 the upgrade process, to upgrade to -current you must first upgrade
39 either stable/9 after r286035 or stable/10 after r286033 (including
40 10.3-RELEASE) or current after r286007 (including stable/11 and
41 11.0-RELEASE). These revisions post-date the 10.2 and 9.3 releases, so
42 you'll need to take the unusual step of upgrading to the tip of the
43 stable branch before moving to 11 or -current via a source upgrade.
44 stable/11 and 11.0-RELEASE have working newer compiler. This differs
45 from the historical situation where one could upgrade from anywhere on
46 the last couple of stable branches, so be careful.
48 If you're running a hybrid system on 9.x or 10.x with an updated clang
49 compiler or are using an supported external toolchain, the build system
50 will allow the upgrade. Otherwise it will print a reminder.
52 ****************************** SPECIAL WARNING: ******************************
55 libstand has turned into a private library for sys/boot use only.
56 It is no longer supported as a public interface outside of sys/boot.
59 The arm port has split armv6 into armv6 and armv7. armv7 is now
60 a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
61 and are running a kernel from before r324363, you will need to add
62 MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
65 When building multiple kernels using KERNCONF, non-existent KERNCONF
66 files will produce an error and buildkernel will fail. Previously
67 missing KERNCONF files silently failed giving no indication as to
68 why, only to subsequently discover during installkernel that the
69 desired kernel was never built in the first place.
72 The default serial number format for CTL LUNs has changed. This will
73 affect users who use /dev/diskid/* device nodes, or whose FibreChannel
74 or iSCSI clients care about their LUNs' serial numbers. Users who
75 require serial number stability should hardcode serial numbers in
79 For 32-bit arm compiled for hard-float support, soft-floating point
80 binaries now always get their shared libraries from
81 LD_SOFT_LIBRARY_PATH (in the past, this was only used if
82 /usr/libsoft also existed). Only users with a hard-float ld.so, but
83 soft-float everything else should be affected.
86 The geli password typed at boot is now hidden. To restore the previous
87 behavior, see geli(8) for configuration options.
90 Move PMTUD blackhole counters to TCPSTATS and remove them from bare
91 sysctl values. Minor nit, but requires a rebuild of both world/kernel
95 "make check" behavior (made in ^/head@r295380) has been changed to
96 execute from a limited sandbox, as opposed to executing from
100 - The "beforecheck" and "aftercheck" targets are now specified.
101 - ${CHECKDIR} (added in commit noted above) has been removed.
102 - Legacy behavior can be enabled by setting
103 WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
105 If the limited sandbox mode is enabled, "make check" will execute
106 "make distribution", then install, execute the tests, and clean up the
107 sandbox if successful.
109 The "make distribution" and "make install" targets are typically run as
110 root to set appropriate permissions and ownership at installation time.
111 The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
112 environment if executing "make check" with limited sandbox mode using
113 an unprivileged user.
116 Since the switch to GPT disk labels, fsck for UFS/FFS has been
117 unable to automatically find alternate superblocks. As of r322297,
118 the information needed to find alternate superblocks has been
119 moved to the end of the area reserved for the boot block.
120 Filesystems created with a newfs of this vintage or later
121 will create the recovery information. If you have a filesystem
122 created prior to this change and wish to have a recovery block
123 created for your filesystem, you can do so by running fsck in
124 forground mode (i.e., do not use the -p or -y options). As it
125 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
126 to which you should answer yes.
129 As of r321665, an NFSv4 server configuration that services
130 Kerberos mounts or clients that do not support the uid/gid in
131 owner/owner_group string capability, must explicitly enable
132 the nfsuserd daemon by adding nfsuserd_enable="YES" to the
133 machine's /etc/rc.conf file.
136 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
137 Please see the 20141231 entry below for information about prerequisites
138 and upgrading, if you are not already using clang 3.5.0 or higher.
141 WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
142 r-commands (rlogin, rsh, etc.) to be built with the base system.
145 The FreeBSD/powerpc platform now uses a 64-bit type for time_t. This is
146 a very major ABI incompatible change, so users of FreeBSD/powerpc must
147 be careful when performing source upgrades. It is best to run
148 'make installworld' from an alternate root system, either a live
149 CD/memory stick, or a temporary root partition. Additionally, all ports
150 must be recompiled. powerpc64 is largely unaffected, except in the case
151 of 32-bit compatibility. All 32-bit binaries will be affected.
154 Forward compatibility for the "ino64" project have been committed. This
155 will allow most new binaries to run on older kernels in a limited
156 fashion. This prevents many of the common foot-shooting actions in the
157 upgrade as well as the limited ability to roll back the kernel across
158 the ino64 upgrade. Complicated use cases may not work properly, though
159 enough simpler ones work to allow recovery in most situations.
162 Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
163 if you require the GPL compiler.
166 The internal ABI used for communication between the NFS kernel modules
167 was changed by r320085, so __FreeBSD_version was bumped to
168 ensure all the NFS related modules are updated together.
171 The ABI of struct event was changed by extending the data
172 member to 64bit and adding ext fields. For upgrade, same
173 precautions as for the entry 20170523 "ino64" must be
177 The GNU roff toolchain has been removed from base. To render manpages
178 which are not supported by mandoc(1), man(1) can fallback on GNU roff
179 from ports (and recommends to install it).
180 To render roff(7) documents, consider using GNU roff from ports or the
181 heirloom doctools roff toolchain from ports via pkg install groff or
182 via pkg install heirloom-doctools.
185 The ath(4) and ath_hal(4) modules now build piecemeal to allow for
186 smaller runtime footprint builds. This is useful for embedded systems
187 which only require one chipset support.
189 If you load it as a module, make sure this is in /boot/loader.conf:
193 This will load the HAL, all chip/RF backends and if_ath_pci.
194 If you have if_ath_pci in /boot/loader.conf, ensure it is after
195 if_ath or it will not load any HAL chipset support.
197 If you want to selectively load things (eg on ye cheape ARM/MIPS
198 platforms where RAM is at a premium) you should:
201 * load the chip modules in question
202 * load ath_rate, ath_dfs
204 * load if_ath_pci and/or if_ath_ahb depending upon your particular
205 bus bind type - this is where probe/attach is done.
207 For further comments/feedback, poke adrian@ .
210 The "ino64" 64-bit inode project has been committed, which extends
211 a number of types to 64 bits. Upgrading in place requires care and
212 adherence to the documented upgrade procedure.
214 If using a custom kernel configuration ensure that the
215 COMPAT_FREEBSD11 option is included (as during the upgrade the
216 system will be running the ino64 kernel with the existing world).
218 For the safest in-place upgrade begin by removing previous build
219 artifacts via "rm -rf /usr/obj/*". Then, carefully follow the
220 full procedure documented below under the heading "To rebuild
221 everything and install it on the current system." Specifically,
222 a reboot is required after installing the new kernel before
226 The NATM framework including the en(4), fatm(4), hatm(4), and
227 patm(4) devices has been removed. Consumers should plan a
228 migration before the end-of-life date for FreeBSD 11.
231 GNU diff has been replaced by a BSD licensed diff. Some features of GNU
232 diff has not been implemented, if those are needed a newer version of
233 GNU diff is available via the diffutils package under the gdiff name.
236 As of r316810 for ipfilter, keep frags is no longer assumed when
237 keep state is specified in a rule. r316810 aligns ipfilter with
238 documentation in man pages separating keep frags from keep state.
239 This allows keep state to be specified without forcing keep frags
240 and allows keep frags to be specified independently of keep state.
241 To maintain previous behaviour, also specify keep frags with
242 keep state (as documented in ipf.conf.5).
245 arm64 builds now use the base system LLD 4.0.0 linker by default,
246 instead of requiring that the aarch64-binutils port or package be
247 installed. To continue using aarch64-binutils, set
248 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
251 The UDP optimization in entry 20160818 that added the sysctl
252 net.inet.udp.require_l2_bcast has been reverted. L2 broadcast
253 packets will no longer be treated as L3 broadcast packets.
256 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
257 use any explicitly assigned loopback address available in the jail
258 instead of using the first assigned address of the jail.
261 The ctl.ko module no longer implements the iSCSI target frontend:
262 cfiscsi.ko does instead.
264 If building cfiscsi.ko as a kernel module, the module can be loaded
265 via one of the following methods:
266 - `cfiscsi_load="YES"` in loader.conf(5).
267 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
268 - ctladm(8)/ctld(8), when compiled with iSCSI support
269 (`WITH_ISCSI=yes` in src.conf(5))
271 Please see cfiscsi(4) for more details.
274 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
275 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
276 same source (previously, the dependency of mmcsd.ko on mmc.ko was
277 missing, but mmcsd.ko now will refuse to load if it is incompatible
281 The syntax of ipfw(8) named states was changed to avoid ambiguity.
282 If you have used named states in the firewall rules, you need to modify
283 them after installworld and before rebooting. Now named states must
284 be prefixed with colon.
287 The old drm (sys/dev/drm/) drivers for i915 and radeon have been
288 removed as the userland we provide cannot use them. The KMS version
289 (sys/dev/drm2) supports the same hardware.
292 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
293 Please see the 20141231 entry below for information about prerequisites
294 and upgrading, if you are not already using clang 3.5.0 or higher.
297 The code that provides support for ZFS .zfs/ directory functionality
298 has been reimplemented. It's not possible now to create a snapshot
299 by mkdir under .zfs/snapshot/. That should be the only user visible
303 EISA bus support has been removed. The WITH_EISA option is no longer
307 MCA bus support has been removed.
310 The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
311 WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
314 The EM_MULTIQUEUE kernel configuration option is deprecated now that
315 the em(4) driver conforms to iflib specifications.
318 The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
319 IFLIB. If you have a custom kernel configuration that excludes em(4)
320 but you use igb(4), you need to re-add em(4) to your custom configuration.
323 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
324 Please see the 20141231 entry below for information about prerequisites
325 and upgrading, if you are not already using clang 3.5.0 or higher.
328 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
329 Please see the 20141231 entry below for information about prerequisites
330 and upgrading, if you are not already using clang 3.5.0 or higher.
333 The layout of the pmap structure has changed for powerpc to put the pmap
334 statistics at the front for all CPU variations. libkvm(3) and all tools
335 that link against it need to be recompiled.
338 isl(4) and cyapa(4) drivers now require a new driver,
339 chromebook_platform(4), to work properly on Chromebook-class hardware.
340 On other types of hardware the drivers may need to be configured using
341 device hints. Please see the corresponding manual pages for details.
344 The urtwn(4) driver was merged into rtwn(4) and now consists of
345 rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
347 Also, firmware for RTL8188CE was renamed due to possible name
348 conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
351 GNU rcs has been removed from base. It is available as packages:
352 - rcs: Latest GPLv3 GNU rcs version.
353 - rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
357 Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
358 modules now requires that the kernel configuration contain the
359 TCP_HHOOK option. (This option is included in the GENERIC kernel.)
362 The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
363 ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
366 Relocatable object files with the extension of .So have been renamed
367 to use an extension of .pico instead. The purpose of this change is
368 to avoid a name clash with shared libraries on case-insensitive file
369 systems. On those file systems, foo.So is the same file as foo.so.
372 GNU rcs has been turned off by default. It can (temporarily) be built
373 again by adding WITH_RCS knob in src.conf.
374 Otherwise, GNU rcs is available from packages:
375 - rcs: Latest GPLv3 GNU rcs version.
376 - rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
379 The backup_uses_rcs functionality has been removed from rc.subr.
382 The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
383 two separate components, QUEUE_MACRO_DEBUG_TRACE and
384 QUEUE_MACRO_DEBUG_TRASH. Define both for the original
385 QUEUE_MACRO_DEBUG behavior.
388 r304787 changed some ioctl interfaces between the iSCSI userspace
389 programs and the kernel. ctladm, ctld, iscsictl, and iscsid must be
390 rebuilt to work with new kernels. __FreeBSD_version has been bumped
394 The UDP receive code has been updated to only treat incoming UDP
395 packets that were addressed to an L2 broadcast address as L3
396 broadcast packets. It is not expected that this will affect any
397 standards-conforming UDP application. The new behaviour can be
398 disabled by setting the sysctl net.inet.udp.require_l2_bcast to
402 Remove the openbsd_poll system call.
403 __FreeBSD_version has been bumped because of this.
406 The libc stub for the pipe(2) system call has been replaced with
407 a wrapper that calls the pipe2(2) system call and the pipe(2)
408 system call is now only implemented by the kernels that include
409 "options COMPAT_FREEBSD10" in their config file (this is the
410 default). Users should ensure that this option is enabled in
411 their kernel or upgrade userspace to r302092 before upgrading their
415 CAM will now strip leading spaces from SCSI disks' serial numbers.
416 This will affect users who create UFS filesystems on SCSI disks using
417 those disk's diskid device nodes. For example, if /etc/fstab
418 previously contained a line like
419 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
420 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
421 transforms like gmirror may also be affected. ZFS users should
425 The bitstring(3) API has been updated with new functionality and
426 improved performance. But it is binary-incompatible with the old API.
427 Objects built with the new headers may not be linked against objects
428 built with the old headers.
431 The brk and sbrk functions have been removed from libc on arm64.
432 Binutils from ports has been updated to not link to these
433 functions and should be updated to the latest version before
434 installing a new libc.
437 The armv6 port now defaults to hard float ABI. Limited support
438 for running both hardfloat and soft float on the same system
439 is available using the libraries installed with -DWITH_LIBSOFT.
440 This has only been tested as an upgrade path for installworld
441 and packages may fail or need manual intervention to run. New
442 packages will be needed.
444 To update an existing self-hosted armv6hf system, you must add
445 TARGET_ARCH=armv6 on the make command line for both the build
446 and the install steps.
449 Kernel modules compiled outside of a kernel build now default to
450 installing to /boot/modules instead of /boot/kernel. Many kernel
451 modules built this way (such as those in ports) already overrode
452 KMODDIR explicitly to install into /boot/modules. However,
453 manually building and installing a module from /sys/modules will
454 now install to /boot/modules instead of /boot/kernel.
457 The CAM I/O scheduler has been committed to the kernel. There should be
458 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
459 list of known rogues that claim support for this but actually corrupt
460 data is believed to be complete, be on the lookout for data
461 corruption. The known rogue list is believed to be complete:
463 o Crucial MX100, M550 drives with MU01 firmware.
464 o Micron M510 and M550 drives with MU01 firmware.
465 o Micron M500 prior to MU07 firmware
466 o Samsung 830, 840, and 850 all firmwares
467 o FCCT M500 all firmwares
469 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
470 with working NCQ TRIM. For Micron branded drives, see your sales rep for
471 updated firmware. Black listed drives will work correctly because these
472 drives work correctly so long as no NCQ TRIMs are sent to them. Given
473 this list is the same as found in Linux, it's believed there are no
474 other rogues in the market place. All other models from the above
477 To be safe, if you are at all concerned, you can quirk each of your
478 drives to prevent NCQ from being sent by setting:
479 kern.cam.ada.X.quirks="0x2"
480 in loader.conf. If the drive requires the 4k sector quirk, set the
484 The FAST_DEPEND build option has been removed and its functionality is
485 now the one true way. The old mkdep(1) style of 'make depend' has
486 been removed. See 20160311 for further details.
489 Resource range types have grown from unsigned long to uintmax_t. All
490 drivers, and anything using libdevinfo, need to be recompiled.
493 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
494 builds. It no longer runs mkdep(1) during 'make depend', and the
495 'make depend' stage can safely be skipped now as it is auto ran
496 when building 'make all' and will generate all SRCS and DPSRCS before
497 building anything else. Dependencies are gathered at compile time with
498 -MF flags kept in separate .depend files per object file. Users should
499 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
503 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
504 kernel modules. Therefore, if you load any kernel modules at boot time,
505 please install the boot loaders after you install the kernel, but before
509 make kernel KERNCONF=YOUR_KERNEL_HERE
510 make -C sys/boot install
511 <reboot in single user>
513 Then follow the usual steps, described in the General Notes section,
517 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
518 see the 20141231 entry below for information about prerequisites and
519 upgrading, if you are not already using clang 3.5.0 or higher.
522 The AIO subsystem is now a standard part of the kernel. The
523 VFS_AIO kernel option and aio.ko kernel module have been removed.
524 Due to stability concerns, asynchronous I/O requests are only
525 permitted on sockets and raw disks by default. To enable
526 asynchronous I/O requests on all file types, set the
527 vfs.aio.enable_unsafe sysctl to a non-zero value.
530 The ELF object manipulation tool objcopy is now provided by the
531 ELF Tool Chain project rather than by GNU binutils. It should be a
532 drop-in replacement, with the addition of arm64 support. The
533 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
534 to obtain the GNU version if necessary.
537 Building ZFS pools on top of zvols is prohibited by default. That
538 feature has never worked safely; it's always been prone to deadlocks.
539 Using a zvol as the backing store for a VM guest's virtual disk will
540 still work, even if the guest is using ZFS. Legacy behavior can be
541 restored by setting vfs.zfs.vol.recursive=1.
544 The NONE and HPN patches has been removed from OpenSSH. They are
545 still available in the security/openssh-portable port.
548 With the addition of ypldap(8), a new _ypldap user is now required
549 during installworld. "mergemaster -p" can be used to add the user
550 prior to installworld, as documented in the handbook.
553 The tftp loader (pxeboot) now uses the option root-path directive. As a
554 consequence it no longer looks for a pxeboot.4th file on the tftp
555 server. Instead it uses the regular /boot infrastructure as with the
559 The code to start recording plug and play data into the modules has
560 been committed. While the old tools will properly build a new kernel,
561 a number of warnings about "unknown metadata record 4" will be produced
562 for an older kldxref. To avoid such warnings, make sure to rebuild
563 the kernel toolchain (or world). Make sure that you have r292078 or
564 later when trying to build 292077 or later before rebuilding.
567 Debug data files are now built by default with 'make buildworld' and
568 installed with 'make installworld'. This facilitates debugging but
569 requires more disk space both during the build and for the installed
570 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
574 r291527 changed the internal interface between the nfsd.ko and
575 nfscommon.ko modules. As such, they must both be upgraded to-gether.
576 __FreeBSD_version has been bumped because of this.
579 Add support for unicode collation strings leads to a change of
580 order of files listed by ls(1) for example. To get back to the old
581 behaviour, set LC_COLLATE environment variable to "C".
583 Databases administrators will need to reindex their databases given
584 collation results will be different.
586 Due to a bug in install(1) it is recommended to remove the ancient
587 locales before running make installworld.
589 rm -rf /usr/share/locale/*
592 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
593 libcrypto.so.7 or libssl.so.7 must be recompiled.
596 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
597 Kernel modules isp_2400_multi and isp_2500_multi were removed and
598 should be replaced with isp_2400 and isp_2500 modules respectively.
601 The build previously allowed using 'make -n' to not recurse into
602 sub-directories while showing what commands would be executed, and
603 'make -n -n' to recursively show commands. Now 'make -n' will recurse
604 and 'make -N' will not.
607 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
608 and etcupdate will now use this file. A custom sendmail.cf is now
609 updated via this mechanism rather than via installworld. If you had
610 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
611 want to remove the exclusion or change it to "always install".
612 /etc/mail/sendmail.cf is now managed the same way regardless of
613 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
614 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
617 Compatibility shims for legacy ATA device names have been removed.
618 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
619 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
620 environment variables, /dev/ad* and /dev/ar* symbolic links.
623 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
624 Please see the 20141231 entry below for information about prerequisites
625 and upgrading, if you are not already using clang 3.5.0 or higher.
628 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
629 and renamed from .symbols to .debug. This reduces the size requirements
630 on the boot partition or file system and provides consistency with
631 userland debug files.
633 When using the supported kernel installation method the
634 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
635 as is done with /boot/kernel.
637 Developers wishing to maintain the historical behavior of installing
638 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
641 The wireless drivers had undergone changes that remove the 'parent
642 interface' from the ifconfig -l output. The rc.d network scripts
643 used to check presence of a parent interface in the list, so old
644 scripts would fail to start wireless networking. Thus, etcupdate(3)
645 or mergemaster(8) run is required after kernel update, to update your
646 rc.d scripts in /etc.
649 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
650 These configurations are now automatically interpreted as
651 'scrub fragment reassemble'.
654 Kernel-loadable modules for the random(4) device are back. To use
655 them, the kernel must have
658 options RANDOM_LOADABLE
660 kldload(8) can then be used to load random_fortuna.ko
661 or random_yarrow.ko. Please note that due to the indirect
662 function calls that the loadable modules need to provide,
663 the build-in variants will be slightly more efficient.
665 The random(4) kernel option RANDOM_DUMMY has been retired due to
666 unpopularity. It was not all that useful anyway.
669 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
670 Control over building the ELF Tool Chain tools is now provided by
671 the WITHOUT_TOOLCHAIN knob.
674 The polarity of Pulse Per Second (PPS) capture events with the
675 uart(4) driver has been corrected. Prior to this change the PPS
676 "assert" event corresponded to the trailing edge of a positive PPS
677 pulse and the "clear" event was the leading edge of the next pulse.
679 As the width of a PPS pulse in a typical GPS receiver is on the
680 order of 1 millisecond, most users will not notice any significant
681 difference with this change.
683 Anyone who has compensated for the historical polarity reversal by
684 configuring a negative offset equal to the pulse width will need to
685 remove that workaround.
688 The default group assigned to /dev/dri entries has been changed
689 from 'wheel' to 'video' with the id of '44'. If you want to have
690 access to the dri devices please add yourself to the video group
693 # pw groupmod video -m $USER
696 The menu.rc and loader.rc files will now be replaced during
697 upgrades. Please migrate local changes to menu.rc.local and
698 loader.rc.local instead.
701 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
702 strings and strip have been removed. The src.conf(5) knob
703 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
706 As ZFS requires more kernel stack pages than is the default on some
707 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
708 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
710 Please consider using 'options KSTACK_PAGES=X' where X is greater
711 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
714 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
715 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
716 default, i.e., they will not contain "::". For example, instead
717 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
718 to have a more specific match, such as different map entries for
719 IPv6:0:0 vs IPv6:0. This change requires that configuration
720 data (including maps, files, classes, custom ruleset, etc.) must
721 use the same format, so make certain such configuration data is
722 upgrading. As a very simple check search for patterns like
723 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
724 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
725 the cf option UseCompressedIPv6Addresses.
728 The default kernel entropy-processing algorithm is now
729 Fortuna, replacing Yarrow.
731 Assuming you have 'device random' in your kernel config
732 file, the configurations allow a kernel option to override
733 this default. You may choose *ONE* of:
735 options RANDOM_YARROW # Legacy /dev/random algorithm.
736 options RANDOM_DUMMY # Blocking-only driver.
738 If you have neither, you get Fortuna. For most people,
739 read no further, Fortuna will give a /dev/random that works
740 like it always used to, and the difference will be irrelevant.
742 If you remove 'device random', you get *NO* kernel-processed
743 entropy at all. This may be acceptable to folks building
744 embedded systems, but has complications. Carry on reading,
745 and it is assumed you know what you need.
747 *PLEASE* read random(4) and random(9) if you are in the
748 habit of tweaking kernel configs, and/or if you are a member
749 of the embedded community, wanting specific and not-usual
750 behaviour from your security subsystems.
752 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
753 random', you will NOT have a functioning /dev/random, and
754 many cryptographic features will not work, including SSH.
755 You may also find strange behaviour from the random(3) set
756 of library functions, in particular sranddev(3), srandomdev(3)
757 and arc4random(3). The reason for this is that the KERN_ARND
758 sysctl only returns entropy if it thinks it has some to
759 share, and with RANDOM_DUMMY or no 'device random' this
763 An additional fix for the issue described in the 20150614 sendmail
764 entry below has been been committed in revision 284717.
767 FreeBSD's old make (fmake) has been removed from the system. It is
768 available as the devel/fmake port or via pkg install fmake.
771 The fix for the issue described in the 20150614 sendmail entry
772 below has been been committed in revision 284436. The work
773 around described in that entry is no longer needed unless the
774 default setting is overridden by a confDH_PARAMETERS configuration
775 setting of '5' or pointing to a 512 bit DH parameter file.
778 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
779 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
780 and devel/kyua to version 0.20+ and adjust any calling code to work
781 with Kyuafile and kyua.
784 The import of openssl to address the FreeBSD-SA-15:10.openssl
785 security advisory includes a change which rejects handshakes
786 with DH parameters below 768 bits. sendmail releases prior
787 to 8.15.2 (not yet released), defaulted to a 512 bit
788 DH parameter setting for client connections. To work around
789 this interoperability, sendmail can be configured to use a
790 2048 bit DH parameter by:
792 1. Edit /etc/mail/`hostname`.mc
793 2. If a setting for confDH_PARAMETERS does not exist or
794 exists and is set to a string beginning with '5',
796 3. If a setting for confDH_PARAMETERS exists and is set to
797 a file path, create a new file with:
798 openssl dhparam -out /path/to/file 2048
799 4. Rebuild the .cf file:
800 cd /etc/mail/; make; make install
802 cd /etc/mail/; make restart
804 A sendmail patch is coming, at which time this file will be
808 Generation of legacy formatted entries have been disabled by default
809 in pwd_mkdb(8), as all base system consumers of the legacy formatted
810 entries were converted to use the new format by default when the new,
811 machine independent format have been added and supported since FreeBSD
814 Please see the pwd_mkdb(8) manual page for further details.
817 Clang and llvm have been upgraded to 3.6.1 release. Please see the
818 20141231 entry below for information about prerequisites and upgrading,
819 if you are not already using 3.5.0 or higher.
822 TI platform code switched to using vendor DTS files and this update
823 may break existing systems running on Beaglebone, Beaglebone Black,
826 - dtb files should be regenerated/reinstalled. Filenames are the
827 same but content is different now
828 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
829 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
830 addressing scheme is now pin 25 on /dev/gpioc3.
831 - Pandaboard: /etc/ttys should be updated, serial console device is
832 now /dev/ttyu2, not /dev/ttyu0
835 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
836 If you need the GNU extension from groff soelim(1), install groff
837 from package: pkg install groff, or via ports: textproc/groff.
840 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
841 defined in symlink(7); previously symlinks were silently ignored.
844 The const qualifier has been removed from iconv(3) to comply with
845 POSIX. The ports tree is aware of this from r384038 onwards.
848 Libraries specified by LIBADD in Makefiles must have a corresponding
849 DPADD_<lib> variable to ensure correct dependencies. This is now
850 enforced in src.libnames.mk.
853 From legacy ata(4) driver was removed support for SATA controllers
854 supported by more functional drivers ahci(4), siis(4) and mvs(4).
855 Kernel modules ataahci and ataadaptec were removed completely,
856 replaced by ahci and mvs modules respectively.
859 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
860 the 20141231 entry below for information about prerequisites and
861 upgrading, if you are not already using 3.5.0 or higher.
864 The 32-bit PowerPC kernel has been changed to a position-independent
865 executable. This can only be booted with a version of loader(8)
866 newer than January 31, 2015, so make sure to update both world and
867 kernel before rebooting.
870 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
871 but before r278950, the RNG was not seeded properly. Immediately
872 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
873 ssh keys or openssl keys) that were generated w/ a kernel from that
874 range. This does not affect programs that directly used /dev/random
875 or /dev/urandom. All userland uses of arc4random(3) are affected.
878 The autofs(4) ABI was changed in order to restore binary compatibility
879 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
883 The powerpc64 kernel has been changed to a position-independent
884 executable. This can only be booted with a new version of loader(8),
885 so make sure to update both world and kernel before rebooting.
888 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
889 only release, no new features have been added. Please see the 20141231
890 entry below for information about prerequisites and upgrading, if you
891 are not already using 3.5.0.
894 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
895 taken from the ELF Tool Chain project rather than GNU binutils. They
896 should be drop-in replacements, with the addition of arm64 support.
897 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
898 binutils tools, if necessary. See 20150805 for updated information.
901 The default Unbound configuration now enables remote control
902 using a local socket. Users who have already enabled the
903 local_unbound service should regenerate their configuration
904 by running "service local_unbound setup" as root.
907 The GNU texinfo and GNU info pages have been removed.
908 To be able to view GNU info pages please install texinfo from ports.
911 Clang, llvm and lldb have been upgraded to 3.5.0 release.
913 As of this release, a prerequisite for building clang, llvm and lldb is
914 a C++11 capable compiler and C++11 standard library. This means that to
915 be able to successfully build the cross-tools stage of buildworld, with
916 clang as the bootstrap compiler, your system compiler or cross compiler
917 should either be clang 3.3 or later, or gcc 4.8 or later, and your
918 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
921 On any standard FreeBSD 10.x or 11.x installation, where clang and
922 libc++ are on by default (that is, on x86 or arm), this should work out
925 On 9.x installations where clang is enabled by default, e.g. on x86 and
926 powerpc, libc++ will not be enabled by default, so libc++ should be
927 built (with clang) and installed first. If both clang and libc++ are
928 missing, build clang first, then use it to build libc++.
930 On 8.x and earlier installations, upgrade to 9.x first, and then follow
931 the instructions for 9.x above.
933 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
934 default, and do not build clang.
936 Many embedded systems are resource constrained, and will not be able to
937 build clang in a reasonable time, or in some cases at all. In those
938 cases, cross building bootable systems on amd64 is a workaround.
940 This new version of clang introduces a number of new warnings, of which
941 the following are most likely to appear:
945 This warns in two cases, for both C and C++:
946 * When the code is trying to take the absolute value of an unsigned
947 quantity, which is effectively a no-op, and almost never what was
948 intended. The code should be fixed, if at all possible. If you are
949 sure that the unsigned quantity can be safely cast to signed, without
950 loss of information or undefined behavior, you can add an explicit
951 cast, or disable the warning.
953 * When the code is trying to take an absolute value, but the called
954 abs() variant is for the wrong type, which can lead to truncation.
955 If you want to disable the warning instead of fixing the code, please
956 make sure that truncation will not occur, or it might lead to unwanted
959 -Wtautological-undefined-compare and
960 -Wundefined-bool-conversion
962 These warn when C++ code is trying to compare 'this' against NULL, while
963 'this' should never be NULL in well-defined C++ code. However, there is
964 some legacy (pre C++11) code out there, which actively abuses this
965 feature, which was less strictly defined in previous C++ versions.
967 Squid and openjdk do this, for example. The warning can be turned off
968 for C++98 and earlier, but compiling the code in C++11 mode might result
969 in unexpected behavior; for example, the parts of the program that are
970 unreachable could be optimized away.
973 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
974 kernel sources have been removed. The .h files remain, since some
975 utilities include them. This will need to be fixed later.
976 If "mount -t oldnfs ..." is attempted, it will fail.
977 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
978 the utilities will report errors.
981 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
982 directories to top level SUBDIR variable when their parent
983 directory is included in LOCAL_DIRS. Users with build systems with
984 such hierarchies and without SUBDIR entries in the parent
985 directory Makefiles should add them or add the directories to
989 faith(4) and faithd(8) have been removed from the base system. Faith
990 has been obsolete for a very long time.
993 vt(4), the new console driver, is enabled by default. It brings
994 support for Unicode and double-width characters, as well as
995 support for UEFI and integration with the KMS kernel video
998 You may need to update your console settings in /etc/rc.conf,
999 most probably the keymap. During boot, /etc/rc.d/syscons will
1000 indicate what you need to do.
1002 vt(4) still has issues and lacks some features compared to
1003 syscons(4). See the wiki for up-to-date information:
1004 https://wiki.freebsd.org/Newcons
1006 If you want to keep using syscons(4), you can do so by adding
1007 the following line to /boot/loader.conf:
1011 pjdfstest has been integrated into kyua as an opt-in test suite.
1012 Please see share/doc/pjdfstest/README for more details on how to
1016 gperf has been removed from the base system for architectures
1017 that use clang. Ports that require gperf will obtain it from the
1021 pjdfstest has been moved from tools/regression/pjdfstest to
1025 At svn r271982, The default linux compat kernel ABI has been adjusted
1026 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1027 update. If you wish to continue using the linux-f10 compat ports,
1028 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1029 encouraged to update their linux-compat packages to linux-c6 during
1030 their next update cycle.
1033 The ofwfb driver, used to provide a graphics console on PowerPC when
1034 using vt(4), no longer allows mmap() of all physical memory. This
1035 will prevent Xorg on PowerPC with some ATI graphics cards from
1036 initializing properly unless x11-servers/xorg-server is updated to
1040 The xdev targets have been converted to using TARGET and
1041 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1044 The default unbound configuration has been modified to address
1045 issues with reverse lookups on networks that use private
1046 address ranges. If you use the local_unbound service, run
1047 "service local_unbound setup" as root to regenerate your
1048 configuration, then "service local_unbound reload" to load the
1052 The GNU texinfo and GNU info pages are not built and installed
1053 anymore, WITH_INFO knob has been added to allow to built and install
1055 UPDATE: see 20150102 entry on texinfo's removal
1058 The GNU readline library is now an INTERNALLIB - that is, it is
1059 statically linked into consumers (GDB and variants) in the base
1060 system, and the shared library is no longer installed. The
1061 devel/readline port is available for third party software that
1065 The Itanium architecture (ia64) has been removed from the list of
1066 known architectures. This is the first step in the removal of the
1070 Commit r268115 has added NFSv4.1 server support, merged from
1071 projects/nfsv4.1-server. Since this includes changes to the
1072 internal interfaces between the NFS related modules, a full
1073 build of the kernel and modules will be necessary.
1074 __FreeBSD_version has been bumped.
1077 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1078 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1079 which differs from the behaviour controlled by this knob.)
1082 Maximal length of the serial number in CTL was increased from 16 to
1083 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1084 and ctld, need to be rebuilt to work with a new kernel.
1087 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1088 1 respectively to match the upstream numbers. They were out of
1089 sync because, when they were originally added to FreeBSD, the
1090 upstream versions were not respected. These libraries are private
1091 and not yet built by default, so renumbering them should be a
1092 non-issue. However, unclean source trees will yield broken test
1093 programs once the operator executes "make delete-old-libs" after a
1094 "make installworld".
1096 Additionally, the atf-sh binary was made private by moving it into
1097 /usr/libexec/. Already-built shell test programs will keep the
1098 path to the old binary so they will break after "make delete-old"
1101 If you are using WITH_TESTS=yes (not the default), wipe the object
1102 tree and rebuild from scratch to prevent spurious test failures.
1103 This is only needed once: the misnumbered libraries and misplaced
1104 binaries have been added to OptionalObsoleteFiles.inc so they will
1105 be removed during a clean upgrade.
1108 Clang and llvm have been upgraded to 3.4.1 release.
1111 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1112 be removed to avoid issues in the future (and has been added to
1116 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1117 past, it affected all builds that used the bsd.*.mk files. The old
1118 behavior was a bug, but people may have relied upon it. To get this
1119 behavior back, you can .include /etc/src.conf from /etc/make.conf
1120 (which is still global and isn't changed). This also changes the
1121 behavior of incremental builds inside the tree of individual
1122 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1123 Although this has survived make universe and some upgrade scenarios,
1124 other upgrade scenarios may have broken. At least one form of
1125 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1126 as well... In cases where MAKESYSPATH isn't working with this
1127 setting, you'll need to set it to the full path to your tree.
1129 One side effect of all this cleaning up is that bsd.compiler.mk
1130 is no longer implicitly included by bsd.own.mk. If you wish to
1131 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1135 The lindev device has been removed since /dev/full has been made a
1136 standard device. __FreeBSD_version has been bumped.
1139 The knob WITHOUT_VI was added to the base system, which controls
1140 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1141 in order to reorder files share/termcap and didn't build ex(1) as a
1142 build tool, so building/installing with WITH_VI is highly advised for
1143 build hosts for older releases.
1145 This issue has been fixed in stable/9 and stable/10 in r277022 and
1146 r276991, respectively.
1149 The YES_HESIOD knob has been removed. It has been obsolete for
1150 a decade. Please move to using WITH_HESIOD instead or your builds
1151 will silently lack HESIOD.
1154 The uart(4) driver has been changed with respect to its handling
1155 of the low-level console. Previously the uart(4) driver prevented
1156 any process from changing the baudrate or the CLOCAL and HUPCL
1157 control flags. By removing the restrictions, operators can make
1158 changes to the serial console port without having to reboot.
1159 However, when getty(8) is started on the serial device that is
1160 associated with the low-level console, a misconfigured terminal
1161 line in /etc/ttys will now have a real impact.
1162 Before upgrading the kernel, make sure that /etc/ttys has the
1163 serial console device configured as 3wire without baudrate to
1164 preserve the previous behaviour. E.g:
1165 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1168 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1169 to improve performance. To re-enable it, if needed, run rpcbind
1170 with command line option -W.
1173 Switched back to the GPL dtc compiler due to updates in the upstream
1174 dts files not being supported by the BSDL dtc compiler. You will need
1175 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1176 may result while building dtb files during a kernel build if you fail
1177 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1180 Clang and llvm have been upgraded to 3.4 release.
1183 The nve(4) driver has been removed. Please use the nfe(4) driver
1184 for NVIDIA nForce MCP Ethernet adapters instead.
1187 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1188 This could cause certain C++ applications using shared libraries built
1189 against the previous version of libc++ to crash. The incompatibility
1190 has now been fixed, but any C++ applications or shared libraries built
1191 between r261283 and r261801 should be recompiled.
1194 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1195 capability mode support. Please note that enabling the feature in
1196 kernel is still highly recommended.
1199 OpenSSH is now built with sandbox support, and will use sandbox as
1200 the default privilege separation method. This requires Capsicum
1201 capability mode support in kernel.
1204 The libelf and libdwarf libraries have been updated to newer
1205 versions from upstream. Shared library version numbers for
1206 these two libraries were bumped. Any ports or binaries
1207 requiring these two libraries should be recompiled.
1208 __FreeBSD_version is bumped to 1100006.
1211 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1212 instead of providing an explicit one, this would prevent such
1213 Makefile from providing its own Kyuafile in the future during
1214 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1215 intervention is needed to clean an objdir if you use NO_CLEAN:
1216 # find /usr/obj -name Kyuafile | xargs rm -f
1219 The behavior of gss_pseudo_random() for the krb5 mechanism
1220 has changed, for applications requesting a longer random string
1221 than produced by the underlying enctype's pseudo-random() function.
1222 In particular, the random string produced from a session key of
1223 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1224 be different at the 17th octet and later, after this change.
1225 The counter used in the PRF+ construction is now encoded as a
1226 big-endian integer in accordance with RFC 4402.
1227 __FreeBSD_version is bumped to 1100004.
1230 The WITHOUT_ATF build knob has been removed and its functionality
1231 has been subsumed into the more generic WITHOUT_TESTS. If you were
1232 using the former to disable the build of the ATF libraries, you
1233 should change your settings to use the latter.
1236 The default version of mtree is nmtree which is obtained from
1237 NetBSD. The output is generally the same, but may vary
1238 slightly. If you found you need identical output adding
1239 "-F freebsd9" to the command line should do the trick. For the
1240 time being, the old mtree is available as fmtree.
1243 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1244 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1245 1.1.4_8 and verify bsdyml not linked in, before running "make
1247 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1249 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1252 The stable/10 branch has been created in subversion from head
1256 The rc.d/jail script has been updated to support jail(8)
1257 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1258 for per-jail configuration are automatically converted to
1259 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1260 This is transparently backward compatible. See below about some
1261 incompatibilities and rc.conf(5) manual page for more details.
1263 These variables are now deprecated in favor of jail(8) configuration
1264 file. One can use "rc.d/jail config <jname>" command to generate
1265 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1266 running the jail(8) utility. The default pathname of the
1267 configuration file is /etc/jail.conf and can be specified by
1268 using $jail_conf or $jail_<jname>_conf variables.
1270 Please note that jail_devfs_ruleset accepts an integer at
1271 this moment. Please consider to rewrite the ruleset name
1275 BIND has been removed from the base system. If all you need
1276 is a local resolver, simply enable and start the local_unbound
1277 service instead. Otherwise, several versions of BIND are
1278 available in the ports tree. The dns/bind99 port is one example.
1280 With this change, nslookup(1) and dig(1) are no longer in the base
1281 system. Users should instead use host(1) and drill(1) which are
1282 in the base system. Alternatively, nslookup and dig can
1283 be obtained by installing the dns/bind-tools port.
1286 With the addition of unbound(8), a new unbound user is now
1287 required during installworld. "mergemaster -p" can be used to
1288 add the user prior to installworld, as documented in the handbook.
1291 OpenSSH is now built with DNSSEC support, and will by default
1292 silently trust signed SSHFP records. This can be controlled with
1293 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1294 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1297 The GNU Compiler Collection and C++ standard library (libstdc++)
1298 are no longer built by default on platforms where clang is the system
1299 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1300 options in src.conf.
1303 The PROCDESC kernel option is now part of the GENERIC kernel
1304 configuration and is required for the rwhod(8) to work.
1305 If you are using custom kernel configuration, you should include
1309 The API and ABI related to the Capsicum framework was modified
1310 in backward incompatible way. The userland libraries and programs
1311 have to be recompiled to work with the new kernel. This includes the
1312 following libraries and programs, but the whole buildworld is
1313 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1314 kdump, procstat, rwho, rwhod, uniq.
1317 AES-NI intrinsic support has been added to gcc. The AES-NI module
1318 has been updated to use this support. A new gcc is required to build
1319 the aesni module on both i386 and amd64.
1322 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1323 Thus "device padlock_rng" and "device rdrand_rng" should be
1324 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1327 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1328 enables just the iconv* functionality and is now on by default.
1329 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1330 compatibility. Set WITHOUT_ICONV to build the old way.
1331 If you have been using WITH_ICONV before, you will very likely
1332 need to turn on WITH_LIBICONV_COMPAT.
1335 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1336 Illumos origin, including ZFS. If you have INVARIANTS in your
1337 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1339 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1340 locks if WITNESS option was set. Because that generated a lot of
1341 witness(9) reports and all of them were believed to be false
1342 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1343 can be used to achieve the previous behavior.
1346 Timer values in IPv6 data structures now use time_uptime instead
1347 of time_second. Although this is not a user-visible functional
1348 change, userland utilities which directly use them---ndp(8),
1349 rtadvd(8), and rtsold(8) in the base system---need to be updated
1350 to r253970 or later.
1353 find -delete can now delete the pathnames given as arguments,
1354 instead of only files found below them or if the pathname did
1355 not contain any slashes. Formerly, the following error message
1358 find: -delete: <path>: relative path potentially not safe
1360 Deleting the pathnames given as arguments can be prevented
1361 without error messages using -mindepth 1 or by changing
1362 directory and passing "." as argument to find. This works in the
1363 old as well as the new version of find.
1366 Behavior of devfs rules path matching has been changed.
1367 Pattern is now always matched against fully qualified devfs
1368 path and slash characters must be explicitly matched by
1369 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1370 subdirectories must be reviewed.
1373 The default ARM ABI has changed to the ARM EABI. The old ABI is
1374 incompatible with the ARM EABI and all programs and modules will
1375 need to be rebuilt to work with a new kernel.
1377 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1379 NOTE: Support for the old ABI will be removed in the future and
1380 users are advised to upgrade.
1383 pkg_install has been disconnected from the build if you really need it
1384 you should add WITH_PKGTOOLS in your src.conf(5).
1387 Most of network statistics structures were changed to be able
1388 keep 64-bits counters. Thus all tools, that work with networking
1389 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1392 Fix a bug that allowed a tracing process (e.g. gdb) to write
1393 to a memory-mapped file in the traced process's address space
1394 even if neither the traced process nor the tracing process had
1395 write access to that file.
1398 CVS has been removed from the base system. An exact copy
1399 of the code is available from the devel/cvs port.
1402 Some people report the following error after the switch to bmake:
1404 make: illegal option -- J
1405 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1407 *** [buildworld] Error code 2
1409 this likely due to an old instance of make in
1410 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1411 which src/Makefile will use that blindly, if it exists, so if
1412 you see the above error:
1414 rm -rf `make -V MAKEPATH`
1419 Use bmake by default.
1420 Whereas before one could choose to build with bmake via
1421 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1422 make. The goal is to remove these knobs for 10-RELEASE.
1424 It is worth noting that bmake (like gmake) treats the command
1425 line as the unit of failure, rather than statements within the
1426 command line. Thus '(cd some/where && dosomething)' is safer
1427 than 'cd some/where; dosomething'. The '()' allows consistent
1428 behavior in parallel build.
1431 Fix a bug that allows NFS clients to issue READDIR on files.
1434 The WITHOUT_IDEA option has been removed because
1435 the IDEA patent expired.
1438 The sysctl which controls TRIM support under ZFS has been renamed
1439 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1443 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1444 rather than creating it's own in the temporary directory in
1445 order allow access to bootstrapped versions of tools such as
1446 install and mtree. When upgrading from version of FreeBSD where
1447 the install command does not support -l, you will need to
1448 install a new mergemaster command if mergemaster -p is required.
1449 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1453 Legacy ATA stack, disabled and replaced by new CAM-based one since
1454 FreeBSD 9.0, completely removed from the sources. Kernel modules
1455 atadisk and atapi*, user-level tools atacontrol and burncd are
1456 removed. Kernel option `options ATA_CAM` is now permanently enabled
1460 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1461 and socketpair(2). Software, in particular Kerberos, may
1462 automatically detect and use these during building. The resulting
1463 binaries will not work on older kernels.
1466 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1467 information, see the respective 20130304 entry).
1470 Recent commits to callout(9) changed the size of struct callout,
1471 so the KBI is probably heavily disturbed. Also, some functions
1472 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1473 by macros. Every kernel module using it won't load, so rebuild
1476 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1477 but does not initialize by default (because of the new CTL_DISABLE
1478 option) to save memory. To re-enable it, remove the CTL_DISABLE
1479 option from the kernel config file or set kern.cam.ctl.disable=0
1480 in /boot/loader.conf.
1483 The ctl device has been disabled in GENERIC for i386 and amd64.
1484 This was done due to the extra memory being allocated at system
1485 initialisation time by the ctl driver which was only used if
1486 a CAM target device was created. This makes a FreeBSD system
1487 unusable on 128MB or less of RAM.
1490 A new compression method (lz4) has been merged to -HEAD. Please
1491 refer to zpool-features(7) for more information.
1493 Please refer to the "ZFS notes" section of this file for information
1494 on upgrading boot ZFS pools.
1497 A BSD-licensed patch(1) variant has been added and is installed
1498 as bsdpatch, being the GNU version the default patch.
1499 To inverse the logic and use the BSD-licensed one as default,
1500 while having the GNU version installed as gnupatch, rebuild
1501 and install world with the WITH_BSD_PATCH knob set.
1504 Due to the use of the new -l option to install(1) during build
1505 and install, you must take care not to directly set the INSTALL
1506 make variable in your /etc/make.conf, /etc/src.conf, or on the
1507 command line. If you wish to use the -C flag for all installs
1508 you may be able to add INSTALL+=-C to /etc/make.conf or
1512 The install(1) option -M has changed meaning and now takes an
1513 argument that is a file or path to append logs to. In the
1514 unlikely event that -M was the last option on the command line
1515 and the command line contained at least two files and a target
1516 directory the first file will have logs appended to it. The -M
1517 option served little practical purpose in the last decade so its
1518 use is expected to be extremely rare.
1521 After switching to Clang as the default compiler some users of ZFS
1522 on i386 systems started to experience stack overflow kernel panics.
1523 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1526 GEOM_LABEL now mangles label names read from file system metadata.
1527 Mangling affect labels containing spaces, non-printable characters,
1528 '%' or '"'. Device names in /etc/fstab and other places may need to
1532 By default, only the 10 most recent kernel dumps will be saved. To
1533 restore the previous behaviour (no limit on the number of kernel dumps
1534 stored in the dump directory) add the following line to /etc/rc.conf:
1539 With the addition of auditdistd(8), a new auditdistd user is now
1540 required during installworld. "mergemaster -p" can be used to
1541 add the user prior to installworld, as documented in the handbook.
1544 The sin6_scope_id member variable in struct sockaddr_in6 is now
1545 filled by the kernel before passing the structure to the userland via
1546 sysctl or routing socket. This means the KAME-specific embedded scope
1547 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1548 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1549 __FreeBSD_version is bumped to 1000025.
1552 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1553 This means that the world and kernel will be compiled with clang
1554 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1555 and /usr/bin/cpp. To disable this behavior and revert to building
1556 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1557 of current may need to bootstrap WITHOUT_CLANG first if the clang
1558 build fails (its compatibility window doesn't extend to the 9 stable
1562 The IPFIREWALL_FORWARD kernel option has been removed. Its
1563 functionality now turned on by default.
1566 The ZERO_COPY_SOCKET kernel option has been removed and
1567 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1568 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1569 mechanism which is not safe and may result in kernel crashes.
1570 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1571 driver supports disposeable external page sized mbuf storage.
1572 Proper replacements for both zero-copy mechanisms are under
1573 consideration and will eventually lead to complete removal
1574 of the two kernel options.
1577 The IPv4 network stack has been converted to network byte
1578 order. The following modules need to be recompiled together
1579 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1580 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1583 Support for non-MPSAFE filesystems was removed from VFS. The
1584 VFS_VERSION was bumped, all filesystem modules shall be
1588 All the non-MPSAFE filesystems have been disconnected from
1589 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1590 portalfs, smbfs, xfs.
1593 The interface cloning API and ABI has changed. The following
1594 modules need to be recompiled together with kernel:
1595 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1596 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1597 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1600 The sdhci driver was split in two parts: sdhci (generic SD Host
1601 Controller logic) and sdhci_pci (actual hardware driver).
1602 No kernel config modifications are required, but if you
1603 load sdhc as a module you must switch to sdhci_pci instead.
1606 Import the FUSE kernel and userland support into base system.
1609 The GNU sort(1) program has been removed since the BSD-licensed
1610 sort(1) has been the default for quite some time and no serious
1611 problems have been reported. The corresponding WITH_GNU_SORT
1615 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1616 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1620 The net80211(4) ABI has been changed to allow for improved driver
1621 PS-POLL and power-save support. All wireless drivers need to be
1622 recompiled to work with the new kernel.
1625 The random(4) support for the VIA hardware random number
1626 generator (`PADLOCK') is no longer enabled unconditionally.
1627 Add the padlock_rng device in the custom kernel config if
1628 needed. The GENERIC kernels on i386 and amd64 do include the
1629 device, so the change only affects the custom kernel
1633 The pf(4) packet filter ABI has been changed. pfctl(8) and
1634 snmp_pf module need to be recompiled to work with new kernel.
1637 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1638 to -HEAD. Pools that have empty_bpobj in active state can not be
1639 imported read-write with ZFS implementations that do not support
1640 this feature. For more information read the zpool-features(5)
1644 The sparc64 ZFS loader has been changed to no longer try to auto-
1645 detect ZFS providers based on diskN aliases but now requires these
1646 to be explicitly listed in the OFW boot-device environment variable.
1649 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1650 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1651 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1654 The following sysctls and tunables have been renamed for consistency
1655 with other variables:
1656 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1657 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1660 The sort utility has been replaced with BSD sort. For now, GNU sort
1661 is also available as "gnusort" or the default can be set back to
1662 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1663 installed as "bsdsort".
1666 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1667 Starting with this version the old system of ZFS pool versioning
1668 is superseded by "feature flags". This concept enables forward
1669 compatibility against certain future changes in functionality of ZFS
1670 pools. The first read-only compatible "feature flag" for ZFS pools
1671 is named "com.delphix:async_destroy". For more information
1672 read the new zpool-features(5) manual page.
1673 Please refer to the "ZFS notes" section of this file for information
1674 on upgrading boot ZFS pools.
1677 The malloc(3) implementation embedded in libc now uses sources imported
1678 as contrib/jemalloc. The most disruptive API change is to
1679 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1680 delete it prior to installworld, and optionally re-create it using the
1681 new format after rebooting. See malloc.conf(5) for details
1682 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1686 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1687 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1688 now spelled mips. This is to aid compatibility with third-party
1689 software that expects this naming scheme in uname(3). Little-endian
1690 settings are unchanged. If you are updating a big-endian mips64 machine
1691 from before this change, you may need to set MACHINE_ARCH=mips64 in
1692 your environment before the new build system will recognize your machine.
1695 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1699 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1700 nullfs(5) did not pass through all behaviours to the underlying layer,
1701 as a result if we bound to a socket on the lower layer we could connect
1702 only to the lower path; if we bound to the upper layer we could connect
1703 only to the upper path. The new behavior is one can connect to both the
1704 lower and the upper paths regardless what layer path one binds to.
1707 The getifaddrs upgrade path broken with 20111215 has been restored.
1708 If you have upgraded in between 20111215 and 20120209 you need to
1709 recompile libc again with your kernel. You still need to recompile
1710 world to be able to configure CARP but this restriction already
1711 comes from 20111215.
1714 The set_rcvar() function has been removed from /etc/rc.subr. All
1715 base and ports rc.d scripts have been updated, so if you have a
1716 port installed with a script in /usr/local/etc/rc.d you can either
1717 hand-edit the rcvar= line, or reinstall the port.
1719 An easy way to handle the mass-update of /etc/rc.d:
1720 rm /etc/rc.d/* && mergemaster -i
1723 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1724 on the current CPU and prevents other threads from running.
1725 This behavior can be reverted using the kern.stop_scheduler_on_panic
1727 The new behavior can be incompatible with kern.sync_on_panic.
1730 The carp(4) facility has been changed significantly. Configuration
1731 of the CARP protocol via ifconfig(8) has changed, as well as format
1732 of CARP events submitted to devd(8) has changed. See manual pages
1733 for more information. The arpbalance feature of carp(4) is currently
1734 not supported anymore.
1736 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1737 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1738 need to be recompiled.
1741 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1745 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1746 explicitely support non-MPSAFE filesystems.
1747 It is on by default for all supported platform at this present
1751 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1752 i386 and pc98 GENERIC kernel configuration files.
1755 sysinstall has been removed
1758 The stable/9 branch created in subversion. This corresponds to the
1759 RELENG_9 branch in CVS.
1765 Avoid using make -j when upgrading. While generally safe, there are
1766 sometimes problems using -j to upgrade. If your upgrade fails with
1767 -j, please try again without -j. From time to time in the past there
1768 have been problems using -j with buildworld and/or installworld. This
1769 is especially true when upgrading between "distant" versions (eg one
1770 that cross a major release boundary or several minor releases, or when
1771 several months have passed on the -current branch).
1773 Sometimes, obscure build problems are the result of environment
1774 poisoning. This can happen because the make utility reads its
1775 environment when searching for values for global variables. To run
1776 your build attempts in an "environmental clean room", prefix all make
1777 commands with 'env -i '. See the env(1) manual page for more details.
1779 When upgrading from one major version to another it is generally best to
1780 upgrade to the latest code in the currently installed branch first, then
1781 do an upgrade to the new branch. This is the best-tested upgrade path,
1782 and has the highest probability of being successful. Please try this
1783 approach if you encounter problems with a major version upgrade. Since
1784 the stable 4.x branch point, one has generally been able to upgade from
1785 anywhere in the most recent stable branch to head / current (or even the
1786 last couple of stable branches). See the top of this file when there's
1789 When upgrading a live system, having a root shell around before
1790 installing anything can help undo problems. Not having a root shell
1791 around can lead to problems if pam has changed too much from your
1792 starting point to allow continued authentication after the upgrade.
1794 This file should be read as a log of events. When a later event changes
1795 information of a prior event, the prior event should not be deleted.
1796 Instead, a pointer to the entry with the new information should be
1797 placed in the old entry. Readers of this file should also sanity check
1798 older entries before relying on them blindly. Authors of new entries
1799 should write them with this in mind.
1803 When upgrading the boot ZFS pool to a new version, always follow
1806 1.) recompile and reinstall the ZFS boot loader and boot block
1807 (this is part of "make buildworld" and "make installworld")
1809 2.) update the ZFS boot block on your boot drive
1811 The following example updates the ZFS boot block on the first
1812 partition (freebsd-boot) of a GPT partitioned drive ada0:
1813 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1815 Non-boot pools do not need these updates.
1819 If you are updating from a prior version of FreeBSD (even one just
1820 a few days old), you should follow this procedure. It is the most
1821 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1823 make kernel-toolchain
1824 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1825 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1827 To test a kernel once
1828 ---------------------
1829 If you just want to boot a kernel once (because you are not sure
1830 if it works, or if you want to boot a known bad kernel to provide
1831 debugging information) run
1832 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1833 nextboot -k testkernel
1835 To just build a kernel when you know that it won't mess you up
1836 --------------------------------------------------------------
1837 This assumes you are already running a CURRENT system. Replace
1838 ${arch} with the architecture of your machine (e.g. "i386",
1839 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1841 cd src/sys/${arch}/conf
1842 config KERNEL_NAME_HERE
1843 cd ../compile/KERNEL_NAME_HERE
1848 If this fails, go to the "To build a kernel" section.
1850 To rebuild everything and install it on the current system.
1851 -----------------------------------------------------------
1852 # Note: sometimes if you are running current you gotta do more than
1853 # is listed here if you are upgrading from a really old current.
1855 <make sure you have good level 0 dumps>
1857 make kernel KERNCONF=YOUR_KERNEL_HERE
1859 <reboot in single user> [3]
1866 To cross-install current onto a separate partition
1867 --------------------------------------------------
1868 # In this approach we use a separate partition to hold
1869 # current's root, 'usr', and 'var' directories. A partition
1870 # holding "/", "/usr" and "/var" should be about 2GB in
1873 <make sure you have good level 0 dumps>
1876 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1877 <maybe newfs current's root partition>
1878 <mount current's root partition on directory ${CURRENT_ROOT}>
1879 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1880 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1881 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1882 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1883 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1884 <reboot into current>
1885 <do a "native" rebuild/install as described in the previous section>
1886 <maybe install compatibility libraries from ports/misc/compat*>
1890 To upgrade in-place from stable to current
1891 ----------------------------------------------
1892 <make sure you have good level 0 dumps>
1894 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1896 <reboot in single user> [3]
1903 Make sure that you've read the UPDATING file to understand the
1904 tweaks to various things you need. At this point in the life
1905 cycle of current, things change often and you are on your own
1906 to cope. The defaults can also change, so please read ALL of
1907 the UPDATING entries.
1909 Also, if you are tracking -current, you must be subscribed to
1910 freebsd-current@freebsd.org. Make sure that before you update
1911 your sources that you have read and understood all the recent
1912 messages there. If in doubt, please track -stable which has
1913 much fewer pitfalls.
1915 [1] If you have third party modules, such as vmware, you
1916 should disable them at this point so they don't crash your
1919 [3] From the bootblocks, boot -s, and then do
1924 adjkerntz -i # if CMOS is wall time
1925 Also, when doing a major release upgrade, it is required that
1926 you boot into single user mode to do the installworld.
1928 [4] Note: This step is non-optional. Failure to do this step
1929 can result in a significant reduction in the functionality of the
1930 system. Attempting to do it by hand is not recommended and those
1931 that pursue this avenue should read this file carefully, as well
1932 as the archives of freebsd-current and freebsd-hackers mailing lists
1933 for potential gotchas. The -U option is also useful to consider.
1934 See mergemaster(8) for more information.
1936 [5] Usually this step is a noop. However, from time to time
1937 you may need to do this if you get unknown user in the following
1938 step. It never hurts to do it all the time. You may need to
1939 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1940 install) after the buildworld before this step if you last updated
1941 from current before 20130425 or from -stable before 20130430.
1943 [6] This only deletes old files and directories. Old libraries
1944 can be deleted by "make delete-old-libs", but you have to make
1945 sure that no program is using those libraries anymore.
1947 [8] In order to have a kernel that can run the 4.x binaries needed to
1948 do an installworld, you must include the COMPAT_FREEBSD4 option in
1949 your kernel. Failure to do so may leave you with a system that is
1950 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1951 required to run the 5.x binaries on more recent kernels. And so on
1952 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1954 Make sure that you merge any new devices from GENERIC since the
1955 last time you updated your kernel config file.
1957 [9] When checking out sources, you must include the -P flag to have
1958 cvs prune empty directories.
1960 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1961 "?=" instead of the "=" assignment operator, so that buildworld can
1962 override the CPUTYPE if it needs to.
1964 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1965 not on the command line, or in /etc/make.conf. buildworld will
1966 warn if it is improperly defined.
1969 This file contains a list, in reverse chronological order, of major
1970 breakages in tracking -current. It is not guaranteed to be a complete
1971 list of such breakages, and only contains entries since September 23, 2011.
1972 If you need to see UPDATING entries from before that date, you will need
1973 to fetch an UPDATING file from an older FreeBSD release.
1975 Copyright information:
1977 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1979 Redistribution, publication, translation and use, with or without
1980 modification, in full or in part, in any form or format of this
1981 document are permitted without further permission from the author.
1983 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1984 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1985 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1986 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1987 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1988 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1989 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1990 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1991 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1992 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1993 POSSIBILITY OF SUCH DAMAGE.
1995 Contact Warner Losh if you have any questions about your use of