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 20161102 p25 FreeBSD-SA-16:35.openssl
21 Fix OpenSSL remote DoS vulnerability. [SA-16:35]
23 20161025 p24 FreeBSD-SA-16:15.sysarch [revised]
25 Fix incorrect argument validation in sysarch(2). [SA-16:15]
27 20161010 p23 FreeBSD-SA-16:29.bspatch
28 FreeBSD-SA-16:30.portsnap
29 FreeBSD-SA-16:31.libarchive
31 Fix bspatch heap overflow vulnerability. [SA-16:29]
33 Fix multiple portsnap vulnerabilities. [SA-16:30]
35 Fix multiple libarchive vulnerabilities. [SA-16:31]
37 20160926 p22 FreeBSD-SA-16:26.openssl [revised]
39 Fix OpenSSL regression introduced in SA-16:26.
41 20160923 p21 FreeBSD-SA-16:26.openssl
43 Fix multiple OpenSSL vulnerabilitites.
45 20160725 p20 FreeBSD-SA-16:25.bspatch
46 FreeBSD-EN-16:09.freebsd-update
48 Fix bspatch heap overflow vulnerability. [SA-16:25]
50 Fix freebsd-update(8) support of FreeBSD 11.0 release
51 distribution. [EN-16:09]
53 20160604 p19 FreeBSD-SA-16:24.ntp
55 Fix multiple vulnerabilities of ntp.
57 20160531 p18 FreeBSD-SA-16:20.linux
58 FreeBSD-SA-16:21.43bsd
59 FreeBSD-SA-16:22.libarchive
61 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
62 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
63 Fix directory traversal in cpio(1). [SA-16:22]
65 20160517 p17 FreeBSD-SA-16:18.atkbd
66 FreeBSD-SA-16:19.sendmsg
68 Fix buffer overflow in keyboard driver. [SA-16:18]
70 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
72 20160504 p16 FreeBSD-SA-16:17.openssl
76 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
78 Fix excessive latency in x86 IPI delivery. [EN-16:07]
80 Fix memory leak in ZFS. [EN-16:08]
82 20160429 p15 FreeBSD-SA-16:16.ntp
84 Fix multiple vulnerabilities of ntp.
86 20160316 p14 FreeBSD-SA-16:14.openssh-xauth
87 FreeBSD-SA-16:15.sysarch
88 FreeBSD-EN-16:04.hyperv
89 FreeBSD-EN-16:05.hv_netvsc
91 Fix OpenSSH xauth(1) command injection. [SA-16:14]
92 Fix incorrect argument validation in sysarch(2). [SA-16:15]
93 Fix Hyper-V KVP (Key-Value Pair) daemon indefinite sleep. [EN-16:04]
94 Fix hv_netvsc(4) incorrect TCP/IP checksums. [EN-16:05]
96 20160303 p13 FreeBSD-SA-16:12.openssl
98 Fix multiple vulnerabilities of OpenSSL.
100 20160130 p12 FreeBSD-SA-16:11.openssl
102 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
104 20160127 p11 FreeBSD-SA-16:09.ntp
105 FreeBSD-SA-16:10.linux
107 Fix multiple vulnerabilities of ntp. [SA-16:09]
109 Fix Linux compatibility layer issetugid(2) system call
110 vulnerability. [SA-16:10]
112 20160114 p10 FreeBSD-SA-16:07.openssh
114 Fix OpenSSH client information leak. [SA-16:07]
116 20160114 p9 FreeBSD-EN-16:01.filemon
118 FreeBSD-EN-16:03.yplib
119 FreeBSD-SA-16:01.sctp
121 FreeBSD-SA-16:03.linux
122 FreeBSD-SA-16:04.linux
124 FreeBSD-SA-16:06.bsnmpd
126 Fix multiple stability and locking problems in filemon(4). [EN-16:01]
127 Fix pf(4) generating bad TCP checksums. [EN-16:02]
128 Fix infinite loop in YP/NIS client library. [EN-16:03]
129 Fix remote denial of service in SCTP. [SA-16:01]
130 Update NTP to 4.2.8p5. [SA-16:02]
131 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
132 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
133 Fix crash in TCP MD5 signatures. [SA-16:05]
134 Fix insecure default permissions for snmpd.config. [SA-16:06]
136 20151205 p8 FreeBSD-SA-15:26.openssl
138 Fix multiple OpenSSL vulnerabilities. [SA-15:26]
140 20151104 p7 FreeBSD-SA-15:25.ntp [revised]
141 FreeBSD-EN-15:19.kqueue
144 Fix regression in ntpd(8) lacking support for RAWDCF reference
145 clock in 10.2-RELEASE-p6. [SA-15:25]
147 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
149 Fix applications exiting due to segmentation violation on a correct
150 memory address. [EN-15:20.vm]
152 20151026: p6 FreeBSD-SA-15:25.ntp
154 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
156 20151002: p5 FreeBSD-SA-15:24.rpcbind [revised]
157 Revised patch to address a regression that prevents NIS from working.
159 20150929: p4 FreeBSD-SA-15:24.rpcbind
161 Fix rpcbind(8) remote denial of service. [SA-15:24]
163 20150916: p3 FreeBSD-EN-15:16.pw
164 FreeBSD-EN-15:17.libc
167 Fix regression in pw(8) when creating numeric users or groups.
170 Fix libc handling of signals for multi-threaded processes.
173 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
175 20150825: p2 FreeBSD-SA-15:22.openssh
177 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
179 Fix insufficient check of unsupported pkg(7) signature methods.
182 20150818: p1 FreeBSD-SA-15:20.expat
183 FreeBSD-EN-15:11.toolchain
184 FreeBSD-EN-15:12.netstat
185 FreeBSD-EN-15:13.vidcontrol
187 Fix multiple integer overflows in expat (libbsdxml) XML parser.
190 Fix make(1) syntax errors when upgrading from 9.x and earlier.
193 Fix incorrect netstat(1) data handling on 32-bit systems.
196 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
202 The default Unbound configuration now enables remote control
203 using a local socket. Users who have already enabled the
204 local_unbound service should regenerate their configuration
205 by running "service local_unbound setup" as root.
208 An additional fix for the issue described in the 20150614 sendmail
209 entry below has been been committed in revision 284786.
212 The fix for the issue described in the 20150614 sendmail entry
213 below has been been committed in revision 284485. The work
214 around described in that entry is no longer needed unless the
215 default setting is overridden by a confDH_PARAMETERS configuration
216 setting of '5' or pointing to a 512 bit DH parameter file.
219 The import of openssl to address the FreeBSD-SA-15:10.openssl
220 security advisory includes a change which rejects handshakes
221 with DH parameters below 768 bits. sendmail releases prior
222 to 8.15.2 (not yet released), defaulted to a 512 bit
223 DH parameter setting for client connections. To work around
224 this interoperability, sendmail can be configured to use a
225 2048 bit DH parameter by:
227 1. Edit /etc/mail/`hostname`.mc
228 2. If a setting for confDH_PARAMETERS does not exist or
229 exists and is set to a string beginning with '5',
231 3. If a setting for confDH_PARAMETERS exists and is set to
232 a file path, create a new file with:
233 openssl dhparam -out /path/to/file 2048
234 4. Rebuild the .cf file:
235 cd /etc/mail/; make; make install
237 cd /etc/mail/; make restart
239 A sendmail patch is coming, at which time this file will be
243 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
244 defined in symlink(7); previously symlinks were silently ignored.
247 The const qualifier has been removed from iconv(3) to comply with
248 POSIX. The ports tree is aware of this from r384038 onwards.
251 At svn r275807, The default linux compat kernel ABI has been adjusted
252 to 2.6.18 in support of the linux-c6 compat ports infrastructure
253 update. If you wish to continue using the linux-f10 compat ports,
254 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
255 encouraged to update their linux-compat packages to linux-c6 during
256 their next update cycle.
258 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
261 pjdfstest has been integrated into kyua as an opt-in test suite.
262 Please see share/doc/pjdfstest/README for a more details on how to
269 The ofwfb driver, used to provide a graphics console on PowerPC when
270 using vt(4), no longer allows mmap() of all of physical memory. This
271 will prevent Xorg on PowerPC with some ATI graphics cards from
272 initializing properly unless x11-servers/xorg-server is updated to
276 The libatf-c and libatf-c++ major versions were downgraded to 0 and
277 1 respectively to match the upstream numbers. They were out of
278 sync because, when they were originally added to FreeBSD, the
279 upstream versions were not respected. These libraries are private
280 and not yet built by default, so renumbering them should be a
281 non-issue. However, unclean source trees will yield broken test
282 programs once the operator executes "make delete-old-libs" after a
285 Additionally, the atf-sh binary was made private by moving it into
286 /usr/libexec/. Already-built shell test programs will keep the
287 path to the old binary so they will break after "make delete-old"
290 If you are using WITH_TESTS=yes (not the default), wipe the object
291 tree and rebuild from scratch to prevent spurious test failures.
292 This is only needed once: the misnumbered libraries and misplaced
293 binaries have been added to OptionalObsoleteFiles.inc so they will
294 be removed during a clean upgrade.
297 The ixgbe tunables now match their sysctl counterparts, for example:
298 hw.ixgbe.enable_aim => hw.ix.enable_aim
299 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
302 The NFSv4.1 server committed by r269398 changes the internal
303 function call interfaces used between the NFS and krpc modules.
304 As such, __FreeBSD_version was bumped.
307 The default unbound configuration has been modified to address
308 issues with reverse lookups on networks that use private
309 address ranges. If you use the local_unbound service, run
310 "service local_unbound setup" as root to regenerate your
311 configuration, then "service local_unbound reload" to load the
315 It is no longer necessary to include the dwarf version in your DEBUG
316 options in your kernel config file. The bug that required it to be
317 placed in the config file has bene fixed. DEBUG should now just
318 contain -g. The build system will automatically update things
319 to do the right thing.
322 Several ABI breaking changes were merged to CTL and new iSCSI code.
323 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
324 iscsictl need to be rebuilt to work with a new kernel.
327 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
328 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
329 which differs from the behaviour controlled by this knob.)
332 On i386 and amd64 systems, the onifconsole flag is now set by default
333 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
334 as a login TTY if it is set in the bootloader as an active kernel
335 console. No changes in behavior should result otherwise. To revert to
336 the previous behavior, set ttyu0 to "off" in /etc/ttys.
339 Clang and llvm have been upgraded to 3.4.1 release.
342 Clang and llvm have been upgraded to 3.4 release.
345 If a Makefile in a tests/ directory was auto-generating a Kyuafile
346 instead of providing an explicit one, this would prevent such
347 Makefile from providing its own Kyuafile in the future during
348 NO_CLEAN builds. This has been fixed in the Makefiles but manual
349 intervention is needed to clean an objdir if you use NO_CLEAN:
350 # find /usr/obj -name Kyuafile | xargs rm -f
353 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
354 capability mode support. Please note that enabling the feature in
355 kernel is still highly recommended.
358 OpenSSH is now built with sandbox support, and will use sandbox as
359 the default privilege separation method. This requires Capsicum
360 capability mode support in kernel.
363 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
364 been deprecated and will not be part of FreeBSD 11.0 and later
365 releases. If you use this driver, please consider switching to
366 the nfe(4) driver instead.
372 The behavior of gss_pseudo_random() for the krb5 mechanism
373 has changed, for applications requesting a longer random string
374 than produced by the underlying enctype's pseudo-random() function.
375 In particular, the random string produced from a session key of
376 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
377 be different at the 17th octet and later, after this change.
378 The counter used in the PRF+ construction is now encoded as a
379 big-endian integer in accordance with RFC 4402.
380 __FreeBSD_version is bumped to 1000701.
383 The WITHOUT_ATF build knob has been removed and its functionality
384 has been subsumed into the more generic WITHOUT_TESTS. If you were
385 using the former to disable the build of the ATF libraries, you
386 should change your settings to use the latter.
389 The default version of mtree is nmtree which is obtained from
390 NetBSD. The output is generally the same, but may vary
391 slightly. If you found you need identical output adding
392 "-F freebsd9" to the command line should do the trick. For the
393 time being, the old mtree is available as fmtree.
396 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
397 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
398 1.1.4_8 and verify bsdyml not linked in, before running "make
400 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
402 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
405 The rc.d/jail script has been updated to support jail(8)
406 configuration file. The "jail_<jname>_*" rc.conf(5) variables
407 for per-jail configuration are automatically converted to
408 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
409 This is transparently backward compatible. See below about some
410 incompatibilities and rc.conf(5) manual page for more details.
412 These variables are now deprecated in favor of jail(8) configuration
413 file. One can use "rc.d/jail config <jname>" command to generate
414 a jail(8) configuration file in /var/run/jail.<jname>.conf without
415 running the jail(8) utility. The default pathname of the
416 configuration file is /etc/jail.conf and can be specified by
417 using $jail_conf or $jail_<jname>_conf variables.
419 Please note that jail_devfs_ruleset accepts an integer at
420 this moment. Please consider to rewrite the ruleset name
424 BIND has been removed from the base system. If all you need
425 is a local resolver, simply enable and start the local_unbound
426 service instead. Otherwise, several versions of BIND are
427 available in the ports tree. The dns/bind99 port is one example.
429 With this change, nslookup(1) and dig(1) are no longer in the base
430 system. Users should instead use host(1) and drill(1) which are
431 in the base system. Alternatively, nslookup and dig can
432 be obtained by installing the dns/bind-tools port.
435 With the addition of unbound(8), a new unbound user is now
436 required during installworld. "mergemaster -p" can be used to
437 add the user prior to installworld, as documented in the handbook.
440 OpenSSH is now built with DNSSEC support, and will by default
441 silently trust signed SSHFP records. This can be controlled with
442 the VerifyHostKeyDNS client configuration setting. DNSSEC support
443 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
446 The GNU Compiler Collection and C++ standard library (libstdc++)
447 are no longer built by default on platforms where clang is the system
448 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
452 The PROCDESC kernel option is now part of the GENERIC kernel
453 configuration and is required for the rwhod(8) to work.
454 If you are using custom kernel configuration, you should include
458 The API and ABI related to the Capsicum framework was modified
459 in backward incompatible way. The userland libraries and programs
460 have to be recompiled to work with the new kernel. This includes the
461 following libraries and programs, but the whole buildworld is
462 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
463 kdump, procstat, rwho, rwhod, uniq.
466 AES-NI intrinsic support has been added to gcc. The AES-NI module
467 has been updated to use this support. A new gcc is required to build
468 the aesni module on both i386 and amd64.
471 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
472 Thus "device padlock_rng" and "device rdrand_rng" should be
473 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
476 WITH_ICONV has been split into two feature sets. WITH_ICONV now
477 enables just the iconv* functionality and is now on by default.
478 WITH_LIBICONV_COMPAT enables the libiconv api and link time
479 compatability. Set WITHOUT_ICONV to build the old way.
480 If you have been using WITH_ICONV before, you will very likely
481 need to turn on WITH_LIBICONV_COMPAT.
484 INVARIANTS option now enables DEBUG for code with OpenSolaris and
485 Illumos origin, including ZFS. If you have INVARIANTS in your
486 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
488 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
489 locks if WITNESS option was set. Because that generated a lot of
490 witness(9) reports and all of them were believed to be false
491 positives, this is no longer done. New option OPENSOLARIS_WITNESS
492 can be used to achieve the previous behavior.
495 Timer values in IPv6 data structures now use time_uptime instead
496 of time_second. Although this is not a user-visible functional
497 change, userland utilities which directly use them---ndp(8),
498 rtadvd(8), and rtsold(8) in the base system---need to be updated
502 find -delete can now delete the pathnames given as arguments,
503 instead of only files found below them or if the pathname did
504 not contain any slashes. Formerly, the following error message
507 find: -delete: <path>: relative path potentially not safe
509 Deleting the pathnames given as arguments can be prevented
510 without error messages using -mindepth 1 or by changing
511 directory and passing "." as argument to find. This works in the
512 old as well as the new version of find.
515 Behavior of devfs rules path matching has been changed.
516 Pattern is now always matched against fully qualified devfs
517 path and slash characters must be explicitly matched by
518 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
519 subdirectories must be reviewed.
522 The default ARM ABI has changed to the ARM EABI. The old ABI is
523 incompatible with the ARM EABI and all programs and modules will
524 need to be rebuilt to work with a new kernel.
526 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
528 NOTE: Support for the old ABI will be removed in the future and
529 users are advised to upgrade.
532 pkg_install has been disconnected from the build if you really need it
533 you should add WITH_PKGTOOLS in your src.conf(5).
536 Most of network statistics structures were changed to be able
537 keep 64-bits counters. Thus all tools, that work with networking
538 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
541 Fix targets that run multiple make's to use && rather than ;
542 so that subsequent steps depend on success of previous.
544 NOTE: if building 'universe' with -j* on stable/8 or stable/9
545 it would be better to start the build using bmake, to avoid
546 overloading the machine.
549 Fix a bug that allowed a tracing process (e.g. gdb) to write
550 to a memory-mapped file in the traced process's address space
551 even if neither the traced process nor the tracing process had
552 write access to that file.
555 CVS has been removed from the base system. An exact copy
556 of the code is available from the devel/cvs port.
559 Some people report the following error after the switch to bmake:
561 make: illegal option -- J
562 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
564 *** [buildworld] Error code 2
566 this likely due to an old instance of make in
567 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
568 which src/Makefile will use that blindly, if it exists, so if
569 you see the above error:
571 rm -rf `make -V MAKEPATH`
576 Use bmake by default.
577 Whereas before one could choose to build with bmake via
578 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
579 make. The goal is to remove these knobs for 10-RELEASE.
581 It is worth noting that bmake (like gmake) treats the command
582 line as the unit of failure, rather than statements within the
583 command line. Thus '(cd some/where && dosomething)' is safer
584 than 'cd some/where; dosomething'. The '()' allows consistent
585 behavior in parallel build.
588 Fix a bug that allows NFS clients to issue READDIR on files.
591 The WITHOUT_IDEA option has been removed because
592 the IDEA patent expired.
595 The sysctl which controls TRIM support under ZFS has been renamed
596 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
600 The mergemaster command now uses the default MAKEOBJDIRPREFIX
601 rather than creating it's own in the temporary directory in
602 order allow access to bootstrapped versions of tools such as
603 install and mtree. When upgrading from version of FreeBSD where
604 the install command does not support -l, you will need to
605 install a new mergemaster command if mergemaster -p is required.
606 This can be accomplished with the command (cd src/usr.sbin/mergemaster
610 Legacy ATA stack, disabled and replaced by new CAM-based one since
611 FreeBSD 9.0, completely removed from the sources. Kernel modules
612 atadisk and atapi*, user-level tools atacontrol and burncd are
613 removed. Kernel option `options ATA_CAM` is now permanently enabled
617 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
618 and socketpair(2). Software, in particular Kerberos, may
619 automatically detect and use these during building. The resulting
620 binaries will not work on older kernels.
623 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
624 information, see the respective 20130304 entry).
627 Recent commits to callout(9) changed the size of struct callout,
628 so the KBI is probably heavily disturbed. Also, some functions
629 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
630 by macros. Every kernel module using it won't load, so rebuild
633 The ctl device has been re-enabled in GENERIC for i386 and amd64,
634 but does not initialize by default (because of the new CTL_DISABLE
635 option) to save memory. To re-enable it, remove the CTL_DISABLE
636 option from the kernel config file or set kern.cam.ctl.disable=0
637 in /boot/loader.conf.
640 The ctl device has been disabled in GENERIC for i386 and amd64.
641 This was done due to the extra memory being allocated at system
642 initialisation time by the ctl driver which was only used if
643 a CAM target device was created. This makes a FreeBSD system
644 unusable on 128MB or less of RAM.
647 A new compression method (lz4) has been merged to -HEAD. Please
648 refer to zpool-features(7) for more information.
650 Please refer to the "ZFS notes" section of this file for information
651 on upgrading boot ZFS pools.
654 A BSD-licensed patch(1) variant has been added and is installed
655 as bsdpatch, being the GNU version the default patch.
656 To inverse the logic and use the BSD-licensed one as default,
657 while having the GNU version installed as gnupatch, rebuild
658 and install world with the WITH_BSD_PATCH knob set.
661 Due to the use of the new -l option to install(1) during build
662 and install, you must take care not to directly set the INSTALL
663 make variable in your /etc/make.conf, /etc/src.conf, or on the
664 command line. If you wish to use the -C flag for all installs
665 you may be able to add INSTALL+=-C to /etc/make.conf or
669 The install(1) option -M has changed meaning and now takes an
670 argument that is a file or path to append logs to. In the
671 unlikely event that -M was the last option on the command line
672 and the command line contained at least two files and a target
673 directory the first file will have logs appended to it. The -M
674 option served little practical purpose in the last decade so its
675 use is expected to be extremely rare.
678 After switching to Clang as the default compiler some users of ZFS
679 on i386 systems started to experience stack overflow kernel panics.
680 Please consider using 'options KSTACK_PAGES=4' in such configurations.
683 GEOM_LABEL now mangles label names read from file system metadata.
684 Mangling affect labels containing spaces, non-printable characters,
685 '%' or '"'. Device names in /etc/fstab and other places may need to
689 By default, only the 10 most recent kernel dumps will be saved. To
690 restore the previous behaviour (no limit on the number of kernel dumps
691 stored in the dump directory) add the following line to /etc/rc.conf:
696 With the addition of auditdistd(8), a new auditdistd user is now
697 required during installworld. "mergemaster -p" can be used to
698 add the user prior to installworld, as documented in the handbook.
701 The sin6_scope_id member variable in struct sockaddr_in6 is now
702 filled by the kernel before passing the structure to the userland via
703 sysctl or routing socket. This means the KAME-specific embedded scope
704 id in sin6_addr.s6_addr[2] is always cleared in userland application.
705 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
706 __FreeBSD_version is bumped to 1000025.
709 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
710 This means that the world and kernel will be compiled with clang
711 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
712 and /usr/bin/cpp. To disable this behavior and revert to building
713 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
714 of current may need to bootstrap WITHOUT_CLANG first if the clang
715 build fails (its compatibility window doesn't extend to the 9 stable
719 The IPFIREWALL_FORWARD kernel option has been removed. Its
720 functionality now turned on by default.
723 The ZERO_COPY_SOCKET kernel option has been removed and
724 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
725 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
726 mechanism which is not safe and may result in kernel crashes.
727 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
728 driver supports disposeable external page sized mbuf storage.
729 Proper replacements for both zero-copy mechanisms are under
730 consideration and will eventually lead to complete removal
731 of the two kernel options.
734 The IPv4 network stack has been converted to network byte
735 order. The following modules need to be recompiled together
736 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
737 pf(4), ipfw(4), ng_ipfw(4), stf(4).
740 Support for non-MPSAFE filesystems was removed from VFS. The
741 VFS_VERSION was bumped, all filesystem modules shall be
745 All the non-MPSAFE filesystems have been disconnected from
746 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
747 portalfs, smbfs, xfs.
750 The interface cloning API and ABI has changed. The following
751 modules need to be recompiled together with kernel:
752 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
753 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
754 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
757 The sdhci driver was split in two parts: sdhci (generic SD Host
758 Controller logic) and sdhci_pci (actual hardware driver).
759 No kernel config modifications are required, but if you
760 load sdhc as a module you must switch to sdhci_pci instead.
763 Import the FUSE kernel and userland support into base system.
766 The GNU sort(1) program has been removed since the BSD-licensed
767 sort(1) has been the default for quite some time and no serious
768 problems have been reported. The corresponding WITH_GNU_SORT
772 The pfil(9) API/ABI for AF_INET family has been changed. Packet
773 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
777 The net80211(4) ABI has been changed to allow for improved driver
778 PS-POLL and power-save support. All wireless drivers need to be
779 recompiled to work with the new kernel.
782 The random(4) support for the VIA hardware random number
783 generator (`PADLOCK') is no longer enabled unconditionally.
784 Add the padlock_rng device in the custom kernel config if
785 needed. The GENERIC kernels on i386 and amd64 do include the
786 device, so the change only affects the custom kernel
790 The pf(4) packet filter ABI has been changed. pfctl(8) and
791 snmp_pf module need to be recompiled to work with new kernel.
794 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
795 to -HEAD. Pools that have empty_bpobj in active state can not be
796 imported read-write with ZFS implementations that do not support
797 this feature. For more information read the zpool-features(5)
801 The sparc64 ZFS loader has been changed to no longer try to auto-
802 detect ZFS providers based on diskN aliases but now requires these
803 to be explicitly listed in the OFW boot-device environment variable.
806 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
807 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
808 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
811 The following sysctls and tunables have been renamed for consistency
812 with other variables:
813 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
814 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
817 The sort utility has been replaced with BSD sort. For now, GNU sort
818 is also available as "gnusort" or the default can be set back to
819 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
820 installed as "bsdsort".
823 A new version of ZFS (pool version 5000) has been merged to -HEAD.
824 Starting with this version the old system of ZFS pool versioning
825 is superseded by "feature flags". This concept enables forward
826 compatibility against certain future changes in functionality of ZFS
827 pools. The first read-only compatible "feature flag" for ZFS pools
828 is named "com.delphix:async_destroy". For more information
829 read the new zpool-features(5) manual page.
830 Please refer to the "ZFS notes" section of this file for information
831 on upgrading boot ZFS pools.
834 The malloc(3) implementation embedded in libc now uses sources imported
835 as contrib/jemalloc. The most disruptive API change is to
836 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
837 delete it prior to installworld, and optionally re-create it using the
838 new format after rebooting. See malloc.conf(5) for details
839 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
843 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
844 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
845 now spelled mips. This is to aid compatibility with third-party
846 software that expects this naming scheme in uname(3). Little-endian
847 settings are unchanged. If you are updating a big-endian mips64 machine
848 from before this change, you may need to set MACHINE_ARCH=mips64 in
849 your environment before the new build system will recognize your machine.
852 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
856 Now unix domain sockets behave "as expected" on nullfs(5). Previously
857 nullfs(5) did not pass through all behaviours to the underlying layer,
858 as a result if we bound to a socket on the lower layer we could connect
859 only to the lower path; if we bound to the upper layer we could connect
860 only to the upper path. The new behavior is one can connect to both the
861 lower and the upper paths regardless what layer path one binds to.
864 The getifaddrs upgrade path broken with 20111215 has been restored.
865 If you have upgraded in between 20111215 and 20120209 you need to
866 recompile libc again with your kernel. You still need to recompile
867 world to be able to configure CARP but this restriction already
871 The set_rcvar() function has been removed from /etc/rc.subr. All
872 base and ports rc.d scripts have been updated, so if you have a
873 port installed with a script in /usr/local/etc/rc.d you can either
874 hand-edit the rcvar= line, or reinstall the port.
876 An easy way to handle the mass-update of /etc/rc.d:
877 rm /etc/rc.d/* && mergemaster -i
880 panic(9) now stops other CPUs in the SMP systems, disables interrupts
881 on the current CPU and prevents other threads from running.
882 This behavior can be reverted using the kern.stop_scheduler_on_panic
884 The new behavior can be incompatible with kern.sync_on_panic.
887 The carp(4) facility has been changed significantly. Configuration
888 of the CARP protocol via ifconfig(8) has changed, as well as format
889 of CARP events submitted to devd(8) has changed. See manual pages
890 for more information. The arpbalance feature of carp(4) is currently
891 not supported anymore.
893 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
894 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
895 need to be recompiled.
898 The acpi_wmi(4) status device /dev/wmistat has been renamed to
902 The option VFS_ALLOW_NONMPSAFE option has been added in order to
903 explicitely support non-MPSAFE filesystems.
904 It is on by default for all supported platform at this present
908 The broken amd(4) driver has been replaced with esp(4) in the amd64,
909 i386 and pc98 GENERIC kernel configuration files.
912 sysinstall has been removed
915 The stable/9 branch created in subversion. This corresponds to the
916 RELENG_9 branch in CVS.
919 This commit modifies vfs_register() so that it uses a hash
920 calculation to set vfc_typenum, which is enabled by default.
921 The first time a system is booted after this change, the
922 vfc_typenum values will change for all file systems. The
923 main effect of this is a change to the NFS server file handles
924 for file systems that use vfc_typenum in their fsid, such as ZFS.
925 It will, however, prevent vfc_typenum from changing when file
926 systems are loaded in a different order for subsequent reboots.
927 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
928 until you are ready to remount all NFS clients after a reboot.
931 Bump the shared library version numbers for libraries that
932 do not use symbol versioning, have changed the ABI compared
933 to stable/8 and which shared library version was not bumped.
934 Done as part of 9.0-RELEASE cycle.
937 During the merge of Capsicum features, the fget(9) KPI was modified.
938 This may require the rebuilding of out-of-tree device drivers --
939 issues have been reported specifically with the nVidia device driver.
940 __FreeBSD_version is bumped to 900041.
942 Also, there is a period between 20110811 and 20110814 where the
943 special devices /dev/{stdin,stdout,stderr} did not work correctly.
944 Building world from a kernel during that window may not work.
947 The packet filter (pf) code has been updated to OpenBSD 4.5.
948 You need to update userland tools to be in sync with kernel.
949 This update breaks backward compatibility with earlier pfsync(4)
950 versions. Care must be taken when updating redundant firewall setups.
953 The following sysctls and tunables are retired on x86 platforms:
955 machdep.hlt_logical_cpus
956 The following sysctl is retired:
957 machdep.hyperthreading_allowed
958 The sysctls were supposed to provide a way to dynamically offline and
959 online selected CPUs on x86 platforms, but the implementation has not
960 been reliable especially with SCHED_ULE scheduler.
961 machdep.hyperthreading_allowed tunable is still available to ignore
962 hyperthreading CPUs at OS level.
963 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
964 where X is an APIC ID of a CPU. Be advised, though, that disabling
965 CPUs in non-uniform fashion will result in non-uniform topology and
966 may lead to sub-optimal system performance with SCHED_ULE, which is
970 cpumask_t type is retired and cpuset_t is used in order to describe
974 Changes to ifconfig(8) for dynamic address family detection mandate
975 that you are running a kernel of 20110525 or later. Make sure to
976 follow the update procedure to boot a new kernel before installing
980 Support for sun4v architecture is officially dropped
983 Several KPI breaking changes have been committed to the mii(4) layer,
984 the PHY drivers and consequently some Ethernet drivers using mii(4).
985 This means that miibus.ko and the modules of the affected Ethernet
986 drivers need to be recompiled.
988 Note to kernel developers: Given that the OUI bit reversion problem
989 was fixed as part of these changes all mii(4) commits related to OUIs,
990 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
991 handling, no longer can be merged verbatim to stable/8 and previous
995 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
996 into their kernel configurations along with 'device pci'.
999 The default NFS client is now the new NFS client, so fstype "newnfs"
1000 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
1001 Although mounts via fstype "nfs" will usually work without userland
1002 changes, it is recommended that the mount(8) and mount_nfs(8)
1003 commands be rebuilt from sources and that a link to mount_nfs called
1004 mount_oldnfs be created. The new client is compiled into the
1005 kernel with "options NFSCL" and this is needed for diskless root
1006 file systems. The GENERIC kernel configs have been changed to use
1007 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
1008 To use the regular/old client, you can "mount -t oldnfs ...". For
1009 a diskless root file system, you must also include a line like:
1011 vfs.root.mountfrom="oldnfs:"
1013 in the boot/loader.conf on the root fs on the NFS server to make
1014 a diskless root fs use the old client.
1017 The GENERIC kernels for all architectures now default to the new
1018 CAM-based ATA stack. It means that all legacy ATA drivers were
1019 removed and replaced by respective CAM drivers. If you are using
1020 ATA device names in /etc/fstab or other places, make sure to update
1021 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
1022 where 'Y's are the sequential numbers starting from zero for each type
1023 in order of detection, unless configured otherwise with tunables,
1024 see cam(4)). There will be symbolic links created in /dev/ to map
1025 old adX devices to the respective adaY. They should provide basic
1026 compatibility for file systems mounting in most cases, but they do
1027 not support old user-level APIs and do not have respective providers
1028 in GEOM. Consider using updated management tools with new device names.
1030 It is possible to load devices ahci, ata, siis and mvs as modules,
1031 but option ATA_CAM should remain in kernel configuration to make ata
1032 module work as CAM driver supporting legacy ATA controllers. Device ata
1033 still can be used in modular fashion (atacore + ...). Modules atadisk
1034 and atapi* are not used and won't affect operation in ATA_CAM mode.
1035 Note that to use CAM-based ATA kernel should include CAM devices
1036 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1037 them are parts of the cam module.
1039 ataraid(4) functionality is now supported by the RAID GEOM class.
1040 To use it you can load geom_raid kernel module and use graid(8) tool
1041 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1043 No kernel config options or code have been removed, so if a problem
1044 arises, please report it and optionally revert to the old ATA stack.
1045 In order to do it you can remove from the kernel config:
1050 , and instead add back:
1051 device atadisk # ATA disk drives
1052 device ataraid # ATA RAID drives
1053 device atapicd # ATAPI CDROM drives
1054 device atapifd # ATAPI floppy drives
1055 device atapist # ATAPI tape drives
1058 The default NFS server has been changed to the new server, which
1059 was referred to as the experimental server. If you need to switch
1060 back to the old NFS server, you must now put the "-o" option on
1061 both the mountd and nfsd commands. This can be done using the
1062 mountd_flags and nfs_server_flags rc.conf variables until an
1063 update to the rc scripts is committed, which is coming soon.
1066 The GNU Objective-C runtime library (libobjc), and other Objective-C
1067 related components have been removed from the base system. If you
1068 require an Objective-C library, please use one of the available ports.
1071 ath(4) has been split into bus- and device- modules. if_ath contains
1072 the HAL, the TX rate control and the network device code. if_ath_pci
1073 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1074 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1075 in order to use ath on everything else.
1077 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1078 need to load if_ath and if_ath_pci for ath(4) operation.
1081 As part of the replacement of sysinstall, the process of building
1082 release media has changed significantly. For details, please re-read
1083 release(7), which has been updated to reflect the new build process.
1086 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1087 is the last available version under GPLv2. It brings a number of new
1088 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1089 4.1 and SSE 4.2), better support for powerpc64, a number of new
1090 directives, and lots of other small improvements. See the ChangeLog
1091 file in contrib/binutils for the full details.
1094 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1095 compliant, and will now use half of hash for authentication.
1096 This will break interoperability with all stacks (including all
1097 actual FreeBSD versions) who implement
1098 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1100 The only workaround with such peers is to use another HMAC
1101 algorithm for IPsec ("phase 2") authentication.
1104 Remove the uio_yield prototype and symbol. This function has
1105 been misnamed since it was introduced and should not be
1106 globally exposed with this name. The equivalent functionality
1107 is now available using kern_yield(curthread->td_user_pri).
1108 The function remains undocumented.
1111 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1112 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1113 for scalar sysctls is defined but disabled. Code that needs
1114 UQUAD to pass the type checking that must compile on older
1115 systems where the define is not present can check against
1116 __FreeBSD_version >= 900030.
1118 The system dialog(1) has been replaced with a new version previously
1119 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1120 with the previous version, but the libdialog associated with it has
1121 a largely incompatible API. As such, the original version of libdialog
1122 will be kept temporarily as libodialog, until its base system consumers
1123 are replaced or updated. Bump __FreeBSD_version to 900030.
1126 If you are trying to run make universe on a -stable system, and you get
1127 the following warning:
1128 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1129 unknown. config(8) likely too old."
1130 or something similar to it, then you must upgrade your -stable system
1131 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1132 stable/8) or build the config from the latest stable/8 branch and
1133 install it on your system.
1135 Prior to this date, building a current universe on 8-stable system from
1136 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1137 error in the first kernel build phase. A new config on those old
1138 systems will fix that problem for older versions of -current.
1141 The TCP stack has been modified to allow Khelp modules to interact with
1142 it via helper hook points and store per-connection data in the TCP
1143 control block. Bump __FreeBSD_version to 900029. User space tools that
1144 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1148 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1149 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1150 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1151 to take advantage of it instead of using custom implementations. This
1152 means that these drivers now no longer unconditionally advertise
1153 support for flow control but only do so if flow control is a selected
1154 media option. This was implemented in the generic support that way in
1155 order to allow flow control to be switched on and off via ifconfig(8)
1156 with the PHY specific default to typically off in order to protect
1157 from unwanted effects. Consequently, if you used flow control with
1158 one of the above mentioned drivers you now need to explicitly enable
1159 it, for example via:
1160 ifconfig bge0 media auto mediaopt flowcontrol
1162 Along with the above mentioned changes generic support for setting
1163 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1164 e1000phy(4) as well as ip1000phy(4) have been converted to take
1165 advantage of it. This means that these drivers now no longer take the
1166 link0 parameter for selecting master mode but the master media option
1167 has to be used instead, for example like in the following:
1168 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1170 Selection of master mode now is also available with all other PHY
1171 drivers supporting 1000baseT.
1174 The TCP stack has received a significant update to add support for
1175 modularised congestion control and generally improve the clarity of
1176 congestion control decisions. Bump __FreeBSD_version to 900025. User
1177 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1178 sockstat) need to be recompiled.
1181 The man(1) utility has been replaced by a new version that no longer
1182 uses /etc/manpath.config. Please consult man.conf(5) for how to
1183 migrate local entries to the new format.
1186 The copyright strings printed by login(1) and sshd(8) at the time of a
1187 new connection have been removed to follow other operating systems and
1191 A workaround for a fixed ld bug has been removed in kernel code,
1192 so make sure that your system ld is built from sources after
1193 revision 210245 from 2010-07-19 (r211583 if building head kernel
1194 on stable/8, r211584 for stable/7; both from 2010-08-21).
1195 A symptom of incorrect ld version is different addresses for
1196 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1199 The $ipv6_prefer variable in rc.conf(5) has been split into
1200 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1202 The $ip6addrctl_policy is a variable to choose a pre-defined
1203 address selection policy set by ip6addrctl(8). A value
1204 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1207 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1208 flag (see an entry of 20090926) is set on an interface with no
1209 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1210 security reason. If you want IPv6 link-local address on all
1211 interfaces by default, set this to "YES".
1213 The old ipv6_prefer="YES" is equivalent to
1214 ipv6_activate_all_interfaces="YES" and
1215 ip6addrctl_policy="ipv6_prefer".
1218 DTrace has grown support for userland tracing. Due to this, DTrace is
1219 now i386 and amd64 only.
1220 dtruss(1) is now installed by default on those systems and a new
1221 kernel module is needed for userland tracing: fasttrap.
1222 No changes to your kernel config file are necessary to enable
1223 userland tracing, but you might consider adding 'STRIP=' and
1224 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1225 to have informative userland stack traces in DTrace (ustack).
1228 The acpi_aiboost(4) driver has been removed in favor of the new
1229 aibs(4) driver. You should update your kernel configuration file.
1232 BSD grep has been imported to the base system and it is built by
1233 default. It is completely BSD licensed, highly GNU-compatible, uses
1234 less memory than its GNU counterpart and has a small codebase.
1235 However, it is slower than its GNU counterpart, which is mostly
1236 noticeable for larger searches, for smaller ones it is measurable
1237 but not significant. The reason is complex, the most important factor
1238 is that we lack a modern and efficient regex library and GNU
1239 overcomes this by optimizing the searches internally. Future work
1240 on improving the regex performance is planned, for the meantime,
1241 users that need better performance, can build GNU grep instead by
1242 setting the WITH_GNU_GREP knob.
1245 Due to the import of powerpc64 support, all existing powerpc kernel
1246 configuration files must be updated with a machine directive like this:
1247 machine powerpc powerpc
1249 In addition, an updated config(8) is required to build powerpc kernels
1253 A new version of ZFS (version 15) has been merged to -HEAD.
1254 This version uses a python library for the following subcommands:
1255 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1256 For full functionality of these commands the following port must
1257 be installed: sysutils/py-zfs
1260 'vm_page's are now hashed by physical address to an array of mutexes.
1261 Currently this is only used to serialize access to hold_count. Over
1262 time the page queue mutex will be peeled away. This changes the size
1263 of pmap on every architecture. And requires all callers of vm_page_hold
1264 and vm_page_unhold to be updated.
1267 WITH_CTF can now be specified in src.conf (not recommended, there
1268 are some problems with static executables), make.conf (would also
1269 affect ports which do not use GNU make and do not override the
1270 compile targets) or in the kernel config (via "makeoptions
1272 When WITH_CTF was specified there before this was silently ignored,
1273 so make sure that WITH_CTF is not used in places which could lead
1274 to unwanted behavior.
1277 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1278 to allow 32-bit compatibility on non-x86 platforms. All kernel
1279 configurations on amd64 and ia64 platforms using these options must
1280 be modified accordingly.
1283 The utmp user accounting database has been replaced with utmpx,
1284 the user accounting interface standardized by POSIX.
1285 Unfortunately the semantics of utmp and utmpx don't match,
1286 making it practically impossible to support both interfaces.
1287 The user accounting database is used by tools like finger(1),
1288 last(1), talk(1), w(1) and ac(8).
1290 All applications in the base system use utmpx. This means only
1291 local binaries (e.g. from the ports tree) may still use these
1292 utmp database files. These applications must be rebuilt to make
1295 After the system has been upgraded, it is safe to remove the old
1296 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1297 assuming their contents is of no importance anymore. Old wtmp
1298 databases can only be used by last(1) and ac(8) after they have
1299 been converted to the new format using wtmpcvt(1).
1302 Introduce the kernel thread "deadlock resolver" (which can be enabled
1303 via the DEADLKRES option, see NOTES for more details) and the
1304 sleepq_type() function for sleepqueues.
1307 The rc.firewall and rc.firewall6 were unified, and
1308 rc.firewall6 and rc.d/ip6fw were removed.
1309 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1310 variables are obsoleted. Instead, the following new rc
1311 variables are added to rc.d/ipfw:
1313 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1314 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1315 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1317 The meanings correspond to the relevant IPv4 variables.
1323 The default terminal emulation for syscons(4) has been changed
1324 from cons25 to xterm on all platforms except pc98. This means
1325 that the /etc/ttys file needs to be updated to ensure correct
1326 operation of applications on the console.
1328 The terminal emulation style can be toggled per window by using
1329 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1330 options can be used to change the compile-time default back to
1333 To prevent graphical artifacts, make sure the TERM environment
1334 variable is set to match the terminal emulation that is being
1335 performed by syscons(4).
1338 The layout of the structure ieee80211req_scan_result has changed.
1339 Applications that require wireless scan results (e.g. ifconfig(8))
1340 from net80211 need to be recompiled.
1342 Applications such as wpa_supplicant(8) may require a full world
1343 build without using NO_CLEAN in order to get synchronized with the
1347 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1348 There's one kernel module for each firmware. Adding "device iwnfw"
1349 to the kernel configuration file means including all three firmware
1350 images inside the kernel. If you want to include just the one for
1351 your wireless card, use the devices iwn4965fw, iwn5000fw or
1355 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1356 into rc.d/netif. The changes are the following:
1358 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1359 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1360 Note that both variables need the "inet6" keyword at the head.
1362 Do not set $ipv6_network_interfaces manually if you do not
1363 understand what you are doing. It is not needed in most cases.
1365 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1368 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1369 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1371 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1372 all configured interfaces have "inet6 accept_rtadv" in the
1373 $ifconfig_IF_ipv6. These are for backward compatibility.
1375 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1376 functionality of interfaces with no corresponding
1377 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1378 and the default address selection policy of ip6addrctl(8)
1379 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1380 Note that if you want to configure IPv6 functionality on the
1381 disabled interfaces after boot, first you need to clear the flag by
1382 using ifconfig(8) like:
1384 ifconfig em0 inet6 -ifdisabled
1386 If YES, the default address selection policy is set as
1389 The default value of $ipv6_prefer is NO.
1391 4. If your system need to receive Router Advertisement messages,
1392 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1393 scripts automatically invoke rtsol(8) when the interface becomes
1394 UP. The Router Advertisement messages are used for SLAAC
1395 (State-Less Address AutoConfiguration).
1398 802.11s D3.03 support was committed. This is incompatible with the
1399 previous code, which was based on D3.0.
1402 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1403 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1404 control whether accepting Router Advertisement messages or not.
1405 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1406 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1407 The ifconfig(8) utility now supports these flags.
1410 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1411 mount(8) and -a option for df(1) to see them.
1414 The old tunable hw.bus.devctl_disable has been superseded by
1415 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1416 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1420 Remove the option STOP_NMI. The default action is now to use NMI only
1421 for KDB via the newly introduced function stop_cpus_hard() and
1422 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1425 The stable/8 branch created in subversion. This corresponds to the
1426 RELENG_8 branch in CVS.
1429 Bump the shared library version numbers for all libraries that do not
1430 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1431 __FreeBSD_version to 800105.
1434 Due to changes in the implementation of virtual network stack support,
1435 all network-related kernel modules must be recompiled. As this change
1436 breaks the ABI, bump __FreeBSD_version to 800104.
1439 The TOE interface to the TCP syncache has been modified to remove
1440 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1441 The cxgb driver is the only TOE consumer affected by this change, and
1442 needs to be recompiled along with the kernel. As this change breaks
1443 the ABI, bump __FreeBSD_version to 800103.
1446 Padding has been added to struct tcpcb, sackhint and tcpstat in
1447 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1448 maintaining the ABI. However, this change breaks the ABI, so bump
1449 __FreeBSD_version to 800102. User space tools that rely on the size of
1450 any of these structs (e.g. sockstat) need to be recompiled.
1453 The NFS_LEGACYRPC option has been removed along with the old kernel
1454 RPC implementation that this option selected. Kernel configurations
1455 may need to be adjusted.
1458 The network interface device nodes at /dev/net/<interface> have been
1459 removed. All ioctl operations can be performed the normal way using
1460 routing sockets. The kqueue functionality can generally be replaced
1461 with routing sockets.
1464 The documentation from the FreeBSD Documentation Project (Handbook,
1465 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1466 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1469 The ABI of various structures related to the SYSV IPC API have been
1470 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1471 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1475 Layout of struct vnet has changed as routing related variables were
1476 moved to their own Vimage module. Modules need to be recompiled. Bump
1477 __FreeBSD_version to 800099.
1480 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1481 respectively. As long as no more than 16 groups per process are used,
1482 no changes should be visible. When more than 16 groups are used, old
1483 binaries may fail if they call getgroups() or getgrouplist() with
1484 statically sized storage. Recompiling will work around this, but
1485 applications should be modified to use dynamically allocated storage
1486 for group arrays as POSIX.1-2008 does not cap an implementation's
1487 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1489 NFS and portalfs mounts may also be affected as the list of groups is
1490 truncated to 16. Users of NFS who use more than 16 groups, should
1491 take care that negative group permissions are not used on the exported
1492 file systems as they will not be reliable unless a GSSAPI based
1493 authentication method is used.
1496 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1497 option compiles in the support for adaptive spinning for lockmgrs
1498 which want to enable it. The lockinit() function now accepts the flag
1499 LK_ADAPTIVE in order to make the lock object subject to adaptive
1500 spinning when both held in write and read mode.
1503 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1504 changed. User applications that use this ioctl need to be rebuilt.
1507 The layout of struct thread has changed. Kernel and modules need to
1511 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1512 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1515 window(1) has been removed from the base system. It can now be
1516 installed from ports. The port is called misc/window.
1519 The way we are storing and accessing `routing table' entries has
1520 changed. Programs reading the FIB, like netstat, need to be
1524 A new netisr implementation has been added for FreeBSD 8. Network
1525 file system modules, such as igmp, ipdivert, and others, should be
1527 Bump __FreeBSD_version to 800096.
1530 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1534 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1535 Bump __FreeBSD_version to 800094.
1538 Add mnt_xflag field to 'struct mount'. File system modules need to be
1540 Bump __FreeBSD_version to 800093.
1543 The compiling option ADAPTIVE_SX has been retired while it has been
1544 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1545 The KPI for sx_init_flags() changes as accepting flags:
1546 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1547 been introduced in order to handle the reversed logic.
1548 Bump __FreeBSD_version to 800092.
1551 Add support for hierarchical jails. Remove global securelevel.
1552 Bump __FreeBSD_version to 800091.
1555 The layout of struct vnet_net has changed, therefore modules
1557 Bump __FreeBSD_version to 800090.
1560 The newly imported zic(8) produces a new format in the output. Please
1561 run tzsetup(8) to install the newly created data to /etc/localtime.
1564 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1565 hw.usb.* and is now consistent again with previous releases.
1568 802.11 monitor mode support was revised and driver api's were changed.
1569 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1570 of DLT_IEEE802_11. No user-visible data structures were changed but
1571 applications that use DLT_IEEE802_11 may require changes.
1572 Bump __FreeBSD_version to 800088.
1575 The layout of the following structs has changed: sysctl_oid,
1576 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1577 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1578 panics may be experienced. World rebuild is required for
1579 correctly checking networking state from userland.
1580 Bump __FreeBSD_version to 800085.
1583 MLDv2 and Source-Specific Multicast (SSM) have been merged
1584 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1585 The implementation of SSM within FreeBSD's IPv6 stack closely
1586 follows the IPv4 implementation.
1588 For kernel developers:
1590 * The most important changes are that the ip6_output() and
1591 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1592 and this lock has been downgraded to a non-recursive mutex.
1594 * As with the changes to the IPv4 stack to support SSM, filtering
1595 of inbound multicast traffic must now be performed by transport
1596 protocols within the IPv6 stack. This does not apply to TCP and
1597 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1599 * The KPIs used by IPv6 multicast are similar to those used by
1600 the IPv4 stack, with the following differences:
1601 * im6o_mc_filter() is analogous to imo_multicast_filter().
1602 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1603 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1604 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1605 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1606 for MLDv1 have an additional 'timer' argument which is used to
1607 jitter the initial membership report for the solicited-node
1608 multicast membership on-link.
1609 * This is not strictly needed for MLDv2, which already jitters
1610 its report transmissions. However, the 'timer' argument is
1611 preserved in case MLDv1 is active on the interface.
1613 * The KAME linked-list based IPv6 membership implementation has
1614 been refactored to use a vector similar to that used by the IPv4
1616 Code which maintains a list of its own multicast memberships
1617 internally, e.g. carp, has been updated to reflect the new
1620 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1621 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1622 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1623 implementation constraint which needs to be addressed in HEAD.
1625 For application developers:
1627 * The changes are broadly similar to those made for the IPv4
1630 * The use of IPv4 and IPv6 multicast socket options on the same
1631 socket, using mapped addresses, HAS NOT been tested or supported.
1633 * There are a number of issues with the implementation of various
1634 IPv6 multicast APIs which need to be resolved in the API surface
1635 before the implementation is fully compatible with KAME userland
1636 use, and these are mostly to do with interface index treatment.
1638 * The literature available discusses the use of either the delta / ASM
1639 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1640 using setsourcefilter(3)/getsourcefilter(3). For more information
1641 please refer to RFC 3768, 'Socket Interface Extensions for
1642 Multicast Source Filters'.
1644 * Applications which use the published RFC 3678 APIs should be fine.
1646 For systems administrators:
1648 * The mtest(8) utility has been refactored to support IPv6, in
1649 addition to IPv4. Interface addresses are no longer accepted
1650 as arguments, their names must be used instead. The utility
1651 will map the interface name to its first IPv4 address as
1652 returned by getifaddrs(3).
1654 * The ifmcstat(8) utility has also been updated to print the MLDv2
1655 endpoint state and source filter lists via sysctl(3).
1657 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1658 loopback of IPv6 multicast datagrams by default; it defaults to 1
1659 to preserve the existing behaviour. Disabling multicast loopback is
1660 recommended for optimal system performance.
1662 * The IPv6 MROUTING code has been changed to examine this sysctl
1663 instead of attempting to perform a group lookup before looping
1664 back forwarded datagrams.
1666 Bump __FreeBSD_version to 800084.
1669 Implement low-level Bluetooth HCI API.
1670 Bump __FreeBSD_version to 800083.
1673 The layout of struct malloc_type, used by modules to register new
1674 memory allocation types, has changed. Most modules will need to
1675 be rebuilt or panics may be experienced.
1676 Bump __FreeBSD_version to 800081.
1679 Anticipate overflowing inp_flags - add inp_flags2.
1680 This changes most offsets in inpcb, so checking v4 connection
1681 state will require a world rebuild.
1682 Bump __FreeBSD_version to 800080.
1685 Add an llentry to struct route and struct route_in6. Modules
1686 embedding a struct route will need to be recompiled.
1687 Bump __FreeBSD_version to 800079.
1690 The size of rt_metrics_lite and by extension rtentry has changed.
1691 Networking administration apps will need to be recompiled.
1692 The route command now supports show as an alias for get, weighting
1693 of routes, sticky and nostick flags to alter the behavior of stateful
1695 Bump __FreeBSD_version to 800078.
1698 Do not use Giant for kbdmux(4) locking. This is wrong and
1699 apparently causing more problems than it solves. This will
1700 re-open the issue where interrupt handlers may race with
1701 kbdmux(4) in polling mode. Typical symptoms include (but
1702 not limited to) duplicated and/or missing characters when
1703 low level console functions (such as gets) are used while
1704 interrupts are enabled (for example geli password prompt,
1705 mountroot prompt etc.). Disabling kbdmux(4) may help.
1708 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1709 kernel modules referencing any of the above need to be recompiled.
1710 Bump __FreeBSD_version to 800075.
1713 GEOM_PART has become the default partition slicer for storage devices,
1714 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1715 introduces some changes:
1717 MSDOS/EBR: the devices created from MSDOS extended partition entries
1718 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1719 to devices with offset-based names. fstabs may need to be modified.
1721 BSD: the "geometry does not match label" warning is harmless in most
1722 cases but it points to problems in file system misalignment with
1723 disk geometry. The "c" partition is now implicit, covers the whole
1724 top-level drive and cannot be (mis)used by users.
1726 General: Kernel dumps are now not allowed to be written to devices
1727 whose partition types indicate they are meant to be used for file
1728 systems (or, in case of MSDOS partitions, as something else than
1731 Most of these changes date approximately from 200812.
1734 The uscanner(4) driver has been removed from the kernel. This follows
1735 Linux removing theirs in 2.6 and making libusb the default interface
1736 (supported by sane).
1739 The multicast forwarding code has been cleaned up. netstat(1)
1740 only relies on KVM now for printing bandwidth upcall meters.
1741 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1742 ip6_mroute_mod respectively. The config(5) options for statically
1743 compiling this code remain the same, i.e. 'options MROUTING'.
1746 Support for the IFF_NEEDSGIANT network interface flag has been
1747 removed, which means that non-MPSAFE network device drivers are no
1748 longer supported. In particular, if_ar, if_sr, and network device
1749 drivers from the old (legacy) USB stack can no longer be built or
1753 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1754 a bunch of new language catalog files have also been added.
1755 This means that some common libc messages are now localized and
1756 they depend on the LC_MESSAGES environmental variable.
1759 The k8temp(4) driver has been renamed to amdtemp(4) since
1760 support for Family 10 and Family 11 CPU families was added.
1763 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1764 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1766 For kernel developers, the most important changes are that the
1767 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1768 and this lock has been downgraded to a non-recursive mutex.
1770 Transport protocols (UDP, Raw IP) are now responsible for filtering
1771 inbound multicast traffic according to group membership and source
1772 filters. The imo_multicast_filter() KPI exists for this purpose.
1773 Transports which do not use multicast (SCTP, TCP) already reject
1774 multicast by default. Forwarding and receive performance may improve
1775 as a mutex acquisition is no longer needed in the ip_input()
1776 low-level input path. in_addmulti() and in_delmulti() are shimmed
1777 to new KPIs which exist to support SSM in-kernel.
1779 For application developers, it is recommended that loopback of
1780 multicast datagrams be disabled for best performance, as this
1781 will still cause the lock to be taken for each looped-back
1782 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1783 be tuned to 0 to disable loopback by default; it defaults to 1
1784 to preserve the existing behaviour.
1786 For systems administrators, to obtain best performance with
1787 multicast reception and multiple groups, it is always recommended
1788 that a card with a suitably precise hash filter is used. Hash
1789 collisions will still result in the lock being taken within the
1790 transport protocol input path to check group membership.
1792 If deploying FreeBSD in an environment with IGMP snooping switches,
1793 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1794 enabled; this forces 224.0.0.0/24 group membership to be announced
1797 The size of 'struct igmpstat' has changed; netstat needs to be
1798 recompiled to reflect this.
1799 Bump __FreeBSD_version to 800070.
1802 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1803 updated to use it. This requires a buildworld/installworld in order to
1804 update the library and dependencies (usbconfig, etc). Its advisable to
1805 rebuild all ports which uses libusb. More specific directions are given
1806 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1807 libusb are no longer required and can be removed.
1810 A workaround is committed to allow the creation of System V shared
1811 memory segment of size > 2 GB on the 64-bit architectures.
1812 Due to a limitation of the existing ABI, the shm_segsz member
1813 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1814 wrong for large segments. Note that limits must be explicitly
1815 raised to allow such segments to be created.
1818 The layout of struct ifnet has changed, requiring a rebuild of all
1819 network device driver modules.
1822 The /dev handling for the new USB stack has changed, a
1823 buildworld/installworld is required for libusb20.
1826 The new USB2 stack has now been permanently moved in and all kernel and
1827 module names reverted to their previous values (eg, usb, ehci, ohci,
1828 ums, ...). The old usb stack can be compiled in by prefixing the name
1829 with the letter 'o', the old usb modules have been removed.
1830 Updating entry 20090216 for xorg and 20090215 for libmap may still
1834 The rc.conf(5) option if_up_delay has been renamed to
1835 defaultroute_delay to better reflect its purpose. If you have
1836 customized this setting in /etc/rc.conf you need to update it to
1840 xorg 7.4 wants to configure its input devices via hald which does not
1841 yet work with USB2. If the keyboard/mouse does not work in xorg then
1843 Option "AllowEmptyInput" "off"
1844 to your ServerLayout section. This will cause X to use the configured
1845 kbd and mouse sections from your xorg.conf.
1848 The GENERIC kernels for all architectures now default to the new USB2
1849 stack. No kernel config options or code have been removed so if a
1850 problem arises please report it and optionally revert to the old USB
1851 stack. If you are loading USB kernel modules or have a custom kernel
1852 that includes GENERIC then ensure that usb names are also changed over,
1853 eg uftdi -> usb2_serial_ftdi.
1855 Older programs linked against the ports libusb 0.1 need to be
1856 redirected to the new stack's libusb20. /etc/libmap.conf can
1858 # Map old usb library to new one for usb2 stack
1859 libusb-0.1.so.8 libusb20.so.1
1862 All USB ethernet devices now attach as interfaces under the name ueN
1863 (eg. ue0). This is to provide a predictable name as vendors often
1864 change usb chipsets in a product without notice.
1867 The ichsmb(4) driver has been changed to require SMBus slave
1868 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1869 All of the other SMBus controller drivers require left-justified
1870 slave addresses, so this change makes all the drivers provide the
1874 INET6 statistics (struct ip6stat) was updated.
1875 netstat(1) needs to be recompiled.
1878 NTFS has been removed from GENERIC kernel on amd64 to match
1879 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1880 will load ntfs.ko module automatically when NTFS support is
1881 actually needed, unless ntfs.ko is not installed or security
1882 level prohibits loading kernel modules. If either is the case,
1883 "options NTFS" has to be added into kernel config.
1886 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1887 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1888 800061. User space tools that rely on the size of struct tcpcb in
1889 tcp_var.h (e.g. sockstat) need to be recompiled.
1892 ng_tty(4) module updated to match the new TTY subsystem.
1893 Due to API change, user-level applications must be updated.
1894 New API support added to mpd5 CVS and expected to be present
1895 in next mpd5.3 release.
1898 With __FreeBSD_version 800060 the makefs tool is part of
1899 the base system (it was a port).
1902 The afdata and ifnet locks have been changed from mutexes to
1903 rwlocks, network modules will need to be re-compiled.
1906 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1907 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1908 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1909 architecture and 40 bytes on 64-bit architecture. The userland
1910 applications "arp" and "ndp" have been updated accordingly.
1911 The output from "netstat -r" shows only routing entries and
1912 none of the L2 information.
1915 __FreeBSD_version 800057 marks the switchover from the
1916 binary ath hal to source code. Users must add the line:
1918 options AH_SUPPORT_AR5416
1920 to their kernel config files when specifying:
1924 The ath_hal module no longer exists; the code is now compiled
1925 together with the driver in the ath module. It is now
1926 possible to tailor chip support (i.e. reduce the set of chips
1927 and thereby the code size); consult ath_hal(4) for details.
1930 __FreeBSD_version 800054 adds memory barriers to
1931 <machine/atomic.h>, new interfaces to ifnet to facilitate
1932 multiple hardware transmit queues for cards that support
1933 them, and a lock-less ring-buffer implementation to
1934 enable drivers to more efficiently manage queueing of
1938 A new version of ZFS (version 13) has been merged to -HEAD.
1939 This version has zpool attribute "listsnapshots" off by
1940 default, which means "zfs list" does not show snapshots,
1941 and is the same as Solaris behavior.
1944 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1947 The uhci, ohci, ehci and slhci USB Host controller drivers have
1948 been put into separate modules. If you load the usb module
1949 separately through loader.conf you will need to load the
1950 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1951 controller add the following to loader.conf:
1957 The ABI used by the PMC toolset has changed. Please keep
1958 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1962 atapci kernel module now includes only generic PCI ATA
1963 driver. AHCI driver moved to ataahci kernel module.
1964 All vendor-specific code moved into separate kernel modules:
1965 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1966 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1967 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1968 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1971 The TTY subsystem of the kernel has been replaced by a new
1972 implementation, which provides better scalability and an
1973 improved driver model. Most common drivers have been migrated to
1974 the new TTY subsystem, while others have not. The following
1975 drivers have not yet been ported to the new TTY layer:
1978 cy, digi, rc, rp, sio
1984 ng_h4, ng_tty, ppp, sl, snp
1986 Adding these drivers to your kernel configuration file shall
1987 cause compilation to fail.
1990 ntpd has been upgraded to 4.2.4p5.
1993 OpenSSH has been upgraded to 5.1p1.
1995 For many years, FreeBSD's version of OpenSSH preferred DSA
1996 over RSA for host and user authentication keys. With this
1997 upgrade, we've switched to the vendor's default of RSA over
1998 DSA. This may cause upgraded clients to warn about unknown
1999 host keys even for previously known hosts. Users should
2000 follow the usual procedure for verifying host keys before
2001 accepting the RSA key.
2003 This can be circumvented by setting the "HostKeyAlgorithms"
2004 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
2007 Please note that the sequence of keys offered for
2008 authentication has been changed as well. You may want to
2009 specify IdentityFile in a different order to revert this
2013 The sio(4) driver has been removed from the i386 and amd64
2014 kernel configuration files. This means uart(4) is now the
2015 default serial port driver on those platforms as well.
2017 To prevent collisions with the sio(4) driver, the uart(4) driver
2018 uses different names for its device nodes. This means the
2019 onboard serial port will now most likely be called "ttyu0"
2020 instead of "ttyd0". You may need to reconfigure applications to
2021 use the new device names.
2023 When using the serial port as a boot console, be sure to update
2024 /boot/device.hints and /etc/ttys before booting the new kernel.
2025 If you forget to do so, you can still manually specify the hints
2026 at the loader prompt:
2028 set hint.uart.0.at="isa"
2029 set hint.uart.0.port="0x3F8"
2030 set hint.uart.0.flags="0x10"
2031 set hint.uart.0.irq="4"
2035 The gpt(8) utility has been removed. Use gpart(8) to partition
2039 The version that Linuxulator emulates was changed from 2.4.2
2040 to 2.6.16. If you experience any problems with Linux binaries
2041 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2042 if it fixes the problem contact emulation mailing list.
2045 ISDN4BSD (I4B) was removed from the src tree. You may need to
2046 update a your kernel configuration and remove relevant entries.
2049 I have checked in code to support multiple routing tables.
2050 See the man pages setfib(1) and setfib(2).
2051 This is a hopefully backwards compatible version,
2052 but to make use of it you need to compile your kernel
2053 with options ROUTETABLES=2 (or more up to 16).
2056 The 802.11 wireless support was redone to enable multi-bss
2057 operation on devices that are capable. The underlying device
2058 is no longer used directly but instead wlanX devices are
2059 cloned with ifconfig. This requires changes to rc.conf files.
2060 For example, change:
2061 ifconfig_ath0="WPA DHCP"
2064 ifconfig_wlan0="WPA DHCP"
2065 see rc.conf(5) for more details. In addition, mergemaster of
2066 /etc/rc.d is highly recommended. Simultaneous update of userland
2067 and kernel wouldn't hurt either.
2069 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2070 modules were merged into the base wlan module. All references
2071 to these modules (e.g. in kernel config files) must be removed.
2074 psm(4) has gained write(2) support in native operation level.
2075 Arbitrary commands can be written to /dev/psm%d and status can
2076 be read back from it. Therefore, an application is responsible
2077 for status validation and error recovery. It is a no-op in
2078 other operation levels.
2081 Support for KSE threading has been removed from the kernel. To
2082 run legacy applications linked against KSE libmap.conf may
2083 be used. The following libmap.conf may be used to ensure
2084 compatibility with any prior release:
2086 libpthread.so.1 libthr.so.1
2087 libpthread.so.2 libthr.so.2
2088 libkse.so.3 libthr.so.3
2091 The layout of struct vmspace has changed. This affects libkvm
2092 and any executables that link against libkvm and use the
2093 kvm_getprocs() function. In particular, but not exclusively,
2094 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2095 The effects are minimal, but it's advisable to upgrade world
2099 The latest em driver no longer has support in it for the
2100 82575 adapter, this is now moved to the igb driver. The
2101 split was done to make new features that are incompatible
2102 with older hardware easier to do.
2105 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2106 likewise the kernel option is now GEOM_LINUX_LVM.
2109 The default NFS mount mode has changed from UDP to TCP for
2110 increased reliability. If you rely on (insecurely) NFS
2111 mounting across a firewall you may need to update your
2115 Belatedly note the addition of m_collapse for compacting
2119 The fts(3) structures have been changed to use adequate
2120 integer types for their members and so to be able to cope
2121 with huge file trees. The old fts(3) ABI is preserved
2122 through symbol versioning in libc, so third-party binaries
2123 using fts(3) should still work, although they will not take
2124 advantage of the extended types. At the same time, some
2125 third-party software might fail to build after this change
2126 due to unportable assumptions made in its source code about
2127 fts(3) structure members. Such software should be fixed
2128 by its vendor or, in the worst case, in the ports tree.
2129 FreeBSD_version 800015 marks this change for the unlikely
2130 case that a portable fix is impossible.
2133 To upgrade to -current after this date, you must be running
2134 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2135 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2138 The ADAPTIVE_GIANT kernel option has been retired because its
2139 functionality is the default now.
2142 The AT keyboard emulation of sunkbd(4) has been turned on
2143 by default. In order to make the special symbols of the Sun
2144 keyboards driven by sunkbd(4) work under X these now have
2145 to be configured the same way as Sun USB keyboards driven
2146 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2148 Option "XkbLayout" "us"
2149 Option "XkbRules" "xorg"
2150 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2153 It has been decided that it is desirable to provide ABI
2154 backwards compatibility to the FreeBSD 4/5/6 versions of the
2155 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2156 broken with the introduction of PCI domain support (see the
2157 20070930 entry). Unfortunately, this required the ABI of
2158 PCIOCGETCONF to be broken again in order to be able to
2159 provide backwards compatibility to the old version of that
2160 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2161 again. As for prominent ports this affects neither pciutils
2162 nor xorg-server this time, the hal port needs to be rebuilt
2166 The misnamed kthread_create() and friends have been renamed
2167 to kproc_create() etc. Many of the callers already
2168 used kproc_start()..
2169 I will return kthread_create() and friends in a while
2170 with implementations that actually create threads, not procs.
2171 Renaming corresponds with version 800002.
2180 Avoid using make -j when upgrading. While generally safe, there are
2181 sometimes problems using -j to upgrade. If your upgrade fails with
2182 -j, please try again without -j. From time to time in the past there
2183 have been problems using -j with buildworld and/or installworld. This
2184 is especially true when upgrading between "distant" versions (eg one
2185 that cross a major release boundary or several minor releases, or when
2186 several months have passed on the -current branch).
2188 Sometimes, obscure build problems are the result of environment
2189 poisoning. This can happen because the make utility reads its
2190 environment when searching for values for global variables. To run
2191 your build attempts in an "environmental clean room", prefix all make
2192 commands with 'env -i '. See the env(1) manual page for more details.
2194 When upgrading from one major version to another it is generally best
2195 to upgrade to the latest code in the currently installed branch first,
2196 then do an upgrade to the new branch. This is the best-tested upgrade
2197 path, and has the highest probability of being successful. Please try
2198 this approach before reporting problems with a major version upgrade.
2200 When upgrading a live system, having a root shell around before
2201 installing anything can help undo problems. Not having a root shell
2202 around can lead to problems if pam has changed too much from your
2203 starting point to allow continued authentication after the upgrade.
2207 When upgrading the boot ZFS pool to a new version, always follow
2210 1.) recompile and reinstall the ZFS boot loader and boot block
2211 (this is part of "make buildworld" and "make installworld")
2213 2.) update the ZFS boot block on your boot drive
2215 The following example updates the ZFS boot block on the first
2216 partition (freebsd-boot) of a GPT partitioned drive ad0:
2217 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2219 Non-boot pools do not need these updates.
2223 If you are updating from a prior version of FreeBSD (even one just
2224 a few days old), you should follow this procedure. It is the most
2225 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2227 make kernel-toolchain
2228 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2229 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2231 To test a kernel once
2232 ---------------------
2233 If you just want to boot a kernel once (because you are not sure
2234 if it works, or if you want to boot a known bad kernel to provide
2235 debugging information) run
2236 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2237 nextboot -k testkernel
2239 To just build a kernel when you know that it won't mess you up
2240 --------------------------------------------------------------
2241 This assumes you are already running a CURRENT system. Replace
2242 ${arch} with the architecture of your machine (e.g. "i386",
2243 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2245 cd src/sys/${arch}/conf
2246 config KERNEL_NAME_HERE
2247 cd ../compile/KERNEL_NAME_HERE
2252 If this fails, go to the "To build a kernel" section.
2254 To rebuild everything and install it on the current system.
2255 -----------------------------------------------------------
2256 # Note: sometimes if you are running current you gotta do more than
2257 # is listed here if you are upgrading from a really old current.
2259 <make sure you have good level 0 dumps>
2261 make kernel KERNCONF=YOUR_KERNEL_HERE
2263 <reboot in single user> [3]
2270 To cross-install current onto a separate partition
2271 --------------------------------------------------
2272 # In this approach we use a separate partition to hold
2273 # current's root, 'usr', and 'var' directories. A partition
2274 # holding "/", "/usr" and "/var" should be about 2GB in
2277 <make sure you have good level 0 dumps>
2280 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2281 <maybe newfs current's root partition>
2282 <mount current's root partition on directory ${CURRENT_ROOT}>
2283 make installworld DESTDIR=${CURRENT_ROOT}
2284 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2285 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2286 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2287 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2288 <reboot into current>
2289 <do a "native" rebuild/install as described in the previous section>
2290 <maybe install compatibility libraries from ports/misc/compat*>
2294 To upgrade in-place from stable to current
2295 ----------------------------------------------
2296 <make sure you have good level 0 dumps>
2298 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2300 <reboot in single user> [3]
2307 Make sure that you've read the UPDATING file to understand the
2308 tweaks to various things you need. At this point in the life
2309 cycle of current, things change often and you are on your own
2310 to cope. The defaults can also change, so please read ALL of
2311 the UPDATING entries.
2313 Also, if you are tracking -current, you must be subscribed to
2314 freebsd-current@freebsd.org. Make sure that before you update
2315 your sources that you have read and understood all the recent
2316 messages there. If in doubt, please track -stable which has
2317 much fewer pitfalls.
2319 [1] If you have third party modules, such as vmware, you
2320 should disable them at this point so they don't crash your
2323 [3] From the bootblocks, boot -s, and then do
2328 adjkerntz -i # if CMOS is wall time
2329 Also, when doing a major release upgrade, it is required that
2330 you boot into single user mode to do the installworld.
2332 [4] Note: This step is non-optional. Failure to do this step
2333 can result in a significant reduction in the functionality of the
2334 system. Attempting to do it by hand is not recommended and those
2335 that pursue this avenue should read this file carefully, as well
2336 as the archives of freebsd-current and freebsd-hackers mailing lists
2337 for potential gotchas. The -U option is also useful to consider.
2338 See mergemaster(8) for more information.
2340 [5] Usually this step is a noop. However, from time to time
2341 you may need to do this if you get unknown user in the following
2342 step. It never hurts to do it all the time. You may need to
2343 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2344 install) after the buildworld before this step if you last updated
2345 from current before 20130425 or from -stable before 20130430.
2347 [6] This only deletes old files and directories. Old libraries
2348 can be deleted by "make delete-old-libs", but you have to make
2349 sure that no program is using those libraries anymore.
2351 [8] In order to have a kernel that can run the 4.x binaries needed to
2352 do an installworld, you must include the COMPAT_FREEBSD4 option in
2353 your kernel. Failure to do so may leave you with a system that is
2354 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2355 required to run the 5.x binaries on more recent kernels. And so on
2356 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2358 Make sure that you merge any new devices from GENERIC since the
2359 last time you updated your kernel config file.
2361 [9] When checking out sources, you must include the -P flag to have
2362 cvs prune empty directories.
2364 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2365 "?=" instead of the "=" assignment operator, so that buildworld can
2366 override the CPUTYPE if it needs to.
2368 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2369 not on the command line, or in /etc/make.conf. buildworld will
2370 warn if it is improperly defined.
2373 This file contains a list, in reverse chronological order, of major
2374 breakages in tracking -current. It is not guaranteed to be a complete
2375 list of such breakages, and only contains entries since October 10, 2007.
2376 If you need to see UPDATING entries from before that date, you will need
2377 to fetch an UPDATING file from an older FreeBSD release.
2379 Copyright information:
2381 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2383 Redistribution, publication, translation and use, with or without
2384 modification, in full or in part, in any form or format of this
2385 document are permitted without further permission from the author.
2387 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2388 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2389 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2390 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2391 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2392 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2393 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2394 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2395 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2396 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2397 POSSIBILITY OF SUCH DAMAGE.
2399 Contact Warner Losh if you have any questions about your use of