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/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 20200609 p10 FreeBSD-SA-20:17.usb
21 Fix USB HID descriptor parsing error. [SA-20:17.usb]
23 20200512 p9 FreeBSD-EN-20:08.tzdata
24 FreeBSD-EN-20:10.build
25 FreeBSD-SA-20:12.libalias
26 FreeBSD-SA-20:13.libalias
28 FreeBSD-SA-20:15.cryptodev
30 Import tzdata 2020a. [EN-20:08.tzdata]
32 Fix incorrect build host Clang version detection [EN-20:10.build]
34 Fix insufficient packet length validation in libalias [SA-20:12.libalias]
36 Fix memory disclosure vulnerability in libalias [SA-20:13.libalias]
38 Fix improper checking in SCTP-AUTH shared key update [SA-20:14.sctp]
40 Fix use after free in cryptodev module [SA-20:15.cryptodev]
42 20200421 p8 FreeBSD-EN-20:07.quotad
45 Fix regression in rpc.rquotad with certain NFS servers [EN-20:07.quotad]
47 Fix ipfw invalid mbuf handling [SA-20:10.ipfw]
49 20200319 p7 FreeBSD-EN-20:04.pfctl
52 FreeBSD-SA-20:05.if_oce_ioctl
53 FreeBSD-SA-20:07.epair
57 Fix missing pfctl(8) tunable [EN-20:04.pfctl]
59 Fix incorrect checksum calculations with IPv6 extension headers [EN-20:06.ipv6]
61 Fix TCP IPv6 SYN cache kernel information disclosure [SA-20:04.tcp]
63 Fix insufficient oce(4) ioctl(2) privilege checking [SA-20:05.if_oce_ioctl]
65 Fix incorrect user-controlled pointer use in epair [SA-20:07.epair]
67 Fix kernel memory disclosure with nested jails [SA-20:08.jail]
69 Fix multiple denial of service in ntpd [SA-20:09.ntp]
71 20200128 p6 FreeBSD-EN-20:01.ssp
72 FreeBSD-EN-20:02.nmount
73 FreeBSD-SA-20:01.libfetch
74 FreeBSD-SA-20:03.thrmisc
76 Fix imprecise ordering of SSP canary initialization [EN-20:01.ssp]
78 Fix nmount invalid pointer dereference [EN-20:02.nmount]
80 Fix libfetch buffer overflow [SA-20:01.libfetch]
82 Fix kernel stack data disclosure [SA-20:03.thrmisc]
84 20191112 p5 FreeBSD-SA-19:25.mcepsc
86 Fix Machine Check Exception on Page Size Change [SA-19:25.mcepsc]
88 20191023 p4 FreeBSD-EN-19:18.tzdata
90 Import tzdata 2019c. [EN-19:18.tzdata]
92 20190820 p3 FreeBSD-EN-19:16.bhyve
96 FreeBSD-SA-19:24.mqueuefs
98 Bhyve instruction emulation improvements (opcode 03H and F7H).
101 Fix ipfw(8) jail keyword prior to jail startup. [EN-19:17.ipfw]
103 Fix IPv6 remote denial of service. [SA-19:22.mbuf]
105 Fix kernel memory disclosure from /dev/midistat. [SA-19:23.midi]
107 Fix reference count overflow in mqueuefs. [SA-19:24.mqueuefs]
109 20190806 p2 FreeBSD-SA-19:18.bzip2
110 FreeBSD-SA-19:19.mldv2
111 FreeBSD-SA-19:20.bsnmp
112 FreeBSD-SA-19:21.bhyve
114 Fix multiple vulnerabilities in bzip2. [SA-19:18.bzip2]
116 Fix ICMPv6 / MLDv2 out-of-bounds memory access. [SA-19:19.mldv2]
118 Fix insufficient message length validation in bsnmp library.
121 Fix insufficient validation of guest-supplied data (e1000 device).
124 20190724 p1 FreeBSD-EN-19:13.mds
125 FreeBSD-SA-19:12.telnet
127 FreeBSD-SA-19:14.freebsd32
128 FreeBSD-SA-19:15.mqueuefs
129 FreeBSD-SA-19:16.bhyve
132 Fix panic from Intel CPU vulnerability mitigation. [EN-19:13.mds]
134 Fix multiple telnet client vulnerabilities. [SA-19:12.telnet]
136 Fix pts write-after-free. [SA-19:13.pts]
138 Fix kernel memory disclosure in freebsd32_ioctl. [SA-19:14.freebsd32]
140 Fix reference count overflow in mqueuefs. [SA-19:15.mqueuefs]
142 Fix byhve out-of-bounds read in XHCI device. [SA-19:16.bhyve]
144 Fix file descriptor reference count leak. [SA-19:17.fd]
149 20190702 FreeBSD-EN-19:12.tzdata
150 FreeBSD-SA-19:09.iconv
151 FreeBSD-SA-19:11.cd_ioctl
153 Import tzdata 2019b. [EN-19:12.tzdata]
155 Fix iconv buffer overflow. [SA-19:09.iconv]
157 Fix privilege escalation in cd(4) driver. [SA-19:11.cd_ioctl]
160 CARP now sets DSCP value CS7(Network Traffic) in the flowlabel field
161 of packets by default instead of only setting TOS_LOWDELAY in IPv4,
162 which was deprecated in 1998. Original behavior can be restored by
163 setting sysctl net.inet.carp.dscp=4.
166 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
167 8.0.0. Please see the 20141231 entry below for information about
168 prerequisites and upgrading, if you are not already using clang 3.5.0
172 geom_uzip(4) depends on the new module xz. If geom_uzip is statically
173 compiled into your custom kernel, add 'device xz' statement to the
177 Co-existance for Forth and Lua interpreters in bootloaders has now been
178 merged to ease testing of lualoader. LOADER_DEFAULT_INTERP, documented
179 in build(7), may be used to control which interpreter flavor is used in
180 the default loader to be installed. For systems where Lua and Forth
181 coexist, this switch can also be made on a running system by creating a
182 link from /boot/loader{,.efi} to /boot/loader_${flavor}{,.efi} rather
183 than requiring a rebuild.
185 The default flavor in this branch will remain Forth. As indicated in
186 the 20190216 UPDATING entry, booting is a complex environment; it would
187 be prudent to assume that lualoader may not work for your setup and make
188 provisions for backup boot methods.
191 zfsloader's functionality has now been folded into loader.
192 zfsloader is no longer necesasary once you've updated your
193 boot blocks. For a transition period, we will install a
194 hardlink for zfsloader to loader to allow a smooth transition
195 until the boot blocks can be updated (hard link because old
196 zfs boot blocks don't understand symlinks).
199 Lualoader has been merged to facilitate testing on this branch. It's
200 purely opt-in for now by building WITH_LOADER_LUA and WITHOUT_FORTH in
201 /etc/src.conf, but co-existance will come shortly. Booting is a complex
202 environment and test coverage for Lua-enabled loaders has been thin, so
203 it would be prudent to assume it might not work and make provisions for
207 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
208 7.0.1. Please see the 20141231 entry below for information about
209 prerequisites and upgrading, if you are not already using clang 3.5.0
213 r342562 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
214 in the same as it is applied to NFSv2 and 3. This implies that NFSv4
215 servers that have vfs.nfsd.nfs_privport set will only allow mounts
216 from clients using a reserved port#. Since both the FreeBSD and Linux
217 NFSv4 clients use reserved port#s by default, this should not affect
221 The '%I' format in the kern.corefile sysctl limits the number of
222 core files that a process can generate to the number stored in the
223 debug.ncores sysctl. The '%I' format is replaced by the single digit
224 index. Previously, if all indexes were taken the kernel would overwrite
225 only a core file with the highest index in a filename.
226 Currently the system will create a new core file if there is a free
227 index or if all slots are taken it will overwrite the oldest one.
230 WITH_OFED option now only enables the build for the OFED libraries
231 and some fundamental client utilities. OpenSM and rest of the
232 debugging tools are enabled by WITH_OFED_EXTRA build switch.
233 WITH_OFED is turned on by default on amd64.
236 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
237 6.0.1. Please see the 20141231 entry below for information about
238 prerequisites and upgrading, if you are not already using clang 3.5.0
242 The releng/11.2 branch has been created from stable/11@r334458.
245 The tz database (tzdb) has been updated to 2018e. This version more
246 correctly models time stamps in time zones with negative DST such as
247 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
248 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
249 time zone abbreviations and the tm_isdst flag.
252 The use of RSS hash from the network card aka flowid has been
253 disabled by default for lagg(4) as it's currently incompatible with
254 the lacp and loadbalance protocols.
256 This can be re-enabled by setting the following in loader.conf:
257 net.link.lagg.default_use_flowid="1"
260 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
261 6.0.0. Please see the 20141231 entry below for information about
262 prerequisites and upgrading, if you are not already using clang 3.5.0
266 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
267 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
268 to WITH/OUT_LOADER_GELI.
271 The geli password typed at boot is now hidden. To restore the previous
272 behavior, see geli(8) for configuration options.
274 The SW_WATCHDOG option is no longer necessary to enable the
275 hardclock-based software watchdog if no hardware watchdog is
276 configured. As before, SW_WATCHDOG will cause the software
277 watchdog to be enabled even if a hardware watchdog is configured.
280 lint(1) binaries and library are no longer built by default. To
281 enable building them, define WITH_LINT in src.conf. If you are using
282 a FreeBSD 12 or later system to build 11-stable, you may need to
283 install a lint(1) binary to use WITH_LINT.
286 When building multiple kernels using KERNCONF, non-existent KERNCONF
287 files will produce an error and buildkernel will fail. Previously
288 missing KERNCONF files silently failed giving no indication as to
289 why, only to subsequently discover during installkernel that the
290 desired kernel was never built in the first place.
293 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
294 Please see the 20141231 entry below for information about prerequisites
295 and upgrading, if you are not already using clang 3.5.0 or higher.
298 Since the switch to GPT disk labels, fsck for UFS/FFS has been
299 unable to automatically find alternate superblocks. As of r322806,
300 the information needed to find alternate superblocks has been
301 moved to the end of the area reserved for the boot block.
302 Filesystems created with a newfs of this vintage or later
303 will create the recovery information. If you have a filesystem
304 created prior to this change and wish to have a recovery block
305 created for your filesystem, you can do so by running fsck in
306 forground mode (i.e., do not use the -p or -y options). As it
307 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
308 to which you should answer yes.
311 The releng/11.1 branch has been created from stable/11@r320475.
314 arm64 builds now use the base system LLD 4.0.0 linker by default,
315 instead of requiring that the aarch64-binutils port or package be
316 installed. To continue using aarch64-binutils, set
317 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
320 The ctl.ko module no longer implements the iSCSI target frontend:
321 cfiscsi.ko does instead.
323 If building cfiscsi.ko as a kernel module, the module can be loaded
324 via one of the following methods:
325 - `cfiscsi_load="YES"` in loader.conf(5).
326 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
327 - ctladm(8)/ctld(8), when compiled with iSCSI support
328 (`WITH_ISCSI=yes` in src.conf(5))
330 Please see cfiscsi(4) for more details.
333 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
334 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
335 same source (previously, the dependency of mmcsd.ko on mmc.ko was
336 missing, but mmcsd.ko now will refuse to load if it is incompatible
340 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
341 use any explicitly assigned loopback address available in the jail
342 instead of using the first assigned address of the jail.
345 As of r316810 for ipfilter, keep frags is no longer assumed when
346 keep state is specified in a rule. r316810 aligns ipfilter with
347 documentation in man pages separating keep frags from keep state.
348 This allows keep state to specified without forcing keep frags
349 and allows keep frags to be specified independently of keep state.
350 To maintain previous behaviour, also specify keep frags with
351 keep state (as documented in ipf.conf.5).
354 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
355 Please see the 20141231 entry below for information about prerequisites
356 and upgrading, if you are not already using clang 3.5.0 or higher.
359 The code that provides support for ZFS .zfs/ directory functionality
360 has been reimplemented. It's not possible now to create a snapshot
361 by mkdir under .zfs/snapshot/. That should be the only user visible
365 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
366 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
367 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
368 and now NAT-T is supported by default. Security associations now use
369 the single namespace for SPI allocation, so if you use several manually
370 configured security associations with the same SPI, this configuration
374 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
375 Please see the 20141231 entry below for information about prerequisites
376 and upgrading, if you are not already using clang 3.5.0 or higher.
379 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
380 Please see the 20141231 entry below for information about prerequisites
381 and upgrading, if you are not already using clang 3.5.0 or higher.
384 The layout of the pmap structure has changed for powerpc to put the pmap
385 statistics at the front for all CPU variations. libkvm(3) and all tools
386 that link against it need to be recompiled.
389 isl(4) and cyapa(4) drivers now require a new driver,
390 chromebook_platform(4), to work properly on Chromebook-class hardware.
391 On other types of hardware the drivers may need to be configured using
392 device hints. Please see the corresponding manual pages for details.
395 Relocatable object files with the extension of .So have been renamed
396 to use an extension of .pico instead. The purpose of this change is
397 to avoid a name clash with shared libraries on case-insensitive file
398 systems. On those file systems, foo.So is the same file as foo.so.
401 The releng/11.0 branch has been created from stable/11@r303970.
404 The stable/11 branch has been created from head@r302406.
407 The libc stub for the pipe(2) system call has been replaced with
408 a wrapper that calls the pipe2(2) system call and the pipe(2)
409 system call is now only implemented by the kernels that include
410 "options COMPAT_FREEBSD10" in their config file (this is the
411 default). Users should ensure that this option is enabled in
412 their kernel or upgrade userspace to r302092 before upgrading their
416 CAM will now strip leading spaces from SCSI disks' serial numbers.
417 This will effect users who create UFS filesystems on SCSI disks using
418 those disk's diskid device nodes. For example, if /etc/fstab
419 previously contained a line like
420 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
421 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
422 transforms like gmirror may also be affected. ZFS users should
426 The bitstring(3) API has been updated with new functionality and
427 improved performance. But it is binary-incompatible with the old API.
428 Objects built with the new headers may not be linked against objects
429 built with the old headers.
432 The brk and sbrk functions have been removed from libc on arm64.
433 Binutils from ports has been updated to not link to these
434 functions and should be updated to the latest version before
435 installing a new libc.
438 The armv6 port now defaults to hard float ABI. Limited support
439 for running both hardfloat and soft float on the same system
440 is available using the libraries installed with -DWITH_LIBSOFT.
441 This has only been tested as an upgrade path for installworld
442 and packages may fail or need manual intervention to run. New
443 packages will be needed.
445 To update an existing self-hosted armv6hf system, you must add
446 TARGET_ARCH=armv6 on the make command line for both the build
447 and the install steps.
450 Kernel modules compiled outside of a kernel build now default to
451 installing to /boot/modules instead of /boot/kernel. Many kernel
452 modules built this way (such as those in ports) already overrode
453 KMODDIR explicitly to install into /boot/modules. However,
454 manually building and installing a module from /sys/modules will
455 now install to /boot/modules instead of /boot/kernel.
458 The CAM I/O scheduler has been committed to the kernel. There should be
459 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
460 list of known rogues that claim support for this but actually corrupt
461 data is believed to be complete, be on the lookout for data
462 corruption. The known rogue list is believed to be complete:
464 o Crucial MX100, M550 drives with MU01 firmware.
465 o Micron M510 and M550 drives with MU01 firmware.
466 o Micron M500 prior to MU07 firmware
467 o Samsung 830, 840, and 850 all firmwares
468 o FCCT M500 all firmwares
470 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
471 with working NCQ TRIM. For Micron branded drives, see your sales rep for
472 updated firmware. Black listed drives will work correctly because these
473 drives work correctly so long as no NCQ TRIMs are sent to them. Given
474 this list is the same as found in Linux, it's believed there are no
475 other rogues in the market place. All other models from the above
478 To be safe, if you are at all concerned, you can quirk each of your
479 drives to prevent NCQ from being sent by setting:
480 kern.cam.ada.X.quirks="0x2"
481 in loader.conf. If the drive requires the 4k sector quirk, set the
485 The FAST_DEPEND build option has been removed and its functionality is
486 now the one true way. The old mkdep(1) style of 'make depend' has
487 been removed. See 20160311 for further details.
490 Resource range types have grown from unsigned long to uintmax_t. All
491 drivers, and anything using libdevinfo, need to be recompiled.
494 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
495 builds. It no longer runs mkdep(1) during 'make depend', and the
496 'make depend' stage can safely be skipped now as it is auto ran
497 when building 'make all' and will generate all SRCS and DPSRCS before
498 building anything else. Dependencies are gathered at compile time with
499 -MF flags kept in separate .depend files per object file. Users should
500 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
504 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
505 kernel modules. Therefore, if you load any kernel modules at boot time,
506 please install the boot loaders after you install the kernel, but before
510 make kernel KERNCONF=YOUR_KERNEL_HERE
511 make -C sys/boot install
512 <reboot in single user>
514 Then follow the usual steps, described in the General Notes section,
518 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
519 see the 20141231 entry below for information about prerequisites and
520 upgrading, if you are not already using clang 3.5.0 or higher.
523 The AIO subsystem is now a standard part of the kernel. The
524 VFS_AIO kernel option and aio.ko kernel module have been removed.
525 Due to stability concerns, asynchronous I/O requests are only
526 permitted on sockets and raw disks by default. To enable
527 asynchronous I/O requests on all file types, set the
528 vfs.aio.enable_unsafe sysctl to a non-zero value.
531 The ELF object manipulation tool objcopy is now provided by the
532 ELF Tool Chain project rather than by GNU binutils. It should be a
533 drop-in replacement, with the addition of arm64 support. The
534 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
535 to obtain the GNU version if necessary.
538 Building ZFS pools on top of zvols is prohibited by default. That
539 feature has never worked safely; it's always been prone to deadlocks.
540 Using a zvol as the backing store for a VM guest's virtual disk will
541 still work, even if the guest is using ZFS. Legacy behavior can be
542 restored by setting vfs.zfs.vol.recursive=1.
545 The NONE and HPN patches has been removed from OpenSSH. They are
546 still available in the security/openssh-portable port.
549 With the addition of ypldap(8), a new _ypldap user is now required
550 during installworld. "mergemaster -p" can be used to add the user
551 prior to installworld, as documented in the handbook.
554 The tftp loader (pxeboot) now uses the option root-path directive. As a
555 consequence it no longer looks for a pxeboot.4th file on the tftp
556 server. Instead it uses the regular /boot infrastructure as with the
560 The code to start recording plug and play data into the modules has
561 been committed. While the old tools will properly build a new kernel,
562 a number of warnings about "unknown metadata record 4" will be produced
563 for an older kldxref. To avoid such warnings, make sure to rebuild
564 the kernel toolchain (or world). Make sure that you have r292078 or
565 later when trying to build 292077 or later before rebuilding.
568 Debug data files are now built by default with 'make buildworld' and
569 installed with 'make installworld'. This facilitates debugging but
570 requires more disk space both during the build and for the installed
571 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
575 r291527 changed the internal interface between the nfsd.ko and
576 nfscommon.ko modules. As such, they must both be upgraded to-gether.
577 __FreeBSD_version has been bumped because of this.
580 Add support for unicode collation strings leads to a change of
581 order of files listed by ls(1) for example. To get back to the old
582 behaviour, set LC_COLLATE environment variable to "C".
584 Databases administrators will need to reindex their databases given
585 collation results will be different.
587 Due to a bug in install(1) it is recommended to remove the ancient
588 locales before running make installworld.
590 rm -rf /usr/share/locale/*
593 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
594 libcrypto.so.7 or libssl.so.7 must be recompiled.
597 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
598 Kernel modules isp_2400_multi and isp_2500_multi were removed and
599 should be replaced with isp_2400 and isp_2500 modules respectively.
602 The build previously allowed using 'make -n' to not recurse into
603 sub-directories while showing what commands would be executed, and
604 'make -n -n' to recursively show commands. Now 'make -n' will recurse
605 and 'make -N' will not.
608 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
609 and etcupdate will now use this file. A custom sendmail.cf is now
610 updated via this mechanism rather than via installworld. If you had
611 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
612 want to remove the exclusion or change it to "always install".
613 /etc/mail/sendmail.cf is now managed the same way regardless of
614 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
615 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
618 Compatibility shims for legacy ATA device names have been removed.
619 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
620 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
621 environment variables, /dev/ad* and /dev/ar* symbolic links.
624 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
625 Please see the 20141231 entry below for information about prerequisites
626 and upgrading, if you are not already using clang 3.5.0 or higher.
629 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
630 and renamed from .symbols to .debug. This reduces the size requirements
631 on the boot partition or file system and provides consistency with
632 userland debug files.
634 When using the supported kernel installation method the
635 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
636 as is done with /boot/kernel.
638 Developers wishing to maintain the historical behavior of installing
639 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
642 The wireless drivers had undergone changes that remove the 'parent
643 interface' from the ifconfig -l output. The rc.d network scripts
644 used to check presence of a parent interface in the list, so old
645 scripts would fail to start wireless networking. Thus, etcupdate(3)
646 or mergemaster(8) run is required after kernel update, to update your
647 rc.d scripts in /etc.
650 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
651 These configurations are now automatically interpreted as
652 'scrub fragment reassemble'.
655 Kernel-loadable modules for the random(4) device are back. To use
656 them, the kernel must have
659 options RANDOM_LOADABLE
661 kldload(8) can then be used to load random_fortuna.ko
662 or random_yarrow.ko. Please note that due to the indirect
663 function calls that the loadable modules need to provide,
664 the build-in variants will be slightly more efficient.
666 The random(4) kernel option RANDOM_DUMMY has been retired due to
667 unpopularity. It was not all that useful anyway.
670 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
671 Control over building the ELF Tool Chain tools is now provided by
672 the WITHOUT_TOOLCHAIN knob.
675 The polarity of Pulse Per Second (PPS) capture events with the
676 uart(4) driver has been corrected. Prior to this change the PPS
677 "assert" event corresponded to the trailing edge of a positive PPS
678 pulse and the "clear" event was the leading edge of the next pulse.
680 As the width of a PPS pulse in a typical GPS receiver is on the
681 order of 1 millisecond, most users will not notice any significant
682 difference with this change.
684 Anyone who has compensated for the historical polarity reversal by
685 configuring a negative offset equal to the pulse width will need to
686 remove that workaround.
689 The default group assigned to /dev/dri entries has been changed
690 from 'wheel' to 'video' with the id of '44'. If you want to have
691 access to the dri devices please add yourself to the video group
694 # pw groupmod video -m $USER
697 The menu.rc and loader.rc files will now be replaced during
698 upgrades. Please migrate local changes to menu.rc.local and
699 loader.rc.local instead.
702 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
703 strings and strip have been removed. The src.conf(5) knob
704 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
707 As ZFS requires more kernel stack pages than is the default on some
708 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
709 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
711 Please consider using 'options KSTACK_PAGES=X' where X is greater
712 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
715 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
716 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
717 default, i.e., they will not contain "::". For example, instead
718 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
719 to have a more specific match, such as different map entries for
720 IPv6:0:0 vs IPv6:0. This change requires that configuration
721 data (including maps, files, classes, custom ruleset, etc.) must
722 use the same format, so make certain such configuration data is
723 upgrading. As a very simple check search for patterns like
724 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
725 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
726 the cf option UseCompressedIPv6Addresses.
729 The default kernel entropy-processing algorithm is now
730 Fortuna, replacing Yarrow.
732 Assuming you have 'device random' in your kernel config
733 file, the configurations allow a kernel option to override
734 this default. You may choose *ONE* of:
736 options RANDOM_YARROW # Legacy /dev/random algorithm.
737 options RANDOM_DUMMY # Blocking-only driver.
739 If you have neither, you get Fortuna. For most people,
740 read no further, Fortuna will give a /dev/random that works
741 like it always used to, and the difference will be irrelevant.
743 If you remove 'device random', you get *NO* kernel-processed
744 entropy at all. This may be acceptable to folks building
745 embedded systems, but has complications. Carry on reading,
746 and it is assumed you know what you need.
748 *PLEASE* read random(4) and random(9) if you are in the
749 habit of tweaking kernel configs, and/or if you are a member
750 of the embedded community, wanting specific and not-usual
751 behaviour from your security subsystems.
753 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
754 random', you will NOT have a functioning /dev/random, and
755 many cryptographic features will not work, including SSH.
756 You may also find strange behaviour from the random(3) set
757 of library functions, in particular sranddev(3), srandomdev(3)
758 and arc4random(3). The reason for this is that the KERN_ARND
759 sysctl only returns entropy if it thinks it has some to
760 share, and with RANDOM_DUMMY or no 'device random' this
764 An additional fix for the issue described in the 20150614 sendmail
765 entry below has been been committed in revision 284717.
768 FreeBSD's old make (fmake) has been removed from the system. It is
769 available as the devel/fmake port or via pkg install fmake.
772 The fix for the issue described in the 20150614 sendmail entry
773 below has been been committed in revision 284436. The work
774 around described in that entry is no longer needed unless the
775 default setting is overridden by a confDH_PARAMETERS configuration
776 setting of '5' or pointing to a 512 bit DH parameter file.
779 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
780 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
781 and devel/kyua to version 0.20+ and adjust any calling code to work
782 with Kyuafile and kyua.
785 The import of openssl to address the FreeBSD-SA-15:10.openssl
786 security advisory includes a change which rejects handshakes
787 with DH parameters below 768 bits. sendmail releases prior
788 to 8.15.2 (not yet released), defaulted to a 512 bit
789 DH parameter setting for client connections. To work around
790 this interoperability, sendmail can be configured to use a
791 2048 bit DH parameter by:
793 1. Edit /etc/mail/`hostname`.mc
794 2. If a setting for confDH_PARAMETERS does not exist or
795 exists and is set to a string beginning with '5',
797 3. If a setting for confDH_PARAMETERS exists and is set to
798 a file path, create a new file with:
799 openssl dhparam -out /path/to/file 2048
800 4. Rebuild the .cf file:
801 cd /etc/mail/; make; make install
803 cd /etc/mail/; make restart
805 A sendmail patch is coming, at which time this file will be
809 Generation of legacy formatted entries have been disabled by default
810 in pwd_mkdb(8), as all base system consumers of the legacy formatted
811 entries were converted to use the new format by default when the new,
812 machine independent format have been added and supported since FreeBSD
815 Please see the pwd_mkdb(8) manual page for further details.
818 Clang and llvm have been upgraded to 3.6.1 release. Please see the
819 20141231 entry below for information about prerequisites and upgrading,
820 if you are not already using 3.5.0 or higher.
823 TI platform code switched to using vendor DTS files and this update
824 may break existing systems running on Beaglebone, Beaglebone Black,
827 - dtb files should be regenerated/reinstalled. Filenames are the
828 same but content is different now
829 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
830 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
831 addressing scheme is now pin 25 on /dev/gpioc3.
832 - Pandaboard: /etc/ttys should be updated, serial console device is
833 now /dev/ttyu2, not /dev/ttyu0
836 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
837 If you need the GNU extension from groff soelim(1), install groff
838 from package: pkg install groff, or via ports: textproc/groff.
841 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
842 defined in symlink(7); previously symlinks were silently ignored.
845 The const qualifier has been removed from iconv(3) to comply with
846 POSIX. The ports tree is aware of this from r384038 onwards.
849 Libraries specified by LIBADD in Makefiles must have a corresponding
850 DPADD_<lib> variable to ensure correct dependencies. This is now
851 enforced in src.libnames.mk.
854 From legacy ata(4) driver was removed support for SATA controllers
855 supported by more functional drivers ahci(4), siis(4) and mvs(4).
856 Kernel modules ataahci and ataadaptec were removed completely,
857 replaced by ahci and mvs modules respectively.
860 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
861 the 20141231 entry below for information about prerequisites and
862 upgrading, if you are not already using 3.5.0 or higher.
865 The 32-bit PowerPC kernel has been changed to a position-independent
866 executable. This can only be booted with a version of loader(8)
867 newer than January 31, 2015, so make sure to update both world and
868 kernel before rebooting.
871 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
872 but before r278950, the RNG was not seeded properly. Immediately
873 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
874 ssh keys or openssl keys) that were generated w/ a kernel from that
875 range. This does not affect programs that directly used /dev/random
876 or /dev/urandom. All userland uses of arc4random(3) are affected.
879 The autofs(4) ABI was changed in order to restore binary compatibility
880 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
884 The powerpc64 kernel has been changed to a position-independent
885 executable. This can only be booted with a new version of loader(8),
886 so make sure to update both world and kernel before rebooting.
889 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
890 only release, no new features have been added. Please see the 20141231
891 entry below for information about prerequisites and upgrading, if you
892 are not already using 3.5.0.
895 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
896 taken from the ELF Tool Chain project rather than GNU binutils. They
897 should be drop-in replacements, with the addition of arm64 support.
898 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
899 binutils tools, if necessary. See 20150805 for updated information.
902 The default Unbound configuration now enables remote control
903 using a local socket. Users who have already enabled the
904 local_unbound service should regenerate their configuration
905 by running "service local_unbound setup" as root.
908 The GNU texinfo and GNU info pages have been removed.
909 To be able to view GNU info pages please install texinfo from ports.
912 Clang, llvm and lldb have been upgraded to 3.5.0 release.
914 As of this release, a prerequisite for building clang, llvm and lldb is
915 a C++11 capable compiler and C++11 standard library. This means that to
916 be able to successfully build the cross-tools stage of buildworld, with
917 clang as the bootstrap compiler, your system compiler or cross compiler
918 should either be clang 3.3 or later, or gcc 4.8 or later, and your
919 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
922 On any standard FreeBSD 10.x or 11.x installation, where clang and
923 libc++ are on by default (that is, on x86 or arm), this should work out
926 On 9.x installations where clang is enabled by default, e.g. on x86 and
927 powerpc, libc++ will not be enabled by default, so libc++ should be
928 built (with clang) and installed first. If both clang and libc++ are
929 missing, build clang first, then use it to build libc++.
931 On 8.x and earlier installations, upgrade to 9.x first, and then follow
932 the instructions for 9.x above.
934 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
935 default, and do not build clang.
937 Many embedded systems are resource constrained, and will not be able to
938 build clang in a reasonable time, or in some cases at all. In those
939 cases, cross building bootable systems on amd64 is a workaround.
941 This new version of clang introduces a number of new warnings, of which
942 the following are most likely to appear:
946 This warns in two cases, for both C and C++:
947 * When the code is trying to take the absolute value of an unsigned
948 quantity, which is effectively a no-op, and almost never what was
949 intended. The code should be fixed, if at all possible. If you are
950 sure that the unsigned quantity can be safely cast to signed, without
951 loss of information or undefined behavior, you can add an explicit
952 cast, or disable the warning.
954 * When the code is trying to take an absolute value, but the called
955 abs() variant is for the wrong type, which can lead to truncation.
956 If you want to disable the warning instead of fixing the code, please
957 make sure that truncation will not occur, or it might lead to unwanted
960 -Wtautological-undefined-compare and
961 -Wundefined-bool-conversion
963 These warn when C++ code is trying to compare 'this' against NULL, while
964 'this' should never be NULL in well-defined C++ code. However, there is
965 some legacy (pre C++11) code out there, which actively abuses this
966 feature, which was less strictly defined in previous C++ versions.
968 Squid and openjdk do this, for example. The warning can be turned off
969 for C++98 and earlier, but compiling the code in C++11 mode might result
970 in unexpected behavior; for example, the parts of the program that are
971 unreachable could be optimized away.
974 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
975 kernel sources have been removed. The .h files remain, since some
976 utilities include them. This will need to be fixed later.
977 If "mount -t oldnfs ..." is attempted, it will fail.
978 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
979 the utilities will report errors.
982 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
983 directories to top level SUBDIR variable when their parent
984 directory is included in LOCAL_DIRS. Users with build systems with
985 such hierarchies and without SUBDIR entries in the parent
986 directory Makefiles should add them or add the directories to
990 faith(4) and faithd(8) have been removed from the base system. Faith
991 has been obsolete for a very long time.
994 vt(4), the new console driver, is enabled by default. It brings
995 support for Unicode and double-width characters, as well as
996 support for UEFI and integration with the KMS kernel video
999 You may need to update your console settings in /etc/rc.conf,
1000 most probably the keymap. During boot, /etc/rc.d/syscons will
1001 indicate what you need to do.
1003 vt(4) still has issues and lacks some features compared to
1004 syscons(4). See the wiki for up-to-date information:
1005 https://wiki.freebsd.org/Newcons
1007 If you want to keep using syscons(4), you can do so by adding
1008 the following line to /boot/loader.conf:
1012 pjdfstest has been integrated into kyua as an opt-in test suite.
1013 Please see share/doc/pjdfstest/README for more details on how to
1017 gperf has been removed from the base system for architectures
1018 that use clang. Ports that require gperf will obtain it from the
1022 pjdfstest has been moved from tools/regression/pjdfstest to
1026 At svn r271982, The default linux compat kernel ABI has been adjusted
1027 to 2.6.18 in support of the linux-c6 compat ports infrastructure
1028 update. If you wish to continue using the linux-f10 compat ports,
1029 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
1030 encouraged to update their linux-compat packages to linux-c6 during
1031 their next update cycle.
1034 The ofwfb driver, used to provide a graphics console on PowerPC when
1035 using vt(4), no longer allows mmap() of all physical memory. This
1036 will prevent Xorg on PowerPC with some ATI graphics cards from
1037 initializing properly unless x11-servers/xorg-server is updated to
1041 The xdev targets have been converted to using TARGET and
1042 TARGET_ARCH instead of XDEV and XDEV_ARCH.
1045 The default unbound configuration has been modified to address
1046 issues with reverse lookups on networks that use private
1047 address ranges. If you use the local_unbound service, run
1048 "service local_unbound setup" as root to regenerate your
1049 configuration, then "service local_unbound reload" to load the
1053 The GNU texinfo and GNU info pages are not built and installed
1054 anymore, WITH_INFO knob has been added to allow to built and install
1056 UPDATE: see 20150102 entry on texinfo's removal
1059 The GNU readline library is now an INTERNALLIB - that is, it is
1060 statically linked into consumers (GDB and variants) in the base
1061 system, and the shared library is no longer installed. The
1062 devel/readline port is available for third party software that
1066 The Itanium architecture (ia64) has been removed from the list of
1067 known architectures. This is the first step in the removal of the
1071 Commit r268115 has added NFSv4.1 server support, merged from
1072 projects/nfsv4.1-server. Since this includes changes to the
1073 internal interfaces between the NFS related modules, a full
1074 build of the kernel and modules will be necessary.
1075 __FreeBSD_version has been bumped.
1078 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1079 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
1080 which differs from the behaviour controlled by this knob.)
1083 Maximal length of the serial number in CTL was increased from 16 to
1084 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
1085 and ctld, need to be rebuilt to work with a new kernel.
1088 The libatf-c and libatf-c++ major versions were downgraded to 0 and
1089 1 respectively to match the upstream numbers. They were out of
1090 sync because, when they were originally added to FreeBSD, the
1091 upstream versions were not respected. These libraries are private
1092 and not yet built by default, so renumbering them should be a
1093 non-issue. However, unclean source trees will yield broken test
1094 programs once the operator executes "make delete-old-libs" after a
1095 "make installworld".
1097 Additionally, the atf-sh binary was made private by moving it into
1098 /usr/libexec/. Already-built shell test programs will keep the
1099 path to the old binary so they will break after "make delete-old"
1102 If you are using WITH_TESTS=yes (not the default), wipe the object
1103 tree and rebuild from scratch to prevent spurious test failures.
1104 This is only needed once: the misnumbered libraries and misplaced
1105 binaries have been added to OptionalObsoleteFiles.inc so they will
1106 be removed during a clean upgrade.
1109 Clang and llvm have been upgraded to 3.4.1 release.
1112 We bogusly installed src.opts.mk in /usr/share/mk. This file should
1113 be removed to avoid issues in the future (and has been added to
1117 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
1118 past, it affected all builds that used the bsd.*.mk files. The old
1119 behavior was a bug, but people may have relied upon it. To get this
1120 behavior back, you can .include /etc/src.conf from /etc/make.conf
1121 (which is still global and isn't changed). This also changes the
1122 behavior of incremental builds inside the tree of individual
1123 directories. Set MAKESYSPATH to ".../share/mk" to do that.
1124 Although this has survived make universe and some upgrade scenarios,
1125 other upgrade scenarios may have broken. At least one form of
1126 temporary breakage was fixed with MAKESYSPATH settings for buildworld
1127 as well... In cases where MAKESYSPATH isn't working with this
1128 setting, you'll need to set it to the full path to your tree.
1130 One side effect of all this cleaning up is that bsd.compiler.mk
1131 is no longer implicitly included by bsd.own.mk. If you wish to
1132 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1136 The lindev device has been removed since /dev/full has been made a
1137 standard device. __FreeBSD_version has been bumped.
1140 The knob WITHOUT_VI was added to the base system, which controls
1141 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1142 in order to reorder files share/termcap and didn't build ex(1) as a
1143 build tool, so building/installing with WITH_VI is highly advised for
1144 build hosts for older releases.
1146 This issue has been fixed in stable/9 and stable/10 in r277022 and
1147 r276991, respectively.
1150 The YES_HESIOD knob has been removed. It has been obsolete for
1151 a decade. Please move to using WITH_HESIOD instead or your builds
1152 will silently lack HESIOD.
1155 The uart(4) driver has been changed with respect to its handling
1156 of the low-level console. Previously the uart(4) driver prevented
1157 any process from changing the baudrate or the CLOCAL and HUPCL
1158 control flags. By removing the restrictions, operators can make
1159 changes to the serial console port without having to reboot.
1160 However, when getty(8) is started on the serial device that is
1161 associated with the low-level console, a misconfigured terminal
1162 line in /etc/ttys will now have a real impact.
1163 Before upgrading the kernel, make sure that /etc/ttys has the
1164 serial console device configured as 3wire without baudrate to
1165 preserve the previous behaviour. E.g:
1166 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
1169 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1170 to improve performance. To re-enable it, if needed, run rpcbind
1171 with command line option -W.
1174 Switched back to the GPL dtc compiler due to updates in the upstream
1175 dts files not being supported by the BSDL dtc compiler. You will need
1176 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1177 may result while building dtb files during a kernel build if you fail
1178 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1181 Clang and llvm have been upgraded to 3.4 release.
1184 The nve(4) driver has been removed. Please use the nfe(4) driver
1185 for NVIDIA nForce MCP Ethernet adapters instead.
1188 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1189 This could cause certain C++ applications using shared libraries built
1190 against the previous version of libc++ to crash. The incompatibility
1191 has now been fixed, but any C++ applications or shared libraries built
1192 between r261283 and r261801 should be recompiled.
1195 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1196 capability mode support. Please note that enabling the feature in
1197 kernel is still highly recommended.
1200 OpenSSH is now built with sandbox support, and will use sandbox as
1201 the default privilege separation method. This requires Capsicum
1202 capability mode support in kernel.
1205 The libelf and libdwarf libraries have been updated to newer
1206 versions from upstream. Shared library version numbers for
1207 these two libraries were bumped. Any ports or binaries
1208 requiring these two libraries should be recompiled.
1209 __FreeBSD_version is bumped to 1100006.
1212 If a Makefile in a tests/ directory was auto-generating a Kyuafile
1213 instead of providing an explicit one, this would prevent such
1214 Makefile from providing its own Kyuafile in the future during
1215 NO_CLEAN builds. This has been fixed in the Makefiles but manual
1216 intervention is needed to clean an objdir if you use NO_CLEAN:
1217 # find /usr/obj -name Kyuafile | xargs rm -f
1220 The behavior of gss_pseudo_random() for the krb5 mechanism
1221 has changed, for applications requesting a longer random string
1222 than produced by the underlying enctype's pseudo-random() function.
1223 In particular, the random string produced from a session key of
1224 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1225 be different at the 17th octet and later, after this change.
1226 The counter used in the PRF+ construction is now encoded as a
1227 big-endian integer in accordance with RFC 4402.
1228 __FreeBSD_version is bumped to 1100004.
1231 The WITHOUT_ATF build knob has been removed and its functionality
1232 has been subsumed into the more generic WITHOUT_TESTS. If you were
1233 using the former to disable the build of the ATF libraries, you
1234 should change your settings to use the latter.
1237 The default version of mtree is nmtree which is obtained from
1238 NetBSD. The output is generally the same, but may vary
1239 slightly. If you found you need identical output adding
1240 "-F freebsd9" to the command line should do the trick. For the
1241 time being, the old mtree is available as fmtree.
1244 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1245 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1246 1.1.4_8 and verify bsdyml not linked in, before running "make
1248 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1250 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1253 The stable/10 branch has been created in subversion from head
1257 The rc.d/jail script has been updated to support jail(8)
1258 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1259 for per-jail configuration are automatically converted to
1260 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1261 This is transparently backward compatible. See below about some
1262 incompatibilities and rc.conf(5) manual page for more details.
1264 These variables are now deprecated in favor of jail(8) configuration
1265 file. One can use "rc.d/jail config <jname>" command to generate
1266 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1267 running the jail(8) utility. The default pathname of the
1268 configuration file is /etc/jail.conf and can be specified by
1269 using $jail_conf or $jail_<jname>_conf variables.
1271 Please note that jail_devfs_ruleset accepts an integer at
1272 this moment. Please consider to rewrite the ruleset name
1276 BIND has been removed from the base system. If all you need
1277 is a local resolver, simply enable and start the local_unbound
1278 service instead. Otherwise, several versions of BIND are
1279 available in the ports tree. The dns/bind99 port is one example.
1281 With this change, nslookup(1) and dig(1) are no longer in the base
1282 system. Users should instead use host(1) and drill(1) which are
1283 in the base system. Alternatively, nslookup and dig can
1284 be obtained by installing the dns/bind-tools port.
1287 With the addition of unbound(8), a new unbound user is now
1288 required during installworld. "mergemaster -p" can be used to
1289 add the user prior to installworld, as documented in the handbook.
1292 OpenSSH is now built with DNSSEC support, and will by default
1293 silently trust signed SSHFP records. This can be controlled with
1294 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1295 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1298 The GNU Compiler Collection and C++ standard library (libstdc++)
1299 are no longer built by default on platforms where clang is the system
1300 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1301 options in src.conf.
1304 The PROCDESC kernel option is now part of the GENERIC kernel
1305 configuration and is required for the rwhod(8) to work.
1306 If you are using custom kernel configuration, you should include
1310 The API and ABI related to the Capsicum framework was modified
1311 in backward incompatible way. The userland libraries and programs
1312 have to be recompiled to work with the new kernel. This includes the
1313 following libraries and programs, but the whole buildworld is
1314 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1315 kdump, procstat, rwho, rwhod, uniq.
1318 AES-NI intrinsic support has been added to gcc. The AES-NI module
1319 has been updated to use this support. A new gcc is required to build
1320 the aesni module on both i386 and amd64.
1323 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1324 Thus "device padlock_rng" and "device rdrand_rng" should be
1325 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1328 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1329 enables just the iconv* functionality and is now on by default.
1330 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1331 compatibility. Set WITHOUT_ICONV to build the old way.
1332 If you have been using WITH_ICONV before, you will very likely
1333 need to turn on WITH_LIBICONV_COMPAT.
1336 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1337 Illumos origin, including ZFS. If you have INVARIANTS in your
1338 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1340 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1341 locks if WITNESS option was set. Because that generated a lot of
1342 witness(9) reports and all of them were believed to be false
1343 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1344 can be used to achieve the previous behavior.
1347 Timer values in IPv6 data structures now use time_uptime instead
1348 of time_second. Although this is not a user-visible functional
1349 change, userland utilities which directly use them---ndp(8),
1350 rtadvd(8), and rtsold(8) in the base system---need to be updated
1351 to r253970 or later.
1354 find -delete can now delete the pathnames given as arguments,
1355 instead of only files found below them or if the pathname did
1356 not contain any slashes. Formerly, the following error message
1359 find: -delete: <path>: relative path potentially not safe
1361 Deleting the pathnames given as arguments can be prevented
1362 without error messages using -mindepth 1 or by changing
1363 directory and passing "." as argument to find. This works in the
1364 old as well as the new version of find.
1367 Behavior of devfs rules path matching has been changed.
1368 Pattern is now always matched against fully qualified devfs
1369 path and slash characters must be explicitly matched by
1370 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1371 subdirectories must be reviewed.
1374 The default ARM ABI has changed to the ARM EABI. The old ABI is
1375 incompatible with the ARM EABI and all programs and modules will
1376 need to be rebuilt to work with a new kernel.
1378 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1380 NOTE: Support for the old ABI will be removed in the future and
1381 users are advised to upgrade.
1384 pkg_install has been disconnected from the build if you really need it
1385 you should add WITH_PKGTOOLS in your src.conf(5).
1388 Most of network statistics structures were changed to be able
1389 keep 64-bits counters. Thus all tools, that work with networking
1390 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1393 Fix a bug that allowed a tracing process (e.g. gdb) to write
1394 to a memory-mapped file in the traced process's address space
1395 even if neither the traced process nor the tracing process had
1396 write access to that file.
1399 CVS has been removed from the base system. An exact copy
1400 of the code is available from the devel/cvs port.
1403 Some people report the following error after the switch to bmake:
1405 make: illegal option -- J
1406 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1408 *** [buildworld] Error code 2
1410 this likely due to an old instance of make in
1411 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1412 which src/Makefile will use that blindly, if it exists, so if
1413 you see the above error:
1415 rm -rf `make -V MAKEPATH`
1420 Use bmake by default.
1421 Whereas before one could choose to build with bmake via
1422 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1423 make. The goal is to remove these knobs for 10-RELEASE.
1425 It is worth noting that bmake (like gmake) treats the command
1426 line as the unit of failure, rather than statements within the
1427 command line. Thus '(cd some/where && dosomething)' is safer
1428 than 'cd some/where; dosomething'. The '()' allows consistent
1429 behavior in parallel build.
1432 Fix a bug that allows NFS clients to issue READDIR on files.
1435 The WITHOUT_IDEA option has been removed because
1436 the IDEA patent expired.
1439 The sysctl which controls TRIM support under ZFS has been renamed
1440 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1444 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1445 rather than creating it's own in the temporary directory in
1446 order allow access to bootstrapped versions of tools such as
1447 install and mtree. When upgrading from version of FreeBSD where
1448 the install command does not support -l, you will need to
1449 install a new mergemaster command if mergemaster -p is required.
1450 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1454 Legacy ATA stack, disabled and replaced by new CAM-based one since
1455 FreeBSD 9.0, completely removed from the sources. Kernel modules
1456 atadisk and atapi*, user-level tools atacontrol and burncd are
1457 removed. Kernel option `options ATA_CAM` is now permanently enabled
1461 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1462 and socketpair(2). Software, in particular Kerberos, may
1463 automatically detect and use these during building. The resulting
1464 binaries will not work on older kernels.
1467 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1468 information, see the respective 20130304 entry).
1471 Recent commits to callout(9) changed the size of struct callout,
1472 so the KBI is probably heavily disturbed. Also, some functions
1473 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1474 by macros. Every kernel module using it won't load, so rebuild
1477 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1478 but does not initialize by default (because of the new CTL_DISABLE
1479 option) to save memory. To re-enable it, remove the CTL_DISABLE
1480 option from the kernel config file or set kern.cam.ctl.disable=0
1481 in /boot/loader.conf.
1484 The ctl device has been disabled in GENERIC for i386 and amd64.
1485 This was done due to the extra memory being allocated at system
1486 initialisation time by the ctl driver which was only used if
1487 a CAM target device was created. This makes a FreeBSD system
1488 unusable on 128MB or less of RAM.
1491 A new compression method (lz4) has been merged to -HEAD. Please
1492 refer to zpool-features(7) for more information.
1494 Please refer to the "ZFS notes" section of this file for information
1495 on upgrading boot ZFS pools.
1498 A BSD-licensed patch(1) variant has been added and is installed
1499 as bsdpatch, being the GNU version the default patch.
1500 To inverse the logic and use the BSD-licensed one as default,
1501 while having the GNU version installed as gnupatch, rebuild
1502 and install world with the WITH_BSD_PATCH knob set.
1505 Due to the use of the new -l option to install(1) during build
1506 and install, you must take care not to directly set the INSTALL
1507 make variable in your /etc/make.conf, /etc/src.conf, or on the
1508 command line. If you wish to use the -C flag for all installs
1509 you may be able to add INSTALL+=-C to /etc/make.conf or
1513 The install(1) option -M has changed meaning and now takes an
1514 argument that is a file or path to append logs to. In the
1515 unlikely event that -M was the last option on the command line
1516 and the command line contained at least two files and a target
1517 directory the first file will have logs appended to it. The -M
1518 option served little practical purpose in the last decade so its
1519 use is expected to be extremely rare.
1522 After switching to Clang as the default compiler some users of ZFS
1523 on i386 systems started to experience stack overflow kernel panics.
1524 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1527 GEOM_LABEL now mangles label names read from file system metadata.
1528 Mangling affect labels containing spaces, non-printable characters,
1529 '%' or '"'. Device names in /etc/fstab and other places may need to
1533 By default, only the 10 most recent kernel dumps will be saved. To
1534 restore the previous behaviour (no limit on the number of kernel dumps
1535 stored in the dump directory) add the following line to /etc/rc.conf:
1540 With the addition of auditdistd(8), a new auditdistd user is now
1541 required during installworld. "mergemaster -p" can be used to
1542 add the user prior to installworld, as documented in the handbook.
1545 The sin6_scope_id member variable in struct sockaddr_in6 is now
1546 filled by the kernel before passing the structure to the userland via
1547 sysctl or routing socket. This means the KAME-specific embedded scope
1548 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1549 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1550 __FreeBSD_version is bumped to 1000025.
1553 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1554 This means that the world and kernel will be compiled with clang
1555 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1556 and /usr/bin/cpp. To disable this behavior and revert to building
1557 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1558 of current may need to bootstrap WITHOUT_CLANG first if the clang
1559 build fails (its compatibility window doesn't extend to the 9 stable
1563 The IPFIREWALL_FORWARD kernel option has been removed. Its
1564 functionality now turned on by default.
1567 The ZERO_COPY_SOCKET kernel option has been removed and
1568 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1569 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1570 mechanism which is not safe and may result in kernel crashes.
1571 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1572 driver supports disposeable external page sized mbuf storage.
1573 Proper replacements for both zero-copy mechanisms are under
1574 consideration and will eventually lead to complete removal
1575 of the two kernel options.
1578 The IPv4 network stack has been converted to network byte
1579 order. The following modules need to be recompiled together
1580 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1581 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1584 Support for non-MPSAFE filesystems was removed from VFS. The
1585 VFS_VERSION was bumped, all filesystem modules shall be
1589 All the non-MPSAFE filesystems have been disconnected from
1590 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1591 portalfs, smbfs, xfs.
1594 The interface cloning API and ABI has changed. The following
1595 modules need to be recompiled together with kernel:
1596 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1597 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1598 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1601 The sdhci driver was split in two parts: sdhci (generic SD Host
1602 Controller logic) and sdhci_pci (actual hardware driver).
1603 No kernel config modifications are required, but if you
1604 load sdhc as a module you must switch to sdhci_pci instead.
1607 Import the FUSE kernel and userland support into base system.
1610 The GNU sort(1) program has been removed since the BSD-licensed
1611 sort(1) has been the default for quite some time and no serious
1612 problems have been reported. The corresponding WITH_GNU_SORT
1616 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1617 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1621 The net80211(4) ABI has been changed to allow for improved driver
1622 PS-POLL and power-save support. All wireless drivers need to be
1623 recompiled to work with the new kernel.
1626 The random(4) support for the VIA hardware random number
1627 generator (`PADLOCK') is no longer enabled unconditionally.
1628 Add the padlock_rng device in the custom kernel config if
1629 needed. The GENERIC kernels on i386 and amd64 do include the
1630 device, so the change only affects the custom kernel
1634 The pf(4) packet filter ABI has been changed. pfctl(8) and
1635 snmp_pf module need to be recompiled to work with new kernel.
1638 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1639 to -HEAD. Pools that have empty_bpobj in active state can not be
1640 imported read-write with ZFS implementations that do not support
1641 this feature. For more information read the zpool-features(5)
1645 The sparc64 ZFS loader has been changed to no longer try to auto-
1646 detect ZFS providers based on diskN aliases but now requires these
1647 to be explicitly listed in the OFW boot-device environment variable.
1650 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1651 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1652 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1655 The following sysctls and tunables have been renamed for consistency
1656 with other variables:
1657 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1658 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1661 The sort utility has been replaced with BSD sort. For now, GNU sort
1662 is also available as "gnusort" or the default can be set back to
1663 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1664 installed as "bsdsort".
1667 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1668 Starting with this version the old system of ZFS pool versioning
1669 is superseded by "feature flags". This concept enables forward
1670 compatibility against certain future changes in functionality of ZFS
1671 pools. The first read-only compatible "feature flag" for ZFS pools
1672 is named "com.delphix:async_destroy". For more information
1673 read the new zpool-features(5) manual page.
1674 Please refer to the "ZFS notes" section of this file for information
1675 on upgrading boot ZFS pools.
1678 The malloc(3) implementation embedded in libc now uses sources imported
1679 as contrib/jemalloc. The most disruptive API change is to
1680 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1681 delete it prior to installworld, and optionally re-create it using the
1682 new format after rebooting. See malloc.conf(5) for details
1683 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1687 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1688 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1689 now spelled mips. This is to aid compatibility with third-party
1690 software that expects this naming scheme in uname(3). Little-endian
1691 settings are unchanged. If you are updating a big-endian mips64 machine
1692 from before this change, you may need to set MACHINE_ARCH=mips64 in
1693 your environment before the new build system will recognize your machine.
1696 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1700 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1701 nullfs(5) did not pass through all behaviours to the underlying layer,
1702 as a result if we bound to a socket on the lower layer we could connect
1703 only to the lower path; if we bound to the upper layer we could connect
1704 only to the upper path. The new behavior is one can connect to both the
1705 lower and the upper paths regardless what layer path one binds to.
1708 The getifaddrs upgrade path broken with 20111215 has been restored.
1709 If you have upgraded in between 20111215 and 20120209 you need to
1710 recompile libc again with your kernel. You still need to recompile
1711 world to be able to configure CARP but this restriction already
1712 comes from 20111215.
1715 The set_rcvar() function has been removed from /etc/rc.subr. All
1716 base and ports rc.d scripts have been updated, so if you have a
1717 port installed with a script in /usr/local/etc/rc.d you can either
1718 hand-edit the rcvar= line, or reinstall the port.
1720 An easy way to handle the mass-update of /etc/rc.d:
1721 rm /etc/rc.d/* && mergemaster -i
1724 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1725 on the current CPU and prevents other threads from running.
1726 This behavior can be reverted using the kern.stop_scheduler_on_panic
1728 The new behavior can be incompatible with kern.sync_on_panic.
1731 The carp(4) facility has been changed significantly. Configuration
1732 of the CARP protocol via ifconfig(8) has changed, as well as format
1733 of CARP events submitted to devd(8) has changed. See manual pages
1734 for more information. The arpbalance feature of carp(4) is currently
1735 not supported anymore.
1737 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1738 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1739 need to be recompiled.
1742 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1746 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1747 explicitely support non-MPSAFE filesystems.
1748 It is on by default for all supported platform at this present
1752 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1753 i386 and pc98 GENERIC kernel configuration files.
1756 sysinstall has been removed
1759 The stable/9 branch created in subversion. This corresponds to the
1760 RELENG_9 branch in CVS.
1766 Avoid using make -j when upgrading. While generally safe, there are
1767 sometimes problems using -j to upgrade. If your upgrade fails with
1768 -j, please try again without -j. From time to time in the past there
1769 have been problems using -j with buildworld and/or installworld. This
1770 is especially true when upgrading between "distant" versions (eg one
1771 that cross a major release boundary or several minor releases, or when
1772 several months have passed on the -current branch).
1774 Sometimes, obscure build problems are the result of environment
1775 poisoning. This can happen because the make utility reads its
1776 environment when searching for values for global variables. To run
1777 your build attempts in an "environmental clean room", prefix all make
1778 commands with 'env -i '. See the env(1) manual page for more details.
1780 When upgrading from one major version to another it is generally best
1781 to upgrade to the latest code in the currently installed branch first,
1782 then do an upgrade to the new branch. This is the best-tested upgrade
1783 path, and has the highest probability of being successful. Please try
1784 this approach before reporting problems with a major version upgrade.
1786 When upgrading a live system, having a root shell around before
1787 installing anything can help undo problems. Not having a root shell
1788 around can lead to problems if pam has changed too much from your
1789 starting point to allow continued authentication after the upgrade.
1791 This file should be read as a log of events. When a later event changes
1792 information of a prior event, the prior event should not be deleted.
1793 Instead, a pointer to the entry with the new information should be
1794 placed in the old entry. Readers of this file should also sanity check
1795 older entries before relying on them blindly. Authors of new entries
1796 should write them with this in mind.
1800 When upgrading the boot ZFS pool to a new version, always follow
1803 1.) recompile and reinstall the ZFS boot loader and boot block
1804 (this is part of "make buildworld" and "make installworld")
1806 2.) update the ZFS boot block on your boot drive
1808 The following example updates the ZFS boot block on the first
1809 partition (freebsd-boot) of a GPT partitioned drive ada0:
1810 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1812 Non-boot pools do not need these updates.
1816 If you are updating from a prior version of FreeBSD (even one just
1817 a few days old), you should follow this procedure. It is the most
1818 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1820 make kernel-toolchain
1821 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1822 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1824 To test a kernel once
1825 ---------------------
1826 If you just want to boot a kernel once (because you are not sure
1827 if it works, or if you want to boot a known bad kernel to provide
1828 debugging information) run
1829 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1830 nextboot -k testkernel
1832 To just build a kernel when you know that it won't mess you up
1833 --------------------------------------------------------------
1834 This assumes you are already running a CURRENT system. Replace
1835 ${arch} with the architecture of your machine (e.g. "i386",
1836 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1838 cd src/sys/${arch}/conf
1839 config KERNEL_NAME_HERE
1840 cd ../compile/KERNEL_NAME_HERE
1845 If this fails, go to the "To build a kernel" section.
1847 To rebuild everything and install it on the current system.
1848 -----------------------------------------------------------
1849 # Note: sometimes if you are running current you gotta do more than
1850 # is listed here if you are upgrading from a really old current.
1852 <make sure you have good level 0 dumps>
1854 make kernel KERNCONF=YOUR_KERNEL_HERE
1856 <reboot in single user> [3]
1863 To cross-install current onto a separate partition
1864 --------------------------------------------------
1865 # In this approach we use a separate partition to hold
1866 # current's root, 'usr', and 'var' directories. A partition
1867 # holding "/", "/usr" and "/var" should be about 2GB in
1870 <make sure you have good level 0 dumps>
1873 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1874 <maybe newfs current's root partition>
1875 <mount current's root partition on directory ${CURRENT_ROOT}>
1876 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1877 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1878 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1879 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1880 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1881 <reboot into current>
1882 <do a "native" rebuild/install as described in the previous section>
1883 <maybe install compatibility libraries from ports/misc/compat*>
1887 To upgrade in-place from stable to current
1888 ----------------------------------------------
1889 <make sure you have good level 0 dumps>
1891 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1893 <reboot in single user> [3]
1900 Make sure that you've read the UPDATING file to understand the
1901 tweaks to various things you need. At this point in the life
1902 cycle of current, things change often and you are on your own
1903 to cope. The defaults can also change, so please read ALL of
1904 the UPDATING entries.
1906 Also, if you are tracking -current, you must be subscribed to
1907 freebsd-current@freebsd.org. Make sure that before you update
1908 your sources that you have read and understood all the recent
1909 messages there. If in doubt, please track -stable which has
1910 much fewer pitfalls.
1912 [1] If you have third party modules, such as vmware, you
1913 should disable them at this point so they don't crash your
1916 [3] From the bootblocks, boot -s, and then do
1921 adjkerntz -i # if CMOS is wall time
1922 Also, when doing a major release upgrade, it is required that
1923 you boot into single user mode to do the installworld.
1925 [4] Note: This step is non-optional. Failure to do this step
1926 can result in a significant reduction in the functionality of the
1927 system. Attempting to do it by hand is not recommended and those
1928 that pursue this avenue should read this file carefully, as well
1929 as the archives of freebsd-current and freebsd-hackers mailing lists
1930 for potential gotchas. The -U option is also useful to consider.
1931 See mergemaster(8) for more information.
1933 [5] Usually this step is a noop. However, from time to time
1934 you may need to do this if you get unknown user in the following
1935 step. It never hurts to do it all the time. You may need to
1936 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1937 install) after the buildworld before this step if you last updated
1938 from current before 20130425 or from -stable before 20130430.
1940 [6] This only deletes old files and directories. Old libraries
1941 can be deleted by "make delete-old-libs", but you have to make
1942 sure that no program is using those libraries anymore.
1944 [8] The new kernel must be able to run existing binaries used by
1945 an installworld. When upgrading across major versions, the new
1946 kernel's configuration must include the correct COMPAT_FREEBSD<n>
1947 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x
1948 binaries). Failure to do so may leave you with a system that is
1949 hard to boot to recover. A GENERIC kernel will include suitable
1950 compatibility options to run binaries from older branches.
1952 Make sure that you merge any new devices from GENERIC since the
1953 last time you updated your kernel config file.
1955 [9] When checking out sources, you must include the -P flag to have
1956 cvs prune empty directories.
1958 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1959 "?=" instead of the "=" assignment operator, so that buildworld can
1960 override the CPUTYPE if it needs to.
1962 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1963 not on the command line, or in /etc/make.conf. buildworld will
1964 warn if it is improperly defined.
1967 This file contains a list, in reverse chronological order, of major
1968 breakages in tracking -current. It is not guaranteed to be a complete
1969 list of such breakages, and only contains entries since September 23, 2011.
1970 If you need to see UPDATING entries from before that date, you will need
1971 to fetch an UPDATING file from an older FreeBSD release.
1973 Copyright information:
1975 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1977 Redistribution, publication, translation and use, with or without
1978 modification, in full or in part, in any form or format of this
1979 document are permitted without further permission from the author.
1981 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1982 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1983 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1984 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1985 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1986 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1987 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1988 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1989 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1990 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1991 POSSIBILITY OF SUCH DAMAGE.
1993 Contact Warner Losh if you have any questions about your use of