1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 head, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 Clang and llvm have been upgraded to 3.4 release.
38 The nve(4) driver has been removed. Please use the nfe(4) driver
39 for NVIDIA nForce MCP Ethernet adapters instead.
42 An ABI incompatibility crept into the libc++ 3.4 import in r261283.
43 This could cause certain C++ applications using shared libraries built
44 against the previous version of libc++ to crash. The incompatibility
45 has now been fixed, but any C++ applications or shared libraries built
46 between r261283 and r261801 should be recompiled.
49 The libelf and libdwarf libraries have been updated to newer
50 versions from upstream. Shared library version numbers for
51 these two libraries were bumped. Any ports or binaries
52 requiring these two libraries should be recompiled.
53 __FreeBSD_version is bumped to 1100006.
56 If a Makefile in a tests/ directory was auto-generating a Kyuafile
57 instead of providing an explicit one, this would prevent such
58 Makefile from providing its own Kyuafile in the future during
59 NO_CLEAN builds. This has been fixed in the Makefiles but manual
60 intervention is needed to clean an objdir if you use NO_CLEAN:
61 # find /usr/obj -name Kyuafile | xargs rm -f
64 The behavior of gss_pseudo_random() for the krb5 mechanism
65 has changed, for applications requesting a longer random string
66 than produced by the underlying enctype's pseudo-random() function.
67 In particular, the random string produced from a session key of
68 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
69 be different at the 17th octet and later, after this change.
70 The counter used in the PRF+ construction is now encoded as a
71 big-endian integer in accordance with RFC 4402.
72 __FreeBSD_version is bumped to 1100004.
75 The WITHOUT_ATF build knob has been removed and its functionality
76 has been subsumed into the more generic WITHOUT_TESTS. If you were
77 using the former to disable the build of the ATF libraries, you
78 should change your settings to use the latter.
81 The default version of mtree is nmtree which is obtained from
82 NetBSD. The output is generally the same, but may vary
83 slightly. If you found you need identical output adding
84 "-F freebsd9" to the command line should do the trick. For the
85 time being, the old mtree is available as fmtree.
88 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
89 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
90 1.1.4_8 and verify bsdyml not linked in, before running "make
92 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
94 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
97 The rc.d/jail script has been updated to support jail(8)
98 configuration file. The "jail_<jname>_*" rc.conf(5) variables
99 for per-jail configuration are automatically converted to
100 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
101 This is transparently backward compatible. See below about some
102 incompatibilities and rc.conf(5) manual page for more details.
104 These variables are now deprecated in favor of jail(8) configuration
105 file. One can use "rc.d/jail config <jname>" command to generate
106 a jail(8) configuration file in /var/run/jail.<jname>.conf without
107 running the jail(8) utility. The default pathname of the
108 configuration file is /etc/jail.conf and can be specified by
109 using $jail_conf or $jail_<jname>_conf variables.
111 Please note that jail_devfs_ruleset accepts an integer at
112 this moment. Please consider to rewrite the ruleset name
116 BIND has been removed from the base system. If all you need
117 is a local resolver, simply enable and start the local_unbound
118 service instead. Otherwise, several versions of BIND are
119 available in the ports tree. The dns/bind99 port is one example.
121 With this change, nslookup(1) and dig(1) are no longer in the base
122 system. Users should instead use host(1) and drill(1) which are
123 in the base system. Alternatively, nslookup and dig can
124 be obtained by installing the dns/bind-tools port.
127 With the addition of unbound(8), a new unbound user is now
128 required during installworld. "mergemaster -p" can be used to
129 add the user prior to installworld, as documented in the handbook.
132 OpenSSH is now built with DNSSEC support, and will by default
133 silently trust signed SSHFP records. This can be controlled with
134 the VerifyHostKeyDNS client configuration setting. DNSSEC support
135 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
138 The GNU Compiler Collection and C++ standard library (libstdc++)
139 are no longer built by default on platforms where clang is the system
140 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
144 The PROCDESC kernel option is now part of the GENERIC kernel
145 configuration and is required for the rwhod(8) to work.
146 If you are using custom kernel configuration, you should include
150 The API and ABI related to the Capsicum framework was modified
151 in backward incompatible way. The userland libraries and programs
152 have to be recompiled to work with the new kernel. This includes the
153 following libraries and programs, but the whole buildworld is
154 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
155 kdump, procstat, rwho, rwhod, uniq.
158 AES-NI intrinsic support has been added to gcc. The AES-NI module
159 has been updated to use this support. A new gcc is required to build
160 the aesni module on both i386 and amd64.
163 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
164 Thus "device padlock_rng" and "device rdrand_rng" should be
165 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
168 WITH_ICONV has been split into two feature sets. WITH_ICONV now
169 enables just the iconv* functionality and is now on by default.
170 WITH_LIBICONV_COMPAT enables the libiconv api and link time
171 compatability. Set WITHOUT_ICONV to build the old way.
172 If you have been using WITH_ICONV before, you will very likely
173 need to turn on WITH_LIBICONV_COMPAT.
176 INVARIANTS option now enables DEBUG for code with OpenSolaris and
177 Illumos origin, including ZFS. If you have INVARIANTS in your
178 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
180 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
181 locks if WITNESS option was set. Because that generated a lot of
182 witness(9) reports and all of them were believed to be false
183 positives, this is no longer done. New option OPENSOLARIS_WITNESS
184 can be used to achieve the previous behavior.
187 Timer values in IPv6 data structures now use time_uptime instead
188 of time_second. Although this is not a user-visible functional
189 change, userland utilities which directly use them---ndp(8),
190 rtadvd(8), and rtsold(8) in the base system---need to be updated
194 find -delete can now delete the pathnames given as arguments,
195 instead of only files found below them or if the pathname did
196 not contain any slashes. Formerly, the following error message
199 find: -delete: <path>: relative path potentially not safe
201 Deleting the pathnames given as arguments can be prevented
202 without error messages using -mindepth 1 or by changing
203 directory and passing "." as argument to find. This works in the
204 old as well as the new version of find.
207 Behavior of devfs rules path matching has been changed.
208 Pattern is now always matched against fully qualified devfs
209 path and slash characters must be explicitly matched by
210 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
211 subdirectories must be reviewed.
214 The default ARM ABI has changed to the ARM EABI. The old ABI is
215 incompatible with the ARM EABI and all programs and modules will
216 need to be rebuilt to work with a new kernel.
218 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
220 NOTE: Support for the old ABI will be removed in the future and
221 users are advised to upgrade.
224 pkg_install has been disconnected from the build if you really need it
225 you should add WITH_PKGTOOLS in your src.conf(5).
228 Most of network statistics structures were changed to be able
229 keep 64-bits counters. Thus all tools, that work with networking
230 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
233 Fix targets that run multiple make's to use && rather than ;
234 so that subsequent steps depend on success of previous.
236 NOTE: if building 'universe' with -j* on stable/8 or stable/9
237 it would be better to start the build using bmake, to avoid
238 overloading the machine.
241 Fix a bug that allowed a tracing process (e.g. gdb) to write
242 to a memory-mapped file in the traced process's address space
243 even if neither the traced process nor the tracing process had
244 write access to that file.
247 CVS has been removed from the base system. An exact copy
248 of the code is available from the devel/cvs port.
251 Some people report the following error after the switch to bmake:
253 make: illegal option -- J
254 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
256 *** [buildworld] Error code 2
258 this likely due to an old instance of make in
259 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
260 which src/Makefile will use that blindly, if it exists, so if
261 you see the above error:
263 rm -rf `make -V MAKEPATH`
268 Use bmake by default.
269 Whereas before one could choose to build with bmake via
270 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
271 make. The goal is to remove these knobs for 10-RELEASE.
273 It is worth noting that bmake (like gmake) treats the command
274 line as the unit of failure, rather than statements within the
275 command line. Thus '(cd some/where && dosomething)' is safer
276 than 'cd some/where; dosomething'. The '()' allows consistent
277 behavior in parallel build.
280 Fix a bug that allows NFS clients to issue READDIR on files.
283 The WITHOUT_IDEA option has been removed because
284 the IDEA patent expired.
287 The sysctl which controls TRIM support under ZFS has been renamed
288 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
292 The mergemaster command now uses the default MAKEOBJDIRPREFIX
293 rather than creating it's own in the temporary directory in
294 order allow access to bootstrapped versions of tools such as
295 install and mtree. When upgrading from version of FreeBSD where
296 the install command does not support -l, you will need to
297 install a new mergemaster command if mergemaster -p is required.
298 This can be accomplished with the command (cd src/usr.sbin/mergemaster
302 Legacy ATA stack, disabled and replaced by new CAM-based one since
303 FreeBSD 9.0, completely removed from the sources. Kernel modules
304 atadisk and atapi*, user-level tools atacontrol and burncd are
305 removed. Kernel option `options ATA_CAM` is now permanently enabled
309 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
310 and socketpair(2). Software, in particular Kerberos, may
311 automatically detect and use these during building. The resulting
312 binaries will not work on older kernels.
315 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
316 information, see the respective 20130304 entry).
319 Recent commits to callout(9) changed the size of struct callout,
320 so the KBI is probably heavily disturbed. Also, some functions
321 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
322 by macros. Every kernel module using it won't load, so rebuild
325 The ctl device has been re-enabled in GENERIC for i386 and amd64,
326 but does not initialize by default (because of the new CTL_DISABLE
327 option) to save memory. To re-enable it, remove the CTL_DISABLE
328 option from the kernel config file or set kern.cam.ctl.disable=0
329 in /boot/loader.conf.
332 The ctl device has been disabled in GENERIC for i386 and amd64.
333 This was done due to the extra memory being allocated at system
334 initialisation time by the ctl driver which was only used if
335 a CAM target device was created. This makes a FreeBSD system
336 unusable on 128MB or less of RAM.
339 A new compression method (lz4) has been merged to -HEAD. Please
340 refer to zpool-features(7) for more information.
342 Please refer to the "ZFS notes" section of this file for information
343 on upgrading boot ZFS pools.
346 A BSD-licensed patch(1) variant has been added and is installed
347 as bsdpatch, being the GNU version the default patch.
348 To inverse the logic and use the BSD-licensed one as default,
349 while having the GNU version installed as gnupatch, rebuild
350 and install world with the WITH_BSD_PATCH knob set.
353 Due to the use of the new -l option to install(1) during build
354 and install, you must take care not to directly set the INSTALL
355 make variable in your /etc/make.conf, /etc/src.conf, or on the
356 command line. If you wish to use the -C flag for all installs
357 you may be able to add INSTALL+=-C to /etc/make.conf or
361 The install(1) option -M has changed meaning and now takes an
362 argument that is a file or path to append logs to. In the
363 unlikely event that -M was the last option on the command line
364 and the command line contained at least two files and a target
365 directory the first file will have logs appended to it. The -M
366 option served little practical purpose in the last decade so its
367 use is expected to be extremely rare.
370 After switching to Clang as the default compiler some users of ZFS
371 on i386 systems started to experience stack overflow kernel panics.
372 Please consider using 'options KSTACK_PAGES=4' in such configurations.
375 GEOM_LABEL now mangles label names read from file system metadata.
376 Mangling affect labels containing spaces, non-printable characters,
377 '%' or '"'. Device names in /etc/fstab and other places may need to
381 By default, only the 10 most recent kernel dumps will be saved. To
382 restore the previous behaviour (no limit on the number of kernel dumps
383 stored in the dump directory) add the following line to /etc/rc.conf:
388 With the addition of auditdistd(8), a new auditdistd user is now
389 required during installworld. "mergemaster -p" can be used to
390 add the user prior to installworld, as documented in the handbook.
393 The sin6_scope_id member variable in struct sockaddr_in6 is now
394 filled by the kernel before passing the structure to the userland via
395 sysctl or routing socket. This means the KAME-specific embedded scope
396 id in sin6_addr.s6_addr[2] is always cleared in userland application.
397 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
398 __FreeBSD_version is bumped to 1000025.
401 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
402 This means that the world and kernel will be compiled with clang
403 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
404 and /usr/bin/cpp. To disable this behavior and revert to building
405 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
406 of current may need to bootstrap WITHOUT_CLANG first if the clang
407 build fails (its compatibility window doesn't extend to the 9 stable
411 The IPFIREWALL_FORWARD kernel option has been removed. Its
412 functionality now turned on by default.
415 The ZERO_COPY_SOCKET kernel option has been removed and
416 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
417 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
418 mechanism which is not safe and may result in kernel crashes.
419 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
420 driver supports disposeable external page sized mbuf storage.
421 Proper replacements for both zero-copy mechanisms are under
422 consideration and will eventually lead to complete removal
423 of the two kernel options.
426 The IPv4 network stack has been converted to network byte
427 order. The following modules need to be recompiled together
428 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
429 pf(4), ipfw(4), ng_ipfw(4), stf(4).
432 Support for non-MPSAFE filesystems was removed from VFS. The
433 VFS_VERSION was bumped, all filesystem modules shall be
437 All the non-MPSAFE filesystems have been disconnected from
438 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
439 portalfs, smbfs, xfs.
442 The interface cloning API and ABI has changed. The following
443 modules need to be recompiled together with kernel:
444 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
445 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
446 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
449 The sdhci driver was split in two parts: sdhci (generic SD Host
450 Controller logic) and sdhci_pci (actual hardware driver).
451 No kernel config modifications are required, but if you
452 load sdhc as a module you must switch to sdhci_pci instead.
455 Import the FUSE kernel and userland support into base system.
458 The GNU sort(1) program has been removed since the BSD-licensed
459 sort(1) has been the default for quite some time and no serious
460 problems have been reported. The corresponding WITH_GNU_SORT
464 The pfil(9) API/ABI for AF_INET family has been changed. Packet
465 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
469 The net80211(4) ABI has been changed to allow for improved driver
470 PS-POLL and power-save support. All wireless drivers need to be
471 recompiled to work with the new kernel.
474 The random(4) support for the VIA hardware random number
475 generator (`PADLOCK') is no longer enabled unconditionally.
476 Add the padlock_rng device in the custom kernel config if
477 needed. The GENERIC kernels on i386 and amd64 do include the
478 device, so the change only affects the custom kernel
482 The pf(4) packet filter ABI has been changed. pfctl(8) and
483 snmp_pf module need to be recompiled to work with new kernel.
486 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
487 to -HEAD. Pools that have empty_bpobj in active state can not be
488 imported read-write with ZFS implementations that do not support
489 this feature. For more information read the zpool-features(5)
493 The sparc64 ZFS loader has been changed to no longer try to auto-
494 detect ZFS providers based on diskN aliases but now requires these
495 to be explicitly listed in the OFW boot-device environment variable.
498 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
499 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
500 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
503 The following sysctls and tunables have been renamed for consistency
504 with other variables:
505 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
506 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
509 The sort utility has been replaced with BSD sort. For now, GNU sort
510 is also available as "gnusort" or the default can be set back to
511 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
512 installed as "bsdsort".
515 A new version of ZFS (pool version 5000) has been merged to -HEAD.
516 Starting with this version the old system of ZFS pool versioning
517 is superseded by "feature flags". This concept enables forward
518 compatibility against certain future changes in functionality of ZFS
519 pools. The first read-only compatible "feature flag" for ZFS pools
520 is named "com.delphix:async_destroy". For more information
521 read the new zpool-features(5) manual page.
522 Please refer to the "ZFS notes" section of this file for information
523 on upgrading boot ZFS pools.
526 The malloc(3) implementation embedded in libc now uses sources imported
527 as contrib/jemalloc. The most disruptive API change is to
528 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
529 delete it prior to installworld, and optionally re-create it using the
530 new format after rebooting. See malloc.conf(5) for details
531 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
535 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
536 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
537 now spelled mips. This is to aid compatibility with third-party
538 software that expects this naming scheme in uname(3). Little-endian
539 settings are unchanged. If you are updating a big-endian mips64 machine
540 from before this change, you may need to set MACHINE_ARCH=mips64 in
541 your environment before the new build system will recognize your machine.
544 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
548 Now unix domain sockets behave "as expected" on nullfs(5). Previously
549 nullfs(5) did not pass through all behaviours to the underlying layer,
550 as a result if we bound to a socket on the lower layer we could connect
551 only to the lower path; if we bound to the upper layer we could connect
552 only to the upper path. The new behavior is one can connect to both the
553 lower and the upper paths regardless what layer path one binds to.
556 The getifaddrs upgrade path broken with 20111215 has been restored.
557 If you have upgraded in between 20111215 and 20120209 you need to
558 recompile libc again with your kernel. You still need to recompile
559 world to be able to configure CARP but this restriction already
563 The set_rcvar() function has been removed from /etc/rc.subr. All
564 base and ports rc.d scripts have been updated, so if you have a
565 port installed with a script in /usr/local/etc/rc.d you can either
566 hand-edit the rcvar= line, or reinstall the port.
568 An easy way to handle the mass-update of /etc/rc.d:
569 rm /etc/rc.d/* && mergemaster -i
572 panic(9) now stops other CPUs in the SMP systems, disables interrupts
573 on the current CPU and prevents other threads from running.
574 This behavior can be reverted using the kern.stop_scheduler_on_panic
576 The new behavior can be incompatible with kern.sync_on_panic.
579 The carp(4) facility has been changed significantly. Configuration
580 of the CARP protocol via ifconfig(8) has changed, as well as format
581 of CARP events submitted to devd(8) has changed. See manual pages
582 for more information. The arpbalance feature of carp(4) is currently
583 not supported anymore.
585 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
586 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
587 need to be recompiled.
590 The acpi_wmi(4) status device /dev/wmistat has been renamed to
594 The option VFS_ALLOW_NONMPSAFE option has been added in order to
595 explicitely support non-MPSAFE filesystems.
596 It is on by default for all supported platform at this present
600 The broken amd(4) driver has been replaced with esp(4) in the amd64,
601 i386 and pc98 GENERIC kernel configuration files.
604 sysinstall has been removed
607 The stable/9 branch created in subversion. This corresponds to the
608 RELENG_9 branch in CVS.
611 This commit modifies vfs_register() so that it uses a hash
612 calculation to set vfc_typenum, which is enabled by default.
613 The first time a system is booted after this change, the
614 vfc_typenum values will change for all file systems. The
615 main effect of this is a change to the NFS server file handles
616 for file systems that use vfc_typenum in their fsid, such as ZFS.
617 It will, however, prevent vfc_typenum from changing when file
618 systems are loaded in a different order for subsequent reboots.
619 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
620 until you are ready to remount all NFS clients after a reboot.
623 Bump the shared library version numbers for libraries that
624 do not use symbol versioning, have changed the ABI compared
625 to stable/8 and which shared library version was not bumped.
626 Done as part of 9.0-RELEASE cycle.
629 During the merge of Capsicum features, the fget(9) KPI was modified.
630 This may require the rebuilding of out-of-tree device drivers --
631 issues have been reported specifically with the nVidia device driver.
632 __FreeBSD_version is bumped to 900041.
634 Also, there is a period between 20110811 and 20110814 where the
635 special devices /dev/{stdin,stdout,stderr} did not work correctly.
636 Building world from a kernel during that window may not work.
639 The packet filter (pf) code has been updated to OpenBSD 4.5.
640 You need to update userland tools to be in sync with kernel.
641 This update breaks backward compatibility with earlier pfsync(4)
642 versions. Care must be taken when updating redundant firewall setups.
645 The following sysctls and tunables are retired on x86 platforms:
647 machdep.hlt_logical_cpus
648 The following sysctl is retired:
649 machdep.hyperthreading_allowed
650 The sysctls were supposed to provide a way to dynamically offline and
651 online selected CPUs on x86 platforms, but the implementation has not
652 been reliable especially with SCHED_ULE scheduler.
653 machdep.hyperthreading_allowed tunable is still available to ignore
654 hyperthreading CPUs at OS level.
655 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
656 where X is an APIC ID of a CPU. Be advised, though, that disabling
657 CPUs in non-uniform fashion will result in non-uniform topology and
658 may lead to sub-optimal system performance with SCHED_ULE, which is
662 cpumask_t type is retired and cpuset_t is used in order to describe
666 Changes to ifconfig(8) for dynamic address family detection mandate
667 that you are running a kernel of 20110525 or later. Make sure to
668 follow the update procedure to boot a new kernel before installing
672 Support for sun4v architecture is officially dropped
675 Several KPI breaking changes have been committed to the mii(4) layer,
676 the PHY drivers and consequently some Ethernet drivers using mii(4).
677 This means that miibus.ko and the modules of the affected Ethernet
678 drivers need to be recompiled.
680 Note to kernel developers: Given that the OUI bit reversion problem
681 was fixed as part of these changes all mii(4) commits related to OUIs,
682 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
683 handling, no longer can be merged verbatim to stable/8 and previous
687 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
688 into their kernel configurations along with 'device pci'.
691 The default NFS client is now the new NFS client, so fstype "newnfs"
692 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
693 Although mounts via fstype "nfs" will usually work without userland
694 changes, it is recommended that the mount(8) and mount_nfs(8)
695 commands be rebuilt from sources and that a link to mount_nfs called
696 mount_oldnfs be created. The new client is compiled into the
697 kernel with "options NFSCL" and this is needed for diskless root
698 file systems. The GENERIC kernel configs have been changed to use
699 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
700 To use the regular/old client, you can "mount -t oldnfs ...". For
701 a diskless root file system, you must also include a line like:
703 vfs.root.mountfrom="oldnfs:"
705 in the boot/loader.conf on the root fs on the NFS server to make
706 a diskless root fs use the old client.
709 The GENERIC kernels for all architectures now default to the new
710 CAM-based ATA stack. It means that all legacy ATA drivers were
711 removed and replaced by respective CAM drivers. If you are using
712 ATA device names in /etc/fstab or other places, make sure to update
713 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
714 where 'Y's are the sequential numbers starting from zero for each type
715 in order of detection, unless configured otherwise with tunables,
716 see cam(4)). There will be symbolic links created in /dev/ to map
717 old adX devices to the respective adaY. They should provide basic
718 compatibility for file systems mounting in most cases, but they do
719 not support old user-level APIs and do not have respective providers
720 in GEOM. Consider using updated management tools with new device names.
722 It is possible to load devices ahci, ata, siis and mvs as modules,
723 but option ATA_CAM should remain in kernel configuration to make ata
724 module work as CAM driver supporting legacy ATA controllers. Device ata
725 still can be used in modular fashion (atacore + ...). Modules atadisk
726 and atapi* are not used and won't affect operation in ATA_CAM mode.
727 Note that to use CAM-based ATA kernel should include CAM devices
728 scbus, pass, da (or explicitly ada), cd and optionally others. All of
729 them are parts of the cam module.
731 ataraid(4) functionality is now supported by the RAID GEOM class.
732 To use it you can load geom_raid kernel module and use graid(8) tool
733 for management. Instead of /dev/arX device names, use /dev/raid/rX.
735 No kernel config options or code have been removed, so if a problem
736 arises, please report it and optionally revert to the old ATA stack.
737 In order to do it you can remove from the kernel config:
742 , and instead add back:
743 device atadisk # ATA disk drives
744 device ataraid # ATA RAID drives
745 device atapicd # ATAPI CDROM drives
746 device atapifd # ATAPI floppy drives
747 device atapist # ATAPI tape drives
750 The default NFS server has been changed to the new server, which
751 was referred to as the experimental server. If you need to switch
752 back to the old NFS server, you must now put the "-o" option on
753 both the mountd and nfsd commands. This can be done using the
754 mountd_flags and nfs_server_flags rc.conf variables until an
755 update to the rc scripts is committed, which is coming soon.
758 The GNU Objective-C runtime library (libobjc), and other Objective-C
759 related components have been removed from the base system. If you
760 require an Objective-C library, please use one of the available ports.
763 ath(4) has been split into bus- and device- modules. if_ath contains
764 the HAL, the TX rate control and the network device code. if_ath_pci
765 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
766 contains the AHB glue. Users need to load both if_ath_pci and if_ath
767 in order to use ath on everything else.
769 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
770 need to load if_ath and if_ath_pci for ath(4) operation.
773 As part of the replacement of sysinstall, the process of building
774 release media has changed significantly. For details, please re-read
775 release(7), which has been updated to reflect the new build process.
778 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
779 is the last available version under GPLv2. It brings a number of new
780 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
781 4.1 and SSE 4.2), better support for powerpc64, a number of new
782 directives, and lots of other small improvements. See the ChangeLog
783 file in contrib/binutils for the full details.
786 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
787 compliant, and will now use half of hash for authentication.
788 This will break interoperability with all stacks (including all
789 actual FreeBSD versions) who implement
790 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
792 The only workaround with such peers is to use another HMAC
793 algorithm for IPsec ("phase 2") authentication.
796 Remove the uio_yield prototype and symbol. This function has
797 been misnamed since it was introduced and should not be
798 globally exposed with this name. The equivalent functionality
799 is now available using kern_yield(curthread->td_user_pri).
800 The function remains undocumented.
803 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
804 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
805 for scalar sysctls is defined but disabled. Code that needs
806 UQUAD to pass the type checking that must compile on older
807 systems where the define is not present can check against
808 __FreeBSD_version >= 900030.
810 The system dialog(1) has been replaced with a new version previously
811 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
812 with the previous version, but the libdialog associated with it has
813 a largely incompatible API. As such, the original version of libdialog
814 will be kept temporarily as libodialog, until its base system consumers
815 are replaced or updated. Bump __FreeBSD_version to 900030.
818 If you are trying to run make universe on a -stable system, and you get
819 the following warning:
820 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
821 unknown. config(8) likely too old."
822 or something similar to it, then you must upgrade your -stable system
823 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
824 stable/8) or build the config from the latest stable/8 branch and
825 install it on your system.
827 Prior to this date, building a current universe on 8-stable system from
828 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
829 error in the first kernel build phase. A new config on those old
830 systems will fix that problem for older versions of -current.
833 The TCP stack has been modified to allow Khelp modules to interact with
834 it via helper hook points and store per-connection data in the TCP
835 control block. Bump __FreeBSD_version to 900029. User space tools that
836 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
840 Generic IEEE 802.3 annex 31B full duplex flow control support has been
841 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
842 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
843 to take advantage of it instead of using custom implementations. This
844 means that these drivers now no longer unconditionally advertise
845 support for flow control but only do so if flow control is a selected
846 media option. This was implemented in the generic support that way in
847 order to allow flow control to be switched on and off via ifconfig(8)
848 with the PHY specific default to typically off in order to protect
849 from unwanted effects. Consequently, if you used flow control with
850 one of the above mentioned drivers you now need to explicitly enable
852 ifconfig bge0 media auto mediaopt flowcontrol
854 Along with the above mentioned changes generic support for setting
855 1000baseT master mode also has been added and brgphy(4), ciphy(4),
856 e1000phy(4) as well as ip1000phy(4) have been converted to take
857 advantage of it. This means that these drivers now no longer take the
858 link0 parameter for selecting master mode but the master media option
859 has to be used instead, for example like in the following:
860 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
862 Selection of master mode now is also available with all other PHY
863 drivers supporting 1000baseT.
866 The TCP stack has received a significant update to add support for
867 modularised congestion control and generally improve the clarity of
868 congestion control decisions. Bump __FreeBSD_version to 900025. User
869 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
870 sockstat) need to be recompiled.
873 The man(1) utility has been replaced by a new version that no longer
874 uses /etc/manpath.config. Please consult man.conf(5) for how to
875 migrate local entries to the new format.
878 The copyright strings printed by login(1) and sshd(8) at the time of a
879 new connection have been removed to follow other operating systems and
883 A workaround for a fixed ld bug has been removed in kernel code,
884 so make sure that your system ld is built from sources after
885 revision 210245 from 2010-07-19 (r211583 if building head kernel
886 on stable/8, r211584 for stable/7; both from 2010-08-21).
887 A symptom of incorrect ld version is different addresses for
888 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
891 The $ipv6_prefer variable in rc.conf(5) has been split into
892 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
894 The $ip6addrctl_policy is a variable to choose a pre-defined
895 address selection policy set by ip6addrctl(8). A value
896 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
899 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
900 flag (see an entry of 20090926) is set on an interface with no
901 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
902 security reason. If you want IPv6 link-local address on all
903 interfaces by default, set this to "YES".
905 The old ipv6_prefer="YES" is equivalent to
906 ipv6_activate_all_interfaces="YES" and
907 ip6addrctl_policy="ipv6_prefer".
910 DTrace has grown support for userland tracing. Due to this, DTrace is
911 now i386 and amd64 only.
912 dtruss(1) is now installed by default on those systems and a new
913 kernel module is needed for userland tracing: fasttrap.
914 No changes to your kernel config file are necessary to enable
915 userland tracing, but you might consider adding 'STRIP=' and
916 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
917 to have informative userland stack traces in DTrace (ustack).
920 The acpi_aiboost(4) driver has been removed in favor of the new
921 aibs(4) driver. You should update your kernel configuration file.
924 BSD grep has been imported to the base system and it is built by
925 default. It is completely BSD licensed, highly GNU-compatible, uses
926 less memory than its GNU counterpart and has a small codebase.
927 However, it is slower than its GNU counterpart, which is mostly
928 noticeable for larger searches, for smaller ones it is measurable
929 but not significant. The reason is complex, the most important factor
930 is that we lack a modern and efficient regex library and GNU
931 overcomes this by optimizing the searches internally. Future work
932 on improving the regex performance is planned, for the meantime,
933 users that need better performance, can build GNU grep instead by
934 setting the WITH_GNU_GREP knob.
937 Due to the import of powerpc64 support, all existing powerpc kernel
938 configuration files must be updated with a machine directive like this:
939 machine powerpc powerpc
941 In addition, an updated config(8) is required to build powerpc kernels
945 A new version of ZFS (version 15) has been merged to -HEAD.
946 This version uses a python library for the following subcommands:
947 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
948 For full functionality of these commands the following port must
949 be installed: sysutils/py-zfs
952 'vm_page's are now hashed by physical address to an array of mutexes.
953 Currently this is only used to serialize access to hold_count. Over
954 time the page queue mutex will be peeled away. This changes the size
955 of pmap on every architecture. And requires all callers of vm_page_hold
956 and vm_page_unhold to be updated.
959 WITH_CTF can now be specified in src.conf (not recommended, there
960 are some problems with static executables), make.conf (would also
961 affect ports which do not use GNU make and do not override the
962 compile targets) or in the kernel config (via "makeoptions
964 When WITH_CTF was specified there before this was silently ignored,
965 so make sure that WITH_CTF is not used in places which could lead
966 to unwanted behavior.
969 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
970 to allow 32-bit compatibility on non-x86 platforms. All kernel
971 configurations on amd64 and ia64 platforms using these options must
972 be modified accordingly.
975 The utmp user accounting database has been replaced with utmpx,
976 the user accounting interface standardized by POSIX.
977 Unfortunately the semantics of utmp and utmpx don't match,
978 making it practically impossible to support both interfaces.
979 The user accounting database is used by tools like finger(1),
980 last(1), talk(1), w(1) and ac(8).
982 All applications in the base system use utmpx. This means only
983 local binaries (e.g. from the ports tree) may still use these
984 utmp database files. These applications must be rebuilt to make
987 After the system has been upgraded, it is safe to remove the old
988 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
989 assuming their contents is of no importance anymore. Old wtmp
990 databases can only be used by last(1) and ac(8) after they have
991 been converted to the new format using wtmpcvt(1).
994 Introduce the kernel thread "deadlock resolver" (which can be enabled
995 via the DEADLKRES option, see NOTES for more details) and the
996 sleepq_type() function for sleepqueues.
999 The rc.firewall and rc.firewall6 were unified, and
1000 rc.firewall6 and rc.d/ip6fw were removed.
1001 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1002 variables are obsoleted. Instead, the following new rc
1003 variables are added to rc.d/ipfw:
1005 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1006 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1007 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1009 The meanings correspond to the relevant IPv4 variables.
1015 The default terminal emulation for syscons(4) has been changed
1016 from cons25 to xterm on all platforms except pc98. This means
1017 that the /etc/ttys file needs to be updated to ensure correct
1018 operation of applications on the console.
1020 The terminal emulation style can be toggled per window by using
1021 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1022 options can be used to change the compile-time default back to
1025 To prevent graphical artifacts, make sure the TERM environment
1026 variable is set to match the terminal emulation that is being
1027 performed by syscons(4).
1030 The layout of the structure ieee80211req_scan_result has changed.
1031 Applications that require wireless scan results (e.g. ifconfig(8))
1032 from net80211 need to be recompiled.
1034 Applications such as wpa_supplicant(8) may require a full world
1035 build without using NO_CLEAN in order to get synchronized with the
1039 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1040 There's one kernel module for each firmware. Adding "device iwnfw"
1041 to the kernel configuration file means including all three firmware
1042 images inside the kernel. If you want to include just the one for
1043 your wireless card, use the devices iwn4965fw, iwn5000fw or
1047 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1048 into rc.d/netif. The changes are the following:
1050 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1051 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1052 Note that both variables need the "inet6" keyword at the head.
1054 Do not set $ipv6_network_interfaces manually if you do not
1055 understand what you are doing. It is not needed in most cases.
1057 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1060 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1061 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1063 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1064 all configured interfaces have "inet6 accept_rtadv" in the
1065 $ifconfig_IF_ipv6. These are for backward compatibility.
1067 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1068 functionality of interfaces with no corresponding
1069 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1070 and the default address selection policy of ip6addrctl(8)
1071 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1072 Note that if you want to configure IPv6 functionality on the
1073 disabled interfaces after boot, first you need to clear the flag by
1074 using ifconfig(8) like:
1076 ifconfig em0 inet6 -ifdisabled
1078 If YES, the default address selection policy is set as
1081 The default value of $ipv6_prefer is NO.
1083 4. If your system need to receive Router Advertisement messages,
1084 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1085 scripts automatically invoke rtsol(8) when the interface becomes
1086 UP. The Router Advertisement messages are used for SLAAC
1087 (State-Less Address AutoConfiguration).
1090 802.11s D3.03 support was committed. This is incompatible with the
1091 previous code, which was based on D3.0.
1094 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1095 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1096 control whether accepting Router Advertisement messages or not.
1097 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1098 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1099 The ifconfig(8) utility now supports these flags.
1102 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1103 mount(8) and -a option for df(1) to see them.
1106 The old tunable hw.bus.devctl_disable has been superseded by
1107 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1108 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1112 Remove the option STOP_NMI. The default action is now to use NMI only
1113 for KDB via the newly introduced function stop_cpus_hard() and
1114 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1117 The stable/8 branch created in subversion. This corresponds to the
1118 RELENG_8 branch in CVS.
1121 Bump the shared library version numbers for all libraries that do not
1122 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1123 __FreeBSD_version to 800105.
1126 Due to changes in the implementation of virtual network stack support,
1127 all network-related kernel modules must be recompiled. As this change
1128 breaks the ABI, bump __FreeBSD_version to 800104.
1131 The TOE interface to the TCP syncache has been modified to remove
1132 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1133 The cxgb driver is the only TOE consumer affected by this change, and
1134 needs to be recompiled along with the kernel. As this change breaks
1135 the ABI, bump __FreeBSD_version to 800103.
1138 Padding has been added to struct tcpcb, sackhint and tcpstat in
1139 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1140 maintaining the ABI. However, this change breaks the ABI, so bump
1141 __FreeBSD_version to 800102. User space tools that rely on the size of
1142 any of these structs (e.g. sockstat) need to be recompiled.
1145 The NFS_LEGACYRPC option has been removed along with the old kernel
1146 RPC implementation that this option selected. Kernel configurations
1147 may need to be adjusted.
1150 The network interface device nodes at /dev/net/<interface> have been
1151 removed. All ioctl operations can be performed the normal way using
1152 routing sockets. The kqueue functionality can generally be replaced
1153 with routing sockets.
1156 The documentation from the FreeBSD Documentation Project (Handbook,
1157 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1158 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1161 The ABI of various structures related to the SYSV IPC API have been
1162 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1163 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1167 Layout of struct vnet has changed as routing related variables were
1168 moved to their own Vimage module. Modules need to be recompiled. Bump
1169 __FreeBSD_version to 800099.
1172 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1173 respectively. As long as no more than 16 groups per process are used,
1174 no changes should be visible. When more than 16 groups are used, old
1175 binaries may fail if they call getgroups() or getgrouplist() with
1176 statically sized storage. Recompiling will work around this, but
1177 applications should be modified to use dynamically allocated storage
1178 for group arrays as POSIX.1-2008 does not cap an implementation's
1179 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1181 NFS and portalfs mounts may also be affected as the list of groups is
1182 truncated to 16. Users of NFS who use more than 16 groups, should
1183 take care that negative group permissions are not used on the exported
1184 file systems as they will not be reliable unless a GSSAPI based
1185 authentication method is used.
1188 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1189 option compiles in the support for adaptive spinning for lockmgrs
1190 which want to enable it. The lockinit() function now accepts the flag
1191 LK_ADAPTIVE in order to make the lock object subject to adaptive
1192 spinning when both held in write and read mode.
1195 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1196 changed. User applications that use this ioctl need to be rebuilt.
1199 The layout of struct thread has changed. Kernel and modules need to
1203 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1204 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1207 window(1) has been removed from the base system. It can now be
1208 installed from ports. The port is called misc/window.
1211 The way we are storing and accessing `routing table' entries has
1212 changed. Programs reading the FIB, like netstat, need to be
1216 A new netisr implementation has been added for FreeBSD 8. Network
1217 file system modules, such as igmp, ipdivert, and others, should be
1219 Bump __FreeBSD_version to 800096.
1222 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1226 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1227 Bump __FreeBSD_version to 800094.
1230 Add mnt_xflag field to 'struct mount'. File system modules need to be
1232 Bump __FreeBSD_version to 800093.
1235 The compiling option ADAPTIVE_SX has been retired while it has been
1236 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1237 The KPI for sx_init_flags() changes as accepting flags:
1238 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1239 been introduced in order to handle the reversed logic.
1240 Bump __FreeBSD_version to 800092.
1243 Add support for hierarchical jails. Remove global securelevel.
1244 Bump __FreeBSD_version to 800091.
1247 The layout of struct vnet_net has changed, therefore modules
1249 Bump __FreeBSD_version to 800090.
1252 The newly imported zic(8) produces a new format in the output. Please
1253 run tzsetup(8) to install the newly created data to /etc/localtime.
1256 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1257 hw.usb.* and is now consistent again with previous releases.
1260 802.11 monitor mode support was revised and driver api's were changed.
1261 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1262 of DLT_IEEE802_11. No user-visible data structures were changed but
1263 applications that use DLT_IEEE802_11 may require changes.
1264 Bump __FreeBSD_version to 800088.
1267 The layout of the following structs has changed: sysctl_oid,
1268 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1269 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1270 panics may be experienced. World rebuild is required for
1271 correctly checking networking state from userland.
1272 Bump __FreeBSD_version to 800085.
1275 MLDv2 and Source-Specific Multicast (SSM) have been merged
1276 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1277 The implementation of SSM within FreeBSD's IPv6 stack closely
1278 follows the IPv4 implementation.
1280 For kernel developers:
1282 * The most important changes are that the ip6_output() and
1283 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1284 and this lock has been downgraded to a non-recursive mutex.
1286 * As with the changes to the IPv4 stack to support SSM, filtering
1287 of inbound multicast traffic must now be performed by transport
1288 protocols within the IPv6 stack. This does not apply to TCP and
1289 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1291 * The KPIs used by IPv6 multicast are similar to those used by
1292 the IPv4 stack, with the following differences:
1293 * im6o_mc_filter() is analogous to imo_multicast_filter().
1294 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1295 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1296 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1297 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1298 for MLDv1 have an additional 'timer' argument which is used to
1299 jitter the initial membership report for the solicited-node
1300 multicast membership on-link.
1301 * This is not strictly needed for MLDv2, which already jitters
1302 its report transmissions. However, the 'timer' argument is
1303 preserved in case MLDv1 is active on the interface.
1305 * The KAME linked-list based IPv6 membership implementation has
1306 been refactored to use a vector similar to that used by the IPv4
1308 Code which maintains a list of its own multicast memberships
1309 internally, e.g. carp, has been updated to reflect the new
1312 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1313 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1314 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1315 implementation constraint which needs to be addressed in HEAD.
1317 For application developers:
1319 * The changes are broadly similar to those made for the IPv4
1322 * The use of IPv4 and IPv6 multicast socket options on the same
1323 socket, using mapped addresses, HAS NOT been tested or supported.
1325 * There are a number of issues with the implementation of various
1326 IPv6 multicast APIs which need to be resolved in the API surface
1327 before the implementation is fully compatible with KAME userland
1328 use, and these are mostly to do with interface index treatment.
1330 * The literature available discusses the use of either the delta / ASM
1331 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1332 using setsourcefilter(3)/getsourcefilter(3). For more information
1333 please refer to RFC 3768, 'Socket Interface Extensions for
1334 Multicast Source Filters'.
1336 * Applications which use the published RFC 3678 APIs should be fine.
1338 For systems administrators:
1340 * The mtest(8) utility has been refactored to support IPv6, in
1341 addition to IPv4. Interface addresses are no longer accepted
1342 as arguments, their names must be used instead. The utility
1343 will map the interface name to its first IPv4 address as
1344 returned by getifaddrs(3).
1346 * The ifmcstat(8) utility has also been updated to print the MLDv2
1347 endpoint state and source filter lists via sysctl(3).
1349 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1350 loopback of IPv6 multicast datagrams by default; it defaults to 1
1351 to preserve the existing behaviour. Disabling multicast loopback is
1352 recommended for optimal system performance.
1354 * The IPv6 MROUTING code has been changed to examine this sysctl
1355 instead of attempting to perform a group lookup before looping
1356 back forwarded datagrams.
1358 Bump __FreeBSD_version to 800084.
1361 Implement low-level Bluetooth HCI API.
1362 Bump __FreeBSD_version to 800083.
1365 The layout of struct malloc_type, used by modules to register new
1366 memory allocation types, has changed. Most modules will need to
1367 be rebuilt or panics may be experienced.
1368 Bump __FreeBSD_version to 800081.
1371 Anticipate overflowing inp_flags - add inp_flags2.
1372 This changes most offsets in inpcb, so checking v4 connection
1373 state will require a world rebuild.
1374 Bump __FreeBSD_version to 800080.
1377 Add an llentry to struct route and struct route_in6. Modules
1378 embedding a struct route will need to be recompiled.
1379 Bump __FreeBSD_version to 800079.
1382 The size of rt_metrics_lite and by extension rtentry has changed.
1383 Networking administration apps will need to be recompiled.
1384 The route command now supports show as an alias for get, weighting
1385 of routes, sticky and nostick flags to alter the behavior of stateful
1387 Bump __FreeBSD_version to 800078.
1390 Do not use Giant for kbdmux(4) locking. This is wrong and
1391 apparently causing more problems than it solves. This will
1392 re-open the issue where interrupt handlers may race with
1393 kbdmux(4) in polling mode. Typical symptoms include (but
1394 not limited to) duplicated and/or missing characters when
1395 low level console functions (such as gets) are used while
1396 interrupts are enabled (for example geli password prompt,
1397 mountroot prompt etc.). Disabling kbdmux(4) may help.
1400 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1401 kernel modules referencing any of the above need to be recompiled.
1402 Bump __FreeBSD_version to 800075.
1405 GEOM_PART has become the default partition slicer for storage devices,
1406 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1407 introduces some changes:
1409 MSDOS/EBR: the devices created from MSDOS extended partition entries
1410 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1411 to devices with offset-based names. fstabs may need to be modified.
1413 BSD: the "geometry does not match label" warning is harmless in most
1414 cases but it points to problems in file system misalignment with
1415 disk geometry. The "c" partition is now implicit, covers the whole
1416 top-level drive and cannot be (mis)used by users.
1418 General: Kernel dumps are now not allowed to be written to devices
1419 whose partition types indicate they are meant to be used for file
1420 systems (or, in case of MSDOS partitions, as something else than
1423 Most of these changes date approximately from 200812.
1426 The uscanner(4) driver has been removed from the kernel. This follows
1427 Linux removing theirs in 2.6 and making libusb the default interface
1428 (supported by sane).
1431 The multicast forwarding code has been cleaned up. netstat(1)
1432 only relies on KVM now for printing bandwidth upcall meters.
1433 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1434 ip6_mroute_mod respectively. The config(5) options for statically
1435 compiling this code remain the same, i.e. 'options MROUTING'.
1438 Support for the IFF_NEEDSGIANT network interface flag has been
1439 removed, which means that non-MPSAFE network device drivers are no
1440 longer supported. In particular, if_ar, if_sr, and network device
1441 drivers from the old (legacy) USB stack can no longer be built or
1445 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1446 a bunch of new language catalog files have also been added.
1447 This means that some common libc messages are now localized and
1448 they depend on the LC_MESSAGES environmental variable.
1451 The k8temp(4) driver has been renamed to amdtemp(4) since
1452 support for Family 10 and Family 11 CPU families was added.
1455 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1456 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1458 For kernel developers, the most important changes are that the
1459 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1460 and this lock has been downgraded to a non-recursive mutex.
1462 Transport protocols (UDP, Raw IP) are now responsible for filtering
1463 inbound multicast traffic according to group membership and source
1464 filters. The imo_multicast_filter() KPI exists for this purpose.
1465 Transports which do not use multicast (SCTP, TCP) already reject
1466 multicast by default. Forwarding and receive performance may improve
1467 as a mutex acquisition is no longer needed in the ip_input()
1468 low-level input path. in_addmulti() and in_delmulti() are shimmed
1469 to new KPIs which exist to support SSM in-kernel.
1471 For application developers, it is recommended that loopback of
1472 multicast datagrams be disabled for best performance, as this
1473 will still cause the lock to be taken for each looped-back
1474 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1475 be tuned to 0 to disable loopback by default; it defaults to 1
1476 to preserve the existing behaviour.
1478 For systems administrators, to obtain best performance with
1479 multicast reception and multiple groups, it is always recommended
1480 that a card with a suitably precise hash filter is used. Hash
1481 collisions will still result in the lock being taken within the
1482 transport protocol input path to check group membership.
1484 If deploying FreeBSD in an environment with IGMP snooping switches,
1485 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1486 enabled; this forces 224.0.0.0/24 group membership to be announced
1489 The size of 'struct igmpstat' has changed; netstat needs to be
1490 recompiled to reflect this.
1491 Bump __FreeBSD_version to 800070.
1494 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1495 updated to use it. This requires a buildworld/installworld in order to
1496 update the library and dependencies (usbconfig, etc). Its advisable to
1497 rebuild all ports which uses libusb. More specific directions are given
1498 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1499 libusb are no longer required and can be removed.
1502 A workaround is committed to allow the creation of System V shared
1503 memory segment of size > 2 GB on the 64-bit architectures.
1504 Due to a limitation of the existing ABI, the shm_segsz member
1505 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1506 wrong for large segments. Note that limits must be explicitly
1507 raised to allow such segments to be created.
1510 The layout of struct ifnet has changed, requiring a rebuild of all
1511 network device driver modules.
1514 The /dev handling for the new USB stack has changed, a
1515 buildworld/installworld is required for libusb20.
1518 The new USB2 stack has now been permanently moved in and all kernel and
1519 module names reverted to their previous values (eg, usb, ehci, ohci,
1520 ums, ...). The old usb stack can be compiled in by prefixing the name
1521 with the letter 'o', the old usb modules have been removed.
1522 Updating entry 20090216 for xorg and 20090215 for libmap may still
1526 The rc.conf(5) option if_up_delay has been renamed to
1527 defaultroute_delay to better reflect its purpose. If you have
1528 customized this setting in /etc/rc.conf you need to update it to
1532 xorg 7.4 wants to configure its input devices via hald which does not
1533 yet work with USB2. If the keyboard/mouse does not work in xorg then
1535 Option "AllowEmptyInput" "off"
1536 to your ServerLayout section. This will cause X to use the configured
1537 kbd and mouse sections from your xorg.conf.
1540 The GENERIC kernels for all architectures now default to the new USB2
1541 stack. No kernel config options or code have been removed so if a
1542 problem arises please report it and optionally revert to the old USB
1543 stack. If you are loading USB kernel modules or have a custom kernel
1544 that includes GENERIC then ensure that usb names are also changed over,
1545 eg uftdi -> usb2_serial_ftdi.
1547 Older programs linked against the ports libusb 0.1 need to be
1548 redirected to the new stack's libusb20. /etc/libmap.conf can
1550 # Map old usb library to new one for usb2 stack
1551 libusb-0.1.so.8 libusb20.so.1
1554 All USB ethernet devices now attach as interfaces under the name ueN
1555 (eg. ue0). This is to provide a predictable name as vendors often
1556 change usb chipsets in a product without notice.
1559 The ichsmb(4) driver has been changed to require SMBus slave
1560 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1561 All of the other SMBus controller drivers require left-justified
1562 slave addresses, so this change makes all the drivers provide the
1566 INET6 statistics (struct ip6stat) was updated.
1567 netstat(1) needs to be recompiled.
1570 NTFS has been removed from GENERIC kernel on amd64 to match
1571 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1572 will load ntfs.ko module automatically when NTFS support is
1573 actually needed, unless ntfs.ko is not installed or security
1574 level prohibits loading kernel modules. If either is the case,
1575 "options NTFS" has to be added into kernel config.
1578 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1579 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1580 800061. User space tools that rely on the size of struct tcpcb in
1581 tcp_var.h (e.g. sockstat) need to be recompiled.
1584 ng_tty(4) module updated to match the new TTY subsystem.
1585 Due to API change, user-level applications must be updated.
1586 New API support added to mpd5 CVS and expected to be present
1587 in next mpd5.3 release.
1590 With __FreeBSD_version 800060 the makefs tool is part of
1591 the base system (it was a port).
1594 The afdata and ifnet locks have been changed from mutexes to
1595 rwlocks, network modules will need to be re-compiled.
1598 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1599 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1600 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1601 architecture and 40 bytes on 64-bit architecture. The userland
1602 applications "arp" and "ndp" have been updated accordingly.
1603 The output from "netstat -r" shows only routing entries and
1604 none of the L2 information.
1607 __FreeBSD_version 800057 marks the switchover from the
1608 binary ath hal to source code. Users must add the line:
1610 options AH_SUPPORT_AR5416
1612 to their kernel config files when specifying:
1616 The ath_hal module no longer exists; the code is now compiled
1617 together with the driver in the ath module. It is now
1618 possible to tailor chip support (i.e. reduce the set of chips
1619 and thereby the code size); consult ath_hal(4) for details.
1622 __FreeBSD_version 800054 adds memory barriers to
1623 <machine/atomic.h>, new interfaces to ifnet to facilitate
1624 multiple hardware transmit queues for cards that support
1625 them, and a lock-less ring-buffer implementation to
1626 enable drivers to more efficiently manage queueing of
1630 A new version of ZFS (version 13) has been merged to -HEAD.
1631 This version has zpool attribute "listsnapshots" off by
1632 default, which means "zfs list" does not show snapshots,
1633 and is the same as Solaris behavior.
1636 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1639 The uhci, ohci, ehci and slhci USB Host controller drivers have
1640 been put into separate modules. If you load the usb module
1641 separately through loader.conf you will need to load the
1642 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1643 controller add the following to loader.conf:
1649 The ABI used by the PMC toolset has changed. Please keep
1650 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1654 atapci kernel module now includes only generic PCI ATA
1655 driver. AHCI driver moved to ataahci kernel module.
1656 All vendor-specific code moved into separate kernel modules:
1657 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1658 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1659 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1660 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1663 The TTY subsystem of the kernel has been replaced by a new
1664 implementation, which provides better scalability and an
1665 improved driver model. Most common drivers have been migrated to
1666 the new TTY subsystem, while others have not. The following
1667 drivers have not yet been ported to the new TTY layer:
1670 cy, digi, rc, rp, sio
1676 ng_h4, ng_tty, ppp, sl, snp
1678 Adding these drivers to your kernel configuration file shall
1679 cause compilation to fail.
1682 ntpd has been upgraded to 4.2.4p5.
1685 OpenSSH has been upgraded to 5.1p1.
1687 For many years, FreeBSD's version of OpenSSH preferred DSA
1688 over RSA for host and user authentication keys. With this
1689 upgrade, we've switched to the vendor's default of RSA over
1690 DSA. This may cause upgraded clients to warn about unknown
1691 host keys even for previously known hosts. Users should
1692 follow the usual procedure for verifying host keys before
1693 accepting the RSA key.
1695 This can be circumvented by setting the "HostKeyAlgorithms"
1696 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1699 Please note that the sequence of keys offered for
1700 authentication has been changed as well. You may want to
1701 specify IdentityFile in a different order to revert this
1705 The sio(4) driver has been removed from the i386 and amd64
1706 kernel configuration files. This means uart(4) is now the
1707 default serial port driver on those platforms as well.
1709 To prevent collisions with the sio(4) driver, the uart(4) driver
1710 uses different names for its device nodes. This means the
1711 onboard serial port will now most likely be called "ttyu0"
1712 instead of "ttyd0". You may need to reconfigure applications to
1713 use the new device names.
1715 When using the serial port as a boot console, be sure to update
1716 /boot/device.hints and /etc/ttys before booting the new kernel.
1717 If you forget to do so, you can still manually specify the hints
1718 at the loader prompt:
1720 set hint.uart.0.at="isa"
1721 set hint.uart.0.port="0x3F8"
1722 set hint.uart.0.flags="0x10"
1723 set hint.uart.0.irq="4"
1727 The gpt(8) utility has been removed. Use gpart(8) to partition
1731 The version that Linuxulator emulates was changed from 2.4.2
1732 to 2.6.16. If you experience any problems with Linux binaries
1733 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1734 if it fixes the problem contact emulation mailing list.
1737 ISDN4BSD (I4B) was removed from the src tree. You may need to
1738 update a your kernel configuration and remove relevant entries.
1741 I have checked in code to support multiple routing tables.
1742 See the man pages setfib(1) and setfib(2).
1743 This is a hopefully backwards compatible version,
1744 but to make use of it you need to compile your kernel
1745 with options ROUTETABLES=2 (or more up to 16).
1748 The 802.11 wireless support was redone to enable multi-bss
1749 operation on devices that are capable. The underlying device
1750 is no longer used directly but instead wlanX devices are
1751 cloned with ifconfig. This requires changes to rc.conf files.
1752 For example, change:
1753 ifconfig_ath0="WPA DHCP"
1756 ifconfig_wlan0="WPA DHCP"
1757 see rc.conf(5) for more details. In addition, mergemaster of
1758 /etc/rc.d is highly recommended. Simultaneous update of userland
1759 and kernel wouldn't hurt either.
1761 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1762 modules were merged into the base wlan module. All references
1763 to these modules (e.g. in kernel config files) must be removed.
1766 psm(4) has gained write(2) support in native operation level.
1767 Arbitrary commands can be written to /dev/psm%d and status can
1768 be read back from it. Therefore, an application is responsible
1769 for status validation and error recovery. It is a no-op in
1770 other operation levels.
1773 Support for KSE threading has been removed from the kernel. To
1774 run legacy applications linked against KSE libmap.conf may
1775 be used. The following libmap.conf may be used to ensure
1776 compatibility with any prior release:
1778 libpthread.so.1 libthr.so.1
1779 libpthread.so.2 libthr.so.2
1780 libkse.so.3 libthr.so.3
1783 The layout of struct vmspace has changed. This affects libkvm
1784 and any executables that link against libkvm and use the
1785 kvm_getprocs() function. In particular, but not exclusively,
1786 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1787 The effects are minimal, but it's advisable to upgrade world
1791 The latest em driver no longer has support in it for the
1792 82575 adapter, this is now moved to the igb driver. The
1793 split was done to make new features that are incompatible
1794 with older hardware easier to do.
1797 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1798 likewise the kernel option is now GEOM_LINUX_LVM.
1801 The default NFS mount mode has changed from UDP to TCP for
1802 increased reliability. If you rely on (insecurely) NFS
1803 mounting across a firewall you may need to update your
1807 Belatedly note the addition of m_collapse for compacting
1811 The fts(3) structures have been changed to use adequate
1812 integer types for their members and so to be able to cope
1813 with huge file trees. The old fts(3) ABI is preserved
1814 through symbol versioning in libc, so third-party binaries
1815 using fts(3) should still work, although they will not take
1816 advantage of the extended types. At the same time, some
1817 third-party software might fail to build after this change
1818 due to unportable assumptions made in its source code about
1819 fts(3) structure members. Such software should be fixed
1820 by its vendor or, in the worst case, in the ports tree.
1821 FreeBSD_version 800015 marks this change for the unlikely
1822 case that a portable fix is impossible.
1825 To upgrade to -current after this date, you must be running
1826 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1827 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1830 The ADAPTIVE_GIANT kernel option has been retired because its
1831 functionality is the default now.
1834 The AT keyboard emulation of sunkbd(4) has been turned on
1835 by default. In order to make the special symbols of the Sun
1836 keyboards driven by sunkbd(4) work under X these now have
1837 to be configured the same way as Sun USB keyboards driven
1838 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1840 Option "XkbLayout" "us"
1841 Option "XkbRules" "xorg"
1842 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1845 It has been decided that it is desirable to provide ABI
1846 backwards compatibility to the FreeBSD 4/5/6 versions of the
1847 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1848 broken with the introduction of PCI domain support (see the
1849 20070930 entry). Unfortunately, this required the ABI of
1850 PCIOCGETCONF to be broken again in order to be able to
1851 provide backwards compatibility to the old version of that
1852 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1853 again. As for prominent ports this affects neither pciutils
1854 nor xorg-server this time, the hal port needs to be rebuilt
1858 The misnamed kthread_create() and friends have been renamed
1859 to kproc_create() etc. Many of the callers already
1860 used kproc_start()..
1861 I will return kthread_create() and friends in a while
1862 with implementations that actually create threads, not procs.
1863 Renaming corresponds with version 800002.
1872 Avoid using make -j when upgrading. While generally safe, there are
1873 sometimes problems using -j to upgrade. If your upgrade fails with
1874 -j, please try again without -j. From time to time in the past there
1875 have been problems using -j with buildworld and/or installworld. This
1876 is especially true when upgrading between "distant" versions (eg one
1877 that cross a major release boundary or several minor releases, or when
1878 several months have passed on the -current branch).
1880 Sometimes, obscure build problems are the result of environment
1881 poisoning. This can happen because the make utility reads its
1882 environment when searching for values for global variables. To run
1883 your build attempts in an "environmental clean room", prefix all make
1884 commands with 'env -i '. See the env(1) manual page for more details.
1886 When upgrading from one major version to another it is generally best
1887 to upgrade to the latest code in the currently installed branch first,
1888 then do an upgrade to the new branch. This is the best-tested upgrade
1889 path, and has the highest probability of being successful. Please try
1890 this approach before reporting problems with a major version upgrade.
1892 When upgrading a live system, having a root shell around before
1893 installing anything can help undo problems. Not having a root shell
1894 around can lead to problems if pam has changed too much from your
1895 starting point to allow continued authentication after the upgrade.
1899 When upgrading the boot ZFS pool to a new version, always follow
1902 1.) recompile and reinstall the ZFS boot loader and boot block
1903 (this is part of "make buildworld" and "make installworld")
1905 2.) update the ZFS boot block on your boot drive
1907 The following example updates the ZFS boot block on the first
1908 partition (freebsd-boot) of a GPT partitioned drive ad0:
1909 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1911 Non-boot pools do not need these updates.
1915 If you are updating from a prior version of FreeBSD (even one just
1916 a few days old), you should follow this procedure. It is the most
1917 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1919 make kernel-toolchain
1920 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1921 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1923 To test a kernel once
1924 ---------------------
1925 If you just want to boot a kernel once (because you are not sure
1926 if it works, or if you want to boot a known bad kernel to provide
1927 debugging information) run
1928 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1929 nextboot -k testkernel
1931 To just build a kernel when you know that it won't mess you up
1932 --------------------------------------------------------------
1933 This assumes you are already running a CURRENT system. Replace
1934 ${arch} with the architecture of your machine (e.g. "i386",
1935 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1937 cd src/sys/${arch}/conf
1938 config KERNEL_NAME_HERE
1939 cd ../compile/KERNEL_NAME_HERE
1944 If this fails, go to the "To build a kernel" section.
1946 To rebuild everything and install it on the current system.
1947 -----------------------------------------------------------
1948 # Note: sometimes if you are running current you gotta do more than
1949 # is listed here if you are upgrading from a really old current.
1951 <make sure you have good level 0 dumps>
1953 make kernel KERNCONF=YOUR_KERNEL_HERE
1955 <reboot in single user> [3]
1962 To cross-install current onto a separate partition
1963 --------------------------------------------------
1964 # In this approach we use a separate partition to hold
1965 # current's root, 'usr', and 'var' directories. A partition
1966 # holding "/", "/usr" and "/var" should be about 2GB in
1969 <make sure you have good level 0 dumps>
1972 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1973 <maybe newfs current's root partition>
1974 <mount current's root partition on directory ${CURRENT_ROOT}>
1975 make installworld DESTDIR=${CURRENT_ROOT} -DDB_FROM_SRC
1976 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1977 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1978 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1979 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1980 <reboot into current>
1981 <do a "native" rebuild/install as described in the previous section>
1982 <maybe install compatibility libraries from ports/misc/compat*>
1986 To upgrade in-place from stable to current
1987 ----------------------------------------------
1988 <make sure you have good level 0 dumps>
1990 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1992 <reboot in single user> [3]
1999 Make sure that you've read the UPDATING file to understand the
2000 tweaks to various things you need. At this point in the life
2001 cycle of current, things change often and you are on your own
2002 to cope. The defaults can also change, so please read ALL of
2003 the UPDATING entries.
2005 Also, if you are tracking -current, you must be subscribed to
2006 freebsd-current@freebsd.org. Make sure that before you update
2007 your sources that you have read and understood all the recent
2008 messages there. If in doubt, please track -stable which has
2009 much fewer pitfalls.
2011 [1] If you have third party modules, such as vmware, you
2012 should disable them at this point so they don't crash your
2015 [3] From the bootblocks, boot -s, and then do
2020 adjkerntz -i # if CMOS is wall time
2021 Also, when doing a major release upgrade, it is required that
2022 you boot into single user mode to do the installworld.
2024 [4] Note: This step is non-optional. Failure to do this step
2025 can result in a significant reduction in the functionality of the
2026 system. Attempting to do it by hand is not recommended and those
2027 that pursue this avenue should read this file carefully, as well
2028 as the archives of freebsd-current and freebsd-hackers mailing lists
2029 for potential gotchas. The -U option is also useful to consider.
2030 See mergemaster(8) for more information.
2032 [5] Usually this step is a noop. However, from time to time
2033 you may need to do this if you get unknown user in the following
2034 step. It never hurts to do it all the time. You may need to
2035 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2036 install) after the buildworld before this step if you last updated
2037 from current before 20130425 or from -stable before 20130430.
2039 [6] This only deletes old files and directories. Old libraries
2040 can be deleted by "make delete-old-libs", but you have to make
2041 sure that no program is using those libraries anymore.
2043 [8] In order to have a kernel that can run the 4.x binaries needed to
2044 do an installworld, you must include the COMPAT_FREEBSD4 option in
2045 your kernel. Failure to do so may leave you with a system that is
2046 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2047 required to run the 5.x binaries on more recent kernels. And so on
2048 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2050 Make sure that you merge any new devices from GENERIC since the
2051 last time you updated your kernel config file.
2053 [9] When checking out sources, you must include the -P flag to have
2054 cvs prune empty directories.
2056 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2057 "?=" instead of the "=" assignment operator, so that buildworld can
2058 override the CPUTYPE if it needs to.
2060 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2061 not on the command line, or in /etc/make.conf. buildworld will
2062 warn if it is improperly defined.
2065 This file contains a list, in reverse chronological order, of major
2066 breakages in tracking -current. It is not guaranteed to be a complete
2067 list of such breakages, and only contains entries since October 10, 2007.
2068 If you need to see UPDATING entries from before that date, you will need
2069 to fetch an UPDATING file from an older FreeBSD release.
2071 Copyright information:
2073 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2075 Redistribution, publication, translation and use, with or without
2076 modification, in full or in part, in any form or format of this
2077 document are permitted without further permission from the author.
2079 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2080 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2081 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2082 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2083 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2084 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2085 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2086 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2087 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2088 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2089 POSSIBILITY OF SUCH DAMAGE.
2091 Contact Warner Losh if you have any questions about your use of