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 20161206 p13 FreeBSD-SA-16:36.telnetd
21 FreeBSD-SA-16:38.bhyve
22 FreeBSD-EN-16:19.tzcode
23 FreeBSD-EN-16:20.tzdata
25 Fix possible login(1) argument injection in telnetd(8). [SA-16:36]
26 Fix link_ntoa(3) buffer overflow in libc. [SA-16:37]
27 Fix possible escape from bhyve(8) virtual machine. [SA-16:38]
28 Fix warnings about valid time zone abbreviations. [EN-16:19]
29 Update timezone database information. [EN-16:20]
31 20161102 p12 FreeBSD-SA-16:33.openssh
32 FreeBSD-SA-16:35.openssl
34 Fix OpenSSH remote Denial of Service vulnerability. [SA-16:33]
36 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
38 20161025 p11 FreeBSD-SA-16:15.sysarch [revised]
41 Fix incorrect argument validation in sysarch(2). [SA-16:15]
42 Fix virtual memory subsystem bugs. [EN-16:17]
44 20161010 p10 FreeBSD-SA-16:29.bspatch
45 FreeBSD-SA-16:30.portsnap
46 FreeBSD-SA-16:31.libarchive
48 Fix bspatch heap overflow vulnerability. [SA-16:29]
50 Fix multiple portsnap vulnerabilities. [SA-16:30]
52 Fix multiple libarchive vulnerabilities. [SA-16:31]
54 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
56 Fix OpenSSL regression introduced in SA-16:26.
58 20160923 p8 FreeBSD-SA-16:26.openssl
60 Fix multiple OpenSSL vulnerabilitites.
62 20160811 p7 FreeBSD-EN-16:10.dhclient
63 FreeBSD-EN-16:11.vmbus
64 FreeBSD-EN-16:12.hv_storvsc
65 FreeBSD-EN-16:13.vmbus
66 FreeBSD-EN-16:14.hv_storvsc
67 FreeBSD-EN-16:15.vmbus
68 FreeBSD-EN-16:16.hv_storvsc
70 Fix handling of unknown options from a DHCP server. [EN-16:10]
71 Fix a panic in hv_vmbus(4). [EN-16:11]
72 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
73 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
74 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
75 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
76 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
78 20160725 p6 FreeBSD-SA-16:25.bspatch
79 FreeBSD-EN-16:09.freebsd-update
81 Fix bspatch heap overflow vulnerability. [SA-16:25]
83 Fix freebsd-update(8) support of FreeBSD 11.0 release
84 distribution. [EN-16:09]
86 20160604 p5 FreeBSD-SA-16:24.ntp
88 Fix multiple vulnerabilities of ntp.
90 20160531 p4 FreeBSD-SA-16:20.linux
91 FreeBSD-SA-16:21.43bsd
92 FreeBSD-SA-16:22.libarchive
94 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
95 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
96 Fix directory traversal in cpio(1). [SA-16:22]
99 20160517 p3 FreeBSD-SA-16:18.atkbd
100 FreeBSD-SA-16:19.sendmsg
102 Fix buffer overflow in keyboard driver. [SA-16:18]
104 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
106 20160504 p2 FreeBSD-SA-16:17.openssl
107 FreeBSD-EN-16:06.libc
111 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
113 Fix performance regression in libc hash(3). [EN-16:06]
115 Fix excessive latency in x86 IPI delivery. [EN-16:07]
117 Fix memory leak in ZFS. [EN-16:08]
119 20160429 p1 FreeBSD-SA-16:16.ntp
121 Fix multiple vulnerabilities of ntp.
127 The NONE and HPN patches has been removed from OpenSSH. They are
128 still available in the security/openssh-portable port.
131 r292223 changed the internal interface between the nfsd.ko and
132 nfscommon.ko modules. As such, they must both be upgraded to-gether.
133 __FreeBSD_version has been bumped because of this.
136 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
137 Kernel modules isp_2400_multi and isp_2500_multi were removed and
138 should be replaced with isp_2400 and isp_2500 modules respectively.
141 The menu.rc and loader.rc files will now be replaced during
142 upgrades. Please migrate local changes to menu.rc.local and
143 loader.rc.local instead.
146 NTP has been upgraded to 4.2.8p4.
149 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
150 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
151 and devel/kyua to version 0.20+ and adjust any calling code to work
152 with Kyuafile and kyua.
155 The polarity of Pulse Per Second (PPS) capture events with the
156 uart(4) driver has been corrected. Prior to this change the PPS
157 "assert" event corresponded to the trailing edge of a positive PPS
158 pulse and the "clear" event was the leading edge of the next pulse.
160 As the width of a PPS pulse in a typical GPS receiver is on the
161 order of 1 millisecond, most users will not notice any significant
162 difference with this change.
164 Anyone who has compensated for the historical polarity reversal by
165 configuring a negative offset equal to the pulse width will need to
166 remove that workaround.
169 From legacy ata(4) driver was removed support for SATA controllers
170 supported by more functional drivers ahci(4), siis(4) and mvs(4).
171 Kernel modules ataahci and ataadaptec were removed completely,
172 replaced by ahci and mvs modules respectively.
178 As ZFS requires more kernel stack pages than is the default on some
179 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
180 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
182 Please consider using 'options KSTACK_PAGES=X' where X is greater
183 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
186 The default Unbound configuration now enables remote control
187 using a local socket. Users who have already enabled the
188 local_unbound service should regenerate their configuration
189 by running "service local_unbound setup" as root.
192 An additional fix for the issue described in the 20150614 sendmail
193 entry below has been been committed in revision 284786.
196 The fix for the issue described in the 20150614 sendmail entry
197 below has been been committed in revision 284485. The work
198 around described in that entry is no longer needed unless the
199 default setting is overridden by a confDH_PARAMETERS configuration
200 setting of '5' or pointing to a 512 bit DH parameter file.
203 The import of openssl to address the FreeBSD-SA-15:10.openssl
204 security advisory includes a change which rejects handshakes
205 with DH parameters below 768 bits. sendmail releases prior
206 to 8.15.2 (not yet released), defaulted to a 512 bit
207 DH parameter setting for client connections. To work around
208 this interoperability, sendmail can be configured to use a
209 2048 bit DH parameter by:
211 1. Edit /etc/mail/`hostname`.mc
212 2. If a setting for confDH_PARAMETERS does not exist or
213 exists and is set to a string beginning with '5',
215 3. If a setting for confDH_PARAMETERS exists and is set to
216 a file path, create a new file with:
217 openssl dhparam -out /path/to/file 2048
218 4. Rebuild the .cf file:
219 cd /etc/mail/; make; make install
221 cd /etc/mail/; make restart
223 A sendmail patch is coming, at which time this file will be
227 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
228 defined in symlink(7); previously symlinks were silently ignored.
231 The const qualifier has been removed from iconv(3) to comply with
232 POSIX. The ports tree is aware of this from r384038 onwards.
235 At svn r275807, The default linux compat kernel ABI has been adjusted
236 to 2.6.18 in support of the linux-c6 compat ports infrastructure
237 update. If you wish to continue using the linux-f10 compat ports,
238 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
239 encouraged to update their linux-compat packages to linux-c6 during
240 their next update cycle.
242 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
245 pjdfstest has been integrated into kyua as an opt-in test suite.
246 Please see share/doc/pjdfstest/README for a more details on how to
253 The ofwfb driver, used to provide a graphics console on PowerPC when
254 using vt(4), no longer allows mmap() of all of physical memory. This
255 will prevent Xorg on PowerPC with some ATI graphics cards from
256 initializing properly unless x11-servers/xorg-server is updated to
260 The libatf-c and libatf-c++ major versions were downgraded to 0 and
261 1 respectively to match the upstream numbers. They were out of
262 sync because, when they were originally added to FreeBSD, the
263 upstream versions were not respected. These libraries are private
264 and not yet built by default, so renumbering them should be a
265 non-issue. However, unclean source trees will yield broken test
266 programs once the operator executes "make delete-old-libs" after a
269 Additionally, the atf-sh binary was made private by moving it into
270 /usr/libexec/. Already-built shell test programs will keep the
271 path to the old binary so they will break after "make delete-old"
274 If you are using WITH_TESTS=yes (not the default), wipe the object
275 tree and rebuild from scratch to prevent spurious test failures.
276 This is only needed once: the misnumbered libraries and misplaced
277 binaries have been added to OptionalObsoleteFiles.inc so they will
278 be removed during a clean upgrade.
281 The ixgbe tunables now match their sysctl counterparts, for example:
282 hw.ixgbe.enable_aim => hw.ix.enable_aim
283 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
286 The NFSv4.1 server committed by r269398 changes the internal
287 function call interfaces used between the NFS and krpc modules.
288 As such, __FreeBSD_version was bumped.
291 The default unbound configuration has been modified to address
292 issues with reverse lookups on networks that use private
293 address ranges. If you use the local_unbound service, run
294 "service local_unbound setup" as root to regenerate your
295 configuration, then "service local_unbound reload" to load the
299 It is no longer necessary to include the dwarf version in your DEBUG
300 options in your kernel config file. The bug that required it to be
301 placed in the config file has bene fixed. DEBUG should now just
302 contain -g. The build system will automatically update things
303 to do the right thing.
306 Several ABI breaking changes were merged to CTL and new iSCSI code.
307 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
308 iscsictl need to be rebuilt to work with a new kernel.
311 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
312 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
313 which differs from the behaviour controlled by this knob.)
316 On i386 and amd64 systems, the onifconsole flag is now set by default
317 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
318 as a login TTY if it is set in the bootloader as an active kernel
319 console. No changes in behavior should result otherwise. To revert to
320 the previous behavior, set ttyu0 to "off" in /etc/ttys.
323 Clang and llvm have been upgraded to 3.4.1 release.
326 Clang and llvm have been upgraded to 3.4 release.
329 If a Makefile in a tests/ directory was auto-generating a Kyuafile
330 instead of providing an explicit one, this would prevent such
331 Makefile from providing its own Kyuafile in the future during
332 NO_CLEAN builds. This has been fixed in the Makefiles but manual
333 intervention is needed to clean an objdir if you use NO_CLEAN:
334 # find /usr/obj -name Kyuafile | xargs rm -f
337 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
338 capability mode support. Please note that enabling the feature in
339 kernel is still highly recommended.
342 OpenSSH is now built with sandbox support, and will use sandbox as
343 the default privilege separation method. This requires Capsicum
344 capability mode support in kernel.
347 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
348 been deprecated and will not be part of FreeBSD 11.0 and later
349 releases. If you use this driver, please consider switching to
350 the nfe(4) driver instead.
356 The behavior of gss_pseudo_random() for the krb5 mechanism
357 has changed, for applications requesting a longer random string
358 than produced by the underlying enctype's pseudo-random() function.
359 In particular, the random string produced from a session key of
360 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
361 be different at the 17th octet and later, after this change.
362 The counter used in the PRF+ construction is now encoded as a
363 big-endian integer in accordance with RFC 4402.
364 __FreeBSD_version is bumped to 1000701.
367 The WITHOUT_ATF build knob has been removed and its functionality
368 has been subsumed into the more generic WITHOUT_TESTS. If you were
369 using the former to disable the build of the ATF libraries, you
370 should change your settings to use the latter.
373 The default version of mtree is nmtree which is obtained from
374 NetBSD. The output is generally the same, but may vary
375 slightly. If you found you need identical output adding
376 "-F freebsd9" to the command line should do the trick. For the
377 time being, the old mtree is available as fmtree.
380 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
381 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
382 1.1.4_8 and verify bsdyml not linked in, before running "make
384 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
386 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
389 The rc.d/jail script has been updated to support jail(8)
390 configuration file. The "jail_<jname>_*" rc.conf(5) variables
391 for per-jail configuration are automatically converted to
392 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
393 This is transparently backward compatible. See below about some
394 incompatibilities and rc.conf(5) manual page for more details.
396 These variables are now deprecated in favor of jail(8) configuration
397 file. One can use "rc.d/jail config <jname>" command to generate
398 a jail(8) configuration file in /var/run/jail.<jname>.conf without
399 running the jail(8) utility. The default pathname of the
400 configuration file is /etc/jail.conf and can be specified by
401 using $jail_conf or $jail_<jname>_conf variables.
403 Please note that jail_devfs_ruleset accepts an integer at
404 this moment. Please consider to rewrite the ruleset name
408 BIND has been removed from the base system. If all you need
409 is a local resolver, simply enable and start the local_unbound
410 service instead. Otherwise, several versions of BIND are
411 available in the ports tree. The dns/bind99 port is one example.
413 With this change, nslookup(1) and dig(1) are no longer in the base
414 system. Users should instead use host(1) and drill(1) which are
415 in the base system. Alternatively, nslookup and dig can
416 be obtained by installing the dns/bind-tools port.
419 With the addition of unbound(8), a new unbound user is now
420 required during installworld. "mergemaster -p" can be used to
421 add the user prior to installworld, as documented in the handbook.
424 OpenSSH is now built with DNSSEC support, and will by default
425 silently trust signed SSHFP records. This can be controlled with
426 the VerifyHostKeyDNS client configuration setting. DNSSEC support
427 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
430 The GNU Compiler Collection and C++ standard library (libstdc++)
431 are no longer built by default on platforms where clang is the system
432 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
436 The PROCDESC kernel option is now part of the GENERIC kernel
437 configuration and is required for the rwhod(8) to work.
438 If you are using custom kernel configuration, you should include
442 The API and ABI related to the Capsicum framework was modified
443 in backward incompatible way. The userland libraries and programs
444 have to be recompiled to work with the new kernel. This includes the
445 following libraries and programs, but the whole buildworld is
446 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
447 kdump, procstat, rwho, rwhod, uniq.
450 AES-NI intrinsic support has been added to gcc. The AES-NI module
451 has been updated to use this support. A new gcc is required to build
452 the aesni module on both i386 and amd64.
455 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
456 Thus "device padlock_rng" and "device rdrand_rng" should be
457 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
460 WITH_ICONV has been split into two feature sets. WITH_ICONV now
461 enables just the iconv* functionality and is now on by default.
462 WITH_LIBICONV_COMPAT enables the libiconv api and link time
463 compatability. Set WITHOUT_ICONV to build the old way.
464 If you have been using WITH_ICONV before, you will very likely
465 need to turn on WITH_LIBICONV_COMPAT.
468 INVARIANTS option now enables DEBUG for code with OpenSolaris and
469 Illumos origin, including ZFS. If you have INVARIANTS in your
470 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
472 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
473 locks if WITNESS option was set. Because that generated a lot of
474 witness(9) reports and all of them were believed to be false
475 positives, this is no longer done. New option OPENSOLARIS_WITNESS
476 can be used to achieve the previous behavior.
479 Timer values in IPv6 data structures now use time_uptime instead
480 of time_second. Although this is not a user-visible functional
481 change, userland utilities which directly use them---ndp(8),
482 rtadvd(8), and rtsold(8) in the base system---need to be updated
486 find -delete can now delete the pathnames given as arguments,
487 instead of only files found below them or if the pathname did
488 not contain any slashes. Formerly, the following error message
491 find: -delete: <path>: relative path potentially not safe
493 Deleting the pathnames given as arguments can be prevented
494 without error messages using -mindepth 1 or by changing
495 directory and passing "." as argument to find. This works in the
496 old as well as the new version of find.
499 Behavior of devfs rules path matching has been changed.
500 Pattern is now always matched against fully qualified devfs
501 path and slash characters must be explicitly matched by
502 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
503 subdirectories must be reviewed.
506 The default ARM ABI has changed to the ARM EABI. The old ABI is
507 incompatible with the ARM EABI and all programs and modules will
508 need to be rebuilt to work with a new kernel.
510 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
512 NOTE: Support for the old ABI will be removed in the future and
513 users are advised to upgrade.
516 pkg_install has been disconnected from the build if you really need it
517 you should add WITH_PKGTOOLS in your src.conf(5).
520 Most of network statistics structures were changed to be able
521 keep 64-bits counters. Thus all tools, that work with networking
522 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
525 Fix a bug that allowed a tracing process (e.g. gdb) to write
526 to a memory-mapped file in the traced process's address space
527 even if neither the traced process nor the tracing process had
528 write access to that file.
531 CVS has been removed from the base system. An exact copy
532 of the code is available from the devel/cvs port.
535 Some people report the following error after the switch to bmake:
537 make: illegal option -- J
538 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
540 *** [buildworld] Error code 2
542 this likely due to an old instance of make in
543 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
544 which src/Makefile will use that blindly, if it exists, so if
545 you see the above error:
547 rm -rf `make -V MAKEPATH`
552 Use bmake by default.
553 Whereas before one could choose to build with bmake via
554 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
555 make. The goal is to remove these knobs for 10-RELEASE.
557 It is worth noting that bmake (like gmake) treats the command
558 line as the unit of failure, rather than statements within the
559 command line. Thus '(cd some/where && dosomething)' is safer
560 than 'cd some/where; dosomething'. The '()' allows consistent
561 behavior in parallel build.
564 Fix a bug that allows NFS clients to issue READDIR on files.
567 The WITHOUT_IDEA option has been removed because
568 the IDEA patent expired.
571 The sysctl which controls TRIM support under ZFS has been renamed
572 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
576 The mergemaster command now uses the default MAKEOBJDIRPREFIX
577 rather than creating it's own in the temporary directory in
578 order allow access to bootstrapped versions of tools such as
579 install and mtree. When upgrading from version of FreeBSD where
580 the install command does not support -l, you will need to
581 install a new mergemaster command if mergemaster -p is required.
582 This can be accomplished with the command (cd src/usr.sbin/mergemaster
586 Legacy ATA stack, disabled and replaced by new CAM-based one since
587 FreeBSD 9.0, completely removed from the sources. Kernel modules
588 atadisk and atapi*, user-level tools atacontrol and burncd are
589 removed. Kernel option `options ATA_CAM` is now permanently enabled
593 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
594 and socketpair(2). Software, in particular Kerberos, may
595 automatically detect and use these during building. The resulting
596 binaries will not work on older kernels.
599 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
600 information, see the respective 20130304 entry).
603 Recent commits to callout(9) changed the size of struct callout,
604 so the KBI is probably heavily disturbed. Also, some functions
605 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
606 by macros. Every kernel module using it won't load, so rebuild
609 The ctl device has been re-enabled in GENERIC for i386 and amd64,
610 but does not initialize by default (because of the new CTL_DISABLE
611 option) to save memory. To re-enable it, remove the CTL_DISABLE
612 option from the kernel config file or set kern.cam.ctl.disable=0
613 in /boot/loader.conf.
616 The ctl device has been disabled in GENERIC for i386 and amd64.
617 This was done due to the extra memory being allocated at system
618 initialisation time by the ctl driver which was only used if
619 a CAM target device was created. This makes a FreeBSD system
620 unusable on 128MB or less of RAM.
623 A new compression method (lz4) has been merged to -HEAD. Please
624 refer to zpool-features(7) for more information.
626 Please refer to the "ZFS notes" section of this file for information
627 on upgrading boot ZFS pools.
630 A BSD-licensed patch(1) variant has been added and is installed
631 as bsdpatch, being the GNU version the default patch.
632 To inverse the logic and use the BSD-licensed one as default,
633 while having the GNU version installed as gnupatch, rebuild
634 and install world with the WITH_BSD_PATCH knob set.
637 Due to the use of the new -l option to install(1) during build
638 and install, you must take care not to directly set the INSTALL
639 make variable in your /etc/make.conf, /etc/src.conf, or on the
640 command line. If you wish to use the -C flag for all installs
641 you may be able to add INSTALL+=-C to /etc/make.conf or
645 The install(1) option -M has changed meaning and now takes an
646 argument that is a file or path to append logs to. In the
647 unlikely event that -M was the last option on the command line
648 and the command line contained at least two files and a target
649 directory the first file will have logs appended to it. The -M
650 option served little practical purpose in the last decade so its
651 use is expected to be extremely rare.
654 After switching to Clang as the default compiler some users of ZFS
655 on i386 systems started to experience stack overflow kernel panics.
656 Please consider using 'options KSTACK_PAGES=4' in such configurations.
659 GEOM_LABEL now mangles label names read from file system metadata.
660 Mangling affect labels containing spaces, non-printable characters,
661 '%' or '"'. Device names in /etc/fstab and other places may need to
665 By default, only the 10 most recent kernel dumps will be saved. To
666 restore the previous behaviour (no limit on the number of kernel dumps
667 stored in the dump directory) add the following line to /etc/rc.conf:
672 With the addition of auditdistd(8), a new auditdistd user is now
673 required during installworld. "mergemaster -p" can be used to
674 add the user prior to installworld, as documented in the handbook.
677 The sin6_scope_id member variable in struct sockaddr_in6 is now
678 filled by the kernel before passing the structure to the userland via
679 sysctl or routing socket. This means the KAME-specific embedded scope
680 id in sin6_addr.s6_addr[2] is always cleared in userland application.
681 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
682 __FreeBSD_version is bumped to 1000025.
685 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
686 This means that the world and kernel will be compiled with clang
687 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
688 and /usr/bin/cpp. To disable this behavior and revert to building
689 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
690 of current may need to bootstrap WITHOUT_CLANG first if the clang
691 build fails (its compatibility window doesn't extend to the 9 stable
695 The IPFIREWALL_FORWARD kernel option has been removed. Its
696 functionality now turned on by default.
699 The ZERO_COPY_SOCKET kernel option has been removed and
700 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
701 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
702 mechanism which is not safe and may result in kernel crashes.
703 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
704 driver supports disposeable external page sized mbuf storage.
705 Proper replacements for both zero-copy mechanisms are under
706 consideration and will eventually lead to complete removal
707 of the two kernel options.
710 The IPv4 network stack has been converted to network byte
711 order. The following modules need to be recompiled together
712 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
713 pf(4), ipfw(4), ng_ipfw(4), stf(4).
716 Support for non-MPSAFE filesystems was removed from VFS. The
717 VFS_VERSION was bumped, all filesystem modules shall be
721 All the non-MPSAFE filesystems have been disconnected from
722 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
723 portalfs, smbfs, xfs.
726 The interface cloning API and ABI has changed. The following
727 modules need to be recompiled together with kernel:
728 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
729 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
730 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
733 The sdhci driver was split in two parts: sdhci (generic SD Host
734 Controller logic) and sdhci_pci (actual hardware driver).
735 No kernel config modifications are required, but if you
736 load sdhc as a module you must switch to sdhci_pci instead.
739 Import the FUSE kernel and userland support into base system.
742 The GNU sort(1) program has been removed since the BSD-licensed
743 sort(1) has been the default for quite some time and no serious
744 problems have been reported. The corresponding WITH_GNU_SORT
748 The pfil(9) API/ABI for AF_INET family has been changed. Packet
749 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
753 The net80211(4) ABI has been changed to allow for improved driver
754 PS-POLL and power-save support. All wireless drivers need to be
755 recompiled to work with the new kernel.
758 The random(4) support for the VIA hardware random number
759 generator (`PADLOCK') is no longer enabled unconditionally.
760 Add the padlock_rng device in the custom kernel config if
761 needed. The GENERIC kernels on i386 and amd64 do include the
762 device, so the change only affects the custom kernel
766 The pf(4) packet filter ABI has been changed. pfctl(8) and
767 snmp_pf module need to be recompiled to work with new kernel.
770 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
771 to -HEAD. Pools that have empty_bpobj in active state can not be
772 imported read-write with ZFS implementations that do not support
773 this feature. For more information read the zpool-features(5)
777 The sparc64 ZFS loader has been changed to no longer try to auto-
778 detect ZFS providers based on diskN aliases but now requires these
779 to be explicitly listed in the OFW boot-device environment variable.
782 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
783 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
784 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
787 The following sysctls and tunables have been renamed for consistency
788 with other variables:
789 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
790 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
793 The sort utility has been replaced with BSD sort. For now, GNU sort
794 is also available as "gnusort" or the default can be set back to
795 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
796 installed as "bsdsort".
799 A new version of ZFS (pool version 5000) has been merged to -HEAD.
800 Starting with this version the old system of ZFS pool versioning
801 is superseded by "feature flags". This concept enables forward
802 compatibility against certain future changes in functionality of ZFS
803 pools. The first read-only compatible "feature flag" for ZFS pools
804 is named "com.delphix:async_destroy". For more information
805 read the new zpool-features(5) manual page.
806 Please refer to the "ZFS notes" section of this file for information
807 on upgrading boot ZFS pools.
810 The malloc(3) implementation embedded in libc now uses sources imported
811 as contrib/jemalloc. The most disruptive API change is to
812 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
813 delete it prior to installworld, and optionally re-create it using the
814 new format after rebooting. See malloc.conf(5) for details
815 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
819 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
820 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
821 now spelled mips. This is to aid compatibility with third-party
822 software that expects this naming scheme in uname(3). Little-endian
823 settings are unchanged. If you are updating a big-endian mips64 machine
824 from before this change, you may need to set MACHINE_ARCH=mips64 in
825 your environment before the new build system will recognize your machine.
828 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
832 Now unix domain sockets behave "as expected" on nullfs(5). Previously
833 nullfs(5) did not pass through all behaviours to the underlying layer,
834 as a result if we bound to a socket on the lower layer we could connect
835 only to the lower path; if we bound to the upper layer we could connect
836 only to the upper path. The new behavior is one can connect to both the
837 lower and the upper paths regardless what layer path one binds to.
840 The getifaddrs upgrade path broken with 20111215 has been restored.
841 If you have upgraded in between 20111215 and 20120209 you need to
842 recompile libc again with your kernel. You still need to recompile
843 world to be able to configure CARP but this restriction already
847 The set_rcvar() function has been removed from /etc/rc.subr. All
848 base and ports rc.d scripts have been updated, so if you have a
849 port installed with a script in /usr/local/etc/rc.d you can either
850 hand-edit the rcvar= line, or reinstall the port.
852 An easy way to handle the mass-update of /etc/rc.d:
853 rm /etc/rc.d/* && mergemaster -i
856 panic(9) now stops other CPUs in the SMP systems, disables interrupts
857 on the current CPU and prevents other threads from running.
858 This behavior can be reverted using the kern.stop_scheduler_on_panic
860 The new behavior can be incompatible with kern.sync_on_panic.
863 The carp(4) facility has been changed significantly. Configuration
864 of the CARP protocol via ifconfig(8) has changed, as well as format
865 of CARP events submitted to devd(8) has changed. See manual pages
866 for more information. The arpbalance feature of carp(4) is currently
867 not supported anymore.
869 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
870 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
871 need to be recompiled.
874 The acpi_wmi(4) status device /dev/wmistat has been renamed to
878 The option VFS_ALLOW_NONMPSAFE option has been added in order to
879 explicitely support non-MPSAFE filesystems.
880 It is on by default for all supported platform at this present
884 The broken amd(4) driver has been replaced with esp(4) in the amd64,
885 i386 and pc98 GENERIC kernel configuration files.
888 sysinstall has been removed
891 The stable/9 branch created in subversion. This corresponds to the
892 RELENG_9 branch in CVS.
895 This commit modifies vfs_register() so that it uses a hash
896 calculation to set vfc_typenum, which is enabled by default.
897 The first time a system is booted after this change, the
898 vfc_typenum values will change for all file systems. The
899 main effect of this is a change to the NFS server file handles
900 for file systems that use vfc_typenum in their fsid, such as ZFS.
901 It will, however, prevent vfc_typenum from changing when file
902 systems are loaded in a different order for subsequent reboots.
903 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
904 until you are ready to remount all NFS clients after a reboot.
907 Bump the shared library version numbers for libraries that
908 do not use symbol versioning, have changed the ABI compared
909 to stable/8 and which shared library version was not bumped.
910 Done as part of 9.0-RELEASE cycle.
913 During the merge of Capsicum features, the fget(9) KPI was modified.
914 This may require the rebuilding of out-of-tree device drivers --
915 issues have been reported specifically with the nVidia device driver.
916 __FreeBSD_version is bumped to 900041.
918 Also, there is a period between 20110811 and 20110814 where the
919 special devices /dev/{stdin,stdout,stderr} did not work correctly.
920 Building world from a kernel during that window may not work.
923 The packet filter (pf) code has been updated to OpenBSD 4.5.
924 You need to update userland tools to be in sync with kernel.
925 This update breaks backward compatibility with earlier pfsync(4)
926 versions. Care must be taken when updating redundant firewall setups.
929 The following sysctls and tunables are retired on x86 platforms:
931 machdep.hlt_logical_cpus
932 The following sysctl is retired:
933 machdep.hyperthreading_allowed
934 The sysctls were supposed to provide a way to dynamically offline and
935 online selected CPUs on x86 platforms, but the implementation has not
936 been reliable especially with SCHED_ULE scheduler.
937 machdep.hyperthreading_allowed tunable is still available to ignore
938 hyperthreading CPUs at OS level.
939 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
940 where X is an APIC ID of a CPU. Be advised, though, that disabling
941 CPUs in non-uniform fashion will result in non-uniform topology and
942 may lead to sub-optimal system performance with SCHED_ULE, which is
946 cpumask_t type is retired and cpuset_t is used in order to describe
950 Changes to ifconfig(8) for dynamic address family detection mandate
951 that you are running a kernel of 20110525 or later. Make sure to
952 follow the update procedure to boot a new kernel before installing
956 Support for sun4v architecture is officially dropped
959 Several KPI breaking changes have been committed to the mii(4) layer,
960 the PHY drivers and consequently some Ethernet drivers using mii(4).
961 This means that miibus.ko and the modules of the affected Ethernet
962 drivers need to be recompiled.
964 Note to kernel developers: Given that the OUI bit reversion problem
965 was fixed as part of these changes all mii(4) commits related to OUIs,
966 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
967 handling, no longer can be merged verbatim to stable/8 and previous
971 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
972 into their kernel configurations along with 'device pci'.
975 The default NFS client is now the new NFS client, so fstype "newnfs"
976 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
977 Although mounts via fstype "nfs" will usually work without userland
978 changes, it is recommended that the mount(8) and mount_nfs(8)
979 commands be rebuilt from sources and that a link to mount_nfs called
980 mount_oldnfs be created. The new client is compiled into the
981 kernel with "options NFSCL" and this is needed for diskless root
982 file systems. The GENERIC kernel configs have been changed to use
983 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
984 To use the regular/old client, you can "mount -t oldnfs ...". For
985 a diskless root file system, you must also include a line like:
987 vfs.root.mountfrom="oldnfs:"
989 in the boot/loader.conf on the root fs on the NFS server to make
990 a diskless root fs use the old client.
993 The GENERIC kernels for all architectures now default to the new
994 CAM-based ATA stack. It means that all legacy ATA drivers were
995 removed and replaced by respective CAM drivers. If you are using
996 ATA device names in /etc/fstab or other places, make sure to update
997 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
998 where 'Y's are the sequential numbers starting from zero for each type
999 in order of detection, unless configured otherwise with tunables,
1000 see cam(4)). There will be symbolic links created in /dev/ to map
1001 old adX devices to the respective adaY. They should provide basic
1002 compatibility for file systems mounting in most cases, but they do
1003 not support old user-level APIs and do not have respective providers
1004 in GEOM. Consider using updated management tools with new device names.
1006 It is possible to load devices ahci, ata, siis and mvs as modules,
1007 but option ATA_CAM should remain in kernel configuration to make ata
1008 module work as CAM driver supporting legacy ATA controllers. Device ata
1009 still can be used in modular fashion (atacore + ...). Modules atadisk
1010 and atapi* are not used and won't affect operation in ATA_CAM mode.
1011 Note that to use CAM-based ATA kernel should include CAM devices
1012 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1013 them are parts of the cam module.
1015 ataraid(4) functionality is now supported by the RAID GEOM class.
1016 To use it you can load geom_raid kernel module and use graid(8) tool
1017 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1019 No kernel config options or code have been removed, so if a problem
1020 arises, please report it and optionally revert to the old ATA stack.
1021 In order to do it you can remove from the kernel config:
1026 , and instead add back:
1027 device atadisk # ATA disk drives
1028 device ataraid # ATA RAID drives
1029 device atapicd # ATAPI CDROM drives
1030 device atapifd # ATAPI floppy drives
1031 device atapist # ATAPI tape drives
1034 The default NFS server has been changed to the new server, which
1035 was referred to as the experimental server. If you need to switch
1036 back to the old NFS server, you must now put the "-o" option on
1037 both the mountd and nfsd commands. This can be done using the
1038 mountd_flags and nfs_server_flags rc.conf variables until an
1039 update to the rc scripts is committed, which is coming soon.
1042 The GNU Objective-C runtime library (libobjc), and other Objective-C
1043 related components have been removed from the base system. If you
1044 require an Objective-C library, please use one of the available ports.
1047 ath(4) has been split into bus- and device- modules. if_ath contains
1048 the HAL, the TX rate control and the network device code. if_ath_pci
1049 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1050 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1051 in order to use ath on everything else.
1053 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1054 need to load if_ath and if_ath_pci for ath(4) operation.
1057 As part of the replacement of sysinstall, the process of building
1058 release media has changed significantly. For details, please re-read
1059 release(7), which has been updated to reflect the new build process.
1062 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1063 is the last available version under GPLv2. It brings a number of new
1064 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1065 4.1 and SSE 4.2), better support for powerpc64, a number of new
1066 directives, and lots of other small improvements. See the ChangeLog
1067 file in contrib/binutils for the full details.
1070 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1071 compliant, and will now use half of hash for authentication.
1072 This will break interoperability with all stacks (including all
1073 actual FreeBSD versions) who implement
1074 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1076 The only workaround with such peers is to use another HMAC
1077 algorithm for IPsec ("phase 2") authentication.
1080 Remove the uio_yield prototype and symbol. This function has
1081 been misnamed since it was introduced and should not be
1082 globally exposed with this name. The equivalent functionality
1083 is now available using kern_yield(curthread->td_user_pri).
1084 The function remains undocumented.
1087 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1088 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1089 for scalar sysctls is defined but disabled. Code that needs
1090 UQUAD to pass the type checking that must compile on older
1091 systems where the define is not present can check against
1092 __FreeBSD_version >= 900030.
1094 The system dialog(1) has been replaced with a new version previously
1095 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1096 with the previous version, but the libdialog associated with it has
1097 a largely incompatible API. As such, the original version of libdialog
1098 will be kept temporarily as libodialog, until its base system consumers
1099 are replaced or updated. Bump __FreeBSD_version to 900030.
1102 If you are trying to run make universe on a -stable system, and you get
1103 the following warning:
1104 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1105 unknown. config(8) likely too old."
1106 or something similar to it, then you must upgrade your -stable system
1107 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1108 stable/8) or build the config from the latest stable/8 branch and
1109 install it on your system.
1111 Prior to this date, building a current universe on 8-stable system from
1112 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1113 error in the first kernel build phase. A new config on those old
1114 systems will fix that problem for older versions of -current.
1117 The TCP stack has been modified to allow Khelp modules to interact with
1118 it via helper hook points and store per-connection data in the TCP
1119 control block. Bump __FreeBSD_version to 900029. User space tools that
1120 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1124 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1125 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1126 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1127 to take advantage of it instead of using custom implementations. This
1128 means that these drivers now no longer unconditionally advertise
1129 support for flow control but only do so if flow control is a selected
1130 media option. This was implemented in the generic support that way in
1131 order to allow flow control to be switched on and off via ifconfig(8)
1132 with the PHY specific default to typically off in order to protect
1133 from unwanted effects. Consequently, if you used flow control with
1134 one of the above mentioned drivers you now need to explicitly enable
1135 it, for example via:
1136 ifconfig bge0 media auto mediaopt flowcontrol
1138 Along with the above mentioned changes generic support for setting
1139 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1140 e1000phy(4) as well as ip1000phy(4) have been converted to take
1141 advantage of it. This means that these drivers now no longer take the
1142 link0 parameter for selecting master mode but the master media option
1143 has to be used instead, for example like in the following:
1144 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1146 Selection of master mode now is also available with all other PHY
1147 drivers supporting 1000baseT.
1150 The TCP stack has received a significant update to add support for
1151 modularised congestion control and generally improve the clarity of
1152 congestion control decisions. Bump __FreeBSD_version to 900025. User
1153 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1154 sockstat) need to be recompiled.
1157 The man(1) utility has been replaced by a new version that no longer
1158 uses /etc/manpath.config. Please consult man.conf(5) for how to
1159 migrate local entries to the new format.
1162 The copyright strings printed by login(1) and sshd(8) at the time of a
1163 new connection have been removed to follow other operating systems and
1167 A workaround for a fixed ld bug has been removed in kernel code,
1168 so make sure that your system ld is built from sources after
1169 revision 210245 from 2010-07-19 (r211583 if building head kernel
1170 on stable/8, r211584 for stable/7; both from 2010-08-21).
1171 A symptom of incorrect ld version is different addresses for
1172 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1175 The $ipv6_prefer variable in rc.conf(5) has been split into
1176 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1178 The $ip6addrctl_policy is a variable to choose a pre-defined
1179 address selection policy set by ip6addrctl(8). A value
1180 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1183 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1184 flag (see an entry of 20090926) is set on an interface with no
1185 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1186 security reason. If you want IPv6 link-local address on all
1187 interfaces by default, set this to "YES".
1189 The old ipv6_prefer="YES" is equivalent to
1190 ipv6_activate_all_interfaces="YES" and
1191 ip6addrctl_policy="ipv6_prefer".
1194 DTrace has grown support for userland tracing. Due to this, DTrace is
1195 now i386 and amd64 only.
1196 dtruss(1) is now installed by default on those systems and a new
1197 kernel module is needed for userland tracing: fasttrap.
1198 No changes to your kernel config file are necessary to enable
1199 userland tracing, but you might consider adding 'STRIP=' and
1200 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1201 to have informative userland stack traces in DTrace (ustack).
1204 The acpi_aiboost(4) driver has been removed in favor of the new
1205 aibs(4) driver. You should update your kernel configuration file.
1208 BSD grep has been imported to the base system and it is built by
1209 default. It is completely BSD licensed, highly GNU-compatible, uses
1210 less memory than its GNU counterpart and has a small codebase.
1211 However, it is slower than its GNU counterpart, which is mostly
1212 noticeable for larger searches, for smaller ones it is measurable
1213 but not significant. The reason is complex, the most important factor
1214 is that we lack a modern and efficient regex library and GNU
1215 overcomes this by optimizing the searches internally. Future work
1216 on improving the regex performance is planned, for the meantime,
1217 users that need better performance, can build GNU grep instead by
1218 setting the WITH_GNU_GREP knob.
1221 Due to the import of powerpc64 support, all existing powerpc kernel
1222 configuration files must be updated with a machine directive like this:
1223 machine powerpc powerpc
1225 In addition, an updated config(8) is required to build powerpc kernels
1229 A new version of ZFS (version 15) has been merged to -HEAD.
1230 This version uses a python library for the following subcommands:
1231 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1232 For full functionality of these commands the following port must
1233 be installed: sysutils/py-zfs
1236 'vm_page's are now hashed by physical address to an array of mutexes.
1237 Currently this is only used to serialize access to hold_count. Over
1238 time the page queue mutex will be peeled away. This changes the size
1239 of pmap on every architecture. And requires all callers of vm_page_hold
1240 and vm_page_unhold to be updated.
1243 WITH_CTF can now be specified in src.conf (not recommended, there
1244 are some problems with static executables), make.conf (would also
1245 affect ports which do not use GNU make and do not override the
1246 compile targets) or in the kernel config (via "makeoptions
1248 When WITH_CTF was specified there before this was silently ignored,
1249 so make sure that WITH_CTF is not used in places which could lead
1250 to unwanted behavior.
1253 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1254 to allow 32-bit compatibility on non-x86 platforms. All kernel
1255 configurations on amd64 and ia64 platforms using these options must
1256 be modified accordingly.
1259 The utmp user accounting database has been replaced with utmpx,
1260 the user accounting interface standardized by POSIX.
1261 Unfortunately the semantics of utmp and utmpx don't match,
1262 making it practically impossible to support both interfaces.
1263 The user accounting database is used by tools like finger(1),
1264 last(1), talk(1), w(1) and ac(8).
1266 All applications in the base system use utmpx. This means only
1267 local binaries (e.g. from the ports tree) may still use these
1268 utmp database files. These applications must be rebuilt to make
1271 After the system has been upgraded, it is safe to remove the old
1272 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1273 assuming their contents is of no importance anymore. Old wtmp
1274 databases can only be used by last(1) and ac(8) after they have
1275 been converted to the new format using wtmpcvt(1).
1278 Introduce the kernel thread "deadlock resolver" (which can be enabled
1279 via the DEADLKRES option, see NOTES for more details) and the
1280 sleepq_type() function for sleepqueues.
1283 The rc.firewall and rc.firewall6 were unified, and
1284 rc.firewall6 and rc.d/ip6fw were removed.
1285 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1286 variables are obsoleted. Instead, the following new rc
1287 variables are added to rc.d/ipfw:
1289 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1290 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1291 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1293 The meanings correspond to the relevant IPv4 variables.
1299 The default terminal emulation for syscons(4) has been changed
1300 from cons25 to xterm on all platforms except pc98. This means
1301 that the /etc/ttys file needs to be updated to ensure correct
1302 operation of applications on the console.
1304 The terminal emulation style can be toggled per window by using
1305 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1306 options can be used to change the compile-time default back to
1309 To prevent graphical artifacts, make sure the TERM environment
1310 variable is set to match the terminal emulation that is being
1311 performed by syscons(4).
1314 The layout of the structure ieee80211req_scan_result has changed.
1315 Applications that require wireless scan results (e.g. ifconfig(8))
1316 from net80211 need to be recompiled.
1318 Applications such as wpa_supplicant(8) may require a full world
1319 build without using NO_CLEAN in order to get synchronized with the
1323 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1324 There's one kernel module for each firmware. Adding "device iwnfw"
1325 to the kernel configuration file means including all three firmware
1326 images inside the kernel. If you want to include just the one for
1327 your wireless card, use the devices iwn4965fw, iwn5000fw or
1331 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1332 into rc.d/netif. The changes are the following:
1334 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1335 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1336 Note that both variables need the "inet6" keyword at the head.
1338 Do not set $ipv6_network_interfaces manually if you do not
1339 understand what you are doing. It is not needed in most cases.
1341 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1344 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1345 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1347 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1348 all configured interfaces have "inet6 accept_rtadv" in the
1349 $ifconfig_IF_ipv6. These are for backward compatibility.
1351 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1352 functionality of interfaces with no corresponding
1353 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1354 and the default address selection policy of ip6addrctl(8)
1355 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1356 Note that if you want to configure IPv6 functionality on the
1357 disabled interfaces after boot, first you need to clear the flag by
1358 using ifconfig(8) like:
1360 ifconfig em0 inet6 -ifdisabled
1362 If YES, the default address selection policy is set as
1365 The default value of $ipv6_prefer is NO.
1367 4. If your system need to receive Router Advertisement messages,
1368 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1369 scripts automatically invoke rtsol(8) when the interface becomes
1370 UP. The Router Advertisement messages are used for SLAAC
1371 (State-Less Address AutoConfiguration).
1374 802.11s D3.03 support was committed. This is incompatible with the
1375 previous code, which was based on D3.0.
1378 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1379 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1380 control whether accepting Router Advertisement messages or not.
1381 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1382 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1383 The ifconfig(8) utility now supports these flags.
1386 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1387 mount(8) and -a option for df(1) to see them.
1390 The old tunable hw.bus.devctl_disable has been superseded by
1391 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1392 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1396 Remove the option STOP_NMI. The default action is now to use NMI only
1397 for KDB via the newly introduced function stop_cpus_hard() and
1398 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1401 The stable/8 branch created in subversion. This corresponds to the
1402 RELENG_8 branch in CVS.
1405 Bump the shared library version numbers for all libraries that do not
1406 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1407 __FreeBSD_version to 800105.
1410 Due to changes in the implementation of virtual network stack support,
1411 all network-related kernel modules must be recompiled. As this change
1412 breaks the ABI, bump __FreeBSD_version to 800104.
1415 The TOE interface to the TCP syncache has been modified to remove
1416 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1417 The cxgb driver is the only TOE consumer affected by this change, and
1418 needs to be recompiled along with the kernel. As this change breaks
1419 the ABI, bump __FreeBSD_version to 800103.
1422 Padding has been added to struct tcpcb, sackhint and tcpstat in
1423 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1424 maintaining the ABI. However, this change breaks the ABI, so bump
1425 __FreeBSD_version to 800102. User space tools that rely on the size of
1426 any of these structs (e.g. sockstat) need to be recompiled.
1429 The NFS_LEGACYRPC option has been removed along with the old kernel
1430 RPC implementation that this option selected. Kernel configurations
1431 may need to be adjusted.
1434 The network interface device nodes at /dev/net/<interface> have been
1435 removed. All ioctl operations can be performed the normal way using
1436 routing sockets. The kqueue functionality can generally be replaced
1437 with routing sockets.
1440 The documentation from the FreeBSD Documentation Project (Handbook,
1441 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1442 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1445 The ABI of various structures related to the SYSV IPC API have been
1446 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1447 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1451 Layout of struct vnet has changed as routing related variables were
1452 moved to their own Vimage module. Modules need to be recompiled. Bump
1453 __FreeBSD_version to 800099.
1456 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1457 respectively. As long as no more than 16 groups per process are used,
1458 no changes should be visible. When more than 16 groups are used, old
1459 binaries may fail if they call getgroups() or getgrouplist() with
1460 statically sized storage. Recompiling will work around this, but
1461 applications should be modified to use dynamically allocated storage
1462 for group arrays as POSIX.1-2008 does not cap an implementation's
1463 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1465 NFS and portalfs mounts may also be affected as the list of groups is
1466 truncated to 16. Users of NFS who use more than 16 groups, should
1467 take care that negative group permissions are not used on the exported
1468 file systems as they will not be reliable unless a GSSAPI based
1469 authentication method is used.
1472 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1473 option compiles in the support for adaptive spinning for lockmgrs
1474 which want to enable it. The lockinit() function now accepts the flag
1475 LK_ADAPTIVE in order to make the lock object subject to adaptive
1476 spinning when both held in write and read mode.
1479 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1480 changed. User applications that use this ioctl need to be rebuilt.
1483 The layout of struct thread has changed. Kernel and modules need to
1487 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1488 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1491 window(1) has been removed from the base system. It can now be
1492 installed from ports. The port is called misc/window.
1495 The way we are storing and accessing `routing table' entries has
1496 changed. Programs reading the FIB, like netstat, need to be
1500 A new netisr implementation has been added for FreeBSD 8. Network
1501 file system modules, such as igmp, ipdivert, and others, should be
1503 Bump __FreeBSD_version to 800096.
1506 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1510 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1511 Bump __FreeBSD_version to 800094.
1514 Add mnt_xflag field to 'struct mount'. File system modules need to be
1516 Bump __FreeBSD_version to 800093.
1519 The compiling option ADAPTIVE_SX has been retired while it has been
1520 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1521 The KPI for sx_init_flags() changes as accepting flags:
1522 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1523 been introduced in order to handle the reversed logic.
1524 Bump __FreeBSD_version to 800092.
1527 Add support for hierarchical jails. Remove global securelevel.
1528 Bump __FreeBSD_version to 800091.
1531 The layout of struct vnet_net has changed, therefore modules
1533 Bump __FreeBSD_version to 800090.
1536 The newly imported zic(8) produces a new format in the output. Please
1537 run tzsetup(8) to install the newly created data to /etc/localtime.
1540 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1541 hw.usb.* and is now consistent again with previous releases.
1544 802.11 monitor mode support was revised and driver api's were changed.
1545 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1546 of DLT_IEEE802_11. No user-visible data structures were changed but
1547 applications that use DLT_IEEE802_11 may require changes.
1548 Bump __FreeBSD_version to 800088.
1551 The layout of the following structs has changed: sysctl_oid,
1552 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1553 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1554 panics may be experienced. World rebuild is required for
1555 correctly checking networking state from userland.
1556 Bump __FreeBSD_version to 800085.
1559 MLDv2 and Source-Specific Multicast (SSM) have been merged
1560 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1561 The implementation of SSM within FreeBSD's IPv6 stack closely
1562 follows the IPv4 implementation.
1564 For kernel developers:
1566 * The most important changes are that the ip6_output() and
1567 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1568 and this lock has been downgraded to a non-recursive mutex.
1570 * As with the changes to the IPv4 stack to support SSM, filtering
1571 of inbound multicast traffic must now be performed by transport
1572 protocols within the IPv6 stack. This does not apply to TCP and
1573 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1575 * The KPIs used by IPv6 multicast are similar to those used by
1576 the IPv4 stack, with the following differences:
1577 * im6o_mc_filter() is analogous to imo_multicast_filter().
1578 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1579 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1580 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1581 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1582 for MLDv1 have an additional 'timer' argument which is used to
1583 jitter the initial membership report for the solicited-node
1584 multicast membership on-link.
1585 * This is not strictly needed for MLDv2, which already jitters
1586 its report transmissions. However, the 'timer' argument is
1587 preserved in case MLDv1 is active on the interface.
1589 * The KAME linked-list based IPv6 membership implementation has
1590 been refactored to use a vector similar to that used by the IPv4
1592 Code which maintains a list of its own multicast memberships
1593 internally, e.g. carp, has been updated to reflect the new
1596 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1597 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1598 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1599 implementation constraint which needs to be addressed in HEAD.
1601 For application developers:
1603 * The changes are broadly similar to those made for the IPv4
1606 * The use of IPv4 and IPv6 multicast socket options on the same
1607 socket, using mapped addresses, HAS NOT been tested or supported.
1609 * There are a number of issues with the implementation of various
1610 IPv6 multicast APIs which need to be resolved in the API surface
1611 before the implementation is fully compatible with KAME userland
1612 use, and these are mostly to do with interface index treatment.
1614 * The literature available discusses the use of either the delta / ASM
1615 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1616 using setsourcefilter(3)/getsourcefilter(3). For more information
1617 please refer to RFC 3768, 'Socket Interface Extensions for
1618 Multicast Source Filters'.
1620 * Applications which use the published RFC 3678 APIs should be fine.
1622 For systems administrators:
1624 * The mtest(8) utility has been refactored to support IPv6, in
1625 addition to IPv4. Interface addresses are no longer accepted
1626 as arguments, their names must be used instead. The utility
1627 will map the interface name to its first IPv4 address as
1628 returned by getifaddrs(3).
1630 * The ifmcstat(8) utility has also been updated to print the MLDv2
1631 endpoint state and source filter lists via sysctl(3).
1633 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1634 loopback of IPv6 multicast datagrams by default; it defaults to 1
1635 to preserve the existing behaviour. Disabling multicast loopback is
1636 recommended for optimal system performance.
1638 * The IPv6 MROUTING code has been changed to examine this sysctl
1639 instead of attempting to perform a group lookup before looping
1640 back forwarded datagrams.
1642 Bump __FreeBSD_version to 800084.
1645 Implement low-level Bluetooth HCI API.
1646 Bump __FreeBSD_version to 800083.
1649 The layout of struct malloc_type, used by modules to register new
1650 memory allocation types, has changed. Most modules will need to
1651 be rebuilt or panics may be experienced.
1652 Bump __FreeBSD_version to 800081.
1655 Anticipate overflowing inp_flags - add inp_flags2.
1656 This changes most offsets in inpcb, so checking v4 connection
1657 state will require a world rebuild.
1658 Bump __FreeBSD_version to 800080.
1661 Add an llentry to struct route and struct route_in6. Modules
1662 embedding a struct route will need to be recompiled.
1663 Bump __FreeBSD_version to 800079.
1666 The size of rt_metrics_lite and by extension rtentry has changed.
1667 Networking administration apps will need to be recompiled.
1668 The route command now supports show as an alias for get, weighting
1669 of routes, sticky and nostick flags to alter the behavior of stateful
1671 Bump __FreeBSD_version to 800078.
1674 Do not use Giant for kbdmux(4) locking. This is wrong and
1675 apparently causing more problems than it solves. This will
1676 re-open the issue where interrupt handlers may race with
1677 kbdmux(4) in polling mode. Typical symptoms include (but
1678 not limited to) duplicated and/or missing characters when
1679 low level console functions (such as gets) are used while
1680 interrupts are enabled (for example geli password prompt,
1681 mountroot prompt etc.). Disabling kbdmux(4) may help.
1684 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1685 kernel modules referencing any of the above need to be recompiled.
1686 Bump __FreeBSD_version to 800075.
1689 GEOM_PART has become the default partition slicer for storage devices,
1690 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1691 introduces some changes:
1693 MSDOS/EBR: the devices created from MSDOS extended partition entries
1694 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1695 to devices with offset-based names. fstabs may need to be modified.
1697 BSD: the "geometry does not match label" warning is harmless in most
1698 cases but it points to problems in file system misalignment with
1699 disk geometry. The "c" partition is now implicit, covers the whole
1700 top-level drive and cannot be (mis)used by users.
1702 General: Kernel dumps are now not allowed to be written to devices
1703 whose partition types indicate they are meant to be used for file
1704 systems (or, in case of MSDOS partitions, as something else than
1707 Most of these changes date approximately from 200812.
1710 The uscanner(4) driver has been removed from the kernel. This follows
1711 Linux removing theirs in 2.6 and making libusb the default interface
1712 (supported by sane).
1715 The multicast forwarding code has been cleaned up. netstat(1)
1716 only relies on KVM now for printing bandwidth upcall meters.
1717 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1718 ip6_mroute_mod respectively. The config(5) options for statically
1719 compiling this code remain the same, i.e. 'options MROUTING'.
1722 Support for the IFF_NEEDSGIANT network interface flag has been
1723 removed, which means that non-MPSAFE network device drivers are no
1724 longer supported. In particular, if_ar, if_sr, and network device
1725 drivers from the old (legacy) USB stack can no longer be built or
1729 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1730 a bunch of new language catalog files have also been added.
1731 This means that some common libc messages are now localized and
1732 they depend on the LC_MESSAGES environmental variable.
1735 The k8temp(4) driver has been renamed to amdtemp(4) since
1736 support for Family 10 and Family 11 CPU families was added.
1739 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1740 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1742 For kernel developers, the most important changes are that the
1743 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1744 and this lock has been downgraded to a non-recursive mutex.
1746 Transport protocols (UDP, Raw IP) are now responsible for filtering
1747 inbound multicast traffic according to group membership and source
1748 filters. The imo_multicast_filter() KPI exists for this purpose.
1749 Transports which do not use multicast (SCTP, TCP) already reject
1750 multicast by default. Forwarding and receive performance may improve
1751 as a mutex acquisition is no longer needed in the ip_input()
1752 low-level input path. in_addmulti() and in_delmulti() are shimmed
1753 to new KPIs which exist to support SSM in-kernel.
1755 For application developers, it is recommended that loopback of
1756 multicast datagrams be disabled for best performance, as this
1757 will still cause the lock to be taken for each looped-back
1758 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1759 be tuned to 0 to disable loopback by default; it defaults to 1
1760 to preserve the existing behaviour.
1762 For systems administrators, to obtain best performance with
1763 multicast reception and multiple groups, it is always recommended
1764 that a card with a suitably precise hash filter is used. Hash
1765 collisions will still result in the lock being taken within the
1766 transport protocol input path to check group membership.
1768 If deploying FreeBSD in an environment with IGMP snooping switches,
1769 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1770 enabled; this forces 224.0.0.0/24 group membership to be announced
1773 The size of 'struct igmpstat' has changed; netstat needs to be
1774 recompiled to reflect this.
1775 Bump __FreeBSD_version to 800070.
1778 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1779 updated to use it. This requires a buildworld/installworld in order to
1780 update the library and dependencies (usbconfig, etc). Its advisable to
1781 rebuild all ports which uses libusb. More specific directions are given
1782 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1783 libusb are no longer required and can be removed.
1786 A workaround is committed to allow the creation of System V shared
1787 memory segment of size > 2 GB on the 64-bit architectures.
1788 Due to a limitation of the existing ABI, the shm_segsz member
1789 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1790 wrong for large segments. Note that limits must be explicitly
1791 raised to allow such segments to be created.
1794 The layout of struct ifnet has changed, requiring a rebuild of all
1795 network device driver modules.
1798 The /dev handling for the new USB stack has changed, a
1799 buildworld/installworld is required for libusb20.
1802 The new USB2 stack has now been permanently moved in and all kernel and
1803 module names reverted to their previous values (eg, usb, ehci, ohci,
1804 ums, ...). The old usb stack can be compiled in by prefixing the name
1805 with the letter 'o', the old usb modules have been removed.
1806 Updating entry 20090216 for xorg and 20090215 for libmap may still
1810 The rc.conf(5) option if_up_delay has been renamed to
1811 defaultroute_delay to better reflect its purpose. If you have
1812 customized this setting in /etc/rc.conf you need to update it to
1816 xorg 7.4 wants to configure its input devices via hald which does not
1817 yet work with USB2. If the keyboard/mouse does not work in xorg then
1819 Option "AllowEmptyInput" "off"
1820 to your ServerLayout section. This will cause X to use the configured
1821 kbd and mouse sections from your xorg.conf.
1824 The GENERIC kernels for all architectures now default to the new USB2
1825 stack. No kernel config options or code have been removed so if a
1826 problem arises please report it and optionally revert to the old USB
1827 stack. If you are loading USB kernel modules or have a custom kernel
1828 that includes GENERIC then ensure that usb names are also changed over,
1829 eg uftdi -> usb2_serial_ftdi.
1831 Older programs linked against the ports libusb 0.1 need to be
1832 redirected to the new stack's libusb20. /etc/libmap.conf can
1834 # Map old usb library to new one for usb2 stack
1835 libusb-0.1.so.8 libusb20.so.1
1838 All USB ethernet devices now attach as interfaces under the name ueN
1839 (eg. ue0). This is to provide a predictable name as vendors often
1840 change usb chipsets in a product without notice.
1843 The ichsmb(4) driver has been changed to require SMBus slave
1844 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1845 All of the other SMBus controller drivers require left-justified
1846 slave addresses, so this change makes all the drivers provide the
1850 INET6 statistics (struct ip6stat) was updated.
1851 netstat(1) needs to be recompiled.
1854 NTFS has been removed from GENERIC kernel on amd64 to match
1855 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1856 will load ntfs.ko module automatically when NTFS support is
1857 actually needed, unless ntfs.ko is not installed or security
1858 level prohibits loading kernel modules. If either is the case,
1859 "options NTFS" has to be added into kernel config.
1862 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1863 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1864 800061. User space tools that rely on the size of struct tcpcb in
1865 tcp_var.h (e.g. sockstat) need to be recompiled.
1868 ng_tty(4) module updated to match the new TTY subsystem.
1869 Due to API change, user-level applications must be updated.
1870 New API support added to mpd5 CVS and expected to be present
1871 in next mpd5.3 release.
1874 With __FreeBSD_version 800060 the makefs tool is part of
1875 the base system (it was a port).
1878 The afdata and ifnet locks have been changed from mutexes to
1879 rwlocks, network modules will need to be re-compiled.
1882 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1883 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1884 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1885 architecture and 40 bytes on 64-bit architecture. The userland
1886 applications "arp" and "ndp" have been updated accordingly.
1887 The output from "netstat -r" shows only routing entries and
1888 none of the L2 information.
1891 __FreeBSD_version 800057 marks the switchover from the
1892 binary ath hal to source code. Users must add the line:
1894 options AH_SUPPORT_AR5416
1896 to their kernel config files when specifying:
1900 The ath_hal module no longer exists; the code is now compiled
1901 together with the driver in the ath module. It is now
1902 possible to tailor chip support (i.e. reduce the set of chips
1903 and thereby the code size); consult ath_hal(4) for details.
1906 __FreeBSD_version 800054 adds memory barriers to
1907 <machine/atomic.h>, new interfaces to ifnet to facilitate
1908 multiple hardware transmit queues for cards that support
1909 them, and a lock-less ring-buffer implementation to
1910 enable drivers to more efficiently manage queueing of
1914 A new version of ZFS (version 13) has been merged to -HEAD.
1915 This version has zpool attribute "listsnapshots" off by
1916 default, which means "zfs list" does not show snapshots,
1917 and is the same as Solaris behavior.
1920 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1923 The uhci, ohci, ehci and slhci USB Host controller drivers have
1924 been put into separate modules. If you load the usb module
1925 separately through loader.conf you will need to load the
1926 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1927 controller add the following to loader.conf:
1933 The ABI used by the PMC toolset has changed. Please keep
1934 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1938 atapci kernel module now includes only generic PCI ATA
1939 driver. AHCI driver moved to ataahci kernel module.
1940 All vendor-specific code moved into separate kernel modules:
1941 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1942 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1943 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1944 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1947 The TTY subsystem of the kernel has been replaced by a new
1948 implementation, which provides better scalability and an
1949 improved driver model. Most common drivers have been migrated to
1950 the new TTY subsystem, while others have not. The following
1951 drivers have not yet been ported to the new TTY layer:
1954 cy, digi, rc, rp, sio
1960 ng_h4, ng_tty, ppp, sl, snp
1962 Adding these drivers to your kernel configuration file shall
1963 cause compilation to fail.
1966 ntpd has been upgraded to 4.2.4p5.
1969 OpenSSH has been upgraded to 5.1p1.
1971 For many years, FreeBSD's version of OpenSSH preferred DSA
1972 over RSA for host and user authentication keys. With this
1973 upgrade, we've switched to the vendor's default of RSA over
1974 DSA. This may cause upgraded clients to warn about unknown
1975 host keys even for previously known hosts. Users should
1976 follow the usual procedure for verifying host keys before
1977 accepting the RSA key.
1979 This can be circumvented by setting the "HostKeyAlgorithms"
1980 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1983 Please note that the sequence of keys offered for
1984 authentication has been changed as well. You may want to
1985 specify IdentityFile in a different order to revert this
1989 The sio(4) driver has been removed from the i386 and amd64
1990 kernel configuration files. This means uart(4) is now the
1991 default serial port driver on those platforms as well.
1993 To prevent collisions with the sio(4) driver, the uart(4) driver
1994 uses different names for its device nodes. This means the
1995 onboard serial port will now most likely be called "ttyu0"
1996 instead of "ttyd0". You may need to reconfigure applications to
1997 use the new device names.
1999 When using the serial port as a boot console, be sure to update
2000 /boot/device.hints and /etc/ttys before booting the new kernel.
2001 If you forget to do so, you can still manually specify the hints
2002 at the loader prompt:
2004 set hint.uart.0.at="isa"
2005 set hint.uart.0.port="0x3F8"
2006 set hint.uart.0.flags="0x10"
2007 set hint.uart.0.irq="4"
2011 The gpt(8) utility has been removed. Use gpart(8) to partition
2015 The version that Linuxulator emulates was changed from 2.4.2
2016 to 2.6.16. If you experience any problems with Linux binaries
2017 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2018 if it fixes the problem contact emulation mailing list.
2021 ISDN4BSD (I4B) was removed from the src tree. You may need to
2022 update a your kernel configuration and remove relevant entries.
2025 I have checked in code to support multiple routing tables.
2026 See the man pages setfib(1) and setfib(2).
2027 This is a hopefully backwards compatible version,
2028 but to make use of it you need to compile your kernel
2029 with options ROUTETABLES=2 (or more up to 16).
2032 The 802.11 wireless support was redone to enable multi-bss
2033 operation on devices that are capable. The underlying device
2034 is no longer used directly but instead wlanX devices are
2035 cloned with ifconfig. This requires changes to rc.conf files.
2036 For example, change:
2037 ifconfig_ath0="WPA DHCP"
2040 ifconfig_wlan0="WPA DHCP"
2041 see rc.conf(5) for more details. In addition, mergemaster of
2042 /etc/rc.d is highly recommended. Simultaneous update of userland
2043 and kernel wouldn't hurt either.
2045 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2046 modules were merged into the base wlan module. All references
2047 to these modules (e.g. in kernel config files) must be removed.
2050 psm(4) has gained write(2) support in native operation level.
2051 Arbitrary commands can be written to /dev/psm%d and status can
2052 be read back from it. Therefore, an application is responsible
2053 for status validation and error recovery. It is a no-op in
2054 other operation levels.
2057 Support for KSE threading has been removed from the kernel. To
2058 run legacy applications linked against KSE libmap.conf may
2059 be used. The following libmap.conf may be used to ensure
2060 compatibility with any prior release:
2062 libpthread.so.1 libthr.so.1
2063 libpthread.so.2 libthr.so.2
2064 libkse.so.3 libthr.so.3
2067 The layout of struct vmspace has changed. This affects libkvm
2068 and any executables that link against libkvm and use the
2069 kvm_getprocs() function. In particular, but not exclusively,
2070 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2071 The effects are minimal, but it's advisable to upgrade world
2075 The latest em driver no longer has support in it for the
2076 82575 adapter, this is now moved to the igb driver. The
2077 split was done to make new features that are incompatible
2078 with older hardware easier to do.
2081 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2082 likewise the kernel option is now GEOM_LINUX_LVM.
2085 The default NFS mount mode has changed from UDP to TCP for
2086 increased reliability. If you rely on (insecurely) NFS
2087 mounting across a firewall you may need to update your
2091 Belatedly note the addition of m_collapse for compacting
2095 The fts(3) structures have been changed to use adequate
2096 integer types for their members and so to be able to cope
2097 with huge file trees. The old fts(3) ABI is preserved
2098 through symbol versioning in libc, so third-party binaries
2099 using fts(3) should still work, although they will not take
2100 advantage of the extended types. At the same time, some
2101 third-party software might fail to build after this change
2102 due to unportable assumptions made in its source code about
2103 fts(3) structure members. Such software should be fixed
2104 by its vendor or, in the worst case, in the ports tree.
2105 FreeBSD_version 800015 marks this change for the unlikely
2106 case that a portable fix is impossible.
2109 To upgrade to -current after this date, you must be running
2110 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2111 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2114 The ADAPTIVE_GIANT kernel option has been retired because its
2115 functionality is the default now.
2118 The AT keyboard emulation of sunkbd(4) has been turned on
2119 by default. In order to make the special symbols of the Sun
2120 keyboards driven by sunkbd(4) work under X these now have
2121 to be configured the same way as Sun USB keyboards driven
2122 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2124 Option "XkbLayout" "us"
2125 Option "XkbRules" "xorg"
2126 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2129 It has been decided that it is desirable to provide ABI
2130 backwards compatibility to the FreeBSD 4/5/6 versions of the
2131 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2132 broken with the introduction of PCI domain support (see the
2133 20070930 entry). Unfortunately, this required the ABI of
2134 PCIOCGETCONF to be broken again in order to be able to
2135 provide backwards compatibility to the old version of that
2136 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2137 again. As for prominent ports this affects neither pciutils
2138 nor xorg-server this time, the hal port needs to be rebuilt
2142 The misnamed kthread_create() and friends have been renamed
2143 to kproc_create() etc. Many of the callers already
2144 used kproc_start()..
2145 I will return kthread_create() and friends in a while
2146 with implementations that actually create threads, not procs.
2147 Renaming corresponds with version 800002.
2156 Avoid using make -j when upgrading. While generally safe, there are
2157 sometimes problems using -j to upgrade. If your upgrade fails with
2158 -j, please try again without -j. From time to time in the past there
2159 have been problems using -j with buildworld and/or installworld. This
2160 is especially true when upgrading between "distant" versions (eg one
2161 that cross a major release boundary or several minor releases, or when
2162 several months have passed on the -current branch).
2164 Sometimes, obscure build problems are the result of environment
2165 poisoning. This can happen because the make utility reads its
2166 environment when searching for values for global variables. To run
2167 your build attempts in an "environmental clean room", prefix all make
2168 commands with 'env -i '. See the env(1) manual page for more details.
2170 When upgrading from one major version to another it is generally best
2171 to upgrade to the latest code in the currently installed branch first,
2172 then do an upgrade to the new branch. This is the best-tested upgrade
2173 path, and has the highest probability of being successful. Please try
2174 this approach before reporting problems with a major version upgrade.
2176 When upgrading a live system, having a root shell around before
2177 installing anything can help undo problems. Not having a root shell
2178 around can lead to problems if pam has changed too much from your
2179 starting point to allow continued authentication after the upgrade.
2183 When upgrading the boot ZFS pool to a new version, always follow
2186 1.) recompile and reinstall the ZFS boot loader and boot block
2187 (this is part of "make buildworld" and "make installworld")
2189 2.) update the ZFS boot block on your boot drive
2191 The following example updates the ZFS boot block on the first
2192 partition (freebsd-boot) of a GPT partitioned drive ad0:
2193 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2195 Non-boot pools do not need these updates.
2199 If you are updating from a prior version of FreeBSD (even one just
2200 a few days old), you should follow this procedure. It is the most
2201 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2203 make kernel-toolchain
2204 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2205 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2207 To test a kernel once
2208 ---------------------
2209 If you just want to boot a kernel once (because you are not sure
2210 if it works, or if you want to boot a known bad kernel to provide
2211 debugging information) run
2212 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2213 nextboot -k testkernel
2215 To just build a kernel when you know that it won't mess you up
2216 --------------------------------------------------------------
2217 This assumes you are already running a CURRENT system. Replace
2218 ${arch} with the architecture of your machine (e.g. "i386",
2219 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2221 cd src/sys/${arch}/conf
2222 config KERNEL_NAME_HERE
2223 cd ../compile/KERNEL_NAME_HERE
2228 If this fails, go to the "To build a kernel" section.
2230 To rebuild everything and install it on the current system.
2231 -----------------------------------------------------------
2232 # Note: sometimes if you are running current you gotta do more than
2233 # is listed here if you are upgrading from a really old current.
2235 <make sure you have good level 0 dumps>
2237 make kernel KERNCONF=YOUR_KERNEL_HERE
2239 <reboot in single user> [3]
2246 To cross-install current onto a separate partition
2247 --------------------------------------------------
2248 # In this approach we use a separate partition to hold
2249 # current's root, 'usr', and 'var' directories. A partition
2250 # holding "/", "/usr" and "/var" should be about 2GB in
2253 <make sure you have good level 0 dumps>
2256 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2257 <maybe newfs current's root partition>
2258 <mount current's root partition on directory ${CURRENT_ROOT}>
2259 make installworld DESTDIR=${CURRENT_ROOT}
2260 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2261 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2262 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2263 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2264 <reboot into current>
2265 <do a "native" rebuild/install as described in the previous section>
2266 <maybe install compatibility libraries from ports/misc/compat*>
2270 To upgrade in-place from stable to current
2271 ----------------------------------------------
2272 <make sure you have good level 0 dumps>
2274 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2276 <reboot in single user> [3]
2283 Make sure that you've read the UPDATING file to understand the
2284 tweaks to various things you need. At this point in the life
2285 cycle of current, things change often and you are on your own
2286 to cope. The defaults can also change, so please read ALL of
2287 the UPDATING entries.
2289 Also, if you are tracking -current, you must be subscribed to
2290 freebsd-current@freebsd.org. Make sure that before you update
2291 your sources that you have read and understood all the recent
2292 messages there. If in doubt, please track -stable which has
2293 much fewer pitfalls.
2295 [1] If you have third party modules, such as vmware, you
2296 should disable them at this point so they don't crash your
2299 [3] From the bootblocks, boot -s, and then do
2304 adjkerntz -i # if CMOS is wall time
2305 Also, when doing a major release upgrade, it is required that
2306 you boot into single user mode to do the installworld.
2308 [4] Note: This step is non-optional. Failure to do this step
2309 can result in a significant reduction in the functionality of the
2310 system. Attempting to do it by hand is not recommended and those
2311 that pursue this avenue should read this file carefully, as well
2312 as the archives of freebsd-current and freebsd-hackers mailing lists
2313 for potential gotchas. The -U option is also useful to consider.
2314 See mergemaster(8) for more information.
2316 [5] Usually this step is a noop. However, from time to time
2317 you may need to do this if you get unknown user in the following
2318 step. It never hurts to do it all the time. You may need to
2319 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2320 install) after the buildworld before this step if you last updated
2321 from current before 20130425 or from -stable before 20130430.
2323 [6] This only deletes old files and directories. Old libraries
2324 can be deleted by "make delete-old-libs", but you have to make
2325 sure that no program is using those libraries anymore.
2327 [8] In order to have a kernel that can run the 4.x binaries needed to
2328 do an installworld, you must include the COMPAT_FREEBSD4 option in
2329 your kernel. Failure to do so may leave you with a system that is
2330 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2331 required to run the 5.x binaries on more recent kernels. And so on
2332 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2334 Make sure that you merge any new devices from GENERIC since the
2335 last time you updated your kernel config file.
2337 [9] When checking out sources, you must include the -P flag to have
2338 cvs prune empty directories.
2340 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2341 "?=" instead of the "=" assignment operator, so that buildworld can
2342 override the CPUTYPE if it needs to.
2344 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2345 not on the command line, or in /etc/make.conf. buildworld will
2346 warn if it is improperly defined.
2349 This file contains a list, in reverse chronological order, of major
2350 breakages in tracking -current. It is not guaranteed to be a complete
2351 list of such breakages, and only contains entries since October 10, 2007.
2352 If you need to see UPDATING entries from before that date, you will need
2353 to fetch an UPDATING file from an older FreeBSD release.
2355 Copyright information:
2357 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2359 Redistribution, publication, translation and use, with or without
2360 modification, in full or in part, in any form or format of this
2361 document are permitted without further permission from the author.
2363 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2364 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2365 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2366 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2367 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2368 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2369 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2370 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2371 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2372 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2373 POSSIBILITY OF SUCH DAMAGE.
2375 Contact Warner Losh if you have any questions about your use of