1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4 See end of file for further details. For commonly done items, please see the
5 COMMON ITEMS: section later in the file. These instructions assume that you
6 basically know what you are doing. If not, then please consult the FreeBSD
9 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
11 Items affecting the ports and packages system can be found in
12 /usr/ports/UPDATING. Please read that file before running portupgrade.
14 NOTE: FreeBSD has switched from gcc to clang. If you have trouble bootstrapping
15 from older versions of FreeBSD, try WITHOUT_CLANG to bootstrap to the tip of
16 stable/10, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 20160316 p14 FreeBSD-SA-16:14.openssh-xauth
20 FreeBSD-SA-16:15.sysarch
21 FreeBSD-EN-16:04.hyperv
22 FreeBSD-EN-16:05.hv_netvsc
24 Fix OpenSSH xauth(1) command injection. [SA-16:14]
25 Fix incorrect argument validation in sysarch(2). [SA-16:15]
26 Fix Hyper-V KVP (Key-Value Pair) daemon indefinite sleep. [EN-16:04]
27 Fix hv_netvsc(4) incorrect TCP/IP checksums. [EN-16:05]
29 20160303 p13 FreeBSD-SA-16:12.openssl
31 Fix multiple vulnerabilities of OpenSSL.
33 20160130 p12 FreeBSD-SA-16:11.openssl
35 Fix OpenSSL SSLv2 ciphersuite downgrade vulnerability. [SA-16:11]
37 20160127 p11 FreeBSD-SA-16:09.ntp
38 FreeBSD-SA-16:10.linux
40 Fix multiple vulnerabilities of ntp. [SA-16:09]
42 Fix Linux compatibility layer issetugid(2) system call
43 vulnerability. [SA-16:10]
45 20160114 p10 FreeBSD-SA-16:07.openssh
47 Fix OpenSSH client information leak. [SA-16:07]
49 20160114 p9 FreeBSD-EN-16:01.filemon
51 FreeBSD-EN-16:03.yplib
54 FreeBSD-SA-16:03.linux
55 FreeBSD-SA-16:04.linux
57 FreeBSD-SA-16:06.bsnmpd
59 Fix multiple stability and locking problems in filemon(4). [EN-16:01]
60 Fix pf(4) generating bad TCP checksums. [EN-16:02]
61 Fix infinite loop in YP/NIS client library. [EN-16:03]
62 Fix remote denial of service in SCTP. [SA-16:01]
63 Update NTP to 4.2.8p5. [SA-16:02]
64 Fix kernel memory diclosure in Linux compatibility layer. [SA-16:03]
65 Fix kernel memory overwrite in Linux compatibility layer. [SA-16:04]
66 Fix crash in TCP MD5 signatures. [SA-16:05]
67 Fix insecure default permissions for snmpd.config. [SA-16:06]
69 20151205 p8 FreeBSD-SA-15:26.openssl
71 Fix multiple OpenSSL vulnerabilities. [SA-15:26]
73 20151104 p7 FreeBSD-SA-15:25.ntp [revised]
74 FreeBSD-EN-15:19.kqueue
77 Fix regression in ntpd(8) lacking support for RAWDCF reference
78 clock in 10.2-RELEASE-p6. [SA-15:25]
80 Fix kqueue write events never fired for files greater 2GB. [EN-15:19]
82 Fix applications exiting due to segmentation violation on a correct
83 memory address. [EN-15:20.vm]
85 20151026: p6 FreeBSD-SA-15:25.ntp
87 Fix multiple NTP vulnerabilities. New NTP version is 4.2.8p4.
89 20151002: p5 FreeBSD-SA-15:24.rpcbind [revised]
90 Revised patch to address a regression that prevents NIS from working.
92 20150929: p4 FreeBSD-SA-15:24.rpcbind
94 Fix rpcbind(8) remote denial of service. [SA-15:24]
96 20150916: p3 FreeBSD-EN-15:16.pw
100 Fix regression in pw(8) when creating numeric users or groups.
103 Fix libc handling of signals for multi-threaded processes.
106 Implement pubkey support for pkg(7) bootstrap. [EN-15:18]
108 20150825: p2 FreeBSD-SA-15:22.openssh
110 Fix OpenSSH multiple vulnerabilities. [SA-15:22]
112 Fix insufficient check of unsupported pkg(7) signature methods.
115 20150818: p1 FreeBSD-SA-15:20.expat
116 FreeBSD-EN-15:11.toolchain
117 FreeBSD-EN-15:12.netstat
118 FreeBSD-EN-15:13.vidcontrol
120 Fix multiple integer overflows in expat (libbsdxml) XML parser.
123 Fix make(1) syntax errors when upgrading from 9.x and earlier.
126 Fix incorrect netstat(1) data handling on 32-bit systems.
129 Allow size argument to vidcontrol(1) for syscons(4). [EN-15:13]
135 The default Unbound configuration now enables remote control
136 using a local socket. Users who have already enabled the
137 local_unbound service should regenerate their configuration
138 by running "service local_unbound setup" as root.
141 An additional fix for the issue described in the 20150614 sendmail
142 entry below has been been committed in revision 284786.
145 The fix for the issue described in the 20150614 sendmail entry
146 below has been been committed in revision 284485. The work
147 around described in that entry is no longer needed unless the
148 default setting is overridden by a confDH_PARAMETERS configuration
149 setting of '5' or pointing to a 512 bit DH parameter file.
152 The import of openssl to address the FreeBSD-SA-15:10.openssl
153 security advisory includes a change which rejects handshakes
154 with DH parameters below 768 bits. sendmail releases prior
155 to 8.15.2 (not yet released), defaulted to a 512 bit
156 DH parameter setting for client connections. To work around
157 this interoperability, sendmail can be configured to use a
158 2048 bit DH parameter by:
160 1. Edit /etc/mail/`hostname`.mc
161 2. If a setting for confDH_PARAMETERS does not exist or
162 exists and is set to a string beginning with '5',
164 3. If a setting for confDH_PARAMETERS exists and is set to
165 a file path, create a new file with:
166 openssl dhparam -out /path/to/file 2048
167 4. Rebuild the .cf file:
168 cd /etc/mail/; make; make install
170 cd /etc/mail/; make restart
172 A sendmail patch is coming, at which time this file will be
176 chmod, chflags, chown and chgrp now affect symlinks in -R mode as
177 defined in symlink(7); previously symlinks were silently ignored.
180 The const qualifier has been removed from iconv(3) to comply with
181 POSIX. The ports tree is aware of this from r384038 onwards.
184 At svn r275807, The default linux compat kernel ABI has been adjusted
185 to 2.6.18 in support of the linux-c6 compat ports infrastructure
186 update. If you wish to continue using the linux-f10 compat ports,
187 add compat.linux.osrelease=2.6.16 to your local sysctl.conf. Users are
188 encouraged to update their linux-compat packages to linux-c6 during
189 their next update cycle.
191 See ports/UPDATING 20141209 and 20141215 on migration to CentOS 6 ports.
194 pjdfstest has been integrated into kyua as an opt-in test suite.
195 Please see share/doc/pjdfstest/README for a more details on how to
202 The ofwfb driver, used to provide a graphics console on PowerPC when
203 using vt(4), no longer allows mmap() of all of physical memory. This
204 will prevent Xorg on PowerPC with some ATI graphics cards from
205 initializing properly unless x11-servers/xorg-server is updated to
209 The libatf-c and libatf-c++ major versions were downgraded to 0 and
210 1 respectively to match the upstream numbers. They were out of
211 sync because, when they were originally added to FreeBSD, the
212 upstream versions were not respected. These libraries are private
213 and not yet built by default, so renumbering them should be a
214 non-issue. However, unclean source trees will yield broken test
215 programs once the operator executes "make delete-old-libs" after a
218 Additionally, the atf-sh binary was made private by moving it into
219 /usr/libexec/. Already-built shell test programs will keep the
220 path to the old binary so they will break after "make delete-old"
223 If you are using WITH_TESTS=yes (not the default), wipe the object
224 tree and rebuild from scratch to prevent spurious test failures.
225 This is only needed once: the misnumbered libraries and misplaced
226 binaries have been added to OptionalObsoleteFiles.inc so they will
227 be removed during a clean upgrade.
230 The ixgbe tunables now match their sysctl counterparts, for example:
231 hw.ixgbe.enable_aim => hw.ix.enable_aim
232 Anyone using ixgbe tunables should ensure they update /boot/loader.conf.
235 The NFSv4.1 server committed by r269398 changes the internal
236 function call interfaces used between the NFS and krpc modules.
237 As such, __FreeBSD_version was bumped.
240 The default unbound configuration has been modified to address
241 issues with reverse lookups on networks that use private
242 address ranges. If you use the local_unbound service, run
243 "service local_unbound setup" as root to regenerate your
244 configuration, then "service local_unbound reload" to load the
248 It is no longer necessary to include the dwarf version in your DEBUG
249 options in your kernel config file. The bug that required it to be
250 placed in the config file has bene fixed. DEBUG should now just
251 contain -g. The build system will automatically update things
252 to do the right thing.
255 Several ABI breaking changes were merged to CTL and new iSCSI code.
256 All CTL and iSCSI-related tools, such as ctladm, ctld, iscsid and
257 iscsictl need to be rebuilt to work with a new kernel.
260 The WITHOUT_VT_SUPPORT kernel config knob has been renamed
261 WITHOUT_VT. (The other _SUPPORT knobs have a consistent meaning
262 which differs from the behaviour controlled by this knob.)
265 On i386 and amd64 systems, the onifconsole flag is now set by default
266 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
267 as a login TTY if it is set in the bootloader as an active kernel
268 console. No changes in behavior should result otherwise. To revert to
269 the previous behavior, set ttyu0 to "off" in /etc/ttys.
272 Clang and llvm have been upgraded to 3.4.1 release.
275 Clang and llvm have been upgraded to 3.4 release.
278 If a Makefile in a tests/ directory was auto-generating a Kyuafile
279 instead of providing an explicit one, this would prevent such
280 Makefile from providing its own Kyuafile in the future during
281 NO_CLEAN builds. This has been fixed in the Makefiles but manual
282 intervention is needed to clean an objdir if you use NO_CLEAN:
283 # find /usr/obj -name Kyuafile | xargs rm -f
286 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
287 capability mode support. Please note that enabling the feature in
288 kernel is still highly recommended.
291 OpenSSH is now built with sandbox support, and will use sandbox as
292 the default privilege separation method. This requires Capsicum
293 capability mode support in kernel.
296 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
297 been deprecated and will not be part of FreeBSD 11.0 and later
298 releases. If you use this driver, please consider switching to
299 the nfe(4) driver instead.
305 The behavior of gss_pseudo_random() for the krb5 mechanism
306 has changed, for applications requesting a longer random string
307 than produced by the underlying enctype's pseudo-random() function.
308 In particular, the random string produced from a session key of
309 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
310 be different at the 17th octet and later, after this change.
311 The counter used in the PRF+ construction is now encoded as a
312 big-endian integer in accordance with RFC 4402.
313 __FreeBSD_version is bumped to 1000701.
316 The WITHOUT_ATF build knob has been removed and its functionality
317 has been subsumed into the more generic WITHOUT_TESTS. If you were
318 using the former to disable the build of the ATF libraries, you
319 should change your settings to use the latter.
322 The default version of mtree is nmtree which is obtained from
323 NetBSD. The output is generally the same, but may vary
324 slightly. If you found you need identical output adding
325 "-F freebsd9" to the command line should do the trick. For the
326 time being, the old mtree is available as fmtree.
329 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
330 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
331 1.1.4_8 and verify bsdyml not linked in, before running "make
333 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
335 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
338 The rc.d/jail script has been updated to support jail(8)
339 configuration file. The "jail_<jname>_*" rc.conf(5) variables
340 for per-jail configuration are automatically converted to
341 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
342 This is transparently backward compatible. See below about some
343 incompatibilities and rc.conf(5) manual page for more details.
345 These variables are now deprecated in favor of jail(8) configuration
346 file. One can use "rc.d/jail config <jname>" command to generate
347 a jail(8) configuration file in /var/run/jail.<jname>.conf without
348 running the jail(8) utility. The default pathname of the
349 configuration file is /etc/jail.conf and can be specified by
350 using $jail_conf or $jail_<jname>_conf variables.
352 Please note that jail_devfs_ruleset accepts an integer at
353 this moment. Please consider to rewrite the ruleset name
357 BIND has been removed from the base system. If all you need
358 is a local resolver, simply enable and start the local_unbound
359 service instead. Otherwise, several versions of BIND are
360 available in the ports tree. The dns/bind99 port is one example.
362 With this change, nslookup(1) and dig(1) are no longer in the base
363 system. Users should instead use host(1) and drill(1) which are
364 in the base system. Alternatively, nslookup and dig can
365 be obtained by installing the dns/bind-tools port.
368 With the addition of unbound(8), a new unbound user is now
369 required during installworld. "mergemaster -p" can be used to
370 add the user prior to installworld, as documented in the handbook.
373 OpenSSH is now built with DNSSEC support, and will by default
374 silently trust signed SSHFP records. This can be controlled with
375 the VerifyHostKeyDNS client configuration setting. DNSSEC support
376 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
379 The GNU Compiler Collection and C++ standard library (libstdc++)
380 are no longer built by default on platforms where clang is the system
381 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
385 The PROCDESC kernel option is now part of the GENERIC kernel
386 configuration and is required for the rwhod(8) to work.
387 If you are using custom kernel configuration, you should include
391 The API and ABI related to the Capsicum framework was modified
392 in backward incompatible way. The userland libraries and programs
393 have to be recompiled to work with the new kernel. This includes the
394 following libraries and programs, but the whole buildworld is
395 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
396 kdump, procstat, rwho, rwhod, uniq.
399 AES-NI intrinsic support has been added to gcc. The AES-NI module
400 has been updated to use this support. A new gcc is required to build
401 the aesni module on both i386 and amd64.
404 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
405 Thus "device padlock_rng" and "device rdrand_rng" should be
406 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
409 WITH_ICONV has been split into two feature sets. WITH_ICONV now
410 enables just the iconv* functionality and is now on by default.
411 WITH_LIBICONV_COMPAT enables the libiconv api and link time
412 compatability. Set WITHOUT_ICONV to build the old way.
413 If you have been using WITH_ICONV before, you will very likely
414 need to turn on WITH_LIBICONV_COMPAT.
417 INVARIANTS option now enables DEBUG for code with OpenSolaris and
418 Illumos origin, including ZFS. If you have INVARIANTS in your
419 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
421 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
422 locks if WITNESS option was set. Because that generated a lot of
423 witness(9) reports and all of them were believed to be false
424 positives, this is no longer done. New option OPENSOLARIS_WITNESS
425 can be used to achieve the previous behavior.
428 Timer values in IPv6 data structures now use time_uptime instead
429 of time_second. Although this is not a user-visible functional
430 change, userland utilities which directly use them---ndp(8),
431 rtadvd(8), and rtsold(8) in the base system---need to be updated
435 find -delete can now delete the pathnames given as arguments,
436 instead of only files found below them or if the pathname did
437 not contain any slashes. Formerly, the following error message
440 find: -delete: <path>: relative path potentially not safe
442 Deleting the pathnames given as arguments can be prevented
443 without error messages using -mindepth 1 or by changing
444 directory and passing "." as argument to find. This works in the
445 old as well as the new version of find.
448 Behavior of devfs rules path matching has been changed.
449 Pattern is now always matched against fully qualified devfs
450 path and slash characters must be explicitly matched by
451 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
452 subdirectories must be reviewed.
455 The default ARM ABI has changed to the ARM EABI. The old ABI is
456 incompatible with the ARM EABI and all programs and modules will
457 need to be rebuilt to work with a new kernel.
459 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
461 NOTE: Support for the old ABI will be removed in the future and
462 users are advised to upgrade.
465 pkg_install has been disconnected from the build if you really need it
466 you should add WITH_PKGTOOLS in your src.conf(5).
469 Most of network statistics structures were changed to be able
470 keep 64-bits counters. Thus all tools, that work with networking
471 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
474 Fix targets that run multiple make's to use && rather than ;
475 so that subsequent steps depend on success of previous.
477 NOTE: if building 'universe' with -j* on stable/8 or stable/9
478 it would be better to start the build using bmake, to avoid
479 overloading the machine.
482 Fix a bug that allowed a tracing process (e.g. gdb) to write
483 to a memory-mapped file in the traced process's address space
484 even if neither the traced process nor the tracing process had
485 write access to that file.
488 CVS has been removed from the base system. An exact copy
489 of the code is available from the devel/cvs port.
492 Some people report the following error after the switch to bmake:
494 make: illegal option -- J
495 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
497 *** [buildworld] Error code 2
499 this likely due to an old instance of make in
500 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
501 which src/Makefile will use that blindly, if it exists, so if
502 you see the above error:
504 rm -rf `make -V MAKEPATH`
509 Use bmake by default.
510 Whereas before one could choose to build with bmake via
511 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
512 make. The goal is to remove these knobs for 10-RELEASE.
514 It is worth noting that bmake (like gmake) treats the command
515 line as the unit of failure, rather than statements within the
516 command line. Thus '(cd some/where && dosomething)' is safer
517 than 'cd some/where; dosomething'. The '()' allows consistent
518 behavior in parallel build.
521 Fix a bug that allows NFS clients to issue READDIR on files.
524 The WITHOUT_IDEA option has been removed because
525 the IDEA patent expired.
528 The sysctl which controls TRIM support under ZFS has been renamed
529 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
533 The mergemaster command now uses the default MAKEOBJDIRPREFIX
534 rather than creating it's own in the temporary directory in
535 order allow access to bootstrapped versions of tools such as
536 install and mtree. When upgrading from version of FreeBSD where
537 the install command does not support -l, you will need to
538 install a new mergemaster command if mergemaster -p is required.
539 This can be accomplished with the command (cd src/usr.sbin/mergemaster
543 Legacy ATA stack, disabled and replaced by new CAM-based one since
544 FreeBSD 9.0, completely removed from the sources. Kernel modules
545 atadisk and atapi*, user-level tools atacontrol and burncd are
546 removed. Kernel option `options ATA_CAM` is now permanently enabled
550 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
551 and socketpair(2). Software, in particular Kerberos, may
552 automatically detect and use these during building. The resulting
553 binaries will not work on older kernels.
556 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
557 information, see the respective 20130304 entry).
560 Recent commits to callout(9) changed the size of struct callout,
561 so the KBI is probably heavily disturbed. Also, some functions
562 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
563 by macros. Every kernel module using it won't load, so rebuild
566 The ctl device has been re-enabled in GENERIC for i386 and amd64,
567 but does not initialize by default (because of the new CTL_DISABLE
568 option) to save memory. To re-enable it, remove the CTL_DISABLE
569 option from the kernel config file or set kern.cam.ctl.disable=0
570 in /boot/loader.conf.
573 The ctl device has been disabled in GENERIC for i386 and amd64.
574 This was done due to the extra memory being allocated at system
575 initialisation time by the ctl driver which was only used if
576 a CAM target device was created. This makes a FreeBSD system
577 unusable on 128MB or less of RAM.
580 A new compression method (lz4) has been merged to -HEAD. Please
581 refer to zpool-features(7) for more information.
583 Please refer to the "ZFS notes" section of this file for information
584 on upgrading boot ZFS pools.
587 A BSD-licensed patch(1) variant has been added and is installed
588 as bsdpatch, being the GNU version the default patch.
589 To inverse the logic and use the BSD-licensed one as default,
590 while having the GNU version installed as gnupatch, rebuild
591 and install world with the WITH_BSD_PATCH knob set.
594 Due to the use of the new -l option to install(1) during build
595 and install, you must take care not to directly set the INSTALL
596 make variable in your /etc/make.conf, /etc/src.conf, or on the
597 command line. If you wish to use the -C flag for all installs
598 you may be able to add INSTALL+=-C to /etc/make.conf or
602 The install(1) option -M has changed meaning and now takes an
603 argument that is a file or path to append logs to. In the
604 unlikely event that -M was the last option on the command line
605 and the command line contained at least two files and a target
606 directory the first file will have logs appended to it. The -M
607 option served little practical purpose in the last decade so its
608 use is expected to be extremely rare.
611 After switching to Clang as the default compiler some users of ZFS
612 on i386 systems started to experience stack overflow kernel panics.
613 Please consider using 'options KSTACK_PAGES=4' in such configurations.
616 GEOM_LABEL now mangles label names read from file system metadata.
617 Mangling affect labels containing spaces, non-printable characters,
618 '%' or '"'. Device names in /etc/fstab and other places may need to
622 By default, only the 10 most recent kernel dumps will be saved. To
623 restore the previous behaviour (no limit on the number of kernel dumps
624 stored in the dump directory) add the following line to /etc/rc.conf:
629 With the addition of auditdistd(8), a new auditdistd user is now
630 required during installworld. "mergemaster -p" can be used to
631 add the user prior to installworld, as documented in the handbook.
634 The sin6_scope_id member variable in struct sockaddr_in6 is now
635 filled by the kernel before passing the structure to the userland via
636 sysctl or routing socket. This means the KAME-specific embedded scope
637 id in sin6_addr.s6_addr[2] is always cleared in userland application.
638 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
639 __FreeBSD_version is bumped to 1000025.
642 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
643 This means that the world and kernel will be compiled with clang
644 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
645 and /usr/bin/cpp. To disable this behavior and revert to building
646 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
647 of current may need to bootstrap WITHOUT_CLANG first if the clang
648 build fails (its compatibility window doesn't extend to the 9 stable
652 The IPFIREWALL_FORWARD kernel option has been removed. Its
653 functionality now turned on by default.
656 The ZERO_COPY_SOCKET kernel option has been removed and
657 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
658 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
659 mechanism which is not safe and may result in kernel crashes.
660 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
661 driver supports disposeable external page sized mbuf storage.
662 Proper replacements for both zero-copy mechanisms are under
663 consideration and will eventually lead to complete removal
664 of the two kernel options.
667 The IPv4 network stack has been converted to network byte
668 order. The following modules need to be recompiled together
669 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
670 pf(4), ipfw(4), ng_ipfw(4), stf(4).
673 Support for non-MPSAFE filesystems was removed from VFS. The
674 VFS_VERSION was bumped, all filesystem modules shall be
678 All the non-MPSAFE filesystems have been disconnected from
679 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
680 portalfs, smbfs, xfs.
683 The interface cloning API and ABI has changed. The following
684 modules need to be recompiled together with kernel:
685 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
686 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
687 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
690 The sdhci driver was split in two parts: sdhci (generic SD Host
691 Controller logic) and sdhci_pci (actual hardware driver).
692 No kernel config modifications are required, but if you
693 load sdhc as a module you must switch to sdhci_pci instead.
696 Import the FUSE kernel and userland support into base system.
699 The GNU sort(1) program has been removed since the BSD-licensed
700 sort(1) has been the default for quite some time and no serious
701 problems have been reported. The corresponding WITH_GNU_SORT
705 The pfil(9) API/ABI for AF_INET family has been changed. Packet
706 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
710 The net80211(4) ABI has been changed to allow for improved driver
711 PS-POLL and power-save support. All wireless drivers need to be
712 recompiled to work with the new kernel.
715 The random(4) support for the VIA hardware random number
716 generator (`PADLOCK') is no longer enabled unconditionally.
717 Add the padlock_rng device in the custom kernel config if
718 needed. The GENERIC kernels on i386 and amd64 do include the
719 device, so the change only affects the custom kernel
723 The pf(4) packet filter ABI has been changed. pfctl(8) and
724 snmp_pf module need to be recompiled to work with new kernel.
727 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
728 to -HEAD. Pools that have empty_bpobj in active state can not be
729 imported read-write with ZFS implementations that do not support
730 this feature. For more information read the zpool-features(5)
734 The sparc64 ZFS loader has been changed to no longer try to auto-
735 detect ZFS providers based on diskN aliases but now requires these
736 to be explicitly listed in the OFW boot-device environment variable.
739 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
740 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
741 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
744 The following sysctls and tunables have been renamed for consistency
745 with other variables:
746 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
747 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
750 The sort utility has been replaced with BSD sort. For now, GNU sort
751 is also available as "gnusort" or the default can be set back to
752 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
753 installed as "bsdsort".
756 A new version of ZFS (pool version 5000) has been merged to -HEAD.
757 Starting with this version the old system of ZFS pool versioning
758 is superseded by "feature flags". This concept enables forward
759 compatibility against certain future changes in functionality of ZFS
760 pools. The first read-only compatible "feature flag" for ZFS pools
761 is named "com.delphix:async_destroy". For more information
762 read the new zpool-features(5) manual page.
763 Please refer to the "ZFS notes" section of this file for information
764 on upgrading boot ZFS pools.
767 The malloc(3) implementation embedded in libc now uses sources imported
768 as contrib/jemalloc. The most disruptive API change is to
769 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
770 delete it prior to installworld, and optionally re-create it using the
771 new format after rebooting. See malloc.conf(5) for details
772 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
776 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
777 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
778 now spelled mips. This is to aid compatibility with third-party
779 software that expects this naming scheme in uname(3). Little-endian
780 settings are unchanged. If you are updating a big-endian mips64 machine
781 from before this change, you may need to set MACHINE_ARCH=mips64 in
782 your environment before the new build system will recognize your machine.
785 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
789 Now unix domain sockets behave "as expected" on nullfs(5). Previously
790 nullfs(5) did not pass through all behaviours to the underlying layer,
791 as a result if we bound to a socket on the lower layer we could connect
792 only to the lower path; if we bound to the upper layer we could connect
793 only to the upper path. The new behavior is one can connect to both the
794 lower and the upper paths regardless what layer path one binds to.
797 The getifaddrs upgrade path broken with 20111215 has been restored.
798 If you have upgraded in between 20111215 and 20120209 you need to
799 recompile libc again with your kernel. You still need to recompile
800 world to be able to configure CARP but this restriction already
804 The set_rcvar() function has been removed from /etc/rc.subr. All
805 base and ports rc.d scripts have been updated, so if you have a
806 port installed with a script in /usr/local/etc/rc.d you can either
807 hand-edit the rcvar= line, or reinstall the port.
809 An easy way to handle the mass-update of /etc/rc.d:
810 rm /etc/rc.d/* && mergemaster -i
813 panic(9) now stops other CPUs in the SMP systems, disables interrupts
814 on the current CPU and prevents other threads from running.
815 This behavior can be reverted using the kern.stop_scheduler_on_panic
817 The new behavior can be incompatible with kern.sync_on_panic.
820 The carp(4) facility has been changed significantly. Configuration
821 of the CARP protocol via ifconfig(8) has changed, as well as format
822 of CARP events submitted to devd(8) has changed. See manual pages
823 for more information. The arpbalance feature of carp(4) is currently
824 not supported anymore.
826 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
827 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
828 need to be recompiled.
831 The acpi_wmi(4) status device /dev/wmistat has been renamed to
835 The option VFS_ALLOW_NONMPSAFE option has been added in order to
836 explicitely support non-MPSAFE filesystems.
837 It is on by default for all supported platform at this present
841 The broken amd(4) driver has been replaced with esp(4) in the amd64,
842 i386 and pc98 GENERIC kernel configuration files.
845 sysinstall has been removed
848 The stable/9 branch created in subversion. This corresponds to the
849 RELENG_9 branch in CVS.
852 This commit modifies vfs_register() so that it uses a hash
853 calculation to set vfc_typenum, which is enabled by default.
854 The first time a system is booted after this change, the
855 vfc_typenum values will change for all file systems. The
856 main effect of this is a change to the NFS server file handles
857 for file systems that use vfc_typenum in their fsid, such as ZFS.
858 It will, however, prevent vfc_typenum from changing when file
859 systems are loaded in a different order for subsequent reboots.
860 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
861 until you are ready to remount all NFS clients after a reboot.
864 Bump the shared library version numbers for libraries that
865 do not use symbol versioning, have changed the ABI compared
866 to stable/8 and which shared library version was not bumped.
867 Done as part of 9.0-RELEASE cycle.
870 During the merge of Capsicum features, the fget(9) KPI was modified.
871 This may require the rebuilding of out-of-tree device drivers --
872 issues have been reported specifically with the nVidia device driver.
873 __FreeBSD_version is bumped to 900041.
875 Also, there is a period between 20110811 and 20110814 where the
876 special devices /dev/{stdin,stdout,stderr} did not work correctly.
877 Building world from a kernel during that window may not work.
880 The packet filter (pf) code has been updated to OpenBSD 4.5.
881 You need to update userland tools to be in sync with kernel.
882 This update breaks backward compatibility with earlier pfsync(4)
883 versions. Care must be taken when updating redundant firewall setups.
886 The following sysctls and tunables are retired on x86 platforms:
888 machdep.hlt_logical_cpus
889 The following sysctl is retired:
890 machdep.hyperthreading_allowed
891 The sysctls were supposed to provide a way to dynamically offline and
892 online selected CPUs on x86 platforms, but the implementation has not
893 been reliable especially with SCHED_ULE scheduler.
894 machdep.hyperthreading_allowed tunable is still available to ignore
895 hyperthreading CPUs at OS level.
896 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
897 where X is an APIC ID of a CPU. Be advised, though, that disabling
898 CPUs in non-uniform fashion will result in non-uniform topology and
899 may lead to sub-optimal system performance with SCHED_ULE, which is
903 cpumask_t type is retired and cpuset_t is used in order to describe
907 Changes to ifconfig(8) for dynamic address family detection mandate
908 that you are running a kernel of 20110525 or later. Make sure to
909 follow the update procedure to boot a new kernel before installing
913 Support for sun4v architecture is officially dropped
916 Several KPI breaking changes have been committed to the mii(4) layer,
917 the PHY drivers and consequently some Ethernet drivers using mii(4).
918 This means that miibus.ko and the modules of the affected Ethernet
919 drivers need to be recompiled.
921 Note to kernel developers: Given that the OUI bit reversion problem
922 was fixed as part of these changes all mii(4) commits related to OUIs,
923 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
924 handling, no longer can be merged verbatim to stable/8 and previous
928 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
929 into their kernel configurations along with 'device pci'.
932 The default NFS client is now the new NFS client, so fstype "newnfs"
933 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
934 Although mounts via fstype "nfs" will usually work without userland
935 changes, it is recommended that the mount(8) and mount_nfs(8)
936 commands be rebuilt from sources and that a link to mount_nfs called
937 mount_oldnfs be created. The new client is compiled into the
938 kernel with "options NFSCL" and this is needed for diskless root
939 file systems. The GENERIC kernel configs have been changed to use
940 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
941 To use the regular/old client, you can "mount -t oldnfs ...". For
942 a diskless root file system, you must also include a line like:
944 vfs.root.mountfrom="oldnfs:"
946 in the boot/loader.conf on the root fs on the NFS server to make
947 a diskless root fs use the old client.
950 The GENERIC kernels for all architectures now default to the new
951 CAM-based ATA stack. It means that all legacy ATA drivers were
952 removed and replaced by respective CAM drivers. If you are using
953 ATA device names in /etc/fstab or other places, make sure to update
954 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
955 where 'Y's are the sequential numbers starting from zero for each type
956 in order of detection, unless configured otherwise with tunables,
957 see cam(4)). There will be symbolic links created in /dev/ to map
958 old adX devices to the respective adaY. They should provide basic
959 compatibility for file systems mounting in most cases, but they do
960 not support old user-level APIs and do not have respective providers
961 in GEOM. Consider using updated management tools with new device names.
963 It is possible to load devices ahci, ata, siis and mvs as modules,
964 but option ATA_CAM should remain in kernel configuration to make ata
965 module work as CAM driver supporting legacy ATA controllers. Device ata
966 still can be used in modular fashion (atacore + ...). Modules atadisk
967 and atapi* are not used and won't affect operation in ATA_CAM mode.
968 Note that to use CAM-based ATA kernel should include CAM devices
969 scbus, pass, da (or explicitly ada), cd and optionally others. All of
970 them are parts of the cam module.
972 ataraid(4) functionality is now supported by the RAID GEOM class.
973 To use it you can load geom_raid kernel module and use graid(8) tool
974 for management. Instead of /dev/arX device names, use /dev/raid/rX.
976 No kernel config options or code have been removed, so if a problem
977 arises, please report it and optionally revert to the old ATA stack.
978 In order to do it you can remove from the kernel config:
983 , and instead add back:
984 device atadisk # ATA disk drives
985 device ataraid # ATA RAID drives
986 device atapicd # ATAPI CDROM drives
987 device atapifd # ATAPI floppy drives
988 device atapist # ATAPI tape drives
991 The default NFS server has been changed to the new server, which
992 was referred to as the experimental server. If you need to switch
993 back to the old NFS server, you must now put the "-o" option on
994 both the mountd and nfsd commands. This can be done using the
995 mountd_flags and nfs_server_flags rc.conf variables until an
996 update to the rc scripts is committed, which is coming soon.
999 The GNU Objective-C runtime library (libobjc), and other Objective-C
1000 related components have been removed from the base system. If you
1001 require an Objective-C library, please use one of the available ports.
1004 ath(4) has been split into bus- and device- modules. if_ath contains
1005 the HAL, the TX rate control and the network device code. if_ath_pci
1006 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
1007 contains the AHB glue. Users need to load both if_ath_pci and if_ath
1008 in order to use ath on everything else.
1010 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
1011 need to load if_ath and if_ath_pci for ath(4) operation.
1014 As part of the replacement of sysinstall, the process of building
1015 release media has changed significantly. For details, please re-read
1016 release(7), which has been updated to reflect the new build process.
1019 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
1020 is the last available version under GPLv2. It brings a number of new
1021 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
1022 4.1 and SSE 4.2), better support for powerpc64, a number of new
1023 directives, and lots of other small improvements. See the ChangeLog
1024 file in contrib/binutils for the full details.
1027 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
1028 compliant, and will now use half of hash for authentication.
1029 This will break interoperability with all stacks (including all
1030 actual FreeBSD versions) who implement
1031 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
1033 The only workaround with such peers is to use another HMAC
1034 algorithm for IPsec ("phase 2") authentication.
1037 Remove the uio_yield prototype and symbol. This function has
1038 been misnamed since it was introduced and should not be
1039 globally exposed with this name. The equivalent functionality
1040 is now available using kern_yield(curthread->td_user_pri).
1041 The function remains undocumented.
1044 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
1045 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
1046 for scalar sysctls is defined but disabled. Code that needs
1047 UQUAD to pass the type checking that must compile on older
1048 systems where the define is not present can check against
1049 __FreeBSD_version >= 900030.
1051 The system dialog(1) has been replaced with a new version previously
1052 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
1053 with the previous version, but the libdialog associated with it has
1054 a largely incompatible API. As such, the original version of libdialog
1055 will be kept temporarily as libodialog, until its base system consumers
1056 are replaced or updated. Bump __FreeBSD_version to 900030.
1059 If you are trying to run make universe on a -stable system, and you get
1060 the following warning:
1061 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
1062 unknown. config(8) likely too old."
1063 or something similar to it, then you must upgrade your -stable system
1064 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
1065 stable/8) or build the config from the latest stable/8 branch and
1066 install it on your system.
1068 Prior to this date, building a current universe on 8-stable system from
1069 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
1070 error in the first kernel build phase. A new config on those old
1071 systems will fix that problem for older versions of -current.
1074 The TCP stack has been modified to allow Khelp modules to interact with
1075 it via helper hook points and store per-connection data in the TCP
1076 control block. Bump __FreeBSD_version to 900029. User space tools that
1077 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
1081 Generic IEEE 802.3 annex 31B full duplex flow control support has been
1082 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
1083 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
1084 to take advantage of it instead of using custom implementations. This
1085 means that these drivers now no longer unconditionally advertise
1086 support for flow control but only do so if flow control is a selected
1087 media option. This was implemented in the generic support that way in
1088 order to allow flow control to be switched on and off via ifconfig(8)
1089 with the PHY specific default to typically off in order to protect
1090 from unwanted effects. Consequently, if you used flow control with
1091 one of the above mentioned drivers you now need to explicitly enable
1092 it, for example via:
1093 ifconfig bge0 media auto mediaopt flowcontrol
1095 Along with the above mentioned changes generic support for setting
1096 1000baseT master mode also has been added and brgphy(4), ciphy(4),
1097 e1000phy(4) as well as ip1000phy(4) have been converted to take
1098 advantage of it. This means that these drivers now no longer take the
1099 link0 parameter for selecting master mode but the master media option
1100 has to be used instead, for example like in the following:
1101 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
1103 Selection of master mode now is also available with all other PHY
1104 drivers supporting 1000baseT.
1107 The TCP stack has received a significant update to add support for
1108 modularised congestion control and generally improve the clarity of
1109 congestion control decisions. Bump __FreeBSD_version to 900025. User
1110 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
1111 sockstat) need to be recompiled.
1114 The man(1) utility has been replaced by a new version that no longer
1115 uses /etc/manpath.config. Please consult man.conf(5) for how to
1116 migrate local entries to the new format.
1119 The copyright strings printed by login(1) and sshd(8) at the time of a
1120 new connection have been removed to follow other operating systems and
1124 A workaround for a fixed ld bug has been removed in kernel code,
1125 so make sure that your system ld is built from sources after
1126 revision 210245 from 2010-07-19 (r211583 if building head kernel
1127 on stable/8, r211584 for stable/7; both from 2010-08-21).
1128 A symptom of incorrect ld version is different addresses for
1129 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
1132 The $ipv6_prefer variable in rc.conf(5) has been split into
1133 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
1135 The $ip6addrctl_policy is a variable to choose a pre-defined
1136 address selection policy set by ip6addrctl(8). A value
1137 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
1140 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
1141 flag (see an entry of 20090926) is set on an interface with no
1142 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
1143 security reason. If you want IPv6 link-local address on all
1144 interfaces by default, set this to "YES".
1146 The old ipv6_prefer="YES" is equivalent to
1147 ipv6_activate_all_interfaces="YES" and
1148 ip6addrctl_policy="ipv6_prefer".
1151 DTrace has grown support for userland tracing. Due to this, DTrace is
1152 now i386 and amd64 only.
1153 dtruss(1) is now installed by default on those systems and a new
1154 kernel module is needed for userland tracing: fasttrap.
1155 No changes to your kernel config file are necessary to enable
1156 userland tracing, but you might consider adding 'STRIP=' and
1157 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
1158 to have informative userland stack traces in DTrace (ustack).
1161 The acpi_aiboost(4) driver has been removed in favor of the new
1162 aibs(4) driver. You should update your kernel configuration file.
1165 BSD grep has been imported to the base system and it is built by
1166 default. It is completely BSD licensed, highly GNU-compatible, uses
1167 less memory than its GNU counterpart and has a small codebase.
1168 However, it is slower than its GNU counterpart, which is mostly
1169 noticeable for larger searches, for smaller ones it is measurable
1170 but not significant. The reason is complex, the most important factor
1171 is that we lack a modern and efficient regex library and GNU
1172 overcomes this by optimizing the searches internally. Future work
1173 on improving the regex performance is planned, for the meantime,
1174 users that need better performance, can build GNU grep instead by
1175 setting the WITH_GNU_GREP knob.
1178 Due to the import of powerpc64 support, all existing powerpc kernel
1179 configuration files must be updated with a machine directive like this:
1180 machine powerpc powerpc
1182 In addition, an updated config(8) is required to build powerpc kernels
1186 A new version of ZFS (version 15) has been merged to -HEAD.
1187 This version uses a python library for the following subcommands:
1188 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
1189 For full functionality of these commands the following port must
1190 be installed: sysutils/py-zfs
1193 'vm_page's are now hashed by physical address to an array of mutexes.
1194 Currently this is only used to serialize access to hold_count. Over
1195 time the page queue mutex will be peeled away. This changes the size
1196 of pmap on every architecture. And requires all callers of vm_page_hold
1197 and vm_page_unhold to be updated.
1200 WITH_CTF can now be specified in src.conf (not recommended, there
1201 are some problems with static executables), make.conf (would also
1202 affect ports which do not use GNU make and do not override the
1203 compile targets) or in the kernel config (via "makeoptions
1205 When WITH_CTF was specified there before this was silently ignored,
1206 so make sure that WITH_CTF is not used in places which could lead
1207 to unwanted behavior.
1210 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
1211 to allow 32-bit compatibility on non-x86 platforms. All kernel
1212 configurations on amd64 and ia64 platforms using these options must
1213 be modified accordingly.
1216 The utmp user accounting database has been replaced with utmpx,
1217 the user accounting interface standardized by POSIX.
1218 Unfortunately the semantics of utmp and utmpx don't match,
1219 making it practically impossible to support both interfaces.
1220 The user accounting database is used by tools like finger(1),
1221 last(1), talk(1), w(1) and ac(8).
1223 All applications in the base system use utmpx. This means only
1224 local binaries (e.g. from the ports tree) may still use these
1225 utmp database files. These applications must be rebuilt to make
1228 After the system has been upgraded, it is safe to remove the old
1229 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
1230 assuming their contents is of no importance anymore. Old wtmp
1231 databases can only be used by last(1) and ac(8) after they have
1232 been converted to the new format using wtmpcvt(1).
1235 Introduce the kernel thread "deadlock resolver" (which can be enabled
1236 via the DEADLKRES option, see NOTES for more details) and the
1237 sleepq_type() function for sleepqueues.
1240 The rc.firewall and rc.firewall6 were unified, and
1241 rc.firewall6 and rc.d/ip6fw were removed.
1242 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
1243 variables are obsoleted. Instead, the following new rc
1244 variables are added to rc.d/ipfw:
1246 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1247 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1248 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1250 The meanings correspond to the relevant IPv4 variables.
1256 The default terminal emulation for syscons(4) has been changed
1257 from cons25 to xterm on all platforms except pc98. This means
1258 that the /etc/ttys file needs to be updated to ensure correct
1259 operation of applications on the console.
1261 The terminal emulation style can be toggled per window by using
1262 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1263 options can be used to change the compile-time default back to
1266 To prevent graphical artifacts, make sure the TERM environment
1267 variable is set to match the terminal emulation that is being
1268 performed by syscons(4).
1271 The layout of the structure ieee80211req_scan_result has changed.
1272 Applications that require wireless scan results (e.g. ifconfig(8))
1273 from net80211 need to be recompiled.
1275 Applications such as wpa_supplicant(8) may require a full world
1276 build without using NO_CLEAN in order to get synchronized with the
1280 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1281 There's one kernel module for each firmware. Adding "device iwnfw"
1282 to the kernel configuration file means including all three firmware
1283 images inside the kernel. If you want to include just the one for
1284 your wireless card, use the devices iwn4965fw, iwn5000fw or
1288 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1289 into rc.d/netif. The changes are the following:
1291 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1292 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1293 Note that both variables need the "inet6" keyword at the head.
1295 Do not set $ipv6_network_interfaces manually if you do not
1296 understand what you are doing. It is not needed in most cases.
1298 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1301 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1302 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1304 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1305 all configured interfaces have "inet6 accept_rtadv" in the
1306 $ifconfig_IF_ipv6. These are for backward compatibility.
1308 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1309 functionality of interfaces with no corresponding
1310 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1311 and the default address selection policy of ip6addrctl(8)
1312 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1313 Note that if you want to configure IPv6 functionality on the
1314 disabled interfaces after boot, first you need to clear the flag by
1315 using ifconfig(8) like:
1317 ifconfig em0 inet6 -ifdisabled
1319 If YES, the default address selection policy is set as
1322 The default value of $ipv6_prefer is NO.
1324 4. If your system need to receive Router Advertisement messages,
1325 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1326 scripts automatically invoke rtsol(8) when the interface becomes
1327 UP. The Router Advertisement messages are used for SLAAC
1328 (State-Less Address AutoConfiguration).
1331 802.11s D3.03 support was committed. This is incompatible with the
1332 previous code, which was based on D3.0.
1335 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1336 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1337 control whether accepting Router Advertisement messages or not.
1338 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1339 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1340 The ifconfig(8) utility now supports these flags.
1343 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1344 mount(8) and -a option for df(1) to see them.
1347 The old tunable hw.bus.devctl_disable has been superseded by
1348 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1349 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1353 Remove the option STOP_NMI. The default action is now to use NMI only
1354 for KDB via the newly introduced function stop_cpus_hard() and
1355 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1358 The stable/8 branch created in subversion. This corresponds to the
1359 RELENG_8 branch in CVS.
1362 Bump the shared library version numbers for all libraries that do not
1363 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1364 __FreeBSD_version to 800105.
1367 Due to changes in the implementation of virtual network stack support,
1368 all network-related kernel modules must be recompiled. As this change
1369 breaks the ABI, bump __FreeBSD_version to 800104.
1372 The TOE interface to the TCP syncache has been modified to remove
1373 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1374 The cxgb driver is the only TOE consumer affected by this change, and
1375 needs to be recompiled along with the kernel. As this change breaks
1376 the ABI, bump __FreeBSD_version to 800103.
1379 Padding has been added to struct tcpcb, sackhint and tcpstat in
1380 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1381 maintaining the ABI. However, this change breaks the ABI, so bump
1382 __FreeBSD_version to 800102. User space tools that rely on the size of
1383 any of these structs (e.g. sockstat) need to be recompiled.
1386 The NFS_LEGACYRPC option has been removed along with the old kernel
1387 RPC implementation that this option selected. Kernel configurations
1388 may need to be adjusted.
1391 The network interface device nodes at /dev/net/<interface> have been
1392 removed. All ioctl operations can be performed the normal way using
1393 routing sockets. The kqueue functionality can generally be replaced
1394 with routing sockets.
1397 The documentation from the FreeBSD Documentation Project (Handbook,
1398 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1399 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1402 The ABI of various structures related to the SYSV IPC API have been
1403 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1404 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1408 Layout of struct vnet has changed as routing related variables were
1409 moved to their own Vimage module. Modules need to be recompiled. Bump
1410 __FreeBSD_version to 800099.
1413 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1414 respectively. As long as no more than 16 groups per process are used,
1415 no changes should be visible. When more than 16 groups are used, old
1416 binaries may fail if they call getgroups() or getgrouplist() with
1417 statically sized storage. Recompiling will work around this, but
1418 applications should be modified to use dynamically allocated storage
1419 for group arrays as POSIX.1-2008 does not cap an implementation's
1420 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1422 NFS and portalfs mounts may also be affected as the list of groups is
1423 truncated to 16. Users of NFS who use more than 16 groups, should
1424 take care that negative group permissions are not used on the exported
1425 file systems as they will not be reliable unless a GSSAPI based
1426 authentication method is used.
1429 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1430 option compiles in the support for adaptive spinning for lockmgrs
1431 which want to enable it. The lockinit() function now accepts the flag
1432 LK_ADAPTIVE in order to make the lock object subject to adaptive
1433 spinning when both held in write and read mode.
1436 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1437 changed. User applications that use this ioctl need to be rebuilt.
1440 The layout of struct thread has changed. Kernel and modules need to
1444 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1445 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1448 window(1) has been removed from the base system. It can now be
1449 installed from ports. The port is called misc/window.
1452 The way we are storing and accessing `routing table' entries has
1453 changed. Programs reading the FIB, like netstat, need to be
1457 A new netisr implementation has been added for FreeBSD 8. Network
1458 file system modules, such as igmp, ipdivert, and others, should be
1460 Bump __FreeBSD_version to 800096.
1463 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1467 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1468 Bump __FreeBSD_version to 800094.
1471 Add mnt_xflag field to 'struct mount'. File system modules need to be
1473 Bump __FreeBSD_version to 800093.
1476 The compiling option ADAPTIVE_SX has been retired while it has been
1477 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1478 The KPI for sx_init_flags() changes as accepting flags:
1479 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1480 been introduced in order to handle the reversed logic.
1481 Bump __FreeBSD_version to 800092.
1484 Add support for hierarchical jails. Remove global securelevel.
1485 Bump __FreeBSD_version to 800091.
1488 The layout of struct vnet_net has changed, therefore modules
1490 Bump __FreeBSD_version to 800090.
1493 The newly imported zic(8) produces a new format in the output. Please
1494 run tzsetup(8) to install the newly created data to /etc/localtime.
1497 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1498 hw.usb.* and is now consistent again with previous releases.
1501 802.11 monitor mode support was revised and driver api's were changed.
1502 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1503 of DLT_IEEE802_11. No user-visible data structures were changed but
1504 applications that use DLT_IEEE802_11 may require changes.
1505 Bump __FreeBSD_version to 800088.
1508 The layout of the following structs has changed: sysctl_oid,
1509 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1510 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1511 panics may be experienced. World rebuild is required for
1512 correctly checking networking state from userland.
1513 Bump __FreeBSD_version to 800085.
1516 MLDv2 and Source-Specific Multicast (SSM) have been merged
1517 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1518 The implementation of SSM within FreeBSD's IPv6 stack closely
1519 follows the IPv4 implementation.
1521 For kernel developers:
1523 * The most important changes are that the ip6_output() and
1524 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1525 and this lock has been downgraded to a non-recursive mutex.
1527 * As with the changes to the IPv4 stack to support SSM, filtering
1528 of inbound multicast traffic must now be performed by transport
1529 protocols within the IPv6 stack. This does not apply to TCP and
1530 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1532 * The KPIs used by IPv6 multicast are similar to those used by
1533 the IPv4 stack, with the following differences:
1534 * im6o_mc_filter() is analogous to imo_multicast_filter().
1535 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1536 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1537 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1538 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1539 for MLDv1 have an additional 'timer' argument which is used to
1540 jitter the initial membership report for the solicited-node
1541 multicast membership on-link.
1542 * This is not strictly needed for MLDv2, which already jitters
1543 its report transmissions. However, the 'timer' argument is
1544 preserved in case MLDv1 is active on the interface.
1546 * The KAME linked-list based IPv6 membership implementation has
1547 been refactored to use a vector similar to that used by the IPv4
1549 Code which maintains a list of its own multicast memberships
1550 internally, e.g. carp, has been updated to reflect the new
1553 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1554 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1555 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1556 implementation constraint which needs to be addressed in HEAD.
1558 For application developers:
1560 * The changes are broadly similar to those made for the IPv4
1563 * The use of IPv4 and IPv6 multicast socket options on the same
1564 socket, using mapped addresses, HAS NOT been tested or supported.
1566 * There are a number of issues with the implementation of various
1567 IPv6 multicast APIs which need to be resolved in the API surface
1568 before the implementation is fully compatible with KAME userland
1569 use, and these are mostly to do with interface index treatment.
1571 * The literature available discusses the use of either the delta / ASM
1572 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1573 using setsourcefilter(3)/getsourcefilter(3). For more information
1574 please refer to RFC 3768, 'Socket Interface Extensions for
1575 Multicast Source Filters'.
1577 * Applications which use the published RFC 3678 APIs should be fine.
1579 For systems administrators:
1581 * The mtest(8) utility has been refactored to support IPv6, in
1582 addition to IPv4. Interface addresses are no longer accepted
1583 as arguments, their names must be used instead. The utility
1584 will map the interface name to its first IPv4 address as
1585 returned by getifaddrs(3).
1587 * The ifmcstat(8) utility has also been updated to print the MLDv2
1588 endpoint state and source filter lists via sysctl(3).
1590 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1591 loopback of IPv6 multicast datagrams by default; it defaults to 1
1592 to preserve the existing behaviour. Disabling multicast loopback is
1593 recommended for optimal system performance.
1595 * The IPv6 MROUTING code has been changed to examine this sysctl
1596 instead of attempting to perform a group lookup before looping
1597 back forwarded datagrams.
1599 Bump __FreeBSD_version to 800084.
1602 Implement low-level Bluetooth HCI API.
1603 Bump __FreeBSD_version to 800083.
1606 The layout of struct malloc_type, used by modules to register new
1607 memory allocation types, has changed. Most modules will need to
1608 be rebuilt or panics may be experienced.
1609 Bump __FreeBSD_version to 800081.
1612 Anticipate overflowing inp_flags - add inp_flags2.
1613 This changes most offsets in inpcb, so checking v4 connection
1614 state will require a world rebuild.
1615 Bump __FreeBSD_version to 800080.
1618 Add an llentry to struct route and struct route_in6. Modules
1619 embedding a struct route will need to be recompiled.
1620 Bump __FreeBSD_version to 800079.
1623 The size of rt_metrics_lite and by extension rtentry has changed.
1624 Networking administration apps will need to be recompiled.
1625 The route command now supports show as an alias for get, weighting
1626 of routes, sticky and nostick flags to alter the behavior of stateful
1628 Bump __FreeBSD_version to 800078.
1631 Do not use Giant for kbdmux(4) locking. This is wrong and
1632 apparently causing more problems than it solves. This will
1633 re-open the issue where interrupt handlers may race with
1634 kbdmux(4) in polling mode. Typical symptoms include (but
1635 not limited to) duplicated and/or missing characters when
1636 low level console functions (such as gets) are used while
1637 interrupts are enabled (for example geli password prompt,
1638 mountroot prompt etc.). Disabling kbdmux(4) may help.
1641 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1642 kernel modules referencing any of the above need to be recompiled.
1643 Bump __FreeBSD_version to 800075.
1646 GEOM_PART has become the default partition slicer for storage devices,
1647 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1648 introduces some changes:
1650 MSDOS/EBR: the devices created from MSDOS extended partition entries
1651 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1652 to devices with offset-based names. fstabs may need to be modified.
1654 BSD: the "geometry does not match label" warning is harmless in most
1655 cases but it points to problems in file system misalignment with
1656 disk geometry. The "c" partition is now implicit, covers the whole
1657 top-level drive and cannot be (mis)used by users.
1659 General: Kernel dumps are now not allowed to be written to devices
1660 whose partition types indicate they are meant to be used for file
1661 systems (or, in case of MSDOS partitions, as something else than
1664 Most of these changes date approximately from 200812.
1667 The uscanner(4) driver has been removed from the kernel. This follows
1668 Linux removing theirs in 2.6 and making libusb the default interface
1669 (supported by sane).
1672 The multicast forwarding code has been cleaned up. netstat(1)
1673 only relies on KVM now for printing bandwidth upcall meters.
1674 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1675 ip6_mroute_mod respectively. The config(5) options for statically
1676 compiling this code remain the same, i.e. 'options MROUTING'.
1679 Support for the IFF_NEEDSGIANT network interface flag has been
1680 removed, which means that non-MPSAFE network device drivers are no
1681 longer supported. In particular, if_ar, if_sr, and network device
1682 drivers from the old (legacy) USB stack can no longer be built or
1686 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1687 a bunch of new language catalog files have also been added.
1688 This means that some common libc messages are now localized and
1689 they depend on the LC_MESSAGES environmental variable.
1692 The k8temp(4) driver has been renamed to amdtemp(4) since
1693 support for Family 10 and Family 11 CPU families was added.
1696 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1697 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1699 For kernel developers, the most important changes are that the
1700 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1701 and this lock has been downgraded to a non-recursive mutex.
1703 Transport protocols (UDP, Raw IP) are now responsible for filtering
1704 inbound multicast traffic according to group membership and source
1705 filters. The imo_multicast_filter() KPI exists for this purpose.
1706 Transports which do not use multicast (SCTP, TCP) already reject
1707 multicast by default. Forwarding and receive performance may improve
1708 as a mutex acquisition is no longer needed in the ip_input()
1709 low-level input path. in_addmulti() and in_delmulti() are shimmed
1710 to new KPIs which exist to support SSM in-kernel.
1712 For application developers, it is recommended that loopback of
1713 multicast datagrams be disabled for best performance, as this
1714 will still cause the lock to be taken for each looped-back
1715 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1716 be tuned to 0 to disable loopback by default; it defaults to 1
1717 to preserve the existing behaviour.
1719 For systems administrators, to obtain best performance with
1720 multicast reception and multiple groups, it is always recommended
1721 that a card with a suitably precise hash filter is used. Hash
1722 collisions will still result in the lock being taken within the
1723 transport protocol input path to check group membership.
1725 If deploying FreeBSD in an environment with IGMP snooping switches,
1726 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1727 enabled; this forces 224.0.0.0/24 group membership to be announced
1730 The size of 'struct igmpstat' has changed; netstat needs to be
1731 recompiled to reflect this.
1732 Bump __FreeBSD_version to 800070.
1735 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1736 updated to use it. This requires a buildworld/installworld in order to
1737 update the library and dependencies (usbconfig, etc). Its advisable to
1738 rebuild all ports which uses libusb. More specific directions are given
1739 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1740 libusb are no longer required and can be removed.
1743 A workaround is committed to allow the creation of System V shared
1744 memory segment of size > 2 GB on the 64-bit architectures.
1745 Due to a limitation of the existing ABI, the shm_segsz member
1746 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1747 wrong for large segments. Note that limits must be explicitly
1748 raised to allow such segments to be created.
1751 The layout of struct ifnet has changed, requiring a rebuild of all
1752 network device driver modules.
1755 The /dev handling for the new USB stack has changed, a
1756 buildworld/installworld is required for libusb20.
1759 The new USB2 stack has now been permanently moved in and all kernel and
1760 module names reverted to their previous values (eg, usb, ehci, ohci,
1761 ums, ...). The old usb stack can be compiled in by prefixing the name
1762 with the letter 'o', the old usb modules have been removed.
1763 Updating entry 20090216 for xorg and 20090215 for libmap may still
1767 The rc.conf(5) option if_up_delay has been renamed to
1768 defaultroute_delay to better reflect its purpose. If you have
1769 customized this setting in /etc/rc.conf you need to update it to
1773 xorg 7.4 wants to configure its input devices via hald which does not
1774 yet work with USB2. If the keyboard/mouse does not work in xorg then
1776 Option "AllowEmptyInput" "off"
1777 to your ServerLayout section. This will cause X to use the configured
1778 kbd and mouse sections from your xorg.conf.
1781 The GENERIC kernels for all architectures now default to the new USB2
1782 stack. No kernel config options or code have been removed so if a
1783 problem arises please report it and optionally revert to the old USB
1784 stack. If you are loading USB kernel modules or have a custom kernel
1785 that includes GENERIC then ensure that usb names are also changed over,
1786 eg uftdi -> usb2_serial_ftdi.
1788 Older programs linked against the ports libusb 0.1 need to be
1789 redirected to the new stack's libusb20. /etc/libmap.conf can
1791 # Map old usb library to new one for usb2 stack
1792 libusb-0.1.so.8 libusb20.so.1
1795 All USB ethernet devices now attach as interfaces under the name ueN
1796 (eg. ue0). This is to provide a predictable name as vendors often
1797 change usb chipsets in a product without notice.
1800 The ichsmb(4) driver has been changed to require SMBus slave
1801 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1802 All of the other SMBus controller drivers require left-justified
1803 slave addresses, so this change makes all the drivers provide the
1807 INET6 statistics (struct ip6stat) was updated.
1808 netstat(1) needs to be recompiled.
1811 NTFS has been removed from GENERIC kernel on amd64 to match
1812 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1813 will load ntfs.ko module automatically when NTFS support is
1814 actually needed, unless ntfs.ko is not installed or security
1815 level prohibits loading kernel modules. If either is the case,
1816 "options NTFS" has to be added into kernel config.
1819 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1820 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1821 800061. User space tools that rely on the size of struct tcpcb in
1822 tcp_var.h (e.g. sockstat) need to be recompiled.
1825 ng_tty(4) module updated to match the new TTY subsystem.
1826 Due to API change, user-level applications must be updated.
1827 New API support added to mpd5 CVS and expected to be present
1828 in next mpd5.3 release.
1831 With __FreeBSD_version 800060 the makefs tool is part of
1832 the base system (it was a port).
1835 The afdata and ifnet locks have been changed from mutexes to
1836 rwlocks, network modules will need to be re-compiled.
1839 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1840 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1841 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1842 architecture and 40 bytes on 64-bit architecture. The userland
1843 applications "arp" and "ndp" have been updated accordingly.
1844 The output from "netstat -r" shows only routing entries and
1845 none of the L2 information.
1848 __FreeBSD_version 800057 marks the switchover from the
1849 binary ath hal to source code. Users must add the line:
1851 options AH_SUPPORT_AR5416
1853 to their kernel config files when specifying:
1857 The ath_hal module no longer exists; the code is now compiled
1858 together with the driver in the ath module. It is now
1859 possible to tailor chip support (i.e. reduce the set of chips
1860 and thereby the code size); consult ath_hal(4) for details.
1863 __FreeBSD_version 800054 adds memory barriers to
1864 <machine/atomic.h>, new interfaces to ifnet to facilitate
1865 multiple hardware transmit queues for cards that support
1866 them, and a lock-less ring-buffer implementation to
1867 enable drivers to more efficiently manage queueing of
1871 A new version of ZFS (version 13) has been merged to -HEAD.
1872 This version has zpool attribute "listsnapshots" off by
1873 default, which means "zfs list" does not show snapshots,
1874 and is the same as Solaris behavior.
1877 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1880 The uhci, ohci, ehci and slhci USB Host controller drivers have
1881 been put into separate modules. If you load the usb module
1882 separately through loader.conf you will need to load the
1883 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1884 controller add the following to loader.conf:
1890 The ABI used by the PMC toolset has changed. Please keep
1891 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1895 atapci kernel module now includes only generic PCI ATA
1896 driver. AHCI driver moved to ataahci kernel module.
1897 All vendor-specific code moved into separate kernel modules:
1898 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1899 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1900 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1901 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1904 The TTY subsystem of the kernel has been replaced by a new
1905 implementation, which provides better scalability and an
1906 improved driver model. Most common drivers have been migrated to
1907 the new TTY subsystem, while others have not. The following
1908 drivers have not yet been ported to the new TTY layer:
1911 cy, digi, rc, rp, sio
1917 ng_h4, ng_tty, ppp, sl, snp
1919 Adding these drivers to your kernel configuration file shall
1920 cause compilation to fail.
1923 ntpd has been upgraded to 4.2.4p5.
1926 OpenSSH has been upgraded to 5.1p1.
1928 For many years, FreeBSD's version of OpenSSH preferred DSA
1929 over RSA for host and user authentication keys. With this
1930 upgrade, we've switched to the vendor's default of RSA over
1931 DSA. This may cause upgraded clients to warn about unknown
1932 host keys even for previously known hosts. Users should
1933 follow the usual procedure for verifying host keys before
1934 accepting the RSA key.
1936 This can be circumvented by setting the "HostKeyAlgorithms"
1937 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1940 Please note that the sequence of keys offered for
1941 authentication has been changed as well. You may want to
1942 specify IdentityFile in a different order to revert this
1946 The sio(4) driver has been removed from the i386 and amd64
1947 kernel configuration files. This means uart(4) is now the
1948 default serial port driver on those platforms as well.
1950 To prevent collisions with the sio(4) driver, the uart(4) driver
1951 uses different names for its device nodes. This means the
1952 onboard serial port will now most likely be called "ttyu0"
1953 instead of "ttyd0". You may need to reconfigure applications to
1954 use the new device names.
1956 When using the serial port as a boot console, be sure to update
1957 /boot/device.hints and /etc/ttys before booting the new kernel.
1958 If you forget to do so, you can still manually specify the hints
1959 at the loader prompt:
1961 set hint.uart.0.at="isa"
1962 set hint.uart.0.port="0x3F8"
1963 set hint.uart.0.flags="0x10"
1964 set hint.uart.0.irq="4"
1968 The gpt(8) utility has been removed. Use gpart(8) to partition
1972 The version that Linuxulator emulates was changed from 2.4.2
1973 to 2.6.16. If you experience any problems with Linux binaries
1974 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1975 if it fixes the problem contact emulation mailing list.
1978 ISDN4BSD (I4B) was removed from the src tree. You may need to
1979 update a your kernel configuration and remove relevant entries.
1982 I have checked in code to support multiple routing tables.
1983 See the man pages setfib(1) and setfib(2).
1984 This is a hopefully backwards compatible version,
1985 but to make use of it you need to compile your kernel
1986 with options ROUTETABLES=2 (or more up to 16).
1989 The 802.11 wireless support was redone to enable multi-bss
1990 operation on devices that are capable. The underlying device
1991 is no longer used directly but instead wlanX devices are
1992 cloned with ifconfig. This requires changes to rc.conf files.
1993 For example, change:
1994 ifconfig_ath0="WPA DHCP"
1997 ifconfig_wlan0="WPA DHCP"
1998 see rc.conf(5) for more details. In addition, mergemaster of
1999 /etc/rc.d is highly recommended. Simultaneous update of userland
2000 and kernel wouldn't hurt either.
2002 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
2003 modules were merged into the base wlan module. All references
2004 to these modules (e.g. in kernel config files) must be removed.
2007 psm(4) has gained write(2) support in native operation level.
2008 Arbitrary commands can be written to /dev/psm%d and status can
2009 be read back from it. Therefore, an application is responsible
2010 for status validation and error recovery. It is a no-op in
2011 other operation levels.
2014 Support for KSE threading has been removed from the kernel. To
2015 run legacy applications linked against KSE libmap.conf may
2016 be used. The following libmap.conf may be used to ensure
2017 compatibility with any prior release:
2019 libpthread.so.1 libthr.so.1
2020 libpthread.so.2 libthr.so.2
2021 libkse.so.3 libthr.so.3
2024 The layout of struct vmspace has changed. This affects libkvm
2025 and any executables that link against libkvm and use the
2026 kvm_getprocs() function. In particular, but not exclusively,
2027 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
2028 The effects are minimal, but it's advisable to upgrade world
2032 The latest em driver no longer has support in it for the
2033 82575 adapter, this is now moved to the igb driver. The
2034 split was done to make new features that are incompatible
2035 with older hardware easier to do.
2038 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
2039 likewise the kernel option is now GEOM_LINUX_LVM.
2042 The default NFS mount mode has changed from UDP to TCP for
2043 increased reliability. If you rely on (insecurely) NFS
2044 mounting across a firewall you may need to update your
2048 Belatedly note the addition of m_collapse for compacting
2052 The fts(3) structures have been changed to use adequate
2053 integer types for their members and so to be able to cope
2054 with huge file trees. The old fts(3) ABI is preserved
2055 through symbol versioning in libc, so third-party binaries
2056 using fts(3) should still work, although they will not take
2057 advantage of the extended types. At the same time, some
2058 third-party software might fail to build after this change
2059 due to unportable assumptions made in its source code about
2060 fts(3) structure members. Such software should be fixed
2061 by its vendor or, in the worst case, in the ports tree.
2062 FreeBSD_version 800015 marks this change for the unlikely
2063 case that a portable fix is impossible.
2066 To upgrade to -current after this date, you must be running
2067 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
2068 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
2071 The ADAPTIVE_GIANT kernel option has been retired because its
2072 functionality is the default now.
2075 The AT keyboard emulation of sunkbd(4) has been turned on
2076 by default. In order to make the special symbols of the Sun
2077 keyboards driven by sunkbd(4) work under X these now have
2078 to be configured the same way as Sun USB keyboards driven
2079 by ukbd(4) (which also does AT keyboard emulation), f.e.:
2081 Option "XkbLayout" "us"
2082 Option "XkbRules" "xorg"
2083 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
2086 It has been decided that it is desirable to provide ABI
2087 backwards compatibility to the FreeBSD 4/5/6 versions of the
2088 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
2089 broken with the introduction of PCI domain support (see the
2090 20070930 entry). Unfortunately, this required the ABI of
2091 PCIOCGETCONF to be broken again in order to be able to
2092 provide backwards compatibility to the old version of that
2093 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
2094 again. As for prominent ports this affects neither pciutils
2095 nor xorg-server this time, the hal port needs to be rebuilt
2099 The misnamed kthread_create() and friends have been renamed
2100 to kproc_create() etc. Many of the callers already
2101 used kproc_start()..
2102 I will return kthread_create() and friends in a while
2103 with implementations that actually create threads, not procs.
2104 Renaming corresponds with version 800002.
2113 Avoid using make -j when upgrading. While generally safe, there are
2114 sometimes problems using -j to upgrade. If your upgrade fails with
2115 -j, please try again without -j. From time to time in the past there
2116 have been problems using -j with buildworld and/or installworld. This
2117 is especially true when upgrading between "distant" versions (eg one
2118 that cross a major release boundary or several minor releases, or when
2119 several months have passed on the -current branch).
2121 Sometimes, obscure build problems are the result of environment
2122 poisoning. This can happen because the make utility reads its
2123 environment when searching for values for global variables. To run
2124 your build attempts in an "environmental clean room", prefix all make
2125 commands with 'env -i '. See the env(1) manual page for more details.
2127 When upgrading from one major version to another it is generally best
2128 to upgrade to the latest code in the currently installed branch first,
2129 then do an upgrade to the new branch. This is the best-tested upgrade
2130 path, and has the highest probability of being successful. Please try
2131 this approach before reporting problems with a major version upgrade.
2133 When upgrading a live system, having a root shell around before
2134 installing anything can help undo problems. Not having a root shell
2135 around can lead to problems if pam has changed too much from your
2136 starting point to allow continued authentication after the upgrade.
2140 When upgrading the boot ZFS pool to a new version, always follow
2143 1.) recompile and reinstall the ZFS boot loader and boot block
2144 (this is part of "make buildworld" and "make installworld")
2146 2.) update the ZFS boot block on your boot drive
2148 The following example updates the ZFS boot block on the first
2149 partition (freebsd-boot) of a GPT partitioned drive ad0:
2150 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
2152 Non-boot pools do not need these updates.
2156 If you are updating from a prior version of FreeBSD (even one just
2157 a few days old), you should follow this procedure. It is the most
2158 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
2160 make kernel-toolchain
2161 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
2162 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
2164 To test a kernel once
2165 ---------------------
2166 If you just want to boot a kernel once (because you are not sure
2167 if it works, or if you want to boot a known bad kernel to provide
2168 debugging information) run
2169 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
2170 nextboot -k testkernel
2172 To just build a kernel when you know that it won't mess you up
2173 --------------------------------------------------------------
2174 This assumes you are already running a CURRENT system. Replace
2175 ${arch} with the architecture of your machine (e.g. "i386",
2176 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
2178 cd src/sys/${arch}/conf
2179 config KERNEL_NAME_HERE
2180 cd ../compile/KERNEL_NAME_HERE
2185 If this fails, go to the "To build a kernel" section.
2187 To rebuild everything and install it on the current system.
2188 -----------------------------------------------------------
2189 # Note: sometimes if you are running current you gotta do more than
2190 # is listed here if you are upgrading from a really old current.
2192 <make sure you have good level 0 dumps>
2194 make kernel KERNCONF=YOUR_KERNEL_HERE
2196 <reboot in single user> [3]
2203 To cross-install current onto a separate partition
2204 --------------------------------------------------
2205 # In this approach we use a separate partition to hold
2206 # current's root, 'usr', and 'var' directories. A partition
2207 # holding "/", "/usr" and "/var" should be about 2GB in
2210 <make sure you have good level 0 dumps>
2213 make buildkernel KERNCONF=YOUR_KERNEL_HERE
2214 <maybe newfs current's root partition>
2215 <mount current's root partition on directory ${CURRENT_ROOT}>
2216 make installworld DESTDIR=${CURRENT_ROOT}
2217 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
2218 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
2219 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
2220 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
2221 <reboot into current>
2222 <do a "native" rebuild/install as described in the previous section>
2223 <maybe install compatibility libraries from ports/misc/compat*>
2227 To upgrade in-place from stable to current
2228 ----------------------------------------------
2229 <make sure you have good level 0 dumps>
2231 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
2233 <reboot in single user> [3]
2240 Make sure that you've read the UPDATING file to understand the
2241 tweaks to various things you need. At this point in the life
2242 cycle of current, things change often and you are on your own
2243 to cope. The defaults can also change, so please read ALL of
2244 the UPDATING entries.
2246 Also, if you are tracking -current, you must be subscribed to
2247 freebsd-current@freebsd.org. Make sure that before you update
2248 your sources that you have read and understood all the recent
2249 messages there. If in doubt, please track -stable which has
2250 much fewer pitfalls.
2252 [1] If you have third party modules, such as vmware, you
2253 should disable them at this point so they don't crash your
2256 [3] From the bootblocks, boot -s, and then do
2261 adjkerntz -i # if CMOS is wall time
2262 Also, when doing a major release upgrade, it is required that
2263 you boot into single user mode to do the installworld.
2265 [4] Note: This step is non-optional. Failure to do this step
2266 can result in a significant reduction in the functionality of the
2267 system. Attempting to do it by hand is not recommended and those
2268 that pursue this avenue should read this file carefully, as well
2269 as the archives of freebsd-current and freebsd-hackers mailing lists
2270 for potential gotchas. The -U option is also useful to consider.
2271 See mergemaster(8) for more information.
2273 [5] Usually this step is a noop. However, from time to time
2274 you may need to do this if you get unknown user in the following
2275 step. It never hurts to do it all the time. You may need to
2276 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2277 install) after the buildworld before this step if you last updated
2278 from current before 20130425 or from -stable before 20130430.
2280 [6] This only deletes old files and directories. Old libraries
2281 can be deleted by "make delete-old-libs", but you have to make
2282 sure that no program is using those libraries anymore.
2284 [8] In order to have a kernel that can run the 4.x binaries needed to
2285 do an installworld, you must include the COMPAT_FREEBSD4 option in
2286 your kernel. Failure to do so may leave you with a system that is
2287 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2288 required to run the 5.x binaries on more recent kernels. And so on
2289 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2291 Make sure that you merge any new devices from GENERIC since the
2292 last time you updated your kernel config file.
2294 [9] When checking out sources, you must include the -P flag to have
2295 cvs prune empty directories.
2297 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2298 "?=" instead of the "=" assignment operator, so that buildworld can
2299 override the CPUTYPE if it needs to.
2301 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2302 not on the command line, or in /etc/make.conf. buildworld will
2303 warn if it is improperly defined.
2306 This file contains a list, in reverse chronological order, of major
2307 breakages in tracking -current. It is not guaranteed to be a complete
2308 list of such breakages, and only contains entries since October 10, 2007.
2309 If you need to see UPDATING entries from before that date, you will need
2310 to fetch an UPDATING file from an older FreeBSD release.
2312 Copyright information:
2314 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2316 Redistribution, publication, translation and use, with or without
2317 modification, in full or in part, in any form or format of this
2318 document are permitted without further permission from the author.
2320 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2321 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2322 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2323 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2324 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2325 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2326 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2327 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2328 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2329 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2330 POSSIBILITY OF SUCH DAMAGE.
2332 Contact Warner Losh if you have any questions about your use of