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.
20 As ZFS requires more kernel stack pages than is the default on some
21 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
22 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
24 Please consider using 'options KSTACK_PAGES=X' where X is greater
25 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
28 The default Unbound configuration now enables remote control
29 using a local socket. Users who have already enabled the
30 local_unbound service should regenerate their configuration
31 by running "service local_unbound setup" as root.
34 An additional fix for the issue described in the 20150614 sendmail
35 entry below has been been committed in revision 284786.
38 The fix for the issue described in the 20150614 sendmail entry
39 below has been been committed in revision 284485. The work
40 around described in that entry is no longer needed unless the
41 default setting is overridden by a confDH_PARAMETERS configuration
42 setting of '5' or pointing to a 512 bit DH parameter file.
45 The import of openssl to address the FreeBSD-SA-15:10.openssl
46 security advisory includes a change which rejects handshakes
47 with DH parameters below 768 bits. sendmail releases prior
48 to 8.15.2 (not yet released), defaulted to a 512 bit
49 DH parameter setting for client connections. To work around
50 this interoperability, sendmail can be configured to use a
51 2048 bit DH parameter by:
53 1. Edit /etc/mail/`hostname`.mc
54 2. If a setting for confDH_PARAMETERS does not exist or
55 exists and is set to a string beginning with '5',
57 3. If a setting for confDH_PARAMETERS exists and is set to
58 a file path, create a new file with:
59 openssl dhparam -out /path/to/file 2048
60 4. Rebuild the .cf file:
61 cd /etc/mail/; make; make install
63 cd /etc/mail/; make restart
65 A sendmail patch is coming, at which time this file will be
69 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
70 defined in symlink(7); previously symlinks were silently ignored.
73 The const qualifier has been removed from iconv(3) to comply with
74 POSIX. The ports tree is aware of this from r384038 onwards.
77 At svn r275807, The default linux compat kernel ABI has been adjusted
78 to 2.6.18 in support of the linux-c6 compat ports infrastructure
79 update. If you wish to continue using the linux-f10 compat ports,
80 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
81 encouraged to update their linux-compat packages to linux-c6 during
82 their next update cycle.
84 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
87 pjdfstest has been integrated into kyua as an opt-in test suite.
88 Please see share/doc/pjdfstest/README for a more details on how to
95 The ofwfb driver, used to provide a graphics console on PowerPC when
96 using vt(4), no longer allows mmap() of all of physical memory. This
97 will prevent Xorg on PowerPC with some ATI graphics cards from
98 initializing properly unless x11-servers/xorg-server is updated to
102 The libatf-c and libatf-c++ major versions were downgraded to 0 and
103 1 respectively to match the upstream numbers. They were out of
104 sync because, when they were originally added to FreeBSD, the
105 upstream versions were not respected. These libraries are private
106 and not yet built by default, so renumbering them should be a
107 non-issue. However, unclean source trees will yield broken test
108 programs once the operator executes "make delete-old-libs" after a
111 Additionally, the atf-sh binary was made private by moving it into
112 /usr/libexec/. Already-built shell test programs will keep the
113 path to the old binary so they will break after "make delete-old"
116 If you are using WITH_TESTS=yes (not the default), wipe the object
117 tree and rebuild from scratch to prevent spurious test failures.
118 This is only needed once: the misnumbered libraries and misplaced
119 binaries have been added to OptionalObsoleteFiles.inc so they will
120 be removed during a clean upgrade.
123 The ixgbe tunables now match their sysctl counterparts, for example:
124 hw.ixgbe.enable_aim => hw.ix.enable_aim
125 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
128 The NFSv4.1 server committed by r269398 changes the internal
129 function call interfaces used between the NFS and krpc modules.
130 As such, __FreeBSD_version was bumped.
133 The default unbound configuration has been modified to address
134 issues with reverse lookups on networks that use private
135 address ranges. If you use the local_unbound service, run
136 "service local_unbound setup" as root to regenerate your
137 configuration, then "service local_unbound reload" to load the
141 It is no longer necessary to include the dwarf version in your DEBUG
142 options in your kernel config file. The bug that required it to be
143 placed in the config file has bene fixed. DEBUG should now just
144 contain -g. The build system will automatically update things
145 to do the right thing.
148 Several ABI breaking changes were merged to CTL and new iSCSI code.
149 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
150 iscsictl need to be rebuilt to work with a new kernel.
153 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
154 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
155 which differs from the behaviour controlled by this knob.)
158 On i386 and amd64 systems, the onifconsole flag is now set by default
159 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
160 as a login TTY if it is set in the bootloader as an active kernel
161 console. No changes in behavior should result otherwise. To revert to
162 the previous behavior, set ttyu0 to "off" in /etc/ttys.
165 Clang and llvm have been upgraded to 3.4.1 release.
168 Clang and llvm have been upgraded to 3.4 release.
171 If a Makefile in a tests/ directory was auto-generating a Kyuafile
172 instead of providing an explicit one, this would prevent such
173 Makefile from providing its own Kyuafile in the future during
174 NO_CLEAN builds. This has been fixed in the Makefiles but manual
175 intervention is needed to clean an objdir if you use NO_CLEAN:
176 # find /usr/obj -name Kyuafile | xargs rm -f
179 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
180 capability mode support. Please note that enabling the feature in
181 kernel is still highly recommended.
184 OpenSSH is now built with sandbox support, and will use sandbox as
185 the default privilege separation method. This requires Capsicum
186 capability mode support in kernel.
189 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
190 been deprecated and will not be part of FreeBSD 11.0 and later
191 releases. If you use this driver, please consider switching to
192 the nfe(4) driver instead.
198 The behavior of gss_pseudo_random() for the krb5 mechanism
199 has changed, for applications requesting a longer random string
200 than produced by the underlying enctype's pseudo-random() function.
201 In particular, the random string produced from a session key of
202 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
203 be different at the 17th octet and later, after this change.
204 The counter used in the PRF+ construction is now encoded as a
205 big-endian integer in accordance with RFC 4402.
206 __FreeBSD_version is bumped to 1000701.
209 The WITHOUT_ATF build knob has been removed and its functionality
210 has been subsumed into the more generic WITHOUT_TESTS. If you were
211 using the former to disable the build of the ATF libraries, you
212 should change your settings to use the latter.
215 The default version of mtree is nmtree which is obtained from
216 NetBSD. The output is generally the same, but may vary
217 slightly. If you found you need identical output adding
218 "-F freebsd9" to the command line should do the trick. For the
219 time being, the old mtree is available as fmtree.
222 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
223 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
224 1.1.4_8 and verify bsdyml not linked in, before running "make
226 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
228 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
231 The rc.d/jail script has been updated to support jail(8)
232 configuration file. The "jail_<jname>_*" rc.conf(5) variables
233 for per-jail configuration are automatically converted to
234 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
235 This is transparently backward compatible. See below about some
236 incompatibilities and rc.conf(5) manual page for more details.
238 These variables are now deprecated in favor of jail(8) configuration
239 file. One can use "rc.d/jail config <jname>" command to generate
240 a jail(8) configuration file in /var/run/jail.<jname>.conf without
241 running the jail(8) utility. The default pathname of the
242 configuration file is /etc/jail.conf and can be specified by
243 using $jail_conf or $jail_<jname>_conf variables.
245 Please note that jail_devfs_ruleset accepts an integer at
246 this moment. Please consider to rewrite the ruleset name
250 BIND has been removed from the base system. If all you need
251 is a local resolver, simply enable and start the local_unbound
252 service instead. Otherwise, several versions of BIND are
253 available in the ports tree. The dns/bind99 port is one example.
255 With this change, nslookup(1) and dig(1) are no longer in the base
256 system. Users should instead use host(1) and drill(1) which are
257 in the base system. Alternatively, nslookup and dig can
258 be obtained by installing the dns/bind-tools port.
261 With the addition of unbound(8), a new unbound user is now
262 required during installworld. "mergemaster -p" can be used to
263 add the user prior to installworld, as documented in the handbook.
266 OpenSSH is now built with DNSSEC support, and will by default
267 silently trust signed SSHFP records. This can be controlled with
268 the VerifyHostKeyDNS client configuration setting. DNSSEC support
269 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
272 The GNU Compiler Collection and C++ standard library (libstdc++)
273 are no longer built by default on platforms where clang is the system
274 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
278 The PROCDESC kernel option is now part of the GENERIC kernel
279 configuration and is required for the rwhod(8) to work.
280 If you are using custom kernel configuration, you should include
284 The API and ABI related to the Capsicum framework was modified
285 in backward incompatible way. The userland libraries and programs
286 have to be recompiled to work with the new kernel. This includes the
287 following libraries and programs, but the whole buildworld is
288 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
289 kdump, procstat, rwho, rwhod, uniq.
292 AES-NI intrinsic support has been added to gcc. The AES-NI module
293 has been updated to use this support. A new gcc is required to build
294 the aesni module on both i386 and amd64.
297 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
298 Thus "device padlock_rng" and "device rdrand_rng" should be
299 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
302 WITH_ICONV has been split into two feature sets. WITH_ICONV now
303 enables just the iconv* functionality and is now on by default.
304 WITH_LIBICONV_COMPAT enables the libiconv api and link time
305 compatability. Set WITHOUT_ICONV to build the old way.
306 If you have been using WITH_ICONV before, you will very likely
307 need to turn on WITH_LIBICONV_COMPAT.
310 INVARIANTS option now enables DEBUG for code with OpenSolaris and
311 Illumos origin, including ZFS. If you have INVARIANTS in your
312 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
314 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
315 locks if WITNESS option was set. Because that generated a lot of
316 witness(9) reports and all of them were believed to be false
317 positives, this is no longer done. New option OPENSOLARIS_WITNESS
318 can be used to achieve the previous behavior.
321 Timer values in IPv6 data structures now use time_uptime instead
322 of time_second. Although this is not a user-visible functional
323 change, userland utilities which directly use them---ndp(8),
324 rtadvd(8), and rtsold(8) in the base system---need to be updated
328 find -delete can now delete the pathnames given as arguments,
329 instead of only files found below them or if the pathname did
330 not contain any slashes. Formerly, the following error message
333 find: -delete: <path>: relative path potentially not safe
335 Deleting the pathnames given as arguments can be prevented
336 without error messages using -mindepth 1 or by changing
337 directory and passing "." as argument to find. This works in the
338 old as well as the new version of find.
341 Behavior of devfs rules path matching has been changed.
342 Pattern is now always matched against fully qualified devfs
343 path and slash characters must be explicitly matched by
344 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
345 subdirectories must be reviewed.
348 The default ARM ABI has changed to the ARM EABI. The old ABI is
349 incompatible with the ARM EABI and all programs and modules will
350 need to be rebuilt to work with a new kernel.
352 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
354 NOTE: Support for the old ABI will be removed in the future and
355 users are advised to upgrade.
358 pkg_install has been disconnected from the build if you really need it
359 you should add WITH_PKGTOOLS in your src.conf(5).
362 Most of network statistics structures were changed to be able
363 keep 64-bits counters. Thus all tools, that work with networking
364 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
367 Fix targets that run multiple make's to use && rather than ;
368 so that subsequent steps depend on success of previous.
370 NOTE: if building 'universe' with -j* on stable/8 or stable/9
371 it would be better to start the build using bmake, to avoid
372 overloading the machine.
375 Fix a bug that allowed a tracing process (e.g. gdb) to write
376 to a memory-mapped file in the traced process's address space
377 even if neither the traced process nor the tracing process had
378 write access to that file.
381 CVS has been removed from the base system. An exact copy
382 of the code is available from the devel/cvs port.
385 Some people report the following error after the switch to bmake:
387 make: illegal option -- J
388 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
390 *** [buildworld] Error code 2
392 this likely due to an old instance of make in
393 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
394 which src/Makefile will use that blindly, if it exists, so if
395 you see the above error:
397 rm -rf `make -V MAKEPATH`
402 Use bmake by default.
403 Whereas before one could choose to build with bmake via
404 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
405 make. The goal is to remove these knobs for 10-RELEASE.
407 It is worth noting that bmake (like gmake) treats the command
408 line as the unit of failure, rather than statements within the
409 command line. Thus '(cd some/where && dosomething)' is safer
410 than 'cd some/where; dosomething'. The '()' allows consistent
411 behavior in parallel build.
414 Fix a bug that allows NFS clients to issue READDIR on files.
417 The WITHOUT_IDEA option has been removed because
418 the IDEA patent expired.
421 The sysctl which controls TRIM support under ZFS has been renamed
422 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
426 The mergemaster command now uses the default MAKEOBJDIRPREFIX
427 rather than creating it's own in the temporary directory in
428 order allow access to bootstrapped versions of tools such as
429 install and mtree. When upgrading from version of FreeBSD where
430 the install command does not support -l, you will need to
431 install a new mergemaster command if mergemaster -p is required.
432 This can be accomplished with the command (cd src/usr.sbin/mergemaster
436 Legacy ATA stack, disabled and replaced by new CAM-based one since
437 FreeBSD 9.0, completely removed from the sources. Kernel modules
438 atadisk and atapi*, user-level tools atacontrol and burncd are
439 removed. Kernel option `options ATA_CAM` is now permanently enabled
443 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
444 and socketpair(2). Software, in particular Kerberos, may
445 automatically detect and use these during building. The resulting
446 binaries will not work on older kernels.
449 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
450 information, see the respective 20130304 entry).
453 Recent commits to callout(9) changed the size of struct callout,
454 so the KBI is probably heavily disturbed. Also, some functions
455 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
456 by macros. Every kernel module using it won't load, so rebuild
459 The ctl device has been re-enabled in GENERIC for i386 and amd64,
460 but does not initialize by default (because of the new CTL_DISABLE
461 option) to save memory. To re-enable it, remove the CTL_DISABLE
462 option from the kernel config file or set kern.cam.ctl.disable=0
463 in /boot/loader.conf.
466 The ctl device has been disabled in GENERIC for i386 and amd64.
467 This was done due to the extra memory being allocated at system
468 initialisation time by the ctl driver which was only used if
469 a CAM target device was created. This makes a FreeBSD system
470 unusable on 128MB or less of RAM.
473 A new compression method (lz4) has been merged to -HEAD. Please
474 refer to zpool-features(7) for more information.
476 Please refer to the "ZFS notes" section of this file for information
477 on upgrading boot ZFS pools.
480 A BSD-licensed patch(1) variant has been added and is installed
481 as bsdpatch, being the GNU version the default patch.
482 To inverse the logic and use the BSD-licensed one as default,
483 while having the GNU version installed as gnupatch, rebuild
484 and install world with the WITH_BSD_PATCH knob set.
487 Due to the use of the new -l option to install(1) during build
488 and install, you must take care not to directly set the INSTALL
489 make variable in your /etc/make.conf, /etc/src.conf, or on the
490 command line. If you wish to use the -C flag for all installs
491 you may be able to add INSTALL+=-C to /etc/make.conf or
495 The install(1) option -M has changed meaning and now takes an
496 argument that is a file or path to append logs to. In the
497 unlikely event that -M was the last option on the command line
498 and the command line contained at least two files and a target
499 directory the first file will have logs appended to it. The -M
500 option served little practical purpose in the last decade so its
501 use is expected to be extremely rare.
504 After switching to Clang as the default compiler some users of ZFS
505 on i386 systems started to experience stack overflow kernel panics.
506 Please consider using 'options KSTACK_PAGES=4' in such configurations.
509 GEOM_LABEL now mangles label names read from file system metadata.
510 Mangling affect labels containing spaces, non-printable characters,
511 '%' or '"'. Device names in /etc/fstab and other places may need to
515 By default, only the 10 most recent kernel dumps will be saved. To
516 restore the previous behaviour (no limit on the number of kernel dumps
517 stored in the dump directory) add the following line to /etc/rc.conf:
522 With the addition of auditdistd(8), a new auditdistd user is now
523 required during installworld. "mergemaster -p" can be used to
524 add the user prior to installworld, as documented in the handbook.
527 The sin6_scope_id member variable in struct sockaddr_in6 is now
528 filled by the kernel before passing the structure to the userland via
529 sysctl or routing socket. This means the KAME-specific embedded scope
530 id in sin6_addr.s6_addr[2] is always cleared in userland application.
531 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
532 __FreeBSD_version is bumped to 1000025.
535 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
536 This means that the world and kernel will be compiled with clang
537 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
538 and /usr/bin/cpp. To disable this behavior and revert to building
539 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
540 of current may need to bootstrap WITHOUT_CLANG first if the clang
541 build fails (its compatibility window doesn't extend to the 9 stable
545 The IPFIREWALL_FORWARD kernel option has been removed. Its
546 functionality now turned on by default.
549 The ZERO_COPY_SOCKET kernel option has been removed and
550 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
551 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
552 mechanism which is not safe and may result in kernel crashes.
553 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
554 driver supports disposeable external page sized mbuf storage.
555 Proper replacements for both zero-copy mechanisms are under
556 consideration and will eventually lead to complete removal
557 of the two kernel options.
560 The IPv4 network stack has been converted to network byte
561 order. The following modules need to be recompiled together
562 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
563 pf(4), ipfw(4), ng_ipfw(4), stf(4).
566 Support for non-MPSAFE filesystems was removed from VFS. The
567 VFS_VERSION was bumped, all filesystem modules shall be
571 All the non-MPSAFE filesystems have been disconnected from
572 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
573 portalfs, smbfs, xfs.
576 The interface cloning API and ABI has changed. The following
577 modules need to be recompiled together with kernel:
578 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
579 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
580 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
583 The sdhci driver was split in two parts: sdhci (generic SD Host
584 Controller logic) and sdhci_pci (actual hardware driver).
585 No kernel config modifications are required, but if you
586 load sdhc as a module you must switch to sdhci_pci instead.
589 Import the FUSE kernel and userland support into base system.
592 The GNU sort(1) program has been removed since the BSD-licensed
593 sort(1) has been the default for quite some time and no serious
594 problems have been reported. The corresponding WITH_GNU_SORT
598 The pfil(9) API/ABI for AF_INET family has been changed. Packet
599 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
603 The net80211(4) ABI has been changed to allow for improved driver
604 PS-POLL and power-save support. All wireless drivers need to be
605 recompiled to work with the new kernel.
608 The random(4) support for the VIA hardware random number
609 generator (`PADLOCK') is no longer enabled unconditionally.
610 Add the padlock_rng device in the custom kernel config if
611 needed. The GENERIC kernels on i386 and amd64 do include the
612 device, so the change only affects the custom kernel
616 The pf(4) packet filter ABI has been changed. pfctl(8) and
617 snmp_pf module need to be recompiled to work with new kernel.
620 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
621 to -HEAD. Pools that have empty_bpobj in active state can not be
622 imported read-write with ZFS implementations that do not support
623 this feature. For more information read the zpool-features(5)
627 The sparc64 ZFS loader has been changed to no longer try to auto-
628 detect ZFS providers based on diskN aliases but now requires these
629 to be explicitly listed in the OFW boot-device environment variable.
632 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
633 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
634 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
637 The following sysctls and tunables have been renamed for consistency
638 with other variables:
639 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
640 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
643 The sort utility has been replaced with BSD sort. For now, GNU sort
644 is also available as "gnusort" or the default can be set back to
645 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
646 installed as "bsdsort".
649 A new version of ZFS (pool version 5000) has been merged to -HEAD.
650 Starting with this version the old system of ZFS pool versioning
651 is superseded by "feature flags". This concept enables forward
652 compatibility against certain future changes in functionality of ZFS
653 pools. The first read-only compatible "feature flag" for ZFS pools
654 is named "com.delphix:async_destroy". For more information
655 read the new zpool-features(5) manual page.
656 Please refer to the "ZFS notes" section of this file for information
657 on upgrading boot ZFS pools.
660 The malloc(3) implementation embedded in libc now uses sources imported
661 as contrib/jemalloc. The most disruptive API change is to
662 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
663 delete it prior to installworld, and optionally re-create it using the
664 new format after rebooting. See malloc.conf(5) for details
665 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
669 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
670 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
671 now spelled mips. This is to aid compatibility with third-party
672 software that expects this naming scheme in uname(3). Little-endian
673 settings are unchanged. If you are updating a big-endian mips64 machine
674 from before this change, you may need to set MACHINE_ARCH=mips64 in
675 your environment before the new build system will recognize your machine.
678 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
682 Now unix domain sockets behave "as expected" on nullfs(5). Previously
683 nullfs(5) did not pass through all behaviours to the underlying layer,
684 as a result if we bound to a socket on the lower layer we could connect
685 only to the lower path; if we bound to the upper layer we could connect
686 only to the upper path. The new behavior is one can connect to both the
687 lower and the upper paths regardless what layer path one binds to.
690 The getifaddrs upgrade path broken with 20111215 has been restored.
691 If you have upgraded in between 20111215 and 20120209 you need to
692 recompile libc again with your kernel. You still need to recompile
693 world to be able to configure CARP but this restriction already
697 The set_rcvar() function has been removed from /etc/rc.subr. All
698 base and ports rc.d scripts have been updated, so if you have a
699 port installed with a script in /usr/local/etc/rc.d you can either
700 hand-edit the rcvar= line, or reinstall the port.
702 An easy way to handle the mass-update of /etc/rc.d:
703 rm /etc/rc.d/* && mergemaster -i
706 panic(9) now stops other CPUs in the SMP systems, disables interrupts
707 on the current CPU and prevents other threads from running.
708 This behavior can be reverted using the kern.stop_scheduler_on_panic
710 The new behavior can be incompatible with kern.sync_on_panic.
713 The carp(4) facility has been changed significantly. Configuration
714 of the CARP protocol via ifconfig(8) has changed, as well as format
715 of CARP events submitted to devd(8) has changed. See manual pages
716 for more information. The arpbalance feature of carp(4) is currently
717 not supported anymore.
719 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
720 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
721 need to be recompiled.
724 The acpi_wmi(4) status device /dev/wmistat has been renamed to
728 The option VFS_ALLOW_NONMPSAFE option has been added in order to
729 explicitely support non-MPSAFE filesystems.
730 It is on by default for all supported platform at this present
734 The broken amd(4) driver has been replaced with esp(4) in the amd64,
735 i386 and pc98 GENERIC kernel configuration files.
738 sysinstall has been removed
741 The stable/9 branch created in subversion. This corresponds to the
742 RELENG_9 branch in CVS.
745 This commit modifies vfs_register() so that it uses a hash
746 calculation to set vfc_typenum, which is enabled by default.
747 The first time a system is booted after this change, the
748 vfc_typenum values will change for all file systems. The
749 main effect of this is a change to the NFS server file handles
750 for file systems that use vfc_typenum in their fsid, such as ZFS.
751 It will, however, prevent vfc_typenum from changing when file
752 systems are loaded in a different order for subsequent reboots.
753 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
754 until you are ready to remount all NFS clients after a reboot.
757 Bump the shared library version numbers for libraries that
758 do not use symbol versioning, have changed the ABI compared
759 to stable/8 and which shared library version was not bumped.
760 Done as part of 9.0-RELEASE cycle.
763 During the merge of Capsicum features, the fget(9) KPI was modified.
764 This may require the rebuilding of out-of-tree device drivers --
765 issues have been reported specifically with the nVidia device driver.
766 __FreeBSD_version is bumped to 900041.
768 Also, there is a period between 20110811 and 20110814 where the
769 special devices /dev/{stdin,stdout,stderr} did not work correctly.
770 Building world from a kernel during that window may not work.
773 The packet filter (pf) code has been updated to OpenBSD 4.5.
774 You need to update userland tools to be in sync with kernel.
775 This update breaks backward compatibility with earlier pfsync(4)
776 versions. Care must be taken when updating redundant firewall setups.
779 The following sysctls and tunables are retired on x86 platforms:
781 machdep.hlt_logical_cpus
782 The following sysctl is retired:
783 machdep.hyperthreading_allowed
784 The sysctls were supposed to provide a way to dynamically offline and
785 online selected CPUs on x86 platforms, but the implementation has not
786 been reliable especially with SCHED_ULE scheduler.
787 machdep.hyperthreading_allowed tunable is still available to ignore
788 hyperthreading CPUs at OS level.
789 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
790 where X is an APIC ID of a CPU. Be advised, though, that disabling
791 CPUs in non-uniform fashion will result in non-uniform topology and
792 may lead to sub-optimal system performance with SCHED_ULE, which is
796 cpumask_t type is retired and cpuset_t is used in order to describe
800 Changes to ifconfig(8) for dynamic address family detection mandate
801 that you are running a kernel of 20110525 or later. Make sure to
802 follow the update procedure to boot a new kernel before installing
806 Support for sun4v architecture is officially dropped
809 Several KPI breaking changes have been committed to the mii(4) layer,
810 the PHY drivers and consequently some Ethernet drivers using mii(4).
811 This means that miibus.ko and the modules of the affected Ethernet
812 drivers need to be recompiled.
814 Note to kernel developers: Given that the OUI bit reversion problem
815 was fixed as part of these changes all mii(4) commits related to OUIs,
816 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
817 handling, no longer can be merged verbatim to stable/8 and previous
821 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
822 into their kernel configurations along with 'device pci'.
825 The default NFS client is now the new NFS client, so fstype "newnfs"
826 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
827 Although mounts via fstype "nfs" will usually work without userland
828 changes, it is recommended that the mount(8) and mount_nfs(8)
829 commands be rebuilt from sources and that a link to mount_nfs called
830 mount_oldnfs be created. The new client is compiled into the
831 kernel with "options NFSCL" and this is needed for diskless root
832 file systems. The GENERIC kernel configs have been changed to use
833 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
834 To use the regular/old client, you can "mount -t oldnfs ...". For
835 a diskless root file system, you must also include a line like:
837 vfs.root.mountfrom="oldnfs:"
839 in the boot/loader.conf on the root fs on the NFS server to make
840 a diskless root fs use the old client.
843 The GENERIC kernels for all architectures now default to the new
844 CAM-based ATA stack. It means that all legacy ATA drivers were
845 removed and replaced by respective CAM drivers. If you are using
846 ATA device names in /etc/fstab or other places, make sure to update
847 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
848 where 'Y's are the sequential numbers starting from zero for each type
849 in order of detection, unless configured otherwise with tunables,
850 see cam(4)). There will be symbolic links created in /dev/ to map
851 old adX devices to the respective adaY. They should provide basic
852 compatibility for file systems mounting in most cases, but they do
853 not support old user-level APIs and do not have respective providers
854 in GEOM. Consider using updated management tools with new device names.
856 It is possible to load devices ahci, ata, siis and mvs as modules,
857 but option ATA_CAM should remain in kernel configuration to make ata
858 module work as CAM driver supporting legacy ATA controllers. Device ata
859 still can be used in modular fashion (atacore + ...). Modules atadisk
860 and atapi* are not used and won't affect operation in ATA_CAM mode.
861 Note that to use CAM-based ATA kernel should include CAM devices
862 scbus, pass, da (or explicitly ada), cd and optionally others. All of
863 them are parts of the cam module.
865 ataraid(4) functionality is now supported by the RAID GEOM class.
866 To use it you can load geom_raid kernel module and use graid(8) tool
867 for management. Instead of /dev/arX device names, use /dev/raid/rX.
869 No kernel config options or code have been removed, so if a problem
870 arises, please report it and optionally revert to the old ATA stack.
871 In order to do it you can remove from the kernel config:
876 , and instead add back:
877 device atadisk # ATA disk drives
878 device ataraid # ATA RAID drives
879 device atapicd # ATAPI CDROM drives
880 device atapifd # ATAPI floppy drives
881 device atapist # ATAPI tape drives
884 The default NFS server has been changed to the new server, which
885 was referred to as the experimental server. If you need to switch
886 back to the old NFS server, you must now put the "-o" option on
887 both the mountd and nfsd commands. This can be done using the
888 mountd_flags and nfs_server_flags rc.conf variables until an
889 update to the rc scripts is committed, which is coming soon.
892 The GNU Objective-C runtime library (libobjc), and other Objective-C
893 related components have been removed from the base system. If you
894 require an Objective-C library, please use one of the available ports.
897 ath(4) has been split into bus- and device- modules. if_ath contains
898 the HAL, the TX rate control and the network device code. if_ath_pci
899 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
900 contains the AHB glue. Users need to load both if_ath_pci and if_ath
901 in order to use ath on everything else.
903 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
904 need to load if_ath and if_ath_pci for ath(4) operation.
907 As part of the replacement of sysinstall, the process of building
908 release media has changed significantly. For details, please re-read
909 release(7), which has been updated to reflect the new build process.
912 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
913 is the last available version under GPLv2. It brings a number of new
914 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
915 4.1 and SSE 4.2), better support for powerpc64, a number of new
916 directives, and lots of other small improvements. See the ChangeLog
917 file in contrib/binutils for the full details.
920 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
921 compliant, and will now use half of hash for authentication.
922 This will break interoperability with all stacks (including all
923 actual FreeBSD versions) who implement
924 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
926 The only workaround with such peers is to use another HMAC
927 algorithm for IPsec ("phase 2") authentication.
930 Remove the uio_yield prototype and symbol. This function has
931 been misnamed since it was introduced and should not be
932 globally exposed with this name. The equivalent functionality
933 is now available using kern_yield(curthread->td_user_pri).
934 The function remains undocumented.
937 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
938 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
939 for scalar sysctls is defined but disabled. Code that needs
940 UQUAD to pass the type checking that must compile on older
941 systems where the define is not present can check against
942 __FreeBSD_version >= 900030.
944 The system dialog(1) has been replaced with a new version previously
945 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
946 with the previous version, but the libdialog associated with it has
947 a largely incompatible API. As such, the original version of libdialog
948 will be kept temporarily as libodialog, until its base system consumers
949 are replaced or updated. Bump __FreeBSD_version to 900030.
952 If you are trying to run make universe on a -stable system, and you get
953 the following warning:
954 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
955 unknown. config(8) likely too old."
956 or something similar to it, then you must upgrade your -stable system
957 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
958 stable/8) or build the config from the latest stable/8 branch and
959 install it on your system.
961 Prior to this date, building a current universe on 8-stable system from
962 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
963 error in the first kernel build phase. A new config on those old
964 systems will fix that problem for older versions of -current.
967 The TCP stack has been modified to allow Khelp modules to interact with
968 it via helper hook points and store per-connection data in the TCP
969 control block. Bump __FreeBSD_version to 900029. User space tools that
970 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
974 Generic IEEE 802.3 annex 31B full duplex flow control support has been
975 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
976 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
977 to take advantage of it instead of using custom implementations. This
978 means that these drivers now no longer unconditionally advertise
979 support for flow control but only do so if flow control is a selected
980 media option. This was implemented in the generic support that way in
981 order to allow flow control to be switched on and off via ifconfig(8)
982 with the PHY specific default to typically off in order to protect
983 from unwanted effects. Consequently, if you used flow control with
984 one of the above mentioned drivers you now need to explicitly enable
986 ifconfig bge0 media auto mediaopt flowcontrol
988 Along with the above mentioned changes generic support for setting
989 1000baseT master mode also has been added and brgphy(4), ciphy(4),
990 e1000phy(4) as well as ip1000phy(4) have been converted to take
991 advantage of it. This means that these drivers now no longer take the
992 link0 parameter for selecting master mode but the master media option
993 has to be used instead, for example like in the following:
994 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
996 Selection of master mode now is also available with all other PHY
997 drivers supporting 1000baseT.
1000 The TCP stack has received a significant update to add support for
1001 modularised congestion control and generally improve the clarity of
1002 congestion control decisions. Bump __FreeBSD_version to 900025. User
1003 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1004 sockstat) need to be recompiled.
1007 The man(1) utility has been replaced by a new version that no longer
1008 uses /etc/manpath.config. Please consult man.conf(5) for how to
1009 migrate local entries to the new format.
1012 The copyright strings printed by login(1) and sshd(8) at the time of a
1013 new connection have been removed to follow other operating systems and
1017 A workaround for a fixed ld bug has been removed in kernel code,
1018 so make sure that your system ld is built from sources after
1019 revision 210245 from 2010-07-19 (r211583 if building head kernel
1020 on stable/8, r211584 for stable/7; both from 2010-08-21).
1021 A symptom of incorrect ld version is different addresses for
1022 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1025 The $ipv6_prefer variable in rc.conf(5) has been split into
1026 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1028 The $ip6addrctl_policy is a variable to choose a pre-defined
1029 address selection policy set by ip6addrctl(8). A value
1030 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1033 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1034 flag (see an entry of 20090926) is set on an interface with no
1035 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1036 security reason. If you want IPv6 link-local address on all
1037 interfaces by default, set this to "YES".
1039 The old ipv6_prefer="YES" is equivalent to
1040 ipv6_activate_all_interfaces="YES" and
1041 ip6addrctl_policy="ipv6_prefer".
1044 DTrace has grown support for userland tracing. Due to this, DTrace is
1045 now i386 and amd64 only.
1046 dtruss(1) is now installed by default on those systems and a new
1047 kernel module is needed for userland tracing: fasttrap.
1048 No changes to your kernel config file are necessary to enable
1049 userland tracing, but you might consider adding 'STRIP=' and
1050 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1051 to have informative userland stack traces in DTrace (ustack).
1054 The acpi_aiboost(4) driver has been removed in favor of the new
1055 aibs(4) driver. You should update your kernel configuration file.
1058 BSD grep has been imported to the base system and it is built by
1059 default. It is completely BSD licensed, highly GNU-compatible, uses
1060 less memory than its GNU counterpart and has a small codebase.
1061 However, it is slower than its GNU counterpart, which is mostly
1062 noticeable for larger searches, for smaller ones it is measurable
1063 but not significant. The reason is complex, the most important factor
1064 is that we lack a modern and efficient regex library and GNU
1065 overcomes this by optimizing the searches internally. Future work
1066 on improving the regex performance is planned, for the meantime,
1067 users that need better performance, can build GNU grep instead by
1068 setting the WITH_GNU_GREP knob.
1071 Due to the import of powerpc64 support, all existing powerpc kernel
1072 configuration files must be updated with a machine directive like this:
1073 machine powerpc powerpc
1075 In addition, an updated config(8) is required to build powerpc kernels
1079 A new version of ZFS (version 15) has been merged to -HEAD.
1080 This version uses a python library for the following subcommands:
1081 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1082 For full functionality of these commands the following port must
1083 be installed: sysutils/py-zfs
1086 'vm_page's are now hashed by physical address to an array of mutexes.
1087 Currently this is only used to serialize access to hold_count. Over
1088 time the page queue mutex will be peeled away. This changes the size
1089 of pmap on every architecture. And requires all callers of vm_page_hold
1090 and vm_page_unhold to be updated.
1093 WITH_CTF can now be specified in src.conf (not recommended, there
1094 are some problems with static executables), make.conf (would also
1095 affect ports which do not use GNU make and do not override the
1096 compile targets) or in the kernel config (via "makeoptions
1098 When WITH_CTF was specified there before this was silently ignored,
1099 so make sure that WITH_CTF is not used in places which could lead
1100 to unwanted behavior.
1103 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1104 to allow 32-bit compatibility on non-x86 platforms. All kernel
1105 configurations on amd64 and ia64 platforms using these options must
1106 be modified accordingly.
1109 The utmp user accounting database has been replaced with utmpx,
1110 the user accounting interface standardized by POSIX.
1111 Unfortunately the semantics of utmp and utmpx don't match,
1112 making it practically impossible to support both interfaces.
1113 The user accounting database is used by tools like finger(1),
1114 last(1), talk(1), w(1) and ac(8).
1116 All applications in the base system use utmpx. This means only
1117 local binaries (e.g. from the ports tree) may still use these
1118 utmp database files. These applications must be rebuilt to make
1121 After the system has been upgraded, it is safe to remove the old
1122 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1123 assuming their contents is of no importance anymore. Old wtmp
1124 databases can only be used by last(1) and ac(8) after they have
1125 been converted to the new format using wtmpcvt(1).
1128 Introduce the kernel thread "deadlock resolver" (which can be enabled
1129 via the DEADLKRES option, see NOTES for more details) and the
1130 sleepq_type() function for sleepqueues.
1133 The rc.firewall and rc.firewall6 were unified, and
1134 rc.firewall6 and rc.d/ip6fw were removed.
1135 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1136 variables are obsoleted. Instead, the following new rc
1137 variables are added to rc.d/ipfw:
1139 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1140 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1141 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1143 The meanings correspond to the relevant IPv4 variables.
1149 The default terminal emulation for syscons(4) has been changed
1150 from cons25 to xterm on all platforms except pc98. This means
1151 that the /etc/ttys file needs to be updated to ensure correct
1152 operation of applications on the console.
1154 The terminal emulation style can be toggled per window by using
1155 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1156 options can be used to change the compile-time default back to
1159 To prevent graphical artifacts, make sure the TERM environment
1160 variable is set to match the terminal emulation that is being
1161 performed by syscons(4).
1164 The layout of the structure ieee80211req_scan_result has changed.
1165 Applications that require wireless scan results (e.g. ifconfig(8))
1166 from net80211 need to be recompiled.
1168 Applications such as wpa_supplicant(8) may require a full world
1169 build without using NO_CLEAN in order to get synchronized with the
1173 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1174 There's one kernel module for each firmware. Adding "device iwnfw"
1175 to the kernel configuration file means including all three firmware
1176 images inside the kernel. If you want to include just the one for
1177 your wireless card, use the devices iwn4965fw, iwn5000fw or
1181 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1182 into rc.d/netif. The changes are the following:
1184 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1185 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1186 Note that both variables need the "inet6" keyword at the head.
1188 Do not set $ipv6_network_interfaces manually if you do not
1189 understand what you are doing. It is not needed in most cases.
1191 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1194 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1195 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1197 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1198 all configured interfaces have "inet6 accept_rtadv" in the
1199 $ifconfig_IF_ipv6. These are for backward compatibility.
1201 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1202 functionality of interfaces with no corresponding
1203 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1204 and the default address selection policy of ip6addrctl(8)
1205 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1206 Note that if you want to configure IPv6 functionality on the
1207 disabled interfaces after boot, first you need to clear the flag by
1208 using ifconfig(8) like:
1210 ifconfig em0 inet6 -ifdisabled
1212 If YES, the default address selection policy is set as
1215 The default value of $ipv6_prefer is NO.
1217 4. If your system need to receive Router Advertisement messages,
1218 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1219 scripts automatically invoke rtsol(8) when the interface becomes
1220 UP. The Router Advertisement messages are used for SLAAC
1221 (State-Less Address AutoConfiguration).
1224 802.11s D3.03 support was committed. This is incompatible with the
1225 previous code, which was based on D3.0.
1228 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1229 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1230 control whether accepting Router Advertisement messages or not.
1231 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1232 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1233 The ifconfig(8) utility now supports these flags.
1236 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1237 mount(8) and -a option for df(1) to see them.
1240 The old tunable hw.bus.devctl_disable has been superseded by
1241 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1242 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1246 Remove the option STOP_NMI. The default action is now to use NMI only
1247 for KDB via the newly introduced function stop_cpus_hard() and
1248 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1251 The stable/8 branch created in subversion. This corresponds to the
1252 RELENG_8 branch in CVS.
1255 Bump the shared library version numbers for all libraries that do not
1256 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1257 __FreeBSD_version to 800105.
1260 Due to changes in the implementation of virtual network stack support,
1261 all network-related kernel modules must be recompiled. As this change
1262 breaks the ABI, bump __FreeBSD_version to 800104.
1265 The TOE interface to the TCP syncache has been modified to remove
1266 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1267 The cxgb driver is the only TOE consumer affected by this change, and
1268 needs to be recompiled along with the kernel. As this change breaks
1269 the ABI, bump __FreeBSD_version to 800103.
1272 Padding has been added to struct tcpcb, sackhint and tcpstat in
1273 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1274 maintaining the ABI. However, this change breaks the ABI, so bump
1275 __FreeBSD_version to 800102. User space tools that rely on the size of
1276 any of these structs (e.g. sockstat) need to be recompiled.
1279 The NFS_LEGACYRPC option has been removed along with the old kernel
1280 RPC implementation that this option selected. Kernel configurations
1281 may need to be adjusted.
1284 The network interface device nodes at /dev/net/<interface> have been
1285 removed. All ioctl operations can be performed the normal way using
1286 routing sockets. The kqueue functionality can generally be replaced
1287 with routing sockets.
1290 The documentation from the FreeBSD Documentation Project (Handbook,
1291 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1292 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1295 The ABI of various structures related to the SYSV IPC API have been
1296 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1297 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1301 Layout of struct vnet has changed as routing related variables were
1302 moved to their own Vimage module. Modules need to be recompiled. Bump
1303 __FreeBSD_version to 800099.
1306 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1307 respectively. As long as no more than 16 groups per process are used,
1308 no changes should be visible. When more than 16 groups are used, old
1309 binaries may fail if they call getgroups() or getgrouplist() with
1310 statically sized storage. Recompiling will work around this, but
1311 applications should be modified to use dynamically allocated storage
1312 for group arrays as POSIX.1-2008 does not cap an implementation's
1313 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1315 NFS and portalfs mounts may also be affected as the list of groups is
1316 truncated to 16. Users of NFS who use more than 16 groups, should
1317 take care that negative group permissions are not used on the exported
1318 file systems as they will not be reliable unless a GSSAPI based
1319 authentication method is used.
1322 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1323 option compiles in the support for adaptive spinning for lockmgrs
1324 which want to enable it. The lockinit() function now accepts the flag
1325 LK_ADAPTIVE in order to make the lock object subject to adaptive
1326 spinning when both held in write and read mode.
1329 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1330 changed. User applications that use this ioctl need to be rebuilt.
1333 The layout of struct thread has changed. Kernel and modules need to
1337 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1338 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1341 window(1) has been removed from the base system. It can now be
1342 installed from ports. The port is called misc/window.
1345 The way we are storing and accessing `routing table' entries has
1346 changed. Programs reading the FIB, like netstat, need to be
1350 A new netisr implementation has been added for FreeBSD 8. Network
1351 file system modules, such as igmp, ipdivert, and others, should be
1353 Bump __FreeBSD_version to 800096.
1356 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1360 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1361 Bump __FreeBSD_version to 800094.
1364 Add mnt_xflag field to 'struct mount'. File system modules need to be
1366 Bump __FreeBSD_version to 800093.
1369 The compiling option ADAPTIVE_SX has been retired while it has been
1370 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1371 The KPI for sx_init_flags() changes as accepting flags:
1372 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1373 been introduced in order to handle the reversed logic.
1374 Bump __FreeBSD_version to 800092.
1377 Add support for hierarchical jails. Remove global securelevel.
1378 Bump __FreeBSD_version to 800091.
1381 The layout of struct vnet_net has changed, therefore modules
1383 Bump __FreeBSD_version to 800090.
1386 The newly imported zic(8) produces a new format in the output. Please
1387 run tzsetup(8) to install the newly created data to /etc/localtime.
1390 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1391 hw.usb.* and is now consistent again with previous releases.
1394 802.11 monitor mode support was revised and driver api's were changed.
1395 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1396 of DLT_IEEE802_11. No user-visible data structures were changed but
1397 applications that use DLT_IEEE802_11 may require changes.
1398 Bump __FreeBSD_version to 800088.
1401 The layout of the following structs has changed: sysctl_oid,
1402 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1403 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1404 panics may be experienced. World rebuild is required for
1405 correctly checking networking state from userland.
1406 Bump __FreeBSD_version to 800085.
1409 MLDv2 and Source-Specific Multicast (SSM) have been merged
1410 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1411 The implementation of SSM within FreeBSD's IPv6 stack closely
1412 follows the IPv4 implementation.
1414 For kernel developers:
1416 * The most important changes are that the ip6_output() and
1417 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1418 and this lock has been downgraded to a non-recursive mutex.
1420 * As with the changes to the IPv4 stack to support SSM, filtering
1421 of inbound multicast traffic must now be performed by transport
1422 protocols within the IPv6 stack. This does not apply to TCP and
1423 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1425 * The KPIs used by IPv6 multicast are similar to those used by
1426 the IPv4 stack, with the following differences:
1427 * im6o_mc_filter() is analogous to imo_multicast_filter().
1428 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1429 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1430 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1431 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1432 for MLDv1 have an additional 'timer' argument which is used to
1433 jitter the initial membership report for the solicited-node
1434 multicast membership on-link.
1435 * This is not strictly needed for MLDv2, which already jitters
1436 its report transmissions. However, the 'timer' argument is
1437 preserved in case MLDv1 is active on the interface.
1439 * The KAME linked-list based IPv6 membership implementation has
1440 been refactored to use a vector similar to that used by the IPv4
1442 Code which maintains a list of its own multicast memberships
1443 internally, e.g. carp, has been updated to reflect the new
1446 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1447 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1448 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1449 implementation constraint which needs to be addressed in HEAD.
1451 For application developers:
1453 * The changes are broadly similar to those made for the IPv4
1456 * The use of IPv4 and IPv6 multicast socket options on the same
1457 socket, using mapped addresses, HAS NOT been tested or supported.
1459 * There are a number of issues with the implementation of various
1460 IPv6 multicast APIs which need to be resolved in the API surface
1461 before the implementation is fully compatible with KAME userland
1462 use, and these are mostly to do with interface index treatment.
1464 * The literature available discusses the use of either the delta / ASM
1465 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1466 using setsourcefilter(3)/getsourcefilter(3). For more information
1467 please refer to RFC 3768, 'Socket Interface Extensions for
1468 Multicast Source Filters'.
1470 * Applications which use the published RFC 3678 APIs should be fine.
1472 For systems administrators:
1474 * The mtest(8) utility has been refactored to support IPv6, in
1475 addition to IPv4. Interface addresses are no longer accepted
1476 as arguments, their names must be used instead. The utility
1477 will map the interface name to its first IPv4 address as
1478 returned by getifaddrs(3).
1480 * The ifmcstat(8) utility has also been updated to print the MLDv2
1481 endpoint state and source filter lists via sysctl(3).
1483 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1484 loopback of IPv6 multicast datagrams by default; it defaults to 1
1485 to preserve the existing behaviour. Disabling multicast loopback is
1486 recommended for optimal system performance.
1488 * The IPv6 MROUTING code has been changed to examine this sysctl
1489 instead of attempting to perform a group lookup before looping
1490 back forwarded datagrams.
1492 Bump __FreeBSD_version to 800084.
1495 Implement low-level Bluetooth HCI API.
1496 Bump __FreeBSD_version to 800083.
1499 The layout of struct malloc_type, used by modules to register new
1500 memory allocation types, has changed. Most modules will need to
1501 be rebuilt or panics may be experienced.
1502 Bump __FreeBSD_version to 800081.
1505 Anticipate overflowing inp_flags - add inp_flags2.
1506 This changes most offsets in inpcb, so checking v4 connection
1507 state will require a world rebuild.
1508 Bump __FreeBSD_version to 800080.
1511 Add an llentry to struct route and struct route_in6. Modules
1512 embedding a struct route will need to be recompiled.
1513 Bump __FreeBSD_version to 800079.
1516 The size of rt_metrics_lite and by extension rtentry has changed.
1517 Networking administration apps will need to be recompiled.
1518 The route command now supports show as an alias for get, weighting
1519 of routes, sticky and nostick flags to alter the behavior of stateful
1521 Bump __FreeBSD_version to 800078.
1524 Do not use Giant for kbdmux(4) locking. This is wrong and
1525 apparently causing more problems than it solves. This will
1526 re-open the issue where interrupt handlers may race with
1527 kbdmux(4) in polling mode. Typical symptoms include (but
1528 not limited to) duplicated and/or missing characters when
1529 low level console functions (such as gets) are used while
1530 interrupts are enabled (for example geli password prompt,
1531 mountroot prompt etc.). Disabling kbdmux(4) may help.
1534 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1535 kernel modules referencing any of the above need to be recompiled.
1536 Bump __FreeBSD_version to 800075.
1539 GEOM_PART has become the default partition slicer for storage devices,
1540 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1541 introduces some changes:
1543 MSDOS/EBR: the devices created from MSDOS extended partition entries
1544 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1545 to devices with offset-based names. fstabs may need to be modified.
1547 BSD: the "geometry does not match label" warning is harmless in most
1548 cases but it points to problems in file system misalignment with
1549 disk geometry. The "c" partition is now implicit, covers the whole
1550 top-level drive and cannot be (mis)used by users.
1552 General: Kernel dumps are now not allowed to be written to devices
1553 whose partition types indicate they are meant to be used for file
1554 systems (or, in case of MSDOS partitions, as something else than
1557 Most of these changes date approximately from 200812.
1560 The uscanner(4) driver has been removed from the kernel. This follows
1561 Linux removing theirs in 2.6 and making libusb the default interface
1562 (supported by sane).
1565 The multicast forwarding code has been cleaned up. netstat(1)
1566 only relies on KVM now for printing bandwidth upcall meters.
1567 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1568 ip6_mroute_mod respectively. The config(5) options for statically
1569 compiling this code remain the same, i.e. 'options MROUTING'.
1572 Support for the IFF_NEEDSGIANT network interface flag has been
1573 removed, which means that non-MPSAFE network device drivers are no
1574 longer supported. In particular, if_ar, if_sr, and network device
1575 drivers from the old (legacy) USB stack can no longer be built or
1579 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1580 a bunch of new language catalog files have also been added.
1581 This means that some common libc messages are now localized and
1582 they depend on the LC_MESSAGES environmental variable.
1585 The k8temp(4) driver has been renamed to amdtemp(4) since
1586 support for Family 10 and Family 11 CPU families was added.
1589 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1590 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1592 For kernel developers, the most important changes are that the
1593 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1594 and this lock has been downgraded to a non-recursive mutex.
1596 Transport protocols (UDP, Raw IP) are now responsible for filtering
1597 inbound multicast traffic according to group membership and source
1598 filters. The imo_multicast_filter() KPI exists for this purpose.
1599 Transports which do not use multicast (SCTP, TCP) already reject
1600 multicast by default. Forwarding and receive performance may improve
1601 as a mutex acquisition is no longer needed in the ip_input()
1602 low-level input path. in_addmulti() and in_delmulti() are shimmed
1603 to new KPIs which exist to support SSM in-kernel.
1605 For application developers, it is recommended that loopback of
1606 multicast datagrams be disabled for best performance, as this
1607 will still cause the lock to be taken for each looped-back
1608 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1609 be tuned to 0 to disable loopback by default; it defaults to 1
1610 to preserve the existing behaviour.
1612 For systems administrators, to obtain best performance with
1613 multicast reception and multiple groups, it is always recommended
1614 that a card with a suitably precise hash filter is used. Hash
1615 collisions will still result in the lock being taken within the
1616 transport protocol input path to check group membership.
1618 If deploying FreeBSD in an environment with IGMP snooping switches,
1619 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1620 enabled; this forces 224.0.0.0/24 group membership to be announced
1623 The size of 'struct igmpstat' has changed; netstat needs to be
1624 recompiled to reflect this.
1625 Bump __FreeBSD_version to 800070.
1628 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1629 updated to use it. This requires a buildworld/installworld in order to
1630 update the library and dependencies (usbconfig, etc). Its advisable to
1631 rebuild all ports which uses libusb. More specific directions are given
1632 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1633 libusb are no longer required and can be removed.
1636 A workaround is committed to allow the creation of System V shared
1637 memory segment of size > 2 GB on the 64-bit architectures.
1638 Due to a limitation of the existing ABI, the shm_segsz member
1639 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1640 wrong for large segments. Note that limits must be explicitly
1641 raised to allow such segments to be created.
1644 The layout of struct ifnet has changed, requiring a rebuild of all
1645 network device driver modules.
1648 The /dev handling for the new USB stack has changed, a
1649 buildworld/installworld is required for libusb20.
1652 The new USB2 stack has now been permanently moved in and all kernel and
1653 module names reverted to their previous values (eg, usb, ehci, ohci,
1654 ums, ...). The old usb stack can be compiled in by prefixing the name
1655 with the letter 'o', the old usb modules have been removed.
1656 Updating entry 20090216 for xorg and 20090215 for libmap may still
1660 The rc.conf(5) option if_up_delay has been renamed to
1661 defaultroute_delay to better reflect its purpose. If you have
1662 customized this setting in /etc/rc.conf you need to update it to
1666 xorg 7.4 wants to configure its input devices via hald which does not
1667 yet work with USB2. If the keyboard/mouse does not work in xorg then
1669 Option "AllowEmptyInput" "off"
1670 to your ServerLayout section. This will cause X to use the configured
1671 kbd and mouse sections from your xorg.conf.
1674 The GENERIC kernels for all architectures now default to the new USB2
1675 stack. No kernel config options or code have been removed so if a
1676 problem arises please report it and optionally revert to the old USB
1677 stack. If you are loading USB kernel modules or have a custom kernel
1678 that includes GENERIC then ensure that usb names are also changed over,
1679 eg uftdi -> usb2_serial_ftdi.
1681 Older programs linked against the ports libusb 0.1 need to be
1682 redirected to the new stack's libusb20. /etc/libmap.conf can
1684 # Map old usb library to new one for usb2 stack
1685 libusb-0.1.so.8 libusb20.so.1
1688 All USB ethernet devices now attach as interfaces under the name ueN
1689 (eg. ue0). This is to provide a predictable name as vendors often
1690 change usb chipsets in a product without notice.
1693 The ichsmb(4) driver has been changed to require SMBus slave
1694 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1695 All of the other SMBus controller drivers require left-justified
1696 slave addresses, so this change makes all the drivers provide the
1700 INET6 statistics (struct ip6stat) was updated.
1701 netstat(1) needs to be recompiled.
1704 NTFS has been removed from GENERIC kernel on amd64 to match
1705 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1706 will load ntfs.ko module automatically when NTFS support is
1707 actually needed, unless ntfs.ko is not installed or security
1708 level prohibits loading kernel modules. If either is the case,
1709 "options NTFS" has to be added into kernel config.
1712 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1713 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1714 800061. User space tools that rely on the size of struct tcpcb in
1715 tcp_var.h (e.g. sockstat) need to be recompiled.
1718 ng_tty(4) module updated to match the new TTY subsystem.
1719 Due to API change, user-level applications must be updated.
1720 New API support added to mpd5 CVS and expected to be present
1721 in next mpd5.3 release.
1724 With __FreeBSD_version 800060 the makefs tool is part of
1725 the base system (it was a port).
1728 The afdata and ifnet locks have been changed from mutexes to
1729 rwlocks, network modules will need to be re-compiled.
1732 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1733 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1734 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1735 architecture and 40 bytes on 64-bit architecture. The userland
1736 applications "arp" and "ndp" have been updated accordingly.
1737 The output from "netstat -r" shows only routing entries and
1738 none of the L2 information.
1741 __FreeBSD_version 800057 marks the switchover from the
1742 binary ath hal to source code. Users must add the line:
1744 options AH_SUPPORT_AR5416
1746 to their kernel config files when specifying:
1750 The ath_hal module no longer exists; the code is now compiled
1751 together with the driver in the ath module. It is now
1752 possible to tailor chip support (i.e. reduce the set of chips
1753 and thereby the code size); consult ath_hal(4) for details.
1756 __FreeBSD_version 800054 adds memory barriers to
1757 <machine/atomic.h>, new interfaces to ifnet to facilitate
1758 multiple hardware transmit queues for cards that support
1759 them, and a lock-less ring-buffer implementation to
1760 enable drivers to more efficiently manage queueing of
1764 A new version of ZFS (version 13) has been merged to -HEAD.
1765 This version has zpool attribute "listsnapshots" off by
1766 default, which means "zfs list" does not show snapshots,
1767 and is the same as Solaris behavior.
1770 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1773 The uhci, ohci, ehci and slhci USB Host controller drivers have
1774 been put into separate modules. If you load the usb module
1775 separately through loader.conf you will need to load the
1776 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1777 controller add the following to loader.conf:
1783 The ABI used by the PMC toolset has changed. Please keep
1784 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1788 atapci kernel module now includes only generic PCI ATA
1789 driver. AHCI driver moved to ataahci kernel module.
1790 All vendor-specific code moved into separate kernel modules:
1791 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1792 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1793 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1794 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1797 The TTY subsystem of the kernel has been replaced by a new
1798 implementation, which provides better scalability and an
1799 improved driver model. Most common drivers have been migrated to
1800 the new TTY subsystem, while others have not. The following
1801 drivers have not yet been ported to the new TTY layer:
1804 cy, digi, rc, rp, sio
1810 ng_h4, ng_tty, ppp, sl, snp
1812 Adding these drivers to your kernel configuration file shall
1813 cause compilation to fail.
1816 ntpd has been upgraded to 4.2.4p5.
1819 OpenSSH has been upgraded to 5.1p1.
1821 For many years, FreeBSD's version of OpenSSH preferred DSA
1822 over RSA for host and user authentication keys. With this
1823 upgrade, we've switched to the vendor's default of RSA over
1824 DSA. This may cause upgraded clients to warn about unknown
1825 host keys even for previously known hosts. Users should
1826 follow the usual procedure for verifying host keys before
1827 accepting the RSA key.
1829 This can be circumvented by setting the "HostKeyAlgorithms"
1830 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1833 Please note that the sequence of keys offered for
1834 authentication has been changed as well. You may want to
1835 specify IdentityFile in a different order to revert this
1839 The sio(4) driver has been removed from the i386 and amd64
1840 kernel configuration files. This means uart(4) is now the
1841 default serial port driver on those platforms as well.
1843 To prevent collisions with the sio(4) driver, the uart(4) driver
1844 uses different names for its device nodes. This means the
1845 onboard serial port will now most likely be called "ttyu0"
1846 instead of "ttyd0". You may need to reconfigure applications to
1847 use the new device names.
1849 When using the serial port as a boot console, be sure to update
1850 /boot/device.hints and /etc/ttys before booting the new kernel.
1851 If you forget to do so, you can still manually specify the hints
1852 at the loader prompt:
1854 set hint.uart.0.at="isa"
1855 set hint.uart.0.port="0x3F8"
1856 set hint.uart.0.flags="0x10"
1857 set hint.uart.0.irq="4"
1861 The gpt(8) utility has been removed. Use gpart(8) to partition
1865 The version that Linuxulator emulates was changed from 2.4.2
1866 to 2.6.16. If you experience any problems with Linux binaries
1867 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1868 if it fixes the problem contact emulation mailing list.
1871 ISDN4BSD (I4B) was removed from the src tree. You may need to
1872 update a your kernel configuration and remove relevant entries.
1875 I have checked in code to support multiple routing tables.
1876 See the man pages setfib(1) and setfib(2).
1877 This is a hopefully backwards compatible version,
1878 but to make use of it you need to compile your kernel
1879 with options ROUTETABLES=2 (or more up to 16).
1882 The 802.11 wireless support was redone to enable multi-bss
1883 operation on devices that are capable. The underlying device
1884 is no longer used directly but instead wlanX devices are
1885 cloned with ifconfig. This requires changes to rc.conf files.
1886 For example, change:
1887 ifconfig_ath0="WPA DHCP"
1890 ifconfig_wlan0="WPA DHCP"
1891 see rc.conf(5) for more details. In addition, mergemaster of
1892 /etc/rc.d is highly recommended. Simultaneous update of userland
1893 and kernel wouldn't hurt either.
1895 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1896 modules were merged into the base wlan module. All references
1897 to these modules (e.g. in kernel config files) must be removed.
1900 psm(4) has gained write(2) support in native operation level.
1901 Arbitrary commands can be written to /dev/psm%d and status can
1902 be read back from it. Therefore, an application is responsible
1903 for status validation and error recovery. It is a no-op in
1904 other operation levels.
1907 Support for KSE threading has been removed from the kernel. To
1908 run legacy applications linked against KSE libmap.conf may
1909 be used. The following libmap.conf may be used to ensure
1910 compatibility with any prior release:
1912 libpthread.so.1 libthr.so.1
1913 libpthread.so.2 libthr.so.2
1914 libkse.so.3 libthr.so.3
1917 The layout of struct vmspace has changed. This affects libkvm
1918 and any executables that link against libkvm and use the
1919 kvm_getprocs() function. In particular, but not exclusively,
1920 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1921 The effects are minimal, but it's advisable to upgrade world
1925 The latest em driver no longer has support in it for the
1926 82575 adapter, this is now moved to the igb driver. The
1927 split was done to make new features that are incompatible
1928 with older hardware easier to do.
1931 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1932 likewise the kernel option is now GEOM_LINUX_LVM.
1935 The default NFS mount mode has changed from UDP to TCP for
1936 increased reliability. If you rely on (insecurely) NFS
1937 mounting across a firewall you may need to update your
1941 Belatedly note the addition of m_collapse for compacting
1945 The fts(3) structures have been changed to use adequate
1946 integer types for their members and so to be able to cope
1947 with huge file trees. The old fts(3) ABI is preserved
1948 through symbol versioning in libc, so third-party binaries
1949 using fts(3) should still work, although they will not take
1950 advantage of the extended types. At the same time, some
1951 third-party software might fail to build after this change
1952 due to unportable assumptions made in its source code about
1953 fts(3) structure members. Such software should be fixed
1954 by its vendor or, in the worst case, in the ports tree.
1955 FreeBSD_version 800015 marks this change for the unlikely
1956 case that a portable fix is impossible.
1959 To upgrade to -current after this date, you must be running
1960 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1961 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1964 The ADAPTIVE_GIANT kernel option has been retired because its
1965 functionality is the default now.
1968 The AT keyboard emulation of sunkbd(4) has been turned on
1969 by default. In order to make the special symbols of the Sun
1970 keyboards driven by sunkbd(4) work under X these now have
1971 to be configured the same way as Sun USB keyboards driven
1972 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1974 Option "XkbLayout" "us"
1975 Option "XkbRules" "xorg"
1976 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1979 It has been decided that it is desirable to provide ABI
1980 backwards compatibility to the FreeBSD 4/5/6 versions of the
1981 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1982 broken with the introduction of PCI domain support (see the
1983 20070930 entry). Unfortunately, this required the ABI of
1984 PCIOCGETCONF to be broken again in order to be able to
1985 provide backwards compatibility to the old version of that
1986 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1987 again. As for prominent ports this affects neither pciutils
1988 nor xorg-server this time, the hal port needs to be rebuilt
1992 The misnamed kthread_create() and friends have been renamed
1993 to kproc_create() etc. Many of the callers already
1994 used kproc_start()..
1995 I will return kthread_create() and friends in a while
1996 with implementations that actually create threads, not procs.
1997 Renaming corresponds with version 800002.
2006 Avoid using make -j when upgrading. While generally safe, there are
2007 sometimes problems using -j to upgrade. If your upgrade fails with
2008 -j, please try again without -j. From time to time in the past there
2009 have been problems using -j with buildworld and/or installworld. This
2010 is especially true when upgrading between "distant" versions (eg one
2011 that cross a major release boundary or several minor releases, or when
2012 several months have passed on the -current branch).
2014 Sometimes, obscure build problems are the result of environment
2015 poisoning. This can happen because the make utility reads its
2016 environment when searching for values for global variables. To run
2017 your build attempts in an "environmental clean room", prefix all make
2018 commands with 'env -i '. See the env(1) manual page for more details.
2020 When upgrading from one major version to another it is generally best
2021 to upgrade to the latest code in the currently installed branch first,
2022 then do an upgrade to the new branch. This is the best-tested upgrade
2023 path, and has the highest probability of being successful. Please try
2024 this approach before reporting problems with a major version upgrade.
2026 When upgrading a live system, having a root shell around before
2027 installing anything can help undo problems. Not having a root shell
2028 around can lead to problems if pam has changed too much from your
2029 starting point to allow continued authentication after the upgrade.
2033 When upgrading the boot ZFS pool to a new version, always follow
2036 1.) recompile and reinstall the ZFS boot loader and boot block
2037 (this is part of "make buildworld" and "make installworld")
2039 2.) update the ZFS boot block on your boot drive
2041 The following example updates the ZFS boot block on the first
2042 partition (freebsd-boot) of a GPT partitioned drive ad0:
2043 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2045 Non-boot pools do not need these updates.
2049 If you are updating from a prior version of FreeBSD (even one just
2050 a few days old), you should follow this procedure. It is the most
2051 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2053 make kernel-toolchain
2054 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2055 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2057 To test a kernel once
2058 ---------------------
2059 If you just want to boot a kernel once (because you are not sure
2060 if it works, or if you want to boot a known bad kernel to provide
2061 debugging information) run
2062 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2063 nextboot -k testkernel
2065 To just build a kernel when you know that it won't mess you up
2066 --------------------------------------------------------------
2067 This assumes you are already running a CURRENT system. Replace
2068 ${arch} with the architecture of your machine (e.g. "i386",
2069 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2071 cd src/sys/${arch}/conf
2072 config KERNEL_NAME_HERE
2073 cd ../compile/KERNEL_NAME_HERE
2078 If this fails, go to the "To build a kernel" section.
2080 To rebuild everything and install it on the current system.
2081 -----------------------------------------------------------
2082 # Note: sometimes if you are running current you gotta do more than
2083 # is listed here if you are upgrading from a really old current.
2085 <make sure you have good level 0 dumps>
2087 make kernel KERNCONF=YOUR_KERNEL_HERE
2089 <reboot in single user> [3]
2096 To cross-install current onto a separate partition
2097 --------------------------------------------------
2098 # In this approach we use a separate partition to hold
2099 # current's root, 'usr', and 'var' directories. A partition
2100 # holding "/", "/usr" and "/var" should be about 2GB in
2103 <make sure you have good level 0 dumps>
2106 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2107 <maybe newfs current's root partition>
2108 <mount current's root partition on directory ${CURRENT_ROOT}>
2109 make installworld DESTDIR=${CURRENT_ROOT}
2110 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2111 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2112 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2113 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2114 <reboot into current>
2115 <do a "native" rebuild/install as described in the previous section>
2116 <maybe install compatibility libraries from ports/misc/compat*>
2120 To upgrade in-place from stable to current
2121 ----------------------------------------------
2122 <make sure you have good level 0 dumps>
2124 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2126 <reboot in single user> [3]
2133 Make sure that you've read the UPDATING file to understand the
2134 tweaks to various things you need. At this point in the life
2135 cycle of current, things change often and you are on your own
2136 to cope. The defaults can also change, so please read ALL of
2137 the UPDATING entries.
2139 Also, if you are tracking -current, you must be subscribed to
2140 freebsd-current@freebsd.org. Make sure that before you update
2141 your sources that you have read and understood all the recent
2142 messages there. If in doubt, please track -stable which has
2143 much fewer pitfalls.
2145 [1] If you have third party modules, such as vmware, you
2146 should disable them at this point so they don't crash your
2149 [3] From the bootblocks, boot -s, and then do
2154 adjkerntz -i # if CMOS is wall time
2155 Also, when doing a major release upgrade, it is required that
2156 you boot into single user mode to do the installworld.
2158 [4] Note: This step is non-optional. Failure to do this step
2159 can result in a significant reduction in the functionality of the
2160 system. Attempting to do it by hand is not recommended and those
2161 that pursue this avenue should read this file carefully, as well
2162 as the archives of freebsd-current and freebsd-hackers mailing lists
2163 for potential gotchas. The -U option is also useful to consider.
2164 See mergemaster(8) for more information.
2166 [5] Usually this step is a noop. However, from time to time
2167 you may need to do this if you get unknown user in the following
2168 step. It never hurts to do it all the time. You may need to
2169 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2170 install) after the buildworld before this step if you last updated
2171 from current before 20130425 or from -stable before 20130430.
2173 [6] This only deletes old files and directories. Old libraries
2174 can be deleted by "make delete-old-libs", but you have to make
2175 sure that no program is using those libraries anymore.
2177 [8] In order to have a kernel that can run the 4.x binaries needed to
2178 do an installworld, you must include the COMPAT_FREEBSD4 option in
2179 your kernel. Failure to do so may leave you with a system that is
2180 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2181 required to run the 5.x binaries on more recent kernels. And so on
2182 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2184 Make sure that you merge any new devices from GENERIC since the
2185 last time you updated your kernel config file.
2187 [9] When checking out sources, you must include the -P flag to have
2188 cvs prune empty directories.
2190 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2191 "?=" instead of the "=" assignment operator, so that buildworld can
2192 override the CPUTYPE if it needs to.
2194 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2195 not on the command line, or in /etc/make.conf. buildworld will
2196 warn if it is improperly defined.
2199 This file contains a list, in reverse chronological order, of major
2200 breakages in tracking -current. It is not guaranteed to be a complete
2201 list of such breakages, and only contains entries since October 10, 2007.
2202 If you need to see UPDATING entries from before that date, you will need
2203 to fetch an UPDATING file from an older FreeBSD release.
2205 Copyright information:
2207 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2209 Redistribution, publication, translation and use, with or without
2210 modification, in full or in part, in any form or format of this
2211 document are permitted without further permission from the author.
2213 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2214 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2215 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2216 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2217 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2218 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2219 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2220 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2221 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2222 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2223 POSSIBILITY OF SUCH DAMAGE.
2225 Contact Warner Losh if you have any questions about your use of