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 20171209 p26 FreeBSD-SA-17:12.openssl
21 Fix OpenSSL error state vulnerability.
23 20171129 p25 FreeBSD-SA-17:11.openssl
25 Fix OpenSSL out-of-bounds read vulnerability.
27 20171115 p24 FreeBSD-SA-17:08.ptrace
29 FreeBSD-SA-17:10.kldstat
31 Fix ptrace(2) vulnerability. [SA-17:08.ptrace]
33 Fix POSIX shm namespace vulnerability. [SA-17:09.shm]
35 Fix kldstat(2) vulnerability. [SA-17:10.kldstat]
37 20171102 p23 FreeBSD-EN-17:09.tzdata
39 Update timezone database information. [EN-17:09]
41 20171017 p22 FreeBSD-SA-17:07.wpa
43 Fix WPA2 protocol vulnerability. [SA-17:07]
45 20170810 p21 FreeBSD-SA-17:06.openssh
47 Fix OpenSSH Denial of Service vulnerability. [SA-17:06]
49 20170712 p20 FreeBSD-SA-17:05.heimdal
50 FreeBSD-EN-17:06.hyperv
52 Fix heimdal KDC-REP service name validation vulnerability [SA-17:05]
54 Boot compatibility improvements with Azure VMs. [EN-17:06]
56 20170427 p19 FreeBSD-SA-17:04.ipfilter
58 Fix ipfilter(4) fragment handling panic. [SA-17:04]
60 20170412 p18 FreeBSD-SA-17:03.ntp
63 Fix multiple vulnerabilities of ntp. [SA-17:03]
65 Xen migration enhancements. [EN-17:05]
67 20170223 p17 FreeBSD-SA-17:02.openssl
69 Fix OpenSSL RC4_MD5 cipher vulnerability.
71 20170111 p16 FreeBSD-SA-17:01.openssh
73 Fix multiple vulnerabilities of OpenSSH.
75 20161222 p15 FreeBSD-SA-16:39.ntp
77 Fix multiple vulnerabilities of ntp.
79 20161208 p14 FreeBSD-SA-16:37.libc [revised]
81 Fix regressions introduced by SA-16:37.libc.
83 20161206 p13 FreeBSD-SA-16:36.telnetd
85 FreeBSD-SA-16:38.bhyve
86 FreeBSD-EN-16:19.tzcode
87 FreeBSD-EN-16:20.tzdata
89 Fix possible login(1) argument injection in telnetd(8). [SA-16:36]
90 Fix link_ntoa(3) buffer overflow in libc. [SA-16:37]
91 Fix possible escape from bhyve(8) virtual machine. [SA-16:38]
92 Fix warnings about valid time zone abbreviations. [EN-16:19]
93 Update timezone database information. [EN-16:20]
95 20161102 p12 FreeBSD-SA-16:33.openssh
96 FreeBSD-SA-16:35.openssl
98 Fix OpenSSH remote Denial of Service vulnerability. [SA-16:33]
100 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
102 20161025 p11 FreeBSD-SA-16:15.sysarch [revised]
105 Fix incorrect argument validation in sysarch(2). [SA-16:15]
106 Fix virtual memory subsystem bugs. [EN-16:17]
108 20161010 p10 FreeBSD-SA-16:29.bspatch
109 FreeBSD-SA-16:30.portsnap
110 FreeBSD-SA-16:31.libarchive
112 Fix bspatch heap overflow vulnerability. [SA-16:29]
114 Fix multiple portsnap vulnerabilities. [SA-16:30]
116 Fix multiple libarchive vulnerabilities. [SA-16:31]
118 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
120 Fix OpenSSL regression introduced in SA-16:26.
122 20160923 p8 FreeBSD-SA-16:26.openssl
124 Fix multiple OpenSSL vulnerabilitites.
126 20160811 p7 FreeBSD-EN-16:10.dhclient
127 FreeBSD-EN-16:11.vmbus
128 FreeBSD-EN-16:12.hv_storvsc
129 FreeBSD-EN-16:13.vmbus
130 FreeBSD-EN-16:14.hv_storvsc
131 FreeBSD-EN-16:15.vmbus
132 FreeBSD-EN-16:16.hv_storvsc
134 Fix handling of unknown options from a DHCP server. [EN-16:10]
135 Fix a panic in hv_vmbus(4). [EN-16:11]
136 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
137 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
138 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
139 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
140 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
142 20160725 p6 FreeBSD-SA-16:25.bspatch
143 FreeBSD-EN-16:09.freebsd-update
145 Fix bspatch heap overflow vulnerability. [SA-16:25]
147 Fix freebsd-update(8) support of FreeBSD 11.0 release
148 distribution. [EN-16:09]
150 20160604 p5 FreeBSD-SA-16:24.ntp
152 Fix multiple vulnerabilities of ntp.
154 20160531 p4 FreeBSD-SA-16:20.linux
155 FreeBSD-SA-16:21.43bsd
156 FreeBSD-SA-16:22.libarchive
158 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
159 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
160 Fix directory traversal in cpio(1). [SA-16:22]
163 20160517 p3 FreeBSD-SA-16:18.atkbd
164 FreeBSD-SA-16:19.sendmsg
166 Fix buffer overflow in keyboard driver. [SA-16:18]
168 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
170 20160504 p2 FreeBSD-SA-16:17.openssl
171 FreeBSD-EN-16:06.libc
175 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
177 Fix performance regression in libc hash(3). [EN-16:06]
179 Fix excessive latency in x86 IPI delivery. [EN-16:07]
181 Fix memory leak in ZFS. [EN-16:08]
183 20160429 p1 FreeBSD-SA-16:16.ntp
185 Fix multiple vulnerabilities of ntp.
191 The NONE and HPN patches has been removed from OpenSSH. They are
192 still available in the security/openssh-portable port.
195 r292223 changed the internal interface between the nfsd.ko and
196 nfscommon.ko modules. As such, they must both be upgraded to-gether.
197 __FreeBSD_version has been bumped because of this.
200 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
201 Kernel modules isp_2400_multi and isp_2500_multi were removed and
202 should be replaced with isp_2400 and isp_2500 modules respectively.
205 The menu.rc and loader.rc files will now be replaced during
206 upgrades. Please migrate local changes to menu.rc.local and
207 loader.rc.local instead.
210 NTP has been upgraded to 4.2.8p4.
213 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
214 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
215 and devel/kyua to version 0.20+ and adjust any calling code to work
216 with Kyuafile and kyua.
219 The polarity of Pulse Per Second (PPS) capture events with the
220 uart(4) driver has been corrected. Prior to this change the PPS
221 "assert" event corresponded to the trailing edge of a positive PPS
222 pulse and the "clear" event was the leading edge of the next pulse.
224 As the width of a PPS pulse in a typical GPS receiver is on the
225 order of 1 millisecond, most users will not notice any significant
226 difference with this change.
228 Anyone who has compensated for the historical polarity reversal by
229 configuring a negative offset equal to the pulse width will need to
230 remove that workaround.
233 From legacy ata(4) driver was removed support for SATA controllers
234 supported by more functional drivers ahci(4), siis(4) and mvs(4).
235 Kernel modules ataahci and ataadaptec were removed completely,
236 replaced by ahci and mvs modules respectively.
242 As ZFS requires more kernel stack pages than is the default on some
243 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
244 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
246 Please consider using 'options KSTACK_PAGES=X' where X is greater
247 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
250 The default Unbound configuration now enables remote control
251 using a local socket. Users who have already enabled the
252 local_unbound service should regenerate their configuration
253 by running "service local_unbound setup" as root.
256 An additional fix for the issue described in the 20150614 sendmail
257 entry below has been been committed in revision 284786.
260 The fix for the issue described in the 20150614 sendmail entry
261 below has been been committed in revision 284485. The work
262 around described in that entry is no longer needed unless the
263 default setting is overridden by a confDH_PARAMETERS configuration
264 setting of '5' or pointing to a 512 bit DH parameter file.
267 The import of openssl to address the FreeBSD-SA-15:10.openssl
268 security advisory includes a change which rejects handshakes
269 with DH parameters below 768 bits. sendmail releases prior
270 to 8.15.2 (not yet released), defaulted to a 512 bit
271 DH parameter setting for client connections. To work around
272 this interoperability, sendmail can be configured to use a
273 2048 bit DH parameter by:
275 1. Edit /etc/mail/`hostname`.mc
276 2. If a setting for confDH_PARAMETERS does not exist or
277 exists and is set to a string beginning with '5',
279 3. If a setting for confDH_PARAMETERS exists and is set to
280 a file path, create a new file with:
281 openssl dhparam -out /path/to/file 2048
282 4. Rebuild the .cf file:
283 cd /etc/mail/; make; make install
285 cd /etc/mail/; make restart
287 A sendmail patch is coming, at which time this file will be
291 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
292 defined in symlink(7); previously symlinks were silently ignored.
295 The const qualifier has been removed from iconv(3) to comply with
296 POSIX. The ports tree is aware of this from r384038 onwards.
299 At svn r275807, The default linux compat kernel ABI has been adjusted
300 to 2.6.18 in support of the linux-c6 compat ports infrastructure
301 update. If you wish to continue using the linux-f10 compat ports,
302 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
303 encouraged to update their linux-compat packages to linux-c6 during
304 their next update cycle.
306 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
309 pjdfstest has been integrated into kyua as an opt-in test suite.
310 Please see share/doc/pjdfstest/README for a more details on how to
317 The ofwfb driver, used to provide a graphics console on PowerPC when
318 using vt(4), no longer allows mmap() of all of physical memory. This
319 will prevent Xorg on PowerPC with some ATI graphics cards from
320 initializing properly unless x11-servers/xorg-server is updated to
324 The libatf-c and libatf-c++ major versions were downgraded to 0 and
325 1 respectively to match the upstream numbers. They were out of
326 sync because, when they were originally added to FreeBSD, the
327 upstream versions were not respected. These libraries are private
328 and not yet built by default, so renumbering them should be a
329 non-issue. However, unclean source trees will yield broken test
330 programs once the operator executes "make delete-old-libs" after a
333 Additionally, the atf-sh binary was made private by moving it into
334 /usr/libexec/. Already-built shell test programs will keep the
335 path to the old binary so they will break after "make delete-old"
338 If you are using WITH_TESTS=yes (not the default), wipe the object
339 tree and rebuild from scratch to prevent spurious test failures.
340 This is only needed once: the misnumbered libraries and misplaced
341 binaries have been added to OptionalObsoleteFiles.inc so they will
342 be removed during a clean upgrade.
345 The ixgbe tunables now match their sysctl counterparts, for example:
346 hw.ixgbe.enable_aim => hw.ix.enable_aim
347 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
350 The NFSv4.1 server committed by r269398 changes the internal
351 function call interfaces used between the NFS and krpc modules.
352 As such, __FreeBSD_version was bumped.
355 The default unbound configuration has been modified to address
356 issues with reverse lookups on networks that use private
357 address ranges. If you use the local_unbound service, run
358 "service local_unbound setup" as root to regenerate your
359 configuration, then "service local_unbound reload" to load the
363 It is no longer necessary to include the dwarf version in your DEBUG
364 options in your kernel config file. The bug that required it to be
365 placed in the config file has bene fixed. DEBUG should now just
366 contain -g. The build system will automatically update things
367 to do the right thing.
370 Several ABI breaking changes were merged to CTL and new iSCSI code.
371 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
372 iscsictl need to be rebuilt to work with a new kernel.
375 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
376 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
377 which differs from the behaviour controlled by this knob.)
380 On i386 and amd64 systems, the onifconsole flag is now set by default
381 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
382 as a login TTY if it is set in the bootloader as an active kernel
383 console. No changes in behavior should result otherwise. To revert to
384 the previous behavior, set ttyu0 to "off" in /etc/ttys.
387 Clang and llvm have been upgraded to 3.4.1 release.
390 Clang and llvm have been upgraded to 3.4 release.
393 If a Makefile in a tests/ directory was auto-generating a Kyuafile
394 instead of providing an explicit one, this would prevent such
395 Makefile from providing its own Kyuafile in the future during
396 NO_CLEAN builds. This has been fixed in the Makefiles but manual
397 intervention is needed to clean an objdir if you use NO_CLEAN:
398 # find /usr/obj -name Kyuafile | xargs rm -f
401 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
402 capability mode support. Please note that enabling the feature in
403 kernel is still highly recommended.
406 OpenSSH is now built with sandbox support, and will use sandbox as
407 the default privilege separation method. This requires Capsicum
408 capability mode support in kernel.
411 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
412 been deprecated and will not be part of FreeBSD 11.0 and later
413 releases. If you use this driver, please consider switching to
414 the nfe(4) driver instead.
420 The behavior of gss_pseudo_random() for the krb5 mechanism
421 has changed, for applications requesting a longer random string
422 than produced by the underlying enctype's pseudo-random() function.
423 In particular, the random string produced from a session key of
424 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
425 be different at the 17th octet and later, after this change.
426 The counter used in the PRF+ construction is now encoded as a
427 big-endian integer in accordance with RFC 4402.
428 __FreeBSD_version is bumped to 1000701.
431 The WITHOUT_ATF build knob has been removed and its functionality
432 has been subsumed into the more generic WITHOUT_TESTS. If you were
433 using the former to disable the build of the ATF libraries, you
434 should change your settings to use the latter.
437 The default version of mtree is nmtree which is obtained from
438 NetBSD. The output is generally the same, but may vary
439 slightly. If you found you need identical output adding
440 "-F freebsd9" to the command line should do the trick. For the
441 time being, the old mtree is available as fmtree.
444 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
445 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
446 1.1.4_8 and verify bsdyml not linked in, before running "make
448 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
450 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
453 The rc.d/jail script has been updated to support jail(8)
454 configuration file. The "jail_<jname>_*" rc.conf(5) variables
455 for per-jail configuration are automatically converted to
456 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
457 This is transparently backward compatible. See below about some
458 incompatibilities and rc.conf(5) manual page for more details.
460 These variables are now deprecated in favor of jail(8) configuration
461 file. One can use "rc.d/jail config <jname>" command to generate
462 a jail(8) configuration file in /var/run/jail.<jname>.conf without
463 running the jail(8) utility. The default pathname of the
464 configuration file is /etc/jail.conf and can be specified by
465 using $jail_conf or $jail_<jname>_conf variables.
467 Please note that jail_devfs_ruleset accepts an integer at
468 this moment. Please consider to rewrite the ruleset name
472 BIND has been removed from the base system. If all you need
473 is a local resolver, simply enable and start the local_unbound
474 service instead. Otherwise, several versions of BIND are
475 available in the ports tree. The dns/bind99 port is one example.
477 With this change, nslookup(1) and dig(1) are no longer in the base
478 system. Users should instead use host(1) and drill(1) which are
479 in the base system. Alternatively, nslookup and dig can
480 be obtained by installing the dns/bind-tools port.
483 With the addition of unbound(8), a new unbound user is now
484 required during installworld. "mergemaster -p" can be used to
485 add the user prior to installworld, as documented in the handbook.
488 OpenSSH is now built with DNSSEC support, and will by default
489 silently trust signed SSHFP records. This can be controlled with
490 the VerifyHostKeyDNS client configuration setting. DNSSEC support
491 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
494 The GNU Compiler Collection and C++ standard library (libstdc++)
495 are no longer built by default on platforms where clang is the system
496 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
500 The PROCDESC kernel option is now part of the GENERIC kernel
501 configuration and is required for the rwhod(8) to work.
502 If you are using custom kernel configuration, you should include
506 The API and ABI related to the Capsicum framework was modified
507 in backward incompatible way. The userland libraries and programs
508 have to be recompiled to work with the new kernel. This includes the
509 following libraries and programs, but the whole buildworld is
510 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
511 kdump, procstat, rwho, rwhod, uniq.
514 AES-NI intrinsic support has been added to gcc. The AES-NI module
515 has been updated to use this support. A new gcc is required to build
516 the aesni module on both i386 and amd64.
519 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
520 Thus "device padlock_rng" and "device rdrand_rng" should be
521 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
524 WITH_ICONV has been split into two feature sets. WITH_ICONV now
525 enables just the iconv* functionality and is now on by default.
526 WITH_LIBICONV_COMPAT enables the libiconv api and link time
527 compatability. Set WITHOUT_ICONV to build the old way.
528 If you have been using WITH_ICONV before, you will very likely
529 need to turn on WITH_LIBICONV_COMPAT.
532 INVARIANTS option now enables DEBUG for code with OpenSolaris and
533 Illumos origin, including ZFS. If you have INVARIANTS in your
534 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
536 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
537 locks if WITNESS option was set. Because that generated a lot of
538 witness(9) reports and all of them were believed to be false
539 positives, this is no longer done. New option OPENSOLARIS_WITNESS
540 can be used to achieve the previous behavior.
543 Timer values in IPv6 data structures now use time_uptime instead
544 of time_second. Although this is not a user-visible functional
545 change, userland utilities which directly use them---ndp(8),
546 rtadvd(8), and rtsold(8) in the base system---need to be updated
550 find -delete can now delete the pathnames given as arguments,
551 instead of only files found below them or if the pathname did
552 not contain any slashes. Formerly, the following error message
555 find: -delete: <path>: relative path potentially not safe
557 Deleting the pathnames given as arguments can be prevented
558 without error messages using -mindepth 1 or by changing
559 directory and passing "." as argument to find. This works in the
560 old as well as the new version of find.
563 Behavior of devfs rules path matching has been changed.
564 Pattern is now always matched against fully qualified devfs
565 path and slash characters must be explicitly matched by
566 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
567 subdirectories must be reviewed.
570 The default ARM ABI has changed to the ARM EABI. The old ABI is
571 incompatible with the ARM EABI and all programs and modules will
572 need to be rebuilt to work with a new kernel.
574 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
576 NOTE: Support for the old ABI will be removed in the future and
577 users are advised to upgrade.
580 pkg_install has been disconnected from the build if you really need it
581 you should add WITH_PKGTOOLS in your src.conf(5).
584 Most of network statistics structures were changed to be able
585 keep 64-bits counters. Thus all tools, that work with networking
586 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
589 Fix a bug that allowed a tracing process (e.g. gdb) to write
590 to a memory-mapped file in the traced process's address space
591 even if neither the traced process nor the tracing process had
592 write access to that file.
595 CVS has been removed from the base system. An exact copy
596 of the code is available from the devel/cvs port.
599 Some people report the following error after the switch to bmake:
601 make: illegal option -- J
602 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
604 *** [buildworld] Error code 2
606 this likely due to an old instance of make in
607 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
608 which src/Makefile will use that blindly, if it exists, so if
609 you see the above error:
611 rm -rf `make -V MAKEPATH`
616 Use bmake by default.
617 Whereas before one could choose to build with bmake via
618 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
619 make. The goal is to remove these knobs for 10-RELEASE.
621 It is worth noting that bmake (like gmake) treats the command
622 line as the unit of failure, rather than statements within the
623 command line. Thus '(cd some/where && dosomething)' is safer
624 than 'cd some/where; dosomething'. The '()' allows consistent
625 behavior in parallel build.
628 Fix a bug that allows NFS clients to issue READDIR on files.
631 The WITHOUT_IDEA option has been removed because
632 the IDEA patent expired.
635 The sysctl which controls TRIM support under ZFS has been renamed
636 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
640 The mergemaster command now uses the default MAKEOBJDIRPREFIX
641 rather than creating it's own in the temporary directory in
642 order allow access to bootstrapped versions of tools such as
643 install and mtree. When upgrading from version of FreeBSD where
644 the install command does not support -l, you will need to
645 install a new mergemaster command if mergemaster -p is required.
646 This can be accomplished with the command (cd src/usr.sbin/mergemaster
650 Legacy ATA stack, disabled and replaced by new CAM-based one since
651 FreeBSD 9.0, completely removed from the sources. Kernel modules
652 atadisk and atapi*, user-level tools atacontrol and burncd are
653 removed. Kernel option `options ATA_CAM` is now permanently enabled
657 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
658 and socketpair(2). Software, in particular Kerberos, may
659 automatically detect and use these during building. The resulting
660 binaries will not work on older kernels.
663 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
664 information, see the respective 20130304 entry).
667 Recent commits to callout(9) changed the size of struct callout,
668 so the KBI is probably heavily disturbed. Also, some functions
669 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
670 by macros. Every kernel module using it won't load, so rebuild
673 The ctl device has been re-enabled in GENERIC for i386 and amd64,
674 but does not initialize by default (because of the new CTL_DISABLE
675 option) to save memory. To re-enable it, remove the CTL_DISABLE
676 option from the kernel config file or set kern.cam.ctl.disable=0
677 in /boot/loader.conf.
680 The ctl device has been disabled in GENERIC for i386 and amd64.
681 This was done due to the extra memory being allocated at system
682 initialisation time by the ctl driver which was only used if
683 a CAM target device was created. This makes a FreeBSD system
684 unusable on 128MB or less of RAM.
687 A new compression method (lz4) has been merged to -HEAD. Please
688 refer to zpool-features(7) for more information.
690 Please refer to the "ZFS notes" section of this file for information
691 on upgrading boot ZFS pools.
694 A BSD-licensed patch(1) variant has been added and is installed
695 as bsdpatch, being the GNU version the default patch.
696 To inverse the logic and use the BSD-licensed one as default,
697 while having the GNU version installed as gnupatch, rebuild
698 and install world with the WITH_BSD_PATCH knob set.
701 Due to the use of the new -l option to install(1) during build
702 and install, you must take care not to directly set the INSTALL
703 make variable in your /etc/make.conf, /etc/src.conf, or on the
704 command line. If you wish to use the -C flag for all installs
705 you may be able to add INSTALL+=-C to /etc/make.conf or
709 The install(1) option -M has changed meaning and now takes an
710 argument that is a file or path to append logs to. In the
711 unlikely event that -M was the last option on the command line
712 and the command line contained at least two files and a target
713 directory the first file will have logs appended to it. The -M
714 option served little practical purpose in the last decade so its
715 use is expected to be extremely rare.
718 After switching to Clang as the default compiler some users of ZFS
719 on i386 systems started to experience stack overflow kernel panics.
720 Please consider using 'options KSTACK_PAGES=4' in such configurations.
723 GEOM_LABEL now mangles label names read from file system metadata.
724 Mangling affect labels containing spaces, non-printable characters,
725 '%' or '"'. Device names in /etc/fstab and other places may need to
729 By default, only the 10 most recent kernel dumps will be saved. To
730 restore the previous behaviour (no limit on the number of kernel dumps
731 stored in the dump directory) add the following line to /etc/rc.conf:
736 With the addition of auditdistd(8), a new auditdistd user is now
737 required during installworld. "mergemaster -p" can be used to
738 add the user prior to installworld, as documented in the handbook.
741 The sin6_scope_id member variable in struct sockaddr_in6 is now
742 filled by the kernel before passing the structure to the userland via
743 sysctl or routing socket. This means the KAME-specific embedded scope
744 id in sin6_addr.s6_addr[2] is always cleared in userland application.
745 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
746 __FreeBSD_version is bumped to 1000025.
749 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
750 This means that the world and kernel will be compiled with clang
751 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
752 and /usr/bin/cpp. To disable this behavior and revert to building
753 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
754 of current may need to bootstrap WITHOUT_CLANG first if the clang
755 build fails (its compatibility window doesn't extend to the 9 stable
759 The IPFIREWALL_FORWARD kernel option has been removed. Its
760 functionality now turned on by default.
763 The ZERO_COPY_SOCKET kernel option has been removed and
764 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
765 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
766 mechanism which is not safe and may result in kernel crashes.
767 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
768 driver supports disposeable external page sized mbuf storage.
769 Proper replacements for both zero-copy mechanisms are under
770 consideration and will eventually lead to complete removal
771 of the two kernel options.
774 The IPv4 network stack has been converted to network byte
775 order. The following modules need to be recompiled together
776 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
777 pf(4), ipfw(4), ng_ipfw(4), stf(4).
780 Support for non-MPSAFE filesystems was removed from VFS. The
781 VFS_VERSION was bumped, all filesystem modules shall be
785 All the non-MPSAFE filesystems have been disconnected from
786 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
787 portalfs, smbfs, xfs.
790 The interface cloning API and ABI has changed. The following
791 modules need to be recompiled together with kernel:
792 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
793 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
794 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
797 The sdhci driver was split in two parts: sdhci (generic SD Host
798 Controller logic) and sdhci_pci (actual hardware driver).
799 No kernel config modifications are required, but if you
800 load sdhc as a module you must switch to sdhci_pci instead.
803 Import the FUSE kernel and userland support into base system.
806 The GNU sort(1) program has been removed since the BSD-licensed
807 sort(1) has been the default for quite some time and no serious
808 problems have been reported. The corresponding WITH_GNU_SORT
812 The pfil(9) API/ABI for AF_INET family has been changed. Packet
813 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
817 The net80211(4) ABI has been changed to allow for improved driver
818 PS-POLL and power-save support. All wireless drivers need to be
819 recompiled to work with the new kernel.
822 The random(4) support for the VIA hardware random number
823 generator (`PADLOCK') is no longer enabled unconditionally.
824 Add the padlock_rng device in the custom kernel config if
825 needed. The GENERIC kernels on i386 and amd64 do include the
826 device, so the change only affects the custom kernel
830 The pf(4) packet filter ABI has been changed. pfctl(8) and
831 snmp_pf module need to be recompiled to work with new kernel.
834 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
835 to -HEAD. Pools that have empty_bpobj in active state can not be
836 imported read-write with ZFS implementations that do not support
837 this feature. For more information read the zpool-features(5)
841 The sparc64 ZFS loader has been changed to no longer try to auto-
842 detect ZFS providers based on diskN aliases but now requires these
843 to be explicitly listed in the OFW boot-device environment variable.
846 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
847 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
848 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
851 The following sysctls and tunables have been renamed for consistency
852 with other variables:
853 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
854 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
857 The sort utility has been replaced with BSD sort. For now, GNU sort
858 is also available as "gnusort" or the default can be set back to
859 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
860 installed as "bsdsort".
863 A new version of ZFS (pool version 5000) has been merged to -HEAD.
864 Starting with this version the old system of ZFS pool versioning
865 is superseded by "feature flags". This concept enables forward
866 compatibility against certain future changes in functionality of ZFS
867 pools. The first read-only compatible "feature flag" for ZFS pools
868 is named "com.delphix:async_destroy". For more information
869 read the new zpool-features(5) manual page.
870 Please refer to the "ZFS notes" section of this file for information
871 on upgrading boot ZFS pools.
874 The malloc(3) implementation embedded in libc now uses sources imported
875 as contrib/jemalloc. The most disruptive API change is to
876 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
877 delete it prior to installworld, and optionally re-create it using the
878 new format after rebooting. See malloc.conf(5) for details
879 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
883 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
884 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
885 now spelled mips. This is to aid compatibility with third-party
886 software that expects this naming scheme in uname(3). Little-endian
887 settings are unchanged. If you are updating a big-endian mips64 machine
888 from before this change, you may need to set MACHINE_ARCH=mips64 in
889 your environment before the new build system will recognize your machine.
892 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
896 Now unix domain sockets behave "as expected" on nullfs(5). Previously
897 nullfs(5) did not pass through all behaviours to the underlying layer,
898 as a result if we bound to a socket on the lower layer we could connect
899 only to the lower path; if we bound to the upper layer we could connect
900 only to the upper path. The new behavior is one can connect to both the
901 lower and the upper paths regardless what layer path one binds to.
904 The getifaddrs upgrade path broken with 20111215 has been restored.
905 If you have upgraded in between 20111215 and 20120209 you need to
906 recompile libc again with your kernel. You still need to recompile
907 world to be able to configure CARP but this restriction already
911 The set_rcvar() function has been removed from /etc/rc.subr. All
912 base and ports rc.d scripts have been updated, so if you have a
913 port installed with a script in /usr/local/etc/rc.d you can either
914 hand-edit the rcvar= line, or reinstall the port.
916 An easy way to handle the mass-update of /etc/rc.d:
917 rm /etc/rc.d/* && mergemaster -i
920 panic(9) now stops other CPUs in the SMP systems, disables interrupts
921 on the current CPU and prevents other threads from running.
922 This behavior can be reverted using the kern.stop_scheduler_on_panic
924 The new behavior can be incompatible with kern.sync_on_panic.
927 The carp(4) facility has been changed significantly. Configuration
928 of the CARP protocol via ifconfig(8) has changed, as well as format
929 of CARP events submitted to devd(8) has changed. See manual pages
930 for more information. The arpbalance feature of carp(4) is currently
931 not supported anymore.
933 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
934 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
935 need to be recompiled.
938 The acpi_wmi(4) status device /dev/wmistat has been renamed to
942 The option VFS_ALLOW_NONMPSAFE option has been added in order to
943 explicitely support non-MPSAFE filesystems.
944 It is on by default for all supported platform at this present
948 The broken amd(4) driver has been replaced with esp(4) in the amd64,
949 i386 and pc98 GENERIC kernel configuration files.
952 sysinstall has been removed
955 The stable/9 branch created in subversion. This corresponds to the
956 RELENG_9 branch in CVS.
959 This commit modifies vfs_register() so that it uses a hash
960 calculation to set vfc_typenum, which is enabled by default.
961 The first time a system is booted after this change, the
962 vfc_typenum values will change for all file systems. The
963 main effect of this is a change to the NFS server file handles
964 for file systems that use vfc_typenum in their fsid, such as ZFS.
965 It will, however, prevent vfc_typenum from changing when file
966 systems are loaded in a different order for subsequent reboots.
967 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
968 until you are ready to remount all NFS clients after a reboot.
971 Bump the shared library version numbers for libraries that
972 do not use symbol versioning, have changed the ABI compared
973 to stable/8 and which shared library version was not bumped.
974 Done as part of 9.0-RELEASE cycle.
977 During the merge of Capsicum features, the fget(9) KPI was modified.
978 This may require the rebuilding of out-of-tree device drivers --
979 issues have been reported specifically with the nVidia device driver.
980 __FreeBSD_version is bumped to 900041.
982 Also, there is a period between 20110811 and 20110814 where the
983 special devices /dev/{stdin,stdout,stderr} did not work correctly.
984 Building world from a kernel during that window may not work.
987 The packet filter (pf) code has been updated to OpenBSD 4.5.
988 You need to update userland tools to be in sync with kernel.
989 This update breaks backward compatibility with earlier pfsync(4)
990 versions. Care must be taken when updating redundant firewall setups.
993 The following sysctls and tunables are retired on x86 platforms:
995 machdep.hlt_logical_cpus
996 The following sysctl is retired:
997 machdep.hyperthreading_allowed
998 The sysctls were supposed to provide a way to dynamically offline and
999 online selected CPUs on x86 platforms, but the implementation has not
1000 been reliable especially with SCHED_ULE scheduler.
1001 machdep.hyperthreading_allowed tunable is still available to ignore
1002 hyperthreading CPUs at OS level.
1003 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
1004 where X is an APIC ID of a CPU. Be advised, though, that disabling
1005 CPUs in non-uniform fashion will result in non-uniform topology and
1006 may lead to sub-optimal system performance with SCHED_ULE, which is
1007 a default scheduler.
1010 cpumask_t type is retired and cpuset_t is used in order to describe
1014 Changes to ifconfig(8) for dynamic address family detection mandate
1015 that you are running a kernel of 20110525 or later. Make sure to
1016 follow the update procedure to boot a new kernel before installing
1020 Support for sun4v architecture is officially dropped
1023 Several KPI breaking changes have been committed to the mii(4) layer,
1024 the PHY drivers and consequently some Ethernet drivers using mii(4).
1025 This means that miibus.ko and the modules of the affected Ethernet
1026 drivers need to be recompiled.
1028 Note to kernel developers: Given that the OUI bit reversion problem
1029 was fixed as part of these changes all mii(4) commits related to OUIs,
1030 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
1031 handling, no longer can be merged verbatim to stable/8 and previous
1035 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
1036 into their kernel configurations along with 'device pci'.
1039 The default NFS client is now the new NFS client, so fstype "newnfs"
1040 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
1041 Although mounts via fstype "nfs" will usually work without userland
1042 changes, it is recommended that the mount(8) and mount_nfs(8)
1043 commands be rebuilt from sources and that a link to mount_nfs called
1044 mount_oldnfs be created. The new client is compiled into the
1045 kernel with "options NFSCL" and this is needed for diskless root
1046 file systems. The GENERIC kernel configs have been changed to use
1047 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
1048 To use the regular/old client, you can "mount -t oldnfs ...". For
1049 a diskless root file system, you must also include a line like:
1051 vfs.root.mountfrom="oldnfs:"
1053 in the boot/loader.conf on the root fs on the NFS server to make
1054 a diskless root fs use the old client.
1057 The GENERIC kernels for all architectures now default to the new
1058 CAM-based ATA stack. It means that all legacy ATA drivers were
1059 removed and replaced by respective CAM drivers. If you are using
1060 ATA device names in /etc/fstab or other places, make sure to update
1061 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
1062 where 'Y's are the sequential numbers starting from zero for each type
1063 in order of detection, unless configured otherwise with tunables,
1064 see cam(4)). There will be symbolic links created in /dev/ to map
1065 old adX devices to the respective adaY. They should provide basic
1066 compatibility for file systems mounting in most cases, but they do
1067 not support old user-level APIs and do not have respective providers
1068 in GEOM. Consider using updated management tools with new device names.
1070 It is possible to load devices ahci, ata, siis and mvs as modules,
1071 but option ATA_CAM should remain in kernel configuration to make ata
1072 module work as CAM driver supporting legacy ATA controllers. Device ata
1073 still can be used in modular fashion (atacore + ...). Modules atadisk
1074 and atapi* are not used and won't affect operation in ATA_CAM mode.
1075 Note that to use CAM-based ATA kernel should include CAM devices
1076 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1077 them are parts of the cam module.
1079 ataraid(4) functionality is now supported by the RAID GEOM class.
1080 To use it you can load geom_raid kernel module and use graid(8) tool
1081 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1083 No kernel config options or code have been removed, so if a problem
1084 arises, please report it and optionally revert to the old ATA stack.
1085 In order to do it you can remove from the kernel config:
1090 , and instead add back:
1091 device atadisk # ATA disk drives
1092 device ataraid # ATA RAID drives
1093 device atapicd # ATAPI CDROM drives
1094 device atapifd # ATAPI floppy drives
1095 device atapist # ATAPI tape drives
1098 The default NFS server has been changed to the new server, which
1099 was referred to as the experimental server. If you need to switch
1100 back to the old NFS server, you must now put the "-o" option on
1101 both the mountd and nfsd commands. This can be done using the
1102 mountd_flags and nfs_server_flags rc.conf variables until an
1103 update to the rc scripts is committed, which is coming soon.
1106 The GNU Objective-C runtime library (libobjc), and other Objective-C
1107 related components have been removed from the base system. If you
1108 require an Objective-C library, please use one of the available ports.
1111 ath(4) has been split into bus- and device- modules. if_ath contains
1112 the HAL, the TX rate control and the network device code. if_ath_pci
1113 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1114 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1115 in order to use ath on everything else.
1117 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1118 need to load if_ath and if_ath_pci for ath(4) operation.
1121 As part of the replacement of sysinstall, the process of building
1122 release media has changed significantly. For details, please re-read
1123 release(7), which has been updated to reflect the new build process.
1126 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1127 is the last available version under GPLv2. It brings a number of new
1128 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1129 4.1 and SSE 4.2), better support for powerpc64, a number of new
1130 directives, and lots of other small improvements. See the ChangeLog
1131 file in contrib/binutils for the full details.
1134 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1135 compliant, and will now use half of hash for authentication.
1136 This will break interoperability with all stacks (including all
1137 actual FreeBSD versions) who implement
1138 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1140 The only workaround with such peers is to use another HMAC
1141 algorithm for IPsec ("phase 2") authentication.
1144 Remove the uio_yield prototype and symbol. This function has
1145 been misnamed since it was introduced and should not be
1146 globally exposed with this name. The equivalent functionality
1147 is now available using kern_yield(curthread->td_user_pri).
1148 The function remains undocumented.
1151 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1152 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1153 for scalar sysctls is defined but disabled. Code that needs
1154 UQUAD to pass the type checking that must compile on older
1155 systems where the define is not present can check against
1156 __FreeBSD_version >= 900030.
1158 The system dialog(1) has been replaced with a new version previously
1159 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1160 with the previous version, but the libdialog associated with it has
1161 a largely incompatible API. As such, the original version of libdialog
1162 will be kept temporarily as libodialog, until its base system consumers
1163 are replaced or updated. Bump __FreeBSD_version to 900030.
1166 If you are trying to run make universe on a -stable system, and you get
1167 the following warning:
1168 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1169 unknown. config(8) likely too old."
1170 or something similar to it, then you must upgrade your -stable system
1171 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1172 stable/8) or build the config from the latest stable/8 branch and
1173 install it on your system.
1175 Prior to this date, building a current universe on 8-stable system from
1176 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1177 error in the first kernel build phase. A new config on those old
1178 systems will fix that problem for older versions of -current.
1181 The TCP stack has been modified to allow Khelp modules to interact with
1182 it via helper hook points and store per-connection data in the TCP
1183 control block. Bump __FreeBSD_version to 900029. User space tools that
1184 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1188 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1189 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1190 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1191 to take advantage of it instead of using custom implementations. This
1192 means that these drivers now no longer unconditionally advertise
1193 support for flow control but only do so if flow control is a selected
1194 media option. This was implemented in the generic support that way in
1195 order to allow flow control to be switched on and off via ifconfig(8)
1196 with the PHY specific default to typically off in order to protect
1197 from unwanted effects. Consequently, if you used flow control with
1198 one of the above mentioned drivers you now need to explicitly enable
1199 it, for example via:
1200 ifconfig bge0 media auto mediaopt flowcontrol
1202 Along with the above mentioned changes generic support for setting
1203 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1204 e1000phy(4) as well as ip1000phy(4) have been converted to take
1205 advantage of it. This means that these drivers now no longer take the
1206 link0 parameter for selecting master mode but the master media option
1207 has to be used instead, for example like in the following:
1208 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1210 Selection of master mode now is also available with all other PHY
1211 drivers supporting 1000baseT.
1214 The TCP stack has received a significant update to add support for
1215 modularised congestion control and generally improve the clarity of
1216 congestion control decisions. Bump __FreeBSD_version to 900025. User
1217 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1218 sockstat) need to be recompiled.
1221 The man(1) utility has been replaced by a new version that no longer
1222 uses /etc/manpath.config. Please consult man.conf(5) for how to
1223 migrate local entries to the new format.
1226 The copyright strings printed by login(1) and sshd(8) at the time of a
1227 new connection have been removed to follow other operating systems and
1231 A workaround for a fixed ld bug has been removed in kernel code,
1232 so make sure that your system ld is built from sources after
1233 revision 210245 from 2010-07-19 (r211583 if building head kernel
1234 on stable/8, r211584 for stable/7; both from 2010-08-21).
1235 A symptom of incorrect ld version is different addresses for
1236 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1239 The $ipv6_prefer variable in rc.conf(5) has been split into
1240 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1242 The $ip6addrctl_policy is a variable to choose a pre-defined
1243 address selection policy set by ip6addrctl(8). A value
1244 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1247 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1248 flag (see an entry of 20090926) is set on an interface with no
1249 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1250 security reason. If you want IPv6 link-local address on all
1251 interfaces by default, set this to "YES".
1253 The old ipv6_prefer="YES" is equivalent to
1254 ipv6_activate_all_interfaces="YES" and
1255 ip6addrctl_policy="ipv6_prefer".
1258 DTrace has grown support for userland tracing. Due to this, DTrace is
1259 now i386 and amd64 only.
1260 dtruss(1) is now installed by default on those systems and a new
1261 kernel module is needed for userland tracing: fasttrap.
1262 No changes to your kernel config file are necessary to enable
1263 userland tracing, but you might consider adding 'STRIP=' and
1264 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1265 to have informative userland stack traces in DTrace (ustack).
1268 The acpi_aiboost(4) driver has been removed in favor of the new
1269 aibs(4) driver. You should update your kernel configuration file.
1272 BSD grep has been imported to the base system and it is built by
1273 default. It is completely BSD licensed, highly GNU-compatible, uses
1274 less memory than its GNU counterpart and has a small codebase.
1275 However, it is slower than its GNU counterpart, which is mostly
1276 noticeable for larger searches, for smaller ones it is measurable
1277 but not significant. The reason is complex, the most important factor
1278 is that we lack a modern and efficient regex library and GNU
1279 overcomes this by optimizing the searches internally. Future work
1280 on improving the regex performance is planned, for the meantime,
1281 users that need better performance, can build GNU grep instead by
1282 setting the WITH_GNU_GREP knob.
1285 Due to the import of powerpc64 support, all existing powerpc kernel
1286 configuration files must be updated with a machine directive like this:
1287 machine powerpc powerpc
1289 In addition, an updated config(8) is required to build powerpc kernels
1293 A new version of ZFS (version 15) has been merged to -HEAD.
1294 This version uses a python library for the following subcommands:
1295 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1296 For full functionality of these commands the following port must
1297 be installed: sysutils/py-zfs
1300 'vm_page's are now hashed by physical address to an array of mutexes.
1301 Currently this is only used to serialize access to hold_count. Over
1302 time the page queue mutex will be peeled away. This changes the size
1303 of pmap on every architecture. And requires all callers of vm_page_hold
1304 and vm_page_unhold to be updated.
1307 WITH_CTF can now be specified in src.conf (not recommended, there
1308 are some problems with static executables), make.conf (would also
1309 affect ports which do not use GNU make and do not override the
1310 compile targets) or in the kernel config (via "makeoptions
1312 When WITH_CTF was specified there before this was silently ignored,
1313 so make sure that WITH_CTF is not used in places which could lead
1314 to unwanted behavior.
1317 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1318 to allow 32-bit compatibility on non-x86 platforms. All kernel
1319 configurations on amd64 and ia64 platforms using these options must
1320 be modified accordingly.
1323 The utmp user accounting database has been replaced with utmpx,
1324 the user accounting interface standardized by POSIX.
1325 Unfortunately the semantics of utmp and utmpx don't match,
1326 making it practically impossible to support both interfaces.
1327 The user accounting database is used by tools like finger(1),
1328 last(1), talk(1), w(1) and ac(8).
1330 All applications in the base system use utmpx. This means only
1331 local binaries (e.g. from the ports tree) may still use these
1332 utmp database files. These applications must be rebuilt to make
1335 After the system has been upgraded, it is safe to remove the old
1336 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1337 assuming their contents is of no importance anymore. Old wtmp
1338 databases can only be used by last(1) and ac(8) after they have
1339 been converted to the new format using wtmpcvt(1).
1342 Introduce the kernel thread "deadlock resolver" (which can be enabled
1343 via the DEADLKRES option, see NOTES for more details) and the
1344 sleepq_type() function for sleepqueues.
1347 The rc.firewall and rc.firewall6 were unified, and
1348 rc.firewall6 and rc.d/ip6fw were removed.
1349 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1350 variables are obsoleted. Instead, the following new rc
1351 variables are added to rc.d/ipfw:
1353 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1354 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1355 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1357 The meanings correspond to the relevant IPv4 variables.
1363 The default terminal emulation for syscons(4) has been changed
1364 from cons25 to xterm on all platforms except pc98. This means
1365 that the /etc/ttys file needs to be updated to ensure correct
1366 operation of applications on the console.
1368 The terminal emulation style can be toggled per window by using
1369 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1370 options can be used to change the compile-time default back to
1373 To prevent graphical artifacts, make sure the TERM environment
1374 variable is set to match the terminal emulation that is being
1375 performed by syscons(4).
1378 The layout of the structure ieee80211req_scan_result has changed.
1379 Applications that require wireless scan results (e.g. ifconfig(8))
1380 from net80211 need to be recompiled.
1382 Applications such as wpa_supplicant(8) may require a full world
1383 build without using NO_CLEAN in order to get synchronized with the
1387 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1388 There's one kernel module for each firmware. Adding "device iwnfw"
1389 to the kernel configuration file means including all three firmware
1390 images inside the kernel. If you want to include just the one for
1391 your wireless card, use the devices iwn4965fw, iwn5000fw or
1395 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1396 into rc.d/netif. The changes are the following:
1398 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1399 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1400 Note that both variables need the "inet6" keyword at the head.
1402 Do not set $ipv6_network_interfaces manually if you do not
1403 understand what you are doing. It is not needed in most cases.
1405 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1408 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1409 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1411 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1412 all configured interfaces have "inet6 accept_rtadv" in the
1413 $ifconfig_IF_ipv6. These are for backward compatibility.
1415 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1416 functionality of interfaces with no corresponding
1417 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1418 and the default address selection policy of ip6addrctl(8)
1419 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1420 Note that if you want to configure IPv6 functionality on the
1421 disabled interfaces after boot, first you need to clear the flag by
1422 using ifconfig(8) like:
1424 ifconfig em0 inet6 -ifdisabled
1426 If YES, the default address selection policy is set as
1429 The default value of $ipv6_prefer is NO.
1431 4. If your system need to receive Router Advertisement messages,
1432 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1433 scripts automatically invoke rtsol(8) when the interface becomes
1434 UP. The Router Advertisement messages are used for SLAAC
1435 (State-Less Address AutoConfiguration).
1438 802.11s D3.03 support was committed. This is incompatible with the
1439 previous code, which was based on D3.0.
1442 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1443 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1444 control whether accepting Router Advertisement messages or not.
1445 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1446 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1447 The ifconfig(8) utility now supports these flags.
1450 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1451 mount(8) and -a option for df(1) to see them.
1454 The old tunable hw.bus.devctl_disable has been superseded by
1455 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1456 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1460 Remove the option STOP_NMI. The default action is now to use NMI only
1461 for KDB via the newly introduced function stop_cpus_hard() and
1462 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1465 The stable/8 branch created in subversion. This corresponds to the
1466 RELENG_8 branch in CVS.
1469 Bump the shared library version numbers for all libraries that do not
1470 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1471 __FreeBSD_version to 800105.
1474 Due to changes in the implementation of virtual network stack support,
1475 all network-related kernel modules must be recompiled. As this change
1476 breaks the ABI, bump __FreeBSD_version to 800104.
1479 The TOE interface to the TCP syncache has been modified to remove
1480 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1481 The cxgb driver is the only TOE consumer affected by this change, and
1482 needs to be recompiled along with the kernel. As this change breaks
1483 the ABI, bump __FreeBSD_version to 800103.
1486 Padding has been added to struct tcpcb, sackhint and tcpstat in
1487 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1488 maintaining the ABI. However, this change breaks the ABI, so bump
1489 __FreeBSD_version to 800102. User space tools that rely on the size of
1490 any of these structs (e.g. sockstat) need to be recompiled.
1493 The NFS_LEGACYRPC option has been removed along with the old kernel
1494 RPC implementation that this option selected. Kernel configurations
1495 may need to be adjusted.
1498 The network interface device nodes at /dev/net/<interface> have been
1499 removed. All ioctl operations can be performed the normal way using
1500 routing sockets. The kqueue functionality can generally be replaced
1501 with routing sockets.
1504 The documentation from the FreeBSD Documentation Project (Handbook,
1505 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1506 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1509 The ABI of various structures related to the SYSV IPC API have been
1510 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1511 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1515 Layout of struct vnet has changed as routing related variables were
1516 moved to their own Vimage module. Modules need to be recompiled. Bump
1517 __FreeBSD_version to 800099.
1520 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1521 respectively. As long as no more than 16 groups per process are used,
1522 no changes should be visible. When more than 16 groups are used, old
1523 binaries may fail if they call getgroups() or getgrouplist() with
1524 statically sized storage. Recompiling will work around this, but
1525 applications should be modified to use dynamically allocated storage
1526 for group arrays as POSIX.1-2008 does not cap an implementation's
1527 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1529 NFS and portalfs mounts may also be affected as the list of groups is
1530 truncated to 16. Users of NFS who use more than 16 groups, should
1531 take care that negative group permissions are not used on the exported
1532 file systems as they will not be reliable unless a GSSAPI based
1533 authentication method is used.
1536 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1537 option compiles in the support for adaptive spinning for lockmgrs
1538 which want to enable it. The lockinit() function now accepts the flag
1539 LK_ADAPTIVE in order to make the lock object subject to adaptive
1540 spinning when both held in write and read mode.
1543 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1544 changed. User applications that use this ioctl need to be rebuilt.
1547 The layout of struct thread has changed. Kernel and modules need to
1551 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1552 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1555 window(1) has been removed from the base system. It can now be
1556 installed from ports. The port is called misc/window.
1559 The way we are storing and accessing `routing table' entries has
1560 changed. Programs reading the FIB, like netstat, need to be
1564 A new netisr implementation has been added for FreeBSD 8. Network
1565 file system modules, such as igmp, ipdivert, and others, should be
1567 Bump __FreeBSD_version to 800096.
1570 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1574 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1575 Bump __FreeBSD_version to 800094.
1578 Add mnt_xflag field to 'struct mount'. File system modules need to be
1580 Bump __FreeBSD_version to 800093.
1583 The compiling option ADAPTIVE_SX has been retired while it has been
1584 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1585 The KPI for sx_init_flags() changes as accepting flags:
1586 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1587 been introduced in order to handle the reversed logic.
1588 Bump __FreeBSD_version to 800092.
1591 Add support for hierarchical jails. Remove global securelevel.
1592 Bump __FreeBSD_version to 800091.
1595 The layout of struct vnet_net has changed, therefore modules
1597 Bump __FreeBSD_version to 800090.
1600 The newly imported zic(8) produces a new format in the output. Please
1601 run tzsetup(8) to install the newly created data to /etc/localtime.
1604 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1605 hw.usb.* and is now consistent again with previous releases.
1608 802.11 monitor mode support was revised and driver api's were changed.
1609 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1610 of DLT_IEEE802_11. No user-visible data structures were changed but
1611 applications that use DLT_IEEE802_11 may require changes.
1612 Bump __FreeBSD_version to 800088.
1615 The layout of the following structs has changed: sysctl_oid,
1616 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1617 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1618 panics may be experienced. World rebuild is required for
1619 correctly checking networking state from userland.
1620 Bump __FreeBSD_version to 800085.
1623 MLDv2 and Source-Specific Multicast (SSM) have been merged
1624 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1625 The implementation of SSM within FreeBSD's IPv6 stack closely
1626 follows the IPv4 implementation.
1628 For kernel developers:
1630 * The most important changes are that the ip6_output() and
1631 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1632 and this lock has been downgraded to a non-recursive mutex.
1634 * As with the changes to the IPv4 stack to support SSM, filtering
1635 of inbound multicast traffic must now be performed by transport
1636 protocols within the IPv6 stack. This does not apply to TCP and
1637 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1639 * The KPIs used by IPv6 multicast are similar to those used by
1640 the IPv4 stack, with the following differences:
1641 * im6o_mc_filter() is analogous to imo_multicast_filter().
1642 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1643 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1644 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1645 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1646 for MLDv1 have an additional 'timer' argument which is used to
1647 jitter the initial membership report for the solicited-node
1648 multicast membership on-link.
1649 * This is not strictly needed for MLDv2, which already jitters
1650 its report transmissions. However, the 'timer' argument is
1651 preserved in case MLDv1 is active on the interface.
1653 * The KAME linked-list based IPv6 membership implementation has
1654 been refactored to use a vector similar to that used by the IPv4
1656 Code which maintains a list of its own multicast memberships
1657 internally, e.g. carp, has been updated to reflect the new
1660 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1661 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1662 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1663 implementation constraint which needs to be addressed in HEAD.
1665 For application developers:
1667 * The changes are broadly similar to those made for the IPv4
1670 * The use of IPv4 and IPv6 multicast socket options on the same
1671 socket, using mapped addresses, HAS NOT been tested or supported.
1673 * There are a number of issues with the implementation of various
1674 IPv6 multicast APIs which need to be resolved in the API surface
1675 before the implementation is fully compatible with KAME userland
1676 use, and these are mostly to do with interface index treatment.
1678 * The literature available discusses the use of either the delta / ASM
1679 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1680 using setsourcefilter(3)/getsourcefilter(3). For more information
1681 please refer to RFC 3768, 'Socket Interface Extensions for
1682 Multicast Source Filters'.
1684 * Applications which use the published RFC 3678 APIs should be fine.
1686 For systems administrators:
1688 * The mtest(8) utility has been refactored to support IPv6, in
1689 addition to IPv4. Interface addresses are no longer accepted
1690 as arguments, their names must be used instead. The utility
1691 will map the interface name to its first IPv4 address as
1692 returned by getifaddrs(3).
1694 * The ifmcstat(8) utility has also been updated to print the MLDv2
1695 endpoint state and source filter lists via sysctl(3).
1697 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1698 loopback of IPv6 multicast datagrams by default; it defaults to 1
1699 to preserve the existing behaviour. Disabling multicast loopback is
1700 recommended for optimal system performance.
1702 * The IPv6 MROUTING code has been changed to examine this sysctl
1703 instead of attempting to perform a group lookup before looping
1704 back forwarded datagrams.
1706 Bump __FreeBSD_version to 800084.
1709 Implement low-level Bluetooth HCI API.
1710 Bump __FreeBSD_version to 800083.
1713 The layout of struct malloc_type, used by modules to register new
1714 memory allocation types, has changed. Most modules will need to
1715 be rebuilt or panics may be experienced.
1716 Bump __FreeBSD_version to 800081.
1719 Anticipate overflowing inp_flags - add inp_flags2.
1720 This changes most offsets in inpcb, so checking v4 connection
1721 state will require a world rebuild.
1722 Bump __FreeBSD_version to 800080.
1725 Add an llentry to struct route and struct route_in6. Modules
1726 embedding a struct route will need to be recompiled.
1727 Bump __FreeBSD_version to 800079.
1730 The size of rt_metrics_lite and by extension rtentry has changed.
1731 Networking administration apps will need to be recompiled.
1732 The route command now supports show as an alias for get, weighting
1733 of routes, sticky and nostick flags to alter the behavior of stateful
1735 Bump __FreeBSD_version to 800078.
1738 Do not use Giant for kbdmux(4) locking. This is wrong and
1739 apparently causing more problems than it solves. This will
1740 re-open the issue where interrupt handlers may race with
1741 kbdmux(4) in polling mode. Typical symptoms include (but
1742 not limited to) duplicated and/or missing characters when
1743 low level console functions (such as gets) are used while
1744 interrupts are enabled (for example geli password prompt,
1745 mountroot prompt etc.). Disabling kbdmux(4) may help.
1748 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1749 kernel modules referencing any of the above need to be recompiled.
1750 Bump __FreeBSD_version to 800075.
1753 GEOM_PART has become the default partition slicer for storage devices,
1754 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1755 introduces some changes:
1757 MSDOS/EBR: the devices created from MSDOS extended partition entries
1758 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1759 to devices with offset-based names. fstabs may need to be modified.
1761 BSD: the "geometry does not match label" warning is harmless in most
1762 cases but it points to problems in file system misalignment with
1763 disk geometry. The "c" partition is now implicit, covers the whole
1764 top-level drive and cannot be (mis)used by users.
1766 General: Kernel dumps are now not allowed to be written to devices
1767 whose partition types indicate they are meant to be used for file
1768 systems (or, in case of MSDOS partitions, as something else than
1771 Most of these changes date approximately from 200812.
1774 The uscanner(4) driver has been removed from the kernel. This follows
1775 Linux removing theirs in 2.6 and making libusb the default interface
1776 (supported by sane).
1779 The multicast forwarding code has been cleaned up. netstat(1)
1780 only relies on KVM now for printing bandwidth upcall meters.
1781 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1782 ip6_mroute_mod respectively. The config(5) options for statically
1783 compiling this code remain the same, i.e. 'options MROUTING'.
1786 Support for the IFF_NEEDSGIANT network interface flag has been
1787 removed, which means that non-MPSAFE network device drivers are no
1788 longer supported. In particular, if_ar, if_sr, and network device
1789 drivers from the old (legacy) USB stack can no longer be built or
1793 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1794 a bunch of new language catalog files have also been added.
1795 This means that some common libc messages are now localized and
1796 they depend on the LC_MESSAGES environmental variable.
1799 The k8temp(4) driver has been renamed to amdtemp(4) since
1800 support for Family 10 and Family 11 CPU families was added.
1803 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1804 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1806 For kernel developers, the most important changes are that the
1807 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1808 and this lock has been downgraded to a non-recursive mutex.
1810 Transport protocols (UDP, Raw IP) are now responsible for filtering
1811 inbound multicast traffic according to group membership and source
1812 filters. The imo_multicast_filter() KPI exists for this purpose.
1813 Transports which do not use multicast (SCTP, TCP) already reject
1814 multicast by default. Forwarding and receive performance may improve
1815 as a mutex acquisition is no longer needed in the ip_input()
1816 low-level input path. in_addmulti() and in_delmulti() are shimmed
1817 to new KPIs which exist to support SSM in-kernel.
1819 For application developers, it is recommended that loopback of
1820 multicast datagrams be disabled for best performance, as this
1821 will still cause the lock to be taken for each looped-back
1822 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1823 be tuned to 0 to disable loopback by default; it defaults to 1
1824 to preserve the existing behaviour.
1826 For systems administrators, to obtain best performance with
1827 multicast reception and multiple groups, it is always recommended
1828 that a card with a suitably precise hash filter is used. Hash
1829 collisions will still result in the lock being taken within the
1830 transport protocol input path to check group membership.
1832 If deploying FreeBSD in an environment with IGMP snooping switches,
1833 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1834 enabled; this forces 224.0.0.0/24 group membership to be announced
1837 The size of 'struct igmpstat' has changed; netstat needs to be
1838 recompiled to reflect this.
1839 Bump __FreeBSD_version to 800070.
1842 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1843 updated to use it. This requires a buildworld/installworld in order to
1844 update the library and dependencies (usbconfig, etc). Its advisable to
1845 rebuild all ports which uses libusb. More specific directions are given
1846 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1847 libusb are no longer required and can be removed.
1850 A workaround is committed to allow the creation of System V shared
1851 memory segment of size > 2 GB on the 64-bit architectures.
1852 Due to a limitation of the existing ABI, the shm_segsz member
1853 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1854 wrong for large segments. Note that limits must be explicitly
1855 raised to allow such segments to be created.
1858 The layout of struct ifnet has changed, requiring a rebuild of all
1859 network device driver modules.
1862 The /dev handling for the new USB stack has changed, a
1863 buildworld/installworld is required for libusb20.
1866 The new USB2 stack has now been permanently moved in and all kernel and
1867 module names reverted to their previous values (eg, usb, ehci, ohci,
1868 ums, ...). The old usb stack can be compiled in by prefixing the name
1869 with the letter 'o', the old usb modules have been removed.
1870 Updating entry 20090216 for xorg and 20090215 for libmap may still
1874 The rc.conf(5) option if_up_delay has been renamed to
1875 defaultroute_delay to better reflect its purpose. If you have
1876 customized this setting in /etc/rc.conf you need to update it to
1880 xorg 7.4 wants to configure its input devices via hald which does not
1881 yet work with USB2. If the keyboard/mouse does not work in xorg then
1883 Option "AllowEmptyInput" "off"
1884 to your ServerLayout section. This will cause X to use the configured
1885 kbd and mouse sections from your xorg.conf.
1888 The GENERIC kernels for all architectures now default to the new USB2
1889 stack. No kernel config options or code have been removed so if a
1890 problem arises please report it and optionally revert to the old USB
1891 stack. If you are loading USB kernel modules or have a custom kernel
1892 that includes GENERIC then ensure that usb names are also changed over,
1893 eg uftdi -> usb2_serial_ftdi.
1895 Older programs linked against the ports libusb 0.1 need to be
1896 redirected to the new stack's libusb20. /etc/libmap.conf can
1898 # Map old usb library to new one for usb2 stack
1899 libusb-0.1.so.8 libusb20.so.1
1902 All USB ethernet devices now attach as interfaces under the name ueN
1903 (eg. ue0). This is to provide a predictable name as vendors often
1904 change usb chipsets in a product without notice.
1907 The ichsmb(4) driver has been changed to require SMBus slave
1908 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1909 All of the other SMBus controller drivers require left-justified
1910 slave addresses, so this change makes all the drivers provide the
1914 INET6 statistics (struct ip6stat) was updated.
1915 netstat(1) needs to be recompiled.
1918 NTFS has been removed from GENERIC kernel on amd64 to match
1919 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1920 will load ntfs.ko module automatically when NTFS support is
1921 actually needed, unless ntfs.ko is not installed or security
1922 level prohibits loading kernel modules. If either is the case,
1923 "options NTFS" has to be added into kernel config.
1926 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1927 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1928 800061. User space tools that rely on the size of struct tcpcb in
1929 tcp_var.h (e.g. sockstat) need to be recompiled.
1932 ng_tty(4) module updated to match the new TTY subsystem.
1933 Due to API change, user-level applications must be updated.
1934 New API support added to mpd5 CVS and expected to be present
1935 in next mpd5.3 release.
1938 With __FreeBSD_version 800060 the makefs tool is part of
1939 the base system (it was a port).
1942 The afdata and ifnet locks have been changed from mutexes to
1943 rwlocks, network modules will need to be re-compiled.
1946 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1947 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1948 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1949 architecture and 40 bytes on 64-bit architecture. The userland
1950 applications "arp" and "ndp" have been updated accordingly.
1951 The output from "netstat -r" shows only routing entries and
1952 none of the L2 information.
1955 __FreeBSD_version 800057 marks the switchover from the
1956 binary ath hal to source code. Users must add the line:
1958 options AH_SUPPORT_AR5416
1960 to their kernel config files when specifying:
1964 The ath_hal module no longer exists; the code is now compiled
1965 together with the driver in the ath module. It is now
1966 possible to tailor chip support (i.e. reduce the set of chips
1967 and thereby the code size); consult ath_hal(4) for details.
1970 __FreeBSD_version 800054 adds memory barriers to
1971 <machine/atomic.h>, new interfaces to ifnet to facilitate
1972 multiple hardware transmit queues for cards that support
1973 them, and a lock-less ring-buffer implementation to
1974 enable drivers to more efficiently manage queueing of
1978 A new version of ZFS (version 13) has been merged to -HEAD.
1979 This version has zpool attribute "listsnapshots" off by
1980 default, which means "zfs list" does not show snapshots,
1981 and is the same as Solaris behavior.
1984 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1987 The uhci, ohci, ehci and slhci USB Host controller drivers have
1988 been put into separate modules. If you load the usb module
1989 separately through loader.conf you will need to load the
1990 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1991 controller add the following to loader.conf:
1997 The ABI used by the PMC toolset has changed. Please keep
1998 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
2002 atapci kernel module now includes only generic PCI ATA
2003 driver. AHCI driver moved to ataahci kernel module.
2004 All vendor-specific code moved into separate kernel modules:
2005 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
2006 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
2007 atamarvell, atamicron, atanational, atanetcell, atanvidia,
2008 atapromise, ataserverworks, atasiliconimage, atasis, atavia
2011 The TTY subsystem of the kernel has been replaced by a new
2012 implementation, which provides better scalability and an
2013 improved driver model. Most common drivers have been migrated to
2014 the new TTY subsystem, while others have not. The following
2015 drivers have not yet been ported to the new TTY layer:
2018 cy, digi, rc, rp, sio
2024 ng_h4, ng_tty, ppp, sl, snp
2026 Adding these drivers to your kernel configuration file shall
2027 cause compilation to fail.
2030 ntpd has been upgraded to 4.2.4p5.
2033 OpenSSH has been upgraded to 5.1p1.
2035 For many years, FreeBSD's version of OpenSSH preferred DSA
2036 over RSA for host and user authentication keys. With this
2037 upgrade, we've switched to the vendor's default of RSA over
2038 DSA. This may cause upgraded clients to warn about unknown
2039 host keys even for previously known hosts. Users should
2040 follow the usual procedure for verifying host keys before
2041 accepting the RSA key.
2043 This can be circumvented by setting the "HostKeyAlgorithms"
2044 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
2047 Please note that the sequence of keys offered for
2048 authentication has been changed as well. You may want to
2049 specify IdentityFile in a different order to revert this
2053 The sio(4) driver has been removed from the i386 and amd64
2054 kernel configuration files. This means uart(4) is now the
2055 default serial port driver on those platforms as well.
2057 To prevent collisions with the sio(4) driver, the uart(4) driver
2058 uses different names for its device nodes. This means the
2059 onboard serial port will now most likely be called "ttyu0"
2060 instead of "ttyd0". You may need to reconfigure applications to
2061 use the new device names.
2063 When using the serial port as a boot console, be sure to update
2064 /boot/device.hints and /etc/ttys before booting the new kernel.
2065 If you forget to do so, you can still manually specify the hints
2066 at the loader prompt:
2068 set hint.uart.0.at="isa"
2069 set hint.uart.0.port="0x3F8"
2070 set hint.uart.0.flags="0x10"
2071 set hint.uart.0.irq="4"
2075 The gpt(8) utility has been removed. Use gpart(8) to partition
2079 The version that Linuxulator emulates was changed from 2.4.2
2080 to 2.6.16. If you experience any problems with Linux binaries
2081 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2082 if it fixes the problem contact emulation mailing list.
2085 ISDN4BSD (I4B) was removed from the src tree. You may need to
2086 update a your kernel configuration and remove relevant entries.
2089 I have checked in code to support multiple routing tables.
2090 See the man pages setfib(1) and setfib(2).
2091 This is a hopefully backwards compatible version,
2092 but to make use of it you need to compile your kernel
2093 with options ROUTETABLES=2 (or more up to 16).
2096 The 802.11 wireless support was redone to enable multi-bss
2097 operation on devices that are capable. The underlying device
2098 is no longer used directly but instead wlanX devices are
2099 cloned with ifconfig. This requires changes to rc.conf files.
2100 For example, change:
2101 ifconfig_ath0="WPA DHCP"
2104 ifconfig_wlan0="WPA DHCP"
2105 see rc.conf(5) for more details. In addition, mergemaster of
2106 /etc/rc.d is highly recommended. Simultaneous update of userland
2107 and kernel wouldn't hurt either.
2109 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2110 modules were merged into the base wlan module. All references
2111 to these modules (e.g. in kernel config files) must be removed.
2114 psm(4) has gained write(2) support in native operation level.
2115 Arbitrary commands can be written to /dev/psm%d and status can
2116 be read back from it. Therefore, an application is responsible
2117 for status validation and error recovery. It is a no-op in
2118 other operation levels.
2121 Support for KSE threading has been removed from the kernel. To
2122 run legacy applications linked against KSE libmap.conf may
2123 be used. The following libmap.conf may be used to ensure
2124 compatibility with any prior release:
2126 libpthread.so.1 libthr.so.1
2127 libpthread.so.2 libthr.so.2
2128 libkse.so.3 libthr.so.3
2131 The layout of struct vmspace has changed. This affects libkvm
2132 and any executables that link against libkvm and use the
2133 kvm_getprocs() function. In particular, but not exclusively,
2134 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2135 The effects are minimal, but it's advisable to upgrade world
2139 The latest em driver no longer has support in it for the
2140 82575 adapter, this is now moved to the igb driver. The
2141 split was done to make new features that are incompatible
2142 with older hardware easier to do.
2145 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2146 likewise the kernel option is now GEOM_LINUX_LVM.
2149 The default NFS mount mode has changed from UDP to TCP for
2150 increased reliability. If you rely on (insecurely) NFS
2151 mounting across a firewall you may need to update your
2155 Belatedly note the addition of m_collapse for compacting
2159 The fts(3) structures have been changed to use adequate
2160 integer types for their members and so to be able to cope
2161 with huge file trees. The old fts(3) ABI is preserved
2162 through symbol versioning in libc, so third-party binaries
2163 using fts(3) should still work, although they will not take
2164 advantage of the extended types. At the same time, some
2165 third-party software might fail to build after this change
2166 due to unportable assumptions made in its source code about
2167 fts(3) structure members. Such software should be fixed
2168 by its vendor or, in the worst case, in the ports tree.
2169 FreeBSD_version 800015 marks this change for the unlikely
2170 case that a portable fix is impossible.
2173 To upgrade to -current after this date, you must be running
2174 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2175 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2178 The ADAPTIVE_GIANT kernel option has been retired because its
2179 functionality is the default now.
2182 The AT keyboard emulation of sunkbd(4) has been turned on
2183 by default. In order to make the special symbols of the Sun
2184 keyboards driven by sunkbd(4) work under X these now have
2185 to be configured the same way as Sun USB keyboards driven
2186 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2188 Option "XkbLayout" "us"
2189 Option "XkbRules" "xorg"
2190 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2193 It has been decided that it is desirable to provide ABI
2194 backwards compatibility to the FreeBSD 4/5/6 versions of the
2195 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2196 broken with the introduction of PCI domain support (see the
2197 20070930 entry). Unfortunately, this required the ABI of
2198 PCIOCGETCONF to be broken again in order to be able to
2199 provide backwards compatibility to the old version of that
2200 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2201 again. As for prominent ports this affects neither pciutils
2202 nor xorg-server this time, the hal port needs to be rebuilt
2206 The misnamed kthread_create() and friends have been renamed
2207 to kproc_create() etc. Many of the callers already
2208 used kproc_start()..
2209 I will return kthread_create() and friends in a while
2210 with implementations that actually create threads, not procs.
2211 Renaming corresponds with version 800002.
2220 Avoid using make -j when upgrading. While generally safe, there are
2221 sometimes problems using -j to upgrade. If your upgrade fails with
2222 -j, please try again without -j. From time to time in the past there
2223 have been problems using -j with buildworld and/or installworld. This
2224 is especially true when upgrading between "distant" versions (eg one
2225 that cross a major release boundary or several minor releases, or when
2226 several months have passed on the -current branch).
2228 Sometimes, obscure build problems are the result of environment
2229 poisoning. This can happen because the make utility reads its
2230 environment when searching for values for global variables. To run
2231 your build attempts in an "environmental clean room", prefix all make
2232 commands with 'env -i '. See the env(1) manual page for more details.
2234 When upgrading from one major version to another it is generally best
2235 to upgrade to the latest code in the currently installed branch first,
2236 then do an upgrade to the new branch. This is the best-tested upgrade
2237 path, and has the highest probability of being successful. Please try
2238 this approach before reporting problems with a major version upgrade.
2240 When upgrading a live system, having a root shell around before
2241 installing anything can help undo problems. Not having a root shell
2242 around can lead to problems if pam has changed too much from your
2243 starting point to allow continued authentication after the upgrade.
2247 When upgrading the boot ZFS pool to a new version, always follow
2250 1.) recompile and reinstall the ZFS boot loader and boot block
2251 (this is part of "make buildworld" and "make installworld")
2253 2.) update the ZFS boot block on your boot drive
2255 The following example updates the ZFS boot block on the first
2256 partition (freebsd-boot) of a GPT partitioned drive ad0:
2257 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2259 Non-boot pools do not need these updates.
2263 If you are updating from a prior version of FreeBSD (even one just
2264 a few days old), you should follow this procedure. It is the most
2265 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2267 make kernel-toolchain
2268 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2269 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2271 To test a kernel once
2272 ---------------------
2273 If you just want to boot a kernel once (because you are not sure
2274 if it works, or if you want to boot a known bad kernel to provide
2275 debugging information) run
2276 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2277 nextboot -k testkernel
2279 To just build a kernel when you know that it won't mess you up
2280 --------------------------------------------------------------
2281 This assumes you are already running a CURRENT system. Replace
2282 ${arch} with the architecture of your machine (e.g. "i386",
2283 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2285 cd src/sys/${arch}/conf
2286 config KERNEL_NAME_HERE
2287 cd ../compile/KERNEL_NAME_HERE
2292 If this fails, go to the "To build a kernel" section.
2294 To rebuild everything and install it on the current system.
2295 -----------------------------------------------------------
2296 # Note: sometimes if you are running current you gotta do more than
2297 # is listed here if you are upgrading from a really old current.
2299 <make sure you have good level 0 dumps>
2301 make kernel KERNCONF=YOUR_KERNEL_HERE
2303 <reboot in single user> [3]
2310 To cross-install current onto a separate partition
2311 --------------------------------------------------
2312 # In this approach we use a separate partition to hold
2313 # current's root, 'usr', and 'var' directories. A partition
2314 # holding "/", "/usr" and "/var" should be about 2GB in
2317 <make sure you have good level 0 dumps>
2320 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2321 <maybe newfs current's root partition>
2322 <mount current's root partition on directory ${CURRENT_ROOT}>
2323 make installworld DESTDIR=${CURRENT_ROOT}
2324 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2325 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2326 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2327 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2328 <reboot into current>
2329 <do a "native" rebuild/install as described in the previous section>
2330 <maybe install compatibility libraries from ports/misc/compat*>
2334 To upgrade in-place from stable to current
2335 ----------------------------------------------
2336 <make sure you have good level 0 dumps>
2338 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2340 <reboot in single user> [3]
2347 Make sure that you've read the UPDATING file to understand the
2348 tweaks to various things you need. At this point in the life
2349 cycle of current, things change often and you are on your own
2350 to cope. The defaults can also change, so please read ALL of
2351 the UPDATING entries.
2353 Also, if you are tracking -current, you must be subscribed to
2354 freebsd-current@freebsd.org. Make sure that before you update
2355 your sources that you have read and understood all the recent
2356 messages there. If in doubt, please track -stable which has
2357 much fewer pitfalls.
2359 [1] If you have third party modules, such as vmware, you
2360 should disable them at this point so they don't crash your
2363 [3] From the bootblocks, boot -s, and then do
2368 adjkerntz -i # if CMOS is wall time
2369 Also, when doing a major release upgrade, it is required that
2370 you boot into single user mode to do the installworld.
2372 [4] Note: This step is non-optional. Failure to do this step
2373 can result in a significant reduction in the functionality of the
2374 system. Attempting to do it by hand is not recommended and those
2375 that pursue this avenue should read this file carefully, as well
2376 as the archives of freebsd-current and freebsd-hackers mailing lists
2377 for potential gotchas. The -U option is also useful to consider.
2378 See mergemaster(8) for more information.
2380 [5] Usually this step is a noop. However, from time to time
2381 you may need to do this if you get unknown user in the following
2382 step. It never hurts to do it all the time. You may need to
2383 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2384 install) after the buildworld before this step if you last updated
2385 from current before 20130425 or from -stable before 20130430.
2387 [6] This only deletes old files and directories. Old libraries
2388 can be deleted by "make delete-old-libs", but you have to make
2389 sure that no program is using those libraries anymore.
2391 [8] In order to have a kernel that can run the 4.x binaries needed to
2392 do an installworld, you must include the COMPAT_FREEBSD4 option in
2393 your kernel. Failure to do so may leave you with a system that is
2394 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2395 required to run the 5.x binaries on more recent kernels. And so on
2396 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2398 Make sure that you merge any new devices from GENERIC since the
2399 last time you updated your kernel config file.
2401 [9] When checking out sources, you must include the -P flag to have
2402 cvs prune empty directories.
2404 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2405 "?=" instead of the "=" assignment operator, so that buildworld can
2406 override the CPUTYPE if it needs to.
2408 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2409 not on the command line, or in /etc/make.conf. buildworld will
2410 warn if it is improperly defined.
2413 This file contains a list, in reverse chronological order, of major
2414 breakages in tracking -current. It is not guaranteed to be a complete
2415 list of such breakages, and only contains entries since October 10, 2007.
2416 If you need to see UPDATING entries from before that date, you will need
2417 to fetch an UPDATING file from an older FreeBSD release.
2419 Copyright information:
2421 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2423 Redistribution, publication, translation and use, with or without
2424 modification, in full or in part, in any form or format of this
2425 document are permitted without further permission from the author.
2427 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2428 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2429 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2430 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2431 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2432 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2433 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2434 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2435 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2436 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2437 POSSIBILITY OF SUCH DAMAGE.
2439 Contact Warner Losh if you have any questions about your use of
projects / FreeBSD / releng / 10.3.git / blob