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 On i386 and amd64 systems, the onifconsole flag is now set by default
21 in /etc/ttys for ttyu0. This causes ttyu0 to be automatically enabled
22 as a login TTY if it is set in the bootloader as an active kernel
23 console. No changes in behavior should result otherwise. To revert to
24 the previous behavior, set ttyu0 to "off" in /etc/ttys.
27 Clang and llvm have been upgraded to 3.4.1 release.
30 Clang and llvm have been upgraded to 3.4 release.
33 If a Makefile in a tests/ directory was auto-generating a Kyuafile
34 instead of providing an explicit one, this would prevent such
35 Makefile from providing its own Kyuafile in the future during
36 NO_CLEAN builds. This has been fixed in the Makefiles but manual
37 intervention is needed to clean an objdir if you use NO_CLEAN:
38 # find /usr/obj -name Kyuafile | xargs rm -f
41 OpenSSH will now ignore errors caused by kernel lacking of Capsicum
42 capability mode support. Please note that enabling the feature in
43 kernel is still highly recommended.
46 OpenSSH is now built with sandbox support, and will use sandbox as
47 the default privilege separation method. This requires Capsicum
48 capability mode support in kernel.
51 The nve(4) driver for NVIDIA nForce MCP Ethernet adapters has
52 been deprecated and will not be part of FreeBSD 11.0 and later
53 releases. If you use this driver, please consider switching to
54 the nfe(4) driver instead.
60 The behavior of gss_pseudo_random() for the krb5 mechanism
61 has changed, for applications requesting a longer random string
62 than produced by the underlying enctype's pseudo-random() function.
63 In particular, the random string produced from a session key of
64 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
65 be different at the 17th octet and later, after this change.
66 The counter used in the PRF+ construction is now encoded as a
67 big-endian integer in accordance with RFC 4402.
68 __FreeBSD_version is bumped to 1000701.
71 The WITHOUT_ATF build knob has been removed and its functionality
72 has been subsumed into the more generic WITHOUT_TESTS. If you were
73 using the former to disable the build of the ATF libraries, you
74 should change your settings to use the latter.
77 The default version of mtree is nmtree which is obtained from
78 NetBSD. The output is generally the same, but may vary
79 slightly. If you found you need identical output adding
80 "-F freebsd9" to the command line should do the trick. For the
81 time being, the old mtree is available as fmtree.
84 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
85 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
86 1.1.4_8 and verify bsdyml not linked in, before running "make
88 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
90 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
93 The rc.d/jail script has been updated to support jail(8)
94 configuration file. The "jail_<jname>_*" rc.conf(5) variables
95 for per-jail configuration are automatically converted to
96 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
97 This is transparently backward compatible. See below about some
98 incompatibilities and rc.conf(5) manual page for more details.
100 These variables are now deprecated in favor of jail(8) configuration
101 file. One can use "rc.d/jail config <jname>" command to generate
102 a jail(8) configuration file in /var/run/jail.<jname>.conf without
103 running the jail(8) utility. The default pathname of the
104 configuration file is /etc/jail.conf and can be specified by
105 using $jail_conf or $jail_<jname>_conf variables.
107 Please note that jail_devfs_ruleset accepts an integer at
108 this moment. Please consider to rewrite the ruleset name
112 BIND has been removed from the base system. If all you need
113 is a local resolver, simply enable and start the local_unbound
114 service instead. Otherwise, several versions of BIND are
115 available in the ports tree. The dns/bind99 port is one example.
117 With this change, nslookup(1) and dig(1) are no longer in the base
118 system. Users should instead use host(1) and drill(1) which are
119 in the base system. Alternatively, nslookup and dig can
120 be obtained by installing the dns/bind-tools port.
123 With the addition of unbound(8), a new unbound user is now
124 required during installworld. "mergemaster -p" can be used to
125 add the user prior to installworld, as documented in the handbook.
128 OpenSSH is now built with DNSSEC support, and will by default
129 silently trust signed SSHFP records. This can be controlled with
130 the VerifyHostKeyDNS client configuration setting. DNSSEC support
131 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
134 The GNU Compiler Collection and C++ standard library (libstdc++)
135 are no longer built by default on platforms where clang is the system
136 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
140 The PROCDESC kernel option is now part of the GENERIC kernel
141 configuration and is required for the rwhod(8) to work.
142 If you are using custom kernel configuration, you should include
146 The API and ABI related to the Capsicum framework was modified
147 in backward incompatible way. The userland libraries and programs
148 have to be recompiled to work with the new kernel. This includes the
149 following libraries and programs, but the whole buildworld is
150 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
151 kdump, procstat, rwho, rwhod, uniq.
154 AES-NI intrinsic support has been added to gcc. The AES-NI module
155 has been updated to use this support. A new gcc is required to build
156 the aesni module on both i386 and amd64.
159 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
160 Thus "device padlock_rng" and "device rdrand_rng" should be
161 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
164 WITH_ICONV has been split into two feature sets. WITH_ICONV now
165 enables just the iconv* functionality and is now on by default.
166 WITH_LIBICONV_COMPAT enables the libiconv api and link time
167 compatability. Set WITHOUT_ICONV to build the old way.
168 If you have been using WITH_ICONV before, you will very likely
169 need to turn on WITH_LIBICONV_COMPAT.
172 INVARIANTS option now enables DEBUG for code with OpenSolaris and
173 Illumos origin, including ZFS. If you have INVARIANTS in your
174 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
176 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
177 locks if WITNESS option was set. Because that generated a lot of
178 witness(9) reports and all of them were believed to be false
179 positives, this is no longer done. New option OPENSOLARIS_WITNESS
180 can be used to achieve the previous behavior.
183 Timer values in IPv6 data structures now use time_uptime instead
184 of time_second. Although this is not a user-visible functional
185 change, userland utilities which directly use them---ndp(8),
186 rtadvd(8), and rtsold(8) in the base system---need to be updated
190 find -delete can now delete the pathnames given as arguments,
191 instead of only files found below them or if the pathname did
192 not contain any slashes. Formerly, the following error message
195 find: -delete: <path>: relative path potentially not safe
197 Deleting the pathnames given as arguments can be prevented
198 without error messages using -mindepth 1 or by changing
199 directory and passing "." as argument to find. This works in the
200 old as well as the new version of find.
203 Behavior of devfs rules path matching has been changed.
204 Pattern is now always matched against fully qualified devfs
205 path and slash characters must be explicitly matched by
206 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
207 subdirectories must be reviewed.
210 The default ARM ABI has changed to the ARM EABI. The old ABI is
211 incompatible with the ARM EABI and all programs and modules will
212 need to be rebuilt to work with a new kernel.
214 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
216 NOTE: Support for the old ABI will be removed in the future and
217 users are advised to upgrade.
220 pkg_install has been disconnected from the build if you really need it
221 you should add WITH_PKGTOOLS in your src.conf(5).
224 Most of network statistics structures were changed to be able
225 keep 64-bits counters. Thus all tools, that work with networking
226 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
229 Fix targets that run multiple make's to use && rather than ;
230 so that subsequent steps depend on success of previous.
232 NOTE: if building 'universe' with -j* on stable/8 or stable/9
233 it would be better to start the build using bmake, to avoid
234 overloading the machine.
237 Fix a bug that allowed a tracing process (e.g. gdb) to write
238 to a memory-mapped file in the traced process's address space
239 even if neither the traced process nor the tracing process had
240 write access to that file.
243 CVS has been removed from the base system. An exact copy
244 of the code is available from the devel/cvs port.
247 Some people report the following error after the switch to bmake:
249 make: illegal option -- J
250 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
252 *** [buildworld] Error code 2
254 this likely due to an old instance of make in
255 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
256 which src/Makefile will use that blindly, if it exists, so if
257 you see the above error:
259 rm -rf `make -V MAKEPATH`
264 Use bmake by default.
265 Whereas before one could choose to build with bmake via
266 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
267 make. The goal is to remove these knobs for 10-RELEASE.
269 It is worth noting that bmake (like gmake) treats the command
270 line as the unit of failure, rather than statements within the
271 command line. Thus '(cd some/where && dosomething)' is safer
272 than 'cd some/where; dosomething'. The '()' allows consistent
273 behavior in parallel build.
276 Fix a bug that allows NFS clients to issue READDIR on files.
279 The WITHOUT_IDEA option has been removed because
280 the IDEA patent expired.
283 The sysctl which controls TRIM support under ZFS has been renamed
284 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
288 The mergemaster command now uses the default MAKEOBJDIRPREFIX
289 rather than creating it's own in the temporary directory in
290 order allow access to bootstrapped versions of tools such as
291 install and mtree. When upgrading from version of FreeBSD where
292 the install command does not support -l, you will need to
293 install a new mergemaster command if mergemaster -p is required.
294 This can be accomplished with the command (cd src/usr.sbin/mergemaster
298 Legacy ATA stack, disabled and replaced by new CAM-based one since
299 FreeBSD 9.0, completely removed from the sources. Kernel modules
300 atadisk and atapi*, user-level tools atacontrol and burncd are
301 removed. Kernel option `options ATA_CAM` is now permanently enabled
305 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
306 and socketpair(2). Software, in particular Kerberos, may
307 automatically detect and use these during building. The resulting
308 binaries will not work on older kernels.
311 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
312 information, see the respective 20130304 entry).
315 Recent commits to callout(9) changed the size of struct callout,
316 so the KBI is probably heavily disturbed. Also, some functions
317 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
318 by macros. Every kernel module using it won't load, so rebuild
321 The ctl device has been re-enabled in GENERIC for i386 and amd64,
322 but does not initialize by default (because of the new CTL_DISABLE
323 option) to save memory. To re-enable it, remove the CTL_DISABLE
324 option from the kernel config file or set kern.cam.ctl.disable=0
325 in /boot/loader.conf.
328 The ctl device has been disabled in GENERIC for i386 and amd64.
329 This was done due to the extra memory being allocated at system
330 initialisation time by the ctl driver which was only used if
331 a CAM target device was created. This makes a FreeBSD system
332 unusable on 128MB or less of RAM.
335 A new compression method (lz4) has been merged to -HEAD. Please
336 refer to zpool-features(7) for more information.
338 Please refer to the "ZFS notes" section of this file for information
339 on upgrading boot ZFS pools.
342 A BSD-licensed patch(1) variant has been added and is installed
343 as bsdpatch, being the GNU version the default patch.
344 To inverse the logic and use the BSD-licensed one as default,
345 while having the GNU version installed as gnupatch, rebuild
346 and install world with the WITH_BSD_PATCH knob set.
349 Due to the use of the new -l option to install(1) during build
350 and install, you must take care not to directly set the INSTALL
351 make variable in your /etc/make.conf, /etc/src.conf, or on the
352 command line. If you wish to use the -C flag for all installs
353 you may be able to add INSTALL+=-C to /etc/make.conf or
357 The install(1) option -M has changed meaning and now takes an
358 argument that is a file or path to append logs to. In the
359 unlikely event that -M was the last option on the command line
360 and the command line contained at least two files and a target
361 directory the first file will have logs appended to it. The -M
362 option served little practical purpose in the last decade so its
363 use is expected to be extremely rare.
366 After switching to Clang as the default compiler some users of ZFS
367 on i386 systems started to experience stack overflow kernel panics.
368 Please consider using 'options KSTACK_PAGES=4' in such configurations.
371 GEOM_LABEL now mangles label names read from file system metadata.
372 Mangling affect labels containing spaces, non-printable characters,
373 '%' or '"'. Device names in /etc/fstab and other places may need to
377 By default, only the 10 most recent kernel dumps will be saved. To
378 restore the previous behaviour (no limit on the number of kernel dumps
379 stored in the dump directory) add the following line to /etc/rc.conf:
384 With the addition of auditdistd(8), a new auditdistd user is now
385 required during installworld. "mergemaster -p" can be used to
386 add the user prior to installworld, as documented in the handbook.
389 The sin6_scope_id member variable in struct sockaddr_in6 is now
390 filled by the kernel before passing the structure to the userland via
391 sysctl or routing socket. This means the KAME-specific embedded scope
392 id in sin6_addr.s6_addr[2] is always cleared in userland application.
393 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
394 __FreeBSD_version is bumped to 1000025.
397 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
398 This means that the world and kernel will be compiled with clang
399 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
400 and /usr/bin/cpp. To disable this behavior and revert to building
401 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
402 of current may need to bootstrap WITHOUT_CLANG first if the clang
403 build fails (its compatibility window doesn't extend to the 9 stable
407 The IPFIREWALL_FORWARD kernel option has been removed. Its
408 functionality now turned on by default.
411 The ZERO_COPY_SOCKET kernel option has been removed and
412 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
413 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
414 mechanism which is not safe and may result in kernel crashes.
415 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
416 driver supports disposeable external page sized mbuf storage.
417 Proper replacements for both zero-copy mechanisms are under
418 consideration and will eventually lead to complete removal
419 of the two kernel options.
422 The IPv4 network stack has been converted to network byte
423 order. The following modules need to be recompiled together
424 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
425 pf(4), ipfw(4), ng_ipfw(4), stf(4).
428 Support for non-MPSAFE filesystems was removed from VFS. The
429 VFS_VERSION was bumped, all filesystem modules shall be
433 All the non-MPSAFE filesystems have been disconnected from
434 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
435 portalfs, smbfs, xfs.
438 The interface cloning API and ABI has changed. The following
439 modules need to be recompiled together with kernel:
440 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
441 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
442 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
445 The sdhci driver was split in two parts: sdhci (generic SD Host
446 Controller logic) and sdhci_pci (actual hardware driver).
447 No kernel config modifications are required, but if you
448 load sdhc as a module you must switch to sdhci_pci instead.
451 Import the FUSE kernel and userland support into base system.
454 The GNU sort(1) program has been removed since the BSD-licensed
455 sort(1) has been the default for quite some time and no serious
456 problems have been reported. The corresponding WITH_GNU_SORT
460 The pfil(9) API/ABI for AF_INET family has been changed. Packet
461 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
465 The net80211(4) ABI has been changed to allow for improved driver
466 PS-POLL and power-save support. All wireless drivers need to be
467 recompiled to work with the new kernel.
470 The random(4) support for the VIA hardware random number
471 generator (`PADLOCK') is no longer enabled unconditionally.
472 Add the padlock_rng device in the custom kernel config if
473 needed. The GENERIC kernels on i386 and amd64 do include the
474 device, so the change only affects the custom kernel
478 The pf(4) packet filter ABI has been changed. pfctl(8) and
479 snmp_pf module need to be recompiled to work with new kernel.
482 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
483 to -HEAD. Pools that have empty_bpobj in active state can not be
484 imported read-write with ZFS implementations that do not support
485 this feature. For more information read the zpool-features(5)
489 The sparc64 ZFS loader has been changed to no longer try to auto-
490 detect ZFS providers based on diskN aliases but now requires these
491 to be explicitly listed in the OFW boot-device environment variable.
494 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
495 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
496 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
499 The following sysctls and tunables have been renamed for consistency
500 with other variables:
501 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
502 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
505 The sort utility has been replaced with BSD sort. For now, GNU sort
506 is also available as "gnusort" or the default can be set back to
507 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
508 installed as "bsdsort".
511 A new version of ZFS (pool version 5000) has been merged to -HEAD.
512 Starting with this version the old system of ZFS pool versioning
513 is superseded by "feature flags". This concept enables forward
514 compatibility against certain future changes in functionality of ZFS
515 pools. The first read-only compatible "feature flag" for ZFS pools
516 is named "com.delphix:async_destroy". For more information
517 read the new zpool-features(5) manual page.
518 Please refer to the "ZFS notes" section of this file for information
519 on upgrading boot ZFS pools.
522 The malloc(3) implementation embedded in libc now uses sources imported
523 as contrib/jemalloc. The most disruptive API change is to
524 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
525 delete it prior to installworld, and optionally re-create it using the
526 new format after rebooting. See malloc.conf(5) for details
527 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
531 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
532 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
533 now spelled mips. This is to aid compatibility with third-party
534 software that expects this naming scheme in uname(3). Little-endian
535 settings are unchanged. If you are updating a big-endian mips64 machine
536 from before this change, you may need to set MACHINE_ARCH=mips64 in
537 your environment before the new build system will recognize your machine.
540 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
544 Now unix domain sockets behave "as expected" on nullfs(5). Previously
545 nullfs(5) did not pass through all behaviours to the underlying layer,
546 as a result if we bound to a socket on the lower layer we could connect
547 only to the lower path; if we bound to the upper layer we could connect
548 only to the upper path. The new behavior is one can connect to both the
549 lower and the upper paths regardless what layer path one binds to.
552 The getifaddrs upgrade path broken with 20111215 has been restored.
553 If you have upgraded in between 20111215 and 20120209 you need to
554 recompile libc again with your kernel. You still need to recompile
555 world to be able to configure CARP but this restriction already
559 The set_rcvar() function has been removed from /etc/rc.subr. All
560 base and ports rc.d scripts have been updated, so if you have a
561 port installed with a script in /usr/local/etc/rc.d you can either
562 hand-edit the rcvar= line, or reinstall the port.
564 An easy way to handle the mass-update of /etc/rc.d:
565 rm /etc/rc.d/* && mergemaster -i
568 panic(9) now stops other CPUs in the SMP systems, disables interrupts
569 on the current CPU and prevents other threads from running.
570 This behavior can be reverted using the kern.stop_scheduler_on_panic
572 The new behavior can be incompatible with kern.sync_on_panic.
575 The carp(4) facility has been changed significantly. Configuration
576 of the CARP protocol via ifconfig(8) has changed, as well as format
577 of CARP events submitted to devd(8) has changed. See manual pages
578 for more information. The arpbalance feature of carp(4) is currently
579 not supported anymore.
581 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
582 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
583 need to be recompiled.
586 The acpi_wmi(4) status device /dev/wmistat has been renamed to
590 The option VFS_ALLOW_NONMPSAFE option has been added in order to
591 explicitely support non-MPSAFE filesystems.
592 It is on by default for all supported platform at this present
596 The broken amd(4) driver has been replaced with esp(4) in the amd64,
597 i386 and pc98 GENERIC kernel configuration files.
600 sysinstall has been removed
603 The stable/9 branch created in subversion. This corresponds to the
604 RELENG_9 branch in CVS.
607 This commit modifies vfs_register() so that it uses a hash
608 calculation to set vfc_typenum, which is enabled by default.
609 The first time a system is booted after this change, the
610 vfc_typenum values will change for all file systems. The
611 main effect of this is a change to the NFS server file handles
612 for file systems that use vfc_typenum in their fsid, such as ZFS.
613 It will, however, prevent vfc_typenum from changing when file
614 systems are loaded in a different order for subsequent reboots.
615 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
616 until you are ready to remount all NFS clients after a reboot.
619 Bump the shared library version numbers for libraries that
620 do not use symbol versioning, have changed the ABI compared
621 to stable/8 and which shared library version was not bumped.
622 Done as part of 9.0-RELEASE cycle.
625 During the merge of Capsicum features, the fget(9) KPI was modified.
626 This may require the rebuilding of out-of-tree device drivers --
627 issues have been reported specifically with the nVidia device driver.
628 __FreeBSD_version is bumped to 900041.
630 Also, there is a period between 20110811 and 20110814 where the
631 special devices /dev/{stdin,stdout,stderr} did not work correctly.
632 Building world from a kernel during that window may not work.
635 The packet filter (pf) code has been updated to OpenBSD 4.5.
636 You need to update userland tools to be in sync with kernel.
637 This update breaks backward compatibility with earlier pfsync(4)
638 versions. Care must be taken when updating redundant firewall setups.
641 The following sysctls and tunables are retired on x86 platforms:
643 machdep.hlt_logical_cpus
644 The following sysctl is retired:
645 machdep.hyperthreading_allowed
646 The sysctls were supposed to provide a way to dynamically offline and
647 online selected CPUs on x86 platforms, but the implementation has not
648 been reliable especially with SCHED_ULE scheduler.
649 machdep.hyperthreading_allowed tunable is still available to ignore
650 hyperthreading CPUs at OS level.
651 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
652 where X is an APIC ID of a CPU. Be advised, though, that disabling
653 CPUs in non-uniform fashion will result in non-uniform topology and
654 may lead to sub-optimal system performance with SCHED_ULE, which is
658 cpumask_t type is retired and cpuset_t is used in order to describe
662 Changes to ifconfig(8) for dynamic address family detection mandate
663 that you are running a kernel of 20110525 or later. Make sure to
664 follow the update procedure to boot a new kernel before installing
668 Support for sun4v architecture is officially dropped
671 Several KPI breaking changes have been committed to the mii(4) layer,
672 the PHY drivers and consequently some Ethernet drivers using mii(4).
673 This means that miibus.ko and the modules of the affected Ethernet
674 drivers need to be recompiled.
676 Note to kernel developers: Given that the OUI bit reversion problem
677 was fixed as part of these changes all mii(4) commits related to OUIs,
678 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
679 handling, no longer can be merged verbatim to stable/8 and previous
683 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
684 into their kernel configurations along with 'device pci'.
687 The default NFS client is now the new NFS client, so fstype "newnfs"
688 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
689 Although mounts via fstype "nfs" will usually work without userland
690 changes, it is recommended that the mount(8) and mount_nfs(8)
691 commands be rebuilt from sources and that a link to mount_nfs called
692 mount_oldnfs be created. The new client is compiled into the
693 kernel with "options NFSCL" and this is needed for diskless root
694 file systems. The GENERIC kernel configs have been changed to use
695 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
696 To use the regular/old client, you can "mount -t oldnfs ...". For
697 a diskless root file system, you must also include a line like:
699 vfs.root.mountfrom="oldnfs:"
701 in the boot/loader.conf on the root fs on the NFS server to make
702 a diskless root fs use the old client.
705 The GENERIC kernels for all architectures now default to the new
706 CAM-based ATA stack. It means that all legacy ATA drivers were
707 removed and replaced by respective CAM drivers. If you are using
708 ATA device names in /etc/fstab or other places, make sure to update
709 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
710 where 'Y's are the sequential numbers starting from zero for each type
711 in order of detection, unless configured otherwise with tunables,
712 see cam(4)). There will be symbolic links created in /dev/ to map
713 old adX devices to the respective adaY. They should provide basic
714 compatibility for file systems mounting in most cases, but they do
715 not support old user-level APIs and do not have respective providers
716 in GEOM. Consider using updated management tools with new device names.
718 It is possible to load devices ahci, ata, siis and mvs as modules,
719 but option ATA_CAM should remain in kernel configuration to make ata
720 module work as CAM driver supporting legacy ATA controllers. Device ata
721 still can be used in modular fashion (atacore + ...). Modules atadisk
722 and atapi* are not used and won't affect operation in ATA_CAM mode.
723 Note that to use CAM-based ATA kernel should include CAM devices
724 scbus, pass, da (or explicitly ada), cd and optionally others. All of
725 them are parts of the cam module.
727 ataraid(4) functionality is now supported by the RAID GEOM class.
728 To use it you can load geom_raid kernel module and use graid(8) tool
729 for management. Instead of /dev/arX device names, use /dev/raid/rX.
731 No kernel config options or code have been removed, so if a problem
732 arises, please report it and optionally revert to the old ATA stack.
733 In order to do it you can remove from the kernel config:
738 , and instead add back:
739 device atadisk # ATA disk drives
740 device ataraid # ATA RAID drives
741 device atapicd # ATAPI CDROM drives
742 device atapifd # ATAPI floppy drives
743 device atapist # ATAPI tape drives
746 The default NFS server has been changed to the new server, which
747 was referred to as the experimental server. If you need to switch
748 back to the old NFS server, you must now put the "-o" option on
749 both the mountd and nfsd commands. This can be done using the
750 mountd_flags and nfs_server_flags rc.conf variables until an
751 update to the rc scripts is committed, which is coming soon.
754 The GNU Objective-C runtime library (libobjc), and other Objective-C
755 related components have been removed from the base system. If you
756 require an Objective-C library, please use one of the available ports.
759 ath(4) has been split into bus- and device- modules. if_ath contains
760 the HAL, the TX rate control and the network device code. if_ath_pci
761 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
762 contains the AHB glue. Users need to load both if_ath_pci and if_ath
763 in order to use ath on everything else.
765 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
766 need to load if_ath and if_ath_pci for ath(4) operation.
769 As part of the replacement of sysinstall, the process of building
770 release media has changed significantly. For details, please re-read
771 release(7), which has been updated to reflect the new build process.
774 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
775 is the last available version under GPLv2. It brings a number of new
776 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
777 4.1 and SSE 4.2), better support for powerpc64, a number of new
778 directives, and lots of other small improvements. See the ChangeLog
779 file in contrib/binutils for the full details.
782 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
783 compliant, and will now use half of hash for authentication.
784 This will break interoperability with all stacks (including all
785 actual FreeBSD versions) who implement
786 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
788 The only workaround with such peers is to use another HMAC
789 algorithm for IPsec ("phase 2") authentication.
792 Remove the uio_yield prototype and symbol. This function has
793 been misnamed since it was introduced and should not be
794 globally exposed with this name. The equivalent functionality
795 is now available using kern_yield(curthread->td_user_pri).
796 The function remains undocumented.
799 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
800 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
801 for scalar sysctls is defined but disabled. Code that needs
802 UQUAD to pass the type checking that must compile on older
803 systems where the define is not present can check against
804 __FreeBSD_version >= 900030.
806 The system dialog(1) has been replaced with a new version previously
807 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
808 with the previous version, but the libdialog associated with it has
809 a largely incompatible API. As such, the original version of libdialog
810 will be kept temporarily as libodialog, until its base system consumers
811 are replaced or updated. Bump __FreeBSD_version to 900030.
814 If you are trying to run make universe on a -stable system, and you get
815 the following warning:
816 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
817 unknown. config(8) likely too old."
818 or something similar to it, then you must upgrade your -stable system
819 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
820 stable/8) or build the config from the latest stable/8 branch and
821 install it on your system.
823 Prior to this date, building a current universe on 8-stable system from
824 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
825 error in the first kernel build phase. A new config on those old
826 systems will fix that problem for older versions of -current.
829 The TCP stack has been modified to allow Khelp modules to interact with
830 it via helper hook points and store per-connection data in the TCP
831 control block. Bump __FreeBSD_version to 900029. User space tools that
832 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
836 Generic IEEE 802.3 annex 31B full duplex flow control support has been
837 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
838 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
839 to take advantage of it instead of using custom implementations. This
840 means that these drivers now no longer unconditionally advertise
841 support for flow control but only do so if flow control is a selected
842 media option. This was implemented in the generic support that way in
843 order to allow flow control to be switched on and off via ifconfig(8)
844 with the PHY specific default to typically off in order to protect
845 from unwanted effects. Consequently, if you used flow control with
846 one of the above mentioned drivers you now need to explicitly enable
848 ifconfig bge0 media auto mediaopt flowcontrol
850 Along with the above mentioned changes generic support for setting
851 1000baseT master mode also has been added and brgphy(4), ciphy(4),
852 e1000phy(4) as well as ip1000phy(4) have been converted to take
853 advantage of it. This means that these drivers now no longer take the
854 link0 parameter for selecting master mode but the master media option
855 has to be used instead, for example like in the following:
856 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
858 Selection of master mode now is also available with all other PHY
859 drivers supporting 1000baseT.
862 The TCP stack has received a significant update to add support for
863 modularised congestion control and generally improve the clarity of
864 congestion control decisions. Bump __FreeBSD_version to 900025. User
865 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
866 sockstat) need to be recompiled.
869 The man(1) utility has been replaced by a new version that no longer
870 uses /etc/manpath.config. Please consult man.conf(5) for how to
871 migrate local entries to the new format.
874 The copyright strings printed by login(1) and sshd(8) at the time of a
875 new connection have been removed to follow other operating systems and
879 A workaround for a fixed ld bug has been removed in kernel code,
880 so make sure that your system ld is built from sources after
881 revision 210245 from 2010-07-19 (r211583 if building head kernel
882 on stable/8, r211584 for stable/7; both from 2010-08-21).
883 A symptom of incorrect ld version is different addresses for
884 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
887 The $ipv6_prefer variable in rc.conf(5) has been split into
888 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
890 The $ip6addrctl_policy is a variable to choose a pre-defined
891 address selection policy set by ip6addrctl(8). A value
892 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
895 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
896 flag (see an entry of 20090926) is set on an interface with no
897 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
898 security reason. If you want IPv6 link-local address on all
899 interfaces by default, set this to "YES".
901 The old ipv6_prefer="YES" is equivalent to
902 ipv6_activate_all_interfaces="YES" and
903 ip6addrctl_policy="ipv6_prefer".
906 DTrace has grown support for userland tracing. Due to this, DTrace is
907 now i386 and amd64 only.
908 dtruss(1) is now installed by default on those systems and a new
909 kernel module is needed for userland tracing: fasttrap.
910 No changes to your kernel config file are necessary to enable
911 userland tracing, but you might consider adding 'STRIP=' and
912 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
913 to have informative userland stack traces in DTrace (ustack).
916 The acpi_aiboost(4) driver has been removed in favor of the new
917 aibs(4) driver. You should update your kernel configuration file.
920 BSD grep has been imported to the base system and it is built by
921 default. It is completely BSD licensed, highly GNU-compatible, uses
922 less memory than its GNU counterpart and has a small codebase.
923 However, it is slower than its GNU counterpart, which is mostly
924 noticeable for larger searches, for smaller ones it is measurable
925 but not significant. The reason is complex, the most important factor
926 is that we lack a modern and efficient regex library and GNU
927 overcomes this by optimizing the searches internally. Future work
928 on improving the regex performance is planned, for the meantime,
929 users that need better performance, can build GNU grep instead by
930 setting the WITH_GNU_GREP knob.
933 Due to the import of powerpc64 support, all existing powerpc kernel
934 configuration files must be updated with a machine directive like this:
935 machine powerpc powerpc
937 In addition, an updated config(8) is required to build powerpc kernels
941 A new version of ZFS (version 15) has been merged to -HEAD.
942 This version uses a python library for the following subcommands:
943 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
944 For full functionality of these commands the following port must
945 be installed: sysutils/py-zfs
948 'vm_page's are now hashed by physical address to an array of mutexes.
949 Currently this is only used to serialize access to hold_count. Over
950 time the page queue mutex will be peeled away. This changes the size
951 of pmap on every architecture. And requires all callers of vm_page_hold
952 and vm_page_unhold to be updated.
955 WITH_CTF can now be specified in src.conf (not recommended, there
956 are some problems with static executables), make.conf (would also
957 affect ports which do not use GNU make and do not override the
958 compile targets) or in the kernel config (via "makeoptions
960 When WITH_CTF was specified there before this was silently ignored,
961 so make sure that WITH_CTF is not used in places which could lead
962 to unwanted behavior.
965 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
966 to allow 32-bit compatibility on non-x86 platforms. All kernel
967 configurations on amd64 and ia64 platforms using these options must
968 be modified accordingly.
971 The utmp user accounting database has been replaced with utmpx,
972 the user accounting interface standardized by POSIX.
973 Unfortunately the semantics of utmp and utmpx don't match,
974 making it practically impossible to support both interfaces.
975 The user accounting database is used by tools like finger(1),
976 last(1), talk(1), w(1) and ac(8).
978 All applications in the base system use utmpx. This means only
979 local binaries (e.g. from the ports tree) may still use these
980 utmp database files. These applications must be rebuilt to make
983 After the system has been upgraded, it is safe to remove the old
984 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
985 assuming their contents is of no importance anymore. Old wtmp
986 databases can only be used by last(1) and ac(8) after they have
987 been converted to the new format using wtmpcvt(1).
990 Introduce the kernel thread "deadlock resolver" (which can be enabled
991 via the DEADLKRES option, see NOTES for more details) and the
992 sleepq_type() function for sleepqueues.
995 The rc.firewall and rc.firewall6 were unified, and
996 rc.firewall6 and rc.d/ip6fw were removed.
997 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
998 variables are obsoleted. Instead, the following new rc
999 variables are added to rc.d/ipfw:
1001 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
1002 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
1003 firewall_simple_onet_ipv6, firewall_trusted_ipv6
1005 The meanings correspond to the relevant IPv4 variables.
1011 The default terminal emulation for syscons(4) has been changed
1012 from cons25 to xterm on all platforms except pc98. This means
1013 that the /etc/ttys file needs to be updated to ensure correct
1014 operation of applications on the console.
1016 The terminal emulation style can be toggled per window by using
1017 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
1018 options can be used to change the compile-time default back to
1021 To prevent graphical artifacts, make sure the TERM environment
1022 variable is set to match the terminal emulation that is being
1023 performed by syscons(4).
1026 The layout of the structure ieee80211req_scan_result has changed.
1027 Applications that require wireless scan results (e.g. ifconfig(8))
1028 from net80211 need to be recompiled.
1030 Applications such as wpa_supplicant(8) may require a full world
1031 build without using NO_CLEAN in order to get synchronized with the
1035 The iwn(4) driver has been updated to support the 5000 and 5150 series.
1036 There's one kernel module for each firmware. Adding "device iwnfw"
1037 to the kernel configuration file means including all three firmware
1038 images inside the kernel. If you want to include just the one for
1039 your wireless card, use the devices iwn4965fw, iwn5000fw or
1043 The rc.d/network_ipv6, IPv6 configuration script has been integrated
1044 into rc.d/netif. The changes are the following:
1046 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1047 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1048 Note that both variables need the "inet6" keyword at the head.
1050 Do not set $ipv6_network_interfaces manually if you do not
1051 understand what you are doing. It is not needed in most cases.
1053 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1056 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1057 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1059 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1060 all configured interfaces have "inet6 accept_rtadv" in the
1061 $ifconfig_IF_ipv6. These are for backward compatibility.
1063 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1064 functionality of interfaces with no corresponding
1065 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1066 and the default address selection policy of ip6addrctl(8)
1067 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1068 Note that if you want to configure IPv6 functionality on the
1069 disabled interfaces after boot, first you need to clear the flag by
1070 using ifconfig(8) like:
1072 ifconfig em0 inet6 -ifdisabled
1074 If YES, the default address selection policy is set as
1077 The default value of $ipv6_prefer is NO.
1079 4. If your system need to receive Router Advertisement messages,
1080 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1081 scripts automatically invoke rtsol(8) when the interface becomes
1082 UP. The Router Advertisement messages are used for SLAAC
1083 (State-Less Address AutoConfiguration).
1086 802.11s D3.03 support was committed. This is incompatible with the
1087 previous code, which was based on D3.0.
1090 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1091 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1092 control whether accepting Router Advertisement messages or not.
1093 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1094 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1095 The ifconfig(8) utility now supports these flags.
1098 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1099 mount(8) and -a option for df(1) to see them.
1102 The old tunable hw.bus.devctl_disable has been superseded by
1103 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1104 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1108 Remove the option STOP_NMI. The default action is now to use NMI only
1109 for KDB via the newly introduced function stop_cpus_hard() and
1110 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1113 The stable/8 branch created in subversion. This corresponds to the
1114 RELENG_8 branch in CVS.
1117 Bump the shared library version numbers for all libraries that do not
1118 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1119 __FreeBSD_version to 800105.
1122 Due to changes in the implementation of virtual network stack support,
1123 all network-related kernel modules must be recompiled. As this change
1124 breaks the ABI, bump __FreeBSD_version to 800104.
1127 The TOE interface to the TCP syncache has been modified to remove
1128 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1129 The cxgb driver is the only TOE consumer affected by this change, and
1130 needs to be recompiled along with the kernel. As this change breaks
1131 the ABI, bump __FreeBSD_version to 800103.
1134 Padding has been added to struct tcpcb, sackhint and tcpstat in
1135 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1136 maintaining the ABI. However, this change breaks the ABI, so bump
1137 __FreeBSD_version to 800102. User space tools that rely on the size of
1138 any of these structs (e.g. sockstat) need to be recompiled.
1141 The NFS_LEGACYRPC option has been removed along with the old kernel
1142 RPC implementation that this option selected. Kernel configurations
1143 may need to be adjusted.
1146 The network interface device nodes at /dev/net/<interface> have been
1147 removed. All ioctl operations can be performed the normal way using
1148 routing sockets. The kqueue functionality can generally be replaced
1149 with routing sockets.
1152 The documentation from the FreeBSD Documentation Project (Handbook,
1153 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1154 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1157 The ABI of various structures related to the SYSV IPC API have been
1158 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1159 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1163 Layout of struct vnet has changed as routing related variables were
1164 moved to their own Vimage module. Modules need to be recompiled. Bump
1165 __FreeBSD_version to 800099.
1168 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1169 respectively. As long as no more than 16 groups per process are used,
1170 no changes should be visible. When more than 16 groups are used, old
1171 binaries may fail if they call getgroups() or getgrouplist() with
1172 statically sized storage. Recompiling will work around this, but
1173 applications should be modified to use dynamically allocated storage
1174 for group arrays as POSIX.1-2008 does not cap an implementation's
1175 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1177 NFS and portalfs mounts may also be affected as the list of groups is
1178 truncated to 16. Users of NFS who use more than 16 groups, should
1179 take care that negative group permissions are not used on the exported
1180 file systems as they will not be reliable unless a GSSAPI based
1181 authentication method is used.
1184 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1185 option compiles in the support for adaptive spinning for lockmgrs
1186 which want to enable it. The lockinit() function now accepts the flag
1187 LK_ADAPTIVE in order to make the lock object subject to adaptive
1188 spinning when both held in write and read mode.
1191 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1192 changed. User applications that use this ioctl need to be rebuilt.
1195 The layout of struct thread has changed. Kernel and modules need to
1199 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1200 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1203 window(1) has been removed from the base system. It can now be
1204 installed from ports. The port is called misc/window.
1207 The way we are storing and accessing `routing table' entries has
1208 changed. Programs reading the FIB, like netstat, need to be
1212 A new netisr implementation has been added for FreeBSD 8. Network
1213 file system modules, such as igmp, ipdivert, and others, should be
1215 Bump __FreeBSD_version to 800096.
1218 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1222 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1223 Bump __FreeBSD_version to 800094.
1226 Add mnt_xflag field to 'struct mount'. File system modules need to be
1228 Bump __FreeBSD_version to 800093.
1231 The compiling option ADAPTIVE_SX has been retired while it has been
1232 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1233 The KPI for sx_init_flags() changes as accepting flags:
1234 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1235 been introduced in order to handle the reversed logic.
1236 Bump __FreeBSD_version to 800092.
1239 Add support for hierarchical jails. Remove global securelevel.
1240 Bump __FreeBSD_version to 800091.
1243 The layout of struct vnet_net has changed, therefore modules
1245 Bump __FreeBSD_version to 800090.
1248 The newly imported zic(8) produces a new format in the output. Please
1249 run tzsetup(8) to install the newly created data to /etc/localtime.
1252 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1253 hw.usb.* and is now consistent again with previous releases.
1256 802.11 monitor mode support was revised and driver api's were changed.
1257 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1258 of DLT_IEEE802_11. No user-visible data structures were changed but
1259 applications that use DLT_IEEE802_11 may require changes.
1260 Bump __FreeBSD_version to 800088.
1263 The layout of the following structs has changed: sysctl_oid,
1264 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1265 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1266 panics may be experienced. World rebuild is required for
1267 correctly checking networking state from userland.
1268 Bump __FreeBSD_version to 800085.
1271 MLDv2 and Source-Specific Multicast (SSM) have been merged
1272 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1273 The implementation of SSM within FreeBSD's IPv6 stack closely
1274 follows the IPv4 implementation.
1276 For kernel developers:
1278 * The most important changes are that the ip6_output() and
1279 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1280 and this lock has been downgraded to a non-recursive mutex.
1282 * As with the changes to the IPv4 stack to support SSM, filtering
1283 of inbound multicast traffic must now be performed by transport
1284 protocols within the IPv6 stack. This does not apply to TCP and
1285 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1287 * The KPIs used by IPv6 multicast are similar to those used by
1288 the IPv4 stack, with the following differences:
1289 * im6o_mc_filter() is analogous to imo_multicast_filter().
1290 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1291 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1292 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1293 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1294 for MLDv1 have an additional 'timer' argument which is used to
1295 jitter the initial membership report for the solicited-node
1296 multicast membership on-link.
1297 * This is not strictly needed for MLDv2, which already jitters
1298 its report transmissions. However, the 'timer' argument is
1299 preserved in case MLDv1 is active on the interface.
1301 * The KAME linked-list based IPv6 membership implementation has
1302 been refactored to use a vector similar to that used by the IPv4
1304 Code which maintains a list of its own multicast memberships
1305 internally, e.g. carp, has been updated to reflect the new
1308 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1309 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1310 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1311 implementation constraint which needs to be addressed in HEAD.
1313 For application developers:
1315 * The changes are broadly similar to those made for the IPv4
1318 * The use of IPv4 and IPv6 multicast socket options on the same
1319 socket, using mapped addresses, HAS NOT been tested or supported.
1321 * There are a number of issues with the implementation of various
1322 IPv6 multicast APIs which need to be resolved in the API surface
1323 before the implementation is fully compatible with KAME userland
1324 use, and these are mostly to do with interface index treatment.
1326 * The literature available discusses the use of either the delta / ASM
1327 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1328 using setsourcefilter(3)/getsourcefilter(3). For more information
1329 please refer to RFC 3768, 'Socket Interface Extensions for
1330 Multicast Source Filters'.
1332 * Applications which use the published RFC 3678 APIs should be fine.
1334 For systems administrators:
1336 * The mtest(8) utility has been refactored to support IPv6, in
1337 addition to IPv4. Interface addresses are no longer accepted
1338 as arguments, their names must be used instead. The utility
1339 will map the interface name to its first IPv4 address as
1340 returned by getifaddrs(3).
1342 * The ifmcstat(8) utility has also been updated to print the MLDv2
1343 endpoint state and source filter lists via sysctl(3).
1345 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1346 loopback of IPv6 multicast datagrams by default; it defaults to 1
1347 to preserve the existing behaviour. Disabling multicast loopback is
1348 recommended for optimal system performance.
1350 * The IPv6 MROUTING code has been changed to examine this sysctl
1351 instead of attempting to perform a group lookup before looping
1352 back forwarded datagrams.
1354 Bump __FreeBSD_version to 800084.
1357 Implement low-level Bluetooth HCI API.
1358 Bump __FreeBSD_version to 800083.
1361 The layout of struct malloc_type, used by modules to register new
1362 memory allocation types, has changed. Most modules will need to
1363 be rebuilt or panics may be experienced.
1364 Bump __FreeBSD_version to 800081.
1367 Anticipate overflowing inp_flags - add inp_flags2.
1368 This changes most offsets in inpcb, so checking v4 connection
1369 state will require a world rebuild.
1370 Bump __FreeBSD_version to 800080.
1373 Add an llentry to struct route and struct route_in6. Modules
1374 embedding a struct route will need to be recompiled.
1375 Bump __FreeBSD_version to 800079.
1378 The size of rt_metrics_lite and by extension rtentry has changed.
1379 Networking administration apps will need to be recompiled.
1380 The route command now supports show as an alias for get, weighting
1381 of routes, sticky and nostick flags to alter the behavior of stateful
1383 Bump __FreeBSD_version to 800078.
1386 Do not use Giant for kbdmux(4) locking. This is wrong and
1387 apparently causing more problems than it solves. This will
1388 re-open the issue where interrupt handlers may race with
1389 kbdmux(4) in polling mode. Typical symptoms include (but
1390 not limited to) duplicated and/or missing characters when
1391 low level console functions (such as gets) are used while
1392 interrupts are enabled (for example geli password prompt,
1393 mountroot prompt etc.). Disabling kbdmux(4) may help.
1396 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1397 kernel modules referencing any of the above need to be recompiled.
1398 Bump __FreeBSD_version to 800075.
1401 GEOM_PART has become the default partition slicer for storage devices,
1402 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1403 introduces some changes:
1405 MSDOS/EBR: the devices created from MSDOS extended partition entries
1406 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1407 to devices with offset-based names. fstabs may need to be modified.
1409 BSD: the "geometry does not match label" warning is harmless in most
1410 cases but it points to problems in file system misalignment with
1411 disk geometry. The "c" partition is now implicit, covers the whole
1412 top-level drive and cannot be (mis)used by users.
1414 General: Kernel dumps are now not allowed to be written to devices
1415 whose partition types indicate they are meant to be used for file
1416 systems (or, in case of MSDOS partitions, as something else than
1419 Most of these changes date approximately from 200812.
1422 The uscanner(4) driver has been removed from the kernel. This follows
1423 Linux removing theirs in 2.6 and making libusb the default interface
1424 (supported by sane).
1427 The multicast forwarding code has been cleaned up. netstat(1)
1428 only relies on KVM now for printing bandwidth upcall meters.
1429 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1430 ip6_mroute_mod respectively. The config(5) options for statically
1431 compiling this code remain the same, i.e. 'options MROUTING'.
1434 Support for the IFF_NEEDSGIANT network interface flag has been
1435 removed, which means that non-MPSAFE network device drivers are no
1436 longer supported. In particular, if_ar, if_sr, and network device
1437 drivers from the old (legacy) USB stack can no longer be built or
1441 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1442 a bunch of new language catalog files have also been added.
1443 This means that some common libc messages are now localized and
1444 they depend on the LC_MESSAGES environmental variable.
1447 The k8temp(4) driver has been renamed to amdtemp(4) since
1448 support for Family 10 and Family 11 CPU families was added.
1451 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1452 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1454 For kernel developers, the most important changes are that the
1455 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1456 and this lock has been downgraded to a non-recursive mutex.
1458 Transport protocols (UDP, Raw IP) are now responsible for filtering
1459 inbound multicast traffic according to group membership and source
1460 filters. The imo_multicast_filter() KPI exists for this purpose.
1461 Transports which do not use multicast (SCTP, TCP) already reject
1462 multicast by default. Forwarding and receive performance may improve
1463 as a mutex acquisition is no longer needed in the ip_input()
1464 low-level input path. in_addmulti() and in_delmulti() are shimmed
1465 to new KPIs which exist to support SSM in-kernel.
1467 For application developers, it is recommended that loopback of
1468 multicast datagrams be disabled for best performance, as this
1469 will still cause the lock to be taken for each looped-back
1470 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1471 be tuned to 0 to disable loopback by default; it defaults to 1
1472 to preserve the existing behaviour.
1474 For systems administrators, to obtain best performance with
1475 multicast reception and multiple groups, it is always recommended
1476 that a card with a suitably precise hash filter is used. Hash
1477 collisions will still result in the lock being taken within the
1478 transport protocol input path to check group membership.
1480 If deploying FreeBSD in an environment with IGMP snooping switches,
1481 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1482 enabled; this forces 224.0.0.0/24 group membership to be announced
1485 The size of 'struct igmpstat' has changed; netstat needs to be
1486 recompiled to reflect this.
1487 Bump __FreeBSD_version to 800070.
1490 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1491 updated to use it. This requires a buildworld/installworld in order to
1492 update the library and dependencies (usbconfig, etc). Its advisable to
1493 rebuild all ports which uses libusb. More specific directions are given
1494 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1495 libusb are no longer required and can be removed.
1498 A workaround is committed to allow the creation of System V shared
1499 memory segment of size > 2 GB on the 64-bit architectures.
1500 Due to a limitation of the existing ABI, the shm_segsz member
1501 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1502 wrong for large segments. Note that limits must be explicitly
1503 raised to allow such segments to be created.
1506 The layout of struct ifnet has changed, requiring a rebuild of all
1507 network device driver modules.
1510 The /dev handling for the new USB stack has changed, a
1511 buildworld/installworld is required for libusb20.
1514 The new USB2 stack has now been permanently moved in and all kernel and
1515 module names reverted to their previous values (eg, usb, ehci, ohci,
1516 ums, ...). The old usb stack can be compiled in by prefixing the name
1517 with the letter 'o', the old usb modules have been removed.
1518 Updating entry 20090216 for xorg and 20090215 for libmap may still
1522 The rc.conf(5) option if_up_delay has been renamed to
1523 defaultroute_delay to better reflect its purpose. If you have
1524 customized this setting in /etc/rc.conf you need to update it to
1528 xorg 7.4 wants to configure its input devices via hald which does not
1529 yet work with USB2. If the keyboard/mouse does not work in xorg then
1531 Option "AllowEmptyInput" "off"
1532 to your ServerLayout section. This will cause X to use the configured
1533 kbd and mouse sections from your xorg.conf.
1536 The GENERIC kernels for all architectures now default to the new USB2
1537 stack. No kernel config options or code have been removed so if a
1538 problem arises please report it and optionally revert to the old USB
1539 stack. If you are loading USB kernel modules or have a custom kernel
1540 that includes GENERIC then ensure that usb names are also changed over,
1541 eg uftdi -> usb2_serial_ftdi.
1543 Older programs linked against the ports libusb 0.1 need to be
1544 redirected to the new stack's libusb20. /etc/libmap.conf can
1546 # Map old usb library to new one for usb2 stack
1547 libusb-0.1.so.8 libusb20.so.1
1550 All USB ethernet devices now attach as interfaces under the name ueN
1551 (eg. ue0). This is to provide a predictable name as vendors often
1552 change usb chipsets in a product without notice.
1555 The ichsmb(4) driver has been changed to require SMBus slave
1556 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1557 All of the other SMBus controller drivers require left-justified
1558 slave addresses, so this change makes all the drivers provide the
1562 INET6 statistics (struct ip6stat) was updated.
1563 netstat(1) needs to be recompiled.
1566 NTFS has been removed from GENERIC kernel on amd64 to match
1567 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1568 will load ntfs.ko module automatically when NTFS support is
1569 actually needed, unless ntfs.ko is not installed or security
1570 level prohibits loading kernel modules. If either is the case,
1571 "options NTFS" has to be added into kernel config.
1574 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1575 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1576 800061. User space tools that rely on the size of struct tcpcb in
1577 tcp_var.h (e.g. sockstat) need to be recompiled.
1580 ng_tty(4) module updated to match the new TTY subsystem.
1581 Due to API change, user-level applications must be updated.
1582 New API support added to mpd5 CVS and expected to be present
1583 in next mpd5.3 release.
1586 With __FreeBSD_version 800060 the makefs tool is part of
1587 the base system (it was a port).
1590 The afdata and ifnet locks have been changed from mutexes to
1591 rwlocks, network modules will need to be re-compiled.
1594 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1595 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1596 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1597 architecture and 40 bytes on 64-bit architecture. The userland
1598 applications "arp" and "ndp" have been updated accordingly.
1599 The output from "netstat -r" shows only routing entries and
1600 none of the L2 information.
1603 __FreeBSD_version 800057 marks the switchover from the
1604 binary ath hal to source code. Users must add the line:
1606 options AH_SUPPORT_AR5416
1608 to their kernel config files when specifying:
1612 The ath_hal module no longer exists; the code is now compiled
1613 together with the driver in the ath module. It is now
1614 possible to tailor chip support (i.e. reduce the set of chips
1615 and thereby the code size); consult ath_hal(4) for details.
1618 __FreeBSD_version 800054 adds memory barriers to
1619 <machine/atomic.h>, new interfaces to ifnet to facilitate
1620 multiple hardware transmit queues for cards that support
1621 them, and a lock-less ring-buffer implementation to
1622 enable drivers to more efficiently manage queueing of
1626 A new version of ZFS (version 13) has been merged to -HEAD.
1627 This version has zpool attribute "listsnapshots" off by
1628 default, which means "zfs list" does not show snapshots,
1629 and is the same as Solaris behavior.
1632 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1635 The uhci, ohci, ehci and slhci USB Host controller drivers have
1636 been put into separate modules. If you load the usb module
1637 separately through loader.conf you will need to load the
1638 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1639 controller add the following to loader.conf:
1645 The ABI used by the PMC toolset has changed. Please keep
1646 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1650 atapci kernel module now includes only generic PCI ATA
1651 driver. AHCI driver moved to ataahci kernel module.
1652 All vendor-specific code moved into separate kernel modules:
1653 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1654 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1655 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1656 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1659 The TTY subsystem of the kernel has been replaced by a new
1660 implementation, which provides better scalability and an
1661 improved driver model. Most common drivers have been migrated to
1662 the new TTY subsystem, while others have not. The following
1663 drivers have not yet been ported to the new TTY layer:
1666 cy, digi, rc, rp, sio
1672 ng_h4, ng_tty, ppp, sl, snp
1674 Adding these drivers to your kernel configuration file shall
1675 cause compilation to fail.
1678 ntpd has been upgraded to 4.2.4p5.
1681 OpenSSH has been upgraded to 5.1p1.
1683 For many years, FreeBSD's version of OpenSSH preferred DSA
1684 over RSA for host and user authentication keys. With this
1685 upgrade, we've switched to the vendor's default of RSA over
1686 DSA. This may cause upgraded clients to warn about unknown
1687 host keys even for previously known hosts. Users should
1688 follow the usual procedure for verifying host keys before
1689 accepting the RSA key.
1691 This can be circumvented by setting the "HostKeyAlgorithms"
1692 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1695 Please note that the sequence of keys offered for
1696 authentication has been changed as well. You may want to
1697 specify IdentityFile in a different order to revert this
1701 The sio(4) driver has been removed from the i386 and amd64
1702 kernel configuration files. This means uart(4) is now the
1703 default serial port driver on those platforms as well.
1705 To prevent collisions with the sio(4) driver, the uart(4) driver
1706 uses different names for its device nodes. This means the
1707 onboard serial port will now most likely be called "ttyu0"
1708 instead of "ttyd0". You may need to reconfigure applications to
1709 use the new device names.
1711 When using the serial port as a boot console, be sure to update
1712 /boot/device.hints and /etc/ttys before booting the new kernel.
1713 If you forget to do so, you can still manually specify the hints
1714 at the loader prompt:
1716 set hint.uart.0.at="isa"
1717 set hint.uart.0.port="0x3F8"
1718 set hint.uart.0.flags="0x10"
1719 set hint.uart.0.irq="4"
1723 The gpt(8) utility has been removed. Use gpart(8) to partition
1727 The version that Linuxulator emulates was changed from 2.4.2
1728 to 2.6.16. If you experience any problems with Linux binaries
1729 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1730 if it fixes the problem contact emulation mailing list.
1733 ISDN4BSD (I4B) was removed from the src tree. You may need to
1734 update a your kernel configuration and remove relevant entries.
1737 I have checked in code to support multiple routing tables.
1738 See the man pages setfib(1) and setfib(2).
1739 This is a hopefully backwards compatible version,
1740 but to make use of it you need to compile your kernel
1741 with options ROUTETABLES=2 (or more up to 16).
1744 The 802.11 wireless support was redone to enable multi-bss
1745 operation on devices that are capable. The underlying device
1746 is no longer used directly but instead wlanX devices are
1747 cloned with ifconfig. This requires changes to rc.conf files.
1748 For example, change:
1749 ifconfig_ath0="WPA DHCP"
1752 ifconfig_wlan0="WPA DHCP"
1753 see rc.conf(5) for more details. In addition, mergemaster of
1754 /etc/rc.d is highly recommended. Simultaneous update of userland
1755 and kernel wouldn't hurt either.
1757 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1758 modules were merged into the base wlan module. All references
1759 to these modules (e.g. in kernel config files) must be removed.
1762 psm(4) has gained write(2) support in native operation level.
1763 Arbitrary commands can be written to /dev/psm%d and status can
1764 be read back from it. Therefore, an application is responsible
1765 for status validation and error recovery. It is a no-op in
1766 other operation levels.
1769 Support for KSE threading has been removed from the kernel. To
1770 run legacy applications linked against KSE libmap.conf may
1771 be used. The following libmap.conf may be used to ensure
1772 compatibility with any prior release:
1774 libpthread.so.1 libthr.so.1
1775 libpthread.so.2 libthr.so.2
1776 libkse.so.3 libthr.so.3
1779 The layout of struct vmspace has changed. This affects libkvm
1780 and any executables that link against libkvm and use the
1781 kvm_getprocs() function. In particular, but not exclusively,
1782 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1783 The effects are minimal, but it's advisable to upgrade world
1787 The latest em driver no longer has support in it for the
1788 82575 adapter, this is now moved to the igb driver. The
1789 split was done to make new features that are incompatible
1790 with older hardware easier to do.
1793 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1794 likewise the kernel option is now GEOM_LINUX_LVM.
1797 The default NFS mount mode has changed from UDP to TCP for
1798 increased reliability. If you rely on (insecurely) NFS
1799 mounting across a firewall you may need to update your
1803 Belatedly note the addition of m_collapse for compacting
1807 The fts(3) structures have been changed to use adequate
1808 integer types for their members and so to be able to cope
1809 with huge file trees. The old fts(3) ABI is preserved
1810 through symbol versioning in libc, so third-party binaries
1811 using fts(3) should still work, although they will not take
1812 advantage of the extended types. At the same time, some
1813 third-party software might fail to build after this change
1814 due to unportable assumptions made in its source code about
1815 fts(3) structure members. Such software should be fixed
1816 by its vendor or, in the worst case, in the ports tree.
1817 FreeBSD_version 800015 marks this change for the unlikely
1818 case that a portable fix is impossible.
1821 To upgrade to -current after this date, you must be running
1822 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1823 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1826 The ADAPTIVE_GIANT kernel option has been retired because its
1827 functionality is the default now.
1830 The AT keyboard emulation of sunkbd(4) has been turned on
1831 by default. In order to make the special symbols of the Sun
1832 keyboards driven by sunkbd(4) work under X these now have
1833 to be configured the same way as Sun USB keyboards driven
1834 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1836 Option "XkbLayout" "us"
1837 Option "XkbRules" "xorg"
1838 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1841 It has been decided that it is desirable to provide ABI
1842 backwards compatibility to the FreeBSD 4/5/6 versions of the
1843 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1844 broken with the introduction of PCI domain support (see the
1845 20070930 entry). Unfortunately, this required the ABI of
1846 PCIOCGETCONF to be broken again in order to be able to
1847 provide backwards compatibility to the old version of that
1848 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1849 again. As for prominent ports this affects neither pciutils
1850 nor xorg-server this time, the hal port needs to be rebuilt
1854 The misnamed kthread_create() and friends have been renamed
1855 to kproc_create() etc. Many of the callers already
1856 used kproc_start()..
1857 I will return kthread_create() and friends in a while
1858 with implementations that actually create threads, not procs.
1859 Renaming corresponds with version 800002.
1868 Avoid using make -j when upgrading. While generally safe, there are
1869 sometimes problems using -j to upgrade. If your upgrade fails with
1870 -j, please try again without -j. From time to time in the past there
1871 have been problems using -j with buildworld and/or installworld. This
1872 is especially true when upgrading between "distant" versions (eg one
1873 that cross a major release boundary or several minor releases, or when
1874 several months have passed on the -current branch).
1876 Sometimes, obscure build problems are the result of environment
1877 poisoning. This can happen because the make utility reads its
1878 environment when searching for values for global variables. To run
1879 your build attempts in an "environmental clean room", prefix all make
1880 commands with 'env -i '. See the env(1) manual page for more details.
1882 When upgrading from one major version to another it is generally best
1883 to upgrade to the latest code in the currently installed branch first,
1884 then do an upgrade to the new branch. This is the best-tested upgrade
1885 path, and has the highest probability of being successful. Please try
1886 this approach before reporting problems with a major version upgrade.
1888 When upgrading a live system, having a root shell around before
1889 installing anything can help undo problems. Not having a root shell
1890 around can lead to problems if pam has changed too much from your
1891 starting point to allow continued authentication after the upgrade.
1895 When upgrading the boot ZFS pool to a new version, always follow
1898 1.) recompile and reinstall the ZFS boot loader and boot block
1899 (this is part of "make buildworld" and "make installworld")
1901 2.) update the ZFS boot block on your boot drive
1903 The following example updates the ZFS boot block on the first
1904 partition (freebsd-boot) of a GPT partitioned drive ad0:
1905 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1907 Non-boot pools do not need these updates.
1911 If you are updating from a prior version of FreeBSD (even one just
1912 a few days old), you should follow this procedure. It is the most
1913 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1915 make kernel-toolchain
1916 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1917 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1919 To test a kernel once
1920 ---------------------
1921 If you just want to boot a kernel once (because you are not sure
1922 if it works, or if you want to boot a known bad kernel to provide
1923 debugging information) run
1924 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1925 nextboot -k testkernel
1927 To just build a kernel when you know that it won't mess you up
1928 --------------------------------------------------------------
1929 This assumes you are already running a CURRENT system. Replace
1930 ${arch} with the architecture of your machine (e.g. "i386",
1931 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1933 cd src/sys/${arch}/conf
1934 config KERNEL_NAME_HERE
1935 cd ../compile/KERNEL_NAME_HERE
1940 If this fails, go to the "To build a kernel" section.
1942 To rebuild everything and install it on the current system.
1943 -----------------------------------------------------------
1944 # Note: sometimes if you are running current you gotta do more than
1945 # is listed here if you are upgrading from a really old current.
1947 <make sure you have good level 0 dumps>
1949 make kernel KERNCONF=YOUR_KERNEL_HERE
1951 <reboot in single user> [3]
1958 To cross-install current onto a separate partition
1959 --------------------------------------------------
1960 # In this approach we use a separate partition to hold
1961 # current's root, 'usr', and 'var' directories. A partition
1962 # holding "/", "/usr" and "/var" should be about 2GB in
1965 <make sure you have good level 0 dumps>
1968 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1969 <maybe newfs current's root partition>
1970 <mount current's root partition on directory ${CURRENT_ROOT}>
1971 make installworld DESTDIR=${CURRENT_ROOT}
1972 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1973 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1974 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1975 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1976 <reboot into current>
1977 <do a "native" rebuild/install as described in the previous section>
1978 <maybe install compatibility libraries from ports/misc/compat*>
1982 To upgrade in-place from stable to current
1983 ----------------------------------------------
1984 <make sure you have good level 0 dumps>
1986 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1988 <reboot in single user> [3]
1995 Make sure that you've read the UPDATING file to understand the
1996 tweaks to various things you need. At this point in the life
1997 cycle of current, things change often and you are on your own
1998 to cope. The defaults can also change, so please read ALL of
1999 the UPDATING entries.
2001 Also, if you are tracking -current, you must be subscribed to
2002 freebsd-current@freebsd.org. Make sure that before you update
2003 your sources that you have read and understood all the recent
2004 messages there. If in doubt, please track -stable which has
2005 much fewer pitfalls.
2007 [1] If you have third party modules, such as vmware, you
2008 should disable them at this point so they don't crash your
2011 [3] From the bootblocks, boot -s, and then do
2016 adjkerntz -i # if CMOS is wall time
2017 Also, when doing a major release upgrade, it is required that
2018 you boot into single user mode to do the installworld.
2020 [4] Note: This step is non-optional. Failure to do this step
2021 can result in a significant reduction in the functionality of the
2022 system. Attempting to do it by hand is not recommended and those
2023 that pursue this avenue should read this file carefully, as well
2024 as the archives of freebsd-current and freebsd-hackers mailing lists
2025 for potential gotchas. The -U option is also useful to consider.
2026 See mergemaster(8) for more information.
2028 [5] Usually this step is a noop. However, from time to time
2029 you may need to do this if you get unknown user in the following
2030 step. It never hurts to do it all the time. You may need to
2031 install a new mergemaster (cd src/usr.sbin/mergemaster && make
2032 install) after the buildworld before this step if you last updated
2033 from current before 20130425 or from -stable before 20130430.
2035 [6] This only deletes old files and directories. Old libraries
2036 can be deleted by "make delete-old-libs", but you have to make
2037 sure that no program is using those libraries anymore.
2039 [8] In order to have a kernel that can run the 4.x binaries needed to
2040 do an installworld, you must include the COMPAT_FREEBSD4 option in
2041 your kernel. Failure to do so may leave you with a system that is
2042 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
2043 required to run the 5.x binaries on more recent kernels. And so on
2044 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
2046 Make sure that you merge any new devices from GENERIC since the
2047 last time you updated your kernel config file.
2049 [9] When checking out sources, you must include the -P flag to have
2050 cvs prune empty directories.
2052 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2053 "?=" instead of the "=" assignment operator, so that buildworld can
2054 override the CPUTYPE if it needs to.
2056 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2057 not on the command line, or in /etc/make.conf. buildworld will
2058 warn if it is improperly defined.
2061 This file contains a list, in reverse chronological order, of major
2062 breakages in tracking -current. It is not guaranteed to be a complete
2063 list of such breakages, and only contains entries since October 10, 2007.
2064 If you need to see UPDATING entries from before that date, you will need
2065 to fetch an UPDATING file from an older FreeBSD release.
2067 Copyright information:
2069 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2071 Redistribution, publication, translation and use, with or without
2072 modification, in full or in part, in any form or format of this
2073 document are permitted without further permission from the author.
2075 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2076 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2077 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2078 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2079 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2080 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2081 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2082 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2083 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2084 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2085 POSSIBILITY OF SUCH DAMAGE.
2087 Contact Warner Losh if you have any questions about your use of