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 20150630: p14 FreeBSD-EN-15:08.sendmail [revised]
20 FreeBSD-EN-15:09.xlocale
21 FreeBSD-EN-15:10.iconv
23 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
25 Fix inconsistency between locale and rune locale states.
28 Improved iconv(3) UTF-7 support. [EN-15:10]
30 20150618: p13 FreeBSD-EN-15:08.sendmail
31 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
33 20150612: p12 FreeBSD-SA-15:10.openssl
34 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
36 20150609: p11 FreeBSD-EN-15:06.file
39 Updated base system file(1) to 5.22 to address multiple denial
40 of service issues. [EN-15:06]
42 Improved reliability of ZFS when TRIM/UNMAP and/or L2ARC is used.
45 20150513: p10 FreeBSD-EN-15:04.freebsd-update
48 Fix bug with freebsd-update(8) that does not ensure the previous
49 upgrade was completed. [EN-15:04]
51 Fix deadlock on reboot with UFS tuned with SU+J. [EN-15:05]
53 20150407: p9 FreeBSD-SA-15:04.igmp [revised]
55 FreeBSD-SA-15:08.bsdinstall
58 Improved patch for SA-15:04.igmp.
60 Fix multiple vulnerabilities of ntp. [SA-15:07]
62 Fix bsdinstall(8) insecure default GELI keyfile permissions. [SA-15:08]
64 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
67 Fix patch for SA-15:06.openssl.
69 20150319: p7 FreeBSD-SA-15:06.openssl
70 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
72 20150225: p6 FreeBSD-SA-15:04.igmp
74 FreeBSD-EN-15:02.openssl
75 FreeBSD-EN-15:03.freebsd-update
77 Fix integer overflow in IGMP protocol. [SA-15:04]
79 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
81 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
83 Fix freebsd-update libraries update ordering issue. [EN-15:03]
85 20150127: p5 FreeBSD-SA-15:02.kmem
88 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
89 vulnerability. [SA-15:02]
91 Fix SCTP stream reset vulnerability. [SA-15:03]
93 20150114: p4 FreeBSD-SA-15:01.openssl
94 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
96 20141223: p3 FreeBSD-SA-14:31.ntp
97 FreeBSD-EN-14:13.freebsd-update
99 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
100 Fix directory deletion issue in freebsd-update. [EN-14:13]
102 20141217: p2 FreeBSD-SA-14:30.unbound
103 Fix unbound remote denial of service vulnerability.
105 20141210: p1 FreeBSD-SA-14:27.stdio
106 FreeBSD-SA-14:28.file
108 Fix buffer overflow in stdio. [SA-14:27]
110 Fix multiple vulnerabilities in file(1) and libmagic(3).
114 The ofwfb driver, used to provide a graphics console on PowerPC when
115 using vt(4), no longer allows mmap() of all of physical memory. This
116 will prevent Xorg on PowerPC with some ATI graphics cards from
117 initializing properly unless x11-servers/xorg-server is updated to
121 The libatf-c and libatf-c++ major versions were downgraded to 0 and
122 1 respectively to match the upstream numbers. They were out of
123 sync because, when they were originally added to FreeBSD, the
124 upstream versions were not respected. These libraries are private
125 and not yet built by default, so renumbering them should be a
126 non-issue. However, unclean source trees will yield broken test
127 programs once the operator executes "make delete-old-libs" after a
130 Additionally, the atf-sh binary was made private by moving it into
131 /usr/libexec/. Already-built shell test programs will keep the
132 path to the old binary so they will break after "make delete-old"
135 If you are using WITH_TESTS=yes (not the default), wipe the object
136 tree and rebuild from scratch to prevent spurious test failures.
137 This is only needed once: the misnumbered libraries and misplaced
138 binaries have been added to OptionalObsoleteFiles.inc so they will
139 be removed during a clean upgrade.
142 The ixgbe tunables now match their sysctl counterparts, for example:
143 hw.ixgbe.enable_aim => hw.ix.enable_aim
144 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
147 The NFSv4.1 server committed by r269398 changes the internal
148 function call interfaces used between the NFS and krpc modules.
149 As such, __FreeBSD_version was bumped.
152 The default unbound configuration has been modified to address
153 issues with reverse lookups on networks that use private
154 address ranges. If you use the local_unbound service, run
155 "service local_unbound setup" as root to regenerate your
156 configuration, then "service local_unbound reload" to load the
160 It is no longer necessary to include the dwarf version in your DEBUG
161 options in your kernel config file. The bug that required it to be
162 placed in the config file has bene fixed. DEBUG should now just
163 contain -g. The build system will automatically update things
164 to do the right thing.
167 Several ABI breaking changes were merged to CTL and new iSCSI code.
168 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
169 iscsictl need to be rebuilt to work with a new kernel.
172 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
173 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
174 which differs from the behaviour controlled by this knob.)
177 On i386 and amd64 systems, the onifconsole flag is now set by default
178 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
179 as a login TTY if it is set in the bootloader as an active kernel
180 console. No changes in behavior should result otherwise. To revert to
181 the previous behavior, set ttyu0 to "off" in /etc/ttys.
184 Clang and llvm have been upgraded to 3.4.1 release.
187 Clang and llvm have been upgraded to 3.4 release.
190 If a Makefile in a tests/ directory was auto-generating a Kyuafile
191 instead of providing an explicit one, this would prevent such
192 Makefile from providing its own Kyuafile in the future during
193 NO_CLEAN builds. This has been fixed in the Makefiles but manual
194 intervention is needed to clean an objdir if you use NO_CLEAN:
195 # find /usr/obj -name Kyuafile | xargs rm -f
198 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
199 capability mode support. Please note that enabling the feature in
200 kernel is still highly recommended.
203 OpenSSH is now built with sandbox support, and will use sandbox as
204 the default privilege separation method. This requires Capsicum
205 capability mode support in kernel.
208 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
209 been deprecated and will not be part of FreeBSD 11.0 and later
210 releases. If you use this driver, please consider switching to
211 the nfe(4) driver instead.
217 The behavior of gss_pseudo_random() for the krb5 mechanism
218 has changed, for applications requesting a longer random string
219 than produced by the underlying enctype's pseudo-random() function.
220 In particular, the random string produced from a session key of
221 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
222 be different at the 17th octet and later, after this change.
223 The counter used in the PRF+ construction is now encoded as a
224 big-endian integer in accordance with RFC 4402.
225 __FreeBSD_version is bumped to 1000701.
228 The WITHOUT_ATF build knob has been removed and its functionality
229 has been subsumed into the more generic WITHOUT_TESTS. If you were
230 using the former to disable the build of the ATF libraries, you
231 should change your settings to use the latter.
234 The default version of mtree is nmtree which is obtained from
235 NetBSD. The output is generally the same, but may vary
236 slightly. If you found you need identical output adding
237 "-F freebsd9" to the command line should do the trick. For the
238 time being, the old mtree is available as fmtree.
241 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
242 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
243 1.1.4_8 and verify bsdyml not linked in, before running "make
245 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
247 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
250 The rc.d/jail script has been updated to support jail(8)
251 configuration file. The "jail_<jname>_*" rc.conf(5) variables
252 for per-jail configuration are automatically converted to
253 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
254 This is transparently backward compatible. See below about some
255 incompatibilities and rc.conf(5) manual page for more details.
257 These variables are now deprecated in favor of jail(8) configuration
258 file. One can use "rc.d/jail config <jname>" command to generate
259 a jail(8) configuration file in /var/run/jail.<jname>.conf without
260 running the jail(8) utility. The default pathname of the
261 configuration file is /etc/jail.conf and can be specified by
262 using $jail_conf or $jail_<jname>_conf variables.
264 Please note that jail_devfs_ruleset accepts an integer at
265 this moment. Please consider to rewrite the ruleset name
269 BIND has been removed from the base system. If all you need
270 is a local resolver, simply enable and start the local_unbound
271 service instead. Otherwise, several versions of BIND are
272 available in the ports tree. The dns/bind99 port is one example.
274 With this change, nslookup(1) and dig(1) are no longer in the base
275 system. Users should instead use host(1) and drill(1) which are
276 in the base system. Alternatively, nslookup and dig can
277 be obtained by installing the dns/bind-tools port.
280 With the addition of unbound(8), a new unbound user is now
281 required during installworld. "mergemaster -p" can be used to
282 add the user prior to installworld, as documented in the handbook.
285 OpenSSH is now built with DNSSEC support, and will by default
286 silently trust signed SSHFP records. This can be controlled with
287 the VerifyHostKeyDNS client configuration setting. DNSSEC support
288 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
291 The GNU Compiler Collection and C++ standard library (libstdc++)
292 are no longer built by default on platforms where clang is the system
293 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
297 The PROCDESC kernel option is now part of the GENERIC kernel
298 configuration and is required for the rwhod(8) to work.
299 If you are using custom kernel configuration, you should include
303 The API and ABI related to the Capsicum framework was modified
304 in backward incompatible way. The userland libraries and programs
305 have to be recompiled to work with the new kernel. This includes the
306 following libraries and programs, but the whole buildworld is
307 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
308 kdump, procstat, rwho, rwhod, uniq.
311 AES-NI intrinsic support has been added to gcc. The AES-NI module
312 has been updated to use this support. A new gcc is required to build
313 the aesni module on both i386 and amd64.
316 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
317 Thus "device padlock_rng" and "device rdrand_rng" should be
318 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
321 WITH_ICONV has been split into two feature sets. WITH_ICONV now
322 enables just the iconv* functionality and is now on by default.
323 WITH_LIBICONV_COMPAT enables the libiconv api and link time
324 compatability. Set WITHOUT_ICONV to build the old way.
325 If you have been using WITH_ICONV before, you will very likely
326 need to turn on WITH_LIBICONV_COMPAT.
329 INVARIANTS option now enables DEBUG for code with OpenSolaris and
330 Illumos origin, including ZFS. If you have INVARIANTS in your
331 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
333 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
334 locks if WITNESS option was set. Because that generated a lot of
335 witness(9) reports and all of them were believed to be false
336 positives, this is no longer done. New option OPENSOLARIS_WITNESS
337 can be used to achieve the previous behavior.
340 Timer values in IPv6 data structures now use time_uptime instead
341 of time_second. Although this is not a user-visible functional
342 change, userland utilities which directly use them---ndp(8),
343 rtadvd(8), and rtsold(8) in the base system---need to be updated
347 find -delete can now delete the pathnames given as arguments,
348 instead of only files found below them or if the pathname did
349 not contain any slashes. Formerly, the following error message
352 find: -delete: <path>: relative path potentially not safe
354 Deleting the pathnames given as arguments can be prevented
355 without error messages using -mindepth 1 or by changing
356 directory and passing "." as argument to find. This works in the
357 old as well as the new version of find.
360 Behavior of devfs rules path matching has been changed.
361 Pattern is now always matched against fully qualified devfs
362 path and slash characters must be explicitly matched by
363 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
364 subdirectories must be reviewed.
367 The default ARM ABI has changed to the ARM EABI. The old ABI is
368 incompatible with the ARM EABI and all programs and modules will
369 need to be rebuilt to work with a new kernel.
371 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
373 NOTE: Support for the old ABI will be removed in the future and
374 users are advised to upgrade.
377 pkg_install has been disconnected from the build if you really need it
378 you should add WITH_PKGTOOLS in your src.conf(5).
381 Most of network statistics structures were changed to be able
382 keep 64-bits counters. Thus all tools, that work with networking
383 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
386 Fix targets that run multiple make's to use && rather than ;
387 so that subsequent steps depend on success of previous.
389 NOTE: if building 'universe' with -j* on stable/8 or stable/9
390 it would be better to start the build using bmake, to avoid
391 overloading the machine.
394 Fix a bug that allowed a tracing process (e.g. gdb) to write
395 to a memory-mapped file in the traced process's address space
396 even if neither the traced process nor the tracing process had
397 write access to that file.
400 CVS has been removed from the base system. An exact copy
401 of the code is available from the devel/cvs port.
404 Some people report the following error after the switch to bmake:
406 make: illegal option -- J
407 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
409 *** [buildworld] Error code 2
411 this likely due to an old instance of make in
412 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
413 which src/Makefile will use that blindly, if it exists, so if
414 you see the above error:
416 rm -rf `make -V MAKEPATH`
421 Use bmake by default.
422 Whereas before one could choose to build with bmake via
423 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
424 make. The goal is to remove these knobs for 10-RELEASE.
426 It is worth noting that bmake (like gmake) treats the command
427 line as the unit of failure, rather than statements within the
428 command line. Thus '(cd some/where && dosomething)' is safer
429 than 'cd some/where; dosomething'. The '()' allows consistent
430 behavior in parallel build.
433 Fix a bug that allows NFS clients to issue READDIR on files.
436 The WITHOUT_IDEA option has been removed because
437 the IDEA patent expired.
440 The sysctl which controls TRIM support under ZFS has been renamed
441 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
445 The mergemaster command now uses the default MAKEOBJDIRPREFIX
446 rather than creating it's own in the temporary directory in
447 order allow access to bootstrapped versions of tools such as
448 install and mtree. When upgrading from version of FreeBSD where
449 the install command does not support -l, you will need to
450 install a new mergemaster command if mergemaster -p is required.
451 This can be accomplished with the command (cd src/usr.sbin/mergemaster
455 Legacy ATA stack, disabled and replaced by new CAM-based one since
456 FreeBSD 9.0, completely removed from the sources. Kernel modules
457 atadisk and atapi*, user-level tools atacontrol and burncd are
458 removed. Kernel option `options ATA_CAM` is now permanently enabled
462 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
463 and socketpair(2). Software, in particular Kerberos, may
464 automatically detect and use these during building. The resulting
465 binaries will not work on older kernels.
468 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
469 information, see the respective 20130304 entry).
472 Recent commits to callout(9) changed the size of struct callout,
473 so the KBI is probably heavily disturbed. Also, some functions
474 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
475 by macros. Every kernel module using it won't load, so rebuild
478 The ctl device has been re-enabled in GENERIC for i386 and amd64,
479 but does not initialize by default (because of the new CTL_DISABLE
480 option) to save memory. To re-enable it, remove the CTL_DISABLE
481 option from the kernel config file or set kern.cam.ctl.disable=0
482 in /boot/loader.conf.
485 The ctl device has been disabled in GENERIC for i386 and amd64.
486 This was done due to the extra memory being allocated at system
487 initialisation time by the ctl driver which was only used if
488 a CAM target device was created. This makes a FreeBSD system
489 unusable on 128MB or less of RAM.
492 A new compression method (lz4) has been merged to -HEAD. Please
493 refer to zpool-features(7) for more information.
495 Please refer to the "ZFS notes" section of this file for information
496 on upgrading boot ZFS pools.
499 A BSD-licensed patch(1) variant has been added and is installed
500 as bsdpatch, being the GNU version the default patch.
501 To inverse the logic and use the BSD-licensed one as default,
502 while having the GNU version installed as gnupatch, rebuild
503 and install world with the WITH_BSD_PATCH knob set.
506 Due to the use of the new -l option to install(1) during build
507 and install, you must take care not to directly set the INSTALL
508 make variable in your /etc/make.conf, /etc/src.conf, or on the
509 command line. If you wish to use the -C flag for all installs
510 you may be able to add INSTALL+=-C to /etc/make.conf or
514 The install(1) option -M has changed meaning and now takes an
515 argument that is a file or path to append logs to. In the
516 unlikely event that -M was the last option on the command line
517 and the command line contained at least two files and a target
518 directory the first file will have logs appended to it. The -M
519 option served little practical purpose in the last decade so its
520 use is expected to be extremely rare.
523 After switching to Clang as the default compiler some users of ZFS
524 on i386 systems started to experience stack overflow kernel panics.
525 Please consider using 'options KSTACK_PAGES=4' in such configurations.
528 GEOM_LABEL now mangles label names read from file system metadata.
529 Mangling affect labels containing spaces, non-printable characters,
530 '%' or '"'. Device names in /etc/fstab and other places may need to
534 By default, only the 10 most recent kernel dumps will be saved. To
535 restore the previous behaviour (no limit on the number of kernel dumps
536 stored in the dump directory) add the following line to /etc/rc.conf:
541 With the addition of auditdistd(8), a new auditdistd user is now
542 required during installworld. "mergemaster -p" can be used to
543 add the user prior to installworld, as documented in the handbook.
546 The sin6_scope_id member variable in struct sockaddr_in6 is now
547 filled by the kernel before passing the structure to the userland via
548 sysctl or routing socket. This means the KAME-specific embedded scope
549 id in sin6_addr.s6_addr[2] is always cleared in userland application.
550 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
551 __FreeBSD_version is bumped to 1000025.
554 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
555 This means that the world and kernel will be compiled with clang
556 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
557 and /usr/bin/cpp. To disable this behavior and revert to building
558 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
559 of current may need to bootstrap WITHOUT_CLANG first if the clang
560 build fails (its compatibility window doesn't extend to the 9 stable
564 The IPFIREWALL_FORWARD kernel option has been removed. Its
565 functionality now turned on by default.
568 The ZERO_COPY_SOCKET kernel option has been removed and
569 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
570 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
571 mechanism which is not safe and may result in kernel crashes.
572 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
573 driver supports disposeable external page sized mbuf storage.
574 Proper replacements for both zero-copy mechanisms are under
575 consideration and will eventually lead to complete removal
576 of the two kernel options.
579 The IPv4 network stack has been converted to network byte
580 order. The following modules need to be recompiled together
581 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
582 pf(4), ipfw(4), ng_ipfw(4), stf(4).
585 Support for non-MPSAFE filesystems was removed from VFS. The
586 VFS_VERSION was bumped, all filesystem modules shall be
590 All the non-MPSAFE filesystems have been disconnected from
591 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
592 portalfs, smbfs, xfs.
595 The interface cloning API and ABI has changed. The following
596 modules need to be recompiled together with kernel:
597 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
598 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
599 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
602 The sdhci driver was split in two parts: sdhci (generic SD Host
603 Controller logic) and sdhci_pci (actual hardware driver).
604 No kernel config modifications are required, but if you
605 load sdhc as a module you must switch to sdhci_pci instead.
608 Import the FUSE kernel and userland support into base system.
611 The GNU sort(1) program has been removed since the BSD-licensed
612 sort(1) has been the default for quite some time and no serious
613 problems have been reported. The corresponding WITH_GNU_SORT
617 The pfil(9) API/ABI for AF_INET family has been changed. Packet
618 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
622 The net80211(4) ABI has been changed to allow for improved driver
623 PS-POLL and power-save support. All wireless drivers need to be
624 recompiled to work with the new kernel.
627 The random(4) support for the VIA hardware random number
628 generator (`PADLOCK') is no longer enabled unconditionally.
629 Add the padlock_rng device in the custom kernel config if
630 needed. The GENERIC kernels on i386 and amd64 do include the
631 device, so the change only affects the custom kernel
635 The pf(4) packet filter ABI has been changed. pfctl(8) and
636 snmp_pf module need to be recompiled to work with new kernel.
639 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
640 to -HEAD. Pools that have empty_bpobj in active state can not be
641 imported read-write with ZFS implementations that do not support
642 this feature. For more information read the zpool-features(5)
646 The sparc64 ZFS loader has been changed to no longer try to auto-
647 detect ZFS providers based on diskN aliases but now requires these
648 to be explicitly listed in the OFW boot-device environment variable.
651 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
652 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
653 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
656 The following sysctls and tunables have been renamed for consistency
657 with other variables:
658 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
659 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
662 The sort utility has been replaced with BSD sort. For now, GNU sort
663 is also available as "gnusort" or the default can be set back to
664 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
665 installed as "bsdsort".
668 A new version of ZFS (pool version 5000) has been merged to -HEAD.
669 Starting with this version the old system of ZFS pool versioning
670 is superseded by "feature flags". This concept enables forward
671 compatibility against certain future changes in functionality of ZFS
672 pools. The first read-only compatible "feature flag" for ZFS pools
673 is named "com.delphix:async_destroy". For more information
674 read the new zpool-features(5) manual page.
675 Please refer to the "ZFS notes" section of this file for information
676 on upgrading boot ZFS pools.
679 The malloc(3) implementation embedded in libc now uses sources imported
680 as contrib/jemalloc. The most disruptive API change is to
681 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
682 delete it prior to installworld, and optionally re-create it using the
683 new format after rebooting. See malloc.conf(5) for details
684 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
688 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
689 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
690 now spelled mips. This is to aid compatibility with third-party
691 software that expects this naming scheme in uname(3). Little-endian
692 settings are unchanged. If you are updating a big-endian mips64 machine
693 from before this change, you may need to set MACHINE_ARCH=mips64 in
694 your environment before the new build system will recognize your machine.
697 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
701 Now unix domain sockets behave "as expected" on nullfs(5). Previously
702 nullfs(5) did not pass through all behaviours to the underlying layer,
703 as a result if we bound to a socket on the lower layer we could connect
704 only to the lower path; if we bound to the upper layer we could connect
705 only to the upper path. The new behavior is one can connect to both the
706 lower and the upper paths regardless what layer path one binds to.
709 The getifaddrs upgrade path broken with 20111215 has been restored.
710 If you have upgraded in between 20111215 and 20120209 you need to
711 recompile libc again with your kernel. You still need to recompile
712 world to be able to configure CARP but this restriction already
716 The set_rcvar() function has been removed from /etc/rc.subr. All
717 base and ports rc.d scripts have been updated, so if you have a
718 port installed with a script in /usr/local/etc/rc.d you can either
719 hand-edit the rcvar= line, or reinstall the port.
721 An easy way to handle the mass-update of /etc/rc.d:
722 rm /etc/rc.d/* && mergemaster -i
725 panic(9) now stops other CPUs in the SMP systems, disables interrupts
726 on the current CPU and prevents other threads from running.
727 This behavior can be reverted using the kern.stop_scheduler_on_panic
729 The new behavior can be incompatible with kern.sync_on_panic.
732 The carp(4) facility has been changed significantly. Configuration
733 of the CARP protocol via ifconfig(8) has changed, as well as format
734 of CARP events submitted to devd(8) has changed. See manual pages
735 for more information. The arpbalance feature of carp(4) is currently
736 not supported anymore.
738 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
739 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
740 need to be recompiled.
743 The acpi_wmi(4) status device /dev/wmistat has been renamed to
747 The option VFS_ALLOW_NONMPSAFE option has been added in order to
748 explicitely support non-MPSAFE filesystems.
749 It is on by default for all supported platform at this present
753 The broken amd(4) driver has been replaced with esp(4) in the amd64,
754 i386 and pc98 GENERIC kernel configuration files.
757 sysinstall has been removed
760 The stable/9 branch created in subversion. This corresponds to the
761 RELENG_9 branch in CVS.
764 This commit modifies vfs_register() so that it uses a hash
765 calculation to set vfc_typenum, which is enabled by default.
766 The first time a system is booted after this change, the
767 vfc_typenum values will change for all file systems. The
768 main effect of this is a change to the NFS server file handles
769 for file systems that use vfc_typenum in their fsid, such as ZFS.
770 It will, however, prevent vfc_typenum from changing when file
771 systems are loaded in a different order for subsequent reboots.
772 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
773 until you are ready to remount all NFS clients after a reboot.
776 Bump the shared library version numbers for libraries that
777 do not use symbol versioning, have changed the ABI compared
778 to stable/8 and which shared library version was not bumped.
779 Done as part of 9.0-RELEASE cycle.
782 During the merge of Capsicum features, the fget(9) KPI was modified.
783 This may require the rebuilding of out-of-tree device drivers --
784 issues have been reported specifically with the nVidia device driver.
785 __FreeBSD_version is bumped to 900041.
787 Also, there is a period between 20110811 and 20110814 where the
788 special devices /dev/{stdin,stdout,stderr} did not work correctly.
789 Building world from a kernel during that window may not work.
792 The packet filter (pf) code has been updated to OpenBSD 4.5.
793 You need to update userland tools to be in sync with kernel.
794 This update breaks backward compatibility with earlier pfsync(4)
795 versions. Care must be taken when updating redundant firewall setups.
798 The following sysctls and tunables are retired on x86 platforms:
800 machdep.hlt_logical_cpus
801 The following sysctl is retired:
802 machdep.hyperthreading_allowed
803 The sysctls were supposed to provide a way to dynamically offline and
804 online selected CPUs on x86 platforms, but the implementation has not
805 been reliable especially with SCHED_ULE scheduler.
806 machdep.hyperthreading_allowed tunable is still available to ignore
807 hyperthreading CPUs at OS level.
808 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
809 where X is an APIC ID of a CPU. Be advised, though, that disabling
810 CPUs in non-uniform fashion will result in non-uniform topology and
811 may lead to sub-optimal system performance with SCHED_ULE, which is
815 cpumask_t type is retired and cpuset_t is used in order to describe
819 Changes to ifconfig(8) for dynamic address family detection mandate
820 that you are running a kernel of 20110525 or later. Make sure to
821 follow the update procedure to boot a new kernel before installing
825 Support for sun4v architecture is officially dropped
828 Several KPI breaking changes have been committed to the mii(4) layer,
829 the PHY drivers and consequently some Ethernet drivers using mii(4).
830 This means that miibus.ko and the modules of the affected Ethernet
831 drivers need to be recompiled.
833 Note to kernel developers: Given that the OUI bit reversion problem
834 was fixed as part of these changes all mii(4) commits related to OUIs,
835 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
836 handling, no longer can be merged verbatim to stable/8 and previous
840 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
841 into their kernel configurations along with 'device pci'.
844 The default NFS client is now the new NFS client, so fstype "newnfs"
845 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
846 Although mounts via fstype "nfs" will usually work without userland
847 changes, it is recommended that the mount(8) and mount_nfs(8)
848 commands be rebuilt from sources and that a link to mount_nfs called
849 mount_oldnfs be created. The new client is compiled into the
850 kernel with "options NFSCL" and this is needed for diskless root
851 file systems. The GENERIC kernel configs have been changed to use
852 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
853 To use the regular/old client, you can "mount -t oldnfs ...". For
854 a diskless root file system, you must also include a line like:
856 vfs.root.mountfrom="oldnfs:"
858 in the boot/loader.conf on the root fs on the NFS server to make
859 a diskless root fs use the old client.
862 The GENERIC kernels for all architectures now default to the new
863 CAM-based ATA stack. It means that all legacy ATA drivers were
864 removed and replaced by respective CAM drivers. If you are using
865 ATA device names in /etc/fstab or other places, make sure to update
866 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
867 where 'Y's are the sequential numbers starting from zero for each type
868 in order of detection, unless configured otherwise with tunables,
869 see cam(4)). There will be symbolic links created in /dev/ to map
870 old adX devices to the respective adaY. They should provide basic
871 compatibility for file systems mounting in most cases, but they do
872 not support old user-level APIs and do not have respective providers
873 in GEOM. Consider using updated management tools with new device names.
875 It is possible to load devices ahci, ata, siis and mvs as modules,
876 but option ATA_CAM should remain in kernel configuration to make ata
877 module work as CAM driver supporting legacy ATA controllers. Device ata
878 still can be used in modular fashion (atacore + ...). Modules atadisk
879 and atapi* are not used and won't affect operation in ATA_CAM mode.
880 Note that to use CAM-based ATA kernel should include CAM devices
881 scbus, pass, da (or explicitly ada), cd and optionally others. All of
882 them are parts of the cam module.
884 ataraid(4) functionality is now supported by the RAID GEOM class.
885 To use it you can load geom_raid kernel module and use graid(8) tool
886 for management. Instead of /dev/arX device names, use /dev/raid/rX.
888 No kernel config options or code have been removed, so if a problem
889 arises, please report it and optionally revert to the old ATA stack.
890 In order to do it you can remove from the kernel config:
895 , and instead add back:
896 device atadisk # ATA disk drives
897 device ataraid # ATA RAID drives
898 device atapicd # ATAPI CDROM drives
899 device atapifd # ATAPI floppy drives
900 device atapist # ATAPI tape drives
903 The default NFS server has been changed to the new server, which
904 was referred to as the experimental server. If you need to switch
905 back to the old NFS server, you must now put the "-o" option on
906 both the mountd and nfsd commands. This can be done using the
907 mountd_flags and nfs_server_flags rc.conf variables until an
908 update to the rc scripts is committed, which is coming soon.
911 The GNU Objective-C runtime library (libobjc), and other Objective-C
912 related components have been removed from the base system. If you
913 require an Objective-C library, please use one of the available ports.
916 ath(4) has been split into bus- and device- modules. if_ath contains
917 the HAL, the TX rate control and the network device code. if_ath_pci
918 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
919 contains the AHB glue. Users need to load both if_ath_pci and if_ath
920 in order to use ath on everything else.
922 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
923 need to load if_ath and if_ath_pci for ath(4) operation.
926 As part of the replacement of sysinstall, the process of building
927 release media has changed significantly. For details, please re-read
928 release(7), which has been updated to reflect the new build process.
931 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
932 is the last available version under GPLv2. It brings a number of new
933 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
934 4.1 and SSE 4.2), better support for powerpc64, a number of new
935 directives, and lots of other small improvements. See the ChangeLog
936 file in contrib/binutils for the full details.
939 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
940 compliant, and will now use half of hash for authentication.
941 This will break interoperability with all stacks (including all
942 actual FreeBSD versions) who implement
943 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
945 The only workaround with such peers is to use another HMAC
946 algorithm for IPsec ("phase 2") authentication.
949 Remove the uio_yield prototype and symbol. This function has
950 been misnamed since it was introduced and should not be
951 globally exposed with this name. The equivalent functionality
952 is now available using kern_yield(curthread->td_user_pri).
953 The function remains undocumented.
956 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
957 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
958 for scalar sysctls is defined but disabled. Code that needs
959 UQUAD to pass the type checking that must compile on older
960 systems where the define is not present can check against
961 __FreeBSD_version >= 900030.
963 The system dialog(1) has been replaced with a new version previously
964 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
965 with the previous version, but the libdialog associated with it has
966 a largely incompatible API. As such, the original version of libdialog
967 will be kept temporarily as libodialog, until its base system consumers
968 are replaced or updated. Bump __FreeBSD_version to 900030.
971 If you are trying to run make universe on a -stable system, and you get
972 the following warning:
973 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
974 unknown. config(8) likely too old."
975 or something similar to it, then you must upgrade your -stable system
976 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
977 stable/8) or build the config from the latest stable/8 branch and
978 install it on your system.
980 Prior to this date, building a current universe on 8-stable system from
981 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
982 error in the first kernel build phase. A new config on those old
983 systems will fix that problem for older versions of -current.
986 The TCP stack has been modified to allow Khelp modules to interact with
987 it via helper hook points and store per-connection data in the TCP
988 control block. Bump __FreeBSD_version to 900029. User space tools that
989 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
993 Generic IEEE 802.3 annex 31B full duplex flow control support has been
994 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
995 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
996 to take advantage of it instead of using custom implementations. This
997 means that these drivers now no longer unconditionally advertise
998 support for flow control but only do so if flow control is a selected
999 media option. This was implemented in the generic support that way in
1000 order to allow flow control to be switched on and off via ifconfig(8)
1001 with the PHY specific default to typically off in order to protect
1002 from unwanted effects. Consequently, if you used flow control with
1003 one of the above mentioned drivers you now need to explicitly enable
1004 it, for example via:
1005 ifconfig bge0 media auto mediaopt flowcontrol
1007 Along with the above mentioned changes generic support for setting
1008 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1009 e1000phy(4) as well as ip1000phy(4) have been converted to take
1010 advantage of it. This means that these drivers now no longer take the
1011 link0 parameter for selecting master mode but the master media option
1012 has to be used instead, for example like in the following:
1013 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1015 Selection of master mode now is also available with all other PHY
1016 drivers supporting 1000baseT.
1019 The TCP stack has received a significant update to add support for
1020 modularised congestion control and generally improve the clarity of
1021 congestion control decisions. Bump __FreeBSD_version to 900025. User
1022 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1023 sockstat) need to be recompiled.
1026 The man(1) utility has been replaced by a new version that no longer
1027 uses /etc/manpath.config. Please consult man.conf(5) for how to
1028 migrate local entries to the new format.
1031 The copyright strings printed by login(1) and sshd(8) at the time of a
1032 new connection have been removed to follow other operating systems and
1036 A workaround for a fixed ld bug has been removed in kernel code,
1037 so make sure that your system ld is built from sources after
1038 revision 210245 from 2010-07-19 (r211583 if building head kernel
1039 on stable/8, r211584 for stable/7; both from 2010-08-21).
1040 A symptom of incorrect ld version is different addresses for
1041 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1044 The $ipv6_prefer variable in rc.conf(5) has been split into
1045 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1047 The $ip6addrctl_policy is a variable to choose a pre-defined
1048 address selection policy set by ip6addrctl(8). A value
1049 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1052 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1053 flag (see an entry of 20090926) is set on an interface with no
1054 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1055 security reason. If you want IPv6 link-local address on all
1056 interfaces by default, set this to "YES".
1058 The old ipv6_prefer="YES" is equivalent to
1059 ipv6_activate_all_interfaces="YES" and
1060 ip6addrctl_policy="ipv6_prefer".
1063 DTrace has grown support for userland tracing. Due to this, DTrace is
1064 now i386 and amd64 only.
1065 dtruss(1) is now installed by default on those systems and a new
1066 kernel module is needed for userland tracing: fasttrap.
1067 No changes to your kernel config file are necessary to enable
1068 userland tracing, but you might consider adding 'STRIP=' and
1069 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1070 to have informative userland stack traces in DTrace (ustack).
1073 The acpi_aiboost(4) driver has been removed in favor of the new
1074 aibs(4) driver. You should update your kernel configuration file.
1077 BSD grep has been imported to the base system and it is built by
1078 default. It is completely BSD licensed, highly GNU-compatible, uses
1079 less memory than its GNU counterpart and has a small codebase.
1080 However, it is slower than its GNU counterpart, which is mostly
1081 noticeable for larger searches, for smaller ones it is measurable
1082 but not significant. The reason is complex, the most important factor
1083 is that we lack a modern and efficient regex library and GNU
1084 overcomes this by optimizing the searches internally. Future work
1085 on improving the regex performance is planned, for the meantime,
1086 users that need better performance, can build GNU grep instead by
1087 setting the WITH_GNU_GREP knob.
1090 Due to the import of powerpc64 support, all existing powerpc kernel
1091 configuration files must be updated with a machine directive like this:
1092 machine powerpc powerpc
1094 In addition, an updated config(8) is required to build powerpc kernels
1098 A new version of ZFS (version 15) has been merged to -HEAD.
1099 This version uses a python library for the following subcommands:
1100 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1101 For full functionality of these commands the following port must
1102 be installed: sysutils/py-zfs
1105 'vm_page's are now hashed by physical address to an array of mutexes.
1106 Currently this is only used to serialize access to hold_count. Over
1107 time the page queue mutex will be peeled away. This changes the size
1108 of pmap on every architecture. And requires all callers of vm_page_hold
1109 and vm_page_unhold to be updated.
1112 WITH_CTF can now be specified in src.conf (not recommended, there
1113 are some problems with static executables), make.conf (would also
1114 affect ports which do not use GNU make and do not override the
1115 compile targets) or in the kernel config (via "makeoptions
1117 When WITH_CTF was specified there before this was silently ignored,
1118 so make sure that WITH_CTF is not used in places which could lead
1119 to unwanted behavior.
1122 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1123 to allow 32-bit compatibility on non-x86 platforms. All kernel
1124 configurations on amd64 and ia64 platforms using these options must
1125 be modified accordingly.
1128 The utmp user accounting database has been replaced with utmpx,
1129 the user accounting interface standardized by POSIX.
1130 Unfortunately the semantics of utmp and utmpx don't match,
1131 making it practically impossible to support both interfaces.
1132 The user accounting database is used by tools like finger(1),
1133 last(1), talk(1), w(1) and ac(8).
1135 All applications in the base system use utmpx. This means only
1136 local binaries (e.g. from the ports tree) may still use these
1137 utmp database files. These applications must be rebuilt to make
1140 After the system has been upgraded, it is safe to remove the old
1141 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1142 assuming their contents is of no importance anymore. Old wtmp
1143 databases can only be used by last(1) and ac(8) after they have
1144 been converted to the new format using wtmpcvt(1).
1147 Introduce the kernel thread "deadlock resolver" (which can be enabled
1148 via the DEADLKRES option, see NOTES for more details) and the
1149 sleepq_type() function for sleepqueues.
1152 The rc.firewall and rc.firewall6 were unified, and
1153 rc.firewall6 and rc.d/ip6fw were removed.
1154 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1155 variables are obsoleted. Instead, the following new rc
1156 variables are added to rc.d/ipfw:
1158 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1159 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1160 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1162 The meanings correspond to the relevant IPv4 variables.
1168 The default terminal emulation for syscons(4) has been changed
1169 from cons25 to xterm on all platforms except pc98. This means
1170 that the /etc/ttys file needs to be updated to ensure correct
1171 operation of applications on the console.
1173 The terminal emulation style can be toggled per window by using
1174 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1175 options can be used to change the compile-time default back to
1178 To prevent graphical artifacts, make sure the TERM environment
1179 variable is set to match the terminal emulation that is being
1180 performed by syscons(4).
1183 The layout of the structure ieee80211req_scan_result has changed.
1184 Applications that require wireless scan results (e.g. ifconfig(8))
1185 from net80211 need to be recompiled.
1187 Applications such as wpa_supplicant(8) may require a full world
1188 build without using NO_CLEAN in order to get synchronized with the
1192 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1193 There's one kernel module for each firmware. Adding "device iwnfw"
1194 to the kernel configuration file means including all three firmware
1195 images inside the kernel. If you want to include just the one for
1196 your wireless card, use the devices iwn4965fw, iwn5000fw or
1200 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1201 into rc.d/netif. The changes are the following:
1203 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1204 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1205 Note that both variables need the "inet6" keyword at the head.
1207 Do not set $ipv6_network_interfaces manually if you do not
1208 understand what you are doing. It is not needed in most cases.
1210 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1213 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1214 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1216 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1217 all configured interfaces have "inet6 accept_rtadv" in the
1218 $ifconfig_IF_ipv6. These are for backward compatibility.
1220 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1221 functionality of interfaces with no corresponding
1222 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1223 and the default address selection policy of ip6addrctl(8)
1224 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1225 Note that if you want to configure IPv6 functionality on the
1226 disabled interfaces after boot, first you need to clear the flag by
1227 using ifconfig(8) like:
1229 ifconfig em0 inet6 -ifdisabled
1231 If YES, the default address selection policy is set as
1234 The default value of $ipv6_prefer is NO.
1236 4. If your system need to receive Router Advertisement messages,
1237 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1238 scripts automatically invoke rtsol(8) when the interface becomes
1239 UP. The Router Advertisement messages are used for SLAAC
1240 (State-Less Address AutoConfiguration).
1243 802.11s D3.03 support was committed. This is incompatible with the
1244 previous code, which was based on D3.0.
1247 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1248 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1249 control whether accepting Router Advertisement messages or not.
1250 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1251 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1252 The ifconfig(8) utility now supports these flags.
1255 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1256 mount(8) and -a option for df(1) to see them.
1259 The old tunable hw.bus.devctl_disable has been superseded by
1260 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1261 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1265 Remove the option STOP_NMI. The default action is now to use NMI only
1266 for KDB via the newly introduced function stop_cpus_hard() and
1267 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1270 The stable/8 branch created in subversion. This corresponds to the
1271 RELENG_8 branch in CVS.
1274 Bump the shared library version numbers for all libraries that do not
1275 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1276 __FreeBSD_version to 800105.
1279 Due to changes in the implementation of virtual network stack support,
1280 all network-related kernel modules must be recompiled. As this change
1281 breaks the ABI, bump __FreeBSD_version to 800104.
1284 The TOE interface to the TCP syncache has been modified to remove
1285 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1286 The cxgb driver is the only TOE consumer affected by this change, and
1287 needs to be recompiled along with the kernel. As this change breaks
1288 the ABI, bump __FreeBSD_version to 800103.
1291 Padding has been added to struct tcpcb, sackhint and tcpstat in
1292 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1293 maintaining the ABI. However, this change breaks the ABI, so bump
1294 __FreeBSD_version to 800102. User space tools that rely on the size of
1295 any of these structs (e.g. sockstat) need to be recompiled.
1298 The NFS_LEGACYRPC option has been removed along with the old kernel
1299 RPC implementation that this option selected. Kernel configurations
1300 may need to be adjusted.
1303 The network interface device nodes at /dev/net/<interface> have been
1304 removed. All ioctl operations can be performed the normal way using
1305 routing sockets. The kqueue functionality can generally be replaced
1306 with routing sockets.
1309 The documentation from the FreeBSD Documentation Project (Handbook,
1310 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1311 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1314 The ABI of various structures related to the SYSV IPC API have been
1315 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1316 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1320 Layout of struct vnet has changed as routing related variables were
1321 moved to their own Vimage module. Modules need to be recompiled. Bump
1322 __FreeBSD_version to 800099.
1325 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1326 respectively. As long as no more than 16 groups per process are used,
1327 no changes should be visible. When more than 16 groups are used, old
1328 binaries may fail if they call getgroups() or getgrouplist() with
1329 statically sized storage. Recompiling will work around this, but
1330 applications should be modified to use dynamically allocated storage
1331 for group arrays as POSIX.1-2008 does not cap an implementation's
1332 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1334 NFS and portalfs mounts may also be affected as the list of groups is
1335 truncated to 16. Users of NFS who use more than 16 groups, should
1336 take care that negative group permissions are not used on the exported
1337 file systems as they will not be reliable unless a GSSAPI based
1338 authentication method is used.
1341 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1342 option compiles in the support for adaptive spinning for lockmgrs
1343 which want to enable it. The lockinit() function now accepts the flag
1344 LK_ADAPTIVE in order to make the lock object subject to adaptive
1345 spinning when both held in write and read mode.
1348 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1349 changed. User applications that use this ioctl need to be rebuilt.
1352 The layout of struct thread has changed. Kernel and modules need to
1356 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1357 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1360 window(1) has been removed from the base system. It can now be
1361 installed from ports. The port is called misc/window.
1364 The way we are storing and accessing `routing table' entries has
1365 changed. Programs reading the FIB, like netstat, need to be
1369 A new netisr implementation has been added for FreeBSD 8. Network
1370 file system modules, such as igmp, ipdivert, and others, should be
1372 Bump __FreeBSD_version to 800096.
1375 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1379 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1380 Bump __FreeBSD_version to 800094.
1383 Add mnt_xflag field to 'struct mount'. File system modules need to be
1385 Bump __FreeBSD_version to 800093.
1388 The compiling option ADAPTIVE_SX has been retired while it has been
1389 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1390 The KPI for sx_init_flags() changes as accepting flags:
1391 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1392 been introduced in order to handle the reversed logic.
1393 Bump __FreeBSD_version to 800092.
1396 Add support for hierarchical jails. Remove global securelevel.
1397 Bump __FreeBSD_version to 800091.
1400 The layout of struct vnet_net has changed, therefore modules
1402 Bump __FreeBSD_version to 800090.
1405 The newly imported zic(8) produces a new format in the output. Please
1406 run tzsetup(8) to install the newly created data to /etc/localtime.
1409 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1410 hw.usb.* and is now consistent again with previous releases.
1413 802.11 monitor mode support was revised and driver api's were changed.
1414 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1415 of DLT_IEEE802_11. No user-visible data structures were changed but
1416 applications that use DLT_IEEE802_11 may require changes.
1417 Bump __FreeBSD_version to 800088.
1420 The layout of the following structs has changed: sysctl_oid,
1421 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1422 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1423 panics may be experienced. World rebuild is required for
1424 correctly checking networking state from userland.
1425 Bump __FreeBSD_version to 800085.
1428 MLDv2 and Source-Specific Multicast (SSM) have been merged
1429 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1430 The implementation of SSM within FreeBSD's IPv6 stack closely
1431 follows the IPv4 implementation.
1433 For kernel developers:
1435 * The most important changes are that the ip6_output() and
1436 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1437 and this lock has been downgraded to a non-recursive mutex.
1439 * As with the changes to the IPv4 stack to support SSM, filtering
1440 of inbound multicast traffic must now be performed by transport
1441 protocols within the IPv6 stack. This does not apply to TCP and
1442 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1444 * The KPIs used by IPv6 multicast are similar to those used by
1445 the IPv4 stack, with the following differences:
1446 * im6o_mc_filter() is analogous to imo_multicast_filter().
1447 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1448 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1449 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1450 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1451 for MLDv1 have an additional 'timer' argument which is used to
1452 jitter the initial membership report for the solicited-node
1453 multicast membership on-link.
1454 * This is not strictly needed for MLDv2, which already jitters
1455 its report transmissions. However, the 'timer' argument is
1456 preserved in case MLDv1 is active on the interface.
1458 * The KAME linked-list based IPv6 membership implementation has
1459 been refactored to use a vector similar to that used by the IPv4
1461 Code which maintains a list of its own multicast memberships
1462 internally, e.g. carp, has been updated to reflect the new
1465 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1466 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1467 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1468 implementation constraint which needs to be addressed in HEAD.
1470 For application developers:
1472 * The changes are broadly similar to those made for the IPv4
1475 * The use of IPv4 and IPv6 multicast socket options on the same
1476 socket, using mapped addresses, HAS NOT been tested or supported.
1478 * There are a number of issues with the implementation of various
1479 IPv6 multicast APIs which need to be resolved in the API surface
1480 before the implementation is fully compatible with KAME userland
1481 use, and these are mostly to do with interface index treatment.
1483 * The literature available discusses the use of either the delta / ASM
1484 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1485 using setsourcefilter(3)/getsourcefilter(3). For more information
1486 please refer to RFC 3768, 'Socket Interface Extensions for
1487 Multicast Source Filters'.
1489 * Applications which use the published RFC 3678 APIs should be fine.
1491 For systems administrators:
1493 * The mtest(8) utility has been refactored to support IPv6, in
1494 addition to IPv4. Interface addresses are no longer accepted
1495 as arguments, their names must be used instead. The utility
1496 will map the interface name to its first IPv4 address as
1497 returned by getifaddrs(3).
1499 * The ifmcstat(8) utility has also been updated to print the MLDv2
1500 endpoint state and source filter lists via sysctl(3).
1502 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1503 loopback of IPv6 multicast datagrams by default; it defaults to 1
1504 to preserve the existing behaviour. Disabling multicast loopback is
1505 recommended for optimal system performance.
1507 * The IPv6 MROUTING code has been changed to examine this sysctl
1508 instead of attempting to perform a group lookup before looping
1509 back forwarded datagrams.
1511 Bump __FreeBSD_version to 800084.
1514 Implement low-level Bluetooth HCI API.
1515 Bump __FreeBSD_version to 800083.
1518 The layout of struct malloc_type, used by modules to register new
1519 memory allocation types, has changed. Most modules will need to
1520 be rebuilt or panics may be experienced.
1521 Bump __FreeBSD_version to 800081.
1524 Anticipate overflowing inp_flags - add inp_flags2.
1525 This changes most offsets in inpcb, so checking v4 connection
1526 state will require a world rebuild.
1527 Bump __FreeBSD_version to 800080.
1530 Add an llentry to struct route and struct route_in6. Modules
1531 embedding a struct route will need to be recompiled.
1532 Bump __FreeBSD_version to 800079.
1535 The size of rt_metrics_lite and by extension rtentry has changed.
1536 Networking administration apps will need to be recompiled.
1537 The route command now supports show as an alias for get, weighting
1538 of routes, sticky and nostick flags to alter the behavior of stateful
1540 Bump __FreeBSD_version to 800078.
1543 Do not use Giant for kbdmux(4) locking. This is wrong and
1544 apparently causing more problems than it solves. This will
1545 re-open the issue where interrupt handlers may race with
1546 kbdmux(4) in polling mode. Typical symptoms include (but
1547 not limited to) duplicated and/or missing characters when
1548 low level console functions (such as gets) are used while
1549 interrupts are enabled (for example geli password prompt,
1550 mountroot prompt etc.). Disabling kbdmux(4) may help.
1553 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1554 kernel modules referencing any of the above need to be recompiled.
1555 Bump __FreeBSD_version to 800075.
1558 GEOM_PART has become the default partition slicer for storage devices,
1559 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1560 introduces some changes:
1562 MSDOS/EBR: the devices created from MSDOS extended partition entries
1563 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1564 to devices with offset-based names. fstabs may need to be modified.
1566 BSD: the "geometry does not match label" warning is harmless in most
1567 cases but it points to problems in file system misalignment with
1568 disk geometry. The "c" partition is now implicit, covers the whole
1569 top-level drive and cannot be (mis)used by users.
1571 General: Kernel dumps are now not allowed to be written to devices
1572 whose partition types indicate they are meant to be used for file
1573 systems (or, in case of MSDOS partitions, as something else than
1576 Most of these changes date approximately from 200812.
1579 The uscanner(4) driver has been removed from the kernel. This follows
1580 Linux removing theirs in 2.6 and making libusb the default interface
1581 (supported by sane).
1584 The multicast forwarding code has been cleaned up. netstat(1)
1585 only relies on KVM now for printing bandwidth upcall meters.
1586 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1587 ip6_mroute_mod respectively. The config(5) options for statically
1588 compiling this code remain the same, i.e. 'options MROUTING'.
1591 Support for the IFF_NEEDSGIANT network interface flag has been
1592 removed, which means that non-MPSAFE network device drivers are no
1593 longer supported. In particular, if_ar, if_sr, and network device
1594 drivers from the old (legacy) USB stack can no longer be built or
1598 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1599 a bunch of new language catalog files have also been added.
1600 This means that some common libc messages are now localized and
1601 they depend on the LC_MESSAGES environmental variable.
1604 The k8temp(4) driver has been renamed to amdtemp(4) since
1605 support for Family 10 and Family 11 CPU families was added.
1608 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1609 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1611 For kernel developers, the most important changes are that the
1612 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1613 and this lock has been downgraded to a non-recursive mutex.
1615 Transport protocols (UDP, Raw IP) are now responsible for filtering
1616 inbound multicast traffic according to group membership and source
1617 filters. The imo_multicast_filter() KPI exists for this purpose.
1618 Transports which do not use multicast (SCTP, TCP) already reject
1619 multicast by default. Forwarding and receive performance may improve
1620 as a mutex acquisition is no longer needed in the ip_input()
1621 low-level input path. in_addmulti() and in_delmulti() are shimmed
1622 to new KPIs which exist to support SSM in-kernel.
1624 For application developers, it is recommended that loopback of
1625 multicast datagrams be disabled for best performance, as this
1626 will still cause the lock to be taken for each looped-back
1627 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1628 be tuned to 0 to disable loopback by default; it defaults to 1
1629 to preserve the existing behaviour.
1631 For systems administrators, to obtain best performance with
1632 multicast reception and multiple groups, it is always recommended
1633 that a card with a suitably precise hash filter is used. Hash
1634 collisions will still result in the lock being taken within the
1635 transport protocol input path to check group membership.
1637 If deploying FreeBSD in an environment with IGMP snooping switches,
1638 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1639 enabled; this forces 224.0.0.0/24 group membership to be announced
1642 The size of 'struct igmpstat' has changed; netstat needs to be
1643 recompiled to reflect this.
1644 Bump __FreeBSD_version to 800070.
1647 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1648 updated to use it. This requires a buildworld/installworld in order to
1649 update the library and dependencies (usbconfig, etc). Its advisable to
1650 rebuild all ports which uses libusb. More specific directions are given
1651 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1652 libusb are no longer required and can be removed.
1655 A workaround is committed to allow the creation of System V shared
1656 memory segment of size > 2 GB on the 64-bit architectures.
1657 Due to a limitation of the existing ABI, the shm_segsz member
1658 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1659 wrong for large segments. Note that limits must be explicitly
1660 raised to allow such segments to be created.
1663 The layout of struct ifnet has changed, requiring a rebuild of all
1664 network device driver modules.
1667 The /dev handling for the new USB stack has changed, a
1668 buildworld/installworld is required for libusb20.
1671 The new USB2 stack has now been permanently moved in and all kernel and
1672 module names reverted to their previous values (eg, usb, ehci, ohci,
1673 ums, ...). The old usb stack can be compiled in by prefixing the name
1674 with the letter 'o', the old usb modules have been removed.
1675 Updating entry 20090216 for xorg and 20090215 for libmap may still
1679 The rc.conf(5) option if_up_delay has been renamed to
1680 defaultroute_delay to better reflect its purpose. If you have
1681 customized this setting in /etc/rc.conf you need to update it to
1685 xorg 7.4 wants to configure its input devices via hald which does not
1686 yet work with USB2. If the keyboard/mouse does not work in xorg then
1688 Option "AllowEmptyInput" "off"
1689 to your ServerLayout section. This will cause X to use the configured
1690 kbd and mouse sections from your xorg.conf.
1693 The GENERIC kernels for all architectures now default to the new USB2
1694 stack. No kernel config options or code have been removed so if a
1695 problem arises please report it and optionally revert to the old USB
1696 stack. If you are loading USB kernel modules or have a custom kernel
1697 that includes GENERIC then ensure that usb names are also changed over,
1698 eg uftdi -> usb2_serial_ftdi.
1700 Older programs linked against the ports libusb 0.1 need to be
1701 redirected to the new stack's libusb20. /etc/libmap.conf can
1703 # Map old usb library to new one for usb2 stack
1704 libusb-0.1.so.8 libusb20.so.1
1707 All USB ethernet devices now attach as interfaces under the name ueN
1708 (eg. ue0). This is to provide a predictable name as vendors often
1709 change usb chipsets in a product without notice.
1712 The ichsmb(4) driver has been changed to require SMBus slave
1713 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1714 All of the other SMBus controller drivers require left-justified
1715 slave addresses, so this change makes all the drivers provide the
1719 INET6 statistics (struct ip6stat) was updated.
1720 netstat(1) needs to be recompiled.
1723 NTFS has been removed from GENERIC kernel on amd64 to match
1724 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1725 will load ntfs.ko module automatically when NTFS support is
1726 actually needed, unless ntfs.ko is not installed or security
1727 level prohibits loading kernel modules. If either is the case,
1728 "options NTFS" has to be added into kernel config.
1731 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1732 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1733 800061. User space tools that rely on the size of struct tcpcb in
1734 tcp_var.h (e.g. sockstat) need to be recompiled.
1737 ng_tty(4) module updated to match the new TTY subsystem.
1738 Due to API change, user-level applications must be updated.
1739 New API support added to mpd5 CVS and expected to be present
1740 in next mpd5.3 release.
1743 With __FreeBSD_version 800060 the makefs tool is part of
1744 the base system (it was a port).
1747 The afdata and ifnet locks have been changed from mutexes to
1748 rwlocks, network modules will need to be re-compiled.
1751 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1752 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1753 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1754 architecture and 40 bytes on 64-bit architecture. The userland
1755 applications "arp" and "ndp" have been updated accordingly.
1756 The output from "netstat -r" shows only routing entries and
1757 none of the L2 information.
1760 __FreeBSD_version 800057 marks the switchover from the
1761 binary ath hal to source code. Users must add the line:
1763 options AH_SUPPORT_AR5416
1765 to their kernel config files when specifying:
1769 The ath_hal module no longer exists; the code is now compiled
1770 together with the driver in the ath module. It is now
1771 possible to tailor chip support (i.e. reduce the set of chips
1772 and thereby the code size); consult ath_hal(4) for details.
1775 __FreeBSD_version 800054 adds memory barriers to
1776 <machine/atomic.h>, new interfaces to ifnet to facilitate
1777 multiple hardware transmit queues for cards that support
1778 them, and a lock-less ring-buffer implementation to
1779 enable drivers to more efficiently manage queueing of
1783 A new version of ZFS (version 13) has been merged to -HEAD.
1784 This version has zpool attribute "listsnapshots" off by
1785 default, which means "zfs list" does not show snapshots,
1786 and is the same as Solaris behavior.
1789 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1792 The uhci, ohci, ehci and slhci USB Host controller drivers have
1793 been put into separate modules. If you load the usb module
1794 separately through loader.conf you will need to load the
1795 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1796 controller add the following to loader.conf:
1802 The ABI used by the PMC toolset has changed. Please keep
1803 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1807 atapci kernel module now includes only generic PCI ATA
1808 driver. AHCI driver moved to ataahci kernel module.
1809 All vendor-specific code moved into separate kernel modules:
1810 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1811 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1812 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1813 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1816 The TTY subsystem of the kernel has been replaced by a new
1817 implementation, which provides better scalability and an
1818 improved driver model. Most common drivers have been migrated to
1819 the new TTY subsystem, while others have not. The following
1820 drivers have not yet been ported to the new TTY layer:
1823 cy, digi, rc, rp, sio
1829 ng_h4, ng_tty, ppp, sl, snp
1831 Adding these drivers to your kernel configuration file shall
1832 cause compilation to fail.
1835 ntpd has been upgraded to 4.2.4p5.
1838 OpenSSH has been upgraded to 5.1p1.
1840 For many years, FreeBSD's version of OpenSSH preferred DSA
1841 over RSA for host and user authentication keys. With this
1842 upgrade, we've switched to the vendor's default of RSA over
1843 DSA. This may cause upgraded clients to warn about unknown
1844 host keys even for previously known hosts. Users should
1845 follow the usual procedure for verifying host keys before
1846 accepting the RSA key.
1848 This can be circumvented by setting the "HostKeyAlgorithms"
1849 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1852 Please note that the sequence of keys offered for
1853 authentication has been changed as well. You may want to
1854 specify IdentityFile in a different order to revert this
1858 The sio(4) driver has been removed from the i386 and amd64
1859 kernel configuration files. This means uart(4) is now the
1860 default serial port driver on those platforms as well.
1862 To prevent collisions with the sio(4) driver, the uart(4) driver
1863 uses different names for its device nodes. This means the
1864 onboard serial port will now most likely be called "ttyu0"
1865 instead of "ttyd0". You may need to reconfigure applications to
1866 use the new device names.
1868 When using the serial port as a boot console, be sure to update
1869 /boot/device.hints and /etc/ttys before booting the new kernel.
1870 If you forget to do so, you can still manually specify the hints
1871 at the loader prompt:
1873 set hint.uart.0.at="isa"
1874 set hint.uart.0.port="0x3F8"
1875 set hint.uart.0.flags="0x10"
1876 set hint.uart.0.irq="4"
1880 The gpt(8) utility has been removed. Use gpart(8) to partition
1884 The version that Linuxulator emulates was changed from 2.4.2
1885 to 2.6.16. If you experience any problems with Linux binaries
1886 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1887 if it fixes the problem contact emulation mailing list.
1890 ISDN4BSD (I4B) was removed from the src tree. You may need to
1891 update a your kernel configuration and remove relevant entries.
1894 I have checked in code to support multiple routing tables.
1895 See the man pages setfib(1) and setfib(2).
1896 This is a hopefully backwards compatible version,
1897 but to make use of it you need to compile your kernel
1898 with options ROUTETABLES=2 (or more up to 16).
1901 The 802.11 wireless support was redone to enable multi-bss
1902 operation on devices that are capable. The underlying device
1903 is no longer used directly but instead wlanX devices are
1904 cloned with ifconfig. This requires changes to rc.conf files.
1905 For example, change:
1906 ifconfig_ath0="WPA DHCP"
1909 ifconfig_wlan0="WPA DHCP"
1910 see rc.conf(5) for more details. In addition, mergemaster of
1911 /etc/rc.d is highly recommended. Simultaneous update of userland
1912 and kernel wouldn't hurt either.
1914 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1915 modules were merged into the base wlan module. All references
1916 to these modules (e.g. in kernel config files) must be removed.
1919 psm(4) has gained write(2) support in native operation level.
1920 Arbitrary commands can be written to /dev/psm%d and status can
1921 be read back from it. Therefore, an application is responsible
1922 for status validation and error recovery. It is a no-op in
1923 other operation levels.
1926 Support for KSE threading has been removed from the kernel. To
1927 run legacy applications linked against KSE libmap.conf may
1928 be used. The following libmap.conf may be used to ensure
1929 compatibility with any prior release:
1931 libpthread.so.1 libthr.so.1
1932 libpthread.so.2 libthr.so.2
1933 libkse.so.3 libthr.so.3
1936 The layout of struct vmspace has changed. This affects libkvm
1937 and any executables that link against libkvm and use the
1938 kvm_getprocs() function. In particular, but not exclusively,
1939 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1940 The effects are minimal, but it's advisable to upgrade world
1944 The latest em driver no longer has support in it for the
1945 82575 adapter, this is now moved to the igb driver. The
1946 split was done to make new features that are incompatible
1947 with older hardware easier to do.
1950 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1951 likewise the kernel option is now GEOM_LINUX_LVM.
1954 The default NFS mount mode has changed from UDP to TCP for
1955 increased reliability. If you rely on (insecurely) NFS
1956 mounting across a firewall you may need to update your
1960 Belatedly note the addition of m_collapse for compacting
1964 The fts(3) structures have been changed to use adequate
1965 integer types for their members and so to be able to cope
1966 with huge file trees. The old fts(3) ABI is preserved
1967 through symbol versioning in libc, so third-party binaries
1968 using fts(3) should still work, although they will not take
1969 advantage of the extended types. At the same time, some
1970 third-party software might fail to build after this change
1971 due to unportable assumptions made in its source code about
1972 fts(3) structure members. Such software should be fixed
1973 by its vendor or, in the worst case, in the ports tree.
1974 FreeBSD_version 800015 marks this change for the unlikely
1975 case that a portable fix is impossible.
1978 To upgrade to -current after this date, you must be running
1979 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1980 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1983 The ADAPTIVE_GIANT kernel option has been retired because its
1984 functionality is the default now.
1987 The AT keyboard emulation of sunkbd(4) has been turned on
1988 by default. In order to make the special symbols of the Sun
1989 keyboards driven by sunkbd(4) work under X these now have
1990 to be configured the same way as Sun USB keyboards driven
1991 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1993 Option "XkbLayout" "us"
1994 Option "XkbRules" "xorg"
1995 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1998 It has been decided that it is desirable to provide ABI
1999 backwards compatibility to the FreeBSD 4/5/6 versions of the
2000 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2001 broken with the introduction of PCI domain support (see the
2002 20070930 entry). Unfortunately, this required the ABI of
2003 PCIOCGETCONF to be broken again in order to be able to
2004 provide backwards compatibility to the old version of that
2005 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2006 again. As for prominent ports this affects neither pciutils
2007 nor xorg-server this time, the hal port needs to be rebuilt
2011 The misnamed kthread_create() and friends have been renamed
2012 to kproc_create() etc. Many of the callers already
2013 used kproc_start()..
2014 I will return kthread_create() and friends in a while
2015 with implementations that actually create threads, not procs.
2016 Renaming corresponds with version 800002.
2025 Avoid using make -j when upgrading. While generally safe, there are
2026 sometimes problems using -j to upgrade. If your upgrade fails with
2027 -j, please try again without -j. From time to time in the past there
2028 have been problems using -j with buildworld and/or installworld. This
2029 is especially true when upgrading between "distant" versions (eg one
2030 that cross a major release boundary or several minor releases, or when
2031 several months have passed on the -current branch).
2033 Sometimes, obscure build problems are the result of environment
2034 poisoning. This can happen because the make utility reads its
2035 environment when searching for values for global variables. To run
2036 your build attempts in an "environmental clean room", prefix all make
2037 commands with 'env -i '. See the env(1) manual page for more details.
2039 When upgrading from one major version to another it is generally best
2040 to upgrade to the latest code in the currently installed branch first,
2041 then do an upgrade to the new branch. This is the best-tested upgrade
2042 path, and has the highest probability of being successful. Please try
2043 this approach before reporting problems with a major version upgrade.
2045 When upgrading a live system, having a root shell around before
2046 installing anything can help undo problems. Not having a root shell
2047 around can lead to problems if pam has changed too much from your
2048 starting point to allow continued authentication after the upgrade.
2052 When upgrading the boot ZFS pool to a new version, always follow
2055 1.) recompile and reinstall the ZFS boot loader and boot block
2056 (this is part of "make buildworld" and "make installworld")
2058 2.) update the ZFS boot block on your boot drive
2060 The following example updates the ZFS boot block on the first
2061 partition (freebsd-boot) of a GPT partitioned drive ad0:
2062 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2064 Non-boot pools do not need these updates.
2068 If you are updating from a prior version of FreeBSD (even one just
2069 a few days old), you should follow this procedure. It is the most
2070 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2072 make kernel-toolchain
2073 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2074 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2076 To test a kernel once
2077 ---------------------
2078 If you just want to boot a kernel once (because you are not sure
2079 if it works, or if you want to boot a known bad kernel to provide
2080 debugging information) run
2081 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2082 nextboot -k testkernel
2084 To just build a kernel when you know that it won't mess you up
2085 --------------------------------------------------------------
2086 This assumes you are already running a CURRENT system. Replace
2087 ${arch} with the architecture of your machine (e.g. "i386",
2088 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2090 cd src/sys/${arch}/conf
2091 config KERNEL_NAME_HERE
2092 cd ../compile/KERNEL_NAME_HERE
2097 If this fails, go to the "To build a kernel" section.
2099 To rebuild everything and install it on the current system.
2100 -----------------------------------------------------------
2101 # Note: sometimes if you are running current you gotta do more than
2102 # is listed here if you are upgrading from a really old current.
2104 <make sure you have good level 0 dumps>
2106 make kernel KERNCONF=YOUR_KERNEL_HERE
2108 <reboot in single user> [3]
2115 To cross-install current onto a separate partition
2116 --------------------------------------------------
2117 # In this approach we use a separate partition to hold
2118 # current's root, 'usr', and 'var' directories. A partition
2119 # holding "/", "/usr" and "/var" should be about 2GB in
2122 <make sure you have good level 0 dumps>
2125 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2126 <maybe newfs current's root partition>
2127 <mount current's root partition on directory ${CURRENT_ROOT}>
2128 make installworld DESTDIR=${CURRENT_ROOT}
2129 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2130 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2131 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2132 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2133 <reboot into current>
2134 <do a "native" rebuild/install as described in the previous section>
2135 <maybe install compatibility libraries from ports/misc/compat*>
2139 To upgrade in-place from stable to current
2140 ----------------------------------------------
2141 <make sure you have good level 0 dumps>
2143 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2145 <reboot in single user> [3]
2152 Make sure that you've read the UPDATING file to understand the
2153 tweaks to various things you need. At this point in the life
2154 cycle of current, things change often and you are on your own
2155 to cope. The defaults can also change, so please read ALL of
2156 the UPDATING entries.
2158 Also, if you are tracking -current, you must be subscribed to
2159 freebsd-current@freebsd.org. Make sure that before you update
2160 your sources that you have read and understood all the recent
2161 messages there. If in doubt, please track -stable which has
2162 much fewer pitfalls.
2164 [1] If you have third party modules, such as vmware, you
2165 should disable them at this point so they don't crash your
2168 [3] From the bootblocks, boot -s, and then do
2173 adjkerntz -i # if CMOS is wall time
2174 Also, when doing a major release upgrade, it is required that
2175 you boot into single user mode to do the installworld.
2177 [4] Note: This step is non-optional. Failure to do this step
2178 can result in a significant reduction in the functionality of the
2179 system. Attempting to do it by hand is not recommended and those
2180 that pursue this avenue should read this file carefully, as well
2181 as the archives of freebsd-current and freebsd-hackers mailing lists
2182 for potential gotchas. The -U option is also useful to consider.
2183 See mergemaster(8) for more information.
2185 [5] Usually this step is a noop. However, from time to time
2186 you may need to do this if you get unknown user in the following
2187 step. It never hurts to do it all the time. You may need to
2188 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2189 install) after the buildworld before this step if you last updated
2190 from current before 20130425 or from -stable before 20130430.
2192 [6] This only deletes old files and directories. Old libraries
2193 can be deleted by "make delete-old-libs", but you have to make
2194 sure that no program is using those libraries anymore.
2196 [8] In order to have a kernel that can run the 4.x binaries needed to
2197 do an installworld, you must include the COMPAT_FREEBSD4 option in
2198 your kernel. Failure to do so may leave you with a system that is
2199 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2200 required to run the 5.x binaries on more recent kernels. And so on
2201 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2203 Make sure that you merge any new devices from GENERIC since the
2204 last time you updated your kernel config file.
2206 [9] When checking out sources, you must include the -P flag to have
2207 cvs prune empty directories.
2209 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2210 "?=" instead of the "=" assignment operator, so that buildworld can
2211 override the CPUTYPE if it needs to.
2213 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2214 not on the command line, or in /etc/make.conf. buildworld will
2215 warn if it is improperly defined.
2218 This file contains a list, in reverse chronological order, of major
2219 breakages in tracking -current. It is not guaranteed to be a complete
2220 list of such breakages, and only contains entries since October 10, 2007.
2221 If you need to see UPDATING entries from before that date, you will need
2222 to fetch an UPDATING file from an older FreeBSD release.
2224 Copyright information:
2226 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2228 Redistribution, publication, translation and use, with or without
2229 modification, in full or in part, in any form or format of this
2230 document are permitted without further permission from the author.
2232 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2233 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2234 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2235 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2236 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2237 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2238 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2239 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2240 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2241 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2242 POSSIBILITY OF SUCH DAMAGE.
2244 Contact Warner Losh if you have any questions about your use of