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