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