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