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 head, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 11.x IS SLOW:
20 FreeBSD 11.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
36 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
37 1.1.4_8 and verify bsdyml not linked in, before running "make
39 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
41 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
44 The rc.d/jail script has been updated to support jail(8)
45 configuration file. The "jail_<jname>_*" rc.conf(5) variables
46 for per-jail configuration are automatically converted to
47 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
48 This is transparently backward compatible. See below about some
49 incompatibilities and rc.conf(5) manual page for more details.
51 These variables are now deprecated in favor of jail(8) configuration
52 file. One can use "rc.d/jail config <jname>" command to generate
53 a jail(8) configuration file in /var/run/jail.<jname>.conf without
54 running the jail(8) utility. The default pathname of the
55 configuration file is /etc/jail.conf and can be specified by
56 using $jail_conf or $jail_<jname>_conf variables.
58 Please note that jail_devfs_ruleset accepts an integer at
59 this moment. Please consider to rewrite the ruleset name
63 BIND has been removed from the base system. If all you need
64 is a local resolver, simply enable and start the local_unbound
65 service instead. Otherwise, several versions of BIND are
66 available in the ports tree.
69 With the addition of unbound(8), a new unbound user is now
70 required during installworld. "mergemaster -p" can be used to
71 add the user prior to installworld, as documented in the handbook.
74 OpenSSH is now built with DNSSEC support, and will by default
75 silently trust signed SSHFP records. This can be controlled with
76 the VerifyHostKeyDNS client configuration setting. DNSSEC support
77 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
80 The GNU Compiler Collection and C++ standard library (libstdc++)
81 are no longer built by default on platforms where clang is the system
82 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
86 The PROCDESC kernel option is now part of the GENERIC kernel
87 configuration and is required for the rwhod(8) to work.
88 If you are using custom kernel configuration, you should include
92 The API and ABI related to the Capsicum framework was modified
93 in backward incompatible way. The userland libraries and programs
94 have to be recompiled to work with the new kernel. This includes the
95 following libraries and programs, but the whole buildworld is
96 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
97 kdump, procstat, rwho, rwhod, uniq.
100 AES-NI intrinsic support has been added to gcc. The AES-NI module
101 has been updated to use this support. A new gcc is required to build
102 the aesni module on both i386 and amd64.
105 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
106 Thus "device padlock_rng" and "device rdrand_rng" should be
107 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
110 WITH_ICONV has been split into two feature sets. WITH_ICONV now
111 enables just the iconv* functionality and is now on by default.
112 WITH_LIBICONV_COMPAT enables the libiconv api and link time
113 compatability. Set WITHOUT_ICONV to build the old way.
114 If you have been using WITH_ICONV before, you will very likely
115 need to turn on WITH_LIBICONV_COMPAT.
118 INVARIANTS option now enables DEBUG for code with OpenSolaris and
119 Illumos origin, including ZFS. If you have INVARIANTS in your
120 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
122 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
123 locks if WITNESS option was set. Because that generated a lot of
124 witness(9) reports and all of them were believed to be false
125 positives, this is no longer done. New option OPENSOLARIS_WITNESS
126 can be used to achieve the previous behavior.
129 Timer values in IPv6 data structures now use time_uptime instead
130 of time_second. Although this is not a user-visible functional
131 change, userland utilities which directly use them---ndp(8),
132 rtadvd(8), and rtsold(8) in the base system---need to be updated
136 find -delete can now delete the pathnames given as arguments,
137 instead of only files found below them or if the pathname did
138 not contain any slashes. Formerly, the following error message
141 find: -delete: <path>: relative path potentially not safe
143 Deleting the pathnames given as arguments can be prevented
144 without error messages using -mindepth 1 or by changing
145 directory and passing "." as argument to find. This works in the
146 old as well as the new version of find.
149 Behavior of devfs rules path matching has been changed.
150 Pattern is now always matched against fully qualified devfs
151 path and slash characters must be explicitly matched by
152 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
153 subdirectories must be reviewed.
156 The default ARM ABI has changed to the ARM EABI. The old ABI is
157 incompatible with the ARM EABI and all programs and modules will
158 need to be rebuilt to work with a new kernel.
160 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
162 NOTE: Support for the old ABI will be removed in the future and
163 users are advised to upgrade.
166 pkg_install has been disconnected from the build if you really need it
167 you should add WITH_PKGTOOLS in your src.conf(5).
170 Most of network statistics structures were changed to be able
171 keep 64-bits counters. Thus all tools, that work with networking
172 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
175 Fix targets that run multiple make's to use && rather than ;
176 so that subsequent steps depend on success of previous.
178 NOTE: if building 'universe' with -j* on stable/8 or stable/9
179 it would be better to start the build using bmake, to avoid
180 overloading the machine.
183 Fix a bug that allowed a tracing process (e.g. gdb) to write
184 to a memory-mapped file in the traced process's address space
185 even if neither the traced process nor the tracing process had
186 write access to that file.
189 CVS has been removed from the base system. An exact copy
190 of the code is available from the devel/cvs port.
193 Some people report the following error after the switch to bmake:
195 make: illegal option -- J
196 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
198 *** [buildworld] Error code 2
200 this likely due to an old instance of make in
201 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
202 which src/Makefile will use that blindly, if it exists, so if
203 you see the above error:
205 rm -rf `make -V MAKEPATH`
210 Use bmake by default.
211 Whereas before one could choose to build with bmake via
212 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
213 make. The goal is to remove these knobs for 10-RELEASE.
215 It is worth noting that bmake (like gmake) treats the command
216 line as the unit of failure, rather than statements within the
217 command line. Thus '(cd some/where && dosomething)' is safer
218 than 'cd some/where; dosomething'. The '()' allows consistent
219 behavior in parallel build.
222 Fix a bug that allows NFS clients to issue READDIR on files.
225 The WITHOUT_IDEA option has been removed because
226 the IDEA patent expired.
229 The sysctl which controls TRIM support under ZFS has been renamed
230 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
234 The mergemaster command now uses the default MAKEOBJDIRPREFIX
235 rather than creating it's own in the temporary directory in
236 order allow access to bootstrapped versions of tools such as
237 install and mtree. When upgrading from version of FreeBSD where
238 the install command does not support -l, you will need to
239 install a new mergemaster command if mergemaster -p is required.
240 This can be accomplished with the command (cd src/usr.sbin/mergemaster
244 Legacy ATA stack, disabled and replaced by new CAM-based one since
245 FreeBSD 9.0, completely removed from the sources. Kernel modules
246 atadisk and atapi*, user-level tools atacontrol and burncd are
247 removed. Kernel option `options ATA_CAM` is now permanently enabled
251 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
252 and socketpair(2). Software, in particular Kerberos, may
253 automatically detect and use these during building. The resulting
254 binaries will not work on older kernels.
257 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
258 information, see the respective 20130304 entry).
261 Recent commits to callout(9) changed the size of struct callout,
262 so the KBI is probably heavily disturbed. Also, some functions
263 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
264 by macros. Every kernel module using it won't load, so rebuild
267 The ctl device has been re-enabled in GENERIC for i386 and amd64,
268 but does not initialize by default (because of the new CTL_DISABLE
269 option) to save memory. To re-enable it, remove the CTL_DISABLE
270 option from the kernel config file or set kern.cam.ctl.disable=0
271 in /boot/loader.conf.
274 The ctl device has been disabled in GENERIC for i386 and amd64.
275 This was done due to the extra memory being allocated at system
276 initialisation time by the ctl driver which was only used if
277 a CAM target device was created. This makes a FreeBSD system
278 unusable on 128MB or less of RAM.
281 A new compression method (lz4) has been merged to -HEAD. Please
282 refer to zpool-features(7) for more information.
284 Please refer to the "ZFS notes" section of this file for information
285 on upgrading boot ZFS pools.
288 A BSD-licensed patch(1) variant has been added and is installed
289 as bsdpatch, being the GNU version the default patch.
290 To inverse the logic and use the BSD-licensed one as default,
291 while having the GNU version installed as gnupatch, rebuild
292 and install world with the WITH_BSD_PATCH knob set.
295 Due to the use of the new -l option to install(1) during build
296 and install, you must take care not to directly set the INSTALL
297 make variable in your /etc/make.conf, /etc/src.conf, or on the
298 command line. If you wish to use the -C flag for all installs
299 you may be able to add INSTALL+=-C to /etc/make.conf or
303 The install(1) option -M has changed meaning and now takes an
304 argument that is a file or path to append logs to. In the
305 unlikely event that -M was the last option on the command line
306 and the command line contained at least two files and a target
307 directory the first file will have logs appended to it. The -M
308 option served little practical purpose in the last decade so its
309 use is expected to be extremely rare.
312 After switching to Clang as the default compiler some users of ZFS
313 on i386 systems started to experience stack overflow kernel panics.
314 Please consider using 'options KSTACK_PAGES=4' in such configurations.
317 GEOM_LABEL now mangles label names read from file system metadata.
318 Mangling affect labels containing spaces, non-printable characters,
319 '%' or '"'. Device names in /etc/fstab and other places may need to
323 By default, only the 10 most recent kernel dumps will be saved. To
324 restore the previous behaviour (no limit on the number of kernel dumps
325 stored in the dump directory) add the following line to /etc/rc.conf:
330 With the addition of auditdistd(8), a new auditdistd user is now
331 required during installworld. "mergemaster -p" can be used to
332 add the user prior to installworld, as documented in the handbook.
335 The sin6_scope_id member variable in struct sockaddr_in6 is now
336 filled by the kernel before passing the structure to the userland via
337 sysctl or routing socket. This means the KAME-specific embedded scope
338 id in sin6_addr.s6_addr[2] is always cleared in userland application.
339 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
340 __FreeBSD_version is bumped to 1000025.
343 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
344 This means that the world and kernel will be compiled with clang
345 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
346 and /usr/bin/cpp. To disable this behavior and revert to building
347 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
348 of current may need to bootstrap WITHOUT_CLANG first if the clang
349 build fails (its compatibility window doesn't extend to the 9 stable
353 The IPFIREWALL_FORWARD kernel option has been removed. Its
354 functionality now turned on by default.
357 The ZERO_COPY_SOCKET kernel option has been removed and
358 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
359 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
360 mechanism which is not safe and may result in kernel crashes.
361 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
362 driver supports disposeable external page sized mbuf storage.
363 Proper replacements for both zero-copy mechanisms are under
364 consideration and will eventually lead to complete removal
365 of the two kernel options.
368 The IPv4 network stack has been converted to network byte
369 order. The following modules need to be recompiled together
370 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
371 pf(4), ipfw(4), ng_ipfw(4), stf(4).
374 Support for non-MPSAFE filesystems was removed from VFS. The
375 VFS_VERSION was bumped, all filesystem modules shall be
379 All the non-MPSAFE filesystems have been disconnected from
380 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
381 portalfs, smbfs, xfs.
384 The interface cloning API and ABI has changed. The following
385 modules need to be recompiled together with kernel:
386 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
387 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
388 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
391 The sdhci driver was split in two parts: sdhci (generic SD Host
392 Controller logic) and sdhci_pci (actual hardware driver).
393 No kernel config modifications are required, but if you
394 load sdhc as a module you must switch to sdhci_pci instead.
397 Import the FUSE kernel and userland support into base system.
400 The GNU sort(1) program has been removed since the BSD-licensed
401 sort(1) has been the default for quite some time and no serious
402 problems have been reported. The corresponding WITH_GNU_SORT
406 The pfil(9) API/ABI for AF_INET family has been changed. Packet
407 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
411 The net80211(4) ABI has been changed to allow for improved driver
412 PS-POLL and power-save support. All wireless drivers need to be
413 recompiled to work with the new kernel.
416 The random(4) support for the VIA hardware random number
417 generator (`PADLOCK') is no longer enabled unconditionally.
418 Add the padlock_rng device in the custom kernel config if
419 needed. The GENERIC kernels on i386 and amd64 do include the
420 device, so the change only affects the custom kernel
424 The pf(4) packet filter ABI has been changed. pfctl(8) and
425 snmp_pf module need to be recompiled to work with new kernel.
428 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
429 to -HEAD. Pools that have empty_bpobj in active state can not be
430 imported read-write with ZFS implementations that do not support
431 this feature. For more information read the zpool-features(5)
435 The sparc64 ZFS loader has been changed to no longer try to auto-
436 detect ZFS providers based on diskN aliases but now requires these
437 to be explicitly listed in the OFW boot-device environment variable.
440 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
441 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
442 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
445 The following sysctls and tunables have been renamed for consistency
446 with other variables:
447 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
448 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
451 The sort utility has been replaced with BSD sort. For now, GNU sort
452 is also available as "gnusort" or the default can be set back to
453 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
454 installed as "bsdsort".
457 A new version of ZFS (pool version 5000) has been merged to -HEAD.
458 Starting with this version the old system of ZFS pool versioning
459 is superseded by "feature flags". This concept enables forward
460 compatibility against certain future changes in functionality of ZFS
461 pools. The first read-only compatible "feature flag" for ZFS pools
462 is named "com.delphix:async_destroy". For more information
463 read the new zpool-features(5) manual page.
464 Please refer to the "ZFS notes" section of this file for information
465 on upgrading boot ZFS pools.
468 The malloc(3) implementation embedded in libc now uses sources imported
469 as contrib/jemalloc. The most disruptive API change is to
470 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
471 delete it prior to installworld, and optionally re-create it using the
472 new format after rebooting. See malloc.conf(5) for details
473 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
477 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
478 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
479 now spelled mips. This is to aid compatibility with third-party
480 software that expects this naming scheme in uname(3). Little-endian
481 settings are unchanged. If you are updating a big-endian mips64 machine
482 from before this change, you may need to set MACHINE_ARCH=mips64 in
483 your environment before the new build system will recognize your machine.
486 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
490 Now unix domain sockets behave "as expected" on nullfs(5). Previously
491 nullfs(5) did not pass through all behaviours to the underlying layer,
492 as a result if we bound to a socket on the lower layer we could connect
493 only to the lower path; if we bound to the upper layer we could connect
494 only to the upper path. The new behavior is one can connect to both the
495 lower and the upper paths regardless what layer path one binds to.
498 The getifaddrs upgrade path broken with 20111215 has been restored.
499 If you have upgraded in between 20111215 and 20120209 you need to
500 recompile libc again with your kernel. You still need to recompile
501 world to be able to configure CARP but this restriction already
505 The set_rcvar() function has been removed from /etc/rc.subr. All
506 base and ports rc.d scripts have been updated, so if you have a
507 port installed with a script in /usr/local/etc/rc.d you can either
508 hand-edit the rcvar= line, or reinstall the port.
510 An easy way to handle the mass-update of /etc/rc.d:
511 rm /etc/rc.d/* && mergemaster -i
514 panic(9) now stops other CPUs in the SMP systems, disables interrupts
515 on the current CPU and prevents other threads from running.
516 This behavior can be reverted using the kern.stop_scheduler_on_panic
518 The new behavior can be incompatible with kern.sync_on_panic.
521 The carp(4) facility has been changed significantly. Configuration
522 of the CARP protocol via ifconfig(8) has changed, as well as format
523 of CARP events submitted to devd(8) has changed. See manual pages
524 for more information. The arpbalance feature of carp(4) is currently
525 not supported anymore.
527 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
528 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
529 need to be recompiled.
532 The acpi_wmi(4) status device /dev/wmistat has been renamed to
536 The option VFS_ALLOW_NONMPSAFE option has been added in order to
537 explicitely support non-MPSAFE filesystems.
538 It is on by default for all supported platform at this present
542 The broken amd(4) driver has been replaced with esp(4) in the amd64,
543 i386 and pc98 GENERIC kernel configuration files.
546 sysinstall has been removed
549 The stable/9 branch created in subversion. This corresponds to the
550 RELENG_9 branch in CVS.
553 This commit modifies vfs_register() so that it uses a hash
554 calculation to set vfc_typenum, which is enabled by default.
555 The first time a system is booted after this change, the
556 vfc_typenum values will change for all file systems. The
557 main effect of this is a change to the NFS server file handles
558 for file systems that use vfc_typenum in their fsid, such as ZFS.
559 It will, however, prevent vfc_typenum from changing when file
560 systems are loaded in a different order for subsequent reboots.
561 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
562 until you are ready to remount all NFS clients after a reboot.
565 Bump the shared library version numbers for libraries that
566 do not use symbol versioning, have changed the ABI compared
567 to stable/8 and which shared library version was not bumped.
568 Done as part of 9.0-RELEASE cycle.
571 During the merge of Capsicum features, the fget(9) KPI was modified.
572 This may require the rebuilding of out-of-tree device drivers --
573 issues have been reported specifically with the nVidia device driver.
574 __FreeBSD_version is bumped to 900041.
576 Also, there is a period between 20110811 and 20110814 where the
577 special devices /dev/{stdin,stdout,stderr} did not work correctly.
578 Building world from a kernel during that window may not work.
581 The packet filter (pf) code has been updated to OpenBSD 4.5.
582 You need to update userland tools to be in sync with kernel.
583 This update breaks backward compatibility with earlier pfsync(4)
584 versions. Care must be taken when updating redundant firewall setups.
587 The following sysctls and tunables are retired on x86 platforms:
589 machdep.hlt_logical_cpus
590 The following sysctl is retired:
591 machdep.hyperthreading_allowed
592 The sysctls were supposed to provide a way to dynamically offline and
593 online selected CPUs on x86 platforms, but the implementation has not
594 been reliable especially with SCHED_ULE scheduler.
595 machdep.hyperthreading_allowed tunable is still available to ignore
596 hyperthreading CPUs at OS level.
597 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
598 where X is an APIC ID of a CPU. Be advised, though, that disabling
599 CPUs in non-uniform fashion will result in non-uniform topology and
600 may lead to sub-optimal system performance with SCHED_ULE, which is
604 cpumask_t type is retired and cpuset_t is used in order to describe
608 Changes to ifconfig(8) for dynamic address family detection mandate
609 that you are running a kernel of 20110525 or later. Make sure to
610 follow the update procedure to boot a new kernel before installing
614 Support for sun4v architecture is officially dropped
617 Several KPI breaking changes have been committed to the mii(4) layer,
618 the PHY drivers and consequently some Ethernet drivers using mii(4).
619 This means that miibus.ko and the modules of the affected Ethernet
620 drivers need to be recompiled.
622 Note to kernel developers: Given that the OUI bit reversion problem
623 was fixed as part of these changes all mii(4) commits related to OUIs,
624 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
625 handling, no longer can be merged verbatim to stable/8 and previous
629 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
630 into their kernel configurations along with 'device pci'.
633 The default NFS client is now the new NFS client, so fstype "newnfs"
634 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
635 Although mounts via fstype "nfs" will usually work without userland
636 changes, it is recommended that the mount(8) and mount_nfs(8)
637 commands be rebuilt from sources and that a link to mount_nfs called
638 mount_oldnfs be created. The new client is compiled into the
639 kernel with "options NFSCL" and this is needed for diskless root
640 file systems. The GENERIC kernel configs have been changed to use
641 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
642 To use the regular/old client, you can "mount -t oldnfs ...". For
643 a diskless root file system, you must also include a line like:
645 vfs.root.mountfrom="oldnfs:"
647 in the boot/loader.conf on the root fs on the NFS server to make
648 a diskless root fs use the old client.
651 The GENERIC kernels for all architectures now default to the new
652 CAM-based ATA stack. It means that all legacy ATA drivers were
653 removed and replaced by respective CAM drivers. If you are using
654 ATA device names in /etc/fstab or other places, make sure to update
655 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
656 where 'Y's are the sequential numbers starting from zero for each type
657 in order of detection, unless configured otherwise with tunables,
658 see cam(4)). There will be symbolic links created in /dev/ to map
659 old adX devices to the respective adaY. They should provide basic
660 compatibility for file systems mounting in most cases, but they do
661 not support old user-level APIs and do not have respective providers
662 in GEOM. Consider using updated management tools with new device names.
664 It is possible to load devices ahci, ata, siis and mvs as modules,
665 but option ATA_CAM should remain in kernel configuration to make ata
666 module work as CAM driver supporting legacy ATA controllers. Device ata
667 still can be used in modular fashion (atacore + ...). Modules atadisk
668 and atapi* are not used and won't affect operation in ATA_CAM mode.
669 Note that to use CAM-based ATA kernel should include CAM devices
670 scbus, pass, da (or explicitly ada), cd and optionally others. All of
671 them are parts of the cam module.
673 ataraid(4) functionality is now supported by the RAID GEOM class.
674 To use it you can load geom_raid kernel module and use graid(8) tool
675 for management. Instead of /dev/arX device names, use /dev/raid/rX.
677 No kernel config options or code have been removed, so if a problem
678 arises, please report it and optionally revert to the old ATA stack.
679 In order to do it you can remove from the kernel config:
684 , and instead add back:
685 device atadisk # ATA disk drives
686 device ataraid # ATA RAID drives
687 device atapicd # ATAPI CDROM drives
688 device atapifd # ATAPI floppy drives
689 device atapist # ATAPI tape drives
692 The default NFS server has been changed to the new server, which
693 was referred to as the experimental server. If you need to switch
694 back to the old NFS server, you must now put the "-o" option on
695 both the mountd and nfsd commands. This can be done using the
696 mountd_flags and nfs_server_flags rc.conf variables until an
697 update to the rc scripts is committed, which is coming soon.
700 The GNU Objective-C runtime library (libobjc), and other Objective-C
701 related components have been removed from the base system. If you
702 require an Objective-C library, please use one of the available ports.
705 ath(4) has been split into bus- and device- modules. if_ath contains
706 the HAL, the TX rate control and the network device code. if_ath_pci
707 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
708 contains the AHB glue. Users need to load both if_ath_pci and if_ath
709 in order to use ath on everything else.
711 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
712 need to load if_ath and if_ath_pci for ath(4) operation.
715 As part of the replacement of sysinstall, the process of building
716 release media has changed significantly. For details, please re-read
717 release(7), which has been updated to reflect the new build process.
720 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
721 is the last available version under GPLv2. It brings a number of new
722 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
723 4.1 and SSE 4.2), better support for powerpc64, a number of new
724 directives, and lots of other small improvements. See the ChangeLog
725 file in contrib/binutils for the full details.
728 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
729 compliant, and will now use half of hash for authentication.
730 This will break interoperability with all stacks (including all
731 actual FreeBSD versions) who implement
732 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
734 The only workaround with such peers is to use another HMAC
735 algorithm for IPsec ("phase 2") authentication.
738 Remove the uio_yield prototype and symbol. This function has
739 been misnamed since it was introduced and should not be
740 globally exposed with this name. The equivalent functionality
741 is now available using kern_yield(curthread->td_user_pri).
742 The function remains undocumented.
745 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
746 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
747 for scalar sysctls is defined but disabled. Code that needs
748 UQUAD to pass the type checking that must compile on older
749 systems where the define is not present can check against
750 __FreeBSD_version >= 900030.
752 The system dialog(1) has been replaced with a new version previously
753 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
754 with the previous version, but the libdialog associated with it has
755 a largely incompatible API. As such, the original version of libdialog
756 will be kept temporarily as libodialog, until its base system consumers
757 are replaced or updated. Bump __FreeBSD_version to 900030.
760 If you are trying to run make universe on a -stable system, and you get
761 the following warning:
762 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
763 unknown. config(8) likely too old."
764 or something similar to it, then you must upgrade your -stable system
765 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
766 stable/8) or build the config from the latest stable/8 branch and
767 install it on your system.
769 Prior to this date, building a current universe on 8-stable system from
770 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
771 error in the first kernel build phase. A new config on those old
772 systems will fix that problem for older versions of -current.
775 The TCP stack has been modified to allow Khelp modules to interact with
776 it via helper hook points and store per-connection data in the TCP
777 control block. Bump __FreeBSD_version to 900029. User space tools that
778 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
782 Generic IEEE 802.3 annex 31B full duplex flow control support has been
783 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
784 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
785 to take advantage of it instead of using custom implementations. This
786 means that these drivers now no longer unconditionally advertise
787 support for flow control but only do so if flow control is a selected
788 media option. This was implemented in the generic support that way in
789 order to allow flow control to be switched on and off via ifconfig(8)
790 with the PHY specific default to typically off in order to protect
791 from unwanted effects. Consequently, if you used flow control with
792 one of the above mentioned drivers you now need to explicitly enable
794 ifconfig bge0 media auto mediaopt flowcontrol
796 Along with the above mentioned changes generic support for setting
797 1000baseT master mode also has been added and brgphy(4), ciphy(4),
798 e1000phy(4) as well as ip1000phy(4) have been converted to take
799 advantage of it. This means that these drivers now no longer take the
800 link0 parameter for selecting master mode but the master media option
801 has to be used instead, for example like in the following:
802 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
804 Selection of master mode now is also available with all other PHY
805 drivers supporting 1000baseT.
808 The TCP stack has received a significant update to add support for
809 modularised congestion control and generally improve the clarity of
810 congestion control decisions. Bump __FreeBSD_version to 900025. User
811 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
812 sockstat) need to be recompiled.
815 The man(1) utility has been replaced by a new version that no longer
816 uses /etc/manpath.config. Please consult man.conf(5) for how to
817 migrate local entries to the new format.
820 The copyright strings printed by login(1) and sshd(8) at the time of a
821 new connection have been removed to follow other operating systems and
825 A workaround for a fixed ld bug has been removed in kernel code,
826 so make sure that your system ld is built from sources after
827 revision 210245 from 2010-07-19 (r211583 if building head kernel
828 on stable/8, r211584 for stable/7; both from 2010-08-21).
829 A symptom of incorrect ld version is different addresses for
830 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
833 The $ipv6_prefer variable in rc.conf(5) has been split into
834 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
836 The $ip6addrctl_policy is a variable to choose a pre-defined
837 address selection policy set by ip6addrctl(8). A value
838 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
841 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
842 flag (see an entry of 20090926) is set on an interface with no
843 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
844 security reason. If you want IPv6 link-local address on all
845 interfaces by default, set this to "YES".
847 The old ipv6_prefer="YES" is equivalent to
848 ipv6_activate_all_interfaces="YES" and
849 ip6addrctl_policy="ipv6_prefer".
852 DTrace has grown support for userland tracing. Due to this, DTrace is
853 now i386 and amd64 only.
854 dtruss(1) is now installed by default on those systems and a new
855 kernel module is needed for userland tracing: fasttrap.
856 No changes to your kernel config file are necessary to enable
857 userland tracing, but you might consider adding 'STRIP=' and
858 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
859 to have informative userland stack traces in DTrace (ustack).
862 The acpi_aiboost(4) driver has been removed in favor of the new
863 aibs(4) driver. You should update your kernel configuration file.
866 BSD grep has been imported to the base system and it is built by
867 default. It is completely BSD licensed, highly GNU-compatible, uses
868 less memory than its GNU counterpart and has a small codebase.
869 However, it is slower than its GNU counterpart, which is mostly
870 noticeable for larger searches, for smaller ones it is measurable
871 but not significant. The reason is complex, the most important factor
872 is that we lack a modern and efficient regex library and GNU
873 overcomes this by optimizing the searches internally. Future work
874 on improving the regex performance is planned, for the meantime,
875 users that need better performance, can build GNU grep instead by
876 setting the WITH_GNU_GREP knob.
879 Due to the import of powerpc64 support, all existing powerpc kernel
880 configuration files must be updated with a machine directive like this:
881 machine powerpc powerpc
883 In addition, an updated config(8) is required to build powerpc kernels
887 A new version of ZFS (version 15) has been merged to -HEAD.
888 This version uses a python library for the following subcommands:
889 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
890 For full functionality of these commands the following port must
891 be installed: sysutils/py-zfs
894 'vm_page's are now hashed by physical address to an array of mutexes.
895 Currently this is only used to serialize access to hold_count. Over
896 time the page queue mutex will be peeled away. This changes the size
897 of pmap on every architecture. And requires all callers of vm_page_hold
898 and vm_page_unhold to be updated.
901 WITH_CTF can now be specified in src.conf (not recommended, there
902 are some problems with static executables), make.conf (would also
903 affect ports which do not use GNU make and do not override the
904 compile targets) or in the kernel config (via "makeoptions
906 When WITH_CTF was specified there before this was silently ignored,
907 so make sure that WITH_CTF is not used in places which could lead
908 to unwanted behavior.
911 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
912 to allow 32-bit compatibility on non-x86 platforms. All kernel
913 configurations on amd64 and ia64 platforms using these options must
914 be modified accordingly.
917 The utmp user accounting database has been replaced with utmpx,
918 the user accounting interface standardized by POSIX.
919 Unfortunately the semantics of utmp and utmpx don't match,
920 making it practically impossible to support both interfaces.
921 The user accounting database is used by tools like finger(1),
922 last(1), talk(1), w(1) and ac(8).
924 All applications in the base system use utmpx. This means only
925 local binaries (e.g. from the ports tree) may still use these
926 utmp database files. These applications must be rebuilt to make
929 After the system has been upgraded, it is safe to remove the old
930 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
931 assuming their contents is of no importance anymore. Old wtmp
932 databases can only be used by last(1) and ac(8) after they have
933 been converted to the new format using wtmpcvt(1).
936 Introduce the kernel thread "deadlock resolver" (which can be enabled
937 via the DEADLKRES option, see NOTES for more details) and the
938 sleepq_type() function for sleepqueues.
941 The rc.firewall and rc.firewall6 were unified, and
942 rc.firewall6 and rc.d/ip6fw were removed.
943 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
944 variables are obsoleted. Instead, the following new rc
945 variables are added to rc.d/ipfw:
947 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
948 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
949 firewall_simple_onet_ipv6, firewall_trusted_ipv6
951 The meanings correspond to the relevant IPv4 variables.
957 The default terminal emulation for syscons(4) has been changed
958 from cons25 to xterm on all platforms except pc98. This means
959 that the /etc/ttys file needs to be updated to ensure correct
960 operation of applications on the console.
962 The terminal emulation style can be toggled per window by using
963 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
964 options can be used to change the compile-time default back to
967 To prevent graphical artifacts, make sure the TERM environment
968 variable is set to match the terminal emulation that is being
969 performed by syscons(4).
972 The layout of the structure ieee80211req_scan_result has changed.
973 Applications that require wireless scan results (e.g. ifconfig(8))
974 from net80211 need to be recompiled.
976 Applications such as wpa_supplicant(8) may require a full world
977 build without using NO_CLEAN in order to get synchronized with the
981 The iwn(4) driver has been updated to support the 5000 and 5150 series.
982 There's one kernel module for each firmware. Adding "device iwnfw"
983 to the kernel configuration file means including all three firmware
984 images inside the kernel. If you want to include just the one for
985 your wireless card, use the devices iwn4965fw, iwn5000fw or
989 The rc.d/network_ipv6, IPv6 configuration script has been integrated
990 into rc.d/netif. The changes are the following:
992 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
993 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
994 Note that both variables need the "inet6" keyword at the head.
996 Do not set $ipv6_network_interfaces manually if you do not
997 understand what you are doing. It is not needed in most cases.
999 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1002 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1003 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1005 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1006 all configured interfaces have "inet6 accept_rtadv" in the
1007 $ifconfig_IF_ipv6. These are for backward compatibility.
1009 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1010 functionality of interfaces with no corresponding
1011 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1012 and the default address selection policy of ip6addrctl(8)
1013 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1014 Note that if you want to configure IPv6 functionality on the
1015 disabled interfaces after boot, first you need to clear the flag by
1016 using ifconfig(8) like:
1018 ifconfig em0 inet6 -ifdisabled
1020 If YES, the default address selection policy is set as
1023 The default value of $ipv6_prefer is NO.
1025 4. If your system need to receive Router Advertisement messages,
1026 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1027 scripts automatically invoke rtsol(8) when the interface becomes
1028 UP. The Router Advertisement messages are used for SLAAC
1029 (State-Less Address AutoConfiguration).
1032 802.11s D3.03 support was committed. This is incompatible with the
1033 previous code, which was based on D3.0.
1036 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1037 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1038 control whether accepting Router Advertisement messages or not.
1039 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1040 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1041 The ifconfig(8) utility now supports these flags.
1044 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1045 mount(8) and -a option for df(1) to see them.
1048 The old tunable hw.bus.devctl_disable has been superseded by
1049 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1050 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1054 Remove the option STOP_NMI. The default action is now to use NMI only
1055 for KDB via the newly introduced function stop_cpus_hard() and
1056 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1059 The stable/8 branch created in subversion. This corresponds to the
1060 RELENG_8 branch in CVS.
1063 Bump the shared library version numbers for all libraries that do not
1064 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1065 __FreeBSD_version to 800105.
1068 Due to changes in the implementation of virtual network stack support,
1069 all network-related kernel modules must be recompiled. As this change
1070 breaks the ABI, bump __FreeBSD_version to 800104.
1073 The TOE interface to the TCP syncache has been modified to remove
1074 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1075 The cxgb driver is the only TOE consumer affected by this change, and
1076 needs to be recompiled along with the kernel. As this change breaks
1077 the ABI, bump __FreeBSD_version to 800103.
1080 Padding has been added to struct tcpcb, sackhint and tcpstat in
1081 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1082 maintaining the ABI. However, this change breaks the ABI, so bump
1083 __FreeBSD_version to 800102. User space tools that rely on the size of
1084 any of these structs (e.g. sockstat) need to be recompiled.
1087 The NFS_LEGACYRPC option has been removed along with the old kernel
1088 RPC implementation that this option selected. Kernel configurations
1089 may need to be adjusted.
1092 The network interface device nodes at /dev/net/<interface> have been
1093 removed. All ioctl operations can be performed the normal way using
1094 routing sockets. The kqueue functionality can generally be replaced
1095 with routing sockets.
1098 The documentation from the FreeBSD Documentation Project (Handbook,
1099 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1100 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1103 The ABI of various structures related to the SYSV IPC API have been
1104 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1105 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1109 Layout of struct vnet has changed as routing related variables were
1110 moved to their own Vimage module. Modules need to be recompiled. Bump
1111 __FreeBSD_version to 800099.
1114 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1115 respectively. As long as no more than 16 groups per process are used,
1116 no changes should be visible. When more than 16 groups are used, old
1117 binaries may fail if they call getgroups() or getgrouplist() with
1118 statically sized storage. Recompiling will work around this, but
1119 applications should be modified to use dynamically allocated storage
1120 for group arrays as POSIX.1-2008 does not cap an implementation's
1121 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1123 NFS and portalfs mounts may also be affected as the list of groups is
1124 truncated to 16. Users of NFS who use more than 16 groups, should
1125 take care that negative group permissions are not used on the exported
1126 file systems as they will not be reliable unless a GSSAPI based
1127 authentication method is used.
1130 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1131 option compiles in the support for adaptive spinning for lockmgrs
1132 which want to enable it. The lockinit() function now accepts the flag
1133 LK_ADAPTIVE in order to make the lock object subject to adaptive
1134 spinning when both held in write and read mode.
1137 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1138 changed. User applications that use this ioctl need to be rebuilt.
1141 The layout of struct thread has changed. Kernel and modules need to
1145 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1146 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1149 window(1) has been removed from the base system. It can now be
1150 installed from ports. The port is called misc/window.
1153 The way we are storing and accessing `routing table' entries has
1154 changed. Programs reading the FIB, like netstat, need to be
1158 A new netisr implementation has been added for FreeBSD 8. Network
1159 file system modules, such as igmp, ipdivert, and others, should be
1161 Bump __FreeBSD_version to 800096.
1164 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1168 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1169 Bump __FreeBSD_version to 800094.
1172 Add mnt_xflag field to 'struct mount'. File system modules need to be
1174 Bump __FreeBSD_version to 800093.
1177 The compiling option ADAPTIVE_SX has been retired while it has been
1178 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1179 The KPI for sx_init_flags() changes as accepting flags:
1180 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1181 been introduced in order to handle the reversed logic.
1182 Bump __FreeBSD_version to 800092.
1185 Add support for hierarchical jails. Remove global securelevel.
1186 Bump __FreeBSD_version to 800091.
1189 The layout of struct vnet_net has changed, therefore modules
1191 Bump __FreeBSD_version to 800090.
1194 The newly imported zic(8) produces a new format in the output. Please
1195 run tzsetup(8) to install the newly created data to /etc/localtime.
1198 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1199 hw.usb.* and is now consistent again with previous releases.
1202 802.11 monitor mode support was revised and driver api's were changed.
1203 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1204 of DLT_IEEE802_11. No user-visible data structures were changed but
1205 applications that use DLT_IEEE802_11 may require changes.
1206 Bump __FreeBSD_version to 800088.
1209 The layout of the following structs has changed: sysctl_oid,
1210 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1211 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1212 panics may be experienced. World rebuild is required for
1213 correctly checking networking state from userland.
1214 Bump __FreeBSD_version to 800085.
1217 MLDv2 and Source-Specific Multicast (SSM) have been merged
1218 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1219 The implementation of SSM within FreeBSD's IPv6 stack closely
1220 follows the IPv4 implementation.
1222 For kernel developers:
1224 * The most important changes are that the ip6_output() and
1225 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1226 and this lock has been downgraded to a non-recursive mutex.
1228 * As with the changes to the IPv4 stack to support SSM, filtering
1229 of inbound multicast traffic must now be performed by transport
1230 protocols within the IPv6 stack. This does not apply to TCP and
1231 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1233 * The KPIs used by IPv6 multicast are similar to those used by
1234 the IPv4 stack, with the following differences:
1235 * im6o_mc_filter() is analogous to imo_multicast_filter().
1236 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1237 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1238 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1239 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1240 for MLDv1 have an additional 'timer' argument which is used to
1241 jitter the initial membership report for the solicited-node
1242 multicast membership on-link.
1243 * This is not strictly needed for MLDv2, which already jitters
1244 its report transmissions. However, the 'timer' argument is
1245 preserved in case MLDv1 is active on the interface.
1247 * The KAME linked-list based IPv6 membership implementation has
1248 been refactored to use a vector similar to that used by the IPv4
1250 Code which maintains a list of its own multicast memberships
1251 internally, e.g. carp, has been updated to reflect the new
1254 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1255 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1256 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1257 implementation constraint which needs to be addressed in HEAD.
1259 For application developers:
1261 * The changes are broadly similar to those made for the IPv4
1264 * The use of IPv4 and IPv6 multicast socket options on the same
1265 socket, using mapped addresses, HAS NOT been tested or supported.
1267 * There are a number of issues with the implementation of various
1268 IPv6 multicast APIs which need to be resolved in the API surface
1269 before the implementation is fully compatible with KAME userland
1270 use, and these are mostly to do with interface index treatment.
1272 * The literature available discusses the use of either the delta / ASM
1273 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1274 using setsourcefilter(3)/getsourcefilter(3). For more information
1275 please refer to RFC 3768, 'Socket Interface Extensions for
1276 Multicast Source Filters'.
1278 * Applications which use the published RFC 3678 APIs should be fine.
1280 For systems administrators:
1282 * The mtest(8) utility has been refactored to support IPv6, in
1283 addition to IPv4. Interface addresses are no longer accepted
1284 as arguments, their names must be used instead. The utility
1285 will map the interface name to its first IPv4 address as
1286 returned by getifaddrs(3).
1288 * The ifmcstat(8) utility has also been updated to print the MLDv2
1289 endpoint state and source filter lists via sysctl(3).
1291 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1292 loopback of IPv6 multicast datagrams by default; it defaults to 1
1293 to preserve the existing behaviour. Disabling multicast loopback is
1294 recommended for optimal system performance.
1296 * The IPv6 MROUTING code has been changed to examine this sysctl
1297 instead of attempting to perform a group lookup before looping
1298 back forwarded datagrams.
1300 Bump __FreeBSD_version to 800084.
1303 Implement low-level Bluetooth HCI API.
1304 Bump __FreeBSD_version to 800083.
1307 The layout of struct malloc_type, used by modules to register new
1308 memory allocation types, has changed. Most modules will need to
1309 be rebuilt or panics may be experienced.
1310 Bump __FreeBSD_version to 800081.
1313 Anticipate overflowing inp_flags - add inp_flags2.
1314 This changes most offsets in inpcb, so checking v4 connection
1315 state will require a world rebuild.
1316 Bump __FreeBSD_version to 800080.
1319 Add an llentry to struct route and struct route_in6. Modules
1320 embedding a struct route will need to be recompiled.
1321 Bump __FreeBSD_version to 800079.
1324 The size of rt_metrics_lite and by extension rtentry has changed.
1325 Networking administration apps will need to be recompiled.
1326 The route command now supports show as an alias for get, weighting
1327 of routes, sticky and nostick flags to alter the behavior of stateful
1329 Bump __FreeBSD_version to 800078.
1332 Do not use Giant for kbdmux(4) locking. This is wrong and
1333 apparently causing more problems than it solves. This will
1334 re-open the issue where interrupt handlers may race with
1335 kbdmux(4) in polling mode. Typical symptoms include (but
1336 not limited to) duplicated and/or missing characters when
1337 low level console functions (such as gets) are used while
1338 interrupts are enabled (for example geli password prompt,
1339 mountroot prompt etc.). Disabling kbdmux(4) may help.
1342 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1343 kernel modules referencing any of the above need to be recompiled.
1344 Bump __FreeBSD_version to 800075.
1347 GEOM_PART has become the default partition slicer for storage devices,
1348 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1349 introduces some changes:
1351 MSDOS/EBR: the devices created from MSDOS extended partition entries
1352 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1353 to devices with offset-based names. fstabs may need to be modified.
1355 BSD: the "geometry does not match label" warning is harmless in most
1356 cases but it points to problems in file system misalignment with
1357 disk geometry. The "c" partition is now implicit, covers the whole
1358 top-level drive and cannot be (mis)used by users.
1360 General: Kernel dumps are now not allowed to be written to devices
1361 whose partition types indicate they are meant to be used for file
1362 systems (or, in case of MSDOS partitions, as something else than
1365 Most of these changes date approximately from 200812.
1368 The uscanner(4) driver has been removed from the kernel. This follows
1369 Linux removing theirs in 2.6 and making libusb the default interface
1370 (supported by sane).
1373 The multicast forwarding code has been cleaned up. netstat(1)
1374 only relies on KVM now for printing bandwidth upcall meters.
1375 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1376 ip6_mroute_mod respectively. The config(5) options for statically
1377 compiling this code remain the same, i.e. 'options MROUTING'.
1380 Support for the IFF_NEEDSGIANT network interface flag has been
1381 removed, which means that non-MPSAFE network device drivers are no
1382 longer supported. In particular, if_ar, if_sr, and network device
1383 drivers from the old (legacy) USB stack can no longer be built or
1387 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1388 a bunch of new language catalog files have also been added.
1389 This means that some common libc messages are now localized and
1390 they depend on the LC_MESSAGES environmental variable.
1393 The k8temp(4) driver has been renamed to amdtemp(4) since
1394 support for Family 10 and Family 11 CPU families was added.
1397 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1398 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1400 For kernel developers, the most important changes are that the
1401 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1402 and this lock has been downgraded to a non-recursive mutex.
1404 Transport protocols (UDP, Raw IP) are now responsible for filtering
1405 inbound multicast traffic according to group membership and source
1406 filters. The imo_multicast_filter() KPI exists for this purpose.
1407 Transports which do not use multicast (SCTP, TCP) already reject
1408 multicast by default. Forwarding and receive performance may improve
1409 as a mutex acquisition is no longer needed in the ip_input()
1410 low-level input path. in_addmulti() and in_delmulti() are shimmed
1411 to new KPIs which exist to support SSM in-kernel.
1413 For application developers, it is recommended that loopback of
1414 multicast datagrams be disabled for best performance, as this
1415 will still cause the lock to be taken for each looped-back
1416 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1417 be tuned to 0 to disable loopback by default; it defaults to 1
1418 to preserve the existing behaviour.
1420 For systems administrators, to obtain best performance with
1421 multicast reception and multiple groups, it is always recommended
1422 that a card with a suitably precise hash filter is used. Hash
1423 collisions will still result in the lock being taken within the
1424 transport protocol input path to check group membership.
1426 If deploying FreeBSD in an environment with IGMP snooping switches,
1427 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1428 enabled; this forces 224.0.0.0/24 group membership to be announced
1431 The size of 'struct igmpstat' has changed; netstat needs to be
1432 recompiled to reflect this.
1433 Bump __FreeBSD_version to 800070.
1436 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1437 updated to use it. This requires a buildworld/installworld in order to
1438 update the library and dependencies (usbconfig, etc). Its advisable to
1439 rebuild all ports which uses libusb. More specific directions are given
1440 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1441 libusb are no longer required and can be removed.
1444 A workaround is committed to allow the creation of System V shared
1445 memory segment of size > 2 GB on the 64-bit architectures.
1446 Due to a limitation of the existing ABI, the shm_segsz member
1447 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1448 wrong for large segments. Note that limits must be explicitly
1449 raised to allow such segments to be created.
1452 The layout of struct ifnet has changed, requiring a rebuild of all
1453 network device driver modules.
1456 The /dev handling for the new USB stack has changed, a
1457 buildworld/installworld is required for libusb20.
1460 The new USB2 stack has now been permanently moved in and all kernel and
1461 module names reverted to their previous values (eg, usb, ehci, ohci,
1462 ums, ...). The old usb stack can be compiled in by prefixing the name
1463 with the letter 'o', the old usb modules have been removed.
1464 Updating entry 20090216 for xorg and 20090215 for libmap may still
1468 The rc.conf(5) option if_up_delay has been renamed to
1469 defaultroute_delay to better reflect its purpose. If you have
1470 customized this setting in /etc/rc.conf you need to update it to
1474 xorg 7.4 wants to configure its input devices via hald which does not
1475 yet work with USB2. If the keyboard/mouse does not work in xorg then
1477 Option "AllowEmptyInput" "off"
1478 to your ServerLayout section. This will cause X to use the configured
1479 kbd and mouse sections from your xorg.conf.
1482 The GENERIC kernels for all architectures now default to the new USB2
1483 stack. No kernel config options or code have been removed so if a
1484 problem arises please report it and optionally revert to the old USB
1485 stack. If you are loading USB kernel modules or have a custom kernel
1486 that includes GENERIC then ensure that usb names are also changed over,
1487 eg uftdi -> usb2_serial_ftdi.
1489 Older programs linked against the ports libusb 0.1 need to be
1490 redirected to the new stack's libusb20. /etc/libmap.conf can
1492 # Map old usb library to new one for usb2 stack
1493 libusb-0.1.so.8 libusb20.so.1
1496 All USB ethernet devices now attach as interfaces under the name ueN
1497 (eg. ue0). This is to provide a predictable name as vendors often
1498 change usb chipsets in a product without notice.
1501 The ichsmb(4) driver has been changed to require SMBus slave
1502 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1503 All of the other SMBus controller drivers require left-justified
1504 slave addresses, so this change makes all the drivers provide the
1508 INET6 statistics (struct ip6stat) was updated.
1509 netstat(1) needs to be recompiled.
1512 NTFS has been removed from GENERIC kernel on amd64 to match
1513 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1514 will load ntfs.ko module automatically when NTFS support is
1515 actually needed, unless ntfs.ko is not installed or security
1516 level prohibits loading kernel modules. If either is the case,
1517 "options NTFS" has to be added into kernel config.
1520 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1521 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1522 800061. User space tools that rely on the size of struct tcpcb in
1523 tcp_var.h (e.g. sockstat) need to be recompiled.
1526 ng_tty(4) module updated to match the new TTY subsystem.
1527 Due to API change, user-level applications must be updated.
1528 New API support added to mpd5 CVS and expected to be present
1529 in next mpd5.3 release.
1532 With __FreeBSD_version 800060 the makefs tool is part of
1533 the base system (it was a port).
1536 The afdata and ifnet locks have been changed from mutexes to
1537 rwlocks, network modules will need to be re-compiled.
1540 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1541 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1542 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1543 architecture and 40 bytes on 64-bit architecture. The userland
1544 applications "arp" and "ndp" have been updated accordingly.
1545 The output from "netstat -r" shows only routing entries and
1546 none of the L2 information.
1549 __FreeBSD_version 800057 marks the switchover from the
1550 binary ath hal to source code. Users must add the line:
1552 options AH_SUPPORT_AR5416
1554 to their kernel config files when specifying:
1558 The ath_hal module no longer exists; the code is now compiled
1559 together with the driver in the ath module. It is now
1560 possible to tailor chip support (i.e. reduce the set of chips
1561 and thereby the code size); consult ath_hal(4) for details.
1564 __FreeBSD_version 800054 adds memory barriers to
1565 <machine/atomic.h>, new interfaces to ifnet to facilitate
1566 multiple hardware transmit queues for cards that support
1567 them, and a lock-less ring-buffer implementation to
1568 enable drivers to more efficiently manage queueing of
1572 A new version of ZFS (version 13) has been merged to -HEAD.
1573 This version has zpool attribute "listsnapshots" off by
1574 default, which means "zfs list" does not show snapshots,
1575 and is the same as Solaris behavior.
1578 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1581 The uhci, ohci, ehci and slhci USB Host controller drivers have
1582 been put into separate modules. If you load the usb module
1583 separately through loader.conf you will need to load the
1584 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1585 controller add the following to loader.conf:
1591 The ABI used by the PMC toolset has changed. Please keep
1592 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1596 atapci kernel module now includes only generic PCI ATA
1597 driver. AHCI driver moved to ataahci kernel module.
1598 All vendor-specific code moved into separate kernel modules:
1599 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1600 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1601 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1602 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1605 The TTY subsystem of the kernel has been replaced by a new
1606 implementation, which provides better scalability and an
1607 improved driver model. Most common drivers have been migrated to
1608 the new TTY subsystem, while others have not. The following
1609 drivers have not yet been ported to the new TTY layer:
1612 cy, digi, rc, rp, sio
1618 ng_h4, ng_tty, ppp, sl, snp
1620 Adding these drivers to your kernel configuration file shall
1621 cause compilation to fail.
1624 ntpd has been upgraded to 4.2.4p5.
1627 OpenSSH has been upgraded to 5.1p1.
1629 For many years, FreeBSD's version of OpenSSH preferred DSA
1630 over RSA for host and user authentication keys. With this
1631 upgrade, we've switched to the vendor's default of RSA over
1632 DSA. This may cause upgraded clients to warn about unknown
1633 host keys even for previously known hosts. Users should
1634 follow the usual procedure for verifying host keys before
1635 accepting the RSA key.
1637 This can be circumvented by setting the "HostKeyAlgorithms"
1638 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1641 Please note that the sequence of keys offered for
1642 authentication has been changed as well. You may want to
1643 specify IdentityFile in a different order to revert this
1647 The sio(4) driver has been removed from the i386 and amd64
1648 kernel configuration files. This means uart(4) is now the
1649 default serial port driver on those platforms as well.
1651 To prevent collisions with the sio(4) driver, the uart(4) driver
1652 uses different names for its device nodes. This means the
1653 onboard serial port will now most likely be called "ttyu0"
1654 instead of "ttyd0". You may need to reconfigure applications to
1655 use the new device names.
1657 When using the serial port as a boot console, be sure to update
1658 /boot/device.hints and /etc/ttys before booting the new kernel.
1659 If you forget to do so, you can still manually specify the hints
1660 at the loader prompt:
1662 set hint.uart.0.at="isa"
1663 set hint.uart.0.port="0x3F8"
1664 set hint.uart.0.flags="0x10"
1665 set hint.uart.0.irq="4"
1669 The gpt(8) utility has been removed. Use gpart(8) to partition
1673 The version that Linuxulator emulates was changed from 2.4.2
1674 to 2.6.16. If you experience any problems with Linux binaries
1675 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1676 if it fixes the problem contact emulation mailing list.
1679 ISDN4BSD (I4B) was removed from the src tree. You may need to
1680 update a your kernel configuration and remove relevant entries.
1683 I have checked in code to support multiple routing tables.
1684 See the man pages setfib(1) and setfib(2).
1685 This is a hopefully backwards compatible version,
1686 but to make use of it you need to compile your kernel
1687 with options ROUTETABLES=2 (or more up to 16).
1690 The 802.11 wireless support was redone to enable multi-bss
1691 operation on devices that are capable. The underlying device
1692 is no longer used directly but instead wlanX devices are
1693 cloned with ifconfig. This requires changes to rc.conf files.
1694 For example, change:
1695 ifconfig_ath0="WPA DHCP"
1698 ifconfig_wlan0="WPA DHCP"
1699 see rc.conf(5) for more details. In addition, mergemaster of
1700 /etc/rc.d is highly recommended. Simultaneous update of userland
1701 and kernel wouldn't hurt either.
1703 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1704 modules were merged into the base wlan module. All references
1705 to these modules (e.g. in kernel config files) must be removed.
1708 psm(4) has gained write(2) support in native operation level.
1709 Arbitrary commands can be written to /dev/psm%d and status can
1710 be read back from it. Therefore, an application is responsible
1711 for status validation and error recovery. It is a no-op in
1712 other operation levels.
1715 Support for KSE threading has been removed from the kernel. To
1716 run legacy applications linked against KSE libmap.conf may
1717 be used. The following libmap.conf may be used to ensure
1718 compatibility with any prior release:
1720 libpthread.so.1 libthr.so.1
1721 libpthread.so.2 libthr.so.2
1722 libkse.so.3 libthr.so.3
1725 The layout of struct vmspace has changed. This affects libkvm
1726 and any executables that link against libkvm and use the
1727 kvm_getprocs() function. In particular, but not exclusively,
1728 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1729 The effects are minimal, but it's advisable to upgrade world
1733 The latest em driver no longer has support in it for the
1734 82575 adapter, this is now moved to the igb driver. The
1735 split was done to make new features that are incompatible
1736 with older hardware easier to do.
1739 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1740 likewise the kernel option is now GEOM_LINUX_LVM.
1743 The default NFS mount mode has changed from UDP to TCP for
1744 increased reliability. If you rely on (insecurely) NFS
1745 mounting across a firewall you may need to update your
1749 Belatedly note the addition of m_collapse for compacting
1753 The fts(3) structures have been changed to use adequate
1754 integer types for their members and so to be able to cope
1755 with huge file trees. The old fts(3) ABI is preserved
1756 through symbol versioning in libc, so third-party binaries
1757 using fts(3) should still work, although they will not take
1758 advantage of the extended types. At the same time, some
1759 third-party software might fail to build after this change
1760 due to unportable assumptions made in its source code about
1761 fts(3) structure members. Such software should be fixed
1762 by its vendor or, in the worst case, in the ports tree.
1763 FreeBSD_version 800015 marks this change for the unlikely
1764 case that a portable fix is impossible.
1767 To upgrade to -current after this date, you must be running
1768 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1769 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1772 The ADAPTIVE_GIANT kernel option has been retired because its
1773 functionality is the default now.
1776 The AT keyboard emulation of sunkbd(4) has been turned on
1777 by default. In order to make the special symbols of the Sun
1778 keyboards driven by sunkbd(4) work under X these now have
1779 to be configured the same way as Sun USB keyboards driven
1780 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1782 Option "XkbLayout" "us"
1783 Option "XkbRules" "xorg"
1784 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1787 It has been decided that it is desirable to provide ABI
1788 backwards compatibility to the FreeBSD 4/5/6 versions of the
1789 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1790 broken with the introduction of PCI domain support (see the
1791 20070930 entry). Unfortunately, this required the ABI of
1792 PCIOCGETCONF to be broken again in order to be able to
1793 provide backwards compatibility to the old version of that
1794 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1795 again. As for prominent ports this affects neither pciutils
1796 nor xorg-server this time, the hal port needs to be rebuilt
1800 The misnamed kthread_create() and friends have been renamed
1801 to kproc_create() etc. Many of the callers already
1802 used kproc_start()..
1803 I will return kthread_create() and friends in a while
1804 with implementations that actually create threads, not procs.
1805 Renaming corresponds with version 800002.
1814 Avoid using make -j when upgrading. While generally safe, there are
1815 sometimes problems using -j to upgrade. If your upgrade fails with
1816 -j, please try again without -j. From time to time in the past there
1817 have been problems using -j with buildworld and/or installworld. This
1818 is especially true when upgrading between "distant" versions (eg one
1819 that cross a major release boundary or several minor releases, or when
1820 several months have passed on the -current branch).
1822 Sometimes, obscure build problems are the result of environment
1823 poisoning. This can happen because the make utility reads its
1824 environment when searching for values for global variables. To run
1825 your build attempts in an "environmental clean room", prefix all make
1826 commands with 'env -i '. See the env(1) manual page for more details.
1828 When upgrading from one major version to another it is generally best
1829 to upgrade to the latest code in the currently installed branch first,
1830 then do an upgrade to the new branch. This is the best-tested upgrade
1831 path, and has the highest probability of being successful. Please try
1832 this approach before reporting problems with a major version upgrade.
1834 When upgrading a live system, having a root shell around before
1835 installing anything can help undo problems. Not having a root shell
1836 around can lead to problems if pam has changed too much from your
1837 starting point to allow continued authentication after the upgrade.
1841 When upgrading the boot ZFS pool to a new version, always follow
1844 1.) recompile and reinstall the ZFS boot loader and boot block
1845 (this is part of "make buildworld" and "make installworld")
1847 2.) update the ZFS boot block on your boot drive
1849 The following example updates the ZFS boot block on the first
1850 partition (freebsd-boot) of a GPT partitioned drive ad0:
1851 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1853 Non-boot pools do not need these updates.
1857 If you are updating from a prior version of FreeBSD (even one just
1858 a few days old), you should follow this procedure. It is the most
1859 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1861 make kernel-toolchain
1862 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1863 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1865 To test a kernel once
1866 ---------------------
1867 If you just want to boot a kernel once (because you are not sure
1868 if it works, or if you want to boot a known bad kernel to provide
1869 debugging information) run
1870 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1871 nextboot -k testkernel
1873 To just build a kernel when you know that it won't mess you up
1874 --------------------------------------------------------------
1875 This assumes you are already running a CURRENT system. Replace
1876 ${arch} with the architecture of your machine (e.g. "i386",
1877 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1879 cd src/sys/${arch}/conf
1880 config KERNEL_NAME_HERE
1881 cd ../compile/KERNEL_NAME_HERE
1886 If this fails, go to the "To build a kernel" section.
1888 To rebuild everything and install it on the current system.
1889 -----------------------------------------------------------
1890 # Note: sometimes if you are running current you gotta do more than
1891 # is listed here if you are upgrading from a really old current.
1893 <make sure you have good level 0 dumps>
1895 make kernel KERNCONF=YOUR_KERNEL_HERE
1897 <reboot in single user> [3]
1904 To cross-install current onto a separate partition
1905 --------------------------------------------------
1906 # In this approach we use a separate partition to hold
1907 # current's root, 'usr', and 'var' directories. A partition
1908 # holding "/", "/usr" and "/var" should be about 2GB in
1911 <make sure you have good level 0 dumps>
1914 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1915 <maybe newfs current's root partition>
1916 <mount current's root partition on directory ${CURRENT_ROOT}>
1917 make installworld DESTDIR=${CURRENT_ROOT}
1918 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1919 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1920 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1921 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1922 <reboot into current>
1923 <do a "native" rebuild/install as described in the previous section>
1924 <maybe install compatibility libraries from ports/misc/compat*>
1928 To upgrade in-place from stable to current
1929 ----------------------------------------------
1930 <make sure you have good level 0 dumps>
1932 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1934 <reboot in single user> [3]
1941 Make sure that you've read the UPDATING file to understand the
1942 tweaks to various things you need. At this point in the life
1943 cycle of current, things change often and you are on your own
1944 to cope. The defaults can also change, so please read ALL of
1945 the UPDATING entries.
1947 Also, if you are tracking -current, you must be subscribed to
1948 freebsd-current@freebsd.org. Make sure that before you update
1949 your sources that you have read and understood all the recent
1950 messages there. If in doubt, please track -stable which has
1951 much fewer pitfalls.
1953 [1] If you have third party modules, such as vmware, you
1954 should disable them at this point so they don't crash your
1957 [3] From the bootblocks, boot -s, and then do
1962 adjkerntz -i # if CMOS is wall time
1963 Also, when doing a major release upgrade, it is required that
1964 you boot into single user mode to do the installworld.
1966 [4] Note: This step is non-optional. Failure to do this step
1967 can result in a significant reduction in the functionality of the
1968 system. Attempting to do it by hand is not recommended and those
1969 that pursue this avenue should read this file carefully, as well
1970 as the archives of freebsd-current and freebsd-hackers mailing lists
1971 for potential gotchas. The -U option is also useful to consider.
1972 See mergemaster(8) for more information.
1974 [5] Usually this step is a noop. However, from time to time
1975 you may need to do this if you get unknown user in the following
1976 step. It never hurts to do it all the time. You may need to
1977 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1978 install) after the buildworld before this step if you last updated
1979 from current before 20130425 or from -stable before 20130430.
1981 [6] This only deletes old files and directories. Old libraries
1982 can be deleted by "make delete-old-libs", but you have to make
1983 sure that no program is using those libraries anymore.
1985 [8] In order to have a kernel that can run the 4.x binaries needed to
1986 do an installworld, you must include the COMPAT_FREEBSD4 option in
1987 your kernel. Failure to do so may leave you with a system that is
1988 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1989 required to run the 5.x binaries on more recent kernels. And so on
1990 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1992 Make sure that you merge any new devices from GENERIC since the
1993 last time you updated your kernel config file.
1995 [9] When checking out sources, you must include the -P flag to have
1996 cvs prune empty directories.
1998 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1999 "?=" instead of the "=" assignment operator, so that buildworld can
2000 override the CPUTYPE if it needs to.
2002 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2003 not on the command line, or in /etc/make.conf. buildworld will
2004 warn if it is improperly defined.
2007 This file contains a list, in reverse chronological order, of major
2008 breakages in tracking -current. It is not guaranteed to be a complete
2009 list of such breakages, and only contains entries since October 10, 2007.
2010 If you need to see UPDATING entries from before that date, you will need
2011 to fetch an UPDATING file from an older FreeBSD release.
2013 Copyright information:
2015 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2017 Redistribution, publication, translation and use, with or without
2018 modification, in full or in part, in any form or format of this
2019 document are permitted without further permission from the author.
2021 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2022 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2023 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2024 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2025 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2026 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2027 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2028 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2029 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2030 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2031 POSSIBILITY OF SUCH DAMAGE.
2033 Contact Warner Losh if you have any questions about your use of