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.
23 The behavior of gss_pseudo_random() for the krb5 mechanism
24 has changed, for applications requesting a longer random string
25 than produced by the underlying enctype's pseudo-random() function.
26 In particular, the random string produced from a session key of
27 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
28 be different at the 17th octet and later, after this change.
29 The counter used in the PRF+ construction is now encoded as a
30 big-endian integer in accordance with RFC 4402.
31 __FreeBSD_version is bumped to 1000701.
34 The WITHOUT_ATF build knob has been removed and its functionality
35 has been subsumed into the more generic WITHOUT_TESTS. If you were
36 using the former to disable the build of the ATF libraries, you
37 should change your settings to use the latter.
40 The default version of mtree is nmtree which is obtained from
41 NetBSD. The output is generally the same, but may vary
42 slightly. If you found you need identical output adding
43 "-F freebsd9" to the command line should do the trick. For the
44 time being, the old mtree is available as fmtree.
47 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
48 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
49 1.1.4_8 and verify bsdyml not linked in, before running "make
51 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
53 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
56 The rc.d/jail script has been updated to support jail(8)
57 configuration file. The "jail_<jname>_*" rc.conf(5) variables
58 for per-jail configuration are automatically converted to
59 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
60 This is transparently backward compatible. See below about some
61 incompatibilities and rc.conf(5) manual page for more details.
63 These variables are now deprecated in favor of jail(8) configuration
64 file. One can use "rc.d/jail config <jname>" command to generate
65 a jail(8) configuration file in /var/run/jail.<jname>.conf without
66 running the jail(8) utility. The default pathname of the
67 configuration file is /etc/jail.conf and can be specified by
68 using $jail_conf or $jail_<jname>_conf variables.
70 Please note that jail_devfs_ruleset accepts an integer at
71 this moment. Please consider to rewrite the ruleset name
75 BIND has been removed from the base system. If all you need
76 is a local resolver, simply enable and start the local_unbound
77 service instead. Otherwise, several versions of BIND are
78 available in the ports tree. The dns/bind99 port is one example.
80 With this change, nslookup(1) and dig(1) are no longer in the base
81 system. Users should instead use host(1) and drill(1) which are
82 in the base system. Alternatively, nslookup and dig can
83 be obtained by installing the dns/bind-tools port.
86 With the addition of unbound(8), a new unbound user is now
87 required during installworld. "mergemaster -p" can be used to
88 add the user prior to installworld, as documented in the handbook.
91 OpenSSH is now built with DNSSEC support, and will by default
92 silently trust signed SSHFP records. This can be controlled with
93 the VerifyHostKeyDNS client configuration setting. DNSSEC support
94 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
97 The GNU Compiler Collection and C++ standard library (libstdc++)
98 are no longer built by default on platforms where clang is the system
99 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
103 The PROCDESC kernel option is now part of the GENERIC kernel
104 configuration and is required for the rwhod(8) to work.
105 If you are using custom kernel configuration, you should include
109 The API and ABI related to the Capsicum framework was modified
110 in backward incompatible way. The userland libraries and programs
111 have to be recompiled to work with the new kernel. This includes the
112 following libraries and programs, but the whole buildworld is
113 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
114 kdump, procstat, rwho, rwhod, uniq.
117 AES-NI intrinsic support has been added to gcc. The AES-NI module
118 has been updated to use this support. A new gcc is required to build
119 the aesni module on both i386 and amd64.
122 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
123 Thus "device padlock_rng" and "device rdrand_rng" should be
124 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
127 WITH_ICONV has been split into two feature sets. WITH_ICONV now
128 enables just the iconv* functionality and is now on by default.
129 WITH_LIBICONV_COMPAT enables the libiconv api and link time
130 compatability. Set WITHOUT_ICONV to build the old way.
131 If you have been using WITH_ICONV before, you will very likely
132 need to turn on WITH_LIBICONV_COMPAT.
135 INVARIANTS option now enables DEBUG for code with OpenSolaris and
136 Illumos origin, including ZFS. If you have INVARIANTS in your
137 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
139 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
140 locks if WITNESS option was set. Because that generated a lot of
141 witness(9) reports and all of them were believed to be false
142 positives, this is no longer done. New option OPENSOLARIS_WITNESS
143 can be used to achieve the previous behavior.
146 Timer values in IPv6 data structures now use time_uptime instead
147 of time_second. Although this is not a user-visible functional
148 change, userland utilities which directly use them---ndp(8),
149 rtadvd(8), and rtsold(8) in the base system---need to be updated
153 find -delete can now delete the pathnames given as arguments,
154 instead of only files found below them or if the pathname did
155 not contain any slashes. Formerly, the following error message
158 find: -delete: <path>: relative path potentially not safe
160 Deleting the pathnames given as arguments can be prevented
161 without error messages using -mindepth 1 or by changing
162 directory and passing "." as argument to find. This works in the
163 old as well as the new version of find.
166 Behavior of devfs rules path matching has been changed.
167 Pattern is now always matched against fully qualified devfs
168 path and slash characters must be explicitly matched by
169 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
170 subdirectories must be reviewed.
173 The default ARM ABI has changed to the ARM EABI. The old ABI is
174 incompatible with the ARM EABI and all programs and modules will
175 need to be rebuilt to work with a new kernel.
177 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
179 NOTE: Support for the old ABI will be removed in the future and
180 users are advised to upgrade.
183 pkg_install has been disconnected from the build if you really need it
184 you should add WITH_PKGTOOLS in your src.conf(5).
187 Most of network statistics structures were changed to be able
188 keep 64-bits counters. Thus all tools, that work with networking
189 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
192 Fix targets that run multiple make's to use && rather than ;
193 so that subsequent steps depend on success of previous.
195 NOTE: if building 'universe' with -j* on stable/8 or stable/9
196 it would be better to start the build using bmake, to avoid
197 overloading the machine.
200 Fix a bug that allowed a tracing process (e.g. gdb) to write
201 to a memory-mapped file in the traced process's address space
202 even if neither the traced process nor the tracing process had
203 write access to that file.
206 CVS has been removed from the base system. An exact copy
207 of the code is available from the devel/cvs port.
210 Some people report the following error after the switch to bmake:
212 make: illegal option -- J
213 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
215 *** [buildworld] Error code 2
217 this likely due to an old instance of make in
218 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
219 which src/Makefile will use that blindly, if it exists, so if
220 you see the above error:
222 rm -rf `make -V MAKEPATH`
227 Use bmake by default.
228 Whereas before one could choose to build with bmake via
229 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
230 make. The goal is to remove these knobs for 10-RELEASE.
232 It is worth noting that bmake (like gmake) treats the command
233 line as the unit of failure, rather than statements within the
234 command line. Thus '(cd some/where && dosomething)' is safer
235 than 'cd some/where; dosomething'. The '()' allows consistent
236 behavior in parallel build.
239 Fix a bug that allows NFS clients to issue READDIR on files.
242 The WITHOUT_IDEA option has been removed because
243 the IDEA patent expired.
246 The sysctl which controls TRIM support under ZFS has been renamed
247 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
251 The mergemaster command now uses the default MAKEOBJDIRPREFIX
252 rather than creating it's own in the temporary directory in
253 order allow access to bootstrapped versions of tools such as
254 install and mtree. When upgrading from version of FreeBSD where
255 the install command does not support -l, you will need to
256 install a new mergemaster command if mergemaster -p is required.
257 This can be accomplished with the command (cd src/usr.sbin/mergemaster
261 Legacy ATA stack, disabled and replaced by new CAM-based one since
262 FreeBSD 9.0, completely removed from the sources. Kernel modules
263 atadisk and atapi*, user-level tools atacontrol and burncd are
264 removed. Kernel option `options ATA_CAM` is now permanently enabled
268 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
269 and socketpair(2). Software, in particular Kerberos, may
270 automatically detect and use these during building. The resulting
271 binaries will not work on older kernels.
274 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
275 information, see the respective 20130304 entry).
278 Recent commits to callout(9) changed the size of struct callout,
279 so the KBI is probably heavily disturbed. Also, some functions
280 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
281 by macros. Every kernel module using it won't load, so rebuild
284 The ctl device has been re-enabled in GENERIC for i386 and amd64,
285 but does not initialize by default (because of the new CTL_DISABLE
286 option) to save memory. To re-enable it, remove the CTL_DISABLE
287 option from the kernel config file or set kern.cam.ctl.disable=0
288 in /boot/loader.conf.
291 The ctl device has been disabled in GENERIC for i386 and amd64.
292 This was done due to the extra memory being allocated at system
293 initialisation time by the ctl driver which was only used if
294 a CAM target device was created. This makes a FreeBSD system
295 unusable on 128MB or less of RAM.
298 A new compression method (lz4) has been merged to -HEAD. Please
299 refer to zpool-features(7) for more information.
301 Please refer to the "ZFS notes" section of this file for information
302 on upgrading boot ZFS pools.
305 A BSD-licensed patch(1) variant has been added and is installed
306 as bsdpatch, being the GNU version the default patch.
307 To inverse the logic and use the BSD-licensed one as default,
308 while having the GNU version installed as gnupatch, rebuild
309 and install world with the WITH_BSD_PATCH knob set.
312 Due to the use of the new -l option to install(1) during build
313 and install, you must take care not to directly set the INSTALL
314 make variable in your /etc/make.conf, /etc/src.conf, or on the
315 command line. If you wish to use the -C flag for all installs
316 you may be able to add INSTALL+=-C to /etc/make.conf or
320 The install(1) option -M has changed meaning and now takes an
321 argument that is a file or path to append logs to. In the
322 unlikely event that -M was the last option on the command line
323 and the command line contained at least two files and a target
324 directory the first file will have logs appended to it. The -M
325 option served little practical purpose in the last decade so its
326 use is expected to be extremely rare.
329 After switching to Clang as the default compiler some users of ZFS
330 on i386 systems started to experience stack overflow kernel panics.
331 Please consider using 'options KSTACK_PAGES=4' in such configurations.
334 GEOM_LABEL now mangles label names read from file system metadata.
335 Mangling affect labels containing spaces, non-printable characters,
336 '%' or '"'. Device names in /etc/fstab and other places may need to
340 By default, only the 10 most recent kernel dumps will be saved. To
341 restore the previous behaviour (no limit on the number of kernel dumps
342 stored in the dump directory) add the following line to /etc/rc.conf:
347 With the addition of auditdistd(8), a new auditdistd user is now
348 required during installworld. "mergemaster -p" can be used to
349 add the user prior to installworld, as documented in the handbook.
352 The sin6_scope_id member variable in struct sockaddr_in6 is now
353 filled by the kernel before passing the structure to the userland via
354 sysctl or routing socket. This means the KAME-specific embedded scope
355 id in sin6_addr.s6_addr[2] is always cleared in userland application.
356 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
357 __FreeBSD_version is bumped to 1000025.
360 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
361 This means that the world and kernel will be compiled with clang
362 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
363 and /usr/bin/cpp. To disable this behavior and revert to building
364 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
365 of current may need to bootstrap WITHOUT_CLANG first if the clang
366 build fails (its compatibility window doesn't extend to the 9 stable
370 The IPFIREWALL_FORWARD kernel option has been removed. Its
371 functionality now turned on by default.
374 The ZERO_COPY_SOCKET kernel option has been removed and
375 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
376 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
377 mechanism which is not safe and may result in kernel crashes.
378 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
379 driver supports disposeable external page sized mbuf storage.
380 Proper replacements for both zero-copy mechanisms are under
381 consideration and will eventually lead to complete removal
382 of the two kernel options.
385 The IPv4 network stack has been converted to network byte
386 order. The following modules need to be recompiled together
387 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
388 pf(4), ipfw(4), ng_ipfw(4), stf(4).
391 Support for non-MPSAFE filesystems was removed from VFS. The
392 VFS_VERSION was bumped, all filesystem modules shall be
396 All the non-MPSAFE filesystems have been disconnected from
397 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
398 portalfs, smbfs, xfs.
401 The interface cloning API and ABI has changed. The following
402 modules need to be recompiled together with kernel:
403 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
404 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
405 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
408 The sdhci driver was split in two parts: sdhci (generic SD Host
409 Controller logic) and sdhci_pci (actual hardware driver).
410 No kernel config modifications are required, but if you
411 load sdhc as a module you must switch to sdhci_pci instead.
414 Import the FUSE kernel and userland support into base system.
417 The GNU sort(1) program has been removed since the BSD-licensed
418 sort(1) has been the default for quite some time and no serious
419 problems have been reported. The corresponding WITH_GNU_SORT
423 The pfil(9) API/ABI for AF_INET family has been changed. Packet
424 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
428 The net80211(4) ABI has been changed to allow for improved driver
429 PS-POLL and power-save support. All wireless drivers need to be
430 recompiled to work with the new kernel.
433 The random(4) support for the VIA hardware random number
434 generator (`PADLOCK') is no longer enabled unconditionally.
435 Add the padlock_rng device in the custom kernel config if
436 needed. The GENERIC kernels on i386 and amd64 do include the
437 device, so the change only affects the custom kernel
441 The pf(4) packet filter ABI has been changed. pfctl(8) and
442 snmp_pf module need to be recompiled to work with new kernel.
445 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
446 to -HEAD. Pools that have empty_bpobj in active state can not be
447 imported read-write with ZFS implementations that do not support
448 this feature. For more information read the zpool-features(5)
452 The sparc64 ZFS loader has been changed to no longer try to auto-
453 detect ZFS providers based on diskN aliases but now requires these
454 to be explicitly listed in the OFW boot-device environment variable.
457 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
458 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
459 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
462 The following sysctls and tunables have been renamed for consistency
463 with other variables:
464 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
465 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
468 The sort utility has been replaced with BSD sort. For now, GNU sort
469 is also available as "gnusort" or the default can be set back to
470 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
471 installed as "bsdsort".
474 A new version of ZFS (pool version 5000) has been merged to -HEAD.
475 Starting with this version the old system of ZFS pool versioning
476 is superseded by "feature flags". This concept enables forward
477 compatibility against certain future changes in functionality of ZFS
478 pools. The first read-only compatible "feature flag" for ZFS pools
479 is named "com.delphix:async_destroy". For more information
480 read the new zpool-features(5) manual page.
481 Please refer to the "ZFS notes" section of this file for information
482 on upgrading boot ZFS pools.
485 The malloc(3) implementation embedded in libc now uses sources imported
486 as contrib/jemalloc. The most disruptive API change is to
487 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
488 delete it prior to installworld, and optionally re-create it using the
489 new format after rebooting. See malloc.conf(5) for details
490 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
494 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
495 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
496 now spelled mips. This is to aid compatibility with third-party
497 software that expects this naming scheme in uname(3). Little-endian
498 settings are unchanged. If you are updating a big-endian mips64 machine
499 from before this change, you may need to set MACHINE_ARCH=mips64 in
500 your environment before the new build system will recognize your machine.
503 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
507 Now unix domain sockets behave "as expected" on nullfs(5). Previously
508 nullfs(5) did not pass through all behaviours to the underlying layer,
509 as a result if we bound to a socket on the lower layer we could connect
510 only to the lower path; if we bound to the upper layer we could connect
511 only to the upper path. The new behavior is one can connect to both the
512 lower and the upper paths regardless what layer path one binds to.
515 The getifaddrs upgrade path broken with 20111215 has been restored.
516 If you have upgraded in between 20111215 and 20120209 you need to
517 recompile libc again with your kernel. You still need to recompile
518 world to be able to configure CARP but this restriction already
522 The set_rcvar() function has been removed from /etc/rc.subr. All
523 base and ports rc.d scripts have been updated, so if you have a
524 port installed with a script in /usr/local/etc/rc.d you can either
525 hand-edit the rcvar= line, or reinstall the port.
527 An easy way to handle the mass-update of /etc/rc.d:
528 rm /etc/rc.d/* && mergemaster -i
531 panic(9) now stops other CPUs in the SMP systems, disables interrupts
532 on the current CPU and prevents other threads from running.
533 This behavior can be reverted using the kern.stop_scheduler_on_panic
535 The new behavior can be incompatible with kern.sync_on_panic.
538 The carp(4) facility has been changed significantly. Configuration
539 of the CARP protocol via ifconfig(8) has changed, as well as format
540 of CARP events submitted to devd(8) has changed. See manual pages
541 for more information. The arpbalance feature of carp(4) is currently
542 not supported anymore.
544 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
545 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
546 need to be recompiled.
549 The acpi_wmi(4) status device /dev/wmistat has been renamed to
553 The option VFS_ALLOW_NONMPSAFE option has been added in order to
554 explicitely support non-MPSAFE filesystems.
555 It is on by default for all supported platform at this present
559 The broken amd(4) driver has been replaced with esp(4) in the amd64,
560 i386 and pc98 GENERIC kernel configuration files.
563 sysinstall has been removed
566 The stable/9 branch created in subversion. This corresponds to the
567 RELENG_9 branch in CVS.
570 This commit modifies vfs_register() so that it uses a hash
571 calculation to set vfc_typenum, which is enabled by default.
572 The first time a system is booted after this change, the
573 vfc_typenum values will change for all file systems. The
574 main effect of this is a change to the NFS server file handles
575 for file systems that use vfc_typenum in their fsid, such as ZFS.
576 It will, however, prevent vfc_typenum from changing when file
577 systems are loaded in a different order for subsequent reboots.
578 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
579 until you are ready to remount all NFS clients after a reboot.
582 Bump the shared library version numbers for libraries that
583 do not use symbol versioning, have changed the ABI compared
584 to stable/8 and which shared library version was not bumped.
585 Done as part of 9.0-RELEASE cycle.
588 During the merge of Capsicum features, the fget(9) KPI was modified.
589 This may require the rebuilding of out-of-tree device drivers --
590 issues have been reported specifically with the nVidia device driver.
591 __FreeBSD_version is bumped to 900041.
593 Also, there is a period between 20110811 and 20110814 where the
594 special devices /dev/{stdin,stdout,stderr} did not work correctly.
595 Building world from a kernel during that window may not work.
598 The packet filter (pf) code has been updated to OpenBSD 4.5.
599 You need to update userland tools to be in sync with kernel.
600 This update breaks backward compatibility with earlier pfsync(4)
601 versions. Care must be taken when updating redundant firewall setups.
604 The following sysctls and tunables are retired on x86 platforms:
606 machdep.hlt_logical_cpus
607 The following sysctl is retired:
608 machdep.hyperthreading_allowed
609 The sysctls were supposed to provide a way to dynamically offline and
610 online selected CPUs on x86 platforms, but the implementation has not
611 been reliable especially with SCHED_ULE scheduler.
612 machdep.hyperthreading_allowed tunable is still available to ignore
613 hyperthreading CPUs at OS level.
614 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
615 where X is an APIC ID of a CPU. Be advised, though, that disabling
616 CPUs in non-uniform fashion will result in non-uniform topology and
617 may lead to sub-optimal system performance with SCHED_ULE, which is
621 cpumask_t type is retired and cpuset_t is used in order to describe
625 Changes to ifconfig(8) for dynamic address family detection mandate
626 that you are running a kernel of 20110525 or later. Make sure to
627 follow the update procedure to boot a new kernel before installing
631 Support for sun4v architecture is officially dropped
634 Several KPI breaking changes have been committed to the mii(4) layer,
635 the PHY drivers and consequently some Ethernet drivers using mii(4).
636 This means that miibus.ko and the modules of the affected Ethernet
637 drivers need to be recompiled.
639 Note to kernel developers: Given that the OUI bit reversion problem
640 was fixed as part of these changes all mii(4) commits related to OUIs,
641 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
642 handling, no longer can be merged verbatim to stable/8 and previous
646 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
647 into their kernel configurations along with 'device pci'.
650 The default NFS client is now the new NFS client, so fstype "newnfs"
651 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
652 Although mounts via fstype "nfs" will usually work without userland
653 changes, it is recommended that the mount(8) and mount_nfs(8)
654 commands be rebuilt from sources and that a link to mount_nfs called
655 mount_oldnfs be created. The new client is compiled into the
656 kernel with "options NFSCL" and this is needed for diskless root
657 file systems. The GENERIC kernel configs have been changed to use
658 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
659 To use the regular/old client, you can "mount -t oldnfs ...". For
660 a diskless root file system, you must also include a line like:
662 vfs.root.mountfrom="oldnfs:"
664 in the boot/loader.conf on the root fs on the NFS server to make
665 a diskless root fs use the old client.
668 The GENERIC kernels for all architectures now default to the new
669 CAM-based ATA stack. It means that all legacy ATA drivers were
670 removed and replaced by respective CAM drivers. If you are using
671 ATA device names in /etc/fstab or other places, make sure to update
672 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
673 where 'Y's are the sequential numbers starting from zero for each type
674 in order of detection, unless configured otherwise with tunables,
675 see cam(4)). There will be symbolic links created in /dev/ to map
676 old adX devices to the respective adaY. They should provide basic
677 compatibility for file systems mounting in most cases, but they do
678 not support old user-level APIs and do not have respective providers
679 in GEOM. Consider using updated management tools with new device names.
681 It is possible to load devices ahci, ata, siis and mvs as modules,
682 but option ATA_CAM should remain in kernel configuration to make ata
683 module work as CAM driver supporting legacy ATA controllers. Device ata
684 still can be used in modular fashion (atacore + ...). Modules atadisk
685 and atapi* are not used and won't affect operation in ATA_CAM mode.
686 Note that to use CAM-based ATA kernel should include CAM devices
687 scbus, pass, da (or explicitly ada), cd and optionally others. All of
688 them are parts of the cam module.
690 ataraid(4) functionality is now supported by the RAID GEOM class.
691 To use it you can load geom_raid kernel module and use graid(8) tool
692 for management. Instead of /dev/arX device names, use /dev/raid/rX.
694 No kernel config options or code have been removed, so if a problem
695 arises, please report it and optionally revert to the old ATA stack.
696 In order to do it you can remove from the kernel config:
701 , and instead add back:
702 device atadisk # ATA disk drives
703 device ataraid # ATA RAID drives
704 device atapicd # ATAPI CDROM drives
705 device atapifd # ATAPI floppy drives
706 device atapist # ATAPI tape drives
709 The default NFS server has been changed to the new server, which
710 was referred to as the experimental server. If you need to switch
711 back to the old NFS server, you must now put the "-o" option on
712 both the mountd and nfsd commands. This can be done using the
713 mountd_flags and nfs_server_flags rc.conf variables until an
714 update to the rc scripts is committed, which is coming soon.
717 The GNU Objective-C runtime library (libobjc), and other Objective-C
718 related components have been removed from the base system. If you
719 require an Objective-C library, please use one of the available ports.
722 ath(4) has been split into bus- and device- modules. if_ath contains
723 the HAL, the TX rate control and the network device code. if_ath_pci
724 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
725 contains the AHB glue. Users need to load both if_ath_pci and if_ath
726 in order to use ath on everything else.
728 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
729 need to load if_ath and if_ath_pci for ath(4) operation.
732 As part of the replacement of sysinstall, the process of building
733 release media has changed significantly. For details, please re-read
734 release(7), which has been updated to reflect the new build process.
737 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
738 is the last available version under GPLv2. It brings a number of new
739 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
740 4.1 and SSE 4.2), better support for powerpc64, a number of new
741 directives, and lots of other small improvements. See the ChangeLog
742 file in contrib/binutils for the full details.
745 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
746 compliant, and will now use half of hash for authentication.
747 This will break interoperability with all stacks (including all
748 actual FreeBSD versions) who implement
749 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
751 The only workaround with such peers is to use another HMAC
752 algorithm for IPsec ("phase 2") authentication.
755 Remove the uio_yield prototype and symbol. This function has
756 been misnamed since it was introduced and should not be
757 globally exposed with this name. The equivalent functionality
758 is now available using kern_yield(curthread->td_user_pri).
759 The function remains undocumented.
762 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
763 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
764 for scalar sysctls is defined but disabled. Code that needs
765 UQUAD to pass the type checking that must compile on older
766 systems where the define is not present can check against
767 __FreeBSD_version >= 900030.
769 The system dialog(1) has been replaced with a new version previously
770 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
771 with the previous version, but the libdialog associated with it has
772 a largely incompatible API. As such, the original version of libdialog
773 will be kept temporarily as libodialog, until its base system consumers
774 are replaced or updated. Bump __FreeBSD_version to 900030.
777 If you are trying to run make universe on a -stable system, and you get
778 the following warning:
779 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
780 unknown. config(8) likely too old."
781 or something similar to it, then you must upgrade your -stable system
782 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
783 stable/8) or build the config from the latest stable/8 branch and
784 install it on your system.
786 Prior to this date, building a current universe on 8-stable system from
787 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
788 error in the first kernel build phase. A new config on those old
789 systems will fix that problem for older versions of -current.
792 The TCP stack has been modified to allow Khelp modules to interact with
793 it via helper hook points and store per-connection data in the TCP
794 control block. Bump __FreeBSD_version to 900029. User space tools that
795 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
799 Generic IEEE 802.3 annex 31B full duplex flow control support has been
800 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
801 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
802 to take advantage of it instead of using custom implementations. This
803 means that these drivers now no longer unconditionally advertise
804 support for flow control but only do so if flow control is a selected
805 media option. This was implemented in the generic support that way in
806 order to allow flow control to be switched on and off via ifconfig(8)
807 with the PHY specific default to typically off in order to protect
808 from unwanted effects. Consequently, if you used flow control with
809 one of the above mentioned drivers you now need to explicitly enable
811 ifconfig bge0 media auto mediaopt flowcontrol
813 Along with the above mentioned changes generic support for setting
814 1000baseT master mode also has been added and brgphy(4), ciphy(4),
815 e1000phy(4) as well as ip1000phy(4) have been converted to take
816 advantage of it. This means that these drivers now no longer take the
817 link0 parameter for selecting master mode but the master media option
818 has to be used instead, for example like in the following:
819 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
821 Selection of master mode now is also available with all other PHY
822 drivers supporting 1000baseT.
825 The TCP stack has received a significant update to add support for
826 modularised congestion control and generally improve the clarity of
827 congestion control decisions. Bump __FreeBSD_version to 900025. User
828 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
829 sockstat) need to be recompiled.
832 The man(1) utility has been replaced by a new version that no longer
833 uses /etc/manpath.config. Please consult man.conf(5) for how to
834 migrate local entries to the new format.
837 The copyright strings printed by login(1) and sshd(8) at the time of a
838 new connection have been removed to follow other operating systems and
842 A workaround for a fixed ld bug has been removed in kernel code,
843 so make sure that your system ld is built from sources after
844 revision 210245 from 2010-07-19 (r211583 if building head kernel
845 on stable/8, r211584 for stable/7; both from 2010-08-21).
846 A symptom of incorrect ld version is different addresses for
847 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
850 The $ipv6_prefer variable in rc.conf(5) has been split into
851 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
853 The $ip6addrctl_policy is a variable to choose a pre-defined
854 address selection policy set by ip6addrctl(8). A value
855 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
858 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
859 flag (see an entry of 20090926) is set on an interface with no
860 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
861 security reason. If you want IPv6 link-local address on all
862 interfaces by default, set this to "YES".
864 The old ipv6_prefer="YES" is equivalent to
865 ipv6_activate_all_interfaces="YES" and
866 ip6addrctl_policy="ipv6_prefer".
869 DTrace has grown support for userland tracing. Due to this, DTrace is
870 now i386 and amd64 only.
871 dtruss(1) is now installed by default on those systems and a new
872 kernel module is needed for userland tracing: fasttrap.
873 No changes to your kernel config file are necessary to enable
874 userland tracing, but you might consider adding 'STRIP=' and
875 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
876 to have informative userland stack traces in DTrace (ustack).
879 The acpi_aiboost(4) driver has been removed in favor of the new
880 aibs(4) driver. You should update your kernel configuration file.
883 BSD grep has been imported to the base system and it is built by
884 default. It is completely BSD licensed, highly GNU-compatible, uses
885 less memory than its GNU counterpart and has a small codebase.
886 However, it is slower than its GNU counterpart, which is mostly
887 noticeable for larger searches, for smaller ones it is measurable
888 but not significant. The reason is complex, the most important factor
889 is that we lack a modern and efficient regex library and GNU
890 overcomes this by optimizing the searches internally. Future work
891 on improving the regex performance is planned, for the meantime,
892 users that need better performance, can build GNU grep instead by
893 setting the WITH_GNU_GREP knob.
896 Due to the import of powerpc64 support, all existing powerpc kernel
897 configuration files must be updated with a machine directive like this:
898 machine powerpc powerpc
900 In addition, an updated config(8) is required to build powerpc kernels
904 A new version of ZFS (version 15) has been merged to -HEAD.
905 This version uses a python library for the following subcommands:
906 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
907 For full functionality of these commands the following port must
908 be installed: sysutils/py-zfs
911 'vm_page's are now hashed by physical address to an array of mutexes.
912 Currently this is only used to serialize access to hold_count. Over
913 time the page queue mutex will be peeled away. This changes the size
914 of pmap on every architecture. And requires all callers of vm_page_hold
915 and vm_page_unhold to be updated.
918 WITH_CTF can now be specified in src.conf (not recommended, there
919 are some problems with static executables), make.conf (would also
920 affect ports which do not use GNU make and do not override the
921 compile targets) or in the kernel config (via "makeoptions
923 When WITH_CTF was specified there before this was silently ignored,
924 so make sure that WITH_CTF is not used in places which could lead
925 to unwanted behavior.
928 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
929 to allow 32-bit compatibility on non-x86 platforms. All kernel
930 configurations on amd64 and ia64 platforms using these options must
931 be modified accordingly.
934 The utmp user accounting database has been replaced with utmpx,
935 the user accounting interface standardized by POSIX.
936 Unfortunately the semantics of utmp and utmpx don't match,
937 making it practically impossible to support both interfaces.
938 The user accounting database is used by tools like finger(1),
939 last(1), talk(1), w(1) and ac(8).
941 All applications in the base system use utmpx. This means only
942 local binaries (e.g. from the ports tree) may still use these
943 utmp database files. These applications must be rebuilt to make
946 After the system has been upgraded, it is safe to remove the old
947 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
948 assuming their contents is of no importance anymore. Old wtmp
949 databases can only be used by last(1) and ac(8) after they have
950 been converted to the new format using wtmpcvt(1).
953 Introduce the kernel thread "deadlock resolver" (which can be enabled
954 via the DEADLKRES option, see NOTES for more details) and the
955 sleepq_type() function for sleepqueues.
958 The rc.firewall and rc.firewall6 were unified, and
959 rc.firewall6 and rc.d/ip6fw were removed.
960 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
961 variables are obsoleted. Instead, the following new rc
962 variables are added to rc.d/ipfw:
964 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
965 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
966 firewall_simple_onet_ipv6, firewall_trusted_ipv6
968 The meanings correspond to the relevant IPv4 variables.
974 The default terminal emulation for syscons(4) has been changed
975 from cons25 to xterm on all platforms except pc98. This means
976 that the /etc/ttys file needs to be updated to ensure correct
977 operation of applications on the console.
979 The terminal emulation style can be toggled per window by using
980 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
981 options can be used to change the compile-time default back to
984 To prevent graphical artifacts, make sure the TERM environment
985 variable is set to match the terminal emulation that is being
986 performed by syscons(4).
989 The layout of the structure ieee80211req_scan_result has changed.
990 Applications that require wireless scan results (e.g. ifconfig(8))
991 from net80211 need to be recompiled.
993 Applications such as wpa_supplicant(8) may require a full world
994 build without using NO_CLEAN in order to get synchronized with the
998 The iwn(4) driver has been updated to support the 5000 and 5150 series.
999 There's one kernel module for each firmware. Adding "device iwnfw"
1000 to the kernel configuration file means including all three firmware
1001 images inside the kernel. If you want to include just the one for
1002 your wireless card, use the devices iwn4965fw, iwn5000fw or
1006 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1007 into rc.d/netif. The changes are the following:
1009 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1010 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1011 Note that both variables need the "inet6" keyword at the head.
1013 Do not set $ipv6_network_interfaces manually if you do not
1014 understand what you are doing. It is not needed in most cases.
1016 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1019 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1020 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1022 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1023 all configured interfaces have "inet6 accept_rtadv" in the
1024 $ifconfig_IF_ipv6. These are for backward compatibility.
1026 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1027 functionality of interfaces with no corresponding
1028 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1029 and the default address selection policy of ip6addrctl(8)
1030 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1031 Note that if you want to configure IPv6 functionality on the
1032 disabled interfaces after boot, first you need to clear the flag by
1033 using ifconfig(8) like:
1035 ifconfig em0 inet6 -ifdisabled
1037 If YES, the default address selection policy is set as
1040 The default value of $ipv6_prefer is NO.
1042 4. If your system need to receive Router Advertisement messages,
1043 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1044 scripts automatically invoke rtsol(8) when the interface becomes
1045 UP. The Router Advertisement messages are used for SLAAC
1046 (State-Less Address AutoConfiguration).
1049 802.11s D3.03 support was committed. This is incompatible with the
1050 previous code, which was based on D3.0.
1053 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1054 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1055 control whether accepting Router Advertisement messages or not.
1056 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1057 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1058 The ifconfig(8) utility now supports these flags.
1061 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1062 mount(8) and -a option for df(1) to see them.
1065 The old tunable hw.bus.devctl_disable has been superseded by
1066 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1067 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1071 Remove the option STOP_NMI. The default action is now to use NMI only
1072 for KDB via the newly introduced function stop_cpus_hard() and
1073 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1076 The stable/8 branch created in subversion. This corresponds to the
1077 RELENG_8 branch in CVS.
1080 Bump the shared library version numbers for all libraries that do not
1081 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1082 __FreeBSD_version to 800105.
1085 Due to changes in the implementation of virtual network stack support,
1086 all network-related kernel modules must be recompiled. As this change
1087 breaks the ABI, bump __FreeBSD_version to 800104.
1090 The TOE interface to the TCP syncache has been modified to remove
1091 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1092 The cxgb driver is the only TOE consumer affected by this change, and
1093 needs to be recompiled along with the kernel. As this change breaks
1094 the ABI, bump __FreeBSD_version to 800103.
1097 Padding has been added to struct tcpcb, sackhint and tcpstat in
1098 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1099 maintaining the ABI. However, this change breaks the ABI, so bump
1100 __FreeBSD_version to 800102. User space tools that rely on the size of
1101 any of these structs (e.g. sockstat) need to be recompiled.
1104 The NFS_LEGACYRPC option has been removed along with the old kernel
1105 RPC implementation that this option selected. Kernel configurations
1106 may need to be adjusted.
1109 The network interface device nodes at /dev/net/<interface> have been
1110 removed. All ioctl operations can be performed the normal way using
1111 routing sockets. The kqueue functionality can generally be replaced
1112 with routing sockets.
1115 The documentation from the FreeBSD Documentation Project (Handbook,
1116 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1117 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1120 The ABI of various structures related to the SYSV IPC API have been
1121 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1122 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1126 Layout of struct vnet has changed as routing related variables were
1127 moved to their own Vimage module. Modules need to be recompiled. Bump
1128 __FreeBSD_version to 800099.
1131 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1132 respectively. As long as no more than 16 groups per process are used,
1133 no changes should be visible. When more than 16 groups are used, old
1134 binaries may fail if they call getgroups() or getgrouplist() with
1135 statically sized storage. Recompiling will work around this, but
1136 applications should be modified to use dynamically allocated storage
1137 for group arrays as POSIX.1-2008 does not cap an implementation's
1138 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1140 NFS and portalfs mounts may also be affected as the list of groups is
1141 truncated to 16. Users of NFS who use more than 16 groups, should
1142 take care that negative group permissions are not used on the exported
1143 file systems as they will not be reliable unless a GSSAPI based
1144 authentication method is used.
1147 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1148 option compiles in the support for adaptive spinning for lockmgrs
1149 which want to enable it. The lockinit() function now accepts the flag
1150 LK_ADAPTIVE in order to make the lock object subject to adaptive
1151 spinning when both held in write and read mode.
1154 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1155 changed. User applications that use this ioctl need to be rebuilt.
1158 The layout of struct thread has changed. Kernel and modules need to
1162 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1163 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1166 window(1) has been removed from the base system. It can now be
1167 installed from ports. The port is called misc/window.
1170 The way we are storing and accessing `routing table' entries has
1171 changed. Programs reading the FIB, like netstat, need to be
1175 A new netisr implementation has been added for FreeBSD 8. Network
1176 file system modules, such as igmp, ipdivert, and others, should be
1178 Bump __FreeBSD_version to 800096.
1181 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1185 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1186 Bump __FreeBSD_version to 800094.
1189 Add mnt_xflag field to 'struct mount'. File system modules need to be
1191 Bump __FreeBSD_version to 800093.
1194 The compiling option ADAPTIVE_SX has been retired while it has been
1195 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1196 The KPI for sx_init_flags() changes as accepting flags:
1197 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1198 been introduced in order to handle the reversed logic.
1199 Bump __FreeBSD_version to 800092.
1202 Add support for hierarchical jails. Remove global securelevel.
1203 Bump __FreeBSD_version to 800091.
1206 The layout of struct vnet_net has changed, therefore modules
1208 Bump __FreeBSD_version to 800090.
1211 The newly imported zic(8) produces a new format in the output. Please
1212 run tzsetup(8) to install the newly created data to /etc/localtime.
1215 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1216 hw.usb.* and is now consistent again with previous releases.
1219 802.11 monitor mode support was revised and driver api's were changed.
1220 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1221 of DLT_IEEE802_11. No user-visible data structures were changed but
1222 applications that use DLT_IEEE802_11 may require changes.
1223 Bump __FreeBSD_version to 800088.
1226 The layout of the following structs has changed: sysctl_oid,
1227 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1228 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1229 panics may be experienced. World rebuild is required for
1230 correctly checking networking state from userland.
1231 Bump __FreeBSD_version to 800085.
1234 MLDv2 and Source-Specific Multicast (SSM) have been merged
1235 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1236 The implementation of SSM within FreeBSD's IPv6 stack closely
1237 follows the IPv4 implementation.
1239 For kernel developers:
1241 * The most important changes are that the ip6_output() and
1242 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1243 and this lock has been downgraded to a non-recursive mutex.
1245 * As with the changes to the IPv4 stack to support SSM, filtering
1246 of inbound multicast traffic must now be performed by transport
1247 protocols within the IPv6 stack. This does not apply to TCP and
1248 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1250 * The KPIs used by IPv6 multicast are similar to those used by
1251 the IPv4 stack, with the following differences:
1252 * im6o_mc_filter() is analogous to imo_multicast_filter().
1253 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1254 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1255 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1256 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1257 for MLDv1 have an additional 'timer' argument which is used to
1258 jitter the initial membership report for the solicited-node
1259 multicast membership on-link.
1260 * This is not strictly needed for MLDv2, which already jitters
1261 its report transmissions. However, the 'timer' argument is
1262 preserved in case MLDv1 is active on the interface.
1264 * The KAME linked-list based IPv6 membership implementation has
1265 been refactored to use a vector similar to that used by the IPv4
1267 Code which maintains a list of its own multicast memberships
1268 internally, e.g. carp, has been updated to reflect the new
1271 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1272 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1273 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1274 implementation constraint which needs to be addressed in HEAD.
1276 For application developers:
1278 * The changes are broadly similar to those made for the IPv4
1281 * The use of IPv4 and IPv6 multicast socket options on the same
1282 socket, using mapped addresses, HAS NOT been tested or supported.
1284 * There are a number of issues with the implementation of various
1285 IPv6 multicast APIs which need to be resolved in the API surface
1286 before the implementation is fully compatible with KAME userland
1287 use, and these are mostly to do with interface index treatment.
1289 * The literature available discusses the use of either the delta / ASM
1290 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1291 using setsourcefilter(3)/getsourcefilter(3). For more information
1292 please refer to RFC 3768, 'Socket Interface Extensions for
1293 Multicast Source Filters'.
1295 * Applications which use the published RFC 3678 APIs should be fine.
1297 For systems administrators:
1299 * The mtest(8) utility has been refactored to support IPv6, in
1300 addition to IPv4. Interface addresses are no longer accepted
1301 as arguments, their names must be used instead. The utility
1302 will map the interface name to its first IPv4 address as
1303 returned by getifaddrs(3).
1305 * The ifmcstat(8) utility has also been updated to print the MLDv2
1306 endpoint state and source filter lists via sysctl(3).
1308 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1309 loopback of IPv6 multicast datagrams by default; it defaults to 1
1310 to preserve the existing behaviour. Disabling multicast loopback is
1311 recommended for optimal system performance.
1313 * The IPv6 MROUTING code has been changed to examine this sysctl
1314 instead of attempting to perform a group lookup before looping
1315 back forwarded datagrams.
1317 Bump __FreeBSD_version to 800084.
1320 Implement low-level Bluetooth HCI API.
1321 Bump __FreeBSD_version to 800083.
1324 The layout of struct malloc_type, used by modules to register new
1325 memory allocation types, has changed. Most modules will need to
1326 be rebuilt or panics may be experienced.
1327 Bump __FreeBSD_version to 800081.
1330 Anticipate overflowing inp_flags - add inp_flags2.
1331 This changes most offsets in inpcb, so checking v4 connection
1332 state will require a world rebuild.
1333 Bump __FreeBSD_version to 800080.
1336 Add an llentry to struct route and struct route_in6. Modules
1337 embedding a struct route will need to be recompiled.
1338 Bump __FreeBSD_version to 800079.
1341 The size of rt_metrics_lite and by extension rtentry has changed.
1342 Networking administration apps will need to be recompiled.
1343 The route command now supports show as an alias for get, weighting
1344 of routes, sticky and nostick flags to alter the behavior of stateful
1346 Bump __FreeBSD_version to 800078.
1349 Do not use Giant for kbdmux(4) locking. This is wrong and
1350 apparently causing more problems than it solves. This will
1351 re-open the issue where interrupt handlers may race with
1352 kbdmux(4) in polling mode. Typical symptoms include (but
1353 not limited to) duplicated and/or missing characters when
1354 low level console functions (such as gets) are used while
1355 interrupts are enabled (for example geli password prompt,
1356 mountroot prompt etc.). Disabling kbdmux(4) may help.
1359 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1360 kernel modules referencing any of the above need to be recompiled.
1361 Bump __FreeBSD_version to 800075.
1364 GEOM_PART has become the default partition slicer for storage devices,
1365 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1366 introduces some changes:
1368 MSDOS/EBR: the devices created from MSDOS extended partition entries
1369 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1370 to devices with offset-based names. fstabs may need to be modified.
1372 BSD: the "geometry does not match label" warning is harmless in most
1373 cases but it points to problems in file system misalignment with
1374 disk geometry. The "c" partition is now implicit, covers the whole
1375 top-level drive and cannot be (mis)used by users.
1377 General: Kernel dumps are now not allowed to be written to devices
1378 whose partition types indicate they are meant to be used for file
1379 systems (or, in case of MSDOS partitions, as something else than
1382 Most of these changes date approximately from 200812.
1385 The uscanner(4) driver has been removed from the kernel. This follows
1386 Linux removing theirs in 2.6 and making libusb the default interface
1387 (supported by sane).
1390 The multicast forwarding code has been cleaned up. netstat(1)
1391 only relies on KVM now for printing bandwidth upcall meters.
1392 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1393 ip6_mroute_mod respectively. The config(5) options for statically
1394 compiling this code remain the same, i.e. 'options MROUTING'.
1397 Support for the IFF_NEEDSGIANT network interface flag has been
1398 removed, which means that non-MPSAFE network device drivers are no
1399 longer supported. In particular, if_ar, if_sr, and network device
1400 drivers from the old (legacy) USB stack can no longer be built or
1404 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1405 a bunch of new language catalog files have also been added.
1406 This means that some common libc messages are now localized and
1407 they depend on the LC_MESSAGES environmental variable.
1410 The k8temp(4) driver has been renamed to amdtemp(4) since
1411 support for Family 10 and Family 11 CPU families was added.
1414 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1415 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1417 For kernel developers, the most important changes are that the
1418 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1419 and this lock has been downgraded to a non-recursive mutex.
1421 Transport protocols (UDP, Raw IP) are now responsible for filtering
1422 inbound multicast traffic according to group membership and source
1423 filters. The imo_multicast_filter() KPI exists for this purpose.
1424 Transports which do not use multicast (SCTP, TCP) already reject
1425 multicast by default. Forwarding and receive performance may improve
1426 as a mutex acquisition is no longer needed in the ip_input()
1427 low-level input path. in_addmulti() and in_delmulti() are shimmed
1428 to new KPIs which exist to support SSM in-kernel.
1430 For application developers, it is recommended that loopback of
1431 multicast datagrams be disabled for best performance, as this
1432 will still cause the lock to be taken for each looped-back
1433 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1434 be tuned to 0 to disable loopback by default; it defaults to 1
1435 to preserve the existing behaviour.
1437 For systems administrators, to obtain best performance with
1438 multicast reception and multiple groups, it is always recommended
1439 that a card with a suitably precise hash filter is used. Hash
1440 collisions will still result in the lock being taken within the
1441 transport protocol input path to check group membership.
1443 If deploying FreeBSD in an environment with IGMP snooping switches,
1444 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1445 enabled; this forces 224.0.0.0/24 group membership to be announced
1448 The size of 'struct igmpstat' has changed; netstat needs to be
1449 recompiled to reflect this.
1450 Bump __FreeBSD_version to 800070.
1453 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1454 updated to use it. This requires a buildworld/installworld in order to
1455 update the library and dependencies (usbconfig, etc). Its advisable to
1456 rebuild all ports which uses libusb. More specific directions are given
1457 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1458 libusb are no longer required and can be removed.
1461 A workaround is committed to allow the creation of System V shared
1462 memory segment of size > 2 GB on the 64-bit architectures.
1463 Due to a limitation of the existing ABI, the shm_segsz member
1464 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1465 wrong for large segments. Note that limits must be explicitly
1466 raised to allow such segments to be created.
1469 The layout of struct ifnet has changed, requiring a rebuild of all
1470 network device driver modules.
1473 The /dev handling for the new USB stack has changed, a
1474 buildworld/installworld is required for libusb20.
1477 The new USB2 stack has now been permanently moved in and all kernel and
1478 module names reverted to their previous values (eg, usb, ehci, ohci,
1479 ums, ...). The old usb stack can be compiled in by prefixing the name
1480 with the letter 'o', the old usb modules have been removed.
1481 Updating entry 20090216 for xorg and 20090215 for libmap may still
1485 The rc.conf(5) option if_up_delay has been renamed to
1486 defaultroute_delay to better reflect its purpose. If you have
1487 customized this setting in /etc/rc.conf you need to update it to
1491 xorg 7.4 wants to configure its input devices via hald which does not
1492 yet work with USB2. If the keyboard/mouse does not work in xorg then
1494 Option "AllowEmptyInput" "off"
1495 to your ServerLayout section. This will cause X to use the configured
1496 kbd and mouse sections from your xorg.conf.
1499 The GENERIC kernels for all architectures now default to the new USB2
1500 stack. No kernel config options or code have been removed so if a
1501 problem arises please report it and optionally revert to the old USB
1502 stack. If you are loading USB kernel modules or have a custom kernel
1503 that includes GENERIC then ensure that usb names are also changed over,
1504 eg uftdi -> usb2_serial_ftdi.
1506 Older programs linked against the ports libusb 0.1 need to be
1507 redirected to the new stack's libusb20. /etc/libmap.conf can
1509 # Map old usb library to new one for usb2 stack
1510 libusb-0.1.so.8 libusb20.so.1
1513 All USB ethernet devices now attach as interfaces under the name ueN
1514 (eg. ue0). This is to provide a predictable name as vendors often
1515 change usb chipsets in a product without notice.
1518 The ichsmb(4) driver has been changed to require SMBus slave
1519 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1520 All of the other SMBus controller drivers require left-justified
1521 slave addresses, so this change makes all the drivers provide the
1525 INET6 statistics (struct ip6stat) was updated.
1526 netstat(1) needs to be recompiled.
1529 NTFS has been removed from GENERIC kernel on amd64 to match
1530 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1531 will load ntfs.ko module automatically when NTFS support is
1532 actually needed, unless ntfs.ko is not installed or security
1533 level prohibits loading kernel modules. If either is the case,
1534 "options NTFS" has to be added into kernel config.
1537 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1538 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1539 800061. User space tools that rely on the size of struct tcpcb in
1540 tcp_var.h (e.g. sockstat) need to be recompiled.
1543 ng_tty(4) module updated to match the new TTY subsystem.
1544 Due to API change, user-level applications must be updated.
1545 New API support added to mpd5 CVS and expected to be present
1546 in next mpd5.3 release.
1549 With __FreeBSD_version 800060 the makefs tool is part of
1550 the base system (it was a port).
1553 The afdata and ifnet locks have been changed from mutexes to
1554 rwlocks, network modules will need to be re-compiled.
1557 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1558 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1559 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1560 architecture and 40 bytes on 64-bit architecture. The userland
1561 applications "arp" and "ndp" have been updated accordingly.
1562 The output from "netstat -r" shows only routing entries and
1563 none of the L2 information.
1566 __FreeBSD_version 800057 marks the switchover from the
1567 binary ath hal to source code. Users must add the line:
1569 options AH_SUPPORT_AR5416
1571 to their kernel config files when specifying:
1575 The ath_hal module no longer exists; the code is now compiled
1576 together with the driver in the ath module. It is now
1577 possible to tailor chip support (i.e. reduce the set of chips
1578 and thereby the code size); consult ath_hal(4) for details.
1581 __FreeBSD_version 800054 adds memory barriers to
1582 <machine/atomic.h>, new interfaces to ifnet to facilitate
1583 multiple hardware transmit queues for cards that support
1584 them, and a lock-less ring-buffer implementation to
1585 enable drivers to more efficiently manage queueing of
1589 A new version of ZFS (version 13) has been merged to -HEAD.
1590 This version has zpool attribute "listsnapshots" off by
1591 default, which means "zfs list" does not show snapshots,
1592 and is the same as Solaris behavior.
1595 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1598 The uhci, ohci, ehci and slhci USB Host controller drivers have
1599 been put into separate modules. If you load the usb module
1600 separately through loader.conf you will need to load the
1601 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1602 controller add the following to loader.conf:
1608 The ABI used by the PMC toolset has changed. Please keep
1609 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1613 atapci kernel module now includes only generic PCI ATA
1614 driver. AHCI driver moved to ataahci kernel module.
1615 All vendor-specific code moved into separate kernel modules:
1616 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1617 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1618 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1619 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1622 The TTY subsystem of the kernel has been replaced by a new
1623 implementation, which provides better scalability and an
1624 improved driver model. Most common drivers have been migrated to
1625 the new TTY subsystem, while others have not. The following
1626 drivers have not yet been ported to the new TTY layer:
1629 cy, digi, rc, rp, sio
1635 ng_h4, ng_tty, ppp, sl, snp
1637 Adding these drivers to your kernel configuration file shall
1638 cause compilation to fail.
1641 ntpd has been upgraded to 4.2.4p5.
1644 OpenSSH has been upgraded to 5.1p1.
1646 For many years, FreeBSD's version of OpenSSH preferred DSA
1647 over RSA for host and user authentication keys. With this
1648 upgrade, we've switched to the vendor's default of RSA over
1649 DSA. This may cause upgraded clients to warn about unknown
1650 host keys even for previously known hosts. Users should
1651 follow the usual procedure for verifying host keys before
1652 accepting the RSA key.
1654 This can be circumvented by setting the "HostKeyAlgorithms"
1655 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1658 Please note that the sequence of keys offered for
1659 authentication has been changed as well. You may want to
1660 specify IdentityFile in a different order to revert this
1664 The sio(4) driver has been removed from the i386 and amd64
1665 kernel configuration files. This means uart(4) is now the
1666 default serial port driver on those platforms as well.
1668 To prevent collisions with the sio(4) driver, the uart(4) driver
1669 uses different names for its device nodes. This means the
1670 onboard serial port will now most likely be called "ttyu0"
1671 instead of "ttyd0". You may need to reconfigure applications to
1672 use the new device names.
1674 When using the serial port as a boot console, be sure to update
1675 /boot/device.hints and /etc/ttys before booting the new kernel.
1676 If you forget to do so, you can still manually specify the hints
1677 at the loader prompt:
1679 set hint.uart.0.at="isa"
1680 set hint.uart.0.port="0x3F8"
1681 set hint.uart.0.flags="0x10"
1682 set hint.uart.0.irq="4"
1686 The gpt(8) utility has been removed. Use gpart(8) to partition
1690 The version that Linuxulator emulates was changed from 2.4.2
1691 to 2.6.16. If you experience any problems with Linux binaries
1692 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1693 if it fixes the problem contact emulation mailing list.
1696 ISDN4BSD (I4B) was removed from the src tree. You may need to
1697 update a your kernel configuration and remove relevant entries.
1700 I have checked in code to support multiple routing tables.
1701 See the man pages setfib(1) and setfib(2).
1702 This is a hopefully backwards compatible version,
1703 but to make use of it you need to compile your kernel
1704 with options ROUTETABLES=2 (or more up to 16).
1707 The 802.11 wireless support was redone to enable multi-bss
1708 operation on devices that are capable. The underlying device
1709 is no longer used directly but instead wlanX devices are
1710 cloned with ifconfig. This requires changes to rc.conf files.
1711 For example, change:
1712 ifconfig_ath0="WPA DHCP"
1715 ifconfig_wlan0="WPA DHCP"
1716 see rc.conf(5) for more details. In addition, mergemaster of
1717 /etc/rc.d is highly recommended. Simultaneous update of userland
1718 and kernel wouldn't hurt either.
1720 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1721 modules were merged into the base wlan module. All references
1722 to these modules (e.g. in kernel config files) must be removed.
1725 psm(4) has gained write(2) support in native operation level.
1726 Arbitrary commands can be written to /dev/psm%d and status can
1727 be read back from it. Therefore, an application is responsible
1728 for status validation and error recovery. It is a no-op in
1729 other operation levels.
1732 Support for KSE threading has been removed from the kernel. To
1733 run legacy applications linked against KSE libmap.conf may
1734 be used. The following libmap.conf may be used to ensure
1735 compatibility with any prior release:
1737 libpthread.so.1 libthr.so.1
1738 libpthread.so.2 libthr.so.2
1739 libkse.so.3 libthr.so.3
1742 The layout of struct vmspace has changed. This affects libkvm
1743 and any executables that link against libkvm and use the
1744 kvm_getprocs() function. In particular, but not exclusively,
1745 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1746 The effects are minimal, but it's advisable to upgrade world
1750 The latest em driver no longer has support in it for the
1751 82575 adapter, this is now moved to the igb driver. The
1752 split was done to make new features that are incompatible
1753 with older hardware easier to do.
1756 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1757 likewise the kernel option is now GEOM_LINUX_LVM.
1760 The default NFS mount mode has changed from UDP to TCP for
1761 increased reliability. If you rely on (insecurely) NFS
1762 mounting across a firewall you may need to update your
1766 Belatedly note the addition of m_collapse for compacting
1770 The fts(3) structures have been changed to use adequate
1771 integer types for their members and so to be able to cope
1772 with huge file trees. The old fts(3) ABI is preserved
1773 through symbol versioning in libc, so third-party binaries
1774 using fts(3) should still work, although they will not take
1775 advantage of the extended types. At the same time, some
1776 third-party software might fail to build after this change
1777 due to unportable assumptions made in its source code about
1778 fts(3) structure members. Such software should be fixed
1779 by its vendor or, in the worst case, in the ports tree.
1780 FreeBSD_version 800015 marks this change for the unlikely
1781 case that a portable fix is impossible.
1784 To upgrade to -current after this date, you must be running
1785 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1786 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1789 The ADAPTIVE_GIANT kernel option has been retired because its
1790 functionality is the default now.
1793 The AT keyboard emulation of sunkbd(4) has been turned on
1794 by default. In order to make the special symbols of the Sun
1795 keyboards driven by sunkbd(4) work under X these now have
1796 to be configured the same way as Sun USB keyboards driven
1797 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1799 Option "XkbLayout" "us"
1800 Option "XkbRules" "xorg"
1801 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1804 It has been decided that it is desirable to provide ABI
1805 backwards compatibility to the FreeBSD 4/5/6 versions of the
1806 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1807 broken with the introduction of PCI domain support (see the
1808 20070930 entry). Unfortunately, this required the ABI of
1809 PCIOCGETCONF to be broken again in order to be able to
1810 provide backwards compatibility to the old version of that
1811 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1812 again. As for prominent ports this affects neither pciutils
1813 nor xorg-server this time, the hal port needs to be rebuilt
1817 The misnamed kthread_create() and friends have been renamed
1818 to kproc_create() etc. Many of the callers already
1819 used kproc_start()..
1820 I will return kthread_create() and friends in a while
1821 with implementations that actually create threads, not procs.
1822 Renaming corresponds with version 800002.
1831 Avoid using make -j when upgrading. While generally safe, there are
1832 sometimes problems using -j to upgrade. If your upgrade fails with
1833 -j, please try again without -j. From time to time in the past there
1834 have been problems using -j with buildworld and/or installworld. This
1835 is especially true when upgrading between "distant" versions (eg one
1836 that cross a major release boundary or several minor releases, or when
1837 several months have passed on the -current branch).
1839 Sometimes, obscure build problems are the result of environment
1840 poisoning. This can happen because the make utility reads its
1841 environment when searching for values for global variables. To run
1842 your build attempts in an "environmental clean room", prefix all make
1843 commands with 'env -i '. See the env(1) manual page for more details.
1845 When upgrading from one major version to another it is generally best
1846 to upgrade to the latest code in the currently installed branch first,
1847 then do an upgrade to the new branch. This is the best-tested upgrade
1848 path, and has the highest probability of being successful. Please try
1849 this approach before reporting problems with a major version upgrade.
1851 When upgrading a live system, having a root shell around before
1852 installing anything can help undo problems. Not having a root shell
1853 around can lead to problems if pam has changed too much from your
1854 starting point to allow continued authentication after the upgrade.
1858 When upgrading the boot ZFS pool to a new version, always follow
1861 1.) recompile and reinstall the ZFS boot loader and boot block
1862 (this is part of "make buildworld" and "make installworld")
1864 2.) update the ZFS boot block on your boot drive
1866 The following example updates the ZFS boot block on the first
1867 partition (freebsd-boot) of a GPT partitioned drive ad0:
1868 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1870 Non-boot pools do not need these updates.
1874 If you are updating from a prior version of FreeBSD (even one just
1875 a few days old), you should follow this procedure. It is the most
1876 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1878 make kernel-toolchain
1879 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1880 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1882 To test a kernel once
1883 ---------------------
1884 If you just want to boot a kernel once (because you are not sure
1885 if it works, or if you want to boot a known bad kernel to provide
1886 debugging information) run
1887 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1888 nextboot -k testkernel
1890 To just build a kernel when you know that it won't mess you up
1891 --------------------------------------------------------------
1892 This assumes you are already running a CURRENT system. Replace
1893 ${arch} with the architecture of your machine (e.g. "i386",
1894 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1896 cd src/sys/${arch}/conf
1897 config KERNEL_NAME_HERE
1898 cd ../compile/KERNEL_NAME_HERE
1903 If this fails, go to the "To build a kernel" section.
1905 To rebuild everything and install it on the current system.
1906 -----------------------------------------------------------
1907 # Note: sometimes if you are running current you gotta do more than
1908 # is listed here if you are upgrading from a really old current.
1910 <make sure you have good level 0 dumps>
1912 make kernel KERNCONF=YOUR_KERNEL_HERE
1914 <reboot in single user> [3]
1921 To cross-install current onto a separate partition
1922 --------------------------------------------------
1923 # In this approach we use a separate partition to hold
1924 # current's root, 'usr', and 'var' directories. A partition
1925 # holding "/", "/usr" and "/var" should be about 2GB in
1928 <make sure you have good level 0 dumps>
1931 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1932 <maybe newfs current's root partition>
1933 <mount current's root partition on directory ${CURRENT_ROOT}>
1934 make installworld DESTDIR=${CURRENT_ROOT}
1935 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1936 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1937 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1938 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1939 <reboot into current>
1940 <do a "native" rebuild/install as described in the previous section>
1941 <maybe install compatibility libraries from ports/misc/compat*>
1945 To upgrade in-place from stable to current
1946 ----------------------------------------------
1947 <make sure you have good level 0 dumps>
1949 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1951 <reboot in single user> [3]
1958 Make sure that you've read the UPDATING file to understand the
1959 tweaks to various things you need. At this point in the life
1960 cycle of current, things change often and you are on your own
1961 to cope. The defaults can also change, so please read ALL of
1962 the UPDATING entries.
1964 Also, if you are tracking -current, you must be subscribed to
1965 freebsd-current@freebsd.org. Make sure that before you update
1966 your sources that you have read and understood all the recent
1967 messages there. If in doubt, please track -stable which has
1968 much fewer pitfalls.
1970 [1] If you have third party modules, such as vmware, you
1971 should disable them at this point so they don't crash your
1974 [3] From the bootblocks, boot -s, and then do
1979 adjkerntz -i # if CMOS is wall time
1980 Also, when doing a major release upgrade, it is required that
1981 you boot into single user mode to do the installworld.
1983 [4] Note: This step is non-optional. Failure to do this step
1984 can result in a significant reduction in the functionality of the
1985 system. Attempting to do it by hand is not recommended and those
1986 that pursue this avenue should read this file carefully, as well
1987 as the archives of freebsd-current and freebsd-hackers mailing lists
1988 for potential gotchas. The -U option is also useful to consider.
1989 See mergemaster(8) for more information.
1991 [5] Usually this step is a noop. However, from time to time
1992 you may need to do this if you get unknown user in the following
1993 step. It never hurts to do it all the time. You may need to
1994 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1995 install) after the buildworld before this step if you last updated
1996 from current before 20130425 or from -stable before 20130430.
1998 [6] This only deletes old files and directories. Old libraries
1999 can be deleted by "make delete-old-libs", but you have to make
2000 sure that no program is using those libraries anymore.
2002 [8] In order to have a kernel that can run the 4.x binaries needed to
2003 do an installworld, you must include the COMPAT_FREEBSD4 option in
2004 your kernel. Failure to do so may leave you with a system that is
2005 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2006 required to run the 5.x binaries on more recent kernels. And so on
2007 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2009 Make sure that you merge any new devices from GENERIC since the
2010 last time you updated your kernel config file.
2012 [9] When checking out sources, you must include the -P flag to have
2013 cvs prune empty directories.
2015 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2016 "?=" instead of the "=" assignment operator, so that buildworld can
2017 override the CPUTYPE if it needs to.
2019 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2020 not on the command line, or in /etc/make.conf. buildworld will
2021 warn if it is improperly defined.
2024 This file contains a list, in reverse chronological order, of major
2025 breakages in tracking -current. It is not guaranteed to be a complete
2026 list of such breakages, and only contains entries since October 10, 2007.
2027 If you need to see UPDATING entries from before that date, you will need
2028 to fetch an UPDATING file from an older FreeBSD release.
2030 Copyright information:
2032 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2034 Redistribution, publication, translation and use, with or without
2035 modification, in full or in part, in any form or format of this
2036 document are permitted without further permission from the author.
2038 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2039 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2040 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2041 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2042 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2043 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2044 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2045 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2046 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2047 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2048 POSSIBILITY OF SUCH DAMAGE.
2050 Contact Warner Losh if you have any questions about your use of