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.
20 The tz database (tzdb) has been updated to 2018e. This version more
21 correctly models time stamps in time zones with negative DST such as
22 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
23 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
24 time zone abbreviations and the tm_isdst flag.
27 The use of RSS hash from the network card aka flowid has been
28 disabled by default for lagg(4) as it's currently incompatible with
29 the lacp and loadbalance protocols.
31 This can be re-enabled by setting the following in loader.conf:
32 net.link.lagg.default_use_flowid="1"
35 Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
36 6.0.0. Please see the 20141231 entry below for information about
37 prerequisites and upgrading, if you are not already using clang 3.5.0
41 The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
42 WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
43 to WITH/OUT_LOADER_GELI.
46 The geli password typed at boot is now hidden. To restore the previous
47 behavior, see geli(8) for configuration options.
49 The SW_WATCHDOG option is no longer necessary to enable the
50 hardclock-based software watchdog if no hardware watchdog is
51 configured. As before, SW_WATCHDOG will cause the software
52 watchdog to be enabled even if a hardware watchdog is configured.
55 lint(1) binaries and library are no longer built by default. To
56 enable building them, define WITH_LINT in src.conf. If you are using
57 a FreeBSD 12 or later system to build 11-stable, you may need to
58 install a lint(1) binary to use WITH_LINT.
61 When building multiple kernels using KERNCONF, non-existent KERNCONF
62 files will produce an error and buildkernel will fail. Previously
63 missing KERNCONF files silently failed giving no indication as to
64 why, only to subsequently discover during installkernel that the
65 desired kernel was never built in the first place.
68 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
69 Please see the 20141231 entry below for information about prerequisites
70 and upgrading, if you are not already using clang 3.5.0 or higher.
73 Since the switch to GPT disk labels, fsck for UFS/FFS has been
74 unable to automatically find alternate superblocks. As of r322806,
75 the information needed to find alternate superblocks has been
76 moved to the end of the area reserved for the boot block.
77 Filesystems created with a newfs of this vintage or later
78 will create the recovery information. If you have a filesystem
79 created prior to this change and wish to have a recovery block
80 created for your filesystem, you can do so by running fsck in
81 forground mode (i.e., do not use the -p or -y options). As it
82 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
83 to which you should answer yes.
86 arm64 builds now use the base system LLD 4.0.0 linker by default,
87 instead of requiring that the aarch64-binutils port or package be
88 installed. To continue using aarch64-binutils, set
89 CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
92 The ctl.ko module no longer implements the iSCSI target frontend:
93 cfiscsi.ko does instead.
95 If building cfiscsi.ko as a kernel module, the module can be loaded
96 via one of the following methods:
97 - `cfiscsi_load="YES"` in loader.conf(5).
98 - Add `cfiscsi` to `$kld_list` in rc.conf(5).
99 - ctladm(8)/ctld(8), when compiled with iSCSI support
100 (`WITH_ISCSI=yes` in src.conf(5))
102 Please see cfiscsi(4) for more details.
105 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
106 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
107 same source (previously, the dependency of mmcsd.ko on mmc.ko was
108 missing, but mmcsd.ko now will refuse to load if it is incompatible
112 Binds and sends to the loopback addresses, IPv6 and IPv4, will now
113 use any explicitly assigned loopback address available in the jail
114 instead of using the first assigned address of the jail.
117 As of r316810 for ipfilter, keep frags is no longer assumed when
118 keep state is specified in a rule. r316810 aligns ipfilter with
119 documentation in man pages separating keep frags from keep state.
120 This allows keep state to specified without forcing keep frags
121 and allows keep frags to be specified independently of keep state.
122 To maintain previous behaviour, also specify keep frags with
123 keep state (as documented in ipf.conf.5).
126 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
127 Please see the 20141231 entry below for information about prerequisites
128 and upgrading, if you are not already using clang 3.5.0 or higher.
131 The code that provides support for ZFS .zfs/ directory functionality
132 has been reimplemented. It's not possible now to create a snapshot
133 by mkdir under .zfs/snapshot/. That should be the only user visible
137 Many changes in the IPsec code have been merged from the FreeBSD-CURRENT
138 branch. The IPSEC_FILTERTUNNEL kernel option is removed in favour of
139 corresponding sysctl. The IPSEC_NAT_T kernel option is also removed,
140 and now NAT-T is supported by default. Security associations now use
141 the single namespace for SPI allocation, so if you use several manually
142 configured security associations with the same SPI, this configuration
146 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
147 Please see the 20141231 entry below for information about prerequisites
148 and upgrading, if you are not already using clang 3.5.0 or higher.
151 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
152 Please see the 20141231 entry below for information about prerequisites
153 and upgrading, if you are not already using clang 3.5.0 or higher.
156 The layout of the pmap structure has changed for powerpc to put the pmap
157 statistics at the front for all CPU variations. libkvm(3) and all tools
158 that link against it need to be recompiled.
161 isl(4) and cyapa(4) drivers now require a new driver,
162 chromebook_platform(4), to work properly on Chromebook-class hardware.
163 On other types of hardware the drivers may need to be configured using
164 device hints. Please see the corresponding manual pages for details.
167 Relocatable object files with the extension of .So have been renamed
168 to use an extension of .pico instead. The purpose of this change is
169 to avoid a name clash with shared libraries on case-insensitive file
170 systems. On those file systems, foo.So is the same file as foo.so.
173 The libc stub for the pipe(2) system call has been replaced with
174 a wrapper that calls the pipe2(2) system call and the pipe(2)
175 system call is now only implemented by the kernels that include
176 "options COMPAT_FREEBSD10" in their config file (this is the
177 default). Users should ensure that this option is enabled in
178 their kernel or upgrade userspace to r302092 before upgrading their
182 CAM will now strip leading spaces from SCSI disks' serial numbers.
183 This will effect users who create UFS filesystems on SCSI disks using
184 those disk's diskid device nodes. For example, if /etc/fstab
185 previously contained a line like
186 "/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
187 change it to "/dev/diskid/DISK-ABCDEFG0123456". Users of geom
188 transforms like gmirror may also be affected. ZFS users should
192 The bitstring(3) API has been updated with new functionality and
193 improved performance. But it is binary-incompatible with the old API.
194 Objects built with the new headers may not be linked against objects
195 built with the old headers.
198 The brk and sbrk functions have been removed from libc on arm64.
199 Binutils from ports has been updated to not link to these
200 functions and should be updated to the latest version before
201 installing a new libc.
204 The armv6 port now defaults to hard float ABI. Limited support
205 for running both hardfloat and soft float on the same system
206 is available using the libraries installed with -DWITH_LIBSOFT.
207 This has only been tested as an upgrade path for installworld
208 and packages may fail or need manual intervention to run. New
209 packages will be needed.
211 To update an existing self-hosted armv6hf system, you must add
212 TARGET_ARCH=armv6 on the make command line for both the build
213 and the install steps.
216 Kernel modules compiled outside of a kernel build now default to
217 installing to /boot/modules instead of /boot/kernel. Many kernel
218 modules built this way (such as those in ports) already overrode
219 KMODDIR explicitly to install into /boot/modules. However,
220 manually building and installing a module from /sys/modules will
221 now install to /boot/modules instead of /boot/kernel.
224 The CAM I/O scheduler has been committed to the kernel. There should be
225 no user visible impact. This does enable NCQ Trim on ada SSDs. While the
226 list of known rogues that claim support for this but actually corrupt
227 data is believed to be complete, be on the lookout for data
228 corruption. The known rogue list is believed to be complete:
230 o Crucial MX100, M550 drives with MU01 firmware.
231 o Micron M510 and M550 drives with MU01 firmware.
232 o Micron M500 prior to MU07 firmware
233 o Samsung 830, 840, and 850 all firmwares
234 o FCCT M500 all firmwares
236 Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
237 with working NCQ TRIM. For Micron branded drives, see your sales rep for
238 updated firmware. Black listed drives will work correctly because these
239 drives work correctly so long as no NCQ TRIMs are sent to them. Given
240 this list is the same as found in Linux, it's believed there are no
241 other rogues in the market place. All other models from the above
244 To be safe, if you are at all concerned, you can quirk each of your
245 drives to prevent NCQ from being sent by setting:
246 kern.cam.ada.X.quirks="0x2"
247 in loader.conf. If the drive requires the 4k sector quirk, set the
251 The FAST_DEPEND build option has been removed and its functionality is
252 now the one true way. The old mkdep(1) style of 'make depend' has
253 been removed. See 20160311 for further details.
256 Resource range types have grown from unsigned long to uintmax_t. All
257 drivers, and anything using libdevinfo, need to be recompiled.
260 WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
261 builds. It no longer runs mkdep(1) during 'make depend', and the
262 'make depend' stage can safely be skipped now as it is auto ran
263 when building 'make all' and will generate all SRCS and DPSRCS before
264 building anything else. Dependencies are gathered at compile time with
265 -MF flags kept in separate .depend files per object file. Users should
266 run 'make cleandepend' once if using -DNO_CLEAN to clean out older
270 On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
271 kernel modules. Therefore, if you load any kernel modules at boot time,
272 please install the boot loaders after you install the kernel, but before
276 make kernel KERNCONF=YOUR_KERNEL_HERE
277 make -C sys/boot install
278 <reboot in single user>
280 Then follow the usual steps, described in the General Notes section,
284 Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0. Please
285 see the 20141231 entry below for information about prerequisites and
286 upgrading, if you are not already using clang 3.5.0 or higher.
289 The AIO subsystem is now a standard part of the kernel. The
290 VFS_AIO kernel option and aio.ko kernel module have been removed.
291 Due to stability concerns, asynchronous I/O requests are only
292 permitted on sockets and raw disks by default. To enable
293 asynchronous I/O requests on all file types, set the
294 vfs.aio.enable_unsafe sysctl to a non-zero value.
297 The ELF object manipulation tool objcopy is now provided by the
298 ELF Tool Chain project rather than by GNU binutils. It should be a
299 drop-in replacement, with the addition of arm64 support. The
300 (temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
301 to obtain the GNU version if necessary.
304 Building ZFS pools on top of zvols is prohibited by default. That
305 feature has never worked safely; it's always been prone to deadlocks.
306 Using a zvol as the backing store for a VM guest's virtual disk will
307 still work, even if the guest is using ZFS. Legacy behavior can be
308 restored by setting vfs.zfs.vol.recursive=1.
311 The NONE and HPN patches has been removed from OpenSSH. They are
312 still available in the security/openssh-portable port.
315 With the addition of ypldap(8), a new _ypldap user is now required
316 during installworld. "mergemaster -p" can be used to add the user
317 prior to installworld, as documented in the handbook.
320 The tftp loader (pxeboot) now uses the option root-path directive. As a
321 consequence it no longer looks for a pxeboot.4th file on the tftp
322 server. Instead it uses the regular /boot infrastructure as with the
326 The code to start recording plug and play data into the modules has
327 been committed. While the old tools will properly build a new kernel,
328 a number of warnings about "unknown metadata record 4" will be produced
329 for an older kldxref. To avoid such warnings, make sure to rebuild
330 the kernel toolchain (or world). Make sure that you have r292078 or
331 later when trying to build 292077 or later before rebuilding.
334 Debug data files are now built by default with 'make buildworld' and
335 installed with 'make installworld'. This facilitates debugging but
336 requires more disk space both during the build and for the installed
337 world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
341 r291527 changed the internal interface between the nfsd.ko and
342 nfscommon.ko modules. As such, they must both be upgraded to-gether.
343 __FreeBSD_version has been bumped because of this.
346 Add support for unicode collation strings leads to a change of
347 order of files listed by ls(1) for example. To get back to the old
348 behaviour, set LC_COLLATE environment variable to "C".
350 Databases administrators will need to reindex their databases given
351 collation results will be different.
353 Due to a bug in install(1) it is recommended to remove the ancient
354 locales before running make installworld.
356 rm -rf /usr/share/locale/*
359 The OpenSSL has been upgraded to 1.0.2d. Any binaries requiring
360 libcrypto.so.7 or libssl.so.7 must be recompiled.
363 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
364 Kernel modules isp_2400_multi and isp_2500_multi were removed and
365 should be replaced with isp_2400 and isp_2500 modules respectively.
368 The build previously allowed using 'make -n' to not recurse into
369 sub-directories while showing what commands would be executed, and
370 'make -n -n' to recursively show commands. Now 'make -n' will recurse
371 and 'make -N' will not.
374 If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
375 and etcupdate will now use this file. A custom sendmail.cf is now
376 updated via this mechanism rather than via installworld. If you had
377 excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
378 want to remove the exclusion or change it to "always install".
379 /etc/mail/sendmail.cf is now managed the same way regardless of
380 whether SENDMAIL_MC/SENDMAIL_CF is used. If you are not using
381 SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
384 Compatibility shims for legacy ATA device names have been removed.
385 It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
386 and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
387 environment variables, /dev/ad* and /dev/ar* symbolic links.
390 Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
391 Please see the 20141231 entry below for information about prerequisites
392 and upgrading, if you are not already using clang 3.5.0 or higher.
395 Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
396 and renamed from .symbols to .debug. This reduces the size requirements
397 on the boot partition or file system and provides consistency with
398 userland debug files.
400 When using the supported kernel installation method the
401 /usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
402 as is done with /boot/kernel.
404 Developers wishing to maintain the historical behavior of installing
405 debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
408 The wireless drivers had undergone changes that remove the 'parent
409 interface' from the ifconfig -l output. The rc.d network scripts
410 used to check presence of a parent interface in the list, so old
411 scripts would fail to start wireless networking. Thus, etcupdate(3)
412 or mergemaster(8) run is required after kernel update, to update your
413 rc.d scripts in /etc.
416 pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
417 These configurations are now automatically interpreted as
418 'scrub fragment reassemble'.
421 Kernel-loadable modules for the random(4) device are back. To use
422 them, the kernel must have
425 options RANDOM_LOADABLE
427 kldload(8) can then be used to load random_fortuna.ko
428 or random_yarrow.ko. Please note that due to the indirect
429 function calls that the loadable modules need to provide,
430 the build-in variants will be slightly more efficient.
432 The random(4) kernel option RANDOM_DUMMY has been retired due to
433 unpopularity. It was not all that useful anyway.
436 The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
437 Control over building the ELF Tool Chain tools is now provided by
438 the WITHOUT_TOOLCHAIN knob.
441 The polarity of Pulse Per Second (PPS) capture events with the
442 uart(4) driver has been corrected. Prior to this change the PPS
443 "assert" event corresponded to the trailing edge of a positive PPS
444 pulse and the "clear" event was the leading edge of the next pulse.
446 As the width of a PPS pulse in a typical GPS receiver is on the
447 order of 1 millisecond, most users will not notice any significant
448 difference with this change.
450 Anyone who has compensated for the historical polarity reversal by
451 configuring a negative offset equal to the pulse width will need to
452 remove that workaround.
455 The default group assigned to /dev/dri entries has been changed
456 from 'wheel' to 'video' with the id of '44'. If you want to have
457 access to the dri devices please add yourself to the video group
460 # pw groupmod video -m $USER
463 The menu.rc and loader.rc files will now be replaced during
464 upgrades. Please migrate local changes to menu.rc.local and
465 loader.rc.local instead.
468 GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
469 strings and strip have been removed. The src.conf(5) knob
470 WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
473 As ZFS requires more kernel stack pages than is the default on some
474 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
475 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
477 Please consider using 'options KSTACK_PAGES=X' where X is greater
478 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
481 sendmail has been updated to 8.15.2. Starting with FreeBSD 11.0
482 and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
483 default, i.e., they will not contain "::". For example, instead
484 of ::1, it will be 0:0:0:0:0:0:0:1. This permits a zero subnet
485 to have a more specific match, such as different map entries for
486 IPv6:0:0 vs IPv6:0. This change requires that configuration
487 data (including maps, files, classes, custom ruleset, etc.) must
488 use the same format, so make certain such configuration data is
489 upgrading. As a very simple check search for patterns like
490 'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'. To return to the old
491 behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
492 the cf option UseCompressedIPv6Addresses.
495 The default kernel entropy-processing algorithm is now
496 Fortuna, replacing Yarrow.
498 Assuming you have 'device random' in your kernel config
499 file, the configurations allow a kernel option to override
500 this default. You may choose *ONE* of:
502 options RANDOM_YARROW # Legacy /dev/random algorithm.
503 options RANDOM_DUMMY # Blocking-only driver.
505 If you have neither, you get Fortuna. For most people,
506 read no further, Fortuna will give a /dev/random that works
507 like it always used to, and the difference will be irrelevant.
509 If you remove 'device random', you get *NO* kernel-processed
510 entropy at all. This may be acceptable to folks building
511 embedded systems, but has complications. Carry on reading,
512 and it is assumed you know what you need.
514 *PLEASE* read random(4) and random(9) if you are in the
515 habit of tweaking kernel configs, and/or if you are a member
516 of the embedded community, wanting specific and not-usual
517 behaviour from your security subsystems.
519 NOTE!! If you use RANDOM_DUMMY and/or have no 'device
520 random', you will NOT have a functioning /dev/random, and
521 many cryptographic features will not work, including SSH.
522 You may also find strange behaviour from the random(3) set
523 of library functions, in particular sranddev(3), srandomdev(3)
524 and arc4random(3). The reason for this is that the KERN_ARND
525 sysctl only returns entropy if it thinks it has some to
526 share, and with RANDOM_DUMMY or no 'device random' this
530 An additional fix for the issue described in the 20150614 sendmail
531 entry below has been been committed in revision 284717.
534 FreeBSD's old make (fmake) has been removed from the system. It is
535 available as the devel/fmake port or via pkg install fmake.
538 The fix for the issue described in the 20150614 sendmail entry
539 below has been been committed in revision 284436. The work
540 around described in that entry is no longer needed unless the
541 default setting is overridden by a confDH_PARAMETERS configuration
542 setting of '5' or pointing to a 512 bit DH parameter file.
545 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
546 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
547 and devel/kyua to version 0.20+ and adjust any calling code to work
548 with Kyuafile and kyua.
551 The import of openssl to address the FreeBSD-SA-15:10.openssl
552 security advisory includes a change which rejects handshakes
553 with DH parameters below 768 bits. sendmail releases prior
554 to 8.15.2 (not yet released), defaulted to a 512 bit
555 DH parameter setting for client connections. To work around
556 this interoperability, sendmail can be configured to use a
557 2048 bit DH parameter by:
559 1. Edit /etc/mail/`hostname`.mc
560 2. If a setting for confDH_PARAMETERS does not exist or
561 exists and is set to a string beginning with '5',
563 3. If a setting for confDH_PARAMETERS exists and is set to
564 a file path, create a new file with:
565 openssl dhparam -out /path/to/file 2048
566 4. Rebuild the .cf file:
567 cd /etc/mail/; make; make install
569 cd /etc/mail/; make restart
571 A sendmail patch is coming, at which time this file will be
575 Generation of legacy formatted entries have been disabled by default
576 in pwd_mkdb(8), as all base system consumers of the legacy formatted
577 entries were converted to use the new format by default when the new,
578 machine independent format have been added and supported since FreeBSD
581 Please see the pwd_mkdb(8) manual page for further details.
584 Clang and llvm have been upgraded to 3.6.1 release. Please see the
585 20141231 entry below for information about prerequisites and upgrading,
586 if you are not already using 3.5.0 or higher.
589 TI platform code switched to using vendor DTS files and this update
590 may break existing systems running on Beaglebone, Beaglebone Black,
593 - dtb files should be regenerated/reinstalled. Filenames are the
594 same but content is different now
595 - GPIO addressing was changed, now each GPIO bank (32 pins per bank)
596 has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
597 addressing scheme is now pin 25 on /dev/gpioc3.
598 - Pandaboard: /etc/ttys should be updated, serial console device is
599 now /dev/ttyu2, not /dev/ttyu0
602 soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
603 If you need the GNU extension from groff soelim(1), install groff
604 from package: pkg install groff, or via ports: textproc/groff.
607 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
608 defined in symlink(7); previously symlinks were silently ignored.
611 The const qualifier has been removed from iconv(3) to comply with
612 POSIX. The ports tree is aware of this from r384038 onwards.
615 Libraries specified by LIBADD in Makefiles must have a corresponding
616 DPADD_<lib> variable to ensure correct dependencies. This is now
617 enforced in src.libnames.mk.
620 From legacy ata(4) driver was removed support for SATA controllers
621 supported by more functional drivers ahci(4), siis(4) and mvs(4).
622 Kernel modules ataahci and ataadaptec were removed completely,
623 replaced by ahci and mvs modules respectively.
626 Clang, llvm and lldb have been upgraded to 3.6.0 release. Please see
627 the 20141231 entry below for information about prerequisites and
628 upgrading, if you are not already using 3.5.0 or higher.
631 The 32-bit PowerPC kernel has been changed to a position-independent
632 executable. This can only be booted with a version of loader(8)
633 newer than January 31, 2015, so make sure to update both world and
634 kernel before rebooting.
637 If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
638 but before r278950, the RNG was not seeded properly. Immediately
639 upgrade the kernel to r278950 or later and regenerate any keys (e.g.
640 ssh keys or openssl keys) that were generated w/ a kernel from that
641 range. This does not affect programs that directly used /dev/random
642 or /dev/urandom. All userland uses of arc4random(3) are affected.
645 The autofs(4) ABI was changed in order to restore binary compatibility
646 with 10.1-RELEASE. The automountd(8) daemon needs to be rebuilt to work
650 The powerpc64 kernel has been changed to a position-independent
651 executable. This can only be booted with a new version of loader(8),
652 so make sure to update both world and kernel before rebooting.
655 Clang and llvm have been upgraded to 3.5.1 release. This is a bugfix
656 only release, no new features have been added. Please see the 20141231
657 entry below for information about prerequisites and upgrading, if you
658 are not already using 3.5.0.
661 ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
662 taken from the ELF Tool Chain project rather than GNU binutils. They
663 should be drop-in replacements, with the addition of arm64 support.
664 The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
665 binutils tools, if necessary. See 20150805 for updated information.
668 The default Unbound configuration now enables remote control
669 using a local socket. Users who have already enabled the
670 local_unbound service should regenerate their configuration
671 by running "service local_unbound setup" as root.
674 The GNU texinfo and GNU info pages have been removed.
675 To be able to view GNU info pages please install texinfo from ports.
678 Clang, llvm and lldb have been upgraded to 3.5.0 release.
680 As of this release, a prerequisite for building clang, llvm and lldb is
681 a C++11 capable compiler and C++11 standard library. This means that to
682 be able to successfully build the cross-tools stage of buildworld, with
683 clang as the bootstrap compiler, your system compiler or cross compiler
684 should either be clang 3.3 or later, or gcc 4.8 or later, and your
685 system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
688 On any standard FreeBSD 10.x or 11.x installation, where clang and
689 libc++ are on by default (that is, on x86 or arm), this should work out
692 On 9.x installations where clang is enabled by default, e.g. on x86 and
693 powerpc, libc++ will not be enabled by default, so libc++ should be
694 built (with clang) and installed first. If both clang and libc++ are
695 missing, build clang first, then use it to build libc++.
697 On 8.x and earlier installations, upgrade to 9.x first, and then follow
698 the instructions for 9.x above.
700 Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
701 default, and do not build clang.
703 Many embedded systems are resource constrained, and will not be able to
704 build clang in a reasonable time, or in some cases at all. In those
705 cases, cross building bootable systems on amd64 is a workaround.
707 This new version of clang introduces a number of new warnings, of which
708 the following are most likely to appear:
712 This warns in two cases, for both C and C++:
713 * When the code is trying to take the absolute value of an unsigned
714 quantity, which is effectively a no-op, and almost never what was
715 intended. The code should be fixed, if at all possible. If you are
716 sure that the unsigned quantity can be safely cast to signed, without
717 loss of information or undefined behavior, you can add an explicit
718 cast, or disable the warning.
720 * When the code is trying to take an absolute value, but the called
721 abs() variant is for the wrong type, which can lead to truncation.
722 If you want to disable the warning instead of fixing the code, please
723 make sure that truncation will not occur, or it might lead to unwanted
726 -Wtautological-undefined-compare and
727 -Wundefined-bool-conversion
729 These warn when C++ code is trying to compare 'this' against NULL, while
730 'this' should never be NULL in well-defined C++ code. However, there is
731 some legacy (pre C++11) code out there, which actively abuses this
732 feature, which was less strictly defined in previous C++ versions.
734 Squid and openjdk do this, for example. The warning can be turned off
735 for C++98 and earlier, but compiling the code in C++11 mode might result
736 in unexpected behavior; for example, the parts of the program that are
737 unreachable could be optimized away.
740 The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
741 kernel sources have been removed. The .h files remain, since some
742 utilities include them. This will need to be fixed later.
743 If "mount -t oldnfs ..." is attempted, it will fail.
744 If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
745 the utilities will report errors.
748 The handling of LOCAL_LIB_DIRS has been altered to skip addition of
749 directories to top level SUBDIR variable when their parent
750 directory is included in LOCAL_DIRS. Users with build systems with
751 such hierarchies and without SUBDIR entries in the parent
752 directory Makefiles should add them or add the directories to
756 faith(4) and faithd(8) have been removed from the base system. Faith
757 has been obsolete for a very long time.
760 vt(4), the new console driver, is enabled by default. It brings
761 support for Unicode and double-width characters, as well as
762 support for UEFI and integration with the KMS kernel video
765 You may need to update your console settings in /etc/rc.conf,
766 most probably the keymap. During boot, /etc/rc.d/syscons will
767 indicate what you need to do.
769 vt(4) still has issues and lacks some features compared to
770 syscons(4). See the wiki for up-to-date information:
771 https://wiki.freebsd.org/Newcons
773 If you want to keep using syscons(4), you can do so by adding
774 the following line to /boot/loader.conf:
778 pjdfstest has been integrated into kyua as an opt-in test suite.
779 Please see share/doc/pjdfstest/README for more details on how to
783 gperf has been removed from the base system for architectures
784 that use clang. Ports that require gperf will obtain it from the
788 pjdfstest has been moved from tools/regression/pjdfstest to
792 At svn r271982, The default linux compat kernel ABI has been adjusted
793 to 2.6.18 in support of the linux-c6 compat ports infrastructure
794 update. If you wish to continue using the linux-f10 compat ports,
795 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
796 encouraged to update their linux-compat packages to linux-c6 during
797 their next update cycle.
800 The ofwfb driver, used to provide a graphics console on PowerPC when
801 using vt(4), no longer allows mmap() of all physical memory. This
802 will prevent Xorg on PowerPC with some ATI graphics cards from
803 initializing properly unless x11-servers/xorg-server is updated to
807 The xdev targets have been converted to using TARGET and
808 TARGET_ARCH instead of XDEV and XDEV_ARCH.
811 The default unbound configuration has been modified to address
812 issues with reverse lookups on networks that use private
813 address ranges. If you use the local_unbound service, run
814 "service local_unbound setup" as root to regenerate your
815 configuration, then "service local_unbound reload" to load the
819 The GNU texinfo and GNU info pages are not built and installed
820 anymore, WITH_INFO knob has been added to allow to built and install
822 UPDATE: see 20150102 entry on texinfo's removal
825 The GNU readline library is now an INTERNALLIB - that is, it is
826 statically linked into consumers (GDB and variants) in the base
827 system, and the shared library is no longer installed. The
828 devel/readline port is available for third party software that
832 The Itanium architecture (ia64) has been removed from the list of
833 known architectures. This is the first step in the removal of the
837 Commit r268115 has added NFSv4.1 server support, merged from
838 projects/nfsv4.1-server. Since this includes changes to the
839 internal interfaces between the NFS related modules, a full
840 build of the kernel and modules will be necessary.
841 __FreeBSD_version has been bumped.
844 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
845 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
846 which differs from the behaviour controlled by this knob.)
849 Maximal length of the serial number in CTL was increased from 16 to
850 64 chars, that breaks ABI. All CTL-related tools, such as ctladm
851 and ctld, need to be rebuilt to work with a new kernel.
854 The libatf-c and libatf-c++ major versions were downgraded to 0 and
855 1 respectively to match the upstream numbers. They were out of
856 sync because, when they were originally added to FreeBSD, the
857 upstream versions were not respected. These libraries are private
858 and not yet built by default, so renumbering them should be a
859 non-issue. However, unclean source trees will yield broken test
860 programs once the operator executes "make delete-old-libs" after a
863 Additionally, the atf-sh binary was made private by moving it into
864 /usr/libexec/. Already-built shell test programs will keep the
865 path to the old binary so they will break after "make delete-old"
868 If you are using WITH_TESTS=yes (not the default), wipe the object
869 tree and rebuild from scratch to prevent spurious test failures.
870 This is only needed once: the misnumbered libraries and misplaced
871 binaries have been added to OptionalObsoleteFiles.inc so they will
872 be removed during a clean upgrade.
875 Clang and llvm have been upgraded to 3.4.1 release.
878 We bogusly installed src.opts.mk in /usr/share/mk. This file should
879 be removed to avoid issues in the future (and has been added to
883 /etc/src.conf now affects only builds of the FreeBSD src tree. In the
884 past, it affected all builds that used the bsd.*.mk files. The old
885 behavior was a bug, but people may have relied upon it. To get this
886 behavior back, you can .include /etc/src.conf from /etc/make.conf
887 (which is still global and isn't changed). This also changes the
888 behavior of incremental builds inside the tree of individual
889 directories. Set MAKESYSPATH to ".../share/mk" to do that.
890 Although this has survived make universe and some upgrade scenarios,
891 other upgrade scenarios may have broken. At least one form of
892 temporary breakage was fixed with MAKESYSPATH settings for buildworld
893 as well... In cases where MAKESYSPATH isn't working with this
894 setting, you'll need to set it to the full path to your tree.
896 One side effect of all this cleaning up is that bsd.compiler.mk
897 is no longer implicitly included by bsd.own.mk. If you wish to
898 use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
902 The lindev device has been removed since /dev/full has been made a
903 standard device. __FreeBSD_version has been bumped.
906 The knob WITHOUT_VI was added to the base system, which controls
907 building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
908 in order to reorder files share/termcap and didn't build ex(1) as a
909 build tool, so building/installing with WITH_VI is highly advised for
910 build hosts for older releases.
912 This issue has been fixed in stable/9 and stable/10 in r277022 and
913 r276991, respectively.
916 The YES_HESIOD knob has been removed. It has been obsolete for
917 a decade. Please move to using WITH_HESIOD instead or your builds
918 will silently lack HESIOD.
921 The uart(4) driver has been changed with respect to its handling
922 of the low-level console. Previously the uart(4) driver prevented
923 any process from changing the baudrate or the CLOCAL and HUPCL
924 control flags. By removing the restrictions, operators can make
925 changes to the serial console port without having to reboot.
926 However, when getty(8) is started on the serial device that is
927 associated with the low-level console, a misconfigured terminal
928 line in /etc/ttys will now have a real impact.
929 Before upgrading the kernel, make sure that /etc/ttys has the
930 serial console device configured as 3wire without baudrate to
931 preserve the previous behaviour. E.g:
932 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
935 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
936 to improve performance. To re-enable it, if needed, run rpcbind
937 with command line option -W.
940 Switched back to the GPL dtc compiler due to updates in the upstream
941 dts files not being supported by the BSDL dtc compiler. You will need
942 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
943 may result while building dtb files during a kernel build if you fail
944 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
947 Clang and llvm have been upgraded to 3.4 release.
950 The nve(4) driver has been removed. Please use the nfe(4) driver
951 for NVIDIA nForce MCP Ethernet adapters instead.
954 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
955 This could cause certain C++ applications using shared libraries built
956 against the previous version of libc++ to crash. The incompatibility
957 has now been fixed, but any C++ applications or shared libraries built
958 between r261283 and r261801 should be recompiled.
961 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
962 capability mode support. Please note that enabling the feature in
963 kernel is still highly recommended.
966 OpenSSH is now built with sandbox support, and will use sandbox as
967 the default privilege separation method. This requires Capsicum
968 capability mode support in kernel.
971 The libelf and libdwarf libraries have been updated to newer
972 versions from upstream. Shared library version numbers for
973 these two libraries were bumped. Any ports or binaries
974 requiring these two libraries should be recompiled.
975 __FreeBSD_version is bumped to 1100006.
978 If a Makefile in a tests/ directory was auto-generating a Kyuafile
979 instead of providing an explicit one, this would prevent such
980 Makefile from providing its own Kyuafile in the future during
981 NO_CLEAN builds. This has been fixed in the Makefiles but manual
982 intervention is needed to clean an objdir if you use NO_CLEAN:
983 # find /usr/obj -name Kyuafile | xargs rm -f
986 The behavior of gss_pseudo_random() for the krb5 mechanism
987 has changed, for applications requesting a longer random string
988 than produced by the underlying enctype's pseudo-random() function.
989 In particular, the random string produced from a session key of
990 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
991 be different at the 17th octet and later, after this change.
992 The counter used in the PRF+ construction is now encoded as a
993 big-endian integer in accordance with RFC 4402.
994 __FreeBSD_version is bumped to 1100004.
997 The WITHOUT_ATF build knob has been removed and its functionality
998 has been subsumed into the more generic WITHOUT_TESTS. If you were
999 using the former to disable the build of the ATF libraries, you
1000 should change your settings to use the latter.
1003 The default version of mtree is nmtree which is obtained from
1004 NetBSD. The output is generally the same, but may vary
1005 slightly. If you found you need identical output adding
1006 "-F freebsd9" to the command line should do the trick. For the
1007 time being, the old mtree is available as fmtree.
1010 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1011 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1012 1.1.4_8 and verify bsdyml not linked in, before running "make
1014 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1016 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1019 The stable/10 branch has been created in subversion from head
1023 The rc.d/jail script has been updated to support jail(8)
1024 configuration file. The "jail_<jname>_*" rc.conf(5) variables
1025 for per-jail configuration are automatically converted to
1026 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
1027 This is transparently backward compatible. See below about some
1028 incompatibilities and rc.conf(5) manual page for more details.
1030 These variables are now deprecated in favor of jail(8) configuration
1031 file. One can use "rc.d/jail config <jname>" command to generate
1032 a jail(8) configuration file in /var/run/jail.<jname>.conf without
1033 running the jail(8) utility. The default pathname of the
1034 configuration file is /etc/jail.conf and can be specified by
1035 using $jail_conf or $jail_<jname>_conf variables.
1037 Please note that jail_devfs_ruleset accepts an integer at
1038 this moment. Please consider to rewrite the ruleset name
1042 BIND has been removed from the base system. If all you need
1043 is a local resolver, simply enable and start the local_unbound
1044 service instead. Otherwise, several versions of BIND are
1045 available in the ports tree. The dns/bind99 port is one example.
1047 With this change, nslookup(1) and dig(1) are no longer in the base
1048 system. Users should instead use host(1) and drill(1) which are
1049 in the base system. Alternatively, nslookup and dig can
1050 be obtained by installing the dns/bind-tools port.
1053 With the addition of unbound(8), a new unbound user is now
1054 required during installworld. "mergemaster -p" can be used to
1055 add the user prior to installworld, as documented in the handbook.
1058 OpenSSH is now built with DNSSEC support, and will by default
1059 silently trust signed SSHFP records. This can be controlled with
1060 the VerifyHostKeyDNS client configuration setting. DNSSEC support
1061 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
1064 The GNU Compiler Collection and C++ standard library (libstdc++)
1065 are no longer built by default on platforms where clang is the system
1066 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
1067 options in src.conf.
1070 The PROCDESC kernel option is now part of the GENERIC kernel
1071 configuration and is required for the rwhod(8) to work.
1072 If you are using custom kernel configuration, you should include
1076 The API and ABI related to the Capsicum framework was modified
1077 in backward incompatible way. The userland libraries and programs
1078 have to be recompiled to work with the new kernel. This includes the
1079 following libraries and programs, but the whole buildworld is
1080 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
1081 kdump, procstat, rwho, rwhod, uniq.
1084 AES-NI intrinsic support has been added to gcc. The AES-NI module
1085 has been updated to use this support. A new gcc is required to build
1086 the aesni module on both i386 and amd64.
1089 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
1090 Thus "device padlock_rng" and "device rdrand_rng" should be
1091 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
1094 WITH_ICONV has been split into two feature sets. WITH_ICONV now
1095 enables just the iconv* functionality and is now on by default.
1096 WITH_LIBICONV_COMPAT enables the libiconv api and link time
1097 compatibility. Set WITHOUT_ICONV to build the old way.
1098 If you have been using WITH_ICONV before, you will very likely
1099 need to turn on WITH_LIBICONV_COMPAT.
1102 INVARIANTS option now enables DEBUG for code with OpenSolaris and
1103 Illumos origin, including ZFS. If you have INVARIANTS in your
1104 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
1106 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
1107 locks if WITNESS option was set. Because that generated a lot of
1108 witness(9) reports and all of them were believed to be false
1109 positives, this is no longer done. New option OPENSOLARIS_WITNESS
1110 can be used to achieve the previous behavior.
1113 Timer values in IPv6 data structures now use time_uptime instead
1114 of time_second. Although this is not a user-visible functional
1115 change, userland utilities which directly use them---ndp(8),
1116 rtadvd(8), and rtsold(8) in the base system---need to be updated
1117 to r253970 or later.
1120 find -delete can now delete the pathnames given as arguments,
1121 instead of only files found below them or if the pathname did
1122 not contain any slashes. Formerly, the following error message
1125 find: -delete: <path>: relative path potentially not safe
1127 Deleting the pathnames given as arguments can be prevented
1128 without error messages using -mindepth 1 or by changing
1129 directory and passing "." as argument to find. This works in the
1130 old as well as the new version of find.
1133 Behavior of devfs rules path matching has been changed.
1134 Pattern is now always matched against fully qualified devfs
1135 path and slash characters must be explicitly matched by
1136 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
1137 subdirectories must be reviewed.
1140 The default ARM ABI has changed to the ARM EABI. The old ABI is
1141 incompatible with the ARM EABI and all programs and modules will
1142 need to be rebuilt to work with a new kernel.
1144 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
1146 NOTE: Support for the old ABI will be removed in the future and
1147 users are advised to upgrade.
1150 pkg_install has been disconnected from the build if you really need it
1151 you should add WITH_PKGTOOLS in your src.conf(5).
1154 Most of network statistics structures were changed to be able
1155 keep 64-bits counters. Thus all tools, that work with networking
1156 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
1159 Fix a bug that allowed a tracing process (e.g. gdb) to write
1160 to a memory-mapped file in the traced process's address space
1161 even if neither the traced process nor the tracing process had
1162 write access to that file.
1165 CVS has been removed from the base system. An exact copy
1166 of the code is available from the devel/cvs port.
1169 Some people report the following error after the switch to bmake:
1171 make: illegal option -- J
1172 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
1174 *** [buildworld] Error code 2
1176 this likely due to an old instance of make in
1177 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
1178 which src/Makefile will use that blindly, if it exists, so if
1179 you see the above error:
1181 rm -rf `make -V MAKEPATH`
1186 Use bmake by default.
1187 Whereas before one could choose to build with bmake via
1188 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
1189 make. The goal is to remove these knobs for 10-RELEASE.
1191 It is worth noting that bmake (like gmake) treats the command
1192 line as the unit of failure, rather than statements within the
1193 command line. Thus '(cd some/where && dosomething)' is safer
1194 than 'cd some/where; dosomething'. The '()' allows consistent
1195 behavior in parallel build.
1198 Fix a bug that allows NFS clients to issue READDIR on files.
1201 The WITHOUT_IDEA option has been removed because
1202 the IDEA patent expired.
1205 The sysctl which controls TRIM support under ZFS has been renamed
1206 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
1210 The mergemaster command now uses the default MAKEOBJDIRPREFIX
1211 rather than creating it's own in the temporary directory in
1212 order allow access to bootstrapped versions of tools such as
1213 install and mtree. When upgrading from version of FreeBSD where
1214 the install command does not support -l, you will need to
1215 install a new mergemaster command if mergemaster -p is required.
1216 This can be accomplished with the command (cd src/usr.sbin/mergemaster
1220 Legacy ATA stack, disabled and replaced by new CAM-based one since
1221 FreeBSD 9.0, completely removed from the sources. Kernel modules
1222 atadisk and atapi*, user-level tools atacontrol and burncd are
1223 removed. Kernel option `options ATA_CAM` is now permanently enabled
1227 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
1228 and socketpair(2). Software, in particular Kerberos, may
1229 automatically detect and use these during building. The resulting
1230 binaries will not work on older kernels.
1233 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
1234 information, see the respective 20130304 entry).
1237 Recent commits to callout(9) changed the size of struct callout,
1238 so the KBI is probably heavily disturbed. Also, some functions
1239 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
1240 by macros. Every kernel module using it won't load, so rebuild
1243 The ctl device has been re-enabled in GENERIC for i386 and amd64,
1244 but does not initialize by default (because of the new CTL_DISABLE
1245 option) to save memory. To re-enable it, remove the CTL_DISABLE
1246 option from the kernel config file or set kern.cam.ctl.disable=0
1247 in /boot/loader.conf.
1250 The ctl device has been disabled in GENERIC for i386 and amd64.
1251 This was done due to the extra memory being allocated at system
1252 initialisation time by the ctl driver which was only used if
1253 a CAM target device was created. This makes a FreeBSD system
1254 unusable on 128MB or less of RAM.
1257 A new compression method (lz4) has been merged to -HEAD. Please
1258 refer to zpool-features(7) for more information.
1260 Please refer to the "ZFS notes" section of this file for information
1261 on upgrading boot ZFS pools.
1264 A BSD-licensed patch(1) variant has been added and is installed
1265 as bsdpatch, being the GNU version the default patch.
1266 To inverse the logic and use the BSD-licensed one as default,
1267 while having the GNU version installed as gnupatch, rebuild
1268 and install world with the WITH_BSD_PATCH knob set.
1271 Due to the use of the new -l option to install(1) during build
1272 and install, you must take care not to directly set the INSTALL
1273 make variable in your /etc/make.conf, /etc/src.conf, or on the
1274 command line. If you wish to use the -C flag for all installs
1275 you may be able to add INSTALL+=-C to /etc/make.conf or
1279 The install(1) option -M has changed meaning and now takes an
1280 argument that is a file or path to append logs to. In the
1281 unlikely event that -M was the last option on the command line
1282 and the command line contained at least two files and a target
1283 directory the first file will have logs appended to it. The -M
1284 option served little practical purpose in the last decade so its
1285 use is expected to be extremely rare.
1288 After switching to Clang as the default compiler some users of ZFS
1289 on i386 systems started to experience stack overflow kernel panics.
1290 Please consider using 'options KSTACK_PAGES=4' in such configurations.
1293 GEOM_LABEL now mangles label names read from file system metadata.
1294 Mangling affect labels containing spaces, non-printable characters,
1295 '%' or '"'. Device names in /etc/fstab and other places may need to
1299 By default, only the 10 most recent kernel dumps will be saved. To
1300 restore the previous behaviour (no limit on the number of kernel dumps
1301 stored in the dump directory) add the following line to /etc/rc.conf:
1306 With the addition of auditdistd(8), a new auditdistd user is now
1307 required during installworld. "mergemaster -p" can be used to
1308 add the user prior to installworld, as documented in the handbook.
1311 The sin6_scope_id member variable in struct sockaddr_in6 is now
1312 filled by the kernel before passing the structure to the userland via
1313 sysctl or routing socket. This means the KAME-specific embedded scope
1314 id in sin6_addr.s6_addr[2] is always cleared in userland application.
1315 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
1316 __FreeBSD_version is bumped to 1000025.
1319 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
1320 This means that the world and kernel will be compiled with clang
1321 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
1322 and /usr/bin/cpp. To disable this behavior and revert to building
1323 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
1324 of current may need to bootstrap WITHOUT_CLANG first if the clang
1325 build fails (its compatibility window doesn't extend to the 9 stable
1329 The IPFIREWALL_FORWARD kernel option has been removed. Its
1330 functionality now turned on by default.
1333 The ZERO_COPY_SOCKET kernel option has been removed and
1334 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
1335 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
1336 mechanism which is not safe and may result in kernel crashes.
1337 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
1338 driver supports disposeable external page sized mbuf storage.
1339 Proper replacements for both zero-copy mechanisms are under
1340 consideration and will eventually lead to complete removal
1341 of the two kernel options.
1344 The IPv4 network stack has been converted to network byte
1345 order. The following modules need to be recompiled together
1346 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
1347 pf(4), ipfw(4), ng_ipfw(4), stf(4).
1350 Support for non-MPSAFE filesystems was removed from VFS. The
1351 VFS_VERSION was bumped, all filesystem modules shall be
1355 All the non-MPSAFE filesystems have been disconnected from
1356 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
1357 portalfs, smbfs, xfs.
1360 The interface cloning API and ABI has changed. The following
1361 modules need to be recompiled together with kernel:
1362 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
1363 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
1364 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
1367 The sdhci driver was split in two parts: sdhci (generic SD Host
1368 Controller logic) and sdhci_pci (actual hardware driver).
1369 No kernel config modifications are required, but if you
1370 load sdhc as a module you must switch to sdhci_pci instead.
1373 Import the FUSE kernel and userland support into base system.
1376 The GNU sort(1) program has been removed since the BSD-licensed
1377 sort(1) has been the default for quite some time and no serious
1378 problems have been reported. The corresponding WITH_GNU_SORT
1382 The pfil(9) API/ABI for AF_INET family has been changed. Packet
1383 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
1387 The net80211(4) ABI has been changed to allow for improved driver
1388 PS-POLL and power-save support. All wireless drivers need to be
1389 recompiled to work with the new kernel.
1392 The random(4) support for the VIA hardware random number
1393 generator (`PADLOCK') is no longer enabled unconditionally.
1394 Add the padlock_rng device in the custom kernel config if
1395 needed. The GENERIC kernels on i386 and amd64 do include the
1396 device, so the change only affects the custom kernel
1400 The pf(4) packet filter ABI has been changed. pfctl(8) and
1401 snmp_pf module need to be recompiled to work with new kernel.
1404 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
1405 to -HEAD. Pools that have empty_bpobj in active state can not be
1406 imported read-write with ZFS implementations that do not support
1407 this feature. For more information read the zpool-features(5)
1411 The sparc64 ZFS loader has been changed to no longer try to auto-
1412 detect ZFS providers based on diskN aliases but now requires these
1413 to be explicitly listed in the OFW boot-device environment variable.
1416 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
1417 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
1418 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
1421 The following sysctls and tunables have been renamed for consistency
1422 with other variables:
1423 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
1424 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
1427 The sort utility has been replaced with BSD sort. For now, GNU sort
1428 is also available as "gnusort" or the default can be set back to
1429 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
1430 installed as "bsdsort".
1433 A new version of ZFS (pool version 5000) has been merged to -HEAD.
1434 Starting with this version the old system of ZFS pool versioning
1435 is superseded by "feature flags". This concept enables forward
1436 compatibility against certain future changes in functionality of ZFS
1437 pools. The first read-only compatible "feature flag" for ZFS pools
1438 is named "com.delphix:async_destroy". For more information
1439 read the new zpool-features(5) manual page.
1440 Please refer to the "ZFS notes" section of this file for information
1441 on upgrading boot ZFS pools.
1444 The malloc(3) implementation embedded in libc now uses sources imported
1445 as contrib/jemalloc. The most disruptive API change is to
1446 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
1447 delete it prior to installworld, and optionally re-create it using the
1448 new format after rebooting. See malloc.conf(5) for details
1449 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
1453 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
1454 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
1455 now spelled mips. This is to aid compatibility with third-party
1456 software that expects this naming scheme in uname(3). Little-endian
1457 settings are unchanged. If you are updating a big-endian mips64 machine
1458 from before this change, you may need to set MACHINE_ARCH=mips64 in
1459 your environment before the new build system will recognize your machine.
1462 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
1466 Now unix domain sockets behave "as expected" on nullfs(5). Previously
1467 nullfs(5) did not pass through all behaviours to the underlying layer,
1468 as a result if we bound to a socket on the lower layer we could connect
1469 only to the lower path; if we bound to the upper layer we could connect
1470 only to the upper path. The new behavior is one can connect to both the
1471 lower and the upper paths regardless what layer path one binds to.
1474 The getifaddrs upgrade path broken with 20111215 has been restored.
1475 If you have upgraded in between 20111215 and 20120209 you need to
1476 recompile libc again with your kernel. You still need to recompile
1477 world to be able to configure CARP but this restriction already
1478 comes from 20111215.
1481 The set_rcvar() function has been removed from /etc/rc.subr. All
1482 base and ports rc.d scripts have been updated, so if you have a
1483 port installed with a script in /usr/local/etc/rc.d you can either
1484 hand-edit the rcvar= line, or reinstall the port.
1486 An easy way to handle the mass-update of /etc/rc.d:
1487 rm /etc/rc.d/* && mergemaster -i
1490 panic(9) now stops other CPUs in the SMP systems, disables interrupts
1491 on the current CPU and prevents other threads from running.
1492 This behavior can be reverted using the kern.stop_scheduler_on_panic
1494 The new behavior can be incompatible with kern.sync_on_panic.
1497 The carp(4) facility has been changed significantly. Configuration
1498 of the CARP protocol via ifconfig(8) has changed, as well as format
1499 of CARP events submitted to devd(8) has changed. See manual pages
1500 for more information. The arpbalance feature of carp(4) is currently
1501 not supported anymore.
1503 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
1504 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
1505 need to be recompiled.
1508 The acpi_wmi(4) status device /dev/wmistat has been renamed to
1512 The option VFS_ALLOW_NONMPSAFE option has been added in order to
1513 explicitely support non-MPSAFE filesystems.
1514 It is on by default for all supported platform at this present
1518 The broken amd(4) driver has been replaced with esp(4) in the amd64,
1519 i386 and pc98 GENERIC kernel configuration files.
1522 sysinstall has been removed
1525 The stable/9 branch created in subversion. This corresponds to the
1526 RELENG_9 branch in CVS.
1532 Avoid using make -j when upgrading. While generally safe, there are
1533 sometimes problems using -j to upgrade. If your upgrade fails with
1534 -j, please try again without -j. From time to time in the past there
1535 have been problems using -j with buildworld and/or installworld. This
1536 is especially true when upgrading between "distant" versions (eg one
1537 that cross a major release boundary or several minor releases, or when
1538 several months have passed on the -current branch).
1540 Sometimes, obscure build problems are the result of environment
1541 poisoning. This can happen because the make utility reads its
1542 environment when searching for values for global variables. To run
1543 your build attempts in an "environmental clean room", prefix all make
1544 commands with 'env -i '. See the env(1) manual page for more details.
1546 When upgrading from one major version to another it is generally best
1547 to upgrade to the latest code in the currently installed branch first,
1548 then do an upgrade to the new branch. This is the best-tested upgrade
1549 path, and has the highest probability of being successful. Please try
1550 this approach before reporting problems with a major version upgrade.
1552 When upgrading a live system, having a root shell around before
1553 installing anything can help undo problems. Not having a root shell
1554 around can lead to problems if pam has changed too much from your
1555 starting point to allow continued authentication after the upgrade.
1557 This file should be read as a log of events. When a later event changes
1558 information of a prior event, the prior event should not be deleted.
1559 Instead, a pointer to the entry with the new information should be
1560 placed in the old entry. Readers of this file should also sanity check
1561 older entries before relying on them blindly. Authors of new entries
1562 should write them with this in mind.
1566 When upgrading the boot ZFS pool to a new version, always follow
1569 1.) recompile and reinstall the ZFS boot loader and boot block
1570 (this is part of "make buildworld" and "make installworld")
1572 2.) update the ZFS boot block on your boot drive
1574 The following example updates the ZFS boot block on the first
1575 partition (freebsd-boot) of a GPT partitioned drive ada0:
1576 "gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1578 Non-boot pools do not need these updates.
1582 If you are updating from a prior version of FreeBSD (even one just
1583 a few days old), you should follow this procedure. It is the most
1584 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1586 make kernel-toolchain
1587 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1588 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1590 To test a kernel once
1591 ---------------------
1592 If you just want to boot a kernel once (because you are not sure
1593 if it works, or if you want to boot a known bad kernel to provide
1594 debugging information) run
1595 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1596 nextboot -k testkernel
1598 To just build a kernel when you know that it won't mess you up
1599 --------------------------------------------------------------
1600 This assumes you are already running a CURRENT system. Replace
1601 ${arch} with the architecture of your machine (e.g. "i386",
1602 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1604 cd src/sys/${arch}/conf
1605 config KERNEL_NAME_HERE
1606 cd ../compile/KERNEL_NAME_HERE
1611 If this fails, go to the "To build a kernel" section.
1613 To rebuild everything and install it on the current system.
1614 -----------------------------------------------------------
1615 # Note: sometimes if you are running current you gotta do more than
1616 # is listed here if you are upgrading from a really old current.
1618 <make sure you have good level 0 dumps>
1620 make kernel KERNCONF=YOUR_KERNEL_HERE
1622 <reboot in single user> [3]
1629 To cross-install current onto a separate partition
1630 --------------------------------------------------
1631 # In this approach we use a separate partition to hold
1632 # current's root, 'usr', and 'var' directories. A partition
1633 # holding "/", "/usr" and "/var" should be about 2GB in
1636 <make sure you have good level 0 dumps>
1639 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1640 <maybe newfs current's root partition>
1641 <mount current's root partition on directory ${CURRENT_ROOT}>
1642 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1643 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1644 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1645 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1646 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1647 <reboot into current>
1648 <do a "native" rebuild/install as described in the previous section>
1649 <maybe install compatibility libraries from ports/misc/compat*>
1653 To upgrade in-place from stable to current
1654 ----------------------------------------------
1655 <make sure you have good level 0 dumps>
1657 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1659 <reboot in single user> [3]
1666 Make sure that you've read the UPDATING file to understand the
1667 tweaks to various things you need. At this point in the life
1668 cycle of current, things change often and you are on your own
1669 to cope. The defaults can also change, so please read ALL of
1670 the UPDATING entries.
1672 Also, if you are tracking -current, you must be subscribed to
1673 freebsd-current@freebsd.org. Make sure that before you update
1674 your sources that you have read and understood all the recent
1675 messages there. If in doubt, please track -stable which has
1676 much fewer pitfalls.
1678 [1] If you have third party modules, such as vmware, you
1679 should disable them at this point so they don't crash your
1682 [3] From the bootblocks, boot -s, and then do
1687 adjkerntz -i # if CMOS is wall time
1688 Also, when doing a major release upgrade, it is required that
1689 you boot into single user mode to do the installworld.
1691 [4] Note: This step is non-optional. Failure to do this step
1692 can result in a significant reduction in the functionality of the
1693 system. Attempting to do it by hand is not recommended and those
1694 that pursue this avenue should read this file carefully, as well
1695 as the archives of freebsd-current and freebsd-hackers mailing lists
1696 for potential gotchas. The -U option is also useful to consider.
1697 See mergemaster(8) for more information.
1699 [5] Usually this step is a noop. However, from time to time
1700 you may need to do this if you get unknown user in the following
1701 step. It never hurts to do it all the time. You may need to
1702 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1703 install) after the buildworld before this step if you last updated
1704 from current before 20130425 or from -stable before 20130430.
1706 [6] This only deletes old files and directories. Old libraries
1707 can be deleted by "make delete-old-libs", but you have to make
1708 sure that no program is using those libraries anymore.
1710 [8] In order to have a kernel that can run the 4.x binaries needed to
1711 do an installworld, you must include the COMPAT_FREEBSD4 option in
1712 your kernel. Failure to do so may leave you with a system that is
1713 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1714 required to run the 5.x binaries on more recent kernels. And so on
1715 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1717 Make sure that you merge any new devices from GENERIC since the
1718 last time you updated your kernel config file.
1720 [9] When checking out sources, you must include the -P flag to have
1721 cvs prune empty directories.
1723 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1724 "?=" instead of the "=" assignment operator, so that buildworld can
1725 override the CPUTYPE if it needs to.
1727 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1728 not on the command line, or in /etc/make.conf. buildworld will
1729 warn if it is improperly defined.
1732 This file contains a list, in reverse chronological order, of major
1733 breakages in tracking -current. It is not guaranteed to be a complete
1734 list of such breakages, and only contains entries since September 23, 2011.
1735 If you need to see UPDATING entries from before that date, you will need
1736 to fetch an UPDATING file from an older FreeBSD release.
1738 Copyright information:
1740 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1742 Redistribution, publication, translation and use, with or without
1743 modification, in full or in part, in any form or format of this
1744 document are permitted without further permission from the author.
1746 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1747 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1748 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1749 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1750 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1751 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1752 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1753 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1754 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1755 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1756 POSSIBILITY OF SUCH DAMAGE.
1758 Contact Warner Losh if you have any questions about your use of