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 rc.d/jail script has been updated to support jail(8)
21 configuration file. The "jail_<jname>_*" rc.conf(5) variables
22 for per-jail configuration are automatically converted to
23 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
24 This is transparently backward compatible. See below about some
25 incompatibilities and rc.conf(5) manual page for more details.
27 These variables are now deprecated in favor of jail(8) configuration
28 file. One can use "rc.d/jail config <jname>" command to generate
29 a jail(8) configuration file in /var/run/jail.<jname>.conf without
30 running the jail(8) utility. The default pathname of the
31 configuration file is /etc/jail.conf and can be specified by
32 using $jail_conf or $jail_<jname>_conf variables.
34 Please note that jail_devfs_ruleset accepts an integer at
35 this moment. Please consider to rewrite the ruleset name
39 BIND has been removed from the base system. If all you need
40 is a local resolver, simply enable and start the local_unbound
41 service instead. Otherwise, several versions of BIND are
42 available in the ports tree.
45 With the addition of unbound(8), a new unbound user is now
46 required during installworld. "mergemaster -p" can be used to
47 add the user prior to installworld, as documented in the handbook.
50 OpenSSH is now built with DNSSEC support, and will by default
51 silently trust signed SSHFP records. This can be controlled with
52 the VerifyHostKeyDNS client configuration setting. DNSSEC support
53 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
56 The GNU Compiler Collection and C++ standard library (libstdc++)
57 are no longer built by default on platforms where clang is the system
58 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
62 The PROCDESC kernel option is now part of the GENERIC kernel
63 configuration and is required for the rwhod(8) to work.
64 If you are using custom kernel configuration, you should include
68 The API and ABI related to the Capsicum framework was modified
69 in backward incompatible way. The userland libraries and programs
70 have to be recompiled to work with the new kernel. This includes the
71 following libraries and programs, but the whole buildworld is
72 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
73 kdump, procstat, rwho, rwhod, uniq.
76 AES-NI intrinsic support has been added to gcc. The AES-NI module
77 has been updated to use this support. A new gcc is required to build
78 the aesni module on both i386 and amd64.
81 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
82 Thus "device padlock_rng" and "device rdrand_rng" should be
83 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
86 WITH_ICONV has been split into two feature sets. WITH_ICONV now
87 enables just the iconv* functionality and is now on by default.
88 WITH_LIBICONV_COMPAT enables the libiconv api and link time
89 compatability. Set WITHOUT_ICONV to build the old way.
90 If you have been using WITH_ICONV before, you will very likely
91 need to turn on WITH_LIBICONV_COMPAT.
94 INVARIANTS option now enables DEBUG for code with OpenSolaris and
95 Illumos origin, including ZFS. If you have INVARIANTS in your
96 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
98 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
99 locks if WITNESS option was set. Because that generated a lot of
100 witness(9) reports and all of them were believed to be false
101 positives, this is no longer done. New option OPENSOLARIS_WITNESS
102 can be used to achieve the previous behavior.
105 Timer values in IPv6 data structures now use time_uptime instead
106 of time_second. Although this is not a user-visible functional
107 change, userland utilities which directly use them---ndp(8),
108 rtadvd(8), and rtsold(8) in the base system---need to be updated
112 find -delete can now delete the pathnames given as arguments,
113 instead of only files found below them or if the pathname did
114 not contain any slashes. Formerly, the following error message
117 find: -delete: <path>: relative path potentially not safe
119 Deleting the pathnames given as arguments can be prevented
120 without error messages using -mindepth 1 or by changing
121 directory and passing "." as argument to find. This works in the
122 old as well as the new version of find.
125 Behavior of devfs rules path matching has been changed.
126 Pattern is now always matched against fully qualified devfs
127 path and slash characters must be explicitly matched by
128 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
129 subdirectories must be reviewed.
132 The default ARM ABI has changed to the ARM EABI. The old ABI is
133 incompatible with the ARM EABI and all programs and modules will
134 need to be rebuilt to work with a new kernel.
136 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
138 NOTE: Support for the old ABI will be removed in the future and
139 users are advised to upgrade.
142 pkg_install has been disconnected from the build if you really need it
143 you should add WITH_PKGTOOLS in your src.conf(5).
146 Most of network statistics structures were changed to be able
147 keep 64-bits counters. Thus all tools, that work with networking
148 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
151 Fix targets that run multiple make's to use && rather than ;
152 so that subsequent steps depend on success of previous.
154 NOTE: if building 'universe' with -j* on stable/8 or stable/9
155 it would be better to start the build using bmake, to avoid
156 overloading the machine.
159 Fix a bug that allowed a tracing process (e.g. gdb) to write
160 to a memory-mapped file in the traced process's address space
161 even if neither the traced process nor the tracing process had
162 write access to that file.
165 CVS has been removed from the base system. An exact copy
166 of the code is available from the devel/cvs port.
169 Some people report the following error after the switch to bmake:
171 make: illegal option -- J
172 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
174 *** [buildworld] Error code 2
176 this likely due to an old instance of make in
177 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
178 which src/Makefile will use that blindly, if it exists, so if
179 you see the above error:
181 rm -rf `make -V MAKEPATH`
186 Use bmake by default.
187 Whereas before one could choose to build with bmake via
188 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
189 make. The goal is to remove these knobs for 10-RELEASE.
191 It is worth noting that bmake (like gmake) treats the command
192 line as the unit of failure, rather than statements within the
193 command line. Thus '(cd some/where && dosomething)' is safer
194 than 'cd some/where; dosomething'. The '()' allows consistent
195 behavior in parallel build.
198 Fix a bug that allows NFS clients to issue READDIR on files.
201 The WITHOUT_IDEA option has been removed because
202 the IDEA patent expired.
205 The sysctl which controls TRIM support under ZFS has been renamed
206 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
210 The mergemaster command now uses the default MAKEOBJDIRPREFIX
211 rather than creating it's own in the temporary directory in
212 order allow access to bootstrapped versions of tools such as
213 install and mtree. When upgrading from version of FreeBSD where
214 the install command does not support -l, you will need to
215 install a new mergemaster command if mergemaster -p is required.
216 This can be accomplished with the command (cd src/usr.sbin/mergemaster
220 Legacy ATA stack, disabled and replaced by new CAM-based one since
221 FreeBSD 9.0, completely removed from the sources. Kernel modules
222 atadisk and atapi*, user-level tools atacontrol and burncd are
223 removed. Kernel option `options ATA_CAM` is now permanently enabled
227 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
228 and socketpair(2). Software, in particular Kerberos, may
229 automatically detect and use these during building. The resulting
230 binaries will not work on older kernels.
233 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
234 information, see the respective 20130304 entry).
237 Recent commits to callout(9) changed the size of struct callout,
238 so the KBI is probably heavily disturbed. Also, some functions
239 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
240 by macros. Every kernel module using it won't load, so rebuild
243 The ctl device has been re-enabled in GENERIC for i386 and amd64,
244 but does not initialize by default (because of the new CTL_DISABLE
245 option) to save memory. To re-enable it, remove the CTL_DISABLE
246 option from the kernel config file or set kern.cam.ctl.disable=0
247 in /boot/loader.conf.
250 The ctl device has been disabled in GENERIC for i386 and amd64.
251 This was done due to the extra memory being allocated at system
252 initialisation time by the ctl driver which was only used if
253 a CAM target device was created. This makes a FreeBSD system
254 unusable on 128MB or less of RAM.
257 A new compression method (lz4) has been merged to -HEAD. Please
258 refer to zpool-features(7) for more information.
260 Please refer to the "ZFS notes" section of this file for information
261 on upgrading boot ZFS pools.
264 A BSD-licensed patch(1) variant has been added and is installed
265 as bsdpatch, being the GNU version the default patch.
266 To inverse the logic and use the BSD-licensed one as default,
267 while having the GNU version installed as gnupatch, rebuild
268 and install world with the WITH_BSD_PATCH knob set.
271 Due to the use of the new -l option to install(1) during build
272 and install, you must take care not to directly set the INSTALL
273 make variable in your /etc/make.conf, /etc/src.conf, or on the
274 command line. If you wish to use the -C flag for all installs
275 you may be able to add INSTALL+=-C to /etc/make.conf or
279 The install(1) option -M has changed meaning and now takes an
280 argument that is a file or path to append logs to. In the
281 unlikely event that -M was the last option on the command line
282 and the command line contained at least two files and a target
283 directory the first file will have logs appended to it. The -M
284 option served little practical purpose in the last decade so its
285 use is expected to be extremely rare.
288 After switching to Clang as the default compiler some users of ZFS
289 on i386 systems started to experience stack overflow kernel panics.
290 Please consider using 'options KSTACK_PAGES=4' in such configurations.
293 GEOM_LABEL now mangles label names read from file system metadata.
294 Mangling affect labels containing spaces, non-printable characters,
295 '%' or '"'. Device names in /etc/fstab and other places may need to
299 By default, only the 10 most recent kernel dumps will be saved. To
300 restore the previous behaviour (no limit on the number of kernel dumps
301 stored in the dump directory) add the following line to /etc/rc.conf:
306 With the addition of auditdistd(8), a new auditdistd user is now
307 required during installworld. "mergemaster -p" can be used to
308 add the user prior to installworld, as documented in the handbook.
311 The sin6_scope_id member variable in struct sockaddr_in6 is now
312 filled by the kernel before passing the structure to the userland via
313 sysctl or routing socket. This means the KAME-specific embedded scope
314 id in sin6_addr.s6_addr[2] is always cleared in userland application.
315 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
316 __FreeBSD_version is bumped to 1000025.
319 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
320 This means that the world and kernel will be compiled with clang
321 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
322 and /usr/bin/cpp. To disable this behavior and revert to building
323 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
324 of current may need to bootstrap WITHOUT_CLANG first if the clang
325 build fails (its compatibility window doesn't extend to the 9 stable
329 The IPFIREWALL_FORWARD kernel option has been removed. Its
330 functionality now turned on by default.
333 The ZERO_COPY_SOCKET kernel option has been removed and
334 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
335 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
336 mechanism which is not safe and may result in kernel crashes.
337 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
338 driver supports disposeable external page sized mbuf storage.
339 Proper replacements for both zero-copy mechanisms are under
340 consideration and will eventually lead to complete removal
341 of the two kernel options.
344 The IPv4 network stack has been converted to network byte
345 order. The following modules need to be recompiled together
346 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
347 pf(4), ipfw(4), ng_ipfw(4), stf(4).
350 Support for non-MPSAFE filesystems was removed from VFS. The
351 VFS_VERSION was bumped, all filesystem modules shall be
355 All the non-MPSAFE filesystems have been disconnected from
356 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
357 portalfs, smbfs, xfs.
360 The interface cloning API and ABI has changed. The following
361 modules need to be recompiled together with kernel:
362 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
363 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
364 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
367 The sdhci driver was split in two parts: sdhci (generic SD Host
368 Controller logic) and sdhci_pci (actual hardware driver).
369 No kernel config modifications are required, but if you
370 load sdhc as a module you must switch to sdhci_pci instead.
373 Import the FUSE kernel and userland support into base system.
376 The GNU sort(1) program has been removed since the BSD-licensed
377 sort(1) has been the default for quite some time and no serious
378 problems have been reported. The corresponding WITH_GNU_SORT
382 The pfil(9) API/ABI for AF_INET family has been changed. Packet
383 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
387 The net80211(4) ABI has been changed to allow for improved driver
388 PS-POLL and power-save support. All wireless drivers need to be
389 recompiled to work with the new kernel.
392 The random(4) support for the VIA hardware random number
393 generator (`PADLOCK') is no longer enabled unconditionally.
394 Add the padlock_rng device in the custom kernel config if
395 needed. The GENERIC kernels on i386 and amd64 do include the
396 device, so the change only affects the custom kernel
400 The pf(4) packet filter ABI has been changed. pfctl(8) and
401 snmp_pf module need to be recompiled to work with new kernel.
404 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
405 to -HEAD. Pools that have empty_bpobj in active state can not be
406 imported read-write with ZFS implementations that do not support
407 this feature. For more information read the zpool-features(5)
411 The sparc64 ZFS loader has been changed to no longer try to auto-
412 detect ZFS providers based on diskN aliases but now requires these
413 to be explicitly listed in the OFW boot-device environment variable.
416 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
417 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
418 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
421 The following sysctls and tunables have been renamed for consistency
422 with other variables:
423 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
424 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
427 The sort utility has been replaced with BSD sort. For now, GNU sort
428 is also available as "gnusort" or the default can be set back to
429 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
430 installed as "bsdsort".
433 A new version of ZFS (pool version 5000) has been merged to -HEAD.
434 Starting with this version the old system of ZFS pool versioning
435 is superseded by "feature flags". This concept enables forward
436 compatibility against certain future changes in functionality of ZFS
437 pools. The first read-only compatible "feature flag" for ZFS pools
438 is named "com.delphix:async_destroy". For more information
439 read the new zpool-features(5) manual page.
440 Please refer to the "ZFS notes" section of this file for information
441 on upgrading boot ZFS pools.
444 The malloc(3) implementation embedded in libc now uses sources imported
445 as contrib/jemalloc. The most disruptive API change is to
446 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
447 delete it prior to installworld, and optionally re-create it using the
448 new format after rebooting. See malloc.conf(5) for details
449 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
453 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
454 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
455 now spelled mips. This is to aid compatibility with third-party
456 software that expects this naming scheme in uname(3). Little-endian
457 settings are unchanged. If you are updating a big-endian mips64 machine
458 from before this change, you may need to set MACHINE_ARCH=mips64 in
459 your environment before the new build system will recognize your machine.
462 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
466 Now unix domain sockets behave "as expected" on nullfs(5). Previously
467 nullfs(5) did not pass through all behaviours to the underlying layer,
468 as a result if we bound to a socket on the lower layer we could connect
469 only to the lower path; if we bound to the upper layer we could connect
470 only to the upper path. The new behavior is one can connect to both the
471 lower and the upper paths regardless what layer path one binds to.
474 The getifaddrs upgrade path broken with 20111215 has been restored.
475 If you have upgraded in between 20111215 and 20120209 you need to
476 recompile libc again with your kernel. You still need to recompile
477 world to be able to configure CARP but this restriction already
481 The set_rcvar() function has been removed from /etc/rc.subr. All
482 base and ports rc.d scripts have been updated, so if you have a
483 port installed with a script in /usr/local/etc/rc.d you can either
484 hand-edit the rcvar= line, or reinstall the port.
486 An easy way to handle the mass-update of /etc/rc.d:
487 rm /etc/rc.d/* && mergemaster -i
490 panic(9) now stops other CPUs in the SMP systems, disables interrupts
491 on the current CPU and prevents other threads from running.
492 This behavior can be reverted using the kern.stop_scheduler_on_panic
494 The new behavior can be incompatible with kern.sync_on_panic.
497 The carp(4) facility has been changed significantly. Configuration
498 of the CARP protocol via ifconfig(8) has changed, as well as format
499 of CARP events submitted to devd(8) has changed. See manual pages
500 for more information. The arpbalance feature of carp(4) is currently
501 not supported anymore.
503 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
504 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
505 need to be recompiled.
508 The acpi_wmi(4) status device /dev/wmistat has been renamed to
512 The option VFS_ALLOW_NONMPSAFE option has been added in order to
513 explicitely support non-MPSAFE filesystems.
514 It is on by default for all supported platform at this present
518 The broken amd(4) driver has been replaced with esp(4) in the amd64,
519 i386 and pc98 GENERIC kernel configuration files.
522 sysinstall has been removed
525 The stable/9 branch created in subversion. This corresponds to the
526 RELENG_9 branch in CVS.
529 This commit modifies vfs_register() so that it uses a hash
530 calculation to set vfc_typenum, which is enabled by default.
531 The first time a system is booted after this change, the
532 vfc_typenum values will change for all file systems. The
533 main effect of this is a change to the NFS server file handles
534 for file systems that use vfc_typenum in their fsid, such as ZFS.
535 It will, however, prevent vfc_typenum from changing when file
536 systems are loaded in a different order for subsequent reboots.
537 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
538 until you are ready to remount all NFS clients after a reboot.
541 Bump the shared library version numbers for libraries that
542 do not use symbol versioning, have changed the ABI compared
543 to stable/8 and which shared library version was not bumped.
544 Done as part of 9.0-RELEASE cycle.
547 During the merge of Capsicum features, the fget(9) KPI was modified.
548 This may require the rebuilding of out-of-tree device drivers --
549 issues have been reported specifically with the nVidia device driver.
550 __FreeBSD_version is bumped to 900041.
552 Also, there is a period between 20110811 and 20110814 where the
553 special devices /dev/{stdin,stdout,stderr} did not work correctly.
554 Building world from a kernel during that window may not work.
557 The packet filter (pf) code has been updated to OpenBSD 4.5.
558 You need to update userland tools to be in sync with kernel.
559 This update breaks backward compatibility with earlier pfsync(4)
560 versions. Care must be taken when updating redundant firewall setups.
563 The following sysctls and tunables are retired on x86 platforms:
565 machdep.hlt_logical_cpus
566 The following sysctl is retired:
567 machdep.hyperthreading_allowed
568 The sysctls were supposed to provide a way to dynamically offline and
569 online selected CPUs on x86 platforms, but the implementation has not
570 been reliable especially with SCHED_ULE scheduler.
571 machdep.hyperthreading_allowed tunable is still available to ignore
572 hyperthreading CPUs at OS level.
573 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
574 where X is an APIC ID of a CPU. Be advised, though, that disabling
575 CPUs in non-uniform fashion will result in non-uniform topology and
576 may lead to sub-optimal system performance with SCHED_ULE, which is
580 cpumask_t type is retired and cpuset_t is used in order to describe
584 Changes to ifconfig(8) for dynamic address family detection mandate
585 that you are running a kernel of 20110525 or later. Make sure to
586 follow the update procedure to boot a new kernel before installing
590 Support for sun4v architecture is officially dropped
593 Several KPI breaking changes have been committed to the mii(4) layer,
594 the PHY drivers and consequently some Ethernet drivers using mii(4).
595 This means that miibus.ko and the modules of the affected Ethernet
596 drivers need to be recompiled.
598 Note to kernel developers: Given that the OUI bit reversion problem
599 was fixed as part of these changes all mii(4) commits related to OUIs,
600 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
601 handling, no longer can be merged verbatim to stable/8 and previous
605 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
606 into their kernel configurations along with 'device pci'.
609 The default NFS client is now the new NFS client, so fstype "newnfs"
610 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
611 Although mounts via fstype "nfs" will usually work without userland
612 changes, it is recommended that the mount(8) and mount_nfs(8)
613 commands be rebuilt from sources and that a link to mount_nfs called
614 mount_oldnfs be created. The new client is compiled into the
615 kernel with "options NFSCL" and this is needed for diskless root
616 file systems. The GENERIC kernel configs have been changed to use
617 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
618 To use the regular/old client, you can "mount -t oldnfs ...". For
619 a diskless root file system, you must also include a line like:
621 vfs.root.mountfrom="oldnfs:"
623 in the boot/loader.conf on the root fs on the NFS server to make
624 a diskless root fs use the old client.
627 The GENERIC kernels for all architectures now default to the new
628 CAM-based ATA stack. It means that all legacy ATA drivers were
629 removed and replaced by respective CAM drivers. If you are using
630 ATA device names in /etc/fstab or other places, make sure to update
631 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
632 where 'Y's are the sequential numbers starting from zero for each type
633 in order of detection, unless configured otherwise with tunables,
634 see cam(4)). There will be symbolic links created in /dev/ to map
635 old adX devices to the respective adaY. They should provide basic
636 compatibility for file systems mounting in most cases, but they do
637 not support old user-level APIs and do not have respective providers
638 in GEOM. Consider using updated management tools with new device names.
640 It is possible to load devices ahci, ata, siis and mvs as modules,
641 but option ATA_CAM should remain in kernel configuration to make ata
642 module work as CAM driver supporting legacy ATA controllers. Device ata
643 still can be used in modular fashion (atacore + ...). Modules atadisk
644 and atapi* are not used and won't affect operation in ATA_CAM mode.
645 Note that to use CAM-based ATA kernel should include CAM devices
646 scbus, pass, da (or explicitly ada), cd and optionally others. All of
647 them are parts of the cam module.
649 ataraid(4) functionality is now supported by the RAID GEOM class.
650 To use it you can load geom_raid kernel module and use graid(8) tool
651 for management. Instead of /dev/arX device names, use /dev/raid/rX.
653 No kernel config options or code have been removed, so if a problem
654 arises, please report it and optionally revert to the old ATA stack.
655 In order to do it you can remove from the kernel config:
660 , and instead add back:
661 device atadisk # ATA disk drives
662 device ataraid # ATA RAID drives
663 device atapicd # ATAPI CDROM drives
664 device atapifd # ATAPI floppy drives
665 device atapist # ATAPI tape drives
668 The default NFS server has been changed to the new server, which
669 was referred to as the experimental server. If you need to switch
670 back to the old NFS server, you must now put the "-o" option on
671 both the mountd and nfsd commands. This can be done using the
672 mountd_flags and nfs_server_flags rc.conf variables until an
673 update to the rc scripts is committed, which is coming soon.
676 The GNU Objective-C runtime library (libobjc), and other Objective-C
677 related components have been removed from the base system. If you
678 require an Objective-C library, please use one of the available ports.
681 ath(4) has been split into bus- and device- modules. if_ath contains
682 the HAL, the TX rate control and the network device code. if_ath_pci
683 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
684 contains the AHB glue. Users need to load both if_ath_pci and if_ath
685 in order to use ath on everything else.
687 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
688 need to load if_ath and if_ath_pci for ath(4) operation.
691 As part of the replacement of sysinstall, the process of building
692 release media has changed significantly. For details, please re-read
693 release(7), which has been updated to reflect the new build process.
696 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
697 is the last available version under GPLv2. It brings a number of new
698 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
699 4.1 and SSE 4.2), better support for powerpc64, a number of new
700 directives, and lots of other small improvements. See the ChangeLog
701 file in contrib/binutils for the full details.
704 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
705 compliant, and will now use half of hash for authentication.
706 This will break interoperability with all stacks (including all
707 actual FreeBSD versions) who implement
708 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
710 The only workaround with such peers is to use another HMAC
711 algorithm for IPsec ("phase 2") authentication.
714 Remove the uio_yield prototype and symbol. This function has
715 been misnamed since it was introduced and should not be
716 globally exposed with this name. The equivalent functionality
717 is now available using kern_yield(curthread->td_user_pri).
718 The function remains undocumented.
721 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
722 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
723 for scalar sysctls is defined but disabled. Code that needs
724 UQUAD to pass the type checking that must compile on older
725 systems where the define is not present can check against
726 __FreeBSD_version >= 900030.
728 The system dialog(1) has been replaced with a new version previously
729 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
730 with the previous version, but the libdialog associated with it has
731 a largely incompatible API. As such, the original version of libdialog
732 will be kept temporarily as libodialog, until its base system consumers
733 are replaced or updated. Bump __FreeBSD_version to 900030.
736 If you are trying to run make universe on a -stable system, and you get
737 the following warning:
738 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
739 unknown. config(8) likely too old."
740 or something similar to it, then you must upgrade your -stable system
741 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
742 stable/8) or build the config from the latest stable/8 branch and
743 install it on your system.
745 Prior to this date, building a current universe on 8-stable system from
746 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
747 error in the first kernel build phase. A new config on those old
748 systems will fix that problem for older versions of -current.
751 The TCP stack has been modified to allow Khelp modules to interact with
752 it via helper hook points and store per-connection data in the TCP
753 control block. Bump __FreeBSD_version to 900029. User space tools that
754 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
758 Generic IEEE 802.3 annex 31B full duplex flow control support has been
759 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
760 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
761 to take advantage of it instead of using custom implementations. This
762 means that these drivers now no longer unconditionally advertise
763 support for flow control but only do so if flow control is a selected
764 media option. This was implemented in the generic support that way in
765 order to allow flow control to be switched on and off via ifconfig(8)
766 with the PHY specific default to typically off in order to protect
767 from unwanted effects. Consequently, if you used flow control with
768 one of the above mentioned drivers you now need to explicitly enable
770 ifconfig bge0 media auto mediaopt flowcontrol
772 Along with the above mentioned changes generic support for setting
773 1000baseT master mode also has been added and brgphy(4), ciphy(4),
774 e1000phy(4) as well as ip1000phy(4) have been converted to take
775 advantage of it. This means that these drivers now no longer take the
776 link0 parameter for selecting master mode but the master media option
777 has to be used instead, for example like in the following:
778 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
780 Selection of master mode now is also available with all other PHY
781 drivers supporting 1000baseT.
784 The TCP stack has received a significant update to add support for
785 modularised congestion control and generally improve the clarity of
786 congestion control decisions. Bump __FreeBSD_version to 900025. User
787 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
788 sockstat) need to be recompiled.
791 The man(1) utility has been replaced by a new version that no longer
792 uses /etc/manpath.config. Please consult man.conf(5) for how to
793 migrate local entries to the new format.
796 The copyright strings printed by login(1) and sshd(8) at the time of a
797 new connection have been removed to follow other operating systems and
801 A workaround for a fixed ld bug has been removed in kernel code,
802 so make sure that your system ld is built from sources after
803 revision 210245 from 2010-07-19 (r211583 if building head kernel
804 on stable/8, r211584 for stable/7; both from 2010-08-21).
805 A symptom of incorrect ld version is different addresses for
806 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
809 The $ipv6_prefer variable in rc.conf(5) has been split into
810 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
812 The $ip6addrctl_policy is a variable to choose a pre-defined
813 address selection policy set by ip6addrctl(8). A value
814 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
817 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
818 flag (see an entry of 20090926) is set on an interface with no
819 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
820 security reason. If you want IPv6 link-local address on all
821 interfaces by default, set this to "YES".
823 The old ipv6_prefer="YES" is equivalent to
824 ipv6_activate_all_interfaces="YES" and
825 ip6addrctl_policy="ipv6_prefer".
828 DTrace has grown support for userland tracing. Due to this, DTrace is
829 now i386 and amd64 only.
830 dtruss(1) is now installed by default on those systems and a new
831 kernel module is needed for userland tracing: fasttrap.
832 No changes to your kernel config file are necessary to enable
833 userland tracing, but you might consider adding 'STRIP=' and
834 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
835 to have informative userland stack traces in DTrace (ustack).
838 The acpi_aiboost(4) driver has been removed in favor of the new
839 aibs(4) driver. You should update your kernel configuration file.
842 BSD grep has been imported to the base system and it is built by
843 default. It is completely BSD licensed, highly GNU-compatible, uses
844 less memory than its GNU counterpart and has a small codebase.
845 However, it is slower than its GNU counterpart, which is mostly
846 noticeable for larger searches, for smaller ones it is measurable
847 but not significant. The reason is complex, the most important factor
848 is that we lack a modern and efficient regex library and GNU
849 overcomes this by optimizing the searches internally. Future work
850 on improving the regex performance is planned, for the meantime,
851 users that need better performance, can build GNU grep instead by
852 setting the WITH_GNU_GREP knob.
855 Due to the import of powerpc64 support, all existing powerpc kernel
856 configuration files must be updated with a machine directive like this:
857 machine powerpc powerpc
859 In addition, an updated config(8) is required to build powerpc kernels
863 A new version of ZFS (version 15) has been merged to -HEAD.
864 This version uses a python library for the following subcommands:
865 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
866 For full functionality of these commands the following port must
867 be installed: sysutils/py-zfs
870 'vm_page's are now hashed by physical address to an array of mutexes.
871 Currently this is only used to serialize access to hold_count. Over
872 time the page queue mutex will be peeled away. This changes the size
873 of pmap on every architecture. And requires all callers of vm_page_hold
874 and vm_page_unhold to be updated.
877 WITH_CTF can now be specified in src.conf (not recommended, there
878 are some problems with static executables), make.conf (would also
879 affect ports which do not use GNU make and do not override the
880 compile targets) or in the kernel config (via "makeoptions
882 When WITH_CTF was specified there before this was silently ignored,
883 so make sure that WITH_CTF is not used in places which could lead
884 to unwanted behavior.
887 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
888 to allow 32-bit compatibility on non-x86 platforms. All kernel
889 configurations on amd64 and ia64 platforms using these options must
890 be modified accordingly.
893 The utmp user accounting database has been replaced with utmpx,
894 the user accounting interface standardized by POSIX.
895 Unfortunately the semantics of utmp and utmpx don't match,
896 making it practically impossible to support both interfaces.
897 The user accounting database is used by tools like finger(1),
898 last(1), talk(1), w(1) and ac(8).
900 All applications in the base system use utmpx. This means only
901 local binaries (e.g. from the ports tree) may still use these
902 utmp database files. These applications must be rebuilt to make
905 After the system has been upgraded, it is safe to remove the old
906 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
907 assuming their contents is of no importance anymore. Old wtmp
908 databases can only be used by last(1) and ac(8) after they have
909 been converted to the new format using wtmpcvt(1).
912 Introduce the kernel thread "deadlock resolver" (which can be enabled
913 via the DEADLKRES option, see NOTES for more details) and the
914 sleepq_type() function for sleepqueues.
917 The rc.firewall and rc.firewall6 were unified, and
918 rc.firewall6 and rc.d/ip6fw were removed.
919 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
920 variables are obsoleted. Instead, the following new rc
921 variables are added to rc.d/ipfw:
923 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
924 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
925 firewall_simple_onet_ipv6, firewall_trusted_ipv6
927 The meanings correspond to the relevant IPv4 variables.
933 The default terminal emulation for syscons(4) has been changed
934 from cons25 to xterm on all platforms except pc98. This means
935 that the /etc/ttys file needs to be updated to ensure correct
936 operation of applications on the console.
938 The terminal emulation style can be toggled per window by using
939 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
940 options can be used to change the compile-time default back to
943 To prevent graphical artifacts, make sure the TERM environment
944 variable is set to match the terminal emulation that is being
945 performed by syscons(4).
948 The layout of the structure ieee80211req_scan_result has changed.
949 Applications that require wireless scan results (e.g. ifconfig(8))
950 from net80211 need to be recompiled.
952 Applications such as wpa_supplicant(8) may require a full world
953 build without using NO_CLEAN in order to get synchronized with the
957 The iwn(4) driver has been updated to support the 5000 and 5150 series.
958 There's one kernel module for each firmware. Adding "device iwnfw"
959 to the kernel configuration file means including all three firmware
960 images inside the kernel. If you want to include just the one for
961 your wireless card, use the devices iwn4965fw, iwn5000fw or
965 The rc.d/network_ipv6, IPv6 configuration script has been integrated
966 into rc.d/netif. The changes are the following:
968 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
969 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
970 Note that both variables need the "inet6" keyword at the head.
972 Do not set $ipv6_network_interfaces manually if you do not
973 understand what you are doing. It is not needed in most cases.
975 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
978 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
979 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
981 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
982 all configured interfaces have "inet6 accept_rtadv" in the
983 $ifconfig_IF_ipv6. These are for backward compatibility.
985 3. A new variable $ipv6_prefer has been added. If NO, IPv6
986 functionality of interfaces with no corresponding
987 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
988 and the default address selection policy of ip6addrctl(8)
989 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
990 Note that if you want to configure IPv6 functionality on the
991 disabled interfaces after boot, first you need to clear the flag by
992 using ifconfig(8) like:
994 ifconfig em0 inet6 -ifdisabled
996 If YES, the default address selection policy is set as
999 The default value of $ipv6_prefer is NO.
1001 4. If your system need to receive Router Advertisement messages,
1002 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1003 scripts automatically invoke rtsol(8) when the interface becomes
1004 UP. The Router Advertisement messages are used for SLAAC
1005 (State-Less Address AutoConfiguration).
1008 802.11s D3.03 support was committed. This is incompatible with the
1009 previous code, which was based on D3.0.
1012 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1013 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1014 control whether accepting Router Advertisement messages or not.
1015 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1016 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1017 The ifconfig(8) utility now supports these flags.
1020 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1021 mount(8) and -a option for df(1) to see them.
1024 The old tunable hw.bus.devctl_disable has been superseded by
1025 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1026 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1030 Remove the option STOP_NMI. The default action is now to use NMI only
1031 for KDB via the newly introduced function stop_cpus_hard() and
1032 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1035 The stable/8 branch created in subversion. This corresponds to the
1036 RELENG_8 branch in CVS.
1039 Bump the shared library version numbers for all libraries that do not
1040 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1041 __FreeBSD_version to 800105.
1044 Due to changes in the implementation of virtual network stack support,
1045 all network-related kernel modules must be recompiled. As this change
1046 breaks the ABI, bump __FreeBSD_version to 800104.
1049 The TOE interface to the TCP syncache has been modified to remove
1050 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1051 The cxgb driver is the only TOE consumer affected by this change, and
1052 needs to be recompiled along with the kernel. As this change breaks
1053 the ABI, bump __FreeBSD_version to 800103.
1056 Padding has been added to struct tcpcb, sackhint and tcpstat in
1057 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1058 maintaining the ABI. However, this change breaks the ABI, so bump
1059 __FreeBSD_version to 800102. User space tools that rely on the size of
1060 any of these structs (e.g. sockstat) need to be recompiled.
1063 The NFS_LEGACYRPC option has been removed along with the old kernel
1064 RPC implementation that this option selected. Kernel configurations
1065 may need to be adjusted.
1068 The network interface device nodes at /dev/net/<interface> have been
1069 removed. All ioctl operations can be performed the normal way using
1070 routing sockets. The kqueue functionality can generally be replaced
1071 with routing sockets.
1074 The documentation from the FreeBSD Documentation Project (Handbook,
1075 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1076 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1079 The ABI of various structures related to the SYSV IPC API have been
1080 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1081 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1085 Layout of struct vnet has changed as routing related variables were
1086 moved to their own Vimage module. Modules need to be recompiled. Bump
1087 __FreeBSD_version to 800099.
1090 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1091 respectively. As long as no more than 16 groups per process are used,
1092 no changes should be visible. When more than 16 groups are used, old
1093 binaries may fail if they call getgroups() or getgrouplist() with
1094 statically sized storage. Recompiling will work around this, but
1095 applications should be modified to use dynamically allocated storage
1096 for group arrays as POSIX.1-2008 does not cap an implementation's
1097 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1099 NFS and portalfs mounts may also be affected as the list of groups is
1100 truncated to 16. Users of NFS who use more than 16 groups, should
1101 take care that negative group permissions are not used on the exported
1102 file systems as they will not be reliable unless a GSSAPI based
1103 authentication method is used.
1106 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1107 option compiles in the support for adaptive spinning for lockmgrs
1108 which want to enable it. The lockinit() function now accepts the flag
1109 LK_ADAPTIVE in order to make the lock object subject to adaptive
1110 spinning when both held in write and read mode.
1113 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1114 changed. User applications that use this ioctl need to be rebuilt.
1117 The layout of struct thread has changed. Kernel and modules need to
1121 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1122 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1125 window(1) has been removed from the base system. It can now be
1126 installed from ports. The port is called misc/window.
1129 The way we are storing and accessing `routing table' entries has
1130 changed. Programs reading the FIB, like netstat, need to be
1134 A new netisr implementation has been added for FreeBSD 8. Network
1135 file system modules, such as igmp, ipdivert, and others, should be
1137 Bump __FreeBSD_version to 800096.
1140 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1144 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1145 Bump __FreeBSD_version to 800094.
1148 Add mnt_xflag field to 'struct mount'. File system modules need to be
1150 Bump __FreeBSD_version to 800093.
1153 The compiling option ADAPTIVE_SX has been retired while it has been
1154 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1155 The KPI for sx_init_flags() changes as accepting flags:
1156 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1157 been introduced in order to handle the reversed logic.
1158 Bump __FreeBSD_version to 800092.
1161 Add support for hierarchical jails. Remove global securelevel.
1162 Bump __FreeBSD_version to 800091.
1165 The layout of struct vnet_net has changed, therefore modules
1167 Bump __FreeBSD_version to 800090.
1170 The newly imported zic(8) produces a new format in the output. Please
1171 run tzsetup(8) to install the newly created data to /etc/localtime.
1174 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1175 hw.usb.* and is now consistent again with previous releases.
1178 802.11 monitor mode support was revised and driver api's were changed.
1179 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1180 of DLT_IEEE802_11. No user-visible data structures were changed but
1181 applications that use DLT_IEEE802_11 may require changes.
1182 Bump __FreeBSD_version to 800088.
1185 The layout of the following structs has changed: sysctl_oid,
1186 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1187 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1188 panics may be experienced. World rebuild is required for
1189 correctly checking networking state from userland.
1190 Bump __FreeBSD_version to 800085.
1193 MLDv2 and Source-Specific Multicast (SSM) have been merged
1194 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1195 The implementation of SSM within FreeBSD's IPv6 stack closely
1196 follows the IPv4 implementation.
1198 For kernel developers:
1200 * The most important changes are that the ip6_output() and
1201 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1202 and this lock has been downgraded to a non-recursive mutex.
1204 * As with the changes to the IPv4 stack to support SSM, filtering
1205 of inbound multicast traffic must now be performed by transport
1206 protocols within the IPv6 stack. This does not apply to TCP and
1207 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1209 * The KPIs used by IPv6 multicast are similar to those used by
1210 the IPv4 stack, with the following differences:
1211 * im6o_mc_filter() is analogous to imo_multicast_filter().
1212 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1213 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1214 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1215 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1216 for MLDv1 have an additional 'timer' argument which is used to
1217 jitter the initial membership report for the solicited-node
1218 multicast membership on-link.
1219 * This is not strictly needed for MLDv2, which already jitters
1220 its report transmissions. However, the 'timer' argument is
1221 preserved in case MLDv1 is active on the interface.
1223 * The KAME linked-list based IPv6 membership implementation has
1224 been refactored to use a vector similar to that used by the IPv4
1226 Code which maintains a list of its own multicast memberships
1227 internally, e.g. carp, has been updated to reflect the new
1230 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1231 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1232 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1233 implementation constraint which needs to be addressed in HEAD.
1235 For application developers:
1237 * The changes are broadly similar to those made for the IPv4
1240 * The use of IPv4 and IPv6 multicast socket options on the same
1241 socket, using mapped addresses, HAS NOT been tested or supported.
1243 * There are a number of issues with the implementation of various
1244 IPv6 multicast APIs which need to be resolved in the API surface
1245 before the implementation is fully compatible with KAME userland
1246 use, and these are mostly to do with interface index treatment.
1248 * The literature available discusses the use of either the delta / ASM
1249 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1250 using setsourcefilter(3)/getsourcefilter(3). For more information
1251 please refer to RFC 3768, 'Socket Interface Extensions for
1252 Multicast Source Filters'.
1254 * Applications which use the published RFC 3678 APIs should be fine.
1256 For systems administrators:
1258 * The mtest(8) utility has been refactored to support IPv6, in
1259 addition to IPv4. Interface addresses are no longer accepted
1260 as arguments, their names must be used instead. The utility
1261 will map the interface name to its first IPv4 address as
1262 returned by getifaddrs(3).
1264 * The ifmcstat(8) utility has also been updated to print the MLDv2
1265 endpoint state and source filter lists via sysctl(3).
1267 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1268 loopback of IPv6 multicast datagrams by default; it defaults to 1
1269 to preserve the existing behaviour. Disabling multicast loopback is
1270 recommended for optimal system performance.
1272 * The IPv6 MROUTING code has been changed to examine this sysctl
1273 instead of attempting to perform a group lookup before looping
1274 back forwarded datagrams.
1276 Bump __FreeBSD_version to 800084.
1279 Implement low-level Bluetooth HCI API.
1280 Bump __FreeBSD_version to 800083.
1283 The layout of struct malloc_type, used by modules to register new
1284 memory allocation types, has changed. Most modules will need to
1285 be rebuilt or panics may be experienced.
1286 Bump __FreeBSD_version to 800081.
1289 Anticipate overflowing inp_flags - add inp_flags2.
1290 This changes most offsets in inpcb, so checking v4 connection
1291 state will require a world rebuild.
1292 Bump __FreeBSD_version to 800080.
1295 Add an llentry to struct route and struct route_in6. Modules
1296 embedding a struct route will need to be recompiled.
1297 Bump __FreeBSD_version to 800079.
1300 The size of rt_metrics_lite and by extension rtentry has changed.
1301 Networking administration apps will need to be recompiled.
1302 The route command now supports show as an alias for get, weighting
1303 of routes, sticky and nostick flags to alter the behavior of stateful
1305 Bump __FreeBSD_version to 800078.
1308 Do not use Giant for kbdmux(4) locking. This is wrong and
1309 apparently causing more problems than it solves. This will
1310 re-open the issue where interrupt handlers may race with
1311 kbdmux(4) in polling mode. Typical symptoms include (but
1312 not limited to) duplicated and/or missing characters when
1313 low level console functions (such as gets) are used while
1314 interrupts are enabled (for example geli password prompt,
1315 mountroot prompt etc.). Disabling kbdmux(4) may help.
1318 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1319 kernel modules referencing any of the above need to be recompiled.
1320 Bump __FreeBSD_version to 800075.
1323 GEOM_PART has become the default partition slicer for storage devices,
1324 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1325 introduces some changes:
1327 MSDOS/EBR: the devices created from MSDOS extended partition entries
1328 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1329 to devices with offset-based names. fstabs may need to be modified.
1331 BSD: the "geometry does not match label" warning is harmless in most
1332 cases but it points to problems in file system misalignment with
1333 disk geometry. The "c" partition is now implicit, covers the whole
1334 top-level drive and cannot be (mis)used by users.
1336 General: Kernel dumps are now not allowed to be written to devices
1337 whose partition types indicate they are meant to be used for file
1338 systems (or, in case of MSDOS partitions, as something else than
1341 Most of these changes date approximately from 200812.
1344 The uscanner(4) driver has been removed from the kernel. This follows
1345 Linux removing theirs in 2.6 and making libusb the default interface
1346 (supported by sane).
1349 The multicast forwarding code has been cleaned up. netstat(1)
1350 only relies on KVM now for printing bandwidth upcall meters.
1351 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1352 ip6_mroute_mod respectively. The config(5) options for statically
1353 compiling this code remain the same, i.e. 'options MROUTING'.
1356 Support for the IFF_NEEDSGIANT network interface flag has been
1357 removed, which means that non-MPSAFE network device drivers are no
1358 longer supported. In particular, if_ar, if_sr, and network device
1359 drivers from the old (legacy) USB stack can no longer be built or
1363 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1364 a bunch of new language catalog files have also been added.
1365 This means that some common libc messages are now localized and
1366 they depend on the LC_MESSAGES environmental variable.
1369 The k8temp(4) driver has been renamed to amdtemp(4) since
1370 support for Family 10 and Family 11 CPU families was added.
1373 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1374 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1376 For kernel developers, the most important changes are that the
1377 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1378 and this lock has been downgraded to a non-recursive mutex.
1380 Transport protocols (UDP, Raw IP) are now responsible for filtering
1381 inbound multicast traffic according to group membership and source
1382 filters. The imo_multicast_filter() KPI exists for this purpose.
1383 Transports which do not use multicast (SCTP, TCP) already reject
1384 multicast by default. Forwarding and receive performance may improve
1385 as a mutex acquisition is no longer needed in the ip_input()
1386 low-level input path. in_addmulti() and in_delmulti() are shimmed
1387 to new KPIs which exist to support SSM in-kernel.
1389 For application developers, it is recommended that loopback of
1390 multicast datagrams be disabled for best performance, as this
1391 will still cause the lock to be taken for each looped-back
1392 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1393 be tuned to 0 to disable loopback by default; it defaults to 1
1394 to preserve the existing behaviour.
1396 For systems administrators, to obtain best performance with
1397 multicast reception and multiple groups, it is always recommended
1398 that a card with a suitably precise hash filter is used. Hash
1399 collisions will still result in the lock being taken within the
1400 transport protocol input path to check group membership.
1402 If deploying FreeBSD in an environment with IGMP snooping switches,
1403 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1404 enabled; this forces 224.0.0.0/24 group membership to be announced
1407 The size of 'struct igmpstat' has changed; netstat needs to be
1408 recompiled to reflect this.
1409 Bump __FreeBSD_version to 800070.
1412 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1413 updated to use it. This requires a buildworld/installworld in order to
1414 update the library and dependencies (usbconfig, etc). Its advisable to
1415 rebuild all ports which uses libusb. More specific directions are given
1416 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1417 libusb are no longer required and can be removed.
1420 A workaround is committed to allow the creation of System V shared
1421 memory segment of size > 2 GB on the 64-bit architectures.
1422 Due to a limitation of the existing ABI, the shm_segsz member
1423 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1424 wrong for large segments. Note that limits must be explicitly
1425 raised to allow such segments to be created.
1428 The layout of struct ifnet has changed, requiring a rebuild of all
1429 network device driver modules.
1432 The /dev handling for the new USB stack has changed, a
1433 buildworld/installworld is required for libusb20.
1436 The new USB2 stack has now been permanently moved in and all kernel and
1437 module names reverted to their previous values (eg, usb, ehci, ohci,
1438 ums, ...). The old usb stack can be compiled in by prefixing the name
1439 with the letter 'o', the old usb modules have been removed.
1440 Updating entry 20090216 for xorg and 20090215 for libmap may still
1444 The rc.conf(5) option if_up_delay has been renamed to
1445 defaultroute_delay to better reflect its purpose. If you have
1446 customized this setting in /etc/rc.conf you need to update it to
1450 xorg 7.4 wants to configure its input devices via hald which does not
1451 yet work with USB2. If the keyboard/mouse does not work in xorg then
1453 Option "AllowEmptyInput" "off"
1454 to your ServerLayout section. This will cause X to use the configured
1455 kbd and mouse sections from your xorg.conf.
1458 The GENERIC kernels for all architectures now default to the new USB2
1459 stack. No kernel config options or code have been removed so if a
1460 problem arises please report it and optionally revert to the old USB
1461 stack. If you are loading USB kernel modules or have a custom kernel
1462 that includes GENERIC then ensure that usb names are also changed over,
1463 eg uftdi -> usb2_serial_ftdi.
1465 Older programs linked against the ports libusb 0.1 need to be
1466 redirected to the new stack's libusb20. /etc/libmap.conf can
1468 # Map old usb library to new one for usb2 stack
1469 libusb-0.1.so.8 libusb20.so.1
1472 All USB ethernet devices now attach as interfaces under the name ueN
1473 (eg. ue0). This is to provide a predictable name as vendors often
1474 change usb chipsets in a product without notice.
1477 The ichsmb(4) driver has been changed to require SMBus slave
1478 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1479 All of the other SMBus controller drivers require left-justified
1480 slave addresses, so this change makes all the drivers provide the
1484 INET6 statistics (struct ip6stat) was updated.
1485 netstat(1) needs to be recompiled.
1488 NTFS has been removed from GENERIC kernel on amd64 to match
1489 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1490 will load ntfs.ko module automatically when NTFS support is
1491 actually needed, unless ntfs.ko is not installed or security
1492 level prohibits loading kernel modules. If either is the case,
1493 "options NTFS" has to be added into kernel config.
1496 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1497 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1498 800061. User space tools that rely on the size of struct tcpcb in
1499 tcp_var.h (e.g. sockstat) need to be recompiled.
1502 ng_tty(4) module updated to match the new TTY subsystem.
1503 Due to API change, user-level applications must be updated.
1504 New API support added to mpd5 CVS and expected to be present
1505 in next mpd5.3 release.
1508 With __FreeBSD_version 800060 the makefs tool is part of
1509 the base system (it was a port).
1512 The afdata and ifnet locks have been changed from mutexes to
1513 rwlocks, network modules will need to be re-compiled.
1516 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1517 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1518 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1519 architecture and 40 bytes on 64-bit architecture. The userland
1520 applications "arp" and "ndp" have been updated accordingly.
1521 The output from "netstat -r" shows only routing entries and
1522 none of the L2 information.
1525 __FreeBSD_version 800057 marks the switchover from the
1526 binary ath hal to source code. Users must add the line:
1528 options AH_SUPPORT_AR5416
1530 to their kernel config files when specifying:
1534 The ath_hal module no longer exists; the code is now compiled
1535 together with the driver in the ath module. It is now
1536 possible to tailor chip support (i.e. reduce the set of chips
1537 and thereby the code size); consult ath_hal(4) for details.
1540 __FreeBSD_version 800054 adds memory barriers to
1541 <machine/atomic.h>, new interfaces to ifnet to facilitate
1542 multiple hardware transmit queues for cards that support
1543 them, and a lock-less ring-buffer implementation to
1544 enable drivers to more efficiently manage queueing of
1548 A new version of ZFS (version 13) has been merged to -HEAD.
1549 This version has zpool attribute "listsnapshots" off by
1550 default, which means "zfs list" does not show snapshots,
1551 and is the same as Solaris behavior.
1554 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1557 The uhci, ohci, ehci and slhci USB Host controller drivers have
1558 been put into separate modules. If you load the usb module
1559 separately through loader.conf you will need to load the
1560 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1561 controller add the following to loader.conf:
1567 The ABI used by the PMC toolset has changed. Please keep
1568 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1572 atapci kernel module now includes only generic PCI ATA
1573 driver. AHCI driver moved to ataahci kernel module.
1574 All vendor-specific code moved into separate kernel modules:
1575 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1576 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1577 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1578 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1581 The TTY subsystem of the kernel has been replaced by a new
1582 implementation, which provides better scalability and an
1583 improved driver model. Most common drivers have been migrated to
1584 the new TTY subsystem, while others have not. The following
1585 drivers have not yet been ported to the new TTY layer:
1588 cy, digi, rc, rp, sio
1594 ng_h4, ng_tty, ppp, sl, snp
1596 Adding these drivers to your kernel configuration file shall
1597 cause compilation to fail.
1600 ntpd has been upgraded to 4.2.4p5.
1603 OpenSSH has been upgraded to 5.1p1.
1605 For many years, FreeBSD's version of OpenSSH preferred DSA
1606 over RSA for host and user authentication keys. With this
1607 upgrade, we've switched to the vendor's default of RSA over
1608 DSA. This may cause upgraded clients to warn about unknown
1609 host keys even for previously known hosts. Users should
1610 follow the usual procedure for verifying host keys before
1611 accepting the RSA key.
1613 This can be circumvented by setting the "HostKeyAlgorithms"
1614 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1617 Please note that the sequence of keys offered for
1618 authentication has been changed as well. You may want to
1619 specify IdentityFile in a different order to revert this
1623 The sio(4) driver has been removed from the i386 and amd64
1624 kernel configuration files. This means uart(4) is now the
1625 default serial port driver on those platforms as well.
1627 To prevent collisions with the sio(4) driver, the uart(4) driver
1628 uses different names for its device nodes. This means the
1629 onboard serial port will now most likely be called "ttyu0"
1630 instead of "ttyd0". You may need to reconfigure applications to
1631 use the new device names.
1633 When using the serial port as a boot console, be sure to update
1634 /boot/device.hints and /etc/ttys before booting the new kernel.
1635 If you forget to do so, you can still manually specify the hints
1636 at the loader prompt:
1638 set hint.uart.0.at="isa"
1639 set hint.uart.0.port="0x3F8"
1640 set hint.uart.0.flags="0x10"
1641 set hint.uart.0.irq="4"
1645 The gpt(8) utility has been removed. Use gpart(8) to partition
1649 The version that Linuxulator emulates was changed from 2.4.2
1650 to 2.6.16. If you experience any problems with Linux binaries
1651 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1652 if it fixes the problem contact emulation mailing list.
1655 ISDN4BSD (I4B) was removed from the src tree. You may need to
1656 update a your kernel configuration and remove relevant entries.
1659 I have checked in code to support multiple routing tables.
1660 See the man pages setfib(1) and setfib(2).
1661 This is a hopefully backwards compatible version,
1662 but to make use of it you need to compile your kernel
1663 with options ROUTETABLES=2 (or more up to 16).
1666 The 802.11 wireless support was redone to enable multi-bss
1667 operation on devices that are capable. The underlying device
1668 is no longer used directly but instead wlanX devices are
1669 cloned with ifconfig. This requires changes to rc.conf files.
1670 For example, change:
1671 ifconfig_ath0="WPA DHCP"
1674 ifconfig_wlan0="WPA DHCP"
1675 see rc.conf(5) for more details. In addition, mergemaster of
1676 /etc/rc.d is highly recommended. Simultaneous update of userland
1677 and kernel wouldn't hurt either.
1679 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1680 modules were merged into the base wlan module. All references
1681 to these modules (e.g. in kernel config files) must be removed.
1684 psm(4) has gained write(2) support in native operation level.
1685 Arbitrary commands can be written to /dev/psm%d and status can
1686 be read back from it. Therefore, an application is responsible
1687 for status validation and error recovery. It is a no-op in
1688 other operation levels.
1691 Support for KSE threading has been removed from the kernel. To
1692 run legacy applications linked against KSE libmap.conf may
1693 be used. The following libmap.conf may be used to ensure
1694 compatibility with any prior release:
1696 libpthread.so.1 libthr.so.1
1697 libpthread.so.2 libthr.so.2
1698 libkse.so.3 libthr.so.3
1701 The layout of struct vmspace has changed. This affects libkvm
1702 and any executables that link against libkvm and use the
1703 kvm_getprocs() function. In particular, but not exclusively,
1704 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1705 The effects are minimal, but it's advisable to upgrade world
1709 The latest em driver no longer has support in it for the
1710 82575 adapter, this is now moved to the igb driver. The
1711 split was done to make new features that are incompatible
1712 with older hardware easier to do.
1715 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1716 likewise the kernel option is now GEOM_LINUX_LVM.
1719 The default NFS mount mode has changed from UDP to TCP for
1720 increased reliability. If you rely on (insecurely) NFS
1721 mounting across a firewall you may need to update your
1725 Belatedly note the addition of m_collapse for compacting
1729 The fts(3) structures have been changed to use adequate
1730 integer types for their members and so to be able to cope
1731 with huge file trees. The old fts(3) ABI is preserved
1732 through symbol versioning in libc, so third-party binaries
1733 using fts(3) should still work, although they will not take
1734 advantage of the extended types. At the same time, some
1735 third-party software might fail to build after this change
1736 due to unportable assumptions made in its source code about
1737 fts(3) structure members. Such software should be fixed
1738 by its vendor or, in the worst case, in the ports tree.
1739 FreeBSD_version 800015 marks this change for the unlikely
1740 case that a portable fix is impossible.
1743 To upgrade to -current after this date, you must be running
1744 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1745 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1748 The ADAPTIVE_GIANT kernel option has been retired because its
1749 functionality is the default now.
1752 The AT keyboard emulation of sunkbd(4) has been turned on
1753 by default. In order to make the special symbols of the Sun
1754 keyboards driven by sunkbd(4) work under X these now have
1755 to be configured the same way as Sun USB keyboards driven
1756 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1758 Option "XkbLayout" "us"
1759 Option "XkbRules" "xorg"
1760 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1763 It has been decided that it is desirable to provide ABI
1764 backwards compatibility to the FreeBSD 4/5/6 versions of the
1765 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1766 broken with the introduction of PCI domain support (see the
1767 20070930 entry). Unfortunately, this required the ABI of
1768 PCIOCGETCONF to be broken again in order to be able to
1769 provide backwards compatibility to the old version of that
1770 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1771 again. As for prominent ports this affects neither pciutils
1772 nor xorg-server this time, the hal port needs to be rebuilt
1776 The misnamed kthread_create() and friends have been renamed
1777 to kproc_create() etc. Many of the callers already
1778 used kproc_start()..
1779 I will return kthread_create() and friends in a while
1780 with implementations that actually create threads, not procs.
1781 Renaming corresponds with version 800002.
1790 Avoid using make -j when upgrading. While generally safe, there are
1791 sometimes problems using -j to upgrade. If your upgrade fails with
1792 -j, please try again without -j. From time to time in the past there
1793 have been problems using -j with buildworld and/or installworld. This
1794 is especially true when upgrading between "distant" versions (eg one
1795 that cross a major release boundary or several minor releases, or when
1796 several months have passed on the -current branch).
1798 Sometimes, obscure build problems are the result of environment
1799 poisoning. This can happen because the make utility reads its
1800 environment when searching for values for global variables. To run
1801 your build attempts in an "environmental clean room", prefix all make
1802 commands with 'env -i '. See the env(1) manual page for more details.
1804 When upgrading from one major version to another it is generally best
1805 to upgrade to the latest code in the currently installed branch first,
1806 then do an upgrade to the new branch. This is the best-tested upgrade
1807 path, and has the highest probability of being successful. Please try
1808 this approach before reporting problems with a major version upgrade.
1810 When upgrading a live system, having a root shell around before
1811 installing anything can help undo problems. Not having a root shell
1812 around can lead to problems if pam has changed too much from your
1813 starting point to allow continued authentication after the upgrade.
1817 When upgrading the boot ZFS pool to a new version, always follow
1820 1.) recompile and reinstall the ZFS boot loader and boot block
1821 (this is part of "make buildworld" and "make installworld")
1823 2.) update the ZFS boot block on your boot drive
1825 The following example updates the ZFS boot block on the first
1826 partition (freebsd-boot) of a GPT partitioned drive ad0:
1827 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1829 Non-boot pools do not need these updates.
1833 If you are updating from a prior version of FreeBSD (even one just
1834 a few days old), you should follow this procedure. It is the most
1835 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1837 make kernel-toolchain
1838 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1839 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1841 To test a kernel once
1842 ---------------------
1843 If you just want to boot a kernel once (because you are not sure
1844 if it works, or if you want to boot a known bad kernel to provide
1845 debugging information) run
1846 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1847 nextboot -k testkernel
1849 To just build a kernel when you know that it won't mess you up
1850 --------------------------------------------------------------
1851 This assumes you are already running a CURRENT system. Replace
1852 ${arch} with the architecture of your machine (e.g. "i386",
1853 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1855 cd src/sys/${arch}/conf
1856 config KERNEL_NAME_HERE
1857 cd ../compile/KERNEL_NAME_HERE
1862 If this fails, go to the "To build a kernel" section.
1864 To rebuild everything and install it on the current system.
1865 -----------------------------------------------------------
1866 # Note: sometimes if you are running current you gotta do more than
1867 # is listed here if you are upgrading from a really old current.
1869 <make sure you have good level 0 dumps>
1871 make kernel KERNCONF=YOUR_KERNEL_HERE
1873 <reboot in single user> [3]
1880 To cross-install current onto a separate partition
1881 --------------------------------------------------
1882 # In this approach we use a separate partition to hold
1883 # current's root, 'usr', and 'var' directories. A partition
1884 # holding "/", "/usr" and "/var" should be about 2GB in
1887 <make sure you have good level 0 dumps>
1890 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1891 <maybe newfs current's root partition>
1892 <mount current's root partition on directory ${CURRENT_ROOT}>
1893 make installworld DESTDIR=${CURRENT_ROOT}
1894 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1895 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1896 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1897 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1898 <reboot into current>
1899 <do a "native" rebuild/install as described in the previous section>
1900 <maybe install compatibility libraries from ports/misc/compat*>
1904 To upgrade in-place from stable to current
1905 ----------------------------------------------
1906 <make sure you have good level 0 dumps>
1908 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1910 <reboot in single user> [3]
1917 Make sure that you've read the UPDATING file to understand the
1918 tweaks to various things you need. At this point in the life
1919 cycle of current, things change often and you are on your own
1920 to cope. The defaults can also change, so please read ALL of
1921 the UPDATING entries.
1923 Also, if you are tracking -current, you must be subscribed to
1924 freebsd-current@freebsd.org. Make sure that before you update
1925 your sources that you have read and understood all the recent
1926 messages there. If in doubt, please track -stable which has
1927 much fewer pitfalls.
1929 [1] If you have third party modules, such as vmware, you
1930 should disable them at this point so they don't crash your
1933 [3] From the bootblocks, boot -s, and then do
1938 adjkerntz -i # if CMOS is wall time
1939 Also, when doing a major release upgrade, it is required that
1940 you boot into single user mode to do the installworld.
1942 [4] Note: This step is non-optional. Failure to do this step
1943 can result in a significant reduction in the functionality of the
1944 system. Attempting to do it by hand is not recommended and those
1945 that pursue this avenue should read this file carefully, as well
1946 as the archives of freebsd-current and freebsd-hackers mailing lists
1947 for potential gotchas. The -U option is also useful to consider.
1948 See mergemaster(8) for more information.
1950 [5] Usually this step is a noop. However, from time to time
1951 you may need to do this if you get unknown user in the following
1952 step. It never hurts to do it all the time. You may need to
1953 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1954 install) after the buildworld before this step if you last updated
1955 from current before 20130425 or from -stable before 20130430.
1957 [6] This only deletes old files and directories. Old libraries
1958 can be deleted by "make delete-old-libs", but you have to make
1959 sure that no program is using those libraries anymore.
1961 [8] In order to have a kernel that can run the 4.x binaries needed to
1962 do an installworld, you must include the COMPAT_FREEBSD4 option in
1963 your kernel. Failure to do so may leave you with a system that is
1964 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1965 required to run the 5.x binaries on more recent kernels. And so on
1966 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1968 Make sure that you merge any new devices from GENERIC since the
1969 last time you updated your kernel config file.
1971 [9] When checking out sources, you must include the -P flag to have
1972 cvs prune empty directories.
1974 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1975 "?=" instead of the "=" assignment operator, so that buildworld can
1976 override the CPUTYPE if it needs to.
1978 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1979 not on the command line, or in /etc/make.conf. buildworld will
1980 warn if it is improperly defined.
1983 This file contains a list, in reverse chronological order, of major
1984 breakages in tracking -current. It is not guaranteed to be a complete
1985 list of such breakages, and only contains entries since October 10, 2007.
1986 If you need to see UPDATING entries from before that date, you will need
1987 to fetch an UPDATING file from an older FreeBSD release.
1989 Copyright information:
1991 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1993 Redistribution, publication, translation and use, with or without
1994 modification, in full or in part, in any form or format of this
1995 document are permitted without further permission from the author.
1997 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1998 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1999 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2000 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2001 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2002 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2003 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2004 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2005 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2006 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2007 POSSIBILITY OF SUCH DAMAGE.
2009 Contact Warner Losh if you have any questions about your use of