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 20160926 p9 FreeBSD-SA-16:26.openssl [revised]
21 Fix OpenSSL regression introduced in SA-16:26.
23 20160923 p8 FreeBSD-SA-16:26.openssl
25 Fix multiple OpenSSL vulnerabilitites.
27 20160811 p7 FreeBSD-EN-16:10.dhclient
28 FreeBSD-EN-16:11.vmbus
29 FreeBSD-EN-16:12.hv_storvsc
30 FreeBSD-EN-16:13.vmbus
31 FreeBSD-EN-16:14.hv_storvsc
32 FreeBSD-EN-16:15.vmbus
33 FreeBSD-EN-16:16.hv_storvsc
35 Fix handling of unknown options from a DHCP server. [EN-16:10]
36 Fix a panic in hv_vmbus(4). [EN-16:11]
37 Fix missing hotplugged disk in hv_storvsc(4). [EN-16:12]
38 Fix the timecounter emulation in hv_vmbus(4). [EN-16:13]
39 Fix callout(9) handling in hv_storvsc(4). [EN-16:14]
40 Fix memory allocation issues in hv_vmbus(4). [EN-16:15]
41 Fix SCSI command handling in hv_storvsc(4). [EN-16:16]
43 20160725 p6 FreeBSD-SA-16:25.bspatch
44 FreeBSD-EN-16:09.freebsd-update
46 Fix bspatch heap overflow vulnerability. [SA-16:25]
48 Fix freebsd-update(8) support of FreeBSD 11.0 release
49 distribution. [EN-16:09]
51 20160604 p5 FreeBSD-SA-16:24.ntp
53 Fix multiple vulnerabilities of ntp.
55 20160531 p4 FreeBSD-SA-16:20.linux
56 FreeBSD-SA-16:21.43bsd
57 FreeBSD-SA-16:22.libarchive
59 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
60 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
61 Fix directory traversal in cpio(1). [SA-16:22]
64 20160517 p3 FreeBSD-SA-16:18.atkbd
65 FreeBSD-SA-16:19.sendmsg
67 Fix buffer overflow in keyboard driver. [SA-16:18]
69 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
71 20160504 p2 FreeBSD-SA-16:17.openssl
76 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
78 Fix performance regression in libc hash(3). [EN-16:06]
80 Fix excessive latency in x86 IPI delivery. [EN-16:07]
82 Fix memory leak in ZFS. [EN-16:08]
84 20160429 p1 FreeBSD-SA-16:16.ntp
86 Fix multiple vulnerabilities of ntp.
92 The NONE and HPN patches has been removed from OpenSSH. They are
93 still available in the security/openssh-portable port.
96 r292223 changed the internal interface between the nfsd.ko and
97 nfscommon.ko modules. As such, they must both be upgraded to-gether.
98 __FreeBSD_version has been bumped because of this.
101 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
102 Kernel modules isp_2400_multi and isp_2500_multi were removed and
103 should be replaced with isp_2400 and isp_2500 modules respectively.
106 The menu.rc and loader.rc files will now be replaced during
107 upgrades. Please migrate local changes to menu.rc.local and
108 loader.rc.local instead.
111 NTP has been upgraded to 4.2.8p4.
114 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
115 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
116 and devel/kyua to version 0.20+ and adjust any calling code to work
117 with Kyuafile and kyua.
120 The polarity of Pulse Per Second (PPS) capture events with the
121 uart(4) driver has been corrected. Prior to this change the PPS
122 "assert" event corresponded to the trailing edge of a positive PPS
123 pulse and the "clear" event was the leading edge of the next pulse.
125 As the width of a PPS pulse in a typical GPS receiver is on the
126 order of 1 millisecond, most users will not notice any significant
127 difference with this change.
129 Anyone who has compensated for the historical polarity reversal by
130 configuring a negative offset equal to the pulse width will need to
131 remove that workaround.
134 From legacy ata(4) driver was removed support for SATA controllers
135 supported by more functional drivers ahci(4), siis(4) and mvs(4).
136 Kernel modules ataahci and ataadaptec were removed completely,
137 replaced by ahci and mvs modules respectively.
143 As ZFS requires more kernel stack pages than is the default on some
144 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
145 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
147 Please consider using 'options KSTACK_PAGES=X' where X is greater
148 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
151 The default Unbound configuration now enables remote control
152 using a local socket. Users who have already enabled the
153 local_unbound service should regenerate their configuration
154 by running "service local_unbound setup" as root.
157 An additional fix for the issue described in the 20150614 sendmail
158 entry below has been been committed in revision 284786.
161 The fix for the issue described in the 20150614 sendmail entry
162 below has been been committed in revision 284485. The work
163 around described in that entry is no longer needed unless the
164 default setting is overridden by a confDH_PARAMETERS configuration
165 setting of '5' or pointing to a 512 bit DH parameter file.
168 The import of openssl to address the FreeBSD-SA-15:10.openssl
169 security advisory includes a change which rejects handshakes
170 with DH parameters below 768 bits. sendmail releases prior
171 to 8.15.2 (not yet released), defaulted to a 512 bit
172 DH parameter setting for client connections. To work around
173 this interoperability, sendmail can be configured to use a
174 2048 bit DH parameter by:
176 1. Edit /etc/mail/`hostname`.mc
177 2. If a setting for confDH_PARAMETERS does not exist or
178 exists and is set to a string beginning with '5',
180 3. If a setting for confDH_PARAMETERS exists and is set to
181 a file path, create a new file with:
182 openssl dhparam -out /path/to/file 2048
183 4. Rebuild the .cf file:
184 cd /etc/mail/; make; make install
186 cd /etc/mail/; make restart
188 A sendmail patch is coming, at which time this file will be
192 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
193 defined in symlink(7); previously symlinks were silently ignored.
196 The const qualifier has been removed from iconv(3) to comply with
197 POSIX. The ports tree is aware of this from r384038 onwards.
200 At svn r275807, The default linux compat kernel ABI has been adjusted
201 to 2.6.18 in support of the linux-c6 compat ports infrastructure
202 update. If you wish to continue using the linux-f10 compat ports,
203 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
204 encouraged to update their linux-compat packages to linux-c6 during
205 their next update cycle.
207 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
210 pjdfstest has been integrated into kyua as an opt-in test suite.
211 Please see share/doc/pjdfstest/README for a more details on how to
218 The ofwfb driver, used to provide a graphics console on PowerPC when
219 using vt(4), no longer allows mmap() of all of physical memory. This
220 will prevent Xorg on PowerPC with some ATI graphics cards from
221 initializing properly unless x11-servers/xorg-server is updated to
225 The libatf-c and libatf-c++ major versions were downgraded to 0 and
226 1 respectively to match the upstream numbers. They were out of
227 sync because, when they were originally added to FreeBSD, the
228 upstream versions were not respected. These libraries are private
229 and not yet built by default, so renumbering them should be a
230 non-issue. However, unclean source trees will yield broken test
231 programs once the operator executes "make delete-old-libs" after a
234 Additionally, the atf-sh binary was made private by moving it into
235 /usr/libexec/. Already-built shell test programs will keep the
236 path to the old binary so they will break after "make delete-old"
239 If you are using WITH_TESTS=yes (not the default), wipe the object
240 tree and rebuild from scratch to prevent spurious test failures.
241 This is only needed once: the misnumbered libraries and misplaced
242 binaries have been added to OptionalObsoleteFiles.inc so they will
243 be removed during a clean upgrade.
246 The ixgbe tunables now match their sysctl counterparts, for example:
247 hw.ixgbe.enable_aim => hw.ix.enable_aim
248 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
251 The NFSv4.1 server committed by r269398 changes the internal
252 function call interfaces used between the NFS and krpc modules.
253 As such, __FreeBSD_version was bumped.
256 The default unbound configuration has been modified to address
257 issues with reverse lookups on networks that use private
258 address ranges. If you use the local_unbound service, run
259 "service local_unbound setup" as root to regenerate your
260 configuration, then "service local_unbound reload" to load the
264 It is no longer necessary to include the dwarf version in your DEBUG
265 options in your kernel config file. The bug that required it to be
266 placed in the config file has bene fixed. DEBUG should now just
267 contain -g. The build system will automatically update things
268 to do the right thing.
271 Several ABI breaking changes were merged to CTL and new iSCSI code.
272 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
273 iscsictl need to be rebuilt to work with a new kernel.
276 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
277 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
278 which differs from the behaviour controlled by this knob.)
281 On i386 and amd64 systems, the onifconsole flag is now set by default
282 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
283 as a login TTY if it is set in the bootloader as an active kernel
284 console. No changes in behavior should result otherwise. To revert to
285 the previous behavior, set ttyu0 to "off" in /etc/ttys.
288 Clang and llvm have been upgraded to 3.4.1 release.
291 Clang and llvm have been upgraded to 3.4 release.
294 If a Makefile in a tests/ directory was auto-generating a Kyuafile
295 instead of providing an explicit one, this would prevent such
296 Makefile from providing its own Kyuafile in the future during
297 NO_CLEAN builds. This has been fixed in the Makefiles but manual
298 intervention is needed to clean an objdir if you use NO_CLEAN:
299 # find /usr/obj -name Kyuafile | xargs rm -f
302 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
303 capability mode support. Please note that enabling the feature in
304 kernel is still highly recommended.
307 OpenSSH is now built with sandbox support, and will use sandbox as
308 the default privilege separation method. This requires Capsicum
309 capability mode support in kernel.
312 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
313 been deprecated and will not be part of FreeBSD 11.0 and later
314 releases. If you use this driver, please consider switching to
315 the nfe(4) driver instead.
321 The behavior of gss_pseudo_random() for the krb5 mechanism
322 has changed, for applications requesting a longer random string
323 than produced by the underlying enctype's pseudo-random() function.
324 In particular, the random string produced from a session key of
325 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
326 be different at the 17th octet and later, after this change.
327 The counter used in the PRF+ construction is now encoded as a
328 big-endian integer in accordance with RFC 4402.
329 __FreeBSD_version is bumped to 1000701.
332 The WITHOUT_ATF build knob has been removed and its functionality
333 has been subsumed into the more generic WITHOUT_TESTS. If you were
334 using the former to disable the build of the ATF libraries, you
335 should change your settings to use the latter.
338 The default version of mtree is nmtree which is obtained from
339 NetBSD. The output is generally the same, but may vary
340 slightly. If you found you need identical output adding
341 "-F freebsd9" to the command line should do the trick. For the
342 time being, the old mtree is available as fmtree.
345 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
346 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
347 1.1.4_8 and verify bsdyml not linked in, before running "make
349 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
351 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
354 The rc.d/jail script has been updated to support jail(8)
355 configuration file. The "jail_<jname>_*" rc.conf(5) variables
356 for per-jail configuration are automatically converted to
357 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
358 This is transparently backward compatible. See below about some
359 incompatibilities and rc.conf(5) manual page for more details.
361 These variables are now deprecated in favor of jail(8) configuration
362 file. One can use "rc.d/jail config <jname>" command to generate
363 a jail(8) configuration file in /var/run/jail.<jname>.conf without
364 running the jail(8) utility. The default pathname of the
365 configuration file is /etc/jail.conf and can be specified by
366 using $jail_conf or $jail_<jname>_conf variables.
368 Please note that jail_devfs_ruleset accepts an integer at
369 this moment. Please consider to rewrite the ruleset name
373 BIND has been removed from the base system. If all you need
374 is a local resolver, simply enable and start the local_unbound
375 service instead. Otherwise, several versions of BIND are
376 available in the ports tree. The dns/bind99 port is one example.
378 With this change, nslookup(1) and dig(1) are no longer in the base
379 system. Users should instead use host(1) and drill(1) which are
380 in the base system. Alternatively, nslookup and dig can
381 be obtained by installing the dns/bind-tools port.
384 With the addition of unbound(8), a new unbound user is now
385 required during installworld. "mergemaster -p" can be used to
386 add the user prior to installworld, as documented in the handbook.
389 OpenSSH is now built with DNSSEC support, and will by default
390 silently trust signed SSHFP records. This can be controlled with
391 the VerifyHostKeyDNS client configuration setting. DNSSEC support
392 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
395 The GNU Compiler Collection and C++ standard library (libstdc++)
396 are no longer built by default on platforms where clang is the system
397 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
401 The PROCDESC kernel option is now part of the GENERIC kernel
402 configuration and is required for the rwhod(8) to work.
403 If you are using custom kernel configuration, you should include
407 The API and ABI related to the Capsicum framework was modified
408 in backward incompatible way. The userland libraries and programs
409 have to be recompiled to work with the new kernel. This includes the
410 following libraries and programs, but the whole buildworld is
411 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
412 kdump, procstat, rwho, rwhod, uniq.
415 AES-NI intrinsic support has been added to gcc. The AES-NI module
416 has been updated to use this support. A new gcc is required to build
417 the aesni module on both i386 and amd64.
420 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
421 Thus "device padlock_rng" and "device rdrand_rng" should be
422 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
425 WITH_ICONV has been split into two feature sets. WITH_ICONV now
426 enables just the iconv* functionality and is now on by default.
427 WITH_LIBICONV_COMPAT enables the libiconv api and link time
428 compatability. Set WITHOUT_ICONV to build the old way.
429 If you have been using WITH_ICONV before, you will very likely
430 need to turn on WITH_LIBICONV_COMPAT.
433 INVARIANTS option now enables DEBUG for code with OpenSolaris and
434 Illumos origin, including ZFS. If you have INVARIANTS in your
435 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
437 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
438 locks if WITNESS option was set. Because that generated a lot of
439 witness(9) reports and all of them were believed to be false
440 positives, this is no longer done. New option OPENSOLARIS_WITNESS
441 can be used to achieve the previous behavior.
444 Timer values in IPv6 data structures now use time_uptime instead
445 of time_second. Although this is not a user-visible functional
446 change, userland utilities which directly use them---ndp(8),
447 rtadvd(8), and rtsold(8) in the base system---need to be updated
451 find -delete can now delete the pathnames given as arguments,
452 instead of only files found below them or if the pathname did
453 not contain any slashes. Formerly, the following error message
456 find: -delete: <path>: relative path potentially not safe
458 Deleting the pathnames given as arguments can be prevented
459 without error messages using -mindepth 1 or by changing
460 directory and passing "." as argument to find. This works in the
461 old as well as the new version of find.
464 Behavior of devfs rules path matching has been changed.
465 Pattern is now always matched against fully qualified devfs
466 path and slash characters must be explicitly matched by
467 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
468 subdirectories must be reviewed.
471 The default ARM ABI has changed to the ARM EABI. The old ABI is
472 incompatible with the ARM EABI and all programs and modules will
473 need to be rebuilt to work with a new kernel.
475 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
477 NOTE: Support for the old ABI will be removed in the future and
478 users are advised to upgrade.
481 pkg_install has been disconnected from the build if you really need it
482 you should add WITH_PKGTOOLS in your src.conf(5).
485 Most of network statistics structures were changed to be able
486 keep 64-bits counters. Thus all tools, that work with networking
487 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
490 Fix a bug that allowed a tracing process (e.g. gdb) to write
491 to a memory-mapped file in the traced process's address space
492 even if neither the traced process nor the tracing process had
493 write access to that file.
496 CVS has been removed from the base system. An exact copy
497 of the code is available from the devel/cvs port.
500 Some people report the following error after the switch to bmake:
502 make: illegal option -- J
503 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
505 *** [buildworld] Error code 2
507 this likely due to an old instance of make in
508 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
509 which src/Makefile will use that blindly, if it exists, so if
510 you see the above error:
512 rm -rf `make -V MAKEPATH`
517 Use bmake by default.
518 Whereas before one could choose to build with bmake via
519 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
520 make. The goal is to remove these knobs for 10-RELEASE.
522 It is worth noting that bmake (like gmake) treats the command
523 line as the unit of failure, rather than statements within the
524 command line. Thus '(cd some/where && dosomething)' is safer
525 than 'cd some/where; dosomething'. The '()' allows consistent
526 behavior in parallel build.
529 Fix a bug that allows NFS clients to issue READDIR on files.
532 The WITHOUT_IDEA option has been removed because
533 the IDEA patent expired.
536 The sysctl which controls TRIM support under ZFS has been renamed
537 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
541 The mergemaster command now uses the default MAKEOBJDIRPREFIX
542 rather than creating it's own in the temporary directory in
543 order allow access to bootstrapped versions of tools such as
544 install and mtree. When upgrading from version of FreeBSD where
545 the install command does not support -l, you will need to
546 install a new mergemaster command if mergemaster -p is required.
547 This can be accomplished with the command (cd src/usr.sbin/mergemaster
551 Legacy ATA stack, disabled and replaced by new CAM-based one since
552 FreeBSD 9.0, completely removed from the sources. Kernel modules
553 atadisk and atapi*, user-level tools atacontrol and burncd are
554 removed. Kernel option `options ATA_CAM` is now permanently enabled
558 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
559 and socketpair(2). Software, in particular Kerberos, may
560 automatically detect and use these during building. The resulting
561 binaries will not work on older kernels.
564 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
565 information, see the respective 20130304 entry).
568 Recent commits to callout(9) changed the size of struct callout,
569 so the KBI is probably heavily disturbed. Also, some functions
570 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
571 by macros. Every kernel module using it won't load, so rebuild
574 The ctl device has been re-enabled in GENERIC for i386 and amd64,
575 but does not initialize by default (because of the new CTL_DISABLE
576 option) to save memory. To re-enable it, remove the CTL_DISABLE
577 option from the kernel config file or set kern.cam.ctl.disable=0
578 in /boot/loader.conf.
581 The ctl device has been disabled in GENERIC for i386 and amd64.
582 This was done due to the extra memory being allocated at system
583 initialisation time by the ctl driver which was only used if
584 a CAM target device was created. This makes a FreeBSD system
585 unusable on 128MB or less of RAM.
588 A new compression method (lz4) has been merged to -HEAD. Please
589 refer to zpool-features(7) for more information.
591 Please refer to the "ZFS notes" section of this file for information
592 on upgrading boot ZFS pools.
595 A BSD-licensed patch(1) variant has been added and is installed
596 as bsdpatch, being the GNU version the default patch.
597 To inverse the logic and use the BSD-licensed one as default,
598 while having the GNU version installed as gnupatch, rebuild
599 and install world with the WITH_BSD_PATCH knob set.
602 Due to the use of the new -l option to install(1) during build
603 and install, you must take care not to directly set the INSTALL
604 make variable in your /etc/make.conf, /etc/src.conf, or on the
605 command line. If you wish to use the -C flag for all installs
606 you may be able to add INSTALL+=-C to /etc/make.conf or
610 The install(1) option -M has changed meaning and now takes an
611 argument that is a file or path to append logs to. In the
612 unlikely event that -M was the last option on the command line
613 and the command line contained at least two files and a target
614 directory the first file will have logs appended to it. The -M
615 option served little practical purpose in the last decade so its
616 use is expected to be extremely rare.
619 After switching to Clang as the default compiler some users of ZFS
620 on i386 systems started to experience stack overflow kernel panics.
621 Please consider using 'options KSTACK_PAGES=4' in such configurations.
624 GEOM_LABEL now mangles label names read from file system metadata.
625 Mangling affect labels containing spaces, non-printable characters,
626 '%' or '"'. Device names in /etc/fstab and other places may need to
630 By default, only the 10 most recent kernel dumps will be saved. To
631 restore the previous behaviour (no limit on the number of kernel dumps
632 stored in the dump directory) add the following line to /etc/rc.conf:
637 With the addition of auditdistd(8), a new auditdistd user is now
638 required during installworld. "mergemaster -p" can be used to
639 add the user prior to installworld, as documented in the handbook.
642 The sin6_scope_id member variable in struct sockaddr_in6 is now
643 filled by the kernel before passing the structure to the userland via
644 sysctl or routing socket. This means the KAME-specific embedded scope
645 id in sin6_addr.s6_addr[2] is always cleared in userland application.
646 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
647 __FreeBSD_version is bumped to 1000025.
650 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
651 This means that the world and kernel will be compiled with clang
652 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
653 and /usr/bin/cpp. To disable this behavior and revert to building
654 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
655 of current may need to bootstrap WITHOUT_CLANG first if the clang
656 build fails (its compatibility window doesn't extend to the 9 stable
660 The IPFIREWALL_FORWARD kernel option has been removed. Its
661 functionality now turned on by default.
664 The ZERO_COPY_SOCKET kernel option has been removed and
665 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
666 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
667 mechanism which is not safe and may result in kernel crashes.
668 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
669 driver supports disposeable external page sized mbuf storage.
670 Proper replacements for both zero-copy mechanisms are under
671 consideration and will eventually lead to complete removal
672 of the two kernel options.
675 The IPv4 network stack has been converted to network byte
676 order. The following modules need to be recompiled together
677 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
678 pf(4), ipfw(4), ng_ipfw(4), stf(4).
681 Support for non-MPSAFE filesystems was removed from VFS. The
682 VFS_VERSION was bumped, all filesystem modules shall be
686 All the non-MPSAFE filesystems have been disconnected from
687 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
688 portalfs, smbfs, xfs.
691 The interface cloning API and ABI has changed. The following
692 modules need to be recompiled together with kernel:
693 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
694 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
695 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
698 The sdhci driver was split in two parts: sdhci (generic SD Host
699 Controller logic) and sdhci_pci (actual hardware driver).
700 No kernel config modifications are required, but if you
701 load sdhc as a module you must switch to sdhci_pci instead.
704 Import the FUSE kernel and userland support into base system.
707 The GNU sort(1) program has been removed since the BSD-licensed
708 sort(1) has been the default for quite some time and no serious
709 problems have been reported. The corresponding WITH_GNU_SORT
713 The pfil(9) API/ABI for AF_INET family has been changed. Packet
714 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
718 The net80211(4) ABI has been changed to allow for improved driver
719 PS-POLL and power-save support. All wireless drivers need to be
720 recompiled to work with the new kernel.
723 The random(4) support for the VIA hardware random number
724 generator (`PADLOCK') is no longer enabled unconditionally.
725 Add the padlock_rng device in the custom kernel config if
726 needed. The GENERIC kernels on i386 and amd64 do include the
727 device, so the change only affects the custom kernel
731 The pf(4) packet filter ABI has been changed. pfctl(8) and
732 snmp_pf module need to be recompiled to work with new kernel.
735 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
736 to -HEAD. Pools that have empty_bpobj in active state can not be
737 imported read-write with ZFS implementations that do not support
738 this feature. For more information read the zpool-features(5)
742 The sparc64 ZFS loader has been changed to no longer try to auto-
743 detect ZFS providers based on diskN aliases but now requires these
744 to be explicitly listed in the OFW boot-device environment variable.
747 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
748 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
749 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
752 The following sysctls and tunables have been renamed for consistency
753 with other variables:
754 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
755 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
758 The sort utility has been replaced with BSD sort. For now, GNU sort
759 is also available as "gnusort" or the default can be set back to
760 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
761 installed as "bsdsort".
764 A new version of ZFS (pool version 5000) has been merged to -HEAD.
765 Starting with this version the old system of ZFS pool versioning
766 is superseded by "feature flags". This concept enables forward
767 compatibility against certain future changes in functionality of ZFS
768 pools. The first read-only compatible "feature flag" for ZFS pools
769 is named "com.delphix:async_destroy". For more information
770 read the new zpool-features(5) manual page.
771 Please refer to the "ZFS notes" section of this file for information
772 on upgrading boot ZFS pools.
775 The malloc(3) implementation embedded in libc now uses sources imported
776 as contrib/jemalloc. The most disruptive API change is to
777 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
778 delete it prior to installworld, and optionally re-create it using the
779 new format after rebooting. See malloc.conf(5) for details
780 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
784 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
785 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
786 now spelled mips. This is to aid compatibility with third-party
787 software that expects this naming scheme in uname(3). Little-endian
788 settings are unchanged. If you are updating a big-endian mips64 machine
789 from before this change, you may need to set MACHINE_ARCH=mips64 in
790 your environment before the new build system will recognize your machine.
793 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
797 Now unix domain sockets behave "as expected" on nullfs(5). Previously
798 nullfs(5) did not pass through all behaviours to the underlying layer,
799 as a result if we bound to a socket on the lower layer we could connect
800 only to the lower path; if we bound to the upper layer we could connect
801 only to the upper path. The new behavior is one can connect to both the
802 lower and the upper paths regardless what layer path one binds to.
805 The getifaddrs upgrade path broken with 20111215 has been restored.
806 If you have upgraded in between 20111215 and 20120209 you need to
807 recompile libc again with your kernel. You still need to recompile
808 world to be able to configure CARP but this restriction already
812 The set_rcvar() function has been removed from /etc/rc.subr. All
813 base and ports rc.d scripts have been updated, so if you have a
814 port installed with a script in /usr/local/etc/rc.d you can either
815 hand-edit the rcvar= line, or reinstall the port.
817 An easy way to handle the mass-update of /etc/rc.d:
818 rm /etc/rc.d/* && mergemaster -i
821 panic(9) now stops other CPUs in the SMP systems, disables interrupts
822 on the current CPU and prevents other threads from running.
823 This behavior can be reverted using the kern.stop_scheduler_on_panic
825 The new behavior can be incompatible with kern.sync_on_panic.
828 The carp(4) facility has been changed significantly. Configuration
829 of the CARP protocol via ifconfig(8) has changed, as well as format
830 of CARP events submitted to devd(8) has changed. See manual pages
831 for more information. The arpbalance feature of carp(4) is currently
832 not supported anymore.
834 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
835 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
836 need to be recompiled.
839 The acpi_wmi(4) status device /dev/wmistat has been renamed to
843 The option VFS_ALLOW_NONMPSAFE option has been added in order to
844 explicitely support non-MPSAFE filesystems.
845 It is on by default for all supported platform at this present
849 The broken amd(4) driver has been replaced with esp(4) in the amd64,
850 i386 and pc98 GENERIC kernel configuration files.
853 sysinstall has been removed
856 The stable/9 branch created in subversion. This corresponds to the
857 RELENG_9 branch in CVS.
860 This commit modifies vfs_register() so that it uses a hash
861 calculation to set vfc_typenum, which is enabled by default.
862 The first time a system is booted after this change, the
863 vfc_typenum values will change for all file systems. The
864 main effect of this is a change to the NFS server file handles
865 for file systems that use vfc_typenum in their fsid, such as ZFS.
866 It will, however, prevent vfc_typenum from changing when file
867 systems are loaded in a different order for subsequent reboots.
868 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
869 until you are ready to remount all NFS clients after a reboot.
872 Bump the shared library version numbers for libraries that
873 do not use symbol versioning, have changed the ABI compared
874 to stable/8 and which shared library version was not bumped.
875 Done as part of 9.0-RELEASE cycle.
878 During the merge of Capsicum features, the fget(9) KPI was modified.
879 This may require the rebuilding of out-of-tree device drivers --
880 issues have been reported specifically with the nVidia device driver.
881 __FreeBSD_version is bumped to 900041.
883 Also, there is a period between 20110811 and 20110814 where the
884 special devices /dev/{stdin,stdout,stderr} did not work correctly.
885 Building world from a kernel during that window may not work.
888 The packet filter (pf) code has been updated to OpenBSD 4.5.
889 You need to update userland tools to be in sync with kernel.
890 This update breaks backward compatibility with earlier pfsync(4)
891 versions. Care must be taken when updating redundant firewall setups.
894 The following sysctls and tunables are retired on x86 platforms:
896 machdep.hlt_logical_cpus
897 The following sysctl is retired:
898 machdep.hyperthreading_allowed
899 The sysctls were supposed to provide a way to dynamically offline and
900 online selected CPUs on x86 platforms, but the implementation has not
901 been reliable especially with SCHED_ULE scheduler.
902 machdep.hyperthreading_allowed tunable is still available to ignore
903 hyperthreading CPUs at OS level.
904 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
905 where X is an APIC ID of a CPU. Be advised, though, that disabling
906 CPUs in non-uniform fashion will result in non-uniform topology and
907 may lead to sub-optimal system performance with SCHED_ULE, which is
911 cpumask_t type is retired and cpuset_t is used in order to describe
915 Changes to ifconfig(8) for dynamic address family detection mandate
916 that you are running a kernel of 20110525 or later. Make sure to
917 follow the update procedure to boot a new kernel before installing
921 Support for sun4v architecture is officially dropped
924 Several KPI breaking changes have been committed to the mii(4) layer,
925 the PHY drivers and consequently some Ethernet drivers using mii(4).
926 This means that miibus.ko and the modules of the affected Ethernet
927 drivers need to be recompiled.
929 Note to kernel developers: Given that the OUI bit reversion problem
930 was fixed as part of these changes all mii(4) commits related to OUIs,
931 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
932 handling, no longer can be merged verbatim to stable/8 and previous
936 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
937 into their kernel configurations along with 'device pci'.
940 The default NFS client is now the new NFS client, so fstype "newnfs"
941 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
942 Although mounts via fstype "nfs" will usually work without userland
943 changes, it is recommended that the mount(8) and mount_nfs(8)
944 commands be rebuilt from sources and that a link to mount_nfs called
945 mount_oldnfs be created. The new client is compiled into the
946 kernel with "options NFSCL" and this is needed for diskless root
947 file systems. The GENERIC kernel configs have been changed to use
948 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
949 To use the regular/old client, you can "mount -t oldnfs ...". For
950 a diskless root file system, you must also include a line like:
952 vfs.root.mountfrom="oldnfs:"
954 in the boot/loader.conf on the root fs on the NFS server to make
955 a diskless root fs use the old client.
958 The GENERIC kernels for all architectures now default to the new
959 CAM-based ATA stack. It means that all legacy ATA drivers were
960 removed and replaced by respective CAM drivers. If you are using
961 ATA device names in /etc/fstab or other places, make sure to update
962 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
963 where 'Y's are the sequential numbers starting from zero for each type
964 in order of detection, unless configured otherwise with tunables,
965 see cam(4)). There will be symbolic links created in /dev/ to map
966 old adX devices to the respective adaY. They should provide basic
967 compatibility for file systems mounting in most cases, but they do
968 not support old user-level APIs and do not have respective providers
969 in GEOM. Consider using updated management tools with new device names.
971 It is possible to load devices ahci, ata, siis and mvs as modules,
972 but option ATA_CAM should remain in kernel configuration to make ata
973 module work as CAM driver supporting legacy ATA controllers. Device ata
974 still can be used in modular fashion (atacore + ...). Modules atadisk
975 and atapi* are not used and won't affect operation in ATA_CAM mode.
976 Note that to use CAM-based ATA kernel should include CAM devices
977 scbus, pass, da (or explicitly ada), cd and optionally others. All of
978 them are parts of the cam module.
980 ataraid(4) functionality is now supported by the RAID GEOM class.
981 To use it you can load geom_raid kernel module and use graid(8) tool
982 for management. Instead of /dev/arX device names, use /dev/raid/rX.
984 No kernel config options or code have been removed, so if a problem
985 arises, please report it and optionally revert to the old ATA stack.
986 In order to do it you can remove from the kernel config:
991 , and instead add back:
992 device atadisk # ATA disk drives
993 device ataraid # ATA RAID drives
994 device atapicd # ATAPI CDROM drives
995 device atapifd # ATAPI floppy drives
996 device atapist # ATAPI tape drives
999 The default NFS server has been changed to the new server, which
1000 was referred to as the experimental server. If you need to switch
1001 back to the old NFS server, you must now put the "-o" option on
1002 both the mountd and nfsd commands. This can be done using the
1003 mountd_flags and nfs_server_flags rc.conf variables until an
1004 update to the rc scripts is committed, which is coming soon.
1007 The GNU Objective-C runtime library (libobjc), and other Objective-C
1008 related components have been removed from the base system. If you
1009 require an Objective-C library, please use one of the available ports.
1012 ath(4) has been split into bus- and device- modules. if_ath contains
1013 the HAL, the TX rate control and the network device code. if_ath_pci
1014 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1015 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1016 in order to use ath on everything else.
1018 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1019 need to load if_ath and if_ath_pci for ath(4) operation.
1022 As part of the replacement of sysinstall, the process of building
1023 release media has changed significantly. For details, please re-read
1024 release(7), which has been updated to reflect the new build process.
1027 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1028 is the last available version under GPLv2. It brings a number of new
1029 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1030 4.1 and SSE 4.2), better support for powerpc64, a number of new
1031 directives, and lots of other small improvements. See the ChangeLog
1032 file in contrib/binutils for the full details.
1035 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1036 compliant, and will now use half of hash for authentication.
1037 This will break interoperability with all stacks (including all
1038 actual FreeBSD versions) who implement
1039 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1041 The only workaround with such peers is to use another HMAC
1042 algorithm for IPsec ("phase 2") authentication.
1045 Remove the uio_yield prototype and symbol. This function has
1046 been misnamed since it was introduced and should not be
1047 globally exposed with this name. The equivalent functionality
1048 is now available using kern_yield(curthread->td_user_pri).
1049 The function remains undocumented.
1052 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1053 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1054 for scalar sysctls is defined but disabled. Code that needs
1055 UQUAD to pass the type checking that must compile on older
1056 systems where the define is not present can check against
1057 __FreeBSD_version >= 900030.
1059 The system dialog(1) has been replaced with a new version previously
1060 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1061 with the previous version, but the libdialog associated with it has
1062 a largely incompatible API. As such, the original version of libdialog
1063 will be kept temporarily as libodialog, until its base system consumers
1064 are replaced or updated. Bump __FreeBSD_version to 900030.
1067 If you are trying to run make universe on a -stable system, and you get
1068 the following warning:
1069 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1070 unknown. config(8) likely too old."
1071 or something similar to it, then you must upgrade your -stable system
1072 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1073 stable/8) or build the config from the latest stable/8 branch and
1074 install it on your system.
1076 Prior to this date, building a current universe on 8-stable system from
1077 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1078 error in the first kernel build phase. A new config on those old
1079 systems will fix that problem for older versions of -current.
1082 The TCP stack has been modified to allow Khelp modules to interact with
1083 it via helper hook points and store per-connection data in the TCP
1084 control block. Bump __FreeBSD_version to 900029. User space tools that
1085 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1089 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1090 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1091 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1092 to take advantage of it instead of using custom implementations. This
1093 means that these drivers now no longer unconditionally advertise
1094 support for flow control but only do so if flow control is a selected
1095 media option. This was implemented in the generic support that way in
1096 order to allow flow control to be switched on and off via ifconfig(8)
1097 with the PHY specific default to typically off in order to protect
1098 from unwanted effects. Consequently, if you used flow control with
1099 one of the above mentioned drivers you now need to explicitly enable
1100 it, for example via:
1101 ifconfig bge0 media auto mediaopt flowcontrol
1103 Along with the above mentioned changes generic support for setting
1104 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1105 e1000phy(4) as well as ip1000phy(4) have been converted to take
1106 advantage of it. This means that these drivers now no longer take the
1107 link0 parameter for selecting master mode but the master media option
1108 has to be used instead, for example like in the following:
1109 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1111 Selection of master mode now is also available with all other PHY
1112 drivers supporting 1000baseT.
1115 The TCP stack has received a significant update to add support for
1116 modularised congestion control and generally improve the clarity of
1117 congestion control decisions. Bump __FreeBSD_version to 900025. User
1118 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1119 sockstat) need to be recompiled.
1122 The man(1) utility has been replaced by a new version that no longer
1123 uses /etc/manpath.config. Please consult man.conf(5) for how to
1124 migrate local entries to the new format.
1127 The copyright strings printed by login(1) and sshd(8) at the time of a
1128 new connection have been removed to follow other operating systems and
1132 A workaround for a fixed ld bug has been removed in kernel code,
1133 so make sure that your system ld is built from sources after
1134 revision 210245 from 2010-07-19 (r211583 if building head kernel
1135 on stable/8, r211584 for stable/7; both from 2010-08-21).
1136 A symptom of incorrect ld version is different addresses for
1137 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1140 The $ipv6_prefer variable in rc.conf(5) has been split into
1141 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1143 The $ip6addrctl_policy is a variable to choose a pre-defined
1144 address selection policy set by ip6addrctl(8). A value
1145 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1148 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1149 flag (see an entry of 20090926) is set on an interface with no
1150 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1151 security reason. If you want IPv6 link-local address on all
1152 interfaces by default, set this to "YES".
1154 The old ipv6_prefer="YES" is equivalent to
1155 ipv6_activate_all_interfaces="YES" and
1156 ip6addrctl_policy="ipv6_prefer".
1159 DTrace has grown support for userland tracing. Due to this, DTrace is
1160 now i386 and amd64 only.
1161 dtruss(1) is now installed by default on those systems and a new
1162 kernel module is needed for userland tracing: fasttrap.
1163 No changes to your kernel config file are necessary to enable
1164 userland tracing, but you might consider adding 'STRIP=' and
1165 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1166 to have informative userland stack traces in DTrace (ustack).
1169 The acpi_aiboost(4) driver has been removed in favor of the new
1170 aibs(4) driver. You should update your kernel configuration file.
1173 BSD grep has been imported to the base system and it is built by
1174 default. It is completely BSD licensed, highly GNU-compatible, uses
1175 less memory than its GNU counterpart and has a small codebase.
1176 However, it is slower than its GNU counterpart, which is mostly
1177 noticeable for larger searches, for smaller ones it is measurable
1178 but not significant. The reason is complex, the most important factor
1179 is that we lack a modern and efficient regex library and GNU
1180 overcomes this by optimizing the searches internally. Future work
1181 on improving the regex performance is planned, for the meantime,
1182 users that need better performance, can build GNU grep instead by
1183 setting the WITH_GNU_GREP knob.
1186 Due to the import of powerpc64 support, all existing powerpc kernel
1187 configuration files must be updated with a machine directive like this:
1188 machine powerpc powerpc
1190 In addition, an updated config(8) is required to build powerpc kernels
1194 A new version of ZFS (version 15) has been merged to -HEAD.
1195 This version uses a python library for the following subcommands:
1196 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1197 For full functionality of these commands the following port must
1198 be installed: sysutils/py-zfs
1201 'vm_page's are now hashed by physical address to an array of mutexes.
1202 Currently this is only used to serialize access to hold_count. Over
1203 time the page queue mutex will be peeled away. This changes the size
1204 of pmap on every architecture. And requires all callers of vm_page_hold
1205 and vm_page_unhold to be updated.
1208 WITH_CTF can now be specified in src.conf (not recommended, there
1209 are some problems with static executables), make.conf (would also
1210 affect ports which do not use GNU make and do not override the
1211 compile targets) or in the kernel config (via "makeoptions
1213 When WITH_CTF was specified there before this was silently ignored,
1214 so make sure that WITH_CTF is not used in places which could lead
1215 to unwanted behavior.
1218 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1219 to allow 32-bit compatibility on non-x86 platforms. All kernel
1220 configurations on amd64 and ia64 platforms using these options must
1221 be modified accordingly.
1224 The utmp user accounting database has been replaced with utmpx,
1225 the user accounting interface standardized by POSIX.
1226 Unfortunately the semantics of utmp and utmpx don't match,
1227 making it practically impossible to support both interfaces.
1228 The user accounting database is used by tools like finger(1),
1229 last(1), talk(1), w(1) and ac(8).
1231 All applications in the base system use utmpx. This means only
1232 local binaries (e.g. from the ports tree) may still use these
1233 utmp database files. These applications must be rebuilt to make
1236 After the system has been upgraded, it is safe to remove the old
1237 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1238 assuming their contents is of no importance anymore. Old wtmp
1239 databases can only be used by last(1) and ac(8) after they have
1240 been converted to the new format using wtmpcvt(1).
1243 Introduce the kernel thread "deadlock resolver" (which can be enabled
1244 via the DEADLKRES option, see NOTES for more details) and the
1245 sleepq_type() function for sleepqueues.
1248 The rc.firewall and rc.firewall6 were unified, and
1249 rc.firewall6 and rc.d/ip6fw were removed.
1250 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1251 variables are obsoleted. Instead, the following new rc
1252 variables are added to rc.d/ipfw:
1254 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1255 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1256 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1258 The meanings correspond to the relevant IPv4 variables.
1264 The default terminal emulation for syscons(4) has been changed
1265 from cons25 to xterm on all platforms except pc98. This means
1266 that the /etc/ttys file needs to be updated to ensure correct
1267 operation of applications on the console.
1269 The terminal emulation style can be toggled per window by using
1270 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1271 options can be used to change the compile-time default back to
1274 To prevent graphical artifacts, make sure the TERM environment
1275 variable is set to match the terminal emulation that is being
1276 performed by syscons(4).
1279 The layout of the structure ieee80211req_scan_result has changed.
1280 Applications that require wireless scan results (e.g. ifconfig(8))
1281 from net80211 need to be recompiled.
1283 Applications such as wpa_supplicant(8) may require a full world
1284 build without using NO_CLEAN in order to get synchronized with the
1288 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1289 There's one kernel module for each firmware. Adding "device iwnfw"
1290 to the kernel configuration file means including all three firmware
1291 images inside the kernel. If you want to include just the one for
1292 your wireless card, use the devices iwn4965fw, iwn5000fw or
1296 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1297 into rc.d/netif. The changes are the following:
1299 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1300 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1301 Note that both variables need the "inet6" keyword at the head.
1303 Do not set $ipv6_network_interfaces manually if you do not
1304 understand what you are doing. It is not needed in most cases.
1306 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1309 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1310 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1312 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1313 all configured interfaces have "inet6 accept_rtadv" in the
1314 $ifconfig_IF_ipv6. These are for backward compatibility.
1316 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1317 functionality of interfaces with no corresponding
1318 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1319 and the default address selection policy of ip6addrctl(8)
1320 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1321 Note that if you want to configure IPv6 functionality on the
1322 disabled interfaces after boot, first you need to clear the flag by
1323 using ifconfig(8) like:
1325 ifconfig em0 inet6 -ifdisabled
1327 If YES, the default address selection policy is set as
1330 The default value of $ipv6_prefer is NO.
1332 4. If your system need to receive Router Advertisement messages,
1333 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1334 scripts automatically invoke rtsol(8) when the interface becomes
1335 UP. The Router Advertisement messages are used for SLAAC
1336 (State-Less Address AutoConfiguration).
1339 802.11s D3.03 support was committed. This is incompatible with the
1340 previous code, which was based on D3.0.
1343 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1344 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1345 control whether accepting Router Advertisement messages or not.
1346 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1347 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1348 The ifconfig(8) utility now supports these flags.
1351 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1352 mount(8) and -a option for df(1) to see them.
1355 The old tunable hw.bus.devctl_disable has been superseded by
1356 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1357 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1361 Remove the option STOP_NMI. The default action is now to use NMI only
1362 for KDB via the newly introduced function stop_cpus_hard() and
1363 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1366 The stable/8 branch created in subversion. This corresponds to the
1367 RELENG_8 branch in CVS.
1370 Bump the shared library version numbers for all libraries that do not
1371 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1372 __FreeBSD_version to 800105.
1375 Due to changes in the implementation of virtual network stack support,
1376 all network-related kernel modules must be recompiled. As this change
1377 breaks the ABI, bump __FreeBSD_version to 800104.
1380 The TOE interface to the TCP syncache has been modified to remove
1381 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1382 The cxgb driver is the only TOE consumer affected by this change, and
1383 needs to be recompiled along with the kernel. As this change breaks
1384 the ABI, bump __FreeBSD_version to 800103.
1387 Padding has been added to struct tcpcb, sackhint and tcpstat in
1388 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1389 maintaining the ABI. However, this change breaks the ABI, so bump
1390 __FreeBSD_version to 800102. User space tools that rely on the size of
1391 any of these structs (e.g. sockstat) need to be recompiled.
1394 The NFS_LEGACYRPC option has been removed along with the old kernel
1395 RPC implementation that this option selected. Kernel configurations
1396 may need to be adjusted.
1399 The network interface device nodes at /dev/net/<interface> have been
1400 removed. All ioctl operations can be performed the normal way using
1401 routing sockets. The kqueue functionality can generally be replaced
1402 with routing sockets.
1405 The documentation from the FreeBSD Documentation Project (Handbook,
1406 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1407 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1410 The ABI of various structures related to the SYSV IPC API have been
1411 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1412 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1416 Layout of struct vnet has changed as routing related variables were
1417 moved to their own Vimage module. Modules need to be recompiled. Bump
1418 __FreeBSD_version to 800099.
1421 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1422 respectively. As long as no more than 16 groups per process are used,
1423 no changes should be visible. When more than 16 groups are used, old
1424 binaries may fail if they call getgroups() or getgrouplist() with
1425 statically sized storage. Recompiling will work around this, but
1426 applications should be modified to use dynamically allocated storage
1427 for group arrays as POSIX.1-2008 does not cap an implementation's
1428 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1430 NFS and portalfs mounts may also be affected as the list of groups is
1431 truncated to 16. Users of NFS who use more than 16 groups, should
1432 take care that negative group permissions are not used on the exported
1433 file systems as they will not be reliable unless a GSSAPI based
1434 authentication method is used.
1437 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1438 option compiles in the support for adaptive spinning for lockmgrs
1439 which want to enable it. The lockinit() function now accepts the flag
1440 LK_ADAPTIVE in order to make the lock object subject to adaptive
1441 spinning when both held in write and read mode.
1444 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1445 changed. User applications that use this ioctl need to be rebuilt.
1448 The layout of struct thread has changed. Kernel and modules need to
1452 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1453 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1456 window(1) has been removed from the base system. It can now be
1457 installed from ports. The port is called misc/window.
1460 The way we are storing and accessing `routing table' entries has
1461 changed. Programs reading the FIB, like netstat, need to be
1465 A new netisr implementation has been added for FreeBSD 8. Network
1466 file system modules, such as igmp, ipdivert, and others, should be
1468 Bump __FreeBSD_version to 800096.
1471 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1475 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1476 Bump __FreeBSD_version to 800094.
1479 Add mnt_xflag field to 'struct mount'. File system modules need to be
1481 Bump __FreeBSD_version to 800093.
1484 The compiling option ADAPTIVE_SX has been retired while it has been
1485 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1486 The KPI for sx_init_flags() changes as accepting flags:
1487 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1488 been introduced in order to handle the reversed logic.
1489 Bump __FreeBSD_version to 800092.
1492 Add support for hierarchical jails. Remove global securelevel.
1493 Bump __FreeBSD_version to 800091.
1496 The layout of struct vnet_net has changed, therefore modules
1498 Bump __FreeBSD_version to 800090.
1501 The newly imported zic(8) produces a new format in the output. Please
1502 run tzsetup(8) to install the newly created data to /etc/localtime.
1505 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1506 hw.usb.* and is now consistent again with previous releases.
1509 802.11 monitor mode support was revised and driver api's were changed.
1510 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1511 of DLT_IEEE802_11. No user-visible data structures were changed but
1512 applications that use DLT_IEEE802_11 may require changes.
1513 Bump __FreeBSD_version to 800088.
1516 The layout of the following structs has changed: sysctl_oid,
1517 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1518 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1519 panics may be experienced. World rebuild is required for
1520 correctly checking networking state from userland.
1521 Bump __FreeBSD_version to 800085.
1524 MLDv2 and Source-Specific Multicast (SSM) have been merged
1525 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1526 The implementation of SSM within FreeBSD's IPv6 stack closely
1527 follows the IPv4 implementation.
1529 For kernel developers:
1531 * The most important changes are that the ip6_output() and
1532 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1533 and this lock has been downgraded to a non-recursive mutex.
1535 * As with the changes to the IPv4 stack to support SSM, filtering
1536 of inbound multicast traffic must now be performed by transport
1537 protocols within the IPv6 stack. This does not apply to TCP and
1538 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1540 * The KPIs used by IPv6 multicast are similar to those used by
1541 the IPv4 stack, with the following differences:
1542 * im6o_mc_filter() is analogous to imo_multicast_filter().
1543 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1544 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1545 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1546 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1547 for MLDv1 have an additional 'timer' argument which is used to
1548 jitter the initial membership report for the solicited-node
1549 multicast membership on-link.
1550 * This is not strictly needed for MLDv2, which already jitters
1551 its report transmissions. However, the 'timer' argument is
1552 preserved in case MLDv1 is active on the interface.
1554 * The KAME linked-list based IPv6 membership implementation has
1555 been refactored to use a vector similar to that used by the IPv4
1557 Code which maintains a list of its own multicast memberships
1558 internally, e.g. carp, has been updated to reflect the new
1561 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1562 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1563 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1564 implementation constraint which needs to be addressed in HEAD.
1566 For application developers:
1568 * The changes are broadly similar to those made for the IPv4
1571 * The use of IPv4 and IPv6 multicast socket options on the same
1572 socket, using mapped addresses, HAS NOT been tested or supported.
1574 * There are a number of issues with the implementation of various
1575 IPv6 multicast APIs which need to be resolved in the API surface
1576 before the implementation is fully compatible with KAME userland
1577 use, and these are mostly to do with interface index treatment.
1579 * The literature available discusses the use of either the delta / ASM
1580 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1581 using setsourcefilter(3)/getsourcefilter(3). For more information
1582 please refer to RFC 3768, 'Socket Interface Extensions for
1583 Multicast Source Filters'.
1585 * Applications which use the published RFC 3678 APIs should be fine.
1587 For systems administrators:
1589 * The mtest(8) utility has been refactored to support IPv6, in
1590 addition to IPv4. Interface addresses are no longer accepted
1591 as arguments, their names must be used instead. The utility
1592 will map the interface name to its first IPv4 address as
1593 returned by getifaddrs(3).
1595 * The ifmcstat(8) utility has also been updated to print the MLDv2
1596 endpoint state and source filter lists via sysctl(3).
1598 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1599 loopback of IPv6 multicast datagrams by default; it defaults to 1
1600 to preserve the existing behaviour. Disabling multicast loopback is
1601 recommended for optimal system performance.
1603 * The IPv6 MROUTING code has been changed to examine this sysctl
1604 instead of attempting to perform a group lookup before looping
1605 back forwarded datagrams.
1607 Bump __FreeBSD_version to 800084.
1610 Implement low-level Bluetooth HCI API.
1611 Bump __FreeBSD_version to 800083.
1614 The layout of struct malloc_type, used by modules to register new
1615 memory allocation types, has changed. Most modules will need to
1616 be rebuilt or panics may be experienced.
1617 Bump __FreeBSD_version to 800081.
1620 Anticipate overflowing inp_flags - add inp_flags2.
1621 This changes most offsets in inpcb, so checking v4 connection
1622 state will require a world rebuild.
1623 Bump __FreeBSD_version to 800080.
1626 Add an llentry to struct route and struct route_in6. Modules
1627 embedding a struct route will need to be recompiled.
1628 Bump __FreeBSD_version to 800079.
1631 The size of rt_metrics_lite and by extension rtentry has changed.
1632 Networking administration apps will need to be recompiled.
1633 The route command now supports show as an alias for get, weighting
1634 of routes, sticky and nostick flags to alter the behavior of stateful
1636 Bump __FreeBSD_version to 800078.
1639 Do not use Giant for kbdmux(4) locking. This is wrong and
1640 apparently causing more problems than it solves. This will
1641 re-open the issue where interrupt handlers may race with
1642 kbdmux(4) in polling mode. Typical symptoms include (but
1643 not limited to) duplicated and/or missing characters when
1644 low level console functions (such as gets) are used while
1645 interrupts are enabled (for example geli password prompt,
1646 mountroot prompt etc.). Disabling kbdmux(4) may help.
1649 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1650 kernel modules referencing any of the above need to be recompiled.
1651 Bump __FreeBSD_version to 800075.
1654 GEOM_PART has become the default partition slicer for storage devices,
1655 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1656 introduces some changes:
1658 MSDOS/EBR: the devices created from MSDOS extended partition entries
1659 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1660 to devices with offset-based names. fstabs may need to be modified.
1662 BSD: the "geometry does not match label" warning is harmless in most
1663 cases but it points to problems in file system misalignment with
1664 disk geometry. The "c" partition is now implicit, covers the whole
1665 top-level drive and cannot be (mis)used by users.
1667 General: Kernel dumps are now not allowed to be written to devices
1668 whose partition types indicate they are meant to be used for file
1669 systems (or, in case of MSDOS partitions, as something else than
1672 Most of these changes date approximately from 200812.
1675 The uscanner(4) driver has been removed from the kernel. This follows
1676 Linux removing theirs in 2.6 and making libusb the default interface
1677 (supported by sane).
1680 The multicast forwarding code has been cleaned up. netstat(1)
1681 only relies on KVM now for printing bandwidth upcall meters.
1682 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1683 ip6_mroute_mod respectively. The config(5) options for statically
1684 compiling this code remain the same, i.e. 'options MROUTING'.
1687 Support for the IFF_NEEDSGIANT network interface flag has been
1688 removed, which means that non-MPSAFE network device drivers are no
1689 longer supported. In particular, if_ar, if_sr, and network device
1690 drivers from the old (legacy) USB stack can no longer be built or
1694 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1695 a bunch of new language catalog files have also been added.
1696 This means that some common libc messages are now localized and
1697 they depend on the LC_MESSAGES environmental variable.
1700 The k8temp(4) driver has been renamed to amdtemp(4) since
1701 support for Family 10 and Family 11 CPU families was added.
1704 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1705 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1707 For kernel developers, the most important changes are that the
1708 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1709 and this lock has been downgraded to a non-recursive mutex.
1711 Transport protocols (UDP, Raw IP) are now responsible for filtering
1712 inbound multicast traffic according to group membership and source
1713 filters. The imo_multicast_filter() KPI exists for this purpose.
1714 Transports which do not use multicast (SCTP, TCP) already reject
1715 multicast by default. Forwarding and receive performance may improve
1716 as a mutex acquisition is no longer needed in the ip_input()
1717 low-level input path. in_addmulti() and in_delmulti() are shimmed
1718 to new KPIs which exist to support SSM in-kernel.
1720 For application developers, it is recommended that loopback of
1721 multicast datagrams be disabled for best performance, as this
1722 will still cause the lock to be taken for each looped-back
1723 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1724 be tuned to 0 to disable loopback by default; it defaults to 1
1725 to preserve the existing behaviour.
1727 For systems administrators, to obtain best performance with
1728 multicast reception and multiple groups, it is always recommended
1729 that a card with a suitably precise hash filter is used. Hash
1730 collisions will still result in the lock being taken within the
1731 transport protocol input path to check group membership.
1733 If deploying FreeBSD in an environment with IGMP snooping switches,
1734 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1735 enabled; this forces 224.0.0.0/24 group membership to be announced
1738 The size of 'struct igmpstat' has changed; netstat needs to be
1739 recompiled to reflect this.
1740 Bump __FreeBSD_version to 800070.
1743 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1744 updated to use it. This requires a buildworld/installworld in order to
1745 update the library and dependencies (usbconfig, etc). Its advisable to
1746 rebuild all ports which uses libusb. More specific directions are given
1747 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1748 libusb are no longer required and can be removed.
1751 A workaround is committed to allow the creation of System V shared
1752 memory segment of size > 2 GB on the 64-bit architectures.
1753 Due to a limitation of the existing ABI, the shm_segsz member
1754 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1755 wrong for large segments. Note that limits must be explicitly
1756 raised to allow such segments to be created.
1759 The layout of struct ifnet has changed, requiring a rebuild of all
1760 network device driver modules.
1763 The /dev handling for the new USB stack has changed, a
1764 buildworld/installworld is required for libusb20.
1767 The new USB2 stack has now been permanently moved in and all kernel and
1768 module names reverted to their previous values (eg, usb, ehci, ohci,
1769 ums, ...). The old usb stack can be compiled in by prefixing the name
1770 with the letter 'o', the old usb modules have been removed.
1771 Updating entry 20090216 for xorg and 20090215 for libmap may still
1775 The rc.conf(5) option if_up_delay has been renamed to
1776 defaultroute_delay to better reflect its purpose. If you have
1777 customized this setting in /etc/rc.conf you need to update it to
1781 xorg 7.4 wants to configure its input devices via hald which does not
1782 yet work with USB2. If the keyboard/mouse does not work in xorg then
1784 Option "AllowEmptyInput" "off"
1785 to your ServerLayout section. This will cause X to use the configured
1786 kbd and mouse sections from your xorg.conf.
1789 The GENERIC kernels for all architectures now default to the new USB2
1790 stack. No kernel config options or code have been removed so if a
1791 problem arises please report it and optionally revert to the old USB
1792 stack. If you are loading USB kernel modules or have a custom kernel
1793 that includes GENERIC then ensure that usb names are also changed over,
1794 eg uftdi -> usb2_serial_ftdi.
1796 Older programs linked against the ports libusb 0.1 need to be
1797 redirected to the new stack's libusb20. /etc/libmap.conf can
1799 # Map old usb library to new one for usb2 stack
1800 libusb-0.1.so.8 libusb20.so.1
1803 All USB ethernet devices now attach as interfaces under the name ueN
1804 (eg. ue0). This is to provide a predictable name as vendors often
1805 change usb chipsets in a product without notice.
1808 The ichsmb(4) driver has been changed to require SMBus slave
1809 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1810 All of the other SMBus controller drivers require left-justified
1811 slave addresses, so this change makes all the drivers provide the
1815 INET6 statistics (struct ip6stat) was updated.
1816 netstat(1) needs to be recompiled.
1819 NTFS has been removed from GENERIC kernel on amd64 to match
1820 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1821 will load ntfs.ko module automatically when NTFS support is
1822 actually needed, unless ntfs.ko is not installed or security
1823 level prohibits loading kernel modules. If either is the case,
1824 "options NTFS" has to be added into kernel config.
1827 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1828 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1829 800061. User space tools that rely on the size of struct tcpcb in
1830 tcp_var.h (e.g. sockstat) need to be recompiled.
1833 ng_tty(4) module updated to match the new TTY subsystem.
1834 Due to API change, user-level applications must be updated.
1835 New API support added to mpd5 CVS and expected to be present
1836 in next mpd5.3 release.
1839 With __FreeBSD_version 800060 the makefs tool is part of
1840 the base system (it was a port).
1843 The afdata and ifnet locks have been changed from mutexes to
1844 rwlocks, network modules will need to be re-compiled.
1847 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1848 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1849 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1850 architecture and 40 bytes on 64-bit architecture. The userland
1851 applications "arp" and "ndp" have been updated accordingly.
1852 The output from "netstat -r" shows only routing entries and
1853 none of the L2 information.
1856 __FreeBSD_version 800057 marks the switchover from the
1857 binary ath hal to source code. Users must add the line:
1859 options AH_SUPPORT_AR5416
1861 to their kernel config files when specifying:
1865 The ath_hal module no longer exists; the code is now compiled
1866 together with the driver in the ath module. It is now
1867 possible to tailor chip support (i.e. reduce the set of chips
1868 and thereby the code size); consult ath_hal(4) for details.
1871 __FreeBSD_version 800054 adds memory barriers to
1872 <machine/atomic.h>, new interfaces to ifnet to facilitate
1873 multiple hardware transmit queues for cards that support
1874 them, and a lock-less ring-buffer implementation to
1875 enable drivers to more efficiently manage queueing of
1879 A new version of ZFS (version 13) has been merged to -HEAD.
1880 This version has zpool attribute "listsnapshots" off by
1881 default, which means "zfs list" does not show snapshots,
1882 and is the same as Solaris behavior.
1885 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1888 The uhci, ohci, ehci and slhci USB Host controller drivers have
1889 been put into separate modules. If you load the usb module
1890 separately through loader.conf you will need to load the
1891 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1892 controller add the following to loader.conf:
1898 The ABI used by the PMC toolset has changed. Please keep
1899 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1903 atapci kernel module now includes only generic PCI ATA
1904 driver. AHCI driver moved to ataahci kernel module.
1905 All vendor-specific code moved into separate kernel modules:
1906 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1907 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1908 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1909 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1912 The TTY subsystem of the kernel has been replaced by a new
1913 implementation, which provides better scalability and an
1914 improved driver model. Most common drivers have been migrated to
1915 the new TTY subsystem, while others have not. The following
1916 drivers have not yet been ported to the new TTY layer:
1919 cy, digi, rc, rp, sio
1925 ng_h4, ng_tty, ppp, sl, snp
1927 Adding these drivers to your kernel configuration file shall
1928 cause compilation to fail.
1931 ntpd has been upgraded to 4.2.4p5.
1934 OpenSSH has been upgraded to 5.1p1.
1936 For many years, FreeBSD's version of OpenSSH preferred DSA
1937 over RSA for host and user authentication keys. With this
1938 upgrade, we've switched to the vendor's default of RSA over
1939 DSA. This may cause upgraded clients to warn about unknown
1940 host keys even for previously known hosts. Users should
1941 follow the usual procedure for verifying host keys before
1942 accepting the RSA key.
1944 This can be circumvented by setting the "HostKeyAlgorithms"
1945 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1948 Please note that the sequence of keys offered for
1949 authentication has been changed as well. You may want to
1950 specify IdentityFile in a different order to revert this
1954 The sio(4) driver has been removed from the i386 and amd64
1955 kernel configuration files. This means uart(4) is now the
1956 default serial port driver on those platforms as well.
1958 To prevent collisions with the sio(4) driver, the uart(4) driver
1959 uses different names for its device nodes. This means the
1960 onboard serial port will now most likely be called "ttyu0"
1961 instead of "ttyd0". You may need to reconfigure applications to
1962 use the new device names.
1964 When using the serial port as a boot console, be sure to update
1965 /boot/device.hints and /etc/ttys before booting the new kernel.
1966 If you forget to do so, you can still manually specify the hints
1967 at the loader prompt:
1969 set hint.uart.0.at="isa"
1970 set hint.uart.0.port="0x3F8"
1971 set hint.uart.0.flags="0x10"
1972 set hint.uart.0.irq="4"
1976 The gpt(8) utility has been removed. Use gpart(8) to partition
1980 The version that Linuxulator emulates was changed from 2.4.2
1981 to 2.6.16. If you experience any problems with Linux binaries
1982 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1983 if it fixes the problem contact emulation mailing list.
1986 ISDN4BSD (I4B) was removed from the src tree. You may need to
1987 update a your kernel configuration and remove relevant entries.
1990 I have checked in code to support multiple routing tables.
1991 See the man pages setfib(1) and setfib(2).
1992 This is a hopefully backwards compatible version,
1993 but to make use of it you need to compile your kernel
1994 with options ROUTETABLES=2 (or more up to 16).
1997 The 802.11 wireless support was redone to enable multi-bss
1998 operation on devices that are capable. The underlying device
1999 is no longer used directly but instead wlanX devices are
2000 cloned with ifconfig. This requires changes to rc.conf files.
2001 For example, change:
2002 ifconfig_ath0="WPA DHCP"
2005 ifconfig_wlan0="WPA DHCP"
2006 see rc.conf(5) for more details. In addition, mergemaster of
2007 /etc/rc.d is highly recommended. Simultaneous update of userland
2008 and kernel wouldn't hurt either.
2010 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2011 modules were merged into the base wlan module. All references
2012 to these modules (e.g. in kernel config files) must be removed.
2015 psm(4) has gained write(2) support in native operation level.
2016 Arbitrary commands can be written to /dev/psm%d and status can
2017 be read back from it. Therefore, an application is responsible
2018 for status validation and error recovery. It is a no-op in
2019 other operation levels.
2022 Support for KSE threading has been removed from the kernel. To
2023 run legacy applications linked against KSE libmap.conf may
2024 be used. The following libmap.conf may be used to ensure
2025 compatibility with any prior release:
2027 libpthread.so.1 libthr.so.1
2028 libpthread.so.2 libthr.so.2
2029 libkse.so.3 libthr.so.3
2032 The layout of struct vmspace has changed. This affects libkvm
2033 and any executables that link against libkvm and use the
2034 kvm_getprocs() function. In particular, but not exclusively,
2035 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2036 The effects are minimal, but it's advisable to upgrade world
2040 The latest em driver no longer has support in it for the
2041 82575 adapter, this is now moved to the igb driver. The
2042 split was done to make new features that are incompatible
2043 with older hardware easier to do.
2046 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2047 likewise the kernel option is now GEOM_LINUX_LVM.
2050 The default NFS mount mode has changed from UDP to TCP for
2051 increased reliability. If you rely on (insecurely) NFS
2052 mounting across a firewall you may need to update your
2056 Belatedly note the addition of m_collapse for compacting
2060 The fts(3) structures have been changed to use adequate
2061 integer types for their members and so to be able to cope
2062 with huge file trees. The old fts(3) ABI is preserved
2063 through symbol versioning in libc, so third-party binaries
2064 using fts(3) should still work, although they will not take
2065 advantage of the extended types. At the same time, some
2066 third-party software might fail to build after this change
2067 due to unportable assumptions made in its source code about
2068 fts(3) structure members. Such software should be fixed
2069 by its vendor or, in the worst case, in the ports tree.
2070 FreeBSD_version 800015 marks this change for the unlikely
2071 case that a portable fix is impossible.
2074 To upgrade to -current after this date, you must be running
2075 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2076 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2079 The ADAPTIVE_GIANT kernel option has been retired because its
2080 functionality is the default now.
2083 The AT keyboard emulation of sunkbd(4) has been turned on
2084 by default. In order to make the special symbols of the Sun
2085 keyboards driven by sunkbd(4) work under X these now have
2086 to be configured the same way as Sun USB keyboards driven
2087 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2089 Option "XkbLayout" "us"
2090 Option "XkbRules" "xorg"
2091 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2094 It has been decided that it is desirable to provide ABI
2095 backwards compatibility to the FreeBSD 4/5/6 versions of the
2096 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2097 broken with the introduction of PCI domain support (see the
2098 20070930 entry). Unfortunately, this required the ABI of
2099 PCIOCGETCONF to be broken again in order to be able to
2100 provide backwards compatibility to the old version of that
2101 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2102 again. As for prominent ports this affects neither pciutils
2103 nor xorg-server this time, the hal port needs to be rebuilt
2107 The misnamed kthread_create() and friends have been renamed
2108 to kproc_create() etc. Many of the callers already
2109 used kproc_start()..
2110 I will return kthread_create() and friends in a while
2111 with implementations that actually create threads, not procs.
2112 Renaming corresponds with version 800002.
2121 Avoid using make -j when upgrading. While generally safe, there are
2122 sometimes problems using -j to upgrade. If your upgrade fails with
2123 -j, please try again without -j. From time to time in the past there
2124 have been problems using -j with buildworld and/or installworld. This
2125 is especially true when upgrading between "distant" versions (eg one
2126 that cross a major release boundary or several minor releases, or when
2127 several months have passed on the -current branch).
2129 Sometimes, obscure build problems are the result of environment
2130 poisoning. This can happen because the make utility reads its
2131 environment when searching for values for global variables. To run
2132 your build attempts in an "environmental clean room", prefix all make
2133 commands with 'env -i '. See the env(1) manual page for more details.
2135 When upgrading from one major version to another it is generally best
2136 to upgrade to the latest code in the currently installed branch first,
2137 then do an upgrade to the new branch. This is the best-tested upgrade
2138 path, and has the highest probability of being successful. Please try
2139 this approach before reporting problems with a major version upgrade.
2141 When upgrading a live system, having a root shell around before
2142 installing anything can help undo problems. Not having a root shell
2143 around can lead to problems if pam has changed too much from your
2144 starting point to allow continued authentication after the upgrade.
2148 When upgrading the boot ZFS pool to a new version, always follow
2151 1.) recompile and reinstall the ZFS boot loader and boot block
2152 (this is part of "make buildworld" and "make installworld")
2154 2.) update the ZFS boot block on your boot drive
2156 The following example updates the ZFS boot block on the first
2157 partition (freebsd-boot) of a GPT partitioned drive ad0:
2158 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2160 Non-boot pools do not need these updates.
2164 If you are updating from a prior version of FreeBSD (even one just
2165 a few days old), you should follow this procedure. It is the most
2166 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2168 make kernel-toolchain
2169 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2170 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2172 To test a kernel once
2173 ---------------------
2174 If you just want to boot a kernel once (because you are not sure
2175 if it works, or if you want to boot a known bad kernel to provide
2176 debugging information) run
2177 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2178 nextboot -k testkernel
2180 To just build a kernel when you know that it won't mess you up
2181 --------------------------------------------------------------
2182 This assumes you are already running a CURRENT system. Replace
2183 ${arch} with the architecture of your machine (e.g. "i386",
2184 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2186 cd src/sys/${arch}/conf
2187 config KERNEL_NAME_HERE
2188 cd ../compile/KERNEL_NAME_HERE
2193 If this fails, go to the "To build a kernel" section.
2195 To rebuild everything and install it on the current system.
2196 -----------------------------------------------------------
2197 # Note: sometimes if you are running current you gotta do more than
2198 # is listed here if you are upgrading from a really old current.
2200 <make sure you have good level 0 dumps>
2202 make kernel KERNCONF=YOUR_KERNEL_HERE
2204 <reboot in single user> [3]
2211 To cross-install current onto a separate partition
2212 --------------------------------------------------
2213 # In this approach we use a separate partition to hold
2214 # current's root, 'usr', and 'var' directories. A partition
2215 # holding "/", "/usr" and "/var" should be about 2GB in
2218 <make sure you have good level 0 dumps>
2221 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2222 <maybe newfs current's root partition>
2223 <mount current's root partition on directory ${CURRENT_ROOT}>
2224 make installworld DESTDIR=${CURRENT_ROOT}
2225 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2226 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2227 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2228 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2229 <reboot into current>
2230 <do a "native" rebuild/install as described in the previous section>
2231 <maybe install compatibility libraries from ports/misc/compat*>
2235 To upgrade in-place from stable to current
2236 ----------------------------------------------
2237 <make sure you have good level 0 dumps>
2239 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2241 <reboot in single user> [3]
2248 Make sure that you've read the UPDATING file to understand the
2249 tweaks to various things you need. At this point in the life
2250 cycle of current, things change often and you are on your own
2251 to cope. The defaults can also change, so please read ALL of
2252 the UPDATING entries.
2254 Also, if you are tracking -current, you must be subscribed to
2255 freebsd-current@freebsd.org. Make sure that before you update
2256 your sources that you have read and understood all the recent
2257 messages there. If in doubt, please track -stable which has
2258 much fewer pitfalls.
2260 [1] If you have third party modules, such as vmware, you
2261 should disable them at this point so they don't crash your
2264 [3] From the bootblocks, boot -s, and then do
2269 adjkerntz -i # if CMOS is wall time
2270 Also, when doing a major release upgrade, it is required that
2271 you boot into single user mode to do the installworld.
2273 [4] Note: This step is non-optional. Failure to do this step
2274 can result in a significant reduction in the functionality of the
2275 system. Attempting to do it by hand is not recommended and those
2276 that pursue this avenue should read this file carefully, as well
2277 as the archives of freebsd-current and freebsd-hackers mailing lists
2278 for potential gotchas. The -U option is also useful to consider.
2279 See mergemaster(8) for more information.
2281 [5] Usually this step is a noop. However, from time to time
2282 you may need to do this if you get unknown user in the following
2283 step. It never hurts to do it all the time. You may need to
2284 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2285 install) after the buildworld before this step if you last updated
2286 from current before 20130425 or from -stable before 20130430.
2288 [6] This only deletes old files and directories. Old libraries
2289 can be deleted by "make delete-old-libs", but you have to make
2290 sure that no program is using those libraries anymore.
2292 [8] In order to have a kernel that can run the 4.x binaries needed to
2293 do an installworld, you must include the COMPAT_FREEBSD4 option in
2294 your kernel. Failure to do so may leave you with a system that is
2295 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2296 required to run the 5.x binaries on more recent kernels. And so on
2297 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2299 Make sure that you merge any new devices from GENERIC since the
2300 last time you updated your kernel config file.
2302 [9] When checking out sources, you must include the -P flag to have
2303 cvs prune empty directories.
2305 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2306 "?=" instead of the "=" assignment operator, so that buildworld can
2307 override the CPUTYPE if it needs to.
2309 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2310 not on the command line, or in /etc/make.conf. buildworld will
2311 warn if it is improperly defined.
2314 This file contains a list, in reverse chronological order, of major
2315 breakages in tracking -current. It is not guaranteed to be a complete
2316 list of such breakages, and only contains entries since October 10, 2007.
2317 If you need to see UPDATING entries from before that date, you will need
2318 to fetch an UPDATING file from an older FreeBSD release.
2320 Copyright information:
2322 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2324 Redistribution, publication, translation and use, with or without
2325 modification, in full or in part, in any form or format of this
2326 document are permitted without further permission from the author.
2328 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2329 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2330 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2331 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2332 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2333 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2334 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2335 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2336 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2337 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2338 POSSIBILITY OF SUCH DAMAGE.
2340 Contact Warner Losh if you have any questions about your use of