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 An additional fix for the issue described in the 20150614 sendmail
21 entry below has been been committed in revision 284786.
24 The fix for the issue described in the 20150614 sendmail entry
25 below has been been committed in revision 284485. The work
26 around described in that entry is no longer needed unless the
27 default setting is overridden by a confDH_PARAMETERS configuration
28 setting of '5' or pointing to a 512 bit DH parameter file.
31 The import of openssl to address the FreeBSD-SA-15:10.openssl
32 security advisory includes a change which rejects handshakes
33 with DH parameters below 768 bits. sendmail releases prior
34 to 8.15.2 (not yet released), defaulted to a 512 bit
35 DH parameter setting for client connections. To work around
36 this interoperability, sendmail can be configured to use a
37 2048 bit DH parameter by:
39 1. Edit /etc/mail/`hostname`.mc
40 2. If a setting for confDH_PARAMETERS does not exist or
41 exists and is set to a string beginning with '5',
43 3. If a setting for confDH_PARAMETERS exists and is set to
44 a file path, create a new file with:
45 openssl dhparam -out /path/to/file 2048
46 4. Rebuild the .cf file:
47 cd /etc/mail/; make; make install
49 cd /etc/mail/; make restart
51 A sendmail patch is coming, at which time this file will be
55 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
56 defined in symlink(7); previously symlinks were silently ignored.
59 The const qualifier has been removed from iconv(3) to comply with
60 POSIX. The ports tree is aware of this from r384038 onwards.
63 At svn r275807, The default linux compat kernel ABI has been adjusted
64 to 2.6.18 in support of the linux-c6 compat ports infrastructure
65 update. If you wish to continue using the linux-f10 compat ports,
66 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
67 encouraged to update their linux-compat packages to linux-c6 during
68 their next update cycle.
70 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
73 pjdfstest has been integrated into kyua as an opt-in test suite.
74 Please see share/doc/pjdfstest/README for a more details on how to
81 The ofwfb driver, used to provide a graphics console on PowerPC when
82 using vt(4), no longer allows mmap() of all of physical memory. This
83 will prevent Xorg on PowerPC with some ATI graphics cards from
84 initializing properly unless x11-servers/xorg-server is updated to
88 The libatf-c and libatf-c++ major versions were downgraded to 0 and
89 1 respectively to match the upstream numbers. They were out of
90 sync because, when they were originally added to FreeBSD, the
91 upstream versions were not respected. These libraries are private
92 and not yet built by default, so renumbering them should be a
93 non-issue. However, unclean source trees will yield broken test
94 programs once the operator executes "make delete-old-libs" after a
97 Additionally, the atf-sh binary was made private by moving it into
98 /usr/libexec/. Already-built shell test programs will keep the
99 path to the old binary so they will break after "make delete-old"
102 If you are using WITH_TESTS=yes (not the default), wipe the object
103 tree and rebuild from scratch to prevent spurious test failures.
104 This is only needed once: the misnumbered libraries and misplaced
105 binaries have been added to OptionalObsoleteFiles.inc so they will
106 be removed during a clean upgrade.
109 The ixgbe tunables now match their sysctl counterparts, for example:
110 hw.ixgbe.enable_aim => hw.ix.enable_aim
111 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
114 The NFSv4.1 server committed by r269398 changes the internal
115 function call interfaces used between the NFS and krpc modules.
116 As such, __FreeBSD_version was bumped.
119 The default unbound configuration has been modified to address
120 issues with reverse lookups on networks that use private
121 address ranges. If you use the local_unbound service, run
122 "service local_unbound setup" as root to regenerate your
123 configuration, then "service local_unbound reload" to load the
127 It is no longer necessary to include the dwarf version in your DEBUG
128 options in your kernel config file. The bug that required it to be
129 placed in the config file has bene fixed. DEBUG should now just
130 contain -g. The build system will automatically update things
131 to do the right thing.
134 Several ABI breaking changes were merged to CTL and new iSCSI code.
135 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
136 iscsictl need to be rebuilt to work with a new kernel.
139 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
140 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
141 which differs from the behaviour controlled by this knob.)
144 On i386 and amd64 systems, the onifconsole flag is now set by default
145 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
146 as a login TTY if it is set in the bootloader as an active kernel
147 console. No changes in behavior should result otherwise. To revert to
148 the previous behavior, set ttyu0 to "off" in /etc/ttys.
151 Clang and llvm have been upgraded to 3.4.1 release.
154 Clang and llvm have been upgraded to 3.4 release.
157 If a Makefile in a tests/ directory was auto-generating a Kyuafile
158 instead of providing an explicit one, this would prevent such
159 Makefile from providing its own Kyuafile in the future during
160 NO_CLEAN builds. This has been fixed in the Makefiles but manual
161 intervention is needed to clean an objdir if you use NO_CLEAN:
162 # find /usr/obj -name Kyuafile | xargs rm -f
165 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
166 capability mode support. Please note that enabling the feature in
167 kernel is still highly recommended.
170 OpenSSH is now built with sandbox support, and will use sandbox as
171 the default privilege separation method. This requires Capsicum
172 capability mode support in kernel.
175 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
176 been deprecated and will not be part of FreeBSD 11.0 and later
177 releases. If you use this driver, please consider switching to
178 the nfe(4) driver instead.
184 The behavior of gss_pseudo_random() for the krb5 mechanism
185 has changed, for applications requesting a longer random string
186 than produced by the underlying enctype's pseudo-random() function.
187 In particular, the random string produced from a session key of
188 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
189 be different at the 17th octet and later, after this change.
190 The counter used in the PRF+ construction is now encoded as a
191 big-endian integer in accordance with RFC 4402.
192 __FreeBSD_version is bumped to 1000701.
195 The WITHOUT_ATF build knob has been removed and its functionality
196 has been subsumed into the more generic WITHOUT_TESTS. If you were
197 using the former to disable the build of the ATF libraries, you
198 should change your settings to use the latter.
201 The default version of mtree is nmtree which is obtained from
202 NetBSD. The output is generally the same, but may vary
203 slightly. If you found you need identical output adding
204 "-F freebsd9" to the command line should do the trick. For the
205 time being, the old mtree is available as fmtree.
208 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
209 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
210 1.1.4_8 and verify bsdyml not linked in, before running "make
212 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
214 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
217 The rc.d/jail script has been updated to support jail(8)
218 configuration file. The "jail_<jname>_*" rc.conf(5) variables
219 for per-jail configuration are automatically converted to
220 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
221 This is transparently backward compatible. See below about some
222 incompatibilities and rc.conf(5) manual page for more details.
224 These variables are now deprecated in favor of jail(8) configuration
225 file. One can use "rc.d/jail config <jname>" command to generate
226 a jail(8) configuration file in /var/run/jail.<jname>.conf without
227 running the jail(8) utility. The default pathname of the
228 configuration file is /etc/jail.conf and can be specified by
229 using $jail_conf or $jail_<jname>_conf variables.
231 Please note that jail_devfs_ruleset accepts an integer at
232 this moment. Please consider to rewrite the ruleset name
236 BIND has been removed from the base system. If all you need
237 is a local resolver, simply enable and start the local_unbound
238 service instead. Otherwise, several versions of BIND are
239 available in the ports tree. The dns/bind99 port is one example.
241 With this change, nslookup(1) and dig(1) are no longer in the base
242 system. Users should instead use host(1) and drill(1) which are
243 in the base system. Alternatively, nslookup and dig can
244 be obtained by installing the dns/bind-tools port.
247 With the addition of unbound(8), a new unbound user is now
248 required during installworld. "mergemaster -p" can be used to
249 add the user prior to installworld, as documented in the handbook.
252 OpenSSH is now built with DNSSEC support, and will by default
253 silently trust signed SSHFP records. This can be controlled with
254 the VerifyHostKeyDNS client configuration setting. DNSSEC support
255 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
258 The GNU Compiler Collection and C++ standard library (libstdc++)
259 are no longer built by default on platforms where clang is the system
260 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
264 The PROCDESC kernel option is now part of the GENERIC kernel
265 configuration and is required for the rwhod(8) to work.
266 If you are using custom kernel configuration, you should include
270 The API and ABI related to the Capsicum framework was modified
271 in backward incompatible way. The userland libraries and programs
272 have to be recompiled to work with the new kernel. This includes the
273 following libraries and programs, but the whole buildworld is
274 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
275 kdump, procstat, rwho, rwhod, uniq.
278 AES-NI intrinsic support has been added to gcc. The AES-NI module
279 has been updated to use this support. A new gcc is required to build
280 the aesni module on both i386 and amd64.
283 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
284 Thus "device padlock_rng" and "device rdrand_rng" should be
285 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
288 WITH_ICONV has been split into two feature sets. WITH_ICONV now
289 enables just the iconv* functionality and is now on by default.
290 WITH_LIBICONV_COMPAT enables the libiconv api and link time
291 compatability. Set WITHOUT_ICONV to build the old way.
292 If you have been using WITH_ICONV before, you will very likely
293 need to turn on WITH_LIBICONV_COMPAT.
296 INVARIANTS option now enables DEBUG for code with OpenSolaris and
297 Illumos origin, including ZFS. If you have INVARIANTS in your
298 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
300 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
301 locks if WITNESS option was set. Because that generated a lot of
302 witness(9) reports and all of them were believed to be false
303 positives, this is no longer done. New option OPENSOLARIS_WITNESS
304 can be used to achieve the previous behavior.
307 Timer values in IPv6 data structures now use time_uptime instead
308 of time_second. Although this is not a user-visible functional
309 change, userland utilities which directly use them---ndp(8),
310 rtadvd(8), and rtsold(8) in the base system---need to be updated
314 find -delete can now delete the pathnames given as arguments,
315 instead of only files found below them or if the pathname did
316 not contain any slashes. Formerly, the following error message
319 find: -delete: <path>: relative path potentially not safe
321 Deleting the pathnames given as arguments can be prevented
322 without error messages using -mindepth 1 or by changing
323 directory and passing "." as argument to find. This works in the
324 old as well as the new version of find.
327 Behavior of devfs rules path matching has been changed.
328 Pattern is now always matched against fully qualified devfs
329 path and slash characters must be explicitly matched by
330 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
331 subdirectories must be reviewed.
334 The default ARM ABI has changed to the ARM EABI. The old ABI is
335 incompatible with the ARM EABI and all programs and modules will
336 need to be rebuilt to work with a new kernel.
338 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
340 NOTE: Support for the old ABI will be removed in the future and
341 users are advised to upgrade.
344 pkg_install has been disconnected from the build if you really need it
345 you should add WITH_PKGTOOLS in your src.conf(5).
348 Most of network statistics structures were changed to be able
349 keep 64-bits counters. Thus all tools, that work with networking
350 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
353 Fix targets that run multiple make's to use && rather than ;
354 so that subsequent steps depend on success of previous.
356 NOTE: if building 'universe' with -j* on stable/8 or stable/9
357 it would be better to start the build using bmake, to avoid
358 overloading the machine.
361 Fix a bug that allowed a tracing process (e.g. gdb) to write
362 to a memory-mapped file in the traced process's address space
363 even if neither the traced process nor the tracing process had
364 write access to that file.
367 CVS has been removed from the base system. An exact copy
368 of the code is available from the devel/cvs port.
371 Some people report the following error after the switch to bmake:
373 make: illegal option -- J
374 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
376 *** [buildworld] Error code 2
378 this likely due to an old instance of make in
379 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
380 which src/Makefile will use that blindly, if it exists, so if
381 you see the above error:
383 rm -rf `make -V MAKEPATH`
388 Use bmake by default.
389 Whereas before one could choose to build with bmake via
390 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
391 make. The goal is to remove these knobs for 10-RELEASE.
393 It is worth noting that bmake (like gmake) treats the command
394 line as the unit of failure, rather than statements within the
395 command line. Thus '(cd some/where && dosomething)' is safer
396 than 'cd some/where; dosomething'. The '()' allows consistent
397 behavior in parallel build.
400 Fix a bug that allows NFS clients to issue READDIR on files.
403 The WITHOUT_IDEA option has been removed because
404 the IDEA patent expired.
407 The sysctl which controls TRIM support under ZFS has been renamed
408 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
412 The mergemaster command now uses the default MAKEOBJDIRPREFIX
413 rather than creating it's own in the temporary directory in
414 order allow access to bootstrapped versions of tools such as
415 install and mtree. When upgrading from version of FreeBSD where
416 the install command does not support -l, you will need to
417 install a new mergemaster command if mergemaster -p is required.
418 This can be accomplished with the command (cd src/usr.sbin/mergemaster
422 Legacy ATA stack, disabled and replaced by new CAM-based one since
423 FreeBSD 9.0, completely removed from the sources. Kernel modules
424 atadisk and atapi*, user-level tools atacontrol and burncd are
425 removed. Kernel option `options ATA_CAM` is now permanently enabled
429 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
430 and socketpair(2). Software, in particular Kerberos, may
431 automatically detect and use these during building. The resulting
432 binaries will not work on older kernels.
435 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
436 information, see the respective 20130304 entry).
439 Recent commits to callout(9) changed the size of struct callout,
440 so the KBI is probably heavily disturbed. Also, some functions
441 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
442 by macros. Every kernel module using it won't load, so rebuild
445 The ctl device has been re-enabled in GENERIC for i386 and amd64,
446 but does not initialize by default (because of the new CTL_DISABLE
447 option) to save memory. To re-enable it, remove the CTL_DISABLE
448 option from the kernel config file or set kern.cam.ctl.disable=0
449 in /boot/loader.conf.
452 The ctl device has been disabled in GENERIC for i386 and amd64.
453 This was done due to the extra memory being allocated at system
454 initialisation time by the ctl driver which was only used if
455 a CAM target device was created. This makes a FreeBSD system
456 unusable on 128MB or less of RAM.
459 A new compression method (lz4) has been merged to -HEAD. Please
460 refer to zpool-features(7) for more information.
462 Please refer to the "ZFS notes" section of this file for information
463 on upgrading boot ZFS pools.
466 A BSD-licensed patch(1) variant has been added and is installed
467 as bsdpatch, being the GNU version the default patch.
468 To inverse the logic and use the BSD-licensed one as default,
469 while having the GNU version installed as gnupatch, rebuild
470 and install world with the WITH_BSD_PATCH knob set.
473 Due to the use of the new -l option to install(1) during build
474 and install, you must take care not to directly set the INSTALL
475 make variable in your /etc/make.conf, /etc/src.conf, or on the
476 command line. If you wish to use the -C flag for all installs
477 you may be able to add INSTALL+=-C to /etc/make.conf or
481 The install(1) option -M has changed meaning and now takes an
482 argument that is a file or path to append logs to. In the
483 unlikely event that -M was the last option on the command line
484 and the command line contained at least two files and a target
485 directory the first file will have logs appended to it. The -M
486 option served little practical purpose in the last decade so its
487 use is expected to be extremely rare.
490 After switching to Clang as the default compiler some users of ZFS
491 on i386 systems started to experience stack overflow kernel panics.
492 Please consider using 'options KSTACK_PAGES=4' in such configurations.
495 GEOM_LABEL now mangles label names read from file system metadata.
496 Mangling affect labels containing spaces, non-printable characters,
497 '%' or '"'. Device names in /etc/fstab and other places may need to
501 By default, only the 10 most recent kernel dumps will be saved. To
502 restore the previous behaviour (no limit on the number of kernel dumps
503 stored in the dump directory) add the following line to /etc/rc.conf:
508 With the addition of auditdistd(8), a new auditdistd user is now
509 required during installworld. "mergemaster -p" can be used to
510 add the user prior to installworld, as documented in the handbook.
513 The sin6_scope_id member variable in struct sockaddr_in6 is now
514 filled by the kernel before passing the structure to the userland via
515 sysctl or routing socket. This means the KAME-specific embedded scope
516 id in sin6_addr.s6_addr[2] is always cleared in userland application.
517 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
518 __FreeBSD_version is bumped to 1000025.
521 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
522 This means that the world and kernel will be compiled with clang
523 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
524 and /usr/bin/cpp. To disable this behavior and revert to building
525 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
526 of current may need to bootstrap WITHOUT_CLANG first if the clang
527 build fails (its compatibility window doesn't extend to the 9 stable
531 The IPFIREWALL_FORWARD kernel option has been removed. Its
532 functionality now turned on by default.
535 The ZERO_COPY_SOCKET kernel option has been removed and
536 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
537 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
538 mechanism which is not safe and may result in kernel crashes.
539 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
540 driver supports disposeable external page sized mbuf storage.
541 Proper replacements for both zero-copy mechanisms are under
542 consideration and will eventually lead to complete removal
543 of the two kernel options.
546 The IPv4 network stack has been converted to network byte
547 order. The following modules need to be recompiled together
548 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
549 pf(4), ipfw(4), ng_ipfw(4), stf(4).
552 Support for non-MPSAFE filesystems was removed from VFS. The
553 VFS_VERSION was bumped, all filesystem modules shall be
557 All the non-MPSAFE filesystems have been disconnected from
558 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
559 portalfs, smbfs, xfs.
562 The interface cloning API and ABI has changed. The following
563 modules need to be recompiled together with kernel:
564 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
565 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
566 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
569 The sdhci driver was split in two parts: sdhci (generic SD Host
570 Controller logic) and sdhci_pci (actual hardware driver).
571 No kernel config modifications are required, but if you
572 load sdhc as a module you must switch to sdhci_pci instead.
575 Import the FUSE kernel and userland support into base system.
578 The GNU sort(1) program has been removed since the BSD-licensed
579 sort(1) has been the default for quite some time and no serious
580 problems have been reported. The corresponding WITH_GNU_SORT
584 The pfil(9) API/ABI for AF_INET family has been changed. Packet
585 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
589 The net80211(4) ABI has been changed to allow for improved driver
590 PS-POLL and power-save support. All wireless drivers need to be
591 recompiled to work with the new kernel.
594 The random(4) support for the VIA hardware random number
595 generator (`PADLOCK') is no longer enabled unconditionally.
596 Add the padlock_rng device in the custom kernel config if
597 needed. The GENERIC kernels on i386 and amd64 do include the
598 device, so the change only affects the custom kernel
602 The pf(4) packet filter ABI has been changed. pfctl(8) and
603 snmp_pf module need to be recompiled to work with new kernel.
606 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
607 to -HEAD. Pools that have empty_bpobj in active state can not be
608 imported read-write with ZFS implementations that do not support
609 this feature. For more information read the zpool-features(5)
613 The sparc64 ZFS loader has been changed to no longer try to auto-
614 detect ZFS providers based on diskN aliases but now requires these
615 to be explicitly listed in the OFW boot-device environment variable.
618 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
619 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
620 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
623 The following sysctls and tunables have been renamed for consistency
624 with other variables:
625 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
626 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
629 The sort utility has been replaced with BSD sort. For now, GNU sort
630 is also available as "gnusort" or the default can be set back to
631 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
632 installed as "bsdsort".
635 A new version of ZFS (pool version 5000) has been merged to -HEAD.
636 Starting with this version the old system of ZFS pool versioning
637 is superseded by "feature flags". This concept enables forward
638 compatibility against certain future changes in functionality of ZFS
639 pools. The first read-only compatible "feature flag" for ZFS pools
640 is named "com.delphix:async_destroy". For more information
641 read the new zpool-features(5) manual page.
642 Please refer to the "ZFS notes" section of this file for information
643 on upgrading boot ZFS pools.
646 The malloc(3) implementation embedded in libc now uses sources imported
647 as contrib/jemalloc. The most disruptive API change is to
648 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
649 delete it prior to installworld, and optionally re-create it using the
650 new format after rebooting. See malloc.conf(5) for details
651 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
655 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
656 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
657 now spelled mips. This is to aid compatibility with third-party
658 software that expects this naming scheme in uname(3). Little-endian
659 settings are unchanged. If you are updating a big-endian mips64 machine
660 from before this change, you may need to set MACHINE_ARCH=mips64 in
661 your environment before the new build system will recognize your machine.
664 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
668 Now unix domain sockets behave "as expected" on nullfs(5). Previously
669 nullfs(5) did not pass through all behaviours to the underlying layer,
670 as a result if we bound to a socket on the lower layer we could connect
671 only to the lower path; if we bound to the upper layer we could connect
672 only to the upper path. The new behavior is one can connect to both the
673 lower and the upper paths regardless what layer path one binds to.
676 The getifaddrs upgrade path broken with 20111215 has been restored.
677 If you have upgraded in between 20111215 and 20120209 you need to
678 recompile libc again with your kernel. You still need to recompile
679 world to be able to configure CARP but this restriction already
683 The set_rcvar() function has been removed from /etc/rc.subr. All
684 base and ports rc.d scripts have been updated, so if you have a
685 port installed with a script in /usr/local/etc/rc.d you can either
686 hand-edit the rcvar= line, or reinstall the port.
688 An easy way to handle the mass-update of /etc/rc.d:
689 rm /etc/rc.d/* && mergemaster -i
692 panic(9) now stops other CPUs in the SMP systems, disables interrupts
693 on the current CPU and prevents other threads from running.
694 This behavior can be reverted using the kern.stop_scheduler_on_panic
696 The new behavior can be incompatible with kern.sync_on_panic.
699 The carp(4) facility has been changed significantly. Configuration
700 of the CARP protocol via ifconfig(8) has changed, as well as format
701 of CARP events submitted to devd(8) has changed. See manual pages
702 for more information. The arpbalance feature of carp(4) is currently
703 not supported anymore.
705 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
706 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
707 need to be recompiled.
710 The acpi_wmi(4) status device /dev/wmistat has been renamed to
714 The option VFS_ALLOW_NONMPSAFE option has been added in order to
715 explicitely support non-MPSAFE filesystems.
716 It is on by default for all supported platform at this present
720 The broken amd(4) driver has been replaced with esp(4) in the amd64,
721 i386 and pc98 GENERIC kernel configuration files.
724 sysinstall has been removed
727 The stable/9 branch created in subversion. This corresponds to the
728 RELENG_9 branch in CVS.
731 This commit modifies vfs_register() so that it uses a hash
732 calculation to set vfc_typenum, which is enabled by default.
733 The first time a system is booted after this change, the
734 vfc_typenum values will change for all file systems. The
735 main effect of this is a change to the NFS server file handles
736 for file systems that use vfc_typenum in their fsid, such as ZFS.
737 It will, however, prevent vfc_typenum from changing when file
738 systems are loaded in a different order for subsequent reboots.
739 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
740 until you are ready to remount all NFS clients after a reboot.
743 Bump the shared library version numbers for libraries that
744 do not use symbol versioning, have changed the ABI compared
745 to stable/8 and which shared library version was not bumped.
746 Done as part of 9.0-RELEASE cycle.
749 During the merge of Capsicum features, the fget(9) KPI was modified.
750 This may require the rebuilding of out-of-tree device drivers --
751 issues have been reported specifically with the nVidia device driver.
752 __FreeBSD_version is bumped to 900041.
754 Also, there is a period between 20110811 and 20110814 where the
755 special devices /dev/{stdin,stdout,stderr} did not work correctly.
756 Building world from a kernel during that window may not work.
759 The packet filter (pf) code has been updated to OpenBSD 4.5.
760 You need to update userland tools to be in sync with kernel.
761 This update breaks backward compatibility with earlier pfsync(4)
762 versions. Care must be taken when updating redundant firewall setups.
765 The following sysctls and tunables are retired on x86 platforms:
767 machdep.hlt_logical_cpus
768 The following sysctl is retired:
769 machdep.hyperthreading_allowed
770 The sysctls were supposed to provide a way to dynamically offline and
771 online selected CPUs on x86 platforms, but the implementation has not
772 been reliable especially with SCHED_ULE scheduler.
773 machdep.hyperthreading_allowed tunable is still available to ignore
774 hyperthreading CPUs at OS level.
775 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
776 where X is an APIC ID of a CPU. Be advised, though, that disabling
777 CPUs in non-uniform fashion will result in non-uniform topology and
778 may lead to sub-optimal system performance with SCHED_ULE, which is
782 cpumask_t type is retired and cpuset_t is used in order to describe
786 Changes to ifconfig(8) for dynamic address family detection mandate
787 that you are running a kernel of 20110525 or later. Make sure to
788 follow the update procedure to boot a new kernel before installing
792 Support for sun4v architecture is officially dropped
795 Several KPI breaking changes have been committed to the mii(4) layer,
796 the PHY drivers and consequently some Ethernet drivers using mii(4).
797 This means that miibus.ko and the modules of the affected Ethernet
798 drivers need to be recompiled.
800 Note to kernel developers: Given that the OUI bit reversion problem
801 was fixed as part of these changes all mii(4) commits related to OUIs,
802 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
803 handling, no longer can be merged verbatim to stable/8 and previous
807 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
808 into their kernel configurations along with 'device pci'.
811 The default NFS client is now the new NFS client, so fstype "newnfs"
812 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
813 Although mounts via fstype "nfs" will usually work without userland
814 changes, it is recommended that the mount(8) and mount_nfs(8)
815 commands be rebuilt from sources and that a link to mount_nfs called
816 mount_oldnfs be created. The new client is compiled into the
817 kernel with "options NFSCL" and this is needed for diskless root
818 file systems. The GENERIC kernel configs have been changed to use
819 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
820 To use the regular/old client, you can "mount -t oldnfs ...". For
821 a diskless root file system, you must also include a line like:
823 vfs.root.mountfrom="oldnfs:"
825 in the boot/loader.conf on the root fs on the NFS server to make
826 a diskless root fs use the old client.
829 The GENERIC kernels for all architectures now default to the new
830 CAM-based ATA stack. It means that all legacy ATA drivers were
831 removed and replaced by respective CAM drivers. If you are using
832 ATA device names in /etc/fstab or other places, make sure to update
833 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
834 where 'Y's are the sequential numbers starting from zero for each type
835 in order of detection, unless configured otherwise with tunables,
836 see cam(4)). There will be symbolic links created in /dev/ to map
837 old adX devices to the respective adaY. They should provide basic
838 compatibility for file systems mounting in most cases, but they do
839 not support old user-level APIs and do not have respective providers
840 in GEOM. Consider using updated management tools with new device names.
842 It is possible to load devices ahci, ata, siis and mvs as modules,
843 but option ATA_CAM should remain in kernel configuration to make ata
844 module work as CAM driver supporting legacy ATA controllers. Device ata
845 still can be used in modular fashion (atacore + ...). Modules atadisk
846 and atapi* are not used and won't affect operation in ATA_CAM mode.
847 Note that to use CAM-based ATA kernel should include CAM devices
848 scbus, pass, da (or explicitly ada), cd and optionally others. All of
849 them are parts of the cam module.
851 ataraid(4) functionality is now supported by the RAID GEOM class.
852 To use it you can load geom_raid kernel module and use graid(8) tool
853 for management. Instead of /dev/arX device names, use /dev/raid/rX.
855 No kernel config options or code have been removed, so if a problem
856 arises, please report it and optionally revert to the old ATA stack.
857 In order to do it you can remove from the kernel config:
862 , and instead add back:
863 device atadisk # ATA disk drives
864 device ataraid # ATA RAID drives
865 device atapicd # ATAPI CDROM drives
866 device atapifd # ATAPI floppy drives
867 device atapist # ATAPI tape drives
870 The default NFS server has been changed to the new server, which
871 was referred to as the experimental server. If you need to switch
872 back to the old NFS server, you must now put the "-o" option on
873 both the mountd and nfsd commands. This can be done using the
874 mountd_flags and nfs_server_flags rc.conf variables until an
875 update to the rc scripts is committed, which is coming soon.
878 The GNU Objective-C runtime library (libobjc), and other Objective-C
879 related components have been removed from the base system. If you
880 require an Objective-C library, please use one of the available ports.
883 ath(4) has been split into bus- and device- modules. if_ath contains
884 the HAL, the TX rate control and the network device code. if_ath_pci
885 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
886 contains the AHB glue. Users need to load both if_ath_pci and if_ath
887 in order to use ath on everything else.
889 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
890 need to load if_ath and if_ath_pci for ath(4) operation.
893 As part of the replacement of sysinstall, the process of building
894 release media has changed significantly. For details, please re-read
895 release(7), which has been updated to reflect the new build process.
898 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
899 is the last available version under GPLv2. It brings a number of new
900 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
901 4.1 and SSE 4.2), better support for powerpc64, a number of new
902 directives, and lots of other small improvements. See the ChangeLog
903 file in contrib/binutils for the full details.
906 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
907 compliant, and will now use half of hash for authentication.
908 This will break interoperability with all stacks (including all
909 actual FreeBSD versions) who implement
910 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
912 The only workaround with such peers is to use another HMAC
913 algorithm for IPsec ("phase 2") authentication.
916 Remove the uio_yield prototype and symbol. This function has
917 been misnamed since it was introduced and should not be
918 globally exposed with this name. The equivalent functionality
919 is now available using kern_yield(curthread->td_user_pri).
920 The function remains undocumented.
923 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
924 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
925 for scalar sysctls is defined but disabled. Code that needs
926 UQUAD to pass the type checking that must compile on older
927 systems where the define is not present can check against
928 __FreeBSD_version >= 900030.
930 The system dialog(1) has been replaced with a new version previously
931 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
932 with the previous version, but the libdialog associated with it has
933 a largely incompatible API. As such, the original version of libdialog
934 will be kept temporarily as libodialog, until its base system consumers
935 are replaced or updated. Bump __FreeBSD_version to 900030.
938 If you are trying to run make universe on a -stable system, and you get
939 the following warning:
940 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
941 unknown. config(8) likely too old."
942 or something similar to it, then you must upgrade your -stable system
943 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
944 stable/8) or build the config from the latest stable/8 branch and
945 install it on your system.
947 Prior to this date, building a current universe on 8-stable system from
948 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
949 error in the first kernel build phase. A new config on those old
950 systems will fix that problem for older versions of -current.
953 The TCP stack has been modified to allow Khelp modules to interact with
954 it via helper hook points and store per-connection data in the TCP
955 control block. Bump __FreeBSD_version to 900029. User space tools that
956 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
960 Generic IEEE 802.3 annex 31B full duplex flow control support has been
961 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
962 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
963 to take advantage of it instead of using custom implementations. This
964 means that these drivers now no longer unconditionally advertise
965 support for flow control but only do so if flow control is a selected
966 media option. This was implemented in the generic support that way in
967 order to allow flow control to be switched on and off via ifconfig(8)
968 with the PHY specific default to typically off in order to protect
969 from unwanted effects. Consequently, if you used flow control with
970 one of the above mentioned drivers you now need to explicitly enable
972 ifconfig bge0 media auto mediaopt flowcontrol
974 Along with the above mentioned changes generic support for setting
975 1000baseT master mode also has been added and brgphy(4), ciphy(4),
976 e1000phy(4) as well as ip1000phy(4) have been converted to take
977 advantage of it. This means that these drivers now no longer take the
978 link0 parameter for selecting master mode but the master media option
979 has to be used instead, for example like in the following:
980 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
982 Selection of master mode now is also available with all other PHY
983 drivers supporting 1000baseT.
986 The TCP stack has received a significant update to add support for
987 modularised congestion control and generally improve the clarity of
988 congestion control decisions. Bump __FreeBSD_version to 900025. User
989 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
990 sockstat) need to be recompiled.
993 The man(1) utility has been replaced by a new version that no longer
994 uses /etc/manpath.config. Please consult man.conf(5) for how to
995 migrate local entries to the new format.
998 The copyright strings printed by login(1) and sshd(8) at the time of a
999 new connection have been removed to follow other operating systems and
1003 A workaround for a fixed ld bug has been removed in kernel code,
1004 so make sure that your system ld is built from sources after
1005 revision 210245 from 2010-07-19 (r211583 if building head kernel
1006 on stable/8, r211584 for stable/7; both from 2010-08-21).
1007 A symptom of incorrect ld version is different addresses for
1008 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1011 The $ipv6_prefer variable in rc.conf(5) has been split into
1012 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1014 The $ip6addrctl_policy is a variable to choose a pre-defined
1015 address selection policy set by ip6addrctl(8). A value
1016 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1019 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1020 flag (see an entry of 20090926) is set on an interface with no
1021 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1022 security reason. If you want IPv6 link-local address on all
1023 interfaces by default, set this to "YES".
1025 The old ipv6_prefer="YES" is equivalent to
1026 ipv6_activate_all_interfaces="YES" and
1027 ip6addrctl_policy="ipv6_prefer".
1030 DTrace has grown support for userland tracing. Due to this, DTrace is
1031 now i386 and amd64 only.
1032 dtruss(1) is now installed by default on those systems and a new
1033 kernel module is needed for userland tracing: fasttrap.
1034 No changes to your kernel config file are necessary to enable
1035 userland tracing, but you might consider adding 'STRIP=' and
1036 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1037 to have informative userland stack traces in DTrace (ustack).
1040 The acpi_aiboost(4) driver has been removed in favor of the new
1041 aibs(4) driver. You should update your kernel configuration file.
1044 BSD grep has been imported to the base system and it is built by
1045 default. It is completely BSD licensed, highly GNU-compatible, uses
1046 less memory than its GNU counterpart and has a small codebase.
1047 However, it is slower than its GNU counterpart, which is mostly
1048 noticeable for larger searches, for smaller ones it is measurable
1049 but not significant. The reason is complex, the most important factor
1050 is that we lack a modern and efficient regex library and GNU
1051 overcomes this by optimizing the searches internally. Future work
1052 on improving the regex performance is planned, for the meantime,
1053 users that need better performance, can build GNU grep instead by
1054 setting the WITH_GNU_GREP knob.
1057 Due to the import of powerpc64 support, all existing powerpc kernel
1058 configuration files must be updated with a machine directive like this:
1059 machine powerpc powerpc
1061 In addition, an updated config(8) is required to build powerpc kernels
1065 A new version of ZFS (version 15) has been merged to -HEAD.
1066 This version uses a python library for the following subcommands:
1067 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1068 For full functionality of these commands the following port must
1069 be installed: sysutils/py-zfs
1072 'vm_page's are now hashed by physical address to an array of mutexes.
1073 Currently this is only used to serialize access to hold_count. Over
1074 time the page queue mutex will be peeled away. This changes the size
1075 of pmap on every architecture. And requires all callers of vm_page_hold
1076 and vm_page_unhold to be updated.
1079 WITH_CTF can now be specified in src.conf (not recommended, there
1080 are some problems with static executables), make.conf (would also
1081 affect ports which do not use GNU make and do not override the
1082 compile targets) or in the kernel config (via "makeoptions
1084 When WITH_CTF was specified there before this was silently ignored,
1085 so make sure that WITH_CTF is not used in places which could lead
1086 to unwanted behavior.
1089 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1090 to allow 32-bit compatibility on non-x86 platforms. All kernel
1091 configurations on amd64 and ia64 platforms using these options must
1092 be modified accordingly.
1095 The utmp user accounting database has been replaced with utmpx,
1096 the user accounting interface standardized by POSIX.
1097 Unfortunately the semantics of utmp and utmpx don't match,
1098 making it practically impossible to support both interfaces.
1099 The user accounting database is used by tools like finger(1),
1100 last(1), talk(1), w(1) and ac(8).
1102 All applications in the base system use utmpx. This means only
1103 local binaries (e.g. from the ports tree) may still use these
1104 utmp database files. These applications must be rebuilt to make
1107 After the system has been upgraded, it is safe to remove the old
1108 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1109 assuming their contents is of no importance anymore. Old wtmp
1110 databases can only be used by last(1) and ac(8) after they have
1111 been converted to the new format using wtmpcvt(1).
1114 Introduce the kernel thread "deadlock resolver" (which can be enabled
1115 via the DEADLKRES option, see NOTES for more details) and the
1116 sleepq_type() function for sleepqueues.
1119 The rc.firewall and rc.firewall6 were unified, and
1120 rc.firewall6 and rc.d/ip6fw were removed.
1121 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1122 variables are obsoleted. Instead, the following new rc
1123 variables are added to rc.d/ipfw:
1125 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1126 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1127 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1129 The meanings correspond to the relevant IPv4 variables.
1135 The default terminal emulation for syscons(4) has been changed
1136 from cons25 to xterm on all platforms except pc98. This means
1137 that the /etc/ttys file needs to be updated to ensure correct
1138 operation of applications on the console.
1140 The terminal emulation style can be toggled per window by using
1141 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1142 options can be used to change the compile-time default back to
1145 To prevent graphical artifacts, make sure the TERM environment
1146 variable is set to match the terminal emulation that is being
1147 performed by syscons(4).
1150 The layout of the structure ieee80211req_scan_result has changed.
1151 Applications that require wireless scan results (e.g. ifconfig(8))
1152 from net80211 need to be recompiled.
1154 Applications such as wpa_supplicant(8) may require a full world
1155 build without using NO_CLEAN in order to get synchronized with the
1159 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1160 There's one kernel module for each firmware. Adding "device iwnfw"
1161 to the kernel configuration file means including all three firmware
1162 images inside the kernel. If you want to include just the one for
1163 your wireless card, use the devices iwn4965fw, iwn5000fw or
1167 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1168 into rc.d/netif. The changes are the following:
1170 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1171 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1172 Note that both variables need the "inet6" keyword at the head.
1174 Do not set $ipv6_network_interfaces manually if you do not
1175 understand what you are doing. It is not needed in most cases.
1177 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1180 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1181 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1183 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1184 all configured interfaces have "inet6 accept_rtadv" in the
1185 $ifconfig_IF_ipv6. These are for backward compatibility.
1187 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1188 functionality of interfaces with no corresponding
1189 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1190 and the default address selection policy of ip6addrctl(8)
1191 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1192 Note that if you want to configure IPv6 functionality on the
1193 disabled interfaces after boot, first you need to clear the flag by
1194 using ifconfig(8) like:
1196 ifconfig em0 inet6 -ifdisabled
1198 If YES, the default address selection policy is set as
1201 The default value of $ipv6_prefer is NO.
1203 4. If your system need to receive Router Advertisement messages,
1204 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1205 scripts automatically invoke rtsol(8) when the interface becomes
1206 UP. The Router Advertisement messages are used for SLAAC
1207 (State-Less Address AutoConfiguration).
1210 802.11s D3.03 support was committed. This is incompatible with the
1211 previous code, which was based on D3.0.
1214 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1215 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1216 control whether accepting Router Advertisement messages or not.
1217 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1218 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1219 The ifconfig(8) utility now supports these flags.
1222 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1223 mount(8) and -a option for df(1) to see them.
1226 The old tunable hw.bus.devctl_disable has been superseded by
1227 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1228 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1232 Remove the option STOP_NMI. The default action is now to use NMI only
1233 for KDB via the newly introduced function stop_cpus_hard() and
1234 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1237 The stable/8 branch created in subversion. This corresponds to the
1238 RELENG_8 branch in CVS.
1241 Bump the shared library version numbers for all libraries that do not
1242 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1243 __FreeBSD_version to 800105.
1246 Due to changes in the implementation of virtual network stack support,
1247 all network-related kernel modules must be recompiled. As this change
1248 breaks the ABI, bump __FreeBSD_version to 800104.
1251 The TOE interface to the TCP syncache has been modified to remove
1252 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1253 The cxgb driver is the only TOE consumer affected by this change, and
1254 needs to be recompiled along with the kernel. As this change breaks
1255 the ABI, bump __FreeBSD_version to 800103.
1258 Padding has been added to struct tcpcb, sackhint and tcpstat in
1259 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1260 maintaining the ABI. However, this change breaks the ABI, so bump
1261 __FreeBSD_version to 800102. User space tools that rely on the size of
1262 any of these structs (e.g. sockstat) need to be recompiled.
1265 The NFS_LEGACYRPC option has been removed along with the old kernel
1266 RPC implementation that this option selected. Kernel configurations
1267 may need to be adjusted.
1270 The network interface device nodes at /dev/net/<interface> have been
1271 removed. All ioctl operations can be performed the normal way using
1272 routing sockets. The kqueue functionality can generally be replaced
1273 with routing sockets.
1276 The documentation from the FreeBSD Documentation Project (Handbook,
1277 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1278 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1281 The ABI of various structures related to the SYSV IPC API have been
1282 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1283 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1287 Layout of struct vnet has changed as routing related variables were
1288 moved to their own Vimage module. Modules need to be recompiled. Bump
1289 __FreeBSD_version to 800099.
1292 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1293 respectively. As long as no more than 16 groups per process are used,
1294 no changes should be visible. When more than 16 groups are used, old
1295 binaries may fail if they call getgroups() or getgrouplist() with
1296 statically sized storage. Recompiling will work around this, but
1297 applications should be modified to use dynamically allocated storage
1298 for group arrays as POSIX.1-2008 does not cap an implementation's
1299 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1301 NFS and portalfs mounts may also be affected as the list of groups is
1302 truncated to 16. Users of NFS who use more than 16 groups, should
1303 take care that negative group permissions are not used on the exported
1304 file systems as they will not be reliable unless a GSSAPI based
1305 authentication method is used.
1308 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1309 option compiles in the support for adaptive spinning for lockmgrs
1310 which want to enable it. The lockinit() function now accepts the flag
1311 LK_ADAPTIVE in order to make the lock object subject to adaptive
1312 spinning when both held in write and read mode.
1315 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1316 changed. User applications that use this ioctl need to be rebuilt.
1319 The layout of struct thread has changed. Kernel and modules need to
1323 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1324 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1327 window(1) has been removed from the base system. It can now be
1328 installed from ports. The port is called misc/window.
1331 The way we are storing and accessing `routing table' entries has
1332 changed. Programs reading the FIB, like netstat, need to be
1336 A new netisr implementation has been added for FreeBSD 8. Network
1337 file system modules, such as igmp, ipdivert, and others, should be
1339 Bump __FreeBSD_version to 800096.
1342 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1346 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1347 Bump __FreeBSD_version to 800094.
1350 Add mnt_xflag field to 'struct mount'. File system modules need to be
1352 Bump __FreeBSD_version to 800093.
1355 The compiling option ADAPTIVE_SX has been retired while it has been
1356 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1357 The KPI for sx_init_flags() changes as accepting flags:
1358 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1359 been introduced in order to handle the reversed logic.
1360 Bump __FreeBSD_version to 800092.
1363 Add support for hierarchical jails. Remove global securelevel.
1364 Bump __FreeBSD_version to 800091.
1367 The layout of struct vnet_net has changed, therefore modules
1369 Bump __FreeBSD_version to 800090.
1372 The newly imported zic(8) produces a new format in the output. Please
1373 run tzsetup(8) to install the newly created data to /etc/localtime.
1376 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1377 hw.usb.* and is now consistent again with previous releases.
1380 802.11 monitor mode support was revised and driver api's were changed.
1381 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1382 of DLT_IEEE802_11. No user-visible data structures were changed but
1383 applications that use DLT_IEEE802_11 may require changes.
1384 Bump __FreeBSD_version to 800088.
1387 The layout of the following structs has changed: sysctl_oid,
1388 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1389 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1390 panics may be experienced. World rebuild is required for
1391 correctly checking networking state from userland.
1392 Bump __FreeBSD_version to 800085.
1395 MLDv2 and Source-Specific Multicast (SSM) have been merged
1396 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1397 The implementation of SSM within FreeBSD's IPv6 stack closely
1398 follows the IPv4 implementation.
1400 For kernel developers:
1402 * The most important changes are that the ip6_output() and
1403 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1404 and this lock has been downgraded to a non-recursive mutex.
1406 * As with the changes to the IPv4 stack to support SSM, filtering
1407 of inbound multicast traffic must now be performed by transport
1408 protocols within the IPv6 stack. This does not apply to TCP and
1409 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1411 * The KPIs used by IPv6 multicast are similar to those used by
1412 the IPv4 stack, with the following differences:
1413 * im6o_mc_filter() is analogous to imo_multicast_filter().
1414 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1415 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1416 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1417 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1418 for MLDv1 have an additional 'timer' argument which is used to
1419 jitter the initial membership report for the solicited-node
1420 multicast membership on-link.
1421 * This is not strictly needed for MLDv2, which already jitters
1422 its report transmissions. However, the 'timer' argument is
1423 preserved in case MLDv1 is active on the interface.
1425 * The KAME linked-list based IPv6 membership implementation has
1426 been refactored to use a vector similar to that used by the IPv4
1428 Code which maintains a list of its own multicast memberships
1429 internally, e.g. carp, has been updated to reflect the new
1432 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1433 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1434 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1435 implementation constraint which needs to be addressed in HEAD.
1437 For application developers:
1439 * The changes are broadly similar to those made for the IPv4
1442 * The use of IPv4 and IPv6 multicast socket options on the same
1443 socket, using mapped addresses, HAS NOT been tested or supported.
1445 * There are a number of issues with the implementation of various
1446 IPv6 multicast APIs which need to be resolved in the API surface
1447 before the implementation is fully compatible with KAME userland
1448 use, and these are mostly to do with interface index treatment.
1450 * The literature available discusses the use of either the delta / ASM
1451 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1452 using setsourcefilter(3)/getsourcefilter(3). For more information
1453 please refer to RFC 3768, 'Socket Interface Extensions for
1454 Multicast Source Filters'.
1456 * Applications which use the published RFC 3678 APIs should be fine.
1458 For systems administrators:
1460 * The mtest(8) utility has been refactored to support IPv6, in
1461 addition to IPv4. Interface addresses are no longer accepted
1462 as arguments, their names must be used instead. The utility
1463 will map the interface name to its first IPv4 address as
1464 returned by getifaddrs(3).
1466 * The ifmcstat(8) utility has also been updated to print the MLDv2
1467 endpoint state and source filter lists via sysctl(3).
1469 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1470 loopback of IPv6 multicast datagrams by default; it defaults to 1
1471 to preserve the existing behaviour. Disabling multicast loopback is
1472 recommended for optimal system performance.
1474 * The IPv6 MROUTING code has been changed to examine this sysctl
1475 instead of attempting to perform a group lookup before looping
1476 back forwarded datagrams.
1478 Bump __FreeBSD_version to 800084.
1481 Implement low-level Bluetooth HCI API.
1482 Bump __FreeBSD_version to 800083.
1485 The layout of struct malloc_type, used by modules to register new
1486 memory allocation types, has changed. Most modules will need to
1487 be rebuilt or panics may be experienced.
1488 Bump __FreeBSD_version to 800081.
1491 Anticipate overflowing inp_flags - add inp_flags2.
1492 This changes most offsets in inpcb, so checking v4 connection
1493 state will require a world rebuild.
1494 Bump __FreeBSD_version to 800080.
1497 Add an llentry to struct route and struct route_in6. Modules
1498 embedding a struct route will need to be recompiled.
1499 Bump __FreeBSD_version to 800079.
1502 The size of rt_metrics_lite and by extension rtentry has changed.
1503 Networking administration apps will need to be recompiled.
1504 The route command now supports show as an alias for get, weighting
1505 of routes, sticky and nostick flags to alter the behavior of stateful
1507 Bump __FreeBSD_version to 800078.
1510 Do not use Giant for kbdmux(4) locking. This is wrong and
1511 apparently causing more problems than it solves. This will
1512 re-open the issue where interrupt handlers may race with
1513 kbdmux(4) in polling mode. Typical symptoms include (but
1514 not limited to) duplicated and/or missing characters when
1515 low level console functions (such as gets) are used while
1516 interrupts are enabled (for example geli password prompt,
1517 mountroot prompt etc.). Disabling kbdmux(4) may help.
1520 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1521 kernel modules referencing any of the above need to be recompiled.
1522 Bump __FreeBSD_version to 800075.
1525 GEOM_PART has become the default partition slicer for storage devices,
1526 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1527 introduces some changes:
1529 MSDOS/EBR: the devices created from MSDOS extended partition entries
1530 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1531 to devices with offset-based names. fstabs may need to be modified.
1533 BSD: the "geometry does not match label" warning is harmless in most
1534 cases but it points to problems in file system misalignment with
1535 disk geometry. The "c" partition is now implicit, covers the whole
1536 top-level drive and cannot be (mis)used by users.
1538 General: Kernel dumps are now not allowed to be written to devices
1539 whose partition types indicate they are meant to be used for file
1540 systems (or, in case of MSDOS partitions, as something else than
1543 Most of these changes date approximately from 200812.
1546 The uscanner(4) driver has been removed from the kernel. This follows
1547 Linux removing theirs in 2.6 and making libusb the default interface
1548 (supported by sane).
1551 The multicast forwarding code has been cleaned up. netstat(1)
1552 only relies on KVM now for printing bandwidth upcall meters.
1553 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1554 ip6_mroute_mod respectively. The config(5) options for statically
1555 compiling this code remain the same, i.e. 'options MROUTING'.
1558 Support for the IFF_NEEDSGIANT network interface flag has been
1559 removed, which means that non-MPSAFE network device drivers are no
1560 longer supported. In particular, if_ar, if_sr, and network device
1561 drivers from the old (legacy) USB stack can no longer be built or
1565 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1566 a bunch of new language catalog files have also been added.
1567 This means that some common libc messages are now localized and
1568 they depend on the LC_MESSAGES environmental variable.
1571 The k8temp(4) driver has been renamed to amdtemp(4) since
1572 support for Family 10 and Family 11 CPU families was added.
1575 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1576 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1578 For kernel developers, the most important changes are that the
1579 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1580 and this lock has been downgraded to a non-recursive mutex.
1582 Transport protocols (UDP, Raw IP) are now responsible for filtering
1583 inbound multicast traffic according to group membership and source
1584 filters. The imo_multicast_filter() KPI exists for this purpose.
1585 Transports which do not use multicast (SCTP, TCP) already reject
1586 multicast by default. Forwarding and receive performance may improve
1587 as a mutex acquisition is no longer needed in the ip_input()
1588 low-level input path. in_addmulti() and in_delmulti() are shimmed
1589 to new KPIs which exist to support SSM in-kernel.
1591 For application developers, it is recommended that loopback of
1592 multicast datagrams be disabled for best performance, as this
1593 will still cause the lock to be taken for each looped-back
1594 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1595 be tuned to 0 to disable loopback by default; it defaults to 1
1596 to preserve the existing behaviour.
1598 For systems administrators, to obtain best performance with
1599 multicast reception and multiple groups, it is always recommended
1600 that a card with a suitably precise hash filter is used. Hash
1601 collisions will still result in the lock being taken within the
1602 transport protocol input path to check group membership.
1604 If deploying FreeBSD in an environment with IGMP snooping switches,
1605 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1606 enabled; this forces 224.0.0.0/24 group membership to be announced
1609 The size of 'struct igmpstat' has changed; netstat needs to be
1610 recompiled to reflect this.
1611 Bump __FreeBSD_version to 800070.
1614 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1615 updated to use it. This requires a buildworld/installworld in order to
1616 update the library and dependencies (usbconfig, etc). Its advisable to
1617 rebuild all ports which uses libusb. More specific directions are given
1618 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1619 libusb are no longer required and can be removed.
1622 A workaround is committed to allow the creation of System V shared
1623 memory segment of size > 2 GB on the 64-bit architectures.
1624 Due to a limitation of the existing ABI, the shm_segsz member
1625 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1626 wrong for large segments. Note that limits must be explicitly
1627 raised to allow such segments to be created.
1630 The layout of struct ifnet has changed, requiring a rebuild of all
1631 network device driver modules.
1634 The /dev handling for the new USB stack has changed, a
1635 buildworld/installworld is required for libusb20.
1638 The new USB2 stack has now been permanently moved in and all kernel and
1639 module names reverted to their previous values (eg, usb, ehci, ohci,
1640 ums, ...). The old usb stack can be compiled in by prefixing the name
1641 with the letter 'o', the old usb modules have been removed.
1642 Updating entry 20090216 for xorg and 20090215 for libmap may still
1646 The rc.conf(5) option if_up_delay has been renamed to
1647 defaultroute_delay to better reflect its purpose. If you have
1648 customized this setting in /etc/rc.conf you need to update it to
1652 xorg 7.4 wants to configure its input devices via hald which does not
1653 yet work with USB2. If the keyboard/mouse does not work in xorg then
1655 Option "AllowEmptyInput" "off"
1656 to your ServerLayout section. This will cause X to use the configured
1657 kbd and mouse sections from your xorg.conf.
1660 The GENERIC kernels for all architectures now default to the new USB2
1661 stack. No kernel config options or code have been removed so if a
1662 problem arises please report it and optionally revert to the old USB
1663 stack. If you are loading USB kernel modules or have a custom kernel
1664 that includes GENERIC then ensure that usb names are also changed over,
1665 eg uftdi -> usb2_serial_ftdi.
1667 Older programs linked against the ports libusb 0.1 need to be
1668 redirected to the new stack's libusb20. /etc/libmap.conf can
1670 # Map old usb library to new one for usb2 stack
1671 libusb-0.1.so.8 libusb20.so.1
1674 All USB ethernet devices now attach as interfaces under the name ueN
1675 (eg. ue0). This is to provide a predictable name as vendors often
1676 change usb chipsets in a product without notice.
1679 The ichsmb(4) driver has been changed to require SMBus slave
1680 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1681 All of the other SMBus controller drivers require left-justified
1682 slave addresses, so this change makes all the drivers provide the
1686 INET6 statistics (struct ip6stat) was updated.
1687 netstat(1) needs to be recompiled.
1690 NTFS has been removed from GENERIC kernel on amd64 to match
1691 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1692 will load ntfs.ko module automatically when NTFS support is
1693 actually needed, unless ntfs.ko is not installed or security
1694 level prohibits loading kernel modules. If either is the case,
1695 "options NTFS" has to be added into kernel config.
1698 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1699 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1700 800061. User space tools that rely on the size of struct tcpcb in
1701 tcp_var.h (e.g. sockstat) need to be recompiled.
1704 ng_tty(4) module updated to match the new TTY subsystem.
1705 Due to API change, user-level applications must be updated.
1706 New API support added to mpd5 CVS and expected to be present
1707 in next mpd5.3 release.
1710 With __FreeBSD_version 800060 the makefs tool is part of
1711 the base system (it was a port).
1714 The afdata and ifnet locks have been changed from mutexes to
1715 rwlocks, network modules will need to be re-compiled.
1718 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1719 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1720 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1721 architecture and 40 bytes on 64-bit architecture. The userland
1722 applications "arp" and "ndp" have been updated accordingly.
1723 The output from "netstat -r" shows only routing entries and
1724 none of the L2 information.
1727 __FreeBSD_version 800057 marks the switchover from the
1728 binary ath hal to source code. Users must add the line:
1730 options AH_SUPPORT_AR5416
1732 to their kernel config files when specifying:
1736 The ath_hal module no longer exists; the code is now compiled
1737 together with the driver in the ath module. It is now
1738 possible to tailor chip support (i.e. reduce the set of chips
1739 and thereby the code size); consult ath_hal(4) for details.
1742 __FreeBSD_version 800054 adds memory barriers to
1743 <machine/atomic.h>, new interfaces to ifnet to facilitate
1744 multiple hardware transmit queues for cards that support
1745 them, and a lock-less ring-buffer implementation to
1746 enable drivers to more efficiently manage queueing of
1750 A new version of ZFS (version 13) has been merged to -HEAD.
1751 This version has zpool attribute "listsnapshots" off by
1752 default, which means "zfs list" does not show snapshots,
1753 and is the same as Solaris behavior.
1756 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1759 The uhci, ohci, ehci and slhci USB Host controller drivers have
1760 been put into separate modules. If you load the usb module
1761 separately through loader.conf you will need to load the
1762 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1763 controller add the following to loader.conf:
1769 The ABI used by the PMC toolset has changed. Please keep
1770 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1774 atapci kernel module now includes only generic PCI ATA
1775 driver. AHCI driver moved to ataahci kernel module.
1776 All vendor-specific code moved into separate kernel modules:
1777 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1778 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1779 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1780 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1783 The TTY subsystem of the kernel has been replaced by a new
1784 implementation, which provides better scalability and an
1785 improved driver model. Most common drivers have been migrated to
1786 the new TTY subsystem, while others have not. The following
1787 drivers have not yet been ported to the new TTY layer:
1790 cy, digi, rc, rp, sio
1796 ng_h4, ng_tty, ppp, sl, snp
1798 Adding these drivers to your kernel configuration file shall
1799 cause compilation to fail.
1802 ntpd has been upgraded to 4.2.4p5.
1805 OpenSSH has been upgraded to 5.1p1.
1807 For many years, FreeBSD's version of OpenSSH preferred DSA
1808 over RSA for host and user authentication keys. With this
1809 upgrade, we've switched to the vendor's default of RSA over
1810 DSA. This may cause upgraded clients to warn about unknown
1811 host keys even for previously known hosts. Users should
1812 follow the usual procedure for verifying host keys before
1813 accepting the RSA key.
1815 This can be circumvented by setting the "HostKeyAlgorithms"
1816 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1819 Please note that the sequence of keys offered for
1820 authentication has been changed as well. You may want to
1821 specify IdentityFile in a different order to revert this
1825 The sio(4) driver has been removed from the i386 and amd64
1826 kernel configuration files. This means uart(4) is now the
1827 default serial port driver on those platforms as well.
1829 To prevent collisions with the sio(4) driver, the uart(4) driver
1830 uses different names for its device nodes. This means the
1831 onboard serial port will now most likely be called "ttyu0"
1832 instead of "ttyd0". You may need to reconfigure applications to
1833 use the new device names.
1835 When using the serial port as a boot console, be sure to update
1836 /boot/device.hints and /etc/ttys before booting the new kernel.
1837 If you forget to do so, you can still manually specify the hints
1838 at the loader prompt:
1840 set hint.uart.0.at="isa"
1841 set hint.uart.0.port="0x3F8"
1842 set hint.uart.0.flags="0x10"
1843 set hint.uart.0.irq="4"
1847 The gpt(8) utility has been removed. Use gpart(8) to partition
1851 The version that Linuxulator emulates was changed from 2.4.2
1852 to 2.6.16. If you experience any problems with Linux binaries
1853 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1854 if it fixes the problem contact emulation mailing list.
1857 ISDN4BSD (I4B) was removed from the src tree. You may need to
1858 update a your kernel configuration and remove relevant entries.
1861 I have checked in code to support multiple routing tables.
1862 See the man pages setfib(1) and setfib(2).
1863 This is a hopefully backwards compatible version,
1864 but to make use of it you need to compile your kernel
1865 with options ROUTETABLES=2 (or more up to 16).
1868 The 802.11 wireless support was redone to enable multi-bss
1869 operation on devices that are capable. The underlying device
1870 is no longer used directly but instead wlanX devices are
1871 cloned with ifconfig. This requires changes to rc.conf files.
1872 For example, change:
1873 ifconfig_ath0="WPA DHCP"
1876 ifconfig_wlan0="WPA DHCP"
1877 see rc.conf(5) for more details. In addition, mergemaster of
1878 /etc/rc.d is highly recommended. Simultaneous update of userland
1879 and kernel wouldn't hurt either.
1881 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1882 modules were merged into the base wlan module. All references
1883 to these modules (e.g. in kernel config files) must be removed.
1886 psm(4) has gained write(2) support in native operation level.
1887 Arbitrary commands can be written to /dev/psm%d and status can
1888 be read back from it. Therefore, an application is responsible
1889 for status validation and error recovery. It is a no-op in
1890 other operation levels.
1893 Support for KSE threading has been removed from the kernel. To
1894 run legacy applications linked against KSE libmap.conf may
1895 be used. The following libmap.conf may be used to ensure
1896 compatibility with any prior release:
1898 libpthread.so.1 libthr.so.1
1899 libpthread.so.2 libthr.so.2
1900 libkse.so.3 libthr.so.3
1903 The layout of struct vmspace has changed. This affects libkvm
1904 and any executables that link against libkvm and use the
1905 kvm_getprocs() function. In particular, but not exclusively,
1906 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1907 The effects are minimal, but it's advisable to upgrade world
1911 The latest em driver no longer has support in it for the
1912 82575 adapter, this is now moved to the igb driver. The
1913 split was done to make new features that are incompatible
1914 with older hardware easier to do.
1917 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1918 likewise the kernel option is now GEOM_LINUX_LVM.
1921 The default NFS mount mode has changed from UDP to TCP for
1922 increased reliability. If you rely on (insecurely) NFS
1923 mounting across a firewall you may need to update your
1927 Belatedly note the addition of m_collapse for compacting
1931 The fts(3) structures have been changed to use adequate
1932 integer types for their members and so to be able to cope
1933 with huge file trees. The old fts(3) ABI is preserved
1934 through symbol versioning in libc, so third-party binaries
1935 using fts(3) should still work, although they will not take
1936 advantage of the extended types. At the same time, some
1937 third-party software might fail to build after this change
1938 due to unportable assumptions made in its source code about
1939 fts(3) structure members. Such software should be fixed
1940 by its vendor or, in the worst case, in the ports tree.
1941 FreeBSD_version 800015 marks this change for the unlikely
1942 case that a portable fix is impossible.
1945 To upgrade to -current after this date, you must be running
1946 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1947 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1950 The ADAPTIVE_GIANT kernel option has been retired because its
1951 functionality is the default now.
1954 The AT keyboard emulation of sunkbd(4) has been turned on
1955 by default. In order to make the special symbols of the Sun
1956 keyboards driven by sunkbd(4) work under X these now have
1957 to be configured the same way as Sun USB keyboards driven
1958 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1960 Option "XkbLayout" "us"
1961 Option "XkbRules" "xorg"
1962 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1965 It has been decided that it is desirable to provide ABI
1966 backwards compatibility to the FreeBSD 4/5/6 versions of the
1967 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1968 broken with the introduction of PCI domain support (see the
1969 20070930 entry). Unfortunately, this required the ABI of
1970 PCIOCGETCONF to be broken again in order to be able to
1971 provide backwards compatibility to the old version of that
1972 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1973 again. As for prominent ports this affects neither pciutils
1974 nor xorg-server this time, the hal port needs to be rebuilt
1978 The misnamed kthread_create() and friends have been renamed
1979 to kproc_create() etc. Many of the callers already
1980 used kproc_start()..
1981 I will return kthread_create() and friends in a while
1982 with implementations that actually create threads, not procs.
1983 Renaming corresponds with version 800002.
1992 Avoid using make -j when upgrading. While generally safe, there are
1993 sometimes problems using -j to upgrade. If your upgrade fails with
1994 -j, please try again without -j. From time to time in the past there
1995 have been problems using -j with buildworld and/or installworld. This
1996 is especially true when upgrading between "distant" versions (eg one
1997 that cross a major release boundary or several minor releases, or when
1998 several months have passed on the -current branch).
2000 Sometimes, obscure build problems are the result of environment
2001 poisoning. This can happen because the make utility reads its
2002 environment when searching for values for global variables. To run
2003 your build attempts in an "environmental clean room", prefix all make
2004 commands with 'env -i '. See the env(1) manual page for more details.
2006 When upgrading from one major version to another it is generally best
2007 to upgrade to the latest code in the currently installed branch first,
2008 then do an upgrade to the new branch. This is the best-tested upgrade
2009 path, and has the highest probability of being successful. Please try
2010 this approach before reporting problems with a major version upgrade.
2012 When upgrading a live system, having a root shell around before
2013 installing anything can help undo problems. Not having a root shell
2014 around can lead to problems if pam has changed too much from your
2015 starting point to allow continued authentication after the upgrade.
2019 When upgrading the boot ZFS pool to a new version, always follow
2022 1.) recompile and reinstall the ZFS boot loader and boot block
2023 (this is part of "make buildworld" and "make installworld")
2025 2.) update the ZFS boot block on your boot drive
2027 The following example updates the ZFS boot block on the first
2028 partition (freebsd-boot) of a GPT partitioned drive ad0:
2029 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2031 Non-boot pools do not need these updates.
2035 If you are updating from a prior version of FreeBSD (even one just
2036 a few days old), you should follow this procedure. It is the most
2037 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2039 make kernel-toolchain
2040 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2041 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2043 To test a kernel once
2044 ---------------------
2045 If you just want to boot a kernel once (because you are not sure
2046 if it works, or if you want to boot a known bad kernel to provide
2047 debugging information) run
2048 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2049 nextboot -k testkernel
2051 To just build a kernel when you know that it won't mess you up
2052 --------------------------------------------------------------
2053 This assumes you are already running a CURRENT system. Replace
2054 ${arch} with the architecture of your machine (e.g. "i386",
2055 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2057 cd src/sys/${arch}/conf
2058 config KERNEL_NAME_HERE
2059 cd ../compile/KERNEL_NAME_HERE
2064 If this fails, go to the "To build a kernel" section.
2066 To rebuild everything and install it on the current system.
2067 -----------------------------------------------------------
2068 # Note: sometimes if you are running current you gotta do more than
2069 # is listed here if you are upgrading from a really old current.
2071 <make sure you have good level 0 dumps>
2073 make kernel KERNCONF=YOUR_KERNEL_HERE
2075 <reboot in single user> [3]
2082 To cross-install current onto a separate partition
2083 --------------------------------------------------
2084 # In this approach we use a separate partition to hold
2085 # current's root, 'usr', and 'var' directories. A partition
2086 # holding "/", "/usr" and "/var" should be about 2GB in
2089 <make sure you have good level 0 dumps>
2092 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2093 <maybe newfs current's root partition>
2094 <mount current's root partition on directory ${CURRENT_ROOT}>
2095 make installworld DESTDIR=${CURRENT_ROOT}
2096 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2097 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2098 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2099 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2100 <reboot into current>
2101 <do a "native" rebuild/install as described in the previous section>
2102 <maybe install compatibility libraries from ports/misc/compat*>
2106 To upgrade in-place from stable to current
2107 ----------------------------------------------
2108 <make sure you have good level 0 dumps>
2110 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2112 <reboot in single user> [3]
2119 Make sure that you've read the UPDATING file to understand the
2120 tweaks to various things you need. At this point in the life
2121 cycle of current, things change often and you are on your own
2122 to cope. The defaults can also change, so please read ALL of
2123 the UPDATING entries.
2125 Also, if you are tracking -current, you must be subscribed to
2126 freebsd-current@freebsd.org. Make sure that before you update
2127 your sources that you have read and understood all the recent
2128 messages there. If in doubt, please track -stable which has
2129 much fewer pitfalls.
2131 [1] If you have third party modules, such as vmware, you
2132 should disable them at this point so they don't crash your
2135 [3] From the bootblocks, boot -s, and then do
2140 adjkerntz -i # if CMOS is wall time
2141 Also, when doing a major release upgrade, it is required that
2142 you boot into single user mode to do the installworld.
2144 [4] Note: This step is non-optional. Failure to do this step
2145 can result in a significant reduction in the functionality of the
2146 system. Attempting to do it by hand is not recommended and those
2147 that pursue this avenue should read this file carefully, as well
2148 as the archives of freebsd-current and freebsd-hackers mailing lists
2149 for potential gotchas. The -U option is also useful to consider.
2150 See mergemaster(8) for more information.
2152 [5] Usually this step is a noop. However, from time to time
2153 you may need to do this if you get unknown user in the following
2154 step. It never hurts to do it all the time. You may need to
2155 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2156 install) after the buildworld before this step if you last updated
2157 from current before 20130425 or from -stable before 20130430.
2159 [6] This only deletes old files and directories. Old libraries
2160 can be deleted by "make delete-old-libs", but you have to make
2161 sure that no program is using those libraries anymore.
2163 [8] In order to have a kernel that can run the 4.x binaries needed to
2164 do an installworld, you must include the COMPAT_FREEBSD4 option in
2165 your kernel. Failure to do so may leave you with a system that is
2166 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2167 required to run the 5.x binaries on more recent kernels. And so on
2168 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2170 Make sure that you merge any new devices from GENERIC since the
2171 last time you updated your kernel config file.
2173 [9] When checking out sources, you must include the -P flag to have
2174 cvs prune empty directories.
2176 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2177 "?=" instead of the "=" assignment operator, so that buildworld can
2178 override the CPUTYPE if it needs to.
2180 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2181 not on the command line, or in /etc/make.conf. buildworld will
2182 warn if it is improperly defined.
2185 This file contains a list, in reverse chronological order, of major
2186 breakages in tracking -current. It is not guaranteed to be a complete
2187 list of such breakages, and only contains entries since October 10, 2007.
2188 If you need to see UPDATING entries from before that date, you will need
2189 to fetch an UPDATING file from an older FreeBSD release.
2191 Copyright information:
2193 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2195 Redistribution, publication, translation and use, with or without
2196 modification, in full or in part, in any form or format of this
2197 document are permitted without further permission from the author.
2199 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2200 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2201 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2202 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2203 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2204 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2205 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2206 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2207 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2208 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2209 POSSIBILITY OF SUCH DAMAGE.
2211 Contact Warner Losh if you have any questions about your use of