1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 20180404 p29 FreeBSD-SA-18:04.vt
20 FreeBSD-SA-18:05.ipsec
21 FreeBSD-EN-18:03.tzdata
24 Fix vt console memory disclosure. [SA-18:04.vt]
26 Fix ipsec crash or denial of service. [SA-18:05.ipsec]
28 Update timezone database information. [EN-18:03.tzdata]
30 Fix multiple small kernel memory disclosures. [EN-18:04.mem]
32 20180308 p28 FreeBSD-SA-18:01.ipsec [revised]
34 Fix ipsec validation and use-after-free.
36 20180307 p27 FreeBSD-SA-18:01.ipsec
38 FreeBSD-EN-18:01.tzdata
41 Fix ipsec validation and use-after-free. [SA-18:01.ipsec]
43 Fix multiple vulnerabilities in ntp. [SA-18:02.ntp]
45 Update timezone database information. [EN-18:01.tzdata]
47 Update file(1) to new version with security update. [EN-18:02.file]
49 20171209 p26 FreeBSD-SA-17:12.openssl
51 Fix OpenSSL error state vulnerability.
53 20171129 p25 FreeBSD-SA-17:11.openssl
55 Fix OpenSSL out-of-bounds read vulnerability.
57 20171115 p24 FreeBSD-SA-17:08.ptrace
59 FreeBSD-SA-17:10.kldstat
61 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
63 Fix POSIX shm namespace vulnerability. [SA-17:09.shm]
65 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
67 20171102 p23 FreeBSD-EN-17:09.tzdata
69 Update timezone database information. [EN-17:09]
71 20171017 p22 FreeBSD-SA-17:07.wpa
73 Fix WPA2 protocol vulnerability. [SA-17:07]
75 20170810 p21 FreeBSD-SA-17:06.openssh
77 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
79 20170712 p20 FreeBSD-SA-17:05.heimdal
80 FreeBSD-EN-17:06.hyperv
82 Fix heimdal KDC-REP service name validation vulnerability [SA-17:05]
84 Boot compatibility improvements with Azure VMs. [EN-17:06]
86 20170427 p19 FreeBSD-SA-17:04.ipfilter
88 Fix ipfilter(4) fragment handling panic. [SA-17:04]
90 20170412 p18 FreeBSD-SA-17:03.ntp
93 Fix multiple vulnerabilities of ntp. [SA-17:03]
95 Xen migration enhancements. [EN-17:05]
97 20170223 p17 FreeBSD-SA-17:02.openssl
99 Fix OpenSSL RC4_MD5 cipher vulnerability.
101 20170111 p16 FreeBSD-SA-17:01.openssh
103 Fix multiple vulnerabilities of OpenSSH.
105 20161222 p15 FreeBSD-SA-16:39.ntp
107 Fix multiple vulnerabilities of ntp.
109 20161208 p14 FreeBSD-SA-16:37.libc [revised]
111 Fix regressions introduced by SA-16:37.libc.
113 20161206 p13 FreeBSD-SA-16:36.telnetd
114 FreeBSD-SA-16:37.libc
115 FreeBSD-SA-16:38.bhyve
116 FreeBSD-EN-16:19.tzcode
117 FreeBSD-EN-16:20.tzdata
119 Fix possible login(1) argument injection in telnetd(8). [SA-16:36]
120 Fix link_ntoa(3) buffer overflow in libc. [SA-16:37]
121 Fix possible escape from bhyve(8) virtual machine. [SA-16:38]
122 Fix warnings about valid time zone abbreviations. [EN-16:19]
123 Update timezone database information. [EN-16:20]
125 20161102 p12 FreeBSD-SA-16:33.openssh
126 FreeBSD-SA-16:35.openssl
128 Fix OpenSSH remote Denial of Service vulnerability. [SA-16:33]
130 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
132 20161025 p11 FreeBSD-SA-16:15.sysarch [revised]
135 Fix incorrect argument validation in sysarch(2). [SA-16:15]
136 Fix virtual memory subsystem bugs. [EN-16:17]
138 20161010 p10 FreeBSD-SA-16:29.bspatch
139 FreeBSD-SA-16:30.portsnap
140 FreeBSD-SA-16:31.libarchive
142 Fix bspatch heap overflow vulnerability. [SA-16:29]
144 Fix multiple portsnap vulnerabilities. [SA-16:30]
146 Fix multiple libarchive vulnerabilities. [SA-16:31]
148 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
150 Fix OpenSSL regression introduced in SA-16:26.
152 20160923 p8 FreeBSD-SA-16:26.openssl
154 Fix multiple OpenSSL vulnerabilitites.
156 20160811 p7 FreeBSD-EN-16:10.dhclient
157 FreeBSD-EN-16:11.vmbus
158 FreeBSD-EN-16:12.hv_storvsc
159 FreeBSD-EN-16:13.vmbus
160 FreeBSD-EN-16:14.hv_storvsc
161 FreeBSD-EN-16:15.vmbus
162 FreeBSD-EN-16:16.hv_storvsc
164 Fix handling of unknown options from a DHCP server. [EN-16:10]
165 Fix a panic in hv_vmbus(4). [EN-16:11]
166 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
167 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
168 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
169 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
170 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
172 20160725 p6 FreeBSD-SA-16:25.bspatch
173 FreeBSD-EN-16:09.freebsd-update
175 Fix bspatch heap overflow vulnerability. [SA-16:25]
177 Fix freebsd-update(8) support of FreeBSD 11.0 release
178 distribution. [EN-16:09]
180 20160604 p5 FreeBSD-SA-16:24.ntp
182 Fix multiple vulnerabilities of ntp.
184 20160531 p4 FreeBSD-SA-16:20.linux
185 FreeBSD-SA-16:21.43bsd
186 FreeBSD-SA-16:22.libarchive
188 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
189 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
190 Fix directory traversal in cpio(1). [SA-16:22]
193 20160517 p3 FreeBSD-SA-16:18.atkbd
194 FreeBSD-SA-16:19.sendmsg
196 Fix buffer overflow in keyboard driver. [SA-16:18]
198 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
200 20160504 p2 FreeBSD-SA-16:17.openssl
201 FreeBSD-EN-16:06.libc
205 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
207 Fix performance regression in libc hash(3). [EN-16:06]
209 Fix excessive latency in x86 IPI delivery. [EN-16:07]
211 Fix memory leak in ZFS. [EN-16:08]
213 20160429 p1 FreeBSD-SA-16:16.ntp
215 Fix multiple vulnerabilities of ntp.
221 The NONE and HPN patches has been removed from OpenSSH. They are
222 still available in the security/openssh-portable port.
225 r292223 changed the internal interface between the nfsd.ko and
226 nfscommon.ko modules. As such, they must both be upgraded to-gether.
227 __FreeBSD_version has been bumped because of this.
230 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
231 Kernel modules isp_2400_multi and isp_2500_multi were removed and
232 should be replaced with isp_2400 and isp_2500 modules respectively.
235 The menu.rc and loader.rc files will now be replaced during
236 upgrades. Please migrate local changes to menu.rc.local and
237 loader.rc.local instead.
240 NTP has been upgraded to 4.2.8p4.
243 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
244 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
245 and devel/kyua to version 0.20+ and adjust any calling code to work
246 with Kyuafile and kyua.
249 The polarity of Pulse Per Second (PPS) capture events with the
250 uart(4) driver has been corrected. Prior to this change the PPS
251 "assert" event corresponded to the trailing edge of a positive PPS
252 pulse and the "clear" event was the leading edge of the next pulse.
254 As the width of a PPS pulse in a typical GPS receiver is on the
255 order of 1 millisecond, most users will not notice any significant
256 difference with this change.
258 Anyone who has compensated for the historical polarity reversal by
259 configuring a negative offset equal to the pulse width will need to
260 remove that workaround.
263 From legacy ata(4) driver was removed support for SATA controllers
264 supported by more functional drivers ahci(4), siis(4) and mvs(4).
265 Kernel modules ataahci and ataadaptec were removed completely,
266 replaced by ahci and mvs modules respectively.
272 As ZFS requires more kernel stack pages than is the default on some
273 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
274 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
276 Please consider using 'options KSTACK_PAGES=X' where X is greater
277 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
280 The default Unbound configuration now enables remote control
281 using a local socket. Users who have already enabled the
282 local_unbound service should regenerate their configuration
283 by running "service local_unbound setup" as root.
286 An additional fix for the issue described in the 20150614 sendmail
287 entry below has been been committed in revision 284786.
290 The fix for the issue described in the 20150614 sendmail entry
291 below has been been committed in revision 284485. The work
292 around described in that entry is no longer needed unless the
293 default setting is overridden by a confDH_PARAMETERS configuration
294 setting of '5' or pointing to a 512 bit DH parameter file.
297 The import of openssl to address the FreeBSD-SA-15:10.openssl
298 security advisory includes a change which rejects handshakes
299 with DH parameters below 768 bits. sendmail releases prior
300 to 8.15.2 (not yet released), defaulted to a 512 bit
301 DH parameter setting for client connections. To work around
302 this interoperability, sendmail can be configured to use a
303 2048 bit DH parameter by:
305 1. Edit /etc/mail/`hostname`.mc
306 2. If a setting for confDH_PARAMETERS does not exist or
307 exists and is set to a string beginning with '5',
309 3. If a setting for confDH_PARAMETERS exists and is set to
310 a file path, create a new file with:
311 openssl dhparam -out /path/to/file 2048
312 4. Rebuild the .cf file:
313 cd /etc/mail/; make; make install
315 cd /etc/mail/; make restart
317 A sendmail patch is coming, at which time this file will be
321 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
322 defined in symlink(7); previously symlinks were silently ignored.
325 The const qualifier has been removed from iconv(3) to comply with
326 POSIX. The ports tree is aware of this from r384038 onwards.
329 At svn r275807, The default linux compat kernel ABI has been adjusted
330 to 2.6.18 in support of the linux-c6 compat ports infrastructure
331 update. If you wish to continue using the linux-f10 compat ports,
332 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
333 encouraged to update their linux-compat packages to linux-c6 during
334 their next update cycle.
336 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
339 pjdfstest has been integrated into kyua as an opt-in test suite.
340 Please see share/doc/pjdfstest/README for a more details on how to
347 The ofwfb driver, used to provide a graphics console on PowerPC when
348 using vt(4), no longer allows mmap() of all of physical memory. This
349 will prevent Xorg on PowerPC with some ATI graphics cards from
350 initializing properly unless x11-servers/xorg-server is updated to
354 The libatf-c and libatf-c++ major versions were downgraded to 0 and
355 1 respectively to match the upstream numbers. They were out of
356 sync because, when they were originally added to FreeBSD, the
357 upstream versions were not respected. These libraries are private
358 and not yet built by default, so renumbering them should be a
359 non-issue. However, unclean source trees will yield broken test
360 programs once the operator executes "make delete-old-libs" after a
363 Additionally, the atf-sh binary was made private by moving it into
364 /usr/libexec/. Already-built shell test programs will keep the
365 path to the old binary so they will break after "make delete-old"
368 If you are using WITH_TESTS=yes (not the default), wipe the object
369 tree and rebuild from scratch to prevent spurious test failures.
370 This is only needed once: the misnumbered libraries and misplaced
371 binaries have been added to OptionalObsoleteFiles.inc so they will
372 be removed during a clean upgrade.
375 The ixgbe tunables now match their sysctl counterparts, for example:
376 hw.ixgbe.enable_aim => hw.ix.enable_aim
377 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
380 The NFSv4.1 server committed by r269398 changes the internal
381 function call interfaces used between the NFS and krpc modules.
382 As such, __FreeBSD_version was bumped.
385 The default unbound configuration has been modified to address
386 issues with reverse lookups on networks that use private
387 address ranges. If you use the local_unbound service, run
388 "service local_unbound setup" as root to regenerate your
389 configuration, then "service local_unbound reload" to load the
393 It is no longer necessary to include the dwarf version in your DEBUG
394 options in your kernel config file. The bug that required it to be
395 placed in the config file has bene fixed. DEBUG should now just
396 contain -g. The build system will automatically update things
397 to do the right thing.
400 Several ABI breaking changes were merged to CTL and new iSCSI code.
401 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
402 iscsictl need to be rebuilt to work with a new kernel.
405 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
406 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
407 which differs from the behaviour controlled by this knob.)
410 On i386 and amd64 systems, the onifconsole flag is now set by default
411 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
412 as a login TTY if it is set in the bootloader as an active kernel
413 console. No changes in behavior should result otherwise. To revert to
414 the previous behavior, set ttyu0 to "off" in /etc/ttys.
417 Clang and llvm have been upgraded to 3.4.1 release.
420 Clang and llvm have been upgraded to 3.4 release.
423 If a Makefile in a tests/ directory was auto-generating a Kyuafile
424 instead of providing an explicit one, this would prevent such
425 Makefile from providing its own Kyuafile in the future during
426 NO_CLEAN builds. This has been fixed in the Makefiles but manual
427 intervention is needed to clean an objdir if you use NO_CLEAN:
428 # find /usr/obj -name Kyuafile | xargs rm -f
431 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
432 capability mode support. Please note that enabling the feature in
433 kernel is still highly recommended.
436 OpenSSH is now built with sandbox support, and will use sandbox as
437 the default privilege separation method. This requires Capsicum
438 capability mode support in kernel.
441 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
442 been deprecated and will not be part of FreeBSD 11.0 and later
443 releases. If you use this driver, please consider switching to
444 the nfe(4) driver instead.
450 The behavior of gss_pseudo_random() for the krb5 mechanism
451 has changed, for applications requesting a longer random string
452 than produced by the underlying enctype's pseudo-random() function.
453 In particular, the random string produced from a session key of
454 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
455 be different at the 17th octet and later, after this change.
456 The counter used in the PRF+ construction is now encoded as a
457 big-endian integer in accordance with RFC 4402.
458 __FreeBSD_version is bumped to 1000701.
461 The WITHOUT_ATF build knob has been removed and its functionality
462 has been subsumed into the more generic WITHOUT_TESTS. If you were
463 using the former to disable the build of the ATF libraries, you
464 should change your settings to use the latter.
467 The default version of mtree is nmtree which is obtained from
468 NetBSD. The output is generally the same, but may vary
469 slightly. If you found you need identical output adding
470 "-F freebsd9" to the command line should do the trick. For the
471 time being, the old mtree is available as fmtree.
474 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
475 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
476 1.1.4_8 and verify bsdyml not linked in, before running "make
478 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
480 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
483 The rc.d/jail script has been updated to support jail(8)
484 configuration file. The "jail_<jname>_*" rc.conf(5) variables
485 for per-jail configuration are automatically converted to
486 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
487 This is transparently backward compatible. See below about some
488 incompatibilities and rc.conf(5) manual page for more details.
490 These variables are now deprecated in favor of jail(8) configuration
491 file. One can use "rc.d/jail config <jname>" command to generate
492 a jail(8) configuration file in /var/run/jail.<jname>.conf without
493 running the jail(8) utility. The default pathname of the
494 configuration file is /etc/jail.conf and can be specified by
495 using $jail_conf or $jail_<jname>_conf variables.
497 Please note that jail_devfs_ruleset accepts an integer at
498 this moment. Please consider to rewrite the ruleset name
502 BIND has been removed from the base system. If all you need
503 is a local resolver, simply enable and start the local_unbound
504 service instead. Otherwise, several versions of BIND are
505 available in the ports tree. The dns/bind99 port is one example.
507 With this change, nslookup(1) and dig(1) are no longer in the base
508 system. Users should instead use host(1) and drill(1) which are
509 in the base system. Alternatively, nslookup and dig can
510 be obtained by installing the dns/bind-tools port.
513 With the addition of unbound(8), a new unbound user is now
514 required during installworld. "mergemaster -p" can be used to
515 add the user prior to installworld, as documented in the handbook.
518 OpenSSH is now built with DNSSEC support, and will by default
519 silently trust signed SSHFP records. This can be controlled with
520 the VerifyHostKeyDNS client configuration setting. DNSSEC support
521 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
524 The GNU Compiler Collection and C++ standard library (libstdc++)
525 are no longer built by default on platforms where clang is the system
526 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
530 The PROCDESC kernel option is now part of the GENERIC kernel
531 configuration and is required for the rwhod(8) to work.
532 If you are using custom kernel configuration, you should include
536 The API and ABI related to the Capsicum framework was modified
537 in backward incompatible way. The userland libraries and programs
538 have to be recompiled to work with the new kernel. This includes the
539 following libraries and programs, but the whole buildworld is
540 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
541 kdump, procstat, rwho, rwhod, uniq.
544 AES-NI intrinsic support has been added to gcc. The AES-NI module
545 has been updated to use this support. A new gcc is required to build
546 the aesni module on both i386 and amd64.
549 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
550 Thus "device padlock_rng" and "device rdrand_rng" should be
551 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
554 WITH_ICONV has been split into two feature sets. WITH_ICONV now
555 enables just the iconv* functionality and is now on by default.
556 WITH_LIBICONV_COMPAT enables the libiconv api and link time
557 compatability. Set WITHOUT_ICONV to build the old way.
558 If you have been using WITH_ICONV before, you will very likely
559 need to turn on WITH_LIBICONV_COMPAT.
562 INVARIANTS option now enables DEBUG for code with OpenSolaris and
563 Illumos origin, including ZFS. If you have INVARIANTS in your
564 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
566 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
567 locks if WITNESS option was set. Because that generated a lot of
568 witness(9) reports and all of them were believed to be false
569 positives, this is no longer done. New option OPENSOLARIS_WITNESS
570 can be used to achieve the previous behavior.
573 Timer values in IPv6 data structures now use time_uptime instead
574 of time_second. Although this is not a user-visible functional
575 change, userland utilities which directly use them---ndp(8),
576 rtadvd(8), and rtsold(8) in the base system---need to be updated
580 find -delete can now delete the pathnames given as arguments,
581 instead of only files found below them or if the pathname did
582 not contain any slashes. Formerly, the following error message
585 find: -delete: <path>: relative path potentially not safe
587 Deleting the pathnames given as arguments can be prevented
588 without error messages using -mindepth 1 or by changing
589 directory and passing "." as argument to find. This works in the
590 old as well as the new version of find.
593 Behavior of devfs rules path matching has been changed.
594 Pattern is now always matched against fully qualified devfs
595 path and slash characters must be explicitly matched by
596 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
597 subdirectories must be reviewed.
600 The default ARM ABI has changed to the ARM EABI. The old ABI is
601 incompatible with the ARM EABI and all programs and modules will
602 need to be rebuilt to work with a new kernel.
604 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
606 NOTE: Support for the old ABI will be removed in the future and
607 users are advised to upgrade.
610 pkg_install has been disconnected from the build if you really need it
611 you should add WITH_PKGTOOLS in your src.conf(5).
614 Most of network statistics structures were changed to be able
615 keep 64-bits counters. Thus all tools, that work with networking
616 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
619 Fix a bug that allowed a tracing process (e.g. gdb) to write
620 to a memory-mapped file in the traced process's address space
621 even if neither the traced process nor the tracing process had
622 write access to that file.
625 CVS has been removed from the base system. An exact copy
626 of the code is available from the devel/cvs port.
629 Some people report the following error after the switch to bmake:
631 make: illegal option -- J
632 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
634 *** [buildworld] Error code 2
636 this likely due to an old instance of make in
637 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
638 which src/Makefile will use that blindly, if it exists, so if
639 you see the above error:
641 rm -rf `make -V MAKEPATH`
646 Use bmake by default.
647 Whereas before one could choose to build with bmake via
648 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
649 make. The goal is to remove these knobs for 10-RELEASE.
651 It is worth noting that bmake (like gmake) treats the command
652 line as the unit of failure, rather than statements within the
653 command line. Thus '(cd some/where && dosomething)' is safer
654 than 'cd some/where; dosomething'. The '()' allows consistent
655 behavior in parallel build.
658 Fix a bug that allows NFS clients to issue READDIR on files.
661 The WITHOUT_IDEA option has been removed because
662 the IDEA patent expired.
665 The sysctl which controls TRIM support under ZFS has been renamed
666 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
670 The mergemaster command now uses the default MAKEOBJDIRPREFIX
671 rather than creating it's own in the temporary directory in
672 order allow access to bootstrapped versions of tools such as
673 install and mtree. When upgrading from version of FreeBSD where
674 the install command does not support -l, you will need to
675 install a new mergemaster command if mergemaster -p is required.
676 This can be accomplished with the command (cd src/usr.sbin/mergemaster
680 Legacy ATA stack, disabled and replaced by new CAM-based one since
681 FreeBSD 9.0, completely removed from the sources. Kernel modules
682 atadisk and atapi*, user-level tools atacontrol and burncd are
683 removed. Kernel option `options ATA_CAM` is now permanently enabled
687 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
688 and socketpair(2). Software, in particular Kerberos, may
689 automatically detect and use these during building. The resulting
690 binaries will not work on older kernels.
693 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
694 information, see the respective 20130304 entry).
697 Recent commits to callout(9) changed the size of struct callout,
698 so the KBI is probably heavily disturbed. Also, some functions
699 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
700 by macros. Every kernel module using it won't load, so rebuild
703 The ctl device has been re-enabled in GENERIC for i386 and amd64,
704 but does not initialize by default (because of the new CTL_DISABLE
705 option) to save memory. To re-enable it, remove the CTL_DISABLE
706 option from the kernel config file or set kern.cam.ctl.disable=0
707 in /boot/loader.conf.
710 The ctl device has been disabled in GENERIC for i386 and amd64.
711 This was done due to the extra memory being allocated at system
712 initialisation time by the ctl driver which was only used if
713 a CAM target device was created. This makes a FreeBSD system
714 unusable on 128MB or less of RAM.
717 A new compression method (lz4) has been merged to -HEAD. Please
718 refer to zpool-features(7) for more information.
720 Please refer to the "ZFS notes" section of this file for information
721 on upgrading boot ZFS pools.
724 A BSD-licensed patch(1) variant has been added and is installed
725 as bsdpatch, being the GNU version the default patch.
726 To inverse the logic and use the BSD-licensed one as default,
727 while having the GNU version installed as gnupatch, rebuild
728 and install world with the WITH_BSD_PATCH knob set.
731 Due to the use of the new -l option to install(1) during build
732 and install, you must take care not to directly set the INSTALL
733 make variable in your /etc/make.conf, /etc/src.conf, or on the
734 command line. If you wish to use the -C flag for all installs
735 you may be able to add INSTALL+=-C to /etc/make.conf or
739 The install(1) option -M has changed meaning and now takes an
740 argument that is a file or path to append logs to. In the
741 unlikely event that -M was the last option on the command line
742 and the command line contained at least two files and a target
743 directory the first file will have logs appended to it. The -M
744 option served little practical purpose in the last decade so its
745 use is expected to be extremely rare.
748 After switching to Clang as the default compiler some users of ZFS
749 on i386 systems started to experience stack overflow kernel panics.
750 Please consider using 'options KSTACK_PAGES=4' in such configurations.
753 GEOM_LABEL now mangles label names read from file system metadata.
754 Mangling affect labels containing spaces, non-printable characters,
755 '%' or '"'. Device names in /etc/fstab and other places may need to
759 By default, only the 10 most recent kernel dumps will be saved. To
760 restore the previous behaviour (no limit on the number of kernel dumps
761 stored in the dump directory) add the following line to /etc/rc.conf:
766 With the addition of auditdistd(8), a new auditdistd user is now
767 required during installworld. "mergemaster -p" can be used to
768 add the user prior to installworld, as documented in the handbook.
771 The sin6_scope_id member variable in struct sockaddr_in6 is now
772 filled by the kernel before passing the structure to the userland via
773 sysctl or routing socket. This means the KAME-specific embedded scope
774 id in sin6_addr.s6_addr[2] is always cleared in userland application.
775 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
776 __FreeBSD_version is bumped to 1000025.
779 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
780 This means that the world and kernel will be compiled with clang
781 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
782 and /usr/bin/cpp. To disable this behavior and revert to building
783 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
784 of current may need to bootstrap WITHOUT_CLANG first if the clang
785 build fails (its compatibility window doesn't extend to the 9 stable
789 The IPFIREWALL_FORWARD kernel option has been removed. Its
790 functionality now turned on by default.
793 The ZERO_COPY_SOCKET kernel option has been removed and
794 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
795 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
796 mechanism which is not safe and may result in kernel crashes.
797 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
798 driver supports disposeable external page sized mbuf storage.
799 Proper replacements for both zero-copy mechanisms are under
800 consideration and will eventually lead to complete removal
801 of the two kernel options.
804 The IPv4 network stack has been converted to network byte
805 order. The following modules need to be recompiled together
806 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
807 pf(4), ipfw(4), ng_ipfw(4), stf(4).
810 Support for non-MPSAFE filesystems was removed from VFS. The
811 VFS_VERSION was bumped, all filesystem modules shall be
815 All the non-MPSAFE filesystems have been disconnected from
816 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
817 portalfs, smbfs, xfs.
820 The interface cloning API and ABI has changed. The following
821 modules need to be recompiled together with kernel:
822 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
823 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
824 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
827 The sdhci driver was split in two parts: sdhci (generic SD Host
828 Controller logic) and sdhci_pci (actual hardware driver).
829 No kernel config modifications are required, but if you
830 load sdhc as a module you must switch to sdhci_pci instead.
833 Import the FUSE kernel and userland support into base system.
836 The GNU sort(1) program has been removed since the BSD-licensed
837 sort(1) has been the default for quite some time and no serious
838 problems have been reported. The corresponding WITH_GNU_SORT
842 The pfil(9) API/ABI for AF_INET family has been changed. Packet
843 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
847 The net80211(4) ABI has been changed to allow for improved driver
848 PS-POLL and power-save support. All wireless drivers need to be
849 recompiled to work with the new kernel.
852 The random(4) support for the VIA hardware random number
853 generator (`PADLOCK') is no longer enabled unconditionally.
854 Add the padlock_rng device in the custom kernel config if
855 needed. The GENERIC kernels on i386 and amd64 do include the
856 device, so the change only affects the custom kernel
860 The pf(4) packet filter ABI has been changed. pfctl(8) and
861 snmp_pf module need to be recompiled to work with new kernel.
864 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
865 to -HEAD. Pools that have empty_bpobj in active state can not be
866 imported read-write with ZFS implementations that do not support
867 this feature. For more information read the zpool-features(5)
871 The sparc64 ZFS loader has been changed to no longer try to auto-
872 detect ZFS providers based on diskN aliases but now requires these
873 to be explicitly listed in the OFW boot-device environment variable.
876 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
877 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
878 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
881 The following sysctls and tunables have been renamed for consistency
882 with other variables:
883 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
884 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
887 The sort utility has been replaced with BSD sort. For now, GNU sort
888 is also available as "gnusort" or the default can be set back to
889 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
890 installed as "bsdsort".
893 A new version of ZFS (pool version 5000) has been merged to -HEAD.
894 Starting with this version the old system of ZFS pool versioning
895 is superseded by "feature flags". This concept enables forward
896 compatibility against certain future changes in functionality of ZFS
897 pools. The first read-only compatible "feature flag" for ZFS pools
898 is named "com.delphix:async_destroy". For more information
899 read the new zpool-features(5) manual page.
900 Please refer to the "ZFS notes" section of this file for information
901 on upgrading boot ZFS pools.
904 The malloc(3) implementation embedded in libc now uses sources imported
905 as contrib/jemalloc. The most disruptive API change is to
906 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
907 delete it prior to installworld, and optionally re-create it using the
908 new format after rebooting. See malloc.conf(5) for details
909 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
913 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
914 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
915 now spelled mips. This is to aid compatibility with third-party
916 software that expects this naming scheme in uname(3). Little-endian
917 settings are unchanged. If you are updating a big-endian mips64 machine
918 from before this change, you may need to set MACHINE_ARCH=mips64 in
919 your environment before the new build system will recognize your machine.
922 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
926 Now unix domain sockets behave "as expected" on nullfs(5). Previously
927 nullfs(5) did not pass through all behaviours to the underlying layer,
928 as a result if we bound to a socket on the lower layer we could connect
929 only to the lower path; if we bound to the upper layer we could connect
930 only to the upper path. The new behavior is one can connect to both the
931 lower and the upper paths regardless what layer path one binds to.
934 The getifaddrs upgrade path broken with 20111215 has been restored.
935 If you have upgraded in between 20111215 and 20120209 you need to
936 recompile libc again with your kernel. You still need to recompile
937 world to be able to configure CARP but this restriction already
941 The set_rcvar() function has been removed from /etc/rc.subr. All
942 base and ports rc.d scripts have been updated, so if you have a
943 port installed with a script in /usr/local/etc/rc.d you can either
944 hand-edit the rcvar= line, or reinstall the port.
946 An easy way to handle the mass-update of /etc/rc.d:
947 rm /etc/rc.d/* && mergemaster -i
950 panic(9) now stops other CPUs in the SMP systems, disables interrupts
951 on the current CPU and prevents other threads from running.
952 This behavior can be reverted using the kern.stop_scheduler_on_panic
954 The new behavior can be incompatible with kern.sync_on_panic.
957 The carp(4) facility has been changed significantly. Configuration
958 of the CARP protocol via ifconfig(8) has changed, as well as format
959 of CARP events submitted to devd(8) has changed. See manual pages
960 for more information. The arpbalance feature of carp(4) is currently
961 not supported anymore.
963 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
964 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
965 need to be recompiled.
968 The acpi_wmi(4) status device /dev/wmistat has been renamed to
972 The option VFS_ALLOW_NONMPSAFE option has been added in order to
973 explicitely support non-MPSAFE filesystems.
974 It is on by default for all supported platform at this present
978 The broken amd(4) driver has been replaced with esp(4) in the amd64,
979 i386 and pc98 GENERIC kernel configuration files.
982 sysinstall has been removed
985 The stable/9 branch created in subversion. This corresponds to the
986 RELENG_9 branch in CVS.
989 This commit modifies vfs_register() so that it uses a hash
990 calculation to set vfc_typenum, which is enabled by default.
991 The first time a system is booted after this change, the
992 vfc_typenum values will change for all file systems. The
993 main effect of this is a change to the NFS server file handles
994 for file systems that use vfc_typenum in their fsid, such as ZFS.
995 It will, however, prevent vfc_typenum from changing when file
996 systems are loaded in a different order for subsequent reboots.
997 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
998 until you are ready to remount all NFS clients after a reboot.
1001 Bump the shared library version numbers for libraries that
1002 do not use symbol versioning, have changed the ABI compared
1003 to stable/8 and which shared library version was not bumped.
1004 Done as part of 9.0-RELEASE cycle.
1007 During the merge of Capsicum features, the fget(9) KPI was modified.
1008 This may require the rebuilding of out-of-tree device drivers --
1009 issues have been reported specifically with the nVidia device driver.
1010 __FreeBSD_version is bumped to 900041.
1012 Also, there is a period between 20110811 and 20110814 where the
1013 special devices /dev/{stdin,stdout,stderr} did not work correctly.
1014 Building world from a kernel during that window may not work.
1017 The packet filter (pf) code has been updated to OpenBSD 4.5.
1018 You need to update userland tools to be in sync with kernel.
1019 This update breaks backward compatibility with earlier pfsync(4)
1020 versions. Care must be taken when updating redundant firewall setups.
1023 The following sysctls and tunables are retired on x86 platforms:
1025 machdep.hlt_logical_cpus
1026 The following sysctl is retired:
1027 machdep.hyperthreading_allowed
1028 The sysctls were supposed to provide a way to dynamically offline and
1029 online selected CPUs on x86 platforms, but the implementation has not
1030 been reliable especially with SCHED_ULE scheduler.
1031 machdep.hyperthreading_allowed tunable is still available to ignore
1032 hyperthreading CPUs at OS level.
1033 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
1034 where X is an APIC ID of a CPU. Be advised, though, that disabling
1035 CPUs in non-uniform fashion will result in non-uniform topology and
1036 may lead to sub-optimal system performance with SCHED_ULE, which is
1037 a default scheduler.
1040 cpumask_t type is retired and cpuset_t is used in order to describe
1044 Changes to ifconfig(8) for dynamic address family detection mandate
1045 that you are running a kernel of 20110525 or later. Make sure to
1046 follow the update procedure to boot a new kernel before installing
1050 Support for sun4v architecture is officially dropped
1053 Several KPI breaking changes have been committed to the mii(4) layer,
1054 the PHY drivers and consequently some Ethernet drivers using mii(4).
1055 This means that miibus.ko and the modules of the affected Ethernet
1056 drivers need to be recompiled.
1058 Note to kernel developers: Given that the OUI bit reversion problem
1059 was fixed as part of these changes all mii(4) commits related to OUIs,
1060 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
1061 handling, no longer can be merged verbatim to stable/8 and previous
1065 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
1066 into their kernel configurations along with 'device pci'.
1069 The default NFS client is now the new NFS client, so fstype "newnfs"
1070 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
1071 Although mounts via fstype "nfs" will usually work without userland
1072 changes, it is recommended that the mount(8) and mount_nfs(8)
1073 commands be rebuilt from sources and that a link to mount_nfs called
1074 mount_oldnfs be created. The new client is compiled into the
1075 kernel with "options NFSCL" and this is needed for diskless root
1076 file systems. The GENERIC kernel configs have been changed to use
1077 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
1078 To use the regular/old client, you can "mount -t oldnfs ...". For
1079 a diskless root file system, you must also include a line like:
1081 vfs.root.mountfrom="oldnfs:"
1083 in the boot/loader.conf on the root fs on the NFS server to make
1084 a diskless root fs use the old client.
1087 The GENERIC kernels for all architectures now default to the new
1088 CAM-based ATA stack. It means that all legacy ATA drivers were
1089 removed and replaced by respective CAM drivers. If you are using
1090 ATA device names in /etc/fstab or other places, make sure to update
1091 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
1092 where 'Y's are the sequential numbers starting from zero for each type
1093 in order of detection, unless configured otherwise with tunables,
1094 see cam(4)). There will be symbolic links created in /dev/ to map
1095 old adX devices to the respective adaY. They should provide basic
1096 compatibility for file systems mounting in most cases, but they do
1097 not support old user-level APIs and do not have respective providers
1098 in GEOM. Consider using updated management tools with new device names.
1100 It is possible to load devices ahci, ata, siis and mvs as modules,
1101 but option ATA_CAM should remain in kernel configuration to make ata
1102 module work as CAM driver supporting legacy ATA controllers. Device ata
1103 still can be used in modular fashion (atacore + ...). Modules atadisk
1104 and atapi* are not used and won't affect operation in ATA_CAM mode.
1105 Note that to use CAM-based ATA kernel should include CAM devices
1106 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1107 them are parts of the cam module.
1109 ataraid(4) functionality is now supported by the RAID GEOM class.
1110 To use it you can load geom_raid kernel module and use graid(8) tool
1111 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1113 No kernel config options or code have been removed, so if a problem
1114 arises, please report it and optionally revert to the old ATA stack.
1115 In order to do it you can remove from the kernel config:
1120 , and instead add back:
1121 device atadisk # ATA disk drives
1122 device ataraid # ATA RAID drives
1123 device atapicd # ATAPI CDROM drives
1124 device atapifd # ATAPI floppy drives
1125 device atapist # ATAPI tape drives
1128 The default NFS server has been changed to the new server, which
1129 was referred to as the experimental server. If you need to switch
1130 back to the old NFS server, you must now put the "-o" option on
1131 both the mountd and nfsd commands. This can be done using the
1132 mountd_flags and nfs_server_flags rc.conf variables until an
1133 update to the rc scripts is committed, which is coming soon.
1136 The GNU Objective-C runtime library (libobjc), and other Objective-C
1137 related components have been removed from the base system. If you
1138 require an Objective-C library, please use one of the available ports.
1141 ath(4) has been split into bus- and device- modules. if_ath contains
1142 the HAL, the TX rate control and the network device code. if_ath_pci
1143 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1144 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1145 in order to use ath on everything else.
1147 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1148 need to load if_ath and if_ath_pci for ath(4) operation.
1151 As part of the replacement of sysinstall, the process of building
1152 release media has changed significantly. For details, please re-read
1153 release(7), which has been updated to reflect the new build process.
1156 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1157 is the last available version under GPLv2. It brings a number of new
1158 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1159 4.1 and SSE 4.2), better support for powerpc64, a number of new
1160 directives, and lots of other small improvements. See the ChangeLog
1161 file in contrib/binutils for the full details.
1164 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1165 compliant, and will now use half of hash for authentication.
1166 This will break interoperability with all stacks (including all
1167 actual FreeBSD versions) who implement
1168 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1170 The only workaround with such peers is to use another HMAC
1171 algorithm for IPsec ("phase 2") authentication.
1174 Remove the uio_yield prototype and symbol. This function has
1175 been misnamed since it was introduced and should not be
1176 globally exposed with this name. The equivalent functionality
1177 is now available using kern_yield(curthread->td_user_pri).
1178 The function remains undocumented.
1181 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1182 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1183 for scalar sysctls is defined but disabled. Code that needs
1184 UQUAD to pass the type checking that must compile on older
1185 systems where the define is not present can check against
1186 __FreeBSD_version >= 900030.
1188 The system dialog(1) has been replaced with a new version previously
1189 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1190 with the previous version, but the libdialog associated with it has
1191 a largely incompatible API. As such, the original version of libdialog
1192 will be kept temporarily as libodialog, until its base system consumers
1193 are replaced or updated. Bump __FreeBSD_version to 900030.
1196 If you are trying to run make universe on a -stable system, and you get
1197 the following warning:
1198 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1199 unknown. config(8) likely too old."
1200 or something similar to it, then you must upgrade your -stable system
1201 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1202 stable/8) or build the config from the latest stable/8 branch and
1203 install it on your system.
1205 Prior to this date, building a current universe on 8-stable system from
1206 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1207 error in the first kernel build phase. A new config on those old
1208 systems will fix that problem for older versions of -current.
1211 The TCP stack has been modified to allow Khelp modules to interact with
1212 it via helper hook points and store per-connection data in the TCP
1213 control block. Bump __FreeBSD_version to 900029. User space tools that
1214 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1218 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1219 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1220 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1221 to take advantage of it instead of using custom implementations. This
1222 means that these drivers now no longer unconditionally advertise
1223 support for flow control but only do so if flow control is a selected
1224 media option. This was implemented in the generic support that way in
1225 order to allow flow control to be switched on and off via ifconfig(8)
1226 with the PHY specific default to typically off in order to protect
1227 from unwanted effects. Consequently, if you used flow control with
1228 one of the above mentioned drivers you now need to explicitly enable
1229 it, for example via:
1230 ifconfig bge0 media auto mediaopt flowcontrol
1232 Along with the above mentioned changes generic support for setting
1233 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1234 e1000phy(4) as well as ip1000phy(4) have been converted to take
1235 advantage of it. This means that these drivers now no longer take the
1236 link0 parameter for selecting master mode but the master media option
1237 has to be used instead, for example like in the following:
1238 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1240 Selection of master mode now is also available with all other PHY
1241 drivers supporting 1000baseT.
1244 The TCP stack has received a significant update to add support for
1245 modularised congestion control and generally improve the clarity of
1246 congestion control decisions. Bump __FreeBSD_version to 900025. User
1247 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1248 sockstat) need to be recompiled.
1251 The man(1) utility has been replaced by a new version that no longer
1252 uses /etc/manpath.config. Please consult man.conf(5) for how to
1253 migrate local entries to the new format.
1256 The copyright strings printed by login(1) and sshd(8) at the time of a
1257 new connection have been removed to follow other operating systems and
1261 A workaround for a fixed ld bug has been removed in kernel code,
1262 so make sure that your system ld is built from sources after
1263 revision 210245 from 2010-07-19 (r211583 if building head kernel
1264 on stable/8, r211584 for stable/7; both from 2010-08-21).
1265 A symptom of incorrect ld version is different addresses for
1266 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1269 The $ipv6_prefer variable in rc.conf(5) has been split into
1270 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1272 The $ip6addrctl_policy is a variable to choose a pre-defined
1273 address selection policy set by ip6addrctl(8). A value
1274 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1277 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1278 flag (see an entry of 20090926) is set on an interface with no
1279 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1280 security reason. If you want IPv6 link-local address on all
1281 interfaces by default, set this to "YES".
1283 The old ipv6_prefer="YES" is equivalent to
1284 ipv6_activate_all_interfaces="YES" and
1285 ip6addrctl_policy="ipv6_prefer".
1288 DTrace has grown support for userland tracing. Due to this, DTrace is
1289 now i386 and amd64 only.
1290 dtruss(1) is now installed by default on those systems and a new
1291 kernel module is needed for userland tracing: fasttrap.
1292 No changes to your kernel config file are necessary to enable
1293 userland tracing, but you might consider adding 'STRIP=' and
1294 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1295 to have informative userland stack traces in DTrace (ustack).
1298 The acpi_aiboost(4) driver has been removed in favor of the new
1299 aibs(4) driver. You should update your kernel configuration file.
1302 BSD grep has been imported to the base system and it is built by
1303 default. It is completely BSD licensed, highly GNU-compatible, uses
1304 less memory than its GNU counterpart and has a small codebase.
1305 However, it is slower than its GNU counterpart, which is mostly
1306 noticeable for larger searches, for smaller ones it is measurable
1307 but not significant. The reason is complex, the most important factor
1308 is that we lack a modern and efficient regex library and GNU
1309 overcomes this by optimizing the searches internally. Future work
1310 on improving the regex performance is planned, for the meantime,
1311 users that need better performance, can build GNU grep instead by
1312 setting the WITH_GNU_GREP knob.
1315 Due to the import of powerpc64 support, all existing powerpc kernel
1316 configuration files must be updated with a machine directive like this:
1317 machine powerpc powerpc
1319 In addition, an updated config(8) is required to build powerpc kernels
1323 A new version of ZFS (version 15) has been merged to -HEAD.
1324 This version uses a python library for the following subcommands:
1325 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1326 For full functionality of these commands the following port must
1327 be installed: sysutils/py-zfs
1330 'vm_page's are now hashed by physical address to an array of mutexes.
1331 Currently this is only used to serialize access to hold_count. Over
1332 time the page queue mutex will be peeled away. This changes the size
1333 of pmap on every architecture. And requires all callers of vm_page_hold
1334 and vm_page_unhold to be updated.
1337 WITH_CTF can now be specified in src.conf (not recommended, there
1338 are some problems with static executables), make.conf (would also
1339 affect ports which do not use GNU make and do not override the
1340 compile targets) or in the kernel config (via "makeoptions
1342 When WITH_CTF was specified there before this was silently ignored,
1343 so make sure that WITH_CTF is not used in places which could lead
1344 to unwanted behavior.
1347 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1348 to allow 32-bit compatibility on non-x86 platforms. All kernel
1349 configurations on amd64 and ia64 platforms using these options must
1350 be modified accordingly.
1353 The utmp user accounting database has been replaced with utmpx,
1354 the user accounting interface standardized by POSIX.
1355 Unfortunately the semantics of utmp and utmpx don't match,
1356 making it practically impossible to support both interfaces.
1357 The user accounting database is used by tools like finger(1),
1358 last(1), talk(1), w(1) and ac(8).
1360 All applications in the base system use utmpx. This means only
1361 local binaries (e.g. from the ports tree) may still use these
1362 utmp database files. These applications must be rebuilt to make
1365 After the system has been upgraded, it is safe to remove the old
1366 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1367 assuming their contents is of no importance anymore. Old wtmp
1368 databases can only be used by last(1) and ac(8) after they have
1369 been converted to the new format using wtmpcvt(1).
1372 Introduce the kernel thread "deadlock resolver" (which can be enabled
1373 via the DEADLKRES option, see NOTES for more details) and the
1374 sleepq_type() function for sleepqueues.
1377 The rc.firewall and rc.firewall6 were unified, and
1378 rc.firewall6 and rc.d/ip6fw were removed.
1379 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1380 variables are obsoleted. Instead, the following new rc
1381 variables are added to rc.d/ipfw:
1383 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1384 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1385 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1387 The meanings correspond to the relevant IPv4 variables.
1393 The default terminal emulation for syscons(4) has been changed
1394 from cons25 to xterm on all platforms except pc98. This means
1395 that the /etc/ttys file needs to be updated to ensure correct
1396 operation of applications on the console.
1398 The terminal emulation style can be toggled per window by using
1399 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1400 options can be used to change the compile-time default back to
1403 To prevent graphical artifacts, make sure the TERM environment
1404 variable is set to match the terminal emulation that is being
1405 performed by syscons(4).
1408 The layout of the structure ieee80211req_scan_result has changed.
1409 Applications that require wireless scan results (e.g. ifconfig(8))
1410 from net80211 need to be recompiled.
1412 Applications such as wpa_supplicant(8) may require a full world
1413 build without using NO_CLEAN in order to get synchronized with the
1417 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1418 There's one kernel module for each firmware. Adding "device iwnfw"
1419 to the kernel configuration file means including all three firmware
1420 images inside the kernel. If you want to include just the one for
1421 your wireless card, use the devices iwn4965fw, iwn5000fw or
1425 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1426 into rc.d/netif. The changes are the following:
1428 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1429 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1430 Note that both variables need the "inet6" keyword at the head.
1432 Do not set $ipv6_network_interfaces manually if you do not
1433 understand what you are doing. It is not needed in most cases.
1435 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1438 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1439 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1441 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1442 all configured interfaces have "inet6 accept_rtadv" in the
1443 $ifconfig_IF_ipv6. These are for backward compatibility.
1445 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1446 functionality of interfaces with no corresponding
1447 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1448 and the default address selection policy of ip6addrctl(8)
1449 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1450 Note that if you want to configure IPv6 functionality on the
1451 disabled interfaces after boot, first you need to clear the flag by
1452 using ifconfig(8) like:
1454 ifconfig em0 inet6 -ifdisabled
1456 If YES, the default address selection policy is set as
1459 The default value of $ipv6_prefer is NO.
1461 4. If your system need to receive Router Advertisement messages,
1462 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1463 scripts automatically invoke rtsol(8) when the interface becomes
1464 UP. The Router Advertisement messages are used for SLAAC
1465 (State-Less Address AutoConfiguration).
1468 802.11s D3.03 support was committed. This is incompatible with the
1469 previous code, which was based on D3.0.
1472 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1473 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1474 control whether accepting Router Advertisement messages or not.
1475 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1476 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1477 The ifconfig(8) utility now supports these flags.
1480 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1481 mount(8) and -a option for df(1) to see them.
1484 The old tunable hw.bus.devctl_disable has been superseded by
1485 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1486 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1490 Remove the option STOP_NMI. The default action is now to use NMI only
1491 for KDB via the newly introduced function stop_cpus_hard() and
1492 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1495 The stable/8 branch created in subversion. This corresponds to the
1496 RELENG_8 branch in CVS.
1499 Bump the shared library version numbers for all libraries that do not
1500 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1501 __FreeBSD_version to 800105.
1504 Due to changes in the implementation of virtual network stack support,
1505 all network-related kernel modules must be recompiled. As this change
1506 breaks the ABI, bump __FreeBSD_version to 800104.
1509 The TOE interface to the TCP syncache has been modified to remove
1510 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1511 The cxgb driver is the only TOE consumer affected by this change, and
1512 needs to be recompiled along with the kernel. As this change breaks
1513 the ABI, bump __FreeBSD_version to 800103.
1516 Padding has been added to struct tcpcb, sackhint and tcpstat in
1517 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1518 maintaining the ABI. However, this change breaks the ABI, so bump
1519 __FreeBSD_version to 800102. User space tools that rely on the size of
1520 any of these structs (e.g. sockstat) need to be recompiled.
1523 The NFS_LEGACYRPC option has been removed along with the old kernel
1524 RPC implementation that this option selected. Kernel configurations
1525 may need to be adjusted.
1528 The network interface device nodes at /dev/net/<interface> have been
1529 removed. All ioctl operations can be performed the normal way using
1530 routing sockets. The kqueue functionality can generally be replaced
1531 with routing sockets.
1534 The documentation from the FreeBSD Documentation Project (Handbook,
1535 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1536 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1539 The ABI of various structures related to the SYSV IPC API have been
1540 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1541 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1545 Layout of struct vnet has changed as routing related variables were
1546 moved to their own Vimage module. Modules need to be recompiled. Bump
1547 __FreeBSD_version to 800099.
1550 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1551 respectively. As long as no more than 16 groups per process are used,
1552 no changes should be visible. When more than 16 groups are used, old
1553 binaries may fail if they call getgroups() or getgrouplist() with
1554 statically sized storage. Recompiling will work around this, but
1555 applications should be modified to use dynamically allocated storage
1556 for group arrays as POSIX.1-2008 does not cap an implementation's
1557 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1559 NFS and portalfs mounts may also be affected as the list of groups is
1560 truncated to 16. Users of NFS who use more than 16 groups, should
1561 take care that negative group permissions are not used on the exported
1562 file systems as they will not be reliable unless a GSSAPI based
1563 authentication method is used.
1566 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1567 option compiles in the support for adaptive spinning for lockmgrs
1568 which want to enable it. The lockinit() function now accepts the flag
1569 LK_ADAPTIVE in order to make the lock object subject to adaptive
1570 spinning when both held in write and read mode.
1573 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1574 changed. User applications that use this ioctl need to be rebuilt.
1577 The layout of struct thread has changed. Kernel and modules need to
1581 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1582 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1585 window(1) has been removed from the base system. It can now be
1586 installed from ports. The port is called misc/window.
1589 The way we are storing and accessing `routing table' entries has
1590 changed. Programs reading the FIB, like netstat, need to be
1594 A new netisr implementation has been added for FreeBSD 8. Network
1595 file system modules, such as igmp, ipdivert, and others, should be
1597 Bump __FreeBSD_version to 800096.
1600 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1604 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1605 Bump __FreeBSD_version to 800094.
1608 Add mnt_xflag field to 'struct mount'. File system modules need to be
1610 Bump __FreeBSD_version to 800093.
1613 The compiling option ADAPTIVE_SX has been retired while it has been
1614 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1615 The KPI for sx_init_flags() changes as accepting flags:
1616 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1617 been introduced in order to handle the reversed logic.
1618 Bump __FreeBSD_version to 800092.
1621 Add support for hierarchical jails. Remove global securelevel.
1622 Bump __FreeBSD_version to 800091.
1625 The layout of struct vnet_net has changed, therefore modules
1627 Bump __FreeBSD_version to 800090.
1630 The newly imported zic(8) produces a new format in the output. Please
1631 run tzsetup(8) to install the newly created data to /etc/localtime.
1634 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1635 hw.usb.* and is now consistent again with previous releases.
1638 802.11 monitor mode support was revised and driver api's were changed.
1639 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1640 of DLT_IEEE802_11. No user-visible data structures were changed but
1641 applications that use DLT_IEEE802_11 may require changes.
1642 Bump __FreeBSD_version to 800088.
1645 The layout of the following structs has changed: sysctl_oid,
1646 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1647 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1648 panics may be experienced. World rebuild is required for
1649 correctly checking networking state from userland.
1650 Bump __FreeBSD_version to 800085.
1653 MLDv2 and Source-Specific Multicast (SSM) have been merged
1654 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1655 The implementation of SSM within FreeBSD's IPv6 stack closely
1656 follows the IPv4 implementation.
1658 For kernel developers:
1660 * The most important changes are that the ip6_output() and
1661 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1662 and this lock has been downgraded to a non-recursive mutex.
1664 * As with the changes to the IPv4 stack to support SSM, filtering
1665 of inbound multicast traffic must now be performed by transport
1666 protocols within the IPv6 stack. This does not apply to TCP and
1667 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1669 * The KPIs used by IPv6 multicast are similar to those used by
1670 the IPv4 stack, with the following differences:
1671 * im6o_mc_filter() is analogous to imo_multicast_filter().
1672 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1673 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1674 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1675 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1676 for MLDv1 have an additional 'timer' argument which is used to
1677 jitter the initial membership report for the solicited-node
1678 multicast membership on-link.
1679 * This is not strictly needed for MLDv2, which already jitters
1680 its report transmissions. However, the 'timer' argument is
1681 preserved in case MLDv1 is active on the interface.
1683 * The KAME linked-list based IPv6 membership implementation has
1684 been refactored to use a vector similar to that used by the IPv4
1686 Code which maintains a list of its own multicast memberships
1687 internally, e.g. carp, has been updated to reflect the new
1690 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1691 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1692 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1693 implementation constraint which needs to be addressed in HEAD.
1695 For application developers:
1697 * The changes are broadly similar to those made for the IPv4
1700 * The use of IPv4 and IPv6 multicast socket options on the same
1701 socket, using mapped addresses, HAS NOT been tested or supported.
1703 * There are a number of issues with the implementation of various
1704 IPv6 multicast APIs which need to be resolved in the API surface
1705 before the implementation is fully compatible with KAME userland
1706 use, and these are mostly to do with interface index treatment.
1708 * The literature available discusses the use of either the delta / ASM
1709 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1710 using setsourcefilter(3)/getsourcefilter(3). For more information
1711 please refer to RFC 3768, 'Socket Interface Extensions for
1712 Multicast Source Filters'.
1714 * Applications which use the published RFC 3678 APIs should be fine.
1716 For systems administrators:
1718 * The mtest(8) utility has been refactored to support IPv6, in
1719 addition to IPv4. Interface addresses are no longer accepted
1720 as arguments, their names must be used instead. The utility
1721 will map the interface name to its first IPv4 address as
1722 returned by getifaddrs(3).
1724 * The ifmcstat(8) utility has also been updated to print the MLDv2
1725 endpoint state and source filter lists via sysctl(3).
1727 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1728 loopback of IPv6 multicast datagrams by default; it defaults to 1
1729 to preserve the existing behaviour. Disabling multicast loopback is
1730 recommended for optimal system performance.
1732 * The IPv6 MROUTING code has been changed to examine this sysctl
1733 instead of attempting to perform a group lookup before looping
1734 back forwarded datagrams.
1736 Bump __FreeBSD_version to 800084.
1739 Implement low-level Bluetooth HCI API.
1740 Bump __FreeBSD_version to 800083.
1743 The layout of struct malloc_type, used by modules to register new
1744 memory allocation types, has changed. Most modules will need to
1745 be rebuilt or panics may be experienced.
1746 Bump __FreeBSD_version to 800081.
1749 Anticipate overflowing inp_flags - add inp_flags2.
1750 This changes most offsets in inpcb, so checking v4 connection
1751 state will require a world rebuild.
1752 Bump __FreeBSD_version to 800080.
1755 Add an llentry to struct route and struct route_in6. Modules
1756 embedding a struct route will need to be recompiled.
1757 Bump __FreeBSD_version to 800079.
1760 The size of rt_metrics_lite and by extension rtentry has changed.
1761 Networking administration apps will need to be recompiled.
1762 The route command now supports show as an alias for get, weighting
1763 of routes, sticky and nostick flags to alter the behavior of stateful
1765 Bump __FreeBSD_version to 800078.
1768 Do not use Giant for kbdmux(4) locking. This is wrong and
1769 apparently causing more problems than it solves. This will
1770 re-open the issue where interrupt handlers may race with
1771 kbdmux(4) in polling mode. Typical symptoms include (but
1772 not limited to) duplicated and/or missing characters when
1773 low level console functions (such as gets) are used while
1774 interrupts are enabled (for example geli password prompt,
1775 mountroot prompt etc.). Disabling kbdmux(4) may help.
1778 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1779 kernel modules referencing any of the above need to be recompiled.
1780 Bump __FreeBSD_version to 800075.
1783 GEOM_PART has become the default partition slicer for storage devices,
1784 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1785 introduces some changes:
1787 MSDOS/EBR: the devices created from MSDOS extended partition entries
1788 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1789 to devices with offset-based names. fstabs may need to be modified.
1791 BSD: the "geometry does not match label" warning is harmless in most
1792 cases but it points to problems in file system misalignment with
1793 disk geometry. The "c" partition is now implicit, covers the whole
1794 top-level drive and cannot be (mis)used by users.
1796 General: Kernel dumps are now not allowed to be written to devices
1797 whose partition types indicate they are meant to be used for file
1798 systems (or, in case of MSDOS partitions, as something else than
1801 Most of these changes date approximately from 200812.
1804 The uscanner(4) driver has been removed from the kernel. This follows
1805 Linux removing theirs in 2.6 and making libusb the default interface
1806 (supported by sane).
1809 The multicast forwarding code has been cleaned up. netstat(1)
1810 only relies on KVM now for printing bandwidth upcall meters.
1811 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1812 ip6_mroute_mod respectively. The config(5) options for statically
1813 compiling this code remain the same, i.e. 'options MROUTING'.
1816 Support for the IFF_NEEDSGIANT network interface flag has been
1817 removed, which means that non-MPSAFE network device drivers are no
1818 longer supported. In particular, if_ar, if_sr, and network device
1819 drivers from the old (legacy) USB stack can no longer be built or
1823 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1824 a bunch of new language catalog files have also been added.
1825 This means that some common libc messages are now localized and
1826 they depend on the LC_MESSAGES environmental variable.
1829 The k8temp(4) driver has been renamed to amdtemp(4) since
1830 support for Family 10 and Family 11 CPU families was added.
1833 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1834 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1836 For kernel developers, the most important changes are that the
1837 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1838 and this lock has been downgraded to a non-recursive mutex.
1840 Transport protocols (UDP, Raw IP) are now responsible for filtering
1841 inbound multicast traffic according to group membership and source
1842 filters. The imo_multicast_filter() KPI exists for this purpose.
1843 Transports which do not use multicast (SCTP, TCP) already reject
1844 multicast by default. Forwarding and receive performance may improve
1845 as a mutex acquisition is no longer needed in the ip_input()
1846 low-level input path. in_addmulti() and in_delmulti() are shimmed
1847 to new KPIs which exist to support SSM in-kernel.
1849 For application developers, it is recommended that loopback of
1850 multicast datagrams be disabled for best performance, as this
1851 will still cause the lock to be taken for each looped-back
1852 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1853 be tuned to 0 to disable loopback by default; it defaults to 1
1854 to preserve the existing behaviour.
1856 For systems administrators, to obtain best performance with
1857 multicast reception and multiple groups, it is always recommended
1858 that a card with a suitably precise hash filter is used. Hash
1859 collisions will still result in the lock being taken within the
1860 transport protocol input path to check group membership.
1862 If deploying FreeBSD in an environment with IGMP snooping switches,
1863 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1864 enabled; this forces 224.0.0.0/24 group membership to be announced
1867 The size of 'struct igmpstat' has changed; netstat needs to be
1868 recompiled to reflect this.
1869 Bump __FreeBSD_version to 800070.
1872 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1873 updated to use it. This requires a buildworld/installworld in order to
1874 update the library and dependencies (usbconfig, etc). Its advisable to
1875 rebuild all ports which uses libusb. More specific directions are given
1876 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1877 libusb are no longer required and can be removed.
1880 A workaround is committed to allow the creation of System V shared
1881 memory segment of size > 2 GB on the 64-bit architectures.
1882 Due to a limitation of the existing ABI, the shm_segsz member
1883 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1884 wrong for large segments. Note that limits must be explicitly
1885 raised to allow such segments to be created.
1888 The layout of struct ifnet has changed, requiring a rebuild of all
1889 network device driver modules.
1892 The /dev handling for the new USB stack has changed, a
1893 buildworld/installworld is required for libusb20.
1896 The new USB2 stack has now been permanently moved in and all kernel and
1897 module names reverted to their previous values (eg, usb, ehci, ohci,
1898 ums, ...). The old usb stack can be compiled in by prefixing the name
1899 with the letter 'o', the old usb modules have been removed.
1900 Updating entry 20090216 for xorg and 20090215 for libmap may still
1904 The rc.conf(5) option if_up_delay has been renamed to
1905 defaultroute_delay to better reflect its purpose. If you have
1906 customized this setting in /etc/rc.conf you need to update it to
1910 xorg 7.4 wants to configure its input devices via hald which does not
1911 yet work with USB2. If the keyboard/mouse does not work in xorg then
1913 Option "AllowEmptyInput" "off"
1914 to your ServerLayout section. This will cause X to use the configured
1915 kbd and mouse sections from your xorg.conf.
1918 The GENERIC kernels for all architectures now default to the new USB2
1919 stack. No kernel config options or code have been removed so if a
1920 problem arises please report it and optionally revert to the old USB
1921 stack. If you are loading USB kernel modules or have a custom kernel
1922 that includes GENERIC then ensure that usb names are also changed over,
1923 eg uftdi -> usb2_serial_ftdi.
1925 Older programs linked against the ports libusb 0.1 need to be
1926 redirected to the new stack's libusb20. /etc/libmap.conf can
1928 # Map old usb library to new one for usb2 stack
1929 libusb-0.1.so.8 libusb20.so.1
1932 All USB ethernet devices now attach as interfaces under the name ueN
1933 (eg. ue0). This is to provide a predictable name as vendors often
1934 change usb chipsets in a product without notice.
1937 The ichsmb(4) driver has been changed to require SMBus slave
1938 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1939 All of the other SMBus controller drivers require left-justified
1940 slave addresses, so this change makes all the drivers provide the
1944 INET6 statistics (struct ip6stat) was updated.
1945 netstat(1) needs to be recompiled.
1948 NTFS has been removed from GENERIC kernel on amd64 to match
1949 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1950 will load ntfs.ko module automatically when NTFS support is
1951 actually needed, unless ntfs.ko is not installed or security
1952 level prohibits loading kernel modules. If either is the case,
1953 "options NTFS" has to be added into kernel config.
1956 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1957 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1958 800061. User space tools that rely on the size of struct tcpcb in
1959 tcp_var.h (e.g. sockstat) need to be recompiled.
1962 ng_tty(4) module updated to match the new TTY subsystem.
1963 Due to API change, user-level applications must be updated.
1964 New API support added to mpd5 CVS and expected to be present
1965 in next mpd5.3 release.
1968 With __FreeBSD_version 800060 the makefs tool is part of
1969 the base system (it was a port).
1972 The afdata and ifnet locks have been changed from mutexes to
1973 rwlocks, network modules will need to be re-compiled.
1976 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1977 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1978 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1979 architecture and 40 bytes on 64-bit architecture. The userland
1980 applications "arp" and "ndp" have been updated accordingly.
1981 The output from "netstat -r" shows only routing entries and
1982 none of the L2 information.
1985 __FreeBSD_version 800057 marks the switchover from the
1986 binary ath hal to source code. Users must add the line:
1988 options AH_SUPPORT_AR5416
1990 to their kernel config files when specifying:
1994 The ath_hal module no longer exists; the code is now compiled
1995 together with the driver in the ath module. It is now
1996 possible to tailor chip support (i.e. reduce the set of chips
1997 and thereby the code size); consult ath_hal(4) for details.
2000 __FreeBSD_version 800054 adds memory barriers to
2001 <machine/atomic.h>, new interfaces to ifnet to facilitate
2002 multiple hardware transmit queues for cards that support
2003 them, and a lock-less ring-buffer implementation to
2004 enable drivers to more efficiently manage queueing of
2008 A new version of ZFS (version 13) has been merged to -HEAD.
2009 This version has zpool attribute "listsnapshots" off by
2010 default, which means "zfs list" does not show snapshots,
2011 and is the same as Solaris behavior.
2014 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
2017 The uhci, ohci, ehci and slhci USB Host controller drivers have
2018 been put into separate modules. If you load the usb module
2019 separately through loader.conf you will need to load the
2020 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
2021 controller add the following to loader.conf:
2027 The ABI used by the PMC toolset has changed. Please keep
2028 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
2032 atapci kernel module now includes only generic PCI ATA
2033 driver. AHCI driver moved to ataahci kernel module.
2034 All vendor-specific code moved into separate kernel modules:
2035 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
2036 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
2037 atamarvell, atamicron, atanational, atanetcell, atanvidia,
2038 atapromise, ataserverworks, atasiliconimage, atasis, atavia
2041 The TTY subsystem of the kernel has been replaced by a new
2042 implementation, which provides better scalability and an
2043 improved driver model. Most common drivers have been migrated to
2044 the new TTY subsystem, while others have not. The following
2045 drivers have not yet been ported to the new TTY layer:
2048 cy, digi, rc, rp, sio
2054 ng_h4, ng_tty, ppp, sl, snp
2056 Adding these drivers to your kernel configuration file shall
2057 cause compilation to fail.
2060 ntpd has been upgraded to 4.2.4p5.
2063 OpenSSH has been upgraded to 5.1p1.
2065 For many years, FreeBSD's version of OpenSSH preferred DSA
2066 over RSA for host and user authentication keys. With this
2067 upgrade, we've switched to the vendor's default of RSA over
2068 DSA. This may cause upgraded clients to warn about unknown
2069 host keys even for previously known hosts. Users should
2070 follow the usual procedure for verifying host keys before
2071 accepting the RSA key.
2073 This can be circumvented by setting the "HostKeyAlgorithms"
2074 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
2077 Please note that the sequence of keys offered for
2078 authentication has been changed as well. You may want to
2079 specify IdentityFile in a different order to revert this
2083 The sio(4) driver has been removed from the i386 and amd64
2084 kernel configuration files. This means uart(4) is now the
2085 default serial port driver on those platforms as well.
2087 To prevent collisions with the sio(4) driver, the uart(4) driver
2088 uses different names for its device nodes. This means the
2089 onboard serial port will now most likely be called "ttyu0"
2090 instead of "ttyd0". You may need to reconfigure applications to
2091 use the new device names.
2093 When using the serial port as a boot console, be sure to update
2094 /boot/device.hints and /etc/ttys before booting the new kernel.
2095 If you forget to do so, you can still manually specify the hints
2096 at the loader prompt:
2098 set hint.uart.0.at="isa"
2099 set hint.uart.0.port="0x3F8"
2100 set hint.uart.0.flags="0x10"
2101 set hint.uart.0.irq="4"
2105 The gpt(8) utility has been removed. Use gpart(8) to partition
2109 The version that Linuxulator emulates was changed from 2.4.2
2110 to 2.6.16. If you experience any problems with Linux binaries
2111 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2112 if it fixes the problem contact emulation mailing list.
2115 ISDN4BSD (I4B) was removed from the src tree. You may need to
2116 update a your kernel configuration and remove relevant entries.
2119 I have checked in code to support multiple routing tables.
2120 See the man pages setfib(1) and setfib(2).
2121 This is a hopefully backwards compatible version,
2122 but to make use of it you need to compile your kernel
2123 with options ROUTETABLES=2 (or more up to 16).
2126 The 802.11 wireless support was redone to enable multi-bss
2127 operation on devices that are capable. The underlying device
2128 is no longer used directly but instead wlanX devices are
2129 cloned with ifconfig. This requires changes to rc.conf files.
2130 For example, change:
2131 ifconfig_ath0="WPA DHCP"
2134 ifconfig_wlan0="WPA DHCP"
2135 see rc.conf(5) for more details. In addition, mergemaster of
2136 /etc/rc.d is highly recommended. Simultaneous update of userland
2137 and kernel wouldn't hurt either.
2139 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2140 modules were merged into the base wlan module. All references
2141 to these modules (e.g. in kernel config files) must be removed.
2144 psm(4) has gained write(2) support in native operation level.
2145 Arbitrary commands can be written to /dev/psm%d and status can
2146 be read back from it. Therefore, an application is responsible
2147 for status validation and error recovery. It is a no-op in
2148 other operation levels.
2151 Support for KSE threading has been removed from the kernel. To
2152 run legacy applications linked against KSE libmap.conf may
2153 be used. The following libmap.conf may be used to ensure
2154 compatibility with any prior release:
2156 libpthread.so.1 libthr.so.1
2157 libpthread.so.2 libthr.so.2
2158 libkse.so.3 libthr.so.3
2161 The layout of struct vmspace has changed. This affects libkvm
2162 and any executables that link against libkvm and use the
2163 kvm_getprocs() function. In particular, but not exclusively,
2164 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2165 The effects are minimal, but it's advisable to upgrade world
2169 The latest em driver no longer has support in it for the
2170 82575 adapter, this is now moved to the igb driver. The
2171 split was done to make new features that are incompatible
2172 with older hardware easier to do.
2175 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2176 likewise the kernel option is now GEOM_LINUX_LVM.
2179 The default NFS mount mode has changed from UDP to TCP for
2180 increased reliability. If you rely on (insecurely) NFS
2181 mounting across a firewall you may need to update your
2185 Belatedly note the addition of m_collapse for compacting
2189 The fts(3) structures have been changed to use adequate
2190 integer types for their members and so to be able to cope
2191 with huge file trees. The old fts(3) ABI is preserved
2192 through symbol versioning in libc, so third-party binaries
2193 using fts(3) should still work, although they will not take
2194 advantage of the extended types. At the same time, some
2195 third-party software might fail to build after this change
2196 due to unportable assumptions made in its source code about
2197 fts(3) structure members. Such software should be fixed
2198 by its vendor or, in the worst case, in the ports tree.
2199 FreeBSD_version 800015 marks this change for the unlikely
2200 case that a portable fix is impossible.
2203 To upgrade to -current after this date, you must be running
2204 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2205 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2208 The ADAPTIVE_GIANT kernel option has been retired because its
2209 functionality is the default now.
2212 The AT keyboard emulation of sunkbd(4) has been turned on
2213 by default. In order to make the special symbols of the Sun
2214 keyboards driven by sunkbd(4) work under X these now have
2215 to be configured the same way as Sun USB keyboards driven
2216 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2218 Option "XkbLayout" "us"
2219 Option "XkbRules" "xorg"
2220 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2223 It has been decided that it is desirable to provide ABI
2224 backwards compatibility to the FreeBSD 4/5/6 versions of the
2225 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2226 broken with the introduction of PCI domain support (see the
2227 20070930 entry). Unfortunately, this required the ABI of
2228 PCIOCGETCONF to be broken again in order to be able to
2229 provide backwards compatibility to the old version of that
2230 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2231 again. As for prominent ports this affects neither pciutils
2232 nor xorg-server this time, the hal port needs to be rebuilt
2236 The misnamed kthread_create() and friends have been renamed
2237 to kproc_create() etc. Many of the callers already
2238 used kproc_start()..
2239 I will return kthread_create() and friends in a while
2240 with implementations that actually create threads, not procs.
2241 Renaming corresponds with version 800002.
2250 Avoid using make -j when upgrading. While generally safe, there are
2251 sometimes problems using -j to upgrade. If your upgrade fails with
2252 -j, please try again without -j. From time to time in the past there
2253 have been problems using -j with buildworld and/or installworld. This
2254 is especially true when upgrading between "distant" versions (eg one
2255 that cross a major release boundary or several minor releases, or when
2256 several months have passed on the -current branch).
2258 Sometimes, obscure build problems are the result of environment
2259 poisoning. This can happen because the make utility reads its
2260 environment when searching for values for global variables. To run
2261 your build attempts in an "environmental clean room", prefix all make
2262 commands with 'env -i '. See the env(1) manual page for more details.
2264 When upgrading from one major version to another it is generally best
2265 to upgrade to the latest code in the currently installed branch first,
2266 then do an upgrade to the new branch. This is the best-tested upgrade
2267 path, and has the highest probability of being successful. Please try
2268 this approach before reporting problems with a major version upgrade.
2270 When upgrading a live system, having a root shell around before
2271 installing anything can help undo problems. Not having a root shell
2272 around can lead to problems if pam has changed too much from your
2273 starting point to allow continued authentication after the upgrade.
2277 When upgrading the boot ZFS pool to a new version, always follow
2280 1.) recompile and reinstall the ZFS boot loader and boot block
2281 (this is part of "make buildworld" and "make installworld")
2283 2.) update the ZFS boot block on your boot drive
2285 The following example updates the ZFS boot block on the first
2286 partition (freebsd-boot) of a GPT partitioned drive ad0:
2287 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2289 Non-boot pools do not need these updates.
2293 If you are updating from a prior version of FreeBSD (even one just
2294 a few days old), you should follow this procedure. It is the most
2295 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2297 make kernel-toolchain
2298 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2299 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2301 To test a kernel once
2302 ---------------------
2303 If you just want to boot a kernel once (because you are not sure
2304 if it works, or if you want to boot a known bad kernel to provide
2305 debugging information) run
2306 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2307 nextboot -k testkernel
2309 To just build a kernel when you know that it won't mess you up
2310 --------------------------------------------------------------
2311 This assumes you are already running a CURRENT system. Replace
2312 ${arch} with the architecture of your machine (e.g. "i386",
2313 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2315 cd src/sys/${arch}/conf
2316 config KERNEL_NAME_HERE
2317 cd ../compile/KERNEL_NAME_HERE
2322 If this fails, go to the "To build a kernel" section.
2324 To rebuild everything and install it on the current system.
2325 -----------------------------------------------------------
2326 # Note: sometimes if you are running current you gotta do more than
2327 # is listed here if you are upgrading from a really old current.
2329 <make sure you have good level 0 dumps>
2331 make kernel KERNCONF=YOUR_KERNEL_HERE
2333 <reboot in single user> [3]
2340 To cross-install current onto a separate partition
2341 --------------------------------------------------
2342 # In this approach we use a separate partition to hold
2343 # current's root, 'usr', and 'var' directories. A partition
2344 # holding "/", "/usr" and "/var" should be about 2GB in
2347 <make sure you have good level 0 dumps>
2350 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2351 <maybe newfs current's root partition>
2352 <mount current's root partition on directory ${CURRENT_ROOT}>
2353 make installworld DESTDIR=${CURRENT_ROOT}
2354 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2355 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2356 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2357 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2358 <reboot into current>
2359 <do a "native" rebuild/install as described in the previous section>
2360 <maybe install compatibility libraries from ports/misc/compat*>
2364 To upgrade in-place from stable to current
2365 ----------------------------------------------
2366 <make sure you have good level 0 dumps>
2368 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2370 <reboot in single user> [3]
2377 Make sure that you've read the UPDATING file to understand the
2378 tweaks to various things you need. At this point in the life
2379 cycle of current, things change often and you are on your own
2380 to cope. The defaults can also change, so please read ALL of
2381 the UPDATING entries.
2383 Also, if you are tracking -current, you must be subscribed to
2384 freebsd-current@freebsd.org. Make sure that before you update
2385 your sources that you have read and understood all the recent
2386 messages there. If in doubt, please track -stable which has
2387 much fewer pitfalls.
2389 [1] If you have third party modules, such as vmware, you
2390 should disable them at this point so they don't crash your
2393 [3] From the bootblocks, boot -s, and then do
2398 adjkerntz -i # if CMOS is wall time
2399 Also, when doing a major release upgrade, it is required that
2400 you boot into single user mode to do the installworld.
2402 [4] Note: This step is non-optional. Failure to do this step
2403 can result in a significant reduction in the functionality of the
2404 system. Attempting to do it by hand is not recommended and those
2405 that pursue this avenue should read this file carefully, as well
2406 as the archives of freebsd-current and freebsd-hackers mailing lists
2407 for potential gotchas. The -U option is also useful to consider.
2408 See mergemaster(8) for more information.
2410 [5] Usually this step is a noop. However, from time to time
2411 you may need to do this if you get unknown user in the following
2412 step. It never hurts to do it all the time. You may need to
2413 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2414 install) after the buildworld before this step if you last updated
2415 from current before 20130425 or from -stable before 20130430.
2417 [6] This only deletes old files and directories. Old libraries
2418 can be deleted by "make delete-old-libs", but you have to make
2419 sure that no program is using those libraries anymore.
2421 [8] In order to have a kernel that can run the 4.x binaries needed to
2422 do an installworld, you must include the COMPAT_FREEBSD4 option in
2423 your kernel. Failure to do so may leave you with a system that is
2424 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2425 required to run the 5.x binaries on more recent kernels. And so on
2426 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2428 Make sure that you merge any new devices from GENERIC since the
2429 last time you updated your kernel config file.
2431 [9] When checking out sources, you must include the -P flag to have
2432 cvs prune empty directories.
2434 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2435 "?=" instead of the "=" assignment operator, so that buildworld can
2436 override the CPUTYPE if it needs to.
2438 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2439 not on the command line, or in /etc/make.conf. buildworld will
2440 warn if it is improperly defined.
2443 This file contains a list, in reverse chronological order, of major
2444 breakages in tracking -current. It is not guaranteed to be a complete
2445 list of such breakages, and only contains entries since October 10, 2007.
2446 If you need to see UPDATING entries from before that date, you will need
2447 to fetch an UPDATING file from an older FreeBSD release.
2449 Copyright information:
2451 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2453 Redistribution, publication, translation and use, with or without
2454 modification, in full or in part, in any form or format of this
2455 document are permitted without further permission from the author.
2457 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2458 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2459 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2460 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2461 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2462 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2463 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2464 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2465 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2466 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2467 POSSIBILITY OF SUCH DAMAGE.
2469 Contact Warner Losh if you have any questions about your use of