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