1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
20 pjdfstest has been integrated into kyua as an opt-in test suite.
21 Please see share/doc/pjdfstest/README for a more details on how to
28 The ofwfb driver, used to provide a graphics console on PowerPC when
29 using vt(4), no longer allows mmap() of all of physical memory. This
30 will prevent Xorg on PowerPC with some ATI graphics cards from
31 initializing properly unless x11-servers/xorg-server is updated to
35 The libatf-c and libatf-c++ major versions were downgraded to 0 and
36 1 respectively to match the upstream numbers. They were out of
37 sync because, when they were originally added to FreeBSD, the
38 upstream versions were not respected. These libraries are private
39 and not yet built by default, so renumbering them should be a
40 non-issue. However, unclean source trees will yield broken test
41 programs once the operator executes "make delete-old-libs" after a
44 Additionally, the atf-sh binary was made private by moving it into
45 /usr/libexec/. Already-built shell test programs will keep the
46 path to the old binary so they will break after "make delete-old"
49 If you are using WITH_TESTS=yes (not the default), wipe the object
50 tree and rebuild from scratch to prevent spurious test failures.
51 This is only needed once: the misnumbered libraries and misplaced
52 binaries have been added to OptionalObsoleteFiles.inc so they will
53 be removed during a clean upgrade.
56 The ixgbe tunables now match their sysctl counterparts, for example:
57 hw.ixgbe.enable_aim => hw.ix.enable_aim
58 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
61 The NFSv4.1 server committed by r269398 changes the internal
62 function call interfaces used between the NFS and krpc modules.
63 As such, __FreeBSD_version was bumped.
66 The default unbound configuration has been modified to address
67 issues with reverse lookups on networks that use private
68 address ranges. If you use the local_unbound service, run
69 "service local_unbound setup" as root to regenerate your
70 configuration, then "service local_unbound reload" to load the
74 It is no longer necessary to include the dwarf version in your DEBUG
75 options in your kernel config file. The bug that required it to be
76 placed in the config file has bene fixed. DEBUG should now just
77 contain -g. The build system will automatically update things
78 to do the right thing.
81 Several ABI breaking changes were merged to CTL and new iSCSI code.
82 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
83 iscsictl need to be rebuilt to work with a new kernel.
86 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
87 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
88 which differs from the behaviour controlled by this knob.)
91 On i386 and amd64 systems, the onifconsole flag is now set by default
92 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
93 as a login TTY if it is set in the bootloader as an active kernel
94 console. No changes in behavior should result otherwise. To revert to
95 the previous behavior, set ttyu0 to "off" in /etc/ttys.
98 Clang and llvm have been upgraded to 3.4.1 release.
101 Clang and llvm have been upgraded to 3.4 release.
104 If a Makefile in a tests/ directory was auto-generating a Kyuafile
105 instead of providing an explicit one, this would prevent such
106 Makefile from providing its own Kyuafile in the future during
107 NO_CLEAN builds. This has been fixed in the Makefiles but manual
108 intervention is needed to clean an objdir if you use NO_CLEAN:
109 # find /usr/obj -name Kyuafile | xargs rm -f
112 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
113 capability mode support. Please note that enabling the feature in
114 kernel is still highly recommended.
117 OpenSSH is now built with sandbox support, and will use sandbox as
118 the default privilege separation method. This requires Capsicum
119 capability mode support in kernel.
122 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
123 been deprecated and will not be part of FreeBSD 11.0 and later
124 releases. If you use this driver, please consider switching to
125 the nfe(4) driver instead.
131 The behavior of gss_pseudo_random() for the krb5 mechanism
132 has changed, for applications requesting a longer random string
133 than produced by the underlying enctype's pseudo-random() function.
134 In particular, the random string produced from a session key of
135 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
136 be different at the 17th octet and later, after this change.
137 The counter used in the PRF+ construction is now encoded as a
138 big-endian integer in accordance with RFC 4402.
139 __FreeBSD_version is bumped to 1000701.
142 The WITHOUT_ATF build knob has been removed and its functionality
143 has been subsumed into the more generic WITHOUT_TESTS. If you were
144 using the former to disable the build of the ATF libraries, you
145 should change your settings to use the latter.
148 The default version of mtree is nmtree which is obtained from
149 NetBSD. The output is generally the same, but may vary
150 slightly. If you found you need identical output adding
151 "-F freebsd9" to the command line should do the trick. For the
152 time being, the old mtree is available as fmtree.
155 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
156 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
157 1.1.4_8 and verify bsdyml not linked in, before running "make
159 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
161 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
164 The rc.d/jail script has been updated to support jail(8)
165 configuration file. The "jail_<jname>_*" rc.conf(5) variables
166 for per-jail configuration are automatically converted to
167 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
168 This is transparently backward compatible. See below about some
169 incompatibilities and rc.conf(5) manual page for more details.
171 These variables are now deprecated in favor of jail(8) configuration
172 file. One can use "rc.d/jail config <jname>" command to generate
173 a jail(8) configuration file in /var/run/jail.<jname>.conf without
174 running the jail(8) utility. The default pathname of the
175 configuration file is /etc/jail.conf and can be specified by
176 using $jail_conf or $jail_<jname>_conf variables.
178 Please note that jail_devfs_ruleset accepts an integer at
179 this moment. Please consider to rewrite the ruleset name
183 BIND has been removed from the base system. If all you need
184 is a local resolver, simply enable and start the local_unbound
185 service instead. Otherwise, several versions of BIND are
186 available in the ports tree. The dns/bind99 port is one example.
188 With this change, nslookup(1) and dig(1) are no longer in the base
189 system. Users should instead use host(1) and drill(1) which are
190 in the base system. Alternatively, nslookup and dig can
191 be obtained by installing the dns/bind-tools port.
194 With the addition of unbound(8), a new unbound user is now
195 required during installworld. "mergemaster -p" can be used to
196 add the user prior to installworld, as documented in the handbook.
199 OpenSSH is now built with DNSSEC support, and will by default
200 silently trust signed SSHFP records. This can be controlled with
201 the VerifyHostKeyDNS client configuration setting. DNSSEC support
202 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
205 The GNU Compiler Collection and C++ standard library (libstdc++)
206 are no longer built by default on platforms where clang is the system
207 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
211 The PROCDESC kernel option is now part of the GENERIC kernel
212 configuration and is required for the rwhod(8) to work.
213 If you are using custom kernel configuration, you should include
217 The API and ABI related to the Capsicum framework was modified
218 in backward incompatible way. The userland libraries and programs
219 have to be recompiled to work with the new kernel. This includes the
220 following libraries and programs, but the whole buildworld is
221 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
222 kdump, procstat, rwho, rwhod, uniq.
225 AES-NI intrinsic support has been added to gcc. The AES-NI module
226 has been updated to use this support. A new gcc is required to build
227 the aesni module on both i386 and amd64.
230 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
231 Thus "device padlock_rng" and "device rdrand_rng" should be
232 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
235 WITH_ICONV has been split into two feature sets. WITH_ICONV now
236 enables just the iconv* functionality and is now on by default.
237 WITH_LIBICONV_COMPAT enables the libiconv api and link time
238 compatability. Set WITHOUT_ICONV to build the old way.
239 If you have been using WITH_ICONV before, you will very likely
240 need to turn on WITH_LIBICONV_COMPAT.
243 INVARIANTS option now enables DEBUG for code with OpenSolaris and
244 Illumos origin, including ZFS. If you have INVARIANTS in your
245 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
247 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
248 locks if WITNESS option was set. Because that generated a lot of
249 witness(9) reports and all of them were believed to be false
250 positives, this is no longer done. New option OPENSOLARIS_WITNESS
251 can be used to achieve the previous behavior.
254 Timer values in IPv6 data structures now use time_uptime instead
255 of time_second. Although this is not a user-visible functional
256 change, userland utilities which directly use them---ndp(8),
257 rtadvd(8), and rtsold(8) in the base system---need to be updated
261 find -delete can now delete the pathnames given as arguments,
262 instead of only files found below them or if the pathname did
263 not contain any slashes. Formerly, the following error message
266 find: -delete: <path>: relative path potentially not safe
268 Deleting the pathnames given as arguments can be prevented
269 without error messages using -mindepth 1 or by changing
270 directory and passing "." as argument to find. This works in the
271 old as well as the new version of find.
274 Behavior of devfs rules path matching has been changed.
275 Pattern is now always matched against fully qualified devfs
276 path and slash characters must be explicitly matched by
277 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
278 subdirectories must be reviewed.
281 The default ARM ABI has changed to the ARM EABI. The old ABI is
282 incompatible with the ARM EABI and all programs and modules will
283 need to be rebuilt to work with a new kernel.
285 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
287 NOTE: Support for the old ABI will be removed in the future and
288 users are advised to upgrade.
291 pkg_install has been disconnected from the build if you really need it
292 you should add WITH_PKGTOOLS in your src.conf(5).
295 Most of network statistics structures were changed to be able
296 keep 64-bits counters. Thus all tools, that work with networking
297 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
300 Fix targets that run multiple make's to use && rather than ;
301 so that subsequent steps depend on success of previous.
303 NOTE: if building 'universe' with -j* on stable/8 or stable/9
304 it would be better to start the build using bmake, to avoid
305 overloading the machine.
308 Fix a bug that allowed a tracing process (e.g. gdb) to write
309 to a memory-mapped file in the traced process's address space
310 even if neither the traced process nor the tracing process had
311 write access to that file.
314 CVS has been removed from the base system. An exact copy
315 of the code is available from the devel/cvs port.
318 Some people report the following error after the switch to bmake:
320 make: illegal option -- J
321 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
323 *** [buildworld] Error code 2
325 this likely due to an old instance of make in
326 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
327 which src/Makefile will use that blindly, if it exists, so if
328 you see the above error:
330 rm -rf `make -V MAKEPATH`
335 Use bmake by default.
336 Whereas before one could choose to build with bmake via
337 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
338 make. The goal is to remove these knobs for 10-RELEASE.
340 It is worth noting that bmake (like gmake) treats the command
341 line as the unit of failure, rather than statements within the
342 command line. Thus '(cd some/where && dosomething)' is safer
343 than 'cd some/where; dosomething'. The '()' allows consistent
344 behavior in parallel build.
347 Fix a bug that allows NFS clients to issue READDIR on files.
350 The WITHOUT_IDEA option has been removed because
351 the IDEA patent expired.
354 The sysctl which controls TRIM support under ZFS has been renamed
355 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
359 The mergemaster command now uses the default MAKEOBJDIRPREFIX
360 rather than creating it's own in the temporary directory in
361 order allow access to bootstrapped versions of tools such as
362 install and mtree. When upgrading from version of FreeBSD where
363 the install command does not support -l, you will need to
364 install a new mergemaster command if mergemaster -p is required.
365 This can be accomplished with the command (cd src/usr.sbin/mergemaster
369 Legacy ATA stack, disabled and replaced by new CAM-based one since
370 FreeBSD 9.0, completely removed from the sources. Kernel modules
371 atadisk and atapi*, user-level tools atacontrol and burncd are
372 removed. Kernel option `options ATA_CAM` is now permanently enabled
376 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
377 and socketpair(2). Software, in particular Kerberos, may
378 automatically detect and use these during building. The resulting
379 binaries will not work on older kernels.
382 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
383 information, see the respective 20130304 entry).
386 Recent commits to callout(9) changed the size of struct callout,
387 so the KBI is probably heavily disturbed. Also, some functions
388 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
389 by macros. Every kernel module using it won't load, so rebuild
392 The ctl device has been re-enabled in GENERIC for i386 and amd64,
393 but does not initialize by default (because of the new CTL_DISABLE
394 option) to save memory. To re-enable it, remove the CTL_DISABLE
395 option from the kernel config file or set kern.cam.ctl.disable=0
396 in /boot/loader.conf.
399 The ctl device has been disabled in GENERIC for i386 and amd64.
400 This was done due to the extra memory being allocated at system
401 initialisation time by the ctl driver which was only used if
402 a CAM target device was created. This makes a FreeBSD system
403 unusable on 128MB or less of RAM.
406 A new compression method (lz4) has been merged to -HEAD. Please
407 refer to zpool-features(7) for more information.
409 Please refer to the "ZFS notes" section of this file for information
410 on upgrading boot ZFS pools.
413 A BSD-licensed patch(1) variant has been added and is installed
414 as bsdpatch, being the GNU version the default patch.
415 To inverse the logic and use the BSD-licensed one as default,
416 while having the GNU version installed as gnupatch, rebuild
417 and install world with the WITH_BSD_PATCH knob set.
420 Due to the use of the new -l option to install(1) during build
421 and install, you must take care not to directly set the INSTALL
422 make variable in your /etc/make.conf, /etc/src.conf, or on the
423 command line. If you wish to use the -C flag for all installs
424 you may be able to add INSTALL+=-C to /etc/make.conf or
428 The install(1) option -M has changed meaning and now takes an
429 argument that is a file or path to append logs to. In the
430 unlikely event that -M was the last option on the command line
431 and the command line contained at least two files and a target
432 directory the first file will have logs appended to it. The -M
433 option served little practical purpose in the last decade so its
434 use is expected to be extremely rare.
437 After switching to Clang as the default compiler some users of ZFS
438 on i386 systems started to experience stack overflow kernel panics.
439 Please consider using 'options KSTACK_PAGES=4' in such configurations.
442 GEOM_LABEL now mangles label names read from file system metadata.
443 Mangling affect labels containing spaces, non-printable characters,
444 '%' or '"'. Device names in /etc/fstab and other places may need to
448 By default, only the 10 most recent kernel dumps will be saved. To
449 restore the previous behaviour (no limit on the number of kernel dumps
450 stored in the dump directory) add the following line to /etc/rc.conf:
455 With the addition of auditdistd(8), a new auditdistd user is now
456 required during installworld. "mergemaster -p" can be used to
457 add the user prior to installworld, as documented in the handbook.
460 The sin6_scope_id member variable in struct sockaddr_in6 is now
461 filled by the kernel before passing the structure to the userland via
462 sysctl or routing socket. This means the KAME-specific embedded scope
463 id in sin6_addr.s6_addr[2] is always cleared in userland application.
464 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
465 __FreeBSD_version is bumped to 1000025.
468 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
469 This means that the world and kernel will be compiled with clang
470 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
471 and /usr/bin/cpp. To disable this behavior and revert to building
472 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
473 of current may need to bootstrap WITHOUT_CLANG first if the clang
474 build fails (its compatibility window doesn't extend to the 9 stable
478 The IPFIREWALL_FORWARD kernel option has been removed. Its
479 functionality now turned on by default.
482 The ZERO_COPY_SOCKET kernel option has been removed and
483 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
484 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
485 mechanism which is not safe and may result in kernel crashes.
486 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
487 driver supports disposeable external page sized mbuf storage.
488 Proper replacements for both zero-copy mechanisms are under
489 consideration and will eventually lead to complete removal
490 of the two kernel options.
493 The IPv4 network stack has been converted to network byte
494 order. The following modules need to be recompiled together
495 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
496 pf(4), ipfw(4), ng_ipfw(4), stf(4).
499 Support for non-MPSAFE filesystems was removed from VFS. The
500 VFS_VERSION was bumped, all filesystem modules shall be
504 All the non-MPSAFE filesystems have been disconnected from
505 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
506 portalfs, smbfs, xfs.
509 The interface cloning API and ABI has changed. The following
510 modules need to be recompiled together with kernel:
511 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
512 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
513 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
516 The sdhci driver was split in two parts: sdhci (generic SD Host
517 Controller logic) and sdhci_pci (actual hardware driver).
518 No kernel config modifications are required, but if you
519 load sdhc as a module you must switch to sdhci_pci instead.
522 Import the FUSE kernel and userland support into base system.
525 The GNU sort(1) program has been removed since the BSD-licensed
526 sort(1) has been the default for quite some time and no serious
527 problems have been reported. The corresponding WITH_GNU_SORT
531 The pfil(9) API/ABI for AF_INET family has been changed. Packet
532 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
536 The net80211(4) ABI has been changed to allow for improved driver
537 PS-POLL and power-save support. All wireless drivers need to be
538 recompiled to work with the new kernel.
541 The random(4) support for the VIA hardware random number
542 generator (`PADLOCK') is no longer enabled unconditionally.
543 Add the padlock_rng device in the custom kernel config if
544 needed. The GENERIC kernels on i386 and amd64 do include the
545 device, so the change only affects the custom kernel
549 The pf(4) packet filter ABI has been changed. pfctl(8) and
550 snmp_pf module need to be recompiled to work with new kernel.
553 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
554 to -HEAD. Pools that have empty_bpobj in active state can not be
555 imported read-write with ZFS implementations that do not support
556 this feature. For more information read the zpool-features(5)
560 The sparc64 ZFS loader has been changed to no longer try to auto-
561 detect ZFS providers based on diskN aliases but now requires these
562 to be explicitly listed in the OFW boot-device environment variable.
565 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
566 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
567 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
570 The following sysctls and tunables have been renamed for consistency
571 with other variables:
572 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
573 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
576 The sort utility has been replaced with BSD sort. For now, GNU sort
577 is also available as "gnusort" or the default can be set back to
578 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
579 installed as "bsdsort".
582 A new version of ZFS (pool version 5000) has been merged to -HEAD.
583 Starting with this version the old system of ZFS pool versioning
584 is superseded by "feature flags". This concept enables forward
585 compatibility against certain future changes in functionality of ZFS
586 pools. The first read-only compatible "feature flag" for ZFS pools
587 is named "com.delphix:async_destroy". For more information
588 read the new zpool-features(5) manual page.
589 Please refer to the "ZFS notes" section of this file for information
590 on upgrading boot ZFS pools.
593 The malloc(3) implementation embedded in libc now uses sources imported
594 as contrib/jemalloc. The most disruptive API change is to
595 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
596 delete it prior to installworld, and optionally re-create it using the
597 new format after rebooting. See malloc.conf(5) for details
598 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
602 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
603 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
604 now spelled mips. This is to aid compatibility with third-party
605 software that expects this naming scheme in uname(3). Little-endian
606 settings are unchanged. If you are updating a big-endian mips64 machine
607 from before this change, you may need to set MACHINE_ARCH=mips64 in
608 your environment before the new build system will recognize your machine.
611 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
615 Now unix domain sockets behave "as expected" on nullfs(5). Previously
616 nullfs(5) did not pass through all behaviours to the underlying layer,
617 as a result if we bound to a socket on the lower layer we could connect
618 only to the lower path; if we bound to the upper layer we could connect
619 only to the upper path. The new behavior is one can connect to both the
620 lower and the upper paths regardless what layer path one binds to.
623 The getifaddrs upgrade path broken with 20111215 has been restored.
624 If you have upgraded in between 20111215 and 20120209 you need to
625 recompile libc again with your kernel. You still need to recompile
626 world to be able to configure CARP but this restriction already
630 The set_rcvar() function has been removed from /etc/rc.subr. All
631 base and ports rc.d scripts have been updated, so if you have a
632 port installed with a script in /usr/local/etc/rc.d you can either
633 hand-edit the rcvar= line, or reinstall the port.
635 An easy way to handle the mass-update of /etc/rc.d:
636 rm /etc/rc.d/* && mergemaster -i
639 panic(9) now stops other CPUs in the SMP systems, disables interrupts
640 on the current CPU and prevents other threads from running.
641 This behavior can be reverted using the kern.stop_scheduler_on_panic
643 The new behavior can be incompatible with kern.sync_on_panic.
646 The carp(4) facility has been changed significantly. Configuration
647 of the CARP protocol via ifconfig(8) has changed, as well as format
648 of CARP events submitted to devd(8) has changed. See manual pages
649 for more information. The arpbalance feature of carp(4) is currently
650 not supported anymore.
652 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
653 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
654 need to be recompiled.
657 The acpi_wmi(4) status device /dev/wmistat has been renamed to
661 The option VFS_ALLOW_NONMPSAFE option has been added in order to
662 explicitely support non-MPSAFE filesystems.
663 It is on by default for all supported platform at this present
667 The broken amd(4) driver has been replaced with esp(4) in the amd64,
668 i386 and pc98 GENERIC kernel configuration files.
671 sysinstall has been removed
674 The stable/9 branch created in subversion. This corresponds to the
675 RELENG_9 branch in CVS.
678 This commit modifies vfs_register() so that it uses a hash
679 calculation to set vfc_typenum, which is enabled by default.
680 The first time a system is booted after this change, the
681 vfc_typenum values will change for all file systems. The
682 main effect of this is a change to the NFS server file handles
683 for file systems that use vfc_typenum in their fsid, such as ZFS.
684 It will, however, prevent vfc_typenum from changing when file
685 systems are loaded in a different order for subsequent reboots.
686 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
687 until you are ready to remount all NFS clients after a reboot.
690 Bump the shared library version numbers for libraries that
691 do not use symbol versioning, have changed the ABI compared
692 to stable/8 and which shared library version was not bumped.
693 Done as part of 9.0-RELEASE cycle.
696 During the merge of Capsicum features, the fget(9) KPI was modified.
697 This may require the rebuilding of out-of-tree device drivers --
698 issues have been reported specifically with the nVidia device driver.
699 __FreeBSD_version is bumped to 900041.
701 Also, there is a period between 20110811 and 20110814 where the
702 special devices /dev/{stdin,stdout,stderr} did not work correctly.
703 Building world from a kernel during that window may not work.
706 The packet filter (pf) code has been updated to OpenBSD 4.5.
707 You need to update userland tools to be in sync with kernel.
708 This update breaks backward compatibility with earlier pfsync(4)
709 versions. Care must be taken when updating redundant firewall setups.
712 The following sysctls and tunables are retired on x86 platforms:
714 machdep.hlt_logical_cpus
715 The following sysctl is retired:
716 machdep.hyperthreading_allowed
717 The sysctls were supposed to provide a way to dynamically offline and
718 online selected CPUs on x86 platforms, but the implementation has not
719 been reliable especially with SCHED_ULE scheduler.
720 machdep.hyperthreading_allowed tunable is still available to ignore
721 hyperthreading CPUs at OS level.
722 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
723 where X is an APIC ID of a CPU. Be advised, though, that disabling
724 CPUs in non-uniform fashion will result in non-uniform topology and
725 may lead to sub-optimal system performance with SCHED_ULE, which is
729 cpumask_t type is retired and cpuset_t is used in order to describe
733 Changes to ifconfig(8) for dynamic address family detection mandate
734 that you are running a kernel of 20110525 or later. Make sure to
735 follow the update procedure to boot a new kernel before installing
739 Support for sun4v architecture is officially dropped
742 Several KPI breaking changes have been committed to the mii(4) layer,
743 the PHY drivers and consequently some Ethernet drivers using mii(4).
744 This means that miibus.ko and the modules of the affected Ethernet
745 drivers need to be recompiled.
747 Note to kernel developers: Given that the OUI bit reversion problem
748 was fixed as part of these changes all mii(4) commits related to OUIs,
749 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
750 handling, no longer can be merged verbatim to stable/8 and previous
754 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
755 into their kernel configurations along with 'device pci'.
758 The default NFS client is now the new NFS client, so fstype "newnfs"
759 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
760 Although mounts via fstype "nfs" will usually work without userland
761 changes, it is recommended that the mount(8) and mount_nfs(8)
762 commands be rebuilt from sources and that a link to mount_nfs called
763 mount_oldnfs be created. The new client is compiled into the
764 kernel with "options NFSCL" and this is needed for diskless root
765 file systems. The GENERIC kernel configs have been changed to use
766 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
767 To use the regular/old client, you can "mount -t oldnfs ...". For
768 a diskless root file system, you must also include a line like:
770 vfs.root.mountfrom="oldnfs:"
772 in the boot/loader.conf on the root fs on the NFS server to make
773 a diskless root fs use the old client.
776 The GENERIC kernels for all architectures now default to the new
777 CAM-based ATA stack. It means that all legacy ATA drivers were
778 removed and replaced by respective CAM drivers. If you are using
779 ATA device names in /etc/fstab or other places, make sure to update
780 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
781 where 'Y's are the sequential numbers starting from zero for each type
782 in order of detection, unless configured otherwise with tunables,
783 see cam(4)). There will be symbolic links created in /dev/ to map
784 old adX devices to the respective adaY. They should provide basic
785 compatibility for file systems mounting in most cases, but they do
786 not support old user-level APIs and do not have respective providers
787 in GEOM. Consider using updated management tools with new device names.
789 It is possible to load devices ahci, ata, siis and mvs as modules,
790 but option ATA_CAM should remain in kernel configuration to make ata
791 module work as CAM driver supporting legacy ATA controllers. Device ata
792 still can be used in modular fashion (atacore + ...). Modules atadisk
793 and atapi* are not used and won't affect operation in ATA_CAM mode.
794 Note that to use CAM-based ATA kernel should include CAM devices
795 scbus, pass, da (or explicitly ada), cd and optionally others. All of
796 them are parts of the cam module.
798 ataraid(4) functionality is now supported by the RAID GEOM class.
799 To use it you can load geom_raid kernel module and use graid(8) tool
800 for management. Instead of /dev/arX device names, use /dev/raid/rX.
802 No kernel config options or code have been removed, so if a problem
803 arises, please report it and optionally revert to the old ATA stack.
804 In order to do it you can remove from the kernel config:
809 , and instead add back:
810 device atadisk # ATA disk drives
811 device ataraid # ATA RAID drives
812 device atapicd # ATAPI CDROM drives
813 device atapifd # ATAPI floppy drives
814 device atapist # ATAPI tape drives
817 The default NFS server has been changed to the new server, which
818 was referred to as the experimental server. If you need to switch
819 back to the old NFS server, you must now put the "-o" option on
820 both the mountd and nfsd commands. This can be done using the
821 mountd_flags and nfs_server_flags rc.conf variables until an
822 update to the rc scripts is committed, which is coming soon.
825 The GNU Objective-C runtime library (libobjc), and other Objective-C
826 related components have been removed from the base system. If you
827 require an Objective-C library, please use one of the available ports.
830 ath(4) has been split into bus- and device- modules. if_ath contains
831 the HAL, the TX rate control and the network device code. if_ath_pci
832 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
833 contains the AHB glue. Users need to load both if_ath_pci and if_ath
834 in order to use ath on everything else.
836 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
837 need to load if_ath and if_ath_pci for ath(4) operation.
840 As part of the replacement of sysinstall, the process of building
841 release media has changed significantly. For details, please re-read
842 release(7), which has been updated to reflect the new build process.
845 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
846 is the last available version under GPLv2. It brings a number of new
847 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
848 4.1 and SSE 4.2), better support for powerpc64, a number of new
849 directives, and lots of other small improvements. See the ChangeLog
850 file in contrib/binutils for the full details.
853 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
854 compliant, and will now use half of hash for authentication.
855 This will break interoperability with all stacks (including all
856 actual FreeBSD versions) who implement
857 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
859 The only workaround with such peers is to use another HMAC
860 algorithm for IPsec ("phase 2") authentication.
863 Remove the uio_yield prototype and symbol. This function has
864 been misnamed since it was introduced and should not be
865 globally exposed with this name. The equivalent functionality
866 is now available using kern_yield(curthread->td_user_pri).
867 The function remains undocumented.
870 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
871 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
872 for scalar sysctls is defined but disabled. Code that needs
873 UQUAD to pass the type checking that must compile on older
874 systems where the define is not present can check against
875 __FreeBSD_version >= 900030.
877 The system dialog(1) has been replaced with a new version previously
878 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
879 with the previous version, but the libdialog associated with it has
880 a largely incompatible API. As such, the original version of libdialog
881 will be kept temporarily as libodialog, until its base system consumers
882 are replaced or updated. Bump __FreeBSD_version to 900030.
885 If you are trying to run make universe on a -stable system, and you get
886 the following warning:
887 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
888 unknown. config(8) likely too old."
889 or something similar to it, then you must upgrade your -stable system
890 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
891 stable/8) or build the config from the latest stable/8 branch and
892 install it on your system.
894 Prior to this date, building a current universe on 8-stable system from
895 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
896 error in the first kernel build phase. A new config on those old
897 systems will fix that problem for older versions of -current.
900 The TCP stack has been modified to allow Khelp modules to interact with
901 it via helper hook points and store per-connection data in the TCP
902 control block. Bump __FreeBSD_version to 900029. User space tools that
903 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
907 Generic IEEE 802.3 annex 31B full duplex flow control support has been
908 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
909 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
910 to take advantage of it instead of using custom implementations. This
911 means that these drivers now no longer unconditionally advertise
912 support for flow control but only do so if flow control is a selected
913 media option. This was implemented in the generic support that way in
914 order to allow flow control to be switched on and off via ifconfig(8)
915 with the PHY specific default to typically off in order to protect
916 from unwanted effects. Consequently, if you used flow control with
917 one of the above mentioned drivers you now need to explicitly enable
919 ifconfig bge0 media auto mediaopt flowcontrol
921 Along with the above mentioned changes generic support for setting
922 1000baseT master mode also has been added and brgphy(4), ciphy(4),
923 e1000phy(4) as well as ip1000phy(4) have been converted to take
924 advantage of it. This means that these drivers now no longer take the
925 link0 parameter for selecting master mode but the master media option
926 has to be used instead, for example like in the following:
927 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
929 Selection of master mode now is also available with all other PHY
930 drivers supporting 1000baseT.
933 The TCP stack has received a significant update to add support for
934 modularised congestion control and generally improve the clarity of
935 congestion control decisions. Bump __FreeBSD_version to 900025. User
936 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
937 sockstat) need to be recompiled.
940 The man(1) utility has been replaced by a new version that no longer
941 uses /etc/manpath.config. Please consult man.conf(5) for how to
942 migrate local entries to the new format.
945 The copyright strings printed by login(1) and sshd(8) at the time of a
946 new connection have been removed to follow other operating systems and
950 A workaround for a fixed ld bug has been removed in kernel code,
951 so make sure that your system ld is built from sources after
952 revision 210245 from 2010-07-19 (r211583 if building head kernel
953 on stable/8, r211584 for stable/7; both from 2010-08-21).
954 A symptom of incorrect ld version is different addresses for
955 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
958 The $ipv6_prefer variable in rc.conf(5) has been split into
959 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
961 The $ip6addrctl_policy is a variable to choose a pre-defined
962 address selection policy set by ip6addrctl(8). A value
963 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
966 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
967 flag (see an entry of 20090926) is set on an interface with no
968 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
969 security reason. If you want IPv6 link-local address on all
970 interfaces by default, set this to "YES".
972 The old ipv6_prefer="YES" is equivalent to
973 ipv6_activate_all_interfaces="YES" and
974 ip6addrctl_policy="ipv6_prefer".
977 DTrace has grown support for userland tracing. Due to this, DTrace is
978 now i386 and amd64 only.
979 dtruss(1) is now installed by default on those systems and a new
980 kernel module is needed for userland tracing: fasttrap.
981 No changes to your kernel config file are necessary to enable
982 userland tracing, but you might consider adding 'STRIP=' and
983 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
984 to have informative userland stack traces in DTrace (ustack).
987 The acpi_aiboost(4) driver has been removed in favor of the new
988 aibs(4) driver. You should update your kernel configuration file.
991 BSD grep has been imported to the base system and it is built by
992 default. It is completely BSD licensed, highly GNU-compatible, uses
993 less memory than its GNU counterpart and has a small codebase.
994 However, it is slower than its GNU counterpart, which is mostly
995 noticeable for larger searches, for smaller ones it is measurable
996 but not significant. The reason is complex, the most important factor
997 is that we lack a modern and efficient regex library and GNU
998 overcomes this by optimizing the searches internally. Future work
999 on improving the regex performance is planned, for the meantime,
1000 users that need better performance, can build GNU grep instead by
1001 setting the WITH_GNU_GREP knob.
1004 Due to the import of powerpc64 support, all existing powerpc kernel
1005 configuration files must be updated with a machine directive like this:
1006 machine powerpc powerpc
1008 In addition, an updated config(8) is required to build powerpc kernels
1012 A new version of ZFS (version 15) has been merged to -HEAD.
1013 This version uses a python library for the following subcommands:
1014 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1015 For full functionality of these commands the following port must
1016 be installed: sysutils/py-zfs
1019 'vm_page's are now hashed by physical address to an array of mutexes.
1020 Currently this is only used to serialize access to hold_count. Over
1021 time the page queue mutex will be peeled away. This changes the size
1022 of pmap on every architecture. And requires all callers of vm_page_hold
1023 and vm_page_unhold to be updated.
1026 WITH_CTF can now be specified in src.conf (not recommended, there
1027 are some problems with static executables), make.conf (would also
1028 affect ports which do not use GNU make and do not override the
1029 compile targets) or in the kernel config (via "makeoptions
1031 When WITH_CTF was specified there before this was silently ignored,
1032 so make sure that WITH_CTF is not used in places which could lead
1033 to unwanted behavior.
1036 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1037 to allow 32-bit compatibility on non-x86 platforms. All kernel
1038 configurations on amd64 and ia64 platforms using these options must
1039 be modified accordingly.
1042 The utmp user accounting database has been replaced with utmpx,
1043 the user accounting interface standardized by POSIX.
1044 Unfortunately the semantics of utmp and utmpx don't match,
1045 making it practically impossible to support both interfaces.
1046 The user accounting database is used by tools like finger(1),
1047 last(1), talk(1), w(1) and ac(8).
1049 All applications in the base system use utmpx. This means only
1050 local binaries (e.g. from the ports tree) may still use these
1051 utmp database files. These applications must be rebuilt to make
1054 After the system has been upgraded, it is safe to remove the old
1055 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1056 assuming their contents is of no importance anymore. Old wtmp
1057 databases can only be used by last(1) and ac(8) after they have
1058 been converted to the new format using wtmpcvt(1).
1061 Introduce the kernel thread "deadlock resolver" (which can be enabled
1062 via the DEADLKRES option, see NOTES for more details) and the
1063 sleepq_type() function for sleepqueues.
1066 The rc.firewall and rc.firewall6 were unified, and
1067 rc.firewall6 and rc.d/ip6fw were removed.
1068 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1069 variables are obsoleted. Instead, the following new rc
1070 variables are added to rc.d/ipfw:
1072 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1073 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1074 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1076 The meanings correspond to the relevant IPv4 variables.
1082 The default terminal emulation for syscons(4) has been changed
1083 from cons25 to xterm on all platforms except pc98. This means
1084 that the /etc/ttys file needs to be updated to ensure correct
1085 operation of applications on the console.
1087 The terminal emulation style can be toggled per window by using
1088 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1089 options can be used to change the compile-time default back to
1092 To prevent graphical artifacts, make sure the TERM environment
1093 variable is set to match the terminal emulation that is being
1094 performed by syscons(4).
1097 The layout of the structure ieee80211req_scan_result has changed.
1098 Applications that require wireless scan results (e.g. ifconfig(8))
1099 from net80211 need to be recompiled.
1101 Applications such as wpa_supplicant(8) may require a full world
1102 build without using NO_CLEAN in order to get synchronized with the
1106 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1107 There's one kernel module for each firmware. Adding "device iwnfw"
1108 to the kernel configuration file means including all three firmware
1109 images inside the kernel. If you want to include just the one for
1110 your wireless card, use the devices iwn4965fw, iwn5000fw or
1114 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1115 into rc.d/netif. The changes are the following:
1117 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1118 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1119 Note that both variables need the "inet6" keyword at the head.
1121 Do not set $ipv6_network_interfaces manually if you do not
1122 understand what you are doing. It is not needed in most cases.
1124 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1127 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1128 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1130 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1131 all configured interfaces have "inet6 accept_rtadv" in the
1132 $ifconfig_IF_ipv6. These are for backward compatibility.
1134 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1135 functionality of interfaces with no corresponding
1136 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1137 and the default address selection policy of ip6addrctl(8)
1138 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1139 Note that if you want to configure IPv6 functionality on the
1140 disabled interfaces after boot, first you need to clear the flag by
1141 using ifconfig(8) like:
1143 ifconfig em0 inet6 -ifdisabled
1145 If YES, the default address selection policy is set as
1148 The default value of $ipv6_prefer is NO.
1150 4. If your system need to receive Router Advertisement messages,
1151 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1152 scripts automatically invoke rtsol(8) when the interface becomes
1153 UP. The Router Advertisement messages are used for SLAAC
1154 (State-Less Address AutoConfiguration).
1157 802.11s D3.03 support was committed. This is incompatible with the
1158 previous code, which was based on D3.0.
1161 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1162 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1163 control whether accepting Router Advertisement messages or not.
1164 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1165 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1166 The ifconfig(8) utility now supports these flags.
1169 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1170 mount(8) and -a option for df(1) to see them.
1173 The old tunable hw.bus.devctl_disable has been superseded by
1174 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1175 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1179 Remove the option STOP_NMI. The default action is now to use NMI only
1180 for KDB via the newly introduced function stop_cpus_hard() and
1181 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1184 The stable/8 branch created in subversion. This corresponds to the
1185 RELENG_8 branch in CVS.
1188 Bump the shared library version numbers for all libraries that do not
1189 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1190 __FreeBSD_version to 800105.
1193 Due to changes in the implementation of virtual network stack support,
1194 all network-related kernel modules must be recompiled. As this change
1195 breaks the ABI, bump __FreeBSD_version to 800104.
1198 The TOE interface to the TCP syncache has been modified to remove
1199 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1200 The cxgb driver is the only TOE consumer affected by this change, and
1201 needs to be recompiled along with the kernel. As this change breaks
1202 the ABI, bump __FreeBSD_version to 800103.
1205 Padding has been added to struct tcpcb, sackhint and tcpstat in
1206 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1207 maintaining the ABI. However, this change breaks the ABI, so bump
1208 __FreeBSD_version to 800102. User space tools that rely on the size of
1209 any of these structs (e.g. sockstat) need to be recompiled.
1212 The NFS_LEGACYRPC option has been removed along with the old kernel
1213 RPC implementation that this option selected. Kernel configurations
1214 may need to be adjusted.
1217 The network interface device nodes at /dev/net/<interface> have been
1218 removed. All ioctl operations can be performed the normal way using
1219 routing sockets. The kqueue functionality can generally be replaced
1220 with routing sockets.
1223 The documentation from the FreeBSD Documentation Project (Handbook,
1224 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1225 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1228 The ABI of various structures related to the SYSV IPC API have been
1229 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1230 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1234 Layout of struct vnet has changed as routing related variables were
1235 moved to their own Vimage module. Modules need to be recompiled. Bump
1236 __FreeBSD_version to 800099.
1239 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1240 respectively. As long as no more than 16 groups per process are used,
1241 no changes should be visible. When more than 16 groups are used, old
1242 binaries may fail if they call getgroups() or getgrouplist() with
1243 statically sized storage. Recompiling will work around this, but
1244 applications should be modified to use dynamically allocated storage
1245 for group arrays as POSIX.1-2008 does not cap an implementation's
1246 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1248 NFS and portalfs mounts may also be affected as the list of groups is
1249 truncated to 16. Users of NFS who use more than 16 groups, should
1250 take care that negative group permissions are not used on the exported
1251 file systems as they will not be reliable unless a GSSAPI based
1252 authentication method is used.
1255 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1256 option compiles in the support for adaptive spinning for lockmgrs
1257 which want to enable it. The lockinit() function now accepts the flag
1258 LK_ADAPTIVE in order to make the lock object subject to adaptive
1259 spinning when both held in write and read mode.
1262 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1263 changed. User applications that use this ioctl need to be rebuilt.
1266 The layout of struct thread has changed. Kernel and modules need to
1270 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1271 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1274 window(1) has been removed from the base system. It can now be
1275 installed from ports. The port is called misc/window.
1278 The way we are storing and accessing `routing table' entries has
1279 changed. Programs reading the FIB, like netstat, need to be
1283 A new netisr implementation has been added for FreeBSD 8. Network
1284 file system modules, such as igmp, ipdivert, and others, should be
1286 Bump __FreeBSD_version to 800096.
1289 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1293 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1294 Bump __FreeBSD_version to 800094.
1297 Add mnt_xflag field to 'struct mount'. File system modules need to be
1299 Bump __FreeBSD_version to 800093.
1302 The compiling option ADAPTIVE_SX has been retired while it has been
1303 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1304 The KPI for sx_init_flags() changes as accepting flags:
1305 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1306 been introduced in order to handle the reversed logic.
1307 Bump __FreeBSD_version to 800092.
1310 Add support for hierarchical jails. Remove global securelevel.
1311 Bump __FreeBSD_version to 800091.
1314 The layout of struct vnet_net has changed, therefore modules
1316 Bump __FreeBSD_version to 800090.
1319 The newly imported zic(8) produces a new format in the output. Please
1320 run tzsetup(8) to install the newly created data to /etc/localtime.
1323 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1324 hw.usb.* and is now consistent again with previous releases.
1327 802.11 monitor mode support was revised and driver api's were changed.
1328 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1329 of DLT_IEEE802_11. No user-visible data structures were changed but
1330 applications that use DLT_IEEE802_11 may require changes.
1331 Bump __FreeBSD_version to 800088.
1334 The layout of the following structs has changed: sysctl_oid,
1335 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1336 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1337 panics may be experienced. World rebuild is required for
1338 correctly checking networking state from userland.
1339 Bump __FreeBSD_version to 800085.
1342 MLDv2 and Source-Specific Multicast (SSM) have been merged
1343 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1344 The implementation of SSM within FreeBSD's IPv6 stack closely
1345 follows the IPv4 implementation.
1347 For kernel developers:
1349 * The most important changes are that the ip6_output() and
1350 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1351 and this lock has been downgraded to a non-recursive mutex.
1353 * As with the changes to the IPv4 stack to support SSM, filtering
1354 of inbound multicast traffic must now be performed by transport
1355 protocols within the IPv6 stack. This does not apply to TCP and
1356 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1358 * The KPIs used by IPv6 multicast are similar to those used by
1359 the IPv4 stack, with the following differences:
1360 * im6o_mc_filter() is analogous to imo_multicast_filter().
1361 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1362 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1363 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1364 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1365 for MLDv1 have an additional 'timer' argument which is used to
1366 jitter the initial membership report for the solicited-node
1367 multicast membership on-link.
1368 * This is not strictly needed for MLDv2, which already jitters
1369 its report transmissions. However, the 'timer' argument is
1370 preserved in case MLDv1 is active on the interface.
1372 * The KAME linked-list based IPv6 membership implementation has
1373 been refactored to use a vector similar to that used by the IPv4
1375 Code which maintains a list of its own multicast memberships
1376 internally, e.g. carp, has been updated to reflect the new
1379 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1380 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1381 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1382 implementation constraint which needs to be addressed in HEAD.
1384 For application developers:
1386 * The changes are broadly similar to those made for the IPv4
1389 * The use of IPv4 and IPv6 multicast socket options on the same
1390 socket, using mapped addresses, HAS NOT been tested or supported.
1392 * There are a number of issues with the implementation of various
1393 IPv6 multicast APIs which need to be resolved in the API surface
1394 before the implementation is fully compatible with KAME userland
1395 use, and these are mostly to do with interface index treatment.
1397 * The literature available discusses the use of either the delta / ASM
1398 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1399 using setsourcefilter(3)/getsourcefilter(3). For more information
1400 please refer to RFC 3768, 'Socket Interface Extensions for
1401 Multicast Source Filters'.
1403 * Applications which use the published RFC 3678 APIs should be fine.
1405 For systems administrators:
1407 * The mtest(8) utility has been refactored to support IPv6, in
1408 addition to IPv4. Interface addresses are no longer accepted
1409 as arguments, their names must be used instead. The utility
1410 will map the interface name to its first IPv4 address as
1411 returned by getifaddrs(3).
1413 * The ifmcstat(8) utility has also been updated to print the MLDv2
1414 endpoint state and source filter lists via sysctl(3).
1416 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1417 loopback of IPv6 multicast datagrams by default; it defaults to 1
1418 to preserve the existing behaviour. Disabling multicast loopback is
1419 recommended for optimal system performance.
1421 * The IPv6 MROUTING code has been changed to examine this sysctl
1422 instead of attempting to perform a group lookup before looping
1423 back forwarded datagrams.
1425 Bump __FreeBSD_version to 800084.
1428 Implement low-level Bluetooth HCI API.
1429 Bump __FreeBSD_version to 800083.
1432 The layout of struct malloc_type, used by modules to register new
1433 memory allocation types, has changed. Most modules will need to
1434 be rebuilt or panics may be experienced.
1435 Bump __FreeBSD_version to 800081.
1438 Anticipate overflowing inp_flags - add inp_flags2.
1439 This changes most offsets in inpcb, so checking v4 connection
1440 state will require a world rebuild.
1441 Bump __FreeBSD_version to 800080.
1444 Add an llentry to struct route and struct route_in6. Modules
1445 embedding a struct route will need to be recompiled.
1446 Bump __FreeBSD_version to 800079.
1449 The size of rt_metrics_lite and by extension rtentry has changed.
1450 Networking administration apps will need to be recompiled.
1451 The route command now supports show as an alias for get, weighting
1452 of routes, sticky and nostick flags to alter the behavior of stateful
1454 Bump __FreeBSD_version to 800078.
1457 Do not use Giant for kbdmux(4) locking. This is wrong and
1458 apparently causing more problems than it solves. This will
1459 re-open the issue where interrupt handlers may race with
1460 kbdmux(4) in polling mode. Typical symptoms include (but
1461 not limited to) duplicated and/or missing characters when
1462 low level console functions (such as gets) are used while
1463 interrupts are enabled (for example geli password prompt,
1464 mountroot prompt etc.). Disabling kbdmux(4) may help.
1467 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1468 kernel modules referencing any of the above need to be recompiled.
1469 Bump __FreeBSD_version to 800075.
1472 GEOM_PART has become the default partition slicer for storage devices,
1473 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1474 introduces some changes:
1476 MSDOS/EBR: the devices created from MSDOS extended partition entries
1477 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1478 to devices with offset-based names. fstabs may need to be modified.
1480 BSD: the "geometry does not match label" warning is harmless in most
1481 cases but it points to problems in file system misalignment with
1482 disk geometry. The "c" partition is now implicit, covers the whole
1483 top-level drive and cannot be (mis)used by users.
1485 General: Kernel dumps are now not allowed to be written to devices
1486 whose partition types indicate they are meant to be used for file
1487 systems (or, in case of MSDOS partitions, as something else than
1490 Most of these changes date approximately from 200812.
1493 The uscanner(4) driver has been removed from the kernel. This follows
1494 Linux removing theirs in 2.6 and making libusb the default interface
1495 (supported by sane).
1498 The multicast forwarding code has been cleaned up. netstat(1)
1499 only relies on KVM now for printing bandwidth upcall meters.
1500 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1501 ip6_mroute_mod respectively. The config(5) options for statically
1502 compiling this code remain the same, i.e. 'options MROUTING'.
1505 Support for the IFF_NEEDSGIANT network interface flag has been
1506 removed, which means that non-MPSAFE network device drivers are no
1507 longer supported. In particular, if_ar, if_sr, and network device
1508 drivers from the old (legacy) USB stack can no longer be built or
1512 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1513 a bunch of new language catalog files have also been added.
1514 This means that some common libc messages are now localized and
1515 they depend on the LC_MESSAGES environmental variable.
1518 The k8temp(4) driver has been renamed to amdtemp(4) since
1519 support for Family 10 and Family 11 CPU families was added.
1522 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1523 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1525 For kernel developers, the most important changes are that the
1526 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1527 and this lock has been downgraded to a non-recursive mutex.
1529 Transport protocols (UDP, Raw IP) are now responsible for filtering
1530 inbound multicast traffic according to group membership and source
1531 filters. The imo_multicast_filter() KPI exists for this purpose.
1532 Transports which do not use multicast (SCTP, TCP) already reject
1533 multicast by default. Forwarding and receive performance may improve
1534 as a mutex acquisition is no longer needed in the ip_input()
1535 low-level input path. in_addmulti() and in_delmulti() are shimmed
1536 to new KPIs which exist to support SSM in-kernel.
1538 For application developers, it is recommended that loopback of
1539 multicast datagrams be disabled for best performance, as this
1540 will still cause the lock to be taken for each looped-back
1541 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1542 be tuned to 0 to disable loopback by default; it defaults to 1
1543 to preserve the existing behaviour.
1545 For systems administrators, to obtain best performance with
1546 multicast reception and multiple groups, it is always recommended
1547 that a card with a suitably precise hash filter is used. Hash
1548 collisions will still result in the lock being taken within the
1549 transport protocol input path to check group membership.
1551 If deploying FreeBSD in an environment with IGMP snooping switches,
1552 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1553 enabled; this forces 224.0.0.0/24 group membership to be announced
1556 The size of 'struct igmpstat' has changed; netstat needs to be
1557 recompiled to reflect this.
1558 Bump __FreeBSD_version to 800070.
1561 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1562 updated to use it. This requires a buildworld/installworld in order to
1563 update the library and dependencies (usbconfig, etc). Its advisable to
1564 rebuild all ports which uses libusb. More specific directions are given
1565 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1566 libusb are no longer required and can be removed.
1569 A workaround is committed to allow the creation of System V shared
1570 memory segment of size > 2 GB on the 64-bit architectures.
1571 Due to a limitation of the existing ABI, the shm_segsz member
1572 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1573 wrong for large segments. Note that limits must be explicitly
1574 raised to allow such segments to be created.
1577 The layout of struct ifnet has changed, requiring a rebuild of all
1578 network device driver modules.
1581 The /dev handling for the new USB stack has changed, a
1582 buildworld/installworld is required for libusb20.
1585 The new USB2 stack has now been permanently moved in and all kernel and
1586 module names reverted to their previous values (eg, usb, ehci, ohci,
1587 ums, ...). The old usb stack can be compiled in by prefixing the name
1588 with the letter 'o', the old usb modules have been removed.
1589 Updating entry 20090216 for xorg and 20090215 for libmap may still
1593 The rc.conf(5) option if_up_delay has been renamed to
1594 defaultroute_delay to better reflect its purpose. If you have
1595 customized this setting in /etc/rc.conf you need to update it to
1599 xorg 7.4 wants to configure its input devices via hald which does not
1600 yet work with USB2. If the keyboard/mouse does not work in xorg then
1602 Option "AllowEmptyInput" "off"
1603 to your ServerLayout section. This will cause X to use the configured
1604 kbd and mouse sections from your xorg.conf.
1607 The GENERIC kernels for all architectures now default to the new USB2
1608 stack. No kernel config options or code have been removed so if a
1609 problem arises please report it and optionally revert to the old USB
1610 stack. If you are loading USB kernel modules or have a custom kernel
1611 that includes GENERIC then ensure that usb names are also changed over,
1612 eg uftdi -> usb2_serial_ftdi.
1614 Older programs linked against the ports libusb 0.1 need to be
1615 redirected to the new stack's libusb20. /etc/libmap.conf can
1617 # Map old usb library to new one for usb2 stack
1618 libusb-0.1.so.8 libusb20.so.1
1621 All USB ethernet devices now attach as interfaces under the name ueN
1622 (eg. ue0). This is to provide a predictable name as vendors often
1623 change usb chipsets in a product without notice.
1626 The ichsmb(4) driver has been changed to require SMBus slave
1627 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1628 All of the other SMBus controller drivers require left-justified
1629 slave addresses, so this change makes all the drivers provide the
1633 INET6 statistics (struct ip6stat) was updated.
1634 netstat(1) needs to be recompiled.
1637 NTFS has been removed from GENERIC kernel on amd64 to match
1638 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1639 will load ntfs.ko module automatically when NTFS support is
1640 actually needed, unless ntfs.ko is not installed or security
1641 level prohibits loading kernel modules. If either is the case,
1642 "options NTFS" has to be added into kernel config.
1645 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1646 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1647 800061. User space tools that rely on the size of struct tcpcb in
1648 tcp_var.h (e.g. sockstat) need to be recompiled.
1651 ng_tty(4) module updated to match the new TTY subsystem.
1652 Due to API change, user-level applications must be updated.
1653 New API support added to mpd5 CVS and expected to be present
1654 in next mpd5.3 release.
1657 With __FreeBSD_version 800060 the makefs tool is part of
1658 the base system (it was a port).
1661 The afdata and ifnet locks have been changed from mutexes to
1662 rwlocks, network modules will need to be re-compiled.
1665 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1666 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1667 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1668 architecture and 40 bytes on 64-bit architecture. The userland
1669 applications "arp" and "ndp" have been updated accordingly.
1670 The output from "netstat -r" shows only routing entries and
1671 none of the L2 information.
1674 __FreeBSD_version 800057 marks the switchover from the
1675 binary ath hal to source code. Users must add the line:
1677 options AH_SUPPORT_AR5416
1679 to their kernel config files when specifying:
1683 The ath_hal module no longer exists; the code is now compiled
1684 together with the driver in the ath module. It is now
1685 possible to tailor chip support (i.e. reduce the set of chips
1686 and thereby the code size); consult ath_hal(4) for details.
1689 __FreeBSD_version 800054 adds memory barriers to
1690 <machine/atomic.h>, new interfaces to ifnet to facilitate
1691 multiple hardware transmit queues for cards that support
1692 them, and a lock-less ring-buffer implementation to
1693 enable drivers to more efficiently manage queueing of
1697 A new version of ZFS (version 13) has been merged to -HEAD.
1698 This version has zpool attribute "listsnapshots" off by
1699 default, which means "zfs list" does not show snapshots,
1700 and is the same as Solaris behavior.
1703 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1706 The uhci, ohci, ehci and slhci USB Host controller drivers have
1707 been put into separate modules. If you load the usb module
1708 separately through loader.conf you will need to load the
1709 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1710 controller add the following to loader.conf:
1716 The ABI used by the PMC toolset has changed. Please keep
1717 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1721 atapci kernel module now includes only generic PCI ATA
1722 driver. AHCI driver moved to ataahci kernel module.
1723 All vendor-specific code moved into separate kernel modules:
1724 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1725 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1726 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1727 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1730 The TTY subsystem of the kernel has been replaced by a new
1731 implementation, which provides better scalability and an
1732 improved driver model. Most common drivers have been migrated to
1733 the new TTY subsystem, while others have not. The following
1734 drivers have not yet been ported to the new TTY layer:
1737 cy, digi, rc, rp, sio
1743 ng_h4, ng_tty, ppp, sl, snp
1745 Adding these drivers to your kernel configuration file shall
1746 cause compilation to fail.
1749 ntpd has been upgraded to 4.2.4p5.
1752 OpenSSH has been upgraded to 5.1p1.
1754 For many years, FreeBSD's version of OpenSSH preferred DSA
1755 over RSA for host and user authentication keys. With this
1756 upgrade, we've switched to the vendor's default of RSA over
1757 DSA. This may cause upgraded clients to warn about unknown
1758 host keys even for previously known hosts. Users should
1759 follow the usual procedure for verifying host keys before
1760 accepting the RSA key.
1762 This can be circumvented by setting the "HostKeyAlgorithms"
1763 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1766 Please note that the sequence of keys offered for
1767 authentication has been changed as well. You may want to
1768 specify IdentityFile in a different order to revert this
1772 The sio(4) driver has been removed from the i386 and amd64
1773 kernel configuration files. This means uart(4) is now the
1774 default serial port driver on those platforms as well.
1776 To prevent collisions with the sio(4) driver, the uart(4) driver
1777 uses different names for its device nodes. This means the
1778 onboard serial port will now most likely be called "ttyu0"
1779 instead of "ttyd0". You may need to reconfigure applications to
1780 use the new device names.
1782 When using the serial port as a boot console, be sure to update
1783 /boot/device.hints and /etc/ttys before booting the new kernel.
1784 If you forget to do so, you can still manually specify the hints
1785 at the loader prompt:
1787 set hint.uart.0.at="isa"
1788 set hint.uart.0.port="0x3F8"
1789 set hint.uart.0.flags="0x10"
1790 set hint.uart.0.irq="4"
1794 The gpt(8) utility has been removed. Use gpart(8) to partition
1798 The version that Linuxulator emulates was changed from 2.4.2
1799 to 2.6.16. If you experience any problems with Linux binaries
1800 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1801 if it fixes the problem contact emulation mailing list.
1804 ISDN4BSD (I4B) was removed from the src tree. You may need to
1805 update a your kernel configuration and remove relevant entries.
1808 I have checked in code to support multiple routing tables.
1809 See the man pages setfib(1) and setfib(2).
1810 This is a hopefully backwards compatible version,
1811 but to make use of it you need to compile your kernel
1812 with options ROUTETABLES=2 (or more up to 16).
1815 The 802.11 wireless support was redone to enable multi-bss
1816 operation on devices that are capable. The underlying device
1817 is no longer used directly but instead wlanX devices are
1818 cloned with ifconfig. This requires changes to rc.conf files.
1819 For example, change:
1820 ifconfig_ath0="WPA DHCP"
1823 ifconfig_wlan0="WPA DHCP"
1824 see rc.conf(5) for more details. In addition, mergemaster of
1825 /etc/rc.d is highly recommended. Simultaneous update of userland
1826 and kernel wouldn't hurt either.
1828 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1829 modules were merged into the base wlan module. All references
1830 to these modules (e.g. in kernel config files) must be removed.
1833 psm(4) has gained write(2) support in native operation level.
1834 Arbitrary commands can be written to /dev/psm%d and status can
1835 be read back from it. Therefore, an application is responsible
1836 for status validation and error recovery. It is a no-op in
1837 other operation levels.
1840 Support for KSE threading has been removed from the kernel. To
1841 run legacy applications linked against KSE libmap.conf may
1842 be used. The following libmap.conf may be used to ensure
1843 compatibility with any prior release:
1845 libpthread.so.1 libthr.so.1
1846 libpthread.so.2 libthr.so.2
1847 libkse.so.3 libthr.so.3
1850 The layout of struct vmspace has changed. This affects libkvm
1851 and any executables that link against libkvm and use the
1852 kvm_getprocs() function. In particular, but not exclusively,
1853 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1854 The effects are minimal, but it's advisable to upgrade world
1858 The latest em driver no longer has support in it for the
1859 82575 adapter, this is now moved to the igb driver. The
1860 split was done to make new features that are incompatible
1861 with older hardware easier to do.
1864 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1865 likewise the kernel option is now GEOM_LINUX_LVM.
1868 The default NFS mount mode has changed from UDP to TCP for
1869 increased reliability. If you rely on (insecurely) NFS
1870 mounting across a firewall you may need to update your
1874 Belatedly note the addition of m_collapse for compacting
1878 The fts(3) structures have been changed to use adequate
1879 integer types for their members and so to be able to cope
1880 with huge file trees. The old fts(3) ABI is preserved
1881 through symbol versioning in libc, so third-party binaries
1882 using fts(3) should still work, although they will not take
1883 advantage of the extended types. At the same time, some
1884 third-party software might fail to build after this change
1885 due to unportable assumptions made in its source code about
1886 fts(3) structure members. Such software should be fixed
1887 by its vendor or, in the worst case, in the ports tree.
1888 FreeBSD_version 800015 marks this change for the unlikely
1889 case that a portable fix is impossible.
1892 To upgrade to -current after this date, you must be running
1893 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1894 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1897 The ADAPTIVE_GIANT kernel option has been retired because its
1898 functionality is the default now.
1901 The AT keyboard emulation of sunkbd(4) has been turned on
1902 by default. In order to make the special symbols of the Sun
1903 keyboards driven by sunkbd(4) work under X these now have
1904 to be configured the same way as Sun USB keyboards driven
1905 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1907 Option "XkbLayout" "us"
1908 Option "XkbRules" "xorg"
1909 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1912 It has been decided that it is desirable to provide ABI
1913 backwards compatibility to the FreeBSD 4/5/6 versions of the
1914 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1915 broken with the introduction of PCI domain support (see the
1916 20070930 entry). Unfortunately, this required the ABI of
1917 PCIOCGETCONF to be broken again in order to be able to
1918 provide backwards compatibility to the old version of that
1919 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1920 again. As for prominent ports this affects neither pciutils
1921 nor xorg-server this time, the hal port needs to be rebuilt
1925 The misnamed kthread_create() and friends have been renamed
1926 to kproc_create() etc. Many of the callers already
1927 used kproc_start()..
1928 I will return kthread_create() and friends in a while
1929 with implementations that actually create threads, not procs.
1930 Renaming corresponds with version 800002.
1939 Avoid using make -j when upgrading. While generally safe, there are
1940 sometimes problems using -j to upgrade. If your upgrade fails with
1941 -j, please try again without -j. From time to time in the past there
1942 have been problems using -j with buildworld and/or installworld. This
1943 is especially true when upgrading between "distant" versions (eg one
1944 that cross a major release boundary or several minor releases, or when
1945 several months have passed on the -current branch).
1947 Sometimes, obscure build problems are the result of environment
1948 poisoning. This can happen because the make utility reads its
1949 environment when searching for values for global variables. To run
1950 your build attempts in an "environmental clean room", prefix all make
1951 commands with 'env -i '. See the env(1) manual page for more details.
1953 When upgrading from one major version to another it is generally best
1954 to upgrade to the latest code in the currently installed branch first,
1955 then do an upgrade to the new branch. This is the best-tested upgrade
1956 path, and has the highest probability of being successful. Please try
1957 this approach before reporting problems with a major version upgrade.
1959 When upgrading a live system, having a root shell around before
1960 installing anything can help undo problems. Not having a root shell
1961 around can lead to problems if pam has changed too much from your
1962 starting point to allow continued authentication after the upgrade.
1966 When upgrading the boot ZFS pool to a new version, always follow
1969 1.) recompile and reinstall the ZFS boot loader and boot block
1970 (this is part of "make buildworld" and "make installworld")
1972 2.) update the ZFS boot block on your boot drive
1974 The following example updates the ZFS boot block on the first
1975 partition (freebsd-boot) of a GPT partitioned drive ad0:
1976 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1978 Non-boot pools do not need these updates.
1982 If you are updating from a prior version of FreeBSD (even one just
1983 a few days old), you should follow this procedure. It is the most
1984 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1986 make kernel-toolchain
1987 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1988 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1990 To test a kernel once
1991 ---------------------
1992 If you just want to boot a kernel once (because you are not sure
1993 if it works, or if you want to boot a known bad kernel to provide
1994 debugging information) run
1995 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1996 nextboot -k testkernel
1998 To just build a kernel when you know that it won't mess you up
1999 --------------------------------------------------------------
2000 This assumes you are already running a CURRENT system. Replace
2001 ${arch} with the architecture of your machine (e.g. "i386",
2002 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2004 cd src/sys/${arch}/conf
2005 config KERNEL_NAME_HERE
2006 cd ../compile/KERNEL_NAME_HERE
2011 If this fails, go to the "To build a kernel" section.
2013 To rebuild everything and install it on the current system.
2014 -----------------------------------------------------------
2015 # Note: sometimes if you are running current you gotta do more than
2016 # is listed here if you are upgrading from a really old current.
2018 <make sure you have good level 0 dumps>
2020 make kernel KERNCONF=YOUR_KERNEL_HERE
2022 <reboot in single user> [3]
2029 To cross-install current onto a separate partition
2030 --------------------------------------------------
2031 # In this approach we use a separate partition to hold
2032 # current's root, 'usr', and 'var' directories. A partition
2033 # holding "/", "/usr" and "/var" should be about 2GB in
2036 <make sure you have good level 0 dumps>
2039 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2040 <maybe newfs current's root partition>
2041 <mount current's root partition on directory ${CURRENT_ROOT}>
2042 make installworld DESTDIR=${CURRENT_ROOT}
2043 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2044 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2045 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2046 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2047 <reboot into current>
2048 <do a "native" rebuild/install as described in the previous section>
2049 <maybe install compatibility libraries from ports/misc/compat*>
2053 To upgrade in-place from stable to current
2054 ----------------------------------------------
2055 <make sure you have good level 0 dumps>
2057 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2059 <reboot in single user> [3]
2066 Make sure that you've read the UPDATING file to understand the
2067 tweaks to various things you need. At this point in the life
2068 cycle of current, things change often and you are on your own
2069 to cope. The defaults can also change, so please read ALL of
2070 the UPDATING entries.
2072 Also, if you are tracking -current, you must be subscribed to
2073 freebsd-current@freebsd.org. Make sure that before you update
2074 your sources that you have read and understood all the recent
2075 messages there. If in doubt, please track -stable which has
2076 much fewer pitfalls.
2078 [1] If you have third party modules, such as vmware, you
2079 should disable them at this point so they don't crash your
2082 [3] From the bootblocks, boot -s, and then do
2087 adjkerntz -i # if CMOS is wall time
2088 Also, when doing a major release upgrade, it is required that
2089 you boot into single user mode to do the installworld.
2091 [4] Note: This step is non-optional. Failure to do this step
2092 can result in a significant reduction in the functionality of the
2093 system. Attempting to do it by hand is not recommended and those
2094 that pursue this avenue should read this file carefully, as well
2095 as the archives of freebsd-current and freebsd-hackers mailing lists
2096 for potential gotchas. The -U option is also useful to consider.
2097 See mergemaster(8) for more information.
2099 [5] Usually this step is a noop. However, from time to time
2100 you may need to do this if you get unknown user in the following
2101 step. It never hurts to do it all the time. You may need to
2102 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2103 install) after the buildworld before this step if you last updated
2104 from current before 20130425 or from -stable before 20130430.
2106 [6] This only deletes old files and directories. Old libraries
2107 can be deleted by "make delete-old-libs", but you have to make
2108 sure that no program is using those libraries anymore.
2110 [8] In order to have a kernel that can run the 4.x binaries needed to
2111 do an installworld, you must include the COMPAT_FREEBSD4 option in
2112 your kernel. Failure to do so may leave you with a system that is
2113 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2114 required to run the 5.x binaries on more recent kernels. And so on
2115 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2117 Make sure that you merge any new devices from GENERIC since the
2118 last time you updated your kernel config file.
2120 [9] When checking out sources, you must include the -P flag to have
2121 cvs prune empty directories.
2123 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2124 "?=" instead of the "=" assignment operator, so that buildworld can
2125 override the CPUTYPE if it needs to.
2127 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2128 not on the command line, or in /etc/make.conf. buildworld will
2129 warn if it is improperly defined.
2132 This file contains a list, in reverse chronological order, of major
2133 breakages in tracking -current. It is not guaranteed to be a complete
2134 list of such breakages, and only contains entries since October 10, 2007.
2135 If you need to see UPDATING entries from before that date, you will need
2136 to fetch an UPDATING file from an older FreeBSD release.
2138 Copyright information:
2140 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2142 Redistribution, publication, translation and use, with or without
2143 modification, in full or in part, in any form or format of this
2144 document are permitted without further permission from the author.
2146 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2147 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2148 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2149 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2150 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2151 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2152 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2153 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2154 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2155 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2156 POSSIBILITY OF SUCH DAMAGE.
2158 Contact Warner Losh if you have any questions about your use of