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.
20 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
21 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
22 same source (previously, the dependency of mmcsd.ko on mmc.ko was
23 missing, but mmcsd.ko now will refuse to load if it is incompatible
27 As of r316810 for ipfilter, keep frags is no longer assumed when
28 keep state is specified in a rule. r316810 aligns ipfilter with
29 documentation in man pages separating keep frags from keep state.
30 This allows keep state to specified without forcing keep frags
31 and allows keep frags to be specified independently of keep state.
32 To maintain previous behaviour, also specify keep frags with
33 keep state (as documented in ipf.conf.5).
36 The code that provides support for ZFS .zfs/ directory functionality
37 has been reimplemented. It's not possible now to create a snapshot
38 by mkdir under .zfs/snapshot/. That should be the only user visible
42 The NONE and HPN patches has been removed from OpenSSH. They are
43 still available in the security/openssh-portable port.
46 r292223 changed the internal interface between the nfsd.ko and
47 nfscommon.ko modules. As such, they must both be upgraded to-gether.
48 __FreeBSD_version has been bumped because of this.
51 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
52 Kernel modules isp_2400_multi and isp_2500_multi were removed and
53 should be replaced with isp_2400 and isp_2500 modules respectively.
56 The menu.rc and loader.rc files will now be replaced during
57 upgrades. Please migrate local changes to menu.rc.local and
58 loader.rc.local instead.
61 NTP has been upgraded to 4.2.8p4.
64 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
65 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
66 and devel/kyua to version 0.20+ and adjust any calling code to work
67 with Kyuafile and kyua.
70 The polarity of Pulse Per Second (PPS) capture events with the
71 uart(4) driver has been corrected. Prior to this change the PPS
72 "assert" event corresponded to the trailing edge of a positive PPS
73 pulse and the "clear" event was the leading edge of the next pulse.
75 As the width of a PPS pulse in a typical GPS receiver is on the
76 order of 1 millisecond, most users will not notice any significant
77 difference with this change.
79 Anyone who has compensated for the historical polarity reversal by
80 configuring a negative offset equal to the pulse width will need to
81 remove that workaround.
84 From legacy ata(4) driver was removed support for SATA controllers
85 supported by more functional drivers ahci(4), siis(4) and mvs(4).
86 Kernel modules ataahci and ataadaptec were removed completely,
87 replaced by ahci and mvs modules respectively.
93 As ZFS requires more kernel stack pages than is the default on some
94 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
95 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
97 Please consider using 'options KSTACK_PAGES=X' where X is greater
98 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
101 The default Unbound configuration now enables remote control
102 using a local socket. Users who have already enabled the
103 local_unbound service should regenerate their configuration
104 by running "service local_unbound setup" as root.
107 An additional fix for the issue described in the 20150614 sendmail
108 entry below has been been committed in revision 284786.
111 The fix for the issue described in the 20150614 sendmail entry
112 below has been been committed in revision 284485. The work
113 around described in that entry is no longer needed unless the
114 default setting is overridden by a confDH_PARAMETERS configuration
115 setting of '5' or pointing to a 512 bit DH parameter file.
118 The import of openssl to address the FreeBSD-SA-15:10.openssl
119 security advisory includes a change which rejects handshakes
120 with DH parameters below 768 bits. sendmail releases prior
121 to 8.15.2 (not yet released), defaulted to a 512 bit
122 DH parameter setting for client connections. To work around
123 this interoperability, sendmail can be configured to use a
124 2048 bit DH parameter by:
126 1. Edit /etc/mail/`hostname`.mc
127 2. If a setting for confDH_PARAMETERS does not exist or
128 exists and is set to a string beginning with '5',
130 3. If a setting for confDH_PARAMETERS exists and is set to
131 a file path, create a new file with:
132 openssl dhparam -out /path/to/file 2048
133 4. Rebuild the .cf file:
134 cd /etc/mail/; make; make install
136 cd /etc/mail/; make restart
138 A sendmail patch is coming, at which time this file will be
142 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
143 defined in symlink(7); previously symlinks were silently ignored.
146 The const qualifier has been removed from iconv(3) to comply with
147 POSIX. The ports tree is aware of this from r384038 onwards.
150 At svn r275807, The default linux compat kernel ABI has been adjusted
151 to 2.6.18 in support of the linux-c6 compat ports infrastructure
152 update. If you wish to continue using the linux-f10 compat ports,
153 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
154 encouraged to update their linux-compat packages to linux-c6 during
155 their next update cycle.
157 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
160 pjdfstest has been integrated into kyua as an opt-in test suite.
161 Please see share/doc/pjdfstest/README for a more details on how to
168 The ofwfb driver, used to provide a graphics console on PowerPC when
169 using vt(4), no longer allows mmap() of all of physical memory. This
170 will prevent Xorg on PowerPC with some ATI graphics cards from
171 initializing properly unless x11-servers/xorg-server is updated to
175 The libatf-c and libatf-c++ major versions were downgraded to 0 and
176 1 respectively to match the upstream numbers. They were out of
177 sync because, when they were originally added to FreeBSD, the
178 upstream versions were not respected. These libraries are private
179 and not yet built by default, so renumbering them should be a
180 non-issue. However, unclean source trees will yield broken test
181 programs once the operator executes "make delete-old-libs" after a
184 Additionally, the atf-sh binary was made private by moving it into
185 /usr/libexec/. Already-built shell test programs will keep the
186 path to the old binary so they will break after "make delete-old"
189 If you are using WITH_TESTS=yes (not the default), wipe the object
190 tree and rebuild from scratch to prevent spurious test failures.
191 This is only needed once: the misnumbered libraries and misplaced
192 binaries have been added to OptionalObsoleteFiles.inc so they will
193 be removed during a clean upgrade.
196 The ixgbe tunables now match their sysctl counterparts, for example:
197 hw.ixgbe.enable_aim => hw.ix.enable_aim
198 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
201 The NFSv4.1 server committed by r269398 changes the internal
202 function call interfaces used between the NFS and krpc modules.
203 As such, __FreeBSD_version was bumped.
206 The default unbound configuration has been modified to address
207 issues with reverse lookups on networks that use private
208 address ranges. If you use the local_unbound service, run
209 "service local_unbound setup" as root to regenerate your
210 configuration, then "service local_unbound reload" to load the
214 It is no longer necessary to include the dwarf version in your DEBUG
215 options in your kernel config file. The bug that required it to be
216 placed in the config file has bene fixed. DEBUG should now just
217 contain -g. The build system will automatically update things
218 to do the right thing.
221 Several ABI breaking changes were merged to CTL and new iSCSI code.
222 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
223 iscsictl need to be rebuilt to work with a new kernel.
226 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
227 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
228 which differs from the behaviour controlled by this knob.)
231 On i386 and amd64 systems, the onifconsole flag is now set by default
232 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
233 as a login TTY if it is set in the bootloader as an active kernel
234 console. No changes in behavior should result otherwise. To revert to
235 the previous behavior, set ttyu0 to "off" in /etc/ttys.
238 Clang and llvm have been upgraded to 3.4.1 release.
241 Clang and llvm have been upgraded to 3.4 release.
244 If a Makefile in a tests/ directory was auto-generating a Kyuafile
245 instead of providing an explicit one, this would prevent such
246 Makefile from providing its own Kyuafile in the future during
247 NO_CLEAN builds. This has been fixed in the Makefiles but manual
248 intervention is needed to clean an objdir if you use NO_CLEAN:
249 # find /usr/obj -name Kyuafile | xargs rm -f
252 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
253 capability mode support. Please note that enabling the feature in
254 kernel is still highly recommended.
257 OpenSSH is now built with sandbox support, and will use sandbox as
258 the default privilege separation method. This requires Capsicum
259 capability mode support in kernel.
262 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
263 been deprecated and will not be part of FreeBSD 11.0 and later
264 releases. If you use this driver, please consider switching to
265 the nfe(4) driver instead.
271 The behavior of gss_pseudo_random() for the krb5 mechanism
272 has changed, for applications requesting a longer random string
273 than produced by the underlying enctype's pseudo-random() function.
274 In particular, the random string produced from a session key of
275 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
276 be different at the 17th octet and later, after this change.
277 The counter used in the PRF+ construction is now encoded as a
278 big-endian integer in accordance with RFC 4402.
279 __FreeBSD_version is bumped to 1000701.
282 The WITHOUT_ATF build knob has been removed and its functionality
283 has been subsumed into the more generic WITHOUT_TESTS. If you were
284 using the former to disable the build of the ATF libraries, you
285 should change your settings to use the latter.
288 The default version of mtree is nmtree which is obtained from
289 NetBSD. The output is generally the same, but may vary
290 slightly. If you found you need identical output adding
291 "-F freebsd9" to the command line should do the trick. For the
292 time being, the old mtree is available as fmtree.
295 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
296 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
297 1.1.4_8 and verify bsdyml not linked in, before running "make
299 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
301 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
304 The rc.d/jail script has been updated to support jail(8)
305 configuration file. The "jail_<jname>_*" rc.conf(5) variables
306 for per-jail configuration are automatically converted to
307 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
308 This is transparently backward compatible. See below about some
309 incompatibilities and rc.conf(5) manual page for more details.
311 These variables are now deprecated in favor of jail(8) configuration
312 file. One can use "rc.d/jail config <jname>" command to generate
313 a jail(8) configuration file in /var/run/jail.<jname>.conf without
314 running the jail(8) utility. The default pathname of the
315 configuration file is /etc/jail.conf and can be specified by
316 using $jail_conf or $jail_<jname>_conf variables.
318 Please note that jail_devfs_ruleset accepts an integer at
319 this moment. Please consider to rewrite the ruleset name
323 BIND has been removed from the base system. If all you need
324 is a local resolver, simply enable and start the local_unbound
325 service instead. Otherwise, several versions of BIND are
326 available in the ports tree. The dns/bind99 port is one example.
328 With this change, nslookup(1) and dig(1) are no longer in the base
329 system. Users should instead use host(1) and drill(1) which are
330 in the base system. Alternatively, nslookup and dig can
331 be obtained by installing the dns/bind-tools port.
334 With the addition of unbound(8), a new unbound user is now
335 required during installworld. "mergemaster -p" can be used to
336 add the user prior to installworld, as documented in the handbook.
339 OpenSSH is now built with DNSSEC support, and will by default
340 silently trust signed SSHFP records. This can be controlled with
341 the VerifyHostKeyDNS client configuration setting. DNSSEC support
342 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
345 The GNU Compiler Collection and C++ standard library (libstdc++)
346 are no longer built by default on platforms where clang is the system
347 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
351 The PROCDESC kernel option is now part of the GENERIC kernel
352 configuration and is required for the rwhod(8) to work.
353 If you are using custom kernel configuration, you should include
357 The API and ABI related to the Capsicum framework was modified
358 in backward incompatible way. The userland libraries and programs
359 have to be recompiled to work with the new kernel. This includes the
360 following libraries and programs, but the whole buildworld is
361 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
362 kdump, procstat, rwho, rwhod, uniq.
365 AES-NI intrinsic support has been added to gcc. The AES-NI module
366 has been updated to use this support. A new gcc is required to build
367 the aesni module on both i386 and amd64.
370 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
371 Thus "device padlock_rng" and "device rdrand_rng" should be
372 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
375 WITH_ICONV has been split into two feature sets. WITH_ICONV now
376 enables just the iconv* functionality and is now on by default.
377 WITH_LIBICONV_COMPAT enables the libiconv api and link time
378 compatability. Set WITHOUT_ICONV to build the old way.
379 If you have been using WITH_ICONV before, you will very likely
380 need to turn on WITH_LIBICONV_COMPAT.
383 INVARIANTS option now enables DEBUG for code with OpenSolaris and
384 Illumos origin, including ZFS. If you have INVARIANTS in your
385 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
387 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
388 locks if WITNESS option was set. Because that generated a lot of
389 witness(9) reports and all of them were believed to be false
390 positives, this is no longer done. New option OPENSOLARIS_WITNESS
391 can be used to achieve the previous behavior.
394 Timer values in IPv6 data structures now use time_uptime instead
395 of time_second. Although this is not a user-visible functional
396 change, userland utilities which directly use them---ndp(8),
397 rtadvd(8), and rtsold(8) in the base system---need to be updated
401 find -delete can now delete the pathnames given as arguments,
402 instead of only files found below them or if the pathname did
403 not contain any slashes. Formerly, the following error message
406 find: -delete: <path>: relative path potentially not safe
408 Deleting the pathnames given as arguments can be prevented
409 without error messages using -mindepth 1 or by changing
410 directory and passing "." as argument to find. This works in the
411 old as well as the new version of find.
414 Behavior of devfs rules path matching has been changed.
415 Pattern is now always matched against fully qualified devfs
416 path and slash characters must be explicitly matched by
417 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
418 subdirectories must be reviewed.
421 The default ARM ABI has changed to the ARM EABI. The old ABI is
422 incompatible with the ARM EABI and all programs and modules will
423 need to be rebuilt to work with a new kernel.
425 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
427 NOTE: Support for the old ABI will be removed in the future and
428 users are advised to upgrade.
431 pkg_install has been disconnected from the build if you really need it
432 you should add WITH_PKGTOOLS in your src.conf(5).
435 Most of network statistics structures were changed to be able
436 keep 64-bits counters. Thus all tools, that work with networking
437 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
440 Fix a bug that allowed a tracing process (e.g. gdb) to write
441 to a memory-mapped file in the traced process's address space
442 even if neither the traced process nor the tracing process had
443 write access to that file.
446 CVS has been removed from the base system. An exact copy
447 of the code is available from the devel/cvs port.
450 Some people report the following error after the switch to bmake:
452 make: illegal option -- J
453 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
455 *** [buildworld] Error code 2
457 this likely due to an old instance of make in
458 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
459 which src/Makefile will use that blindly, if it exists, so if
460 you see the above error:
462 rm -rf `make -V MAKEPATH`
467 Use bmake by default.
468 Whereas before one could choose to build with bmake via
469 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
470 make. The goal is to remove these knobs for 10-RELEASE.
472 It is worth noting that bmake (like gmake) treats the command
473 line as the unit of failure, rather than statements within the
474 command line. Thus '(cd some/where && dosomething)' is safer
475 than 'cd some/where; dosomething'. The '()' allows consistent
476 behavior in parallel build.
479 Fix a bug that allows NFS clients to issue READDIR on files.
482 The WITHOUT_IDEA option has been removed because
483 the IDEA patent expired.
486 The sysctl which controls TRIM support under ZFS has been renamed
487 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
491 The mergemaster command now uses the default MAKEOBJDIRPREFIX
492 rather than creating it's own in the temporary directory in
493 order allow access to bootstrapped versions of tools such as
494 install and mtree. When upgrading from version of FreeBSD where
495 the install command does not support -l, you will need to
496 install a new mergemaster command if mergemaster -p is required.
497 This can be accomplished with the command (cd src/usr.sbin/mergemaster
501 Legacy ATA stack, disabled and replaced by new CAM-based one since
502 FreeBSD 9.0, completely removed from the sources. Kernel modules
503 atadisk and atapi*, user-level tools atacontrol and burncd are
504 removed. Kernel option `options ATA_CAM` is now permanently enabled
508 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
509 and socketpair(2). Software, in particular Kerberos, may
510 automatically detect and use these during building. The resulting
511 binaries will not work on older kernels.
514 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
515 information, see the respective 20130304 entry).
518 Recent commits to callout(9) changed the size of struct callout,
519 so the KBI is probably heavily disturbed. Also, some functions
520 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
521 by macros. Every kernel module using it won't load, so rebuild
524 The ctl device has been re-enabled in GENERIC for i386 and amd64,
525 but does not initialize by default (because of the new CTL_DISABLE
526 option) to save memory. To re-enable it, remove the CTL_DISABLE
527 option from the kernel config file or set kern.cam.ctl.disable=0
528 in /boot/loader.conf.
531 The ctl device has been disabled in GENERIC for i386 and amd64.
532 This was done due to the extra memory being allocated at system
533 initialisation time by the ctl driver which was only used if
534 a CAM target device was created. This makes a FreeBSD system
535 unusable on 128MB or less of RAM.
538 A new compression method (lz4) has been merged to -HEAD. Please
539 refer to zpool-features(7) for more information.
541 Please refer to the "ZFS notes" section of this file for information
542 on upgrading boot ZFS pools.
545 A BSD-licensed patch(1) variant has been added and is installed
546 as bsdpatch, being the GNU version the default patch.
547 To inverse the logic and use the BSD-licensed one as default,
548 while having the GNU version installed as gnupatch, rebuild
549 and install world with the WITH_BSD_PATCH knob set.
552 Due to the use of the new -l option to install(1) during build
553 and install, you must take care not to directly set the INSTALL
554 make variable in your /etc/make.conf, /etc/src.conf, or on the
555 command line. If you wish to use the -C flag for all installs
556 you may be able to add INSTALL+=-C to /etc/make.conf or
560 The install(1) option -M has changed meaning and now takes an
561 argument that is a file or path to append logs to. In the
562 unlikely event that -M was the last option on the command line
563 and the command line contained at least two files and a target
564 directory the first file will have logs appended to it. The -M
565 option served little practical purpose in the last decade so its
566 use is expected to be extremely rare.
569 After switching to Clang as the default compiler some users of ZFS
570 on i386 systems started to experience stack overflow kernel panics.
571 Please consider using 'options KSTACK_PAGES=4' in such configurations.
574 GEOM_LABEL now mangles label names read from file system metadata.
575 Mangling affect labels containing spaces, non-printable characters,
576 '%' or '"'. Device names in /etc/fstab and other places may need to
580 By default, only the 10 most recent kernel dumps will be saved. To
581 restore the previous behaviour (no limit on the number of kernel dumps
582 stored in the dump directory) add the following line to /etc/rc.conf:
587 With the addition of auditdistd(8), a new auditdistd user is now
588 required during installworld. "mergemaster -p" can be used to
589 add the user prior to installworld, as documented in the handbook.
592 The sin6_scope_id member variable in struct sockaddr_in6 is now
593 filled by the kernel before passing the structure to the userland via
594 sysctl or routing socket. This means the KAME-specific embedded scope
595 id in sin6_addr.s6_addr[2] is always cleared in userland application.
596 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
597 __FreeBSD_version is bumped to 1000025.
600 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
601 This means that the world and kernel will be compiled with clang
602 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
603 and /usr/bin/cpp. To disable this behavior and revert to building
604 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
605 of current may need to bootstrap WITHOUT_CLANG first if the clang
606 build fails (its compatibility window doesn't extend to the 9 stable
610 The IPFIREWALL_FORWARD kernel option has been removed. Its
611 functionality now turned on by default.
614 The ZERO_COPY_SOCKET kernel option has been removed and
615 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
616 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
617 mechanism which is not safe and may result in kernel crashes.
618 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
619 driver supports disposeable external page sized mbuf storage.
620 Proper replacements for both zero-copy mechanisms are under
621 consideration and will eventually lead to complete removal
622 of the two kernel options.
625 The IPv4 network stack has been converted to network byte
626 order. The following modules need to be recompiled together
627 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
628 pf(4), ipfw(4), ng_ipfw(4), stf(4).
631 Support for non-MPSAFE filesystems was removed from VFS. The
632 VFS_VERSION was bumped, all filesystem modules shall be
636 All the non-MPSAFE filesystems have been disconnected from
637 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
638 portalfs, smbfs, xfs.
641 The interface cloning API and ABI has changed. The following
642 modules need to be recompiled together with kernel:
643 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
644 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
645 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
648 The sdhci driver was split in two parts: sdhci (generic SD Host
649 Controller logic) and sdhci_pci (actual hardware driver).
650 No kernel config modifications are required, but if you
651 load sdhc as a module you must switch to sdhci_pci instead.
654 Import the FUSE kernel and userland support into base system.
657 The GNU sort(1) program has been removed since the BSD-licensed
658 sort(1) has been the default for quite some time and no serious
659 problems have been reported. The corresponding WITH_GNU_SORT
663 The pfil(9) API/ABI for AF_INET family has been changed. Packet
664 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
668 The net80211(4) ABI has been changed to allow for improved driver
669 PS-POLL and power-save support. All wireless drivers need to be
670 recompiled to work with the new kernel.
673 The random(4) support for the VIA hardware random number
674 generator (`PADLOCK') is no longer enabled unconditionally.
675 Add the padlock_rng device in the custom kernel config if
676 needed. The GENERIC kernels on i386 and amd64 do include the
677 device, so the change only affects the custom kernel
681 The pf(4) packet filter ABI has been changed. pfctl(8) and
682 snmp_pf module need to be recompiled to work with new kernel.
685 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
686 to -HEAD. Pools that have empty_bpobj in active state can not be
687 imported read-write with ZFS implementations that do not support
688 this feature. For more information read the zpool-features(5)
692 The sparc64 ZFS loader has been changed to no longer try to auto-
693 detect ZFS providers based on diskN aliases but now requires these
694 to be explicitly listed in the OFW boot-device environment variable.
697 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
698 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
699 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
702 The following sysctls and tunables have been renamed for consistency
703 with other variables:
704 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
705 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
708 The sort utility has been replaced with BSD sort. For now, GNU sort
709 is also available as "gnusort" or the default can be set back to
710 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
711 installed as "bsdsort".
714 A new version of ZFS (pool version 5000) has been merged to -HEAD.
715 Starting with this version the old system of ZFS pool versioning
716 is superseded by "feature flags". This concept enables forward
717 compatibility against certain future changes in functionality of ZFS
718 pools. The first read-only compatible "feature flag" for ZFS pools
719 is named "com.delphix:async_destroy". For more information
720 read the new zpool-features(5) manual page.
721 Please refer to the "ZFS notes" section of this file for information
722 on upgrading boot ZFS pools.
725 The malloc(3) implementation embedded in libc now uses sources imported
726 as contrib/jemalloc. The most disruptive API change is to
727 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
728 delete it prior to installworld, and optionally re-create it using the
729 new format after rebooting. See malloc.conf(5) for details
730 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
734 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
735 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
736 now spelled mips. This is to aid compatibility with third-party
737 software that expects this naming scheme in uname(3). Little-endian
738 settings are unchanged. If you are updating a big-endian mips64 machine
739 from before this change, you may need to set MACHINE_ARCH=mips64 in
740 your environment before the new build system will recognize your machine.
743 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
747 Now unix domain sockets behave "as expected" on nullfs(5). Previously
748 nullfs(5) did not pass through all behaviours to the underlying layer,
749 as a result if we bound to a socket on the lower layer we could connect
750 only to the lower path; if we bound to the upper layer we could connect
751 only to the upper path. The new behavior is one can connect to both the
752 lower and the upper paths regardless what layer path one binds to.
755 The getifaddrs upgrade path broken with 20111215 has been restored.
756 If you have upgraded in between 20111215 and 20120209 you need to
757 recompile libc again with your kernel. You still need to recompile
758 world to be able to configure CARP but this restriction already
762 The set_rcvar() function has been removed from /etc/rc.subr. All
763 base and ports rc.d scripts have been updated, so if you have a
764 port installed with a script in /usr/local/etc/rc.d you can either
765 hand-edit the rcvar= line, or reinstall the port.
767 An easy way to handle the mass-update of /etc/rc.d:
768 rm /etc/rc.d/* && mergemaster -i
771 panic(9) now stops other CPUs in the SMP systems, disables interrupts
772 on the current CPU and prevents other threads from running.
773 This behavior can be reverted using the kern.stop_scheduler_on_panic
775 The new behavior can be incompatible with kern.sync_on_panic.
778 The carp(4) facility has been changed significantly. Configuration
779 of the CARP protocol via ifconfig(8) has changed, as well as format
780 of CARP events submitted to devd(8) has changed. See manual pages
781 for more information. The arpbalance feature of carp(4) is currently
782 not supported anymore.
784 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
785 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
786 need to be recompiled.
789 The acpi_wmi(4) status device /dev/wmistat has been renamed to
793 The option VFS_ALLOW_NONMPSAFE option has been added in order to
794 explicitely support non-MPSAFE filesystems.
795 It is on by default for all supported platform at this present
799 The broken amd(4) driver has been replaced with esp(4) in the amd64,
800 i386 and pc98 GENERIC kernel configuration files.
803 sysinstall has been removed
806 The stable/9 branch created in subversion. This corresponds to the
807 RELENG_9 branch in CVS.
810 This commit modifies vfs_register() so that it uses a hash
811 calculation to set vfc_typenum, which is enabled by default.
812 The first time a system is booted after this change, the
813 vfc_typenum values will change for all file systems. The
814 main effect of this is a change to the NFS server file handles
815 for file systems that use vfc_typenum in their fsid, such as ZFS.
816 It will, however, prevent vfc_typenum from changing when file
817 systems are loaded in a different order for subsequent reboots.
818 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
819 until you are ready to remount all NFS clients after a reboot.
822 Bump the shared library version numbers for libraries that
823 do not use symbol versioning, have changed the ABI compared
824 to stable/8 and which shared library version was not bumped.
825 Done as part of 9.0-RELEASE cycle.
828 During the merge of Capsicum features, the fget(9) KPI was modified.
829 This may require the rebuilding of out-of-tree device drivers --
830 issues have been reported specifically with the nVidia device driver.
831 __FreeBSD_version is bumped to 900041.
833 Also, there is a period between 20110811 and 20110814 where the
834 special devices /dev/{stdin,stdout,stderr} did not work correctly.
835 Building world from a kernel during that window may not work.
838 The packet filter (pf) code has been updated to OpenBSD 4.5.
839 You need to update userland tools to be in sync with kernel.
840 This update breaks backward compatibility with earlier pfsync(4)
841 versions. Care must be taken when updating redundant firewall setups.
844 The following sysctls and tunables are retired on x86 platforms:
846 machdep.hlt_logical_cpus
847 The following sysctl is retired:
848 machdep.hyperthreading_allowed
849 The sysctls were supposed to provide a way to dynamically offline and
850 online selected CPUs on x86 platforms, but the implementation has not
851 been reliable especially with SCHED_ULE scheduler.
852 machdep.hyperthreading_allowed tunable is still available to ignore
853 hyperthreading CPUs at OS level.
854 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
855 where X is an APIC ID of a CPU. Be advised, though, that disabling
856 CPUs in non-uniform fashion will result in non-uniform topology and
857 may lead to sub-optimal system performance with SCHED_ULE, which is
861 cpumask_t type is retired and cpuset_t is used in order to describe
865 Changes to ifconfig(8) for dynamic address family detection mandate
866 that you are running a kernel of 20110525 or later. Make sure to
867 follow the update procedure to boot a new kernel before installing
871 Support for sun4v architecture is officially dropped
874 Several KPI breaking changes have been committed to the mii(4) layer,
875 the PHY drivers and consequently some Ethernet drivers using mii(4).
876 This means that miibus.ko and the modules of the affected Ethernet
877 drivers need to be recompiled.
879 Note to kernel developers: Given that the OUI bit reversion problem
880 was fixed as part of these changes all mii(4) commits related to OUIs,
881 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
882 handling, no longer can be merged verbatim to stable/8 and previous
886 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
887 into their kernel configurations along with 'device pci'.
890 The default NFS client is now the new NFS client, so fstype "newnfs"
891 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
892 Although mounts via fstype "nfs" will usually work without userland
893 changes, it is recommended that the mount(8) and mount_nfs(8)
894 commands be rebuilt from sources and that a link to mount_nfs called
895 mount_oldnfs be created. The new client is compiled into the
896 kernel with "options NFSCL" and this is needed for diskless root
897 file systems. The GENERIC kernel configs have been changed to use
898 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
899 To use the regular/old client, you can "mount -t oldnfs ...". For
900 a diskless root file system, you must also include a line like:
902 vfs.root.mountfrom="oldnfs:"
904 in the boot/loader.conf on the root fs on the NFS server to make
905 a diskless root fs use the old client.
908 The GENERIC kernels for all architectures now default to the new
909 CAM-based ATA stack. It means that all legacy ATA drivers were
910 removed and replaced by respective CAM drivers. If you are using
911 ATA device names in /etc/fstab or other places, make sure to update
912 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
913 where 'Y's are the sequential numbers starting from zero for each type
914 in order of detection, unless configured otherwise with tunables,
915 see cam(4)). There will be symbolic links created in /dev/ to map
916 old adX devices to the respective adaY. They should provide basic
917 compatibility for file systems mounting in most cases, but they do
918 not support old user-level APIs and do not have respective providers
919 in GEOM. Consider using updated management tools with new device names.
921 It is possible to load devices ahci, ata, siis and mvs as modules,
922 but option ATA_CAM should remain in kernel configuration to make ata
923 module work as CAM driver supporting legacy ATA controllers. Device ata
924 still can be used in modular fashion (atacore + ...). Modules atadisk
925 and atapi* are not used and won't affect operation in ATA_CAM mode.
926 Note that to use CAM-based ATA kernel should include CAM devices
927 scbus, pass, da (or explicitly ada), cd and optionally others. All of
928 them are parts of the cam module.
930 ataraid(4) functionality is now supported by the RAID GEOM class.
931 To use it you can load geom_raid kernel module and use graid(8) tool
932 for management. Instead of /dev/arX device names, use /dev/raid/rX.
934 No kernel config options or code have been removed, so if a problem
935 arises, please report it and optionally revert to the old ATA stack.
936 In order to do it you can remove from the kernel config:
941 , and instead add back:
942 device atadisk # ATA disk drives
943 device ataraid # ATA RAID drives
944 device atapicd # ATAPI CDROM drives
945 device atapifd # ATAPI floppy drives
946 device atapist # ATAPI tape drives
949 The default NFS server has been changed to the new server, which
950 was referred to as the experimental server. If you need to switch
951 back to the old NFS server, you must now put the "-o" option on
952 both the mountd and nfsd commands. This can be done using the
953 mountd_flags and nfs_server_flags rc.conf variables until an
954 update to the rc scripts is committed, which is coming soon.
957 The GNU Objective-C runtime library (libobjc), and other Objective-C
958 related components have been removed from the base system. If you
959 require an Objective-C library, please use one of the available ports.
962 ath(4) has been split into bus- and device- modules. if_ath contains
963 the HAL, the TX rate control and the network device code. if_ath_pci
964 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
965 contains the AHB glue. Users need to load both if_ath_pci and if_ath
966 in order to use ath on everything else.
968 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
969 need to load if_ath and if_ath_pci for ath(4) operation.
972 As part of the replacement of sysinstall, the process of building
973 release media has changed significantly. For details, please re-read
974 release(7), which has been updated to reflect the new build process.
977 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
978 is the last available version under GPLv2. It brings a number of new
979 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
980 4.1 and SSE 4.2), better support for powerpc64, a number of new
981 directives, and lots of other small improvements. See the ChangeLog
982 file in contrib/binutils for the full details.
985 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
986 compliant, and will now use half of hash for authentication.
987 This will break interoperability with all stacks (including all
988 actual FreeBSD versions) who implement
989 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
991 The only workaround with such peers is to use another HMAC
992 algorithm for IPsec ("phase 2") authentication.
995 Remove the uio_yield prototype and symbol. This function has
996 been misnamed since it was introduced and should not be
997 globally exposed with this name. The equivalent functionality
998 is now available using kern_yield(curthread->td_user_pri).
999 The function remains undocumented.
1002 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1003 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1004 for scalar sysctls is defined but disabled. Code that needs
1005 UQUAD to pass the type checking that must compile on older
1006 systems where the define is not present can check against
1007 __FreeBSD_version >= 900030.
1009 The system dialog(1) has been replaced with a new version previously
1010 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1011 with the previous version, but the libdialog associated with it has
1012 a largely incompatible API. As such, the original version of libdialog
1013 will be kept temporarily as libodialog, until its base system consumers
1014 are replaced or updated. Bump __FreeBSD_version to 900030.
1017 If you are trying to run make universe on a -stable system, and you get
1018 the following warning:
1019 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1020 unknown. config(8) likely too old."
1021 or something similar to it, then you must upgrade your -stable system
1022 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1023 stable/8) or build the config from the latest stable/8 branch and
1024 install it on your system.
1026 Prior to this date, building a current universe on 8-stable system from
1027 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1028 error in the first kernel build phase. A new config on those old
1029 systems will fix that problem for older versions of -current.
1032 The TCP stack has been modified to allow Khelp modules to interact with
1033 it via helper hook points and store per-connection data in the TCP
1034 control block. Bump __FreeBSD_version to 900029. User space tools that
1035 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1039 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1040 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1041 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1042 to take advantage of it instead of using custom implementations. This
1043 means that these drivers now no longer unconditionally advertise
1044 support for flow control but only do so if flow control is a selected
1045 media option. This was implemented in the generic support that way in
1046 order to allow flow control to be switched on and off via ifconfig(8)
1047 with the PHY specific default to typically off in order to protect
1048 from unwanted effects. Consequently, if you used flow control with
1049 one of the above mentioned drivers you now need to explicitly enable
1050 it, for example via:
1051 ifconfig bge0 media auto mediaopt flowcontrol
1053 Along with the above mentioned changes generic support for setting
1054 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1055 e1000phy(4) as well as ip1000phy(4) have been converted to take
1056 advantage of it. This means that these drivers now no longer take the
1057 link0 parameter for selecting master mode but the master media option
1058 has to be used instead, for example like in the following:
1059 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1061 Selection of master mode now is also available with all other PHY
1062 drivers supporting 1000baseT.
1065 The TCP stack has received a significant update to add support for
1066 modularised congestion control and generally improve the clarity of
1067 congestion control decisions. Bump __FreeBSD_version to 900025. User
1068 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1069 sockstat) need to be recompiled.
1072 The man(1) utility has been replaced by a new version that no longer
1073 uses /etc/manpath.config. Please consult man.conf(5) for how to
1074 migrate local entries to the new format.
1077 The copyright strings printed by login(1) and sshd(8) at the time of a
1078 new connection have been removed to follow other operating systems and
1082 A workaround for a fixed ld bug has been removed in kernel code,
1083 so make sure that your system ld is built from sources after
1084 revision 210245 from 2010-07-19 (r211583 if building head kernel
1085 on stable/8, r211584 for stable/7; both from 2010-08-21).
1086 A symptom of incorrect ld version is different addresses for
1087 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1090 The $ipv6_prefer variable in rc.conf(5) has been split into
1091 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1093 The $ip6addrctl_policy is a variable to choose a pre-defined
1094 address selection policy set by ip6addrctl(8). A value
1095 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1098 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1099 flag (see an entry of 20090926) is set on an interface with no
1100 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1101 security reason. If you want IPv6 link-local address on all
1102 interfaces by default, set this to "YES".
1104 The old ipv6_prefer="YES" is equivalent to
1105 ipv6_activate_all_interfaces="YES" and
1106 ip6addrctl_policy="ipv6_prefer".
1109 DTrace has grown support for userland tracing. Due to this, DTrace is
1110 now i386 and amd64 only.
1111 dtruss(1) is now installed by default on those systems and a new
1112 kernel module is needed for userland tracing: fasttrap.
1113 No changes to your kernel config file are necessary to enable
1114 userland tracing, but you might consider adding 'STRIP=' and
1115 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1116 to have informative userland stack traces in DTrace (ustack).
1119 The acpi_aiboost(4) driver has been removed in favor of the new
1120 aibs(4) driver. You should update your kernel configuration file.
1123 BSD grep has been imported to the base system and it is built by
1124 default. It is completely BSD licensed, highly GNU-compatible, uses
1125 less memory than its GNU counterpart and has a small codebase.
1126 However, it is slower than its GNU counterpart, which is mostly
1127 noticeable for larger searches, for smaller ones it is measurable
1128 but not significant. The reason is complex, the most important factor
1129 is that we lack a modern and efficient regex library and GNU
1130 overcomes this by optimizing the searches internally. Future work
1131 on improving the regex performance is planned, for the meantime,
1132 users that need better performance, can build GNU grep instead by
1133 setting the WITH_GNU_GREP knob.
1136 Due to the import of powerpc64 support, all existing powerpc kernel
1137 configuration files must be updated with a machine directive like this:
1138 machine powerpc powerpc
1140 In addition, an updated config(8) is required to build powerpc kernels
1144 A new version of ZFS (version 15) has been merged to -HEAD.
1145 This version uses a python library for the following subcommands:
1146 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1147 For full functionality of these commands the following port must
1148 be installed: sysutils/py-zfs
1151 'vm_page's are now hashed by physical address to an array of mutexes.
1152 Currently this is only used to serialize access to hold_count. Over
1153 time the page queue mutex will be peeled away. This changes the size
1154 of pmap on every architecture. And requires all callers of vm_page_hold
1155 and vm_page_unhold to be updated.
1158 WITH_CTF can now be specified in src.conf (not recommended, there
1159 are some problems with static executables), make.conf (would also
1160 affect ports which do not use GNU make and do not override the
1161 compile targets) or in the kernel config (via "makeoptions
1163 When WITH_CTF was specified there before this was silently ignored,
1164 so make sure that WITH_CTF is not used in places which could lead
1165 to unwanted behavior.
1168 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1169 to allow 32-bit compatibility on non-x86 platforms. All kernel
1170 configurations on amd64 and ia64 platforms using these options must
1171 be modified accordingly.
1174 The utmp user accounting database has been replaced with utmpx,
1175 the user accounting interface standardized by POSIX.
1176 Unfortunately the semantics of utmp and utmpx don't match,
1177 making it practically impossible to support both interfaces.
1178 The user accounting database is used by tools like finger(1),
1179 last(1), talk(1), w(1) and ac(8).
1181 All applications in the base system use utmpx. This means only
1182 local binaries (e.g. from the ports tree) may still use these
1183 utmp database files. These applications must be rebuilt to make
1186 After the system has been upgraded, it is safe to remove the old
1187 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1188 assuming their contents is of no importance anymore. Old wtmp
1189 databases can only be used by last(1) and ac(8) after they have
1190 been converted to the new format using wtmpcvt(1).
1193 Introduce the kernel thread "deadlock resolver" (which can be enabled
1194 via the DEADLKRES option, see NOTES for more details) and the
1195 sleepq_type() function for sleepqueues.
1198 The rc.firewall and rc.firewall6 were unified, and
1199 rc.firewall6 and rc.d/ip6fw were removed.
1200 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1201 variables are obsoleted. Instead, the following new rc
1202 variables are added to rc.d/ipfw:
1204 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1205 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1206 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1208 The meanings correspond to the relevant IPv4 variables.
1214 The default terminal emulation for syscons(4) has been changed
1215 from cons25 to xterm on all platforms except pc98. This means
1216 that the /etc/ttys file needs to be updated to ensure correct
1217 operation of applications on the console.
1219 The terminal emulation style can be toggled per window by using
1220 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1221 options can be used to change the compile-time default back to
1224 To prevent graphical artifacts, make sure the TERM environment
1225 variable is set to match the terminal emulation that is being
1226 performed by syscons(4).
1229 The layout of the structure ieee80211req_scan_result has changed.
1230 Applications that require wireless scan results (e.g. ifconfig(8))
1231 from net80211 need to be recompiled.
1233 Applications such as wpa_supplicant(8) may require a full world
1234 build without using NO_CLEAN in order to get synchronized with the
1238 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1239 There's one kernel module for each firmware. Adding "device iwnfw"
1240 to the kernel configuration file means including all three firmware
1241 images inside the kernel. If you want to include just the one for
1242 your wireless card, use the devices iwn4965fw, iwn5000fw or
1246 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1247 into rc.d/netif. The changes are the following:
1249 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1250 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1251 Note that both variables need the "inet6" keyword at the head.
1253 Do not set $ipv6_network_interfaces manually if you do not
1254 understand what you are doing. It is not needed in most cases.
1256 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1259 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1260 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1262 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1263 all configured interfaces have "inet6 accept_rtadv" in the
1264 $ifconfig_IF_ipv6. These are for backward compatibility.
1266 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1267 functionality of interfaces with no corresponding
1268 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1269 and the default address selection policy of ip6addrctl(8)
1270 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1271 Note that if you want to configure IPv6 functionality on the
1272 disabled interfaces after boot, first you need to clear the flag by
1273 using ifconfig(8) like:
1275 ifconfig em0 inet6 -ifdisabled
1277 If YES, the default address selection policy is set as
1280 The default value of $ipv6_prefer is NO.
1282 4. If your system need to receive Router Advertisement messages,
1283 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1284 scripts automatically invoke rtsol(8) when the interface becomes
1285 UP. The Router Advertisement messages are used for SLAAC
1286 (State-Less Address AutoConfiguration).
1289 802.11s D3.03 support was committed. This is incompatible with the
1290 previous code, which was based on D3.0.
1293 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1294 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1295 control whether accepting Router Advertisement messages or not.
1296 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1297 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1298 The ifconfig(8) utility now supports these flags.
1301 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1302 mount(8) and -a option for df(1) to see them.
1305 The old tunable hw.bus.devctl_disable has been superseded by
1306 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1307 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1311 Remove the option STOP_NMI. The default action is now to use NMI only
1312 for KDB via the newly introduced function stop_cpus_hard() and
1313 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1316 The stable/8 branch created in subversion. This corresponds to the
1317 RELENG_8 branch in CVS.
1320 Bump the shared library version numbers for all libraries that do not
1321 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1322 __FreeBSD_version to 800105.
1325 Due to changes in the implementation of virtual network stack support,
1326 all network-related kernel modules must be recompiled. As this change
1327 breaks the ABI, bump __FreeBSD_version to 800104.
1330 The TOE interface to the TCP syncache has been modified to remove
1331 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1332 The cxgb driver is the only TOE consumer affected by this change, and
1333 needs to be recompiled along with the kernel. As this change breaks
1334 the ABI, bump __FreeBSD_version to 800103.
1337 Padding has been added to struct tcpcb, sackhint and tcpstat in
1338 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1339 maintaining the ABI. However, this change breaks the ABI, so bump
1340 __FreeBSD_version to 800102. User space tools that rely on the size of
1341 any of these structs (e.g. sockstat) need to be recompiled.
1344 The NFS_LEGACYRPC option has been removed along with the old kernel
1345 RPC implementation that this option selected. Kernel configurations
1346 may need to be adjusted.
1349 The network interface device nodes at /dev/net/<interface> have been
1350 removed. All ioctl operations can be performed the normal way using
1351 routing sockets. The kqueue functionality can generally be replaced
1352 with routing sockets.
1355 The documentation from the FreeBSD Documentation Project (Handbook,
1356 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1357 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1360 The ABI of various structures related to the SYSV IPC API have been
1361 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1362 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1366 Layout of struct vnet has changed as routing related variables were
1367 moved to their own Vimage module. Modules need to be recompiled. Bump
1368 __FreeBSD_version to 800099.
1371 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1372 respectively. As long as no more than 16 groups per process are used,
1373 no changes should be visible. When more than 16 groups are used, old
1374 binaries may fail if they call getgroups() or getgrouplist() with
1375 statically sized storage. Recompiling will work around this, but
1376 applications should be modified to use dynamically allocated storage
1377 for group arrays as POSIX.1-2008 does not cap an implementation's
1378 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1380 NFS and portalfs mounts may also be affected as the list of groups is
1381 truncated to 16. Users of NFS who use more than 16 groups, should
1382 take care that negative group permissions are not used on the exported
1383 file systems as they will not be reliable unless a GSSAPI based
1384 authentication method is used.
1387 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1388 option compiles in the support for adaptive spinning for lockmgrs
1389 which want to enable it. The lockinit() function now accepts the flag
1390 LK_ADAPTIVE in order to make the lock object subject to adaptive
1391 spinning when both held in write and read mode.
1394 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1395 changed. User applications that use this ioctl need to be rebuilt.
1398 The layout of struct thread has changed. Kernel and modules need to
1402 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1403 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1406 window(1) has been removed from the base system. It can now be
1407 installed from ports. The port is called misc/window.
1410 The way we are storing and accessing `routing table' entries has
1411 changed. Programs reading the FIB, like netstat, need to be
1415 A new netisr implementation has been added for FreeBSD 8. Network
1416 file system modules, such as igmp, ipdivert, and others, should be
1418 Bump __FreeBSD_version to 800096.
1421 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1425 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1426 Bump __FreeBSD_version to 800094.
1429 Add mnt_xflag field to 'struct mount'. File system modules need to be
1431 Bump __FreeBSD_version to 800093.
1434 The compiling option ADAPTIVE_SX has been retired while it has been
1435 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1436 The KPI for sx_init_flags() changes as accepting flags:
1437 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1438 been introduced in order to handle the reversed logic.
1439 Bump __FreeBSD_version to 800092.
1442 Add support for hierarchical jails. Remove global securelevel.
1443 Bump __FreeBSD_version to 800091.
1446 The layout of struct vnet_net has changed, therefore modules
1448 Bump __FreeBSD_version to 800090.
1451 The newly imported zic(8) produces a new format in the output. Please
1452 run tzsetup(8) to install the newly created data to /etc/localtime.
1455 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1456 hw.usb.* and is now consistent again with previous releases.
1459 802.11 monitor mode support was revised and driver api's were changed.
1460 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1461 of DLT_IEEE802_11. No user-visible data structures were changed but
1462 applications that use DLT_IEEE802_11 may require changes.
1463 Bump __FreeBSD_version to 800088.
1466 The layout of the following structs has changed: sysctl_oid,
1467 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1468 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1469 panics may be experienced. World rebuild is required for
1470 correctly checking networking state from userland.
1471 Bump __FreeBSD_version to 800085.
1474 MLDv2 and Source-Specific Multicast (SSM) have been merged
1475 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1476 The implementation of SSM within FreeBSD's IPv6 stack closely
1477 follows the IPv4 implementation.
1479 For kernel developers:
1481 * The most important changes are that the ip6_output() and
1482 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1483 and this lock has been downgraded to a non-recursive mutex.
1485 * As with the changes to the IPv4 stack to support SSM, filtering
1486 of inbound multicast traffic must now be performed by transport
1487 protocols within the IPv6 stack. This does not apply to TCP and
1488 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1490 * The KPIs used by IPv6 multicast are similar to those used by
1491 the IPv4 stack, with the following differences:
1492 * im6o_mc_filter() is analogous to imo_multicast_filter().
1493 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1494 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1495 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1496 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1497 for MLDv1 have an additional 'timer' argument which is used to
1498 jitter the initial membership report for the solicited-node
1499 multicast membership on-link.
1500 * This is not strictly needed for MLDv2, which already jitters
1501 its report transmissions. However, the 'timer' argument is
1502 preserved in case MLDv1 is active on the interface.
1504 * The KAME linked-list based IPv6 membership implementation has
1505 been refactored to use a vector similar to that used by the IPv4
1507 Code which maintains a list of its own multicast memberships
1508 internally, e.g. carp, has been updated to reflect the new
1511 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1512 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1513 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1514 implementation constraint which needs to be addressed in HEAD.
1516 For application developers:
1518 * The changes are broadly similar to those made for the IPv4
1521 * The use of IPv4 and IPv6 multicast socket options on the same
1522 socket, using mapped addresses, HAS NOT been tested or supported.
1524 * There are a number of issues with the implementation of various
1525 IPv6 multicast APIs which need to be resolved in the API surface
1526 before the implementation is fully compatible with KAME userland
1527 use, and these are mostly to do with interface index treatment.
1529 * The literature available discusses the use of either the delta / ASM
1530 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1531 using setsourcefilter(3)/getsourcefilter(3). For more information
1532 please refer to RFC 3768, 'Socket Interface Extensions for
1533 Multicast Source Filters'.
1535 * Applications which use the published RFC 3678 APIs should be fine.
1537 For systems administrators:
1539 * The mtest(8) utility has been refactored to support IPv6, in
1540 addition to IPv4. Interface addresses are no longer accepted
1541 as arguments, their names must be used instead. The utility
1542 will map the interface name to its first IPv4 address as
1543 returned by getifaddrs(3).
1545 * The ifmcstat(8) utility has also been updated to print the MLDv2
1546 endpoint state and source filter lists via sysctl(3).
1548 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1549 loopback of IPv6 multicast datagrams by default; it defaults to 1
1550 to preserve the existing behaviour. Disabling multicast loopback is
1551 recommended for optimal system performance.
1553 * The IPv6 MROUTING code has been changed to examine this sysctl
1554 instead of attempting to perform a group lookup before looping
1555 back forwarded datagrams.
1557 Bump __FreeBSD_version to 800084.
1560 Implement low-level Bluetooth HCI API.
1561 Bump __FreeBSD_version to 800083.
1564 The layout of struct malloc_type, used by modules to register new
1565 memory allocation types, has changed. Most modules will need to
1566 be rebuilt or panics may be experienced.
1567 Bump __FreeBSD_version to 800081.
1570 Anticipate overflowing inp_flags - add inp_flags2.
1571 This changes most offsets in inpcb, so checking v4 connection
1572 state will require a world rebuild.
1573 Bump __FreeBSD_version to 800080.
1576 Add an llentry to struct route and struct route_in6. Modules
1577 embedding a struct route will need to be recompiled.
1578 Bump __FreeBSD_version to 800079.
1581 The size of rt_metrics_lite and by extension rtentry has changed.
1582 Networking administration apps will need to be recompiled.
1583 The route command now supports show as an alias for get, weighting
1584 of routes, sticky and nostick flags to alter the behavior of stateful
1586 Bump __FreeBSD_version to 800078.
1589 Do not use Giant for kbdmux(4) locking. This is wrong and
1590 apparently causing more problems than it solves. This will
1591 re-open the issue where interrupt handlers may race with
1592 kbdmux(4) in polling mode. Typical symptoms include (but
1593 not limited to) duplicated and/or missing characters when
1594 low level console functions (such as gets) are used while
1595 interrupts are enabled (for example geli password prompt,
1596 mountroot prompt etc.). Disabling kbdmux(4) may help.
1599 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1600 kernel modules referencing any of the above need to be recompiled.
1601 Bump __FreeBSD_version to 800075.
1604 GEOM_PART has become the default partition slicer for storage devices,
1605 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1606 introduces some changes:
1608 MSDOS/EBR: the devices created from MSDOS extended partition entries
1609 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1610 to devices with offset-based names. fstabs may need to be modified.
1612 BSD: the "geometry does not match label" warning is harmless in most
1613 cases but it points to problems in file system misalignment with
1614 disk geometry. The "c" partition is now implicit, covers the whole
1615 top-level drive and cannot be (mis)used by users.
1617 General: Kernel dumps are now not allowed to be written to devices
1618 whose partition types indicate they are meant to be used for file
1619 systems (or, in case of MSDOS partitions, as something else than
1622 Most of these changes date approximately from 200812.
1625 The uscanner(4) driver has been removed from the kernel. This follows
1626 Linux removing theirs in 2.6 and making libusb the default interface
1627 (supported by sane).
1630 The multicast forwarding code has been cleaned up. netstat(1)
1631 only relies on KVM now for printing bandwidth upcall meters.
1632 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1633 ip6_mroute_mod respectively. The config(5) options for statically
1634 compiling this code remain the same, i.e. 'options MROUTING'.
1637 Support for the IFF_NEEDSGIANT network interface flag has been
1638 removed, which means that non-MPSAFE network device drivers are no
1639 longer supported. In particular, if_ar, if_sr, and network device
1640 drivers from the old (legacy) USB stack can no longer be built or
1644 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1645 a bunch of new language catalog files have also been added.
1646 This means that some common libc messages are now localized and
1647 they depend on the LC_MESSAGES environmental variable.
1650 The k8temp(4) driver has been renamed to amdtemp(4) since
1651 support for Family 10 and Family 11 CPU families was added.
1654 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1655 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1657 For kernel developers, the most important changes are that the
1658 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1659 and this lock has been downgraded to a non-recursive mutex.
1661 Transport protocols (UDP, Raw IP) are now responsible for filtering
1662 inbound multicast traffic according to group membership and source
1663 filters. The imo_multicast_filter() KPI exists for this purpose.
1664 Transports which do not use multicast (SCTP, TCP) already reject
1665 multicast by default. Forwarding and receive performance may improve
1666 as a mutex acquisition is no longer needed in the ip_input()
1667 low-level input path. in_addmulti() and in_delmulti() are shimmed
1668 to new KPIs which exist to support SSM in-kernel.
1670 For application developers, it is recommended that loopback of
1671 multicast datagrams be disabled for best performance, as this
1672 will still cause the lock to be taken for each looped-back
1673 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1674 be tuned to 0 to disable loopback by default; it defaults to 1
1675 to preserve the existing behaviour.
1677 For systems administrators, to obtain best performance with
1678 multicast reception and multiple groups, it is always recommended
1679 that a card with a suitably precise hash filter is used. Hash
1680 collisions will still result in the lock being taken within the
1681 transport protocol input path to check group membership.
1683 If deploying FreeBSD in an environment with IGMP snooping switches,
1684 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1685 enabled; this forces 224.0.0.0/24 group membership to be announced
1688 The size of 'struct igmpstat' has changed; netstat needs to be
1689 recompiled to reflect this.
1690 Bump __FreeBSD_version to 800070.
1693 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1694 updated to use it. This requires a buildworld/installworld in order to
1695 update the library and dependencies (usbconfig, etc). Its advisable to
1696 rebuild all ports which uses libusb. More specific directions are given
1697 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1698 libusb are no longer required and can be removed.
1701 A workaround is committed to allow the creation of System V shared
1702 memory segment of size > 2 GB on the 64-bit architectures.
1703 Due to a limitation of the existing ABI, the shm_segsz member
1704 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1705 wrong for large segments. Note that limits must be explicitly
1706 raised to allow such segments to be created.
1709 The layout of struct ifnet has changed, requiring a rebuild of all
1710 network device driver modules.
1713 The /dev handling for the new USB stack has changed, a
1714 buildworld/installworld is required for libusb20.
1717 The new USB2 stack has now been permanently moved in and all kernel and
1718 module names reverted to their previous values (eg, usb, ehci, ohci,
1719 ums, ...). The old usb stack can be compiled in by prefixing the name
1720 with the letter 'o', the old usb modules have been removed.
1721 Updating entry 20090216 for xorg and 20090215 for libmap may still
1725 The rc.conf(5) option if_up_delay has been renamed to
1726 defaultroute_delay to better reflect its purpose. If you have
1727 customized this setting in /etc/rc.conf you need to update it to
1731 xorg 7.4 wants to configure its input devices via hald which does not
1732 yet work with USB2. If the keyboard/mouse does not work in xorg then
1734 Option "AllowEmptyInput" "off"
1735 to your ServerLayout section. This will cause X to use the configured
1736 kbd and mouse sections from your xorg.conf.
1739 The GENERIC kernels for all architectures now default to the new USB2
1740 stack. No kernel config options or code have been removed so if a
1741 problem arises please report it and optionally revert to the old USB
1742 stack. If you are loading USB kernel modules or have a custom kernel
1743 that includes GENERIC then ensure that usb names are also changed over,
1744 eg uftdi -> usb2_serial_ftdi.
1746 Older programs linked against the ports libusb 0.1 need to be
1747 redirected to the new stack's libusb20. /etc/libmap.conf can
1749 # Map old usb library to new one for usb2 stack
1750 libusb-0.1.so.8 libusb20.so.1
1753 All USB ethernet devices now attach as interfaces under the name ueN
1754 (eg. ue0). This is to provide a predictable name as vendors often
1755 change usb chipsets in a product without notice.
1758 The ichsmb(4) driver has been changed to require SMBus slave
1759 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1760 All of the other SMBus controller drivers require left-justified
1761 slave addresses, so this change makes all the drivers provide the
1765 INET6 statistics (struct ip6stat) was updated.
1766 netstat(1) needs to be recompiled.
1769 NTFS has been removed from GENERIC kernel on amd64 to match
1770 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1771 will load ntfs.ko module automatically when NTFS support is
1772 actually needed, unless ntfs.ko is not installed or security
1773 level prohibits loading kernel modules. If either is the case,
1774 "options NTFS" has to be added into kernel config.
1777 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1778 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1779 800061. User space tools that rely on the size of struct tcpcb in
1780 tcp_var.h (e.g. sockstat) need to be recompiled.
1783 ng_tty(4) module updated to match the new TTY subsystem.
1784 Due to API change, user-level applications must be updated.
1785 New API support added to mpd5 CVS and expected to be present
1786 in next mpd5.3 release.
1789 With __FreeBSD_version 800060 the makefs tool is part of
1790 the base system (it was a port).
1793 The afdata and ifnet locks have been changed from mutexes to
1794 rwlocks, network modules will need to be re-compiled.
1797 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1798 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1799 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1800 architecture and 40 bytes on 64-bit architecture. The userland
1801 applications "arp" and "ndp" have been updated accordingly.
1802 The output from "netstat -r" shows only routing entries and
1803 none of the L2 information.
1806 __FreeBSD_version 800057 marks the switchover from the
1807 binary ath hal to source code. Users must add the line:
1809 options AH_SUPPORT_AR5416
1811 to their kernel config files when specifying:
1815 The ath_hal module no longer exists; the code is now compiled
1816 together with the driver in the ath module. It is now
1817 possible to tailor chip support (i.e. reduce the set of chips
1818 and thereby the code size); consult ath_hal(4) for details.
1821 __FreeBSD_version 800054 adds memory barriers to
1822 <machine/atomic.h>, new interfaces to ifnet to facilitate
1823 multiple hardware transmit queues for cards that support
1824 them, and a lock-less ring-buffer implementation to
1825 enable drivers to more efficiently manage queueing of
1829 A new version of ZFS (version 13) has been merged to -HEAD.
1830 This version has zpool attribute "listsnapshots" off by
1831 default, which means "zfs list" does not show snapshots,
1832 and is the same as Solaris behavior.
1835 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1838 The uhci, ohci, ehci and slhci USB Host controller drivers have
1839 been put into separate modules. If you load the usb module
1840 separately through loader.conf you will need to load the
1841 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1842 controller add the following to loader.conf:
1848 The ABI used by the PMC toolset has changed. Please keep
1849 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1853 atapci kernel module now includes only generic PCI ATA
1854 driver. AHCI driver moved to ataahci kernel module.
1855 All vendor-specific code moved into separate kernel modules:
1856 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1857 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1858 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1859 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1862 The TTY subsystem of the kernel has been replaced by a new
1863 implementation, which provides better scalability and an
1864 improved driver model. Most common drivers have been migrated to
1865 the new TTY subsystem, while others have not. The following
1866 drivers have not yet been ported to the new TTY layer:
1869 cy, digi, rc, rp, sio
1875 ng_h4, ng_tty, ppp, sl, snp
1877 Adding these drivers to your kernel configuration file shall
1878 cause compilation to fail.
1881 ntpd has been upgraded to 4.2.4p5.
1884 OpenSSH has been upgraded to 5.1p1.
1886 For many years, FreeBSD's version of OpenSSH preferred DSA
1887 over RSA for host and user authentication keys. With this
1888 upgrade, we've switched to the vendor's default of RSA over
1889 DSA. This may cause upgraded clients to warn about unknown
1890 host keys even for previously known hosts. Users should
1891 follow the usual procedure for verifying host keys before
1892 accepting the RSA key.
1894 This can be circumvented by setting the "HostKeyAlgorithms"
1895 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1898 Please note that the sequence of keys offered for
1899 authentication has been changed as well. You may want to
1900 specify IdentityFile in a different order to revert this
1904 The sio(4) driver has been removed from the i386 and amd64
1905 kernel configuration files. This means uart(4) is now the
1906 default serial port driver on those platforms as well.
1908 To prevent collisions with the sio(4) driver, the uart(4) driver
1909 uses different names for its device nodes. This means the
1910 onboard serial port will now most likely be called "ttyu0"
1911 instead of "ttyd0". You may need to reconfigure applications to
1912 use the new device names.
1914 When using the serial port as a boot console, be sure to update
1915 /boot/device.hints and /etc/ttys before booting the new kernel.
1916 If you forget to do so, you can still manually specify the hints
1917 at the loader prompt:
1919 set hint.uart.0.at="isa"
1920 set hint.uart.0.port="0x3F8"
1921 set hint.uart.0.flags="0x10"
1922 set hint.uart.0.irq="4"
1926 The gpt(8) utility has been removed. Use gpart(8) to partition
1930 The version that Linuxulator emulates was changed from 2.4.2
1931 to 2.6.16. If you experience any problems with Linux binaries
1932 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1933 if it fixes the problem contact emulation mailing list.
1936 ISDN4BSD (I4B) was removed from the src tree. You may need to
1937 update a your kernel configuration and remove relevant entries.
1940 I have checked in code to support multiple routing tables.
1941 See the man pages setfib(1) and setfib(2).
1942 This is a hopefully backwards compatible version,
1943 but to make use of it you need to compile your kernel
1944 with options ROUTETABLES=2 (or more up to 16).
1947 The 802.11 wireless support was redone to enable multi-bss
1948 operation on devices that are capable. The underlying device
1949 is no longer used directly but instead wlanX devices are
1950 cloned with ifconfig. This requires changes to rc.conf files.
1951 For example, change:
1952 ifconfig_ath0="WPA DHCP"
1955 ifconfig_wlan0="WPA DHCP"
1956 see rc.conf(5) for more details. In addition, mergemaster of
1957 /etc/rc.d is highly recommended. Simultaneous update of userland
1958 and kernel wouldn't hurt either.
1960 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1961 modules were merged into the base wlan module. All references
1962 to these modules (e.g. in kernel config files) must be removed.
1965 psm(4) has gained write(2) support in native operation level.
1966 Arbitrary commands can be written to /dev/psm%d and status can
1967 be read back from it. Therefore, an application is responsible
1968 for status validation and error recovery. It is a no-op in
1969 other operation levels.
1972 Support for KSE threading has been removed from the kernel. To
1973 run legacy applications linked against KSE libmap.conf may
1974 be used. The following libmap.conf may be used to ensure
1975 compatibility with any prior release:
1977 libpthread.so.1 libthr.so.1
1978 libpthread.so.2 libthr.so.2
1979 libkse.so.3 libthr.so.3
1982 The layout of struct vmspace has changed. This affects libkvm
1983 and any executables that link against libkvm and use the
1984 kvm_getprocs() function. In particular, but not exclusively,
1985 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1986 The effects are minimal, but it's advisable to upgrade world
1990 The latest em driver no longer has support in it for the
1991 82575 adapter, this is now moved to the igb driver. The
1992 split was done to make new features that are incompatible
1993 with older hardware easier to do.
1996 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1997 likewise the kernel option is now GEOM_LINUX_LVM.
2000 The default NFS mount mode has changed from UDP to TCP for
2001 increased reliability. If you rely on (insecurely) NFS
2002 mounting across a firewall you may need to update your
2006 Belatedly note the addition of m_collapse for compacting
2010 The fts(3) structures have been changed to use adequate
2011 integer types for their members and so to be able to cope
2012 with huge file trees. The old fts(3) ABI is preserved
2013 through symbol versioning in libc, so third-party binaries
2014 using fts(3) should still work, although they will not take
2015 advantage of the extended types. At the same time, some
2016 third-party software might fail to build after this change
2017 due to unportable assumptions made in its source code about
2018 fts(3) structure members. Such software should be fixed
2019 by its vendor or, in the worst case, in the ports tree.
2020 FreeBSD_version 800015 marks this change for the unlikely
2021 case that a portable fix is impossible.
2024 To upgrade to -current after this date, you must be running
2025 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2026 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2029 The ADAPTIVE_GIANT kernel option has been retired because its
2030 functionality is the default now.
2033 The AT keyboard emulation of sunkbd(4) has been turned on
2034 by default. In order to make the special symbols of the Sun
2035 keyboards driven by sunkbd(4) work under X these now have
2036 to be configured the same way as Sun USB keyboards driven
2037 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2039 Option "XkbLayout" "us"
2040 Option "XkbRules" "xorg"
2041 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2044 It has been decided that it is desirable to provide ABI
2045 backwards compatibility to the FreeBSD 4/5/6 versions of the
2046 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2047 broken with the introduction of PCI domain support (see the
2048 20070930 entry). Unfortunately, this required the ABI of
2049 PCIOCGETCONF to be broken again in order to be able to
2050 provide backwards compatibility to the old version of that
2051 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2052 again. As for prominent ports this affects neither pciutils
2053 nor xorg-server this time, the hal port needs to be rebuilt
2057 The misnamed kthread_create() and friends have been renamed
2058 to kproc_create() etc. Many of the callers already
2059 used kproc_start()..
2060 I will return kthread_create() and friends in a while
2061 with implementations that actually create threads, not procs.
2062 Renaming corresponds with version 800002.
2071 Avoid using make -j when upgrading. While generally safe, there are
2072 sometimes problems using -j to upgrade. If your upgrade fails with
2073 -j, please try again without -j. From time to time in the past there
2074 have been problems using -j with buildworld and/or installworld. This
2075 is especially true when upgrading between "distant" versions (eg one
2076 that cross a major release boundary or several minor releases, or when
2077 several months have passed on the -current branch).
2079 Sometimes, obscure build problems are the result of environment
2080 poisoning. This can happen because the make utility reads its
2081 environment when searching for values for global variables. To run
2082 your build attempts in an "environmental clean room", prefix all make
2083 commands with 'env -i '. See the env(1) manual page for more details.
2085 When upgrading from one major version to another it is generally best
2086 to upgrade to the latest code in the currently installed branch first,
2087 then do an upgrade to the new branch. This is the best-tested upgrade
2088 path, and has the highest probability of being successful. Please try
2089 this approach before reporting problems with a major version upgrade.
2091 When upgrading a live system, having a root shell around before
2092 installing anything can help undo problems. Not having a root shell
2093 around can lead to problems if pam has changed too much from your
2094 starting point to allow continued authentication after the upgrade.
2098 When upgrading the boot ZFS pool to a new version, always follow
2101 1.) recompile and reinstall the ZFS boot loader and boot block
2102 (this is part of "make buildworld" and "make installworld")
2104 2.) update the ZFS boot block on your boot drive
2106 The following example updates the ZFS boot block on the first
2107 partition (freebsd-boot) of a GPT partitioned drive ad0:
2108 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2110 Non-boot pools do not need these updates.
2114 If you are updating from a prior version of FreeBSD (even one just
2115 a few days old), you should follow this procedure. It is the most
2116 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2118 make kernel-toolchain
2119 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2120 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2122 To test a kernel once
2123 ---------------------
2124 If you just want to boot a kernel once (because you are not sure
2125 if it works, or if you want to boot a known bad kernel to provide
2126 debugging information) run
2127 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2128 nextboot -k testkernel
2130 To just build a kernel when you know that it won't mess you up
2131 --------------------------------------------------------------
2132 This assumes you are already running a CURRENT system. Replace
2133 ${arch} with the architecture of your machine (e.g. "i386",
2134 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2136 cd src/sys/${arch}/conf
2137 config KERNEL_NAME_HERE
2138 cd ../compile/KERNEL_NAME_HERE
2143 If this fails, go to the "To build a kernel" section.
2145 To rebuild everything and install it on the current system.
2146 -----------------------------------------------------------
2147 # Note: sometimes if you are running current you gotta do more than
2148 # is listed here if you are upgrading from a really old current.
2150 <make sure you have good level 0 dumps>
2152 make kernel KERNCONF=YOUR_KERNEL_HERE
2154 <reboot in single user> [3]
2161 To cross-install current onto a separate partition
2162 --------------------------------------------------
2163 # In this approach we use a separate partition to hold
2164 # current's root, 'usr', and 'var' directories. A partition
2165 # holding "/", "/usr" and "/var" should be about 2GB in
2168 <make sure you have good level 0 dumps>
2171 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2172 <maybe newfs current's root partition>
2173 <mount current's root partition on directory ${CURRENT_ROOT}>
2174 make installworld DESTDIR=${CURRENT_ROOT}
2175 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2176 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2177 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2178 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2179 <reboot into current>
2180 <do a "native" rebuild/install as described in the previous section>
2181 <maybe install compatibility libraries from ports/misc/compat*>
2185 To upgrade in-place from stable to current
2186 ----------------------------------------------
2187 <make sure you have good level 0 dumps>
2189 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2191 <reboot in single user> [3]
2198 Make sure that you've read the UPDATING file to understand the
2199 tweaks to various things you need. At this point in the life
2200 cycle of current, things change often and you are on your own
2201 to cope. The defaults can also change, so please read ALL of
2202 the UPDATING entries.
2204 Also, if you are tracking -current, you must be subscribed to
2205 freebsd-current@freebsd.org. Make sure that before you update
2206 your sources that you have read and understood all the recent
2207 messages there. If in doubt, please track -stable which has
2208 much fewer pitfalls.
2210 [1] If you have third party modules, such as vmware, you
2211 should disable them at this point so they don't crash your
2214 [3] From the bootblocks, boot -s, and then do
2219 adjkerntz -i # if CMOS is wall time
2220 Also, when doing a major release upgrade, it is required that
2221 you boot into single user mode to do the installworld.
2223 [4] Note: This step is non-optional. Failure to do this step
2224 can result in a significant reduction in the functionality of the
2225 system. Attempting to do it by hand is not recommended and those
2226 that pursue this avenue should read this file carefully, as well
2227 as the archives of freebsd-current and freebsd-hackers mailing lists
2228 for potential gotchas. The -U option is also useful to consider.
2229 See mergemaster(8) for more information.
2231 [5] Usually this step is a noop. However, from time to time
2232 you may need to do this if you get unknown user in the following
2233 step. It never hurts to do it all the time. You may need to
2234 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2235 install) after the buildworld before this step if you last updated
2236 from current before 20130425 or from -stable before 20130430.
2238 [6] This only deletes old files and directories. Old libraries
2239 can be deleted by "make delete-old-libs", but you have to make
2240 sure that no program is using those libraries anymore.
2242 [8] In order to have a kernel that can run the 4.x binaries needed to
2243 do an installworld, you must include the COMPAT_FREEBSD4 option in
2244 your kernel. Failure to do so may leave you with a system that is
2245 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2246 required to run the 5.x binaries on more recent kernels. And so on
2247 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2249 Make sure that you merge any new devices from GENERIC since the
2250 last time you updated your kernel config file.
2252 [9] When checking out sources, you must include the -P flag to have
2253 cvs prune empty directories.
2255 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2256 "?=" instead of the "=" assignment operator, so that buildworld can
2257 override the CPUTYPE if it needs to.
2259 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2260 not on the command line, or in /etc/make.conf. buildworld will
2261 warn if it is improperly defined.
2264 This file contains a list, in reverse chronological order, of major
2265 breakages in tracking -current. It is not guaranteed to be a complete
2266 list of such breakages, and only contains entries since October 10, 2007.
2267 If you need to see UPDATING entries from before that date, you will need
2268 to fetch an UPDATING file from an older FreeBSD release.
2270 Copyright information:
2272 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2274 Redistribution, publication, translation and use, with or without
2275 modification, in full or in part, in any form or format of this
2276 document are permitted without further permission from the author.
2278 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2279 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2280 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2281 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2282 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2283 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2284 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2285 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2286 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2287 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2288 POSSIBILITY OF SUCH DAMAGE.
2290 Contact Warner Losh if you have any questions about your use of