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 Support for libwrap (TCP wrappers) in rpcbind was disabled by default
36 to improve performance. To re-enable it, if needed, run rpcbind
37 with command line option -W.
40 Switched back to the GPL dtc compiler due to updates in the upstream
41 dts files not being supported by the BSDL dtc compiler. You will need
42 to rebuild your kernel toolchain to pick up the new compiler. Core dumps
43 may result while building dtb files during a kernel build if you fail
44 to do so. Set WITHOUT_GPL_DTC if you require the BSDL compiler.
47 Clang and llvm have been upgraded to 3.4 release.
50 The nve(4) driver has been removed. Please use the nfe(4) driver
51 for NVIDIA nForce MCP Ethernet adapters instead.
54 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
55 This could cause certain C++ applications using shared libraries built
56 against the previous version of libc++ to crash. The incompatibility
57 has now been fixed, but any C++ applications or shared libraries built
58 between r261283 and r261801 should be recompiled.
61 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
62 capability mode support. Please note that enabling the feature in
63 kernel is still highly recommended.
66 OpenSSH is now built with sandbox support, and will use sandbox as
67 the default privilege separation method. This requires Capsicum
68 capability mode support in kernel.
71 The libelf and libdwarf libraries have been updated to newer
72 versions from upstream. Shared library version numbers for
73 these two libraries were bumped. Any ports or binaries
74 requiring these two libraries should be recompiled.
75 __FreeBSD_version is bumped to 1100006.
78 If a Makefile in a tests/ directory was auto-generating a Kyuafile
79 instead of providing an explicit one, this would prevent such
80 Makefile from providing its own Kyuafile in the future during
81 NO_CLEAN builds. This has been fixed in the Makefiles but manual
82 intervention is needed to clean an objdir if you use NO_CLEAN:
83 # find /usr/obj -name Kyuafile | xargs rm -f
86 The behavior of gss_pseudo_random() for the krb5 mechanism
87 has changed, for applications requesting a longer random string
88 than produced by the underlying enctype's pseudo-random() function.
89 In particular, the random string produced from a session key of
90 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
91 be different at the 17th octet and later, after this change.
92 The counter used in the PRF+ construction is now encoded as a
93 big-endian integer in accordance with RFC 4402.
94 __FreeBSD_version is bumped to 1100004.
97 The WITHOUT_ATF build knob has been removed and its functionality
98 has been subsumed into the more generic WITHOUT_TESTS. If you were
99 using the former to disable the build of the ATF libraries, you
100 should change your settings to use the latter.
103 The default version of mtree is nmtree which is obtained from
104 NetBSD. The output is generally the same, but may vary
105 slightly. If you found you need identical output adding
106 "-F freebsd9" to the command line should do the trick. For the
107 time being, the old mtree is available as fmtree.
110 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
111 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
112 1.1.4_8 and verify bsdyml not linked in, before running "make
114 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
116 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
119 The rc.d/jail script has been updated to support jail(8)
120 configuration file. The "jail_<jname>_*" rc.conf(5) variables
121 for per-jail configuration are automatically converted to
122 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
123 This is transparently backward compatible. See below about some
124 incompatibilities and rc.conf(5) manual page for more details.
126 These variables are now deprecated in favor of jail(8) configuration
127 file. One can use "rc.d/jail config <jname>" command to generate
128 a jail(8) configuration file in /var/run/jail.<jname>.conf without
129 running the jail(8) utility. The default pathname of the
130 configuration file is /etc/jail.conf and can be specified by
131 using $jail_conf or $jail_<jname>_conf variables.
133 Please note that jail_devfs_ruleset accepts an integer at
134 this moment. Please consider to rewrite the ruleset name
138 BIND has been removed from the base system. If all you need
139 is a local resolver, simply enable and start the local_unbound
140 service instead. Otherwise, several versions of BIND are
141 available in the ports tree. The dns/bind99 port is one example.
143 With this change, nslookup(1) and dig(1) are no longer in the base
144 system. Users should instead use host(1) and drill(1) which are
145 in the base system. Alternatively, nslookup and dig can
146 be obtained by installing the dns/bind-tools port.
149 With the addition of unbound(8), a new unbound user is now
150 required during installworld. "mergemaster -p" can be used to
151 add the user prior to installworld, as documented in the handbook.
154 OpenSSH is now built with DNSSEC support, and will by default
155 silently trust signed SSHFP records. This can be controlled with
156 the VerifyHostKeyDNS client configuration setting. DNSSEC support
157 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
160 The GNU Compiler Collection and C++ standard library (libstdc++)
161 are no longer built by default on platforms where clang is the system
162 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
166 The PROCDESC kernel option is now part of the GENERIC kernel
167 configuration and is required for the rwhod(8) to work.
168 If you are using custom kernel configuration, you should include
172 The API and ABI related to the Capsicum framework was modified
173 in backward incompatible way. The userland libraries and programs
174 have to be recompiled to work with the new kernel. This includes the
175 following libraries and programs, but the whole buildworld is
176 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
177 kdump, procstat, rwho, rwhod, uniq.
180 AES-NI intrinsic support has been added to gcc. The AES-NI module
181 has been updated to use this support. A new gcc is required to build
182 the aesni module on both i386 and amd64.
185 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
186 Thus "device padlock_rng" and "device rdrand_rng" should be
187 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
190 WITH_ICONV has been split into two feature sets. WITH_ICONV now
191 enables just the iconv* functionality and is now on by default.
192 WITH_LIBICONV_COMPAT enables the libiconv api and link time
193 compatability. Set WITHOUT_ICONV to build the old way.
194 If you have been using WITH_ICONV before, you will very likely
195 need to turn on WITH_LIBICONV_COMPAT.
198 INVARIANTS option now enables DEBUG for code with OpenSolaris and
199 Illumos origin, including ZFS. If you have INVARIANTS in your
200 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
202 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
203 locks if WITNESS option was set. Because that generated a lot of
204 witness(9) reports and all of them were believed to be false
205 positives, this is no longer done. New option OPENSOLARIS_WITNESS
206 can be used to achieve the previous behavior.
209 Timer values in IPv6 data structures now use time_uptime instead
210 of time_second. Although this is not a user-visible functional
211 change, userland utilities which directly use them---ndp(8),
212 rtadvd(8), and rtsold(8) in the base system---need to be updated
216 find -delete can now delete the pathnames given as arguments,
217 instead of only files found below them or if the pathname did
218 not contain any slashes. Formerly, the following error message
221 find: -delete: <path>: relative path potentially not safe
223 Deleting the pathnames given as arguments can be prevented
224 without error messages using -mindepth 1 or by changing
225 directory and passing "." as argument to find. This works in the
226 old as well as the new version of find.
229 Behavior of devfs rules path matching has been changed.
230 Pattern is now always matched against fully qualified devfs
231 path and slash characters must be explicitly matched by
232 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
233 subdirectories must be reviewed.
236 The default ARM ABI has changed to the ARM EABI. The old ABI is
237 incompatible with the ARM EABI and all programs and modules will
238 need to be rebuilt to work with a new kernel.
240 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
242 NOTE: Support for the old ABI will be removed in the future and
243 users are advised to upgrade.
246 pkg_install has been disconnected from the build if you really need it
247 you should add WITH_PKGTOOLS in your src.conf(5).
250 Most of network statistics structures were changed to be able
251 keep 64-bits counters. Thus all tools, that work with networking
252 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
255 Fix targets that run multiple make's to use && rather than ;
256 so that subsequent steps depend on success of previous.
258 NOTE: if building 'universe' with -j* on stable/8 or stable/9
259 it would be better to start the build using bmake, to avoid
260 overloading the machine.
263 Fix a bug that allowed a tracing process (e.g. gdb) to write
264 to a memory-mapped file in the traced process's address space
265 even if neither the traced process nor the tracing process had
266 write access to that file.
269 CVS has been removed from the base system. An exact copy
270 of the code is available from the devel/cvs port.
273 Some people report the following error after the switch to bmake:
275 make: illegal option -- J
276 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
278 *** [buildworld] Error code 2
280 this likely due to an old instance of make in
281 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
282 which src/Makefile will use that blindly, if it exists, so if
283 you see the above error:
285 rm -rf `make -V MAKEPATH`
290 Use bmake by default.
291 Whereas before one could choose to build with bmake via
292 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
293 make. The goal is to remove these knobs for 10-RELEASE.
295 It is worth noting that bmake (like gmake) treats the command
296 line as the unit of failure, rather than statements within the
297 command line. Thus '(cd some/where && dosomething)' is safer
298 than 'cd some/where; dosomething'. The '()' allows consistent
299 behavior in parallel build.
302 Fix a bug that allows NFS clients to issue READDIR on files.
305 The WITHOUT_IDEA option has been removed because
306 the IDEA patent expired.
309 The sysctl which controls TRIM support under ZFS has been renamed
310 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
314 The mergemaster command now uses the default MAKEOBJDIRPREFIX
315 rather than creating it's own in the temporary directory in
316 order allow access to bootstrapped versions of tools such as
317 install and mtree. When upgrading from version of FreeBSD where
318 the install command does not support -l, you will need to
319 install a new mergemaster command if mergemaster -p is required.
320 This can be accomplished with the command (cd src/usr.sbin/mergemaster
324 Legacy ATA stack, disabled and replaced by new CAM-based one since
325 FreeBSD 9.0, completely removed from the sources. Kernel modules
326 atadisk and atapi*, user-level tools atacontrol and burncd are
327 removed. Kernel option `options ATA_CAM` is now permanently enabled
331 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
332 and socketpair(2). Software, in particular Kerberos, may
333 automatically detect and use these during building. The resulting
334 binaries will not work on older kernels.
337 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
338 information, see the respective 20130304 entry).
341 Recent commits to callout(9) changed the size of struct callout,
342 so the KBI is probably heavily disturbed. Also, some functions
343 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
344 by macros. Every kernel module using it won't load, so rebuild
347 The ctl device has been re-enabled in GENERIC for i386 and amd64,
348 but does not initialize by default (because of the new CTL_DISABLE
349 option) to save memory. To re-enable it, remove the CTL_DISABLE
350 option from the kernel config file or set kern.cam.ctl.disable=0
351 in /boot/loader.conf.
354 The ctl device has been disabled in GENERIC for i386 and amd64.
355 This was done due to the extra memory being allocated at system
356 initialisation time by the ctl driver which was only used if
357 a CAM target device was created. This makes a FreeBSD system
358 unusable on 128MB or less of RAM.
361 A new compression method (lz4) has been merged to -HEAD. Please
362 refer to zpool-features(7) for more information.
364 Please refer to the "ZFS notes" section of this file for information
365 on upgrading boot ZFS pools.
368 A BSD-licensed patch(1) variant has been added and is installed
369 as bsdpatch, being the GNU version the default patch.
370 To inverse the logic and use the BSD-licensed one as default,
371 while having the GNU version installed as gnupatch, rebuild
372 and install world with the WITH_BSD_PATCH knob set.
375 Due to the use of the new -l option to install(1) during build
376 and install, you must take care not to directly set the INSTALL
377 make variable in your /etc/make.conf, /etc/src.conf, or on the
378 command line. If you wish to use the -C flag for all installs
379 you may be able to add INSTALL+=-C to /etc/make.conf or
383 The install(1) option -M has changed meaning and now takes an
384 argument that is a file or path to append logs to. In the
385 unlikely event that -M was the last option on the command line
386 and the command line contained at least two files and a target
387 directory the first file will have logs appended to it. The -M
388 option served little practical purpose in the last decade so its
389 use is expected to be extremely rare.
392 After switching to Clang as the default compiler some users of ZFS
393 on i386 systems started to experience stack overflow kernel panics.
394 Please consider using 'options KSTACK_PAGES=4' in such configurations.
397 GEOM_LABEL now mangles label names read from file system metadata.
398 Mangling affect labels containing spaces, non-printable characters,
399 '%' or '"'. Device names in /etc/fstab and other places may need to
403 By default, only the 10 most recent kernel dumps will be saved. To
404 restore the previous behaviour (no limit on the number of kernel dumps
405 stored in the dump directory) add the following line to /etc/rc.conf:
410 With the addition of auditdistd(8), a new auditdistd user is now
411 required during installworld. "mergemaster -p" can be used to
412 add the user prior to installworld, as documented in the handbook.
415 The sin6_scope_id member variable in struct sockaddr_in6 is now
416 filled by the kernel before passing the structure to the userland via
417 sysctl or routing socket. This means the KAME-specific embedded scope
418 id in sin6_addr.s6_addr[2] is always cleared in userland application.
419 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
420 __FreeBSD_version is bumped to 1000025.
423 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
424 This means that the world and kernel will be compiled with clang
425 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
426 and /usr/bin/cpp. To disable this behavior and revert to building
427 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
428 of current may need to bootstrap WITHOUT_CLANG first if the clang
429 build fails (its compatibility window doesn't extend to the 9 stable
433 The IPFIREWALL_FORWARD kernel option has been removed. Its
434 functionality now turned on by default.
437 The ZERO_COPY_SOCKET kernel option has been removed and
438 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
439 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
440 mechanism which is not safe and may result in kernel crashes.
441 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
442 driver supports disposeable external page sized mbuf storage.
443 Proper replacements for both zero-copy mechanisms are under
444 consideration and will eventually lead to complete removal
445 of the two kernel options.
448 The IPv4 network stack has been converted to network byte
449 order. The following modules need to be recompiled together
450 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
451 pf(4), ipfw(4), ng_ipfw(4), stf(4).
454 Support for non-MPSAFE filesystems was removed from VFS. The
455 VFS_VERSION was bumped, all filesystem modules shall be
459 All the non-MPSAFE filesystems have been disconnected from
460 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
461 portalfs, smbfs, xfs.
464 The interface cloning API and ABI has changed. The following
465 modules need to be recompiled together with kernel:
466 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
467 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
468 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
471 The sdhci driver was split in two parts: sdhci (generic SD Host
472 Controller logic) and sdhci_pci (actual hardware driver).
473 No kernel config modifications are required, but if you
474 load sdhc as a module you must switch to sdhci_pci instead.
477 Import the FUSE kernel and userland support into base system.
480 The GNU sort(1) program has been removed since the BSD-licensed
481 sort(1) has been the default for quite some time and no serious
482 problems have been reported. The corresponding WITH_GNU_SORT
486 The pfil(9) API/ABI for AF_INET family has been changed. Packet
487 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
491 The net80211(4) ABI has been changed to allow for improved driver
492 PS-POLL and power-save support. All wireless drivers need to be
493 recompiled to work with the new kernel.
496 The random(4) support for the VIA hardware random number
497 generator (`PADLOCK') is no longer enabled unconditionally.
498 Add the padlock_rng device in the custom kernel config if
499 needed. The GENERIC kernels on i386 and amd64 do include the
500 device, so the change only affects the custom kernel
504 The pf(4) packet filter ABI has been changed. pfctl(8) and
505 snmp_pf module need to be recompiled to work with new kernel.
508 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
509 to -HEAD. Pools that have empty_bpobj in active state can not be
510 imported read-write with ZFS implementations that do not support
511 this feature. For more information read the zpool-features(5)
515 The sparc64 ZFS loader has been changed to no longer try to auto-
516 detect ZFS providers based on diskN aliases but now requires these
517 to be explicitly listed in the OFW boot-device environment variable.
520 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
521 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
522 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
525 The following sysctls and tunables have been renamed for consistency
526 with other variables:
527 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
528 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
531 The sort utility has been replaced with BSD sort. For now, GNU sort
532 is also available as "gnusort" or the default can be set back to
533 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
534 installed as "bsdsort".
537 A new version of ZFS (pool version 5000) has been merged to -HEAD.
538 Starting with this version the old system of ZFS pool versioning
539 is superseded by "feature flags". This concept enables forward
540 compatibility against certain future changes in functionality of ZFS
541 pools. The first read-only compatible "feature flag" for ZFS pools
542 is named "com.delphix:async_destroy". For more information
543 read the new zpool-features(5) manual page.
544 Please refer to the "ZFS notes" section of this file for information
545 on upgrading boot ZFS pools.
548 The malloc(3) implementation embedded in libc now uses sources imported
549 as contrib/jemalloc. The most disruptive API change is to
550 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
551 delete it prior to installworld, and optionally re-create it using the
552 new format after rebooting. See malloc.conf(5) for details
553 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
557 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
558 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
559 now spelled mips. This is to aid compatibility with third-party
560 software that expects this naming scheme in uname(3). Little-endian
561 settings are unchanged. If you are updating a big-endian mips64 machine
562 from before this change, you may need to set MACHINE_ARCH=mips64 in
563 your environment before the new build system will recognize your machine.
566 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
570 Now unix domain sockets behave "as expected" on nullfs(5). Previously
571 nullfs(5) did not pass through all behaviours to the underlying layer,
572 as a result if we bound to a socket on the lower layer we could connect
573 only to the lower path; if we bound to the upper layer we could connect
574 only to the upper path. The new behavior is one can connect to both the
575 lower and the upper paths regardless what layer path one binds to.
578 The getifaddrs upgrade path broken with 20111215 has been restored.
579 If you have upgraded in between 20111215 and 20120209 you need to
580 recompile libc again with your kernel. You still need to recompile
581 world to be able to configure CARP but this restriction already
585 The set_rcvar() function has been removed from /etc/rc.subr. All
586 base and ports rc.d scripts have been updated, so if you have a
587 port installed with a script in /usr/local/etc/rc.d you can either
588 hand-edit the rcvar= line, or reinstall the port.
590 An easy way to handle the mass-update of /etc/rc.d:
591 rm /etc/rc.d/* && mergemaster -i
594 panic(9) now stops other CPUs in the SMP systems, disables interrupts
595 on the current CPU and prevents other threads from running.
596 This behavior can be reverted using the kern.stop_scheduler_on_panic
598 The new behavior can be incompatible with kern.sync_on_panic.
601 The carp(4) facility has been changed significantly. Configuration
602 of the CARP protocol via ifconfig(8) has changed, as well as format
603 of CARP events submitted to devd(8) has changed. See manual pages
604 for more information. The arpbalance feature of carp(4) is currently
605 not supported anymore.
607 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
608 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
609 need to be recompiled.
612 The acpi_wmi(4) status device /dev/wmistat has been renamed to
616 The option VFS_ALLOW_NONMPSAFE option has been added in order to
617 explicitely support non-MPSAFE filesystems.
618 It is on by default for all supported platform at this present
622 The broken amd(4) driver has been replaced with esp(4) in the amd64,
623 i386 and pc98 GENERIC kernel configuration files.
626 sysinstall has been removed
629 The stable/9 branch created in subversion. This corresponds to the
630 RELENG_9 branch in CVS.
633 This commit modifies vfs_register() so that it uses a hash
634 calculation to set vfc_typenum, which is enabled by default.
635 The first time a system is booted after this change, the
636 vfc_typenum values will change for all file systems. The
637 main effect of this is a change to the NFS server file handles
638 for file systems that use vfc_typenum in their fsid, such as ZFS.
639 It will, however, prevent vfc_typenum from changing when file
640 systems are loaded in a different order for subsequent reboots.
641 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
642 until you are ready to remount all NFS clients after a reboot.
645 Bump the shared library version numbers for libraries that
646 do not use symbol versioning, have changed the ABI compared
647 to stable/8 and which shared library version was not bumped.
648 Done as part of 9.0-RELEASE cycle.
651 During the merge of Capsicum features, the fget(9) KPI was modified.
652 This may require the rebuilding of out-of-tree device drivers --
653 issues have been reported specifically with the nVidia device driver.
654 __FreeBSD_version is bumped to 900041.
656 Also, there is a period between 20110811 and 20110814 where the
657 special devices /dev/{stdin,stdout,stderr} did not work correctly.
658 Building world from a kernel during that window may not work.
661 The packet filter (pf) code has been updated to OpenBSD 4.5.
662 You need to update userland tools to be in sync with kernel.
663 This update breaks backward compatibility with earlier pfsync(4)
664 versions. Care must be taken when updating redundant firewall setups.
667 The following sysctls and tunables are retired on x86 platforms:
669 machdep.hlt_logical_cpus
670 The following sysctl is retired:
671 machdep.hyperthreading_allowed
672 The sysctls were supposed to provide a way to dynamically offline and
673 online selected CPUs on x86 platforms, but the implementation has not
674 been reliable especially with SCHED_ULE scheduler.
675 machdep.hyperthreading_allowed tunable is still available to ignore
676 hyperthreading CPUs at OS level.
677 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
678 where X is an APIC ID of a CPU. Be advised, though, that disabling
679 CPUs in non-uniform fashion will result in non-uniform topology and
680 may lead to sub-optimal system performance with SCHED_ULE, which is
684 cpumask_t type is retired and cpuset_t is used in order to describe
688 Changes to ifconfig(8) for dynamic address family detection mandate
689 that you are running a kernel of 20110525 or later. Make sure to
690 follow the update procedure to boot a new kernel before installing
694 Support for sun4v architecture is officially dropped
697 Several KPI breaking changes have been committed to the mii(4) layer,
698 the PHY drivers and consequently some Ethernet drivers using mii(4).
699 This means that miibus.ko and the modules of the affected Ethernet
700 drivers need to be recompiled.
702 Note to kernel developers: Given that the OUI bit reversion problem
703 was fixed as part of these changes all mii(4) commits related to OUIs,
704 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
705 handling, no longer can be merged verbatim to stable/8 and previous
709 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
710 into their kernel configurations along with 'device pci'.
713 The default NFS client is now the new NFS client, so fstype "newnfs"
714 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
715 Although mounts via fstype "nfs" will usually work without userland
716 changes, it is recommended that the mount(8) and mount_nfs(8)
717 commands be rebuilt from sources and that a link to mount_nfs called
718 mount_oldnfs be created. The new client is compiled into the
719 kernel with "options NFSCL" and this is needed for diskless root
720 file systems. The GENERIC kernel configs have been changed to use
721 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
722 To use the regular/old client, you can "mount -t oldnfs ...". For
723 a diskless root file system, you must also include a line like:
725 vfs.root.mountfrom="oldnfs:"
727 in the boot/loader.conf on the root fs on the NFS server to make
728 a diskless root fs use the old client.
731 The GENERIC kernels for all architectures now default to the new
732 CAM-based ATA stack. It means that all legacy ATA drivers were
733 removed and replaced by respective CAM drivers. If you are using
734 ATA device names in /etc/fstab or other places, make sure to update
735 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
736 where 'Y's are the sequential numbers starting from zero for each type
737 in order of detection, unless configured otherwise with tunables,
738 see cam(4)). There will be symbolic links created in /dev/ to map
739 old adX devices to the respective adaY. They should provide basic
740 compatibility for file systems mounting in most cases, but they do
741 not support old user-level APIs and do not have respective providers
742 in GEOM. Consider using updated management tools with new device names.
744 It is possible to load devices ahci, ata, siis and mvs as modules,
745 but option ATA_CAM should remain in kernel configuration to make ata
746 module work as CAM driver supporting legacy ATA controllers. Device ata
747 still can be used in modular fashion (atacore + ...). Modules atadisk
748 and atapi* are not used and won't affect operation in ATA_CAM mode.
749 Note that to use CAM-based ATA kernel should include CAM devices
750 scbus, pass, da (or explicitly ada), cd and optionally others. All of
751 them are parts of the cam module.
753 ataraid(4) functionality is now supported by the RAID GEOM class.
754 To use it you can load geom_raid kernel module and use graid(8) tool
755 for management. Instead of /dev/arX device names, use /dev/raid/rX.
757 No kernel config options or code have been removed, so if a problem
758 arises, please report it and optionally revert to the old ATA stack.
759 In order to do it you can remove from the kernel config:
764 , and instead add back:
765 device atadisk # ATA disk drives
766 device ataraid # ATA RAID drives
767 device atapicd # ATAPI CDROM drives
768 device atapifd # ATAPI floppy drives
769 device atapist # ATAPI tape drives
772 The default NFS server has been changed to the new server, which
773 was referred to as the experimental server. If you need to switch
774 back to the old NFS server, you must now put the "-o" option on
775 both the mountd and nfsd commands. This can be done using the
776 mountd_flags and nfs_server_flags rc.conf variables until an
777 update to the rc scripts is committed, which is coming soon.
780 The GNU Objective-C runtime library (libobjc), and other Objective-C
781 related components have been removed from the base system. If you
782 require an Objective-C library, please use one of the available ports.
785 ath(4) has been split into bus- and device- modules. if_ath contains
786 the HAL, the TX rate control and the network device code. if_ath_pci
787 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
788 contains the AHB glue. Users need to load both if_ath_pci and if_ath
789 in order to use ath on everything else.
791 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
792 need to load if_ath and if_ath_pci for ath(4) operation.
795 As part of the replacement of sysinstall, the process of building
796 release media has changed significantly. For details, please re-read
797 release(7), which has been updated to reflect the new build process.
800 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
801 is the last available version under GPLv2. It brings a number of new
802 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
803 4.1 and SSE 4.2), better support for powerpc64, a number of new
804 directives, and lots of other small improvements. See the ChangeLog
805 file in contrib/binutils for the full details.
808 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
809 compliant, and will now use half of hash for authentication.
810 This will break interoperability with all stacks (including all
811 actual FreeBSD versions) who implement
812 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
814 The only workaround with such peers is to use another HMAC
815 algorithm for IPsec ("phase 2") authentication.
818 Remove the uio_yield prototype and symbol. This function has
819 been misnamed since it was introduced and should not be
820 globally exposed with this name. The equivalent functionality
821 is now available using kern_yield(curthread->td_user_pri).
822 The function remains undocumented.
825 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
826 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
827 for scalar sysctls is defined but disabled. Code that needs
828 UQUAD to pass the type checking that must compile on older
829 systems where the define is not present can check against
830 __FreeBSD_version >= 900030.
832 The system dialog(1) has been replaced with a new version previously
833 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
834 with the previous version, but the libdialog associated with it has
835 a largely incompatible API. As such, the original version of libdialog
836 will be kept temporarily as libodialog, until its base system consumers
837 are replaced or updated. Bump __FreeBSD_version to 900030.
840 If you are trying to run make universe on a -stable system, and you get
841 the following warning:
842 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
843 unknown. config(8) likely too old."
844 or something similar to it, then you must upgrade your -stable system
845 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
846 stable/8) or build the config from the latest stable/8 branch and
847 install it on your system.
849 Prior to this date, building a current universe on 8-stable system from
850 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
851 error in the first kernel build phase. A new config on those old
852 systems will fix that problem for older versions of -current.
855 The TCP stack has been modified to allow Khelp modules to interact with
856 it via helper hook points and store per-connection data in the TCP
857 control block. Bump __FreeBSD_version to 900029. User space tools that
858 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
862 Generic IEEE 802.3 annex 31B full duplex flow control support has been
863 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
864 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
865 to take advantage of it instead of using custom implementations. This
866 means that these drivers now no longer unconditionally advertise
867 support for flow control but only do so if flow control is a selected
868 media option. This was implemented in the generic support that way in
869 order to allow flow control to be switched on and off via ifconfig(8)
870 with the PHY specific default to typically off in order to protect
871 from unwanted effects. Consequently, if you used flow control with
872 one of the above mentioned drivers you now need to explicitly enable
874 ifconfig bge0 media auto mediaopt flowcontrol
876 Along with the above mentioned changes generic support for setting
877 1000baseT master mode also has been added and brgphy(4), ciphy(4),
878 e1000phy(4) as well as ip1000phy(4) have been converted to take
879 advantage of it. This means that these drivers now no longer take the
880 link0 parameter for selecting master mode but the master media option
881 has to be used instead, for example like in the following:
882 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
884 Selection of master mode now is also available with all other PHY
885 drivers supporting 1000baseT.
888 The TCP stack has received a significant update to add support for
889 modularised congestion control and generally improve the clarity of
890 congestion control decisions. Bump __FreeBSD_version to 900025. User
891 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
892 sockstat) need to be recompiled.
895 The man(1) utility has been replaced by a new version that no longer
896 uses /etc/manpath.config. Please consult man.conf(5) for how to
897 migrate local entries to the new format.
900 The copyright strings printed by login(1) and sshd(8) at the time of a
901 new connection have been removed to follow other operating systems and
905 A workaround for a fixed ld bug has been removed in kernel code,
906 so make sure that your system ld is built from sources after
907 revision 210245 from 2010-07-19 (r211583 if building head kernel
908 on stable/8, r211584 for stable/7; both from 2010-08-21).
909 A symptom of incorrect ld version is different addresses for
910 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
913 The $ipv6_prefer variable in rc.conf(5) has been split into
914 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
916 The $ip6addrctl_policy is a variable to choose a pre-defined
917 address selection policy set by ip6addrctl(8). A value
918 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
921 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
922 flag (see an entry of 20090926) is set on an interface with no
923 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
924 security reason. If you want IPv6 link-local address on all
925 interfaces by default, set this to "YES".
927 The old ipv6_prefer="YES" is equivalent to
928 ipv6_activate_all_interfaces="YES" and
929 ip6addrctl_policy="ipv6_prefer".
932 DTrace has grown support for userland tracing. Due to this, DTrace is
933 now i386 and amd64 only.
934 dtruss(1) is now installed by default on those systems and a new
935 kernel module is needed for userland tracing: fasttrap.
936 No changes to your kernel config file are necessary to enable
937 userland tracing, but you might consider adding 'STRIP=' and
938 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
939 to have informative userland stack traces in DTrace (ustack).
942 The acpi_aiboost(4) driver has been removed in favor of the new
943 aibs(4) driver. You should update your kernel configuration file.
946 BSD grep has been imported to the base system and it is built by
947 default. It is completely BSD licensed, highly GNU-compatible, uses
948 less memory than its GNU counterpart and has a small codebase.
949 However, it is slower than its GNU counterpart, which is mostly
950 noticeable for larger searches, for smaller ones it is measurable
951 but not significant. The reason is complex, the most important factor
952 is that we lack a modern and efficient regex library and GNU
953 overcomes this by optimizing the searches internally. Future work
954 on improving the regex performance is planned, for the meantime,
955 users that need better performance, can build GNU grep instead by
956 setting the WITH_GNU_GREP knob.
959 Due to the import of powerpc64 support, all existing powerpc kernel
960 configuration files must be updated with a machine directive like this:
961 machine powerpc powerpc
963 In addition, an updated config(8) is required to build powerpc kernels
967 A new version of ZFS (version 15) has been merged to -HEAD.
968 This version uses a python library for the following subcommands:
969 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
970 For full functionality of these commands the following port must
971 be installed: sysutils/py-zfs
974 'vm_page's are now hashed by physical address to an array of mutexes.
975 Currently this is only used to serialize access to hold_count. Over
976 time the page queue mutex will be peeled away. This changes the size
977 of pmap on every architecture. And requires all callers of vm_page_hold
978 and vm_page_unhold to be updated.
981 WITH_CTF can now be specified in src.conf (not recommended, there
982 are some problems with static executables), make.conf (would also
983 affect ports which do not use GNU make and do not override the
984 compile targets) or in the kernel config (via "makeoptions
986 When WITH_CTF was specified there before this was silently ignored,
987 so make sure that WITH_CTF is not used in places which could lead
988 to unwanted behavior.
991 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
992 to allow 32-bit compatibility on non-x86 platforms. All kernel
993 configurations on amd64 and ia64 platforms using these options must
994 be modified accordingly.
997 The utmp user accounting database has been replaced with utmpx,
998 the user accounting interface standardized by POSIX.
999 Unfortunately the semantics of utmp and utmpx don't match,
1000 making it practically impossible to support both interfaces.
1001 The user accounting database is used by tools like finger(1),
1002 last(1), talk(1), w(1) and ac(8).
1004 All applications in the base system use utmpx. This means only
1005 local binaries (e.g. from the ports tree) may still use these
1006 utmp database files. These applications must be rebuilt to make
1009 After the system has been upgraded, it is safe to remove the old
1010 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1011 assuming their contents is of no importance anymore. Old wtmp
1012 databases can only be used by last(1) and ac(8) after they have
1013 been converted to the new format using wtmpcvt(1).
1016 Introduce the kernel thread "deadlock resolver" (which can be enabled
1017 via the DEADLKRES option, see NOTES for more details) and the
1018 sleepq_type() function for sleepqueues.
1021 The rc.firewall and rc.firewall6 were unified, and
1022 rc.firewall6 and rc.d/ip6fw were removed.
1023 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1024 variables are obsoleted. Instead, the following new rc
1025 variables are added to rc.d/ipfw:
1027 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1028 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1029 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1031 The meanings correspond to the relevant IPv4 variables.
1037 The default terminal emulation for syscons(4) has been changed
1038 from cons25 to xterm on all platforms except pc98. This means
1039 that the /etc/ttys file needs to be updated to ensure correct
1040 operation of applications on the console.
1042 The terminal emulation style can be toggled per window by using
1043 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1044 options can be used to change the compile-time default back to
1047 To prevent graphical artifacts, make sure the TERM environment
1048 variable is set to match the terminal emulation that is being
1049 performed by syscons(4).
1052 The layout of the structure ieee80211req_scan_result has changed.
1053 Applications that require wireless scan results (e.g. ifconfig(8))
1054 from net80211 need to be recompiled.
1056 Applications such as wpa_supplicant(8) may require a full world
1057 build without using NO_CLEAN in order to get synchronized with the
1061 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1062 There's one kernel module for each firmware. Adding "device iwnfw"
1063 to the kernel configuration file means including all three firmware
1064 images inside the kernel. If you want to include just the one for
1065 your wireless card, use the devices iwn4965fw, iwn5000fw or
1069 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1070 into rc.d/netif. The changes are the following:
1072 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1073 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1074 Note that both variables need the "inet6" keyword at the head.
1076 Do not set $ipv6_network_interfaces manually if you do not
1077 understand what you are doing. It is not needed in most cases.
1079 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1082 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1083 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1085 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1086 all configured interfaces have "inet6 accept_rtadv" in the
1087 $ifconfig_IF_ipv6. These are for backward compatibility.
1089 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1090 functionality of interfaces with no corresponding
1091 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1092 and the default address selection policy of ip6addrctl(8)
1093 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1094 Note that if you want to configure IPv6 functionality on the
1095 disabled interfaces after boot, first you need to clear the flag by
1096 using ifconfig(8) like:
1098 ifconfig em0 inet6 -ifdisabled
1100 If YES, the default address selection policy is set as
1103 The default value of $ipv6_prefer is NO.
1105 4. If your system need to receive Router Advertisement messages,
1106 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1107 scripts automatically invoke rtsol(8) when the interface becomes
1108 UP. The Router Advertisement messages are used for SLAAC
1109 (State-Less Address AutoConfiguration).
1112 802.11s D3.03 support was committed. This is incompatible with the
1113 previous code, which was based on D3.0.
1116 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1117 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1118 control whether accepting Router Advertisement messages or not.
1119 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1120 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1121 The ifconfig(8) utility now supports these flags.
1124 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1125 mount(8) and -a option for df(1) to see them.
1128 The old tunable hw.bus.devctl_disable has been superseded by
1129 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1130 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1134 Remove the option STOP_NMI. The default action is now to use NMI only
1135 for KDB via the newly introduced function stop_cpus_hard() and
1136 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1139 The stable/8 branch created in subversion. This corresponds to the
1140 RELENG_8 branch in CVS.
1143 Bump the shared library version numbers for all libraries that do not
1144 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1145 __FreeBSD_version to 800105.
1148 Due to changes in the implementation of virtual network stack support,
1149 all network-related kernel modules must be recompiled. As this change
1150 breaks the ABI, bump __FreeBSD_version to 800104.
1153 The TOE interface to the TCP syncache has been modified to remove
1154 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1155 The cxgb driver is the only TOE consumer affected by this change, and
1156 needs to be recompiled along with the kernel. As this change breaks
1157 the ABI, bump __FreeBSD_version to 800103.
1160 Padding has been added to struct tcpcb, sackhint and tcpstat in
1161 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1162 maintaining the ABI. However, this change breaks the ABI, so bump
1163 __FreeBSD_version to 800102. User space tools that rely on the size of
1164 any of these structs (e.g. sockstat) need to be recompiled.
1167 The NFS_LEGACYRPC option has been removed along with the old kernel
1168 RPC implementation that this option selected. Kernel configurations
1169 may need to be adjusted.
1172 The network interface device nodes at /dev/net/<interface> have been
1173 removed. All ioctl operations can be performed the normal way using
1174 routing sockets. The kqueue functionality can generally be replaced
1175 with routing sockets.
1178 The documentation from the FreeBSD Documentation Project (Handbook,
1179 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1180 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1183 The ABI of various structures related to the SYSV IPC API have been
1184 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1185 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1189 Layout of struct vnet has changed as routing related variables were
1190 moved to their own Vimage module. Modules need to be recompiled. Bump
1191 __FreeBSD_version to 800099.
1194 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1195 respectively. As long as no more than 16 groups per process are used,
1196 no changes should be visible. When more than 16 groups are used, old
1197 binaries may fail if they call getgroups() or getgrouplist() with
1198 statically sized storage. Recompiling will work around this, but
1199 applications should be modified to use dynamically allocated storage
1200 for group arrays as POSIX.1-2008 does not cap an implementation's
1201 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1203 NFS and portalfs mounts may also be affected as the list of groups is
1204 truncated to 16. Users of NFS who use more than 16 groups, should
1205 take care that negative group permissions are not used on the exported
1206 file systems as they will not be reliable unless a GSSAPI based
1207 authentication method is used.
1210 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1211 option compiles in the support for adaptive spinning for lockmgrs
1212 which want to enable it. The lockinit() function now accepts the flag
1213 LK_ADAPTIVE in order to make the lock object subject to adaptive
1214 spinning when both held in write and read mode.
1217 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1218 changed. User applications that use this ioctl need to be rebuilt.
1221 The layout of struct thread has changed. Kernel and modules need to
1225 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1226 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1229 window(1) has been removed from the base system. It can now be
1230 installed from ports. The port is called misc/window.
1233 The way we are storing and accessing `routing table' entries has
1234 changed. Programs reading the FIB, like netstat, need to be
1238 A new netisr implementation has been added for FreeBSD 8. Network
1239 file system modules, such as igmp, ipdivert, and others, should be
1241 Bump __FreeBSD_version to 800096.
1244 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1248 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1249 Bump __FreeBSD_version to 800094.
1252 Add mnt_xflag field to 'struct mount'. File system modules need to be
1254 Bump __FreeBSD_version to 800093.
1257 The compiling option ADAPTIVE_SX has been retired while it has been
1258 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1259 The KPI for sx_init_flags() changes as accepting flags:
1260 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1261 been introduced in order to handle the reversed logic.
1262 Bump __FreeBSD_version to 800092.
1265 Add support for hierarchical jails. Remove global securelevel.
1266 Bump __FreeBSD_version to 800091.
1269 The layout of struct vnet_net has changed, therefore modules
1271 Bump __FreeBSD_version to 800090.
1274 The newly imported zic(8) produces a new format in the output. Please
1275 run tzsetup(8) to install the newly created data to /etc/localtime.
1278 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1279 hw.usb.* and is now consistent again with previous releases.
1282 802.11 monitor mode support was revised and driver api's were changed.
1283 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1284 of DLT_IEEE802_11. No user-visible data structures were changed but
1285 applications that use DLT_IEEE802_11 may require changes.
1286 Bump __FreeBSD_version to 800088.
1289 The layout of the following structs has changed: sysctl_oid,
1290 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1291 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1292 panics may be experienced. World rebuild is required for
1293 correctly checking networking state from userland.
1294 Bump __FreeBSD_version to 800085.
1297 MLDv2 and Source-Specific Multicast (SSM) have been merged
1298 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1299 The implementation of SSM within FreeBSD's IPv6 stack closely
1300 follows the IPv4 implementation.
1302 For kernel developers:
1304 * The most important changes are that the ip6_output() and
1305 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1306 and this lock has been downgraded to a non-recursive mutex.
1308 * As with the changes to the IPv4 stack to support SSM, filtering
1309 of inbound multicast traffic must now be performed by transport
1310 protocols within the IPv6 stack. This does not apply to TCP and
1311 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1313 * The KPIs used by IPv6 multicast are similar to those used by
1314 the IPv4 stack, with the following differences:
1315 * im6o_mc_filter() is analogous to imo_multicast_filter().
1316 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1317 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1318 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1319 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1320 for MLDv1 have an additional 'timer' argument which is used to
1321 jitter the initial membership report for the solicited-node
1322 multicast membership on-link.
1323 * This is not strictly needed for MLDv2, which already jitters
1324 its report transmissions. However, the 'timer' argument is
1325 preserved in case MLDv1 is active on the interface.
1327 * The KAME linked-list based IPv6 membership implementation has
1328 been refactored to use a vector similar to that used by the IPv4
1330 Code which maintains a list of its own multicast memberships
1331 internally, e.g. carp, has been updated to reflect the new
1334 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1335 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1336 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1337 implementation constraint which needs to be addressed in HEAD.
1339 For application developers:
1341 * The changes are broadly similar to those made for the IPv4
1344 * The use of IPv4 and IPv6 multicast socket options on the same
1345 socket, using mapped addresses, HAS NOT been tested or supported.
1347 * There are a number of issues with the implementation of various
1348 IPv6 multicast APIs which need to be resolved in the API surface
1349 before the implementation is fully compatible with KAME userland
1350 use, and these are mostly to do with interface index treatment.
1352 * The literature available discusses the use of either the delta / ASM
1353 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1354 using setsourcefilter(3)/getsourcefilter(3). For more information
1355 please refer to RFC 3768, 'Socket Interface Extensions for
1356 Multicast Source Filters'.
1358 * Applications which use the published RFC 3678 APIs should be fine.
1360 For systems administrators:
1362 * The mtest(8) utility has been refactored to support IPv6, in
1363 addition to IPv4. Interface addresses are no longer accepted
1364 as arguments, their names must be used instead. The utility
1365 will map the interface name to its first IPv4 address as
1366 returned by getifaddrs(3).
1368 * The ifmcstat(8) utility has also been updated to print the MLDv2
1369 endpoint state and source filter lists via sysctl(3).
1371 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1372 loopback of IPv6 multicast datagrams by default; it defaults to 1
1373 to preserve the existing behaviour. Disabling multicast loopback is
1374 recommended for optimal system performance.
1376 * The IPv6 MROUTING code has been changed to examine this sysctl
1377 instead of attempting to perform a group lookup before looping
1378 back forwarded datagrams.
1380 Bump __FreeBSD_version to 800084.
1383 Implement low-level Bluetooth HCI API.
1384 Bump __FreeBSD_version to 800083.
1387 The layout of struct malloc_type, used by modules to register new
1388 memory allocation types, has changed. Most modules will need to
1389 be rebuilt or panics may be experienced.
1390 Bump __FreeBSD_version to 800081.
1393 Anticipate overflowing inp_flags - add inp_flags2.
1394 This changes most offsets in inpcb, so checking v4 connection
1395 state will require a world rebuild.
1396 Bump __FreeBSD_version to 800080.
1399 Add an llentry to struct route and struct route_in6. Modules
1400 embedding a struct route will need to be recompiled.
1401 Bump __FreeBSD_version to 800079.
1404 The size of rt_metrics_lite and by extension rtentry has changed.
1405 Networking administration apps will need to be recompiled.
1406 The route command now supports show as an alias for get, weighting
1407 of routes, sticky and nostick flags to alter the behavior of stateful
1409 Bump __FreeBSD_version to 800078.
1412 Do not use Giant for kbdmux(4) locking. This is wrong and
1413 apparently causing more problems than it solves. This will
1414 re-open the issue where interrupt handlers may race with
1415 kbdmux(4) in polling mode. Typical symptoms include (but
1416 not limited to) duplicated and/or missing characters when
1417 low level console functions (such as gets) are used while
1418 interrupts are enabled (for example geli password prompt,
1419 mountroot prompt etc.). Disabling kbdmux(4) may help.
1422 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1423 kernel modules referencing any of the above need to be recompiled.
1424 Bump __FreeBSD_version to 800075.
1427 GEOM_PART has become the default partition slicer for storage devices,
1428 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1429 introduces some changes:
1431 MSDOS/EBR: the devices created from MSDOS extended partition entries
1432 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1433 to devices with offset-based names. fstabs may need to be modified.
1435 BSD: the "geometry does not match label" warning is harmless in most
1436 cases but it points to problems in file system misalignment with
1437 disk geometry. The "c" partition is now implicit, covers the whole
1438 top-level drive and cannot be (mis)used by users.
1440 General: Kernel dumps are now not allowed to be written to devices
1441 whose partition types indicate they are meant to be used for file
1442 systems (or, in case of MSDOS partitions, as something else than
1445 Most of these changes date approximately from 200812.
1448 The uscanner(4) driver has been removed from the kernel. This follows
1449 Linux removing theirs in 2.6 and making libusb the default interface
1450 (supported by sane).
1453 The multicast forwarding code has been cleaned up. netstat(1)
1454 only relies on KVM now for printing bandwidth upcall meters.
1455 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1456 ip6_mroute_mod respectively. The config(5) options for statically
1457 compiling this code remain the same, i.e. 'options MROUTING'.
1460 Support for the IFF_NEEDSGIANT network interface flag has been
1461 removed, which means that non-MPSAFE network device drivers are no
1462 longer supported. In particular, if_ar, if_sr, and network device
1463 drivers from the old (legacy) USB stack can no longer be built or
1467 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1468 a bunch of new language catalog files have also been added.
1469 This means that some common libc messages are now localized and
1470 they depend on the LC_MESSAGES environmental variable.
1473 The k8temp(4) driver has been renamed to amdtemp(4) since
1474 support for Family 10 and Family 11 CPU families was added.
1477 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1478 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1480 For kernel developers, the most important changes are that the
1481 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1482 and this lock has been downgraded to a non-recursive mutex.
1484 Transport protocols (UDP, Raw IP) are now responsible for filtering
1485 inbound multicast traffic according to group membership and source
1486 filters. The imo_multicast_filter() KPI exists for this purpose.
1487 Transports which do not use multicast (SCTP, TCP) already reject
1488 multicast by default. Forwarding and receive performance may improve
1489 as a mutex acquisition is no longer needed in the ip_input()
1490 low-level input path. in_addmulti() and in_delmulti() are shimmed
1491 to new KPIs which exist to support SSM in-kernel.
1493 For application developers, it is recommended that loopback of
1494 multicast datagrams be disabled for best performance, as this
1495 will still cause the lock to be taken for each looped-back
1496 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1497 be tuned to 0 to disable loopback by default; it defaults to 1
1498 to preserve the existing behaviour.
1500 For systems administrators, to obtain best performance with
1501 multicast reception and multiple groups, it is always recommended
1502 that a card with a suitably precise hash filter is used. Hash
1503 collisions will still result in the lock being taken within the
1504 transport protocol input path to check group membership.
1506 If deploying FreeBSD in an environment with IGMP snooping switches,
1507 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1508 enabled; this forces 224.0.0.0/24 group membership to be announced
1511 The size of 'struct igmpstat' has changed; netstat needs to be
1512 recompiled to reflect this.
1513 Bump __FreeBSD_version to 800070.
1516 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1517 updated to use it. This requires a buildworld/installworld in order to
1518 update the library and dependencies (usbconfig, etc). Its advisable to
1519 rebuild all ports which uses libusb. More specific directions are given
1520 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1521 libusb are no longer required and can be removed.
1524 A workaround is committed to allow the creation of System V shared
1525 memory segment of size > 2 GB on the 64-bit architectures.
1526 Due to a limitation of the existing ABI, the shm_segsz member
1527 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1528 wrong for large segments. Note that limits must be explicitly
1529 raised to allow such segments to be created.
1532 The layout of struct ifnet has changed, requiring a rebuild of all
1533 network device driver modules.
1536 The /dev handling for the new USB stack has changed, a
1537 buildworld/installworld is required for libusb20.
1540 The new USB2 stack has now been permanently moved in and all kernel and
1541 module names reverted to their previous values (eg, usb, ehci, ohci,
1542 ums, ...). The old usb stack can be compiled in by prefixing the name
1543 with the letter 'o', the old usb modules have been removed.
1544 Updating entry 20090216 for xorg and 20090215 for libmap may still
1548 The rc.conf(5) option if_up_delay has been renamed to
1549 defaultroute_delay to better reflect its purpose. If you have
1550 customized this setting in /etc/rc.conf you need to update it to
1554 xorg 7.4 wants to configure its input devices via hald which does not
1555 yet work with USB2. If the keyboard/mouse does not work in xorg then
1557 Option "AllowEmptyInput" "off"
1558 to your ServerLayout section. This will cause X to use the configured
1559 kbd and mouse sections from your xorg.conf.
1562 The GENERIC kernels for all architectures now default to the new USB2
1563 stack. No kernel config options or code have been removed so if a
1564 problem arises please report it and optionally revert to the old USB
1565 stack. If you are loading USB kernel modules or have a custom kernel
1566 that includes GENERIC then ensure that usb names are also changed over,
1567 eg uftdi -> usb2_serial_ftdi.
1569 Older programs linked against the ports libusb 0.1 need to be
1570 redirected to the new stack's libusb20. /etc/libmap.conf can
1572 # Map old usb library to new one for usb2 stack
1573 libusb-0.1.so.8 libusb20.so.1
1576 All USB ethernet devices now attach as interfaces under the name ueN
1577 (eg. ue0). This is to provide a predictable name as vendors often
1578 change usb chipsets in a product without notice.
1581 The ichsmb(4) driver has been changed to require SMBus slave
1582 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1583 All of the other SMBus controller drivers require left-justified
1584 slave addresses, so this change makes all the drivers provide the
1588 INET6 statistics (struct ip6stat) was updated.
1589 netstat(1) needs to be recompiled.
1592 NTFS has been removed from GENERIC kernel on amd64 to match
1593 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1594 will load ntfs.ko module automatically when NTFS support is
1595 actually needed, unless ntfs.ko is not installed or security
1596 level prohibits loading kernel modules. If either is the case,
1597 "options NTFS" has to be added into kernel config.
1600 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1601 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1602 800061. User space tools that rely on the size of struct tcpcb in
1603 tcp_var.h (e.g. sockstat) need to be recompiled.
1606 ng_tty(4) module updated to match the new TTY subsystem.
1607 Due to API change, user-level applications must be updated.
1608 New API support added to mpd5 CVS and expected to be present
1609 in next mpd5.3 release.
1612 With __FreeBSD_version 800060 the makefs tool is part of
1613 the base system (it was a port).
1616 The afdata and ifnet locks have been changed from mutexes to
1617 rwlocks, network modules will need to be re-compiled.
1620 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1621 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1622 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1623 architecture and 40 bytes on 64-bit architecture. The userland
1624 applications "arp" and "ndp" have been updated accordingly.
1625 The output from "netstat -r" shows only routing entries and
1626 none of the L2 information.
1629 __FreeBSD_version 800057 marks the switchover from the
1630 binary ath hal to source code. Users must add the line:
1632 options AH_SUPPORT_AR5416
1634 to their kernel config files when specifying:
1638 The ath_hal module no longer exists; the code is now compiled
1639 together with the driver in the ath module. It is now
1640 possible to tailor chip support (i.e. reduce the set of chips
1641 and thereby the code size); consult ath_hal(4) for details.
1644 __FreeBSD_version 800054 adds memory barriers to
1645 <machine/atomic.h>, new interfaces to ifnet to facilitate
1646 multiple hardware transmit queues for cards that support
1647 them, and a lock-less ring-buffer implementation to
1648 enable drivers to more efficiently manage queueing of
1652 A new version of ZFS (version 13) has been merged to -HEAD.
1653 This version has zpool attribute "listsnapshots" off by
1654 default, which means "zfs list" does not show snapshots,
1655 and is the same as Solaris behavior.
1658 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1661 The uhci, ohci, ehci and slhci USB Host controller drivers have
1662 been put into separate modules. If you load the usb module
1663 separately through loader.conf you will need to load the
1664 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1665 controller add the following to loader.conf:
1671 The ABI used by the PMC toolset has changed. Please keep
1672 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1676 atapci kernel module now includes only generic PCI ATA
1677 driver. AHCI driver moved to ataahci kernel module.
1678 All vendor-specific code moved into separate kernel modules:
1679 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1680 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1681 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1682 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1685 The TTY subsystem of the kernel has been replaced by a new
1686 implementation, which provides better scalability and an
1687 improved driver model. Most common drivers have been migrated to
1688 the new TTY subsystem, while others have not. The following
1689 drivers have not yet been ported to the new TTY layer:
1692 cy, digi, rc, rp, sio
1698 ng_h4, ng_tty, ppp, sl, snp
1700 Adding these drivers to your kernel configuration file shall
1701 cause compilation to fail.
1704 ntpd has been upgraded to 4.2.4p5.
1707 OpenSSH has been upgraded to 5.1p1.
1709 For many years, FreeBSD's version of OpenSSH preferred DSA
1710 over RSA for host and user authentication keys. With this
1711 upgrade, we've switched to the vendor's default of RSA over
1712 DSA. This may cause upgraded clients to warn about unknown
1713 host keys even for previously known hosts. Users should
1714 follow the usual procedure for verifying host keys before
1715 accepting the RSA key.
1717 This can be circumvented by setting the "HostKeyAlgorithms"
1718 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1721 Please note that the sequence of keys offered for
1722 authentication has been changed as well. You may want to
1723 specify IdentityFile in a different order to revert this
1727 The sio(4) driver has been removed from the i386 and amd64
1728 kernel configuration files. This means uart(4) is now the
1729 default serial port driver on those platforms as well.
1731 To prevent collisions with the sio(4) driver, the uart(4) driver
1732 uses different names for its device nodes. This means the
1733 onboard serial port will now most likely be called "ttyu0"
1734 instead of "ttyd0". You may need to reconfigure applications to
1735 use the new device names.
1737 When using the serial port as a boot console, be sure to update
1738 /boot/device.hints and /etc/ttys before booting the new kernel.
1739 If you forget to do so, you can still manually specify the hints
1740 at the loader prompt:
1742 set hint.uart.0.at="isa"
1743 set hint.uart.0.port="0x3F8"
1744 set hint.uart.0.flags="0x10"
1745 set hint.uart.0.irq="4"
1749 The gpt(8) utility has been removed. Use gpart(8) to partition
1753 The version that Linuxulator emulates was changed from 2.4.2
1754 to 2.6.16. If you experience any problems with Linux binaries
1755 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1756 if it fixes the problem contact emulation mailing list.
1759 ISDN4BSD (I4B) was removed from the src tree. You may need to
1760 update a your kernel configuration and remove relevant entries.
1763 I have checked in code to support multiple routing tables.
1764 See the man pages setfib(1) and setfib(2).
1765 This is a hopefully backwards compatible version,
1766 but to make use of it you need to compile your kernel
1767 with options ROUTETABLES=2 (or more up to 16).
1770 The 802.11 wireless support was redone to enable multi-bss
1771 operation on devices that are capable. The underlying device
1772 is no longer used directly but instead wlanX devices are
1773 cloned with ifconfig. This requires changes to rc.conf files.
1774 For example, change:
1775 ifconfig_ath0="WPA DHCP"
1778 ifconfig_wlan0="WPA DHCP"
1779 see rc.conf(5) for more details. In addition, mergemaster of
1780 /etc/rc.d is highly recommended. Simultaneous update of userland
1781 and kernel wouldn't hurt either.
1783 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1784 modules were merged into the base wlan module. All references
1785 to these modules (e.g. in kernel config files) must be removed.
1788 psm(4) has gained write(2) support in native operation level.
1789 Arbitrary commands can be written to /dev/psm%d and status can
1790 be read back from it. Therefore, an application is responsible
1791 for status validation and error recovery. It is a no-op in
1792 other operation levels.
1795 Support for KSE threading has been removed from the kernel. To
1796 run legacy applications linked against KSE libmap.conf may
1797 be used. The following libmap.conf may be used to ensure
1798 compatibility with any prior release:
1800 libpthread.so.1 libthr.so.1
1801 libpthread.so.2 libthr.so.2
1802 libkse.so.3 libthr.so.3
1805 The layout of struct vmspace has changed. This affects libkvm
1806 and any executables that link against libkvm and use the
1807 kvm_getprocs() function. In particular, but not exclusively,
1808 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1809 The effects are minimal, but it's advisable to upgrade world
1813 The latest em driver no longer has support in it for the
1814 82575 adapter, this is now moved to the igb driver. The
1815 split was done to make new features that are incompatible
1816 with older hardware easier to do.
1819 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1820 likewise the kernel option is now GEOM_LINUX_LVM.
1823 The default NFS mount mode has changed from UDP to TCP for
1824 increased reliability. If you rely on (insecurely) NFS
1825 mounting across a firewall you may need to update your
1829 Belatedly note the addition of m_collapse for compacting
1833 The fts(3) structures have been changed to use adequate
1834 integer types for their members and so to be able to cope
1835 with huge file trees. The old fts(3) ABI is preserved
1836 through symbol versioning in libc, so third-party binaries
1837 using fts(3) should still work, although they will not take
1838 advantage of the extended types. At the same time, some
1839 third-party software might fail to build after this change
1840 due to unportable assumptions made in its source code about
1841 fts(3) structure members. Such software should be fixed
1842 by its vendor or, in the worst case, in the ports tree.
1843 FreeBSD_version 800015 marks this change for the unlikely
1844 case that a portable fix is impossible.
1847 To upgrade to -current after this date, you must be running
1848 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1849 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1852 The ADAPTIVE_GIANT kernel option has been retired because its
1853 functionality is the default now.
1856 The AT keyboard emulation of sunkbd(4) has been turned on
1857 by default. In order to make the special symbols of the Sun
1858 keyboards driven by sunkbd(4) work under X these now have
1859 to be configured the same way as Sun USB keyboards driven
1860 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1862 Option "XkbLayout" "us"
1863 Option "XkbRules" "xorg"
1864 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1867 It has been decided that it is desirable to provide ABI
1868 backwards compatibility to the FreeBSD 4/5/6 versions of the
1869 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1870 broken with the introduction of PCI domain support (see the
1871 20070930 entry). Unfortunately, this required the ABI of
1872 PCIOCGETCONF to be broken again in order to be able to
1873 provide backwards compatibility to the old version of that
1874 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1875 again. As for prominent ports this affects neither pciutils
1876 nor xorg-server this time, the hal port needs to be rebuilt
1880 The misnamed kthread_create() and friends have been renamed
1881 to kproc_create() etc. Many of the callers already
1882 used kproc_start()..
1883 I will return kthread_create() and friends in a while
1884 with implementations that actually create threads, not procs.
1885 Renaming corresponds with version 800002.
1894 Avoid using make -j when upgrading. While generally safe, there are
1895 sometimes problems using -j to upgrade. If your upgrade fails with
1896 -j, please try again without -j. From time to time in the past there
1897 have been problems using -j with buildworld and/or installworld. This
1898 is especially true when upgrading between "distant" versions (eg one
1899 that cross a major release boundary or several minor releases, or when
1900 several months have passed on the -current branch).
1902 Sometimes, obscure build problems are the result of environment
1903 poisoning. This can happen because the make utility reads its
1904 environment when searching for values for global variables. To run
1905 your build attempts in an "environmental clean room", prefix all make
1906 commands with 'env -i '. See the env(1) manual page for more details.
1908 When upgrading from one major version to another it is generally best
1909 to upgrade to the latest code in the currently installed branch first,
1910 then do an upgrade to the new branch. This is the best-tested upgrade
1911 path, and has the highest probability of being successful. Please try
1912 this approach before reporting problems with a major version upgrade.
1914 When upgrading a live system, having a root shell around before
1915 installing anything can help undo problems. Not having a root shell
1916 around can lead to problems if pam has changed too much from your
1917 starting point to allow continued authentication after the upgrade.
1921 When upgrading the boot ZFS pool to a new version, always follow
1924 1.) recompile and reinstall the ZFS boot loader and boot block
1925 (this is part of "make buildworld" and "make installworld")
1927 2.) update the ZFS boot block on your boot drive
1929 The following example updates the ZFS boot block on the first
1930 partition (freebsd-boot) of a GPT partitioned drive ad0:
1931 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1933 Non-boot pools do not need these updates.
1937 If you are updating from a prior version of FreeBSD (even one just
1938 a few days old), you should follow this procedure. It is the most
1939 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1941 make kernel-toolchain
1942 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1943 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1945 To test a kernel once
1946 ---------------------
1947 If you just want to boot a kernel once (because you are not sure
1948 if it works, or if you want to boot a known bad kernel to provide
1949 debugging information) run
1950 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1951 nextboot -k testkernel
1953 To just build a kernel when you know that it won't mess you up
1954 --------------------------------------------------------------
1955 This assumes you are already running a CURRENT system. Replace
1956 ${arch} with the architecture of your machine (e.g. "i386",
1957 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1959 cd src/sys/${arch}/conf
1960 config KERNEL_NAME_HERE
1961 cd ../compile/KERNEL_NAME_HERE
1966 If this fails, go to the "To build a kernel" section.
1968 To rebuild everything and install it on the current system.
1969 -----------------------------------------------------------
1970 # Note: sometimes if you are running current you gotta do more than
1971 # is listed here if you are upgrading from a really old current.
1973 <make sure you have good level 0 dumps>
1975 make kernel KERNCONF=YOUR_KERNEL_HERE
1977 <reboot in single user> [3]
1984 To cross-install current onto a separate partition
1985 --------------------------------------------------
1986 # In this approach we use a separate partition to hold
1987 # current's root, 'usr', and 'var' directories. A partition
1988 # holding "/", "/usr" and "/var" should be about 2GB in
1991 <make sure you have good level 0 dumps>
1994 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1995 <maybe newfs current's root partition>
1996 <mount current's root partition on directory ${CURRENT_ROOT}>
1997 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1998 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1999 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2000 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2001 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2002 <reboot into current>
2003 <do a "native" rebuild/install as described in the previous section>
2004 <maybe install compatibility libraries from ports/misc/compat*>
2008 To upgrade in-place from stable to current
2009 ----------------------------------------------
2010 <make sure you have good level 0 dumps>
2012 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2014 <reboot in single user> [3]
2021 Make sure that you've read the UPDATING file to understand the
2022 tweaks to various things you need. At this point in the life
2023 cycle of current, things change often and you are on your own
2024 to cope. The defaults can also change, so please read ALL of
2025 the UPDATING entries.
2027 Also, if you are tracking -current, you must be subscribed to
2028 freebsd-current@freebsd.org. Make sure that before you update
2029 your sources that you have read and understood all the recent
2030 messages there. If in doubt, please track -stable which has
2031 much fewer pitfalls.
2033 [1] If you have third party modules, such as vmware, you
2034 should disable them at this point so they don't crash your
2037 [3] From the bootblocks, boot -s, and then do
2042 adjkerntz -i # if CMOS is wall time
2043 Also, when doing a major release upgrade, it is required that
2044 you boot into single user mode to do the installworld.
2046 [4] Note: This step is non-optional. Failure to do this step
2047 can result in a significant reduction in the functionality of the
2048 system. Attempting to do it by hand is not recommended and those
2049 that pursue this avenue should read this file carefully, as well
2050 as the archives of freebsd-current and freebsd-hackers mailing lists
2051 for potential gotchas. The -U option is also useful to consider.
2052 See mergemaster(8) for more information.
2054 [5] Usually this step is a noop. However, from time to time
2055 you may need to do this if you get unknown user in the following
2056 step. It never hurts to do it all the time. You may need to
2057 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2058 install) after the buildworld before this step if you last updated
2059 from current before 20130425 or from -stable before 20130430.
2061 [6] This only deletes old files and directories. Old libraries
2062 can be deleted by "make delete-old-libs", but you have to make
2063 sure that no program is using those libraries anymore.
2065 [8] In order to have a kernel that can run the 4.x binaries needed to
2066 do an installworld, you must include the COMPAT_FREEBSD4 option in
2067 your kernel. Failure to do so may leave you with a system that is
2068 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2069 required to run the 5.x binaries on more recent kernels. And so on
2070 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2072 Make sure that you merge any new devices from GENERIC since the
2073 last time you updated your kernel config file.
2075 [9] When checking out sources, you must include the -P flag to have
2076 cvs prune empty directories.
2078 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2079 "?=" instead of the "=" assignment operator, so that buildworld can
2080 override the CPUTYPE if it needs to.
2082 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2083 not on the command line, or in /etc/make.conf. buildworld will
2084 warn if it is improperly defined.
2087 This file contains a list, in reverse chronological order, of major
2088 breakages in tracking -current. It is not guaranteed to be a complete
2089 list of such breakages, and only contains entries since October 10, 2007.
2090 If you need to see UPDATING entries from before that date, you will need
2091 to fetch an UPDATING file from an older FreeBSD release.
2093 Copyright information:
2095 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2097 Redistribution, publication, translation and use, with or without
2098 modification, in full or in part, in any form or format of this
2099 document are permitted without further permission from the author.
2101 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2102 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2103 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2104 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2105 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2106 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2107 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2108 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2109 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2110 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2111 POSSIBILITY OF SUCH DAMAGE.
2113 Contact Warner Losh if you have any questions about your use of