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 20160531 p4 FreeBSD-SA-16:20.linux
20 FreeBSD-SA-16:21.43bsd
21 FreeBSD-SA-16:22.libarchive
23 Fix kernel stack disclosure in Linux compatibility layer. [SA-16:20]
24 Fix kernel stack disclosure in 4.3BSD compatibility layer. [SA-16:21]
25 Fix directory traversal in cpio(1). [SA-16:22]
28 20160517 p3 FreeBSD-SA-16:18.atkbd
29 FreeBSD-SA-16:19.sendmsg
31 Fix buffer overflow in keyboard driver. [SA-16:18]
33 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
35 20160504 p2 FreeBSD-SA-16:17.openssl
40 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
42 Fix performance regression in libc hash(3). [EN-16:06]
44 Fix excessive latency in x86 IPI delivery. [EN-16:07]
46 Fix memory leak in ZFS. [EN-16:08]
48 20160429 p1 FreeBSD-SA-16:16.ntp
50 Fix multiple vulnerabilities of ntp.
56 The NONE and HPN patches has been removed from OpenSSH. They are
57 still available in the security/openssh-portable port.
60 r292223 changed the internal interface between the nfsd.ko and
61 nfscommon.ko modules. As such, they must both be upgraded to-gether.
62 __FreeBSD_version has been bumped because of this.
65 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
66 Kernel modules isp_2400_multi and isp_2500_multi were removed and
67 should be replaced with isp_2400 and isp_2500 modules respectively.
70 The menu.rc and loader.rc files will now be replaced during
71 upgrades. Please migrate local changes to menu.rc.local and
72 loader.rc.local instead.
75 NTP has been upgraded to 4.2.8p4.
78 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
79 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
80 and devel/kyua to version 0.20+ and adjust any calling code to work
81 with Kyuafile and kyua.
84 The polarity of Pulse Per Second (PPS) capture events with the
85 uart(4) driver has been corrected. Prior to this change the PPS
86 "assert" event corresponded to the trailing edge of a positive PPS
87 pulse and the "clear" event was the leading edge of the next pulse.
89 As the width of a PPS pulse in a typical GPS receiver is on the
90 order of 1 millisecond, most users will not notice any significant
91 difference with this change.
93 Anyone who has compensated for the historical polarity reversal by
94 configuring a negative offset equal to the pulse width will need to
95 remove that workaround.
98 From legacy ata(4) driver was removed support for SATA controllers
99 supported by more functional drivers ahci(4), siis(4) and mvs(4).
100 Kernel modules ataahci and ataadaptec were removed completely,
101 replaced by ahci and mvs modules respectively.
107 As ZFS requires more kernel stack pages than is the default on some
108 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
109 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
111 Please consider using 'options KSTACK_PAGES=X' where X is greater
112 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
115 The default Unbound configuration now enables remote control
116 using a local socket. Users who have already enabled the
117 local_unbound service should regenerate their configuration
118 by running "service local_unbound setup" as root.
121 An additional fix for the issue described in the 20150614 sendmail
122 entry below has been been committed in revision 284786.
125 The fix for the issue described in the 20150614 sendmail entry
126 below has been been committed in revision 284485. The work
127 around described in that entry is no longer needed unless the
128 default setting is overridden by a confDH_PARAMETERS configuration
129 setting of '5' or pointing to a 512 bit DH parameter file.
132 The import of openssl to address the FreeBSD-SA-15:10.openssl
133 security advisory includes a change which rejects handshakes
134 with DH parameters below 768 bits. sendmail releases prior
135 to 8.15.2 (not yet released), defaulted to a 512 bit
136 DH parameter setting for client connections. To work around
137 this interoperability, sendmail can be configured to use a
138 2048 bit DH parameter by:
140 1. Edit /etc/mail/`hostname`.mc
141 2. If a setting for confDH_PARAMETERS does not exist or
142 exists and is set to a string beginning with '5',
144 3. If a setting for confDH_PARAMETERS exists and is set to
145 a file path, create a new file with:
146 openssl dhparam -out /path/to/file 2048
147 4. Rebuild the .cf file:
148 cd /etc/mail/; make; make install
150 cd /etc/mail/; make restart
152 A sendmail patch is coming, at which time this file will be
156 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
157 defined in symlink(7); previously symlinks were silently ignored.
160 The const qualifier has been removed from iconv(3) to comply with
161 POSIX. The ports tree is aware of this from r384038 onwards.
164 At svn r275807, The default linux compat kernel ABI has been adjusted
165 to 2.6.18 in support of the linux-c6 compat ports infrastructure
166 update. If you wish to continue using the linux-f10 compat ports,
167 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
168 encouraged to update their linux-compat packages to linux-c6 during
169 their next update cycle.
171 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
174 pjdfstest has been integrated into kyua as an opt-in test suite.
175 Please see share/doc/pjdfstest/README for a more details on how to
182 The ofwfb driver, used to provide a graphics console on PowerPC when
183 using vt(4), no longer allows mmap() of all of physical memory. This
184 will prevent Xorg on PowerPC with some ATI graphics cards from
185 initializing properly unless x11-servers/xorg-server is updated to
189 The libatf-c and libatf-c++ major versions were downgraded to 0 and
190 1 respectively to match the upstream numbers. They were out of
191 sync because, when they were originally added to FreeBSD, the
192 upstream versions were not respected. These libraries are private
193 and not yet built by default, so renumbering them should be a
194 non-issue. However, unclean source trees will yield broken test
195 programs once the operator executes "make delete-old-libs" after a
198 Additionally, the atf-sh binary was made private by moving it into
199 /usr/libexec/. Already-built shell test programs will keep the
200 path to the old binary so they will break after "make delete-old"
203 If you are using WITH_TESTS=yes (not the default), wipe the object
204 tree and rebuild from scratch to prevent spurious test failures.
205 This is only needed once: the misnumbered libraries and misplaced
206 binaries have been added to OptionalObsoleteFiles.inc so they will
207 be removed during a clean upgrade.
210 The ixgbe tunables now match their sysctl counterparts, for example:
211 hw.ixgbe.enable_aim => hw.ix.enable_aim
212 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
215 The NFSv4.1 server committed by r269398 changes the internal
216 function call interfaces used between the NFS and krpc modules.
217 As such, __FreeBSD_version was bumped.
220 The default unbound configuration has been modified to address
221 issues with reverse lookups on networks that use private
222 address ranges. If you use the local_unbound service, run
223 "service local_unbound setup" as root to regenerate your
224 configuration, then "service local_unbound reload" to load the
228 It is no longer necessary to include the dwarf version in your DEBUG
229 options in your kernel config file. The bug that required it to be
230 placed in the config file has bene fixed. DEBUG should now just
231 contain -g. The build system will automatically update things
232 to do the right thing.
235 Several ABI breaking changes were merged to CTL and new iSCSI code.
236 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
237 iscsictl need to be rebuilt to work with a new kernel.
240 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
241 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
242 which differs from the behaviour controlled by this knob.)
245 On i386 and amd64 systems, the onifconsole flag is now set by default
246 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
247 as a login TTY if it is set in the bootloader as an active kernel
248 console. No changes in behavior should result otherwise. To revert to
249 the previous behavior, set ttyu0 to "off" in /etc/ttys.
252 Clang and llvm have been upgraded to 3.4.1 release.
255 Clang and llvm have been upgraded to 3.4 release.
258 If a Makefile in a tests/ directory was auto-generating a Kyuafile
259 instead of providing an explicit one, this would prevent such
260 Makefile from providing its own Kyuafile in the future during
261 NO_CLEAN builds. This has been fixed in the Makefiles but manual
262 intervention is needed to clean an objdir if you use NO_CLEAN:
263 # find /usr/obj -name Kyuafile | xargs rm -f
266 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
267 capability mode support. Please note that enabling the feature in
268 kernel is still highly recommended.
271 OpenSSH is now built with sandbox support, and will use sandbox as
272 the default privilege separation method. This requires Capsicum
273 capability mode support in kernel.
276 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
277 been deprecated and will not be part of FreeBSD 11.0 and later
278 releases. If you use this driver, please consider switching to
279 the nfe(4) driver instead.
285 The behavior of gss_pseudo_random() for the krb5 mechanism
286 has changed, for applications requesting a longer random string
287 than produced by the underlying enctype's pseudo-random() function.
288 In particular, the random string produced from a session key of
289 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
290 be different at the 17th octet and later, after this change.
291 The counter used in the PRF+ construction is now encoded as a
292 big-endian integer in accordance with RFC 4402.
293 __FreeBSD_version is bumped to 1000701.
296 The WITHOUT_ATF build knob has been removed and its functionality
297 has been subsumed into the more generic WITHOUT_TESTS. If you were
298 using the former to disable the build of the ATF libraries, you
299 should change your settings to use the latter.
302 The default version of mtree is nmtree which is obtained from
303 NetBSD. The output is generally the same, but may vary
304 slightly. If you found you need identical output adding
305 "-F freebsd9" to the command line should do the trick. For the
306 time being, the old mtree is available as fmtree.
309 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
310 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
311 1.1.4_8 and verify bsdyml not linked in, before running "make
313 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
315 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
318 The rc.d/jail script has been updated to support jail(8)
319 configuration file. The "jail_<jname>_*" rc.conf(5) variables
320 for per-jail configuration are automatically converted to
321 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
322 This is transparently backward compatible. See below about some
323 incompatibilities and rc.conf(5) manual page for more details.
325 These variables are now deprecated in favor of jail(8) configuration
326 file. One can use "rc.d/jail config <jname>" command to generate
327 a jail(8) configuration file in /var/run/jail.<jname>.conf without
328 running the jail(8) utility. The default pathname of the
329 configuration file is /etc/jail.conf and can be specified by
330 using $jail_conf or $jail_<jname>_conf variables.
332 Please note that jail_devfs_ruleset accepts an integer at
333 this moment. Please consider to rewrite the ruleset name
337 BIND has been removed from the base system. If all you need
338 is a local resolver, simply enable and start the local_unbound
339 service instead. Otherwise, several versions of BIND are
340 available in the ports tree. The dns/bind99 port is one example.
342 With this change, nslookup(1) and dig(1) are no longer in the base
343 system. Users should instead use host(1) and drill(1) which are
344 in the base system. Alternatively, nslookup and dig can
345 be obtained by installing the dns/bind-tools port.
348 With the addition of unbound(8), a new unbound user is now
349 required during installworld. "mergemaster -p" can be used to
350 add the user prior to installworld, as documented in the handbook.
353 OpenSSH is now built with DNSSEC support, and will by default
354 silently trust signed SSHFP records. This can be controlled with
355 the VerifyHostKeyDNS client configuration setting. DNSSEC support
356 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
359 The GNU Compiler Collection and C++ standard library (libstdc++)
360 are no longer built by default on platforms where clang is the system
361 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
365 The PROCDESC kernel option is now part of the GENERIC kernel
366 configuration and is required for the rwhod(8) to work.
367 If you are using custom kernel configuration, you should include
371 The API and ABI related to the Capsicum framework was modified
372 in backward incompatible way. The userland libraries and programs
373 have to be recompiled to work with the new kernel. This includes the
374 following libraries and programs, but the whole buildworld is
375 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
376 kdump, procstat, rwho, rwhod, uniq.
379 AES-NI intrinsic support has been added to gcc. The AES-NI module
380 has been updated to use this support. A new gcc is required to build
381 the aesni module on both i386 and amd64.
384 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
385 Thus "device padlock_rng" and "device rdrand_rng" should be
386 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
389 WITH_ICONV has been split into two feature sets. WITH_ICONV now
390 enables just the iconv* functionality and is now on by default.
391 WITH_LIBICONV_COMPAT enables the libiconv api and link time
392 compatability. Set WITHOUT_ICONV to build the old way.
393 If you have been using WITH_ICONV before, you will very likely
394 need to turn on WITH_LIBICONV_COMPAT.
397 INVARIANTS option now enables DEBUG for code with OpenSolaris and
398 Illumos origin, including ZFS. If you have INVARIANTS in your
399 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
401 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
402 locks if WITNESS option was set. Because that generated a lot of
403 witness(9) reports and all of them were believed to be false
404 positives, this is no longer done. New option OPENSOLARIS_WITNESS
405 can be used to achieve the previous behavior.
408 Timer values in IPv6 data structures now use time_uptime instead
409 of time_second. Although this is not a user-visible functional
410 change, userland utilities which directly use them---ndp(8),
411 rtadvd(8), and rtsold(8) in the base system---need to be updated
415 find -delete can now delete the pathnames given as arguments,
416 instead of only files found below them or if the pathname did
417 not contain any slashes. Formerly, the following error message
420 find: -delete: <path>: relative path potentially not safe
422 Deleting the pathnames given as arguments can be prevented
423 without error messages using -mindepth 1 or by changing
424 directory and passing "." as argument to find. This works in the
425 old as well as the new version of find.
428 Behavior of devfs rules path matching has been changed.
429 Pattern is now always matched against fully qualified devfs
430 path and slash characters must be explicitly matched by
431 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
432 subdirectories must be reviewed.
435 The default ARM ABI has changed to the ARM EABI. The old ABI is
436 incompatible with the ARM EABI and all programs and modules will
437 need to be rebuilt to work with a new kernel.
439 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
441 NOTE: Support for the old ABI will be removed in the future and
442 users are advised to upgrade.
445 pkg_install has been disconnected from the build if you really need it
446 you should add WITH_PKGTOOLS in your src.conf(5).
449 Most of network statistics structures were changed to be able
450 keep 64-bits counters. Thus all tools, that work with networking
451 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
454 Fix a bug that allowed a tracing process (e.g. gdb) to write
455 to a memory-mapped file in the traced process's address space
456 even if neither the traced process nor the tracing process had
457 write access to that file.
460 CVS has been removed from the base system. An exact copy
461 of the code is available from the devel/cvs port.
464 Some people report the following error after the switch to bmake:
466 make: illegal option -- J
467 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
469 *** [buildworld] Error code 2
471 this likely due to an old instance of make in
472 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
473 which src/Makefile will use that blindly, if it exists, so if
474 you see the above error:
476 rm -rf `make -V MAKEPATH`
481 Use bmake by default.
482 Whereas before one could choose to build with bmake via
483 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
484 make. The goal is to remove these knobs for 10-RELEASE.
486 It is worth noting that bmake (like gmake) treats the command
487 line as the unit of failure, rather than statements within the
488 command line. Thus '(cd some/where && dosomething)' is safer
489 than 'cd some/where; dosomething'. The '()' allows consistent
490 behavior in parallel build.
493 Fix a bug that allows NFS clients to issue READDIR on files.
496 The WITHOUT_IDEA option has been removed because
497 the IDEA patent expired.
500 The sysctl which controls TRIM support under ZFS has been renamed
501 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
505 The mergemaster command now uses the default MAKEOBJDIRPREFIX
506 rather than creating it's own in the temporary directory in
507 order allow access to bootstrapped versions of tools such as
508 install and mtree. When upgrading from version of FreeBSD where
509 the install command does not support -l, you will need to
510 install a new mergemaster command if mergemaster -p is required.
511 This can be accomplished with the command (cd src/usr.sbin/mergemaster
515 Legacy ATA stack, disabled and replaced by new CAM-based one since
516 FreeBSD 9.0, completely removed from the sources. Kernel modules
517 atadisk and atapi*, user-level tools atacontrol and burncd are
518 removed. Kernel option `options ATA_CAM` is now permanently enabled
522 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
523 and socketpair(2). Software, in particular Kerberos, may
524 automatically detect and use these during building. The resulting
525 binaries will not work on older kernels.
528 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
529 information, see the respective 20130304 entry).
532 Recent commits to callout(9) changed the size of struct callout,
533 so the KBI is probably heavily disturbed. Also, some functions
534 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
535 by macros. Every kernel module using it won't load, so rebuild
538 The ctl device has been re-enabled in GENERIC for i386 and amd64,
539 but does not initialize by default (because of the new CTL_DISABLE
540 option) to save memory. To re-enable it, remove the CTL_DISABLE
541 option from the kernel config file or set kern.cam.ctl.disable=0
542 in /boot/loader.conf.
545 The ctl device has been disabled in GENERIC for i386 and amd64.
546 This was done due to the extra memory being allocated at system
547 initialisation time by the ctl driver which was only used if
548 a CAM target device was created. This makes a FreeBSD system
549 unusable on 128MB or less of RAM.
552 A new compression method (lz4) has been merged to -HEAD. Please
553 refer to zpool-features(7) for more information.
555 Please refer to the "ZFS notes" section of this file for information
556 on upgrading boot ZFS pools.
559 A BSD-licensed patch(1) variant has been added and is installed
560 as bsdpatch, being the GNU version the default patch.
561 To inverse the logic and use the BSD-licensed one as default,
562 while having the GNU version installed as gnupatch, rebuild
563 and install world with the WITH_BSD_PATCH knob set.
566 Due to the use of the new -l option to install(1) during build
567 and install, you must take care not to directly set the INSTALL
568 make variable in your /etc/make.conf, /etc/src.conf, or on the
569 command line. If you wish to use the -C flag for all installs
570 you may be able to add INSTALL+=-C to /etc/make.conf or
574 The install(1) option -M has changed meaning and now takes an
575 argument that is a file or path to append logs to. In the
576 unlikely event that -M was the last option on the command line
577 and the command line contained at least two files and a target
578 directory the first file will have logs appended to it. The -M
579 option served little practical purpose in the last decade so its
580 use is expected to be extremely rare.
583 After switching to Clang as the default compiler some users of ZFS
584 on i386 systems started to experience stack overflow kernel panics.
585 Please consider using 'options KSTACK_PAGES=4' in such configurations.
588 GEOM_LABEL now mangles label names read from file system metadata.
589 Mangling affect labels containing spaces, non-printable characters,
590 '%' or '"'. Device names in /etc/fstab and other places may need to
594 By default, only the 10 most recent kernel dumps will be saved. To
595 restore the previous behaviour (no limit on the number of kernel dumps
596 stored in the dump directory) add the following line to /etc/rc.conf:
601 With the addition of auditdistd(8), a new auditdistd user is now
602 required during installworld. "mergemaster -p" can be used to
603 add the user prior to installworld, as documented in the handbook.
606 The sin6_scope_id member variable in struct sockaddr_in6 is now
607 filled by the kernel before passing the structure to the userland via
608 sysctl or routing socket. This means the KAME-specific embedded scope
609 id in sin6_addr.s6_addr[2] is always cleared in userland application.
610 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
611 __FreeBSD_version is bumped to 1000025.
614 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
615 This means that the world and kernel will be compiled with clang
616 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
617 and /usr/bin/cpp. To disable this behavior and revert to building
618 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
619 of current may need to bootstrap WITHOUT_CLANG first if the clang
620 build fails (its compatibility window doesn't extend to the 9 stable
624 The IPFIREWALL_FORWARD kernel option has been removed. Its
625 functionality now turned on by default.
628 The ZERO_COPY_SOCKET kernel option has been removed and
629 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
630 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
631 mechanism which is not safe and may result in kernel crashes.
632 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
633 driver supports disposeable external page sized mbuf storage.
634 Proper replacements for both zero-copy mechanisms are under
635 consideration and will eventually lead to complete removal
636 of the two kernel options.
639 The IPv4 network stack has been converted to network byte
640 order. The following modules need to be recompiled together
641 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
642 pf(4), ipfw(4), ng_ipfw(4), stf(4).
645 Support for non-MPSAFE filesystems was removed from VFS. The
646 VFS_VERSION was bumped, all filesystem modules shall be
650 All the non-MPSAFE filesystems have been disconnected from
651 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
652 portalfs, smbfs, xfs.
655 The interface cloning API and ABI has changed. The following
656 modules need to be recompiled together with kernel:
657 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
658 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
659 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
662 The sdhci driver was split in two parts: sdhci (generic SD Host
663 Controller logic) and sdhci_pci (actual hardware driver).
664 No kernel config modifications are required, but if you
665 load sdhc as a module you must switch to sdhci_pci instead.
668 Import the FUSE kernel and userland support into base system.
671 The GNU sort(1) program has been removed since the BSD-licensed
672 sort(1) has been the default for quite some time and no serious
673 problems have been reported. The corresponding WITH_GNU_SORT
677 The pfil(9) API/ABI for AF_INET family has been changed. Packet
678 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
682 The net80211(4) ABI has been changed to allow for improved driver
683 PS-POLL and power-save support. All wireless drivers need to be
684 recompiled to work with the new kernel.
687 The random(4) support for the VIA hardware random number
688 generator (`PADLOCK') is no longer enabled unconditionally.
689 Add the padlock_rng device in the custom kernel config if
690 needed. The GENERIC kernels on i386 and amd64 do include the
691 device, so the change only affects the custom kernel
695 The pf(4) packet filter ABI has been changed. pfctl(8) and
696 snmp_pf module need to be recompiled to work with new kernel.
699 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
700 to -HEAD. Pools that have empty_bpobj in active state can not be
701 imported read-write with ZFS implementations that do not support
702 this feature. For more information read the zpool-features(5)
706 The sparc64 ZFS loader has been changed to no longer try to auto-
707 detect ZFS providers based on diskN aliases but now requires these
708 to be explicitly listed in the OFW boot-device environment variable.
711 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
712 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
713 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
716 The following sysctls and tunables have been renamed for consistency
717 with other variables:
718 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
719 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
722 The sort utility has been replaced with BSD sort. For now, GNU sort
723 is also available as "gnusort" or the default can be set back to
724 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
725 installed as "bsdsort".
728 A new version of ZFS (pool version 5000) has been merged to -HEAD.
729 Starting with this version the old system of ZFS pool versioning
730 is superseded by "feature flags". This concept enables forward
731 compatibility against certain future changes in functionality of ZFS
732 pools. The first read-only compatible "feature flag" for ZFS pools
733 is named "com.delphix:async_destroy". For more information
734 read the new zpool-features(5) manual page.
735 Please refer to the "ZFS notes" section of this file for information
736 on upgrading boot ZFS pools.
739 The malloc(3) implementation embedded in libc now uses sources imported
740 as contrib/jemalloc. The most disruptive API change is to
741 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
742 delete it prior to installworld, and optionally re-create it using the
743 new format after rebooting. See malloc.conf(5) for details
744 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
748 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
749 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
750 now spelled mips. This is to aid compatibility with third-party
751 software that expects this naming scheme in uname(3). Little-endian
752 settings are unchanged. If you are updating a big-endian mips64 machine
753 from before this change, you may need to set MACHINE_ARCH=mips64 in
754 your environment before the new build system will recognize your machine.
757 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
761 Now unix domain sockets behave "as expected" on nullfs(5). Previously
762 nullfs(5) did not pass through all behaviours to the underlying layer,
763 as a result if we bound to a socket on the lower layer we could connect
764 only to the lower path; if we bound to the upper layer we could connect
765 only to the upper path. The new behavior is one can connect to both the
766 lower and the upper paths regardless what layer path one binds to.
769 The getifaddrs upgrade path broken with 20111215 has been restored.
770 If you have upgraded in between 20111215 and 20120209 you need to
771 recompile libc again with your kernel. You still need to recompile
772 world to be able to configure CARP but this restriction already
776 The set_rcvar() function has been removed from /etc/rc.subr. All
777 base and ports rc.d scripts have been updated, so if you have a
778 port installed with a script in /usr/local/etc/rc.d you can either
779 hand-edit the rcvar= line, or reinstall the port.
781 An easy way to handle the mass-update of /etc/rc.d:
782 rm /etc/rc.d/* && mergemaster -i
785 panic(9) now stops other CPUs in the SMP systems, disables interrupts
786 on the current CPU and prevents other threads from running.
787 This behavior can be reverted using the kern.stop_scheduler_on_panic
789 The new behavior can be incompatible with kern.sync_on_panic.
792 The carp(4) facility has been changed significantly. Configuration
793 of the CARP protocol via ifconfig(8) has changed, as well as format
794 of CARP events submitted to devd(8) has changed. See manual pages
795 for more information. The arpbalance feature of carp(4) is currently
796 not supported anymore.
798 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
799 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
800 need to be recompiled.
803 The acpi_wmi(4) status device /dev/wmistat has been renamed to
807 The option VFS_ALLOW_NONMPSAFE option has been added in order to
808 explicitely support non-MPSAFE filesystems.
809 It is on by default for all supported platform at this present
813 The broken amd(4) driver has been replaced with esp(4) in the amd64,
814 i386 and pc98 GENERIC kernel configuration files.
817 sysinstall has been removed
820 The stable/9 branch created in subversion. This corresponds to the
821 RELENG_9 branch in CVS.
824 This commit modifies vfs_register() so that it uses a hash
825 calculation to set vfc_typenum, which is enabled by default.
826 The first time a system is booted after this change, the
827 vfc_typenum values will change for all file systems. The
828 main effect of this is a change to the NFS server file handles
829 for file systems that use vfc_typenum in their fsid, such as ZFS.
830 It will, however, prevent vfc_typenum from changing when file
831 systems are loaded in a different order for subsequent reboots.
832 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
833 until you are ready to remount all NFS clients after a reboot.
836 Bump the shared library version numbers for libraries that
837 do not use symbol versioning, have changed the ABI compared
838 to stable/8 and which shared library version was not bumped.
839 Done as part of 9.0-RELEASE cycle.
842 During the merge of Capsicum features, the fget(9) KPI was modified.
843 This may require the rebuilding of out-of-tree device drivers --
844 issues have been reported specifically with the nVidia device driver.
845 __FreeBSD_version is bumped to 900041.
847 Also, there is a period between 20110811 and 20110814 where the
848 special devices /dev/{stdin,stdout,stderr} did not work correctly.
849 Building world from a kernel during that window may not work.
852 The packet filter (pf) code has been updated to OpenBSD 4.5.
853 You need to update userland tools to be in sync with kernel.
854 This update breaks backward compatibility with earlier pfsync(4)
855 versions. Care must be taken when updating redundant firewall setups.
858 The following sysctls and tunables are retired on x86 platforms:
860 machdep.hlt_logical_cpus
861 The following sysctl is retired:
862 machdep.hyperthreading_allowed
863 The sysctls were supposed to provide a way to dynamically offline and
864 online selected CPUs on x86 platforms, but the implementation has not
865 been reliable especially with SCHED_ULE scheduler.
866 machdep.hyperthreading_allowed tunable is still available to ignore
867 hyperthreading CPUs at OS level.
868 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
869 where X is an APIC ID of a CPU. Be advised, though, that disabling
870 CPUs in non-uniform fashion will result in non-uniform topology and
871 may lead to sub-optimal system performance with SCHED_ULE, which is
875 cpumask_t type is retired and cpuset_t is used in order to describe
879 Changes to ifconfig(8) for dynamic address family detection mandate
880 that you are running a kernel of 20110525 or later. Make sure to
881 follow the update procedure to boot a new kernel before installing
885 Support for sun4v architecture is officially dropped
888 Several KPI breaking changes have been committed to the mii(4) layer,
889 the PHY drivers and consequently some Ethernet drivers using mii(4).
890 This means that miibus.ko and the modules of the affected Ethernet
891 drivers need to be recompiled.
893 Note to kernel developers: Given that the OUI bit reversion problem
894 was fixed as part of these changes all mii(4) commits related to OUIs,
895 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
896 handling, no longer can be merged verbatim to stable/8 and previous
900 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
901 into their kernel configurations along with 'device pci'.
904 The default NFS client is now the new NFS client, so fstype "newnfs"
905 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
906 Although mounts via fstype "nfs" will usually work without userland
907 changes, it is recommended that the mount(8) and mount_nfs(8)
908 commands be rebuilt from sources and that a link to mount_nfs called
909 mount_oldnfs be created. The new client is compiled into the
910 kernel with "options NFSCL" and this is needed for diskless root
911 file systems. The GENERIC kernel configs have been changed to use
912 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
913 To use the regular/old client, you can "mount -t oldnfs ...". For
914 a diskless root file system, you must also include a line like:
916 vfs.root.mountfrom="oldnfs:"
918 in the boot/loader.conf on the root fs on the NFS server to make
919 a diskless root fs use the old client.
922 The GENERIC kernels for all architectures now default to the new
923 CAM-based ATA stack. It means that all legacy ATA drivers were
924 removed and replaced by respective CAM drivers. If you are using
925 ATA device names in /etc/fstab or other places, make sure to update
926 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
927 where 'Y's are the sequential numbers starting from zero for each type
928 in order of detection, unless configured otherwise with tunables,
929 see cam(4)). There will be symbolic links created in /dev/ to map
930 old adX devices to the respective adaY. They should provide basic
931 compatibility for file systems mounting in most cases, but they do
932 not support old user-level APIs and do not have respective providers
933 in GEOM. Consider using updated management tools with new device names.
935 It is possible to load devices ahci, ata, siis and mvs as modules,
936 but option ATA_CAM should remain in kernel configuration to make ata
937 module work as CAM driver supporting legacy ATA controllers. Device ata
938 still can be used in modular fashion (atacore + ...). Modules atadisk
939 and atapi* are not used and won't affect operation in ATA_CAM mode.
940 Note that to use CAM-based ATA kernel should include CAM devices
941 scbus, pass, da (or explicitly ada), cd and optionally others. All of
942 them are parts of the cam module.
944 ataraid(4) functionality is now supported by the RAID GEOM class.
945 To use it you can load geom_raid kernel module and use graid(8) tool
946 for management. Instead of /dev/arX device names, use /dev/raid/rX.
948 No kernel config options or code have been removed, so if a problem
949 arises, please report it and optionally revert to the old ATA stack.
950 In order to do it you can remove from the kernel config:
955 , and instead add back:
956 device atadisk # ATA disk drives
957 device ataraid # ATA RAID drives
958 device atapicd # ATAPI CDROM drives
959 device atapifd # ATAPI floppy drives
960 device atapist # ATAPI tape drives
963 The default NFS server has been changed to the new server, which
964 was referred to as the experimental server. If you need to switch
965 back to the old NFS server, you must now put the "-o" option on
966 both the mountd and nfsd commands. This can be done using the
967 mountd_flags and nfs_server_flags rc.conf variables until an
968 update to the rc scripts is committed, which is coming soon.
971 The GNU Objective-C runtime library (libobjc), and other Objective-C
972 related components have been removed from the base system. If you
973 require an Objective-C library, please use one of the available ports.
976 ath(4) has been split into bus- and device- modules. if_ath contains
977 the HAL, the TX rate control and the network device code. if_ath_pci
978 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
979 contains the AHB glue. Users need to load both if_ath_pci and if_ath
980 in order to use ath on everything else.
982 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
983 need to load if_ath and if_ath_pci for ath(4) operation.
986 As part of the replacement of sysinstall, the process of building
987 release media has changed significantly. For details, please re-read
988 release(7), which has been updated to reflect the new build process.
991 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
992 is the last available version under GPLv2. It brings a number of new
993 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
994 4.1 and SSE 4.2), better support for powerpc64, a number of new
995 directives, and lots of other small improvements. See the ChangeLog
996 file in contrib/binutils for the full details.
999 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1000 compliant, and will now use half of hash for authentication.
1001 This will break interoperability with all stacks (including all
1002 actual FreeBSD versions) who implement
1003 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1005 The only workaround with such peers is to use another HMAC
1006 algorithm for IPsec ("phase 2") authentication.
1009 Remove the uio_yield prototype and symbol. This function has
1010 been misnamed since it was introduced and should not be
1011 globally exposed with this name. The equivalent functionality
1012 is now available using kern_yield(curthread->td_user_pri).
1013 The function remains undocumented.
1016 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1017 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1018 for scalar sysctls is defined but disabled. Code that needs
1019 UQUAD to pass the type checking that must compile on older
1020 systems where the define is not present can check against
1021 __FreeBSD_version >= 900030.
1023 The system dialog(1) has been replaced with a new version previously
1024 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1025 with the previous version, but the libdialog associated with it has
1026 a largely incompatible API. As such, the original version of libdialog
1027 will be kept temporarily as libodialog, until its base system consumers
1028 are replaced or updated. Bump __FreeBSD_version to 900030.
1031 If you are trying to run make universe on a -stable system, and you get
1032 the following warning:
1033 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1034 unknown. config(8) likely too old."
1035 or something similar to it, then you must upgrade your -stable system
1036 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1037 stable/8) or build the config from the latest stable/8 branch and
1038 install it on your system.
1040 Prior to this date, building a current universe on 8-stable system from
1041 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1042 error in the first kernel build phase. A new config on those old
1043 systems will fix that problem for older versions of -current.
1046 The TCP stack has been modified to allow Khelp modules to interact with
1047 it via helper hook points and store per-connection data in the TCP
1048 control block. Bump __FreeBSD_version to 900029. User space tools that
1049 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1053 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1054 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1055 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1056 to take advantage of it instead of using custom implementations. This
1057 means that these drivers now no longer unconditionally advertise
1058 support for flow control but only do so if flow control is a selected
1059 media option. This was implemented in the generic support that way in
1060 order to allow flow control to be switched on and off via ifconfig(8)
1061 with the PHY specific default to typically off in order to protect
1062 from unwanted effects. Consequently, if you used flow control with
1063 one of the above mentioned drivers you now need to explicitly enable
1064 it, for example via:
1065 ifconfig bge0 media auto mediaopt flowcontrol
1067 Along with the above mentioned changes generic support for setting
1068 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1069 e1000phy(4) as well as ip1000phy(4) have been converted to take
1070 advantage of it. This means that these drivers now no longer take the
1071 link0 parameter for selecting master mode but the master media option
1072 has to be used instead, for example like in the following:
1073 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1075 Selection of master mode now is also available with all other PHY
1076 drivers supporting 1000baseT.
1079 The TCP stack has received a significant update to add support for
1080 modularised congestion control and generally improve the clarity of
1081 congestion control decisions. Bump __FreeBSD_version to 900025. User
1082 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1083 sockstat) need to be recompiled.
1086 The man(1) utility has been replaced by a new version that no longer
1087 uses /etc/manpath.config. Please consult man.conf(5) for how to
1088 migrate local entries to the new format.
1091 The copyright strings printed by login(1) and sshd(8) at the time of a
1092 new connection have been removed to follow other operating systems and
1096 A workaround for a fixed ld bug has been removed in kernel code,
1097 so make sure that your system ld is built from sources after
1098 revision 210245 from 2010-07-19 (r211583 if building head kernel
1099 on stable/8, r211584 for stable/7; both from 2010-08-21).
1100 A symptom of incorrect ld version is different addresses for
1101 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1104 The $ipv6_prefer variable in rc.conf(5) has been split into
1105 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1107 The $ip6addrctl_policy is a variable to choose a pre-defined
1108 address selection policy set by ip6addrctl(8). A value
1109 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1112 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1113 flag (see an entry of 20090926) is set on an interface with no
1114 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1115 security reason. If you want IPv6 link-local address on all
1116 interfaces by default, set this to "YES".
1118 The old ipv6_prefer="YES" is equivalent to
1119 ipv6_activate_all_interfaces="YES" and
1120 ip6addrctl_policy="ipv6_prefer".
1123 DTrace has grown support for userland tracing. Due to this, DTrace is
1124 now i386 and amd64 only.
1125 dtruss(1) is now installed by default on those systems and a new
1126 kernel module is needed for userland tracing: fasttrap.
1127 No changes to your kernel config file are necessary to enable
1128 userland tracing, but you might consider adding 'STRIP=' and
1129 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1130 to have informative userland stack traces in DTrace (ustack).
1133 The acpi_aiboost(4) driver has been removed in favor of the new
1134 aibs(4) driver. You should update your kernel configuration file.
1137 BSD grep has been imported to the base system and it is built by
1138 default. It is completely BSD licensed, highly GNU-compatible, uses
1139 less memory than its GNU counterpart and has a small codebase.
1140 However, it is slower than its GNU counterpart, which is mostly
1141 noticeable for larger searches, for smaller ones it is measurable
1142 but not significant. The reason is complex, the most important factor
1143 is that we lack a modern and efficient regex library and GNU
1144 overcomes this by optimizing the searches internally. Future work
1145 on improving the regex performance is planned, for the meantime,
1146 users that need better performance, can build GNU grep instead by
1147 setting the WITH_GNU_GREP knob.
1150 Due to the import of powerpc64 support, all existing powerpc kernel
1151 configuration files must be updated with a machine directive like this:
1152 machine powerpc powerpc
1154 In addition, an updated config(8) is required to build powerpc kernels
1158 A new version of ZFS (version 15) has been merged to -HEAD.
1159 This version uses a python library for the following subcommands:
1160 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1161 For full functionality of these commands the following port must
1162 be installed: sysutils/py-zfs
1165 'vm_page's are now hashed by physical address to an array of mutexes.
1166 Currently this is only used to serialize access to hold_count. Over
1167 time the page queue mutex will be peeled away. This changes the size
1168 of pmap on every architecture. And requires all callers of vm_page_hold
1169 and vm_page_unhold to be updated.
1172 WITH_CTF can now be specified in src.conf (not recommended, there
1173 are some problems with static executables), make.conf (would also
1174 affect ports which do not use GNU make and do not override the
1175 compile targets) or in the kernel config (via "makeoptions
1177 When WITH_CTF was specified there before this was silently ignored,
1178 so make sure that WITH_CTF is not used in places which could lead
1179 to unwanted behavior.
1182 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1183 to allow 32-bit compatibility on non-x86 platforms. All kernel
1184 configurations on amd64 and ia64 platforms using these options must
1185 be modified accordingly.
1188 The utmp user accounting database has been replaced with utmpx,
1189 the user accounting interface standardized by POSIX.
1190 Unfortunately the semantics of utmp and utmpx don't match,
1191 making it practically impossible to support both interfaces.
1192 The user accounting database is used by tools like finger(1),
1193 last(1), talk(1), w(1) and ac(8).
1195 All applications in the base system use utmpx. This means only
1196 local binaries (e.g. from the ports tree) may still use these
1197 utmp database files. These applications must be rebuilt to make
1200 After the system has been upgraded, it is safe to remove the old
1201 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1202 assuming their contents is of no importance anymore. Old wtmp
1203 databases can only be used by last(1) and ac(8) after they have
1204 been converted to the new format using wtmpcvt(1).
1207 Introduce the kernel thread "deadlock resolver" (which can be enabled
1208 via the DEADLKRES option, see NOTES for more details) and the
1209 sleepq_type() function for sleepqueues.
1212 The rc.firewall and rc.firewall6 were unified, and
1213 rc.firewall6 and rc.d/ip6fw were removed.
1214 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1215 variables are obsoleted. Instead, the following new rc
1216 variables are added to rc.d/ipfw:
1218 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1219 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1220 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1222 The meanings correspond to the relevant IPv4 variables.
1228 The default terminal emulation for syscons(4) has been changed
1229 from cons25 to xterm on all platforms except pc98. This means
1230 that the /etc/ttys file needs to be updated to ensure correct
1231 operation of applications on the console.
1233 The terminal emulation style can be toggled per window by using
1234 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1235 options can be used to change the compile-time default back to
1238 To prevent graphical artifacts, make sure the TERM environment
1239 variable is set to match the terminal emulation that is being
1240 performed by syscons(4).
1243 The layout of the structure ieee80211req_scan_result has changed.
1244 Applications that require wireless scan results (e.g. ifconfig(8))
1245 from net80211 need to be recompiled.
1247 Applications such as wpa_supplicant(8) may require a full world
1248 build without using NO_CLEAN in order to get synchronized with the
1252 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1253 There's one kernel module for each firmware. Adding "device iwnfw"
1254 to the kernel configuration file means including all three firmware
1255 images inside the kernel. If you want to include just the one for
1256 your wireless card, use the devices iwn4965fw, iwn5000fw or
1260 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1261 into rc.d/netif. The changes are the following:
1263 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1264 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1265 Note that both variables need the "inet6" keyword at the head.
1267 Do not set $ipv6_network_interfaces manually if you do not
1268 understand what you are doing. It is not needed in most cases.
1270 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1273 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1274 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1276 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1277 all configured interfaces have "inet6 accept_rtadv" in the
1278 $ifconfig_IF_ipv6. These are for backward compatibility.
1280 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1281 functionality of interfaces with no corresponding
1282 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1283 and the default address selection policy of ip6addrctl(8)
1284 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1285 Note that if you want to configure IPv6 functionality on the
1286 disabled interfaces after boot, first you need to clear the flag by
1287 using ifconfig(8) like:
1289 ifconfig em0 inet6 -ifdisabled
1291 If YES, the default address selection policy is set as
1294 The default value of $ipv6_prefer is NO.
1296 4. If your system need to receive Router Advertisement messages,
1297 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1298 scripts automatically invoke rtsol(8) when the interface becomes
1299 UP. The Router Advertisement messages are used for SLAAC
1300 (State-Less Address AutoConfiguration).
1303 802.11s D3.03 support was committed. This is incompatible with the
1304 previous code, which was based on D3.0.
1307 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1308 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1309 control whether accepting Router Advertisement messages or not.
1310 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1311 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1312 The ifconfig(8) utility now supports these flags.
1315 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1316 mount(8) and -a option for df(1) to see them.
1319 The old tunable hw.bus.devctl_disable has been superseded by
1320 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1321 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1325 Remove the option STOP_NMI. The default action is now to use NMI only
1326 for KDB via the newly introduced function stop_cpus_hard() and
1327 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1330 The stable/8 branch created in subversion. This corresponds to the
1331 RELENG_8 branch in CVS.
1334 Bump the shared library version numbers for all libraries that do not
1335 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1336 __FreeBSD_version to 800105.
1339 Due to changes in the implementation of virtual network stack support,
1340 all network-related kernel modules must be recompiled. As this change
1341 breaks the ABI, bump __FreeBSD_version to 800104.
1344 The TOE interface to the TCP syncache has been modified to remove
1345 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1346 The cxgb driver is the only TOE consumer affected by this change, and
1347 needs to be recompiled along with the kernel. As this change breaks
1348 the ABI, bump __FreeBSD_version to 800103.
1351 Padding has been added to struct tcpcb, sackhint and tcpstat in
1352 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1353 maintaining the ABI. However, this change breaks the ABI, so bump
1354 __FreeBSD_version to 800102. User space tools that rely on the size of
1355 any of these structs (e.g. sockstat) need to be recompiled.
1358 The NFS_LEGACYRPC option has been removed along with the old kernel
1359 RPC implementation that this option selected. Kernel configurations
1360 may need to be adjusted.
1363 The network interface device nodes at /dev/net/<interface> have been
1364 removed. All ioctl operations can be performed the normal way using
1365 routing sockets. The kqueue functionality can generally be replaced
1366 with routing sockets.
1369 The documentation from the FreeBSD Documentation Project (Handbook,
1370 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1371 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1374 The ABI of various structures related to the SYSV IPC API have been
1375 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1376 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1380 Layout of struct vnet has changed as routing related variables were
1381 moved to their own Vimage module. Modules need to be recompiled. Bump
1382 __FreeBSD_version to 800099.
1385 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1386 respectively. As long as no more than 16 groups per process are used,
1387 no changes should be visible. When more than 16 groups are used, old
1388 binaries may fail if they call getgroups() or getgrouplist() with
1389 statically sized storage. Recompiling will work around this, but
1390 applications should be modified to use dynamically allocated storage
1391 for group arrays as POSIX.1-2008 does not cap an implementation's
1392 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1394 NFS and portalfs mounts may also be affected as the list of groups is
1395 truncated to 16. Users of NFS who use more than 16 groups, should
1396 take care that negative group permissions are not used on the exported
1397 file systems as they will not be reliable unless a GSSAPI based
1398 authentication method is used.
1401 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1402 option compiles in the support for adaptive spinning for lockmgrs
1403 which want to enable it. The lockinit() function now accepts the flag
1404 LK_ADAPTIVE in order to make the lock object subject to adaptive
1405 spinning when both held in write and read mode.
1408 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1409 changed. User applications that use this ioctl need to be rebuilt.
1412 The layout of struct thread has changed. Kernel and modules need to
1416 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1417 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1420 window(1) has been removed from the base system. It can now be
1421 installed from ports. The port is called misc/window.
1424 The way we are storing and accessing `routing table' entries has
1425 changed. Programs reading the FIB, like netstat, need to be
1429 A new netisr implementation has been added for FreeBSD 8. Network
1430 file system modules, such as igmp, ipdivert, and others, should be
1432 Bump __FreeBSD_version to 800096.
1435 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1439 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1440 Bump __FreeBSD_version to 800094.
1443 Add mnt_xflag field to 'struct mount'. File system modules need to be
1445 Bump __FreeBSD_version to 800093.
1448 The compiling option ADAPTIVE_SX has been retired while it has been
1449 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1450 The KPI for sx_init_flags() changes as accepting flags:
1451 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1452 been introduced in order to handle the reversed logic.
1453 Bump __FreeBSD_version to 800092.
1456 Add support for hierarchical jails. Remove global securelevel.
1457 Bump __FreeBSD_version to 800091.
1460 The layout of struct vnet_net has changed, therefore modules
1462 Bump __FreeBSD_version to 800090.
1465 The newly imported zic(8) produces a new format in the output. Please
1466 run tzsetup(8) to install the newly created data to /etc/localtime.
1469 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1470 hw.usb.* and is now consistent again with previous releases.
1473 802.11 monitor mode support was revised and driver api's were changed.
1474 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1475 of DLT_IEEE802_11. No user-visible data structures were changed but
1476 applications that use DLT_IEEE802_11 may require changes.
1477 Bump __FreeBSD_version to 800088.
1480 The layout of the following structs has changed: sysctl_oid,
1481 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1482 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1483 panics may be experienced. World rebuild is required for
1484 correctly checking networking state from userland.
1485 Bump __FreeBSD_version to 800085.
1488 MLDv2 and Source-Specific Multicast (SSM) have been merged
1489 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1490 The implementation of SSM within FreeBSD's IPv6 stack closely
1491 follows the IPv4 implementation.
1493 For kernel developers:
1495 * The most important changes are that the ip6_output() and
1496 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1497 and this lock has been downgraded to a non-recursive mutex.
1499 * As with the changes to the IPv4 stack to support SSM, filtering
1500 of inbound multicast traffic must now be performed by transport
1501 protocols within the IPv6 stack. This does not apply to TCP and
1502 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1504 * The KPIs used by IPv6 multicast are similar to those used by
1505 the IPv4 stack, with the following differences:
1506 * im6o_mc_filter() is analogous to imo_multicast_filter().
1507 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1508 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1509 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1510 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1511 for MLDv1 have an additional 'timer' argument which is used to
1512 jitter the initial membership report for the solicited-node
1513 multicast membership on-link.
1514 * This is not strictly needed for MLDv2, which already jitters
1515 its report transmissions. However, the 'timer' argument is
1516 preserved in case MLDv1 is active on the interface.
1518 * The KAME linked-list based IPv6 membership implementation has
1519 been refactored to use a vector similar to that used by the IPv4
1521 Code which maintains a list of its own multicast memberships
1522 internally, e.g. carp, has been updated to reflect the new
1525 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1526 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1527 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1528 implementation constraint which needs to be addressed in HEAD.
1530 For application developers:
1532 * The changes are broadly similar to those made for the IPv4
1535 * The use of IPv4 and IPv6 multicast socket options on the same
1536 socket, using mapped addresses, HAS NOT been tested or supported.
1538 * There are a number of issues with the implementation of various
1539 IPv6 multicast APIs which need to be resolved in the API surface
1540 before the implementation is fully compatible with KAME userland
1541 use, and these are mostly to do with interface index treatment.
1543 * The literature available discusses the use of either the delta / ASM
1544 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1545 using setsourcefilter(3)/getsourcefilter(3). For more information
1546 please refer to RFC 3768, 'Socket Interface Extensions for
1547 Multicast Source Filters'.
1549 * Applications which use the published RFC 3678 APIs should be fine.
1551 For systems administrators:
1553 * The mtest(8) utility has been refactored to support IPv6, in
1554 addition to IPv4. Interface addresses are no longer accepted
1555 as arguments, their names must be used instead. The utility
1556 will map the interface name to its first IPv4 address as
1557 returned by getifaddrs(3).
1559 * The ifmcstat(8) utility has also been updated to print the MLDv2
1560 endpoint state and source filter lists via sysctl(3).
1562 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1563 loopback of IPv6 multicast datagrams by default; it defaults to 1
1564 to preserve the existing behaviour. Disabling multicast loopback is
1565 recommended for optimal system performance.
1567 * The IPv6 MROUTING code has been changed to examine this sysctl
1568 instead of attempting to perform a group lookup before looping
1569 back forwarded datagrams.
1571 Bump __FreeBSD_version to 800084.
1574 Implement low-level Bluetooth HCI API.
1575 Bump __FreeBSD_version to 800083.
1578 The layout of struct malloc_type, used by modules to register new
1579 memory allocation types, has changed. Most modules will need to
1580 be rebuilt or panics may be experienced.
1581 Bump __FreeBSD_version to 800081.
1584 Anticipate overflowing inp_flags - add inp_flags2.
1585 This changes most offsets in inpcb, so checking v4 connection
1586 state will require a world rebuild.
1587 Bump __FreeBSD_version to 800080.
1590 Add an llentry to struct route and struct route_in6. Modules
1591 embedding a struct route will need to be recompiled.
1592 Bump __FreeBSD_version to 800079.
1595 The size of rt_metrics_lite and by extension rtentry has changed.
1596 Networking administration apps will need to be recompiled.
1597 The route command now supports show as an alias for get, weighting
1598 of routes, sticky and nostick flags to alter the behavior of stateful
1600 Bump __FreeBSD_version to 800078.
1603 Do not use Giant for kbdmux(4) locking. This is wrong and
1604 apparently causing more problems than it solves. This will
1605 re-open the issue where interrupt handlers may race with
1606 kbdmux(4) in polling mode. Typical symptoms include (but
1607 not limited to) duplicated and/or missing characters when
1608 low level console functions (such as gets) are used while
1609 interrupts are enabled (for example geli password prompt,
1610 mountroot prompt etc.). Disabling kbdmux(4) may help.
1613 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1614 kernel modules referencing any of the above need to be recompiled.
1615 Bump __FreeBSD_version to 800075.
1618 GEOM_PART has become the default partition slicer for storage devices,
1619 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1620 introduces some changes:
1622 MSDOS/EBR: the devices created from MSDOS extended partition entries
1623 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1624 to devices with offset-based names. fstabs may need to be modified.
1626 BSD: the "geometry does not match label" warning is harmless in most
1627 cases but it points to problems in file system misalignment with
1628 disk geometry. The "c" partition is now implicit, covers the whole
1629 top-level drive and cannot be (mis)used by users.
1631 General: Kernel dumps are now not allowed to be written to devices
1632 whose partition types indicate they are meant to be used for file
1633 systems (or, in case of MSDOS partitions, as something else than
1636 Most of these changes date approximately from 200812.
1639 The uscanner(4) driver has been removed from the kernel. This follows
1640 Linux removing theirs in 2.6 and making libusb the default interface
1641 (supported by sane).
1644 The multicast forwarding code has been cleaned up. netstat(1)
1645 only relies on KVM now for printing bandwidth upcall meters.
1646 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1647 ip6_mroute_mod respectively. The config(5) options for statically
1648 compiling this code remain the same, i.e. 'options MROUTING'.
1651 Support for the IFF_NEEDSGIANT network interface flag has been
1652 removed, which means that non-MPSAFE network device drivers are no
1653 longer supported. In particular, if_ar, if_sr, and network device
1654 drivers from the old (legacy) USB stack can no longer be built or
1658 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1659 a bunch of new language catalog files have also been added.
1660 This means that some common libc messages are now localized and
1661 they depend on the LC_MESSAGES environmental variable.
1664 The k8temp(4) driver has been renamed to amdtemp(4) since
1665 support for Family 10 and Family 11 CPU families was added.
1668 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1669 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1671 For kernel developers, the most important changes are that the
1672 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1673 and this lock has been downgraded to a non-recursive mutex.
1675 Transport protocols (UDP, Raw IP) are now responsible for filtering
1676 inbound multicast traffic according to group membership and source
1677 filters. The imo_multicast_filter() KPI exists for this purpose.
1678 Transports which do not use multicast (SCTP, TCP) already reject
1679 multicast by default. Forwarding and receive performance may improve
1680 as a mutex acquisition is no longer needed in the ip_input()
1681 low-level input path. in_addmulti() and in_delmulti() are shimmed
1682 to new KPIs which exist to support SSM in-kernel.
1684 For application developers, it is recommended that loopback of
1685 multicast datagrams be disabled for best performance, as this
1686 will still cause the lock to be taken for each looped-back
1687 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1688 be tuned to 0 to disable loopback by default; it defaults to 1
1689 to preserve the existing behaviour.
1691 For systems administrators, to obtain best performance with
1692 multicast reception and multiple groups, it is always recommended
1693 that a card with a suitably precise hash filter is used. Hash
1694 collisions will still result in the lock being taken within the
1695 transport protocol input path to check group membership.
1697 If deploying FreeBSD in an environment with IGMP snooping switches,
1698 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1699 enabled; this forces 224.0.0.0/24 group membership to be announced
1702 The size of 'struct igmpstat' has changed; netstat needs to be
1703 recompiled to reflect this.
1704 Bump __FreeBSD_version to 800070.
1707 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1708 updated to use it. This requires a buildworld/installworld in order to
1709 update the library and dependencies (usbconfig, etc). Its advisable to
1710 rebuild all ports which uses libusb. More specific directions are given
1711 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1712 libusb are no longer required and can be removed.
1715 A workaround is committed to allow the creation of System V shared
1716 memory segment of size > 2 GB on the 64-bit architectures.
1717 Due to a limitation of the existing ABI, the shm_segsz member
1718 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1719 wrong for large segments. Note that limits must be explicitly
1720 raised to allow such segments to be created.
1723 The layout of struct ifnet has changed, requiring a rebuild of all
1724 network device driver modules.
1727 The /dev handling for the new USB stack has changed, a
1728 buildworld/installworld is required for libusb20.
1731 The new USB2 stack has now been permanently moved in and all kernel and
1732 module names reverted to their previous values (eg, usb, ehci, ohci,
1733 ums, ...). The old usb stack can be compiled in by prefixing the name
1734 with the letter 'o', the old usb modules have been removed.
1735 Updating entry 20090216 for xorg and 20090215 for libmap may still
1739 The rc.conf(5) option if_up_delay has been renamed to
1740 defaultroute_delay to better reflect its purpose. If you have
1741 customized this setting in /etc/rc.conf you need to update it to
1745 xorg 7.4 wants to configure its input devices via hald which does not
1746 yet work with USB2. If the keyboard/mouse does not work in xorg then
1748 Option "AllowEmptyInput" "off"
1749 to your ServerLayout section. This will cause X to use the configured
1750 kbd and mouse sections from your xorg.conf.
1753 The GENERIC kernels for all architectures now default to the new USB2
1754 stack. No kernel config options or code have been removed so if a
1755 problem arises please report it and optionally revert to the old USB
1756 stack. If you are loading USB kernel modules or have a custom kernel
1757 that includes GENERIC then ensure that usb names are also changed over,
1758 eg uftdi -> usb2_serial_ftdi.
1760 Older programs linked against the ports libusb 0.1 need to be
1761 redirected to the new stack's libusb20. /etc/libmap.conf can
1763 # Map old usb library to new one for usb2 stack
1764 libusb-0.1.so.8 libusb20.so.1
1767 All USB ethernet devices now attach as interfaces under the name ueN
1768 (eg. ue0). This is to provide a predictable name as vendors often
1769 change usb chipsets in a product without notice.
1772 The ichsmb(4) driver has been changed to require SMBus slave
1773 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1774 All of the other SMBus controller drivers require left-justified
1775 slave addresses, so this change makes all the drivers provide the
1779 INET6 statistics (struct ip6stat) was updated.
1780 netstat(1) needs to be recompiled.
1783 NTFS has been removed from GENERIC kernel on amd64 to match
1784 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1785 will load ntfs.ko module automatically when NTFS support is
1786 actually needed, unless ntfs.ko is not installed or security
1787 level prohibits loading kernel modules. If either is the case,
1788 "options NTFS" has to be added into kernel config.
1791 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1792 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1793 800061. User space tools that rely on the size of struct tcpcb in
1794 tcp_var.h (e.g. sockstat) need to be recompiled.
1797 ng_tty(4) module updated to match the new TTY subsystem.
1798 Due to API change, user-level applications must be updated.
1799 New API support added to mpd5 CVS and expected to be present
1800 in next mpd5.3 release.
1803 With __FreeBSD_version 800060 the makefs tool is part of
1804 the base system (it was a port).
1807 The afdata and ifnet locks have been changed from mutexes to
1808 rwlocks, network modules will need to be re-compiled.
1811 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1812 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1813 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1814 architecture and 40 bytes on 64-bit architecture. The userland
1815 applications "arp" and "ndp" have been updated accordingly.
1816 The output from "netstat -r" shows only routing entries and
1817 none of the L2 information.
1820 __FreeBSD_version 800057 marks the switchover from the
1821 binary ath hal to source code. Users must add the line:
1823 options AH_SUPPORT_AR5416
1825 to their kernel config files when specifying:
1829 The ath_hal module no longer exists; the code is now compiled
1830 together with the driver in the ath module. It is now
1831 possible to tailor chip support (i.e. reduce the set of chips
1832 and thereby the code size); consult ath_hal(4) for details.
1835 __FreeBSD_version 800054 adds memory barriers to
1836 <machine/atomic.h>, new interfaces to ifnet to facilitate
1837 multiple hardware transmit queues for cards that support
1838 them, and a lock-less ring-buffer implementation to
1839 enable drivers to more efficiently manage queueing of
1843 A new version of ZFS (version 13) has been merged to -HEAD.
1844 This version has zpool attribute "listsnapshots" off by
1845 default, which means "zfs list" does not show snapshots,
1846 and is the same as Solaris behavior.
1849 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1852 The uhci, ohci, ehci and slhci USB Host controller drivers have
1853 been put into separate modules. If you load the usb module
1854 separately through loader.conf you will need to load the
1855 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1856 controller add the following to loader.conf:
1862 The ABI used by the PMC toolset has changed. Please keep
1863 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1867 atapci kernel module now includes only generic PCI ATA
1868 driver. AHCI driver moved to ataahci kernel module.
1869 All vendor-specific code moved into separate kernel modules:
1870 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1871 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1872 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1873 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1876 The TTY subsystem of the kernel has been replaced by a new
1877 implementation, which provides better scalability and an
1878 improved driver model. Most common drivers have been migrated to
1879 the new TTY subsystem, while others have not. The following
1880 drivers have not yet been ported to the new TTY layer:
1883 cy, digi, rc, rp, sio
1889 ng_h4, ng_tty, ppp, sl, snp
1891 Adding these drivers to your kernel configuration file shall
1892 cause compilation to fail.
1895 ntpd has been upgraded to 4.2.4p5.
1898 OpenSSH has been upgraded to 5.1p1.
1900 For many years, FreeBSD's version of OpenSSH preferred DSA
1901 over RSA for host and user authentication keys. With this
1902 upgrade, we've switched to the vendor's default of RSA over
1903 DSA. This may cause upgraded clients to warn about unknown
1904 host keys even for previously known hosts. Users should
1905 follow the usual procedure for verifying host keys before
1906 accepting the RSA key.
1908 This can be circumvented by setting the "HostKeyAlgorithms"
1909 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1912 Please note that the sequence of keys offered for
1913 authentication has been changed as well. You may want to
1914 specify IdentityFile in a different order to revert this
1918 The sio(4) driver has been removed from the i386 and amd64
1919 kernel configuration files. This means uart(4) is now the
1920 default serial port driver on those platforms as well.
1922 To prevent collisions with the sio(4) driver, the uart(4) driver
1923 uses different names for its device nodes. This means the
1924 onboard serial port will now most likely be called "ttyu0"
1925 instead of "ttyd0". You may need to reconfigure applications to
1926 use the new device names.
1928 When using the serial port as a boot console, be sure to update
1929 /boot/device.hints and /etc/ttys before booting the new kernel.
1930 If you forget to do so, you can still manually specify the hints
1931 at the loader prompt:
1933 set hint.uart.0.at="isa"
1934 set hint.uart.0.port="0x3F8"
1935 set hint.uart.0.flags="0x10"
1936 set hint.uart.0.irq="4"
1940 The gpt(8) utility has been removed. Use gpart(8) to partition
1944 The version that Linuxulator emulates was changed from 2.4.2
1945 to 2.6.16. If you experience any problems with Linux binaries
1946 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1947 if it fixes the problem contact emulation mailing list.
1950 ISDN4BSD (I4B) was removed from the src tree. You may need to
1951 update a your kernel configuration and remove relevant entries.
1954 I have checked in code to support multiple routing tables.
1955 See the man pages setfib(1) and setfib(2).
1956 This is a hopefully backwards compatible version,
1957 but to make use of it you need to compile your kernel
1958 with options ROUTETABLES=2 (or more up to 16).
1961 The 802.11 wireless support was redone to enable multi-bss
1962 operation on devices that are capable. The underlying device
1963 is no longer used directly but instead wlanX devices are
1964 cloned with ifconfig. This requires changes to rc.conf files.
1965 For example, change:
1966 ifconfig_ath0="WPA DHCP"
1969 ifconfig_wlan0="WPA DHCP"
1970 see rc.conf(5) for more details. In addition, mergemaster of
1971 /etc/rc.d is highly recommended. Simultaneous update of userland
1972 and kernel wouldn't hurt either.
1974 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1975 modules were merged into the base wlan module. All references
1976 to these modules (e.g. in kernel config files) must be removed.
1979 psm(4) has gained write(2) support in native operation level.
1980 Arbitrary commands can be written to /dev/psm%d and status can
1981 be read back from it. Therefore, an application is responsible
1982 for status validation and error recovery. It is a no-op in
1983 other operation levels.
1986 Support for KSE threading has been removed from the kernel. To
1987 run legacy applications linked against KSE libmap.conf may
1988 be used. The following libmap.conf may be used to ensure
1989 compatibility with any prior release:
1991 libpthread.so.1 libthr.so.1
1992 libpthread.so.2 libthr.so.2
1993 libkse.so.3 libthr.so.3
1996 The layout of struct vmspace has changed. This affects libkvm
1997 and any executables that link against libkvm and use the
1998 kvm_getprocs() function. In particular, but not exclusively,
1999 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2000 The effects are minimal, but it's advisable to upgrade world
2004 The latest em driver no longer has support in it for the
2005 82575 adapter, this is now moved to the igb driver. The
2006 split was done to make new features that are incompatible
2007 with older hardware easier to do.
2010 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2011 likewise the kernel option is now GEOM_LINUX_LVM.
2014 The default NFS mount mode has changed from UDP to TCP for
2015 increased reliability. If you rely on (insecurely) NFS
2016 mounting across a firewall you may need to update your
2020 Belatedly note the addition of m_collapse for compacting
2024 The fts(3) structures have been changed to use adequate
2025 integer types for their members and so to be able to cope
2026 with huge file trees. The old fts(3) ABI is preserved
2027 through symbol versioning in libc, so third-party binaries
2028 using fts(3) should still work, although they will not take
2029 advantage of the extended types. At the same time, some
2030 third-party software might fail to build after this change
2031 due to unportable assumptions made in its source code about
2032 fts(3) structure members. Such software should be fixed
2033 by its vendor or, in the worst case, in the ports tree.
2034 FreeBSD_version 800015 marks this change for the unlikely
2035 case that a portable fix is impossible.
2038 To upgrade to -current after this date, you must be running
2039 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2040 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2043 The ADAPTIVE_GIANT kernel option has been retired because its
2044 functionality is the default now.
2047 The AT keyboard emulation of sunkbd(4) has been turned on
2048 by default. In order to make the special symbols of the Sun
2049 keyboards driven by sunkbd(4) work under X these now have
2050 to be configured the same way as Sun USB keyboards driven
2051 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2053 Option "XkbLayout" "us"
2054 Option "XkbRules" "xorg"
2055 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2058 It has been decided that it is desirable to provide ABI
2059 backwards compatibility to the FreeBSD 4/5/6 versions of the
2060 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2061 broken with the introduction of PCI domain support (see the
2062 20070930 entry). Unfortunately, this required the ABI of
2063 PCIOCGETCONF to be broken again in order to be able to
2064 provide backwards compatibility to the old version of that
2065 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2066 again. As for prominent ports this affects neither pciutils
2067 nor xorg-server this time, the hal port needs to be rebuilt
2071 The misnamed kthread_create() and friends have been renamed
2072 to kproc_create() etc. Many of the callers already
2073 used kproc_start()..
2074 I will return kthread_create() and friends in a while
2075 with implementations that actually create threads, not procs.
2076 Renaming corresponds with version 800002.
2085 Avoid using make -j when upgrading. While generally safe, there are
2086 sometimes problems using -j to upgrade. If your upgrade fails with
2087 -j, please try again without -j. From time to time in the past there
2088 have been problems using -j with buildworld and/or installworld. This
2089 is especially true when upgrading between "distant" versions (eg one
2090 that cross a major release boundary or several minor releases, or when
2091 several months have passed on the -current branch).
2093 Sometimes, obscure build problems are the result of environment
2094 poisoning. This can happen because the make utility reads its
2095 environment when searching for values for global variables. To run
2096 your build attempts in an "environmental clean room", prefix all make
2097 commands with 'env -i '. See the env(1) manual page for more details.
2099 When upgrading from one major version to another it is generally best
2100 to upgrade to the latest code in the currently installed branch first,
2101 then do an upgrade to the new branch. This is the best-tested upgrade
2102 path, and has the highest probability of being successful. Please try
2103 this approach before reporting problems with a major version upgrade.
2105 When upgrading a live system, having a root shell around before
2106 installing anything can help undo problems. Not having a root shell
2107 around can lead to problems if pam has changed too much from your
2108 starting point to allow continued authentication after the upgrade.
2112 When upgrading the boot ZFS pool to a new version, always follow
2115 1.) recompile and reinstall the ZFS boot loader and boot block
2116 (this is part of "make buildworld" and "make installworld")
2118 2.) update the ZFS boot block on your boot drive
2120 The following example updates the ZFS boot block on the first
2121 partition (freebsd-boot) of a GPT partitioned drive ad0:
2122 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2124 Non-boot pools do not need these updates.
2128 If you are updating from a prior version of FreeBSD (even one just
2129 a few days old), you should follow this procedure. It is the most
2130 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2132 make kernel-toolchain
2133 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2134 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2136 To test a kernel once
2137 ---------------------
2138 If you just want to boot a kernel once (because you are not sure
2139 if it works, or if you want to boot a known bad kernel to provide
2140 debugging information) run
2141 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2142 nextboot -k testkernel
2144 To just build a kernel when you know that it won't mess you up
2145 --------------------------------------------------------------
2146 This assumes you are already running a CURRENT system. Replace
2147 ${arch} with the architecture of your machine (e.g. "i386",
2148 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2150 cd src/sys/${arch}/conf
2151 config KERNEL_NAME_HERE
2152 cd ../compile/KERNEL_NAME_HERE
2157 If this fails, go to the "To build a kernel" section.
2159 To rebuild everything and install it on the current system.
2160 -----------------------------------------------------------
2161 # Note: sometimes if you are running current you gotta do more than
2162 # is listed here if you are upgrading from a really old current.
2164 <make sure you have good level 0 dumps>
2166 make kernel KERNCONF=YOUR_KERNEL_HERE
2168 <reboot in single user> [3]
2175 To cross-install current onto a separate partition
2176 --------------------------------------------------
2177 # In this approach we use a separate partition to hold
2178 # current's root, 'usr', and 'var' directories. A partition
2179 # holding "/", "/usr" and "/var" should be about 2GB in
2182 <make sure you have good level 0 dumps>
2185 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2186 <maybe newfs current's root partition>
2187 <mount current's root partition on directory ${CURRENT_ROOT}>
2188 make installworld DESTDIR=${CURRENT_ROOT}
2189 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2190 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2191 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2192 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2193 <reboot into current>
2194 <do a "native" rebuild/install as described in the previous section>
2195 <maybe install compatibility libraries from ports/misc/compat*>
2199 To upgrade in-place from stable to current
2200 ----------------------------------------------
2201 <make sure you have good level 0 dumps>
2203 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2205 <reboot in single user> [3]
2212 Make sure that you've read the UPDATING file to understand the
2213 tweaks to various things you need. At this point in the life
2214 cycle of current, things change often and you are on your own
2215 to cope. The defaults can also change, so please read ALL of
2216 the UPDATING entries.
2218 Also, if you are tracking -current, you must be subscribed to
2219 freebsd-current@freebsd.org. Make sure that before you update
2220 your sources that you have read and understood all the recent
2221 messages there. If in doubt, please track -stable which has
2222 much fewer pitfalls.
2224 [1] If you have third party modules, such as vmware, you
2225 should disable them at this point so they don't crash your
2228 [3] From the bootblocks, boot -s, and then do
2233 adjkerntz -i # if CMOS is wall time
2234 Also, when doing a major release upgrade, it is required that
2235 you boot into single user mode to do the installworld.
2237 [4] Note: This step is non-optional. Failure to do this step
2238 can result in a significant reduction in the functionality of the
2239 system. Attempting to do it by hand is not recommended and those
2240 that pursue this avenue should read this file carefully, as well
2241 as the archives of freebsd-current and freebsd-hackers mailing lists
2242 for potential gotchas. The -U option is also useful to consider.
2243 See mergemaster(8) for more information.
2245 [5] Usually this step is a noop. However, from time to time
2246 you may need to do this if you get unknown user in the following
2247 step. It never hurts to do it all the time. You may need to
2248 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2249 install) after the buildworld before this step if you last updated
2250 from current before 20130425 or from -stable before 20130430.
2252 [6] This only deletes old files and directories. Old libraries
2253 can be deleted by "make delete-old-libs", but you have to make
2254 sure that no program is using those libraries anymore.
2256 [8] In order to have a kernel that can run the 4.x binaries needed to
2257 do an installworld, you must include the COMPAT_FREEBSD4 option in
2258 your kernel. Failure to do so may leave you with a system that is
2259 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2260 required to run the 5.x binaries on more recent kernels. And so on
2261 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2263 Make sure that you merge any new devices from GENERIC since the
2264 last time you updated your kernel config file.
2266 [9] When checking out sources, you must include the -P flag to have
2267 cvs prune empty directories.
2269 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2270 "?=" instead of the "=" assignment operator, so that buildworld can
2271 override the CPUTYPE if it needs to.
2273 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2274 not on the command line, or in /etc/make.conf. buildworld will
2275 warn if it is improperly defined.
2278 This file contains a list, in reverse chronological order, of major
2279 breakages in tracking -current. It is not guaranteed to be a complete
2280 list of such breakages, and only contains entries since October 10, 2007.
2281 If you need to see UPDATING entries from before that date, you will need
2282 to fetch an UPDATING file from an older FreeBSD release.
2284 Copyright information:
2286 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2288 Redistribution, publication, translation and use, with or without
2289 modification, in full or in part, in any form or format of this
2290 document are permitted without further permission from the author.
2292 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2293 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2294 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2295 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2296 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2297 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2298 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2299 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2300 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2301 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2302 POSSIBILITY OF SUCH DAMAGE.
2304 Contact Warner Losh if you have any questions about your use of