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 behavior of gss_pseudo_random() for the krb5 mechanism
21 has changed, for applications requesting a longer random string
22 than produced by the underlying enctype's pseudo-random() function.
23 In particular, the random string produced from a session key of
24 enctype aes256-cts-hmac-sha1-96 or aes256-cts-hmac-sha1-96 will
25 be different at the 17th octet and later, after this change.
26 The counter used in the PRF+ construction is now encoded as a
27 big-endian integer in accordance with RFC 4402.
30 The default version of mtree is nmtree which is obtained from
31 NetBSD. The output is generally the same, but may vary
32 slightly. If you found you need identical output adding
33 "-F freebsd9" to the command line should do the trick. For the
34 time being, the old mtree is available as fmtree.
37 libbsdyml has been renamed to libyaml and moved to /usr/lib/private.
38 This will break ports-mgmt/pkg. Rebuild the port, or upgrade to pkg
39 1.1.4_8 and verify bsdyml not linked in, before running "make
41 # make -C /usr/ports/ports-mgmt/pkg build deinstall install clean
43 # pkg install pkg; ldd /usr/local/sbin/pkg | grep bsdyml
46 The rc.d/jail script has been updated to support jail(8)
47 configuration file. The "jail_<jname>_*" rc.conf(5) variables
48 for per-jail configuration are automatically converted to
49 /var/run/jail.<jname>.conf before the jail(8) utility is invoked.
50 This is transparently backward compatible. See below about some
51 incompatibilities and rc.conf(5) manual page for more details.
53 These variables are now deprecated in favor of jail(8) configuration
54 file. One can use "rc.d/jail config <jname>" command to generate
55 a jail(8) configuration file in /var/run/jail.<jname>.conf without
56 running the jail(8) utility. The default pathname of the
57 configuration file is /etc/jail.conf and can be specified by
58 using $jail_conf or $jail_<jname>_conf variables.
60 Please note that jail_devfs_ruleset accepts an integer at
61 this moment. Please consider to rewrite the ruleset name
65 BIND has been removed from the base system. If all you need
66 is a local resolver, simply enable and start the local_unbound
67 service instead. Otherwise, several versions of BIND are
68 available in the ports tree. The dns/bind99 port is one example.
70 With this change, nslookup(1) and dig(1) are no longer in the base
71 system. Users should instead use host(1) and drill(1) which are
72 in the base system. Alternatively, nslookup and dig can
73 be obtained by installing the dns/bind-tools port.
76 With the addition of unbound(8), a new unbound user is now
77 required during installworld. "mergemaster -p" can be used to
78 add the user prior to installworld, as documented in the handbook.
81 OpenSSH is now built with DNSSEC support, and will by default
82 silently trust signed SSHFP records. This can be controlled with
83 the VerifyHostKeyDNS client configuration setting. DNSSEC support
84 can be disabled entirely with the WITHOUT_LDNS option in src.conf.
87 The GNU Compiler Collection and C++ standard library (libstdc++)
88 are no longer built by default on platforms where clang is the system
89 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
93 The PROCDESC kernel option is now part of the GENERIC kernel
94 configuration and is required for the rwhod(8) to work.
95 If you are using custom kernel configuration, you should include
99 The API and ABI related to the Capsicum framework was modified
100 in backward incompatible way. The userland libraries and programs
101 have to be recompiled to work with the new kernel. This includes the
102 following libraries and programs, but the whole buildworld is
103 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
104 kdump, procstat, rwho, rwhod, uniq.
107 AES-NI intrinsic support has been added to gcc. The AES-NI module
108 has been updated to use this support. A new gcc is required to build
109 the aesni module on both i386 and amd64.
112 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
113 Thus "device padlock_rng" and "device rdrand_rng" should be
114 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
117 WITH_ICONV has been split into two feature sets. WITH_ICONV now
118 enables just the iconv* functionality and is now on by default.
119 WITH_LIBICONV_COMPAT enables the libiconv api and link time
120 compatability. Set WITHOUT_ICONV to build the old way.
121 If you have been using WITH_ICONV before, you will very likely
122 need to turn on WITH_LIBICONV_COMPAT.
125 INVARIANTS option now enables DEBUG for code with OpenSolaris and
126 Illumos origin, including ZFS. If you have INVARIANTS in your
127 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
129 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
130 locks if WITNESS option was set. Because that generated a lot of
131 witness(9) reports and all of them were believed to be false
132 positives, this is no longer done. New option OPENSOLARIS_WITNESS
133 can be used to achieve the previous behavior.
136 Timer values in IPv6 data structures now use time_uptime instead
137 of time_second. Although this is not a user-visible functional
138 change, userland utilities which directly use them---ndp(8),
139 rtadvd(8), and rtsold(8) in the base system---need to be updated
143 find -delete can now delete the pathnames given as arguments,
144 instead of only files found below them or if the pathname did
145 not contain any slashes. Formerly, the following error message
148 find: -delete: <path>: relative path potentially not safe
150 Deleting the pathnames given as arguments can be prevented
151 without error messages using -mindepth 1 or by changing
152 directory and passing "." as argument to find. This works in the
153 old as well as the new version of find.
156 Behavior of devfs rules path matching has been changed.
157 Pattern is now always matched against fully qualified devfs
158 path and slash characters must be explicitly matched by
159 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
160 subdirectories must be reviewed.
163 The default ARM ABI has changed to the ARM EABI. The old ABI is
164 incompatible with the ARM EABI and all programs and modules will
165 need to be rebuilt to work with a new kernel.
167 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
169 NOTE: Support for the old ABI will be removed in the future and
170 users are advised to upgrade.
173 pkg_install has been disconnected from the build if you really need it
174 you should add WITH_PKGTOOLS in your src.conf(5).
177 Most of network statistics structures were changed to be able
178 keep 64-bits counters. Thus all tools, that work with networking
179 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
182 Fix targets that run multiple make's to use && rather than ;
183 so that subsequent steps depend on success of previous.
185 NOTE: if building 'universe' with -j* on stable/8 or stable/9
186 it would be better to start the build using bmake, to avoid
187 overloading the machine.
190 Fix a bug that allowed a tracing process (e.g. gdb) to write
191 to a memory-mapped file in the traced process's address space
192 even if neither the traced process nor the tracing process had
193 write access to that file.
196 CVS has been removed from the base system. An exact copy
197 of the code is available from the devel/cvs port.
200 Some people report the following error after the switch to bmake:
202 make: illegal option -- J
203 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
205 *** [buildworld] Error code 2
207 this likely due to an old instance of make in
208 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
209 which src/Makefile will use that blindly, if it exists, so if
210 you see the above error:
212 rm -rf `make -V MAKEPATH`
217 Use bmake by default.
218 Whereas before one could choose to build with bmake via
219 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
220 make. The goal is to remove these knobs for 10-RELEASE.
222 It is worth noting that bmake (like gmake) treats the command
223 line as the unit of failure, rather than statements within the
224 command line. Thus '(cd some/where && dosomething)' is safer
225 than 'cd some/where; dosomething'. The '()' allows consistent
226 behavior in parallel build.
229 Fix a bug that allows NFS clients to issue READDIR on files.
232 The WITHOUT_IDEA option has been removed because
233 the IDEA patent expired.
236 The sysctl which controls TRIM support under ZFS has been renamed
237 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
241 The mergemaster command now uses the default MAKEOBJDIRPREFIX
242 rather than creating it's own in the temporary directory in
243 order allow access to bootstrapped versions of tools such as
244 install and mtree. When upgrading from version of FreeBSD where
245 the install command does not support -l, you will need to
246 install a new mergemaster command if mergemaster -p is required.
247 This can be accomplished with the command (cd src/usr.sbin/mergemaster
251 Legacy ATA stack, disabled and replaced by new CAM-based one since
252 FreeBSD 9.0, completely removed from the sources. Kernel modules
253 atadisk and atapi*, user-level tools atacontrol and burncd are
254 removed. Kernel option `options ATA_CAM` is now permanently enabled
258 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
259 and socketpair(2). Software, in particular Kerberos, may
260 automatically detect and use these during building. The resulting
261 binaries will not work on older kernels.
264 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
265 information, see the respective 20130304 entry).
268 Recent commits to callout(9) changed the size of struct callout,
269 so the KBI is probably heavily disturbed. Also, some functions
270 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
271 by macros. Every kernel module using it won't load, so rebuild
274 The ctl device has been re-enabled in GENERIC for i386 and amd64,
275 but does not initialize by default (because of the new CTL_DISABLE
276 option) to save memory. To re-enable it, remove the CTL_DISABLE
277 option from the kernel config file or set kern.cam.ctl.disable=0
278 in /boot/loader.conf.
281 The ctl device has been disabled in GENERIC for i386 and amd64.
282 This was done due to the extra memory being allocated at system
283 initialisation time by the ctl driver which was only used if
284 a CAM target device was created. This makes a FreeBSD system
285 unusable on 128MB or less of RAM.
288 A new compression method (lz4) has been merged to -HEAD. Please
289 refer to zpool-features(7) for more information.
291 Please refer to the "ZFS notes" section of this file for information
292 on upgrading boot ZFS pools.
295 A BSD-licensed patch(1) variant has been added and is installed
296 as bsdpatch, being the GNU version the default patch.
297 To inverse the logic and use the BSD-licensed one as default,
298 while having the GNU version installed as gnupatch, rebuild
299 and install world with the WITH_BSD_PATCH knob set.
302 Due to the use of the new -l option to install(1) during build
303 and install, you must take care not to directly set the INSTALL
304 make variable in your /etc/make.conf, /etc/src.conf, or on the
305 command line. If you wish to use the -C flag for all installs
306 you may be able to add INSTALL+=-C to /etc/make.conf or
310 The install(1) option -M has changed meaning and now takes an
311 argument that is a file or path to append logs to. In the
312 unlikely event that -M was the last option on the command line
313 and the command line contained at least two files and a target
314 directory the first file will have logs appended to it. The -M
315 option served little practical purpose in the last decade so its
316 use is expected to be extremely rare.
319 After switching to Clang as the default compiler some users of ZFS
320 on i386 systems started to experience stack overflow kernel panics.
321 Please consider using 'options KSTACK_PAGES=4' in such configurations.
324 GEOM_LABEL now mangles label names read from file system metadata.
325 Mangling affect labels containing spaces, non-printable characters,
326 '%' or '"'. Device names in /etc/fstab and other places may need to
330 By default, only the 10 most recent kernel dumps will be saved. To
331 restore the previous behaviour (no limit on the number of kernel dumps
332 stored in the dump directory) add the following line to /etc/rc.conf:
337 With the addition of auditdistd(8), a new auditdistd user is now
338 required during installworld. "mergemaster -p" can be used to
339 add the user prior to installworld, as documented in the handbook.
342 The sin6_scope_id member variable in struct sockaddr_in6 is now
343 filled by the kernel before passing the structure to the userland via
344 sysctl or routing socket. This means the KAME-specific embedded scope
345 id in sin6_addr.s6_addr[2] is always cleared in userland application.
346 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
347 __FreeBSD_version is bumped to 1000025.
350 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
351 This means that the world and kernel will be compiled with clang
352 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
353 and /usr/bin/cpp. To disable this behavior and revert to building
354 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
355 of current may need to bootstrap WITHOUT_CLANG first if the clang
356 build fails (its compatibility window doesn't extend to the 9 stable
360 The IPFIREWALL_FORWARD kernel option has been removed. Its
361 functionality now turned on by default.
364 The ZERO_COPY_SOCKET kernel option has been removed and
365 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
366 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
367 mechanism which is not safe and may result in kernel crashes.
368 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
369 driver supports disposeable external page sized mbuf storage.
370 Proper replacements for both zero-copy mechanisms are under
371 consideration and will eventually lead to complete removal
372 of the two kernel options.
375 The IPv4 network stack has been converted to network byte
376 order. The following modules need to be recompiled together
377 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
378 pf(4), ipfw(4), ng_ipfw(4), stf(4).
381 Support for non-MPSAFE filesystems was removed from VFS. The
382 VFS_VERSION was bumped, all filesystem modules shall be
386 All the non-MPSAFE filesystems have been disconnected from
387 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
388 portalfs, smbfs, xfs.
391 The interface cloning API and ABI has changed. The following
392 modules need to be recompiled together with kernel:
393 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
394 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
395 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
398 The sdhci driver was split in two parts: sdhci (generic SD Host
399 Controller logic) and sdhci_pci (actual hardware driver).
400 No kernel config modifications are required, but if you
401 load sdhc as a module you must switch to sdhci_pci instead.
404 Import the FUSE kernel and userland support into base system.
407 The GNU sort(1) program has been removed since the BSD-licensed
408 sort(1) has been the default for quite some time and no serious
409 problems have been reported. The corresponding WITH_GNU_SORT
413 The pfil(9) API/ABI for AF_INET family has been changed. Packet
414 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
418 The net80211(4) ABI has been changed to allow for improved driver
419 PS-POLL and power-save support. All wireless drivers need to be
420 recompiled to work with the new kernel.
423 The random(4) support for the VIA hardware random number
424 generator (`PADLOCK') is no longer enabled unconditionally.
425 Add the padlock_rng device in the custom kernel config if
426 needed. The GENERIC kernels on i386 and amd64 do include the
427 device, so the change only affects the custom kernel
431 The pf(4) packet filter ABI has been changed. pfctl(8) and
432 snmp_pf module need to be recompiled to work with new kernel.
435 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
436 to -HEAD. Pools that have empty_bpobj in active state can not be
437 imported read-write with ZFS implementations that do not support
438 this feature. For more information read the zpool-features(5)
442 The sparc64 ZFS loader has been changed to no longer try to auto-
443 detect ZFS providers based on diskN aliases but now requires these
444 to be explicitly listed in the OFW boot-device environment variable.
447 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
448 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
449 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
452 The following sysctls and tunables have been renamed for consistency
453 with other variables:
454 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
455 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
458 The sort utility has been replaced with BSD sort. For now, GNU sort
459 is also available as "gnusort" or the default can be set back to
460 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
461 installed as "bsdsort".
464 A new version of ZFS (pool version 5000) has been merged to -HEAD.
465 Starting with this version the old system of ZFS pool versioning
466 is superseded by "feature flags". This concept enables forward
467 compatibility against certain future changes in functionality of ZFS
468 pools. The first read-only compatible "feature flag" for ZFS pools
469 is named "com.delphix:async_destroy". For more information
470 read the new zpool-features(5) manual page.
471 Please refer to the "ZFS notes" section of this file for information
472 on upgrading boot ZFS pools.
475 The malloc(3) implementation embedded in libc now uses sources imported
476 as contrib/jemalloc. The most disruptive API change is to
477 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
478 delete it prior to installworld, and optionally re-create it using the
479 new format after rebooting. See malloc.conf(5) for details
480 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
484 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
485 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
486 now spelled mips. This is to aid compatibility with third-party
487 software that expects this naming scheme in uname(3). Little-endian
488 settings are unchanged. If you are updating a big-endian mips64 machine
489 from before this change, you may need to set MACHINE_ARCH=mips64 in
490 your environment before the new build system will recognize your machine.
493 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
497 Now unix domain sockets behave "as expected" on nullfs(5). Previously
498 nullfs(5) did not pass through all behaviours to the underlying layer,
499 as a result if we bound to a socket on the lower layer we could connect
500 only to the lower path; if we bound to the upper layer we could connect
501 only to the upper path. The new behavior is one can connect to both the
502 lower and the upper paths regardless what layer path one binds to.
505 The getifaddrs upgrade path broken with 20111215 has been restored.
506 If you have upgraded in between 20111215 and 20120209 you need to
507 recompile libc again with your kernel. You still need to recompile
508 world to be able to configure CARP but this restriction already
512 The set_rcvar() function has been removed from /etc/rc.subr. All
513 base and ports rc.d scripts have been updated, so if you have a
514 port installed with a script in /usr/local/etc/rc.d you can either
515 hand-edit the rcvar= line, or reinstall the port.
517 An easy way to handle the mass-update of /etc/rc.d:
518 rm /etc/rc.d/* && mergemaster -i
521 panic(9) now stops other CPUs in the SMP systems, disables interrupts
522 on the current CPU and prevents other threads from running.
523 This behavior can be reverted using the kern.stop_scheduler_on_panic
525 The new behavior can be incompatible with kern.sync_on_panic.
528 The carp(4) facility has been changed significantly. Configuration
529 of the CARP protocol via ifconfig(8) has changed, as well as format
530 of CARP events submitted to devd(8) has changed. See manual pages
531 for more information. The arpbalance feature of carp(4) is currently
532 not supported anymore.
534 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
535 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
536 need to be recompiled.
539 The acpi_wmi(4) status device /dev/wmistat has been renamed to
543 The option VFS_ALLOW_NONMPSAFE option has been added in order to
544 explicitely support non-MPSAFE filesystems.
545 It is on by default for all supported platform at this present
549 The broken amd(4) driver has been replaced with esp(4) in the amd64,
550 i386 and pc98 GENERIC kernel configuration files.
553 sysinstall has been removed
556 The stable/9 branch created in subversion. This corresponds to the
557 RELENG_9 branch in CVS.
560 This commit modifies vfs_register() so that it uses a hash
561 calculation to set vfc_typenum, which is enabled by default.
562 The first time a system is booted after this change, the
563 vfc_typenum values will change for all file systems. The
564 main effect of this is a change to the NFS server file handles
565 for file systems that use vfc_typenum in their fsid, such as ZFS.
566 It will, however, prevent vfc_typenum from changing when file
567 systems are loaded in a different order for subsequent reboots.
568 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
569 until you are ready to remount all NFS clients after a reboot.
572 Bump the shared library version numbers for libraries that
573 do not use symbol versioning, have changed the ABI compared
574 to stable/8 and which shared library version was not bumped.
575 Done as part of 9.0-RELEASE cycle.
578 During the merge of Capsicum features, the fget(9) KPI was modified.
579 This may require the rebuilding of out-of-tree device drivers --
580 issues have been reported specifically with the nVidia device driver.
581 __FreeBSD_version is bumped to 900041.
583 Also, there is a period between 20110811 and 20110814 where the
584 special devices /dev/{stdin,stdout,stderr} did not work correctly.
585 Building world from a kernel during that window may not work.
588 The packet filter (pf) code has been updated to OpenBSD 4.5.
589 You need to update userland tools to be in sync with kernel.
590 This update breaks backward compatibility with earlier pfsync(4)
591 versions. Care must be taken when updating redundant firewall setups.
594 The following sysctls and tunables are retired on x86 platforms:
596 machdep.hlt_logical_cpus
597 The following sysctl is retired:
598 machdep.hyperthreading_allowed
599 The sysctls were supposed to provide a way to dynamically offline and
600 online selected CPUs on x86 platforms, but the implementation has not
601 been reliable especially with SCHED_ULE scheduler.
602 machdep.hyperthreading_allowed tunable is still available to ignore
603 hyperthreading CPUs at OS level.
604 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
605 where X is an APIC ID of a CPU. Be advised, though, that disabling
606 CPUs in non-uniform fashion will result in non-uniform topology and
607 may lead to sub-optimal system performance with SCHED_ULE, which is
611 cpumask_t type is retired and cpuset_t is used in order to describe
615 Changes to ifconfig(8) for dynamic address family detection mandate
616 that you are running a kernel of 20110525 or later. Make sure to
617 follow the update procedure to boot a new kernel before installing
621 Support for sun4v architecture is officially dropped
624 Several KPI breaking changes have been committed to the mii(4) layer,
625 the PHY drivers and consequently some Ethernet drivers using mii(4).
626 This means that miibus.ko and the modules of the affected Ethernet
627 drivers need to be recompiled.
629 Note to kernel developers: Given that the OUI bit reversion problem
630 was fixed as part of these changes all mii(4) commits related to OUIs,
631 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
632 handling, no longer can be merged verbatim to stable/8 and previous
636 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
637 into their kernel configurations along with 'device pci'.
640 The default NFS client is now the new NFS client, so fstype "newnfs"
641 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
642 Although mounts via fstype "nfs" will usually work without userland
643 changes, it is recommended that the mount(8) and mount_nfs(8)
644 commands be rebuilt from sources and that a link to mount_nfs called
645 mount_oldnfs be created. The new client is compiled into the
646 kernel with "options NFSCL" and this is needed for diskless root
647 file systems. The GENERIC kernel configs have been changed to use
648 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
649 To use the regular/old client, you can "mount -t oldnfs ...". For
650 a diskless root file system, you must also include a line like:
652 vfs.root.mountfrom="oldnfs:"
654 in the boot/loader.conf on the root fs on the NFS server to make
655 a diskless root fs use the old client.
658 The GENERIC kernels for all architectures now default to the new
659 CAM-based ATA stack. It means that all legacy ATA drivers were
660 removed and replaced by respective CAM drivers. If you are using
661 ATA device names in /etc/fstab or other places, make sure to update
662 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
663 where 'Y's are the sequential numbers starting from zero for each type
664 in order of detection, unless configured otherwise with tunables,
665 see cam(4)). There will be symbolic links created in /dev/ to map
666 old adX devices to the respective adaY. They should provide basic
667 compatibility for file systems mounting in most cases, but they do
668 not support old user-level APIs and do not have respective providers
669 in GEOM. Consider using updated management tools with new device names.
671 It is possible to load devices ahci, ata, siis and mvs as modules,
672 but option ATA_CAM should remain in kernel configuration to make ata
673 module work as CAM driver supporting legacy ATA controllers. Device ata
674 still can be used in modular fashion (atacore + ...). Modules atadisk
675 and atapi* are not used and won't affect operation in ATA_CAM mode.
676 Note that to use CAM-based ATA kernel should include CAM devices
677 scbus, pass, da (or explicitly ada), cd and optionally others. All of
678 them are parts of the cam module.
680 ataraid(4) functionality is now supported by the RAID GEOM class.
681 To use it you can load geom_raid kernel module and use graid(8) tool
682 for management. Instead of /dev/arX device names, use /dev/raid/rX.
684 No kernel config options or code have been removed, so if a problem
685 arises, please report it and optionally revert to the old ATA stack.
686 In order to do it you can remove from the kernel config:
691 , and instead add back:
692 device atadisk # ATA disk drives
693 device ataraid # ATA RAID drives
694 device atapicd # ATAPI CDROM drives
695 device atapifd # ATAPI floppy drives
696 device atapist # ATAPI tape drives
699 The default NFS server has been changed to the new server, which
700 was referred to as the experimental server. If you need to switch
701 back to the old NFS server, you must now put the "-o" option on
702 both the mountd and nfsd commands. This can be done using the
703 mountd_flags and nfs_server_flags rc.conf variables until an
704 update to the rc scripts is committed, which is coming soon.
707 The GNU Objective-C runtime library (libobjc), and other Objective-C
708 related components have been removed from the base system. If you
709 require an Objective-C library, please use one of the available ports.
712 ath(4) has been split into bus- and device- modules. if_ath contains
713 the HAL, the TX rate control and the network device code. if_ath_pci
714 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
715 contains the AHB glue. Users need to load both if_ath_pci and if_ath
716 in order to use ath on everything else.
718 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
719 need to load if_ath and if_ath_pci for ath(4) operation.
722 As part of the replacement of sysinstall, the process of building
723 release media has changed significantly. For details, please re-read
724 release(7), which has been updated to reflect the new build process.
727 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
728 is the last available version under GPLv2. It brings a number of new
729 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
730 4.1 and SSE 4.2), better support for powerpc64, a number of new
731 directives, and lots of other small improvements. See the ChangeLog
732 file in contrib/binutils for the full details.
735 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
736 compliant, and will now use half of hash for authentication.
737 This will break interoperability with all stacks (including all
738 actual FreeBSD versions) who implement
739 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
741 The only workaround with such peers is to use another HMAC
742 algorithm for IPsec ("phase 2") authentication.
745 Remove the uio_yield prototype and symbol. This function has
746 been misnamed since it was introduced and should not be
747 globally exposed with this name. The equivalent functionality
748 is now available using kern_yield(curthread->td_user_pri).
749 The function remains undocumented.
752 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
753 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
754 for scalar sysctls is defined but disabled. Code that needs
755 UQUAD to pass the type checking that must compile on older
756 systems where the define is not present can check against
757 __FreeBSD_version >= 900030.
759 The system dialog(1) has been replaced with a new version previously
760 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
761 with the previous version, but the libdialog associated with it has
762 a largely incompatible API. As such, the original version of libdialog
763 will be kept temporarily as libodialog, until its base system consumers
764 are replaced or updated. Bump __FreeBSD_version to 900030.
767 If you are trying to run make universe on a -stable system, and you get
768 the following warning:
769 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
770 unknown. config(8) likely too old."
771 or something similar to it, then you must upgrade your -stable system
772 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
773 stable/8) or build the config from the latest stable/8 branch and
774 install it on your system.
776 Prior to this date, building a current universe on 8-stable system from
777 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
778 error in the first kernel build phase. A new config on those old
779 systems will fix that problem for older versions of -current.
782 The TCP stack has been modified to allow Khelp modules to interact with
783 it via helper hook points and store per-connection data in the TCP
784 control block. Bump __FreeBSD_version to 900029. User space tools that
785 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
789 Generic IEEE 802.3 annex 31B full duplex flow control support has been
790 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
791 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
792 to take advantage of it instead of using custom implementations. This
793 means that these drivers now no longer unconditionally advertise
794 support for flow control but only do so if flow control is a selected
795 media option. This was implemented in the generic support that way in
796 order to allow flow control to be switched on and off via ifconfig(8)
797 with the PHY specific default to typically off in order to protect
798 from unwanted effects. Consequently, if you used flow control with
799 one of the above mentioned drivers you now need to explicitly enable
801 ifconfig bge0 media auto mediaopt flowcontrol
803 Along with the above mentioned changes generic support for setting
804 1000baseT master mode also has been added and brgphy(4), ciphy(4),
805 e1000phy(4) as well as ip1000phy(4) have been converted to take
806 advantage of it. This means that these drivers now no longer take the
807 link0 parameter for selecting master mode but the master media option
808 has to be used instead, for example like in the following:
809 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
811 Selection of master mode now is also available with all other PHY
812 drivers supporting 1000baseT.
815 The TCP stack has received a significant update to add support for
816 modularised congestion control and generally improve the clarity of
817 congestion control decisions. Bump __FreeBSD_version to 900025. User
818 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
819 sockstat) need to be recompiled.
822 The man(1) utility has been replaced by a new version that no longer
823 uses /etc/manpath.config. Please consult man.conf(5) for how to
824 migrate local entries to the new format.
827 The copyright strings printed by login(1) and sshd(8) at the time of a
828 new connection have been removed to follow other operating systems and
832 A workaround for a fixed ld bug has been removed in kernel code,
833 so make sure that your system ld is built from sources after
834 revision 210245 from 2010-07-19 (r211583 if building head kernel
835 on stable/8, r211584 for stable/7; both from 2010-08-21).
836 A symptom of incorrect ld version is different addresses for
837 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
840 The $ipv6_prefer variable in rc.conf(5) has been split into
841 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
843 The $ip6addrctl_policy is a variable to choose a pre-defined
844 address selection policy set by ip6addrctl(8). A value
845 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
848 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
849 flag (see an entry of 20090926) is set on an interface with no
850 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
851 security reason. If you want IPv6 link-local address on all
852 interfaces by default, set this to "YES".
854 The old ipv6_prefer="YES" is equivalent to
855 ipv6_activate_all_interfaces="YES" and
856 ip6addrctl_policy="ipv6_prefer".
859 DTrace has grown support for userland tracing. Due to this, DTrace is
860 now i386 and amd64 only.
861 dtruss(1) is now installed by default on those systems and a new
862 kernel module is needed for userland tracing: fasttrap.
863 No changes to your kernel config file are necessary to enable
864 userland tracing, but you might consider adding 'STRIP=' and
865 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
866 to have informative userland stack traces in DTrace (ustack).
869 The acpi_aiboost(4) driver has been removed in favor of the new
870 aibs(4) driver. You should update your kernel configuration file.
873 BSD grep has been imported to the base system and it is built by
874 default. It is completely BSD licensed, highly GNU-compatible, uses
875 less memory than its GNU counterpart and has a small codebase.
876 However, it is slower than its GNU counterpart, which is mostly
877 noticeable for larger searches, for smaller ones it is measurable
878 but not significant. The reason is complex, the most important factor
879 is that we lack a modern and efficient regex library and GNU
880 overcomes this by optimizing the searches internally. Future work
881 on improving the regex performance is planned, for the meantime,
882 users that need better performance, can build GNU grep instead by
883 setting the WITH_GNU_GREP knob.
886 Due to the import of powerpc64 support, all existing powerpc kernel
887 configuration files must be updated with a machine directive like this:
888 machine powerpc powerpc
890 In addition, an updated config(8) is required to build powerpc kernels
894 A new version of ZFS (version 15) has been merged to -HEAD.
895 This version uses a python library for the following subcommands:
896 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
897 For full functionality of these commands the following port must
898 be installed: sysutils/py-zfs
901 'vm_page's are now hashed by physical address to an array of mutexes.
902 Currently this is only used to serialize access to hold_count. Over
903 time the page queue mutex will be peeled away. This changes the size
904 of pmap on every architecture. And requires all callers of vm_page_hold
905 and vm_page_unhold to be updated.
908 WITH_CTF can now be specified in src.conf (not recommended, there
909 are some problems with static executables), make.conf (would also
910 affect ports which do not use GNU make and do not override the
911 compile targets) or in the kernel config (via "makeoptions
913 When WITH_CTF was specified there before this was silently ignored,
914 so make sure that WITH_CTF is not used in places which could lead
915 to unwanted behavior.
918 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
919 to allow 32-bit compatibility on non-x86 platforms. All kernel
920 configurations on amd64 and ia64 platforms using these options must
921 be modified accordingly.
924 The utmp user accounting database has been replaced with utmpx,
925 the user accounting interface standardized by POSIX.
926 Unfortunately the semantics of utmp and utmpx don't match,
927 making it practically impossible to support both interfaces.
928 The user accounting database is used by tools like finger(1),
929 last(1), talk(1), w(1) and ac(8).
931 All applications in the base system use utmpx. This means only
932 local binaries (e.g. from the ports tree) may still use these
933 utmp database files. These applications must be rebuilt to make
936 After the system has been upgraded, it is safe to remove the old
937 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
938 assuming their contents is of no importance anymore. Old wtmp
939 databases can only be used by last(1) and ac(8) after they have
940 been converted to the new format using wtmpcvt(1).
943 Introduce the kernel thread "deadlock resolver" (which can be enabled
944 via the DEADLKRES option, see NOTES for more details) and the
945 sleepq_type() function for sleepqueues.
948 The rc.firewall and rc.firewall6 were unified, and
949 rc.firewall6 and rc.d/ip6fw were removed.
950 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
951 variables are obsoleted. Instead, the following new rc
952 variables are added to rc.d/ipfw:
954 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
955 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
956 firewall_simple_onet_ipv6, firewall_trusted_ipv6
958 The meanings correspond to the relevant IPv4 variables.
964 The default terminal emulation for syscons(4) has been changed
965 from cons25 to xterm on all platforms except pc98. This means
966 that the /etc/ttys file needs to be updated to ensure correct
967 operation of applications on the console.
969 The terminal emulation style can be toggled per window by using
970 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
971 options can be used to change the compile-time default back to
974 To prevent graphical artifacts, make sure the TERM environment
975 variable is set to match the terminal emulation that is being
976 performed by syscons(4).
979 The layout of the structure ieee80211req_scan_result has changed.
980 Applications that require wireless scan results (e.g. ifconfig(8))
981 from net80211 need to be recompiled.
983 Applications such as wpa_supplicant(8) may require a full world
984 build without using NO_CLEAN in order to get synchronized with the
988 The iwn(4) driver has been updated to support the 5000 and 5150 series.
989 There's one kernel module for each firmware. Adding "device iwnfw"
990 to the kernel configuration file means including all three firmware
991 images inside the kernel. If you want to include just the one for
992 your wireless card, use the devices iwn4965fw, iwn5000fw or
996 The rc.d/network_ipv6, IPv6 configuration script has been integrated
997 into rc.d/netif. The changes are the following:
999 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
1000 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
1001 Note that both variables need the "inet6" keyword at the head.
1003 Do not set $ipv6_network_interfaces manually if you do not
1004 understand what you are doing. It is not needed in most cases.
1006 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
1009 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
1010 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
1012 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
1013 all configured interfaces have "inet6 accept_rtadv" in the
1014 $ifconfig_IF_ipv6. These are for backward compatibility.
1016 3. A new variable $ipv6_prefer has been added. If NO, IPv6
1017 functionality of interfaces with no corresponding
1018 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
1019 and the default address selection policy of ip6addrctl(8)
1020 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
1021 Note that if you want to configure IPv6 functionality on the
1022 disabled interfaces after boot, first you need to clear the flag by
1023 using ifconfig(8) like:
1025 ifconfig em0 inet6 -ifdisabled
1027 If YES, the default address selection policy is set as
1030 The default value of $ipv6_prefer is NO.
1032 4. If your system need to receive Router Advertisement messages,
1033 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
1034 scripts automatically invoke rtsol(8) when the interface becomes
1035 UP. The Router Advertisement messages are used for SLAAC
1036 (State-Less Address AutoConfiguration).
1039 802.11s D3.03 support was committed. This is incompatible with the
1040 previous code, which was based on D3.0.
1043 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1044 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1045 control whether accepting Router Advertisement messages or not.
1046 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1047 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1048 The ifconfig(8) utility now supports these flags.
1051 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1052 mount(8) and -a option for df(1) to see them.
1055 The old tunable hw.bus.devctl_disable has been superseded by
1056 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1057 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1061 Remove the option STOP_NMI. The default action is now to use NMI only
1062 for KDB via the newly introduced function stop_cpus_hard() and
1063 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1066 The stable/8 branch created in subversion. This corresponds to the
1067 RELENG_8 branch in CVS.
1070 Bump the shared library version numbers for all libraries that do not
1071 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1072 __FreeBSD_version to 800105.
1075 Due to changes in the implementation of virtual network stack support,
1076 all network-related kernel modules must be recompiled. As this change
1077 breaks the ABI, bump __FreeBSD_version to 800104.
1080 The TOE interface to the TCP syncache has been modified to remove
1081 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1082 The cxgb driver is the only TOE consumer affected by this change, and
1083 needs to be recompiled along with the kernel. As this change breaks
1084 the ABI, bump __FreeBSD_version to 800103.
1087 Padding has been added to struct tcpcb, sackhint and tcpstat in
1088 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1089 maintaining the ABI. However, this change breaks the ABI, so bump
1090 __FreeBSD_version to 800102. User space tools that rely on the size of
1091 any of these structs (e.g. sockstat) need to be recompiled.
1094 The NFS_LEGACYRPC option has been removed along with the old kernel
1095 RPC implementation that this option selected. Kernel configurations
1096 may need to be adjusted.
1099 The network interface device nodes at /dev/net/<interface> have been
1100 removed. All ioctl operations can be performed the normal way using
1101 routing sockets. The kqueue functionality can generally be replaced
1102 with routing sockets.
1105 The documentation from the FreeBSD Documentation Project (Handbook,
1106 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1107 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1110 The ABI of various structures related to the SYSV IPC API have been
1111 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1112 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1116 Layout of struct vnet has changed as routing related variables were
1117 moved to their own Vimage module. Modules need to be recompiled. Bump
1118 __FreeBSD_version to 800099.
1121 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1122 respectively. As long as no more than 16 groups per process are used,
1123 no changes should be visible. When more than 16 groups are used, old
1124 binaries may fail if they call getgroups() or getgrouplist() with
1125 statically sized storage. Recompiling will work around this, but
1126 applications should be modified to use dynamically allocated storage
1127 for group arrays as POSIX.1-2008 does not cap an implementation's
1128 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1130 NFS and portalfs mounts may also be affected as the list of groups is
1131 truncated to 16. Users of NFS who use more than 16 groups, should
1132 take care that negative group permissions are not used on the exported
1133 file systems as they will not be reliable unless a GSSAPI based
1134 authentication method is used.
1137 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1138 option compiles in the support for adaptive spinning for lockmgrs
1139 which want to enable it. The lockinit() function now accepts the flag
1140 LK_ADAPTIVE in order to make the lock object subject to adaptive
1141 spinning when both held in write and read mode.
1144 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1145 changed. User applications that use this ioctl need to be rebuilt.
1148 The layout of struct thread has changed. Kernel and modules need to
1152 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1153 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1156 window(1) has been removed from the base system. It can now be
1157 installed from ports. The port is called misc/window.
1160 The way we are storing and accessing `routing table' entries has
1161 changed. Programs reading the FIB, like netstat, need to be
1165 A new netisr implementation has been added for FreeBSD 8. Network
1166 file system modules, such as igmp, ipdivert, and others, should be
1168 Bump __FreeBSD_version to 800096.
1171 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1175 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1176 Bump __FreeBSD_version to 800094.
1179 Add mnt_xflag field to 'struct mount'. File system modules need to be
1181 Bump __FreeBSD_version to 800093.
1184 The compiling option ADAPTIVE_SX has been retired while it has been
1185 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1186 The KPI for sx_init_flags() changes as accepting flags:
1187 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1188 been introduced in order to handle the reversed logic.
1189 Bump __FreeBSD_version to 800092.
1192 Add support for hierarchical jails. Remove global securelevel.
1193 Bump __FreeBSD_version to 800091.
1196 The layout of struct vnet_net has changed, therefore modules
1198 Bump __FreeBSD_version to 800090.
1201 The newly imported zic(8) produces a new format in the output. Please
1202 run tzsetup(8) to install the newly created data to /etc/localtime.
1205 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1206 hw.usb.* and is now consistent again with previous releases.
1209 802.11 monitor mode support was revised and driver api's were changed.
1210 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1211 of DLT_IEEE802_11. No user-visible data structures were changed but
1212 applications that use DLT_IEEE802_11 may require changes.
1213 Bump __FreeBSD_version to 800088.
1216 The layout of the following structs has changed: sysctl_oid,
1217 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1218 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1219 panics may be experienced. World rebuild is required for
1220 correctly checking networking state from userland.
1221 Bump __FreeBSD_version to 800085.
1224 MLDv2 and Source-Specific Multicast (SSM) have been merged
1225 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1226 The implementation of SSM within FreeBSD's IPv6 stack closely
1227 follows the IPv4 implementation.
1229 For kernel developers:
1231 * The most important changes are that the ip6_output() and
1232 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1233 and this lock has been downgraded to a non-recursive mutex.
1235 * As with the changes to the IPv4 stack to support SSM, filtering
1236 of inbound multicast traffic must now be performed by transport
1237 protocols within the IPv6 stack. This does not apply to TCP and
1238 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1240 * The KPIs used by IPv6 multicast are similar to those used by
1241 the IPv4 stack, with the following differences:
1242 * im6o_mc_filter() is analogous to imo_multicast_filter().
1243 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1244 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1245 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1246 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1247 for MLDv1 have an additional 'timer' argument which is used to
1248 jitter the initial membership report for the solicited-node
1249 multicast membership on-link.
1250 * This is not strictly needed for MLDv2, which already jitters
1251 its report transmissions. However, the 'timer' argument is
1252 preserved in case MLDv1 is active on the interface.
1254 * The KAME linked-list based IPv6 membership implementation has
1255 been refactored to use a vector similar to that used by the IPv4
1257 Code which maintains a list of its own multicast memberships
1258 internally, e.g. carp, has been updated to reflect the new
1261 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1262 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1263 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1264 implementation constraint which needs to be addressed in HEAD.
1266 For application developers:
1268 * The changes are broadly similar to those made for the IPv4
1271 * The use of IPv4 and IPv6 multicast socket options on the same
1272 socket, using mapped addresses, HAS NOT been tested or supported.
1274 * There are a number of issues with the implementation of various
1275 IPv6 multicast APIs which need to be resolved in the API surface
1276 before the implementation is fully compatible with KAME userland
1277 use, and these are mostly to do with interface index treatment.
1279 * The literature available discusses the use of either the delta / ASM
1280 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1281 using setsourcefilter(3)/getsourcefilter(3). For more information
1282 please refer to RFC 3768, 'Socket Interface Extensions for
1283 Multicast Source Filters'.
1285 * Applications which use the published RFC 3678 APIs should be fine.
1287 For systems administrators:
1289 * The mtest(8) utility has been refactored to support IPv6, in
1290 addition to IPv4. Interface addresses are no longer accepted
1291 as arguments, their names must be used instead. The utility
1292 will map the interface name to its first IPv4 address as
1293 returned by getifaddrs(3).
1295 * The ifmcstat(8) utility has also been updated to print the MLDv2
1296 endpoint state and source filter lists via sysctl(3).
1298 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1299 loopback of IPv6 multicast datagrams by default; it defaults to 1
1300 to preserve the existing behaviour. Disabling multicast loopback is
1301 recommended for optimal system performance.
1303 * The IPv6 MROUTING code has been changed to examine this sysctl
1304 instead of attempting to perform a group lookup before looping
1305 back forwarded datagrams.
1307 Bump __FreeBSD_version to 800084.
1310 Implement low-level Bluetooth HCI API.
1311 Bump __FreeBSD_version to 800083.
1314 The layout of struct malloc_type, used by modules to register new
1315 memory allocation types, has changed. Most modules will need to
1316 be rebuilt or panics may be experienced.
1317 Bump __FreeBSD_version to 800081.
1320 Anticipate overflowing inp_flags - add inp_flags2.
1321 This changes most offsets in inpcb, so checking v4 connection
1322 state will require a world rebuild.
1323 Bump __FreeBSD_version to 800080.
1326 Add an llentry to struct route and struct route_in6. Modules
1327 embedding a struct route will need to be recompiled.
1328 Bump __FreeBSD_version to 800079.
1331 The size of rt_metrics_lite and by extension rtentry has changed.
1332 Networking administration apps will need to be recompiled.
1333 The route command now supports show as an alias for get, weighting
1334 of routes, sticky and nostick flags to alter the behavior of stateful
1336 Bump __FreeBSD_version to 800078.
1339 Do not use Giant for kbdmux(4) locking. This is wrong and
1340 apparently causing more problems than it solves. This will
1341 re-open the issue where interrupt handlers may race with
1342 kbdmux(4) in polling mode. Typical symptoms include (but
1343 not limited to) duplicated and/or missing characters when
1344 low level console functions (such as gets) are used while
1345 interrupts are enabled (for example geli password prompt,
1346 mountroot prompt etc.). Disabling kbdmux(4) may help.
1349 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1350 kernel modules referencing any of the above need to be recompiled.
1351 Bump __FreeBSD_version to 800075.
1354 GEOM_PART has become the default partition slicer for storage devices,
1355 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1356 introduces some changes:
1358 MSDOS/EBR: the devices created from MSDOS extended partition entries
1359 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1360 to devices with offset-based names. fstabs may need to be modified.
1362 BSD: the "geometry does not match label" warning is harmless in most
1363 cases but it points to problems in file system misalignment with
1364 disk geometry. The "c" partition is now implicit, covers the whole
1365 top-level drive and cannot be (mis)used by users.
1367 General: Kernel dumps are now not allowed to be written to devices
1368 whose partition types indicate they are meant to be used for file
1369 systems (or, in case of MSDOS partitions, as something else than
1372 Most of these changes date approximately from 200812.
1375 The uscanner(4) driver has been removed from the kernel. This follows
1376 Linux removing theirs in 2.6 and making libusb the default interface
1377 (supported by sane).
1380 The multicast forwarding code has been cleaned up. netstat(1)
1381 only relies on KVM now for printing bandwidth upcall meters.
1382 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1383 ip6_mroute_mod respectively. The config(5) options for statically
1384 compiling this code remain the same, i.e. 'options MROUTING'.
1387 Support for the IFF_NEEDSGIANT network interface flag has been
1388 removed, which means that non-MPSAFE network device drivers are no
1389 longer supported. In particular, if_ar, if_sr, and network device
1390 drivers from the old (legacy) USB stack can no longer be built or
1394 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1395 a bunch of new language catalog files have also been added.
1396 This means that some common libc messages are now localized and
1397 they depend on the LC_MESSAGES environmental variable.
1400 The k8temp(4) driver has been renamed to amdtemp(4) since
1401 support for Family 10 and Family 11 CPU families was added.
1404 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1405 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1407 For kernel developers, the most important changes are that the
1408 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1409 and this lock has been downgraded to a non-recursive mutex.
1411 Transport protocols (UDP, Raw IP) are now responsible for filtering
1412 inbound multicast traffic according to group membership and source
1413 filters. The imo_multicast_filter() KPI exists for this purpose.
1414 Transports which do not use multicast (SCTP, TCP) already reject
1415 multicast by default. Forwarding and receive performance may improve
1416 as a mutex acquisition is no longer needed in the ip_input()
1417 low-level input path. in_addmulti() and in_delmulti() are shimmed
1418 to new KPIs which exist to support SSM in-kernel.
1420 For application developers, it is recommended that loopback of
1421 multicast datagrams be disabled for best performance, as this
1422 will still cause the lock to be taken for each looped-back
1423 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1424 be tuned to 0 to disable loopback by default; it defaults to 1
1425 to preserve the existing behaviour.
1427 For systems administrators, to obtain best performance with
1428 multicast reception and multiple groups, it is always recommended
1429 that a card with a suitably precise hash filter is used. Hash
1430 collisions will still result in the lock being taken within the
1431 transport protocol input path to check group membership.
1433 If deploying FreeBSD in an environment with IGMP snooping switches,
1434 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1435 enabled; this forces 224.0.0.0/24 group membership to be announced
1438 The size of 'struct igmpstat' has changed; netstat needs to be
1439 recompiled to reflect this.
1440 Bump __FreeBSD_version to 800070.
1443 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1444 updated to use it. This requires a buildworld/installworld in order to
1445 update the library and dependencies (usbconfig, etc). Its advisable to
1446 rebuild all ports which uses libusb. More specific directions are given
1447 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1448 libusb are no longer required and can be removed.
1451 A workaround is committed to allow the creation of System V shared
1452 memory segment of size > 2 GB on the 64-bit architectures.
1453 Due to a limitation of the existing ABI, the shm_segsz member
1454 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1455 wrong for large segments. Note that limits must be explicitly
1456 raised to allow such segments to be created.
1459 The layout of struct ifnet has changed, requiring a rebuild of all
1460 network device driver modules.
1463 The /dev handling for the new USB stack has changed, a
1464 buildworld/installworld is required for libusb20.
1467 The new USB2 stack has now been permanently moved in and all kernel and
1468 module names reverted to their previous values (eg, usb, ehci, ohci,
1469 ums, ...). The old usb stack can be compiled in by prefixing the name
1470 with the letter 'o', the old usb modules have been removed.
1471 Updating entry 20090216 for xorg and 20090215 for libmap may still
1475 The rc.conf(5) option if_up_delay has been renamed to
1476 defaultroute_delay to better reflect its purpose. If you have
1477 customized this setting in /etc/rc.conf you need to update it to
1481 xorg 7.4 wants to configure its input devices via hald which does not
1482 yet work with USB2. If the keyboard/mouse does not work in xorg then
1484 Option "AllowEmptyInput" "off"
1485 to your ServerLayout section. This will cause X to use the configured
1486 kbd and mouse sections from your xorg.conf.
1489 The GENERIC kernels for all architectures now default to the new USB2
1490 stack. No kernel config options or code have been removed so if a
1491 problem arises please report it and optionally revert to the old USB
1492 stack. If you are loading USB kernel modules or have a custom kernel
1493 that includes GENERIC then ensure that usb names are also changed over,
1494 eg uftdi -> usb2_serial_ftdi.
1496 Older programs linked against the ports libusb 0.1 need to be
1497 redirected to the new stack's libusb20. /etc/libmap.conf can
1499 # Map old usb library to new one for usb2 stack
1500 libusb-0.1.so.8 libusb20.so.1
1503 All USB ethernet devices now attach as interfaces under the name ueN
1504 (eg. ue0). This is to provide a predictable name as vendors often
1505 change usb chipsets in a product without notice.
1508 The ichsmb(4) driver has been changed to require SMBus slave
1509 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1510 All of the other SMBus controller drivers require left-justified
1511 slave addresses, so this change makes all the drivers provide the
1515 INET6 statistics (struct ip6stat) was updated.
1516 netstat(1) needs to be recompiled.
1519 NTFS has been removed from GENERIC kernel on amd64 to match
1520 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1521 will load ntfs.ko module automatically when NTFS support is
1522 actually needed, unless ntfs.ko is not installed or security
1523 level prohibits loading kernel modules. If either is the case,
1524 "options NTFS" has to be added into kernel config.
1527 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1528 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1529 800061. User space tools that rely on the size of struct tcpcb in
1530 tcp_var.h (e.g. sockstat) need to be recompiled.
1533 ng_tty(4) module updated to match the new TTY subsystem.
1534 Due to API change, user-level applications must be updated.
1535 New API support added to mpd5 CVS and expected to be present
1536 in next mpd5.3 release.
1539 With __FreeBSD_version 800060 the makefs tool is part of
1540 the base system (it was a port).
1543 The afdata and ifnet locks have been changed from mutexes to
1544 rwlocks, network modules will need to be re-compiled.
1547 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1548 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1549 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1550 architecture and 40 bytes on 64-bit architecture. The userland
1551 applications "arp" and "ndp" have been updated accordingly.
1552 The output from "netstat -r" shows only routing entries and
1553 none of the L2 information.
1556 __FreeBSD_version 800057 marks the switchover from the
1557 binary ath hal to source code. Users must add the line:
1559 options AH_SUPPORT_AR5416
1561 to their kernel config files when specifying:
1565 The ath_hal module no longer exists; the code is now compiled
1566 together with the driver in the ath module. It is now
1567 possible to tailor chip support (i.e. reduce the set of chips
1568 and thereby the code size); consult ath_hal(4) for details.
1571 __FreeBSD_version 800054 adds memory barriers to
1572 <machine/atomic.h>, new interfaces to ifnet to facilitate
1573 multiple hardware transmit queues for cards that support
1574 them, and a lock-less ring-buffer implementation to
1575 enable drivers to more efficiently manage queueing of
1579 A new version of ZFS (version 13) has been merged to -HEAD.
1580 This version has zpool attribute "listsnapshots" off by
1581 default, which means "zfs list" does not show snapshots,
1582 and is the same as Solaris behavior.
1585 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1588 The uhci, ohci, ehci and slhci USB Host controller drivers have
1589 been put into separate modules. If you load the usb module
1590 separately through loader.conf you will need to load the
1591 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1592 controller add the following to loader.conf:
1598 The ABI used by the PMC toolset has changed. Please keep
1599 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1603 atapci kernel module now includes only generic PCI ATA
1604 driver. AHCI driver moved to ataahci kernel module.
1605 All vendor-specific code moved into separate kernel modules:
1606 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1607 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1608 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1609 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1612 The TTY subsystem of the kernel has been replaced by a new
1613 implementation, which provides better scalability and an
1614 improved driver model. Most common drivers have been migrated to
1615 the new TTY subsystem, while others have not. The following
1616 drivers have not yet been ported to the new TTY layer:
1619 cy, digi, rc, rp, sio
1625 ng_h4, ng_tty, ppp, sl, snp
1627 Adding these drivers to your kernel configuration file shall
1628 cause compilation to fail.
1631 ntpd has been upgraded to 4.2.4p5.
1634 OpenSSH has been upgraded to 5.1p1.
1636 For many years, FreeBSD's version of OpenSSH preferred DSA
1637 over RSA for host and user authentication keys. With this
1638 upgrade, we've switched to the vendor's default of RSA over
1639 DSA. This may cause upgraded clients to warn about unknown
1640 host keys even for previously known hosts. Users should
1641 follow the usual procedure for verifying host keys before
1642 accepting the RSA key.
1644 This can be circumvented by setting the "HostKeyAlgorithms"
1645 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1648 Please note that the sequence of keys offered for
1649 authentication has been changed as well. You may want to
1650 specify IdentityFile in a different order to revert this
1654 The sio(4) driver has been removed from the i386 and amd64
1655 kernel configuration files. This means uart(4) is now the
1656 default serial port driver on those platforms as well.
1658 To prevent collisions with the sio(4) driver, the uart(4) driver
1659 uses different names for its device nodes. This means the
1660 onboard serial port will now most likely be called "ttyu0"
1661 instead of "ttyd0". You may need to reconfigure applications to
1662 use the new device names.
1664 When using the serial port as a boot console, be sure to update
1665 /boot/device.hints and /etc/ttys before booting the new kernel.
1666 If you forget to do so, you can still manually specify the hints
1667 at the loader prompt:
1669 set hint.uart.0.at="isa"
1670 set hint.uart.0.port="0x3F8"
1671 set hint.uart.0.flags="0x10"
1672 set hint.uart.0.irq="4"
1676 The gpt(8) utility has been removed. Use gpart(8) to partition
1680 The version that Linuxulator emulates was changed from 2.4.2
1681 to 2.6.16. If you experience any problems with Linux binaries
1682 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1683 if it fixes the problem contact emulation mailing list.
1686 ISDN4BSD (I4B) was removed from the src tree. You may need to
1687 update a your kernel configuration and remove relevant entries.
1690 I have checked in code to support multiple routing tables.
1691 See the man pages setfib(1) and setfib(2).
1692 This is a hopefully backwards compatible version,
1693 but to make use of it you need to compile your kernel
1694 with options ROUTETABLES=2 (or more up to 16).
1697 The 802.11 wireless support was redone to enable multi-bss
1698 operation on devices that are capable. The underlying device
1699 is no longer used directly but instead wlanX devices are
1700 cloned with ifconfig. This requires changes to rc.conf files.
1701 For example, change:
1702 ifconfig_ath0="WPA DHCP"
1705 ifconfig_wlan0="WPA DHCP"
1706 see rc.conf(5) for more details. In addition, mergemaster of
1707 /etc/rc.d is highly recommended. Simultaneous update of userland
1708 and kernel wouldn't hurt either.
1710 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1711 modules were merged into the base wlan module. All references
1712 to these modules (e.g. in kernel config files) must be removed.
1715 psm(4) has gained write(2) support in native operation level.
1716 Arbitrary commands can be written to /dev/psm%d and status can
1717 be read back from it. Therefore, an application is responsible
1718 for status validation and error recovery. It is a no-op in
1719 other operation levels.
1722 Support for KSE threading has been removed from the kernel. To
1723 run legacy applications linked against KSE libmap.conf may
1724 be used. The following libmap.conf may be used to ensure
1725 compatibility with any prior release:
1727 libpthread.so.1 libthr.so.1
1728 libpthread.so.2 libthr.so.2
1729 libkse.so.3 libthr.so.3
1732 The layout of struct vmspace has changed. This affects libkvm
1733 and any executables that link against libkvm and use the
1734 kvm_getprocs() function. In particular, but not exclusively,
1735 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1736 The effects are minimal, but it's advisable to upgrade world
1740 The latest em driver no longer has support in it for the
1741 82575 adapter, this is now moved to the igb driver. The
1742 split was done to make new features that are incompatible
1743 with older hardware easier to do.
1746 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1747 likewise the kernel option is now GEOM_LINUX_LVM.
1750 The default NFS mount mode has changed from UDP to TCP for
1751 increased reliability. If you rely on (insecurely) NFS
1752 mounting across a firewall you may need to update your
1756 Belatedly note the addition of m_collapse for compacting
1760 The fts(3) structures have been changed to use adequate
1761 integer types for their members and so to be able to cope
1762 with huge file trees. The old fts(3) ABI is preserved
1763 through symbol versioning in libc, so third-party binaries
1764 using fts(3) should still work, although they will not take
1765 advantage of the extended types. At the same time, some
1766 third-party software might fail to build after this change
1767 due to unportable assumptions made in its source code about
1768 fts(3) structure members. Such software should be fixed
1769 by its vendor or, in the worst case, in the ports tree.
1770 FreeBSD_version 800015 marks this change for the unlikely
1771 case that a portable fix is impossible.
1774 To upgrade to -current after this date, you must be running
1775 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1776 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1779 The ADAPTIVE_GIANT kernel option has been retired because its
1780 functionality is the default now.
1783 The AT keyboard emulation of sunkbd(4) has been turned on
1784 by default. In order to make the special symbols of the Sun
1785 keyboards driven by sunkbd(4) work under X these now have
1786 to be configured the same way as Sun USB keyboards driven
1787 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1789 Option "XkbLayout" "us"
1790 Option "XkbRules" "xorg"
1791 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1794 It has been decided that it is desirable to provide ABI
1795 backwards compatibility to the FreeBSD 4/5/6 versions of the
1796 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1797 broken with the introduction of PCI domain support (see the
1798 20070930 entry). Unfortunately, this required the ABI of
1799 PCIOCGETCONF to be broken again in order to be able to
1800 provide backwards compatibility to the old version of that
1801 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1802 again. As for prominent ports this affects neither pciutils
1803 nor xorg-server this time, the hal port needs to be rebuilt
1807 The misnamed kthread_create() and friends have been renamed
1808 to kproc_create() etc. Many of the callers already
1809 used kproc_start()..
1810 I will return kthread_create() and friends in a while
1811 with implementations that actually create threads, not procs.
1812 Renaming corresponds with version 800002.
1821 Avoid using make -j when upgrading. While generally safe, there are
1822 sometimes problems using -j to upgrade. If your upgrade fails with
1823 -j, please try again without -j. From time to time in the past there
1824 have been problems using -j with buildworld and/or installworld. This
1825 is especially true when upgrading between "distant" versions (eg one
1826 that cross a major release boundary or several minor releases, or when
1827 several months have passed on the -current branch).
1829 Sometimes, obscure build problems are the result of environment
1830 poisoning. This can happen because the make utility reads its
1831 environment when searching for values for global variables. To run
1832 your build attempts in an "environmental clean room", prefix all make
1833 commands with 'env -i '. See the env(1) manual page for more details.
1835 When upgrading from one major version to another it is generally best
1836 to upgrade to the latest code in the currently installed branch first,
1837 then do an upgrade to the new branch. This is the best-tested upgrade
1838 path, and has the highest probability of being successful. Please try
1839 this approach before reporting problems with a major version upgrade.
1841 When upgrading a live system, having a root shell around before
1842 installing anything can help undo problems. Not having a root shell
1843 around can lead to problems if pam has changed too much from your
1844 starting point to allow continued authentication after the upgrade.
1848 When upgrading the boot ZFS pool to a new version, always follow
1851 1.) recompile and reinstall the ZFS boot loader and boot block
1852 (this is part of "make buildworld" and "make installworld")
1854 2.) update the ZFS boot block on your boot drive
1856 The following example updates the ZFS boot block on the first
1857 partition (freebsd-boot) of a GPT partitioned drive ad0:
1858 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1860 Non-boot pools do not need these updates.
1864 If you are updating from a prior version of FreeBSD (even one just
1865 a few days old), you should follow this procedure. It is the most
1866 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1868 make kernel-toolchain
1869 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1870 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1872 To test a kernel once
1873 ---------------------
1874 If you just want to boot a kernel once (because you are not sure
1875 if it works, or if you want to boot a known bad kernel to provide
1876 debugging information) run
1877 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1878 nextboot -k testkernel
1880 To just build a kernel when you know that it won't mess you up
1881 --------------------------------------------------------------
1882 This assumes you are already running a CURRENT system. Replace
1883 ${arch} with the architecture of your machine (e.g. "i386",
1884 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1886 cd src/sys/${arch}/conf
1887 config KERNEL_NAME_HERE
1888 cd ../compile/KERNEL_NAME_HERE
1893 If this fails, go to the "To build a kernel" section.
1895 To rebuild everything and install it on the current system.
1896 -----------------------------------------------------------
1897 # Note: sometimes if you are running current you gotta do more than
1898 # is listed here if you are upgrading from a really old current.
1900 <make sure you have good level 0 dumps>
1902 make kernel KERNCONF=YOUR_KERNEL_HERE
1904 <reboot in single user> [3]
1911 To cross-install current onto a separate partition
1912 --------------------------------------------------
1913 # In this approach we use a separate partition to hold
1914 # current's root, 'usr', and 'var' directories. A partition
1915 # holding "/", "/usr" and "/var" should be about 2GB in
1918 <make sure you have good level 0 dumps>
1921 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1922 <maybe newfs current's root partition>
1923 <mount current's root partition on directory ${CURRENT_ROOT}>
1924 make installworld DESTDIR=${CURRENT_ROOT}
1925 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1926 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1927 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1928 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1929 <reboot into current>
1930 <do a "native" rebuild/install as described in the previous section>
1931 <maybe install compatibility libraries from ports/misc/compat*>
1935 To upgrade in-place from stable to current
1936 ----------------------------------------------
1937 <make sure you have good level 0 dumps>
1939 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1941 <reboot in single user> [3]
1948 Make sure that you've read the UPDATING file to understand the
1949 tweaks to various things you need. At this point in the life
1950 cycle of current, things change often and you are on your own
1951 to cope. The defaults can also change, so please read ALL of
1952 the UPDATING entries.
1954 Also, if you are tracking -current, you must be subscribed to
1955 freebsd-current@freebsd.org. Make sure that before you update
1956 your sources that you have read and understood all the recent
1957 messages there. If in doubt, please track -stable which has
1958 much fewer pitfalls.
1960 [1] If you have third party modules, such as vmware, you
1961 should disable them at this point so they don't crash your
1964 [3] From the bootblocks, boot -s, and then do
1969 adjkerntz -i # if CMOS is wall time
1970 Also, when doing a major release upgrade, it is required that
1971 you boot into single user mode to do the installworld.
1973 [4] Note: This step is non-optional. Failure to do this step
1974 can result in a significant reduction in the functionality of the
1975 system. Attempting to do it by hand is not recommended and those
1976 that pursue this avenue should read this file carefully, as well
1977 as the archives of freebsd-current and freebsd-hackers mailing lists
1978 for potential gotchas. The -U option is also useful to consider.
1979 See mergemaster(8) for more information.
1981 [5] Usually this step is a noop. However, from time to time
1982 you may need to do this if you get unknown user in the following
1983 step. It never hurts to do it all the time. You may need to
1984 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1985 install) after the buildworld before this step if you last updated
1986 from current before 20130425 or from -stable before 20130430.
1988 [6] This only deletes old files and directories. Old libraries
1989 can be deleted by "make delete-old-libs", but you have to make
1990 sure that no program is using those libraries anymore.
1992 [8] In order to have a kernel that can run the 4.x binaries needed to
1993 do an installworld, you must include the COMPAT_FREEBSD4 option in
1994 your kernel. Failure to do so may leave you with a system that is
1995 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1996 required to run the 5.x binaries on more recent kernels. And so on
1997 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1999 Make sure that you merge any new devices from GENERIC since the
2000 last time you updated your kernel config file.
2002 [9] When checking out sources, you must include the -P flag to have
2003 cvs prune empty directories.
2005 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
2006 "?=" instead of the "=" assignment operator, so that buildworld can
2007 override the CPUTYPE if it needs to.
2009 MAKEOBJDIRPREFIX must be defined in an environment variable, and
2010 not on the command line, or in /etc/make.conf. buildworld will
2011 warn if it is improperly defined.
2014 This file contains a list, in reverse chronological order, of major
2015 breakages in tracking -current. It is not guaranteed to be a complete
2016 list of such breakages, and only contains entries since October 10, 2007.
2017 If you need to see UPDATING entries from before that date, you will need
2018 to fetch an UPDATING file from an older FreeBSD release.
2020 Copyright information:
2022 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
2024 Redistribution, publication, translation and use, with or without
2025 modification, in full or in part, in any form or format of this
2026 document are permitted without further permission from the author.
2028 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
2029 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
2030 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
2031 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
2032 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
2033 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
2034 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
2035 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
2036 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
2037 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
2038 POSSIBILITY OF SUCH DAMAGE.
2040 Contact Warner Losh if you have any questions about your use of