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 20150513: p10 FreeBSD-EN-15:04.freebsd-update
22 Fix bug with freebsd-update(8) that does not ensure the previous
23 upgrade was completed. [EN-15:04]
25 Fix deadlock on reboot with UFS tuned with SU+J. [EN-15:05]
27 20150407: p9 FreeBSD-SA-15:04.igmp [revised]
29 FreeBSD-SA-15:08.bsdinstall
32 Improved patch for SA-15:04.igmp.
34 Fix multiple vulnerabilities of ntp. [SA-15:07]
36 Fix bsdinstall(8) insecure default GELI keyfile permissions. [SA-15:08]
38 Fix Denial of Service with IPv6 Router Advertisements. [SA-15:09]
41 Fix patch for SA-15:06.openssl.
43 20150319: p7 FreeBSD-SA-15:06.openssl
44 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
46 20150225: p6 FreeBSD-SA-15:04.igmp
48 FreeBSD-EN-15:02.openssl
49 FreeBSD-EN-15:03.freebsd-update
51 Fix integer overflow in IGMP protocol. [SA-15:04]
53 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
55 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
57 Fix freebsd-update libraries update ordering issue. [EN-15:03]
59 20150127: p5 FreeBSD-SA-15:02.kmem
62 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
63 vulnerability. [SA-15:02]
65 Fix SCTP stream reset vulnerability. [SA-15:03]
67 20150114: p4 FreeBSD-SA-15:01.openssl
68 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
70 20141223: p3 FreeBSD-SA-14:31.ntp
71 FreeBSD-EN-14:13.freebsd-update
73 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
74 Fix directory deletion issue in freebsd-update. [EN-14:13]
76 20141217: p2 FreeBSD-SA-14:30.unbound
77 Fix unbound remote denial of service vulnerability.
79 20141210: p1 FreeBSD-SA-14:27.stdio
82 Fix buffer overflow in stdio. [SA-14:27]
84 Fix multiple vulnerabilities in file(1) and libmagic(3).
88 The ofwfb driver, used to provide a graphics console on PowerPC when
89 using vt(4), no longer allows mmap() of all of physical memory. This
90 will prevent Xorg on PowerPC with some ATI graphics cards from
91 initializing properly unless x11-servers/xorg-server is updated to
95 The libatf-c and libatf-c++ major versions were downgraded to 0 and
96 1 respectively to match the upstream numbers. They were out of
97 sync because, when they were originally added to FreeBSD, the
98 upstream versions were not respected. These libraries are private
99 and not yet built by default, so renumbering them should be a
100 non-issue. However, unclean source trees will yield broken test
101 programs once the operator executes "make delete-old-libs" after a
104 Additionally, the atf-sh binary was made private by moving it into
105 /usr/libexec/. Already-built shell test programs will keep the
106 path to the old binary so they will break after "make delete-old"
109 If you are using WITH_TESTS=yes (not the default), wipe the object
110 tree and rebuild from scratch to prevent spurious test failures.
111 This is only needed once: the misnumbered libraries and misplaced
112 binaries have been added to OptionalObsoleteFiles.inc so they will
113 be removed during a clean upgrade.
116 The ixgbe tunables now match their sysctl counterparts, for example:
117 hw.ixgbe.enable_aim => hw.ix.enable_aim
118 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
121 The NFSv4.1 server committed by r269398 changes the internal
122 function call interfaces used between the NFS and krpc modules.
123 As such, __FreeBSD_version was bumped.
126 The default unbound configuration has been modified to address
127 issues with reverse lookups on networks that use private
128 address ranges. If you use the local_unbound service, run
129 "service local_unbound setup" as root to regenerate your
130 configuration, then "service local_unbound reload" to load the
134 It is no longer necessary to include the dwarf version in your DEBUG
135 options in your kernel config file. The bug that required it to be
136 placed in the config file has bene fixed. DEBUG should now just
137 contain -g. The build system will automatically update things
138 to do the right thing.
141 Several ABI breaking changes were merged to CTL and new iSCSI code.
142 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
143 iscsictl need to be rebuilt to work with a new kernel.
146 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
147 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
148 which differs from the behaviour controlled by this knob.)
151 On i386 and amd64 systems, the onifconsole flag is now set by default
152 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
153 as a login TTY if it is set in the bootloader as an active kernel
154 console. No changes in behavior should result otherwise. To revert to
155 the previous behavior, set ttyu0 to "off" in /etc/ttys.
158 Clang and llvm have been upgraded to 3.4.1 release.
161 Clang and llvm have been upgraded to 3.4 release.
164 If a Makefile in a tests/ directory was auto-generating a Kyuafile
165 instead of providing an explicit one, this would prevent such
166 Makefile from providing its own Kyuafile in the future during
167 NO_CLEAN builds. This has been fixed in the Makefiles but manual
168 intervention is needed to clean an objdir if you use NO_CLEAN:
169 # find /usr/obj -name Kyuafile | xargs rm -f
172 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
173 capability mode support. Please note that enabling the feature in
174 kernel is still highly recommended.
177 OpenSSH is now built with sandbox support, and will use sandbox as
178 the default privilege separation method. This requires Capsicum
179 capability mode support in kernel.
182 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
183 been deprecated and will not be part of FreeBSD 11.0 and later
184 releases. If you use this driver, please consider switching to
185 the nfe(4) driver instead.
191 The behavior of gss_pseudo_random() for the krb5 mechanism
192 has changed, for applications requesting a longer random string
193 than produced by the underlying enctype's pseudo-random() function.
194 In particular, the random string produced from a session key of
195 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
196 be different at the 17th octet and later, after this change.
197 The counter used in the PRF+ construction is now encoded as a
198 big-endian integer in accordance with RFC 4402.
199 __FreeBSD_version is bumped to 1000701.
202 The WITHOUT_ATF build knob has been removed and its functionality
203 has been subsumed into the more generic WITHOUT_TESTS. If you were
204 using the former to disable the build of the ATF libraries, you
205 should change your settings to use the latter.
208 The default version of mtree is nmtree which is obtained from
209 NetBSD. The output is generally the same, but may vary
210 slightly. If you found you need identical output adding
211 "-F freebsd9" to the command line should do the trick. For the
212 time being, the old mtree is available as fmtree.
215 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
216 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
217 1.1.4_8 and verify bsdyml not linked in, before running "make
219 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
221 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
224 The rc.d/jail script has been updated to support jail(8)
225 configuration file. The "jail_<jname>_*" rc.conf(5) variables
226 for per-jail configuration are automatically converted to
227 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
228 This is transparently backward compatible. See below about some
229 incompatibilities and rc.conf(5) manual page for more details.
231 These variables are now deprecated in favor of jail(8) configuration
232 file. One can use "rc.d/jail config <jname>" command to generate
233 a jail(8) configuration file in /var/run/jail.<jname>.conf without
234 running the jail(8) utility. The default pathname of the
235 configuration file is /etc/jail.conf and can be specified by
236 using $jail_conf or $jail_<jname>_conf variables.
238 Please note that jail_devfs_ruleset accepts an integer at
239 this moment. Please consider to rewrite the ruleset name
243 BIND has been removed from the base system. If all you need
244 is a local resolver, simply enable and start the local_unbound
245 service instead. Otherwise, several versions of BIND are
246 available in the ports tree. The dns/bind99 port is one example.
248 With this change, nslookup(1) and dig(1) are no longer in the base
249 system. Users should instead use host(1) and drill(1) which are
250 in the base system. Alternatively, nslookup and dig can
251 be obtained by installing the dns/bind-tools port.
254 With the addition of unbound(8), a new unbound user is now
255 required during installworld. "mergemaster -p" can be used to
256 add the user prior to installworld, as documented in the handbook.
259 OpenSSH is now built with DNSSEC support, and will by default
260 silently trust signed SSHFP records. This can be controlled with
261 the VerifyHostKeyDNS client configuration setting. DNSSEC support
262 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
265 The GNU Compiler Collection and C++ standard library (libstdc++)
266 are no longer built by default on platforms where clang is the system
267 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
271 The PROCDESC kernel option is now part of the GENERIC kernel
272 configuration and is required for the rwhod(8) to work.
273 If you are using custom kernel configuration, you should include
277 The API and ABI related to the Capsicum framework was modified
278 in backward incompatible way. The userland libraries and programs
279 have to be recompiled to work with the new kernel. This includes the
280 following libraries and programs, but the whole buildworld is
281 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
282 kdump, procstat, rwho, rwhod, uniq.
285 AES-NI intrinsic support has been added to gcc. The AES-NI module
286 has been updated to use this support. A new gcc is required to build
287 the aesni module on both i386 and amd64.
290 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
291 Thus "device padlock_rng" and "device rdrand_rng" should be
292 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
295 WITH_ICONV has been split into two feature sets. WITH_ICONV now
296 enables just the iconv* functionality and is now on by default.
297 WITH_LIBICONV_COMPAT enables the libiconv api and link time
298 compatability. Set WITHOUT_ICONV to build the old way.
299 If you have been using WITH_ICONV before, you will very likely
300 need to turn on WITH_LIBICONV_COMPAT.
303 INVARIANTS option now enables DEBUG for code with OpenSolaris and
304 Illumos origin, including ZFS. If you have INVARIANTS in your
305 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
307 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
308 locks if WITNESS option was set. Because that generated a lot of
309 witness(9) reports and all of them were believed to be false
310 positives, this is no longer done. New option OPENSOLARIS_WITNESS
311 can be used to achieve the previous behavior.
314 Timer values in IPv6 data structures now use time_uptime instead
315 of time_second. Although this is not a user-visible functional
316 change, userland utilities which directly use them---ndp(8),
317 rtadvd(8), and rtsold(8) in the base system---need to be updated
321 find -delete can now delete the pathnames given as arguments,
322 instead of only files found below them or if the pathname did
323 not contain any slashes. Formerly, the following error message
326 find: -delete: <path>: relative path potentially not safe
328 Deleting the pathnames given as arguments can be prevented
329 without error messages using -mindepth 1 or by changing
330 directory and passing "." as argument to find. This works in the
331 old as well as the new version of find.
334 Behavior of devfs rules path matching has been changed.
335 Pattern is now always matched against fully qualified devfs
336 path and slash characters must be explicitly matched by
337 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
338 subdirectories must be reviewed.
341 The default ARM ABI has changed to the ARM EABI. The old ABI is
342 incompatible with the ARM EABI and all programs and modules will
343 need to be rebuilt to work with a new kernel.
345 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
347 NOTE: Support for the old ABI will be removed in the future and
348 users are advised to upgrade.
351 pkg_install has been disconnected from the build if you really need it
352 you should add WITH_PKGTOOLS in your src.conf(5).
355 Most of network statistics structures were changed to be able
356 keep 64-bits counters. Thus all tools, that work with networking
357 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
360 Fix targets that run multiple make's to use && rather than ;
361 so that subsequent steps depend on success of previous.
363 NOTE: if building 'universe' with -j* on stable/8 or stable/9
364 it would be better to start the build using bmake, to avoid
365 overloading the machine.
368 Fix a bug that allowed a tracing process (e.g. gdb) to write
369 to a memory-mapped file in the traced process's address space
370 even if neither the traced process nor the tracing process had
371 write access to that file.
374 CVS has been removed from the base system. An exact copy
375 of the code is available from the devel/cvs port.
378 Some people report the following error after the switch to bmake:
380 make: illegal option -- J
381 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
383 *** [buildworld] Error code 2
385 this likely due to an old instance of make in
386 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
387 which src/Makefile will use that blindly, if it exists, so if
388 you see the above error:
390 rm -rf `make -V MAKEPATH`
395 Use bmake by default.
396 Whereas before one could choose to build with bmake via
397 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
398 make. The goal is to remove these knobs for 10-RELEASE.
400 It is worth noting that bmake (like gmake) treats the command
401 line as the unit of failure, rather than statements within the
402 command line. Thus '(cd some/where && dosomething)' is safer
403 than 'cd some/where; dosomething'. The '()' allows consistent
404 behavior in parallel build.
407 Fix a bug that allows NFS clients to issue READDIR on files.
410 The WITHOUT_IDEA option has been removed because
411 the IDEA patent expired.
414 The sysctl which controls TRIM support under ZFS has been renamed
415 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
419 The mergemaster command now uses the default MAKEOBJDIRPREFIX
420 rather than creating it's own in the temporary directory in
421 order allow access to bootstrapped versions of tools such as
422 install and mtree. When upgrading from version of FreeBSD where
423 the install command does not support -l, you will need to
424 install a new mergemaster command if mergemaster -p is required.
425 This can be accomplished with the command (cd src/usr.sbin/mergemaster
429 Legacy ATA stack, disabled and replaced by new CAM-based one since
430 FreeBSD 9.0, completely removed from the sources. Kernel modules
431 atadisk and atapi*, user-level tools atacontrol and burncd are
432 removed. Kernel option `options ATA_CAM` is now permanently enabled
436 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
437 and socketpair(2). Software, in particular Kerberos, may
438 automatically detect and use these during building. The resulting
439 binaries will not work on older kernels.
442 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
443 information, see the respective 20130304 entry).
446 Recent commits to callout(9) changed the size of struct callout,
447 so the KBI is probably heavily disturbed. Also, some functions
448 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
449 by macros. Every kernel module using it won't load, so rebuild
452 The ctl device has been re-enabled in GENERIC for i386 and amd64,
453 but does not initialize by default (because of the new CTL_DISABLE
454 option) to save memory. To re-enable it, remove the CTL_DISABLE
455 option from the kernel config file or set kern.cam.ctl.disable=0
456 in /boot/loader.conf.
459 The ctl device has been disabled in GENERIC for i386 and amd64.
460 This was done due to the extra memory being allocated at system
461 initialisation time by the ctl driver which was only used if
462 a CAM target device was created. This makes a FreeBSD system
463 unusable on 128MB or less of RAM.
466 A new compression method (lz4) has been merged to -HEAD. Please
467 refer to zpool-features(7) for more information.
469 Please refer to the "ZFS notes" section of this file for information
470 on upgrading boot ZFS pools.
473 A BSD-licensed patch(1) variant has been added and is installed
474 as bsdpatch, being the GNU version the default patch.
475 To inverse the logic and use the BSD-licensed one as default,
476 while having the GNU version installed as gnupatch, rebuild
477 and install world with the WITH_BSD_PATCH knob set.
480 Due to the use of the new -l option to install(1) during build
481 and install, you must take care not to directly set the INSTALL
482 make variable in your /etc/make.conf, /etc/src.conf, or on the
483 command line. If you wish to use the -C flag for all installs
484 you may be able to add INSTALL+=-C to /etc/make.conf or
488 The install(1) option -M has changed meaning and now takes an
489 argument that is a file or path to append logs to. In the
490 unlikely event that -M was the last option on the command line
491 and the command line contained at least two files and a target
492 directory the first file will have logs appended to it. The -M
493 option served little practical purpose in the last decade so its
494 use is expected to be extremely rare.
497 After switching to Clang as the default compiler some users of ZFS
498 on i386 systems started to experience stack overflow kernel panics.
499 Please consider using 'options KSTACK_PAGES=4' in such configurations.
502 GEOM_LABEL now mangles label names read from file system metadata.
503 Mangling affect labels containing spaces, non-printable characters,
504 '%' or '"'. Device names in /etc/fstab and other places may need to
508 By default, only the 10 most recent kernel dumps will be saved. To
509 restore the previous behaviour (no limit on the number of kernel dumps
510 stored in the dump directory) add the following line to /etc/rc.conf:
515 With the addition of auditdistd(8), a new auditdistd user is now
516 required during installworld. "mergemaster -p" can be used to
517 add the user prior to installworld, as documented in the handbook.
520 The sin6_scope_id member variable in struct sockaddr_in6 is now
521 filled by the kernel before passing the structure to the userland via
522 sysctl or routing socket. This means the KAME-specific embedded scope
523 id in sin6_addr.s6_addr[2] is always cleared in userland application.
524 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
525 __FreeBSD_version is bumped to 1000025.
528 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
529 This means that the world and kernel will be compiled with clang
530 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
531 and /usr/bin/cpp. To disable this behavior and revert to building
532 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
533 of current may need to bootstrap WITHOUT_CLANG first if the clang
534 build fails (its compatibility window doesn't extend to the 9 stable
538 The IPFIREWALL_FORWARD kernel option has been removed. Its
539 functionality now turned on by default.
542 The ZERO_COPY_SOCKET kernel option has been removed and
543 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
544 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
545 mechanism which is not safe and may result in kernel crashes.
546 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
547 driver supports disposeable external page sized mbuf storage.
548 Proper replacements for both zero-copy mechanisms are under
549 consideration and will eventually lead to complete removal
550 of the two kernel options.
553 The IPv4 network stack has been converted to network byte
554 order. The following modules need to be recompiled together
555 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
556 pf(4), ipfw(4), ng_ipfw(4), stf(4).
559 Support for non-MPSAFE filesystems was removed from VFS. The
560 VFS_VERSION was bumped, all filesystem modules shall be
564 All the non-MPSAFE filesystems have been disconnected from
565 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
566 portalfs, smbfs, xfs.
569 The interface cloning API and ABI has changed. The following
570 modules need to be recompiled together with kernel:
571 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
572 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
573 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
576 The sdhci driver was split in two parts: sdhci (generic SD Host
577 Controller logic) and sdhci_pci (actual hardware driver).
578 No kernel config modifications are required, but if you
579 load sdhc as a module you must switch to sdhci_pci instead.
582 Import the FUSE kernel and userland support into base system.
585 The GNU sort(1) program has been removed since the BSD-licensed
586 sort(1) has been the default for quite some time and no serious
587 problems have been reported. The corresponding WITH_GNU_SORT
591 The pfil(9) API/ABI for AF_INET family has been changed. Packet
592 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
596 The net80211(4) ABI has been changed to allow for improved driver
597 PS-POLL and power-save support. All wireless drivers need to be
598 recompiled to work with the new kernel.
601 The random(4) support for the VIA hardware random number
602 generator (`PADLOCK') is no longer enabled unconditionally.
603 Add the padlock_rng device in the custom kernel config if
604 needed. The GENERIC kernels on i386 and amd64 do include the
605 device, so the change only affects the custom kernel
609 The pf(4) packet filter ABI has been changed. pfctl(8) and
610 snmp_pf module need to be recompiled to work with new kernel.
613 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
614 to -HEAD. Pools that have empty_bpobj in active state can not be
615 imported read-write with ZFS implementations that do not support
616 this feature. For more information read the zpool-features(5)
620 The sparc64 ZFS loader has been changed to no longer try to auto-
621 detect ZFS providers based on diskN aliases but now requires these
622 to be explicitly listed in the OFW boot-device environment variable.
625 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
626 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
627 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
630 The following sysctls and tunables have been renamed for consistency
631 with other variables:
632 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
633 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
636 The sort utility has been replaced with BSD sort. For now, GNU sort
637 is also available as "gnusort" or the default can be set back to
638 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
639 installed as "bsdsort".
642 A new version of ZFS (pool version 5000) has been merged to -HEAD.
643 Starting with this version the old system of ZFS pool versioning
644 is superseded by "feature flags". This concept enables forward
645 compatibility against certain future changes in functionality of ZFS
646 pools. The first read-only compatible "feature flag" for ZFS pools
647 is named "com.delphix:async_destroy". For more information
648 read the new zpool-features(5) manual page.
649 Please refer to the "ZFS notes" section of this file for information
650 on upgrading boot ZFS pools.
653 The malloc(3) implementation embedded in libc now uses sources imported
654 as contrib/jemalloc. The most disruptive API change is to
655 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
656 delete it prior to installworld, and optionally re-create it using the
657 new format after rebooting. See malloc.conf(5) for details
658 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
662 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
663 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
664 now spelled mips. This is to aid compatibility with third-party
665 software that expects this naming scheme in uname(3). Little-endian
666 settings are unchanged. If you are updating a big-endian mips64 machine
667 from before this change, you may need to set MACHINE_ARCH=mips64 in
668 your environment before the new build system will recognize your machine.
671 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
675 Now unix domain sockets behave "as expected" on nullfs(5). Previously
676 nullfs(5) did not pass through all behaviours to the underlying layer,
677 as a result if we bound to a socket on the lower layer we could connect
678 only to the lower path; if we bound to the upper layer we could connect
679 only to the upper path. The new behavior is one can connect to both the
680 lower and the upper paths regardless what layer path one binds to.
683 The getifaddrs upgrade path broken with 20111215 has been restored.
684 If you have upgraded in between 20111215 and 20120209 you need to
685 recompile libc again with your kernel. You still need to recompile
686 world to be able to configure CARP but this restriction already
690 The set_rcvar() function has been removed from /etc/rc.subr. All
691 base and ports rc.d scripts have been updated, so if you have a
692 port installed with a script in /usr/local/etc/rc.d you can either
693 hand-edit the rcvar= line, or reinstall the port.
695 An easy way to handle the mass-update of /etc/rc.d:
696 rm /etc/rc.d/* && mergemaster -i
699 panic(9) now stops other CPUs in the SMP systems, disables interrupts
700 on the current CPU and prevents other threads from running.
701 This behavior can be reverted using the kern.stop_scheduler_on_panic
703 The new behavior can be incompatible with kern.sync_on_panic.
706 The carp(4) facility has been changed significantly. Configuration
707 of the CARP protocol via ifconfig(8) has changed, as well as format
708 of CARP events submitted to devd(8) has changed. See manual pages
709 for more information. The arpbalance feature of carp(4) is currently
710 not supported anymore.
712 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
713 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
714 need to be recompiled.
717 The acpi_wmi(4) status device /dev/wmistat has been renamed to
721 The option VFS_ALLOW_NONMPSAFE option has been added in order to
722 explicitely support non-MPSAFE filesystems.
723 It is on by default for all supported platform at this present
727 The broken amd(4) driver has been replaced with esp(4) in the amd64,
728 i386 and pc98 GENERIC kernel configuration files.
731 sysinstall has been removed
734 The stable/9 branch created in subversion. This corresponds to the
735 RELENG_9 branch in CVS.
738 This commit modifies vfs_register() so that it uses a hash
739 calculation to set vfc_typenum, which is enabled by default.
740 The first time a system is booted after this change, the
741 vfc_typenum values will change for all file systems. The
742 main effect of this is a change to the NFS server file handles
743 for file systems that use vfc_typenum in their fsid, such as ZFS.
744 It will, however, prevent vfc_typenum from changing when file
745 systems are loaded in a different order for subsequent reboots.
746 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
747 until you are ready to remount all NFS clients after a reboot.
750 Bump the shared library version numbers for libraries that
751 do not use symbol versioning, have changed the ABI compared
752 to stable/8 and which shared library version was not bumped.
753 Done as part of 9.0-RELEASE cycle.
756 During the merge of Capsicum features, the fget(9) KPI was modified.
757 This may require the rebuilding of out-of-tree device drivers --
758 issues have been reported specifically with the nVidia device driver.
759 __FreeBSD_version is bumped to 900041.
761 Also, there is a period between 20110811 and 20110814 where the
762 special devices /dev/{stdin,stdout,stderr} did not work correctly.
763 Building world from a kernel during that window may not work.
766 The packet filter (pf) code has been updated to OpenBSD 4.5.
767 You need to update userland tools to be in sync with kernel.
768 This update breaks backward compatibility with earlier pfsync(4)
769 versions. Care must be taken when updating redundant firewall setups.
772 The following sysctls and tunables are retired on x86 platforms:
774 machdep.hlt_logical_cpus
775 The following sysctl is retired:
776 machdep.hyperthreading_allowed
777 The sysctls were supposed to provide a way to dynamically offline and
778 online selected CPUs on x86 platforms, but the implementation has not
779 been reliable especially with SCHED_ULE scheduler.
780 machdep.hyperthreading_allowed tunable is still available to ignore
781 hyperthreading CPUs at OS level.
782 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
783 where X is an APIC ID of a CPU. Be advised, though, that disabling
784 CPUs in non-uniform fashion will result in non-uniform topology and
785 may lead to sub-optimal system performance with SCHED_ULE, which is
789 cpumask_t type is retired and cpuset_t is used in order to describe
793 Changes to ifconfig(8) for dynamic address family detection mandate
794 that you are running a kernel of 20110525 or later. Make sure to
795 follow the update procedure to boot a new kernel before installing
799 Support for sun4v architecture is officially dropped
802 Several KPI breaking changes have been committed to the mii(4) layer,
803 the PHY drivers and consequently some Ethernet drivers using mii(4).
804 This means that miibus.ko and the modules of the affected Ethernet
805 drivers need to be recompiled.
807 Note to kernel developers: Given that the OUI bit reversion problem
808 was fixed as part of these changes all mii(4) commits related to OUIs,
809 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
810 handling, no longer can be merged verbatim to stable/8 and previous
814 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
815 into their kernel configurations along with 'device pci'.
818 The default NFS client is now the new NFS client, so fstype "newnfs"
819 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
820 Although mounts via fstype "nfs" will usually work without userland
821 changes, it is recommended that the mount(8) and mount_nfs(8)
822 commands be rebuilt from sources and that a link to mount_nfs called
823 mount_oldnfs be created. The new client is compiled into the
824 kernel with "options NFSCL" and this is needed for diskless root
825 file systems. The GENERIC kernel configs have been changed to use
826 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
827 To use the regular/old client, you can "mount -t oldnfs ...". For
828 a diskless root file system, you must also include a line like:
830 vfs.root.mountfrom="oldnfs:"
832 in the boot/loader.conf on the root fs on the NFS server to make
833 a diskless root fs use the old client.
836 The GENERIC kernels for all architectures now default to the new
837 CAM-based ATA stack. It means that all legacy ATA drivers were
838 removed and replaced by respective CAM drivers. If you are using
839 ATA device names in /etc/fstab or other places, make sure to update
840 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
841 where 'Y's are the sequential numbers starting from zero for each type
842 in order of detection, unless configured otherwise with tunables,
843 see cam(4)). There will be symbolic links created in /dev/ to map
844 old adX devices to the respective adaY. They should provide basic
845 compatibility for file systems mounting in most cases, but they do
846 not support old user-level APIs and do not have respective providers
847 in GEOM. Consider using updated management tools with new device names.
849 It is possible to load devices ahci, ata, siis and mvs as modules,
850 but option ATA_CAM should remain in kernel configuration to make ata
851 module work as CAM driver supporting legacy ATA controllers. Device ata
852 still can be used in modular fashion (atacore + ...). Modules atadisk
853 and atapi* are not used and won't affect operation in ATA_CAM mode.
854 Note that to use CAM-based ATA kernel should include CAM devices
855 scbus, pass, da (or explicitly ada), cd and optionally others. All of
856 them are parts of the cam module.
858 ataraid(4) functionality is now supported by the RAID GEOM class.
859 To use it you can load geom_raid kernel module and use graid(8) tool
860 for management. Instead of /dev/arX device names, use /dev/raid/rX.
862 No kernel config options or code have been removed, so if a problem
863 arises, please report it and optionally revert to the old ATA stack.
864 In order to do it you can remove from the kernel config:
869 , and instead add back:
870 device atadisk # ATA disk drives
871 device ataraid # ATA RAID drives
872 device atapicd # ATAPI CDROM drives
873 device atapifd # ATAPI floppy drives
874 device atapist # ATAPI tape drives
877 The default NFS server has been changed to the new server, which
878 was referred to as the experimental server. If you need to switch
879 back to the old NFS server, you must now put the "-o" option on
880 both the mountd and nfsd commands. This can be done using the
881 mountd_flags and nfs_server_flags rc.conf variables until an
882 update to the rc scripts is committed, which is coming soon.
885 The GNU Objective-C runtime library (libobjc), and other Objective-C
886 related components have been removed from the base system. If you
887 require an Objective-C library, please use one of the available ports.
890 ath(4) has been split into bus- and device- modules. if_ath contains
891 the HAL, the TX rate control and the network device code. if_ath_pci
892 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
893 contains the AHB glue. Users need to load both if_ath_pci and if_ath
894 in order to use ath on everything else.
896 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
897 need to load if_ath and if_ath_pci for ath(4) operation.
900 As part of the replacement of sysinstall, the process of building
901 release media has changed significantly. For details, please re-read
902 release(7), which has been updated to reflect the new build process.
905 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
906 is the last available version under GPLv2. It brings a number of new
907 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
908 4.1 and SSE 4.2), better support for powerpc64, a number of new
909 directives, and lots of other small improvements. See the ChangeLog
910 file in contrib/binutils for the full details.
913 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
914 compliant, and will now use half of hash for authentication.
915 This will break interoperability with all stacks (including all
916 actual FreeBSD versions) who implement
917 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
919 The only workaround with such peers is to use another HMAC
920 algorithm for IPsec ("phase 2") authentication.
923 Remove the uio_yield prototype and symbol. This function has
924 been misnamed since it was introduced and should not be
925 globally exposed with this name. The equivalent functionality
926 is now available using kern_yield(curthread->td_user_pri).
927 The function remains undocumented.
930 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
931 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
932 for scalar sysctls is defined but disabled. Code that needs
933 UQUAD to pass the type checking that must compile on older
934 systems where the define is not present can check against
935 __FreeBSD_version >= 900030.
937 The system dialog(1) has been replaced with a new version previously
938 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
939 with the previous version, but the libdialog associated with it has
940 a largely incompatible API. As such, the original version of libdialog
941 will be kept temporarily as libodialog, until its base system consumers
942 are replaced or updated. Bump __FreeBSD_version to 900030.
945 If you are trying to run make universe on a -stable system, and you get
946 the following warning:
947 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
948 unknown. config(8) likely too old."
949 or something similar to it, then you must upgrade your -stable system
950 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
951 stable/8) or build the config from the latest stable/8 branch and
952 install it on your system.
954 Prior to this date, building a current universe on 8-stable system from
955 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
956 error in the first kernel build phase. A new config on those old
957 systems will fix that problem for older versions of -current.
960 The TCP stack has been modified to allow Khelp modules to interact with
961 it via helper hook points and store per-connection data in the TCP
962 control block. Bump __FreeBSD_version to 900029. User space tools that
963 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
967 Generic IEEE 802.3 annex 31B full duplex flow control support has been
968 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
969 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
970 to take advantage of it instead of using custom implementations. This
971 means that these drivers now no longer unconditionally advertise
972 support for flow control but only do so if flow control is a selected
973 media option. This was implemented in the generic support that way in
974 order to allow flow control to be switched on and off via ifconfig(8)
975 with the PHY specific default to typically off in order to protect
976 from unwanted effects. Consequently, if you used flow control with
977 one of the above mentioned drivers you now need to explicitly enable
979 ifconfig bge0 media auto mediaopt flowcontrol
981 Along with the above mentioned changes generic support for setting
982 1000baseT master mode also has been added and brgphy(4), ciphy(4),
983 e1000phy(4) as well as ip1000phy(4) have been converted to take
984 advantage of it. This means that these drivers now no longer take the
985 link0 parameter for selecting master mode but the master media option
986 has to be used instead, for example like in the following:
987 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
989 Selection of master mode now is also available with all other PHY
990 drivers supporting 1000baseT.
993 The TCP stack has received a significant update to add support for
994 modularised congestion control and generally improve the clarity of
995 congestion control decisions. Bump __FreeBSD_version to 900025. User
996 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
997 sockstat) need to be recompiled.
1000 The man(1) utility has been replaced by a new version that no longer
1001 uses /etc/manpath.config. Please consult man.conf(5) for how to
1002 migrate local entries to the new format.
1005 The copyright strings printed by login(1) and sshd(8) at the time of a
1006 new connection have been removed to follow other operating systems and
1010 A workaround for a fixed ld bug has been removed in kernel code,
1011 so make sure that your system ld is built from sources after
1012 revision 210245 from 2010-07-19 (r211583 if building head kernel
1013 on stable/8, r211584 for stable/7; both from 2010-08-21).
1014 A symptom of incorrect ld version is different addresses for
1015 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1018 The $ipv6_prefer variable in rc.conf(5) has been split into
1019 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1021 The $ip6addrctl_policy is a variable to choose a pre-defined
1022 address selection policy set by ip6addrctl(8). A value
1023 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1026 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1027 flag (see an entry of 20090926) is set on an interface with no
1028 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1029 security reason. If you want IPv6 link-local address on all
1030 interfaces by default, set this to "YES".
1032 The old ipv6_prefer="YES" is equivalent to
1033 ipv6_activate_all_interfaces="YES" and
1034 ip6addrctl_policy="ipv6_prefer".
1037 DTrace has grown support for userland tracing. Due to this, DTrace is
1038 now i386 and amd64 only.
1039 dtruss(1) is now installed by default on those systems and a new
1040 kernel module is needed for userland tracing: fasttrap.
1041 No changes to your kernel config file are necessary to enable
1042 userland tracing, but you might consider adding 'STRIP=' and
1043 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1044 to have informative userland stack traces in DTrace (ustack).
1047 The acpi_aiboost(4) driver has been removed in favor of the new
1048 aibs(4) driver. You should update your kernel configuration file.
1051 BSD grep has been imported to the base system and it is built by
1052 default. It is completely BSD licensed, highly GNU-compatible, uses
1053 less memory than its GNU counterpart and has a small codebase.
1054 However, it is slower than its GNU counterpart, which is mostly
1055 noticeable for larger searches, for smaller ones it is measurable
1056 but not significant. The reason is complex, the most important factor
1057 is that we lack a modern and efficient regex library and GNU
1058 overcomes this by optimizing the searches internally. Future work
1059 on improving the regex performance is planned, for the meantime,
1060 users that need better performance, can build GNU grep instead by
1061 setting the WITH_GNU_GREP knob.
1064 Due to the import of powerpc64 support, all existing powerpc kernel
1065 configuration files must be updated with a machine directive like this:
1066 machine powerpc powerpc
1068 In addition, an updated config(8) is required to build powerpc kernels
1072 A new version of ZFS (version 15) has been merged to -HEAD.
1073 This version uses a python library for the following subcommands:
1074 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1075 For full functionality of these commands the following port must
1076 be installed: sysutils/py-zfs
1079 'vm_page's are now hashed by physical address to an array of mutexes.
1080 Currently this is only used to serialize access to hold_count. Over
1081 time the page queue mutex will be peeled away. This changes the size
1082 of pmap on every architecture. And requires all callers of vm_page_hold
1083 and vm_page_unhold to be updated.
1086 WITH_CTF can now be specified in src.conf (not recommended, there
1087 are some problems with static executables), make.conf (would also
1088 affect ports which do not use GNU make and do not override the
1089 compile targets) or in the kernel config (via "makeoptions
1091 When WITH_CTF was specified there before this was silently ignored,
1092 so make sure that WITH_CTF is not used in places which could lead
1093 to unwanted behavior.
1096 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1097 to allow 32-bit compatibility on non-x86 platforms. All kernel
1098 configurations on amd64 and ia64 platforms using these options must
1099 be modified accordingly.
1102 The utmp user accounting database has been replaced with utmpx,
1103 the user accounting interface standardized by POSIX.
1104 Unfortunately the semantics of utmp and utmpx don't match,
1105 making it practically impossible to support both interfaces.
1106 The user accounting database is used by tools like finger(1),
1107 last(1), talk(1), w(1) and ac(8).
1109 All applications in the base system use utmpx. This means only
1110 local binaries (e.g. from the ports tree) may still use these
1111 utmp database files. These applications must be rebuilt to make
1114 After the system has been upgraded, it is safe to remove the old
1115 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1116 assuming their contents is of no importance anymore. Old wtmp
1117 databases can only be used by last(1) and ac(8) after they have
1118 been converted to the new format using wtmpcvt(1).
1121 Introduce the kernel thread "deadlock resolver" (which can be enabled
1122 via the DEADLKRES option, see NOTES for more details) and the
1123 sleepq_type() function for sleepqueues.
1126 The rc.firewall and rc.firewall6 were unified, and
1127 rc.firewall6 and rc.d/ip6fw were removed.
1128 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1129 variables are obsoleted. Instead, the following new rc
1130 variables are added to rc.d/ipfw:
1132 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1133 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1134 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1136 The meanings correspond to the relevant IPv4 variables.
1142 The default terminal emulation for syscons(4) has been changed
1143 from cons25 to xterm on all platforms except pc98. This means
1144 that the /etc/ttys file needs to be updated to ensure correct
1145 operation of applications on the console.
1147 The terminal emulation style can be toggled per window by using
1148 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1149 options can be used to change the compile-time default back to
1152 To prevent graphical artifacts, make sure the TERM environment
1153 variable is set to match the terminal emulation that is being
1154 performed by syscons(4).
1157 The layout of the structure ieee80211req_scan_result has changed.
1158 Applications that require wireless scan results (e.g. ifconfig(8))
1159 from net80211 need to be recompiled.
1161 Applications such as wpa_supplicant(8) may require a full world
1162 build without using NO_CLEAN in order to get synchronized with the
1166 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1167 There's one kernel module for each firmware. Adding "device iwnfw"
1168 to the kernel configuration file means including all three firmware
1169 images inside the kernel. If you want to include just the one for
1170 your wireless card, use the devices iwn4965fw, iwn5000fw or
1174 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1175 into rc.d/netif. The changes are the following:
1177 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1178 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1179 Note that both variables need the "inet6" keyword at the head.
1181 Do not set $ipv6_network_interfaces manually if you do not
1182 understand what you are doing. It is not needed in most cases.
1184 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1187 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1188 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1190 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1191 all configured interfaces have "inet6 accept_rtadv" in the
1192 $ifconfig_IF_ipv6. These are for backward compatibility.
1194 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1195 functionality of interfaces with no corresponding
1196 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1197 and the default address selection policy of ip6addrctl(8)
1198 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1199 Note that if you want to configure IPv6 functionality on the
1200 disabled interfaces after boot, first you need to clear the flag by
1201 using ifconfig(8) like:
1203 ifconfig em0 inet6 -ifdisabled
1205 If YES, the default address selection policy is set as
1208 The default value of $ipv6_prefer is NO.
1210 4. If your system need to receive Router Advertisement messages,
1211 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1212 scripts automatically invoke rtsol(8) when the interface becomes
1213 UP. The Router Advertisement messages are used for SLAAC
1214 (State-Less Address AutoConfiguration).
1217 802.11s D3.03 support was committed. This is incompatible with the
1218 previous code, which was based on D3.0.
1221 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1222 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1223 control whether accepting Router Advertisement messages or not.
1224 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1225 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1226 The ifconfig(8) utility now supports these flags.
1229 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1230 mount(8) and -a option for df(1) to see them.
1233 The old tunable hw.bus.devctl_disable has been superseded by
1234 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1235 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1239 Remove the option STOP_NMI. The default action is now to use NMI only
1240 for KDB via the newly introduced function stop_cpus_hard() and
1241 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1244 The stable/8 branch created in subversion. This corresponds to the
1245 RELENG_8 branch in CVS.
1248 Bump the shared library version numbers for all libraries that do not
1249 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1250 __FreeBSD_version to 800105.
1253 Due to changes in the implementation of virtual network stack support,
1254 all network-related kernel modules must be recompiled. As this change
1255 breaks the ABI, bump __FreeBSD_version to 800104.
1258 The TOE interface to the TCP syncache has been modified to remove
1259 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1260 The cxgb driver is the only TOE consumer affected by this change, and
1261 needs to be recompiled along with the kernel. As this change breaks
1262 the ABI, bump __FreeBSD_version to 800103.
1265 Padding has been added to struct tcpcb, sackhint and tcpstat in
1266 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1267 maintaining the ABI. However, this change breaks the ABI, so bump
1268 __FreeBSD_version to 800102. User space tools that rely on the size of
1269 any of these structs (e.g. sockstat) need to be recompiled.
1272 The NFS_LEGACYRPC option has been removed along with the old kernel
1273 RPC implementation that this option selected. Kernel configurations
1274 may need to be adjusted.
1277 The network interface device nodes at /dev/net/<interface> have been
1278 removed. All ioctl operations can be performed the normal way using
1279 routing sockets. The kqueue functionality can generally be replaced
1280 with routing sockets.
1283 The documentation from the FreeBSD Documentation Project (Handbook,
1284 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1285 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1288 The ABI of various structures related to the SYSV IPC API have been
1289 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1290 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1294 Layout of struct vnet has changed as routing related variables were
1295 moved to their own Vimage module. Modules need to be recompiled. Bump
1296 __FreeBSD_version to 800099.
1299 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1300 respectively. As long as no more than 16 groups per process are used,
1301 no changes should be visible. When more than 16 groups are used, old
1302 binaries may fail if they call getgroups() or getgrouplist() with
1303 statically sized storage. Recompiling will work around this, but
1304 applications should be modified to use dynamically allocated storage
1305 for group arrays as POSIX.1-2008 does not cap an implementation's
1306 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1308 NFS and portalfs mounts may also be affected as the list of groups is
1309 truncated to 16. Users of NFS who use more than 16 groups, should
1310 take care that negative group permissions are not used on the exported
1311 file systems as they will not be reliable unless a GSSAPI based
1312 authentication method is used.
1315 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1316 option compiles in the support for adaptive spinning for lockmgrs
1317 which want to enable it. The lockinit() function now accepts the flag
1318 LK_ADAPTIVE in order to make the lock object subject to adaptive
1319 spinning when both held in write and read mode.
1322 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1323 changed. User applications that use this ioctl need to be rebuilt.
1326 The layout of struct thread has changed. Kernel and modules need to
1330 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1331 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1334 window(1) has been removed from the base system. It can now be
1335 installed from ports. The port is called misc/window.
1338 The way we are storing and accessing `routing table' entries has
1339 changed. Programs reading the FIB, like netstat, need to be
1343 A new netisr implementation has been added for FreeBSD 8. Network
1344 file system modules, such as igmp, ipdivert, and others, should be
1346 Bump __FreeBSD_version to 800096.
1349 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1353 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1354 Bump __FreeBSD_version to 800094.
1357 Add mnt_xflag field to 'struct mount'. File system modules need to be
1359 Bump __FreeBSD_version to 800093.
1362 The compiling option ADAPTIVE_SX has been retired while it has been
1363 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1364 The KPI for sx_init_flags() changes as accepting flags:
1365 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1366 been introduced in order to handle the reversed logic.
1367 Bump __FreeBSD_version to 800092.
1370 Add support for hierarchical jails. Remove global securelevel.
1371 Bump __FreeBSD_version to 800091.
1374 The layout of struct vnet_net has changed, therefore modules
1376 Bump __FreeBSD_version to 800090.
1379 The newly imported zic(8) produces a new format in the output. Please
1380 run tzsetup(8) to install the newly created data to /etc/localtime.
1383 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1384 hw.usb.* and is now consistent again with previous releases.
1387 802.11 monitor mode support was revised and driver api's were changed.
1388 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1389 of DLT_IEEE802_11. No user-visible data structures were changed but
1390 applications that use DLT_IEEE802_11 may require changes.
1391 Bump __FreeBSD_version to 800088.
1394 The layout of the following structs has changed: sysctl_oid,
1395 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1396 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1397 panics may be experienced. World rebuild is required for
1398 correctly checking networking state from userland.
1399 Bump __FreeBSD_version to 800085.
1402 MLDv2 and Source-Specific Multicast (SSM) have been merged
1403 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1404 The implementation of SSM within FreeBSD's IPv6 stack closely
1405 follows the IPv4 implementation.
1407 For kernel developers:
1409 * The most important changes are that the ip6_output() and
1410 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1411 and this lock has been downgraded to a non-recursive mutex.
1413 * As with the changes to the IPv4 stack to support SSM, filtering
1414 of inbound multicast traffic must now be performed by transport
1415 protocols within the IPv6 stack. This does not apply to TCP and
1416 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1418 * The KPIs used by IPv6 multicast are similar to those used by
1419 the IPv4 stack, with the following differences:
1420 * im6o_mc_filter() is analogous to imo_multicast_filter().
1421 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1422 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1423 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1424 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1425 for MLDv1 have an additional 'timer' argument which is used to
1426 jitter the initial membership report for the solicited-node
1427 multicast membership on-link.
1428 * This is not strictly needed for MLDv2, which already jitters
1429 its report transmissions. However, the 'timer' argument is
1430 preserved in case MLDv1 is active on the interface.
1432 * The KAME linked-list based IPv6 membership implementation has
1433 been refactored to use a vector similar to that used by the IPv4
1435 Code which maintains a list of its own multicast memberships
1436 internally, e.g. carp, has been updated to reflect the new
1439 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1440 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1441 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1442 implementation constraint which needs to be addressed in HEAD.
1444 For application developers:
1446 * The changes are broadly similar to those made for the IPv4
1449 * The use of IPv4 and IPv6 multicast socket options on the same
1450 socket, using mapped addresses, HAS NOT been tested or supported.
1452 * There are a number of issues with the implementation of various
1453 IPv6 multicast APIs which need to be resolved in the API surface
1454 before the implementation is fully compatible with KAME userland
1455 use, and these are mostly to do with interface index treatment.
1457 * The literature available discusses the use of either the delta / ASM
1458 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1459 using setsourcefilter(3)/getsourcefilter(3). For more information
1460 please refer to RFC 3768, 'Socket Interface Extensions for
1461 Multicast Source Filters'.
1463 * Applications which use the published RFC 3678 APIs should be fine.
1465 For systems administrators:
1467 * The mtest(8) utility has been refactored to support IPv6, in
1468 addition to IPv4. Interface addresses are no longer accepted
1469 as arguments, their names must be used instead. The utility
1470 will map the interface name to its first IPv4 address as
1471 returned by getifaddrs(3).
1473 * The ifmcstat(8) utility has also been updated to print the MLDv2
1474 endpoint state and source filter lists via sysctl(3).
1476 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1477 loopback of IPv6 multicast datagrams by default; it defaults to 1
1478 to preserve the existing behaviour. Disabling multicast loopback is
1479 recommended for optimal system performance.
1481 * The IPv6 MROUTING code has been changed to examine this sysctl
1482 instead of attempting to perform a group lookup before looping
1483 back forwarded datagrams.
1485 Bump __FreeBSD_version to 800084.
1488 Implement low-level Bluetooth HCI API.
1489 Bump __FreeBSD_version to 800083.
1492 The layout of struct malloc_type, used by modules to register new
1493 memory allocation types, has changed. Most modules will need to
1494 be rebuilt or panics may be experienced.
1495 Bump __FreeBSD_version to 800081.
1498 Anticipate overflowing inp_flags - add inp_flags2.
1499 This changes most offsets in inpcb, so checking v4 connection
1500 state will require a world rebuild.
1501 Bump __FreeBSD_version to 800080.
1504 Add an llentry to struct route and struct route_in6. Modules
1505 embedding a struct route will need to be recompiled.
1506 Bump __FreeBSD_version to 800079.
1509 The size of rt_metrics_lite and by extension rtentry has changed.
1510 Networking administration apps will need to be recompiled.
1511 The route command now supports show as an alias for get, weighting
1512 of routes, sticky and nostick flags to alter the behavior of stateful
1514 Bump __FreeBSD_version to 800078.
1517 Do not use Giant for kbdmux(4) locking. This is wrong and
1518 apparently causing more problems than it solves. This will
1519 re-open the issue where interrupt handlers may race with
1520 kbdmux(4) in polling mode. Typical symptoms include (but
1521 not limited to) duplicated and/or missing characters when
1522 low level console functions (such as gets) are used while
1523 interrupts are enabled (for example geli password prompt,
1524 mountroot prompt etc.). Disabling kbdmux(4) may help.
1527 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1528 kernel modules referencing any of the above need to be recompiled.
1529 Bump __FreeBSD_version to 800075.
1532 GEOM_PART has become the default partition slicer for storage devices,
1533 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1534 introduces some changes:
1536 MSDOS/EBR: the devices created from MSDOS extended partition entries
1537 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1538 to devices with offset-based names. fstabs may need to be modified.
1540 BSD: the "geometry does not match label" warning is harmless in most
1541 cases but it points to problems in file system misalignment with
1542 disk geometry. The "c" partition is now implicit, covers the whole
1543 top-level drive and cannot be (mis)used by users.
1545 General: Kernel dumps are now not allowed to be written to devices
1546 whose partition types indicate they are meant to be used for file
1547 systems (or, in case of MSDOS partitions, as something else than
1550 Most of these changes date approximately from 200812.
1553 The uscanner(4) driver has been removed from the kernel. This follows
1554 Linux removing theirs in 2.6 and making libusb the default interface
1555 (supported by sane).
1558 The multicast forwarding code has been cleaned up. netstat(1)
1559 only relies on KVM now for printing bandwidth upcall meters.
1560 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1561 ip6_mroute_mod respectively. The config(5) options for statically
1562 compiling this code remain the same, i.e. 'options MROUTING'.
1565 Support for the IFF_NEEDSGIANT network interface flag has been
1566 removed, which means that non-MPSAFE network device drivers are no
1567 longer supported. In particular, if_ar, if_sr, and network device
1568 drivers from the old (legacy) USB stack can no longer be built or
1572 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1573 a bunch of new language catalog files have also been added.
1574 This means that some common libc messages are now localized and
1575 they depend on the LC_MESSAGES environmental variable.
1578 The k8temp(4) driver has been renamed to amdtemp(4) since
1579 support for Family 10 and Family 11 CPU families was added.
1582 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1583 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1585 For kernel developers, the most important changes are that the
1586 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1587 and this lock has been downgraded to a non-recursive mutex.
1589 Transport protocols (UDP, Raw IP) are now responsible for filtering
1590 inbound multicast traffic according to group membership and source
1591 filters. The imo_multicast_filter() KPI exists for this purpose.
1592 Transports which do not use multicast (SCTP, TCP) already reject
1593 multicast by default. Forwarding and receive performance may improve
1594 as a mutex acquisition is no longer needed in the ip_input()
1595 low-level input path. in_addmulti() and in_delmulti() are shimmed
1596 to new KPIs which exist to support SSM in-kernel.
1598 For application developers, it is recommended that loopback of
1599 multicast datagrams be disabled for best performance, as this
1600 will still cause the lock to be taken for each looped-back
1601 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1602 be tuned to 0 to disable loopback by default; it defaults to 1
1603 to preserve the existing behaviour.
1605 For systems administrators, to obtain best performance with
1606 multicast reception and multiple groups, it is always recommended
1607 that a card with a suitably precise hash filter is used. Hash
1608 collisions will still result in the lock being taken within the
1609 transport protocol input path to check group membership.
1611 If deploying FreeBSD in an environment with IGMP snooping switches,
1612 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1613 enabled; this forces 224.0.0.0/24 group membership to be announced
1616 The size of 'struct igmpstat' has changed; netstat needs to be
1617 recompiled to reflect this.
1618 Bump __FreeBSD_version to 800070.
1621 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1622 updated to use it. This requires a buildworld/installworld in order to
1623 update the library and dependencies (usbconfig, etc). Its advisable to
1624 rebuild all ports which uses libusb. More specific directions are given
1625 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1626 libusb are no longer required and can be removed.
1629 A workaround is committed to allow the creation of System V shared
1630 memory segment of size > 2 GB on the 64-bit architectures.
1631 Due to a limitation of the existing ABI, the shm_segsz member
1632 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1633 wrong for large segments. Note that limits must be explicitly
1634 raised to allow such segments to be created.
1637 The layout of struct ifnet has changed, requiring a rebuild of all
1638 network device driver modules.
1641 The /dev handling for the new USB stack has changed, a
1642 buildworld/installworld is required for libusb20.
1645 The new USB2 stack has now been permanently moved in and all kernel and
1646 module names reverted to their previous values (eg, usb, ehci, ohci,
1647 ums, ...). The old usb stack can be compiled in by prefixing the name
1648 with the letter 'o', the old usb modules have been removed.
1649 Updating entry 20090216 for xorg and 20090215 for libmap may still
1653 The rc.conf(5) option if_up_delay has been renamed to
1654 defaultroute_delay to better reflect its purpose. If you have
1655 customized this setting in /etc/rc.conf you need to update it to
1659 xorg 7.4 wants to configure its input devices via hald which does not
1660 yet work with USB2. If the keyboard/mouse does not work in xorg then
1662 Option "AllowEmptyInput" "off"
1663 to your ServerLayout section. This will cause X to use the configured
1664 kbd and mouse sections from your xorg.conf.
1667 The GENERIC kernels for all architectures now default to the new USB2
1668 stack. No kernel config options or code have been removed so if a
1669 problem arises please report it and optionally revert to the old USB
1670 stack. If you are loading USB kernel modules or have a custom kernel
1671 that includes GENERIC then ensure that usb names are also changed over,
1672 eg uftdi -> usb2_serial_ftdi.
1674 Older programs linked against the ports libusb 0.1 need to be
1675 redirected to the new stack's libusb20. /etc/libmap.conf can
1677 # Map old usb library to new one for usb2 stack
1678 libusb-0.1.so.8 libusb20.so.1
1681 All USB ethernet devices now attach as interfaces under the name ueN
1682 (eg. ue0). This is to provide a predictable name as vendors often
1683 change usb chipsets in a product without notice.
1686 The ichsmb(4) driver has been changed to require SMBus slave
1687 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1688 All of the other SMBus controller drivers require left-justified
1689 slave addresses, so this change makes all the drivers provide the
1693 INET6 statistics (struct ip6stat) was updated.
1694 netstat(1) needs to be recompiled.
1697 NTFS has been removed from GENERIC kernel on amd64 to match
1698 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1699 will load ntfs.ko module automatically when NTFS support is
1700 actually needed, unless ntfs.ko is not installed or security
1701 level prohibits loading kernel modules. If either is the case,
1702 "options NTFS" has to be added into kernel config.
1705 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1706 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1707 800061. User space tools that rely on the size of struct tcpcb in
1708 tcp_var.h (e.g. sockstat) need to be recompiled.
1711 ng_tty(4) module updated to match the new TTY subsystem.
1712 Due to API change, user-level applications must be updated.
1713 New API support added to mpd5 CVS and expected to be present
1714 in next mpd5.3 release.
1717 With __FreeBSD_version 800060 the makefs tool is part of
1718 the base system (it was a port).
1721 The afdata and ifnet locks have been changed from mutexes to
1722 rwlocks, network modules will need to be re-compiled.
1725 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1726 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1727 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1728 architecture and 40 bytes on 64-bit architecture. The userland
1729 applications "arp" and "ndp" have been updated accordingly.
1730 The output from "netstat -r" shows only routing entries and
1731 none of the L2 information.
1734 __FreeBSD_version 800057 marks the switchover from the
1735 binary ath hal to source code. Users must add the line:
1737 options AH_SUPPORT_AR5416
1739 to their kernel config files when specifying:
1743 The ath_hal module no longer exists; the code is now compiled
1744 together with the driver in the ath module. It is now
1745 possible to tailor chip support (i.e. reduce the set of chips
1746 and thereby the code size); consult ath_hal(4) for details.
1749 __FreeBSD_version 800054 adds memory barriers to
1750 <machine/atomic.h>, new interfaces to ifnet to facilitate
1751 multiple hardware transmit queues for cards that support
1752 them, and a lock-less ring-buffer implementation to
1753 enable drivers to more efficiently manage queueing of
1757 A new version of ZFS (version 13) has been merged to -HEAD.
1758 This version has zpool attribute "listsnapshots" off by
1759 default, which means "zfs list" does not show snapshots,
1760 and is the same as Solaris behavior.
1763 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1766 The uhci, ohci, ehci and slhci USB Host controller drivers have
1767 been put into separate modules. If you load the usb module
1768 separately through loader.conf you will need to load the
1769 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1770 controller add the following to loader.conf:
1776 The ABI used by the PMC toolset has changed. Please keep
1777 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1781 atapci kernel module now includes only generic PCI ATA
1782 driver. AHCI driver moved to ataahci kernel module.
1783 All vendor-specific code moved into separate kernel modules:
1784 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1785 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1786 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1787 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1790 The TTY subsystem of the kernel has been replaced by a new
1791 implementation, which provides better scalability and an
1792 improved driver model. Most common drivers have been migrated to
1793 the new TTY subsystem, while others have not. The following
1794 drivers have not yet been ported to the new TTY layer:
1797 cy, digi, rc, rp, sio
1803 ng_h4, ng_tty, ppp, sl, snp
1805 Adding these drivers to your kernel configuration file shall
1806 cause compilation to fail.
1809 ntpd has been upgraded to 4.2.4p5.
1812 OpenSSH has been upgraded to 5.1p1.
1814 For many years, FreeBSD's version of OpenSSH preferred DSA
1815 over RSA for host and user authentication keys. With this
1816 upgrade, we've switched to the vendor's default of RSA over
1817 DSA. This may cause upgraded clients to warn about unknown
1818 host keys even for previously known hosts. Users should
1819 follow the usual procedure for verifying host keys before
1820 accepting the RSA key.
1822 This can be circumvented by setting the "HostKeyAlgorithms"
1823 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1826 Please note that the sequence of keys offered for
1827 authentication has been changed as well. You may want to
1828 specify IdentityFile in a different order to revert this
1832 The sio(4) driver has been removed from the i386 and amd64
1833 kernel configuration files. This means uart(4) is now the
1834 default serial port driver on those platforms as well.
1836 To prevent collisions with the sio(4) driver, the uart(4) driver
1837 uses different names for its device nodes. This means the
1838 onboard serial port will now most likely be called "ttyu0"
1839 instead of "ttyd0". You may need to reconfigure applications to
1840 use the new device names.
1842 When using the serial port as a boot console, be sure to update
1843 /boot/device.hints and /etc/ttys before booting the new kernel.
1844 If you forget to do so, you can still manually specify the hints
1845 at the loader prompt:
1847 set hint.uart.0.at="isa"
1848 set hint.uart.0.port="0x3F8"
1849 set hint.uart.0.flags="0x10"
1850 set hint.uart.0.irq="4"
1854 The gpt(8) utility has been removed. Use gpart(8) to partition
1858 The version that Linuxulator emulates was changed from 2.4.2
1859 to 2.6.16. If you experience any problems with Linux binaries
1860 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1861 if it fixes the problem contact emulation mailing list.
1864 ISDN4BSD (I4B) was removed from the src tree. You may need to
1865 update a your kernel configuration and remove relevant entries.
1868 I have checked in code to support multiple routing tables.
1869 See the man pages setfib(1) and setfib(2).
1870 This is a hopefully backwards compatible version,
1871 but to make use of it you need to compile your kernel
1872 with options ROUTETABLES=2 (or more up to 16).
1875 The 802.11 wireless support was redone to enable multi-bss
1876 operation on devices that are capable. The underlying device
1877 is no longer used directly but instead wlanX devices are
1878 cloned with ifconfig. This requires changes to rc.conf files.
1879 For example, change:
1880 ifconfig_ath0="WPA DHCP"
1883 ifconfig_wlan0="WPA DHCP"
1884 see rc.conf(5) for more details. In addition, mergemaster of
1885 /etc/rc.d is highly recommended. Simultaneous update of userland
1886 and kernel wouldn't hurt either.
1888 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1889 modules were merged into the base wlan module. All references
1890 to these modules (e.g. in kernel config files) must be removed.
1893 psm(4) has gained write(2) support in native operation level.
1894 Arbitrary commands can be written to /dev/psm%d and status can
1895 be read back from it. Therefore, an application is responsible
1896 for status validation and error recovery. It is a no-op in
1897 other operation levels.
1900 Support for KSE threading has been removed from the kernel. To
1901 run legacy applications linked against KSE libmap.conf may
1902 be used. The following libmap.conf may be used to ensure
1903 compatibility with any prior release:
1905 libpthread.so.1 libthr.so.1
1906 libpthread.so.2 libthr.so.2
1907 libkse.so.3 libthr.so.3
1910 The layout of struct vmspace has changed. This affects libkvm
1911 and any executables that link against libkvm and use the
1912 kvm_getprocs() function. In particular, but not exclusively,
1913 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1914 The effects are minimal, but it's advisable to upgrade world
1918 The latest em driver no longer has support in it for the
1919 82575 adapter, this is now moved to the igb driver. The
1920 split was done to make new features that are incompatible
1921 with older hardware easier to do.
1924 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1925 likewise the kernel option is now GEOM_LINUX_LVM.
1928 The default NFS mount mode has changed from UDP to TCP for
1929 increased reliability. If you rely on (insecurely) NFS
1930 mounting across a firewall you may need to update your
1934 Belatedly note the addition of m_collapse for compacting
1938 The fts(3) structures have been changed to use adequate
1939 integer types for their members and so to be able to cope
1940 with huge file trees. The old fts(3) ABI is preserved
1941 through symbol versioning in libc, so third-party binaries
1942 using fts(3) should still work, although they will not take
1943 advantage of the extended types. At the same time, some
1944 third-party software might fail to build after this change
1945 due to unportable assumptions made in its source code about
1946 fts(3) structure members. Such software should be fixed
1947 by its vendor or, in the worst case, in the ports tree.
1948 FreeBSD_version 800015 marks this change for the unlikely
1949 case that a portable fix is impossible.
1952 To upgrade to -current after this date, you must be running
1953 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1954 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1957 The ADAPTIVE_GIANT kernel option has been retired because its
1958 functionality is the default now.
1961 The AT keyboard emulation of sunkbd(4) has been turned on
1962 by default. In order to make the special symbols of the Sun
1963 keyboards driven by sunkbd(4) work under X these now have
1964 to be configured the same way as Sun USB keyboards driven
1965 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1967 Option "XkbLayout" "us"
1968 Option "XkbRules" "xorg"
1969 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1972 It has been decided that it is desirable to provide ABI
1973 backwards compatibility to the FreeBSD 4/5/6 versions of the
1974 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1975 broken with the introduction of PCI domain support (see the
1976 20070930 entry). Unfortunately, this required the ABI of
1977 PCIOCGETCONF to be broken again in order to be able to
1978 provide backwards compatibility to the old version of that
1979 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1980 again. As for prominent ports this affects neither pciutils
1981 nor xorg-server this time, the hal port needs to be rebuilt
1985 The misnamed kthread_create() and friends have been renamed
1986 to kproc_create() etc. Many of the callers already
1987 used kproc_start()..
1988 I will return kthread_create() and friends in a while
1989 with implementations that actually create threads, not procs.
1990 Renaming corresponds with version 800002.
1999 Avoid using make -j when upgrading. While generally safe, there are
2000 sometimes problems using -j to upgrade. If your upgrade fails with
2001 -j, please try again without -j. From time to time in the past there
2002 have been problems using -j with buildworld and/or installworld. This
2003 is especially true when upgrading between "distant" versions (eg one
2004 that cross a major release boundary or several minor releases, or when
2005 several months have passed on the -current branch).
2007 Sometimes, obscure build problems are the result of environment
2008 poisoning. This can happen because the make utility reads its
2009 environment when searching for values for global variables. To run
2010 your build attempts in an "environmental clean room", prefix all make
2011 commands with 'env -i '. See the env(1) manual page for more details.
2013 When upgrading from one major version to another it is generally best
2014 to upgrade to the latest code in the currently installed branch first,
2015 then do an upgrade to the new branch. This is the best-tested upgrade
2016 path, and has the highest probability of being successful. Please try
2017 this approach before reporting problems with a major version upgrade.
2019 When upgrading a live system, having a root shell around before
2020 installing anything can help undo problems. Not having a root shell
2021 around can lead to problems if pam has changed too much from your
2022 starting point to allow continued authentication after the upgrade.
2026 When upgrading the boot ZFS pool to a new version, always follow
2029 1.) recompile and reinstall the ZFS boot loader and boot block
2030 (this is part of "make buildworld" and "make installworld")
2032 2.) update the ZFS boot block on your boot drive
2034 The following example updates the ZFS boot block on the first
2035 partition (freebsd-boot) of a GPT partitioned drive ad0:
2036 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2038 Non-boot pools do not need these updates.
2042 If you are updating from a prior version of FreeBSD (even one just
2043 a few days old), you should follow this procedure. It is the most
2044 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2046 make kernel-toolchain
2047 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2048 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2050 To test a kernel once
2051 ---------------------
2052 If you just want to boot a kernel once (because you are not sure
2053 if it works, or if you want to boot a known bad kernel to provide
2054 debugging information) run
2055 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2056 nextboot -k testkernel
2058 To just build a kernel when you know that it won't mess you up
2059 --------------------------------------------------------------
2060 This assumes you are already running a CURRENT system. Replace
2061 ${arch} with the architecture of your machine (e.g. "i386",
2062 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2064 cd src/sys/${arch}/conf
2065 config KERNEL_NAME_HERE
2066 cd ../compile/KERNEL_NAME_HERE
2071 If this fails, go to the "To build a kernel" section.
2073 To rebuild everything and install it on the current system.
2074 -----------------------------------------------------------
2075 # Note: sometimes if you are running current you gotta do more than
2076 # is listed here if you are upgrading from a really old current.
2078 <make sure you have good level 0 dumps>
2080 make kernel KERNCONF=YOUR_KERNEL_HERE
2082 <reboot in single user> [3]
2089 To cross-install current onto a separate partition
2090 --------------------------------------------------
2091 # In this approach we use a separate partition to hold
2092 # current's root, 'usr', and 'var' directories. A partition
2093 # holding "/", "/usr" and "/var" should be about 2GB in
2096 <make sure you have good level 0 dumps>
2099 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2100 <maybe newfs current's root partition>
2101 <mount current's root partition on directory ${CURRENT_ROOT}>
2102 make installworld DESTDIR=${CURRENT_ROOT}
2103 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2104 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2105 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2106 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2107 <reboot into current>
2108 <do a "native" rebuild/install as described in the previous section>
2109 <maybe install compatibility libraries from ports/misc/compat*>
2113 To upgrade in-place from stable to current
2114 ----------------------------------------------
2115 <make sure you have good level 0 dumps>
2117 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2119 <reboot in single user> [3]
2126 Make sure that you've read the UPDATING file to understand the
2127 tweaks to various things you need. At this point in the life
2128 cycle of current, things change often and you are on your own
2129 to cope. The defaults can also change, so please read ALL of
2130 the UPDATING entries.
2132 Also, if you are tracking -current, you must be subscribed to
2133 freebsd-current@freebsd.org. Make sure that before you update
2134 your sources that you have read and understood all the recent
2135 messages there. If in doubt, please track -stable which has
2136 much fewer pitfalls.
2138 [1] If you have third party modules, such as vmware, you
2139 should disable them at this point so they don't crash your
2142 [3] From the bootblocks, boot -s, and then do
2147 adjkerntz -i # if CMOS is wall time
2148 Also, when doing a major release upgrade, it is required that
2149 you boot into single user mode to do the installworld.
2151 [4] Note: This step is non-optional. Failure to do this step
2152 can result in a significant reduction in the functionality of the
2153 system. Attempting to do it by hand is not recommended and those
2154 that pursue this avenue should read this file carefully, as well
2155 as the archives of freebsd-current and freebsd-hackers mailing lists
2156 for potential gotchas. The -U option is also useful to consider.
2157 See mergemaster(8) for more information.
2159 [5] Usually this step is a noop. However, from time to time
2160 you may need to do this if you get unknown user in the following
2161 step. It never hurts to do it all the time. You may need to
2162 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2163 install) after the buildworld before this step if you last updated
2164 from current before 20130425 or from -stable before 20130430.
2166 [6] This only deletes old files and directories. Old libraries
2167 can be deleted by "make delete-old-libs", but you have to make
2168 sure that no program is using those libraries anymore.
2170 [8] In order to have a kernel that can run the 4.x binaries needed to
2171 do an installworld, you must include the COMPAT_FREEBSD4 option in
2172 your kernel. Failure to do so may leave you with a system that is
2173 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2174 required to run the 5.x binaries on more recent kernels. And so on
2175 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2177 Make sure that you merge any new devices from GENERIC since the
2178 last time you updated your kernel config file.
2180 [9] When checking out sources, you must include the -P flag to have
2181 cvs prune empty directories.
2183 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2184 "?=" instead of the "=" assignment operator, so that buildworld can
2185 override the CPUTYPE if it needs to.
2187 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2188 not on the command line, or in /etc/make.conf. buildworld will
2189 warn if it is improperly defined.
2192 This file contains a list, in reverse chronological order, of major
2193 breakages in tracking -current. It is not guaranteed to be a complete
2194 list of such breakages, and only contains entries since October 10, 2007.
2195 If you need to see UPDATING entries from before that date, you will need
2196 to fetch an UPDATING file from an older FreeBSD release.
2198 Copyright information:
2200 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2202 Redistribution, publication, translation and use, with or without
2203 modification, in full or in part, in any form or format of this
2204 document are permitted without further permission from the author.
2206 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2207 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2208 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2209 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2210 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2211 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2212 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2213 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2214 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2215 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2216 POSSIBILITY OF SUCH DAMAGE.
2218 Contact Warner Losh if you have any questions about your use of