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 NTP has been upgraded to 4.2.8p4.
23 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
24 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
25 and devel/kyua to version 0.20+ and adjust any calling code to work
26 with Kyuafile and kyua.
29 The polarity of Pulse Per Second (PPS) capture events with the
30 uart(4) driver has been corrected. Prior to this change the PPS
31 "assert" event corresponded to the trailing edge of a positive PPS
32 pulse and the "clear" event was the leading edge of the next pulse.
34 As the width of a PPS pulse in a typical GPS receiver is on the
35 order of 1 millisecond, most users will not notice any significant
36 difference with this change.
38 Anyone who has compensated for the historical polarity reversal by
39 configuring a negative offset equal to the pulse width will need to
40 remove that workaround.
43 From legacy ata(4) driver was removed support for SATA controllers
44 supported by more functional drivers ahci(4), siis(4) and mvs(4).
45 Kernel modules ataahci and ataadaptec were removed completely,
46 replaced by ahci and mvs modules respectively.
52 As ZFS requires more kernel stack pages than is the default on some
53 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
54 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
56 Please consider using 'options KSTACK_PAGES=X' where X is greater
57 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
60 The default Unbound configuration now enables remote control
61 using a local socket. Users who have already enabled the
62 local_unbound service should regenerate their configuration
63 by running "service local_unbound setup" as root.
66 An additional fix for the issue described in the 20150614 sendmail
67 entry below has been been committed in revision 284786.
70 The fix for the issue described in the 20150614 sendmail entry
71 below has been been committed in revision 284485. The work
72 around described in that entry is no longer needed unless the
73 default setting is overridden by a confDH_PARAMETERS configuration
74 setting of '5' or pointing to a 512 bit DH parameter file.
77 The import of openssl to address the FreeBSD-SA-15:10.openssl
78 security advisory includes a change which rejects handshakes
79 with DH parameters below 768 bits. sendmail releases prior
80 to 8.15.2 (not yet released), defaulted to a 512 bit
81 DH parameter setting for client connections. To work around
82 this interoperability, sendmail can be configured to use a
83 2048 bit DH parameter by:
85 1. Edit /etc/mail/`hostname`.mc
86 2. If a setting for confDH_PARAMETERS does not exist or
87 exists and is set to a string beginning with '5',
89 3. If a setting for confDH_PARAMETERS exists and is set to
90 a file path, create a new file with:
91 openssl dhparam -out /path/to/file 2048
92 4. Rebuild the .cf file:
93 cd /etc/mail/; make; make install
95 cd /etc/mail/; make restart
97 A sendmail patch is coming, at which time this file will be
101 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
102 defined in symlink(7); previously symlinks were silently ignored.
105 The const qualifier has been removed from iconv(3) to comply with
106 POSIX. The ports tree is aware of this from r384038 onwards.
109 At svn r275807, The default linux compat kernel ABI has been adjusted
110 to 2.6.18 in support of the linux-c6 compat ports infrastructure
111 update. If you wish to continue using the linux-f10 compat ports,
112 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
113 encouraged to update their linux-compat packages to linux-c6 during
114 their next update cycle.
116 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
119 pjdfstest has been integrated into kyua as an opt-in test suite.
120 Please see share/doc/pjdfstest/README for a more details on how to
127 The ofwfb driver, used to provide a graphics console on PowerPC when
128 using vt(4), no longer allows mmap() of all of physical memory. This
129 will prevent Xorg on PowerPC with some ATI graphics cards from
130 initializing properly unless x11-servers/xorg-server is updated to
134 The libatf-c and libatf-c++ major versions were downgraded to 0 and
135 1 respectively to match the upstream numbers. They were out of
136 sync because, when they were originally added to FreeBSD, the
137 upstream versions were not respected. These libraries are private
138 and not yet built by default, so renumbering them should be a
139 non-issue. However, unclean source trees will yield broken test
140 programs once the operator executes "make delete-old-libs" after a
143 Additionally, the atf-sh binary was made private by moving it into
144 /usr/libexec/. Already-built shell test programs will keep the
145 path to the old binary so they will break after "make delete-old"
148 If you are using WITH_TESTS=yes (not the default), wipe the object
149 tree and rebuild from scratch to prevent spurious test failures.
150 This is only needed once: the misnumbered libraries and misplaced
151 binaries have been added to OptionalObsoleteFiles.inc so they will
152 be removed during a clean upgrade.
155 The ixgbe tunables now match their sysctl counterparts, for example:
156 hw.ixgbe.enable_aim => hw.ix.enable_aim
157 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
160 The NFSv4.1 server committed by r269398 changes the internal
161 function call interfaces used between the NFS and krpc modules.
162 As such, __FreeBSD_version was bumped.
165 The default unbound configuration has been modified to address
166 issues with reverse lookups on networks that use private
167 address ranges. If you use the local_unbound service, run
168 "service local_unbound setup" as root to regenerate your
169 configuration, then "service local_unbound reload" to load the
173 It is no longer necessary to include the dwarf version in your DEBUG
174 options in your kernel config file. The bug that required it to be
175 placed in the config file has bene fixed. DEBUG should now just
176 contain -g. The build system will automatically update things
177 to do the right thing.
180 Several ABI breaking changes were merged to CTL and new iSCSI code.
181 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
182 iscsictl need to be rebuilt to work with a new kernel.
185 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
186 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
187 which differs from the behaviour controlled by this knob.)
190 On i386 and amd64 systems, the onifconsole flag is now set by default
191 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
192 as a login TTY if it is set in the bootloader as an active kernel
193 console. No changes in behavior should result otherwise. To revert to
194 the previous behavior, set ttyu0 to "off" in /etc/ttys.
197 Clang and llvm have been upgraded to 3.4.1 release.
200 Clang and llvm have been upgraded to 3.4 release.
203 If a Makefile in a tests/ directory was auto-generating a Kyuafile
204 instead of providing an explicit one, this would prevent such
205 Makefile from providing its own Kyuafile in the future during
206 NO_CLEAN builds. This has been fixed in the Makefiles but manual
207 intervention is needed to clean an objdir if you use NO_CLEAN:
208 # find /usr/obj -name Kyuafile | xargs rm -f
211 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
212 capability mode support. Please note that enabling the feature in
213 kernel is still highly recommended.
216 OpenSSH is now built with sandbox support, and will use sandbox as
217 the default privilege separation method. This requires Capsicum
218 capability mode support in kernel.
221 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
222 been deprecated and will not be part of FreeBSD 11.0 and later
223 releases. If you use this driver, please consider switching to
224 the nfe(4) driver instead.
230 The behavior of gss_pseudo_random() for the krb5 mechanism
231 has changed, for applications requesting a longer random string
232 than produced by the underlying enctype's pseudo-random() function.
233 In particular, the random string produced from a session key of
234 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
235 be different at the 17th octet and later, after this change.
236 The counter used in the PRF+ construction is now encoded as a
237 big-endian integer in accordance with RFC 4402.
238 __FreeBSD_version is bumped to 1000701.
241 The WITHOUT_ATF build knob has been removed and its functionality
242 has been subsumed into the more generic WITHOUT_TESTS. If you were
243 using the former to disable the build of the ATF libraries, you
244 should change your settings to use the latter.
247 The default version of mtree is nmtree which is obtained from
248 NetBSD. The output is generally the same, but may vary
249 slightly. If you found you need identical output adding
250 "-F freebsd9" to the command line should do the trick. For the
251 time being, the old mtree is available as fmtree.
254 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
255 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
256 1.1.4_8 and verify bsdyml not linked in, before running "make
258 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
260 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
263 The rc.d/jail script has been updated to support jail(8)
264 configuration file. The "jail_<jname>_*" rc.conf(5) variables
265 for per-jail configuration are automatically converted to
266 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
267 This is transparently backward compatible. See below about some
268 incompatibilities and rc.conf(5) manual page for more details.
270 These variables are now deprecated in favor of jail(8) configuration
271 file. One can use "rc.d/jail config <jname>" command to generate
272 a jail(8) configuration file in /var/run/jail.<jname>.conf without
273 running the jail(8) utility. The default pathname of the
274 configuration file is /etc/jail.conf and can be specified by
275 using $jail_conf or $jail_<jname>_conf variables.
277 Please note that jail_devfs_ruleset accepts an integer at
278 this moment. Please consider to rewrite the ruleset name
282 BIND has been removed from the base system. If all you need
283 is a local resolver, simply enable and start the local_unbound
284 service instead. Otherwise, several versions of BIND are
285 available in the ports tree. The dns/bind99 port is one example.
287 With this change, nslookup(1) and dig(1) are no longer in the base
288 system. Users should instead use host(1) and drill(1) which are
289 in the base system. Alternatively, nslookup and dig can
290 be obtained by installing the dns/bind-tools port.
293 With the addition of unbound(8), a new unbound user is now
294 required during installworld. "mergemaster -p" can be used to
295 add the user prior to installworld, as documented in the handbook.
298 OpenSSH is now built with DNSSEC support, and will by default
299 silently trust signed SSHFP records. This can be controlled with
300 the VerifyHostKeyDNS client configuration setting. DNSSEC support
301 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
304 The GNU Compiler Collection and C++ standard library (libstdc++)
305 are no longer built by default on platforms where clang is the system
306 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
310 The PROCDESC kernel option is now part of the GENERIC kernel
311 configuration and is required for the rwhod(8) to work.
312 If you are using custom kernel configuration, you should include
316 The API and ABI related to the Capsicum framework was modified
317 in backward incompatible way. The userland libraries and programs
318 have to be recompiled to work with the new kernel. This includes the
319 following libraries and programs, but the whole buildworld is
320 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
321 kdump, procstat, rwho, rwhod, uniq.
324 AES-NI intrinsic support has been added to gcc. The AES-NI module
325 has been updated to use this support. A new gcc is required to build
326 the aesni module on both i386 and amd64.
329 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
330 Thus "device padlock_rng" and "device rdrand_rng" should be
331 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
334 WITH_ICONV has been split into two feature sets. WITH_ICONV now
335 enables just the iconv* functionality and is now on by default.
336 WITH_LIBICONV_COMPAT enables the libiconv api and link time
337 compatability. Set WITHOUT_ICONV to build the old way.
338 If you have been using WITH_ICONV before, you will very likely
339 need to turn on WITH_LIBICONV_COMPAT.
342 INVARIANTS option now enables DEBUG for code with OpenSolaris and
343 Illumos origin, including ZFS. If you have INVARIANTS in your
344 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
346 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
347 locks if WITNESS option was set. Because that generated a lot of
348 witness(9) reports and all of them were believed to be false
349 positives, this is no longer done. New option OPENSOLARIS_WITNESS
350 can be used to achieve the previous behavior.
353 Timer values in IPv6 data structures now use time_uptime instead
354 of time_second. Although this is not a user-visible functional
355 change, userland utilities which directly use them---ndp(8),
356 rtadvd(8), and rtsold(8) in the base system---need to be updated
360 find -delete can now delete the pathnames given as arguments,
361 instead of only files found below them or if the pathname did
362 not contain any slashes. Formerly, the following error message
365 find: -delete: <path>: relative path potentially not safe
367 Deleting the pathnames given as arguments can be prevented
368 without error messages using -mindepth 1 or by changing
369 directory and passing "." as argument to find. This works in the
370 old as well as the new version of find.
373 Behavior of devfs rules path matching has been changed.
374 Pattern is now always matched against fully qualified devfs
375 path and slash characters must be explicitly matched by
376 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
377 subdirectories must be reviewed.
380 The default ARM ABI has changed to the ARM EABI. The old ABI is
381 incompatible with the ARM EABI and all programs and modules will
382 need to be rebuilt to work with a new kernel.
384 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
386 NOTE: Support for the old ABI will be removed in the future and
387 users are advised to upgrade.
390 pkg_install has been disconnected from the build if you really need it
391 you should add WITH_PKGTOOLS in your src.conf(5).
394 Most of network statistics structures were changed to be able
395 keep 64-bits counters. Thus all tools, that work with networking
396 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
399 Fix targets that run multiple make's to use && rather than ;
400 so that subsequent steps depend on success of previous.
402 NOTE: if building 'universe' with -j* on stable/8 or stable/9
403 it would be better to start the build using bmake, to avoid
404 overloading the machine.
407 Fix a bug that allowed a tracing process (e.g. gdb) to write
408 to a memory-mapped file in the traced process's address space
409 even if neither the traced process nor the tracing process had
410 write access to that file.
413 CVS has been removed from the base system. An exact copy
414 of the code is available from the devel/cvs port.
417 Some people report the following error after the switch to bmake:
419 make: illegal option -- J
420 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
422 *** [buildworld] Error code 2
424 this likely due to an old instance of make in
425 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
426 which src/Makefile will use that blindly, if it exists, so if
427 you see the above error:
429 rm -rf `make -V MAKEPATH`
434 Use bmake by default.
435 Whereas before one could choose to build with bmake via
436 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
437 make. The goal is to remove these knobs for 10-RELEASE.
439 It is worth noting that bmake (like gmake) treats the command
440 line as the unit of failure, rather than statements within the
441 command line. Thus '(cd some/where && dosomething)' is safer
442 than 'cd some/where; dosomething'. The '()' allows consistent
443 behavior in parallel build.
446 Fix a bug that allows NFS clients to issue READDIR on files.
449 The WITHOUT_IDEA option has been removed because
450 the IDEA patent expired.
453 The sysctl which controls TRIM support under ZFS has been renamed
454 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
458 The mergemaster command now uses the default MAKEOBJDIRPREFIX
459 rather than creating it's own in the temporary directory in
460 order allow access to bootstrapped versions of tools such as
461 install and mtree. When upgrading from version of FreeBSD where
462 the install command does not support -l, you will need to
463 install a new mergemaster command if mergemaster -p is required.
464 This can be accomplished with the command (cd src/usr.sbin/mergemaster
468 Legacy ATA stack, disabled and replaced by new CAM-based one since
469 FreeBSD 9.0, completely removed from the sources. Kernel modules
470 atadisk and atapi*, user-level tools atacontrol and burncd are
471 removed. Kernel option `options ATA_CAM` is now permanently enabled
475 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
476 and socketpair(2). Software, in particular Kerberos, may
477 automatically detect and use these during building. The resulting
478 binaries will not work on older kernels.
481 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
482 information, see the respective 20130304 entry).
485 Recent commits to callout(9) changed the size of struct callout,
486 so the KBI is probably heavily disturbed. Also, some functions
487 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
488 by macros. Every kernel module using it won't load, so rebuild
491 The ctl device has been re-enabled in GENERIC for i386 and amd64,
492 but does not initialize by default (because of the new CTL_DISABLE
493 option) to save memory. To re-enable it, remove the CTL_DISABLE
494 option from the kernel config file or set kern.cam.ctl.disable=0
495 in /boot/loader.conf.
498 The ctl device has been disabled in GENERIC for i386 and amd64.
499 This was done due to the extra memory being allocated at system
500 initialisation time by the ctl driver which was only used if
501 a CAM target device was created. This makes a FreeBSD system
502 unusable on 128MB or less of RAM.
505 A new compression method (lz4) has been merged to -HEAD. Please
506 refer to zpool-features(7) for more information.
508 Please refer to the "ZFS notes" section of this file for information
509 on upgrading boot ZFS pools.
512 A BSD-licensed patch(1) variant has been added and is installed
513 as bsdpatch, being the GNU version the default patch.
514 To inverse the logic and use the BSD-licensed one as default,
515 while having the GNU version installed as gnupatch, rebuild
516 and install world with the WITH_BSD_PATCH knob set.
519 Due to the use of the new -l option to install(1) during build
520 and install, you must take care not to directly set the INSTALL
521 make variable in your /etc/make.conf, /etc/src.conf, or on the
522 command line. If you wish to use the -C flag for all installs
523 you may be able to add INSTALL+=-C to /etc/make.conf or
527 The install(1) option -M has changed meaning and now takes an
528 argument that is a file or path to append logs to. In the
529 unlikely event that -M was the last option on the command line
530 and the command line contained at least two files and a target
531 directory the first file will have logs appended to it. The -M
532 option served little practical purpose in the last decade so its
533 use is expected to be extremely rare.
536 After switching to Clang as the default compiler some users of ZFS
537 on i386 systems started to experience stack overflow kernel panics.
538 Please consider using 'options KSTACK_PAGES=4' in such configurations.
541 GEOM_LABEL now mangles label names read from file system metadata.
542 Mangling affect labels containing spaces, non-printable characters,
543 '%' or '"'. Device names in /etc/fstab and other places may need to
547 By default, only the 10 most recent kernel dumps will be saved. To
548 restore the previous behaviour (no limit on the number of kernel dumps
549 stored in the dump directory) add the following line to /etc/rc.conf:
554 With the addition of auditdistd(8), a new auditdistd user is now
555 required during installworld. "mergemaster -p" can be used to
556 add the user prior to installworld, as documented in the handbook.
559 The sin6_scope_id member variable in struct sockaddr_in6 is now
560 filled by the kernel before passing the structure to the userland via
561 sysctl or routing socket. This means the KAME-specific embedded scope
562 id in sin6_addr.s6_addr[2] is always cleared in userland application.
563 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
564 __FreeBSD_version is bumped to 1000025.
567 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
568 This means that the world and kernel will be compiled with clang
569 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
570 and /usr/bin/cpp. To disable this behavior and revert to building
571 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
572 of current may need to bootstrap WITHOUT_CLANG first if the clang
573 build fails (its compatibility window doesn't extend to the 9 stable
577 The IPFIREWALL_FORWARD kernel option has been removed. Its
578 functionality now turned on by default.
581 The ZERO_COPY_SOCKET kernel option has been removed and
582 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
583 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
584 mechanism which is not safe and may result in kernel crashes.
585 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
586 driver supports disposeable external page sized mbuf storage.
587 Proper replacements for both zero-copy mechanisms are under
588 consideration and will eventually lead to complete removal
589 of the two kernel options.
592 The IPv4 network stack has been converted to network byte
593 order. The following modules need to be recompiled together
594 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
595 pf(4), ipfw(4), ng_ipfw(4), stf(4).
598 Support for non-MPSAFE filesystems was removed from VFS. The
599 VFS_VERSION was bumped, all filesystem modules shall be
603 All the non-MPSAFE filesystems have been disconnected from
604 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
605 portalfs, smbfs, xfs.
608 The interface cloning API and ABI has changed. The following
609 modules need to be recompiled together with kernel:
610 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
611 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
612 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
615 The sdhci driver was split in two parts: sdhci (generic SD Host
616 Controller logic) and sdhci_pci (actual hardware driver).
617 No kernel config modifications are required, but if you
618 load sdhc as a module you must switch to sdhci_pci instead.
621 Import the FUSE kernel and userland support into base system.
624 The GNU sort(1) program has been removed since the BSD-licensed
625 sort(1) has been the default for quite some time and no serious
626 problems have been reported. The corresponding WITH_GNU_SORT
630 The pfil(9) API/ABI for AF_INET family has been changed. Packet
631 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
635 The net80211(4) ABI has been changed to allow for improved driver
636 PS-POLL and power-save support. All wireless drivers need to be
637 recompiled to work with the new kernel.
640 The random(4) support for the VIA hardware random number
641 generator (`PADLOCK') is no longer enabled unconditionally.
642 Add the padlock_rng device in the custom kernel config if
643 needed. The GENERIC kernels on i386 and amd64 do include the
644 device, so the change only affects the custom kernel
648 The pf(4) packet filter ABI has been changed. pfctl(8) and
649 snmp_pf module need to be recompiled to work with new kernel.
652 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
653 to -HEAD. Pools that have empty_bpobj in active state can not be
654 imported read-write with ZFS implementations that do not support
655 this feature. For more information read the zpool-features(5)
659 The sparc64 ZFS loader has been changed to no longer try to auto-
660 detect ZFS providers based on diskN aliases but now requires these
661 to be explicitly listed in the OFW boot-device environment variable.
664 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
665 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
666 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
669 The following sysctls and tunables have been renamed for consistency
670 with other variables:
671 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
672 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
675 The sort utility has been replaced with BSD sort. For now, GNU sort
676 is also available as "gnusort" or the default can be set back to
677 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
678 installed as "bsdsort".
681 A new version of ZFS (pool version 5000) has been merged to -HEAD.
682 Starting with this version the old system of ZFS pool versioning
683 is superseded by "feature flags". This concept enables forward
684 compatibility against certain future changes in functionality of ZFS
685 pools. The first read-only compatible "feature flag" for ZFS pools
686 is named "com.delphix:async_destroy". For more information
687 read the new zpool-features(5) manual page.
688 Please refer to the "ZFS notes" section of this file for information
689 on upgrading boot ZFS pools.
692 The malloc(3) implementation embedded in libc now uses sources imported
693 as contrib/jemalloc. The most disruptive API change is to
694 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
695 delete it prior to installworld, and optionally re-create it using the
696 new format after rebooting. See malloc.conf(5) for details
697 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
701 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
702 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
703 now spelled mips. This is to aid compatibility with third-party
704 software that expects this naming scheme in uname(3). Little-endian
705 settings are unchanged. If you are updating a big-endian mips64 machine
706 from before this change, you may need to set MACHINE_ARCH=mips64 in
707 your environment before the new build system will recognize your machine.
710 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
714 Now unix domain sockets behave "as expected" on nullfs(5). Previously
715 nullfs(5) did not pass through all behaviours to the underlying layer,
716 as a result if we bound to a socket on the lower layer we could connect
717 only to the lower path; if we bound to the upper layer we could connect
718 only to the upper path. The new behavior is one can connect to both the
719 lower and the upper paths regardless what layer path one binds to.
722 The getifaddrs upgrade path broken with 20111215 has been restored.
723 If you have upgraded in between 20111215 and 20120209 you need to
724 recompile libc again with your kernel. You still need to recompile
725 world to be able to configure CARP but this restriction already
729 The set_rcvar() function has been removed from /etc/rc.subr. All
730 base and ports rc.d scripts have been updated, so if you have a
731 port installed with a script in /usr/local/etc/rc.d you can either
732 hand-edit the rcvar= line, or reinstall the port.
734 An easy way to handle the mass-update of /etc/rc.d:
735 rm /etc/rc.d/* && mergemaster -i
738 panic(9) now stops other CPUs in the SMP systems, disables interrupts
739 on the current CPU and prevents other threads from running.
740 This behavior can be reverted using the kern.stop_scheduler_on_panic
742 The new behavior can be incompatible with kern.sync_on_panic.
745 The carp(4) facility has been changed significantly. Configuration
746 of the CARP protocol via ifconfig(8) has changed, as well as format
747 of CARP events submitted to devd(8) has changed. See manual pages
748 for more information. The arpbalance feature of carp(4) is currently
749 not supported anymore.
751 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
752 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
753 need to be recompiled.
756 The acpi_wmi(4) status device /dev/wmistat has been renamed to
760 The option VFS_ALLOW_NONMPSAFE option has been added in order to
761 explicitely support non-MPSAFE filesystems.
762 It is on by default for all supported platform at this present
766 The broken amd(4) driver has been replaced with esp(4) in the amd64,
767 i386 and pc98 GENERIC kernel configuration files.
770 sysinstall has been removed
773 The stable/9 branch created in subversion. This corresponds to the
774 RELENG_9 branch in CVS.
777 This commit modifies vfs_register() so that it uses a hash
778 calculation to set vfc_typenum, which is enabled by default.
779 The first time a system is booted after this change, the
780 vfc_typenum values will change for all file systems. The
781 main effect of this is a change to the NFS server file handles
782 for file systems that use vfc_typenum in their fsid, such as ZFS.
783 It will, however, prevent vfc_typenum from changing when file
784 systems are loaded in a different order for subsequent reboots.
785 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
786 until you are ready to remount all NFS clients after a reboot.
789 Bump the shared library version numbers for libraries that
790 do not use symbol versioning, have changed the ABI compared
791 to stable/8 and which shared library version was not bumped.
792 Done as part of 9.0-RELEASE cycle.
795 During the merge of Capsicum features, the fget(9) KPI was modified.
796 This may require the rebuilding of out-of-tree device drivers --
797 issues have been reported specifically with the nVidia device driver.
798 __FreeBSD_version is bumped to 900041.
800 Also, there is a period between 20110811 and 20110814 where the
801 special devices /dev/{stdin,stdout,stderr} did not work correctly.
802 Building world from a kernel during that window may not work.
805 The packet filter (pf) code has been updated to OpenBSD 4.5.
806 You need to update userland tools to be in sync with kernel.
807 This update breaks backward compatibility with earlier pfsync(4)
808 versions. Care must be taken when updating redundant firewall setups.
811 The following sysctls and tunables are retired on x86 platforms:
813 machdep.hlt_logical_cpus
814 The following sysctl is retired:
815 machdep.hyperthreading_allowed
816 The sysctls were supposed to provide a way to dynamically offline and
817 online selected CPUs on x86 platforms, but the implementation has not
818 been reliable especially with SCHED_ULE scheduler.
819 machdep.hyperthreading_allowed tunable is still available to ignore
820 hyperthreading CPUs at OS level.
821 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
822 where X is an APIC ID of a CPU. Be advised, though, that disabling
823 CPUs in non-uniform fashion will result in non-uniform topology and
824 may lead to sub-optimal system performance with SCHED_ULE, which is
828 cpumask_t type is retired and cpuset_t is used in order to describe
832 Changes to ifconfig(8) for dynamic address family detection mandate
833 that you are running a kernel of 20110525 or later. Make sure to
834 follow the update procedure to boot a new kernel before installing
838 Support for sun4v architecture is officially dropped
841 Several KPI breaking changes have been committed to the mii(4) layer,
842 the PHY drivers and consequently some Ethernet drivers using mii(4).
843 This means that miibus.ko and the modules of the affected Ethernet
844 drivers need to be recompiled.
846 Note to kernel developers: Given that the OUI bit reversion problem
847 was fixed as part of these changes all mii(4) commits related to OUIs,
848 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
849 handling, no longer can be merged verbatim to stable/8 and previous
853 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
854 into their kernel configurations along with 'device pci'.
857 The default NFS client is now the new NFS client, so fstype "newnfs"
858 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
859 Although mounts via fstype "nfs" will usually work without userland
860 changes, it is recommended that the mount(8) and mount_nfs(8)
861 commands be rebuilt from sources and that a link to mount_nfs called
862 mount_oldnfs be created. The new client is compiled into the
863 kernel with "options NFSCL" and this is needed for diskless root
864 file systems. The GENERIC kernel configs have been changed to use
865 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
866 To use the regular/old client, you can "mount -t oldnfs ...". For
867 a diskless root file system, you must also include a line like:
869 vfs.root.mountfrom="oldnfs:"
871 in the boot/loader.conf on the root fs on the NFS server to make
872 a diskless root fs use the old client.
875 The GENERIC kernels for all architectures now default to the new
876 CAM-based ATA stack. It means that all legacy ATA drivers were
877 removed and replaced by respective CAM drivers. If you are using
878 ATA device names in /etc/fstab or other places, make sure to update
879 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
880 where 'Y's are the sequential numbers starting from zero for each type
881 in order of detection, unless configured otherwise with tunables,
882 see cam(4)). There will be symbolic links created in /dev/ to map
883 old adX devices to the respective adaY. They should provide basic
884 compatibility for file systems mounting in most cases, but they do
885 not support old user-level APIs and do not have respective providers
886 in GEOM. Consider using updated management tools with new device names.
888 It is possible to load devices ahci, ata, siis and mvs as modules,
889 but option ATA_CAM should remain in kernel configuration to make ata
890 module work as CAM driver supporting legacy ATA controllers. Device ata
891 still can be used in modular fashion (atacore + ...). Modules atadisk
892 and atapi* are not used and won't affect operation in ATA_CAM mode.
893 Note that to use CAM-based ATA kernel should include CAM devices
894 scbus, pass, da (or explicitly ada), cd and optionally others. All of
895 them are parts of the cam module.
897 ataraid(4) functionality is now supported by the RAID GEOM class.
898 To use it you can load geom_raid kernel module and use graid(8) tool
899 for management. Instead of /dev/arX device names, use /dev/raid/rX.
901 No kernel config options or code have been removed, so if a problem
902 arises, please report it and optionally revert to the old ATA stack.
903 In order to do it you can remove from the kernel config:
908 , and instead add back:
909 device atadisk # ATA disk drives
910 device ataraid # ATA RAID drives
911 device atapicd # ATAPI CDROM drives
912 device atapifd # ATAPI floppy drives
913 device atapist # ATAPI tape drives
916 The default NFS server has been changed to the new server, which
917 was referred to as the experimental server. If you need to switch
918 back to the old NFS server, you must now put the "-o" option on
919 both the mountd and nfsd commands. This can be done using the
920 mountd_flags and nfs_server_flags rc.conf variables until an
921 update to the rc scripts is committed, which is coming soon.
924 The GNU Objective-C runtime library (libobjc), and other Objective-C
925 related components have been removed from the base system. If you
926 require an Objective-C library, please use one of the available ports.
929 ath(4) has been split into bus- and device- modules. if_ath contains
930 the HAL, the TX rate control and the network device code. if_ath_pci
931 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
932 contains the AHB glue. Users need to load both if_ath_pci and if_ath
933 in order to use ath on everything else.
935 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
936 need to load if_ath and if_ath_pci for ath(4) operation.
939 As part of the replacement of sysinstall, the process of building
940 release media has changed significantly. For details, please re-read
941 release(7), which has been updated to reflect the new build process.
944 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
945 is the last available version under GPLv2. It brings a number of new
946 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
947 4.1 and SSE 4.2), better support for powerpc64, a number of new
948 directives, and lots of other small improvements. See the ChangeLog
949 file in contrib/binutils for the full details.
952 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
953 compliant, and will now use half of hash for authentication.
954 This will break interoperability with all stacks (including all
955 actual FreeBSD versions) who implement
956 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
958 The only workaround with such peers is to use another HMAC
959 algorithm for IPsec ("phase 2") authentication.
962 Remove the uio_yield prototype and symbol. This function has
963 been misnamed since it was introduced and should not be
964 globally exposed with this name. The equivalent functionality
965 is now available using kern_yield(curthread->td_user_pri).
966 The function remains undocumented.
969 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
970 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
971 for scalar sysctls is defined but disabled. Code that needs
972 UQUAD to pass the type checking that must compile on older
973 systems where the define is not present can check against
974 __FreeBSD_version >= 900030.
976 The system dialog(1) has been replaced with a new version previously
977 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
978 with the previous version, but the libdialog associated with it has
979 a largely incompatible API. As such, the original version of libdialog
980 will be kept temporarily as libodialog, until its base system consumers
981 are replaced or updated. Bump __FreeBSD_version to 900030.
984 If you are trying to run make universe on a -stable system, and you get
985 the following warning:
986 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
987 unknown. config(8) likely too old."
988 or something similar to it, then you must upgrade your -stable system
989 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
990 stable/8) or build the config from the latest stable/8 branch and
991 install it on your system.
993 Prior to this date, building a current universe on 8-stable system from
994 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
995 error in the first kernel build phase. A new config on those old
996 systems will fix that problem for older versions of -current.
999 The TCP stack has been modified to allow Khelp modules to interact with
1000 it via helper hook points and store per-connection data in the TCP
1001 control block. Bump __FreeBSD_version to 900029. User space tools that
1002 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1006 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1007 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1008 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1009 to take advantage of it instead of using custom implementations. This
1010 means that these drivers now no longer unconditionally advertise
1011 support for flow control but only do so if flow control is a selected
1012 media option. This was implemented in the generic support that way in
1013 order to allow flow control to be switched on and off via ifconfig(8)
1014 with the PHY specific default to typically off in order to protect
1015 from unwanted effects. Consequently, if you used flow control with
1016 one of the above mentioned drivers you now need to explicitly enable
1017 it, for example via:
1018 ifconfig bge0 media auto mediaopt flowcontrol
1020 Along with the above mentioned changes generic support for setting
1021 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1022 e1000phy(4) as well as ip1000phy(4) have been converted to take
1023 advantage of it. This means that these drivers now no longer take the
1024 link0 parameter for selecting master mode but the master media option
1025 has to be used instead, for example like in the following:
1026 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1028 Selection of master mode now is also available with all other PHY
1029 drivers supporting 1000baseT.
1032 The TCP stack has received a significant update to add support for
1033 modularised congestion control and generally improve the clarity of
1034 congestion control decisions. Bump __FreeBSD_version to 900025. User
1035 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1036 sockstat) need to be recompiled.
1039 The man(1) utility has been replaced by a new version that no longer
1040 uses /etc/manpath.config. Please consult man.conf(5) for how to
1041 migrate local entries to the new format.
1044 The copyright strings printed by login(1) and sshd(8) at the time of a
1045 new connection have been removed to follow other operating systems and
1049 A workaround for a fixed ld bug has been removed in kernel code,
1050 so make sure that your system ld is built from sources after
1051 revision 210245 from 2010-07-19 (r211583 if building head kernel
1052 on stable/8, r211584 for stable/7; both from 2010-08-21).
1053 A symptom of incorrect ld version is different addresses for
1054 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1057 The $ipv6_prefer variable in rc.conf(5) has been split into
1058 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1060 The $ip6addrctl_policy is a variable to choose a pre-defined
1061 address selection policy set by ip6addrctl(8). A value
1062 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1065 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1066 flag (see an entry of 20090926) is set on an interface with no
1067 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1068 security reason. If you want IPv6 link-local address on all
1069 interfaces by default, set this to "YES".
1071 The old ipv6_prefer="YES" is equivalent to
1072 ipv6_activate_all_interfaces="YES" and
1073 ip6addrctl_policy="ipv6_prefer".
1076 DTrace has grown support for userland tracing. Due to this, DTrace is
1077 now i386 and amd64 only.
1078 dtruss(1) is now installed by default on those systems and a new
1079 kernel module is needed for userland tracing: fasttrap.
1080 No changes to your kernel config file are necessary to enable
1081 userland tracing, but you might consider adding 'STRIP=' and
1082 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1083 to have informative userland stack traces in DTrace (ustack).
1086 The acpi_aiboost(4) driver has been removed in favor of the new
1087 aibs(4) driver. You should update your kernel configuration file.
1090 BSD grep has been imported to the base system and it is built by
1091 default. It is completely BSD licensed, highly GNU-compatible, uses
1092 less memory than its GNU counterpart and has a small codebase.
1093 However, it is slower than its GNU counterpart, which is mostly
1094 noticeable for larger searches, for smaller ones it is measurable
1095 but not significant. The reason is complex, the most important factor
1096 is that we lack a modern and efficient regex library and GNU
1097 overcomes this by optimizing the searches internally. Future work
1098 on improving the regex performance is planned, for the meantime,
1099 users that need better performance, can build GNU grep instead by
1100 setting the WITH_GNU_GREP knob.
1103 Due to the import of powerpc64 support, all existing powerpc kernel
1104 configuration files must be updated with a machine directive like this:
1105 machine powerpc powerpc
1107 In addition, an updated config(8) is required to build powerpc kernels
1111 A new version of ZFS (version 15) has been merged to -HEAD.
1112 This version uses a python library for the following subcommands:
1113 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1114 For full functionality of these commands the following port must
1115 be installed: sysutils/py-zfs
1118 'vm_page's are now hashed by physical address to an array of mutexes.
1119 Currently this is only used to serialize access to hold_count. Over
1120 time the page queue mutex will be peeled away. This changes the size
1121 of pmap on every architecture. And requires all callers of vm_page_hold
1122 and vm_page_unhold to be updated.
1125 WITH_CTF can now be specified in src.conf (not recommended, there
1126 are some problems with static executables), make.conf (would also
1127 affect ports which do not use GNU make and do not override the
1128 compile targets) or in the kernel config (via "makeoptions
1130 When WITH_CTF was specified there before this was silently ignored,
1131 so make sure that WITH_CTF is not used in places which could lead
1132 to unwanted behavior.
1135 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1136 to allow 32-bit compatibility on non-x86 platforms. All kernel
1137 configurations on amd64 and ia64 platforms using these options must
1138 be modified accordingly.
1141 The utmp user accounting database has been replaced with utmpx,
1142 the user accounting interface standardized by POSIX.
1143 Unfortunately the semantics of utmp and utmpx don't match,
1144 making it practically impossible to support both interfaces.
1145 The user accounting database is used by tools like finger(1),
1146 last(1), talk(1), w(1) and ac(8).
1148 All applications in the base system use utmpx. This means only
1149 local binaries (e.g. from the ports tree) may still use these
1150 utmp database files. These applications must be rebuilt to make
1153 After the system has been upgraded, it is safe to remove the old
1154 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1155 assuming their contents is of no importance anymore. Old wtmp
1156 databases can only be used by last(1) and ac(8) after they have
1157 been converted to the new format using wtmpcvt(1).
1160 Introduce the kernel thread "deadlock resolver" (which can be enabled
1161 via the DEADLKRES option, see NOTES for more details) and the
1162 sleepq_type() function for sleepqueues.
1165 The rc.firewall and rc.firewall6 were unified, and
1166 rc.firewall6 and rc.d/ip6fw were removed.
1167 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1168 variables are obsoleted. Instead, the following new rc
1169 variables are added to rc.d/ipfw:
1171 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1172 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1173 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1175 The meanings correspond to the relevant IPv4 variables.
1181 The default terminal emulation for syscons(4) has been changed
1182 from cons25 to xterm on all platforms except pc98. This means
1183 that the /etc/ttys file needs to be updated to ensure correct
1184 operation of applications on the console.
1186 The terminal emulation style can be toggled per window by using
1187 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1188 options can be used to change the compile-time default back to
1191 To prevent graphical artifacts, make sure the TERM environment
1192 variable is set to match the terminal emulation that is being
1193 performed by syscons(4).
1196 The layout of the structure ieee80211req_scan_result has changed.
1197 Applications that require wireless scan results (e.g. ifconfig(8))
1198 from net80211 need to be recompiled.
1200 Applications such as wpa_supplicant(8) may require a full world
1201 build without using NO_CLEAN in order to get synchronized with the
1205 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1206 There's one kernel module for each firmware. Adding "device iwnfw"
1207 to the kernel configuration file means including all three firmware
1208 images inside the kernel. If you want to include just the one for
1209 your wireless card, use the devices iwn4965fw, iwn5000fw or
1213 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1214 into rc.d/netif. The changes are the following:
1216 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1217 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1218 Note that both variables need the "inet6" keyword at the head.
1220 Do not set $ipv6_network_interfaces manually if you do not
1221 understand what you are doing. It is not needed in most cases.
1223 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1226 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1227 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1229 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1230 all configured interfaces have "inet6 accept_rtadv" in the
1231 $ifconfig_IF_ipv6. These are for backward compatibility.
1233 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1234 functionality of interfaces with no corresponding
1235 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1236 and the default address selection policy of ip6addrctl(8)
1237 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1238 Note that if you want to configure IPv6 functionality on the
1239 disabled interfaces after boot, first you need to clear the flag by
1240 using ifconfig(8) like:
1242 ifconfig em0 inet6 -ifdisabled
1244 If YES, the default address selection policy is set as
1247 The default value of $ipv6_prefer is NO.
1249 4. If your system need to receive Router Advertisement messages,
1250 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1251 scripts automatically invoke rtsol(8) when the interface becomes
1252 UP. The Router Advertisement messages are used for SLAAC
1253 (State-Less Address AutoConfiguration).
1256 802.11s D3.03 support was committed. This is incompatible with the
1257 previous code, which was based on D3.0.
1260 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1261 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1262 control whether accepting Router Advertisement messages or not.
1263 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1264 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1265 The ifconfig(8) utility now supports these flags.
1268 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1269 mount(8) and -a option for df(1) to see them.
1272 The old tunable hw.bus.devctl_disable has been superseded by
1273 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1274 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1278 Remove the option STOP_NMI. The default action is now to use NMI only
1279 for KDB via the newly introduced function stop_cpus_hard() and
1280 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1283 The stable/8 branch created in subversion. This corresponds to the
1284 RELENG_8 branch in CVS.
1287 Bump the shared library version numbers for all libraries that do not
1288 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1289 __FreeBSD_version to 800105.
1292 Due to changes in the implementation of virtual network stack support,
1293 all network-related kernel modules must be recompiled. As this change
1294 breaks the ABI, bump __FreeBSD_version to 800104.
1297 The TOE interface to the TCP syncache has been modified to remove
1298 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1299 The cxgb driver is the only TOE consumer affected by this change, and
1300 needs to be recompiled along with the kernel. As this change breaks
1301 the ABI, bump __FreeBSD_version to 800103.
1304 Padding has been added to struct tcpcb, sackhint and tcpstat in
1305 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1306 maintaining the ABI. However, this change breaks the ABI, so bump
1307 __FreeBSD_version to 800102. User space tools that rely on the size of
1308 any of these structs (e.g. sockstat) need to be recompiled.
1311 The NFS_LEGACYRPC option has been removed along with the old kernel
1312 RPC implementation that this option selected. Kernel configurations
1313 may need to be adjusted.
1316 The network interface device nodes at /dev/net/<interface> have been
1317 removed. All ioctl operations can be performed the normal way using
1318 routing sockets. The kqueue functionality can generally be replaced
1319 with routing sockets.
1322 The documentation from the FreeBSD Documentation Project (Handbook,
1323 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1324 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1327 The ABI of various structures related to the SYSV IPC API have been
1328 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1329 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1333 Layout of struct vnet has changed as routing related variables were
1334 moved to their own Vimage module. Modules need to be recompiled. Bump
1335 __FreeBSD_version to 800099.
1338 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1339 respectively. As long as no more than 16 groups per process are used,
1340 no changes should be visible. When more than 16 groups are used, old
1341 binaries may fail if they call getgroups() or getgrouplist() with
1342 statically sized storage. Recompiling will work around this, but
1343 applications should be modified to use dynamically allocated storage
1344 for group arrays as POSIX.1-2008 does not cap an implementation's
1345 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1347 NFS and portalfs mounts may also be affected as the list of groups is
1348 truncated to 16. Users of NFS who use more than 16 groups, should
1349 take care that negative group permissions are not used on the exported
1350 file systems as they will not be reliable unless a GSSAPI based
1351 authentication method is used.
1354 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1355 option compiles in the support for adaptive spinning for lockmgrs
1356 which want to enable it. The lockinit() function now accepts the flag
1357 LK_ADAPTIVE in order to make the lock object subject to adaptive
1358 spinning when both held in write and read mode.
1361 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1362 changed. User applications that use this ioctl need to be rebuilt.
1365 The layout of struct thread has changed. Kernel and modules need to
1369 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1370 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1373 window(1) has been removed from the base system. It can now be
1374 installed from ports. The port is called misc/window.
1377 The way we are storing and accessing `routing table' entries has
1378 changed. Programs reading the FIB, like netstat, need to be
1382 A new netisr implementation has been added for FreeBSD 8. Network
1383 file system modules, such as igmp, ipdivert, and others, should be
1385 Bump __FreeBSD_version to 800096.
1388 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1392 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1393 Bump __FreeBSD_version to 800094.
1396 Add mnt_xflag field to 'struct mount'. File system modules need to be
1398 Bump __FreeBSD_version to 800093.
1401 The compiling option ADAPTIVE_SX has been retired while it has been
1402 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1403 The KPI for sx_init_flags() changes as accepting flags:
1404 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1405 been introduced in order to handle the reversed logic.
1406 Bump __FreeBSD_version to 800092.
1409 Add support for hierarchical jails. Remove global securelevel.
1410 Bump __FreeBSD_version to 800091.
1413 The layout of struct vnet_net has changed, therefore modules
1415 Bump __FreeBSD_version to 800090.
1418 The newly imported zic(8) produces a new format in the output. Please
1419 run tzsetup(8) to install the newly created data to /etc/localtime.
1422 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1423 hw.usb.* and is now consistent again with previous releases.
1426 802.11 monitor mode support was revised and driver api's were changed.
1427 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1428 of DLT_IEEE802_11. No user-visible data structures were changed but
1429 applications that use DLT_IEEE802_11 may require changes.
1430 Bump __FreeBSD_version to 800088.
1433 The layout of the following structs has changed: sysctl_oid,
1434 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1435 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1436 panics may be experienced. World rebuild is required for
1437 correctly checking networking state from userland.
1438 Bump __FreeBSD_version to 800085.
1441 MLDv2 and Source-Specific Multicast (SSM) have been merged
1442 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1443 The implementation of SSM within FreeBSD's IPv6 stack closely
1444 follows the IPv4 implementation.
1446 For kernel developers:
1448 * The most important changes are that the ip6_output() and
1449 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1450 and this lock has been downgraded to a non-recursive mutex.
1452 * As with the changes to the IPv4 stack to support SSM, filtering
1453 of inbound multicast traffic must now be performed by transport
1454 protocols within the IPv6 stack. This does not apply to TCP and
1455 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1457 * The KPIs used by IPv6 multicast are similar to those used by
1458 the IPv4 stack, with the following differences:
1459 * im6o_mc_filter() is analogous to imo_multicast_filter().
1460 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1461 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1462 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1463 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1464 for MLDv1 have an additional 'timer' argument which is used to
1465 jitter the initial membership report for the solicited-node
1466 multicast membership on-link.
1467 * This is not strictly needed for MLDv2, which already jitters
1468 its report transmissions. However, the 'timer' argument is
1469 preserved in case MLDv1 is active on the interface.
1471 * The KAME linked-list based IPv6 membership implementation has
1472 been refactored to use a vector similar to that used by the IPv4
1474 Code which maintains a list of its own multicast memberships
1475 internally, e.g. carp, has been updated to reflect the new
1478 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1479 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1480 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1481 implementation constraint which needs to be addressed in HEAD.
1483 For application developers:
1485 * The changes are broadly similar to those made for the IPv4
1488 * The use of IPv4 and IPv6 multicast socket options on the same
1489 socket, using mapped addresses, HAS NOT been tested or supported.
1491 * There are a number of issues with the implementation of various
1492 IPv6 multicast APIs which need to be resolved in the API surface
1493 before the implementation is fully compatible with KAME userland
1494 use, and these are mostly to do with interface index treatment.
1496 * The literature available discusses the use of either the delta / ASM
1497 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1498 using setsourcefilter(3)/getsourcefilter(3). For more information
1499 please refer to RFC 3768, 'Socket Interface Extensions for
1500 Multicast Source Filters'.
1502 * Applications which use the published RFC 3678 APIs should be fine.
1504 For systems administrators:
1506 * The mtest(8) utility has been refactored to support IPv6, in
1507 addition to IPv4. Interface addresses are no longer accepted
1508 as arguments, their names must be used instead. The utility
1509 will map the interface name to its first IPv4 address as
1510 returned by getifaddrs(3).
1512 * The ifmcstat(8) utility has also been updated to print the MLDv2
1513 endpoint state and source filter lists via sysctl(3).
1515 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1516 loopback of IPv6 multicast datagrams by default; it defaults to 1
1517 to preserve the existing behaviour. Disabling multicast loopback is
1518 recommended for optimal system performance.
1520 * The IPv6 MROUTING code has been changed to examine this sysctl
1521 instead of attempting to perform a group lookup before looping
1522 back forwarded datagrams.
1524 Bump __FreeBSD_version to 800084.
1527 Implement low-level Bluetooth HCI API.
1528 Bump __FreeBSD_version to 800083.
1531 The layout of struct malloc_type, used by modules to register new
1532 memory allocation types, has changed. Most modules will need to
1533 be rebuilt or panics may be experienced.
1534 Bump __FreeBSD_version to 800081.
1537 Anticipate overflowing inp_flags - add inp_flags2.
1538 This changes most offsets in inpcb, so checking v4 connection
1539 state will require a world rebuild.
1540 Bump __FreeBSD_version to 800080.
1543 Add an llentry to struct route and struct route_in6. Modules
1544 embedding a struct route will need to be recompiled.
1545 Bump __FreeBSD_version to 800079.
1548 The size of rt_metrics_lite and by extension rtentry has changed.
1549 Networking administration apps will need to be recompiled.
1550 The route command now supports show as an alias for get, weighting
1551 of routes, sticky and nostick flags to alter the behavior of stateful
1553 Bump __FreeBSD_version to 800078.
1556 Do not use Giant for kbdmux(4) locking. This is wrong and
1557 apparently causing more problems than it solves. This will
1558 re-open the issue where interrupt handlers may race with
1559 kbdmux(4) in polling mode. Typical symptoms include (but
1560 not limited to) duplicated and/or missing characters when
1561 low level console functions (such as gets) are used while
1562 interrupts are enabled (for example geli password prompt,
1563 mountroot prompt etc.). Disabling kbdmux(4) may help.
1566 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1567 kernel modules referencing any of the above need to be recompiled.
1568 Bump __FreeBSD_version to 800075.
1571 GEOM_PART has become the default partition slicer for storage devices,
1572 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1573 introduces some changes:
1575 MSDOS/EBR: the devices created from MSDOS extended partition entries
1576 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1577 to devices with offset-based names. fstabs may need to be modified.
1579 BSD: the "geometry does not match label" warning is harmless in most
1580 cases but it points to problems in file system misalignment with
1581 disk geometry. The "c" partition is now implicit, covers the whole
1582 top-level drive and cannot be (mis)used by users.
1584 General: Kernel dumps are now not allowed to be written to devices
1585 whose partition types indicate they are meant to be used for file
1586 systems (or, in case of MSDOS partitions, as something else than
1589 Most of these changes date approximately from 200812.
1592 The uscanner(4) driver has been removed from the kernel. This follows
1593 Linux removing theirs in 2.6 and making libusb the default interface
1594 (supported by sane).
1597 The multicast forwarding code has been cleaned up. netstat(1)
1598 only relies on KVM now for printing bandwidth upcall meters.
1599 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1600 ip6_mroute_mod respectively. The config(5) options for statically
1601 compiling this code remain the same, i.e. 'options MROUTING'.
1604 Support for the IFF_NEEDSGIANT network interface flag has been
1605 removed, which means that non-MPSAFE network device drivers are no
1606 longer supported. In particular, if_ar, if_sr, and network device
1607 drivers from the old (legacy) USB stack can no longer be built or
1611 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1612 a bunch of new language catalog files have also been added.
1613 This means that some common libc messages are now localized and
1614 they depend on the LC_MESSAGES environmental variable.
1617 The k8temp(4) driver has been renamed to amdtemp(4) since
1618 support for Family 10 and Family 11 CPU families was added.
1621 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1622 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1624 For kernel developers, the most important changes are that the
1625 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1626 and this lock has been downgraded to a non-recursive mutex.
1628 Transport protocols (UDP, Raw IP) are now responsible for filtering
1629 inbound multicast traffic according to group membership and source
1630 filters. The imo_multicast_filter() KPI exists for this purpose.
1631 Transports which do not use multicast (SCTP, TCP) already reject
1632 multicast by default. Forwarding and receive performance may improve
1633 as a mutex acquisition is no longer needed in the ip_input()
1634 low-level input path. in_addmulti() and in_delmulti() are shimmed
1635 to new KPIs which exist to support SSM in-kernel.
1637 For application developers, it is recommended that loopback of
1638 multicast datagrams be disabled for best performance, as this
1639 will still cause the lock to be taken for each looped-back
1640 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1641 be tuned to 0 to disable loopback by default; it defaults to 1
1642 to preserve the existing behaviour.
1644 For systems administrators, to obtain best performance with
1645 multicast reception and multiple groups, it is always recommended
1646 that a card with a suitably precise hash filter is used. Hash
1647 collisions will still result in the lock being taken within the
1648 transport protocol input path to check group membership.
1650 If deploying FreeBSD in an environment with IGMP snooping switches,
1651 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1652 enabled; this forces 224.0.0.0/24 group membership to be announced
1655 The size of 'struct igmpstat' has changed; netstat needs to be
1656 recompiled to reflect this.
1657 Bump __FreeBSD_version to 800070.
1660 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1661 updated to use it. This requires a buildworld/installworld in order to
1662 update the library and dependencies (usbconfig, etc). Its advisable to
1663 rebuild all ports which uses libusb. More specific directions are given
1664 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1665 libusb are no longer required and can be removed.
1668 A workaround is committed to allow the creation of System V shared
1669 memory segment of size > 2 GB on the 64-bit architectures.
1670 Due to a limitation of the existing ABI, the shm_segsz member
1671 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1672 wrong for large segments. Note that limits must be explicitly
1673 raised to allow such segments to be created.
1676 The layout of struct ifnet has changed, requiring a rebuild of all
1677 network device driver modules.
1680 The /dev handling for the new USB stack has changed, a
1681 buildworld/installworld is required for libusb20.
1684 The new USB2 stack has now been permanently moved in and all kernel and
1685 module names reverted to their previous values (eg, usb, ehci, ohci,
1686 ums, ...). The old usb stack can be compiled in by prefixing the name
1687 with the letter 'o', the old usb modules have been removed.
1688 Updating entry 20090216 for xorg and 20090215 for libmap may still
1692 The rc.conf(5) option if_up_delay has been renamed to
1693 defaultroute_delay to better reflect its purpose. If you have
1694 customized this setting in /etc/rc.conf you need to update it to
1698 xorg 7.4 wants to configure its input devices via hald which does not
1699 yet work with USB2. If the keyboard/mouse does not work in xorg then
1701 Option "AllowEmptyInput" "off"
1702 to your ServerLayout section. This will cause X to use the configured
1703 kbd and mouse sections from your xorg.conf.
1706 The GENERIC kernels for all architectures now default to the new USB2
1707 stack. No kernel config options or code have been removed so if a
1708 problem arises please report it and optionally revert to the old USB
1709 stack. If you are loading USB kernel modules or have a custom kernel
1710 that includes GENERIC then ensure that usb names are also changed over,
1711 eg uftdi -> usb2_serial_ftdi.
1713 Older programs linked against the ports libusb 0.1 need to be
1714 redirected to the new stack's libusb20. /etc/libmap.conf can
1716 # Map old usb library to new one for usb2 stack
1717 libusb-0.1.so.8 libusb20.so.1
1720 All USB ethernet devices now attach as interfaces under the name ueN
1721 (eg. ue0). This is to provide a predictable name as vendors often
1722 change usb chipsets in a product without notice.
1725 The ichsmb(4) driver has been changed to require SMBus slave
1726 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1727 All of the other SMBus controller drivers require left-justified
1728 slave addresses, so this change makes all the drivers provide the
1732 INET6 statistics (struct ip6stat) was updated.
1733 netstat(1) needs to be recompiled.
1736 NTFS has been removed from GENERIC kernel on amd64 to match
1737 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1738 will load ntfs.ko module automatically when NTFS support is
1739 actually needed, unless ntfs.ko is not installed or security
1740 level prohibits loading kernel modules. If either is the case,
1741 "options NTFS" has to be added into kernel config.
1744 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1745 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1746 800061. User space tools that rely on the size of struct tcpcb in
1747 tcp_var.h (e.g. sockstat) need to be recompiled.
1750 ng_tty(4) module updated to match the new TTY subsystem.
1751 Due to API change, user-level applications must be updated.
1752 New API support added to mpd5 CVS and expected to be present
1753 in next mpd5.3 release.
1756 With __FreeBSD_version 800060 the makefs tool is part of
1757 the base system (it was a port).
1760 The afdata and ifnet locks have been changed from mutexes to
1761 rwlocks, network modules will need to be re-compiled.
1764 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1765 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1766 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1767 architecture and 40 bytes on 64-bit architecture. The userland
1768 applications "arp" and "ndp" have been updated accordingly.
1769 The output from "netstat -r" shows only routing entries and
1770 none of the L2 information.
1773 __FreeBSD_version 800057 marks the switchover from the
1774 binary ath hal to source code. Users must add the line:
1776 options AH_SUPPORT_AR5416
1778 to their kernel config files when specifying:
1782 The ath_hal module no longer exists; the code is now compiled
1783 together with the driver in the ath module. It is now
1784 possible to tailor chip support (i.e. reduce the set of chips
1785 and thereby the code size); consult ath_hal(4) for details.
1788 __FreeBSD_version 800054 adds memory barriers to
1789 <machine/atomic.h>, new interfaces to ifnet to facilitate
1790 multiple hardware transmit queues for cards that support
1791 them, and a lock-less ring-buffer implementation to
1792 enable drivers to more efficiently manage queueing of
1796 A new version of ZFS (version 13) has been merged to -HEAD.
1797 This version has zpool attribute "listsnapshots" off by
1798 default, which means "zfs list" does not show snapshots,
1799 and is the same as Solaris behavior.
1802 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1805 The uhci, ohci, ehci and slhci USB Host controller drivers have
1806 been put into separate modules. If you load the usb module
1807 separately through loader.conf you will need to load the
1808 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1809 controller add the following to loader.conf:
1815 The ABI used by the PMC toolset has changed. Please keep
1816 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1820 atapci kernel module now includes only generic PCI ATA
1821 driver. AHCI driver moved to ataahci kernel module.
1822 All vendor-specific code moved into separate kernel modules:
1823 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1824 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1825 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1826 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1829 The TTY subsystem of the kernel has been replaced by a new
1830 implementation, which provides better scalability and an
1831 improved driver model. Most common drivers have been migrated to
1832 the new TTY subsystem, while others have not. The following
1833 drivers have not yet been ported to the new TTY layer:
1836 cy, digi, rc, rp, sio
1842 ng_h4, ng_tty, ppp, sl, snp
1844 Adding these drivers to your kernel configuration file shall
1845 cause compilation to fail.
1848 ntpd has been upgraded to 4.2.4p5.
1851 OpenSSH has been upgraded to 5.1p1.
1853 For many years, FreeBSD's version of OpenSSH preferred DSA
1854 over RSA for host and user authentication keys. With this
1855 upgrade, we've switched to the vendor's default of RSA over
1856 DSA. This may cause upgraded clients to warn about unknown
1857 host keys even for previously known hosts. Users should
1858 follow the usual procedure for verifying host keys before
1859 accepting the RSA key.
1861 This can be circumvented by setting the "HostKeyAlgorithms"
1862 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1865 Please note that the sequence of keys offered for
1866 authentication has been changed as well. You may want to
1867 specify IdentityFile in a different order to revert this
1871 The sio(4) driver has been removed from the i386 and amd64
1872 kernel configuration files. This means uart(4) is now the
1873 default serial port driver on those platforms as well.
1875 To prevent collisions with the sio(4) driver, the uart(4) driver
1876 uses different names for its device nodes. This means the
1877 onboard serial port will now most likely be called "ttyu0"
1878 instead of "ttyd0". You may need to reconfigure applications to
1879 use the new device names.
1881 When using the serial port as a boot console, be sure to update
1882 /boot/device.hints and /etc/ttys before booting the new kernel.
1883 If you forget to do so, you can still manually specify the hints
1884 at the loader prompt:
1886 set hint.uart.0.at="isa"
1887 set hint.uart.0.port="0x3F8"
1888 set hint.uart.0.flags="0x10"
1889 set hint.uart.0.irq="4"
1893 The gpt(8) utility has been removed. Use gpart(8) to partition
1897 The version that Linuxulator emulates was changed from 2.4.2
1898 to 2.6.16. If you experience any problems with Linux binaries
1899 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1900 if it fixes the problem contact emulation mailing list.
1903 ISDN4BSD (I4B) was removed from the src tree. You may need to
1904 update a your kernel configuration and remove relevant entries.
1907 I have checked in code to support multiple routing tables.
1908 See the man pages setfib(1) and setfib(2).
1909 This is a hopefully backwards compatible version,
1910 but to make use of it you need to compile your kernel
1911 with options ROUTETABLES=2 (or more up to 16).
1914 The 802.11 wireless support was redone to enable multi-bss
1915 operation on devices that are capable. The underlying device
1916 is no longer used directly but instead wlanX devices are
1917 cloned with ifconfig. This requires changes to rc.conf files.
1918 For example, change:
1919 ifconfig_ath0="WPA DHCP"
1922 ifconfig_wlan0="WPA DHCP"
1923 see rc.conf(5) for more details. In addition, mergemaster of
1924 /etc/rc.d is highly recommended. Simultaneous update of userland
1925 and kernel wouldn't hurt either.
1927 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1928 modules were merged into the base wlan module. All references
1929 to these modules (e.g. in kernel config files) must be removed.
1932 psm(4) has gained write(2) support in native operation level.
1933 Arbitrary commands can be written to /dev/psm%d and status can
1934 be read back from it. Therefore, an application is responsible
1935 for status validation and error recovery. It is a no-op in
1936 other operation levels.
1939 Support for KSE threading has been removed from the kernel. To
1940 run legacy applications linked against KSE libmap.conf may
1941 be used. The following libmap.conf may be used to ensure
1942 compatibility with any prior release:
1944 libpthread.so.1 libthr.so.1
1945 libpthread.so.2 libthr.so.2
1946 libkse.so.3 libthr.so.3
1949 The layout of struct vmspace has changed. This affects libkvm
1950 and any executables that link against libkvm and use the
1951 kvm_getprocs() function. In particular, but not exclusively,
1952 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1953 The effects are minimal, but it's advisable to upgrade world
1957 The latest em driver no longer has support in it for the
1958 82575 adapter, this is now moved to the igb driver. The
1959 split was done to make new features that are incompatible
1960 with older hardware easier to do.
1963 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1964 likewise the kernel option is now GEOM_LINUX_LVM.
1967 The default NFS mount mode has changed from UDP to TCP for
1968 increased reliability. If you rely on (insecurely) NFS
1969 mounting across a firewall you may need to update your
1973 Belatedly note the addition of m_collapse for compacting
1977 The fts(3) structures have been changed to use adequate
1978 integer types for their members and so to be able to cope
1979 with huge file trees. The old fts(3) ABI is preserved
1980 through symbol versioning in libc, so third-party binaries
1981 using fts(3) should still work, although they will not take
1982 advantage of the extended types. At the same time, some
1983 third-party software might fail to build after this change
1984 due to unportable assumptions made in its source code about
1985 fts(3) structure members. Such software should be fixed
1986 by its vendor or, in the worst case, in the ports tree.
1987 FreeBSD_version 800015 marks this change for the unlikely
1988 case that a portable fix is impossible.
1991 To upgrade to -current after this date, you must be running
1992 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1993 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1996 The ADAPTIVE_GIANT kernel option has been retired because its
1997 functionality is the default now.
2000 The AT keyboard emulation of sunkbd(4) has been turned on
2001 by default. In order to make the special symbols of the Sun
2002 keyboards driven by sunkbd(4) work under X these now have
2003 to be configured the same way as Sun USB keyboards driven
2004 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2006 Option "XkbLayout" "us"
2007 Option "XkbRules" "xorg"
2008 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2011 It has been decided that it is desirable to provide ABI
2012 backwards compatibility to the FreeBSD 4/5/6 versions of the
2013 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2014 broken with the introduction of PCI domain support (see the
2015 20070930 entry). Unfortunately, this required the ABI of
2016 PCIOCGETCONF to be broken again in order to be able to
2017 provide backwards compatibility to the old version of that
2018 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2019 again. As for prominent ports this affects neither pciutils
2020 nor xorg-server this time, the hal port needs to be rebuilt
2024 The misnamed kthread_create() and friends have been renamed
2025 to kproc_create() etc. Many of the callers already
2026 used kproc_start()..
2027 I will return kthread_create() and friends in a while
2028 with implementations that actually create threads, not procs.
2029 Renaming corresponds with version 800002.
2038 Avoid using make -j when upgrading. While generally safe, there are
2039 sometimes problems using -j to upgrade. If your upgrade fails with
2040 -j, please try again without -j. From time to time in the past there
2041 have been problems using -j with buildworld and/or installworld. This
2042 is especially true when upgrading between "distant" versions (eg one
2043 that cross a major release boundary or several minor releases, or when
2044 several months have passed on the -current branch).
2046 Sometimes, obscure build problems are the result of environment
2047 poisoning. This can happen because the make utility reads its
2048 environment when searching for values for global variables. To run
2049 your build attempts in an "environmental clean room", prefix all make
2050 commands with 'env -i '. See the env(1) manual page for more details.
2052 When upgrading from one major version to another it is generally best
2053 to upgrade to the latest code in the currently installed branch first,
2054 then do an upgrade to the new branch. This is the best-tested upgrade
2055 path, and has the highest probability of being successful. Please try
2056 this approach before reporting problems with a major version upgrade.
2058 When upgrading a live system, having a root shell around before
2059 installing anything can help undo problems. Not having a root shell
2060 around can lead to problems if pam has changed too much from your
2061 starting point to allow continued authentication after the upgrade.
2065 When upgrading the boot ZFS pool to a new version, always follow
2068 1.) recompile and reinstall the ZFS boot loader and boot block
2069 (this is part of "make buildworld" and "make installworld")
2071 2.) update the ZFS boot block on your boot drive
2073 The following example updates the ZFS boot block on the first
2074 partition (freebsd-boot) of a GPT partitioned drive ad0:
2075 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2077 Non-boot pools do not need these updates.
2081 If you are updating from a prior version of FreeBSD (even one just
2082 a few days old), you should follow this procedure. It is the most
2083 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2085 make kernel-toolchain
2086 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2087 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2089 To test a kernel once
2090 ---------------------
2091 If you just want to boot a kernel once (because you are not sure
2092 if it works, or if you want to boot a known bad kernel to provide
2093 debugging information) run
2094 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2095 nextboot -k testkernel
2097 To just build a kernel when you know that it won't mess you up
2098 --------------------------------------------------------------
2099 This assumes you are already running a CURRENT system. Replace
2100 ${arch} with the architecture of your machine (e.g. "i386",
2101 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2103 cd src/sys/${arch}/conf
2104 config KERNEL_NAME_HERE
2105 cd ../compile/KERNEL_NAME_HERE
2110 If this fails, go to the "To build a kernel" section.
2112 To rebuild everything and install it on the current system.
2113 -----------------------------------------------------------
2114 # Note: sometimes if you are running current you gotta do more than
2115 # is listed here if you are upgrading from a really old current.
2117 <make sure you have good level 0 dumps>
2119 make kernel KERNCONF=YOUR_KERNEL_HERE
2121 <reboot in single user> [3]
2128 To cross-install current onto a separate partition
2129 --------------------------------------------------
2130 # In this approach we use a separate partition to hold
2131 # current's root, 'usr', and 'var' directories. A partition
2132 # holding "/", "/usr" and "/var" should be about 2GB in
2135 <make sure you have good level 0 dumps>
2138 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2139 <maybe newfs current's root partition>
2140 <mount current's root partition on directory ${CURRENT_ROOT}>
2141 make installworld DESTDIR=${CURRENT_ROOT}
2142 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2143 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2144 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2145 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2146 <reboot into current>
2147 <do a "native" rebuild/install as described in the previous section>
2148 <maybe install compatibility libraries from ports/misc/compat*>
2152 To upgrade in-place from stable to current
2153 ----------------------------------------------
2154 <make sure you have good level 0 dumps>
2156 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2158 <reboot in single user> [3]
2165 Make sure that you've read the UPDATING file to understand the
2166 tweaks to various things you need. At this point in the life
2167 cycle of current, things change often and you are on your own
2168 to cope. The defaults can also change, so please read ALL of
2169 the UPDATING entries.
2171 Also, if you are tracking -current, you must be subscribed to
2172 freebsd-current@freebsd.org. Make sure that before you update
2173 your sources that you have read and understood all the recent
2174 messages there. If in doubt, please track -stable which has
2175 much fewer pitfalls.
2177 [1] If you have third party modules, such as vmware, you
2178 should disable them at this point so they don't crash your
2181 [3] From the bootblocks, boot -s, and then do
2186 adjkerntz -i # if CMOS is wall time
2187 Also, when doing a major release upgrade, it is required that
2188 you boot into single user mode to do the installworld.
2190 [4] Note: This step is non-optional. Failure to do this step
2191 can result in a significant reduction in the functionality of the
2192 system. Attempting to do it by hand is not recommended and those
2193 that pursue this avenue should read this file carefully, as well
2194 as the archives of freebsd-current and freebsd-hackers mailing lists
2195 for potential gotchas. The -U option is also useful to consider.
2196 See mergemaster(8) for more information.
2198 [5] Usually this step is a noop. However, from time to time
2199 you may need to do this if you get unknown user in the following
2200 step. It never hurts to do it all the time. You may need to
2201 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2202 install) after the buildworld before this step if you last updated
2203 from current before 20130425 or from -stable before 20130430.
2205 [6] This only deletes old files and directories. Old libraries
2206 can be deleted by "make delete-old-libs", but you have to make
2207 sure that no program is using those libraries anymore.
2209 [8] In order to have a kernel that can run the 4.x binaries needed to
2210 do an installworld, you must include the COMPAT_FREEBSD4 option in
2211 your kernel. Failure to do so may leave you with a system that is
2212 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2213 required to run the 5.x binaries on more recent kernels. And so on
2214 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2216 Make sure that you merge any new devices from GENERIC since the
2217 last time you updated your kernel config file.
2219 [9] When checking out sources, you must include the -P flag to have
2220 cvs prune empty directories.
2222 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2223 "?=" instead of the "=" assignment operator, so that buildworld can
2224 override the CPUTYPE if it needs to.
2226 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2227 not on the command line, or in /etc/make.conf. buildworld will
2228 warn if it is improperly defined.
2231 This file contains a list, in reverse chronological order, of major
2232 breakages in tracking -current. It is not guaranteed to be a complete
2233 list of such breakages, and only contains entries since October 10, 2007.
2234 If you need to see UPDATING entries from before that date, you will need
2235 to fetch an UPDATING file from an older FreeBSD release.
2237 Copyright information:
2239 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2241 Redistribution, publication, translation and use, with or without
2242 modification, in full or in part, in any form or format of this
2243 document are permitted without further permission from the author.
2245 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2246 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2247 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2248 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2249 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2250 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2251 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2252 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2253 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2254 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2255 POSSIBILITY OF SUCH DAMAGE.
2257 Contact Warner Losh if you have any questions about your use of