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 20150612: p12 FreeBSD-SA-15:10.openssl
20 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
22 20150609: p11 FreeBSD-EN-15:06.file
25 Updated base system file(1) to 5.22 to address multiple denial
26 of service issues. [EN-15:06]
28 Improved reliability of ZFS when TRIM/UNMAP and/or L2ARC is used.
31 20150513: p10 FreeBSD-EN-15:04.freebsd-update
34 Fix bug with freebsd-update(8) that does not ensure the previous
35 upgrade was completed. [EN-15:04]
37 Fix deadlock on reboot with UFS tuned with SU+J. [EN-15:05]
39 20150407: p9 FreeBSD-SA-15:04.igmp [revised]
41 FreeBSD-SA-15:08.bsdinstall
44 Improved patch for SA-15:04.igmp.
46 Fix multiple vulnerabilities of ntp. [SA-15:07]
48 Fix bsdinstall(8) insecure default GELI keyfile permissions. [SA-15:08]
50 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
53 Fix patch for SA-15:06.openssl.
55 20150319: p7 FreeBSD-SA-15:06.openssl
56 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
58 20150225: p6 FreeBSD-SA-15:04.igmp
60 FreeBSD-EN-15:02.openssl
61 FreeBSD-EN-15:03.freebsd-update
63 Fix integer overflow in IGMP protocol. [SA-15:04]
65 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
67 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
69 Fix freebsd-update libraries update ordering issue. [EN-15:03]
71 20150127: p5 FreeBSD-SA-15:02.kmem
74 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
75 vulnerability. [SA-15:02]
77 Fix SCTP stream reset vulnerability. [SA-15:03]
79 20150114: p4 FreeBSD-SA-15:01.openssl
80 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
82 20141223: p3 FreeBSD-SA-14:31.ntp
83 FreeBSD-EN-14:13.freebsd-update
85 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
86 Fix directory deletion issue in freebsd-update. [EN-14:13]
88 20141217: p2 FreeBSD-SA-14:30.unbound
89 Fix unbound remote denial of service vulnerability.
91 20141210: p1 FreeBSD-SA-14:27.stdio
94 Fix buffer overflow in stdio. [SA-14:27]
96 Fix multiple vulnerabilities in file(1) and libmagic(3).
100 The ofwfb driver, used to provide a graphics console on PowerPC when
101 using vt(4), no longer allows mmap() of all of physical memory. This
102 will prevent Xorg on PowerPC with some ATI graphics cards from
103 initializing properly unless x11-servers/xorg-server is updated to
107 The libatf-c and libatf-c++ major versions were downgraded to 0 and
108 1 respectively to match the upstream numbers. They were out of
109 sync because, when they were originally added to FreeBSD, the
110 upstream versions were not respected. These libraries are private
111 and not yet built by default, so renumbering them should be a
112 non-issue. However, unclean source trees will yield broken test
113 programs once the operator executes "make delete-old-libs" after a
116 Additionally, the atf-sh binary was made private by moving it into
117 /usr/libexec/. Already-built shell test programs will keep the
118 path to the old binary so they will break after "make delete-old"
121 If you are using WITH_TESTS=yes (not the default), wipe the object
122 tree and rebuild from scratch to prevent spurious test failures.
123 This is only needed once: the misnumbered libraries and misplaced
124 binaries have been added to OptionalObsoleteFiles.inc so they will
125 be removed during a clean upgrade.
128 The ixgbe tunables now match their sysctl counterparts, for example:
129 hw.ixgbe.enable_aim => hw.ix.enable_aim
130 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
133 The NFSv4.1 server committed by r269398 changes the internal
134 function call interfaces used between the NFS and krpc modules.
135 As such, __FreeBSD_version was bumped.
138 The default unbound configuration has been modified to address
139 issues with reverse lookups on networks that use private
140 address ranges. If you use the local_unbound service, run
141 "service local_unbound setup" as root to regenerate your
142 configuration, then "service local_unbound reload" to load the
146 It is no longer necessary to include the dwarf version in your DEBUG
147 options in your kernel config file. The bug that required it to be
148 placed in the config file has bene fixed. DEBUG should now just
149 contain -g. The build system will automatically update things
150 to do the right thing.
153 Several ABI breaking changes were merged to CTL and new iSCSI code.
154 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
155 iscsictl need to be rebuilt to work with a new kernel.
158 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
159 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
160 which differs from the behaviour controlled by this knob.)
163 On i386 and amd64 systems, the onifconsole flag is now set by default
164 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
165 as a login TTY if it is set in the bootloader as an active kernel
166 console. No changes in behavior should result otherwise. To revert to
167 the previous behavior, set ttyu0 to "off" in /etc/ttys.
170 Clang and llvm have been upgraded to 3.4.1 release.
173 Clang and llvm have been upgraded to 3.4 release.
176 If a Makefile in a tests/ directory was auto-generating a Kyuafile
177 instead of providing an explicit one, this would prevent such
178 Makefile from providing its own Kyuafile in the future during
179 NO_CLEAN builds. This has been fixed in the Makefiles but manual
180 intervention is needed to clean an objdir if you use NO_CLEAN:
181 # find /usr/obj -name Kyuafile | xargs rm -f
184 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
185 capability mode support. Please note that enabling the feature in
186 kernel is still highly recommended.
189 OpenSSH is now built with sandbox support, and will use sandbox as
190 the default privilege separation method. This requires Capsicum
191 capability mode support in kernel.
194 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
195 been deprecated and will not be part of FreeBSD 11.0 and later
196 releases. If you use this driver, please consider switching to
197 the nfe(4) driver instead.
203 The behavior of gss_pseudo_random() for the krb5 mechanism
204 has changed, for applications requesting a longer random string
205 than produced by the underlying enctype's pseudo-random() function.
206 In particular, the random string produced from a session key of
207 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
208 be different at the 17th octet and later, after this change.
209 The counter used in the PRF+ construction is now encoded as a
210 big-endian integer in accordance with RFC 4402.
211 __FreeBSD_version is bumped to 1000701.
214 The WITHOUT_ATF build knob has been removed and its functionality
215 has been subsumed into the more generic WITHOUT_TESTS. If you were
216 using the former to disable the build of the ATF libraries, you
217 should change your settings to use the latter.
220 The default version of mtree is nmtree which is obtained from
221 NetBSD. The output is generally the same, but may vary
222 slightly. If you found you need identical output adding
223 "-F freebsd9" to the command line should do the trick. For the
224 time being, the old mtree is available as fmtree.
227 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
228 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
229 1.1.4_8 and verify bsdyml not linked in, before running "make
231 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
233 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
236 The rc.d/jail script has been updated to support jail(8)
237 configuration file. The "jail_<jname>_*" rc.conf(5) variables
238 for per-jail configuration are automatically converted to
239 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
240 This is transparently backward compatible. See below about some
241 incompatibilities and rc.conf(5) manual page for more details.
243 These variables are now deprecated in favor of jail(8) configuration
244 file. One can use "rc.d/jail config <jname>" command to generate
245 a jail(8) configuration file in /var/run/jail.<jname>.conf without
246 running the jail(8) utility. The default pathname of the
247 configuration file is /etc/jail.conf and can be specified by
248 using $jail_conf or $jail_<jname>_conf variables.
250 Please note that jail_devfs_ruleset accepts an integer at
251 this moment. Please consider to rewrite the ruleset name
255 BIND has been removed from the base system. If all you need
256 is a local resolver, simply enable and start the local_unbound
257 service instead. Otherwise, several versions of BIND are
258 available in the ports tree. The dns/bind99 port is one example.
260 With this change, nslookup(1) and dig(1) are no longer in the base
261 system. Users should instead use host(1) and drill(1) which are
262 in the base system. Alternatively, nslookup and dig can
263 be obtained by installing the dns/bind-tools port.
266 With the addition of unbound(8), a new unbound user is now
267 required during installworld. "mergemaster -p" can be used to
268 add the user prior to installworld, as documented in the handbook.
271 OpenSSH is now built with DNSSEC support, and will by default
272 silently trust signed SSHFP records. This can be controlled with
273 the VerifyHostKeyDNS client configuration setting. DNSSEC support
274 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
277 The GNU Compiler Collection and C++ standard library (libstdc++)
278 are no longer built by default on platforms where clang is the system
279 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
283 The PROCDESC kernel option is now part of the GENERIC kernel
284 configuration and is required for the rwhod(8) to work.
285 If you are using custom kernel configuration, you should include
289 The API and ABI related to the Capsicum framework was modified
290 in backward incompatible way. The userland libraries and programs
291 have to be recompiled to work with the new kernel. This includes the
292 following libraries and programs, but the whole buildworld is
293 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
294 kdump, procstat, rwho, rwhod, uniq.
297 AES-NI intrinsic support has been added to gcc. The AES-NI module
298 has been updated to use this support. A new gcc is required to build
299 the aesni module on both i386 and amd64.
302 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
303 Thus "device padlock_rng" and "device rdrand_rng" should be
304 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
307 WITH_ICONV has been split into two feature sets. WITH_ICONV now
308 enables just the iconv* functionality and is now on by default.
309 WITH_LIBICONV_COMPAT enables the libiconv api and link time
310 compatability. Set WITHOUT_ICONV to build the old way.
311 If you have been using WITH_ICONV before, you will very likely
312 need to turn on WITH_LIBICONV_COMPAT.
315 INVARIANTS option now enables DEBUG for code with OpenSolaris and
316 Illumos origin, including ZFS. If you have INVARIANTS in your
317 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
319 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
320 locks if WITNESS option was set. Because that generated a lot of
321 witness(9) reports and all of them were believed to be false
322 positives, this is no longer done. New option OPENSOLARIS_WITNESS
323 can be used to achieve the previous behavior.
326 Timer values in IPv6 data structures now use time_uptime instead
327 of time_second. Although this is not a user-visible functional
328 change, userland utilities which directly use them---ndp(8),
329 rtadvd(8), and rtsold(8) in the base system---need to be updated
333 find -delete can now delete the pathnames given as arguments,
334 instead of only files found below them or if the pathname did
335 not contain any slashes. Formerly, the following error message
338 find: -delete: <path>: relative path potentially not safe
340 Deleting the pathnames given as arguments can be prevented
341 without error messages using -mindepth 1 or by changing
342 directory and passing "." as argument to find. This works in the
343 old as well as the new version of find.
346 Behavior of devfs rules path matching has been changed.
347 Pattern is now always matched against fully qualified devfs
348 path and slash characters must be explicitly matched by
349 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
350 subdirectories must be reviewed.
353 The default ARM ABI has changed to the ARM EABI. The old ABI is
354 incompatible with the ARM EABI and all programs and modules will
355 need to be rebuilt to work with a new kernel.
357 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
359 NOTE: Support for the old ABI will be removed in the future and
360 users are advised to upgrade.
363 pkg_install has been disconnected from the build if you really need it
364 you should add WITH_PKGTOOLS in your src.conf(5).
367 Most of network statistics structures were changed to be able
368 keep 64-bits counters. Thus all tools, that work with networking
369 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
372 Fix targets that run multiple make's to use && rather than ;
373 so that subsequent steps depend on success of previous.
375 NOTE: if building 'universe' with -j* on stable/8 or stable/9
376 it would be better to start the build using bmake, to avoid
377 overloading the machine.
380 Fix a bug that allowed a tracing process (e.g. gdb) to write
381 to a memory-mapped file in the traced process's address space
382 even if neither the traced process nor the tracing process had
383 write access to that file.
386 CVS has been removed from the base system. An exact copy
387 of the code is available from the devel/cvs port.
390 Some people report the following error after the switch to bmake:
392 make: illegal option -- J
393 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
395 *** [buildworld] Error code 2
397 this likely due to an old instance of make in
398 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
399 which src/Makefile will use that blindly, if it exists, so if
400 you see the above error:
402 rm -rf `make -V MAKEPATH`
407 Use bmake by default.
408 Whereas before one could choose to build with bmake via
409 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
410 make. The goal is to remove these knobs for 10-RELEASE.
412 It is worth noting that bmake (like gmake) treats the command
413 line as the unit of failure, rather than statements within the
414 command line. Thus '(cd some/where && dosomething)' is safer
415 than 'cd some/where; dosomething'. The '()' allows consistent
416 behavior in parallel build.
419 Fix a bug that allows NFS clients to issue READDIR on files.
422 The WITHOUT_IDEA option has been removed because
423 the IDEA patent expired.
426 The sysctl which controls TRIM support under ZFS has been renamed
427 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
431 The mergemaster command now uses the default MAKEOBJDIRPREFIX
432 rather than creating it's own in the temporary directory in
433 order allow access to bootstrapped versions of tools such as
434 install and mtree. When upgrading from version of FreeBSD where
435 the install command does not support -l, you will need to
436 install a new mergemaster command if mergemaster -p is required.
437 This can be accomplished with the command (cd src/usr.sbin/mergemaster
441 Legacy ATA stack, disabled and replaced by new CAM-based one since
442 FreeBSD 9.0, completely removed from the sources. Kernel modules
443 atadisk and atapi*, user-level tools atacontrol and burncd are
444 removed. Kernel option `options ATA_CAM` is now permanently enabled
448 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
449 and socketpair(2). Software, in particular Kerberos, may
450 automatically detect and use these during building. The resulting
451 binaries will not work on older kernels.
454 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
455 information, see the respective 20130304 entry).
458 Recent commits to callout(9) changed the size of struct callout,
459 so the KBI is probably heavily disturbed. Also, some functions
460 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
461 by macros. Every kernel module using it won't load, so rebuild
464 The ctl device has been re-enabled in GENERIC for i386 and amd64,
465 but does not initialize by default (because of the new CTL_DISABLE
466 option) to save memory. To re-enable it, remove the CTL_DISABLE
467 option from the kernel config file or set kern.cam.ctl.disable=0
468 in /boot/loader.conf.
471 The ctl device has been disabled in GENERIC for i386 and amd64.
472 This was done due to the extra memory being allocated at system
473 initialisation time by the ctl driver which was only used if
474 a CAM target device was created. This makes a FreeBSD system
475 unusable on 128MB or less of RAM.
478 A new compression method (lz4) has been merged to -HEAD. Please
479 refer to zpool-features(7) for more information.
481 Please refer to the "ZFS notes" section of this file for information
482 on upgrading boot ZFS pools.
485 A BSD-licensed patch(1) variant has been added and is installed
486 as bsdpatch, being the GNU version the default patch.
487 To inverse the logic and use the BSD-licensed one as default,
488 while having the GNU version installed as gnupatch, rebuild
489 and install world with the WITH_BSD_PATCH knob set.
492 Due to the use of the new -l option to install(1) during build
493 and install, you must take care not to directly set the INSTALL
494 make variable in your /etc/make.conf, /etc/src.conf, or on the
495 command line. If you wish to use the -C flag for all installs
496 you may be able to add INSTALL+=-C to /etc/make.conf or
500 The install(1) option -M has changed meaning and now takes an
501 argument that is a file or path to append logs to. In the
502 unlikely event that -M was the last option on the command line
503 and the command line contained at least two files and a target
504 directory the first file will have logs appended to it. The -M
505 option served little practical purpose in the last decade so its
506 use is expected to be extremely rare.
509 After switching to Clang as the default compiler some users of ZFS
510 on i386 systems started to experience stack overflow kernel panics.
511 Please consider using 'options KSTACK_PAGES=4' in such configurations.
514 GEOM_LABEL now mangles label names read from file system metadata.
515 Mangling affect labels containing spaces, non-printable characters,
516 '%' or '"'. Device names in /etc/fstab and other places may need to
520 By default, only the 10 most recent kernel dumps will be saved. To
521 restore the previous behaviour (no limit on the number of kernel dumps
522 stored in the dump directory) add the following line to /etc/rc.conf:
527 With the addition of auditdistd(8), a new auditdistd user is now
528 required during installworld. "mergemaster -p" can be used to
529 add the user prior to installworld, as documented in the handbook.
532 The sin6_scope_id member variable in struct sockaddr_in6 is now
533 filled by the kernel before passing the structure to the userland via
534 sysctl or routing socket. This means the KAME-specific embedded scope
535 id in sin6_addr.s6_addr[2] is always cleared in userland application.
536 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
537 __FreeBSD_version is bumped to 1000025.
540 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
541 This means that the world and kernel will be compiled with clang
542 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
543 and /usr/bin/cpp. To disable this behavior and revert to building
544 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
545 of current may need to bootstrap WITHOUT_CLANG first if the clang
546 build fails (its compatibility window doesn't extend to the 9 stable
550 The IPFIREWALL_FORWARD kernel option has been removed. Its
551 functionality now turned on by default.
554 The ZERO_COPY_SOCKET kernel option has been removed and
555 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
556 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
557 mechanism which is not safe and may result in kernel crashes.
558 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
559 driver supports disposeable external page sized mbuf storage.
560 Proper replacements for both zero-copy mechanisms are under
561 consideration and will eventually lead to complete removal
562 of the two kernel options.
565 The IPv4 network stack has been converted to network byte
566 order. The following modules need to be recompiled together
567 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
568 pf(4), ipfw(4), ng_ipfw(4), stf(4).
571 Support for non-MPSAFE filesystems was removed from VFS. The
572 VFS_VERSION was bumped, all filesystem modules shall be
576 All the non-MPSAFE filesystems have been disconnected from
577 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
578 portalfs, smbfs, xfs.
581 The interface cloning API and ABI has changed. The following
582 modules need to be recompiled together with kernel:
583 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
584 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
585 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
588 The sdhci driver was split in two parts: sdhci (generic SD Host
589 Controller logic) and sdhci_pci (actual hardware driver).
590 No kernel config modifications are required, but if you
591 load sdhc as a module you must switch to sdhci_pci instead.
594 Import the FUSE kernel and userland support into base system.
597 The GNU sort(1) program has been removed since the BSD-licensed
598 sort(1) has been the default for quite some time and no serious
599 problems have been reported. The corresponding WITH_GNU_SORT
603 The pfil(9) API/ABI for AF_INET family has been changed. Packet
604 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
608 The net80211(4) ABI has been changed to allow for improved driver
609 PS-POLL and power-save support. All wireless drivers need to be
610 recompiled to work with the new kernel.
613 The random(4) support for the VIA hardware random number
614 generator (`PADLOCK') is no longer enabled unconditionally.
615 Add the padlock_rng device in the custom kernel config if
616 needed. The GENERIC kernels on i386 and amd64 do include the
617 device, so the change only affects the custom kernel
621 The pf(4) packet filter ABI has been changed. pfctl(8) and
622 snmp_pf module need to be recompiled to work with new kernel.
625 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
626 to -HEAD. Pools that have empty_bpobj in active state can not be
627 imported read-write with ZFS implementations that do not support
628 this feature. For more information read the zpool-features(5)
632 The sparc64 ZFS loader has been changed to no longer try to auto-
633 detect ZFS providers based on diskN aliases but now requires these
634 to be explicitly listed in the OFW boot-device environment variable.
637 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
638 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
639 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
642 The following sysctls and tunables have been renamed for consistency
643 with other variables:
644 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
645 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
648 The sort utility has been replaced with BSD sort. For now, GNU sort
649 is also available as "gnusort" or the default can be set back to
650 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
651 installed as "bsdsort".
654 A new version of ZFS (pool version 5000) has been merged to -HEAD.
655 Starting with this version the old system of ZFS pool versioning
656 is superseded by "feature flags". This concept enables forward
657 compatibility against certain future changes in functionality of ZFS
658 pools. The first read-only compatible "feature flag" for ZFS pools
659 is named "com.delphix:async_destroy". For more information
660 read the new zpool-features(5) manual page.
661 Please refer to the "ZFS notes" section of this file for information
662 on upgrading boot ZFS pools.
665 The malloc(3) implementation embedded in libc now uses sources imported
666 as contrib/jemalloc. The most disruptive API change is to
667 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
668 delete it prior to installworld, and optionally re-create it using the
669 new format after rebooting. See malloc.conf(5) for details
670 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
674 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
675 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
676 now spelled mips. This is to aid compatibility with third-party
677 software that expects this naming scheme in uname(3). Little-endian
678 settings are unchanged. If you are updating a big-endian mips64 machine
679 from before this change, you may need to set MACHINE_ARCH=mips64 in
680 your environment before the new build system will recognize your machine.
683 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
687 Now unix domain sockets behave "as expected" on nullfs(5). Previously
688 nullfs(5) did not pass through all behaviours to the underlying layer,
689 as a result if we bound to a socket on the lower layer we could connect
690 only to the lower path; if we bound to the upper layer we could connect
691 only to the upper path. The new behavior is one can connect to both the
692 lower and the upper paths regardless what layer path one binds to.
695 The getifaddrs upgrade path broken with 20111215 has been restored.
696 If you have upgraded in between 20111215 and 20120209 you need to
697 recompile libc again with your kernel. You still need to recompile
698 world to be able to configure CARP but this restriction already
702 The set_rcvar() function has been removed from /etc/rc.subr. All
703 base and ports rc.d scripts have been updated, so if you have a
704 port installed with a script in /usr/local/etc/rc.d you can either
705 hand-edit the rcvar= line, or reinstall the port.
707 An easy way to handle the mass-update of /etc/rc.d:
708 rm /etc/rc.d/* && mergemaster -i
711 panic(9) now stops other CPUs in the SMP systems, disables interrupts
712 on the current CPU and prevents other threads from running.
713 This behavior can be reverted using the kern.stop_scheduler_on_panic
715 The new behavior can be incompatible with kern.sync_on_panic.
718 The carp(4) facility has been changed significantly. Configuration
719 of the CARP protocol via ifconfig(8) has changed, as well as format
720 of CARP events submitted to devd(8) has changed. See manual pages
721 for more information. The arpbalance feature of carp(4) is currently
722 not supported anymore.
724 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
725 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
726 need to be recompiled.
729 The acpi_wmi(4) status device /dev/wmistat has been renamed to
733 The option VFS_ALLOW_NONMPSAFE option has been added in order to
734 explicitely support non-MPSAFE filesystems.
735 It is on by default for all supported platform at this present
739 The broken amd(4) driver has been replaced with esp(4) in the amd64,
740 i386 and pc98 GENERIC kernel configuration files.
743 sysinstall has been removed
746 The stable/9 branch created in subversion. This corresponds to the
747 RELENG_9 branch in CVS.
750 This commit modifies vfs_register() so that it uses a hash
751 calculation to set vfc_typenum, which is enabled by default.
752 The first time a system is booted after this change, the
753 vfc_typenum values will change for all file systems. The
754 main effect of this is a change to the NFS server file handles
755 for file systems that use vfc_typenum in their fsid, such as ZFS.
756 It will, however, prevent vfc_typenum from changing when file
757 systems are loaded in a different order for subsequent reboots.
758 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
759 until you are ready to remount all NFS clients after a reboot.
762 Bump the shared library version numbers for libraries that
763 do not use symbol versioning, have changed the ABI compared
764 to stable/8 and which shared library version was not bumped.
765 Done as part of 9.0-RELEASE cycle.
768 During the merge of Capsicum features, the fget(9) KPI was modified.
769 This may require the rebuilding of out-of-tree device drivers --
770 issues have been reported specifically with the nVidia device driver.
771 __FreeBSD_version is bumped to 900041.
773 Also, there is a period between 20110811 and 20110814 where the
774 special devices /dev/{stdin,stdout,stderr} did not work correctly.
775 Building world from a kernel during that window may not work.
778 The packet filter (pf) code has been updated to OpenBSD 4.5.
779 You need to update userland tools to be in sync with kernel.
780 This update breaks backward compatibility with earlier pfsync(4)
781 versions. Care must be taken when updating redundant firewall setups.
784 The following sysctls and tunables are retired on x86 platforms:
786 machdep.hlt_logical_cpus
787 The following sysctl is retired:
788 machdep.hyperthreading_allowed
789 The sysctls were supposed to provide a way to dynamically offline and
790 online selected CPUs on x86 platforms, but the implementation has not
791 been reliable especially with SCHED_ULE scheduler.
792 machdep.hyperthreading_allowed tunable is still available to ignore
793 hyperthreading CPUs at OS level.
794 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
795 where X is an APIC ID of a CPU. Be advised, though, that disabling
796 CPUs in non-uniform fashion will result in non-uniform topology and
797 may lead to sub-optimal system performance with SCHED_ULE, which is
801 cpumask_t type is retired and cpuset_t is used in order to describe
805 Changes to ifconfig(8) for dynamic address family detection mandate
806 that you are running a kernel of 20110525 or later. Make sure to
807 follow the update procedure to boot a new kernel before installing
811 Support for sun4v architecture is officially dropped
814 Several KPI breaking changes have been committed to the mii(4) layer,
815 the PHY drivers and consequently some Ethernet drivers using mii(4).
816 This means that miibus.ko and the modules of the affected Ethernet
817 drivers need to be recompiled.
819 Note to kernel developers: Given that the OUI bit reversion problem
820 was fixed as part of these changes all mii(4) commits related to OUIs,
821 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
822 handling, no longer can be merged verbatim to stable/8 and previous
826 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
827 into their kernel configurations along with 'device pci'.
830 The default NFS client is now the new NFS client, so fstype "newnfs"
831 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
832 Although mounts via fstype "nfs" will usually work without userland
833 changes, it is recommended that the mount(8) and mount_nfs(8)
834 commands be rebuilt from sources and that a link to mount_nfs called
835 mount_oldnfs be created. The new client is compiled into the
836 kernel with "options NFSCL" and this is needed for diskless root
837 file systems. The GENERIC kernel configs have been changed to use
838 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
839 To use the regular/old client, you can "mount -t oldnfs ...". For
840 a diskless root file system, you must also include a line like:
842 vfs.root.mountfrom="oldnfs:"
844 in the boot/loader.conf on the root fs on the NFS server to make
845 a diskless root fs use the old client.
848 The GENERIC kernels for all architectures now default to the new
849 CAM-based ATA stack. It means that all legacy ATA drivers were
850 removed and replaced by respective CAM drivers. If you are using
851 ATA device names in /etc/fstab or other places, make sure to update
852 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
853 where 'Y's are the sequential numbers starting from zero for each type
854 in order of detection, unless configured otherwise with tunables,
855 see cam(4)). There will be symbolic links created in /dev/ to map
856 old adX devices to the respective adaY. They should provide basic
857 compatibility for file systems mounting in most cases, but they do
858 not support old user-level APIs and do not have respective providers
859 in GEOM. Consider using updated management tools with new device names.
861 It is possible to load devices ahci, ata, siis and mvs as modules,
862 but option ATA_CAM should remain in kernel configuration to make ata
863 module work as CAM driver supporting legacy ATA controllers. Device ata
864 still can be used in modular fashion (atacore + ...). Modules atadisk
865 and atapi* are not used and won't affect operation in ATA_CAM mode.
866 Note that to use CAM-based ATA kernel should include CAM devices
867 scbus, pass, da (or explicitly ada), cd and optionally others. All of
868 them are parts of the cam module.
870 ataraid(4) functionality is now supported by the RAID GEOM class.
871 To use it you can load geom_raid kernel module and use graid(8) tool
872 for management. Instead of /dev/arX device names, use /dev/raid/rX.
874 No kernel config options or code have been removed, so if a problem
875 arises, please report it and optionally revert to the old ATA stack.
876 In order to do it you can remove from the kernel config:
881 , and instead add back:
882 device atadisk # ATA disk drives
883 device ataraid # ATA RAID drives
884 device atapicd # ATAPI CDROM drives
885 device atapifd # ATAPI floppy drives
886 device atapist # ATAPI tape drives
889 The default NFS server has been changed to the new server, which
890 was referred to as the experimental server. If you need to switch
891 back to the old NFS server, you must now put the "-o" option on
892 both the mountd and nfsd commands. This can be done using the
893 mountd_flags and nfs_server_flags rc.conf variables until an
894 update to the rc scripts is committed, which is coming soon.
897 The GNU Objective-C runtime library (libobjc), and other Objective-C
898 related components have been removed from the base system. If you
899 require an Objective-C library, please use one of the available ports.
902 ath(4) has been split into bus- and device- modules. if_ath contains
903 the HAL, the TX rate control and the network device code. if_ath_pci
904 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
905 contains the AHB glue. Users need to load both if_ath_pci and if_ath
906 in order to use ath on everything else.
908 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
909 need to load if_ath and if_ath_pci for ath(4) operation.
912 As part of the replacement of sysinstall, the process of building
913 release media has changed significantly. For details, please re-read
914 release(7), which has been updated to reflect the new build process.
917 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
918 is the last available version under GPLv2. It brings a number of new
919 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
920 4.1 and SSE 4.2), better support for powerpc64, a number of new
921 directives, and lots of other small improvements. See the ChangeLog
922 file in contrib/binutils for the full details.
925 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
926 compliant, and will now use half of hash for authentication.
927 This will break interoperability with all stacks (including all
928 actual FreeBSD versions) who implement
929 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
931 The only workaround with such peers is to use another HMAC
932 algorithm for IPsec ("phase 2") authentication.
935 Remove the uio_yield prototype and symbol. This function has
936 been misnamed since it was introduced and should not be
937 globally exposed with this name. The equivalent functionality
938 is now available using kern_yield(curthread->td_user_pri).
939 The function remains undocumented.
942 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
943 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
944 for scalar sysctls is defined but disabled. Code that needs
945 UQUAD to pass the type checking that must compile on older
946 systems where the define is not present can check against
947 __FreeBSD_version >= 900030.
949 The system dialog(1) has been replaced with a new version previously
950 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
951 with the previous version, but the libdialog associated with it has
952 a largely incompatible API. As such, the original version of libdialog
953 will be kept temporarily as libodialog, until its base system consumers
954 are replaced or updated. Bump __FreeBSD_version to 900030.
957 If you are trying to run make universe on a -stable system, and you get
958 the following warning:
959 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
960 unknown. config(8) likely too old."
961 or something similar to it, then you must upgrade your -stable system
962 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
963 stable/8) or build the config from the latest stable/8 branch and
964 install it on your system.
966 Prior to this date, building a current universe on 8-stable system from
967 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
968 error in the first kernel build phase. A new config on those old
969 systems will fix that problem for older versions of -current.
972 The TCP stack has been modified to allow Khelp modules to interact with
973 it via helper hook points and store per-connection data in the TCP
974 control block. Bump __FreeBSD_version to 900029. User space tools that
975 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
979 Generic IEEE 802.3 annex 31B full duplex flow control support has been
980 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
981 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
982 to take advantage of it instead of using custom implementations. This
983 means that these drivers now no longer unconditionally advertise
984 support for flow control but only do so if flow control is a selected
985 media option. This was implemented in the generic support that way in
986 order to allow flow control to be switched on and off via ifconfig(8)
987 with the PHY specific default to typically off in order to protect
988 from unwanted effects. Consequently, if you used flow control with
989 one of the above mentioned drivers you now need to explicitly enable
991 ifconfig bge0 media auto mediaopt flowcontrol
993 Along with the above mentioned changes generic support for setting
994 1000baseT master mode also has been added and brgphy(4), ciphy(4),
995 e1000phy(4) as well as ip1000phy(4) have been converted to take
996 advantage of it. This means that these drivers now no longer take the
997 link0 parameter for selecting master mode but the master media option
998 has to be used instead, for example like in the following:
999 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1001 Selection of master mode now is also available with all other PHY
1002 drivers supporting 1000baseT.
1005 The TCP stack has received a significant update to add support for
1006 modularised congestion control and generally improve the clarity of
1007 congestion control decisions. Bump __FreeBSD_version to 900025. User
1008 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1009 sockstat) need to be recompiled.
1012 The man(1) utility has been replaced by a new version that no longer
1013 uses /etc/manpath.config. Please consult man.conf(5) for how to
1014 migrate local entries to the new format.
1017 The copyright strings printed by login(1) and sshd(8) at the time of a
1018 new connection have been removed to follow other operating systems and
1022 A workaround for a fixed ld bug has been removed in kernel code,
1023 so make sure that your system ld is built from sources after
1024 revision 210245 from 2010-07-19 (r211583 if building head kernel
1025 on stable/8, r211584 for stable/7; both from 2010-08-21).
1026 A symptom of incorrect ld version is different addresses for
1027 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1030 The $ipv6_prefer variable in rc.conf(5) has been split into
1031 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1033 The $ip6addrctl_policy is a variable to choose a pre-defined
1034 address selection policy set by ip6addrctl(8). A value
1035 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1038 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1039 flag (see an entry of 20090926) is set on an interface with no
1040 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1041 security reason. If you want IPv6 link-local address on all
1042 interfaces by default, set this to "YES".
1044 The old ipv6_prefer="YES" is equivalent to
1045 ipv6_activate_all_interfaces="YES" and
1046 ip6addrctl_policy="ipv6_prefer".
1049 DTrace has grown support for userland tracing. Due to this, DTrace is
1050 now i386 and amd64 only.
1051 dtruss(1) is now installed by default on those systems and a new
1052 kernel module is needed for userland tracing: fasttrap.
1053 No changes to your kernel config file are necessary to enable
1054 userland tracing, but you might consider adding 'STRIP=' and
1055 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1056 to have informative userland stack traces in DTrace (ustack).
1059 The acpi_aiboost(4) driver has been removed in favor of the new
1060 aibs(4) driver. You should update your kernel configuration file.
1063 BSD grep has been imported to the base system and it is built by
1064 default. It is completely BSD licensed, highly GNU-compatible, uses
1065 less memory than its GNU counterpart and has a small codebase.
1066 However, it is slower than its GNU counterpart, which is mostly
1067 noticeable for larger searches, for smaller ones it is measurable
1068 but not significant. The reason is complex, the most important factor
1069 is that we lack a modern and efficient regex library and GNU
1070 overcomes this by optimizing the searches internally. Future work
1071 on improving the regex performance is planned, for the meantime,
1072 users that need better performance, can build GNU grep instead by
1073 setting the WITH_GNU_GREP knob.
1076 Due to the import of powerpc64 support, all existing powerpc kernel
1077 configuration files must be updated with a machine directive like this:
1078 machine powerpc powerpc
1080 In addition, an updated config(8) is required to build powerpc kernels
1084 A new version of ZFS (version 15) has been merged to -HEAD.
1085 This version uses a python library for the following subcommands:
1086 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1087 For full functionality of these commands the following port must
1088 be installed: sysutils/py-zfs
1091 'vm_page's are now hashed by physical address to an array of mutexes.
1092 Currently this is only used to serialize access to hold_count. Over
1093 time the page queue mutex will be peeled away. This changes the size
1094 of pmap on every architecture. And requires all callers of vm_page_hold
1095 and vm_page_unhold to be updated.
1098 WITH_CTF can now be specified in src.conf (not recommended, there
1099 are some problems with static executables), make.conf (would also
1100 affect ports which do not use GNU make and do not override the
1101 compile targets) or in the kernel config (via "makeoptions
1103 When WITH_CTF was specified there before this was silently ignored,
1104 so make sure that WITH_CTF is not used in places which could lead
1105 to unwanted behavior.
1108 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1109 to allow 32-bit compatibility on non-x86 platforms. All kernel
1110 configurations on amd64 and ia64 platforms using these options must
1111 be modified accordingly.
1114 The utmp user accounting database has been replaced with utmpx,
1115 the user accounting interface standardized by POSIX.
1116 Unfortunately the semantics of utmp and utmpx don't match,
1117 making it practically impossible to support both interfaces.
1118 The user accounting database is used by tools like finger(1),
1119 last(1), talk(1), w(1) and ac(8).
1121 All applications in the base system use utmpx. This means only
1122 local binaries (e.g. from the ports tree) may still use these
1123 utmp database files. These applications must be rebuilt to make
1126 After the system has been upgraded, it is safe to remove the old
1127 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1128 assuming their contents is of no importance anymore. Old wtmp
1129 databases can only be used by last(1) and ac(8) after they have
1130 been converted to the new format using wtmpcvt(1).
1133 Introduce the kernel thread "deadlock resolver" (which can be enabled
1134 via the DEADLKRES option, see NOTES for more details) and the
1135 sleepq_type() function for sleepqueues.
1138 The rc.firewall and rc.firewall6 were unified, and
1139 rc.firewall6 and rc.d/ip6fw were removed.
1140 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1141 variables are obsoleted. Instead, the following new rc
1142 variables are added to rc.d/ipfw:
1144 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1145 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1146 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1148 The meanings correspond to the relevant IPv4 variables.
1154 The default terminal emulation for syscons(4) has been changed
1155 from cons25 to xterm on all platforms except pc98. This means
1156 that the /etc/ttys file needs to be updated to ensure correct
1157 operation of applications on the console.
1159 The terminal emulation style can be toggled per window by using
1160 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1161 options can be used to change the compile-time default back to
1164 To prevent graphical artifacts, make sure the TERM environment
1165 variable is set to match the terminal emulation that is being
1166 performed by syscons(4).
1169 The layout of the structure ieee80211req_scan_result has changed.
1170 Applications that require wireless scan results (e.g. ifconfig(8))
1171 from net80211 need to be recompiled.
1173 Applications such as wpa_supplicant(8) may require a full world
1174 build without using NO_CLEAN in order to get synchronized with the
1178 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1179 There's one kernel module for each firmware. Adding "device iwnfw"
1180 to the kernel configuration file means including all three firmware
1181 images inside the kernel. If you want to include just the one for
1182 your wireless card, use the devices iwn4965fw, iwn5000fw or
1186 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1187 into rc.d/netif. The changes are the following:
1189 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1190 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1191 Note that both variables need the "inet6" keyword at the head.
1193 Do not set $ipv6_network_interfaces manually if you do not
1194 understand what you are doing. It is not needed in most cases.
1196 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1199 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1200 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1202 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1203 all configured interfaces have "inet6 accept_rtadv" in the
1204 $ifconfig_IF_ipv6. These are for backward compatibility.
1206 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1207 functionality of interfaces with no corresponding
1208 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1209 and the default address selection policy of ip6addrctl(8)
1210 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1211 Note that if you want to configure IPv6 functionality on the
1212 disabled interfaces after boot, first you need to clear the flag by
1213 using ifconfig(8) like:
1215 ifconfig em0 inet6 -ifdisabled
1217 If YES, the default address selection policy is set as
1220 The default value of $ipv6_prefer is NO.
1222 4. If your system need to receive Router Advertisement messages,
1223 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1224 scripts automatically invoke rtsol(8) when the interface becomes
1225 UP. The Router Advertisement messages are used for SLAAC
1226 (State-Less Address AutoConfiguration).
1229 802.11s D3.03 support was committed. This is incompatible with the
1230 previous code, which was based on D3.0.
1233 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1234 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1235 control whether accepting Router Advertisement messages or not.
1236 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1237 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1238 The ifconfig(8) utility now supports these flags.
1241 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1242 mount(8) and -a option for df(1) to see them.
1245 The old tunable hw.bus.devctl_disable has been superseded by
1246 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1247 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1251 Remove the option STOP_NMI. The default action is now to use NMI only
1252 for KDB via the newly introduced function stop_cpus_hard() and
1253 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1256 The stable/8 branch created in subversion. This corresponds to the
1257 RELENG_8 branch in CVS.
1260 Bump the shared library version numbers for all libraries that do not
1261 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1262 __FreeBSD_version to 800105.
1265 Due to changes in the implementation of virtual network stack support,
1266 all network-related kernel modules must be recompiled. As this change
1267 breaks the ABI, bump __FreeBSD_version to 800104.
1270 The TOE interface to the TCP syncache has been modified to remove
1271 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1272 The cxgb driver is the only TOE consumer affected by this change, and
1273 needs to be recompiled along with the kernel. As this change breaks
1274 the ABI, bump __FreeBSD_version to 800103.
1277 Padding has been added to struct tcpcb, sackhint and tcpstat in
1278 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1279 maintaining the ABI. However, this change breaks the ABI, so bump
1280 __FreeBSD_version to 800102. User space tools that rely on the size of
1281 any of these structs (e.g. sockstat) need to be recompiled.
1284 The NFS_LEGACYRPC option has been removed along with the old kernel
1285 RPC implementation that this option selected. Kernel configurations
1286 may need to be adjusted.
1289 The network interface device nodes at /dev/net/<interface> have been
1290 removed. All ioctl operations can be performed the normal way using
1291 routing sockets. The kqueue functionality can generally be replaced
1292 with routing sockets.
1295 The documentation from the FreeBSD Documentation Project (Handbook,
1296 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1297 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1300 The ABI of various structures related to the SYSV IPC API have been
1301 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1302 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1306 Layout of struct vnet has changed as routing related variables were
1307 moved to their own Vimage module. Modules need to be recompiled. Bump
1308 __FreeBSD_version to 800099.
1311 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1312 respectively. As long as no more than 16 groups per process are used,
1313 no changes should be visible. When more than 16 groups are used, old
1314 binaries may fail if they call getgroups() or getgrouplist() with
1315 statically sized storage. Recompiling will work around this, but
1316 applications should be modified to use dynamically allocated storage
1317 for group arrays as POSIX.1-2008 does not cap an implementation's
1318 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1320 NFS and portalfs mounts may also be affected as the list of groups is
1321 truncated to 16. Users of NFS who use more than 16 groups, should
1322 take care that negative group permissions are not used on the exported
1323 file systems as they will not be reliable unless a GSSAPI based
1324 authentication method is used.
1327 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1328 option compiles in the support for adaptive spinning for lockmgrs
1329 which want to enable it. The lockinit() function now accepts the flag
1330 LK_ADAPTIVE in order to make the lock object subject to adaptive
1331 spinning when both held in write and read mode.
1334 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1335 changed. User applications that use this ioctl need to be rebuilt.
1338 The layout of struct thread has changed. Kernel and modules need to
1342 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1343 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1346 window(1) has been removed from the base system. It can now be
1347 installed from ports. The port is called misc/window.
1350 The way we are storing and accessing `routing table' entries has
1351 changed. Programs reading the FIB, like netstat, need to be
1355 A new netisr implementation has been added for FreeBSD 8. Network
1356 file system modules, such as igmp, ipdivert, and others, should be
1358 Bump __FreeBSD_version to 800096.
1361 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1365 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1366 Bump __FreeBSD_version to 800094.
1369 Add mnt_xflag field to 'struct mount'. File system modules need to be
1371 Bump __FreeBSD_version to 800093.
1374 The compiling option ADAPTIVE_SX has been retired while it has been
1375 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1376 The KPI for sx_init_flags() changes as accepting flags:
1377 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1378 been introduced in order to handle the reversed logic.
1379 Bump __FreeBSD_version to 800092.
1382 Add support for hierarchical jails. Remove global securelevel.
1383 Bump __FreeBSD_version to 800091.
1386 The layout of struct vnet_net has changed, therefore modules
1388 Bump __FreeBSD_version to 800090.
1391 The newly imported zic(8) produces a new format in the output. Please
1392 run tzsetup(8) to install the newly created data to /etc/localtime.
1395 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1396 hw.usb.* and is now consistent again with previous releases.
1399 802.11 monitor mode support was revised and driver api's were changed.
1400 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1401 of DLT_IEEE802_11. No user-visible data structures were changed but
1402 applications that use DLT_IEEE802_11 may require changes.
1403 Bump __FreeBSD_version to 800088.
1406 The layout of the following structs has changed: sysctl_oid,
1407 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1408 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1409 panics may be experienced. World rebuild is required for
1410 correctly checking networking state from userland.
1411 Bump __FreeBSD_version to 800085.
1414 MLDv2 and Source-Specific Multicast (SSM) have been merged
1415 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1416 The implementation of SSM within FreeBSD's IPv6 stack closely
1417 follows the IPv4 implementation.
1419 For kernel developers:
1421 * The most important changes are that the ip6_output() and
1422 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1423 and this lock has been downgraded to a non-recursive mutex.
1425 * As with the changes to the IPv4 stack to support SSM, filtering
1426 of inbound multicast traffic must now be performed by transport
1427 protocols within the IPv6 stack. This does not apply to TCP and
1428 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1430 * The KPIs used by IPv6 multicast are similar to those used by
1431 the IPv4 stack, with the following differences:
1432 * im6o_mc_filter() is analogous to imo_multicast_filter().
1433 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1434 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1435 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1436 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1437 for MLDv1 have an additional 'timer' argument which is used to
1438 jitter the initial membership report for the solicited-node
1439 multicast membership on-link.
1440 * This is not strictly needed for MLDv2, which already jitters
1441 its report transmissions. However, the 'timer' argument is
1442 preserved in case MLDv1 is active on the interface.
1444 * The KAME linked-list based IPv6 membership implementation has
1445 been refactored to use a vector similar to that used by the IPv4
1447 Code which maintains a list of its own multicast memberships
1448 internally, e.g. carp, has been updated to reflect the new
1451 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1452 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1453 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1454 implementation constraint which needs to be addressed in HEAD.
1456 For application developers:
1458 * The changes are broadly similar to those made for the IPv4
1461 * The use of IPv4 and IPv6 multicast socket options on the same
1462 socket, using mapped addresses, HAS NOT been tested or supported.
1464 * There are a number of issues with the implementation of various
1465 IPv6 multicast APIs which need to be resolved in the API surface
1466 before the implementation is fully compatible with KAME userland
1467 use, and these are mostly to do with interface index treatment.
1469 * The literature available discusses the use of either the delta / ASM
1470 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1471 using setsourcefilter(3)/getsourcefilter(3). For more information
1472 please refer to RFC 3768, 'Socket Interface Extensions for
1473 Multicast Source Filters'.
1475 * Applications which use the published RFC 3678 APIs should be fine.
1477 For systems administrators:
1479 * The mtest(8) utility has been refactored to support IPv6, in
1480 addition to IPv4. Interface addresses are no longer accepted
1481 as arguments, their names must be used instead. The utility
1482 will map the interface name to its first IPv4 address as
1483 returned by getifaddrs(3).
1485 * The ifmcstat(8) utility has also been updated to print the MLDv2
1486 endpoint state and source filter lists via sysctl(3).
1488 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1489 loopback of IPv6 multicast datagrams by default; it defaults to 1
1490 to preserve the existing behaviour. Disabling multicast loopback is
1491 recommended for optimal system performance.
1493 * The IPv6 MROUTING code has been changed to examine this sysctl
1494 instead of attempting to perform a group lookup before looping
1495 back forwarded datagrams.
1497 Bump __FreeBSD_version to 800084.
1500 Implement low-level Bluetooth HCI API.
1501 Bump __FreeBSD_version to 800083.
1504 The layout of struct malloc_type, used by modules to register new
1505 memory allocation types, has changed. Most modules will need to
1506 be rebuilt or panics may be experienced.
1507 Bump __FreeBSD_version to 800081.
1510 Anticipate overflowing inp_flags - add inp_flags2.
1511 This changes most offsets in inpcb, so checking v4 connection
1512 state will require a world rebuild.
1513 Bump __FreeBSD_version to 800080.
1516 Add an llentry to struct route and struct route_in6. Modules
1517 embedding a struct route will need to be recompiled.
1518 Bump __FreeBSD_version to 800079.
1521 The size of rt_metrics_lite and by extension rtentry has changed.
1522 Networking administration apps will need to be recompiled.
1523 The route command now supports show as an alias for get, weighting
1524 of routes, sticky and nostick flags to alter the behavior of stateful
1526 Bump __FreeBSD_version to 800078.
1529 Do not use Giant for kbdmux(4) locking. This is wrong and
1530 apparently causing more problems than it solves. This will
1531 re-open the issue where interrupt handlers may race with
1532 kbdmux(4) in polling mode. Typical symptoms include (but
1533 not limited to) duplicated and/or missing characters when
1534 low level console functions (such as gets) are used while
1535 interrupts are enabled (for example geli password prompt,
1536 mountroot prompt etc.). Disabling kbdmux(4) may help.
1539 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1540 kernel modules referencing any of the above need to be recompiled.
1541 Bump __FreeBSD_version to 800075.
1544 GEOM_PART has become the default partition slicer for storage devices,
1545 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1546 introduces some changes:
1548 MSDOS/EBR: the devices created from MSDOS extended partition entries
1549 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1550 to devices with offset-based names. fstabs may need to be modified.
1552 BSD: the "geometry does not match label" warning is harmless in most
1553 cases but it points to problems in file system misalignment with
1554 disk geometry. The "c" partition is now implicit, covers the whole
1555 top-level drive and cannot be (mis)used by users.
1557 General: Kernel dumps are now not allowed to be written to devices
1558 whose partition types indicate they are meant to be used for file
1559 systems (or, in case of MSDOS partitions, as something else than
1562 Most of these changes date approximately from 200812.
1565 The uscanner(4) driver has been removed from the kernel. This follows
1566 Linux removing theirs in 2.6 and making libusb the default interface
1567 (supported by sane).
1570 The multicast forwarding code has been cleaned up. netstat(1)
1571 only relies on KVM now for printing bandwidth upcall meters.
1572 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1573 ip6_mroute_mod respectively. The config(5) options for statically
1574 compiling this code remain the same, i.e. 'options MROUTING'.
1577 Support for the IFF_NEEDSGIANT network interface flag has been
1578 removed, which means that non-MPSAFE network device drivers are no
1579 longer supported. In particular, if_ar, if_sr, and network device
1580 drivers from the old (legacy) USB stack can no longer be built or
1584 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1585 a bunch of new language catalog files have also been added.
1586 This means that some common libc messages are now localized and
1587 they depend on the LC_MESSAGES environmental variable.
1590 The k8temp(4) driver has been renamed to amdtemp(4) since
1591 support for Family 10 and Family 11 CPU families was added.
1594 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1595 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1597 For kernel developers, the most important changes are that the
1598 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1599 and this lock has been downgraded to a non-recursive mutex.
1601 Transport protocols (UDP, Raw IP) are now responsible for filtering
1602 inbound multicast traffic according to group membership and source
1603 filters. The imo_multicast_filter() KPI exists for this purpose.
1604 Transports which do not use multicast (SCTP, TCP) already reject
1605 multicast by default. Forwarding and receive performance may improve
1606 as a mutex acquisition is no longer needed in the ip_input()
1607 low-level input path. in_addmulti() and in_delmulti() are shimmed
1608 to new KPIs which exist to support SSM in-kernel.
1610 For application developers, it is recommended that loopback of
1611 multicast datagrams be disabled for best performance, as this
1612 will still cause the lock to be taken for each looped-back
1613 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1614 be tuned to 0 to disable loopback by default; it defaults to 1
1615 to preserve the existing behaviour.
1617 For systems administrators, to obtain best performance with
1618 multicast reception and multiple groups, it is always recommended
1619 that a card with a suitably precise hash filter is used. Hash
1620 collisions will still result in the lock being taken within the
1621 transport protocol input path to check group membership.
1623 If deploying FreeBSD in an environment with IGMP snooping switches,
1624 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1625 enabled; this forces 224.0.0.0/24 group membership to be announced
1628 The size of 'struct igmpstat' has changed; netstat needs to be
1629 recompiled to reflect this.
1630 Bump __FreeBSD_version to 800070.
1633 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1634 updated to use it. This requires a buildworld/installworld in order to
1635 update the library and dependencies (usbconfig, etc). Its advisable to
1636 rebuild all ports which uses libusb. More specific directions are given
1637 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1638 libusb are no longer required and can be removed.
1641 A workaround is committed to allow the creation of System V shared
1642 memory segment of size > 2 GB on the 64-bit architectures.
1643 Due to a limitation of the existing ABI, the shm_segsz member
1644 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1645 wrong for large segments. Note that limits must be explicitly
1646 raised to allow such segments to be created.
1649 The layout of struct ifnet has changed, requiring a rebuild of all
1650 network device driver modules.
1653 The /dev handling for the new USB stack has changed, a
1654 buildworld/installworld is required for libusb20.
1657 The new USB2 stack has now been permanently moved in and all kernel and
1658 module names reverted to their previous values (eg, usb, ehci, ohci,
1659 ums, ...). The old usb stack can be compiled in by prefixing the name
1660 with the letter 'o', the old usb modules have been removed.
1661 Updating entry 20090216 for xorg and 20090215 for libmap may still
1665 The rc.conf(5) option if_up_delay has been renamed to
1666 defaultroute_delay to better reflect its purpose. If you have
1667 customized this setting in /etc/rc.conf you need to update it to
1671 xorg 7.4 wants to configure its input devices via hald which does not
1672 yet work with USB2. If the keyboard/mouse does not work in xorg then
1674 Option "AllowEmptyInput" "off"
1675 to your ServerLayout section. This will cause X to use the configured
1676 kbd and mouse sections from your xorg.conf.
1679 The GENERIC kernels for all architectures now default to the new USB2
1680 stack. No kernel config options or code have been removed so if a
1681 problem arises please report it and optionally revert to the old USB
1682 stack. If you are loading USB kernel modules or have a custom kernel
1683 that includes GENERIC then ensure that usb names are also changed over,
1684 eg uftdi -> usb2_serial_ftdi.
1686 Older programs linked against the ports libusb 0.1 need to be
1687 redirected to the new stack's libusb20. /etc/libmap.conf can
1689 # Map old usb library to new one for usb2 stack
1690 libusb-0.1.so.8 libusb20.so.1
1693 All USB ethernet devices now attach as interfaces under the name ueN
1694 (eg. ue0). This is to provide a predictable name as vendors often
1695 change usb chipsets in a product without notice.
1698 The ichsmb(4) driver has been changed to require SMBus slave
1699 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1700 All of the other SMBus controller drivers require left-justified
1701 slave addresses, so this change makes all the drivers provide the
1705 INET6 statistics (struct ip6stat) was updated.
1706 netstat(1) needs to be recompiled.
1709 NTFS has been removed from GENERIC kernel on amd64 to match
1710 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1711 will load ntfs.ko module automatically when NTFS support is
1712 actually needed, unless ntfs.ko is not installed or security
1713 level prohibits loading kernel modules. If either is the case,
1714 "options NTFS" has to be added into kernel config.
1717 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1718 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1719 800061. User space tools that rely on the size of struct tcpcb in
1720 tcp_var.h (e.g. sockstat) need to be recompiled.
1723 ng_tty(4) module updated to match the new TTY subsystem.
1724 Due to API change, user-level applications must be updated.
1725 New API support added to mpd5 CVS and expected to be present
1726 in next mpd5.3 release.
1729 With __FreeBSD_version 800060 the makefs tool is part of
1730 the base system (it was a port).
1733 The afdata and ifnet locks have been changed from mutexes to
1734 rwlocks, network modules will need to be re-compiled.
1737 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1738 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1739 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1740 architecture and 40 bytes on 64-bit architecture. The userland
1741 applications "arp" and "ndp" have been updated accordingly.
1742 The output from "netstat -r" shows only routing entries and
1743 none of the L2 information.
1746 __FreeBSD_version 800057 marks the switchover from the
1747 binary ath hal to source code. Users must add the line:
1749 options AH_SUPPORT_AR5416
1751 to their kernel config files when specifying:
1755 The ath_hal module no longer exists; the code is now compiled
1756 together with the driver in the ath module. It is now
1757 possible to tailor chip support (i.e. reduce the set of chips
1758 and thereby the code size); consult ath_hal(4) for details.
1761 __FreeBSD_version 800054 adds memory barriers to
1762 <machine/atomic.h>, new interfaces to ifnet to facilitate
1763 multiple hardware transmit queues for cards that support
1764 them, and a lock-less ring-buffer implementation to
1765 enable drivers to more efficiently manage queueing of
1769 A new version of ZFS (version 13) has been merged to -HEAD.
1770 This version has zpool attribute "listsnapshots" off by
1771 default, which means "zfs list" does not show snapshots,
1772 and is the same as Solaris behavior.
1775 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1778 The uhci, ohci, ehci and slhci USB Host controller drivers have
1779 been put into separate modules. If you load the usb module
1780 separately through loader.conf you will need to load the
1781 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1782 controller add the following to loader.conf:
1788 The ABI used by the PMC toolset has changed. Please keep
1789 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1793 atapci kernel module now includes only generic PCI ATA
1794 driver. AHCI driver moved to ataahci kernel module.
1795 All vendor-specific code moved into separate kernel modules:
1796 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1797 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1798 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1799 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1802 The TTY subsystem of the kernel has been replaced by a new
1803 implementation, which provides better scalability and an
1804 improved driver model. Most common drivers have been migrated to
1805 the new TTY subsystem, while others have not. The following
1806 drivers have not yet been ported to the new TTY layer:
1809 cy, digi, rc, rp, sio
1815 ng_h4, ng_tty, ppp, sl, snp
1817 Adding these drivers to your kernel configuration file shall
1818 cause compilation to fail.
1821 ntpd has been upgraded to 4.2.4p5.
1824 OpenSSH has been upgraded to 5.1p1.
1826 For many years, FreeBSD's version of OpenSSH preferred DSA
1827 over RSA for host and user authentication keys. With this
1828 upgrade, we've switched to the vendor's default of RSA over
1829 DSA. This may cause upgraded clients to warn about unknown
1830 host keys even for previously known hosts. Users should
1831 follow the usual procedure for verifying host keys before
1832 accepting the RSA key.
1834 This can be circumvented by setting the "HostKeyAlgorithms"
1835 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1838 Please note that the sequence of keys offered for
1839 authentication has been changed as well. You may want to
1840 specify IdentityFile in a different order to revert this
1844 The sio(4) driver has been removed from the i386 and amd64
1845 kernel configuration files. This means uart(4) is now the
1846 default serial port driver on those platforms as well.
1848 To prevent collisions with the sio(4) driver, the uart(4) driver
1849 uses different names for its device nodes. This means the
1850 onboard serial port will now most likely be called "ttyu0"
1851 instead of "ttyd0". You may need to reconfigure applications to
1852 use the new device names.
1854 When using the serial port as a boot console, be sure to update
1855 /boot/device.hints and /etc/ttys before booting the new kernel.
1856 If you forget to do so, you can still manually specify the hints
1857 at the loader prompt:
1859 set hint.uart.0.at="isa"
1860 set hint.uart.0.port="0x3F8"
1861 set hint.uart.0.flags="0x10"
1862 set hint.uart.0.irq="4"
1866 The gpt(8) utility has been removed. Use gpart(8) to partition
1870 The version that Linuxulator emulates was changed from 2.4.2
1871 to 2.6.16. If you experience any problems with Linux binaries
1872 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1873 if it fixes the problem contact emulation mailing list.
1876 ISDN4BSD (I4B) was removed from the src tree. You may need to
1877 update a your kernel configuration and remove relevant entries.
1880 I have checked in code to support multiple routing tables.
1881 See the man pages setfib(1) and setfib(2).
1882 This is a hopefully backwards compatible version,
1883 but to make use of it you need to compile your kernel
1884 with options ROUTETABLES=2 (or more up to 16).
1887 The 802.11 wireless support was redone to enable multi-bss
1888 operation on devices that are capable. The underlying device
1889 is no longer used directly but instead wlanX devices are
1890 cloned with ifconfig. This requires changes to rc.conf files.
1891 For example, change:
1892 ifconfig_ath0="WPA DHCP"
1895 ifconfig_wlan0="WPA DHCP"
1896 see rc.conf(5) for more details. In addition, mergemaster of
1897 /etc/rc.d is highly recommended. Simultaneous update of userland
1898 and kernel wouldn't hurt either.
1900 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1901 modules were merged into the base wlan module. All references
1902 to these modules (e.g. in kernel config files) must be removed.
1905 psm(4) has gained write(2) support in native operation level.
1906 Arbitrary commands can be written to /dev/psm%d and status can
1907 be read back from it. Therefore, an application is responsible
1908 for status validation and error recovery. It is a no-op in
1909 other operation levels.
1912 Support for KSE threading has been removed from the kernel. To
1913 run legacy applications linked against KSE libmap.conf may
1914 be used. The following libmap.conf may be used to ensure
1915 compatibility with any prior release:
1917 libpthread.so.1 libthr.so.1
1918 libpthread.so.2 libthr.so.2
1919 libkse.so.3 libthr.so.3
1922 The layout of struct vmspace has changed. This affects libkvm
1923 and any executables that link against libkvm and use the
1924 kvm_getprocs() function. In particular, but not exclusively,
1925 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1926 The effects are minimal, but it's advisable to upgrade world
1930 The latest em driver no longer has support in it for the
1931 82575 adapter, this is now moved to the igb driver. The
1932 split was done to make new features that are incompatible
1933 with older hardware easier to do.
1936 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1937 likewise the kernel option is now GEOM_LINUX_LVM.
1940 The default NFS mount mode has changed from UDP to TCP for
1941 increased reliability. If you rely on (insecurely) NFS
1942 mounting across a firewall you may need to update your
1946 Belatedly note the addition of m_collapse for compacting
1950 The fts(3) structures have been changed to use adequate
1951 integer types for their members and so to be able to cope
1952 with huge file trees. The old fts(3) ABI is preserved
1953 through symbol versioning in libc, so third-party binaries
1954 using fts(3) should still work, although they will not take
1955 advantage of the extended types. At the same time, some
1956 third-party software might fail to build after this change
1957 due to unportable assumptions made in its source code about
1958 fts(3) structure members. Such software should be fixed
1959 by its vendor or, in the worst case, in the ports tree.
1960 FreeBSD_version 800015 marks this change for the unlikely
1961 case that a portable fix is impossible.
1964 To upgrade to -current after this date, you must be running
1965 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1966 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1969 The ADAPTIVE_GIANT kernel option has been retired because its
1970 functionality is the default now.
1973 The AT keyboard emulation of sunkbd(4) has been turned on
1974 by default. In order to make the special symbols of the Sun
1975 keyboards driven by sunkbd(4) work under X these now have
1976 to be configured the same way as Sun USB keyboards driven
1977 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1979 Option "XkbLayout" "us"
1980 Option "XkbRules" "xorg"
1981 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1984 It has been decided that it is desirable to provide ABI
1985 backwards compatibility to the FreeBSD 4/5/6 versions of the
1986 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1987 broken with the introduction of PCI domain support (see the
1988 20070930 entry). Unfortunately, this required the ABI of
1989 PCIOCGETCONF to be broken again in order to be able to
1990 provide backwards compatibility to the old version of that
1991 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1992 again. As for prominent ports this affects neither pciutils
1993 nor xorg-server this time, the hal port needs to be rebuilt
1997 The misnamed kthread_create() and friends have been renamed
1998 to kproc_create() etc. Many of the callers already
1999 used kproc_start()..
2000 I will return kthread_create() and friends in a while
2001 with implementations that actually create threads, not procs.
2002 Renaming corresponds with version 800002.
2011 Avoid using make -j when upgrading. While generally safe, there are
2012 sometimes problems using -j to upgrade. If your upgrade fails with
2013 -j, please try again without -j. From time to time in the past there
2014 have been problems using -j with buildworld and/or installworld. This
2015 is especially true when upgrading between "distant" versions (eg one
2016 that cross a major release boundary or several minor releases, or when
2017 several months have passed on the -current branch).
2019 Sometimes, obscure build problems are the result of environment
2020 poisoning. This can happen because the make utility reads its
2021 environment when searching for values for global variables. To run
2022 your build attempts in an "environmental clean room", prefix all make
2023 commands with 'env -i '. See the env(1) manual page for more details.
2025 When upgrading from one major version to another it is generally best
2026 to upgrade to the latest code in the currently installed branch first,
2027 then do an upgrade to the new branch. This is the best-tested upgrade
2028 path, and has the highest probability of being successful. Please try
2029 this approach before reporting problems with a major version upgrade.
2031 When upgrading a live system, having a root shell around before
2032 installing anything can help undo problems. Not having a root shell
2033 around can lead to problems if pam has changed too much from your
2034 starting point to allow continued authentication after the upgrade.
2038 When upgrading the boot ZFS pool to a new version, always follow
2041 1.) recompile and reinstall the ZFS boot loader and boot block
2042 (this is part of "make buildworld" and "make installworld")
2044 2.) update the ZFS boot block on your boot drive
2046 The following example updates the ZFS boot block on the first
2047 partition (freebsd-boot) of a GPT partitioned drive ad0:
2048 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2050 Non-boot pools do not need these updates.
2054 If you are updating from a prior version of FreeBSD (even one just
2055 a few days old), you should follow this procedure. It is the most
2056 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2058 make kernel-toolchain
2059 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2060 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2062 To test a kernel once
2063 ---------------------
2064 If you just want to boot a kernel once (because you are not sure
2065 if it works, or if you want to boot a known bad kernel to provide
2066 debugging information) run
2067 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2068 nextboot -k testkernel
2070 To just build a kernel when you know that it won't mess you up
2071 --------------------------------------------------------------
2072 This assumes you are already running a CURRENT system. Replace
2073 ${arch} with the architecture of your machine (e.g. "i386",
2074 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2076 cd src/sys/${arch}/conf
2077 config KERNEL_NAME_HERE
2078 cd ../compile/KERNEL_NAME_HERE
2083 If this fails, go to the "To build a kernel" section.
2085 To rebuild everything and install it on the current system.
2086 -----------------------------------------------------------
2087 # Note: sometimes if you are running current you gotta do more than
2088 # is listed here if you are upgrading from a really old current.
2090 <make sure you have good level 0 dumps>
2092 make kernel KERNCONF=YOUR_KERNEL_HERE
2094 <reboot in single user> [3]
2101 To cross-install current onto a separate partition
2102 --------------------------------------------------
2103 # In this approach we use a separate partition to hold
2104 # current's root, 'usr', and 'var' directories. A partition
2105 # holding "/", "/usr" and "/var" should be about 2GB in
2108 <make sure you have good level 0 dumps>
2111 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2112 <maybe newfs current's root partition>
2113 <mount current's root partition on directory ${CURRENT_ROOT}>
2114 make installworld DESTDIR=${CURRENT_ROOT}
2115 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2116 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2117 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2118 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2119 <reboot into current>
2120 <do a "native" rebuild/install as described in the previous section>
2121 <maybe install compatibility libraries from ports/misc/compat*>
2125 To upgrade in-place from stable to current
2126 ----------------------------------------------
2127 <make sure you have good level 0 dumps>
2129 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2131 <reboot in single user> [3]
2138 Make sure that you've read the UPDATING file to understand the
2139 tweaks to various things you need. At this point in the life
2140 cycle of current, things change often and you are on your own
2141 to cope. The defaults can also change, so please read ALL of
2142 the UPDATING entries.
2144 Also, if you are tracking -current, you must be subscribed to
2145 freebsd-current@freebsd.org. Make sure that before you update
2146 your sources that you have read and understood all the recent
2147 messages there. If in doubt, please track -stable which has
2148 much fewer pitfalls.
2150 [1] If you have third party modules, such as vmware, you
2151 should disable them at this point so they don't crash your
2154 [3] From the bootblocks, boot -s, and then do
2159 adjkerntz -i # if CMOS is wall time
2160 Also, when doing a major release upgrade, it is required that
2161 you boot into single user mode to do the installworld.
2163 [4] Note: This step is non-optional. Failure to do this step
2164 can result in a significant reduction in the functionality of the
2165 system. Attempting to do it by hand is not recommended and those
2166 that pursue this avenue should read this file carefully, as well
2167 as the archives of freebsd-current and freebsd-hackers mailing lists
2168 for potential gotchas. The -U option is also useful to consider.
2169 See mergemaster(8) for more information.
2171 [5] Usually this step is a noop. However, from time to time
2172 you may need to do this if you get unknown user in the following
2173 step. It never hurts to do it all the time. You may need to
2174 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2175 install) after the buildworld before this step if you last updated
2176 from current before 20130425 or from -stable before 20130430.
2178 [6] This only deletes old files and directories. Old libraries
2179 can be deleted by "make delete-old-libs", but you have to make
2180 sure that no program is using those libraries anymore.
2182 [8] In order to have a kernel that can run the 4.x binaries needed to
2183 do an installworld, you must include the COMPAT_FREEBSD4 option in
2184 your kernel. Failure to do so may leave you with a system that is
2185 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2186 required to run the 5.x binaries on more recent kernels. And so on
2187 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2189 Make sure that you merge any new devices from GENERIC since the
2190 last time you updated your kernel config file.
2192 [9] When checking out sources, you must include the -P flag to have
2193 cvs prune empty directories.
2195 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2196 "?=" instead of the "=" assignment operator, so that buildworld can
2197 override the CPUTYPE if it needs to.
2199 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2200 not on the command line, or in /etc/make.conf. buildworld will
2201 warn if it is improperly defined.
2204 This file contains a list, in reverse chronological order, of major
2205 breakages in tracking -current. It is not guaranteed to be a complete
2206 list of such breakages, and only contains entries since October 10, 2007.
2207 If you need to see UPDATING entries from before that date, you will need
2208 to fetch an UPDATING file from an older FreeBSD release.
2210 Copyright information:
2212 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2214 Redistribution, publication, translation and use, with or without
2215 modification, in full or in part, in any form or format of this
2216 document are permitted without further permission from the author.
2218 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2219 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2220 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2221 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2222 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2223 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2224 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2225 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2226 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2227 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2228 POSSIBILITY OF SUCH DAMAGE.
2230 Contact Warner Losh if you have any questions about your use of