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 As of r316810 for ipfilter, keep frags is no longer assumed when
21 keep state is specified in a rule. r316810 aligns ipfilter with
22 documentation in man pages separating keep frags from keep state.
23 This allows keep state to specified without forcing keep frags
24 and allows keep frags to be specified independently of keep state.
25 To maintain previous behaviour, also specify keep frags with
26 keep state (as documented in ipf.conf.5).
29 The code that provides support for ZFS .zfs/ directory functionality
30 has been reimplemented. It's not possible now to create a snapshot
31 by mkdir under .zfs/snapshot/. That should be the only user visible
35 The NONE and HPN patches has been removed from OpenSSH. They are
36 still available in the security/openssh-portable port.
39 r292223 changed the internal interface between the nfsd.ko and
40 nfscommon.ko modules. As such, they must both be upgraded to-gether.
41 __FreeBSD_version has been bumped because of this.
44 Qlogic 24xx/25xx firmware images were updated from 5.5.0 to 7.3.0.
45 Kernel modules isp_2400_multi and isp_2500_multi were removed and
46 should be replaced with isp_2400 and isp_2500 modules respectively.
49 The menu.rc and loader.rc files will now be replaced during
50 upgrades. Please migrate local changes to menu.rc.local and
51 loader.rc.local instead.
54 NTP has been upgraded to 4.2.8p4.
57 ALLOW_DEPRECATED_ATF_TOOLS/ATFFILE support has been removed from
58 atf.test.mk (included from bsd.test.mk). Please upgrade devel/atf
59 and devel/kyua to version 0.20+ and adjust any calling code to work
60 with Kyuafile and kyua.
63 The polarity of Pulse Per Second (PPS) capture events with the
64 uart(4) driver has been corrected. Prior to this change the PPS
65 "assert" event corresponded to the trailing edge of a positive PPS
66 pulse and the "clear" event was the leading edge of the next pulse.
68 As the width of a PPS pulse in a typical GPS receiver is on the
69 order of 1 millisecond, most users will not notice any significant
70 difference with this change.
72 Anyone who has compensated for the historical polarity reversal by
73 configuring a negative offset equal to the pulse width will need to
74 remove that workaround.
77 From legacy ata(4) driver was removed support for SATA controllers
78 supported by more functional drivers ahci(4), siis(4) and mvs(4).
79 Kernel modules ataahci and ataadaptec were removed completely,
80 replaced by ahci and mvs modules respectively.
86 As ZFS requires more kernel stack pages than is the default on some
87 architectures e.g. i386, it now warns if KSTACK_PAGES is less than
88 ZFS_MIN_KSTACK_PAGES (which is 4 at the time of writing).
90 Please consider using 'options KSTACK_PAGES=X' where X is greater
91 than or equal to ZFS_MIN_KSTACK_PAGES i.e. 4 in such configurations.
94 The default Unbound configuration now enables remote control
95 using a local socket. Users who have already enabled the
96 local_unbound service should regenerate their configuration
97 by running "service local_unbound setup" as root.
100 An additional fix for the issue described in the 20150614 sendmail
101 entry below has been been committed in revision 284786.
104 The fix for the issue described in the 20150614 sendmail entry
105 below has been been committed in revision 284485. The work
106 around described in that entry is no longer needed unless the
107 default setting is overridden by a confDH_PARAMETERS configuration
108 setting of '5' or pointing to a 512 bit DH parameter file.
111 The import of openssl to address the FreeBSD-SA-15:10.openssl
112 security advisory includes a change which rejects handshakes
113 with DH parameters below 768 bits. sendmail releases prior
114 to 8.15.2 (not yet released), defaulted to a 512 bit
115 DH parameter setting for client connections. To work around
116 this interoperability, sendmail can be configured to use a
117 2048 bit DH parameter by:
119 1. Edit /etc/mail/`hostname`.mc
120 2. If a setting for confDH_PARAMETERS does not exist or
121 exists and is set to a string beginning with '5',
123 3. If a setting for confDH_PARAMETERS exists and is set to
124 a file path, create a new file with:
125 openssl dhparam -out /path/to/file 2048
126 4. Rebuild the .cf file:
127 cd /etc/mail/; make; make install
129 cd /etc/mail/; make restart
131 A sendmail patch is coming, at which time this file will be
135 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
136 defined in symlink(7); previously symlinks were silently ignored.
139 The const qualifier has been removed from iconv(3) to comply with
140 POSIX. The ports tree is aware of this from r384038 onwards.
143 At svn r275807, The default linux compat kernel ABI has been adjusted
144 to 2.6.18 in support of the linux-c6 compat ports infrastructure
145 update. If you wish to continue using the linux-f10 compat ports,
146 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
147 encouraged to update their linux-compat packages to linux-c6 during
148 their next update cycle.
150 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
153 pjdfstest has been integrated into kyua as an opt-in test suite.
154 Please see share/doc/pjdfstest/README for a more details on how to
161 The ofwfb driver, used to provide a graphics console on PowerPC when
162 using vt(4), no longer allows mmap() of all of physical memory. This
163 will prevent Xorg on PowerPC with some ATI graphics cards from
164 initializing properly unless x11-servers/xorg-server is updated to
168 The libatf-c and libatf-c++ major versions were downgraded to 0 and
169 1 respectively to match the upstream numbers. They were out of
170 sync because, when they were originally added to FreeBSD, the
171 upstream versions were not respected. These libraries are private
172 and not yet built by default, so renumbering them should be a
173 non-issue. However, unclean source trees will yield broken test
174 programs once the operator executes "make delete-old-libs" after a
177 Additionally, the atf-sh binary was made private by moving it into
178 /usr/libexec/. Already-built shell test programs will keep the
179 path to the old binary so they will break after "make delete-old"
182 If you are using WITH_TESTS=yes (not the default), wipe the object
183 tree and rebuild from scratch to prevent spurious test failures.
184 This is only needed once: the misnumbered libraries and misplaced
185 binaries have been added to OptionalObsoleteFiles.inc so they will
186 be removed during a clean upgrade.
189 The ixgbe tunables now match their sysctl counterparts, for example:
190 hw.ixgbe.enable_aim => hw.ix.enable_aim
191 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
194 The NFSv4.1 server committed by r269398 changes the internal
195 function call interfaces used between the NFS and krpc modules.
196 As such, __FreeBSD_version was bumped.
199 The default unbound configuration has been modified to address
200 issues with reverse lookups on networks that use private
201 address ranges. If you use the local_unbound service, run
202 "service local_unbound setup" as root to regenerate your
203 configuration, then "service local_unbound reload" to load the
207 It is no longer necessary to include the dwarf version in your DEBUG
208 options in your kernel config file. The bug that required it to be
209 placed in the config file has bene fixed. DEBUG should now just
210 contain -g. The build system will automatically update things
211 to do the right thing.
214 Several ABI breaking changes were merged to CTL and new iSCSI code.
215 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
216 iscsictl need to be rebuilt to work with a new kernel.
219 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
220 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
221 which differs from the behaviour controlled by this knob.)
224 On i386 and amd64 systems, the onifconsole flag is now set by default
225 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
226 as a login TTY if it is set in the bootloader as an active kernel
227 console. No changes in behavior should result otherwise. To revert to
228 the previous behavior, set ttyu0 to "off" in /etc/ttys.
231 Clang and llvm have been upgraded to 3.4.1 release.
234 Clang and llvm have been upgraded to 3.4 release.
237 If a Makefile in a tests/ directory was auto-generating a Kyuafile
238 instead of providing an explicit one, this would prevent such
239 Makefile from providing its own Kyuafile in the future during
240 NO_CLEAN builds. This has been fixed in the Makefiles but manual
241 intervention is needed to clean an objdir if you use NO_CLEAN:
242 # find /usr/obj -name Kyuafile | xargs rm -f
245 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
246 capability mode support. Please note that enabling the feature in
247 kernel is still highly recommended.
250 OpenSSH is now built with sandbox support, and will use sandbox as
251 the default privilege separation method. This requires Capsicum
252 capability mode support in kernel.
255 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
256 been deprecated and will not be part of FreeBSD 11.0 and later
257 releases. If you use this driver, please consider switching to
258 the nfe(4) driver instead.
264 The behavior of gss_pseudo_random() for the krb5 mechanism
265 has changed, for applications requesting a longer random string
266 than produced by the underlying enctype's pseudo-random() function.
267 In particular, the random string produced from a session key of
268 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
269 be different at the 17th octet and later, after this change.
270 The counter used in the PRF+ construction is now encoded as a
271 big-endian integer in accordance with RFC 4402.
272 __FreeBSD_version is bumped to 1000701.
275 The WITHOUT_ATF build knob has been removed and its functionality
276 has been subsumed into the more generic WITHOUT_TESTS. If you were
277 using the former to disable the build of the ATF libraries, you
278 should change your settings to use the latter.
281 The default version of mtree is nmtree which is obtained from
282 NetBSD. The output is generally the same, but may vary
283 slightly. If you found you need identical output adding
284 "-F freebsd9" to the command line should do the trick. For the
285 time being, the old mtree is available as fmtree.
288 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
289 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
290 1.1.4_8 and verify bsdyml not linked in, before running "make
292 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
294 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
297 The rc.d/jail script has been updated to support jail(8)
298 configuration file. The "jail_<jname>_*" rc.conf(5) variables
299 for per-jail configuration are automatically converted to
300 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
301 This is transparently backward compatible. See below about some
302 incompatibilities and rc.conf(5) manual page for more details.
304 These variables are now deprecated in favor of jail(8) configuration
305 file. One can use "rc.d/jail config <jname>" command to generate
306 a jail(8) configuration file in /var/run/jail.<jname>.conf without
307 running the jail(8) utility. The default pathname of the
308 configuration file is /etc/jail.conf and can be specified by
309 using $jail_conf or $jail_<jname>_conf variables.
311 Please note that jail_devfs_ruleset accepts an integer at
312 this moment. Please consider to rewrite the ruleset name
316 BIND has been removed from the base system. If all you need
317 is a local resolver, simply enable and start the local_unbound
318 service instead. Otherwise, several versions of BIND are
319 available in the ports tree. The dns/bind99 port is one example.
321 With this change, nslookup(1) and dig(1) are no longer in the base
322 system. Users should instead use host(1) and drill(1) which are
323 in the base system. Alternatively, nslookup and dig can
324 be obtained by installing the dns/bind-tools port.
327 With the addition of unbound(8), a new unbound user is now
328 required during installworld. "mergemaster -p" can be used to
329 add the user prior to installworld, as documented in the handbook.
332 OpenSSH is now built with DNSSEC support, and will by default
333 silently trust signed SSHFP records. This can be controlled with
334 the VerifyHostKeyDNS client configuration setting. DNSSEC support
335 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
338 The GNU Compiler Collection and C++ standard library (libstdc++)
339 are no longer built by default on platforms where clang is the system
340 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
344 The PROCDESC kernel option is now part of the GENERIC kernel
345 configuration and is required for the rwhod(8) to work.
346 If you are using custom kernel configuration, you should include
350 The API and ABI related to the Capsicum framework was modified
351 in backward incompatible way. The userland libraries and programs
352 have to be recompiled to work with the new kernel. This includes the
353 following libraries and programs, but the whole buildworld is
354 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
355 kdump, procstat, rwho, rwhod, uniq.
358 AES-NI intrinsic support has been added to gcc. The AES-NI module
359 has been updated to use this support. A new gcc is required to build
360 the aesni module on both i386 and amd64.
363 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
364 Thus "device padlock_rng" and "device rdrand_rng" should be
365 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
368 WITH_ICONV has been split into two feature sets. WITH_ICONV now
369 enables just the iconv* functionality and is now on by default.
370 WITH_LIBICONV_COMPAT enables the libiconv api and link time
371 compatability. Set WITHOUT_ICONV to build the old way.
372 If you have been using WITH_ICONV before, you will very likely
373 need to turn on WITH_LIBICONV_COMPAT.
376 INVARIANTS option now enables DEBUG for code with OpenSolaris and
377 Illumos origin, including ZFS. If you have INVARIANTS in your
378 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
380 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
381 locks if WITNESS option was set. Because that generated a lot of
382 witness(9) reports and all of them were believed to be false
383 positives, this is no longer done. New option OPENSOLARIS_WITNESS
384 can be used to achieve the previous behavior.
387 Timer values in IPv6 data structures now use time_uptime instead
388 of time_second. Although this is not a user-visible functional
389 change, userland utilities which directly use them---ndp(8),
390 rtadvd(8), and rtsold(8) in the base system---need to be updated
394 find -delete can now delete the pathnames given as arguments,
395 instead of only files found below them or if the pathname did
396 not contain any slashes. Formerly, the following error message
399 find: -delete: <path>: relative path potentially not safe
401 Deleting the pathnames given as arguments can be prevented
402 without error messages using -mindepth 1 or by changing
403 directory and passing "." as argument to find. This works in the
404 old as well as the new version of find.
407 Behavior of devfs rules path matching has been changed.
408 Pattern is now always matched against fully qualified devfs
409 path and slash characters must be explicitly matched by
410 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
411 subdirectories must be reviewed.
414 The default ARM ABI has changed to the ARM EABI. The old ABI is
415 incompatible with the ARM EABI and all programs and modules will
416 need to be rebuilt to work with a new kernel.
418 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
420 NOTE: Support for the old ABI will be removed in the future and
421 users are advised to upgrade.
424 pkg_install has been disconnected from the build if you really need it
425 you should add WITH_PKGTOOLS in your src.conf(5).
428 Most of network statistics structures were changed to be able
429 keep 64-bits counters. Thus all tools, that work with networking
430 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
433 Fix a bug that allowed a tracing process (e.g. gdb) to write
434 to a memory-mapped file in the traced process's address space
435 even if neither the traced process nor the tracing process had
436 write access to that file.
439 CVS has been removed from the base system. An exact copy
440 of the code is available from the devel/cvs port.
443 Some people report the following error after the switch to bmake:
445 make: illegal option -- J
446 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
448 *** [buildworld] Error code 2
450 this likely due to an old instance of make in
451 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
452 which src/Makefile will use that blindly, if it exists, so if
453 you see the above error:
455 rm -rf `make -V MAKEPATH`
460 Use bmake by default.
461 Whereas before one could choose to build with bmake via
462 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
463 make. The goal is to remove these knobs for 10-RELEASE.
465 It is worth noting that bmake (like gmake) treats the command
466 line as the unit of failure, rather than statements within the
467 command line. Thus '(cd some/where && dosomething)' is safer
468 than 'cd some/where; dosomething'. The '()' allows consistent
469 behavior in parallel build.
472 Fix a bug that allows NFS clients to issue READDIR on files.
475 The WITHOUT_IDEA option has been removed because
476 the IDEA patent expired.
479 The sysctl which controls TRIM support under ZFS has been renamed
480 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
484 The mergemaster command now uses the default MAKEOBJDIRPREFIX
485 rather than creating it's own in the temporary directory in
486 order allow access to bootstrapped versions of tools such as
487 install and mtree. When upgrading from version of FreeBSD where
488 the install command does not support -l, you will need to
489 install a new mergemaster command if mergemaster -p is required.
490 This can be accomplished with the command (cd src/usr.sbin/mergemaster
494 Legacy ATA stack, disabled and replaced by new CAM-based one since
495 FreeBSD 9.0, completely removed from the sources. Kernel modules
496 atadisk and atapi*, user-level tools atacontrol and burncd are
497 removed. Kernel option `options ATA_CAM` is now permanently enabled
501 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
502 and socketpair(2). Software, in particular Kerberos, may
503 automatically detect and use these during building. The resulting
504 binaries will not work on older kernels.
507 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
508 information, see the respective 20130304 entry).
511 Recent commits to callout(9) changed the size of struct callout,
512 so the KBI is probably heavily disturbed. Also, some functions
513 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
514 by macros. Every kernel module using it won't load, so rebuild
517 The ctl device has been re-enabled in GENERIC for i386 and amd64,
518 but does not initialize by default (because of the new CTL_DISABLE
519 option) to save memory. To re-enable it, remove the CTL_DISABLE
520 option from the kernel config file or set kern.cam.ctl.disable=0
521 in /boot/loader.conf.
524 The ctl device has been disabled in GENERIC for i386 and amd64.
525 This was done due to the extra memory being allocated at system
526 initialisation time by the ctl driver which was only used if
527 a CAM target device was created. This makes a FreeBSD system
528 unusable on 128MB or less of RAM.
531 A new compression method (lz4) has been merged to -HEAD. Please
532 refer to zpool-features(7) for more information.
534 Please refer to the "ZFS notes" section of this file for information
535 on upgrading boot ZFS pools.
538 A BSD-licensed patch(1) variant has been added and is installed
539 as bsdpatch, being the GNU version the default patch.
540 To inverse the logic and use the BSD-licensed one as default,
541 while having the GNU version installed as gnupatch, rebuild
542 and install world with the WITH_BSD_PATCH knob set.
545 Due to the use of the new -l option to install(1) during build
546 and install, you must take care not to directly set the INSTALL
547 make variable in your /etc/make.conf, /etc/src.conf, or on the
548 command line. If you wish to use the -C flag for all installs
549 you may be able to add INSTALL+=-C to /etc/make.conf or
553 The install(1) option -M has changed meaning and now takes an
554 argument that is a file or path to append logs to. In the
555 unlikely event that -M was the last option on the command line
556 and the command line contained at least two files and a target
557 directory the first file will have logs appended to it. The -M
558 option served little practical purpose in the last decade so its
559 use is expected to be extremely rare.
562 After switching to Clang as the default compiler some users of ZFS
563 on i386 systems started to experience stack overflow kernel panics.
564 Please consider using 'options KSTACK_PAGES=4' in such configurations.
567 GEOM_LABEL now mangles label names read from file system metadata.
568 Mangling affect labels containing spaces, non-printable characters,
569 '%' or '"'. Device names in /etc/fstab and other places may need to
573 By default, only the 10 most recent kernel dumps will be saved. To
574 restore the previous behaviour (no limit on the number of kernel dumps
575 stored in the dump directory) add the following line to /etc/rc.conf:
580 With the addition of auditdistd(8), a new auditdistd user is now
581 required during installworld. "mergemaster -p" can be used to
582 add the user prior to installworld, as documented in the handbook.
585 The sin6_scope_id member variable in struct sockaddr_in6 is now
586 filled by the kernel before passing the structure to the userland via
587 sysctl or routing socket. This means the KAME-specific embedded scope
588 id in sin6_addr.s6_addr[2] is always cleared in userland application.
589 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
590 __FreeBSD_version is bumped to 1000025.
593 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
594 This means that the world and kernel will be compiled with clang
595 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
596 and /usr/bin/cpp. To disable this behavior and revert to building
597 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
598 of current may need to bootstrap WITHOUT_CLANG first if the clang
599 build fails (its compatibility window doesn't extend to the 9 stable
603 The IPFIREWALL_FORWARD kernel option has been removed. Its
604 functionality now turned on by default.
607 The ZERO_COPY_SOCKET kernel option has been removed and
608 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
609 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
610 mechanism which is not safe and may result in kernel crashes.
611 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
612 driver supports disposeable external page sized mbuf storage.
613 Proper replacements for both zero-copy mechanisms are under
614 consideration and will eventually lead to complete removal
615 of the two kernel options.
618 The IPv4 network stack has been converted to network byte
619 order. The following modules need to be recompiled together
620 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
621 pf(4), ipfw(4), ng_ipfw(4), stf(4).
624 Support for non-MPSAFE filesystems was removed from VFS. The
625 VFS_VERSION was bumped, all filesystem modules shall be
629 All the non-MPSAFE filesystems have been disconnected from
630 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
631 portalfs, smbfs, xfs.
634 The interface cloning API and ABI has changed. The following
635 modules need to be recompiled together with kernel:
636 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
637 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
638 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
641 The sdhci driver was split in two parts: sdhci (generic SD Host
642 Controller logic) and sdhci_pci (actual hardware driver).
643 No kernel config modifications are required, but if you
644 load sdhc as a module you must switch to sdhci_pci instead.
647 Import the FUSE kernel and userland support into base system.
650 The GNU sort(1) program has been removed since the BSD-licensed
651 sort(1) has been the default for quite some time and no serious
652 problems have been reported. The corresponding WITH_GNU_SORT
656 The pfil(9) API/ABI for AF_INET family has been changed. Packet
657 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
661 The net80211(4) ABI has been changed to allow for improved driver
662 PS-POLL and power-save support. All wireless drivers need to be
663 recompiled to work with the new kernel.
666 The random(4) support for the VIA hardware random number
667 generator (`PADLOCK') is no longer enabled unconditionally.
668 Add the padlock_rng device in the custom kernel config if
669 needed. The GENERIC kernels on i386 and amd64 do include the
670 device, so the change only affects the custom kernel
674 The pf(4) packet filter ABI has been changed. pfctl(8) and
675 snmp_pf module need to be recompiled to work with new kernel.
678 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
679 to -HEAD. Pools that have empty_bpobj in active state can not be
680 imported read-write with ZFS implementations that do not support
681 this feature. For more information read the zpool-features(5)
685 The sparc64 ZFS loader has been changed to no longer try to auto-
686 detect ZFS providers based on diskN aliases but now requires these
687 to be explicitly listed in the OFW boot-device environment variable.
690 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
691 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
692 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
695 The following sysctls and tunables have been renamed for consistency
696 with other variables:
697 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
698 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
701 The sort utility has been replaced with BSD sort. For now, GNU sort
702 is also available as "gnusort" or the default can be set back to
703 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
704 installed as "bsdsort".
707 A new version of ZFS (pool version 5000) has been merged to -HEAD.
708 Starting with this version the old system of ZFS pool versioning
709 is superseded by "feature flags". This concept enables forward
710 compatibility against certain future changes in functionality of ZFS
711 pools. The first read-only compatible "feature flag" for ZFS pools
712 is named "com.delphix:async_destroy". For more information
713 read the new zpool-features(5) manual page.
714 Please refer to the "ZFS notes" section of this file for information
715 on upgrading boot ZFS pools.
718 The malloc(3) implementation embedded in libc now uses sources imported
719 as contrib/jemalloc. The most disruptive API change is to
720 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
721 delete it prior to installworld, and optionally re-create it using the
722 new format after rebooting. See malloc.conf(5) for details
723 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
727 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
728 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
729 now spelled mips. This is to aid compatibility with third-party
730 software that expects this naming scheme in uname(3). Little-endian
731 settings are unchanged. If you are updating a big-endian mips64 machine
732 from before this change, you may need to set MACHINE_ARCH=mips64 in
733 your environment before the new build system will recognize your machine.
736 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
740 Now unix domain sockets behave "as expected" on nullfs(5). Previously
741 nullfs(5) did not pass through all behaviours to the underlying layer,
742 as a result if we bound to a socket on the lower layer we could connect
743 only to the lower path; if we bound to the upper layer we could connect
744 only to the upper path. The new behavior is one can connect to both the
745 lower and the upper paths regardless what layer path one binds to.
748 The getifaddrs upgrade path broken with 20111215 has been restored.
749 If you have upgraded in between 20111215 and 20120209 you need to
750 recompile libc again with your kernel. You still need to recompile
751 world to be able to configure CARP but this restriction already
755 The set_rcvar() function has been removed from /etc/rc.subr. All
756 base and ports rc.d scripts have been updated, so if you have a
757 port installed with a script in /usr/local/etc/rc.d you can either
758 hand-edit the rcvar= line, or reinstall the port.
760 An easy way to handle the mass-update of /etc/rc.d:
761 rm /etc/rc.d/* && mergemaster -i
764 panic(9) now stops other CPUs in the SMP systems, disables interrupts
765 on the current CPU and prevents other threads from running.
766 This behavior can be reverted using the kern.stop_scheduler_on_panic
768 The new behavior can be incompatible with kern.sync_on_panic.
771 The carp(4) facility has been changed significantly. Configuration
772 of the CARP protocol via ifconfig(8) has changed, as well as format
773 of CARP events submitted to devd(8) has changed. See manual pages
774 for more information. The arpbalance feature of carp(4) is currently
775 not supported anymore.
777 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
778 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
779 need to be recompiled.
782 The acpi_wmi(4) status device /dev/wmistat has been renamed to
786 The option VFS_ALLOW_NONMPSAFE option has been added in order to
787 explicitely support non-MPSAFE filesystems.
788 It is on by default for all supported platform at this present
792 The broken amd(4) driver has been replaced with esp(4) in the amd64,
793 i386 and pc98 GENERIC kernel configuration files.
796 sysinstall has been removed
799 The stable/9 branch created in subversion. This corresponds to the
800 RELENG_9 branch in CVS.
803 This commit modifies vfs_register() so that it uses a hash
804 calculation to set vfc_typenum, which is enabled by default.
805 The first time a system is booted after this change, the
806 vfc_typenum values will change for all file systems. The
807 main effect of this is a change to the NFS server file handles
808 for file systems that use vfc_typenum in their fsid, such as ZFS.
809 It will, however, prevent vfc_typenum from changing when file
810 systems are loaded in a different order for subsequent reboots.
811 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
812 until you are ready to remount all NFS clients after a reboot.
815 Bump the shared library version numbers for libraries that
816 do not use symbol versioning, have changed the ABI compared
817 to stable/8 and which shared library version was not bumped.
818 Done as part of 9.0-RELEASE cycle.
821 During the merge of Capsicum features, the fget(9) KPI was modified.
822 This may require the rebuilding of out-of-tree device drivers --
823 issues have been reported specifically with the nVidia device driver.
824 __FreeBSD_version is bumped to 900041.
826 Also, there is a period between 20110811 and 20110814 where the
827 special devices /dev/{stdin,stdout,stderr} did not work correctly.
828 Building world from a kernel during that window may not work.
831 The packet filter (pf) code has been updated to OpenBSD 4.5.
832 You need to update userland tools to be in sync with kernel.
833 This update breaks backward compatibility with earlier pfsync(4)
834 versions. Care must be taken when updating redundant firewall setups.
837 The following sysctls and tunables are retired on x86 platforms:
839 machdep.hlt_logical_cpus
840 The following sysctl is retired:
841 machdep.hyperthreading_allowed
842 The sysctls were supposed to provide a way to dynamically offline and
843 online selected CPUs on x86 platforms, but the implementation has not
844 been reliable especially with SCHED_ULE scheduler.
845 machdep.hyperthreading_allowed tunable is still available to ignore
846 hyperthreading CPUs at OS level.
847 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
848 where X is an APIC ID of a CPU. Be advised, though, that disabling
849 CPUs in non-uniform fashion will result in non-uniform topology and
850 may lead to sub-optimal system performance with SCHED_ULE, which is
854 cpumask_t type is retired and cpuset_t is used in order to describe
858 Changes to ifconfig(8) for dynamic address family detection mandate
859 that you are running a kernel of 20110525 or later. Make sure to
860 follow the update procedure to boot a new kernel before installing
864 Support for sun4v architecture is officially dropped
867 Several KPI breaking changes have been committed to the mii(4) layer,
868 the PHY drivers and consequently some Ethernet drivers using mii(4).
869 This means that miibus.ko and the modules of the affected Ethernet
870 drivers need to be recompiled.
872 Note to kernel developers: Given that the OUI bit reversion problem
873 was fixed as part of these changes all mii(4) commits related to OUIs,
874 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
875 handling, no longer can be merged verbatim to stable/8 and previous
879 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
880 into their kernel configurations along with 'device pci'.
883 The default NFS client is now the new NFS client, so fstype "newnfs"
884 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
885 Although mounts via fstype "nfs" will usually work without userland
886 changes, it is recommended that the mount(8) and mount_nfs(8)
887 commands be rebuilt from sources and that a link to mount_nfs called
888 mount_oldnfs be created. The new client is compiled into the
889 kernel with "options NFSCL" and this is needed for diskless root
890 file systems. The GENERIC kernel configs have been changed to use
891 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
892 To use the regular/old client, you can "mount -t oldnfs ...". For
893 a diskless root file system, you must also include a line like:
895 vfs.root.mountfrom="oldnfs:"
897 in the boot/loader.conf on the root fs on the NFS server to make
898 a diskless root fs use the old client.
901 The GENERIC kernels for all architectures now default to the new
902 CAM-based ATA stack. It means that all legacy ATA drivers were
903 removed and replaced by respective CAM drivers. If you are using
904 ATA device names in /etc/fstab or other places, make sure to update
905 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
906 where 'Y's are the sequential numbers starting from zero for each type
907 in order of detection, unless configured otherwise with tunables,
908 see cam(4)). There will be symbolic links created in /dev/ to map
909 old adX devices to the respective adaY. They should provide basic
910 compatibility for file systems mounting in most cases, but they do
911 not support old user-level APIs and do not have respective providers
912 in GEOM. Consider using updated management tools with new device names.
914 It is possible to load devices ahci, ata, siis and mvs as modules,
915 but option ATA_CAM should remain in kernel configuration to make ata
916 module work as CAM driver supporting legacy ATA controllers. Device ata
917 still can be used in modular fashion (atacore + ...). Modules atadisk
918 and atapi* are not used and won't affect operation in ATA_CAM mode.
919 Note that to use CAM-based ATA kernel should include CAM devices
920 scbus, pass, da (or explicitly ada), cd and optionally others. All of
921 them are parts of the cam module.
923 ataraid(4) functionality is now supported by the RAID GEOM class.
924 To use it you can load geom_raid kernel module and use graid(8) tool
925 for management. Instead of /dev/arX device names, use /dev/raid/rX.
927 No kernel config options or code have been removed, so if a problem
928 arises, please report it and optionally revert to the old ATA stack.
929 In order to do it you can remove from the kernel config:
934 , and instead add back:
935 device atadisk # ATA disk drives
936 device ataraid # ATA RAID drives
937 device atapicd # ATAPI CDROM drives
938 device atapifd # ATAPI floppy drives
939 device atapist # ATAPI tape drives
942 The default NFS server has been changed to the new server, which
943 was referred to as the experimental server. If you need to switch
944 back to the old NFS server, you must now put the "-o" option on
945 both the mountd and nfsd commands. This can be done using the
946 mountd_flags and nfs_server_flags rc.conf variables until an
947 update to the rc scripts is committed, which is coming soon.
950 The GNU Objective-C runtime library (libobjc), and other Objective-C
951 related components have been removed from the base system. If you
952 require an Objective-C library, please use one of the available ports.
955 ath(4) has been split into bus- and device- modules. if_ath contains
956 the HAL, the TX rate control and the network device code. if_ath_pci
957 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
958 contains the AHB glue. Users need to load both if_ath_pci and if_ath
959 in order to use ath on everything else.
961 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
962 need to load if_ath and if_ath_pci for ath(4) operation.
965 As part of the replacement of sysinstall, the process of building
966 release media has changed significantly. For details, please re-read
967 release(7), which has been updated to reflect the new build process.
970 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
971 is the last available version under GPLv2. It brings a number of new
972 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
973 4.1 and SSE 4.2), better support for powerpc64, a number of new
974 directives, and lots of other small improvements. See the ChangeLog
975 file in contrib/binutils for the full details.
978 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
979 compliant, and will now use half of hash for authentication.
980 This will break interoperability with all stacks (including all
981 actual FreeBSD versions) who implement
982 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
984 The only workaround with such peers is to use another HMAC
985 algorithm for IPsec ("phase 2") authentication.
988 Remove the uio_yield prototype and symbol. This function has
989 been misnamed since it was introduced and should not be
990 globally exposed with this name. The equivalent functionality
991 is now available using kern_yield(curthread->td_user_pri).
992 The function remains undocumented.
995 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
996 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
997 for scalar sysctls is defined but disabled. Code that needs
998 UQUAD to pass the type checking that must compile on older
999 systems where the define is not present can check against
1000 __FreeBSD_version >= 900030.
1002 The system dialog(1) has been replaced with a new version previously
1003 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1004 with the previous version, but the libdialog associated with it has
1005 a largely incompatible API. As such, the original version of libdialog
1006 will be kept temporarily as libodialog, until its base system consumers
1007 are replaced or updated. Bump __FreeBSD_version to 900030.
1010 If you are trying to run make universe on a -stable system, and you get
1011 the following warning:
1012 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1013 unknown. config(8) likely too old."
1014 or something similar to it, then you must upgrade your -stable system
1015 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1016 stable/8) or build the config from the latest stable/8 branch and
1017 install it on your system.
1019 Prior to this date, building a current universe on 8-stable system from
1020 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1021 error in the first kernel build phase. A new config on those old
1022 systems will fix that problem for older versions of -current.
1025 The TCP stack has been modified to allow Khelp modules to interact with
1026 it via helper hook points and store per-connection data in the TCP
1027 control block. Bump __FreeBSD_version to 900029. User space tools that
1028 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1032 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1033 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1034 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1035 to take advantage of it instead of using custom implementations. This
1036 means that these drivers now no longer unconditionally advertise
1037 support for flow control but only do so if flow control is a selected
1038 media option. This was implemented in the generic support that way in
1039 order to allow flow control to be switched on and off via ifconfig(8)
1040 with the PHY specific default to typically off in order to protect
1041 from unwanted effects. Consequently, if you used flow control with
1042 one of the above mentioned drivers you now need to explicitly enable
1043 it, for example via:
1044 ifconfig bge0 media auto mediaopt flowcontrol
1046 Along with the above mentioned changes generic support for setting
1047 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1048 e1000phy(4) as well as ip1000phy(4) have been converted to take
1049 advantage of it. This means that these drivers now no longer take the
1050 link0 parameter for selecting master mode but the master media option
1051 has to be used instead, for example like in the following:
1052 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1054 Selection of master mode now is also available with all other PHY
1055 drivers supporting 1000baseT.
1058 The TCP stack has received a significant update to add support for
1059 modularised congestion control and generally improve the clarity of
1060 congestion control decisions. Bump __FreeBSD_version to 900025. User
1061 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1062 sockstat) need to be recompiled.
1065 The man(1) utility has been replaced by a new version that no longer
1066 uses /etc/manpath.config. Please consult man.conf(5) for how to
1067 migrate local entries to the new format.
1070 The copyright strings printed by login(1) and sshd(8) at the time of a
1071 new connection have been removed to follow other operating systems and
1075 A workaround for a fixed ld bug has been removed in kernel code,
1076 so make sure that your system ld is built from sources after
1077 revision 210245 from 2010-07-19 (r211583 if building head kernel
1078 on stable/8, r211584 for stable/7; both from 2010-08-21).
1079 A symptom of incorrect ld version is different addresses for
1080 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1083 The $ipv6_prefer variable in rc.conf(5) has been split into
1084 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1086 The $ip6addrctl_policy is a variable to choose a pre-defined
1087 address selection policy set by ip6addrctl(8). A value
1088 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1091 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1092 flag (see an entry of 20090926) is set on an interface with no
1093 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1094 security reason. If you want IPv6 link-local address on all
1095 interfaces by default, set this to "YES".
1097 The old ipv6_prefer="YES" is equivalent to
1098 ipv6_activate_all_interfaces="YES" and
1099 ip6addrctl_policy="ipv6_prefer".
1102 DTrace has grown support for userland tracing. Due to this, DTrace is
1103 now i386 and amd64 only.
1104 dtruss(1) is now installed by default on those systems and a new
1105 kernel module is needed for userland tracing: fasttrap.
1106 No changes to your kernel config file are necessary to enable
1107 userland tracing, but you might consider adding 'STRIP=' and
1108 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1109 to have informative userland stack traces in DTrace (ustack).
1112 The acpi_aiboost(4) driver has been removed in favor of the new
1113 aibs(4) driver. You should update your kernel configuration file.
1116 BSD grep has been imported to the base system and it is built by
1117 default. It is completely BSD licensed, highly GNU-compatible, uses
1118 less memory than its GNU counterpart and has a small codebase.
1119 However, it is slower than its GNU counterpart, which is mostly
1120 noticeable for larger searches, for smaller ones it is measurable
1121 but not significant. The reason is complex, the most important factor
1122 is that we lack a modern and efficient regex library and GNU
1123 overcomes this by optimizing the searches internally. Future work
1124 on improving the regex performance is planned, for the meantime,
1125 users that need better performance, can build GNU grep instead by
1126 setting the WITH_GNU_GREP knob.
1129 Due to the import of powerpc64 support, all existing powerpc kernel
1130 configuration files must be updated with a machine directive like this:
1131 machine powerpc powerpc
1133 In addition, an updated config(8) is required to build powerpc kernels
1137 A new version of ZFS (version 15) has been merged to -HEAD.
1138 This version uses a python library for the following subcommands:
1139 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1140 For full functionality of these commands the following port must
1141 be installed: sysutils/py-zfs
1144 'vm_page's are now hashed by physical address to an array of mutexes.
1145 Currently this is only used to serialize access to hold_count. Over
1146 time the page queue mutex will be peeled away. This changes the size
1147 of pmap on every architecture. And requires all callers of vm_page_hold
1148 and vm_page_unhold to be updated.
1151 WITH_CTF can now be specified in src.conf (not recommended, there
1152 are some problems with static executables), make.conf (would also
1153 affect ports which do not use GNU make and do not override the
1154 compile targets) or in the kernel config (via "makeoptions
1156 When WITH_CTF was specified there before this was silently ignored,
1157 so make sure that WITH_CTF is not used in places which could lead
1158 to unwanted behavior.
1161 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1162 to allow 32-bit compatibility on non-x86 platforms. All kernel
1163 configurations on amd64 and ia64 platforms using these options must
1164 be modified accordingly.
1167 The utmp user accounting database has been replaced with utmpx,
1168 the user accounting interface standardized by POSIX.
1169 Unfortunately the semantics of utmp and utmpx don't match,
1170 making it practically impossible to support both interfaces.
1171 The user accounting database is used by tools like finger(1),
1172 last(1), talk(1), w(1) and ac(8).
1174 All applications in the base system use utmpx. This means only
1175 local binaries (e.g. from the ports tree) may still use these
1176 utmp database files. These applications must be rebuilt to make
1179 After the system has been upgraded, it is safe to remove the old
1180 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1181 assuming their contents is of no importance anymore. Old wtmp
1182 databases can only be used by last(1) and ac(8) after they have
1183 been converted to the new format using wtmpcvt(1).
1186 Introduce the kernel thread "deadlock resolver" (which can be enabled
1187 via the DEADLKRES option, see NOTES for more details) and the
1188 sleepq_type() function for sleepqueues.
1191 The rc.firewall and rc.firewall6 were unified, and
1192 rc.firewall6 and rc.d/ip6fw were removed.
1193 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1194 variables are obsoleted. Instead, the following new rc
1195 variables are added to rc.d/ipfw:
1197 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1198 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1199 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1201 The meanings correspond to the relevant IPv4 variables.
1207 The default terminal emulation for syscons(4) has been changed
1208 from cons25 to xterm on all platforms except pc98. This means
1209 that the /etc/ttys file needs to be updated to ensure correct
1210 operation of applications on the console.
1212 The terminal emulation style can be toggled per window by using
1213 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1214 options can be used to change the compile-time default back to
1217 To prevent graphical artifacts, make sure the TERM environment
1218 variable is set to match the terminal emulation that is being
1219 performed by syscons(4).
1222 The layout of the structure ieee80211req_scan_result has changed.
1223 Applications that require wireless scan results (e.g. ifconfig(8))
1224 from net80211 need to be recompiled.
1226 Applications such as wpa_supplicant(8) may require a full world
1227 build without using NO_CLEAN in order to get synchronized with the
1231 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1232 There's one kernel module for each firmware. Adding "device iwnfw"
1233 to the kernel configuration file means including all three firmware
1234 images inside the kernel. If you want to include just the one for
1235 your wireless card, use the devices iwn4965fw, iwn5000fw or
1239 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1240 into rc.d/netif. The changes are the following:
1242 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1243 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1244 Note that both variables need the "inet6" keyword at the head.
1246 Do not set $ipv6_network_interfaces manually if you do not
1247 understand what you are doing. It is not needed in most cases.
1249 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1252 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1253 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1255 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1256 all configured interfaces have "inet6 accept_rtadv" in the
1257 $ifconfig_IF_ipv6. These are for backward compatibility.
1259 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1260 functionality of interfaces with no corresponding
1261 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1262 and the default address selection policy of ip6addrctl(8)
1263 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1264 Note that if you want to configure IPv6 functionality on the
1265 disabled interfaces after boot, first you need to clear the flag by
1266 using ifconfig(8) like:
1268 ifconfig em0 inet6 -ifdisabled
1270 If YES, the default address selection policy is set as
1273 The default value of $ipv6_prefer is NO.
1275 4. If your system need to receive Router Advertisement messages,
1276 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1277 scripts automatically invoke rtsol(8) when the interface becomes
1278 UP. The Router Advertisement messages are used for SLAAC
1279 (State-Less Address AutoConfiguration).
1282 802.11s D3.03 support was committed. This is incompatible with the
1283 previous code, which was based on D3.0.
1286 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1287 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1288 control whether accepting Router Advertisement messages or not.
1289 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1290 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1291 The ifconfig(8) utility now supports these flags.
1294 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1295 mount(8) and -a option for df(1) to see them.
1298 The old tunable hw.bus.devctl_disable has been superseded by
1299 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1300 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1304 Remove the option STOP_NMI. The default action is now to use NMI only
1305 for KDB via the newly introduced function stop_cpus_hard() and
1306 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1309 The stable/8 branch created in subversion. This corresponds to the
1310 RELENG_8 branch in CVS.
1313 Bump the shared library version numbers for all libraries that do not
1314 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1315 __FreeBSD_version to 800105.
1318 Due to changes in the implementation of virtual network stack support,
1319 all network-related kernel modules must be recompiled. As this change
1320 breaks the ABI, bump __FreeBSD_version to 800104.
1323 The TOE interface to the TCP syncache has been modified to remove
1324 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1325 The cxgb driver is the only TOE consumer affected by this change, and
1326 needs to be recompiled along with the kernel. As this change breaks
1327 the ABI, bump __FreeBSD_version to 800103.
1330 Padding has been added to struct tcpcb, sackhint and tcpstat in
1331 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1332 maintaining the ABI. However, this change breaks the ABI, so bump
1333 __FreeBSD_version to 800102. User space tools that rely on the size of
1334 any of these structs (e.g. sockstat) need to be recompiled.
1337 The NFS_LEGACYRPC option has been removed along with the old kernel
1338 RPC implementation that this option selected. Kernel configurations
1339 may need to be adjusted.
1342 The network interface device nodes at /dev/net/<interface> have been
1343 removed. All ioctl operations can be performed the normal way using
1344 routing sockets. The kqueue functionality can generally be replaced
1345 with routing sockets.
1348 The documentation from the FreeBSD Documentation Project (Handbook,
1349 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1350 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1353 The ABI of various structures related to the SYSV IPC API have been
1354 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1355 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1359 Layout of struct vnet has changed as routing related variables were
1360 moved to their own Vimage module. Modules need to be recompiled. Bump
1361 __FreeBSD_version to 800099.
1364 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1365 respectively. As long as no more than 16 groups per process are used,
1366 no changes should be visible. When more than 16 groups are used, old
1367 binaries may fail if they call getgroups() or getgrouplist() with
1368 statically sized storage. Recompiling will work around this, but
1369 applications should be modified to use dynamically allocated storage
1370 for group arrays as POSIX.1-2008 does not cap an implementation's
1371 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1373 NFS and portalfs mounts may also be affected as the list of groups is
1374 truncated to 16. Users of NFS who use more than 16 groups, should
1375 take care that negative group permissions are not used on the exported
1376 file systems as they will not be reliable unless a GSSAPI based
1377 authentication method is used.
1380 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1381 option compiles in the support for adaptive spinning for lockmgrs
1382 which want to enable it. The lockinit() function now accepts the flag
1383 LK_ADAPTIVE in order to make the lock object subject to adaptive
1384 spinning when both held in write and read mode.
1387 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1388 changed. User applications that use this ioctl need to be rebuilt.
1391 The layout of struct thread has changed. Kernel and modules need to
1395 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1396 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1399 window(1) has been removed from the base system. It can now be
1400 installed from ports. The port is called misc/window.
1403 The way we are storing and accessing `routing table' entries has
1404 changed. Programs reading the FIB, like netstat, need to be
1408 A new netisr implementation has been added for FreeBSD 8. Network
1409 file system modules, such as igmp, ipdivert, and others, should be
1411 Bump __FreeBSD_version to 800096.
1414 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1418 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1419 Bump __FreeBSD_version to 800094.
1422 Add mnt_xflag field to 'struct mount'. File system modules need to be
1424 Bump __FreeBSD_version to 800093.
1427 The compiling option ADAPTIVE_SX has been retired while it has been
1428 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1429 The KPI for sx_init_flags() changes as accepting flags:
1430 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1431 been introduced in order to handle the reversed logic.
1432 Bump __FreeBSD_version to 800092.
1435 Add support for hierarchical jails. Remove global securelevel.
1436 Bump __FreeBSD_version to 800091.
1439 The layout of struct vnet_net has changed, therefore modules
1441 Bump __FreeBSD_version to 800090.
1444 The newly imported zic(8) produces a new format in the output. Please
1445 run tzsetup(8) to install the newly created data to /etc/localtime.
1448 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1449 hw.usb.* and is now consistent again with previous releases.
1452 802.11 monitor mode support was revised and driver api's were changed.
1453 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1454 of DLT_IEEE802_11. No user-visible data structures were changed but
1455 applications that use DLT_IEEE802_11 may require changes.
1456 Bump __FreeBSD_version to 800088.
1459 The layout of the following structs has changed: sysctl_oid,
1460 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1461 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1462 panics may be experienced. World rebuild is required for
1463 correctly checking networking state from userland.
1464 Bump __FreeBSD_version to 800085.
1467 MLDv2 and Source-Specific Multicast (SSM) have been merged
1468 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1469 The implementation of SSM within FreeBSD's IPv6 stack closely
1470 follows the IPv4 implementation.
1472 For kernel developers:
1474 * The most important changes are that the ip6_output() and
1475 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1476 and this lock has been downgraded to a non-recursive mutex.
1478 * As with the changes to the IPv4 stack to support SSM, filtering
1479 of inbound multicast traffic must now be performed by transport
1480 protocols within the IPv6 stack. This does not apply to TCP and
1481 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1483 * The KPIs used by IPv6 multicast are similar to those used by
1484 the IPv4 stack, with the following differences:
1485 * im6o_mc_filter() is analogous to imo_multicast_filter().
1486 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1487 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1488 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1489 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1490 for MLDv1 have an additional 'timer' argument which is used to
1491 jitter the initial membership report for the solicited-node
1492 multicast membership on-link.
1493 * This is not strictly needed for MLDv2, which already jitters
1494 its report transmissions. However, the 'timer' argument is
1495 preserved in case MLDv1 is active on the interface.
1497 * The KAME linked-list based IPv6 membership implementation has
1498 been refactored to use a vector similar to that used by the IPv4
1500 Code which maintains a list of its own multicast memberships
1501 internally, e.g. carp, has been updated to reflect the new
1504 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1505 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1506 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1507 implementation constraint which needs to be addressed in HEAD.
1509 For application developers:
1511 * The changes are broadly similar to those made for the IPv4
1514 * The use of IPv4 and IPv6 multicast socket options on the same
1515 socket, using mapped addresses, HAS NOT been tested or supported.
1517 * There are a number of issues with the implementation of various
1518 IPv6 multicast APIs which need to be resolved in the API surface
1519 before the implementation is fully compatible with KAME userland
1520 use, and these are mostly to do with interface index treatment.
1522 * The literature available discusses the use of either the delta / ASM
1523 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1524 using setsourcefilter(3)/getsourcefilter(3). For more information
1525 please refer to RFC 3768, 'Socket Interface Extensions for
1526 Multicast Source Filters'.
1528 * Applications which use the published RFC 3678 APIs should be fine.
1530 For systems administrators:
1532 * The mtest(8) utility has been refactored to support IPv6, in
1533 addition to IPv4. Interface addresses are no longer accepted
1534 as arguments, their names must be used instead. The utility
1535 will map the interface name to its first IPv4 address as
1536 returned by getifaddrs(3).
1538 * The ifmcstat(8) utility has also been updated to print the MLDv2
1539 endpoint state and source filter lists via sysctl(3).
1541 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1542 loopback of IPv6 multicast datagrams by default; it defaults to 1
1543 to preserve the existing behaviour. Disabling multicast loopback is
1544 recommended for optimal system performance.
1546 * The IPv6 MROUTING code has been changed to examine this sysctl
1547 instead of attempting to perform a group lookup before looping
1548 back forwarded datagrams.
1550 Bump __FreeBSD_version to 800084.
1553 Implement low-level Bluetooth HCI API.
1554 Bump __FreeBSD_version to 800083.
1557 The layout of struct malloc_type, used by modules to register new
1558 memory allocation types, has changed. Most modules will need to
1559 be rebuilt or panics may be experienced.
1560 Bump __FreeBSD_version to 800081.
1563 Anticipate overflowing inp_flags - add inp_flags2.
1564 This changes most offsets in inpcb, so checking v4 connection
1565 state will require a world rebuild.
1566 Bump __FreeBSD_version to 800080.
1569 Add an llentry to struct route and struct route_in6. Modules
1570 embedding a struct route will need to be recompiled.
1571 Bump __FreeBSD_version to 800079.
1574 The size of rt_metrics_lite and by extension rtentry has changed.
1575 Networking administration apps will need to be recompiled.
1576 The route command now supports show as an alias for get, weighting
1577 of routes, sticky and nostick flags to alter the behavior of stateful
1579 Bump __FreeBSD_version to 800078.
1582 Do not use Giant for kbdmux(4) locking. This is wrong and
1583 apparently causing more problems than it solves. This will
1584 re-open the issue where interrupt handlers may race with
1585 kbdmux(4) in polling mode. Typical symptoms include (but
1586 not limited to) duplicated and/or missing characters when
1587 low level console functions (such as gets) are used while
1588 interrupts are enabled (for example geli password prompt,
1589 mountroot prompt etc.). Disabling kbdmux(4) may help.
1592 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1593 kernel modules referencing any of the above need to be recompiled.
1594 Bump __FreeBSD_version to 800075.
1597 GEOM_PART has become the default partition slicer for storage devices,
1598 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1599 introduces some changes:
1601 MSDOS/EBR: the devices created from MSDOS extended partition entries
1602 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1603 to devices with offset-based names. fstabs may need to be modified.
1605 BSD: the "geometry does not match label" warning is harmless in most
1606 cases but it points to problems in file system misalignment with
1607 disk geometry. The "c" partition is now implicit, covers the whole
1608 top-level drive and cannot be (mis)used by users.
1610 General: Kernel dumps are now not allowed to be written to devices
1611 whose partition types indicate they are meant to be used for file
1612 systems (or, in case of MSDOS partitions, as something else than
1615 Most of these changes date approximately from 200812.
1618 The uscanner(4) driver has been removed from the kernel. This follows
1619 Linux removing theirs in 2.6 and making libusb the default interface
1620 (supported by sane).
1623 The multicast forwarding code has been cleaned up. netstat(1)
1624 only relies on KVM now for printing bandwidth upcall meters.
1625 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1626 ip6_mroute_mod respectively. The config(5) options for statically
1627 compiling this code remain the same, i.e. 'options MROUTING'.
1630 Support for the IFF_NEEDSGIANT network interface flag has been
1631 removed, which means that non-MPSAFE network device drivers are no
1632 longer supported. In particular, if_ar, if_sr, and network device
1633 drivers from the old (legacy) USB stack can no longer be built or
1637 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1638 a bunch of new language catalog files have also been added.
1639 This means that some common libc messages are now localized and
1640 they depend on the LC_MESSAGES environmental variable.
1643 The k8temp(4) driver has been renamed to amdtemp(4) since
1644 support for Family 10 and Family 11 CPU families was added.
1647 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1648 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1650 For kernel developers, the most important changes are that the
1651 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1652 and this lock has been downgraded to a non-recursive mutex.
1654 Transport protocols (UDP, Raw IP) are now responsible for filtering
1655 inbound multicast traffic according to group membership and source
1656 filters. The imo_multicast_filter() KPI exists for this purpose.
1657 Transports which do not use multicast (SCTP, TCP) already reject
1658 multicast by default. Forwarding and receive performance may improve
1659 as a mutex acquisition is no longer needed in the ip_input()
1660 low-level input path. in_addmulti() and in_delmulti() are shimmed
1661 to new KPIs which exist to support SSM in-kernel.
1663 For application developers, it is recommended that loopback of
1664 multicast datagrams be disabled for best performance, as this
1665 will still cause the lock to be taken for each looped-back
1666 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1667 be tuned to 0 to disable loopback by default; it defaults to 1
1668 to preserve the existing behaviour.
1670 For systems administrators, to obtain best performance with
1671 multicast reception and multiple groups, it is always recommended
1672 that a card with a suitably precise hash filter is used. Hash
1673 collisions will still result in the lock being taken within the
1674 transport protocol input path to check group membership.
1676 If deploying FreeBSD in an environment with IGMP snooping switches,
1677 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1678 enabled; this forces 224.0.0.0/24 group membership to be announced
1681 The size of 'struct igmpstat' has changed; netstat needs to be
1682 recompiled to reflect this.
1683 Bump __FreeBSD_version to 800070.
1686 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1687 updated to use it. This requires a buildworld/installworld in order to
1688 update the library and dependencies (usbconfig, etc). Its advisable to
1689 rebuild all ports which uses libusb. More specific directions are given
1690 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1691 libusb are no longer required and can be removed.
1694 A workaround is committed to allow the creation of System V shared
1695 memory segment of size > 2 GB on the 64-bit architectures.
1696 Due to a limitation of the existing ABI, the shm_segsz member
1697 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1698 wrong for large segments. Note that limits must be explicitly
1699 raised to allow such segments to be created.
1702 The layout of struct ifnet has changed, requiring a rebuild of all
1703 network device driver modules.
1706 The /dev handling for the new USB stack has changed, a
1707 buildworld/installworld is required for libusb20.
1710 The new USB2 stack has now been permanently moved in and all kernel and
1711 module names reverted to their previous values (eg, usb, ehci, ohci,
1712 ums, ...). The old usb stack can be compiled in by prefixing the name
1713 with the letter 'o', the old usb modules have been removed.
1714 Updating entry 20090216 for xorg and 20090215 for libmap may still
1718 The rc.conf(5) option if_up_delay has been renamed to
1719 defaultroute_delay to better reflect its purpose. If you have
1720 customized this setting in /etc/rc.conf you need to update it to
1724 xorg 7.4 wants to configure its input devices via hald which does not
1725 yet work with USB2. If the keyboard/mouse does not work in xorg then
1727 Option "AllowEmptyInput" "off"
1728 to your ServerLayout section. This will cause X to use the configured
1729 kbd and mouse sections from your xorg.conf.
1732 The GENERIC kernels for all architectures now default to the new USB2
1733 stack. No kernel config options or code have been removed so if a
1734 problem arises please report it and optionally revert to the old USB
1735 stack. If you are loading USB kernel modules or have a custom kernel
1736 that includes GENERIC then ensure that usb names are also changed over,
1737 eg uftdi -> usb2_serial_ftdi.
1739 Older programs linked against the ports libusb 0.1 need to be
1740 redirected to the new stack's libusb20. /etc/libmap.conf can
1742 # Map old usb library to new one for usb2 stack
1743 libusb-0.1.so.8 libusb20.so.1
1746 All USB ethernet devices now attach as interfaces under the name ueN
1747 (eg. ue0). This is to provide a predictable name as vendors often
1748 change usb chipsets in a product without notice.
1751 The ichsmb(4) driver has been changed to require SMBus slave
1752 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1753 All of the other SMBus controller drivers require left-justified
1754 slave addresses, so this change makes all the drivers provide the
1758 INET6 statistics (struct ip6stat) was updated.
1759 netstat(1) needs to be recompiled.
1762 NTFS has been removed from GENERIC kernel on amd64 to match
1763 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1764 will load ntfs.ko module automatically when NTFS support is
1765 actually needed, unless ntfs.ko is not installed or security
1766 level prohibits loading kernel modules. If either is the case,
1767 "options NTFS" has to be added into kernel config.
1770 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1771 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1772 800061. User space tools that rely on the size of struct tcpcb in
1773 tcp_var.h (e.g. sockstat) need to be recompiled.
1776 ng_tty(4) module updated to match the new TTY subsystem.
1777 Due to API change, user-level applications must be updated.
1778 New API support added to mpd5 CVS and expected to be present
1779 in next mpd5.3 release.
1782 With __FreeBSD_version 800060 the makefs tool is part of
1783 the base system (it was a port).
1786 The afdata and ifnet locks have been changed from mutexes to
1787 rwlocks, network modules will need to be re-compiled.
1790 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1791 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1792 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1793 architecture and 40 bytes on 64-bit architecture. The userland
1794 applications "arp" and "ndp" have been updated accordingly.
1795 The output from "netstat -r" shows only routing entries and
1796 none of the L2 information.
1799 __FreeBSD_version 800057 marks the switchover from the
1800 binary ath hal to source code. Users must add the line:
1802 options AH_SUPPORT_AR5416
1804 to their kernel config files when specifying:
1808 The ath_hal module no longer exists; the code is now compiled
1809 together with the driver in the ath module. It is now
1810 possible to tailor chip support (i.e. reduce the set of chips
1811 and thereby the code size); consult ath_hal(4) for details.
1814 __FreeBSD_version 800054 adds memory barriers to
1815 <machine/atomic.h>, new interfaces to ifnet to facilitate
1816 multiple hardware transmit queues for cards that support
1817 them, and a lock-less ring-buffer implementation to
1818 enable drivers to more efficiently manage queueing of
1822 A new version of ZFS (version 13) has been merged to -HEAD.
1823 This version has zpool attribute "listsnapshots" off by
1824 default, which means "zfs list" does not show snapshots,
1825 and is the same as Solaris behavior.
1828 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1831 The uhci, ohci, ehci and slhci USB Host controller drivers have
1832 been put into separate modules. If you load the usb module
1833 separately through loader.conf you will need to load the
1834 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1835 controller add the following to loader.conf:
1841 The ABI used by the PMC toolset has changed. Please keep
1842 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1846 atapci kernel module now includes only generic PCI ATA
1847 driver. AHCI driver moved to ataahci kernel module.
1848 All vendor-specific code moved into separate kernel modules:
1849 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1850 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1851 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1852 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1855 The TTY subsystem of the kernel has been replaced by a new
1856 implementation, which provides better scalability and an
1857 improved driver model. Most common drivers have been migrated to
1858 the new TTY subsystem, while others have not. The following
1859 drivers have not yet been ported to the new TTY layer:
1862 cy, digi, rc, rp, sio
1868 ng_h4, ng_tty, ppp, sl, snp
1870 Adding these drivers to your kernel configuration file shall
1871 cause compilation to fail.
1874 ntpd has been upgraded to 4.2.4p5.
1877 OpenSSH has been upgraded to 5.1p1.
1879 For many years, FreeBSD's version of OpenSSH preferred DSA
1880 over RSA for host and user authentication keys. With this
1881 upgrade, we've switched to the vendor's default of RSA over
1882 DSA. This may cause upgraded clients to warn about unknown
1883 host keys even for previously known hosts. Users should
1884 follow the usual procedure for verifying host keys before
1885 accepting the RSA key.
1887 This can be circumvented by setting the "HostKeyAlgorithms"
1888 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1891 Please note that the sequence of keys offered for
1892 authentication has been changed as well. You may want to
1893 specify IdentityFile in a different order to revert this
1897 The sio(4) driver has been removed from the i386 and amd64
1898 kernel configuration files. This means uart(4) is now the
1899 default serial port driver on those platforms as well.
1901 To prevent collisions with the sio(4) driver, the uart(4) driver
1902 uses different names for its device nodes. This means the
1903 onboard serial port will now most likely be called "ttyu0"
1904 instead of "ttyd0". You may need to reconfigure applications to
1905 use the new device names.
1907 When using the serial port as a boot console, be sure to update
1908 /boot/device.hints and /etc/ttys before booting the new kernel.
1909 If you forget to do so, you can still manually specify the hints
1910 at the loader prompt:
1912 set hint.uart.0.at="isa"
1913 set hint.uart.0.port="0x3F8"
1914 set hint.uart.0.flags="0x10"
1915 set hint.uart.0.irq="4"
1919 The gpt(8) utility has been removed. Use gpart(8) to partition
1923 The version that Linuxulator emulates was changed from 2.4.2
1924 to 2.6.16. If you experience any problems with Linux binaries
1925 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1926 if it fixes the problem contact emulation mailing list.
1929 ISDN4BSD (I4B) was removed from the src tree. You may need to
1930 update a your kernel configuration and remove relevant entries.
1933 I have checked in code to support multiple routing tables.
1934 See the man pages setfib(1) and setfib(2).
1935 This is a hopefully backwards compatible version,
1936 but to make use of it you need to compile your kernel
1937 with options ROUTETABLES=2 (or more up to 16).
1940 The 802.11 wireless support was redone to enable multi-bss
1941 operation on devices that are capable. The underlying device
1942 is no longer used directly but instead wlanX devices are
1943 cloned with ifconfig. This requires changes to rc.conf files.
1944 For example, change:
1945 ifconfig_ath0="WPA DHCP"
1948 ifconfig_wlan0="WPA DHCP"
1949 see rc.conf(5) for more details. In addition, mergemaster of
1950 /etc/rc.d is highly recommended. Simultaneous update of userland
1951 and kernel wouldn't hurt either.
1953 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1954 modules were merged into the base wlan module. All references
1955 to these modules (e.g. in kernel config files) must be removed.
1958 psm(4) has gained write(2) support in native operation level.
1959 Arbitrary commands can be written to /dev/psm%d and status can
1960 be read back from it. Therefore, an application is responsible
1961 for status validation and error recovery. It is a no-op in
1962 other operation levels.
1965 Support for KSE threading has been removed from the kernel. To
1966 run legacy applications linked against KSE libmap.conf may
1967 be used. The following libmap.conf may be used to ensure
1968 compatibility with any prior release:
1970 libpthread.so.1 libthr.so.1
1971 libpthread.so.2 libthr.so.2
1972 libkse.so.3 libthr.so.3
1975 The layout of struct vmspace has changed. This affects libkvm
1976 and any executables that link against libkvm and use the
1977 kvm_getprocs() function. In particular, but not exclusively,
1978 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1979 The effects are minimal, but it's advisable to upgrade world
1983 The latest em driver no longer has support in it for the
1984 82575 adapter, this is now moved to the igb driver. The
1985 split was done to make new features that are incompatible
1986 with older hardware easier to do.
1989 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1990 likewise the kernel option is now GEOM_LINUX_LVM.
1993 The default NFS mount mode has changed from UDP to TCP for
1994 increased reliability. If you rely on (insecurely) NFS
1995 mounting across a firewall you may need to update your
1999 Belatedly note the addition of m_collapse for compacting
2003 The fts(3) structures have been changed to use adequate
2004 integer types for their members and so to be able to cope
2005 with huge file trees. The old fts(3) ABI is preserved
2006 through symbol versioning in libc, so third-party binaries
2007 using fts(3) should still work, although they will not take
2008 advantage of the extended types. At the same time, some
2009 third-party software might fail to build after this change
2010 due to unportable assumptions made in its source code about
2011 fts(3) structure members. Such software should be fixed
2012 by its vendor or, in the worst case, in the ports tree.
2013 FreeBSD_version 800015 marks this change for the unlikely
2014 case that a portable fix is impossible.
2017 To upgrade to -current after this date, you must be running
2018 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2019 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2022 The ADAPTIVE_GIANT kernel option has been retired because its
2023 functionality is the default now.
2026 The AT keyboard emulation of sunkbd(4) has been turned on
2027 by default. In order to make the special symbols of the Sun
2028 keyboards driven by sunkbd(4) work under X these now have
2029 to be configured the same way as Sun USB keyboards driven
2030 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2032 Option "XkbLayout" "us"
2033 Option "XkbRules" "xorg"
2034 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2037 It has been decided that it is desirable to provide ABI
2038 backwards compatibility to the FreeBSD 4/5/6 versions of the
2039 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2040 broken with the introduction of PCI domain support (see the
2041 20070930 entry). Unfortunately, this required the ABI of
2042 PCIOCGETCONF to be broken again in order to be able to
2043 provide backwards compatibility to the old version of that
2044 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2045 again. As for prominent ports this affects neither pciutils
2046 nor xorg-server this time, the hal port needs to be rebuilt
2050 The misnamed kthread_create() and friends have been renamed
2051 to kproc_create() etc. Many of the callers already
2052 used kproc_start()..
2053 I will return kthread_create() and friends in a while
2054 with implementations that actually create threads, not procs.
2055 Renaming corresponds with version 800002.
2064 Avoid using make -j when upgrading. While generally safe, there are
2065 sometimes problems using -j to upgrade. If your upgrade fails with
2066 -j, please try again without -j. From time to time in the past there
2067 have been problems using -j with buildworld and/or installworld. This
2068 is especially true when upgrading between "distant" versions (eg one
2069 that cross a major release boundary or several minor releases, or when
2070 several months have passed on the -current branch).
2072 Sometimes, obscure build problems are the result of environment
2073 poisoning. This can happen because the make utility reads its
2074 environment when searching for values for global variables. To run
2075 your build attempts in an "environmental clean room", prefix all make
2076 commands with 'env -i '. See the env(1) manual page for more details.
2078 When upgrading from one major version to another it is generally best
2079 to upgrade to the latest code in the currently installed branch first,
2080 then do an upgrade to the new branch. This is the best-tested upgrade
2081 path, and has the highest probability of being successful. Please try
2082 this approach before reporting problems with a major version upgrade.
2084 When upgrading a live system, having a root shell around before
2085 installing anything can help undo problems. Not having a root shell
2086 around can lead to problems if pam has changed too much from your
2087 starting point to allow continued authentication after the upgrade.
2091 When upgrading the boot ZFS pool to a new version, always follow
2094 1.) recompile and reinstall the ZFS boot loader and boot block
2095 (this is part of "make buildworld" and "make installworld")
2097 2.) update the ZFS boot block on your boot drive
2099 The following example updates the ZFS boot block on the first
2100 partition (freebsd-boot) of a GPT partitioned drive ad0:
2101 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2103 Non-boot pools do not need these updates.
2107 If you are updating from a prior version of FreeBSD (even one just
2108 a few days old), you should follow this procedure. It is the most
2109 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2111 make kernel-toolchain
2112 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2113 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2115 To test a kernel once
2116 ---------------------
2117 If you just want to boot a kernel once (because you are not sure
2118 if it works, or if you want to boot a known bad kernel to provide
2119 debugging information) run
2120 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2121 nextboot -k testkernel
2123 To just build a kernel when you know that it won't mess you up
2124 --------------------------------------------------------------
2125 This assumes you are already running a CURRENT system. Replace
2126 ${arch} with the architecture of your machine (e.g. "i386",
2127 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2129 cd src/sys/${arch}/conf
2130 config KERNEL_NAME_HERE
2131 cd ../compile/KERNEL_NAME_HERE
2136 If this fails, go to the "To build a kernel" section.
2138 To rebuild everything and install it on the current system.
2139 -----------------------------------------------------------
2140 # Note: sometimes if you are running current you gotta do more than
2141 # is listed here if you are upgrading from a really old current.
2143 <make sure you have good level 0 dumps>
2145 make kernel KERNCONF=YOUR_KERNEL_HERE
2147 <reboot in single user> [3]
2154 To cross-install current onto a separate partition
2155 --------------------------------------------------
2156 # In this approach we use a separate partition to hold
2157 # current's root, 'usr', and 'var' directories. A partition
2158 # holding "/", "/usr" and "/var" should be about 2GB in
2161 <make sure you have good level 0 dumps>
2164 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2165 <maybe newfs current's root partition>
2166 <mount current's root partition on directory ${CURRENT_ROOT}>
2167 make installworld DESTDIR=${CURRENT_ROOT}
2168 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2169 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2170 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2171 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2172 <reboot into current>
2173 <do a "native" rebuild/install as described in the previous section>
2174 <maybe install compatibility libraries from ports/misc/compat*>
2178 To upgrade in-place from stable to current
2179 ----------------------------------------------
2180 <make sure you have good level 0 dumps>
2182 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2184 <reboot in single user> [3]
2191 Make sure that you've read the UPDATING file to understand the
2192 tweaks to various things you need. At this point in the life
2193 cycle of current, things change often and you are on your own
2194 to cope. The defaults can also change, so please read ALL of
2195 the UPDATING entries.
2197 Also, if you are tracking -current, you must be subscribed to
2198 freebsd-current@freebsd.org. Make sure that before you update
2199 your sources that you have read and understood all the recent
2200 messages there. If in doubt, please track -stable which has
2201 much fewer pitfalls.
2203 [1] If you have third party modules, such as vmware, you
2204 should disable them at this point so they don't crash your
2207 [3] From the bootblocks, boot -s, and then do
2212 adjkerntz -i # if CMOS is wall time
2213 Also, when doing a major release upgrade, it is required that
2214 you boot into single user mode to do the installworld.
2216 [4] Note: This step is non-optional. Failure to do this step
2217 can result in a significant reduction in the functionality of the
2218 system. Attempting to do it by hand is not recommended and those
2219 that pursue this avenue should read this file carefully, as well
2220 as the archives of freebsd-current and freebsd-hackers mailing lists
2221 for potential gotchas. The -U option is also useful to consider.
2222 See mergemaster(8) for more information.
2224 [5] Usually this step is a noop. However, from time to time
2225 you may need to do this if you get unknown user in the following
2226 step. It never hurts to do it all the time. You may need to
2227 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2228 install) after the buildworld before this step if you last updated
2229 from current before 20130425 or from -stable before 20130430.
2231 [6] This only deletes old files and directories. Old libraries
2232 can be deleted by "make delete-old-libs", but you have to make
2233 sure that no program is using those libraries anymore.
2235 [8] In order to have a kernel that can run the 4.x binaries needed to
2236 do an installworld, you must include the COMPAT_FREEBSD4 option in
2237 your kernel. Failure to do so may leave you with a system that is
2238 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2239 required to run the 5.x binaries on more recent kernels. And so on
2240 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2242 Make sure that you merge any new devices from GENERIC since the
2243 last time you updated your kernel config file.
2245 [9] When checking out sources, you must include the -P flag to have
2246 cvs prune empty directories.
2248 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2249 "?=" instead of the "=" assignment operator, so that buildworld can
2250 override the CPUTYPE if it needs to.
2252 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2253 not on the command line, or in /etc/make.conf. buildworld will
2254 warn if it is improperly defined.
2257 This file contains a list, in reverse chronological order, of major
2258 breakages in tracking -current. It is not guaranteed to be a complete
2259 list of such breakages, and only contains entries since October 10, 2007.
2260 If you need to see UPDATING entries from before that date, you will need
2261 to fetch an UPDATING file from an older FreeBSD release.
2263 Copyright information:
2265 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2267 Redistribution, publication, translation and use, with or without
2268 modification, in full or in part, in any form or format of this
2269 document are permitted without further permission from the author.
2271 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2272 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2273 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2274 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2275 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2276 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2277 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2278 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2279 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2280 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2281 POSSIBILITY OF SUCH DAMAGE.
2283 Contact Warner Losh if you have any questions about your use of