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 20160725 p20 FreeBSD-SA-16:25.bspatch
20 FreeBSD-EN-16:09.freebsd-update
22 Fix bspatch heap overflow vulnerability. [SA-16:25]
24 Fix freebsd-update(8) support of FreeBSD 11.0 release
25 distribution. [EN-16:09]
27 20160604 p19 FreeBSD-SA-16:24.ntp
29 Fix multiple vulnerabilities of ntp.
31 20160531 p18 FreeBSD-SA-16:20.linux
32 FreeBSD-SA-16:21.43bsd
33 FreeBSD-SA-16:22.libarchive
35 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
36 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
37 Fix directory traversal in cpio(1). [SA-16:22]
39 20160517 p17 FreeBSD-SA-16:18.atkbd
40 FreeBSD-SA-16:19.sendmsg
42 Fix buffer overflow in keyboard driver. [SA-16:18]
44 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
46 20160504 p16 FreeBSD-SA-16:17.openssl
50 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
52 Fix excessive latency in x86 IPI delivery. [EN-16:07]
54 Fix memory leak in ZFS. [EN-16:08]
56 20160429 p15 FreeBSD-SA-16:16.ntp
58 Fix multiple vulnerabilities of ntp.
60 20160316 p14 FreeBSD-SA-16:14.openssh-xauth
61 FreeBSD-SA-16:15.sysarch
62 FreeBSD-EN-16:04.hyperv
63 FreeBSD-EN-16:05.hv_netvsc
65 Fix OpenSSH xauth(1) command injection. [SA-16:14]
66 Fix incorrect argument validation in sysarch(2). [SA-16:15]
67 Fix Hyper-V KVP (Key-Value Pair) daemon indefinite sleep. [EN-16:04]
68 Fix hv_netvsc(4) incorrect TCP/IP checksums. [EN-16:05]
70 20160303 p13 FreeBSD-SA-16:12.openssl
72 Fix multiple vulnerabilities of OpenSSL.
74 20160130 p12 FreeBSD-SA-16:11.openssl
76 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
78 20160127 p11 FreeBSD-SA-16:09.ntp
79 FreeBSD-SA-16:10.linux
81 Fix multiple vulnerabilities of ntp. [SA-16:09]
83 Fix Linux compatibility layer issetugid(2) system call
84 vulnerability. [SA-16:10]
86 20160114 p10 FreeBSD-SA-16:07.openssh
88 Fix OpenSSH client information leak. [SA-16:07]
90 20160114 p9 FreeBSD-EN-16:01.filemon
92 FreeBSD-EN-16:03.yplib
95 FreeBSD-SA-16:03.linux
96 FreeBSD-SA-16:04.linux
98 FreeBSD-SA-16:06.bsnmpd
100 Fix multiple stability and locking problems in filemon(4). [EN-16:01]
101 Fix pf(4) generating bad TCP checksums. [EN-16:02]
102 Fix infinite loop in YP/NIS client library. [EN-16:03]
103 Fix remote denial of service in SCTP. [SA-16:01]
104 Update NTP to 4.2.8p5. [SA-16:02]
105 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
106 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
107 Fix crash in TCP MD5 signatures. [SA-16:05]
108 Fix insecure default permissions for snmpd.config. [SA-16:06]
110 20151205 p8 FreeBSD-SA-15:26.openssl
112 Fix multiple OpenSSL vulnerabilities. [SA-15:26]
114 20151104 p7 FreeBSD-SA-15:25.ntp [revised]
115 FreeBSD-EN-15:19.kqueue
118 Fix regression in ntpd(8) lacking support for RAWDCF reference
119 clock in 10.2-RELEASE-p6. [SA-15:25]
121 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
123 Fix applications exiting due to segmentation violation on a correct
124 memory address. [EN-15:20.vm]
126 20151026: p6 FreeBSD-SA-15:25.ntp
128 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
130 20151002: p5 FreeBSD-SA-15:24.rpcbind [revised]
131 Revised patch to address a regression that prevents NIS from working.
133 20150929: p4 FreeBSD-SA-15:24.rpcbind
135 Fix rpcbind(8) remote denial of service. [SA-15:24]
137 20150916: p3 FreeBSD-EN-15:16.pw
138 FreeBSD-EN-15:17.libc
141 Fix regression in pw(8) when creating numeric users or groups.
144 Fix libc handling of signals for multi-threaded processes.
147 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
149 20150825: p2 FreeBSD-SA-15:22.openssh
151 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
153 Fix insufficient check of unsupported pkg(7) signature methods.
156 20150818: p1 FreeBSD-SA-15:20.expat
157 FreeBSD-EN-15:11.toolchain
158 FreeBSD-EN-15:12.netstat
159 FreeBSD-EN-15:13.vidcontrol
161 Fix multiple integer overflows in expat (libbsdxml) XML parser.
164 Fix make(1) syntax errors when upgrading from 9.x and earlier.
167 Fix incorrect netstat(1) data handling on 32-bit systems.
170 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
176 The default Unbound configuration now enables remote control
177 using a local socket. Users who have already enabled the
178 local_unbound service should regenerate their configuration
179 by running "service local_unbound setup" as root.
182 An additional fix for the issue described in the 20150614 sendmail
183 entry below has been been committed in revision 284786.
186 The fix for the issue described in the 20150614 sendmail entry
187 below has been been committed in revision 284485. The work
188 around described in that entry is no longer needed unless the
189 default setting is overridden by a confDH_PARAMETERS configuration
190 setting of '5' or pointing to a 512 bit DH parameter file.
193 The import of openssl to address the FreeBSD-SA-15:10.openssl
194 security advisory includes a change which rejects handshakes
195 with DH parameters below 768 bits. sendmail releases prior
196 to 8.15.2 (not yet released), defaulted to a 512 bit
197 DH parameter setting for client connections. To work around
198 this interoperability, sendmail can be configured to use a
199 2048 bit DH parameter by:
201 1. Edit /etc/mail/`hostname`.mc
202 2. If a setting for confDH_PARAMETERS does not exist or
203 exists and is set to a string beginning with '5',
205 3. If a setting for confDH_PARAMETERS exists and is set to
206 a file path, create a new file with:
207 openssl dhparam -out /path/to/file 2048
208 4. Rebuild the .cf file:
209 cd /etc/mail/; make; make install
211 cd /etc/mail/; make restart
213 A sendmail patch is coming, at which time this file will be
217 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
218 defined in symlink(7); previously symlinks were silently ignored.
221 The const qualifier has been removed from iconv(3) to comply with
222 POSIX. The ports tree is aware of this from r384038 onwards.
225 At svn r275807, The default linux compat kernel ABI has been adjusted
226 to 2.6.18 in support of the linux-c6 compat ports infrastructure
227 update. If you wish to continue using the linux-f10 compat ports,
228 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
229 encouraged to update their linux-compat packages to linux-c6 during
230 their next update cycle.
232 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
235 pjdfstest has been integrated into kyua as an opt-in test suite.
236 Please see share/doc/pjdfstest/README for a more details on how to
243 The ofwfb driver, used to provide a graphics console on PowerPC when
244 using vt(4), no longer allows mmap() of all of physical memory. This
245 will prevent Xorg on PowerPC with some ATI graphics cards from
246 initializing properly unless x11-servers/xorg-server is updated to
250 The libatf-c and libatf-c++ major versions were downgraded to 0 and
251 1 respectively to match the upstream numbers. They were out of
252 sync because, when they were originally added to FreeBSD, the
253 upstream versions were not respected. These libraries are private
254 and not yet built by default, so renumbering them should be a
255 non-issue. However, unclean source trees will yield broken test
256 programs once the operator executes "make delete-old-libs" after a
259 Additionally, the atf-sh binary was made private by moving it into
260 /usr/libexec/. Already-built shell test programs will keep the
261 path to the old binary so they will break after "make delete-old"
264 If you are using WITH_TESTS=yes (not the default), wipe the object
265 tree and rebuild from scratch to prevent spurious test failures.
266 This is only needed once: the misnumbered libraries and misplaced
267 binaries have been added to OptionalObsoleteFiles.inc so they will
268 be removed during a clean upgrade.
271 The ixgbe tunables now match their sysctl counterparts, for example:
272 hw.ixgbe.enable_aim => hw.ix.enable_aim
273 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
276 The NFSv4.1 server committed by r269398 changes the internal
277 function call interfaces used between the NFS and krpc modules.
278 As such, __FreeBSD_version was bumped.
281 The default unbound configuration has been modified to address
282 issues with reverse lookups on networks that use private
283 address ranges. If you use the local_unbound service, run
284 "service local_unbound setup" as root to regenerate your
285 configuration, then "service local_unbound reload" to load the
289 It is no longer necessary to include the dwarf version in your DEBUG
290 options in your kernel config file. The bug that required it to be
291 placed in the config file has bene fixed. DEBUG should now just
292 contain -g. The build system will automatically update things
293 to do the right thing.
296 Several ABI breaking changes were merged to CTL and new iSCSI code.
297 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
298 iscsictl need to be rebuilt to work with a new kernel.
301 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
302 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
303 which differs from the behaviour controlled by this knob.)
306 On i386 and amd64 systems, the onifconsole flag is now set by default
307 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
308 as a login TTY if it is set in the bootloader as an active kernel
309 console. No changes in behavior should result otherwise. To revert to
310 the previous behavior, set ttyu0 to "off" in /etc/ttys.
313 Clang and llvm have been upgraded to 3.4.1 release.
316 Clang and llvm have been upgraded to 3.4 release.
319 If a Makefile in a tests/ directory was auto-generating a Kyuafile
320 instead of providing an explicit one, this would prevent such
321 Makefile from providing its own Kyuafile in the future during
322 NO_CLEAN builds. This has been fixed in the Makefiles but manual
323 intervention is needed to clean an objdir if you use NO_CLEAN:
324 # find /usr/obj -name Kyuafile | xargs rm -f
327 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
328 capability mode support. Please note that enabling the feature in
329 kernel is still highly recommended.
332 OpenSSH is now built with sandbox support, and will use sandbox as
333 the default privilege separation method. This requires Capsicum
334 capability mode support in kernel.
337 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
338 been deprecated and will not be part of FreeBSD 11.0 and later
339 releases. If you use this driver, please consider switching to
340 the nfe(4) driver instead.
346 The behavior of gss_pseudo_random() for the krb5 mechanism
347 has changed, for applications requesting a longer random string
348 than produced by the underlying enctype's pseudo-random() function.
349 In particular, the random string produced from a session key of
350 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
351 be different at the 17th octet and later, after this change.
352 The counter used in the PRF+ construction is now encoded as a
353 big-endian integer in accordance with RFC 4402.
354 __FreeBSD_version is bumped to 1000701.
357 The WITHOUT_ATF build knob has been removed and its functionality
358 has been subsumed into the more generic WITHOUT_TESTS. If you were
359 using the former to disable the build of the ATF libraries, you
360 should change your settings to use the latter.
363 The default version of mtree is nmtree which is obtained from
364 NetBSD. The output is generally the same, but may vary
365 slightly. If you found you need identical output adding
366 "-F freebsd9" to the command line should do the trick. For the
367 time being, the old mtree is available as fmtree.
370 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
371 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
372 1.1.4_8 and verify bsdyml not linked in, before running "make
374 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
376 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
379 The rc.d/jail script has been updated to support jail(8)
380 configuration file. The "jail_<jname>_*" rc.conf(5) variables
381 for per-jail configuration are automatically converted to
382 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
383 This is transparently backward compatible. See below about some
384 incompatibilities and rc.conf(5) manual page for more details.
386 These variables are now deprecated in favor of jail(8) configuration
387 file. One can use "rc.d/jail config <jname>" command to generate
388 a jail(8) configuration file in /var/run/jail.<jname>.conf without
389 running the jail(8) utility. The default pathname of the
390 configuration file is /etc/jail.conf and can be specified by
391 using $jail_conf or $jail_<jname>_conf variables.
393 Please note that jail_devfs_ruleset accepts an integer at
394 this moment. Please consider to rewrite the ruleset name
398 BIND has been removed from the base system. If all you need
399 is a local resolver, simply enable and start the local_unbound
400 service instead. Otherwise, several versions of BIND are
401 available in the ports tree. The dns/bind99 port is one example.
403 With this change, nslookup(1) and dig(1) are no longer in the base
404 system. Users should instead use host(1) and drill(1) which are
405 in the base system. Alternatively, nslookup and dig can
406 be obtained by installing the dns/bind-tools port.
409 With the addition of unbound(8), a new unbound user is now
410 required during installworld. "mergemaster -p" can be used to
411 add the user prior to installworld, as documented in the handbook.
414 OpenSSH is now built with DNSSEC support, and will by default
415 silently trust signed SSHFP records. This can be controlled with
416 the VerifyHostKeyDNS client configuration setting. DNSSEC support
417 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
420 The GNU Compiler Collection and C++ standard library (libstdc++)
421 are no longer built by default on platforms where clang is the system
422 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
426 The PROCDESC kernel option is now part of the GENERIC kernel
427 configuration and is required for the rwhod(8) to work.
428 If you are using custom kernel configuration, you should include
432 The API and ABI related to the Capsicum framework was modified
433 in backward incompatible way. The userland libraries and programs
434 have to be recompiled to work with the new kernel. This includes the
435 following libraries and programs, but the whole buildworld is
436 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
437 kdump, procstat, rwho, rwhod, uniq.
440 AES-NI intrinsic support has been added to gcc. The AES-NI module
441 has been updated to use this support. A new gcc is required to build
442 the aesni module on both i386 and amd64.
445 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
446 Thus "device padlock_rng" and "device rdrand_rng" should be
447 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
450 WITH_ICONV has been split into two feature sets. WITH_ICONV now
451 enables just the iconv* functionality and is now on by default.
452 WITH_LIBICONV_COMPAT enables the libiconv api and link time
453 compatability. Set WITHOUT_ICONV to build the old way.
454 If you have been using WITH_ICONV before, you will very likely
455 need to turn on WITH_LIBICONV_COMPAT.
458 INVARIANTS option now enables DEBUG for code with OpenSolaris and
459 Illumos origin, including ZFS. If you have INVARIANTS in your
460 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
462 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
463 locks if WITNESS option was set. Because that generated a lot of
464 witness(9) reports and all of them were believed to be false
465 positives, this is no longer done. New option OPENSOLARIS_WITNESS
466 can be used to achieve the previous behavior.
469 Timer values in IPv6 data structures now use time_uptime instead
470 of time_second. Although this is not a user-visible functional
471 change, userland utilities which directly use them---ndp(8),
472 rtadvd(8), and rtsold(8) in the base system---need to be updated
476 find -delete can now delete the pathnames given as arguments,
477 instead of only files found below them or if the pathname did
478 not contain any slashes. Formerly, the following error message
481 find: -delete: <path>: relative path potentially not safe
483 Deleting the pathnames given as arguments can be prevented
484 without error messages using -mindepth 1 or by changing
485 directory and passing "." as argument to find. This works in the
486 old as well as the new version of find.
489 Behavior of devfs rules path matching has been changed.
490 Pattern is now always matched against fully qualified devfs
491 path and slash characters must be explicitly matched by
492 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
493 subdirectories must be reviewed.
496 The default ARM ABI has changed to the ARM EABI. The old ABI is
497 incompatible with the ARM EABI and all programs and modules will
498 need to be rebuilt to work with a new kernel.
500 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
502 NOTE: Support for the old ABI will be removed in the future and
503 users are advised to upgrade.
506 pkg_install has been disconnected from the build if you really need it
507 you should add WITH_PKGTOOLS in your src.conf(5).
510 Most of network statistics structures were changed to be able
511 keep 64-bits counters. Thus all tools, that work with networking
512 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
515 Fix targets that run multiple make's to use && rather than ;
516 so that subsequent steps depend on success of previous.
518 NOTE: if building 'universe' with -j* on stable/8 or stable/9
519 it would be better to start the build using bmake, to avoid
520 overloading the machine.
523 Fix a bug that allowed a tracing process (e.g. gdb) to write
524 to a memory-mapped file in the traced process's address space
525 even if neither the traced process nor the tracing process had
526 write access to that file.
529 CVS has been removed from the base system. An exact copy
530 of the code is available from the devel/cvs port.
533 Some people report the following error after the switch to bmake:
535 make: illegal option -- J
536 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
538 *** [buildworld] Error code 2
540 this likely due to an old instance of make in
541 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
542 which src/Makefile will use that blindly, if it exists, so if
543 you see the above error:
545 rm -rf `make -V MAKEPATH`
550 Use bmake by default.
551 Whereas before one could choose to build with bmake via
552 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
553 make. The goal is to remove these knobs for 10-RELEASE.
555 It is worth noting that bmake (like gmake) treats the command
556 line as the unit of failure, rather than statements within the
557 command line. Thus '(cd some/where && dosomething)' is safer
558 than 'cd some/where; dosomething'. The '()' allows consistent
559 behavior in parallel build.
562 Fix a bug that allows NFS clients to issue READDIR on files.
565 The WITHOUT_IDEA option has been removed because
566 the IDEA patent expired.
569 The sysctl which controls TRIM support under ZFS has been renamed
570 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
574 The mergemaster command now uses the default MAKEOBJDIRPREFIX
575 rather than creating it's own in the temporary directory in
576 order allow access to bootstrapped versions of tools such as
577 install and mtree. When upgrading from version of FreeBSD where
578 the install command does not support -l, you will need to
579 install a new mergemaster command if mergemaster -p is required.
580 This can be accomplished with the command (cd src/usr.sbin/mergemaster
584 Legacy ATA stack, disabled and replaced by new CAM-based one since
585 FreeBSD 9.0, completely removed from the sources. Kernel modules
586 atadisk and atapi*, user-level tools atacontrol and burncd are
587 removed. Kernel option `options ATA_CAM` is now permanently enabled
591 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
592 and socketpair(2). Software, in particular Kerberos, may
593 automatically detect and use these during building. The resulting
594 binaries will not work on older kernels.
597 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
598 information, see the respective 20130304 entry).
601 Recent commits to callout(9) changed the size of struct callout,
602 so the KBI is probably heavily disturbed. Also, some functions
603 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
604 by macros. Every kernel module using it won't load, so rebuild
607 The ctl device has been re-enabled in GENERIC for i386 and amd64,
608 but does not initialize by default (because of the new CTL_DISABLE
609 option) to save memory. To re-enable it, remove the CTL_DISABLE
610 option from the kernel config file or set kern.cam.ctl.disable=0
611 in /boot/loader.conf.
614 The ctl device has been disabled in GENERIC for i386 and amd64.
615 This was done due to the extra memory being allocated at system
616 initialisation time by the ctl driver which was only used if
617 a CAM target device was created. This makes a FreeBSD system
618 unusable on 128MB or less of RAM.
621 A new compression method (lz4) has been merged to -HEAD. Please
622 refer to zpool-features(7) for more information.
624 Please refer to the "ZFS notes" section of this file for information
625 on upgrading boot ZFS pools.
628 A BSD-licensed patch(1) variant has been added and is installed
629 as bsdpatch, being the GNU version the default patch.
630 To inverse the logic and use the BSD-licensed one as default,
631 while having the GNU version installed as gnupatch, rebuild
632 and install world with the WITH_BSD_PATCH knob set.
635 Due to the use of the new -l option to install(1) during build
636 and install, you must take care not to directly set the INSTALL
637 make variable in your /etc/make.conf, /etc/src.conf, or on the
638 command line. If you wish to use the -C flag for all installs
639 you may be able to add INSTALL+=-C to /etc/make.conf or
643 The install(1) option -M has changed meaning and now takes an
644 argument that is a file or path to append logs to. In the
645 unlikely event that -M was the last option on the command line
646 and the command line contained at least two files and a target
647 directory the first file will have logs appended to it. The -M
648 option served little practical purpose in the last decade so its
649 use is expected to be extremely rare.
652 After switching to Clang as the default compiler some users of ZFS
653 on i386 systems started to experience stack overflow kernel panics.
654 Please consider using 'options KSTACK_PAGES=4' in such configurations.
657 GEOM_LABEL now mangles label names read from file system metadata.
658 Mangling affect labels containing spaces, non-printable characters,
659 '%' or '"'. Device names in /etc/fstab and other places may need to
663 By default, only the 10 most recent kernel dumps will be saved. To
664 restore the previous behaviour (no limit on the number of kernel dumps
665 stored in the dump directory) add the following line to /etc/rc.conf:
670 With the addition of auditdistd(8), a new auditdistd user is now
671 required during installworld. "mergemaster -p" can be used to
672 add the user prior to installworld, as documented in the handbook.
675 The sin6_scope_id member variable in struct sockaddr_in6 is now
676 filled by the kernel before passing the structure to the userland via
677 sysctl or routing socket. This means the KAME-specific embedded scope
678 id in sin6_addr.s6_addr[2] is always cleared in userland application.
679 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
680 __FreeBSD_version is bumped to 1000025.
683 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
684 This means that the world and kernel will be compiled with clang
685 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
686 and /usr/bin/cpp. To disable this behavior and revert to building
687 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
688 of current may need to bootstrap WITHOUT_CLANG first if the clang
689 build fails (its compatibility window doesn't extend to the 9 stable
693 The IPFIREWALL_FORWARD kernel option has been removed. Its
694 functionality now turned on by default.
697 The ZERO_COPY_SOCKET kernel option has been removed and
698 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
699 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
700 mechanism which is not safe and may result in kernel crashes.
701 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
702 driver supports disposeable external page sized mbuf storage.
703 Proper replacements for both zero-copy mechanisms are under
704 consideration and will eventually lead to complete removal
705 of the two kernel options.
708 The IPv4 network stack has been converted to network byte
709 order. The following modules need to be recompiled together
710 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
711 pf(4), ipfw(4), ng_ipfw(4), stf(4).
714 Support for non-MPSAFE filesystems was removed from VFS. The
715 VFS_VERSION was bumped, all filesystem modules shall be
719 All the non-MPSAFE filesystems have been disconnected from
720 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
721 portalfs, smbfs, xfs.
724 The interface cloning API and ABI has changed. The following
725 modules need to be recompiled together with kernel:
726 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
727 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
728 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
731 The sdhci driver was split in two parts: sdhci (generic SD Host
732 Controller logic) and sdhci_pci (actual hardware driver).
733 No kernel config modifications are required, but if you
734 load sdhc as a module you must switch to sdhci_pci instead.
737 Import the FUSE kernel and userland support into base system.
740 The GNU sort(1) program has been removed since the BSD-licensed
741 sort(1) has been the default for quite some time and no serious
742 problems have been reported. The corresponding WITH_GNU_SORT
746 The pfil(9) API/ABI for AF_INET family has been changed. Packet
747 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
751 The net80211(4) ABI has been changed to allow for improved driver
752 PS-POLL and power-save support. All wireless drivers need to be
753 recompiled to work with the new kernel.
756 The random(4) support for the VIA hardware random number
757 generator (`PADLOCK') is no longer enabled unconditionally.
758 Add the padlock_rng device in the custom kernel config if
759 needed. The GENERIC kernels on i386 and amd64 do include the
760 device, so the change only affects the custom kernel
764 The pf(4) packet filter ABI has been changed. pfctl(8) and
765 snmp_pf module need to be recompiled to work with new kernel.
768 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
769 to -HEAD. Pools that have empty_bpobj in active state can not be
770 imported read-write with ZFS implementations that do not support
771 this feature. For more information read the zpool-features(5)
775 The sparc64 ZFS loader has been changed to no longer try to auto-
776 detect ZFS providers based on diskN aliases but now requires these
777 to be explicitly listed in the OFW boot-device environment variable.
780 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
781 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
782 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
785 The following sysctls and tunables have been renamed for consistency
786 with other variables:
787 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
788 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
791 The sort utility has been replaced with BSD sort. For now, GNU sort
792 is also available as "gnusort" or the default can be set back to
793 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
794 installed as "bsdsort".
797 A new version of ZFS (pool version 5000) has been merged to -HEAD.
798 Starting with this version the old system of ZFS pool versioning
799 is superseded by "feature flags". This concept enables forward
800 compatibility against certain future changes in functionality of ZFS
801 pools. The first read-only compatible "feature flag" for ZFS pools
802 is named "com.delphix:async_destroy". For more information
803 read the new zpool-features(5) manual page.
804 Please refer to the "ZFS notes" section of this file for information
805 on upgrading boot ZFS pools.
808 The malloc(3) implementation embedded in libc now uses sources imported
809 as contrib/jemalloc. The most disruptive API change is to
810 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
811 delete it prior to installworld, and optionally re-create it using the
812 new format after rebooting. See malloc.conf(5) for details
813 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
817 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
818 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
819 now spelled mips. This is to aid compatibility with third-party
820 software that expects this naming scheme in uname(3). Little-endian
821 settings are unchanged. If you are updating a big-endian mips64 machine
822 from before this change, you may need to set MACHINE_ARCH=mips64 in
823 your environment before the new build system will recognize your machine.
826 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
830 Now unix domain sockets behave "as expected" on nullfs(5). Previously
831 nullfs(5) did not pass through all behaviours to the underlying layer,
832 as a result if we bound to a socket on the lower layer we could connect
833 only to the lower path; if we bound to the upper layer we could connect
834 only to the upper path. The new behavior is one can connect to both the
835 lower and the upper paths regardless what layer path one binds to.
838 The getifaddrs upgrade path broken with 20111215 has been restored.
839 If you have upgraded in between 20111215 and 20120209 you need to
840 recompile libc again with your kernel. You still need to recompile
841 world to be able to configure CARP but this restriction already
845 The set_rcvar() function has been removed from /etc/rc.subr. All
846 base and ports rc.d scripts have been updated, so if you have a
847 port installed with a script in /usr/local/etc/rc.d you can either
848 hand-edit the rcvar= line, or reinstall the port.
850 An easy way to handle the mass-update of /etc/rc.d:
851 rm /etc/rc.d/* && mergemaster -i
854 panic(9) now stops other CPUs in the SMP systems, disables interrupts
855 on the current CPU and prevents other threads from running.
856 This behavior can be reverted using the kern.stop_scheduler_on_panic
858 The new behavior can be incompatible with kern.sync_on_panic.
861 The carp(4) facility has been changed significantly. Configuration
862 of the CARP protocol via ifconfig(8) has changed, as well as format
863 of CARP events submitted to devd(8) has changed. See manual pages
864 for more information. The arpbalance feature of carp(4) is currently
865 not supported anymore.
867 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
868 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
869 need to be recompiled.
872 The acpi_wmi(4) status device /dev/wmistat has been renamed to
876 The option VFS_ALLOW_NONMPSAFE option has been added in order to
877 explicitely support non-MPSAFE filesystems.
878 It is on by default for all supported platform at this present
882 The broken amd(4) driver has been replaced with esp(4) in the amd64,
883 i386 and pc98 GENERIC kernel configuration files.
886 sysinstall has been removed
889 The stable/9 branch created in subversion. This corresponds to the
890 RELENG_9 branch in CVS.
893 This commit modifies vfs_register() so that it uses a hash
894 calculation to set vfc_typenum, which is enabled by default.
895 The first time a system is booted after this change, the
896 vfc_typenum values will change for all file systems. The
897 main effect of this is a change to the NFS server file handles
898 for file systems that use vfc_typenum in their fsid, such as ZFS.
899 It will, however, prevent vfc_typenum from changing when file
900 systems are loaded in a different order for subsequent reboots.
901 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
902 until you are ready to remount all NFS clients after a reboot.
905 Bump the shared library version numbers for libraries that
906 do not use symbol versioning, have changed the ABI compared
907 to stable/8 and which shared library version was not bumped.
908 Done as part of 9.0-RELEASE cycle.
911 During the merge of Capsicum features, the fget(9) KPI was modified.
912 This may require the rebuilding of out-of-tree device drivers --
913 issues have been reported specifically with the nVidia device driver.
914 __FreeBSD_version is bumped to 900041.
916 Also, there is a period between 20110811 and 20110814 where the
917 special devices /dev/{stdin,stdout,stderr} did not work correctly.
918 Building world from a kernel during that window may not work.
921 The packet filter (pf) code has been updated to OpenBSD 4.5.
922 You need to update userland tools to be in sync with kernel.
923 This update breaks backward compatibility with earlier pfsync(4)
924 versions. Care must be taken when updating redundant firewall setups.
927 The following sysctls and tunables are retired on x86 platforms:
929 machdep.hlt_logical_cpus
930 The following sysctl is retired:
931 machdep.hyperthreading_allowed
932 The sysctls were supposed to provide a way to dynamically offline and
933 online selected CPUs on x86 platforms, but the implementation has not
934 been reliable especially with SCHED_ULE scheduler.
935 machdep.hyperthreading_allowed tunable is still available to ignore
936 hyperthreading CPUs at OS level.
937 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
938 where X is an APIC ID of a CPU. Be advised, though, that disabling
939 CPUs in non-uniform fashion will result in non-uniform topology and
940 may lead to sub-optimal system performance with SCHED_ULE, which is
944 cpumask_t type is retired and cpuset_t is used in order to describe
948 Changes to ifconfig(8) for dynamic address family detection mandate
949 that you are running a kernel of 20110525 or later. Make sure to
950 follow the update procedure to boot a new kernel before installing
954 Support for sun4v architecture is officially dropped
957 Several KPI breaking changes have been committed to the mii(4) layer,
958 the PHY drivers and consequently some Ethernet drivers using mii(4).
959 This means that miibus.ko and the modules of the affected Ethernet
960 drivers need to be recompiled.
962 Note to kernel developers: Given that the OUI bit reversion problem
963 was fixed as part of these changes all mii(4) commits related to OUIs,
964 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
965 handling, no longer can be merged verbatim to stable/8 and previous
969 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
970 into their kernel configurations along with 'device pci'.
973 The default NFS client is now the new NFS client, so fstype "newnfs"
974 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
975 Although mounts via fstype "nfs" will usually work without userland
976 changes, it is recommended that the mount(8) and mount_nfs(8)
977 commands be rebuilt from sources and that a link to mount_nfs called
978 mount_oldnfs be created. The new client is compiled into the
979 kernel with "options NFSCL" and this is needed for diskless root
980 file systems. The GENERIC kernel configs have been changed to use
981 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
982 To use the regular/old client, you can "mount -t oldnfs ...". For
983 a diskless root file system, you must also include a line like:
985 vfs.root.mountfrom="oldnfs:"
987 in the boot/loader.conf on the root fs on the NFS server to make
988 a diskless root fs use the old client.
991 The GENERIC kernels for all architectures now default to the new
992 CAM-based ATA stack. It means that all legacy ATA drivers were
993 removed and replaced by respective CAM drivers. If you are using
994 ATA device names in /etc/fstab or other places, make sure to update
995 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
996 where 'Y's are the sequential numbers starting from zero for each type
997 in order of detection, unless configured otherwise with tunables,
998 see cam(4)). There will be symbolic links created in /dev/ to map
999 old adX devices to the respective adaY. They should provide basic
1000 compatibility for file systems mounting in most cases, but they do
1001 not support old user-level APIs and do not have respective providers
1002 in GEOM. Consider using updated management tools with new device names.
1004 It is possible to load devices ahci, ata, siis and mvs as modules,
1005 but option ATA_CAM should remain in kernel configuration to make ata
1006 module work as CAM driver supporting legacy ATA controllers. Device ata
1007 still can be used in modular fashion (atacore + ...). Modules atadisk
1008 and atapi* are not used and won't affect operation in ATA_CAM mode.
1009 Note that to use CAM-based ATA kernel should include CAM devices
1010 scbus, pass, da (or explicitly ada), cd and optionally others. All of
1011 them are parts of the cam module.
1013 ataraid(4) functionality is now supported by the RAID GEOM class.
1014 To use it you can load geom_raid kernel module and use graid(8) tool
1015 for management. Instead of /dev/arX device names, use /dev/raid/rX.
1017 No kernel config options or code have been removed, so if a problem
1018 arises, please report it and optionally revert to the old ATA stack.
1019 In order to do it you can remove from the kernel config:
1024 , and instead add back:
1025 device atadisk # ATA disk drives
1026 device ataraid # ATA RAID drives
1027 device atapicd # ATAPI CDROM drives
1028 device atapifd # ATAPI floppy drives
1029 device atapist # ATAPI tape drives
1032 The default NFS server has been changed to the new server, which
1033 was referred to as the experimental server. If you need to switch
1034 back to the old NFS server, you must now put the "-o" option on
1035 both the mountd and nfsd commands. This can be done using the
1036 mountd_flags and nfs_server_flags rc.conf variables until an
1037 update to the rc scripts is committed, which is coming soon.
1040 The GNU Objective-C runtime library (libobjc), and other Objective-C
1041 related components have been removed from the base system. If you
1042 require an Objective-C library, please use one of the available ports.
1045 ath(4) has been split into bus- and device- modules. if_ath contains
1046 the HAL, the TX rate control and the network device code. if_ath_pci
1047 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1048 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1049 in order to use ath on everything else.
1051 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1052 need to load if_ath and if_ath_pci for ath(4) operation.
1055 As part of the replacement of sysinstall, the process of building
1056 release media has changed significantly. For details, please re-read
1057 release(7), which has been updated to reflect the new build process.
1060 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1061 is the last available version under GPLv2. It brings a number of new
1062 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1063 4.1 and SSE 4.2), better support for powerpc64, a number of new
1064 directives, and lots of other small improvements. See the ChangeLog
1065 file in contrib/binutils for the full details.
1068 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1069 compliant, and will now use half of hash for authentication.
1070 This will break interoperability with all stacks (including all
1071 actual FreeBSD versions) who implement
1072 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1074 The only workaround with such peers is to use another HMAC
1075 algorithm for IPsec ("phase 2") authentication.
1078 Remove the uio_yield prototype and symbol. This function has
1079 been misnamed since it was introduced and should not be
1080 globally exposed with this name. The equivalent functionality
1081 is now available using kern_yield(curthread->td_user_pri).
1082 The function remains undocumented.
1085 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1086 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1087 for scalar sysctls is defined but disabled. Code that needs
1088 UQUAD to pass the type checking that must compile on older
1089 systems where the define is not present can check against
1090 __FreeBSD_version >= 900030.
1092 The system dialog(1) has been replaced with a new version previously
1093 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1094 with the previous version, but the libdialog associated with it has
1095 a largely incompatible API. As such, the original version of libdialog
1096 will be kept temporarily as libodialog, until its base system consumers
1097 are replaced or updated. Bump __FreeBSD_version to 900030.
1100 If you are trying to run make universe on a -stable system, and you get
1101 the following warning:
1102 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1103 unknown. config(8) likely too old."
1104 or something similar to it, then you must upgrade your -stable system
1105 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1106 stable/8) or build the config from the latest stable/8 branch and
1107 install it on your system.
1109 Prior to this date, building a current universe on 8-stable system from
1110 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1111 error in the first kernel build phase. A new config on those old
1112 systems will fix that problem for older versions of -current.
1115 The TCP stack has been modified to allow Khelp modules to interact with
1116 it via helper hook points and store per-connection data in the TCP
1117 control block. Bump __FreeBSD_version to 900029. User space tools that
1118 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1122 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1123 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1124 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1125 to take advantage of it instead of using custom implementations. This
1126 means that these drivers now no longer unconditionally advertise
1127 support for flow control but only do so if flow control is a selected
1128 media option. This was implemented in the generic support that way in
1129 order to allow flow control to be switched on and off via ifconfig(8)
1130 with the PHY specific default to typically off in order to protect
1131 from unwanted effects. Consequently, if you used flow control with
1132 one of the above mentioned drivers you now need to explicitly enable
1133 it, for example via:
1134 ifconfig bge0 media auto mediaopt flowcontrol
1136 Along with the above mentioned changes generic support for setting
1137 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1138 e1000phy(4) as well as ip1000phy(4) have been converted to take
1139 advantage of it. This means that these drivers now no longer take the
1140 link0 parameter for selecting master mode but the master media option
1141 has to be used instead, for example like in the following:
1142 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1144 Selection of master mode now is also available with all other PHY
1145 drivers supporting 1000baseT.
1148 The TCP stack has received a significant update to add support for
1149 modularised congestion control and generally improve the clarity of
1150 congestion control decisions. Bump __FreeBSD_version to 900025. User
1151 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1152 sockstat) need to be recompiled.
1155 The man(1) utility has been replaced by a new version that no longer
1156 uses /etc/manpath.config. Please consult man.conf(5) for how to
1157 migrate local entries to the new format.
1160 The copyright strings printed by login(1) and sshd(8) at the time of a
1161 new connection have been removed to follow other operating systems and
1165 A workaround for a fixed ld bug has been removed in kernel code,
1166 so make sure that your system ld is built from sources after
1167 revision 210245 from 2010-07-19 (r211583 if building head kernel
1168 on stable/8, r211584 for stable/7; both from 2010-08-21).
1169 A symptom of incorrect ld version is different addresses for
1170 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1173 The $ipv6_prefer variable in rc.conf(5) has been split into
1174 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1176 The $ip6addrctl_policy is a variable to choose a pre-defined
1177 address selection policy set by ip6addrctl(8). A value
1178 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1181 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1182 flag (see an entry of 20090926) is set on an interface with no
1183 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1184 security reason. If you want IPv6 link-local address on all
1185 interfaces by default, set this to "YES".
1187 The old ipv6_prefer="YES" is equivalent to
1188 ipv6_activate_all_interfaces="YES" and
1189 ip6addrctl_policy="ipv6_prefer".
1192 DTrace has grown support for userland tracing. Due to this, DTrace is
1193 now i386 and amd64 only.
1194 dtruss(1) is now installed by default on those systems and a new
1195 kernel module is needed for userland tracing: fasttrap.
1196 No changes to your kernel config file are necessary to enable
1197 userland tracing, but you might consider adding 'STRIP=' and
1198 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1199 to have informative userland stack traces in DTrace (ustack).
1202 The acpi_aiboost(4) driver has been removed in favor of the new
1203 aibs(4) driver. You should update your kernel configuration file.
1206 BSD grep has been imported to the base system and it is built by
1207 default. It is completely BSD licensed, highly GNU-compatible, uses
1208 less memory than its GNU counterpart and has a small codebase.
1209 However, it is slower than its GNU counterpart, which is mostly
1210 noticeable for larger searches, for smaller ones it is measurable
1211 but not significant. The reason is complex, the most important factor
1212 is that we lack a modern and efficient regex library and GNU
1213 overcomes this by optimizing the searches internally. Future work
1214 on improving the regex performance is planned, for the meantime,
1215 users that need better performance, can build GNU grep instead by
1216 setting the WITH_GNU_GREP knob.
1219 Due to the import of powerpc64 support, all existing powerpc kernel
1220 configuration files must be updated with a machine directive like this:
1221 machine powerpc powerpc
1223 In addition, an updated config(8) is required to build powerpc kernels
1227 A new version of ZFS (version 15) has been merged to -HEAD.
1228 This version uses a python library for the following subcommands:
1229 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1230 For full functionality of these commands the following port must
1231 be installed: sysutils/py-zfs
1234 'vm_page's are now hashed by physical address to an array of mutexes.
1235 Currently this is only used to serialize access to hold_count. Over
1236 time the page queue mutex will be peeled away. This changes the size
1237 of pmap on every architecture. And requires all callers of vm_page_hold
1238 and vm_page_unhold to be updated.
1241 WITH_CTF can now be specified in src.conf (not recommended, there
1242 are some problems with static executables), make.conf (would also
1243 affect ports which do not use GNU make and do not override the
1244 compile targets) or in the kernel config (via "makeoptions
1246 When WITH_CTF was specified there before this was silently ignored,
1247 so make sure that WITH_CTF is not used in places which could lead
1248 to unwanted behavior.
1251 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1252 to allow 32-bit compatibility on non-x86 platforms. All kernel
1253 configurations on amd64 and ia64 platforms using these options must
1254 be modified accordingly.
1257 The utmp user accounting database has been replaced with utmpx,
1258 the user accounting interface standardized by POSIX.
1259 Unfortunately the semantics of utmp and utmpx don't match,
1260 making it practically impossible to support both interfaces.
1261 The user accounting database is used by tools like finger(1),
1262 last(1), talk(1), w(1) and ac(8).
1264 All applications in the base system use utmpx. This means only
1265 local binaries (e.g. from the ports tree) may still use these
1266 utmp database files. These applications must be rebuilt to make
1269 After the system has been upgraded, it is safe to remove the old
1270 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1271 assuming their contents is of no importance anymore. Old wtmp
1272 databases can only be used by last(1) and ac(8) after they have
1273 been converted to the new format using wtmpcvt(1).
1276 Introduce the kernel thread "deadlock resolver" (which can be enabled
1277 via the DEADLKRES option, see NOTES for more details) and the
1278 sleepq_type() function for sleepqueues.
1281 The rc.firewall and rc.firewall6 were unified, and
1282 rc.firewall6 and rc.d/ip6fw were removed.
1283 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1284 variables are obsoleted. Instead, the following new rc
1285 variables are added to rc.d/ipfw:
1287 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1288 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1289 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1291 The meanings correspond to the relevant IPv4 variables.
1297 The default terminal emulation for syscons(4) has been changed
1298 from cons25 to xterm on all platforms except pc98. This means
1299 that the /etc/ttys file needs to be updated to ensure correct
1300 operation of applications on the console.
1302 The terminal emulation style can be toggled per window by using
1303 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1304 options can be used to change the compile-time default back to
1307 To prevent graphical artifacts, make sure the TERM environment
1308 variable is set to match the terminal emulation that is being
1309 performed by syscons(4).
1312 The layout of the structure ieee80211req_scan_result has changed.
1313 Applications that require wireless scan results (e.g. ifconfig(8))
1314 from net80211 need to be recompiled.
1316 Applications such as wpa_supplicant(8) may require a full world
1317 build without using NO_CLEAN in order to get synchronized with the
1321 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1322 There's one kernel module for each firmware. Adding "device iwnfw"
1323 to the kernel configuration file means including all three firmware
1324 images inside the kernel. If you want to include just the one for
1325 your wireless card, use the devices iwn4965fw, iwn5000fw or
1329 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1330 into rc.d/netif. The changes are the following:
1332 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1333 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1334 Note that both variables need the "inet6" keyword at the head.
1336 Do not set $ipv6_network_interfaces manually if you do not
1337 understand what you are doing. It is not needed in most cases.
1339 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1342 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1343 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1345 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1346 all configured interfaces have "inet6 accept_rtadv" in the
1347 $ifconfig_IF_ipv6. These are for backward compatibility.
1349 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1350 functionality of interfaces with no corresponding
1351 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1352 and the default address selection policy of ip6addrctl(8)
1353 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1354 Note that if you want to configure IPv6 functionality on the
1355 disabled interfaces after boot, first you need to clear the flag by
1356 using ifconfig(8) like:
1358 ifconfig em0 inet6 -ifdisabled
1360 If YES, the default address selection policy is set as
1363 The default value of $ipv6_prefer is NO.
1365 4. If your system need to receive Router Advertisement messages,
1366 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1367 scripts automatically invoke rtsol(8) when the interface becomes
1368 UP. The Router Advertisement messages are used for SLAAC
1369 (State-Less Address AutoConfiguration).
1372 802.11s D3.03 support was committed. This is incompatible with the
1373 previous code, which was based on D3.0.
1376 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1377 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1378 control whether accepting Router Advertisement messages or not.
1379 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1380 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1381 The ifconfig(8) utility now supports these flags.
1384 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1385 mount(8) and -a option for df(1) to see them.
1388 The old tunable hw.bus.devctl_disable has been superseded by
1389 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1390 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1394 Remove the option STOP_NMI. The default action is now to use NMI only
1395 for KDB via the newly introduced function stop_cpus_hard() and
1396 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1399 The stable/8 branch created in subversion. This corresponds to the
1400 RELENG_8 branch in CVS.
1403 Bump the shared library version numbers for all libraries that do not
1404 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1405 __FreeBSD_version to 800105.
1408 Due to changes in the implementation of virtual network stack support,
1409 all network-related kernel modules must be recompiled. As this change
1410 breaks the ABI, bump __FreeBSD_version to 800104.
1413 The TOE interface to the TCP syncache has been modified to remove
1414 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1415 The cxgb driver is the only TOE consumer affected by this change, and
1416 needs to be recompiled along with the kernel. As this change breaks
1417 the ABI, bump __FreeBSD_version to 800103.
1420 Padding has been added to struct tcpcb, sackhint and tcpstat in
1421 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1422 maintaining the ABI. However, this change breaks the ABI, so bump
1423 __FreeBSD_version to 800102. User space tools that rely on the size of
1424 any of these structs (e.g. sockstat) need to be recompiled.
1427 The NFS_LEGACYRPC option has been removed along with the old kernel
1428 RPC implementation that this option selected. Kernel configurations
1429 may need to be adjusted.
1432 The network interface device nodes at /dev/net/<interface> have been
1433 removed. All ioctl operations can be performed the normal way using
1434 routing sockets. The kqueue functionality can generally be replaced
1435 with routing sockets.
1438 The documentation from the FreeBSD Documentation Project (Handbook,
1439 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1440 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1443 The ABI of various structures related to the SYSV IPC API have been
1444 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1445 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1449 Layout of struct vnet has changed as routing related variables were
1450 moved to their own Vimage module. Modules need to be recompiled. Bump
1451 __FreeBSD_version to 800099.
1454 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1455 respectively. As long as no more than 16 groups per process are used,
1456 no changes should be visible. When more than 16 groups are used, old
1457 binaries may fail if they call getgroups() or getgrouplist() with
1458 statically sized storage. Recompiling will work around this, but
1459 applications should be modified to use dynamically allocated storage
1460 for group arrays as POSIX.1-2008 does not cap an implementation's
1461 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1463 NFS and portalfs mounts may also be affected as the list of groups is
1464 truncated to 16. Users of NFS who use more than 16 groups, should
1465 take care that negative group permissions are not used on the exported
1466 file systems as they will not be reliable unless a GSSAPI based
1467 authentication method is used.
1470 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1471 option compiles in the support for adaptive spinning for lockmgrs
1472 which want to enable it. The lockinit() function now accepts the flag
1473 LK_ADAPTIVE in order to make the lock object subject to adaptive
1474 spinning when both held in write and read mode.
1477 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1478 changed. User applications that use this ioctl need to be rebuilt.
1481 The layout of struct thread has changed. Kernel and modules need to
1485 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1486 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1489 window(1) has been removed from the base system. It can now be
1490 installed from ports. The port is called misc/window.
1493 The way we are storing and accessing `routing table' entries has
1494 changed. Programs reading the FIB, like netstat, need to be
1498 A new netisr implementation has been added for FreeBSD 8. Network
1499 file system modules, such as igmp, ipdivert, and others, should be
1501 Bump __FreeBSD_version to 800096.
1504 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1508 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1509 Bump __FreeBSD_version to 800094.
1512 Add mnt_xflag field to 'struct mount'. File system modules need to be
1514 Bump __FreeBSD_version to 800093.
1517 The compiling option ADAPTIVE_SX has been retired while it has been
1518 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1519 The KPI for sx_init_flags() changes as accepting flags:
1520 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1521 been introduced in order to handle the reversed logic.
1522 Bump __FreeBSD_version to 800092.
1525 Add support for hierarchical jails. Remove global securelevel.
1526 Bump __FreeBSD_version to 800091.
1529 The layout of struct vnet_net has changed, therefore modules
1531 Bump __FreeBSD_version to 800090.
1534 The newly imported zic(8) produces a new format in the output. Please
1535 run tzsetup(8) to install the newly created data to /etc/localtime.
1538 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1539 hw.usb.* and is now consistent again with previous releases.
1542 802.11 monitor mode support was revised and driver api's were changed.
1543 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1544 of DLT_IEEE802_11. No user-visible data structures were changed but
1545 applications that use DLT_IEEE802_11 may require changes.
1546 Bump __FreeBSD_version to 800088.
1549 The layout of the following structs has changed: sysctl_oid,
1550 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1551 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1552 panics may be experienced. World rebuild is required for
1553 correctly checking networking state from userland.
1554 Bump __FreeBSD_version to 800085.
1557 MLDv2 and Source-Specific Multicast (SSM) have been merged
1558 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1559 The implementation of SSM within FreeBSD's IPv6 stack closely
1560 follows the IPv4 implementation.
1562 For kernel developers:
1564 * The most important changes are that the ip6_output() and
1565 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1566 and this lock has been downgraded to a non-recursive mutex.
1568 * As with the changes to the IPv4 stack to support SSM, filtering
1569 of inbound multicast traffic must now be performed by transport
1570 protocols within the IPv6 stack. This does not apply to TCP and
1571 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1573 * The KPIs used by IPv6 multicast are similar to those used by
1574 the IPv4 stack, with the following differences:
1575 * im6o_mc_filter() is analogous to imo_multicast_filter().
1576 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1577 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1578 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1579 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1580 for MLDv1 have an additional 'timer' argument which is used to
1581 jitter the initial membership report for the solicited-node
1582 multicast membership on-link.
1583 * This is not strictly needed for MLDv2, which already jitters
1584 its report transmissions. However, the 'timer' argument is
1585 preserved in case MLDv1 is active on the interface.
1587 * The KAME linked-list based IPv6 membership implementation has
1588 been refactored to use a vector similar to that used by the IPv4
1590 Code which maintains a list of its own multicast memberships
1591 internally, e.g. carp, has been updated to reflect the new
1594 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1595 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1596 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1597 implementation constraint which needs to be addressed in HEAD.
1599 For application developers:
1601 * The changes are broadly similar to those made for the IPv4
1604 * The use of IPv4 and IPv6 multicast socket options on the same
1605 socket, using mapped addresses, HAS NOT been tested or supported.
1607 * There are a number of issues with the implementation of various
1608 IPv6 multicast APIs which need to be resolved in the API surface
1609 before the implementation is fully compatible with KAME userland
1610 use, and these are mostly to do with interface index treatment.
1612 * The literature available discusses the use of either the delta / ASM
1613 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1614 using setsourcefilter(3)/getsourcefilter(3). For more information
1615 please refer to RFC 3768, 'Socket Interface Extensions for
1616 Multicast Source Filters'.
1618 * Applications which use the published RFC 3678 APIs should be fine.
1620 For systems administrators:
1622 * The mtest(8) utility has been refactored to support IPv6, in
1623 addition to IPv4. Interface addresses are no longer accepted
1624 as arguments, their names must be used instead. The utility
1625 will map the interface name to its first IPv4 address as
1626 returned by getifaddrs(3).
1628 * The ifmcstat(8) utility has also been updated to print the MLDv2
1629 endpoint state and source filter lists via sysctl(3).
1631 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1632 loopback of IPv6 multicast datagrams by default; it defaults to 1
1633 to preserve the existing behaviour. Disabling multicast loopback is
1634 recommended for optimal system performance.
1636 * The IPv6 MROUTING code has been changed to examine this sysctl
1637 instead of attempting to perform a group lookup before looping
1638 back forwarded datagrams.
1640 Bump __FreeBSD_version to 800084.
1643 Implement low-level Bluetooth HCI API.
1644 Bump __FreeBSD_version to 800083.
1647 The layout of struct malloc_type, used by modules to register new
1648 memory allocation types, has changed. Most modules will need to
1649 be rebuilt or panics may be experienced.
1650 Bump __FreeBSD_version to 800081.
1653 Anticipate overflowing inp_flags - add inp_flags2.
1654 This changes most offsets in inpcb, so checking v4 connection
1655 state will require a world rebuild.
1656 Bump __FreeBSD_version to 800080.
1659 Add an llentry to struct route and struct route_in6. Modules
1660 embedding a struct route will need to be recompiled.
1661 Bump __FreeBSD_version to 800079.
1664 The size of rt_metrics_lite and by extension rtentry has changed.
1665 Networking administration apps will need to be recompiled.
1666 The route command now supports show as an alias for get, weighting
1667 of routes, sticky and nostick flags to alter the behavior of stateful
1669 Bump __FreeBSD_version to 800078.
1672 Do not use Giant for kbdmux(4) locking. This is wrong and
1673 apparently causing more problems than it solves. This will
1674 re-open the issue where interrupt handlers may race with
1675 kbdmux(4) in polling mode. Typical symptoms include (but
1676 not limited to) duplicated and/or missing characters when
1677 low level console functions (such as gets) are used while
1678 interrupts are enabled (for example geli password prompt,
1679 mountroot prompt etc.). Disabling kbdmux(4) may help.
1682 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1683 kernel modules referencing any of the above need to be recompiled.
1684 Bump __FreeBSD_version to 800075.
1687 GEOM_PART has become the default partition slicer for storage devices,
1688 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1689 introduces some changes:
1691 MSDOS/EBR: the devices created from MSDOS extended partition entries
1692 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1693 to devices with offset-based names. fstabs may need to be modified.
1695 BSD: the "geometry does not match label" warning is harmless in most
1696 cases but it points to problems in file system misalignment with
1697 disk geometry. The "c" partition is now implicit, covers the whole
1698 top-level drive and cannot be (mis)used by users.
1700 General: Kernel dumps are now not allowed to be written to devices
1701 whose partition types indicate they are meant to be used for file
1702 systems (or, in case of MSDOS partitions, as something else than
1705 Most of these changes date approximately from 200812.
1708 The uscanner(4) driver has been removed from the kernel. This follows
1709 Linux removing theirs in 2.6 and making libusb the default interface
1710 (supported by sane).
1713 The multicast forwarding code has been cleaned up. netstat(1)
1714 only relies on KVM now for printing bandwidth upcall meters.
1715 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1716 ip6_mroute_mod respectively. The config(5) options for statically
1717 compiling this code remain the same, i.e. 'options MROUTING'.
1720 Support for the IFF_NEEDSGIANT network interface flag has been
1721 removed, which means that non-MPSAFE network device drivers are no
1722 longer supported. In particular, if_ar, if_sr, and network device
1723 drivers from the old (legacy) USB stack can no longer be built or
1727 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1728 a bunch of new language catalog files have also been added.
1729 This means that some common libc messages are now localized and
1730 they depend on the LC_MESSAGES environmental variable.
1733 The k8temp(4) driver has been renamed to amdtemp(4) since
1734 support for Family 10 and Family 11 CPU families was added.
1737 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1738 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1740 For kernel developers, the most important changes are that the
1741 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1742 and this lock has been downgraded to a non-recursive mutex.
1744 Transport protocols (UDP, Raw IP) are now responsible for filtering
1745 inbound multicast traffic according to group membership and source
1746 filters. The imo_multicast_filter() KPI exists for this purpose.
1747 Transports which do not use multicast (SCTP, TCP) already reject
1748 multicast by default. Forwarding and receive performance may improve
1749 as a mutex acquisition is no longer needed in the ip_input()
1750 low-level input path. in_addmulti() and in_delmulti() are shimmed
1751 to new KPIs which exist to support SSM in-kernel.
1753 For application developers, it is recommended that loopback of
1754 multicast datagrams be disabled for best performance, as this
1755 will still cause the lock to be taken for each looped-back
1756 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1757 be tuned to 0 to disable loopback by default; it defaults to 1
1758 to preserve the existing behaviour.
1760 For systems administrators, to obtain best performance with
1761 multicast reception and multiple groups, it is always recommended
1762 that a card with a suitably precise hash filter is used. Hash
1763 collisions will still result in the lock being taken within the
1764 transport protocol input path to check group membership.
1766 If deploying FreeBSD in an environment with IGMP snooping switches,
1767 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1768 enabled; this forces 224.0.0.0/24 group membership to be announced
1771 The size of 'struct igmpstat' has changed; netstat needs to be
1772 recompiled to reflect this.
1773 Bump __FreeBSD_version to 800070.
1776 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1777 updated to use it. This requires a buildworld/installworld in order to
1778 update the library and dependencies (usbconfig, etc). Its advisable to
1779 rebuild all ports which uses libusb. More specific directions are given
1780 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1781 libusb are no longer required and can be removed.
1784 A workaround is committed to allow the creation of System V shared
1785 memory segment of size > 2 GB on the 64-bit architectures.
1786 Due to a limitation of the existing ABI, the shm_segsz member
1787 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1788 wrong for large segments. Note that limits must be explicitly
1789 raised to allow such segments to be created.
1792 The layout of struct ifnet has changed, requiring a rebuild of all
1793 network device driver modules.
1796 The /dev handling for the new USB stack has changed, a
1797 buildworld/installworld is required for libusb20.
1800 The new USB2 stack has now been permanently moved in and all kernel and
1801 module names reverted to their previous values (eg, usb, ehci, ohci,
1802 ums, ...). The old usb stack can be compiled in by prefixing the name
1803 with the letter 'o', the old usb modules have been removed.
1804 Updating entry 20090216 for xorg and 20090215 for libmap may still
1808 The rc.conf(5) option if_up_delay has been renamed to
1809 defaultroute_delay to better reflect its purpose. If you have
1810 customized this setting in /etc/rc.conf you need to update it to
1814 xorg 7.4 wants to configure its input devices via hald which does not
1815 yet work with USB2. If the keyboard/mouse does not work in xorg then
1817 Option "AllowEmptyInput" "off"
1818 to your ServerLayout section. This will cause X to use the configured
1819 kbd and mouse sections from your xorg.conf.
1822 The GENERIC kernels for all architectures now default to the new USB2
1823 stack. No kernel config options or code have been removed so if a
1824 problem arises please report it and optionally revert to the old USB
1825 stack. If you are loading USB kernel modules or have a custom kernel
1826 that includes GENERIC then ensure that usb names are also changed over,
1827 eg uftdi -> usb2_serial_ftdi.
1829 Older programs linked against the ports libusb 0.1 need to be
1830 redirected to the new stack's libusb20. /etc/libmap.conf can
1832 # Map old usb library to new one for usb2 stack
1833 libusb-0.1.so.8 libusb20.so.1
1836 All USB ethernet devices now attach as interfaces under the name ueN
1837 (eg. ue0). This is to provide a predictable name as vendors often
1838 change usb chipsets in a product without notice.
1841 The ichsmb(4) driver has been changed to require SMBus slave
1842 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1843 All of the other SMBus controller drivers require left-justified
1844 slave addresses, so this change makes all the drivers provide the
1848 INET6 statistics (struct ip6stat) was updated.
1849 netstat(1) needs to be recompiled.
1852 NTFS has been removed from GENERIC kernel on amd64 to match
1853 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1854 will load ntfs.ko module automatically when NTFS support is
1855 actually needed, unless ntfs.ko is not installed or security
1856 level prohibits loading kernel modules. If either is the case,
1857 "options NTFS" has to be added into kernel config.
1860 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1861 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1862 800061. User space tools that rely on the size of struct tcpcb in
1863 tcp_var.h (e.g. sockstat) need to be recompiled.
1866 ng_tty(4) module updated to match the new TTY subsystem.
1867 Due to API change, user-level applications must be updated.
1868 New API support added to mpd5 CVS and expected to be present
1869 in next mpd5.3 release.
1872 With __FreeBSD_version 800060 the makefs tool is part of
1873 the base system (it was a port).
1876 The afdata and ifnet locks have been changed from mutexes to
1877 rwlocks, network modules will need to be re-compiled.
1880 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1881 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1882 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1883 architecture and 40 bytes on 64-bit architecture. The userland
1884 applications "arp" and "ndp" have been updated accordingly.
1885 The output from "netstat -r" shows only routing entries and
1886 none of the L2 information.
1889 __FreeBSD_version 800057 marks the switchover from the
1890 binary ath hal to source code. Users must add the line:
1892 options AH_SUPPORT_AR5416
1894 to their kernel config files when specifying:
1898 The ath_hal module no longer exists; the code is now compiled
1899 together with the driver in the ath module. It is now
1900 possible to tailor chip support (i.e. reduce the set of chips
1901 and thereby the code size); consult ath_hal(4) for details.
1904 __FreeBSD_version 800054 adds memory barriers to
1905 <machine/atomic.h>, new interfaces to ifnet to facilitate
1906 multiple hardware transmit queues for cards that support
1907 them, and a lock-less ring-buffer implementation to
1908 enable drivers to more efficiently manage queueing of
1912 A new version of ZFS (version 13) has been merged to -HEAD.
1913 This version has zpool attribute "listsnapshots" off by
1914 default, which means "zfs list" does not show snapshots,
1915 and is the same as Solaris behavior.
1918 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1921 The uhci, ohci, ehci and slhci USB Host controller drivers have
1922 been put into separate modules. If you load the usb module
1923 separately through loader.conf you will need to load the
1924 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1925 controller add the following to loader.conf:
1931 The ABI used by the PMC toolset has changed. Please keep
1932 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1936 atapci kernel module now includes only generic PCI ATA
1937 driver. AHCI driver moved to ataahci kernel module.
1938 All vendor-specific code moved into separate kernel modules:
1939 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1940 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1941 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1942 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1945 The TTY subsystem of the kernel has been replaced by a new
1946 implementation, which provides better scalability and an
1947 improved driver model. Most common drivers have been migrated to
1948 the new TTY subsystem, while others have not. The following
1949 drivers have not yet been ported to the new TTY layer:
1952 cy, digi, rc, rp, sio
1958 ng_h4, ng_tty, ppp, sl, snp
1960 Adding these drivers to your kernel configuration file shall
1961 cause compilation to fail.
1964 ntpd has been upgraded to 4.2.4p5.
1967 OpenSSH has been upgraded to 5.1p1.
1969 For many years, FreeBSD's version of OpenSSH preferred DSA
1970 over RSA for host and user authentication keys. With this
1971 upgrade, we've switched to the vendor's default of RSA over
1972 DSA. This may cause upgraded clients to warn about unknown
1973 host keys even for previously known hosts. Users should
1974 follow the usual procedure for verifying host keys before
1975 accepting the RSA key.
1977 This can be circumvented by setting the "HostKeyAlgorithms"
1978 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1981 Please note that the sequence of keys offered for
1982 authentication has been changed as well. You may want to
1983 specify IdentityFile in a different order to revert this
1987 The sio(4) driver has been removed from the i386 and amd64
1988 kernel configuration files. This means uart(4) is now the
1989 default serial port driver on those platforms as well.
1991 To prevent collisions with the sio(4) driver, the uart(4) driver
1992 uses different names for its device nodes. This means the
1993 onboard serial port will now most likely be called "ttyu0"
1994 instead of "ttyd0". You may need to reconfigure applications to
1995 use the new device names.
1997 When using the serial port as a boot console, be sure to update
1998 /boot/device.hints and /etc/ttys before booting the new kernel.
1999 If you forget to do so, you can still manually specify the hints
2000 at the loader prompt:
2002 set hint.uart.0.at="isa"
2003 set hint.uart.0.port="0x3F8"
2004 set hint.uart.0.flags="0x10"
2005 set hint.uart.0.irq="4"
2009 The gpt(8) utility has been removed. Use gpart(8) to partition
2013 The version that Linuxulator emulates was changed from 2.4.2
2014 to 2.6.16. If you experience any problems with Linux binaries
2015 please try to set sysctl compat.linux.osrelease to 2.4.2 and
2016 if it fixes the problem contact emulation mailing list.
2019 ISDN4BSD (I4B) was removed from the src tree. You may need to
2020 update a your kernel configuration and remove relevant entries.
2023 I have checked in code to support multiple routing tables.
2024 See the man pages setfib(1) and setfib(2).
2025 This is a hopefully backwards compatible version,
2026 but to make use of it you need to compile your kernel
2027 with options ROUTETABLES=2 (or more up to 16).
2030 The 802.11 wireless support was redone to enable multi-bss
2031 operation on devices that are capable. The underlying device
2032 is no longer used directly but instead wlanX devices are
2033 cloned with ifconfig. This requires changes to rc.conf files.
2034 For example, change:
2035 ifconfig_ath0="WPA DHCP"
2038 ifconfig_wlan0="WPA DHCP"
2039 see rc.conf(5) for more details. In addition, mergemaster of
2040 /etc/rc.d is highly recommended. Simultaneous update of userland
2041 and kernel wouldn't hurt either.
2043 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2044 modules were merged into the base wlan module. All references
2045 to these modules (e.g. in kernel config files) must be removed.
2048 psm(4) has gained write(2) support in native operation level.
2049 Arbitrary commands can be written to /dev/psm%d and status can
2050 be read back from it. Therefore, an application is responsible
2051 for status validation and error recovery. It is a no-op in
2052 other operation levels.
2055 Support for KSE threading has been removed from the kernel. To
2056 run legacy applications linked against KSE libmap.conf may
2057 be used. The following libmap.conf may be used to ensure
2058 compatibility with any prior release:
2060 libpthread.so.1 libthr.so.1
2061 libpthread.so.2 libthr.so.2
2062 libkse.so.3 libthr.so.3
2065 The layout of struct vmspace has changed. This affects libkvm
2066 and any executables that link against libkvm and use the
2067 kvm_getprocs() function. In particular, but not exclusively,
2068 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2069 The effects are minimal, but it's advisable to upgrade world
2073 The latest em driver no longer has support in it for the
2074 82575 adapter, this is now moved to the igb driver. The
2075 split was done to make new features that are incompatible
2076 with older hardware easier to do.
2079 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2080 likewise the kernel option is now GEOM_LINUX_LVM.
2083 The default NFS mount mode has changed from UDP to TCP for
2084 increased reliability. If you rely on (insecurely) NFS
2085 mounting across a firewall you may need to update your
2089 Belatedly note the addition of m_collapse for compacting
2093 The fts(3) structures have been changed to use adequate
2094 integer types for their members and so to be able to cope
2095 with huge file trees. The old fts(3) ABI is preserved
2096 through symbol versioning in libc, so third-party binaries
2097 using fts(3) should still work, although they will not take
2098 advantage of the extended types. At the same time, some
2099 third-party software might fail to build after this change
2100 due to unportable assumptions made in its source code about
2101 fts(3) structure members. Such software should be fixed
2102 by its vendor or, in the worst case, in the ports tree.
2103 FreeBSD_version 800015 marks this change for the unlikely
2104 case that a portable fix is impossible.
2107 To upgrade to -current after this date, you must be running
2108 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2109 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2112 The ADAPTIVE_GIANT kernel option has been retired because its
2113 functionality is the default now.
2116 The AT keyboard emulation of sunkbd(4) has been turned on
2117 by default. In order to make the special symbols of the Sun
2118 keyboards driven by sunkbd(4) work under X these now have
2119 to be configured the same way as Sun USB keyboards driven
2120 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2122 Option "XkbLayout" "us"
2123 Option "XkbRules" "xorg"
2124 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2127 It has been decided that it is desirable to provide ABI
2128 backwards compatibility to the FreeBSD 4/5/6 versions of the
2129 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2130 broken with the introduction of PCI domain support (see the
2131 20070930 entry). Unfortunately, this required the ABI of
2132 PCIOCGETCONF to be broken again in order to be able to
2133 provide backwards compatibility to the old version of that
2134 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2135 again. As for prominent ports this affects neither pciutils
2136 nor xorg-server this time, the hal port needs to be rebuilt
2140 The misnamed kthread_create() and friends have been renamed
2141 to kproc_create() etc. Many of the callers already
2142 used kproc_start()..
2143 I will return kthread_create() and friends in a while
2144 with implementations that actually create threads, not procs.
2145 Renaming corresponds with version 800002.
2154 Avoid using make -j when upgrading. While generally safe, there are
2155 sometimes problems using -j to upgrade. If your upgrade fails with
2156 -j, please try again without -j. From time to time in the past there
2157 have been problems using -j with buildworld and/or installworld. This
2158 is especially true when upgrading between "distant" versions (eg one
2159 that cross a major release boundary or several minor releases, or when
2160 several months have passed on the -current branch).
2162 Sometimes, obscure build problems are the result of environment
2163 poisoning. This can happen because the make utility reads its
2164 environment when searching for values for global variables. To run
2165 your build attempts in an "environmental clean room", prefix all make
2166 commands with 'env -i '. See the env(1) manual page for more details.
2168 When upgrading from one major version to another it is generally best
2169 to upgrade to the latest code in the currently installed branch first,
2170 then do an upgrade to the new branch. This is the best-tested upgrade
2171 path, and has the highest probability of being successful. Please try
2172 this approach before reporting problems with a major version upgrade.
2174 When upgrading a live system, having a root shell around before
2175 installing anything can help undo problems. Not having a root shell
2176 around can lead to problems if pam has changed too much from your
2177 starting point to allow continued authentication after the upgrade.
2181 When upgrading the boot ZFS pool to a new version, always follow
2184 1.) recompile and reinstall the ZFS boot loader and boot block
2185 (this is part of "make buildworld" and "make installworld")
2187 2.) update the ZFS boot block on your boot drive
2189 The following example updates the ZFS boot block on the first
2190 partition (freebsd-boot) of a GPT partitioned drive ad0:
2191 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2193 Non-boot pools do not need these updates.
2197 If you are updating from a prior version of FreeBSD (even one just
2198 a few days old), you should follow this procedure. It is the most
2199 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2201 make kernel-toolchain
2202 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2203 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2205 To test a kernel once
2206 ---------------------
2207 If you just want to boot a kernel once (because you are not sure
2208 if it works, or if you want to boot a known bad kernel to provide
2209 debugging information) run
2210 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2211 nextboot -k testkernel
2213 To just build a kernel when you know that it won't mess you up
2214 --------------------------------------------------------------
2215 This assumes you are already running a CURRENT system. Replace
2216 ${arch} with the architecture of your machine (e.g. "i386",
2217 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2219 cd src/sys/${arch}/conf
2220 config KERNEL_NAME_HERE
2221 cd ../compile/KERNEL_NAME_HERE
2226 If this fails, go to the "To build a kernel" section.
2228 To rebuild everything and install it on the current system.
2229 -----------------------------------------------------------
2230 # Note: sometimes if you are running current you gotta do more than
2231 # is listed here if you are upgrading from a really old current.
2233 <make sure you have good level 0 dumps>
2235 make kernel KERNCONF=YOUR_KERNEL_HERE
2237 <reboot in single user> [3]
2244 To cross-install current onto a separate partition
2245 --------------------------------------------------
2246 # In this approach we use a separate partition to hold
2247 # current's root, 'usr', and 'var' directories. A partition
2248 # holding "/", "/usr" and "/var" should be about 2GB in
2251 <make sure you have good level 0 dumps>
2254 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2255 <maybe newfs current's root partition>
2256 <mount current's root partition on directory ${CURRENT_ROOT}>
2257 make installworld DESTDIR=${CURRENT_ROOT}
2258 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2259 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2260 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2261 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2262 <reboot into current>
2263 <do a "native" rebuild/install as described in the previous section>
2264 <maybe install compatibility libraries from ports/misc/compat*>
2268 To upgrade in-place from stable to current
2269 ----------------------------------------------
2270 <make sure you have good level 0 dumps>
2272 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2274 <reboot in single user> [3]
2281 Make sure that you've read the UPDATING file to understand the
2282 tweaks to various things you need. At this point in the life
2283 cycle of current, things change often and you are on your own
2284 to cope. The defaults can also change, so please read ALL of
2285 the UPDATING entries.
2287 Also, if you are tracking -current, you must be subscribed to
2288 freebsd-current@freebsd.org. Make sure that before you update
2289 your sources that you have read and understood all the recent
2290 messages there. If in doubt, please track -stable which has
2291 much fewer pitfalls.
2293 [1] If you have third party modules, such as vmware, you
2294 should disable them at this point so they don't crash your
2297 [3] From the bootblocks, boot -s, and then do
2302 adjkerntz -i # if CMOS is wall time
2303 Also, when doing a major release upgrade, it is required that
2304 you boot into single user mode to do the installworld.
2306 [4] Note: This step is non-optional. Failure to do this step
2307 can result in a significant reduction in the functionality of the
2308 system. Attempting to do it by hand is not recommended and those
2309 that pursue this avenue should read this file carefully, as well
2310 as the archives of freebsd-current and freebsd-hackers mailing lists
2311 for potential gotchas. The -U option is also useful to consider.
2312 See mergemaster(8) for more information.
2314 [5] Usually this step is a noop. However, from time to time
2315 you may need to do this if you get unknown user in the following
2316 step. It never hurts to do it all the time. You may need to
2317 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2318 install) after the buildworld before this step if you last updated
2319 from current before 20130425 or from -stable before 20130430.
2321 [6] This only deletes old files and directories. Old libraries
2322 can be deleted by "make delete-old-libs", but you have to make
2323 sure that no program is using those libraries anymore.
2325 [8] In order to have a kernel that can run the 4.x binaries needed to
2326 do an installworld, you must include the COMPAT_FREEBSD4 option in
2327 your kernel. Failure to do so may leave you with a system that is
2328 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2329 required to run the 5.x binaries on more recent kernels. And so on
2330 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2332 Make sure that you merge any new devices from GENERIC since the
2333 last time you updated your kernel config file.
2335 [9] When checking out sources, you must include the -P flag to have
2336 cvs prune empty directories.
2338 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2339 "?=" instead of the "=" assignment operator, so that buildworld can
2340 override the CPUTYPE if it needs to.
2342 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2343 not on the command line, or in /etc/make.conf. buildworld will
2344 warn if it is improperly defined.
2347 This file contains a list, in reverse chronological order, of major
2348 breakages in tracking -current. It is not guaranteed to be a complete
2349 list of such breakages, and only contains entries since October 10, 2007.
2350 If you need to see UPDATING entries from before that date, you will need
2351 to fetch an UPDATING file from an older FreeBSD release.
2353 Copyright information:
2355 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2357 Redistribution, publication, translation and use, with or without
2358 modification, in full or in part, in any form or format of this
2359 document are permitted without further permission from the author.
2361 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2362 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2363 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2364 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2365 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2366 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2367 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2368 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2369 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2370 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2371 POSSIBILITY OF SUCH DAMAGE.
2373 Contact Warner Losh if you have any questions about your use of