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