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 20160127 p28 FreeBSD-SA-16:09.ntp
20 FreeBSD-SA-16:10.linux
22 Fix multiple vulnerabilities of ntp. [SA-16:09]
24 Fix Linux compatibility layer issetugid(2) system call
25 vulnerability. [SA-16:10]
27 20160114 p27 FreeBSD-SA-16:07.openssh
29 Fix OpenSSH client information leak. [SA-16:07]
31 20160114 p26 FreeBSD-EN-16:02.pf
32 FreeBSD-EN-16:03.yplib
35 FreeBSD-SA-16:03.linux
36 FreeBSD-SA-16:04.linux
38 FreeBSD-SA-16:06.bsnmpd
40 Fix pf(4) generating bad TCP checksums. [EN-16:02]
41 Fix infinite loop in YP/NIS client library. [EN-16:03]
42 Fix remote denial of service in SCTP. [SA-16:01]
43 Update NTP to 4.2.8p5. [SA-16:02]
44 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
45 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
46 Fix crash in TCP MD5 signatures. [SA-16:05]
47 Fix insecure default permissions for snmpd.config. [SA-16:06]
49 20151205 p25 FreeBSD-SA-15:26.openssl
51 Fix multiple OpenSSL vulnerabilities. [SA-15:26]
53 20151104 p24 FreeBSD-SA-15:25.ntp [revised]
54 FreeBSD-EN-15:19.kqueue
57 Fix regression in ntpd(8) lacking support for RAWDCF reference
58 clock in 10.1-RELEASE-p23. [SA-15:25.ntp]
60 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
62 Fix applications exiting due to segmentation violation on a correct
63 memory address. [EN-15:20]
65 20151026: p23 FreeBSD-SA-15:25.ntp
67 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
69 The configuration file syntax has been changed, thus mergemaster
70 run is recommended. Now the "kod" parameter requires "limited"
71 parameter. If the ntp.conf is not updated, the ntpd will run
72 successfully, but with KoD disabled.
74 20151002: p22 FreeBSD-SA-15:24.rpcbind [revised]
75 Revised patch to address a regression that prevents NIS from working.
77 20150929: p21 FreeBSD-SA-15:24.rpcbind
79 Fix rpcbind(8) remote denial of service. [SA-15:24]
81 20150916: p20 FreeBSD-EN-15:18.pkg
83 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
85 20150825: p19 FreeBSD-SA-15:21.amd64
86 FreeBSD-SA-15:22.openssh
87 FreeBSD-EN-15:14.ixgbe
90 Fix local privilege escalation in IRET handler. [SA-15:21]
92 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
94 Disabled ixgbe(4) flow-director support. [EN-15:14]
96 Fix insufficient check of unsupported pkg(7) signature methods.
99 20150818: p18 FreeBSD-SA-15:20.expat
101 Fix multiple integer overflows in expat (libbsdxml) XML parser.
104 20150805: p17 FreeBSD-SA-15:18.bsdpatch
105 FreeBSD-SA-15:19.routed
107 Fix patch(1) shell injection vulnerability via ed(1).
110 Fix routed remote denial of service vulnerability. [SA-15:19]
112 20150728: p16 FreeBSD-SA-15:14.bsdpatch
114 FreeBSD-SA-15:16.openssh
116 Fix patch(1) shell injection vulnerability. [SA-15:14]
118 Fix resource exhaustion in TCP reassembly. [SA-15:15]
120 Fix OpenSSH multiple vulnerabilities. [SA-15:16]
122 20150721: p15 FreeBSD-SA-15:13.tcp
124 Fix resource exhaustion due to sessions stuck in LAST_ACK state.
127 20150630: p14 FreeBSD-EN-15:08.sendmail [revised]
128 FreeBSD-EN-15:09.xlocale
129 FreeBSD-EN-15:10.iconv
131 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
133 Fix inconsistency between locale and rune locale states.
136 Improved iconv(3) UTF-7 support. [EN-15:10]
138 20150618: p13 FreeBSD-EN-15:08.sendmail
139 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
141 20150612: p12 FreeBSD-SA-15:10.openssl
142 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
144 20150609: p11 FreeBSD-EN-15:06.file
147 Updated base system file(1) to 5.22 to address multiple denial
148 of service issues. [EN-15:06]
150 Improved reliability of ZFS when TRIM/UNMAP and/or L2ARC is used.
153 20150513: p10 FreeBSD-EN-15:04.freebsd-update
156 Fix bug with freebsd-update(8) that does not ensure the previous
157 upgrade was completed. [EN-15:04]
159 Fix deadlock on reboot with UFS tuned with SU+J. [EN-15:05]
161 20150407: p9 FreeBSD-SA-15:04.igmp [revised]
163 FreeBSD-SA-15:08.bsdinstall
164 FreeBSD-SA-15:09.ipv6
166 Improved patch for SA-15:04.igmp.
168 Fix multiple vulnerabilities of ntp. [SA-15:07]
170 Fix bsdinstall(8) insecure default GELI keyfile permissions. [SA-15:08]
172 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
175 Fix patch for SA-15:06.openssl.
177 20150319: p7 FreeBSD-SA-15:06.openssl
178 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
180 20150225: p6 FreeBSD-SA-15:04.igmp
182 FreeBSD-EN-15:02.openssl
183 FreeBSD-EN-15:03.freebsd-update
185 Fix integer overflow in IGMP protocol. [SA-15:04]
187 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
189 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
191 Fix freebsd-update libraries update ordering issue. [EN-15:03]
193 20150127: p5 FreeBSD-SA-15:02.kmem
194 FreeBSD-SA-15:03.sctp
196 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
197 vulnerability. [SA-15:02]
199 Fix SCTP stream reset vulnerability. [SA-15:03]
201 20150114: p4 FreeBSD-SA-15:01.openssl
202 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
204 20141223: p3 FreeBSD-SA-14:31.ntp
205 FreeBSD-EN-14:13.freebsd-update
207 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
208 Fix directory deletion issue in freebsd-update. [EN-14:13]
210 20141217: p2 FreeBSD-SA-14:30.unbound
211 Fix unbound remote denial of service vulnerability.
213 20141210: p1 FreeBSD-SA-14:27.stdio
214 FreeBSD-SA-14:28.file
216 Fix buffer overflow in stdio. [SA-14:27]
218 Fix multiple vulnerabilities in file(1) and libmagic(3).
222 The ofwfb driver, used to provide a graphics console on PowerPC when
223 using vt(4), no longer allows mmap() of all of physical memory. This
224 will prevent Xorg on PowerPC with some ATI graphics cards from
225 initializing properly unless x11-servers/xorg-server is updated to
229 The libatf-c and libatf-c++ major versions were downgraded to 0 and
230 1 respectively to match the upstream numbers. They were out of
231 sync because, when they were originally added to FreeBSD, the
232 upstream versions were not respected. These libraries are private
233 and not yet built by default, so renumbering them should be a
234 non-issue. However, unclean source trees will yield broken test
235 programs once the operator executes "make delete-old-libs" after a
238 Additionally, the atf-sh binary was made private by moving it into
239 /usr/libexec/. Already-built shell test programs will keep the
240 path to the old binary so they will break after "make delete-old"
243 If you are using WITH_TESTS=yes (not the default), wipe the object
244 tree and rebuild from scratch to prevent spurious test failures.
245 This is only needed once: the misnumbered libraries and misplaced
246 binaries have been added to OptionalObsoleteFiles.inc so they will
247 be removed during a clean upgrade.
250 The ixgbe tunables now match their sysctl counterparts, for example:
251 hw.ixgbe.enable_aim => hw.ix.enable_aim
252 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
255 The NFSv4.1 server committed by r269398 changes the internal
256 function call interfaces used between the NFS and krpc modules.
257 As such, __FreeBSD_version was bumped.
260 The default unbound configuration has been modified to address
261 issues with reverse lookups on networks that use private
262 address ranges. If you use the local_unbound service, run
263 "service local_unbound setup" as root to regenerate your
264 configuration, then "service local_unbound reload" to load the
268 It is no longer necessary to include the dwarf version in your DEBUG
269 options in your kernel config file. The bug that required it to be
270 placed in the config file has bene fixed. DEBUG should now just
271 contain -g. The build system will automatically update things
272 to do the right thing.
275 Several ABI breaking changes were merged to CTL and new iSCSI code.
276 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
277 iscsictl need to be rebuilt to work with a new kernel.
280 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
281 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
282 which differs from the behaviour controlled by this knob.)
285 On i386 and amd64 systems, the onifconsole flag is now set by default
286 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
287 as a login TTY if it is set in the bootloader as an active kernel
288 console. No changes in behavior should result otherwise. To revert to
289 the previous behavior, set ttyu0 to "off" in /etc/ttys.
292 Clang and llvm have been upgraded to 3.4.1 release.
295 Clang and llvm have been upgraded to 3.4 release.
298 If a Makefile in a tests/ directory was auto-generating a Kyuafile
299 instead of providing an explicit one, this would prevent such
300 Makefile from providing its own Kyuafile in the future during
301 NO_CLEAN builds. This has been fixed in the Makefiles but manual
302 intervention is needed to clean an objdir if you use NO_CLEAN:
303 # find /usr/obj -name Kyuafile | xargs rm -f
306 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
307 capability mode support. Please note that enabling the feature in
308 kernel is still highly recommended.
311 OpenSSH is now built with sandbox support, and will use sandbox as
312 the default privilege separation method. This requires Capsicum
313 capability mode support in kernel.
316 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
317 been deprecated and will not be part of FreeBSD 11.0 and later
318 releases. If you use this driver, please consider switching to
319 the nfe(4) driver instead.
325 The behavior of gss_pseudo_random() for the krb5 mechanism
326 has changed, for applications requesting a longer random string
327 than produced by the underlying enctype's pseudo-random() function.
328 In particular, the random string produced from a session key of
329 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
330 be different at the 17th octet and later, after this change.
331 The counter used in the PRF+ construction is now encoded as a
332 big-endian integer in accordance with RFC 4402.
333 __FreeBSD_version is bumped to 1000701.
336 The WITHOUT_ATF build knob has been removed and its functionality
337 has been subsumed into the more generic WITHOUT_TESTS. If you were
338 using the former to disable the build of the ATF libraries, you
339 should change your settings to use the latter.
342 The default version of mtree is nmtree which is obtained from
343 NetBSD. The output is generally the same, but may vary
344 slightly. If you found you need identical output adding
345 "-F freebsd9" to the command line should do the trick. For the
346 time being, the old mtree is available as fmtree.
349 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
350 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
351 1.1.4_8 and verify bsdyml not linked in, before running "make
353 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
355 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
358 The rc.d/jail script has been updated to support jail(8)
359 configuration file. The "jail_<jname>_*" rc.conf(5) variables
360 for per-jail configuration are automatically converted to
361 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
362 This is transparently backward compatible. See below about some
363 incompatibilities and rc.conf(5) manual page for more details.
365 These variables are now deprecated in favor of jail(8) configuration
366 file. One can use "rc.d/jail config <jname>" command to generate
367 a jail(8) configuration file in /var/run/jail.<jname>.conf without
368 running the jail(8) utility. The default pathname of the
369 configuration file is /etc/jail.conf and can be specified by
370 using $jail_conf or $jail_<jname>_conf variables.
372 Please note that jail_devfs_ruleset accepts an integer at
373 this moment. Please consider to rewrite the ruleset name
377 BIND has been removed from the base system. If all you need
378 is a local resolver, simply enable and start the local_unbound
379 service instead. Otherwise, several versions of BIND are
380 available in the ports tree. The dns/bind99 port is one example.
382 With this change, nslookup(1) and dig(1) are no longer in the base
383 system. Users should instead use host(1) and drill(1) which are
384 in the base system. Alternatively, nslookup and dig can
385 be obtained by installing the dns/bind-tools port.
388 With the addition of unbound(8), a new unbound user is now
389 required during installworld. "mergemaster -p" can be used to
390 add the user prior to installworld, as documented in the handbook.
393 OpenSSH is now built with DNSSEC support, and will by default
394 silently trust signed SSHFP records. This can be controlled with
395 the VerifyHostKeyDNS client configuration setting. DNSSEC support
396 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
399 The GNU Compiler Collection and C++ standard library (libstdc++)
400 are no longer built by default on platforms where clang is the system
401 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
405 The PROCDESC kernel option is now part of the GENERIC kernel
406 configuration and is required for the rwhod(8) to work.
407 If you are using custom kernel configuration, you should include
411 The API and ABI related to the Capsicum framework was modified
412 in backward incompatible way. The userland libraries and programs
413 have to be recompiled to work with the new kernel. This includes the
414 following libraries and programs, but the whole buildworld is
415 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
416 kdump, procstat, rwho, rwhod, uniq.
419 AES-NI intrinsic support has been added to gcc. The AES-NI module
420 has been updated to use this support. A new gcc is required to build
421 the aesni module on both i386 and amd64.
424 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
425 Thus "device padlock_rng" and "device rdrand_rng" should be
426 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
429 WITH_ICONV has been split into two feature sets. WITH_ICONV now
430 enables just the iconv* functionality and is now on by default.
431 WITH_LIBICONV_COMPAT enables the libiconv api and link time
432 compatability. Set WITHOUT_ICONV to build the old way.
433 If you have been using WITH_ICONV before, you will very likely
434 need to turn on WITH_LIBICONV_COMPAT.
437 INVARIANTS option now enables DEBUG for code with OpenSolaris and
438 Illumos origin, including ZFS. If you have INVARIANTS in your
439 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
441 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
442 locks if WITNESS option was set. Because that generated a lot of
443 witness(9) reports and all of them were believed to be false
444 positives, this is no longer done. New option OPENSOLARIS_WITNESS
445 can be used to achieve the previous behavior.
448 Timer values in IPv6 data structures now use time_uptime instead
449 of time_second. Although this is not a user-visible functional
450 change, userland utilities which directly use them---ndp(8),
451 rtadvd(8), and rtsold(8) in the base system---need to be updated
455 find -delete can now delete the pathnames given as arguments,
456 instead of only files found below them or if the pathname did
457 not contain any slashes. Formerly, the following error message
460 find: -delete: <path>: relative path potentially not safe
462 Deleting the pathnames given as arguments can be prevented
463 without error messages using -mindepth 1 or by changing
464 directory and passing "." as argument to find. This works in the
465 old as well as the new version of find.
468 Behavior of devfs rules path matching has been changed.
469 Pattern is now always matched against fully qualified devfs
470 path and slash characters must be explicitly matched by
471 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
472 subdirectories must be reviewed.
475 The default ARM ABI has changed to the ARM EABI. The old ABI is
476 incompatible with the ARM EABI and all programs and modules will
477 need to be rebuilt to work with a new kernel.
479 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
481 NOTE: Support for the old ABI will be removed in the future and
482 users are advised to upgrade.
485 pkg_install has been disconnected from the build if you really need it
486 you should add WITH_PKGTOOLS in your src.conf(5).
489 Most of network statistics structures were changed to be able
490 keep 64-bits counters. Thus all tools, that work with networking
491 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
494 Fix targets that run multiple make's to use && rather than ;
495 so that subsequent steps depend on success of previous.
497 NOTE: if building 'universe' with -j* on stable/8 or stable/9
498 it would be better to start the build using bmake, to avoid
499 overloading the machine.
502 Fix a bug that allowed a tracing process (e.g. gdb) to write
503 to a memory-mapped file in the traced process's address space
504 even if neither the traced process nor the tracing process had
505 write access to that file.
508 CVS has been removed from the base system. An exact copy
509 of the code is available from the devel/cvs port.
512 Some people report the following error after the switch to bmake:
514 make: illegal option -- J
515 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
517 *** [buildworld] Error code 2
519 this likely due to an old instance of make in
520 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
521 which src/Makefile will use that blindly, if it exists, so if
522 you see the above error:
524 rm -rf `make -V MAKEPATH`
529 Use bmake by default.
530 Whereas before one could choose to build with bmake via
531 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
532 make. The goal is to remove these knobs for 10-RELEASE.
534 It is worth noting that bmake (like gmake) treats the command
535 line as the unit of failure, rather than statements within the
536 command line. Thus '(cd some/where && dosomething)' is safer
537 than 'cd some/where; dosomething'. The '()' allows consistent
538 behavior in parallel build.
541 Fix a bug that allows NFS clients to issue READDIR on files.
544 The WITHOUT_IDEA option has been removed because
545 the IDEA patent expired.
548 The sysctl which controls TRIM support under ZFS has been renamed
549 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
553 The mergemaster command now uses the default MAKEOBJDIRPREFIX
554 rather than creating it's own in the temporary directory in
555 order allow access to bootstrapped versions of tools such as
556 install and mtree. When upgrading from version of FreeBSD where
557 the install command does not support -l, you will need to
558 install a new mergemaster command if mergemaster -p is required.
559 This can be accomplished with the command (cd src/usr.sbin/mergemaster
563 Legacy ATA stack, disabled and replaced by new CAM-based one since
564 FreeBSD 9.0, completely removed from the sources. Kernel modules
565 atadisk and atapi*, user-level tools atacontrol and burncd are
566 removed. Kernel option `options ATA_CAM` is now permanently enabled
570 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
571 and socketpair(2). Software, in particular Kerberos, may
572 automatically detect and use these during building. The resulting
573 binaries will not work on older kernels.
576 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
577 information, see the respective 20130304 entry).
580 Recent commits to callout(9) changed the size of struct callout,
581 so the KBI is probably heavily disturbed. Also, some functions
582 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
583 by macros. Every kernel module using it won't load, so rebuild
586 The ctl device has been re-enabled in GENERIC for i386 and amd64,
587 but does not initialize by default (because of the new CTL_DISABLE
588 option) to save memory. To re-enable it, remove the CTL_DISABLE
589 option from the kernel config file or set kern.cam.ctl.disable=0
590 in /boot/loader.conf.
593 The ctl device has been disabled in GENERIC for i386 and amd64.
594 This was done due to the extra memory being allocated at system
595 initialisation time by the ctl driver which was only used if
596 a CAM target device was created. This makes a FreeBSD system
597 unusable on 128MB or less of RAM.
600 A new compression method (lz4) has been merged to -HEAD. Please
601 refer to zpool-features(7) for more information.
603 Please refer to the "ZFS notes" section of this file for information
604 on upgrading boot ZFS pools.
607 A BSD-licensed patch(1) variant has been added and is installed
608 as bsdpatch, being the GNU version the default patch.
609 To inverse the logic and use the BSD-licensed one as default,
610 while having the GNU version installed as gnupatch, rebuild
611 and install world with the WITH_BSD_PATCH knob set.
614 Due to the use of the new -l option to install(1) during build
615 and install, you must take care not to directly set the INSTALL
616 make variable in your /etc/make.conf, /etc/src.conf, or on the
617 command line. If you wish to use the -C flag for all installs
618 you may be able to add INSTALL+=-C to /etc/make.conf or
622 The install(1) option -M has changed meaning and now takes an
623 argument that is a file or path to append logs to. In the
624 unlikely event that -M was the last option on the command line
625 and the command line contained at least two files and a target
626 directory the first file will have logs appended to it. The -M
627 option served little practical purpose in the last decade so its
628 use is expected to be extremely rare.
631 After switching to Clang as the default compiler some users of ZFS
632 on i386 systems started to experience stack overflow kernel panics.
633 Please consider using 'options KSTACK_PAGES=4' in such configurations.
636 GEOM_LABEL now mangles label names read from file system metadata.
637 Mangling affect labels containing spaces, non-printable characters,
638 '%' or '"'. Device names in /etc/fstab and other places may need to
642 By default, only the 10 most recent kernel dumps will be saved. To
643 restore the previous behaviour (no limit on the number of kernel dumps
644 stored in the dump directory) add the following line to /etc/rc.conf:
649 With the addition of auditdistd(8), a new auditdistd user is now
650 required during installworld. "mergemaster -p" can be used to
651 add the user prior to installworld, as documented in the handbook.
654 The sin6_scope_id member variable in struct sockaddr_in6 is now
655 filled by the kernel before passing the structure to the userland via
656 sysctl or routing socket. This means the KAME-specific embedded scope
657 id in sin6_addr.s6_addr[2] is always cleared in userland application.
658 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
659 __FreeBSD_version is bumped to 1000025.
662 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
663 This means that the world and kernel will be compiled with clang
664 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
665 and /usr/bin/cpp. To disable this behavior and revert to building
666 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
667 of current may need to bootstrap WITHOUT_CLANG first if the clang
668 build fails (its compatibility window doesn't extend to the 9 stable
672 The IPFIREWALL_FORWARD kernel option has been removed. Its
673 functionality now turned on by default.
676 The ZERO_COPY_SOCKET kernel option has been removed and
677 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
678 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
679 mechanism which is not safe and may result in kernel crashes.
680 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
681 driver supports disposeable external page sized mbuf storage.
682 Proper replacements for both zero-copy mechanisms are under
683 consideration and will eventually lead to complete removal
684 of the two kernel options.
687 The IPv4 network stack has been converted to network byte
688 order. The following modules need to be recompiled together
689 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
690 pf(4), ipfw(4), ng_ipfw(4), stf(4).
693 Support for non-MPSAFE filesystems was removed from VFS. The
694 VFS_VERSION was bumped, all filesystem modules shall be
698 All the non-MPSAFE filesystems have been disconnected from
699 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
700 portalfs, smbfs, xfs.
703 The interface cloning API and ABI has changed. The following
704 modules need to be recompiled together with kernel:
705 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
706 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
707 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
710 The sdhci driver was split in two parts: sdhci (generic SD Host
711 Controller logic) and sdhci_pci (actual hardware driver).
712 No kernel config modifications are required, but if you
713 load sdhc as a module you must switch to sdhci_pci instead.
716 Import the FUSE kernel and userland support into base system.
719 The GNU sort(1) program has been removed since the BSD-licensed
720 sort(1) has been the default for quite some time and no serious
721 problems have been reported. The corresponding WITH_GNU_SORT
725 The pfil(9) API/ABI for AF_INET family has been changed. Packet
726 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
730 The net80211(4) ABI has been changed to allow for improved driver
731 PS-POLL and power-save support. All wireless drivers need to be
732 recompiled to work with the new kernel.
735 The random(4) support for the VIA hardware random number
736 generator (`PADLOCK') is no longer enabled unconditionally.
737 Add the padlock_rng device in the custom kernel config if
738 needed. The GENERIC kernels on i386 and amd64 do include the
739 device, so the change only affects the custom kernel
743 The pf(4) packet filter ABI has been changed. pfctl(8) and
744 snmp_pf module need to be recompiled to work with new kernel.
747 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
748 to -HEAD. Pools that have empty_bpobj in active state can not be
749 imported read-write with ZFS implementations that do not support
750 this feature. For more information read the zpool-features(5)
754 The sparc64 ZFS loader has been changed to no longer try to auto-
755 detect ZFS providers based on diskN aliases but now requires these
756 to be explicitly listed in the OFW boot-device environment variable.
759 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
760 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
761 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
764 The following sysctls and tunables have been renamed for consistency
765 with other variables:
766 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
767 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
770 The sort utility has been replaced with BSD sort. For now, GNU sort
771 is also available as "gnusort" or the default can be set back to
772 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
773 installed as "bsdsort".
776 A new version of ZFS (pool version 5000) has been merged to -HEAD.
777 Starting with this version the old system of ZFS pool versioning
778 is superseded by "feature flags". This concept enables forward
779 compatibility against certain future changes in functionality of ZFS
780 pools. The first read-only compatible "feature flag" for ZFS pools
781 is named "com.delphix:async_destroy". For more information
782 read the new zpool-features(5) manual page.
783 Please refer to the "ZFS notes" section of this file for information
784 on upgrading boot ZFS pools.
787 The malloc(3) implementation embedded in libc now uses sources imported
788 as contrib/jemalloc. The most disruptive API change is to
789 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
790 delete it prior to installworld, and optionally re-create it using the
791 new format after rebooting. See malloc.conf(5) for details
792 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
796 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
797 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
798 now spelled mips. This is to aid compatibility with third-party
799 software that expects this naming scheme in uname(3). Little-endian
800 settings are unchanged. If you are updating a big-endian mips64 machine
801 from before this change, you may need to set MACHINE_ARCH=mips64 in
802 your environment before the new build system will recognize your machine.
805 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
809 Now unix domain sockets behave "as expected" on nullfs(5). Previously
810 nullfs(5) did not pass through all behaviours to the underlying layer,
811 as a result if we bound to a socket on the lower layer we could connect
812 only to the lower path; if we bound to the upper layer we could connect
813 only to the upper path. The new behavior is one can connect to both the
814 lower and the upper paths regardless what layer path one binds to.
817 The getifaddrs upgrade path broken with 20111215 has been restored.
818 If you have upgraded in between 20111215 and 20120209 you need to
819 recompile libc again with your kernel. You still need to recompile
820 world to be able to configure CARP but this restriction already
824 The set_rcvar() function has been removed from /etc/rc.subr. All
825 base and ports rc.d scripts have been updated, so if you have a
826 port installed with a script in /usr/local/etc/rc.d you can either
827 hand-edit the rcvar= line, or reinstall the port.
829 An easy way to handle the mass-update of /etc/rc.d:
830 rm /etc/rc.d/* && mergemaster -i
833 panic(9) now stops other CPUs in the SMP systems, disables interrupts
834 on the current CPU and prevents other threads from running.
835 This behavior can be reverted using the kern.stop_scheduler_on_panic
837 The new behavior can be incompatible with kern.sync_on_panic.
840 The carp(4) facility has been changed significantly. Configuration
841 of the CARP protocol via ifconfig(8) has changed, as well as format
842 of CARP events submitted to devd(8) has changed. See manual pages
843 for more information. The arpbalance feature of carp(4) is currently
844 not supported anymore.
846 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
847 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
848 need to be recompiled.
851 The acpi_wmi(4) status device /dev/wmistat has been renamed to
855 The option VFS_ALLOW_NONMPSAFE option has been added in order to
856 explicitely support non-MPSAFE filesystems.
857 It is on by default for all supported platform at this present
861 The broken amd(4) driver has been replaced with esp(4) in the amd64,
862 i386 and pc98 GENERIC kernel configuration files.
865 sysinstall has been removed
868 The stable/9 branch created in subversion. This corresponds to the
869 RELENG_9 branch in CVS.
872 This commit modifies vfs_register() so that it uses a hash
873 calculation to set vfc_typenum, which is enabled by default.
874 The first time a system is booted after this change, the
875 vfc_typenum values will change for all file systems. The
876 main effect of this is a change to the NFS server file handles
877 for file systems that use vfc_typenum in their fsid, such as ZFS.
878 It will, however, prevent vfc_typenum from changing when file
879 systems are loaded in a different order for subsequent reboots.
880 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
881 until you are ready to remount all NFS clients after a reboot.
884 Bump the shared library version numbers for libraries that
885 do not use symbol versioning, have changed the ABI compared
886 to stable/8 and which shared library version was not bumped.
887 Done as part of 9.0-RELEASE cycle.
890 During the merge of Capsicum features, the fget(9) KPI was modified.
891 This may require the rebuilding of out-of-tree device drivers --
892 issues have been reported specifically with the nVidia device driver.
893 __FreeBSD_version is bumped to 900041.
895 Also, there is a period between 20110811 and 20110814 where the
896 special devices /dev/{stdin,stdout,stderr} did not work correctly.
897 Building world from a kernel during that window may not work.
900 The packet filter (pf) code has been updated to OpenBSD 4.5.
901 You need to update userland tools to be in sync with kernel.
902 This update breaks backward compatibility with earlier pfsync(4)
903 versions. Care must be taken when updating redundant firewall setups.
906 The following sysctls and tunables are retired on x86 platforms:
908 machdep.hlt_logical_cpus
909 The following sysctl is retired:
910 machdep.hyperthreading_allowed
911 The sysctls were supposed to provide a way to dynamically offline and
912 online selected CPUs on x86 platforms, but the implementation has not
913 been reliable especially with SCHED_ULE scheduler.
914 machdep.hyperthreading_allowed tunable is still available to ignore
915 hyperthreading CPUs at OS level.
916 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
917 where X is an APIC ID of a CPU. Be advised, though, that disabling
918 CPUs in non-uniform fashion will result in non-uniform topology and
919 may lead to sub-optimal system performance with SCHED_ULE, which is
923 cpumask_t type is retired and cpuset_t is used in order to describe
927 Changes to ifconfig(8) for dynamic address family detection mandate
928 that you are running a kernel of 20110525 or later. Make sure to
929 follow the update procedure to boot a new kernel before installing
933 Support for sun4v architecture is officially dropped
936 Several KPI breaking changes have been committed to the mii(4) layer,
937 the PHY drivers and consequently some Ethernet drivers using mii(4).
938 This means that miibus.ko and the modules of the affected Ethernet
939 drivers need to be recompiled.
941 Note to kernel developers: Given that the OUI bit reversion problem
942 was fixed as part of these changes all mii(4) commits related to OUIs,
943 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
944 handling, no longer can be merged verbatim to stable/8 and previous
948 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
949 into their kernel configurations along with 'device pci'.
952 The default NFS client is now the new NFS client, so fstype "newnfs"
953 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
954 Although mounts via fstype "nfs" will usually work without userland
955 changes, it is recommended that the mount(8) and mount_nfs(8)
956 commands be rebuilt from sources and that a link to mount_nfs called
957 mount_oldnfs be created. The new client is compiled into the
958 kernel with "options NFSCL" and this is needed for diskless root
959 file systems. The GENERIC kernel configs have been changed to use
960 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
961 To use the regular/old client, you can "mount -t oldnfs ...". For
962 a diskless root file system, you must also include a line like:
964 vfs.root.mountfrom="oldnfs:"
966 in the boot/loader.conf on the root fs on the NFS server to make
967 a diskless root fs use the old client.
970 The GENERIC kernels for all architectures now default to the new
971 CAM-based ATA stack. It means that all legacy ATA drivers were
972 removed and replaced by respective CAM drivers. If you are using
973 ATA device names in /etc/fstab or other places, make sure to update
974 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
975 where 'Y's are the sequential numbers starting from zero for each type
976 in order of detection, unless configured otherwise with tunables,
977 see cam(4)). There will be symbolic links created in /dev/ to map
978 old adX devices to the respective adaY. They should provide basic
979 compatibility for file systems mounting in most cases, but they do
980 not support old user-level APIs and do not have respective providers
981 in GEOM. Consider using updated management tools with new device names.
983 It is possible to load devices ahci, ata, siis and mvs as modules,
984 but option ATA_CAM should remain in kernel configuration to make ata
985 module work as CAM driver supporting legacy ATA controllers. Device ata
986 still can be used in modular fashion (atacore + ...). Modules atadisk
987 and atapi* are not used and won't affect operation in ATA_CAM mode.
988 Note that to use CAM-based ATA kernel should include CAM devices
989 scbus, pass, da (or explicitly ada), cd and optionally others. All of
990 them are parts of the cam module.
992 ataraid(4) functionality is now supported by the RAID GEOM class.
993 To use it you can load geom_raid kernel module and use graid(8) tool
994 for management. Instead of /dev/arX device names, use /dev/raid/rX.
996 No kernel config options or code have been removed, so if a problem
997 arises, please report it and optionally revert to the old ATA stack.
998 In order to do it you can remove from the kernel config:
1003 , and instead add back:
1004 device atadisk # ATA disk drives
1005 device ataraid # ATA RAID drives
1006 device atapicd # ATAPI CDROM drives
1007 device atapifd # ATAPI floppy drives
1008 device atapist # ATAPI tape drives
1011 The default NFS server has been changed to the new server, which
1012 was referred to as the experimental server. If you need to switch
1013 back to the old NFS server, you must now put the "-o" option on
1014 both the mountd and nfsd commands. This can be done using the
1015 mountd_flags and nfs_server_flags rc.conf variables until an
1016 update to the rc scripts is committed, which is coming soon.
1019 The GNU Objective-C runtime library (libobjc), and other Objective-C
1020 related components have been removed from the base system. If you
1021 require an Objective-C library, please use one of the available ports.
1024 ath(4) has been split into bus- and device- modules. if_ath contains
1025 the HAL, the TX rate control and the network device code. if_ath_pci
1026 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1027 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1028 in order to use ath on everything else.
1030 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1031 need to load if_ath and if_ath_pci for ath(4) operation.
1034 As part of the replacement of sysinstall, the process of building
1035 release media has changed significantly. For details, please re-read
1036 release(7), which has been updated to reflect the new build process.
1039 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1040 is the last available version under GPLv2. It brings a number of new
1041 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1042 4.1 and SSE 4.2), better support for powerpc64, a number of new
1043 directives, and lots of other small improvements. See the ChangeLog
1044 file in contrib/binutils for the full details.
1047 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1048 compliant, and will now use half of hash for authentication.
1049 This will break interoperability with all stacks (including all
1050 actual FreeBSD versions) who implement
1051 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1053 The only workaround with such peers is to use another HMAC
1054 algorithm for IPsec ("phase 2") authentication.
1057 Remove the uio_yield prototype and symbol. This function has
1058 been misnamed since it was introduced and should not be
1059 globally exposed with this name. The equivalent functionality
1060 is now available using kern_yield(curthread->td_user_pri).
1061 The function remains undocumented.
1064 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1065 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1066 for scalar sysctls is defined but disabled. Code that needs
1067 UQUAD to pass the type checking that must compile on older
1068 systems where the define is not present can check against
1069 __FreeBSD_version >= 900030.
1071 The system dialog(1) has been replaced with a new version previously
1072 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1073 with the previous version, but the libdialog associated with it has
1074 a largely incompatible API. As such, the original version of libdialog
1075 will be kept temporarily as libodialog, until its base system consumers
1076 are replaced or updated. Bump __FreeBSD_version to 900030.
1079 If you are trying to run make universe on a -stable system, and you get
1080 the following warning:
1081 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1082 unknown. config(8) likely too old."
1083 or something similar to it, then you must upgrade your -stable system
1084 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1085 stable/8) or build the config from the latest stable/8 branch and
1086 install it on your system.
1088 Prior to this date, building a current universe on 8-stable system from
1089 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1090 error in the first kernel build phase. A new config on those old
1091 systems will fix that problem for older versions of -current.
1094 The TCP stack has been modified to allow Khelp modules to interact with
1095 it via helper hook points and store per-connection data in the TCP
1096 control block. Bump __FreeBSD_version to 900029. User space tools that
1097 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1101 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1102 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1103 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1104 to take advantage of it instead of using custom implementations. This
1105 means that these drivers now no longer unconditionally advertise
1106 support for flow control but only do so if flow control is a selected
1107 media option. This was implemented in the generic support that way in
1108 order to allow flow control to be switched on and off via ifconfig(8)
1109 with the PHY specific default to typically off in order to protect
1110 from unwanted effects. Consequently, if you used flow control with
1111 one of the above mentioned drivers you now need to explicitly enable
1112 it, for example via:
1113 ifconfig bge0 media auto mediaopt flowcontrol
1115 Along with the above mentioned changes generic support for setting
1116 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1117 e1000phy(4) as well as ip1000phy(4) have been converted to take
1118 advantage of it. This means that these drivers now no longer take the
1119 link0 parameter for selecting master mode but the master media option
1120 has to be used instead, for example like in the following:
1121 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1123 Selection of master mode now is also available with all other PHY
1124 drivers supporting 1000baseT.
1127 The TCP stack has received a significant update to add support for
1128 modularised congestion control and generally improve the clarity of
1129 congestion control decisions. Bump __FreeBSD_version to 900025. User
1130 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1131 sockstat) need to be recompiled.
1134 The man(1) utility has been replaced by a new version that no longer
1135 uses /etc/manpath.config. Please consult man.conf(5) for how to
1136 migrate local entries to the new format.
1139 The copyright strings printed by login(1) and sshd(8) at the time of a
1140 new connection have been removed to follow other operating systems and
1144 A workaround for a fixed ld bug has been removed in kernel code,
1145 so make sure that your system ld is built from sources after
1146 revision 210245 from 2010-07-19 (r211583 if building head kernel
1147 on stable/8, r211584 for stable/7; both from 2010-08-21).
1148 A symptom of incorrect ld version is different addresses for
1149 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1152 The $ipv6_prefer variable in rc.conf(5) has been split into
1153 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1155 The $ip6addrctl_policy is a variable to choose a pre-defined
1156 address selection policy set by ip6addrctl(8). A value
1157 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1160 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1161 flag (see an entry of 20090926) is set on an interface with no
1162 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1163 security reason. If you want IPv6 link-local address on all
1164 interfaces by default, set this to "YES".
1166 The old ipv6_prefer="YES" is equivalent to
1167 ipv6_activate_all_interfaces="YES" and
1168 ip6addrctl_policy="ipv6_prefer".
1171 DTrace has grown support for userland tracing. Due to this, DTrace is
1172 now i386 and amd64 only.
1173 dtruss(1) is now installed by default on those systems and a new
1174 kernel module is needed for userland tracing: fasttrap.
1175 No changes to your kernel config file are necessary to enable
1176 userland tracing, but you might consider adding 'STRIP=' and
1177 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1178 to have informative userland stack traces in DTrace (ustack).
1181 The acpi_aiboost(4) driver has been removed in favor of the new
1182 aibs(4) driver. You should update your kernel configuration file.
1185 BSD grep has been imported to the base system and it is built by
1186 default. It is completely BSD licensed, highly GNU-compatible, uses
1187 less memory than its GNU counterpart and has a small codebase.
1188 However, it is slower than its GNU counterpart, which is mostly
1189 noticeable for larger searches, for smaller ones it is measurable
1190 but not significant. The reason is complex, the most important factor
1191 is that we lack a modern and efficient regex library and GNU
1192 overcomes this by optimizing the searches internally. Future work
1193 on improving the regex performance is planned, for the meantime,
1194 users that need better performance, can build GNU grep instead by
1195 setting the WITH_GNU_GREP knob.
1198 Due to the import of powerpc64 support, all existing powerpc kernel
1199 configuration files must be updated with a machine directive like this:
1200 machine powerpc powerpc
1202 In addition, an updated config(8) is required to build powerpc kernels
1206 A new version of ZFS (version 15) has been merged to -HEAD.
1207 This version uses a python library for the following subcommands:
1208 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1209 For full functionality of these commands the following port must
1210 be installed: sysutils/py-zfs
1213 'vm_page's are now hashed by physical address to an array of mutexes.
1214 Currently this is only used to serialize access to hold_count. Over
1215 time the page queue mutex will be peeled away. This changes the size
1216 of pmap on every architecture. And requires all callers of vm_page_hold
1217 and vm_page_unhold to be updated.
1220 WITH_CTF can now be specified in src.conf (not recommended, there
1221 are some problems with static executables), make.conf (would also
1222 affect ports which do not use GNU make and do not override the
1223 compile targets) or in the kernel config (via "makeoptions
1225 When WITH_CTF was specified there before this was silently ignored,
1226 so make sure that WITH_CTF is not used in places which could lead
1227 to unwanted behavior.
1230 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1231 to allow 32-bit compatibility on non-x86 platforms. All kernel
1232 configurations on amd64 and ia64 platforms using these options must
1233 be modified accordingly.
1236 The utmp user accounting database has been replaced with utmpx,
1237 the user accounting interface standardized by POSIX.
1238 Unfortunately the semantics of utmp and utmpx don't match,
1239 making it practically impossible to support both interfaces.
1240 The user accounting database is used by tools like finger(1),
1241 last(1), talk(1), w(1) and ac(8).
1243 All applications in the base system use utmpx. This means only
1244 local binaries (e.g. from the ports tree) may still use these
1245 utmp database files. These applications must be rebuilt to make
1248 After the system has been upgraded, it is safe to remove the old
1249 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1250 assuming their contents is of no importance anymore. Old wtmp
1251 databases can only be used by last(1) and ac(8) after they have
1252 been converted to the new format using wtmpcvt(1).
1255 Introduce the kernel thread "deadlock resolver" (which can be enabled
1256 via the DEADLKRES option, see NOTES for more details) and the
1257 sleepq_type() function for sleepqueues.
1260 The rc.firewall and rc.firewall6 were unified, and
1261 rc.firewall6 and rc.d/ip6fw were removed.
1262 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1263 variables are obsoleted. Instead, the following new rc
1264 variables are added to rc.d/ipfw:
1266 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1267 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1268 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1270 The meanings correspond to the relevant IPv4 variables.
1276 The default terminal emulation for syscons(4) has been changed
1277 from cons25 to xterm on all platforms except pc98. This means
1278 that the /etc/ttys file needs to be updated to ensure correct
1279 operation of applications on the console.
1281 The terminal emulation style can be toggled per window by using
1282 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1283 options can be used to change the compile-time default back to
1286 To prevent graphical artifacts, make sure the TERM environment
1287 variable is set to match the terminal emulation that is being
1288 performed by syscons(4).
1291 The layout of the structure ieee80211req_scan_result has changed.
1292 Applications that require wireless scan results (e.g. ifconfig(8))
1293 from net80211 need to be recompiled.
1295 Applications such as wpa_supplicant(8) may require a full world
1296 build without using NO_CLEAN in order to get synchronized with the
1300 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1301 There's one kernel module for each firmware. Adding "device iwnfw"
1302 to the kernel configuration file means including all three firmware
1303 images inside the kernel. If you want to include just the one for
1304 your wireless card, use the devices iwn4965fw, iwn5000fw or
1308 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1309 into rc.d/netif. The changes are the following:
1311 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1312 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1313 Note that both variables need the "inet6" keyword at the head.
1315 Do not set $ipv6_network_interfaces manually if you do not
1316 understand what you are doing. It is not needed in most cases.
1318 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1321 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1322 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1324 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1325 all configured interfaces have "inet6 accept_rtadv" in the
1326 $ifconfig_IF_ipv6. These are for backward compatibility.
1328 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1329 functionality of interfaces with no corresponding
1330 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1331 and the default address selection policy of ip6addrctl(8)
1332 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1333 Note that if you want to configure IPv6 functionality on the
1334 disabled interfaces after boot, first you need to clear the flag by
1335 using ifconfig(8) like:
1337 ifconfig em0 inet6 -ifdisabled
1339 If YES, the default address selection policy is set as
1342 The default value of $ipv6_prefer is NO.
1344 4. If your system need to receive Router Advertisement messages,
1345 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1346 scripts automatically invoke rtsol(8) when the interface becomes
1347 UP. The Router Advertisement messages are used for SLAAC
1348 (State-Less Address AutoConfiguration).
1351 802.11s D3.03 support was committed. This is incompatible with the
1352 previous code, which was based on D3.0.
1355 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1356 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1357 control whether accepting Router Advertisement messages or not.
1358 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1359 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1360 The ifconfig(8) utility now supports these flags.
1363 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1364 mount(8) and -a option for df(1) to see them.
1367 The old tunable hw.bus.devctl_disable has been superseded by
1368 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1369 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1373 Remove the option STOP_NMI. The default action is now to use NMI only
1374 for KDB via the newly introduced function stop_cpus_hard() and
1375 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1378 The stable/8 branch created in subversion. This corresponds to the
1379 RELENG_8 branch in CVS.
1382 Bump the shared library version numbers for all libraries that do not
1383 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1384 __FreeBSD_version to 800105.
1387 Due to changes in the implementation of virtual network stack support,
1388 all network-related kernel modules must be recompiled. As this change
1389 breaks the ABI, bump __FreeBSD_version to 800104.
1392 The TOE interface to the TCP syncache has been modified to remove
1393 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1394 The cxgb driver is the only TOE consumer affected by this change, and
1395 needs to be recompiled along with the kernel. As this change breaks
1396 the ABI, bump __FreeBSD_version to 800103.
1399 Padding has been added to struct tcpcb, sackhint and tcpstat in
1400 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1401 maintaining the ABI. However, this change breaks the ABI, so bump
1402 __FreeBSD_version to 800102. User space tools that rely on the size of
1403 any of these structs (e.g. sockstat) need to be recompiled.
1406 The NFS_LEGACYRPC option has been removed along with the old kernel
1407 RPC implementation that this option selected. Kernel configurations
1408 may need to be adjusted.
1411 The network interface device nodes at /dev/net/<interface> have been
1412 removed. All ioctl operations can be performed the normal way using
1413 routing sockets. The kqueue functionality can generally be replaced
1414 with routing sockets.
1417 The documentation from the FreeBSD Documentation Project (Handbook,
1418 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1419 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1422 The ABI of various structures related to the SYSV IPC API have been
1423 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1424 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1428 Layout of struct vnet has changed as routing related variables were
1429 moved to their own Vimage module. Modules need to be recompiled. Bump
1430 __FreeBSD_version to 800099.
1433 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1434 respectively. As long as no more than 16 groups per process are used,
1435 no changes should be visible. When more than 16 groups are used, old
1436 binaries may fail if they call getgroups() or getgrouplist() with
1437 statically sized storage. Recompiling will work around this, but
1438 applications should be modified to use dynamically allocated storage
1439 for group arrays as POSIX.1-2008 does not cap an implementation's
1440 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1442 NFS and portalfs mounts may also be affected as the list of groups is
1443 truncated to 16. Users of NFS who use more than 16 groups, should
1444 take care that negative group permissions are not used on the exported
1445 file systems as they will not be reliable unless a GSSAPI based
1446 authentication method is used.
1449 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1450 option compiles in the support for adaptive spinning for lockmgrs
1451 which want to enable it. The lockinit() function now accepts the flag
1452 LK_ADAPTIVE in order to make the lock object subject to adaptive
1453 spinning when both held in write and read mode.
1456 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1457 changed. User applications that use this ioctl need to be rebuilt.
1460 The layout of struct thread has changed. Kernel and modules need to
1464 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1465 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1468 window(1) has been removed from the base system. It can now be
1469 installed from ports. The port is called misc/window.
1472 The way we are storing and accessing `routing table' entries has
1473 changed. Programs reading the FIB, like netstat, need to be
1477 A new netisr implementation has been added for FreeBSD 8. Network
1478 file system modules, such as igmp, ipdivert, and others, should be
1480 Bump __FreeBSD_version to 800096.
1483 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1487 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1488 Bump __FreeBSD_version to 800094.
1491 Add mnt_xflag field to 'struct mount'. File system modules need to be
1493 Bump __FreeBSD_version to 800093.
1496 The compiling option ADAPTIVE_SX has been retired while it has been
1497 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1498 The KPI for sx_init_flags() changes as accepting flags:
1499 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1500 been introduced in order to handle the reversed logic.
1501 Bump __FreeBSD_version to 800092.
1504 Add support for hierarchical jails. Remove global securelevel.
1505 Bump __FreeBSD_version to 800091.
1508 The layout of struct vnet_net has changed, therefore modules
1510 Bump __FreeBSD_version to 800090.
1513 The newly imported zic(8) produces a new format in the output. Please
1514 run tzsetup(8) to install the newly created data to /etc/localtime.
1517 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1518 hw.usb.* and is now consistent again with previous releases.
1521 802.11 monitor mode support was revised and driver api's were changed.
1522 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1523 of DLT_IEEE802_11. No user-visible data structures were changed but
1524 applications that use DLT_IEEE802_11 may require changes.
1525 Bump __FreeBSD_version to 800088.
1528 The layout of the following structs has changed: sysctl_oid,
1529 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1530 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1531 panics may be experienced. World rebuild is required for
1532 correctly checking networking state from userland.
1533 Bump __FreeBSD_version to 800085.
1536 MLDv2 and Source-Specific Multicast (SSM) have been merged
1537 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1538 The implementation of SSM within FreeBSD's IPv6 stack closely
1539 follows the IPv4 implementation.
1541 For kernel developers:
1543 * The most important changes are that the ip6_output() and
1544 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1545 and this lock has been downgraded to a non-recursive mutex.
1547 * As with the changes to the IPv4 stack to support SSM, filtering
1548 of inbound multicast traffic must now be performed by transport
1549 protocols within the IPv6 stack. This does not apply to TCP and
1550 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1552 * The KPIs used by IPv6 multicast are similar to those used by
1553 the IPv4 stack, with the following differences:
1554 * im6o_mc_filter() is analogous to imo_multicast_filter().
1555 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1556 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1557 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1558 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1559 for MLDv1 have an additional 'timer' argument which is used to
1560 jitter the initial membership report for the solicited-node
1561 multicast membership on-link.
1562 * This is not strictly needed for MLDv2, which already jitters
1563 its report transmissions. However, the 'timer' argument is
1564 preserved in case MLDv1 is active on the interface.
1566 * The KAME linked-list based IPv6 membership implementation has
1567 been refactored to use a vector similar to that used by the IPv4
1569 Code which maintains a list of its own multicast memberships
1570 internally, e.g. carp, has been updated to reflect the new
1573 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1574 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1575 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1576 implementation constraint which needs to be addressed in HEAD.
1578 For application developers:
1580 * The changes are broadly similar to those made for the IPv4
1583 * The use of IPv4 and IPv6 multicast socket options on the same
1584 socket, using mapped addresses, HAS NOT been tested or supported.
1586 * There are a number of issues with the implementation of various
1587 IPv6 multicast APIs which need to be resolved in the API surface
1588 before the implementation is fully compatible with KAME userland
1589 use, and these are mostly to do with interface index treatment.
1591 * The literature available discusses the use of either the delta / ASM
1592 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1593 using setsourcefilter(3)/getsourcefilter(3). For more information
1594 please refer to RFC 3768, 'Socket Interface Extensions for
1595 Multicast Source Filters'.
1597 * Applications which use the published RFC 3678 APIs should be fine.
1599 For systems administrators:
1601 * The mtest(8) utility has been refactored to support IPv6, in
1602 addition to IPv4. Interface addresses are no longer accepted
1603 as arguments, their names must be used instead. The utility
1604 will map the interface name to its first IPv4 address as
1605 returned by getifaddrs(3).
1607 * The ifmcstat(8) utility has also been updated to print the MLDv2
1608 endpoint state and source filter lists via sysctl(3).
1610 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1611 loopback of IPv6 multicast datagrams by default; it defaults to 1
1612 to preserve the existing behaviour. Disabling multicast loopback is
1613 recommended for optimal system performance.
1615 * The IPv6 MROUTING code has been changed to examine this sysctl
1616 instead of attempting to perform a group lookup before looping
1617 back forwarded datagrams.
1619 Bump __FreeBSD_version to 800084.
1622 Implement low-level Bluetooth HCI API.
1623 Bump __FreeBSD_version to 800083.
1626 The layout of struct malloc_type, used by modules to register new
1627 memory allocation types, has changed. Most modules will need to
1628 be rebuilt or panics may be experienced.
1629 Bump __FreeBSD_version to 800081.
1632 Anticipate overflowing inp_flags - add inp_flags2.
1633 This changes most offsets in inpcb, so checking v4 connection
1634 state will require a world rebuild.
1635 Bump __FreeBSD_version to 800080.
1638 Add an llentry to struct route and struct route_in6. Modules
1639 embedding a struct route will need to be recompiled.
1640 Bump __FreeBSD_version to 800079.
1643 The size of rt_metrics_lite and by extension rtentry has changed.
1644 Networking administration apps will need to be recompiled.
1645 The route command now supports show as an alias for get, weighting
1646 of routes, sticky and nostick flags to alter the behavior of stateful
1648 Bump __FreeBSD_version to 800078.
1651 Do not use Giant for kbdmux(4) locking. This is wrong and
1652 apparently causing more problems than it solves. This will
1653 re-open the issue where interrupt handlers may race with
1654 kbdmux(4) in polling mode. Typical symptoms include (but
1655 not limited to) duplicated and/or missing characters when
1656 low level console functions (such as gets) are used while
1657 interrupts are enabled (for example geli password prompt,
1658 mountroot prompt etc.). Disabling kbdmux(4) may help.
1661 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1662 kernel modules referencing any of the above need to be recompiled.
1663 Bump __FreeBSD_version to 800075.
1666 GEOM_PART has become the default partition slicer for storage devices,
1667 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1668 introduces some changes:
1670 MSDOS/EBR: the devices created from MSDOS extended partition entries
1671 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1672 to devices with offset-based names. fstabs may need to be modified.
1674 BSD: the "geometry does not match label" warning is harmless in most
1675 cases but it points to problems in file system misalignment with
1676 disk geometry. The "c" partition is now implicit, covers the whole
1677 top-level drive and cannot be (mis)used by users.
1679 General: Kernel dumps are now not allowed to be written to devices
1680 whose partition types indicate they are meant to be used for file
1681 systems (or, in case of MSDOS partitions, as something else than
1684 Most of these changes date approximately from 200812.
1687 The uscanner(4) driver has been removed from the kernel. This follows
1688 Linux removing theirs in 2.6 and making libusb the default interface
1689 (supported by sane).
1692 The multicast forwarding code has been cleaned up. netstat(1)
1693 only relies on KVM now for printing bandwidth upcall meters.
1694 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1695 ip6_mroute_mod respectively. The config(5) options for statically
1696 compiling this code remain the same, i.e. 'options MROUTING'.
1699 Support for the IFF_NEEDSGIANT network interface flag has been
1700 removed, which means that non-MPSAFE network device drivers are no
1701 longer supported. In particular, if_ar, if_sr, and network device
1702 drivers from the old (legacy) USB stack can no longer be built or
1706 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1707 a bunch of new language catalog files have also been added.
1708 This means that some common libc messages are now localized and
1709 they depend on the LC_MESSAGES environmental variable.
1712 The k8temp(4) driver has been renamed to amdtemp(4) since
1713 support for Family 10 and Family 11 CPU families was added.
1716 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1717 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1719 For kernel developers, the most important changes are that the
1720 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1721 and this lock has been downgraded to a non-recursive mutex.
1723 Transport protocols (UDP, Raw IP) are now responsible for filtering
1724 inbound multicast traffic according to group membership and source
1725 filters. The imo_multicast_filter() KPI exists for this purpose.
1726 Transports which do not use multicast (SCTP, TCP) already reject
1727 multicast by default. Forwarding and receive performance may improve
1728 as a mutex acquisition is no longer needed in the ip_input()
1729 low-level input path. in_addmulti() and in_delmulti() are shimmed
1730 to new KPIs which exist to support SSM in-kernel.
1732 For application developers, it is recommended that loopback of
1733 multicast datagrams be disabled for best performance, as this
1734 will still cause the lock to be taken for each looped-back
1735 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1736 be tuned to 0 to disable loopback by default; it defaults to 1
1737 to preserve the existing behaviour.
1739 For systems administrators, to obtain best performance with
1740 multicast reception and multiple groups, it is always recommended
1741 that a card with a suitably precise hash filter is used. Hash
1742 collisions will still result in the lock being taken within the
1743 transport protocol input path to check group membership.
1745 If deploying FreeBSD in an environment with IGMP snooping switches,
1746 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1747 enabled; this forces 224.0.0.0/24 group membership to be announced
1750 The size of 'struct igmpstat' has changed; netstat needs to be
1751 recompiled to reflect this.
1752 Bump __FreeBSD_version to 800070.
1755 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1756 updated to use it. This requires a buildworld/installworld in order to
1757 update the library and dependencies (usbconfig, etc). Its advisable to
1758 rebuild all ports which uses libusb. More specific directions are given
1759 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1760 libusb are no longer required and can be removed.
1763 A workaround is committed to allow the creation of System V shared
1764 memory segment of size > 2 GB on the 64-bit architectures.
1765 Due to a limitation of the existing ABI, the shm_segsz member
1766 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1767 wrong for large segments. Note that limits must be explicitly
1768 raised to allow such segments to be created.
1771 The layout of struct ifnet has changed, requiring a rebuild of all
1772 network device driver modules.
1775 The /dev handling for the new USB stack has changed, a
1776 buildworld/installworld is required for libusb20.
1779 The new USB2 stack has now been permanently moved in and all kernel and
1780 module names reverted to their previous values (eg, usb, ehci, ohci,
1781 ums, ...). The old usb stack can be compiled in by prefixing the name
1782 with the letter 'o', the old usb modules have been removed.
1783 Updating entry 20090216 for xorg and 20090215 for libmap may still
1787 The rc.conf(5) option if_up_delay has been renamed to
1788 defaultroute_delay to better reflect its purpose. If you have
1789 customized this setting in /etc/rc.conf you need to update it to
1793 xorg 7.4 wants to configure its input devices via hald which does not
1794 yet work with USB2. If the keyboard/mouse does not work in xorg then
1796 Option "AllowEmptyInput" "off"
1797 to your ServerLayout section. This will cause X to use the configured
1798 kbd and mouse sections from your xorg.conf.
1801 The GENERIC kernels for all architectures now default to the new USB2
1802 stack. No kernel config options or code have been removed so if a
1803 problem arises please report it and optionally revert to the old USB
1804 stack. If you are loading USB kernel modules or have a custom kernel
1805 that includes GENERIC then ensure that usb names are also changed over,
1806 eg uftdi -> usb2_serial_ftdi.
1808 Older programs linked against the ports libusb 0.1 need to be
1809 redirected to the new stack's libusb20. /etc/libmap.conf can
1811 # Map old usb library to new one for usb2 stack
1812 libusb-0.1.so.8 libusb20.so.1
1815 All USB ethernet devices now attach as interfaces under the name ueN
1816 (eg. ue0). This is to provide a predictable name as vendors often
1817 change usb chipsets in a product without notice.
1820 The ichsmb(4) driver has been changed to require SMBus slave
1821 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1822 All of the other SMBus controller drivers require left-justified
1823 slave addresses, so this change makes all the drivers provide the
1827 INET6 statistics (struct ip6stat) was updated.
1828 netstat(1) needs to be recompiled.
1831 NTFS has been removed from GENERIC kernel on amd64 to match
1832 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1833 will load ntfs.ko module automatically when NTFS support is
1834 actually needed, unless ntfs.ko is not installed or security
1835 level prohibits loading kernel modules. If either is the case,
1836 "options NTFS" has to be added into kernel config.
1839 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1840 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1841 800061. User space tools that rely on the size of struct tcpcb in
1842 tcp_var.h (e.g. sockstat) need to be recompiled.
1845 ng_tty(4) module updated to match the new TTY subsystem.
1846 Due to API change, user-level applications must be updated.
1847 New API support added to mpd5 CVS and expected to be present
1848 in next mpd5.3 release.
1851 With __FreeBSD_version 800060 the makefs tool is part of
1852 the base system (it was a port).
1855 The afdata and ifnet locks have been changed from mutexes to
1856 rwlocks, network modules will need to be re-compiled.
1859 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1860 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1861 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1862 architecture and 40 bytes on 64-bit architecture. The userland
1863 applications "arp" and "ndp" have been updated accordingly.
1864 The output from "netstat -r" shows only routing entries and
1865 none of the L2 information.
1868 __FreeBSD_version 800057 marks the switchover from the
1869 binary ath hal to source code. Users must add the line:
1871 options AH_SUPPORT_AR5416
1873 to their kernel config files when specifying:
1877 The ath_hal module no longer exists; the code is now compiled
1878 together with the driver in the ath module. It is now
1879 possible to tailor chip support (i.e. reduce the set of chips
1880 and thereby the code size); consult ath_hal(4) for details.
1883 __FreeBSD_version 800054 adds memory barriers to
1884 <machine/atomic.h>, new interfaces to ifnet to facilitate
1885 multiple hardware transmit queues for cards that support
1886 them, and a lock-less ring-buffer implementation to
1887 enable drivers to more efficiently manage queueing of
1891 A new version of ZFS (version 13) has been merged to -HEAD.
1892 This version has zpool attribute "listsnapshots" off by
1893 default, which means "zfs list" does not show snapshots,
1894 and is the same as Solaris behavior.
1897 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1900 The uhci, ohci, ehci and slhci USB Host controller drivers have
1901 been put into separate modules. If you load the usb module
1902 separately through loader.conf you will need to load the
1903 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1904 controller add the following to loader.conf:
1910 The ABI used by the PMC toolset has changed. Please keep
1911 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1915 atapci kernel module now includes only generic PCI ATA
1916 driver. AHCI driver moved to ataahci kernel module.
1917 All vendor-specific code moved into separate kernel modules:
1918 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1919 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1920 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1921 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1924 The TTY subsystem of the kernel has been replaced by a new
1925 implementation, which provides better scalability and an
1926 improved driver model. Most common drivers have been migrated to
1927 the new TTY subsystem, while others have not. The following
1928 drivers have not yet been ported to the new TTY layer:
1931 cy, digi, rc, rp, sio
1937 ng_h4, ng_tty, ppp, sl, snp
1939 Adding these drivers to your kernel configuration file shall
1940 cause compilation to fail.
1943 ntpd has been upgraded to 4.2.4p5.
1946 OpenSSH has been upgraded to 5.1p1.
1948 For many years, FreeBSD's version of OpenSSH preferred DSA
1949 over RSA for host and user authentication keys. With this
1950 upgrade, we've switched to the vendor's default of RSA over
1951 DSA. This may cause upgraded clients to warn about unknown
1952 host keys even for previously known hosts. Users should
1953 follow the usual procedure for verifying host keys before
1954 accepting the RSA key.
1956 This can be circumvented by setting the "HostKeyAlgorithms"
1957 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1960 Please note that the sequence of keys offered for
1961 authentication has been changed as well. You may want to
1962 specify IdentityFile in a different order to revert this
1966 The sio(4) driver has been removed from the i386 and amd64
1967 kernel configuration files. This means uart(4) is now the
1968 default serial port driver on those platforms as well.
1970 To prevent collisions with the sio(4) driver, the uart(4) driver
1971 uses different names for its device nodes. This means the
1972 onboard serial port will now most likely be called "ttyu0"
1973 instead of "ttyd0". You may need to reconfigure applications to
1974 use the new device names.
1976 When using the serial port as a boot console, be sure to update
1977 /boot/device.hints and /etc/ttys before booting the new kernel.
1978 If you forget to do so, you can still manually specify the hints
1979 at the loader prompt:
1981 set hint.uart.0.at="isa"
1982 set hint.uart.0.port="0x3F8"
1983 set hint.uart.0.flags="0x10"
1984 set hint.uart.0.irq="4"
1988 The gpt(8) utility has been removed. Use gpart(8) to partition
1992 The version that Linuxulator emulates was changed from 2.4.2
1993 to 2.6.16. If you experience any problems with Linux binaries
1994 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1995 if it fixes the problem contact emulation mailing list.
1998 ISDN4BSD (I4B) was removed from the src tree. You may need to
1999 update a your kernel configuration and remove relevant entries.
2002 I have checked in code to support multiple routing tables.
2003 See the man pages setfib(1) and setfib(2).
2004 This is a hopefully backwards compatible version,
2005 but to make use of it you need to compile your kernel
2006 with options ROUTETABLES=2 (or more up to 16).
2009 The 802.11 wireless support was redone to enable multi-bss
2010 operation on devices that are capable. The underlying device
2011 is no longer used directly but instead wlanX devices are
2012 cloned with ifconfig. This requires changes to rc.conf files.
2013 For example, change:
2014 ifconfig_ath0="WPA DHCP"
2017 ifconfig_wlan0="WPA DHCP"
2018 see rc.conf(5) for more details. In addition, mergemaster of
2019 /etc/rc.d is highly recommended. Simultaneous update of userland
2020 and kernel wouldn't hurt either.
2022 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2023 modules were merged into the base wlan module. All references
2024 to these modules (e.g. in kernel config files) must be removed.
2027 psm(4) has gained write(2) support in native operation level.
2028 Arbitrary commands can be written to /dev/psm%d and status can
2029 be read back from it. Therefore, an application is responsible
2030 for status validation and error recovery. It is a no-op in
2031 other operation levels.
2034 Support for KSE threading has been removed from the kernel. To
2035 run legacy applications linked against KSE libmap.conf may
2036 be used. The following libmap.conf may be used to ensure
2037 compatibility with any prior release:
2039 libpthread.so.1 libthr.so.1
2040 libpthread.so.2 libthr.so.2
2041 libkse.so.3 libthr.so.3
2044 The layout of struct vmspace has changed. This affects libkvm
2045 and any executables that link against libkvm and use the
2046 kvm_getprocs() function. In particular, but not exclusively,
2047 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2048 The effects are minimal, but it's advisable to upgrade world
2052 The latest em driver no longer has support in it for the
2053 82575 adapter, this is now moved to the igb driver. The
2054 split was done to make new features that are incompatible
2055 with older hardware easier to do.
2058 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2059 likewise the kernel option is now GEOM_LINUX_LVM.
2062 The default NFS mount mode has changed from UDP to TCP for
2063 increased reliability. If you rely on (insecurely) NFS
2064 mounting across a firewall you may need to update your
2068 Belatedly note the addition of m_collapse for compacting
2072 The fts(3) structures have been changed to use adequate
2073 integer types for their members and so to be able to cope
2074 with huge file trees. The old fts(3) ABI is preserved
2075 through symbol versioning in libc, so third-party binaries
2076 using fts(3) should still work, although they will not take
2077 advantage of the extended types. At the same time, some
2078 third-party software might fail to build after this change
2079 due to unportable assumptions made in its source code about
2080 fts(3) structure members. Such software should be fixed
2081 by its vendor or, in the worst case, in the ports tree.
2082 FreeBSD_version 800015 marks this change for the unlikely
2083 case that a portable fix is impossible.
2086 To upgrade to -current after this date, you must be running
2087 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2088 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2091 The ADAPTIVE_GIANT kernel option has been retired because its
2092 functionality is the default now.
2095 The AT keyboard emulation of sunkbd(4) has been turned on
2096 by default. In order to make the special symbols of the Sun
2097 keyboards driven by sunkbd(4) work under X these now have
2098 to be configured the same way as Sun USB keyboards driven
2099 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2101 Option "XkbLayout" "us"
2102 Option "XkbRules" "xorg"
2103 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2106 It has been decided that it is desirable to provide ABI
2107 backwards compatibility to the FreeBSD 4/5/6 versions of the
2108 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2109 broken with the introduction of PCI domain support (see the
2110 20070930 entry). Unfortunately, this required the ABI of
2111 PCIOCGETCONF to be broken again in order to be able to
2112 provide backwards compatibility to the old version of that
2113 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2114 again. As for prominent ports this affects neither pciutils
2115 nor xorg-server this time, the hal port needs to be rebuilt
2119 The misnamed kthread_create() and friends have been renamed
2120 to kproc_create() etc. Many of the callers already
2121 used kproc_start()..
2122 I will return kthread_create() and friends in a while
2123 with implementations that actually create threads, not procs.
2124 Renaming corresponds with version 800002.
2133 Avoid using make -j when upgrading. While generally safe, there are
2134 sometimes problems using -j to upgrade. If your upgrade fails with
2135 -j, please try again without -j. From time to time in the past there
2136 have been problems using -j with buildworld and/or installworld. This
2137 is especially true when upgrading between "distant" versions (eg one
2138 that cross a major release boundary or several minor releases, or when
2139 several months have passed on the -current branch).
2141 Sometimes, obscure build problems are the result of environment
2142 poisoning. This can happen because the make utility reads its
2143 environment when searching for values for global variables. To run
2144 your build attempts in an "environmental clean room", prefix all make
2145 commands with 'env -i '. See the env(1) manual page for more details.
2147 When upgrading from one major version to another it is generally best
2148 to upgrade to the latest code in the currently installed branch first,
2149 then do an upgrade to the new branch. This is the best-tested upgrade
2150 path, and has the highest probability of being successful. Please try
2151 this approach before reporting problems with a major version upgrade.
2153 When upgrading a live system, having a root shell around before
2154 installing anything can help undo problems. Not having a root shell
2155 around can lead to problems if pam has changed too much from your
2156 starting point to allow continued authentication after the upgrade.
2160 When upgrading the boot ZFS pool to a new version, always follow
2163 1.) recompile and reinstall the ZFS boot loader and boot block
2164 (this is part of "make buildworld" and "make installworld")
2166 2.) update the ZFS boot block on your boot drive
2168 The following example updates the ZFS boot block on the first
2169 partition (freebsd-boot) of a GPT partitioned drive ad0:
2170 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2172 Non-boot pools do not need these updates.
2176 If you are updating from a prior version of FreeBSD (even one just
2177 a few days old), you should follow this procedure. It is the most
2178 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2180 make kernel-toolchain
2181 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2182 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2184 To test a kernel once
2185 ---------------------
2186 If you just want to boot a kernel once (because you are not sure
2187 if it works, or if you want to boot a known bad kernel to provide
2188 debugging information) run
2189 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2190 nextboot -k testkernel
2192 To just build a kernel when you know that it won't mess you up
2193 --------------------------------------------------------------
2194 This assumes you are already running a CURRENT system. Replace
2195 ${arch} with the architecture of your machine (e.g. "i386",
2196 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2198 cd src/sys/${arch}/conf
2199 config KERNEL_NAME_HERE
2200 cd ../compile/KERNEL_NAME_HERE
2205 If this fails, go to the "To build a kernel" section.
2207 To rebuild everything and install it on the current system.
2208 -----------------------------------------------------------
2209 # Note: sometimes if you are running current you gotta do more than
2210 # is listed here if you are upgrading from a really old current.
2212 <make sure you have good level 0 dumps>
2214 make kernel KERNCONF=YOUR_KERNEL_HERE
2216 <reboot in single user> [3]
2223 To cross-install current onto a separate partition
2224 --------------------------------------------------
2225 # In this approach we use a separate partition to hold
2226 # current's root, 'usr', and 'var' directories. A partition
2227 # holding "/", "/usr" and "/var" should be about 2GB in
2230 <make sure you have good level 0 dumps>
2233 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2234 <maybe newfs current's root partition>
2235 <mount current's root partition on directory ${CURRENT_ROOT}>
2236 make installworld DESTDIR=${CURRENT_ROOT}
2237 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2238 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2239 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2240 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2241 <reboot into current>
2242 <do a "native" rebuild/install as described in the previous section>
2243 <maybe install compatibility libraries from ports/misc/compat*>
2247 To upgrade in-place from stable to current
2248 ----------------------------------------------
2249 <make sure you have good level 0 dumps>
2251 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2253 <reboot in single user> [3]
2260 Make sure that you've read the UPDATING file to understand the
2261 tweaks to various things you need. At this point in the life
2262 cycle of current, things change often and you are on your own
2263 to cope. The defaults can also change, so please read ALL of
2264 the UPDATING entries.
2266 Also, if you are tracking -current, you must be subscribed to
2267 freebsd-current@freebsd.org. Make sure that before you update
2268 your sources that you have read and understood all the recent
2269 messages there. If in doubt, please track -stable which has
2270 much fewer pitfalls.
2272 [1] If you have third party modules, such as vmware, you
2273 should disable them at this point so they don't crash your
2276 [3] From the bootblocks, boot -s, and then do
2281 adjkerntz -i # if CMOS is wall time
2282 Also, when doing a major release upgrade, it is required that
2283 you boot into single user mode to do the installworld.
2285 [4] Note: This step is non-optional. Failure to do this step
2286 can result in a significant reduction in the functionality of the
2287 system. Attempting to do it by hand is not recommended and those
2288 that pursue this avenue should read this file carefully, as well
2289 as the archives of freebsd-current and freebsd-hackers mailing lists
2290 for potential gotchas. The -U option is also useful to consider.
2291 See mergemaster(8) for more information.
2293 [5] Usually this step is a noop. However, from time to time
2294 you may need to do this if you get unknown user in the following
2295 step. It never hurts to do it all the time. You may need to
2296 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2297 install) after the buildworld before this step if you last updated
2298 from current before 20130425 or from -stable before 20130430.
2300 [6] This only deletes old files and directories. Old libraries
2301 can be deleted by "make delete-old-libs", but you have to make
2302 sure that no program is using those libraries anymore.
2304 [8] In order to have a kernel that can run the 4.x binaries needed to
2305 do an installworld, you must include the COMPAT_FREEBSD4 option in
2306 your kernel. Failure to do so may leave you with a system that is
2307 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2308 required to run the 5.x binaries on more recent kernels. And so on
2309 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2311 Make sure that you merge any new devices from GENERIC since the
2312 last time you updated your kernel config file.
2314 [9] When checking out sources, you must include the -P flag to have
2315 cvs prune empty directories.
2317 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2318 "?=" instead of the "=" assignment operator, so that buildworld can
2319 override the CPUTYPE if it needs to.
2321 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2322 not on the command line, or in /etc/make.conf. buildworld will
2323 warn if it is improperly defined.
2326 This file contains a list, in reverse chronological order, of major
2327 breakages in tracking -current. It is not guaranteed to be a complete
2328 list of such breakages, and only contains entries since October 10, 2007.
2329 If you need to see UPDATING entries from before that date, you will need
2330 to fetch an UPDATING file from an older FreeBSD release.
2332 Copyright information:
2334 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2336 Redistribution, publication, translation and use, with or without
2337 modification, in full or in part, in any form or format of this
2338 document are permitted without further permission from the author.
2340 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2341 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2342 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2343 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2344 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2345 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2346 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2347 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2348 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2349 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2350 POSSIBILITY OF SUCH DAMAGE.
2352 Contact Warner Losh if you have any questions about your use of