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.
19 20150825: p2 FreeBSD-SA-15:22.openssh
21 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
23 Fix insufficient check of unsupported pkg(7) signature methods.
26 20150818: p1 FreeBSD-SA-15:20.expat
27 FreeBSD-EN-15:11.toolchain
28 FreeBSD-EN-15:12.netstat
29 FreeBSD-EN-15:13.vidcontrol
31 Fix multiple integer overflows in expat (libbsdxml) XML parser.
34 Fix make(1) syntax errors when upgrading from 9.x and earlier.
37 Fix incorrect netstat(1) data handling on 32-bit systems.
40 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
46 The default Unbound configuration now enables remote control
47 using a local socket. Users who have already enabled the
48 local_unbound service should regenerate their configuration
49 by running "service local_unbound setup" as root.
52 An additional fix for the issue described in the 20150614 sendmail
53 entry below has been been committed in revision 284786.
56 The fix for the issue described in the 20150614 sendmail entry
57 below has been been committed in revision 284485. The work
58 around described in that entry is no longer needed unless the
59 default setting is overridden by a confDH_PARAMETERS configuration
60 setting of '5' or pointing to a 512 bit DH parameter file.
63 The import of openssl to address the FreeBSD-SA-15:10.openssl
64 security advisory includes a change which rejects handshakes
65 with DH parameters below 768 bits. sendmail releases prior
66 to 8.15.2 (not yet released), defaulted to a 512 bit
67 DH parameter setting for client connections. To work around
68 this interoperability, sendmail can be configured to use a
69 2048 bit DH parameter by:
71 1. Edit /etc/mail/`hostname`.mc
72 2. If a setting for confDH_PARAMETERS does not exist or
73 exists and is set to a string beginning with '5',
75 3. If a setting for confDH_PARAMETERS exists and is set to
76 a file path, create a new file with:
77 openssl dhparam -out /path/to/file 2048
78 4. Rebuild the .cf file:
79 cd /etc/mail/; make; make install
81 cd /etc/mail/; make restart
83 A sendmail patch is coming, at which time this file will be
87 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
88 defined in symlink(7); previously symlinks were silently ignored.
91 The const qualifier has been removed from iconv(3) to comply with
92 POSIX. The ports tree is aware of this from r384038 onwards.
95 At svn r275807, The default linux compat kernel ABI has been adjusted
96 to 2.6.18 in support of the linux-c6 compat ports infrastructure
97 update. If you wish to continue using the linux-f10 compat ports,
98 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
99 encouraged to update their linux-compat packages to linux-c6 during
100 their next update cycle.
102 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
105 pjdfstest has been integrated into kyua as an opt-in test suite.
106 Please see share/doc/pjdfstest/README for a more details on how to
113 The ofwfb driver, used to provide a graphics console on PowerPC when
114 using vt(4), no longer allows mmap() of all of physical memory. This
115 will prevent Xorg on PowerPC with some ATI graphics cards from
116 initializing properly unless x11-servers/xorg-server is updated to
120 The libatf-c and libatf-c++ major versions were downgraded to 0 and
121 1 respectively to match the upstream numbers. They were out of
122 sync because, when they were originally added to FreeBSD, the
123 upstream versions were not respected. These libraries are private
124 and not yet built by default, so renumbering them should be a
125 non-issue. However, unclean source trees will yield broken test
126 programs once the operator executes "make delete-old-libs" after a
129 Additionally, the atf-sh binary was made private by moving it into
130 /usr/libexec/. Already-built shell test programs will keep the
131 path to the old binary so they will break after "make delete-old"
134 If you are using WITH_TESTS=yes (not the default), wipe the object
135 tree and rebuild from scratch to prevent spurious test failures.
136 This is only needed once: the misnumbered libraries and misplaced
137 binaries have been added to OptionalObsoleteFiles.inc so they will
138 be removed during a clean upgrade.
141 The ixgbe tunables now match their sysctl counterparts, for example:
142 hw.ixgbe.enable_aim => hw.ix.enable_aim
143 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
146 The NFSv4.1 server committed by r269398 changes the internal
147 function call interfaces used between the NFS and krpc modules.
148 As such, __FreeBSD_version was bumped.
151 The default unbound configuration has been modified to address
152 issues with reverse lookups on networks that use private
153 address ranges. If you use the local_unbound service, run
154 "service local_unbound setup" as root to regenerate your
155 configuration, then "service local_unbound reload" to load the
159 It is no longer necessary to include the dwarf version in your DEBUG
160 options in your kernel config file. The bug that required it to be
161 placed in the config file has bene fixed. DEBUG should now just
162 contain -g. The build system will automatically update things
163 to do the right thing.
166 Several ABI breaking changes were merged to CTL and new iSCSI code.
167 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
168 iscsictl need to be rebuilt to work with a new kernel.
171 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
172 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
173 which differs from the behaviour controlled by this knob.)
176 On i386 and amd64 systems, the onifconsole flag is now set by default
177 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
178 as a login TTY if it is set in the bootloader as an active kernel
179 console. No changes in behavior should result otherwise. To revert to
180 the previous behavior, set ttyu0 to "off" in /etc/ttys.
183 Clang and llvm have been upgraded to 3.4.1 release.
186 Clang and llvm have been upgraded to 3.4 release.
189 If a Makefile in a tests/ directory was auto-generating a Kyuafile
190 instead of providing an explicit one, this would prevent such
191 Makefile from providing its own Kyuafile in the future during
192 NO_CLEAN builds. This has been fixed in the Makefiles but manual
193 intervention is needed to clean an objdir if you use NO_CLEAN:
194 # find /usr/obj -name Kyuafile | xargs rm -f
197 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
198 capability mode support. Please note that enabling the feature in
199 kernel is still highly recommended.
202 OpenSSH is now built with sandbox support, and will use sandbox as
203 the default privilege separation method. This requires Capsicum
204 capability mode support in kernel.
207 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
208 been deprecated and will not be part of FreeBSD 11.0 and later
209 releases. If you use this driver, please consider switching to
210 the nfe(4) driver instead.
216 The behavior of gss_pseudo_random() for the krb5 mechanism
217 has changed, for applications requesting a longer random string
218 than produced by the underlying enctype's pseudo-random() function.
219 In particular, the random string produced from a session key of
220 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
221 be different at the 17th octet and later, after this change.
222 The counter used in the PRF+ construction is now encoded as a
223 big-endian integer in accordance with RFC 4402.
224 __FreeBSD_version is bumped to 1000701.
227 The WITHOUT_ATF build knob has been removed and its functionality
228 has been subsumed into the more generic WITHOUT_TESTS. If you were
229 using the former to disable the build of the ATF libraries, you
230 should change your settings to use the latter.
233 The default version of mtree is nmtree which is obtained from
234 NetBSD. The output is generally the same, but may vary
235 slightly. If you found you need identical output adding
236 "-F freebsd9" to the command line should do the trick. For the
237 time being, the old mtree is available as fmtree.
240 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
241 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
242 1.1.4_8 and verify bsdyml not linked in, before running "make
244 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
246 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
249 The rc.d/jail script has been updated to support jail(8)
250 configuration file. The "jail_<jname>_*" rc.conf(5) variables
251 for per-jail configuration are automatically converted to
252 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
253 This is transparently backward compatible. See below about some
254 incompatibilities and rc.conf(5) manual page for more details.
256 These variables are now deprecated in favor of jail(8) configuration
257 file. One can use "rc.d/jail config <jname>" command to generate
258 a jail(8) configuration file in /var/run/jail.<jname>.conf without
259 running the jail(8) utility. The default pathname of the
260 configuration file is /etc/jail.conf and can be specified by
261 using $jail_conf or $jail_<jname>_conf variables.
263 Please note that jail_devfs_ruleset accepts an integer at
264 this moment. Please consider to rewrite the ruleset name
268 BIND has been removed from the base system. If all you need
269 is a local resolver, simply enable and start the local_unbound
270 service instead. Otherwise, several versions of BIND are
271 available in the ports tree. The dns/bind99 port is one example.
273 With this change, nslookup(1) and dig(1) are no longer in the base
274 system. Users should instead use host(1) and drill(1) which are
275 in the base system. Alternatively, nslookup and dig can
276 be obtained by installing the dns/bind-tools port.
279 With the addition of unbound(8), a new unbound user is now
280 required during installworld. "mergemaster -p" can be used to
281 add the user prior to installworld, as documented in the handbook.
284 OpenSSH is now built with DNSSEC support, and will by default
285 silently trust signed SSHFP records. This can be controlled with
286 the VerifyHostKeyDNS client configuration setting. DNSSEC support
287 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
290 The GNU Compiler Collection and C++ standard library (libstdc++)
291 are no longer built by default on platforms where clang is the system
292 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
296 The PROCDESC kernel option is now part of the GENERIC kernel
297 configuration and is required for the rwhod(8) to work.
298 If you are using custom kernel configuration, you should include
302 The API and ABI related to the Capsicum framework was modified
303 in backward incompatible way. The userland libraries and programs
304 have to be recompiled to work with the new kernel. This includes the
305 following libraries and programs, but the whole buildworld is
306 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
307 kdump, procstat, rwho, rwhod, uniq.
310 AES-NI intrinsic support has been added to gcc. The AES-NI module
311 has been updated to use this support. A new gcc is required to build
312 the aesni module on both i386 and amd64.
315 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
316 Thus "device padlock_rng" and "device rdrand_rng" should be
317 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
320 WITH_ICONV has been split into two feature sets. WITH_ICONV now
321 enables just the iconv* functionality and is now on by default.
322 WITH_LIBICONV_COMPAT enables the libiconv api and link time
323 compatability. Set WITHOUT_ICONV to build the old way.
324 If you have been using WITH_ICONV before, you will very likely
325 need to turn on WITH_LIBICONV_COMPAT.
328 INVARIANTS option now enables DEBUG for code with OpenSolaris and
329 Illumos origin, including ZFS. If you have INVARIANTS in your
330 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
332 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
333 locks if WITNESS option was set. Because that generated a lot of
334 witness(9) reports and all of them were believed to be false
335 positives, this is no longer done. New option OPENSOLARIS_WITNESS
336 can be used to achieve the previous behavior.
339 Timer values in IPv6 data structures now use time_uptime instead
340 of time_second. Although this is not a user-visible functional
341 change, userland utilities which directly use them---ndp(8),
342 rtadvd(8), and rtsold(8) in the base system---need to be updated
346 find -delete can now delete the pathnames given as arguments,
347 instead of only files found below them or if the pathname did
348 not contain any slashes. Formerly, the following error message
351 find: -delete: <path>: relative path potentially not safe
353 Deleting the pathnames given as arguments can be prevented
354 without error messages using -mindepth 1 or by changing
355 directory and passing "." as argument to find. This works in the
356 old as well as the new version of find.
359 Behavior of devfs rules path matching has been changed.
360 Pattern is now always matched against fully qualified devfs
361 path and slash characters must be explicitly matched by
362 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
363 subdirectories must be reviewed.
366 The default ARM ABI has changed to the ARM EABI. The old ABI is
367 incompatible with the ARM EABI and all programs and modules will
368 need to be rebuilt to work with a new kernel.
370 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
372 NOTE: Support for the old ABI will be removed in the future and
373 users are advised to upgrade.
376 pkg_install has been disconnected from the build if you really need it
377 you should add WITH_PKGTOOLS in your src.conf(5).
380 Most of network statistics structures were changed to be able
381 keep 64-bits counters. Thus all tools, that work with networking
382 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
385 Fix targets that run multiple make's to use && rather than ;
386 so that subsequent steps depend on success of previous.
388 NOTE: if building 'universe' with -j* on stable/8 or stable/9
389 it would be better to start the build using bmake, to avoid
390 overloading the machine.
393 Fix a bug that allowed a tracing process (e.g. gdb) to write
394 to a memory-mapped file in the traced process's address space
395 even if neither the traced process nor the tracing process had
396 write access to that file.
399 CVS has been removed from the base system. An exact copy
400 of the code is available from the devel/cvs port.
403 Some people report the following error after the switch to bmake:
405 make: illegal option -- J
406 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
408 *** [buildworld] Error code 2
410 this likely due to an old instance of make in
411 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
412 which src/Makefile will use that blindly, if it exists, so if
413 you see the above error:
415 rm -rf `make -V MAKEPATH`
420 Use bmake by default.
421 Whereas before one could choose to build with bmake via
422 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
423 make. The goal is to remove these knobs for 10-RELEASE.
425 It is worth noting that bmake (like gmake) treats the command
426 line as the unit of failure, rather than statements within the
427 command line. Thus '(cd some/where && dosomething)' is safer
428 than 'cd some/where; dosomething'. The '()' allows consistent
429 behavior in parallel build.
432 Fix a bug that allows NFS clients to issue READDIR on files.
435 The WITHOUT_IDEA option has been removed because
436 the IDEA patent expired.
439 The sysctl which controls TRIM support under ZFS has been renamed
440 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
444 The mergemaster command now uses the default MAKEOBJDIRPREFIX
445 rather than creating it's own in the temporary directory in
446 order allow access to bootstrapped versions of tools such as
447 install and mtree. When upgrading from version of FreeBSD where
448 the install command does not support -l, you will need to
449 install a new mergemaster command if mergemaster -p is required.
450 This can be accomplished with the command (cd src/usr.sbin/mergemaster
454 Legacy ATA stack, disabled and replaced by new CAM-based one since
455 FreeBSD 9.0, completely removed from the sources. Kernel modules
456 atadisk and atapi*, user-level tools atacontrol and burncd are
457 removed. Kernel option `options ATA_CAM` is now permanently enabled
461 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
462 and socketpair(2). Software, in particular Kerberos, may
463 automatically detect and use these during building. The resulting
464 binaries will not work on older kernels.
467 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
468 information, see the respective 20130304 entry).
471 Recent commits to callout(9) changed the size of struct callout,
472 so the KBI is probably heavily disturbed. Also, some functions
473 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
474 by macros. Every kernel module using it won't load, so rebuild
477 The ctl device has been re-enabled in GENERIC for i386 and amd64,
478 but does not initialize by default (because of the new CTL_DISABLE
479 option) to save memory. To re-enable it, remove the CTL_DISABLE
480 option from the kernel config file or set kern.cam.ctl.disable=0
481 in /boot/loader.conf.
484 The ctl device has been disabled in GENERIC for i386 and amd64.
485 This was done due to the extra memory being allocated at system
486 initialisation time by the ctl driver which was only used if
487 a CAM target device was created. This makes a FreeBSD system
488 unusable on 128MB or less of RAM.
491 A new compression method (lz4) has been merged to -HEAD. Please
492 refer to zpool-features(7) for more information.
494 Please refer to the "ZFS notes" section of this file for information
495 on upgrading boot ZFS pools.
498 A BSD-licensed patch(1) variant has been added and is installed
499 as bsdpatch, being the GNU version the default patch.
500 To inverse the logic and use the BSD-licensed one as default,
501 while having the GNU version installed as gnupatch, rebuild
502 and install world with the WITH_BSD_PATCH knob set.
505 Due to the use of the new -l option to install(1) during build
506 and install, you must take care not to directly set the INSTALL
507 make variable in your /etc/make.conf, /etc/src.conf, or on the
508 command line. If you wish to use the -C flag for all installs
509 you may be able to add INSTALL+=-C to /etc/make.conf or
513 The install(1) option -M has changed meaning and now takes an
514 argument that is a file or path to append logs to. In the
515 unlikely event that -M was the last option on the command line
516 and the command line contained at least two files and a target
517 directory the first file will have logs appended to it. The -M
518 option served little practical purpose in the last decade so its
519 use is expected to be extremely rare.
522 After switching to Clang as the default compiler some users of ZFS
523 on i386 systems started to experience stack overflow kernel panics.
524 Please consider using 'options KSTACK_PAGES=4' in such configurations.
527 GEOM_LABEL now mangles label names read from file system metadata.
528 Mangling affect labels containing spaces, non-printable characters,
529 '%' or '"'. Device names in /etc/fstab and other places may need to
533 By default, only the 10 most recent kernel dumps will be saved. To
534 restore the previous behaviour (no limit on the number of kernel dumps
535 stored in the dump directory) add the following line to /etc/rc.conf:
540 With the addition of auditdistd(8), a new auditdistd user is now
541 required during installworld. "mergemaster -p" can be used to
542 add the user prior to installworld, as documented in the handbook.
545 The sin6_scope_id member variable in struct sockaddr_in6 is now
546 filled by the kernel before passing the structure to the userland via
547 sysctl or routing socket. This means the KAME-specific embedded scope
548 id in sin6_addr.s6_addr[2] is always cleared in userland application.
549 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
550 __FreeBSD_version is bumped to 1000025.
553 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
554 This means that the world and kernel will be compiled with clang
555 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
556 and /usr/bin/cpp. To disable this behavior and revert to building
557 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
558 of current may need to bootstrap WITHOUT_CLANG first if the clang
559 build fails (its compatibility window doesn't extend to the 9 stable
563 The IPFIREWALL_FORWARD kernel option has been removed. Its
564 functionality now turned on by default.
567 The ZERO_COPY_SOCKET kernel option has been removed and
568 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
569 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
570 mechanism which is not safe and may result in kernel crashes.
571 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
572 driver supports disposeable external page sized mbuf storage.
573 Proper replacements for both zero-copy mechanisms are under
574 consideration and will eventually lead to complete removal
575 of the two kernel options.
578 The IPv4 network stack has been converted to network byte
579 order. The following modules need to be recompiled together
580 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
581 pf(4), ipfw(4), ng_ipfw(4), stf(4).
584 Support for non-MPSAFE filesystems was removed from VFS. The
585 VFS_VERSION was bumped, all filesystem modules shall be
589 All the non-MPSAFE filesystems have been disconnected from
590 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
591 portalfs, smbfs, xfs.
594 The interface cloning API and ABI has changed. The following
595 modules need to be recompiled together with kernel:
596 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
597 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
598 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
601 The sdhci driver was split in two parts: sdhci (generic SD Host
602 Controller logic) and sdhci_pci (actual hardware driver).
603 No kernel config modifications are required, but if you
604 load sdhc as a module you must switch to sdhci_pci instead.
607 Import the FUSE kernel and userland support into base system.
610 The GNU sort(1) program has been removed since the BSD-licensed
611 sort(1) has been the default for quite some time and no serious
612 problems have been reported. The corresponding WITH_GNU_SORT
616 The pfil(9) API/ABI for AF_INET family has been changed. Packet
617 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
621 The net80211(4) ABI has been changed to allow for improved driver
622 PS-POLL and power-save support. All wireless drivers need to be
623 recompiled to work with the new kernel.
626 The random(4) support for the VIA hardware random number
627 generator (`PADLOCK') is no longer enabled unconditionally.
628 Add the padlock_rng device in the custom kernel config if
629 needed. The GENERIC kernels on i386 and amd64 do include the
630 device, so the change only affects the custom kernel
634 The pf(4) packet filter ABI has been changed. pfctl(8) and
635 snmp_pf module need to be recompiled to work with new kernel.
638 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
639 to -HEAD. Pools that have empty_bpobj in active state can not be
640 imported read-write with ZFS implementations that do not support
641 this feature. For more information read the zpool-features(5)
645 The sparc64 ZFS loader has been changed to no longer try to auto-
646 detect ZFS providers based on diskN aliases but now requires these
647 to be explicitly listed in the OFW boot-device environment variable.
650 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
651 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
652 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
655 The following sysctls and tunables have been renamed for consistency
656 with other variables:
657 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
658 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
661 The sort utility has been replaced with BSD sort. For now, GNU sort
662 is also available as "gnusort" or the default can be set back to
663 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
664 installed as "bsdsort".
667 A new version of ZFS (pool version 5000) has been merged to -HEAD.
668 Starting with this version the old system of ZFS pool versioning
669 is superseded by "feature flags". This concept enables forward
670 compatibility against certain future changes in functionality of ZFS
671 pools. The first read-only compatible "feature flag" for ZFS pools
672 is named "com.delphix:async_destroy". For more information
673 read the new zpool-features(5) manual page.
674 Please refer to the "ZFS notes" section of this file for information
675 on upgrading boot ZFS pools.
678 The malloc(3) implementation embedded in libc now uses sources imported
679 as contrib/jemalloc. The most disruptive API change is to
680 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
681 delete it prior to installworld, and optionally re-create it using the
682 new format after rebooting. See malloc.conf(5) for details
683 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
687 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
688 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
689 now spelled mips. This is to aid compatibility with third-party
690 software that expects this naming scheme in uname(3). Little-endian
691 settings are unchanged. If you are updating a big-endian mips64 machine
692 from before this change, you may need to set MACHINE_ARCH=mips64 in
693 your environment before the new build system will recognize your machine.
696 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
700 Now unix domain sockets behave "as expected" on nullfs(5). Previously
701 nullfs(5) did not pass through all behaviours to the underlying layer,
702 as a result if we bound to a socket on the lower layer we could connect
703 only to the lower path; if we bound to the upper layer we could connect
704 only to the upper path. The new behavior is one can connect to both the
705 lower and the upper paths regardless what layer path one binds to.
708 The getifaddrs upgrade path broken with 20111215 has been restored.
709 If you have upgraded in between 20111215 and 20120209 you need to
710 recompile libc again with your kernel. You still need to recompile
711 world to be able to configure CARP but this restriction already
715 The set_rcvar() function has been removed from /etc/rc.subr. All
716 base and ports rc.d scripts have been updated, so if you have a
717 port installed with a script in /usr/local/etc/rc.d you can either
718 hand-edit the rcvar= line, or reinstall the port.
720 An easy way to handle the mass-update of /etc/rc.d:
721 rm /etc/rc.d/* && mergemaster -i
724 panic(9) now stops other CPUs in the SMP systems, disables interrupts
725 on the current CPU and prevents other threads from running.
726 This behavior can be reverted using the kern.stop_scheduler_on_panic
728 The new behavior can be incompatible with kern.sync_on_panic.
731 The carp(4) facility has been changed significantly. Configuration
732 of the CARP protocol via ifconfig(8) has changed, as well as format
733 of CARP events submitted to devd(8) has changed. See manual pages
734 for more information. The arpbalance feature of carp(4) is currently
735 not supported anymore.
737 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
738 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
739 need to be recompiled.
742 The acpi_wmi(4) status device /dev/wmistat has been renamed to
746 The option VFS_ALLOW_NONMPSAFE option has been added in order to
747 explicitely support non-MPSAFE filesystems.
748 It is on by default for all supported platform at this present
752 The broken amd(4) driver has been replaced with esp(4) in the amd64,
753 i386 and pc98 GENERIC kernel configuration files.
756 sysinstall has been removed
759 The stable/9 branch created in subversion. This corresponds to the
760 RELENG_9 branch in CVS.
763 This commit modifies vfs_register() so that it uses a hash
764 calculation to set vfc_typenum, which is enabled by default.
765 The first time a system is booted after this change, the
766 vfc_typenum values will change for all file systems. The
767 main effect of this is a change to the NFS server file handles
768 for file systems that use vfc_typenum in their fsid, such as ZFS.
769 It will, however, prevent vfc_typenum from changing when file
770 systems are loaded in a different order for subsequent reboots.
771 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
772 until you are ready to remount all NFS clients after a reboot.
775 Bump the shared library version numbers for libraries that
776 do not use symbol versioning, have changed the ABI compared
777 to stable/8 and which shared library version was not bumped.
778 Done as part of 9.0-RELEASE cycle.
781 During the merge of Capsicum features, the fget(9) KPI was modified.
782 This may require the rebuilding of out-of-tree device drivers --
783 issues have been reported specifically with the nVidia device driver.
784 __FreeBSD_version is bumped to 900041.
786 Also, there is a period between 20110811 and 20110814 where the
787 special devices /dev/{stdin,stdout,stderr} did not work correctly.
788 Building world from a kernel during that window may not work.
791 The packet filter (pf) code has been updated to OpenBSD 4.5.
792 You need to update userland tools to be in sync with kernel.
793 This update breaks backward compatibility with earlier pfsync(4)
794 versions. Care must be taken when updating redundant firewall setups.
797 The following sysctls and tunables are retired on x86 platforms:
799 machdep.hlt_logical_cpus
800 The following sysctl is retired:
801 machdep.hyperthreading_allowed
802 The sysctls were supposed to provide a way to dynamically offline and
803 online selected CPUs on x86 platforms, but the implementation has not
804 been reliable especially with SCHED_ULE scheduler.
805 machdep.hyperthreading_allowed tunable is still available to ignore
806 hyperthreading CPUs at OS level.
807 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
808 where X is an APIC ID of a CPU. Be advised, though, that disabling
809 CPUs in non-uniform fashion will result in non-uniform topology and
810 may lead to sub-optimal system performance with SCHED_ULE, which is
814 cpumask_t type is retired and cpuset_t is used in order to describe
818 Changes to ifconfig(8) for dynamic address family detection mandate
819 that you are running a kernel of 20110525 or later. Make sure to
820 follow the update procedure to boot a new kernel before installing
824 Support for sun4v architecture is officially dropped
827 Several KPI breaking changes have been committed to the mii(4) layer,
828 the PHY drivers and consequently some Ethernet drivers using mii(4).
829 This means that miibus.ko and the modules of the affected Ethernet
830 drivers need to be recompiled.
832 Note to kernel developers: Given that the OUI bit reversion problem
833 was fixed as part of these changes all mii(4) commits related to OUIs,
834 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
835 handling, no longer can be merged verbatim to stable/8 and previous
839 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
840 into their kernel configurations along with 'device pci'.
843 The default NFS client is now the new NFS client, so fstype "newnfs"
844 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
845 Although mounts via fstype "nfs" will usually work without userland
846 changes, it is recommended that the mount(8) and mount_nfs(8)
847 commands be rebuilt from sources and that a link to mount_nfs called
848 mount_oldnfs be created. The new client is compiled into the
849 kernel with "options NFSCL" and this is needed for diskless root
850 file systems. The GENERIC kernel configs have been changed to use
851 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
852 To use the regular/old client, you can "mount -t oldnfs ...". For
853 a diskless root file system, you must also include a line like:
855 vfs.root.mountfrom="oldnfs:"
857 in the boot/loader.conf on the root fs on the NFS server to make
858 a diskless root fs use the old client.
861 The GENERIC kernels for all architectures now default to the new
862 CAM-based ATA stack. It means that all legacy ATA drivers were
863 removed and replaced by respective CAM drivers. If you are using
864 ATA device names in /etc/fstab or other places, make sure to update
865 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
866 where 'Y's are the sequential numbers starting from zero for each type
867 in order of detection, unless configured otherwise with tunables,
868 see cam(4)). There will be symbolic links created in /dev/ to map
869 old adX devices to the respective adaY. They should provide basic
870 compatibility for file systems mounting in most cases, but they do
871 not support old user-level APIs and do not have respective providers
872 in GEOM. Consider using updated management tools with new device names.
874 It is possible to load devices ahci, ata, siis and mvs as modules,
875 but option ATA_CAM should remain in kernel configuration to make ata
876 module work as CAM driver supporting legacy ATA controllers. Device ata
877 still can be used in modular fashion (atacore + ...). Modules atadisk
878 and atapi* are not used and won't affect operation in ATA_CAM mode.
879 Note that to use CAM-based ATA kernel should include CAM devices
880 scbus, pass, da (or explicitly ada), cd and optionally others. All of
881 them are parts of the cam module.
883 ataraid(4) functionality is now supported by the RAID GEOM class.
884 To use it you can load geom_raid kernel module and use graid(8) tool
885 for management. Instead of /dev/arX device names, use /dev/raid/rX.
887 No kernel config options or code have been removed, so if a problem
888 arises, please report it and optionally revert to the old ATA stack.
889 In order to do it you can remove from the kernel config:
894 , and instead add back:
895 device atadisk # ATA disk drives
896 device ataraid # ATA RAID drives
897 device atapicd # ATAPI CDROM drives
898 device atapifd # ATAPI floppy drives
899 device atapist # ATAPI tape drives
902 The default NFS server has been changed to the new server, which
903 was referred to as the experimental server. If you need to switch
904 back to the old NFS server, you must now put the "-o" option on
905 both the mountd and nfsd commands. This can be done using the
906 mountd_flags and nfs_server_flags rc.conf variables until an
907 update to the rc scripts is committed, which is coming soon.
910 The GNU Objective-C runtime library (libobjc), and other Objective-C
911 related components have been removed from the base system. If you
912 require an Objective-C library, please use one of the available ports.
915 ath(4) has been split into bus- and device- modules. if_ath contains
916 the HAL, the TX rate control and the network device code. if_ath_pci
917 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
918 contains the AHB glue. Users need to load both if_ath_pci and if_ath
919 in order to use ath on everything else.
921 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
922 need to load if_ath and if_ath_pci for ath(4) operation.
925 As part of the replacement of sysinstall, the process of building
926 release media has changed significantly. For details, please re-read
927 release(7), which has been updated to reflect the new build process.
930 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
931 is the last available version under GPLv2. It brings a number of new
932 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
933 4.1 and SSE 4.2), better support for powerpc64, a number of new
934 directives, and lots of other small improvements. See the ChangeLog
935 file in contrib/binutils for the full details.
938 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
939 compliant, and will now use half of hash for authentication.
940 This will break interoperability with all stacks (including all
941 actual FreeBSD versions) who implement
942 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
944 The only workaround with such peers is to use another HMAC
945 algorithm for IPsec ("phase 2") authentication.
948 Remove the uio_yield prototype and symbol. This function has
949 been misnamed since it was introduced and should not be
950 globally exposed with this name. The equivalent functionality
951 is now available using kern_yield(curthread->td_user_pri).
952 The function remains undocumented.
955 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
956 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
957 for scalar sysctls is defined but disabled. Code that needs
958 UQUAD to pass the type checking that must compile on older
959 systems where the define is not present can check against
960 __FreeBSD_version >= 900030.
962 The system dialog(1) has been replaced with a new version previously
963 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
964 with the previous version, but the libdialog associated with it has
965 a largely incompatible API. As such, the original version of libdialog
966 will be kept temporarily as libodialog, until its base system consumers
967 are replaced or updated. Bump __FreeBSD_version to 900030.
970 If you are trying to run make universe on a -stable system, and you get
971 the following warning:
972 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
973 unknown. config(8) likely too old."
974 or something similar to it, then you must upgrade your -stable system
975 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
976 stable/8) or build the config from the latest stable/8 branch and
977 install it on your system.
979 Prior to this date, building a current universe on 8-stable system from
980 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
981 error in the first kernel build phase. A new config on those old
982 systems will fix that problem for older versions of -current.
985 The TCP stack has been modified to allow Khelp modules to interact with
986 it via helper hook points and store per-connection data in the TCP
987 control block. Bump __FreeBSD_version to 900029. User space tools that
988 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
992 Generic IEEE 802.3 annex 31B full duplex flow control support has been
993 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
994 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
995 to take advantage of it instead of using custom implementations. This
996 means that these drivers now no longer unconditionally advertise
997 support for flow control but only do so if flow control is a selected
998 media option. This was implemented in the generic support that way in
999 order to allow flow control to be switched on and off via ifconfig(8)
1000 with the PHY specific default to typically off in order to protect
1001 from unwanted effects. Consequently, if you used flow control with
1002 one of the above mentioned drivers you now need to explicitly enable
1003 it, for example via:
1004 ifconfig bge0 media auto mediaopt flowcontrol
1006 Along with the above mentioned changes generic support for setting
1007 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1008 e1000phy(4) as well as ip1000phy(4) have been converted to take
1009 advantage of it. This means that these drivers now no longer take the
1010 link0 parameter for selecting master mode but the master media option
1011 has to be used instead, for example like in the following:
1012 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1014 Selection of master mode now is also available with all other PHY
1015 drivers supporting 1000baseT.
1018 The TCP stack has received a significant update to add support for
1019 modularised congestion control and generally improve the clarity of
1020 congestion control decisions. Bump __FreeBSD_version to 900025. User
1021 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1022 sockstat) need to be recompiled.
1025 The man(1) utility has been replaced by a new version that no longer
1026 uses /etc/manpath.config. Please consult man.conf(5) for how to
1027 migrate local entries to the new format.
1030 The copyright strings printed by login(1) and sshd(8) at the time of a
1031 new connection have been removed to follow other operating systems and
1035 A workaround for a fixed ld bug has been removed in kernel code,
1036 so make sure that your system ld is built from sources after
1037 revision 210245 from 2010-07-19 (r211583 if building head kernel
1038 on stable/8, r211584 for stable/7; both from 2010-08-21).
1039 A symptom of incorrect ld version is different addresses for
1040 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1043 The $ipv6_prefer variable in rc.conf(5) has been split into
1044 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1046 The $ip6addrctl_policy is a variable to choose a pre-defined
1047 address selection policy set by ip6addrctl(8). A value
1048 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1051 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1052 flag (see an entry of 20090926) is set on an interface with no
1053 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1054 security reason. If you want IPv6 link-local address on all
1055 interfaces by default, set this to "YES".
1057 The old ipv6_prefer="YES" is equivalent to
1058 ipv6_activate_all_interfaces="YES" and
1059 ip6addrctl_policy="ipv6_prefer".
1062 DTrace has grown support for userland tracing. Due to this, DTrace is
1063 now i386 and amd64 only.
1064 dtruss(1) is now installed by default on those systems and a new
1065 kernel module is needed for userland tracing: fasttrap.
1066 No changes to your kernel config file are necessary to enable
1067 userland tracing, but you might consider adding 'STRIP=' and
1068 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1069 to have informative userland stack traces in DTrace (ustack).
1072 The acpi_aiboost(4) driver has been removed in favor of the new
1073 aibs(4) driver. You should update your kernel configuration file.
1076 BSD grep has been imported to the base system and it is built by
1077 default. It is completely BSD licensed, highly GNU-compatible, uses
1078 less memory than its GNU counterpart and has a small codebase.
1079 However, it is slower than its GNU counterpart, which is mostly
1080 noticeable for larger searches, for smaller ones it is measurable
1081 but not significant. The reason is complex, the most important factor
1082 is that we lack a modern and efficient regex library and GNU
1083 overcomes this by optimizing the searches internally. Future work
1084 on improving the regex performance is planned, for the meantime,
1085 users that need better performance, can build GNU grep instead by
1086 setting the WITH_GNU_GREP knob.
1089 Due to the import of powerpc64 support, all existing powerpc kernel
1090 configuration files must be updated with a machine directive like this:
1091 machine powerpc powerpc
1093 In addition, an updated config(8) is required to build powerpc kernels
1097 A new version of ZFS (version 15) has been merged to -HEAD.
1098 This version uses a python library for the following subcommands:
1099 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1100 For full functionality of these commands the following port must
1101 be installed: sysutils/py-zfs
1104 'vm_page's are now hashed by physical address to an array of mutexes.
1105 Currently this is only used to serialize access to hold_count. Over
1106 time the page queue mutex will be peeled away. This changes the size
1107 of pmap on every architecture. And requires all callers of vm_page_hold
1108 and vm_page_unhold to be updated.
1111 WITH_CTF can now be specified in src.conf (not recommended, there
1112 are some problems with static executables), make.conf (would also
1113 affect ports which do not use GNU make and do not override the
1114 compile targets) or in the kernel config (via "makeoptions
1116 When WITH_CTF was specified there before this was silently ignored,
1117 so make sure that WITH_CTF is not used in places which could lead
1118 to unwanted behavior.
1121 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1122 to allow 32-bit compatibility on non-x86 platforms. All kernel
1123 configurations on amd64 and ia64 platforms using these options must
1124 be modified accordingly.
1127 The utmp user accounting database has been replaced with utmpx,
1128 the user accounting interface standardized by POSIX.
1129 Unfortunately the semantics of utmp and utmpx don't match,
1130 making it practically impossible to support both interfaces.
1131 The user accounting database is used by tools like finger(1),
1132 last(1), talk(1), w(1) and ac(8).
1134 All applications in the base system use utmpx. This means only
1135 local binaries (e.g. from the ports tree) may still use these
1136 utmp database files. These applications must be rebuilt to make
1139 After the system has been upgraded, it is safe to remove the old
1140 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1141 assuming their contents is of no importance anymore. Old wtmp
1142 databases can only be used by last(1) and ac(8) after they have
1143 been converted to the new format using wtmpcvt(1).
1146 Introduce the kernel thread "deadlock resolver" (which can be enabled
1147 via the DEADLKRES option, see NOTES for more details) and the
1148 sleepq_type() function for sleepqueues.
1151 The rc.firewall and rc.firewall6 were unified, and
1152 rc.firewall6 and rc.d/ip6fw were removed.
1153 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1154 variables are obsoleted. Instead, the following new rc
1155 variables are added to rc.d/ipfw:
1157 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1158 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1159 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1161 The meanings correspond to the relevant IPv4 variables.
1167 The default terminal emulation for syscons(4) has been changed
1168 from cons25 to xterm on all platforms except pc98. This means
1169 that the /etc/ttys file needs to be updated to ensure correct
1170 operation of applications on the console.
1172 The terminal emulation style can be toggled per window by using
1173 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1174 options can be used to change the compile-time default back to
1177 To prevent graphical artifacts, make sure the TERM environment
1178 variable is set to match the terminal emulation that is being
1179 performed by syscons(4).
1182 The layout of the structure ieee80211req_scan_result has changed.
1183 Applications that require wireless scan results (e.g. ifconfig(8))
1184 from net80211 need to be recompiled.
1186 Applications such as wpa_supplicant(8) may require a full world
1187 build without using NO_CLEAN in order to get synchronized with the
1191 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1192 There's one kernel module for each firmware. Adding "device iwnfw"
1193 to the kernel configuration file means including all three firmware
1194 images inside the kernel. If you want to include just the one for
1195 your wireless card, use the devices iwn4965fw, iwn5000fw or
1199 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1200 into rc.d/netif. The changes are the following:
1202 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1203 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1204 Note that both variables need the "inet6" keyword at the head.
1206 Do not set $ipv6_network_interfaces manually if you do not
1207 understand what you are doing. It is not needed in most cases.
1209 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1212 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1213 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1215 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1216 all configured interfaces have "inet6 accept_rtadv" in the
1217 $ifconfig_IF_ipv6. These are for backward compatibility.
1219 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1220 functionality of interfaces with no corresponding
1221 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1222 and the default address selection policy of ip6addrctl(8)
1223 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1224 Note that if you want to configure IPv6 functionality on the
1225 disabled interfaces after boot, first you need to clear the flag by
1226 using ifconfig(8) like:
1228 ifconfig em0 inet6 -ifdisabled
1230 If YES, the default address selection policy is set as
1233 The default value of $ipv6_prefer is NO.
1235 4. If your system need to receive Router Advertisement messages,
1236 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1237 scripts automatically invoke rtsol(8) when the interface becomes
1238 UP. The Router Advertisement messages are used for SLAAC
1239 (State-Less Address AutoConfiguration).
1242 802.11s D3.03 support was committed. This is incompatible with the
1243 previous code, which was based on D3.0.
1246 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1247 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1248 control whether accepting Router Advertisement messages or not.
1249 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1250 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1251 The ifconfig(8) utility now supports these flags.
1254 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1255 mount(8) and -a option for df(1) to see them.
1258 The old tunable hw.bus.devctl_disable has been superseded by
1259 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1260 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1264 Remove the option STOP_NMI. The default action is now to use NMI only
1265 for KDB via the newly introduced function stop_cpus_hard() and
1266 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1269 The stable/8 branch created in subversion. This corresponds to the
1270 RELENG_8 branch in CVS.
1273 Bump the shared library version numbers for all libraries that do not
1274 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1275 __FreeBSD_version to 800105.
1278 Due to changes in the implementation of virtual network stack support,
1279 all network-related kernel modules must be recompiled. As this change
1280 breaks the ABI, bump __FreeBSD_version to 800104.
1283 The TOE interface to the TCP syncache has been modified to remove
1284 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1285 The cxgb driver is the only TOE consumer affected by this change, and
1286 needs to be recompiled along with the kernel. As this change breaks
1287 the ABI, bump __FreeBSD_version to 800103.
1290 Padding has been added to struct tcpcb, sackhint and tcpstat in
1291 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1292 maintaining the ABI. However, this change breaks the ABI, so bump
1293 __FreeBSD_version to 800102. User space tools that rely on the size of
1294 any of these structs (e.g. sockstat) need to be recompiled.
1297 The NFS_LEGACYRPC option has been removed along with the old kernel
1298 RPC implementation that this option selected. Kernel configurations
1299 may need to be adjusted.
1302 The network interface device nodes at /dev/net/<interface> have been
1303 removed. All ioctl operations can be performed the normal way using
1304 routing sockets. The kqueue functionality can generally be replaced
1305 with routing sockets.
1308 The documentation from the FreeBSD Documentation Project (Handbook,
1309 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1310 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1313 The ABI of various structures related to the SYSV IPC API have been
1314 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1315 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1319 Layout of struct vnet has changed as routing related variables were
1320 moved to their own Vimage module. Modules need to be recompiled. Bump
1321 __FreeBSD_version to 800099.
1324 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1325 respectively. As long as no more than 16 groups per process are used,
1326 no changes should be visible. When more than 16 groups are used, old
1327 binaries may fail if they call getgroups() or getgrouplist() with
1328 statically sized storage. Recompiling will work around this, but
1329 applications should be modified to use dynamically allocated storage
1330 for group arrays as POSIX.1-2008 does not cap an implementation's
1331 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1333 NFS and portalfs mounts may also be affected as the list of groups is
1334 truncated to 16. Users of NFS who use more than 16 groups, should
1335 take care that negative group permissions are not used on the exported
1336 file systems as they will not be reliable unless a GSSAPI based
1337 authentication method is used.
1340 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1341 option compiles in the support for adaptive spinning for lockmgrs
1342 which want to enable it. The lockinit() function now accepts the flag
1343 LK_ADAPTIVE in order to make the lock object subject to adaptive
1344 spinning when both held in write and read mode.
1347 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1348 changed. User applications that use this ioctl need to be rebuilt.
1351 The layout of struct thread has changed. Kernel and modules need to
1355 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1356 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1359 window(1) has been removed from the base system. It can now be
1360 installed from ports. The port is called misc/window.
1363 The way we are storing and accessing `routing table' entries has
1364 changed. Programs reading the FIB, like netstat, need to be
1368 A new netisr implementation has been added for FreeBSD 8. Network
1369 file system modules, such as igmp, ipdivert, and others, should be
1371 Bump __FreeBSD_version to 800096.
1374 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1378 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1379 Bump __FreeBSD_version to 800094.
1382 Add mnt_xflag field to 'struct mount'. File system modules need to be
1384 Bump __FreeBSD_version to 800093.
1387 The compiling option ADAPTIVE_SX has been retired while it has been
1388 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1389 The KPI for sx_init_flags() changes as accepting flags:
1390 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1391 been introduced in order to handle the reversed logic.
1392 Bump __FreeBSD_version to 800092.
1395 Add support for hierarchical jails. Remove global securelevel.
1396 Bump __FreeBSD_version to 800091.
1399 The layout of struct vnet_net has changed, therefore modules
1401 Bump __FreeBSD_version to 800090.
1404 The newly imported zic(8) produces a new format in the output. Please
1405 run tzsetup(8) to install the newly created data to /etc/localtime.
1408 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1409 hw.usb.* and is now consistent again with previous releases.
1412 802.11 monitor mode support was revised and driver api's were changed.
1413 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1414 of DLT_IEEE802_11. No user-visible data structures were changed but
1415 applications that use DLT_IEEE802_11 may require changes.
1416 Bump __FreeBSD_version to 800088.
1419 The layout of the following structs has changed: sysctl_oid,
1420 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1421 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1422 panics may be experienced. World rebuild is required for
1423 correctly checking networking state from userland.
1424 Bump __FreeBSD_version to 800085.
1427 MLDv2 and Source-Specific Multicast (SSM) have been merged
1428 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1429 The implementation of SSM within FreeBSD's IPv6 stack closely
1430 follows the IPv4 implementation.
1432 For kernel developers:
1434 * The most important changes are that the ip6_output() and
1435 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1436 and this lock has been downgraded to a non-recursive mutex.
1438 * As with the changes to the IPv4 stack to support SSM, filtering
1439 of inbound multicast traffic must now be performed by transport
1440 protocols within the IPv6 stack. This does not apply to TCP and
1441 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1443 * The KPIs used by IPv6 multicast are similar to those used by
1444 the IPv4 stack, with the following differences:
1445 * im6o_mc_filter() is analogous to imo_multicast_filter().
1446 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1447 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1448 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1449 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1450 for MLDv1 have an additional 'timer' argument which is used to
1451 jitter the initial membership report for the solicited-node
1452 multicast membership on-link.
1453 * This is not strictly needed for MLDv2, which already jitters
1454 its report transmissions. However, the 'timer' argument is
1455 preserved in case MLDv1 is active on the interface.
1457 * The KAME linked-list based IPv6 membership implementation has
1458 been refactored to use a vector similar to that used by the IPv4
1460 Code which maintains a list of its own multicast memberships
1461 internally, e.g. carp, has been updated to reflect the new
1464 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1465 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1466 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1467 implementation constraint which needs to be addressed in HEAD.
1469 For application developers:
1471 * The changes are broadly similar to those made for the IPv4
1474 * The use of IPv4 and IPv6 multicast socket options on the same
1475 socket, using mapped addresses, HAS NOT been tested or supported.
1477 * There are a number of issues with the implementation of various
1478 IPv6 multicast APIs which need to be resolved in the API surface
1479 before the implementation is fully compatible with KAME userland
1480 use, and these are mostly to do with interface index treatment.
1482 * The literature available discusses the use of either the delta / ASM
1483 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1484 using setsourcefilter(3)/getsourcefilter(3). For more information
1485 please refer to RFC 3768, 'Socket Interface Extensions for
1486 Multicast Source Filters'.
1488 * Applications which use the published RFC 3678 APIs should be fine.
1490 For systems administrators:
1492 * The mtest(8) utility has been refactored to support IPv6, in
1493 addition to IPv4. Interface addresses are no longer accepted
1494 as arguments, their names must be used instead. The utility
1495 will map the interface name to its first IPv4 address as
1496 returned by getifaddrs(3).
1498 * The ifmcstat(8) utility has also been updated to print the MLDv2
1499 endpoint state and source filter lists via sysctl(3).
1501 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1502 loopback of IPv6 multicast datagrams by default; it defaults to 1
1503 to preserve the existing behaviour. Disabling multicast loopback is
1504 recommended for optimal system performance.
1506 * The IPv6 MROUTING code has been changed to examine this sysctl
1507 instead of attempting to perform a group lookup before looping
1508 back forwarded datagrams.
1510 Bump __FreeBSD_version to 800084.
1513 Implement low-level Bluetooth HCI API.
1514 Bump __FreeBSD_version to 800083.
1517 The layout of struct malloc_type, used by modules to register new
1518 memory allocation types, has changed. Most modules will need to
1519 be rebuilt or panics may be experienced.
1520 Bump __FreeBSD_version to 800081.
1523 Anticipate overflowing inp_flags - add inp_flags2.
1524 This changes most offsets in inpcb, so checking v4 connection
1525 state will require a world rebuild.
1526 Bump __FreeBSD_version to 800080.
1529 Add an llentry to struct route and struct route_in6. Modules
1530 embedding a struct route will need to be recompiled.
1531 Bump __FreeBSD_version to 800079.
1534 The size of rt_metrics_lite and by extension rtentry has changed.
1535 Networking administration apps will need to be recompiled.
1536 The route command now supports show as an alias for get, weighting
1537 of routes, sticky and nostick flags to alter the behavior of stateful
1539 Bump __FreeBSD_version to 800078.
1542 Do not use Giant for kbdmux(4) locking. This is wrong and
1543 apparently causing more problems than it solves. This will
1544 re-open the issue where interrupt handlers may race with
1545 kbdmux(4) in polling mode. Typical symptoms include (but
1546 not limited to) duplicated and/or missing characters when
1547 low level console functions (such as gets) are used while
1548 interrupts are enabled (for example geli password prompt,
1549 mountroot prompt etc.). Disabling kbdmux(4) may help.
1552 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1553 kernel modules referencing any of the above need to be recompiled.
1554 Bump __FreeBSD_version to 800075.
1557 GEOM_PART has become the default partition slicer for storage devices,
1558 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1559 introduces some changes:
1561 MSDOS/EBR: the devices created from MSDOS extended partition entries
1562 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1563 to devices with offset-based names. fstabs may need to be modified.
1565 BSD: the "geometry does not match label" warning is harmless in most
1566 cases but it points to problems in file system misalignment with
1567 disk geometry. The "c" partition is now implicit, covers the whole
1568 top-level drive and cannot be (mis)used by users.
1570 General: Kernel dumps are now not allowed to be written to devices
1571 whose partition types indicate they are meant to be used for file
1572 systems (or, in case of MSDOS partitions, as something else than
1575 Most of these changes date approximately from 200812.
1578 The uscanner(4) driver has been removed from the kernel. This follows
1579 Linux removing theirs in 2.6 and making libusb the default interface
1580 (supported by sane).
1583 The multicast forwarding code has been cleaned up. netstat(1)
1584 only relies on KVM now for printing bandwidth upcall meters.
1585 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1586 ip6_mroute_mod respectively. The config(5) options for statically
1587 compiling this code remain the same, i.e. 'options MROUTING'.
1590 Support for the IFF_NEEDSGIANT network interface flag has been
1591 removed, which means that non-MPSAFE network device drivers are no
1592 longer supported. In particular, if_ar, if_sr, and network device
1593 drivers from the old (legacy) USB stack can no longer be built or
1597 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1598 a bunch of new language catalog files have also been added.
1599 This means that some common libc messages are now localized and
1600 they depend on the LC_MESSAGES environmental variable.
1603 The k8temp(4) driver has been renamed to amdtemp(4) since
1604 support for Family 10 and Family 11 CPU families was added.
1607 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1608 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1610 For kernel developers, the most important changes are that the
1611 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1612 and this lock has been downgraded to a non-recursive mutex.
1614 Transport protocols (UDP, Raw IP) are now responsible for filtering
1615 inbound multicast traffic according to group membership and source
1616 filters. The imo_multicast_filter() KPI exists for this purpose.
1617 Transports which do not use multicast (SCTP, TCP) already reject
1618 multicast by default. Forwarding and receive performance may improve
1619 as a mutex acquisition is no longer needed in the ip_input()
1620 low-level input path. in_addmulti() and in_delmulti() are shimmed
1621 to new KPIs which exist to support SSM in-kernel.
1623 For application developers, it is recommended that loopback of
1624 multicast datagrams be disabled for best performance, as this
1625 will still cause the lock to be taken for each looped-back
1626 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1627 be tuned to 0 to disable loopback by default; it defaults to 1
1628 to preserve the existing behaviour.
1630 For systems administrators, to obtain best performance with
1631 multicast reception and multiple groups, it is always recommended
1632 that a card with a suitably precise hash filter is used. Hash
1633 collisions will still result in the lock being taken within the
1634 transport protocol input path to check group membership.
1636 If deploying FreeBSD in an environment with IGMP snooping switches,
1637 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1638 enabled; this forces 224.0.0.0/24 group membership to be announced
1641 The size of 'struct igmpstat' has changed; netstat needs to be
1642 recompiled to reflect this.
1643 Bump __FreeBSD_version to 800070.
1646 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1647 updated to use it. This requires a buildworld/installworld in order to
1648 update the library and dependencies (usbconfig, etc). Its advisable to
1649 rebuild all ports which uses libusb. More specific directions are given
1650 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1651 libusb are no longer required and can be removed.
1654 A workaround is committed to allow the creation of System V shared
1655 memory segment of size > 2 GB on the 64-bit architectures.
1656 Due to a limitation of the existing ABI, the shm_segsz member
1657 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1658 wrong for large segments. Note that limits must be explicitly
1659 raised to allow such segments to be created.
1662 The layout of struct ifnet has changed, requiring a rebuild of all
1663 network device driver modules.
1666 The /dev handling for the new USB stack has changed, a
1667 buildworld/installworld is required for libusb20.
1670 The new USB2 stack has now been permanently moved in and all kernel and
1671 module names reverted to their previous values (eg, usb, ehci, ohci,
1672 ums, ...). The old usb stack can be compiled in by prefixing the name
1673 with the letter 'o', the old usb modules have been removed.
1674 Updating entry 20090216 for xorg and 20090215 for libmap may still
1678 The rc.conf(5) option if_up_delay has been renamed to
1679 defaultroute_delay to better reflect its purpose. If you have
1680 customized this setting in /etc/rc.conf you need to update it to
1684 xorg 7.4 wants to configure its input devices via hald which does not
1685 yet work with USB2. If the keyboard/mouse does not work in xorg then
1687 Option "AllowEmptyInput" "off"
1688 to your ServerLayout section. This will cause X to use the configured
1689 kbd and mouse sections from your xorg.conf.
1692 The GENERIC kernels for all architectures now default to the new USB2
1693 stack. No kernel config options or code have been removed so if a
1694 problem arises please report it and optionally revert to the old USB
1695 stack. If you are loading USB kernel modules or have a custom kernel
1696 that includes GENERIC then ensure that usb names are also changed over,
1697 eg uftdi -> usb2_serial_ftdi.
1699 Older programs linked against the ports libusb 0.1 need to be
1700 redirected to the new stack's libusb20. /etc/libmap.conf can
1702 # Map old usb library to new one for usb2 stack
1703 libusb-0.1.so.8 libusb20.so.1
1706 All USB ethernet devices now attach as interfaces under the name ueN
1707 (eg. ue0). This is to provide a predictable name as vendors often
1708 change usb chipsets in a product without notice.
1711 The ichsmb(4) driver has been changed to require SMBus slave
1712 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1713 All of the other SMBus controller drivers require left-justified
1714 slave addresses, so this change makes all the drivers provide the
1718 INET6 statistics (struct ip6stat) was updated.
1719 netstat(1) needs to be recompiled.
1722 NTFS has been removed from GENERIC kernel on amd64 to match
1723 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1724 will load ntfs.ko module automatically when NTFS support is
1725 actually needed, unless ntfs.ko is not installed or security
1726 level prohibits loading kernel modules. If either is the case,
1727 "options NTFS" has to be added into kernel config.
1730 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1731 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1732 800061. User space tools that rely on the size of struct tcpcb in
1733 tcp_var.h (e.g. sockstat) need to be recompiled.
1736 ng_tty(4) module updated to match the new TTY subsystem.
1737 Due to API change, user-level applications must be updated.
1738 New API support added to mpd5 CVS and expected to be present
1739 in next mpd5.3 release.
1742 With __FreeBSD_version 800060 the makefs tool is part of
1743 the base system (it was a port).
1746 The afdata and ifnet locks have been changed from mutexes to
1747 rwlocks, network modules will need to be re-compiled.
1750 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1751 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1752 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1753 architecture and 40 bytes on 64-bit architecture. The userland
1754 applications "arp" and "ndp" have been updated accordingly.
1755 The output from "netstat -r" shows only routing entries and
1756 none of the L2 information.
1759 __FreeBSD_version 800057 marks the switchover from the
1760 binary ath hal to source code. Users must add the line:
1762 options AH_SUPPORT_AR5416
1764 to their kernel config files when specifying:
1768 The ath_hal module no longer exists; the code is now compiled
1769 together with the driver in the ath module. It is now
1770 possible to tailor chip support (i.e. reduce the set of chips
1771 and thereby the code size); consult ath_hal(4) for details.
1774 __FreeBSD_version 800054 adds memory barriers to
1775 <machine/atomic.h>, new interfaces to ifnet to facilitate
1776 multiple hardware transmit queues for cards that support
1777 them, and a lock-less ring-buffer implementation to
1778 enable drivers to more efficiently manage queueing of
1782 A new version of ZFS (version 13) has been merged to -HEAD.
1783 This version has zpool attribute "listsnapshots" off by
1784 default, which means "zfs list" does not show snapshots,
1785 and is the same as Solaris behavior.
1788 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1791 The uhci, ohci, ehci and slhci USB Host controller drivers have
1792 been put into separate modules. If you load the usb module
1793 separately through loader.conf you will need to load the
1794 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1795 controller add the following to loader.conf:
1801 The ABI used by the PMC toolset has changed. Please keep
1802 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1806 atapci kernel module now includes only generic PCI ATA
1807 driver. AHCI driver moved to ataahci kernel module.
1808 All vendor-specific code moved into separate kernel modules:
1809 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1810 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1811 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1812 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1815 The TTY subsystem of the kernel has been replaced by a new
1816 implementation, which provides better scalability and an
1817 improved driver model. Most common drivers have been migrated to
1818 the new TTY subsystem, while others have not. The following
1819 drivers have not yet been ported to the new TTY layer:
1822 cy, digi, rc, rp, sio
1828 ng_h4, ng_tty, ppp, sl, snp
1830 Adding these drivers to your kernel configuration file shall
1831 cause compilation to fail.
1834 ntpd has been upgraded to 4.2.4p5.
1837 OpenSSH has been upgraded to 5.1p1.
1839 For many years, FreeBSD's version of OpenSSH preferred DSA
1840 over RSA for host and user authentication keys. With this
1841 upgrade, we've switched to the vendor's default of RSA over
1842 DSA. This may cause upgraded clients to warn about unknown
1843 host keys even for previously known hosts. Users should
1844 follow the usual procedure for verifying host keys before
1845 accepting the RSA key.
1847 This can be circumvented by setting the "HostKeyAlgorithms"
1848 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1851 Please note that the sequence of keys offered for
1852 authentication has been changed as well. You may want to
1853 specify IdentityFile in a different order to revert this
1857 The sio(4) driver has been removed from the i386 and amd64
1858 kernel configuration files. This means uart(4) is now the
1859 default serial port driver on those platforms as well.
1861 To prevent collisions with the sio(4) driver, the uart(4) driver
1862 uses different names for its device nodes. This means the
1863 onboard serial port will now most likely be called "ttyu0"
1864 instead of "ttyd0". You may need to reconfigure applications to
1865 use the new device names.
1867 When using the serial port as a boot console, be sure to update
1868 /boot/device.hints and /etc/ttys before booting the new kernel.
1869 If you forget to do so, you can still manually specify the hints
1870 at the loader prompt:
1872 set hint.uart.0.at="isa"
1873 set hint.uart.0.port="0x3F8"
1874 set hint.uart.0.flags="0x10"
1875 set hint.uart.0.irq="4"
1879 The gpt(8) utility has been removed. Use gpart(8) to partition
1883 The version that Linuxulator emulates was changed from 2.4.2
1884 to 2.6.16. If you experience any problems with Linux binaries
1885 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1886 if it fixes the problem contact emulation mailing list.
1889 ISDN4BSD (I4B) was removed from the src tree. You may need to
1890 update a your kernel configuration and remove relevant entries.
1893 I have checked in code to support multiple routing tables.
1894 See the man pages setfib(1) and setfib(2).
1895 This is a hopefully backwards compatible version,
1896 but to make use of it you need to compile your kernel
1897 with options ROUTETABLES=2 (or more up to 16).
1900 The 802.11 wireless support was redone to enable multi-bss
1901 operation on devices that are capable. The underlying device
1902 is no longer used directly but instead wlanX devices are
1903 cloned with ifconfig. This requires changes to rc.conf files.
1904 For example, change:
1905 ifconfig_ath0="WPA DHCP"
1908 ifconfig_wlan0="WPA DHCP"
1909 see rc.conf(5) for more details. In addition, mergemaster of
1910 /etc/rc.d is highly recommended. Simultaneous update of userland
1911 and kernel wouldn't hurt either.
1913 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1914 modules were merged into the base wlan module. All references
1915 to these modules (e.g. in kernel config files) must be removed.
1918 psm(4) has gained write(2) support in native operation level.
1919 Arbitrary commands can be written to /dev/psm%d and status can
1920 be read back from it. Therefore, an application is responsible
1921 for status validation and error recovery. It is a no-op in
1922 other operation levels.
1925 Support for KSE threading has been removed from the kernel. To
1926 run legacy applications linked against KSE libmap.conf may
1927 be used. The following libmap.conf may be used to ensure
1928 compatibility with any prior release:
1930 libpthread.so.1 libthr.so.1
1931 libpthread.so.2 libthr.so.2
1932 libkse.so.3 libthr.so.3
1935 The layout of struct vmspace has changed. This affects libkvm
1936 and any executables that link against libkvm and use the
1937 kvm_getprocs() function. In particular, but not exclusively,
1938 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1939 The effects are minimal, but it's advisable to upgrade world
1943 The latest em driver no longer has support in it for the
1944 82575 adapter, this is now moved to the igb driver. The
1945 split was done to make new features that are incompatible
1946 with older hardware easier to do.
1949 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1950 likewise the kernel option is now GEOM_LINUX_LVM.
1953 The default NFS mount mode has changed from UDP to TCP for
1954 increased reliability. If you rely on (insecurely) NFS
1955 mounting across a firewall you may need to update your
1959 Belatedly note the addition of m_collapse for compacting
1963 The fts(3) structures have been changed to use adequate
1964 integer types for their members and so to be able to cope
1965 with huge file trees. The old fts(3) ABI is preserved
1966 through symbol versioning in libc, so third-party binaries
1967 using fts(3) should still work, although they will not take
1968 advantage of the extended types. At the same time, some
1969 third-party software might fail to build after this change
1970 due to unportable assumptions made in its source code about
1971 fts(3) structure members. Such software should be fixed
1972 by its vendor or, in the worst case, in the ports tree.
1973 FreeBSD_version 800015 marks this change for the unlikely
1974 case that a portable fix is impossible.
1977 To upgrade to -current after this date, you must be running
1978 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1979 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1982 The ADAPTIVE_GIANT kernel option has been retired because its
1983 functionality is the default now.
1986 The AT keyboard emulation of sunkbd(4) has been turned on
1987 by default. In order to make the special symbols of the Sun
1988 keyboards driven by sunkbd(4) work under X these now have
1989 to be configured the same way as Sun USB keyboards driven
1990 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1992 Option "XkbLayout" "us"
1993 Option "XkbRules" "xorg"
1994 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1997 It has been decided that it is desirable to provide ABI
1998 backwards compatibility to the FreeBSD 4/5/6 versions of the
1999 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2000 broken with the introduction of PCI domain support (see the
2001 20070930 entry). Unfortunately, this required the ABI of
2002 PCIOCGETCONF to be broken again in order to be able to
2003 provide backwards compatibility to the old version of that
2004 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2005 again. As for prominent ports this affects neither pciutils
2006 nor xorg-server this time, the hal port needs to be rebuilt
2010 The misnamed kthread_create() and friends have been renamed
2011 to kproc_create() etc. Many of the callers already
2012 used kproc_start()..
2013 I will return kthread_create() and friends in a while
2014 with implementations that actually create threads, not procs.
2015 Renaming corresponds with version 800002.
2024 Avoid using make -j when upgrading. While generally safe, there are
2025 sometimes problems using -j to upgrade. If your upgrade fails with
2026 -j, please try again without -j. From time to time in the past there
2027 have been problems using -j with buildworld and/or installworld. This
2028 is especially true when upgrading between "distant" versions (eg one
2029 that cross a major release boundary or several minor releases, or when
2030 several months have passed on the -current branch).
2032 Sometimes, obscure build problems are the result of environment
2033 poisoning. This can happen because the make utility reads its
2034 environment when searching for values for global variables. To run
2035 your build attempts in an "environmental clean room", prefix all make
2036 commands with 'env -i '. See the env(1) manual page for more details.
2038 When upgrading from one major version to another it is generally best
2039 to upgrade to the latest code in the currently installed branch first,
2040 then do an upgrade to the new branch. This is the best-tested upgrade
2041 path, and has the highest probability of being successful. Please try
2042 this approach before reporting problems with a major version upgrade.
2044 When upgrading a live system, having a root shell around before
2045 installing anything can help undo problems. Not having a root shell
2046 around can lead to problems if pam has changed too much from your
2047 starting point to allow continued authentication after the upgrade.
2051 When upgrading the boot ZFS pool to a new version, always follow
2054 1.) recompile and reinstall the ZFS boot loader and boot block
2055 (this is part of "make buildworld" and "make installworld")
2057 2.) update the ZFS boot block on your boot drive
2059 The following example updates the ZFS boot block on the first
2060 partition (freebsd-boot) of a GPT partitioned drive ad0:
2061 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2063 Non-boot pools do not need these updates.
2067 If you are updating from a prior version of FreeBSD (even one just
2068 a few days old), you should follow this procedure. It is the most
2069 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2071 make kernel-toolchain
2072 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2073 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2075 To test a kernel once
2076 ---------------------
2077 If you just want to boot a kernel once (because you are not sure
2078 if it works, or if you want to boot a known bad kernel to provide
2079 debugging information) run
2080 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2081 nextboot -k testkernel
2083 To just build a kernel when you know that it won't mess you up
2084 --------------------------------------------------------------
2085 This assumes you are already running a CURRENT system. Replace
2086 ${arch} with the architecture of your machine (e.g. "i386",
2087 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2089 cd src/sys/${arch}/conf
2090 config KERNEL_NAME_HERE
2091 cd ../compile/KERNEL_NAME_HERE
2096 If this fails, go to the "To build a kernel" section.
2098 To rebuild everything and install it on the current system.
2099 -----------------------------------------------------------
2100 # Note: sometimes if you are running current you gotta do more than
2101 # is listed here if you are upgrading from a really old current.
2103 <make sure you have good level 0 dumps>
2105 make kernel KERNCONF=YOUR_KERNEL_HERE
2107 <reboot in single user> [3]
2114 To cross-install current onto a separate partition
2115 --------------------------------------------------
2116 # In this approach we use a separate partition to hold
2117 # current's root, 'usr', and 'var' directories. A partition
2118 # holding "/", "/usr" and "/var" should be about 2GB in
2121 <make sure you have good level 0 dumps>
2124 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2125 <maybe newfs current's root partition>
2126 <mount current's root partition on directory ${CURRENT_ROOT}>
2127 make installworld DESTDIR=${CURRENT_ROOT}
2128 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2129 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2130 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2131 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2132 <reboot into current>
2133 <do a "native" rebuild/install as described in the previous section>
2134 <maybe install compatibility libraries from ports/misc/compat*>
2138 To upgrade in-place from stable to current
2139 ----------------------------------------------
2140 <make sure you have good level 0 dumps>
2142 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2144 <reboot in single user> [3]
2151 Make sure that you've read the UPDATING file to understand the
2152 tweaks to various things you need. At this point in the life
2153 cycle of current, things change often and you are on your own
2154 to cope. The defaults can also change, so please read ALL of
2155 the UPDATING entries.
2157 Also, if you are tracking -current, you must be subscribed to
2158 freebsd-current@freebsd.org. Make sure that before you update
2159 your sources that you have read and understood all the recent
2160 messages there. If in doubt, please track -stable which has
2161 much fewer pitfalls.
2163 [1] If you have third party modules, such as vmware, you
2164 should disable them at this point so they don't crash your
2167 [3] From the bootblocks, boot -s, and then do
2172 adjkerntz -i # if CMOS is wall time
2173 Also, when doing a major release upgrade, it is required that
2174 you boot into single user mode to do the installworld.
2176 [4] Note: This step is non-optional. Failure to do this step
2177 can result in a significant reduction in the functionality of the
2178 system. Attempting to do it by hand is not recommended and those
2179 that pursue this avenue should read this file carefully, as well
2180 as the archives of freebsd-current and freebsd-hackers mailing lists
2181 for potential gotchas. The -U option is also useful to consider.
2182 See mergemaster(8) for more information.
2184 [5] Usually this step is a noop. However, from time to time
2185 you may need to do this if you get unknown user in the following
2186 step. It never hurts to do it all the time. You may need to
2187 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2188 install) after the buildworld before this step if you last updated
2189 from current before 20130425 or from -stable before 20130430.
2191 [6] This only deletes old files and directories. Old libraries
2192 can be deleted by "make delete-old-libs", but you have to make
2193 sure that no program is using those libraries anymore.
2195 [8] In order to have a kernel that can run the 4.x binaries needed to
2196 do an installworld, you must include the COMPAT_FREEBSD4 option in
2197 your kernel. Failure to do so may leave you with a system that is
2198 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2199 required to run the 5.x binaries on more recent kernels. And so on
2200 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2202 Make sure that you merge any new devices from GENERIC since the
2203 last time you updated your kernel config file.
2205 [9] When checking out sources, you must include the -P flag to have
2206 cvs prune empty directories.
2208 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2209 "?=" instead of the "=" assignment operator, so that buildworld can
2210 override the CPUTYPE if it needs to.
2212 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2213 not on the command line, or in /etc/make.conf. buildworld will
2214 warn if it is improperly defined.
2217 This file contains a list, in reverse chronological order, of major
2218 breakages in tracking -current. It is not guaranteed to be a complete
2219 list of such breakages, and only contains entries since October 10, 2007.
2220 If you need to see UPDATING entries from before that date, you will need
2221 to fetch an UPDATING file from an older FreeBSD release.
2223 Copyright information:
2225 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2227 Redistribution, publication, translation and use, with or without
2228 modification, in full or in part, in any form or format of this
2229 document are permitted without further permission from the author.
2231 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2232 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2233 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2234 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2235 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2236 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2237 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2238 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2239 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2240 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2241 POSSIBILITY OF SUCH DAMAGE.
2243 Contact Warner Losh if you have any questions about your use of