1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
20 The ofwfb driver, used to provide a graphics console on PowerPC when
21 using vt(4), no longer allows mmap() of all of physical memory. This
22 will prevent Xorg on PowerPC with some ATI graphics cards from
23 initializing properly unless x11-servers/xorg-server is updated to
27 The libatf-c and libatf-c++ major versions were downgraded to 0 and
28 1 respectively to match the upstream numbers. They were out of
29 sync because, when they were originally added to FreeBSD, the
30 upstream versions were not respected. These libraries are private
31 and not yet built by default, so renumbering them should be a
32 non-issue. However, unclean source trees will yield broken test
33 programs once the operator executes "make delete-old-libs" after a
36 If you are using WITH_TESTS=yes (not the default), wipe the object
37 tree and rebuild from scratch to prevent spurious test failures.
38 This is only needed once: the old, misnumbered libraries have been
39 added to OptionalObsoleteFiles.inc so they will be removed during a
43 The ixgbe tunables now match their sysctl counterparts, for example:
44 hw.ixgbe.enable_aim => hw.ix.enable_aim
45 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
48 The NFSv4.1 server committed by r269398 changes the internal
49 function call interfaces used between the NFS and krpc modules.
50 As such, __FreeBSD_version was bumped.
53 The default unbound configuration has been modified to address
54 issues with reverse lookups on networks that use private
55 address ranges. If you use the local_unbound service, run
56 "service local_unbound setup" as root to regenerate your
57 configuration, then "service local_unbound reload" to load the
61 It is no longer necessary to include the dwarf version in your DEBUG
62 options in your kernel config file. The bug that required it to be
63 placed in the config file has bene fixed. DEBUG should now just
64 contain -g. The build system will automatically update things
65 to do the right thing.
68 Several ABI breaking changes were merged to CTL and new iSCSI code.
69 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
70 iscsictl need to be rebuilt to work with a new kernel.
73 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
74 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
75 which differs from the behaviour controlled by this knob.)
78 On i386 and amd64 systems, the onifconsole flag is now set by default
79 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
80 as a login TTY if it is set in the bootloader as an active kernel
81 console. No changes in behavior should result otherwise. To revert to
82 the previous behavior, set ttyu0 to "off" in /etc/ttys.
85 Clang and llvm have been upgraded to 3.4.1 release.
88 Clang and llvm have been upgraded to 3.4 release.
91 If a Makefile in a tests/ directory was auto-generating a Kyuafile
92 instead of providing an explicit one, this would prevent such
93 Makefile from providing its own Kyuafile in the future during
94 NO_CLEAN builds. This has been fixed in the Makefiles but manual
95 intervention is needed to clean an objdir if you use NO_CLEAN:
96 # find /usr/obj -name Kyuafile | xargs rm -f
99 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
100 capability mode support. Please note that enabling the feature in
101 kernel is still highly recommended.
104 OpenSSH is now built with sandbox support, and will use sandbox as
105 the default privilege separation method. This requires Capsicum
106 capability mode support in kernel.
109 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
110 been deprecated and will not be part of FreeBSD 11.0 and later
111 releases. If you use this driver, please consider switching to
112 the nfe(4) driver instead.
118 The behavior of gss_pseudo_random() for the krb5 mechanism
119 has changed, for applications requesting a longer random string
120 than produced by the underlying enctype's pseudo-random() function.
121 In particular, the random string produced from a session key of
122 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
123 be different at the 17th octet and later, after this change.
124 The counter used in the PRF+ construction is now encoded as a
125 big-endian integer in accordance with RFC 4402.
126 __FreeBSD_version is bumped to 1000701.
129 The WITHOUT_ATF build knob has been removed and its functionality
130 has been subsumed into the more generic WITHOUT_TESTS. If you were
131 using the former to disable the build of the ATF libraries, you
132 should change your settings to use the latter.
135 The default version of mtree is nmtree which is obtained from
136 NetBSD. The output is generally the same, but may vary
137 slightly. If you found you need identical output adding
138 "-F freebsd9" to the command line should do the trick. For the
139 time being, the old mtree is available as fmtree.
142 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
143 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
144 1.1.4_8 and verify bsdyml not linked in, before running "make
146 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
148 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
151 The rc.d/jail script has been updated to support jail(8)
152 configuration file. The "jail_<jname>_*" rc.conf(5) variables
153 for per-jail configuration are automatically converted to
154 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
155 This is transparently backward compatible. See below about some
156 incompatibilities and rc.conf(5) manual page for more details.
158 These variables are now deprecated in favor of jail(8) configuration
159 file. One can use "rc.d/jail config <jname>" command to generate
160 a jail(8) configuration file in /var/run/jail.<jname>.conf without
161 running the jail(8) utility. The default pathname of the
162 configuration file is /etc/jail.conf and can be specified by
163 using $jail_conf or $jail_<jname>_conf variables.
165 Please note that jail_devfs_ruleset accepts an integer at
166 this moment. Please consider to rewrite the ruleset name
170 BIND has been removed from the base system. If all you need
171 is a local resolver, simply enable and start the local_unbound
172 service instead. Otherwise, several versions of BIND are
173 available in the ports tree. The dns/bind99 port is one example.
175 With this change, nslookup(1) and dig(1) are no longer in the base
176 system. Users should instead use host(1) and drill(1) which are
177 in the base system. Alternatively, nslookup and dig can
178 be obtained by installing the dns/bind-tools port.
181 With the addition of unbound(8), a new unbound user is now
182 required during installworld. "mergemaster -p" can be used to
183 add the user prior to installworld, as documented in the handbook.
186 OpenSSH is now built with DNSSEC support, and will by default
187 silently trust signed SSHFP records. This can be controlled with
188 the VerifyHostKeyDNS client configuration setting. DNSSEC support
189 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
192 The GNU Compiler Collection and C++ standard library (libstdc++)
193 are no longer built by default on platforms where clang is the system
194 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
198 The PROCDESC kernel option is now part of the GENERIC kernel
199 configuration and is required for the rwhod(8) to work.
200 If you are using custom kernel configuration, you should include
204 The API and ABI related to the Capsicum framework was modified
205 in backward incompatible way. The userland libraries and programs
206 have to be recompiled to work with the new kernel. This includes the
207 following libraries and programs, but the whole buildworld is
208 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
209 kdump, procstat, rwho, rwhod, uniq.
212 AES-NI intrinsic support has been added to gcc. The AES-NI module
213 has been updated to use this support. A new gcc is required to build
214 the aesni module on both i386 and amd64.
217 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
218 Thus "device padlock_rng" and "device rdrand_rng" should be
219 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
222 WITH_ICONV has been split into two feature sets. WITH_ICONV now
223 enables just the iconv* functionality and is now on by default.
224 WITH_LIBICONV_COMPAT enables the libiconv api and link time
225 compatability. Set WITHOUT_ICONV to build the old way.
226 If you have been using WITH_ICONV before, you will very likely
227 need to turn on WITH_LIBICONV_COMPAT.
230 INVARIANTS option now enables DEBUG for code with OpenSolaris and
231 Illumos origin, including ZFS. If you have INVARIANTS in your
232 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
234 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
235 locks if WITNESS option was set. Because that generated a lot of
236 witness(9) reports and all of them were believed to be false
237 positives, this is no longer done. New option OPENSOLARIS_WITNESS
238 can be used to achieve the previous behavior.
241 Timer values in IPv6 data structures now use time_uptime instead
242 of time_second. Although this is not a user-visible functional
243 change, userland utilities which directly use them---ndp(8),
244 rtadvd(8), and rtsold(8) in the base system---need to be updated
248 find -delete can now delete the pathnames given as arguments,
249 instead of only files found below them or if the pathname did
250 not contain any slashes. Formerly, the following error message
253 find: -delete: <path>: relative path potentially not safe
255 Deleting the pathnames given as arguments can be prevented
256 without error messages using -mindepth 1 or by changing
257 directory and passing "." as argument to find. This works in the
258 old as well as the new version of find.
261 Behavior of devfs rules path matching has been changed.
262 Pattern is now always matched against fully qualified devfs
263 path and slash characters must be explicitly matched by
264 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
265 subdirectories must be reviewed.
268 The default ARM ABI has changed to the ARM EABI. The old ABI is
269 incompatible with the ARM EABI and all programs and modules will
270 need to be rebuilt to work with a new kernel.
272 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
274 NOTE: Support for the old ABI will be removed in the future and
275 users are advised to upgrade.
278 pkg_install has been disconnected from the build if you really need it
279 you should add WITH_PKGTOOLS in your src.conf(5).
282 Most of network statistics structures were changed to be able
283 keep 64-bits counters. Thus all tools, that work with networking
284 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
287 Fix targets that run multiple make's to use && rather than ;
288 so that subsequent steps depend on success of previous.
290 NOTE: if building 'universe' with -j* on stable/8 or stable/9
291 it would be better to start the build using bmake, to avoid
292 overloading the machine.
295 Fix a bug that allowed a tracing process (e.g. gdb) to write
296 to a memory-mapped file in the traced process's address space
297 even if neither the traced process nor the tracing process had
298 write access to that file.
301 CVS has been removed from the base system. An exact copy
302 of the code is available from the devel/cvs port.
305 Some people report the following error after the switch to bmake:
307 make: illegal option -- J
308 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
310 *** [buildworld] Error code 2
312 this likely due to an old instance of make in
313 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
314 which src/Makefile will use that blindly, if it exists, so if
315 you see the above error:
317 rm -rf `make -V MAKEPATH`
322 Use bmake by default.
323 Whereas before one could choose to build with bmake via
324 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
325 make. The goal is to remove these knobs for 10-RELEASE.
327 It is worth noting that bmake (like gmake) treats the command
328 line as the unit of failure, rather than statements within the
329 command line. Thus '(cd some/where && dosomething)' is safer
330 than 'cd some/where; dosomething'. The '()' allows consistent
331 behavior in parallel build.
334 Fix a bug that allows NFS clients to issue READDIR on files.
337 The WITHOUT_IDEA option has been removed because
338 the IDEA patent expired.
341 The sysctl which controls TRIM support under ZFS has been renamed
342 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
346 The mergemaster command now uses the default MAKEOBJDIRPREFIX
347 rather than creating it's own in the temporary directory in
348 order allow access to bootstrapped versions of tools such as
349 install and mtree. When upgrading from version of FreeBSD where
350 the install command does not support -l, you will need to
351 install a new mergemaster command if mergemaster -p is required.
352 This can be accomplished with the command (cd src/usr.sbin/mergemaster
356 Legacy ATA stack, disabled and replaced by new CAM-based one since
357 FreeBSD 9.0, completely removed from the sources. Kernel modules
358 atadisk and atapi*, user-level tools atacontrol and burncd are
359 removed. Kernel option `options ATA_CAM` is now permanently enabled
363 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
364 and socketpair(2). Software, in particular Kerberos, may
365 automatically detect and use these during building. The resulting
366 binaries will not work on older kernels.
369 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
370 information, see the respective 20130304 entry).
373 Recent commits to callout(9) changed the size of struct callout,
374 so the KBI is probably heavily disturbed. Also, some functions
375 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
376 by macros. Every kernel module using it won't load, so rebuild
379 The ctl device has been re-enabled in GENERIC for i386 and amd64,
380 but does not initialize by default (because of the new CTL_DISABLE
381 option) to save memory. To re-enable it, remove the CTL_DISABLE
382 option from the kernel config file or set kern.cam.ctl.disable=0
383 in /boot/loader.conf.
386 The ctl device has been disabled in GENERIC for i386 and amd64.
387 This was done due to the extra memory being allocated at system
388 initialisation time by the ctl driver which was only used if
389 a CAM target device was created. This makes a FreeBSD system
390 unusable on 128MB or less of RAM.
393 A new compression method (lz4) has been merged to -HEAD. Please
394 refer to zpool-features(7) for more information.
396 Please refer to the "ZFS notes" section of this file for information
397 on upgrading boot ZFS pools.
400 A BSD-licensed patch(1) variant has been added and is installed
401 as bsdpatch, being the GNU version the default patch.
402 To inverse the logic and use the BSD-licensed one as default,
403 while having the GNU version installed as gnupatch, rebuild
404 and install world with the WITH_BSD_PATCH knob set.
407 Due to the use of the new -l option to install(1) during build
408 and install, you must take care not to directly set the INSTALL
409 make variable in your /etc/make.conf, /etc/src.conf, or on the
410 command line. If you wish to use the -C flag for all installs
411 you may be able to add INSTALL+=-C to /etc/make.conf or
415 The install(1) option -M has changed meaning and now takes an
416 argument that is a file or path to append logs to. In the
417 unlikely event that -M was the last option on the command line
418 and the command line contained at least two files and a target
419 directory the first file will have logs appended to it. The -M
420 option served little practical purpose in the last decade so its
421 use is expected to be extremely rare.
424 After switching to Clang as the default compiler some users of ZFS
425 on i386 systems started to experience stack overflow kernel panics.
426 Please consider using 'options KSTACK_PAGES=4' in such configurations.
429 GEOM_LABEL now mangles label names read from file system metadata.
430 Mangling affect labels containing spaces, non-printable characters,
431 '%' or '"'. Device names in /etc/fstab and other places may need to
435 By default, only the 10 most recent kernel dumps will be saved. To
436 restore the previous behaviour (no limit on the number of kernel dumps
437 stored in the dump directory) add the following line to /etc/rc.conf:
442 With the addition of auditdistd(8), a new auditdistd user is now
443 required during installworld. "mergemaster -p" can be used to
444 add the user prior to installworld, as documented in the handbook.
447 The sin6_scope_id member variable in struct sockaddr_in6 is now
448 filled by the kernel before passing the structure to the userland via
449 sysctl or routing socket. This means the KAME-specific embedded scope
450 id in sin6_addr.s6_addr[2] is always cleared in userland application.
451 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
452 __FreeBSD_version is bumped to 1000025.
455 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
456 This means that the world and kernel will be compiled with clang
457 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
458 and /usr/bin/cpp. To disable this behavior and revert to building
459 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
460 of current may need to bootstrap WITHOUT_CLANG first if the clang
461 build fails (its compatibility window doesn't extend to the 9 stable
465 The IPFIREWALL_FORWARD kernel option has been removed. Its
466 functionality now turned on by default.
469 The ZERO_COPY_SOCKET kernel option has been removed and
470 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
471 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
472 mechanism which is not safe and may result in kernel crashes.
473 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
474 driver supports disposeable external page sized mbuf storage.
475 Proper replacements for both zero-copy mechanisms are under
476 consideration and will eventually lead to complete removal
477 of the two kernel options.
480 The IPv4 network stack has been converted to network byte
481 order. The following modules need to be recompiled together
482 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
483 pf(4), ipfw(4), ng_ipfw(4), stf(4).
486 Support for non-MPSAFE filesystems was removed from VFS. The
487 VFS_VERSION was bumped, all filesystem modules shall be
491 All the non-MPSAFE filesystems have been disconnected from
492 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
493 portalfs, smbfs, xfs.
496 The interface cloning API and ABI has changed. The following
497 modules need to be recompiled together with kernel:
498 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
499 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
500 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
503 The sdhci driver was split in two parts: sdhci (generic SD Host
504 Controller logic) and sdhci_pci (actual hardware driver).
505 No kernel config modifications are required, but if you
506 load sdhc as a module you must switch to sdhci_pci instead.
509 Import the FUSE kernel and userland support into base system.
512 The GNU sort(1) program has been removed since the BSD-licensed
513 sort(1) has been the default for quite some time and no serious
514 problems have been reported. The corresponding WITH_GNU_SORT
518 The pfil(9) API/ABI for AF_INET family has been changed. Packet
519 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
523 The net80211(4) ABI has been changed to allow for improved driver
524 PS-POLL and power-save support. All wireless drivers need to be
525 recompiled to work with the new kernel.
528 The random(4) support for the VIA hardware random number
529 generator (`PADLOCK') is no longer enabled unconditionally.
530 Add the padlock_rng device in the custom kernel config if
531 needed. The GENERIC kernels on i386 and amd64 do include the
532 device, so the change only affects the custom kernel
536 The pf(4) packet filter ABI has been changed. pfctl(8) and
537 snmp_pf module need to be recompiled to work with new kernel.
540 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
541 to -HEAD. Pools that have empty_bpobj in active state can not be
542 imported read-write with ZFS implementations that do not support
543 this feature. For more information read the zpool-features(5)
547 The sparc64 ZFS loader has been changed to no longer try to auto-
548 detect ZFS providers based on diskN aliases but now requires these
549 to be explicitly listed in the OFW boot-device environment variable.
552 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
553 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
554 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
557 The following sysctls and tunables have been renamed for consistency
558 with other variables:
559 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
560 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
563 The sort utility has been replaced with BSD sort. For now, GNU sort
564 is also available as "gnusort" or the default can be set back to
565 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
566 installed as "bsdsort".
569 A new version of ZFS (pool version 5000) has been merged to -HEAD.
570 Starting with this version the old system of ZFS pool versioning
571 is superseded by "feature flags". This concept enables forward
572 compatibility against certain future changes in functionality of ZFS
573 pools. The first read-only compatible "feature flag" for ZFS pools
574 is named "com.delphix:async_destroy". For more information
575 read the new zpool-features(5) manual page.
576 Please refer to the "ZFS notes" section of this file for information
577 on upgrading boot ZFS pools.
580 The malloc(3) implementation embedded in libc now uses sources imported
581 as contrib/jemalloc. The most disruptive API change is to
582 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
583 delete it prior to installworld, and optionally re-create it using the
584 new format after rebooting. See malloc.conf(5) for details
585 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
589 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
590 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
591 now spelled mips. This is to aid compatibility with third-party
592 software that expects this naming scheme in uname(3). Little-endian
593 settings are unchanged. If you are updating a big-endian mips64 machine
594 from before this change, you may need to set MACHINE_ARCH=mips64 in
595 your environment before the new build system will recognize your machine.
598 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
602 Now unix domain sockets behave "as expected" on nullfs(5). Previously
603 nullfs(5) did not pass through all behaviours to the underlying layer,
604 as a result if we bound to a socket on the lower layer we could connect
605 only to the lower path; if we bound to the upper layer we could connect
606 only to the upper path. The new behavior is one can connect to both the
607 lower and the upper paths regardless what layer path one binds to.
610 The getifaddrs upgrade path broken with 20111215 has been restored.
611 If you have upgraded in between 20111215 and 20120209 you need to
612 recompile libc again with your kernel. You still need to recompile
613 world to be able to configure CARP but this restriction already
617 The set_rcvar() function has been removed from /etc/rc.subr. All
618 base and ports rc.d scripts have been updated, so if you have a
619 port installed with a script in /usr/local/etc/rc.d you can either
620 hand-edit the rcvar= line, or reinstall the port.
622 An easy way to handle the mass-update of /etc/rc.d:
623 rm /etc/rc.d/* && mergemaster -i
626 panic(9) now stops other CPUs in the SMP systems, disables interrupts
627 on the current CPU and prevents other threads from running.
628 This behavior can be reverted using the kern.stop_scheduler_on_panic
630 The new behavior can be incompatible with kern.sync_on_panic.
633 The carp(4) facility has been changed significantly. Configuration
634 of the CARP protocol via ifconfig(8) has changed, as well as format
635 of CARP events submitted to devd(8) has changed. See manual pages
636 for more information. The arpbalance feature of carp(4) is currently
637 not supported anymore.
639 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
640 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
641 need to be recompiled.
644 The acpi_wmi(4) status device /dev/wmistat has been renamed to
648 The option VFS_ALLOW_NONMPSAFE option has been added in order to
649 explicitely support non-MPSAFE filesystems.
650 It is on by default for all supported platform at this present
654 The broken amd(4) driver has been replaced with esp(4) in the amd64,
655 i386 and pc98 GENERIC kernel configuration files.
658 sysinstall has been removed
661 The stable/9 branch created in subversion. This corresponds to the
662 RELENG_9 branch in CVS.
665 This commit modifies vfs_register() so that it uses a hash
666 calculation to set vfc_typenum, which is enabled by default.
667 The first time a system is booted after this change, the
668 vfc_typenum values will change for all file systems. The
669 main effect of this is a change to the NFS server file handles
670 for file systems that use vfc_typenum in their fsid, such as ZFS.
671 It will, however, prevent vfc_typenum from changing when file
672 systems are loaded in a different order for subsequent reboots.
673 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
674 until you are ready to remount all NFS clients after a reboot.
677 Bump the shared library version numbers for libraries that
678 do not use symbol versioning, have changed the ABI compared
679 to stable/8 and which shared library version was not bumped.
680 Done as part of 9.0-RELEASE cycle.
683 During the merge of Capsicum features, the fget(9) KPI was modified.
684 This may require the rebuilding of out-of-tree device drivers --
685 issues have been reported specifically with the nVidia device driver.
686 __FreeBSD_version is bumped to 900041.
688 Also, there is a period between 20110811 and 20110814 where the
689 special devices /dev/{stdin,stdout,stderr} did not work correctly.
690 Building world from a kernel during that window may not work.
693 The packet filter (pf) code has been updated to OpenBSD 4.5.
694 You need to update userland tools to be in sync with kernel.
695 This update breaks backward compatibility with earlier pfsync(4)
696 versions. Care must be taken when updating redundant firewall setups.
699 The following sysctls and tunables are retired on x86 platforms:
701 machdep.hlt_logical_cpus
702 The following sysctl is retired:
703 machdep.hyperthreading_allowed
704 The sysctls were supposed to provide a way to dynamically offline and
705 online selected CPUs on x86 platforms, but the implementation has not
706 been reliable especially with SCHED_ULE scheduler.
707 machdep.hyperthreading_allowed tunable is still available to ignore
708 hyperthreading CPUs at OS level.
709 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
710 where X is an APIC ID of a CPU. Be advised, though, that disabling
711 CPUs in non-uniform fashion will result in non-uniform topology and
712 may lead to sub-optimal system performance with SCHED_ULE, which is
716 cpumask_t type is retired and cpuset_t is used in order to describe
720 Changes to ifconfig(8) for dynamic address family detection mandate
721 that you are running a kernel of 20110525 or later. Make sure to
722 follow the update procedure to boot a new kernel before installing
726 Support for sun4v architecture is officially dropped
729 Several KPI breaking changes have been committed to the mii(4) layer,
730 the PHY drivers and consequently some Ethernet drivers using mii(4).
731 This means that miibus.ko and the modules of the affected Ethernet
732 drivers need to be recompiled.
734 Note to kernel developers: Given that the OUI bit reversion problem
735 was fixed as part of these changes all mii(4) commits related to OUIs,
736 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
737 handling, no longer can be merged verbatim to stable/8 and previous
741 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
742 into their kernel configurations along with 'device pci'.
745 The default NFS client is now the new NFS client, so fstype "newnfs"
746 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
747 Although mounts via fstype "nfs" will usually work without userland
748 changes, it is recommended that the mount(8) and mount_nfs(8)
749 commands be rebuilt from sources and that a link to mount_nfs called
750 mount_oldnfs be created. The new client is compiled into the
751 kernel with "options NFSCL" and this is needed for diskless root
752 file systems. The GENERIC kernel configs have been changed to use
753 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
754 To use the regular/old client, you can "mount -t oldnfs ...". For
755 a diskless root file system, you must also include a line like:
757 vfs.root.mountfrom="oldnfs:"
759 in the boot/loader.conf on the root fs on the NFS server to make
760 a diskless root fs use the old client.
763 The GENERIC kernels for all architectures now default to the new
764 CAM-based ATA stack. It means that all legacy ATA drivers were
765 removed and replaced by respective CAM drivers. If you are using
766 ATA device names in /etc/fstab or other places, make sure to update
767 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
768 where 'Y's are the sequential numbers starting from zero for each type
769 in order of detection, unless configured otherwise with tunables,
770 see cam(4)). There will be symbolic links created in /dev/ to map
771 old adX devices to the respective adaY. They should provide basic
772 compatibility for file systems mounting in most cases, but they do
773 not support old user-level APIs and do not have respective providers
774 in GEOM. Consider using updated management tools with new device names.
776 It is possible to load devices ahci, ata, siis and mvs as modules,
777 but option ATA_CAM should remain in kernel configuration to make ata
778 module work as CAM driver supporting legacy ATA controllers. Device ata
779 still can be used in modular fashion (atacore + ...). Modules atadisk
780 and atapi* are not used and won't affect operation in ATA_CAM mode.
781 Note that to use CAM-based ATA kernel should include CAM devices
782 scbus, pass, da (or explicitly ada), cd and optionally others. All of
783 them are parts of the cam module.
785 ataraid(4) functionality is now supported by the RAID GEOM class.
786 To use it you can load geom_raid kernel module and use graid(8) tool
787 for management. Instead of /dev/arX device names, use /dev/raid/rX.
789 No kernel config options or code have been removed, so if a problem
790 arises, please report it and optionally revert to the old ATA stack.
791 In order to do it you can remove from the kernel config:
796 , and instead add back:
797 device atadisk # ATA disk drives
798 device ataraid # ATA RAID drives
799 device atapicd # ATAPI CDROM drives
800 device atapifd # ATAPI floppy drives
801 device atapist # ATAPI tape drives
804 The default NFS server has been changed to the new server, which
805 was referred to as the experimental server. If you need to switch
806 back to the old NFS server, you must now put the "-o" option on
807 both the mountd and nfsd commands. This can be done using the
808 mountd_flags and nfs_server_flags rc.conf variables until an
809 update to the rc scripts is committed, which is coming soon.
812 The GNU Objective-C runtime library (libobjc), and other Objective-C
813 related components have been removed from the base system. If you
814 require an Objective-C library, please use one of the available ports.
817 ath(4) has been split into bus- and device- modules. if_ath contains
818 the HAL, the TX rate control and the network device code. if_ath_pci
819 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
820 contains the AHB glue. Users need to load both if_ath_pci and if_ath
821 in order to use ath on everything else.
823 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
824 need to load if_ath and if_ath_pci for ath(4) operation.
827 As part of the replacement of sysinstall, the process of building
828 release media has changed significantly. For details, please re-read
829 release(7), which has been updated to reflect the new build process.
832 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
833 is the last available version under GPLv2. It brings a number of new
834 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
835 4.1 and SSE 4.2), better support for powerpc64, a number of new
836 directives, and lots of other small improvements. See the ChangeLog
837 file in contrib/binutils for the full details.
840 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
841 compliant, and will now use half of hash for authentication.
842 This will break interoperability with all stacks (including all
843 actual FreeBSD versions) who implement
844 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
846 The only workaround with such peers is to use another HMAC
847 algorithm for IPsec ("phase 2") authentication.
850 Remove the uio_yield prototype and symbol. This function has
851 been misnamed since it was introduced and should not be
852 globally exposed with this name. The equivalent functionality
853 is now available using kern_yield(curthread->td_user_pri).
854 The function remains undocumented.
857 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
858 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
859 for scalar sysctls is defined but disabled. Code that needs
860 UQUAD to pass the type checking that must compile on older
861 systems where the define is not present can check against
862 __FreeBSD_version >= 900030.
864 The system dialog(1) has been replaced with a new version previously
865 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
866 with the previous version, but the libdialog associated with it has
867 a largely incompatible API. As such, the original version of libdialog
868 will be kept temporarily as libodialog, until its base system consumers
869 are replaced or updated. Bump __FreeBSD_version to 900030.
872 If you are trying to run make universe on a -stable system, and you get
873 the following warning:
874 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
875 unknown. config(8) likely too old."
876 or something similar to it, then you must upgrade your -stable system
877 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
878 stable/8) or build the config from the latest stable/8 branch and
879 install it on your system.
881 Prior to this date, building a current universe on 8-stable system from
882 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
883 error in the first kernel build phase. A new config on those old
884 systems will fix that problem for older versions of -current.
887 The TCP stack has been modified to allow Khelp modules to interact with
888 it via helper hook points and store per-connection data in the TCP
889 control block. Bump __FreeBSD_version to 900029. User space tools that
890 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
894 Generic IEEE 802.3 annex 31B full duplex flow control support has been
895 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
896 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
897 to take advantage of it instead of using custom implementations. This
898 means that these drivers now no longer unconditionally advertise
899 support for flow control but only do so if flow control is a selected
900 media option. This was implemented in the generic support that way in
901 order to allow flow control to be switched on and off via ifconfig(8)
902 with the PHY specific default to typically off in order to protect
903 from unwanted effects. Consequently, if you used flow control with
904 one of the above mentioned drivers you now need to explicitly enable
906 ifconfig bge0 media auto mediaopt flowcontrol
908 Along with the above mentioned changes generic support for setting
909 1000baseT master mode also has been added and brgphy(4), ciphy(4),
910 e1000phy(4) as well as ip1000phy(4) have been converted to take
911 advantage of it. This means that these drivers now no longer take the
912 link0 parameter for selecting master mode but the master media option
913 has to be used instead, for example like in the following:
914 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
916 Selection of master mode now is also available with all other PHY
917 drivers supporting 1000baseT.
920 The TCP stack has received a significant update to add support for
921 modularised congestion control and generally improve the clarity of
922 congestion control decisions. Bump __FreeBSD_version to 900025. User
923 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
924 sockstat) need to be recompiled.
927 The man(1) utility has been replaced by a new version that no longer
928 uses /etc/manpath.config. Please consult man.conf(5) for how to
929 migrate local entries to the new format.
932 The copyright strings printed by login(1) and sshd(8) at the time of a
933 new connection have been removed to follow other operating systems and
937 A workaround for a fixed ld bug has been removed in kernel code,
938 so make sure that your system ld is built from sources after
939 revision 210245 from 2010-07-19 (r211583 if building head kernel
940 on stable/8, r211584 for stable/7; both from 2010-08-21).
941 A symptom of incorrect ld version is different addresses for
942 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
945 The $ipv6_prefer variable in rc.conf(5) has been split into
946 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
948 The $ip6addrctl_policy is a variable to choose a pre-defined
949 address selection policy set by ip6addrctl(8). A value
950 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
953 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
954 flag (see an entry of 20090926) is set on an interface with no
955 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
956 security reason. If you want IPv6 link-local address on all
957 interfaces by default, set this to "YES".
959 The old ipv6_prefer="YES" is equivalent to
960 ipv6_activate_all_interfaces="YES" and
961 ip6addrctl_policy="ipv6_prefer".
964 DTrace has grown support for userland tracing. Due to this, DTrace is
965 now i386 and amd64 only.
966 dtruss(1) is now installed by default on those systems and a new
967 kernel module is needed for userland tracing: fasttrap.
968 No changes to your kernel config file are necessary to enable
969 userland tracing, but you might consider adding 'STRIP=' and
970 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
971 to have informative userland stack traces in DTrace (ustack).
974 The acpi_aiboost(4) driver has been removed in favor of the new
975 aibs(4) driver. You should update your kernel configuration file.
978 BSD grep has been imported to the base system and it is built by
979 default. It is completely BSD licensed, highly GNU-compatible, uses
980 less memory than its GNU counterpart and has a small codebase.
981 However, it is slower than its GNU counterpart, which is mostly
982 noticeable for larger searches, for smaller ones it is measurable
983 but not significant. The reason is complex, the most important factor
984 is that we lack a modern and efficient regex library and GNU
985 overcomes this by optimizing the searches internally. Future work
986 on improving the regex performance is planned, for the meantime,
987 users that need better performance, can build GNU grep instead by
988 setting the WITH_GNU_GREP knob.
991 Due to the import of powerpc64 support, all existing powerpc kernel
992 configuration files must be updated with a machine directive like this:
993 machine powerpc powerpc
995 In addition, an updated config(8) is required to build powerpc kernels
999 A new version of ZFS (version 15) has been merged to -HEAD.
1000 This version uses a python library for the following subcommands:
1001 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1002 For full functionality of these commands the following port must
1003 be installed: sysutils/py-zfs
1006 'vm_page's are now hashed by physical address to an array of mutexes.
1007 Currently this is only used to serialize access to hold_count. Over
1008 time the page queue mutex will be peeled away. This changes the size
1009 of pmap on every architecture. And requires all callers of vm_page_hold
1010 and vm_page_unhold to be updated.
1013 WITH_CTF can now be specified in src.conf (not recommended, there
1014 are some problems with static executables), make.conf (would also
1015 affect ports which do not use GNU make and do not override the
1016 compile targets) or in the kernel config (via "makeoptions
1018 When WITH_CTF was specified there before this was silently ignored,
1019 so make sure that WITH_CTF is not used in places which could lead
1020 to unwanted behavior.
1023 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1024 to allow 32-bit compatibility on non-x86 platforms. All kernel
1025 configurations on amd64 and ia64 platforms using these options must
1026 be modified accordingly.
1029 The utmp user accounting database has been replaced with utmpx,
1030 the user accounting interface standardized by POSIX.
1031 Unfortunately the semantics of utmp and utmpx don't match,
1032 making it practically impossible to support both interfaces.
1033 The user accounting database is used by tools like finger(1),
1034 last(1), talk(1), w(1) and ac(8).
1036 All applications in the base system use utmpx. This means only
1037 local binaries (e.g. from the ports tree) may still use these
1038 utmp database files. These applications must be rebuilt to make
1041 After the system has been upgraded, it is safe to remove the old
1042 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1043 assuming their contents is of no importance anymore. Old wtmp
1044 databases can only be used by last(1) and ac(8) after they have
1045 been converted to the new format using wtmpcvt(1).
1048 Introduce the kernel thread "deadlock resolver" (which can be enabled
1049 via the DEADLKRES option, see NOTES for more details) and the
1050 sleepq_type() function for sleepqueues.
1053 The rc.firewall and rc.firewall6 were unified, and
1054 rc.firewall6 and rc.d/ip6fw were removed.
1055 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1056 variables are obsoleted. Instead, the following new rc
1057 variables are added to rc.d/ipfw:
1059 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1060 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1061 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1063 The meanings correspond to the relevant IPv4 variables.
1069 The default terminal emulation for syscons(4) has been changed
1070 from cons25 to xterm on all platforms except pc98. This means
1071 that the /etc/ttys file needs to be updated to ensure correct
1072 operation of applications on the console.
1074 The terminal emulation style can be toggled per window by using
1075 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1076 options can be used to change the compile-time default back to
1079 To prevent graphical artifacts, make sure the TERM environment
1080 variable is set to match the terminal emulation that is being
1081 performed by syscons(4).
1084 The layout of the structure ieee80211req_scan_result has changed.
1085 Applications that require wireless scan results (e.g. ifconfig(8))
1086 from net80211 need to be recompiled.
1088 Applications such as wpa_supplicant(8) may require a full world
1089 build without using NO_CLEAN in order to get synchronized with the
1093 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1094 There's one kernel module for each firmware. Adding "device iwnfw"
1095 to the kernel configuration file means including all three firmware
1096 images inside the kernel. If you want to include just the one for
1097 your wireless card, use the devices iwn4965fw, iwn5000fw or
1101 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1102 into rc.d/netif. The changes are the following:
1104 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1105 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1106 Note that both variables need the "inet6" keyword at the head.
1108 Do not set $ipv6_network_interfaces manually if you do not
1109 understand what you are doing. It is not needed in most cases.
1111 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1114 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1115 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1117 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1118 all configured interfaces have "inet6 accept_rtadv" in the
1119 $ifconfig_IF_ipv6. These are for backward compatibility.
1121 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1122 functionality of interfaces with no corresponding
1123 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1124 and the default address selection policy of ip6addrctl(8)
1125 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1126 Note that if you want to configure IPv6 functionality on the
1127 disabled interfaces after boot, first you need to clear the flag by
1128 using ifconfig(8) like:
1130 ifconfig em0 inet6 -ifdisabled
1132 If YES, the default address selection policy is set as
1135 The default value of $ipv6_prefer is NO.
1137 4. If your system need to receive Router Advertisement messages,
1138 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1139 scripts automatically invoke rtsol(8) when the interface becomes
1140 UP. The Router Advertisement messages are used for SLAAC
1141 (State-Less Address AutoConfiguration).
1144 802.11s D3.03 support was committed. This is incompatible with the
1145 previous code, which was based on D3.0.
1148 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1149 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1150 control whether accepting Router Advertisement messages or not.
1151 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1152 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1153 The ifconfig(8) utility now supports these flags.
1156 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1157 mount(8) and -a option for df(1) to see them.
1160 The old tunable hw.bus.devctl_disable has been superseded by
1161 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1162 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1166 Remove the option STOP_NMI. The default action is now to use NMI only
1167 for KDB via the newly introduced function stop_cpus_hard() and
1168 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1171 The stable/8 branch created in subversion. This corresponds to the
1172 RELENG_8 branch in CVS.
1175 Bump the shared library version numbers for all libraries that do not
1176 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1177 __FreeBSD_version to 800105.
1180 Due to changes in the implementation of virtual network stack support,
1181 all network-related kernel modules must be recompiled. As this change
1182 breaks the ABI, bump __FreeBSD_version to 800104.
1185 The TOE interface to the TCP syncache has been modified to remove
1186 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1187 The cxgb driver is the only TOE consumer affected by this change, and
1188 needs to be recompiled along with the kernel. As this change breaks
1189 the ABI, bump __FreeBSD_version to 800103.
1192 Padding has been added to struct tcpcb, sackhint and tcpstat in
1193 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1194 maintaining the ABI. However, this change breaks the ABI, so bump
1195 __FreeBSD_version to 800102. User space tools that rely on the size of
1196 any of these structs (e.g. sockstat) need to be recompiled.
1199 The NFS_LEGACYRPC option has been removed along with the old kernel
1200 RPC implementation that this option selected. Kernel configurations
1201 may need to be adjusted.
1204 The network interface device nodes at /dev/net/<interface> have been
1205 removed. All ioctl operations can be performed the normal way using
1206 routing sockets. The kqueue functionality can generally be replaced
1207 with routing sockets.
1210 The documentation from the FreeBSD Documentation Project (Handbook,
1211 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1212 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1215 The ABI of various structures related to the SYSV IPC API have been
1216 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1217 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1221 Layout of struct vnet has changed as routing related variables were
1222 moved to their own Vimage module. Modules need to be recompiled. Bump
1223 __FreeBSD_version to 800099.
1226 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1227 respectively. As long as no more than 16 groups per process are used,
1228 no changes should be visible. When more than 16 groups are used, old
1229 binaries may fail if they call getgroups() or getgrouplist() with
1230 statically sized storage. Recompiling will work around this, but
1231 applications should be modified to use dynamically allocated storage
1232 for group arrays as POSIX.1-2008 does not cap an implementation's
1233 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1235 NFS and portalfs mounts may also be affected as the list of groups is
1236 truncated to 16. Users of NFS who use more than 16 groups, should
1237 take care that negative group permissions are not used on the exported
1238 file systems as they will not be reliable unless a GSSAPI based
1239 authentication method is used.
1242 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1243 option compiles in the support for adaptive spinning for lockmgrs
1244 which want to enable it. The lockinit() function now accepts the flag
1245 LK_ADAPTIVE in order to make the lock object subject to adaptive
1246 spinning when both held in write and read mode.
1249 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1250 changed. User applications that use this ioctl need to be rebuilt.
1253 The layout of struct thread has changed. Kernel and modules need to
1257 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1258 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1261 window(1) has been removed from the base system. It can now be
1262 installed from ports. The port is called misc/window.
1265 The way we are storing and accessing `routing table' entries has
1266 changed. Programs reading the FIB, like netstat, need to be
1270 A new netisr implementation has been added for FreeBSD 8. Network
1271 file system modules, such as igmp, ipdivert, and others, should be
1273 Bump __FreeBSD_version to 800096.
1276 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1280 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1281 Bump __FreeBSD_version to 800094.
1284 Add mnt_xflag field to 'struct mount'. File system modules need to be
1286 Bump __FreeBSD_version to 800093.
1289 The compiling option ADAPTIVE_SX has been retired while it has been
1290 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1291 The KPI for sx_init_flags() changes as accepting flags:
1292 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1293 been introduced in order to handle the reversed logic.
1294 Bump __FreeBSD_version to 800092.
1297 Add support for hierarchical jails. Remove global securelevel.
1298 Bump __FreeBSD_version to 800091.
1301 The layout of struct vnet_net has changed, therefore modules
1303 Bump __FreeBSD_version to 800090.
1306 The newly imported zic(8) produces a new format in the output. Please
1307 run tzsetup(8) to install the newly created data to /etc/localtime.
1310 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1311 hw.usb.* and is now consistent again with previous releases.
1314 802.11 monitor mode support was revised and driver api's were changed.
1315 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1316 of DLT_IEEE802_11. No user-visible data structures were changed but
1317 applications that use DLT_IEEE802_11 may require changes.
1318 Bump __FreeBSD_version to 800088.
1321 The layout of the following structs has changed: sysctl_oid,
1322 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1323 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1324 panics may be experienced. World rebuild is required for
1325 correctly checking networking state from userland.
1326 Bump __FreeBSD_version to 800085.
1329 MLDv2 and Source-Specific Multicast (SSM) have been merged
1330 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1331 The implementation of SSM within FreeBSD's IPv6 stack closely
1332 follows the IPv4 implementation.
1334 For kernel developers:
1336 * The most important changes are that the ip6_output() and
1337 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1338 and this lock has been downgraded to a non-recursive mutex.
1340 * As with the changes to the IPv4 stack to support SSM, filtering
1341 of inbound multicast traffic must now be performed by transport
1342 protocols within the IPv6 stack. This does not apply to TCP and
1343 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1345 * The KPIs used by IPv6 multicast are similar to those used by
1346 the IPv4 stack, with the following differences:
1347 * im6o_mc_filter() is analogous to imo_multicast_filter().
1348 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1349 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1350 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1351 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1352 for MLDv1 have an additional 'timer' argument which is used to
1353 jitter the initial membership report for the solicited-node
1354 multicast membership on-link.
1355 * This is not strictly needed for MLDv2, which already jitters
1356 its report transmissions. However, the 'timer' argument is
1357 preserved in case MLDv1 is active on the interface.
1359 * The KAME linked-list based IPv6 membership implementation has
1360 been refactored to use a vector similar to that used by the IPv4
1362 Code which maintains a list of its own multicast memberships
1363 internally, e.g. carp, has been updated to reflect the new
1366 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1367 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1368 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1369 implementation constraint which needs to be addressed in HEAD.
1371 For application developers:
1373 * The changes are broadly similar to those made for the IPv4
1376 * The use of IPv4 and IPv6 multicast socket options on the same
1377 socket, using mapped addresses, HAS NOT been tested or supported.
1379 * There are a number of issues with the implementation of various
1380 IPv6 multicast APIs which need to be resolved in the API surface
1381 before the implementation is fully compatible with KAME userland
1382 use, and these are mostly to do with interface index treatment.
1384 * The literature available discusses the use of either the delta / ASM
1385 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1386 using setsourcefilter(3)/getsourcefilter(3). For more information
1387 please refer to RFC 3768, 'Socket Interface Extensions for
1388 Multicast Source Filters'.
1390 * Applications which use the published RFC 3678 APIs should be fine.
1392 For systems administrators:
1394 * The mtest(8) utility has been refactored to support IPv6, in
1395 addition to IPv4. Interface addresses are no longer accepted
1396 as arguments, their names must be used instead. The utility
1397 will map the interface name to its first IPv4 address as
1398 returned by getifaddrs(3).
1400 * The ifmcstat(8) utility has also been updated to print the MLDv2
1401 endpoint state and source filter lists via sysctl(3).
1403 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1404 loopback of IPv6 multicast datagrams by default; it defaults to 1
1405 to preserve the existing behaviour. Disabling multicast loopback is
1406 recommended for optimal system performance.
1408 * The IPv6 MROUTING code has been changed to examine this sysctl
1409 instead of attempting to perform a group lookup before looping
1410 back forwarded datagrams.
1412 Bump __FreeBSD_version to 800084.
1415 Implement low-level Bluetooth HCI API.
1416 Bump __FreeBSD_version to 800083.
1419 The layout of struct malloc_type, used by modules to register new
1420 memory allocation types, has changed. Most modules will need to
1421 be rebuilt or panics may be experienced.
1422 Bump __FreeBSD_version to 800081.
1425 Anticipate overflowing inp_flags - add inp_flags2.
1426 This changes most offsets in inpcb, so checking v4 connection
1427 state will require a world rebuild.
1428 Bump __FreeBSD_version to 800080.
1431 Add an llentry to struct route and struct route_in6. Modules
1432 embedding a struct route will need to be recompiled.
1433 Bump __FreeBSD_version to 800079.
1436 The size of rt_metrics_lite and by extension rtentry has changed.
1437 Networking administration apps will need to be recompiled.
1438 The route command now supports show as an alias for get, weighting
1439 of routes, sticky and nostick flags to alter the behavior of stateful
1441 Bump __FreeBSD_version to 800078.
1444 Do not use Giant for kbdmux(4) locking. This is wrong and
1445 apparently causing more problems than it solves. This will
1446 re-open the issue where interrupt handlers may race with
1447 kbdmux(4) in polling mode. Typical symptoms include (but
1448 not limited to) duplicated and/or missing characters when
1449 low level console functions (such as gets) are used while
1450 interrupts are enabled (for example geli password prompt,
1451 mountroot prompt etc.). Disabling kbdmux(4) may help.
1454 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1455 kernel modules referencing any of the above need to be recompiled.
1456 Bump __FreeBSD_version to 800075.
1459 GEOM_PART has become the default partition slicer for storage devices,
1460 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1461 introduces some changes:
1463 MSDOS/EBR: the devices created from MSDOS extended partition entries
1464 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1465 to devices with offset-based names. fstabs may need to be modified.
1467 BSD: the "geometry does not match label" warning is harmless in most
1468 cases but it points to problems in file system misalignment with
1469 disk geometry. The "c" partition is now implicit, covers the whole
1470 top-level drive and cannot be (mis)used by users.
1472 General: Kernel dumps are now not allowed to be written to devices
1473 whose partition types indicate they are meant to be used for file
1474 systems (or, in case of MSDOS partitions, as something else than
1477 Most of these changes date approximately from 200812.
1480 The uscanner(4) driver has been removed from the kernel. This follows
1481 Linux removing theirs in 2.6 and making libusb the default interface
1482 (supported by sane).
1485 The multicast forwarding code has been cleaned up. netstat(1)
1486 only relies on KVM now for printing bandwidth upcall meters.
1487 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1488 ip6_mroute_mod respectively. The config(5) options for statically
1489 compiling this code remain the same, i.e. 'options MROUTING'.
1492 Support for the IFF_NEEDSGIANT network interface flag has been
1493 removed, which means that non-MPSAFE network device drivers are no
1494 longer supported. In particular, if_ar, if_sr, and network device
1495 drivers from the old (legacy) USB stack can no longer be built or
1499 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1500 a bunch of new language catalog files have also been added.
1501 This means that some common libc messages are now localized and
1502 they depend on the LC_MESSAGES environmental variable.
1505 The k8temp(4) driver has been renamed to amdtemp(4) since
1506 support for Family 10 and Family 11 CPU families was added.
1509 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1510 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1512 For kernel developers, the most important changes are that the
1513 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1514 and this lock has been downgraded to a non-recursive mutex.
1516 Transport protocols (UDP, Raw IP) are now responsible for filtering
1517 inbound multicast traffic according to group membership and source
1518 filters. The imo_multicast_filter() KPI exists for this purpose.
1519 Transports which do not use multicast (SCTP, TCP) already reject
1520 multicast by default. Forwarding and receive performance may improve
1521 as a mutex acquisition is no longer needed in the ip_input()
1522 low-level input path. in_addmulti() and in_delmulti() are shimmed
1523 to new KPIs which exist to support SSM in-kernel.
1525 For application developers, it is recommended that loopback of
1526 multicast datagrams be disabled for best performance, as this
1527 will still cause the lock to be taken for each looped-back
1528 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1529 be tuned to 0 to disable loopback by default; it defaults to 1
1530 to preserve the existing behaviour.
1532 For systems administrators, to obtain best performance with
1533 multicast reception and multiple groups, it is always recommended
1534 that a card with a suitably precise hash filter is used. Hash
1535 collisions will still result in the lock being taken within the
1536 transport protocol input path to check group membership.
1538 If deploying FreeBSD in an environment with IGMP snooping switches,
1539 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1540 enabled; this forces 224.0.0.0/24 group membership to be announced
1543 The size of 'struct igmpstat' has changed; netstat needs to be
1544 recompiled to reflect this.
1545 Bump __FreeBSD_version to 800070.
1548 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1549 updated to use it. This requires a buildworld/installworld in order to
1550 update the library and dependencies (usbconfig, etc). Its advisable to
1551 rebuild all ports which uses libusb. More specific directions are given
1552 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1553 libusb are no longer required and can be removed.
1556 A workaround is committed to allow the creation of System V shared
1557 memory segment of size > 2 GB on the 64-bit architectures.
1558 Due to a limitation of the existing ABI, the shm_segsz member
1559 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1560 wrong for large segments. Note that limits must be explicitly
1561 raised to allow such segments to be created.
1564 The layout of struct ifnet has changed, requiring a rebuild of all
1565 network device driver modules.
1568 The /dev handling for the new USB stack has changed, a
1569 buildworld/installworld is required for libusb20.
1572 The new USB2 stack has now been permanently moved in and all kernel and
1573 module names reverted to their previous values (eg, usb, ehci, ohci,
1574 ums, ...). The old usb stack can be compiled in by prefixing the name
1575 with the letter 'o', the old usb modules have been removed.
1576 Updating entry 20090216 for xorg and 20090215 for libmap may still
1580 The rc.conf(5) option if_up_delay has been renamed to
1581 defaultroute_delay to better reflect its purpose. If you have
1582 customized this setting in /etc/rc.conf you need to update it to
1586 xorg 7.4 wants to configure its input devices via hald which does not
1587 yet work with USB2. If the keyboard/mouse does not work in xorg then
1589 Option "AllowEmptyInput" "off"
1590 to your ServerLayout section. This will cause X to use the configured
1591 kbd and mouse sections from your xorg.conf.
1594 The GENERIC kernels for all architectures now default to the new USB2
1595 stack. No kernel config options or code have been removed so if a
1596 problem arises please report it and optionally revert to the old USB
1597 stack. If you are loading USB kernel modules or have a custom kernel
1598 that includes GENERIC then ensure that usb names are also changed over,
1599 eg uftdi -> usb2_serial_ftdi.
1601 Older programs linked against the ports libusb 0.1 need to be
1602 redirected to the new stack's libusb20. /etc/libmap.conf can
1604 # Map old usb library to new one for usb2 stack
1605 libusb-0.1.so.8 libusb20.so.1
1608 All USB ethernet devices now attach as interfaces under the name ueN
1609 (eg. ue0). This is to provide a predictable name as vendors often
1610 change usb chipsets in a product without notice.
1613 The ichsmb(4) driver has been changed to require SMBus slave
1614 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1615 All of the other SMBus controller drivers require left-justified
1616 slave addresses, so this change makes all the drivers provide the
1620 INET6 statistics (struct ip6stat) was updated.
1621 netstat(1) needs to be recompiled.
1624 NTFS has been removed from GENERIC kernel on amd64 to match
1625 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1626 will load ntfs.ko module automatically when NTFS support is
1627 actually needed, unless ntfs.ko is not installed or security
1628 level prohibits loading kernel modules. If either is the case,
1629 "options NTFS" has to be added into kernel config.
1632 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1633 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1634 800061. User space tools that rely on the size of struct tcpcb in
1635 tcp_var.h (e.g. sockstat) need to be recompiled.
1638 ng_tty(4) module updated to match the new TTY subsystem.
1639 Due to API change, user-level applications must be updated.
1640 New API support added to mpd5 CVS and expected to be present
1641 in next mpd5.3 release.
1644 With __FreeBSD_version 800060 the makefs tool is part of
1645 the base system (it was a port).
1648 The afdata and ifnet locks have been changed from mutexes to
1649 rwlocks, network modules will need to be re-compiled.
1652 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1653 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1654 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1655 architecture and 40 bytes on 64-bit architecture. The userland
1656 applications "arp" and "ndp" have been updated accordingly.
1657 The output from "netstat -r" shows only routing entries and
1658 none of the L2 information.
1661 __FreeBSD_version 800057 marks the switchover from the
1662 binary ath hal to source code. Users must add the line:
1664 options AH_SUPPORT_AR5416
1666 to their kernel config files when specifying:
1670 The ath_hal module no longer exists; the code is now compiled
1671 together with the driver in the ath module. It is now
1672 possible to tailor chip support (i.e. reduce the set of chips
1673 and thereby the code size); consult ath_hal(4) for details.
1676 __FreeBSD_version 800054 adds memory barriers to
1677 <machine/atomic.h>, new interfaces to ifnet to facilitate
1678 multiple hardware transmit queues for cards that support
1679 them, and a lock-less ring-buffer implementation to
1680 enable drivers to more efficiently manage queueing of
1684 A new version of ZFS (version 13) has been merged to -HEAD.
1685 This version has zpool attribute "listsnapshots" off by
1686 default, which means "zfs list" does not show snapshots,
1687 and is the same as Solaris behavior.
1690 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1693 The uhci, ohci, ehci and slhci USB Host controller drivers have
1694 been put into separate modules. If you load the usb module
1695 separately through loader.conf you will need to load the
1696 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1697 controller add the following to loader.conf:
1703 The ABI used by the PMC toolset has changed. Please keep
1704 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1708 atapci kernel module now includes only generic PCI ATA
1709 driver. AHCI driver moved to ataahci kernel module.
1710 All vendor-specific code moved into separate kernel modules:
1711 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1712 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1713 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1714 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1717 The TTY subsystem of the kernel has been replaced by a new
1718 implementation, which provides better scalability and an
1719 improved driver model. Most common drivers have been migrated to
1720 the new TTY subsystem, while others have not. The following
1721 drivers have not yet been ported to the new TTY layer:
1724 cy, digi, rc, rp, sio
1730 ng_h4, ng_tty, ppp, sl, snp
1732 Adding these drivers to your kernel configuration file shall
1733 cause compilation to fail.
1736 ntpd has been upgraded to 4.2.4p5.
1739 OpenSSH has been upgraded to 5.1p1.
1741 For many years, FreeBSD's version of OpenSSH preferred DSA
1742 over RSA for host and user authentication keys. With this
1743 upgrade, we've switched to the vendor's default of RSA over
1744 DSA. This may cause upgraded clients to warn about unknown
1745 host keys even for previously known hosts. Users should
1746 follow the usual procedure for verifying host keys before
1747 accepting the RSA key.
1749 This can be circumvented by setting the "HostKeyAlgorithms"
1750 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1753 Please note that the sequence of keys offered for
1754 authentication has been changed as well. You may want to
1755 specify IdentityFile in a different order to revert this
1759 The sio(4) driver has been removed from the i386 and amd64
1760 kernel configuration files. This means uart(4) is now the
1761 default serial port driver on those platforms as well.
1763 To prevent collisions with the sio(4) driver, the uart(4) driver
1764 uses different names for its device nodes. This means the
1765 onboard serial port will now most likely be called "ttyu0"
1766 instead of "ttyd0". You may need to reconfigure applications to
1767 use the new device names.
1769 When using the serial port as a boot console, be sure to update
1770 /boot/device.hints and /etc/ttys before booting the new kernel.
1771 If you forget to do so, you can still manually specify the hints
1772 at the loader prompt:
1774 set hint.uart.0.at="isa"
1775 set hint.uart.0.port="0x3F8"
1776 set hint.uart.0.flags="0x10"
1777 set hint.uart.0.irq="4"
1781 The gpt(8) utility has been removed. Use gpart(8) to partition
1785 The version that Linuxulator emulates was changed from 2.4.2
1786 to 2.6.16. If you experience any problems with Linux binaries
1787 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1788 if it fixes the problem contact emulation mailing list.
1791 ISDN4BSD (I4B) was removed from the src tree. You may need to
1792 update a your kernel configuration and remove relevant entries.
1795 I have checked in code to support multiple routing tables.
1796 See the man pages setfib(1) and setfib(2).
1797 This is a hopefully backwards compatible version,
1798 but to make use of it you need to compile your kernel
1799 with options ROUTETABLES=2 (or more up to 16).
1802 The 802.11 wireless support was redone to enable multi-bss
1803 operation on devices that are capable. The underlying device
1804 is no longer used directly but instead wlanX devices are
1805 cloned with ifconfig. This requires changes to rc.conf files.
1806 For example, change:
1807 ifconfig_ath0="WPA DHCP"
1810 ifconfig_wlan0="WPA DHCP"
1811 see rc.conf(5) for more details. In addition, mergemaster of
1812 /etc/rc.d is highly recommended. Simultaneous update of userland
1813 and kernel wouldn't hurt either.
1815 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1816 modules were merged into the base wlan module. All references
1817 to these modules (e.g. in kernel config files) must be removed.
1820 psm(4) has gained write(2) support in native operation level.
1821 Arbitrary commands can be written to /dev/psm%d and status can
1822 be read back from it. Therefore, an application is responsible
1823 for status validation and error recovery. It is a no-op in
1824 other operation levels.
1827 Support for KSE threading has been removed from the kernel. To
1828 run legacy applications linked against KSE libmap.conf may
1829 be used. The following libmap.conf may be used to ensure
1830 compatibility with any prior release:
1832 libpthread.so.1 libthr.so.1
1833 libpthread.so.2 libthr.so.2
1834 libkse.so.3 libthr.so.3
1837 The layout of struct vmspace has changed. This affects libkvm
1838 and any executables that link against libkvm and use the
1839 kvm_getprocs() function. In particular, but not exclusively,
1840 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1841 The effects are minimal, but it's advisable to upgrade world
1845 The latest em driver no longer has support in it for the
1846 82575 adapter, this is now moved to the igb driver. The
1847 split was done to make new features that are incompatible
1848 with older hardware easier to do.
1851 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1852 likewise the kernel option is now GEOM_LINUX_LVM.
1855 The default NFS mount mode has changed from UDP to TCP for
1856 increased reliability. If you rely on (insecurely) NFS
1857 mounting across a firewall you may need to update your
1861 Belatedly note the addition of m_collapse for compacting
1865 The fts(3) structures have been changed to use adequate
1866 integer types for their members and so to be able to cope
1867 with huge file trees. The old fts(3) ABI is preserved
1868 through symbol versioning in libc, so third-party binaries
1869 using fts(3) should still work, although they will not take
1870 advantage of the extended types. At the same time, some
1871 third-party software might fail to build after this change
1872 due to unportable assumptions made in its source code about
1873 fts(3) structure members. Such software should be fixed
1874 by its vendor or, in the worst case, in the ports tree.
1875 FreeBSD_version 800015 marks this change for the unlikely
1876 case that a portable fix is impossible.
1879 To upgrade to -current after this date, you must be running
1880 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1881 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1884 The ADAPTIVE_GIANT kernel option has been retired because its
1885 functionality is the default now.
1888 The AT keyboard emulation of sunkbd(4) has been turned on
1889 by default. In order to make the special symbols of the Sun
1890 keyboards driven by sunkbd(4) work under X these now have
1891 to be configured the same way as Sun USB keyboards driven
1892 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1894 Option "XkbLayout" "us"
1895 Option "XkbRules" "xorg"
1896 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1899 It has been decided that it is desirable to provide ABI
1900 backwards compatibility to the FreeBSD 4/5/6 versions of the
1901 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1902 broken with the introduction of PCI domain support (see the
1903 20070930 entry). Unfortunately, this required the ABI of
1904 PCIOCGETCONF to be broken again in order to be able to
1905 provide backwards compatibility to the old version of that
1906 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1907 again. As for prominent ports this affects neither pciutils
1908 nor xorg-server this time, the hal port needs to be rebuilt
1912 The misnamed kthread_create() and friends have been renamed
1913 to kproc_create() etc. Many of the callers already
1914 used kproc_start()..
1915 I will return kthread_create() and friends in a while
1916 with implementations that actually create threads, not procs.
1917 Renaming corresponds with version 800002.
1926 Avoid using make -j when upgrading. While generally safe, there are
1927 sometimes problems using -j to upgrade. If your upgrade fails with
1928 -j, please try again without -j. From time to time in the past there
1929 have been problems using -j with buildworld and/or installworld. This
1930 is especially true when upgrading between "distant" versions (eg one
1931 that cross a major release boundary or several minor releases, or when
1932 several months have passed on the -current branch).
1934 Sometimes, obscure build problems are the result of environment
1935 poisoning. This can happen because the make utility reads its
1936 environment when searching for values for global variables. To run
1937 your build attempts in an "environmental clean room", prefix all make
1938 commands with 'env -i '. See the env(1) manual page for more details.
1940 When upgrading from one major version to another it is generally best
1941 to upgrade to the latest code in the currently installed branch first,
1942 then do an upgrade to the new branch. This is the best-tested upgrade
1943 path, and has the highest probability of being successful. Please try
1944 this approach before reporting problems with a major version upgrade.
1946 When upgrading a live system, having a root shell around before
1947 installing anything can help undo problems. Not having a root shell
1948 around can lead to problems if pam has changed too much from your
1949 starting point to allow continued authentication after the upgrade.
1953 When upgrading the boot ZFS pool to a new version, always follow
1956 1.) recompile and reinstall the ZFS boot loader and boot block
1957 (this is part of "make buildworld" and "make installworld")
1959 2.) update the ZFS boot block on your boot drive
1961 The following example updates the ZFS boot block on the first
1962 partition (freebsd-boot) of a GPT partitioned drive ad0:
1963 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1965 Non-boot pools do not need these updates.
1969 If you are updating from a prior version of FreeBSD (even one just
1970 a few days old), you should follow this procedure. It is the most
1971 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1973 make kernel-toolchain
1974 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1975 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1977 To test a kernel once
1978 ---------------------
1979 If you just want to boot a kernel once (because you are not sure
1980 if it works, or if you want to boot a known bad kernel to provide
1981 debugging information) run
1982 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1983 nextboot -k testkernel
1985 To just build a kernel when you know that it won't mess you up
1986 --------------------------------------------------------------
1987 This assumes you are already running a CURRENT system. Replace
1988 ${arch} with the architecture of your machine (e.g. "i386",
1989 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1991 cd src/sys/${arch}/conf
1992 config KERNEL_NAME_HERE
1993 cd ../compile/KERNEL_NAME_HERE
1998 If this fails, go to the "To build a kernel" section.
2000 To rebuild everything and install it on the current system.
2001 -----------------------------------------------------------
2002 # Note: sometimes if you are running current you gotta do more than
2003 # is listed here if you are upgrading from a really old current.
2005 <make sure you have good level 0 dumps>
2007 make kernel KERNCONF=YOUR_KERNEL_HERE
2009 <reboot in single user> [3]
2016 To cross-install current onto a separate partition
2017 --------------------------------------------------
2018 # In this approach we use a separate partition to hold
2019 # current's root, 'usr', and 'var' directories. A partition
2020 # holding "/", "/usr" and "/var" should be about 2GB in
2023 <make sure you have good level 0 dumps>
2026 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2027 <maybe newfs current's root partition>
2028 <mount current's root partition on directory ${CURRENT_ROOT}>
2029 make installworld DESTDIR=${CURRENT_ROOT}
2030 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2031 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2032 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2033 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2034 <reboot into current>
2035 <do a "native" rebuild/install as described in the previous section>
2036 <maybe install compatibility libraries from ports/misc/compat*>
2040 To upgrade in-place from stable to current
2041 ----------------------------------------------
2042 <make sure you have good level 0 dumps>
2044 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2046 <reboot in single user> [3]
2053 Make sure that you've read the UPDATING file to understand the
2054 tweaks to various things you need. At this point in the life
2055 cycle of current, things change often and you are on your own
2056 to cope. The defaults can also change, so please read ALL of
2057 the UPDATING entries.
2059 Also, if you are tracking -current, you must be subscribed to
2060 freebsd-current@freebsd.org. Make sure that before you update
2061 your sources that you have read and understood all the recent
2062 messages there. If in doubt, please track -stable which has
2063 much fewer pitfalls.
2065 [1] If you have third party modules, such as vmware, you
2066 should disable them at this point so they don't crash your
2069 [3] From the bootblocks, boot -s, and then do
2074 adjkerntz -i # if CMOS is wall time
2075 Also, when doing a major release upgrade, it is required that
2076 you boot into single user mode to do the installworld.
2078 [4] Note: This step is non-optional. Failure to do this step
2079 can result in a significant reduction in the functionality of the
2080 system. Attempting to do it by hand is not recommended and those
2081 that pursue this avenue should read this file carefully, as well
2082 as the archives of freebsd-current and freebsd-hackers mailing lists
2083 for potential gotchas. The -U option is also useful to consider.
2084 See mergemaster(8) for more information.
2086 [5] Usually this step is a noop. However, from time to time
2087 you may need to do this if you get unknown user in the following
2088 step. It never hurts to do it all the time. You may need to
2089 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2090 install) after the buildworld before this step if you last updated
2091 from current before 20130425 or from -stable before 20130430.
2093 [6] This only deletes old files and directories. Old libraries
2094 can be deleted by "make delete-old-libs", but you have to make
2095 sure that no program is using those libraries anymore.
2097 [8] In order to have a kernel that can run the 4.x binaries needed to
2098 do an installworld, you must include the COMPAT_FREEBSD4 option in
2099 your kernel. Failure to do so may leave you with a system that is
2100 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2101 required to run the 5.x binaries on more recent kernels. And so on
2102 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2104 Make sure that you merge any new devices from GENERIC since the
2105 last time you updated your kernel config file.
2107 [9] When checking out sources, you must include the -P flag to have
2108 cvs prune empty directories.
2110 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2111 "?=" instead of the "=" assignment operator, so that buildworld can
2112 override the CPUTYPE if it needs to.
2114 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2115 not on the command line, or in /etc/make.conf. buildworld will
2116 warn if it is improperly defined.
2119 This file contains a list, in reverse chronological order, of major
2120 breakages in tracking -current. It is not guaranteed to be a complete
2121 list of such breakages, and only contains entries since October 10, 2007.
2122 If you need to see UPDATING entries from before that date, you will need
2123 to fetch an UPDATING file from an older FreeBSD release.
2125 Copyright information:
2127 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2129 Redistribution, publication, translation and use, with or without
2130 modification, in full or in part, in any form or format of this
2131 document are permitted without further permission from the author.
2133 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2134 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2135 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2136 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2137 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2138 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2139 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2140 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2141 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2142 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2143 POSSIBILITY OF SUCH DAMAGE.
2145 Contact Warner Losh if you have any questions about your use of