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 20141223: p3 FreeBSD-SA-14:31.ntp
20 FreeBSD-EN-14:13.freebsd-update
22 Fix multiple vulnerabilities in NTP suite. [SA-14:31]
23 Fix directory deletion issue in freebsd-update. [EN-14:13]
25 20141217: p2 FreeBSD-SA-14:30.unbound
26 Fix unbound remote denial of service vulnerability.
28 20141210: p1 FreeBSD-SA-14:27.stdio
31 Fix buffer overflow in stdio. [SA-14:27]
33 Fix multiple vulnerabilities in file(1) and libmagic(3).
37 The ofwfb driver, used to provide a graphics console on PowerPC when
38 using vt(4), no longer allows mmap() of all of physical memory. This
39 will prevent Xorg on PowerPC with some ATI graphics cards from
40 initializing properly unless x11-servers/xorg-server is updated to
44 The libatf-c and libatf-c++ major versions were downgraded to 0 and
45 1 respectively to match the upstream numbers. They were out of
46 sync because, when they were originally added to FreeBSD, the
47 upstream versions were not respected. These libraries are private
48 and not yet built by default, so renumbering them should be a
49 non-issue. However, unclean source trees will yield broken test
50 programs once the operator executes "make delete-old-libs" after a
53 Additionally, the atf-sh binary was made private by moving it into
54 /usr/libexec/. Already-built shell test programs will keep the
55 path to the old binary so they will break after "make delete-old"
58 If you are using WITH_TESTS=yes (not the default), wipe the object
59 tree and rebuild from scratch to prevent spurious test failures.
60 This is only needed once: the misnumbered libraries and misplaced
61 binaries have been added to OptionalObsoleteFiles.inc so they will
62 be removed during a clean upgrade.
65 The ixgbe tunables now match their sysctl counterparts, for example:
66 hw.ixgbe.enable_aim => hw.ix.enable_aim
67 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
70 The NFSv4.1 server committed by r269398 changes the internal
71 function call interfaces used between the NFS and krpc modules.
72 As such, __FreeBSD_version was bumped.
75 The default unbound configuration has been modified to address
76 issues with reverse lookups on networks that use private
77 address ranges. If you use the local_unbound service, run
78 "service local_unbound setup" as root to regenerate your
79 configuration, then "service local_unbound reload" to load the
83 It is no longer necessary to include the dwarf version in your DEBUG
84 options in your kernel config file. The bug that required it to be
85 placed in the config file has bene fixed. DEBUG should now just
86 contain -g. The build system will automatically update things
87 to do the right thing.
90 Several ABI breaking changes were merged to CTL and new iSCSI code.
91 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
92 iscsictl need to be rebuilt to work with a new kernel.
95 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
96 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
97 which differs from the behaviour controlled by this knob.)
100 On i386 and amd64 systems, the onifconsole flag is now set by default
101 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
102 as a login TTY if it is set in the bootloader as an active kernel
103 console. No changes in behavior should result otherwise. To revert to
104 the previous behavior, set ttyu0 to "off" in /etc/ttys.
107 Clang and llvm have been upgraded to 3.4.1 release.
110 Clang and llvm have been upgraded to 3.4 release.
113 If a Makefile in a tests/ directory was auto-generating a Kyuafile
114 instead of providing an explicit one, this would prevent such
115 Makefile from providing its own Kyuafile in the future during
116 NO_CLEAN builds. This has been fixed in the Makefiles but manual
117 intervention is needed to clean an objdir if you use NO_CLEAN:
118 # find /usr/obj -name Kyuafile | xargs rm -f
121 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
122 capability mode support. Please note that enabling the feature in
123 kernel is still highly recommended.
126 OpenSSH is now built with sandbox support, and will use sandbox as
127 the default privilege separation method. This requires Capsicum
128 capability mode support in kernel.
131 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
132 been deprecated and will not be part of FreeBSD 11.0 and later
133 releases. If you use this driver, please consider switching to
134 the nfe(4) driver instead.
140 The behavior of gss_pseudo_random() for the krb5 mechanism
141 has changed, for applications requesting a longer random string
142 than produced by the underlying enctype's pseudo-random() function.
143 In particular, the random string produced from a session key of
144 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
145 be different at the 17th octet and later, after this change.
146 The counter used in the PRF+ construction is now encoded as a
147 big-endian integer in accordance with RFC 4402.
148 __FreeBSD_version is bumped to 1000701.
151 The WITHOUT_ATF build knob has been removed and its functionality
152 has been subsumed into the more generic WITHOUT_TESTS. If you were
153 using the former to disable the build of the ATF libraries, you
154 should change your settings to use the latter.
157 The default version of mtree is nmtree which is obtained from
158 NetBSD. The output is generally the same, but may vary
159 slightly. If you found you need identical output adding
160 "-F freebsd9" to the command line should do the trick. For the
161 time being, the old mtree is available as fmtree.
164 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
165 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
166 1.1.4_8 and verify bsdyml not linked in, before running "make
168 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
170 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
173 The rc.d/jail script has been updated to support jail(8)
174 configuration file. The "jail_<jname>_*" rc.conf(5) variables
175 for per-jail configuration are automatically converted to
176 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
177 This is transparently backward compatible. See below about some
178 incompatibilities and rc.conf(5) manual page for more details.
180 These variables are now deprecated in favor of jail(8) configuration
181 file. One can use "rc.d/jail config <jname>" command to generate
182 a jail(8) configuration file in /var/run/jail.<jname>.conf without
183 running the jail(8) utility. The default pathname of the
184 configuration file is /etc/jail.conf and can be specified by
185 using $jail_conf or $jail_<jname>_conf variables.
187 Please note that jail_devfs_ruleset accepts an integer at
188 this moment. Please consider to rewrite the ruleset name
192 BIND has been removed from the base system. If all you need
193 is a local resolver, simply enable and start the local_unbound
194 service instead. Otherwise, several versions of BIND are
195 available in the ports tree. The dns/bind99 port is one example.
197 With this change, nslookup(1) and dig(1) are no longer in the base
198 system. Users should instead use host(1) and drill(1) which are
199 in the base system. Alternatively, nslookup and dig can
200 be obtained by installing the dns/bind-tools port.
203 With the addition of unbound(8), a new unbound user is now
204 required during installworld. "mergemaster -p" can be used to
205 add the user prior to installworld, as documented in the handbook.
208 OpenSSH is now built with DNSSEC support, and will by default
209 silently trust signed SSHFP records. This can be controlled with
210 the VerifyHostKeyDNS client configuration setting. DNSSEC support
211 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
214 The GNU Compiler Collection and C++ standard library (libstdc++)
215 are no longer built by default on platforms where clang is the system
216 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
220 The PROCDESC kernel option is now part of the GENERIC kernel
221 configuration and is required for the rwhod(8) to work.
222 If you are using custom kernel configuration, you should include
226 The API and ABI related to the Capsicum framework was modified
227 in backward incompatible way. The userland libraries and programs
228 have to be recompiled to work with the new kernel. This includes the
229 following libraries and programs, but the whole buildworld is
230 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
231 kdump, procstat, rwho, rwhod, uniq.
234 AES-NI intrinsic support has been added to gcc. The AES-NI module
235 has been updated to use this support. A new gcc is required to build
236 the aesni module on both i386 and amd64.
239 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
240 Thus "device padlock_rng" and "device rdrand_rng" should be
241 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
244 WITH_ICONV has been split into two feature sets. WITH_ICONV now
245 enables just the iconv* functionality and is now on by default.
246 WITH_LIBICONV_COMPAT enables the libiconv api and link time
247 compatability. Set WITHOUT_ICONV to build the old way.
248 If you have been using WITH_ICONV before, you will very likely
249 need to turn on WITH_LIBICONV_COMPAT.
252 INVARIANTS option now enables DEBUG for code with OpenSolaris and
253 Illumos origin, including ZFS. If you have INVARIANTS in your
254 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
256 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
257 locks if WITNESS option was set. Because that generated a lot of
258 witness(9) reports and all of them were believed to be false
259 positives, this is no longer done. New option OPENSOLARIS_WITNESS
260 can be used to achieve the previous behavior.
263 Timer values in IPv6 data structures now use time_uptime instead
264 of time_second. Although this is not a user-visible functional
265 change, userland utilities which directly use them---ndp(8),
266 rtadvd(8), and rtsold(8) in the base system---need to be updated
270 find -delete can now delete the pathnames given as arguments,
271 instead of only files found below them or if the pathname did
272 not contain any slashes. Formerly, the following error message
275 find: -delete: <path>: relative path potentially not safe
277 Deleting the pathnames given as arguments can be prevented
278 without error messages using -mindepth 1 or by changing
279 directory and passing "." as argument to find. This works in the
280 old as well as the new version of find.
283 Behavior of devfs rules path matching has been changed.
284 Pattern is now always matched against fully qualified devfs
285 path and slash characters must be explicitly matched by
286 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
287 subdirectories must be reviewed.
290 The default ARM ABI has changed to the ARM EABI. The old ABI is
291 incompatible with the ARM EABI and all programs and modules will
292 need to be rebuilt to work with a new kernel.
294 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
296 NOTE: Support for the old ABI will be removed in the future and
297 users are advised to upgrade.
300 pkg_install has been disconnected from the build if you really need it
301 you should add WITH_PKGTOOLS in your src.conf(5).
304 Most of network statistics structures were changed to be able
305 keep 64-bits counters. Thus all tools, that work with networking
306 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
309 Fix targets that run multiple make's to use && rather than ;
310 so that subsequent steps depend on success of previous.
312 NOTE: if building 'universe' with -j* on stable/8 or stable/9
313 it would be better to start the build using bmake, to avoid
314 overloading the machine.
317 Fix a bug that allowed a tracing process (e.g. gdb) to write
318 to a memory-mapped file in the traced process's address space
319 even if neither the traced process nor the tracing process had
320 write access to that file.
323 CVS has been removed from the base system. An exact copy
324 of the code is available from the devel/cvs port.
327 Some people report the following error after the switch to bmake:
329 make: illegal option -- J
330 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
332 *** [buildworld] Error code 2
334 this likely due to an old instance of make in
335 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
336 which src/Makefile will use that blindly, if it exists, so if
337 you see the above error:
339 rm -rf `make -V MAKEPATH`
344 Use bmake by default.
345 Whereas before one could choose to build with bmake via
346 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
347 make. The goal is to remove these knobs for 10-RELEASE.
349 It is worth noting that bmake (like gmake) treats the command
350 line as the unit of failure, rather than statements within the
351 command line. Thus '(cd some/where && dosomething)' is safer
352 than 'cd some/where; dosomething'. The '()' allows consistent
353 behavior in parallel build.
356 Fix a bug that allows NFS clients to issue READDIR on files.
359 The WITHOUT_IDEA option has been removed because
360 the IDEA patent expired.
363 The sysctl which controls TRIM support under ZFS has been renamed
364 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
368 The mergemaster command now uses the default MAKEOBJDIRPREFIX
369 rather than creating it's own in the temporary directory in
370 order allow access to bootstrapped versions of tools such as
371 install and mtree. When upgrading from version of FreeBSD where
372 the install command does not support -l, you will need to
373 install a new mergemaster command if mergemaster -p is required.
374 This can be accomplished with the command (cd src/usr.sbin/mergemaster
378 Legacy ATA stack, disabled and replaced by new CAM-based one since
379 FreeBSD 9.0, completely removed from the sources. Kernel modules
380 atadisk and atapi*, user-level tools atacontrol and burncd are
381 removed. Kernel option `options ATA_CAM` is now permanently enabled
385 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
386 and socketpair(2). Software, in particular Kerberos, may
387 automatically detect and use these during building. The resulting
388 binaries will not work on older kernels.
391 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
392 information, see the respective 20130304 entry).
395 Recent commits to callout(9) changed the size of struct callout,
396 so the KBI is probably heavily disturbed. Also, some functions
397 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
398 by macros. Every kernel module using it won't load, so rebuild
401 The ctl device has been re-enabled in GENERIC for i386 and amd64,
402 but does not initialize by default (because of the new CTL_DISABLE
403 option) to save memory. To re-enable it, remove the CTL_DISABLE
404 option from the kernel config file or set kern.cam.ctl.disable=0
405 in /boot/loader.conf.
408 The ctl device has been disabled in GENERIC for i386 and amd64.
409 This was done due to the extra memory being allocated at system
410 initialisation time by the ctl driver which was only used if
411 a CAM target device was created. This makes a FreeBSD system
412 unusable on 128MB or less of RAM.
415 A new compression method (lz4) has been merged to -HEAD. Please
416 refer to zpool-features(7) for more information.
418 Please refer to the "ZFS notes" section of this file for information
419 on upgrading boot ZFS pools.
422 A BSD-licensed patch(1) variant has been added and is installed
423 as bsdpatch, being the GNU version the default patch.
424 To inverse the logic and use the BSD-licensed one as default,
425 while having the GNU version installed as gnupatch, rebuild
426 and install world with the WITH_BSD_PATCH knob set.
429 Due to the use of the new -l option to install(1) during build
430 and install, you must take care not to directly set the INSTALL
431 make variable in your /etc/make.conf, /etc/src.conf, or on the
432 command line. If you wish to use the -C flag for all installs
433 you may be able to add INSTALL+=-C to /etc/make.conf or
437 The install(1) option -M has changed meaning and now takes an
438 argument that is a file or path to append logs to. In the
439 unlikely event that -M was the last option on the command line
440 and the command line contained at least two files and a target
441 directory the first file will have logs appended to it. The -M
442 option served little practical purpose in the last decade so its
443 use is expected to be extremely rare.
446 After switching to Clang as the default compiler some users of ZFS
447 on i386 systems started to experience stack overflow kernel panics.
448 Please consider using 'options KSTACK_PAGES=4' in such configurations.
451 GEOM_LABEL now mangles label names read from file system metadata.
452 Mangling affect labels containing spaces, non-printable characters,
453 '%' or '"'. Device names in /etc/fstab and other places may need to
457 By default, only the 10 most recent kernel dumps will be saved. To
458 restore the previous behaviour (no limit on the number of kernel dumps
459 stored in the dump directory) add the following line to /etc/rc.conf:
464 With the addition of auditdistd(8), a new auditdistd user is now
465 required during installworld. "mergemaster -p" can be used to
466 add the user prior to installworld, as documented in the handbook.
469 The sin6_scope_id member variable in struct sockaddr_in6 is now
470 filled by the kernel before passing the structure to the userland via
471 sysctl or routing socket. This means the KAME-specific embedded scope
472 id in sin6_addr.s6_addr[2] is always cleared in userland application.
473 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
474 __FreeBSD_version is bumped to 1000025.
477 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
478 This means that the world and kernel will be compiled with clang
479 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
480 and /usr/bin/cpp. To disable this behavior and revert to building
481 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
482 of current may need to bootstrap WITHOUT_CLANG first if the clang
483 build fails (its compatibility window doesn't extend to the 9 stable
487 The IPFIREWALL_FORWARD kernel option has been removed. Its
488 functionality now turned on by default.
491 The ZERO_COPY_SOCKET kernel option has been removed and
492 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
493 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
494 mechanism which is not safe and may result in kernel crashes.
495 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
496 driver supports disposeable external page sized mbuf storage.
497 Proper replacements for both zero-copy mechanisms are under
498 consideration and will eventually lead to complete removal
499 of the two kernel options.
502 The IPv4 network stack has been converted to network byte
503 order. The following modules need to be recompiled together
504 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
505 pf(4), ipfw(4), ng_ipfw(4), stf(4).
508 Support for non-MPSAFE filesystems was removed from VFS. The
509 VFS_VERSION was bumped, all filesystem modules shall be
513 All the non-MPSAFE filesystems have been disconnected from
514 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
515 portalfs, smbfs, xfs.
518 The interface cloning API and ABI has changed. The following
519 modules need to be recompiled together with kernel:
520 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
521 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
522 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
525 The sdhci driver was split in two parts: sdhci (generic SD Host
526 Controller logic) and sdhci_pci (actual hardware driver).
527 No kernel config modifications are required, but if you
528 load sdhc as a module you must switch to sdhci_pci instead.
531 Import the FUSE kernel and userland support into base system.
534 The GNU sort(1) program has been removed since the BSD-licensed
535 sort(1) has been the default for quite some time and no serious
536 problems have been reported. The corresponding WITH_GNU_SORT
540 The pfil(9) API/ABI for AF_INET family has been changed. Packet
541 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
545 The net80211(4) ABI has been changed to allow for improved driver
546 PS-POLL and power-save support. All wireless drivers need to be
547 recompiled to work with the new kernel.
550 The random(4) support for the VIA hardware random number
551 generator (`PADLOCK') is no longer enabled unconditionally.
552 Add the padlock_rng device in the custom kernel config if
553 needed. The GENERIC kernels on i386 and amd64 do include the
554 device, so the change only affects the custom kernel
558 The pf(4) packet filter ABI has been changed. pfctl(8) and
559 snmp_pf module need to be recompiled to work with new kernel.
562 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
563 to -HEAD. Pools that have empty_bpobj in active state can not be
564 imported read-write with ZFS implementations that do not support
565 this feature. For more information read the zpool-features(5)
569 The sparc64 ZFS loader has been changed to no longer try to auto-
570 detect ZFS providers based on diskN aliases but now requires these
571 to be explicitly listed in the OFW boot-device environment variable.
574 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
575 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
576 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
579 The following sysctls and tunables have been renamed for consistency
580 with other variables:
581 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
582 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
585 The sort utility has been replaced with BSD sort. For now, GNU sort
586 is also available as "gnusort" or the default can be set back to
587 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
588 installed as "bsdsort".
591 A new version of ZFS (pool version 5000) has been merged to -HEAD.
592 Starting with this version the old system of ZFS pool versioning
593 is superseded by "feature flags". This concept enables forward
594 compatibility against certain future changes in functionality of ZFS
595 pools. The first read-only compatible "feature flag" for ZFS pools
596 is named "com.delphix:async_destroy". For more information
597 read the new zpool-features(5) manual page.
598 Please refer to the "ZFS notes" section of this file for information
599 on upgrading boot ZFS pools.
602 The malloc(3) implementation embedded in libc now uses sources imported
603 as contrib/jemalloc. The most disruptive API change is to
604 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
605 delete it prior to installworld, and optionally re-create it using the
606 new format after rebooting. See malloc.conf(5) for details
607 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
611 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
612 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
613 now spelled mips. This is to aid compatibility with third-party
614 software that expects this naming scheme in uname(3). Little-endian
615 settings are unchanged. If you are updating a big-endian mips64 machine
616 from before this change, you may need to set MACHINE_ARCH=mips64 in
617 your environment before the new build system will recognize your machine.
620 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
624 Now unix domain sockets behave "as expected" on nullfs(5). Previously
625 nullfs(5) did not pass through all behaviours to the underlying layer,
626 as a result if we bound to a socket on the lower layer we could connect
627 only to the lower path; if we bound to the upper layer we could connect
628 only to the upper path. The new behavior is one can connect to both the
629 lower and the upper paths regardless what layer path one binds to.
632 The getifaddrs upgrade path broken with 20111215 has been restored.
633 If you have upgraded in between 20111215 and 20120209 you need to
634 recompile libc again with your kernel. You still need to recompile
635 world to be able to configure CARP but this restriction already
639 The set_rcvar() function has been removed from /etc/rc.subr. All
640 base and ports rc.d scripts have been updated, so if you have a
641 port installed with a script in /usr/local/etc/rc.d you can either
642 hand-edit the rcvar= line, or reinstall the port.
644 An easy way to handle the mass-update of /etc/rc.d:
645 rm /etc/rc.d/* && mergemaster -i
648 panic(9) now stops other CPUs in the SMP systems, disables interrupts
649 on the current CPU and prevents other threads from running.
650 This behavior can be reverted using the kern.stop_scheduler_on_panic
652 The new behavior can be incompatible with kern.sync_on_panic.
655 The carp(4) facility has been changed significantly. Configuration
656 of the CARP protocol via ifconfig(8) has changed, as well as format
657 of CARP events submitted to devd(8) has changed. See manual pages
658 for more information. The arpbalance feature of carp(4) is currently
659 not supported anymore.
661 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
662 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
663 need to be recompiled.
666 The acpi_wmi(4) status device /dev/wmistat has been renamed to
670 The option VFS_ALLOW_NONMPSAFE option has been added in order to
671 explicitely support non-MPSAFE filesystems.
672 It is on by default for all supported platform at this present
676 The broken amd(4) driver has been replaced with esp(4) in the amd64,
677 i386 and pc98 GENERIC kernel configuration files.
680 sysinstall has been removed
683 The stable/9 branch created in subversion. This corresponds to the
684 RELENG_9 branch in CVS.
687 This commit modifies vfs_register() so that it uses a hash
688 calculation to set vfc_typenum, which is enabled by default.
689 The first time a system is booted after this change, the
690 vfc_typenum values will change for all file systems. The
691 main effect of this is a change to the NFS server file handles
692 for file systems that use vfc_typenum in their fsid, such as ZFS.
693 It will, however, prevent vfc_typenum from changing when file
694 systems are loaded in a different order for subsequent reboots.
695 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
696 until you are ready to remount all NFS clients after a reboot.
699 Bump the shared library version numbers for libraries that
700 do not use symbol versioning, have changed the ABI compared
701 to stable/8 and which shared library version was not bumped.
702 Done as part of 9.0-RELEASE cycle.
705 During the merge of Capsicum features, the fget(9) KPI was modified.
706 This may require the rebuilding of out-of-tree device drivers --
707 issues have been reported specifically with the nVidia device driver.
708 __FreeBSD_version is bumped to 900041.
710 Also, there is a period between 20110811 and 20110814 where the
711 special devices /dev/{stdin,stdout,stderr} did not work correctly.
712 Building world from a kernel during that window may not work.
715 The packet filter (pf) code has been updated to OpenBSD 4.5.
716 You need to update userland tools to be in sync with kernel.
717 This update breaks backward compatibility with earlier pfsync(4)
718 versions. Care must be taken when updating redundant firewall setups.
721 The following sysctls and tunables are retired on x86 platforms:
723 machdep.hlt_logical_cpus
724 The following sysctl is retired:
725 machdep.hyperthreading_allowed
726 The sysctls were supposed to provide a way to dynamically offline and
727 online selected CPUs on x86 platforms, but the implementation has not
728 been reliable especially with SCHED_ULE scheduler.
729 machdep.hyperthreading_allowed tunable is still available to ignore
730 hyperthreading CPUs at OS level.
731 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
732 where X is an APIC ID of a CPU. Be advised, though, that disabling
733 CPUs in non-uniform fashion will result in non-uniform topology and
734 may lead to sub-optimal system performance with SCHED_ULE, which is
738 cpumask_t type is retired and cpuset_t is used in order to describe
742 Changes to ifconfig(8) for dynamic address family detection mandate
743 that you are running a kernel of 20110525 or later. Make sure to
744 follow the update procedure to boot a new kernel before installing
748 Support for sun4v architecture is officially dropped
751 Several KPI breaking changes have been committed to the mii(4) layer,
752 the PHY drivers and consequently some Ethernet drivers using mii(4).
753 This means that miibus.ko and the modules of the affected Ethernet
754 drivers need to be recompiled.
756 Note to kernel developers: Given that the OUI bit reversion problem
757 was fixed as part of these changes all mii(4) commits related to OUIs,
758 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
759 handling, no longer can be merged verbatim to stable/8 and previous
763 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
764 into their kernel configurations along with 'device pci'.
767 The default NFS client is now the new NFS client, so fstype "newnfs"
768 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
769 Although mounts via fstype "nfs" will usually work without userland
770 changes, it is recommended that the mount(8) and mount_nfs(8)
771 commands be rebuilt from sources and that a link to mount_nfs called
772 mount_oldnfs be created. The new client is compiled into the
773 kernel with "options NFSCL" and this is needed for diskless root
774 file systems. The GENERIC kernel configs have been changed to use
775 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
776 To use the regular/old client, you can "mount -t oldnfs ...". For
777 a diskless root file system, you must also include a line like:
779 vfs.root.mountfrom="oldnfs:"
781 in the boot/loader.conf on the root fs on the NFS server to make
782 a diskless root fs use the old client.
785 The GENERIC kernels for all architectures now default to the new
786 CAM-based ATA stack. It means that all legacy ATA drivers were
787 removed and replaced by respective CAM drivers. If you are using
788 ATA device names in /etc/fstab or other places, make sure to update
789 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
790 where 'Y's are the sequential numbers starting from zero for each type
791 in order of detection, unless configured otherwise with tunables,
792 see cam(4)). There will be symbolic links created in /dev/ to map
793 old adX devices to the respective adaY. They should provide basic
794 compatibility for file systems mounting in most cases, but they do
795 not support old user-level APIs and do not have respective providers
796 in GEOM. Consider using updated management tools with new device names.
798 It is possible to load devices ahci, ata, siis and mvs as modules,
799 but option ATA_CAM should remain in kernel configuration to make ata
800 module work as CAM driver supporting legacy ATA controllers. Device ata
801 still can be used in modular fashion (atacore + ...). Modules atadisk
802 and atapi* are not used and won't affect operation in ATA_CAM mode.
803 Note that to use CAM-based ATA kernel should include CAM devices
804 scbus, pass, da (or explicitly ada), cd and optionally others. All of
805 them are parts of the cam module.
807 ataraid(4) functionality is now supported by the RAID GEOM class.
808 To use it you can load geom_raid kernel module and use graid(8) tool
809 for management. Instead of /dev/arX device names, use /dev/raid/rX.
811 No kernel config options or code have been removed, so if a problem
812 arises, please report it and optionally revert to the old ATA stack.
813 In order to do it you can remove from the kernel config:
818 , and instead add back:
819 device atadisk # ATA disk drives
820 device ataraid # ATA RAID drives
821 device atapicd # ATAPI CDROM drives
822 device atapifd # ATAPI floppy drives
823 device atapist # ATAPI tape drives
826 The default NFS server has been changed to the new server, which
827 was referred to as the experimental server. If you need to switch
828 back to the old NFS server, you must now put the "-o" option on
829 both the mountd and nfsd commands. This can be done using the
830 mountd_flags and nfs_server_flags rc.conf variables until an
831 update to the rc scripts is committed, which is coming soon.
834 The GNU Objective-C runtime library (libobjc), and other Objective-C
835 related components have been removed from the base system. If you
836 require an Objective-C library, please use one of the available ports.
839 ath(4) has been split into bus- and device- modules. if_ath contains
840 the HAL, the TX rate control and the network device code. if_ath_pci
841 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
842 contains the AHB glue. Users need to load both if_ath_pci and if_ath
843 in order to use ath on everything else.
845 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
846 need to load if_ath and if_ath_pci for ath(4) operation.
849 As part of the replacement of sysinstall, the process of building
850 release media has changed significantly. For details, please re-read
851 release(7), which has been updated to reflect the new build process.
854 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
855 is the last available version under GPLv2. It brings a number of new
856 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
857 4.1 and SSE 4.2), better support for powerpc64, a number of new
858 directives, and lots of other small improvements. See the ChangeLog
859 file in contrib/binutils for the full details.
862 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
863 compliant, and will now use half of hash for authentication.
864 This will break interoperability with all stacks (including all
865 actual FreeBSD versions) who implement
866 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
868 The only workaround with such peers is to use another HMAC
869 algorithm for IPsec ("phase 2") authentication.
872 Remove the uio_yield prototype and symbol. This function has
873 been misnamed since it was introduced and should not be
874 globally exposed with this name. The equivalent functionality
875 is now available using kern_yield(curthread->td_user_pri).
876 The function remains undocumented.
879 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
880 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
881 for scalar sysctls is defined but disabled. Code that needs
882 UQUAD to pass the type checking that must compile on older
883 systems where the define is not present can check against
884 __FreeBSD_version >= 900030.
886 The system dialog(1) has been replaced with a new version previously
887 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
888 with the previous version, but the libdialog associated with it has
889 a largely incompatible API. As such, the original version of libdialog
890 will be kept temporarily as libodialog, until its base system consumers
891 are replaced or updated. Bump __FreeBSD_version to 900030.
894 If you are trying to run make universe on a -stable system, and you get
895 the following warning:
896 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
897 unknown. config(8) likely too old."
898 or something similar to it, then you must upgrade your -stable system
899 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
900 stable/8) or build the config from the latest stable/8 branch and
901 install it on your system.
903 Prior to this date, building a current universe on 8-stable system from
904 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
905 error in the first kernel build phase. A new config on those old
906 systems will fix that problem for older versions of -current.
909 The TCP stack has been modified to allow Khelp modules to interact with
910 it via helper hook points and store per-connection data in the TCP
911 control block. Bump __FreeBSD_version to 900029. User space tools that
912 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
916 Generic IEEE 802.3 annex 31B full duplex flow control support has been
917 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
918 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
919 to take advantage of it instead of using custom implementations. This
920 means that these drivers now no longer unconditionally advertise
921 support for flow control but only do so if flow control is a selected
922 media option. This was implemented in the generic support that way in
923 order to allow flow control to be switched on and off via ifconfig(8)
924 with the PHY specific default to typically off in order to protect
925 from unwanted effects. Consequently, if you used flow control with
926 one of the above mentioned drivers you now need to explicitly enable
928 ifconfig bge0 media auto mediaopt flowcontrol
930 Along with the above mentioned changes generic support for setting
931 1000baseT master mode also has been added and brgphy(4), ciphy(4),
932 e1000phy(4) as well as ip1000phy(4) have been converted to take
933 advantage of it. This means that these drivers now no longer take the
934 link0 parameter for selecting master mode but the master media option
935 has to be used instead, for example like in the following:
936 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
938 Selection of master mode now is also available with all other PHY
939 drivers supporting 1000baseT.
942 The TCP stack has received a significant update to add support for
943 modularised congestion control and generally improve the clarity of
944 congestion control decisions. Bump __FreeBSD_version to 900025. User
945 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
946 sockstat) need to be recompiled.
949 The man(1) utility has been replaced by a new version that no longer
950 uses /etc/manpath.config. Please consult man.conf(5) for how to
951 migrate local entries to the new format.
954 The copyright strings printed by login(1) and sshd(8) at the time of a
955 new connection have been removed to follow other operating systems and
959 A workaround for a fixed ld bug has been removed in kernel code,
960 so make sure that your system ld is built from sources after
961 revision 210245 from 2010-07-19 (r211583 if building head kernel
962 on stable/8, r211584 for stable/7; both from 2010-08-21).
963 A symptom of incorrect ld version is different addresses for
964 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
967 The $ipv6_prefer variable in rc.conf(5) has been split into
968 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
970 The $ip6addrctl_policy is a variable to choose a pre-defined
971 address selection policy set by ip6addrctl(8). A value
972 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
975 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
976 flag (see an entry of 20090926) is set on an interface with no
977 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
978 security reason. If you want IPv6 link-local address on all
979 interfaces by default, set this to "YES".
981 The old ipv6_prefer="YES" is equivalent to
982 ipv6_activate_all_interfaces="YES" and
983 ip6addrctl_policy="ipv6_prefer".
986 DTrace has grown support for userland tracing. Due to this, DTrace is
987 now i386 and amd64 only.
988 dtruss(1) is now installed by default on those systems and a new
989 kernel module is needed for userland tracing: fasttrap.
990 No changes to your kernel config file are necessary to enable
991 userland tracing, but you might consider adding 'STRIP=' and
992 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
993 to have informative userland stack traces in DTrace (ustack).
996 The acpi_aiboost(4) driver has been removed in favor of the new
997 aibs(4) driver. You should update your kernel configuration file.
1000 BSD grep has been imported to the base system and it is built by
1001 default. It is completely BSD licensed, highly GNU-compatible, uses
1002 less memory than its GNU counterpart and has a small codebase.
1003 However, it is slower than its GNU counterpart, which is mostly
1004 noticeable for larger searches, for smaller ones it is measurable
1005 but not significant. The reason is complex, the most important factor
1006 is that we lack a modern and efficient regex library and GNU
1007 overcomes this by optimizing the searches internally. Future work
1008 on improving the regex performance is planned, for the meantime,
1009 users that need better performance, can build GNU grep instead by
1010 setting the WITH_GNU_GREP knob.
1013 Due to the import of powerpc64 support, all existing powerpc kernel
1014 configuration files must be updated with a machine directive like this:
1015 machine powerpc powerpc
1017 In addition, an updated config(8) is required to build powerpc kernels
1021 A new version of ZFS (version 15) has been merged to -HEAD.
1022 This version uses a python library for the following subcommands:
1023 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1024 For full functionality of these commands the following port must
1025 be installed: sysutils/py-zfs
1028 'vm_page's are now hashed by physical address to an array of mutexes.
1029 Currently this is only used to serialize access to hold_count. Over
1030 time the page queue mutex will be peeled away. This changes the size
1031 of pmap on every architecture. And requires all callers of vm_page_hold
1032 and vm_page_unhold to be updated.
1035 WITH_CTF can now be specified in src.conf (not recommended, there
1036 are some problems with static executables), make.conf (would also
1037 affect ports which do not use GNU make and do not override the
1038 compile targets) or in the kernel config (via "makeoptions
1040 When WITH_CTF was specified there before this was silently ignored,
1041 so make sure that WITH_CTF is not used in places which could lead
1042 to unwanted behavior.
1045 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1046 to allow 32-bit compatibility on non-x86 platforms. All kernel
1047 configurations on amd64 and ia64 platforms using these options must
1048 be modified accordingly.
1051 The utmp user accounting database has been replaced with utmpx,
1052 the user accounting interface standardized by POSIX.
1053 Unfortunately the semantics of utmp and utmpx don't match,
1054 making it practically impossible to support both interfaces.
1055 The user accounting database is used by tools like finger(1),
1056 last(1), talk(1), w(1) and ac(8).
1058 All applications in the base system use utmpx. This means only
1059 local binaries (e.g. from the ports tree) may still use these
1060 utmp database files. These applications must be rebuilt to make
1063 After the system has been upgraded, it is safe to remove the old
1064 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1065 assuming their contents is of no importance anymore. Old wtmp
1066 databases can only be used by last(1) and ac(8) after they have
1067 been converted to the new format using wtmpcvt(1).
1070 Introduce the kernel thread "deadlock resolver" (which can be enabled
1071 via the DEADLKRES option, see NOTES for more details) and the
1072 sleepq_type() function for sleepqueues.
1075 The rc.firewall and rc.firewall6 were unified, and
1076 rc.firewall6 and rc.d/ip6fw were removed.
1077 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1078 variables are obsoleted. Instead, the following new rc
1079 variables are added to rc.d/ipfw:
1081 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1082 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1083 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1085 The meanings correspond to the relevant IPv4 variables.
1091 The default terminal emulation for syscons(4) has been changed
1092 from cons25 to xterm on all platforms except pc98. This means
1093 that the /etc/ttys file needs to be updated to ensure correct
1094 operation of applications on the console.
1096 The terminal emulation style can be toggled per window by using
1097 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1098 options can be used to change the compile-time default back to
1101 To prevent graphical artifacts, make sure the TERM environment
1102 variable is set to match the terminal emulation that is being
1103 performed by syscons(4).
1106 The layout of the structure ieee80211req_scan_result has changed.
1107 Applications that require wireless scan results (e.g. ifconfig(8))
1108 from net80211 need to be recompiled.
1110 Applications such as wpa_supplicant(8) may require a full world
1111 build without using NO_CLEAN in order to get synchronized with the
1115 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1116 There's one kernel module for each firmware. Adding "device iwnfw"
1117 to the kernel configuration file means including all three firmware
1118 images inside the kernel. If you want to include just the one for
1119 your wireless card, use the devices iwn4965fw, iwn5000fw or
1123 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1124 into rc.d/netif. The changes are the following:
1126 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1127 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1128 Note that both variables need the "inet6" keyword at the head.
1130 Do not set $ipv6_network_interfaces manually if you do not
1131 understand what you are doing. It is not needed in most cases.
1133 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1136 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1137 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1139 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1140 all configured interfaces have "inet6 accept_rtadv" in the
1141 $ifconfig_IF_ipv6. These are for backward compatibility.
1143 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1144 functionality of interfaces with no corresponding
1145 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1146 and the default address selection policy of ip6addrctl(8)
1147 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1148 Note that if you want to configure IPv6 functionality on the
1149 disabled interfaces after boot, first you need to clear the flag by
1150 using ifconfig(8) like:
1152 ifconfig em0 inet6 -ifdisabled
1154 If YES, the default address selection policy is set as
1157 The default value of $ipv6_prefer is NO.
1159 4. If your system need to receive Router Advertisement messages,
1160 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1161 scripts automatically invoke rtsol(8) when the interface becomes
1162 UP. The Router Advertisement messages are used for SLAAC
1163 (State-Less Address AutoConfiguration).
1166 802.11s D3.03 support was committed. This is incompatible with the
1167 previous code, which was based on D3.0.
1170 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1171 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1172 control whether accepting Router Advertisement messages or not.
1173 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1174 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1175 The ifconfig(8) utility now supports these flags.
1178 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1179 mount(8) and -a option for df(1) to see them.
1182 The old tunable hw.bus.devctl_disable has been superseded by
1183 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1184 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1188 Remove the option STOP_NMI. The default action is now to use NMI only
1189 for KDB via the newly introduced function stop_cpus_hard() and
1190 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1193 The stable/8 branch created in subversion. This corresponds to the
1194 RELENG_8 branch in CVS.
1197 Bump the shared library version numbers for all libraries that do not
1198 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1199 __FreeBSD_version to 800105.
1202 Due to changes in the implementation of virtual network stack support,
1203 all network-related kernel modules must be recompiled. As this change
1204 breaks the ABI, bump __FreeBSD_version to 800104.
1207 The TOE interface to the TCP syncache has been modified to remove
1208 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1209 The cxgb driver is the only TOE consumer affected by this change, and
1210 needs to be recompiled along with the kernel. As this change breaks
1211 the ABI, bump __FreeBSD_version to 800103.
1214 Padding has been added to struct tcpcb, sackhint and tcpstat in
1215 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1216 maintaining the ABI. However, this change breaks the ABI, so bump
1217 __FreeBSD_version to 800102. User space tools that rely on the size of
1218 any of these structs (e.g. sockstat) need to be recompiled.
1221 The NFS_LEGACYRPC option has been removed along with the old kernel
1222 RPC implementation that this option selected. Kernel configurations
1223 may need to be adjusted.
1226 The network interface device nodes at /dev/net/<interface> have been
1227 removed. All ioctl operations can be performed the normal way using
1228 routing sockets. The kqueue functionality can generally be replaced
1229 with routing sockets.
1232 The documentation from the FreeBSD Documentation Project (Handbook,
1233 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1234 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1237 The ABI of various structures related to the SYSV IPC API have been
1238 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1239 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1243 Layout of struct vnet has changed as routing related variables were
1244 moved to their own Vimage module. Modules need to be recompiled. Bump
1245 __FreeBSD_version to 800099.
1248 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1249 respectively. As long as no more than 16 groups per process are used,
1250 no changes should be visible. When more than 16 groups are used, old
1251 binaries may fail if they call getgroups() or getgrouplist() with
1252 statically sized storage. Recompiling will work around this, but
1253 applications should be modified to use dynamically allocated storage
1254 for group arrays as POSIX.1-2008 does not cap an implementation's
1255 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1257 NFS and portalfs mounts may also be affected as the list of groups is
1258 truncated to 16. Users of NFS who use more than 16 groups, should
1259 take care that negative group permissions are not used on the exported
1260 file systems as they will not be reliable unless a GSSAPI based
1261 authentication method is used.
1264 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1265 option compiles in the support for adaptive spinning for lockmgrs
1266 which want to enable it. The lockinit() function now accepts the flag
1267 LK_ADAPTIVE in order to make the lock object subject to adaptive
1268 spinning when both held in write and read mode.
1271 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1272 changed. User applications that use this ioctl need to be rebuilt.
1275 The layout of struct thread has changed. Kernel and modules need to
1279 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1280 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1283 window(1) has been removed from the base system. It can now be
1284 installed from ports. The port is called misc/window.
1287 The way we are storing and accessing `routing table' entries has
1288 changed. Programs reading the FIB, like netstat, need to be
1292 A new netisr implementation has been added for FreeBSD 8. Network
1293 file system modules, such as igmp, ipdivert, and others, should be
1295 Bump __FreeBSD_version to 800096.
1298 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1302 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1303 Bump __FreeBSD_version to 800094.
1306 Add mnt_xflag field to 'struct mount'. File system modules need to be
1308 Bump __FreeBSD_version to 800093.
1311 The compiling option ADAPTIVE_SX has been retired while it has been
1312 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1313 The KPI for sx_init_flags() changes as accepting flags:
1314 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1315 been introduced in order to handle the reversed logic.
1316 Bump __FreeBSD_version to 800092.
1319 Add support for hierarchical jails. Remove global securelevel.
1320 Bump __FreeBSD_version to 800091.
1323 The layout of struct vnet_net has changed, therefore modules
1325 Bump __FreeBSD_version to 800090.
1328 The newly imported zic(8) produces a new format in the output. Please
1329 run tzsetup(8) to install the newly created data to /etc/localtime.
1332 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1333 hw.usb.* and is now consistent again with previous releases.
1336 802.11 monitor mode support was revised and driver api's were changed.
1337 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1338 of DLT_IEEE802_11. No user-visible data structures were changed but
1339 applications that use DLT_IEEE802_11 may require changes.
1340 Bump __FreeBSD_version to 800088.
1343 The layout of the following structs has changed: sysctl_oid,
1344 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1345 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1346 panics may be experienced. World rebuild is required for
1347 correctly checking networking state from userland.
1348 Bump __FreeBSD_version to 800085.
1351 MLDv2 and Source-Specific Multicast (SSM) have been merged
1352 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1353 The implementation of SSM within FreeBSD's IPv6 stack closely
1354 follows the IPv4 implementation.
1356 For kernel developers:
1358 * The most important changes are that the ip6_output() and
1359 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1360 and this lock has been downgraded to a non-recursive mutex.
1362 * As with the changes to the IPv4 stack to support SSM, filtering
1363 of inbound multicast traffic must now be performed by transport
1364 protocols within the IPv6 stack. This does not apply to TCP and
1365 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1367 * The KPIs used by IPv6 multicast are similar to those used by
1368 the IPv4 stack, with the following differences:
1369 * im6o_mc_filter() is analogous to imo_multicast_filter().
1370 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1371 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1372 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1373 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1374 for MLDv1 have an additional 'timer' argument which is used to
1375 jitter the initial membership report for the solicited-node
1376 multicast membership on-link.
1377 * This is not strictly needed for MLDv2, which already jitters
1378 its report transmissions. However, the 'timer' argument is
1379 preserved in case MLDv1 is active on the interface.
1381 * The KAME linked-list based IPv6 membership implementation has
1382 been refactored to use a vector similar to that used by the IPv4
1384 Code which maintains a list of its own multicast memberships
1385 internally, e.g. carp, has been updated to reflect the new
1388 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1389 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1390 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1391 implementation constraint which needs to be addressed in HEAD.
1393 For application developers:
1395 * The changes are broadly similar to those made for the IPv4
1398 * The use of IPv4 and IPv6 multicast socket options on the same
1399 socket, using mapped addresses, HAS NOT been tested or supported.
1401 * There are a number of issues with the implementation of various
1402 IPv6 multicast APIs which need to be resolved in the API surface
1403 before the implementation is fully compatible with KAME userland
1404 use, and these are mostly to do with interface index treatment.
1406 * The literature available discusses the use of either the delta / ASM
1407 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1408 using setsourcefilter(3)/getsourcefilter(3). For more information
1409 please refer to RFC 3768, 'Socket Interface Extensions for
1410 Multicast Source Filters'.
1412 * Applications which use the published RFC 3678 APIs should be fine.
1414 For systems administrators:
1416 * The mtest(8) utility has been refactored to support IPv6, in
1417 addition to IPv4. Interface addresses are no longer accepted
1418 as arguments, their names must be used instead. The utility
1419 will map the interface name to its first IPv4 address as
1420 returned by getifaddrs(3).
1422 * The ifmcstat(8) utility has also been updated to print the MLDv2
1423 endpoint state and source filter lists via sysctl(3).
1425 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1426 loopback of IPv6 multicast datagrams by default; it defaults to 1
1427 to preserve the existing behaviour. Disabling multicast loopback is
1428 recommended for optimal system performance.
1430 * The IPv6 MROUTING code has been changed to examine this sysctl
1431 instead of attempting to perform a group lookup before looping
1432 back forwarded datagrams.
1434 Bump __FreeBSD_version to 800084.
1437 Implement low-level Bluetooth HCI API.
1438 Bump __FreeBSD_version to 800083.
1441 The layout of struct malloc_type, used by modules to register new
1442 memory allocation types, has changed. Most modules will need to
1443 be rebuilt or panics may be experienced.
1444 Bump __FreeBSD_version to 800081.
1447 Anticipate overflowing inp_flags - add inp_flags2.
1448 This changes most offsets in inpcb, so checking v4 connection
1449 state will require a world rebuild.
1450 Bump __FreeBSD_version to 800080.
1453 Add an llentry to struct route and struct route_in6. Modules
1454 embedding a struct route will need to be recompiled.
1455 Bump __FreeBSD_version to 800079.
1458 The size of rt_metrics_lite and by extension rtentry has changed.
1459 Networking administration apps will need to be recompiled.
1460 The route command now supports show as an alias for get, weighting
1461 of routes, sticky and nostick flags to alter the behavior of stateful
1463 Bump __FreeBSD_version to 800078.
1466 Do not use Giant for kbdmux(4) locking. This is wrong and
1467 apparently causing more problems than it solves. This will
1468 re-open the issue where interrupt handlers may race with
1469 kbdmux(4) in polling mode. Typical symptoms include (but
1470 not limited to) duplicated and/or missing characters when
1471 low level console functions (such as gets) are used while
1472 interrupts are enabled (for example geli password prompt,
1473 mountroot prompt etc.). Disabling kbdmux(4) may help.
1476 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1477 kernel modules referencing any of the above need to be recompiled.
1478 Bump __FreeBSD_version to 800075.
1481 GEOM_PART has become the default partition slicer for storage devices,
1482 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1483 introduces some changes:
1485 MSDOS/EBR: the devices created from MSDOS extended partition entries
1486 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1487 to devices with offset-based names. fstabs may need to be modified.
1489 BSD: the "geometry does not match label" warning is harmless in most
1490 cases but it points to problems in file system misalignment with
1491 disk geometry. The "c" partition is now implicit, covers the whole
1492 top-level drive and cannot be (mis)used by users.
1494 General: Kernel dumps are now not allowed to be written to devices
1495 whose partition types indicate they are meant to be used for file
1496 systems (or, in case of MSDOS partitions, as something else than
1499 Most of these changes date approximately from 200812.
1502 The uscanner(4) driver has been removed from the kernel. This follows
1503 Linux removing theirs in 2.6 and making libusb the default interface
1504 (supported by sane).
1507 The multicast forwarding code has been cleaned up. netstat(1)
1508 only relies on KVM now for printing bandwidth upcall meters.
1509 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1510 ip6_mroute_mod respectively. The config(5) options for statically
1511 compiling this code remain the same, i.e. 'options MROUTING'.
1514 Support for the IFF_NEEDSGIANT network interface flag has been
1515 removed, which means that non-MPSAFE network device drivers are no
1516 longer supported. In particular, if_ar, if_sr, and network device
1517 drivers from the old (legacy) USB stack can no longer be built or
1521 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1522 a bunch of new language catalog files have also been added.
1523 This means that some common libc messages are now localized and
1524 they depend on the LC_MESSAGES environmental variable.
1527 The k8temp(4) driver has been renamed to amdtemp(4) since
1528 support for Family 10 and Family 11 CPU families was added.
1531 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1532 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1534 For kernel developers, the most important changes are that the
1535 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1536 and this lock has been downgraded to a non-recursive mutex.
1538 Transport protocols (UDP, Raw IP) are now responsible for filtering
1539 inbound multicast traffic according to group membership and source
1540 filters. The imo_multicast_filter() KPI exists for this purpose.
1541 Transports which do not use multicast (SCTP, TCP) already reject
1542 multicast by default. Forwarding and receive performance may improve
1543 as a mutex acquisition is no longer needed in the ip_input()
1544 low-level input path. in_addmulti() and in_delmulti() are shimmed
1545 to new KPIs which exist to support SSM in-kernel.
1547 For application developers, it is recommended that loopback of
1548 multicast datagrams be disabled for best performance, as this
1549 will still cause the lock to be taken for each looped-back
1550 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1551 be tuned to 0 to disable loopback by default; it defaults to 1
1552 to preserve the existing behaviour.
1554 For systems administrators, to obtain best performance with
1555 multicast reception and multiple groups, it is always recommended
1556 that a card with a suitably precise hash filter is used. Hash
1557 collisions will still result in the lock being taken within the
1558 transport protocol input path to check group membership.
1560 If deploying FreeBSD in an environment with IGMP snooping switches,
1561 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1562 enabled; this forces 224.0.0.0/24 group membership to be announced
1565 The size of 'struct igmpstat' has changed; netstat needs to be
1566 recompiled to reflect this.
1567 Bump __FreeBSD_version to 800070.
1570 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1571 updated to use it. This requires a buildworld/installworld in order to
1572 update the library and dependencies (usbconfig, etc). Its advisable to
1573 rebuild all ports which uses libusb. More specific directions are given
1574 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1575 libusb are no longer required and can be removed.
1578 A workaround is committed to allow the creation of System V shared
1579 memory segment of size > 2 GB on the 64-bit architectures.
1580 Due to a limitation of the existing ABI, the shm_segsz member
1581 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1582 wrong for large segments. Note that limits must be explicitly
1583 raised to allow such segments to be created.
1586 The layout of struct ifnet has changed, requiring a rebuild of all
1587 network device driver modules.
1590 The /dev handling for the new USB stack has changed, a
1591 buildworld/installworld is required for libusb20.
1594 The new USB2 stack has now been permanently moved in and all kernel and
1595 module names reverted to their previous values (eg, usb, ehci, ohci,
1596 ums, ...). The old usb stack can be compiled in by prefixing the name
1597 with the letter 'o', the old usb modules have been removed.
1598 Updating entry 20090216 for xorg and 20090215 for libmap may still
1602 The rc.conf(5) option if_up_delay has been renamed to
1603 defaultroute_delay to better reflect its purpose. If you have
1604 customized this setting in /etc/rc.conf you need to update it to
1608 xorg 7.4 wants to configure its input devices via hald which does not
1609 yet work with USB2. If the keyboard/mouse does not work in xorg then
1611 Option "AllowEmptyInput" "off"
1612 to your ServerLayout section. This will cause X to use the configured
1613 kbd and mouse sections from your xorg.conf.
1616 The GENERIC kernels for all architectures now default to the new USB2
1617 stack. No kernel config options or code have been removed so if a
1618 problem arises please report it and optionally revert to the old USB
1619 stack. If you are loading USB kernel modules or have a custom kernel
1620 that includes GENERIC then ensure that usb names are also changed over,
1621 eg uftdi -> usb2_serial_ftdi.
1623 Older programs linked against the ports libusb 0.1 need to be
1624 redirected to the new stack's libusb20. /etc/libmap.conf can
1626 # Map old usb library to new one for usb2 stack
1627 libusb-0.1.so.8 libusb20.so.1
1630 All USB ethernet devices now attach as interfaces under the name ueN
1631 (eg. ue0). This is to provide a predictable name as vendors often
1632 change usb chipsets in a product without notice.
1635 The ichsmb(4) driver has been changed to require SMBus slave
1636 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1637 All of the other SMBus controller drivers require left-justified
1638 slave addresses, so this change makes all the drivers provide the
1642 INET6 statistics (struct ip6stat) was updated.
1643 netstat(1) needs to be recompiled.
1646 NTFS has been removed from GENERIC kernel on amd64 to match
1647 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1648 will load ntfs.ko module automatically when NTFS support is
1649 actually needed, unless ntfs.ko is not installed or security
1650 level prohibits loading kernel modules. If either is the case,
1651 "options NTFS" has to be added into kernel config.
1654 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1655 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1656 800061. User space tools that rely on the size of struct tcpcb in
1657 tcp_var.h (e.g. sockstat) need to be recompiled.
1660 ng_tty(4) module updated to match the new TTY subsystem.
1661 Due to API change, user-level applications must be updated.
1662 New API support added to mpd5 CVS and expected to be present
1663 in next mpd5.3 release.
1666 With __FreeBSD_version 800060 the makefs tool is part of
1667 the base system (it was a port).
1670 The afdata and ifnet locks have been changed from mutexes to
1671 rwlocks, network modules will need to be re-compiled.
1674 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1675 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1676 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1677 architecture and 40 bytes on 64-bit architecture. The userland
1678 applications "arp" and "ndp" have been updated accordingly.
1679 The output from "netstat -r" shows only routing entries and
1680 none of the L2 information.
1683 __FreeBSD_version 800057 marks the switchover from the
1684 binary ath hal to source code. Users must add the line:
1686 options AH_SUPPORT_AR5416
1688 to their kernel config files when specifying:
1692 The ath_hal module no longer exists; the code is now compiled
1693 together with the driver in the ath module. It is now
1694 possible to tailor chip support (i.e. reduce the set of chips
1695 and thereby the code size); consult ath_hal(4) for details.
1698 __FreeBSD_version 800054 adds memory barriers to
1699 <machine/atomic.h>, new interfaces to ifnet to facilitate
1700 multiple hardware transmit queues for cards that support
1701 them, and a lock-less ring-buffer implementation to
1702 enable drivers to more efficiently manage queueing of
1706 A new version of ZFS (version 13) has been merged to -HEAD.
1707 This version has zpool attribute "listsnapshots" off by
1708 default, which means "zfs list" does not show snapshots,
1709 and is the same as Solaris behavior.
1712 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1715 The uhci, ohci, ehci and slhci USB Host controller drivers have
1716 been put into separate modules. If you load the usb module
1717 separately through loader.conf you will need to load the
1718 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1719 controller add the following to loader.conf:
1725 The ABI used by the PMC toolset has changed. Please keep
1726 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1730 atapci kernel module now includes only generic PCI ATA
1731 driver. AHCI driver moved to ataahci kernel module.
1732 All vendor-specific code moved into separate kernel modules:
1733 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1734 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1735 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1736 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1739 The TTY subsystem of the kernel has been replaced by a new
1740 implementation, which provides better scalability and an
1741 improved driver model. Most common drivers have been migrated to
1742 the new TTY subsystem, while others have not. The following
1743 drivers have not yet been ported to the new TTY layer:
1746 cy, digi, rc, rp, sio
1752 ng_h4, ng_tty, ppp, sl, snp
1754 Adding these drivers to your kernel configuration file shall
1755 cause compilation to fail.
1758 ntpd has been upgraded to 4.2.4p5.
1761 OpenSSH has been upgraded to 5.1p1.
1763 For many years, FreeBSD's version of OpenSSH preferred DSA
1764 over RSA for host and user authentication keys. With this
1765 upgrade, we've switched to the vendor's default of RSA over
1766 DSA. This may cause upgraded clients to warn about unknown
1767 host keys even for previously known hosts. Users should
1768 follow the usual procedure for verifying host keys before
1769 accepting the RSA key.
1771 This can be circumvented by setting the "HostKeyAlgorithms"
1772 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1775 Please note that the sequence of keys offered for
1776 authentication has been changed as well. You may want to
1777 specify IdentityFile in a different order to revert this
1781 The sio(4) driver has been removed from the i386 and amd64
1782 kernel configuration files. This means uart(4) is now the
1783 default serial port driver on those platforms as well.
1785 To prevent collisions with the sio(4) driver, the uart(4) driver
1786 uses different names for its device nodes. This means the
1787 onboard serial port will now most likely be called "ttyu0"
1788 instead of "ttyd0". You may need to reconfigure applications to
1789 use the new device names.
1791 When using the serial port as a boot console, be sure to update
1792 /boot/device.hints and /etc/ttys before booting the new kernel.
1793 If you forget to do so, you can still manually specify the hints
1794 at the loader prompt:
1796 set hint.uart.0.at="isa"
1797 set hint.uart.0.port="0x3F8"
1798 set hint.uart.0.flags="0x10"
1799 set hint.uart.0.irq="4"
1803 The gpt(8) utility has been removed. Use gpart(8) to partition
1807 The version that Linuxulator emulates was changed from 2.4.2
1808 to 2.6.16. If you experience any problems with Linux binaries
1809 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1810 if it fixes the problem contact emulation mailing list.
1813 ISDN4BSD (I4B) was removed from the src tree. You may need to
1814 update a your kernel configuration and remove relevant entries.
1817 I have checked in code to support multiple routing tables.
1818 See the man pages setfib(1) and setfib(2).
1819 This is a hopefully backwards compatible version,
1820 but to make use of it you need to compile your kernel
1821 with options ROUTETABLES=2 (or more up to 16).
1824 The 802.11 wireless support was redone to enable multi-bss
1825 operation on devices that are capable. The underlying device
1826 is no longer used directly but instead wlanX devices are
1827 cloned with ifconfig. This requires changes to rc.conf files.
1828 For example, change:
1829 ifconfig_ath0="WPA DHCP"
1832 ifconfig_wlan0="WPA DHCP"
1833 see rc.conf(5) for more details. In addition, mergemaster of
1834 /etc/rc.d is highly recommended. Simultaneous update of userland
1835 and kernel wouldn't hurt either.
1837 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1838 modules were merged into the base wlan module. All references
1839 to these modules (e.g. in kernel config files) must be removed.
1842 psm(4) has gained write(2) support in native operation level.
1843 Arbitrary commands can be written to /dev/psm%d and status can
1844 be read back from it. Therefore, an application is responsible
1845 for status validation and error recovery. It is a no-op in
1846 other operation levels.
1849 Support for KSE threading has been removed from the kernel. To
1850 run legacy applications linked against KSE libmap.conf may
1851 be used. The following libmap.conf may be used to ensure
1852 compatibility with any prior release:
1854 libpthread.so.1 libthr.so.1
1855 libpthread.so.2 libthr.so.2
1856 libkse.so.3 libthr.so.3
1859 The layout of struct vmspace has changed. This affects libkvm
1860 and any executables that link against libkvm and use the
1861 kvm_getprocs() function. In particular, but not exclusively,
1862 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1863 The effects are minimal, but it's advisable to upgrade world
1867 The latest em driver no longer has support in it for the
1868 82575 adapter, this is now moved to the igb driver. The
1869 split was done to make new features that are incompatible
1870 with older hardware easier to do.
1873 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1874 likewise the kernel option is now GEOM_LINUX_LVM.
1877 The default NFS mount mode has changed from UDP to TCP for
1878 increased reliability. If you rely on (insecurely) NFS
1879 mounting across a firewall you may need to update your
1883 Belatedly note the addition of m_collapse for compacting
1887 The fts(3) structures have been changed to use adequate
1888 integer types for their members and so to be able to cope
1889 with huge file trees. The old fts(3) ABI is preserved
1890 through symbol versioning in libc, so third-party binaries
1891 using fts(3) should still work, although they will not take
1892 advantage of the extended types. At the same time, some
1893 third-party software might fail to build after this change
1894 due to unportable assumptions made in its source code about
1895 fts(3) structure members. Such software should be fixed
1896 by its vendor or, in the worst case, in the ports tree.
1897 FreeBSD_version 800015 marks this change for the unlikely
1898 case that a portable fix is impossible.
1901 To upgrade to -current after this date, you must be running
1902 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1903 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1906 The ADAPTIVE_GIANT kernel option has been retired because its
1907 functionality is the default now.
1910 The AT keyboard emulation of sunkbd(4) has been turned on
1911 by default. In order to make the special symbols of the Sun
1912 keyboards driven by sunkbd(4) work under X these now have
1913 to be configured the same way as Sun USB keyboards driven
1914 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1916 Option "XkbLayout" "us"
1917 Option "XkbRules" "xorg"
1918 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1921 It has been decided that it is desirable to provide ABI
1922 backwards compatibility to the FreeBSD 4/5/6 versions of the
1923 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1924 broken with the introduction of PCI domain support (see the
1925 20070930 entry). Unfortunately, this required the ABI of
1926 PCIOCGETCONF to be broken again in order to be able to
1927 provide backwards compatibility to the old version of that
1928 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1929 again. As for prominent ports this affects neither pciutils
1930 nor xorg-server this time, the hal port needs to be rebuilt
1934 The misnamed kthread_create() and friends have been renamed
1935 to kproc_create() etc. Many of the callers already
1936 used kproc_start()..
1937 I will return kthread_create() and friends in a while
1938 with implementations that actually create threads, not procs.
1939 Renaming corresponds with version 800002.
1948 Avoid using make -j when upgrading. While generally safe, there are
1949 sometimes problems using -j to upgrade. If your upgrade fails with
1950 -j, please try again without -j. From time to time in the past there
1951 have been problems using -j with buildworld and/or installworld. This
1952 is especially true when upgrading between "distant" versions (eg one
1953 that cross a major release boundary or several minor releases, or when
1954 several months have passed on the -current branch).
1956 Sometimes, obscure build problems are the result of environment
1957 poisoning. This can happen because the make utility reads its
1958 environment when searching for values for global variables. To run
1959 your build attempts in an "environmental clean room", prefix all make
1960 commands with 'env -i '. See the env(1) manual page for more details.
1962 When upgrading from one major version to another it is generally best
1963 to upgrade to the latest code in the currently installed branch first,
1964 then do an upgrade to the new branch. This is the best-tested upgrade
1965 path, and has the highest probability of being successful. Please try
1966 this approach before reporting problems with a major version upgrade.
1968 When upgrading a live system, having a root shell around before
1969 installing anything can help undo problems. Not having a root shell
1970 around can lead to problems if pam has changed too much from your
1971 starting point to allow continued authentication after the upgrade.
1975 When upgrading the boot ZFS pool to a new version, always follow
1978 1.) recompile and reinstall the ZFS boot loader and boot block
1979 (this is part of "make buildworld" and "make installworld")
1981 2.) update the ZFS boot block on your boot drive
1983 The following example updates the ZFS boot block on the first
1984 partition (freebsd-boot) of a GPT partitioned drive ad0:
1985 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1987 Non-boot pools do not need these updates.
1991 If you are updating from a prior version of FreeBSD (even one just
1992 a few days old), you should follow this procedure. It is the most
1993 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1995 make kernel-toolchain
1996 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1997 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1999 To test a kernel once
2000 ---------------------
2001 If you just want to boot a kernel once (because you are not sure
2002 if it works, or if you want to boot a known bad kernel to provide
2003 debugging information) run
2004 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2005 nextboot -k testkernel
2007 To just build a kernel when you know that it won't mess you up
2008 --------------------------------------------------------------
2009 This assumes you are already running a CURRENT system. Replace
2010 ${arch} with the architecture of your machine (e.g. "i386",
2011 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2013 cd src/sys/${arch}/conf
2014 config KERNEL_NAME_HERE
2015 cd ../compile/KERNEL_NAME_HERE
2020 If this fails, go to the "To build a kernel" section.
2022 To rebuild everything and install it on the current system.
2023 -----------------------------------------------------------
2024 # Note: sometimes if you are running current you gotta do more than
2025 # is listed here if you are upgrading from a really old current.
2027 <make sure you have good level 0 dumps>
2029 make kernel KERNCONF=YOUR_KERNEL_HERE
2031 <reboot in single user> [3]
2038 To cross-install current onto a separate partition
2039 --------------------------------------------------
2040 # In this approach we use a separate partition to hold
2041 # current's root, 'usr', and 'var' directories. A partition
2042 # holding "/", "/usr" and "/var" should be about 2GB in
2045 <make sure you have good level 0 dumps>
2048 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2049 <maybe newfs current's root partition>
2050 <mount current's root partition on directory ${CURRENT_ROOT}>
2051 make installworld DESTDIR=${CURRENT_ROOT}
2052 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2053 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2054 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2055 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2056 <reboot into current>
2057 <do a "native" rebuild/install as described in the previous section>
2058 <maybe install compatibility libraries from ports/misc/compat*>
2062 To upgrade in-place from stable to current
2063 ----------------------------------------------
2064 <make sure you have good level 0 dumps>
2066 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2068 <reboot in single user> [3]
2075 Make sure that you've read the UPDATING file to understand the
2076 tweaks to various things you need. At this point in the life
2077 cycle of current, things change often and you are on your own
2078 to cope. The defaults can also change, so please read ALL of
2079 the UPDATING entries.
2081 Also, if you are tracking -current, you must be subscribed to
2082 freebsd-current@freebsd.org. Make sure that before you update
2083 your sources that you have read and understood all the recent
2084 messages there. If in doubt, please track -stable which has
2085 much fewer pitfalls.
2087 [1] If you have third party modules, such as vmware, you
2088 should disable them at this point so they don't crash your
2091 [3] From the bootblocks, boot -s, and then do
2096 adjkerntz -i # if CMOS is wall time
2097 Also, when doing a major release upgrade, it is required that
2098 you boot into single user mode to do the installworld.
2100 [4] Note: This step is non-optional. Failure to do this step
2101 can result in a significant reduction in the functionality of the
2102 system. Attempting to do it by hand is not recommended and those
2103 that pursue this avenue should read this file carefully, as well
2104 as the archives of freebsd-current and freebsd-hackers mailing lists
2105 for potential gotchas. The -U option is also useful to consider.
2106 See mergemaster(8) for more information.
2108 [5] Usually this step is a noop. However, from time to time
2109 you may need to do this if you get unknown user in the following
2110 step. It never hurts to do it all the time. You may need to
2111 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2112 install) after the buildworld before this step if you last updated
2113 from current before 20130425 or from -stable before 20130430.
2115 [6] This only deletes old files and directories. Old libraries
2116 can be deleted by "make delete-old-libs", but you have to make
2117 sure that no program is using those libraries anymore.
2119 [8] In order to have a kernel that can run the 4.x binaries needed to
2120 do an installworld, you must include the COMPAT_FREEBSD4 option in
2121 your kernel. Failure to do so may leave you with a system that is
2122 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2123 required to run the 5.x binaries on more recent kernels. And so on
2124 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2126 Make sure that you merge any new devices from GENERIC since the
2127 last time you updated your kernel config file.
2129 [9] When checking out sources, you must include the -P flag to have
2130 cvs prune empty directories.
2132 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2133 "?=" instead of the "=" assignment operator, so that buildworld can
2134 override the CPUTYPE if it needs to.
2136 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2137 not on the command line, or in /etc/make.conf. buildworld will
2138 warn if it is improperly defined.
2141 This file contains a list, in reverse chronological order, of major
2142 breakages in tracking -current. It is not guaranteed to be a complete
2143 list of such breakages, and only contains entries since October 10, 2007.
2144 If you need to see UPDATING entries from before that date, you will need
2145 to fetch an UPDATING file from an older FreeBSD release.
2147 Copyright information:
2149 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2151 Redistribution, publication, translation and use, with or without
2152 modification, in full or in part, in any form or format of this
2153 document are permitted without further permission from the author.
2155 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2156 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2157 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2158 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2159 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2160 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2161 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2162 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2163 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2164 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2165 POSSIBILITY OF SUCH DAMAGE.
2167 Contact Warner Losh if you have any questions about your use of