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