1 Updating Information for FreeBSD stable/10 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 The releng/10.4 branch has been created from stable/10@r323601
37 Since the switch to GPT disk labels, fsck for UFS/FFS has been
38 unable to automatically find alternate superblocks. As of r322860,
39 the information needed to find alternate superblocks has been
40 moved to the end of the area reserved for the boot block.
41 Filesystems created with a newfs of this vintage or later
42 will create the recovery information. If you have a filesystem
43 created prior to this change and wish to have a recovery block
44 created for your filesystem, you can do so by running fsck in
45 forground mode (i.e., do not use the -p or -y options). As it
46 starts, fsck will ask ``SAVE DATA TO FIND ALTERNATE SUPERBLOCKS''
47 to which you should answer yes.
50 The mmcsd.ko module now additionally depends on geom_flashmap.ko.
51 Also, mmc.ko and mmcsd.ko need to be a matching pair built from the
52 same source (previously, the dependency of mmcsd.ko on mmc.ko was
53 missing, but mmcsd.ko now will refuse to load if it is incompatible
57 As of r316810 for ipfilter, keep frags is no longer assumed when
58 keep state is specified in a rule. r316810 aligns ipfilter with
59 documentation in man pages separating keep frags from keep state.
60 This allows keep state to specified without forcing keep frags
61 and allows keep frags to be specified independently of keep state.
62 To maintain previous behaviour, also specify keep frags with
63 keep state (as documented in ipf.conf.5).
66 The code that provides support for ZFS .zfs/ directory functionality
67 has been reimplemented. It's not possible now to create a snapshot
68 by mkdir under .zfs/snapshot/. That should be the only user visible
72 The releng/10.3 branch has been created from stable/10@r296371
75 The NONE and HPN patches has been removed from OpenSSH. They are
76 still available in the security/openssh-portable port.
79 r292223 changed the internal interface between the nfsd.ko and
80 nfscommon.ko modules. As such, they must both be upgraded to-gether.
81 __FreeBSD_version has been bumped because of this.
84 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
85 Kernel modules isp_2400_multi and isp_2500_multi were removed and
86 should be replaced with isp_2400 and isp_2500 modules respectively.
89 The menu.rc and loader.rc files will now be replaced during
90 upgrades. Please migrate local changes to menu.rc.local and
91 loader.rc.local instead.
94 NTP has been upgraded to 4.2.8p4.
97 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
98 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
99 and devel/kyua to version 0.20+ and adjust any calling code to work
100 with Kyuafile and kyua.
103 The polarity of Pulse Per Second (PPS) capture events with the
104 uart(4) driver has been corrected. Prior to this change the PPS
105 "assert" event corresponded to the trailing edge of a positive PPS
106 pulse and the "clear" event was the leading edge of the next pulse.
108 As the width of a PPS pulse in a typical GPS receiver is on the
109 order of 1 millisecond, most users will not notice any significant
110 difference with this change.
112 Anyone who has compensated for the historical polarity reversal by
113 configuring a negative offset equal to the pulse width will need to
114 remove that workaround.
117 From legacy ata(4) driver was removed support for SATA controllers
118 supported by more functional drivers ahci(4), siis(4) and mvs(4).
119 Kernel modules ataahci and ataadaptec were removed completely,
120 replaced by ahci and mvs modules respectively.
126 As ZFS requires more kernel stack pages than is the default on some
127 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
128 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
130 Please consider using 'options KSTACK_PAGES=X' where X is greater
131 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
134 The releng/10.2 branch has been created from stable/10@r285827
137 The default Unbound configuration now enables remote control
138 using a local socket. Users who have already enabled the
139 local_unbound service should regenerate their configuration
140 by running "service local_unbound setup" as root.
143 An additional fix for the issue described in the 20150614 sendmail
144 entry below has been been committed in revision 284786.
147 The fix for the issue described in the 20150614 sendmail entry
148 below has been been committed in revision 284485. The work
149 around described in that entry is no longer needed unless the
150 default setting is overridden by a confDH_PARAMETERS configuration
151 setting of '5' or pointing to a 512 bit DH parameter file.
154 The import of openssl to address the FreeBSD-SA-15:10.openssl
155 security advisory includes a change which rejects handshakes
156 with DH parameters below 768 bits. sendmail releases prior
157 to 8.15.2 (not yet released), defaulted to a 512 bit
158 DH parameter setting for client connections. To work around
159 this interoperability, sendmail can be configured to use a
160 2048 bit DH parameter by:
162 1. Edit /etc/mail/`hostname`.mc
163 2. If a setting for confDH_PARAMETERS does not exist or
164 exists and is set to a string beginning with '5',
166 3. If a setting for confDH_PARAMETERS exists and is set to
167 a file path, create a new file with:
168 openssl dhparam -out /path/to/file 2048
169 4. Rebuild the .cf file:
170 cd /etc/mail/; make; make install
172 cd /etc/mail/; make restart
174 A sendmail patch is coming, at which time this file will be
178 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
179 defined in symlink(7); previously symlinks were silently ignored.
182 The const qualifier has been removed from iconv(3) to comply with
183 POSIX. The ports tree is aware of this from r384038 onwards.
186 At svn r275807, The default linux compat kernel ABI has been adjusted
187 to 2.6.18 in support of the linux-c6 compat ports infrastructure
188 update. If you wish to continue using the linux-f10 compat ports,
189 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
190 encouraged to update their linux-compat packages to linux-c6 during
191 their next update cycle.
193 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
196 pjdfstest has been integrated into kyua as an opt-in test suite.
197 Please see share/doc/pjdfstest/README for a more details on how to
204 The releng/10.1 branch has been created from stable/10@r272459.
207 The ofwfb driver, used to provide a graphics console on PowerPC when
208 using vt(4), no longer allows mmap() of all of physical memory. This
209 will prevent Xorg on PowerPC with some ATI graphics cards from
210 initializing properly unless x11-servers/xorg-server is updated to
214 The libatf-c and libatf-c++ major versions were downgraded to 0 and
215 1 respectively to match the upstream numbers. They were out of
216 sync because, when they were originally added to FreeBSD, the
217 upstream versions were not respected. These libraries are private
218 and not yet built by default, so renumbering them should be a
219 non-issue. However, unclean source trees will yield broken test
220 programs once the operator executes "make delete-old-libs" after a
223 Additionally, the atf-sh binary was made private by moving it into
224 /usr/libexec/. Already-built shell test programs will keep the
225 path to the old binary so they will break after "make delete-old"
228 If you are using WITH_TESTS=yes (not the default), wipe the object
229 tree and rebuild from scratch to prevent spurious test failures.
230 This is only needed once: the misnumbered libraries and misplaced
231 binaries have been added to OptionalObsoleteFiles.inc so they will
232 be removed during a clean upgrade.
235 The ixgbe tunables now match their sysctl counterparts, for example:
236 hw.ixgbe.enable_aim => hw.ix.enable_aim
237 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
240 The NFSv4.1 server committed by r269398 changes the internal
241 function call interfaces used between the NFS and krpc modules.
242 As such, __FreeBSD_version was bumped.
245 The default unbound configuration has been modified to address
246 issues with reverse lookups on networks that use private
247 address ranges. If you use the local_unbound service, run
248 "service local_unbound setup" as root to regenerate your
249 configuration, then "service local_unbound reload" to load the
253 It is no longer necessary to include the dwarf version in your DEBUG
254 options in your kernel config file. The bug that required it to be
255 placed in the config file has bene fixed. DEBUG should now just
256 contain -g. The build system will automatically update things
257 to do the right thing.
260 Several ABI breaking changes were merged to CTL and new iSCSI code.
261 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
262 iscsictl need to be rebuilt to work with a new kernel.
265 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
266 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
267 which differs from the behaviour controlled by this knob.)
270 On i386 and amd64 systems, the onifconsole flag is now set by default
271 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
272 as a login TTY if it is set in the bootloader as an active kernel
273 console. No changes in behavior should result otherwise. To revert to
274 the previous behavior, set ttyu0 to "off" in /etc/ttys.
277 Clang and llvm have been upgraded to 3.4.1 release.
280 Clang and llvm have been upgraded to 3.4 release.
283 If a Makefile in a tests/ directory was auto-generating a Kyuafile
284 instead of providing an explicit one, this would prevent such
285 Makefile from providing its own Kyuafile in the future during
286 NO_CLEAN builds. This has been fixed in the Makefiles but manual
287 intervention is needed to clean an objdir if you use NO_CLEAN:
288 # find /usr/obj -name Kyuafile | xargs rm -f
291 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
292 capability mode support. Please note that enabling the feature in
293 kernel is still highly recommended.
296 OpenSSH is now built with sandbox support, and will use sandbox as
297 the default privilege separation method. This requires Capsicum
298 capability mode support in kernel.
301 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
302 been deprecated and will not be part of FreeBSD 11.0 and later
303 releases. If you use this driver, please consider switching to
304 the nfe(4) driver instead.
310 The behavior of gss_pseudo_random() for the krb5 mechanism
311 has changed, for applications requesting a longer random string
312 than produced by the underlying enctype's pseudo-random() function.
313 In particular, the random string produced from a session key of
314 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
315 be different at the 17th octet and later, after this change.
316 The counter used in the PRF+ construction is now encoded as a
317 big-endian integer in accordance with RFC 4402.
318 __FreeBSD_version is bumped to 1000701.
321 The releng/10.0 branch has been created from stable/10@r259064.
324 The WITHOUT_ATF build knob has been removed and its functionality
325 has been subsumed into the more generic WITHOUT_TESTS. If you were
326 using the former to disable the build of the ATF libraries, you
327 should change your settings to use the latter.
330 The default version of mtree is nmtree which is obtained from
331 NetBSD. The output is generally the same, but may vary
332 slightly. If you found you need identical output adding
333 "-F freebsd9" to the command line should do the trick. For the
334 time being, the old mtree is available as fmtree.
337 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
338 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
339 1.1.4_8 and verify bsdyml not linked in, before running "make
341 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
343 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
346 The stable/10 branch has been created in subversion from head
350 The rc.d/jail script has been updated to support jail(8)
351 configuration file. The "jail_<jname>_*" rc.conf(5) variables
352 for per-jail configuration are automatically converted to
353 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
354 This is transparently backward compatible. See below about some
355 incompatibilities and rc.conf(5) manual page for more details.
357 These variables are now deprecated in favor of jail(8) configuration
358 file. One can use "rc.d/jail config <jname>" command to generate
359 a jail(8) configuration file in /var/run/jail.<jname>.conf without
360 running the jail(8) utility. The default pathname of the
361 configuration file is /etc/jail.conf and can be specified by
362 using $jail_conf or $jail_<jname>_conf variables.
364 Please note that jail_devfs_ruleset accepts an integer at
365 this moment. Please consider to rewrite the ruleset name
369 BIND has been removed from the base system. If all you need
370 is a local resolver, simply enable and start the local_unbound
371 service instead. Otherwise, several versions of BIND are
372 available in the ports tree. The dns/bind99 port is one example.
374 With this change, nslookup(1) and dig(1) are no longer in the base
375 system. Users should instead use host(1) and drill(1) which are
376 in the base system. Alternatively, nslookup and dig can
377 be obtained by installing the dns/bind-tools port.
380 With the addition of unbound(8), a new unbound user is now
381 required during installworld. "mergemaster -p" can be used to
382 add the user prior to installworld, as documented in the handbook.
385 OpenSSH is now built with DNSSEC support, and will by default
386 silently trust signed SSHFP records. This can be controlled with
387 the VerifyHostKeyDNS client configuration setting. DNSSEC support
388 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
391 The GNU Compiler Collection and C++ standard library (libstdc++)
392 are no longer built by default on platforms where clang is the system
393 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
397 The PROCDESC kernel option is now part of the GENERIC kernel
398 configuration and is required for the rwhod(8) to work.
399 If you are using custom kernel configuration, you should include
403 The API and ABI related to the Capsicum framework was modified
404 in backward incompatible way. The userland libraries and programs
405 have to be recompiled to work with the new kernel. This includes the
406 following libraries and programs, but the whole buildworld is
407 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
408 kdump, procstat, rwho, rwhod, uniq.
411 AES-NI intrinsic support has been added to gcc. The AES-NI module
412 has been updated to use this support. A new gcc is required to build
413 the aesni module on both i386 and amd64.
416 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
417 Thus "device padlock_rng" and "device rdrand_rng" should be
418 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
421 WITH_ICONV has been split into two feature sets. WITH_ICONV now
422 enables just the iconv* functionality and is now on by default.
423 WITH_LIBICONV_COMPAT enables the libiconv api and link time
424 compatability. Set WITHOUT_ICONV to build the old way.
425 If you have been using WITH_ICONV before, you will very likely
426 need to turn on WITH_LIBICONV_COMPAT.
429 INVARIANTS option now enables DEBUG for code with OpenSolaris and
430 Illumos origin, including ZFS. If you have INVARIANTS in your
431 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
433 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
434 locks if WITNESS option was set. Because that generated a lot of
435 witness(9) reports and all of them were believed to be false
436 positives, this is no longer done. New option OPENSOLARIS_WITNESS
437 can be used to achieve the previous behavior.
440 Timer values in IPv6 data structures now use time_uptime instead
441 of time_second. Although this is not a user-visible functional
442 change, userland utilities which directly use them---ndp(8),
443 rtadvd(8), and rtsold(8) in the base system---need to be updated
447 find -delete can now delete the pathnames given as arguments,
448 instead of only files found below them or if the pathname did
449 not contain any slashes. Formerly, the following error message
452 find: -delete: <path>: relative path potentially not safe
454 Deleting the pathnames given as arguments can be prevented
455 without error messages using -mindepth 1 or by changing
456 directory and passing "." as argument to find. This works in the
457 old as well as the new version of find.
460 Behavior of devfs rules path matching has been changed.
461 Pattern is now always matched against fully qualified devfs
462 path and slash characters must be explicitly matched by
463 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
464 subdirectories must be reviewed.
467 The default ARM ABI has changed to the ARM EABI. The old ABI is
468 incompatible with the ARM EABI and all programs and modules will
469 need to be rebuilt to work with a new kernel.
471 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
473 NOTE: Support for the old ABI will be removed in the future and
474 users are advised to upgrade.
477 pkg_install has been disconnected from the build if you really need it
478 you should add WITH_PKGTOOLS in your src.conf(5).
481 Most of network statistics structures were changed to be able
482 keep 64-bits counters. Thus all tools, that work with networking
483 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
486 Fix a bug that allowed a tracing process (e.g. gdb) to write
487 to a memory-mapped file in the traced process's address space
488 even if neither the traced process nor the tracing process had
489 write access to that file.
492 CVS has been removed from the base system. An exact copy
493 of the code is available from the devel/cvs port.
496 Some people report the following error after the switch to bmake:
498 make: illegal option -- J
499 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
501 *** [buildworld] Error code 2
503 this likely due to an old instance of make in
504 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
505 which src/Makefile will use that blindly, if it exists, so if
506 you see the above error:
508 rm -rf `make -V MAKEPATH`
513 Use bmake by default.
514 Whereas before one could choose to build with bmake via
515 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
516 make. The goal is to remove these knobs for 10-RELEASE.
518 It is worth noting that bmake (like gmake) treats the command
519 line as the unit of failure, rather than statements within the
520 command line. Thus '(cd some/where && dosomething)' is safer
521 than 'cd some/where; dosomething'. The '()' allows consistent
522 behavior in parallel build.
525 Fix a bug that allows NFS clients to issue READDIR on files.
528 The WITHOUT_IDEA option has been removed because
529 the IDEA patent expired.
532 The sysctl which controls TRIM support under ZFS has been renamed
533 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
537 The mergemaster command now uses the default MAKEOBJDIRPREFIX
538 rather than creating it's own in the temporary directory in
539 order allow access to bootstrapped versions of tools such as
540 install and mtree. When upgrading from version of FreeBSD where
541 the install command does not support -l, you will need to
542 install a new mergemaster command if mergemaster -p is required.
543 This can be accomplished with the command (cd src/usr.sbin/mergemaster
547 Legacy ATA stack, disabled and replaced by new CAM-based one since
548 FreeBSD 9.0, completely removed from the sources. Kernel modules
549 atadisk and atapi*, user-level tools atacontrol and burncd are
550 removed. Kernel option `options ATA_CAM` is now permanently enabled
554 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
555 and socketpair(2). Software, in particular Kerberos, may
556 automatically detect and use these during building. The resulting
557 binaries will not work on older kernels.
560 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
561 information, see the respective 20130304 entry).
564 Recent commits to callout(9) changed the size of struct callout,
565 so the KBI is probably heavily disturbed. Also, some functions
566 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
567 by macros. Every kernel module using it won't load, so rebuild
570 The ctl device has been re-enabled in GENERIC for i386 and amd64,
571 but does not initialize by default (because of the new CTL_DISABLE
572 option) to save memory. To re-enable it, remove the CTL_DISABLE
573 option from the kernel config file or set kern.cam.ctl.disable=0
574 in /boot/loader.conf.
577 The ctl device has been disabled in GENERIC for i386 and amd64.
578 This was done due to the extra memory being allocated at system
579 initialisation time by the ctl driver which was only used if
580 a CAM target device was created. This makes a FreeBSD system
581 unusable on 128MB or less of RAM.
584 A new compression method (lz4) has been merged to -HEAD. Please
585 refer to zpool-features(7) for more information.
587 Please refer to the "ZFS notes" section of this file for information
588 on upgrading boot ZFS pools.
591 A BSD-licensed patch(1) variant has been added and is installed
592 as bsdpatch, being the GNU version the default patch.
593 To inverse the logic and use the BSD-licensed one as default,
594 while having the GNU version installed as gnupatch, rebuild
595 and install world with the WITH_BSD_PATCH knob set.
598 Due to the use of the new -l option to install(1) during build
599 and install, you must take care not to directly set the INSTALL
600 make variable in your /etc/make.conf, /etc/src.conf, or on the
601 command line. If you wish to use the -C flag for all installs
602 you may be able to add INSTALL+=-C to /etc/make.conf or
606 The install(1) option -M has changed meaning and now takes an
607 argument that is a file or path to append logs to. In the
608 unlikely event that -M was the last option on the command line
609 and the command line contained at least two files and a target
610 directory the first file will have logs appended to it. The -M
611 option served little practical purpose in the last decade so its
612 use is expected to be extremely rare.
615 After switching to Clang as the default compiler some users of ZFS
616 on i386 systems started to experience stack overflow kernel panics.
617 Please consider using 'options KSTACK_PAGES=4' in such configurations.
620 GEOM_LABEL now mangles label names read from file system metadata.
621 Mangling affect labels containing spaces, non-printable characters,
622 '%' or '"'. Device names in /etc/fstab and other places may need to
626 By default, only the 10 most recent kernel dumps will be saved. To
627 restore the previous behaviour (no limit on the number of kernel dumps
628 stored in the dump directory) add the following line to /etc/rc.conf:
633 With the addition of auditdistd(8), a new auditdistd user is now
634 required during installworld. "mergemaster -p" can be used to
635 add the user prior to installworld, as documented in the handbook.
638 The sin6_scope_id member variable in struct sockaddr_in6 is now
639 filled by the kernel before passing the structure to the userland via
640 sysctl or routing socket. This means the KAME-specific embedded scope
641 id in sin6_addr.s6_addr[2] is always cleared in userland application.
642 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
643 __FreeBSD_version is bumped to 1000025.
646 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
647 This means that the world and kernel will be compiled with clang
648 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
649 and /usr/bin/cpp. To disable this behavior and revert to building
650 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
651 of current may need to bootstrap WITHOUT_CLANG first if the clang
652 build fails (its compatibility window doesn't extend to the 9 stable
656 The IPFIREWALL_FORWARD kernel option has been removed. Its
657 functionality now turned on by default.
660 The ZERO_COPY_SOCKET kernel option has been removed and
661 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
662 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
663 mechanism which is not safe and may result in kernel crashes.
664 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
665 driver supports disposeable external page sized mbuf storage.
666 Proper replacements for both zero-copy mechanisms are under
667 consideration and will eventually lead to complete removal
668 of the two kernel options.
671 The IPv4 network stack has been converted to network byte
672 order. The following modules need to be recompiled together
673 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
674 pf(4), ipfw(4), ng_ipfw(4), stf(4).
677 Support for non-MPSAFE filesystems was removed from VFS. The
678 VFS_VERSION was bumped, all filesystem modules shall be
682 All the non-MPSAFE filesystems have been disconnected from
683 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
684 portalfs, smbfs, xfs.
687 The interface cloning API and ABI has changed. The following
688 modules need to be recompiled together with kernel:
689 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
690 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
691 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
694 The sdhci driver was split in two parts: sdhci (generic SD Host
695 Controller logic) and sdhci_pci (actual hardware driver).
696 No kernel config modifications are required, but if you
697 load sdhc as a module you must switch to sdhci_pci instead.
700 Import the FUSE kernel and userland support into base system.
703 The GNU sort(1) program has been removed since the BSD-licensed
704 sort(1) has been the default for quite some time and no serious
705 problems have been reported. The corresponding WITH_GNU_SORT
709 The pfil(9) API/ABI for AF_INET family has been changed. Packet
710 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
714 The net80211(4) ABI has been changed to allow for improved driver
715 PS-POLL and power-save support. All wireless drivers need to be
716 recompiled to work with the new kernel.
719 The random(4) support for the VIA hardware random number
720 generator (`PADLOCK') is no longer enabled unconditionally.
721 Add the padlock_rng device in the custom kernel config if
722 needed. The GENERIC kernels on i386 and amd64 do include the
723 device, so the change only affects the custom kernel
727 The pf(4) packet filter ABI has been changed. pfctl(8) and
728 snmp_pf module need to be recompiled to work with new kernel.
731 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
732 to -HEAD. Pools that have empty_bpobj in active state can not be
733 imported read-write with ZFS implementations that do not support
734 this feature. For more information read the zpool-features(5)
738 The sparc64 ZFS loader has been changed to no longer try to auto-
739 detect ZFS providers based on diskN aliases but now requires these
740 to be explicitly listed in the OFW boot-device environment variable.
743 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
744 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
745 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
748 The following sysctls and tunables have been renamed for consistency
749 with other variables:
750 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
751 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
754 The sort utility has been replaced with BSD sort. For now, GNU sort
755 is also available as "gnusort" or the default can be set back to
756 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
757 installed as "bsdsort".
760 A new version of ZFS (pool version 5000) has been merged to -HEAD.
761 Starting with this version the old system of ZFS pool versioning
762 is superseded by "feature flags". This concept enables forward
763 compatibility against certain future changes in functionality of ZFS
764 pools. The first read-only compatible "feature flag" for ZFS pools
765 is named "com.delphix:async_destroy". For more information
766 read the new zpool-features(5) manual page.
767 Please refer to the "ZFS notes" section of this file for information
768 on upgrading boot ZFS pools.
771 The malloc(3) implementation embedded in libc now uses sources imported
772 as contrib/jemalloc. The most disruptive API change is to
773 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
774 delete it prior to installworld, and optionally re-create it using the
775 new format after rebooting. See malloc.conf(5) for details
776 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
780 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
781 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
782 now spelled mips. This is to aid compatibility with third-party
783 software that expects this naming scheme in uname(3). Little-endian
784 settings are unchanged. If you are updating a big-endian mips64 machine
785 from before this change, you may need to set MACHINE_ARCH=mips64 in
786 your environment before the new build system will recognize your machine.
789 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
793 Now unix domain sockets behave "as expected" on nullfs(5). Previously
794 nullfs(5) did not pass through all behaviours to the underlying layer,
795 as a result if we bound to a socket on the lower layer we could connect
796 only to the lower path; if we bound to the upper layer we could connect
797 only to the upper path. The new behavior is one can connect to both the
798 lower and the upper paths regardless what layer path one binds to.
801 The getifaddrs upgrade path broken with 20111215 has been restored.
802 If you have upgraded in between 20111215 and 20120209 you need to
803 recompile libc again with your kernel. You still need to recompile
804 world to be able to configure CARP but this restriction already
808 The set_rcvar() function has been removed from /etc/rc.subr. All
809 base and ports rc.d scripts have been updated, so if you have a
810 port installed with a script in /usr/local/etc/rc.d you can either
811 hand-edit the rcvar= line, or reinstall the port.
813 An easy way to handle the mass-update of /etc/rc.d:
814 rm /etc/rc.d/* && mergemaster -i
817 panic(9) now stops other CPUs in the SMP systems, disables interrupts
818 on the current CPU and prevents other threads from running.
819 This behavior can be reverted using the kern.stop_scheduler_on_panic
821 The new behavior can be incompatible with kern.sync_on_panic.
824 The carp(4) facility has been changed significantly. Configuration
825 of the CARP protocol via ifconfig(8) has changed, as well as format
826 of CARP events submitted to devd(8) has changed. See manual pages
827 for more information. The arpbalance feature of carp(4) is currently
828 not supported anymore.
830 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
831 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
832 need to be recompiled.
835 The acpi_wmi(4) status device /dev/wmistat has been renamed to
839 The option VFS_ALLOW_NONMPSAFE option has been added in order to
840 explicitely support non-MPSAFE filesystems.
841 It is on by default for all supported platform at this present
845 The broken amd(4) driver has been replaced with esp(4) in the amd64,
846 i386 and pc98 GENERIC kernel configuration files.
849 sysinstall has been removed
852 The stable/9 branch created in subversion. This corresponds to the
853 RELENG_9 branch in CVS.
856 This commit modifies vfs_register() so that it uses a hash
857 calculation to set vfc_typenum, which is enabled by default.
858 The first time a system is booted after this change, the
859 vfc_typenum values will change for all file systems. The
860 main effect of this is a change to the NFS server file handles
861 for file systems that use vfc_typenum in their fsid, such as ZFS.
862 It will, however, prevent vfc_typenum from changing when file
863 systems are loaded in a different order for subsequent reboots.
864 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
865 until you are ready to remount all NFS clients after a reboot.
868 Bump the shared library version numbers for libraries that
869 do not use symbol versioning, have changed the ABI compared
870 to stable/8 and which shared library version was not bumped.
871 Done as part of 9.0-RELEASE cycle.
874 During the merge of Capsicum features, the fget(9) KPI was modified.
875 This may require the rebuilding of out-of-tree device drivers --
876 issues have been reported specifically with the nVidia device driver.
877 __FreeBSD_version is bumped to 900041.
879 Also, there is a period between 20110811 and 20110814 where the
880 special devices /dev/{stdin,stdout,stderr} did not work correctly.
881 Building world from a kernel during that window may not work.
884 The packet filter (pf) code has been updated to OpenBSD 4.5.
885 You need to update userland tools to be in sync with kernel.
886 This update breaks backward compatibility with earlier pfsync(4)
887 versions. Care must be taken when updating redundant firewall setups.
890 The following sysctls and tunables are retired on x86 platforms:
892 machdep.hlt_logical_cpus
893 The following sysctl is retired:
894 machdep.hyperthreading_allowed
895 The sysctls were supposed to provide a way to dynamically offline and
896 online selected CPUs on x86 platforms, but the implementation has not
897 been reliable especially with SCHED_ULE scheduler.
898 machdep.hyperthreading_allowed tunable is still available to ignore
899 hyperthreading CPUs at OS level.
900 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
901 where X is an APIC ID of a CPU. Be advised, though, that disabling
902 CPUs in non-uniform fashion will result in non-uniform topology and
903 may lead to sub-optimal system performance with SCHED_ULE, which is
907 cpumask_t type is retired and cpuset_t is used in order to describe
911 Changes to ifconfig(8) for dynamic address family detection mandate
912 that you are running a kernel of 20110525 or later. Make sure to
913 follow the update procedure to boot a new kernel before installing
917 Support for sun4v architecture is officially dropped
920 Several KPI breaking changes have been committed to the mii(4) layer,
921 the PHY drivers and consequently some Ethernet drivers using mii(4).
922 This means that miibus.ko and the modules of the affected Ethernet
923 drivers need to be recompiled.
925 Note to kernel developers: Given that the OUI bit reversion problem
926 was fixed as part of these changes all mii(4) commits related to OUIs,
927 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
928 handling, no longer can be merged verbatim to stable/8 and previous
932 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
933 into their kernel configurations along with 'device pci'.
936 The default NFS client is now the new NFS client, so fstype "newnfs"
937 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
938 Although mounts via fstype "nfs" will usually work without userland
939 changes, it is recommended that the mount(8) and mount_nfs(8)
940 commands be rebuilt from sources and that a link to mount_nfs called
941 mount_oldnfs be created. The new client is compiled into the
942 kernel with "options NFSCL" and this is needed for diskless root
943 file systems. The GENERIC kernel configs have been changed to use
944 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
945 To use the regular/old client, you can "mount -t oldnfs ...". For
946 a diskless root file system, you must also include a line like:
948 vfs.root.mountfrom="oldnfs:"
950 in the boot/loader.conf on the root fs on the NFS server to make
951 a diskless root fs use the old client.
954 The GENERIC kernels for all architectures now default to the new
955 CAM-based ATA stack. It means that all legacy ATA drivers were
956 removed and replaced by respective CAM drivers. If you are using
957 ATA device names in /etc/fstab or other places, make sure to update
958 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
959 where 'Y's are the sequential numbers starting from zero for each type
960 in order of detection, unless configured otherwise with tunables,
961 see cam(4)). There will be symbolic links created in /dev/ to map
962 old adX devices to the respective adaY. They should provide basic
963 compatibility for file systems mounting in most cases, but they do
964 not support old user-level APIs and do not have respective providers
965 in GEOM. Consider using updated management tools with new device names.
967 It is possible to load devices ahci, ata, siis and mvs as modules,
968 but option ATA_CAM should remain in kernel configuration to make ata
969 module work as CAM driver supporting legacy ATA controllers. Device ata
970 still can be used in modular fashion (atacore + ...). Modules atadisk
971 and atapi* are not used and won't affect operation in ATA_CAM mode.
972 Note that to use CAM-based ATA kernel should include CAM devices
973 scbus, pass, da (or explicitly ada), cd and optionally others. All of
974 them are parts of the cam module.
976 ataraid(4) functionality is now supported by the RAID GEOM class.
977 To use it you can load geom_raid kernel module and use graid(8) tool
978 for management. Instead of /dev/arX device names, use /dev/raid/rX.
980 No kernel config options or code have been removed, so if a problem
981 arises, please report it and optionally revert to the old ATA stack.
982 In order to do it you can remove from the kernel config:
987 , and instead add back:
988 device atadisk # ATA disk drives
989 device ataraid # ATA RAID drives
990 device atapicd # ATAPI CDROM drives
991 device atapifd # ATAPI floppy drives
992 device atapist # ATAPI tape drives
995 The default NFS server has been changed to the new server, which
996 was referred to as the experimental server. If you need to switch
997 back to the old NFS server, you must now put the "-o" option on
998 both the mountd and nfsd commands. This can be done using the
999 mountd_flags and nfs_server_flags rc.conf variables until an
1000 update to the rc scripts is committed, which is coming soon.
1003 The GNU Objective-C runtime library (libobjc), and other Objective-C
1004 related components have been removed from the base system. If you
1005 require an Objective-C library, please use one of the available ports.
1008 ath(4) has been split into bus- and device- modules. if_ath contains
1009 the HAL, the TX rate control and the network device code. if_ath_pci
1010 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1011 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1012 in order to use ath on everything else.
1014 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1015 need to load if_ath and if_ath_pci for ath(4) operation.
1018 As part of the replacement of sysinstall, the process of building
1019 release media has changed significantly. For details, please re-read
1020 release(7), which has been updated to reflect the new build process.
1023 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1024 is the last available version under GPLv2. It brings a number of new
1025 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1026 4.1 and SSE 4.2), better support for powerpc64, a number of new
1027 directives, and lots of other small improvements. See the ChangeLog
1028 file in contrib/binutils for the full details.
1031 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1032 compliant, and will now use half of hash for authentication.
1033 This will break interoperability with all stacks (including all
1034 actual FreeBSD versions) who implement
1035 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1037 The only workaround with such peers is to use another HMAC
1038 algorithm for IPsec ("phase 2") authentication.
1041 Remove the uio_yield prototype and symbol. This function has
1042 been misnamed since it was introduced and should not be
1043 globally exposed with this name. The equivalent functionality
1044 is now available using kern_yield(curthread->td_user_pri).
1045 The function remains undocumented.
1048 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1049 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1050 for scalar sysctls is defined but disabled. Code that needs
1051 UQUAD to pass the type checking that must compile on older
1052 systems where the define is not present can check against
1053 __FreeBSD_version >= 900030.
1055 The system dialog(1) has been replaced with a new version previously
1056 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1057 with the previous version, but the libdialog associated with it has
1058 a largely incompatible API. As such, the original version of libdialog
1059 will be kept temporarily as libodialog, until its base system consumers
1060 are replaced or updated. Bump __FreeBSD_version to 900030.
1063 If you are trying to run make universe on a -stable system, and you get
1064 the following warning:
1065 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1066 unknown. config(8) likely too old."
1067 or something similar to it, then you must upgrade your -stable system
1068 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1069 stable/8) or build the config from the latest stable/8 branch and
1070 install it on your system.
1072 Prior to this date, building a current universe on 8-stable system from
1073 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1074 error in the first kernel build phase. A new config on those old
1075 systems will fix that problem for older versions of -current.
1078 The TCP stack has been modified to allow Khelp modules to interact with
1079 it via helper hook points and store per-connection data in the TCP
1080 control block. Bump __FreeBSD_version to 900029. User space tools that
1081 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1085 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1086 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1087 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1088 to take advantage of it instead of using custom implementations. This
1089 means that these drivers now no longer unconditionally advertise
1090 support for flow control but only do so if flow control is a selected
1091 media option. This was implemented in the generic support that way in
1092 order to allow flow control to be switched on and off via ifconfig(8)
1093 with the PHY specific default to typically off in order to protect
1094 from unwanted effects. Consequently, if you used flow control with
1095 one of the above mentioned drivers you now need to explicitly enable
1096 it, for example via:
1097 ifconfig bge0 media auto mediaopt flowcontrol
1099 Along with the above mentioned changes generic support for setting
1100 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1101 e1000phy(4) as well as ip1000phy(4) have been converted to take
1102 advantage of it. This means that these drivers now no longer take the
1103 link0 parameter for selecting master mode but the master media option
1104 has to be used instead, for example like in the following:
1105 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1107 Selection of master mode now is also available with all other PHY
1108 drivers supporting 1000baseT.
1111 The TCP stack has received a significant update to add support for
1112 modularised congestion control and generally improve the clarity of
1113 congestion control decisions. Bump __FreeBSD_version to 900025. User
1114 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1115 sockstat) need to be recompiled.
1118 The man(1) utility has been replaced by a new version that no longer
1119 uses /etc/manpath.config. Please consult man.conf(5) for how to
1120 migrate local entries to the new format.
1123 The copyright strings printed by login(1) and sshd(8) at the time of a
1124 new connection have been removed to follow other operating systems and
1128 A workaround for a fixed ld bug has been removed in kernel code,
1129 so make sure that your system ld is built from sources after
1130 revision 210245 from 2010-07-19 (r211583 if building head kernel
1131 on stable/8, r211584 for stable/7; both from 2010-08-21).
1132 A symptom of incorrect ld version is different addresses for
1133 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1136 The $ipv6_prefer variable in rc.conf(5) has been split into
1137 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1139 The $ip6addrctl_policy is a variable to choose a pre-defined
1140 address selection policy set by ip6addrctl(8). A value
1141 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1144 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1145 flag (see an entry of 20090926) is set on an interface with no
1146 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1147 security reason. If you want IPv6 link-local address on all
1148 interfaces by default, set this to "YES".
1150 The old ipv6_prefer="YES" is equivalent to
1151 ipv6_activate_all_interfaces="YES" and
1152 ip6addrctl_policy="ipv6_prefer".
1155 DTrace has grown support for userland tracing. Due to this, DTrace is
1156 now i386 and amd64 only.
1157 dtruss(1) is now installed by default on those systems and a new
1158 kernel module is needed for userland tracing: fasttrap.
1159 No changes to your kernel config file are necessary to enable
1160 userland tracing, but you might consider adding 'STRIP=' and
1161 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1162 to have informative userland stack traces in DTrace (ustack).
1165 The acpi_aiboost(4) driver has been removed in favor of the new
1166 aibs(4) driver. You should update your kernel configuration file.
1169 BSD grep has been imported to the base system and it is built by
1170 default. It is completely BSD licensed, highly GNU-compatible, uses
1171 less memory than its GNU counterpart and has a small codebase.
1172 However, it is slower than its GNU counterpart, which is mostly
1173 noticeable for larger searches, for smaller ones it is measurable
1174 but not significant. The reason is complex, the most important factor
1175 is that we lack a modern and efficient regex library and GNU
1176 overcomes this by optimizing the searches internally. Future work
1177 on improving the regex performance is planned, for the meantime,
1178 users that need better performance, can build GNU grep instead by
1179 setting the WITH_GNU_GREP knob.
1182 Due to the import of powerpc64 support, all existing powerpc kernel
1183 configuration files must be updated with a machine directive like this:
1184 machine powerpc powerpc
1186 In addition, an updated config(8) is required to build powerpc kernels
1190 A new version of ZFS (version 15) has been merged to -HEAD.
1191 This version uses a python library for the following subcommands:
1192 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1193 For full functionality of these commands the following port must
1194 be installed: sysutils/py-zfs
1197 'vm_page's are now hashed by physical address to an array of mutexes.
1198 Currently this is only used to serialize access to hold_count. Over
1199 time the page queue mutex will be peeled away. This changes the size
1200 of pmap on every architecture. And requires all callers of vm_page_hold
1201 and vm_page_unhold to be updated.
1204 WITH_CTF can now be specified in src.conf (not recommended, there
1205 are some problems with static executables), make.conf (would also
1206 affect ports which do not use GNU make and do not override the
1207 compile targets) or in the kernel config (via "makeoptions
1209 When WITH_CTF was specified there before this was silently ignored,
1210 so make sure that WITH_CTF is not used in places which could lead
1211 to unwanted behavior.
1214 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1215 to allow 32-bit compatibility on non-x86 platforms. All kernel
1216 configurations on amd64 and ia64 platforms using these options must
1217 be modified accordingly.
1220 The utmp user accounting database has been replaced with utmpx,
1221 the user accounting interface standardized by POSIX.
1222 Unfortunately the semantics of utmp and utmpx don't match,
1223 making it practically impossible to support both interfaces.
1224 The user accounting database is used by tools like finger(1),
1225 last(1), talk(1), w(1) and ac(8).
1227 All applications in the base system use utmpx. This means only
1228 local binaries (e.g. from the ports tree) may still use these
1229 utmp database files. These applications must be rebuilt to make
1232 After the system has been upgraded, it is safe to remove the old
1233 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1234 assuming their contents is of no importance anymore. Old wtmp
1235 databases can only be used by last(1) and ac(8) after they have
1236 been converted to the new format using wtmpcvt(1).
1239 Introduce the kernel thread "deadlock resolver" (which can be enabled
1240 via the DEADLKRES option, see NOTES for more details) and the
1241 sleepq_type() function for sleepqueues.
1244 The rc.firewall and rc.firewall6 were unified, and
1245 rc.firewall6 and rc.d/ip6fw were removed.
1246 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1247 variables are obsoleted. Instead, the following new rc
1248 variables are added to rc.d/ipfw:
1250 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1251 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1252 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1254 The meanings correspond to the relevant IPv4 variables.
1260 The default terminal emulation for syscons(4) has been changed
1261 from cons25 to xterm on all platforms except pc98. This means
1262 that the /etc/ttys file needs to be updated to ensure correct
1263 operation of applications on the console.
1265 The terminal emulation style can be toggled per window by using
1266 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1267 options can be used to change the compile-time default back to
1270 To prevent graphical artifacts, make sure the TERM environment
1271 variable is set to match the terminal emulation that is being
1272 performed by syscons(4).
1275 The layout of the structure ieee80211req_scan_result has changed.
1276 Applications that require wireless scan results (e.g. ifconfig(8))
1277 from net80211 need to be recompiled.
1279 Applications such as wpa_supplicant(8) may require a full world
1280 build without using NO_CLEAN in order to get synchronized with the
1284 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1285 There's one kernel module for each firmware. Adding "device iwnfw"
1286 to the kernel configuration file means including all three firmware
1287 images inside the kernel. If you want to include just the one for
1288 your wireless card, use the devices iwn4965fw, iwn5000fw or
1292 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1293 into rc.d/netif. The changes are the following:
1295 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1296 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1297 Note that both variables need the "inet6" keyword at the head.
1299 Do not set $ipv6_network_interfaces manually if you do not
1300 understand what you are doing. It is not needed in most cases.
1302 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1305 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1306 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1308 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1309 all configured interfaces have "inet6 accept_rtadv" in the
1310 $ifconfig_IF_ipv6. These are for backward compatibility.
1312 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1313 functionality of interfaces with no corresponding
1314 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1315 and the default address selection policy of ip6addrctl(8)
1316 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1317 Note that if you want to configure IPv6 functionality on the
1318 disabled interfaces after boot, first you need to clear the flag by
1319 using ifconfig(8) like:
1321 ifconfig em0 inet6 -ifdisabled
1323 If YES, the default address selection policy is set as
1326 The default value of $ipv6_prefer is NO.
1328 4. If your system need to receive Router Advertisement messages,
1329 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1330 scripts automatically invoke rtsol(8) when the interface becomes
1331 UP. The Router Advertisement messages are used for SLAAC
1332 (State-Less Address AutoConfiguration).
1335 802.11s D3.03 support was committed. This is incompatible with the
1336 previous code, which was based on D3.0.
1339 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1340 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1341 control whether accepting Router Advertisement messages or not.
1342 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1343 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1344 The ifconfig(8) utility now supports these flags.
1347 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1348 mount(8) and -a option for df(1) to see them.
1351 The old tunable hw.bus.devctl_disable has been superseded by
1352 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1353 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1357 Remove the option STOP_NMI. The default action is now to use NMI only
1358 for KDB via the newly introduced function stop_cpus_hard() and
1359 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1362 The stable/8 branch created in subversion. This corresponds to the
1363 RELENG_8 branch in CVS.
1366 Bump the shared library version numbers for all libraries that do not
1367 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1368 __FreeBSD_version to 800105.
1371 Due to changes in the implementation of virtual network stack support,
1372 all network-related kernel modules must be recompiled. As this change
1373 breaks the ABI, bump __FreeBSD_version to 800104.
1376 The TOE interface to the TCP syncache has been modified to remove
1377 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1378 The cxgb driver is the only TOE consumer affected by this change, and
1379 needs to be recompiled along with the kernel. As this change breaks
1380 the ABI, bump __FreeBSD_version to 800103.
1383 Padding has been added to struct tcpcb, sackhint and tcpstat in
1384 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1385 maintaining the ABI. However, this change breaks the ABI, so bump
1386 __FreeBSD_version to 800102. User space tools that rely on the size of
1387 any of these structs (e.g. sockstat) need to be recompiled.
1390 The NFS_LEGACYRPC option has been removed along with the old kernel
1391 RPC implementation that this option selected. Kernel configurations
1392 may need to be adjusted.
1395 The network interface device nodes at /dev/net/<interface> have been
1396 removed. All ioctl operations can be performed the normal way using
1397 routing sockets. The kqueue functionality can generally be replaced
1398 with routing sockets.
1401 The documentation from the FreeBSD Documentation Project (Handbook,
1402 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1403 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1406 The ABI of various structures related to the SYSV IPC API have been
1407 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1408 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1412 Layout of struct vnet has changed as routing related variables were
1413 moved to their own Vimage module. Modules need to be recompiled. Bump
1414 __FreeBSD_version to 800099.
1417 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1418 respectively. As long as no more than 16 groups per process are used,
1419 no changes should be visible. When more than 16 groups are used, old
1420 binaries may fail if they call getgroups() or getgrouplist() with
1421 statically sized storage. Recompiling will work around this, but
1422 applications should be modified to use dynamically allocated storage
1423 for group arrays as POSIX.1-2008 does not cap an implementation's
1424 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1426 NFS and portalfs mounts may also be affected as the list of groups is
1427 truncated to 16. Users of NFS who use more than 16 groups, should
1428 take care that negative group permissions are not used on the exported
1429 file systems as they will not be reliable unless a GSSAPI based
1430 authentication method is used.
1433 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1434 option compiles in the support for adaptive spinning for lockmgrs
1435 which want to enable it. The lockinit() function now accepts the flag
1436 LK_ADAPTIVE in order to make the lock object subject to adaptive
1437 spinning when both held in write and read mode.
1440 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1441 changed. User applications that use this ioctl need to be rebuilt.
1444 The layout of struct thread has changed. Kernel and modules need to
1448 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1449 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1452 window(1) has been removed from the base system. It can now be
1453 installed from ports. The port is called misc/window.
1456 The way we are storing and accessing `routing table' entries has
1457 changed. Programs reading the FIB, like netstat, need to be
1461 A new netisr implementation has been added for FreeBSD 8. Network
1462 file system modules, such as igmp, ipdivert, and others, should be
1464 Bump __FreeBSD_version to 800096.
1467 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1471 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1472 Bump __FreeBSD_version to 800094.
1475 Add mnt_xflag field to 'struct mount'. File system modules need to be
1477 Bump __FreeBSD_version to 800093.
1480 The compiling option ADAPTIVE_SX has been retired while it has been
1481 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1482 The KPI for sx_init_flags() changes as accepting flags:
1483 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1484 been introduced in order to handle the reversed logic.
1485 Bump __FreeBSD_version to 800092.
1488 Add support for hierarchical jails. Remove global securelevel.
1489 Bump __FreeBSD_version to 800091.
1492 The layout of struct vnet_net has changed, therefore modules
1494 Bump __FreeBSD_version to 800090.
1497 The newly imported zic(8) produces a new format in the output. Please
1498 run tzsetup(8) to install the newly created data to /etc/localtime.
1501 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1502 hw.usb.* and is now consistent again with previous releases.
1505 802.11 monitor mode support was revised and driver api's were changed.
1506 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1507 of DLT_IEEE802_11. No user-visible data structures were changed but
1508 applications that use DLT_IEEE802_11 may require changes.
1509 Bump __FreeBSD_version to 800088.
1512 The layout of the following structs has changed: sysctl_oid,
1513 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1514 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1515 panics may be experienced. World rebuild is required for
1516 correctly checking networking state from userland.
1517 Bump __FreeBSD_version to 800085.
1520 MLDv2 and Source-Specific Multicast (SSM) have been merged
1521 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1522 The implementation of SSM within FreeBSD's IPv6 stack closely
1523 follows the IPv4 implementation.
1525 For kernel developers:
1527 * The most important changes are that the ip6_output() and
1528 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1529 and this lock has been downgraded to a non-recursive mutex.
1531 * As with the changes to the IPv4 stack to support SSM, filtering
1532 of inbound multicast traffic must now be performed by transport
1533 protocols within the IPv6 stack. This does not apply to TCP and
1534 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1536 * The KPIs used by IPv6 multicast are similar to those used by
1537 the IPv4 stack, with the following differences:
1538 * im6o_mc_filter() is analogous to imo_multicast_filter().
1539 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1540 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1541 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1542 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1543 for MLDv1 have an additional 'timer' argument which is used to
1544 jitter the initial membership report for the solicited-node
1545 multicast membership on-link.
1546 * This is not strictly needed for MLDv2, which already jitters
1547 its report transmissions. However, the 'timer' argument is
1548 preserved in case MLDv1 is active on the interface.
1550 * The KAME linked-list based IPv6 membership implementation has
1551 been refactored to use a vector similar to that used by the IPv4
1553 Code which maintains a list of its own multicast memberships
1554 internally, e.g. carp, has been updated to reflect the new
1557 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1558 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1559 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1560 implementation constraint which needs to be addressed in HEAD.
1562 For application developers:
1564 * The changes are broadly similar to those made for the IPv4
1567 * The use of IPv4 and IPv6 multicast socket options on the same
1568 socket, using mapped addresses, HAS NOT been tested or supported.
1570 * There are a number of issues with the implementation of various
1571 IPv6 multicast APIs which need to be resolved in the API surface
1572 before the implementation is fully compatible with KAME userland
1573 use, and these are mostly to do with interface index treatment.
1575 * The literature available discusses the use of either the delta / ASM
1576 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1577 using setsourcefilter(3)/getsourcefilter(3). For more information
1578 please refer to RFC 3768, 'Socket Interface Extensions for
1579 Multicast Source Filters'.
1581 * Applications which use the published RFC 3678 APIs should be fine.
1583 For systems administrators:
1585 * The mtest(8) utility has been refactored to support IPv6, in
1586 addition to IPv4. Interface addresses are no longer accepted
1587 as arguments, their names must be used instead. The utility
1588 will map the interface name to its first IPv4 address as
1589 returned by getifaddrs(3).
1591 * The ifmcstat(8) utility has also been updated to print the MLDv2
1592 endpoint state and source filter lists via sysctl(3).
1594 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1595 loopback of IPv6 multicast datagrams by default; it defaults to 1
1596 to preserve the existing behaviour. Disabling multicast loopback is
1597 recommended for optimal system performance.
1599 * The IPv6 MROUTING code has been changed to examine this sysctl
1600 instead of attempting to perform a group lookup before looping
1601 back forwarded datagrams.
1603 Bump __FreeBSD_version to 800084.
1606 Implement low-level Bluetooth HCI API.
1607 Bump __FreeBSD_version to 800083.
1610 The layout of struct malloc_type, used by modules to register new
1611 memory allocation types, has changed. Most modules will need to
1612 be rebuilt or panics may be experienced.
1613 Bump __FreeBSD_version to 800081.
1616 Anticipate overflowing inp_flags - add inp_flags2.
1617 This changes most offsets in inpcb, so checking v4 connection
1618 state will require a world rebuild.
1619 Bump __FreeBSD_version to 800080.
1622 Add an llentry to struct route and struct route_in6. Modules
1623 embedding a struct route will need to be recompiled.
1624 Bump __FreeBSD_version to 800079.
1627 The size of rt_metrics_lite and by extension rtentry has changed.
1628 Networking administration apps will need to be recompiled.
1629 The route command now supports show as an alias for get, weighting
1630 of routes, sticky and nostick flags to alter the behavior of stateful
1632 Bump __FreeBSD_version to 800078.
1635 Do not use Giant for kbdmux(4) locking. This is wrong and
1636 apparently causing more problems than it solves. This will
1637 re-open the issue where interrupt handlers may race with
1638 kbdmux(4) in polling mode. Typical symptoms include (but
1639 not limited to) duplicated and/or missing characters when
1640 low level console functions (such as gets) are used while
1641 interrupts are enabled (for example geli password prompt,
1642 mountroot prompt etc.). Disabling kbdmux(4) may help.
1645 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1646 kernel modules referencing any of the above need to be recompiled.
1647 Bump __FreeBSD_version to 800075.
1650 GEOM_PART has become the default partition slicer for storage devices,
1651 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1652 introduces some changes:
1654 MSDOS/EBR: the devices created from MSDOS extended partition entries
1655 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1656 to devices with offset-based names. fstabs may need to be modified.
1658 BSD: the "geometry does not match label" warning is harmless in most
1659 cases but it points to problems in file system misalignment with
1660 disk geometry. The "c" partition is now implicit, covers the whole
1661 top-level drive and cannot be (mis)used by users.
1663 General: Kernel dumps are now not allowed to be written to devices
1664 whose partition types indicate they are meant to be used for file
1665 systems (or, in case of MSDOS partitions, as something else than
1668 Most of these changes date approximately from 200812.
1671 The uscanner(4) driver has been removed from the kernel. This follows
1672 Linux removing theirs in 2.6 and making libusb the default interface
1673 (supported by sane).
1676 The multicast forwarding code has been cleaned up. netstat(1)
1677 only relies on KVM now for printing bandwidth upcall meters.
1678 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1679 ip6_mroute_mod respectively. The config(5) options for statically
1680 compiling this code remain the same, i.e. 'options MROUTING'.
1683 Support for the IFF_NEEDSGIANT network interface flag has been
1684 removed, which means that non-MPSAFE network device drivers are no
1685 longer supported. In particular, if_ar, if_sr, and network device
1686 drivers from the old (legacy) USB stack can no longer be built or
1690 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1691 a bunch of new language catalog files have also been added.
1692 This means that some common libc messages are now localized and
1693 they depend on the LC_MESSAGES environmental variable.
1696 The k8temp(4) driver has been renamed to amdtemp(4) since
1697 support for Family 10 and Family 11 CPU families was added.
1700 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1701 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1703 For kernel developers, the most important changes are that the
1704 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1705 and this lock has been downgraded to a non-recursive mutex.
1707 Transport protocols (UDP, Raw IP) are now responsible for filtering
1708 inbound multicast traffic according to group membership and source
1709 filters. The imo_multicast_filter() KPI exists for this purpose.
1710 Transports which do not use multicast (SCTP, TCP) already reject
1711 multicast by default. Forwarding and receive performance may improve
1712 as a mutex acquisition is no longer needed in the ip_input()
1713 low-level input path. in_addmulti() and in_delmulti() are shimmed
1714 to new KPIs which exist to support SSM in-kernel.
1716 For application developers, it is recommended that loopback of
1717 multicast datagrams be disabled for best performance, as this
1718 will still cause the lock to be taken for each looped-back
1719 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1720 be tuned to 0 to disable loopback by default; it defaults to 1
1721 to preserve the existing behaviour.
1723 For systems administrators, to obtain best performance with
1724 multicast reception and multiple groups, it is always recommended
1725 that a card with a suitably precise hash filter is used. Hash
1726 collisions will still result in the lock being taken within the
1727 transport protocol input path to check group membership.
1729 If deploying FreeBSD in an environment with IGMP snooping switches,
1730 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1731 enabled; this forces 224.0.0.0/24 group membership to be announced
1734 The size of 'struct igmpstat' has changed; netstat needs to be
1735 recompiled to reflect this.
1736 Bump __FreeBSD_version to 800070.
1739 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1740 updated to use it. This requires a buildworld/installworld in order to
1741 update the library and dependencies (usbconfig, etc). Its advisable to
1742 rebuild all ports which uses libusb. More specific directions are given
1743 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1744 libusb are no longer required and can be removed.
1747 A workaround is committed to allow the creation of System V shared
1748 memory segment of size > 2 GB on the 64-bit architectures.
1749 Due to a limitation of the existing ABI, the shm_segsz member
1750 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1751 wrong for large segments. Note that limits must be explicitly
1752 raised to allow such segments to be created.
1755 The layout of struct ifnet has changed, requiring a rebuild of all
1756 network device driver modules.
1759 The /dev handling for the new USB stack has changed, a
1760 buildworld/installworld is required for libusb20.
1763 The new USB2 stack has now been permanently moved in and all kernel and
1764 module names reverted to their previous values (eg, usb, ehci, ohci,
1765 ums, ...). The old usb stack can be compiled in by prefixing the name
1766 with the letter 'o', the old usb modules have been removed.
1767 Updating entry 20090216 for xorg and 20090215 for libmap may still
1771 The rc.conf(5) option if_up_delay has been renamed to
1772 defaultroute_delay to better reflect its purpose. If you have
1773 customized this setting in /etc/rc.conf you need to update it to
1777 xorg 7.4 wants to configure its input devices via hald which does not
1778 yet work with USB2. If the keyboard/mouse does not work in xorg then
1780 Option "AllowEmptyInput" "off"
1781 to your ServerLayout section. This will cause X to use the configured
1782 kbd and mouse sections from your xorg.conf.
1785 The GENERIC kernels for all architectures now default to the new USB2
1786 stack. No kernel config options or code have been removed so if a
1787 problem arises please report it and optionally revert to the old USB
1788 stack. If you are loading USB kernel modules or have a custom kernel
1789 that includes GENERIC then ensure that usb names are also changed over,
1790 eg uftdi -> usb2_serial_ftdi.
1792 Older programs linked against the ports libusb 0.1 need to be
1793 redirected to the new stack's libusb20. /etc/libmap.conf can
1795 # Map old usb library to new one for usb2 stack
1796 libusb-0.1.so.8 libusb20.so.1
1799 All USB ethernet devices now attach as interfaces under the name ueN
1800 (eg. ue0). This is to provide a predictable name as vendors often
1801 change usb chipsets in a product without notice.
1804 The ichsmb(4) driver has been changed to require SMBus slave
1805 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1806 All of the other SMBus controller drivers require left-justified
1807 slave addresses, so this change makes all the drivers provide the
1811 INET6 statistics (struct ip6stat) was updated.
1812 netstat(1) needs to be recompiled.
1815 NTFS has been removed from GENERIC kernel on amd64 to match
1816 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1817 will load ntfs.ko module automatically when NTFS support is
1818 actually needed, unless ntfs.ko is not installed or security
1819 level prohibits loading kernel modules. If either is the case,
1820 "options NTFS" has to be added into kernel config.
1823 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1824 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1825 800061. User space tools that rely on the size of struct tcpcb in
1826 tcp_var.h (e.g. sockstat) need to be recompiled.
1829 ng_tty(4) module updated to match the new TTY subsystem.
1830 Due to API change, user-level applications must be updated.
1831 New API support added to mpd5 CVS and expected to be present
1832 in next mpd5.3 release.
1835 With __FreeBSD_version 800060 the makefs tool is part of
1836 the base system (it was a port).
1839 The afdata and ifnet locks have been changed from mutexes to
1840 rwlocks, network modules will need to be re-compiled.
1843 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1844 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1845 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1846 architecture and 40 bytes on 64-bit architecture. The userland
1847 applications "arp" and "ndp" have been updated accordingly.
1848 The output from "netstat -r" shows only routing entries and
1849 none of the L2 information.
1852 __FreeBSD_version 800057 marks the switchover from the
1853 binary ath hal to source code. Users must add the line:
1855 options AH_SUPPORT_AR5416
1857 to their kernel config files when specifying:
1861 The ath_hal module no longer exists; the code is now compiled
1862 together with the driver in the ath module. It is now
1863 possible to tailor chip support (i.e. reduce the set of chips
1864 and thereby the code size); consult ath_hal(4) for details.
1867 __FreeBSD_version 800054 adds memory barriers to
1868 <machine/atomic.h>, new interfaces to ifnet to facilitate
1869 multiple hardware transmit queues for cards that support
1870 them, and a lock-less ring-buffer implementation to
1871 enable drivers to more efficiently manage queueing of
1875 A new version of ZFS (version 13) has been merged to -HEAD.
1876 This version has zpool attribute "listsnapshots" off by
1877 default, which means "zfs list" does not show snapshots,
1878 and is the same as Solaris behavior.
1881 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1884 The uhci, ohci, ehci and slhci USB Host controller drivers have
1885 been put into separate modules. If you load the usb module
1886 separately through loader.conf you will need to load the
1887 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1888 controller add the following to loader.conf:
1894 The ABI used by the PMC toolset has changed. Please keep
1895 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1899 atapci kernel module now includes only generic PCI ATA
1900 driver. AHCI driver moved to ataahci kernel module.
1901 All vendor-specific code moved into separate kernel modules:
1902 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1903 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1904 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1905 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1908 The TTY subsystem of the kernel has been replaced by a new
1909 implementation, which provides better scalability and an
1910 improved driver model. Most common drivers have been migrated to
1911 the new TTY subsystem, while others have not. The following
1912 drivers have not yet been ported to the new TTY layer:
1915 cy, digi, rc, rp, sio
1921 ng_h4, ng_tty, ppp, sl, snp
1923 Adding these drivers to your kernel configuration file shall
1924 cause compilation to fail.
1927 ntpd has been upgraded to 4.2.4p5.
1930 OpenSSH has been upgraded to 5.1p1.
1932 For many years, FreeBSD's version of OpenSSH preferred DSA
1933 over RSA for host and user authentication keys. With this
1934 upgrade, we've switched to the vendor's default of RSA over
1935 DSA. This may cause upgraded clients to warn about unknown
1936 host keys even for previously known hosts. Users should
1937 follow the usual procedure for verifying host keys before
1938 accepting the RSA key.
1940 This can be circumvented by setting the "HostKeyAlgorithms"
1941 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1944 Please note that the sequence of keys offered for
1945 authentication has been changed as well. You may want to
1946 specify IdentityFile in a different order to revert this
1950 The sio(4) driver has been removed from the i386 and amd64
1951 kernel configuration files. This means uart(4) is now the
1952 default serial port driver on those platforms as well.
1954 To prevent collisions with the sio(4) driver, the uart(4) driver
1955 uses different names for its device nodes. This means the
1956 onboard serial port will now most likely be called "ttyu0"
1957 instead of "ttyd0". You may need to reconfigure applications to
1958 use the new device names.
1960 When using the serial port as a boot console, be sure to update
1961 /boot/device.hints and /etc/ttys before booting the new kernel.
1962 If you forget to do so, you can still manually specify the hints
1963 at the loader prompt:
1965 set hint.uart.0.at="isa"
1966 set hint.uart.0.port="0x3F8"
1967 set hint.uart.0.flags="0x10"
1968 set hint.uart.0.irq="4"
1972 The gpt(8) utility has been removed. Use gpart(8) to partition
1976 The version that Linuxulator emulates was changed from 2.4.2
1977 to 2.6.16. If you experience any problems with Linux binaries
1978 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1979 if it fixes the problem contact emulation mailing list.
1982 ISDN4BSD (I4B) was removed from the src tree. You may need to
1983 update a your kernel configuration and remove relevant entries.
1986 I have checked in code to support multiple routing tables.
1987 See the man pages setfib(1) and setfib(2).
1988 This is a hopefully backwards compatible version,
1989 but to make use of it you need to compile your kernel
1990 with options ROUTETABLES=2 (or more up to 16).
1993 The 802.11 wireless support was redone to enable multi-bss
1994 operation on devices that are capable. The underlying device
1995 is no longer used directly but instead wlanX devices are
1996 cloned with ifconfig. This requires changes to rc.conf files.
1997 For example, change:
1998 ifconfig_ath0="WPA DHCP"
2001 ifconfig_wlan0="WPA DHCP"
2002 see rc.conf(5) for more details. In addition, mergemaster of
2003 /etc/rc.d is highly recommended. Simultaneous update of userland
2004 and kernel wouldn't hurt either.
2006 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2007 modules were merged into the base wlan module. All references
2008 to these modules (e.g. in kernel config files) must be removed.
2011 psm(4) has gained write(2) support in native operation level.
2012 Arbitrary commands can be written to /dev/psm%d and status can
2013 be read back from it. Therefore, an application is responsible
2014 for status validation and error recovery. It is a no-op in
2015 other operation levels.
2018 Support for KSE threading has been removed from the kernel. To
2019 run legacy applications linked against KSE libmap.conf may
2020 be used. The following libmap.conf may be used to ensure
2021 compatibility with any prior release:
2023 libpthread.so.1 libthr.so.1
2024 libpthread.so.2 libthr.so.2
2025 libkse.so.3 libthr.so.3
2028 The layout of struct vmspace has changed. This affects libkvm
2029 and any executables that link against libkvm and use the
2030 kvm_getprocs() function. In particular, but not exclusively,
2031 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2032 The effects are minimal, but it's advisable to upgrade world
2036 The latest em driver no longer has support in it for the
2037 82575 adapter, this is now moved to the igb driver. The
2038 split was done to make new features that are incompatible
2039 with older hardware easier to do.
2042 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2043 likewise the kernel option is now GEOM_LINUX_LVM.
2046 The default NFS mount mode has changed from UDP to TCP for
2047 increased reliability. If you rely on (insecurely) NFS
2048 mounting across a firewall you may need to update your
2052 Belatedly note the addition of m_collapse for compacting
2056 The fts(3) structures have been changed to use adequate
2057 integer types for their members and so to be able to cope
2058 with huge file trees. The old fts(3) ABI is preserved
2059 through symbol versioning in libc, so third-party binaries
2060 using fts(3) should still work, although they will not take
2061 advantage of the extended types. At the same time, some
2062 third-party software might fail to build after this change
2063 due to unportable assumptions made in its source code about
2064 fts(3) structure members. Such software should be fixed
2065 by its vendor or, in the worst case, in the ports tree.
2066 FreeBSD_version 800015 marks this change for the unlikely
2067 case that a portable fix is impossible.
2070 To upgrade to -current after this date, you must be running
2071 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2072 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2075 The ADAPTIVE_GIANT kernel option has been retired because its
2076 functionality is the default now.
2079 The AT keyboard emulation of sunkbd(4) has been turned on
2080 by default. In order to make the special symbols of the Sun
2081 keyboards driven by sunkbd(4) work under X these now have
2082 to be configured the same way as Sun USB keyboards driven
2083 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2085 Option "XkbLayout" "us"
2086 Option "XkbRules" "xorg"
2087 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2090 It has been decided that it is desirable to provide ABI
2091 backwards compatibility to the FreeBSD 4/5/6 versions of the
2092 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2093 broken with the introduction of PCI domain support (see the
2094 20070930 entry). Unfortunately, this required the ABI of
2095 PCIOCGETCONF to be broken again in order to be able to
2096 provide backwards compatibility to the old version of that
2097 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2098 again. As for prominent ports this affects neither pciutils
2099 nor xorg-server this time, the hal port needs to be rebuilt
2103 The misnamed kthread_create() and friends have been renamed
2104 to kproc_create() etc. Many of the callers already
2105 used kproc_start()..
2106 I will return kthread_create() and friends in a while
2107 with implementations that actually create threads, not procs.
2108 Renaming corresponds with version 800002.
2117 Avoid using make -j when upgrading. While generally safe, there are
2118 sometimes problems using -j to upgrade. If your upgrade fails with
2119 -j, please try again without -j. From time to time in the past there
2120 have been problems using -j with buildworld and/or installworld. This
2121 is especially true when upgrading between "distant" versions (eg one
2122 that cross a major release boundary or several minor releases, or when
2123 several months have passed on the -current branch).
2125 Sometimes, obscure build problems are the result of environment
2126 poisoning. This can happen because the make utility reads its
2127 environment when searching for values for global variables. To run
2128 your build attempts in an "environmental clean room", prefix all make
2129 commands with 'env -i '. See the env(1) manual page for more details.
2131 When upgrading from one major version to another it is generally best
2132 to upgrade to the latest code in the currently installed branch first,
2133 then do an upgrade to the new branch. This is the best-tested upgrade
2134 path, and has the highest probability of being successful. Please try
2135 this approach before reporting problems with a major version upgrade.
2137 When upgrading a live system, having a root shell around before
2138 installing anything can help undo problems. Not having a root shell
2139 around can lead to problems if pam has changed too much from your
2140 starting point to allow continued authentication after the upgrade.
2144 When upgrading the boot ZFS pool to a new version, always follow
2147 1.) recompile and reinstall the ZFS boot loader and boot block
2148 (this is part of "make buildworld" and "make installworld")
2150 2.) update the ZFS boot block on your boot drive
2152 The following example updates the ZFS boot block on the first
2153 partition (freebsd-boot) of a GPT partitioned drive ad0:
2154 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2156 Non-boot pools do not need these updates.
2160 If you are updating from a prior version of FreeBSD (even one just
2161 a few days old), you should follow this procedure. It is the most
2162 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2164 make kernel-toolchain
2165 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2166 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2168 To test a kernel once
2169 ---------------------
2170 If you just want to boot a kernel once (because you are not sure
2171 if it works, or if you want to boot a known bad kernel to provide
2172 debugging information) run
2173 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2174 nextboot -k testkernel
2176 To just build a kernel when you know that it won't mess you up
2177 --------------------------------------------------------------
2178 This assumes you are already running a CURRENT system. Replace
2179 ${arch} with the architecture of your machine (e.g. "i386",
2180 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2182 cd src/sys/${arch}/conf
2183 config KERNEL_NAME_HERE
2184 cd ../compile/KERNEL_NAME_HERE
2189 If this fails, go to the "To build a kernel" section.
2191 To rebuild everything and install it on the current system.
2192 -----------------------------------------------------------
2193 # Note: sometimes if you are running current you gotta do more than
2194 # is listed here if you are upgrading from a really old current.
2196 <make sure you have good level 0 dumps>
2198 make kernel KERNCONF=YOUR_KERNEL_HERE
2200 <reboot in single user> [3]
2207 To cross-install current onto a separate partition
2208 --------------------------------------------------
2209 # In this approach we use a separate partition to hold
2210 # current's root, 'usr', and 'var' directories. A partition
2211 # holding "/", "/usr" and "/var" should be about 2GB in
2214 <make sure you have good level 0 dumps>
2217 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2218 <maybe newfs current's root partition>
2219 <mount current's root partition on directory ${CURRENT_ROOT}>
2220 make installworld DESTDIR=${CURRENT_ROOT}
2221 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2222 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2223 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2224 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2225 <reboot into current>
2226 <do a "native" rebuild/install as described in the previous section>
2227 <maybe install compatibility libraries from ports/misc/compat*>
2231 To upgrade in-place from stable to current
2232 ----------------------------------------------
2233 <make sure you have good level 0 dumps>
2235 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2237 <reboot in single user> [3]
2244 Make sure that you've read the UPDATING file to understand the
2245 tweaks to various things you need. At this point in the life
2246 cycle of current, things change often and you are on your own
2247 to cope. The defaults can also change, so please read ALL of
2248 the UPDATING entries.
2250 Also, if you are tracking -current, you must be subscribed to
2251 freebsd-current@freebsd.org. Make sure that before you update
2252 your sources that you have read and understood all the recent
2253 messages there. If in doubt, please track -stable which has
2254 much fewer pitfalls.
2256 [1] If you have third party modules, such as vmware, you
2257 should disable them at this point so they don't crash your
2260 [3] From the bootblocks, boot -s, and then do
2265 adjkerntz -i # if CMOS is wall time
2266 Also, when doing a major release upgrade, it is required that
2267 you boot into single user mode to do the installworld.
2269 [4] Note: This step is non-optional. Failure to do this step
2270 can result in a significant reduction in the functionality of the
2271 system. Attempting to do it by hand is not recommended and those
2272 that pursue this avenue should read this file carefully, as well
2273 as the archives of freebsd-current and freebsd-hackers mailing lists
2274 for potential gotchas. The -U option is also useful to consider.
2275 See mergemaster(8) for more information.
2277 [5] Usually this step is a noop. However, from time to time
2278 you may need to do this if you get unknown user in the following
2279 step. It never hurts to do it all the time. You may need to
2280 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2281 install) after the buildworld before this step if you last updated
2282 from current before 20130425 or from -stable before 20130430.
2284 [6] This only deletes old files and directories. Old libraries
2285 can be deleted by "make delete-old-libs", but you have to make
2286 sure that no program is using those libraries anymore.
2288 [8] In order to have a kernel that can run the 4.x binaries needed to
2289 do an installworld, you must include the COMPAT_FREEBSD4 option in
2290 your kernel. Failure to do so may leave you with a system that is
2291 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2292 required to run the 5.x binaries on more recent kernels. And so on
2293 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2295 Make sure that you merge any new devices from GENERIC since the
2296 last time you updated your kernel config file.
2298 [9] When checking out sources, you must include the -P flag to have
2299 cvs prune empty directories.
2301 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2302 "?=" instead of the "=" assignment operator, so that buildworld can
2303 override the CPUTYPE if it needs to.
2305 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2306 not on the command line, or in /etc/make.conf. buildworld will
2307 warn if it is improperly defined.
2310 This file contains a list, in reverse chronological order, of major
2311 breakages in tracking -current. It is not guaranteed to be a complete
2312 list of such breakages, and only contains entries since October 10, 2007.
2313 If you need to see UPDATING entries from before that date, you will need
2314 to fetch an UPDATING file from an older FreeBSD release.
2316 Copyright information:
2318 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2320 Redistribution, publication, translation and use, with or without
2321 modification, in full or in part, in any form or format of this
2322 document are permitted without further permission from the author.
2324 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2325 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2326 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2327 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2328 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2329 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2330 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2331 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2332 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2333 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2334 POSSIBILITY OF SUCH DAMAGE.
2336 Contact Warner Losh if you have any questions about your use of