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