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