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 head, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The YES_HESIOD knob has been removed. It has been obsolete for
36 a decade. Please move to using WITH_HESIOD instead or your builds
37 will silently lack HESIOD.
40 The uart(4) driver has been changed with respect to its handling
41 of the low-level console. Previously the uart(4) driver prevented
42 any process from changing the baudrate or the CLOCAL and HUPCL
43 control flags. By removing the restrictions, operators can make
44 changes to the serial console port without having to reboot.
45 However, when getty(8) is started on the serial device that is
46 associated with the low-level console, a misconfigured terminal
47 line in /etc/ttys will now have a real impact.
48 Before upgrading the kernel, make sure that /etc/ttys has the
49 serial console device configured as 3wire without baudrate to
50 preserve the previous behaviour. E.g:
51 ttyu0 "/usr/libexec/getty 3wire" vt100 on secure
54 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
55 to improve performance. To re-enable it, if needed, run rpcbind
56 with command line option -W.
59 Switched back to the GPL dtc compiler due to updates in the upstream
60 dts files not being supported by the BSDL dtc compiler. You will need
61 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
62 may result while building dtb files during a kernel build if you fail
63 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
66 Clang and llvm have been upgraded to 3.4 release.
69 The nve(4) driver has been removed. Please use the nfe(4) driver
70 for NVIDIA nForce MCP Ethernet adapters instead.
73 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
74 This could cause certain C++ applications using shared libraries built
75 against the previous version of libc++ to crash. The incompatibility
76 has now been fixed, but any C++ applications or shared libraries built
77 between r261283 and r261801 should be recompiled.
80 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
81 capability mode support. Please note that enabling the feature in
82 kernel is still highly recommended.
85 OpenSSH is now built with sandbox support, and will use sandbox as
86 the default privilege separation method. This requires Capsicum
87 capability mode support in kernel.
90 The libelf and libdwarf libraries have been updated to newer
91 versions from upstream. Shared library version numbers for
92 these two libraries were bumped. Any ports or binaries
93 requiring these two libraries should be recompiled.
94 __FreeBSD_version is bumped to 1100006.
97 If a Makefile in a tests/ directory was auto-generating a Kyuafile
98 instead of providing an explicit one, this would prevent such
99 Makefile from providing its own Kyuafile in the future during
100 NO_CLEAN builds. This has been fixed in the Makefiles but manual
101 intervention is needed to clean an objdir if you use NO_CLEAN:
102 # find /usr/obj -name Kyuafile | xargs rm -f
105 The behavior of gss_pseudo_random() for the krb5 mechanism
106 has changed, for applications requesting a longer random string
107 than produced by the underlying enctype's pseudo-random() function.
108 In particular, the random string produced from a session key of
109 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
110 be different at the 17th octet and later, after this change.
111 The counter used in the PRF+ construction is now encoded as a
112 big-endian integer in accordance with RFC 4402.
113 __FreeBSD_version is bumped to 1100004.
116 The WITHOUT_ATF build knob has been removed and its functionality
117 has been subsumed into the more generic WITHOUT_TESTS. If you were
118 using the former to disable the build of the ATF libraries, you
119 should change your settings to use the latter.
122 The default version of mtree is nmtree which is obtained from
123 NetBSD. The output is generally the same, but may vary
124 slightly. If you found you need identical output adding
125 "-F freebsd9" to the command line should do the trick. For the
126 time being, the old mtree is available as fmtree.
129 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
130 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
131 1.1.4_8 and verify bsdyml not linked in, before running "make
133 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
135 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
138 The rc.d/jail script has been updated to support jail(8)
139 configuration file. The "jail_<jname>_*" rc.conf(5) variables
140 for per-jail configuration are automatically converted to
141 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
142 This is transparently backward compatible. See below about some
143 incompatibilities and rc.conf(5) manual page for more details.
145 These variables are now deprecated in favor of jail(8) configuration
146 file. One can use "rc.d/jail config <jname>" command to generate
147 a jail(8) configuration file in /var/run/jail.<jname>.conf without
148 running the jail(8) utility. The default pathname of the
149 configuration file is /etc/jail.conf and can be specified by
150 using $jail_conf or $jail_<jname>_conf variables.
152 Please note that jail_devfs_ruleset accepts an integer at
153 this moment. Please consider to rewrite the ruleset name
157 BIND has been removed from the base system. If all you need
158 is a local resolver, simply enable and start the local_unbound
159 service instead. Otherwise, several versions of BIND are
160 available in the ports tree. The dns/bind99 port is one example.
162 With this change, nslookup(1) and dig(1) are no longer in the base
163 system. Users should instead use host(1) and drill(1) which are
164 in the base system. Alternatively, nslookup and dig can
165 be obtained by installing the dns/bind-tools port.
168 With the addition of unbound(8), a new unbound user is now
169 required during installworld. "mergemaster -p" can be used to
170 add the user prior to installworld, as documented in the handbook.
173 OpenSSH is now built with DNSSEC support, and will by default
174 silently trust signed SSHFP records. This can be controlled with
175 the VerifyHostKeyDNS client configuration setting. DNSSEC support
176 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
179 The GNU Compiler Collection and C++ standard library (libstdc++)
180 are no longer built by default on platforms where clang is the system
181 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
185 The PROCDESC kernel option is now part of the GENERIC kernel
186 configuration and is required for the rwhod(8) to work.
187 If you are using custom kernel configuration, you should include
191 The API and ABI related to the Capsicum framework was modified
192 in backward incompatible way. The userland libraries and programs
193 have to be recompiled to work with the new kernel. This includes the
194 following libraries and programs, but the whole buildworld is
195 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
196 kdump, procstat, rwho, rwhod, uniq.
199 AES-NI intrinsic support has been added to gcc. The AES-NI module
200 has been updated to use this support. A new gcc is required to build
201 the aesni module on both i386 and amd64.
204 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
205 Thus "device padlock_rng" and "device rdrand_rng" should be
206 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
209 WITH_ICONV has been split into two feature sets. WITH_ICONV now
210 enables just the iconv* functionality and is now on by default.
211 WITH_LIBICONV_COMPAT enables the libiconv api and link time
212 compatability. Set WITHOUT_ICONV to build the old way.
213 If you have been using WITH_ICONV before, you will very likely
214 need to turn on WITH_LIBICONV_COMPAT.
217 INVARIANTS option now enables DEBUG for code with OpenSolaris and
218 Illumos origin, including ZFS. If you have INVARIANTS in your
219 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
221 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
222 locks if WITNESS option was set. Because that generated a lot of
223 witness(9) reports and all of them were believed to be false
224 positives, this is no longer done. New option OPENSOLARIS_WITNESS
225 can be used to achieve the previous behavior.
228 Timer values in IPv6 data structures now use time_uptime instead
229 of time_second. Although this is not a user-visible functional
230 change, userland utilities which directly use them---ndp(8),
231 rtadvd(8), and rtsold(8) in the base system---need to be updated
235 find -delete can now delete the pathnames given as arguments,
236 instead of only files found below them or if the pathname did
237 not contain any slashes. Formerly, the following error message
240 find: -delete: <path>: relative path potentially not safe
242 Deleting the pathnames given as arguments can be prevented
243 without error messages using -mindepth 1 or by changing
244 directory and passing "." as argument to find. This works in the
245 old as well as the new version of find.
248 Behavior of devfs rules path matching has been changed.
249 Pattern is now always matched against fully qualified devfs
250 path and slash characters must be explicitly matched by
251 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
252 subdirectories must be reviewed.
255 The default ARM ABI has changed to the ARM EABI. The old ABI is
256 incompatible with the ARM EABI and all programs and modules will
257 need to be rebuilt to work with a new kernel.
259 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
261 NOTE: Support for the old ABI will be removed in the future and
262 users are advised to upgrade.
265 pkg_install has been disconnected from the build if you really need it
266 you should add WITH_PKGTOOLS in your src.conf(5).
269 Most of network statistics structures were changed to be able
270 keep 64-bits counters. Thus all tools, that work with networking
271 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
274 Fix targets that run multiple make's to use && rather than ;
275 so that subsequent steps depend on success of previous.
277 NOTE: if building 'universe' with -j* on stable/8 or stable/9
278 it would be better to start the build using bmake, to avoid
279 overloading the machine.
282 Fix a bug that allowed a tracing process (e.g. gdb) to write
283 to a memory-mapped file in the traced process's address space
284 even if neither the traced process nor the tracing process had
285 write access to that file.
288 CVS has been removed from the base system. An exact copy
289 of the code is available from the devel/cvs port.
292 Some people report the following error after the switch to bmake:
294 make: illegal option -- J
295 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
297 *** [buildworld] Error code 2
299 this likely due to an old instance of make in
300 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
301 which src/Makefile will use that blindly, if it exists, so if
302 you see the above error:
304 rm -rf `make -V MAKEPATH`
309 Use bmake by default.
310 Whereas before one could choose to build with bmake via
311 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
312 make. The goal is to remove these knobs for 10-RELEASE.
314 It is worth noting that bmake (like gmake) treats the command
315 line as the unit of failure, rather than statements within the
316 command line. Thus '(cd some/where && dosomething)' is safer
317 than 'cd some/where; dosomething'. The '()' allows consistent
318 behavior in parallel build.
321 Fix a bug that allows NFS clients to issue READDIR on files.
324 The WITHOUT_IDEA option has been removed because
325 the IDEA patent expired.
328 The sysctl which controls TRIM support under ZFS has been renamed
329 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
333 The mergemaster command now uses the default MAKEOBJDIRPREFIX
334 rather than creating it's own in the temporary directory in
335 order allow access to bootstrapped versions of tools such as
336 install and mtree. When upgrading from version of FreeBSD where
337 the install command does not support -l, you will need to
338 install a new mergemaster command if mergemaster -p is required.
339 This can be accomplished with the command (cd src/usr.sbin/mergemaster
343 Legacy ATA stack, disabled and replaced by new CAM-based one since
344 FreeBSD 9.0, completely removed from the sources. Kernel modules
345 atadisk and atapi*, user-level tools atacontrol and burncd are
346 removed. Kernel option `options ATA_CAM` is now permanently enabled
350 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
351 and socketpair(2). Software, in particular Kerberos, may
352 automatically detect and use these during building. The resulting
353 binaries will not work on older kernels.
356 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
357 information, see the respective 20130304 entry).
360 Recent commits to callout(9) changed the size of struct callout,
361 so the KBI is probably heavily disturbed. Also, some functions
362 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
363 by macros. Every kernel module using it won't load, so rebuild
366 The ctl device has been re-enabled in GENERIC for i386 and amd64,
367 but does not initialize by default (because of the new CTL_DISABLE
368 option) to save memory. To re-enable it, remove the CTL_DISABLE
369 option from the kernel config file or set kern.cam.ctl.disable=0
370 in /boot/loader.conf.
373 The ctl device has been disabled in GENERIC for i386 and amd64.
374 This was done due to the extra memory being allocated at system
375 initialisation time by the ctl driver which was only used if
376 a CAM target device was created. This makes a FreeBSD system
377 unusable on 128MB or less of RAM.
380 A new compression method (lz4) has been merged to -HEAD. Please
381 refer to zpool-features(7) for more information.
383 Please refer to the "ZFS notes" section of this file for information
384 on upgrading boot ZFS pools.
387 A BSD-licensed patch(1) variant has been added and is installed
388 as bsdpatch, being the GNU version the default patch.
389 To inverse the logic and use the BSD-licensed one as default,
390 while having the GNU version installed as gnupatch, rebuild
391 and install world with the WITH_BSD_PATCH knob set.
394 Due to the use of the new -l option to install(1) during build
395 and install, you must take care not to directly set the INSTALL
396 make variable in your /etc/make.conf, /etc/src.conf, or on the
397 command line. If you wish to use the -C flag for all installs
398 you may be able to add INSTALL+=-C to /etc/make.conf or
402 The install(1) option -M has changed meaning and now takes an
403 argument that is a file or path to append logs to. In the
404 unlikely event that -M was the last option on the command line
405 and the command line contained at least two files and a target
406 directory the first file will have logs appended to it. The -M
407 option served little practical purpose in the last decade so its
408 use is expected to be extremely rare.
411 After switching to Clang as the default compiler some users of ZFS
412 on i386 systems started to experience stack overflow kernel panics.
413 Please consider using 'options KSTACK_PAGES=4' in such configurations.
416 GEOM_LABEL now mangles label names read from file system metadata.
417 Mangling affect labels containing spaces, non-printable characters,
418 '%' or '"'. Device names in /etc/fstab and other places may need to
422 By default, only the 10 most recent kernel dumps will be saved. To
423 restore the previous behaviour (no limit on the number of kernel dumps
424 stored in the dump directory) add the following line to /etc/rc.conf:
429 With the addition of auditdistd(8), a new auditdistd user is now
430 required during installworld. "mergemaster -p" can be used to
431 add the user prior to installworld, as documented in the handbook.
434 The sin6_scope_id member variable in struct sockaddr_in6 is now
435 filled by the kernel before passing the structure to the userland via
436 sysctl or routing socket. This means the KAME-specific embedded scope
437 id in sin6_addr.s6_addr[2] is always cleared in userland application.
438 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
439 __FreeBSD_version is bumped to 1000025.
442 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
443 This means that the world and kernel will be compiled with clang
444 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
445 and /usr/bin/cpp. To disable this behavior and revert to building
446 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
447 of current may need to bootstrap WITHOUT_CLANG first if the clang
448 build fails (its compatibility window doesn't extend to the 9 stable
452 The IPFIREWALL_FORWARD kernel option has been removed. Its
453 functionality now turned on by default.
456 The ZERO_COPY_SOCKET kernel option has been removed and
457 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
458 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
459 mechanism which is not safe and may result in kernel crashes.
460 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
461 driver supports disposeable external page sized mbuf storage.
462 Proper replacements for both zero-copy mechanisms are under
463 consideration and will eventually lead to complete removal
464 of the two kernel options.
467 The IPv4 network stack has been converted to network byte
468 order. The following modules need to be recompiled together
469 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
470 pf(4), ipfw(4), ng_ipfw(4), stf(4).
473 Support for non-MPSAFE filesystems was removed from VFS. The
474 VFS_VERSION was bumped, all filesystem modules shall be
478 All the non-MPSAFE filesystems have been disconnected from
479 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
480 portalfs, smbfs, xfs.
483 The interface cloning API and ABI has changed. The following
484 modules need to be recompiled together with kernel:
485 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
486 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
487 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
490 The sdhci driver was split in two parts: sdhci (generic SD Host
491 Controller logic) and sdhci_pci (actual hardware driver).
492 No kernel config modifications are required, but if you
493 load sdhc as a module you must switch to sdhci_pci instead.
496 Import the FUSE kernel and userland support into base system.
499 The GNU sort(1) program has been removed since the BSD-licensed
500 sort(1) has been the default for quite some time and no serious
501 problems have been reported. The corresponding WITH_GNU_SORT
505 The pfil(9) API/ABI for AF_INET family has been changed. Packet
506 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
510 The net80211(4) ABI has been changed to allow for improved driver
511 PS-POLL and power-save support. All wireless drivers need to be
512 recompiled to work with the new kernel.
515 The random(4) support for the VIA hardware random number
516 generator (`PADLOCK') is no longer enabled unconditionally.
517 Add the padlock_rng device in the custom kernel config if
518 needed. The GENERIC kernels on i386 and amd64 do include the
519 device, so the change only affects the custom kernel
523 The pf(4) packet filter ABI has been changed. pfctl(8) and
524 snmp_pf module need to be recompiled to work with new kernel.
527 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
528 to -HEAD. Pools that have empty_bpobj in active state can not be
529 imported read-write with ZFS implementations that do not support
530 this feature. For more information read the zpool-features(5)
534 The sparc64 ZFS loader has been changed to no longer try to auto-
535 detect ZFS providers based on diskN aliases but now requires these
536 to be explicitly listed in the OFW boot-device environment variable.
539 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
540 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
541 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
544 The following sysctls and tunables have been renamed for consistency
545 with other variables:
546 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
547 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
550 The sort utility has been replaced with BSD sort. For now, GNU sort
551 is also available as "gnusort" or the default can be set back to
552 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
553 installed as "bsdsort".
556 A new version of ZFS (pool version 5000) has been merged to -HEAD.
557 Starting with this version the old system of ZFS pool versioning
558 is superseded by "feature flags". This concept enables forward
559 compatibility against certain future changes in functionality of ZFS
560 pools. The first read-only compatible "feature flag" for ZFS pools
561 is named "com.delphix:async_destroy". For more information
562 read the new zpool-features(5) manual page.
563 Please refer to the "ZFS notes" section of this file for information
564 on upgrading boot ZFS pools.
567 The malloc(3) implementation embedded in libc now uses sources imported
568 as contrib/jemalloc. The most disruptive API change is to
569 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
570 delete it prior to installworld, and optionally re-create it using the
571 new format after rebooting. See malloc.conf(5) for details
572 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
576 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
577 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
578 now spelled mips. This is to aid compatibility with third-party
579 software that expects this naming scheme in uname(3). Little-endian
580 settings are unchanged. If you are updating a big-endian mips64 machine
581 from before this change, you may need to set MACHINE_ARCH=mips64 in
582 your environment before the new build system will recognize your machine.
585 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
589 Now unix domain sockets behave "as expected" on nullfs(5). Previously
590 nullfs(5) did not pass through all behaviours to the underlying layer,
591 as a result if we bound to a socket on the lower layer we could connect
592 only to the lower path; if we bound to the upper layer we could connect
593 only to the upper path. The new behavior is one can connect to both the
594 lower and the upper paths regardless what layer path one binds to.
597 The getifaddrs upgrade path broken with 20111215 has been restored.
598 If you have upgraded in between 20111215 and 20120209 you need to
599 recompile libc again with your kernel. You still need to recompile
600 world to be able to configure CARP but this restriction already
604 The set_rcvar() function has been removed from /etc/rc.subr. All
605 base and ports rc.d scripts have been updated, so if you have a
606 port installed with a script in /usr/local/etc/rc.d you can either
607 hand-edit the rcvar= line, or reinstall the port.
609 An easy way to handle the mass-update of /etc/rc.d:
610 rm /etc/rc.d/* && mergemaster -i
613 panic(9) now stops other CPUs in the SMP systems, disables interrupts
614 on the current CPU and prevents other threads from running.
615 This behavior can be reverted using the kern.stop_scheduler_on_panic
617 The new behavior can be incompatible with kern.sync_on_panic.
620 The carp(4) facility has been changed significantly. Configuration
621 of the CARP protocol via ifconfig(8) has changed, as well as format
622 of CARP events submitted to devd(8) has changed. See manual pages
623 for more information. The arpbalance feature of carp(4) is currently
624 not supported anymore.
626 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
627 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
628 need to be recompiled.
631 The acpi_wmi(4) status device /dev/wmistat has been renamed to
635 The option VFS_ALLOW_NONMPSAFE option has been added in order to
636 explicitely support non-MPSAFE filesystems.
637 It is on by default for all supported platform at this present
641 The broken amd(4) driver has been replaced with esp(4) in the amd64,
642 i386 and pc98 GENERIC kernel configuration files.
645 sysinstall has been removed
648 The stable/9 branch created in subversion. This corresponds to the
649 RELENG_9 branch in CVS.
652 This commit modifies vfs_register() so that it uses a hash
653 calculation to set vfc_typenum, which is enabled by default.
654 The first time a system is booted after this change, the
655 vfc_typenum values will change for all file systems. The
656 main effect of this is a change to the NFS server file handles
657 for file systems that use vfc_typenum in their fsid, such as ZFS.
658 It will, however, prevent vfc_typenum from changing when file
659 systems are loaded in a different order for subsequent reboots.
660 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
661 until you are ready to remount all NFS clients after a reboot.
664 Bump the shared library version numbers for libraries that
665 do not use symbol versioning, have changed the ABI compared
666 to stable/8 and which shared library version was not bumped.
667 Done as part of 9.0-RELEASE cycle.
670 During the merge of Capsicum features, the fget(9) KPI was modified.
671 This may require the rebuilding of out-of-tree device drivers --
672 issues have been reported specifically with the nVidia device driver.
673 __FreeBSD_version is bumped to 900041.
675 Also, there is a period between 20110811 and 20110814 where the
676 special devices /dev/{stdin,stdout,stderr} did not work correctly.
677 Building world from a kernel during that window may not work.
680 The packet filter (pf) code has been updated to OpenBSD 4.5.
681 You need to update userland tools to be in sync with kernel.
682 This update breaks backward compatibility with earlier pfsync(4)
683 versions. Care must be taken when updating redundant firewall setups.
686 The following sysctls and tunables are retired on x86 platforms:
688 machdep.hlt_logical_cpus
689 The following sysctl is retired:
690 machdep.hyperthreading_allowed
691 The sysctls were supposed to provide a way to dynamically offline and
692 online selected CPUs on x86 platforms, but the implementation has not
693 been reliable especially with SCHED_ULE scheduler.
694 machdep.hyperthreading_allowed tunable is still available to ignore
695 hyperthreading CPUs at OS level.
696 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
697 where X is an APIC ID of a CPU. Be advised, though, that disabling
698 CPUs in non-uniform fashion will result in non-uniform topology and
699 may lead to sub-optimal system performance with SCHED_ULE, which is
703 cpumask_t type is retired and cpuset_t is used in order to describe
707 Changes to ifconfig(8) for dynamic address family detection mandate
708 that you are running a kernel of 20110525 or later. Make sure to
709 follow the update procedure to boot a new kernel before installing
713 Support for sun4v architecture is officially dropped
716 Several KPI breaking changes have been committed to the mii(4) layer,
717 the PHY drivers and consequently some Ethernet drivers using mii(4).
718 This means that miibus.ko and the modules of the affected Ethernet
719 drivers need to be recompiled.
721 Note to kernel developers: Given that the OUI bit reversion problem
722 was fixed as part of these changes all mii(4) commits related to OUIs,
723 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
724 handling, no longer can be merged verbatim to stable/8 and previous
728 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
729 into their kernel configurations along with 'device pci'.
732 The default NFS client is now the new NFS client, so fstype "newnfs"
733 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
734 Although mounts via fstype "nfs" will usually work without userland
735 changes, it is recommended that the mount(8) and mount_nfs(8)
736 commands be rebuilt from sources and that a link to mount_nfs called
737 mount_oldnfs be created. The new client is compiled into the
738 kernel with "options NFSCL" and this is needed for diskless root
739 file systems. The GENERIC kernel configs have been changed to use
740 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
741 To use the regular/old client, you can "mount -t oldnfs ...". For
742 a diskless root file system, you must also include a line like:
744 vfs.root.mountfrom="oldnfs:"
746 in the boot/loader.conf on the root fs on the NFS server to make
747 a diskless root fs use the old client.
750 The GENERIC kernels for all architectures now default to the new
751 CAM-based ATA stack. It means that all legacy ATA drivers were
752 removed and replaced by respective CAM drivers. If you are using
753 ATA device names in /etc/fstab or other places, make sure to update
754 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
755 where 'Y's are the sequential numbers starting from zero for each type
756 in order of detection, unless configured otherwise with tunables,
757 see cam(4)). There will be symbolic links created in /dev/ to map
758 old adX devices to the respective adaY. They should provide basic
759 compatibility for file systems mounting in most cases, but they do
760 not support old user-level APIs and do not have respective providers
761 in GEOM. Consider using updated management tools with new device names.
763 It is possible to load devices ahci, ata, siis and mvs as modules,
764 but option ATA_CAM should remain in kernel configuration to make ata
765 module work as CAM driver supporting legacy ATA controllers. Device ata
766 still can be used in modular fashion (atacore + ...). Modules atadisk
767 and atapi* are not used and won't affect operation in ATA_CAM mode.
768 Note that to use CAM-based ATA kernel should include CAM devices
769 scbus, pass, da (or explicitly ada), cd and optionally others. All of
770 them are parts of the cam module.
772 ataraid(4) functionality is now supported by the RAID GEOM class.
773 To use it you can load geom_raid kernel module and use graid(8) tool
774 for management. Instead of /dev/arX device names, use /dev/raid/rX.
776 No kernel config options or code have been removed, so if a problem
777 arises, please report it and optionally revert to the old ATA stack.
778 In order to do it you can remove from the kernel config:
783 , and instead add back:
784 device atadisk # ATA disk drives
785 device ataraid # ATA RAID drives
786 device atapicd # ATAPI CDROM drives
787 device atapifd # ATAPI floppy drives
788 device atapist # ATAPI tape drives
791 The default NFS server has been changed to the new server, which
792 was referred to as the experimental server. If you need to switch
793 back to the old NFS server, you must now put the "-o" option on
794 both the mountd and nfsd commands. This can be done using the
795 mountd_flags and nfs_server_flags rc.conf variables until an
796 update to the rc scripts is committed, which is coming soon.
799 The GNU Objective-C runtime library (libobjc), and other Objective-C
800 related components have been removed from the base system. If you
801 require an Objective-C library, please use one of the available ports.
804 ath(4) has been split into bus- and device- modules. if_ath contains
805 the HAL, the TX rate control and the network device code. if_ath_pci
806 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
807 contains the AHB glue. Users need to load both if_ath_pci and if_ath
808 in order to use ath on everything else.
810 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
811 need to load if_ath and if_ath_pci for ath(4) operation.
814 As part of the replacement of sysinstall, the process of building
815 release media has changed significantly. For details, please re-read
816 release(7), which has been updated to reflect the new build process.
819 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
820 is the last available version under GPLv2. It brings a number of new
821 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
822 4.1 and SSE 4.2), better support for powerpc64, a number of new
823 directives, and lots of other small improvements. See the ChangeLog
824 file in contrib/binutils for the full details.
827 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
828 compliant, and will now use half of hash for authentication.
829 This will break interoperability with all stacks (including all
830 actual FreeBSD versions) who implement
831 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
833 The only workaround with such peers is to use another HMAC
834 algorithm for IPsec ("phase 2") authentication.
837 Remove the uio_yield prototype and symbol. This function has
838 been misnamed since it was introduced and should not be
839 globally exposed with this name. The equivalent functionality
840 is now available using kern_yield(curthread->td_user_pri).
841 The function remains undocumented.
844 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
845 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
846 for scalar sysctls is defined but disabled. Code that needs
847 UQUAD to pass the type checking that must compile on older
848 systems where the define is not present can check against
849 __FreeBSD_version >= 900030.
851 The system dialog(1) has been replaced with a new version previously
852 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
853 with the previous version, but the libdialog associated with it has
854 a largely incompatible API. As such, the original version of libdialog
855 will be kept temporarily as libodialog, until its base system consumers
856 are replaced or updated. Bump __FreeBSD_version to 900030.
859 If you are trying to run make universe on a -stable system, and you get
860 the following warning:
861 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
862 unknown. config(8) likely too old."
863 or something similar to it, then you must upgrade your -stable system
864 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
865 stable/8) or build the config from the latest stable/8 branch and
866 install it on your system.
868 Prior to this date, building a current universe on 8-stable system from
869 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
870 error in the first kernel build phase. A new config on those old
871 systems will fix that problem for older versions of -current.
874 The TCP stack has been modified to allow Khelp modules to interact with
875 it via helper hook points and store per-connection data in the TCP
876 control block. Bump __FreeBSD_version to 900029. User space tools that
877 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
881 Generic IEEE 802.3 annex 31B full duplex flow control support has been
882 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
883 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
884 to take advantage of it instead of using custom implementations. This
885 means that these drivers now no longer unconditionally advertise
886 support for flow control but only do so if flow control is a selected
887 media option. This was implemented in the generic support that way in
888 order to allow flow control to be switched on and off via ifconfig(8)
889 with the PHY specific default to typically off in order to protect
890 from unwanted effects. Consequently, if you used flow control with
891 one of the above mentioned drivers you now need to explicitly enable
893 ifconfig bge0 media auto mediaopt flowcontrol
895 Along with the above mentioned changes generic support for setting
896 1000baseT master mode also has been added and brgphy(4), ciphy(4),
897 e1000phy(4) as well as ip1000phy(4) have been converted to take
898 advantage of it. This means that these drivers now no longer take the
899 link0 parameter for selecting master mode but the master media option
900 has to be used instead, for example like in the following:
901 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
903 Selection of master mode now is also available with all other PHY
904 drivers supporting 1000baseT.
907 The TCP stack has received a significant update to add support for
908 modularised congestion control and generally improve the clarity of
909 congestion control decisions. Bump __FreeBSD_version to 900025. User
910 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
911 sockstat) need to be recompiled.
914 The man(1) utility has been replaced by a new version that no longer
915 uses /etc/manpath.config. Please consult man.conf(5) for how to
916 migrate local entries to the new format.
919 The copyright strings printed by login(1) and sshd(8) at the time of a
920 new connection have been removed to follow other operating systems and
924 A workaround for a fixed ld bug has been removed in kernel code,
925 so make sure that your system ld is built from sources after
926 revision 210245 from 2010-07-19 (r211583 if building head kernel
927 on stable/8, r211584 for stable/7; both from 2010-08-21).
928 A symptom of incorrect ld version is different addresses for
929 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
932 The $ipv6_prefer variable in rc.conf(5) has been split into
933 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
935 The $ip6addrctl_policy is a variable to choose a pre-defined
936 address selection policy set by ip6addrctl(8). A value
937 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
940 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
941 flag (see an entry of 20090926) is set on an interface with no
942 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
943 security reason. If you want IPv6 link-local address on all
944 interfaces by default, set this to "YES".
946 The old ipv6_prefer="YES" is equivalent to
947 ipv6_activate_all_interfaces="YES" and
948 ip6addrctl_policy="ipv6_prefer".
951 DTrace has grown support for userland tracing. Due to this, DTrace is
952 now i386 and amd64 only.
953 dtruss(1) is now installed by default on those systems and a new
954 kernel module is needed for userland tracing: fasttrap.
955 No changes to your kernel config file are necessary to enable
956 userland tracing, but you might consider adding 'STRIP=' and
957 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
958 to have informative userland stack traces in DTrace (ustack).
961 The acpi_aiboost(4) driver has been removed in favor of the new
962 aibs(4) driver. You should update your kernel configuration file.
965 BSD grep has been imported to the base system and it is built by
966 default. It is completely BSD licensed, highly GNU-compatible, uses
967 less memory than its GNU counterpart and has a small codebase.
968 However, it is slower than its GNU counterpart, which is mostly
969 noticeable for larger searches, for smaller ones it is measurable
970 but not significant. The reason is complex, the most important factor
971 is that we lack a modern and efficient regex library and GNU
972 overcomes this by optimizing the searches internally. Future work
973 on improving the regex performance is planned, for the meantime,
974 users that need better performance, can build GNU grep instead by
975 setting the WITH_GNU_GREP knob.
978 Due to the import of powerpc64 support, all existing powerpc kernel
979 configuration files must be updated with a machine directive like this:
980 machine powerpc powerpc
982 In addition, an updated config(8) is required to build powerpc kernels
986 A new version of ZFS (version 15) has been merged to -HEAD.
987 This version uses a python library for the following subcommands:
988 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
989 For full functionality of these commands the following port must
990 be installed: sysutils/py-zfs
993 'vm_page's are now hashed by physical address to an array of mutexes.
994 Currently this is only used to serialize access to hold_count. Over
995 time the page queue mutex will be peeled away. This changes the size
996 of pmap on every architecture. And requires all callers of vm_page_hold
997 and vm_page_unhold to be updated.
1000 WITH_CTF can now be specified in src.conf (not recommended, there
1001 are some problems with static executables), make.conf (would also
1002 affect ports which do not use GNU make and do not override the
1003 compile targets) or in the kernel config (via "makeoptions
1005 When WITH_CTF was specified there before this was silently ignored,
1006 so make sure that WITH_CTF is not used in places which could lead
1007 to unwanted behavior.
1010 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1011 to allow 32-bit compatibility on non-x86 platforms. All kernel
1012 configurations on amd64 and ia64 platforms using these options must
1013 be modified accordingly.
1016 The utmp user accounting database has been replaced with utmpx,
1017 the user accounting interface standardized by POSIX.
1018 Unfortunately the semantics of utmp and utmpx don't match,
1019 making it practically impossible to support both interfaces.
1020 The user accounting database is used by tools like finger(1),
1021 last(1), talk(1), w(1) and ac(8).
1023 All applications in the base system use utmpx. This means only
1024 local binaries (e.g. from the ports tree) may still use these
1025 utmp database files. These applications must be rebuilt to make
1028 After the system has been upgraded, it is safe to remove the old
1029 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1030 assuming their contents is of no importance anymore. Old wtmp
1031 databases can only be used by last(1) and ac(8) after they have
1032 been converted to the new format using wtmpcvt(1).
1035 Introduce the kernel thread "deadlock resolver" (which can be enabled
1036 via the DEADLKRES option, see NOTES for more details) and the
1037 sleepq_type() function for sleepqueues.
1040 The rc.firewall and rc.firewall6 were unified, and
1041 rc.firewall6 and rc.d/ip6fw were removed.
1042 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1043 variables are obsoleted. Instead, the following new rc
1044 variables are added to rc.d/ipfw:
1046 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1047 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1048 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1050 The meanings correspond to the relevant IPv4 variables.
1056 The default terminal emulation for syscons(4) has been changed
1057 from cons25 to xterm on all platforms except pc98. This means
1058 that the /etc/ttys file needs to be updated to ensure correct
1059 operation of applications on the console.
1061 The terminal emulation style can be toggled per window by using
1062 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1063 options can be used to change the compile-time default back to
1066 To prevent graphical artifacts, make sure the TERM environment
1067 variable is set to match the terminal emulation that is being
1068 performed by syscons(4).
1071 The layout of the structure ieee80211req_scan_result has changed.
1072 Applications that require wireless scan results (e.g. ifconfig(8))
1073 from net80211 need to be recompiled.
1075 Applications such as wpa_supplicant(8) may require a full world
1076 build without using NO_CLEAN in order to get synchronized with the
1080 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1081 There's one kernel module for each firmware. Adding "device iwnfw"
1082 to the kernel configuration file means including all three firmware
1083 images inside the kernel. If you want to include just the one for
1084 your wireless card, use the devices iwn4965fw, iwn5000fw or
1088 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1089 into rc.d/netif. The changes are the following:
1091 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1092 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1093 Note that both variables need the "inet6" keyword at the head.
1095 Do not set $ipv6_network_interfaces manually if you do not
1096 understand what you are doing. It is not needed in most cases.
1098 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1101 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1102 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1104 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1105 all configured interfaces have "inet6 accept_rtadv" in the
1106 $ifconfig_IF_ipv6. These are for backward compatibility.
1108 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1109 functionality of interfaces with no corresponding
1110 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1111 and the default address selection policy of ip6addrctl(8)
1112 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1113 Note that if you want to configure IPv6 functionality on the
1114 disabled interfaces after boot, first you need to clear the flag by
1115 using ifconfig(8) like:
1117 ifconfig em0 inet6 -ifdisabled
1119 If YES, the default address selection policy is set as
1122 The default value of $ipv6_prefer is NO.
1124 4. If your system need to receive Router Advertisement messages,
1125 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1126 scripts automatically invoke rtsol(8) when the interface becomes
1127 UP. The Router Advertisement messages are used for SLAAC
1128 (State-Less Address AutoConfiguration).
1131 802.11s D3.03 support was committed. This is incompatible with the
1132 previous code, which was based on D3.0.
1135 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1136 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1137 control whether accepting Router Advertisement messages or not.
1138 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1139 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1140 The ifconfig(8) utility now supports these flags.
1143 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1144 mount(8) and -a option for df(1) to see them.
1147 The old tunable hw.bus.devctl_disable has been superseded by
1148 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1149 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1153 Remove the option STOP_NMI. The default action is now to use NMI only
1154 for KDB via the newly introduced function stop_cpus_hard() and
1155 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1158 The stable/8 branch created in subversion. This corresponds to the
1159 RELENG_8 branch in CVS.
1162 Bump the shared library version numbers for all libraries that do not
1163 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1164 __FreeBSD_version to 800105.
1167 Due to changes in the implementation of virtual network stack support,
1168 all network-related kernel modules must be recompiled. As this change
1169 breaks the ABI, bump __FreeBSD_version to 800104.
1172 The TOE interface to the TCP syncache has been modified to remove
1173 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1174 The cxgb driver is the only TOE consumer affected by this change, and
1175 needs to be recompiled along with the kernel. As this change breaks
1176 the ABI, bump __FreeBSD_version to 800103.
1179 Padding has been added to struct tcpcb, sackhint and tcpstat in
1180 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1181 maintaining the ABI. However, this change breaks the ABI, so bump
1182 __FreeBSD_version to 800102. User space tools that rely on the size of
1183 any of these structs (e.g. sockstat) need to be recompiled.
1186 The NFS_LEGACYRPC option has been removed along with the old kernel
1187 RPC implementation that this option selected. Kernel configurations
1188 may need to be adjusted.
1191 The network interface device nodes at /dev/net/<interface> have been
1192 removed. All ioctl operations can be performed the normal way using
1193 routing sockets. The kqueue functionality can generally be replaced
1194 with routing sockets.
1197 The documentation from the FreeBSD Documentation Project (Handbook,
1198 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1199 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1202 The ABI of various structures related to the SYSV IPC API have been
1203 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1204 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1208 Layout of struct vnet has changed as routing related variables were
1209 moved to their own Vimage module. Modules need to be recompiled. Bump
1210 __FreeBSD_version to 800099.
1213 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1214 respectively. As long as no more than 16 groups per process are used,
1215 no changes should be visible. When more than 16 groups are used, old
1216 binaries may fail if they call getgroups() or getgrouplist() with
1217 statically sized storage. Recompiling will work around this, but
1218 applications should be modified to use dynamically allocated storage
1219 for group arrays as POSIX.1-2008 does not cap an implementation's
1220 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1222 NFS and portalfs mounts may also be affected as the list of groups is
1223 truncated to 16. Users of NFS who use more than 16 groups, should
1224 take care that negative group permissions are not used on the exported
1225 file systems as they will not be reliable unless a GSSAPI based
1226 authentication method is used.
1229 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1230 option compiles in the support for adaptive spinning for lockmgrs
1231 which want to enable it. The lockinit() function now accepts the flag
1232 LK_ADAPTIVE in order to make the lock object subject to adaptive
1233 spinning when both held in write and read mode.
1236 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1237 changed. User applications that use this ioctl need to be rebuilt.
1240 The layout of struct thread has changed. Kernel and modules need to
1244 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1245 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1248 window(1) has been removed from the base system. It can now be
1249 installed from ports. The port is called misc/window.
1252 The way we are storing and accessing `routing table' entries has
1253 changed. Programs reading the FIB, like netstat, need to be
1257 A new netisr implementation has been added for FreeBSD 8. Network
1258 file system modules, such as igmp, ipdivert, and others, should be
1260 Bump __FreeBSD_version to 800096.
1263 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1267 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1268 Bump __FreeBSD_version to 800094.
1271 Add mnt_xflag field to 'struct mount'. File system modules need to be
1273 Bump __FreeBSD_version to 800093.
1276 The compiling option ADAPTIVE_SX has been retired while it has been
1277 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1278 The KPI for sx_init_flags() changes as accepting flags:
1279 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1280 been introduced in order to handle the reversed logic.
1281 Bump __FreeBSD_version to 800092.
1284 Add support for hierarchical jails. Remove global securelevel.
1285 Bump __FreeBSD_version to 800091.
1288 The layout of struct vnet_net has changed, therefore modules
1290 Bump __FreeBSD_version to 800090.
1293 The newly imported zic(8) produces a new format in the output. Please
1294 run tzsetup(8) to install the newly created data to /etc/localtime.
1297 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1298 hw.usb.* and is now consistent again with previous releases.
1301 802.11 monitor mode support was revised and driver api's were changed.
1302 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1303 of DLT_IEEE802_11. No user-visible data structures were changed but
1304 applications that use DLT_IEEE802_11 may require changes.
1305 Bump __FreeBSD_version to 800088.
1308 The layout of the following structs has changed: sysctl_oid,
1309 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1310 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1311 panics may be experienced. World rebuild is required for
1312 correctly checking networking state from userland.
1313 Bump __FreeBSD_version to 800085.
1316 MLDv2 and Source-Specific Multicast (SSM) have been merged
1317 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1318 The implementation of SSM within FreeBSD's IPv6 stack closely
1319 follows the IPv4 implementation.
1321 For kernel developers:
1323 * The most important changes are that the ip6_output() and
1324 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1325 and this lock has been downgraded to a non-recursive mutex.
1327 * As with the changes to the IPv4 stack to support SSM, filtering
1328 of inbound multicast traffic must now be performed by transport
1329 protocols within the IPv6 stack. This does not apply to TCP and
1330 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1332 * The KPIs used by IPv6 multicast are similar to those used by
1333 the IPv4 stack, with the following differences:
1334 * im6o_mc_filter() is analogous to imo_multicast_filter().
1335 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1336 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1337 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1338 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1339 for MLDv1 have an additional 'timer' argument which is used to
1340 jitter the initial membership report for the solicited-node
1341 multicast membership on-link.
1342 * This is not strictly needed for MLDv2, which already jitters
1343 its report transmissions. However, the 'timer' argument is
1344 preserved in case MLDv1 is active on the interface.
1346 * The KAME linked-list based IPv6 membership implementation has
1347 been refactored to use a vector similar to that used by the IPv4
1349 Code which maintains a list of its own multicast memberships
1350 internally, e.g. carp, has been updated to reflect the new
1353 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1354 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1355 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1356 implementation constraint which needs to be addressed in HEAD.
1358 For application developers:
1360 * The changes are broadly similar to those made for the IPv4
1363 * The use of IPv4 and IPv6 multicast socket options on the same
1364 socket, using mapped addresses, HAS NOT been tested or supported.
1366 * There are a number of issues with the implementation of various
1367 IPv6 multicast APIs which need to be resolved in the API surface
1368 before the implementation is fully compatible with KAME userland
1369 use, and these are mostly to do with interface index treatment.
1371 * The literature available discusses the use of either the delta / ASM
1372 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1373 using setsourcefilter(3)/getsourcefilter(3). For more information
1374 please refer to RFC 3768, 'Socket Interface Extensions for
1375 Multicast Source Filters'.
1377 * Applications which use the published RFC 3678 APIs should be fine.
1379 For systems administrators:
1381 * The mtest(8) utility has been refactored to support IPv6, in
1382 addition to IPv4. Interface addresses are no longer accepted
1383 as arguments, their names must be used instead. The utility
1384 will map the interface name to its first IPv4 address as
1385 returned by getifaddrs(3).
1387 * The ifmcstat(8) utility has also been updated to print the MLDv2
1388 endpoint state and source filter lists via sysctl(3).
1390 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1391 loopback of IPv6 multicast datagrams by default; it defaults to 1
1392 to preserve the existing behaviour. Disabling multicast loopback is
1393 recommended for optimal system performance.
1395 * The IPv6 MROUTING code has been changed to examine this sysctl
1396 instead of attempting to perform a group lookup before looping
1397 back forwarded datagrams.
1399 Bump __FreeBSD_version to 800084.
1402 Implement low-level Bluetooth HCI API.
1403 Bump __FreeBSD_version to 800083.
1406 The layout of struct malloc_type, used by modules to register new
1407 memory allocation types, has changed. Most modules will need to
1408 be rebuilt or panics may be experienced.
1409 Bump __FreeBSD_version to 800081.
1412 Anticipate overflowing inp_flags - add inp_flags2.
1413 This changes most offsets in inpcb, so checking v4 connection
1414 state will require a world rebuild.
1415 Bump __FreeBSD_version to 800080.
1418 Add an llentry to struct route and struct route_in6. Modules
1419 embedding a struct route will need to be recompiled.
1420 Bump __FreeBSD_version to 800079.
1423 The size of rt_metrics_lite and by extension rtentry has changed.
1424 Networking administration apps will need to be recompiled.
1425 The route command now supports show as an alias for get, weighting
1426 of routes, sticky and nostick flags to alter the behavior of stateful
1428 Bump __FreeBSD_version to 800078.
1431 Do not use Giant for kbdmux(4) locking. This is wrong and
1432 apparently causing more problems than it solves. This will
1433 re-open the issue where interrupt handlers may race with
1434 kbdmux(4) in polling mode. Typical symptoms include (but
1435 not limited to) duplicated and/or missing characters when
1436 low level console functions (such as gets) are used while
1437 interrupts are enabled (for example geli password prompt,
1438 mountroot prompt etc.). Disabling kbdmux(4) may help.
1441 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1442 kernel modules referencing any of the above need to be recompiled.
1443 Bump __FreeBSD_version to 800075.
1446 GEOM_PART has become the default partition slicer for storage devices,
1447 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1448 introduces some changes:
1450 MSDOS/EBR: the devices created from MSDOS extended partition entries
1451 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1452 to devices with offset-based names. fstabs may need to be modified.
1454 BSD: the "geometry does not match label" warning is harmless in most
1455 cases but it points to problems in file system misalignment with
1456 disk geometry. The "c" partition is now implicit, covers the whole
1457 top-level drive and cannot be (mis)used by users.
1459 General: Kernel dumps are now not allowed to be written to devices
1460 whose partition types indicate they are meant to be used for file
1461 systems (or, in case of MSDOS partitions, as something else than
1464 Most of these changes date approximately from 200812.
1467 The uscanner(4) driver has been removed from the kernel. This follows
1468 Linux removing theirs in 2.6 and making libusb the default interface
1469 (supported by sane).
1472 The multicast forwarding code has been cleaned up. netstat(1)
1473 only relies on KVM now for printing bandwidth upcall meters.
1474 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1475 ip6_mroute_mod respectively. The config(5) options for statically
1476 compiling this code remain the same, i.e. 'options MROUTING'.
1479 Support for the IFF_NEEDSGIANT network interface flag has been
1480 removed, which means that non-MPSAFE network device drivers are no
1481 longer supported. In particular, if_ar, if_sr, and network device
1482 drivers from the old (legacy) USB stack can no longer be built or
1486 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1487 a bunch of new language catalog files have also been added.
1488 This means that some common libc messages are now localized and
1489 they depend on the LC_MESSAGES environmental variable.
1492 The k8temp(4) driver has been renamed to amdtemp(4) since
1493 support for Family 10 and Family 11 CPU families was added.
1496 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1497 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1499 For kernel developers, the most important changes are that the
1500 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1501 and this lock has been downgraded to a non-recursive mutex.
1503 Transport protocols (UDP, Raw IP) are now responsible for filtering
1504 inbound multicast traffic according to group membership and source
1505 filters. The imo_multicast_filter() KPI exists for this purpose.
1506 Transports which do not use multicast (SCTP, TCP) already reject
1507 multicast by default. Forwarding and receive performance may improve
1508 as a mutex acquisition is no longer needed in the ip_input()
1509 low-level input path. in_addmulti() and in_delmulti() are shimmed
1510 to new KPIs which exist to support SSM in-kernel.
1512 For application developers, it is recommended that loopback of
1513 multicast datagrams be disabled for best performance, as this
1514 will still cause the lock to be taken for each looped-back
1515 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1516 be tuned to 0 to disable loopback by default; it defaults to 1
1517 to preserve the existing behaviour.
1519 For systems administrators, to obtain best performance with
1520 multicast reception and multiple groups, it is always recommended
1521 that a card with a suitably precise hash filter is used. Hash
1522 collisions will still result in the lock being taken within the
1523 transport protocol input path to check group membership.
1525 If deploying FreeBSD in an environment with IGMP snooping switches,
1526 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1527 enabled; this forces 224.0.0.0/24 group membership to be announced
1530 The size of 'struct igmpstat' has changed; netstat needs to be
1531 recompiled to reflect this.
1532 Bump __FreeBSD_version to 800070.
1535 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1536 updated to use it. This requires a buildworld/installworld in order to
1537 update the library and dependencies (usbconfig, etc). Its advisable to
1538 rebuild all ports which uses libusb. More specific directions are given
1539 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1540 libusb are no longer required and can be removed.
1543 A workaround is committed to allow the creation of System V shared
1544 memory segment of size > 2 GB on the 64-bit architectures.
1545 Due to a limitation of the existing ABI, the shm_segsz member
1546 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1547 wrong for large segments. Note that limits must be explicitly
1548 raised to allow such segments to be created.
1551 The layout of struct ifnet has changed, requiring a rebuild of all
1552 network device driver modules.
1555 The /dev handling for the new USB stack has changed, a
1556 buildworld/installworld is required for libusb20.
1559 The new USB2 stack has now been permanently moved in and all kernel and
1560 module names reverted to their previous values (eg, usb, ehci, ohci,
1561 ums, ...). The old usb stack can be compiled in by prefixing the name
1562 with the letter 'o', the old usb modules have been removed.
1563 Updating entry 20090216 for xorg and 20090215 for libmap may still
1567 The rc.conf(5) option if_up_delay has been renamed to
1568 defaultroute_delay to better reflect its purpose. If you have
1569 customized this setting in /etc/rc.conf you need to update it to
1573 xorg 7.4 wants to configure its input devices via hald which does not
1574 yet work with USB2. If the keyboard/mouse does not work in xorg then
1576 Option "AllowEmptyInput" "off"
1577 to your ServerLayout section. This will cause X to use the configured
1578 kbd and mouse sections from your xorg.conf.
1581 The GENERIC kernels for all architectures now default to the new USB2
1582 stack. No kernel config options or code have been removed so if a
1583 problem arises please report it and optionally revert to the old USB
1584 stack. If you are loading USB kernel modules or have a custom kernel
1585 that includes GENERIC then ensure that usb names are also changed over,
1586 eg uftdi -> usb2_serial_ftdi.
1588 Older programs linked against the ports libusb 0.1 need to be
1589 redirected to the new stack's libusb20. /etc/libmap.conf can
1591 # Map old usb library to new one for usb2 stack
1592 libusb-0.1.so.8 libusb20.so.1
1595 All USB ethernet devices now attach as interfaces under the name ueN
1596 (eg. ue0). This is to provide a predictable name as vendors often
1597 change usb chipsets in a product without notice.
1600 The ichsmb(4) driver has been changed to require SMBus slave
1601 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1602 All of the other SMBus controller drivers require left-justified
1603 slave addresses, so this change makes all the drivers provide the
1607 INET6 statistics (struct ip6stat) was updated.
1608 netstat(1) needs to be recompiled.
1611 NTFS has been removed from GENERIC kernel on amd64 to match
1612 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1613 will load ntfs.ko module automatically when NTFS support is
1614 actually needed, unless ntfs.ko is not installed or security
1615 level prohibits loading kernel modules. If either is the case,
1616 "options NTFS" has to be added into kernel config.
1619 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1620 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1621 800061. User space tools that rely on the size of struct tcpcb in
1622 tcp_var.h (e.g. sockstat) need to be recompiled.
1625 ng_tty(4) module updated to match the new TTY subsystem.
1626 Due to API change, user-level applications must be updated.
1627 New API support added to mpd5 CVS and expected to be present
1628 in next mpd5.3 release.
1631 With __FreeBSD_version 800060 the makefs tool is part of
1632 the base system (it was a port).
1635 The afdata and ifnet locks have been changed from mutexes to
1636 rwlocks, network modules will need to be re-compiled.
1639 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1640 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1641 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1642 architecture and 40 bytes on 64-bit architecture. The userland
1643 applications "arp" and "ndp" have been updated accordingly.
1644 The output from "netstat -r" shows only routing entries and
1645 none of the L2 information.
1648 __FreeBSD_version 800057 marks the switchover from the
1649 binary ath hal to source code. Users must add the line:
1651 options AH_SUPPORT_AR5416
1653 to their kernel config files when specifying:
1657 The ath_hal module no longer exists; the code is now compiled
1658 together with the driver in the ath module. It is now
1659 possible to tailor chip support (i.e. reduce the set of chips
1660 and thereby the code size); consult ath_hal(4) for details.
1663 __FreeBSD_version 800054 adds memory barriers to
1664 <machine/atomic.h>, new interfaces to ifnet to facilitate
1665 multiple hardware transmit queues for cards that support
1666 them, and a lock-less ring-buffer implementation to
1667 enable drivers to more efficiently manage queueing of
1671 A new version of ZFS (version 13) has been merged to -HEAD.
1672 This version has zpool attribute "listsnapshots" off by
1673 default, which means "zfs list" does not show snapshots,
1674 and is the same as Solaris behavior.
1677 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1680 The uhci, ohci, ehci and slhci USB Host controller drivers have
1681 been put into separate modules. If you load the usb module
1682 separately through loader.conf you will need to load the
1683 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1684 controller add the following to loader.conf:
1690 The ABI used by the PMC toolset has changed. Please keep
1691 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1695 atapci kernel module now includes only generic PCI ATA
1696 driver. AHCI driver moved to ataahci kernel module.
1697 All vendor-specific code moved into separate kernel modules:
1698 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1699 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1700 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1701 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1704 The TTY subsystem of the kernel has been replaced by a new
1705 implementation, which provides better scalability and an
1706 improved driver model. Most common drivers have been migrated to
1707 the new TTY subsystem, while others have not. The following
1708 drivers have not yet been ported to the new TTY layer:
1711 cy, digi, rc, rp, sio
1717 ng_h4, ng_tty, ppp, sl, snp
1719 Adding these drivers to your kernel configuration file shall
1720 cause compilation to fail.
1723 ntpd has been upgraded to 4.2.4p5.
1726 OpenSSH has been upgraded to 5.1p1.
1728 For many years, FreeBSD's version of OpenSSH preferred DSA
1729 over RSA for host and user authentication keys. With this
1730 upgrade, we've switched to the vendor's default of RSA over
1731 DSA. This may cause upgraded clients to warn about unknown
1732 host keys even for previously known hosts. Users should
1733 follow the usual procedure for verifying host keys before
1734 accepting the RSA key.
1736 This can be circumvented by setting the "HostKeyAlgorithms"
1737 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1740 Please note that the sequence of keys offered for
1741 authentication has been changed as well. You may want to
1742 specify IdentityFile in a different order to revert this
1746 The sio(4) driver has been removed from the i386 and amd64
1747 kernel configuration files. This means uart(4) is now the
1748 default serial port driver on those platforms as well.
1750 To prevent collisions with the sio(4) driver, the uart(4) driver
1751 uses different names for its device nodes. This means the
1752 onboard serial port will now most likely be called "ttyu0"
1753 instead of "ttyd0". You may need to reconfigure applications to
1754 use the new device names.
1756 When using the serial port as a boot console, be sure to update
1757 /boot/device.hints and /etc/ttys before booting the new kernel.
1758 If you forget to do so, you can still manually specify the hints
1759 at the loader prompt:
1761 set hint.uart.0.at="isa"
1762 set hint.uart.0.port="0x3F8"
1763 set hint.uart.0.flags="0x10"
1764 set hint.uart.0.irq="4"
1768 The gpt(8) utility has been removed. Use gpart(8) to partition
1772 The version that Linuxulator emulates was changed from 2.4.2
1773 to 2.6.16. If you experience any problems with Linux binaries
1774 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1775 if it fixes the problem contact emulation mailing list.
1778 ISDN4BSD (I4B) was removed from the src tree. You may need to
1779 update a your kernel configuration and remove relevant entries.
1782 I have checked in code to support multiple routing tables.
1783 See the man pages setfib(1) and setfib(2).
1784 This is a hopefully backwards compatible version,
1785 but to make use of it you need to compile your kernel
1786 with options ROUTETABLES=2 (or more up to 16).
1789 The 802.11 wireless support was redone to enable multi-bss
1790 operation on devices that are capable. The underlying device
1791 is no longer used directly but instead wlanX devices are
1792 cloned with ifconfig. This requires changes to rc.conf files.
1793 For example, change:
1794 ifconfig_ath0="WPA DHCP"
1797 ifconfig_wlan0="WPA DHCP"
1798 see rc.conf(5) for more details. In addition, mergemaster of
1799 /etc/rc.d is highly recommended. Simultaneous update of userland
1800 and kernel wouldn't hurt either.
1802 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1803 modules were merged into the base wlan module. All references
1804 to these modules (e.g. in kernel config files) must be removed.
1807 psm(4) has gained write(2) support in native operation level.
1808 Arbitrary commands can be written to /dev/psm%d and status can
1809 be read back from it. Therefore, an application is responsible
1810 for status validation and error recovery. It is a no-op in
1811 other operation levels.
1814 Support for KSE threading has been removed from the kernel. To
1815 run legacy applications linked against KSE libmap.conf may
1816 be used. The following libmap.conf may be used to ensure
1817 compatibility with any prior release:
1819 libpthread.so.1 libthr.so.1
1820 libpthread.so.2 libthr.so.2
1821 libkse.so.3 libthr.so.3
1824 The layout of struct vmspace has changed. This affects libkvm
1825 and any executables that link against libkvm and use the
1826 kvm_getprocs() function. In particular, but not exclusively,
1827 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1828 The effects are minimal, but it's advisable to upgrade world
1832 The latest em driver no longer has support in it for the
1833 82575 adapter, this is now moved to the igb driver. The
1834 split was done to make new features that are incompatible
1835 with older hardware easier to do.
1838 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1839 likewise the kernel option is now GEOM_LINUX_LVM.
1842 The default NFS mount mode has changed from UDP to TCP for
1843 increased reliability. If you rely on (insecurely) NFS
1844 mounting across a firewall you may need to update your
1848 Belatedly note the addition of m_collapse for compacting
1852 The fts(3) structures have been changed to use adequate
1853 integer types for their members and so to be able to cope
1854 with huge file trees. The old fts(3) ABI is preserved
1855 through symbol versioning in libc, so third-party binaries
1856 using fts(3) should still work, although they will not take
1857 advantage of the extended types. At the same time, some
1858 third-party software might fail to build after this change
1859 due to unportable assumptions made in its source code about
1860 fts(3) structure members. Such software should be fixed
1861 by its vendor or, in the worst case, in the ports tree.
1862 FreeBSD_version 800015 marks this change for the unlikely
1863 case that a portable fix is impossible.
1866 To upgrade to -current after this date, you must be running
1867 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1868 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1871 The ADAPTIVE_GIANT kernel option has been retired because its
1872 functionality is the default now.
1875 The AT keyboard emulation of sunkbd(4) has been turned on
1876 by default. In order to make the special symbols of the Sun
1877 keyboards driven by sunkbd(4) work under X these now have
1878 to be configured the same way as Sun USB keyboards driven
1879 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1881 Option "XkbLayout" "us"
1882 Option "XkbRules" "xorg"
1883 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1886 It has been decided that it is desirable to provide ABI
1887 backwards compatibility to the FreeBSD 4/5/6 versions of the
1888 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1889 broken with the introduction of PCI domain support (see the
1890 20070930 entry). Unfortunately, this required the ABI of
1891 PCIOCGETCONF to be broken again in order to be able to
1892 provide backwards compatibility to the old version of that
1893 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1894 again. As for prominent ports this affects neither pciutils
1895 nor xorg-server this time, the hal port needs to be rebuilt
1899 The misnamed kthread_create() and friends have been renamed
1900 to kproc_create() etc. Many of the callers already
1901 used kproc_start()..
1902 I will return kthread_create() and friends in a while
1903 with implementations that actually create threads, not procs.
1904 Renaming corresponds with version 800002.
1913 Avoid using make -j when upgrading. While generally safe, there are
1914 sometimes problems using -j to upgrade. If your upgrade fails with
1915 -j, please try again without -j. From time to time in the past there
1916 have been problems using -j with buildworld and/or installworld. This
1917 is especially true when upgrading between "distant" versions (eg one
1918 that cross a major release boundary or several minor releases, or when
1919 several months have passed on the -current branch).
1921 Sometimes, obscure build problems are the result of environment
1922 poisoning. This can happen because the make utility reads its
1923 environment when searching for values for global variables. To run
1924 your build attempts in an "environmental clean room", prefix all make
1925 commands with 'env -i '. See the env(1) manual page for more details.
1927 When upgrading from one major version to another it is generally best
1928 to upgrade to the latest code in the currently installed branch first,
1929 then do an upgrade to the new branch. This is the best-tested upgrade
1930 path, and has the highest probability of being successful. Please try
1931 this approach before reporting problems with a major version upgrade.
1933 When upgrading a live system, having a root shell around before
1934 installing anything can help undo problems. Not having a root shell
1935 around can lead to problems if pam has changed too much from your
1936 starting point to allow continued authentication after the upgrade.
1940 When upgrading the boot ZFS pool to a new version, always follow
1943 1.) recompile and reinstall the ZFS boot loader and boot block
1944 (this is part of "make buildworld" and "make installworld")
1946 2.) update the ZFS boot block on your boot drive
1948 The following example updates the ZFS boot block on the first
1949 partition (freebsd-boot) of a GPT partitioned drive ad0:
1950 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1952 Non-boot pools do not need these updates.
1956 If you are updating from a prior version of FreeBSD (even one just
1957 a few days old), you should follow this procedure. It is the most
1958 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1960 make kernel-toolchain
1961 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1962 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1964 To test a kernel once
1965 ---------------------
1966 If you just want to boot a kernel once (because you are not sure
1967 if it works, or if you want to boot a known bad kernel to provide
1968 debugging information) run
1969 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1970 nextboot -k testkernel
1972 To just build a kernel when you know that it won't mess you up
1973 --------------------------------------------------------------
1974 This assumes you are already running a CURRENT system. Replace
1975 ${arch} with the architecture of your machine (e.g. "i386",
1976 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1978 cd src/sys/${arch}/conf
1979 config KERNEL_NAME_HERE
1980 cd ../compile/KERNEL_NAME_HERE
1985 If this fails, go to the "To build a kernel" section.
1987 To rebuild everything and install it on the current system.
1988 -----------------------------------------------------------
1989 # Note: sometimes if you are running current you gotta do more than
1990 # is listed here if you are upgrading from a really old current.
1992 <make sure you have good level 0 dumps>
1994 make kernel KERNCONF=YOUR_KERNEL_HERE
1996 <reboot in single user> [3]
2003 To cross-install current onto a separate partition
2004 --------------------------------------------------
2005 # In this approach we use a separate partition to hold
2006 # current's root, 'usr', and 'var' directories. A partition
2007 # holding "/", "/usr" and "/var" should be about 2GB in
2010 <make sure you have good level 0 dumps>
2013 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2014 <maybe newfs current's root partition>
2015 <mount current's root partition on directory ${CURRENT_ROOT}>
2016 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
2017 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2018 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2019 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2020 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2021 <reboot into current>
2022 <do a "native" rebuild/install as described in the previous section>
2023 <maybe install compatibility libraries from ports/misc/compat*>
2027 To upgrade in-place from stable to current
2028 ----------------------------------------------
2029 <make sure you have good level 0 dumps>
2031 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2033 <reboot in single user> [3]
2040 Make sure that you've read the UPDATING file to understand the
2041 tweaks to various things you need. At this point in the life
2042 cycle of current, things change often and you are on your own
2043 to cope. The defaults can also change, so please read ALL of
2044 the UPDATING entries.
2046 Also, if you are tracking -current, you must be subscribed to
2047 freebsd-current@freebsd.org. Make sure that before you update
2048 your sources that you have read and understood all the recent
2049 messages there. If in doubt, please track -stable which has
2050 much fewer pitfalls.
2052 [1] If you have third party modules, such as vmware, you
2053 should disable them at this point so they don't crash your
2056 [3] From the bootblocks, boot -s, and then do
2061 adjkerntz -i # if CMOS is wall time
2062 Also, when doing a major release upgrade, it is required that
2063 you boot into single user mode to do the installworld.
2065 [4] Note: This step is non-optional. Failure to do this step
2066 can result in a significant reduction in the functionality of the
2067 system. Attempting to do it by hand is not recommended and those
2068 that pursue this avenue should read this file carefully, as well
2069 as the archives of freebsd-current and freebsd-hackers mailing lists
2070 for potential gotchas. The -U option is also useful to consider.
2071 See mergemaster(8) for more information.
2073 [5] Usually this step is a noop. However, from time to time
2074 you may need to do this if you get unknown user in the following
2075 step. It never hurts to do it all the time. You may need to
2076 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2077 install) after the buildworld before this step if you last updated
2078 from current before 20130425 or from -stable before 20130430.
2080 [6] This only deletes old files and directories. Old libraries
2081 can be deleted by "make delete-old-libs", but you have to make
2082 sure that no program is using those libraries anymore.
2084 [8] In order to have a kernel that can run the 4.x binaries needed to
2085 do an installworld, you must include the COMPAT_FREEBSD4 option in
2086 your kernel. Failure to do so may leave you with a system that is
2087 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2088 required to run the 5.x binaries on more recent kernels. And so on
2089 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2091 Make sure that you merge any new devices from GENERIC since the
2092 last time you updated your kernel config file.
2094 [9] When checking out sources, you must include the -P flag to have
2095 cvs prune empty directories.
2097 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2098 "?=" instead of the "=" assignment operator, so that buildworld can
2099 override the CPUTYPE if it needs to.
2101 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2102 not on the command line, or in /etc/make.conf. buildworld will
2103 warn if it is improperly defined.
2106 This file contains a list, in reverse chronological order, of major
2107 breakages in tracking -current. It is not guaranteed to be a complete
2108 list of such breakages, and only contains entries since October 10, 2007.
2109 If you need to see UPDATING entries from before that date, you will need
2110 to fetch an UPDATING file from an older FreeBSD release.
2112 Copyright information:
2114 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2116 Redistribution, publication, translation and use, with or without
2117 modification, in full or in part, in any form or format of this
2118 document are permitted without further permission from the author.
2120 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2121 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2122 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2123 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2124 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2125 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2126 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2127 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2128 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2129 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2130 POSSIBILITY OF SUCH DAMAGE.
2132 Contact Warner Losh if you have any questions about your use of