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 default version of mtree is nmtree which is obtained from
21 NetBSD. The output is generally the same, but may vary
22 slightly. If you found you need identical output adding
23 "-F freebsd9" to the command line should do the trick. For the
24 time being, the old mtree is available as fmtree.
27 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
28 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
29 1.1.4_8 and verify bsdyml not linked in, before running "make
31 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
33 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
36 The rc.d/jail script has been updated to support jail(8)
37 configuration file. The "jail_<jname>_*" rc.conf(5) variables
38 for per-jail configuration are automatically converted to
39 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
40 This is transparently backward compatible. See below about some
41 incompatibilities and rc.conf(5) manual page for more details.
43 These variables are now deprecated in favor of jail(8) configuration
44 file. One can use "rc.d/jail config <jname>" command to generate
45 a jail(8) configuration file in /var/run/jail.<jname>.conf without
46 running the jail(8) utility. The default pathname of the
47 configuration file is /etc/jail.conf and can be specified by
48 using $jail_conf or $jail_<jname>_conf variables.
50 Please note that jail_devfs_ruleset accepts an integer at
51 this moment. Please consider to rewrite the ruleset name
55 BIND has been removed from the base system. If all you need
56 is a local resolver, simply enable and start the local_unbound
57 service instead. Otherwise, several versions of BIND are
58 available in the ports tree.
61 With the addition of unbound(8), a new unbound user is now
62 required during installworld. "mergemaster -p" can be used to
63 add the user prior to installworld, as documented in the handbook.
66 OpenSSH is now built with DNSSEC support, and will by default
67 silently trust signed SSHFP records. This can be controlled with
68 the VerifyHostKeyDNS client configuration setting. DNSSEC support
69 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
72 The GNU Compiler Collection and C++ standard library (libstdc++)
73 are no longer built by default on platforms where clang is the system
74 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
78 The PROCDESC kernel option is now part of the GENERIC kernel
79 configuration and is required for the rwhod(8) to work.
80 If you are using custom kernel configuration, you should include
84 The API and ABI related to the Capsicum framework was modified
85 in backward incompatible way. The userland libraries and programs
86 have to be recompiled to work with the new kernel. This includes the
87 following libraries and programs, but the whole buildworld is
88 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
89 kdump, procstat, rwho, rwhod, uniq.
92 AES-NI intrinsic support has been added to gcc. The AES-NI module
93 has been updated to use this support. A new gcc is required to build
94 the aesni module on both i386 and amd64.
97 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
98 Thus "device padlock_rng" and "device rdrand_rng" should be
99 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
102 WITH_ICONV has been split into two feature sets. WITH_ICONV now
103 enables just the iconv* functionality and is now on by default.
104 WITH_LIBICONV_COMPAT enables the libiconv api and link time
105 compatability. Set WITHOUT_ICONV to build the old way.
106 If you have been using WITH_ICONV before, you will very likely
107 need to turn on WITH_LIBICONV_COMPAT.
110 INVARIANTS option now enables DEBUG for code with OpenSolaris and
111 Illumos origin, including ZFS. If you have INVARIANTS in your
112 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
114 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
115 locks if WITNESS option was set. Because that generated a lot of
116 witness(9) reports and all of them were believed to be false
117 positives, this is no longer done. New option OPENSOLARIS_WITNESS
118 can be used to achieve the previous behavior.
121 Timer values in IPv6 data structures now use time_uptime instead
122 of time_second. Although this is not a user-visible functional
123 change, userland utilities which directly use them---ndp(8),
124 rtadvd(8), and rtsold(8) in the base system---need to be updated
128 find -delete can now delete the pathnames given as arguments,
129 instead of only files found below them or if the pathname did
130 not contain any slashes. Formerly, the following error message
133 find: -delete: <path>: relative path potentially not safe
135 Deleting the pathnames given as arguments can be prevented
136 without error messages using -mindepth 1 or by changing
137 directory and passing "." as argument to find. This works in the
138 old as well as the new version of find.
141 Behavior of devfs rules path matching has been changed.
142 Pattern is now always matched against fully qualified devfs
143 path and slash characters must be explicitly matched by
144 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
145 subdirectories must be reviewed.
148 The default ARM ABI has changed to the ARM EABI. The old ABI is
149 incompatible with the ARM EABI and all programs and modules will
150 need to be rebuilt to work with a new kernel.
152 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
154 NOTE: Support for the old ABI will be removed in the future and
155 users are advised to upgrade.
158 pkg_install has been disconnected from the build if you really need it
159 you should add WITH_PKGTOOLS in your src.conf(5).
162 Most of network statistics structures were changed to be able
163 keep 64-bits counters. Thus all tools, that work with networking
164 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
167 Fix targets that run multiple make's to use && rather than ;
168 so that subsequent steps depend on success of previous.
170 NOTE: if building 'universe' with -j* on stable/8 or stable/9
171 it would be better to start the build using bmake, to avoid
172 overloading the machine.
175 Fix a bug that allowed a tracing process (e.g. gdb) to write
176 to a memory-mapped file in the traced process's address space
177 even if neither the traced process nor the tracing process had
178 write access to that file.
181 CVS has been removed from the base system. An exact copy
182 of the code is available from the devel/cvs port.
185 Some people report the following error after the switch to bmake:
187 make: illegal option -- J
188 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
190 *** [buildworld] Error code 2
192 this likely due to an old instance of make in
193 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
194 which src/Makefile will use that blindly, if it exists, so if
195 you see the above error:
197 rm -rf `make -V MAKEPATH`
202 Use bmake by default.
203 Whereas before one could choose to build with bmake via
204 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
205 make. The goal is to remove these knobs for 10-RELEASE.
207 It is worth noting that bmake (like gmake) treats the command
208 line as the unit of failure, rather than statements within the
209 command line. Thus '(cd some/where && dosomething)' is safer
210 than 'cd some/where; dosomething'. The '()' allows consistent
211 behavior in parallel build.
214 Fix a bug that allows NFS clients to issue READDIR on files.
217 The WITHOUT_IDEA option has been removed because
218 the IDEA patent expired.
221 The sysctl which controls TRIM support under ZFS has been renamed
222 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
226 The mergemaster command now uses the default MAKEOBJDIRPREFIX
227 rather than creating it's own in the temporary directory in
228 order allow access to bootstrapped versions of tools such as
229 install and mtree. When upgrading from version of FreeBSD where
230 the install command does not support -l, you will need to
231 install a new mergemaster command if mergemaster -p is required.
232 This can be accomplished with the command (cd src/usr.sbin/mergemaster
236 Legacy ATA stack, disabled and replaced by new CAM-based one since
237 FreeBSD 9.0, completely removed from the sources. Kernel modules
238 atadisk and atapi*, user-level tools atacontrol and burncd are
239 removed. Kernel option `options ATA_CAM` is now permanently enabled
243 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
244 and socketpair(2). Software, in particular Kerberos, may
245 automatically detect and use these during building. The resulting
246 binaries will not work on older kernels.
249 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
250 information, see the respective 20130304 entry).
253 Recent commits to callout(9) changed the size of struct callout,
254 so the KBI is probably heavily disturbed. Also, some functions
255 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
256 by macros. Every kernel module using it won't load, so rebuild
259 The ctl device has been re-enabled in GENERIC for i386 and amd64,
260 but does not initialize by default (because of the new CTL_DISABLE
261 option) to save memory. To re-enable it, remove the CTL_DISABLE
262 option from the kernel config file or set kern.cam.ctl.disable=0
263 in /boot/loader.conf.
266 The ctl device has been disabled in GENERIC for i386 and amd64.
267 This was done due to the extra memory being allocated at system
268 initialisation time by the ctl driver which was only used if
269 a CAM target device was created. This makes a FreeBSD system
270 unusable on 128MB or less of RAM.
273 A new compression method (lz4) has been merged to -HEAD. Please
274 refer to zpool-features(7) for more information.
276 Please refer to the "ZFS notes" section of this file for information
277 on upgrading boot ZFS pools.
280 A BSD-licensed patch(1) variant has been added and is installed
281 as bsdpatch, being the GNU version the default patch.
282 To inverse the logic and use the BSD-licensed one as default,
283 while having the GNU version installed as gnupatch, rebuild
284 and install world with the WITH_BSD_PATCH knob set.
287 Due to the use of the new -l option to install(1) during build
288 and install, you must take care not to directly set the INSTALL
289 make variable in your /etc/make.conf, /etc/src.conf, or on the
290 command line. If you wish to use the -C flag for all installs
291 you may be able to add INSTALL+=-C to /etc/make.conf or
295 The install(1) option -M has changed meaning and now takes an
296 argument that is a file or path to append logs to. In the
297 unlikely event that -M was the last option on the command line
298 and the command line contained at least two files and a target
299 directory the first file will have logs appended to it. The -M
300 option served little practical purpose in the last decade so its
301 use is expected to be extremely rare.
304 After switching to Clang as the default compiler some users of ZFS
305 on i386 systems started to experience stack overflow kernel panics.
306 Please consider using 'options KSTACK_PAGES=4' in such configurations.
309 GEOM_LABEL now mangles label names read from file system metadata.
310 Mangling affect labels containing spaces, non-printable characters,
311 '%' or '"'. Device names in /etc/fstab and other places may need to
315 By default, only the 10 most recent kernel dumps will be saved. To
316 restore the previous behaviour (no limit on the number of kernel dumps
317 stored in the dump directory) add the following line to /etc/rc.conf:
322 With the addition of auditdistd(8), a new auditdistd user is now
323 required during installworld. "mergemaster -p" can be used to
324 add the user prior to installworld, as documented in the handbook.
327 The sin6_scope_id member variable in struct sockaddr_in6 is now
328 filled by the kernel before passing the structure to the userland via
329 sysctl or routing socket. This means the KAME-specific embedded scope
330 id in sin6_addr.s6_addr[2] is always cleared in userland application.
331 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
332 __FreeBSD_version is bumped to 1000025.
335 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
336 This means that the world and kernel will be compiled with clang
337 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
338 and /usr/bin/cpp. To disable this behavior and revert to building
339 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
340 of current may need to bootstrap WITHOUT_CLANG first if the clang
341 build fails (its compatibility window doesn't extend to the 9 stable
345 The IPFIREWALL_FORWARD kernel option has been removed. Its
346 functionality now turned on by default.
349 The ZERO_COPY_SOCKET kernel option has been removed and
350 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
351 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
352 mechanism which is not safe and may result in kernel crashes.
353 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
354 driver supports disposeable external page sized mbuf storage.
355 Proper replacements for both zero-copy mechanisms are under
356 consideration and will eventually lead to complete removal
357 of the two kernel options.
360 The IPv4 network stack has been converted to network byte
361 order. The following modules need to be recompiled together
362 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
363 pf(4), ipfw(4), ng_ipfw(4), stf(4).
366 Support for non-MPSAFE filesystems was removed from VFS. The
367 VFS_VERSION was bumped, all filesystem modules shall be
371 All the non-MPSAFE filesystems have been disconnected from
372 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
373 portalfs, smbfs, xfs.
376 The interface cloning API and ABI has changed. The following
377 modules need to be recompiled together with kernel:
378 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
379 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
380 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
383 The sdhci driver was split in two parts: sdhci (generic SD Host
384 Controller logic) and sdhci_pci (actual hardware driver).
385 No kernel config modifications are required, but if you
386 load sdhc as a module you must switch to sdhci_pci instead.
389 Import the FUSE kernel and userland support into base system.
392 The GNU sort(1) program has been removed since the BSD-licensed
393 sort(1) has been the default for quite some time and no serious
394 problems have been reported. The corresponding WITH_GNU_SORT
398 The pfil(9) API/ABI for AF_INET family has been changed. Packet
399 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
403 The net80211(4) ABI has been changed to allow for improved driver
404 PS-POLL and power-save support. All wireless drivers need to be
405 recompiled to work with the new kernel.
408 The random(4) support for the VIA hardware random number
409 generator (`PADLOCK') is no longer enabled unconditionally.
410 Add the padlock_rng device in the custom kernel config if
411 needed. The GENERIC kernels on i386 and amd64 do include the
412 device, so the change only affects the custom kernel
416 The pf(4) packet filter ABI has been changed. pfctl(8) and
417 snmp_pf module need to be recompiled to work with new kernel.
420 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
421 to -HEAD. Pools that have empty_bpobj in active state can not be
422 imported read-write with ZFS implementations that do not support
423 this feature. For more information read the zpool-features(5)
427 The sparc64 ZFS loader has been changed to no longer try to auto-
428 detect ZFS providers based on diskN aliases but now requires these
429 to be explicitly listed in the OFW boot-device environment variable.
432 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
433 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
434 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
437 The following sysctls and tunables have been renamed for consistency
438 with other variables:
439 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
440 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
443 The sort utility has been replaced with BSD sort. For now, GNU sort
444 is also available as "gnusort" or the default can be set back to
445 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
446 installed as "bsdsort".
449 A new version of ZFS (pool version 5000) has been merged to -HEAD.
450 Starting with this version the old system of ZFS pool versioning
451 is superseded by "feature flags". This concept enables forward
452 compatibility against certain future changes in functionality of ZFS
453 pools. The first read-only compatible "feature flag" for ZFS pools
454 is named "com.delphix:async_destroy". For more information
455 read the new zpool-features(5) manual page.
456 Please refer to the "ZFS notes" section of this file for information
457 on upgrading boot ZFS pools.
460 The malloc(3) implementation embedded in libc now uses sources imported
461 as contrib/jemalloc. The most disruptive API change is to
462 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
463 delete it prior to installworld, and optionally re-create it using the
464 new format after rebooting. See malloc.conf(5) for details
465 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
469 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
470 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
471 now spelled mips. This is to aid compatibility with third-party
472 software that expects this naming scheme in uname(3). Little-endian
473 settings are unchanged. If you are updating a big-endian mips64 machine
474 from before this change, you may need to set MACHINE_ARCH=mips64 in
475 your environment before the new build system will recognize your machine.
478 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
482 Now unix domain sockets behave "as expected" on nullfs(5). Previously
483 nullfs(5) did not pass through all behaviours to the underlying layer,
484 as a result if we bound to a socket on the lower layer we could connect
485 only to the lower path; if we bound to the upper layer we could connect
486 only to the upper path. The new behavior is one can connect to both the
487 lower and the upper paths regardless what layer path one binds to.
490 The getifaddrs upgrade path broken with 20111215 has been restored.
491 If you have upgraded in between 20111215 and 20120209 you need to
492 recompile libc again with your kernel. You still need to recompile
493 world to be able to configure CARP but this restriction already
497 The set_rcvar() function has been removed from /etc/rc.subr. All
498 base and ports rc.d scripts have been updated, so if you have a
499 port installed with a script in /usr/local/etc/rc.d you can either
500 hand-edit the rcvar= line, or reinstall the port.
502 An easy way to handle the mass-update of /etc/rc.d:
503 rm /etc/rc.d/* && mergemaster -i
506 panic(9) now stops other CPUs in the SMP systems, disables interrupts
507 on the current CPU and prevents other threads from running.
508 This behavior can be reverted using the kern.stop_scheduler_on_panic
510 The new behavior can be incompatible with kern.sync_on_panic.
513 The carp(4) facility has been changed significantly. Configuration
514 of the CARP protocol via ifconfig(8) has changed, as well as format
515 of CARP events submitted to devd(8) has changed. See manual pages
516 for more information. The arpbalance feature of carp(4) is currently
517 not supported anymore.
519 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
520 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
521 need to be recompiled.
524 The acpi_wmi(4) status device /dev/wmistat has been renamed to
528 The option VFS_ALLOW_NONMPSAFE option has been added in order to
529 explicitely support non-MPSAFE filesystems.
530 It is on by default for all supported platform at this present
534 The broken amd(4) driver has been replaced with esp(4) in the amd64,
535 i386 and pc98 GENERIC kernel configuration files.
538 sysinstall has been removed
541 The stable/9 branch created in subversion. This corresponds to the
542 RELENG_9 branch in CVS.
545 This commit modifies vfs_register() so that it uses a hash
546 calculation to set vfc_typenum, which is enabled by default.
547 The first time a system is booted after this change, the
548 vfc_typenum values will change for all file systems. The
549 main effect of this is a change to the NFS server file handles
550 for file systems that use vfc_typenum in their fsid, such as ZFS.
551 It will, however, prevent vfc_typenum from changing when file
552 systems are loaded in a different order for subsequent reboots.
553 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
554 until you are ready to remount all NFS clients after a reboot.
557 Bump the shared library version numbers for libraries that
558 do not use symbol versioning, have changed the ABI compared
559 to stable/8 and which shared library version was not bumped.
560 Done as part of 9.0-RELEASE cycle.
563 During the merge of Capsicum features, the fget(9) KPI was modified.
564 This may require the rebuilding of out-of-tree device drivers --
565 issues have been reported specifically with the nVidia device driver.
566 __FreeBSD_version is bumped to 900041.
568 Also, there is a period between 20110811 and 20110814 where the
569 special devices /dev/{stdin,stdout,stderr} did not work correctly.
570 Building world from a kernel during that window may not work.
573 The packet filter (pf) code has been updated to OpenBSD 4.5.
574 You need to update userland tools to be in sync with kernel.
575 This update breaks backward compatibility with earlier pfsync(4)
576 versions. Care must be taken when updating redundant firewall setups.
579 The following sysctls and tunables are retired on x86 platforms:
581 machdep.hlt_logical_cpus
582 The following sysctl is retired:
583 machdep.hyperthreading_allowed
584 The sysctls were supposed to provide a way to dynamically offline and
585 online selected CPUs on x86 platforms, but the implementation has not
586 been reliable especially with SCHED_ULE scheduler.
587 machdep.hyperthreading_allowed tunable is still available to ignore
588 hyperthreading CPUs at OS level.
589 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
590 where X is an APIC ID of a CPU. Be advised, though, that disabling
591 CPUs in non-uniform fashion will result in non-uniform topology and
592 may lead to sub-optimal system performance with SCHED_ULE, which is
596 cpumask_t type is retired and cpuset_t is used in order to describe
600 Changes to ifconfig(8) for dynamic address family detection mandate
601 that you are running a kernel of 20110525 or later. Make sure to
602 follow the update procedure to boot a new kernel before installing
606 Support for sun4v architecture is officially dropped
609 Several KPI breaking changes have been committed to the mii(4) layer,
610 the PHY drivers and consequently some Ethernet drivers using mii(4).
611 This means that miibus.ko and the modules of the affected Ethernet
612 drivers need to be recompiled.
614 Note to kernel developers: Given that the OUI bit reversion problem
615 was fixed as part of these changes all mii(4) commits related to OUIs,
616 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
617 handling, no longer can be merged verbatim to stable/8 and previous
621 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
622 into their kernel configurations along with 'device pci'.
625 The default NFS client is now the new NFS client, so fstype "newnfs"
626 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
627 Although mounts via fstype "nfs" will usually work without userland
628 changes, it is recommended that the mount(8) and mount_nfs(8)
629 commands be rebuilt from sources and that a link to mount_nfs called
630 mount_oldnfs be created. The new client is compiled into the
631 kernel with "options NFSCL" and this is needed for diskless root
632 file systems. The GENERIC kernel configs have been changed to use
633 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
634 To use the regular/old client, you can "mount -t oldnfs ...". For
635 a diskless root file system, you must also include a line like:
637 vfs.root.mountfrom="oldnfs:"
639 in the boot/loader.conf on the root fs on the NFS server to make
640 a diskless root fs use the old client.
643 The GENERIC kernels for all architectures now default to the new
644 CAM-based ATA stack. It means that all legacy ATA drivers were
645 removed and replaced by respective CAM drivers. If you are using
646 ATA device names in /etc/fstab or other places, make sure to update
647 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
648 where 'Y's are the sequential numbers starting from zero for each type
649 in order of detection, unless configured otherwise with tunables,
650 see cam(4)). There will be symbolic links created in /dev/ to map
651 old adX devices to the respective adaY. They should provide basic
652 compatibility for file systems mounting in most cases, but they do
653 not support old user-level APIs and do not have respective providers
654 in GEOM. Consider using updated management tools with new device names.
656 It is possible to load devices ahci, ata, siis and mvs as modules,
657 but option ATA_CAM should remain in kernel configuration to make ata
658 module work as CAM driver supporting legacy ATA controllers. Device ata
659 still can be used in modular fashion (atacore + ...). Modules atadisk
660 and atapi* are not used and won't affect operation in ATA_CAM mode.
661 Note that to use CAM-based ATA kernel should include CAM devices
662 scbus, pass, da (or explicitly ada), cd and optionally others. All of
663 them are parts of the cam module.
665 ataraid(4) functionality is now supported by the RAID GEOM class.
666 To use it you can load geom_raid kernel module and use graid(8) tool
667 for management. Instead of /dev/arX device names, use /dev/raid/rX.
669 No kernel config options or code have been removed, so if a problem
670 arises, please report it and optionally revert to the old ATA stack.
671 In order to do it you can remove from the kernel config:
676 , and instead add back:
677 device atadisk # ATA disk drives
678 device ataraid # ATA RAID drives
679 device atapicd # ATAPI CDROM drives
680 device atapifd # ATAPI floppy drives
681 device atapist # ATAPI tape drives
684 The default NFS server has been changed to the new server, which
685 was referred to as the experimental server. If you need to switch
686 back to the old NFS server, you must now put the "-o" option on
687 both the mountd and nfsd commands. This can be done using the
688 mountd_flags and nfs_server_flags rc.conf variables until an
689 update to the rc scripts is committed, which is coming soon.
692 The GNU Objective-C runtime library (libobjc), and other Objective-C
693 related components have been removed from the base system. If you
694 require an Objective-C library, please use one of the available ports.
697 ath(4) has been split into bus- and device- modules. if_ath contains
698 the HAL, the TX rate control and the network device code. if_ath_pci
699 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
700 contains the AHB glue. Users need to load both if_ath_pci and if_ath
701 in order to use ath on everything else.
703 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
704 need to load if_ath and if_ath_pci for ath(4) operation.
707 As part of the replacement of sysinstall, the process of building
708 release media has changed significantly. For details, please re-read
709 release(7), which has been updated to reflect the new build process.
712 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
713 is the last available version under GPLv2. It brings a number of new
714 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
715 4.1 and SSE 4.2), better support for powerpc64, a number of new
716 directives, and lots of other small improvements. See the ChangeLog
717 file in contrib/binutils for the full details.
720 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
721 compliant, and will now use half of hash for authentication.
722 This will break interoperability with all stacks (including all
723 actual FreeBSD versions) who implement
724 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
726 The only workaround with such peers is to use another HMAC
727 algorithm for IPsec ("phase 2") authentication.
730 Remove the uio_yield prototype and symbol. This function has
731 been misnamed since it was introduced and should not be
732 globally exposed with this name. The equivalent functionality
733 is now available using kern_yield(curthread->td_user_pri).
734 The function remains undocumented.
737 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
738 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
739 for scalar sysctls is defined but disabled. Code that needs
740 UQUAD to pass the type checking that must compile on older
741 systems where the define is not present can check against
742 __FreeBSD_version >= 900030.
744 The system dialog(1) has been replaced with a new version previously
745 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
746 with the previous version, but the libdialog associated with it has
747 a largely incompatible API. As such, the original version of libdialog
748 will be kept temporarily as libodialog, until its base system consumers
749 are replaced or updated. Bump __FreeBSD_version to 900030.
752 If you are trying to run make universe on a -stable system, and you get
753 the following warning:
754 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
755 unknown. config(8) likely too old."
756 or something similar to it, then you must upgrade your -stable system
757 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
758 stable/8) or build the config from the latest stable/8 branch and
759 install it on your system.
761 Prior to this date, building a current universe on 8-stable system from
762 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
763 error in the first kernel build phase. A new config on those old
764 systems will fix that problem for older versions of -current.
767 The TCP stack has been modified to allow Khelp modules to interact with
768 it via helper hook points and store per-connection data in the TCP
769 control block. Bump __FreeBSD_version to 900029. User space tools that
770 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
774 Generic IEEE 802.3 annex 31B full duplex flow control support has been
775 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
776 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
777 to take advantage of it instead of using custom implementations. This
778 means that these drivers now no longer unconditionally advertise
779 support for flow control but only do so if flow control is a selected
780 media option. This was implemented in the generic support that way in
781 order to allow flow control to be switched on and off via ifconfig(8)
782 with the PHY specific default to typically off in order to protect
783 from unwanted effects. Consequently, if you used flow control with
784 one of the above mentioned drivers you now need to explicitly enable
786 ifconfig bge0 media auto mediaopt flowcontrol
788 Along with the above mentioned changes generic support for setting
789 1000baseT master mode also has been added and brgphy(4), ciphy(4),
790 e1000phy(4) as well as ip1000phy(4) have been converted to take
791 advantage of it. This means that these drivers now no longer take the
792 link0 parameter for selecting master mode but the master media option
793 has to be used instead, for example like in the following:
794 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
796 Selection of master mode now is also available with all other PHY
797 drivers supporting 1000baseT.
800 The TCP stack has received a significant update to add support for
801 modularised congestion control and generally improve the clarity of
802 congestion control decisions. Bump __FreeBSD_version to 900025. User
803 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
804 sockstat) need to be recompiled.
807 The man(1) utility has been replaced by a new version that no longer
808 uses /etc/manpath.config. Please consult man.conf(5) for how to
809 migrate local entries to the new format.
812 The copyright strings printed by login(1) and sshd(8) at the time of a
813 new connection have been removed to follow other operating systems and
817 A workaround for a fixed ld bug has been removed in kernel code,
818 so make sure that your system ld is built from sources after
819 revision 210245 from 2010-07-19 (r211583 if building head kernel
820 on stable/8, r211584 for stable/7; both from 2010-08-21).
821 A symptom of incorrect ld version is different addresses for
822 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
825 The $ipv6_prefer variable in rc.conf(5) has been split into
826 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
828 The $ip6addrctl_policy is a variable to choose a pre-defined
829 address selection policy set by ip6addrctl(8). A value
830 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
833 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
834 flag (see an entry of 20090926) is set on an interface with no
835 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
836 security reason. If you want IPv6 link-local address on all
837 interfaces by default, set this to "YES".
839 The old ipv6_prefer="YES" is equivalent to
840 ipv6_activate_all_interfaces="YES" and
841 ip6addrctl_policy="ipv6_prefer".
844 DTrace has grown support for userland tracing. Due to this, DTrace is
845 now i386 and amd64 only.
846 dtruss(1) is now installed by default on those systems and a new
847 kernel module is needed for userland tracing: fasttrap.
848 No changes to your kernel config file are necessary to enable
849 userland tracing, but you might consider adding 'STRIP=' and
850 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
851 to have informative userland stack traces in DTrace (ustack).
854 The acpi_aiboost(4) driver has been removed in favor of the new
855 aibs(4) driver. You should update your kernel configuration file.
858 BSD grep has been imported to the base system and it is built by
859 default. It is completely BSD licensed, highly GNU-compatible, uses
860 less memory than its GNU counterpart and has a small codebase.
861 However, it is slower than its GNU counterpart, which is mostly
862 noticeable for larger searches, for smaller ones it is measurable
863 but not significant. The reason is complex, the most important factor
864 is that we lack a modern and efficient regex library and GNU
865 overcomes this by optimizing the searches internally. Future work
866 on improving the regex performance is planned, for the meantime,
867 users that need better performance, can build GNU grep instead by
868 setting the WITH_GNU_GREP knob.
871 Due to the import of powerpc64 support, all existing powerpc kernel
872 configuration files must be updated with a machine directive like this:
873 machine powerpc powerpc
875 In addition, an updated config(8) is required to build powerpc kernels
879 A new version of ZFS (version 15) has been merged to -HEAD.
880 This version uses a python library for the following subcommands:
881 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
882 For full functionality of these commands the following port must
883 be installed: sysutils/py-zfs
886 'vm_page's are now hashed by physical address to an array of mutexes.
887 Currently this is only used to serialize access to hold_count. Over
888 time the page queue mutex will be peeled away. This changes the size
889 of pmap on every architecture. And requires all callers of vm_page_hold
890 and vm_page_unhold to be updated.
893 WITH_CTF can now be specified in src.conf (not recommended, there
894 are some problems with static executables), make.conf (would also
895 affect ports which do not use GNU make and do not override the
896 compile targets) or in the kernel config (via "makeoptions
898 When WITH_CTF was specified there before this was silently ignored,
899 so make sure that WITH_CTF is not used in places which could lead
900 to unwanted behavior.
903 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
904 to allow 32-bit compatibility on non-x86 platforms. All kernel
905 configurations on amd64 and ia64 platforms using these options must
906 be modified accordingly.
909 The utmp user accounting database has been replaced with utmpx,
910 the user accounting interface standardized by POSIX.
911 Unfortunately the semantics of utmp and utmpx don't match,
912 making it practically impossible to support both interfaces.
913 The user accounting database is used by tools like finger(1),
914 last(1), talk(1), w(1) and ac(8).
916 All applications in the base system use utmpx. This means only
917 local binaries (e.g. from the ports tree) may still use these
918 utmp database files. These applications must be rebuilt to make
921 After the system has been upgraded, it is safe to remove the old
922 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
923 assuming their contents is of no importance anymore. Old wtmp
924 databases can only be used by last(1) and ac(8) after they have
925 been converted to the new format using wtmpcvt(1).
928 Introduce the kernel thread "deadlock resolver" (which can be enabled
929 via the DEADLKRES option, see NOTES for more details) and the
930 sleepq_type() function for sleepqueues.
933 The rc.firewall and rc.firewall6 were unified, and
934 rc.firewall6 and rc.d/ip6fw were removed.
935 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
936 variables are obsoleted. Instead, the following new rc
937 variables are added to rc.d/ipfw:
939 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
940 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
941 firewall_simple_onet_ipv6, firewall_trusted_ipv6
943 The meanings correspond to the relevant IPv4 variables.
949 The default terminal emulation for syscons(4) has been changed
950 from cons25 to xterm on all platforms except pc98. This means
951 that the /etc/ttys file needs to be updated to ensure correct
952 operation of applications on the console.
954 The terminal emulation style can be toggled per window by using
955 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
956 options can be used to change the compile-time default back to
959 To prevent graphical artifacts, make sure the TERM environment
960 variable is set to match the terminal emulation that is being
961 performed by syscons(4).
964 The layout of the structure ieee80211req_scan_result has changed.
965 Applications that require wireless scan results (e.g. ifconfig(8))
966 from net80211 need to be recompiled.
968 Applications such as wpa_supplicant(8) may require a full world
969 build without using NO_CLEAN in order to get synchronized with the
973 The iwn(4) driver has been updated to support the 5000 and 5150 series.
974 There's one kernel module for each firmware. Adding "device iwnfw"
975 to the kernel configuration file means including all three firmware
976 images inside the kernel. If you want to include just the one for
977 your wireless card, use the devices iwn4965fw, iwn5000fw or
981 The rc.d/network_ipv6, IPv6 configuration script has been integrated
982 into rc.d/netif. The changes are the following:
984 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
985 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
986 Note that both variables need the "inet6" keyword at the head.
988 Do not set $ipv6_network_interfaces manually if you do not
989 understand what you are doing. It is not needed in most cases.
991 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
994 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
995 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
997 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
998 all configured interfaces have "inet6 accept_rtadv" in the
999 $ifconfig_IF_ipv6. These are for backward compatibility.
1001 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1002 functionality of interfaces with no corresponding
1003 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1004 and the default address selection policy of ip6addrctl(8)
1005 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1006 Note that if you want to configure IPv6 functionality on the
1007 disabled interfaces after boot, first you need to clear the flag by
1008 using ifconfig(8) like:
1010 ifconfig em0 inet6 -ifdisabled
1012 If YES, the default address selection policy is set as
1015 The default value of $ipv6_prefer is NO.
1017 4. If your system need to receive Router Advertisement messages,
1018 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1019 scripts automatically invoke rtsol(8) when the interface becomes
1020 UP. The Router Advertisement messages are used for SLAAC
1021 (State-Less Address AutoConfiguration).
1024 802.11s D3.03 support was committed. This is incompatible with the
1025 previous code, which was based on D3.0.
1028 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1029 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1030 control whether accepting Router Advertisement messages or not.
1031 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1032 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1033 The ifconfig(8) utility now supports these flags.
1036 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1037 mount(8) and -a option for df(1) to see them.
1040 The old tunable hw.bus.devctl_disable has been superseded by
1041 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1042 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1046 Remove the option STOP_NMI. The default action is now to use NMI only
1047 for KDB via the newly introduced function stop_cpus_hard() and
1048 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1051 The stable/8 branch created in subversion. This corresponds to the
1052 RELENG_8 branch in CVS.
1055 Bump the shared library version numbers for all libraries that do not
1056 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1057 __FreeBSD_version to 800105.
1060 Due to changes in the implementation of virtual network stack support,
1061 all network-related kernel modules must be recompiled. As this change
1062 breaks the ABI, bump __FreeBSD_version to 800104.
1065 The TOE interface to the TCP syncache has been modified to remove
1066 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1067 The cxgb driver is the only TOE consumer affected by this change, and
1068 needs to be recompiled along with the kernel. As this change breaks
1069 the ABI, bump __FreeBSD_version to 800103.
1072 Padding has been added to struct tcpcb, sackhint and tcpstat in
1073 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1074 maintaining the ABI. However, this change breaks the ABI, so bump
1075 __FreeBSD_version to 800102. User space tools that rely on the size of
1076 any of these structs (e.g. sockstat) need to be recompiled.
1079 The NFS_LEGACYRPC option has been removed along with the old kernel
1080 RPC implementation that this option selected. Kernel configurations
1081 may need to be adjusted.
1084 The network interface device nodes at /dev/net/<interface> have been
1085 removed. All ioctl operations can be performed the normal way using
1086 routing sockets. The kqueue functionality can generally be replaced
1087 with routing sockets.
1090 The documentation from the FreeBSD Documentation Project (Handbook,
1091 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1092 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1095 The ABI of various structures related to the SYSV IPC API have been
1096 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1097 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1101 Layout of struct vnet has changed as routing related variables were
1102 moved to their own Vimage module. Modules need to be recompiled. Bump
1103 __FreeBSD_version to 800099.
1106 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1107 respectively. As long as no more than 16 groups per process are used,
1108 no changes should be visible. When more than 16 groups are used, old
1109 binaries may fail if they call getgroups() or getgrouplist() with
1110 statically sized storage. Recompiling will work around this, but
1111 applications should be modified to use dynamically allocated storage
1112 for group arrays as POSIX.1-2008 does not cap an implementation's
1113 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1115 NFS and portalfs mounts may also be affected as the list of groups is
1116 truncated to 16. Users of NFS who use more than 16 groups, should
1117 take care that negative group permissions are not used on the exported
1118 file systems as they will not be reliable unless a GSSAPI based
1119 authentication method is used.
1122 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1123 option compiles in the support for adaptive spinning for lockmgrs
1124 which want to enable it. The lockinit() function now accepts the flag
1125 LK_ADAPTIVE in order to make the lock object subject to adaptive
1126 spinning when both held in write and read mode.
1129 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1130 changed. User applications that use this ioctl need to be rebuilt.
1133 The layout of struct thread has changed. Kernel and modules need to
1137 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1138 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1141 window(1) has been removed from the base system. It can now be
1142 installed from ports. The port is called misc/window.
1145 The way we are storing and accessing `routing table' entries has
1146 changed. Programs reading the FIB, like netstat, need to be
1150 A new netisr implementation has been added for FreeBSD 8. Network
1151 file system modules, such as igmp, ipdivert, and others, should be
1153 Bump __FreeBSD_version to 800096.
1156 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1160 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1161 Bump __FreeBSD_version to 800094.
1164 Add mnt_xflag field to 'struct mount'. File system modules need to be
1166 Bump __FreeBSD_version to 800093.
1169 The compiling option ADAPTIVE_SX has been retired while it has been
1170 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1171 The KPI for sx_init_flags() changes as accepting flags:
1172 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1173 been introduced in order to handle the reversed logic.
1174 Bump __FreeBSD_version to 800092.
1177 Add support for hierarchical jails. Remove global securelevel.
1178 Bump __FreeBSD_version to 800091.
1181 The layout of struct vnet_net has changed, therefore modules
1183 Bump __FreeBSD_version to 800090.
1186 The newly imported zic(8) produces a new format in the output. Please
1187 run tzsetup(8) to install the newly created data to /etc/localtime.
1190 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1191 hw.usb.* and is now consistent again with previous releases.
1194 802.11 monitor mode support was revised and driver api's were changed.
1195 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1196 of DLT_IEEE802_11. No user-visible data structures were changed but
1197 applications that use DLT_IEEE802_11 may require changes.
1198 Bump __FreeBSD_version to 800088.
1201 The layout of the following structs has changed: sysctl_oid,
1202 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1203 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1204 panics may be experienced. World rebuild is required for
1205 correctly checking networking state from userland.
1206 Bump __FreeBSD_version to 800085.
1209 MLDv2 and Source-Specific Multicast (SSM) have been merged
1210 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1211 The implementation of SSM within FreeBSD's IPv6 stack closely
1212 follows the IPv4 implementation.
1214 For kernel developers:
1216 * The most important changes are that the ip6_output() and
1217 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1218 and this lock has been downgraded to a non-recursive mutex.
1220 * As with the changes to the IPv4 stack to support SSM, filtering
1221 of inbound multicast traffic must now be performed by transport
1222 protocols within the IPv6 stack. This does not apply to TCP and
1223 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1225 * The KPIs used by IPv6 multicast are similar to those used by
1226 the IPv4 stack, with the following differences:
1227 * im6o_mc_filter() is analogous to imo_multicast_filter().
1228 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1229 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1230 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1231 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1232 for MLDv1 have an additional 'timer' argument which is used to
1233 jitter the initial membership report for the solicited-node
1234 multicast membership on-link.
1235 * This is not strictly needed for MLDv2, which already jitters
1236 its report transmissions. However, the 'timer' argument is
1237 preserved in case MLDv1 is active on the interface.
1239 * The KAME linked-list based IPv6 membership implementation has
1240 been refactored to use a vector similar to that used by the IPv4
1242 Code which maintains a list of its own multicast memberships
1243 internally, e.g. carp, has been updated to reflect the new
1246 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1247 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1248 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1249 implementation constraint which needs to be addressed in HEAD.
1251 For application developers:
1253 * The changes are broadly similar to those made for the IPv4
1256 * The use of IPv4 and IPv6 multicast socket options on the same
1257 socket, using mapped addresses, HAS NOT been tested or supported.
1259 * There are a number of issues with the implementation of various
1260 IPv6 multicast APIs which need to be resolved in the API surface
1261 before the implementation is fully compatible with KAME userland
1262 use, and these are mostly to do with interface index treatment.
1264 * The literature available discusses the use of either the delta / ASM
1265 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1266 using setsourcefilter(3)/getsourcefilter(3). For more information
1267 please refer to RFC 3768, 'Socket Interface Extensions for
1268 Multicast Source Filters'.
1270 * Applications which use the published RFC 3678 APIs should be fine.
1272 For systems administrators:
1274 * The mtest(8) utility has been refactored to support IPv6, in
1275 addition to IPv4. Interface addresses are no longer accepted
1276 as arguments, their names must be used instead. The utility
1277 will map the interface name to its first IPv4 address as
1278 returned by getifaddrs(3).
1280 * The ifmcstat(8) utility has also been updated to print the MLDv2
1281 endpoint state and source filter lists via sysctl(3).
1283 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1284 loopback of IPv6 multicast datagrams by default; it defaults to 1
1285 to preserve the existing behaviour. Disabling multicast loopback is
1286 recommended for optimal system performance.
1288 * The IPv6 MROUTING code has been changed to examine this sysctl
1289 instead of attempting to perform a group lookup before looping
1290 back forwarded datagrams.
1292 Bump __FreeBSD_version to 800084.
1295 Implement low-level Bluetooth HCI API.
1296 Bump __FreeBSD_version to 800083.
1299 The layout of struct malloc_type, used by modules to register new
1300 memory allocation types, has changed. Most modules will need to
1301 be rebuilt or panics may be experienced.
1302 Bump __FreeBSD_version to 800081.
1305 Anticipate overflowing inp_flags - add inp_flags2.
1306 This changes most offsets in inpcb, so checking v4 connection
1307 state will require a world rebuild.
1308 Bump __FreeBSD_version to 800080.
1311 Add an llentry to struct route and struct route_in6. Modules
1312 embedding a struct route will need to be recompiled.
1313 Bump __FreeBSD_version to 800079.
1316 The size of rt_metrics_lite and by extension rtentry has changed.
1317 Networking administration apps will need to be recompiled.
1318 The route command now supports show as an alias for get, weighting
1319 of routes, sticky and nostick flags to alter the behavior of stateful
1321 Bump __FreeBSD_version to 800078.
1324 Do not use Giant for kbdmux(4) locking. This is wrong and
1325 apparently causing more problems than it solves. This will
1326 re-open the issue where interrupt handlers may race with
1327 kbdmux(4) in polling mode. Typical symptoms include (but
1328 not limited to) duplicated and/or missing characters when
1329 low level console functions (such as gets) are used while
1330 interrupts are enabled (for example geli password prompt,
1331 mountroot prompt etc.). Disabling kbdmux(4) may help.
1334 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1335 kernel modules referencing any of the above need to be recompiled.
1336 Bump __FreeBSD_version to 800075.
1339 GEOM_PART has become the default partition slicer for storage devices,
1340 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1341 introduces some changes:
1343 MSDOS/EBR: the devices created from MSDOS extended partition entries
1344 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1345 to devices with offset-based names. fstabs may need to be modified.
1347 BSD: the "geometry does not match label" warning is harmless in most
1348 cases but it points to problems in file system misalignment with
1349 disk geometry. The "c" partition is now implicit, covers the whole
1350 top-level drive and cannot be (mis)used by users.
1352 General: Kernel dumps are now not allowed to be written to devices
1353 whose partition types indicate they are meant to be used for file
1354 systems (or, in case of MSDOS partitions, as something else than
1357 Most of these changes date approximately from 200812.
1360 The uscanner(4) driver has been removed from the kernel. This follows
1361 Linux removing theirs in 2.6 and making libusb the default interface
1362 (supported by sane).
1365 The multicast forwarding code has been cleaned up. netstat(1)
1366 only relies on KVM now for printing bandwidth upcall meters.
1367 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1368 ip6_mroute_mod respectively. The config(5) options for statically
1369 compiling this code remain the same, i.e. 'options MROUTING'.
1372 Support for the IFF_NEEDSGIANT network interface flag has been
1373 removed, which means that non-MPSAFE network device drivers are no
1374 longer supported. In particular, if_ar, if_sr, and network device
1375 drivers from the old (legacy) USB stack can no longer be built or
1379 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1380 a bunch of new language catalog files have also been added.
1381 This means that some common libc messages are now localized and
1382 they depend on the LC_MESSAGES environmental variable.
1385 The k8temp(4) driver has been renamed to amdtemp(4) since
1386 support for Family 10 and Family 11 CPU families was added.
1389 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1390 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1392 For kernel developers, the most important changes are that the
1393 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1394 and this lock has been downgraded to a non-recursive mutex.
1396 Transport protocols (UDP, Raw IP) are now responsible for filtering
1397 inbound multicast traffic according to group membership and source
1398 filters. The imo_multicast_filter() KPI exists for this purpose.
1399 Transports which do not use multicast (SCTP, TCP) already reject
1400 multicast by default. Forwarding and receive performance may improve
1401 as a mutex acquisition is no longer needed in the ip_input()
1402 low-level input path. in_addmulti() and in_delmulti() are shimmed
1403 to new KPIs which exist to support SSM in-kernel.
1405 For application developers, it is recommended that loopback of
1406 multicast datagrams be disabled for best performance, as this
1407 will still cause the lock to be taken for each looped-back
1408 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1409 be tuned to 0 to disable loopback by default; it defaults to 1
1410 to preserve the existing behaviour.
1412 For systems administrators, to obtain best performance with
1413 multicast reception and multiple groups, it is always recommended
1414 that a card with a suitably precise hash filter is used. Hash
1415 collisions will still result in the lock being taken within the
1416 transport protocol input path to check group membership.
1418 If deploying FreeBSD in an environment with IGMP snooping switches,
1419 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1420 enabled; this forces 224.0.0.0/24 group membership to be announced
1423 The size of 'struct igmpstat' has changed; netstat needs to be
1424 recompiled to reflect this.
1425 Bump __FreeBSD_version to 800070.
1428 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1429 updated to use it. This requires a buildworld/installworld in order to
1430 update the library and dependencies (usbconfig, etc). Its advisable to
1431 rebuild all ports which uses libusb. More specific directions are given
1432 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1433 libusb are no longer required and can be removed.
1436 A workaround is committed to allow the creation of System V shared
1437 memory segment of size > 2 GB on the 64-bit architectures.
1438 Due to a limitation of the existing ABI, the shm_segsz member
1439 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1440 wrong for large segments. Note that limits must be explicitly
1441 raised to allow such segments to be created.
1444 The layout of struct ifnet has changed, requiring a rebuild of all
1445 network device driver modules.
1448 The /dev handling for the new USB stack has changed, a
1449 buildworld/installworld is required for libusb20.
1452 The new USB2 stack has now been permanently moved in and all kernel and
1453 module names reverted to their previous values (eg, usb, ehci, ohci,
1454 ums, ...). The old usb stack can be compiled in by prefixing the name
1455 with the letter 'o', the old usb modules have been removed.
1456 Updating entry 20090216 for xorg and 20090215 for libmap may still
1460 The rc.conf(5) option if_up_delay has been renamed to
1461 defaultroute_delay to better reflect its purpose. If you have
1462 customized this setting in /etc/rc.conf you need to update it to
1466 xorg 7.4 wants to configure its input devices via hald which does not
1467 yet work with USB2. If the keyboard/mouse does not work in xorg then
1469 Option "AllowEmptyInput" "off"
1470 to your ServerLayout section. This will cause X to use the configured
1471 kbd and mouse sections from your xorg.conf.
1474 The GENERIC kernels for all architectures now default to the new USB2
1475 stack. No kernel config options or code have been removed so if a
1476 problem arises please report it and optionally revert to the old USB
1477 stack. If you are loading USB kernel modules or have a custom kernel
1478 that includes GENERIC then ensure that usb names are also changed over,
1479 eg uftdi -> usb2_serial_ftdi.
1481 Older programs linked against the ports libusb 0.1 need to be
1482 redirected to the new stack's libusb20. /etc/libmap.conf can
1484 # Map old usb library to new one for usb2 stack
1485 libusb-0.1.so.8 libusb20.so.1
1488 All USB ethernet devices now attach as interfaces under the name ueN
1489 (eg. ue0). This is to provide a predictable name as vendors often
1490 change usb chipsets in a product without notice.
1493 The ichsmb(4) driver has been changed to require SMBus slave
1494 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1495 All of the other SMBus controller drivers require left-justified
1496 slave addresses, so this change makes all the drivers provide the
1500 INET6 statistics (struct ip6stat) was updated.
1501 netstat(1) needs to be recompiled.
1504 NTFS has been removed from GENERIC kernel on amd64 to match
1505 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1506 will load ntfs.ko module automatically when NTFS support is
1507 actually needed, unless ntfs.ko is not installed or security
1508 level prohibits loading kernel modules. If either is the case,
1509 "options NTFS" has to be added into kernel config.
1512 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1513 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1514 800061. User space tools that rely on the size of struct tcpcb in
1515 tcp_var.h (e.g. sockstat) need to be recompiled.
1518 ng_tty(4) module updated to match the new TTY subsystem.
1519 Due to API change, user-level applications must be updated.
1520 New API support added to mpd5 CVS and expected to be present
1521 in next mpd5.3 release.
1524 With __FreeBSD_version 800060 the makefs tool is part of
1525 the base system (it was a port).
1528 The afdata and ifnet locks have been changed from mutexes to
1529 rwlocks, network modules will need to be re-compiled.
1532 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1533 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1534 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1535 architecture and 40 bytes on 64-bit architecture. The userland
1536 applications "arp" and "ndp" have been updated accordingly.
1537 The output from "netstat -r" shows only routing entries and
1538 none of the L2 information.
1541 __FreeBSD_version 800057 marks the switchover from the
1542 binary ath hal to source code. Users must add the line:
1544 options AH_SUPPORT_AR5416
1546 to their kernel config files when specifying:
1550 The ath_hal module no longer exists; the code is now compiled
1551 together with the driver in the ath module. It is now
1552 possible to tailor chip support (i.e. reduce the set of chips
1553 and thereby the code size); consult ath_hal(4) for details.
1556 __FreeBSD_version 800054 adds memory barriers to
1557 <machine/atomic.h>, new interfaces to ifnet to facilitate
1558 multiple hardware transmit queues for cards that support
1559 them, and a lock-less ring-buffer implementation to
1560 enable drivers to more efficiently manage queueing of
1564 A new version of ZFS (version 13) has been merged to -HEAD.
1565 This version has zpool attribute "listsnapshots" off by
1566 default, which means "zfs list" does not show snapshots,
1567 and is the same as Solaris behavior.
1570 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1573 The uhci, ohci, ehci and slhci USB Host controller drivers have
1574 been put into separate modules. If you load the usb module
1575 separately through loader.conf you will need to load the
1576 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1577 controller add the following to loader.conf:
1583 The ABI used by the PMC toolset has changed. Please keep
1584 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1588 atapci kernel module now includes only generic PCI ATA
1589 driver. AHCI driver moved to ataahci kernel module.
1590 All vendor-specific code moved into separate kernel modules:
1591 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1592 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1593 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1594 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1597 The TTY subsystem of the kernel has been replaced by a new
1598 implementation, which provides better scalability and an
1599 improved driver model. Most common drivers have been migrated to
1600 the new TTY subsystem, while others have not. The following
1601 drivers have not yet been ported to the new TTY layer:
1604 cy, digi, rc, rp, sio
1610 ng_h4, ng_tty, ppp, sl, snp
1612 Adding these drivers to your kernel configuration file shall
1613 cause compilation to fail.
1616 ntpd has been upgraded to 4.2.4p5.
1619 OpenSSH has been upgraded to 5.1p1.
1621 For many years, FreeBSD's version of OpenSSH preferred DSA
1622 over RSA for host and user authentication keys. With this
1623 upgrade, we've switched to the vendor's default of RSA over
1624 DSA. This may cause upgraded clients to warn about unknown
1625 host keys even for previously known hosts. Users should
1626 follow the usual procedure for verifying host keys before
1627 accepting the RSA key.
1629 This can be circumvented by setting the "HostKeyAlgorithms"
1630 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1633 Please note that the sequence of keys offered for
1634 authentication has been changed as well. You may want to
1635 specify IdentityFile in a different order to revert this
1639 The sio(4) driver has been removed from the i386 and amd64
1640 kernel configuration files. This means uart(4) is now the
1641 default serial port driver on those platforms as well.
1643 To prevent collisions with the sio(4) driver, the uart(4) driver
1644 uses different names for its device nodes. This means the
1645 onboard serial port will now most likely be called "ttyu0"
1646 instead of "ttyd0". You may need to reconfigure applications to
1647 use the new device names.
1649 When using the serial port as a boot console, be sure to update
1650 /boot/device.hints and /etc/ttys before booting the new kernel.
1651 If you forget to do so, you can still manually specify the hints
1652 at the loader prompt:
1654 set hint.uart.0.at="isa"
1655 set hint.uart.0.port="0x3F8"
1656 set hint.uart.0.flags="0x10"
1657 set hint.uart.0.irq="4"
1661 The gpt(8) utility has been removed. Use gpart(8) to partition
1665 The version that Linuxulator emulates was changed from 2.4.2
1666 to 2.6.16. If you experience any problems with Linux binaries
1667 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1668 if it fixes the problem contact emulation mailing list.
1671 ISDN4BSD (I4B) was removed from the src tree. You may need to
1672 update a your kernel configuration and remove relevant entries.
1675 I have checked in code to support multiple routing tables.
1676 See the man pages setfib(1) and setfib(2).
1677 This is a hopefully backwards compatible version,
1678 but to make use of it you need to compile your kernel
1679 with options ROUTETABLES=2 (or more up to 16).
1682 The 802.11 wireless support was redone to enable multi-bss
1683 operation on devices that are capable. The underlying device
1684 is no longer used directly but instead wlanX devices are
1685 cloned with ifconfig. This requires changes to rc.conf files.
1686 For example, change:
1687 ifconfig_ath0="WPA DHCP"
1690 ifconfig_wlan0="WPA DHCP"
1691 see rc.conf(5) for more details. In addition, mergemaster of
1692 /etc/rc.d is highly recommended. Simultaneous update of userland
1693 and kernel wouldn't hurt either.
1695 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1696 modules were merged into the base wlan module. All references
1697 to these modules (e.g. in kernel config files) must be removed.
1700 psm(4) has gained write(2) support in native operation level.
1701 Arbitrary commands can be written to /dev/psm%d and status can
1702 be read back from it. Therefore, an application is responsible
1703 for status validation and error recovery. It is a no-op in
1704 other operation levels.
1707 Support for KSE threading has been removed from the kernel. To
1708 run legacy applications linked against KSE libmap.conf may
1709 be used. The following libmap.conf may be used to ensure
1710 compatibility with any prior release:
1712 libpthread.so.1 libthr.so.1
1713 libpthread.so.2 libthr.so.2
1714 libkse.so.3 libthr.so.3
1717 The layout of struct vmspace has changed. This affects libkvm
1718 and any executables that link against libkvm and use the
1719 kvm_getprocs() function. In particular, but not exclusively,
1720 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1721 The effects are minimal, but it's advisable to upgrade world
1725 The latest em driver no longer has support in it for the
1726 82575 adapter, this is now moved to the igb driver. The
1727 split was done to make new features that are incompatible
1728 with older hardware easier to do.
1731 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1732 likewise the kernel option is now GEOM_LINUX_LVM.
1735 The default NFS mount mode has changed from UDP to TCP for
1736 increased reliability. If you rely on (insecurely) NFS
1737 mounting across a firewall you may need to update your
1741 Belatedly note the addition of m_collapse for compacting
1745 The fts(3) structures have been changed to use adequate
1746 integer types for their members and so to be able to cope
1747 with huge file trees. The old fts(3) ABI is preserved
1748 through symbol versioning in libc, so third-party binaries
1749 using fts(3) should still work, although they will not take
1750 advantage of the extended types. At the same time, some
1751 third-party software might fail to build after this change
1752 due to unportable assumptions made in its source code about
1753 fts(3) structure members. Such software should be fixed
1754 by its vendor or, in the worst case, in the ports tree.
1755 FreeBSD_version 800015 marks this change for the unlikely
1756 case that a portable fix is impossible.
1759 To upgrade to -current after this date, you must be running
1760 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1761 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1764 The ADAPTIVE_GIANT kernel option has been retired because its
1765 functionality is the default now.
1768 The AT keyboard emulation of sunkbd(4) has been turned on
1769 by default. In order to make the special symbols of the Sun
1770 keyboards driven by sunkbd(4) work under X these now have
1771 to be configured the same way as Sun USB keyboards driven
1772 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1774 Option "XkbLayout" "us"
1775 Option "XkbRules" "xorg"
1776 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1779 It has been decided that it is desirable to provide ABI
1780 backwards compatibility to the FreeBSD 4/5/6 versions of the
1781 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1782 broken with the introduction of PCI domain support (see the
1783 20070930 entry). Unfortunately, this required the ABI of
1784 PCIOCGETCONF to be broken again in order to be able to
1785 provide backwards compatibility to the old version of that
1786 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1787 again. As for prominent ports this affects neither pciutils
1788 nor xorg-server this time, the hal port needs to be rebuilt
1792 The misnamed kthread_create() and friends have been renamed
1793 to kproc_create() etc. Many of the callers already
1794 used kproc_start()..
1795 I will return kthread_create() and friends in a while
1796 with implementations that actually create threads, not procs.
1797 Renaming corresponds with version 800002.
1806 Avoid using make -j when upgrading. While generally safe, there are
1807 sometimes problems using -j to upgrade. If your upgrade fails with
1808 -j, please try again without -j. From time to time in the past there
1809 have been problems using -j with buildworld and/or installworld. This
1810 is especially true when upgrading between "distant" versions (eg one
1811 that cross a major release boundary or several minor releases, or when
1812 several months have passed on the -current branch).
1814 Sometimes, obscure build problems are the result of environment
1815 poisoning. This can happen because the make utility reads its
1816 environment when searching for values for global variables. To run
1817 your build attempts in an "environmental clean room", prefix all make
1818 commands with 'env -i '. See the env(1) manual page for more details.
1820 When upgrading from one major version to another it is generally best
1821 to upgrade to the latest code in the currently installed branch first,
1822 then do an upgrade to the new branch. This is the best-tested upgrade
1823 path, and has the highest probability of being successful. Please try
1824 this approach before reporting problems with a major version upgrade.
1826 When upgrading a live system, having a root shell around before
1827 installing anything can help undo problems. Not having a root shell
1828 around can lead to problems if pam has changed too much from your
1829 starting point to allow continued authentication after the upgrade.
1833 When upgrading the boot ZFS pool to a new version, always follow
1836 1.) recompile and reinstall the ZFS boot loader and boot block
1837 (this is part of "make buildworld" and "make installworld")
1839 2.) update the ZFS boot block on your boot drive
1841 The following example updates the ZFS boot block on the first
1842 partition (freebsd-boot) of a GPT partitioned drive ad0:
1843 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1845 Non-boot pools do not need these updates.
1849 If you are updating from a prior version of FreeBSD (even one just
1850 a few days old), you should follow this procedure. It is the most
1851 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1853 make kernel-toolchain
1854 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1855 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1857 To test a kernel once
1858 ---------------------
1859 If you just want to boot a kernel once (because you are not sure
1860 if it works, or if you want to boot a known bad kernel to provide
1861 debugging information) run
1862 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1863 nextboot -k testkernel
1865 To just build a kernel when you know that it won't mess you up
1866 --------------------------------------------------------------
1867 This assumes you are already running a CURRENT system. Replace
1868 ${arch} with the architecture of your machine (e.g. "i386",
1869 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1871 cd src/sys/${arch}/conf
1872 config KERNEL_NAME_HERE
1873 cd ../compile/KERNEL_NAME_HERE
1878 If this fails, go to the "To build a kernel" section.
1880 To rebuild everything and install it on the current system.
1881 -----------------------------------------------------------
1882 # Note: sometimes if you are running current you gotta do more than
1883 # is listed here if you are upgrading from a really old current.
1885 <make sure you have good level 0 dumps>
1887 make kernel KERNCONF=YOUR_KERNEL_HERE
1889 <reboot in single user> [3]
1896 To cross-install current onto a separate partition
1897 --------------------------------------------------
1898 # In this approach we use a separate partition to hold
1899 # current's root, 'usr', and 'var' directories. A partition
1900 # holding "/", "/usr" and "/var" should be about 2GB in
1903 <make sure you have good level 0 dumps>
1906 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1907 <maybe newfs current's root partition>
1908 <mount current's root partition on directory ${CURRENT_ROOT}>
1909 make installworld DESTDIR=${CURRENT_ROOT}
1910 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1911 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1912 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1913 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1914 <reboot into current>
1915 <do a "native" rebuild/install as described in the previous section>
1916 <maybe install compatibility libraries from ports/misc/compat*>
1920 To upgrade in-place from stable to current
1921 ----------------------------------------------
1922 <make sure you have good level 0 dumps>
1924 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1926 <reboot in single user> [3]
1933 Make sure that you've read the UPDATING file to understand the
1934 tweaks to various things you need. At this point in the life
1935 cycle of current, things change often and you are on your own
1936 to cope. The defaults can also change, so please read ALL of
1937 the UPDATING entries.
1939 Also, if you are tracking -current, you must be subscribed to
1940 freebsd-current@freebsd.org. Make sure that before you update
1941 your sources that you have read and understood all the recent
1942 messages there. If in doubt, please track -stable which has
1943 much fewer pitfalls.
1945 [1] If you have third party modules, such as vmware, you
1946 should disable them at this point so they don't crash your
1949 [3] From the bootblocks, boot -s, and then do
1954 adjkerntz -i # if CMOS is wall time
1955 Also, when doing a major release upgrade, it is required that
1956 you boot into single user mode to do the installworld.
1958 [4] Note: This step is non-optional. Failure to do this step
1959 can result in a significant reduction in the functionality of the
1960 system. Attempting to do it by hand is not recommended and those
1961 that pursue this avenue should read this file carefully, as well
1962 as the archives of freebsd-current and freebsd-hackers mailing lists
1963 for potential gotchas. The -U option is also useful to consider.
1964 See mergemaster(8) for more information.
1966 [5] Usually this step is a noop. However, from time to time
1967 you may need to do this if you get unknown user in the following
1968 step. It never hurts to do it all the time. You may need to
1969 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1970 install) after the buildworld before this step if you last updated
1971 from current before 20130425 or from -stable before 20130430.
1973 [6] This only deletes old files and directories. Old libraries
1974 can be deleted by "make delete-old-libs", but you have to make
1975 sure that no program is using those libraries anymore.
1977 [8] In order to have a kernel that can run the 4.x binaries needed to
1978 do an installworld, you must include the COMPAT_FREEBSD4 option in
1979 your kernel. Failure to do so may leave you with a system that is
1980 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1981 required to run the 5.x binaries on more recent kernels. And so on
1982 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1984 Make sure that you merge any new devices from GENERIC since the
1985 last time you updated your kernel config file.
1987 [9] When checking out sources, you must include the -P flag to have
1988 cvs prune empty directories.
1990 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1991 "?=" instead of the "=" assignment operator, so that buildworld can
1992 override the CPUTYPE if it needs to.
1994 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1995 not on the command line, or in /etc/make.conf. buildworld will
1996 warn if it is improperly defined.
1999 This file contains a list, in reverse chronological order, of major
2000 breakages in tracking -current. It is not guaranteed to be a complete
2001 list of such breakages, and only contains entries since October 10, 2007.
2002 If you need to see UPDATING entries from before that date, you will need
2003 to fetch an UPDATING file from an older FreeBSD release.
2005 Copyright information:
2007 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2009 Redistribution, publication, translation and use, with or without
2010 modification, in full or in part, in any form or format of this
2011 document are permitted without further permission from the author.
2013 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2014 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2015 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2016 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2017 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2018 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2019 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2020 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2021 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2022 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2023 POSSIBILITY OF SUCH DAMAGE.
2025 Contact Warner Losh if you have any questions about your use of