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 20161222 p15 FreeBSD-SA-16:39.ntp
21 Fix multiple vulnerabilities of ntp.
23 20161208 p14 FreeBSD-SA-16:37.libc [revised]
25 Fix regressions introduced by SA-16:37.libc.
27 20161206 p13 FreeBSD-SA-16:36.telnetd
29 FreeBSD-SA-16:38.bhyve
30 FreeBSD-EN-16:19.tzcode
31 FreeBSD-EN-16:20.tzdata
33 Fix possible login(1) argument injection in telnetd(8). [SA-16:36]
34 Fix link_ntoa(3) buffer overflow in libc. [SA-16:37]
35 Fix possible escape from bhyve(8) virtual machine. [SA-16:38]
36 Fix warnings about valid time zone abbreviations. [EN-16:19]
37 Update timezone database information. [EN-16:20]
39 20161102 p12 FreeBSD-SA-16:33.openssh
40 FreeBSD-SA-16:35.openssl
42 Fix OpenSSH remote Denial of Service vulnerability. [SA-16:33]
44 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
46 20161025 p11 FreeBSD-SA-16:15.sysarch [revised]
49 Fix incorrect argument validation in sysarch(2). [SA-16:15]
50 Fix virtual memory subsystem bugs. [EN-16:17]
52 20161010 p10 FreeBSD-SA-16:29.bspatch
53 FreeBSD-SA-16:30.portsnap
54 FreeBSD-SA-16:31.libarchive
56 Fix bspatch heap overflow vulnerability. [SA-16:29]
58 Fix multiple portsnap vulnerabilities. [SA-16:30]
60 Fix multiple libarchive vulnerabilities. [SA-16:31]
62 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
64 Fix OpenSSL regression introduced in SA-16:26.
66 20160923 p8 FreeBSD-SA-16:26.openssl
68 Fix multiple OpenSSL vulnerabilitites.
70 20160811 p7 FreeBSD-EN-16:10.dhclient
71 FreeBSD-EN-16:11.vmbus
72 FreeBSD-EN-16:12.hv_storvsc
73 FreeBSD-EN-16:13.vmbus
74 FreeBSD-EN-16:14.hv_storvsc
75 FreeBSD-EN-16:15.vmbus
76 FreeBSD-EN-16:16.hv_storvsc
78 Fix handling of unknown options from a DHCP server. [EN-16:10]
79 Fix a panic in hv_vmbus(4). [EN-16:11]
80 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
81 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
82 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
83 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
84 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
86 20160725 p6 FreeBSD-SA-16:25.bspatch
87 FreeBSD-EN-16:09.freebsd-update
89 Fix bspatch heap overflow vulnerability. [SA-16:25]
91 Fix freebsd-update(8) support of FreeBSD 11.0 release
92 distribution. [EN-16:09]
94 20160604 p5 FreeBSD-SA-16:24.ntp
96 Fix multiple vulnerabilities of ntp.
98 20160531 p4 FreeBSD-SA-16:20.linux
99 FreeBSD-SA-16:21.43bsd
100 FreeBSD-SA-16:22.libarchive
102 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
103 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
104 Fix directory traversal in cpio(1). [SA-16:22]
107 20160517 p3 FreeBSD-SA-16:18.atkbd
108 FreeBSD-SA-16:19.sendmsg
110 Fix buffer overflow in keyboard driver. [SA-16:18]
112 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
114 20160504 p2 FreeBSD-SA-16:17.openssl
115 FreeBSD-EN-16:06.libc
119 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
121 Fix performance regression in libc hash(3). [EN-16:06]
123 Fix excessive latency in x86 IPI delivery. [EN-16:07]
125 Fix memory leak in ZFS. [EN-16:08]
127 20160429 p1 FreeBSD-SA-16:16.ntp
129 Fix multiple vulnerabilities of ntp.
135 The NONE and HPN patches has been removed from OpenSSH. They are
136 still available in the security/openssh-portable port.
139 r292223 changed the internal interface between the nfsd.ko and
140 nfscommon.ko modules. As such, they must both be upgraded to-gether.
141 __FreeBSD_version has been bumped because of this.
144 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
145 Kernel modules isp_2400_multi and isp_2500_multi were removed and
146 should be replaced with isp_2400 and isp_2500 modules respectively.
149 The menu.rc and loader.rc files will now be replaced during
150 upgrades. Please migrate local changes to menu.rc.local and
151 loader.rc.local instead.
154 NTP has been upgraded to 4.2.8p4.
157 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
158 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
159 and devel/kyua to version 0.20+ and adjust any calling code to work
160 with Kyuafile and kyua.
163 The polarity of Pulse Per Second (PPS) capture events with the
164 uart(4) driver has been corrected. Prior to this change the PPS
165 "assert" event corresponded to the trailing edge of a positive PPS
166 pulse and the "clear" event was the leading edge of the next pulse.
168 As the width of a PPS pulse in a typical GPS receiver is on the
169 order of 1 millisecond, most users will not notice any significant
170 difference with this change.
172 Anyone who has compensated for the historical polarity reversal by
173 configuring a negative offset equal to the pulse width will need to
174 remove that workaround.
177 From legacy ata(4) driver was removed support for SATA controllers
178 supported by more functional drivers ahci(4), siis(4) and mvs(4).
179 Kernel modules ataahci and ataadaptec were removed completely,
180 replaced by ahci and mvs modules respectively.
186 As ZFS requires more kernel stack pages than is the default on some
187 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
188 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
190 Please consider using 'options KSTACK_PAGES=X' where X is greater
191 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
194 The default Unbound configuration now enables remote control
195 using a local socket. Users who have already enabled the
196 local_unbound service should regenerate their configuration
197 by running "service local_unbound setup" as root.
200 An additional fix for the issue described in the 20150614 sendmail
201 entry below has been been committed in revision 284786.
204 The fix for the issue described in the 20150614 sendmail entry
205 below has been been committed in revision 284485. The work
206 around described in that entry is no longer needed unless the
207 default setting is overridden by a confDH_PARAMETERS configuration
208 setting of '5' or pointing to a 512 bit DH parameter file.
211 The import of openssl to address the FreeBSD-SA-15:10.openssl
212 security advisory includes a change which rejects handshakes
213 with DH parameters below 768 bits. sendmail releases prior
214 to 8.15.2 (not yet released), defaulted to a 512 bit
215 DH parameter setting for client connections. To work around
216 this interoperability, sendmail can be configured to use a
217 2048 bit DH parameter by:
219 1. Edit /etc/mail/`hostname`.mc
220 2. If a setting for confDH_PARAMETERS does not exist or
221 exists and is set to a string beginning with '5',
223 3. If a setting for confDH_PARAMETERS exists and is set to
224 a file path, create a new file with:
225 openssl dhparam -out /path/to/file 2048
226 4. Rebuild the .cf file:
227 cd /etc/mail/; make; make install
229 cd /etc/mail/; make restart
231 A sendmail patch is coming, at which time this file will be
235 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
236 defined in symlink(7); previously symlinks were silently ignored.
239 The const qualifier has been removed from iconv(3) to comply with
240 POSIX. The ports tree is aware of this from r384038 onwards.
243 At svn r275807, The default linux compat kernel ABI has been adjusted
244 to 2.6.18 in support of the linux-c6 compat ports infrastructure
245 update. If you wish to continue using the linux-f10 compat ports,
246 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
247 encouraged to update their linux-compat packages to linux-c6 during
248 their next update cycle.
250 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
253 pjdfstest has been integrated into kyua as an opt-in test suite.
254 Please see share/doc/pjdfstest/README for a more details on how to
261 The ofwfb driver, used to provide a graphics console on PowerPC when
262 using vt(4), no longer allows mmap() of all of physical memory. This
263 will prevent Xorg on PowerPC with some ATI graphics cards from
264 initializing properly unless x11-servers/xorg-server is updated to
268 The libatf-c and libatf-c++ major versions were downgraded to 0 and
269 1 respectively to match the upstream numbers. They were out of
270 sync because, when they were originally added to FreeBSD, the
271 upstream versions were not respected. These libraries are private
272 and not yet built by default, so renumbering them should be a
273 non-issue. However, unclean source trees will yield broken test
274 programs once the operator executes "make delete-old-libs" after a
277 Additionally, the atf-sh binary was made private by moving it into
278 /usr/libexec/. Already-built shell test programs will keep the
279 path to the old binary so they will break after "make delete-old"
282 If you are using WITH_TESTS=yes (not the default), wipe the object
283 tree and rebuild from scratch to prevent spurious test failures.
284 This is only needed once: the misnumbered libraries and misplaced
285 binaries have been added to OptionalObsoleteFiles.inc so they will
286 be removed during a clean upgrade.
289 The ixgbe tunables now match their sysctl counterparts, for example:
290 hw.ixgbe.enable_aim => hw.ix.enable_aim
291 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
294 The NFSv4.1 server committed by r269398 changes the internal
295 function call interfaces used between the NFS and krpc modules.
296 As such, __FreeBSD_version was bumped.
299 The default unbound configuration has been modified to address
300 issues with reverse lookups on networks that use private
301 address ranges. If you use the local_unbound service, run
302 "service local_unbound setup" as root to regenerate your
303 configuration, then "service local_unbound reload" to load the
307 It is no longer necessary to include the dwarf version in your DEBUG
308 options in your kernel config file. The bug that required it to be
309 placed in the config file has bene fixed. DEBUG should now just
310 contain -g. The build system will automatically update things
311 to do the right thing.
314 Several ABI breaking changes were merged to CTL and new iSCSI code.
315 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
316 iscsictl need to be rebuilt to work with a new kernel.
319 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
320 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
321 which differs from the behaviour controlled by this knob.)
324 On i386 and amd64 systems, the onifconsole flag is now set by default
325 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
326 as a login TTY if it is set in the bootloader as an active kernel
327 console. No changes in behavior should result otherwise. To revert to
328 the previous behavior, set ttyu0 to "off" in /etc/ttys.
331 Clang and llvm have been upgraded to 3.4.1 release.
334 Clang and llvm have been upgraded to 3.4 release.
337 If a Makefile in a tests/ directory was auto-generating a Kyuafile
338 instead of providing an explicit one, this would prevent such
339 Makefile from providing its own Kyuafile in the future during
340 NO_CLEAN builds. This has been fixed in the Makefiles but manual
341 intervention is needed to clean an objdir if you use NO_CLEAN:
342 # find /usr/obj -name Kyuafile | xargs rm -f
345 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
346 capability mode support. Please note that enabling the feature in
347 kernel is still highly recommended.
350 OpenSSH is now built with sandbox support, and will use sandbox as
351 the default privilege separation method. This requires Capsicum
352 capability mode support in kernel.
355 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
356 been deprecated and will not be part of FreeBSD 11.0 and later
357 releases. If you use this driver, please consider switching to
358 the nfe(4) driver instead.
364 The behavior of gss_pseudo_random() for the krb5 mechanism
365 has changed, for applications requesting a longer random string
366 than produced by the underlying enctype's pseudo-random() function.
367 In particular, the random string produced from a session key of
368 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
369 be different at the 17th octet and later, after this change.
370 The counter used in the PRF+ construction is now encoded as a
371 big-endian integer in accordance with RFC 4402.
372 __FreeBSD_version is bumped to 1000701.
375 The WITHOUT_ATF build knob has been removed and its functionality
376 has been subsumed into the more generic WITHOUT_TESTS. If you were
377 using the former to disable the build of the ATF libraries, you
378 should change your settings to use the latter.
381 The default version of mtree is nmtree which is obtained from
382 NetBSD. The output is generally the same, but may vary
383 slightly. If you found you need identical output adding
384 "-F freebsd9" to the command line should do the trick. For the
385 time being, the old mtree is available as fmtree.
388 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
389 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
390 1.1.4_8 and verify bsdyml not linked in, before running "make
392 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
394 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
397 The rc.d/jail script has been updated to support jail(8)
398 configuration file. The "jail_<jname>_*" rc.conf(5) variables
399 for per-jail configuration are automatically converted to
400 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
401 This is transparently backward compatible. See below about some
402 incompatibilities and rc.conf(5) manual page for more details.
404 These variables are now deprecated in favor of jail(8) configuration
405 file. One can use "rc.d/jail config <jname>" command to generate
406 a jail(8) configuration file in /var/run/jail.<jname>.conf without
407 running the jail(8) utility. The default pathname of the
408 configuration file is /etc/jail.conf and can be specified by
409 using $jail_conf or $jail_<jname>_conf variables.
411 Please note that jail_devfs_ruleset accepts an integer at
412 this moment. Please consider to rewrite the ruleset name
416 BIND has been removed from the base system. If all you need
417 is a local resolver, simply enable and start the local_unbound
418 service instead. Otherwise, several versions of BIND are
419 available in the ports tree. The dns/bind99 port is one example.
421 With this change, nslookup(1) and dig(1) are no longer in the base
422 system. Users should instead use host(1) and drill(1) which are
423 in the base system. Alternatively, nslookup and dig can
424 be obtained by installing the dns/bind-tools port.
427 With the addition of unbound(8), a new unbound user is now
428 required during installworld. "mergemaster -p" can be used to
429 add the user prior to installworld, as documented in the handbook.
432 OpenSSH is now built with DNSSEC support, and will by default
433 silently trust signed SSHFP records. This can be controlled with
434 the VerifyHostKeyDNS client configuration setting. DNSSEC support
435 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
438 The GNU Compiler Collection and C++ standard library (libstdc++)
439 are no longer built by default on platforms where clang is the system
440 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
444 The PROCDESC kernel option is now part of the GENERIC kernel
445 configuration and is required for the rwhod(8) to work.
446 If you are using custom kernel configuration, you should include
450 The API and ABI related to the Capsicum framework was modified
451 in backward incompatible way. The userland libraries and programs
452 have to be recompiled to work with the new kernel. This includes the
453 following libraries and programs, but the whole buildworld is
454 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
455 kdump, procstat, rwho, rwhod, uniq.
458 AES-NI intrinsic support has been added to gcc. The AES-NI module
459 has been updated to use this support. A new gcc is required to build
460 the aesni module on both i386 and amd64.
463 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
464 Thus "device padlock_rng" and "device rdrand_rng" should be
465 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
468 WITH_ICONV has been split into two feature sets. WITH_ICONV now
469 enables just the iconv* functionality and is now on by default.
470 WITH_LIBICONV_COMPAT enables the libiconv api and link time
471 compatability. Set WITHOUT_ICONV to build the old way.
472 If you have been using WITH_ICONV before, you will very likely
473 need to turn on WITH_LIBICONV_COMPAT.
476 INVARIANTS option now enables DEBUG for code with OpenSolaris and
477 Illumos origin, including ZFS. If you have INVARIANTS in your
478 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
480 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
481 locks if WITNESS option was set. Because that generated a lot of
482 witness(9) reports and all of them were believed to be false
483 positives, this is no longer done. New option OPENSOLARIS_WITNESS
484 can be used to achieve the previous behavior.
487 Timer values in IPv6 data structures now use time_uptime instead
488 of time_second. Although this is not a user-visible functional
489 change, userland utilities which directly use them---ndp(8),
490 rtadvd(8), and rtsold(8) in the base system---need to be updated
494 find -delete can now delete the pathnames given as arguments,
495 instead of only files found below them or if the pathname did
496 not contain any slashes. Formerly, the following error message
499 find: -delete: <path>: relative path potentially not safe
501 Deleting the pathnames given as arguments can be prevented
502 without error messages using -mindepth 1 or by changing
503 directory and passing "." as argument to find. This works in the
504 old as well as the new version of find.
507 Behavior of devfs rules path matching has been changed.
508 Pattern is now always matched against fully qualified devfs
509 path and slash characters must be explicitly matched by
510 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
511 subdirectories must be reviewed.
514 The default ARM ABI has changed to the ARM EABI. The old ABI is
515 incompatible with the ARM EABI and all programs and modules will
516 need to be rebuilt to work with a new kernel.
518 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
520 NOTE: Support for the old ABI will be removed in the future and
521 users are advised to upgrade.
524 pkg_install has been disconnected from the build if you really need it
525 you should add WITH_PKGTOOLS in your src.conf(5).
528 Most of network statistics structures were changed to be able
529 keep 64-bits counters. Thus all tools, that work with networking
530 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
533 Fix a bug that allowed a tracing process (e.g. gdb) to write
534 to a memory-mapped file in the traced process's address space
535 even if neither the traced process nor the tracing process had
536 write access to that file.
539 CVS has been removed from the base system. An exact copy
540 of the code is available from the devel/cvs port.
543 Some people report the following error after the switch to bmake:
545 make: illegal option -- J
546 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
548 *** [buildworld] Error code 2
550 this likely due to an old instance of make in
551 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
552 which src/Makefile will use that blindly, if it exists, so if
553 you see the above error:
555 rm -rf `make -V MAKEPATH`
560 Use bmake by default.
561 Whereas before one could choose to build with bmake via
562 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
563 make. The goal is to remove these knobs for 10-RELEASE.
565 It is worth noting that bmake (like gmake) treats the command
566 line as the unit of failure, rather than statements within the
567 command line. Thus '(cd some/where && dosomething)' is safer
568 than 'cd some/where; dosomething'. The '()' allows consistent
569 behavior in parallel build.
572 Fix a bug that allows NFS clients to issue READDIR on files.
575 The WITHOUT_IDEA option has been removed because
576 the IDEA patent expired.
579 The sysctl which controls TRIM support under ZFS has been renamed
580 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
584 The mergemaster command now uses the default MAKEOBJDIRPREFIX
585 rather than creating it's own in the temporary directory in
586 order allow access to bootstrapped versions of tools such as
587 install and mtree. When upgrading from version of FreeBSD where
588 the install command does not support -l, you will need to
589 install a new mergemaster command if mergemaster -p is required.
590 This can be accomplished with the command (cd src/usr.sbin/mergemaster
594 Legacy ATA stack, disabled and replaced by new CAM-based one since
595 FreeBSD 9.0, completely removed from the sources. Kernel modules
596 atadisk and atapi*, user-level tools atacontrol and burncd are
597 removed. Kernel option `options ATA_CAM` is now permanently enabled
601 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
602 and socketpair(2). Software, in particular Kerberos, may
603 automatically detect and use these during building. The resulting
604 binaries will not work on older kernels.
607 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
608 information, see the respective 20130304 entry).
611 Recent commits to callout(9) changed the size of struct callout,
612 so the KBI is probably heavily disturbed. Also, some functions
613 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
614 by macros. Every kernel module using it won't load, so rebuild
617 The ctl device has been re-enabled in GENERIC for i386 and amd64,
618 but does not initialize by default (because of the new CTL_DISABLE
619 option) to save memory. To re-enable it, remove the CTL_DISABLE
620 option from the kernel config file or set kern.cam.ctl.disable=0
621 in /boot/loader.conf.
624 The ctl device has been disabled in GENERIC for i386 and amd64.
625 This was done due to the extra memory being allocated at system
626 initialisation time by the ctl driver which was only used if
627 a CAM target device was created. This makes a FreeBSD system
628 unusable on 128MB or less of RAM.
631 A new compression method (lz4) has been merged to -HEAD. Please
632 refer to zpool-features(7) for more information.
634 Please refer to the "ZFS notes" section of this file for information
635 on upgrading boot ZFS pools.
638 A BSD-licensed patch(1) variant has been added and is installed
639 as bsdpatch, being the GNU version the default patch.
640 To inverse the logic and use the BSD-licensed one as default,
641 while having the GNU version installed as gnupatch, rebuild
642 and install world with the WITH_BSD_PATCH knob set.
645 Due to the use of the new -l option to install(1) during build
646 and install, you must take care not to directly set the INSTALL
647 make variable in your /etc/make.conf, /etc/src.conf, or on the
648 command line. If you wish to use the -C flag for all installs
649 you may be able to add INSTALL+=-C to /etc/make.conf or
653 The install(1) option -M has changed meaning and now takes an
654 argument that is a file or path to append logs to. In the
655 unlikely event that -M was the last option on the command line
656 and the command line contained at least two files and a target
657 directory the first file will have logs appended to it. The -M
658 option served little practical purpose in the last decade so its
659 use is expected to be extremely rare.
662 After switching to Clang as the default compiler some users of ZFS
663 on i386 systems started to experience stack overflow kernel panics.
664 Please consider using 'options KSTACK_PAGES=4' in such configurations.
667 GEOM_LABEL now mangles label names read from file system metadata.
668 Mangling affect labels containing spaces, non-printable characters,
669 '%' or '"'. Device names in /etc/fstab and other places may need to
673 By default, only the 10 most recent kernel dumps will be saved. To
674 restore the previous behaviour (no limit on the number of kernel dumps
675 stored in the dump directory) add the following line to /etc/rc.conf:
680 With the addition of auditdistd(8), a new auditdistd user is now
681 required during installworld. "mergemaster -p" can be used to
682 add the user prior to installworld, as documented in the handbook.
685 The sin6_scope_id member variable in struct sockaddr_in6 is now
686 filled by the kernel before passing the structure to the userland via
687 sysctl or routing socket. This means the KAME-specific embedded scope
688 id in sin6_addr.s6_addr[2] is always cleared in userland application.
689 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
690 __FreeBSD_version is bumped to 1000025.
693 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
694 This means that the world and kernel will be compiled with clang
695 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
696 and /usr/bin/cpp. To disable this behavior and revert to building
697 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
698 of current may need to bootstrap WITHOUT_CLANG first if the clang
699 build fails (its compatibility window doesn't extend to the 9 stable
703 The IPFIREWALL_FORWARD kernel option has been removed. Its
704 functionality now turned on by default.
707 The ZERO_COPY_SOCKET kernel option has been removed and
708 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
709 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
710 mechanism which is not safe and may result in kernel crashes.
711 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
712 driver supports disposeable external page sized mbuf storage.
713 Proper replacements for both zero-copy mechanisms are under
714 consideration and will eventually lead to complete removal
715 of the two kernel options.
718 The IPv4 network stack has been converted to network byte
719 order. The following modules need to be recompiled together
720 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
721 pf(4), ipfw(4), ng_ipfw(4), stf(4).
724 Support for non-MPSAFE filesystems was removed from VFS. The
725 VFS_VERSION was bumped, all filesystem modules shall be
729 All the non-MPSAFE filesystems have been disconnected from
730 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
731 portalfs, smbfs, xfs.
734 The interface cloning API and ABI has changed. The following
735 modules need to be recompiled together with kernel:
736 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
737 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
738 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
741 The sdhci driver was split in two parts: sdhci (generic SD Host
742 Controller logic) and sdhci_pci (actual hardware driver).
743 No kernel config modifications are required, but if you
744 load sdhc as a module you must switch to sdhci_pci instead.
747 Import the FUSE kernel and userland support into base system.
750 The GNU sort(1) program has been removed since the BSD-licensed
751 sort(1) has been the default for quite some time and no serious
752 problems have been reported. The corresponding WITH_GNU_SORT
756 The pfil(9) API/ABI for AF_INET family has been changed. Packet
757 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
761 The net80211(4) ABI has been changed to allow for improved driver
762 PS-POLL and power-save support. All wireless drivers need to be
763 recompiled to work with the new kernel.
766 The random(4) support for the VIA hardware random number
767 generator (`PADLOCK') is no longer enabled unconditionally.
768 Add the padlock_rng device in the custom kernel config if
769 needed. The GENERIC kernels on i386 and amd64 do include the
770 device, so the change only affects the custom kernel
774 The pf(4) packet filter ABI has been changed. pfctl(8) and
775 snmp_pf module need to be recompiled to work with new kernel.
778 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
779 to -HEAD. Pools that have empty_bpobj in active state can not be
780 imported read-write with ZFS implementations that do not support
781 this feature. For more information read the zpool-features(5)
785 The sparc64 ZFS loader has been changed to no longer try to auto-
786 detect ZFS providers based on diskN aliases but now requires these
787 to be explicitly listed in the OFW boot-device environment variable.
790 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
791 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
792 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
795 The following sysctls and tunables have been renamed for consistency
796 with other variables:
797 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
798 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
801 The sort utility has been replaced with BSD sort. For now, GNU sort
802 is also available as "gnusort" or the default can be set back to
803 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
804 installed as "bsdsort".
807 A new version of ZFS (pool version 5000) has been merged to -HEAD.
808 Starting with this version the old system of ZFS pool versioning
809 is superseded by "feature flags". This concept enables forward
810 compatibility against certain future changes in functionality of ZFS
811 pools. The first read-only compatible "feature flag" for ZFS pools
812 is named "com.delphix:async_destroy". For more information
813 read the new zpool-features(5) manual page.
814 Please refer to the "ZFS notes" section of this file for information
815 on upgrading boot ZFS pools.
818 The malloc(3) implementation embedded in libc now uses sources imported
819 as contrib/jemalloc. The most disruptive API change is to
820 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
821 delete it prior to installworld, and optionally re-create it using the
822 new format after rebooting. See malloc.conf(5) for details
823 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
827 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
828 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
829 now spelled mips. This is to aid compatibility with third-party
830 software that expects this naming scheme in uname(3). Little-endian
831 settings are unchanged. If you are updating a big-endian mips64 machine
832 from before this change, you may need to set MACHINE_ARCH=mips64 in
833 your environment before the new build system will recognize your machine.
836 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
840 Now unix domain sockets behave "as expected" on nullfs(5). Previously
841 nullfs(5) did not pass through all behaviours to the underlying layer,
842 as a result if we bound to a socket on the lower layer we could connect
843 only to the lower path; if we bound to the upper layer we could connect
844 only to the upper path. The new behavior is one can connect to both the
845 lower and the upper paths regardless what layer path one binds to.
848 The getifaddrs upgrade path broken with 20111215 has been restored.
849 If you have upgraded in between 20111215 and 20120209 you need to
850 recompile libc again with your kernel. You still need to recompile
851 world to be able to configure CARP but this restriction already
855 The set_rcvar() function has been removed from /etc/rc.subr. All
856 base and ports rc.d scripts have been updated, so if you have a
857 port installed with a script in /usr/local/etc/rc.d you can either
858 hand-edit the rcvar= line, or reinstall the port.
860 An easy way to handle the mass-update of /etc/rc.d:
861 rm /etc/rc.d/* && mergemaster -i
864 panic(9) now stops other CPUs in the SMP systems, disables interrupts
865 on the current CPU and prevents other threads from running.
866 This behavior can be reverted using the kern.stop_scheduler_on_panic
868 The new behavior can be incompatible with kern.sync_on_panic.
871 The carp(4) facility has been changed significantly. Configuration
872 of the CARP protocol via ifconfig(8) has changed, as well as format
873 of CARP events submitted to devd(8) has changed. See manual pages
874 for more information. The arpbalance feature of carp(4) is currently
875 not supported anymore.
877 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
878 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
879 need to be recompiled.
882 The acpi_wmi(4) status device /dev/wmistat has been renamed to
886 The option VFS_ALLOW_NONMPSAFE option has been added in order to
887 explicitely support non-MPSAFE filesystems.
888 It is on by default for all supported platform at this present
892 The broken amd(4) driver has been replaced with esp(4) in the amd64,
893 i386 and pc98 GENERIC kernel configuration files.
896 sysinstall has been removed
899 The stable/9 branch created in subversion. This corresponds to the
900 RELENG_9 branch in CVS.
903 This commit modifies vfs_register() so that it uses a hash
904 calculation to set vfc_typenum, which is enabled by default.
905 The first time a system is booted after this change, the
906 vfc_typenum values will change for all file systems. The
907 main effect of this is a change to the NFS server file handles
908 for file systems that use vfc_typenum in their fsid, such as ZFS.
909 It will, however, prevent vfc_typenum from changing when file
910 systems are loaded in a different order for subsequent reboots.
911 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
912 until you are ready to remount all NFS clients after a reboot.
915 Bump the shared library version numbers for libraries that
916 do not use symbol versioning, have changed the ABI compared
917 to stable/8 and which shared library version was not bumped.
918 Done as part of 9.0-RELEASE cycle.
921 During the merge of Capsicum features, the fget(9) KPI was modified.
922 This may require the rebuilding of out-of-tree device drivers --
923 issues have been reported specifically with the nVidia device driver.
924 __FreeBSD_version is bumped to 900041.
926 Also, there is a period between 20110811 and 20110814 where the
927 special devices /dev/{stdin,stdout,stderr} did not work correctly.
928 Building world from a kernel during that window may not work.
931 The packet filter (pf) code has been updated to OpenBSD 4.5.
932 You need to update userland tools to be in sync with kernel.
933 This update breaks backward compatibility with earlier pfsync(4)
934 versions. Care must be taken when updating redundant firewall setups.
937 The following sysctls and tunables are retired on x86 platforms:
939 machdep.hlt_logical_cpus
940 The following sysctl is retired:
941 machdep.hyperthreading_allowed
942 The sysctls were supposed to provide a way to dynamically offline and
943 online selected CPUs on x86 platforms, but the implementation has not
944 been reliable especially with SCHED_ULE scheduler.
945 machdep.hyperthreading_allowed tunable is still available to ignore
946 hyperthreading CPUs at OS level.
947 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
948 where X is an APIC ID of a CPU. Be advised, though, that disabling
949 CPUs in non-uniform fashion will result in non-uniform topology and
950 may lead to sub-optimal system performance with SCHED_ULE, which is
954 cpumask_t type is retired and cpuset_t is used in order to describe
958 Changes to ifconfig(8) for dynamic address family detection mandate
959 that you are running a kernel of 20110525 or later. Make sure to
960 follow the update procedure to boot a new kernel before installing
964 Support for sun4v architecture is officially dropped
967 Several KPI breaking changes have been committed to the mii(4) layer,
968 the PHY drivers and consequently some Ethernet drivers using mii(4).
969 This means that miibus.ko and the modules of the affected Ethernet
970 drivers need to be recompiled.
972 Note to kernel developers: Given that the OUI bit reversion problem
973 was fixed as part of these changes all mii(4) commits related to OUIs,
974 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
975 handling, no longer can be merged verbatim to stable/8 and previous
979 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
980 into their kernel configurations along with 'device pci'.
983 The default NFS client is now the new NFS client, so fstype "newnfs"
984 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
985 Although mounts via fstype "nfs" will usually work without userland
986 changes, it is recommended that the mount(8) and mount_nfs(8)
987 commands be rebuilt from sources and that a link to mount_nfs called
988 mount_oldnfs be created. The new client is compiled into the
989 kernel with "options NFSCL" and this is needed for diskless root
990 file systems. The GENERIC kernel configs have been changed to use
991 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
992 To use the regular/old client, you can "mount -t oldnfs ...". For
993 a diskless root file system, you must also include a line like:
995 vfs.root.mountfrom="oldnfs:"
997 in the boot/loader.conf on the root fs on the NFS server to make
998 a diskless root fs use the old client.
1001 The GENERIC kernels for all architectures now default to the new
1002 CAM-based ATA stack. It means that all legacy ATA drivers were
1003 removed and replaced by respective CAM drivers. If you are using
1004 ATA device names in /etc/fstab or other places, make sure to update
1005 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
1006 where 'Y's are the sequential numbers starting from zero for each type
1007 in order of detection, unless configured otherwise with tunables,
1008 see cam(4)). There will be symbolic links created in /dev/ to map
1009 old adX devices to the respective adaY. They should provide basic
1010 compatibility for file systems mounting in most cases, but they do
1011 not support old user-level APIs and do not have respective providers
1012 in GEOM. Consider using updated management tools with new device names.
1014 It is possible to load devices ahci, ata, siis and mvs as modules,
1015 but option ATA_CAM should remain in kernel configuration to make ata
1016 module work as CAM driver supporting legacy ATA controllers. Device ata
1017 still can be used in modular fashion (atacore + ...). Modules atadisk
1018 and atapi* are not used and won't affect operation in ATA_CAM mode.
1019 Note that to use CAM-based ATA kernel should include CAM devices
1020 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1021 them are parts of the cam module.
1023 ataraid(4) functionality is now supported by the RAID GEOM class.
1024 To use it you can load geom_raid kernel module and use graid(8) tool
1025 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1027 No kernel config options or code have been removed, so if a problem
1028 arises, please report it and optionally revert to the old ATA stack.
1029 In order to do it you can remove from the kernel config:
1034 , and instead add back:
1035 device atadisk # ATA disk drives
1036 device ataraid # ATA RAID drives
1037 device atapicd # ATAPI CDROM drives
1038 device atapifd # ATAPI floppy drives
1039 device atapist # ATAPI tape drives
1042 The default NFS server has been changed to the new server, which
1043 was referred to as the experimental server. If you need to switch
1044 back to the old NFS server, you must now put the "-o" option on
1045 both the mountd and nfsd commands. This can be done using the
1046 mountd_flags and nfs_server_flags rc.conf variables until an
1047 update to the rc scripts is committed, which is coming soon.
1050 The GNU Objective-C runtime library (libobjc), and other Objective-C
1051 related components have been removed from the base system. If you
1052 require an Objective-C library, please use one of the available ports.
1055 ath(4) has been split into bus- and device- modules. if_ath contains
1056 the HAL, the TX rate control and the network device code. if_ath_pci
1057 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1058 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1059 in order to use ath on everything else.
1061 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1062 need to load if_ath and if_ath_pci for ath(4) operation.
1065 As part of the replacement of sysinstall, the process of building
1066 release media has changed significantly. For details, please re-read
1067 release(7), which has been updated to reflect the new build process.
1070 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1071 is the last available version under GPLv2. It brings a number of new
1072 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1073 4.1 and SSE 4.2), better support for powerpc64, a number of new
1074 directives, and lots of other small improvements. See the ChangeLog
1075 file in contrib/binutils for the full details.
1078 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1079 compliant, and will now use half of hash for authentication.
1080 This will break interoperability with all stacks (including all
1081 actual FreeBSD versions) who implement
1082 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1084 The only workaround with such peers is to use another HMAC
1085 algorithm for IPsec ("phase 2") authentication.
1088 Remove the uio_yield prototype and symbol. This function has
1089 been misnamed since it was introduced and should not be
1090 globally exposed with this name. The equivalent functionality
1091 is now available using kern_yield(curthread->td_user_pri).
1092 The function remains undocumented.
1095 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1096 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1097 for scalar sysctls is defined but disabled. Code that needs
1098 UQUAD to pass the type checking that must compile on older
1099 systems where the define is not present can check against
1100 __FreeBSD_version >= 900030.
1102 The system dialog(1) has been replaced with a new version previously
1103 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1104 with the previous version, but the libdialog associated with it has
1105 a largely incompatible API. As such, the original version of libdialog
1106 will be kept temporarily as libodialog, until its base system consumers
1107 are replaced or updated. Bump __FreeBSD_version to 900030.
1110 If you are trying to run make universe on a -stable system, and you get
1111 the following warning:
1112 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1113 unknown. config(8) likely too old."
1114 or something similar to it, then you must upgrade your -stable system
1115 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1116 stable/8) or build the config from the latest stable/8 branch and
1117 install it on your system.
1119 Prior to this date, building a current universe on 8-stable system from
1120 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1121 error in the first kernel build phase. A new config on those old
1122 systems will fix that problem for older versions of -current.
1125 The TCP stack has been modified to allow Khelp modules to interact with
1126 it via helper hook points and store per-connection data in the TCP
1127 control block. Bump __FreeBSD_version to 900029. User space tools that
1128 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1132 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1133 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1134 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1135 to take advantage of it instead of using custom implementations. This
1136 means that these drivers now no longer unconditionally advertise
1137 support for flow control but only do so if flow control is a selected
1138 media option. This was implemented in the generic support that way in
1139 order to allow flow control to be switched on and off via ifconfig(8)
1140 with the PHY specific default to typically off in order to protect
1141 from unwanted effects. Consequently, if you used flow control with
1142 one of the above mentioned drivers you now need to explicitly enable
1143 it, for example via:
1144 ifconfig bge0 media auto mediaopt flowcontrol
1146 Along with the above mentioned changes generic support for setting
1147 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1148 e1000phy(4) as well as ip1000phy(4) have been converted to take
1149 advantage of it. This means that these drivers now no longer take the
1150 link0 parameter for selecting master mode but the master media option
1151 has to be used instead, for example like in the following:
1152 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1154 Selection of master mode now is also available with all other PHY
1155 drivers supporting 1000baseT.
1158 The TCP stack has received a significant update to add support for
1159 modularised congestion control and generally improve the clarity of
1160 congestion control decisions. Bump __FreeBSD_version to 900025. User
1161 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1162 sockstat) need to be recompiled.
1165 The man(1) utility has been replaced by a new version that no longer
1166 uses /etc/manpath.config. Please consult man.conf(5) for how to
1167 migrate local entries to the new format.
1170 The copyright strings printed by login(1) and sshd(8) at the time of a
1171 new connection have been removed to follow other operating systems and
1175 A workaround for a fixed ld bug has been removed in kernel code,
1176 so make sure that your system ld is built from sources after
1177 revision 210245 from 2010-07-19 (r211583 if building head kernel
1178 on stable/8, r211584 for stable/7; both from 2010-08-21).
1179 A symptom of incorrect ld version is different addresses for
1180 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1183 The $ipv6_prefer variable in rc.conf(5) has been split into
1184 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1186 The $ip6addrctl_policy is a variable to choose a pre-defined
1187 address selection policy set by ip6addrctl(8). A value
1188 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1191 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1192 flag (see an entry of 20090926) is set on an interface with no
1193 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1194 security reason. If you want IPv6 link-local address on all
1195 interfaces by default, set this to "YES".
1197 The old ipv6_prefer="YES" is equivalent to
1198 ipv6_activate_all_interfaces="YES" and
1199 ip6addrctl_policy="ipv6_prefer".
1202 DTrace has grown support for userland tracing. Due to this, DTrace is
1203 now i386 and amd64 only.
1204 dtruss(1) is now installed by default on those systems and a new
1205 kernel module is needed for userland tracing: fasttrap.
1206 No changes to your kernel config file are necessary to enable
1207 userland tracing, but you might consider adding 'STRIP=' and
1208 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1209 to have informative userland stack traces in DTrace (ustack).
1212 The acpi_aiboost(4) driver has been removed in favor of the new
1213 aibs(4) driver. You should update your kernel configuration file.
1216 BSD grep has been imported to the base system and it is built by
1217 default. It is completely BSD licensed, highly GNU-compatible, uses
1218 less memory than its GNU counterpart and has a small codebase.
1219 However, it is slower than its GNU counterpart, which is mostly
1220 noticeable for larger searches, for smaller ones it is measurable
1221 but not significant. The reason is complex, the most important factor
1222 is that we lack a modern and efficient regex library and GNU
1223 overcomes this by optimizing the searches internally. Future work
1224 on improving the regex performance is planned, for the meantime,
1225 users that need better performance, can build GNU grep instead by
1226 setting the WITH_GNU_GREP knob.
1229 Due to the import of powerpc64 support, all existing powerpc kernel
1230 configuration files must be updated with a machine directive like this:
1231 machine powerpc powerpc
1233 In addition, an updated config(8) is required to build powerpc kernels
1237 A new version of ZFS (version 15) has been merged to -HEAD.
1238 This version uses a python library for the following subcommands:
1239 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1240 For full functionality of these commands the following port must
1241 be installed: sysutils/py-zfs
1244 'vm_page's are now hashed by physical address to an array of mutexes.
1245 Currently this is only used to serialize access to hold_count. Over
1246 time the page queue mutex will be peeled away. This changes the size
1247 of pmap on every architecture. And requires all callers of vm_page_hold
1248 and vm_page_unhold to be updated.
1251 WITH_CTF can now be specified in src.conf (not recommended, there
1252 are some problems with static executables), make.conf (would also
1253 affect ports which do not use GNU make and do not override the
1254 compile targets) or in the kernel config (via "makeoptions
1256 When WITH_CTF was specified there before this was silently ignored,
1257 so make sure that WITH_CTF is not used in places which could lead
1258 to unwanted behavior.
1261 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1262 to allow 32-bit compatibility on non-x86 platforms. All kernel
1263 configurations on amd64 and ia64 platforms using these options must
1264 be modified accordingly.
1267 The utmp user accounting database has been replaced with utmpx,
1268 the user accounting interface standardized by POSIX.
1269 Unfortunately the semantics of utmp and utmpx don't match,
1270 making it practically impossible to support both interfaces.
1271 The user accounting database is used by tools like finger(1),
1272 last(1), talk(1), w(1) and ac(8).
1274 All applications in the base system use utmpx. This means only
1275 local binaries (e.g. from the ports tree) may still use these
1276 utmp database files. These applications must be rebuilt to make
1279 After the system has been upgraded, it is safe to remove the old
1280 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1281 assuming their contents is of no importance anymore. Old wtmp
1282 databases can only be used by last(1) and ac(8) after they have
1283 been converted to the new format using wtmpcvt(1).
1286 Introduce the kernel thread "deadlock resolver" (which can be enabled
1287 via the DEADLKRES option, see NOTES for more details) and the
1288 sleepq_type() function for sleepqueues.
1291 The rc.firewall and rc.firewall6 were unified, and
1292 rc.firewall6 and rc.d/ip6fw were removed.
1293 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1294 variables are obsoleted. Instead, the following new rc
1295 variables are added to rc.d/ipfw:
1297 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1298 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1299 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1301 The meanings correspond to the relevant IPv4 variables.
1307 The default terminal emulation for syscons(4) has been changed
1308 from cons25 to xterm on all platforms except pc98. This means
1309 that the /etc/ttys file needs to be updated to ensure correct
1310 operation of applications on the console.
1312 The terminal emulation style can be toggled per window by using
1313 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1314 options can be used to change the compile-time default back to
1317 To prevent graphical artifacts, make sure the TERM environment
1318 variable is set to match the terminal emulation that is being
1319 performed by syscons(4).
1322 The layout of the structure ieee80211req_scan_result has changed.
1323 Applications that require wireless scan results (e.g. ifconfig(8))
1324 from net80211 need to be recompiled.
1326 Applications such as wpa_supplicant(8) may require a full world
1327 build without using NO_CLEAN in order to get synchronized with the
1331 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1332 There's one kernel module for each firmware. Adding "device iwnfw"
1333 to the kernel configuration file means including all three firmware
1334 images inside the kernel. If you want to include just the one for
1335 your wireless card, use the devices iwn4965fw, iwn5000fw or
1339 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1340 into rc.d/netif. The changes are the following:
1342 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1343 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1344 Note that both variables need the "inet6" keyword at the head.
1346 Do not set $ipv6_network_interfaces manually if you do not
1347 understand what you are doing. It is not needed in most cases.
1349 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1352 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1353 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1355 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1356 all configured interfaces have "inet6 accept_rtadv" in the
1357 $ifconfig_IF_ipv6. These are for backward compatibility.
1359 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1360 functionality of interfaces with no corresponding
1361 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1362 and the default address selection policy of ip6addrctl(8)
1363 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1364 Note that if you want to configure IPv6 functionality on the
1365 disabled interfaces after boot, first you need to clear the flag by
1366 using ifconfig(8) like:
1368 ifconfig em0 inet6 -ifdisabled
1370 If YES, the default address selection policy is set as
1373 The default value of $ipv6_prefer is NO.
1375 4. If your system need to receive Router Advertisement messages,
1376 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1377 scripts automatically invoke rtsol(8) when the interface becomes
1378 UP. The Router Advertisement messages are used for SLAAC
1379 (State-Less Address AutoConfiguration).
1382 802.11s D3.03 support was committed. This is incompatible with the
1383 previous code, which was based on D3.0.
1386 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1387 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1388 control whether accepting Router Advertisement messages or not.
1389 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1390 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1391 The ifconfig(8) utility now supports these flags.
1394 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1395 mount(8) and -a option for df(1) to see them.
1398 The old tunable hw.bus.devctl_disable has been superseded by
1399 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1400 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1404 Remove the option STOP_NMI. The default action is now to use NMI only
1405 for KDB via the newly introduced function stop_cpus_hard() and
1406 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1409 The stable/8 branch created in subversion. This corresponds to the
1410 RELENG_8 branch in CVS.
1413 Bump the shared library version numbers for all libraries that do not
1414 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1415 __FreeBSD_version to 800105.
1418 Due to changes in the implementation of virtual network stack support,
1419 all network-related kernel modules must be recompiled. As this change
1420 breaks the ABI, bump __FreeBSD_version to 800104.
1423 The TOE interface to the TCP syncache has been modified to remove
1424 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1425 The cxgb driver is the only TOE consumer affected by this change, and
1426 needs to be recompiled along with the kernel. As this change breaks
1427 the ABI, bump __FreeBSD_version to 800103.
1430 Padding has been added to struct tcpcb, sackhint and tcpstat in
1431 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1432 maintaining the ABI. However, this change breaks the ABI, so bump
1433 __FreeBSD_version to 800102. User space tools that rely on the size of
1434 any of these structs (e.g. sockstat) need to be recompiled.
1437 The NFS_LEGACYRPC option has been removed along with the old kernel
1438 RPC implementation that this option selected. Kernel configurations
1439 may need to be adjusted.
1442 The network interface device nodes at /dev/net/<interface> have been
1443 removed. All ioctl operations can be performed the normal way using
1444 routing sockets. The kqueue functionality can generally be replaced
1445 with routing sockets.
1448 The documentation from the FreeBSD Documentation Project (Handbook,
1449 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1450 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1453 The ABI of various structures related to the SYSV IPC API have been
1454 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1455 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1459 Layout of struct vnet has changed as routing related variables were
1460 moved to their own Vimage module. Modules need to be recompiled. Bump
1461 __FreeBSD_version to 800099.
1464 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1465 respectively. As long as no more than 16 groups per process are used,
1466 no changes should be visible. When more than 16 groups are used, old
1467 binaries may fail if they call getgroups() or getgrouplist() with
1468 statically sized storage. Recompiling will work around this, but
1469 applications should be modified to use dynamically allocated storage
1470 for group arrays as POSIX.1-2008 does not cap an implementation's
1471 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1473 NFS and portalfs mounts may also be affected as the list of groups is
1474 truncated to 16. Users of NFS who use more than 16 groups, should
1475 take care that negative group permissions are not used on the exported
1476 file systems as they will not be reliable unless a GSSAPI based
1477 authentication method is used.
1480 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1481 option compiles in the support for adaptive spinning for lockmgrs
1482 which want to enable it. The lockinit() function now accepts the flag
1483 LK_ADAPTIVE in order to make the lock object subject to adaptive
1484 spinning when both held in write and read mode.
1487 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1488 changed. User applications that use this ioctl need to be rebuilt.
1491 The layout of struct thread has changed. Kernel and modules need to
1495 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1496 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1499 window(1) has been removed from the base system. It can now be
1500 installed from ports. The port is called misc/window.
1503 The way we are storing and accessing `routing table' entries has
1504 changed. Programs reading the FIB, like netstat, need to be
1508 A new netisr implementation has been added for FreeBSD 8. Network
1509 file system modules, such as igmp, ipdivert, and others, should be
1511 Bump __FreeBSD_version to 800096.
1514 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1518 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1519 Bump __FreeBSD_version to 800094.
1522 Add mnt_xflag field to 'struct mount'. File system modules need to be
1524 Bump __FreeBSD_version to 800093.
1527 The compiling option ADAPTIVE_SX has been retired while it has been
1528 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1529 The KPI for sx_init_flags() changes as accepting flags:
1530 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1531 been introduced in order to handle the reversed logic.
1532 Bump __FreeBSD_version to 800092.
1535 Add support for hierarchical jails. Remove global securelevel.
1536 Bump __FreeBSD_version to 800091.
1539 The layout of struct vnet_net has changed, therefore modules
1541 Bump __FreeBSD_version to 800090.
1544 The newly imported zic(8) produces a new format in the output. Please
1545 run tzsetup(8) to install the newly created data to /etc/localtime.
1548 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1549 hw.usb.* and is now consistent again with previous releases.
1552 802.11 monitor mode support was revised and driver api's were changed.
1553 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1554 of DLT_IEEE802_11. No user-visible data structures were changed but
1555 applications that use DLT_IEEE802_11 may require changes.
1556 Bump __FreeBSD_version to 800088.
1559 The layout of the following structs has changed: sysctl_oid,
1560 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1561 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1562 panics may be experienced. World rebuild is required for
1563 correctly checking networking state from userland.
1564 Bump __FreeBSD_version to 800085.
1567 MLDv2 and Source-Specific Multicast (SSM) have been merged
1568 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1569 The implementation of SSM within FreeBSD's IPv6 stack closely
1570 follows the IPv4 implementation.
1572 For kernel developers:
1574 * The most important changes are that the ip6_output() and
1575 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1576 and this lock has been downgraded to a non-recursive mutex.
1578 * As with the changes to the IPv4 stack to support SSM, filtering
1579 of inbound multicast traffic must now be performed by transport
1580 protocols within the IPv6 stack. This does not apply to TCP and
1581 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1583 * The KPIs used by IPv6 multicast are similar to those used by
1584 the IPv4 stack, with the following differences:
1585 * im6o_mc_filter() is analogous to imo_multicast_filter().
1586 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1587 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1588 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1589 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1590 for MLDv1 have an additional 'timer' argument which is used to
1591 jitter the initial membership report for the solicited-node
1592 multicast membership on-link.
1593 * This is not strictly needed for MLDv2, which already jitters
1594 its report transmissions. However, the 'timer' argument is
1595 preserved in case MLDv1 is active on the interface.
1597 * The KAME linked-list based IPv6 membership implementation has
1598 been refactored to use a vector similar to that used by the IPv4
1600 Code which maintains a list of its own multicast memberships
1601 internally, e.g. carp, has been updated to reflect the new
1604 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1605 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1606 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1607 implementation constraint which needs to be addressed in HEAD.
1609 For application developers:
1611 * The changes are broadly similar to those made for the IPv4
1614 * The use of IPv4 and IPv6 multicast socket options on the same
1615 socket, using mapped addresses, HAS NOT been tested or supported.
1617 * There are a number of issues with the implementation of various
1618 IPv6 multicast APIs which need to be resolved in the API surface
1619 before the implementation is fully compatible with KAME userland
1620 use, and these are mostly to do with interface index treatment.
1622 * The literature available discusses the use of either the delta / ASM
1623 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1624 using setsourcefilter(3)/getsourcefilter(3). For more information
1625 please refer to RFC 3768, 'Socket Interface Extensions for
1626 Multicast Source Filters'.
1628 * Applications which use the published RFC 3678 APIs should be fine.
1630 For systems administrators:
1632 * The mtest(8) utility has been refactored to support IPv6, in
1633 addition to IPv4. Interface addresses are no longer accepted
1634 as arguments, their names must be used instead. The utility
1635 will map the interface name to its first IPv4 address as
1636 returned by getifaddrs(3).
1638 * The ifmcstat(8) utility has also been updated to print the MLDv2
1639 endpoint state and source filter lists via sysctl(3).
1641 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1642 loopback of IPv6 multicast datagrams by default; it defaults to 1
1643 to preserve the existing behaviour. Disabling multicast loopback is
1644 recommended for optimal system performance.
1646 * The IPv6 MROUTING code has been changed to examine this sysctl
1647 instead of attempting to perform a group lookup before looping
1648 back forwarded datagrams.
1650 Bump __FreeBSD_version to 800084.
1653 Implement low-level Bluetooth HCI API.
1654 Bump __FreeBSD_version to 800083.
1657 The layout of struct malloc_type, used by modules to register new
1658 memory allocation types, has changed. Most modules will need to
1659 be rebuilt or panics may be experienced.
1660 Bump __FreeBSD_version to 800081.
1663 Anticipate overflowing inp_flags - add inp_flags2.
1664 This changes most offsets in inpcb, so checking v4 connection
1665 state will require a world rebuild.
1666 Bump __FreeBSD_version to 800080.
1669 Add an llentry to struct route and struct route_in6. Modules
1670 embedding a struct route will need to be recompiled.
1671 Bump __FreeBSD_version to 800079.
1674 The size of rt_metrics_lite and by extension rtentry has changed.
1675 Networking administration apps will need to be recompiled.
1676 The route command now supports show as an alias for get, weighting
1677 of routes, sticky and nostick flags to alter the behavior of stateful
1679 Bump __FreeBSD_version to 800078.
1682 Do not use Giant for kbdmux(4) locking. This is wrong and
1683 apparently causing more problems than it solves. This will
1684 re-open the issue where interrupt handlers may race with
1685 kbdmux(4) in polling mode. Typical symptoms include (but
1686 not limited to) duplicated and/or missing characters when
1687 low level console functions (such as gets) are used while
1688 interrupts are enabled (for example geli password prompt,
1689 mountroot prompt etc.). Disabling kbdmux(4) may help.
1692 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1693 kernel modules referencing any of the above need to be recompiled.
1694 Bump __FreeBSD_version to 800075.
1697 GEOM_PART has become the default partition slicer for storage devices,
1698 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1699 introduces some changes:
1701 MSDOS/EBR: the devices created from MSDOS extended partition entries
1702 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1703 to devices with offset-based names. fstabs may need to be modified.
1705 BSD: the "geometry does not match label" warning is harmless in most
1706 cases but it points to problems in file system misalignment with
1707 disk geometry. The "c" partition is now implicit, covers the whole
1708 top-level drive and cannot be (mis)used by users.
1710 General: Kernel dumps are now not allowed to be written to devices
1711 whose partition types indicate they are meant to be used for file
1712 systems (or, in case of MSDOS partitions, as something else than
1715 Most of these changes date approximately from 200812.
1718 The uscanner(4) driver has been removed from the kernel. This follows
1719 Linux removing theirs in 2.6 and making libusb the default interface
1720 (supported by sane).
1723 The multicast forwarding code has been cleaned up. netstat(1)
1724 only relies on KVM now for printing bandwidth upcall meters.
1725 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1726 ip6_mroute_mod respectively. The config(5) options for statically
1727 compiling this code remain the same, i.e. 'options MROUTING'.
1730 Support for the IFF_NEEDSGIANT network interface flag has been
1731 removed, which means that non-MPSAFE network device drivers are no
1732 longer supported. In particular, if_ar, if_sr, and network device
1733 drivers from the old (legacy) USB stack can no longer be built or
1737 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1738 a bunch of new language catalog files have also been added.
1739 This means that some common libc messages are now localized and
1740 they depend on the LC_MESSAGES environmental variable.
1743 The k8temp(4) driver has been renamed to amdtemp(4) since
1744 support for Family 10 and Family 11 CPU families was added.
1747 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1748 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1750 For kernel developers, the most important changes are that the
1751 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1752 and this lock has been downgraded to a non-recursive mutex.
1754 Transport protocols (UDP, Raw IP) are now responsible for filtering
1755 inbound multicast traffic according to group membership and source
1756 filters. The imo_multicast_filter() KPI exists for this purpose.
1757 Transports which do not use multicast (SCTP, TCP) already reject
1758 multicast by default. Forwarding and receive performance may improve
1759 as a mutex acquisition is no longer needed in the ip_input()
1760 low-level input path. in_addmulti() and in_delmulti() are shimmed
1761 to new KPIs which exist to support SSM in-kernel.
1763 For application developers, it is recommended that loopback of
1764 multicast datagrams be disabled for best performance, as this
1765 will still cause the lock to be taken for each looped-back
1766 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1767 be tuned to 0 to disable loopback by default; it defaults to 1
1768 to preserve the existing behaviour.
1770 For systems administrators, to obtain best performance with
1771 multicast reception and multiple groups, it is always recommended
1772 that a card with a suitably precise hash filter is used. Hash
1773 collisions will still result in the lock being taken within the
1774 transport protocol input path to check group membership.
1776 If deploying FreeBSD in an environment with IGMP snooping switches,
1777 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1778 enabled; this forces 224.0.0.0/24 group membership to be announced
1781 The size of 'struct igmpstat' has changed; netstat needs to be
1782 recompiled to reflect this.
1783 Bump __FreeBSD_version to 800070.
1786 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1787 updated to use it. This requires a buildworld/installworld in order to
1788 update the library and dependencies (usbconfig, etc). Its advisable to
1789 rebuild all ports which uses libusb. More specific directions are given
1790 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1791 libusb are no longer required and can be removed.
1794 A workaround is committed to allow the creation of System V shared
1795 memory segment of size > 2 GB on the 64-bit architectures.
1796 Due to a limitation of the existing ABI, the shm_segsz member
1797 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1798 wrong for large segments. Note that limits must be explicitly
1799 raised to allow such segments to be created.
1802 The layout of struct ifnet has changed, requiring a rebuild of all
1803 network device driver modules.
1806 The /dev handling for the new USB stack has changed, a
1807 buildworld/installworld is required for libusb20.
1810 The new USB2 stack has now been permanently moved in and all kernel and
1811 module names reverted to their previous values (eg, usb, ehci, ohci,
1812 ums, ...). The old usb stack can be compiled in by prefixing the name
1813 with the letter 'o', the old usb modules have been removed.
1814 Updating entry 20090216 for xorg and 20090215 for libmap may still
1818 The rc.conf(5) option if_up_delay has been renamed to
1819 defaultroute_delay to better reflect its purpose. If you have
1820 customized this setting in /etc/rc.conf you need to update it to
1824 xorg 7.4 wants to configure its input devices via hald which does not
1825 yet work with USB2. If the keyboard/mouse does not work in xorg then
1827 Option "AllowEmptyInput" "off"
1828 to your ServerLayout section. This will cause X to use the configured
1829 kbd and mouse sections from your xorg.conf.
1832 The GENERIC kernels for all architectures now default to the new USB2
1833 stack. No kernel config options or code have been removed so if a
1834 problem arises please report it and optionally revert to the old USB
1835 stack. If you are loading USB kernel modules or have a custom kernel
1836 that includes GENERIC then ensure that usb names are also changed over,
1837 eg uftdi -> usb2_serial_ftdi.
1839 Older programs linked against the ports libusb 0.1 need to be
1840 redirected to the new stack's libusb20. /etc/libmap.conf can
1842 # Map old usb library to new one for usb2 stack
1843 libusb-0.1.so.8 libusb20.so.1
1846 All USB ethernet devices now attach as interfaces under the name ueN
1847 (eg. ue0). This is to provide a predictable name as vendors often
1848 change usb chipsets in a product without notice.
1851 The ichsmb(4) driver has been changed to require SMBus slave
1852 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1853 All of the other SMBus controller drivers require left-justified
1854 slave addresses, so this change makes all the drivers provide the
1858 INET6 statistics (struct ip6stat) was updated.
1859 netstat(1) needs to be recompiled.
1862 NTFS has been removed from GENERIC kernel on amd64 to match
1863 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1864 will load ntfs.ko module automatically when NTFS support is
1865 actually needed, unless ntfs.ko is not installed or security
1866 level prohibits loading kernel modules. If either is the case,
1867 "options NTFS" has to be added into kernel config.
1870 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1871 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1872 800061. User space tools that rely on the size of struct tcpcb in
1873 tcp_var.h (e.g. sockstat) need to be recompiled.
1876 ng_tty(4) module updated to match the new TTY subsystem.
1877 Due to API change, user-level applications must be updated.
1878 New API support added to mpd5 CVS and expected to be present
1879 in next mpd5.3 release.
1882 With __FreeBSD_version 800060 the makefs tool is part of
1883 the base system (it was a port).
1886 The afdata and ifnet locks have been changed from mutexes to
1887 rwlocks, network modules will need to be re-compiled.
1890 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1891 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1892 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1893 architecture and 40 bytes on 64-bit architecture. The userland
1894 applications "arp" and "ndp" have been updated accordingly.
1895 The output from "netstat -r" shows only routing entries and
1896 none of the L2 information.
1899 __FreeBSD_version 800057 marks the switchover from the
1900 binary ath hal to source code. Users must add the line:
1902 options AH_SUPPORT_AR5416
1904 to their kernel config files when specifying:
1908 The ath_hal module no longer exists; the code is now compiled
1909 together with the driver in the ath module. It is now
1910 possible to tailor chip support (i.e. reduce the set of chips
1911 and thereby the code size); consult ath_hal(4) for details.
1914 __FreeBSD_version 800054 adds memory barriers to
1915 <machine/atomic.h>, new interfaces to ifnet to facilitate
1916 multiple hardware transmit queues for cards that support
1917 them, and a lock-less ring-buffer implementation to
1918 enable drivers to more efficiently manage queueing of
1922 A new version of ZFS (version 13) has been merged to -HEAD.
1923 This version has zpool attribute "listsnapshots" off by
1924 default, which means "zfs list" does not show snapshots,
1925 and is the same as Solaris behavior.
1928 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1931 The uhci, ohci, ehci and slhci USB Host controller drivers have
1932 been put into separate modules. If you load the usb module
1933 separately through loader.conf you will need to load the
1934 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1935 controller add the following to loader.conf:
1941 The ABI used by the PMC toolset has changed. Please keep
1942 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1946 atapci kernel module now includes only generic PCI ATA
1947 driver. AHCI driver moved to ataahci kernel module.
1948 All vendor-specific code moved into separate kernel modules:
1949 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1950 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1951 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1952 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1955 The TTY subsystem of the kernel has been replaced by a new
1956 implementation, which provides better scalability and an
1957 improved driver model. Most common drivers have been migrated to
1958 the new TTY subsystem, while others have not. The following
1959 drivers have not yet been ported to the new TTY layer:
1962 cy, digi, rc, rp, sio
1968 ng_h4, ng_tty, ppp, sl, snp
1970 Adding these drivers to your kernel configuration file shall
1971 cause compilation to fail.
1974 ntpd has been upgraded to 4.2.4p5.
1977 OpenSSH has been upgraded to 5.1p1.
1979 For many years, FreeBSD's version of OpenSSH preferred DSA
1980 over RSA for host and user authentication keys. With this
1981 upgrade, we've switched to the vendor's default of RSA over
1982 DSA. This may cause upgraded clients to warn about unknown
1983 host keys even for previously known hosts. Users should
1984 follow the usual procedure for verifying host keys before
1985 accepting the RSA key.
1987 This can be circumvented by setting the "HostKeyAlgorithms"
1988 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1991 Please note that the sequence of keys offered for
1992 authentication has been changed as well. You may want to
1993 specify IdentityFile in a different order to revert this
1997 The sio(4) driver has been removed from the i386 and amd64
1998 kernel configuration files. This means uart(4) is now the
1999 default serial port driver on those platforms as well.
2001 To prevent collisions with the sio(4) driver, the uart(4) driver
2002 uses different names for its device nodes. This means the
2003 onboard serial port will now most likely be called "ttyu0"
2004 instead of "ttyd0". You may need to reconfigure applications to
2005 use the new device names.
2007 When using the serial port as a boot console, be sure to update
2008 /boot/device.hints and /etc/ttys before booting the new kernel.
2009 If you forget to do so, you can still manually specify the hints
2010 at the loader prompt:
2012 set hint.uart.0.at="isa"
2013 set hint.uart.0.port="0x3F8"
2014 set hint.uart.0.flags="0x10"
2015 set hint.uart.0.irq="4"
2019 The gpt(8) utility has been removed. Use gpart(8) to partition
2023 The version that Linuxulator emulates was changed from 2.4.2
2024 to 2.6.16. If you experience any problems with Linux binaries
2025 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2026 if it fixes the problem contact emulation mailing list.
2029 ISDN4BSD (I4B) was removed from the src tree. You may need to
2030 update a your kernel configuration and remove relevant entries.
2033 I have checked in code to support multiple routing tables.
2034 See the man pages setfib(1) and setfib(2).
2035 This is a hopefully backwards compatible version,
2036 but to make use of it you need to compile your kernel
2037 with options ROUTETABLES=2 (or more up to 16).
2040 The 802.11 wireless support was redone to enable multi-bss
2041 operation on devices that are capable. The underlying device
2042 is no longer used directly but instead wlanX devices are
2043 cloned with ifconfig. This requires changes to rc.conf files.
2044 For example, change:
2045 ifconfig_ath0="WPA DHCP"
2048 ifconfig_wlan0="WPA DHCP"
2049 see rc.conf(5) for more details. In addition, mergemaster of
2050 /etc/rc.d is highly recommended. Simultaneous update of userland
2051 and kernel wouldn't hurt either.
2053 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2054 modules were merged into the base wlan module. All references
2055 to these modules (e.g. in kernel config files) must be removed.
2058 psm(4) has gained write(2) support in native operation level.
2059 Arbitrary commands can be written to /dev/psm%d and status can
2060 be read back from it. Therefore, an application is responsible
2061 for status validation and error recovery. It is a no-op in
2062 other operation levels.
2065 Support for KSE threading has been removed from the kernel. To
2066 run legacy applications linked against KSE libmap.conf may
2067 be used. The following libmap.conf may be used to ensure
2068 compatibility with any prior release:
2070 libpthread.so.1 libthr.so.1
2071 libpthread.so.2 libthr.so.2
2072 libkse.so.3 libthr.so.3
2075 The layout of struct vmspace has changed. This affects libkvm
2076 and any executables that link against libkvm and use the
2077 kvm_getprocs() function. In particular, but not exclusively,
2078 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2079 The effects are minimal, but it's advisable to upgrade world
2083 The latest em driver no longer has support in it for the
2084 82575 adapter, this is now moved to the igb driver. The
2085 split was done to make new features that are incompatible
2086 with older hardware easier to do.
2089 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2090 likewise the kernel option is now GEOM_LINUX_LVM.
2093 The default NFS mount mode has changed from UDP to TCP for
2094 increased reliability. If you rely on (insecurely) NFS
2095 mounting across a firewall you may need to update your
2099 Belatedly note the addition of m_collapse for compacting
2103 The fts(3) structures have been changed to use adequate
2104 integer types for their members and so to be able to cope
2105 with huge file trees. The old fts(3) ABI is preserved
2106 through symbol versioning in libc, so third-party binaries
2107 using fts(3) should still work, although they will not take
2108 advantage of the extended types. At the same time, some
2109 third-party software might fail to build after this change
2110 due to unportable assumptions made in its source code about
2111 fts(3) structure members. Such software should be fixed
2112 by its vendor or, in the worst case, in the ports tree.
2113 FreeBSD_version 800015 marks this change for the unlikely
2114 case that a portable fix is impossible.
2117 To upgrade to -current after this date, you must be running
2118 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2119 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2122 The ADAPTIVE_GIANT kernel option has been retired because its
2123 functionality is the default now.
2126 The AT keyboard emulation of sunkbd(4) has been turned on
2127 by default. In order to make the special symbols of the Sun
2128 keyboards driven by sunkbd(4) work under X these now have
2129 to be configured the same way as Sun USB keyboards driven
2130 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2132 Option "XkbLayout" "us"
2133 Option "XkbRules" "xorg"
2134 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2137 It has been decided that it is desirable to provide ABI
2138 backwards compatibility to the FreeBSD 4/5/6 versions of the
2139 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2140 broken with the introduction of PCI domain support (see the
2141 20070930 entry). Unfortunately, this required the ABI of
2142 PCIOCGETCONF to be broken again in order to be able to
2143 provide backwards compatibility to the old version of that
2144 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2145 again. As for prominent ports this affects neither pciutils
2146 nor xorg-server this time, the hal port needs to be rebuilt
2150 The misnamed kthread_create() and friends have been renamed
2151 to kproc_create() etc. Many of the callers already
2152 used kproc_start()..
2153 I will return kthread_create() and friends in a while
2154 with implementations that actually create threads, not procs.
2155 Renaming corresponds with version 800002.
2164 Avoid using make -j when upgrading. While generally safe, there are
2165 sometimes problems using -j to upgrade. If your upgrade fails with
2166 -j, please try again without -j. From time to time in the past there
2167 have been problems using -j with buildworld and/or installworld. This
2168 is especially true when upgrading between "distant" versions (eg one
2169 that cross a major release boundary or several minor releases, or when
2170 several months have passed on the -current branch).
2172 Sometimes, obscure build problems are the result of environment
2173 poisoning. This can happen because the make utility reads its
2174 environment when searching for values for global variables. To run
2175 your build attempts in an "environmental clean room", prefix all make
2176 commands with 'env -i '. See the env(1) manual page for more details.
2178 When upgrading from one major version to another it is generally best
2179 to upgrade to the latest code in the currently installed branch first,
2180 then do an upgrade to the new branch. This is the best-tested upgrade
2181 path, and has the highest probability of being successful. Please try
2182 this approach before reporting problems with a major version upgrade.
2184 When upgrading a live system, having a root shell around before
2185 installing anything can help undo problems. Not having a root shell
2186 around can lead to problems if pam has changed too much from your
2187 starting point to allow continued authentication after the upgrade.
2191 When upgrading the boot ZFS pool to a new version, always follow
2194 1.) recompile and reinstall the ZFS boot loader and boot block
2195 (this is part of "make buildworld" and "make installworld")
2197 2.) update the ZFS boot block on your boot drive
2199 The following example updates the ZFS boot block on the first
2200 partition (freebsd-boot) of a GPT partitioned drive ad0:
2201 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2203 Non-boot pools do not need these updates.
2207 If you are updating from a prior version of FreeBSD (even one just
2208 a few days old), you should follow this procedure. It is the most
2209 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2211 make kernel-toolchain
2212 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2213 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2215 To test a kernel once
2216 ---------------------
2217 If you just want to boot a kernel once (because you are not sure
2218 if it works, or if you want to boot a known bad kernel to provide
2219 debugging information) run
2220 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2221 nextboot -k testkernel
2223 To just build a kernel when you know that it won't mess you up
2224 --------------------------------------------------------------
2225 This assumes you are already running a CURRENT system. Replace
2226 ${arch} with the architecture of your machine (e.g. "i386",
2227 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2229 cd src/sys/${arch}/conf
2230 config KERNEL_NAME_HERE
2231 cd ../compile/KERNEL_NAME_HERE
2236 If this fails, go to the "To build a kernel" section.
2238 To rebuild everything and install it on the current system.
2239 -----------------------------------------------------------
2240 # Note: sometimes if you are running current you gotta do more than
2241 # is listed here if you are upgrading from a really old current.
2243 <make sure you have good level 0 dumps>
2245 make kernel KERNCONF=YOUR_KERNEL_HERE
2247 <reboot in single user> [3]
2254 To cross-install current onto a separate partition
2255 --------------------------------------------------
2256 # In this approach we use a separate partition to hold
2257 # current's root, 'usr', and 'var' directories. A partition
2258 # holding "/", "/usr" and "/var" should be about 2GB in
2261 <make sure you have good level 0 dumps>
2264 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2265 <maybe newfs current's root partition>
2266 <mount current's root partition on directory ${CURRENT_ROOT}>
2267 make installworld DESTDIR=${CURRENT_ROOT}
2268 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2269 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2270 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2271 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2272 <reboot into current>
2273 <do a "native" rebuild/install as described in the previous section>
2274 <maybe install compatibility libraries from ports/misc/compat*>
2278 To upgrade in-place from stable to current
2279 ----------------------------------------------
2280 <make sure you have good level 0 dumps>
2282 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2284 <reboot in single user> [3]
2291 Make sure that you've read the UPDATING file to understand the
2292 tweaks to various things you need. At this point in the life
2293 cycle of current, things change often and you are on your own
2294 to cope. The defaults can also change, so please read ALL of
2295 the UPDATING entries.
2297 Also, if you are tracking -current, you must be subscribed to
2298 freebsd-current@freebsd.org. Make sure that before you update
2299 your sources that you have read and understood all the recent
2300 messages there. If in doubt, please track -stable which has
2301 much fewer pitfalls.
2303 [1] If you have third party modules, such as vmware, you
2304 should disable them at this point so they don't crash your
2307 [3] From the bootblocks, boot -s, and then do
2312 adjkerntz -i # if CMOS is wall time
2313 Also, when doing a major release upgrade, it is required that
2314 you boot into single user mode to do the installworld.
2316 [4] Note: This step is non-optional. Failure to do this step
2317 can result in a significant reduction in the functionality of the
2318 system. Attempting to do it by hand is not recommended and those
2319 that pursue this avenue should read this file carefully, as well
2320 as the archives of freebsd-current and freebsd-hackers mailing lists
2321 for potential gotchas. The -U option is also useful to consider.
2322 See mergemaster(8) for more information.
2324 [5] Usually this step is a noop. However, from time to time
2325 you may need to do this if you get unknown user in the following
2326 step. It never hurts to do it all the time. You may need to
2327 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2328 install) after the buildworld before this step if you last updated
2329 from current before 20130425 or from -stable before 20130430.
2331 [6] This only deletes old files and directories. Old libraries
2332 can be deleted by "make delete-old-libs", but you have to make
2333 sure that no program is using those libraries anymore.
2335 [8] In order to have a kernel that can run the 4.x binaries needed to
2336 do an installworld, you must include the COMPAT_FREEBSD4 option in
2337 your kernel. Failure to do so may leave you with a system that is
2338 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2339 required to run the 5.x binaries on more recent kernels. And so on
2340 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2342 Make sure that you merge any new devices from GENERIC since the
2343 last time you updated your kernel config file.
2345 [9] When checking out sources, you must include the -P flag to have
2346 cvs prune empty directories.
2348 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2349 "?=" instead of the "=" assignment operator, so that buildworld can
2350 override the CPUTYPE if it needs to.
2352 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2353 not on the command line, or in /etc/make.conf. buildworld will
2354 warn if it is improperly defined.
2357 This file contains a list, in reverse chronological order, of major
2358 breakages in tracking -current. It is not guaranteed to be a complete
2359 list of such breakages, and only contains entries since October 10, 2007.
2360 If you need to see UPDATING entries from before that date, you will need
2361 to fetch an UPDATING file from an older FreeBSD release.
2363 Copyright information:
2365 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2367 Redistribution, publication, translation and use, with or without
2368 modification, in full or in part, in any form or format of this
2369 document are permitted without further permission from the author.
2371 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2372 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2373 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2374 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2375 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2376 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2377 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2378 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2379 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2380 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2381 POSSIBILITY OF SUCH DAMAGE.
2383 Contact Warner Losh if you have any questions about your use of