xref: /freebsd/UPDATING (revision 9cdd5c07ad924249d620437d00458c3b6434dbe5)
1 Updating Information for FreeBSD current users.
2
3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4See end of file for further details.  For commonly done items, please see the
5COMMON ITEMS: section later in the file.  These instructions assume that you
6basically know what you are doing.  If not, then please consult the FreeBSD
7handbook:
8
9    https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
10
11Items affecting the ports and packages system can be found in
12/usr/ports/UPDATING.  Please read that file before running portupgrade.
13
14NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15from older versions of FreeBSD, try WITHOUT_CLANG and WITH_GCC to bootstrap to
16the tip of head, and then rebuild without this option. The bootstrap process
17from older version of current across the gcc/clang cutover is a bit fragile.
18
19NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW:
20	FreeBSD 13.x has many debugging features turned on, in both the kernel
21	and userland.  These features attempt to detect incorrect use of
22	system primitives, and encourage loud failure through extra sanity
23	checking and fail stop semantics.  They also substantially impact
24	system performance.  If you want to do performance measurement,
25	benchmarking, and optimization, you'll want to turn them off.  This
26	includes various WITNESS- related kernel options, INVARIANTS, malloc
27	debugging flags in userland, and various verbose features in the
28	kernel.  Many developers choose to disable these features on build
29	machines to maximize performance.  (To completely disable malloc
30	debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31	disable the most expensive debugging functionality run
32	"ln -s 'abort:false,junk:false' /etc/malloc.conf".)
33
3420190404:
35	r345895 reverts r320698. This implies that an nfsuserd(8) daemon
36	built from head sources between r320757 (July 6, 2017) and
37	r338192 (Aug. 22, 2018) will not work unless the "-use-udpsock"
38	is added to the command line.
39	nfsuserd daemons built from head sources that are post-r338192 are
40	not affected and should continue to work.
41
4220190320:
43	The fuse(4) module has been renamed to fusefs(4) for consistency with
44	other filesystems.  You should update any kld_load="fuse" entries in
45	/etc/rc.conf, fuse_load="YES" entries in /boot/loader.conf, and
46	"options FUSE" enties in kernel config files.
47
4820190304:
49	Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
50	8.0.0.  Please see the 20141231 entry below for information about
51	prerequisites and upgrading, if you are not already using clang 3.5.0
52	or higher.
53
5420190226:
55	geom_uzip(4) depends on the new module xz.  If geom_uzip is statically
56	compiled into your custom kernel, add 'device xz' statement to the
57	kernel config.
58
5920190219:
60	drm and drm2 have been removed from the tree. Please see
61	https://wiki.freebsd.org/Graphics for the latest information on
62	migrating to the drm ports.
63
6420190131:
65	Iflib is no longer unconditionally compiled into the kernel.  Drivers
66	using iflib and statically compiled into the kernel, now require
67	the 'device iflib' config option.  For the same drivers loaded as
68	modules on kernels not having 'device iflib', the iflib.ko module
69	is loaded automatically.
70
7120190125:
72	The IEEE80211_AMPDU_AGE and AH_SUPPORT_AR5416 kernel configuration
73	options no longer exist since r343219 and r343427 respectively;
74	nothing uses them, so they should be just removed from custom
75	kernel config files.
76
7720181230:
78	r342635 changes the way efibootmgr(8) works by requiring users to add
79	the -b (bootnum) parameter for commands where the bootnum was previously
80	specified with each option. For example 'efibootmgr -B 0001' is now
81	'efibootmgr -B -b 0001'.
82
8320181220:
84	r342286 modifies the NFSv4 server so that it obeys vfs.nfsd.nfs_privport
85	in the same as it is applied to NFSv2 and 3.  This implies that NFSv4
86	servers that have vfs.nfsd.nfs_privport set will only allow mounts
87	from clients using a reserved port#. Since both the FreeBSD and Linux
88	NFSv4 clients use reserved port#s by default, this should not affect
89	most NFSv4 mounts.
90
9120181219:
92	The XLP config has been removed. We can't support 64-bit atomics in this
93	kernel because it is running in 32-bit mode. XLP users must transition
94	to running a 64-bit kernel (XLP64 or XLPN32).
95
96	The mips GXEMUL support has been removed from FreeBSD. MALTA* + qemu is
97	the preferred emulator today and we don't need two different ones.
98
99	The old sibyte / swarm / Broadcom BCM1250 support has been
100	removed from the mips port.
101
10220181211:
103	Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
104	7.0.1.  Please see the 20141231 entry below for information about
105	prerequisites and upgrading, if you are not already using clang 3.5.0
106	or higher.
107
10820181211:
109	Remove the timed and netdate programs from the base tree.  Setting
110	the time with these deamons has been obsolete for over a decade.
111
11220181126:
113	On amd64, arm64 and armv7 (architectures that install LLVM's ld.lld
114	linker as /usr/bin/ld) GNU ld is no longer installed as ld.bfd, as
115	it produces broken binaries when ifuncs are in use.  Users needing
116	GNU ld should install the binutils port or package.
117
11820181123:
119	The BSD crtbegin and crtend code has been enabled by default. It has
120	had extensive testing on amd64, arm64, and i386. It can be disabled
121	by building a world with -DWITHOUT_BSD_CRTBEGIN.
122
12320181115:
124	The set of CTM commands (ctm, ctm_smail, ctm_rmail, ctm_dequeue)
125	has been converted to a port (misc/ctm) and will be removed from
126	FreeBSD-13.  It is available as a package (ctm) for all supported
127	FreeBSD versions.
128
12920181110:
130	The default newsyslog.conf(5) file has been changed to only include
131	files in /etc/newsyslog.conf.d/ and /usr/local/etc/newsyslog.conf.d/ if
132	the filenames end in '.conf' and do not begin with a '.'.
133
134	You should check the configuration files in these two directories match
135	this naming convention. You can verify which configuration files are
136	being included using the command:
137		$ newsyslog -Nrv
138
13920181015:
140	Ports for the DRM modules have been simplified. Now, amd64 users should
141	just install the drm-kmod port. All others should install
142	drm-legacy-kmod.
143
144	Graphics hardware that's newer than about 2010 usually works with
145	drm-kmod.  For hardware older than 2013, however, some users will need
146	to use drm-legacy-kmod if drm-kmod doesn't work for them. Hardware older
147	than 2008 usually only works in drm-legacy-kmod. The graphics team can
148	only commit to hardware made since 2013 due to the complexity of the
149	market and difficulty to test all the older cards effectively. If you
150	have hardware supported by drm-kmod, you are strongly encouraged to use
151	that as you will get better support.
152
153	Other than KPI chasing, drm-legacy-kmod will not be updated. As outlined
154	elsewhere, the drm and drm2 modules will be eliminated from the src base
155	soon (with a limited exception for arm). Please update to the package
156	asap and report any issues to x11@freebsd.org.
157
158	Generally, anybody using the drm*-kmod packages should add
159	WITHOUT_DRM_MODULE=t and WITHOUT_DRM2_MODULE=t to avoid nasty
160	cross-threading surprises, especially with automatic driver
161	loading from X11 startup. These will become the defaults in 13-current
162	shortly.
163
16420181012:
165	The ixlv(4) driver has been renamed to iavf(4).  As a consequence,
166	custom kernel and module loading configuration files must be updated
167	accordingly.  Moreover, interfaces previous presented as ixlvN to the
168	system are now exposed as iavfN and network configuration files must
169	be adjusted as necessary.
170
17120181009:
172	OpenSSL has been updated to version 1.1.1.  This update included
173	additional various API changes througout the base system.  It is
174	important to rebuild third-party software after upgrading.  The value
175	of __FreeBSD_version has been bumped accordingly.
176
17720181006:
178	The legacy DRM modules and drivers have now been added to the loader's
179	module blacklist, in favor of loading them with kld_list in rc.conf(5).
180	The module blacklist may be overridden with the loader.conf(5)
181	'module_blacklist' variable, but loading them via rc.conf(5) is strongly
182	encouraged.
183
18420181002:
185	The cam(4) based nda(4) driver will be used over nvd(4) by default on
186	powerpc64. You may set 'options NVME_USE_NVD=1' in your kernel conf or
187	loader tunable 'hw.nvme.use_nvd=1' if you wish to use the existing
188	driver.  Make sure to edit /boot/etc/kboot.conf and fstab to use the
189	nda device name.
190
19120180913:
192	Reproducible build mode is now on by default, in preparation for
193	FreeBSD 12.0.  This eliminates build metadata such as the user,
194	host, and time from the kernel (and uname), unless the working tree
195	corresponds to a modified checkout from a version control system.
196	The previous behavior can be obtained by setting the /etc/src.conf
197	knob WITHOUT_REPRODUCIBLE_BUILD.
198
19920180826:
200	The Yarrow CSPRNG has been removed from the kernel as it has not been
201	supported by its designers since at least 2003. Fortuna has been the
202	default since FreeBSD-11.
203
20420180822:
205	devctl freeze/thaw have gone into the tree, the rc scripts have been
206	updated to use them and devmatch has been changed.  You should update
207	kernel, userland and rc scripts all at the same time.
208
20920180818:
210	The default interpreter has been switched from 4th to Lua.
211	LOADER_DEFAULT_INTERP, documented in build(7), will override the default
212	interpreter.  If you have custom FORTH code you will need to set
213	LOADER_DEFAULT_INTERP=4th (valid values are 4th, lua or simp) in
214	src.conf for the build.  This will create default hard links between
215	loader and loader_4th instead of loader and loader_lua, the new default.
216	If you are using UEFI it will create the proper hard link to loader.efi.
217
218	bhyve uses userboot.so. It remains 4th-only until some issues are solved
219	regarding coexisting with multiple versions of FreeBSD are resolved.
220
22120180815:
222	ls(1) now respects the COLORTERM environment variable used in other
223	systems and software to indicate that a colored terminal is both
224	supported and desired.  If ls(1) is suddenly emitting colors, they may
225	be disabled again by either removing the unwanted COLORTERM from your
226	environment, or using `ls --color=never`.  The ls(1) specific CLICOLOR
227	may not be observed in a future release.
228
22920180808:
230	The default pager for most commands has been changed to "less".  To
231	restore the old behavior, set PAGER="more" and MANPAGER="more -s" in
232	your environment.
233
23420180731:
235	The jedec_ts(4) driver has been removed. A superset of its functionality
236	is available in the jedec_dimm(4) driver, and the manpage for that
237	driver includes migration instructions. If you have "device jedec_ts"
238	in your kernel configuration file, it must be removed.
239
24020180730:
241	amd64/GENERIC now has EFI runtime services, EFIRT, enabled by default.
242	This should have no effect if the kernel is booted via BIOS/legacy boot.
243	EFIRT may be disabled via a loader tunable, efi.rt.disabled, if a system
244	has a buggy firmware that prevents a successful boot due to use of
245	runtime services.
246
24720180727:
248	Atmel AT91RM9200 and AT91SAM9, Cavium CNS 11xx and XScale
249	support has been removed from the tree. These ports were
250	obsolete and/or known to be broken for many years.
251
25220180723:
253	loader.efi has been augmented to participate more fully in the
254	UEFI boot manager protocol. loader.efi will now look at the
255	BootXXXX environment variable to determine if a specific kernel
256	or root partition was specified. XXXX is derived from BootCurrent.
257	efibootmgr(8) manages these standard UEFI variables.
258
25920180720:
260	zfsloader's functionality has now been folded into loader.
261	zfsloader is no longer necessary once you've updated your
262	boot blocks. For a transition period, we will install a
263	hardlink for zfsloader to loader to allow a smooth transition
264	until the boot blocks can be updated (hard link because old
265	zfs boot blocks don't understand symlinks).
266
26720180719:
268	ARM64 now have efifb support, if you want to have serial console
269	on your arm64 board when an screen is connected and the bootloader
270	setup a framebuffer for us to use, just add :
271	boot_serial=YES
272	boot_multicons=YES
273	in /boot/loader.conf
274	For Raspberry Pi 3 (RPI) users, this is needed even if you don't have
275	an screen connected as the firmware will setup a framebuffer are that
276	u-boot will expose as an EFI framebuffer.
277
27820180719:
279	New uid:gid added, ntpd:ntpd (123:123).  Be sure to run mergemaster
280	or take steps to update /etc/passwd before doing installworld on
281	existing systems.  Do not skip the "mergemaster -Fp" step before
282	installworld, as described in the update procedures near the bottom
283	of this document.  Also, rc.d/ntpd now starts ntpd(8) as user ntpd
284	if the new mac_ntpd(4) policy is available, unless ntpd_flags or
285	the ntp config file contain options that change file/dir locations.
286	When such options (e.g., "statsdir" or "crypto") are used, ntpd can
287	still be run as non-root by setting ntpd_user=ntpd in rc.conf, after
288	taking steps to ensure that all required files/dirs are accessible
289	by the ntpd user.
290
29120180717:
292	Big endian arm support has been removed.
293
29420180711:
295	The static environment setup in kernel configs is no longer mutually
296	exclusive with the loader(8) environment by default.  In order to
297	restore the previous default behavior of disabling the loader(8)
298	environment if a static environment is present, you must specify
299	loader_env.disabled=1 in the static environment.
300
30120180705:
302	The ABI of syscalls used by management tools like sockstat and
303	netstat has been broken to allow 32-bit binaries to work on
304	64-bit kernels without modification.  These programs will need
305	to match the kernel in order to function.  External programs may
306	require minor modifications to accommodate a change of type in
307	structures from pointers to 64-bit virtual addresses.
308
30920180702:
310	On i386 and amd64 atomics are now inlined. Out of tree modules using
311	atomics will need to be rebuilt.
312
31320180701:
314	The '%I' format in the kern.corefile sysctl limits the number of
315	core files that a process can generate to the number stored in the
316	debug.ncores sysctl. The '%I' format is replaced by the single digit
317	index. Previously, if all indexes were taken the kernel would overwrite
318	only a core file with the highest index in a filename.
319	Currently the system will create a new core file if there is a free
320	index or if all slots are taken it will overwrite the oldest one.
321
32220180630:
323	Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
324	6.0.1.  Please see the 20141231 entry below for information about
325	prerequisites and upgrading, if you are not already using clang 3.5.0
326	or higher.
327
32820180628:
329	r335753 introduced a new quoting method. However, etc/devd/devmatch.conf
330	needed to be changed to work with it. This change was made with r335763
331	and requires a mergemaster / etcupdate / etc to update the installed
332	file.
333
33420180612:
335	r334930 changed the interface between the NFS modules, so they all
336	need to be rebuilt.  r335018 did a __FreeBSD_version bump for this.
337
33820180530:
339	As of r334391 lld is the default amd64 system linker; it is installed
340	as /usr/bin/ld.  Kernel build workarounds (see 20180510 entry) are no
341	longer necessary.
342
34320180530:
344	The kernel / userland interface for devinfo changed, so you'll
345	need a new kernel and userland as a pair for it to work (rebuilding
346	lib/libdevinfo is all that's required). devinfo and devmatch will
347	not work, but everything else will when there's a mismatch.
348
34920180523:
350	The on-disk format for hwpmc callchain records has changed to include
351	threadid corresponding to a given record. This changes the field offsets
352	and thus requires that libpmcstat be rebuilt before using a kernel
353	later than r334108.
354
35520180517:
356	The vxge(4) driver has been removed.  This driver was introduced into
357	HEAD one week before the Exar left the Ethernet market and is not
358	known to be used.  If you have device vxge in your kernel config file
359	it must be removed.
360
36120180510:
362	The amd64 kernel now requires a ld that supports ifunc to produce a
363	working kernel, either lld or a newer binutils. lld is built by default
364	on amd64, and the 'buildkernel' target uses it automatically. However,
365	it is not the default linker, so building the kernel the traditional
366	way requires LD=ld.lld on the command line (or LD=/usr/local/bin/ld for
367	binutils port/package). lld will soon be default, and this requirement
368	will go away.
369
370	NOTE: As of r334391 lld is the default system linker on amd64, and no
371	workaround is necessary.
372
37320180508:
374	The nxge(4) driver has been removed.  This driver was for PCI-X 10g
375	cards made by s2io/Neterion.  The company was aquired by Exar and
376	no longer sells or supports Ethernet products.  If you have device
377	nxge in your kernel config file it must be removed.
378
37920180504:
380	The tz database (tzdb) has been updated to 2018e.  This version more
381	correctly models time stamps in time zones with negative DST such as
382	Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
383	Africa/Windhoek (1994/2017).  This does not affect the UT offsets, only
384	time zone abbreviations and the tm_isdst flag.
385
38620180502:
387	The ixgb(4) driver has been removed.  This driver was for an early and
388	uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel
389	quickly shifted to the long lived ixgbe family.  If you have device
390	ixgb in your kernel config file it must be removed.
391
39220180501:
393	The lmc(4) driver has been removed.  This was a WAN interface
394	card that was already reportedly rare in 2003, and had an ambiguous
395	license.  If you have device lmc in your kernel config file it must
396	be removed.
397
39820180413:
399	Support for Arcnet networks has been removed.  If you have device
400	arcnet or device cm in your kernel config file they must be
401	removed.
402
40320180411:
404	Support for FDDI networks has been removed.  If you have device
405	fddi or device fpa in your kernel config file they must be
406	removed.
407
40820180406:
409	In addition to supporting RFC 3164 formatted messages, the
410	syslogd(8) service is now capable of parsing RFC 5424 formatted
411	log messages. The main benefit of using RFC 5424 is that clients
412	may now send log messages with timestamps containing year numbers,
413	microseconds and time zone offsets.
414
415	Similarly, the syslog(3) C library function has been altered to
416	send RFC 5424 formatted messages to the local system logging
417	daemon. On systems using syslogd(8), this change should have no
418	negative impact, as long as syslogd(8) and the C library are
419	updated at the same time. On systems using a different system
420	logging daemon, it may be necessary to make configuration
421	adjustments, depending on the software used.
422
423	When using syslog-ng, add the 'syslog-protocol' flag to local
424	input sources to enable parsing of RFC 5424 formatted messages:
425
426		source src {
427			unix-dgram("/var/run/log" flags(syslog-protocol));
428		}
429
430	When using rsyslog, disable the 'SysSock.UseSpecialParser' option
431	of the 'imuxsock' module to let messages be processed by the
432	regular RFC 3164/5424 parsing pipeline:
433
434		module(load="imuxsock" SysSock.UseSpecialParser="off")
435
436	Do note that these changes only affect communication between local
437	applications and syslogd(8). The format that syslogd(8) uses to
438	store messages on disk or forward messages to other systems
439	remains unchanged. syslogd(8) still uses RFC 3164 for these
440	purposes. Options to customize this behaviour will be added in the
441	future. Utilities that process log files stored in /var/log are
442	thus expected to continue to function as before.
443
444	__FreeBSD_version has been incremented to 1200061 to denote this
445	change.
446
44720180328:
448	Support for token ring networks has been removed. If you
449	have "device token" in your kernel config you should remove
450	it. No device drivers supported token ring.
451
45220180323:
453	makefs was modified to be able to tag ISO9660 El Torito boot catalog
454	entries as EFI instead of overloading the i386 tag as done previously.
455	The amd64 mkisoimages.sh script used to build amd64 ISO images for
456	release was updated to use this. This may mean that makefs must be
457	updated before "make cdrom" can be run in the release directory. This
458	should be as simple as:
459
460		$ cd $SRCDIR/usr.sbin/makefs
461		$ make depend all install
462
46320180212:
464	FreeBSD boot loader enhanced with Lua scripting. It's purely opt-in for
465	now by building WITH_LOADER_LUA and WITHOUT_FORTH in /etc/src.conf.
466	Co-existance for the transition period will come shortly. Booting is a
467	complex environment and test coverage for Lua-enabled loaders has been
468	thin, so it would be prudent to assume it might not work and make
469	provisions for backup boot methods.
470
47120180211:
472	devmatch functionality has been turned on in devd. It will automatically
473	load drivers for unattached devices. This may cause unexpected drivers
474	to be loaded. Please report any problems to current@ and
475	imp@freebsd.org.
476
47720180114:
478	Clang, llvm, lld, lldb, compiler-rt and libc++ have been upgraded to
479	6.0.0.  Please see the 20141231 entry below for information about
480	prerequisites and upgrading, if you are not already using clang 3.5.0
481	or higher.
482
48320180110:
484	LLVM's lld linker is now used as the FreeBSD/amd64 bootstrap linker.
485	This means it is used to link the kernel and userland libraries and
486	executables, but is not yet installed as /usr/bin/ld by default.
487
488	To revert to ld.bfd as the bootstrap linker, in /etc/src.conf set
489        WITHOUT_LLD_BOOTSTRAP=yes
490
49120180110:
492	On i386, pmtimer has been removed. Its functionality has been folded
493	into apm. It was a no-op on ACPI in current for a while now (but was
494	still needed on i386 in FreeBSD 11 and earlier). Users may need to
495	remove it from kernel config files.
496
49720180104:
498	The use of RSS hash from the network card aka flowid has been
499	disabled by default for lagg(4) as it's currently incompatible with
500	the lacp and loadbalance protocols.
501
502	This can be re-enabled by setting the following in loader.conf:
503	net.link.lagg.default_use_flowid="1"
504
50520180102:
506	The SW_WATCHDOG option is no longer necessary to enable the
507	hardclock-based software watchdog if no hardware watchdog is
508	configured. As before, SW_WATCHDOG will cause the software
509	watchdog to be enabled even if a hardware watchdog is configured.
510
51120171215:
512	r326887 fixes the issue described in the 20171214 UPDATING entry.
513	r326888 flips the switch back to building GELI support always.
514
51520171214:
516	r362593 broke ZFS + GELI support for reasons unknown. However,
517	it also broke ZFS support generally, so GELI has been turned off
518	by default as the lesser evil in r326857. If you boot off ZFS and/or
519	GELI, it might not be a good time to update.
520
52120171125:
522	PowerPC users must update loader(8) by rebuilding world before
523	installing a new kernel, as the protocol connecting them has
524	changed. Without the update, loader metadata will not be passed
525	successfully to the kernel and users will have to enter their
526	root partition at the kernel mountroot prompt to continue booting.
527	Newer versions of loader can boot old kernels without issue.
528
52920171110:
530	The LOADER_FIREWIRE_SUPPORT build variable as been renamed to
531	WITH/OUT_LOADER_FIREWIRE. LOADER_{NO_,}GELI_SUPPORT has been renamed
532	to WITH/OUT_LOADER_GELI.
533
53420171106:
535	The naive and non-compliant support of posix_fallocate(2) in ZFS
536	has been removed as of r325320.  The system call now returns EINVAL
537	when used on a ZFS file.  Although the new behavior complies with the
538	standard, some consumers are not prepared to cope with it.
539	One known victim is lld prior to r325420.
540
54120171102:
542	Building in a FreeBSD src checkout will automatically create object
543	directories now rather than store files in the current directory if
544	'make obj' was not ran.  Calling 'make obj' is no longer necessary.
545	This feature can be disabled by setting WITHOUT_AUTO_OBJ=yes in
546	/etc/src-env.conf (not /etc/src.conf), or passing the option in the
547	environment.
548
54920171101:
550	The default MAKEOBJDIR has changed from /usr/obj/<srcdir> for native
551	builds, and /usr/obj/<arch>/<srcdir> for cross-builds, to a unified
552	/usr/obj/<srcdir>/<arch>.  This behavior can be changed to the old
553	format by setting WITHOUT_UNIFIED_OBJDIR=yes in /etc/src-env.conf,
554	the environment, or with -DWITHOUT_UNIFIED_OBJDIR when building.
555	The UNIFIED_OBJDIR option is a transitional feature that will be
556	removed for 12.0 release; please migrate to the new format for any
557	tools by looking up the OBJDIR used by 'make -V .OBJDIR' means rather
558	than hardcoding paths.
559
56020171028:
561	The native-xtools target no longer installs the files by default to the
562	OBJDIR.  Use the native-xtools-install target with a DESTDIR to install
563	to ${DESTDIR}/${NXTP} where NXTP defaults to /nxb-bin.
564
56520171021:
566	As part of the boot loader infrastructure cleanup, LOADER_*_SUPPORT
567	options are changing from controlling the build if defined / undefined
568	to controlling the build with explicit 'yes' or 'no' values. They will
569	shift to WITH/WITHOUT options to match other options in the system.
570
57120171010:
572	libstand has turned into a private library for sys/boot use only.
573	It is no longer supported as a public interface outside of sys/boot.
574
57520171005:
576	The arm port has split armv6 into armv6 and armv7. armv7 is now
577	a valid TARGET_ARCH/MACHINE_ARCH setting. If you have an armv7 system
578	and are running a kernel from before r324363, you will need to add
579	MACHINE_ARCH=armv7 to 'make buildworld' to do a native build.
580
58120171003:
582	When building multiple kernels using KERNCONF, non-existent KERNCONF
583	files will produce an error and buildkernel will fail. Previously
584	missing KERNCONF files silently failed giving no indication as to
585	why, only to subsequently discover during installkernel that the
586	desired kernel was never built in the first place.
587
58820170912:
589	The default serial number format for CTL LUNs has changed.  This will
590	affect users who use /dev/diskid/* device nodes, or whose FibreChannel
591	or iSCSI clients care about their LUNs' serial numbers.  Users who
592	require serial number stability should hardcode serial numbers in
593	/etc/ctl.conf .
594
59520170912:
596	For 32-bit arm compiled for hard-float support, soft-floating point
597	binaries now always get their shared libraries from
598	LD_SOFT_LIBRARY_PATH (in the past, this was only used if
599	/usr/libsoft also existed). Only users with a hard-float ld.so, but
600	soft-float everything else should be affected.
601
60220170826:
603	The geli password typed at boot is now hidden.  To restore the previous
604	behavior, see geli(8) for configuration options.
605
60620170825:
607	Move PMTUD blackhole counters to TCPSTATS and remove them from bare
608	sysctl values.  Minor nit, but requires a rebuild of both world/kernel
609	to complete.
610
61120170814:
612	"make check" behavior (made in ^/head@r295380) has been changed to
613	execute from a limited sandbox, as opposed to executing from
614	${TESTSDIR}.
615
616	Behavioral changes:
617	- The "beforecheck" and "aftercheck" targets are now specified.
618	- ${CHECKDIR} (added in commit noted above) has been removed.
619	- Legacy behavior can be enabled by setting
620	  WITHOUT_MAKE_CHECK_USE_SANDBOX in src.conf(5) or the environment.
621
622	If the limited sandbox mode is enabled, "make check" will execute
623	"make distribution", then install, execute the tests, and clean up the
624	sandbox if successful.
625
626	The "make distribution" and "make install" targets are typically run as
627	root to set appropriate permissions and ownership at installation time.
628	The end-user should set "WITH_INSTALL_AS_USER" in src.conf(5) or the
629	environment if executing "make check" with limited sandbox mode using
630	an unprivileged user.
631
63220170808:
633	Since the switch to GPT disk labels, fsck for UFS/FFS has been
634	unable to automatically find alternate superblocks. As of r322297,
635	the information needed to find alternate superblocks has been
636	moved to the end of the area reserved for the boot block.
637	Filesystems created with a newfs of this vintage or later
638	will create the recovery information. If you have a filesystem
639	created prior to this change and wish to have a recovery block
640	created for your filesystem, you can do so by running fsck in
641	foreground mode (i.e., do not use the -p or -y options). As it
642	starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
643	to which you should answer yes.
644
64520170728:
646	As of r321665, an NFSv4 server configuration that services
647	Kerberos mounts or clients that do not support the uid/gid in
648	owner/owner_group string capability, must explicitly enable
649	the nfsuserd daemon by adding nfsuserd_enable="YES" to the
650	machine's /etc/rc.conf file.
651
65220170722:
653	Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 5.0.0.
654	Please see the 20141231 entry below for information about prerequisites
655	and upgrading, if you are not already using clang 3.5.0 or higher.
656
65720170701:
658	WITHOUT_RCMDS is now the default. Set WITH_RCMDS if you need the
659	r-commands (rlogin, rsh, etc.) to be built with the base system.
660
66120170625:
662	The FreeBSD/powerpc platform now uses a 64-bit type for time_t.  This is
663	a very major ABI incompatible change, so users of FreeBSD/powerpc must
664	be careful when performing source upgrades.  It is best to run
665	'make installworld' from an alternate root system, either a live
666	CD/memory stick, or a temporary root partition.  Additionally, all ports
667	must be recompiled.  powerpc64 is largely unaffected, except in the case
668	of 32-bit compatibility.  All 32-bit binaries will be affected.
669
67020170623:
671	Forward compatibility for the "ino64" project have been committed. This
672	will allow most new binaries to run on older kernels in a limited
673	fashion.  This prevents many of the common foot-shooting actions in the
674	upgrade as well as the limited ability to roll back the kernel across
675	the ino64 upgrade. Complicated use cases may not work properly, though
676	enough simpler ones work to allow recovery in most situations.
677
67820170620:
679	Switch back to the BSDL dtc (Device Tree Compiler). Set WITH_GPL_DTC
680	if you require the GPL compiler.
681
68220170618:
683	The internal ABI used for communication between the NFS kernel modules
684	was changed by r320085, so __FreeBSD_version was bumped to
685	ensure all the NFS related modules are updated together.
686
68720170617:
688	The ABI of struct event was changed by extending the data
689	member to 64bit and adding ext fields.  For upgrade, same
690	precautions as for the entry 20170523 "ino64" must be
691	followed.
692
69320170531:
694	The GNU roff toolchain has been removed from base. To render manpages
695	which are not supported by mandoc(1), man(1) can fallback on GNU roff
696	from ports (and recommends to install it).
697	To render roff(7) documents, consider using GNU roff from ports or the
698	heirloom doctools roff toolchain from ports via pkg install groff or
699	via pkg install heirloom-doctools.
700
70120170524:
702	The ath(4) and ath_hal(4) modules now build piecemeal to allow for
703	smaller runtime footprint builds.  This is useful for embedded systems
704	which only require one chipset support.
705
706	If you load it as a module, make sure this is in /boot/loader.conf:
707
708	if_ath_load="YES"
709
710	This will load the HAL, all chip/RF backends and if_ath_pci.
711	If you have if_ath_pci in /boot/loader.conf, ensure it is after
712	if_ath or it will not load any HAL chipset support.
713
714	If you want to selectively load things (eg on ye cheape ARM/MIPS
715	platforms where RAM is at a premium) you should:
716
717	* load ath_hal
718	* load the chip modules in question
719	* load ath_rate, ath_dfs
720	* load ath_main
721	* load if_ath_pci and/or if_ath_ahb depending upon your particular
722	  bus bind type - this is where probe/attach is done.
723
724	For further comments/feedback, poke adrian@ .
725
72620170523:
727	The "ino64" 64-bit inode project has been committed, which extends
728	a number of types to 64 bits.  Upgrading in place requires care and
729	adherence to the documented upgrade procedure.
730
731	If using a custom kernel configuration ensure that the
732	COMPAT_FREEBSD11 option is included (as during the upgrade the
733	system will be running the ino64 kernel with the existing world).
734
735	For the safest in-place upgrade begin by removing previous build
736	artifacts via "rm -rf /usr/obj/*".  Then, carefully follow the full
737	procedure documented below under the heading "To rebuild everything and
738	install it on the current system."  Specifically, a reboot is required
739	after installing the new kernel before installing world. While an
740	installworld normally works by accident from multiuser after rebooting
741	the proper kernel, there are many cases where this will fail across this
742	upgrade and installworld from single user is required.
743
74420170424:
745	The NATM framework including the en(4), fatm(4), hatm(4), and
746	patm(4) devices has been removed.  Consumers should plan a
747	migration before the end-of-life date for FreeBSD 11.
748
74920170420:
750	GNU diff has been replaced by a BSD licensed diff. Some features of GNU
751	diff has not been implemented, if those are needed a newer version of
752	GNU diff is available via the diffutils package under the gdiff name.
753
75420170413:
755	As of r316810 for ipfilter, keep frags is no longer assumed when
756	keep state is specified in a rule. r316810 aligns ipfilter with
757	documentation in man pages separating keep frags from keep state.
758	This allows keep state to be specified without forcing keep frags
759	and allows keep frags to be specified independently of keep state.
760	To maintain previous behaviour, also specify keep frags with
761	keep state (as documented in ipf.conf.5).
762
76320170407:
764	arm64 builds now use the base system LLD 4.0.0 linker by default,
765	instead of requiring that the aarch64-binutils port or package be
766	installed. To continue using aarch64-binutils, set
767	CROSS_BINUTILS_PREFIX=/usr/local/aarch64-freebsd/bin .
768
76920170405:
770	The UDP optimization in entry 20160818 that added the sysctl
771	net.inet.udp.require_l2_bcast has been reverted.  L2 broadcast
772	packets will no longer be treated as L3 broadcast packets.
773
77420170331:
775	Binds and sends to the loopback addresses, IPv6 and IPv4, will now
776	use any explicitly assigned loopback address available in the jail
777	instead of using the first assigned address of the jail.
778
77920170329:
780	The ctl.ko module no longer implements the iSCSI target frontend:
781	cfiscsi.ko does instead.
782
783	If building cfiscsi.ko as a kernel module, the module can be loaded
784	via one of the following methods:
785	- `cfiscsi_load="YES"` in loader.conf(5).
786	- Add `cfiscsi` to `$kld_list` in rc.conf(5).
787	- ctladm(8)/ctld(8), when compiled with iSCSI support
788	  (`WITH_ISCSI=yes` in src.conf(5))
789
790	Please see cfiscsi(4) for more details.
791
79220170316:
793	The mmcsd.ko module now additionally depends on geom_flashmap.ko.
794	Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
795	same source (previously, the dependency of mmcsd.ko on mmc.ko was
796	missing, but mmcsd.ko now will refuse to load if it is incompatible
797	with mmc.ko).
798
79920170315:
800	The syntax of ipfw(8) named states was changed to avoid ambiguity.
801	If you have used named states in the firewall rules, you need to modify
802	them after installworld and before rebooting. Now named states must
803	be prefixed with colon.
804
80520170311:
806	The old drm (sys/dev/drm/) drivers for i915 and radeon have been
807	removed as the userland we provide cannot use them. The KMS version
808	(sys/dev/drm2) supports the same hardware.
809
81020170302:
811	Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 4.0.0.
812	Please see the 20141231 entry below for information about prerequisites
813	and upgrading, if you are not already using clang 3.5.0 or higher.
814
81520170221:
816	The code that provides support for ZFS .zfs/ directory functionality
817	has been reimplemented.  It's not possible now to create a snapshot
818	by mkdir under .zfs/snapshot/.  That should be the only user visible
819	change.
820
82120170216:
822	EISA bus support has been removed. The WITH_EISA option is no longer
823	valid.
824
82520170215:
826	MCA bus support has been removed.
827
82820170127:
829	The WITH_LLD_AS_LD / WITHOUT_LLD_AS_LD build knobs have been renamed
830	WITH_LLD_IS_LD / WITHOUT_LLD_IS_LD, for consistency with CLANG_IS_CC.
831
83220170112:
833	The EM_MULTIQUEUE kernel configuration option is deprecated now that
834	the em(4) driver conforms to iflib specifications.
835
83620170109:
837	The igb(4), em(4) and lem(4) ethernet drivers are now implemented via
838	IFLIB.  If you have a custom kernel configuration that excludes em(4)
839	but you use igb(4), you need to re-add em(4) to your custom
840	configuration.
841
84220161217:
843	Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.1.
844	Please see the 20141231 entry below for information about prerequisites
845	and upgrading, if you are not already using clang 3.5.0 or higher.
846
84720161124:
848	Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.9.0.
849	Please see the 20141231 entry below for information about prerequisites
850	and upgrading, if you are not already using clang 3.5.0 or higher.
851
85220161119:
853	The layout of the pmap structure has changed for powerpc to put the pmap
854	statistics at the front for all CPU variations.  libkvm(3) and all tools
855	that link against it need to be recompiled.
856
85720161030:
858	isl(4) and cyapa(4) drivers now require a new driver,
859	chromebook_platform(4), to work properly on Chromebook-class hardware.
860	On other types of hardware the drivers may need to be configured using
861	device hints.  Please see the corresponding manual pages for details.
862
86320161017:
864	The urtwn(4) driver was merged into rtwn(4) and now consists of
865	rtwn(4) main module + rtwn_usb(4) and rtwn_pci(4) bus-specific
866	parts.
867	Also, firmware for RTL8188CE was renamed due to possible name
868	conflict (rtwnrtl8192cU(B) -> rtwnrtl8192cE(B))
869
87020161015:
871	GNU rcs has been removed from base.  It is available as packages:
872	- rcs: Latest GPLv3 GNU rcs version.
873	- rcs57: Copy of the latest version of GNU rcs (GPLv2) before it was
874	removed from base.
875
87620161008:
877	Use of the cc_cdg, cc_chd, cc_hd, or cc_vegas congestion control
878	modules now requires that the kernel configuration contain the
879	TCP_HHOOK option. (This option is included in the GENERIC kernel.)
880
88120161003:
882	The WITHOUT_ELFCOPY_AS_OBJCOPY src.conf(5) knob has been retired.
883	ELF Tool Chain's elfcopy is always installed as /usr/bin/objcopy.
884
88520160924:
886	Relocatable object files with the extension of .So have been renamed
887	to use an extension of .pico instead.  The purpose of this change is
888	to avoid a name clash with shared libraries on case-insensitive file
889	systems.  On those file systems, foo.So is the same file as foo.so.
890
89120160918:
892	GNU rcs has been turned off by default.  It can (temporarily) be built
893	again by adding WITH_RCS knob in src.conf.
894	Otherwise, GNU rcs is available from packages:
895	- rcs: Latest GPLv3 GNU rcs version.
896	- rcs57: Copy of the latest version of GNU rcs (GPLv2) from base.
897
89820160918:
899	The backup_uses_rcs functionality has been removed from rc.subr.
900
90120160908:
902	The queue(3) debugging macro, QUEUE_MACRO_DEBUG, has been split into
903	two separate components, QUEUE_MACRO_DEBUG_TRACE and
904	QUEUE_MACRO_DEBUG_TRASH.  Define both for the original
905	QUEUE_MACRO_DEBUG behavior.
906
90720160824:
908	r304787 changed some ioctl interfaces between the iSCSI userspace
909	programs and the kernel.  ctladm, ctld, iscsictl, and iscsid must be
910	rebuilt to work with new kernels.  __FreeBSD_version has been bumped
911	to 1200005.
912
91320160818:
914	The UDP receive code has been updated to only treat incoming UDP
915	packets that were addressed to an L2 broadcast address as L3
916	broadcast packets.  It is not expected that this will affect any
917	standards-conforming UDP application.  The new behaviour can be
918	disabled by setting the sysctl net.inet.udp.require_l2_bcast to
919	0.
920
92120160818:
922	Remove the openbsd_poll system call.
923	__FreeBSD_version has been bumped because of this.
924
92520160708:
926	The stable/11 branch has been created from head@r302406.
927
92820160622:
929	The libc stub for the pipe(2) system call has been replaced with
930	a wrapper that calls the pipe2(2) system call and the pipe(2)
931	system call is now only implemented by the kernels that include
932	"options COMPAT_FREEBSD10" in their config file (this is the
933	default).  Users should ensure that this option is enabled in
934	their kernel or upgrade userspace to r302092 before upgrading their
935	kernel.
936
93720160527:
938	CAM will now strip leading spaces from SCSI disks' serial numbers.
939	This will affect users who create UFS filesystems on SCSI disks using
940	those disk's diskid device nodes.  For example, if /etc/fstab
941	previously contained a line like
942	"/dev/diskid/DISK-%20%20%20%20%20%20%20ABCDEFG0123456", you should
943	change it to "/dev/diskid/DISK-ABCDEFG0123456".  Users of geom
944	transforms like gmirror may also be affected.  ZFS users should
945	generally be fine.
946
94720160523:
948	The bitstring(3) API has been updated with new functionality and
949	improved performance.  But it is binary-incompatible with the old API.
950	Objects built with the new headers may not be linked against objects
951	built with the old headers.
952
95320160520:
954	The brk and sbrk functions have been removed from libc on arm64.
955	Binutils from ports has been updated to not link to these
956	functions and should be updated to the latest version before
957	installing a new libc.
958
95920160517:
960	The armv6 port now defaults to hard float ABI. Limited support
961	for running both hardfloat and soft float on the same system
962	is available using the libraries installed with -DWITH_LIBSOFT.
963	This has only been tested as an upgrade path for installworld
964	and packages may fail or need manual intervention to run. New
965	packages will be needed.
966
967	To update an existing self-hosted armv6hf system, you must add
968	TARGET_ARCH=armv6 on the make command line for both the build
969	and the install steps.
970
97120160510:
972	Kernel modules compiled outside of a kernel build now default to
973	installing to /boot/modules instead of /boot/kernel.  Many kernel
974	modules built this way (such as those in ports) already overrode
975	KMODDIR explicitly to install into /boot/modules.  However,
976	manually building and installing a module from /sys/modules will
977	now install to /boot/modules instead of /boot/kernel.
978
97920160414:
980	The CAM I/O scheduler has been committed to the kernel. There should be
981	no user visible impact. This does enable NCQ Trim on ada SSDs. While the
982	list of known rogues that claim support for this but actually corrupt
983	data is believed to be complete, be on the lookout for data
984	corruption. The known rogue list is believed to be complete:
985
986		o Crucial MX100, M550 drives with MU01 firmware.
987		o Micron M510 and M550 drives with MU01 firmware.
988		o Micron M500 prior to MU07 firmware
989		o Samsung 830, 840, and 850 all firmwares
990		o FCCT M500 all firmwares
991
992	Crucial has firmware http://www.crucial.com/usa/en/support-ssd-firmware
993	with working NCQ TRIM. For Micron branded drives, see your sales rep for
994	updated firmware. Black listed drives will work correctly because these
995	drives work correctly so long as no NCQ TRIMs are sent to them. Given
996	this list is the same as found in Linux, it's believed there are no
997	other rogues in the market place. All other models from the above
998	vendors work.
999
1000	To be safe, if you are at all concerned, you can quirk each of your
1001	drives to prevent NCQ from being sent by setting:
1002		kern.cam.ada.X.quirks="0x2"
1003	in loader.conf. If the drive requires the 4k sector quirk, set the
1004	quirks entry to 0x3.
1005
100620160330:
1007	The FAST_DEPEND build option has been removed and its functionality is
1008	now the one true way.  The old mkdep(1) style of 'make depend' has
1009	been removed.  See 20160311 for further details.
1010
101120160317:
1012	Resource range types have grown from unsigned long to uintmax_t.  All
1013	drivers, and anything using libdevinfo, need to be recompiled.
1014
101520160311:
1016	WITH_FAST_DEPEND is now enabled by default for in-tree and out-of-tree
1017	builds.  It no longer runs mkdep(1) during 'make depend', and the
1018	'make depend' stage can safely be skipped now as it is auto ran
1019	when building 'make all' and will generate all SRCS and DPSRCS before
1020	building anything else.  Dependencies are gathered at compile time with
1021	-MF flags kept in separate .depend files per object file.  Users should
1022	run 'make cleandepend' once if using -DNO_CLEAN to clean out older
1023	stale .depend files.
1024
102520160306:
1026	On amd64, clang 3.8.0 can now insert sections of type AMD64_UNWIND into
1027	kernel modules.  Therefore, if you load any kernel modules at boot time,
1028	please install the boot loaders after you install the kernel, but before
1029	rebooting, e.g.:
1030
1031	make buildworld
1032	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1033	make installkernel KERNCONF=YOUR_KERNEL_HERE
1034	make -C sys/boot install
1035	<reboot in single user>
1036
1037	Then follow the usual steps, described in the General Notes section,
1038	below.
1039
104020160305:
1041	Clang, llvm, lldb and compiler-rt have been upgraded to 3.8.0.  Please
1042	see the 20141231 entry below for information about prerequisites and
1043	upgrading, if you are not already using clang 3.5.0 or higher.
1044
104520160301:
1046	The AIO subsystem is now a standard part of the kernel.  The
1047	VFS_AIO kernel option and aio.ko kernel module have been removed.
1048	Due to stability concerns, asynchronous I/O requests are only
1049	permitted on sockets and raw disks by default.  To enable
1050	asynchronous I/O requests on all file types, set the
1051	vfs.aio.enable_unsafe sysctl to a non-zero value.
1052
105320160226:
1054	The ELF object manipulation tool objcopy is now provided by the
1055	ELF Tool Chain project rather than by GNU binutils. It should be a
1056	drop-in replacement, with the addition of arm64 support. The
1057	(temporary) src.conf knob WITHOUT_ELFCOPY_AS_OBJCOPY knob may be set
1058	to obtain the GNU version if necessary.
1059
106020160129:
1061	Building ZFS pools on top of zvols is prohibited by default.  That
1062	feature has never worked safely; it's always been prone to deadlocks.
1063	Using a zvol as the backing store for a VM guest's virtual disk will
1064	still work, even if the guest is using ZFS.  Legacy behavior can be
1065	restored by setting vfs.zfs.vol.recursive=1.
1066
106720160119:
1068	The NONE and HPN patches has been removed from OpenSSH.  They are
1069	still available in the security/openssh-portable port.
1070
107120160113:
1072	With the addition of ypldap(8), a new _ypldap user is now required
1073	during installworld. "mergemaster -p" can be used to add the user
1074	prior to installworld, as documented in the handbook.
1075
107620151216:
1077	The tftp loader (pxeboot) now uses the option root-path directive. As a
1078	consequence it no longer looks for a pxeboot.4th file on the tftp
1079	server. Instead it uses the regular /boot infrastructure as with the
1080	other loaders.
1081
108220151211:
1083	The code to start recording plug and play data into the modules has
1084	been committed. While the old tools will properly build a new kernel,
1085	a number of warnings about "unknown metadata record 4" will be produced
1086	for an older kldxref. To avoid such warnings, make sure to rebuild
1087	the kernel toolchain (or world). Make sure that you have r292078 or
1088	later when trying to build 292077 or later before rebuilding.
1089
109020151207:
1091	Debug data files are now built by default with 'make buildworld' and
1092	installed with 'make installworld'. This facilitates debugging but
1093	requires more disk space both during the build and for the installed
1094	world. Debug files may be disabled by setting WITHOUT_DEBUG_FILES=yes
1095	in src.conf(5).
1096
109720151130:
1098	r291527 changed the internal interface between the nfsd.ko and
1099	nfscommon.ko modules. As such, they must both be upgraded to-gether.
1100	__FreeBSD_version has been bumped because of this.
1101
110220151108:
1103	Add support for unicode collation strings leads to a change of
1104	order of files listed by ls(1) for example. To get back to the old
1105	behaviour, set LC_COLLATE environment variable to "C".
1106
1107	Databases administrators will need to reindex their databases given
1108	collation results will be different.
1109
1110	Due to a bug in install(1) it is recommended to remove the ancient
1111	locales before running make installworld.
1112
1113	rm -rf /usr/share/locale/*
1114
111520151030:
1116	The OpenSSL has been upgraded to 1.0.2d.  Any binaries requiring
1117	libcrypto.so.7 or libssl.so.7 must be recompiled.
1118
111920151020:
1120	Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
1121	Kernel modules isp_2400_multi and isp_2500_multi were removed and
1122	should be replaced with isp_2400 and isp_2500 modules respectively.
1123
112420151017:
1125	The build previously allowed using 'make -n' to not recurse into
1126	sub-directories while showing what commands would be executed, and
1127	'make -n -n' to recursively show commands.  Now 'make -n' will recurse
1128	and 'make -N' will not.
1129
113020151012:
1131	If you specify SENDMAIL_MC or SENDMAIL_CF in make.conf, mergemaster
1132	and etcupdate will now use this file. A custom sendmail.cf is now
1133	updated via this mechanism rather than via installworld.  If you had
1134	excluded sendmail.cf in mergemaster.rc or etcupdate.conf, you may
1135	want to remove the exclusion or change it to "always install".
1136	/etc/mail/sendmail.cf is now managed the same way regardless of
1137	whether SENDMAIL_MC/SENDMAIL_CF is used.  If you are not using
1138	SENDMAIL_MC/SENDMAIL_CF there should be no change in behavior.
1139
114020151011:
1141	Compatibility shims for legacy ATA device names have been removed.
1142	It includes ATA_STATIC_ID kernel option, kern.cam.ada.legacy_aliases
1143	and kern.geom.raid.legacy_aliases loader tunables, kern.devalias.*
1144	environment variables, /dev/ad* and /dev/ar* symbolic links.
1145
114620151006:
1147	Clang, llvm, lldb, compiler-rt and libc++ have been upgraded to 3.7.0.
1148	Please see the 20141231 entry below for information about prerequisites
1149	and upgrading, if you are not already using clang 3.5.0 or higher.
1150
115120150924:
1152	Kernel debug files have been moved to /usr/lib/debug/boot/kernel/,
1153	and renamed from .symbols to .debug. This reduces the size requirements
1154	on the boot partition or file system and provides consistency with
1155	userland debug files.
1156
1157	When using the supported kernel installation method the
1158	/usr/lib/debug/boot/kernel directory will be renamed (to kernel.old)
1159	as is done with /boot/kernel.
1160
1161	Developers wishing to maintain the historical behavior of installing
1162	debug files in /boot/kernel/ can set KERN_DEBUGDIR="" in src.conf(5).
1163
116420150827:
1165	The wireless drivers had undergone changes that remove the 'parent
1166	interface' from the ifconfig -l output. The rc.d network scripts
1167	used to check presence of a parent interface in the list, so old
1168	scripts would fail to start wireless networking. Thus, etcupdate(3)
1169	or mergemaster(8) run is required after kernel update, to update your
1170	rc.d scripts in /etc.
1171
117220150827:
1173	pf no longer supports 'scrub fragment crop' or 'scrub fragment drop-ovl'
1174	These configurations are now automatically interpreted as
1175	'scrub fragment reassemble'.
1176
117720150817:
1178	Kernel-loadable modules for the random(4) device are back. To use
1179	them, the kernel must have
1180
1181	device	random
1182	options	RANDOM_LOADABLE
1183
1184	kldload(8) can then be used to load random_fortuna.ko
1185	or random_yarrow.ko. Please note that due to the indirect
1186	function calls that the loadable modules need to provide,
1187	the build-in variants will be slightly more efficient.
1188
1189	The random(4) kernel option RANDOM_DUMMY has been retired due to
1190	unpopularity. It was not all that useful anyway.
1191
119220150813:
1193	The WITHOUT_ELFTOOLCHAIN_TOOLS src.conf(5) knob has been retired.
1194	Control over building the ELF Tool Chain tools is now provided by
1195	the WITHOUT_TOOLCHAIN knob.
1196
119720150810:
1198	The polarity of Pulse Per Second (PPS) capture events with the
1199	uart(4) driver has been corrected.  Prior to this change the PPS
1200	"assert" event corresponded to the trailing edge of a positive PPS
1201	pulse and the "clear" event was the leading edge of the next pulse.
1202
1203	As the width of a PPS pulse in a typical GPS receiver is on the
1204	order of 1 millisecond, most users will not notice any significant
1205	difference with this change.
1206
1207	Anyone who has compensated for the historical polarity reversal by
1208	configuring a negative offset equal to the pulse width will need to
1209	remove that workaround.
1210
121120150809:
1212	The default group assigned to /dev/dri entries has been changed
1213	from 'wheel' to 'video' with the id of '44'. If you want to have
1214	access to the dri devices please add yourself to the video group
1215	with:
1216
1217	# pw groupmod video -m $USER
1218
121920150806:
1220	The menu.rc and loader.rc files will now be replaced during
1221	upgrades. Please migrate local changes to menu.rc.local and
1222	loader.rc.local instead.
1223
122420150805:
1225	GNU Binutils versions of addr2line, c++filt, nm, readelf, size,
1226	strings and strip have been removed. The src.conf(5) knob
1227	WITHOUT_ELFTOOLCHAIN_TOOLS no longer provides the binutils tools.
1228
122920150728:
1230	As ZFS requires more kernel stack pages than is the default on some
1231	architectures e.g. i386, it now warns if KSTACK_PAGES is less than
1232	ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
1233
1234	Please consider using 'options KSTACK_PAGES=X' where X is greater
1235	than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
1236
123720150706:
1238	sendmail has been updated to 8.15.2.  Starting with FreeBSD 11.0
1239	and sendmail 8.15, sendmail uses uncompressed IPv6 addresses by
1240	default, i.e., they will not contain "::".  For example, instead
1241	of ::1, it will be 0:0:0:0:0:0:0:1.  This permits a zero subnet
1242	to have a more specific match, such as different map entries for
1243	IPv6:0:0 vs IPv6:0.  This change requires that configuration
1244	data (including maps, files, classes, custom ruleset, etc.) must
1245	use the same format, so make certain such configuration data is
1246	upgrading.  As a very simple check search for patterns like
1247	'IPv6:[0-9a-fA-F:]*::' and 'IPv6::'.  To return to the old
1248	behavior, set the m4 option confUSE_COMPRESSED_IPV6_ADDRESSES or
1249	the cf option UseCompressedIPv6Addresses.
1250
125120150630:
1252	The default kernel entropy-processing algorithm is now
1253	Fortuna, replacing Yarrow.
1254
1255	Assuming you have 'device random' in your kernel config
1256	file, the configurations allow a kernel option to override
1257	this default. You may choose *ONE* of:
1258
1259	options	RANDOM_YARROW	# Legacy /dev/random algorithm.
1260	options	RANDOM_DUMMY	# Blocking-only driver.
1261
1262	If you have neither, you get Fortuna.  For most people,
1263	read no further, Fortuna will give a /dev/random that works
1264	like it always used to, and the difference will be irrelevant.
1265
1266	If you remove 'device random', you get *NO* kernel-processed
1267	entropy at all. This may be acceptable to folks building
1268	embedded systems, but has complications. Carry on reading,
1269	and it is assumed you know what you need.
1270
1271	*PLEASE* read random(4) and random(9) if you are in the
1272	habit of tweaking kernel configs, and/or if you are a member
1273	of the embedded community, wanting specific and not-usual
1274	behaviour from your security subsystems.
1275
1276	NOTE!! If you use RANDOM_DUMMY and/or have no 'device
1277	random', you will NOT have a functioning /dev/random, and
1278	many cryptographic features will not work, including SSH.
1279	You may also find strange behaviour from the random(3) set
1280	of library functions, in particular sranddev(3), srandomdev(3)
1281	and arc4random(3). The reason for this is that the KERN_ARND
1282	sysctl only returns entropy if it thinks it has some to
1283	share, and with RANDOM_DUMMY or no 'device random' this
1284	will never happen.
1285
128620150623:
1287	An additional fix for the issue described in the 20150614 sendmail
1288	entry below has been committed in revision 284717.
1289
129020150616:
1291	FreeBSD's old make (fmake) has been removed from the system. It is
1292	available as the devel/fmake port or via pkg install fmake.
1293
129420150615:
1295	The fix for the issue described in the 20150614 sendmail entry
1296	below has been committed in revision 284436.  The work
1297	around described in that entry is no longer needed unless the
1298	default setting is overridden by a confDH_PARAMETERS configuration
1299	setting of '5' or pointing to a 512 bit DH parameter file.
1300
130120150614:
1302	ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
1303	atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
1304	and devel/kyua to version 0.20+ and adjust any calling code to work
1305	with Kyuafile and kyua.
1306
130720150614:
1308	The import of openssl to address the FreeBSD-SA-15:10.openssl
1309	security advisory includes a change which rejects handshakes
1310	with DH parameters below 768 bits.  sendmail releases prior
1311	to 8.15.2 (not yet released), defaulted to a 512 bit
1312	DH parameter setting for client connections.  To work around
1313	this interoperability, sendmail can be configured to use a
1314	2048 bit DH parameter by:
1315
1316	1. Edit /etc/mail/`hostname`.mc
1317	2. If a setting for confDH_PARAMETERS does not exist or
1318	   exists and is set to a string beginning with '5',
1319	   replace it with '2'.
1320	3. If a setting for confDH_PARAMETERS exists and is set to
1321	   a file path, create a new file with:
1322		openssl dhparam -out /path/to/file 2048
1323	4. Rebuild the .cf file:
1324		cd /etc/mail/; make; make install
1325	5. Restart sendmail:
1326		cd /etc/mail/; make restart
1327
1328	A sendmail patch is coming, at which time this file will be
1329	updated.
1330
133120150604:
1332	Generation of legacy formatted entries have been disabled by default
1333	in pwd_mkdb(8), as all base system consumers of the legacy formatted
1334	entries were converted to use the new format by default when the new,
1335	machine independent format have been added and supported since FreeBSD
1336	5.x.
1337
1338	Please see the pwd_mkdb(8) manual page for further details.
1339
134020150525:
1341	Clang and llvm have been upgraded to 3.6.1 release.  Please see the
1342	20141231 entry below for information about prerequisites and upgrading,
1343	if you are not already using 3.5.0 or higher.
1344
134520150521:
1346	TI platform code switched to using vendor DTS files and this update
1347	may break existing systems running on Beaglebone, Beaglebone Black,
1348	and Pandaboard:
1349
1350	- dtb files should be regenerated/reinstalled. Filenames are the
1351	  same but content is different now
1352	- GPIO addressing was changed, now each GPIO bank (32 pins per bank)
1353	  has its own /dev/gpiocX device, e.g. pin 121 on /dev/gpioc0 in old
1354	  addressing scheme is now pin 25 on /dev/gpioc3.
1355	- Pandaboard: /etc/ttys should be updated, serial console device is
1356	  now /dev/ttyu2, not /dev/ttyu0
1357
135820150501:
1359	soelim(1) from gnu/usr.bin/groff has been replaced by usr.bin/soelim.
1360	If you need the GNU extension from groff soelim(1), install groff
1361	from package: pkg install groff, or via ports: textproc/groff.
1362
136320150423:
1364	chmod, chflags, chown and chgrp now affect symlinks in -R mode as
1365	defined in symlink(7); previously symlinks were silently ignored.
1366
136720150415:
1368	The const qualifier has been removed from iconv(3) to comply with
1369	POSIX.  The ports tree is aware of this from r384038 onwards.
1370
137120150416:
1372	Libraries specified by LIBADD in Makefiles must have a corresponding
1373	DPADD_<lib> variable to ensure correct dependencies.  This is now
1374	enforced in src.libnames.mk.
1375
137620150324:
1377	From legacy ata(4) driver was removed support for SATA controllers
1378	supported by more functional drivers ahci(4), siis(4) and mvs(4).
1379	Kernel modules ataahci and ataadaptec were removed completely,
1380	replaced by ahci and mvs modules respectively.
1381
138220150315:
1383	Clang, llvm and lldb have been upgraded to 3.6.0 release.  Please see
1384	the 20141231 entry below for information about prerequisites and
1385	upgrading, if you are not already using 3.5.0 or higher.
1386
138720150307:
1388	The 32-bit PowerPC kernel has been changed to a position-independent
1389	executable. This can only be booted with a version of loader(8)
1390	newer than January 31, 2015, so make sure to update both world and
1391	kernel before rebooting.
1392
139320150217:
1394	If you are running a -CURRENT kernel since r273872 (Oct 30th, 2014),
1395	but before r278950, the RNG was not seeded properly.  Immediately
1396	upgrade the kernel to r278950 or later and regenerate any keys (e.g.
1397	ssh keys or openssl keys) that were generated w/ a kernel from that
1398	range.  This does not affect programs that directly used /dev/random
1399	or /dev/urandom.  All userland uses of arc4random(3) are affected.
1400
140120150210:
1402	The autofs(4) ABI was changed in order to restore binary compatibility
1403	with 10.1-RELEASE.  The automountd(8) daemon needs to be rebuilt to work
1404	with the new kernel.
1405
140620150131:
1407	The powerpc64 kernel has been changed to a position-independent
1408	executable. This can only be booted with a new version of loader(8),
1409	so make sure to update both world and kernel before rebooting.
1410
141120150118:
1412	Clang and llvm have been upgraded to 3.5.1 release.  This is a bugfix
1413	only release, no new features have been added.  Please see the 20141231
1414	entry below for information about prerequisites and upgrading, if you
1415	are not already using 3.5.0.
1416
141720150107:
1418	ELF tools addr2line, elfcopy (strip), nm, size, and strings are now
1419	taken from the ELF Tool Chain project rather than GNU binutils. They
1420	should be drop-in replacements, with the addition of arm64 support.
1421	The WITHOUT_ELFTOOLCHAIN_TOOLS= knob may be used to obtain the
1422	binutils tools, if necessary. See 20150805 for updated information.
1423
142420150105:
1425	The default Unbound configuration now enables remote control
1426	using a local socket.  Users who have already enabled the
1427	local_unbound service should regenerate their configuration
1428	by running "service local_unbound setup" as root.
1429
143020150102:
1431	The GNU texinfo and GNU info pages have been removed.
1432	To be able to view GNU info pages please install texinfo from ports.
1433
143420141231:
1435	Clang, llvm and lldb have been upgraded to 3.5.0 release.
1436
1437	As of this release, a prerequisite for building clang, llvm and lldb is
1438	a C++11 capable compiler and C++11 standard library.  This means that to
1439	be able to successfully build the cross-tools stage of buildworld, with
1440	clang as the bootstrap compiler, your system compiler or cross compiler
1441	should either be clang 3.3 or later, or gcc 4.8 or later, and your
1442	system C++ library should be libc++, or libdstdc++ from gcc 4.8 or
1443	later.
1444
1445	On any standard FreeBSD 10.x or 11.x installation, where clang and
1446	libc++ are on by default (that is, on x86 or arm), this should work out
1447	of the box.
1448
1449	On 9.x installations where clang is enabled by default, e.g. on x86 and
1450	powerpc, libc++ will not be enabled by default, so libc++ should be
1451	built (with clang) and installed first.  If both clang and libc++ are
1452	missing, build clang first, then use it to build libc++.
1453
1454	On 8.x and earlier installations, upgrade to 9.x first, and then follow
1455	the instructions for 9.x above.
1456
1457	Sparc64 and mips users are unaffected, as they still use gcc 4.2.1 by
1458	default, and do not build clang.
1459
1460	Many embedded systems are resource constrained, and will not be able to
1461	build clang in a reasonable time, or in some cases at all.  In those
1462	cases, cross building bootable systems on amd64 is a workaround.
1463
1464	This new version of clang introduces a number of new warnings, of which
1465	the following are most likely to appear:
1466
1467	-Wabsolute-value
1468
1469	This warns in two cases, for both C and C++:
1470	* When the code is trying to take the absolute value of an unsigned
1471	  quantity, which is effectively a no-op, and almost never what was
1472	  intended.  The code should be fixed, if at all possible.  If you are
1473	  sure that the unsigned quantity can be safely cast to signed, without
1474	  loss of information or undefined behavior, you can add an explicit
1475	  cast, or disable the warning.
1476
1477	* When the code is trying to take an absolute value, but the called
1478	  abs() variant is for the wrong type, which can lead to truncation.
1479	  If you want to disable the warning instead of fixing the code, please
1480	  make sure that truncation will not occur, or it might lead to unwanted
1481	  side-effects.
1482
1483	-Wtautological-undefined-compare and
1484	-Wundefined-bool-conversion
1485
1486	These warn when C++ code is trying to compare 'this' against NULL, while
1487	'this' should never be NULL in well-defined C++ code.  However, there is
1488	some legacy (pre C++11) code out there, which actively abuses this
1489	feature, which was less strictly defined in previous C++ versions.
1490
1491	Squid and openjdk do this, for example.  The warning can be turned off
1492	for C++98 and earlier, but compiling the code in C++11 mode might result
1493	in unexpected behavior; for example, the parts of the program that are
1494	unreachable could be optimized away.
1495
149620141222:
1497	The old NFS client and server (kernel options NFSCLIENT, NFSSERVER)
1498	kernel sources have been removed. The .h files remain, since some
1499	utilities include them. This will need to be fixed later.
1500	If "mount -t oldnfs ..." is attempted, it will fail.
1501	If the "-o" option on mountd(8), nfsd(8) or nfsstat(1) is used,
1502	the utilities will report errors.
1503
150420141121:
1505	The handling of LOCAL_LIB_DIRS has been altered to skip addition of
1506	directories to top level SUBDIR variable when their parent
1507	directory is included in LOCAL_DIRS.  Users with build systems with
1508	such hierarchies and without SUBDIR entries in the parent
1509	directory Makefiles should add them or add the directories to
1510	LOCAL_DIRS.
1511
151220141109:
1513	faith(4) and faithd(8) have been removed from the base system. Faith
1514	has been obsolete for a very long time.
1515
151620141104:
1517	vt(4), the new console driver, is enabled by default. It brings
1518	support for Unicode and double-width characters, as well as
1519	support for UEFI and integration with the KMS kernel video
1520	drivers.
1521
1522	You may need to update your console settings in /etc/rc.conf,
1523	most probably the keymap. During boot, /etc/rc.d/syscons will
1524	indicate what you need to do.
1525
1526	vt(4) still has issues and lacks some features compared to
1527	syscons(4). See the wiki for up-to-date information:
1528	  https://wiki.freebsd.org/Newcons
1529
1530	If you want to keep using syscons(4), you can do so by adding
1531	the following line to /boot/loader.conf:
1532	  kern.vty=sc
1533
153420141102:
1535	pjdfstest has been integrated into kyua as an opt-in test suite.
1536	Please see share/doc/pjdfstest/README for more details on how to
1537	execute it.
1538
153920141009:
1540	gperf has been removed from the base system for architectures
1541	that use clang. Ports that require gperf will obtain it from the
1542	devel/gperf port.
1543
154420140923:
1545	pjdfstest has been moved from tools/regression/pjdfstest to
1546	contrib/pjdfstest .
1547
154820140922:
1549	At svn r271982, The default linux compat kernel ABI has been adjusted
1550	to 2.6.18 in support of the linux-c6 compat ports infrastructure
1551	update.  If you wish to continue using the linux-f10 compat ports,
1552	add compat.linux.osrelease=2.6.16 to your local sysctl.conf.  Users are
1553	encouraged to update their linux-compat packages to linux-c6 during
1554	their next update cycle.
1555
155620140729:
1557	The ofwfb driver, used to provide a graphics console on PowerPC when
1558	using vt(4), no longer allows mmap() of all physical memory. This
1559	will prevent Xorg on PowerPC with some ATI graphics cards from
1560	initializing properly unless x11-servers/xorg-server is updated to
1561	1.12.4_8 or newer.
1562
156320140723:
1564	The xdev targets have been converted to using TARGET and
1565	TARGET_ARCH instead of XDEV and XDEV_ARCH.
1566
156720140719:
1568	The default unbound configuration has been modified to address
1569	issues with reverse lookups on networks that use private
1570	address ranges.  If you use the local_unbound service, run
1571	"service local_unbound setup" as root to regenerate your
1572	configuration, then "service local_unbound reload" to load the
1573	new configuration.
1574
157520140709:
1576	The GNU texinfo and GNU info pages are not built and installed
1577	anymore, WITH_INFO knob has been added to allow to built and install
1578	them again.
1579	UPDATE: see 20150102 entry on texinfo's removal
1580
158120140708:
1582	The GNU readline library is now an INTERNALLIB - that is, it is
1583	statically linked into consumers (GDB and variants) in the base
1584	system, and the shared library is no longer installed.  The
1585	devel/readline port is available for third party software that
1586	requires readline.
1587
158820140702:
1589	The Itanium architecture (ia64) has been removed from the list of
1590	known architectures. This is the first step in the removal of the
1591	architecture.
1592
159320140701:
1594	Commit r268115 has added NFSv4.1 server support, merged from
1595	projects/nfsv4.1-server.  Since this includes changes to the
1596	internal interfaces between the NFS related modules, a full
1597	build of the kernel and modules will be necessary.
1598	__FreeBSD_version has been bumped.
1599
160020140629:
1601	The WITHOUT_VT_SUPPORT kernel config knob has been renamed
1602	WITHOUT_VT.  (The other _SUPPORT knobs have a consistent meaning
1603	which differs from the behaviour controlled by this knob.)
1604
160520140619:
1606	Maximal length of the serial number in CTL was increased from 16 to
1607	64 chars, that breaks ABI.  All CTL-related tools, such as ctladm
1608	and ctld, need to be rebuilt to work with a new kernel.
1609
161020140606:
1611	The libatf-c and libatf-c++ major versions were downgraded to 0 and
1612	1 respectively to match the upstream numbers.  They were out of
1613	sync because, when they were originally added to FreeBSD, the
1614	upstream versions were not respected.  These libraries are private
1615	and not yet built by default, so renumbering them should be a
1616	non-issue.  However, unclean source trees will yield broken test
1617	programs once the operator executes "make delete-old-libs" after a
1618	"make installworld".
1619
1620	Additionally, the atf-sh binary was made private by moving it into
1621	/usr/libexec/.  Already-built shell test programs will keep the
1622	path to the old binary so they will break after "make delete-old"
1623	is run.
1624
1625	If you are using WITH_TESTS=yes (not the default), wipe the object
1626	tree and rebuild from scratch to prevent spurious test failures.
1627	This is only needed once: the misnumbered libraries and misplaced
1628	binaries have been added to OptionalObsoleteFiles.inc so they will
1629	be removed during a clean upgrade.
1630
163120140512:
1632	Clang and llvm have been upgraded to 3.4.1 release.
1633
163420140508:
1635	We bogusly installed src.opts.mk in /usr/share/mk. This file should
1636	be removed to avoid issues in the future (and has been added to
1637	ObsoleteFiles.inc).
1638
163920140505:
1640	/etc/src.conf now affects only builds of the FreeBSD src tree. In the
1641	past, it affected all builds that used the bsd.*.mk files. The old
1642	behavior was a bug, but people may have relied upon it. To get this
1643	behavior back, you can .include /etc/src.conf from /etc/make.conf
1644	(which is still global and isn't changed). This also changes the
1645	behavior of incremental builds inside the tree of individual
1646	directories. Set MAKESYSPATH to ".../share/mk" to do that.
1647	Although this has survived make universe and some upgrade scenarios,
1648	other upgrade scenarios may have broken. At least one form of
1649	temporary breakage was fixed with MAKESYSPATH settings for buildworld
1650	as well... In cases where MAKESYSPATH isn't working with this
1651	setting, you'll need to set it to the full path to your tree.
1652
1653	One side effect of all this cleaning up is that bsd.compiler.mk
1654	is no longer implicitly included by bsd.own.mk. If you wish to
1655	use COMPILER_TYPE, you must now explicitly include bsd.compiler.mk
1656	as well.
1657
165820140430:
1659	The lindev device has been removed since /dev/full has been made a
1660	standard device.  __FreeBSD_version has been bumped.
1661
166220140424:
1663	The knob WITHOUT_VI was added to the base system, which controls
1664	building ex(1), vi(1), etc. Older releases of FreeBSD required ex(1)
1665	in order to reorder files share/termcap and didn't build ex(1) as a
1666	build tool, so building/installing with WITH_VI is highly advised for
1667	build hosts for older releases.
1668
1669	This issue has been fixed in stable/9 and stable/10 in r277022 and
1670	r276991, respectively.
1671
167220140418:
1673	The YES_HESIOD knob has been removed. It has been obsolete for
1674	a decade. Please move to using WITH_HESIOD instead or your builds
1675	will silently lack HESIOD.
1676
167720140405:
1678	The uart(4) driver has been changed with respect to its handling
1679	of the low-level console. Previously the uart(4) driver prevented
1680	any process from changing the baudrate or the CLOCAL and HUPCL
1681	control flags. By removing the restrictions, operators can make
1682	changes to the serial console port without having to reboot.
1683	However, when getty(8) is started on the serial device that is
1684	associated with the low-level console, a misconfigured terminal
1685	line in /etc/ttys will now have a real impact.
1686	Before upgrading the kernel, make sure that /etc/ttys has the
1687	serial console device configured as 3wire without baudrate to
1688	preserve the previous behaviour. E.g:
1689	    ttyu0  "/usr/libexec/getty 3wire"  vt100  on  secure
1690
169120140306:
1692	Support for libwrap (TCP wrappers) in rpcbind was disabled by default
1693	to improve performance.  To re-enable it, if needed, run rpcbind
1694	with command line option -W.
1695
169620140226:
1697	Switched back to the GPL dtc compiler due to updates in the upstream
1698	dts files not being supported by the BSDL dtc compiler. You will need
1699	to rebuild your kernel toolchain to pick up the new compiler. Core dumps
1700	may result while building dtb files during a kernel build if you fail
1701	to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
1702
170320140216:
1704	Clang and llvm have been upgraded to 3.4 release.
1705
170620140216:
1707	The nve(4) driver has been removed.  Please use the nfe(4) driver
1708	for NVIDIA nForce MCP Ethernet adapters instead.
1709
171020140212:
1711	An ABI incompatibility crept into the libc++ 3.4 import in r261283.
1712	This could cause certain C++ applications using shared libraries built
1713	against the previous version of libc++ to crash.  The incompatibility
1714	has now been fixed, but any C++ applications or shared libraries built
1715	between r261283 and r261801 should be recompiled.
1716
171720140204:
1718	OpenSSH will now ignore errors caused by kernel lacking of Capsicum
1719	capability mode support.  Please note that enabling the feature in
1720	kernel is still highly recommended.
1721
172220140131:
1723	OpenSSH is now built with sandbox support, and will use sandbox as
1724	the default privilege separation method.  This requires Capsicum
1725	capability mode support in kernel.
1726
172720140128:
1728	The libelf and libdwarf libraries have been updated to newer
1729	versions from upstream. Shared library version numbers for
1730	these two libraries were bumped. Any ports or binaries
1731	requiring these two libraries should be recompiled.
1732	__FreeBSD_version is bumped to 1100006.
1733
173420140110:
1735	If a Makefile in a tests/ directory was auto-generating a Kyuafile
1736	instead of providing an explicit one, this would prevent such
1737	Makefile from providing its own Kyuafile in the future during
1738	NO_CLEAN builds.  This has been fixed in the Makefiles but manual
1739	intervention is needed to clean an objdir if you use NO_CLEAN:
1740	  # find /usr/obj -name Kyuafile | xargs rm -f
1741
174220131213:
1743	The behavior of gss_pseudo_random() for the krb5 mechanism
1744	has changed, for applications requesting a longer random string
1745	than produced by the underlying enctype's pseudo-random() function.
1746	In particular, the random string produced from a session key of
1747	enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
1748	be different at the 17th octet and later, after this change.
1749	The counter used in the PRF+ construction is now encoded as a
1750	big-endian integer in accordance with RFC 4402.
1751	__FreeBSD_version is bumped to 1100004.
1752
175320131108:
1754	The WITHOUT_ATF build knob has been removed and its functionality
1755	has been subsumed into the more generic WITHOUT_TESTS.  If you were
1756	using the former to disable the build of the ATF libraries, you
1757	should change your settings to use the latter.
1758
175920131025:
1760	The default version of mtree is nmtree which is obtained from
1761	NetBSD.  The output is generally the same, but may vary
1762	slightly.  If you found you need identical output adding
1763	"-F freebsd9" to the command line should do the trick.  For the
1764	time being, the old mtree is available as fmtree.
1765
176620131014:
1767	libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
1768	This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
1769	1.1.4_8 and verify bsdyml not linked in, before running "make
1770	delete-old-libs":
1771	  # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
1772	  or
1773	  # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
1774
177520131010:
1776	The stable/10 branch has been created in subversion from head
1777	revision r256279.
1778
1779COMMON ITEMS:
1780
1781	General Notes
1782	-------------
1783	Avoid using make -j when upgrading.  While generally safe, there are
1784	sometimes problems using -j to upgrade.  If your upgrade fails with
1785	-j, please try again without -j.  From time to time in the past there
1786	have been problems using -j with buildworld and/or installworld.  This
1787	is especially true when upgrading between "distant" versions (eg one
1788	that cross a major release boundary or several minor releases, or when
1789	several months have passed on the -current branch).
1790
1791	Sometimes, obscure build problems are the result of environment
1792	poisoning.  This can happen because the make utility reads its
1793	environment when searching for values for global variables.  To run
1794	your build attempts in an "environmental clean room", prefix all make
1795	commands with 'env -i '.  See the env(1) manual page for more details.
1796
1797	When upgrading from one major version to another it is generally best to
1798	upgrade to the latest code in the currently installed branch first, then
1799	do an upgrade to the new branch. This is the best-tested upgrade path,
1800	and has the highest probability of being successful.  Please try this
1801	approach if you encounter problems with a major version upgrade.  Since
1802	the stable 4.x branch point, one has generally been able to upgrade from
1803	anywhere in the most recent stable branch to head / current (or even the
1804	last couple of stable branches). See the top of this file when there's
1805	an exception.
1806
1807	When upgrading a live system, having a root shell around before
1808	installing anything can help undo problems. Not having a root shell
1809	around can lead to problems if pam has changed too much from your
1810	starting point to allow continued authentication after the upgrade.
1811
1812	This file should be read as a log of events. When a later event changes
1813	information of a prior event, the prior event should not be deleted.
1814	Instead, a pointer to the entry with the new information should be
1815	placed in the old entry. Readers of this file should also sanity check
1816	older entries before relying on them blindly. Authors of new entries
1817	should write them with this in mind.
1818
1819	ZFS notes
1820	---------
1821	When upgrading the boot ZFS pool to a new version, always follow
1822	these two steps:
1823
1824	1.) recompile and reinstall the ZFS boot loader and boot block
1825	(this is part of "make buildworld" and "make installworld")
1826
1827	2.) update the ZFS boot block on your boot drive
1828
1829	The following example updates the ZFS boot block on the first
1830	partition (freebsd-boot) of a GPT partitioned drive ada0:
1831	"gpart bootcode -p /boot/gptzfsboot -i 1 ada0"
1832
1833	Non-boot pools do not need these updates.
1834
1835	To build a kernel
1836	-----------------
1837	If you are updating from a prior version of FreeBSD (even one just
1838	a few days old), you should follow this procedure.  It is the most
1839	failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1840
1841	make kernel-toolchain
1842	make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1843	make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1844
1845	To test a kernel once
1846	---------------------
1847	If you just want to boot a kernel once (because you are not sure
1848	if it works, or if you want to boot a known bad kernel to provide
1849	debugging information) run
1850	make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1851	nextboot -k testkernel
1852
1853	To rebuild everything and install it on the current system.
1854	-----------------------------------------------------------
1855	# Note: sometimes if you are running current you gotta do more than
1856	# is listed here if you are upgrading from a really old current.
1857
1858	<make sure you have good level 0 dumps>
1859	make buildworld
1860	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1861	make installkernel KERNCONF=YOUR_KERNEL_HERE
1862							[1]
1863	<reboot in single user>				[3]
1864	mergemaster -Fp					[5]
1865	make installworld
1866	mergemaster -Fi					[4]
1867	make delete-old					[6]
1868	<reboot>
1869
1870	To cross-install current onto a separate partition
1871	--------------------------------------------------
1872	# In this approach we use a separate partition to hold
1873	# current's root, 'usr', and 'var' directories.   A partition
1874	# holding "/", "/usr" and "/var" should be about 2GB in
1875	# size.
1876
1877	<make sure you have good level 0 dumps>
1878	<boot into -stable>
1879	make buildworld
1880	make buildkernel KERNCONF=YOUR_KERNEL_HERE
1881	<maybe newfs current's root partition>
1882	<mount current's root partition on directory ${CURRENT_ROOT}>
1883	make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1884	make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1885	make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1886	cp /etc/fstab ${CURRENT_ROOT}/etc/fstab 		   # if newfs'd
1887	<edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1888	<reboot into current>
1889	<do a "native" rebuild/install as described in the previous section>
1890	<maybe install compatibility libraries from ports/misc/compat*>
1891	<reboot>
1892
1893
1894	To upgrade in-place from stable to current
1895	----------------------------------------------
1896	<make sure you have good level 0 dumps>
1897	make buildworld					[9]
1898	make buildkernel KERNCONF=YOUR_KERNEL_HERE	[8]
1899	make installkernel KERNCONF=YOUR_KERNEL_HERE
1900							[1]
1901	<reboot in single user>				[3]
1902	mergemaster -Fp					[5]
1903	make installworld
1904	mergemaster -Fi					[4]
1905	make delete-old					[6]
1906	<reboot>
1907
1908	Make sure that you've read the UPDATING file to understand the
1909	tweaks to various things you need.  At this point in the life
1910	cycle of current, things change often and you are on your own
1911	to cope.  The defaults can also change, so please read ALL of
1912	the UPDATING entries.
1913
1914	Also, if you are tracking -current, you must be subscribed to
1915	freebsd-current@freebsd.org.  Make sure that before you update
1916	your sources that you have read and understood all the recent
1917	messages there.  If in doubt, please track -stable which has
1918	much fewer pitfalls.
1919
1920	[1] If you have third party modules, such as vmware, you
1921	should disable them at this point so they don't crash your
1922	system on reboot.
1923
1924	[3] From the bootblocks, boot -s, and then do
1925		fsck -p
1926		mount -u /
1927		mount -a
1928		sh /etc/rc.d/zfs start	# mount zfs filesystem, if needed
1929		cd src			# full path to source
1930		adjkerntz -i		# if CMOS is wall time
1931	Also, when doing a major release upgrade, it is required that
1932	you boot into single user mode to do the installworld.
1933
1934	[4] Note: This step is non-optional.  Failure to do this step
1935	can result in a significant reduction in the functionality of the
1936	system.  Attempting to do it by hand is not recommended and those
1937	that pursue this avenue should read this file carefully, as well
1938	as the archives of freebsd-current and freebsd-hackers mailing lists
1939	for potential gotchas.  The -U option is also useful to consider.
1940	See mergemaster(8) for more information.
1941
1942	[5] Usually this step is a no-op.  However, from time to time
1943	you may need to do this if you get unknown user in the following
1944	step.  It never hurts to do it all the time.  You may need to
1945	install a new mergemaster (cd src/usr.sbin/mergemaster && make
1946	install) after the buildworld before this step if you last updated
1947	from current before 20130425 or from -stable before 20130430.
1948
1949	[6] This only deletes old files and directories. Old libraries
1950	can be deleted by "make delete-old-libs", but you have to make
1951	sure that no program is using those libraries anymore.
1952
1953	[8] The new kernel must be able to run existing binaries used by an
1954	installworld.  When upgrading across major versions, the new kernel's
1955	configuration must include the correct COMPAT_FREEBSD<n> option for
1956	existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries).  Failure
1957	to do so may leave you with a system that is hard to boot to recover. A
1958	GENERIC kernel will include suitable compatibility options to run
1959	binaries from older branches.  Note that the ability to run binaries
1960	from unsupported branches is not guaranteed.
1961
1962	Make sure that you merge any new devices from GENERIC since the
1963	last time you updated your kernel config file. Options also
1964	change over time, so you may need to adjust your custom kernels
1965	for these as well.
1966
1967	[9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1968	"?=" instead of the "=" assignment operator, so that buildworld can
1969	override the CPUTYPE if it needs to.
1970
1971	MAKEOBJDIRPREFIX must be defined in an environment variable, and
1972	not on the command line, or in /etc/make.conf.  buildworld will
1973	warn if it is improperly defined.
1974FORMAT:
1975
1976This file contains a list, in reverse chronological order, of major
1977breakages in tracking -current.  It is not guaranteed to be a complete
1978list of such breakages, and only contains entries since September 23, 2011.
1979If you need to see UPDATING entries from before that date, you will need
1980to fetch an UPDATING file from an older FreeBSD release.
1981
1982Copyright information:
1983
1984Copyright 1998-2009 M. Warner Losh.
1985
1986Redistribution, publication, translation and use, with or without
1987modification, in full or in part, in any form or format of this
1988document are permitted without further permission from the author.
1989
1990THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1991IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1992WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1993DISCLAIMED.  IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1994INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1995(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1996SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1997HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1998STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1999IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2000POSSIBILITY OF SUCH DAMAGE.
2001
2002Contact Warner Losh if you have any questions about your use of
2003this document.
2004
2005$FreeBSD$
2006