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