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 20160504 p16 FreeBSD-SA-16:17.openssl
23 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
25 Fix excessive latency in x86 IPI delivery. [EN-16:07]
27 Fix memory leak in ZFS. [EN-16:08]
29 20160429 p15 FreeBSD-SA-16:16.ntp
31 Fix multiple vulnerabilities of ntp.
33 20160316 p14 FreeBSD-SA-16:14.openssh-xauth
34 FreeBSD-SA-16:15.sysarch
35 FreeBSD-EN-16:04.hyperv
36 FreeBSD-EN-16:05.hv_netvsc
38 Fix OpenSSH xauth(1) command injection. [SA-16:14]
39 Fix incorrect argument validation in sysarch(2). [SA-16:15]
40 Fix Hyper-V KVP (Key-Value Pair) daemon indefinite sleep. [EN-16:04]
41 Fix hv_netvsc(4) incorrect TCP/IP checksums. [EN-16:05]
43 20160303 p13 FreeBSD-SA-16:12.openssl
45 Fix multiple vulnerabilities of OpenSSL.
47 20160130 p12 FreeBSD-SA-16:11.openssl
49 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
51 20160127 p11 FreeBSD-SA-16:09.ntp
52 FreeBSD-SA-16:10.linux
54 Fix multiple vulnerabilities of ntp. [SA-16:09]
56 Fix Linux compatibility layer issetugid(2) system call
57 vulnerability. [SA-16:10]
59 20160114 p10 FreeBSD-SA-16:07.openssh
61 Fix OpenSSH client information leak. [SA-16:07]
63 20160114 p9 FreeBSD-EN-16:01.filemon
65 FreeBSD-EN-16:03.yplib
68 FreeBSD-SA-16:03.linux
69 FreeBSD-SA-16:04.linux
71 FreeBSD-SA-16:06.bsnmpd
73 Fix multiple stability and locking problems in filemon(4). [EN-16:01]
74 Fix pf(4) generating bad TCP checksums. [EN-16:02]
75 Fix infinite loop in YP/NIS client library. [EN-16:03]
76 Fix remote denial of service in SCTP. [SA-16:01]
77 Update NTP to 4.2.8p5. [SA-16:02]
78 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
79 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
80 Fix crash in TCP MD5 signatures. [SA-16:05]
81 Fix insecure default permissions for snmpd.config. [SA-16:06]
83 20151205 p8 FreeBSD-SA-15:26.openssl
85 Fix multiple OpenSSL vulnerabilities. [SA-15:26]
87 20151104 p7 FreeBSD-SA-15:25.ntp [revised]
88 FreeBSD-EN-15:19.kqueue
91 Fix regression in ntpd(8) lacking support for RAWDCF reference
92 clock in 10.2-RELEASE-p6. [SA-15:25]
94 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
96 Fix applications exiting due to segmentation violation on a correct
97 memory address. [EN-15:20.vm]
99 20151026: p6 FreeBSD-SA-15:25.ntp
101 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
103 20151002: p5 FreeBSD-SA-15:24.rpcbind [revised]
104 Revised patch to address a regression that prevents NIS from working.
106 20150929: p4 FreeBSD-SA-15:24.rpcbind
108 Fix rpcbind(8) remote denial of service. [SA-15:24]
110 20150916: p3 FreeBSD-EN-15:16.pw
111 FreeBSD-EN-15:17.libc
114 Fix regression in pw(8) when creating numeric users or groups.
117 Fix libc handling of signals for multi-threaded processes.
120 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
122 20150825: p2 FreeBSD-SA-15:22.openssh
124 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
126 Fix insufficient check of unsupported pkg(7) signature methods.
129 20150818: p1 FreeBSD-SA-15:20.expat
130 FreeBSD-EN-15:11.toolchain
131 FreeBSD-EN-15:12.netstat
132 FreeBSD-EN-15:13.vidcontrol
134 Fix multiple integer overflows in expat (libbsdxml) XML parser.
137 Fix make(1) syntax errors when upgrading from 9.x and earlier.
140 Fix incorrect netstat(1) data handling on 32-bit systems.
143 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
149 The default Unbound configuration now enables remote control
150 using a local socket. Users who have already enabled the
151 local_unbound service should regenerate their configuration
152 by running "service local_unbound setup" as root.
155 An additional fix for the issue described in the 20150614 sendmail
156 entry below has been been committed in revision 284786.
159 The fix for the issue described in the 20150614 sendmail entry
160 below has been been committed in revision 284485. The work
161 around described in that entry is no longer needed unless the
162 default setting is overridden by a confDH_PARAMETERS configuration
163 setting of '5' or pointing to a 512 bit DH parameter file.
166 The import of openssl to address the FreeBSD-SA-15:10.openssl
167 security advisory includes a change which rejects handshakes
168 with DH parameters below 768 bits. sendmail releases prior
169 to 8.15.2 (not yet released), defaulted to a 512 bit
170 DH parameter setting for client connections. To work around
171 this interoperability, sendmail can be configured to use a
172 2048 bit DH parameter by:
174 1. Edit /etc/mail/`hostname`.mc
175 2. If a setting for confDH_PARAMETERS does not exist or
176 exists and is set to a string beginning with '5',
178 3. If a setting for confDH_PARAMETERS exists and is set to
179 a file path, create a new file with:
180 openssl dhparam -out /path/to/file 2048
181 4. Rebuild the .cf file:
182 cd /etc/mail/; make; make install
184 cd /etc/mail/; make restart
186 A sendmail patch is coming, at which time this file will be
190 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
191 defined in symlink(7); previously symlinks were silently ignored.
194 The const qualifier has been removed from iconv(3) to comply with
195 POSIX. The ports tree is aware of this from r384038 onwards.
198 At svn r275807, The default linux compat kernel ABI has been adjusted
199 to 2.6.18 in support of the linux-c6 compat ports infrastructure
200 update. If you wish to continue using the linux-f10 compat ports,
201 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
202 encouraged to update their linux-compat packages to linux-c6 during
203 their next update cycle.
205 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
208 pjdfstest has been integrated into kyua as an opt-in test suite.
209 Please see share/doc/pjdfstest/README for a more details on how to
216 The ofwfb driver, used to provide a graphics console on PowerPC when
217 using vt(4), no longer allows mmap() of all of physical memory. This
218 will prevent Xorg on PowerPC with some ATI graphics cards from
219 initializing properly unless x11-servers/xorg-server is updated to
223 The libatf-c and libatf-c++ major versions were downgraded to 0 and
224 1 respectively to match the upstream numbers. They were out of
225 sync because, when they were originally added to FreeBSD, the
226 upstream versions were not respected. These libraries are private
227 and not yet built by default, so renumbering them should be a
228 non-issue. However, unclean source trees will yield broken test
229 programs once the operator executes "make delete-old-libs" after a
232 Additionally, the atf-sh binary was made private by moving it into
233 /usr/libexec/. Already-built shell test programs will keep the
234 path to the old binary so they will break after "make delete-old"
237 If you are using WITH_TESTS=yes (not the default), wipe the object
238 tree and rebuild from scratch to prevent spurious test failures.
239 This is only needed once: the misnumbered libraries and misplaced
240 binaries have been added to OptionalObsoleteFiles.inc so they will
241 be removed during a clean upgrade.
244 The ixgbe tunables now match their sysctl counterparts, for example:
245 hw.ixgbe.enable_aim => hw.ix.enable_aim
246 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
249 The NFSv4.1 server committed by r269398 changes the internal
250 function call interfaces used between the NFS and krpc modules.
251 As such, __FreeBSD_version was bumped.
254 The default unbound configuration has been modified to address
255 issues with reverse lookups on networks that use private
256 address ranges. If you use the local_unbound service, run
257 "service local_unbound setup" as root to regenerate your
258 configuration, then "service local_unbound reload" to load the
262 It is no longer necessary to include the dwarf version in your DEBUG
263 options in your kernel config file. The bug that required it to be
264 placed in the config file has bene fixed. DEBUG should now just
265 contain -g. The build system will automatically update things
266 to do the right thing.
269 Several ABI breaking changes were merged to CTL and new iSCSI code.
270 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
271 iscsictl need to be rebuilt to work with a new kernel.
274 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
275 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
276 which differs from the behaviour controlled by this knob.)
279 On i386 and amd64 systems, the onifconsole flag is now set by default
280 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
281 as a login TTY if it is set in the bootloader as an active kernel
282 console. No changes in behavior should result otherwise. To revert to
283 the previous behavior, set ttyu0 to "off" in /etc/ttys.
286 Clang and llvm have been upgraded to 3.4.1 release.
289 Clang and llvm have been upgraded to 3.4 release.
292 If a Makefile in a tests/ directory was auto-generating a Kyuafile
293 instead of providing an explicit one, this would prevent such
294 Makefile from providing its own Kyuafile in the future during
295 NO_CLEAN builds. This has been fixed in the Makefiles but manual
296 intervention is needed to clean an objdir if you use NO_CLEAN:
297 # find /usr/obj -name Kyuafile | xargs rm -f
300 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
301 capability mode support. Please note that enabling the feature in
302 kernel is still highly recommended.
305 OpenSSH is now built with sandbox support, and will use sandbox as
306 the default privilege separation method. This requires Capsicum
307 capability mode support in kernel.
310 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
311 been deprecated and will not be part of FreeBSD 11.0 and later
312 releases. If you use this driver, please consider switching to
313 the nfe(4) driver instead.
319 The behavior of gss_pseudo_random() for the krb5 mechanism
320 has changed, for applications requesting a longer random string
321 than produced by the underlying enctype's pseudo-random() function.
322 In particular, the random string produced from a session key of
323 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
324 be different at the 17th octet and later, after this change.
325 The counter used in the PRF+ construction is now encoded as a
326 big-endian integer in accordance with RFC 4402.
327 __FreeBSD_version is bumped to 1000701.
330 The WITHOUT_ATF build knob has been removed and its functionality
331 has been subsumed into the more generic WITHOUT_TESTS. If you were
332 using the former to disable the build of the ATF libraries, you
333 should change your settings to use the latter.
336 The default version of mtree is nmtree which is obtained from
337 NetBSD. The output is generally the same, but may vary
338 slightly. If you found you need identical output adding
339 "-F freebsd9" to the command line should do the trick. For the
340 time being, the old mtree is available as fmtree.
343 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
344 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
345 1.1.4_8 and verify bsdyml not linked in, before running "make
347 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
349 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
352 The rc.d/jail script has been updated to support jail(8)
353 configuration file. The "jail_<jname>_*" rc.conf(5) variables
354 for per-jail configuration are automatically converted to
355 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
356 This is transparently backward compatible. See below about some
357 incompatibilities and rc.conf(5) manual page for more details.
359 These variables are now deprecated in favor of jail(8) configuration
360 file. One can use "rc.d/jail config <jname>" command to generate
361 a jail(8) configuration file in /var/run/jail.<jname>.conf without
362 running the jail(8) utility. The default pathname of the
363 configuration file is /etc/jail.conf and can be specified by
364 using $jail_conf or $jail_<jname>_conf variables.
366 Please note that jail_devfs_ruleset accepts an integer at
367 this moment. Please consider to rewrite the ruleset name
371 BIND has been removed from the base system. If all you need
372 is a local resolver, simply enable and start the local_unbound
373 service instead. Otherwise, several versions of BIND are
374 available in the ports tree. The dns/bind99 port is one example.
376 With this change, nslookup(1) and dig(1) are no longer in the base
377 system. Users should instead use host(1) and drill(1) which are
378 in the base system. Alternatively, nslookup and dig can
379 be obtained by installing the dns/bind-tools port.
382 With the addition of unbound(8), a new unbound user is now
383 required during installworld. "mergemaster -p" can be used to
384 add the user prior to installworld, as documented in the handbook.
387 OpenSSH is now built with DNSSEC support, and will by default
388 silently trust signed SSHFP records. This can be controlled with
389 the VerifyHostKeyDNS client configuration setting. DNSSEC support
390 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
393 The GNU Compiler Collection and C++ standard library (libstdc++)
394 are no longer built by default on platforms where clang is the system
395 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
399 The PROCDESC kernel option is now part of the GENERIC kernel
400 configuration and is required for the rwhod(8) to work.
401 If you are using custom kernel configuration, you should include
405 The API and ABI related to the Capsicum framework was modified
406 in backward incompatible way. The userland libraries and programs
407 have to be recompiled to work with the new kernel. This includes the
408 following libraries and programs, but the whole buildworld is
409 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
410 kdump, procstat, rwho, rwhod, uniq.
413 AES-NI intrinsic support has been added to gcc. The AES-NI module
414 has been updated to use this support. A new gcc is required to build
415 the aesni module on both i386 and amd64.
418 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
419 Thus "device padlock_rng" and "device rdrand_rng" should be
420 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
423 WITH_ICONV has been split into two feature sets. WITH_ICONV now
424 enables just the iconv* functionality and is now on by default.
425 WITH_LIBICONV_COMPAT enables the libiconv api and link time
426 compatability. Set WITHOUT_ICONV to build the old way.
427 If you have been using WITH_ICONV before, you will very likely
428 need to turn on WITH_LIBICONV_COMPAT.
431 INVARIANTS option now enables DEBUG for code with OpenSolaris and
432 Illumos origin, including ZFS. If you have INVARIANTS in your
433 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
435 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
436 locks if WITNESS option was set. Because that generated a lot of
437 witness(9) reports and all of them were believed to be false
438 positives, this is no longer done. New option OPENSOLARIS_WITNESS
439 can be used to achieve the previous behavior.
442 Timer values in IPv6 data structures now use time_uptime instead
443 of time_second. Although this is not a user-visible functional
444 change, userland utilities which directly use them---ndp(8),
445 rtadvd(8), and rtsold(8) in the base system---need to be updated
449 find -delete can now delete the pathnames given as arguments,
450 instead of only files found below them or if the pathname did
451 not contain any slashes. Formerly, the following error message
454 find: -delete: <path>: relative path potentially not safe
456 Deleting the pathnames given as arguments can be prevented
457 without error messages using -mindepth 1 or by changing
458 directory and passing "." as argument to find. This works in the
459 old as well as the new version of find.
462 Behavior of devfs rules path matching has been changed.
463 Pattern is now always matched against fully qualified devfs
464 path and slash characters must be explicitly matched by
465 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
466 subdirectories must be reviewed.
469 The default ARM ABI has changed to the ARM EABI. The old ABI is
470 incompatible with the ARM EABI and all programs and modules will
471 need to be rebuilt to work with a new kernel.
473 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
475 NOTE: Support for the old ABI will be removed in the future and
476 users are advised to upgrade.
479 pkg_install has been disconnected from the build if you really need it
480 you should add WITH_PKGTOOLS in your src.conf(5).
483 Most of network statistics structures were changed to be able
484 keep 64-bits counters. Thus all tools, that work with networking
485 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
488 Fix targets that run multiple make's to use && rather than ;
489 so that subsequent steps depend on success of previous.
491 NOTE: if building 'universe' with -j* on stable/8 or stable/9
492 it would be better to start the build using bmake, to avoid
493 overloading the machine.
496 Fix a bug that allowed a tracing process (e.g. gdb) to write
497 to a memory-mapped file in the traced process's address space
498 even if neither the traced process nor the tracing process had
499 write access to that file.
502 CVS has been removed from the base system. An exact copy
503 of the code is available from the devel/cvs port.
506 Some people report the following error after the switch to bmake:
508 make: illegal option -- J
509 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
511 *** [buildworld] Error code 2
513 this likely due to an old instance of make in
514 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
515 which src/Makefile will use that blindly, if it exists, so if
516 you see the above error:
518 rm -rf `make -V MAKEPATH`
523 Use bmake by default.
524 Whereas before one could choose to build with bmake via
525 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
526 make. The goal is to remove these knobs for 10-RELEASE.
528 It is worth noting that bmake (like gmake) treats the command
529 line as the unit of failure, rather than statements within the
530 command line. Thus '(cd some/where && dosomething)' is safer
531 than 'cd some/where; dosomething'. The '()' allows consistent
532 behavior in parallel build.
535 Fix a bug that allows NFS clients to issue READDIR on files.
538 The WITHOUT_IDEA option has been removed because
539 the IDEA patent expired.
542 The sysctl which controls TRIM support under ZFS has been renamed
543 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
547 The mergemaster command now uses the default MAKEOBJDIRPREFIX
548 rather than creating it's own in the temporary directory in
549 order allow access to bootstrapped versions of tools such as
550 install and mtree. When upgrading from version of FreeBSD where
551 the install command does not support -l, you will need to
552 install a new mergemaster command if mergemaster -p is required.
553 This can be accomplished with the command (cd src/usr.sbin/mergemaster
557 Legacy ATA stack, disabled and replaced by new CAM-based one since
558 FreeBSD 9.0, completely removed from the sources. Kernel modules
559 atadisk and atapi*, user-level tools atacontrol and burncd are
560 removed. Kernel option `options ATA_CAM` is now permanently enabled
564 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
565 and socketpair(2). Software, in particular Kerberos, may
566 automatically detect and use these during building. The resulting
567 binaries will not work on older kernels.
570 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
571 information, see the respective 20130304 entry).
574 Recent commits to callout(9) changed the size of struct callout,
575 so the KBI is probably heavily disturbed. Also, some functions
576 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
577 by macros. Every kernel module using it won't load, so rebuild
580 The ctl device has been re-enabled in GENERIC for i386 and amd64,
581 but does not initialize by default (because of the new CTL_DISABLE
582 option) to save memory. To re-enable it, remove the CTL_DISABLE
583 option from the kernel config file or set kern.cam.ctl.disable=0
584 in /boot/loader.conf.
587 The ctl device has been disabled in GENERIC for i386 and amd64.
588 This was done due to the extra memory being allocated at system
589 initialisation time by the ctl driver which was only used if
590 a CAM target device was created. This makes a FreeBSD system
591 unusable on 128MB or less of RAM.
594 A new compression method (lz4) has been merged to -HEAD. Please
595 refer to zpool-features(7) for more information.
597 Please refer to the "ZFS notes" section of this file for information
598 on upgrading boot ZFS pools.
601 A BSD-licensed patch(1) variant has been added and is installed
602 as bsdpatch, being the GNU version the default patch.
603 To inverse the logic and use the BSD-licensed one as default,
604 while having the GNU version installed as gnupatch, rebuild
605 and install world with the WITH_BSD_PATCH knob set.
608 Due to the use of the new -l option to install(1) during build
609 and install, you must take care not to directly set the INSTALL
610 make variable in your /etc/make.conf, /etc/src.conf, or on the
611 command line. If you wish to use the -C flag for all installs
612 you may be able to add INSTALL+=-C to /etc/make.conf or
616 The install(1) option -M has changed meaning and now takes an
617 argument that is a file or path to append logs to. In the
618 unlikely event that -M was the last option on the command line
619 and the command line contained at least two files and a target
620 directory the first file will have logs appended to it. The -M
621 option served little practical purpose in the last decade so its
622 use is expected to be extremely rare.
625 After switching to Clang as the default compiler some users of ZFS
626 on i386 systems started to experience stack overflow kernel panics.
627 Please consider using 'options KSTACK_PAGES=4' in such configurations.
630 GEOM_LABEL now mangles label names read from file system metadata.
631 Mangling affect labels containing spaces, non-printable characters,
632 '%' or '"'. Device names in /etc/fstab and other places may need to
636 By default, only the 10 most recent kernel dumps will be saved. To
637 restore the previous behaviour (no limit on the number of kernel dumps
638 stored in the dump directory) add the following line to /etc/rc.conf:
643 With the addition of auditdistd(8), a new auditdistd user is now
644 required during installworld. "mergemaster -p" can be used to
645 add the user prior to installworld, as documented in the handbook.
648 The sin6_scope_id member variable in struct sockaddr_in6 is now
649 filled by the kernel before passing the structure to the userland via
650 sysctl or routing socket. This means the KAME-specific embedded scope
651 id in sin6_addr.s6_addr[2] is always cleared in userland application.
652 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
653 __FreeBSD_version is bumped to 1000025.
656 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
657 This means that the world and kernel will be compiled with clang
658 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
659 and /usr/bin/cpp. To disable this behavior and revert to building
660 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
661 of current may need to bootstrap WITHOUT_CLANG first if the clang
662 build fails (its compatibility window doesn't extend to the 9 stable
666 The IPFIREWALL_FORWARD kernel option has been removed. Its
667 functionality now turned on by default.
670 The ZERO_COPY_SOCKET kernel option has been removed and
671 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
672 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
673 mechanism which is not safe and may result in kernel crashes.
674 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
675 driver supports disposeable external page sized mbuf storage.
676 Proper replacements for both zero-copy mechanisms are under
677 consideration and will eventually lead to complete removal
678 of the two kernel options.
681 The IPv4 network stack has been converted to network byte
682 order. The following modules need to be recompiled together
683 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
684 pf(4), ipfw(4), ng_ipfw(4), stf(4).
687 Support for non-MPSAFE filesystems was removed from VFS. The
688 VFS_VERSION was bumped, all filesystem modules shall be
692 All the non-MPSAFE filesystems have been disconnected from
693 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
694 portalfs, smbfs, xfs.
697 The interface cloning API and ABI has changed. The following
698 modules need to be recompiled together with kernel:
699 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
700 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
701 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
704 The sdhci driver was split in two parts: sdhci (generic SD Host
705 Controller logic) and sdhci_pci (actual hardware driver).
706 No kernel config modifications are required, but if you
707 load sdhc as a module you must switch to sdhci_pci instead.
710 Import the FUSE kernel and userland support into base system.
713 The GNU sort(1) program has been removed since the BSD-licensed
714 sort(1) has been the default for quite some time and no serious
715 problems have been reported. The corresponding WITH_GNU_SORT
719 The pfil(9) API/ABI for AF_INET family has been changed. Packet
720 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
724 The net80211(4) ABI has been changed to allow for improved driver
725 PS-POLL and power-save support. All wireless drivers need to be
726 recompiled to work with the new kernel.
729 The random(4) support for the VIA hardware random number
730 generator (`PADLOCK') is no longer enabled unconditionally.
731 Add the padlock_rng device in the custom kernel config if
732 needed. The GENERIC kernels on i386 and amd64 do include the
733 device, so the change only affects the custom kernel
737 The pf(4) packet filter ABI has been changed. pfctl(8) and
738 snmp_pf module need to be recompiled to work with new kernel.
741 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
742 to -HEAD. Pools that have empty_bpobj in active state can not be
743 imported read-write with ZFS implementations that do not support
744 this feature. For more information read the zpool-features(5)
748 The sparc64 ZFS loader has been changed to no longer try to auto-
749 detect ZFS providers based on diskN aliases but now requires these
750 to be explicitly listed in the OFW boot-device environment variable.
753 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
754 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
755 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
758 The following sysctls and tunables have been renamed for consistency
759 with other variables:
760 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
761 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
764 The sort utility has been replaced with BSD sort. For now, GNU sort
765 is also available as "gnusort" or the default can be set back to
766 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
767 installed as "bsdsort".
770 A new version of ZFS (pool version 5000) has been merged to -HEAD.
771 Starting with this version the old system of ZFS pool versioning
772 is superseded by "feature flags". This concept enables forward
773 compatibility against certain future changes in functionality of ZFS
774 pools. The first read-only compatible "feature flag" for ZFS pools
775 is named "com.delphix:async_destroy". For more information
776 read the new zpool-features(5) manual page.
777 Please refer to the "ZFS notes" section of this file for information
778 on upgrading boot ZFS pools.
781 The malloc(3) implementation embedded in libc now uses sources imported
782 as contrib/jemalloc. The most disruptive API change is to
783 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
784 delete it prior to installworld, and optionally re-create it using the
785 new format after rebooting. See malloc.conf(5) for details
786 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
790 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
791 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
792 now spelled mips. This is to aid compatibility with third-party
793 software that expects this naming scheme in uname(3). Little-endian
794 settings are unchanged. If you are updating a big-endian mips64 machine
795 from before this change, you may need to set MACHINE_ARCH=mips64 in
796 your environment before the new build system will recognize your machine.
799 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
803 Now unix domain sockets behave "as expected" on nullfs(5). Previously
804 nullfs(5) did not pass through all behaviours to the underlying layer,
805 as a result if we bound to a socket on the lower layer we could connect
806 only to the lower path; if we bound to the upper layer we could connect
807 only to the upper path. The new behavior is one can connect to both the
808 lower and the upper paths regardless what layer path one binds to.
811 The getifaddrs upgrade path broken with 20111215 has been restored.
812 If you have upgraded in between 20111215 and 20120209 you need to
813 recompile libc again with your kernel. You still need to recompile
814 world to be able to configure CARP but this restriction already
818 The set_rcvar() function has been removed from /etc/rc.subr. All
819 base and ports rc.d scripts have been updated, so if you have a
820 port installed with a script in /usr/local/etc/rc.d you can either
821 hand-edit the rcvar= line, or reinstall the port.
823 An easy way to handle the mass-update of /etc/rc.d:
824 rm /etc/rc.d/* && mergemaster -i
827 panic(9) now stops other CPUs in the SMP systems, disables interrupts
828 on the current CPU and prevents other threads from running.
829 This behavior can be reverted using the kern.stop_scheduler_on_panic
831 The new behavior can be incompatible with kern.sync_on_panic.
834 The carp(4) facility has been changed significantly. Configuration
835 of the CARP protocol via ifconfig(8) has changed, as well as format
836 of CARP events submitted to devd(8) has changed. See manual pages
837 for more information. The arpbalance feature of carp(4) is currently
838 not supported anymore.
840 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
841 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
842 need to be recompiled.
845 The acpi_wmi(4) status device /dev/wmistat has been renamed to
849 The option VFS_ALLOW_NONMPSAFE option has been added in order to
850 explicitely support non-MPSAFE filesystems.
851 It is on by default for all supported platform at this present
855 The broken amd(4) driver has been replaced with esp(4) in the amd64,
856 i386 and pc98 GENERIC kernel configuration files.
859 sysinstall has been removed
862 The stable/9 branch created in subversion. This corresponds to the
863 RELENG_9 branch in CVS.
866 This commit modifies vfs_register() so that it uses a hash
867 calculation to set vfc_typenum, which is enabled by default.
868 The first time a system is booted after this change, the
869 vfc_typenum values will change for all file systems. The
870 main effect of this is a change to the NFS server file handles
871 for file systems that use vfc_typenum in their fsid, such as ZFS.
872 It will, however, prevent vfc_typenum from changing when file
873 systems are loaded in a different order for subsequent reboots.
874 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
875 until you are ready to remount all NFS clients after a reboot.
878 Bump the shared library version numbers for libraries that
879 do not use symbol versioning, have changed the ABI compared
880 to stable/8 and which shared library version was not bumped.
881 Done as part of 9.0-RELEASE cycle.
884 During the merge of Capsicum features, the fget(9) KPI was modified.
885 This may require the rebuilding of out-of-tree device drivers --
886 issues have been reported specifically with the nVidia device driver.
887 __FreeBSD_version is bumped to 900041.
889 Also, there is a period between 20110811 and 20110814 where the
890 special devices /dev/{stdin,stdout,stderr} did not work correctly.
891 Building world from a kernel during that window may not work.
894 The packet filter (pf) code has been updated to OpenBSD 4.5.
895 You need to update userland tools to be in sync with kernel.
896 This update breaks backward compatibility with earlier pfsync(4)
897 versions. Care must be taken when updating redundant firewall setups.
900 The following sysctls and tunables are retired on x86 platforms:
902 machdep.hlt_logical_cpus
903 The following sysctl is retired:
904 machdep.hyperthreading_allowed
905 The sysctls were supposed to provide a way to dynamically offline and
906 online selected CPUs on x86 platforms, but the implementation has not
907 been reliable especially with SCHED_ULE scheduler.
908 machdep.hyperthreading_allowed tunable is still available to ignore
909 hyperthreading CPUs at OS level.
910 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
911 where X is an APIC ID of a CPU. Be advised, though, that disabling
912 CPUs in non-uniform fashion will result in non-uniform topology and
913 may lead to sub-optimal system performance with SCHED_ULE, which is
917 cpumask_t type is retired and cpuset_t is used in order to describe
921 Changes to ifconfig(8) for dynamic address family detection mandate
922 that you are running a kernel of 20110525 or later. Make sure to
923 follow the update procedure to boot a new kernel before installing
927 Support for sun4v architecture is officially dropped
930 Several KPI breaking changes have been committed to the mii(4) layer,
931 the PHY drivers and consequently some Ethernet drivers using mii(4).
932 This means that miibus.ko and the modules of the affected Ethernet
933 drivers need to be recompiled.
935 Note to kernel developers: Given that the OUI bit reversion problem
936 was fixed as part of these changes all mii(4) commits related to OUIs,
937 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
938 handling, no longer can be merged verbatim to stable/8 and previous
942 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
943 into their kernel configurations along with 'device pci'.
946 The default NFS client is now the new NFS client, so fstype "newnfs"
947 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
948 Although mounts via fstype "nfs" will usually work without userland
949 changes, it is recommended that the mount(8) and mount_nfs(8)
950 commands be rebuilt from sources and that a link to mount_nfs called
951 mount_oldnfs be created. The new client is compiled into the
952 kernel with "options NFSCL" and this is needed for diskless root
953 file systems. The GENERIC kernel configs have been changed to use
954 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
955 To use the regular/old client, you can "mount -t oldnfs ...". For
956 a diskless root file system, you must also include a line like:
958 vfs.root.mountfrom="oldnfs:"
960 in the boot/loader.conf on the root fs on the NFS server to make
961 a diskless root fs use the old client.
964 The GENERIC kernels for all architectures now default to the new
965 CAM-based ATA stack. It means that all legacy ATA drivers were
966 removed and replaced by respective CAM drivers. If you are using
967 ATA device names in /etc/fstab or other places, make sure to update
968 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
969 where 'Y's are the sequential numbers starting from zero for each type
970 in order of detection, unless configured otherwise with tunables,
971 see cam(4)). There will be symbolic links created in /dev/ to map
972 old adX devices to the respective adaY. They should provide basic
973 compatibility for file systems mounting in most cases, but they do
974 not support old user-level APIs and do not have respective providers
975 in GEOM. Consider using updated management tools with new device names.
977 It is possible to load devices ahci, ata, siis and mvs as modules,
978 but option ATA_CAM should remain in kernel configuration to make ata
979 module work as CAM driver supporting legacy ATA controllers. Device ata
980 still can be used in modular fashion (atacore + ...). Modules atadisk
981 and atapi* are not used and won't affect operation in ATA_CAM mode.
982 Note that to use CAM-based ATA kernel should include CAM devices
983 scbus, pass, da (or explicitly ada), cd and optionally others. All of
984 them are parts of the cam module.
986 ataraid(4) functionality is now supported by the RAID GEOM class.
987 To use it you can load geom_raid kernel module and use graid(8) tool
988 for management. Instead of /dev/arX device names, use /dev/raid/rX.
990 No kernel config options or code have been removed, so if a problem
991 arises, please report it and optionally revert to the old ATA stack.
992 In order to do it you can remove from the kernel config:
997 , and instead add back:
998 device atadisk # ATA disk drives
999 device ataraid # ATA RAID drives
1000 device atapicd # ATAPI CDROM drives
1001 device atapifd # ATAPI floppy drives
1002 device atapist # ATAPI tape drives
1005 The default NFS server has been changed to the new server, which
1006 was referred to as the experimental server. If you need to switch
1007 back to the old NFS server, you must now put the "-o" option on
1008 both the mountd and nfsd commands. This can be done using the
1009 mountd_flags and nfs_server_flags rc.conf variables until an
1010 update to the rc scripts is committed, which is coming soon.
1013 The GNU Objective-C runtime library (libobjc), and other Objective-C
1014 related components have been removed from the base system. If you
1015 require an Objective-C library, please use one of the available ports.
1018 ath(4) has been split into bus- and device- modules. if_ath contains
1019 the HAL, the TX rate control and the network device code. if_ath_pci
1020 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1021 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1022 in order to use ath on everything else.
1024 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1025 need to load if_ath and if_ath_pci for ath(4) operation.
1028 As part of the replacement of sysinstall, the process of building
1029 release media has changed significantly. For details, please re-read
1030 release(7), which has been updated to reflect the new build process.
1033 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1034 is the last available version under GPLv2. It brings a number of new
1035 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1036 4.1 and SSE 4.2), better support for powerpc64, a number of new
1037 directives, and lots of other small improvements. See the ChangeLog
1038 file in contrib/binutils for the full details.
1041 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1042 compliant, and will now use half of hash for authentication.
1043 This will break interoperability with all stacks (including all
1044 actual FreeBSD versions) who implement
1045 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1047 The only workaround with such peers is to use another HMAC
1048 algorithm for IPsec ("phase 2") authentication.
1051 Remove the uio_yield prototype and symbol. This function has
1052 been misnamed since it was introduced and should not be
1053 globally exposed with this name. The equivalent functionality
1054 is now available using kern_yield(curthread->td_user_pri).
1055 The function remains undocumented.
1058 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1059 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1060 for scalar sysctls is defined but disabled. Code that needs
1061 UQUAD to pass the type checking that must compile on older
1062 systems where the define is not present can check against
1063 __FreeBSD_version >= 900030.
1065 The system dialog(1) has been replaced with a new version previously
1066 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1067 with the previous version, but the libdialog associated with it has
1068 a largely incompatible API. As such, the original version of libdialog
1069 will be kept temporarily as libodialog, until its base system consumers
1070 are replaced or updated. Bump __FreeBSD_version to 900030.
1073 If you are trying to run make universe on a -stable system, and you get
1074 the following warning:
1075 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1076 unknown. config(8) likely too old."
1077 or something similar to it, then you must upgrade your -stable system
1078 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1079 stable/8) or build the config from the latest stable/8 branch and
1080 install it on your system.
1082 Prior to this date, building a current universe on 8-stable system from
1083 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1084 error in the first kernel build phase. A new config on those old
1085 systems will fix that problem for older versions of -current.
1088 The TCP stack has been modified to allow Khelp modules to interact with
1089 it via helper hook points and store per-connection data in the TCP
1090 control block. Bump __FreeBSD_version to 900029. User space tools that
1091 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1095 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1096 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1097 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1098 to take advantage of it instead of using custom implementations. This
1099 means that these drivers now no longer unconditionally advertise
1100 support for flow control but only do so if flow control is a selected
1101 media option. This was implemented in the generic support that way in
1102 order to allow flow control to be switched on and off via ifconfig(8)
1103 with the PHY specific default to typically off in order to protect
1104 from unwanted effects. Consequently, if you used flow control with
1105 one of the above mentioned drivers you now need to explicitly enable
1106 it, for example via:
1107 ifconfig bge0 media auto mediaopt flowcontrol
1109 Along with the above mentioned changes generic support for setting
1110 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1111 e1000phy(4) as well as ip1000phy(4) have been converted to take
1112 advantage of it. This means that these drivers now no longer take the
1113 link0 parameter for selecting master mode but the master media option
1114 has to be used instead, for example like in the following:
1115 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1117 Selection of master mode now is also available with all other PHY
1118 drivers supporting 1000baseT.
1121 The TCP stack has received a significant update to add support for
1122 modularised congestion control and generally improve the clarity of
1123 congestion control decisions. Bump __FreeBSD_version to 900025. User
1124 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1125 sockstat) need to be recompiled.
1128 The man(1) utility has been replaced by a new version that no longer
1129 uses /etc/manpath.config. Please consult man.conf(5) for how to
1130 migrate local entries to the new format.
1133 The copyright strings printed by login(1) and sshd(8) at the time of a
1134 new connection have been removed to follow other operating systems and
1138 A workaround for a fixed ld bug has been removed in kernel code,
1139 so make sure that your system ld is built from sources after
1140 revision 210245 from 2010-07-19 (r211583 if building head kernel
1141 on stable/8, r211584 for stable/7; both from 2010-08-21).
1142 A symptom of incorrect ld version is different addresses for
1143 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1146 The $ipv6_prefer variable in rc.conf(5) has been split into
1147 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1149 The $ip6addrctl_policy is a variable to choose a pre-defined
1150 address selection policy set by ip6addrctl(8). A value
1151 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1154 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1155 flag (see an entry of 20090926) is set on an interface with no
1156 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1157 security reason. If you want IPv6 link-local address on all
1158 interfaces by default, set this to "YES".
1160 The old ipv6_prefer="YES" is equivalent to
1161 ipv6_activate_all_interfaces="YES" and
1162 ip6addrctl_policy="ipv6_prefer".
1165 DTrace has grown support for userland tracing. Due to this, DTrace is
1166 now i386 and amd64 only.
1167 dtruss(1) is now installed by default on those systems and a new
1168 kernel module is needed for userland tracing: fasttrap.
1169 No changes to your kernel config file are necessary to enable
1170 userland tracing, but you might consider adding 'STRIP=' and
1171 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1172 to have informative userland stack traces in DTrace (ustack).
1175 The acpi_aiboost(4) driver has been removed in favor of the new
1176 aibs(4) driver. You should update your kernel configuration file.
1179 BSD grep has been imported to the base system and it is built by
1180 default. It is completely BSD licensed, highly GNU-compatible, uses
1181 less memory than its GNU counterpart and has a small codebase.
1182 However, it is slower than its GNU counterpart, which is mostly
1183 noticeable for larger searches, for smaller ones it is measurable
1184 but not significant. The reason is complex, the most important factor
1185 is that we lack a modern and efficient regex library and GNU
1186 overcomes this by optimizing the searches internally. Future work
1187 on improving the regex performance is planned, for the meantime,
1188 users that need better performance, can build GNU grep instead by
1189 setting the WITH_GNU_GREP knob.
1192 Due to the import of powerpc64 support, all existing powerpc kernel
1193 configuration files must be updated with a machine directive like this:
1194 machine powerpc powerpc
1196 In addition, an updated config(8) is required to build powerpc kernels
1200 A new version of ZFS (version 15) has been merged to -HEAD.
1201 This version uses a python library for the following subcommands:
1202 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1203 For full functionality of these commands the following port must
1204 be installed: sysutils/py-zfs
1207 'vm_page's are now hashed by physical address to an array of mutexes.
1208 Currently this is only used to serialize access to hold_count. Over
1209 time the page queue mutex will be peeled away. This changes the size
1210 of pmap on every architecture. And requires all callers of vm_page_hold
1211 and vm_page_unhold to be updated.
1214 WITH_CTF can now be specified in src.conf (not recommended, there
1215 are some problems with static executables), make.conf (would also
1216 affect ports which do not use GNU make and do not override the
1217 compile targets) or in the kernel config (via "makeoptions
1219 When WITH_CTF was specified there before this was silently ignored,
1220 so make sure that WITH_CTF is not used in places which could lead
1221 to unwanted behavior.
1224 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1225 to allow 32-bit compatibility on non-x86 platforms. All kernel
1226 configurations on amd64 and ia64 platforms using these options must
1227 be modified accordingly.
1230 The utmp user accounting database has been replaced with utmpx,
1231 the user accounting interface standardized by POSIX.
1232 Unfortunately the semantics of utmp and utmpx don't match,
1233 making it practically impossible to support both interfaces.
1234 The user accounting database is used by tools like finger(1),
1235 last(1), talk(1), w(1) and ac(8).
1237 All applications in the base system use utmpx. This means only
1238 local binaries (e.g. from the ports tree) may still use these
1239 utmp database files. These applications must be rebuilt to make
1242 After the system has been upgraded, it is safe to remove the old
1243 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1244 assuming their contents is of no importance anymore. Old wtmp
1245 databases can only be used by last(1) and ac(8) after they have
1246 been converted to the new format using wtmpcvt(1).
1249 Introduce the kernel thread "deadlock resolver" (which can be enabled
1250 via the DEADLKRES option, see NOTES for more details) and the
1251 sleepq_type() function for sleepqueues.
1254 The rc.firewall and rc.firewall6 were unified, and
1255 rc.firewall6 and rc.d/ip6fw were removed.
1256 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1257 variables are obsoleted. Instead, the following new rc
1258 variables are added to rc.d/ipfw:
1260 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1261 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1262 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1264 The meanings correspond to the relevant IPv4 variables.
1270 The default terminal emulation for syscons(4) has been changed
1271 from cons25 to xterm on all platforms except pc98. This means
1272 that the /etc/ttys file needs to be updated to ensure correct
1273 operation of applications on the console.
1275 The terminal emulation style can be toggled per window by using
1276 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1277 options can be used to change the compile-time default back to
1280 To prevent graphical artifacts, make sure the TERM environment
1281 variable is set to match the terminal emulation that is being
1282 performed by syscons(4).
1285 The layout of the structure ieee80211req_scan_result has changed.
1286 Applications that require wireless scan results (e.g. ifconfig(8))
1287 from net80211 need to be recompiled.
1289 Applications such as wpa_supplicant(8) may require a full world
1290 build without using NO_CLEAN in order to get synchronized with the
1294 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1295 There's one kernel module for each firmware. Adding "device iwnfw"
1296 to the kernel configuration file means including all three firmware
1297 images inside the kernel. If you want to include just the one for
1298 your wireless card, use the devices iwn4965fw, iwn5000fw or
1302 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1303 into rc.d/netif. The changes are the following:
1305 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1306 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1307 Note that both variables need the "inet6" keyword at the head.
1309 Do not set $ipv6_network_interfaces manually if you do not
1310 understand what you are doing. It is not needed in most cases.
1312 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1315 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1316 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1318 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1319 all configured interfaces have "inet6 accept_rtadv" in the
1320 $ifconfig_IF_ipv6. These are for backward compatibility.
1322 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1323 functionality of interfaces with no corresponding
1324 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1325 and the default address selection policy of ip6addrctl(8)
1326 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1327 Note that if you want to configure IPv6 functionality on the
1328 disabled interfaces after boot, first you need to clear the flag by
1329 using ifconfig(8) like:
1331 ifconfig em0 inet6 -ifdisabled
1333 If YES, the default address selection policy is set as
1336 The default value of $ipv6_prefer is NO.
1338 4. If your system need to receive Router Advertisement messages,
1339 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1340 scripts automatically invoke rtsol(8) when the interface becomes
1341 UP. The Router Advertisement messages are used for SLAAC
1342 (State-Less Address AutoConfiguration).
1345 802.11s D3.03 support was committed. This is incompatible with the
1346 previous code, which was based on D3.0.
1349 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1350 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1351 control whether accepting Router Advertisement messages or not.
1352 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1353 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1354 The ifconfig(8) utility now supports these flags.
1357 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1358 mount(8) and -a option for df(1) to see them.
1361 The old tunable hw.bus.devctl_disable has been superseded by
1362 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1363 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1367 Remove the option STOP_NMI. The default action is now to use NMI only
1368 for KDB via the newly introduced function stop_cpus_hard() and
1369 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1372 The stable/8 branch created in subversion. This corresponds to the
1373 RELENG_8 branch in CVS.
1376 Bump the shared library version numbers for all libraries that do not
1377 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1378 __FreeBSD_version to 800105.
1381 Due to changes in the implementation of virtual network stack support,
1382 all network-related kernel modules must be recompiled. As this change
1383 breaks the ABI, bump __FreeBSD_version to 800104.
1386 The TOE interface to the TCP syncache has been modified to remove
1387 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1388 The cxgb driver is the only TOE consumer affected by this change, and
1389 needs to be recompiled along with the kernel. As this change breaks
1390 the ABI, bump __FreeBSD_version to 800103.
1393 Padding has been added to struct tcpcb, sackhint and tcpstat in
1394 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1395 maintaining the ABI. However, this change breaks the ABI, so bump
1396 __FreeBSD_version to 800102. User space tools that rely on the size of
1397 any of these structs (e.g. sockstat) need to be recompiled.
1400 The NFS_LEGACYRPC option has been removed along with the old kernel
1401 RPC implementation that this option selected. Kernel configurations
1402 may need to be adjusted.
1405 The network interface device nodes at /dev/net/<interface> have been
1406 removed. All ioctl operations can be performed the normal way using
1407 routing sockets. The kqueue functionality can generally be replaced
1408 with routing sockets.
1411 The documentation from the FreeBSD Documentation Project (Handbook,
1412 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1413 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1416 The ABI of various structures related to the SYSV IPC API have been
1417 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1418 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1422 Layout of struct vnet has changed as routing related variables were
1423 moved to their own Vimage module. Modules need to be recompiled. Bump
1424 __FreeBSD_version to 800099.
1427 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1428 respectively. As long as no more than 16 groups per process are used,
1429 no changes should be visible. When more than 16 groups are used, old
1430 binaries may fail if they call getgroups() or getgrouplist() with
1431 statically sized storage. Recompiling will work around this, but
1432 applications should be modified to use dynamically allocated storage
1433 for group arrays as POSIX.1-2008 does not cap an implementation's
1434 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1436 NFS and portalfs mounts may also be affected as the list of groups is
1437 truncated to 16. Users of NFS who use more than 16 groups, should
1438 take care that negative group permissions are not used on the exported
1439 file systems as they will not be reliable unless a GSSAPI based
1440 authentication method is used.
1443 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1444 option compiles in the support for adaptive spinning for lockmgrs
1445 which want to enable it. The lockinit() function now accepts the flag
1446 LK_ADAPTIVE in order to make the lock object subject to adaptive
1447 spinning when both held in write and read mode.
1450 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1451 changed. User applications that use this ioctl need to be rebuilt.
1454 The layout of struct thread has changed. Kernel and modules need to
1458 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1459 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1462 window(1) has been removed from the base system. It can now be
1463 installed from ports. The port is called misc/window.
1466 The way we are storing and accessing `routing table' entries has
1467 changed. Programs reading the FIB, like netstat, need to be
1471 A new netisr implementation has been added for FreeBSD 8. Network
1472 file system modules, such as igmp, ipdivert, and others, should be
1474 Bump __FreeBSD_version to 800096.
1477 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1481 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1482 Bump __FreeBSD_version to 800094.
1485 Add mnt_xflag field to 'struct mount'. File system modules need to be
1487 Bump __FreeBSD_version to 800093.
1490 The compiling option ADAPTIVE_SX has been retired while it has been
1491 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1492 The KPI for sx_init_flags() changes as accepting flags:
1493 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1494 been introduced in order to handle the reversed logic.
1495 Bump __FreeBSD_version to 800092.
1498 Add support for hierarchical jails. Remove global securelevel.
1499 Bump __FreeBSD_version to 800091.
1502 The layout of struct vnet_net has changed, therefore modules
1504 Bump __FreeBSD_version to 800090.
1507 The newly imported zic(8) produces a new format in the output. Please
1508 run tzsetup(8) to install the newly created data to /etc/localtime.
1511 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1512 hw.usb.* and is now consistent again with previous releases.
1515 802.11 monitor mode support was revised and driver api's were changed.
1516 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1517 of DLT_IEEE802_11. No user-visible data structures were changed but
1518 applications that use DLT_IEEE802_11 may require changes.
1519 Bump __FreeBSD_version to 800088.
1522 The layout of the following structs has changed: sysctl_oid,
1523 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1524 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1525 panics may be experienced. World rebuild is required for
1526 correctly checking networking state from userland.
1527 Bump __FreeBSD_version to 800085.
1530 MLDv2 and Source-Specific Multicast (SSM) have been merged
1531 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1532 The implementation of SSM within FreeBSD's IPv6 stack closely
1533 follows the IPv4 implementation.
1535 For kernel developers:
1537 * The most important changes are that the ip6_output() and
1538 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1539 and this lock has been downgraded to a non-recursive mutex.
1541 * As with the changes to the IPv4 stack to support SSM, filtering
1542 of inbound multicast traffic must now be performed by transport
1543 protocols within the IPv6 stack. This does not apply to TCP and
1544 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1546 * The KPIs used by IPv6 multicast are similar to those used by
1547 the IPv4 stack, with the following differences:
1548 * im6o_mc_filter() is analogous to imo_multicast_filter().
1549 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1550 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1551 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1552 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1553 for MLDv1 have an additional 'timer' argument which is used to
1554 jitter the initial membership report for the solicited-node
1555 multicast membership on-link.
1556 * This is not strictly needed for MLDv2, which already jitters
1557 its report transmissions. However, the 'timer' argument is
1558 preserved in case MLDv1 is active on the interface.
1560 * The KAME linked-list based IPv6 membership implementation has
1561 been refactored to use a vector similar to that used by the IPv4
1563 Code which maintains a list of its own multicast memberships
1564 internally, e.g. carp, has been updated to reflect the new
1567 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1568 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1569 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1570 implementation constraint which needs to be addressed in HEAD.
1572 For application developers:
1574 * The changes are broadly similar to those made for the IPv4
1577 * The use of IPv4 and IPv6 multicast socket options on the same
1578 socket, using mapped addresses, HAS NOT been tested or supported.
1580 * There are a number of issues with the implementation of various
1581 IPv6 multicast APIs which need to be resolved in the API surface
1582 before the implementation is fully compatible with KAME userland
1583 use, and these are mostly to do with interface index treatment.
1585 * The literature available discusses the use of either the delta / ASM
1586 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1587 using setsourcefilter(3)/getsourcefilter(3). For more information
1588 please refer to RFC 3768, 'Socket Interface Extensions for
1589 Multicast Source Filters'.
1591 * Applications which use the published RFC 3678 APIs should be fine.
1593 For systems administrators:
1595 * The mtest(8) utility has been refactored to support IPv6, in
1596 addition to IPv4. Interface addresses are no longer accepted
1597 as arguments, their names must be used instead. The utility
1598 will map the interface name to its first IPv4 address as
1599 returned by getifaddrs(3).
1601 * The ifmcstat(8) utility has also been updated to print the MLDv2
1602 endpoint state and source filter lists via sysctl(3).
1604 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1605 loopback of IPv6 multicast datagrams by default; it defaults to 1
1606 to preserve the existing behaviour. Disabling multicast loopback is
1607 recommended for optimal system performance.
1609 * The IPv6 MROUTING code has been changed to examine this sysctl
1610 instead of attempting to perform a group lookup before looping
1611 back forwarded datagrams.
1613 Bump __FreeBSD_version to 800084.
1616 Implement low-level Bluetooth HCI API.
1617 Bump __FreeBSD_version to 800083.
1620 The layout of struct malloc_type, used by modules to register new
1621 memory allocation types, has changed. Most modules will need to
1622 be rebuilt or panics may be experienced.
1623 Bump __FreeBSD_version to 800081.
1626 Anticipate overflowing inp_flags - add inp_flags2.
1627 This changes most offsets in inpcb, so checking v4 connection
1628 state will require a world rebuild.
1629 Bump __FreeBSD_version to 800080.
1632 Add an llentry to struct route and struct route_in6. Modules
1633 embedding a struct route will need to be recompiled.
1634 Bump __FreeBSD_version to 800079.
1637 The size of rt_metrics_lite and by extension rtentry has changed.
1638 Networking administration apps will need to be recompiled.
1639 The route command now supports show as an alias for get, weighting
1640 of routes, sticky and nostick flags to alter the behavior of stateful
1642 Bump __FreeBSD_version to 800078.
1645 Do not use Giant for kbdmux(4) locking. This is wrong and
1646 apparently causing more problems than it solves. This will
1647 re-open the issue where interrupt handlers may race with
1648 kbdmux(4) in polling mode. Typical symptoms include (but
1649 not limited to) duplicated and/or missing characters when
1650 low level console functions (such as gets) are used while
1651 interrupts are enabled (for example geli password prompt,
1652 mountroot prompt etc.). Disabling kbdmux(4) may help.
1655 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1656 kernel modules referencing any of the above need to be recompiled.
1657 Bump __FreeBSD_version to 800075.
1660 GEOM_PART has become the default partition slicer for storage devices,
1661 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1662 introduces some changes:
1664 MSDOS/EBR: the devices created from MSDOS extended partition entries
1665 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1666 to devices with offset-based names. fstabs may need to be modified.
1668 BSD: the "geometry does not match label" warning is harmless in most
1669 cases but it points to problems in file system misalignment with
1670 disk geometry. The "c" partition is now implicit, covers the whole
1671 top-level drive and cannot be (mis)used by users.
1673 General: Kernel dumps are now not allowed to be written to devices
1674 whose partition types indicate they are meant to be used for file
1675 systems (or, in case of MSDOS partitions, as something else than
1678 Most of these changes date approximately from 200812.
1681 The uscanner(4) driver has been removed from the kernel. This follows
1682 Linux removing theirs in 2.6 and making libusb the default interface
1683 (supported by sane).
1686 The multicast forwarding code has been cleaned up. netstat(1)
1687 only relies on KVM now for printing bandwidth upcall meters.
1688 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1689 ip6_mroute_mod respectively. The config(5) options for statically
1690 compiling this code remain the same, i.e. 'options MROUTING'.
1693 Support for the IFF_NEEDSGIANT network interface flag has been
1694 removed, which means that non-MPSAFE network device drivers are no
1695 longer supported. In particular, if_ar, if_sr, and network device
1696 drivers from the old (legacy) USB stack can no longer be built or
1700 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1701 a bunch of new language catalog files have also been added.
1702 This means that some common libc messages are now localized and
1703 they depend on the LC_MESSAGES environmental variable.
1706 The k8temp(4) driver has been renamed to amdtemp(4) since
1707 support for Family 10 and Family 11 CPU families was added.
1710 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1711 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1713 For kernel developers, the most important changes are that the
1714 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1715 and this lock has been downgraded to a non-recursive mutex.
1717 Transport protocols (UDP, Raw IP) are now responsible for filtering
1718 inbound multicast traffic according to group membership and source
1719 filters. The imo_multicast_filter() KPI exists for this purpose.
1720 Transports which do not use multicast (SCTP, TCP) already reject
1721 multicast by default. Forwarding and receive performance may improve
1722 as a mutex acquisition is no longer needed in the ip_input()
1723 low-level input path. in_addmulti() and in_delmulti() are shimmed
1724 to new KPIs which exist to support SSM in-kernel.
1726 For application developers, it is recommended that loopback of
1727 multicast datagrams be disabled for best performance, as this
1728 will still cause the lock to be taken for each looped-back
1729 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1730 be tuned to 0 to disable loopback by default; it defaults to 1
1731 to preserve the existing behaviour.
1733 For systems administrators, to obtain best performance with
1734 multicast reception and multiple groups, it is always recommended
1735 that a card with a suitably precise hash filter is used. Hash
1736 collisions will still result in the lock being taken within the
1737 transport protocol input path to check group membership.
1739 If deploying FreeBSD in an environment with IGMP snooping switches,
1740 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1741 enabled; this forces 224.0.0.0/24 group membership to be announced
1744 The size of 'struct igmpstat' has changed; netstat needs to be
1745 recompiled to reflect this.
1746 Bump __FreeBSD_version to 800070.
1749 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1750 updated to use it. This requires a buildworld/installworld in order to
1751 update the library and dependencies (usbconfig, etc). Its advisable to
1752 rebuild all ports which uses libusb. More specific directions are given
1753 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1754 libusb are no longer required and can be removed.
1757 A workaround is committed to allow the creation of System V shared
1758 memory segment of size > 2 GB on the 64-bit architectures.
1759 Due to a limitation of the existing ABI, the shm_segsz member
1760 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1761 wrong for large segments. Note that limits must be explicitly
1762 raised to allow such segments to be created.
1765 The layout of struct ifnet has changed, requiring a rebuild of all
1766 network device driver modules.
1769 The /dev handling for the new USB stack has changed, a
1770 buildworld/installworld is required for libusb20.
1773 The new USB2 stack has now been permanently moved in and all kernel and
1774 module names reverted to their previous values (eg, usb, ehci, ohci,
1775 ums, ...). The old usb stack can be compiled in by prefixing the name
1776 with the letter 'o', the old usb modules have been removed.
1777 Updating entry 20090216 for xorg and 20090215 for libmap may still
1781 The rc.conf(5) option if_up_delay has been renamed to
1782 defaultroute_delay to better reflect its purpose. If you have
1783 customized this setting in /etc/rc.conf you need to update it to
1787 xorg 7.4 wants to configure its input devices via hald which does not
1788 yet work with USB2. If the keyboard/mouse does not work in xorg then
1790 Option "AllowEmptyInput" "off"
1791 to your ServerLayout section. This will cause X to use the configured
1792 kbd and mouse sections from your xorg.conf.
1795 The GENERIC kernels for all architectures now default to the new USB2
1796 stack. No kernel config options or code have been removed so if a
1797 problem arises please report it and optionally revert to the old USB
1798 stack. If you are loading USB kernel modules or have a custom kernel
1799 that includes GENERIC then ensure that usb names are also changed over,
1800 eg uftdi -> usb2_serial_ftdi.
1802 Older programs linked against the ports libusb 0.1 need to be
1803 redirected to the new stack's libusb20. /etc/libmap.conf can
1805 # Map old usb library to new one for usb2 stack
1806 libusb-0.1.so.8 libusb20.so.1
1809 All USB ethernet devices now attach as interfaces under the name ueN
1810 (eg. ue0). This is to provide a predictable name as vendors often
1811 change usb chipsets in a product without notice.
1814 The ichsmb(4) driver has been changed to require SMBus slave
1815 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1816 All of the other SMBus controller drivers require left-justified
1817 slave addresses, so this change makes all the drivers provide the
1821 INET6 statistics (struct ip6stat) was updated.
1822 netstat(1) needs to be recompiled.
1825 NTFS has been removed from GENERIC kernel on amd64 to match
1826 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1827 will load ntfs.ko module automatically when NTFS support is
1828 actually needed, unless ntfs.ko is not installed or security
1829 level prohibits loading kernel modules. If either is the case,
1830 "options NTFS" has to be added into kernel config.
1833 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1834 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1835 800061. User space tools that rely on the size of struct tcpcb in
1836 tcp_var.h (e.g. sockstat) need to be recompiled.
1839 ng_tty(4) module updated to match the new TTY subsystem.
1840 Due to API change, user-level applications must be updated.
1841 New API support added to mpd5 CVS and expected to be present
1842 in next mpd5.3 release.
1845 With __FreeBSD_version 800060 the makefs tool is part of
1846 the base system (it was a port).
1849 The afdata and ifnet locks have been changed from mutexes to
1850 rwlocks, network modules will need to be re-compiled.
1853 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1854 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1855 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1856 architecture and 40 bytes on 64-bit architecture. The userland
1857 applications "arp" and "ndp" have been updated accordingly.
1858 The output from "netstat -r" shows only routing entries and
1859 none of the L2 information.
1862 __FreeBSD_version 800057 marks the switchover from the
1863 binary ath hal to source code. Users must add the line:
1865 options AH_SUPPORT_AR5416
1867 to their kernel config files when specifying:
1871 The ath_hal module no longer exists; the code is now compiled
1872 together with the driver in the ath module. It is now
1873 possible to tailor chip support (i.e. reduce the set of chips
1874 and thereby the code size); consult ath_hal(4) for details.
1877 __FreeBSD_version 800054 adds memory barriers to
1878 <machine/atomic.h>, new interfaces to ifnet to facilitate
1879 multiple hardware transmit queues for cards that support
1880 them, and a lock-less ring-buffer implementation to
1881 enable drivers to more efficiently manage queueing of
1885 A new version of ZFS (version 13) has been merged to -HEAD.
1886 This version has zpool attribute "listsnapshots" off by
1887 default, which means "zfs list" does not show snapshots,
1888 and is the same as Solaris behavior.
1891 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1894 The uhci, ohci, ehci and slhci USB Host controller drivers have
1895 been put into separate modules. If you load the usb module
1896 separately through loader.conf you will need to load the
1897 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1898 controller add the following to loader.conf:
1904 The ABI used by the PMC toolset has changed. Please keep
1905 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1909 atapci kernel module now includes only generic PCI ATA
1910 driver. AHCI driver moved to ataahci kernel module.
1911 All vendor-specific code moved into separate kernel modules:
1912 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1913 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1914 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1915 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1918 The TTY subsystem of the kernel has been replaced by a new
1919 implementation, which provides better scalability and an
1920 improved driver model. Most common drivers have been migrated to
1921 the new TTY subsystem, while others have not. The following
1922 drivers have not yet been ported to the new TTY layer:
1925 cy, digi, rc, rp, sio
1931 ng_h4, ng_tty, ppp, sl, snp
1933 Adding these drivers to your kernel configuration file shall
1934 cause compilation to fail.
1937 ntpd has been upgraded to 4.2.4p5.
1940 OpenSSH has been upgraded to 5.1p1.
1942 For many years, FreeBSD's version of OpenSSH preferred DSA
1943 over RSA for host and user authentication keys. With this
1944 upgrade, we've switched to the vendor's default of RSA over
1945 DSA. This may cause upgraded clients to warn about unknown
1946 host keys even for previously known hosts. Users should
1947 follow the usual procedure for verifying host keys before
1948 accepting the RSA key.
1950 This can be circumvented by setting the "HostKeyAlgorithms"
1951 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1954 Please note that the sequence of keys offered for
1955 authentication has been changed as well. You may want to
1956 specify IdentityFile in a different order to revert this
1960 The sio(4) driver has been removed from the i386 and amd64
1961 kernel configuration files. This means uart(4) is now the
1962 default serial port driver on those platforms as well.
1964 To prevent collisions with the sio(4) driver, the uart(4) driver
1965 uses different names for its device nodes. This means the
1966 onboard serial port will now most likely be called "ttyu0"
1967 instead of "ttyd0". You may need to reconfigure applications to
1968 use the new device names.
1970 When using the serial port as a boot console, be sure to update
1971 /boot/device.hints and /etc/ttys before booting the new kernel.
1972 If you forget to do so, you can still manually specify the hints
1973 at the loader prompt:
1975 set hint.uart.0.at="isa"
1976 set hint.uart.0.port="0x3F8"
1977 set hint.uart.0.flags="0x10"
1978 set hint.uart.0.irq="4"
1982 The gpt(8) utility has been removed. Use gpart(8) to partition
1986 The version that Linuxulator emulates was changed from 2.4.2
1987 to 2.6.16. If you experience any problems with Linux binaries
1988 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1989 if it fixes the problem contact emulation mailing list.
1992 ISDN4BSD (I4B) was removed from the src tree. You may need to
1993 update a your kernel configuration and remove relevant entries.
1996 I have checked in code to support multiple routing tables.
1997 See the man pages setfib(1) and setfib(2).
1998 This is a hopefully backwards compatible version,
1999 but to make use of it you need to compile your kernel
2000 with options ROUTETABLES=2 (or more up to 16).
2003 The 802.11 wireless support was redone to enable multi-bss
2004 operation on devices that are capable. The underlying device
2005 is no longer used directly but instead wlanX devices are
2006 cloned with ifconfig. This requires changes to rc.conf files.
2007 For example, change:
2008 ifconfig_ath0="WPA DHCP"
2011 ifconfig_wlan0="WPA DHCP"
2012 see rc.conf(5) for more details. In addition, mergemaster of
2013 /etc/rc.d is highly recommended. Simultaneous update of userland
2014 and kernel wouldn't hurt either.
2016 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2017 modules were merged into the base wlan module. All references
2018 to these modules (e.g. in kernel config files) must be removed.
2021 psm(4) has gained write(2) support in native operation level.
2022 Arbitrary commands can be written to /dev/psm%d and status can
2023 be read back from it. Therefore, an application is responsible
2024 for status validation and error recovery. It is a no-op in
2025 other operation levels.
2028 Support for KSE threading has been removed from the kernel. To
2029 run legacy applications linked against KSE libmap.conf may
2030 be used. The following libmap.conf may be used to ensure
2031 compatibility with any prior release:
2033 libpthread.so.1 libthr.so.1
2034 libpthread.so.2 libthr.so.2
2035 libkse.so.3 libthr.so.3
2038 The layout of struct vmspace has changed. This affects libkvm
2039 and any executables that link against libkvm and use the
2040 kvm_getprocs() function. In particular, but not exclusively,
2041 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2042 The effects are minimal, but it's advisable to upgrade world
2046 The latest em driver no longer has support in it for the
2047 82575 adapter, this is now moved to the igb driver. The
2048 split was done to make new features that are incompatible
2049 with older hardware easier to do.
2052 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2053 likewise the kernel option is now GEOM_LINUX_LVM.
2056 The default NFS mount mode has changed from UDP to TCP for
2057 increased reliability. If you rely on (insecurely) NFS
2058 mounting across a firewall you may need to update your
2062 Belatedly note the addition of m_collapse for compacting
2066 The fts(3) structures have been changed to use adequate
2067 integer types for their members and so to be able to cope
2068 with huge file trees. The old fts(3) ABI is preserved
2069 through symbol versioning in libc, so third-party binaries
2070 using fts(3) should still work, although they will not take
2071 advantage of the extended types. At the same time, some
2072 third-party software might fail to build after this change
2073 due to unportable assumptions made in its source code about
2074 fts(3) structure members. Such software should be fixed
2075 by its vendor or, in the worst case, in the ports tree.
2076 FreeBSD_version 800015 marks this change for the unlikely
2077 case that a portable fix is impossible.
2080 To upgrade to -current after this date, you must be running
2081 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2082 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2085 The ADAPTIVE_GIANT kernel option has been retired because its
2086 functionality is the default now.
2089 The AT keyboard emulation of sunkbd(4) has been turned on
2090 by default. In order to make the special symbols of the Sun
2091 keyboards driven by sunkbd(4) work under X these now have
2092 to be configured the same way as Sun USB keyboards driven
2093 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2095 Option "XkbLayout" "us"
2096 Option "XkbRules" "xorg"
2097 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2100 It has been decided that it is desirable to provide ABI
2101 backwards compatibility to the FreeBSD 4/5/6 versions of the
2102 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2103 broken with the introduction of PCI domain support (see the
2104 20070930 entry). Unfortunately, this required the ABI of
2105 PCIOCGETCONF to be broken again in order to be able to
2106 provide backwards compatibility to the old version of that
2107 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2108 again. As for prominent ports this affects neither pciutils
2109 nor xorg-server this time, the hal port needs to be rebuilt
2113 The misnamed kthread_create() and friends have been renamed
2114 to kproc_create() etc. Many of the callers already
2115 used kproc_start()..
2116 I will return kthread_create() and friends in a while
2117 with implementations that actually create threads, not procs.
2118 Renaming corresponds with version 800002.
2127 Avoid using make -j when upgrading. While generally safe, there are
2128 sometimes problems using -j to upgrade. If your upgrade fails with
2129 -j, please try again without -j. From time to time in the past there
2130 have been problems using -j with buildworld and/or installworld. This
2131 is especially true when upgrading between "distant" versions (eg one
2132 that cross a major release boundary or several minor releases, or when
2133 several months have passed on the -current branch).
2135 Sometimes, obscure build problems are the result of environment
2136 poisoning. This can happen because the make utility reads its
2137 environment when searching for values for global variables. To run
2138 your build attempts in an "environmental clean room", prefix all make
2139 commands with 'env -i '. See the env(1) manual page for more details.
2141 When upgrading from one major version to another it is generally best
2142 to upgrade to the latest code in the currently installed branch first,
2143 then do an upgrade to the new branch. This is the best-tested upgrade
2144 path, and has the highest probability of being successful. Please try
2145 this approach before reporting problems with a major version upgrade.
2147 When upgrading a live system, having a root shell around before
2148 installing anything can help undo problems. Not having a root shell
2149 around can lead to problems if pam has changed too much from your
2150 starting point to allow continued authentication after the upgrade.
2154 When upgrading the boot ZFS pool to a new version, always follow
2157 1.) recompile and reinstall the ZFS boot loader and boot block
2158 (this is part of "make buildworld" and "make installworld")
2160 2.) update the ZFS boot block on your boot drive
2162 The following example updates the ZFS boot block on the first
2163 partition (freebsd-boot) of a GPT partitioned drive ad0:
2164 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2166 Non-boot pools do not need these updates.
2170 If you are updating from a prior version of FreeBSD (even one just
2171 a few days old), you should follow this procedure. It is the most
2172 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2174 make kernel-toolchain
2175 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2176 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2178 To test a kernel once
2179 ---------------------
2180 If you just want to boot a kernel once (because you are not sure
2181 if it works, or if you want to boot a known bad kernel to provide
2182 debugging information) run
2183 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2184 nextboot -k testkernel
2186 To just build a kernel when you know that it won't mess you up
2187 --------------------------------------------------------------
2188 This assumes you are already running a CURRENT system. Replace
2189 ${arch} with the architecture of your machine (e.g. "i386",
2190 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2192 cd src/sys/${arch}/conf
2193 config KERNEL_NAME_HERE
2194 cd ../compile/KERNEL_NAME_HERE
2199 If this fails, go to the "To build a kernel" section.
2201 To rebuild everything and install it on the current system.
2202 -----------------------------------------------------------
2203 # Note: sometimes if you are running current you gotta do more than
2204 # is listed here if you are upgrading from a really old current.
2206 <make sure you have good level 0 dumps>
2208 make kernel KERNCONF=YOUR_KERNEL_HERE
2210 <reboot in single user> [3]
2217 To cross-install current onto a separate partition
2218 --------------------------------------------------
2219 # In this approach we use a separate partition to hold
2220 # current's root, 'usr', and 'var' directories. A partition
2221 # holding "/", "/usr" and "/var" should be about 2GB in
2224 <make sure you have good level 0 dumps>
2227 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2228 <maybe newfs current's root partition>
2229 <mount current's root partition on directory ${CURRENT_ROOT}>
2230 make installworld DESTDIR=${CURRENT_ROOT}
2231 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2232 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2233 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2234 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2235 <reboot into current>
2236 <do a "native" rebuild/install as described in the previous section>
2237 <maybe install compatibility libraries from ports/misc/compat*>
2241 To upgrade in-place from stable to current
2242 ----------------------------------------------
2243 <make sure you have good level 0 dumps>
2245 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2247 <reboot in single user> [3]
2254 Make sure that you've read the UPDATING file to understand the
2255 tweaks to various things you need. At this point in the life
2256 cycle of current, things change often and you are on your own
2257 to cope. The defaults can also change, so please read ALL of
2258 the UPDATING entries.
2260 Also, if you are tracking -current, you must be subscribed to
2261 freebsd-current@freebsd.org. Make sure that before you update
2262 your sources that you have read and understood all the recent
2263 messages there. If in doubt, please track -stable which has
2264 much fewer pitfalls.
2266 [1] If you have third party modules, such as vmware, you
2267 should disable them at this point so they don't crash your
2270 [3] From the bootblocks, boot -s, and then do
2275 adjkerntz -i # if CMOS is wall time
2276 Also, when doing a major release upgrade, it is required that
2277 you boot into single user mode to do the installworld.
2279 [4] Note: This step is non-optional. Failure to do this step
2280 can result in a significant reduction in the functionality of the
2281 system. Attempting to do it by hand is not recommended and those
2282 that pursue this avenue should read this file carefully, as well
2283 as the archives of freebsd-current and freebsd-hackers mailing lists
2284 for potential gotchas. The -U option is also useful to consider.
2285 See mergemaster(8) for more information.
2287 [5] Usually this step is a noop. However, from time to time
2288 you may need to do this if you get unknown user in the following
2289 step. It never hurts to do it all the time. You may need to
2290 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2291 install) after the buildworld before this step if you last updated
2292 from current before 20130425 or from -stable before 20130430.
2294 [6] This only deletes old files and directories. Old libraries
2295 can be deleted by "make delete-old-libs", but you have to make
2296 sure that no program is using those libraries anymore.
2298 [8] In order to have a kernel that can run the 4.x binaries needed to
2299 do an installworld, you must include the COMPAT_FREEBSD4 option in
2300 your kernel. Failure to do so may leave you with a system that is
2301 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2302 required to run the 5.x binaries on more recent kernels. And so on
2303 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2305 Make sure that you merge any new devices from GENERIC since the
2306 last time you updated your kernel config file.
2308 [9] When checking out sources, you must include the -P flag to have
2309 cvs prune empty directories.
2311 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2312 "?=" instead of the "=" assignment operator, so that buildworld can
2313 override the CPUTYPE if it needs to.
2315 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2316 not on the command line, or in /etc/make.conf. buildworld will
2317 warn if it is improperly defined.
2320 This file contains a list, in reverse chronological order, of major
2321 breakages in tracking -current. It is not guaranteed to be a complete
2322 list of such breakages, and only contains entries since October 10, 2007.
2323 If you need to see UPDATING entries from before that date, you will need
2324 to fetch an UPDATING file from an older FreeBSD release.
2326 Copyright information:
2328 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2330 Redistribution, publication, translation and use, with or without
2331 modification, in full or in part, in any form or format of this
2332 document are permitted without further permission from the author.
2334 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2335 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2336 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2337 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2338 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2339 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2340 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2341 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2342 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2343 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2344 POSSIBILITY OF SUCH DAMAGE.
2346 Contact Warner Losh if you have any questions about your use of