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 20150929: p21 FreeBSD-SA-15:24.rpcbind
21 Fix rpcbind(8) remote denial of service. [SA-15:24]
23 20150916: p20 FreeBSD-EN-15:18.pkg
25 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
27 20150825: p19 FreeBSD-SA-15:21.amd64
28 FreeBSD-SA-15:22.openssh
29 FreeBSD-EN-15:14.ixgbe
32 Fix local privilege escalation in IRET handler. [SA-15:21]
34 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
36 Disabled ixgbe(4) flow-director support. [EN-15:14]
38 Fix insufficient check of unsupported pkg(7) signature methods.
41 20150818: p18 FreeBSD-SA-15:20.expat
43 Fix multiple integer overflows in expat (libbsdxml) XML parser.
46 20150805: p17 FreeBSD-SA-15:18.bsdpatch
47 FreeBSD-SA-15:19.routed
49 Fix patch(1) shell injection vulnerability via ed(1).
52 Fix routed remote denial of service vulnerability. [SA-15:19]
54 20150728: p16 FreeBSD-SA-15:14.bsdpatch
56 FreeBSD-SA-15:16.openssh
58 Fix patch(1) shell injection vulnerability. [SA-15:14]
60 Fix resource exhaustion in TCP reassembly. [SA-15:15]
62 Fix OpenSSH multiple vulnerabilities. [SA-15:16]
64 20150721: p15 FreeBSD-SA-15:13.tcp
66 Fix resource exhaustion due to sessions stuck in LAST_ACK state.
69 20150630: p14 FreeBSD-EN-15:08.sendmail [revised]
70 FreeBSD-EN-15:09.xlocale
71 FreeBSD-EN-15:10.iconv
73 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
75 Fix inconsistency between locale and rune locale states.
78 Improved iconv(3) UTF-7 support. [EN-15:10]
80 20150618: p13 FreeBSD-EN-15:08.sendmail
81 Improvements to sendmail TLS/DH interoperability. [EN-15:08]
83 20150612: p12 FreeBSD-SA-15:10.openssl
84 Fix multiple vulnerabilities in OpenSSL. [SA-15:10]
86 20150609: p11 FreeBSD-EN-15:06.file
89 Updated base system file(1) to 5.22 to address multiple denial
90 of service issues. [EN-15:06]
92 Improved reliability of ZFS when TRIM/UNMAP and/or L2ARC is used.
95 20150513: p10 FreeBSD-EN-15:04.freebsd-update
98 Fix bug with freebsd-update(8) that does not ensure the previous
99 upgrade was completed. [EN-15:04]
101 Fix deadlock on reboot with UFS tuned with SU+J. [EN-15:05]
103 20150407: p9 FreeBSD-SA-15:04.igmp [revised]
105 FreeBSD-SA-15:08.bsdinstall
106 FreeBSD-SA-15:09.ipv6
108 Improved patch for SA-15:04.igmp.
110 Fix multiple vulnerabilities of ntp. [SA-15:07]
112 Fix bsdinstall(8) insecure default GELI keyfile permissions. [SA-15:08]
114 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
117 Fix patch for SA-15:06.openssl.
119 20150319: p7 FreeBSD-SA-15:06.openssl
120 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
122 20150225: p6 FreeBSD-SA-15:04.igmp
124 FreeBSD-EN-15:02.openssl
125 FreeBSD-EN-15:03.freebsd-update
127 Fix integer overflow in IGMP protocol. [SA-15:04]
129 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
131 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
133 Fix freebsd-update libraries update ordering issue. [EN-15:03]
135 20150127: p5 FreeBSD-SA-15:02.kmem
136 FreeBSD-SA-15:03.sctp
138 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
139 vulnerability. [SA-15:02]
141 Fix SCTP stream reset vulnerability. [SA-15:03]
143 20150114: p4 FreeBSD-SA-15:01.openssl
144 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
146 20141223: p3 FreeBSD-SA-14:31.ntp
147 FreeBSD-EN-14:13.freebsd-update
149 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
150 Fix directory deletion issue in freebsd-update. [EN-14:13]
152 20141217: p2 FreeBSD-SA-14:30.unbound
153 Fix unbound remote denial of service vulnerability.
155 20141210: p1 FreeBSD-SA-14:27.stdio
156 FreeBSD-SA-14:28.file
158 Fix buffer overflow in stdio. [SA-14:27]
160 Fix multiple vulnerabilities in file(1) and libmagic(3).
164 The ofwfb driver, used to provide a graphics console on PowerPC when
165 using vt(4), no longer allows mmap() of all of physical memory. This
166 will prevent Xorg on PowerPC with some ATI graphics cards from
167 initializing properly unless x11-servers/xorg-server is updated to
171 The libatf-c and libatf-c++ major versions were downgraded to 0 and
172 1 respectively to match the upstream numbers. They were out of
173 sync because, when they were originally added to FreeBSD, the
174 upstream versions were not respected. These libraries are private
175 and not yet built by default, so renumbering them should be a
176 non-issue. However, unclean source trees will yield broken test
177 programs once the operator executes "make delete-old-libs" after a
180 Additionally, the atf-sh binary was made private by moving it into
181 /usr/libexec/. Already-built shell test programs will keep the
182 path to the old binary so they will break after "make delete-old"
185 If you are using WITH_TESTS=yes (not the default), wipe the object
186 tree and rebuild from scratch to prevent spurious test failures.
187 This is only needed once: the misnumbered libraries and misplaced
188 binaries have been added to OptionalObsoleteFiles.inc so they will
189 be removed during a clean upgrade.
192 The ixgbe tunables now match their sysctl counterparts, for example:
193 hw.ixgbe.enable_aim => hw.ix.enable_aim
194 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
197 The NFSv4.1 server committed by r269398 changes the internal
198 function call interfaces used between the NFS and krpc modules.
199 As such, __FreeBSD_version was bumped.
202 The default unbound configuration has been modified to address
203 issues with reverse lookups on networks that use private
204 address ranges. If you use the local_unbound service, run
205 "service local_unbound setup" as root to regenerate your
206 configuration, then "service local_unbound reload" to load the
210 It is no longer necessary to include the dwarf version in your DEBUG
211 options in your kernel config file. The bug that required it to be
212 placed in the config file has bene fixed. DEBUG should now just
213 contain -g. The build system will automatically update things
214 to do the right thing.
217 Several ABI breaking changes were merged to CTL and new iSCSI code.
218 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
219 iscsictl need to be rebuilt to work with a new kernel.
222 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
223 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
224 which differs from the behaviour controlled by this knob.)
227 On i386 and amd64 systems, the onifconsole flag is now set by default
228 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
229 as a login TTY if it is set in the bootloader as an active kernel
230 console. No changes in behavior should result otherwise. To revert to
231 the previous behavior, set ttyu0 to "off" in /etc/ttys.
234 Clang and llvm have been upgraded to 3.4.1 release.
237 Clang and llvm have been upgraded to 3.4 release.
240 If a Makefile in a tests/ directory was auto-generating a Kyuafile
241 instead of providing an explicit one, this would prevent such
242 Makefile from providing its own Kyuafile in the future during
243 NO_CLEAN builds. This has been fixed in the Makefiles but manual
244 intervention is needed to clean an objdir if you use NO_CLEAN:
245 # find /usr/obj -name Kyuafile | xargs rm -f
248 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
249 capability mode support. Please note that enabling the feature in
250 kernel is still highly recommended.
253 OpenSSH is now built with sandbox support, and will use sandbox as
254 the default privilege separation method. This requires Capsicum
255 capability mode support in kernel.
258 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
259 been deprecated and will not be part of FreeBSD 11.0 and later
260 releases. If you use this driver, please consider switching to
261 the nfe(4) driver instead.
267 The behavior of gss_pseudo_random() for the krb5 mechanism
268 has changed, for applications requesting a longer random string
269 than produced by the underlying enctype's pseudo-random() function.
270 In particular, the random string produced from a session key of
271 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
272 be different at the 17th octet and later, after this change.
273 The counter used in the PRF+ construction is now encoded as a
274 big-endian integer in accordance with RFC 4402.
275 __FreeBSD_version is bumped to 1000701.
278 The WITHOUT_ATF build knob has been removed and its functionality
279 has been subsumed into the more generic WITHOUT_TESTS. If you were
280 using the former to disable the build of the ATF libraries, you
281 should change your settings to use the latter.
284 The default version of mtree is nmtree which is obtained from
285 NetBSD. The output is generally the same, but may vary
286 slightly. If you found you need identical output adding
287 "-F freebsd9" to the command line should do the trick. For the
288 time being, the old mtree is available as fmtree.
291 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
292 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
293 1.1.4_8 and verify bsdyml not linked in, before running "make
295 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
297 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
300 The rc.d/jail script has been updated to support jail(8)
301 configuration file. The "jail_<jname>_*" rc.conf(5) variables
302 for per-jail configuration are automatically converted to
303 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
304 This is transparently backward compatible. See below about some
305 incompatibilities and rc.conf(5) manual page for more details.
307 These variables are now deprecated in favor of jail(8) configuration
308 file. One can use "rc.d/jail config <jname>" command to generate
309 a jail(8) configuration file in /var/run/jail.<jname>.conf without
310 running the jail(8) utility. The default pathname of the
311 configuration file is /etc/jail.conf and can be specified by
312 using $jail_conf or $jail_<jname>_conf variables.
314 Please note that jail_devfs_ruleset accepts an integer at
315 this moment. Please consider to rewrite the ruleset name
319 BIND has been removed from the base system. If all you need
320 is a local resolver, simply enable and start the local_unbound
321 service instead. Otherwise, several versions of BIND are
322 available in the ports tree. The dns/bind99 port is one example.
324 With this change, nslookup(1) and dig(1) are no longer in the base
325 system. Users should instead use host(1) and drill(1) which are
326 in the base system. Alternatively, nslookup and dig can
327 be obtained by installing the dns/bind-tools port.
330 With the addition of unbound(8), a new unbound user is now
331 required during installworld. "mergemaster -p" can be used to
332 add the user prior to installworld, as documented in the handbook.
335 OpenSSH is now built with DNSSEC support, and will by default
336 silently trust signed SSHFP records. This can be controlled with
337 the VerifyHostKeyDNS client configuration setting. DNSSEC support
338 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
341 The GNU Compiler Collection and C++ standard library (libstdc++)
342 are no longer built by default on platforms where clang is the system
343 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
347 The PROCDESC kernel option is now part of the GENERIC kernel
348 configuration and is required for the rwhod(8) to work.
349 If you are using custom kernel configuration, you should include
353 The API and ABI related to the Capsicum framework was modified
354 in backward incompatible way. The userland libraries and programs
355 have to be recompiled to work with the new kernel. This includes the
356 following libraries and programs, but the whole buildworld is
357 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
358 kdump, procstat, rwho, rwhod, uniq.
361 AES-NI intrinsic support has been added to gcc. The AES-NI module
362 has been updated to use this support. A new gcc is required to build
363 the aesni module on both i386 and amd64.
366 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
367 Thus "device padlock_rng" and "device rdrand_rng" should be
368 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
371 WITH_ICONV has been split into two feature sets. WITH_ICONV now
372 enables just the iconv* functionality and is now on by default.
373 WITH_LIBICONV_COMPAT enables the libiconv api and link time
374 compatability. Set WITHOUT_ICONV to build the old way.
375 If you have been using WITH_ICONV before, you will very likely
376 need to turn on WITH_LIBICONV_COMPAT.
379 INVARIANTS option now enables DEBUG for code with OpenSolaris and
380 Illumos origin, including ZFS. If you have INVARIANTS in your
381 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
383 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
384 locks if WITNESS option was set. Because that generated a lot of
385 witness(9) reports and all of them were believed to be false
386 positives, this is no longer done. New option OPENSOLARIS_WITNESS
387 can be used to achieve the previous behavior.
390 Timer values in IPv6 data structures now use time_uptime instead
391 of time_second. Although this is not a user-visible functional
392 change, userland utilities which directly use them---ndp(8),
393 rtadvd(8), and rtsold(8) in the base system---need to be updated
397 find -delete can now delete the pathnames given as arguments,
398 instead of only files found below them or if the pathname did
399 not contain any slashes. Formerly, the following error message
402 find: -delete: <path>: relative path potentially not safe
404 Deleting the pathnames given as arguments can be prevented
405 without error messages using -mindepth 1 or by changing
406 directory and passing "." as argument to find. This works in the
407 old as well as the new version of find.
410 Behavior of devfs rules path matching has been changed.
411 Pattern is now always matched against fully qualified devfs
412 path and slash characters must be explicitly matched by
413 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
414 subdirectories must be reviewed.
417 The default ARM ABI has changed to the ARM EABI. The old ABI is
418 incompatible with the ARM EABI and all programs and modules will
419 need to be rebuilt to work with a new kernel.
421 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
423 NOTE: Support for the old ABI will be removed in the future and
424 users are advised to upgrade.
427 pkg_install has been disconnected from the build if you really need it
428 you should add WITH_PKGTOOLS in your src.conf(5).
431 Most of network statistics structures were changed to be able
432 keep 64-bits counters. Thus all tools, that work with networking
433 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
436 Fix targets that run multiple make's to use && rather than ;
437 so that subsequent steps depend on success of previous.
439 NOTE: if building 'universe' with -j* on stable/8 or stable/9
440 it would be better to start the build using bmake, to avoid
441 overloading the machine.
444 Fix a bug that allowed a tracing process (e.g. gdb) to write
445 to a memory-mapped file in the traced process's address space
446 even if neither the traced process nor the tracing process had
447 write access to that file.
450 CVS has been removed from the base system. An exact copy
451 of the code is available from the devel/cvs port.
454 Some people report the following error after the switch to bmake:
456 make: illegal option -- J
457 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
459 *** [buildworld] Error code 2
461 this likely due to an old instance of make in
462 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
463 which src/Makefile will use that blindly, if it exists, so if
464 you see the above error:
466 rm -rf `make -V MAKEPATH`
471 Use bmake by default.
472 Whereas before one could choose to build with bmake via
473 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
474 make. The goal is to remove these knobs for 10-RELEASE.
476 It is worth noting that bmake (like gmake) treats the command
477 line as the unit of failure, rather than statements within the
478 command line. Thus '(cd some/where && dosomething)' is safer
479 than 'cd some/where; dosomething'. The '()' allows consistent
480 behavior in parallel build.
483 Fix a bug that allows NFS clients to issue READDIR on files.
486 The WITHOUT_IDEA option has been removed because
487 the IDEA patent expired.
490 The sysctl which controls TRIM support under ZFS has been renamed
491 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
495 The mergemaster command now uses the default MAKEOBJDIRPREFIX
496 rather than creating it's own in the temporary directory in
497 order allow access to bootstrapped versions of tools such as
498 install and mtree. When upgrading from version of FreeBSD where
499 the install command does not support -l, you will need to
500 install a new mergemaster command if mergemaster -p is required.
501 This can be accomplished with the command (cd src/usr.sbin/mergemaster
505 Legacy ATA stack, disabled and replaced by new CAM-based one since
506 FreeBSD 9.0, completely removed from the sources. Kernel modules
507 atadisk and atapi*, user-level tools atacontrol and burncd are
508 removed. Kernel option `options ATA_CAM` is now permanently enabled
512 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
513 and socketpair(2). Software, in particular Kerberos, may
514 automatically detect and use these during building. The resulting
515 binaries will not work on older kernels.
518 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
519 information, see the respective 20130304 entry).
522 Recent commits to callout(9) changed the size of struct callout,
523 so the KBI is probably heavily disturbed. Also, some functions
524 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
525 by macros. Every kernel module using it won't load, so rebuild
528 The ctl device has been re-enabled in GENERIC for i386 and amd64,
529 but does not initialize by default (because of the new CTL_DISABLE
530 option) to save memory. To re-enable it, remove the CTL_DISABLE
531 option from the kernel config file or set kern.cam.ctl.disable=0
532 in /boot/loader.conf.
535 The ctl device has been disabled in GENERIC for i386 and amd64.
536 This was done due to the extra memory being allocated at system
537 initialisation time by the ctl driver which was only used if
538 a CAM target device was created. This makes a FreeBSD system
539 unusable on 128MB or less of RAM.
542 A new compression method (lz4) has been merged to -HEAD. Please
543 refer to zpool-features(7) for more information.
545 Please refer to the "ZFS notes" section of this file for information
546 on upgrading boot ZFS pools.
549 A BSD-licensed patch(1) variant has been added and is installed
550 as bsdpatch, being the GNU version the default patch.
551 To inverse the logic and use the BSD-licensed one as default,
552 while having the GNU version installed as gnupatch, rebuild
553 and install world with the WITH_BSD_PATCH knob set.
556 Due to the use of the new -l option to install(1) during build
557 and install, you must take care not to directly set the INSTALL
558 make variable in your /etc/make.conf, /etc/src.conf, or on the
559 command line. If you wish to use the -C flag for all installs
560 you may be able to add INSTALL+=-C to /etc/make.conf or
564 The install(1) option -M has changed meaning and now takes an
565 argument that is a file or path to append logs to. In the
566 unlikely event that -M was the last option on the command line
567 and the command line contained at least two files and a target
568 directory the first file will have logs appended to it. The -M
569 option served little practical purpose in the last decade so its
570 use is expected to be extremely rare.
573 After switching to Clang as the default compiler some users of ZFS
574 on i386 systems started to experience stack overflow kernel panics.
575 Please consider using 'options KSTACK_PAGES=4' in such configurations.
578 GEOM_LABEL now mangles label names read from file system metadata.
579 Mangling affect labels containing spaces, non-printable characters,
580 '%' or '"'. Device names in /etc/fstab and other places may need to
584 By default, only the 10 most recent kernel dumps will be saved. To
585 restore the previous behaviour (no limit on the number of kernel dumps
586 stored in the dump directory) add the following line to /etc/rc.conf:
591 With the addition of auditdistd(8), a new auditdistd user is now
592 required during installworld. "mergemaster -p" can be used to
593 add the user prior to installworld, as documented in the handbook.
596 The sin6_scope_id member variable in struct sockaddr_in6 is now
597 filled by the kernel before passing the structure to the userland via
598 sysctl or routing socket. This means the KAME-specific embedded scope
599 id in sin6_addr.s6_addr[2] is always cleared in userland application.
600 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
601 __FreeBSD_version is bumped to 1000025.
604 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
605 This means that the world and kernel will be compiled with clang
606 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
607 and /usr/bin/cpp. To disable this behavior and revert to building
608 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
609 of current may need to bootstrap WITHOUT_CLANG first if the clang
610 build fails (its compatibility window doesn't extend to the 9 stable
614 The IPFIREWALL_FORWARD kernel option has been removed. Its
615 functionality now turned on by default.
618 The ZERO_COPY_SOCKET kernel option has been removed and
619 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
620 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
621 mechanism which is not safe and may result in kernel crashes.
622 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
623 driver supports disposeable external page sized mbuf storage.
624 Proper replacements for both zero-copy mechanisms are under
625 consideration and will eventually lead to complete removal
626 of the two kernel options.
629 The IPv4 network stack has been converted to network byte
630 order. The following modules need to be recompiled together
631 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
632 pf(4), ipfw(4), ng_ipfw(4), stf(4).
635 Support for non-MPSAFE filesystems was removed from VFS. The
636 VFS_VERSION was bumped, all filesystem modules shall be
640 All the non-MPSAFE filesystems have been disconnected from
641 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
642 portalfs, smbfs, xfs.
645 The interface cloning API and ABI has changed. The following
646 modules need to be recompiled together with kernel:
647 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
648 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
649 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
652 The sdhci driver was split in two parts: sdhci (generic SD Host
653 Controller logic) and sdhci_pci (actual hardware driver).
654 No kernel config modifications are required, but if you
655 load sdhc as a module you must switch to sdhci_pci instead.
658 Import the FUSE kernel and userland support into base system.
661 The GNU sort(1) program has been removed since the BSD-licensed
662 sort(1) has been the default for quite some time and no serious
663 problems have been reported. The corresponding WITH_GNU_SORT
667 The pfil(9) API/ABI for AF_INET family has been changed. Packet
668 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
672 The net80211(4) ABI has been changed to allow for improved driver
673 PS-POLL and power-save support. All wireless drivers need to be
674 recompiled to work with the new kernel.
677 The random(4) support for the VIA hardware random number
678 generator (`PADLOCK') is no longer enabled unconditionally.
679 Add the padlock_rng device in the custom kernel config if
680 needed. The GENERIC kernels on i386 and amd64 do include the
681 device, so the change only affects the custom kernel
685 The pf(4) packet filter ABI has been changed. pfctl(8) and
686 snmp_pf module need to be recompiled to work with new kernel.
689 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
690 to -HEAD. Pools that have empty_bpobj in active state can not be
691 imported read-write with ZFS implementations that do not support
692 this feature. For more information read the zpool-features(5)
696 The sparc64 ZFS loader has been changed to no longer try to auto-
697 detect ZFS providers based on diskN aliases but now requires these
698 to be explicitly listed in the OFW boot-device environment variable.
701 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
702 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
703 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
706 The following sysctls and tunables have been renamed for consistency
707 with other variables:
708 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
709 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
712 The sort utility has been replaced with BSD sort. For now, GNU sort
713 is also available as "gnusort" or the default can be set back to
714 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
715 installed as "bsdsort".
718 A new version of ZFS (pool version 5000) has been merged to -HEAD.
719 Starting with this version the old system of ZFS pool versioning
720 is superseded by "feature flags". This concept enables forward
721 compatibility against certain future changes in functionality of ZFS
722 pools. The first read-only compatible "feature flag" for ZFS pools
723 is named "com.delphix:async_destroy". For more information
724 read the new zpool-features(5) manual page.
725 Please refer to the "ZFS notes" section of this file for information
726 on upgrading boot ZFS pools.
729 The malloc(3) implementation embedded in libc now uses sources imported
730 as contrib/jemalloc. The most disruptive API change is to
731 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
732 delete it prior to installworld, and optionally re-create it using the
733 new format after rebooting. See malloc.conf(5) for details
734 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
738 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
739 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
740 now spelled mips. This is to aid compatibility with third-party
741 software that expects this naming scheme in uname(3). Little-endian
742 settings are unchanged. If you are updating a big-endian mips64 machine
743 from before this change, you may need to set MACHINE_ARCH=mips64 in
744 your environment before the new build system will recognize your machine.
747 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
751 Now unix domain sockets behave "as expected" on nullfs(5). Previously
752 nullfs(5) did not pass through all behaviours to the underlying layer,
753 as a result if we bound to a socket on the lower layer we could connect
754 only to the lower path; if we bound to the upper layer we could connect
755 only to the upper path. The new behavior is one can connect to both the
756 lower and the upper paths regardless what layer path one binds to.
759 The getifaddrs upgrade path broken with 20111215 has been restored.
760 If you have upgraded in between 20111215 and 20120209 you need to
761 recompile libc again with your kernel. You still need to recompile
762 world to be able to configure CARP but this restriction already
766 The set_rcvar() function has been removed from /etc/rc.subr. All
767 base and ports rc.d scripts have been updated, so if you have a
768 port installed with a script in /usr/local/etc/rc.d you can either
769 hand-edit the rcvar= line, or reinstall the port.
771 An easy way to handle the mass-update of /etc/rc.d:
772 rm /etc/rc.d/* && mergemaster -i
775 panic(9) now stops other CPUs in the SMP systems, disables interrupts
776 on the current CPU and prevents other threads from running.
777 This behavior can be reverted using the kern.stop_scheduler_on_panic
779 The new behavior can be incompatible with kern.sync_on_panic.
782 The carp(4) facility has been changed significantly. Configuration
783 of the CARP protocol via ifconfig(8) has changed, as well as format
784 of CARP events submitted to devd(8) has changed. See manual pages
785 for more information. The arpbalance feature of carp(4) is currently
786 not supported anymore.
788 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
789 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
790 need to be recompiled.
793 The acpi_wmi(4) status device /dev/wmistat has been renamed to
797 The option VFS_ALLOW_NONMPSAFE option has been added in order to
798 explicitely support non-MPSAFE filesystems.
799 It is on by default for all supported platform at this present
803 The broken amd(4) driver has been replaced with esp(4) in the amd64,
804 i386 and pc98 GENERIC kernel configuration files.
807 sysinstall has been removed
810 The stable/9 branch created in subversion. This corresponds to the
811 RELENG_9 branch in CVS.
814 This commit modifies vfs_register() so that it uses a hash
815 calculation to set vfc_typenum, which is enabled by default.
816 The first time a system is booted after this change, the
817 vfc_typenum values will change for all file systems. The
818 main effect of this is a change to the NFS server file handles
819 for file systems that use vfc_typenum in their fsid, such as ZFS.
820 It will, however, prevent vfc_typenum from changing when file
821 systems are loaded in a different order for subsequent reboots.
822 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
823 until you are ready to remount all NFS clients after a reboot.
826 Bump the shared library version numbers for libraries that
827 do not use symbol versioning, have changed the ABI compared
828 to stable/8 and which shared library version was not bumped.
829 Done as part of 9.0-RELEASE cycle.
832 During the merge of Capsicum features, the fget(9) KPI was modified.
833 This may require the rebuilding of out-of-tree device drivers --
834 issues have been reported specifically with the nVidia device driver.
835 __FreeBSD_version is bumped to 900041.
837 Also, there is a period between 20110811 and 20110814 where the
838 special devices /dev/{stdin,stdout,stderr} did not work correctly.
839 Building world from a kernel during that window may not work.
842 The packet filter (pf) code has been updated to OpenBSD 4.5.
843 You need to update userland tools to be in sync with kernel.
844 This update breaks backward compatibility with earlier pfsync(4)
845 versions. Care must be taken when updating redundant firewall setups.
848 The following sysctls and tunables are retired on x86 platforms:
850 machdep.hlt_logical_cpus
851 The following sysctl is retired:
852 machdep.hyperthreading_allowed
853 The sysctls were supposed to provide a way to dynamically offline and
854 online selected CPUs on x86 platforms, but the implementation has not
855 been reliable especially with SCHED_ULE scheduler.
856 machdep.hyperthreading_allowed tunable is still available to ignore
857 hyperthreading CPUs at OS level.
858 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
859 where X is an APIC ID of a CPU. Be advised, though, that disabling
860 CPUs in non-uniform fashion will result in non-uniform topology and
861 may lead to sub-optimal system performance with SCHED_ULE, which is
865 cpumask_t type is retired and cpuset_t is used in order to describe
869 Changes to ifconfig(8) for dynamic address family detection mandate
870 that you are running a kernel of 20110525 or later. Make sure to
871 follow the update procedure to boot a new kernel before installing
875 Support for sun4v architecture is officially dropped
878 Several KPI breaking changes have been committed to the mii(4) layer,
879 the PHY drivers and consequently some Ethernet drivers using mii(4).
880 This means that miibus.ko and the modules of the affected Ethernet
881 drivers need to be recompiled.
883 Note to kernel developers: Given that the OUI bit reversion problem
884 was fixed as part of these changes all mii(4) commits related to OUIs,
885 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
886 handling, no longer can be merged verbatim to stable/8 and previous
890 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
891 into their kernel configurations along with 'device pci'.
894 The default NFS client is now the new NFS client, so fstype "newnfs"
895 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
896 Although mounts via fstype "nfs" will usually work without userland
897 changes, it is recommended that the mount(8) and mount_nfs(8)
898 commands be rebuilt from sources and that a link to mount_nfs called
899 mount_oldnfs be created. The new client is compiled into the
900 kernel with "options NFSCL" and this is needed for diskless root
901 file systems. The GENERIC kernel configs have been changed to use
902 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
903 To use the regular/old client, you can "mount -t oldnfs ...". For
904 a diskless root file system, you must also include a line like:
906 vfs.root.mountfrom="oldnfs:"
908 in the boot/loader.conf on the root fs on the NFS server to make
909 a diskless root fs use the old client.
912 The GENERIC kernels for all architectures now default to the new
913 CAM-based ATA stack. It means that all legacy ATA drivers were
914 removed and replaced by respective CAM drivers. If you are using
915 ATA device names in /etc/fstab or other places, make sure to update
916 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
917 where 'Y's are the sequential numbers starting from zero for each type
918 in order of detection, unless configured otherwise with tunables,
919 see cam(4)). There will be symbolic links created in /dev/ to map
920 old adX devices to the respective adaY. They should provide basic
921 compatibility for file systems mounting in most cases, but they do
922 not support old user-level APIs and do not have respective providers
923 in GEOM. Consider using updated management tools with new device names.
925 It is possible to load devices ahci, ata, siis and mvs as modules,
926 but option ATA_CAM should remain in kernel configuration to make ata
927 module work as CAM driver supporting legacy ATA controllers. Device ata
928 still can be used in modular fashion (atacore + ...). Modules atadisk
929 and atapi* are not used and won't affect operation in ATA_CAM mode.
930 Note that to use CAM-based ATA kernel should include CAM devices
931 scbus, pass, da (or explicitly ada), cd and optionally others. All of
932 them are parts of the cam module.
934 ataraid(4) functionality is now supported by the RAID GEOM class.
935 To use it you can load geom_raid kernel module and use graid(8) tool
936 for management. Instead of /dev/arX device names, use /dev/raid/rX.
938 No kernel config options or code have been removed, so if a problem
939 arises, please report it and optionally revert to the old ATA stack.
940 In order to do it you can remove from the kernel config:
945 , and instead add back:
946 device atadisk # ATA disk drives
947 device ataraid # ATA RAID drives
948 device atapicd # ATAPI CDROM drives
949 device atapifd # ATAPI floppy drives
950 device atapist # ATAPI tape drives
953 The default NFS server has been changed to the new server, which
954 was referred to as the experimental server. If you need to switch
955 back to the old NFS server, you must now put the "-o" option on
956 both the mountd and nfsd commands. This can be done using the
957 mountd_flags and nfs_server_flags rc.conf variables until an
958 update to the rc scripts is committed, which is coming soon.
961 The GNU Objective-C runtime library (libobjc), and other Objective-C
962 related components have been removed from the base system. If you
963 require an Objective-C library, please use one of the available ports.
966 ath(4) has been split into bus- and device- modules. if_ath contains
967 the HAL, the TX rate control and the network device code. if_ath_pci
968 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
969 contains the AHB glue. Users need to load both if_ath_pci and if_ath
970 in order to use ath on everything else.
972 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
973 need to load if_ath and if_ath_pci for ath(4) operation.
976 As part of the replacement of sysinstall, the process of building
977 release media has changed significantly. For details, please re-read
978 release(7), which has been updated to reflect the new build process.
981 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
982 is the last available version under GPLv2. It brings a number of new
983 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
984 4.1 and SSE 4.2), better support for powerpc64, a number of new
985 directives, and lots of other small improvements. See the ChangeLog
986 file in contrib/binutils for the full details.
989 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
990 compliant, and will now use half of hash for authentication.
991 This will break interoperability with all stacks (including all
992 actual FreeBSD versions) who implement
993 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
995 The only workaround with such peers is to use another HMAC
996 algorithm for IPsec ("phase 2") authentication.
999 Remove the uio_yield prototype and symbol. This function has
1000 been misnamed since it was introduced and should not be
1001 globally exposed with this name. The equivalent functionality
1002 is now available using kern_yield(curthread->td_user_pri).
1003 The function remains undocumented.
1006 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1007 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1008 for scalar sysctls is defined but disabled. Code that needs
1009 UQUAD to pass the type checking that must compile on older
1010 systems where the define is not present can check against
1011 __FreeBSD_version >= 900030.
1013 The system dialog(1) has been replaced with a new version previously
1014 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1015 with the previous version, but the libdialog associated with it has
1016 a largely incompatible API. As such, the original version of libdialog
1017 will be kept temporarily as libodialog, until its base system consumers
1018 are replaced or updated. Bump __FreeBSD_version to 900030.
1021 If you are trying to run make universe on a -stable system, and you get
1022 the following warning:
1023 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1024 unknown. config(8) likely too old."
1025 or something similar to it, then you must upgrade your -stable system
1026 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1027 stable/8) or build the config from the latest stable/8 branch and
1028 install it on your system.
1030 Prior to this date, building a current universe on 8-stable system from
1031 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1032 error in the first kernel build phase. A new config on those old
1033 systems will fix that problem for older versions of -current.
1036 The TCP stack has been modified to allow Khelp modules to interact with
1037 it via helper hook points and store per-connection data in the TCP
1038 control block. Bump __FreeBSD_version to 900029. User space tools that
1039 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1043 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1044 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1045 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1046 to take advantage of it instead of using custom implementations. This
1047 means that these drivers now no longer unconditionally advertise
1048 support for flow control but only do so if flow control is a selected
1049 media option. This was implemented in the generic support that way in
1050 order to allow flow control to be switched on and off via ifconfig(8)
1051 with the PHY specific default to typically off in order to protect
1052 from unwanted effects. Consequently, if you used flow control with
1053 one of the above mentioned drivers you now need to explicitly enable
1054 it, for example via:
1055 ifconfig bge0 media auto mediaopt flowcontrol
1057 Along with the above mentioned changes generic support for setting
1058 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1059 e1000phy(4) as well as ip1000phy(4) have been converted to take
1060 advantage of it. This means that these drivers now no longer take the
1061 link0 parameter for selecting master mode but the master media option
1062 has to be used instead, for example like in the following:
1063 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1065 Selection of master mode now is also available with all other PHY
1066 drivers supporting 1000baseT.
1069 The TCP stack has received a significant update to add support for
1070 modularised congestion control and generally improve the clarity of
1071 congestion control decisions. Bump __FreeBSD_version to 900025. User
1072 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1073 sockstat) need to be recompiled.
1076 The man(1) utility has been replaced by a new version that no longer
1077 uses /etc/manpath.config. Please consult man.conf(5) for how to
1078 migrate local entries to the new format.
1081 The copyright strings printed by login(1) and sshd(8) at the time of a
1082 new connection have been removed to follow other operating systems and
1086 A workaround for a fixed ld bug has been removed in kernel code,
1087 so make sure that your system ld is built from sources after
1088 revision 210245 from 2010-07-19 (r211583 if building head kernel
1089 on stable/8, r211584 for stable/7; both from 2010-08-21).
1090 A symptom of incorrect ld version is different addresses for
1091 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1094 The $ipv6_prefer variable in rc.conf(5) has been split into
1095 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1097 The $ip6addrctl_policy is a variable to choose a pre-defined
1098 address selection policy set by ip6addrctl(8). A value
1099 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1102 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1103 flag (see an entry of 20090926) is set on an interface with no
1104 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1105 security reason. If you want IPv6 link-local address on all
1106 interfaces by default, set this to "YES".
1108 The old ipv6_prefer="YES" is equivalent to
1109 ipv6_activate_all_interfaces="YES" and
1110 ip6addrctl_policy="ipv6_prefer".
1113 DTrace has grown support for userland tracing. Due to this, DTrace is
1114 now i386 and amd64 only.
1115 dtruss(1) is now installed by default on those systems and a new
1116 kernel module is needed for userland tracing: fasttrap.
1117 No changes to your kernel config file are necessary to enable
1118 userland tracing, but you might consider adding 'STRIP=' and
1119 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1120 to have informative userland stack traces in DTrace (ustack).
1123 The acpi_aiboost(4) driver has been removed in favor of the new
1124 aibs(4) driver. You should update your kernel configuration file.
1127 BSD grep has been imported to the base system and it is built by
1128 default. It is completely BSD licensed, highly GNU-compatible, uses
1129 less memory than its GNU counterpart and has a small codebase.
1130 However, it is slower than its GNU counterpart, which is mostly
1131 noticeable for larger searches, for smaller ones it is measurable
1132 but not significant. The reason is complex, the most important factor
1133 is that we lack a modern and efficient regex library and GNU
1134 overcomes this by optimizing the searches internally. Future work
1135 on improving the regex performance is planned, for the meantime,
1136 users that need better performance, can build GNU grep instead by
1137 setting the WITH_GNU_GREP knob.
1140 Due to the import of powerpc64 support, all existing powerpc kernel
1141 configuration files must be updated with a machine directive like this:
1142 machine powerpc powerpc
1144 In addition, an updated config(8) is required to build powerpc kernels
1148 A new version of ZFS (version 15) has been merged to -HEAD.
1149 This version uses a python library for the following subcommands:
1150 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1151 For full functionality of these commands the following port must
1152 be installed: sysutils/py-zfs
1155 'vm_page's are now hashed by physical address to an array of mutexes.
1156 Currently this is only used to serialize access to hold_count. Over
1157 time the page queue mutex will be peeled away. This changes the size
1158 of pmap on every architecture. And requires all callers of vm_page_hold
1159 and vm_page_unhold to be updated.
1162 WITH_CTF can now be specified in src.conf (not recommended, there
1163 are some problems with static executables), make.conf (would also
1164 affect ports which do not use GNU make and do not override the
1165 compile targets) or in the kernel config (via "makeoptions
1167 When WITH_CTF was specified there before this was silently ignored,
1168 so make sure that WITH_CTF is not used in places which could lead
1169 to unwanted behavior.
1172 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1173 to allow 32-bit compatibility on non-x86 platforms. All kernel
1174 configurations on amd64 and ia64 platforms using these options must
1175 be modified accordingly.
1178 The utmp user accounting database has been replaced with utmpx,
1179 the user accounting interface standardized by POSIX.
1180 Unfortunately the semantics of utmp and utmpx don't match,
1181 making it practically impossible to support both interfaces.
1182 The user accounting database is used by tools like finger(1),
1183 last(1), talk(1), w(1) and ac(8).
1185 All applications in the base system use utmpx. This means only
1186 local binaries (e.g. from the ports tree) may still use these
1187 utmp database files. These applications must be rebuilt to make
1190 After the system has been upgraded, it is safe to remove the old
1191 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1192 assuming their contents is of no importance anymore. Old wtmp
1193 databases can only be used by last(1) and ac(8) after they have
1194 been converted to the new format using wtmpcvt(1).
1197 Introduce the kernel thread "deadlock resolver" (which can be enabled
1198 via the DEADLKRES option, see NOTES for more details) and the
1199 sleepq_type() function for sleepqueues.
1202 The rc.firewall and rc.firewall6 were unified, and
1203 rc.firewall6 and rc.d/ip6fw were removed.
1204 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1205 variables are obsoleted. Instead, the following new rc
1206 variables are added to rc.d/ipfw:
1208 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1209 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1210 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1212 The meanings correspond to the relevant IPv4 variables.
1218 The default terminal emulation for syscons(4) has been changed
1219 from cons25 to xterm on all platforms except pc98. This means
1220 that the /etc/ttys file needs to be updated to ensure correct
1221 operation of applications on the console.
1223 The terminal emulation style can be toggled per window by using
1224 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1225 options can be used to change the compile-time default back to
1228 To prevent graphical artifacts, make sure the TERM environment
1229 variable is set to match the terminal emulation that is being
1230 performed by syscons(4).
1233 The layout of the structure ieee80211req_scan_result has changed.
1234 Applications that require wireless scan results (e.g. ifconfig(8))
1235 from net80211 need to be recompiled.
1237 Applications such as wpa_supplicant(8) may require a full world
1238 build without using NO_CLEAN in order to get synchronized with the
1242 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1243 There's one kernel module for each firmware. Adding "device iwnfw"
1244 to the kernel configuration file means including all three firmware
1245 images inside the kernel. If you want to include just the one for
1246 your wireless card, use the devices iwn4965fw, iwn5000fw or
1250 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1251 into rc.d/netif. The changes are the following:
1253 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1254 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1255 Note that both variables need the "inet6" keyword at the head.
1257 Do not set $ipv6_network_interfaces manually if you do not
1258 understand what you are doing. It is not needed in most cases.
1260 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1263 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1264 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1266 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1267 all configured interfaces have "inet6 accept_rtadv" in the
1268 $ifconfig_IF_ipv6. These are for backward compatibility.
1270 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1271 functionality of interfaces with no corresponding
1272 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1273 and the default address selection policy of ip6addrctl(8)
1274 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1275 Note that if you want to configure IPv6 functionality on the
1276 disabled interfaces after boot, first you need to clear the flag by
1277 using ifconfig(8) like:
1279 ifconfig em0 inet6 -ifdisabled
1281 If YES, the default address selection policy is set as
1284 The default value of $ipv6_prefer is NO.
1286 4. If your system need to receive Router Advertisement messages,
1287 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1288 scripts automatically invoke rtsol(8) when the interface becomes
1289 UP. The Router Advertisement messages are used for SLAAC
1290 (State-Less Address AutoConfiguration).
1293 802.11s D3.03 support was committed. This is incompatible with the
1294 previous code, which was based on D3.0.
1297 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1298 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1299 control whether accepting Router Advertisement messages or not.
1300 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1301 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1302 The ifconfig(8) utility now supports these flags.
1305 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1306 mount(8) and -a option for df(1) to see them.
1309 The old tunable hw.bus.devctl_disable has been superseded by
1310 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1311 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1315 Remove the option STOP_NMI. The default action is now to use NMI only
1316 for KDB via the newly introduced function stop_cpus_hard() and
1317 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1320 The stable/8 branch created in subversion. This corresponds to the
1321 RELENG_8 branch in CVS.
1324 Bump the shared library version numbers for all libraries that do not
1325 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1326 __FreeBSD_version to 800105.
1329 Due to changes in the implementation of virtual network stack support,
1330 all network-related kernel modules must be recompiled. As this change
1331 breaks the ABI, bump __FreeBSD_version to 800104.
1334 The TOE interface to the TCP syncache has been modified to remove
1335 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1336 The cxgb driver is the only TOE consumer affected by this change, and
1337 needs to be recompiled along with the kernel. As this change breaks
1338 the ABI, bump __FreeBSD_version to 800103.
1341 Padding has been added to struct tcpcb, sackhint and tcpstat in
1342 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1343 maintaining the ABI. However, this change breaks the ABI, so bump
1344 __FreeBSD_version to 800102. User space tools that rely on the size of
1345 any of these structs (e.g. sockstat) need to be recompiled.
1348 The NFS_LEGACYRPC option has been removed along with the old kernel
1349 RPC implementation that this option selected. Kernel configurations
1350 may need to be adjusted.
1353 The network interface device nodes at /dev/net/<interface> have been
1354 removed. All ioctl operations can be performed the normal way using
1355 routing sockets. The kqueue functionality can generally be replaced
1356 with routing sockets.
1359 The documentation from the FreeBSD Documentation Project (Handbook,
1360 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1361 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1364 The ABI of various structures related to the SYSV IPC API have been
1365 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1366 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1370 Layout of struct vnet has changed as routing related variables were
1371 moved to their own Vimage module. Modules need to be recompiled. Bump
1372 __FreeBSD_version to 800099.
1375 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1376 respectively. As long as no more than 16 groups per process are used,
1377 no changes should be visible. When more than 16 groups are used, old
1378 binaries may fail if they call getgroups() or getgrouplist() with
1379 statically sized storage. Recompiling will work around this, but
1380 applications should be modified to use dynamically allocated storage
1381 for group arrays as POSIX.1-2008 does not cap an implementation's
1382 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1384 NFS and portalfs mounts may also be affected as the list of groups is
1385 truncated to 16. Users of NFS who use more than 16 groups, should
1386 take care that negative group permissions are not used on the exported
1387 file systems as they will not be reliable unless a GSSAPI based
1388 authentication method is used.
1391 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1392 option compiles in the support for adaptive spinning for lockmgrs
1393 which want to enable it. The lockinit() function now accepts the flag
1394 LK_ADAPTIVE in order to make the lock object subject to adaptive
1395 spinning when both held in write and read mode.
1398 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1399 changed. User applications that use this ioctl need to be rebuilt.
1402 The layout of struct thread has changed. Kernel and modules need to
1406 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1407 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1410 window(1) has been removed from the base system. It can now be
1411 installed from ports. The port is called misc/window.
1414 The way we are storing and accessing `routing table' entries has
1415 changed. Programs reading the FIB, like netstat, need to be
1419 A new netisr implementation has been added for FreeBSD 8. Network
1420 file system modules, such as igmp, ipdivert, and others, should be
1422 Bump __FreeBSD_version to 800096.
1425 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1429 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1430 Bump __FreeBSD_version to 800094.
1433 Add mnt_xflag field to 'struct mount'. File system modules need to be
1435 Bump __FreeBSD_version to 800093.
1438 The compiling option ADAPTIVE_SX has been retired while it has been
1439 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1440 The KPI for sx_init_flags() changes as accepting flags:
1441 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1442 been introduced in order to handle the reversed logic.
1443 Bump __FreeBSD_version to 800092.
1446 Add support for hierarchical jails. Remove global securelevel.
1447 Bump __FreeBSD_version to 800091.
1450 The layout of struct vnet_net has changed, therefore modules
1452 Bump __FreeBSD_version to 800090.
1455 The newly imported zic(8) produces a new format in the output. Please
1456 run tzsetup(8) to install the newly created data to /etc/localtime.
1459 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1460 hw.usb.* and is now consistent again with previous releases.
1463 802.11 monitor mode support was revised and driver api's were changed.
1464 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1465 of DLT_IEEE802_11. No user-visible data structures were changed but
1466 applications that use DLT_IEEE802_11 may require changes.
1467 Bump __FreeBSD_version to 800088.
1470 The layout of the following structs has changed: sysctl_oid,
1471 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1472 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1473 panics may be experienced. World rebuild is required for
1474 correctly checking networking state from userland.
1475 Bump __FreeBSD_version to 800085.
1478 MLDv2 and Source-Specific Multicast (SSM) have been merged
1479 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1480 The implementation of SSM within FreeBSD's IPv6 stack closely
1481 follows the IPv4 implementation.
1483 For kernel developers:
1485 * The most important changes are that the ip6_output() and
1486 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1487 and this lock has been downgraded to a non-recursive mutex.
1489 * As with the changes to the IPv4 stack to support SSM, filtering
1490 of inbound multicast traffic must now be performed by transport
1491 protocols within the IPv6 stack. This does not apply to TCP and
1492 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1494 * The KPIs used by IPv6 multicast are similar to those used by
1495 the IPv4 stack, with the following differences:
1496 * im6o_mc_filter() is analogous to imo_multicast_filter().
1497 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1498 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1499 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1500 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1501 for MLDv1 have an additional 'timer' argument which is used to
1502 jitter the initial membership report for the solicited-node
1503 multicast membership on-link.
1504 * This is not strictly needed for MLDv2, which already jitters
1505 its report transmissions. However, the 'timer' argument is
1506 preserved in case MLDv1 is active on the interface.
1508 * The KAME linked-list based IPv6 membership implementation has
1509 been refactored to use a vector similar to that used by the IPv4
1511 Code which maintains a list of its own multicast memberships
1512 internally, e.g. carp, has been updated to reflect the new
1515 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1516 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1517 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1518 implementation constraint which needs to be addressed in HEAD.
1520 For application developers:
1522 * The changes are broadly similar to those made for the IPv4
1525 * The use of IPv4 and IPv6 multicast socket options on the same
1526 socket, using mapped addresses, HAS NOT been tested or supported.
1528 * There are a number of issues with the implementation of various
1529 IPv6 multicast APIs which need to be resolved in the API surface
1530 before the implementation is fully compatible with KAME userland
1531 use, and these are mostly to do with interface index treatment.
1533 * The literature available discusses the use of either the delta / ASM
1534 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1535 using setsourcefilter(3)/getsourcefilter(3). For more information
1536 please refer to RFC 3768, 'Socket Interface Extensions for
1537 Multicast Source Filters'.
1539 * Applications which use the published RFC 3678 APIs should be fine.
1541 For systems administrators:
1543 * The mtest(8) utility has been refactored to support IPv6, in
1544 addition to IPv4. Interface addresses are no longer accepted
1545 as arguments, their names must be used instead. The utility
1546 will map the interface name to its first IPv4 address as
1547 returned by getifaddrs(3).
1549 * The ifmcstat(8) utility has also been updated to print the MLDv2
1550 endpoint state and source filter lists via sysctl(3).
1552 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1553 loopback of IPv6 multicast datagrams by default; it defaults to 1
1554 to preserve the existing behaviour. Disabling multicast loopback is
1555 recommended for optimal system performance.
1557 * The IPv6 MROUTING code has been changed to examine this sysctl
1558 instead of attempting to perform a group lookup before looping
1559 back forwarded datagrams.
1561 Bump __FreeBSD_version to 800084.
1564 Implement low-level Bluetooth HCI API.
1565 Bump __FreeBSD_version to 800083.
1568 The layout of struct malloc_type, used by modules to register new
1569 memory allocation types, has changed. Most modules will need to
1570 be rebuilt or panics may be experienced.
1571 Bump __FreeBSD_version to 800081.
1574 Anticipate overflowing inp_flags - add inp_flags2.
1575 This changes most offsets in inpcb, so checking v4 connection
1576 state will require a world rebuild.
1577 Bump __FreeBSD_version to 800080.
1580 Add an llentry to struct route and struct route_in6. Modules
1581 embedding a struct route will need to be recompiled.
1582 Bump __FreeBSD_version to 800079.
1585 The size of rt_metrics_lite and by extension rtentry has changed.
1586 Networking administration apps will need to be recompiled.
1587 The route command now supports show as an alias for get, weighting
1588 of routes, sticky and nostick flags to alter the behavior of stateful
1590 Bump __FreeBSD_version to 800078.
1593 Do not use Giant for kbdmux(4) locking. This is wrong and
1594 apparently causing more problems than it solves. This will
1595 re-open the issue where interrupt handlers may race with
1596 kbdmux(4) in polling mode. Typical symptoms include (but
1597 not limited to) duplicated and/or missing characters when
1598 low level console functions (such as gets) are used while
1599 interrupts are enabled (for example geli password prompt,
1600 mountroot prompt etc.). Disabling kbdmux(4) may help.
1603 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1604 kernel modules referencing any of the above need to be recompiled.
1605 Bump __FreeBSD_version to 800075.
1608 GEOM_PART has become the default partition slicer for storage devices,
1609 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1610 introduces some changes:
1612 MSDOS/EBR: the devices created from MSDOS extended partition entries
1613 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1614 to devices with offset-based names. fstabs may need to be modified.
1616 BSD: the "geometry does not match label" warning is harmless in most
1617 cases but it points to problems in file system misalignment with
1618 disk geometry. The "c" partition is now implicit, covers the whole
1619 top-level drive and cannot be (mis)used by users.
1621 General: Kernel dumps are now not allowed to be written to devices
1622 whose partition types indicate they are meant to be used for file
1623 systems (or, in case of MSDOS partitions, as something else than
1626 Most of these changes date approximately from 200812.
1629 The uscanner(4) driver has been removed from the kernel. This follows
1630 Linux removing theirs in 2.6 and making libusb the default interface
1631 (supported by sane).
1634 The multicast forwarding code has been cleaned up. netstat(1)
1635 only relies on KVM now for printing bandwidth upcall meters.
1636 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1637 ip6_mroute_mod respectively. The config(5) options for statically
1638 compiling this code remain the same, i.e. 'options MROUTING'.
1641 Support for the IFF_NEEDSGIANT network interface flag has been
1642 removed, which means that non-MPSAFE network device drivers are no
1643 longer supported. In particular, if_ar, if_sr, and network device
1644 drivers from the old (legacy) USB stack can no longer be built or
1648 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1649 a bunch of new language catalog files have also been added.
1650 This means that some common libc messages are now localized and
1651 they depend on the LC_MESSAGES environmental variable.
1654 The k8temp(4) driver has been renamed to amdtemp(4) since
1655 support for Family 10 and Family 11 CPU families was added.
1658 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1659 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1661 For kernel developers, the most important changes are that the
1662 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1663 and this lock has been downgraded to a non-recursive mutex.
1665 Transport protocols (UDP, Raw IP) are now responsible for filtering
1666 inbound multicast traffic according to group membership and source
1667 filters. The imo_multicast_filter() KPI exists for this purpose.
1668 Transports which do not use multicast (SCTP, TCP) already reject
1669 multicast by default. Forwarding and receive performance may improve
1670 as a mutex acquisition is no longer needed in the ip_input()
1671 low-level input path. in_addmulti() and in_delmulti() are shimmed
1672 to new KPIs which exist to support SSM in-kernel.
1674 For application developers, it is recommended that loopback of
1675 multicast datagrams be disabled for best performance, as this
1676 will still cause the lock to be taken for each looped-back
1677 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1678 be tuned to 0 to disable loopback by default; it defaults to 1
1679 to preserve the existing behaviour.
1681 For systems administrators, to obtain best performance with
1682 multicast reception and multiple groups, it is always recommended
1683 that a card with a suitably precise hash filter is used. Hash
1684 collisions will still result in the lock being taken within the
1685 transport protocol input path to check group membership.
1687 If deploying FreeBSD in an environment with IGMP snooping switches,
1688 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1689 enabled; this forces 224.0.0.0/24 group membership to be announced
1692 The size of 'struct igmpstat' has changed; netstat needs to be
1693 recompiled to reflect this.
1694 Bump __FreeBSD_version to 800070.
1697 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1698 updated to use it. This requires a buildworld/installworld in order to
1699 update the library and dependencies (usbconfig, etc). Its advisable to
1700 rebuild all ports which uses libusb. More specific directions are given
1701 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1702 libusb are no longer required and can be removed.
1705 A workaround is committed to allow the creation of System V shared
1706 memory segment of size > 2 GB on the 64-bit architectures.
1707 Due to a limitation of the existing ABI, the shm_segsz member
1708 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1709 wrong for large segments. Note that limits must be explicitly
1710 raised to allow such segments to be created.
1713 The layout of struct ifnet has changed, requiring a rebuild of all
1714 network device driver modules.
1717 The /dev handling for the new USB stack has changed, a
1718 buildworld/installworld is required for libusb20.
1721 The new USB2 stack has now been permanently moved in and all kernel and
1722 module names reverted to their previous values (eg, usb, ehci, ohci,
1723 ums, ...). The old usb stack can be compiled in by prefixing the name
1724 with the letter 'o', the old usb modules have been removed.
1725 Updating entry 20090216 for xorg and 20090215 for libmap may still
1729 The rc.conf(5) option if_up_delay has been renamed to
1730 defaultroute_delay to better reflect its purpose. If you have
1731 customized this setting in /etc/rc.conf you need to update it to
1735 xorg 7.4 wants to configure its input devices via hald which does not
1736 yet work with USB2. If the keyboard/mouse does not work in xorg then
1738 Option "AllowEmptyInput" "off"
1739 to your ServerLayout section. This will cause X to use the configured
1740 kbd and mouse sections from your xorg.conf.
1743 The GENERIC kernels for all architectures now default to the new USB2
1744 stack. No kernel config options or code have been removed so if a
1745 problem arises please report it and optionally revert to the old USB
1746 stack. If you are loading USB kernel modules or have a custom kernel
1747 that includes GENERIC then ensure that usb names are also changed over,
1748 eg uftdi -> usb2_serial_ftdi.
1750 Older programs linked against the ports libusb 0.1 need to be
1751 redirected to the new stack's libusb20. /etc/libmap.conf can
1753 # Map old usb library to new one for usb2 stack
1754 libusb-0.1.so.8 libusb20.so.1
1757 All USB ethernet devices now attach as interfaces under the name ueN
1758 (eg. ue0). This is to provide a predictable name as vendors often
1759 change usb chipsets in a product without notice.
1762 The ichsmb(4) driver has been changed to require SMBus slave
1763 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1764 All of the other SMBus controller drivers require left-justified
1765 slave addresses, so this change makes all the drivers provide the
1769 INET6 statistics (struct ip6stat) was updated.
1770 netstat(1) needs to be recompiled.
1773 NTFS has been removed from GENERIC kernel on amd64 to match
1774 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1775 will load ntfs.ko module automatically when NTFS support is
1776 actually needed, unless ntfs.ko is not installed or security
1777 level prohibits loading kernel modules. If either is the case,
1778 "options NTFS" has to be added into kernel config.
1781 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1782 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1783 800061. User space tools that rely on the size of struct tcpcb in
1784 tcp_var.h (e.g. sockstat) need to be recompiled.
1787 ng_tty(4) module updated to match the new TTY subsystem.
1788 Due to API change, user-level applications must be updated.
1789 New API support added to mpd5 CVS and expected to be present
1790 in next mpd5.3 release.
1793 With __FreeBSD_version 800060 the makefs tool is part of
1794 the base system (it was a port).
1797 The afdata and ifnet locks have been changed from mutexes to
1798 rwlocks, network modules will need to be re-compiled.
1801 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1802 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1803 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1804 architecture and 40 bytes on 64-bit architecture. The userland
1805 applications "arp" and "ndp" have been updated accordingly.
1806 The output from "netstat -r" shows only routing entries and
1807 none of the L2 information.
1810 __FreeBSD_version 800057 marks the switchover from the
1811 binary ath hal to source code. Users must add the line:
1813 options AH_SUPPORT_AR5416
1815 to their kernel config files when specifying:
1819 The ath_hal module no longer exists; the code is now compiled
1820 together with the driver in the ath module. It is now
1821 possible to tailor chip support (i.e. reduce the set of chips
1822 and thereby the code size); consult ath_hal(4) for details.
1825 __FreeBSD_version 800054 adds memory barriers to
1826 <machine/atomic.h>, new interfaces to ifnet to facilitate
1827 multiple hardware transmit queues for cards that support
1828 them, and a lock-less ring-buffer implementation to
1829 enable drivers to more efficiently manage queueing of
1833 A new version of ZFS (version 13) has been merged to -HEAD.
1834 This version has zpool attribute "listsnapshots" off by
1835 default, which means "zfs list" does not show snapshots,
1836 and is the same as Solaris behavior.
1839 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1842 The uhci, ohci, ehci and slhci USB Host controller drivers have
1843 been put into separate modules. If you load the usb module
1844 separately through loader.conf you will need to load the
1845 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1846 controller add the following to loader.conf:
1852 The ABI used by the PMC toolset has changed. Please keep
1853 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1857 atapci kernel module now includes only generic PCI ATA
1858 driver. AHCI driver moved to ataahci kernel module.
1859 All vendor-specific code moved into separate kernel modules:
1860 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1861 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1862 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1863 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1866 The TTY subsystem of the kernel has been replaced by a new
1867 implementation, which provides better scalability and an
1868 improved driver model. Most common drivers have been migrated to
1869 the new TTY subsystem, while others have not. The following
1870 drivers have not yet been ported to the new TTY layer:
1873 cy, digi, rc, rp, sio
1879 ng_h4, ng_tty, ppp, sl, snp
1881 Adding these drivers to your kernel configuration file shall
1882 cause compilation to fail.
1885 ntpd has been upgraded to 4.2.4p5.
1888 OpenSSH has been upgraded to 5.1p1.
1890 For many years, FreeBSD's version of OpenSSH preferred DSA
1891 over RSA for host and user authentication keys. With this
1892 upgrade, we've switched to the vendor's default of RSA over
1893 DSA. This may cause upgraded clients to warn about unknown
1894 host keys even for previously known hosts. Users should
1895 follow the usual procedure for verifying host keys before
1896 accepting the RSA key.
1898 This can be circumvented by setting the "HostKeyAlgorithms"
1899 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1902 Please note that the sequence of keys offered for
1903 authentication has been changed as well. You may want to
1904 specify IdentityFile in a different order to revert this
1908 The sio(4) driver has been removed from the i386 and amd64
1909 kernel configuration files. This means uart(4) is now the
1910 default serial port driver on those platforms as well.
1912 To prevent collisions with the sio(4) driver, the uart(4) driver
1913 uses different names for its device nodes. This means the
1914 onboard serial port will now most likely be called "ttyu0"
1915 instead of "ttyd0". You may need to reconfigure applications to
1916 use the new device names.
1918 When using the serial port as a boot console, be sure to update
1919 /boot/device.hints and /etc/ttys before booting the new kernel.
1920 If you forget to do so, you can still manually specify the hints
1921 at the loader prompt:
1923 set hint.uart.0.at="isa"
1924 set hint.uart.0.port="0x3F8"
1925 set hint.uart.0.flags="0x10"
1926 set hint.uart.0.irq="4"
1930 The gpt(8) utility has been removed. Use gpart(8) to partition
1934 The version that Linuxulator emulates was changed from 2.4.2
1935 to 2.6.16. If you experience any problems with Linux binaries
1936 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1937 if it fixes the problem contact emulation mailing list.
1940 ISDN4BSD (I4B) was removed from the src tree. You may need to
1941 update a your kernel configuration and remove relevant entries.
1944 I have checked in code to support multiple routing tables.
1945 See the man pages setfib(1) and setfib(2).
1946 This is a hopefully backwards compatible version,
1947 but to make use of it you need to compile your kernel
1948 with options ROUTETABLES=2 (or more up to 16).
1951 The 802.11 wireless support was redone to enable multi-bss
1952 operation on devices that are capable. The underlying device
1953 is no longer used directly but instead wlanX devices are
1954 cloned with ifconfig. This requires changes to rc.conf files.
1955 For example, change:
1956 ifconfig_ath0="WPA DHCP"
1959 ifconfig_wlan0="WPA DHCP"
1960 see rc.conf(5) for more details. In addition, mergemaster of
1961 /etc/rc.d is highly recommended. Simultaneous update of userland
1962 and kernel wouldn't hurt either.
1964 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1965 modules were merged into the base wlan module. All references
1966 to these modules (e.g. in kernel config files) must be removed.
1969 psm(4) has gained write(2) support in native operation level.
1970 Arbitrary commands can be written to /dev/psm%d and status can
1971 be read back from it. Therefore, an application is responsible
1972 for status validation and error recovery. It is a no-op in
1973 other operation levels.
1976 Support for KSE threading has been removed from the kernel. To
1977 run legacy applications linked against KSE libmap.conf may
1978 be used. The following libmap.conf may be used to ensure
1979 compatibility with any prior release:
1981 libpthread.so.1 libthr.so.1
1982 libpthread.so.2 libthr.so.2
1983 libkse.so.3 libthr.so.3
1986 The layout of struct vmspace has changed. This affects libkvm
1987 and any executables that link against libkvm and use the
1988 kvm_getprocs() function. In particular, but not exclusively,
1989 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1990 The effects are minimal, but it's advisable to upgrade world
1994 The latest em driver no longer has support in it for the
1995 82575 adapter, this is now moved to the igb driver. The
1996 split was done to make new features that are incompatible
1997 with older hardware easier to do.
2000 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2001 likewise the kernel option is now GEOM_LINUX_LVM.
2004 The default NFS mount mode has changed from UDP to TCP for
2005 increased reliability. If you rely on (insecurely) NFS
2006 mounting across a firewall you may need to update your
2010 Belatedly note the addition of m_collapse for compacting
2014 The fts(3) structures have been changed to use adequate
2015 integer types for their members and so to be able to cope
2016 with huge file trees. The old fts(3) ABI is preserved
2017 through symbol versioning in libc, so third-party binaries
2018 using fts(3) should still work, although they will not take
2019 advantage of the extended types. At the same time, some
2020 third-party software might fail to build after this change
2021 due to unportable assumptions made in its source code about
2022 fts(3) structure members. Such software should be fixed
2023 by its vendor or, in the worst case, in the ports tree.
2024 FreeBSD_version 800015 marks this change for the unlikely
2025 case that a portable fix is impossible.
2028 To upgrade to -current after this date, you must be running
2029 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2030 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2033 The ADAPTIVE_GIANT kernel option has been retired because its
2034 functionality is the default now.
2037 The AT keyboard emulation of sunkbd(4) has been turned on
2038 by default. In order to make the special symbols of the Sun
2039 keyboards driven by sunkbd(4) work under X these now have
2040 to be configured the same way as Sun USB keyboards driven
2041 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2043 Option "XkbLayout" "us"
2044 Option "XkbRules" "xorg"
2045 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2048 It has been decided that it is desirable to provide ABI
2049 backwards compatibility to the FreeBSD 4/5/6 versions of the
2050 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2051 broken with the introduction of PCI domain support (see the
2052 20070930 entry). Unfortunately, this required the ABI of
2053 PCIOCGETCONF to be broken again in order to be able to
2054 provide backwards compatibility to the old version of that
2055 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2056 again. As for prominent ports this affects neither pciutils
2057 nor xorg-server this time, the hal port needs to be rebuilt
2061 The misnamed kthread_create() and friends have been renamed
2062 to kproc_create() etc. Many of the callers already
2063 used kproc_start()..
2064 I will return kthread_create() and friends in a while
2065 with implementations that actually create threads, not procs.
2066 Renaming corresponds with version 800002.
2075 Avoid using make -j when upgrading. While generally safe, there are
2076 sometimes problems using -j to upgrade. If your upgrade fails with
2077 -j, please try again without -j. From time to time in the past there
2078 have been problems using -j with buildworld and/or installworld. This
2079 is especially true when upgrading between "distant" versions (eg one
2080 that cross a major release boundary or several minor releases, or when
2081 several months have passed on the -current branch).
2083 Sometimes, obscure build problems are the result of environment
2084 poisoning. This can happen because the make utility reads its
2085 environment when searching for values for global variables. To run
2086 your build attempts in an "environmental clean room", prefix all make
2087 commands with 'env -i '. See the env(1) manual page for more details.
2089 When upgrading from one major version to another it is generally best
2090 to upgrade to the latest code in the currently installed branch first,
2091 then do an upgrade to the new branch. This is the best-tested upgrade
2092 path, and has the highest probability of being successful. Please try
2093 this approach before reporting problems with a major version upgrade.
2095 When upgrading a live system, having a root shell around before
2096 installing anything can help undo problems. Not having a root shell
2097 around can lead to problems if pam has changed too much from your
2098 starting point to allow continued authentication after the upgrade.
2102 When upgrading the boot ZFS pool to a new version, always follow
2105 1.) recompile and reinstall the ZFS boot loader and boot block
2106 (this is part of "make buildworld" and "make installworld")
2108 2.) update the ZFS boot block on your boot drive
2110 The following example updates the ZFS boot block on the first
2111 partition (freebsd-boot) of a GPT partitioned drive ad0:
2112 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2114 Non-boot pools do not need these updates.
2118 If you are updating from a prior version of FreeBSD (even one just
2119 a few days old), you should follow this procedure. It is the most
2120 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2122 make kernel-toolchain
2123 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2124 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2126 To test a kernel once
2127 ---------------------
2128 If you just want to boot a kernel once (because you are not sure
2129 if it works, or if you want to boot a known bad kernel to provide
2130 debugging information) run
2131 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2132 nextboot -k testkernel
2134 To just build a kernel when you know that it won't mess you up
2135 --------------------------------------------------------------
2136 This assumes you are already running a CURRENT system. Replace
2137 ${arch} with the architecture of your machine (e.g. "i386",
2138 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2140 cd src/sys/${arch}/conf
2141 config KERNEL_NAME_HERE
2142 cd ../compile/KERNEL_NAME_HERE
2147 If this fails, go to the "To build a kernel" section.
2149 To rebuild everything and install it on the current system.
2150 -----------------------------------------------------------
2151 # Note: sometimes if you are running current you gotta do more than
2152 # is listed here if you are upgrading from a really old current.
2154 <make sure you have good level 0 dumps>
2156 make kernel KERNCONF=YOUR_KERNEL_HERE
2158 <reboot in single user> [3]
2165 To cross-install current onto a separate partition
2166 --------------------------------------------------
2167 # In this approach we use a separate partition to hold
2168 # current's root, 'usr', and 'var' directories. A partition
2169 # holding "/", "/usr" and "/var" should be about 2GB in
2172 <make sure you have good level 0 dumps>
2175 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2176 <maybe newfs current's root partition>
2177 <mount current's root partition on directory ${CURRENT_ROOT}>
2178 make installworld DESTDIR=${CURRENT_ROOT}
2179 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2180 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2181 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2182 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2183 <reboot into current>
2184 <do a "native" rebuild/install as described in the previous section>
2185 <maybe install compatibility libraries from ports/misc/compat*>
2189 To upgrade in-place from stable to current
2190 ----------------------------------------------
2191 <make sure you have good level 0 dumps>
2193 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2195 <reboot in single user> [3]
2202 Make sure that you've read the UPDATING file to understand the
2203 tweaks to various things you need. At this point in the life
2204 cycle of current, things change often and you are on your own
2205 to cope. The defaults can also change, so please read ALL of
2206 the UPDATING entries.
2208 Also, if you are tracking -current, you must be subscribed to
2209 freebsd-current@freebsd.org. Make sure that before you update
2210 your sources that you have read and understood all the recent
2211 messages there. If in doubt, please track -stable which has
2212 much fewer pitfalls.
2214 [1] If you have third party modules, such as vmware, you
2215 should disable them at this point so they don't crash your
2218 [3] From the bootblocks, boot -s, and then do
2223 adjkerntz -i # if CMOS is wall time
2224 Also, when doing a major release upgrade, it is required that
2225 you boot into single user mode to do the installworld.
2227 [4] Note: This step is non-optional. Failure to do this step
2228 can result in a significant reduction in the functionality of the
2229 system. Attempting to do it by hand is not recommended and those
2230 that pursue this avenue should read this file carefully, as well
2231 as the archives of freebsd-current and freebsd-hackers mailing lists
2232 for potential gotchas. The -U option is also useful to consider.
2233 See mergemaster(8) for more information.
2235 [5] Usually this step is a noop. However, from time to time
2236 you may need to do this if you get unknown user in the following
2237 step. It never hurts to do it all the time. You may need to
2238 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2239 install) after the buildworld before this step if you last updated
2240 from current before 20130425 or from -stable before 20130430.
2242 [6] This only deletes old files and directories. Old libraries
2243 can be deleted by "make delete-old-libs", but you have to make
2244 sure that no program is using those libraries anymore.
2246 [8] In order to have a kernel that can run the 4.x binaries needed to
2247 do an installworld, you must include the COMPAT_FREEBSD4 option in
2248 your kernel. Failure to do so may leave you with a system that is
2249 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2250 required to run the 5.x binaries on more recent kernels. And so on
2251 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2253 Make sure that you merge any new devices from GENERIC since the
2254 last time you updated your kernel config file.
2256 [9] When checking out sources, you must include the -P flag to have
2257 cvs prune empty directories.
2259 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2260 "?=" instead of the "=" assignment operator, so that buildworld can
2261 override the CPUTYPE if it needs to.
2263 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2264 not on the command line, or in /etc/make.conf. buildworld will
2265 warn if it is improperly defined.
2268 This file contains a list, in reverse chronological order, of major
2269 breakages in tracking -current. It is not guaranteed to be a complete
2270 list of such breakages, and only contains entries since October 10, 2007.
2271 If you need to see UPDATING entries from before that date, you will need
2272 to fetch an UPDATING file from an older FreeBSD release.
2274 Copyright information:
2276 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2278 Redistribution, publication, translation and use, with or without
2279 modification, in full or in part, in any form or format of this
2280 document are permitted without further permission from the author.
2282 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2283 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2284 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2285 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2286 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2287 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2288 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2289 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2290 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2291 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2292 POSSIBILITY OF SUCH DAMAGE.
2294 Contact Warner Losh if you have any questions about your use of