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 20150916: p3 FreeBSD-EN-15:16.pw
23 Fix regression in pw(8) when creating numeric users or groups.
26 Fix libc handling of signals for multi-threaded processes.
29 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
31 20150825: p2 FreeBSD-SA-15:22.openssh
33 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
35 Fix insufficient check of unsupported pkg(7) signature methods.
38 20150818: p1 FreeBSD-SA-15:20.expat
39 FreeBSD-EN-15:11.toolchain
40 FreeBSD-EN-15:12.netstat
41 FreeBSD-EN-15:13.vidcontrol
43 Fix multiple integer overflows in expat (libbsdxml) XML parser.
46 Fix make(1) syntax errors when upgrading from 9.x and earlier.
49 Fix incorrect netstat(1) data handling on 32-bit systems.
52 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
58 The default Unbound configuration now enables remote control
59 using a local socket. Users who have already enabled the
60 local_unbound service should regenerate their configuration
61 by running "service local_unbound setup" as root.
64 An additional fix for the issue described in the 20150614 sendmail
65 entry below has been been committed in revision 284786.
68 The fix for the issue described in the 20150614 sendmail entry
69 below has been been committed in revision 284485. The work
70 around described in that entry is no longer needed unless the
71 default setting is overridden by a confDH_PARAMETERS configuration
72 setting of '5' or pointing to a 512 bit DH parameter file.
75 The import of openssl to address the FreeBSD-SA-15:10.openssl
76 security advisory includes a change which rejects handshakes
77 with DH parameters below 768 bits. sendmail releases prior
78 to 8.15.2 (not yet released), defaulted to a 512 bit
79 DH parameter setting for client connections. To work around
80 this interoperability, sendmail can be configured to use a
81 2048 bit DH parameter by:
83 1. Edit /etc/mail/`hostname`.mc
84 2. If a setting for confDH_PARAMETERS does not exist or
85 exists and is set to a string beginning with '5',
87 3. If a setting for confDH_PARAMETERS exists and is set to
88 a file path, create a new file with:
89 openssl dhparam -out /path/to/file 2048
90 4. Rebuild the .cf file:
91 cd /etc/mail/; make; make install
93 cd /etc/mail/; make restart
95 A sendmail patch is coming, at which time this file will be
99 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
100 defined in symlink(7); previously symlinks were silently ignored.
103 The const qualifier has been removed from iconv(3) to comply with
104 POSIX. The ports tree is aware of this from r384038 onwards.
107 At svn r275807, The default linux compat kernel ABI has been adjusted
108 to 2.6.18 in support of the linux-c6 compat ports infrastructure
109 update. If you wish to continue using the linux-f10 compat ports,
110 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
111 encouraged to update their linux-compat packages to linux-c6 during
112 their next update cycle.
114 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
117 pjdfstest has been integrated into kyua as an opt-in test suite.
118 Please see share/doc/pjdfstest/README for a more details on how to
125 The ofwfb driver, used to provide a graphics console on PowerPC when
126 using vt(4), no longer allows mmap() of all of physical memory. This
127 will prevent Xorg on PowerPC with some ATI graphics cards from
128 initializing properly unless x11-servers/xorg-server is updated to
132 The libatf-c and libatf-c++ major versions were downgraded to 0 and
133 1 respectively to match the upstream numbers. They were out of
134 sync because, when they were originally added to FreeBSD, the
135 upstream versions were not respected. These libraries are private
136 and not yet built by default, so renumbering them should be a
137 non-issue. However, unclean source trees will yield broken test
138 programs once the operator executes "make delete-old-libs" after a
141 Additionally, the atf-sh binary was made private by moving it into
142 /usr/libexec/. Already-built shell test programs will keep the
143 path to the old binary so they will break after "make delete-old"
146 If you are using WITH_TESTS=yes (not the default), wipe the object
147 tree and rebuild from scratch to prevent spurious test failures.
148 This is only needed once: the misnumbered libraries and misplaced
149 binaries have been added to OptionalObsoleteFiles.inc so they will
150 be removed during a clean upgrade.
153 The ixgbe tunables now match their sysctl counterparts, for example:
154 hw.ixgbe.enable_aim => hw.ix.enable_aim
155 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
158 The NFSv4.1 server committed by r269398 changes the internal
159 function call interfaces used between the NFS and krpc modules.
160 As such, __FreeBSD_version was bumped.
163 The default unbound configuration has been modified to address
164 issues with reverse lookups on networks that use private
165 address ranges. If you use the local_unbound service, run
166 "service local_unbound setup" as root to regenerate your
167 configuration, then "service local_unbound reload" to load the
171 It is no longer necessary to include the dwarf version in your DEBUG
172 options in your kernel config file. The bug that required it to be
173 placed in the config file has bene fixed. DEBUG should now just
174 contain -g. The build system will automatically update things
175 to do the right thing.
178 Several ABI breaking changes were merged to CTL and new iSCSI code.
179 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
180 iscsictl need to be rebuilt to work with a new kernel.
183 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
184 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
185 which differs from the behaviour controlled by this knob.)
188 On i386 and amd64 systems, the onifconsole flag is now set by default
189 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
190 as a login TTY if it is set in the bootloader as an active kernel
191 console. No changes in behavior should result otherwise. To revert to
192 the previous behavior, set ttyu0 to "off" in /etc/ttys.
195 Clang and llvm have been upgraded to 3.4.1 release.
198 Clang and llvm have been upgraded to 3.4 release.
201 If a Makefile in a tests/ directory was auto-generating a Kyuafile
202 instead of providing an explicit one, this would prevent such
203 Makefile from providing its own Kyuafile in the future during
204 NO_CLEAN builds. This has been fixed in the Makefiles but manual
205 intervention is needed to clean an objdir if you use NO_CLEAN:
206 # find /usr/obj -name Kyuafile | xargs rm -f
209 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
210 capability mode support. Please note that enabling the feature in
211 kernel is still highly recommended.
214 OpenSSH is now built with sandbox support, and will use sandbox as
215 the default privilege separation method. This requires Capsicum
216 capability mode support in kernel.
219 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
220 been deprecated and will not be part of FreeBSD 11.0 and later
221 releases. If you use this driver, please consider switching to
222 the nfe(4) driver instead.
228 The behavior of gss_pseudo_random() for the krb5 mechanism
229 has changed, for applications requesting a longer random string
230 than produced by the underlying enctype's pseudo-random() function.
231 In particular, the random string produced from a session key of
232 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
233 be different at the 17th octet and later, after this change.
234 The counter used in the PRF+ construction is now encoded as a
235 big-endian integer in accordance with RFC 4402.
236 __FreeBSD_version is bumped to 1000701.
239 The WITHOUT_ATF build knob has been removed and its functionality
240 has been subsumed into the more generic WITHOUT_TESTS. If you were
241 using the former to disable the build of the ATF libraries, you
242 should change your settings to use the latter.
245 The default version of mtree is nmtree which is obtained from
246 NetBSD. The output is generally the same, but may vary
247 slightly. If you found you need identical output adding
248 "-F freebsd9" to the command line should do the trick. For the
249 time being, the old mtree is available as fmtree.
252 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
253 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
254 1.1.4_8 and verify bsdyml not linked in, before running "make
256 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
258 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
261 The rc.d/jail script has been updated to support jail(8)
262 configuration file. The "jail_<jname>_*" rc.conf(5) variables
263 for per-jail configuration are automatically converted to
264 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
265 This is transparently backward compatible. See below about some
266 incompatibilities and rc.conf(5) manual page for more details.
268 These variables are now deprecated in favor of jail(8) configuration
269 file. One can use "rc.d/jail config <jname>" command to generate
270 a jail(8) configuration file in /var/run/jail.<jname>.conf without
271 running the jail(8) utility. The default pathname of the
272 configuration file is /etc/jail.conf and can be specified by
273 using $jail_conf or $jail_<jname>_conf variables.
275 Please note that jail_devfs_ruleset accepts an integer at
276 this moment. Please consider to rewrite the ruleset name
280 BIND has been removed from the base system. If all you need
281 is a local resolver, simply enable and start the local_unbound
282 service instead. Otherwise, several versions of BIND are
283 available in the ports tree. The dns/bind99 port is one example.
285 With this change, nslookup(1) and dig(1) are no longer in the base
286 system. Users should instead use host(1) and drill(1) which are
287 in the base system. Alternatively, nslookup and dig can
288 be obtained by installing the dns/bind-tools port.
291 With the addition of unbound(8), a new unbound user is now
292 required during installworld. "mergemaster -p" can be used to
293 add the user prior to installworld, as documented in the handbook.
296 OpenSSH is now built with DNSSEC support, and will by default
297 silently trust signed SSHFP records. This can be controlled with
298 the VerifyHostKeyDNS client configuration setting. DNSSEC support
299 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
302 The GNU Compiler Collection and C++ standard library (libstdc++)
303 are no longer built by default on platforms where clang is the system
304 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
308 The PROCDESC kernel option is now part of the GENERIC kernel
309 configuration and is required for the rwhod(8) to work.
310 If you are using custom kernel configuration, you should include
314 The API and ABI related to the Capsicum framework was modified
315 in backward incompatible way. The userland libraries and programs
316 have to be recompiled to work with the new kernel. This includes the
317 following libraries and programs, but the whole buildworld is
318 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
319 kdump, procstat, rwho, rwhod, uniq.
322 AES-NI intrinsic support has been added to gcc. The AES-NI module
323 has been updated to use this support. A new gcc is required to build
324 the aesni module on both i386 and amd64.
327 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
328 Thus "device padlock_rng" and "device rdrand_rng" should be
329 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
332 WITH_ICONV has been split into two feature sets. WITH_ICONV now
333 enables just the iconv* functionality and is now on by default.
334 WITH_LIBICONV_COMPAT enables the libiconv api and link time
335 compatability. Set WITHOUT_ICONV to build the old way.
336 If you have been using WITH_ICONV before, you will very likely
337 need to turn on WITH_LIBICONV_COMPAT.
340 INVARIANTS option now enables DEBUG for code with OpenSolaris and
341 Illumos origin, including ZFS. If you have INVARIANTS in your
342 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
344 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
345 locks if WITNESS option was set. Because that generated a lot of
346 witness(9) reports and all of them were believed to be false
347 positives, this is no longer done. New option OPENSOLARIS_WITNESS
348 can be used to achieve the previous behavior.
351 Timer values in IPv6 data structures now use time_uptime instead
352 of time_second. Although this is not a user-visible functional
353 change, userland utilities which directly use them---ndp(8),
354 rtadvd(8), and rtsold(8) in the base system---need to be updated
358 find -delete can now delete the pathnames given as arguments,
359 instead of only files found below them or if the pathname did
360 not contain any slashes. Formerly, the following error message
363 find: -delete: <path>: relative path potentially not safe
365 Deleting the pathnames given as arguments can be prevented
366 without error messages using -mindepth 1 or by changing
367 directory and passing "." as argument to find. This works in the
368 old as well as the new version of find.
371 Behavior of devfs rules path matching has been changed.
372 Pattern is now always matched against fully qualified devfs
373 path and slash characters must be explicitly matched by
374 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
375 subdirectories must be reviewed.
378 The default ARM ABI has changed to the ARM EABI. The old ABI is
379 incompatible with the ARM EABI and all programs and modules will
380 need to be rebuilt to work with a new kernel.
382 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
384 NOTE: Support for the old ABI will be removed in the future and
385 users are advised to upgrade.
388 pkg_install has been disconnected from the build if you really need it
389 you should add WITH_PKGTOOLS in your src.conf(5).
392 Most of network statistics structures were changed to be able
393 keep 64-bits counters. Thus all tools, that work with networking
394 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
397 Fix targets that run multiple make's to use && rather than ;
398 so that subsequent steps depend on success of previous.
400 NOTE: if building 'universe' with -j* on stable/8 or stable/9
401 it would be better to start the build using bmake, to avoid
402 overloading the machine.
405 Fix a bug that allowed a tracing process (e.g. gdb) to write
406 to a memory-mapped file in the traced process's address space
407 even if neither the traced process nor the tracing process had
408 write access to that file.
411 CVS has been removed from the base system. An exact copy
412 of the code is available from the devel/cvs port.
415 Some people report the following error after the switch to bmake:
417 make: illegal option -- J
418 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
420 *** [buildworld] Error code 2
422 this likely due to an old instance of make in
423 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
424 which src/Makefile will use that blindly, if it exists, so if
425 you see the above error:
427 rm -rf `make -V MAKEPATH`
432 Use bmake by default.
433 Whereas before one could choose to build with bmake via
434 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
435 make. The goal is to remove these knobs for 10-RELEASE.
437 It is worth noting that bmake (like gmake) treats the command
438 line as the unit of failure, rather than statements within the
439 command line. Thus '(cd some/where && dosomething)' is safer
440 than 'cd some/where; dosomething'. The '()' allows consistent
441 behavior in parallel build.
444 Fix a bug that allows NFS clients to issue READDIR on files.
447 The WITHOUT_IDEA option has been removed because
448 the IDEA patent expired.
451 The sysctl which controls TRIM support under ZFS has been renamed
452 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
456 The mergemaster command now uses the default MAKEOBJDIRPREFIX
457 rather than creating it's own in the temporary directory in
458 order allow access to bootstrapped versions of tools such as
459 install and mtree. When upgrading from version of FreeBSD where
460 the install command does not support -l, you will need to
461 install a new mergemaster command if mergemaster -p is required.
462 This can be accomplished with the command (cd src/usr.sbin/mergemaster
466 Legacy ATA stack, disabled and replaced by new CAM-based one since
467 FreeBSD 9.0, completely removed from the sources. Kernel modules
468 atadisk and atapi*, user-level tools atacontrol and burncd are
469 removed. Kernel option `options ATA_CAM` is now permanently enabled
473 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
474 and socketpair(2). Software, in particular Kerberos, may
475 automatically detect and use these during building. The resulting
476 binaries will not work on older kernels.
479 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
480 information, see the respective 20130304 entry).
483 Recent commits to callout(9) changed the size of struct callout,
484 so the KBI is probably heavily disturbed. Also, some functions
485 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
486 by macros. Every kernel module using it won't load, so rebuild
489 The ctl device has been re-enabled in GENERIC for i386 and amd64,
490 but does not initialize by default (because of the new CTL_DISABLE
491 option) to save memory. To re-enable it, remove the CTL_DISABLE
492 option from the kernel config file or set kern.cam.ctl.disable=0
493 in /boot/loader.conf.
496 The ctl device has been disabled in GENERIC for i386 and amd64.
497 This was done due to the extra memory being allocated at system
498 initialisation time by the ctl driver which was only used if
499 a CAM target device was created. This makes a FreeBSD system
500 unusable on 128MB or less of RAM.
503 A new compression method (lz4) has been merged to -HEAD. Please
504 refer to zpool-features(7) for more information.
506 Please refer to the "ZFS notes" section of this file for information
507 on upgrading boot ZFS pools.
510 A BSD-licensed patch(1) variant has been added and is installed
511 as bsdpatch, being the GNU version the default patch.
512 To inverse the logic and use the BSD-licensed one as default,
513 while having the GNU version installed as gnupatch, rebuild
514 and install world with the WITH_BSD_PATCH knob set.
517 Due to the use of the new -l option to install(1) during build
518 and install, you must take care not to directly set the INSTALL
519 make variable in your /etc/make.conf, /etc/src.conf, or on the
520 command line. If you wish to use the -C flag for all installs
521 you may be able to add INSTALL+=-C to /etc/make.conf or
525 The install(1) option -M has changed meaning and now takes an
526 argument that is a file or path to append logs to. In the
527 unlikely event that -M was the last option on the command line
528 and the command line contained at least two files and a target
529 directory the first file will have logs appended to it. The -M
530 option served little practical purpose in the last decade so its
531 use is expected to be extremely rare.
534 After switching to Clang as the default compiler some users of ZFS
535 on i386 systems started to experience stack overflow kernel panics.
536 Please consider using 'options KSTACK_PAGES=4' in such configurations.
539 GEOM_LABEL now mangles label names read from file system metadata.
540 Mangling affect labels containing spaces, non-printable characters,
541 '%' or '"'. Device names in /etc/fstab and other places may need to
545 By default, only the 10 most recent kernel dumps will be saved. To
546 restore the previous behaviour (no limit on the number of kernel dumps
547 stored in the dump directory) add the following line to /etc/rc.conf:
552 With the addition of auditdistd(8), a new auditdistd user is now
553 required during installworld. "mergemaster -p" can be used to
554 add the user prior to installworld, as documented in the handbook.
557 The sin6_scope_id member variable in struct sockaddr_in6 is now
558 filled by the kernel before passing the structure to the userland via
559 sysctl or routing socket. This means the KAME-specific embedded scope
560 id in sin6_addr.s6_addr[2] is always cleared in userland application.
561 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
562 __FreeBSD_version is bumped to 1000025.
565 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
566 This means that the world and kernel will be compiled with clang
567 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
568 and /usr/bin/cpp. To disable this behavior and revert to building
569 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
570 of current may need to bootstrap WITHOUT_CLANG first if the clang
571 build fails (its compatibility window doesn't extend to the 9 stable
575 The IPFIREWALL_FORWARD kernel option has been removed. Its
576 functionality now turned on by default.
579 The ZERO_COPY_SOCKET kernel option has been removed and
580 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
581 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
582 mechanism which is not safe and may result in kernel crashes.
583 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
584 driver supports disposeable external page sized mbuf storage.
585 Proper replacements for both zero-copy mechanisms are under
586 consideration and will eventually lead to complete removal
587 of the two kernel options.
590 The IPv4 network stack has been converted to network byte
591 order. The following modules need to be recompiled together
592 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
593 pf(4), ipfw(4), ng_ipfw(4), stf(4).
596 Support for non-MPSAFE filesystems was removed from VFS. The
597 VFS_VERSION was bumped, all filesystem modules shall be
601 All the non-MPSAFE filesystems have been disconnected from
602 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
603 portalfs, smbfs, xfs.
606 The interface cloning API and ABI has changed. The following
607 modules need to be recompiled together with kernel:
608 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
609 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
610 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
613 The sdhci driver was split in two parts: sdhci (generic SD Host
614 Controller logic) and sdhci_pci (actual hardware driver).
615 No kernel config modifications are required, but if you
616 load sdhc as a module you must switch to sdhci_pci instead.
619 Import the FUSE kernel and userland support into base system.
622 The GNU sort(1) program has been removed since the BSD-licensed
623 sort(1) has been the default for quite some time and no serious
624 problems have been reported. The corresponding WITH_GNU_SORT
628 The pfil(9) API/ABI for AF_INET family has been changed. Packet
629 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
633 The net80211(4) ABI has been changed to allow for improved driver
634 PS-POLL and power-save support. All wireless drivers need to be
635 recompiled to work with the new kernel.
638 The random(4) support for the VIA hardware random number
639 generator (`PADLOCK') is no longer enabled unconditionally.
640 Add the padlock_rng device in the custom kernel config if
641 needed. The GENERIC kernels on i386 and amd64 do include the
642 device, so the change only affects the custom kernel
646 The pf(4) packet filter ABI has been changed. pfctl(8) and
647 snmp_pf module need to be recompiled to work with new kernel.
650 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
651 to -HEAD. Pools that have empty_bpobj in active state can not be
652 imported read-write with ZFS implementations that do not support
653 this feature. For more information read the zpool-features(5)
657 The sparc64 ZFS loader has been changed to no longer try to auto-
658 detect ZFS providers based on diskN aliases but now requires these
659 to be explicitly listed in the OFW boot-device environment variable.
662 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
663 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
664 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
667 The following sysctls and tunables have been renamed for consistency
668 with other variables:
669 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
670 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
673 The sort utility has been replaced with BSD sort. For now, GNU sort
674 is also available as "gnusort" or the default can be set back to
675 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
676 installed as "bsdsort".
679 A new version of ZFS (pool version 5000) has been merged to -HEAD.
680 Starting with this version the old system of ZFS pool versioning
681 is superseded by "feature flags". This concept enables forward
682 compatibility against certain future changes in functionality of ZFS
683 pools. The first read-only compatible "feature flag" for ZFS pools
684 is named "com.delphix:async_destroy". For more information
685 read the new zpool-features(5) manual page.
686 Please refer to the "ZFS notes" section of this file for information
687 on upgrading boot ZFS pools.
690 The malloc(3) implementation embedded in libc now uses sources imported
691 as contrib/jemalloc. The most disruptive API change is to
692 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
693 delete it prior to installworld, and optionally re-create it using the
694 new format after rebooting. See malloc.conf(5) for details
695 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
699 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
700 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
701 now spelled mips. This is to aid compatibility with third-party
702 software that expects this naming scheme in uname(3). Little-endian
703 settings are unchanged. If you are updating a big-endian mips64 machine
704 from before this change, you may need to set MACHINE_ARCH=mips64 in
705 your environment before the new build system will recognize your machine.
708 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
712 Now unix domain sockets behave "as expected" on nullfs(5). Previously
713 nullfs(5) did not pass through all behaviours to the underlying layer,
714 as a result if we bound to a socket on the lower layer we could connect
715 only to the lower path; if we bound to the upper layer we could connect
716 only to the upper path. The new behavior is one can connect to both the
717 lower and the upper paths regardless what layer path one binds to.
720 The getifaddrs upgrade path broken with 20111215 has been restored.
721 If you have upgraded in between 20111215 and 20120209 you need to
722 recompile libc again with your kernel. You still need to recompile
723 world to be able to configure CARP but this restriction already
727 The set_rcvar() function has been removed from /etc/rc.subr. All
728 base and ports rc.d scripts have been updated, so if you have a
729 port installed with a script in /usr/local/etc/rc.d you can either
730 hand-edit the rcvar= line, or reinstall the port.
732 An easy way to handle the mass-update of /etc/rc.d:
733 rm /etc/rc.d/* && mergemaster -i
736 panic(9) now stops other CPUs in the SMP systems, disables interrupts
737 on the current CPU and prevents other threads from running.
738 This behavior can be reverted using the kern.stop_scheduler_on_panic
740 The new behavior can be incompatible with kern.sync_on_panic.
743 The carp(4) facility has been changed significantly. Configuration
744 of the CARP protocol via ifconfig(8) has changed, as well as format
745 of CARP events submitted to devd(8) has changed. See manual pages
746 for more information. The arpbalance feature of carp(4) is currently
747 not supported anymore.
749 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
750 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
751 need to be recompiled.
754 The acpi_wmi(4) status device /dev/wmistat has been renamed to
758 The option VFS_ALLOW_NONMPSAFE option has been added in order to
759 explicitely support non-MPSAFE filesystems.
760 It is on by default for all supported platform at this present
764 The broken amd(4) driver has been replaced with esp(4) in the amd64,
765 i386 and pc98 GENERIC kernel configuration files.
768 sysinstall has been removed
771 The stable/9 branch created in subversion. This corresponds to the
772 RELENG_9 branch in CVS.
775 This commit modifies vfs_register() so that it uses a hash
776 calculation to set vfc_typenum, which is enabled by default.
777 The first time a system is booted after this change, the
778 vfc_typenum values will change for all file systems. The
779 main effect of this is a change to the NFS server file handles
780 for file systems that use vfc_typenum in their fsid, such as ZFS.
781 It will, however, prevent vfc_typenum from changing when file
782 systems are loaded in a different order for subsequent reboots.
783 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
784 until you are ready to remount all NFS clients after a reboot.
787 Bump the shared library version numbers for libraries that
788 do not use symbol versioning, have changed the ABI compared
789 to stable/8 and which shared library version was not bumped.
790 Done as part of 9.0-RELEASE cycle.
793 During the merge of Capsicum features, the fget(9) KPI was modified.
794 This may require the rebuilding of out-of-tree device drivers --
795 issues have been reported specifically with the nVidia device driver.
796 __FreeBSD_version is bumped to 900041.
798 Also, there is a period between 20110811 and 20110814 where the
799 special devices /dev/{stdin,stdout,stderr} did not work correctly.
800 Building world from a kernel during that window may not work.
803 The packet filter (pf) code has been updated to OpenBSD 4.5.
804 You need to update userland tools to be in sync with kernel.
805 This update breaks backward compatibility with earlier pfsync(4)
806 versions. Care must be taken when updating redundant firewall setups.
809 The following sysctls and tunables are retired on x86 platforms:
811 machdep.hlt_logical_cpus
812 The following sysctl is retired:
813 machdep.hyperthreading_allowed
814 The sysctls were supposed to provide a way to dynamically offline and
815 online selected CPUs on x86 platforms, but the implementation has not
816 been reliable especially with SCHED_ULE scheduler.
817 machdep.hyperthreading_allowed tunable is still available to ignore
818 hyperthreading CPUs at OS level.
819 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
820 where X is an APIC ID of a CPU. Be advised, though, that disabling
821 CPUs in non-uniform fashion will result in non-uniform topology and
822 may lead to sub-optimal system performance with SCHED_ULE, which is
826 cpumask_t type is retired and cpuset_t is used in order to describe
830 Changes to ifconfig(8) for dynamic address family detection mandate
831 that you are running a kernel of 20110525 or later. Make sure to
832 follow the update procedure to boot a new kernel before installing
836 Support for sun4v architecture is officially dropped
839 Several KPI breaking changes have been committed to the mii(4) layer,
840 the PHY drivers and consequently some Ethernet drivers using mii(4).
841 This means that miibus.ko and the modules of the affected Ethernet
842 drivers need to be recompiled.
844 Note to kernel developers: Given that the OUI bit reversion problem
845 was fixed as part of these changes all mii(4) commits related to OUIs,
846 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
847 handling, no longer can be merged verbatim to stable/8 and previous
851 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
852 into their kernel configurations along with 'device pci'.
855 The default NFS client is now the new NFS client, so fstype "newnfs"
856 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
857 Although mounts via fstype "nfs" will usually work without userland
858 changes, it is recommended that the mount(8) and mount_nfs(8)
859 commands be rebuilt from sources and that a link to mount_nfs called
860 mount_oldnfs be created. The new client is compiled into the
861 kernel with "options NFSCL" and this is needed for diskless root
862 file systems. The GENERIC kernel configs have been changed to use
863 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
864 To use the regular/old client, you can "mount -t oldnfs ...". For
865 a diskless root file system, you must also include a line like:
867 vfs.root.mountfrom="oldnfs:"
869 in the boot/loader.conf on the root fs on the NFS server to make
870 a diskless root fs use the old client.
873 The GENERIC kernels for all architectures now default to the new
874 CAM-based ATA stack. It means that all legacy ATA drivers were
875 removed and replaced by respective CAM drivers. If you are using
876 ATA device names in /etc/fstab or other places, make sure to update
877 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
878 where 'Y's are the sequential numbers starting from zero for each type
879 in order of detection, unless configured otherwise with tunables,
880 see cam(4)). There will be symbolic links created in /dev/ to map
881 old adX devices to the respective adaY. They should provide basic
882 compatibility for file systems mounting in most cases, but they do
883 not support old user-level APIs and do not have respective providers
884 in GEOM. Consider using updated management tools with new device names.
886 It is possible to load devices ahci, ata, siis and mvs as modules,
887 but option ATA_CAM should remain in kernel configuration to make ata
888 module work as CAM driver supporting legacy ATA controllers. Device ata
889 still can be used in modular fashion (atacore + ...). Modules atadisk
890 and atapi* are not used and won't affect operation in ATA_CAM mode.
891 Note that to use CAM-based ATA kernel should include CAM devices
892 scbus, pass, da (or explicitly ada), cd and optionally others. All of
893 them are parts of the cam module.
895 ataraid(4) functionality is now supported by the RAID GEOM class.
896 To use it you can load geom_raid kernel module and use graid(8) tool
897 for management. Instead of /dev/arX device names, use /dev/raid/rX.
899 No kernel config options or code have been removed, so if a problem
900 arises, please report it and optionally revert to the old ATA stack.
901 In order to do it you can remove from the kernel config:
906 , and instead add back:
907 device atadisk # ATA disk drives
908 device ataraid # ATA RAID drives
909 device atapicd # ATAPI CDROM drives
910 device atapifd # ATAPI floppy drives
911 device atapist # ATAPI tape drives
914 The default NFS server has been changed to the new server, which
915 was referred to as the experimental server. If you need to switch
916 back to the old NFS server, you must now put the "-o" option on
917 both the mountd and nfsd commands. This can be done using the
918 mountd_flags and nfs_server_flags rc.conf variables until an
919 update to the rc scripts is committed, which is coming soon.
922 The GNU Objective-C runtime library (libobjc), and other Objective-C
923 related components have been removed from the base system. If you
924 require an Objective-C library, please use one of the available ports.
927 ath(4) has been split into bus- and device- modules. if_ath contains
928 the HAL, the TX rate control and the network device code. if_ath_pci
929 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
930 contains the AHB glue. Users need to load both if_ath_pci and if_ath
931 in order to use ath on everything else.
933 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
934 need to load if_ath and if_ath_pci for ath(4) operation.
937 As part of the replacement of sysinstall, the process of building
938 release media has changed significantly. For details, please re-read
939 release(7), which has been updated to reflect the new build process.
942 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
943 is the last available version under GPLv2. It brings a number of new
944 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
945 4.1 and SSE 4.2), better support for powerpc64, a number of new
946 directives, and lots of other small improvements. See the ChangeLog
947 file in contrib/binutils for the full details.
950 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
951 compliant, and will now use half of hash for authentication.
952 This will break interoperability with all stacks (including all
953 actual FreeBSD versions) who implement
954 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
956 The only workaround with such peers is to use another HMAC
957 algorithm for IPsec ("phase 2") authentication.
960 Remove the uio_yield prototype and symbol. This function has
961 been misnamed since it was introduced and should not be
962 globally exposed with this name. The equivalent functionality
963 is now available using kern_yield(curthread->td_user_pri).
964 The function remains undocumented.
967 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
968 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
969 for scalar sysctls is defined but disabled. Code that needs
970 UQUAD to pass the type checking that must compile on older
971 systems where the define is not present can check against
972 __FreeBSD_version >= 900030.
974 The system dialog(1) has been replaced with a new version previously
975 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
976 with the previous version, but the libdialog associated with it has
977 a largely incompatible API. As such, the original version of libdialog
978 will be kept temporarily as libodialog, until its base system consumers
979 are replaced or updated. Bump __FreeBSD_version to 900030.
982 If you are trying to run make universe on a -stable system, and you get
983 the following warning:
984 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
985 unknown. config(8) likely too old."
986 or something similar to it, then you must upgrade your -stable system
987 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
988 stable/8) or build the config from the latest stable/8 branch and
989 install it on your system.
991 Prior to this date, building a current universe on 8-stable system from
992 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
993 error in the first kernel build phase. A new config on those old
994 systems will fix that problem for older versions of -current.
997 The TCP stack has been modified to allow Khelp modules to interact with
998 it via helper hook points and store per-connection data in the TCP
999 control block. Bump __FreeBSD_version to 900029. User space tools that
1000 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1004 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1005 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1006 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1007 to take advantage of it instead of using custom implementations. This
1008 means that these drivers now no longer unconditionally advertise
1009 support for flow control but only do so if flow control is a selected
1010 media option. This was implemented in the generic support that way in
1011 order to allow flow control to be switched on and off via ifconfig(8)
1012 with the PHY specific default to typically off in order to protect
1013 from unwanted effects. Consequently, if you used flow control with
1014 one of the above mentioned drivers you now need to explicitly enable
1015 it, for example via:
1016 ifconfig bge0 media auto mediaopt flowcontrol
1018 Along with the above mentioned changes generic support for setting
1019 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1020 e1000phy(4) as well as ip1000phy(4) have been converted to take
1021 advantage of it. This means that these drivers now no longer take the
1022 link0 parameter for selecting master mode but the master media option
1023 has to be used instead, for example like in the following:
1024 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1026 Selection of master mode now is also available with all other PHY
1027 drivers supporting 1000baseT.
1030 The TCP stack has received a significant update to add support for
1031 modularised congestion control and generally improve the clarity of
1032 congestion control decisions. Bump __FreeBSD_version to 900025. User
1033 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1034 sockstat) need to be recompiled.
1037 The man(1) utility has been replaced by a new version that no longer
1038 uses /etc/manpath.config. Please consult man.conf(5) for how to
1039 migrate local entries to the new format.
1042 The copyright strings printed by login(1) and sshd(8) at the time of a
1043 new connection have been removed to follow other operating systems and
1047 A workaround for a fixed ld bug has been removed in kernel code,
1048 so make sure that your system ld is built from sources after
1049 revision 210245 from 2010-07-19 (r211583 if building head kernel
1050 on stable/8, r211584 for stable/7; both from 2010-08-21).
1051 A symptom of incorrect ld version is different addresses for
1052 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1055 The $ipv6_prefer variable in rc.conf(5) has been split into
1056 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1058 The $ip6addrctl_policy is a variable to choose a pre-defined
1059 address selection policy set by ip6addrctl(8). A value
1060 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1063 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1064 flag (see an entry of 20090926) is set on an interface with no
1065 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1066 security reason. If you want IPv6 link-local address on all
1067 interfaces by default, set this to "YES".
1069 The old ipv6_prefer="YES" is equivalent to
1070 ipv6_activate_all_interfaces="YES" and
1071 ip6addrctl_policy="ipv6_prefer".
1074 DTrace has grown support for userland tracing. Due to this, DTrace is
1075 now i386 and amd64 only.
1076 dtruss(1) is now installed by default on those systems and a new
1077 kernel module is needed for userland tracing: fasttrap.
1078 No changes to your kernel config file are necessary to enable
1079 userland tracing, but you might consider adding 'STRIP=' and
1080 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1081 to have informative userland stack traces in DTrace (ustack).
1084 The acpi_aiboost(4) driver has been removed in favor of the new
1085 aibs(4) driver. You should update your kernel configuration file.
1088 BSD grep has been imported to the base system and it is built by
1089 default. It is completely BSD licensed, highly GNU-compatible, uses
1090 less memory than its GNU counterpart and has a small codebase.
1091 However, it is slower than its GNU counterpart, which is mostly
1092 noticeable for larger searches, for smaller ones it is measurable
1093 but not significant. The reason is complex, the most important factor
1094 is that we lack a modern and efficient regex library and GNU
1095 overcomes this by optimizing the searches internally. Future work
1096 on improving the regex performance is planned, for the meantime,
1097 users that need better performance, can build GNU grep instead by
1098 setting the WITH_GNU_GREP knob.
1101 Due to the import of powerpc64 support, all existing powerpc kernel
1102 configuration files must be updated with a machine directive like this:
1103 machine powerpc powerpc
1105 In addition, an updated config(8) is required to build powerpc kernels
1109 A new version of ZFS (version 15) has been merged to -HEAD.
1110 This version uses a python library for the following subcommands:
1111 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1112 For full functionality of these commands the following port must
1113 be installed: sysutils/py-zfs
1116 'vm_page's are now hashed by physical address to an array of mutexes.
1117 Currently this is only used to serialize access to hold_count. Over
1118 time the page queue mutex will be peeled away. This changes the size
1119 of pmap on every architecture. And requires all callers of vm_page_hold
1120 and vm_page_unhold to be updated.
1123 WITH_CTF can now be specified in src.conf (not recommended, there
1124 are some problems with static executables), make.conf (would also
1125 affect ports which do not use GNU make and do not override the
1126 compile targets) or in the kernel config (via "makeoptions
1128 When WITH_CTF was specified there before this was silently ignored,
1129 so make sure that WITH_CTF is not used in places which could lead
1130 to unwanted behavior.
1133 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1134 to allow 32-bit compatibility on non-x86 platforms. All kernel
1135 configurations on amd64 and ia64 platforms using these options must
1136 be modified accordingly.
1139 The utmp user accounting database has been replaced with utmpx,
1140 the user accounting interface standardized by POSIX.
1141 Unfortunately the semantics of utmp and utmpx don't match,
1142 making it practically impossible to support both interfaces.
1143 The user accounting database is used by tools like finger(1),
1144 last(1), talk(1), w(1) and ac(8).
1146 All applications in the base system use utmpx. This means only
1147 local binaries (e.g. from the ports tree) may still use these
1148 utmp database files. These applications must be rebuilt to make
1151 After the system has been upgraded, it is safe to remove the old
1152 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1153 assuming their contents is of no importance anymore. Old wtmp
1154 databases can only be used by last(1) and ac(8) after they have
1155 been converted to the new format using wtmpcvt(1).
1158 Introduce the kernel thread "deadlock resolver" (which can be enabled
1159 via the DEADLKRES option, see NOTES for more details) and the
1160 sleepq_type() function for sleepqueues.
1163 The rc.firewall and rc.firewall6 were unified, and
1164 rc.firewall6 and rc.d/ip6fw were removed.
1165 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1166 variables are obsoleted. Instead, the following new rc
1167 variables are added to rc.d/ipfw:
1169 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1170 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1171 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1173 The meanings correspond to the relevant IPv4 variables.
1179 The default terminal emulation for syscons(4) has been changed
1180 from cons25 to xterm on all platforms except pc98. This means
1181 that the /etc/ttys file needs to be updated to ensure correct
1182 operation of applications on the console.
1184 The terminal emulation style can be toggled per window by using
1185 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1186 options can be used to change the compile-time default back to
1189 To prevent graphical artifacts, make sure the TERM environment
1190 variable is set to match the terminal emulation that is being
1191 performed by syscons(4).
1194 The layout of the structure ieee80211req_scan_result has changed.
1195 Applications that require wireless scan results (e.g. ifconfig(8))
1196 from net80211 need to be recompiled.
1198 Applications such as wpa_supplicant(8) may require a full world
1199 build without using NO_CLEAN in order to get synchronized with the
1203 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1204 There's one kernel module for each firmware. Adding "device iwnfw"
1205 to the kernel configuration file means including all three firmware
1206 images inside the kernel. If you want to include just the one for
1207 your wireless card, use the devices iwn4965fw, iwn5000fw or
1211 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1212 into rc.d/netif. The changes are the following:
1214 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1215 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1216 Note that both variables need the "inet6" keyword at the head.
1218 Do not set $ipv6_network_interfaces manually if you do not
1219 understand what you are doing. It is not needed in most cases.
1221 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1224 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1225 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1227 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1228 all configured interfaces have "inet6 accept_rtadv" in the
1229 $ifconfig_IF_ipv6. These are for backward compatibility.
1231 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1232 functionality of interfaces with no corresponding
1233 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1234 and the default address selection policy of ip6addrctl(8)
1235 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1236 Note that if you want to configure IPv6 functionality on the
1237 disabled interfaces after boot, first you need to clear the flag by
1238 using ifconfig(8) like:
1240 ifconfig em0 inet6 -ifdisabled
1242 If YES, the default address selection policy is set as
1245 The default value of $ipv6_prefer is NO.
1247 4. If your system need to receive Router Advertisement messages,
1248 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1249 scripts automatically invoke rtsol(8) when the interface becomes
1250 UP. The Router Advertisement messages are used for SLAAC
1251 (State-Less Address AutoConfiguration).
1254 802.11s D3.03 support was committed. This is incompatible with the
1255 previous code, which was based on D3.0.
1258 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1259 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1260 control whether accepting Router Advertisement messages or not.
1261 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1262 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1263 The ifconfig(8) utility now supports these flags.
1266 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1267 mount(8) and -a option for df(1) to see them.
1270 The old tunable hw.bus.devctl_disable has been superseded by
1271 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1272 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1276 Remove the option STOP_NMI. The default action is now to use NMI only
1277 for KDB via the newly introduced function stop_cpus_hard() and
1278 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1281 The stable/8 branch created in subversion. This corresponds to the
1282 RELENG_8 branch in CVS.
1285 Bump the shared library version numbers for all libraries that do not
1286 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1287 __FreeBSD_version to 800105.
1290 Due to changes in the implementation of virtual network stack support,
1291 all network-related kernel modules must be recompiled. As this change
1292 breaks the ABI, bump __FreeBSD_version to 800104.
1295 The TOE interface to the TCP syncache has been modified to remove
1296 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1297 The cxgb driver is the only TOE consumer affected by this change, and
1298 needs to be recompiled along with the kernel. As this change breaks
1299 the ABI, bump __FreeBSD_version to 800103.
1302 Padding has been added to struct tcpcb, sackhint and tcpstat in
1303 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1304 maintaining the ABI. However, this change breaks the ABI, so bump
1305 __FreeBSD_version to 800102. User space tools that rely on the size of
1306 any of these structs (e.g. sockstat) need to be recompiled.
1309 The NFS_LEGACYRPC option has been removed along with the old kernel
1310 RPC implementation that this option selected. Kernel configurations
1311 may need to be adjusted.
1314 The network interface device nodes at /dev/net/<interface> have been
1315 removed. All ioctl operations can be performed the normal way using
1316 routing sockets. The kqueue functionality can generally be replaced
1317 with routing sockets.
1320 The documentation from the FreeBSD Documentation Project (Handbook,
1321 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1322 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1325 The ABI of various structures related to the SYSV IPC API have been
1326 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1327 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1331 Layout of struct vnet has changed as routing related variables were
1332 moved to their own Vimage module. Modules need to be recompiled. Bump
1333 __FreeBSD_version to 800099.
1336 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1337 respectively. As long as no more than 16 groups per process are used,
1338 no changes should be visible. When more than 16 groups are used, old
1339 binaries may fail if they call getgroups() or getgrouplist() with
1340 statically sized storage. Recompiling will work around this, but
1341 applications should be modified to use dynamically allocated storage
1342 for group arrays as POSIX.1-2008 does not cap an implementation's
1343 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1345 NFS and portalfs mounts may also be affected as the list of groups is
1346 truncated to 16. Users of NFS who use more than 16 groups, should
1347 take care that negative group permissions are not used on the exported
1348 file systems as they will not be reliable unless a GSSAPI based
1349 authentication method is used.
1352 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1353 option compiles in the support for adaptive spinning for lockmgrs
1354 which want to enable it. The lockinit() function now accepts the flag
1355 LK_ADAPTIVE in order to make the lock object subject to adaptive
1356 spinning when both held in write and read mode.
1359 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1360 changed. User applications that use this ioctl need to be rebuilt.
1363 The layout of struct thread has changed. Kernel and modules need to
1367 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1368 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1371 window(1) has been removed from the base system. It can now be
1372 installed from ports. The port is called misc/window.
1375 The way we are storing and accessing `routing table' entries has
1376 changed. Programs reading the FIB, like netstat, need to be
1380 A new netisr implementation has been added for FreeBSD 8. Network
1381 file system modules, such as igmp, ipdivert, and others, should be
1383 Bump __FreeBSD_version to 800096.
1386 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1390 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1391 Bump __FreeBSD_version to 800094.
1394 Add mnt_xflag field to 'struct mount'. File system modules need to be
1396 Bump __FreeBSD_version to 800093.
1399 The compiling option ADAPTIVE_SX has been retired while it has been
1400 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1401 The KPI for sx_init_flags() changes as accepting flags:
1402 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1403 been introduced in order to handle the reversed logic.
1404 Bump __FreeBSD_version to 800092.
1407 Add support for hierarchical jails. Remove global securelevel.
1408 Bump __FreeBSD_version to 800091.
1411 The layout of struct vnet_net has changed, therefore modules
1413 Bump __FreeBSD_version to 800090.
1416 The newly imported zic(8) produces a new format in the output. Please
1417 run tzsetup(8) to install the newly created data to /etc/localtime.
1420 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1421 hw.usb.* and is now consistent again with previous releases.
1424 802.11 monitor mode support was revised and driver api's were changed.
1425 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1426 of DLT_IEEE802_11. No user-visible data structures were changed but
1427 applications that use DLT_IEEE802_11 may require changes.
1428 Bump __FreeBSD_version to 800088.
1431 The layout of the following structs has changed: sysctl_oid,
1432 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1433 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1434 panics may be experienced. World rebuild is required for
1435 correctly checking networking state from userland.
1436 Bump __FreeBSD_version to 800085.
1439 MLDv2 and Source-Specific Multicast (SSM) have been merged
1440 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1441 The implementation of SSM within FreeBSD's IPv6 stack closely
1442 follows the IPv4 implementation.
1444 For kernel developers:
1446 * The most important changes are that the ip6_output() and
1447 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1448 and this lock has been downgraded to a non-recursive mutex.
1450 * As with the changes to the IPv4 stack to support SSM, filtering
1451 of inbound multicast traffic must now be performed by transport
1452 protocols within the IPv6 stack. This does not apply to TCP and
1453 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1455 * The KPIs used by IPv6 multicast are similar to those used by
1456 the IPv4 stack, with the following differences:
1457 * im6o_mc_filter() is analogous to imo_multicast_filter().
1458 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1459 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1460 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1461 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1462 for MLDv1 have an additional 'timer' argument which is used to
1463 jitter the initial membership report for the solicited-node
1464 multicast membership on-link.
1465 * This is not strictly needed for MLDv2, which already jitters
1466 its report transmissions. However, the 'timer' argument is
1467 preserved in case MLDv1 is active on the interface.
1469 * The KAME linked-list based IPv6 membership implementation has
1470 been refactored to use a vector similar to that used by the IPv4
1472 Code which maintains a list of its own multicast memberships
1473 internally, e.g. carp, has been updated to reflect the new
1476 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1477 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1478 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1479 implementation constraint which needs to be addressed in HEAD.
1481 For application developers:
1483 * The changes are broadly similar to those made for the IPv4
1486 * The use of IPv4 and IPv6 multicast socket options on the same
1487 socket, using mapped addresses, HAS NOT been tested or supported.
1489 * There are a number of issues with the implementation of various
1490 IPv6 multicast APIs which need to be resolved in the API surface
1491 before the implementation is fully compatible with KAME userland
1492 use, and these are mostly to do with interface index treatment.
1494 * The literature available discusses the use of either the delta / ASM
1495 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1496 using setsourcefilter(3)/getsourcefilter(3). For more information
1497 please refer to RFC 3768, 'Socket Interface Extensions for
1498 Multicast Source Filters'.
1500 * Applications which use the published RFC 3678 APIs should be fine.
1502 For systems administrators:
1504 * The mtest(8) utility has been refactored to support IPv6, in
1505 addition to IPv4. Interface addresses are no longer accepted
1506 as arguments, their names must be used instead. The utility
1507 will map the interface name to its first IPv4 address as
1508 returned by getifaddrs(3).
1510 * The ifmcstat(8) utility has also been updated to print the MLDv2
1511 endpoint state and source filter lists via sysctl(3).
1513 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1514 loopback of IPv6 multicast datagrams by default; it defaults to 1
1515 to preserve the existing behaviour. Disabling multicast loopback is
1516 recommended for optimal system performance.
1518 * The IPv6 MROUTING code has been changed to examine this sysctl
1519 instead of attempting to perform a group lookup before looping
1520 back forwarded datagrams.
1522 Bump __FreeBSD_version to 800084.
1525 Implement low-level Bluetooth HCI API.
1526 Bump __FreeBSD_version to 800083.
1529 The layout of struct malloc_type, used by modules to register new
1530 memory allocation types, has changed. Most modules will need to
1531 be rebuilt or panics may be experienced.
1532 Bump __FreeBSD_version to 800081.
1535 Anticipate overflowing inp_flags - add inp_flags2.
1536 This changes most offsets in inpcb, so checking v4 connection
1537 state will require a world rebuild.
1538 Bump __FreeBSD_version to 800080.
1541 Add an llentry to struct route and struct route_in6. Modules
1542 embedding a struct route will need to be recompiled.
1543 Bump __FreeBSD_version to 800079.
1546 The size of rt_metrics_lite and by extension rtentry has changed.
1547 Networking administration apps will need to be recompiled.
1548 The route command now supports show as an alias for get, weighting
1549 of routes, sticky and nostick flags to alter the behavior of stateful
1551 Bump __FreeBSD_version to 800078.
1554 Do not use Giant for kbdmux(4) locking. This is wrong and
1555 apparently causing more problems than it solves. This will
1556 re-open the issue where interrupt handlers may race with
1557 kbdmux(4) in polling mode. Typical symptoms include (but
1558 not limited to) duplicated and/or missing characters when
1559 low level console functions (such as gets) are used while
1560 interrupts are enabled (for example geli password prompt,
1561 mountroot prompt etc.). Disabling kbdmux(4) may help.
1564 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1565 kernel modules referencing any of the above need to be recompiled.
1566 Bump __FreeBSD_version to 800075.
1569 GEOM_PART has become the default partition slicer for storage devices,
1570 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1571 introduces some changes:
1573 MSDOS/EBR: the devices created from MSDOS extended partition entries
1574 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1575 to devices with offset-based names. fstabs may need to be modified.
1577 BSD: the "geometry does not match label" warning is harmless in most
1578 cases but it points to problems in file system misalignment with
1579 disk geometry. The "c" partition is now implicit, covers the whole
1580 top-level drive and cannot be (mis)used by users.
1582 General: Kernel dumps are now not allowed to be written to devices
1583 whose partition types indicate they are meant to be used for file
1584 systems (or, in case of MSDOS partitions, as something else than
1587 Most of these changes date approximately from 200812.
1590 The uscanner(4) driver has been removed from the kernel. This follows
1591 Linux removing theirs in 2.6 and making libusb the default interface
1592 (supported by sane).
1595 The multicast forwarding code has been cleaned up. netstat(1)
1596 only relies on KVM now for printing bandwidth upcall meters.
1597 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1598 ip6_mroute_mod respectively. The config(5) options for statically
1599 compiling this code remain the same, i.e. 'options MROUTING'.
1602 Support for the IFF_NEEDSGIANT network interface flag has been
1603 removed, which means that non-MPSAFE network device drivers are no
1604 longer supported. In particular, if_ar, if_sr, and network device
1605 drivers from the old (legacy) USB stack can no longer be built or
1609 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1610 a bunch of new language catalog files have also been added.
1611 This means that some common libc messages are now localized and
1612 they depend on the LC_MESSAGES environmental variable.
1615 The k8temp(4) driver has been renamed to amdtemp(4) since
1616 support for Family 10 and Family 11 CPU families was added.
1619 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1620 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1622 For kernel developers, the most important changes are that the
1623 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1624 and this lock has been downgraded to a non-recursive mutex.
1626 Transport protocols (UDP, Raw IP) are now responsible for filtering
1627 inbound multicast traffic according to group membership and source
1628 filters. The imo_multicast_filter() KPI exists for this purpose.
1629 Transports which do not use multicast (SCTP, TCP) already reject
1630 multicast by default. Forwarding and receive performance may improve
1631 as a mutex acquisition is no longer needed in the ip_input()
1632 low-level input path. in_addmulti() and in_delmulti() are shimmed
1633 to new KPIs which exist to support SSM in-kernel.
1635 For application developers, it is recommended that loopback of
1636 multicast datagrams be disabled for best performance, as this
1637 will still cause the lock to be taken for each looped-back
1638 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1639 be tuned to 0 to disable loopback by default; it defaults to 1
1640 to preserve the existing behaviour.
1642 For systems administrators, to obtain best performance with
1643 multicast reception and multiple groups, it is always recommended
1644 that a card with a suitably precise hash filter is used. Hash
1645 collisions will still result in the lock being taken within the
1646 transport protocol input path to check group membership.
1648 If deploying FreeBSD in an environment with IGMP snooping switches,
1649 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1650 enabled; this forces 224.0.0.0/24 group membership to be announced
1653 The size of 'struct igmpstat' has changed; netstat needs to be
1654 recompiled to reflect this.
1655 Bump __FreeBSD_version to 800070.
1658 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1659 updated to use it. This requires a buildworld/installworld in order to
1660 update the library and dependencies (usbconfig, etc). Its advisable to
1661 rebuild all ports which uses libusb. More specific directions are given
1662 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1663 libusb are no longer required and can be removed.
1666 A workaround is committed to allow the creation of System V shared
1667 memory segment of size > 2 GB on the 64-bit architectures.
1668 Due to a limitation of the existing ABI, the shm_segsz member
1669 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1670 wrong for large segments. Note that limits must be explicitly
1671 raised to allow such segments to be created.
1674 The layout of struct ifnet has changed, requiring a rebuild of all
1675 network device driver modules.
1678 The /dev handling for the new USB stack has changed, a
1679 buildworld/installworld is required for libusb20.
1682 The new USB2 stack has now been permanently moved in and all kernel and
1683 module names reverted to their previous values (eg, usb, ehci, ohci,
1684 ums, ...). The old usb stack can be compiled in by prefixing the name
1685 with the letter 'o', the old usb modules have been removed.
1686 Updating entry 20090216 for xorg and 20090215 for libmap may still
1690 The rc.conf(5) option if_up_delay has been renamed to
1691 defaultroute_delay to better reflect its purpose. If you have
1692 customized this setting in /etc/rc.conf you need to update it to
1696 xorg 7.4 wants to configure its input devices via hald which does not
1697 yet work with USB2. If the keyboard/mouse does not work in xorg then
1699 Option "AllowEmptyInput" "off"
1700 to your ServerLayout section. This will cause X to use the configured
1701 kbd and mouse sections from your xorg.conf.
1704 The GENERIC kernels for all architectures now default to the new USB2
1705 stack. No kernel config options or code have been removed so if a
1706 problem arises please report it and optionally revert to the old USB
1707 stack. If you are loading USB kernel modules or have a custom kernel
1708 that includes GENERIC then ensure that usb names are also changed over,
1709 eg uftdi -> usb2_serial_ftdi.
1711 Older programs linked against the ports libusb 0.1 need to be
1712 redirected to the new stack's libusb20. /etc/libmap.conf can
1714 # Map old usb library to new one for usb2 stack
1715 libusb-0.1.so.8 libusb20.so.1
1718 All USB ethernet devices now attach as interfaces under the name ueN
1719 (eg. ue0). This is to provide a predictable name as vendors often
1720 change usb chipsets in a product without notice.
1723 The ichsmb(4) driver has been changed to require SMBus slave
1724 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1725 All of the other SMBus controller drivers require left-justified
1726 slave addresses, so this change makes all the drivers provide the
1730 INET6 statistics (struct ip6stat) was updated.
1731 netstat(1) needs to be recompiled.
1734 NTFS has been removed from GENERIC kernel on amd64 to match
1735 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1736 will load ntfs.ko module automatically when NTFS support is
1737 actually needed, unless ntfs.ko is not installed or security
1738 level prohibits loading kernel modules. If either is the case,
1739 "options NTFS" has to be added into kernel config.
1742 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1743 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1744 800061. User space tools that rely on the size of struct tcpcb in
1745 tcp_var.h (e.g. sockstat) need to be recompiled.
1748 ng_tty(4) module updated to match the new TTY subsystem.
1749 Due to API change, user-level applications must be updated.
1750 New API support added to mpd5 CVS and expected to be present
1751 in next mpd5.3 release.
1754 With __FreeBSD_version 800060 the makefs tool is part of
1755 the base system (it was a port).
1758 The afdata and ifnet locks have been changed from mutexes to
1759 rwlocks, network modules will need to be re-compiled.
1762 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1763 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1764 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1765 architecture and 40 bytes on 64-bit architecture. The userland
1766 applications "arp" and "ndp" have been updated accordingly.
1767 The output from "netstat -r" shows only routing entries and
1768 none of the L2 information.
1771 __FreeBSD_version 800057 marks the switchover from the
1772 binary ath hal to source code. Users must add the line:
1774 options AH_SUPPORT_AR5416
1776 to their kernel config files when specifying:
1780 The ath_hal module no longer exists; the code is now compiled
1781 together with the driver in the ath module. It is now
1782 possible to tailor chip support (i.e. reduce the set of chips
1783 and thereby the code size); consult ath_hal(4) for details.
1786 __FreeBSD_version 800054 adds memory barriers to
1787 <machine/atomic.h>, new interfaces to ifnet to facilitate
1788 multiple hardware transmit queues for cards that support
1789 them, and a lock-less ring-buffer implementation to
1790 enable drivers to more efficiently manage queueing of
1794 A new version of ZFS (version 13) has been merged to -HEAD.
1795 This version has zpool attribute "listsnapshots" off by
1796 default, which means "zfs list" does not show snapshots,
1797 and is the same as Solaris behavior.
1800 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1803 The uhci, ohci, ehci and slhci USB Host controller drivers have
1804 been put into separate modules. If you load the usb module
1805 separately through loader.conf you will need to load the
1806 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1807 controller add the following to loader.conf:
1813 The ABI used by the PMC toolset has changed. Please keep
1814 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1818 atapci kernel module now includes only generic PCI ATA
1819 driver. AHCI driver moved to ataahci kernel module.
1820 All vendor-specific code moved into separate kernel modules:
1821 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1822 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1823 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1824 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1827 The TTY subsystem of the kernel has been replaced by a new
1828 implementation, which provides better scalability and an
1829 improved driver model. Most common drivers have been migrated to
1830 the new TTY subsystem, while others have not. The following
1831 drivers have not yet been ported to the new TTY layer:
1834 cy, digi, rc, rp, sio
1840 ng_h4, ng_tty, ppp, sl, snp
1842 Adding these drivers to your kernel configuration file shall
1843 cause compilation to fail.
1846 ntpd has been upgraded to 4.2.4p5.
1849 OpenSSH has been upgraded to 5.1p1.
1851 For many years, FreeBSD's version of OpenSSH preferred DSA
1852 over RSA for host and user authentication keys. With this
1853 upgrade, we've switched to the vendor's default of RSA over
1854 DSA. This may cause upgraded clients to warn about unknown
1855 host keys even for previously known hosts. Users should
1856 follow the usual procedure for verifying host keys before
1857 accepting the RSA key.
1859 This can be circumvented by setting the "HostKeyAlgorithms"
1860 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1863 Please note that the sequence of keys offered for
1864 authentication has been changed as well. You may want to
1865 specify IdentityFile in a different order to revert this
1869 The sio(4) driver has been removed from the i386 and amd64
1870 kernel configuration files. This means uart(4) is now the
1871 default serial port driver on those platforms as well.
1873 To prevent collisions with the sio(4) driver, the uart(4) driver
1874 uses different names for its device nodes. This means the
1875 onboard serial port will now most likely be called "ttyu0"
1876 instead of "ttyd0". You may need to reconfigure applications to
1877 use the new device names.
1879 When using the serial port as a boot console, be sure to update
1880 /boot/device.hints and /etc/ttys before booting the new kernel.
1881 If you forget to do so, you can still manually specify the hints
1882 at the loader prompt:
1884 set hint.uart.0.at="isa"
1885 set hint.uart.0.port="0x3F8"
1886 set hint.uart.0.flags="0x10"
1887 set hint.uart.0.irq="4"
1891 The gpt(8) utility has been removed. Use gpart(8) to partition
1895 The version that Linuxulator emulates was changed from 2.4.2
1896 to 2.6.16. If you experience any problems with Linux binaries
1897 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1898 if it fixes the problem contact emulation mailing list.
1901 ISDN4BSD (I4B) was removed from the src tree. You may need to
1902 update a your kernel configuration and remove relevant entries.
1905 I have checked in code to support multiple routing tables.
1906 See the man pages setfib(1) and setfib(2).
1907 This is a hopefully backwards compatible version,
1908 but to make use of it you need to compile your kernel
1909 with options ROUTETABLES=2 (or more up to 16).
1912 The 802.11 wireless support was redone to enable multi-bss
1913 operation on devices that are capable. The underlying device
1914 is no longer used directly but instead wlanX devices are
1915 cloned with ifconfig. This requires changes to rc.conf files.
1916 For example, change:
1917 ifconfig_ath0="WPA DHCP"
1920 ifconfig_wlan0="WPA DHCP"
1921 see rc.conf(5) for more details. In addition, mergemaster of
1922 /etc/rc.d is highly recommended. Simultaneous update of userland
1923 and kernel wouldn't hurt either.
1925 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1926 modules were merged into the base wlan module. All references
1927 to these modules (e.g. in kernel config files) must be removed.
1930 psm(4) has gained write(2) support in native operation level.
1931 Arbitrary commands can be written to /dev/psm%d and status can
1932 be read back from it. Therefore, an application is responsible
1933 for status validation and error recovery. It is a no-op in
1934 other operation levels.
1937 Support for KSE threading has been removed from the kernel. To
1938 run legacy applications linked against KSE libmap.conf may
1939 be used. The following libmap.conf may be used to ensure
1940 compatibility with any prior release:
1942 libpthread.so.1 libthr.so.1
1943 libpthread.so.2 libthr.so.2
1944 libkse.so.3 libthr.so.3
1947 The layout of struct vmspace has changed. This affects libkvm
1948 and any executables that link against libkvm and use the
1949 kvm_getprocs() function. In particular, but not exclusively,
1950 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1951 The effects are minimal, but it's advisable to upgrade world
1955 The latest em driver no longer has support in it for the
1956 82575 adapter, this is now moved to the igb driver. The
1957 split was done to make new features that are incompatible
1958 with older hardware easier to do.
1961 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1962 likewise the kernel option is now GEOM_LINUX_LVM.
1965 The default NFS mount mode has changed from UDP to TCP for
1966 increased reliability. If you rely on (insecurely) NFS
1967 mounting across a firewall you may need to update your
1971 Belatedly note the addition of m_collapse for compacting
1975 The fts(3) structures have been changed to use adequate
1976 integer types for their members and so to be able to cope
1977 with huge file trees. The old fts(3) ABI is preserved
1978 through symbol versioning in libc, so third-party binaries
1979 using fts(3) should still work, although they will not take
1980 advantage of the extended types. At the same time, some
1981 third-party software might fail to build after this change
1982 due to unportable assumptions made in its source code about
1983 fts(3) structure members. Such software should be fixed
1984 by its vendor or, in the worst case, in the ports tree.
1985 FreeBSD_version 800015 marks this change for the unlikely
1986 case that a portable fix is impossible.
1989 To upgrade to -current after this date, you must be running
1990 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1991 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1994 The ADAPTIVE_GIANT kernel option has been retired because its
1995 functionality is the default now.
1998 The AT keyboard emulation of sunkbd(4) has been turned on
1999 by default. In order to make the special symbols of the Sun
2000 keyboards driven by sunkbd(4) work under X these now have
2001 to be configured the same way as Sun USB keyboards driven
2002 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2004 Option "XkbLayout" "us"
2005 Option "XkbRules" "xorg"
2006 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2009 It has been decided that it is desirable to provide ABI
2010 backwards compatibility to the FreeBSD 4/5/6 versions of the
2011 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2012 broken with the introduction of PCI domain support (see the
2013 20070930 entry). Unfortunately, this required the ABI of
2014 PCIOCGETCONF to be broken again in order to be able to
2015 provide backwards compatibility to the old version of that
2016 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2017 again. As for prominent ports this affects neither pciutils
2018 nor xorg-server this time, the hal port needs to be rebuilt
2022 The misnamed kthread_create() and friends have been renamed
2023 to kproc_create() etc. Many of the callers already
2024 used kproc_start()..
2025 I will return kthread_create() and friends in a while
2026 with implementations that actually create threads, not procs.
2027 Renaming corresponds with version 800002.
2036 Avoid using make -j when upgrading. While generally safe, there are
2037 sometimes problems using -j to upgrade. If your upgrade fails with
2038 -j, please try again without -j. From time to time in the past there
2039 have been problems using -j with buildworld and/or installworld. This
2040 is especially true when upgrading between "distant" versions (eg one
2041 that cross a major release boundary or several minor releases, or when
2042 several months have passed on the -current branch).
2044 Sometimes, obscure build problems are the result of environment
2045 poisoning. This can happen because the make utility reads its
2046 environment when searching for values for global variables. To run
2047 your build attempts in an "environmental clean room", prefix all make
2048 commands with 'env -i '. See the env(1) manual page for more details.
2050 When upgrading from one major version to another it is generally best
2051 to upgrade to the latest code in the currently installed branch first,
2052 then do an upgrade to the new branch. This is the best-tested upgrade
2053 path, and has the highest probability of being successful. Please try
2054 this approach before reporting problems with a major version upgrade.
2056 When upgrading a live system, having a root shell around before
2057 installing anything can help undo problems. Not having a root shell
2058 around can lead to problems if pam has changed too much from your
2059 starting point to allow continued authentication after the upgrade.
2063 When upgrading the boot ZFS pool to a new version, always follow
2066 1.) recompile and reinstall the ZFS boot loader and boot block
2067 (this is part of "make buildworld" and "make installworld")
2069 2.) update the ZFS boot block on your boot drive
2071 The following example updates the ZFS boot block on the first
2072 partition (freebsd-boot) of a GPT partitioned drive ad0:
2073 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2075 Non-boot pools do not need these updates.
2079 If you are updating from a prior version of FreeBSD (even one just
2080 a few days old), you should follow this procedure. It is the most
2081 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2083 make kernel-toolchain
2084 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2085 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2087 To test a kernel once
2088 ---------------------
2089 If you just want to boot a kernel once (because you are not sure
2090 if it works, or if you want to boot a known bad kernel to provide
2091 debugging information) run
2092 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2093 nextboot -k testkernel
2095 To just build a kernel when you know that it won't mess you up
2096 --------------------------------------------------------------
2097 This assumes you are already running a CURRENT system. Replace
2098 ${arch} with the architecture of your machine (e.g. "i386",
2099 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2101 cd src/sys/${arch}/conf
2102 config KERNEL_NAME_HERE
2103 cd ../compile/KERNEL_NAME_HERE
2108 If this fails, go to the "To build a kernel" section.
2110 To rebuild everything and install it on the current system.
2111 -----------------------------------------------------------
2112 # Note: sometimes if you are running current you gotta do more than
2113 # is listed here if you are upgrading from a really old current.
2115 <make sure you have good level 0 dumps>
2117 make kernel KERNCONF=YOUR_KERNEL_HERE
2119 <reboot in single user> [3]
2126 To cross-install current onto a separate partition
2127 --------------------------------------------------
2128 # In this approach we use a separate partition to hold
2129 # current's root, 'usr', and 'var' directories. A partition
2130 # holding "/", "/usr" and "/var" should be about 2GB in
2133 <make sure you have good level 0 dumps>
2136 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2137 <maybe newfs current's root partition>
2138 <mount current's root partition on directory ${CURRENT_ROOT}>
2139 make installworld DESTDIR=${CURRENT_ROOT}
2140 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2141 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2142 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2143 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2144 <reboot into current>
2145 <do a "native" rebuild/install as described in the previous section>
2146 <maybe install compatibility libraries from ports/misc/compat*>
2150 To upgrade in-place from stable to current
2151 ----------------------------------------------
2152 <make sure you have good level 0 dumps>
2154 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2156 <reboot in single user> [3]
2163 Make sure that you've read the UPDATING file to understand the
2164 tweaks to various things you need. At this point in the life
2165 cycle of current, things change often and you are on your own
2166 to cope. The defaults can also change, so please read ALL of
2167 the UPDATING entries.
2169 Also, if you are tracking -current, you must be subscribed to
2170 freebsd-current@freebsd.org. Make sure that before you update
2171 your sources that you have read and understood all the recent
2172 messages there. If in doubt, please track -stable which has
2173 much fewer pitfalls.
2175 [1] If you have third party modules, such as vmware, you
2176 should disable them at this point so they don't crash your
2179 [3] From the bootblocks, boot -s, and then do
2184 adjkerntz -i # if CMOS is wall time
2185 Also, when doing a major release upgrade, it is required that
2186 you boot into single user mode to do the installworld.
2188 [4] Note: This step is non-optional. Failure to do this step
2189 can result in a significant reduction in the functionality of the
2190 system. Attempting to do it by hand is not recommended and those
2191 that pursue this avenue should read this file carefully, as well
2192 as the archives of freebsd-current and freebsd-hackers mailing lists
2193 for potential gotchas. The -U option is also useful to consider.
2194 See mergemaster(8) for more information.
2196 [5] Usually this step is a noop. However, from time to time
2197 you may need to do this if you get unknown user in the following
2198 step. It never hurts to do it all the time. You may need to
2199 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2200 install) after the buildworld before this step if you last updated
2201 from current before 20130425 or from -stable before 20130430.
2203 [6] This only deletes old files and directories. Old libraries
2204 can be deleted by "make delete-old-libs", but you have to make
2205 sure that no program is using those libraries anymore.
2207 [8] In order to have a kernel that can run the 4.x binaries needed to
2208 do an installworld, you must include the COMPAT_FREEBSD4 option in
2209 your kernel. Failure to do so may leave you with a system that is
2210 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2211 required to run the 5.x binaries on more recent kernels. And so on
2212 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2214 Make sure that you merge any new devices from GENERIC since the
2215 last time you updated your kernel config file.
2217 [9] When checking out sources, you must include the -P flag to have
2218 cvs prune empty directories.
2220 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2221 "?=" instead of the "=" assignment operator, so that buildworld can
2222 override the CPUTYPE if it needs to.
2224 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2225 not on the command line, or in /etc/make.conf. buildworld will
2226 warn if it is improperly defined.
2229 This file contains a list, in reverse chronological order, of major
2230 breakages in tracking -current. It is not guaranteed to be a complete
2231 list of such breakages, and only contains entries since October 10, 2007.
2232 If you need to see UPDATING entries from before that date, you will need
2233 to fetch an UPDATING file from an older FreeBSD release.
2235 Copyright information:
2237 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2239 Redistribution, publication, translation and use, with or without
2240 modification, in full or in part, in any form or format of this
2241 document are permitted without further permission from the author.
2243 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2244 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2245 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2246 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2247 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2248 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2249 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2250 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2251 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2252 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2253 POSSIBILITY OF SUCH DAMAGE.
2255 Contact Warner Losh if you have any questions about your use of