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