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.
20 Fix patch for SA-15:06.openssl.
22 20150319: p7 FreeBSD-SA-15:06.openssl
23 Fix multiple vulnerabilities in OpenSSL. [SA-15:06]
25 20150225: p6 FreeBSD-SA-15:04.igmp
27 FreeBSD-EN-15:02.openssl
28 FreeBSD-EN-15:03.freebsd-update
30 Fix integer overflow in IGMP protocol. [SA-15:04]
32 Fix vt(4) crash with improper ioctl parameters. [EN-15:01]
34 Updated base system OpenSSL to 1.0.1l. [EN-15:02]
36 Fix freebsd-update libraries update ordering issue. [EN-15:03]
38 20150127: p5 FreeBSD-SA-15:02.kmem
41 Fix SCTP SCTP_SS_VALUE kernel memory corruption and disclosure
42 vulnerability. [SA-15:02]
44 Fix SCTP stream reset vulnerability. [SA-15:03]
46 20150114: p4 FreeBSD-SA-15:01.openssl
47 Fix multiple vulnerabilities in OpenSSL. [SA-15:01]
49 20141223: p3 FreeBSD-SA-14:31.ntp
50 FreeBSD-EN-14:13.freebsd-update
52 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
53 Fix directory deletion issue in freebsd-update. [EN-14:13]
55 20141217: p2 FreeBSD-SA-14:30.unbound
56 Fix unbound remote denial of service vulnerability.
58 20141210: p1 FreeBSD-SA-14:27.stdio
61 Fix buffer overflow in stdio. [SA-14:27]
63 Fix multiple vulnerabilities in file(1) and libmagic(3).
67 The ofwfb driver, used to provide a graphics console on PowerPC when
68 using vt(4), no longer allows mmap() of all of physical memory. This
69 will prevent Xorg on PowerPC with some ATI graphics cards from
70 initializing properly unless x11-servers/xorg-server is updated to
74 The libatf-c and libatf-c++ major versions were downgraded to 0 and
75 1 respectively to match the upstream numbers. They were out of
76 sync because, when they were originally added to FreeBSD, the
77 upstream versions were not respected. These libraries are private
78 and not yet built by default, so renumbering them should be a
79 non-issue. However, unclean source trees will yield broken test
80 programs once the operator executes "make delete-old-libs" after a
83 Additionally, the atf-sh binary was made private by moving it into
84 /usr/libexec/. Already-built shell test programs will keep the
85 path to the old binary so they will break after "make delete-old"
88 If you are using WITH_TESTS=yes (not the default), wipe the object
89 tree and rebuild from scratch to prevent spurious test failures.
90 This is only needed once: the misnumbered libraries and misplaced
91 binaries have been added to OptionalObsoleteFiles.inc so they will
92 be removed during a clean upgrade.
95 The ixgbe tunables now match their sysctl counterparts, for example:
96 hw.ixgbe.enable_aim => hw.ix.enable_aim
97 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
100 The NFSv4.1 server committed by r269398 changes the internal
101 function call interfaces used between the NFS and krpc modules.
102 As such, __FreeBSD_version was bumped.
105 The default unbound configuration has been modified to address
106 issues with reverse lookups on networks that use private
107 address ranges. If you use the local_unbound service, run
108 "service local_unbound setup" as root to regenerate your
109 configuration, then "service local_unbound reload" to load the
113 It is no longer necessary to include the dwarf version in your DEBUG
114 options in your kernel config file. The bug that required it to be
115 placed in the config file has bene fixed. DEBUG should now just
116 contain -g. The build system will automatically update things
117 to do the right thing.
120 Several ABI breaking changes were merged to CTL and new iSCSI code.
121 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
122 iscsictl need to be rebuilt to work with a new kernel.
125 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
126 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
127 which differs from the behaviour controlled by this knob.)
130 On i386 and amd64 systems, the onifconsole flag is now set by default
131 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
132 as a login TTY if it is set in the bootloader as an active kernel
133 console. No changes in behavior should result otherwise. To revert to
134 the previous behavior, set ttyu0 to "off" in /etc/ttys.
137 Clang and llvm have been upgraded to 3.4.1 release.
140 Clang and llvm have been upgraded to 3.4 release.
143 If a Makefile in a tests/ directory was auto-generating a Kyuafile
144 instead of providing an explicit one, this would prevent such
145 Makefile from providing its own Kyuafile in the future during
146 NO_CLEAN builds. This has been fixed in the Makefiles but manual
147 intervention is needed to clean an objdir if you use NO_CLEAN:
148 # find /usr/obj -name Kyuafile | xargs rm -f
151 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
152 capability mode support. Please note that enabling the feature in
153 kernel is still highly recommended.
156 OpenSSH is now built with sandbox support, and will use sandbox as
157 the default privilege separation method. This requires Capsicum
158 capability mode support in kernel.
161 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
162 been deprecated and will not be part of FreeBSD 11.0 and later
163 releases. If you use this driver, please consider switching to
164 the nfe(4) driver instead.
170 The behavior of gss_pseudo_random() for the krb5 mechanism
171 has changed, for applications requesting a longer random string
172 than produced by the underlying enctype's pseudo-random() function.
173 In particular, the random string produced from a session key of
174 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
175 be different at the 17th octet and later, after this change.
176 The counter used in the PRF+ construction is now encoded as a
177 big-endian integer in accordance with RFC 4402.
178 __FreeBSD_version is bumped to 1000701.
181 The WITHOUT_ATF build knob has been removed and its functionality
182 has been subsumed into the more generic WITHOUT_TESTS. If you were
183 using the former to disable the build of the ATF libraries, you
184 should change your settings to use the latter.
187 The default version of mtree is nmtree which is obtained from
188 NetBSD. The output is generally the same, but may vary
189 slightly. If you found you need identical output adding
190 "-F freebsd9" to the command line should do the trick. For the
191 time being, the old mtree is available as fmtree.
194 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
195 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
196 1.1.4_8 and verify bsdyml not linked in, before running "make
198 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
200 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
203 The rc.d/jail script has been updated to support jail(8)
204 configuration file. The "jail_<jname>_*" rc.conf(5) variables
205 for per-jail configuration are automatically converted to
206 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
207 This is transparently backward compatible. See below about some
208 incompatibilities and rc.conf(5) manual page for more details.
210 These variables are now deprecated in favor of jail(8) configuration
211 file. One can use "rc.d/jail config <jname>" command to generate
212 a jail(8) configuration file in /var/run/jail.<jname>.conf without
213 running the jail(8) utility. The default pathname of the
214 configuration file is /etc/jail.conf and can be specified by
215 using $jail_conf or $jail_<jname>_conf variables.
217 Please note that jail_devfs_ruleset accepts an integer at
218 this moment. Please consider to rewrite the ruleset name
222 BIND has been removed from the base system. If all you need
223 is a local resolver, simply enable and start the local_unbound
224 service instead. Otherwise, several versions of BIND are
225 available in the ports tree. The dns/bind99 port is one example.
227 With this change, nslookup(1) and dig(1) are no longer in the base
228 system. Users should instead use host(1) and drill(1) which are
229 in the base system. Alternatively, nslookup and dig can
230 be obtained by installing the dns/bind-tools port.
233 With the addition of unbound(8), a new unbound user is now
234 required during installworld. "mergemaster -p" can be used to
235 add the user prior to installworld, as documented in the handbook.
238 OpenSSH is now built with DNSSEC support, and will by default
239 silently trust signed SSHFP records. This can be controlled with
240 the VerifyHostKeyDNS client configuration setting. DNSSEC support
241 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
244 The GNU Compiler Collection and C++ standard library (libstdc++)
245 are no longer built by default on platforms where clang is the system
246 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
250 The PROCDESC kernel option is now part of the GENERIC kernel
251 configuration and is required for the rwhod(8) to work.
252 If you are using custom kernel configuration, you should include
256 The API and ABI related to the Capsicum framework was modified
257 in backward incompatible way. The userland libraries and programs
258 have to be recompiled to work with the new kernel. This includes the
259 following libraries and programs, but the whole buildworld is
260 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
261 kdump, procstat, rwho, rwhod, uniq.
264 AES-NI intrinsic support has been added to gcc. The AES-NI module
265 has been updated to use this support. A new gcc is required to build
266 the aesni module on both i386 and amd64.
269 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
270 Thus "device padlock_rng" and "device rdrand_rng" should be
271 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
274 WITH_ICONV has been split into two feature sets. WITH_ICONV now
275 enables just the iconv* functionality and is now on by default.
276 WITH_LIBICONV_COMPAT enables the libiconv api and link time
277 compatability. Set WITHOUT_ICONV to build the old way.
278 If you have been using WITH_ICONV before, you will very likely
279 need to turn on WITH_LIBICONV_COMPAT.
282 INVARIANTS option now enables DEBUG for code with OpenSolaris and
283 Illumos origin, including ZFS. If you have INVARIANTS in your
284 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
286 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
287 locks if WITNESS option was set. Because that generated a lot of
288 witness(9) reports and all of them were believed to be false
289 positives, this is no longer done. New option OPENSOLARIS_WITNESS
290 can be used to achieve the previous behavior.
293 Timer values in IPv6 data structures now use time_uptime instead
294 of time_second. Although this is not a user-visible functional
295 change, userland utilities which directly use them---ndp(8),
296 rtadvd(8), and rtsold(8) in the base system---need to be updated
300 find -delete can now delete the pathnames given as arguments,
301 instead of only files found below them or if the pathname did
302 not contain any slashes. Formerly, the following error message
305 find: -delete: <path>: relative path potentially not safe
307 Deleting the pathnames given as arguments can be prevented
308 without error messages using -mindepth 1 or by changing
309 directory and passing "." as argument to find. This works in the
310 old as well as the new version of find.
313 Behavior of devfs rules path matching has been changed.
314 Pattern is now always matched against fully qualified devfs
315 path and slash characters must be explicitly matched by
316 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
317 subdirectories must be reviewed.
320 The default ARM ABI has changed to the ARM EABI. The old ABI is
321 incompatible with the ARM EABI and all programs and modules will
322 need to be rebuilt to work with a new kernel.
324 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
326 NOTE: Support for the old ABI will be removed in the future and
327 users are advised to upgrade.
330 pkg_install has been disconnected from the build if you really need it
331 you should add WITH_PKGTOOLS in your src.conf(5).
334 Most of network statistics structures were changed to be able
335 keep 64-bits counters. Thus all tools, that work with networking
336 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
339 Fix targets that run multiple make's to use && rather than ;
340 so that subsequent steps depend on success of previous.
342 NOTE: if building 'universe' with -j* on stable/8 or stable/9
343 it would be better to start the build using bmake, to avoid
344 overloading the machine.
347 Fix a bug that allowed a tracing process (e.g. gdb) to write
348 to a memory-mapped file in the traced process's address space
349 even if neither the traced process nor the tracing process had
350 write access to that file.
353 CVS has been removed from the base system. An exact copy
354 of the code is available from the devel/cvs port.
357 Some people report the following error after the switch to bmake:
359 make: illegal option -- J
360 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
362 *** [buildworld] Error code 2
364 this likely due to an old instance of make in
365 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
366 which src/Makefile will use that blindly, if it exists, so if
367 you see the above error:
369 rm -rf `make -V MAKEPATH`
374 Use bmake by default.
375 Whereas before one could choose to build with bmake via
376 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
377 make. The goal is to remove these knobs for 10-RELEASE.
379 It is worth noting that bmake (like gmake) treats the command
380 line as the unit of failure, rather than statements within the
381 command line. Thus '(cd some/where && dosomething)' is safer
382 than 'cd some/where; dosomething'. The '()' allows consistent
383 behavior in parallel build.
386 Fix a bug that allows NFS clients to issue READDIR on files.
389 The WITHOUT_IDEA option has been removed because
390 the IDEA patent expired.
393 The sysctl which controls TRIM support under ZFS has been renamed
394 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
398 The mergemaster command now uses the default MAKEOBJDIRPREFIX
399 rather than creating it's own in the temporary directory in
400 order allow access to bootstrapped versions of tools such as
401 install and mtree. When upgrading from version of FreeBSD where
402 the install command does not support -l, you will need to
403 install a new mergemaster command if mergemaster -p is required.
404 This can be accomplished with the command (cd src/usr.sbin/mergemaster
408 Legacy ATA stack, disabled and replaced by new CAM-based one since
409 FreeBSD 9.0, completely removed from the sources. Kernel modules
410 atadisk and atapi*, user-level tools atacontrol and burncd are
411 removed. Kernel option `options ATA_CAM` is now permanently enabled
415 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
416 and socketpair(2). Software, in particular Kerberos, may
417 automatically detect and use these during building. The resulting
418 binaries will not work on older kernels.
421 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
422 information, see the respective 20130304 entry).
425 Recent commits to callout(9) changed the size of struct callout,
426 so the KBI is probably heavily disturbed. Also, some functions
427 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
428 by macros. Every kernel module using it won't load, so rebuild
431 The ctl device has been re-enabled in GENERIC for i386 and amd64,
432 but does not initialize by default (because of the new CTL_DISABLE
433 option) to save memory. To re-enable it, remove the CTL_DISABLE
434 option from the kernel config file or set kern.cam.ctl.disable=0
435 in /boot/loader.conf.
438 The ctl device has been disabled in GENERIC for i386 and amd64.
439 This was done due to the extra memory being allocated at system
440 initialisation time by the ctl driver which was only used if
441 a CAM target device was created. This makes a FreeBSD system
442 unusable on 128MB or less of RAM.
445 A new compression method (lz4) has been merged to -HEAD. Please
446 refer to zpool-features(7) for more information.
448 Please refer to the "ZFS notes" section of this file for information
449 on upgrading boot ZFS pools.
452 A BSD-licensed patch(1) variant has been added and is installed
453 as bsdpatch, being the GNU version the default patch.
454 To inverse the logic and use the BSD-licensed one as default,
455 while having the GNU version installed as gnupatch, rebuild
456 and install world with the WITH_BSD_PATCH knob set.
459 Due to the use of the new -l option to install(1) during build
460 and install, you must take care not to directly set the INSTALL
461 make variable in your /etc/make.conf, /etc/src.conf, or on the
462 command line. If you wish to use the -C flag for all installs
463 you may be able to add INSTALL+=-C to /etc/make.conf or
467 The install(1) option -M has changed meaning and now takes an
468 argument that is a file or path to append logs to. In the
469 unlikely event that -M was the last option on the command line
470 and the command line contained at least two files and a target
471 directory the first file will have logs appended to it. The -M
472 option served little practical purpose in the last decade so its
473 use is expected to be extremely rare.
476 After switching to Clang as the default compiler some users of ZFS
477 on i386 systems started to experience stack overflow kernel panics.
478 Please consider using 'options KSTACK_PAGES=4' in such configurations.
481 GEOM_LABEL now mangles label names read from file system metadata.
482 Mangling affect labels containing spaces, non-printable characters,
483 '%' or '"'. Device names in /etc/fstab and other places may need to
487 By default, only the 10 most recent kernel dumps will be saved. To
488 restore the previous behaviour (no limit on the number of kernel dumps
489 stored in the dump directory) add the following line to /etc/rc.conf:
494 With the addition of auditdistd(8), a new auditdistd user is now
495 required during installworld. "mergemaster -p" can be used to
496 add the user prior to installworld, as documented in the handbook.
499 The sin6_scope_id member variable in struct sockaddr_in6 is now
500 filled by the kernel before passing the structure to the userland via
501 sysctl or routing socket. This means the KAME-specific embedded scope
502 id in sin6_addr.s6_addr[2] is always cleared in userland application.
503 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
504 __FreeBSD_version is bumped to 1000025.
507 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
508 This means that the world and kernel will be compiled with clang
509 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
510 and /usr/bin/cpp. To disable this behavior and revert to building
511 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
512 of current may need to bootstrap WITHOUT_CLANG first if the clang
513 build fails (its compatibility window doesn't extend to the 9 stable
517 The IPFIREWALL_FORWARD kernel option has been removed. Its
518 functionality now turned on by default.
521 The ZERO_COPY_SOCKET kernel option has been removed and
522 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
523 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
524 mechanism which is not safe and may result in kernel crashes.
525 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
526 driver supports disposeable external page sized mbuf storage.
527 Proper replacements for both zero-copy mechanisms are under
528 consideration and will eventually lead to complete removal
529 of the two kernel options.
532 The IPv4 network stack has been converted to network byte
533 order. The following modules need to be recompiled together
534 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
535 pf(4), ipfw(4), ng_ipfw(4), stf(4).
538 Support for non-MPSAFE filesystems was removed from VFS. The
539 VFS_VERSION was bumped, all filesystem modules shall be
543 All the non-MPSAFE filesystems have been disconnected from
544 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
545 portalfs, smbfs, xfs.
548 The interface cloning API and ABI has changed. The following
549 modules need to be recompiled together with kernel:
550 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
551 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
552 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
555 The sdhci driver was split in two parts: sdhci (generic SD Host
556 Controller logic) and sdhci_pci (actual hardware driver).
557 No kernel config modifications are required, but if you
558 load sdhc as a module you must switch to sdhci_pci instead.
561 Import the FUSE kernel and userland support into base system.
564 The GNU sort(1) program has been removed since the BSD-licensed
565 sort(1) has been the default for quite some time and no serious
566 problems have been reported. The corresponding WITH_GNU_SORT
570 The pfil(9) API/ABI for AF_INET family has been changed. Packet
571 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
575 The net80211(4) ABI has been changed to allow for improved driver
576 PS-POLL and power-save support. All wireless drivers need to be
577 recompiled to work with the new kernel.
580 The random(4) support for the VIA hardware random number
581 generator (`PADLOCK') is no longer enabled unconditionally.
582 Add the padlock_rng device in the custom kernel config if
583 needed. The GENERIC kernels on i386 and amd64 do include the
584 device, so the change only affects the custom kernel
588 The pf(4) packet filter ABI has been changed. pfctl(8) and
589 snmp_pf module need to be recompiled to work with new kernel.
592 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
593 to -HEAD. Pools that have empty_bpobj in active state can not be
594 imported read-write with ZFS implementations that do not support
595 this feature. For more information read the zpool-features(5)
599 The sparc64 ZFS loader has been changed to no longer try to auto-
600 detect ZFS providers based on diskN aliases but now requires these
601 to be explicitly listed in the OFW boot-device environment variable.
604 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
605 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
606 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
609 The following sysctls and tunables have been renamed for consistency
610 with other variables:
611 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
612 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
615 The sort utility has been replaced with BSD sort. For now, GNU sort
616 is also available as "gnusort" or the default can be set back to
617 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
618 installed as "bsdsort".
621 A new version of ZFS (pool version 5000) has been merged to -HEAD.
622 Starting with this version the old system of ZFS pool versioning
623 is superseded by "feature flags". This concept enables forward
624 compatibility against certain future changes in functionality of ZFS
625 pools. The first read-only compatible "feature flag" for ZFS pools
626 is named "com.delphix:async_destroy". For more information
627 read the new zpool-features(5) manual page.
628 Please refer to the "ZFS notes" section of this file for information
629 on upgrading boot ZFS pools.
632 The malloc(3) implementation embedded in libc now uses sources imported
633 as contrib/jemalloc. The most disruptive API change is to
634 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
635 delete it prior to installworld, and optionally re-create it using the
636 new format after rebooting. See malloc.conf(5) for details
637 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
641 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
642 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
643 now spelled mips. This is to aid compatibility with third-party
644 software that expects this naming scheme in uname(3). Little-endian
645 settings are unchanged. If you are updating a big-endian mips64 machine
646 from before this change, you may need to set MACHINE_ARCH=mips64 in
647 your environment before the new build system will recognize your machine.
650 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
654 Now unix domain sockets behave "as expected" on nullfs(5). Previously
655 nullfs(5) did not pass through all behaviours to the underlying layer,
656 as a result if we bound to a socket on the lower layer we could connect
657 only to the lower path; if we bound to the upper layer we could connect
658 only to the upper path. The new behavior is one can connect to both the
659 lower and the upper paths regardless what layer path one binds to.
662 The getifaddrs upgrade path broken with 20111215 has been restored.
663 If you have upgraded in between 20111215 and 20120209 you need to
664 recompile libc again with your kernel. You still need to recompile
665 world to be able to configure CARP but this restriction already
669 The set_rcvar() function has been removed from /etc/rc.subr. All
670 base and ports rc.d scripts have been updated, so if you have a
671 port installed with a script in /usr/local/etc/rc.d you can either
672 hand-edit the rcvar= line, or reinstall the port.
674 An easy way to handle the mass-update of /etc/rc.d:
675 rm /etc/rc.d/* && mergemaster -i
678 panic(9) now stops other CPUs in the SMP systems, disables interrupts
679 on the current CPU and prevents other threads from running.
680 This behavior can be reverted using the kern.stop_scheduler_on_panic
682 The new behavior can be incompatible with kern.sync_on_panic.
685 The carp(4) facility has been changed significantly. Configuration
686 of the CARP protocol via ifconfig(8) has changed, as well as format
687 of CARP events submitted to devd(8) has changed. See manual pages
688 for more information. The arpbalance feature of carp(4) is currently
689 not supported anymore.
691 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
692 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
693 need to be recompiled.
696 The acpi_wmi(4) status device /dev/wmistat has been renamed to
700 The option VFS_ALLOW_NONMPSAFE option has been added in order to
701 explicitely support non-MPSAFE filesystems.
702 It is on by default for all supported platform at this present
706 The broken amd(4) driver has been replaced with esp(4) in the amd64,
707 i386 and pc98 GENERIC kernel configuration files.
710 sysinstall has been removed
713 The stable/9 branch created in subversion. This corresponds to the
714 RELENG_9 branch in CVS.
717 This commit modifies vfs_register() so that it uses a hash
718 calculation to set vfc_typenum, which is enabled by default.
719 The first time a system is booted after this change, the
720 vfc_typenum values will change for all file systems. The
721 main effect of this is a change to the NFS server file handles
722 for file systems that use vfc_typenum in their fsid, such as ZFS.
723 It will, however, prevent vfc_typenum from changing when file
724 systems are loaded in a different order for subsequent reboots.
725 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
726 until you are ready to remount all NFS clients after a reboot.
729 Bump the shared library version numbers for libraries that
730 do not use symbol versioning, have changed the ABI compared
731 to stable/8 and which shared library version was not bumped.
732 Done as part of 9.0-RELEASE cycle.
735 During the merge of Capsicum features, the fget(9) KPI was modified.
736 This may require the rebuilding of out-of-tree device drivers --
737 issues have been reported specifically with the nVidia device driver.
738 __FreeBSD_version is bumped to 900041.
740 Also, there is a period between 20110811 and 20110814 where the
741 special devices /dev/{stdin,stdout,stderr} did not work correctly.
742 Building world from a kernel during that window may not work.
745 The packet filter (pf) code has been updated to OpenBSD 4.5.
746 You need to update userland tools to be in sync with kernel.
747 This update breaks backward compatibility with earlier pfsync(4)
748 versions. Care must be taken when updating redundant firewall setups.
751 The following sysctls and tunables are retired on x86 platforms:
753 machdep.hlt_logical_cpus
754 The following sysctl is retired:
755 machdep.hyperthreading_allowed
756 The sysctls were supposed to provide a way to dynamically offline and
757 online selected CPUs on x86 platforms, but the implementation has not
758 been reliable especially with SCHED_ULE scheduler.
759 machdep.hyperthreading_allowed tunable is still available to ignore
760 hyperthreading CPUs at OS level.
761 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
762 where X is an APIC ID of a CPU. Be advised, though, that disabling
763 CPUs in non-uniform fashion will result in non-uniform topology and
764 may lead to sub-optimal system performance with SCHED_ULE, which is
768 cpumask_t type is retired and cpuset_t is used in order to describe
772 Changes to ifconfig(8) for dynamic address family detection mandate
773 that you are running a kernel of 20110525 or later. Make sure to
774 follow the update procedure to boot a new kernel before installing
778 Support for sun4v architecture is officially dropped
781 Several KPI breaking changes have been committed to the mii(4) layer,
782 the PHY drivers and consequently some Ethernet drivers using mii(4).
783 This means that miibus.ko and the modules of the affected Ethernet
784 drivers need to be recompiled.
786 Note to kernel developers: Given that the OUI bit reversion problem
787 was fixed as part of these changes all mii(4) commits related to OUIs,
788 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
789 handling, no longer can be merged verbatim to stable/8 and previous
793 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
794 into their kernel configurations along with 'device pci'.
797 The default NFS client is now the new NFS client, so fstype "newnfs"
798 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
799 Although mounts via fstype "nfs" will usually work without userland
800 changes, it is recommended that the mount(8) and mount_nfs(8)
801 commands be rebuilt from sources and that a link to mount_nfs called
802 mount_oldnfs be created. The new client is compiled into the
803 kernel with "options NFSCL" and this is needed for diskless root
804 file systems. The GENERIC kernel configs have been changed to use
805 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
806 To use the regular/old client, you can "mount -t oldnfs ...". For
807 a diskless root file system, you must also include a line like:
809 vfs.root.mountfrom="oldnfs:"
811 in the boot/loader.conf on the root fs on the NFS server to make
812 a diskless root fs use the old client.
815 The GENERIC kernels for all architectures now default to the new
816 CAM-based ATA stack. It means that all legacy ATA drivers were
817 removed and replaced by respective CAM drivers. If you are using
818 ATA device names in /etc/fstab or other places, make sure to update
819 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
820 where 'Y's are the sequential numbers starting from zero for each type
821 in order of detection, unless configured otherwise with tunables,
822 see cam(4)). There will be symbolic links created in /dev/ to map
823 old adX devices to the respective adaY. They should provide basic
824 compatibility for file systems mounting in most cases, but they do
825 not support old user-level APIs and do not have respective providers
826 in GEOM. Consider using updated management tools with new device names.
828 It is possible to load devices ahci, ata, siis and mvs as modules,
829 but option ATA_CAM should remain in kernel configuration to make ata
830 module work as CAM driver supporting legacy ATA controllers. Device ata
831 still can be used in modular fashion (atacore + ...). Modules atadisk
832 and atapi* are not used and won't affect operation in ATA_CAM mode.
833 Note that to use CAM-based ATA kernel should include CAM devices
834 scbus, pass, da (or explicitly ada), cd and optionally others. All of
835 them are parts of the cam module.
837 ataraid(4) functionality is now supported by the RAID GEOM class.
838 To use it you can load geom_raid kernel module and use graid(8) tool
839 for management. Instead of /dev/arX device names, use /dev/raid/rX.
841 No kernel config options or code have been removed, so if a problem
842 arises, please report it and optionally revert to the old ATA stack.
843 In order to do it you can remove from the kernel config:
848 , and instead add back:
849 device atadisk # ATA disk drives
850 device ataraid # ATA RAID drives
851 device atapicd # ATAPI CDROM drives
852 device atapifd # ATAPI floppy drives
853 device atapist # ATAPI tape drives
856 The default NFS server has been changed to the new server, which
857 was referred to as the experimental server. If you need to switch
858 back to the old NFS server, you must now put the "-o" option on
859 both the mountd and nfsd commands. This can be done using the
860 mountd_flags and nfs_server_flags rc.conf variables until an
861 update to the rc scripts is committed, which is coming soon.
864 The GNU Objective-C runtime library (libobjc), and other Objective-C
865 related components have been removed from the base system. If you
866 require an Objective-C library, please use one of the available ports.
869 ath(4) has been split into bus- and device- modules. if_ath contains
870 the HAL, the TX rate control and the network device code. if_ath_pci
871 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
872 contains the AHB glue. Users need to load both if_ath_pci and if_ath
873 in order to use ath on everything else.
875 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
876 need to load if_ath and if_ath_pci for ath(4) operation.
879 As part of the replacement of sysinstall, the process of building
880 release media has changed significantly. For details, please re-read
881 release(7), which has been updated to reflect the new build process.
884 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
885 is the last available version under GPLv2. It brings a number of new
886 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
887 4.1 and SSE 4.2), better support for powerpc64, a number of new
888 directives, and lots of other small improvements. See the ChangeLog
889 file in contrib/binutils for the full details.
892 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
893 compliant, and will now use half of hash for authentication.
894 This will break interoperability with all stacks (including all
895 actual FreeBSD versions) who implement
896 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
898 The only workaround with such peers is to use another HMAC
899 algorithm for IPsec ("phase 2") authentication.
902 Remove the uio_yield prototype and symbol. This function has
903 been misnamed since it was introduced and should not be
904 globally exposed with this name. The equivalent functionality
905 is now available using kern_yield(curthread->td_user_pri).
906 The function remains undocumented.
909 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
910 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
911 for scalar sysctls is defined but disabled. Code that needs
912 UQUAD to pass the type checking that must compile on older
913 systems where the define is not present can check against
914 __FreeBSD_version >= 900030.
916 The system dialog(1) has been replaced with a new version previously
917 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
918 with the previous version, but the libdialog associated with it has
919 a largely incompatible API. As such, the original version of libdialog
920 will be kept temporarily as libodialog, until its base system consumers
921 are replaced or updated. Bump __FreeBSD_version to 900030.
924 If you are trying to run make universe on a -stable system, and you get
925 the following warning:
926 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
927 unknown. config(8) likely too old."
928 or something similar to it, then you must upgrade your -stable system
929 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
930 stable/8) or build the config from the latest stable/8 branch and
931 install it on your system.
933 Prior to this date, building a current universe on 8-stable system from
934 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
935 error in the first kernel build phase. A new config on those old
936 systems will fix that problem for older versions of -current.
939 The TCP stack has been modified to allow Khelp modules to interact with
940 it via helper hook points and store per-connection data in the TCP
941 control block. Bump __FreeBSD_version to 900029. User space tools that
942 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
946 Generic IEEE 802.3 annex 31B full duplex flow control support has been
947 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
948 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
949 to take advantage of it instead of using custom implementations. This
950 means that these drivers now no longer unconditionally advertise
951 support for flow control but only do so if flow control is a selected
952 media option. This was implemented in the generic support that way in
953 order to allow flow control to be switched on and off via ifconfig(8)
954 with the PHY specific default to typically off in order to protect
955 from unwanted effects. Consequently, if you used flow control with
956 one of the above mentioned drivers you now need to explicitly enable
958 ifconfig bge0 media auto mediaopt flowcontrol
960 Along with the above mentioned changes generic support for setting
961 1000baseT master mode also has been added and brgphy(4), ciphy(4),
962 e1000phy(4) as well as ip1000phy(4) have been converted to take
963 advantage of it. This means that these drivers now no longer take the
964 link0 parameter for selecting master mode but the master media option
965 has to be used instead, for example like in the following:
966 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
968 Selection of master mode now is also available with all other PHY
969 drivers supporting 1000baseT.
972 The TCP stack has received a significant update to add support for
973 modularised congestion control and generally improve the clarity of
974 congestion control decisions. Bump __FreeBSD_version to 900025. User
975 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
976 sockstat) need to be recompiled.
979 The man(1) utility has been replaced by a new version that no longer
980 uses /etc/manpath.config. Please consult man.conf(5) for how to
981 migrate local entries to the new format.
984 The copyright strings printed by login(1) and sshd(8) at the time of a
985 new connection have been removed to follow other operating systems and
989 A workaround for a fixed ld bug has been removed in kernel code,
990 so make sure that your system ld is built from sources after
991 revision 210245 from 2010-07-19 (r211583 if building head kernel
992 on stable/8, r211584 for stable/7; both from 2010-08-21).
993 A symptom of incorrect ld version is different addresses for
994 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
997 The $ipv6_prefer variable in rc.conf(5) has been split into
998 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1000 The $ip6addrctl_policy is a variable to choose a pre-defined
1001 address selection policy set by ip6addrctl(8). A value
1002 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1005 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1006 flag (see an entry of 20090926) is set on an interface with no
1007 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1008 security reason. If you want IPv6 link-local address on all
1009 interfaces by default, set this to "YES".
1011 The old ipv6_prefer="YES" is equivalent to
1012 ipv6_activate_all_interfaces="YES" and
1013 ip6addrctl_policy="ipv6_prefer".
1016 DTrace has grown support for userland tracing. Due to this, DTrace is
1017 now i386 and amd64 only.
1018 dtruss(1) is now installed by default on those systems and a new
1019 kernel module is needed for userland tracing: fasttrap.
1020 No changes to your kernel config file are necessary to enable
1021 userland tracing, but you might consider adding 'STRIP=' and
1022 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1023 to have informative userland stack traces in DTrace (ustack).
1026 The acpi_aiboost(4) driver has been removed in favor of the new
1027 aibs(4) driver. You should update your kernel configuration file.
1030 BSD grep has been imported to the base system and it is built by
1031 default. It is completely BSD licensed, highly GNU-compatible, uses
1032 less memory than its GNU counterpart and has a small codebase.
1033 However, it is slower than its GNU counterpart, which is mostly
1034 noticeable for larger searches, for smaller ones it is measurable
1035 but not significant. The reason is complex, the most important factor
1036 is that we lack a modern and efficient regex library and GNU
1037 overcomes this by optimizing the searches internally. Future work
1038 on improving the regex performance is planned, for the meantime,
1039 users that need better performance, can build GNU grep instead by
1040 setting the WITH_GNU_GREP knob.
1043 Due to the import of powerpc64 support, all existing powerpc kernel
1044 configuration files must be updated with a machine directive like this:
1045 machine powerpc powerpc
1047 In addition, an updated config(8) is required to build powerpc kernels
1051 A new version of ZFS (version 15) has been merged to -HEAD.
1052 This version uses a python library for the following subcommands:
1053 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1054 For full functionality of these commands the following port must
1055 be installed: sysutils/py-zfs
1058 'vm_page's are now hashed by physical address to an array of mutexes.
1059 Currently this is only used to serialize access to hold_count. Over
1060 time the page queue mutex will be peeled away. This changes the size
1061 of pmap on every architecture. And requires all callers of vm_page_hold
1062 and vm_page_unhold to be updated.
1065 WITH_CTF can now be specified in src.conf (not recommended, there
1066 are some problems with static executables), make.conf (would also
1067 affect ports which do not use GNU make and do not override the
1068 compile targets) or in the kernel config (via "makeoptions
1070 When WITH_CTF was specified there before this was silently ignored,
1071 so make sure that WITH_CTF is not used in places which could lead
1072 to unwanted behavior.
1075 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1076 to allow 32-bit compatibility on non-x86 platforms. All kernel
1077 configurations on amd64 and ia64 platforms using these options must
1078 be modified accordingly.
1081 The utmp user accounting database has been replaced with utmpx,
1082 the user accounting interface standardized by POSIX.
1083 Unfortunately the semantics of utmp and utmpx don't match,
1084 making it practically impossible to support both interfaces.
1085 The user accounting database is used by tools like finger(1),
1086 last(1), talk(1), w(1) and ac(8).
1088 All applications in the base system use utmpx. This means only
1089 local binaries (e.g. from the ports tree) may still use these
1090 utmp database files. These applications must be rebuilt to make
1093 After the system has been upgraded, it is safe to remove the old
1094 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1095 assuming their contents is of no importance anymore. Old wtmp
1096 databases can only be used by last(1) and ac(8) after they have
1097 been converted to the new format using wtmpcvt(1).
1100 Introduce the kernel thread "deadlock resolver" (which can be enabled
1101 via the DEADLKRES option, see NOTES for more details) and the
1102 sleepq_type() function for sleepqueues.
1105 The rc.firewall and rc.firewall6 were unified, and
1106 rc.firewall6 and rc.d/ip6fw were removed.
1107 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1108 variables are obsoleted. Instead, the following new rc
1109 variables are added to rc.d/ipfw:
1111 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1112 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1113 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1115 The meanings correspond to the relevant IPv4 variables.
1121 The default terminal emulation for syscons(4) has been changed
1122 from cons25 to xterm on all platforms except pc98. This means
1123 that the /etc/ttys file needs to be updated to ensure correct
1124 operation of applications on the console.
1126 The terminal emulation style can be toggled per window by using
1127 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1128 options can be used to change the compile-time default back to
1131 To prevent graphical artifacts, make sure the TERM environment
1132 variable is set to match the terminal emulation that is being
1133 performed by syscons(4).
1136 The layout of the structure ieee80211req_scan_result has changed.
1137 Applications that require wireless scan results (e.g. ifconfig(8))
1138 from net80211 need to be recompiled.
1140 Applications such as wpa_supplicant(8) may require a full world
1141 build without using NO_CLEAN in order to get synchronized with the
1145 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1146 There's one kernel module for each firmware. Adding "device iwnfw"
1147 to the kernel configuration file means including all three firmware
1148 images inside the kernel. If you want to include just the one for
1149 your wireless card, use the devices iwn4965fw, iwn5000fw or
1153 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1154 into rc.d/netif. The changes are the following:
1156 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1157 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1158 Note that both variables need the "inet6" keyword at the head.
1160 Do not set $ipv6_network_interfaces manually if you do not
1161 understand what you are doing. It is not needed in most cases.
1163 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1166 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1167 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1169 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1170 all configured interfaces have "inet6 accept_rtadv" in the
1171 $ifconfig_IF_ipv6. These are for backward compatibility.
1173 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1174 functionality of interfaces with no corresponding
1175 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1176 and the default address selection policy of ip6addrctl(8)
1177 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1178 Note that if you want to configure IPv6 functionality on the
1179 disabled interfaces after boot, first you need to clear the flag by
1180 using ifconfig(8) like:
1182 ifconfig em0 inet6 -ifdisabled
1184 If YES, the default address selection policy is set as
1187 The default value of $ipv6_prefer is NO.
1189 4. If your system need to receive Router Advertisement messages,
1190 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1191 scripts automatically invoke rtsol(8) when the interface becomes
1192 UP. The Router Advertisement messages are used for SLAAC
1193 (State-Less Address AutoConfiguration).
1196 802.11s D3.03 support was committed. This is incompatible with the
1197 previous code, which was based on D3.0.
1200 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1201 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1202 control whether accepting Router Advertisement messages or not.
1203 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1204 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1205 The ifconfig(8) utility now supports these flags.
1208 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1209 mount(8) and -a option for df(1) to see them.
1212 The old tunable hw.bus.devctl_disable has been superseded by
1213 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1214 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1218 Remove the option STOP_NMI. The default action is now to use NMI only
1219 for KDB via the newly introduced function stop_cpus_hard() and
1220 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1223 The stable/8 branch created in subversion. This corresponds to the
1224 RELENG_8 branch in CVS.
1227 Bump the shared library version numbers for all libraries that do not
1228 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1229 __FreeBSD_version to 800105.
1232 Due to changes in the implementation of virtual network stack support,
1233 all network-related kernel modules must be recompiled. As this change
1234 breaks the ABI, bump __FreeBSD_version to 800104.
1237 The TOE interface to the TCP syncache has been modified to remove
1238 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1239 The cxgb driver is the only TOE consumer affected by this change, and
1240 needs to be recompiled along with the kernel. As this change breaks
1241 the ABI, bump __FreeBSD_version to 800103.
1244 Padding has been added to struct tcpcb, sackhint and tcpstat in
1245 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1246 maintaining the ABI. However, this change breaks the ABI, so bump
1247 __FreeBSD_version to 800102. User space tools that rely on the size of
1248 any of these structs (e.g. sockstat) need to be recompiled.
1251 The NFS_LEGACYRPC option has been removed along with the old kernel
1252 RPC implementation that this option selected. Kernel configurations
1253 may need to be adjusted.
1256 The network interface device nodes at /dev/net/<interface> have been
1257 removed. All ioctl operations can be performed the normal way using
1258 routing sockets. The kqueue functionality can generally be replaced
1259 with routing sockets.
1262 The documentation from the FreeBSD Documentation Project (Handbook,
1263 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1264 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1267 The ABI of various structures related to the SYSV IPC API have been
1268 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1269 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1273 Layout of struct vnet has changed as routing related variables were
1274 moved to their own Vimage module. Modules need to be recompiled. Bump
1275 __FreeBSD_version to 800099.
1278 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1279 respectively. As long as no more than 16 groups per process are used,
1280 no changes should be visible. When more than 16 groups are used, old
1281 binaries may fail if they call getgroups() or getgrouplist() with
1282 statically sized storage. Recompiling will work around this, but
1283 applications should be modified to use dynamically allocated storage
1284 for group arrays as POSIX.1-2008 does not cap an implementation's
1285 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1287 NFS and portalfs mounts may also be affected as the list of groups is
1288 truncated to 16. Users of NFS who use more than 16 groups, should
1289 take care that negative group permissions are not used on the exported
1290 file systems as they will not be reliable unless a GSSAPI based
1291 authentication method is used.
1294 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1295 option compiles in the support for adaptive spinning for lockmgrs
1296 which want to enable it. The lockinit() function now accepts the flag
1297 LK_ADAPTIVE in order to make the lock object subject to adaptive
1298 spinning when both held in write and read mode.
1301 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1302 changed. User applications that use this ioctl need to be rebuilt.
1305 The layout of struct thread has changed. Kernel and modules need to
1309 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1310 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1313 window(1) has been removed from the base system. It can now be
1314 installed from ports. The port is called misc/window.
1317 The way we are storing and accessing `routing table' entries has
1318 changed. Programs reading the FIB, like netstat, need to be
1322 A new netisr implementation has been added for FreeBSD 8. Network
1323 file system modules, such as igmp, ipdivert, and others, should be
1325 Bump __FreeBSD_version to 800096.
1328 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1332 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1333 Bump __FreeBSD_version to 800094.
1336 Add mnt_xflag field to 'struct mount'. File system modules need to be
1338 Bump __FreeBSD_version to 800093.
1341 The compiling option ADAPTIVE_SX has been retired while it has been
1342 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1343 The KPI for sx_init_flags() changes as accepting flags:
1344 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1345 been introduced in order to handle the reversed logic.
1346 Bump __FreeBSD_version to 800092.
1349 Add support for hierarchical jails. Remove global securelevel.
1350 Bump __FreeBSD_version to 800091.
1353 The layout of struct vnet_net has changed, therefore modules
1355 Bump __FreeBSD_version to 800090.
1358 The newly imported zic(8) produces a new format in the output. Please
1359 run tzsetup(8) to install the newly created data to /etc/localtime.
1362 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1363 hw.usb.* and is now consistent again with previous releases.
1366 802.11 monitor mode support was revised and driver api's were changed.
1367 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1368 of DLT_IEEE802_11. No user-visible data structures were changed but
1369 applications that use DLT_IEEE802_11 may require changes.
1370 Bump __FreeBSD_version to 800088.
1373 The layout of the following structs has changed: sysctl_oid,
1374 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1375 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1376 panics may be experienced. World rebuild is required for
1377 correctly checking networking state from userland.
1378 Bump __FreeBSD_version to 800085.
1381 MLDv2 and Source-Specific Multicast (SSM) have been merged
1382 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1383 The implementation of SSM within FreeBSD's IPv6 stack closely
1384 follows the IPv4 implementation.
1386 For kernel developers:
1388 * The most important changes are that the ip6_output() and
1389 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1390 and this lock has been downgraded to a non-recursive mutex.
1392 * As with the changes to the IPv4 stack to support SSM, filtering
1393 of inbound multicast traffic must now be performed by transport
1394 protocols within the IPv6 stack. This does not apply to TCP and
1395 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1397 * The KPIs used by IPv6 multicast are similar to those used by
1398 the IPv4 stack, with the following differences:
1399 * im6o_mc_filter() is analogous to imo_multicast_filter().
1400 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1401 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1402 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1403 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1404 for MLDv1 have an additional 'timer' argument which is used to
1405 jitter the initial membership report for the solicited-node
1406 multicast membership on-link.
1407 * This is not strictly needed for MLDv2, which already jitters
1408 its report transmissions. However, the 'timer' argument is
1409 preserved in case MLDv1 is active on the interface.
1411 * The KAME linked-list based IPv6 membership implementation has
1412 been refactored to use a vector similar to that used by the IPv4
1414 Code which maintains a list of its own multicast memberships
1415 internally, e.g. carp, has been updated to reflect the new
1418 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1419 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1420 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1421 implementation constraint which needs to be addressed in HEAD.
1423 For application developers:
1425 * The changes are broadly similar to those made for the IPv4
1428 * The use of IPv4 and IPv6 multicast socket options on the same
1429 socket, using mapped addresses, HAS NOT been tested or supported.
1431 * There are a number of issues with the implementation of various
1432 IPv6 multicast APIs which need to be resolved in the API surface
1433 before the implementation is fully compatible with KAME userland
1434 use, and these are mostly to do with interface index treatment.
1436 * The literature available discusses the use of either the delta / ASM
1437 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1438 using setsourcefilter(3)/getsourcefilter(3). For more information
1439 please refer to RFC 3768, 'Socket Interface Extensions for
1440 Multicast Source Filters'.
1442 * Applications which use the published RFC 3678 APIs should be fine.
1444 For systems administrators:
1446 * The mtest(8) utility has been refactored to support IPv6, in
1447 addition to IPv4. Interface addresses are no longer accepted
1448 as arguments, their names must be used instead. The utility
1449 will map the interface name to its first IPv4 address as
1450 returned by getifaddrs(3).
1452 * The ifmcstat(8) utility has also been updated to print the MLDv2
1453 endpoint state and source filter lists via sysctl(3).
1455 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1456 loopback of IPv6 multicast datagrams by default; it defaults to 1
1457 to preserve the existing behaviour. Disabling multicast loopback is
1458 recommended for optimal system performance.
1460 * The IPv6 MROUTING code has been changed to examine this sysctl
1461 instead of attempting to perform a group lookup before looping
1462 back forwarded datagrams.
1464 Bump __FreeBSD_version to 800084.
1467 Implement low-level Bluetooth HCI API.
1468 Bump __FreeBSD_version to 800083.
1471 The layout of struct malloc_type, used by modules to register new
1472 memory allocation types, has changed. Most modules will need to
1473 be rebuilt or panics may be experienced.
1474 Bump __FreeBSD_version to 800081.
1477 Anticipate overflowing inp_flags - add inp_flags2.
1478 This changes most offsets in inpcb, so checking v4 connection
1479 state will require a world rebuild.
1480 Bump __FreeBSD_version to 800080.
1483 Add an llentry to struct route and struct route_in6. Modules
1484 embedding a struct route will need to be recompiled.
1485 Bump __FreeBSD_version to 800079.
1488 The size of rt_metrics_lite and by extension rtentry has changed.
1489 Networking administration apps will need to be recompiled.
1490 The route command now supports show as an alias for get, weighting
1491 of routes, sticky and nostick flags to alter the behavior of stateful
1493 Bump __FreeBSD_version to 800078.
1496 Do not use Giant for kbdmux(4) locking. This is wrong and
1497 apparently causing more problems than it solves. This will
1498 re-open the issue where interrupt handlers may race with
1499 kbdmux(4) in polling mode. Typical symptoms include (but
1500 not limited to) duplicated and/or missing characters when
1501 low level console functions (such as gets) are used while
1502 interrupts are enabled (for example geli password prompt,
1503 mountroot prompt etc.). Disabling kbdmux(4) may help.
1506 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1507 kernel modules referencing any of the above need to be recompiled.
1508 Bump __FreeBSD_version to 800075.
1511 GEOM_PART has become the default partition slicer for storage devices,
1512 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1513 introduces some changes:
1515 MSDOS/EBR: the devices created from MSDOS extended partition entries
1516 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1517 to devices with offset-based names. fstabs may need to be modified.
1519 BSD: the "geometry does not match label" warning is harmless in most
1520 cases but it points to problems in file system misalignment with
1521 disk geometry. The "c" partition is now implicit, covers the whole
1522 top-level drive and cannot be (mis)used by users.
1524 General: Kernel dumps are now not allowed to be written to devices
1525 whose partition types indicate they are meant to be used for file
1526 systems (or, in case of MSDOS partitions, as something else than
1529 Most of these changes date approximately from 200812.
1532 The uscanner(4) driver has been removed from the kernel. This follows
1533 Linux removing theirs in 2.6 and making libusb the default interface
1534 (supported by sane).
1537 The multicast forwarding code has been cleaned up. netstat(1)
1538 only relies on KVM now for printing bandwidth upcall meters.
1539 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1540 ip6_mroute_mod respectively. The config(5) options for statically
1541 compiling this code remain the same, i.e. 'options MROUTING'.
1544 Support for the IFF_NEEDSGIANT network interface flag has been
1545 removed, which means that non-MPSAFE network device drivers are no
1546 longer supported. In particular, if_ar, if_sr, and network device
1547 drivers from the old (legacy) USB stack can no longer be built or
1551 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1552 a bunch of new language catalog files have also been added.
1553 This means that some common libc messages are now localized and
1554 they depend on the LC_MESSAGES environmental variable.
1557 The k8temp(4) driver has been renamed to amdtemp(4) since
1558 support for Family 10 and Family 11 CPU families was added.
1561 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1562 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1564 For kernel developers, the most important changes are that the
1565 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1566 and this lock has been downgraded to a non-recursive mutex.
1568 Transport protocols (UDP, Raw IP) are now responsible for filtering
1569 inbound multicast traffic according to group membership and source
1570 filters. The imo_multicast_filter() KPI exists for this purpose.
1571 Transports which do not use multicast (SCTP, TCP) already reject
1572 multicast by default. Forwarding and receive performance may improve
1573 as a mutex acquisition is no longer needed in the ip_input()
1574 low-level input path. in_addmulti() and in_delmulti() are shimmed
1575 to new KPIs which exist to support SSM in-kernel.
1577 For application developers, it is recommended that loopback of
1578 multicast datagrams be disabled for best performance, as this
1579 will still cause the lock to be taken for each looped-back
1580 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1581 be tuned to 0 to disable loopback by default; it defaults to 1
1582 to preserve the existing behaviour.
1584 For systems administrators, to obtain best performance with
1585 multicast reception and multiple groups, it is always recommended
1586 that a card with a suitably precise hash filter is used. Hash
1587 collisions will still result in the lock being taken within the
1588 transport protocol input path to check group membership.
1590 If deploying FreeBSD in an environment with IGMP snooping switches,
1591 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1592 enabled; this forces 224.0.0.0/24 group membership to be announced
1595 The size of 'struct igmpstat' has changed; netstat needs to be
1596 recompiled to reflect this.
1597 Bump __FreeBSD_version to 800070.
1600 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1601 updated to use it. This requires a buildworld/installworld in order to
1602 update the library and dependencies (usbconfig, etc). Its advisable to
1603 rebuild all ports which uses libusb. More specific directions are given
1604 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1605 libusb are no longer required and can be removed.
1608 A workaround is committed to allow the creation of System V shared
1609 memory segment of size > 2 GB on the 64-bit architectures.
1610 Due to a limitation of the existing ABI, the shm_segsz member
1611 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1612 wrong for large segments. Note that limits must be explicitly
1613 raised to allow such segments to be created.
1616 The layout of struct ifnet has changed, requiring a rebuild of all
1617 network device driver modules.
1620 The /dev handling for the new USB stack has changed, a
1621 buildworld/installworld is required for libusb20.
1624 The new USB2 stack has now been permanently moved in and all kernel and
1625 module names reverted to their previous values (eg, usb, ehci, ohci,
1626 ums, ...). The old usb stack can be compiled in by prefixing the name
1627 with the letter 'o', the old usb modules have been removed.
1628 Updating entry 20090216 for xorg and 20090215 for libmap may still
1632 The rc.conf(5) option if_up_delay has been renamed to
1633 defaultroute_delay to better reflect its purpose. If you have
1634 customized this setting in /etc/rc.conf you need to update it to
1638 xorg 7.4 wants to configure its input devices via hald which does not
1639 yet work with USB2. If the keyboard/mouse does not work in xorg then
1641 Option "AllowEmptyInput" "off"
1642 to your ServerLayout section. This will cause X to use the configured
1643 kbd and mouse sections from your xorg.conf.
1646 The GENERIC kernels for all architectures now default to the new USB2
1647 stack. No kernel config options or code have been removed so if a
1648 problem arises please report it and optionally revert to the old USB
1649 stack. If you are loading USB kernel modules or have a custom kernel
1650 that includes GENERIC then ensure that usb names are also changed over,
1651 eg uftdi -> usb2_serial_ftdi.
1653 Older programs linked against the ports libusb 0.1 need to be
1654 redirected to the new stack's libusb20. /etc/libmap.conf can
1656 # Map old usb library to new one for usb2 stack
1657 libusb-0.1.so.8 libusb20.so.1
1660 All USB ethernet devices now attach as interfaces under the name ueN
1661 (eg. ue0). This is to provide a predictable name as vendors often
1662 change usb chipsets in a product without notice.
1665 The ichsmb(4) driver has been changed to require SMBus slave
1666 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1667 All of the other SMBus controller drivers require left-justified
1668 slave addresses, so this change makes all the drivers provide the
1672 INET6 statistics (struct ip6stat) was updated.
1673 netstat(1) needs to be recompiled.
1676 NTFS has been removed from GENERIC kernel on amd64 to match
1677 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1678 will load ntfs.ko module automatically when NTFS support is
1679 actually needed, unless ntfs.ko is not installed or security
1680 level prohibits loading kernel modules. If either is the case,
1681 "options NTFS" has to be added into kernel config.
1684 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1685 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1686 800061. User space tools that rely on the size of struct tcpcb in
1687 tcp_var.h (e.g. sockstat) need to be recompiled.
1690 ng_tty(4) module updated to match the new TTY subsystem.
1691 Due to API change, user-level applications must be updated.
1692 New API support added to mpd5 CVS and expected to be present
1693 in next mpd5.3 release.
1696 With __FreeBSD_version 800060 the makefs tool is part of
1697 the base system (it was a port).
1700 The afdata and ifnet locks have been changed from mutexes to
1701 rwlocks, network modules will need to be re-compiled.
1704 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1705 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1706 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1707 architecture and 40 bytes on 64-bit architecture. The userland
1708 applications "arp" and "ndp" have been updated accordingly.
1709 The output from "netstat -r" shows only routing entries and
1710 none of the L2 information.
1713 __FreeBSD_version 800057 marks the switchover from the
1714 binary ath hal to source code. Users must add the line:
1716 options AH_SUPPORT_AR5416
1718 to their kernel config files when specifying:
1722 The ath_hal module no longer exists; the code is now compiled
1723 together with the driver in the ath module. It is now
1724 possible to tailor chip support (i.e. reduce the set of chips
1725 and thereby the code size); consult ath_hal(4) for details.
1728 __FreeBSD_version 800054 adds memory barriers to
1729 <machine/atomic.h>, new interfaces to ifnet to facilitate
1730 multiple hardware transmit queues for cards that support
1731 them, and a lock-less ring-buffer implementation to
1732 enable drivers to more efficiently manage queueing of
1736 A new version of ZFS (version 13) has been merged to -HEAD.
1737 This version has zpool attribute "listsnapshots" off by
1738 default, which means "zfs list" does not show snapshots,
1739 and is the same as Solaris behavior.
1742 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1745 The uhci, ohci, ehci and slhci USB Host controller drivers have
1746 been put into separate modules. If you load the usb module
1747 separately through loader.conf you will need to load the
1748 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1749 controller add the following to loader.conf:
1755 The ABI used by the PMC toolset has changed. Please keep
1756 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1760 atapci kernel module now includes only generic PCI ATA
1761 driver. AHCI driver moved to ataahci kernel module.
1762 All vendor-specific code moved into separate kernel modules:
1763 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1764 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1765 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1766 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1769 The TTY subsystem of the kernel has been replaced by a new
1770 implementation, which provides better scalability and an
1771 improved driver model. Most common drivers have been migrated to
1772 the new TTY subsystem, while others have not. The following
1773 drivers have not yet been ported to the new TTY layer:
1776 cy, digi, rc, rp, sio
1782 ng_h4, ng_tty, ppp, sl, snp
1784 Adding these drivers to your kernel configuration file shall
1785 cause compilation to fail.
1788 ntpd has been upgraded to 4.2.4p5.
1791 OpenSSH has been upgraded to 5.1p1.
1793 For many years, FreeBSD's version of OpenSSH preferred DSA
1794 over RSA for host and user authentication keys. With this
1795 upgrade, we've switched to the vendor's default of RSA over
1796 DSA. This may cause upgraded clients to warn about unknown
1797 host keys even for previously known hosts. Users should
1798 follow the usual procedure for verifying host keys before
1799 accepting the RSA key.
1801 This can be circumvented by setting the "HostKeyAlgorithms"
1802 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1805 Please note that the sequence of keys offered for
1806 authentication has been changed as well. You may want to
1807 specify IdentityFile in a different order to revert this
1811 The sio(4) driver has been removed from the i386 and amd64
1812 kernel configuration files. This means uart(4) is now the
1813 default serial port driver on those platforms as well.
1815 To prevent collisions with the sio(4) driver, the uart(4) driver
1816 uses different names for its device nodes. This means the
1817 onboard serial port will now most likely be called "ttyu0"
1818 instead of "ttyd0". You may need to reconfigure applications to
1819 use the new device names.
1821 When using the serial port as a boot console, be sure to update
1822 /boot/device.hints and /etc/ttys before booting the new kernel.
1823 If you forget to do so, you can still manually specify the hints
1824 at the loader prompt:
1826 set hint.uart.0.at="isa"
1827 set hint.uart.0.port="0x3F8"
1828 set hint.uart.0.flags="0x10"
1829 set hint.uart.0.irq="4"
1833 The gpt(8) utility has been removed. Use gpart(8) to partition
1837 The version that Linuxulator emulates was changed from 2.4.2
1838 to 2.6.16. If you experience any problems with Linux binaries
1839 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1840 if it fixes the problem contact emulation mailing list.
1843 ISDN4BSD (I4B) was removed from the src tree. You may need to
1844 update a your kernel configuration and remove relevant entries.
1847 I have checked in code to support multiple routing tables.
1848 See the man pages setfib(1) and setfib(2).
1849 This is a hopefully backwards compatible version,
1850 but to make use of it you need to compile your kernel
1851 with options ROUTETABLES=2 (or more up to 16).
1854 The 802.11 wireless support was redone to enable multi-bss
1855 operation on devices that are capable. The underlying device
1856 is no longer used directly but instead wlanX devices are
1857 cloned with ifconfig. This requires changes to rc.conf files.
1858 For example, change:
1859 ifconfig_ath0="WPA DHCP"
1862 ifconfig_wlan0="WPA DHCP"
1863 see rc.conf(5) for more details. In addition, mergemaster of
1864 /etc/rc.d is highly recommended. Simultaneous update of userland
1865 and kernel wouldn't hurt either.
1867 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1868 modules were merged into the base wlan module. All references
1869 to these modules (e.g. in kernel config files) must be removed.
1872 psm(4) has gained write(2) support in native operation level.
1873 Arbitrary commands can be written to /dev/psm%d and status can
1874 be read back from it. Therefore, an application is responsible
1875 for status validation and error recovery. It is a no-op in
1876 other operation levels.
1879 Support for KSE threading has been removed from the kernel. To
1880 run legacy applications linked against KSE libmap.conf may
1881 be used. The following libmap.conf may be used to ensure
1882 compatibility with any prior release:
1884 libpthread.so.1 libthr.so.1
1885 libpthread.so.2 libthr.so.2
1886 libkse.so.3 libthr.so.3
1889 The layout of struct vmspace has changed. This affects libkvm
1890 and any executables that link against libkvm and use the
1891 kvm_getprocs() function. In particular, but not exclusively,
1892 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1893 The effects are minimal, but it's advisable to upgrade world
1897 The latest em driver no longer has support in it for the
1898 82575 adapter, this is now moved to the igb driver. The
1899 split was done to make new features that are incompatible
1900 with older hardware easier to do.
1903 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1904 likewise the kernel option is now GEOM_LINUX_LVM.
1907 The default NFS mount mode has changed from UDP to TCP for
1908 increased reliability. If you rely on (insecurely) NFS
1909 mounting across a firewall you may need to update your
1913 Belatedly note the addition of m_collapse for compacting
1917 The fts(3) structures have been changed to use adequate
1918 integer types for their members and so to be able to cope
1919 with huge file trees. The old fts(3) ABI is preserved
1920 through symbol versioning in libc, so third-party binaries
1921 using fts(3) should still work, although they will not take
1922 advantage of the extended types. At the same time, some
1923 third-party software might fail to build after this change
1924 due to unportable assumptions made in its source code about
1925 fts(3) structure members. Such software should be fixed
1926 by its vendor or, in the worst case, in the ports tree.
1927 FreeBSD_version 800015 marks this change for the unlikely
1928 case that a portable fix is impossible.
1931 To upgrade to -current after this date, you must be running
1932 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1933 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1936 The ADAPTIVE_GIANT kernel option has been retired because its
1937 functionality is the default now.
1940 The AT keyboard emulation of sunkbd(4) has been turned on
1941 by default. In order to make the special symbols of the Sun
1942 keyboards driven by sunkbd(4) work under X these now have
1943 to be configured the same way as Sun USB keyboards driven
1944 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1946 Option "XkbLayout" "us"
1947 Option "XkbRules" "xorg"
1948 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1951 It has been decided that it is desirable to provide ABI
1952 backwards compatibility to the FreeBSD 4/5/6 versions of the
1953 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1954 broken with the introduction of PCI domain support (see the
1955 20070930 entry). Unfortunately, this required the ABI of
1956 PCIOCGETCONF to be broken again in order to be able to
1957 provide backwards compatibility to the old version of that
1958 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1959 again. As for prominent ports this affects neither pciutils
1960 nor xorg-server this time, the hal port needs to be rebuilt
1964 The misnamed kthread_create() and friends have been renamed
1965 to kproc_create() etc. Many of the callers already
1966 used kproc_start()..
1967 I will return kthread_create() and friends in a while
1968 with implementations that actually create threads, not procs.
1969 Renaming corresponds with version 800002.
1978 Avoid using make -j when upgrading. While generally safe, there are
1979 sometimes problems using -j to upgrade. If your upgrade fails with
1980 -j, please try again without -j. From time to time in the past there
1981 have been problems using -j with buildworld and/or installworld. This
1982 is especially true when upgrading between "distant" versions (eg one
1983 that cross a major release boundary or several minor releases, or when
1984 several months have passed on the -current branch).
1986 Sometimes, obscure build problems are the result of environment
1987 poisoning. This can happen because the make utility reads its
1988 environment when searching for values for global variables. To run
1989 your build attempts in an "environmental clean room", prefix all make
1990 commands with 'env -i '. See the env(1) manual page for more details.
1992 When upgrading from one major version to another it is generally best
1993 to upgrade to the latest code in the currently installed branch first,
1994 then do an upgrade to the new branch. This is the best-tested upgrade
1995 path, and has the highest probability of being successful. Please try
1996 this approach before reporting problems with a major version upgrade.
1998 When upgrading a live system, having a root shell around before
1999 installing anything can help undo problems. Not having a root shell
2000 around can lead to problems if pam has changed too much from your
2001 starting point to allow continued authentication after the upgrade.
2005 When upgrading the boot ZFS pool to a new version, always follow
2008 1.) recompile and reinstall the ZFS boot loader and boot block
2009 (this is part of "make buildworld" and "make installworld")
2011 2.) update the ZFS boot block on your boot drive
2013 The following example updates the ZFS boot block on the first
2014 partition (freebsd-boot) of a GPT partitioned drive ad0:
2015 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2017 Non-boot pools do not need these updates.
2021 If you are updating from a prior version of FreeBSD (even one just
2022 a few days old), you should follow this procedure. It is the most
2023 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2025 make kernel-toolchain
2026 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2027 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2029 To test a kernel once
2030 ---------------------
2031 If you just want to boot a kernel once (because you are not sure
2032 if it works, or if you want to boot a known bad kernel to provide
2033 debugging information) run
2034 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2035 nextboot -k testkernel
2037 To just build a kernel when you know that it won't mess you up
2038 --------------------------------------------------------------
2039 This assumes you are already running a CURRENT system. Replace
2040 ${arch} with the architecture of your machine (e.g. "i386",
2041 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2043 cd src/sys/${arch}/conf
2044 config KERNEL_NAME_HERE
2045 cd ../compile/KERNEL_NAME_HERE
2050 If this fails, go to the "To build a kernel" section.
2052 To rebuild everything and install it on the current system.
2053 -----------------------------------------------------------
2054 # Note: sometimes if you are running current you gotta do more than
2055 # is listed here if you are upgrading from a really old current.
2057 <make sure you have good level 0 dumps>
2059 make kernel KERNCONF=YOUR_KERNEL_HERE
2061 <reboot in single user> [3]
2068 To cross-install current onto a separate partition
2069 --------------------------------------------------
2070 # In this approach we use a separate partition to hold
2071 # current's root, 'usr', and 'var' directories. A partition
2072 # holding "/", "/usr" and "/var" should be about 2GB in
2075 <make sure you have good level 0 dumps>
2078 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2079 <maybe newfs current's root partition>
2080 <mount current's root partition on directory ${CURRENT_ROOT}>
2081 make installworld DESTDIR=${CURRENT_ROOT}
2082 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2083 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2084 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2085 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2086 <reboot into current>
2087 <do a "native" rebuild/install as described in the previous section>
2088 <maybe install compatibility libraries from ports/misc/compat*>
2092 To upgrade in-place from stable to current
2093 ----------------------------------------------
2094 <make sure you have good level 0 dumps>
2096 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2098 <reboot in single user> [3]
2105 Make sure that you've read the UPDATING file to understand the
2106 tweaks to various things you need. At this point in the life
2107 cycle of current, things change often and you are on your own
2108 to cope. The defaults can also change, so please read ALL of
2109 the UPDATING entries.
2111 Also, if you are tracking -current, you must be subscribed to
2112 freebsd-current@freebsd.org. Make sure that before you update
2113 your sources that you have read and understood all the recent
2114 messages there. If in doubt, please track -stable which has
2115 much fewer pitfalls.
2117 [1] If you have third party modules, such as vmware, you
2118 should disable them at this point so they don't crash your
2121 [3] From the bootblocks, boot -s, and then do
2126 adjkerntz -i # if CMOS is wall time
2127 Also, when doing a major release upgrade, it is required that
2128 you boot into single user mode to do the installworld.
2130 [4] Note: This step is non-optional. Failure to do this step
2131 can result in a significant reduction in the functionality of the
2132 system. Attempting to do it by hand is not recommended and those
2133 that pursue this avenue should read this file carefully, as well
2134 as the archives of freebsd-current and freebsd-hackers mailing lists
2135 for potential gotchas. The -U option is also useful to consider.
2136 See mergemaster(8) for more information.
2138 [5] Usually this step is a noop. However, from time to time
2139 you may need to do this if you get unknown user in the following
2140 step. It never hurts to do it all the time. You may need to
2141 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2142 install) after the buildworld before this step if you last updated
2143 from current before 20130425 or from -stable before 20130430.
2145 [6] This only deletes old files and directories. Old libraries
2146 can be deleted by "make delete-old-libs", but you have to make
2147 sure that no program is using those libraries anymore.
2149 [8] In order to have a kernel that can run the 4.x binaries needed to
2150 do an installworld, you must include the COMPAT_FREEBSD4 option in
2151 your kernel. Failure to do so may leave you with a system that is
2152 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2153 required to run the 5.x binaries on more recent kernels. And so on
2154 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2156 Make sure that you merge any new devices from GENERIC since the
2157 last time you updated your kernel config file.
2159 [9] When checking out sources, you must include the -P flag to have
2160 cvs prune empty directories.
2162 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2163 "?=" instead of the "=" assignment operator, so that buildworld can
2164 override the CPUTYPE if it needs to.
2166 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2167 not on the command line, or in /etc/make.conf. buildworld will
2168 warn if it is improperly defined.
2171 This file contains a list, in reverse chronological order, of major
2172 breakages in tracking -current. It is not guaranteed to be a complete
2173 list of such breakages, and only contains entries since October 10, 2007.
2174 If you need to see UPDATING entries from before that date, you will need
2175 to fetch an UPDATING file from an older FreeBSD release.
2177 Copyright information:
2179 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2181 Redistribution, publication, translation and use, with or without
2182 modification, in full or in part, in any form or format of this
2183 document are permitted without further permission from the author.
2185 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2186 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2187 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2188 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2189 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2190 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2191 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2192 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2193 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2194 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2195 POSSIBILITY OF SUCH DAMAGE.
2197 Contact Warner Losh if you have any questions about your use of