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 Several ABI breaking changes were merged to CTL and new iSCSI code.
21 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
22 iscsictl need to be rebuilt to work with a new kernel.
25 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
26 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
27 which differs from the behaviour controlled by this knob.)
30 On i386 and amd64 systems, the onifconsole flag is now set by default
31 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
32 as a login TTY if it is set in the bootloader as an active kernel
33 console. No changes in behavior should result otherwise. To revert to
34 the previous behavior, set ttyu0 to "off" in /etc/ttys.
37 Clang and llvm have been upgraded to 3.4.1 release.
40 Clang and llvm have been upgraded to 3.4 release.
43 If a Makefile in a tests/ directory was auto-generating a Kyuafile
44 instead of providing an explicit one, this would prevent such
45 Makefile from providing its own Kyuafile in the future during
46 NO_CLEAN builds. This has been fixed in the Makefiles but manual
47 intervention is needed to clean an objdir if you use NO_CLEAN:
48 # find /usr/obj -name Kyuafile | xargs rm -f
51 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
52 capability mode support. Please note that enabling the feature in
53 kernel is still highly recommended.
56 OpenSSH is now built with sandbox support, and will use sandbox as
57 the default privilege separation method. This requires Capsicum
58 capability mode support in kernel.
61 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
62 been deprecated and will not be part of FreeBSD 11.0 and later
63 releases. If you use this driver, please consider switching to
64 the nfe(4) driver instead.
70 The behavior of gss_pseudo_random() for the krb5 mechanism
71 has changed, for applications requesting a longer random string
72 than produced by the underlying enctype's pseudo-random() function.
73 In particular, the random string produced from a session key of
74 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
75 be different at the 17th octet and later, after this change.
76 The counter used in the PRF+ construction is now encoded as a
77 big-endian integer in accordance with RFC 4402.
78 __FreeBSD_version is bumped to 1000701.
81 The WITHOUT_ATF build knob has been removed and its functionality
82 has been subsumed into the more generic WITHOUT_TESTS. If you were
83 using the former to disable the build of the ATF libraries, you
84 should change your settings to use the latter.
87 The default version of mtree is nmtree which is obtained from
88 NetBSD. The output is generally the same, but may vary
89 slightly. If you found you need identical output adding
90 "-F freebsd9" to the command line should do the trick. For the
91 time being, the old mtree is available as fmtree.
94 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
95 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
96 1.1.4_8 and verify bsdyml not linked in, before running "make
98 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
100 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
103 The rc.d/jail script has been updated to support jail(8)
104 configuration file. The "jail_<jname>_*" rc.conf(5) variables
105 for per-jail configuration are automatically converted to
106 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
107 This is transparently backward compatible. See below about some
108 incompatibilities and rc.conf(5) manual page for more details.
110 These variables are now deprecated in favor of jail(8) configuration
111 file. One can use "rc.d/jail config <jname>" command to generate
112 a jail(8) configuration file in /var/run/jail.<jname>.conf without
113 running the jail(8) utility. The default pathname of the
114 configuration file is /etc/jail.conf and can be specified by
115 using $jail_conf or $jail_<jname>_conf variables.
117 Please note that jail_devfs_ruleset accepts an integer at
118 this moment. Please consider to rewrite the ruleset name
122 BIND has been removed from the base system. If all you need
123 is a local resolver, simply enable and start the local_unbound
124 service instead. Otherwise, several versions of BIND are
125 available in the ports tree. The dns/bind99 port is one example.
127 With this change, nslookup(1) and dig(1) are no longer in the base
128 system. Users should instead use host(1) and drill(1) which are
129 in the base system. Alternatively, nslookup and dig can
130 be obtained by installing the dns/bind-tools port.
133 With the addition of unbound(8), a new unbound user is now
134 required during installworld. "mergemaster -p" can be used to
135 add the user prior to installworld, as documented in the handbook.
138 OpenSSH is now built with DNSSEC support, and will by default
139 silently trust signed SSHFP records. This can be controlled with
140 the VerifyHostKeyDNS client configuration setting. DNSSEC support
141 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
144 The GNU Compiler Collection and C++ standard library (libstdc++)
145 are no longer built by default on platforms where clang is the system
146 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
150 The PROCDESC kernel option is now part of the GENERIC kernel
151 configuration and is required for the rwhod(8) to work.
152 If you are using custom kernel configuration, you should include
156 The API and ABI related to the Capsicum framework was modified
157 in backward incompatible way. The userland libraries and programs
158 have to be recompiled to work with the new kernel. This includes the
159 following libraries and programs, but the whole buildworld is
160 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
161 kdump, procstat, rwho, rwhod, uniq.
164 AES-NI intrinsic support has been added to gcc. The AES-NI module
165 has been updated to use this support. A new gcc is required to build
166 the aesni module on both i386 and amd64.
169 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
170 Thus "device padlock_rng" and "device rdrand_rng" should be
171 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
174 WITH_ICONV has been split into two feature sets. WITH_ICONV now
175 enables just the iconv* functionality and is now on by default.
176 WITH_LIBICONV_COMPAT enables the libiconv api and link time
177 compatability. Set WITHOUT_ICONV to build the old way.
178 If you have been using WITH_ICONV before, you will very likely
179 need to turn on WITH_LIBICONV_COMPAT.
182 INVARIANTS option now enables DEBUG for code with OpenSolaris and
183 Illumos origin, including ZFS. If you have INVARIANTS in your
184 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
186 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
187 locks if WITNESS option was set. Because that generated a lot of
188 witness(9) reports and all of them were believed to be false
189 positives, this is no longer done. New option OPENSOLARIS_WITNESS
190 can be used to achieve the previous behavior.
193 Timer values in IPv6 data structures now use time_uptime instead
194 of time_second. Although this is not a user-visible functional
195 change, userland utilities which directly use them---ndp(8),
196 rtadvd(8), and rtsold(8) in the base system---need to be updated
200 find -delete can now delete the pathnames given as arguments,
201 instead of only files found below them or if the pathname did
202 not contain any slashes. Formerly, the following error message
205 find: -delete: <path>: relative path potentially not safe
207 Deleting the pathnames given as arguments can be prevented
208 without error messages using -mindepth 1 or by changing
209 directory and passing "." as argument to find. This works in the
210 old as well as the new version of find.
213 Behavior of devfs rules path matching has been changed.
214 Pattern is now always matched against fully qualified devfs
215 path and slash characters must be explicitly matched by
216 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
217 subdirectories must be reviewed.
220 The default ARM ABI has changed to the ARM EABI. The old ABI is
221 incompatible with the ARM EABI and all programs and modules will
222 need to be rebuilt to work with a new kernel.
224 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
226 NOTE: Support for the old ABI will be removed in the future and
227 users are advised to upgrade.
230 pkg_install has been disconnected from the build if you really need it
231 you should add WITH_PKGTOOLS in your src.conf(5).
234 Most of network statistics structures were changed to be able
235 keep 64-bits counters. Thus all tools, that work with networking
236 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
239 Fix targets that run multiple make's to use && rather than ;
240 so that subsequent steps depend on success of previous.
242 NOTE: if building 'universe' with -j* on stable/8 or stable/9
243 it would be better to start the build using bmake, to avoid
244 overloading the machine.
247 Fix a bug that allowed a tracing process (e.g. gdb) to write
248 to a memory-mapped file in the traced process's address space
249 even if neither the traced process nor the tracing process had
250 write access to that file.
253 CVS has been removed from the base system. An exact copy
254 of the code is available from the devel/cvs port.
257 Some people report the following error after the switch to bmake:
259 make: illegal option -- J
260 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
262 *** [buildworld] Error code 2
264 this likely due to an old instance of make in
265 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
266 which src/Makefile will use that blindly, if it exists, so if
267 you see the above error:
269 rm -rf `make -V MAKEPATH`
274 Use bmake by default.
275 Whereas before one could choose to build with bmake via
276 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
277 make. The goal is to remove these knobs for 10-RELEASE.
279 It is worth noting that bmake (like gmake) treats the command
280 line as the unit of failure, rather than statements within the
281 command line. Thus '(cd some/where && dosomething)' is safer
282 than 'cd some/where; dosomething'. The '()' allows consistent
283 behavior in parallel build.
286 Fix a bug that allows NFS clients to issue READDIR on files.
289 The WITHOUT_IDEA option has been removed because
290 the IDEA patent expired.
293 The sysctl which controls TRIM support under ZFS has been renamed
294 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
298 The mergemaster command now uses the default MAKEOBJDIRPREFIX
299 rather than creating it's own in the temporary directory in
300 order allow access to bootstrapped versions of tools such as
301 install and mtree. When upgrading from version of FreeBSD where
302 the install command does not support -l, you will need to
303 install a new mergemaster command if mergemaster -p is required.
304 This can be accomplished with the command (cd src/usr.sbin/mergemaster
308 Legacy ATA stack, disabled and replaced by new CAM-based one since
309 FreeBSD 9.0, completely removed from the sources. Kernel modules
310 atadisk and atapi*, user-level tools atacontrol and burncd are
311 removed. Kernel option `options ATA_CAM` is now permanently enabled
315 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
316 and socketpair(2). Software, in particular Kerberos, may
317 automatically detect and use these during building. The resulting
318 binaries will not work on older kernels.
321 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
322 information, see the respective 20130304 entry).
325 Recent commits to callout(9) changed the size of struct callout,
326 so the KBI is probably heavily disturbed. Also, some functions
327 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
328 by macros. Every kernel module using it won't load, so rebuild
331 The ctl device has been re-enabled in GENERIC for i386 and amd64,
332 but does not initialize by default (because of the new CTL_DISABLE
333 option) to save memory. To re-enable it, remove the CTL_DISABLE
334 option from the kernel config file or set kern.cam.ctl.disable=0
335 in /boot/loader.conf.
338 The ctl device has been disabled in GENERIC for i386 and amd64.
339 This was done due to the extra memory being allocated at system
340 initialisation time by the ctl driver which was only used if
341 a CAM target device was created. This makes a FreeBSD system
342 unusable on 128MB or less of RAM.
345 A new compression method (lz4) has been merged to -HEAD. Please
346 refer to zpool-features(7) for more information.
348 Please refer to the "ZFS notes" section of this file for information
349 on upgrading boot ZFS pools.
352 A BSD-licensed patch(1) variant has been added and is installed
353 as bsdpatch, being the GNU version the default patch.
354 To inverse the logic and use the BSD-licensed one as default,
355 while having the GNU version installed as gnupatch, rebuild
356 and install world with the WITH_BSD_PATCH knob set.
359 Due to the use of the new -l option to install(1) during build
360 and install, you must take care not to directly set the INSTALL
361 make variable in your /etc/make.conf, /etc/src.conf, or on the
362 command line. If you wish to use the -C flag for all installs
363 you may be able to add INSTALL+=-C to /etc/make.conf or
367 The install(1) option -M has changed meaning and now takes an
368 argument that is a file or path to append logs to. In the
369 unlikely event that -M was the last option on the command line
370 and the command line contained at least two files and a target
371 directory the first file will have logs appended to it. The -M
372 option served little practical purpose in the last decade so its
373 use is expected to be extremely rare.
376 After switching to Clang as the default compiler some users of ZFS
377 on i386 systems started to experience stack overflow kernel panics.
378 Please consider using 'options KSTACK_PAGES=4' in such configurations.
381 GEOM_LABEL now mangles label names read from file system metadata.
382 Mangling affect labels containing spaces, non-printable characters,
383 '%' or '"'. Device names in /etc/fstab and other places may need to
387 By default, only the 10 most recent kernel dumps will be saved. To
388 restore the previous behaviour (no limit on the number of kernel dumps
389 stored in the dump directory) add the following line to /etc/rc.conf:
394 With the addition of auditdistd(8), a new auditdistd user is now
395 required during installworld. "mergemaster -p" can be used to
396 add the user prior to installworld, as documented in the handbook.
399 The sin6_scope_id member variable in struct sockaddr_in6 is now
400 filled by the kernel before passing the structure to the userland via
401 sysctl or routing socket. This means the KAME-specific embedded scope
402 id in sin6_addr.s6_addr[2] is always cleared in userland application.
403 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
404 __FreeBSD_version is bumped to 1000025.
407 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
408 This means that the world and kernel will be compiled with clang
409 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
410 and /usr/bin/cpp. To disable this behavior and revert to building
411 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
412 of current may need to bootstrap WITHOUT_CLANG first if the clang
413 build fails (its compatibility window doesn't extend to the 9 stable
417 The IPFIREWALL_FORWARD kernel option has been removed. Its
418 functionality now turned on by default.
421 The ZERO_COPY_SOCKET kernel option has been removed and
422 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
423 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
424 mechanism which is not safe and may result in kernel crashes.
425 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
426 driver supports disposeable external page sized mbuf storage.
427 Proper replacements for both zero-copy mechanisms are under
428 consideration and will eventually lead to complete removal
429 of the two kernel options.
432 The IPv4 network stack has been converted to network byte
433 order. The following modules need to be recompiled together
434 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
435 pf(4), ipfw(4), ng_ipfw(4), stf(4).
438 Support for non-MPSAFE filesystems was removed from VFS. The
439 VFS_VERSION was bumped, all filesystem modules shall be
443 All the non-MPSAFE filesystems have been disconnected from
444 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
445 portalfs, smbfs, xfs.
448 The interface cloning API and ABI has changed. The following
449 modules need to be recompiled together with kernel:
450 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
451 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
452 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
455 The sdhci driver was split in two parts: sdhci (generic SD Host
456 Controller logic) and sdhci_pci (actual hardware driver).
457 No kernel config modifications are required, but if you
458 load sdhc as a module you must switch to sdhci_pci instead.
461 Import the FUSE kernel and userland support into base system.
464 The GNU sort(1) program has been removed since the BSD-licensed
465 sort(1) has been the default for quite some time and no serious
466 problems have been reported. The corresponding WITH_GNU_SORT
470 The pfil(9) API/ABI for AF_INET family has been changed. Packet
471 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
475 The net80211(4) ABI has been changed to allow for improved driver
476 PS-POLL and power-save support. All wireless drivers need to be
477 recompiled to work with the new kernel.
480 The random(4) support for the VIA hardware random number
481 generator (`PADLOCK') is no longer enabled unconditionally.
482 Add the padlock_rng device in the custom kernel config if
483 needed. The GENERIC kernels on i386 and amd64 do include the
484 device, so the change only affects the custom kernel
488 The pf(4) packet filter ABI has been changed. pfctl(8) and
489 snmp_pf module need to be recompiled to work with new kernel.
492 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
493 to -HEAD. Pools that have empty_bpobj in active state can not be
494 imported read-write with ZFS implementations that do not support
495 this feature. For more information read the zpool-features(5)
499 The sparc64 ZFS loader has been changed to no longer try to auto-
500 detect ZFS providers based on diskN aliases but now requires these
501 to be explicitly listed in the OFW boot-device environment variable.
504 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
505 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
506 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
509 The following sysctls and tunables have been renamed for consistency
510 with other variables:
511 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
512 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
515 The sort utility has been replaced with BSD sort. For now, GNU sort
516 is also available as "gnusort" or the default can be set back to
517 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
518 installed as "bsdsort".
521 A new version of ZFS (pool version 5000) has been merged to -HEAD.
522 Starting with this version the old system of ZFS pool versioning
523 is superseded by "feature flags". This concept enables forward
524 compatibility against certain future changes in functionality of ZFS
525 pools. The first read-only compatible "feature flag" for ZFS pools
526 is named "com.delphix:async_destroy". For more information
527 read the new zpool-features(5) manual page.
528 Please refer to the "ZFS notes" section of this file for information
529 on upgrading boot ZFS pools.
532 The malloc(3) implementation embedded in libc now uses sources imported
533 as contrib/jemalloc. The most disruptive API change is to
534 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
535 delete it prior to installworld, and optionally re-create it using the
536 new format after rebooting. See malloc.conf(5) for details
537 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
541 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
542 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
543 now spelled mips. This is to aid compatibility with third-party
544 software that expects this naming scheme in uname(3). Little-endian
545 settings are unchanged. If you are updating a big-endian mips64 machine
546 from before this change, you may need to set MACHINE_ARCH=mips64 in
547 your environment before the new build system will recognize your machine.
550 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
554 Now unix domain sockets behave "as expected" on nullfs(5). Previously
555 nullfs(5) did not pass through all behaviours to the underlying layer,
556 as a result if we bound to a socket on the lower layer we could connect
557 only to the lower path; if we bound to the upper layer we could connect
558 only to the upper path. The new behavior is one can connect to both the
559 lower and the upper paths regardless what layer path one binds to.
562 The getifaddrs upgrade path broken with 20111215 has been restored.
563 If you have upgraded in between 20111215 and 20120209 you need to
564 recompile libc again with your kernel. You still need to recompile
565 world to be able to configure CARP but this restriction already
569 The set_rcvar() function has been removed from /etc/rc.subr. All
570 base and ports rc.d scripts have been updated, so if you have a
571 port installed with a script in /usr/local/etc/rc.d you can either
572 hand-edit the rcvar= line, or reinstall the port.
574 An easy way to handle the mass-update of /etc/rc.d:
575 rm /etc/rc.d/* && mergemaster -i
578 panic(9) now stops other CPUs in the SMP systems, disables interrupts
579 on the current CPU and prevents other threads from running.
580 This behavior can be reverted using the kern.stop_scheduler_on_panic
582 The new behavior can be incompatible with kern.sync_on_panic.
585 The carp(4) facility has been changed significantly. Configuration
586 of the CARP protocol via ifconfig(8) has changed, as well as format
587 of CARP events submitted to devd(8) has changed. See manual pages
588 for more information. The arpbalance feature of carp(4) is currently
589 not supported anymore.
591 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
592 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
593 need to be recompiled.
596 The acpi_wmi(4) status device /dev/wmistat has been renamed to
600 The option VFS_ALLOW_NONMPSAFE option has been added in order to
601 explicitely support non-MPSAFE filesystems.
602 It is on by default for all supported platform at this present
606 The broken amd(4) driver has been replaced with esp(4) in the amd64,
607 i386 and pc98 GENERIC kernel configuration files.
610 sysinstall has been removed
613 The stable/9 branch created in subversion. This corresponds to the
614 RELENG_9 branch in CVS.
617 This commit modifies vfs_register() so that it uses a hash
618 calculation to set vfc_typenum, which is enabled by default.
619 The first time a system is booted after this change, the
620 vfc_typenum values will change for all file systems. The
621 main effect of this is a change to the NFS server file handles
622 for file systems that use vfc_typenum in their fsid, such as ZFS.
623 It will, however, prevent vfc_typenum from changing when file
624 systems are loaded in a different order for subsequent reboots.
625 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
626 until you are ready to remount all NFS clients after a reboot.
629 Bump the shared library version numbers for libraries that
630 do not use symbol versioning, have changed the ABI compared
631 to stable/8 and which shared library version was not bumped.
632 Done as part of 9.0-RELEASE cycle.
635 During the merge of Capsicum features, the fget(9) KPI was modified.
636 This may require the rebuilding of out-of-tree device drivers --
637 issues have been reported specifically with the nVidia device driver.
638 __FreeBSD_version is bumped to 900041.
640 Also, there is a period between 20110811 and 20110814 where the
641 special devices /dev/{stdin,stdout,stderr} did not work correctly.
642 Building world from a kernel during that window may not work.
645 The packet filter (pf) code has been updated to OpenBSD 4.5.
646 You need to update userland tools to be in sync with kernel.
647 This update breaks backward compatibility with earlier pfsync(4)
648 versions. Care must be taken when updating redundant firewall setups.
651 The following sysctls and tunables are retired on x86 platforms:
653 machdep.hlt_logical_cpus
654 The following sysctl is retired:
655 machdep.hyperthreading_allowed
656 The sysctls were supposed to provide a way to dynamically offline and
657 online selected CPUs on x86 platforms, but the implementation has not
658 been reliable especially with SCHED_ULE scheduler.
659 machdep.hyperthreading_allowed tunable is still available to ignore
660 hyperthreading CPUs at OS level.
661 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
662 where X is an APIC ID of a CPU. Be advised, though, that disabling
663 CPUs in non-uniform fashion will result in non-uniform topology and
664 may lead to sub-optimal system performance with SCHED_ULE, which is
668 cpumask_t type is retired and cpuset_t is used in order to describe
672 Changes to ifconfig(8) for dynamic address family detection mandate
673 that you are running a kernel of 20110525 or later. Make sure to
674 follow the update procedure to boot a new kernel before installing
678 Support for sun4v architecture is officially dropped
681 Several KPI breaking changes have been committed to the mii(4) layer,
682 the PHY drivers and consequently some Ethernet drivers using mii(4).
683 This means that miibus.ko and the modules of the affected Ethernet
684 drivers need to be recompiled.
686 Note to kernel developers: Given that the OUI bit reversion problem
687 was fixed as part of these changes all mii(4) commits related to OUIs,
688 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
689 handling, no longer can be merged verbatim to stable/8 and previous
693 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
694 into their kernel configurations along with 'device pci'.
697 The default NFS client is now the new NFS client, so fstype "newnfs"
698 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
699 Although mounts via fstype "nfs" will usually work without userland
700 changes, it is recommended that the mount(8) and mount_nfs(8)
701 commands be rebuilt from sources and that a link to mount_nfs called
702 mount_oldnfs be created. The new client is compiled into the
703 kernel with "options NFSCL" and this is needed for diskless root
704 file systems. The GENERIC kernel configs have been changed to use
705 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
706 To use the regular/old client, you can "mount -t oldnfs ...". For
707 a diskless root file system, you must also include a line like:
709 vfs.root.mountfrom="oldnfs:"
711 in the boot/loader.conf on the root fs on the NFS server to make
712 a diskless root fs use the old client.
715 The GENERIC kernels for all architectures now default to the new
716 CAM-based ATA stack. It means that all legacy ATA drivers were
717 removed and replaced by respective CAM drivers. If you are using
718 ATA device names in /etc/fstab or other places, make sure to update
719 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
720 where 'Y's are the sequential numbers starting from zero for each type
721 in order of detection, unless configured otherwise with tunables,
722 see cam(4)). There will be symbolic links created in /dev/ to map
723 old adX devices to the respective adaY. They should provide basic
724 compatibility for file systems mounting in most cases, but they do
725 not support old user-level APIs and do not have respective providers
726 in GEOM. Consider using updated management tools with new device names.
728 It is possible to load devices ahci, ata, siis and mvs as modules,
729 but option ATA_CAM should remain in kernel configuration to make ata
730 module work as CAM driver supporting legacy ATA controllers. Device ata
731 still can be used in modular fashion (atacore + ...). Modules atadisk
732 and atapi* are not used and won't affect operation in ATA_CAM mode.
733 Note that to use CAM-based ATA kernel should include CAM devices
734 scbus, pass, da (or explicitly ada), cd and optionally others. All of
735 them are parts of the cam module.
737 ataraid(4) functionality is now supported by the RAID GEOM class.
738 To use it you can load geom_raid kernel module and use graid(8) tool
739 for management. Instead of /dev/arX device names, use /dev/raid/rX.
741 No kernel config options or code have been removed, so if a problem
742 arises, please report it and optionally revert to the old ATA stack.
743 In order to do it you can remove from the kernel config:
748 , and instead add back:
749 device atadisk # ATA disk drives
750 device ataraid # ATA RAID drives
751 device atapicd # ATAPI CDROM drives
752 device atapifd # ATAPI floppy drives
753 device atapist # ATAPI tape drives
756 The default NFS server has been changed to the new server, which
757 was referred to as the experimental server. If you need to switch
758 back to the old NFS server, you must now put the "-o" option on
759 both the mountd and nfsd commands. This can be done using the
760 mountd_flags and nfs_server_flags rc.conf variables until an
761 update to the rc scripts is committed, which is coming soon.
764 The GNU Objective-C runtime library (libobjc), and other Objective-C
765 related components have been removed from the base system. If you
766 require an Objective-C library, please use one of the available ports.
769 ath(4) has been split into bus- and device- modules. if_ath contains
770 the HAL, the TX rate control and the network device code. if_ath_pci
771 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
772 contains the AHB glue. Users need to load both if_ath_pci and if_ath
773 in order to use ath on everything else.
775 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
776 need to load if_ath and if_ath_pci for ath(4) operation.
779 As part of the replacement of sysinstall, the process of building
780 release media has changed significantly. For details, please re-read
781 release(7), which has been updated to reflect the new build process.
784 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
785 is the last available version under GPLv2. It brings a number of new
786 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
787 4.1 and SSE 4.2), better support for powerpc64, a number of new
788 directives, and lots of other small improvements. See the ChangeLog
789 file in contrib/binutils for the full details.
792 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
793 compliant, and will now use half of hash for authentication.
794 This will break interoperability with all stacks (including all
795 actual FreeBSD versions) who implement
796 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
798 The only workaround with such peers is to use another HMAC
799 algorithm for IPsec ("phase 2") authentication.
802 Remove the uio_yield prototype and symbol. This function has
803 been misnamed since it was introduced and should not be
804 globally exposed with this name. The equivalent functionality
805 is now available using kern_yield(curthread->td_user_pri).
806 The function remains undocumented.
809 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
810 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
811 for scalar sysctls is defined but disabled. Code that needs
812 UQUAD to pass the type checking that must compile on older
813 systems where the define is not present can check against
814 __FreeBSD_version >= 900030.
816 The system dialog(1) has been replaced with a new version previously
817 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
818 with the previous version, but the libdialog associated with it has
819 a largely incompatible API. As such, the original version of libdialog
820 will be kept temporarily as libodialog, until its base system consumers
821 are replaced or updated. Bump __FreeBSD_version to 900030.
824 If you are trying to run make universe on a -stable system, and you get
825 the following warning:
826 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
827 unknown. config(8) likely too old."
828 or something similar to it, then you must upgrade your -stable system
829 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
830 stable/8) or build the config from the latest stable/8 branch and
831 install it on your system.
833 Prior to this date, building a current universe on 8-stable system from
834 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
835 error in the first kernel build phase. A new config on those old
836 systems will fix that problem for older versions of -current.
839 The TCP stack has been modified to allow Khelp modules to interact with
840 it via helper hook points and store per-connection data in the TCP
841 control block. Bump __FreeBSD_version to 900029. User space tools that
842 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
846 Generic IEEE 802.3 annex 31B full duplex flow control support has been
847 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
848 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
849 to take advantage of it instead of using custom implementations. This
850 means that these drivers now no longer unconditionally advertise
851 support for flow control but only do so if flow control is a selected
852 media option. This was implemented in the generic support that way in
853 order to allow flow control to be switched on and off via ifconfig(8)
854 with the PHY specific default to typically off in order to protect
855 from unwanted effects. Consequently, if you used flow control with
856 one of the above mentioned drivers you now need to explicitly enable
858 ifconfig bge0 media auto mediaopt flowcontrol
860 Along with the above mentioned changes generic support for setting
861 1000baseT master mode also has been added and brgphy(4), ciphy(4),
862 e1000phy(4) as well as ip1000phy(4) have been converted to take
863 advantage of it. This means that these drivers now no longer take the
864 link0 parameter for selecting master mode but the master media option
865 has to be used instead, for example like in the following:
866 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
868 Selection of master mode now is also available with all other PHY
869 drivers supporting 1000baseT.
872 The TCP stack has received a significant update to add support for
873 modularised congestion control and generally improve the clarity of
874 congestion control decisions. Bump __FreeBSD_version to 900025. User
875 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
876 sockstat) need to be recompiled.
879 The man(1) utility has been replaced by a new version that no longer
880 uses /etc/manpath.config. Please consult man.conf(5) for how to
881 migrate local entries to the new format.
884 The copyright strings printed by login(1) and sshd(8) at the time of a
885 new connection have been removed to follow other operating systems and
889 A workaround for a fixed ld bug has been removed in kernel code,
890 so make sure that your system ld is built from sources after
891 revision 210245 from 2010-07-19 (r211583 if building head kernel
892 on stable/8, r211584 for stable/7; both from 2010-08-21).
893 A symptom of incorrect ld version is different addresses for
894 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
897 The $ipv6_prefer variable in rc.conf(5) has been split into
898 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
900 The $ip6addrctl_policy is a variable to choose a pre-defined
901 address selection policy set by ip6addrctl(8). A value
902 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
905 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
906 flag (see an entry of 20090926) is set on an interface with no
907 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
908 security reason. If you want IPv6 link-local address on all
909 interfaces by default, set this to "YES".
911 The old ipv6_prefer="YES" is equivalent to
912 ipv6_activate_all_interfaces="YES" and
913 ip6addrctl_policy="ipv6_prefer".
916 DTrace has grown support for userland tracing. Due to this, DTrace is
917 now i386 and amd64 only.
918 dtruss(1) is now installed by default on those systems and a new
919 kernel module is needed for userland tracing: fasttrap.
920 No changes to your kernel config file are necessary to enable
921 userland tracing, but you might consider adding 'STRIP=' and
922 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
923 to have informative userland stack traces in DTrace (ustack).
926 The acpi_aiboost(4) driver has been removed in favor of the new
927 aibs(4) driver. You should update your kernel configuration file.
930 BSD grep has been imported to the base system and it is built by
931 default. It is completely BSD licensed, highly GNU-compatible, uses
932 less memory than its GNU counterpart and has a small codebase.
933 However, it is slower than its GNU counterpart, which is mostly
934 noticeable for larger searches, for smaller ones it is measurable
935 but not significant. The reason is complex, the most important factor
936 is that we lack a modern and efficient regex library and GNU
937 overcomes this by optimizing the searches internally. Future work
938 on improving the regex performance is planned, for the meantime,
939 users that need better performance, can build GNU grep instead by
940 setting the WITH_GNU_GREP knob.
943 Due to the import of powerpc64 support, all existing powerpc kernel
944 configuration files must be updated with a machine directive like this:
945 machine powerpc powerpc
947 In addition, an updated config(8) is required to build powerpc kernels
951 A new version of ZFS (version 15) has been merged to -HEAD.
952 This version uses a python library for the following subcommands:
953 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
954 For full functionality of these commands the following port must
955 be installed: sysutils/py-zfs
958 'vm_page's are now hashed by physical address to an array of mutexes.
959 Currently this is only used to serialize access to hold_count. Over
960 time the page queue mutex will be peeled away. This changes the size
961 of pmap on every architecture. And requires all callers of vm_page_hold
962 and vm_page_unhold to be updated.
965 WITH_CTF can now be specified in src.conf (not recommended, there
966 are some problems with static executables), make.conf (would also
967 affect ports which do not use GNU make and do not override the
968 compile targets) or in the kernel config (via "makeoptions
970 When WITH_CTF was specified there before this was silently ignored,
971 so make sure that WITH_CTF is not used in places which could lead
972 to unwanted behavior.
975 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
976 to allow 32-bit compatibility on non-x86 platforms. All kernel
977 configurations on amd64 and ia64 platforms using these options must
978 be modified accordingly.
981 The utmp user accounting database has been replaced with utmpx,
982 the user accounting interface standardized by POSIX.
983 Unfortunately the semantics of utmp and utmpx don't match,
984 making it practically impossible to support both interfaces.
985 The user accounting database is used by tools like finger(1),
986 last(1), talk(1), w(1) and ac(8).
988 All applications in the base system use utmpx. This means only
989 local binaries (e.g. from the ports tree) may still use these
990 utmp database files. These applications must be rebuilt to make
993 After the system has been upgraded, it is safe to remove the old
994 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
995 assuming their contents is of no importance anymore. Old wtmp
996 databases can only be used by last(1) and ac(8) after they have
997 been converted to the new format using wtmpcvt(1).
1000 Introduce the kernel thread "deadlock resolver" (which can be enabled
1001 via the DEADLKRES option, see NOTES for more details) and the
1002 sleepq_type() function for sleepqueues.
1005 The rc.firewall and rc.firewall6 were unified, and
1006 rc.firewall6 and rc.d/ip6fw were removed.
1007 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1008 variables are obsoleted. Instead, the following new rc
1009 variables are added to rc.d/ipfw:
1011 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1012 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1013 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1015 The meanings correspond to the relevant IPv4 variables.
1021 The default terminal emulation for syscons(4) has been changed
1022 from cons25 to xterm on all platforms except pc98. This means
1023 that the /etc/ttys file needs to be updated to ensure correct
1024 operation of applications on the console.
1026 The terminal emulation style can be toggled per window by using
1027 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1028 options can be used to change the compile-time default back to
1031 To prevent graphical artifacts, make sure the TERM environment
1032 variable is set to match the terminal emulation that is being
1033 performed by syscons(4).
1036 The layout of the structure ieee80211req_scan_result has changed.
1037 Applications that require wireless scan results (e.g. ifconfig(8))
1038 from net80211 need to be recompiled.
1040 Applications such as wpa_supplicant(8) may require a full world
1041 build without using NO_CLEAN in order to get synchronized with the
1045 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1046 There's one kernel module for each firmware. Adding "device iwnfw"
1047 to the kernel configuration file means including all three firmware
1048 images inside the kernel. If you want to include just the one for
1049 your wireless card, use the devices iwn4965fw, iwn5000fw or
1053 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1054 into rc.d/netif. The changes are the following:
1056 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1057 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1058 Note that both variables need the "inet6" keyword at the head.
1060 Do not set $ipv6_network_interfaces manually if you do not
1061 understand what you are doing. It is not needed in most cases.
1063 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1066 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1067 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1069 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1070 all configured interfaces have "inet6 accept_rtadv" in the
1071 $ifconfig_IF_ipv6. These are for backward compatibility.
1073 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1074 functionality of interfaces with no corresponding
1075 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1076 and the default address selection policy of ip6addrctl(8)
1077 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1078 Note that if you want to configure IPv6 functionality on the
1079 disabled interfaces after boot, first you need to clear the flag by
1080 using ifconfig(8) like:
1082 ifconfig em0 inet6 -ifdisabled
1084 If YES, the default address selection policy is set as
1087 The default value of $ipv6_prefer is NO.
1089 4. If your system need to receive Router Advertisement messages,
1090 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1091 scripts automatically invoke rtsol(8) when the interface becomes
1092 UP. The Router Advertisement messages are used for SLAAC
1093 (State-Less Address AutoConfiguration).
1096 802.11s D3.03 support was committed. This is incompatible with the
1097 previous code, which was based on D3.0.
1100 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1101 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1102 control whether accepting Router Advertisement messages or not.
1103 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1104 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1105 The ifconfig(8) utility now supports these flags.
1108 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1109 mount(8) and -a option for df(1) to see them.
1112 The old tunable hw.bus.devctl_disable has been superseded by
1113 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1114 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1118 Remove the option STOP_NMI. The default action is now to use NMI only
1119 for KDB via the newly introduced function stop_cpus_hard() and
1120 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1123 The stable/8 branch created in subversion. This corresponds to the
1124 RELENG_8 branch in CVS.
1127 Bump the shared library version numbers for all libraries that do not
1128 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1129 __FreeBSD_version to 800105.
1132 Due to changes in the implementation of virtual network stack support,
1133 all network-related kernel modules must be recompiled. As this change
1134 breaks the ABI, bump __FreeBSD_version to 800104.
1137 The TOE interface to the TCP syncache has been modified to remove
1138 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1139 The cxgb driver is the only TOE consumer affected by this change, and
1140 needs to be recompiled along with the kernel. As this change breaks
1141 the ABI, bump __FreeBSD_version to 800103.
1144 Padding has been added to struct tcpcb, sackhint and tcpstat in
1145 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1146 maintaining the ABI. However, this change breaks the ABI, so bump
1147 __FreeBSD_version to 800102. User space tools that rely on the size of
1148 any of these structs (e.g. sockstat) need to be recompiled.
1151 The NFS_LEGACYRPC option has been removed along with the old kernel
1152 RPC implementation that this option selected. Kernel configurations
1153 may need to be adjusted.
1156 The network interface device nodes at /dev/net/<interface> have been
1157 removed. All ioctl operations can be performed the normal way using
1158 routing sockets. The kqueue functionality can generally be replaced
1159 with routing sockets.
1162 The documentation from the FreeBSD Documentation Project (Handbook,
1163 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1164 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1167 The ABI of various structures related to the SYSV IPC API have been
1168 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1169 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1173 Layout of struct vnet has changed as routing related variables were
1174 moved to their own Vimage module. Modules need to be recompiled. Bump
1175 __FreeBSD_version to 800099.
1178 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1179 respectively. As long as no more than 16 groups per process are used,
1180 no changes should be visible. When more than 16 groups are used, old
1181 binaries may fail if they call getgroups() or getgrouplist() with
1182 statically sized storage. Recompiling will work around this, but
1183 applications should be modified to use dynamically allocated storage
1184 for group arrays as POSIX.1-2008 does not cap an implementation's
1185 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1187 NFS and portalfs mounts may also be affected as the list of groups is
1188 truncated to 16. Users of NFS who use more than 16 groups, should
1189 take care that negative group permissions are not used on the exported
1190 file systems as they will not be reliable unless a GSSAPI based
1191 authentication method is used.
1194 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1195 option compiles in the support for adaptive spinning for lockmgrs
1196 which want to enable it. The lockinit() function now accepts the flag
1197 LK_ADAPTIVE in order to make the lock object subject to adaptive
1198 spinning when both held in write and read mode.
1201 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1202 changed. User applications that use this ioctl need to be rebuilt.
1205 The layout of struct thread has changed. Kernel and modules need to
1209 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1210 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1213 window(1) has been removed from the base system. It can now be
1214 installed from ports. The port is called misc/window.
1217 The way we are storing and accessing `routing table' entries has
1218 changed. Programs reading the FIB, like netstat, need to be
1222 A new netisr implementation has been added for FreeBSD 8. Network
1223 file system modules, such as igmp, ipdivert, and others, should be
1225 Bump __FreeBSD_version to 800096.
1228 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1232 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1233 Bump __FreeBSD_version to 800094.
1236 Add mnt_xflag field to 'struct mount'. File system modules need to be
1238 Bump __FreeBSD_version to 800093.
1241 The compiling option ADAPTIVE_SX has been retired while it has been
1242 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1243 The KPI for sx_init_flags() changes as accepting flags:
1244 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1245 been introduced in order to handle the reversed logic.
1246 Bump __FreeBSD_version to 800092.
1249 Add support for hierarchical jails. Remove global securelevel.
1250 Bump __FreeBSD_version to 800091.
1253 The layout of struct vnet_net has changed, therefore modules
1255 Bump __FreeBSD_version to 800090.
1258 The newly imported zic(8) produces a new format in the output. Please
1259 run tzsetup(8) to install the newly created data to /etc/localtime.
1262 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1263 hw.usb.* and is now consistent again with previous releases.
1266 802.11 monitor mode support was revised and driver api's were changed.
1267 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1268 of DLT_IEEE802_11. No user-visible data structures were changed but
1269 applications that use DLT_IEEE802_11 may require changes.
1270 Bump __FreeBSD_version to 800088.
1273 The layout of the following structs has changed: sysctl_oid,
1274 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1275 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1276 panics may be experienced. World rebuild is required for
1277 correctly checking networking state from userland.
1278 Bump __FreeBSD_version to 800085.
1281 MLDv2 and Source-Specific Multicast (SSM) have been merged
1282 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1283 The implementation of SSM within FreeBSD's IPv6 stack closely
1284 follows the IPv4 implementation.
1286 For kernel developers:
1288 * The most important changes are that the ip6_output() and
1289 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1290 and this lock has been downgraded to a non-recursive mutex.
1292 * As with the changes to the IPv4 stack to support SSM, filtering
1293 of inbound multicast traffic must now be performed by transport
1294 protocols within the IPv6 stack. This does not apply to TCP and
1295 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1297 * The KPIs used by IPv6 multicast are similar to those used by
1298 the IPv4 stack, with the following differences:
1299 * im6o_mc_filter() is analogous to imo_multicast_filter().
1300 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1301 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1302 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1303 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1304 for MLDv1 have an additional 'timer' argument which is used to
1305 jitter the initial membership report for the solicited-node
1306 multicast membership on-link.
1307 * This is not strictly needed for MLDv2, which already jitters
1308 its report transmissions. However, the 'timer' argument is
1309 preserved in case MLDv1 is active on the interface.
1311 * The KAME linked-list based IPv6 membership implementation has
1312 been refactored to use a vector similar to that used by the IPv4
1314 Code which maintains a list of its own multicast memberships
1315 internally, e.g. carp, has been updated to reflect the new
1318 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1319 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1320 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1321 implementation constraint which needs to be addressed in HEAD.
1323 For application developers:
1325 * The changes are broadly similar to those made for the IPv4
1328 * The use of IPv4 and IPv6 multicast socket options on the same
1329 socket, using mapped addresses, HAS NOT been tested or supported.
1331 * There are a number of issues with the implementation of various
1332 IPv6 multicast APIs which need to be resolved in the API surface
1333 before the implementation is fully compatible with KAME userland
1334 use, and these are mostly to do with interface index treatment.
1336 * The literature available discusses the use of either the delta / ASM
1337 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1338 using setsourcefilter(3)/getsourcefilter(3). For more information
1339 please refer to RFC 3768, 'Socket Interface Extensions for
1340 Multicast Source Filters'.
1342 * Applications which use the published RFC 3678 APIs should be fine.
1344 For systems administrators:
1346 * The mtest(8) utility has been refactored to support IPv6, in
1347 addition to IPv4. Interface addresses are no longer accepted
1348 as arguments, their names must be used instead. The utility
1349 will map the interface name to its first IPv4 address as
1350 returned by getifaddrs(3).
1352 * The ifmcstat(8) utility has also been updated to print the MLDv2
1353 endpoint state and source filter lists via sysctl(3).
1355 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1356 loopback of IPv6 multicast datagrams by default; it defaults to 1
1357 to preserve the existing behaviour. Disabling multicast loopback is
1358 recommended for optimal system performance.
1360 * The IPv6 MROUTING code has been changed to examine this sysctl
1361 instead of attempting to perform a group lookup before looping
1362 back forwarded datagrams.
1364 Bump __FreeBSD_version to 800084.
1367 Implement low-level Bluetooth HCI API.
1368 Bump __FreeBSD_version to 800083.
1371 The layout of struct malloc_type, used by modules to register new
1372 memory allocation types, has changed. Most modules will need to
1373 be rebuilt or panics may be experienced.
1374 Bump __FreeBSD_version to 800081.
1377 Anticipate overflowing inp_flags - add inp_flags2.
1378 This changes most offsets in inpcb, so checking v4 connection
1379 state will require a world rebuild.
1380 Bump __FreeBSD_version to 800080.
1383 Add an llentry to struct route and struct route_in6. Modules
1384 embedding a struct route will need to be recompiled.
1385 Bump __FreeBSD_version to 800079.
1388 The size of rt_metrics_lite and by extension rtentry has changed.
1389 Networking administration apps will need to be recompiled.
1390 The route command now supports show as an alias for get, weighting
1391 of routes, sticky and nostick flags to alter the behavior of stateful
1393 Bump __FreeBSD_version to 800078.
1396 Do not use Giant for kbdmux(4) locking. This is wrong and
1397 apparently causing more problems than it solves. This will
1398 re-open the issue where interrupt handlers may race with
1399 kbdmux(4) in polling mode. Typical symptoms include (but
1400 not limited to) duplicated and/or missing characters when
1401 low level console functions (such as gets) are used while
1402 interrupts are enabled (for example geli password prompt,
1403 mountroot prompt etc.). Disabling kbdmux(4) may help.
1406 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1407 kernel modules referencing any of the above need to be recompiled.
1408 Bump __FreeBSD_version to 800075.
1411 GEOM_PART has become the default partition slicer for storage devices,
1412 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1413 introduces some changes:
1415 MSDOS/EBR: the devices created from MSDOS extended partition entries
1416 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1417 to devices with offset-based names. fstabs may need to be modified.
1419 BSD: the "geometry does not match label" warning is harmless in most
1420 cases but it points to problems in file system misalignment with
1421 disk geometry. The "c" partition is now implicit, covers the whole
1422 top-level drive and cannot be (mis)used by users.
1424 General: Kernel dumps are now not allowed to be written to devices
1425 whose partition types indicate they are meant to be used for file
1426 systems (or, in case of MSDOS partitions, as something else than
1429 Most of these changes date approximately from 200812.
1432 The uscanner(4) driver has been removed from the kernel. This follows
1433 Linux removing theirs in 2.6 and making libusb the default interface
1434 (supported by sane).
1437 The multicast forwarding code has been cleaned up. netstat(1)
1438 only relies on KVM now for printing bandwidth upcall meters.
1439 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1440 ip6_mroute_mod respectively. The config(5) options for statically
1441 compiling this code remain the same, i.e. 'options MROUTING'.
1444 Support for the IFF_NEEDSGIANT network interface flag has been
1445 removed, which means that non-MPSAFE network device drivers are no
1446 longer supported. In particular, if_ar, if_sr, and network device
1447 drivers from the old (legacy) USB stack can no longer be built or
1451 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1452 a bunch of new language catalog files have also been added.
1453 This means that some common libc messages are now localized and
1454 they depend on the LC_MESSAGES environmental variable.
1457 The k8temp(4) driver has been renamed to amdtemp(4) since
1458 support for Family 10 and Family 11 CPU families was added.
1461 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1462 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1464 For kernel developers, the most important changes are that the
1465 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1466 and this lock has been downgraded to a non-recursive mutex.
1468 Transport protocols (UDP, Raw IP) are now responsible for filtering
1469 inbound multicast traffic according to group membership and source
1470 filters. The imo_multicast_filter() KPI exists for this purpose.
1471 Transports which do not use multicast (SCTP, TCP) already reject
1472 multicast by default. Forwarding and receive performance may improve
1473 as a mutex acquisition is no longer needed in the ip_input()
1474 low-level input path. in_addmulti() and in_delmulti() are shimmed
1475 to new KPIs which exist to support SSM in-kernel.
1477 For application developers, it is recommended that loopback of
1478 multicast datagrams be disabled for best performance, as this
1479 will still cause the lock to be taken for each looped-back
1480 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1481 be tuned to 0 to disable loopback by default; it defaults to 1
1482 to preserve the existing behaviour.
1484 For systems administrators, to obtain best performance with
1485 multicast reception and multiple groups, it is always recommended
1486 that a card with a suitably precise hash filter is used. Hash
1487 collisions will still result in the lock being taken within the
1488 transport protocol input path to check group membership.
1490 If deploying FreeBSD in an environment with IGMP snooping switches,
1491 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1492 enabled; this forces 224.0.0.0/24 group membership to be announced
1495 The size of 'struct igmpstat' has changed; netstat needs to be
1496 recompiled to reflect this.
1497 Bump __FreeBSD_version to 800070.
1500 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1501 updated to use it. This requires a buildworld/installworld in order to
1502 update the library and dependencies (usbconfig, etc). Its advisable to
1503 rebuild all ports which uses libusb. More specific directions are given
1504 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1505 libusb are no longer required and can be removed.
1508 A workaround is committed to allow the creation of System V shared
1509 memory segment of size > 2 GB on the 64-bit architectures.
1510 Due to a limitation of the existing ABI, the shm_segsz member
1511 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1512 wrong for large segments. Note that limits must be explicitly
1513 raised to allow such segments to be created.
1516 The layout of struct ifnet has changed, requiring a rebuild of all
1517 network device driver modules.
1520 The /dev handling for the new USB stack has changed, a
1521 buildworld/installworld is required for libusb20.
1524 The new USB2 stack has now been permanently moved in and all kernel and
1525 module names reverted to their previous values (eg, usb, ehci, ohci,
1526 ums, ...). The old usb stack can be compiled in by prefixing the name
1527 with the letter 'o', the old usb modules have been removed.
1528 Updating entry 20090216 for xorg and 20090215 for libmap may still
1532 The rc.conf(5) option if_up_delay has been renamed to
1533 defaultroute_delay to better reflect its purpose. If you have
1534 customized this setting in /etc/rc.conf you need to update it to
1538 xorg 7.4 wants to configure its input devices via hald which does not
1539 yet work with USB2. If the keyboard/mouse does not work in xorg then
1541 Option "AllowEmptyInput" "off"
1542 to your ServerLayout section. This will cause X to use the configured
1543 kbd and mouse sections from your xorg.conf.
1546 The GENERIC kernels for all architectures now default to the new USB2
1547 stack. No kernel config options or code have been removed so if a
1548 problem arises please report it and optionally revert to the old USB
1549 stack. If you are loading USB kernel modules or have a custom kernel
1550 that includes GENERIC then ensure that usb names are also changed over,
1551 eg uftdi -> usb2_serial_ftdi.
1553 Older programs linked against the ports libusb 0.1 need to be
1554 redirected to the new stack's libusb20. /etc/libmap.conf can
1556 # Map old usb library to new one for usb2 stack
1557 libusb-0.1.so.8 libusb20.so.1
1560 All USB ethernet devices now attach as interfaces under the name ueN
1561 (eg. ue0). This is to provide a predictable name as vendors often
1562 change usb chipsets in a product without notice.
1565 The ichsmb(4) driver has been changed to require SMBus slave
1566 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1567 All of the other SMBus controller drivers require left-justified
1568 slave addresses, so this change makes all the drivers provide the
1572 INET6 statistics (struct ip6stat) was updated.
1573 netstat(1) needs to be recompiled.
1576 NTFS has been removed from GENERIC kernel on amd64 to match
1577 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1578 will load ntfs.ko module automatically when NTFS support is
1579 actually needed, unless ntfs.ko is not installed or security
1580 level prohibits loading kernel modules. If either is the case,
1581 "options NTFS" has to be added into kernel config.
1584 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1585 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1586 800061. User space tools that rely on the size of struct tcpcb in
1587 tcp_var.h (e.g. sockstat) need to be recompiled.
1590 ng_tty(4) module updated to match the new TTY subsystem.
1591 Due to API change, user-level applications must be updated.
1592 New API support added to mpd5 CVS and expected to be present
1593 in next mpd5.3 release.
1596 With __FreeBSD_version 800060 the makefs tool is part of
1597 the base system (it was a port).
1600 The afdata and ifnet locks have been changed from mutexes to
1601 rwlocks, network modules will need to be re-compiled.
1604 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1605 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1606 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1607 architecture and 40 bytes on 64-bit architecture. The userland
1608 applications "arp" and "ndp" have been updated accordingly.
1609 The output from "netstat -r" shows only routing entries and
1610 none of the L2 information.
1613 __FreeBSD_version 800057 marks the switchover from the
1614 binary ath hal to source code. Users must add the line:
1616 options AH_SUPPORT_AR5416
1618 to their kernel config files when specifying:
1622 The ath_hal module no longer exists; the code is now compiled
1623 together with the driver in the ath module. It is now
1624 possible to tailor chip support (i.e. reduce the set of chips
1625 and thereby the code size); consult ath_hal(4) for details.
1628 __FreeBSD_version 800054 adds memory barriers to
1629 <machine/atomic.h>, new interfaces to ifnet to facilitate
1630 multiple hardware transmit queues for cards that support
1631 them, and a lock-less ring-buffer implementation to
1632 enable drivers to more efficiently manage queueing of
1636 A new version of ZFS (version 13) has been merged to -HEAD.
1637 This version has zpool attribute "listsnapshots" off by
1638 default, which means "zfs list" does not show snapshots,
1639 and is the same as Solaris behavior.
1642 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1645 The uhci, ohci, ehci and slhci USB Host controller drivers have
1646 been put into separate modules. If you load the usb module
1647 separately through loader.conf you will need to load the
1648 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1649 controller add the following to loader.conf:
1655 The ABI used by the PMC toolset has changed. Please keep
1656 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1660 atapci kernel module now includes only generic PCI ATA
1661 driver. AHCI driver moved to ataahci kernel module.
1662 All vendor-specific code moved into separate kernel modules:
1663 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1664 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1665 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1666 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1669 The TTY subsystem of the kernel has been replaced by a new
1670 implementation, which provides better scalability and an
1671 improved driver model. Most common drivers have been migrated to
1672 the new TTY subsystem, while others have not. The following
1673 drivers have not yet been ported to the new TTY layer:
1676 cy, digi, rc, rp, sio
1682 ng_h4, ng_tty, ppp, sl, snp
1684 Adding these drivers to your kernel configuration file shall
1685 cause compilation to fail.
1688 ntpd has been upgraded to 4.2.4p5.
1691 OpenSSH has been upgraded to 5.1p1.
1693 For many years, FreeBSD's version of OpenSSH preferred DSA
1694 over RSA for host and user authentication keys. With this
1695 upgrade, we've switched to the vendor's default of RSA over
1696 DSA. This may cause upgraded clients to warn about unknown
1697 host keys even for previously known hosts. Users should
1698 follow the usual procedure for verifying host keys before
1699 accepting the RSA key.
1701 This can be circumvented by setting the "HostKeyAlgorithms"
1702 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1705 Please note that the sequence of keys offered for
1706 authentication has been changed as well. You may want to
1707 specify IdentityFile in a different order to revert this
1711 The sio(4) driver has been removed from the i386 and amd64
1712 kernel configuration files. This means uart(4) is now the
1713 default serial port driver on those platforms as well.
1715 To prevent collisions with the sio(4) driver, the uart(4) driver
1716 uses different names for its device nodes. This means the
1717 onboard serial port will now most likely be called "ttyu0"
1718 instead of "ttyd0". You may need to reconfigure applications to
1719 use the new device names.
1721 When using the serial port as a boot console, be sure to update
1722 /boot/device.hints and /etc/ttys before booting the new kernel.
1723 If you forget to do so, you can still manually specify the hints
1724 at the loader prompt:
1726 set hint.uart.0.at="isa"
1727 set hint.uart.0.port="0x3F8"
1728 set hint.uart.0.flags="0x10"
1729 set hint.uart.0.irq="4"
1733 The gpt(8) utility has been removed. Use gpart(8) to partition
1737 The version that Linuxulator emulates was changed from 2.4.2
1738 to 2.6.16. If you experience any problems with Linux binaries
1739 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1740 if it fixes the problem contact emulation mailing list.
1743 ISDN4BSD (I4B) was removed from the src tree. You may need to
1744 update a your kernel configuration and remove relevant entries.
1747 I have checked in code to support multiple routing tables.
1748 See the man pages setfib(1) and setfib(2).
1749 This is a hopefully backwards compatible version,
1750 but to make use of it you need to compile your kernel
1751 with options ROUTETABLES=2 (or more up to 16).
1754 The 802.11 wireless support was redone to enable multi-bss
1755 operation on devices that are capable. The underlying device
1756 is no longer used directly but instead wlanX devices are
1757 cloned with ifconfig. This requires changes to rc.conf files.
1758 For example, change:
1759 ifconfig_ath0="WPA DHCP"
1762 ifconfig_wlan0="WPA DHCP"
1763 see rc.conf(5) for more details. In addition, mergemaster of
1764 /etc/rc.d is highly recommended. Simultaneous update of userland
1765 and kernel wouldn't hurt either.
1767 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1768 modules were merged into the base wlan module. All references
1769 to these modules (e.g. in kernel config files) must be removed.
1772 psm(4) has gained write(2) support in native operation level.
1773 Arbitrary commands can be written to /dev/psm%d and status can
1774 be read back from it. Therefore, an application is responsible
1775 for status validation and error recovery. It is a no-op in
1776 other operation levels.
1779 Support for KSE threading has been removed from the kernel. To
1780 run legacy applications linked against KSE libmap.conf may
1781 be used. The following libmap.conf may be used to ensure
1782 compatibility with any prior release:
1784 libpthread.so.1 libthr.so.1
1785 libpthread.so.2 libthr.so.2
1786 libkse.so.3 libthr.so.3
1789 The layout of struct vmspace has changed. This affects libkvm
1790 and any executables that link against libkvm and use the
1791 kvm_getprocs() function. In particular, but not exclusively,
1792 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1793 The effects are minimal, but it's advisable to upgrade world
1797 The latest em driver no longer has support in it for the
1798 82575 adapter, this is now moved to the igb driver. The
1799 split was done to make new features that are incompatible
1800 with older hardware easier to do.
1803 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1804 likewise the kernel option is now GEOM_LINUX_LVM.
1807 The default NFS mount mode has changed from UDP to TCP for
1808 increased reliability. If you rely on (insecurely) NFS
1809 mounting across a firewall you may need to update your
1813 Belatedly note the addition of m_collapse for compacting
1817 The fts(3) structures have been changed to use adequate
1818 integer types for their members and so to be able to cope
1819 with huge file trees. The old fts(3) ABI is preserved
1820 through symbol versioning in libc, so third-party binaries
1821 using fts(3) should still work, although they will not take
1822 advantage of the extended types. At the same time, some
1823 third-party software might fail to build after this change
1824 due to unportable assumptions made in its source code about
1825 fts(3) structure members. Such software should be fixed
1826 by its vendor or, in the worst case, in the ports tree.
1827 FreeBSD_version 800015 marks this change for the unlikely
1828 case that a portable fix is impossible.
1831 To upgrade to -current after this date, you must be running
1832 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1833 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1836 The ADAPTIVE_GIANT kernel option has been retired because its
1837 functionality is the default now.
1840 The AT keyboard emulation of sunkbd(4) has been turned on
1841 by default. In order to make the special symbols of the Sun
1842 keyboards driven by sunkbd(4) work under X these now have
1843 to be configured the same way as Sun USB keyboards driven
1844 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1846 Option "XkbLayout" "us"
1847 Option "XkbRules" "xorg"
1848 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1851 It has been decided that it is desirable to provide ABI
1852 backwards compatibility to the FreeBSD 4/5/6 versions of the
1853 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1854 broken with the introduction of PCI domain support (see the
1855 20070930 entry). Unfortunately, this required the ABI of
1856 PCIOCGETCONF to be broken again in order to be able to
1857 provide backwards compatibility to the old version of that
1858 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1859 again. As for prominent ports this affects neither pciutils
1860 nor xorg-server this time, the hal port needs to be rebuilt
1864 The misnamed kthread_create() and friends have been renamed
1865 to kproc_create() etc. Many of the callers already
1866 used kproc_start()..
1867 I will return kthread_create() and friends in a while
1868 with implementations that actually create threads, not procs.
1869 Renaming corresponds with version 800002.
1878 Avoid using make -j when upgrading. While generally safe, there are
1879 sometimes problems using -j to upgrade. If your upgrade fails with
1880 -j, please try again without -j. From time to time in the past there
1881 have been problems using -j with buildworld and/or installworld. This
1882 is especially true when upgrading between "distant" versions (eg one
1883 that cross a major release boundary or several minor releases, or when
1884 several months have passed on the -current branch).
1886 Sometimes, obscure build problems are the result of environment
1887 poisoning. This can happen because the make utility reads its
1888 environment when searching for values for global variables. To run
1889 your build attempts in an "environmental clean room", prefix all make
1890 commands with 'env -i '. See the env(1) manual page for more details.
1892 When upgrading from one major version to another it is generally best
1893 to upgrade to the latest code in the currently installed branch first,
1894 then do an upgrade to the new branch. This is the best-tested upgrade
1895 path, and has the highest probability of being successful. Please try
1896 this approach before reporting problems with a major version upgrade.
1898 When upgrading a live system, having a root shell around before
1899 installing anything can help undo problems. Not having a root shell
1900 around can lead to problems if pam has changed too much from your
1901 starting point to allow continued authentication after the upgrade.
1905 When upgrading the boot ZFS pool to a new version, always follow
1908 1.) recompile and reinstall the ZFS boot loader and boot block
1909 (this is part of "make buildworld" and "make installworld")
1911 2.) update the ZFS boot block on your boot drive
1913 The following example updates the ZFS boot block on the first
1914 partition (freebsd-boot) of a GPT partitioned drive ad0:
1915 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1917 Non-boot pools do not need these updates.
1921 If you are updating from a prior version of FreeBSD (even one just
1922 a few days old), you should follow this procedure. It is the most
1923 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1925 make kernel-toolchain
1926 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1927 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1929 To test a kernel once
1930 ---------------------
1931 If you just want to boot a kernel once (because you are not sure
1932 if it works, or if you want to boot a known bad kernel to provide
1933 debugging information) run
1934 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1935 nextboot -k testkernel
1937 To just build a kernel when you know that it won't mess you up
1938 --------------------------------------------------------------
1939 This assumes you are already running a CURRENT system. Replace
1940 ${arch} with the architecture of your machine (e.g. "i386",
1941 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1943 cd src/sys/${arch}/conf
1944 config KERNEL_NAME_HERE
1945 cd ../compile/KERNEL_NAME_HERE
1950 If this fails, go to the "To build a kernel" section.
1952 To rebuild everything and install it on the current system.
1953 -----------------------------------------------------------
1954 # Note: sometimes if you are running current you gotta do more than
1955 # is listed here if you are upgrading from a really old current.
1957 <make sure you have good level 0 dumps>
1959 make kernel KERNCONF=YOUR_KERNEL_HERE
1961 <reboot in single user> [3]
1968 To cross-install current onto a separate partition
1969 --------------------------------------------------
1970 # In this approach we use a separate partition to hold
1971 # current's root, 'usr', and 'var' directories. A partition
1972 # holding "/", "/usr" and "/var" should be about 2GB in
1975 <make sure you have good level 0 dumps>
1978 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1979 <maybe newfs current's root partition>
1980 <mount current's root partition on directory ${CURRENT_ROOT}>
1981 make installworld DESTDIR=${CURRENT_ROOT}
1982 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1983 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1984 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1985 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1986 <reboot into current>
1987 <do a "native" rebuild/install as described in the previous section>
1988 <maybe install compatibility libraries from ports/misc/compat*>
1992 To upgrade in-place from stable to current
1993 ----------------------------------------------
1994 <make sure you have good level 0 dumps>
1996 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1998 <reboot in single user> [3]
2005 Make sure that you've read the UPDATING file to understand the
2006 tweaks to various things you need. At this point in the life
2007 cycle of current, things change often and you are on your own
2008 to cope. The defaults can also change, so please read ALL of
2009 the UPDATING entries.
2011 Also, if you are tracking -current, you must be subscribed to
2012 freebsd-current@freebsd.org. Make sure that before you update
2013 your sources that you have read and understood all the recent
2014 messages there. If in doubt, please track -stable which has
2015 much fewer pitfalls.
2017 [1] If you have third party modules, such as vmware, you
2018 should disable them at this point so they don't crash your
2021 [3] From the bootblocks, boot -s, and then do
2026 adjkerntz -i # if CMOS is wall time
2027 Also, when doing a major release upgrade, it is required that
2028 you boot into single user mode to do the installworld.
2030 [4] Note: This step is non-optional. Failure to do this step
2031 can result in a significant reduction in the functionality of the
2032 system. Attempting to do it by hand is not recommended and those
2033 that pursue this avenue should read this file carefully, as well
2034 as the archives of freebsd-current and freebsd-hackers mailing lists
2035 for potential gotchas. The -U option is also useful to consider.
2036 See mergemaster(8) for more information.
2038 [5] Usually this step is a noop. However, from time to time
2039 you may need to do this if you get unknown user in the following
2040 step. It never hurts to do it all the time. You may need to
2041 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2042 install) after the buildworld before this step if you last updated
2043 from current before 20130425 or from -stable before 20130430.
2045 [6] This only deletes old files and directories. Old libraries
2046 can be deleted by "make delete-old-libs", but you have to make
2047 sure that no program is using those libraries anymore.
2049 [8] In order to have a kernel that can run the 4.x binaries needed to
2050 do an installworld, you must include the COMPAT_FREEBSD4 option in
2051 your kernel. Failure to do so may leave you with a system that is
2052 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2053 required to run the 5.x binaries on more recent kernels. And so on
2054 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2056 Make sure that you merge any new devices from GENERIC since the
2057 last time you updated your kernel config file.
2059 [9] When checking out sources, you must include the -P flag to have
2060 cvs prune empty directories.
2062 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2063 "?=" instead of the "=" assignment operator, so that buildworld can
2064 override the CPUTYPE if it needs to.
2066 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2067 not on the command line, or in /etc/make.conf. buildworld will
2068 warn if it is improperly defined.
2071 This file contains a list, in reverse chronological order, of major
2072 breakages in tracking -current. It is not guaranteed to be a complete
2073 list of such breakages, and only contains entries since October 10, 2007.
2074 If you need to see UPDATING entries from before that date, you will need
2075 to fetch an UPDATING file from an older FreeBSD release.
2077 Copyright information:
2079 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2081 Redistribution, publication, translation and use, with or without
2082 modification, in full or in part, in any form or format of this
2083 document are permitted without further permission from the author.
2085 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2086 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2087 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2088 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2089 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2090 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2091 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2092 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2093 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2094 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2095 POSSIBILITY OF SUCH DAMAGE.
2097 Contact Warner Losh if you have any questions about your use of