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