1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
20 The behavior of gss_pseudo_random() for the krb5 mechanism
21 has changed, for applications requesting a longer random string
22 than produced by the underlying enctype's pseudo-random() function.
23 In particular, the random string produced from a session key of
24 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
25 be different at the 17th octet and later, after this change.
26 The counter used in the PRF+ construction is now encoded as a
27 big-endian integer in accordance with RFC 4402.
28 __FreeBSD_version is bumped to 1000701.
31 The WITHOUT_ATF build knob has been removed and its functionality
32 has been subsumed into the more generic WITHOUT_TESTS. If you were
33 using the former to disable the build of the ATF libraries, you
34 should change your settings to use the latter.
37 The default version of mtree is nmtree which is obtained from
38 NetBSD. The output is generally the same, but may vary
39 slightly. If you found you need identical output adding
40 "-F freebsd9" to the command line should do the trick. For the
41 time being, the old mtree is available as fmtree.
44 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
45 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
46 1.1.4_8 and verify bsdyml not linked in, before running "make
48 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
50 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
53 The rc.d/jail script has been updated to support jail(8)
54 configuration file. The "jail_<jname>_*" rc.conf(5) variables
55 for per-jail configuration are automatically converted to
56 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
57 This is transparently backward compatible. See below about some
58 incompatibilities and rc.conf(5) manual page for more details.
60 These variables are now deprecated in favor of jail(8) configuration
61 file. One can use "rc.d/jail config <jname>" command to generate
62 a jail(8) configuration file in /var/run/jail.<jname>.conf without
63 running the jail(8) utility. The default pathname of the
64 configuration file is /etc/jail.conf and can be specified by
65 using $jail_conf or $jail_<jname>_conf variables.
67 Please note that jail_devfs_ruleset accepts an integer at
68 this moment. Please consider to rewrite the ruleset name
72 BIND has been removed from the base system. If all you need
73 is a local resolver, simply enable and start the local_unbound
74 service instead. Otherwise, several versions of BIND are
75 available in the ports tree. The dns/bind99 port is one example.
77 With this change, nslookup(1) and dig(1) are no longer in the base
78 system. Users should instead use host(1) and drill(1) which are
79 in the base system. Alternatively, nslookup and dig can
80 be obtained by installing the dns/bind-tools port.
83 With the addition of unbound(8), a new unbound user is now
84 required during installworld. "mergemaster -p" can be used to
85 add the user prior to installworld, as documented in the handbook.
88 OpenSSH is now built with DNSSEC support, and will by default
89 silently trust signed SSHFP records. This can be controlled with
90 the VerifyHostKeyDNS client configuration setting. DNSSEC support
91 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
94 The GNU Compiler Collection and C++ standard library (libstdc++)
95 are no longer built by default on platforms where clang is the system
96 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
100 The PROCDESC kernel option is now part of the GENERIC kernel
101 configuration and is required for the rwhod(8) to work.
102 If you are using custom kernel configuration, you should include
106 The API and ABI related to the Capsicum framework was modified
107 in backward incompatible way. The userland libraries and programs
108 have to be recompiled to work with the new kernel. This includes the
109 following libraries and programs, but the whole buildworld is
110 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
111 kdump, procstat, rwho, rwhod, uniq.
114 AES-NI intrinsic support has been added to gcc. The AES-NI module
115 has been updated to use this support. A new gcc is required to build
116 the aesni module on both i386 and amd64.
119 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
120 Thus "device padlock_rng" and "device rdrand_rng" should be
121 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
124 WITH_ICONV has been split into two feature sets. WITH_ICONV now
125 enables just the iconv* functionality and is now on by default.
126 WITH_LIBICONV_COMPAT enables the libiconv api and link time
127 compatability. Set WITHOUT_ICONV to build the old way.
128 If you have been using WITH_ICONV before, you will very likely
129 need to turn on WITH_LIBICONV_COMPAT.
132 INVARIANTS option now enables DEBUG for code with OpenSolaris and
133 Illumos origin, including ZFS. If you have INVARIANTS in your
134 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
136 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
137 locks if WITNESS option was set. Because that generated a lot of
138 witness(9) reports and all of them were believed to be false
139 positives, this is no longer done. New option OPENSOLARIS_WITNESS
140 can be used to achieve the previous behavior.
143 Timer values in IPv6 data structures now use time_uptime instead
144 of time_second. Although this is not a user-visible functional
145 change, userland utilities which directly use them---ndp(8),
146 rtadvd(8), and rtsold(8) in the base system---need to be updated
150 find -delete can now delete the pathnames given as arguments,
151 instead of only files found below them or if the pathname did
152 not contain any slashes. Formerly, the following error message
155 find: -delete: <path>: relative path potentially not safe
157 Deleting the pathnames given as arguments can be prevented
158 without error messages using -mindepth 1 or by changing
159 directory and passing "." as argument to find. This works in the
160 old as well as the new version of find.
163 Behavior of devfs rules path matching has been changed.
164 Pattern is now always matched against fully qualified devfs
165 path and slash characters must be explicitly matched by
166 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
167 subdirectories must be reviewed.
170 The default ARM ABI has changed to the ARM EABI. The old ABI is
171 incompatible with the ARM EABI and all programs and modules will
172 need to be rebuilt to work with a new kernel.
174 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
176 NOTE: Support for the old ABI will be removed in the future and
177 users are advised to upgrade.
180 pkg_install has been disconnected from the build if you really need it
181 you should add WITH_PKGTOOLS in your src.conf(5).
184 Most of network statistics structures were changed to be able
185 keep 64-bits counters. Thus all tools, that work with networking
186 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
189 Fix targets that run multiple make's to use && rather than ;
190 so that subsequent steps depend on success of previous.
192 NOTE: if building 'universe' with -j* on stable/8 or stable/9
193 it would be better to start the build using bmake, to avoid
194 overloading the machine.
197 Fix a bug that allowed a tracing process (e.g. gdb) to write
198 to a memory-mapped file in the traced process's address space
199 even if neither the traced process nor the tracing process had
200 write access to that file.
203 CVS has been removed from the base system. An exact copy
204 of the code is available from the devel/cvs port.
207 Some people report the following error after the switch to bmake:
209 make: illegal option -- J
210 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
212 *** [buildworld] Error code 2
214 this likely due to an old instance of make in
215 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
216 which src/Makefile will use that blindly, if it exists, so if
217 you see the above error:
219 rm -rf `make -V MAKEPATH`
224 Use bmake by default.
225 Whereas before one could choose to build with bmake via
226 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
227 make. The goal is to remove these knobs for 10-RELEASE.
229 It is worth noting that bmake (like gmake) treats the command
230 line as the unit of failure, rather than statements within the
231 command line. Thus '(cd some/where && dosomething)' is safer
232 than 'cd some/where; dosomething'. The '()' allows consistent
233 behavior in parallel build.
236 Fix a bug that allows NFS clients to issue READDIR on files.
239 The WITHOUT_IDEA option has been removed because
240 the IDEA patent expired.
243 The sysctl which controls TRIM support under ZFS has been renamed
244 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
248 The mergemaster command now uses the default MAKEOBJDIRPREFIX
249 rather than creating it's own in the temporary directory in
250 order allow access to bootstrapped versions of tools such as
251 install and mtree. When upgrading from version of FreeBSD where
252 the install command does not support -l, you will need to
253 install a new mergemaster command if mergemaster -p is required.
254 This can be accomplished with the command (cd src/usr.sbin/mergemaster
258 Legacy ATA stack, disabled and replaced by new CAM-based one since
259 FreeBSD 9.0, completely removed from the sources. Kernel modules
260 atadisk and atapi*, user-level tools atacontrol and burncd are
261 removed. Kernel option `options ATA_CAM` is now permanently enabled
265 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
266 and socketpair(2). Software, in particular Kerberos, may
267 automatically detect and use these during building. The resulting
268 binaries will not work on older kernels.
271 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
272 information, see the respective 20130304 entry).
275 Recent commits to callout(9) changed the size of struct callout,
276 so the KBI is probably heavily disturbed. Also, some functions
277 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
278 by macros. Every kernel module using it won't load, so rebuild
281 The ctl device has been re-enabled in GENERIC for i386 and amd64,
282 but does not initialize by default (because of the new CTL_DISABLE
283 option) to save memory. To re-enable it, remove the CTL_DISABLE
284 option from the kernel config file or set kern.cam.ctl.disable=0
285 in /boot/loader.conf.
288 The ctl device has been disabled in GENERIC for i386 and amd64.
289 This was done due to the extra memory being allocated at system
290 initialisation time by the ctl driver which was only used if
291 a CAM target device was created. This makes a FreeBSD system
292 unusable on 128MB or less of RAM.
295 A new compression method (lz4) has been merged to -HEAD. Please
296 refer to zpool-features(7) for more information.
298 Please refer to the "ZFS notes" section of this file for information
299 on upgrading boot ZFS pools.
302 A BSD-licensed patch(1) variant has been added and is installed
303 as bsdpatch, being the GNU version the default patch.
304 To inverse the logic and use the BSD-licensed one as default,
305 while having the GNU version installed as gnupatch, rebuild
306 and install world with the WITH_BSD_PATCH knob set.
309 Due to the use of the new -l option to install(1) during build
310 and install, you must take care not to directly set the INSTALL
311 make variable in your /etc/make.conf, /etc/src.conf, or on the
312 command line. If you wish to use the -C flag for all installs
313 you may be able to add INSTALL+=-C to /etc/make.conf or
317 The install(1) option -M has changed meaning and now takes an
318 argument that is a file or path to append logs to. In the
319 unlikely event that -M was the last option on the command line
320 and the command line contained at least two files and a target
321 directory the first file will have logs appended to it. The -M
322 option served little practical purpose in the last decade so its
323 use is expected to be extremely rare.
326 After switching to Clang as the default compiler some users of ZFS
327 on i386 systems started to experience stack overflow kernel panics.
328 Please consider using 'options KSTACK_PAGES=4' in such configurations.
331 GEOM_LABEL now mangles label names read from file system metadata.
332 Mangling affect labels containing spaces, non-printable characters,
333 '%' or '"'. Device names in /etc/fstab and other places may need to
337 By default, only the 10 most recent kernel dumps will be saved. To
338 restore the previous behaviour (no limit on the number of kernel dumps
339 stored in the dump directory) add the following line to /etc/rc.conf:
344 With the addition of auditdistd(8), a new auditdistd user is now
345 required during installworld. "mergemaster -p" can be used to
346 add the user prior to installworld, as documented in the handbook.
349 The sin6_scope_id member variable in struct sockaddr_in6 is now
350 filled by the kernel before passing the structure to the userland via
351 sysctl or routing socket. This means the KAME-specific embedded scope
352 id in sin6_addr.s6_addr[2] is always cleared in userland application.
353 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
354 __FreeBSD_version is bumped to 1000025.
357 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
358 This means that the world and kernel will be compiled with clang
359 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
360 and /usr/bin/cpp. To disable this behavior and revert to building
361 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
362 of current may need to bootstrap WITHOUT_CLANG first if the clang
363 build fails (its compatibility window doesn't extend to the 9 stable
367 The IPFIREWALL_FORWARD kernel option has been removed. Its
368 functionality now turned on by default.
371 The ZERO_COPY_SOCKET kernel option has been removed and
372 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
373 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
374 mechanism which is not safe and may result in kernel crashes.
375 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
376 driver supports disposeable external page sized mbuf storage.
377 Proper replacements for both zero-copy mechanisms are under
378 consideration and will eventually lead to complete removal
379 of the two kernel options.
382 The IPv4 network stack has been converted to network byte
383 order. The following modules need to be recompiled together
384 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
385 pf(4), ipfw(4), ng_ipfw(4), stf(4).
388 Support for non-MPSAFE filesystems was removed from VFS. The
389 VFS_VERSION was bumped, all filesystem modules shall be
393 All the non-MPSAFE filesystems have been disconnected from
394 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
395 portalfs, smbfs, xfs.
398 The interface cloning API and ABI has changed. The following
399 modules need to be recompiled together with kernel:
400 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
401 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
402 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
405 The sdhci driver was split in two parts: sdhci (generic SD Host
406 Controller logic) and sdhci_pci (actual hardware driver).
407 No kernel config modifications are required, but if you
408 load sdhc as a module you must switch to sdhci_pci instead.
411 Import the FUSE kernel and userland support into base system.
414 The GNU sort(1) program has been removed since the BSD-licensed
415 sort(1) has been the default for quite some time and no serious
416 problems have been reported. The corresponding WITH_GNU_SORT
420 The pfil(9) API/ABI for AF_INET family has been changed. Packet
421 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
425 The net80211(4) ABI has been changed to allow for improved driver
426 PS-POLL and power-save support. All wireless drivers need to be
427 recompiled to work with the new kernel.
430 The random(4) support for the VIA hardware random number
431 generator (`PADLOCK') is no longer enabled unconditionally.
432 Add the padlock_rng device in the custom kernel config if
433 needed. The GENERIC kernels on i386 and amd64 do include the
434 device, so the change only affects the custom kernel
438 The pf(4) packet filter ABI has been changed. pfctl(8) and
439 snmp_pf module need to be recompiled to work with new kernel.
442 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
443 to -HEAD. Pools that have empty_bpobj in active state can not be
444 imported read-write with ZFS implementations that do not support
445 this feature. For more information read the zpool-features(5)
449 The sparc64 ZFS loader has been changed to no longer try to auto-
450 detect ZFS providers based on diskN aliases but now requires these
451 to be explicitly listed in the OFW boot-device environment variable.
454 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
455 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
456 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
459 The following sysctls and tunables have been renamed for consistency
460 with other variables:
461 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
462 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
465 The sort utility has been replaced with BSD sort. For now, GNU sort
466 is also available as "gnusort" or the default can be set back to
467 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
468 installed as "bsdsort".
471 A new version of ZFS (pool version 5000) has been merged to -HEAD.
472 Starting with this version the old system of ZFS pool versioning
473 is superseded by "feature flags". This concept enables forward
474 compatibility against certain future changes in functionality of ZFS
475 pools. The first read-only compatible "feature flag" for ZFS pools
476 is named "com.delphix:async_destroy". For more information
477 read the new zpool-features(5) manual page.
478 Please refer to the "ZFS notes" section of this file for information
479 on upgrading boot ZFS pools.
482 The malloc(3) implementation embedded in libc now uses sources imported
483 as contrib/jemalloc. The most disruptive API change is to
484 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
485 delete it prior to installworld, and optionally re-create it using the
486 new format after rebooting. See malloc.conf(5) for details
487 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
491 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
492 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
493 now spelled mips. This is to aid compatibility with third-party
494 software that expects this naming scheme in uname(3). Little-endian
495 settings are unchanged. If you are updating a big-endian mips64 machine
496 from before this change, you may need to set MACHINE_ARCH=mips64 in
497 your environment before the new build system will recognize your machine.
500 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
504 Now unix domain sockets behave "as expected" on nullfs(5). Previously
505 nullfs(5) did not pass through all behaviours to the underlying layer,
506 as a result if we bound to a socket on the lower layer we could connect
507 only to the lower path; if we bound to the upper layer we could connect
508 only to the upper path. The new behavior is one can connect to both the
509 lower and the upper paths regardless what layer path one binds to.
512 The getifaddrs upgrade path broken with 20111215 has been restored.
513 If you have upgraded in between 20111215 and 20120209 you need to
514 recompile libc again with your kernel. You still need to recompile
515 world to be able to configure CARP but this restriction already
519 The set_rcvar() function has been removed from /etc/rc.subr. All
520 base and ports rc.d scripts have been updated, so if you have a
521 port installed with a script in /usr/local/etc/rc.d you can either
522 hand-edit the rcvar= line, or reinstall the port.
524 An easy way to handle the mass-update of /etc/rc.d:
525 rm /etc/rc.d/* && mergemaster -i
528 panic(9) now stops other CPUs in the SMP systems, disables interrupts
529 on the current CPU and prevents other threads from running.
530 This behavior can be reverted using the kern.stop_scheduler_on_panic
532 The new behavior can be incompatible with kern.sync_on_panic.
535 The carp(4) facility has been changed significantly. Configuration
536 of the CARP protocol via ifconfig(8) has changed, as well as format
537 of CARP events submitted to devd(8) has changed. See manual pages
538 for more information. The arpbalance feature of carp(4) is currently
539 not supported anymore.
541 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
542 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
543 need to be recompiled.
546 The acpi_wmi(4) status device /dev/wmistat has been renamed to
550 The option VFS_ALLOW_NONMPSAFE option has been added in order to
551 explicitely support non-MPSAFE filesystems.
552 It is on by default for all supported platform at this present
556 The broken amd(4) driver has been replaced with esp(4) in the amd64,
557 i386 and pc98 GENERIC kernel configuration files.
560 sysinstall has been removed
563 The stable/9 branch created in subversion. This corresponds to the
564 RELENG_9 branch in CVS.
567 This commit modifies vfs_register() so that it uses a hash
568 calculation to set vfc_typenum, which is enabled by default.
569 The first time a system is booted after this change, the
570 vfc_typenum values will change for all file systems. The
571 main effect of this is a change to the NFS server file handles
572 for file systems that use vfc_typenum in their fsid, such as ZFS.
573 It will, however, prevent vfc_typenum from changing when file
574 systems are loaded in a different order for subsequent reboots.
575 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
576 until you are ready to remount all NFS clients after a reboot.
579 Bump the shared library version numbers for libraries that
580 do not use symbol versioning, have changed the ABI compared
581 to stable/8 and which shared library version was not bumped.
582 Done as part of 9.0-RELEASE cycle.
585 During the merge of Capsicum features, the fget(9) KPI was modified.
586 This may require the rebuilding of out-of-tree device drivers --
587 issues have been reported specifically with the nVidia device driver.
588 __FreeBSD_version is bumped to 900041.
590 Also, there is a period between 20110811 and 20110814 where the
591 special devices /dev/{stdin,stdout,stderr} did not work correctly.
592 Building world from a kernel during that window may not work.
595 The packet filter (pf) code has been updated to OpenBSD 4.5.
596 You need to update userland tools to be in sync with kernel.
597 This update breaks backward compatibility with earlier pfsync(4)
598 versions. Care must be taken when updating redundant firewall setups.
601 The following sysctls and tunables are retired on x86 platforms:
603 machdep.hlt_logical_cpus
604 The following sysctl is retired:
605 machdep.hyperthreading_allowed
606 The sysctls were supposed to provide a way to dynamically offline and
607 online selected CPUs on x86 platforms, but the implementation has not
608 been reliable especially with SCHED_ULE scheduler.
609 machdep.hyperthreading_allowed tunable is still available to ignore
610 hyperthreading CPUs at OS level.
611 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
612 where X is an APIC ID of a CPU. Be advised, though, that disabling
613 CPUs in non-uniform fashion will result in non-uniform topology and
614 may lead to sub-optimal system performance with SCHED_ULE, which is
618 cpumask_t type is retired and cpuset_t is used in order to describe
622 Changes to ifconfig(8) for dynamic address family detection mandate
623 that you are running a kernel of 20110525 or later. Make sure to
624 follow the update procedure to boot a new kernel before installing
628 Support for sun4v architecture is officially dropped
631 Several KPI breaking changes have been committed to the mii(4) layer,
632 the PHY drivers and consequently some Ethernet drivers using mii(4).
633 This means that miibus.ko and the modules of the affected Ethernet
634 drivers need to be recompiled.
636 Note to kernel developers: Given that the OUI bit reversion problem
637 was fixed as part of these changes all mii(4) commits related to OUIs,
638 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
639 handling, no longer can be merged verbatim to stable/8 and previous
643 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
644 into their kernel configurations along with 'device pci'.
647 The default NFS client is now the new NFS client, so fstype "newnfs"
648 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
649 Although mounts via fstype "nfs" will usually work without userland
650 changes, it is recommended that the mount(8) and mount_nfs(8)
651 commands be rebuilt from sources and that a link to mount_nfs called
652 mount_oldnfs be created. The new client is compiled into the
653 kernel with "options NFSCL" and this is needed for diskless root
654 file systems. The GENERIC kernel configs have been changed to use
655 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
656 To use the regular/old client, you can "mount -t oldnfs ...". For
657 a diskless root file system, you must also include a line like:
659 vfs.root.mountfrom="oldnfs:"
661 in the boot/loader.conf on the root fs on the NFS server to make
662 a diskless root fs use the old client.
665 The GENERIC kernels for all architectures now default to the new
666 CAM-based ATA stack. It means that all legacy ATA drivers were
667 removed and replaced by respective CAM drivers. If you are using
668 ATA device names in /etc/fstab or other places, make sure to update
669 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
670 where 'Y's are the sequential numbers starting from zero for each type
671 in order of detection, unless configured otherwise with tunables,
672 see cam(4)). There will be symbolic links created in /dev/ to map
673 old adX devices to the respective adaY. They should provide basic
674 compatibility for file systems mounting in most cases, but they do
675 not support old user-level APIs and do not have respective providers
676 in GEOM. Consider using updated management tools with new device names.
678 It is possible to load devices ahci, ata, siis and mvs as modules,
679 but option ATA_CAM should remain in kernel configuration to make ata
680 module work as CAM driver supporting legacy ATA controllers. Device ata
681 still can be used in modular fashion (atacore + ...). Modules atadisk
682 and atapi* are not used and won't affect operation in ATA_CAM mode.
683 Note that to use CAM-based ATA kernel should include CAM devices
684 scbus, pass, da (or explicitly ada), cd and optionally others. All of
685 them are parts of the cam module.
687 ataraid(4) functionality is now supported by the RAID GEOM class.
688 To use it you can load geom_raid kernel module and use graid(8) tool
689 for management. Instead of /dev/arX device names, use /dev/raid/rX.
691 No kernel config options or code have been removed, so if a problem
692 arises, please report it and optionally revert to the old ATA stack.
693 In order to do it you can remove from the kernel config:
698 , and instead add back:
699 device atadisk # ATA disk drives
700 device ataraid # ATA RAID drives
701 device atapicd # ATAPI CDROM drives
702 device atapifd # ATAPI floppy drives
703 device atapist # ATAPI tape drives
706 The default NFS server has been changed to the new server, which
707 was referred to as the experimental server. If you need to switch
708 back to the old NFS server, you must now put the "-o" option on
709 both the mountd and nfsd commands. This can be done using the
710 mountd_flags and nfs_server_flags rc.conf variables until an
711 update to the rc scripts is committed, which is coming soon.
714 The GNU Objective-C runtime library (libobjc), and other Objective-C
715 related components have been removed from the base system. If you
716 require an Objective-C library, please use one of the available ports.
719 ath(4) has been split into bus- and device- modules. if_ath contains
720 the HAL, the TX rate control and the network device code. if_ath_pci
721 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
722 contains the AHB glue. Users need to load both if_ath_pci and if_ath
723 in order to use ath on everything else.
725 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
726 need to load if_ath and if_ath_pci for ath(4) operation.
729 As part of the replacement of sysinstall, the process of building
730 release media has changed significantly. For details, please re-read
731 release(7), which has been updated to reflect the new build process.
734 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
735 is the last available version under GPLv2. It brings a number of new
736 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
737 4.1 and SSE 4.2), better support for powerpc64, a number of new
738 directives, and lots of other small improvements. See the ChangeLog
739 file in contrib/binutils for the full details.
742 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
743 compliant, and will now use half of hash for authentication.
744 This will break interoperability with all stacks (including all
745 actual FreeBSD versions) who implement
746 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
748 The only workaround with such peers is to use another HMAC
749 algorithm for IPsec ("phase 2") authentication.
752 Remove the uio_yield prototype and symbol. This function has
753 been misnamed since it was introduced and should not be
754 globally exposed with this name. The equivalent functionality
755 is now available using kern_yield(curthread->td_user_pri).
756 The function remains undocumented.
759 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
760 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
761 for scalar sysctls is defined but disabled. Code that needs
762 UQUAD to pass the type checking that must compile on older
763 systems where the define is not present can check against
764 __FreeBSD_version >= 900030.
766 The system dialog(1) has been replaced with a new version previously
767 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
768 with the previous version, but the libdialog associated with it has
769 a largely incompatible API. As such, the original version of libdialog
770 will be kept temporarily as libodialog, until its base system consumers
771 are replaced or updated. Bump __FreeBSD_version to 900030.
774 If you are trying to run make universe on a -stable system, and you get
775 the following warning:
776 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
777 unknown. config(8) likely too old."
778 or something similar to it, then you must upgrade your -stable system
779 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
780 stable/8) or build the config from the latest stable/8 branch and
781 install it on your system.
783 Prior to this date, building a current universe on 8-stable system from
784 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
785 error in the first kernel build phase. A new config on those old
786 systems will fix that problem for older versions of -current.
789 The TCP stack has been modified to allow Khelp modules to interact with
790 it via helper hook points and store per-connection data in the TCP
791 control block. Bump __FreeBSD_version to 900029. User space tools that
792 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
796 Generic IEEE 802.3 annex 31B full duplex flow control support has been
797 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
798 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
799 to take advantage of it instead of using custom implementations. This
800 means that these drivers now no longer unconditionally advertise
801 support for flow control but only do so if flow control is a selected
802 media option. This was implemented in the generic support that way in
803 order to allow flow control to be switched on and off via ifconfig(8)
804 with the PHY specific default to typically off in order to protect
805 from unwanted effects. Consequently, if you used flow control with
806 one of the above mentioned drivers you now need to explicitly enable
808 ifconfig bge0 media auto mediaopt flowcontrol
810 Along with the above mentioned changes generic support for setting
811 1000baseT master mode also has been added and brgphy(4), ciphy(4),
812 e1000phy(4) as well as ip1000phy(4) have been converted to take
813 advantage of it. This means that these drivers now no longer take the
814 link0 parameter for selecting master mode but the master media option
815 has to be used instead, for example like in the following:
816 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
818 Selection of master mode now is also available with all other PHY
819 drivers supporting 1000baseT.
822 The TCP stack has received a significant update to add support for
823 modularised congestion control and generally improve the clarity of
824 congestion control decisions. Bump __FreeBSD_version to 900025. User
825 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
826 sockstat) need to be recompiled.
829 The man(1) utility has been replaced by a new version that no longer
830 uses /etc/manpath.config. Please consult man.conf(5) for how to
831 migrate local entries to the new format.
834 The copyright strings printed by login(1) and sshd(8) at the time of a
835 new connection have been removed to follow other operating systems and
839 A workaround for a fixed ld bug has been removed in kernel code,
840 so make sure that your system ld is built from sources after
841 revision 210245 from 2010-07-19 (r211583 if building head kernel
842 on stable/8, r211584 for stable/7; both from 2010-08-21).
843 A symptom of incorrect ld version is different addresses for
844 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
847 The $ipv6_prefer variable in rc.conf(5) has been split into
848 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
850 The $ip6addrctl_policy is a variable to choose a pre-defined
851 address selection policy set by ip6addrctl(8). A value
852 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
855 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
856 flag (see an entry of 20090926) is set on an interface with no
857 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
858 security reason. If you want IPv6 link-local address on all
859 interfaces by default, set this to "YES".
861 The old ipv6_prefer="YES" is equivalent to
862 ipv6_activate_all_interfaces="YES" and
863 ip6addrctl_policy="ipv6_prefer".
866 DTrace has grown support for userland tracing. Due to this, DTrace is
867 now i386 and amd64 only.
868 dtruss(1) is now installed by default on those systems and a new
869 kernel module is needed for userland tracing: fasttrap.
870 No changes to your kernel config file are necessary to enable
871 userland tracing, but you might consider adding 'STRIP=' and
872 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
873 to have informative userland stack traces in DTrace (ustack).
876 The acpi_aiboost(4) driver has been removed in favor of the new
877 aibs(4) driver. You should update your kernel configuration file.
880 BSD grep has been imported to the base system and it is built by
881 default. It is completely BSD licensed, highly GNU-compatible, uses
882 less memory than its GNU counterpart and has a small codebase.
883 However, it is slower than its GNU counterpart, which is mostly
884 noticeable for larger searches, for smaller ones it is measurable
885 but not significant. The reason is complex, the most important factor
886 is that we lack a modern and efficient regex library and GNU
887 overcomes this by optimizing the searches internally. Future work
888 on improving the regex performance is planned, for the meantime,
889 users that need better performance, can build GNU grep instead by
890 setting the WITH_GNU_GREP knob.
893 Due to the import of powerpc64 support, all existing powerpc kernel
894 configuration files must be updated with a machine directive like this:
895 machine powerpc powerpc
897 In addition, an updated config(8) is required to build powerpc kernels
901 A new version of ZFS (version 15) has been merged to -HEAD.
902 This version uses a python library for the following subcommands:
903 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
904 For full functionality of these commands the following port must
905 be installed: sysutils/py-zfs
908 'vm_page's are now hashed by physical address to an array of mutexes.
909 Currently this is only used to serialize access to hold_count. Over
910 time the page queue mutex will be peeled away. This changes the size
911 of pmap on every architecture. And requires all callers of vm_page_hold
912 and vm_page_unhold to be updated.
915 WITH_CTF can now be specified in src.conf (not recommended, there
916 are some problems with static executables), make.conf (would also
917 affect ports which do not use GNU make and do not override the
918 compile targets) or in the kernel config (via "makeoptions
920 When WITH_CTF was specified there before this was silently ignored,
921 so make sure that WITH_CTF is not used in places which could lead
922 to unwanted behavior.
925 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
926 to allow 32-bit compatibility on non-x86 platforms. All kernel
927 configurations on amd64 and ia64 platforms using these options must
928 be modified accordingly.
931 The utmp user accounting database has been replaced with utmpx,
932 the user accounting interface standardized by POSIX.
933 Unfortunately the semantics of utmp and utmpx don't match,
934 making it practically impossible to support both interfaces.
935 The user accounting database is used by tools like finger(1),
936 last(1), talk(1), w(1) and ac(8).
938 All applications in the base system use utmpx. This means only
939 local binaries (e.g. from the ports tree) may still use these
940 utmp database files. These applications must be rebuilt to make
943 After the system has been upgraded, it is safe to remove the old
944 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
945 assuming their contents is of no importance anymore. Old wtmp
946 databases can only be used by last(1) and ac(8) after they have
947 been converted to the new format using wtmpcvt(1).
950 Introduce the kernel thread "deadlock resolver" (which can be enabled
951 via the DEADLKRES option, see NOTES for more details) and the
952 sleepq_type() function for sleepqueues.
955 The rc.firewall and rc.firewall6 were unified, and
956 rc.firewall6 and rc.d/ip6fw were removed.
957 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
958 variables are obsoleted. Instead, the following new rc
959 variables are added to rc.d/ipfw:
961 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
962 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
963 firewall_simple_onet_ipv6, firewall_trusted_ipv6
965 The meanings correspond to the relevant IPv4 variables.
971 The default terminal emulation for syscons(4) has been changed
972 from cons25 to xterm on all platforms except pc98. This means
973 that the /etc/ttys file needs to be updated to ensure correct
974 operation of applications on the console.
976 The terminal emulation style can be toggled per window by using
977 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
978 options can be used to change the compile-time default back to
981 To prevent graphical artifacts, make sure the TERM environment
982 variable is set to match the terminal emulation that is being
983 performed by syscons(4).
986 The layout of the structure ieee80211req_scan_result has changed.
987 Applications that require wireless scan results (e.g. ifconfig(8))
988 from net80211 need to be recompiled.
990 Applications such as wpa_supplicant(8) may require a full world
991 build without using NO_CLEAN in order to get synchronized with the
995 The iwn(4) driver has been updated to support the 5000 and 5150 series.
996 There's one kernel module for each firmware. Adding "device iwnfw"
997 to the kernel configuration file means including all three firmware
998 images inside the kernel. If you want to include just the one for
999 your wireless card, use the devices iwn4965fw, iwn5000fw or
1003 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1004 into rc.d/netif. The changes are the following:
1006 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1007 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1008 Note that both variables need the "inet6" keyword at the head.
1010 Do not set $ipv6_network_interfaces manually if you do not
1011 understand what you are doing. It is not needed in most cases.
1013 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1016 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1017 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1019 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1020 all configured interfaces have "inet6 accept_rtadv" in the
1021 $ifconfig_IF_ipv6. These are for backward compatibility.
1023 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1024 functionality of interfaces with no corresponding
1025 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1026 and the default address selection policy of ip6addrctl(8)
1027 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1028 Note that if you want to configure IPv6 functionality on the
1029 disabled interfaces after boot, first you need to clear the flag by
1030 using ifconfig(8) like:
1032 ifconfig em0 inet6 -ifdisabled
1034 If YES, the default address selection policy is set as
1037 The default value of $ipv6_prefer is NO.
1039 4. If your system need to receive Router Advertisement messages,
1040 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1041 scripts automatically invoke rtsol(8) when the interface becomes
1042 UP. The Router Advertisement messages are used for SLAAC
1043 (State-Less Address AutoConfiguration).
1046 802.11s D3.03 support was committed. This is incompatible with the
1047 previous code, which was based on D3.0.
1050 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1051 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1052 control whether accepting Router Advertisement messages or not.
1053 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1054 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1055 The ifconfig(8) utility now supports these flags.
1058 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1059 mount(8) and -a option for df(1) to see them.
1062 The old tunable hw.bus.devctl_disable has been superseded by
1063 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1064 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1068 Remove the option STOP_NMI. The default action is now to use NMI only
1069 for KDB via the newly introduced function stop_cpus_hard() and
1070 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1073 The stable/8 branch created in subversion. This corresponds to the
1074 RELENG_8 branch in CVS.
1077 Bump the shared library version numbers for all libraries that do not
1078 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1079 __FreeBSD_version to 800105.
1082 Due to changes in the implementation of virtual network stack support,
1083 all network-related kernel modules must be recompiled. As this change
1084 breaks the ABI, bump __FreeBSD_version to 800104.
1087 The TOE interface to the TCP syncache has been modified to remove
1088 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1089 The cxgb driver is the only TOE consumer affected by this change, and
1090 needs to be recompiled along with the kernel. As this change breaks
1091 the ABI, bump __FreeBSD_version to 800103.
1094 Padding has been added to struct tcpcb, sackhint and tcpstat in
1095 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1096 maintaining the ABI. However, this change breaks the ABI, so bump
1097 __FreeBSD_version to 800102. User space tools that rely on the size of
1098 any of these structs (e.g. sockstat) need to be recompiled.
1101 The NFS_LEGACYRPC option has been removed along with the old kernel
1102 RPC implementation that this option selected. Kernel configurations
1103 may need to be adjusted.
1106 The network interface device nodes at /dev/net/<interface> have been
1107 removed. All ioctl operations can be performed the normal way using
1108 routing sockets. The kqueue functionality can generally be replaced
1109 with routing sockets.
1112 The documentation from the FreeBSD Documentation Project (Handbook,
1113 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1114 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1117 The ABI of various structures related to the SYSV IPC API have been
1118 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1119 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1123 Layout of struct vnet has changed as routing related variables were
1124 moved to their own Vimage module. Modules need to be recompiled. Bump
1125 __FreeBSD_version to 800099.
1128 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1129 respectively. As long as no more than 16 groups per process are used,
1130 no changes should be visible. When more than 16 groups are used, old
1131 binaries may fail if they call getgroups() or getgrouplist() with
1132 statically sized storage. Recompiling will work around this, but
1133 applications should be modified to use dynamically allocated storage
1134 for group arrays as POSIX.1-2008 does not cap an implementation's
1135 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1137 NFS and portalfs mounts may also be affected as the list of groups is
1138 truncated to 16. Users of NFS who use more than 16 groups, should
1139 take care that negative group permissions are not used on the exported
1140 file systems as they will not be reliable unless a GSSAPI based
1141 authentication method is used.
1144 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1145 option compiles in the support for adaptive spinning for lockmgrs
1146 which want to enable it. The lockinit() function now accepts the flag
1147 LK_ADAPTIVE in order to make the lock object subject to adaptive
1148 spinning when both held in write and read mode.
1151 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1152 changed. User applications that use this ioctl need to be rebuilt.
1155 The layout of struct thread has changed. Kernel and modules need to
1159 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1160 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1163 window(1) has been removed from the base system. It can now be
1164 installed from ports. The port is called misc/window.
1167 The way we are storing and accessing `routing table' entries has
1168 changed. Programs reading the FIB, like netstat, need to be
1172 A new netisr implementation has been added for FreeBSD 8. Network
1173 file system modules, such as igmp, ipdivert, and others, should be
1175 Bump __FreeBSD_version to 800096.
1178 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1182 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1183 Bump __FreeBSD_version to 800094.
1186 Add mnt_xflag field to 'struct mount'. File system modules need to be
1188 Bump __FreeBSD_version to 800093.
1191 The compiling option ADAPTIVE_SX has been retired while it has been
1192 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1193 The KPI for sx_init_flags() changes as accepting flags:
1194 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1195 been introduced in order to handle the reversed logic.
1196 Bump __FreeBSD_version to 800092.
1199 Add support for hierarchical jails. Remove global securelevel.
1200 Bump __FreeBSD_version to 800091.
1203 The layout of struct vnet_net has changed, therefore modules
1205 Bump __FreeBSD_version to 800090.
1208 The newly imported zic(8) produces a new format in the output. Please
1209 run tzsetup(8) to install the newly created data to /etc/localtime.
1212 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1213 hw.usb.* and is now consistent again with previous releases.
1216 802.11 monitor mode support was revised and driver api's were changed.
1217 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1218 of DLT_IEEE802_11. No user-visible data structures were changed but
1219 applications that use DLT_IEEE802_11 may require changes.
1220 Bump __FreeBSD_version to 800088.
1223 The layout of the following structs has changed: sysctl_oid,
1224 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1225 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1226 panics may be experienced. World rebuild is required for
1227 correctly checking networking state from userland.
1228 Bump __FreeBSD_version to 800085.
1231 MLDv2 and Source-Specific Multicast (SSM) have been merged
1232 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1233 The implementation of SSM within FreeBSD's IPv6 stack closely
1234 follows the IPv4 implementation.
1236 For kernel developers:
1238 * The most important changes are that the ip6_output() and
1239 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1240 and this lock has been downgraded to a non-recursive mutex.
1242 * As with the changes to the IPv4 stack to support SSM, filtering
1243 of inbound multicast traffic must now be performed by transport
1244 protocols within the IPv6 stack. This does not apply to TCP and
1245 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1247 * The KPIs used by IPv6 multicast are similar to those used by
1248 the IPv4 stack, with the following differences:
1249 * im6o_mc_filter() is analogous to imo_multicast_filter().
1250 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1251 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1252 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1253 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1254 for MLDv1 have an additional 'timer' argument which is used to
1255 jitter the initial membership report for the solicited-node
1256 multicast membership on-link.
1257 * This is not strictly needed for MLDv2, which already jitters
1258 its report transmissions. However, the 'timer' argument is
1259 preserved in case MLDv1 is active on the interface.
1261 * The KAME linked-list based IPv6 membership implementation has
1262 been refactored to use a vector similar to that used by the IPv4
1264 Code which maintains a list of its own multicast memberships
1265 internally, e.g. carp, has been updated to reflect the new
1268 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1269 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1270 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1271 implementation constraint which needs to be addressed in HEAD.
1273 For application developers:
1275 * The changes are broadly similar to those made for the IPv4
1278 * The use of IPv4 and IPv6 multicast socket options on the same
1279 socket, using mapped addresses, HAS NOT been tested or supported.
1281 * There are a number of issues with the implementation of various
1282 IPv6 multicast APIs which need to be resolved in the API surface
1283 before the implementation is fully compatible with KAME userland
1284 use, and these are mostly to do with interface index treatment.
1286 * The literature available discusses the use of either the delta / ASM
1287 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1288 using setsourcefilter(3)/getsourcefilter(3). For more information
1289 please refer to RFC 3768, 'Socket Interface Extensions for
1290 Multicast Source Filters'.
1292 * Applications which use the published RFC 3678 APIs should be fine.
1294 For systems administrators:
1296 * The mtest(8) utility has been refactored to support IPv6, in
1297 addition to IPv4. Interface addresses are no longer accepted
1298 as arguments, their names must be used instead. The utility
1299 will map the interface name to its first IPv4 address as
1300 returned by getifaddrs(3).
1302 * The ifmcstat(8) utility has also been updated to print the MLDv2
1303 endpoint state and source filter lists via sysctl(3).
1305 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1306 loopback of IPv6 multicast datagrams by default; it defaults to 1
1307 to preserve the existing behaviour. Disabling multicast loopback is
1308 recommended for optimal system performance.
1310 * The IPv6 MROUTING code has been changed to examine this sysctl
1311 instead of attempting to perform a group lookup before looping
1312 back forwarded datagrams.
1314 Bump __FreeBSD_version to 800084.
1317 Implement low-level Bluetooth HCI API.
1318 Bump __FreeBSD_version to 800083.
1321 The layout of struct malloc_type, used by modules to register new
1322 memory allocation types, has changed. Most modules will need to
1323 be rebuilt or panics may be experienced.
1324 Bump __FreeBSD_version to 800081.
1327 Anticipate overflowing inp_flags - add inp_flags2.
1328 This changes most offsets in inpcb, so checking v4 connection
1329 state will require a world rebuild.
1330 Bump __FreeBSD_version to 800080.
1333 Add an llentry to struct route and struct route_in6. Modules
1334 embedding a struct route will need to be recompiled.
1335 Bump __FreeBSD_version to 800079.
1338 The size of rt_metrics_lite and by extension rtentry has changed.
1339 Networking administration apps will need to be recompiled.
1340 The route command now supports show as an alias for get, weighting
1341 of routes, sticky and nostick flags to alter the behavior of stateful
1343 Bump __FreeBSD_version to 800078.
1346 Do not use Giant for kbdmux(4) locking. This is wrong and
1347 apparently causing more problems than it solves. This will
1348 re-open the issue where interrupt handlers may race with
1349 kbdmux(4) in polling mode. Typical symptoms include (but
1350 not limited to) duplicated and/or missing characters when
1351 low level console functions (such as gets) are used while
1352 interrupts are enabled (for example geli password prompt,
1353 mountroot prompt etc.). Disabling kbdmux(4) may help.
1356 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1357 kernel modules referencing any of the above need to be recompiled.
1358 Bump __FreeBSD_version to 800075.
1361 GEOM_PART has become the default partition slicer for storage devices,
1362 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1363 introduces some changes:
1365 MSDOS/EBR: the devices created from MSDOS extended partition entries
1366 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1367 to devices with offset-based names. fstabs may need to be modified.
1369 BSD: the "geometry does not match label" warning is harmless in most
1370 cases but it points to problems in file system misalignment with
1371 disk geometry. The "c" partition is now implicit, covers the whole
1372 top-level drive and cannot be (mis)used by users.
1374 General: Kernel dumps are now not allowed to be written to devices
1375 whose partition types indicate they are meant to be used for file
1376 systems (or, in case of MSDOS partitions, as something else than
1379 Most of these changes date approximately from 200812.
1382 The uscanner(4) driver has been removed from the kernel. This follows
1383 Linux removing theirs in 2.6 and making libusb the default interface
1384 (supported by sane).
1387 The multicast forwarding code has been cleaned up. netstat(1)
1388 only relies on KVM now for printing bandwidth upcall meters.
1389 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1390 ip6_mroute_mod respectively. The config(5) options for statically
1391 compiling this code remain the same, i.e. 'options MROUTING'.
1394 Support for the IFF_NEEDSGIANT network interface flag has been
1395 removed, which means that non-MPSAFE network device drivers are no
1396 longer supported. In particular, if_ar, if_sr, and network device
1397 drivers from the old (legacy) USB stack can no longer be built or
1401 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1402 a bunch of new language catalog files have also been added.
1403 This means that some common libc messages are now localized and
1404 they depend on the LC_MESSAGES environmental variable.
1407 The k8temp(4) driver has been renamed to amdtemp(4) since
1408 support for Family 10 and Family 11 CPU families was added.
1411 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1412 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1414 For kernel developers, the most important changes are that the
1415 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1416 and this lock has been downgraded to a non-recursive mutex.
1418 Transport protocols (UDP, Raw IP) are now responsible for filtering
1419 inbound multicast traffic according to group membership and source
1420 filters. The imo_multicast_filter() KPI exists for this purpose.
1421 Transports which do not use multicast (SCTP, TCP) already reject
1422 multicast by default. Forwarding and receive performance may improve
1423 as a mutex acquisition is no longer needed in the ip_input()
1424 low-level input path. in_addmulti() and in_delmulti() are shimmed
1425 to new KPIs which exist to support SSM in-kernel.
1427 For application developers, it is recommended that loopback of
1428 multicast datagrams be disabled for best performance, as this
1429 will still cause the lock to be taken for each looped-back
1430 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1431 be tuned to 0 to disable loopback by default; it defaults to 1
1432 to preserve the existing behaviour.
1434 For systems administrators, to obtain best performance with
1435 multicast reception and multiple groups, it is always recommended
1436 that a card with a suitably precise hash filter is used. Hash
1437 collisions will still result in the lock being taken within the
1438 transport protocol input path to check group membership.
1440 If deploying FreeBSD in an environment with IGMP snooping switches,
1441 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1442 enabled; this forces 224.0.0.0/24 group membership to be announced
1445 The size of 'struct igmpstat' has changed; netstat needs to be
1446 recompiled to reflect this.
1447 Bump __FreeBSD_version to 800070.
1450 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1451 updated to use it. This requires a buildworld/installworld in order to
1452 update the library and dependencies (usbconfig, etc). Its advisable to
1453 rebuild all ports which uses libusb. More specific directions are given
1454 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1455 libusb are no longer required and can be removed.
1458 A workaround is committed to allow the creation of System V shared
1459 memory segment of size > 2 GB on the 64-bit architectures.
1460 Due to a limitation of the existing ABI, the shm_segsz member
1461 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1462 wrong for large segments. Note that limits must be explicitly
1463 raised to allow such segments to be created.
1466 The layout of struct ifnet has changed, requiring a rebuild of all
1467 network device driver modules.
1470 The /dev handling for the new USB stack has changed, a
1471 buildworld/installworld is required for libusb20.
1474 The new USB2 stack has now been permanently moved in and all kernel and
1475 module names reverted to their previous values (eg, usb, ehci, ohci,
1476 ums, ...). The old usb stack can be compiled in by prefixing the name
1477 with the letter 'o', the old usb modules have been removed.
1478 Updating entry 20090216 for xorg and 20090215 for libmap may still
1482 The rc.conf(5) option if_up_delay has been renamed to
1483 defaultroute_delay to better reflect its purpose. If you have
1484 customized this setting in /etc/rc.conf you need to update it to
1488 xorg 7.4 wants to configure its input devices via hald which does not
1489 yet work with USB2. If the keyboard/mouse does not work in xorg then
1491 Option "AllowEmptyInput" "off"
1492 to your ServerLayout section. This will cause X to use the configured
1493 kbd and mouse sections from your xorg.conf.
1496 The GENERIC kernels for all architectures now default to the new USB2
1497 stack. No kernel config options or code have been removed so if a
1498 problem arises please report it and optionally revert to the old USB
1499 stack. If you are loading USB kernel modules or have a custom kernel
1500 that includes GENERIC then ensure that usb names are also changed over,
1501 eg uftdi -> usb2_serial_ftdi.
1503 Older programs linked against the ports libusb 0.1 need to be
1504 redirected to the new stack's libusb20. /etc/libmap.conf can
1506 # Map old usb library to new one for usb2 stack
1507 libusb-0.1.so.8 libusb20.so.1
1510 All USB ethernet devices now attach as interfaces under the name ueN
1511 (eg. ue0). This is to provide a predictable name as vendors often
1512 change usb chipsets in a product without notice.
1515 The ichsmb(4) driver has been changed to require SMBus slave
1516 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1517 All of the other SMBus controller drivers require left-justified
1518 slave addresses, so this change makes all the drivers provide the
1522 INET6 statistics (struct ip6stat) was updated.
1523 netstat(1) needs to be recompiled.
1526 NTFS has been removed from GENERIC kernel on amd64 to match
1527 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1528 will load ntfs.ko module automatically when NTFS support is
1529 actually needed, unless ntfs.ko is not installed or security
1530 level prohibits loading kernel modules. If either is the case,
1531 "options NTFS" has to be added into kernel config.
1534 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1535 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1536 800061. User space tools that rely on the size of struct tcpcb in
1537 tcp_var.h (e.g. sockstat) need to be recompiled.
1540 ng_tty(4) module updated to match the new TTY subsystem.
1541 Due to API change, user-level applications must be updated.
1542 New API support added to mpd5 CVS and expected to be present
1543 in next mpd5.3 release.
1546 With __FreeBSD_version 800060 the makefs tool is part of
1547 the base system (it was a port).
1550 The afdata and ifnet locks have been changed from mutexes to
1551 rwlocks, network modules will need to be re-compiled.
1554 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1555 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1556 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1557 architecture and 40 bytes on 64-bit architecture. The userland
1558 applications "arp" and "ndp" have been updated accordingly.
1559 The output from "netstat -r" shows only routing entries and
1560 none of the L2 information.
1563 __FreeBSD_version 800057 marks the switchover from the
1564 binary ath hal to source code. Users must add the line:
1566 options AH_SUPPORT_AR5416
1568 to their kernel config files when specifying:
1572 The ath_hal module no longer exists; the code is now compiled
1573 together with the driver in the ath module. It is now
1574 possible to tailor chip support (i.e. reduce the set of chips
1575 and thereby the code size); consult ath_hal(4) for details.
1578 __FreeBSD_version 800054 adds memory barriers to
1579 <machine/atomic.h>, new interfaces to ifnet to facilitate
1580 multiple hardware transmit queues for cards that support
1581 them, and a lock-less ring-buffer implementation to
1582 enable drivers to more efficiently manage queueing of
1586 A new version of ZFS (version 13) has been merged to -HEAD.
1587 This version has zpool attribute "listsnapshots" off by
1588 default, which means "zfs list" does not show snapshots,
1589 and is the same as Solaris behavior.
1592 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1595 The uhci, ohci, ehci and slhci USB Host controller drivers have
1596 been put into separate modules. If you load the usb module
1597 separately through loader.conf you will need to load the
1598 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1599 controller add the following to loader.conf:
1605 The ABI used by the PMC toolset has changed. Please keep
1606 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1610 atapci kernel module now includes only generic PCI ATA
1611 driver. AHCI driver moved to ataahci kernel module.
1612 All vendor-specific code moved into separate kernel modules:
1613 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1614 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1615 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1616 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1619 The TTY subsystem of the kernel has been replaced by a new
1620 implementation, which provides better scalability and an
1621 improved driver model. Most common drivers have been migrated to
1622 the new TTY subsystem, while others have not. The following
1623 drivers have not yet been ported to the new TTY layer:
1626 cy, digi, rc, rp, sio
1632 ng_h4, ng_tty, ppp, sl, snp
1634 Adding these drivers to your kernel configuration file shall
1635 cause compilation to fail.
1638 ntpd has been upgraded to 4.2.4p5.
1641 OpenSSH has been upgraded to 5.1p1.
1643 For many years, FreeBSD's version of OpenSSH preferred DSA
1644 over RSA for host and user authentication keys. With this
1645 upgrade, we've switched to the vendor's default of RSA over
1646 DSA. This may cause upgraded clients to warn about unknown
1647 host keys even for previously known hosts. Users should
1648 follow the usual procedure for verifying host keys before
1649 accepting the RSA key.
1651 This can be circumvented by setting the "HostKeyAlgorithms"
1652 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1655 Please note that the sequence of keys offered for
1656 authentication has been changed as well. You may want to
1657 specify IdentityFile in a different order to revert this
1661 The sio(4) driver has been removed from the i386 and amd64
1662 kernel configuration files. This means uart(4) is now the
1663 default serial port driver on those platforms as well.
1665 To prevent collisions with the sio(4) driver, the uart(4) driver
1666 uses different names for its device nodes. This means the
1667 onboard serial port will now most likely be called "ttyu0"
1668 instead of "ttyd0". You may need to reconfigure applications to
1669 use the new device names.
1671 When using the serial port as a boot console, be sure to update
1672 /boot/device.hints and /etc/ttys before booting the new kernel.
1673 If you forget to do so, you can still manually specify the hints
1674 at the loader prompt:
1676 set hint.uart.0.at="isa"
1677 set hint.uart.0.port="0x3F8"
1678 set hint.uart.0.flags="0x10"
1679 set hint.uart.0.irq="4"
1683 The gpt(8) utility has been removed. Use gpart(8) to partition
1687 The version that Linuxulator emulates was changed from 2.4.2
1688 to 2.6.16. If you experience any problems with Linux binaries
1689 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1690 if it fixes the problem contact emulation mailing list.
1693 ISDN4BSD (I4B) was removed from the src tree. You may need to
1694 update a your kernel configuration and remove relevant entries.
1697 I have checked in code to support multiple routing tables.
1698 See the man pages setfib(1) and setfib(2).
1699 This is a hopefully backwards compatible version,
1700 but to make use of it you need to compile your kernel
1701 with options ROUTETABLES=2 (or more up to 16).
1704 The 802.11 wireless support was redone to enable multi-bss
1705 operation on devices that are capable. The underlying device
1706 is no longer used directly but instead wlanX devices are
1707 cloned with ifconfig. This requires changes to rc.conf files.
1708 For example, change:
1709 ifconfig_ath0="WPA DHCP"
1712 ifconfig_wlan0="WPA DHCP"
1713 see rc.conf(5) for more details. In addition, mergemaster of
1714 /etc/rc.d is highly recommended. Simultaneous update of userland
1715 and kernel wouldn't hurt either.
1717 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1718 modules were merged into the base wlan module. All references
1719 to these modules (e.g. in kernel config files) must be removed.
1722 psm(4) has gained write(2) support in native operation level.
1723 Arbitrary commands can be written to /dev/psm%d and status can
1724 be read back from it. Therefore, an application is responsible
1725 for status validation and error recovery. It is a no-op in
1726 other operation levels.
1729 Support for KSE threading has been removed from the kernel. To
1730 run legacy applications linked against KSE libmap.conf may
1731 be used. The following libmap.conf may be used to ensure
1732 compatibility with any prior release:
1734 libpthread.so.1 libthr.so.1
1735 libpthread.so.2 libthr.so.2
1736 libkse.so.3 libthr.so.3
1739 The layout of struct vmspace has changed. This affects libkvm
1740 and any executables that link against libkvm and use the
1741 kvm_getprocs() function. In particular, but not exclusively,
1742 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1743 The effects are minimal, but it's advisable to upgrade world
1747 The latest em driver no longer has support in it for the
1748 82575 adapter, this is now moved to the igb driver. The
1749 split was done to make new features that are incompatible
1750 with older hardware easier to do.
1753 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1754 likewise the kernel option is now GEOM_LINUX_LVM.
1757 The default NFS mount mode has changed from UDP to TCP for
1758 increased reliability. If you rely on (insecurely) NFS
1759 mounting across a firewall you may need to update your
1763 Belatedly note the addition of m_collapse for compacting
1767 The fts(3) structures have been changed to use adequate
1768 integer types for their members and so to be able to cope
1769 with huge file trees. The old fts(3) ABI is preserved
1770 through symbol versioning in libc, so third-party binaries
1771 using fts(3) should still work, although they will not take
1772 advantage of the extended types. At the same time, some
1773 third-party software might fail to build after this change
1774 due to unportable assumptions made in its source code about
1775 fts(3) structure members. Such software should be fixed
1776 by its vendor or, in the worst case, in the ports tree.
1777 FreeBSD_version 800015 marks this change for the unlikely
1778 case that a portable fix is impossible.
1781 To upgrade to -current after this date, you must be running
1782 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1783 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1786 The ADAPTIVE_GIANT kernel option has been retired because its
1787 functionality is the default now.
1790 The AT keyboard emulation of sunkbd(4) has been turned on
1791 by default. In order to make the special symbols of the Sun
1792 keyboards driven by sunkbd(4) work under X these now have
1793 to be configured the same way as Sun USB keyboards driven
1794 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1796 Option "XkbLayout" "us"
1797 Option "XkbRules" "xorg"
1798 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1801 It has been decided that it is desirable to provide ABI
1802 backwards compatibility to the FreeBSD 4/5/6 versions of the
1803 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1804 broken with the introduction of PCI domain support (see the
1805 20070930 entry). Unfortunately, this required the ABI of
1806 PCIOCGETCONF to be broken again in order to be able to
1807 provide backwards compatibility to the old version of that
1808 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1809 again. As for prominent ports this affects neither pciutils
1810 nor xorg-server this time, the hal port needs to be rebuilt
1814 The misnamed kthread_create() and friends have been renamed
1815 to kproc_create() etc. Many of the callers already
1816 used kproc_start()..
1817 I will return kthread_create() and friends in a while
1818 with implementations that actually create threads, not procs.
1819 Renaming corresponds with version 800002.
1828 Avoid using make -j when upgrading. While generally safe, there are
1829 sometimes problems using -j to upgrade. If your upgrade fails with
1830 -j, please try again without -j. From time to time in the past there
1831 have been problems using -j with buildworld and/or installworld. This
1832 is especially true when upgrading between "distant" versions (eg one
1833 that cross a major release boundary or several minor releases, or when
1834 several months have passed on the -current branch).
1836 Sometimes, obscure build problems are the result of environment
1837 poisoning. This can happen because the make utility reads its
1838 environment when searching for values for global variables. To run
1839 your build attempts in an "environmental clean room", prefix all make
1840 commands with 'env -i '. See the env(1) manual page for more details.
1842 When upgrading from one major version to another it is generally best
1843 to upgrade to the latest code in the currently installed branch first,
1844 then do an upgrade to the new branch. This is the best-tested upgrade
1845 path, and has the highest probability of being successful. Please try
1846 this approach before reporting problems with a major version upgrade.
1848 When upgrading a live system, having a root shell around before
1849 installing anything can help undo problems. Not having a root shell
1850 around can lead to problems if pam has changed too much from your
1851 starting point to allow continued authentication after the upgrade.
1855 When upgrading the boot ZFS pool to a new version, always follow
1858 1.) recompile and reinstall the ZFS boot loader and boot block
1859 (this is part of "make buildworld" and "make installworld")
1861 2.) update the ZFS boot block on your boot drive
1863 The following example updates the ZFS boot block on the first
1864 partition (freebsd-boot) of a GPT partitioned drive ad0:
1865 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1867 Non-boot pools do not need these updates.
1871 If you are updating from a prior version of FreeBSD (even one just
1872 a few days old), you should follow this procedure. It is the most
1873 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1875 make kernel-toolchain
1876 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1877 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1879 To test a kernel once
1880 ---------------------
1881 If you just want to boot a kernel once (because you are not sure
1882 if it works, or if you want to boot a known bad kernel to provide
1883 debugging information) run
1884 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1885 nextboot -k testkernel
1887 To just build a kernel when you know that it won't mess you up
1888 --------------------------------------------------------------
1889 This assumes you are already running a CURRENT system. Replace
1890 ${arch} with the architecture of your machine (e.g. "i386",
1891 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1893 cd src/sys/${arch}/conf
1894 config KERNEL_NAME_HERE
1895 cd ../compile/KERNEL_NAME_HERE
1900 If this fails, go to the "To build a kernel" section.
1902 To rebuild everything and install it on the current system.
1903 -----------------------------------------------------------
1904 # Note: sometimes if you are running current you gotta do more than
1905 # is listed here if you are upgrading from a really old current.
1907 <make sure you have good level 0 dumps>
1909 make kernel KERNCONF=YOUR_KERNEL_HERE
1911 <reboot in single user> [3]
1918 To cross-install current onto a separate partition
1919 --------------------------------------------------
1920 # In this approach we use a separate partition to hold
1921 # current's root, 'usr', and 'var' directories. A partition
1922 # holding "/", "/usr" and "/var" should be about 2GB in
1925 <make sure you have good level 0 dumps>
1928 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1929 <maybe newfs current's root partition>
1930 <mount current's root partition on directory ${CURRENT_ROOT}>
1931 make installworld DESTDIR=${CURRENT_ROOT}
1932 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1933 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1934 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1935 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1936 <reboot into current>
1937 <do a "native" rebuild/install as described in the previous section>
1938 <maybe install compatibility libraries from ports/misc/compat*>
1942 To upgrade in-place from stable to current
1943 ----------------------------------------------
1944 <make sure you have good level 0 dumps>
1946 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1948 <reboot in single user> [3]
1955 Make sure that you've read the UPDATING file to understand the
1956 tweaks to various things you need. At this point in the life
1957 cycle of current, things change often and you are on your own
1958 to cope. The defaults can also change, so please read ALL of
1959 the UPDATING entries.
1961 Also, if you are tracking -current, you must be subscribed to
1962 freebsd-current@freebsd.org. Make sure that before you update
1963 your sources that you have read and understood all the recent
1964 messages there. If in doubt, please track -stable which has
1965 much fewer pitfalls.
1967 [1] If you have third party modules, such as vmware, you
1968 should disable them at this point so they don't crash your
1971 [3] From the bootblocks, boot -s, and then do
1976 adjkerntz -i # if CMOS is wall time
1977 Also, when doing a major release upgrade, it is required that
1978 you boot into single user mode to do the installworld.
1980 [4] Note: This step is non-optional. Failure to do this step
1981 can result in a significant reduction in the functionality of the
1982 system. Attempting to do it by hand is not recommended and those
1983 that pursue this avenue should read this file carefully, as well
1984 as the archives of freebsd-current and freebsd-hackers mailing lists
1985 for potential gotchas. The -U option is also useful to consider.
1986 See mergemaster(8) for more information.
1988 [5] Usually this step is a noop. However, from time to time
1989 you may need to do this if you get unknown user in the following
1990 step. It never hurts to do it all the time. You may need to
1991 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1992 install) after the buildworld before this step if you last updated
1993 from current before 20130425 or from -stable before 20130430.
1995 [6] This only deletes old files and directories. Old libraries
1996 can be deleted by "make delete-old-libs", but you have to make
1997 sure that no program is using those libraries anymore.
1999 [8] In order to have a kernel that can run the 4.x binaries needed to
2000 do an installworld, you must include the COMPAT_FREEBSD4 option in
2001 your kernel. Failure to do so may leave you with a system that is
2002 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2003 required to run the 5.x binaries on more recent kernels. And so on
2004 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2006 Make sure that you merge any new devices from GENERIC since the
2007 last time you updated your kernel config file.
2009 [9] When checking out sources, you must include the -P flag to have
2010 cvs prune empty directories.
2012 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2013 "?=" instead of the "=" assignment operator, so that buildworld can
2014 override the CPUTYPE if it needs to.
2016 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2017 not on the command line, or in /etc/make.conf. buildworld will
2018 warn if it is improperly defined.
2021 This file contains a list, in reverse chronological order, of major
2022 breakages in tracking -current. It is not guaranteed to be a complete
2023 list of such breakages, and only contains entries since October 10, 2007.
2024 If you need to see UPDATING entries from before that date, you will need
2025 to fetch an UPDATING file from an older FreeBSD release.
2027 Copyright information:
2029 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2031 Redistribution, publication, translation and use, with or without
2032 modification, in full or in part, in any form or format of this
2033 document are permitted without further permission from the author.
2035 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2036 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2037 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2038 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2039 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2040 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2041 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2042 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2043 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2044 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2045 POSSIBILITY OF SUCH DAMAGE.
2047 Contact Warner Losh if you have any questions about your use of