1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 20160517 p3 FreeBSD-SA-16:18.atkbd
20 FreeBSD-SA-16:19.sendmsg
22 Fix buffer overflow in keyboard driver. [SA-16:18]
24 Fix incorrect argument handling in sendmsg(2). [SA-16:19]
26 20160504 p2 FreeBSD-SA-16:17.openssl
31 Fix multiple OpenSSL vulnerabilitites. [SA-16:17]
33 Fix performance regression in libc hash(3). [EN-16:06]
35 Fix excessive latency in x86 IPI delivery. [EN-16:07]
37 Fix memory leak in ZFS. [EN-16:08]
39 20160429 p1 FreeBSD-SA-16:16.ntp
41 Fix multiple vulnerabilities of ntp.
47 The NONE and HPN patches has been removed from OpenSSH. They are
48 still available in the security/openssh-portable port.
51 r292223 changed the internal interface between the nfsd.ko and
52 nfscommon.ko modules. As such, they must both be upgraded to-gether.
53 __FreeBSD_version has been bumped because of this.
56 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
57 Kernel modules isp_2400_multi and isp_2500_multi were removed and
58 should be replaced with isp_2400 and isp_2500 modules respectively.
61 The menu.rc and loader.rc files will now be replaced during
62 upgrades. Please migrate local changes to menu.rc.local and
63 loader.rc.local instead.
66 NTP has been upgraded to 4.2.8p4.
69 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
70 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
71 and devel/kyua to version 0.20+ and adjust any calling code to work
72 with Kyuafile and kyua.
75 The polarity of Pulse Per Second (PPS) capture events with the
76 uart(4) driver has been corrected. Prior to this change the PPS
77 "assert" event corresponded to the trailing edge of a positive PPS
78 pulse and the "clear" event was the leading edge of the next pulse.
80 As the width of a PPS pulse in a typical GPS receiver is on the
81 order of 1 millisecond, most users will not notice any significant
82 difference with this change.
84 Anyone who has compensated for the historical polarity reversal by
85 configuring a negative offset equal to the pulse width will need to
86 remove that workaround.
89 From legacy ata(4) driver was removed support for SATA controllers
90 supported by more functional drivers ahci(4), siis(4) and mvs(4).
91 Kernel modules ataahci and ataadaptec were removed completely,
92 replaced by ahci and mvs modules respectively.
98 As ZFS requires more kernel stack pages than is the default on some
99 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
100 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
102 Please consider using 'options KSTACK_PAGES=X' where X is greater
103 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
106 The default Unbound configuration now enables remote control
107 using a local socket. Users who have already enabled the
108 local_unbound service should regenerate their configuration
109 by running "service local_unbound setup" as root.
112 An additional fix for the issue described in the 20150614 sendmail
113 entry below has been been committed in revision 284786.
116 The fix for the issue described in the 20150614 sendmail entry
117 below has been been committed in revision 284485. The work
118 around described in that entry is no longer needed unless the
119 default setting is overridden by a confDH_PARAMETERS configuration
120 setting of '5' or pointing to a 512 bit DH parameter file.
123 The import of openssl to address the FreeBSD-SA-15:10.openssl
124 security advisory includes a change which rejects handshakes
125 with DH parameters below 768 bits. sendmail releases prior
126 to 8.15.2 (not yet released), defaulted to a 512 bit
127 DH parameter setting for client connections. To work around
128 this interoperability, sendmail can be configured to use a
129 2048 bit DH parameter by:
131 1. Edit /etc/mail/`hostname`.mc
132 2. If a setting for confDH_PARAMETERS does not exist or
133 exists and is set to a string beginning with '5',
135 3. If a setting for confDH_PARAMETERS exists and is set to
136 a file path, create a new file with:
137 openssl dhparam -out /path/to/file 2048
138 4. Rebuild the .cf file:
139 cd /etc/mail/; make; make install
141 cd /etc/mail/; make restart
143 A sendmail patch is coming, at which time this file will be
147 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
148 defined in symlink(7); previously symlinks were silently ignored.
151 The const qualifier has been removed from iconv(3) to comply with
152 POSIX. The ports tree is aware of this from r384038 onwards.
155 At svn r275807, The default linux compat kernel ABI has been adjusted
156 to 2.6.18 in support of the linux-c6 compat ports infrastructure
157 update. If you wish to continue using the linux-f10 compat ports,
158 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
159 encouraged to update their linux-compat packages to linux-c6 during
160 their next update cycle.
162 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
165 pjdfstest has been integrated into kyua as an opt-in test suite.
166 Please see share/doc/pjdfstest/README for a more details on how to
173 The ofwfb driver, used to provide a graphics console on PowerPC when
174 using vt(4), no longer allows mmap() of all of physical memory. This
175 will prevent Xorg on PowerPC with some ATI graphics cards from
176 initializing properly unless x11-servers/xorg-server is updated to
180 The libatf-c and libatf-c++ major versions were downgraded to 0 and
181 1 respectively to match the upstream numbers. They were out of
182 sync because, when they were originally added to FreeBSD, the
183 upstream versions were not respected. These libraries are private
184 and not yet built by default, so renumbering them should be a
185 non-issue. However, unclean source trees will yield broken test
186 programs once the operator executes "make delete-old-libs" after a
189 Additionally, the atf-sh binary was made private by moving it into
190 /usr/libexec/. Already-built shell test programs will keep the
191 path to the old binary so they will break after "make delete-old"
194 If you are using WITH_TESTS=yes (not the default), wipe the object
195 tree and rebuild from scratch to prevent spurious test failures.
196 This is only needed once: the misnumbered libraries and misplaced
197 binaries have been added to OptionalObsoleteFiles.inc so they will
198 be removed during a clean upgrade.
201 The ixgbe tunables now match their sysctl counterparts, for example:
202 hw.ixgbe.enable_aim => hw.ix.enable_aim
203 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
206 The NFSv4.1 server committed by r269398 changes the internal
207 function call interfaces used between the NFS and krpc modules.
208 As such, __FreeBSD_version was bumped.
211 The default unbound configuration has been modified to address
212 issues with reverse lookups on networks that use private
213 address ranges. If you use the local_unbound service, run
214 "service local_unbound setup" as root to regenerate your
215 configuration, then "service local_unbound reload" to load the
219 It is no longer necessary to include the dwarf version in your DEBUG
220 options in your kernel config file. The bug that required it to be
221 placed in the config file has bene fixed. DEBUG should now just
222 contain -g. The build system will automatically update things
223 to do the right thing.
226 Several ABI breaking changes were merged to CTL and new iSCSI code.
227 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
228 iscsictl need to be rebuilt to work with a new kernel.
231 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
232 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
233 which differs from the behaviour controlled by this knob.)
236 On i386 and amd64 systems, the onifconsole flag is now set by default
237 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
238 as a login TTY if it is set in the bootloader as an active kernel
239 console. No changes in behavior should result otherwise. To revert to
240 the previous behavior, set ttyu0 to "off" in /etc/ttys.
243 Clang and llvm have been upgraded to 3.4.1 release.
246 Clang and llvm have been upgraded to 3.4 release.
249 If a Makefile in a tests/ directory was auto-generating a Kyuafile
250 instead of providing an explicit one, this would prevent such
251 Makefile from providing its own Kyuafile in the future during
252 NO_CLEAN builds. This has been fixed in the Makefiles but manual
253 intervention is needed to clean an objdir if you use NO_CLEAN:
254 # find /usr/obj -name Kyuafile | xargs rm -f
257 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
258 capability mode support. Please note that enabling the feature in
259 kernel is still highly recommended.
262 OpenSSH is now built with sandbox support, and will use sandbox as
263 the default privilege separation method. This requires Capsicum
264 capability mode support in kernel.
267 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
268 been deprecated and will not be part of FreeBSD 11.0 and later
269 releases. If you use this driver, please consider switching to
270 the nfe(4) driver instead.
276 The behavior of gss_pseudo_random() for the krb5 mechanism
277 has changed, for applications requesting a longer random string
278 than produced by the underlying enctype's pseudo-random() function.
279 In particular, the random string produced from a session key of
280 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
281 be different at the 17th octet and later, after this change.
282 The counter used in the PRF+ construction is now encoded as a
283 big-endian integer in accordance with RFC 4402.
284 __FreeBSD_version is bumped to 1000701.
287 The WITHOUT_ATF build knob has been removed and its functionality
288 has been subsumed into the more generic WITHOUT_TESTS. If you were
289 using the former to disable the build of the ATF libraries, you
290 should change your settings to use the latter.
293 The default version of mtree is nmtree which is obtained from
294 NetBSD. The output is generally the same, but may vary
295 slightly. If you found you need identical output adding
296 "-F freebsd9" to the command line should do the trick. For the
297 time being, the old mtree is available as fmtree.
300 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
301 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
302 1.1.4_8 and verify bsdyml not linked in, before running "make
304 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
306 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
309 The rc.d/jail script has been updated to support jail(8)
310 configuration file. The "jail_<jname>_*" rc.conf(5) variables
311 for per-jail configuration are automatically converted to
312 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
313 This is transparently backward compatible. See below about some
314 incompatibilities and rc.conf(5) manual page for more details.
316 These variables are now deprecated in favor of jail(8) configuration
317 file. One can use "rc.d/jail config <jname>" command to generate
318 a jail(8) configuration file in /var/run/jail.<jname>.conf without
319 running the jail(8) utility. The default pathname of the
320 configuration file is /etc/jail.conf and can be specified by
321 using $jail_conf or $jail_<jname>_conf variables.
323 Please note that jail_devfs_ruleset accepts an integer at
324 this moment. Please consider to rewrite the ruleset name
328 BIND has been removed from the base system. If all you need
329 is a local resolver, simply enable and start the local_unbound
330 service instead. Otherwise, several versions of BIND are
331 available in the ports tree. The dns/bind99 port is one example.
333 With this change, nslookup(1) and dig(1) are no longer in the base
334 system. Users should instead use host(1) and drill(1) which are
335 in the base system. Alternatively, nslookup and dig can
336 be obtained by installing the dns/bind-tools port.
339 With the addition of unbound(8), a new unbound user is now
340 required during installworld. "mergemaster -p" can be used to
341 add the user prior to installworld, as documented in the handbook.
344 OpenSSH is now built with DNSSEC support, and will by default
345 silently trust signed SSHFP records. This can be controlled with
346 the VerifyHostKeyDNS client configuration setting. DNSSEC support
347 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
350 The GNU Compiler Collection and C++ standard library (libstdc++)
351 are no longer built by default on platforms where clang is the system
352 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
356 The PROCDESC kernel option is now part of the GENERIC kernel
357 configuration and is required for the rwhod(8) to work.
358 If you are using custom kernel configuration, you should include
362 The API and ABI related to the Capsicum framework was modified
363 in backward incompatible way. The userland libraries and programs
364 have to be recompiled to work with the new kernel. This includes the
365 following libraries and programs, but the whole buildworld is
366 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
367 kdump, procstat, rwho, rwhod, uniq.
370 AES-NI intrinsic support has been added to gcc. The AES-NI module
371 has been updated to use this support. A new gcc is required to build
372 the aesni module on both i386 and amd64.
375 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
376 Thus "device padlock_rng" and "device rdrand_rng" should be
377 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
380 WITH_ICONV has been split into two feature sets. WITH_ICONV now
381 enables just the iconv* functionality and is now on by default.
382 WITH_LIBICONV_COMPAT enables the libiconv api and link time
383 compatability. Set WITHOUT_ICONV to build the old way.
384 If you have been using WITH_ICONV before, you will very likely
385 need to turn on WITH_LIBICONV_COMPAT.
388 INVARIANTS option now enables DEBUG for code with OpenSolaris and
389 Illumos origin, including ZFS. If you have INVARIANTS in your
390 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
392 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
393 locks if WITNESS option was set. Because that generated a lot of
394 witness(9) reports and all of them were believed to be false
395 positives, this is no longer done. New option OPENSOLARIS_WITNESS
396 can be used to achieve the previous behavior.
399 Timer values in IPv6 data structures now use time_uptime instead
400 of time_second. Although this is not a user-visible functional
401 change, userland utilities which directly use them---ndp(8),
402 rtadvd(8), and rtsold(8) in the base system---need to be updated
406 find -delete can now delete the pathnames given as arguments,
407 instead of only files found below them or if the pathname did
408 not contain any slashes. Formerly, the following error message
411 find: -delete: <path>: relative path potentially not safe
413 Deleting the pathnames given as arguments can be prevented
414 without error messages using -mindepth 1 or by changing
415 directory and passing "." as argument to find. This works in the
416 old as well as the new version of find.
419 Behavior of devfs rules path matching has been changed.
420 Pattern is now always matched against fully qualified devfs
421 path and slash characters must be explicitly matched by
422 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
423 subdirectories must be reviewed.
426 The default ARM ABI has changed to the ARM EABI. The old ABI is
427 incompatible with the ARM EABI and all programs and modules will
428 need to be rebuilt to work with a new kernel.
430 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
432 NOTE: Support for the old ABI will be removed in the future and
433 users are advised to upgrade.
436 pkg_install has been disconnected from the build if you really need it
437 you should add WITH_PKGTOOLS in your src.conf(5).
440 Most of network statistics structures were changed to be able
441 keep 64-bits counters. Thus all tools, that work with networking
442 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
445 Fix a bug that allowed a tracing process (e.g. gdb) to write
446 to a memory-mapped file in the traced process's address space
447 even if neither the traced process nor the tracing process had
448 write access to that file.
451 CVS has been removed from the base system. An exact copy
452 of the code is available from the devel/cvs port.
455 Some people report the following error after the switch to bmake:
457 make: illegal option -- J
458 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
460 *** [buildworld] Error code 2
462 this likely due to an old instance of make in
463 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
464 which src/Makefile will use that blindly, if it exists, so if
465 you see the above error:
467 rm -rf `make -V MAKEPATH`
472 Use bmake by default.
473 Whereas before one could choose to build with bmake via
474 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
475 make. The goal is to remove these knobs for 10-RELEASE.
477 It is worth noting that bmake (like gmake) treats the command
478 line as the unit of failure, rather than statements within the
479 command line. Thus '(cd some/where && dosomething)' is safer
480 than 'cd some/where; dosomething'. The '()' allows consistent
481 behavior in parallel build.
484 Fix a bug that allows NFS clients to issue READDIR on files.
487 The WITHOUT_IDEA option has been removed because
488 the IDEA patent expired.
491 The sysctl which controls TRIM support under ZFS has been renamed
492 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
496 The mergemaster command now uses the default MAKEOBJDIRPREFIX
497 rather than creating it's own in the temporary directory in
498 order allow access to bootstrapped versions of tools such as
499 install and mtree. When upgrading from version of FreeBSD where
500 the install command does not support -l, you will need to
501 install a new mergemaster command if mergemaster -p is required.
502 This can be accomplished with the command (cd src/usr.sbin/mergemaster
506 Legacy ATA stack, disabled and replaced by new CAM-based one since
507 FreeBSD 9.0, completely removed from the sources. Kernel modules
508 atadisk and atapi*, user-level tools atacontrol and burncd are
509 removed. Kernel option `options ATA_CAM` is now permanently enabled
513 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
514 and socketpair(2). Software, in particular Kerberos, may
515 automatically detect and use these during building. The resulting
516 binaries will not work on older kernels.
519 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
520 information, see the respective 20130304 entry).
523 Recent commits to callout(9) changed the size of struct callout,
524 so the KBI is probably heavily disturbed. Also, some functions
525 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
526 by macros. Every kernel module using it won't load, so rebuild
529 The ctl device has been re-enabled in GENERIC for i386 and amd64,
530 but does not initialize by default (because of the new CTL_DISABLE
531 option) to save memory. To re-enable it, remove the CTL_DISABLE
532 option from the kernel config file or set kern.cam.ctl.disable=0
533 in /boot/loader.conf.
536 The ctl device has been disabled in GENERIC for i386 and amd64.
537 This was done due to the extra memory being allocated at system
538 initialisation time by the ctl driver which was only used if
539 a CAM target device was created. This makes a FreeBSD system
540 unusable on 128MB or less of RAM.
543 A new compression method (lz4) has been merged to -HEAD. Please
544 refer to zpool-features(7) for more information.
546 Please refer to the "ZFS notes" section of this file for information
547 on upgrading boot ZFS pools.
550 A BSD-licensed patch(1) variant has been added and is installed
551 as bsdpatch, being the GNU version the default patch.
552 To inverse the logic and use the BSD-licensed one as default,
553 while having the GNU version installed as gnupatch, rebuild
554 and install world with the WITH_BSD_PATCH knob set.
557 Due to the use of the new -l option to install(1) during build
558 and install, you must take care not to directly set the INSTALL
559 make variable in your /etc/make.conf, /etc/src.conf, or on the
560 command line. If you wish to use the -C flag for all installs
561 you may be able to add INSTALL+=-C to /etc/make.conf or
565 The install(1) option -M has changed meaning and now takes an
566 argument that is a file or path to append logs to. In the
567 unlikely event that -M was the last option on the command line
568 and the command line contained at least two files and a target
569 directory the first file will have logs appended to it. The -M
570 option served little practical purpose in the last decade so its
571 use is expected to be extremely rare.
574 After switching to Clang as the default compiler some users of ZFS
575 on i386 systems started to experience stack overflow kernel panics.
576 Please consider using 'options KSTACK_PAGES=4' in such configurations.
579 GEOM_LABEL now mangles label names read from file system metadata.
580 Mangling affect labels containing spaces, non-printable characters,
581 '%' or '"'. Device names in /etc/fstab and other places may need to
585 By default, only the 10 most recent kernel dumps will be saved. To
586 restore the previous behaviour (no limit on the number of kernel dumps
587 stored in the dump directory) add the following line to /etc/rc.conf:
592 With the addition of auditdistd(8), a new auditdistd user is now
593 required during installworld. "mergemaster -p" can be used to
594 add the user prior to installworld, as documented in the handbook.
597 The sin6_scope_id member variable in struct sockaddr_in6 is now
598 filled by the kernel before passing the structure to the userland via
599 sysctl or routing socket. This means the KAME-specific embedded scope
600 id in sin6_addr.s6_addr[2] is always cleared in userland application.
601 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
602 __FreeBSD_version is bumped to 1000025.
605 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
606 This means that the world and kernel will be compiled with clang
607 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
608 and /usr/bin/cpp. To disable this behavior and revert to building
609 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
610 of current may need to bootstrap WITHOUT_CLANG first if the clang
611 build fails (its compatibility window doesn't extend to the 9 stable
615 The IPFIREWALL_FORWARD kernel option has been removed. Its
616 functionality now turned on by default.
619 The ZERO_COPY_SOCKET kernel option has been removed and
620 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
621 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
622 mechanism which is not safe and may result in kernel crashes.
623 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
624 driver supports disposeable external page sized mbuf storage.
625 Proper replacements for both zero-copy mechanisms are under
626 consideration and will eventually lead to complete removal
627 of the two kernel options.
630 The IPv4 network stack has been converted to network byte
631 order. The following modules need to be recompiled together
632 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
633 pf(4), ipfw(4), ng_ipfw(4), stf(4).
636 Support for non-MPSAFE filesystems was removed from VFS. The
637 VFS_VERSION was bumped, all filesystem modules shall be
641 All the non-MPSAFE filesystems have been disconnected from
642 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
643 portalfs, smbfs, xfs.
646 The interface cloning API and ABI has changed. The following
647 modules need to be recompiled together with kernel:
648 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
649 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
650 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
653 The sdhci driver was split in two parts: sdhci (generic SD Host
654 Controller logic) and sdhci_pci (actual hardware driver).
655 No kernel config modifications are required, but if you
656 load sdhc as a module you must switch to sdhci_pci instead.
659 Import the FUSE kernel and userland support into base system.
662 The GNU sort(1) program has been removed since the BSD-licensed
663 sort(1) has been the default for quite some time and no serious
664 problems have been reported. The corresponding WITH_GNU_SORT
668 The pfil(9) API/ABI for AF_INET family has been changed. Packet
669 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
673 The net80211(4) ABI has been changed to allow for improved driver
674 PS-POLL and power-save support. All wireless drivers need to be
675 recompiled to work with the new kernel.
678 The random(4) support for the VIA hardware random number
679 generator (`PADLOCK') is no longer enabled unconditionally.
680 Add the padlock_rng device in the custom kernel config if
681 needed. The GENERIC kernels on i386 and amd64 do include the
682 device, so the change only affects the custom kernel
686 The pf(4) packet filter ABI has been changed. pfctl(8) and
687 snmp_pf module need to be recompiled to work with new kernel.
690 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
691 to -HEAD. Pools that have empty_bpobj in active state can not be
692 imported read-write with ZFS implementations that do not support
693 this feature. For more information read the zpool-features(5)
697 The sparc64 ZFS loader has been changed to no longer try to auto-
698 detect ZFS providers based on diskN aliases but now requires these
699 to be explicitly listed in the OFW boot-device environment variable.
702 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
703 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
704 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
707 The following sysctls and tunables have been renamed for consistency
708 with other variables:
709 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
710 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
713 The sort utility has been replaced with BSD sort. For now, GNU sort
714 is also available as "gnusort" or the default can be set back to
715 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
716 installed as "bsdsort".
719 A new version of ZFS (pool version 5000) has been merged to -HEAD.
720 Starting with this version the old system of ZFS pool versioning
721 is superseded by "feature flags". This concept enables forward
722 compatibility against certain future changes in functionality of ZFS
723 pools. The first read-only compatible "feature flag" for ZFS pools
724 is named "com.delphix:async_destroy". For more information
725 read the new zpool-features(5) manual page.
726 Please refer to the "ZFS notes" section of this file for information
727 on upgrading boot ZFS pools.
730 The malloc(3) implementation embedded in libc now uses sources imported
731 as contrib/jemalloc. The most disruptive API change is to
732 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
733 delete it prior to installworld, and optionally re-create it using the
734 new format after rebooting. See malloc.conf(5) for details
735 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
739 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
740 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
741 now spelled mips. This is to aid compatibility with third-party
742 software that expects this naming scheme in uname(3). Little-endian
743 settings are unchanged. If you are updating a big-endian mips64 machine
744 from before this change, you may need to set MACHINE_ARCH=mips64 in
745 your environment before the new build system will recognize your machine.
748 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
752 Now unix domain sockets behave "as expected" on nullfs(5). Previously
753 nullfs(5) did not pass through all behaviours to the underlying layer,
754 as a result if we bound to a socket on the lower layer we could connect
755 only to the lower path; if we bound to the upper layer we could connect
756 only to the upper path. The new behavior is one can connect to both the
757 lower and the upper paths regardless what layer path one binds to.
760 The getifaddrs upgrade path broken with 20111215 has been restored.
761 If you have upgraded in between 20111215 and 20120209 you need to
762 recompile libc again with your kernel. You still need to recompile
763 world to be able to configure CARP but this restriction already
767 The set_rcvar() function has been removed from /etc/rc.subr. All
768 base and ports rc.d scripts have been updated, so if you have a
769 port installed with a script in /usr/local/etc/rc.d you can either
770 hand-edit the rcvar= line, or reinstall the port.
772 An easy way to handle the mass-update of /etc/rc.d:
773 rm /etc/rc.d/* && mergemaster -i
776 panic(9) now stops other CPUs in the SMP systems, disables interrupts
777 on the current CPU and prevents other threads from running.
778 This behavior can be reverted using the kern.stop_scheduler_on_panic
780 The new behavior can be incompatible with kern.sync_on_panic.
783 The carp(4) facility has been changed significantly. Configuration
784 of the CARP protocol via ifconfig(8) has changed, as well as format
785 of CARP events submitted to devd(8) has changed. See manual pages
786 for more information. The arpbalance feature of carp(4) is currently
787 not supported anymore.
789 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
790 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
791 need to be recompiled.
794 The acpi_wmi(4) status device /dev/wmistat has been renamed to
798 The option VFS_ALLOW_NONMPSAFE option has been added in order to
799 explicitely support non-MPSAFE filesystems.
800 It is on by default for all supported platform at this present
804 The broken amd(4) driver has been replaced with esp(4) in the amd64,
805 i386 and pc98 GENERIC kernel configuration files.
808 sysinstall has been removed
811 The stable/9 branch created in subversion. This corresponds to the
812 RELENG_9 branch in CVS.
815 This commit modifies vfs_register() so that it uses a hash
816 calculation to set vfc_typenum, which is enabled by default.
817 The first time a system is booted after this change, the
818 vfc_typenum values will change for all file systems. The
819 main effect of this is a change to the NFS server file handles
820 for file systems that use vfc_typenum in their fsid, such as ZFS.
821 It will, however, prevent vfc_typenum from changing when file
822 systems are loaded in a different order for subsequent reboots.
823 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
824 until you are ready to remount all NFS clients after a reboot.
827 Bump the shared library version numbers for libraries that
828 do not use symbol versioning, have changed the ABI compared
829 to stable/8 and which shared library version was not bumped.
830 Done as part of 9.0-RELEASE cycle.
833 During the merge of Capsicum features, the fget(9) KPI was modified.
834 This may require the rebuilding of out-of-tree device drivers --
835 issues have been reported specifically with the nVidia device driver.
836 __FreeBSD_version is bumped to 900041.
838 Also, there is a period between 20110811 and 20110814 where the
839 special devices /dev/{stdin,stdout,stderr} did not work correctly.
840 Building world from a kernel during that window may not work.
843 The packet filter (pf) code has been updated to OpenBSD 4.5.
844 You need to update userland tools to be in sync with kernel.
845 This update breaks backward compatibility with earlier pfsync(4)
846 versions. Care must be taken when updating redundant firewall setups.
849 The following sysctls and tunables are retired on x86 platforms:
851 machdep.hlt_logical_cpus
852 The following sysctl is retired:
853 machdep.hyperthreading_allowed
854 The sysctls were supposed to provide a way to dynamically offline and
855 online selected CPUs on x86 platforms, but the implementation has not
856 been reliable especially with SCHED_ULE scheduler.
857 machdep.hyperthreading_allowed tunable is still available to ignore
858 hyperthreading CPUs at OS level.
859 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
860 where X is an APIC ID of a CPU. Be advised, though, that disabling
861 CPUs in non-uniform fashion will result in non-uniform topology and
862 may lead to sub-optimal system performance with SCHED_ULE, which is
866 cpumask_t type is retired and cpuset_t is used in order to describe
870 Changes to ifconfig(8) for dynamic address family detection mandate
871 that you are running a kernel of 20110525 or later. Make sure to
872 follow the update procedure to boot a new kernel before installing
876 Support for sun4v architecture is officially dropped
879 Several KPI breaking changes have been committed to the mii(4) layer,
880 the PHY drivers and consequently some Ethernet drivers using mii(4).
881 This means that miibus.ko and the modules of the affected Ethernet
882 drivers need to be recompiled.
884 Note to kernel developers: Given that the OUI bit reversion problem
885 was fixed as part of these changes all mii(4) commits related to OUIs,
886 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
887 handling, no longer can be merged verbatim to stable/8 and previous
891 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
892 into their kernel configurations along with 'device pci'.
895 The default NFS client is now the new NFS client, so fstype "newnfs"
896 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
897 Although mounts via fstype "nfs" will usually work without userland
898 changes, it is recommended that the mount(8) and mount_nfs(8)
899 commands be rebuilt from sources and that a link to mount_nfs called
900 mount_oldnfs be created. The new client is compiled into the
901 kernel with "options NFSCL" and this is needed for diskless root
902 file systems. The GENERIC kernel configs have been changed to use
903 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
904 To use the regular/old client, you can "mount -t oldnfs ...". For
905 a diskless root file system, you must also include a line like:
907 vfs.root.mountfrom="oldnfs:"
909 in the boot/loader.conf on the root fs on the NFS server to make
910 a diskless root fs use the old client.
913 The GENERIC kernels for all architectures now default to the new
914 CAM-based ATA stack. It means that all legacy ATA drivers were
915 removed and replaced by respective CAM drivers. If you are using
916 ATA device names in /etc/fstab or other places, make sure to update
917 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
918 where 'Y's are the sequential numbers starting from zero for each type
919 in order of detection, unless configured otherwise with tunables,
920 see cam(4)). There will be symbolic links created in /dev/ to map
921 old adX devices to the respective adaY. They should provide basic
922 compatibility for file systems mounting in most cases, but they do
923 not support old user-level APIs and do not have respective providers
924 in GEOM. Consider using updated management tools with new device names.
926 It is possible to load devices ahci, ata, siis and mvs as modules,
927 but option ATA_CAM should remain in kernel configuration to make ata
928 module work as CAM driver supporting legacy ATA controllers. Device ata
929 still can be used in modular fashion (atacore + ...). Modules atadisk
930 and atapi* are not used and won't affect operation in ATA_CAM mode.
931 Note that to use CAM-based ATA kernel should include CAM devices
932 scbus, pass, da (or explicitly ada), cd and optionally others. All of
933 them are parts of the cam module.
935 ataraid(4) functionality is now supported by the RAID GEOM class.
936 To use it you can load geom_raid kernel module and use graid(8) tool
937 for management. Instead of /dev/arX device names, use /dev/raid/rX.
939 No kernel config options or code have been removed, so if a problem
940 arises, please report it and optionally revert to the old ATA stack.
941 In order to do it you can remove from the kernel config:
946 , and instead add back:
947 device atadisk # ATA disk drives
948 device ataraid # ATA RAID drives
949 device atapicd # ATAPI CDROM drives
950 device atapifd # ATAPI floppy drives
951 device atapist # ATAPI tape drives
954 The default NFS server has been changed to the new server, which
955 was referred to as the experimental server. If you need to switch
956 back to the old NFS server, you must now put the "-o" option on
957 both the mountd and nfsd commands. This can be done using the
958 mountd_flags and nfs_server_flags rc.conf variables until an
959 update to the rc scripts is committed, which is coming soon.
962 The GNU Objective-C runtime library (libobjc), and other Objective-C
963 related components have been removed from the base system. If you
964 require an Objective-C library, please use one of the available ports.
967 ath(4) has been split into bus- and device- modules. if_ath contains
968 the HAL, the TX rate control and the network device code. if_ath_pci
969 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
970 contains the AHB glue. Users need to load both if_ath_pci and if_ath
971 in order to use ath on everything else.
973 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
974 need to load if_ath and if_ath_pci for ath(4) operation.
977 As part of the replacement of sysinstall, the process of building
978 release media has changed significantly. For details, please re-read
979 release(7), which has been updated to reflect the new build process.
982 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
983 is the last available version under GPLv2. It brings a number of new
984 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
985 4.1 and SSE 4.2), better support for powerpc64, a number of new
986 directives, and lots of other small improvements. See the ChangeLog
987 file in contrib/binutils for the full details.
990 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
991 compliant, and will now use half of hash for authentication.
992 This will break interoperability with all stacks (including all
993 actual FreeBSD versions) who implement
994 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
996 The only workaround with such peers is to use another HMAC
997 algorithm for IPsec ("phase 2") authentication.
1000 Remove the uio_yield prototype and symbol. This function has
1001 been misnamed since it was introduced and should not be
1002 globally exposed with this name. The equivalent functionality
1003 is now available using kern_yield(curthread->td_user_pri).
1004 The function remains undocumented.
1007 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1008 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1009 for scalar sysctls is defined but disabled. Code that needs
1010 UQUAD to pass the type checking that must compile on older
1011 systems where the define is not present can check against
1012 __FreeBSD_version >= 900030.
1014 The system dialog(1) has been replaced with a new version previously
1015 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1016 with the previous version, but the libdialog associated with it has
1017 a largely incompatible API. As such, the original version of libdialog
1018 will be kept temporarily as libodialog, until its base system consumers
1019 are replaced or updated. Bump __FreeBSD_version to 900030.
1022 If you are trying to run make universe on a -stable system, and you get
1023 the following warning:
1024 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1025 unknown. config(8) likely too old."
1026 or something similar to it, then you must upgrade your -stable system
1027 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1028 stable/8) or build the config from the latest stable/8 branch and
1029 install it on your system.
1031 Prior to this date, building a current universe on 8-stable system from
1032 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1033 error in the first kernel build phase. A new config on those old
1034 systems will fix that problem for older versions of -current.
1037 The TCP stack has been modified to allow Khelp modules to interact with
1038 it via helper hook points and store per-connection data in the TCP
1039 control block. Bump __FreeBSD_version to 900029. User space tools that
1040 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1044 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1045 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1046 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1047 to take advantage of it instead of using custom implementations. This
1048 means that these drivers now no longer unconditionally advertise
1049 support for flow control but only do so if flow control is a selected
1050 media option. This was implemented in the generic support that way in
1051 order to allow flow control to be switched on and off via ifconfig(8)
1052 with the PHY specific default to typically off in order to protect
1053 from unwanted effects. Consequently, if you used flow control with
1054 one of the above mentioned drivers you now need to explicitly enable
1055 it, for example via:
1056 ifconfig bge0 media auto mediaopt flowcontrol
1058 Along with the above mentioned changes generic support for setting
1059 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1060 e1000phy(4) as well as ip1000phy(4) have been converted to take
1061 advantage of it. This means that these drivers now no longer take the
1062 link0 parameter for selecting master mode but the master media option
1063 has to be used instead, for example like in the following:
1064 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1066 Selection of master mode now is also available with all other PHY
1067 drivers supporting 1000baseT.
1070 The TCP stack has received a significant update to add support for
1071 modularised congestion control and generally improve the clarity of
1072 congestion control decisions. Bump __FreeBSD_version to 900025. User
1073 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1074 sockstat) need to be recompiled.
1077 The man(1) utility has been replaced by a new version that no longer
1078 uses /etc/manpath.config. Please consult man.conf(5) for how to
1079 migrate local entries to the new format.
1082 The copyright strings printed by login(1) and sshd(8) at the time of a
1083 new connection have been removed to follow other operating systems and
1087 A workaround for a fixed ld bug has been removed in kernel code,
1088 so make sure that your system ld is built from sources after
1089 revision 210245 from 2010-07-19 (r211583 if building head kernel
1090 on stable/8, r211584 for stable/7; both from 2010-08-21).
1091 A symptom of incorrect ld version is different addresses for
1092 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1095 The $ipv6_prefer variable in rc.conf(5) has been split into
1096 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1098 The $ip6addrctl_policy is a variable to choose a pre-defined
1099 address selection policy set by ip6addrctl(8). A value
1100 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1103 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1104 flag (see an entry of 20090926) is set on an interface with no
1105 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1106 security reason. If you want IPv6 link-local address on all
1107 interfaces by default, set this to "YES".
1109 The old ipv6_prefer="YES" is equivalent to
1110 ipv6_activate_all_interfaces="YES" and
1111 ip6addrctl_policy="ipv6_prefer".
1114 DTrace has grown support for userland tracing. Due to this, DTrace is
1115 now i386 and amd64 only.
1116 dtruss(1) is now installed by default on those systems and a new
1117 kernel module is needed for userland tracing: fasttrap.
1118 No changes to your kernel config file are necessary to enable
1119 userland tracing, but you might consider adding 'STRIP=' and
1120 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1121 to have informative userland stack traces in DTrace (ustack).
1124 The acpi_aiboost(4) driver has been removed in favor of the new
1125 aibs(4) driver. You should update your kernel configuration file.
1128 BSD grep has been imported to the base system and it is built by
1129 default. It is completely BSD licensed, highly GNU-compatible, uses
1130 less memory than its GNU counterpart and has a small codebase.
1131 However, it is slower than its GNU counterpart, which is mostly
1132 noticeable for larger searches, for smaller ones it is measurable
1133 but not significant. The reason is complex, the most important factor
1134 is that we lack a modern and efficient regex library and GNU
1135 overcomes this by optimizing the searches internally. Future work
1136 on improving the regex performance is planned, for the meantime,
1137 users that need better performance, can build GNU grep instead by
1138 setting the WITH_GNU_GREP knob.
1141 Due to the import of powerpc64 support, all existing powerpc kernel
1142 configuration files must be updated with a machine directive like this:
1143 machine powerpc powerpc
1145 In addition, an updated config(8) is required to build powerpc kernels
1149 A new version of ZFS (version 15) has been merged to -HEAD.
1150 This version uses a python library for the following subcommands:
1151 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1152 For full functionality of these commands the following port must
1153 be installed: sysutils/py-zfs
1156 'vm_page's are now hashed by physical address to an array of mutexes.
1157 Currently this is only used to serialize access to hold_count. Over
1158 time the page queue mutex will be peeled away. This changes the size
1159 of pmap on every architecture. And requires all callers of vm_page_hold
1160 and vm_page_unhold to be updated.
1163 WITH_CTF can now be specified in src.conf (not recommended, there
1164 are some problems with static executables), make.conf (would also
1165 affect ports which do not use GNU make and do not override the
1166 compile targets) or in the kernel config (via "makeoptions
1168 When WITH_CTF was specified there before this was silently ignored,
1169 so make sure that WITH_CTF is not used in places which could lead
1170 to unwanted behavior.
1173 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1174 to allow 32-bit compatibility on non-x86 platforms. All kernel
1175 configurations on amd64 and ia64 platforms using these options must
1176 be modified accordingly.
1179 The utmp user accounting database has been replaced with utmpx,
1180 the user accounting interface standardized by POSIX.
1181 Unfortunately the semantics of utmp and utmpx don't match,
1182 making it practically impossible to support both interfaces.
1183 The user accounting database is used by tools like finger(1),
1184 last(1), talk(1), w(1) and ac(8).
1186 All applications in the base system use utmpx. This means only
1187 local binaries (e.g. from the ports tree) may still use these
1188 utmp database files. These applications must be rebuilt to make
1191 After the system has been upgraded, it is safe to remove the old
1192 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1193 assuming their contents is of no importance anymore. Old wtmp
1194 databases can only be used by last(1) and ac(8) after they have
1195 been converted to the new format using wtmpcvt(1).
1198 Introduce the kernel thread "deadlock resolver" (which can be enabled
1199 via the DEADLKRES option, see NOTES for more details) and the
1200 sleepq_type() function for sleepqueues.
1203 The rc.firewall and rc.firewall6 were unified, and
1204 rc.firewall6 and rc.d/ip6fw were removed.
1205 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1206 variables are obsoleted. Instead, the following new rc
1207 variables are added to rc.d/ipfw:
1209 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1210 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1211 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1213 The meanings correspond to the relevant IPv4 variables.
1219 The default terminal emulation for syscons(4) has been changed
1220 from cons25 to xterm on all platforms except pc98. This means
1221 that the /etc/ttys file needs to be updated to ensure correct
1222 operation of applications on the console.
1224 The terminal emulation style can be toggled per window by using
1225 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1226 options can be used to change the compile-time default back to
1229 To prevent graphical artifacts, make sure the TERM environment
1230 variable is set to match the terminal emulation that is being
1231 performed by syscons(4).
1234 The layout of the structure ieee80211req_scan_result has changed.
1235 Applications that require wireless scan results (e.g. ifconfig(8))
1236 from net80211 need to be recompiled.
1238 Applications such as wpa_supplicant(8) may require a full world
1239 build without using NO_CLEAN in order to get synchronized with the
1243 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1244 There's one kernel module for each firmware. Adding "device iwnfw"
1245 to the kernel configuration file means including all three firmware
1246 images inside the kernel. If you want to include just the one for
1247 your wireless card, use the devices iwn4965fw, iwn5000fw or
1251 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1252 into rc.d/netif. The changes are the following:
1254 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1255 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1256 Note that both variables need the "inet6" keyword at the head.
1258 Do not set $ipv6_network_interfaces manually if you do not
1259 understand what you are doing. It is not needed in most cases.
1261 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1264 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1265 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1267 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1268 all configured interfaces have "inet6 accept_rtadv" in the
1269 $ifconfig_IF_ipv6. These are for backward compatibility.
1271 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1272 functionality of interfaces with no corresponding
1273 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1274 and the default address selection policy of ip6addrctl(8)
1275 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1276 Note that if you want to configure IPv6 functionality on the
1277 disabled interfaces after boot, first you need to clear the flag by
1278 using ifconfig(8) like:
1280 ifconfig em0 inet6 -ifdisabled
1282 If YES, the default address selection policy is set as
1285 The default value of $ipv6_prefer is NO.
1287 4. If your system need to receive Router Advertisement messages,
1288 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1289 scripts automatically invoke rtsol(8) when the interface becomes
1290 UP. The Router Advertisement messages are used for SLAAC
1291 (State-Less Address AutoConfiguration).
1294 802.11s D3.03 support was committed. This is incompatible with the
1295 previous code, which was based on D3.0.
1298 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1299 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1300 control whether accepting Router Advertisement messages or not.
1301 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1302 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1303 The ifconfig(8) utility now supports these flags.
1306 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1307 mount(8) and -a option for df(1) to see them.
1310 The old tunable hw.bus.devctl_disable has been superseded by
1311 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1312 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1316 Remove the option STOP_NMI. The default action is now to use NMI only
1317 for KDB via the newly introduced function stop_cpus_hard() and
1318 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1321 The stable/8 branch created in subversion. This corresponds to the
1322 RELENG_8 branch in CVS.
1325 Bump the shared library version numbers for all libraries that do not
1326 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1327 __FreeBSD_version to 800105.
1330 Due to changes in the implementation of virtual network stack support,
1331 all network-related kernel modules must be recompiled. As this change
1332 breaks the ABI, bump __FreeBSD_version to 800104.
1335 The TOE interface to the TCP syncache has been modified to remove
1336 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1337 The cxgb driver is the only TOE consumer affected by this change, and
1338 needs to be recompiled along with the kernel. As this change breaks
1339 the ABI, bump __FreeBSD_version to 800103.
1342 Padding has been added to struct tcpcb, sackhint and tcpstat in
1343 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1344 maintaining the ABI. However, this change breaks the ABI, so bump
1345 __FreeBSD_version to 800102. User space tools that rely on the size of
1346 any of these structs (e.g. sockstat) need to be recompiled.
1349 The NFS_LEGACYRPC option has been removed along with the old kernel
1350 RPC implementation that this option selected. Kernel configurations
1351 may need to be adjusted.
1354 The network interface device nodes at /dev/net/<interface> have been
1355 removed. All ioctl operations can be performed the normal way using
1356 routing sockets. The kqueue functionality can generally be replaced
1357 with routing sockets.
1360 The documentation from the FreeBSD Documentation Project (Handbook,
1361 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1362 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1365 The ABI of various structures related to the SYSV IPC API have been
1366 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1367 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1371 Layout of struct vnet has changed as routing related variables were
1372 moved to their own Vimage module. Modules need to be recompiled. Bump
1373 __FreeBSD_version to 800099.
1376 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1377 respectively. As long as no more than 16 groups per process are used,
1378 no changes should be visible. When more than 16 groups are used, old
1379 binaries may fail if they call getgroups() or getgrouplist() with
1380 statically sized storage. Recompiling will work around this, but
1381 applications should be modified to use dynamically allocated storage
1382 for group arrays as POSIX.1-2008 does not cap an implementation's
1383 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1385 NFS and portalfs mounts may also be affected as the list of groups is
1386 truncated to 16. Users of NFS who use more than 16 groups, should
1387 take care that negative group permissions are not used on the exported
1388 file systems as they will not be reliable unless a GSSAPI based
1389 authentication method is used.
1392 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1393 option compiles in the support for adaptive spinning for lockmgrs
1394 which want to enable it. The lockinit() function now accepts the flag
1395 LK_ADAPTIVE in order to make the lock object subject to adaptive
1396 spinning when both held in write and read mode.
1399 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1400 changed. User applications that use this ioctl need to be rebuilt.
1403 The layout of struct thread has changed. Kernel and modules need to
1407 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1408 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1411 window(1) has been removed from the base system. It can now be
1412 installed from ports. The port is called misc/window.
1415 The way we are storing and accessing `routing table' entries has
1416 changed. Programs reading the FIB, like netstat, need to be
1420 A new netisr implementation has been added for FreeBSD 8. Network
1421 file system modules, such as igmp, ipdivert, and others, should be
1423 Bump __FreeBSD_version to 800096.
1426 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1430 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1431 Bump __FreeBSD_version to 800094.
1434 Add mnt_xflag field to 'struct mount'. File system modules need to be
1436 Bump __FreeBSD_version to 800093.
1439 The compiling option ADAPTIVE_SX has been retired while it has been
1440 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1441 The KPI for sx_init_flags() changes as accepting flags:
1442 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1443 been introduced in order to handle the reversed logic.
1444 Bump __FreeBSD_version to 800092.
1447 Add support for hierarchical jails. Remove global securelevel.
1448 Bump __FreeBSD_version to 800091.
1451 The layout of struct vnet_net has changed, therefore modules
1453 Bump __FreeBSD_version to 800090.
1456 The newly imported zic(8) produces a new format in the output. Please
1457 run tzsetup(8) to install the newly created data to /etc/localtime.
1460 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1461 hw.usb.* and is now consistent again with previous releases.
1464 802.11 monitor mode support was revised and driver api's were changed.
1465 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1466 of DLT_IEEE802_11. No user-visible data structures were changed but
1467 applications that use DLT_IEEE802_11 may require changes.
1468 Bump __FreeBSD_version to 800088.
1471 The layout of the following structs has changed: sysctl_oid,
1472 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1473 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1474 panics may be experienced. World rebuild is required for
1475 correctly checking networking state from userland.
1476 Bump __FreeBSD_version to 800085.
1479 MLDv2 and Source-Specific Multicast (SSM) have been merged
1480 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1481 The implementation of SSM within FreeBSD's IPv6 stack closely
1482 follows the IPv4 implementation.
1484 For kernel developers:
1486 * The most important changes are that the ip6_output() and
1487 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1488 and this lock has been downgraded to a non-recursive mutex.
1490 * As with the changes to the IPv4 stack to support SSM, filtering
1491 of inbound multicast traffic must now be performed by transport
1492 protocols within the IPv6 stack. This does not apply to TCP and
1493 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1495 * The KPIs used by IPv6 multicast are similar to those used by
1496 the IPv4 stack, with the following differences:
1497 * im6o_mc_filter() is analogous to imo_multicast_filter().
1498 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1499 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1500 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1501 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1502 for MLDv1 have an additional 'timer' argument which is used to
1503 jitter the initial membership report for the solicited-node
1504 multicast membership on-link.
1505 * This is not strictly needed for MLDv2, which already jitters
1506 its report transmissions. However, the 'timer' argument is
1507 preserved in case MLDv1 is active on the interface.
1509 * The KAME linked-list based IPv6 membership implementation has
1510 been refactored to use a vector similar to that used by the IPv4
1512 Code which maintains a list of its own multicast memberships
1513 internally, e.g. carp, has been updated to reflect the new
1516 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1517 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1518 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1519 implementation constraint which needs to be addressed in HEAD.
1521 For application developers:
1523 * The changes are broadly similar to those made for the IPv4
1526 * The use of IPv4 and IPv6 multicast socket options on the same
1527 socket, using mapped addresses, HAS NOT been tested or supported.
1529 * There are a number of issues with the implementation of various
1530 IPv6 multicast APIs which need to be resolved in the API surface
1531 before the implementation is fully compatible with KAME userland
1532 use, and these are mostly to do with interface index treatment.
1534 * The literature available discusses the use of either the delta / ASM
1535 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1536 using setsourcefilter(3)/getsourcefilter(3). For more information
1537 please refer to RFC 3768, 'Socket Interface Extensions for
1538 Multicast Source Filters'.
1540 * Applications which use the published RFC 3678 APIs should be fine.
1542 For systems administrators:
1544 * The mtest(8) utility has been refactored to support IPv6, in
1545 addition to IPv4. Interface addresses are no longer accepted
1546 as arguments, their names must be used instead. The utility
1547 will map the interface name to its first IPv4 address as
1548 returned by getifaddrs(3).
1550 * The ifmcstat(8) utility has also been updated to print the MLDv2
1551 endpoint state and source filter lists via sysctl(3).
1553 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1554 loopback of IPv6 multicast datagrams by default; it defaults to 1
1555 to preserve the existing behaviour. Disabling multicast loopback is
1556 recommended for optimal system performance.
1558 * The IPv6 MROUTING code has been changed to examine this sysctl
1559 instead of attempting to perform a group lookup before looping
1560 back forwarded datagrams.
1562 Bump __FreeBSD_version to 800084.
1565 Implement low-level Bluetooth HCI API.
1566 Bump __FreeBSD_version to 800083.
1569 The layout of struct malloc_type, used by modules to register new
1570 memory allocation types, has changed. Most modules will need to
1571 be rebuilt or panics may be experienced.
1572 Bump __FreeBSD_version to 800081.
1575 Anticipate overflowing inp_flags - add inp_flags2.
1576 This changes most offsets in inpcb, so checking v4 connection
1577 state will require a world rebuild.
1578 Bump __FreeBSD_version to 800080.
1581 Add an llentry to struct route and struct route_in6. Modules
1582 embedding a struct route will need to be recompiled.
1583 Bump __FreeBSD_version to 800079.
1586 The size of rt_metrics_lite and by extension rtentry has changed.
1587 Networking administration apps will need to be recompiled.
1588 The route command now supports show as an alias for get, weighting
1589 of routes, sticky and nostick flags to alter the behavior of stateful
1591 Bump __FreeBSD_version to 800078.
1594 Do not use Giant for kbdmux(4) locking. This is wrong and
1595 apparently causing more problems than it solves. This will
1596 re-open the issue where interrupt handlers may race with
1597 kbdmux(4) in polling mode. Typical symptoms include (but
1598 not limited to) duplicated and/or missing characters when
1599 low level console functions (such as gets) are used while
1600 interrupts are enabled (for example geli password prompt,
1601 mountroot prompt etc.). Disabling kbdmux(4) may help.
1604 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1605 kernel modules referencing any of the above need to be recompiled.
1606 Bump __FreeBSD_version to 800075.
1609 GEOM_PART has become the default partition slicer for storage devices,
1610 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1611 introduces some changes:
1613 MSDOS/EBR: the devices created from MSDOS extended partition entries
1614 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1615 to devices with offset-based names. fstabs may need to be modified.
1617 BSD: the "geometry does not match label" warning is harmless in most
1618 cases but it points to problems in file system misalignment with
1619 disk geometry. The "c" partition is now implicit, covers the whole
1620 top-level drive and cannot be (mis)used by users.
1622 General: Kernel dumps are now not allowed to be written to devices
1623 whose partition types indicate they are meant to be used for file
1624 systems (or, in case of MSDOS partitions, as something else than
1627 Most of these changes date approximately from 200812.
1630 The uscanner(4) driver has been removed from the kernel. This follows
1631 Linux removing theirs in 2.6 and making libusb the default interface
1632 (supported by sane).
1635 The multicast forwarding code has been cleaned up. netstat(1)
1636 only relies on KVM now for printing bandwidth upcall meters.
1637 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1638 ip6_mroute_mod respectively. The config(5) options for statically
1639 compiling this code remain the same, i.e. 'options MROUTING'.
1642 Support for the IFF_NEEDSGIANT network interface flag has been
1643 removed, which means that non-MPSAFE network device drivers are no
1644 longer supported. In particular, if_ar, if_sr, and network device
1645 drivers from the old (legacy) USB stack can no longer be built or
1649 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1650 a bunch of new language catalog files have also been added.
1651 This means that some common libc messages are now localized and
1652 they depend on the LC_MESSAGES environmental variable.
1655 The k8temp(4) driver has been renamed to amdtemp(4) since
1656 support for Family 10 and Family 11 CPU families was added.
1659 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1660 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1662 For kernel developers, the most important changes are that the
1663 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1664 and this lock has been downgraded to a non-recursive mutex.
1666 Transport protocols (UDP, Raw IP) are now responsible for filtering
1667 inbound multicast traffic according to group membership and source
1668 filters. The imo_multicast_filter() KPI exists for this purpose.
1669 Transports which do not use multicast (SCTP, TCP) already reject
1670 multicast by default. Forwarding and receive performance may improve
1671 as a mutex acquisition is no longer needed in the ip_input()
1672 low-level input path. in_addmulti() and in_delmulti() are shimmed
1673 to new KPIs which exist to support SSM in-kernel.
1675 For application developers, it is recommended that loopback of
1676 multicast datagrams be disabled for best performance, as this
1677 will still cause the lock to be taken for each looped-back
1678 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1679 be tuned to 0 to disable loopback by default; it defaults to 1
1680 to preserve the existing behaviour.
1682 For systems administrators, to obtain best performance with
1683 multicast reception and multiple groups, it is always recommended
1684 that a card with a suitably precise hash filter is used. Hash
1685 collisions will still result in the lock being taken within the
1686 transport protocol input path to check group membership.
1688 If deploying FreeBSD in an environment with IGMP snooping switches,
1689 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1690 enabled; this forces 224.0.0.0/24 group membership to be announced
1693 The size of 'struct igmpstat' has changed; netstat needs to be
1694 recompiled to reflect this.
1695 Bump __FreeBSD_version to 800070.
1698 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1699 updated to use it. This requires a buildworld/installworld in order to
1700 update the library and dependencies (usbconfig, etc). Its advisable to
1701 rebuild all ports which uses libusb. More specific directions are given
1702 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1703 libusb are no longer required and can be removed.
1706 A workaround is committed to allow the creation of System V shared
1707 memory segment of size > 2 GB on the 64-bit architectures.
1708 Due to a limitation of the existing ABI, the shm_segsz member
1709 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1710 wrong for large segments. Note that limits must be explicitly
1711 raised to allow such segments to be created.
1714 The layout of struct ifnet has changed, requiring a rebuild of all
1715 network device driver modules.
1718 The /dev handling for the new USB stack has changed, a
1719 buildworld/installworld is required for libusb20.
1722 The new USB2 stack has now been permanently moved in and all kernel and
1723 module names reverted to their previous values (eg, usb, ehci, ohci,
1724 ums, ...). The old usb stack can be compiled in by prefixing the name
1725 with the letter 'o', the old usb modules have been removed.
1726 Updating entry 20090216 for xorg and 20090215 for libmap may still
1730 The rc.conf(5) option if_up_delay has been renamed to
1731 defaultroute_delay to better reflect its purpose. If you have
1732 customized this setting in /etc/rc.conf you need to update it to
1736 xorg 7.4 wants to configure its input devices via hald which does not
1737 yet work with USB2. If the keyboard/mouse does not work in xorg then
1739 Option "AllowEmptyInput" "off"
1740 to your ServerLayout section. This will cause X to use the configured
1741 kbd and mouse sections from your xorg.conf.
1744 The GENERIC kernels for all architectures now default to the new USB2
1745 stack. No kernel config options or code have been removed so if a
1746 problem arises please report it and optionally revert to the old USB
1747 stack. If you are loading USB kernel modules or have a custom kernel
1748 that includes GENERIC then ensure that usb names are also changed over,
1749 eg uftdi -> usb2_serial_ftdi.
1751 Older programs linked against the ports libusb 0.1 need to be
1752 redirected to the new stack's libusb20. /etc/libmap.conf can
1754 # Map old usb library to new one for usb2 stack
1755 libusb-0.1.so.8 libusb20.so.1
1758 All USB ethernet devices now attach as interfaces under the name ueN
1759 (eg. ue0). This is to provide a predictable name as vendors often
1760 change usb chipsets in a product without notice.
1763 The ichsmb(4) driver has been changed to require SMBus slave
1764 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1765 All of the other SMBus controller drivers require left-justified
1766 slave addresses, so this change makes all the drivers provide the
1770 INET6 statistics (struct ip6stat) was updated.
1771 netstat(1) needs to be recompiled.
1774 NTFS has been removed from GENERIC kernel on amd64 to match
1775 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1776 will load ntfs.ko module automatically when NTFS support is
1777 actually needed, unless ntfs.ko is not installed or security
1778 level prohibits loading kernel modules. If either is the case,
1779 "options NTFS" has to be added into kernel config.
1782 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1783 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1784 800061. User space tools that rely on the size of struct tcpcb in
1785 tcp_var.h (e.g. sockstat) need to be recompiled.
1788 ng_tty(4) module updated to match the new TTY subsystem.
1789 Due to API change, user-level applications must be updated.
1790 New API support added to mpd5 CVS and expected to be present
1791 in next mpd5.3 release.
1794 With __FreeBSD_version 800060 the makefs tool is part of
1795 the base system (it was a port).
1798 The afdata and ifnet locks have been changed from mutexes to
1799 rwlocks, network modules will need to be re-compiled.
1802 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1803 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1804 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1805 architecture and 40 bytes on 64-bit architecture. The userland
1806 applications "arp" and "ndp" have been updated accordingly.
1807 The output from "netstat -r" shows only routing entries and
1808 none of the L2 information.
1811 __FreeBSD_version 800057 marks the switchover from the
1812 binary ath hal to source code. Users must add the line:
1814 options AH_SUPPORT_AR5416
1816 to their kernel config files when specifying:
1820 The ath_hal module no longer exists; the code is now compiled
1821 together with the driver in the ath module. It is now
1822 possible to tailor chip support (i.e. reduce the set of chips
1823 and thereby the code size); consult ath_hal(4) for details.
1826 __FreeBSD_version 800054 adds memory barriers to
1827 <machine/atomic.h>, new interfaces to ifnet to facilitate
1828 multiple hardware transmit queues for cards that support
1829 them, and a lock-less ring-buffer implementation to
1830 enable drivers to more efficiently manage queueing of
1834 A new version of ZFS (version 13) has been merged to -HEAD.
1835 This version has zpool attribute "listsnapshots" off by
1836 default, which means "zfs list" does not show snapshots,
1837 and is the same as Solaris behavior.
1840 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1843 The uhci, ohci, ehci and slhci USB Host controller drivers have
1844 been put into separate modules. If you load the usb module
1845 separately through loader.conf you will need to load the
1846 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1847 controller add the following to loader.conf:
1853 The ABI used by the PMC toolset has changed. Please keep
1854 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1858 atapci kernel module now includes only generic PCI ATA
1859 driver. AHCI driver moved to ataahci kernel module.
1860 All vendor-specific code moved into separate kernel modules:
1861 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1862 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1863 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1864 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1867 The TTY subsystem of the kernel has been replaced by a new
1868 implementation, which provides better scalability and an
1869 improved driver model. Most common drivers have been migrated to
1870 the new TTY subsystem, while others have not. The following
1871 drivers have not yet been ported to the new TTY layer:
1874 cy, digi, rc, rp, sio
1880 ng_h4, ng_tty, ppp, sl, snp
1882 Adding these drivers to your kernel configuration file shall
1883 cause compilation to fail.
1886 ntpd has been upgraded to 4.2.4p5.
1889 OpenSSH has been upgraded to 5.1p1.
1891 For many years, FreeBSD's version of OpenSSH preferred DSA
1892 over RSA for host and user authentication keys. With this
1893 upgrade, we've switched to the vendor's default of RSA over
1894 DSA. This may cause upgraded clients to warn about unknown
1895 host keys even for previously known hosts. Users should
1896 follow the usual procedure for verifying host keys before
1897 accepting the RSA key.
1899 This can be circumvented by setting the "HostKeyAlgorithms"
1900 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1903 Please note that the sequence of keys offered for
1904 authentication has been changed as well. You may want to
1905 specify IdentityFile in a different order to revert this
1909 The sio(4) driver has been removed from the i386 and amd64
1910 kernel configuration files. This means uart(4) is now the
1911 default serial port driver on those platforms as well.
1913 To prevent collisions with the sio(4) driver, the uart(4) driver
1914 uses different names for its device nodes. This means the
1915 onboard serial port will now most likely be called "ttyu0"
1916 instead of "ttyd0". You may need to reconfigure applications to
1917 use the new device names.
1919 When using the serial port as a boot console, be sure to update
1920 /boot/device.hints and /etc/ttys before booting the new kernel.
1921 If you forget to do so, you can still manually specify the hints
1922 at the loader prompt:
1924 set hint.uart.0.at="isa"
1925 set hint.uart.0.port="0x3F8"
1926 set hint.uart.0.flags="0x10"
1927 set hint.uart.0.irq="4"
1931 The gpt(8) utility has been removed. Use gpart(8) to partition
1935 The version that Linuxulator emulates was changed from 2.4.2
1936 to 2.6.16. If you experience any problems with Linux binaries
1937 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1938 if it fixes the problem contact emulation mailing list.
1941 ISDN4BSD (I4B) was removed from the src tree. You may need to
1942 update a your kernel configuration and remove relevant entries.
1945 I have checked in code to support multiple routing tables.
1946 See the man pages setfib(1) and setfib(2).
1947 This is a hopefully backwards compatible version,
1948 but to make use of it you need to compile your kernel
1949 with options ROUTETABLES=2 (or more up to 16).
1952 The 802.11 wireless support was redone to enable multi-bss
1953 operation on devices that are capable. The underlying device
1954 is no longer used directly but instead wlanX devices are
1955 cloned with ifconfig. This requires changes to rc.conf files.
1956 For example, change:
1957 ifconfig_ath0="WPA DHCP"
1960 ifconfig_wlan0="WPA DHCP"
1961 see rc.conf(5) for more details. In addition, mergemaster of
1962 /etc/rc.d is highly recommended. Simultaneous update of userland
1963 and kernel wouldn't hurt either.
1965 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1966 modules were merged into the base wlan module. All references
1967 to these modules (e.g. in kernel config files) must be removed.
1970 psm(4) has gained write(2) support in native operation level.
1971 Arbitrary commands can be written to /dev/psm%d and status can
1972 be read back from it. Therefore, an application is responsible
1973 for status validation and error recovery. It is a no-op in
1974 other operation levels.
1977 Support for KSE threading has been removed from the kernel. To
1978 run legacy applications linked against KSE libmap.conf may
1979 be used. The following libmap.conf may be used to ensure
1980 compatibility with any prior release:
1982 libpthread.so.1 libthr.so.1
1983 libpthread.so.2 libthr.so.2
1984 libkse.so.3 libthr.so.3
1987 The layout of struct vmspace has changed. This affects libkvm
1988 and any executables that link against libkvm and use the
1989 kvm_getprocs() function. In particular, but not exclusively,
1990 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1991 The effects are minimal, but it's advisable to upgrade world
1995 The latest em driver no longer has support in it for the
1996 82575 adapter, this is now moved to the igb driver. The
1997 split was done to make new features that are incompatible
1998 with older hardware easier to do.
2001 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2002 likewise the kernel option is now GEOM_LINUX_LVM.
2005 The default NFS mount mode has changed from UDP to TCP for
2006 increased reliability. If you rely on (insecurely) NFS
2007 mounting across a firewall you may need to update your
2011 Belatedly note the addition of m_collapse for compacting
2015 The fts(3) structures have been changed to use adequate
2016 integer types for their members and so to be able to cope
2017 with huge file trees. The old fts(3) ABI is preserved
2018 through symbol versioning in libc, so third-party binaries
2019 using fts(3) should still work, although they will not take
2020 advantage of the extended types. At the same time, some
2021 third-party software might fail to build after this change
2022 due to unportable assumptions made in its source code about
2023 fts(3) structure members. Such software should be fixed
2024 by its vendor or, in the worst case, in the ports tree.
2025 FreeBSD_version 800015 marks this change for the unlikely
2026 case that a portable fix is impossible.
2029 To upgrade to -current after this date, you must be running
2030 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2031 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2034 The ADAPTIVE_GIANT kernel option has been retired because its
2035 functionality is the default now.
2038 The AT keyboard emulation of sunkbd(4) has been turned on
2039 by default. In order to make the special symbols of the Sun
2040 keyboards driven by sunkbd(4) work under X these now have
2041 to be configured the same way as Sun USB keyboards driven
2042 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2044 Option "XkbLayout" "us"
2045 Option "XkbRules" "xorg"
2046 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2049 It has been decided that it is desirable to provide ABI
2050 backwards compatibility to the FreeBSD 4/5/6 versions of the
2051 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2052 broken with the introduction of PCI domain support (see the
2053 20070930 entry). Unfortunately, this required the ABI of
2054 PCIOCGETCONF to be broken again in order to be able to
2055 provide backwards compatibility to the old version of that
2056 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2057 again. As for prominent ports this affects neither pciutils
2058 nor xorg-server this time, the hal port needs to be rebuilt
2062 The misnamed kthread_create() and friends have been renamed
2063 to kproc_create() etc. Many of the callers already
2064 used kproc_start()..
2065 I will return kthread_create() and friends in a while
2066 with implementations that actually create threads, not procs.
2067 Renaming corresponds with version 800002.
2076 Avoid using make -j when upgrading. While generally safe, there are
2077 sometimes problems using -j to upgrade. If your upgrade fails with
2078 -j, please try again without -j. From time to time in the past there
2079 have been problems using -j with buildworld and/or installworld. This
2080 is especially true when upgrading between "distant" versions (eg one
2081 that cross a major release boundary or several minor releases, or when
2082 several months have passed on the -current branch).
2084 Sometimes, obscure build problems are the result of environment
2085 poisoning. This can happen because the make utility reads its
2086 environment when searching for values for global variables. To run
2087 your build attempts in an "environmental clean room", prefix all make
2088 commands with 'env -i '. See the env(1) manual page for more details.
2090 When upgrading from one major version to another it is generally best
2091 to upgrade to the latest code in the currently installed branch first,
2092 then do an upgrade to the new branch. This is the best-tested upgrade
2093 path, and has the highest probability of being successful. Please try
2094 this approach before reporting problems with a major version upgrade.
2096 When upgrading a live system, having a root shell around before
2097 installing anything can help undo problems. Not having a root shell
2098 around can lead to problems if pam has changed too much from your
2099 starting point to allow continued authentication after the upgrade.
2103 When upgrading the boot ZFS pool to a new version, always follow
2106 1.) recompile and reinstall the ZFS boot loader and boot block
2107 (this is part of "make buildworld" and "make installworld")
2109 2.) update the ZFS boot block on your boot drive
2111 The following example updates the ZFS boot block on the first
2112 partition (freebsd-boot) of a GPT partitioned drive ad0:
2113 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2115 Non-boot pools do not need these updates.
2119 If you are updating from a prior version of FreeBSD (even one just
2120 a few days old), you should follow this procedure. It is the most
2121 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2123 make kernel-toolchain
2124 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2125 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2127 To test a kernel once
2128 ---------------------
2129 If you just want to boot a kernel once (because you are not sure
2130 if it works, or if you want to boot a known bad kernel to provide
2131 debugging information) run
2132 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2133 nextboot -k testkernel
2135 To just build a kernel when you know that it won't mess you up
2136 --------------------------------------------------------------
2137 This assumes you are already running a CURRENT system. Replace
2138 ${arch} with the architecture of your machine (e.g. "i386",
2139 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2141 cd src/sys/${arch}/conf
2142 config KERNEL_NAME_HERE
2143 cd ../compile/KERNEL_NAME_HERE
2148 If this fails, go to the "To build a kernel" section.
2150 To rebuild everything and install it on the current system.
2151 -----------------------------------------------------------
2152 # Note: sometimes if you are running current you gotta do more than
2153 # is listed here if you are upgrading from a really old current.
2155 <make sure you have good level 0 dumps>
2157 make kernel KERNCONF=YOUR_KERNEL_HERE
2159 <reboot in single user> [3]
2166 To cross-install current onto a separate partition
2167 --------------------------------------------------
2168 # In this approach we use a separate partition to hold
2169 # current's root, 'usr', and 'var' directories. A partition
2170 # holding "/", "/usr" and "/var" should be about 2GB in
2173 <make sure you have good level 0 dumps>
2176 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2177 <maybe newfs current's root partition>
2178 <mount current's root partition on directory ${CURRENT_ROOT}>
2179 make installworld DESTDIR=${CURRENT_ROOT}
2180 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2181 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2182 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2183 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2184 <reboot into current>
2185 <do a "native" rebuild/install as described in the previous section>
2186 <maybe install compatibility libraries from ports/misc/compat*>
2190 To upgrade in-place from stable to current
2191 ----------------------------------------------
2192 <make sure you have good level 0 dumps>
2194 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2196 <reboot in single user> [3]
2203 Make sure that you've read the UPDATING file to understand the
2204 tweaks to various things you need. At this point in the life
2205 cycle of current, things change often and you are on your own
2206 to cope. The defaults can also change, so please read ALL of
2207 the UPDATING entries.
2209 Also, if you are tracking -current, you must be subscribed to
2210 freebsd-current@freebsd.org. Make sure that before you update
2211 your sources that you have read and understood all the recent
2212 messages there. If in doubt, please track -stable which has
2213 much fewer pitfalls.
2215 [1] If you have third party modules, such as vmware, you
2216 should disable them at this point so they don't crash your
2219 [3] From the bootblocks, boot -s, and then do
2224 adjkerntz -i # if CMOS is wall time
2225 Also, when doing a major release upgrade, it is required that
2226 you boot into single user mode to do the installworld.
2228 [4] Note: This step is non-optional. Failure to do this step
2229 can result in a significant reduction in the functionality of the
2230 system. Attempting to do it by hand is not recommended and those
2231 that pursue this avenue should read this file carefully, as well
2232 as the archives of freebsd-current and freebsd-hackers mailing lists
2233 for potential gotchas. The -U option is also useful to consider.
2234 See mergemaster(8) for more information.
2236 [5] Usually this step is a noop. However, from time to time
2237 you may need to do this if you get unknown user in the following
2238 step. It never hurts to do it all the time. You may need to
2239 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2240 install) after the buildworld before this step if you last updated
2241 from current before 20130425 or from -stable before 20130430.
2243 [6] This only deletes old files and directories. Old libraries
2244 can be deleted by "make delete-old-libs", but you have to make
2245 sure that no program is using those libraries anymore.
2247 [8] In order to have a kernel that can run the 4.x binaries needed to
2248 do an installworld, you must include the COMPAT_FREEBSD4 option in
2249 your kernel. Failure to do so may leave you with a system that is
2250 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2251 required to run the 5.x binaries on more recent kernels. And so on
2252 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2254 Make sure that you merge any new devices from GENERIC since the
2255 last time you updated your kernel config file.
2257 [9] When checking out sources, you must include the -P flag to have
2258 cvs prune empty directories.
2260 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2261 "?=" instead of the "=" assignment operator, so that buildworld can
2262 override the CPUTYPE if it needs to.
2264 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2265 not on the command line, or in /etc/make.conf. buildworld will
2266 warn if it is improperly defined.
2269 This file contains a list, in reverse chronological order, of major
2270 breakages in tracking -current. It is not guaranteed to be a complete
2271 list of such breakages, and only contains entries since October 10, 2007.
2272 If you need to see UPDATING entries from before that date, you will need
2273 to fetch an UPDATING file from an older FreeBSD release.
2275 Copyright information:
2277 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2279 Redistribution, publication, translation and use, with or without
2280 modification, in full or in part, in any form or format of this
2281 document are permitted without further permission from the author.
2283 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2284 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2285 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2286 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2287 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2288 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2289 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2290 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2291 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2292 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2293 POSSIBILITY OF SUCH DAMAGE.
2295 Contact Warner Losh if you have any questions about your use of