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 code that provides support for ZFS .zfs/ directory functionality
21 has been reimplemented. It's not possible now to create a snapshot
22 by mkdir under .zfs/snapshot/. That should be the only user visible
26 The NONE and HPN patches has been removed from OpenSSH. They are
27 still available in the security/openssh-portable port.
30 r292223 changed the internal interface between the nfsd.ko and
31 nfscommon.ko modules. As such, they must both be upgraded to-gether.
32 __FreeBSD_version has been bumped because of this.
35 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
36 Kernel modules isp_2400_multi and isp_2500_multi were removed and
37 should be replaced with isp_2400 and isp_2500 modules respectively.
40 The menu.rc and loader.rc files will now be replaced during
41 upgrades. Please migrate local changes to menu.rc.local and
42 loader.rc.local instead.
45 NTP has been upgraded to 4.2.8p4.
48 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
49 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
50 and devel/kyua to version 0.20+ and adjust any calling code to work
51 with Kyuafile and kyua.
54 The polarity of Pulse Per Second (PPS) capture events with the
55 uart(4) driver has been corrected. Prior to this change the PPS
56 "assert" event corresponded to the trailing edge of a positive PPS
57 pulse and the "clear" event was the leading edge of the next pulse.
59 As the width of a PPS pulse in a typical GPS receiver is on the
60 order of 1 millisecond, most users will not notice any significant
61 difference with this change.
63 Anyone who has compensated for the historical polarity reversal by
64 configuring a negative offset equal to the pulse width will need to
65 remove that workaround.
68 From legacy ata(4) driver was removed support for SATA controllers
69 supported by more functional drivers ahci(4), siis(4) and mvs(4).
70 Kernel modules ataahci and ataadaptec were removed completely,
71 replaced by ahci and mvs modules respectively.
77 As ZFS requires more kernel stack pages than is the default on some
78 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
79 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
81 Please consider using 'options KSTACK_PAGES=X' where X is greater
82 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
85 The default Unbound configuration now enables remote control
86 using a local socket. Users who have already enabled the
87 local_unbound service should regenerate their configuration
88 by running "service local_unbound setup" as root.
91 An additional fix for the issue described in the 20150614 sendmail
92 entry below has been been committed in revision 284786.
95 The fix for the issue described in the 20150614 sendmail entry
96 below has been been committed in revision 284485. The work
97 around described in that entry is no longer needed unless the
98 default setting is overridden by a confDH_PARAMETERS configuration
99 setting of '5' or pointing to a 512 bit DH parameter file.
102 The import of openssl to address the FreeBSD-SA-15:10.openssl
103 security advisory includes a change which rejects handshakes
104 with DH parameters below 768 bits. sendmail releases prior
105 to 8.15.2 (not yet released), defaulted to a 512 bit
106 DH parameter setting for client connections. To work around
107 this interoperability, sendmail can be configured to use a
108 2048 bit DH parameter by:
110 1. Edit /etc/mail/`hostname`.mc
111 2. If a setting for confDH_PARAMETERS does not exist or
112 exists and is set to a string beginning with '5',
114 3. If a setting for confDH_PARAMETERS exists and is set to
115 a file path, create a new file with:
116 openssl dhparam -out /path/to/file 2048
117 4. Rebuild the .cf file:
118 cd /etc/mail/; make; make install
120 cd /etc/mail/; make restart
122 A sendmail patch is coming, at which time this file will be
126 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
127 defined in symlink(7); previously symlinks were silently ignored.
130 The const qualifier has been removed from iconv(3) to comply with
131 POSIX. The ports tree is aware of this from r384038 onwards.
134 At svn r275807, The default linux compat kernel ABI has been adjusted
135 to 2.6.18 in support of the linux-c6 compat ports infrastructure
136 update. If you wish to continue using the linux-f10 compat ports,
137 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
138 encouraged to update their linux-compat packages to linux-c6 during
139 their next update cycle.
141 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
144 pjdfstest has been integrated into kyua as an opt-in test suite.
145 Please see share/doc/pjdfstest/README for a more details on how to
152 The ofwfb driver, used to provide a graphics console on PowerPC when
153 using vt(4), no longer allows mmap() of all of physical memory. This
154 will prevent Xorg on PowerPC with some ATI graphics cards from
155 initializing properly unless x11-servers/xorg-server is updated to
159 The libatf-c and libatf-c++ major versions were downgraded to 0 and
160 1 respectively to match the upstream numbers. They were out of
161 sync because, when they were originally added to FreeBSD, the
162 upstream versions were not respected. These libraries are private
163 and not yet built by default, so renumbering them should be a
164 non-issue. However, unclean source trees will yield broken test
165 programs once the operator executes "make delete-old-libs" after a
168 Additionally, the atf-sh binary was made private by moving it into
169 /usr/libexec/. Already-built shell test programs will keep the
170 path to the old binary so they will break after "make delete-old"
173 If you are using WITH_TESTS=yes (not the default), wipe the object
174 tree and rebuild from scratch to prevent spurious test failures.
175 This is only needed once: the misnumbered libraries and misplaced
176 binaries have been added to OptionalObsoleteFiles.inc so they will
177 be removed during a clean upgrade.
180 The ixgbe tunables now match their sysctl counterparts, for example:
181 hw.ixgbe.enable_aim => hw.ix.enable_aim
182 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
185 The NFSv4.1 server committed by r269398 changes the internal
186 function call interfaces used between the NFS and krpc modules.
187 As such, __FreeBSD_version was bumped.
190 The default unbound configuration has been modified to address
191 issues with reverse lookups on networks that use private
192 address ranges. If you use the local_unbound service, run
193 "service local_unbound setup" as root to regenerate your
194 configuration, then "service local_unbound reload" to load the
198 It is no longer necessary to include the dwarf version in your DEBUG
199 options in your kernel config file. The bug that required it to be
200 placed in the config file has bene fixed. DEBUG should now just
201 contain -g. The build system will automatically update things
202 to do the right thing.
205 Several ABI breaking changes were merged to CTL and new iSCSI code.
206 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
207 iscsictl need to be rebuilt to work with a new kernel.
210 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
211 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
212 which differs from the behaviour controlled by this knob.)
215 On i386 and amd64 systems, the onifconsole flag is now set by default
216 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
217 as a login TTY if it is set in the bootloader as an active kernel
218 console. No changes in behavior should result otherwise. To revert to
219 the previous behavior, set ttyu0 to "off" in /etc/ttys.
222 Clang and llvm have been upgraded to 3.4.1 release.
225 Clang and llvm have been upgraded to 3.4 release.
228 If a Makefile in a tests/ directory was auto-generating a Kyuafile
229 instead of providing an explicit one, this would prevent such
230 Makefile from providing its own Kyuafile in the future during
231 NO_CLEAN builds. This has been fixed in the Makefiles but manual
232 intervention is needed to clean an objdir if you use NO_CLEAN:
233 # find /usr/obj -name Kyuafile | xargs rm -f
236 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
237 capability mode support. Please note that enabling the feature in
238 kernel is still highly recommended.
241 OpenSSH is now built with sandbox support, and will use sandbox as
242 the default privilege separation method. This requires Capsicum
243 capability mode support in kernel.
246 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
247 been deprecated and will not be part of FreeBSD 11.0 and later
248 releases. If you use this driver, please consider switching to
249 the nfe(4) driver instead.
255 The behavior of gss_pseudo_random() for the krb5 mechanism
256 has changed, for applications requesting a longer random string
257 than produced by the underlying enctype's pseudo-random() function.
258 In particular, the random string produced from a session key of
259 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
260 be different at the 17th octet and later, after this change.
261 The counter used in the PRF+ construction is now encoded as a
262 big-endian integer in accordance with RFC 4402.
263 __FreeBSD_version is bumped to 1000701.
266 The WITHOUT_ATF build knob has been removed and its functionality
267 has been subsumed into the more generic WITHOUT_TESTS. If you were
268 using the former to disable the build of the ATF libraries, you
269 should change your settings to use the latter.
272 The default version of mtree is nmtree which is obtained from
273 NetBSD. The output is generally the same, but may vary
274 slightly. If you found you need identical output adding
275 "-F freebsd9" to the command line should do the trick. For the
276 time being, the old mtree is available as fmtree.
279 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
280 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
281 1.1.4_8 and verify bsdyml not linked in, before running "make
283 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
285 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
288 The rc.d/jail script has been updated to support jail(8)
289 configuration file. The "jail_<jname>_*" rc.conf(5) variables
290 for per-jail configuration are automatically converted to
291 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
292 This is transparently backward compatible. See below about some
293 incompatibilities and rc.conf(5) manual page for more details.
295 These variables are now deprecated in favor of jail(8) configuration
296 file. One can use "rc.d/jail config <jname>" command to generate
297 a jail(8) configuration file in /var/run/jail.<jname>.conf without
298 running the jail(8) utility. The default pathname of the
299 configuration file is /etc/jail.conf and can be specified by
300 using $jail_conf or $jail_<jname>_conf variables.
302 Please note that jail_devfs_ruleset accepts an integer at
303 this moment. Please consider to rewrite the ruleset name
307 BIND has been removed from the base system. If all you need
308 is a local resolver, simply enable and start the local_unbound
309 service instead. Otherwise, several versions of BIND are
310 available in the ports tree. The dns/bind99 port is one example.
312 With this change, nslookup(1) and dig(1) are no longer in the base
313 system. Users should instead use host(1) and drill(1) which are
314 in the base system. Alternatively, nslookup and dig can
315 be obtained by installing the dns/bind-tools port.
318 With the addition of unbound(8), a new unbound user is now
319 required during installworld. "mergemaster -p" can be used to
320 add the user prior to installworld, as documented in the handbook.
323 OpenSSH is now built with DNSSEC support, and will by default
324 silently trust signed SSHFP records. This can be controlled with
325 the VerifyHostKeyDNS client configuration setting. DNSSEC support
326 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
329 The GNU Compiler Collection and C++ standard library (libstdc++)
330 are no longer built by default on platforms where clang is the system
331 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
335 The PROCDESC kernel option is now part of the GENERIC kernel
336 configuration and is required for the rwhod(8) to work.
337 If you are using custom kernel configuration, you should include
341 The API and ABI related to the Capsicum framework was modified
342 in backward incompatible way. The userland libraries and programs
343 have to be recompiled to work with the new kernel. This includes the
344 following libraries and programs, but the whole buildworld is
345 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
346 kdump, procstat, rwho, rwhod, uniq.
349 AES-NI intrinsic support has been added to gcc. The AES-NI module
350 has been updated to use this support. A new gcc is required to build
351 the aesni module on both i386 and amd64.
354 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
355 Thus "device padlock_rng" and "device rdrand_rng" should be
356 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
359 WITH_ICONV has been split into two feature sets. WITH_ICONV now
360 enables just the iconv* functionality and is now on by default.
361 WITH_LIBICONV_COMPAT enables the libiconv api and link time
362 compatability. Set WITHOUT_ICONV to build the old way.
363 If you have been using WITH_ICONV before, you will very likely
364 need to turn on WITH_LIBICONV_COMPAT.
367 INVARIANTS option now enables DEBUG for code with OpenSolaris and
368 Illumos origin, including ZFS. If you have INVARIANTS in your
369 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
371 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
372 locks if WITNESS option was set. Because that generated a lot of
373 witness(9) reports and all of them were believed to be false
374 positives, this is no longer done. New option OPENSOLARIS_WITNESS
375 can be used to achieve the previous behavior.
378 Timer values in IPv6 data structures now use time_uptime instead
379 of time_second. Although this is not a user-visible functional
380 change, userland utilities which directly use them---ndp(8),
381 rtadvd(8), and rtsold(8) in the base system---need to be updated
385 find -delete can now delete the pathnames given as arguments,
386 instead of only files found below them or if the pathname did
387 not contain any slashes. Formerly, the following error message
390 find: -delete: <path>: relative path potentially not safe
392 Deleting the pathnames given as arguments can be prevented
393 without error messages using -mindepth 1 or by changing
394 directory and passing "." as argument to find. This works in the
395 old as well as the new version of find.
398 Behavior of devfs rules path matching has been changed.
399 Pattern is now always matched against fully qualified devfs
400 path and slash characters must be explicitly matched by
401 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
402 subdirectories must be reviewed.
405 The default ARM ABI has changed to the ARM EABI. The old ABI is
406 incompatible with the ARM EABI and all programs and modules will
407 need to be rebuilt to work with a new kernel.
409 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
411 NOTE: Support for the old ABI will be removed in the future and
412 users are advised to upgrade.
415 pkg_install has been disconnected from the build if you really need it
416 you should add WITH_PKGTOOLS in your src.conf(5).
419 Most of network statistics structures were changed to be able
420 keep 64-bits counters. Thus all tools, that work with networking
421 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
424 Fix a bug that allowed a tracing process (e.g. gdb) to write
425 to a memory-mapped file in the traced process's address space
426 even if neither the traced process nor the tracing process had
427 write access to that file.
430 CVS has been removed from the base system. An exact copy
431 of the code is available from the devel/cvs port.
434 Some people report the following error after the switch to bmake:
436 make: illegal option -- J
437 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
439 *** [buildworld] Error code 2
441 this likely due to an old instance of make in
442 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
443 which src/Makefile will use that blindly, if it exists, so if
444 you see the above error:
446 rm -rf `make -V MAKEPATH`
451 Use bmake by default.
452 Whereas before one could choose to build with bmake via
453 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
454 make. The goal is to remove these knobs for 10-RELEASE.
456 It is worth noting that bmake (like gmake) treats the command
457 line as the unit of failure, rather than statements within the
458 command line. Thus '(cd some/where && dosomething)' is safer
459 than 'cd some/where; dosomething'. The '()' allows consistent
460 behavior in parallel build.
463 Fix a bug that allows NFS clients to issue READDIR on files.
466 The WITHOUT_IDEA option has been removed because
467 the IDEA patent expired.
470 The sysctl which controls TRIM support under ZFS has been renamed
471 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
475 The mergemaster command now uses the default MAKEOBJDIRPREFIX
476 rather than creating it's own in the temporary directory in
477 order allow access to bootstrapped versions of tools such as
478 install and mtree. When upgrading from version of FreeBSD where
479 the install command does not support -l, you will need to
480 install a new mergemaster command if mergemaster -p is required.
481 This can be accomplished with the command (cd src/usr.sbin/mergemaster
485 Legacy ATA stack, disabled and replaced by new CAM-based one since
486 FreeBSD 9.0, completely removed from the sources. Kernel modules
487 atadisk and atapi*, user-level tools atacontrol and burncd are
488 removed. Kernel option `options ATA_CAM` is now permanently enabled
492 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
493 and socketpair(2). Software, in particular Kerberos, may
494 automatically detect and use these during building. The resulting
495 binaries will not work on older kernels.
498 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
499 information, see the respective 20130304 entry).
502 Recent commits to callout(9) changed the size of struct callout,
503 so the KBI is probably heavily disturbed. Also, some functions
504 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
505 by macros. Every kernel module using it won't load, so rebuild
508 The ctl device has been re-enabled in GENERIC for i386 and amd64,
509 but does not initialize by default (because of the new CTL_DISABLE
510 option) to save memory. To re-enable it, remove the CTL_DISABLE
511 option from the kernel config file or set kern.cam.ctl.disable=0
512 in /boot/loader.conf.
515 The ctl device has been disabled in GENERIC for i386 and amd64.
516 This was done due to the extra memory being allocated at system
517 initialisation time by the ctl driver which was only used if
518 a CAM target device was created. This makes a FreeBSD system
519 unusable on 128MB or less of RAM.
522 A new compression method (lz4) has been merged to -HEAD. Please
523 refer to zpool-features(7) for more information.
525 Please refer to the "ZFS notes" section of this file for information
526 on upgrading boot ZFS pools.
529 A BSD-licensed patch(1) variant has been added and is installed
530 as bsdpatch, being the GNU version the default patch.
531 To inverse the logic and use the BSD-licensed one as default,
532 while having the GNU version installed as gnupatch, rebuild
533 and install world with the WITH_BSD_PATCH knob set.
536 Due to the use of the new -l option to install(1) during build
537 and install, you must take care not to directly set the INSTALL
538 make variable in your /etc/make.conf, /etc/src.conf, or on the
539 command line. If you wish to use the -C flag for all installs
540 you may be able to add INSTALL+=-C to /etc/make.conf or
544 The install(1) option -M has changed meaning and now takes an
545 argument that is a file or path to append logs to. In the
546 unlikely event that -M was the last option on the command line
547 and the command line contained at least two files and a target
548 directory the first file will have logs appended to it. The -M
549 option served little practical purpose in the last decade so its
550 use is expected to be extremely rare.
553 After switching to Clang as the default compiler some users of ZFS
554 on i386 systems started to experience stack overflow kernel panics.
555 Please consider using 'options KSTACK_PAGES=4' in such configurations.
558 GEOM_LABEL now mangles label names read from file system metadata.
559 Mangling affect labels containing spaces, non-printable characters,
560 '%' or '"'. Device names in /etc/fstab and other places may need to
564 By default, only the 10 most recent kernel dumps will be saved. To
565 restore the previous behaviour (no limit on the number of kernel dumps
566 stored in the dump directory) add the following line to /etc/rc.conf:
571 With the addition of auditdistd(8), a new auditdistd user is now
572 required during installworld. "mergemaster -p" can be used to
573 add the user prior to installworld, as documented in the handbook.
576 The sin6_scope_id member variable in struct sockaddr_in6 is now
577 filled by the kernel before passing the structure to the userland via
578 sysctl or routing socket. This means the KAME-specific embedded scope
579 id in sin6_addr.s6_addr[2] is always cleared in userland application.
580 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
581 __FreeBSD_version is bumped to 1000025.
584 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
585 This means that the world and kernel will be compiled with clang
586 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
587 and /usr/bin/cpp. To disable this behavior and revert to building
588 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
589 of current may need to bootstrap WITHOUT_CLANG first if the clang
590 build fails (its compatibility window doesn't extend to the 9 stable
594 The IPFIREWALL_FORWARD kernel option has been removed. Its
595 functionality now turned on by default.
598 The ZERO_COPY_SOCKET kernel option has been removed and
599 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
600 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
601 mechanism which is not safe and may result in kernel crashes.
602 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
603 driver supports disposeable external page sized mbuf storage.
604 Proper replacements for both zero-copy mechanisms are under
605 consideration and will eventually lead to complete removal
606 of the two kernel options.
609 The IPv4 network stack has been converted to network byte
610 order. The following modules need to be recompiled together
611 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
612 pf(4), ipfw(4), ng_ipfw(4), stf(4).
615 Support for non-MPSAFE filesystems was removed from VFS. The
616 VFS_VERSION was bumped, all filesystem modules shall be
620 All the non-MPSAFE filesystems have been disconnected from
621 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
622 portalfs, smbfs, xfs.
625 The interface cloning API and ABI has changed. The following
626 modules need to be recompiled together with kernel:
627 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
628 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
629 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
632 The sdhci driver was split in two parts: sdhci (generic SD Host
633 Controller logic) and sdhci_pci (actual hardware driver).
634 No kernel config modifications are required, but if you
635 load sdhc as a module you must switch to sdhci_pci instead.
638 Import the FUSE kernel and userland support into base system.
641 The GNU sort(1) program has been removed since the BSD-licensed
642 sort(1) has been the default for quite some time and no serious
643 problems have been reported. The corresponding WITH_GNU_SORT
647 The pfil(9) API/ABI for AF_INET family has been changed. Packet
648 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
652 The net80211(4) ABI has been changed to allow for improved driver
653 PS-POLL and power-save support. All wireless drivers need to be
654 recompiled to work with the new kernel.
657 The random(4) support for the VIA hardware random number
658 generator (`PADLOCK') is no longer enabled unconditionally.
659 Add the padlock_rng device in the custom kernel config if
660 needed. The GENERIC kernels on i386 and amd64 do include the
661 device, so the change only affects the custom kernel
665 The pf(4) packet filter ABI has been changed. pfctl(8) and
666 snmp_pf module need to be recompiled to work with new kernel.
669 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
670 to -HEAD. Pools that have empty_bpobj in active state can not be
671 imported read-write with ZFS implementations that do not support
672 this feature. For more information read the zpool-features(5)
676 The sparc64 ZFS loader has been changed to no longer try to auto-
677 detect ZFS providers based on diskN aliases but now requires these
678 to be explicitly listed in the OFW boot-device environment variable.
681 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
682 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
683 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
686 The following sysctls and tunables have been renamed for consistency
687 with other variables:
688 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
689 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
692 The sort utility has been replaced with BSD sort. For now, GNU sort
693 is also available as "gnusort" or the default can be set back to
694 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
695 installed as "bsdsort".
698 A new version of ZFS (pool version 5000) has been merged to -HEAD.
699 Starting with this version the old system of ZFS pool versioning
700 is superseded by "feature flags". This concept enables forward
701 compatibility against certain future changes in functionality of ZFS
702 pools. The first read-only compatible "feature flag" for ZFS pools
703 is named "com.delphix:async_destroy". For more information
704 read the new zpool-features(5) manual page.
705 Please refer to the "ZFS notes" section of this file for information
706 on upgrading boot ZFS pools.
709 The malloc(3) implementation embedded in libc now uses sources imported
710 as contrib/jemalloc. The most disruptive API change is to
711 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
712 delete it prior to installworld, and optionally re-create it using the
713 new format after rebooting. See malloc.conf(5) for details
714 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
718 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
719 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
720 now spelled mips. This is to aid compatibility with third-party
721 software that expects this naming scheme in uname(3). Little-endian
722 settings are unchanged. If you are updating a big-endian mips64 machine
723 from before this change, you may need to set MACHINE_ARCH=mips64 in
724 your environment before the new build system will recognize your machine.
727 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
731 Now unix domain sockets behave "as expected" on nullfs(5). Previously
732 nullfs(5) did not pass through all behaviours to the underlying layer,
733 as a result if we bound to a socket on the lower layer we could connect
734 only to the lower path; if we bound to the upper layer we could connect
735 only to the upper path. The new behavior is one can connect to both the
736 lower and the upper paths regardless what layer path one binds to.
739 The getifaddrs upgrade path broken with 20111215 has been restored.
740 If you have upgraded in between 20111215 and 20120209 you need to
741 recompile libc again with your kernel. You still need to recompile
742 world to be able to configure CARP but this restriction already
746 The set_rcvar() function has been removed from /etc/rc.subr. All
747 base and ports rc.d scripts have been updated, so if you have a
748 port installed with a script in /usr/local/etc/rc.d you can either
749 hand-edit the rcvar= line, or reinstall the port.
751 An easy way to handle the mass-update of /etc/rc.d:
752 rm /etc/rc.d/* && mergemaster -i
755 panic(9) now stops other CPUs in the SMP systems, disables interrupts
756 on the current CPU and prevents other threads from running.
757 This behavior can be reverted using the kern.stop_scheduler_on_panic
759 The new behavior can be incompatible with kern.sync_on_panic.
762 The carp(4) facility has been changed significantly. Configuration
763 of the CARP protocol via ifconfig(8) has changed, as well as format
764 of CARP events submitted to devd(8) has changed. See manual pages
765 for more information. The arpbalance feature of carp(4) is currently
766 not supported anymore.
768 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
769 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
770 need to be recompiled.
773 The acpi_wmi(4) status device /dev/wmistat has been renamed to
777 The option VFS_ALLOW_NONMPSAFE option has been added in order to
778 explicitely support non-MPSAFE filesystems.
779 It is on by default for all supported platform at this present
783 The broken amd(4) driver has been replaced with esp(4) in the amd64,
784 i386 and pc98 GENERIC kernel configuration files.
787 sysinstall has been removed
790 The stable/9 branch created in subversion. This corresponds to the
791 RELENG_9 branch in CVS.
794 This commit modifies vfs_register() so that it uses a hash
795 calculation to set vfc_typenum, which is enabled by default.
796 The first time a system is booted after this change, the
797 vfc_typenum values will change for all file systems. The
798 main effect of this is a change to the NFS server file handles
799 for file systems that use vfc_typenum in their fsid, such as ZFS.
800 It will, however, prevent vfc_typenum from changing when file
801 systems are loaded in a different order for subsequent reboots.
802 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
803 until you are ready to remount all NFS clients after a reboot.
806 Bump the shared library version numbers for libraries that
807 do not use symbol versioning, have changed the ABI compared
808 to stable/8 and which shared library version was not bumped.
809 Done as part of 9.0-RELEASE cycle.
812 During the merge of Capsicum features, the fget(9) KPI was modified.
813 This may require the rebuilding of out-of-tree device drivers --
814 issues have been reported specifically with the nVidia device driver.
815 __FreeBSD_version is bumped to 900041.
817 Also, there is a period between 20110811 and 20110814 where the
818 special devices /dev/{stdin,stdout,stderr} did not work correctly.
819 Building world from a kernel during that window may not work.
822 The packet filter (pf) code has been updated to OpenBSD 4.5.
823 You need to update userland tools to be in sync with kernel.
824 This update breaks backward compatibility with earlier pfsync(4)
825 versions. Care must be taken when updating redundant firewall setups.
828 The following sysctls and tunables are retired on x86 platforms:
830 machdep.hlt_logical_cpus
831 The following sysctl is retired:
832 machdep.hyperthreading_allowed
833 The sysctls were supposed to provide a way to dynamically offline and
834 online selected CPUs on x86 platforms, but the implementation has not
835 been reliable especially with SCHED_ULE scheduler.
836 machdep.hyperthreading_allowed tunable is still available to ignore
837 hyperthreading CPUs at OS level.
838 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
839 where X is an APIC ID of a CPU. Be advised, though, that disabling
840 CPUs in non-uniform fashion will result in non-uniform topology and
841 may lead to sub-optimal system performance with SCHED_ULE, which is
845 cpumask_t type is retired and cpuset_t is used in order to describe
849 Changes to ifconfig(8) for dynamic address family detection mandate
850 that you are running a kernel of 20110525 or later. Make sure to
851 follow the update procedure to boot a new kernel before installing
855 Support for sun4v architecture is officially dropped
858 Several KPI breaking changes have been committed to the mii(4) layer,
859 the PHY drivers and consequently some Ethernet drivers using mii(4).
860 This means that miibus.ko and the modules of the affected Ethernet
861 drivers need to be recompiled.
863 Note to kernel developers: Given that the OUI bit reversion problem
864 was fixed as part of these changes all mii(4) commits related to OUIs,
865 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
866 handling, no longer can be merged verbatim to stable/8 and previous
870 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
871 into their kernel configurations along with 'device pci'.
874 The default NFS client is now the new NFS client, so fstype "newnfs"
875 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
876 Although mounts via fstype "nfs" will usually work without userland
877 changes, it is recommended that the mount(8) and mount_nfs(8)
878 commands be rebuilt from sources and that a link to mount_nfs called
879 mount_oldnfs be created. The new client is compiled into the
880 kernel with "options NFSCL" and this is needed for diskless root
881 file systems. The GENERIC kernel configs have been changed to use
882 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
883 To use the regular/old client, you can "mount -t oldnfs ...". For
884 a diskless root file system, you must also include a line like:
886 vfs.root.mountfrom="oldnfs:"
888 in the boot/loader.conf on the root fs on the NFS server to make
889 a diskless root fs use the old client.
892 The GENERIC kernels for all architectures now default to the new
893 CAM-based ATA stack. It means that all legacy ATA drivers were
894 removed and replaced by respective CAM drivers. If you are using
895 ATA device names in /etc/fstab or other places, make sure to update
896 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
897 where 'Y's are the sequential numbers starting from zero for each type
898 in order of detection, unless configured otherwise with tunables,
899 see cam(4)). There will be symbolic links created in /dev/ to map
900 old adX devices to the respective adaY. They should provide basic
901 compatibility for file systems mounting in most cases, but they do
902 not support old user-level APIs and do not have respective providers
903 in GEOM. Consider using updated management tools with new device names.
905 It is possible to load devices ahci, ata, siis and mvs as modules,
906 but option ATA_CAM should remain in kernel configuration to make ata
907 module work as CAM driver supporting legacy ATA controllers. Device ata
908 still can be used in modular fashion (atacore + ...). Modules atadisk
909 and atapi* are not used and won't affect operation in ATA_CAM mode.
910 Note that to use CAM-based ATA kernel should include CAM devices
911 scbus, pass, da (or explicitly ada), cd and optionally others. All of
912 them are parts of the cam module.
914 ataraid(4) functionality is now supported by the RAID GEOM class.
915 To use it you can load geom_raid kernel module and use graid(8) tool
916 for management. Instead of /dev/arX device names, use /dev/raid/rX.
918 No kernel config options or code have been removed, so if a problem
919 arises, please report it and optionally revert to the old ATA stack.
920 In order to do it you can remove from the kernel config:
925 , and instead add back:
926 device atadisk # ATA disk drives
927 device ataraid # ATA RAID drives
928 device atapicd # ATAPI CDROM drives
929 device atapifd # ATAPI floppy drives
930 device atapist # ATAPI tape drives
933 The default NFS server has been changed to the new server, which
934 was referred to as the experimental server. If you need to switch
935 back to the old NFS server, you must now put the "-o" option on
936 both the mountd and nfsd commands. This can be done using the
937 mountd_flags and nfs_server_flags rc.conf variables until an
938 update to the rc scripts is committed, which is coming soon.
941 The GNU Objective-C runtime library (libobjc), and other Objective-C
942 related components have been removed from the base system. If you
943 require an Objective-C library, please use one of the available ports.
946 ath(4) has been split into bus- and device- modules. if_ath contains
947 the HAL, the TX rate control and the network device code. if_ath_pci
948 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
949 contains the AHB glue. Users need to load both if_ath_pci and if_ath
950 in order to use ath on everything else.
952 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
953 need to load if_ath and if_ath_pci for ath(4) operation.
956 As part of the replacement of sysinstall, the process of building
957 release media has changed significantly. For details, please re-read
958 release(7), which has been updated to reflect the new build process.
961 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
962 is the last available version under GPLv2. It brings a number of new
963 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
964 4.1 and SSE 4.2), better support for powerpc64, a number of new
965 directives, and lots of other small improvements. See the ChangeLog
966 file in contrib/binutils for the full details.
969 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
970 compliant, and will now use half of hash for authentication.
971 This will break interoperability with all stacks (including all
972 actual FreeBSD versions) who implement
973 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
975 The only workaround with such peers is to use another HMAC
976 algorithm for IPsec ("phase 2") authentication.
979 Remove the uio_yield prototype and symbol. This function has
980 been misnamed since it was introduced and should not be
981 globally exposed with this name. The equivalent functionality
982 is now available using kern_yield(curthread->td_user_pri).
983 The function remains undocumented.
986 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
987 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
988 for scalar sysctls is defined but disabled. Code that needs
989 UQUAD to pass the type checking that must compile on older
990 systems where the define is not present can check against
991 __FreeBSD_version >= 900030.
993 The system dialog(1) has been replaced with a new version previously
994 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
995 with the previous version, but the libdialog associated with it has
996 a largely incompatible API. As such, the original version of libdialog
997 will be kept temporarily as libodialog, until its base system consumers
998 are replaced or updated. Bump __FreeBSD_version to 900030.
1001 If you are trying to run make universe on a -stable system, and you get
1002 the following warning:
1003 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1004 unknown. config(8) likely too old."
1005 or something similar to it, then you must upgrade your -stable system
1006 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1007 stable/8) or build the config from the latest stable/8 branch and
1008 install it on your system.
1010 Prior to this date, building a current universe on 8-stable system from
1011 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1012 error in the first kernel build phase. A new config on those old
1013 systems will fix that problem for older versions of -current.
1016 The TCP stack has been modified to allow Khelp modules to interact with
1017 it via helper hook points and store per-connection data in the TCP
1018 control block. Bump __FreeBSD_version to 900029. User space tools that
1019 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1023 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1024 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1025 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1026 to take advantage of it instead of using custom implementations. This
1027 means that these drivers now no longer unconditionally advertise
1028 support for flow control but only do so if flow control is a selected
1029 media option. This was implemented in the generic support that way in
1030 order to allow flow control to be switched on and off via ifconfig(8)
1031 with the PHY specific default to typically off in order to protect
1032 from unwanted effects. Consequently, if you used flow control with
1033 one of the above mentioned drivers you now need to explicitly enable
1034 it, for example via:
1035 ifconfig bge0 media auto mediaopt flowcontrol
1037 Along with the above mentioned changes generic support for setting
1038 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1039 e1000phy(4) as well as ip1000phy(4) have been converted to take
1040 advantage of it. This means that these drivers now no longer take the
1041 link0 parameter for selecting master mode but the master media option
1042 has to be used instead, for example like in the following:
1043 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1045 Selection of master mode now is also available with all other PHY
1046 drivers supporting 1000baseT.
1049 The TCP stack has received a significant update to add support for
1050 modularised congestion control and generally improve the clarity of
1051 congestion control decisions. Bump __FreeBSD_version to 900025. User
1052 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1053 sockstat) need to be recompiled.
1056 The man(1) utility has been replaced by a new version that no longer
1057 uses /etc/manpath.config. Please consult man.conf(5) for how to
1058 migrate local entries to the new format.
1061 The copyright strings printed by login(1) and sshd(8) at the time of a
1062 new connection have been removed to follow other operating systems and
1066 A workaround for a fixed ld bug has been removed in kernel code,
1067 so make sure that your system ld is built from sources after
1068 revision 210245 from 2010-07-19 (r211583 if building head kernel
1069 on stable/8, r211584 for stable/7; both from 2010-08-21).
1070 A symptom of incorrect ld version is different addresses for
1071 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1074 The $ipv6_prefer variable in rc.conf(5) has been split into
1075 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1077 The $ip6addrctl_policy is a variable to choose a pre-defined
1078 address selection policy set by ip6addrctl(8). A value
1079 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1082 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1083 flag (see an entry of 20090926) is set on an interface with no
1084 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1085 security reason. If you want IPv6 link-local address on all
1086 interfaces by default, set this to "YES".
1088 The old ipv6_prefer="YES" is equivalent to
1089 ipv6_activate_all_interfaces="YES" and
1090 ip6addrctl_policy="ipv6_prefer".
1093 DTrace has grown support for userland tracing. Due to this, DTrace is
1094 now i386 and amd64 only.
1095 dtruss(1) is now installed by default on those systems and a new
1096 kernel module is needed for userland tracing: fasttrap.
1097 No changes to your kernel config file are necessary to enable
1098 userland tracing, but you might consider adding 'STRIP=' and
1099 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1100 to have informative userland stack traces in DTrace (ustack).
1103 The acpi_aiboost(4) driver has been removed in favor of the new
1104 aibs(4) driver. You should update your kernel configuration file.
1107 BSD grep has been imported to the base system and it is built by
1108 default. It is completely BSD licensed, highly GNU-compatible, uses
1109 less memory than its GNU counterpart and has a small codebase.
1110 However, it is slower than its GNU counterpart, which is mostly
1111 noticeable for larger searches, for smaller ones it is measurable
1112 but not significant. The reason is complex, the most important factor
1113 is that we lack a modern and efficient regex library and GNU
1114 overcomes this by optimizing the searches internally. Future work
1115 on improving the regex performance is planned, for the meantime,
1116 users that need better performance, can build GNU grep instead by
1117 setting the WITH_GNU_GREP knob.
1120 Due to the import of powerpc64 support, all existing powerpc kernel
1121 configuration files must be updated with a machine directive like this:
1122 machine powerpc powerpc
1124 In addition, an updated config(8) is required to build powerpc kernels
1128 A new version of ZFS (version 15) has been merged to -HEAD.
1129 This version uses a python library for the following subcommands:
1130 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1131 For full functionality of these commands the following port must
1132 be installed: sysutils/py-zfs
1135 'vm_page's are now hashed by physical address to an array of mutexes.
1136 Currently this is only used to serialize access to hold_count. Over
1137 time the page queue mutex will be peeled away. This changes the size
1138 of pmap on every architecture. And requires all callers of vm_page_hold
1139 and vm_page_unhold to be updated.
1142 WITH_CTF can now be specified in src.conf (not recommended, there
1143 are some problems with static executables), make.conf (would also
1144 affect ports which do not use GNU make and do not override the
1145 compile targets) or in the kernel config (via "makeoptions
1147 When WITH_CTF was specified there before this was silently ignored,
1148 so make sure that WITH_CTF is not used in places which could lead
1149 to unwanted behavior.
1152 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1153 to allow 32-bit compatibility on non-x86 platforms. All kernel
1154 configurations on amd64 and ia64 platforms using these options must
1155 be modified accordingly.
1158 The utmp user accounting database has been replaced with utmpx,
1159 the user accounting interface standardized by POSIX.
1160 Unfortunately the semantics of utmp and utmpx don't match,
1161 making it practically impossible to support both interfaces.
1162 The user accounting database is used by tools like finger(1),
1163 last(1), talk(1), w(1) and ac(8).
1165 All applications in the base system use utmpx. This means only
1166 local binaries (e.g. from the ports tree) may still use these
1167 utmp database files. These applications must be rebuilt to make
1170 After the system has been upgraded, it is safe to remove the old
1171 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1172 assuming their contents is of no importance anymore. Old wtmp
1173 databases can only be used by last(1) and ac(8) after they have
1174 been converted to the new format using wtmpcvt(1).
1177 Introduce the kernel thread "deadlock resolver" (which can be enabled
1178 via the DEADLKRES option, see NOTES for more details) and the
1179 sleepq_type() function for sleepqueues.
1182 The rc.firewall and rc.firewall6 were unified, and
1183 rc.firewall6 and rc.d/ip6fw were removed.
1184 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1185 variables are obsoleted. Instead, the following new rc
1186 variables are added to rc.d/ipfw:
1188 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1189 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1190 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1192 The meanings correspond to the relevant IPv4 variables.
1198 The default terminal emulation for syscons(4) has been changed
1199 from cons25 to xterm on all platforms except pc98. This means
1200 that the /etc/ttys file needs to be updated to ensure correct
1201 operation of applications on the console.
1203 The terminal emulation style can be toggled per window by using
1204 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1205 options can be used to change the compile-time default back to
1208 To prevent graphical artifacts, make sure the TERM environment
1209 variable is set to match the terminal emulation that is being
1210 performed by syscons(4).
1213 The layout of the structure ieee80211req_scan_result has changed.
1214 Applications that require wireless scan results (e.g. ifconfig(8))
1215 from net80211 need to be recompiled.
1217 Applications such as wpa_supplicant(8) may require a full world
1218 build without using NO_CLEAN in order to get synchronized with the
1222 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1223 There's one kernel module for each firmware. Adding "device iwnfw"
1224 to the kernel configuration file means including all three firmware
1225 images inside the kernel. If you want to include just the one for
1226 your wireless card, use the devices iwn4965fw, iwn5000fw or
1230 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1231 into rc.d/netif. The changes are the following:
1233 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1234 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1235 Note that both variables need the "inet6" keyword at the head.
1237 Do not set $ipv6_network_interfaces manually if you do not
1238 understand what you are doing. It is not needed in most cases.
1240 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1243 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1244 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1246 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1247 all configured interfaces have "inet6 accept_rtadv" in the
1248 $ifconfig_IF_ipv6. These are for backward compatibility.
1250 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1251 functionality of interfaces with no corresponding
1252 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1253 and the default address selection policy of ip6addrctl(8)
1254 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1255 Note that if you want to configure IPv6 functionality on the
1256 disabled interfaces after boot, first you need to clear the flag by
1257 using ifconfig(8) like:
1259 ifconfig em0 inet6 -ifdisabled
1261 If YES, the default address selection policy is set as
1264 The default value of $ipv6_prefer is NO.
1266 4. If your system need to receive Router Advertisement messages,
1267 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1268 scripts automatically invoke rtsol(8) when the interface becomes
1269 UP. The Router Advertisement messages are used for SLAAC
1270 (State-Less Address AutoConfiguration).
1273 802.11s D3.03 support was committed. This is incompatible with the
1274 previous code, which was based on D3.0.
1277 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1278 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1279 control whether accepting Router Advertisement messages or not.
1280 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1281 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1282 The ifconfig(8) utility now supports these flags.
1285 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1286 mount(8) and -a option for df(1) to see them.
1289 The old tunable hw.bus.devctl_disable has been superseded by
1290 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1291 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1295 Remove the option STOP_NMI. The default action is now to use NMI only
1296 for KDB via the newly introduced function stop_cpus_hard() and
1297 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1300 The stable/8 branch created in subversion. This corresponds to the
1301 RELENG_8 branch in CVS.
1304 Bump the shared library version numbers for all libraries that do not
1305 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1306 __FreeBSD_version to 800105.
1309 Due to changes in the implementation of virtual network stack support,
1310 all network-related kernel modules must be recompiled. As this change
1311 breaks the ABI, bump __FreeBSD_version to 800104.
1314 The TOE interface to the TCP syncache has been modified to remove
1315 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1316 The cxgb driver is the only TOE consumer affected by this change, and
1317 needs to be recompiled along with the kernel. As this change breaks
1318 the ABI, bump __FreeBSD_version to 800103.
1321 Padding has been added to struct tcpcb, sackhint and tcpstat in
1322 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1323 maintaining the ABI. However, this change breaks the ABI, so bump
1324 __FreeBSD_version to 800102. User space tools that rely on the size of
1325 any of these structs (e.g. sockstat) need to be recompiled.
1328 The NFS_LEGACYRPC option has been removed along with the old kernel
1329 RPC implementation that this option selected. Kernel configurations
1330 may need to be adjusted.
1333 The network interface device nodes at /dev/net/<interface> have been
1334 removed. All ioctl operations can be performed the normal way using
1335 routing sockets. The kqueue functionality can generally be replaced
1336 with routing sockets.
1339 The documentation from the FreeBSD Documentation Project (Handbook,
1340 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1341 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1344 The ABI of various structures related to the SYSV IPC API have been
1345 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1346 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1350 Layout of struct vnet has changed as routing related variables were
1351 moved to their own Vimage module. Modules need to be recompiled. Bump
1352 __FreeBSD_version to 800099.
1355 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1356 respectively. As long as no more than 16 groups per process are used,
1357 no changes should be visible. When more than 16 groups are used, old
1358 binaries may fail if they call getgroups() or getgrouplist() with
1359 statically sized storage. Recompiling will work around this, but
1360 applications should be modified to use dynamically allocated storage
1361 for group arrays as POSIX.1-2008 does not cap an implementation's
1362 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1364 NFS and portalfs mounts may also be affected as the list of groups is
1365 truncated to 16. Users of NFS who use more than 16 groups, should
1366 take care that negative group permissions are not used on the exported
1367 file systems as they will not be reliable unless a GSSAPI based
1368 authentication method is used.
1371 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1372 option compiles in the support for adaptive spinning for lockmgrs
1373 which want to enable it. The lockinit() function now accepts the flag
1374 LK_ADAPTIVE in order to make the lock object subject to adaptive
1375 spinning when both held in write and read mode.
1378 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1379 changed. User applications that use this ioctl need to be rebuilt.
1382 The layout of struct thread has changed. Kernel and modules need to
1386 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1387 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1390 window(1) has been removed from the base system. It can now be
1391 installed from ports. The port is called misc/window.
1394 The way we are storing and accessing `routing table' entries has
1395 changed. Programs reading the FIB, like netstat, need to be
1399 A new netisr implementation has been added for FreeBSD 8. Network
1400 file system modules, such as igmp, ipdivert, and others, should be
1402 Bump __FreeBSD_version to 800096.
1405 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1409 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1410 Bump __FreeBSD_version to 800094.
1413 Add mnt_xflag field to 'struct mount'. File system modules need to be
1415 Bump __FreeBSD_version to 800093.
1418 The compiling option ADAPTIVE_SX has been retired while it has been
1419 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1420 The KPI for sx_init_flags() changes as accepting flags:
1421 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1422 been introduced in order to handle the reversed logic.
1423 Bump __FreeBSD_version to 800092.
1426 Add support for hierarchical jails. Remove global securelevel.
1427 Bump __FreeBSD_version to 800091.
1430 The layout of struct vnet_net has changed, therefore modules
1432 Bump __FreeBSD_version to 800090.
1435 The newly imported zic(8) produces a new format in the output. Please
1436 run tzsetup(8) to install the newly created data to /etc/localtime.
1439 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1440 hw.usb.* and is now consistent again with previous releases.
1443 802.11 monitor mode support was revised and driver api's were changed.
1444 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1445 of DLT_IEEE802_11. No user-visible data structures were changed but
1446 applications that use DLT_IEEE802_11 may require changes.
1447 Bump __FreeBSD_version to 800088.
1450 The layout of the following structs has changed: sysctl_oid,
1451 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1452 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1453 panics may be experienced. World rebuild is required for
1454 correctly checking networking state from userland.
1455 Bump __FreeBSD_version to 800085.
1458 MLDv2 and Source-Specific Multicast (SSM) have been merged
1459 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1460 The implementation of SSM within FreeBSD's IPv6 stack closely
1461 follows the IPv4 implementation.
1463 For kernel developers:
1465 * The most important changes are that the ip6_output() and
1466 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1467 and this lock has been downgraded to a non-recursive mutex.
1469 * As with the changes to the IPv4 stack to support SSM, filtering
1470 of inbound multicast traffic must now be performed by transport
1471 protocols within the IPv6 stack. This does not apply to TCP and
1472 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1474 * The KPIs used by IPv6 multicast are similar to those used by
1475 the IPv4 stack, with the following differences:
1476 * im6o_mc_filter() is analogous to imo_multicast_filter().
1477 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1478 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1479 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1480 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1481 for MLDv1 have an additional 'timer' argument which is used to
1482 jitter the initial membership report for the solicited-node
1483 multicast membership on-link.
1484 * This is not strictly needed for MLDv2, which already jitters
1485 its report transmissions. However, the 'timer' argument is
1486 preserved in case MLDv1 is active on the interface.
1488 * The KAME linked-list based IPv6 membership implementation has
1489 been refactored to use a vector similar to that used by the IPv4
1491 Code which maintains a list of its own multicast memberships
1492 internally, e.g. carp, has been updated to reflect the new
1495 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1496 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1497 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1498 implementation constraint which needs to be addressed in HEAD.
1500 For application developers:
1502 * The changes are broadly similar to those made for the IPv4
1505 * The use of IPv4 and IPv6 multicast socket options on the same
1506 socket, using mapped addresses, HAS NOT been tested or supported.
1508 * There are a number of issues with the implementation of various
1509 IPv6 multicast APIs which need to be resolved in the API surface
1510 before the implementation is fully compatible with KAME userland
1511 use, and these are mostly to do with interface index treatment.
1513 * The literature available discusses the use of either the delta / ASM
1514 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1515 using setsourcefilter(3)/getsourcefilter(3). For more information
1516 please refer to RFC 3768, 'Socket Interface Extensions for
1517 Multicast Source Filters'.
1519 * Applications which use the published RFC 3678 APIs should be fine.
1521 For systems administrators:
1523 * The mtest(8) utility has been refactored to support IPv6, in
1524 addition to IPv4. Interface addresses are no longer accepted
1525 as arguments, their names must be used instead. The utility
1526 will map the interface name to its first IPv4 address as
1527 returned by getifaddrs(3).
1529 * The ifmcstat(8) utility has also been updated to print the MLDv2
1530 endpoint state and source filter lists via sysctl(3).
1532 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1533 loopback of IPv6 multicast datagrams by default; it defaults to 1
1534 to preserve the existing behaviour. Disabling multicast loopback is
1535 recommended for optimal system performance.
1537 * The IPv6 MROUTING code has been changed to examine this sysctl
1538 instead of attempting to perform a group lookup before looping
1539 back forwarded datagrams.
1541 Bump __FreeBSD_version to 800084.
1544 Implement low-level Bluetooth HCI API.
1545 Bump __FreeBSD_version to 800083.
1548 The layout of struct malloc_type, used by modules to register new
1549 memory allocation types, has changed. Most modules will need to
1550 be rebuilt or panics may be experienced.
1551 Bump __FreeBSD_version to 800081.
1554 Anticipate overflowing inp_flags - add inp_flags2.
1555 This changes most offsets in inpcb, so checking v4 connection
1556 state will require a world rebuild.
1557 Bump __FreeBSD_version to 800080.
1560 Add an llentry to struct route and struct route_in6. Modules
1561 embedding a struct route will need to be recompiled.
1562 Bump __FreeBSD_version to 800079.
1565 The size of rt_metrics_lite and by extension rtentry has changed.
1566 Networking administration apps will need to be recompiled.
1567 The route command now supports show as an alias for get, weighting
1568 of routes, sticky and nostick flags to alter the behavior of stateful
1570 Bump __FreeBSD_version to 800078.
1573 Do not use Giant for kbdmux(4) locking. This is wrong and
1574 apparently causing more problems than it solves. This will
1575 re-open the issue where interrupt handlers may race with
1576 kbdmux(4) in polling mode. Typical symptoms include (but
1577 not limited to) duplicated and/or missing characters when
1578 low level console functions (such as gets) are used while
1579 interrupts are enabled (for example geli password prompt,
1580 mountroot prompt etc.). Disabling kbdmux(4) may help.
1583 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1584 kernel modules referencing any of the above need to be recompiled.
1585 Bump __FreeBSD_version to 800075.
1588 GEOM_PART has become the default partition slicer for storage devices,
1589 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1590 introduces some changes:
1592 MSDOS/EBR: the devices created from MSDOS extended partition entries
1593 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1594 to devices with offset-based names. fstabs may need to be modified.
1596 BSD: the "geometry does not match label" warning is harmless in most
1597 cases but it points to problems in file system misalignment with
1598 disk geometry. The "c" partition is now implicit, covers the whole
1599 top-level drive and cannot be (mis)used by users.
1601 General: Kernel dumps are now not allowed to be written to devices
1602 whose partition types indicate they are meant to be used for file
1603 systems (or, in case of MSDOS partitions, as something else than
1606 Most of these changes date approximately from 200812.
1609 The uscanner(4) driver has been removed from the kernel. This follows
1610 Linux removing theirs in 2.6 and making libusb the default interface
1611 (supported by sane).
1614 The multicast forwarding code has been cleaned up. netstat(1)
1615 only relies on KVM now for printing bandwidth upcall meters.
1616 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1617 ip6_mroute_mod respectively. The config(5) options for statically
1618 compiling this code remain the same, i.e. 'options MROUTING'.
1621 Support for the IFF_NEEDSGIANT network interface flag has been
1622 removed, which means that non-MPSAFE network device drivers are no
1623 longer supported. In particular, if_ar, if_sr, and network device
1624 drivers from the old (legacy) USB stack can no longer be built or
1628 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1629 a bunch of new language catalog files have also been added.
1630 This means that some common libc messages are now localized and
1631 they depend on the LC_MESSAGES environmental variable.
1634 The k8temp(4) driver has been renamed to amdtemp(4) since
1635 support for Family 10 and Family 11 CPU families was added.
1638 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1639 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1641 For kernel developers, the most important changes are that the
1642 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1643 and this lock has been downgraded to a non-recursive mutex.
1645 Transport protocols (UDP, Raw IP) are now responsible for filtering
1646 inbound multicast traffic according to group membership and source
1647 filters. The imo_multicast_filter() KPI exists for this purpose.
1648 Transports which do not use multicast (SCTP, TCP) already reject
1649 multicast by default. Forwarding and receive performance may improve
1650 as a mutex acquisition is no longer needed in the ip_input()
1651 low-level input path. in_addmulti() and in_delmulti() are shimmed
1652 to new KPIs which exist to support SSM in-kernel.
1654 For application developers, it is recommended that loopback of
1655 multicast datagrams be disabled for best performance, as this
1656 will still cause the lock to be taken for each looped-back
1657 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1658 be tuned to 0 to disable loopback by default; it defaults to 1
1659 to preserve the existing behaviour.
1661 For systems administrators, to obtain best performance with
1662 multicast reception and multiple groups, it is always recommended
1663 that a card with a suitably precise hash filter is used. Hash
1664 collisions will still result in the lock being taken within the
1665 transport protocol input path to check group membership.
1667 If deploying FreeBSD in an environment with IGMP snooping switches,
1668 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1669 enabled; this forces 224.0.0.0/24 group membership to be announced
1672 The size of 'struct igmpstat' has changed; netstat needs to be
1673 recompiled to reflect this.
1674 Bump __FreeBSD_version to 800070.
1677 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1678 updated to use it. This requires a buildworld/installworld in order to
1679 update the library and dependencies (usbconfig, etc). Its advisable to
1680 rebuild all ports which uses libusb. More specific directions are given
1681 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1682 libusb are no longer required and can be removed.
1685 A workaround is committed to allow the creation of System V shared
1686 memory segment of size > 2 GB on the 64-bit architectures.
1687 Due to a limitation of the existing ABI, the shm_segsz member
1688 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1689 wrong for large segments. Note that limits must be explicitly
1690 raised to allow such segments to be created.
1693 The layout of struct ifnet has changed, requiring a rebuild of all
1694 network device driver modules.
1697 The /dev handling for the new USB stack has changed, a
1698 buildworld/installworld is required for libusb20.
1701 The new USB2 stack has now been permanently moved in and all kernel and
1702 module names reverted to their previous values (eg, usb, ehci, ohci,
1703 ums, ...). The old usb stack can be compiled in by prefixing the name
1704 with the letter 'o', the old usb modules have been removed.
1705 Updating entry 20090216 for xorg and 20090215 for libmap may still
1709 The rc.conf(5) option if_up_delay has been renamed to
1710 defaultroute_delay to better reflect its purpose. If you have
1711 customized this setting in /etc/rc.conf you need to update it to
1715 xorg 7.4 wants to configure its input devices via hald which does not
1716 yet work with USB2. If the keyboard/mouse does not work in xorg then
1718 Option "AllowEmptyInput" "off"
1719 to your ServerLayout section. This will cause X to use the configured
1720 kbd and mouse sections from your xorg.conf.
1723 The GENERIC kernels for all architectures now default to the new USB2
1724 stack. No kernel config options or code have been removed so if a
1725 problem arises please report it and optionally revert to the old USB
1726 stack. If you are loading USB kernel modules or have a custom kernel
1727 that includes GENERIC then ensure that usb names are also changed over,
1728 eg uftdi -> usb2_serial_ftdi.
1730 Older programs linked against the ports libusb 0.1 need to be
1731 redirected to the new stack's libusb20. /etc/libmap.conf can
1733 # Map old usb library to new one for usb2 stack
1734 libusb-0.1.so.8 libusb20.so.1
1737 All USB ethernet devices now attach as interfaces under the name ueN
1738 (eg. ue0). This is to provide a predictable name as vendors often
1739 change usb chipsets in a product without notice.
1742 The ichsmb(4) driver has been changed to require SMBus slave
1743 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1744 All of the other SMBus controller drivers require left-justified
1745 slave addresses, so this change makes all the drivers provide the
1749 INET6 statistics (struct ip6stat) was updated.
1750 netstat(1) needs to be recompiled.
1753 NTFS has been removed from GENERIC kernel on amd64 to match
1754 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1755 will load ntfs.ko module automatically when NTFS support is
1756 actually needed, unless ntfs.ko is not installed or security
1757 level prohibits loading kernel modules. If either is the case,
1758 "options NTFS" has to be added into kernel config.
1761 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1762 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1763 800061. User space tools that rely on the size of struct tcpcb in
1764 tcp_var.h (e.g. sockstat) need to be recompiled.
1767 ng_tty(4) module updated to match the new TTY subsystem.
1768 Due to API change, user-level applications must be updated.
1769 New API support added to mpd5 CVS and expected to be present
1770 in next mpd5.3 release.
1773 With __FreeBSD_version 800060 the makefs tool is part of
1774 the base system (it was a port).
1777 The afdata and ifnet locks have been changed from mutexes to
1778 rwlocks, network modules will need to be re-compiled.
1781 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1782 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1783 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1784 architecture and 40 bytes on 64-bit architecture. The userland
1785 applications "arp" and "ndp" have been updated accordingly.
1786 The output from "netstat -r" shows only routing entries and
1787 none of the L2 information.
1790 __FreeBSD_version 800057 marks the switchover from the
1791 binary ath hal to source code. Users must add the line:
1793 options AH_SUPPORT_AR5416
1795 to their kernel config files when specifying:
1799 The ath_hal module no longer exists; the code is now compiled
1800 together with the driver in the ath module. It is now
1801 possible to tailor chip support (i.e. reduce the set of chips
1802 and thereby the code size); consult ath_hal(4) for details.
1805 __FreeBSD_version 800054 adds memory barriers to
1806 <machine/atomic.h>, new interfaces to ifnet to facilitate
1807 multiple hardware transmit queues for cards that support
1808 them, and a lock-less ring-buffer implementation to
1809 enable drivers to more efficiently manage queueing of
1813 A new version of ZFS (version 13) has been merged to -HEAD.
1814 This version has zpool attribute "listsnapshots" off by
1815 default, which means "zfs list" does not show snapshots,
1816 and is the same as Solaris behavior.
1819 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1822 The uhci, ohci, ehci and slhci USB Host controller drivers have
1823 been put into separate modules. If you load the usb module
1824 separately through loader.conf you will need to load the
1825 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1826 controller add the following to loader.conf:
1832 The ABI used by the PMC toolset has changed. Please keep
1833 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1837 atapci kernel module now includes only generic PCI ATA
1838 driver. AHCI driver moved to ataahci kernel module.
1839 All vendor-specific code moved into separate kernel modules:
1840 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1841 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1842 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1843 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1846 The TTY subsystem of the kernel has been replaced by a new
1847 implementation, which provides better scalability and an
1848 improved driver model. Most common drivers have been migrated to
1849 the new TTY subsystem, while others have not. The following
1850 drivers have not yet been ported to the new TTY layer:
1853 cy, digi, rc, rp, sio
1859 ng_h4, ng_tty, ppp, sl, snp
1861 Adding these drivers to your kernel configuration file shall
1862 cause compilation to fail.
1865 ntpd has been upgraded to 4.2.4p5.
1868 OpenSSH has been upgraded to 5.1p1.
1870 For many years, FreeBSD's version of OpenSSH preferred DSA
1871 over RSA for host and user authentication keys. With this
1872 upgrade, we've switched to the vendor's default of RSA over
1873 DSA. This may cause upgraded clients to warn about unknown
1874 host keys even for previously known hosts. Users should
1875 follow the usual procedure for verifying host keys before
1876 accepting the RSA key.
1878 This can be circumvented by setting the "HostKeyAlgorithms"
1879 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1882 Please note that the sequence of keys offered for
1883 authentication has been changed as well. You may want to
1884 specify IdentityFile in a different order to revert this
1888 The sio(4) driver has been removed from the i386 and amd64
1889 kernel configuration files. This means uart(4) is now the
1890 default serial port driver on those platforms as well.
1892 To prevent collisions with the sio(4) driver, the uart(4) driver
1893 uses different names for its device nodes. This means the
1894 onboard serial port will now most likely be called "ttyu0"
1895 instead of "ttyd0". You may need to reconfigure applications to
1896 use the new device names.
1898 When using the serial port as a boot console, be sure to update
1899 /boot/device.hints and /etc/ttys before booting the new kernel.
1900 If you forget to do so, you can still manually specify the hints
1901 at the loader prompt:
1903 set hint.uart.0.at="isa"
1904 set hint.uart.0.port="0x3F8"
1905 set hint.uart.0.flags="0x10"
1906 set hint.uart.0.irq="4"
1910 The gpt(8) utility has been removed. Use gpart(8) to partition
1914 The version that Linuxulator emulates was changed from 2.4.2
1915 to 2.6.16. If you experience any problems with Linux binaries
1916 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1917 if it fixes the problem contact emulation mailing list.
1920 ISDN4BSD (I4B) was removed from the src tree. You may need to
1921 update a your kernel configuration and remove relevant entries.
1924 I have checked in code to support multiple routing tables.
1925 See the man pages setfib(1) and setfib(2).
1926 This is a hopefully backwards compatible version,
1927 but to make use of it you need to compile your kernel
1928 with options ROUTETABLES=2 (or more up to 16).
1931 The 802.11 wireless support was redone to enable multi-bss
1932 operation on devices that are capable. The underlying device
1933 is no longer used directly but instead wlanX devices are
1934 cloned with ifconfig. This requires changes to rc.conf files.
1935 For example, change:
1936 ifconfig_ath0="WPA DHCP"
1939 ifconfig_wlan0="WPA DHCP"
1940 see rc.conf(5) for more details. In addition, mergemaster of
1941 /etc/rc.d is highly recommended. Simultaneous update of userland
1942 and kernel wouldn't hurt either.
1944 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1945 modules were merged into the base wlan module. All references
1946 to these modules (e.g. in kernel config files) must be removed.
1949 psm(4) has gained write(2) support in native operation level.
1950 Arbitrary commands can be written to /dev/psm%d and status can
1951 be read back from it. Therefore, an application is responsible
1952 for status validation and error recovery. It is a no-op in
1953 other operation levels.
1956 Support for KSE threading has been removed from the kernel. To
1957 run legacy applications linked against KSE libmap.conf may
1958 be used. The following libmap.conf may be used to ensure
1959 compatibility with any prior release:
1961 libpthread.so.1 libthr.so.1
1962 libpthread.so.2 libthr.so.2
1963 libkse.so.3 libthr.so.3
1966 The layout of struct vmspace has changed. This affects libkvm
1967 and any executables that link against libkvm and use the
1968 kvm_getprocs() function. In particular, but not exclusively,
1969 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1970 The effects are minimal, but it's advisable to upgrade world
1974 The latest em driver no longer has support in it for the
1975 82575 adapter, this is now moved to the igb driver. The
1976 split was done to make new features that are incompatible
1977 with older hardware easier to do.
1980 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1981 likewise the kernel option is now GEOM_LINUX_LVM.
1984 The default NFS mount mode has changed from UDP to TCP for
1985 increased reliability. If you rely on (insecurely) NFS
1986 mounting across a firewall you may need to update your
1990 Belatedly note the addition of m_collapse for compacting
1994 The fts(3) structures have been changed to use adequate
1995 integer types for their members and so to be able to cope
1996 with huge file trees. The old fts(3) ABI is preserved
1997 through symbol versioning in libc, so third-party binaries
1998 using fts(3) should still work, although they will not take
1999 advantage of the extended types. At the same time, some
2000 third-party software might fail to build after this change
2001 due to unportable assumptions made in its source code about
2002 fts(3) structure members. Such software should be fixed
2003 by its vendor or, in the worst case, in the ports tree.
2004 FreeBSD_version 800015 marks this change for the unlikely
2005 case that a portable fix is impossible.
2008 To upgrade to -current after this date, you must be running
2009 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2010 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2013 The ADAPTIVE_GIANT kernel option has been retired because its
2014 functionality is the default now.
2017 The AT keyboard emulation of sunkbd(4) has been turned on
2018 by default. In order to make the special symbols of the Sun
2019 keyboards driven by sunkbd(4) work under X these now have
2020 to be configured the same way as Sun USB keyboards driven
2021 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2023 Option "XkbLayout" "us"
2024 Option "XkbRules" "xorg"
2025 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2028 It has been decided that it is desirable to provide ABI
2029 backwards compatibility to the FreeBSD 4/5/6 versions of the
2030 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2031 broken with the introduction of PCI domain support (see the
2032 20070930 entry). Unfortunately, this required the ABI of
2033 PCIOCGETCONF to be broken again in order to be able to
2034 provide backwards compatibility to the old version of that
2035 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2036 again. As for prominent ports this affects neither pciutils
2037 nor xorg-server this time, the hal port needs to be rebuilt
2041 The misnamed kthread_create() and friends have been renamed
2042 to kproc_create() etc. Many of the callers already
2043 used kproc_start()..
2044 I will return kthread_create() and friends in a while
2045 with implementations that actually create threads, not procs.
2046 Renaming corresponds with version 800002.
2055 Avoid using make -j when upgrading. While generally safe, there are
2056 sometimes problems using -j to upgrade. If your upgrade fails with
2057 -j, please try again without -j. From time to time in the past there
2058 have been problems using -j with buildworld and/or installworld. This
2059 is especially true when upgrading between "distant" versions (eg one
2060 that cross a major release boundary or several minor releases, or when
2061 several months have passed on the -current branch).
2063 Sometimes, obscure build problems are the result of environment
2064 poisoning. This can happen because the make utility reads its
2065 environment when searching for values for global variables. To run
2066 your build attempts in an "environmental clean room", prefix all make
2067 commands with 'env -i '. See the env(1) manual page for more details.
2069 When upgrading from one major version to another it is generally best
2070 to upgrade to the latest code in the currently installed branch first,
2071 then do an upgrade to the new branch. This is the best-tested upgrade
2072 path, and has the highest probability of being successful. Please try
2073 this approach before reporting problems with a major version upgrade.
2075 When upgrading a live system, having a root shell around before
2076 installing anything can help undo problems. Not having a root shell
2077 around can lead to problems if pam has changed too much from your
2078 starting point to allow continued authentication after the upgrade.
2082 When upgrading the boot ZFS pool to a new version, always follow
2085 1.) recompile and reinstall the ZFS boot loader and boot block
2086 (this is part of "make buildworld" and "make installworld")
2088 2.) update the ZFS boot block on your boot drive
2090 The following example updates the ZFS boot block on the first
2091 partition (freebsd-boot) of a GPT partitioned drive ad0:
2092 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2094 Non-boot pools do not need these updates.
2098 If you are updating from a prior version of FreeBSD (even one just
2099 a few days old), you should follow this procedure. It is the most
2100 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2102 make kernel-toolchain
2103 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2104 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2106 To test a kernel once
2107 ---------------------
2108 If you just want to boot a kernel once (because you are not sure
2109 if it works, or if you want to boot a known bad kernel to provide
2110 debugging information) run
2111 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2112 nextboot -k testkernel
2114 To just build a kernel when you know that it won't mess you up
2115 --------------------------------------------------------------
2116 This assumes you are already running a CURRENT system. Replace
2117 ${arch} with the architecture of your machine (e.g. "i386",
2118 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2120 cd src/sys/${arch}/conf
2121 config KERNEL_NAME_HERE
2122 cd ../compile/KERNEL_NAME_HERE
2127 If this fails, go to the "To build a kernel" section.
2129 To rebuild everything and install it on the current system.
2130 -----------------------------------------------------------
2131 # Note: sometimes if you are running current you gotta do more than
2132 # is listed here if you are upgrading from a really old current.
2134 <make sure you have good level 0 dumps>
2136 make kernel KERNCONF=YOUR_KERNEL_HERE
2138 <reboot in single user> [3]
2145 To cross-install current onto a separate partition
2146 --------------------------------------------------
2147 # In this approach we use a separate partition to hold
2148 # current's root, 'usr', and 'var' directories. A partition
2149 # holding "/", "/usr" and "/var" should be about 2GB in
2152 <make sure you have good level 0 dumps>
2155 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2156 <maybe newfs current's root partition>
2157 <mount current's root partition on directory ${CURRENT_ROOT}>
2158 make installworld DESTDIR=${CURRENT_ROOT}
2159 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2160 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2161 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2162 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2163 <reboot into current>
2164 <do a "native" rebuild/install as described in the previous section>
2165 <maybe install compatibility libraries from ports/misc/compat*>
2169 To upgrade in-place from stable to current
2170 ----------------------------------------------
2171 <make sure you have good level 0 dumps>
2173 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2175 <reboot in single user> [3]
2182 Make sure that you've read the UPDATING file to understand the
2183 tweaks to various things you need. At this point in the life
2184 cycle of current, things change often and you are on your own
2185 to cope. The defaults can also change, so please read ALL of
2186 the UPDATING entries.
2188 Also, if you are tracking -current, you must be subscribed to
2189 freebsd-current@freebsd.org. Make sure that before you update
2190 your sources that you have read and understood all the recent
2191 messages there. If in doubt, please track -stable which has
2192 much fewer pitfalls.
2194 [1] If you have third party modules, such as vmware, you
2195 should disable them at this point so they don't crash your
2198 [3] From the bootblocks, boot -s, and then do
2203 adjkerntz -i # if CMOS is wall time
2204 Also, when doing a major release upgrade, it is required that
2205 you boot into single user mode to do the installworld.
2207 [4] Note: This step is non-optional. Failure to do this step
2208 can result in a significant reduction in the functionality of the
2209 system. Attempting to do it by hand is not recommended and those
2210 that pursue this avenue should read this file carefully, as well
2211 as the archives of freebsd-current and freebsd-hackers mailing lists
2212 for potential gotchas. The -U option is also useful to consider.
2213 See mergemaster(8) for more information.
2215 [5] Usually this step is a noop. However, from time to time
2216 you may need to do this if you get unknown user in the following
2217 step. It never hurts to do it all the time. You may need to
2218 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2219 install) after the buildworld before this step if you last updated
2220 from current before 20130425 or from -stable before 20130430.
2222 [6] This only deletes old files and directories. Old libraries
2223 can be deleted by "make delete-old-libs", but you have to make
2224 sure that no program is using those libraries anymore.
2226 [8] In order to have a kernel that can run the 4.x binaries needed to
2227 do an installworld, you must include the COMPAT_FREEBSD4 option in
2228 your kernel. Failure to do so may leave you with a system that is
2229 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2230 required to run the 5.x binaries on more recent kernels. And so on
2231 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2233 Make sure that you merge any new devices from GENERIC since the
2234 last time you updated your kernel config file.
2236 [9] When checking out sources, you must include the -P flag to have
2237 cvs prune empty directories.
2239 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2240 "?=" instead of the "=" assignment operator, so that buildworld can
2241 override the CPUTYPE if it needs to.
2243 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2244 not on the command line, or in /etc/make.conf. buildworld will
2245 warn if it is improperly defined.
2248 This file contains a list, in reverse chronological order, of major
2249 breakages in tracking -current. It is not guaranteed to be a complete
2250 list of such breakages, and only contains entries since October 10, 2007.
2251 If you need to see UPDATING entries from before that date, you will need
2252 to fetch an UPDATING file from an older FreeBSD release.
2254 Copyright information:
2256 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2258 Redistribution, publication, translation and use, with or without
2259 modification, in full or in part, in any form or format of this
2260 document are permitted without further permission from the author.
2262 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2263 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2264 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2265 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2266 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2267 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2268 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2269 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2270 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2271 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2272 POSSIBILITY OF SUCH DAMAGE.
2274 Contact Warner Losh if you have any questions about your use of