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 libatf-c and libatf-c++ major versions were downgraded to 0 and
21 1 respectively to match the upstream numbers. They were out of
22 sync because, when they were originally added to FreeBSD, the
23 upstream versions were not respected. These libraries are private
24 and not yet built by default, so renumbering them should be a
25 non-issue. However, unclean source trees will yield broken test
26 programs once the operator executes "make delete-old-libs" after a
29 If you are using WITH_TESTS=yes (not the default), wipe the object
30 tree and rebuild from scratch to prevent spurious test failures.
31 This is only needed once: the old, misnumbered libraries have been
32 added to OptionalObsoleteFiles.inc so they will be removed during a
36 The ixgbe tunables now match their sysctl counterparts, for example:
37 hw.ixgbe.enable_aim => hw.ix.enable_aim
38 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
41 The NFSv4.1 server committed by r269398 changes the internal
42 function call interfaces used between the NFS and krpc modules.
43 As such, __FreeBSD_version was bumped.
46 The default unbound configuration has been modified to address
47 issues with reverse lookups on networks that use private
48 address ranges. If you use the local_unbound service, run
49 "service local_unbound setup" as root to regenerate your
50 configuration, then "service local_unbound reload" to load the
54 It is no longer necessary to include the dwarf version in your DEBUG
55 options in your kernel config file. The bug that required it to be
56 placed in the config file has bene fixed. DEBUG should now just
57 contain -g. The build system will automatically update things
58 to do the right thing.
61 Several ABI breaking changes were merged to CTL and new iSCSI code.
62 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
63 iscsictl need to be rebuilt to work with a new kernel.
66 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
67 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
68 which differs from the behaviour controlled by this knob.)
71 On i386 and amd64 systems, the onifconsole flag is now set by default
72 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
73 as a login TTY if it is set in the bootloader as an active kernel
74 console. No changes in behavior should result otherwise. To revert to
75 the previous behavior, set ttyu0 to "off" in /etc/ttys.
78 Clang and llvm have been upgraded to 3.4.1 release.
81 Clang and llvm have been upgraded to 3.4 release.
84 If a Makefile in a tests/ directory was auto-generating a Kyuafile
85 instead of providing an explicit one, this would prevent such
86 Makefile from providing its own Kyuafile in the future during
87 NO_CLEAN builds. This has been fixed in the Makefiles but manual
88 intervention is needed to clean an objdir if you use NO_CLEAN:
89 # find /usr/obj -name Kyuafile | xargs rm -f
92 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
93 capability mode support. Please note that enabling the feature in
94 kernel is still highly recommended.
97 OpenSSH is now built with sandbox support, and will use sandbox as
98 the default privilege separation method. This requires Capsicum
99 capability mode support in kernel.
102 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
103 been deprecated and will not be part of FreeBSD 11.0 and later
104 releases. If you use this driver, please consider switching to
105 the nfe(4) driver instead.
111 The behavior of gss_pseudo_random() for the krb5 mechanism
112 has changed, for applications requesting a longer random string
113 than produced by the underlying enctype's pseudo-random() function.
114 In particular, the random string produced from a session key of
115 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
116 be different at the 17th octet and later, after this change.
117 The counter used in the PRF+ construction is now encoded as a
118 big-endian integer in accordance with RFC 4402.
119 __FreeBSD_version is bumped to 1000701.
122 The WITHOUT_ATF build knob has been removed and its functionality
123 has been subsumed into the more generic WITHOUT_TESTS. If you were
124 using the former to disable the build of the ATF libraries, you
125 should change your settings to use the latter.
128 The default version of mtree is nmtree which is obtained from
129 NetBSD. The output is generally the same, but may vary
130 slightly. If you found you need identical output adding
131 "-F freebsd9" to the command line should do the trick. For the
132 time being, the old mtree is available as fmtree.
135 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
136 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
137 1.1.4_8 and verify bsdyml not linked in, before running "make
139 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
141 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
144 The rc.d/jail script has been updated to support jail(8)
145 configuration file. The "jail_<jname>_*" rc.conf(5) variables
146 for per-jail configuration are automatically converted to
147 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
148 This is transparently backward compatible. See below about some
149 incompatibilities and rc.conf(5) manual page for more details.
151 These variables are now deprecated in favor of jail(8) configuration
152 file. One can use "rc.d/jail config <jname>" command to generate
153 a jail(8) configuration file in /var/run/jail.<jname>.conf without
154 running the jail(8) utility. The default pathname of the
155 configuration file is /etc/jail.conf and can be specified by
156 using $jail_conf or $jail_<jname>_conf variables.
158 Please note that jail_devfs_ruleset accepts an integer at
159 this moment. Please consider to rewrite the ruleset name
163 BIND has been removed from the base system. If all you need
164 is a local resolver, simply enable and start the local_unbound
165 service instead. Otherwise, several versions of BIND are
166 available in the ports tree. The dns/bind99 port is one example.
168 With this change, nslookup(1) and dig(1) are no longer in the base
169 system. Users should instead use host(1) and drill(1) which are
170 in the base system. Alternatively, nslookup and dig can
171 be obtained by installing the dns/bind-tools port.
174 With the addition of unbound(8), a new unbound user is now
175 required during installworld. "mergemaster -p" can be used to
176 add the user prior to installworld, as documented in the handbook.
179 OpenSSH is now built with DNSSEC support, and will by default
180 silently trust signed SSHFP records. This can be controlled with
181 the VerifyHostKeyDNS client configuration setting. DNSSEC support
182 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
185 The GNU Compiler Collection and C++ standard library (libstdc++)
186 are no longer built by default on platforms where clang is the system
187 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
191 The PROCDESC kernel option is now part of the GENERIC kernel
192 configuration and is required for the rwhod(8) to work.
193 If you are using custom kernel configuration, you should include
197 The API and ABI related to the Capsicum framework was modified
198 in backward incompatible way. The userland libraries and programs
199 have to be recompiled to work with the new kernel. This includes the
200 following libraries and programs, but the whole buildworld is
201 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
202 kdump, procstat, rwho, rwhod, uniq.
205 AES-NI intrinsic support has been added to gcc. The AES-NI module
206 has been updated to use this support. A new gcc is required to build
207 the aesni module on both i386 and amd64.
210 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
211 Thus "device padlock_rng" and "device rdrand_rng" should be
212 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
215 WITH_ICONV has been split into two feature sets. WITH_ICONV now
216 enables just the iconv* functionality and is now on by default.
217 WITH_LIBICONV_COMPAT enables the libiconv api and link time
218 compatability. Set WITHOUT_ICONV to build the old way.
219 If you have been using WITH_ICONV before, you will very likely
220 need to turn on WITH_LIBICONV_COMPAT.
223 INVARIANTS option now enables DEBUG for code with OpenSolaris and
224 Illumos origin, including ZFS. If you have INVARIANTS in your
225 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
227 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
228 locks if WITNESS option was set. Because that generated a lot of
229 witness(9) reports and all of them were believed to be false
230 positives, this is no longer done. New option OPENSOLARIS_WITNESS
231 can be used to achieve the previous behavior.
234 Timer values in IPv6 data structures now use time_uptime instead
235 of time_second. Although this is not a user-visible functional
236 change, userland utilities which directly use them---ndp(8),
237 rtadvd(8), and rtsold(8) in the base system---need to be updated
241 find -delete can now delete the pathnames given as arguments,
242 instead of only files found below them or if the pathname did
243 not contain any slashes. Formerly, the following error message
246 find: -delete: <path>: relative path potentially not safe
248 Deleting the pathnames given as arguments can be prevented
249 without error messages using -mindepth 1 or by changing
250 directory and passing "." as argument to find. This works in the
251 old as well as the new version of find.
254 Behavior of devfs rules path matching has been changed.
255 Pattern is now always matched against fully qualified devfs
256 path and slash characters must be explicitly matched by
257 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
258 subdirectories must be reviewed.
261 The default ARM ABI has changed to the ARM EABI. The old ABI is
262 incompatible with the ARM EABI and all programs and modules will
263 need to be rebuilt to work with a new kernel.
265 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
267 NOTE: Support for the old ABI will be removed in the future and
268 users are advised to upgrade.
271 pkg_install has been disconnected from the build if you really need it
272 you should add WITH_PKGTOOLS in your src.conf(5).
275 Most of network statistics structures were changed to be able
276 keep 64-bits counters. Thus all tools, that work with networking
277 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
280 Fix targets that run multiple make's to use && rather than ;
281 so that subsequent steps depend on success of previous.
283 NOTE: if building 'universe' with -j* on stable/8 or stable/9
284 it would be better to start the build using bmake, to avoid
285 overloading the machine.
288 Fix a bug that allowed a tracing process (e.g. gdb) to write
289 to a memory-mapped file in the traced process's address space
290 even if neither the traced process nor the tracing process had
291 write access to that file.
294 CVS has been removed from the base system. An exact copy
295 of the code is available from the devel/cvs port.
298 Some people report the following error after the switch to bmake:
300 make: illegal option -- J
301 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
303 *** [buildworld] Error code 2
305 this likely due to an old instance of make in
306 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
307 which src/Makefile will use that blindly, if it exists, so if
308 you see the above error:
310 rm -rf `make -V MAKEPATH`
315 Use bmake by default.
316 Whereas before one could choose to build with bmake via
317 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
318 make. The goal is to remove these knobs for 10-RELEASE.
320 It is worth noting that bmake (like gmake) treats the command
321 line as the unit of failure, rather than statements within the
322 command line. Thus '(cd some/where && dosomething)' is safer
323 than 'cd some/where; dosomething'. The '()' allows consistent
324 behavior in parallel build.
327 Fix a bug that allows NFS clients to issue READDIR on files.
330 The WITHOUT_IDEA option has been removed because
331 the IDEA patent expired.
334 The sysctl which controls TRIM support under ZFS has been renamed
335 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
339 The mergemaster command now uses the default MAKEOBJDIRPREFIX
340 rather than creating it's own in the temporary directory in
341 order allow access to bootstrapped versions of tools such as
342 install and mtree. When upgrading from version of FreeBSD where
343 the install command does not support -l, you will need to
344 install a new mergemaster command if mergemaster -p is required.
345 This can be accomplished with the command (cd src/usr.sbin/mergemaster
349 Legacy ATA stack, disabled and replaced by new CAM-based one since
350 FreeBSD 9.0, completely removed from the sources. Kernel modules
351 atadisk and atapi*, user-level tools atacontrol and burncd are
352 removed. Kernel option `options ATA_CAM` is now permanently enabled
356 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
357 and socketpair(2). Software, in particular Kerberos, may
358 automatically detect and use these during building. The resulting
359 binaries will not work on older kernels.
362 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
363 information, see the respective 20130304 entry).
366 Recent commits to callout(9) changed the size of struct callout,
367 so the KBI is probably heavily disturbed. Also, some functions
368 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
369 by macros. Every kernel module using it won't load, so rebuild
372 The ctl device has been re-enabled in GENERIC for i386 and amd64,
373 but does not initialize by default (because of the new CTL_DISABLE
374 option) to save memory. To re-enable it, remove the CTL_DISABLE
375 option from the kernel config file or set kern.cam.ctl.disable=0
376 in /boot/loader.conf.
379 The ctl device has been disabled in GENERIC for i386 and amd64.
380 This was done due to the extra memory being allocated at system
381 initialisation time by the ctl driver which was only used if
382 a CAM target device was created. This makes a FreeBSD system
383 unusable on 128MB or less of RAM.
386 A new compression method (lz4) has been merged to -HEAD. Please
387 refer to zpool-features(7) for more information.
389 Please refer to the "ZFS notes" section of this file for information
390 on upgrading boot ZFS pools.
393 A BSD-licensed patch(1) variant has been added and is installed
394 as bsdpatch, being the GNU version the default patch.
395 To inverse the logic and use the BSD-licensed one as default,
396 while having the GNU version installed as gnupatch, rebuild
397 and install world with the WITH_BSD_PATCH knob set.
400 Due to the use of the new -l option to install(1) during build
401 and install, you must take care not to directly set the INSTALL
402 make variable in your /etc/make.conf, /etc/src.conf, or on the
403 command line. If you wish to use the -C flag for all installs
404 you may be able to add INSTALL+=-C to /etc/make.conf or
408 The install(1) option -M has changed meaning and now takes an
409 argument that is a file or path to append logs to. In the
410 unlikely event that -M was the last option on the command line
411 and the command line contained at least two files and a target
412 directory the first file will have logs appended to it. The -M
413 option served little practical purpose in the last decade so its
414 use is expected to be extremely rare.
417 After switching to Clang as the default compiler some users of ZFS
418 on i386 systems started to experience stack overflow kernel panics.
419 Please consider using 'options KSTACK_PAGES=4' in such configurations.
422 GEOM_LABEL now mangles label names read from file system metadata.
423 Mangling affect labels containing spaces, non-printable characters,
424 '%' or '"'. Device names in /etc/fstab and other places may need to
428 By default, only the 10 most recent kernel dumps will be saved. To
429 restore the previous behaviour (no limit on the number of kernel dumps
430 stored in the dump directory) add the following line to /etc/rc.conf:
435 With the addition of auditdistd(8), a new auditdistd user is now
436 required during installworld. "mergemaster -p" can be used to
437 add the user prior to installworld, as documented in the handbook.
440 The sin6_scope_id member variable in struct sockaddr_in6 is now
441 filled by the kernel before passing the structure to the userland via
442 sysctl or routing socket. This means the KAME-specific embedded scope
443 id in sin6_addr.s6_addr[2] is always cleared in userland application.
444 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
445 __FreeBSD_version is bumped to 1000025.
448 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
449 This means that the world and kernel will be compiled with clang
450 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
451 and /usr/bin/cpp. To disable this behavior and revert to building
452 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
453 of current may need to bootstrap WITHOUT_CLANG first if the clang
454 build fails (its compatibility window doesn't extend to the 9 stable
458 The IPFIREWALL_FORWARD kernel option has been removed. Its
459 functionality now turned on by default.
462 The ZERO_COPY_SOCKET kernel option has been removed and
463 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
464 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
465 mechanism which is not safe and may result in kernel crashes.
466 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
467 driver supports disposeable external page sized mbuf storage.
468 Proper replacements for both zero-copy mechanisms are under
469 consideration and will eventually lead to complete removal
470 of the two kernel options.
473 The IPv4 network stack has been converted to network byte
474 order. The following modules need to be recompiled together
475 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
476 pf(4), ipfw(4), ng_ipfw(4), stf(4).
479 Support for non-MPSAFE filesystems was removed from VFS. The
480 VFS_VERSION was bumped, all filesystem modules shall be
484 All the non-MPSAFE filesystems have been disconnected from
485 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
486 portalfs, smbfs, xfs.
489 The interface cloning API and ABI has changed. The following
490 modules need to be recompiled together with kernel:
491 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
492 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
493 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
496 The sdhci driver was split in two parts: sdhci (generic SD Host
497 Controller logic) and sdhci_pci (actual hardware driver).
498 No kernel config modifications are required, but if you
499 load sdhc as a module you must switch to sdhci_pci instead.
502 Import the FUSE kernel and userland support into base system.
505 The GNU sort(1) program has been removed since the BSD-licensed
506 sort(1) has been the default for quite some time and no serious
507 problems have been reported. The corresponding WITH_GNU_SORT
511 The pfil(9) API/ABI for AF_INET family has been changed. Packet
512 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
516 The net80211(4) ABI has been changed to allow for improved driver
517 PS-POLL and power-save support. All wireless drivers need to be
518 recompiled to work with the new kernel.
521 The random(4) support for the VIA hardware random number
522 generator (`PADLOCK') is no longer enabled unconditionally.
523 Add the padlock_rng device in the custom kernel config if
524 needed. The GENERIC kernels on i386 and amd64 do include the
525 device, so the change only affects the custom kernel
529 The pf(4) packet filter ABI has been changed. pfctl(8) and
530 snmp_pf module need to be recompiled to work with new kernel.
533 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
534 to -HEAD. Pools that have empty_bpobj in active state can not be
535 imported read-write with ZFS implementations that do not support
536 this feature. For more information read the zpool-features(5)
540 The sparc64 ZFS loader has been changed to no longer try to auto-
541 detect ZFS providers based on diskN aliases but now requires these
542 to be explicitly listed in the OFW boot-device environment variable.
545 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
546 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
547 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
550 The following sysctls and tunables have been renamed for consistency
551 with other variables:
552 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
553 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
556 The sort utility has been replaced with BSD sort. For now, GNU sort
557 is also available as "gnusort" or the default can be set back to
558 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
559 installed as "bsdsort".
562 A new version of ZFS (pool version 5000) has been merged to -HEAD.
563 Starting with this version the old system of ZFS pool versioning
564 is superseded by "feature flags". This concept enables forward
565 compatibility against certain future changes in functionality of ZFS
566 pools. The first read-only compatible "feature flag" for ZFS pools
567 is named "com.delphix:async_destroy". For more information
568 read the new zpool-features(5) manual page.
569 Please refer to the "ZFS notes" section of this file for information
570 on upgrading boot ZFS pools.
573 The malloc(3) implementation embedded in libc now uses sources imported
574 as contrib/jemalloc. The most disruptive API change is to
575 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
576 delete it prior to installworld, and optionally re-create it using the
577 new format after rebooting. See malloc.conf(5) for details
578 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
582 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
583 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
584 now spelled mips. This is to aid compatibility with third-party
585 software that expects this naming scheme in uname(3). Little-endian
586 settings are unchanged. If you are updating a big-endian mips64 machine
587 from before this change, you may need to set MACHINE_ARCH=mips64 in
588 your environment before the new build system will recognize your machine.
591 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
595 Now unix domain sockets behave "as expected" on nullfs(5). Previously
596 nullfs(5) did not pass through all behaviours to the underlying layer,
597 as a result if we bound to a socket on the lower layer we could connect
598 only to the lower path; if we bound to the upper layer we could connect
599 only to the upper path. The new behavior is one can connect to both the
600 lower and the upper paths regardless what layer path one binds to.
603 The getifaddrs upgrade path broken with 20111215 has been restored.
604 If you have upgraded in between 20111215 and 20120209 you need to
605 recompile libc again with your kernel. You still need to recompile
606 world to be able to configure CARP but this restriction already
610 The set_rcvar() function has been removed from /etc/rc.subr. All
611 base and ports rc.d scripts have been updated, so if you have a
612 port installed with a script in /usr/local/etc/rc.d you can either
613 hand-edit the rcvar= line, or reinstall the port.
615 An easy way to handle the mass-update of /etc/rc.d:
616 rm /etc/rc.d/* && mergemaster -i
619 panic(9) now stops other CPUs in the SMP systems, disables interrupts
620 on the current CPU and prevents other threads from running.
621 This behavior can be reverted using the kern.stop_scheduler_on_panic
623 The new behavior can be incompatible with kern.sync_on_panic.
626 The carp(4) facility has been changed significantly. Configuration
627 of the CARP protocol via ifconfig(8) has changed, as well as format
628 of CARP events submitted to devd(8) has changed. See manual pages
629 for more information. The arpbalance feature of carp(4) is currently
630 not supported anymore.
632 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
633 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
634 need to be recompiled.
637 The acpi_wmi(4) status device /dev/wmistat has been renamed to
641 The option VFS_ALLOW_NONMPSAFE option has been added in order to
642 explicitely support non-MPSAFE filesystems.
643 It is on by default for all supported platform at this present
647 The broken amd(4) driver has been replaced with esp(4) in the amd64,
648 i386 and pc98 GENERIC kernel configuration files.
651 sysinstall has been removed
654 The stable/9 branch created in subversion. This corresponds to the
655 RELENG_9 branch in CVS.
658 This commit modifies vfs_register() so that it uses a hash
659 calculation to set vfc_typenum, which is enabled by default.
660 The first time a system is booted after this change, the
661 vfc_typenum values will change for all file systems. The
662 main effect of this is a change to the NFS server file handles
663 for file systems that use vfc_typenum in their fsid, such as ZFS.
664 It will, however, prevent vfc_typenum from changing when file
665 systems are loaded in a different order for subsequent reboots.
666 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
667 until you are ready to remount all NFS clients after a reboot.
670 Bump the shared library version numbers for libraries that
671 do not use symbol versioning, have changed the ABI compared
672 to stable/8 and which shared library version was not bumped.
673 Done as part of 9.0-RELEASE cycle.
676 During the merge of Capsicum features, the fget(9) KPI was modified.
677 This may require the rebuilding of out-of-tree device drivers --
678 issues have been reported specifically with the nVidia device driver.
679 __FreeBSD_version is bumped to 900041.
681 Also, there is a period between 20110811 and 20110814 where the
682 special devices /dev/{stdin,stdout,stderr} did not work correctly.
683 Building world from a kernel during that window may not work.
686 The packet filter (pf) code has been updated to OpenBSD 4.5.
687 You need to update userland tools to be in sync with kernel.
688 This update breaks backward compatibility with earlier pfsync(4)
689 versions. Care must be taken when updating redundant firewall setups.
692 The following sysctls and tunables are retired on x86 platforms:
694 machdep.hlt_logical_cpus
695 The following sysctl is retired:
696 machdep.hyperthreading_allowed
697 The sysctls were supposed to provide a way to dynamically offline and
698 online selected CPUs on x86 platforms, but the implementation has not
699 been reliable especially with SCHED_ULE scheduler.
700 machdep.hyperthreading_allowed tunable is still available to ignore
701 hyperthreading CPUs at OS level.
702 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
703 where X is an APIC ID of a CPU. Be advised, though, that disabling
704 CPUs in non-uniform fashion will result in non-uniform topology and
705 may lead to sub-optimal system performance with SCHED_ULE, which is
709 cpumask_t type is retired and cpuset_t is used in order to describe
713 Changes to ifconfig(8) for dynamic address family detection mandate
714 that you are running a kernel of 20110525 or later. Make sure to
715 follow the update procedure to boot a new kernel before installing
719 Support for sun4v architecture is officially dropped
722 Several KPI breaking changes have been committed to the mii(4) layer,
723 the PHY drivers and consequently some Ethernet drivers using mii(4).
724 This means that miibus.ko and the modules of the affected Ethernet
725 drivers need to be recompiled.
727 Note to kernel developers: Given that the OUI bit reversion problem
728 was fixed as part of these changes all mii(4) commits related to OUIs,
729 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
730 handling, no longer can be merged verbatim to stable/8 and previous
734 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
735 into their kernel configurations along with 'device pci'.
738 The default NFS client is now the new NFS client, so fstype "newnfs"
739 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
740 Although mounts via fstype "nfs" will usually work without userland
741 changes, it is recommended that the mount(8) and mount_nfs(8)
742 commands be rebuilt from sources and that a link to mount_nfs called
743 mount_oldnfs be created. The new client is compiled into the
744 kernel with "options NFSCL" and this is needed for diskless root
745 file systems. The GENERIC kernel configs have been changed to use
746 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
747 To use the regular/old client, you can "mount -t oldnfs ...". For
748 a diskless root file system, you must also include a line like:
750 vfs.root.mountfrom="oldnfs:"
752 in the boot/loader.conf on the root fs on the NFS server to make
753 a diskless root fs use the old client.
756 The GENERIC kernels for all architectures now default to the new
757 CAM-based ATA stack. It means that all legacy ATA drivers were
758 removed and replaced by respective CAM drivers. If you are using
759 ATA device names in /etc/fstab or other places, make sure to update
760 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
761 where 'Y's are the sequential numbers starting from zero for each type
762 in order of detection, unless configured otherwise with tunables,
763 see cam(4)). There will be symbolic links created in /dev/ to map
764 old adX devices to the respective adaY. They should provide basic
765 compatibility for file systems mounting in most cases, but they do
766 not support old user-level APIs and do not have respective providers
767 in GEOM. Consider using updated management tools with new device names.
769 It is possible to load devices ahci, ata, siis and mvs as modules,
770 but option ATA_CAM should remain in kernel configuration to make ata
771 module work as CAM driver supporting legacy ATA controllers. Device ata
772 still can be used in modular fashion (atacore + ...). Modules atadisk
773 and atapi* are not used and won't affect operation in ATA_CAM mode.
774 Note that to use CAM-based ATA kernel should include CAM devices
775 scbus, pass, da (or explicitly ada), cd and optionally others. All of
776 them are parts of the cam module.
778 ataraid(4) functionality is now supported by the RAID GEOM class.
779 To use it you can load geom_raid kernel module and use graid(8) tool
780 for management. Instead of /dev/arX device names, use /dev/raid/rX.
782 No kernel config options or code have been removed, so if a problem
783 arises, please report it and optionally revert to the old ATA stack.
784 In order to do it you can remove from the kernel config:
789 , and instead add back:
790 device atadisk # ATA disk drives
791 device ataraid # ATA RAID drives
792 device atapicd # ATAPI CDROM drives
793 device atapifd # ATAPI floppy drives
794 device atapist # ATAPI tape drives
797 The default NFS server has been changed to the new server, which
798 was referred to as the experimental server. If you need to switch
799 back to the old NFS server, you must now put the "-o" option on
800 both the mountd and nfsd commands. This can be done using the
801 mountd_flags and nfs_server_flags rc.conf variables until an
802 update to the rc scripts is committed, which is coming soon.
805 The GNU Objective-C runtime library (libobjc), and other Objective-C
806 related components have been removed from the base system. If you
807 require an Objective-C library, please use one of the available ports.
810 ath(4) has been split into bus- and device- modules. if_ath contains
811 the HAL, the TX rate control and the network device code. if_ath_pci
812 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
813 contains the AHB glue. Users need to load both if_ath_pci and if_ath
814 in order to use ath on everything else.
816 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
817 need to load if_ath and if_ath_pci for ath(4) operation.
820 As part of the replacement of sysinstall, the process of building
821 release media has changed significantly. For details, please re-read
822 release(7), which has been updated to reflect the new build process.
825 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
826 is the last available version under GPLv2. It brings a number of new
827 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
828 4.1 and SSE 4.2), better support for powerpc64, a number of new
829 directives, and lots of other small improvements. See the ChangeLog
830 file in contrib/binutils for the full details.
833 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
834 compliant, and will now use half of hash for authentication.
835 This will break interoperability with all stacks (including all
836 actual FreeBSD versions) who implement
837 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
839 The only workaround with such peers is to use another HMAC
840 algorithm for IPsec ("phase 2") authentication.
843 Remove the uio_yield prototype and symbol. This function has
844 been misnamed since it was introduced and should not be
845 globally exposed with this name. The equivalent functionality
846 is now available using kern_yield(curthread->td_user_pri).
847 The function remains undocumented.
850 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
851 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
852 for scalar sysctls is defined but disabled. Code that needs
853 UQUAD to pass the type checking that must compile on older
854 systems where the define is not present can check against
855 __FreeBSD_version >= 900030.
857 The system dialog(1) has been replaced with a new version previously
858 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
859 with the previous version, but the libdialog associated with it has
860 a largely incompatible API. As such, the original version of libdialog
861 will be kept temporarily as libodialog, until its base system consumers
862 are replaced or updated. Bump __FreeBSD_version to 900030.
865 If you are trying to run make universe on a -stable system, and you get
866 the following warning:
867 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
868 unknown. config(8) likely too old."
869 or something similar to it, then you must upgrade your -stable system
870 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
871 stable/8) or build the config from the latest stable/8 branch and
872 install it on your system.
874 Prior to this date, building a current universe on 8-stable system from
875 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
876 error in the first kernel build phase. A new config on those old
877 systems will fix that problem for older versions of -current.
880 The TCP stack has been modified to allow Khelp modules to interact with
881 it via helper hook points and store per-connection data in the TCP
882 control block. Bump __FreeBSD_version to 900029. User space tools that
883 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
887 Generic IEEE 802.3 annex 31B full duplex flow control support has been
888 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
889 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
890 to take advantage of it instead of using custom implementations. This
891 means that these drivers now no longer unconditionally advertise
892 support for flow control but only do so if flow control is a selected
893 media option. This was implemented in the generic support that way in
894 order to allow flow control to be switched on and off via ifconfig(8)
895 with the PHY specific default to typically off in order to protect
896 from unwanted effects. Consequently, if you used flow control with
897 one of the above mentioned drivers you now need to explicitly enable
899 ifconfig bge0 media auto mediaopt flowcontrol
901 Along with the above mentioned changes generic support for setting
902 1000baseT master mode also has been added and brgphy(4), ciphy(4),
903 e1000phy(4) as well as ip1000phy(4) have been converted to take
904 advantage of it. This means that these drivers now no longer take the
905 link0 parameter for selecting master mode but the master media option
906 has to be used instead, for example like in the following:
907 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
909 Selection of master mode now is also available with all other PHY
910 drivers supporting 1000baseT.
913 The TCP stack has received a significant update to add support for
914 modularised congestion control and generally improve the clarity of
915 congestion control decisions. Bump __FreeBSD_version to 900025. User
916 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
917 sockstat) need to be recompiled.
920 The man(1) utility has been replaced by a new version that no longer
921 uses /etc/manpath.config. Please consult man.conf(5) for how to
922 migrate local entries to the new format.
925 The copyright strings printed by login(1) and sshd(8) at the time of a
926 new connection have been removed to follow other operating systems and
930 A workaround for a fixed ld bug has been removed in kernel code,
931 so make sure that your system ld is built from sources after
932 revision 210245 from 2010-07-19 (r211583 if building head kernel
933 on stable/8, r211584 for stable/7; both from 2010-08-21).
934 A symptom of incorrect ld version is different addresses for
935 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
938 The $ipv6_prefer variable in rc.conf(5) has been split into
939 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
941 The $ip6addrctl_policy is a variable to choose a pre-defined
942 address selection policy set by ip6addrctl(8). A value
943 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
946 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
947 flag (see an entry of 20090926) is set on an interface with no
948 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
949 security reason. If you want IPv6 link-local address on all
950 interfaces by default, set this to "YES".
952 The old ipv6_prefer="YES" is equivalent to
953 ipv6_activate_all_interfaces="YES" and
954 ip6addrctl_policy="ipv6_prefer".
957 DTrace has grown support for userland tracing. Due to this, DTrace is
958 now i386 and amd64 only.
959 dtruss(1) is now installed by default on those systems and a new
960 kernel module is needed for userland tracing: fasttrap.
961 No changes to your kernel config file are necessary to enable
962 userland tracing, but you might consider adding 'STRIP=' and
963 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
964 to have informative userland stack traces in DTrace (ustack).
967 The acpi_aiboost(4) driver has been removed in favor of the new
968 aibs(4) driver. You should update your kernel configuration file.
971 BSD grep has been imported to the base system and it is built by
972 default. It is completely BSD licensed, highly GNU-compatible, uses
973 less memory than its GNU counterpart and has a small codebase.
974 However, it is slower than its GNU counterpart, which is mostly
975 noticeable for larger searches, for smaller ones it is measurable
976 but not significant. The reason is complex, the most important factor
977 is that we lack a modern and efficient regex library and GNU
978 overcomes this by optimizing the searches internally. Future work
979 on improving the regex performance is planned, for the meantime,
980 users that need better performance, can build GNU grep instead by
981 setting the WITH_GNU_GREP knob.
984 Due to the import of powerpc64 support, all existing powerpc kernel
985 configuration files must be updated with a machine directive like this:
986 machine powerpc powerpc
988 In addition, an updated config(8) is required to build powerpc kernels
992 A new version of ZFS (version 15) has been merged to -HEAD.
993 This version uses a python library for the following subcommands:
994 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
995 For full functionality of these commands the following port must
996 be installed: sysutils/py-zfs
999 'vm_page's are now hashed by physical address to an array of mutexes.
1000 Currently this is only used to serialize access to hold_count. Over
1001 time the page queue mutex will be peeled away. This changes the size
1002 of pmap on every architecture. And requires all callers of vm_page_hold
1003 and vm_page_unhold to be updated.
1006 WITH_CTF can now be specified in src.conf (not recommended, there
1007 are some problems with static executables), make.conf (would also
1008 affect ports which do not use GNU make and do not override the
1009 compile targets) or in the kernel config (via "makeoptions
1011 When WITH_CTF was specified there before this was silently ignored,
1012 so make sure that WITH_CTF is not used in places which could lead
1013 to unwanted behavior.
1016 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1017 to allow 32-bit compatibility on non-x86 platforms. All kernel
1018 configurations on amd64 and ia64 platforms using these options must
1019 be modified accordingly.
1022 The utmp user accounting database has been replaced with utmpx,
1023 the user accounting interface standardized by POSIX.
1024 Unfortunately the semantics of utmp and utmpx don't match,
1025 making it practically impossible to support both interfaces.
1026 The user accounting database is used by tools like finger(1),
1027 last(1), talk(1), w(1) and ac(8).
1029 All applications in the base system use utmpx. This means only
1030 local binaries (e.g. from the ports tree) may still use these
1031 utmp database files. These applications must be rebuilt to make
1034 After the system has been upgraded, it is safe to remove the old
1035 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1036 assuming their contents is of no importance anymore. Old wtmp
1037 databases can only be used by last(1) and ac(8) after they have
1038 been converted to the new format using wtmpcvt(1).
1041 Introduce the kernel thread "deadlock resolver" (which can be enabled
1042 via the DEADLKRES option, see NOTES for more details) and the
1043 sleepq_type() function for sleepqueues.
1046 The rc.firewall and rc.firewall6 were unified, and
1047 rc.firewall6 and rc.d/ip6fw were removed.
1048 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1049 variables are obsoleted. Instead, the following new rc
1050 variables are added to rc.d/ipfw:
1052 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1053 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1054 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1056 The meanings correspond to the relevant IPv4 variables.
1062 The default terminal emulation for syscons(4) has been changed
1063 from cons25 to xterm on all platforms except pc98. This means
1064 that the /etc/ttys file needs to be updated to ensure correct
1065 operation of applications on the console.
1067 The terminal emulation style can be toggled per window by using
1068 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1069 options can be used to change the compile-time default back to
1072 To prevent graphical artifacts, make sure the TERM environment
1073 variable is set to match the terminal emulation that is being
1074 performed by syscons(4).
1077 The layout of the structure ieee80211req_scan_result has changed.
1078 Applications that require wireless scan results (e.g. ifconfig(8))
1079 from net80211 need to be recompiled.
1081 Applications such as wpa_supplicant(8) may require a full world
1082 build without using NO_CLEAN in order to get synchronized with the
1086 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1087 There's one kernel module for each firmware. Adding "device iwnfw"
1088 to the kernel configuration file means including all three firmware
1089 images inside the kernel. If you want to include just the one for
1090 your wireless card, use the devices iwn4965fw, iwn5000fw or
1094 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1095 into rc.d/netif. The changes are the following:
1097 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1098 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1099 Note that both variables need the "inet6" keyword at the head.
1101 Do not set $ipv6_network_interfaces manually if you do not
1102 understand what you are doing. It is not needed in most cases.
1104 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1107 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1108 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1110 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1111 all configured interfaces have "inet6 accept_rtadv" in the
1112 $ifconfig_IF_ipv6. These are for backward compatibility.
1114 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1115 functionality of interfaces with no corresponding
1116 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1117 and the default address selection policy of ip6addrctl(8)
1118 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1119 Note that if you want to configure IPv6 functionality on the
1120 disabled interfaces after boot, first you need to clear the flag by
1121 using ifconfig(8) like:
1123 ifconfig em0 inet6 -ifdisabled
1125 If YES, the default address selection policy is set as
1128 The default value of $ipv6_prefer is NO.
1130 4. If your system need to receive Router Advertisement messages,
1131 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1132 scripts automatically invoke rtsol(8) when the interface becomes
1133 UP. The Router Advertisement messages are used for SLAAC
1134 (State-Less Address AutoConfiguration).
1137 802.11s D3.03 support was committed. This is incompatible with the
1138 previous code, which was based on D3.0.
1141 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1142 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1143 control whether accepting Router Advertisement messages or not.
1144 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1145 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1146 The ifconfig(8) utility now supports these flags.
1149 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1150 mount(8) and -a option for df(1) to see them.
1153 The old tunable hw.bus.devctl_disable has been superseded by
1154 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1155 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1159 Remove the option STOP_NMI. The default action is now to use NMI only
1160 for KDB via the newly introduced function stop_cpus_hard() and
1161 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1164 The stable/8 branch created in subversion. This corresponds to the
1165 RELENG_8 branch in CVS.
1168 Bump the shared library version numbers for all libraries that do not
1169 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1170 __FreeBSD_version to 800105.
1173 Due to changes in the implementation of virtual network stack support,
1174 all network-related kernel modules must be recompiled. As this change
1175 breaks the ABI, bump __FreeBSD_version to 800104.
1178 The TOE interface to the TCP syncache has been modified to remove
1179 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1180 The cxgb driver is the only TOE consumer affected by this change, and
1181 needs to be recompiled along with the kernel. As this change breaks
1182 the ABI, bump __FreeBSD_version to 800103.
1185 Padding has been added to struct tcpcb, sackhint and tcpstat in
1186 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1187 maintaining the ABI. However, this change breaks the ABI, so bump
1188 __FreeBSD_version to 800102. User space tools that rely on the size of
1189 any of these structs (e.g. sockstat) need to be recompiled.
1192 The NFS_LEGACYRPC option has been removed along with the old kernel
1193 RPC implementation that this option selected. Kernel configurations
1194 may need to be adjusted.
1197 The network interface device nodes at /dev/net/<interface> have been
1198 removed. All ioctl operations can be performed the normal way using
1199 routing sockets. The kqueue functionality can generally be replaced
1200 with routing sockets.
1203 The documentation from the FreeBSD Documentation Project (Handbook,
1204 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1205 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1208 The ABI of various structures related to the SYSV IPC API have been
1209 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1210 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1214 Layout of struct vnet has changed as routing related variables were
1215 moved to their own Vimage module. Modules need to be recompiled. Bump
1216 __FreeBSD_version to 800099.
1219 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1220 respectively. As long as no more than 16 groups per process are used,
1221 no changes should be visible. When more than 16 groups are used, old
1222 binaries may fail if they call getgroups() or getgrouplist() with
1223 statically sized storage. Recompiling will work around this, but
1224 applications should be modified to use dynamically allocated storage
1225 for group arrays as POSIX.1-2008 does not cap an implementation's
1226 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1228 NFS and portalfs mounts may also be affected as the list of groups is
1229 truncated to 16. Users of NFS who use more than 16 groups, should
1230 take care that negative group permissions are not used on the exported
1231 file systems as they will not be reliable unless a GSSAPI based
1232 authentication method is used.
1235 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1236 option compiles in the support for adaptive spinning for lockmgrs
1237 which want to enable it. The lockinit() function now accepts the flag
1238 LK_ADAPTIVE in order to make the lock object subject to adaptive
1239 spinning when both held in write and read mode.
1242 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1243 changed. User applications that use this ioctl need to be rebuilt.
1246 The layout of struct thread has changed. Kernel and modules need to
1250 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1251 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1254 window(1) has been removed from the base system. It can now be
1255 installed from ports. The port is called misc/window.
1258 The way we are storing and accessing `routing table' entries has
1259 changed. Programs reading the FIB, like netstat, need to be
1263 A new netisr implementation has been added for FreeBSD 8. Network
1264 file system modules, such as igmp, ipdivert, and others, should be
1266 Bump __FreeBSD_version to 800096.
1269 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1273 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1274 Bump __FreeBSD_version to 800094.
1277 Add mnt_xflag field to 'struct mount'. File system modules need to be
1279 Bump __FreeBSD_version to 800093.
1282 The compiling option ADAPTIVE_SX has been retired while it has been
1283 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1284 The KPI for sx_init_flags() changes as accepting flags:
1285 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1286 been introduced in order to handle the reversed logic.
1287 Bump __FreeBSD_version to 800092.
1290 Add support for hierarchical jails. Remove global securelevel.
1291 Bump __FreeBSD_version to 800091.
1294 The layout of struct vnet_net has changed, therefore modules
1296 Bump __FreeBSD_version to 800090.
1299 The newly imported zic(8) produces a new format in the output. Please
1300 run tzsetup(8) to install the newly created data to /etc/localtime.
1303 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1304 hw.usb.* and is now consistent again with previous releases.
1307 802.11 monitor mode support was revised and driver api's were changed.
1308 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1309 of DLT_IEEE802_11. No user-visible data structures were changed but
1310 applications that use DLT_IEEE802_11 may require changes.
1311 Bump __FreeBSD_version to 800088.
1314 The layout of the following structs has changed: sysctl_oid,
1315 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1316 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1317 panics may be experienced. World rebuild is required for
1318 correctly checking networking state from userland.
1319 Bump __FreeBSD_version to 800085.
1322 MLDv2 and Source-Specific Multicast (SSM) have been merged
1323 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1324 The implementation of SSM within FreeBSD's IPv6 stack closely
1325 follows the IPv4 implementation.
1327 For kernel developers:
1329 * The most important changes are that the ip6_output() and
1330 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1331 and this lock has been downgraded to a non-recursive mutex.
1333 * As with the changes to the IPv4 stack to support SSM, filtering
1334 of inbound multicast traffic must now be performed by transport
1335 protocols within the IPv6 stack. This does not apply to TCP and
1336 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1338 * The KPIs used by IPv6 multicast are similar to those used by
1339 the IPv4 stack, with the following differences:
1340 * im6o_mc_filter() is analogous to imo_multicast_filter().
1341 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1342 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1343 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1344 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1345 for MLDv1 have an additional 'timer' argument which is used to
1346 jitter the initial membership report for the solicited-node
1347 multicast membership on-link.
1348 * This is not strictly needed for MLDv2, which already jitters
1349 its report transmissions. However, the 'timer' argument is
1350 preserved in case MLDv1 is active on the interface.
1352 * The KAME linked-list based IPv6 membership implementation has
1353 been refactored to use a vector similar to that used by the IPv4
1355 Code which maintains a list of its own multicast memberships
1356 internally, e.g. carp, has been updated to reflect the new
1359 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1360 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1361 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1362 implementation constraint which needs to be addressed in HEAD.
1364 For application developers:
1366 * The changes are broadly similar to those made for the IPv4
1369 * The use of IPv4 and IPv6 multicast socket options on the same
1370 socket, using mapped addresses, HAS NOT been tested or supported.
1372 * There are a number of issues with the implementation of various
1373 IPv6 multicast APIs which need to be resolved in the API surface
1374 before the implementation is fully compatible with KAME userland
1375 use, and these are mostly to do with interface index treatment.
1377 * The literature available discusses the use of either the delta / ASM
1378 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1379 using setsourcefilter(3)/getsourcefilter(3). For more information
1380 please refer to RFC 3768, 'Socket Interface Extensions for
1381 Multicast Source Filters'.
1383 * Applications which use the published RFC 3678 APIs should be fine.
1385 For systems administrators:
1387 * The mtest(8) utility has been refactored to support IPv6, in
1388 addition to IPv4. Interface addresses are no longer accepted
1389 as arguments, their names must be used instead. The utility
1390 will map the interface name to its first IPv4 address as
1391 returned by getifaddrs(3).
1393 * The ifmcstat(8) utility has also been updated to print the MLDv2
1394 endpoint state and source filter lists via sysctl(3).
1396 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1397 loopback of IPv6 multicast datagrams by default; it defaults to 1
1398 to preserve the existing behaviour. Disabling multicast loopback is
1399 recommended for optimal system performance.
1401 * The IPv6 MROUTING code has been changed to examine this sysctl
1402 instead of attempting to perform a group lookup before looping
1403 back forwarded datagrams.
1405 Bump __FreeBSD_version to 800084.
1408 Implement low-level Bluetooth HCI API.
1409 Bump __FreeBSD_version to 800083.
1412 The layout of struct malloc_type, used by modules to register new
1413 memory allocation types, has changed. Most modules will need to
1414 be rebuilt or panics may be experienced.
1415 Bump __FreeBSD_version to 800081.
1418 Anticipate overflowing inp_flags - add inp_flags2.
1419 This changes most offsets in inpcb, so checking v4 connection
1420 state will require a world rebuild.
1421 Bump __FreeBSD_version to 800080.
1424 Add an llentry to struct route and struct route_in6. Modules
1425 embedding a struct route will need to be recompiled.
1426 Bump __FreeBSD_version to 800079.
1429 The size of rt_metrics_lite and by extension rtentry has changed.
1430 Networking administration apps will need to be recompiled.
1431 The route command now supports show as an alias for get, weighting
1432 of routes, sticky and nostick flags to alter the behavior of stateful
1434 Bump __FreeBSD_version to 800078.
1437 Do not use Giant for kbdmux(4) locking. This is wrong and
1438 apparently causing more problems than it solves. This will
1439 re-open the issue where interrupt handlers may race with
1440 kbdmux(4) in polling mode. Typical symptoms include (but
1441 not limited to) duplicated and/or missing characters when
1442 low level console functions (such as gets) are used while
1443 interrupts are enabled (for example geli password prompt,
1444 mountroot prompt etc.). Disabling kbdmux(4) may help.
1447 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1448 kernel modules referencing any of the above need to be recompiled.
1449 Bump __FreeBSD_version to 800075.
1452 GEOM_PART has become the default partition slicer for storage devices,
1453 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1454 introduces some changes:
1456 MSDOS/EBR: the devices created from MSDOS extended partition entries
1457 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1458 to devices with offset-based names. fstabs may need to be modified.
1460 BSD: the "geometry does not match label" warning is harmless in most
1461 cases but it points to problems in file system misalignment with
1462 disk geometry. The "c" partition is now implicit, covers the whole
1463 top-level drive and cannot be (mis)used by users.
1465 General: Kernel dumps are now not allowed to be written to devices
1466 whose partition types indicate they are meant to be used for file
1467 systems (or, in case of MSDOS partitions, as something else than
1470 Most of these changes date approximately from 200812.
1473 The uscanner(4) driver has been removed from the kernel. This follows
1474 Linux removing theirs in 2.6 and making libusb the default interface
1475 (supported by sane).
1478 The multicast forwarding code has been cleaned up. netstat(1)
1479 only relies on KVM now for printing bandwidth upcall meters.
1480 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1481 ip6_mroute_mod respectively. The config(5) options for statically
1482 compiling this code remain the same, i.e. 'options MROUTING'.
1485 Support for the IFF_NEEDSGIANT network interface flag has been
1486 removed, which means that non-MPSAFE network device drivers are no
1487 longer supported. In particular, if_ar, if_sr, and network device
1488 drivers from the old (legacy) USB stack can no longer be built or
1492 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1493 a bunch of new language catalog files have also been added.
1494 This means that some common libc messages are now localized and
1495 they depend on the LC_MESSAGES environmental variable.
1498 The k8temp(4) driver has been renamed to amdtemp(4) since
1499 support for Family 10 and Family 11 CPU families was added.
1502 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1503 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1505 For kernel developers, the most important changes are that the
1506 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1507 and this lock has been downgraded to a non-recursive mutex.
1509 Transport protocols (UDP, Raw IP) are now responsible for filtering
1510 inbound multicast traffic according to group membership and source
1511 filters. The imo_multicast_filter() KPI exists for this purpose.
1512 Transports which do not use multicast (SCTP, TCP) already reject
1513 multicast by default. Forwarding and receive performance may improve
1514 as a mutex acquisition is no longer needed in the ip_input()
1515 low-level input path. in_addmulti() and in_delmulti() are shimmed
1516 to new KPIs which exist to support SSM in-kernel.
1518 For application developers, it is recommended that loopback of
1519 multicast datagrams be disabled for best performance, as this
1520 will still cause the lock to be taken for each looped-back
1521 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1522 be tuned to 0 to disable loopback by default; it defaults to 1
1523 to preserve the existing behaviour.
1525 For systems administrators, to obtain best performance with
1526 multicast reception and multiple groups, it is always recommended
1527 that a card with a suitably precise hash filter is used. Hash
1528 collisions will still result in the lock being taken within the
1529 transport protocol input path to check group membership.
1531 If deploying FreeBSD in an environment with IGMP snooping switches,
1532 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1533 enabled; this forces 224.0.0.0/24 group membership to be announced
1536 The size of 'struct igmpstat' has changed; netstat needs to be
1537 recompiled to reflect this.
1538 Bump __FreeBSD_version to 800070.
1541 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1542 updated to use it. This requires a buildworld/installworld in order to
1543 update the library and dependencies (usbconfig, etc). Its advisable to
1544 rebuild all ports which uses libusb. More specific directions are given
1545 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1546 libusb are no longer required and can be removed.
1549 A workaround is committed to allow the creation of System V shared
1550 memory segment of size > 2 GB on the 64-bit architectures.
1551 Due to a limitation of the existing ABI, the shm_segsz member
1552 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1553 wrong for large segments. Note that limits must be explicitly
1554 raised to allow such segments to be created.
1557 The layout of struct ifnet has changed, requiring a rebuild of all
1558 network device driver modules.
1561 The /dev handling for the new USB stack has changed, a
1562 buildworld/installworld is required for libusb20.
1565 The new USB2 stack has now been permanently moved in and all kernel and
1566 module names reverted to their previous values (eg, usb, ehci, ohci,
1567 ums, ...). The old usb stack can be compiled in by prefixing the name
1568 with the letter 'o', the old usb modules have been removed.
1569 Updating entry 20090216 for xorg and 20090215 for libmap may still
1573 The rc.conf(5) option if_up_delay has been renamed to
1574 defaultroute_delay to better reflect its purpose. If you have
1575 customized this setting in /etc/rc.conf you need to update it to
1579 xorg 7.4 wants to configure its input devices via hald which does not
1580 yet work with USB2. If the keyboard/mouse does not work in xorg then
1582 Option "AllowEmptyInput" "off"
1583 to your ServerLayout section. This will cause X to use the configured
1584 kbd and mouse sections from your xorg.conf.
1587 The GENERIC kernels for all architectures now default to the new USB2
1588 stack. No kernel config options or code have been removed so if a
1589 problem arises please report it and optionally revert to the old USB
1590 stack. If you are loading USB kernel modules or have a custom kernel
1591 that includes GENERIC then ensure that usb names are also changed over,
1592 eg uftdi -> usb2_serial_ftdi.
1594 Older programs linked against the ports libusb 0.1 need to be
1595 redirected to the new stack's libusb20. /etc/libmap.conf can
1597 # Map old usb library to new one for usb2 stack
1598 libusb-0.1.so.8 libusb20.so.1
1601 All USB ethernet devices now attach as interfaces under the name ueN
1602 (eg. ue0). This is to provide a predictable name as vendors often
1603 change usb chipsets in a product without notice.
1606 The ichsmb(4) driver has been changed to require SMBus slave
1607 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1608 All of the other SMBus controller drivers require left-justified
1609 slave addresses, so this change makes all the drivers provide the
1613 INET6 statistics (struct ip6stat) was updated.
1614 netstat(1) needs to be recompiled.
1617 NTFS has been removed from GENERIC kernel on amd64 to match
1618 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1619 will load ntfs.ko module automatically when NTFS support is
1620 actually needed, unless ntfs.ko is not installed or security
1621 level prohibits loading kernel modules. If either is the case,
1622 "options NTFS" has to be added into kernel config.
1625 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1626 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1627 800061. User space tools that rely on the size of struct tcpcb in
1628 tcp_var.h (e.g. sockstat) need to be recompiled.
1631 ng_tty(4) module updated to match the new TTY subsystem.
1632 Due to API change, user-level applications must be updated.
1633 New API support added to mpd5 CVS and expected to be present
1634 in next mpd5.3 release.
1637 With __FreeBSD_version 800060 the makefs tool is part of
1638 the base system (it was a port).
1641 The afdata and ifnet locks have been changed from mutexes to
1642 rwlocks, network modules will need to be re-compiled.
1645 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1646 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1647 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1648 architecture and 40 bytes on 64-bit architecture. The userland
1649 applications "arp" and "ndp" have been updated accordingly.
1650 The output from "netstat -r" shows only routing entries and
1651 none of the L2 information.
1654 __FreeBSD_version 800057 marks the switchover from the
1655 binary ath hal to source code. Users must add the line:
1657 options AH_SUPPORT_AR5416
1659 to their kernel config files when specifying:
1663 The ath_hal module no longer exists; the code is now compiled
1664 together with the driver in the ath module. It is now
1665 possible to tailor chip support (i.e. reduce the set of chips
1666 and thereby the code size); consult ath_hal(4) for details.
1669 __FreeBSD_version 800054 adds memory barriers to
1670 <machine/atomic.h>, new interfaces to ifnet to facilitate
1671 multiple hardware transmit queues for cards that support
1672 them, and a lock-less ring-buffer implementation to
1673 enable drivers to more efficiently manage queueing of
1677 A new version of ZFS (version 13) has been merged to -HEAD.
1678 This version has zpool attribute "listsnapshots" off by
1679 default, which means "zfs list" does not show snapshots,
1680 and is the same as Solaris behavior.
1683 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1686 The uhci, ohci, ehci and slhci USB Host controller drivers have
1687 been put into separate modules. If you load the usb module
1688 separately through loader.conf you will need to load the
1689 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1690 controller add the following to loader.conf:
1696 The ABI used by the PMC toolset has changed. Please keep
1697 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1701 atapci kernel module now includes only generic PCI ATA
1702 driver. AHCI driver moved to ataahci kernel module.
1703 All vendor-specific code moved into separate kernel modules:
1704 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1705 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1706 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1707 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1710 The TTY subsystem of the kernel has been replaced by a new
1711 implementation, which provides better scalability and an
1712 improved driver model. Most common drivers have been migrated to
1713 the new TTY subsystem, while others have not. The following
1714 drivers have not yet been ported to the new TTY layer:
1717 cy, digi, rc, rp, sio
1723 ng_h4, ng_tty, ppp, sl, snp
1725 Adding these drivers to your kernel configuration file shall
1726 cause compilation to fail.
1729 ntpd has been upgraded to 4.2.4p5.
1732 OpenSSH has been upgraded to 5.1p1.
1734 For many years, FreeBSD's version of OpenSSH preferred DSA
1735 over RSA for host and user authentication keys. With this
1736 upgrade, we've switched to the vendor's default of RSA over
1737 DSA. This may cause upgraded clients to warn about unknown
1738 host keys even for previously known hosts. Users should
1739 follow the usual procedure for verifying host keys before
1740 accepting the RSA key.
1742 This can be circumvented by setting the "HostKeyAlgorithms"
1743 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1746 Please note that the sequence of keys offered for
1747 authentication has been changed as well. You may want to
1748 specify IdentityFile in a different order to revert this
1752 The sio(4) driver has been removed from the i386 and amd64
1753 kernel configuration files. This means uart(4) is now the
1754 default serial port driver on those platforms as well.
1756 To prevent collisions with the sio(4) driver, the uart(4) driver
1757 uses different names for its device nodes. This means the
1758 onboard serial port will now most likely be called "ttyu0"
1759 instead of "ttyd0". You may need to reconfigure applications to
1760 use the new device names.
1762 When using the serial port as a boot console, be sure to update
1763 /boot/device.hints and /etc/ttys before booting the new kernel.
1764 If you forget to do so, you can still manually specify the hints
1765 at the loader prompt:
1767 set hint.uart.0.at="isa"
1768 set hint.uart.0.port="0x3F8"
1769 set hint.uart.0.flags="0x10"
1770 set hint.uart.0.irq="4"
1774 The gpt(8) utility has been removed. Use gpart(8) to partition
1778 The version that Linuxulator emulates was changed from 2.4.2
1779 to 2.6.16. If you experience any problems with Linux binaries
1780 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1781 if it fixes the problem contact emulation mailing list.
1784 ISDN4BSD (I4B) was removed from the src tree. You may need to
1785 update a your kernel configuration and remove relevant entries.
1788 I have checked in code to support multiple routing tables.
1789 See the man pages setfib(1) and setfib(2).
1790 This is a hopefully backwards compatible version,
1791 but to make use of it you need to compile your kernel
1792 with options ROUTETABLES=2 (or more up to 16).
1795 The 802.11 wireless support was redone to enable multi-bss
1796 operation on devices that are capable. The underlying device
1797 is no longer used directly but instead wlanX devices are
1798 cloned with ifconfig. This requires changes to rc.conf files.
1799 For example, change:
1800 ifconfig_ath0="WPA DHCP"
1803 ifconfig_wlan0="WPA DHCP"
1804 see rc.conf(5) for more details. In addition, mergemaster of
1805 /etc/rc.d is highly recommended. Simultaneous update of userland
1806 and kernel wouldn't hurt either.
1808 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1809 modules were merged into the base wlan module. All references
1810 to these modules (e.g. in kernel config files) must be removed.
1813 psm(4) has gained write(2) support in native operation level.
1814 Arbitrary commands can be written to /dev/psm%d and status can
1815 be read back from it. Therefore, an application is responsible
1816 for status validation and error recovery. It is a no-op in
1817 other operation levels.
1820 Support for KSE threading has been removed from the kernel. To
1821 run legacy applications linked against KSE libmap.conf may
1822 be used. The following libmap.conf may be used to ensure
1823 compatibility with any prior release:
1825 libpthread.so.1 libthr.so.1
1826 libpthread.so.2 libthr.so.2
1827 libkse.so.3 libthr.so.3
1830 The layout of struct vmspace has changed. This affects libkvm
1831 and any executables that link against libkvm and use the
1832 kvm_getprocs() function. In particular, but not exclusively,
1833 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1834 The effects are minimal, but it's advisable to upgrade world
1838 The latest em driver no longer has support in it for the
1839 82575 adapter, this is now moved to the igb driver. The
1840 split was done to make new features that are incompatible
1841 with older hardware easier to do.
1844 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1845 likewise the kernel option is now GEOM_LINUX_LVM.
1848 The default NFS mount mode has changed from UDP to TCP for
1849 increased reliability. If you rely on (insecurely) NFS
1850 mounting across a firewall you may need to update your
1854 Belatedly note the addition of m_collapse for compacting
1858 The fts(3) structures have been changed to use adequate
1859 integer types for their members and so to be able to cope
1860 with huge file trees. The old fts(3) ABI is preserved
1861 through symbol versioning in libc, so third-party binaries
1862 using fts(3) should still work, although they will not take
1863 advantage of the extended types. At the same time, some
1864 third-party software might fail to build after this change
1865 due to unportable assumptions made in its source code about
1866 fts(3) structure members. Such software should be fixed
1867 by its vendor or, in the worst case, in the ports tree.
1868 FreeBSD_version 800015 marks this change for the unlikely
1869 case that a portable fix is impossible.
1872 To upgrade to -current after this date, you must be running
1873 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1874 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1877 The ADAPTIVE_GIANT kernel option has been retired because its
1878 functionality is the default now.
1881 The AT keyboard emulation of sunkbd(4) has been turned on
1882 by default. In order to make the special symbols of the Sun
1883 keyboards driven by sunkbd(4) work under X these now have
1884 to be configured the same way as Sun USB keyboards driven
1885 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1887 Option "XkbLayout" "us"
1888 Option "XkbRules" "xorg"
1889 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1892 It has been decided that it is desirable to provide ABI
1893 backwards compatibility to the FreeBSD 4/5/6 versions of the
1894 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1895 broken with the introduction of PCI domain support (see the
1896 20070930 entry). Unfortunately, this required the ABI of
1897 PCIOCGETCONF to be broken again in order to be able to
1898 provide backwards compatibility to the old version of that
1899 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1900 again. As for prominent ports this affects neither pciutils
1901 nor xorg-server this time, the hal port needs to be rebuilt
1905 The misnamed kthread_create() and friends have been renamed
1906 to kproc_create() etc. Many of the callers already
1907 used kproc_start()..
1908 I will return kthread_create() and friends in a while
1909 with implementations that actually create threads, not procs.
1910 Renaming corresponds with version 800002.
1919 Avoid using make -j when upgrading. While generally safe, there are
1920 sometimes problems using -j to upgrade. If your upgrade fails with
1921 -j, please try again without -j. From time to time in the past there
1922 have been problems using -j with buildworld and/or installworld. This
1923 is especially true when upgrading between "distant" versions (eg one
1924 that cross a major release boundary or several minor releases, or when
1925 several months have passed on the -current branch).
1927 Sometimes, obscure build problems are the result of environment
1928 poisoning. This can happen because the make utility reads its
1929 environment when searching for values for global variables. To run
1930 your build attempts in an "environmental clean room", prefix all make
1931 commands with 'env -i '. See the env(1) manual page for more details.
1933 When upgrading from one major version to another it is generally best
1934 to upgrade to the latest code in the currently installed branch first,
1935 then do an upgrade to the new branch. This is the best-tested upgrade
1936 path, and has the highest probability of being successful. Please try
1937 this approach before reporting problems with a major version upgrade.
1939 When upgrading a live system, having a root shell around before
1940 installing anything can help undo problems. Not having a root shell
1941 around can lead to problems if pam has changed too much from your
1942 starting point to allow continued authentication after the upgrade.
1946 When upgrading the boot ZFS pool to a new version, always follow
1949 1.) recompile and reinstall the ZFS boot loader and boot block
1950 (this is part of "make buildworld" and "make installworld")
1952 2.) update the ZFS boot block on your boot drive
1954 The following example updates the ZFS boot block on the first
1955 partition (freebsd-boot) of a GPT partitioned drive ad0:
1956 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1958 Non-boot pools do not need these updates.
1962 If you are updating from a prior version of FreeBSD (even one just
1963 a few days old), you should follow this procedure. It is the most
1964 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1966 make kernel-toolchain
1967 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1968 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1970 To test a kernel once
1971 ---------------------
1972 If you just want to boot a kernel once (because you are not sure
1973 if it works, or if you want to boot a known bad kernel to provide
1974 debugging information) run
1975 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1976 nextboot -k testkernel
1978 To just build a kernel when you know that it won't mess you up
1979 --------------------------------------------------------------
1980 This assumes you are already running a CURRENT system. Replace
1981 ${arch} with the architecture of your machine (e.g. "i386",
1982 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1984 cd src/sys/${arch}/conf
1985 config KERNEL_NAME_HERE
1986 cd ../compile/KERNEL_NAME_HERE
1991 If this fails, go to the "To build a kernel" section.
1993 To rebuild everything and install it on the current system.
1994 -----------------------------------------------------------
1995 # Note: sometimes if you are running current you gotta do more than
1996 # is listed here if you are upgrading from a really old current.
1998 <make sure you have good level 0 dumps>
2000 make kernel KERNCONF=YOUR_KERNEL_HERE
2002 <reboot in single user> [3]
2009 To cross-install current onto a separate partition
2010 --------------------------------------------------
2011 # In this approach we use a separate partition to hold
2012 # current's root, 'usr', and 'var' directories. A partition
2013 # holding "/", "/usr" and "/var" should be about 2GB in
2016 <make sure you have good level 0 dumps>
2019 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2020 <maybe newfs current's root partition>
2021 <mount current's root partition on directory ${CURRENT_ROOT}>
2022 make installworld DESTDIR=${CURRENT_ROOT}
2023 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2024 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2025 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2026 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2027 <reboot into current>
2028 <do a "native" rebuild/install as described in the previous section>
2029 <maybe install compatibility libraries from ports/misc/compat*>
2033 To upgrade in-place from stable to current
2034 ----------------------------------------------
2035 <make sure you have good level 0 dumps>
2037 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2039 <reboot in single user> [3]
2046 Make sure that you've read the UPDATING file to understand the
2047 tweaks to various things you need. At this point in the life
2048 cycle of current, things change often and you are on your own
2049 to cope. The defaults can also change, so please read ALL of
2050 the UPDATING entries.
2052 Also, if you are tracking -current, you must be subscribed to
2053 freebsd-current@freebsd.org. Make sure that before you update
2054 your sources that you have read and understood all the recent
2055 messages there. If in doubt, please track -stable which has
2056 much fewer pitfalls.
2058 [1] If you have third party modules, such as vmware, you
2059 should disable them at this point so they don't crash your
2062 [3] From the bootblocks, boot -s, and then do
2067 adjkerntz -i # if CMOS is wall time
2068 Also, when doing a major release upgrade, it is required that
2069 you boot into single user mode to do the installworld.
2071 [4] Note: This step is non-optional. Failure to do this step
2072 can result in a significant reduction in the functionality of the
2073 system. Attempting to do it by hand is not recommended and those
2074 that pursue this avenue should read this file carefully, as well
2075 as the archives of freebsd-current and freebsd-hackers mailing lists
2076 for potential gotchas. The -U option is also useful to consider.
2077 See mergemaster(8) for more information.
2079 [5] Usually this step is a noop. However, from time to time
2080 you may need to do this if you get unknown user in the following
2081 step. It never hurts to do it all the time. You may need to
2082 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2083 install) after the buildworld before this step if you last updated
2084 from current before 20130425 or from -stable before 20130430.
2086 [6] This only deletes old files and directories. Old libraries
2087 can be deleted by "make delete-old-libs", but you have to make
2088 sure that no program is using those libraries anymore.
2090 [8] In order to have a kernel that can run the 4.x binaries needed to
2091 do an installworld, you must include the COMPAT_FREEBSD4 option in
2092 your kernel. Failure to do so may leave you with a system that is
2093 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2094 required to run the 5.x binaries on more recent kernels. And so on
2095 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2097 Make sure that you merge any new devices from GENERIC since the
2098 last time you updated your kernel config file.
2100 [9] When checking out sources, you must include the -P flag to have
2101 cvs prune empty directories.
2103 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2104 "?=" instead of the "=" assignment operator, so that buildworld can
2105 override the CPUTYPE if it needs to.
2107 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2108 not on the command line, or in /etc/make.conf. buildworld will
2109 warn if it is improperly defined.
2112 This file contains a list, in reverse chronological order, of major
2113 breakages in tracking -current. It is not guaranteed to be a complete
2114 list of such breakages, and only contains entries since October 10, 2007.
2115 If you need to see UPDATING entries from before that date, you will need
2116 to fetch an UPDATING file from an older FreeBSD release.
2118 Copyright information:
2120 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2122 Redistribution, publication, translation and use, with or without
2123 modification, in full or in part, in any form or format of this
2124 document are permitted without further permission from the author.
2126 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2127 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2128 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2129 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2130 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2131 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2132 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2133 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2134 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2135 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2136 POSSIBILITY OF SUCH DAMAGE.
2138 Contact Warner Losh if you have any questions about your use of