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 At svn r275807, The default linux compat kernel ABI has been adjusted
21 to 2.6.18 in support of the linux-c6 compat ports infrastructure
22 update. If you wish to continue using the linux-f10 compat ports,
23 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
24 encouraged to update their linux-compat packages to linux-c6 during
25 their next update cycle.
27 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
30 pjdfstest has been integrated into kyua as an opt-in test suite.
31 Please see share/doc/pjdfstest/README for a more details on how to
38 The ofwfb driver, used to provide a graphics console on PowerPC when
39 using vt(4), no longer allows mmap() of all of physical memory. This
40 will prevent Xorg on PowerPC with some ATI graphics cards from
41 initializing properly unless x11-servers/xorg-server is updated to
45 The libatf-c and libatf-c++ major versions were downgraded to 0 and
46 1 respectively to match the upstream numbers. They were out of
47 sync because, when they were originally added to FreeBSD, the
48 upstream versions were not respected. These libraries are private
49 and not yet built by default, so renumbering them should be a
50 non-issue. However, unclean source trees will yield broken test
51 programs once the operator executes "make delete-old-libs" after a
54 Additionally, the atf-sh binary was made private by moving it into
55 /usr/libexec/. Already-built shell test programs will keep the
56 path to the old binary so they will break after "make delete-old"
59 If you are using WITH_TESTS=yes (not the default), wipe the object
60 tree and rebuild from scratch to prevent spurious test failures.
61 This is only needed once: the misnumbered libraries and misplaced
62 binaries have been added to OptionalObsoleteFiles.inc so they will
63 be removed during a clean upgrade.
66 The ixgbe tunables now match their sysctl counterparts, for example:
67 hw.ixgbe.enable_aim => hw.ix.enable_aim
68 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
71 The NFSv4.1 server committed by r269398 changes the internal
72 function call interfaces used between the NFS and krpc modules.
73 As such, __FreeBSD_version was bumped.
76 The default unbound configuration has been modified to address
77 issues with reverse lookups on networks that use private
78 address ranges. If you use the local_unbound service, run
79 "service local_unbound setup" as root to regenerate your
80 configuration, then "service local_unbound reload" to load the
84 It is no longer necessary to include the dwarf version in your DEBUG
85 options in your kernel config file. The bug that required it to be
86 placed in the config file has bene fixed. DEBUG should now just
87 contain -g. The build system will automatically update things
88 to do the right thing.
91 Several ABI breaking changes were merged to CTL and new iSCSI code.
92 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
93 iscsictl need to be rebuilt to work with a new kernel.
96 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
97 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
98 which differs from the behaviour controlled by this knob.)
101 On i386 and amd64 systems, the onifconsole flag is now set by default
102 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
103 as a login TTY if it is set in the bootloader as an active kernel
104 console. No changes in behavior should result otherwise. To revert to
105 the previous behavior, set ttyu0 to "off" in /etc/ttys.
108 Clang and llvm have been upgraded to 3.4.1 release.
111 Clang and llvm have been upgraded to 3.4 release.
114 If a Makefile in a tests/ directory was auto-generating a Kyuafile
115 instead of providing an explicit one, this would prevent such
116 Makefile from providing its own Kyuafile in the future during
117 NO_CLEAN builds. This has been fixed in the Makefiles but manual
118 intervention is needed to clean an objdir if you use NO_CLEAN:
119 # find /usr/obj -name Kyuafile | xargs rm -f
122 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
123 capability mode support. Please note that enabling the feature in
124 kernel is still highly recommended.
127 OpenSSH is now built with sandbox support, and will use sandbox as
128 the default privilege separation method. This requires Capsicum
129 capability mode support in kernel.
132 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
133 been deprecated and will not be part of FreeBSD 11.0 and later
134 releases. If you use this driver, please consider switching to
135 the nfe(4) driver instead.
141 The behavior of gss_pseudo_random() for the krb5 mechanism
142 has changed, for applications requesting a longer random string
143 than produced by the underlying enctype's pseudo-random() function.
144 In particular, the random string produced from a session key of
145 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
146 be different at the 17th octet and later, after this change.
147 The counter used in the PRF+ construction is now encoded as a
148 big-endian integer in accordance with RFC 4402.
149 __FreeBSD_version is bumped to 1000701.
152 The WITHOUT_ATF build knob has been removed and its functionality
153 has been subsumed into the more generic WITHOUT_TESTS. If you were
154 using the former to disable the build of the ATF libraries, you
155 should change your settings to use the latter.
158 The default version of mtree is nmtree which is obtained from
159 NetBSD. The output is generally the same, but may vary
160 slightly. If you found you need identical output adding
161 "-F freebsd9" to the command line should do the trick. For the
162 time being, the old mtree is available as fmtree.
165 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
166 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
167 1.1.4_8 and verify bsdyml not linked in, before running "make
169 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
171 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
174 The rc.d/jail script has been updated to support jail(8)
175 configuration file. The "jail_<jname>_*" rc.conf(5) variables
176 for per-jail configuration are automatically converted to
177 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
178 This is transparently backward compatible. See below about some
179 incompatibilities and rc.conf(5) manual page for more details.
181 These variables are now deprecated in favor of jail(8) configuration
182 file. One can use "rc.d/jail config <jname>" command to generate
183 a jail(8) configuration file in /var/run/jail.<jname>.conf without
184 running the jail(8) utility. The default pathname of the
185 configuration file is /etc/jail.conf and can be specified by
186 using $jail_conf or $jail_<jname>_conf variables.
188 Please note that jail_devfs_ruleset accepts an integer at
189 this moment. Please consider to rewrite the ruleset name
193 BIND has been removed from the base system. If all you need
194 is a local resolver, simply enable and start the local_unbound
195 service instead. Otherwise, several versions of BIND are
196 available in the ports tree. The dns/bind99 port is one example.
198 With this change, nslookup(1) and dig(1) are no longer in the base
199 system. Users should instead use host(1) and drill(1) which are
200 in the base system. Alternatively, nslookup and dig can
201 be obtained by installing the dns/bind-tools port.
204 With the addition of unbound(8), a new unbound user is now
205 required during installworld. "mergemaster -p" can be used to
206 add the user prior to installworld, as documented in the handbook.
209 OpenSSH is now built with DNSSEC support, and will by default
210 silently trust signed SSHFP records. This can be controlled with
211 the VerifyHostKeyDNS client configuration setting. DNSSEC support
212 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
215 The GNU Compiler Collection and C++ standard library (libstdc++)
216 are no longer built by default on platforms where clang is the system
217 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
221 The PROCDESC kernel option is now part of the GENERIC kernel
222 configuration and is required for the rwhod(8) to work.
223 If you are using custom kernel configuration, you should include
227 The API and ABI related to the Capsicum framework was modified
228 in backward incompatible way. The userland libraries and programs
229 have to be recompiled to work with the new kernel. This includes the
230 following libraries and programs, but the whole buildworld is
231 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
232 kdump, procstat, rwho, rwhod, uniq.
235 AES-NI intrinsic support has been added to gcc. The AES-NI module
236 has been updated to use this support. A new gcc is required to build
237 the aesni module on both i386 and amd64.
240 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
241 Thus "device padlock_rng" and "device rdrand_rng" should be
242 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
245 WITH_ICONV has been split into two feature sets. WITH_ICONV now
246 enables just the iconv* functionality and is now on by default.
247 WITH_LIBICONV_COMPAT enables the libiconv api and link time
248 compatability. Set WITHOUT_ICONV to build the old way.
249 If you have been using WITH_ICONV before, you will very likely
250 need to turn on WITH_LIBICONV_COMPAT.
253 INVARIANTS option now enables DEBUG for code with OpenSolaris and
254 Illumos origin, including ZFS. If you have INVARIANTS in your
255 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
257 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
258 locks if WITNESS option was set. Because that generated a lot of
259 witness(9) reports and all of them were believed to be false
260 positives, this is no longer done. New option OPENSOLARIS_WITNESS
261 can be used to achieve the previous behavior.
264 Timer values in IPv6 data structures now use time_uptime instead
265 of time_second. Although this is not a user-visible functional
266 change, userland utilities which directly use them---ndp(8),
267 rtadvd(8), and rtsold(8) in the base system---need to be updated
271 find -delete can now delete the pathnames given as arguments,
272 instead of only files found below them or if the pathname did
273 not contain any slashes. Formerly, the following error message
276 find: -delete: <path>: relative path potentially not safe
278 Deleting the pathnames given as arguments can be prevented
279 without error messages using -mindepth 1 or by changing
280 directory and passing "." as argument to find. This works in the
281 old as well as the new version of find.
284 Behavior of devfs rules path matching has been changed.
285 Pattern is now always matched against fully qualified devfs
286 path and slash characters must be explicitly matched by
287 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
288 subdirectories must be reviewed.
291 The default ARM ABI has changed to the ARM EABI. The old ABI is
292 incompatible with the ARM EABI and all programs and modules will
293 need to be rebuilt to work with a new kernel.
295 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
297 NOTE: Support for the old ABI will be removed in the future and
298 users are advised to upgrade.
301 pkg_install has been disconnected from the build if you really need it
302 you should add WITH_PKGTOOLS in your src.conf(5).
305 Most of network statistics structures were changed to be able
306 keep 64-bits counters. Thus all tools, that work with networking
307 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
310 Fix targets that run multiple make's to use && rather than ;
311 so that subsequent steps depend on success of previous.
313 NOTE: if building 'universe' with -j* on stable/8 or stable/9
314 it would be better to start the build using bmake, to avoid
315 overloading the machine.
318 Fix a bug that allowed a tracing process (e.g. gdb) to write
319 to a memory-mapped file in the traced process's address space
320 even if neither the traced process nor the tracing process had
321 write access to that file.
324 CVS has been removed from the base system. An exact copy
325 of the code is available from the devel/cvs port.
328 Some people report the following error after the switch to bmake:
330 make: illegal option -- J
331 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
333 *** [buildworld] Error code 2
335 this likely due to an old instance of make in
336 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
337 which src/Makefile will use that blindly, if it exists, so if
338 you see the above error:
340 rm -rf `make -V MAKEPATH`
345 Use bmake by default.
346 Whereas before one could choose to build with bmake via
347 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
348 make. The goal is to remove these knobs for 10-RELEASE.
350 It is worth noting that bmake (like gmake) treats the command
351 line as the unit of failure, rather than statements within the
352 command line. Thus '(cd some/where && dosomething)' is safer
353 than 'cd some/where; dosomething'. The '()' allows consistent
354 behavior in parallel build.
357 Fix a bug that allows NFS clients to issue READDIR on files.
360 The WITHOUT_IDEA option has been removed because
361 the IDEA patent expired.
364 The sysctl which controls TRIM support under ZFS has been renamed
365 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
369 The mergemaster command now uses the default MAKEOBJDIRPREFIX
370 rather than creating it's own in the temporary directory in
371 order allow access to bootstrapped versions of tools such as
372 install and mtree. When upgrading from version of FreeBSD where
373 the install command does not support -l, you will need to
374 install a new mergemaster command if mergemaster -p is required.
375 This can be accomplished with the command (cd src/usr.sbin/mergemaster
379 Legacy ATA stack, disabled and replaced by new CAM-based one since
380 FreeBSD 9.0, completely removed from the sources. Kernel modules
381 atadisk and atapi*, user-level tools atacontrol and burncd are
382 removed. Kernel option `options ATA_CAM` is now permanently enabled
386 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
387 and socketpair(2). Software, in particular Kerberos, may
388 automatically detect and use these during building. The resulting
389 binaries will not work on older kernels.
392 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
393 information, see the respective 20130304 entry).
396 Recent commits to callout(9) changed the size of struct callout,
397 so the KBI is probably heavily disturbed. Also, some functions
398 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
399 by macros. Every kernel module using it won't load, so rebuild
402 The ctl device has been re-enabled in GENERIC for i386 and amd64,
403 but does not initialize by default (because of the new CTL_DISABLE
404 option) to save memory. To re-enable it, remove the CTL_DISABLE
405 option from the kernel config file or set kern.cam.ctl.disable=0
406 in /boot/loader.conf.
409 The ctl device has been disabled in GENERIC for i386 and amd64.
410 This was done due to the extra memory being allocated at system
411 initialisation time by the ctl driver which was only used if
412 a CAM target device was created. This makes a FreeBSD system
413 unusable on 128MB or less of RAM.
416 A new compression method (lz4) has been merged to -HEAD. Please
417 refer to zpool-features(7) for more information.
419 Please refer to the "ZFS notes" section of this file for information
420 on upgrading boot ZFS pools.
423 A BSD-licensed patch(1) variant has been added and is installed
424 as bsdpatch, being the GNU version the default patch.
425 To inverse the logic and use the BSD-licensed one as default,
426 while having the GNU version installed as gnupatch, rebuild
427 and install world with the WITH_BSD_PATCH knob set.
430 Due to the use of the new -l option to install(1) during build
431 and install, you must take care not to directly set the INSTALL
432 make variable in your /etc/make.conf, /etc/src.conf, or on the
433 command line. If you wish to use the -C flag for all installs
434 you may be able to add INSTALL+=-C to /etc/make.conf or
438 The install(1) option -M has changed meaning and now takes an
439 argument that is a file or path to append logs to. In the
440 unlikely event that -M was the last option on the command line
441 and the command line contained at least two files and a target
442 directory the first file will have logs appended to it. The -M
443 option served little practical purpose in the last decade so its
444 use is expected to be extremely rare.
447 After switching to Clang as the default compiler some users of ZFS
448 on i386 systems started to experience stack overflow kernel panics.
449 Please consider using 'options KSTACK_PAGES=4' in such configurations.
452 GEOM_LABEL now mangles label names read from file system metadata.
453 Mangling affect labels containing spaces, non-printable characters,
454 '%' or '"'. Device names in /etc/fstab and other places may need to
458 By default, only the 10 most recent kernel dumps will be saved. To
459 restore the previous behaviour (no limit on the number of kernel dumps
460 stored in the dump directory) add the following line to /etc/rc.conf:
465 With the addition of auditdistd(8), a new auditdistd user is now
466 required during installworld. "mergemaster -p" can be used to
467 add the user prior to installworld, as documented in the handbook.
470 The sin6_scope_id member variable in struct sockaddr_in6 is now
471 filled by the kernel before passing the structure to the userland via
472 sysctl or routing socket. This means the KAME-specific embedded scope
473 id in sin6_addr.s6_addr[2] is always cleared in userland application.
474 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
475 __FreeBSD_version is bumped to 1000025.
478 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
479 This means that the world and kernel will be compiled with clang
480 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
481 and /usr/bin/cpp. To disable this behavior and revert to building
482 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
483 of current may need to bootstrap WITHOUT_CLANG first if the clang
484 build fails (its compatibility window doesn't extend to the 9 stable
488 The IPFIREWALL_FORWARD kernel option has been removed. Its
489 functionality now turned on by default.
492 The ZERO_COPY_SOCKET kernel option has been removed and
493 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
494 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
495 mechanism which is not safe and may result in kernel crashes.
496 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
497 driver supports disposeable external page sized mbuf storage.
498 Proper replacements for both zero-copy mechanisms are under
499 consideration and will eventually lead to complete removal
500 of the two kernel options.
503 The IPv4 network stack has been converted to network byte
504 order. The following modules need to be recompiled together
505 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
506 pf(4), ipfw(4), ng_ipfw(4), stf(4).
509 Support for non-MPSAFE filesystems was removed from VFS. The
510 VFS_VERSION was bumped, all filesystem modules shall be
514 All the non-MPSAFE filesystems have been disconnected from
515 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
516 portalfs, smbfs, xfs.
519 The interface cloning API and ABI has changed. The following
520 modules need to be recompiled together with kernel:
521 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
522 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
523 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
526 The sdhci driver was split in two parts: sdhci (generic SD Host
527 Controller logic) and sdhci_pci (actual hardware driver).
528 No kernel config modifications are required, but if you
529 load sdhc as a module you must switch to sdhci_pci instead.
532 Import the FUSE kernel and userland support into base system.
535 The GNU sort(1) program has been removed since the BSD-licensed
536 sort(1) has been the default for quite some time and no serious
537 problems have been reported. The corresponding WITH_GNU_SORT
541 The pfil(9) API/ABI for AF_INET family has been changed. Packet
542 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
546 The net80211(4) ABI has been changed to allow for improved driver
547 PS-POLL and power-save support. All wireless drivers need to be
548 recompiled to work with the new kernel.
551 The random(4) support for the VIA hardware random number
552 generator (`PADLOCK') is no longer enabled unconditionally.
553 Add the padlock_rng device in the custom kernel config if
554 needed. The GENERIC kernels on i386 and amd64 do include the
555 device, so the change only affects the custom kernel
559 The pf(4) packet filter ABI has been changed. pfctl(8) and
560 snmp_pf module need to be recompiled to work with new kernel.
563 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
564 to -HEAD. Pools that have empty_bpobj in active state can not be
565 imported read-write with ZFS implementations that do not support
566 this feature. For more information read the zpool-features(5)
570 The sparc64 ZFS loader has been changed to no longer try to auto-
571 detect ZFS providers based on diskN aliases but now requires these
572 to be explicitly listed in the OFW boot-device environment variable.
575 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
576 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
577 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
580 The following sysctls and tunables have been renamed for consistency
581 with other variables:
582 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
583 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
586 The sort utility has been replaced with BSD sort. For now, GNU sort
587 is also available as "gnusort" or the default can be set back to
588 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
589 installed as "bsdsort".
592 A new version of ZFS (pool version 5000) has been merged to -HEAD.
593 Starting with this version the old system of ZFS pool versioning
594 is superseded by "feature flags". This concept enables forward
595 compatibility against certain future changes in functionality of ZFS
596 pools. The first read-only compatible "feature flag" for ZFS pools
597 is named "com.delphix:async_destroy". For more information
598 read the new zpool-features(5) manual page.
599 Please refer to the "ZFS notes" section of this file for information
600 on upgrading boot ZFS pools.
603 The malloc(3) implementation embedded in libc now uses sources imported
604 as contrib/jemalloc. The most disruptive API change is to
605 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
606 delete it prior to installworld, and optionally re-create it using the
607 new format after rebooting. See malloc.conf(5) for details
608 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
612 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
613 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
614 now spelled mips. This is to aid compatibility with third-party
615 software that expects this naming scheme in uname(3). Little-endian
616 settings are unchanged. If you are updating a big-endian mips64 machine
617 from before this change, you may need to set MACHINE_ARCH=mips64 in
618 your environment before the new build system will recognize your machine.
621 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
625 Now unix domain sockets behave "as expected" on nullfs(5). Previously
626 nullfs(5) did not pass through all behaviours to the underlying layer,
627 as a result if we bound to a socket on the lower layer we could connect
628 only to the lower path; if we bound to the upper layer we could connect
629 only to the upper path. The new behavior is one can connect to both the
630 lower and the upper paths regardless what layer path one binds to.
633 The getifaddrs upgrade path broken with 20111215 has been restored.
634 If you have upgraded in between 20111215 and 20120209 you need to
635 recompile libc again with your kernel. You still need to recompile
636 world to be able to configure CARP but this restriction already
640 The set_rcvar() function has been removed from /etc/rc.subr. All
641 base and ports rc.d scripts have been updated, so if you have a
642 port installed with a script in /usr/local/etc/rc.d you can either
643 hand-edit the rcvar= line, or reinstall the port.
645 An easy way to handle the mass-update of /etc/rc.d:
646 rm /etc/rc.d/* && mergemaster -i
649 panic(9) now stops other CPUs in the SMP systems, disables interrupts
650 on the current CPU and prevents other threads from running.
651 This behavior can be reverted using the kern.stop_scheduler_on_panic
653 The new behavior can be incompatible with kern.sync_on_panic.
656 The carp(4) facility has been changed significantly. Configuration
657 of the CARP protocol via ifconfig(8) has changed, as well as format
658 of CARP events submitted to devd(8) has changed. See manual pages
659 for more information. The arpbalance feature of carp(4) is currently
660 not supported anymore.
662 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
663 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
664 need to be recompiled.
667 The acpi_wmi(4) status device /dev/wmistat has been renamed to
671 The option VFS_ALLOW_NONMPSAFE option has been added in order to
672 explicitely support non-MPSAFE filesystems.
673 It is on by default for all supported platform at this present
677 The broken amd(4) driver has been replaced with esp(4) in the amd64,
678 i386 and pc98 GENERIC kernel configuration files.
681 sysinstall has been removed
684 The stable/9 branch created in subversion. This corresponds to the
685 RELENG_9 branch in CVS.
688 This commit modifies vfs_register() so that it uses a hash
689 calculation to set vfc_typenum, which is enabled by default.
690 The first time a system is booted after this change, the
691 vfc_typenum values will change for all file systems. The
692 main effect of this is a change to the NFS server file handles
693 for file systems that use vfc_typenum in their fsid, such as ZFS.
694 It will, however, prevent vfc_typenum from changing when file
695 systems are loaded in a different order for subsequent reboots.
696 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
697 until you are ready to remount all NFS clients after a reboot.
700 Bump the shared library version numbers for libraries that
701 do not use symbol versioning, have changed the ABI compared
702 to stable/8 and which shared library version was not bumped.
703 Done as part of 9.0-RELEASE cycle.
706 During the merge of Capsicum features, the fget(9) KPI was modified.
707 This may require the rebuilding of out-of-tree device drivers --
708 issues have been reported specifically with the nVidia device driver.
709 __FreeBSD_version is bumped to 900041.
711 Also, there is a period between 20110811 and 20110814 where the
712 special devices /dev/{stdin,stdout,stderr} did not work correctly.
713 Building world from a kernel during that window may not work.
716 The packet filter (pf) code has been updated to OpenBSD 4.5.
717 You need to update userland tools to be in sync with kernel.
718 This update breaks backward compatibility with earlier pfsync(4)
719 versions. Care must be taken when updating redundant firewall setups.
722 The following sysctls and tunables are retired on x86 platforms:
724 machdep.hlt_logical_cpus
725 The following sysctl is retired:
726 machdep.hyperthreading_allowed
727 The sysctls were supposed to provide a way to dynamically offline and
728 online selected CPUs on x86 platforms, but the implementation has not
729 been reliable especially with SCHED_ULE scheduler.
730 machdep.hyperthreading_allowed tunable is still available to ignore
731 hyperthreading CPUs at OS level.
732 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
733 where X is an APIC ID of a CPU. Be advised, though, that disabling
734 CPUs in non-uniform fashion will result in non-uniform topology and
735 may lead to sub-optimal system performance with SCHED_ULE, which is
739 cpumask_t type is retired and cpuset_t is used in order to describe
743 Changes to ifconfig(8) for dynamic address family detection mandate
744 that you are running a kernel of 20110525 or later. Make sure to
745 follow the update procedure to boot a new kernel before installing
749 Support for sun4v architecture is officially dropped
752 Several KPI breaking changes have been committed to the mii(4) layer,
753 the PHY drivers and consequently some Ethernet drivers using mii(4).
754 This means that miibus.ko and the modules of the affected Ethernet
755 drivers need to be recompiled.
757 Note to kernel developers: Given that the OUI bit reversion problem
758 was fixed as part of these changes all mii(4) commits related to OUIs,
759 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
760 handling, no longer can be merged verbatim to stable/8 and previous
764 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
765 into their kernel configurations along with 'device pci'.
768 The default NFS client is now the new NFS client, so fstype "newnfs"
769 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
770 Although mounts via fstype "nfs" will usually work without userland
771 changes, it is recommended that the mount(8) and mount_nfs(8)
772 commands be rebuilt from sources and that a link to mount_nfs called
773 mount_oldnfs be created. The new client is compiled into the
774 kernel with "options NFSCL" and this is needed for diskless root
775 file systems. The GENERIC kernel configs have been changed to use
776 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
777 To use the regular/old client, you can "mount -t oldnfs ...". For
778 a diskless root file system, you must also include a line like:
780 vfs.root.mountfrom="oldnfs:"
782 in the boot/loader.conf on the root fs on the NFS server to make
783 a diskless root fs use the old client.
786 The GENERIC kernels for all architectures now default to the new
787 CAM-based ATA stack. It means that all legacy ATA drivers were
788 removed and replaced by respective CAM drivers. If you are using
789 ATA device names in /etc/fstab or other places, make sure to update
790 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
791 where 'Y's are the sequential numbers starting from zero for each type
792 in order of detection, unless configured otherwise with tunables,
793 see cam(4)). There will be symbolic links created in /dev/ to map
794 old adX devices to the respective adaY. They should provide basic
795 compatibility for file systems mounting in most cases, but they do
796 not support old user-level APIs and do not have respective providers
797 in GEOM. Consider using updated management tools with new device names.
799 It is possible to load devices ahci, ata, siis and mvs as modules,
800 but option ATA_CAM should remain in kernel configuration to make ata
801 module work as CAM driver supporting legacy ATA controllers. Device ata
802 still can be used in modular fashion (atacore + ...). Modules atadisk
803 and atapi* are not used and won't affect operation in ATA_CAM mode.
804 Note that to use CAM-based ATA kernel should include CAM devices
805 scbus, pass, da (or explicitly ada), cd and optionally others. All of
806 them are parts of the cam module.
808 ataraid(4) functionality is now supported by the RAID GEOM class.
809 To use it you can load geom_raid kernel module and use graid(8) tool
810 for management. Instead of /dev/arX device names, use /dev/raid/rX.
812 No kernel config options or code have been removed, so if a problem
813 arises, please report it and optionally revert to the old ATA stack.
814 In order to do it you can remove from the kernel config:
819 , and instead add back:
820 device atadisk # ATA disk drives
821 device ataraid # ATA RAID drives
822 device atapicd # ATAPI CDROM drives
823 device atapifd # ATAPI floppy drives
824 device atapist # ATAPI tape drives
827 The default NFS server has been changed to the new server, which
828 was referred to as the experimental server. If you need to switch
829 back to the old NFS server, you must now put the "-o" option on
830 both the mountd and nfsd commands. This can be done using the
831 mountd_flags and nfs_server_flags rc.conf variables until an
832 update to the rc scripts is committed, which is coming soon.
835 The GNU Objective-C runtime library (libobjc), and other Objective-C
836 related components have been removed from the base system. If you
837 require an Objective-C library, please use one of the available ports.
840 ath(4) has been split into bus- and device- modules. if_ath contains
841 the HAL, the TX rate control and the network device code. if_ath_pci
842 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
843 contains the AHB glue. Users need to load both if_ath_pci and if_ath
844 in order to use ath on everything else.
846 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
847 need to load if_ath and if_ath_pci for ath(4) operation.
850 As part of the replacement of sysinstall, the process of building
851 release media has changed significantly. For details, please re-read
852 release(7), which has been updated to reflect the new build process.
855 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
856 is the last available version under GPLv2. It brings a number of new
857 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
858 4.1 and SSE 4.2), better support for powerpc64, a number of new
859 directives, and lots of other small improvements. See the ChangeLog
860 file in contrib/binutils for the full details.
863 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
864 compliant, and will now use half of hash for authentication.
865 This will break interoperability with all stacks (including all
866 actual FreeBSD versions) who implement
867 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
869 The only workaround with such peers is to use another HMAC
870 algorithm for IPsec ("phase 2") authentication.
873 Remove the uio_yield prototype and symbol. This function has
874 been misnamed since it was introduced and should not be
875 globally exposed with this name. The equivalent functionality
876 is now available using kern_yield(curthread->td_user_pri).
877 The function remains undocumented.
880 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
881 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
882 for scalar sysctls is defined but disabled. Code that needs
883 UQUAD to pass the type checking that must compile on older
884 systems where the define is not present can check against
885 __FreeBSD_version >= 900030.
887 The system dialog(1) has been replaced with a new version previously
888 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
889 with the previous version, but the libdialog associated with it has
890 a largely incompatible API. As such, the original version of libdialog
891 will be kept temporarily as libodialog, until its base system consumers
892 are replaced or updated. Bump __FreeBSD_version to 900030.
895 If you are trying to run make universe on a -stable system, and you get
896 the following warning:
897 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
898 unknown. config(8) likely too old."
899 or something similar to it, then you must upgrade your -stable system
900 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
901 stable/8) or build the config from the latest stable/8 branch and
902 install it on your system.
904 Prior to this date, building a current universe on 8-stable system from
905 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
906 error in the first kernel build phase. A new config on those old
907 systems will fix that problem for older versions of -current.
910 The TCP stack has been modified to allow Khelp modules to interact with
911 it via helper hook points and store per-connection data in the TCP
912 control block. Bump __FreeBSD_version to 900029. User space tools that
913 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
917 Generic IEEE 802.3 annex 31B full duplex flow control support has been
918 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
919 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
920 to take advantage of it instead of using custom implementations. This
921 means that these drivers now no longer unconditionally advertise
922 support for flow control but only do so if flow control is a selected
923 media option. This was implemented in the generic support that way in
924 order to allow flow control to be switched on and off via ifconfig(8)
925 with the PHY specific default to typically off in order to protect
926 from unwanted effects. Consequently, if you used flow control with
927 one of the above mentioned drivers you now need to explicitly enable
929 ifconfig bge0 media auto mediaopt flowcontrol
931 Along with the above mentioned changes generic support for setting
932 1000baseT master mode also has been added and brgphy(4), ciphy(4),
933 e1000phy(4) as well as ip1000phy(4) have been converted to take
934 advantage of it. This means that these drivers now no longer take the
935 link0 parameter for selecting master mode but the master media option
936 has to be used instead, for example like in the following:
937 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
939 Selection of master mode now is also available with all other PHY
940 drivers supporting 1000baseT.
943 The TCP stack has received a significant update to add support for
944 modularised congestion control and generally improve the clarity of
945 congestion control decisions. Bump __FreeBSD_version to 900025. User
946 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
947 sockstat) need to be recompiled.
950 The man(1) utility has been replaced by a new version that no longer
951 uses /etc/manpath.config. Please consult man.conf(5) for how to
952 migrate local entries to the new format.
955 The copyright strings printed by login(1) and sshd(8) at the time of a
956 new connection have been removed to follow other operating systems and
960 A workaround for a fixed ld bug has been removed in kernel code,
961 so make sure that your system ld is built from sources after
962 revision 210245 from 2010-07-19 (r211583 if building head kernel
963 on stable/8, r211584 for stable/7; both from 2010-08-21).
964 A symptom of incorrect ld version is different addresses for
965 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
968 The $ipv6_prefer variable in rc.conf(5) has been split into
969 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
971 The $ip6addrctl_policy is a variable to choose a pre-defined
972 address selection policy set by ip6addrctl(8). A value
973 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
976 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
977 flag (see an entry of 20090926) is set on an interface with no
978 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
979 security reason. If you want IPv6 link-local address on all
980 interfaces by default, set this to "YES".
982 The old ipv6_prefer="YES" is equivalent to
983 ipv6_activate_all_interfaces="YES" and
984 ip6addrctl_policy="ipv6_prefer".
987 DTrace has grown support for userland tracing. Due to this, DTrace is
988 now i386 and amd64 only.
989 dtruss(1) is now installed by default on those systems and a new
990 kernel module is needed for userland tracing: fasttrap.
991 No changes to your kernel config file are necessary to enable
992 userland tracing, but you might consider adding 'STRIP=' and
993 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
994 to have informative userland stack traces in DTrace (ustack).
997 The acpi_aiboost(4) driver has been removed in favor of the new
998 aibs(4) driver. You should update your kernel configuration file.
1001 BSD grep has been imported to the base system and it is built by
1002 default. It is completely BSD licensed, highly GNU-compatible, uses
1003 less memory than its GNU counterpart and has a small codebase.
1004 However, it is slower than its GNU counterpart, which is mostly
1005 noticeable for larger searches, for smaller ones it is measurable
1006 but not significant. The reason is complex, the most important factor
1007 is that we lack a modern and efficient regex library and GNU
1008 overcomes this by optimizing the searches internally. Future work
1009 on improving the regex performance is planned, for the meantime,
1010 users that need better performance, can build GNU grep instead by
1011 setting the WITH_GNU_GREP knob.
1014 Due to the import of powerpc64 support, all existing powerpc kernel
1015 configuration files must be updated with a machine directive like this:
1016 machine powerpc powerpc
1018 In addition, an updated config(8) is required to build powerpc kernels
1022 A new version of ZFS (version 15) has been merged to -HEAD.
1023 This version uses a python library for the following subcommands:
1024 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1025 For full functionality of these commands the following port must
1026 be installed: sysutils/py-zfs
1029 'vm_page's are now hashed by physical address to an array of mutexes.
1030 Currently this is only used to serialize access to hold_count. Over
1031 time the page queue mutex will be peeled away. This changes the size
1032 of pmap on every architecture. And requires all callers of vm_page_hold
1033 and vm_page_unhold to be updated.
1036 WITH_CTF can now be specified in src.conf (not recommended, there
1037 are some problems with static executables), make.conf (would also
1038 affect ports which do not use GNU make and do not override the
1039 compile targets) or in the kernel config (via "makeoptions
1041 When WITH_CTF was specified there before this was silently ignored,
1042 so make sure that WITH_CTF is not used in places which could lead
1043 to unwanted behavior.
1046 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1047 to allow 32-bit compatibility on non-x86 platforms. All kernel
1048 configurations on amd64 and ia64 platforms using these options must
1049 be modified accordingly.
1052 The utmp user accounting database has been replaced with utmpx,
1053 the user accounting interface standardized by POSIX.
1054 Unfortunately the semantics of utmp and utmpx don't match,
1055 making it practically impossible to support both interfaces.
1056 The user accounting database is used by tools like finger(1),
1057 last(1), talk(1), w(1) and ac(8).
1059 All applications in the base system use utmpx. This means only
1060 local binaries (e.g. from the ports tree) may still use these
1061 utmp database files. These applications must be rebuilt to make
1064 After the system has been upgraded, it is safe to remove the old
1065 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1066 assuming their contents is of no importance anymore. Old wtmp
1067 databases can only be used by last(1) and ac(8) after they have
1068 been converted to the new format using wtmpcvt(1).
1071 Introduce the kernel thread "deadlock resolver" (which can be enabled
1072 via the DEADLKRES option, see NOTES for more details) and the
1073 sleepq_type() function for sleepqueues.
1076 The rc.firewall and rc.firewall6 were unified, and
1077 rc.firewall6 and rc.d/ip6fw were removed.
1078 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1079 variables are obsoleted. Instead, the following new rc
1080 variables are added to rc.d/ipfw:
1082 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1083 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1084 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1086 The meanings correspond to the relevant IPv4 variables.
1092 The default terminal emulation for syscons(4) has been changed
1093 from cons25 to xterm on all platforms except pc98. This means
1094 that the /etc/ttys file needs to be updated to ensure correct
1095 operation of applications on the console.
1097 The terminal emulation style can be toggled per window by using
1098 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1099 options can be used to change the compile-time default back to
1102 To prevent graphical artifacts, make sure the TERM environment
1103 variable is set to match the terminal emulation that is being
1104 performed by syscons(4).
1107 The layout of the structure ieee80211req_scan_result has changed.
1108 Applications that require wireless scan results (e.g. ifconfig(8))
1109 from net80211 need to be recompiled.
1111 Applications such as wpa_supplicant(8) may require a full world
1112 build without using NO_CLEAN in order to get synchronized with the
1116 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1117 There's one kernel module for each firmware. Adding "device iwnfw"
1118 to the kernel configuration file means including all three firmware
1119 images inside the kernel. If you want to include just the one for
1120 your wireless card, use the devices iwn4965fw, iwn5000fw or
1124 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1125 into rc.d/netif. The changes are the following:
1127 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1128 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1129 Note that both variables need the "inet6" keyword at the head.
1131 Do not set $ipv6_network_interfaces manually if you do not
1132 understand what you are doing. It is not needed in most cases.
1134 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1137 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1138 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1140 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1141 all configured interfaces have "inet6 accept_rtadv" in the
1142 $ifconfig_IF_ipv6. These are for backward compatibility.
1144 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1145 functionality of interfaces with no corresponding
1146 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1147 and the default address selection policy of ip6addrctl(8)
1148 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1149 Note that if you want to configure IPv6 functionality on the
1150 disabled interfaces after boot, first you need to clear the flag by
1151 using ifconfig(8) like:
1153 ifconfig em0 inet6 -ifdisabled
1155 If YES, the default address selection policy is set as
1158 The default value of $ipv6_prefer is NO.
1160 4. If your system need to receive Router Advertisement messages,
1161 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1162 scripts automatically invoke rtsol(8) when the interface becomes
1163 UP. The Router Advertisement messages are used for SLAAC
1164 (State-Less Address AutoConfiguration).
1167 802.11s D3.03 support was committed. This is incompatible with the
1168 previous code, which was based on D3.0.
1171 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1172 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1173 control whether accepting Router Advertisement messages or not.
1174 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1175 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1176 The ifconfig(8) utility now supports these flags.
1179 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1180 mount(8) and -a option for df(1) to see them.
1183 The old tunable hw.bus.devctl_disable has been superseded by
1184 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1185 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1189 Remove the option STOP_NMI. The default action is now to use NMI only
1190 for KDB via the newly introduced function stop_cpus_hard() and
1191 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1194 The stable/8 branch created in subversion. This corresponds to the
1195 RELENG_8 branch in CVS.
1198 Bump the shared library version numbers for all libraries that do not
1199 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1200 __FreeBSD_version to 800105.
1203 Due to changes in the implementation of virtual network stack support,
1204 all network-related kernel modules must be recompiled. As this change
1205 breaks the ABI, bump __FreeBSD_version to 800104.
1208 The TOE interface to the TCP syncache has been modified to remove
1209 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1210 The cxgb driver is the only TOE consumer affected by this change, and
1211 needs to be recompiled along with the kernel. As this change breaks
1212 the ABI, bump __FreeBSD_version to 800103.
1215 Padding has been added to struct tcpcb, sackhint and tcpstat in
1216 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1217 maintaining the ABI. However, this change breaks the ABI, so bump
1218 __FreeBSD_version to 800102. User space tools that rely on the size of
1219 any of these structs (e.g. sockstat) need to be recompiled.
1222 The NFS_LEGACYRPC option has been removed along with the old kernel
1223 RPC implementation that this option selected. Kernel configurations
1224 may need to be adjusted.
1227 The network interface device nodes at /dev/net/<interface> have been
1228 removed. All ioctl operations can be performed the normal way using
1229 routing sockets. The kqueue functionality can generally be replaced
1230 with routing sockets.
1233 The documentation from the FreeBSD Documentation Project (Handbook,
1234 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1235 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1238 The ABI of various structures related to the SYSV IPC API have been
1239 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1240 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1244 Layout of struct vnet has changed as routing related variables were
1245 moved to their own Vimage module. Modules need to be recompiled. Bump
1246 __FreeBSD_version to 800099.
1249 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1250 respectively. As long as no more than 16 groups per process are used,
1251 no changes should be visible. When more than 16 groups are used, old
1252 binaries may fail if they call getgroups() or getgrouplist() with
1253 statically sized storage. Recompiling will work around this, but
1254 applications should be modified to use dynamically allocated storage
1255 for group arrays as POSIX.1-2008 does not cap an implementation's
1256 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1258 NFS and portalfs mounts may also be affected as the list of groups is
1259 truncated to 16. Users of NFS who use more than 16 groups, should
1260 take care that negative group permissions are not used on the exported
1261 file systems as they will not be reliable unless a GSSAPI based
1262 authentication method is used.
1265 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1266 option compiles in the support for adaptive spinning for lockmgrs
1267 which want to enable it. The lockinit() function now accepts the flag
1268 LK_ADAPTIVE in order to make the lock object subject to adaptive
1269 spinning when both held in write and read mode.
1272 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1273 changed. User applications that use this ioctl need to be rebuilt.
1276 The layout of struct thread has changed. Kernel and modules need to
1280 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1281 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1284 window(1) has been removed from the base system. It can now be
1285 installed from ports. The port is called misc/window.
1288 The way we are storing and accessing `routing table' entries has
1289 changed. Programs reading the FIB, like netstat, need to be
1293 A new netisr implementation has been added for FreeBSD 8. Network
1294 file system modules, such as igmp, ipdivert, and others, should be
1296 Bump __FreeBSD_version to 800096.
1299 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1303 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1304 Bump __FreeBSD_version to 800094.
1307 Add mnt_xflag field to 'struct mount'. File system modules need to be
1309 Bump __FreeBSD_version to 800093.
1312 The compiling option ADAPTIVE_SX has been retired while it has been
1313 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1314 The KPI for sx_init_flags() changes as accepting flags:
1315 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1316 been introduced in order to handle the reversed logic.
1317 Bump __FreeBSD_version to 800092.
1320 Add support for hierarchical jails. Remove global securelevel.
1321 Bump __FreeBSD_version to 800091.
1324 The layout of struct vnet_net has changed, therefore modules
1326 Bump __FreeBSD_version to 800090.
1329 The newly imported zic(8) produces a new format in the output. Please
1330 run tzsetup(8) to install the newly created data to /etc/localtime.
1333 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1334 hw.usb.* and is now consistent again with previous releases.
1337 802.11 monitor mode support was revised and driver api's were changed.
1338 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1339 of DLT_IEEE802_11. No user-visible data structures were changed but
1340 applications that use DLT_IEEE802_11 may require changes.
1341 Bump __FreeBSD_version to 800088.
1344 The layout of the following structs has changed: sysctl_oid,
1345 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1346 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1347 panics may be experienced. World rebuild is required for
1348 correctly checking networking state from userland.
1349 Bump __FreeBSD_version to 800085.
1352 MLDv2 and Source-Specific Multicast (SSM) have been merged
1353 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1354 The implementation of SSM within FreeBSD's IPv6 stack closely
1355 follows the IPv4 implementation.
1357 For kernel developers:
1359 * The most important changes are that the ip6_output() and
1360 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1361 and this lock has been downgraded to a non-recursive mutex.
1363 * As with the changes to the IPv4 stack to support SSM, filtering
1364 of inbound multicast traffic must now be performed by transport
1365 protocols within the IPv6 stack. This does not apply to TCP and
1366 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1368 * The KPIs used by IPv6 multicast are similar to those used by
1369 the IPv4 stack, with the following differences:
1370 * im6o_mc_filter() is analogous to imo_multicast_filter().
1371 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1372 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1373 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1374 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1375 for MLDv1 have an additional 'timer' argument which is used to
1376 jitter the initial membership report for the solicited-node
1377 multicast membership on-link.
1378 * This is not strictly needed for MLDv2, which already jitters
1379 its report transmissions. However, the 'timer' argument is
1380 preserved in case MLDv1 is active on the interface.
1382 * The KAME linked-list based IPv6 membership implementation has
1383 been refactored to use a vector similar to that used by the IPv4
1385 Code which maintains a list of its own multicast memberships
1386 internally, e.g. carp, has been updated to reflect the new
1389 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1390 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1391 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1392 implementation constraint which needs to be addressed in HEAD.
1394 For application developers:
1396 * The changes are broadly similar to those made for the IPv4
1399 * The use of IPv4 and IPv6 multicast socket options on the same
1400 socket, using mapped addresses, HAS NOT been tested or supported.
1402 * There are a number of issues with the implementation of various
1403 IPv6 multicast APIs which need to be resolved in the API surface
1404 before the implementation is fully compatible with KAME userland
1405 use, and these are mostly to do with interface index treatment.
1407 * The literature available discusses the use of either the delta / ASM
1408 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1409 using setsourcefilter(3)/getsourcefilter(3). For more information
1410 please refer to RFC 3768, 'Socket Interface Extensions for
1411 Multicast Source Filters'.
1413 * Applications which use the published RFC 3678 APIs should be fine.
1415 For systems administrators:
1417 * The mtest(8) utility has been refactored to support IPv6, in
1418 addition to IPv4. Interface addresses are no longer accepted
1419 as arguments, their names must be used instead. The utility
1420 will map the interface name to its first IPv4 address as
1421 returned by getifaddrs(3).
1423 * The ifmcstat(8) utility has also been updated to print the MLDv2
1424 endpoint state and source filter lists via sysctl(3).
1426 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1427 loopback of IPv6 multicast datagrams by default; it defaults to 1
1428 to preserve the existing behaviour. Disabling multicast loopback is
1429 recommended for optimal system performance.
1431 * The IPv6 MROUTING code has been changed to examine this sysctl
1432 instead of attempting to perform a group lookup before looping
1433 back forwarded datagrams.
1435 Bump __FreeBSD_version to 800084.
1438 Implement low-level Bluetooth HCI API.
1439 Bump __FreeBSD_version to 800083.
1442 The layout of struct malloc_type, used by modules to register new
1443 memory allocation types, has changed. Most modules will need to
1444 be rebuilt or panics may be experienced.
1445 Bump __FreeBSD_version to 800081.
1448 Anticipate overflowing inp_flags - add inp_flags2.
1449 This changes most offsets in inpcb, so checking v4 connection
1450 state will require a world rebuild.
1451 Bump __FreeBSD_version to 800080.
1454 Add an llentry to struct route and struct route_in6. Modules
1455 embedding a struct route will need to be recompiled.
1456 Bump __FreeBSD_version to 800079.
1459 The size of rt_metrics_lite and by extension rtentry has changed.
1460 Networking administration apps will need to be recompiled.
1461 The route command now supports show as an alias for get, weighting
1462 of routes, sticky and nostick flags to alter the behavior of stateful
1464 Bump __FreeBSD_version to 800078.
1467 Do not use Giant for kbdmux(4) locking. This is wrong and
1468 apparently causing more problems than it solves. This will
1469 re-open the issue where interrupt handlers may race with
1470 kbdmux(4) in polling mode. Typical symptoms include (but
1471 not limited to) duplicated and/or missing characters when
1472 low level console functions (such as gets) are used while
1473 interrupts are enabled (for example geli password prompt,
1474 mountroot prompt etc.). Disabling kbdmux(4) may help.
1477 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1478 kernel modules referencing any of the above need to be recompiled.
1479 Bump __FreeBSD_version to 800075.
1482 GEOM_PART has become the default partition slicer for storage devices,
1483 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1484 introduces some changes:
1486 MSDOS/EBR: the devices created from MSDOS extended partition entries
1487 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1488 to devices with offset-based names. fstabs may need to be modified.
1490 BSD: the "geometry does not match label" warning is harmless in most
1491 cases but it points to problems in file system misalignment with
1492 disk geometry. The "c" partition is now implicit, covers the whole
1493 top-level drive and cannot be (mis)used by users.
1495 General: Kernel dumps are now not allowed to be written to devices
1496 whose partition types indicate they are meant to be used for file
1497 systems (or, in case of MSDOS partitions, as something else than
1500 Most of these changes date approximately from 200812.
1503 The uscanner(4) driver has been removed from the kernel. This follows
1504 Linux removing theirs in 2.6 and making libusb the default interface
1505 (supported by sane).
1508 The multicast forwarding code has been cleaned up. netstat(1)
1509 only relies on KVM now for printing bandwidth upcall meters.
1510 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1511 ip6_mroute_mod respectively. The config(5) options for statically
1512 compiling this code remain the same, i.e. 'options MROUTING'.
1515 Support for the IFF_NEEDSGIANT network interface flag has been
1516 removed, which means that non-MPSAFE network device drivers are no
1517 longer supported. In particular, if_ar, if_sr, and network device
1518 drivers from the old (legacy) USB stack can no longer be built or
1522 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1523 a bunch of new language catalog files have also been added.
1524 This means that some common libc messages are now localized and
1525 they depend on the LC_MESSAGES environmental variable.
1528 The k8temp(4) driver has been renamed to amdtemp(4) since
1529 support for Family 10 and Family 11 CPU families was added.
1532 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1533 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1535 For kernel developers, the most important changes are that the
1536 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1537 and this lock has been downgraded to a non-recursive mutex.
1539 Transport protocols (UDP, Raw IP) are now responsible for filtering
1540 inbound multicast traffic according to group membership and source
1541 filters. The imo_multicast_filter() KPI exists for this purpose.
1542 Transports which do not use multicast (SCTP, TCP) already reject
1543 multicast by default. Forwarding and receive performance may improve
1544 as a mutex acquisition is no longer needed in the ip_input()
1545 low-level input path. in_addmulti() and in_delmulti() are shimmed
1546 to new KPIs which exist to support SSM in-kernel.
1548 For application developers, it is recommended that loopback of
1549 multicast datagrams be disabled for best performance, as this
1550 will still cause the lock to be taken for each looped-back
1551 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1552 be tuned to 0 to disable loopback by default; it defaults to 1
1553 to preserve the existing behaviour.
1555 For systems administrators, to obtain best performance with
1556 multicast reception and multiple groups, it is always recommended
1557 that a card with a suitably precise hash filter is used. Hash
1558 collisions will still result in the lock being taken within the
1559 transport protocol input path to check group membership.
1561 If deploying FreeBSD in an environment with IGMP snooping switches,
1562 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1563 enabled; this forces 224.0.0.0/24 group membership to be announced
1566 The size of 'struct igmpstat' has changed; netstat needs to be
1567 recompiled to reflect this.
1568 Bump __FreeBSD_version to 800070.
1571 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1572 updated to use it. This requires a buildworld/installworld in order to
1573 update the library and dependencies (usbconfig, etc). Its advisable to
1574 rebuild all ports which uses libusb. More specific directions are given
1575 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1576 libusb are no longer required and can be removed.
1579 A workaround is committed to allow the creation of System V shared
1580 memory segment of size > 2 GB on the 64-bit architectures.
1581 Due to a limitation of the existing ABI, the shm_segsz member
1582 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1583 wrong for large segments. Note that limits must be explicitly
1584 raised to allow such segments to be created.
1587 The layout of struct ifnet has changed, requiring a rebuild of all
1588 network device driver modules.
1591 The /dev handling for the new USB stack has changed, a
1592 buildworld/installworld is required for libusb20.
1595 The new USB2 stack has now been permanently moved in and all kernel and
1596 module names reverted to their previous values (eg, usb, ehci, ohci,
1597 ums, ...). The old usb stack can be compiled in by prefixing the name
1598 with the letter 'o', the old usb modules have been removed.
1599 Updating entry 20090216 for xorg and 20090215 for libmap may still
1603 The rc.conf(5) option if_up_delay has been renamed to
1604 defaultroute_delay to better reflect its purpose. If you have
1605 customized this setting in /etc/rc.conf you need to update it to
1609 xorg 7.4 wants to configure its input devices via hald which does not
1610 yet work with USB2. If the keyboard/mouse does not work in xorg then
1612 Option "AllowEmptyInput" "off"
1613 to your ServerLayout section. This will cause X to use the configured
1614 kbd and mouse sections from your xorg.conf.
1617 The GENERIC kernels for all architectures now default to the new USB2
1618 stack. No kernel config options or code have been removed so if a
1619 problem arises please report it and optionally revert to the old USB
1620 stack. If you are loading USB kernel modules or have a custom kernel
1621 that includes GENERIC then ensure that usb names are also changed over,
1622 eg uftdi -> usb2_serial_ftdi.
1624 Older programs linked against the ports libusb 0.1 need to be
1625 redirected to the new stack's libusb20. /etc/libmap.conf can
1627 # Map old usb library to new one for usb2 stack
1628 libusb-0.1.so.8 libusb20.so.1
1631 All USB ethernet devices now attach as interfaces under the name ueN
1632 (eg. ue0). This is to provide a predictable name as vendors often
1633 change usb chipsets in a product without notice.
1636 The ichsmb(4) driver has been changed to require SMBus slave
1637 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1638 All of the other SMBus controller drivers require left-justified
1639 slave addresses, so this change makes all the drivers provide the
1643 INET6 statistics (struct ip6stat) was updated.
1644 netstat(1) needs to be recompiled.
1647 NTFS has been removed from GENERIC kernel on amd64 to match
1648 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1649 will load ntfs.ko module automatically when NTFS support is
1650 actually needed, unless ntfs.ko is not installed or security
1651 level prohibits loading kernel modules. If either is the case,
1652 "options NTFS" has to be added into kernel config.
1655 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1656 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1657 800061. User space tools that rely on the size of struct tcpcb in
1658 tcp_var.h (e.g. sockstat) need to be recompiled.
1661 ng_tty(4) module updated to match the new TTY subsystem.
1662 Due to API change, user-level applications must be updated.
1663 New API support added to mpd5 CVS and expected to be present
1664 in next mpd5.3 release.
1667 With __FreeBSD_version 800060 the makefs tool is part of
1668 the base system (it was a port).
1671 The afdata and ifnet locks have been changed from mutexes to
1672 rwlocks, network modules will need to be re-compiled.
1675 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1676 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1677 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1678 architecture and 40 bytes on 64-bit architecture. The userland
1679 applications "arp" and "ndp" have been updated accordingly.
1680 The output from "netstat -r" shows only routing entries and
1681 none of the L2 information.
1684 __FreeBSD_version 800057 marks the switchover from the
1685 binary ath hal to source code. Users must add the line:
1687 options AH_SUPPORT_AR5416
1689 to their kernel config files when specifying:
1693 The ath_hal module no longer exists; the code is now compiled
1694 together with the driver in the ath module. It is now
1695 possible to tailor chip support (i.e. reduce the set of chips
1696 and thereby the code size); consult ath_hal(4) for details.
1699 __FreeBSD_version 800054 adds memory barriers to
1700 <machine/atomic.h>, new interfaces to ifnet to facilitate
1701 multiple hardware transmit queues for cards that support
1702 them, and a lock-less ring-buffer implementation to
1703 enable drivers to more efficiently manage queueing of
1707 A new version of ZFS (version 13) has been merged to -HEAD.
1708 This version has zpool attribute "listsnapshots" off by
1709 default, which means "zfs list" does not show snapshots,
1710 and is the same as Solaris behavior.
1713 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1716 The uhci, ohci, ehci and slhci USB Host controller drivers have
1717 been put into separate modules. If you load the usb module
1718 separately through loader.conf you will need to load the
1719 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1720 controller add the following to loader.conf:
1726 The ABI used by the PMC toolset has changed. Please keep
1727 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1731 atapci kernel module now includes only generic PCI ATA
1732 driver. AHCI driver moved to ataahci kernel module.
1733 All vendor-specific code moved into separate kernel modules:
1734 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1735 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1736 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1737 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1740 The TTY subsystem of the kernel has been replaced by a new
1741 implementation, which provides better scalability and an
1742 improved driver model. Most common drivers have been migrated to
1743 the new TTY subsystem, while others have not. The following
1744 drivers have not yet been ported to the new TTY layer:
1747 cy, digi, rc, rp, sio
1753 ng_h4, ng_tty, ppp, sl, snp
1755 Adding these drivers to your kernel configuration file shall
1756 cause compilation to fail.
1759 ntpd has been upgraded to 4.2.4p5.
1762 OpenSSH has been upgraded to 5.1p1.
1764 For many years, FreeBSD's version of OpenSSH preferred DSA
1765 over RSA for host and user authentication keys. With this
1766 upgrade, we've switched to the vendor's default of RSA over
1767 DSA. This may cause upgraded clients to warn about unknown
1768 host keys even for previously known hosts. Users should
1769 follow the usual procedure for verifying host keys before
1770 accepting the RSA key.
1772 This can be circumvented by setting the "HostKeyAlgorithms"
1773 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1776 Please note that the sequence of keys offered for
1777 authentication has been changed as well. You may want to
1778 specify IdentityFile in a different order to revert this
1782 The sio(4) driver has been removed from the i386 and amd64
1783 kernel configuration files. This means uart(4) is now the
1784 default serial port driver on those platforms as well.
1786 To prevent collisions with the sio(4) driver, the uart(4) driver
1787 uses different names for its device nodes. This means the
1788 onboard serial port will now most likely be called "ttyu0"
1789 instead of "ttyd0". You may need to reconfigure applications to
1790 use the new device names.
1792 When using the serial port as a boot console, be sure to update
1793 /boot/device.hints and /etc/ttys before booting the new kernel.
1794 If you forget to do so, you can still manually specify the hints
1795 at the loader prompt:
1797 set hint.uart.0.at="isa"
1798 set hint.uart.0.port="0x3F8"
1799 set hint.uart.0.flags="0x10"
1800 set hint.uart.0.irq="4"
1804 The gpt(8) utility has been removed. Use gpart(8) to partition
1808 The version that Linuxulator emulates was changed from 2.4.2
1809 to 2.6.16. If you experience any problems with Linux binaries
1810 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1811 if it fixes the problem contact emulation mailing list.
1814 ISDN4BSD (I4B) was removed from the src tree. You may need to
1815 update a your kernel configuration and remove relevant entries.
1818 I have checked in code to support multiple routing tables.
1819 See the man pages setfib(1) and setfib(2).
1820 This is a hopefully backwards compatible version,
1821 but to make use of it you need to compile your kernel
1822 with options ROUTETABLES=2 (or more up to 16).
1825 The 802.11 wireless support was redone to enable multi-bss
1826 operation on devices that are capable. The underlying device
1827 is no longer used directly but instead wlanX devices are
1828 cloned with ifconfig. This requires changes to rc.conf files.
1829 For example, change:
1830 ifconfig_ath0="WPA DHCP"
1833 ifconfig_wlan0="WPA DHCP"
1834 see rc.conf(5) for more details. In addition, mergemaster of
1835 /etc/rc.d is highly recommended. Simultaneous update of userland
1836 and kernel wouldn't hurt either.
1838 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1839 modules were merged into the base wlan module. All references
1840 to these modules (e.g. in kernel config files) must be removed.
1843 psm(4) has gained write(2) support in native operation level.
1844 Arbitrary commands can be written to /dev/psm%d and status can
1845 be read back from it. Therefore, an application is responsible
1846 for status validation and error recovery. It is a no-op in
1847 other operation levels.
1850 Support for KSE threading has been removed from the kernel. To
1851 run legacy applications linked against KSE libmap.conf may
1852 be used. The following libmap.conf may be used to ensure
1853 compatibility with any prior release:
1855 libpthread.so.1 libthr.so.1
1856 libpthread.so.2 libthr.so.2
1857 libkse.so.3 libthr.so.3
1860 The layout of struct vmspace has changed. This affects libkvm
1861 and any executables that link against libkvm and use the
1862 kvm_getprocs() function. In particular, but not exclusively,
1863 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1864 The effects are minimal, but it's advisable to upgrade world
1868 The latest em driver no longer has support in it for the
1869 82575 adapter, this is now moved to the igb driver. The
1870 split was done to make new features that are incompatible
1871 with older hardware easier to do.
1874 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1875 likewise the kernel option is now GEOM_LINUX_LVM.
1878 The default NFS mount mode has changed from UDP to TCP for
1879 increased reliability. If you rely on (insecurely) NFS
1880 mounting across a firewall you may need to update your
1884 Belatedly note the addition of m_collapse for compacting
1888 The fts(3) structures have been changed to use adequate
1889 integer types for their members and so to be able to cope
1890 with huge file trees. The old fts(3) ABI is preserved
1891 through symbol versioning in libc, so third-party binaries
1892 using fts(3) should still work, although they will not take
1893 advantage of the extended types. At the same time, some
1894 third-party software might fail to build after this change
1895 due to unportable assumptions made in its source code about
1896 fts(3) structure members. Such software should be fixed
1897 by its vendor or, in the worst case, in the ports tree.
1898 FreeBSD_version 800015 marks this change for the unlikely
1899 case that a portable fix is impossible.
1902 To upgrade to -current after this date, you must be running
1903 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1904 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1907 The ADAPTIVE_GIANT kernel option has been retired because its
1908 functionality is the default now.
1911 The AT keyboard emulation of sunkbd(4) has been turned on
1912 by default. In order to make the special symbols of the Sun
1913 keyboards driven by sunkbd(4) work under X these now have
1914 to be configured the same way as Sun USB keyboards driven
1915 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1917 Option "XkbLayout" "us"
1918 Option "XkbRules" "xorg"
1919 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1922 It has been decided that it is desirable to provide ABI
1923 backwards compatibility to the FreeBSD 4/5/6 versions of the
1924 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1925 broken with the introduction of PCI domain support (see the
1926 20070930 entry). Unfortunately, this required the ABI of
1927 PCIOCGETCONF to be broken again in order to be able to
1928 provide backwards compatibility to the old version of that
1929 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1930 again. As for prominent ports this affects neither pciutils
1931 nor xorg-server this time, the hal port needs to be rebuilt
1935 The misnamed kthread_create() and friends have been renamed
1936 to kproc_create() etc. Many of the callers already
1937 used kproc_start()..
1938 I will return kthread_create() and friends in a while
1939 with implementations that actually create threads, not procs.
1940 Renaming corresponds with version 800002.
1949 Avoid using make -j when upgrading. While generally safe, there are
1950 sometimes problems using -j to upgrade. If your upgrade fails with
1951 -j, please try again without -j. From time to time in the past there
1952 have been problems using -j with buildworld and/or installworld. This
1953 is especially true when upgrading between "distant" versions (eg one
1954 that cross a major release boundary or several minor releases, or when
1955 several months have passed on the -current branch).
1957 Sometimes, obscure build problems are the result of environment
1958 poisoning. This can happen because the make utility reads its
1959 environment when searching for values for global variables. To run
1960 your build attempts in an "environmental clean room", prefix all make
1961 commands with 'env -i '. See the env(1) manual page for more details.
1963 When upgrading from one major version to another it is generally best
1964 to upgrade to the latest code in the currently installed branch first,
1965 then do an upgrade to the new branch. This is the best-tested upgrade
1966 path, and has the highest probability of being successful. Please try
1967 this approach before reporting problems with a major version upgrade.
1969 When upgrading a live system, having a root shell around before
1970 installing anything can help undo problems. Not having a root shell
1971 around can lead to problems if pam has changed too much from your
1972 starting point to allow continued authentication after the upgrade.
1976 When upgrading the boot ZFS pool to a new version, always follow
1979 1.) recompile and reinstall the ZFS boot loader and boot block
1980 (this is part of "make buildworld" and "make installworld")
1982 2.) update the ZFS boot block on your boot drive
1984 The following example updates the ZFS boot block on the first
1985 partition (freebsd-boot) of a GPT partitioned drive ad0:
1986 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1988 Non-boot pools do not need these updates.
1992 If you are updating from a prior version of FreeBSD (even one just
1993 a few days old), you should follow this procedure. It is the most
1994 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1996 make kernel-toolchain
1997 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1998 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2000 To test a kernel once
2001 ---------------------
2002 If you just want to boot a kernel once (because you are not sure
2003 if it works, or if you want to boot a known bad kernel to provide
2004 debugging information) run
2005 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2006 nextboot -k testkernel
2008 To just build a kernel when you know that it won't mess you up
2009 --------------------------------------------------------------
2010 This assumes you are already running a CURRENT system. Replace
2011 ${arch} with the architecture of your machine (e.g. "i386",
2012 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2014 cd src/sys/${arch}/conf
2015 config KERNEL_NAME_HERE
2016 cd ../compile/KERNEL_NAME_HERE
2021 If this fails, go to the "To build a kernel" section.
2023 To rebuild everything and install it on the current system.
2024 -----------------------------------------------------------
2025 # Note: sometimes if you are running current you gotta do more than
2026 # is listed here if you are upgrading from a really old current.
2028 <make sure you have good level 0 dumps>
2030 make kernel KERNCONF=YOUR_KERNEL_HERE
2032 <reboot in single user> [3]
2039 To cross-install current onto a separate partition
2040 --------------------------------------------------
2041 # In this approach we use a separate partition to hold
2042 # current's root, 'usr', and 'var' directories. A partition
2043 # holding "/", "/usr" and "/var" should be about 2GB in
2046 <make sure you have good level 0 dumps>
2049 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2050 <maybe newfs current's root partition>
2051 <mount current's root partition on directory ${CURRENT_ROOT}>
2052 make installworld DESTDIR=${CURRENT_ROOT}
2053 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2054 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2055 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2056 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2057 <reboot into current>
2058 <do a "native" rebuild/install as described in the previous section>
2059 <maybe install compatibility libraries from ports/misc/compat*>
2063 To upgrade in-place from stable to current
2064 ----------------------------------------------
2065 <make sure you have good level 0 dumps>
2067 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2069 <reboot in single user> [3]
2076 Make sure that you've read the UPDATING file to understand the
2077 tweaks to various things you need. At this point in the life
2078 cycle of current, things change often and you are on your own
2079 to cope. The defaults can also change, so please read ALL of
2080 the UPDATING entries.
2082 Also, if you are tracking -current, you must be subscribed to
2083 freebsd-current@freebsd.org. Make sure that before you update
2084 your sources that you have read and understood all the recent
2085 messages there. If in doubt, please track -stable which has
2086 much fewer pitfalls.
2088 [1] If you have third party modules, such as vmware, you
2089 should disable them at this point so they don't crash your
2092 [3] From the bootblocks, boot -s, and then do
2097 adjkerntz -i # if CMOS is wall time
2098 Also, when doing a major release upgrade, it is required that
2099 you boot into single user mode to do the installworld.
2101 [4] Note: This step is non-optional. Failure to do this step
2102 can result in a significant reduction in the functionality of the
2103 system. Attempting to do it by hand is not recommended and those
2104 that pursue this avenue should read this file carefully, as well
2105 as the archives of freebsd-current and freebsd-hackers mailing lists
2106 for potential gotchas. The -U option is also useful to consider.
2107 See mergemaster(8) for more information.
2109 [5] Usually this step is a noop. However, from time to time
2110 you may need to do this if you get unknown user in the following
2111 step. It never hurts to do it all the time. You may need to
2112 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2113 install) after the buildworld before this step if you last updated
2114 from current before 20130425 or from -stable before 20130430.
2116 [6] This only deletes old files and directories. Old libraries
2117 can be deleted by "make delete-old-libs", but you have to make
2118 sure that no program is using those libraries anymore.
2120 [8] In order to have a kernel that can run the 4.x binaries needed to
2121 do an installworld, you must include the COMPAT_FREEBSD4 option in
2122 your kernel. Failure to do so may leave you with a system that is
2123 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2124 required to run the 5.x binaries on more recent kernels. And so on
2125 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2127 Make sure that you merge any new devices from GENERIC since the
2128 last time you updated your kernel config file.
2130 [9] When checking out sources, you must include the -P flag to have
2131 cvs prune empty directories.
2133 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2134 "?=" instead of the "=" assignment operator, so that buildworld can
2135 override the CPUTYPE if it needs to.
2137 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2138 not on the command line, or in /etc/make.conf. buildworld will
2139 warn if it is improperly defined.
2142 This file contains a list, in reverse chronological order, of major
2143 breakages in tracking -current. It is not guaranteed to be a complete
2144 list of such breakages, and only contains entries since October 10, 2007.
2145 If you need to see UPDATING entries from before that date, you will need
2146 to fetch an UPDATING file from an older FreeBSD release.
2148 Copyright information:
2150 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2152 Redistribution, publication, translation and use, with or without
2153 modification, in full or in part, in any form or format of this
2154 document are permitted without further permission from the author.
2156 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2157 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2158 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2159 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2160 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2161 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2162 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2163 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2164 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2165 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2166 POSSIBILITY OF SUCH DAMAGE.
2168 Contact Warner Losh if you have any questions about your use of