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 20161102 p12 FreeBSD-SA-16:33.openssh
20 FreeBSD-SA-16:35.openssl
22 Fix OpenSSH remote Denial of Service vulnerability. [SA-16:33]
24 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
26 20161025 p11 FreeBSD-SA-16:15.sysarch [revised]
29 Fix incorrect argument validation in sysarch(2). [SA-16:15]
30 Fix virtual memory subsystem bugs. [EN-16:17]
32 20161010 p10 FreeBSD-SA-16:29.bspatch
33 FreeBSD-SA-16:30.portsnap
34 FreeBSD-SA-16:31.libarchive
36 Fix bspatch heap overflow vulnerability. [SA-16:29]
38 Fix multiple portsnap vulnerabilities. [SA-16:30]
40 Fix multiple libarchive vulnerabilities. [SA-16:31]
42 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
44 Fix OpenSSL regression introduced in SA-16:26.
46 20160923 p8 FreeBSD-SA-16:26.openssl
48 Fix multiple OpenSSL vulnerabilitites.
50 20160811 p7 FreeBSD-EN-16:10.dhclient
51 FreeBSD-EN-16:11.vmbus
52 FreeBSD-EN-16:12.hv_storvsc
53 FreeBSD-EN-16:13.vmbus
54 FreeBSD-EN-16:14.hv_storvsc
55 FreeBSD-EN-16:15.vmbus
56 FreeBSD-EN-16:16.hv_storvsc
58 Fix handling of unknown options from a DHCP server. [EN-16:10]
59 Fix a panic in hv_vmbus(4). [EN-16:11]
60 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
61 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
62 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
63 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
64 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
66 20160725 p6 FreeBSD-SA-16:25.bspatch
67 FreeBSD-EN-16:09.freebsd-update
69 Fix bspatch heap overflow vulnerability. [SA-16:25]
71 Fix freebsd-update(8) support of FreeBSD 11.0 release
72 distribution. [EN-16:09]
74 20160604 p5 FreeBSD-SA-16:24.ntp
76 Fix multiple vulnerabilities of ntp.
78 20160531 p4 FreeBSD-SA-16:20.linux
79 FreeBSD-SA-16:21.43bsd
80 FreeBSD-SA-16:22.libarchive
82 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
83 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
84 Fix directory traversal in cpio(1). [SA-16:22]
87 20160517 p3 FreeBSD-SA-16:18.atkbd
88 FreeBSD-SA-16:19.sendmsg
90 Fix buffer overflow in keyboard driver. [SA-16:18]
92 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
94 20160504 p2 FreeBSD-SA-16:17.openssl
99 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
101 Fix performance regression in libc hash(3). [EN-16:06]
103 Fix excessive latency in x86 IPI delivery. [EN-16:07]
105 Fix memory leak in ZFS. [EN-16:08]
107 20160429 p1 FreeBSD-SA-16:16.ntp
109 Fix multiple vulnerabilities of ntp.
115 The NONE and HPN patches has been removed from OpenSSH. They are
116 still available in the security/openssh-portable port.
119 r292223 changed the internal interface between the nfsd.ko and
120 nfscommon.ko modules. As such, they must both be upgraded to-gether.
121 __FreeBSD_version has been bumped because of this.
124 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
125 Kernel modules isp_2400_multi and isp_2500_multi were removed and
126 should be replaced with isp_2400 and isp_2500 modules respectively.
129 The menu.rc and loader.rc files will now be replaced during
130 upgrades. Please migrate local changes to menu.rc.local and
131 loader.rc.local instead.
134 NTP has been upgraded to 4.2.8p4.
137 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
138 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
139 and devel/kyua to version 0.20+ and adjust any calling code to work
140 with Kyuafile and kyua.
143 The polarity of Pulse Per Second (PPS) capture events with the
144 uart(4) driver has been corrected. Prior to this change the PPS
145 "assert" event corresponded to the trailing edge of a positive PPS
146 pulse and the "clear" event was the leading edge of the next pulse.
148 As the width of a PPS pulse in a typical GPS receiver is on the
149 order of 1 millisecond, most users will not notice any significant
150 difference with this change.
152 Anyone who has compensated for the historical polarity reversal by
153 configuring a negative offset equal to the pulse width will need to
154 remove that workaround.
157 From legacy ata(4) driver was removed support for SATA controllers
158 supported by more functional drivers ahci(4), siis(4) and mvs(4).
159 Kernel modules ataahci and ataadaptec were removed completely,
160 replaced by ahci and mvs modules respectively.
166 As ZFS requires more kernel stack pages than is the default on some
167 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
168 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
170 Please consider using 'options KSTACK_PAGES=X' where X is greater
171 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
174 The default Unbound configuration now enables remote control
175 using a local socket. Users who have already enabled the
176 local_unbound service should regenerate their configuration
177 by running "service local_unbound setup" as root.
180 An additional fix for the issue described in the 20150614 sendmail
181 entry below has been been committed in revision 284786.
184 The fix for the issue described in the 20150614 sendmail entry
185 below has been been committed in revision 284485. The work
186 around described in that entry is no longer needed unless the
187 default setting is overridden by a confDH_PARAMETERS configuration
188 setting of '5' or pointing to a 512 bit DH parameter file.
191 The import of openssl to address the FreeBSD-SA-15:10.openssl
192 security advisory includes a change which rejects handshakes
193 with DH parameters below 768 bits. sendmail releases prior
194 to 8.15.2 (not yet released), defaulted to a 512 bit
195 DH parameter setting for client connections. To work around
196 this interoperability, sendmail can be configured to use a
197 2048 bit DH parameter by:
199 1. Edit /etc/mail/`hostname`.mc
200 2. If a setting for confDH_PARAMETERS does not exist or
201 exists and is set to a string beginning with '5',
203 3. If a setting for confDH_PARAMETERS exists and is set to
204 a file path, create a new file with:
205 openssl dhparam -out /path/to/file 2048
206 4. Rebuild the .cf file:
207 cd /etc/mail/; make; make install
209 cd /etc/mail/; make restart
211 A sendmail patch is coming, at which time this file will be
215 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
216 defined in symlink(7); previously symlinks were silently ignored.
219 The const qualifier has been removed from iconv(3) to comply with
220 POSIX. The ports tree is aware of this from r384038 onwards.
223 At svn r275807, The default linux compat kernel ABI has been adjusted
224 to 2.6.18 in support of the linux-c6 compat ports infrastructure
225 update. If you wish to continue using the linux-f10 compat ports,
226 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
227 encouraged to update their linux-compat packages to linux-c6 during
228 their next update cycle.
230 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
233 pjdfstest has been integrated into kyua as an opt-in test suite.
234 Please see share/doc/pjdfstest/README for a more details on how to
241 The ofwfb driver, used to provide a graphics console on PowerPC when
242 using vt(4), no longer allows mmap() of all of physical memory. This
243 will prevent Xorg on PowerPC with some ATI graphics cards from
244 initializing properly unless x11-servers/xorg-server is updated to
248 The libatf-c and libatf-c++ major versions were downgraded to 0 and
249 1 respectively to match the upstream numbers. They were out of
250 sync because, when they were originally added to FreeBSD, the
251 upstream versions were not respected. These libraries are private
252 and not yet built by default, so renumbering them should be a
253 non-issue. However, unclean source trees will yield broken test
254 programs once the operator executes "make delete-old-libs" after a
257 Additionally, the atf-sh binary was made private by moving it into
258 /usr/libexec/. Already-built shell test programs will keep the
259 path to the old binary so they will break after "make delete-old"
262 If you are using WITH_TESTS=yes (not the default), wipe the object
263 tree and rebuild from scratch to prevent spurious test failures.
264 This is only needed once: the misnumbered libraries and misplaced
265 binaries have been added to OptionalObsoleteFiles.inc so they will
266 be removed during a clean upgrade.
269 The ixgbe tunables now match their sysctl counterparts, for example:
270 hw.ixgbe.enable_aim => hw.ix.enable_aim
271 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
274 The NFSv4.1 server committed by r269398 changes the internal
275 function call interfaces used between the NFS and krpc modules.
276 As such, __FreeBSD_version was bumped.
279 The default unbound configuration has been modified to address
280 issues with reverse lookups on networks that use private
281 address ranges. If you use the local_unbound service, run
282 "service local_unbound setup" as root to regenerate your
283 configuration, then "service local_unbound reload" to load the
287 It is no longer necessary to include the dwarf version in your DEBUG
288 options in your kernel config file. The bug that required it to be
289 placed in the config file has bene fixed. DEBUG should now just
290 contain -g. The build system will automatically update things
291 to do the right thing.
294 Several ABI breaking changes were merged to CTL and new iSCSI code.
295 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
296 iscsictl need to be rebuilt to work with a new kernel.
299 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
300 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
301 which differs from the behaviour controlled by this knob.)
304 On i386 and amd64 systems, the onifconsole flag is now set by default
305 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
306 as a login TTY if it is set in the bootloader as an active kernel
307 console. No changes in behavior should result otherwise. To revert to
308 the previous behavior, set ttyu0 to "off" in /etc/ttys.
311 Clang and llvm have been upgraded to 3.4.1 release.
314 Clang and llvm have been upgraded to 3.4 release.
317 If a Makefile in a tests/ directory was auto-generating a Kyuafile
318 instead of providing an explicit one, this would prevent such
319 Makefile from providing its own Kyuafile in the future during
320 NO_CLEAN builds. This has been fixed in the Makefiles but manual
321 intervention is needed to clean an objdir if you use NO_CLEAN:
322 # find /usr/obj -name Kyuafile | xargs rm -f
325 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
326 capability mode support. Please note that enabling the feature in
327 kernel is still highly recommended.
330 OpenSSH is now built with sandbox support, and will use sandbox as
331 the default privilege separation method. This requires Capsicum
332 capability mode support in kernel.
335 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
336 been deprecated and will not be part of FreeBSD 11.0 and later
337 releases. If you use this driver, please consider switching to
338 the nfe(4) driver instead.
344 The behavior of gss_pseudo_random() for the krb5 mechanism
345 has changed, for applications requesting a longer random string
346 than produced by the underlying enctype's pseudo-random() function.
347 In particular, the random string produced from a session key of
348 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
349 be different at the 17th octet and later, after this change.
350 The counter used in the PRF+ construction is now encoded as a
351 big-endian integer in accordance with RFC 4402.
352 __FreeBSD_version is bumped to 1000701.
355 The WITHOUT_ATF build knob has been removed and its functionality
356 has been subsumed into the more generic WITHOUT_TESTS. If you were
357 using the former to disable the build of the ATF libraries, you
358 should change your settings to use the latter.
361 The default version of mtree is nmtree which is obtained from
362 NetBSD. The output is generally the same, but may vary
363 slightly. If you found you need identical output adding
364 "-F freebsd9" to the command line should do the trick. For the
365 time being, the old mtree is available as fmtree.
368 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
369 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
370 1.1.4_8 and verify bsdyml not linked in, before running "make
372 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
374 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
377 The rc.d/jail script has been updated to support jail(8)
378 configuration file. The "jail_<jname>_*" rc.conf(5) variables
379 for per-jail configuration are automatically converted to
380 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
381 This is transparently backward compatible. See below about some
382 incompatibilities and rc.conf(5) manual page for more details.
384 These variables are now deprecated in favor of jail(8) configuration
385 file. One can use "rc.d/jail config <jname>" command to generate
386 a jail(8) configuration file in /var/run/jail.<jname>.conf without
387 running the jail(8) utility. The default pathname of the
388 configuration file is /etc/jail.conf and can be specified by
389 using $jail_conf or $jail_<jname>_conf variables.
391 Please note that jail_devfs_ruleset accepts an integer at
392 this moment. Please consider to rewrite the ruleset name
396 BIND has been removed from the base system. If all you need
397 is a local resolver, simply enable and start the local_unbound
398 service instead. Otherwise, several versions of BIND are
399 available in the ports tree. The dns/bind99 port is one example.
401 With this change, nslookup(1) and dig(1) are no longer in the base
402 system. Users should instead use host(1) and drill(1) which are
403 in the base system. Alternatively, nslookup and dig can
404 be obtained by installing the dns/bind-tools port.
407 With the addition of unbound(8), a new unbound user is now
408 required during installworld. "mergemaster -p" can be used to
409 add the user prior to installworld, as documented in the handbook.
412 OpenSSH is now built with DNSSEC support, and will by default
413 silently trust signed SSHFP records. This can be controlled with
414 the VerifyHostKeyDNS client configuration setting. DNSSEC support
415 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
418 The GNU Compiler Collection and C++ standard library (libstdc++)
419 are no longer built by default on platforms where clang is the system
420 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
424 The PROCDESC kernel option is now part of the GENERIC kernel
425 configuration and is required for the rwhod(8) to work.
426 If you are using custom kernel configuration, you should include
430 The API and ABI related to the Capsicum framework was modified
431 in backward incompatible way. The userland libraries and programs
432 have to be recompiled to work with the new kernel. This includes the
433 following libraries and programs, but the whole buildworld is
434 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
435 kdump, procstat, rwho, rwhod, uniq.
438 AES-NI intrinsic support has been added to gcc. The AES-NI module
439 has been updated to use this support. A new gcc is required to build
440 the aesni module on both i386 and amd64.
443 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
444 Thus "device padlock_rng" and "device rdrand_rng" should be
445 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
448 WITH_ICONV has been split into two feature sets. WITH_ICONV now
449 enables just the iconv* functionality and is now on by default.
450 WITH_LIBICONV_COMPAT enables the libiconv api and link time
451 compatability. Set WITHOUT_ICONV to build the old way.
452 If you have been using WITH_ICONV before, you will very likely
453 need to turn on WITH_LIBICONV_COMPAT.
456 INVARIANTS option now enables DEBUG for code with OpenSolaris and
457 Illumos origin, including ZFS. If you have INVARIANTS in your
458 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
460 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
461 locks if WITNESS option was set. Because that generated a lot of
462 witness(9) reports and all of them were believed to be false
463 positives, this is no longer done. New option OPENSOLARIS_WITNESS
464 can be used to achieve the previous behavior.
467 Timer values in IPv6 data structures now use time_uptime instead
468 of time_second. Although this is not a user-visible functional
469 change, userland utilities which directly use them---ndp(8),
470 rtadvd(8), and rtsold(8) in the base system---need to be updated
474 find -delete can now delete the pathnames given as arguments,
475 instead of only files found below them or if the pathname did
476 not contain any slashes. Formerly, the following error message
479 find: -delete: <path>: relative path potentially not safe
481 Deleting the pathnames given as arguments can be prevented
482 without error messages using -mindepth 1 or by changing
483 directory and passing "." as argument to find. This works in the
484 old as well as the new version of find.
487 Behavior of devfs rules path matching has been changed.
488 Pattern is now always matched against fully qualified devfs
489 path and slash characters must be explicitly matched by
490 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
491 subdirectories must be reviewed.
494 The default ARM ABI has changed to the ARM EABI. The old ABI is
495 incompatible with the ARM EABI and all programs and modules will
496 need to be rebuilt to work with a new kernel.
498 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
500 NOTE: Support for the old ABI will be removed in the future and
501 users are advised to upgrade.
504 pkg_install has been disconnected from the build if you really need it
505 you should add WITH_PKGTOOLS in your src.conf(5).
508 Most of network statistics structures were changed to be able
509 keep 64-bits counters. Thus all tools, that work with networking
510 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
513 Fix a bug that allowed a tracing process (e.g. gdb) to write
514 to a memory-mapped file in the traced process's address space
515 even if neither the traced process nor the tracing process had
516 write access to that file.
519 CVS has been removed from the base system. An exact copy
520 of the code is available from the devel/cvs port.
523 Some people report the following error after the switch to bmake:
525 make: illegal option -- J
526 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
528 *** [buildworld] Error code 2
530 this likely due to an old instance of make in
531 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
532 which src/Makefile will use that blindly, if it exists, so if
533 you see the above error:
535 rm -rf `make -V MAKEPATH`
540 Use bmake by default.
541 Whereas before one could choose to build with bmake via
542 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
543 make. The goal is to remove these knobs for 10-RELEASE.
545 It is worth noting that bmake (like gmake) treats the command
546 line as the unit of failure, rather than statements within the
547 command line. Thus '(cd some/where && dosomething)' is safer
548 than 'cd some/where; dosomething'. The '()' allows consistent
549 behavior in parallel build.
552 Fix a bug that allows NFS clients to issue READDIR on files.
555 The WITHOUT_IDEA option has been removed because
556 the IDEA patent expired.
559 The sysctl which controls TRIM support under ZFS has been renamed
560 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
564 The mergemaster command now uses the default MAKEOBJDIRPREFIX
565 rather than creating it's own in the temporary directory in
566 order allow access to bootstrapped versions of tools such as
567 install and mtree. When upgrading from version of FreeBSD where
568 the install command does not support -l, you will need to
569 install a new mergemaster command if mergemaster -p is required.
570 This can be accomplished with the command (cd src/usr.sbin/mergemaster
574 Legacy ATA stack, disabled and replaced by new CAM-based one since
575 FreeBSD 9.0, completely removed from the sources. Kernel modules
576 atadisk and atapi*, user-level tools atacontrol and burncd are
577 removed. Kernel option `options ATA_CAM` is now permanently enabled
581 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
582 and socketpair(2). Software, in particular Kerberos, may
583 automatically detect and use these during building. The resulting
584 binaries will not work on older kernels.
587 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
588 information, see the respective 20130304 entry).
591 Recent commits to callout(9) changed the size of struct callout,
592 so the KBI is probably heavily disturbed. Also, some functions
593 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
594 by macros. Every kernel module using it won't load, so rebuild
597 The ctl device has been re-enabled in GENERIC for i386 and amd64,
598 but does not initialize by default (because of the new CTL_DISABLE
599 option) to save memory. To re-enable it, remove the CTL_DISABLE
600 option from the kernel config file or set kern.cam.ctl.disable=0
601 in /boot/loader.conf.
604 The ctl device has been disabled in GENERIC for i386 and amd64.
605 This was done due to the extra memory being allocated at system
606 initialisation time by the ctl driver which was only used if
607 a CAM target device was created. This makes a FreeBSD system
608 unusable on 128MB or less of RAM.
611 A new compression method (lz4) has been merged to -HEAD. Please
612 refer to zpool-features(7) for more information.
614 Please refer to the "ZFS notes" section of this file for information
615 on upgrading boot ZFS pools.
618 A BSD-licensed patch(1) variant has been added and is installed
619 as bsdpatch, being the GNU version the default patch.
620 To inverse the logic and use the BSD-licensed one as default,
621 while having the GNU version installed as gnupatch, rebuild
622 and install world with the WITH_BSD_PATCH knob set.
625 Due to the use of the new -l option to install(1) during build
626 and install, you must take care not to directly set the INSTALL
627 make variable in your /etc/make.conf, /etc/src.conf, or on the
628 command line. If you wish to use the -C flag for all installs
629 you may be able to add INSTALL+=-C to /etc/make.conf or
633 The install(1) option -M has changed meaning and now takes an
634 argument that is a file or path to append logs to. In the
635 unlikely event that -M was the last option on the command line
636 and the command line contained at least two files and a target
637 directory the first file will have logs appended to it. The -M
638 option served little practical purpose in the last decade so its
639 use is expected to be extremely rare.
642 After switching to Clang as the default compiler some users of ZFS
643 on i386 systems started to experience stack overflow kernel panics.
644 Please consider using 'options KSTACK_PAGES=4' in such configurations.
647 GEOM_LABEL now mangles label names read from file system metadata.
648 Mangling affect labels containing spaces, non-printable characters,
649 '%' or '"'. Device names in /etc/fstab and other places may need to
653 By default, only the 10 most recent kernel dumps will be saved. To
654 restore the previous behaviour (no limit on the number of kernel dumps
655 stored in the dump directory) add the following line to /etc/rc.conf:
660 With the addition of auditdistd(8), a new auditdistd user is now
661 required during installworld. "mergemaster -p" can be used to
662 add the user prior to installworld, as documented in the handbook.
665 The sin6_scope_id member variable in struct sockaddr_in6 is now
666 filled by the kernel before passing the structure to the userland via
667 sysctl or routing socket. This means the KAME-specific embedded scope
668 id in sin6_addr.s6_addr[2] is always cleared in userland application.
669 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
670 __FreeBSD_version is bumped to 1000025.
673 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
674 This means that the world and kernel will be compiled with clang
675 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
676 and /usr/bin/cpp. To disable this behavior and revert to building
677 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
678 of current may need to bootstrap WITHOUT_CLANG first if the clang
679 build fails (its compatibility window doesn't extend to the 9 stable
683 The IPFIREWALL_FORWARD kernel option has been removed. Its
684 functionality now turned on by default.
687 The ZERO_COPY_SOCKET kernel option has been removed and
688 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
689 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
690 mechanism which is not safe and may result in kernel crashes.
691 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
692 driver supports disposeable external page sized mbuf storage.
693 Proper replacements for both zero-copy mechanisms are under
694 consideration and will eventually lead to complete removal
695 of the two kernel options.
698 The IPv4 network stack has been converted to network byte
699 order. The following modules need to be recompiled together
700 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
701 pf(4), ipfw(4), ng_ipfw(4), stf(4).
704 Support for non-MPSAFE filesystems was removed from VFS. The
705 VFS_VERSION was bumped, all filesystem modules shall be
709 All the non-MPSAFE filesystems have been disconnected from
710 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
711 portalfs, smbfs, xfs.
714 The interface cloning API and ABI has changed. The following
715 modules need to be recompiled together with kernel:
716 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
717 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
718 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
721 The sdhci driver was split in two parts: sdhci (generic SD Host
722 Controller logic) and sdhci_pci (actual hardware driver).
723 No kernel config modifications are required, but if you
724 load sdhc as a module you must switch to sdhci_pci instead.
727 Import the FUSE kernel and userland support into base system.
730 The GNU sort(1) program has been removed since the BSD-licensed
731 sort(1) has been the default for quite some time and no serious
732 problems have been reported. The corresponding WITH_GNU_SORT
736 The pfil(9) API/ABI for AF_INET family has been changed. Packet
737 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
741 The net80211(4) ABI has been changed to allow for improved driver
742 PS-POLL and power-save support. All wireless drivers need to be
743 recompiled to work with the new kernel.
746 The random(4) support for the VIA hardware random number
747 generator (`PADLOCK') is no longer enabled unconditionally.
748 Add the padlock_rng device in the custom kernel config if
749 needed. The GENERIC kernels on i386 and amd64 do include the
750 device, so the change only affects the custom kernel
754 The pf(4) packet filter ABI has been changed. pfctl(8) and
755 snmp_pf module need to be recompiled to work with new kernel.
758 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
759 to -HEAD. Pools that have empty_bpobj in active state can not be
760 imported read-write with ZFS implementations that do not support
761 this feature. For more information read the zpool-features(5)
765 The sparc64 ZFS loader has been changed to no longer try to auto-
766 detect ZFS providers based on diskN aliases but now requires these
767 to be explicitly listed in the OFW boot-device environment variable.
770 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
771 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
772 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
775 The following sysctls and tunables have been renamed for consistency
776 with other variables:
777 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
778 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
781 The sort utility has been replaced with BSD sort. For now, GNU sort
782 is also available as "gnusort" or the default can be set back to
783 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
784 installed as "bsdsort".
787 A new version of ZFS (pool version 5000) has been merged to -HEAD.
788 Starting with this version the old system of ZFS pool versioning
789 is superseded by "feature flags". This concept enables forward
790 compatibility against certain future changes in functionality of ZFS
791 pools. The first read-only compatible "feature flag" for ZFS pools
792 is named "com.delphix:async_destroy". For more information
793 read the new zpool-features(5) manual page.
794 Please refer to the "ZFS notes" section of this file for information
795 on upgrading boot ZFS pools.
798 The malloc(3) implementation embedded in libc now uses sources imported
799 as contrib/jemalloc. The most disruptive API change is to
800 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
801 delete it prior to installworld, and optionally re-create it using the
802 new format after rebooting. See malloc.conf(5) for details
803 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
807 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
808 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
809 now spelled mips. This is to aid compatibility with third-party
810 software that expects this naming scheme in uname(3). Little-endian
811 settings are unchanged. If you are updating a big-endian mips64 machine
812 from before this change, you may need to set MACHINE_ARCH=mips64 in
813 your environment before the new build system will recognize your machine.
816 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
820 Now unix domain sockets behave "as expected" on nullfs(5). Previously
821 nullfs(5) did not pass through all behaviours to the underlying layer,
822 as a result if we bound to a socket on the lower layer we could connect
823 only to the lower path; if we bound to the upper layer we could connect
824 only to the upper path. The new behavior is one can connect to both the
825 lower and the upper paths regardless what layer path one binds to.
828 The getifaddrs upgrade path broken with 20111215 has been restored.
829 If you have upgraded in between 20111215 and 20120209 you need to
830 recompile libc again with your kernel. You still need to recompile
831 world to be able to configure CARP but this restriction already
835 The set_rcvar() function has been removed from /etc/rc.subr. All
836 base and ports rc.d scripts have been updated, so if you have a
837 port installed with a script in /usr/local/etc/rc.d you can either
838 hand-edit the rcvar= line, or reinstall the port.
840 An easy way to handle the mass-update of /etc/rc.d:
841 rm /etc/rc.d/* && mergemaster -i
844 panic(9) now stops other CPUs in the SMP systems, disables interrupts
845 on the current CPU and prevents other threads from running.
846 This behavior can be reverted using the kern.stop_scheduler_on_panic
848 The new behavior can be incompatible with kern.sync_on_panic.
851 The carp(4) facility has been changed significantly. Configuration
852 of the CARP protocol via ifconfig(8) has changed, as well as format
853 of CARP events submitted to devd(8) has changed. See manual pages
854 for more information. The arpbalance feature of carp(4) is currently
855 not supported anymore.
857 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
858 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
859 need to be recompiled.
862 The acpi_wmi(4) status device /dev/wmistat has been renamed to
866 The option VFS_ALLOW_NONMPSAFE option has been added in order to
867 explicitely support non-MPSAFE filesystems.
868 It is on by default for all supported platform at this present
872 The broken amd(4) driver has been replaced with esp(4) in the amd64,
873 i386 and pc98 GENERIC kernel configuration files.
876 sysinstall has been removed
879 The stable/9 branch created in subversion. This corresponds to the
880 RELENG_9 branch in CVS.
883 This commit modifies vfs_register() so that it uses a hash
884 calculation to set vfc_typenum, which is enabled by default.
885 The first time a system is booted after this change, the
886 vfc_typenum values will change for all file systems. The
887 main effect of this is a change to the NFS server file handles
888 for file systems that use vfc_typenum in their fsid, such as ZFS.
889 It will, however, prevent vfc_typenum from changing when file
890 systems are loaded in a different order for subsequent reboots.
891 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
892 until you are ready to remount all NFS clients after a reboot.
895 Bump the shared library version numbers for libraries that
896 do not use symbol versioning, have changed the ABI compared
897 to stable/8 and which shared library version was not bumped.
898 Done as part of 9.0-RELEASE cycle.
901 During the merge of Capsicum features, the fget(9) KPI was modified.
902 This may require the rebuilding of out-of-tree device drivers --
903 issues have been reported specifically with the nVidia device driver.
904 __FreeBSD_version is bumped to 900041.
906 Also, there is a period between 20110811 and 20110814 where the
907 special devices /dev/{stdin,stdout,stderr} did not work correctly.
908 Building world from a kernel during that window may not work.
911 The packet filter (pf) code has been updated to OpenBSD 4.5.
912 You need to update userland tools to be in sync with kernel.
913 This update breaks backward compatibility with earlier pfsync(4)
914 versions. Care must be taken when updating redundant firewall setups.
917 The following sysctls and tunables are retired on x86 platforms:
919 machdep.hlt_logical_cpus
920 The following sysctl is retired:
921 machdep.hyperthreading_allowed
922 The sysctls were supposed to provide a way to dynamically offline and
923 online selected CPUs on x86 platforms, but the implementation has not
924 been reliable especially with SCHED_ULE scheduler.
925 machdep.hyperthreading_allowed tunable is still available to ignore
926 hyperthreading CPUs at OS level.
927 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
928 where X is an APIC ID of a CPU. Be advised, though, that disabling
929 CPUs in non-uniform fashion will result in non-uniform topology and
930 may lead to sub-optimal system performance with SCHED_ULE, which is
934 cpumask_t type is retired and cpuset_t is used in order to describe
938 Changes to ifconfig(8) for dynamic address family detection mandate
939 that you are running a kernel of 20110525 or later. Make sure to
940 follow the update procedure to boot a new kernel before installing
944 Support for sun4v architecture is officially dropped
947 Several KPI breaking changes have been committed to the mii(4) layer,
948 the PHY drivers and consequently some Ethernet drivers using mii(4).
949 This means that miibus.ko and the modules of the affected Ethernet
950 drivers need to be recompiled.
952 Note to kernel developers: Given that the OUI bit reversion problem
953 was fixed as part of these changes all mii(4) commits related to OUIs,
954 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
955 handling, no longer can be merged verbatim to stable/8 and previous
959 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
960 into their kernel configurations along with 'device pci'.
963 The default NFS client is now the new NFS client, so fstype "newnfs"
964 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
965 Although mounts via fstype "nfs" will usually work without userland
966 changes, it is recommended that the mount(8) and mount_nfs(8)
967 commands be rebuilt from sources and that a link to mount_nfs called
968 mount_oldnfs be created. The new client is compiled into the
969 kernel with "options NFSCL" and this is needed for diskless root
970 file systems. The GENERIC kernel configs have been changed to use
971 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
972 To use the regular/old client, you can "mount -t oldnfs ...". For
973 a diskless root file system, you must also include a line like:
975 vfs.root.mountfrom="oldnfs:"
977 in the boot/loader.conf on the root fs on the NFS server to make
978 a diskless root fs use the old client.
981 The GENERIC kernels for all architectures now default to the new
982 CAM-based ATA stack. It means that all legacy ATA drivers were
983 removed and replaced by respective CAM drivers. If you are using
984 ATA device names in /etc/fstab or other places, make sure to update
985 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
986 where 'Y's are the sequential numbers starting from zero for each type
987 in order of detection, unless configured otherwise with tunables,
988 see cam(4)). There will be symbolic links created in /dev/ to map
989 old adX devices to the respective adaY. They should provide basic
990 compatibility for file systems mounting in most cases, but they do
991 not support old user-level APIs and do not have respective providers
992 in GEOM. Consider using updated management tools with new device names.
994 It is possible to load devices ahci, ata, siis and mvs as modules,
995 but option ATA_CAM should remain in kernel configuration to make ata
996 module work as CAM driver supporting legacy ATA controllers. Device ata
997 still can be used in modular fashion (atacore + ...). Modules atadisk
998 and atapi* are not used and won't affect operation in ATA_CAM mode.
999 Note that to use CAM-based ATA kernel should include CAM devices
1000 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1001 them are parts of the cam module.
1003 ataraid(4) functionality is now supported by the RAID GEOM class.
1004 To use it you can load geom_raid kernel module and use graid(8) tool
1005 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1007 No kernel config options or code have been removed, so if a problem
1008 arises, please report it and optionally revert to the old ATA stack.
1009 In order to do it you can remove from the kernel config:
1014 , and instead add back:
1015 device atadisk # ATA disk drives
1016 device ataraid # ATA RAID drives
1017 device atapicd # ATAPI CDROM drives
1018 device atapifd # ATAPI floppy drives
1019 device atapist # ATAPI tape drives
1022 The default NFS server has been changed to the new server, which
1023 was referred to as the experimental server. If you need to switch
1024 back to the old NFS server, you must now put the "-o" option on
1025 both the mountd and nfsd commands. This can be done using the
1026 mountd_flags and nfs_server_flags rc.conf variables until an
1027 update to the rc scripts is committed, which is coming soon.
1030 The GNU Objective-C runtime library (libobjc), and other Objective-C
1031 related components have been removed from the base system. If you
1032 require an Objective-C library, please use one of the available ports.
1035 ath(4) has been split into bus- and device- modules. if_ath contains
1036 the HAL, the TX rate control and the network device code. if_ath_pci
1037 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1038 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1039 in order to use ath on everything else.
1041 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1042 need to load if_ath and if_ath_pci for ath(4) operation.
1045 As part of the replacement of sysinstall, the process of building
1046 release media has changed significantly. For details, please re-read
1047 release(7), which has been updated to reflect the new build process.
1050 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1051 is the last available version under GPLv2. It brings a number of new
1052 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1053 4.1 and SSE 4.2), better support for powerpc64, a number of new
1054 directives, and lots of other small improvements. See the ChangeLog
1055 file in contrib/binutils for the full details.
1058 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1059 compliant, and will now use half of hash for authentication.
1060 This will break interoperability with all stacks (including all
1061 actual FreeBSD versions) who implement
1062 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1064 The only workaround with such peers is to use another HMAC
1065 algorithm for IPsec ("phase 2") authentication.
1068 Remove the uio_yield prototype and symbol. This function has
1069 been misnamed since it was introduced and should not be
1070 globally exposed with this name. The equivalent functionality
1071 is now available using kern_yield(curthread->td_user_pri).
1072 The function remains undocumented.
1075 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1076 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1077 for scalar sysctls is defined but disabled. Code that needs
1078 UQUAD to pass the type checking that must compile on older
1079 systems where the define is not present can check against
1080 __FreeBSD_version >= 900030.
1082 The system dialog(1) has been replaced with a new version previously
1083 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1084 with the previous version, but the libdialog associated with it has
1085 a largely incompatible API. As such, the original version of libdialog
1086 will be kept temporarily as libodialog, until its base system consumers
1087 are replaced or updated. Bump __FreeBSD_version to 900030.
1090 If you are trying to run make universe on a -stable system, and you get
1091 the following warning:
1092 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1093 unknown. config(8) likely too old."
1094 or something similar to it, then you must upgrade your -stable system
1095 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1096 stable/8) or build the config from the latest stable/8 branch and
1097 install it on your system.
1099 Prior to this date, building a current universe on 8-stable system from
1100 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1101 error in the first kernel build phase. A new config on those old
1102 systems will fix that problem for older versions of -current.
1105 The TCP stack has been modified to allow Khelp modules to interact with
1106 it via helper hook points and store per-connection data in the TCP
1107 control block. Bump __FreeBSD_version to 900029. User space tools that
1108 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1112 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1113 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1114 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1115 to take advantage of it instead of using custom implementations. This
1116 means that these drivers now no longer unconditionally advertise
1117 support for flow control but only do so if flow control is a selected
1118 media option. This was implemented in the generic support that way in
1119 order to allow flow control to be switched on and off via ifconfig(8)
1120 with the PHY specific default to typically off in order to protect
1121 from unwanted effects. Consequently, if you used flow control with
1122 one of the above mentioned drivers you now need to explicitly enable
1123 it, for example via:
1124 ifconfig bge0 media auto mediaopt flowcontrol
1126 Along with the above mentioned changes generic support for setting
1127 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1128 e1000phy(4) as well as ip1000phy(4) have been converted to take
1129 advantage of it. This means that these drivers now no longer take the
1130 link0 parameter for selecting master mode but the master media option
1131 has to be used instead, for example like in the following:
1132 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1134 Selection of master mode now is also available with all other PHY
1135 drivers supporting 1000baseT.
1138 The TCP stack has received a significant update to add support for
1139 modularised congestion control and generally improve the clarity of
1140 congestion control decisions. Bump __FreeBSD_version to 900025. User
1141 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1142 sockstat) need to be recompiled.
1145 The man(1) utility has been replaced by a new version that no longer
1146 uses /etc/manpath.config. Please consult man.conf(5) for how to
1147 migrate local entries to the new format.
1150 The copyright strings printed by login(1) and sshd(8) at the time of a
1151 new connection have been removed to follow other operating systems and
1155 A workaround for a fixed ld bug has been removed in kernel code,
1156 so make sure that your system ld is built from sources after
1157 revision 210245 from 2010-07-19 (r211583 if building head kernel
1158 on stable/8, r211584 for stable/7; both from 2010-08-21).
1159 A symptom of incorrect ld version is different addresses for
1160 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1163 The $ipv6_prefer variable in rc.conf(5) has been split into
1164 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1166 The $ip6addrctl_policy is a variable to choose a pre-defined
1167 address selection policy set by ip6addrctl(8). A value
1168 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1171 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1172 flag (see an entry of 20090926) is set on an interface with no
1173 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1174 security reason. If you want IPv6 link-local address on all
1175 interfaces by default, set this to "YES".
1177 The old ipv6_prefer="YES" is equivalent to
1178 ipv6_activate_all_interfaces="YES" and
1179 ip6addrctl_policy="ipv6_prefer".
1182 DTrace has grown support for userland tracing. Due to this, DTrace is
1183 now i386 and amd64 only.
1184 dtruss(1) is now installed by default on those systems and a new
1185 kernel module is needed for userland tracing: fasttrap.
1186 No changes to your kernel config file are necessary to enable
1187 userland tracing, but you might consider adding 'STRIP=' and
1188 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1189 to have informative userland stack traces in DTrace (ustack).
1192 The acpi_aiboost(4) driver has been removed in favor of the new
1193 aibs(4) driver. You should update your kernel configuration file.
1196 BSD grep has been imported to the base system and it is built by
1197 default. It is completely BSD licensed, highly GNU-compatible, uses
1198 less memory than its GNU counterpart and has a small codebase.
1199 However, it is slower than its GNU counterpart, which is mostly
1200 noticeable for larger searches, for smaller ones it is measurable
1201 but not significant. The reason is complex, the most important factor
1202 is that we lack a modern and efficient regex library and GNU
1203 overcomes this by optimizing the searches internally. Future work
1204 on improving the regex performance is planned, for the meantime,
1205 users that need better performance, can build GNU grep instead by
1206 setting the WITH_GNU_GREP knob.
1209 Due to the import of powerpc64 support, all existing powerpc kernel
1210 configuration files must be updated with a machine directive like this:
1211 machine powerpc powerpc
1213 In addition, an updated config(8) is required to build powerpc kernels
1217 A new version of ZFS (version 15) has been merged to -HEAD.
1218 This version uses a python library for the following subcommands:
1219 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1220 For full functionality of these commands the following port must
1221 be installed: sysutils/py-zfs
1224 'vm_page's are now hashed by physical address to an array of mutexes.
1225 Currently this is only used to serialize access to hold_count. Over
1226 time the page queue mutex will be peeled away. This changes the size
1227 of pmap on every architecture. And requires all callers of vm_page_hold
1228 and vm_page_unhold to be updated.
1231 WITH_CTF can now be specified in src.conf (not recommended, there
1232 are some problems with static executables), make.conf (would also
1233 affect ports which do not use GNU make and do not override the
1234 compile targets) or in the kernel config (via "makeoptions
1236 When WITH_CTF was specified there before this was silently ignored,
1237 so make sure that WITH_CTF is not used in places which could lead
1238 to unwanted behavior.
1241 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1242 to allow 32-bit compatibility on non-x86 platforms. All kernel
1243 configurations on amd64 and ia64 platforms using these options must
1244 be modified accordingly.
1247 The utmp user accounting database has been replaced with utmpx,
1248 the user accounting interface standardized by POSIX.
1249 Unfortunately the semantics of utmp and utmpx don't match,
1250 making it practically impossible to support both interfaces.
1251 The user accounting database is used by tools like finger(1),
1252 last(1), talk(1), w(1) and ac(8).
1254 All applications in the base system use utmpx. This means only
1255 local binaries (e.g. from the ports tree) may still use these
1256 utmp database files. These applications must be rebuilt to make
1259 After the system has been upgraded, it is safe to remove the old
1260 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1261 assuming their contents is of no importance anymore. Old wtmp
1262 databases can only be used by last(1) and ac(8) after they have
1263 been converted to the new format using wtmpcvt(1).
1266 Introduce the kernel thread "deadlock resolver" (which can be enabled
1267 via the DEADLKRES option, see NOTES for more details) and the
1268 sleepq_type() function for sleepqueues.
1271 The rc.firewall and rc.firewall6 were unified, and
1272 rc.firewall6 and rc.d/ip6fw were removed.
1273 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1274 variables are obsoleted. Instead, the following new rc
1275 variables are added to rc.d/ipfw:
1277 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1278 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1279 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1281 The meanings correspond to the relevant IPv4 variables.
1287 The default terminal emulation for syscons(4) has been changed
1288 from cons25 to xterm on all platforms except pc98. This means
1289 that the /etc/ttys file needs to be updated to ensure correct
1290 operation of applications on the console.
1292 The terminal emulation style can be toggled per window by using
1293 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1294 options can be used to change the compile-time default back to
1297 To prevent graphical artifacts, make sure the TERM environment
1298 variable is set to match the terminal emulation that is being
1299 performed by syscons(4).
1302 The layout of the structure ieee80211req_scan_result has changed.
1303 Applications that require wireless scan results (e.g. ifconfig(8))
1304 from net80211 need to be recompiled.
1306 Applications such as wpa_supplicant(8) may require a full world
1307 build without using NO_CLEAN in order to get synchronized with the
1311 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1312 There's one kernel module for each firmware. Adding "device iwnfw"
1313 to the kernel configuration file means including all three firmware
1314 images inside the kernel. If you want to include just the one for
1315 your wireless card, use the devices iwn4965fw, iwn5000fw or
1319 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1320 into rc.d/netif. The changes are the following:
1322 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1323 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1324 Note that both variables need the "inet6" keyword at the head.
1326 Do not set $ipv6_network_interfaces manually if you do not
1327 understand what you are doing. It is not needed in most cases.
1329 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1332 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1333 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1335 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1336 all configured interfaces have "inet6 accept_rtadv" in the
1337 $ifconfig_IF_ipv6. These are for backward compatibility.
1339 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1340 functionality of interfaces with no corresponding
1341 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1342 and the default address selection policy of ip6addrctl(8)
1343 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1344 Note that if you want to configure IPv6 functionality on the
1345 disabled interfaces after boot, first you need to clear the flag by
1346 using ifconfig(8) like:
1348 ifconfig em0 inet6 -ifdisabled
1350 If YES, the default address selection policy is set as
1353 The default value of $ipv6_prefer is NO.
1355 4. If your system need to receive Router Advertisement messages,
1356 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1357 scripts automatically invoke rtsol(8) when the interface becomes
1358 UP. The Router Advertisement messages are used for SLAAC
1359 (State-Less Address AutoConfiguration).
1362 802.11s D3.03 support was committed. This is incompatible with the
1363 previous code, which was based on D3.0.
1366 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1367 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1368 control whether accepting Router Advertisement messages or not.
1369 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1370 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1371 The ifconfig(8) utility now supports these flags.
1374 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1375 mount(8) and -a option for df(1) to see them.
1378 The old tunable hw.bus.devctl_disable has been superseded by
1379 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1380 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1384 Remove the option STOP_NMI. The default action is now to use NMI only
1385 for KDB via the newly introduced function stop_cpus_hard() and
1386 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1389 The stable/8 branch created in subversion. This corresponds to the
1390 RELENG_8 branch in CVS.
1393 Bump the shared library version numbers for all libraries that do not
1394 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1395 __FreeBSD_version to 800105.
1398 Due to changes in the implementation of virtual network stack support,
1399 all network-related kernel modules must be recompiled. As this change
1400 breaks the ABI, bump __FreeBSD_version to 800104.
1403 The TOE interface to the TCP syncache has been modified to remove
1404 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1405 The cxgb driver is the only TOE consumer affected by this change, and
1406 needs to be recompiled along with the kernel. As this change breaks
1407 the ABI, bump __FreeBSD_version to 800103.
1410 Padding has been added to struct tcpcb, sackhint and tcpstat in
1411 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1412 maintaining the ABI. However, this change breaks the ABI, so bump
1413 __FreeBSD_version to 800102. User space tools that rely on the size of
1414 any of these structs (e.g. sockstat) need to be recompiled.
1417 The NFS_LEGACYRPC option has been removed along with the old kernel
1418 RPC implementation that this option selected. Kernel configurations
1419 may need to be adjusted.
1422 The network interface device nodes at /dev/net/<interface> have been
1423 removed. All ioctl operations can be performed the normal way using
1424 routing sockets. The kqueue functionality can generally be replaced
1425 with routing sockets.
1428 The documentation from the FreeBSD Documentation Project (Handbook,
1429 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1430 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1433 The ABI of various structures related to the SYSV IPC API have been
1434 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1435 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1439 Layout of struct vnet has changed as routing related variables were
1440 moved to their own Vimage module. Modules need to be recompiled. Bump
1441 __FreeBSD_version to 800099.
1444 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1445 respectively. As long as no more than 16 groups per process are used,
1446 no changes should be visible. When more than 16 groups are used, old
1447 binaries may fail if they call getgroups() or getgrouplist() with
1448 statically sized storage. Recompiling will work around this, but
1449 applications should be modified to use dynamically allocated storage
1450 for group arrays as POSIX.1-2008 does not cap an implementation's
1451 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1453 NFS and portalfs mounts may also be affected as the list of groups is
1454 truncated to 16. Users of NFS who use more than 16 groups, should
1455 take care that negative group permissions are not used on the exported
1456 file systems as they will not be reliable unless a GSSAPI based
1457 authentication method is used.
1460 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1461 option compiles in the support for adaptive spinning for lockmgrs
1462 which want to enable it. The lockinit() function now accepts the flag
1463 LK_ADAPTIVE in order to make the lock object subject to adaptive
1464 spinning when both held in write and read mode.
1467 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1468 changed. User applications that use this ioctl need to be rebuilt.
1471 The layout of struct thread has changed. Kernel and modules need to
1475 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1476 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1479 window(1) has been removed from the base system. It can now be
1480 installed from ports. The port is called misc/window.
1483 The way we are storing and accessing `routing table' entries has
1484 changed. Programs reading the FIB, like netstat, need to be
1488 A new netisr implementation has been added for FreeBSD 8. Network
1489 file system modules, such as igmp, ipdivert, and others, should be
1491 Bump __FreeBSD_version to 800096.
1494 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1498 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1499 Bump __FreeBSD_version to 800094.
1502 Add mnt_xflag field to 'struct mount'. File system modules need to be
1504 Bump __FreeBSD_version to 800093.
1507 The compiling option ADAPTIVE_SX has been retired while it has been
1508 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1509 The KPI for sx_init_flags() changes as accepting flags:
1510 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1511 been introduced in order to handle the reversed logic.
1512 Bump __FreeBSD_version to 800092.
1515 Add support for hierarchical jails. Remove global securelevel.
1516 Bump __FreeBSD_version to 800091.
1519 The layout of struct vnet_net has changed, therefore modules
1521 Bump __FreeBSD_version to 800090.
1524 The newly imported zic(8) produces a new format in the output. Please
1525 run tzsetup(8) to install the newly created data to /etc/localtime.
1528 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1529 hw.usb.* and is now consistent again with previous releases.
1532 802.11 monitor mode support was revised and driver api's were changed.
1533 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1534 of DLT_IEEE802_11. No user-visible data structures were changed but
1535 applications that use DLT_IEEE802_11 may require changes.
1536 Bump __FreeBSD_version to 800088.
1539 The layout of the following structs has changed: sysctl_oid,
1540 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1541 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1542 panics may be experienced. World rebuild is required for
1543 correctly checking networking state from userland.
1544 Bump __FreeBSD_version to 800085.
1547 MLDv2 and Source-Specific Multicast (SSM) have been merged
1548 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1549 The implementation of SSM within FreeBSD's IPv6 stack closely
1550 follows the IPv4 implementation.
1552 For kernel developers:
1554 * The most important changes are that the ip6_output() and
1555 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1556 and this lock has been downgraded to a non-recursive mutex.
1558 * As with the changes to the IPv4 stack to support SSM, filtering
1559 of inbound multicast traffic must now be performed by transport
1560 protocols within the IPv6 stack. This does not apply to TCP and
1561 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1563 * The KPIs used by IPv6 multicast are similar to those used by
1564 the IPv4 stack, with the following differences:
1565 * im6o_mc_filter() is analogous to imo_multicast_filter().
1566 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1567 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1568 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1569 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1570 for MLDv1 have an additional 'timer' argument which is used to
1571 jitter the initial membership report for the solicited-node
1572 multicast membership on-link.
1573 * This is not strictly needed for MLDv2, which already jitters
1574 its report transmissions. However, the 'timer' argument is
1575 preserved in case MLDv1 is active on the interface.
1577 * The KAME linked-list based IPv6 membership implementation has
1578 been refactored to use a vector similar to that used by the IPv4
1580 Code which maintains a list of its own multicast memberships
1581 internally, e.g. carp, has been updated to reflect the new
1584 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1585 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1586 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1587 implementation constraint which needs to be addressed in HEAD.
1589 For application developers:
1591 * The changes are broadly similar to those made for the IPv4
1594 * The use of IPv4 and IPv6 multicast socket options on the same
1595 socket, using mapped addresses, HAS NOT been tested or supported.
1597 * There are a number of issues with the implementation of various
1598 IPv6 multicast APIs which need to be resolved in the API surface
1599 before the implementation is fully compatible with KAME userland
1600 use, and these are mostly to do with interface index treatment.
1602 * The literature available discusses the use of either the delta / ASM
1603 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1604 using setsourcefilter(3)/getsourcefilter(3). For more information
1605 please refer to RFC 3768, 'Socket Interface Extensions for
1606 Multicast Source Filters'.
1608 * Applications which use the published RFC 3678 APIs should be fine.
1610 For systems administrators:
1612 * The mtest(8) utility has been refactored to support IPv6, in
1613 addition to IPv4. Interface addresses are no longer accepted
1614 as arguments, their names must be used instead. The utility
1615 will map the interface name to its first IPv4 address as
1616 returned by getifaddrs(3).
1618 * The ifmcstat(8) utility has also been updated to print the MLDv2
1619 endpoint state and source filter lists via sysctl(3).
1621 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1622 loopback of IPv6 multicast datagrams by default; it defaults to 1
1623 to preserve the existing behaviour. Disabling multicast loopback is
1624 recommended for optimal system performance.
1626 * The IPv6 MROUTING code has been changed to examine this sysctl
1627 instead of attempting to perform a group lookup before looping
1628 back forwarded datagrams.
1630 Bump __FreeBSD_version to 800084.
1633 Implement low-level Bluetooth HCI API.
1634 Bump __FreeBSD_version to 800083.
1637 The layout of struct malloc_type, used by modules to register new
1638 memory allocation types, has changed. Most modules will need to
1639 be rebuilt or panics may be experienced.
1640 Bump __FreeBSD_version to 800081.
1643 Anticipate overflowing inp_flags - add inp_flags2.
1644 This changes most offsets in inpcb, so checking v4 connection
1645 state will require a world rebuild.
1646 Bump __FreeBSD_version to 800080.
1649 Add an llentry to struct route and struct route_in6. Modules
1650 embedding a struct route will need to be recompiled.
1651 Bump __FreeBSD_version to 800079.
1654 The size of rt_metrics_lite and by extension rtentry has changed.
1655 Networking administration apps will need to be recompiled.
1656 The route command now supports show as an alias for get, weighting
1657 of routes, sticky and nostick flags to alter the behavior of stateful
1659 Bump __FreeBSD_version to 800078.
1662 Do not use Giant for kbdmux(4) locking. This is wrong and
1663 apparently causing more problems than it solves. This will
1664 re-open the issue where interrupt handlers may race with
1665 kbdmux(4) in polling mode. Typical symptoms include (but
1666 not limited to) duplicated and/or missing characters when
1667 low level console functions (such as gets) are used while
1668 interrupts are enabled (for example geli password prompt,
1669 mountroot prompt etc.). Disabling kbdmux(4) may help.
1672 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1673 kernel modules referencing any of the above need to be recompiled.
1674 Bump __FreeBSD_version to 800075.
1677 GEOM_PART has become the default partition slicer for storage devices,
1678 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1679 introduces some changes:
1681 MSDOS/EBR: the devices created from MSDOS extended partition entries
1682 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1683 to devices with offset-based names. fstabs may need to be modified.
1685 BSD: the "geometry does not match label" warning is harmless in most
1686 cases but it points to problems in file system misalignment with
1687 disk geometry. The "c" partition is now implicit, covers the whole
1688 top-level drive and cannot be (mis)used by users.
1690 General: Kernel dumps are now not allowed to be written to devices
1691 whose partition types indicate they are meant to be used for file
1692 systems (or, in case of MSDOS partitions, as something else than
1695 Most of these changes date approximately from 200812.
1698 The uscanner(4) driver has been removed from the kernel. This follows
1699 Linux removing theirs in 2.6 and making libusb the default interface
1700 (supported by sane).
1703 The multicast forwarding code has been cleaned up. netstat(1)
1704 only relies on KVM now for printing bandwidth upcall meters.
1705 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1706 ip6_mroute_mod respectively. The config(5) options for statically
1707 compiling this code remain the same, i.e. 'options MROUTING'.
1710 Support for the IFF_NEEDSGIANT network interface flag has been
1711 removed, which means that non-MPSAFE network device drivers are no
1712 longer supported. In particular, if_ar, if_sr, and network device
1713 drivers from the old (legacy) USB stack can no longer be built or
1717 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1718 a bunch of new language catalog files have also been added.
1719 This means that some common libc messages are now localized and
1720 they depend on the LC_MESSAGES environmental variable.
1723 The k8temp(4) driver has been renamed to amdtemp(4) since
1724 support for Family 10 and Family 11 CPU families was added.
1727 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1728 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1730 For kernel developers, the most important changes are that the
1731 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1732 and this lock has been downgraded to a non-recursive mutex.
1734 Transport protocols (UDP, Raw IP) are now responsible for filtering
1735 inbound multicast traffic according to group membership and source
1736 filters. The imo_multicast_filter() KPI exists for this purpose.
1737 Transports which do not use multicast (SCTP, TCP) already reject
1738 multicast by default. Forwarding and receive performance may improve
1739 as a mutex acquisition is no longer needed in the ip_input()
1740 low-level input path. in_addmulti() and in_delmulti() are shimmed
1741 to new KPIs which exist to support SSM in-kernel.
1743 For application developers, it is recommended that loopback of
1744 multicast datagrams be disabled for best performance, as this
1745 will still cause the lock to be taken for each looped-back
1746 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1747 be tuned to 0 to disable loopback by default; it defaults to 1
1748 to preserve the existing behaviour.
1750 For systems administrators, to obtain best performance with
1751 multicast reception and multiple groups, it is always recommended
1752 that a card with a suitably precise hash filter is used. Hash
1753 collisions will still result in the lock being taken within the
1754 transport protocol input path to check group membership.
1756 If deploying FreeBSD in an environment with IGMP snooping switches,
1757 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1758 enabled; this forces 224.0.0.0/24 group membership to be announced
1761 The size of 'struct igmpstat' has changed; netstat needs to be
1762 recompiled to reflect this.
1763 Bump __FreeBSD_version to 800070.
1766 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1767 updated to use it. This requires a buildworld/installworld in order to
1768 update the library and dependencies (usbconfig, etc). Its advisable to
1769 rebuild all ports which uses libusb. More specific directions are given
1770 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1771 libusb are no longer required and can be removed.
1774 A workaround is committed to allow the creation of System V shared
1775 memory segment of size > 2 GB on the 64-bit architectures.
1776 Due to a limitation of the existing ABI, the shm_segsz member
1777 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1778 wrong for large segments. Note that limits must be explicitly
1779 raised to allow such segments to be created.
1782 The layout of struct ifnet has changed, requiring a rebuild of all
1783 network device driver modules.
1786 The /dev handling for the new USB stack has changed, a
1787 buildworld/installworld is required for libusb20.
1790 The new USB2 stack has now been permanently moved in and all kernel and
1791 module names reverted to their previous values (eg, usb, ehci, ohci,
1792 ums, ...). The old usb stack can be compiled in by prefixing the name
1793 with the letter 'o', the old usb modules have been removed.
1794 Updating entry 20090216 for xorg and 20090215 for libmap may still
1798 The rc.conf(5) option if_up_delay has been renamed to
1799 defaultroute_delay to better reflect its purpose. If you have
1800 customized this setting in /etc/rc.conf you need to update it to
1804 xorg 7.4 wants to configure its input devices via hald which does not
1805 yet work with USB2. If the keyboard/mouse does not work in xorg then
1807 Option "AllowEmptyInput" "off"
1808 to your ServerLayout section. This will cause X to use the configured
1809 kbd and mouse sections from your xorg.conf.
1812 The GENERIC kernels for all architectures now default to the new USB2
1813 stack. No kernel config options or code have been removed so if a
1814 problem arises please report it and optionally revert to the old USB
1815 stack. If you are loading USB kernel modules or have a custom kernel
1816 that includes GENERIC then ensure that usb names are also changed over,
1817 eg uftdi -> usb2_serial_ftdi.
1819 Older programs linked against the ports libusb 0.1 need to be
1820 redirected to the new stack's libusb20. /etc/libmap.conf can
1822 # Map old usb library to new one for usb2 stack
1823 libusb-0.1.so.8 libusb20.so.1
1826 All USB ethernet devices now attach as interfaces under the name ueN
1827 (eg. ue0). This is to provide a predictable name as vendors often
1828 change usb chipsets in a product without notice.
1831 The ichsmb(4) driver has been changed to require SMBus slave
1832 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1833 All of the other SMBus controller drivers require left-justified
1834 slave addresses, so this change makes all the drivers provide the
1838 INET6 statistics (struct ip6stat) was updated.
1839 netstat(1) needs to be recompiled.
1842 NTFS has been removed from GENERIC kernel on amd64 to match
1843 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1844 will load ntfs.ko module automatically when NTFS support is
1845 actually needed, unless ntfs.ko is not installed or security
1846 level prohibits loading kernel modules. If either is the case,
1847 "options NTFS" has to be added into kernel config.
1850 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1851 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1852 800061. User space tools that rely on the size of struct tcpcb in
1853 tcp_var.h (e.g. sockstat) need to be recompiled.
1856 ng_tty(4) module updated to match the new TTY subsystem.
1857 Due to API change, user-level applications must be updated.
1858 New API support added to mpd5 CVS and expected to be present
1859 in next mpd5.3 release.
1862 With __FreeBSD_version 800060 the makefs tool is part of
1863 the base system (it was a port).
1866 The afdata and ifnet locks have been changed from mutexes to
1867 rwlocks, network modules will need to be re-compiled.
1870 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1871 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1872 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1873 architecture and 40 bytes on 64-bit architecture. The userland
1874 applications "arp" and "ndp" have been updated accordingly.
1875 The output from "netstat -r" shows only routing entries and
1876 none of the L2 information.
1879 __FreeBSD_version 800057 marks the switchover from the
1880 binary ath hal to source code. Users must add the line:
1882 options AH_SUPPORT_AR5416
1884 to their kernel config files when specifying:
1888 The ath_hal module no longer exists; the code is now compiled
1889 together with the driver in the ath module. It is now
1890 possible to tailor chip support (i.e. reduce the set of chips
1891 and thereby the code size); consult ath_hal(4) for details.
1894 __FreeBSD_version 800054 adds memory barriers to
1895 <machine/atomic.h>, new interfaces to ifnet to facilitate
1896 multiple hardware transmit queues for cards that support
1897 them, and a lock-less ring-buffer implementation to
1898 enable drivers to more efficiently manage queueing of
1902 A new version of ZFS (version 13) has been merged to -HEAD.
1903 This version has zpool attribute "listsnapshots" off by
1904 default, which means "zfs list" does not show snapshots,
1905 and is the same as Solaris behavior.
1908 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1911 The uhci, ohci, ehci and slhci USB Host controller drivers have
1912 been put into separate modules. If you load the usb module
1913 separately through loader.conf you will need to load the
1914 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1915 controller add the following to loader.conf:
1921 The ABI used by the PMC toolset has changed. Please keep
1922 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1926 atapci kernel module now includes only generic PCI ATA
1927 driver. AHCI driver moved to ataahci kernel module.
1928 All vendor-specific code moved into separate kernel modules:
1929 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1930 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1931 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1932 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1935 The TTY subsystem of the kernel has been replaced by a new
1936 implementation, which provides better scalability and an
1937 improved driver model. Most common drivers have been migrated to
1938 the new TTY subsystem, while others have not. The following
1939 drivers have not yet been ported to the new TTY layer:
1942 cy, digi, rc, rp, sio
1948 ng_h4, ng_tty, ppp, sl, snp
1950 Adding these drivers to your kernel configuration file shall
1951 cause compilation to fail.
1954 ntpd has been upgraded to 4.2.4p5.
1957 OpenSSH has been upgraded to 5.1p1.
1959 For many years, FreeBSD's version of OpenSSH preferred DSA
1960 over RSA for host and user authentication keys. With this
1961 upgrade, we've switched to the vendor's default of RSA over
1962 DSA. This may cause upgraded clients to warn about unknown
1963 host keys even for previously known hosts. Users should
1964 follow the usual procedure for verifying host keys before
1965 accepting the RSA key.
1967 This can be circumvented by setting the "HostKeyAlgorithms"
1968 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1971 Please note that the sequence of keys offered for
1972 authentication has been changed as well. You may want to
1973 specify IdentityFile in a different order to revert this
1977 The sio(4) driver has been removed from the i386 and amd64
1978 kernel configuration files. This means uart(4) is now the
1979 default serial port driver on those platforms as well.
1981 To prevent collisions with the sio(4) driver, the uart(4) driver
1982 uses different names for its device nodes. This means the
1983 onboard serial port will now most likely be called "ttyu0"
1984 instead of "ttyd0". You may need to reconfigure applications to
1985 use the new device names.
1987 When using the serial port as a boot console, be sure to update
1988 /boot/device.hints and /etc/ttys before booting the new kernel.
1989 If you forget to do so, you can still manually specify the hints
1990 at the loader prompt:
1992 set hint.uart.0.at="isa"
1993 set hint.uart.0.port="0x3F8"
1994 set hint.uart.0.flags="0x10"
1995 set hint.uart.0.irq="4"
1999 The gpt(8) utility has been removed. Use gpart(8) to partition
2003 The version that Linuxulator emulates was changed from 2.4.2
2004 to 2.6.16. If you experience any problems with Linux binaries
2005 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2006 if it fixes the problem contact emulation mailing list.
2009 ISDN4BSD (I4B) was removed from the src tree. You may need to
2010 update a your kernel configuration and remove relevant entries.
2013 I have checked in code to support multiple routing tables.
2014 See the man pages setfib(1) and setfib(2).
2015 This is a hopefully backwards compatible version,
2016 but to make use of it you need to compile your kernel
2017 with options ROUTETABLES=2 (or more up to 16).
2020 The 802.11 wireless support was redone to enable multi-bss
2021 operation on devices that are capable. The underlying device
2022 is no longer used directly but instead wlanX devices are
2023 cloned with ifconfig. This requires changes to rc.conf files.
2024 For example, change:
2025 ifconfig_ath0="WPA DHCP"
2028 ifconfig_wlan0="WPA DHCP"
2029 see rc.conf(5) for more details. In addition, mergemaster of
2030 /etc/rc.d is highly recommended. Simultaneous update of userland
2031 and kernel wouldn't hurt either.
2033 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2034 modules were merged into the base wlan module. All references
2035 to these modules (e.g. in kernel config files) must be removed.
2038 psm(4) has gained write(2) support in native operation level.
2039 Arbitrary commands can be written to /dev/psm%d and status can
2040 be read back from it. Therefore, an application is responsible
2041 for status validation and error recovery. It is a no-op in
2042 other operation levels.
2045 Support for KSE threading has been removed from the kernel. To
2046 run legacy applications linked against KSE libmap.conf may
2047 be used. The following libmap.conf may be used to ensure
2048 compatibility with any prior release:
2050 libpthread.so.1 libthr.so.1
2051 libpthread.so.2 libthr.so.2
2052 libkse.so.3 libthr.so.3
2055 The layout of struct vmspace has changed. This affects libkvm
2056 and any executables that link against libkvm and use the
2057 kvm_getprocs() function. In particular, but not exclusively,
2058 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2059 The effects are minimal, but it's advisable to upgrade world
2063 The latest em driver no longer has support in it for the
2064 82575 adapter, this is now moved to the igb driver. The
2065 split was done to make new features that are incompatible
2066 with older hardware easier to do.
2069 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2070 likewise the kernel option is now GEOM_LINUX_LVM.
2073 The default NFS mount mode has changed from UDP to TCP for
2074 increased reliability. If you rely on (insecurely) NFS
2075 mounting across a firewall you may need to update your
2079 Belatedly note the addition of m_collapse for compacting
2083 The fts(3) structures have been changed to use adequate
2084 integer types for their members and so to be able to cope
2085 with huge file trees. The old fts(3) ABI is preserved
2086 through symbol versioning in libc, so third-party binaries
2087 using fts(3) should still work, although they will not take
2088 advantage of the extended types. At the same time, some
2089 third-party software might fail to build after this change
2090 due to unportable assumptions made in its source code about
2091 fts(3) structure members. Such software should be fixed
2092 by its vendor or, in the worst case, in the ports tree.
2093 FreeBSD_version 800015 marks this change for the unlikely
2094 case that a portable fix is impossible.
2097 To upgrade to -current after this date, you must be running
2098 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2099 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2102 The ADAPTIVE_GIANT kernel option has been retired because its
2103 functionality is the default now.
2106 The AT keyboard emulation of sunkbd(4) has been turned on
2107 by default. In order to make the special symbols of the Sun
2108 keyboards driven by sunkbd(4) work under X these now have
2109 to be configured the same way as Sun USB keyboards driven
2110 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2112 Option "XkbLayout" "us"
2113 Option "XkbRules" "xorg"
2114 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2117 It has been decided that it is desirable to provide ABI
2118 backwards compatibility to the FreeBSD 4/5/6 versions of the
2119 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2120 broken with the introduction of PCI domain support (see the
2121 20070930 entry). Unfortunately, this required the ABI of
2122 PCIOCGETCONF to be broken again in order to be able to
2123 provide backwards compatibility to the old version of that
2124 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2125 again. As for prominent ports this affects neither pciutils
2126 nor xorg-server this time, the hal port needs to be rebuilt
2130 The misnamed kthread_create() and friends have been renamed
2131 to kproc_create() etc. Many of the callers already
2132 used kproc_start()..
2133 I will return kthread_create() and friends in a while
2134 with implementations that actually create threads, not procs.
2135 Renaming corresponds with version 800002.
2144 Avoid using make -j when upgrading. While generally safe, there are
2145 sometimes problems using -j to upgrade. If your upgrade fails with
2146 -j, please try again without -j. From time to time in the past there
2147 have been problems using -j with buildworld and/or installworld. This
2148 is especially true when upgrading between "distant" versions (eg one
2149 that cross a major release boundary or several minor releases, or when
2150 several months have passed on the -current branch).
2152 Sometimes, obscure build problems are the result of environment
2153 poisoning. This can happen because the make utility reads its
2154 environment when searching for values for global variables. To run
2155 your build attempts in an "environmental clean room", prefix all make
2156 commands with 'env -i '. See the env(1) manual page for more details.
2158 When upgrading from one major version to another it is generally best
2159 to upgrade to the latest code in the currently installed branch first,
2160 then do an upgrade to the new branch. This is the best-tested upgrade
2161 path, and has the highest probability of being successful. Please try
2162 this approach before reporting problems with a major version upgrade.
2164 When upgrading a live system, having a root shell around before
2165 installing anything can help undo problems. Not having a root shell
2166 around can lead to problems if pam has changed too much from your
2167 starting point to allow continued authentication after the upgrade.
2171 When upgrading the boot ZFS pool to a new version, always follow
2174 1.) recompile and reinstall the ZFS boot loader and boot block
2175 (this is part of "make buildworld" and "make installworld")
2177 2.) update the ZFS boot block on your boot drive
2179 The following example updates the ZFS boot block on the first
2180 partition (freebsd-boot) of a GPT partitioned drive ad0:
2181 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2183 Non-boot pools do not need these updates.
2187 If you are updating from a prior version of FreeBSD (even one just
2188 a few days old), you should follow this procedure. It is the most
2189 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2191 make kernel-toolchain
2192 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2193 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2195 To test a kernel once
2196 ---------------------
2197 If you just want to boot a kernel once (because you are not sure
2198 if it works, or if you want to boot a known bad kernel to provide
2199 debugging information) run
2200 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2201 nextboot -k testkernel
2203 To just build a kernel when you know that it won't mess you up
2204 --------------------------------------------------------------
2205 This assumes you are already running a CURRENT system. Replace
2206 ${arch} with the architecture of your machine (e.g. "i386",
2207 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2209 cd src/sys/${arch}/conf
2210 config KERNEL_NAME_HERE
2211 cd ../compile/KERNEL_NAME_HERE
2216 If this fails, go to the "To build a kernel" section.
2218 To rebuild everything and install it on the current system.
2219 -----------------------------------------------------------
2220 # Note: sometimes if you are running current you gotta do more than
2221 # is listed here if you are upgrading from a really old current.
2223 <make sure you have good level 0 dumps>
2225 make kernel KERNCONF=YOUR_KERNEL_HERE
2227 <reboot in single user> [3]
2234 To cross-install current onto a separate partition
2235 --------------------------------------------------
2236 # In this approach we use a separate partition to hold
2237 # current's root, 'usr', and 'var' directories. A partition
2238 # holding "/", "/usr" and "/var" should be about 2GB in
2241 <make sure you have good level 0 dumps>
2244 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2245 <maybe newfs current's root partition>
2246 <mount current's root partition on directory ${CURRENT_ROOT}>
2247 make installworld DESTDIR=${CURRENT_ROOT}
2248 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2249 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2250 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2251 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2252 <reboot into current>
2253 <do a "native" rebuild/install as described in the previous section>
2254 <maybe install compatibility libraries from ports/misc/compat*>
2258 To upgrade in-place from stable to current
2259 ----------------------------------------------
2260 <make sure you have good level 0 dumps>
2262 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2264 <reboot in single user> [3]
2271 Make sure that you've read the UPDATING file to understand the
2272 tweaks to various things you need. At this point in the life
2273 cycle of current, things change often and you are on your own
2274 to cope. The defaults can also change, so please read ALL of
2275 the UPDATING entries.
2277 Also, if you are tracking -current, you must be subscribed to
2278 freebsd-current@freebsd.org. Make sure that before you update
2279 your sources that you have read and understood all the recent
2280 messages there. If in doubt, please track -stable which has
2281 much fewer pitfalls.
2283 [1] If you have third party modules, such as vmware, you
2284 should disable them at this point so they don't crash your
2287 [3] From the bootblocks, boot -s, and then do
2292 adjkerntz -i # if CMOS is wall time
2293 Also, when doing a major release upgrade, it is required that
2294 you boot into single user mode to do the installworld.
2296 [4] Note: This step is non-optional. Failure to do this step
2297 can result in a significant reduction in the functionality of the
2298 system. Attempting to do it by hand is not recommended and those
2299 that pursue this avenue should read this file carefully, as well
2300 as the archives of freebsd-current and freebsd-hackers mailing lists
2301 for potential gotchas. The -U option is also useful to consider.
2302 See mergemaster(8) for more information.
2304 [5] Usually this step is a noop. However, from time to time
2305 you may need to do this if you get unknown user in the following
2306 step. It never hurts to do it all the time. You may need to
2307 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2308 install) after the buildworld before this step if you last updated
2309 from current before 20130425 or from -stable before 20130430.
2311 [6] This only deletes old files and directories. Old libraries
2312 can be deleted by "make delete-old-libs", but you have to make
2313 sure that no program is using those libraries anymore.
2315 [8] In order to have a kernel that can run the 4.x binaries needed to
2316 do an installworld, you must include the COMPAT_FREEBSD4 option in
2317 your kernel. Failure to do so may leave you with a system that is
2318 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2319 required to run the 5.x binaries on more recent kernels. And so on
2320 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2322 Make sure that you merge any new devices from GENERIC since the
2323 last time you updated your kernel config file.
2325 [9] When checking out sources, you must include the -P flag to have
2326 cvs prune empty directories.
2328 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2329 "?=" instead of the "=" assignment operator, so that buildworld can
2330 override the CPUTYPE if it needs to.
2332 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2333 not on the command line, or in /etc/make.conf. buildworld will
2334 warn if it is improperly defined.
2337 This file contains a list, in reverse chronological order, of major
2338 breakages in tracking -current. It is not guaranteed to be a complete
2339 list of such breakages, and only contains entries since October 10, 2007.
2340 If you need to see UPDATING entries from before that date, you will need
2341 to fetch an UPDATING file from an older FreeBSD release.
2343 Copyright information:
2345 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2347 Redistribution, publication, translation and use, with or without
2348 modification, in full or in part, in any form or format of this
2349 document are permitted without further permission from the author.
2351 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2352 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2353 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2354 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2355 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2356 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2357 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2358 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2359 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2360 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2361 POSSIBILITY OF SUCH DAMAGE.
2363 Contact Warner Losh if you have any questions about your use of