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 https://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 tz database (tzdb) has been updated to 2018e. This version more
21 correctly models time stamps in time zones with negative DST such as
22 Europe/Dublin (from 1971 on), Europe/Prague (1946/7), and
23 Africa/Windhoek (1994/2017). This does not affect the UT offsets, only
24 time zone abbreviations and the tm_isdst flag.
27 When building multiple kernels using KERNCONF, non-existent KERNCONF
28 files will produce an error and buildkernel will fail. Previously
29 missing KERNCONF files silently failed giving no indication as to
30 why, only to subsequently discover during installkernel that the
31 desired kernel was never built in the first place.
34 Since the switch to GPT disk labels, fsck for UFS/FFS has been
35 unable to automatically find alternate superblocks. As of r322860,
36 the information needed to find alternate superblocks has been
37 moved to the end of the area reserved for the boot block.
38 Filesystems created with a newfs of this vintage or later
39 will create the recovery information. If you have a filesystem
40 created prior to this change and wish to have a recovery block
41 created for your filesystem, you can do so by running fsck in
42 forground mode (i.e., do not use the -p or -y options). As it
43 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
44 to which you should answer yes.
47 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
48 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
49 same source (previously, the dependency of mmcsd.ko on mmc.ko was
50 missing, but mmcsd.ko now will refuse to load if it is incompatible
54 As of r316810 for ipfilter, keep frags is no longer assumed when
55 keep state is specified in a rule. r316810 aligns ipfilter with
56 documentation in man pages separating keep frags from keep state.
57 This allows keep state to specified without forcing keep frags
58 and allows keep frags to be specified independently of keep state.
59 To maintain previous behaviour, also specify keep frags with
60 keep state (as documented in ipf.conf.5).
63 The code that provides support for ZFS .zfs/ directory functionality
64 has been reimplemented. It's not possible now to create a snapshot
65 by mkdir under .zfs/snapshot/. That should be the only user visible
69 The NONE and HPN patches has been removed from OpenSSH. They are
70 still available in the security/openssh-portable port.
73 r292223 changed the internal interface between the nfsd.ko and
74 nfscommon.ko modules. As such, they must both be upgraded to-gether.
75 __FreeBSD_version has been bumped because of this.
78 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
79 Kernel modules isp_2400_multi and isp_2500_multi were removed and
80 should be replaced with isp_2400 and isp_2500 modules respectively.
83 The menu.rc and loader.rc files will now be replaced during
84 upgrades. Please migrate local changes to menu.rc.local and
85 loader.rc.local instead.
88 NTP has been upgraded to 4.2.8p4.
91 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
92 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
93 and devel/kyua to version 0.20+ and adjust any calling code to work
94 with Kyuafile and kyua.
97 The polarity of Pulse Per Second (PPS) capture events with the
98 uart(4) driver has been corrected. Prior to this change the PPS
99 "assert" event corresponded to the trailing edge of a positive PPS
100 pulse and the "clear" event was the leading edge of the next pulse.
102 As the width of a PPS pulse in a typical GPS receiver is on the
103 order of 1 millisecond, most users will not notice any significant
104 difference with this change.
106 Anyone who has compensated for the historical polarity reversal by
107 configuring a negative offset equal to the pulse width will need to
108 remove that workaround.
111 From legacy ata(4) driver was removed support for SATA controllers
112 supported by more functional drivers ahci(4), siis(4) and mvs(4).
113 Kernel modules ataahci and ataadaptec were removed completely,
114 replaced by ahci and mvs modules respectively.
120 As ZFS requires more kernel stack pages than is the default on some
121 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
122 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
124 Please consider using 'options KSTACK_PAGES=X' where X is greater
125 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
128 The default Unbound configuration now enables remote control
129 using a local socket. Users who have already enabled the
130 local_unbound service should regenerate their configuration
131 by running "service local_unbound setup" as root.
134 An additional fix for the issue described in the 20150614 sendmail
135 entry below has been been committed in revision 284786.
138 The fix for the issue described in the 20150614 sendmail entry
139 below has been been committed in revision 284485. The work
140 around described in that entry is no longer needed unless the
141 default setting is overridden by a confDH_PARAMETERS configuration
142 setting of '5' or pointing to a 512 bit DH parameter file.
145 The import of openssl to address the FreeBSD-SA-15:10.openssl
146 security advisory includes a change which rejects handshakes
147 with DH parameters below 768 bits. sendmail releases prior
148 to 8.15.2 (not yet released), defaulted to a 512 bit
149 DH parameter setting for client connections. To work around
150 this interoperability, sendmail can be configured to use a
151 2048 bit DH parameter by:
153 1. Edit /etc/mail/`hostname`.mc
154 2. If a setting for confDH_PARAMETERS does not exist or
155 exists and is set to a string beginning with '5',
157 3. If a setting for confDH_PARAMETERS exists and is set to
158 a file path, create a new file with:
159 openssl dhparam -out /path/to/file 2048
160 4. Rebuild the .cf file:
161 cd /etc/mail/; make; make install
163 cd /etc/mail/; make restart
165 A sendmail patch is coming, at which time this file will be
169 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
170 defined in symlink(7); previously symlinks were silently ignored.
173 The const qualifier has been removed from iconv(3) to comply with
174 POSIX. The ports tree is aware of this from r384038 onwards.
177 At svn r275807, The default linux compat kernel ABI has been adjusted
178 to 2.6.18 in support of the linux-c6 compat ports infrastructure
179 update. If you wish to continue using the linux-f10 compat ports,
180 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
181 encouraged to update their linux-compat packages to linux-c6 during
182 their next update cycle.
184 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
187 pjdfstest has been integrated into kyua as an opt-in test suite.
188 Please see share/doc/pjdfstest/README for a more details on how to
195 The ofwfb driver, used to provide a graphics console on PowerPC when
196 using vt(4), no longer allows mmap() of all of physical memory. This
197 will prevent Xorg on PowerPC with some ATI graphics cards from
198 initializing properly unless x11-servers/xorg-server is updated to
202 The libatf-c and libatf-c++ major versions were downgraded to 0 and
203 1 respectively to match the upstream numbers. They were out of
204 sync because, when they were originally added to FreeBSD, the
205 upstream versions were not respected. These libraries are private
206 and not yet built by default, so renumbering them should be a
207 non-issue. However, unclean source trees will yield broken test
208 programs once the operator executes "make delete-old-libs" after a
211 Additionally, the atf-sh binary was made private by moving it into
212 /usr/libexec/. Already-built shell test programs will keep the
213 path to the old binary so they will break after "make delete-old"
216 If you are using WITH_TESTS=yes (not the default), wipe the object
217 tree and rebuild from scratch to prevent spurious test failures.
218 This is only needed once: the misnumbered libraries and misplaced
219 binaries have been added to OptionalObsoleteFiles.inc so they will
220 be removed during a clean upgrade.
223 The ixgbe tunables now match their sysctl counterparts, for example:
224 hw.ixgbe.enable_aim => hw.ix.enable_aim
225 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
228 The NFSv4.1 server committed by r269398 changes the internal
229 function call interfaces used between the NFS and krpc modules.
230 As such, __FreeBSD_version was bumped.
233 The default unbound configuration has been modified to address
234 issues with reverse lookups on networks that use private
235 address ranges. If you use the local_unbound service, run
236 "service local_unbound setup" as root to regenerate your
237 configuration, then "service local_unbound reload" to load the
241 It is no longer necessary to include the dwarf version in your DEBUG
242 options in your kernel config file. The bug that required it to be
243 placed in the config file has bene fixed. DEBUG should now just
244 contain -g. The build system will automatically update things
245 to do the right thing.
248 Several ABI breaking changes were merged to CTL and new iSCSI code.
249 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
250 iscsictl need to be rebuilt to work with a new kernel.
253 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
254 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
255 which differs from the behaviour controlled by this knob.)
258 On i386 and amd64 systems, the onifconsole flag is now set by default
259 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
260 as a login TTY if it is set in the bootloader as an active kernel
261 console. No changes in behavior should result otherwise. To revert to
262 the previous behavior, set ttyu0 to "off" in /etc/ttys.
265 Clang and llvm have been upgraded to 3.4.1 release.
268 Clang and llvm have been upgraded to 3.4 release.
271 If a Makefile in a tests/ directory was auto-generating a Kyuafile
272 instead of providing an explicit one, this would prevent such
273 Makefile from providing its own Kyuafile in the future during
274 NO_CLEAN builds. This has been fixed in the Makefiles but manual
275 intervention is needed to clean an objdir if you use NO_CLEAN:
276 # find /usr/obj -name Kyuafile | xargs rm -f
279 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
280 capability mode support. Please note that enabling the feature in
281 kernel is still highly recommended.
284 OpenSSH is now built with sandbox support, and will use sandbox as
285 the default privilege separation method. This requires Capsicum
286 capability mode support in kernel.
289 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
290 been deprecated and will not be part of FreeBSD 11.0 and later
291 releases. If you use this driver, please consider switching to
292 the nfe(4) driver instead.
298 The behavior of gss_pseudo_random() for the krb5 mechanism
299 has changed, for applications requesting a longer random string
300 than produced by the underlying enctype's pseudo-random() function.
301 In particular, the random string produced from a session key of
302 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
303 be different at the 17th octet and later, after this change.
304 The counter used in the PRF+ construction is now encoded as a
305 big-endian integer in accordance with RFC 4402.
306 __FreeBSD_version is bumped to 1000701.
309 The WITHOUT_ATF build knob has been removed and its functionality
310 has been subsumed into the more generic WITHOUT_TESTS. If you were
311 using the former to disable the build of the ATF libraries, you
312 should change your settings to use the latter.
315 The default version of mtree is nmtree which is obtained from
316 NetBSD. The output is generally the same, but may vary
317 slightly. If you found you need identical output adding
318 "-F freebsd9" to the command line should do the trick. For the
319 time being, the old mtree is available as fmtree.
322 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
323 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
324 1.1.4_8 and verify bsdyml not linked in, before running "make
326 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
328 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
331 The rc.d/jail script has been updated to support jail(8)
332 configuration file. The "jail_<jname>_*" rc.conf(5) variables
333 for per-jail configuration are automatically converted to
334 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
335 This is transparently backward compatible. See below about some
336 incompatibilities and rc.conf(5) manual page for more details.
338 These variables are now deprecated in favor of jail(8) configuration
339 file. One can use "rc.d/jail config <jname>" command to generate
340 a jail(8) configuration file in /var/run/jail.<jname>.conf without
341 running the jail(8) utility. The default pathname of the
342 configuration file is /etc/jail.conf and can be specified by
343 using $jail_conf or $jail_<jname>_conf variables.
345 Please note that jail_devfs_ruleset accepts an integer at
346 this moment. Please consider to rewrite the ruleset name
350 BIND has been removed from the base system. If all you need
351 is a local resolver, simply enable and start the local_unbound
352 service instead. Otherwise, several versions of BIND are
353 available in the ports tree. The dns/bind99 port is one example.
355 With this change, nslookup(1) and dig(1) are no longer in the base
356 system. Users should instead use host(1) and drill(1) which are
357 in the base system. Alternatively, nslookup and dig can
358 be obtained by installing the dns/bind-tools port.
361 With the addition of unbound(8), a new unbound user is now
362 required during installworld. "mergemaster -p" can be used to
363 add the user prior to installworld, as documented in the handbook.
366 OpenSSH is now built with DNSSEC support, and will by default
367 silently trust signed SSHFP records. This can be controlled with
368 the VerifyHostKeyDNS client configuration setting. DNSSEC support
369 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
372 The GNU Compiler Collection and C++ standard library (libstdc++)
373 are no longer built by default on platforms where clang is the system
374 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
378 The PROCDESC kernel option is now part of the GENERIC kernel
379 configuration and is required for the rwhod(8) to work.
380 If you are using custom kernel configuration, you should include
384 The API and ABI related to the Capsicum framework was modified
385 in backward incompatible way. The userland libraries and programs
386 have to be recompiled to work with the new kernel. This includes the
387 following libraries and programs, but the whole buildworld is
388 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
389 kdump, procstat, rwho, rwhod, uniq.
392 AES-NI intrinsic support has been added to gcc. The AES-NI module
393 has been updated to use this support. A new gcc is required to build
394 the aesni module on both i386 and amd64.
397 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
398 Thus "device padlock_rng" and "device rdrand_rng" should be
399 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
402 WITH_ICONV has been split into two feature sets. WITH_ICONV now
403 enables just the iconv* functionality and is now on by default.
404 WITH_LIBICONV_COMPAT enables the libiconv api and link time
405 compatability. Set WITHOUT_ICONV to build the old way.
406 If you have been using WITH_ICONV before, you will very likely
407 need to turn on WITH_LIBICONV_COMPAT.
410 INVARIANTS option now enables DEBUG for code with OpenSolaris and
411 Illumos origin, including ZFS. If you have INVARIANTS in your
412 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
414 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
415 locks if WITNESS option was set. Because that generated a lot of
416 witness(9) reports and all of them were believed to be false
417 positives, this is no longer done. New option OPENSOLARIS_WITNESS
418 can be used to achieve the previous behavior.
421 Timer values in IPv6 data structures now use time_uptime instead
422 of time_second. Although this is not a user-visible functional
423 change, userland utilities which directly use them---ndp(8),
424 rtadvd(8), and rtsold(8) in the base system---need to be updated
428 find -delete can now delete the pathnames given as arguments,
429 instead of only files found below them or if the pathname did
430 not contain any slashes. Formerly, the following error message
433 find: -delete: <path>: relative path potentially not safe
435 Deleting the pathnames given as arguments can be prevented
436 without error messages using -mindepth 1 or by changing
437 directory and passing "." as argument to find. This works in the
438 old as well as the new version of find.
441 Behavior of devfs rules path matching has been changed.
442 Pattern is now always matched against fully qualified devfs
443 path and slash characters must be explicitly matched by
444 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
445 subdirectories must be reviewed.
448 The default ARM ABI has changed to the ARM EABI. The old ABI is
449 incompatible with the ARM EABI and all programs and modules will
450 need to be rebuilt to work with a new kernel.
452 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
454 NOTE: Support for the old ABI will be removed in the future and
455 users are advised to upgrade.
458 pkg_install has been disconnected from the build if you really need it
459 you should add WITH_PKGTOOLS in your src.conf(5).
462 Most of network statistics structures were changed to be able
463 keep 64-bits counters. Thus all tools, that work with networking
464 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
467 Fix a bug that allowed a tracing process (e.g. gdb) to write
468 to a memory-mapped file in the traced process's address space
469 even if neither the traced process nor the tracing process had
470 write access to that file.
473 CVS has been removed from the base system. An exact copy
474 of the code is available from the devel/cvs port.
477 Some people report the following error after the switch to bmake:
479 make: illegal option -- J
480 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
482 *** [buildworld] Error code 2
484 this likely due to an old instance of make in
485 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
486 which src/Makefile will use that blindly, if it exists, so if
487 you see the above error:
489 rm -rf `make -V MAKEPATH`
494 Use bmake by default.
495 Whereas before one could choose to build with bmake via
496 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
497 make. The goal is to remove these knobs for 10-RELEASE.
499 It is worth noting that bmake (like gmake) treats the command
500 line as the unit of failure, rather than statements within the
501 command line. Thus '(cd some/where && dosomething)' is safer
502 than 'cd some/where; dosomething'. The '()' allows consistent
503 behavior in parallel build.
506 Fix a bug that allows NFS clients to issue READDIR on files.
509 The WITHOUT_IDEA option has been removed because
510 the IDEA patent expired.
513 The sysctl which controls TRIM support under ZFS has been renamed
514 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
518 The mergemaster command now uses the default MAKEOBJDIRPREFIX
519 rather than creating it's own in the temporary directory in
520 order allow access to bootstrapped versions of tools such as
521 install and mtree. When upgrading from version of FreeBSD where
522 the install command does not support -l, you will need to
523 install a new mergemaster command if mergemaster -p is required.
524 This can be accomplished with the command (cd src/usr.sbin/mergemaster
528 Legacy ATA stack, disabled and replaced by new CAM-based one since
529 FreeBSD 9.0, completely removed from the sources. Kernel modules
530 atadisk and atapi*, user-level tools atacontrol and burncd are
531 removed. Kernel option `options ATA_CAM` is now permanently enabled
535 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
536 and socketpair(2). Software, in particular Kerberos, may
537 automatically detect and use these during building. The resulting
538 binaries will not work on older kernels.
541 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
542 information, see the respective 20130304 entry).
545 Recent commits to callout(9) changed the size of struct callout,
546 so the KBI is probably heavily disturbed. Also, some functions
547 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
548 by macros. Every kernel module using it won't load, so rebuild
551 The ctl device has been re-enabled in GENERIC for i386 and amd64,
552 but does not initialize by default (because of the new CTL_DISABLE
553 option) to save memory. To re-enable it, remove the CTL_DISABLE
554 option from the kernel config file or set kern.cam.ctl.disable=0
555 in /boot/loader.conf.
558 The ctl device has been disabled in GENERIC for i386 and amd64.
559 This was done due to the extra memory being allocated at system
560 initialisation time by the ctl driver which was only used if
561 a CAM target device was created. This makes a FreeBSD system
562 unusable on 128MB or less of RAM.
565 A new compression method (lz4) has been merged to -HEAD. Please
566 refer to zpool-features(7) for more information.
568 Please refer to the "ZFS notes" section of this file for information
569 on upgrading boot ZFS pools.
572 A BSD-licensed patch(1) variant has been added and is installed
573 as bsdpatch, being the GNU version the default patch.
574 To inverse the logic and use the BSD-licensed one as default,
575 while having the GNU version installed as gnupatch, rebuild
576 and install world with the WITH_BSD_PATCH knob set.
579 Due to the use of the new -l option to install(1) during build
580 and install, you must take care not to directly set the INSTALL
581 make variable in your /etc/make.conf, /etc/src.conf, or on the
582 command line. If you wish to use the -C flag for all installs
583 you may be able to add INSTALL+=-C to /etc/make.conf or
587 The install(1) option -M has changed meaning and now takes an
588 argument that is a file or path to append logs to. In the
589 unlikely event that -M was the last option on the command line
590 and the command line contained at least two files and a target
591 directory the first file will have logs appended to it. The -M
592 option served little practical purpose in the last decade so its
593 use is expected to be extremely rare.
596 After switching to Clang as the default compiler some users of ZFS
597 on i386 systems started to experience stack overflow kernel panics.
598 Please consider using 'options KSTACK_PAGES=4' in such configurations.
601 GEOM_LABEL now mangles label names read from file system metadata.
602 Mangling affect labels containing spaces, non-printable characters,
603 '%' or '"'. Device names in /etc/fstab and other places may need to
607 By default, only the 10 most recent kernel dumps will be saved. To
608 restore the previous behaviour (no limit on the number of kernel dumps
609 stored in the dump directory) add the following line to /etc/rc.conf:
614 With the addition of auditdistd(8), a new auditdistd user is now
615 required during installworld. "mergemaster -p" can be used to
616 add the user prior to installworld, as documented in the handbook.
619 The sin6_scope_id member variable in struct sockaddr_in6 is now
620 filled by the kernel before passing the structure to the userland via
621 sysctl or routing socket. This means the KAME-specific embedded scope
622 id in sin6_addr.s6_addr[2] is always cleared in userland application.
623 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
624 __FreeBSD_version is bumped to 1000025.
627 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
628 This means that the world and kernel will be compiled with clang
629 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
630 and /usr/bin/cpp. To disable this behavior and revert to building
631 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
632 of current may need to bootstrap WITHOUT_CLANG first if the clang
633 build fails (its compatibility window doesn't extend to the 9 stable
637 The IPFIREWALL_FORWARD kernel option has been removed. Its
638 functionality now turned on by default.
641 The ZERO_COPY_SOCKET kernel option has been removed and
642 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
643 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
644 mechanism which is not safe and may result in kernel crashes.
645 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
646 driver supports disposeable external page sized mbuf storage.
647 Proper replacements for both zero-copy mechanisms are under
648 consideration and will eventually lead to complete removal
649 of the two kernel options.
652 The IPv4 network stack has been converted to network byte
653 order. The following modules need to be recompiled together
654 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
655 pf(4), ipfw(4), ng_ipfw(4), stf(4).
658 Support for non-MPSAFE filesystems was removed from VFS. The
659 VFS_VERSION was bumped, all filesystem modules shall be
663 All the non-MPSAFE filesystems have been disconnected from
664 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
665 portalfs, smbfs, xfs.
668 The interface cloning API and ABI has changed. The following
669 modules need to be recompiled together with kernel:
670 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
671 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
672 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
675 The sdhci driver was split in two parts: sdhci (generic SD Host
676 Controller logic) and sdhci_pci (actual hardware driver).
677 No kernel config modifications are required, but if you
678 load sdhc as a module you must switch to sdhci_pci instead.
681 Import the FUSE kernel and userland support into base system.
684 The GNU sort(1) program has been removed since the BSD-licensed
685 sort(1) has been the default for quite some time and no serious
686 problems have been reported. The corresponding WITH_GNU_SORT
690 The pfil(9) API/ABI for AF_INET family has been changed. Packet
691 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
695 The net80211(4) ABI has been changed to allow for improved driver
696 PS-POLL and power-save support. All wireless drivers need to be
697 recompiled to work with the new kernel.
700 The random(4) support for the VIA hardware random number
701 generator (`PADLOCK') is no longer enabled unconditionally.
702 Add the padlock_rng device in the custom kernel config if
703 needed. The GENERIC kernels on i386 and amd64 do include the
704 device, so the change only affects the custom kernel
708 The pf(4) packet filter ABI has been changed. pfctl(8) and
709 snmp_pf module need to be recompiled to work with new kernel.
712 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
713 to -HEAD. Pools that have empty_bpobj in active state can not be
714 imported read-write with ZFS implementations that do not support
715 this feature. For more information read the zpool-features(5)
719 The sparc64 ZFS loader has been changed to no longer try to auto-
720 detect ZFS providers based on diskN aliases but now requires these
721 to be explicitly listed in the OFW boot-device environment variable.
724 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
725 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
726 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
729 The following sysctls and tunables have been renamed for consistency
730 with other variables:
731 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
732 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
735 The sort utility has been replaced with BSD sort. For now, GNU sort
736 is also available as "gnusort" or the default can be set back to
737 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
738 installed as "bsdsort".
741 A new version of ZFS (pool version 5000) has been merged to -HEAD.
742 Starting with this version the old system of ZFS pool versioning
743 is superseded by "feature flags". This concept enables forward
744 compatibility against certain future changes in functionality of ZFS
745 pools. The first read-only compatible "feature flag" for ZFS pools
746 is named "com.delphix:async_destroy". For more information
747 read the new zpool-features(5) manual page.
748 Please refer to the "ZFS notes" section of this file for information
749 on upgrading boot ZFS pools.
752 The malloc(3) implementation embedded in libc now uses sources imported
753 as contrib/jemalloc. The most disruptive API change is to
754 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
755 delete it prior to installworld, and optionally re-create it using the
756 new format after rebooting. See malloc.conf(5) for details
757 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
761 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
762 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
763 now spelled mips. This is to aid compatibility with third-party
764 software that expects this naming scheme in uname(3). Little-endian
765 settings are unchanged. If you are updating a big-endian mips64 machine
766 from before this change, you may need to set MACHINE_ARCH=mips64 in
767 your environment before the new build system will recognize your machine.
770 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
774 Now unix domain sockets behave "as expected" on nullfs(5). Previously
775 nullfs(5) did not pass through all behaviours to the underlying layer,
776 as a result if we bound to a socket on the lower layer we could connect
777 only to the lower path; if we bound to the upper layer we could connect
778 only to the upper path. The new behavior is one can connect to both the
779 lower and the upper paths regardless what layer path one binds to.
782 The getifaddrs upgrade path broken with 20111215 has been restored.
783 If you have upgraded in between 20111215 and 20120209 you need to
784 recompile libc again with your kernel. You still need to recompile
785 world to be able to configure CARP but this restriction already
789 The set_rcvar() function has been removed from /etc/rc.subr. All
790 base and ports rc.d scripts have been updated, so if you have a
791 port installed with a script in /usr/local/etc/rc.d you can either
792 hand-edit the rcvar= line, or reinstall the port.
794 An easy way to handle the mass-update of /etc/rc.d:
795 rm /etc/rc.d/* && mergemaster -i
798 panic(9) now stops other CPUs in the SMP systems, disables interrupts
799 on the current CPU and prevents other threads from running.
800 This behavior can be reverted using the kern.stop_scheduler_on_panic
802 The new behavior can be incompatible with kern.sync_on_panic.
805 The carp(4) facility has been changed significantly. Configuration
806 of the CARP protocol via ifconfig(8) has changed, as well as format
807 of CARP events submitted to devd(8) has changed. See manual pages
808 for more information. The arpbalance feature of carp(4) is currently
809 not supported anymore.
811 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
812 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
813 need to be recompiled.
816 The acpi_wmi(4) status device /dev/wmistat has been renamed to
820 The option VFS_ALLOW_NONMPSAFE option has been added in order to
821 explicitely support non-MPSAFE filesystems.
822 It is on by default for all supported platform at this present
826 The broken amd(4) driver has been replaced with esp(4) in the amd64,
827 i386 and pc98 GENERIC kernel configuration files.
830 sysinstall has been removed
833 The stable/9 branch created in subversion. This corresponds to the
834 RELENG_9 branch in CVS.
837 This commit modifies vfs_register() so that it uses a hash
838 calculation to set vfc_typenum, which is enabled by default.
839 The first time a system is booted after this change, the
840 vfc_typenum values will change for all file systems. The
841 main effect of this is a change to the NFS server file handles
842 for file systems that use vfc_typenum in their fsid, such as ZFS.
843 It will, however, prevent vfc_typenum from changing when file
844 systems are loaded in a different order for subsequent reboots.
845 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
846 until you are ready to remount all NFS clients after a reboot.
849 Bump the shared library version numbers for libraries that
850 do not use symbol versioning, have changed the ABI compared
851 to stable/8 and which shared library version was not bumped.
852 Done as part of 9.0-RELEASE cycle.
855 During the merge of Capsicum features, the fget(9) KPI was modified.
856 This may require the rebuilding of out-of-tree device drivers --
857 issues have been reported specifically with the nVidia device driver.
858 __FreeBSD_version is bumped to 900041.
860 Also, there is a period between 20110811 and 20110814 where the
861 special devices /dev/{stdin,stdout,stderr} did not work correctly.
862 Building world from a kernel during that window may not work.
865 The packet filter (pf) code has been updated to OpenBSD 4.5.
866 You need to update userland tools to be in sync with kernel.
867 This update breaks backward compatibility with earlier pfsync(4)
868 versions. Care must be taken when updating redundant firewall setups.
871 The following sysctls and tunables are retired on x86 platforms:
873 machdep.hlt_logical_cpus
874 The following sysctl is retired:
875 machdep.hyperthreading_allowed
876 The sysctls were supposed to provide a way to dynamically offline and
877 online selected CPUs on x86 platforms, but the implementation has not
878 been reliable especially with SCHED_ULE scheduler.
879 machdep.hyperthreading_allowed tunable is still available to ignore
880 hyperthreading CPUs at OS level.
881 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
882 where X is an APIC ID of a CPU. Be advised, though, that disabling
883 CPUs in non-uniform fashion will result in non-uniform topology and
884 may lead to sub-optimal system performance with SCHED_ULE, which is
888 cpumask_t type is retired and cpuset_t is used in order to describe
892 Changes to ifconfig(8) for dynamic address family detection mandate
893 that you are running a kernel of 20110525 or later. Make sure to
894 follow the update procedure to boot a new kernel before installing
898 Support for sun4v architecture is officially dropped
901 Several KPI breaking changes have been committed to the mii(4) layer,
902 the PHY drivers and consequently some Ethernet drivers using mii(4).
903 This means that miibus.ko and the modules of the affected Ethernet
904 drivers need to be recompiled.
906 Note to kernel developers: Given that the OUI bit reversion problem
907 was fixed as part of these changes all mii(4) commits related to OUIs,
908 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
909 handling, no longer can be merged verbatim to stable/8 and previous
913 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
914 into their kernel configurations along with 'device pci'.
917 The default NFS client is now the new NFS client, so fstype "newnfs"
918 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
919 Although mounts via fstype "nfs" will usually work without userland
920 changes, it is recommended that the mount(8) and mount_nfs(8)
921 commands be rebuilt from sources and that a link to mount_nfs called
922 mount_oldnfs be created. The new client is compiled into the
923 kernel with "options NFSCL" and this is needed for diskless root
924 file systems. The GENERIC kernel configs have been changed to use
925 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
926 To use the regular/old client, you can "mount -t oldnfs ...". For
927 a diskless root file system, you must also include a line like:
929 vfs.root.mountfrom="oldnfs:"
931 in the boot/loader.conf on the root fs on the NFS server to make
932 a diskless root fs use the old client.
935 The GENERIC kernels for all architectures now default to the new
936 CAM-based ATA stack. It means that all legacy ATA drivers were
937 removed and replaced by respective CAM drivers. If you are using
938 ATA device names in /etc/fstab or other places, make sure to update
939 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
940 where 'Y's are the sequential numbers starting from zero for each type
941 in order of detection, unless configured otherwise with tunables,
942 see cam(4)). There will be symbolic links created in /dev/ to map
943 old adX devices to the respective adaY. They should provide basic
944 compatibility for file systems mounting in most cases, but they do
945 not support old user-level APIs and do not have respective providers
946 in GEOM. Consider using updated management tools with new device names.
948 It is possible to load devices ahci, ata, siis and mvs as modules,
949 but option ATA_CAM should remain in kernel configuration to make ata
950 module work as CAM driver supporting legacy ATA controllers. Device ata
951 still can be used in modular fashion (atacore + ...). Modules atadisk
952 and atapi* are not used and won't affect operation in ATA_CAM mode.
953 Note that to use CAM-based ATA kernel should include CAM devices
954 scbus, pass, da (or explicitly ada), cd and optionally others. All of
955 them are parts of the cam module.
957 ataraid(4) functionality is now supported by the RAID GEOM class.
958 To use it you can load geom_raid kernel module and use graid(8) tool
959 for management. Instead of /dev/arX device names, use /dev/raid/rX.
961 No kernel config options or code have been removed, so if a problem
962 arises, please report it and optionally revert to the old ATA stack.
963 In order to do it you can remove from the kernel config:
968 , and instead add back:
969 device atadisk # ATA disk drives
970 device ataraid # ATA RAID drives
971 device atapicd # ATAPI CDROM drives
972 device atapifd # ATAPI floppy drives
973 device atapist # ATAPI tape drives
976 The default NFS server has been changed to the new server, which
977 was referred to as the experimental server. If you need to switch
978 back to the old NFS server, you must now put the "-o" option on
979 both the mountd and nfsd commands. This can be done using the
980 mountd_flags and nfs_server_flags rc.conf variables until an
981 update to the rc scripts is committed, which is coming soon.
984 The GNU Objective-C runtime library (libobjc), and other Objective-C
985 related components have been removed from the base system. If you
986 require an Objective-C library, please use one of the available ports.
989 ath(4) has been split into bus- and device- modules. if_ath contains
990 the HAL, the TX rate control and the network device code. if_ath_pci
991 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
992 contains the AHB glue. Users need to load both if_ath_pci and if_ath
993 in order to use ath on everything else.
995 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
996 need to load if_ath and if_ath_pci for ath(4) operation.
999 As part of the replacement of sysinstall, the process of building
1000 release media has changed significantly. For details, please re-read
1001 release(7), which has been updated to reflect the new build process.
1004 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1005 is the last available version under GPLv2. It brings a number of new
1006 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1007 4.1 and SSE 4.2), better support for powerpc64, a number of new
1008 directives, and lots of other small improvements. See the ChangeLog
1009 file in contrib/binutils for the full details.
1012 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1013 compliant, and will now use half of hash for authentication.
1014 This will break interoperability with all stacks (including all
1015 actual FreeBSD versions) who implement
1016 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1018 The only workaround with such peers is to use another HMAC
1019 algorithm for IPsec ("phase 2") authentication.
1022 Remove the uio_yield prototype and symbol. This function has
1023 been misnamed since it was introduced and should not be
1024 globally exposed with this name. The equivalent functionality
1025 is now available using kern_yield(curthread->td_user_pri).
1026 The function remains undocumented.
1029 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1030 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1031 for scalar sysctls is defined but disabled. Code that needs
1032 UQUAD to pass the type checking that must compile on older
1033 systems where the define is not present can check against
1034 __FreeBSD_version >= 900030.
1036 The system dialog(1) has been replaced with a new version previously
1037 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1038 with the previous version, but the libdialog associated with it has
1039 a largely incompatible API. As such, the original version of libdialog
1040 will be kept temporarily as libodialog, until its base system consumers
1041 are replaced or updated. Bump __FreeBSD_version to 900030.
1044 If you are trying to run make universe on a -stable system, and you get
1045 the following warning:
1046 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1047 unknown. config(8) likely too old."
1048 or something similar to it, then you must upgrade your -stable system
1049 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1050 stable/8) or build the config from the latest stable/8 branch and
1051 install it on your system.
1053 Prior to this date, building a current universe on 8-stable system from
1054 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1055 error in the first kernel build phase. A new config on those old
1056 systems will fix that problem for older versions of -current.
1059 The TCP stack has been modified to allow Khelp modules to interact with
1060 it via helper hook points and store per-connection data in the TCP
1061 control block. Bump __FreeBSD_version to 900029. User space tools that
1062 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1066 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1067 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1068 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1069 to take advantage of it instead of using custom implementations. This
1070 means that these drivers now no longer unconditionally advertise
1071 support for flow control but only do so if flow control is a selected
1072 media option. This was implemented in the generic support that way in
1073 order to allow flow control to be switched on and off via ifconfig(8)
1074 with the PHY specific default to typically off in order to protect
1075 from unwanted effects. Consequently, if you used flow control with
1076 one of the above mentioned drivers you now need to explicitly enable
1077 it, for example via:
1078 ifconfig bge0 media auto mediaopt flowcontrol
1080 Along with the above mentioned changes generic support for setting
1081 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1082 e1000phy(4) as well as ip1000phy(4) have been converted to take
1083 advantage of it. This means that these drivers now no longer take the
1084 link0 parameter for selecting master mode but the master media option
1085 has to be used instead, for example like in the following:
1086 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1088 Selection of master mode now is also available with all other PHY
1089 drivers supporting 1000baseT.
1092 The TCP stack has received a significant update to add support for
1093 modularised congestion control and generally improve the clarity of
1094 congestion control decisions. Bump __FreeBSD_version to 900025. User
1095 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1096 sockstat) need to be recompiled.
1099 The man(1) utility has been replaced by a new version that no longer
1100 uses /etc/manpath.config. Please consult man.conf(5) for how to
1101 migrate local entries to the new format.
1104 The copyright strings printed by login(1) and sshd(8) at the time of a
1105 new connection have been removed to follow other operating systems and
1109 A workaround for a fixed ld bug has been removed in kernel code,
1110 so make sure that your system ld is built from sources after
1111 revision 210245 from 2010-07-19 (r211583 if building head kernel
1112 on stable/8, r211584 for stable/7; both from 2010-08-21).
1113 A symptom of incorrect ld version is different addresses for
1114 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1117 The $ipv6_prefer variable in rc.conf(5) has been split into
1118 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1120 The $ip6addrctl_policy is a variable to choose a pre-defined
1121 address selection policy set by ip6addrctl(8). A value
1122 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1125 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1126 flag (see an entry of 20090926) is set on an interface with no
1127 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1128 security reason. If you want IPv6 link-local address on all
1129 interfaces by default, set this to "YES".
1131 The old ipv6_prefer="YES" is equivalent to
1132 ipv6_activate_all_interfaces="YES" and
1133 ip6addrctl_policy="ipv6_prefer".
1136 DTrace has grown support for userland tracing. Due to this, DTrace is
1137 now i386 and amd64 only.
1138 dtruss(1) is now installed by default on those systems and a new
1139 kernel module is needed for userland tracing: fasttrap.
1140 No changes to your kernel config file are necessary to enable
1141 userland tracing, but you might consider adding 'STRIP=' and
1142 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1143 to have informative userland stack traces in DTrace (ustack).
1146 The acpi_aiboost(4) driver has been removed in favor of the new
1147 aibs(4) driver. You should update your kernel configuration file.
1150 BSD grep has been imported to the base system and it is built by
1151 default. It is completely BSD licensed, highly GNU-compatible, uses
1152 less memory than its GNU counterpart and has a small codebase.
1153 However, it is slower than its GNU counterpart, which is mostly
1154 noticeable for larger searches, for smaller ones it is measurable
1155 but not significant. The reason is complex, the most important factor
1156 is that we lack a modern and efficient regex library and GNU
1157 overcomes this by optimizing the searches internally. Future work
1158 on improving the regex performance is planned, for the meantime,
1159 users that need better performance, can build GNU grep instead by
1160 setting the WITH_GNU_GREP knob.
1163 Due to the import of powerpc64 support, all existing powerpc kernel
1164 configuration files must be updated with a machine directive like this:
1165 machine powerpc powerpc
1167 In addition, an updated config(8) is required to build powerpc kernels
1171 A new version of ZFS (version 15) has been merged to -HEAD.
1172 This version uses a python library for the following subcommands:
1173 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1174 For full functionality of these commands the following port must
1175 be installed: sysutils/py-zfs
1178 'vm_page's are now hashed by physical address to an array of mutexes.
1179 Currently this is only used to serialize access to hold_count. Over
1180 time the page queue mutex will be peeled away. This changes the size
1181 of pmap on every architecture. And requires all callers of vm_page_hold
1182 and vm_page_unhold to be updated.
1185 WITH_CTF can now be specified in src.conf (not recommended, there
1186 are some problems with static executables), make.conf (would also
1187 affect ports which do not use GNU make and do not override the
1188 compile targets) or in the kernel config (via "makeoptions
1190 When WITH_CTF was specified there before this was silently ignored,
1191 so make sure that WITH_CTF is not used in places which could lead
1192 to unwanted behavior.
1195 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1196 to allow 32-bit compatibility on non-x86 platforms. All kernel
1197 configurations on amd64 and ia64 platforms using these options must
1198 be modified accordingly.
1201 The utmp user accounting database has been replaced with utmpx,
1202 the user accounting interface standardized by POSIX.
1203 Unfortunately the semantics of utmp and utmpx don't match,
1204 making it practically impossible to support both interfaces.
1205 The user accounting database is used by tools like finger(1),
1206 last(1), talk(1), w(1) and ac(8).
1208 All applications in the base system use utmpx. This means only
1209 local binaries (e.g. from the ports tree) may still use these
1210 utmp database files. These applications must be rebuilt to make
1213 After the system has been upgraded, it is safe to remove the old
1214 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1215 assuming their contents is of no importance anymore. Old wtmp
1216 databases can only be used by last(1) and ac(8) after they have
1217 been converted to the new format using wtmpcvt(1).
1220 Introduce the kernel thread "deadlock resolver" (which can be enabled
1221 via the DEADLKRES option, see NOTES for more details) and the
1222 sleepq_type() function for sleepqueues.
1225 The rc.firewall and rc.firewall6 were unified, and
1226 rc.firewall6 and rc.d/ip6fw were removed.
1227 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1228 variables are obsoleted. Instead, the following new rc
1229 variables are added to rc.d/ipfw:
1231 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1232 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1233 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1235 The meanings correspond to the relevant IPv4 variables.
1241 The default terminal emulation for syscons(4) has been changed
1242 from cons25 to xterm on all platforms except pc98. This means
1243 that the /etc/ttys file needs to be updated to ensure correct
1244 operation of applications on the console.
1246 The terminal emulation style can be toggled per window by using
1247 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1248 options can be used to change the compile-time default back to
1251 To prevent graphical artifacts, make sure the TERM environment
1252 variable is set to match the terminal emulation that is being
1253 performed by syscons(4).
1256 The layout of the structure ieee80211req_scan_result has changed.
1257 Applications that require wireless scan results (e.g. ifconfig(8))
1258 from net80211 need to be recompiled.
1260 Applications such as wpa_supplicant(8) may require a full world
1261 build without using NO_CLEAN in order to get synchronized with the
1265 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1266 There's one kernel module for each firmware. Adding "device iwnfw"
1267 to the kernel configuration file means including all three firmware
1268 images inside the kernel. If you want to include just the one for
1269 your wireless card, use the devices iwn4965fw, iwn5000fw or
1273 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1274 into rc.d/netif. The changes are the following:
1276 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1277 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1278 Note that both variables need the "inet6" keyword at the head.
1280 Do not set $ipv6_network_interfaces manually if you do not
1281 understand what you are doing. It is not needed in most cases.
1283 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1286 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1287 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1289 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1290 all configured interfaces have "inet6 accept_rtadv" in the
1291 $ifconfig_IF_ipv6. These are for backward compatibility.
1293 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1294 functionality of interfaces with no corresponding
1295 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1296 and the default address selection policy of ip6addrctl(8)
1297 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1298 Note that if you want to configure IPv6 functionality on the
1299 disabled interfaces after boot, first you need to clear the flag by
1300 using ifconfig(8) like:
1302 ifconfig em0 inet6 -ifdisabled
1304 If YES, the default address selection policy is set as
1307 The default value of $ipv6_prefer is NO.
1309 4. If your system need to receive Router Advertisement messages,
1310 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1311 scripts automatically invoke rtsol(8) when the interface becomes
1312 UP. The Router Advertisement messages are used for SLAAC
1313 (State-Less Address AutoConfiguration).
1316 802.11s D3.03 support was committed. This is incompatible with the
1317 previous code, which was based on D3.0.
1320 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1321 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1322 control whether accepting Router Advertisement messages or not.
1323 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1324 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1325 The ifconfig(8) utility now supports these flags.
1328 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1329 mount(8) and -a option for df(1) to see them.
1332 The old tunable hw.bus.devctl_disable has been superseded by
1333 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1334 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1338 Remove the option STOP_NMI. The default action is now to use NMI only
1339 for KDB via the newly introduced function stop_cpus_hard() and
1340 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1343 The stable/8 branch created in subversion. This corresponds to the
1344 RELENG_8 branch in CVS.
1347 Bump the shared library version numbers for all libraries that do not
1348 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1349 __FreeBSD_version to 800105.
1352 Due to changes in the implementation of virtual network stack support,
1353 all network-related kernel modules must be recompiled. As this change
1354 breaks the ABI, bump __FreeBSD_version to 800104.
1357 The TOE interface to the TCP syncache has been modified to remove
1358 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1359 The cxgb driver is the only TOE consumer affected by this change, and
1360 needs to be recompiled along with the kernel. As this change breaks
1361 the ABI, bump __FreeBSD_version to 800103.
1364 Padding has been added to struct tcpcb, sackhint and tcpstat in
1365 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1366 maintaining the ABI. However, this change breaks the ABI, so bump
1367 __FreeBSD_version to 800102. User space tools that rely on the size of
1368 any of these structs (e.g. sockstat) need to be recompiled.
1371 The NFS_LEGACYRPC option has been removed along with the old kernel
1372 RPC implementation that this option selected. Kernel configurations
1373 may need to be adjusted.
1376 The network interface device nodes at /dev/net/<interface> have been
1377 removed. All ioctl operations can be performed the normal way using
1378 routing sockets. The kqueue functionality can generally be replaced
1379 with routing sockets.
1382 The documentation from the FreeBSD Documentation Project (Handbook,
1383 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1384 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1387 The ABI of various structures related to the SYSV IPC API have been
1388 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1389 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1393 Layout of struct vnet has changed as routing related variables were
1394 moved to their own Vimage module. Modules need to be recompiled. Bump
1395 __FreeBSD_version to 800099.
1398 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1399 respectively. As long as no more than 16 groups per process are used,
1400 no changes should be visible. When more than 16 groups are used, old
1401 binaries may fail if they call getgroups() or getgrouplist() with
1402 statically sized storage. Recompiling will work around this, but
1403 applications should be modified to use dynamically allocated storage
1404 for group arrays as POSIX.1-2008 does not cap an implementation's
1405 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1407 NFS and portalfs mounts may also be affected as the list of groups is
1408 truncated to 16. Users of NFS who use more than 16 groups, should
1409 take care that negative group permissions are not used on the exported
1410 file systems as they will not be reliable unless a GSSAPI based
1411 authentication method is used.
1414 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1415 option compiles in the support for adaptive spinning for lockmgrs
1416 which want to enable it. The lockinit() function now accepts the flag
1417 LK_ADAPTIVE in order to make the lock object subject to adaptive
1418 spinning when both held in write and read mode.
1421 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1422 changed. User applications that use this ioctl need to be rebuilt.
1425 The layout of struct thread has changed. Kernel and modules need to
1429 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1430 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1433 window(1) has been removed from the base system. It can now be
1434 installed from ports. The port is called misc/window.
1437 The way we are storing and accessing `routing table' entries has
1438 changed. Programs reading the FIB, like netstat, need to be
1442 A new netisr implementation has been added for FreeBSD 8. Network
1443 file system modules, such as igmp, ipdivert, and others, should be
1445 Bump __FreeBSD_version to 800096.
1448 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1452 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1453 Bump __FreeBSD_version to 800094.
1456 Add mnt_xflag field to 'struct mount'. File system modules need to be
1458 Bump __FreeBSD_version to 800093.
1461 The compiling option ADAPTIVE_SX has been retired while it has been
1462 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1463 The KPI for sx_init_flags() changes as accepting flags:
1464 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1465 been introduced in order to handle the reversed logic.
1466 Bump __FreeBSD_version to 800092.
1469 Add support for hierarchical jails. Remove global securelevel.
1470 Bump __FreeBSD_version to 800091.
1473 The layout of struct vnet_net has changed, therefore modules
1475 Bump __FreeBSD_version to 800090.
1478 The newly imported zic(8) produces a new format in the output. Please
1479 run tzsetup(8) to install the newly created data to /etc/localtime.
1482 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1483 hw.usb.* and is now consistent again with previous releases.
1486 802.11 monitor mode support was revised and driver api's were changed.
1487 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1488 of DLT_IEEE802_11. No user-visible data structures were changed but
1489 applications that use DLT_IEEE802_11 may require changes.
1490 Bump __FreeBSD_version to 800088.
1493 The layout of the following structs has changed: sysctl_oid,
1494 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1495 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1496 panics may be experienced. World rebuild is required for
1497 correctly checking networking state from userland.
1498 Bump __FreeBSD_version to 800085.
1501 MLDv2 and Source-Specific Multicast (SSM) have been merged
1502 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1503 The implementation of SSM within FreeBSD's IPv6 stack closely
1504 follows the IPv4 implementation.
1506 For kernel developers:
1508 * The most important changes are that the ip6_output() and
1509 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1510 and this lock has been downgraded to a non-recursive mutex.
1512 * As with the changes to the IPv4 stack to support SSM, filtering
1513 of inbound multicast traffic must now be performed by transport
1514 protocols within the IPv6 stack. This does not apply to TCP and
1515 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1517 * The KPIs used by IPv6 multicast are similar to those used by
1518 the IPv4 stack, with the following differences:
1519 * im6o_mc_filter() is analogous to imo_multicast_filter().
1520 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1521 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1522 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1523 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1524 for MLDv1 have an additional 'timer' argument which is used to
1525 jitter the initial membership report for the solicited-node
1526 multicast membership on-link.
1527 * This is not strictly needed for MLDv2, which already jitters
1528 its report transmissions. However, the 'timer' argument is
1529 preserved in case MLDv1 is active on the interface.
1531 * The KAME linked-list based IPv6 membership implementation has
1532 been refactored to use a vector similar to that used by the IPv4
1534 Code which maintains a list of its own multicast memberships
1535 internally, e.g. carp, has been updated to reflect the new
1538 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1539 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1540 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1541 implementation constraint which needs to be addressed in HEAD.
1543 For application developers:
1545 * The changes are broadly similar to those made for the IPv4
1548 * The use of IPv4 and IPv6 multicast socket options on the same
1549 socket, using mapped addresses, HAS NOT been tested or supported.
1551 * There are a number of issues with the implementation of various
1552 IPv6 multicast APIs which need to be resolved in the API surface
1553 before the implementation is fully compatible with KAME userland
1554 use, and these are mostly to do with interface index treatment.
1556 * The literature available discusses the use of either the delta / ASM
1557 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1558 using setsourcefilter(3)/getsourcefilter(3). For more information
1559 please refer to RFC 3768, 'Socket Interface Extensions for
1560 Multicast Source Filters'.
1562 * Applications which use the published RFC 3678 APIs should be fine.
1564 For systems administrators:
1566 * The mtest(8) utility has been refactored to support IPv6, in
1567 addition to IPv4. Interface addresses are no longer accepted
1568 as arguments, their names must be used instead. The utility
1569 will map the interface name to its first IPv4 address as
1570 returned by getifaddrs(3).
1572 * The ifmcstat(8) utility has also been updated to print the MLDv2
1573 endpoint state and source filter lists via sysctl(3).
1575 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1576 loopback of IPv6 multicast datagrams by default; it defaults to 1
1577 to preserve the existing behaviour. Disabling multicast loopback is
1578 recommended for optimal system performance.
1580 * The IPv6 MROUTING code has been changed to examine this sysctl
1581 instead of attempting to perform a group lookup before looping
1582 back forwarded datagrams.
1584 Bump __FreeBSD_version to 800084.
1587 Implement low-level Bluetooth HCI API.
1588 Bump __FreeBSD_version to 800083.
1591 The layout of struct malloc_type, used by modules to register new
1592 memory allocation types, has changed. Most modules will need to
1593 be rebuilt or panics may be experienced.
1594 Bump __FreeBSD_version to 800081.
1597 Anticipate overflowing inp_flags - add inp_flags2.
1598 This changes most offsets in inpcb, so checking v4 connection
1599 state will require a world rebuild.
1600 Bump __FreeBSD_version to 800080.
1603 Add an llentry to struct route and struct route_in6. Modules
1604 embedding a struct route will need to be recompiled.
1605 Bump __FreeBSD_version to 800079.
1608 The size of rt_metrics_lite and by extension rtentry has changed.
1609 Networking administration apps will need to be recompiled.
1610 The route command now supports show as an alias for get, weighting
1611 of routes, sticky and nostick flags to alter the behavior of stateful
1613 Bump __FreeBSD_version to 800078.
1616 Do not use Giant for kbdmux(4) locking. This is wrong and
1617 apparently causing more problems than it solves. This will
1618 re-open the issue where interrupt handlers may race with
1619 kbdmux(4) in polling mode. Typical symptoms include (but
1620 not limited to) duplicated and/or missing characters when
1621 low level console functions (such as gets) are used while
1622 interrupts are enabled (for example geli password prompt,
1623 mountroot prompt etc.). Disabling kbdmux(4) may help.
1626 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1627 kernel modules referencing any of the above need to be recompiled.
1628 Bump __FreeBSD_version to 800075.
1631 GEOM_PART has become the default partition slicer for storage devices,
1632 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1633 introduces some changes:
1635 MSDOS/EBR: the devices created from MSDOS extended partition entries
1636 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1637 to devices with offset-based names. fstabs may need to be modified.
1639 BSD: the "geometry does not match label" warning is harmless in most
1640 cases but it points to problems in file system misalignment with
1641 disk geometry. The "c" partition is now implicit, covers the whole
1642 top-level drive and cannot be (mis)used by users.
1644 General: Kernel dumps are now not allowed to be written to devices
1645 whose partition types indicate they are meant to be used for file
1646 systems (or, in case of MSDOS partitions, as something else than
1649 Most of these changes date approximately from 200812.
1652 The uscanner(4) driver has been removed from the kernel. This follows
1653 Linux removing theirs in 2.6 and making libusb the default interface
1654 (supported by sane).
1657 The multicast forwarding code has been cleaned up. netstat(1)
1658 only relies on KVM now for printing bandwidth upcall meters.
1659 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1660 ip6_mroute_mod respectively. The config(5) options for statically
1661 compiling this code remain the same, i.e. 'options MROUTING'.
1664 Support for the IFF_NEEDSGIANT network interface flag has been
1665 removed, which means that non-MPSAFE network device drivers are no
1666 longer supported. In particular, if_ar, if_sr, and network device
1667 drivers from the old (legacy) USB stack can no longer be built or
1671 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1672 a bunch of new language catalog files have also been added.
1673 This means that some common libc messages are now localized and
1674 they depend on the LC_MESSAGES environmental variable.
1677 The k8temp(4) driver has been renamed to amdtemp(4) since
1678 support for Family 10 and Family 11 CPU families was added.
1681 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1682 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1684 For kernel developers, the most important changes are that the
1685 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1686 and this lock has been downgraded to a non-recursive mutex.
1688 Transport protocols (UDP, Raw IP) are now responsible for filtering
1689 inbound multicast traffic according to group membership and source
1690 filters. The imo_multicast_filter() KPI exists for this purpose.
1691 Transports which do not use multicast (SCTP, TCP) already reject
1692 multicast by default. Forwarding and receive performance may improve
1693 as a mutex acquisition is no longer needed in the ip_input()
1694 low-level input path. in_addmulti() and in_delmulti() are shimmed
1695 to new KPIs which exist to support SSM in-kernel.
1697 For application developers, it is recommended that loopback of
1698 multicast datagrams be disabled for best performance, as this
1699 will still cause the lock to be taken for each looped-back
1700 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1701 be tuned to 0 to disable loopback by default; it defaults to 1
1702 to preserve the existing behaviour.
1704 For systems administrators, to obtain best performance with
1705 multicast reception and multiple groups, it is always recommended
1706 that a card with a suitably precise hash filter is used. Hash
1707 collisions will still result in the lock being taken within the
1708 transport protocol input path to check group membership.
1710 If deploying FreeBSD in an environment with IGMP snooping switches,
1711 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1712 enabled; this forces 224.0.0.0/24 group membership to be announced
1715 The size of 'struct igmpstat' has changed; netstat needs to be
1716 recompiled to reflect this.
1717 Bump __FreeBSD_version to 800070.
1720 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1721 updated to use it. This requires a buildworld/installworld in order to
1722 update the library and dependencies (usbconfig, etc). Its advisable to
1723 rebuild all ports which uses libusb. More specific directions are given
1724 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1725 libusb are no longer required and can be removed.
1728 A workaround is committed to allow the creation of System V shared
1729 memory segment of size > 2 GB on the 64-bit architectures.
1730 Due to a limitation of the existing ABI, the shm_segsz member
1731 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1732 wrong for large segments. Note that limits must be explicitly
1733 raised to allow such segments to be created.
1736 The layout of struct ifnet has changed, requiring a rebuild of all
1737 network device driver modules.
1740 The /dev handling for the new USB stack has changed, a
1741 buildworld/installworld is required for libusb20.
1744 The new USB2 stack has now been permanently moved in and all kernel and
1745 module names reverted to their previous values (eg, usb, ehci, ohci,
1746 ums, ...). The old usb stack can be compiled in by prefixing the name
1747 with the letter 'o', the old usb modules have been removed.
1748 Updating entry 20090216 for xorg and 20090215 for libmap may still
1752 The rc.conf(5) option if_up_delay has been renamed to
1753 defaultroute_delay to better reflect its purpose. If you have
1754 customized this setting in /etc/rc.conf you need to update it to
1758 xorg 7.4 wants to configure its input devices via hald which does not
1759 yet work with USB2. If the keyboard/mouse does not work in xorg then
1761 Option "AllowEmptyInput" "off"
1762 to your ServerLayout section. This will cause X to use the configured
1763 kbd and mouse sections from your xorg.conf.
1766 The GENERIC kernels for all architectures now default to the new USB2
1767 stack. No kernel config options or code have been removed so if a
1768 problem arises please report it and optionally revert to the old USB
1769 stack. If you are loading USB kernel modules or have a custom kernel
1770 that includes GENERIC then ensure that usb names are also changed over,
1771 eg uftdi -> usb2_serial_ftdi.
1773 Older programs linked against the ports libusb 0.1 need to be
1774 redirected to the new stack's libusb20. /etc/libmap.conf can
1776 # Map old usb library to new one for usb2 stack
1777 libusb-0.1.so.8 libusb20.so.1
1780 All USB ethernet devices now attach as interfaces under the name ueN
1781 (eg. ue0). This is to provide a predictable name as vendors often
1782 change usb chipsets in a product without notice.
1785 The ichsmb(4) driver has been changed to require SMBus slave
1786 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1787 All of the other SMBus controller drivers require left-justified
1788 slave addresses, so this change makes all the drivers provide the
1792 INET6 statistics (struct ip6stat) was updated.
1793 netstat(1) needs to be recompiled.
1796 NTFS has been removed from GENERIC kernel on amd64 to match
1797 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1798 will load ntfs.ko module automatically when NTFS support is
1799 actually needed, unless ntfs.ko is not installed or security
1800 level prohibits loading kernel modules. If either is the case,
1801 "options NTFS" has to be added into kernel config.
1804 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1805 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1806 800061. User space tools that rely on the size of struct tcpcb in
1807 tcp_var.h (e.g. sockstat) need to be recompiled.
1810 ng_tty(4) module updated to match the new TTY subsystem.
1811 Due to API change, user-level applications must be updated.
1812 New API support added to mpd5 CVS and expected to be present
1813 in next mpd5.3 release.
1816 With __FreeBSD_version 800060 the makefs tool is part of
1817 the base system (it was a port).
1820 The afdata and ifnet locks have been changed from mutexes to
1821 rwlocks, network modules will need to be re-compiled.
1824 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1825 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1826 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1827 architecture and 40 bytes on 64-bit architecture. The userland
1828 applications "arp" and "ndp" have been updated accordingly.
1829 The output from "netstat -r" shows only routing entries and
1830 none of the L2 information.
1833 __FreeBSD_version 800057 marks the switchover from the
1834 binary ath hal to source code. Users must add the line:
1836 options AH_SUPPORT_AR5416
1838 to their kernel config files when specifying:
1842 The ath_hal module no longer exists; the code is now compiled
1843 together with the driver in the ath module. It is now
1844 possible to tailor chip support (i.e. reduce the set of chips
1845 and thereby the code size); consult ath_hal(4) for details.
1848 __FreeBSD_version 800054 adds memory barriers to
1849 <machine/atomic.h>, new interfaces to ifnet to facilitate
1850 multiple hardware transmit queues for cards that support
1851 them, and a lock-less ring-buffer implementation to
1852 enable drivers to more efficiently manage queueing of
1856 A new version of ZFS (version 13) has been merged to -HEAD.
1857 This version has zpool attribute "listsnapshots" off by
1858 default, which means "zfs list" does not show snapshots,
1859 and is the same as Solaris behavior.
1862 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1865 The uhci, ohci, ehci and slhci USB Host controller drivers have
1866 been put into separate modules. If you load the usb module
1867 separately through loader.conf you will need to load the
1868 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1869 controller add the following to loader.conf:
1875 The ABI used by the PMC toolset has changed. Please keep
1876 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1880 atapci kernel module now includes only generic PCI ATA
1881 driver. AHCI driver moved to ataahci kernel module.
1882 All vendor-specific code moved into separate kernel modules:
1883 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1884 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1885 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1886 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1889 The TTY subsystem of the kernel has been replaced by a new
1890 implementation, which provides better scalability and an
1891 improved driver model. Most common drivers have been migrated to
1892 the new TTY subsystem, while others have not. The following
1893 drivers have not yet been ported to the new TTY layer:
1896 cy, digi, rc, rp, sio
1902 ng_h4, ng_tty, ppp, sl, snp
1904 Adding these drivers to your kernel configuration file shall
1905 cause compilation to fail.
1908 ntpd has been upgraded to 4.2.4p5.
1911 OpenSSH has been upgraded to 5.1p1.
1913 For many years, FreeBSD's version of OpenSSH preferred DSA
1914 over RSA for host and user authentication keys. With this
1915 upgrade, we've switched to the vendor's default of RSA over
1916 DSA. This may cause upgraded clients to warn about unknown
1917 host keys even for previously known hosts. Users should
1918 follow the usual procedure for verifying host keys before
1919 accepting the RSA key.
1921 This can be circumvented by setting the "HostKeyAlgorithms"
1922 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1925 Please note that the sequence of keys offered for
1926 authentication has been changed as well. You may want to
1927 specify IdentityFile in a different order to revert this
1931 The sio(4) driver has been removed from the i386 and amd64
1932 kernel configuration files. This means uart(4) is now the
1933 default serial port driver on those platforms as well.
1935 To prevent collisions with the sio(4) driver, the uart(4) driver
1936 uses different names for its device nodes. This means the
1937 onboard serial port will now most likely be called "ttyu0"
1938 instead of "ttyd0". You may need to reconfigure applications to
1939 use the new device names.
1941 When using the serial port as a boot console, be sure to update
1942 /boot/device.hints and /etc/ttys before booting the new kernel.
1943 If you forget to do so, you can still manually specify the hints
1944 at the loader prompt:
1946 set hint.uart.0.at="isa"
1947 set hint.uart.0.port="0x3F8"
1948 set hint.uart.0.flags="0x10"
1949 set hint.uart.0.irq="4"
1953 The gpt(8) utility has been removed. Use gpart(8) to partition
1957 The version that Linuxulator emulates was changed from 2.4.2
1958 to 2.6.16. If you experience any problems with Linux binaries
1959 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1960 if it fixes the problem contact emulation mailing list.
1963 ISDN4BSD (I4B) was removed from the src tree. You may need to
1964 update a your kernel configuration and remove relevant entries.
1967 I have checked in code to support multiple routing tables.
1968 See the man pages setfib(1) and setfib(2).
1969 This is a hopefully backwards compatible version,
1970 but to make use of it you need to compile your kernel
1971 with options ROUTETABLES=2 (or more up to 16).
1974 The 802.11 wireless support was redone to enable multi-bss
1975 operation on devices that are capable. The underlying device
1976 is no longer used directly but instead wlanX devices are
1977 cloned with ifconfig. This requires changes to rc.conf files.
1978 For example, change:
1979 ifconfig_ath0="WPA DHCP"
1982 ifconfig_wlan0="WPA DHCP"
1983 see rc.conf(5) for more details. In addition, mergemaster of
1984 /etc/rc.d is highly recommended. Simultaneous update of userland
1985 and kernel wouldn't hurt either.
1987 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1988 modules were merged into the base wlan module. All references
1989 to these modules (e.g. in kernel config files) must be removed.
1992 psm(4) has gained write(2) support in native operation level.
1993 Arbitrary commands can be written to /dev/psm%d and status can
1994 be read back from it. Therefore, an application is responsible
1995 for status validation and error recovery. It is a no-op in
1996 other operation levels.
1999 Support for KSE threading has been removed from the kernel. To
2000 run legacy applications linked against KSE libmap.conf may
2001 be used. The following libmap.conf may be used to ensure
2002 compatibility with any prior release:
2004 libpthread.so.1 libthr.so.1
2005 libpthread.so.2 libthr.so.2
2006 libkse.so.3 libthr.so.3
2009 The layout of struct vmspace has changed. This affects libkvm
2010 and any executables that link against libkvm and use the
2011 kvm_getprocs() function. In particular, but not exclusively,
2012 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2013 The effects are minimal, but it's advisable to upgrade world
2017 The latest em driver no longer has support in it for the
2018 82575 adapter, this is now moved to the igb driver. The
2019 split was done to make new features that are incompatible
2020 with older hardware easier to do.
2023 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2024 likewise the kernel option is now GEOM_LINUX_LVM.
2027 The default NFS mount mode has changed from UDP to TCP for
2028 increased reliability. If you rely on (insecurely) NFS
2029 mounting across a firewall you may need to update your
2033 Belatedly note the addition of m_collapse for compacting
2037 The fts(3) structures have been changed to use adequate
2038 integer types for their members and so to be able to cope
2039 with huge file trees. The old fts(3) ABI is preserved
2040 through symbol versioning in libc, so third-party binaries
2041 using fts(3) should still work, although they will not take
2042 advantage of the extended types. At the same time, some
2043 third-party software might fail to build after this change
2044 due to unportable assumptions made in its source code about
2045 fts(3) structure members. Such software should be fixed
2046 by its vendor or, in the worst case, in the ports tree.
2047 FreeBSD_version 800015 marks this change for the unlikely
2048 case that a portable fix is impossible.
2051 To upgrade to -current after this date, you must be running
2052 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2053 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2056 The ADAPTIVE_GIANT kernel option has been retired because its
2057 functionality is the default now.
2060 The AT keyboard emulation of sunkbd(4) has been turned on
2061 by default. In order to make the special symbols of the Sun
2062 keyboards driven by sunkbd(4) work under X these now have
2063 to be configured the same way as Sun USB keyboards driven
2064 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2066 Option "XkbLayout" "us"
2067 Option "XkbRules" "xorg"
2068 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2071 It has been decided that it is desirable to provide ABI
2072 backwards compatibility to the FreeBSD 4/5/6 versions of the
2073 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2074 broken with the introduction of PCI domain support (see the
2075 20070930 entry). Unfortunately, this required the ABI of
2076 PCIOCGETCONF to be broken again in order to be able to
2077 provide backwards compatibility to the old version of that
2078 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2079 again. As for prominent ports this affects neither pciutils
2080 nor xorg-server this time, the hal port needs to be rebuilt
2084 The misnamed kthread_create() and friends have been renamed
2085 to kproc_create() etc. Many of the callers already
2086 used kproc_start()..
2087 I will return kthread_create() and friends in a while
2088 with implementations that actually create threads, not procs.
2089 Renaming corresponds with version 800002.
2098 Avoid using make -j when upgrading. While generally safe, there are
2099 sometimes problems using -j to upgrade. If your upgrade fails with
2100 -j, please try again without -j. From time to time in the past there
2101 have been problems using -j with buildworld and/or installworld. This
2102 is especially true when upgrading between "distant" versions (eg one
2103 that cross a major release boundary or several minor releases, or when
2104 several months have passed on the -current branch).
2106 Sometimes, obscure build problems are the result of environment
2107 poisoning. This can happen because the make utility reads its
2108 environment when searching for values for global variables. To run
2109 your build attempts in an "environmental clean room", prefix all make
2110 commands with 'env -i '. See the env(1) manual page for more details.
2112 When upgrading from one major version to another it is generally best
2113 to upgrade to the latest code in the currently installed branch first,
2114 then do an upgrade to the new branch. This is the best-tested upgrade
2115 path, and has the highest probability of being successful. Please try
2116 this approach before reporting problems with a major version upgrade.
2118 When upgrading a live system, having a root shell around before
2119 installing anything can help undo problems. Not having a root shell
2120 around can lead to problems if pam has changed too much from your
2121 starting point to allow continued authentication after the upgrade.
2125 When upgrading the boot ZFS pool to a new version, always follow
2128 1.) recompile and reinstall the ZFS boot loader and boot block
2129 (this is part of "make buildworld" and "make installworld")
2131 2.) update the ZFS boot block on your boot drive
2133 The following example updates the ZFS boot block on the first
2134 partition (freebsd-boot) of a GPT partitioned drive ad0:
2135 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2137 Non-boot pools do not need these updates.
2141 If you are updating from a prior version of FreeBSD (even one just
2142 a few days old), you should follow this procedure. It is the most
2143 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2145 make kernel-toolchain
2146 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2147 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2149 To test a kernel once
2150 ---------------------
2151 If you just want to boot a kernel once (because you are not sure
2152 if it works, or if you want to boot a known bad kernel to provide
2153 debugging information) run
2154 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2155 nextboot -k testkernel
2157 To just build a kernel when you know that it won't mess you up
2158 --------------------------------------------------------------
2159 This assumes you are already running a CURRENT system. Replace
2160 ${arch} with the architecture of your machine (e.g. "i386",
2161 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2163 cd src/sys/${arch}/conf
2164 config KERNEL_NAME_HERE
2165 cd ../compile/KERNEL_NAME_HERE
2170 If this fails, go to the "To build a kernel" section.
2172 To rebuild everything and install it on the current system.
2173 -----------------------------------------------------------
2174 # Note: sometimes if you are running current you gotta do more than
2175 # is listed here if you are upgrading from a really old current.
2177 <make sure you have good level 0 dumps>
2179 make kernel KERNCONF=YOUR_KERNEL_HERE
2181 <reboot in single user> [3]
2188 To cross-install current onto a separate partition
2189 --------------------------------------------------
2190 # In this approach we use a separate partition to hold
2191 # current's root, 'usr', and 'var' directories. A partition
2192 # holding "/", "/usr" and "/var" should be about 2GB in
2195 <make sure you have good level 0 dumps>
2198 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2199 <maybe newfs current's root partition>
2200 <mount current's root partition on directory ${CURRENT_ROOT}>
2201 make installworld DESTDIR=${CURRENT_ROOT}
2202 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2203 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2204 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2205 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2206 <reboot into current>
2207 <do a "native" rebuild/install as described in the previous section>
2208 <maybe install compatibility libraries from ports/misc/compat*>
2212 To upgrade in-place from stable to current
2213 ----------------------------------------------
2214 <make sure you have good level 0 dumps>
2216 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2218 <reboot in single user> [3]
2225 Make sure that you've read the UPDATING file to understand the
2226 tweaks to various things you need. At this point in the life
2227 cycle of current, things change often and you are on your own
2228 to cope. The defaults can also change, so please read ALL of
2229 the UPDATING entries.
2231 Also, if you are tracking -current, you must be subscribed to
2232 freebsd-current@freebsd.org. Make sure that before you update
2233 your sources that you have read and understood all the recent
2234 messages there. If in doubt, please track -stable which has
2235 much fewer pitfalls.
2237 [1] If you have third party modules, such as vmware, you
2238 should disable them at this point so they don't crash your
2241 [3] From the bootblocks, boot -s, and then do
2246 adjkerntz -i # if CMOS is wall time
2247 Also, when doing a major release upgrade, it is required that
2248 you boot into single user mode to do the installworld.
2250 [4] Note: This step is non-optional. Failure to do this step
2251 can result in a significant reduction in the functionality of the
2252 system. Attempting to do it by hand is not recommended and those
2253 that pursue this avenue should read this file carefully, as well
2254 as the archives of freebsd-current and freebsd-hackers mailing lists
2255 for potential gotchas. The -U option is also useful to consider.
2256 See mergemaster(8) for more information.
2258 [5] Usually this step is a noop. However, from time to time
2259 you may need to do this if you get unknown user in the following
2260 step. It never hurts to do it all the time. You may need to
2261 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2262 install) after the buildworld before this step if you last updated
2263 from current before 20130425 or from -stable before 20130430.
2265 [6] This only deletes old files and directories. Old libraries
2266 can be deleted by "make delete-old-libs", but you have to make
2267 sure that no program is using those libraries anymore.
2269 [8] In order to have a kernel that can run the 4.x binaries needed to
2270 do an installworld, you must include the COMPAT_FREEBSD4 option in
2271 your kernel. Failure to do so may leave you with a system that is
2272 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2273 required to run the 5.x binaries on more recent kernels. And so on
2274 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2276 Make sure that you merge any new devices from GENERIC since the
2277 last time you updated your kernel config file.
2279 [9] When checking out sources, you must include the -P flag to have
2280 cvs prune empty directories.
2282 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2283 "?=" instead of the "=" assignment operator, so that buildworld can
2284 override the CPUTYPE if it needs to.
2286 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2287 not on the command line, or in /etc/make.conf. buildworld will
2288 warn if it is improperly defined.
2291 This file contains a list, in reverse chronological order, of major
2292 breakages in tracking -current. It is not guaranteed to be a complete
2293 list of such breakages, and only contains entries since October 10, 2007.
2294 If you need to see UPDATING entries from before that date, you will need
2295 to fetch an UPDATING file from an older FreeBSD release.
2297 Copyright information:
2299 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2301 Redistribution, publication, translation and use, with or without
2302 modification, in full or in part, in any form or format of this
2303 document are permitted without further permission from the author.
2305 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2306 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2307 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2308 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2309 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2310 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2311 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2312 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2313 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2314 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2315 POSSIBILITY OF SUCH DAMAGE.
2317 Contact Warner Losh if you have any questions about your use of