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 head, and then rebuild without this option. The bootstrap process from
17 older version of current is a bit fragile.
19 NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
20 FreeBSD 10.x has many debugging features turned on, in both the kernel
21 and userland. These features attempt to detect incorrect use of
22 system primitives, and encourage loud failure through extra sanity
23 checking and fail stop semantics. They also substantially impact
24 system performance. If you want to do performance measurement,
25 benchmarking, and optimization, you'll want to turn them off. This
26 includes various WITNESS- related kernel options, INVARIANTS, malloc
27 debugging flags in userland, and various verbose features in the
28 kernel. Many developers choose to disable these features on build
29 machines to maximize performance. (To completely disable malloc
30 debugging, define MALLOC_PRODUCTION in /etc/make.conf, or to merely
31 disable the most expensive debugging functionality run
32 "ln -s 'abort:false,junk:false' /etc/malloc.conf".)
35 The GNU Compiler Collection and C++ standard library (libstdc++)
36 are no longer built by default on platforms where clang is the system
37 compiler. You can enable them with the WITH_GCC and WITH_GNUCXX
41 The PROCDESC kernel option is now part of the GENERIC kernel
42 configuration and is required for the rwhod(8) to work.
43 If you are using custom kernel configuration, you should include
47 The API and ABI related to the Capsicum framework was modified
48 in backward incompatible way. The userland libraries and programs
49 have to be recompiled to work with the new kernel. This includes the
50 following libraries and programs, but the whole buildworld is
51 advised: libc, libprocstat, dhclient, tcpdump, hastd, hastctl,
52 kdump, procstat, rwho, rwhod, uniq.
55 Thomas Dickey (vendor author thereof) reports that dialog(1) since
56 2011/10/18 has a bug in handling --hline. Testers and I noticed the
57 --hline is not ignored but displayed as a NULL string, regardless of
58 value. This will cause confusion in some bsdconfig dialogs where the
59 --hline is used to inform users which keybindings to use. This will
60 likewise affect any other persons relying on --hline. It also looks
61 rather strange seeing "[]" at the bottom of dialog(1) widgets when
62 passing --hline "anything". Thomas said he will have a look in a few
63 weeks. NOTE: The "[]" brackets appear with the left-edge where it
64 would normally appear given the width of text to display, but the
65 displayed text is not there (part of the bug).
68 The PADLOCK_RNG and RDRAND_RNG kernel options are now devices.
69 Thus "device padlock_rng" and "device rdrand_rng" should be
70 used instead of "options PADLOCK_RNG" & "options RDRAND_RNG".
73 WITH_ICONV has been split into two feature sets. WITH_ICONV now
74 enables just the iconv* functionality and is now on by default.
75 WITH_LIBICONV_COMPAT enables the libiconv api and link time
76 compatability. Set WITHOUT_ICONV to build the old way.
77 If you have been using WITH_ICONV before, you will very likely
78 need to turn on WITH_LIBICONV_COMPAT.
81 INVARIANTS option now enables DEBUG for code with OpenSolaris and
82 Illumos origin, including ZFS. If you have INVARIANTS in your
83 kernel configuration, then there is no need to set DEBUG or ZFS_DEBUG
85 DEBUG used to enable witness(9) tracking of OpenSolaris (mostly ZFS)
86 locks if WITNESS option was set. Because that generated a lot of
87 witness(9) reports and all of them were believed to be false
88 positives, this is no longer done. New option OPENSOLARIS_WITNESS
89 can be used to achieve the previous behavior.
92 Timer values in IPv6 data structures now use time_uptime instead
93 of time_second. Although this is not a user-visible functional
94 change, userland utilities which directly use them---ndp(8),
95 rtadvd(8), and rtsold(8) in the base system---need to be updated
99 find -delete can now delete the pathnames given as arguments,
100 instead of only files found below them or if the pathname did
101 not contain any slashes. Formerly, the following error message
104 find: -delete: <path>: relative path potentially not safe
106 Deleting the pathnames given as arguments can be prevented
107 without error messages using -mindepth 1 or by changing
108 directory and passing "." as argument to find. This works in the
109 old as well as the new version of find.
112 Behavior of devfs rules path matching has been changed.
113 Pattern is now always matched against fully qualified devfs
114 path and slash characters must be explicitly matched by
115 slashes in pattern (FNM_PATHNAME). Rulesets involving devfs
116 subdirectories must be reviewed.
119 The default ARM ABI has changed to the ARM EABI. The old ABI is
120 incompatible with the ARM EABI and all programs and modules will
121 need to be rebuilt to work with a new kernel.
123 To keep using the old ABI ensure the WITHOUT_ARM_EABI knob is set.
125 NOTE: Support for the old ABI will be removed in the future and
126 users are advised to upgrade.
129 pkg_install has been disconnected from the build if you really need it
130 you should add WITH_PKGTOOLS in your src.conf(5).
133 Most of network statistics structures were changed to be able
134 keep 64-bits counters. Thus all tools, that work with networking
135 statistics, must be rebuilt (netstat(1), bsnmpd(1), etc.)
138 Fix targets that run multiple make's to use && rather than ;
139 so that subsequent steps depend on success of previous.
141 NOTE: if building 'universe' with -j* on stable/8 or stable/9
142 it would be better to start the build using bmake, to avoid
143 overloading the machine.
146 Fix a bug that allowed a tracing process (e.g. gdb) to write
147 to a memory-mapped file in the traced process's address space
148 even if neither the traced process nor the tracing process had
149 write access to that file.
152 CVS has been removed from the base system. An exact copy
153 of the code is available from the devel/cvs port.
156 Some people report the following error after the switch to bmake:
158 make: illegal option -- J
159 usage: make [-BPSXeiknpqrstv] [-C directory] [-D variable]
161 *** [buildworld] Error code 2
163 this likely due to an old instance of make in
164 ${MAKEPATH} (${MAKEOBJDIRPREFIX}${.CURDIR}/make.${MACHINE})
165 which src/Makefile will use that blindly, if it exists, so if
166 you see the above error:
168 rm -rf `make -V MAKEPATH`
173 Use bmake by default.
174 Whereas before one could choose to build with bmake via
175 -DWITH_BMAKE one must now use -DWITHOUT_BMAKE to use the old
176 make. The goal is to remove these knobs for 10-RELEASE.
178 It is worth noting that bmake (like gmake) treats the command
179 line as the unit of failure, rather than statements within the
180 command line. Thus '(cd some/where && dosomething)' is safer
181 than 'cd some/where; dosomething'. The '()' allows consistent
182 behavior in parallel build.
185 Fix a bug that allows NFS clients to issue READDIR on files.
188 The WITHOUT_IDEA option has been removed because
189 the IDEA patent expired.
192 The sysctl which controls TRIM support under ZFS has been renamed
193 from vfs.zfs.trim_disable -> vfs.zfs.trim.enabled and has been
197 The mergemaster command now uses the default MAKEOBJDIRPREFIX
198 rather than creating it's own in the temporary directory in
199 order allow access to bootstrapped versions of tools such as
200 install and mtree. When upgrading from version of FreeBSD where
201 the install command does not support -l, you will need to
202 install a new mergemaster command if mergemaster -p is required.
203 This can be accomplished with the command (cd src/usr.sbin/mergemaster
207 Legacy ATA stack, disabled and replaced by new CAM-based one since
208 FreeBSD 9.0, completely removed from the sources. Kernel modules
209 atadisk and atapi*, user-level tools atacontrol and burncd are
210 removed. Kernel option `options ATA_CAM` is now permanently enabled
214 SOCK_CLOEXEC and SOCK_NONBLOCK flags have been added to socket(2)
215 and socketpair(2). Software, in particular Kerberos, may
216 automatically detect and use these during building. The resulting
217 binaries will not work on older kernels.
220 CTL_DISABLE has also been added to the sparc64 GENERIC (for further
221 information, see the respective 20130304 entry).
224 Recent commits to callout(9) changed the size of struct callout,
225 so the KBI is probably heavily disturbed. Also, some functions
226 in callout(9)/sleep(9)/sleepqueue(9)/condvar(9) KPIs were replaced
227 by macros. Every kernel module using it won't load, so rebuild
230 The ctl device has been re-enabled in GENERIC for i386 and amd64,
231 but does not initialize by default (because of the new CTL_DISABLE
232 option) to save memory. To re-enable it, remove the CTL_DISABLE
233 option from the kernel config file or set kern.cam.ctl.disable=0
234 in /boot/loader.conf.
237 The ctl device has been disabled in GENERIC for i386 and amd64.
238 This was done due to the extra memory being allocated at system
239 initialisation time by the ctl driver which was only used if
240 a CAM target device was created. This makes a FreeBSD system
241 unusable on 128MB or less of RAM.
244 A new compression method (lz4) has been merged to -HEAD. Please
245 refer to zpool-features(7) for more information.
247 Please refer to the "ZFS notes" section of this file for information
248 on upgrading boot ZFS pools.
251 A BSD-licensed patch(1) variant has been added and is installed
252 as bsdpatch, being the GNU version the default patch.
253 To inverse the logic and use the BSD-licensed one as default,
254 while having the GNU version installed as gnupatch, rebuild
255 and install world with the WITH_BSD_PATCH knob set.
258 Due to the use of the new -l option to install(1) during build
259 and install, you must take care not to directly set the INSTALL
260 make variable in your /etc/make.conf, /etc/src.conf, or on the
261 command line. If you wish to use the -C flag for all installs
262 you may be able to add INSTALL+=-C to /etc/make.conf or
266 The install(1) option -M has changed meaning and now takes an
267 argument that is a file or path to append logs to. In the
268 unlikely event that -M was the last option on the command line
269 and the command line contained at least two files and a target
270 directory the first file will have logs appended to it. The -M
271 option served little practical purpose in the last decade so its
272 use is expected to be extremely rare.
275 After switching to Clang as the default compiler some users of ZFS
276 on i386 systems started to experience stack overflow kernel panics.
277 Please consider using 'options KSTACK_PAGES=4' in such configurations.
280 GEOM_LABEL now mangles label names read from file system metadata.
281 Mangling affect labels containing spaces, non-printable characters,
282 '%' or '"'. Device names in /etc/fstab and other places may need to
286 By default, only the 10 most recent kernel dumps will be saved. To
287 restore the previous behaviour (no limit on the number of kernel dumps
288 stored in the dump directory) add the following line to /etc/rc.conf:
293 With the addition of auditdistd(8), a new auditdistd user is now
294 depended on during installworld. "mergemaster -p" can be used to add
295 the user prior to installworld, as documented in the handbook.
298 The sin6_scope_id member variable in struct sockaddr_in6 is now
299 filled by the kernel before passing the structure to the userland via
300 sysctl or routing socket. This means the KAME-specific embedded scope
301 id in sin6_addr.s6_addr[2] is always cleared in userland application.
302 This behavior can be controlled by net.inet6.ip6.deembed_scopeid.
303 __FreeBSD_version is bumped to 1000025.
306 On i386 and amd64 systems WITH_CLANG_IS_CC is now the default.
307 This means that the world and kernel will be compiled with clang
308 and that clang will be installed as /usr/bin/cc, /usr/bin/c++,
309 and /usr/bin/cpp. To disable this behavior and revert to building
310 with gcc, compile with WITHOUT_CLANG_IS_CC. Really old versions
311 of current may need to bootstrap WITHOUT_CLANG first if the clang
312 build fails (its compatibility window doesn't extend to the 9 stable
316 The IPFIREWALL_FORWARD kernel option has been removed. Its
317 functionality now turned on by default.
320 The ZERO_COPY_SOCKET kernel option has been removed and
321 split into SOCKET_SEND_COW and SOCKET_RECV_PFLIP.
322 NB: SOCKET_SEND_COW uses the VM page based copy-on-write
323 mechanism which is not safe and may result in kernel crashes.
324 NB: The SOCKET_RECV_PFLIP mechanism is useless as no current
325 driver supports disposeable external page sized mbuf storage.
326 Proper replacements for both zero-copy mechanisms are under
327 consideration and will eventually lead to complete removal
328 of the two kernel options.
331 The IPv4 network stack has been converted to network byte
332 order. The following modules need to be recompiled together
333 with kernel: carp(4), divert(4), gif(4), siftr(4), gre(4),
334 pf(4), ipfw(4), ng_ipfw(4), stf(4).
337 Support for non-MPSAFE filesystems was removed from VFS. The
338 VFS_VERSION was bumped, all filesystem modules shall be
342 All the non-MPSAFE filesystems have been disconnected from
343 the build. The full list includes: codafs, hpfs, ntfs, nwfs,
344 portalfs, smbfs, xfs.
347 The interface cloning API and ABI has changed. The following
348 modules need to be recompiled together with kernel:
349 ipfw(4), pfsync(4), pflog(4), usb(4), wlan(4), stf(4),
350 vlan(4), disc(4), edsc(4), if_bridge(4), gif(4), tap(4),
351 faith(4), epair(4), enc(4), tun(4), if_lagg(4), gre(4).
354 The sdhci driver was split in two parts: sdhci (generic SD Host
355 Controller logic) and sdhci_pci (actual hardware driver).
356 No kernel config modifications are required, but if you
357 load sdhc as a module you must switch to sdhci_pci instead.
360 Import the FUSE kernel and userland support into base system.
363 The GNU sort(1) program has been removed since the BSD-licensed
364 sort(1) has been the default for quite some time and no serious
365 problems have been reported. The corresponding WITH_GNU_SORT
369 The pfil(9) API/ABI for AF_INET family has been changed. Packet
370 filtering modules: pf(4), ipfw(4), ipfilter(4) need to be recompiled
374 The net80211(4) ABI has been changed to allow for improved driver
375 PS-POLL and power-save support. All wireless drivers need to be
376 recompiled to work with the new kernel.
379 The random(4) support for the VIA hardware random number
380 generator (`PADLOCK') is no longer enabled unconditionally.
381 Add the padlock_rng device in the custom kernel config if
382 needed. The GENERIC kernels on i386 and amd64 do include the
383 device, so the change only affects the custom kernel
387 The pf(4) packet filter ABI has been changed. pfctl(8) and
388 snmp_pf module need to be recompiled to work with new kernel.
391 A new ZFS feature flag "com.delphix:empty_bpobj" has been merged
392 to -HEAD. Pools that have empty_bpobj in active state can not be
393 imported read-write with ZFS implementations that do not support
394 this feature. For more information read the zpool-features(5)
398 The sparc64 ZFS loader has been changed to no longer try to auto-
399 detect ZFS providers based on diskN aliases but now requires these
400 to be explicitly listed in the OFW boot-device environment variable.
403 The OpenSSL has been upgraded to 1.0.1c. Any binaries requiring
404 libcrypto.so.6 or libssl.so.6 must be recompiled. Also, there are
405 configuration changes. Make sure to merge /etc/ssl/openssl.cnf.
408 The following sysctls and tunables have been renamed for consistency
409 with other variables:
410 kern.cam.da.da_send_ordered -> kern.cam.da.send_ordered
411 kern.cam.ada.ada_send_ordered -> kern.cam.ada.send_ordered
414 The sort utility has been replaced with BSD sort. For now, GNU sort
415 is also available as "gnusort" or the default can be set back to
416 GNU sort by setting WITH_GNU_SORT. In this case, BSD sort will be
417 installed as "bsdsort".
420 A new version of ZFS (pool version 5000) has been merged to -HEAD.
421 Starting with this version the old system of ZFS pool versioning
422 is superseded by "feature flags". This concept enables forward
423 compatibility against certain future changes in functionality of ZFS
424 pools. The first read-only compatible "feature flag" for ZFS pools
425 is named "com.delphix:async_destroy". For more information
426 read the new zpool-features(5) manual page.
427 Please refer to the "ZFS notes" section of this file for information
428 on upgrading boot ZFS pools.
431 The malloc(3) implementation embedded in libc now uses sources imported
432 as contrib/jemalloc. The most disruptive API change is to
433 /etc/malloc.conf. If your system has an old-style /etc/malloc.conf,
434 delete it prior to installworld, and optionally re-create it using the
435 new format after rebooting. See malloc.conf(5) for details
436 (specifically the TUNING section and the "opt.*" entries in the MALLCTL
440 Big-endian MIPS TARGET_ARCH values no longer end in "eb". mips64eb
441 is now spelled mips64. mipsn32eb is now spelled mipsn32. mipseb is
442 now spelled mips. This is to aid compatibility with third-party
443 software that expects this naming scheme in uname(3). Little-endian
444 settings are unchanged. If you are updating a big-endian mips64 machine
445 from before this change, you may need to set MACHINE_ARCH=mips64 in
446 your environment before the new build system will recognize your machine.
449 Disable by default the option VFS_ALLOW_NONMPSAFE for all supported
453 Now unix domain sockets behave "as expected" on nullfs(5). Previously
454 nullfs(5) did not pass through all behaviours to the underlying layer,
455 as a result if we bound to a socket on the lower layer we could connect
456 only to the lower path; if we bound to the upper layer we could connect
457 only to the upper path. The new behavior is one can connect to both the
458 lower and the upper paths regardless what layer path one binds to.
461 The getifaddrs upgrade path broken with 20111215 has been restored.
462 If you have upgraded in between 20111215 and 20120209 you need to
463 recompile libc again with your kernel. You still need to recompile
464 world to be able to configure CARP but this restriction already
468 The set_rcvar() function has been removed from /etc/rc.subr. All
469 base and ports rc.d scripts have been updated, so if you have a
470 port installed with a script in /usr/local/etc/rc.d you can either
471 hand-edit the rcvar= line, or reinstall the port.
473 An easy way to handle the mass-update of /etc/rc.d:
474 rm /etc/rc.d/* && mergemaster -i
477 panic(9) now stops other CPUs in the SMP systems, disables interrupts
478 on the current CPU and prevents other threads from running.
479 This behavior can be reverted using the kern.stop_scheduler_on_panic
481 The new behavior can be incompatible with kern.sync_on_panic.
484 The carp(4) facility has been changed significantly. Configuration
485 of the CARP protocol via ifconfig(8) has changed, as well as format
486 of CARP events submitted to devd(8) has changed. See manual pages
487 for more information. The arpbalance feature of carp(4) is currently
488 not supported anymore.
490 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
491 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
492 need to be recompiled.
495 The acpi_wmi(4) status device /dev/wmistat has been renamed to
499 The option VFS_ALLOW_NONMPSAFE option has been added in order to
500 explicitely support non-MPSAFE filesystems.
501 It is on by default for all supported platform at this present
505 The broken amd(4) driver has been replaced with esp(4) in the amd64,
506 i386 and pc98 GENERIC kernel configuration files.
509 sysinstall has been removed
512 The stable/9 branch created in subversion. This corresponds to the
513 RELENG_9 branch in CVS.
516 This commit modifies vfs_register() so that it uses a hash
517 calculation to set vfc_typenum, which is enabled by default.
518 The first time a system is booted after this change, the
519 vfc_typenum values will change for all file systems. The
520 main effect of this is a change to the NFS server file handles
521 for file systems that use vfc_typenum in their fsid, such as ZFS.
522 It will, however, prevent vfc_typenum from changing when file
523 systems are loaded in a different order for subsequent reboots.
524 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
525 until you are ready to remount all NFS clients after a reboot.
528 Bump the shared library version numbers for libraries that
529 do not use symbol versioning, have changed the ABI compared
530 to stable/8 and which shared library version was not bumped.
531 Done as part of 9.0-RELEASE cycle.
534 During the merge of Capsicum features, the fget(9) KPI was modified.
535 This may require the rebuilding of out-of-tree device drivers --
536 issues have been reported specifically with the nVidia device driver.
537 __FreeBSD_version is bumped to 900041.
539 Also, there is a period between 20110811 and 20110814 where the
540 special devices /dev/{stdin,stdout,stderr} did not work correctly.
541 Building world from a kernel during that window may not work.
544 The packet filter (pf) code has been updated to OpenBSD 4.5.
545 You need to update userland tools to be in sync with kernel.
546 This update breaks backward compatibility with earlier pfsync(4)
547 versions. Care must be taken when updating redundant firewall setups.
550 The following sysctls and tunables are retired on x86 platforms:
552 machdep.hlt_logical_cpus
553 The following sysctl is retired:
554 machdep.hyperthreading_allowed
555 The sysctls were supposed to provide a way to dynamically offline and
556 online selected CPUs on x86 platforms, but the implementation has not
557 been reliable especially with SCHED_ULE scheduler.
558 machdep.hyperthreading_allowed tunable is still available to ignore
559 hyperthreading CPUs at OS level.
560 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
561 where X is an APIC ID of a CPU. Be advised, though, that disabling
562 CPUs in non-uniform fashion will result in non-uniform topology and
563 may lead to sub-optimal system performance with SCHED_ULE, which is
567 cpumask_t type is retired and cpuset_t is used in order to describe
571 Changes to ifconfig(8) for dynamic address family detection mandate
572 that you are running a kernel of 20110525 or later. Make sure to
573 follow the update procedure to boot a new kernel before installing
577 Support for sun4v architecture is officially dropped
580 Several KPI breaking changes have been committed to the mii(4) layer,
581 the PHY drivers and consequently some Ethernet drivers using mii(4).
582 This means that miibus.ko and the modules of the affected Ethernet
583 drivers need to be recompiled.
585 Note to kernel developers: Given that the OUI bit reversion problem
586 was fixed as part of these changes all mii(4) commits related to OUIs,
587 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
588 handling, no longer can be merged verbatim to stable/8 and previous
592 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
593 into their kernel configurations along with 'device pci'.
596 The default NFS client is now the new NFS client, so fstype "newnfs"
597 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
598 Although mounts via fstype "nfs" will usually work without userland
599 changes, it is recommended that the mount(8) and mount_nfs(8)
600 commands be rebuilt from sources and that a link to mount_nfs called
601 mount_oldnfs be created. The new client is compiled into the
602 kernel with "options NFSCL" and this is needed for diskless root
603 file systems. The GENERIC kernel configs have been changed to use
604 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
605 To use the regular/old client, you can "mount -t oldnfs ...". For
606 a diskless root file system, you must also include a line like:
608 vfs.root.mountfrom="oldnfs:"
610 in the boot/loader.conf on the root fs on the NFS server to make
611 a diskless root fs use the old client.
614 The GENERIC kernels for all architectures now default to the new
615 CAM-based ATA stack. It means that all legacy ATA drivers were
616 removed and replaced by respective CAM drivers. If you are using
617 ATA device names in /etc/fstab or other places, make sure to update
618 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
619 where 'Y's are the sequential numbers starting from zero for each type
620 in order of detection, unless configured otherwise with tunables,
621 see cam(4)). There will be symbolic links created in /dev/ to map
622 old adX devices to the respective adaY. They should provide basic
623 compatibility for file systems mounting in most cases, but they do
624 not support old user-level APIs and do not have respective providers
625 in GEOM. Consider using updated management tools with new device names.
627 It is possible to load devices ahci, ata, siis and mvs as modules,
628 but option ATA_CAM should remain in kernel configuration to make ata
629 module work as CAM driver supporting legacy ATA controllers. Device ata
630 still can be used in modular fashion (atacore + ...). Modules atadisk
631 and atapi* are not used and won't affect operation in ATA_CAM mode.
632 Note that to use CAM-based ATA kernel should include CAM devices
633 scbus, pass, da (or explicitly ada), cd and optionally others. All of
634 them are parts of the cam module.
636 ataraid(4) functionality is now supported by the RAID GEOM class.
637 To use it you can load geom_raid kernel module and use graid(8) tool
638 for management. Instead of /dev/arX device names, use /dev/raid/rX.
640 No kernel config options or code have been removed, so if a problem
641 arises, please report it and optionally revert to the old ATA stack.
642 In order to do it you can remove from the kernel config:
647 , and instead add back:
648 device atadisk # ATA disk drives
649 device ataraid # ATA RAID drives
650 device atapicd # ATAPI CDROM drives
651 device atapifd # ATAPI floppy drives
652 device atapist # ATAPI tape drives
655 The default NFS server has been changed to the new server, which
656 was referred to as the experimental server. If you need to switch
657 back to the old NFS server, you must now put the "-o" option on
658 both the mountd and nfsd commands. This can be done using the
659 mountd_flags and nfs_server_flags rc.conf variables until an
660 update to the rc scripts is committed, which is coming soon.
663 The GNU Objective-C runtime library (libobjc), and other Objective-C
664 related components have been removed from the base system. If you
665 require an Objective-C library, please use one of the available ports.
668 ath(4) has been split into bus- and device- modules. if_ath contains
669 the HAL, the TX rate control and the network device code. if_ath_pci
670 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
671 contains the AHB glue. Users need to load both if_ath_pci and if_ath
672 in order to use ath on everything else.
674 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
675 need to load if_ath and if_ath_pci for ath(4) operation.
678 As part of the replacement of sysinstall, the process of building
679 release media has changed significantly. For details, please re-read
680 release(7), which has been updated to reflect the new build process.
683 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
684 is the last available version under GPLv2. It brings a number of new
685 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
686 4.1 and SSE 4.2), better support for powerpc64, a number of new
687 directives, and lots of other small improvements. See the ChangeLog
688 file in contrib/binutils for the full details.
691 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
692 compliant, and will now use half of hash for authentication.
693 This will break interoperability with all stacks (including all
694 actual FreeBSD versions) who implement
695 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
697 The only workaround with such peers is to use another HMAC
698 algorithm for IPsec ("phase 2") authentication.
701 Remove the uio_yield prototype and symbol. This function has
702 been misnamed since it was introduced and should not be
703 globally exposed with this name. The equivalent functionality
704 is now available using kern_yield(curthread->td_user_pri).
705 The function remains undocumented.
708 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
709 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
710 for scalar sysctls is defined but disabled. Code that needs
711 UQUAD to pass the type checking that must compile on older
712 systems where the define is not present can check against
713 __FreeBSD_version >= 900030.
715 The system dialog(1) has been replaced with a new version previously
716 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
717 with the previous version, but the libdialog associated with it has
718 a largely incompatible API. As such, the original version of libdialog
719 will be kept temporarily as libodialog, until its base system consumers
720 are replaced or updated. Bump __FreeBSD_version to 900030.
723 If you are trying to run make universe on a -stable system, and you get
724 the following warning:
725 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
726 unknown. config(8) likely too old."
727 or something similar to it, then you must upgrade your -stable system
728 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
729 stable/8) or build the config from the latest stable/8 branch and
730 install it on your system.
732 Prior to this date, building a current universe on 8-stable system from
733 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
734 error in the first kernel build phase. A new config on those old
735 systems will fix that problem for older versions of -current.
738 The TCP stack has been modified to allow Khelp modules to interact with
739 it via helper hook points and store per-connection data in the TCP
740 control block. Bump __FreeBSD_version to 900029. User space tools that
741 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
745 Generic IEEE 802.3 annex 31B full duplex flow control support has been
746 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
747 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
748 to take advantage of it instead of using custom implementations. This
749 means that these drivers now no longer unconditionally advertise
750 support for flow control but only do so if flow control is a selected
751 media option. This was implemented in the generic support that way in
752 order to allow flow control to be switched on and off via ifconfig(8)
753 with the PHY specific default to typically off in order to protect
754 from unwanted effects. Consequently, if you used flow control with
755 one of the above mentioned drivers you now need to explicitly enable
757 ifconfig bge0 media auto mediaopt flowcontrol
759 Along with the above mentioned changes generic support for setting
760 1000baseT master mode also has been added and brgphy(4), ciphy(4),
761 e1000phy(4) as well as ip1000phy(4) have been converted to take
762 advantage of it. This means that these drivers now no longer take the
763 link0 parameter for selecting master mode but the master media option
764 has to be used instead, for example like in the following:
765 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
767 Selection of master mode now is also available with all other PHY
768 drivers supporting 1000baseT.
771 The TCP stack has received a significant update to add support for
772 modularised congestion control and generally improve the clarity of
773 congestion control decisions. Bump __FreeBSD_version to 900025. User
774 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
775 sockstat) need to be recompiled.
778 The man(1) utility has been replaced by a new version that no longer
779 uses /etc/manpath.config. Please consult man.conf(5) for how to
780 migrate local entries to the new format.
783 The copyright strings printed by login(1) and sshd(8) at the time of a
784 new connection have been removed to follow other operating systems and
788 A workaround for a fixed ld bug has been removed in kernel code,
789 so make sure that your system ld is built from sources after
790 revision 210245 from 2010-07-19 (r211583 if building head kernel
791 on stable/8, r211584 for stable/7; both from 2010-08-21).
792 A symptom of incorrect ld version is different addresses for
793 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
796 The $ipv6_prefer variable in rc.conf(5) has been split into
797 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
799 The $ip6addrctl_policy is a variable to choose a pre-defined
800 address selection policy set by ip6addrctl(8). A value
801 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
804 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
805 flag (see an entry of 20090926) is set on an interface with no
806 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
807 security reason. If you want IPv6 link-local address on all
808 interfaces by default, set this to "YES".
810 The old ipv6_prefer="YES" is equivalent to
811 ipv6_activate_all_interfaces="YES" and
812 ip6addrctl_policy="ipv6_prefer".
815 DTrace has grown support for userland tracing. Due to this, DTrace is
816 now i386 and amd64 only.
817 dtruss(1) is now installed by default on those systems and a new
818 kernel module is needed for userland tracing: fasttrap.
819 No changes to your kernel config file are necessary to enable
820 userland tracing, but you might consider adding 'STRIP=' and
821 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
822 to have informative userland stack traces in DTrace (ustack).
825 The acpi_aiboost(4) driver has been removed in favor of the new
826 aibs(4) driver. You should update your kernel configuration file.
829 BSD grep has been imported to the base system and it is built by
830 default. It is completely BSD licensed, highly GNU-compatible, uses
831 less memory than its GNU counterpart and has a small codebase.
832 However, it is slower than its GNU counterpart, which is mostly
833 noticeable for larger searches, for smaller ones it is measurable
834 but not significant. The reason is complex, the most important factor
835 is that we lack a modern and efficient regex library and GNU
836 overcomes this by optimizing the searches internally. Future work
837 on improving the regex performance is planned, for the meantime,
838 users that need better performance, can build GNU grep instead by
839 setting the WITH_GNU_GREP knob.
842 Due to the import of powerpc64 support, all existing powerpc kernel
843 configuration files must be updated with a machine directive like this:
844 machine powerpc powerpc
846 In addition, an updated config(8) is required to build powerpc kernels
850 A new version of ZFS (version 15) has been merged to -HEAD.
851 This version uses a python library for the following subcommands:
852 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
853 For full functionality of these commands the following port must
854 be installed: sysutils/py-zfs
857 'vm_page's are now hashed by physical address to an array of mutexes.
858 Currently this is only used to serialize access to hold_count. Over
859 time the page queue mutex will be peeled away. This changes the size
860 of pmap on every architecture. And requires all callers of vm_page_hold
861 and vm_page_unhold to be updated.
864 WITH_CTF can now be specified in src.conf (not recommended, there
865 are some problems with static executables), make.conf (would also
866 affect ports which do not use GNU make and do not override the
867 compile targets) or in the kernel config (via "makeoptions
869 When WITH_CTF was specified there before this was silently ignored,
870 so make sure that WITH_CTF is not used in places which could lead
871 to unwanted behavior.
874 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
875 to allow 32-bit compatibility on non-x86 platforms. All kernel
876 configurations on amd64 and ia64 platforms using these options must
877 be modified accordingly.
880 The utmp user accounting database has been replaced with utmpx,
881 the user accounting interface standardized by POSIX.
882 Unfortunately the semantics of utmp and utmpx don't match,
883 making it practically impossible to support both interfaces.
884 The user accounting database is used by tools like finger(1),
885 last(1), talk(1), w(1) and ac(8).
887 All applications in the base system use utmpx. This means only
888 local binaries (e.g. from the ports tree) may still use these
889 utmp database files. These applications must be rebuilt to make
892 After the system has been upgraded, it is safe to remove the old
893 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
894 assuming their contents is of no importance anymore. Old wtmp
895 databases can only be used by last(1) and ac(8) after they have
896 been converted to the new format using wtmpcvt(1).
899 Introduce the kernel thread "deadlock resolver" (which can be enabled
900 via the DEADLKRES option, see NOTES for more details) and the
901 sleepq_type() function for sleepqueues.
904 The rc.firewall and rc.firewall6 were unified, and
905 rc.firewall6 and rc.d/ip6fw were removed.
906 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
907 variables are obsoleted. Instead, the following new rc
908 variables are added to rc.d/ipfw:
910 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
911 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
912 firewall_simple_onet_ipv6, firewall_trusted_ipv6
914 The meanings correspond to the relevant IPv4 variables.
920 The default terminal emulation for syscons(4) has been changed
921 from cons25 to xterm on all platforms except pc98. This means
922 that the /etc/ttys file needs to be updated to ensure correct
923 operation of applications on the console.
925 The terminal emulation style can be toggled per window by using
926 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
927 options can be used to change the compile-time default back to
930 To prevent graphical artifacts, make sure the TERM environment
931 variable is set to match the terminal emulation that is being
932 performed by syscons(4).
935 The layout of the structure ieee80211req_scan_result has changed.
936 Applications that require wireless scan results (e.g. ifconfig(8))
937 from net80211 need to be recompiled.
939 Applications such as wpa_supplicant(8) may require a full world
940 build without using NO_CLEAN in order to get synchronized with the
944 The iwn(4) driver has been updated to support the 5000 and 5150 series.
945 There's one kernel module for each firmware. Adding "device iwnfw"
946 to the kernel configuration file means including all three firmware
947 images inside the kernel. If you want to include just the one for
948 your wireless card, use the devices iwn4965fw, iwn5000fw or
952 The rc.d/network_ipv6, IPv6 configuration script has been integrated
953 into rc.d/netif. The changes are the following:
955 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
956 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
957 Note that both variables need the "inet6" keyword at the head.
959 Do not set $ipv6_network_interfaces manually if you do not
960 understand what you are doing. It is not needed in most cases.
962 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
965 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
966 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
968 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
969 all configured interfaces have "inet6 accept_rtadv" in the
970 $ifconfig_IF_ipv6. These are for backward compatibility.
972 3. A new variable $ipv6_prefer has been added. If NO, IPv6
973 functionality of interfaces with no corresponding
974 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
975 and the default address selection policy of ip6addrctl(8)
976 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
977 Note that if you want to configure IPv6 functionality on the
978 disabled interfaces after boot, first you need to clear the flag by
979 using ifconfig(8) like:
981 ifconfig em0 inet6 -ifdisabled
983 If YES, the default address selection policy is set as
986 The default value of $ipv6_prefer is NO.
988 4. If your system need to receive Router Advertisement messages,
989 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
990 scripts automatically invoke rtsol(8) when the interface becomes
991 UP. The Router Advertisement messages are used for SLAAC
992 (State-Less Address AutoConfiguration).
995 802.11s D3.03 support was committed. This is incompatible with the
996 previous code, which was based on D3.0.
999 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
1000 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
1001 control whether accepting Router Advertisement messages or not.
1002 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
1003 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
1004 The ifconfig(8) utility now supports these flags.
1007 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
1008 mount(8) and -a option for df(1) to see them.
1011 The old tunable hw.bus.devctl_disable has been superseded by
1012 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
1013 replaced by hw.bus.devctl_queue=0. The default for this new tunable
1017 Remove the option STOP_NMI. The default action is now to use NMI only
1018 for KDB via the newly introduced function stop_cpus_hard() and
1019 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
1022 The stable/8 branch created in subversion. This corresponds to the
1023 RELENG_8 branch in CVS.
1026 Bump the shared library version numbers for all libraries that do not
1027 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
1028 __FreeBSD_version to 800105.
1031 Due to changes in the implementation of virtual network stack support,
1032 all network-related kernel modules must be recompiled. As this change
1033 breaks the ABI, bump __FreeBSD_version to 800104.
1036 The TOE interface to the TCP syncache has been modified to remove
1037 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
1038 The cxgb driver is the only TOE consumer affected by this change, and
1039 needs to be recompiled along with the kernel. As this change breaks
1040 the ABI, bump __FreeBSD_version to 800103.
1043 Padding has been added to struct tcpcb, sackhint and tcpstat in
1044 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
1045 maintaining the ABI. However, this change breaks the ABI, so bump
1046 __FreeBSD_version to 800102. User space tools that rely on the size of
1047 any of these structs (e.g. sockstat) need to be recompiled.
1050 The NFS_LEGACYRPC option has been removed along with the old kernel
1051 RPC implementation that this option selected. Kernel configurations
1052 may need to be adjusted.
1055 The network interface device nodes at /dev/net/<interface> have been
1056 removed. All ioctl operations can be performed the normal way using
1057 routing sockets. The kqueue functionality can generally be replaced
1058 with routing sockets.
1061 The documentation from the FreeBSD Documentation Project (Handbook,
1062 FAQ, etc.) is now installed via packages by sysinstall(8) and under
1063 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
1066 The ABI of various structures related to the SYSV IPC API have been
1067 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
1068 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
1072 Layout of struct vnet has changed as routing related variables were
1073 moved to their own Vimage module. Modules need to be recompiled. Bump
1074 __FreeBSD_version to 800099.
1077 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
1078 respectively. As long as no more than 16 groups per process are used,
1079 no changes should be visible. When more than 16 groups are used, old
1080 binaries may fail if they call getgroups() or getgrouplist() with
1081 statically sized storage. Recompiling will work around this, but
1082 applications should be modified to use dynamically allocated storage
1083 for group arrays as POSIX.1-2008 does not cap an implementation's
1084 number of supported groups at NGROUPS_MAX+1 as previous versions did.
1086 NFS and portalfs mounts may also be affected as the list of groups is
1087 truncated to 16. Users of NFS who use more than 16 groups, should
1088 take care that negative group permissions are not used on the exported
1089 file systems as they will not be reliable unless a GSSAPI based
1090 authentication method is used.
1093 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
1094 option compiles in the support for adaptive spinning for lockmgrs
1095 which want to enable it. The lockinit() function now accepts the flag
1096 LK_ADAPTIVE in order to make the lock object subject to adaptive
1097 spinning when both held in write and read mode.
1100 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
1101 changed. User applications that use this ioctl need to be rebuilt.
1104 The layout of struct thread has changed. Kernel and modules need to
1108 The layout of structs ifnet, domain, protosw and vnet_net has changed.
1109 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
1112 window(1) has been removed from the base system. It can now be
1113 installed from ports. The port is called misc/window.
1116 The way we are storing and accessing `routing table' entries has
1117 changed. Programs reading the FIB, like netstat, need to be
1121 A new netisr implementation has been added for FreeBSD 8. Network
1122 file system modules, such as igmp, ipdivert, and others, should be
1124 Bump __FreeBSD_version to 800096.
1127 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
1131 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
1132 Bump __FreeBSD_version to 800094.
1135 Add mnt_xflag field to 'struct mount'. File system modules need to be
1137 Bump __FreeBSD_version to 800093.
1140 The compiling option ADAPTIVE_SX has been retired while it has been
1141 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
1142 The KPI for sx_init_flags() changes as accepting flags:
1143 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
1144 been introduced in order to handle the reversed logic.
1145 Bump __FreeBSD_version to 800092.
1148 Add support for hierarchical jails. Remove global securelevel.
1149 Bump __FreeBSD_version to 800091.
1152 The layout of struct vnet_net has changed, therefore modules
1154 Bump __FreeBSD_version to 800090.
1157 The newly imported zic(8) produces a new format in the output. Please
1158 run tzsetup(8) to install the newly created data to /etc/localtime.
1161 The sysctl tree for the usb stack has renamed from hw.usb2.* to
1162 hw.usb.* and is now consistent again with previous releases.
1165 802.11 monitor mode support was revised and driver api's were changed.
1166 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
1167 of DLT_IEEE802_11. No user-visible data structures were changed but
1168 applications that use DLT_IEEE802_11 may require changes.
1169 Bump __FreeBSD_version to 800088.
1172 The layout of the following structs has changed: sysctl_oid,
1173 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
1174 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
1175 panics may be experienced. World rebuild is required for
1176 correctly checking networking state from userland.
1177 Bump __FreeBSD_version to 800085.
1180 MLDv2 and Source-Specific Multicast (SSM) have been merged
1181 to the IPv6 stack. VIMAGE hooks are in but not yet used.
1182 The implementation of SSM within FreeBSD's IPv6 stack closely
1183 follows the IPv4 implementation.
1185 For kernel developers:
1187 * The most important changes are that the ip6_output() and
1188 ip6_input() paths no longer take the IN6_MULTI_LOCK,
1189 and this lock has been downgraded to a non-recursive mutex.
1191 * As with the changes to the IPv4 stack to support SSM, filtering
1192 of inbound multicast traffic must now be performed by transport
1193 protocols within the IPv6 stack. This does not apply to TCP and
1194 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
1196 * The KPIs used by IPv6 multicast are similar to those used by
1197 the IPv4 stack, with the following differences:
1198 * im6o_mc_filter() is analogous to imo_multicast_filter().
1199 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
1200 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
1201 * IN6_LOOKUP_MULTI() has been deprecated and removed.
1202 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
1203 for MLDv1 have an additional 'timer' argument which is used to
1204 jitter the initial membership report for the solicited-node
1205 multicast membership on-link.
1206 * This is not strictly needed for MLDv2, which already jitters
1207 its report transmissions. However, the 'timer' argument is
1208 preserved in case MLDv1 is active on the interface.
1210 * The KAME linked-list based IPv6 membership implementation has
1211 been refactored to use a vector similar to that used by the IPv4
1213 Code which maintains a list of its own multicast memberships
1214 internally, e.g. carp, has been updated to reflect the new
1217 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
1218 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
1219 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
1220 implementation constraint which needs to be addressed in HEAD.
1222 For application developers:
1224 * The changes are broadly similar to those made for the IPv4
1227 * The use of IPv4 and IPv6 multicast socket options on the same
1228 socket, using mapped addresses, HAS NOT been tested or supported.
1230 * There are a number of issues with the implementation of various
1231 IPv6 multicast APIs which need to be resolved in the API surface
1232 before the implementation is fully compatible with KAME userland
1233 use, and these are mostly to do with interface index treatment.
1235 * The literature available discusses the use of either the delta / ASM
1236 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
1237 using setsourcefilter(3)/getsourcefilter(3). For more information
1238 please refer to RFC 3768, 'Socket Interface Extensions for
1239 Multicast Source Filters'.
1241 * Applications which use the published RFC 3678 APIs should be fine.
1243 For systems administrators:
1245 * The mtest(8) utility has been refactored to support IPv6, in
1246 addition to IPv4. Interface addresses are no longer accepted
1247 as arguments, their names must be used instead. The utility
1248 will map the interface name to its first IPv4 address as
1249 returned by getifaddrs(3).
1251 * The ifmcstat(8) utility has also been updated to print the MLDv2
1252 endpoint state and source filter lists via sysctl(3).
1254 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
1255 loopback of IPv6 multicast datagrams by default; it defaults to 1
1256 to preserve the existing behaviour. Disabling multicast loopback is
1257 recommended for optimal system performance.
1259 * The IPv6 MROUTING code has been changed to examine this sysctl
1260 instead of attempting to perform a group lookup before looping
1261 back forwarded datagrams.
1263 Bump __FreeBSD_version to 800084.
1266 Implement low-level Bluetooth HCI API.
1267 Bump __FreeBSD_version to 800083.
1270 The layout of struct malloc_type, used by modules to register new
1271 memory allocation types, has changed. Most modules will need to
1272 be rebuilt or panics may be experienced.
1273 Bump __FreeBSD_version to 800081.
1276 Anticipate overflowing inp_flags - add inp_flags2.
1277 This changes most offsets in inpcb, so checking v4 connection
1278 state will require a world rebuild.
1279 Bump __FreeBSD_version to 800080.
1282 Add an llentry to struct route and struct route_in6. Modules
1283 embedding a struct route will need to be recompiled.
1284 Bump __FreeBSD_version to 800079.
1287 The size of rt_metrics_lite and by extension rtentry has changed.
1288 Networking administration apps will need to be recompiled.
1289 The route command now supports show as an alias for get, weighting
1290 of routes, sticky and nostick flags to alter the behavior of stateful
1292 Bump __FreeBSD_version to 800078.
1295 Do not use Giant for kbdmux(4) locking. This is wrong and
1296 apparently causing more problems than it solves. This will
1297 re-open the issue where interrupt handlers may race with
1298 kbdmux(4) in polling mode. Typical symptoms include (but
1299 not limited to) duplicated and/or missing characters when
1300 low level console functions (such as gets) are used while
1301 interrupts are enabled (for example geli password prompt,
1302 mountroot prompt etc.). Disabling kbdmux(4) may help.
1305 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
1306 kernel modules referencing any of the above need to be recompiled.
1307 Bump __FreeBSD_version to 800075.
1310 GEOM_PART has become the default partition slicer for storage devices,
1311 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
1312 introduces some changes:
1314 MSDOS/EBR: the devices created from MSDOS extended partition entries
1315 (EBR) can be named differently than with GEOM_MBR and are now symlinks
1316 to devices with offset-based names. fstabs may need to be modified.
1318 BSD: the "geometry does not match label" warning is harmless in most
1319 cases but it points to problems in file system misalignment with
1320 disk geometry. The "c" partition is now implicit, covers the whole
1321 top-level drive and cannot be (mis)used by users.
1323 General: Kernel dumps are now not allowed to be written to devices
1324 whose partition types indicate they are meant to be used for file
1325 systems (or, in case of MSDOS partitions, as something else than
1328 Most of these changes date approximately from 200812.
1331 The uscanner(4) driver has been removed from the kernel. This follows
1332 Linux removing theirs in 2.6 and making libusb the default interface
1333 (supported by sane).
1336 The multicast forwarding code has been cleaned up. netstat(1)
1337 only relies on KVM now for printing bandwidth upcall meters.
1338 The IPv4 and IPv6 modules are split into ip_mroute_mod and
1339 ip6_mroute_mod respectively. The config(5) options for statically
1340 compiling this code remain the same, i.e. 'options MROUTING'.
1343 Support for the IFF_NEEDSGIANT network interface flag has been
1344 removed, which means that non-MPSAFE network device drivers are no
1345 longer supported. In particular, if_ar, if_sr, and network device
1346 drivers from the old (legacy) USB stack can no longer be built or
1350 POSIX.1 Native Language Support (NLS) has been enabled in libc and
1351 a bunch of new language catalog files have also been added.
1352 This means that some common libc messages are now localized and
1353 they depend on the LC_MESSAGES environmental variable.
1356 The k8temp(4) driver has been renamed to amdtemp(4) since
1357 support for Family 10 and Family 11 CPU families was added.
1360 IGMPv3 and Source-Specific Multicast (SSM) have been merged
1361 to the IPv4 stack. VIMAGE hooks are in but not yet used.
1363 For kernel developers, the most important changes are that the
1364 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
1365 and this lock has been downgraded to a non-recursive mutex.
1367 Transport protocols (UDP, Raw IP) are now responsible for filtering
1368 inbound multicast traffic according to group membership and source
1369 filters. The imo_multicast_filter() KPI exists for this purpose.
1370 Transports which do not use multicast (SCTP, TCP) already reject
1371 multicast by default. Forwarding and receive performance may improve
1372 as a mutex acquisition is no longer needed in the ip_input()
1373 low-level input path. in_addmulti() and in_delmulti() are shimmed
1374 to new KPIs which exist to support SSM in-kernel.
1376 For application developers, it is recommended that loopback of
1377 multicast datagrams be disabled for best performance, as this
1378 will still cause the lock to be taken for each looped-back
1379 datagram transmission. The net.inet.ip.mcast.loop sysctl may
1380 be tuned to 0 to disable loopback by default; it defaults to 1
1381 to preserve the existing behaviour.
1383 For systems administrators, to obtain best performance with
1384 multicast reception and multiple groups, it is always recommended
1385 that a card with a suitably precise hash filter is used. Hash
1386 collisions will still result in the lock being taken within the
1387 transport protocol input path to check group membership.
1389 If deploying FreeBSD in an environment with IGMP snooping switches,
1390 it is recommended that the net.inet.igmp.sendlocal sysctl remain
1391 enabled; this forces 224.0.0.0/24 group membership to be announced
1394 The size of 'struct igmpstat' has changed; netstat needs to be
1395 recompiled to reflect this.
1396 Bump __FreeBSD_version to 800070.
1399 libusb20.so.1 is now installed as libusb.so.1 and the ports system
1400 updated to use it. This requires a buildworld/installworld in order to
1401 update the library and dependencies (usbconfig, etc). Its advisable to
1402 rebuild all ports which uses libusb. More specific directions are given
1403 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
1404 libusb are no longer required and can be removed.
1407 A workaround is committed to allow the creation of System V shared
1408 memory segment of size > 2 GB on the 64-bit architectures.
1409 Due to a limitation of the existing ABI, the shm_segsz member
1410 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
1411 wrong for large segments. Note that limits must be explicitly
1412 raised to allow such segments to be created.
1415 The layout of struct ifnet has changed, requiring a rebuild of all
1416 network device driver modules.
1419 The /dev handling for the new USB stack has changed, a
1420 buildworld/installworld is required for libusb20.
1423 The new USB2 stack has now been permanently moved in and all kernel and
1424 module names reverted to their previous values (eg, usb, ehci, ohci,
1425 ums, ...). The old usb stack can be compiled in by prefixing the name
1426 with the letter 'o', the old usb modules have been removed.
1427 Updating entry 20090216 for xorg and 20090215 for libmap may still
1431 The rc.conf(5) option if_up_delay has been renamed to
1432 defaultroute_delay to better reflect its purpose. If you have
1433 customized this setting in /etc/rc.conf you need to update it to
1437 xorg 7.4 wants to configure its input devices via hald which does not
1438 yet work with USB2. If the keyboard/mouse does not work in xorg then
1440 Option "AllowEmptyInput" "off"
1441 to your ServerLayout section. This will cause X to use the configured
1442 kbd and mouse sections from your xorg.conf.
1445 The GENERIC kernels for all architectures now default to the new USB2
1446 stack. No kernel config options or code have been removed so if a
1447 problem arises please report it and optionally revert to the old USB
1448 stack. If you are loading USB kernel modules or have a custom kernel
1449 that includes GENERIC then ensure that usb names are also changed over,
1450 eg uftdi -> usb2_serial_ftdi.
1452 Older programs linked against the ports libusb 0.1 need to be
1453 redirected to the new stack's libusb20. /etc/libmap.conf can
1455 # Map old usb library to new one for usb2 stack
1456 libusb-0.1.so.8 libusb20.so.1
1459 All USB ethernet devices now attach as interfaces under the name ueN
1460 (eg. ue0). This is to provide a predictable name as vendors often
1461 change usb chipsets in a product without notice.
1464 The ichsmb(4) driver has been changed to require SMBus slave
1465 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1466 All of the other SMBus controller drivers require left-justified
1467 slave addresses, so this change makes all the drivers provide the
1471 INET6 statistics (struct ip6stat) was updated.
1472 netstat(1) needs to be recompiled.
1475 NTFS has been removed from GENERIC kernel on amd64 to match
1476 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1477 will load ntfs.ko module automatically when NTFS support is
1478 actually needed, unless ntfs.ko is not installed or security
1479 level prohibits loading kernel modules. If either is the case,
1480 "options NTFS" has to be added into kernel config.
1483 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1484 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1485 800061. User space tools that rely on the size of struct tcpcb in
1486 tcp_var.h (e.g. sockstat) need to be recompiled.
1489 ng_tty(4) module updated to match the new TTY subsystem.
1490 Due to API change, user-level applications must be updated.
1491 New API support added to mpd5 CVS and expected to be present
1492 in next mpd5.3 release.
1495 With __FreeBSD_version 800060 the makefs tool is part of
1496 the base system (it was a port).
1499 The afdata and ifnet locks have been changed from mutexes to
1500 rwlocks, network modules will need to be re-compiled.
1503 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1504 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1505 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1506 architecture and 40 bytes on 64-bit architecture. The userland
1507 applications "arp" and "ndp" have been updated accordingly.
1508 The output from "netstat -r" shows only routing entries and
1509 none of the L2 information.
1512 __FreeBSD_version 800057 marks the switchover from the
1513 binary ath hal to source code. Users must add the line:
1515 options AH_SUPPORT_AR5416
1517 to their kernel config files when specifying:
1521 The ath_hal module no longer exists; the code is now compiled
1522 together with the driver in the ath module. It is now
1523 possible to tailor chip support (i.e. reduce the set of chips
1524 and thereby the code size); consult ath_hal(4) for details.
1527 __FreeBSD_version 800054 adds memory barriers to
1528 <machine/atomic.h>, new interfaces to ifnet to facilitate
1529 multiple hardware transmit queues for cards that support
1530 them, and a lock-less ring-buffer implementation to
1531 enable drivers to more efficiently manage queueing of
1535 A new version of ZFS (version 13) has been merged to -HEAD.
1536 This version has zpool attribute "listsnapshots" off by
1537 default, which means "zfs list" does not show snapshots,
1538 and is the same as Solaris behavior.
1541 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1544 The uhci, ohci, ehci and slhci USB Host controller drivers have
1545 been put into separate modules. If you load the usb module
1546 separately through loader.conf you will need to load the
1547 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1548 controller add the following to loader.conf:
1554 The ABI used by the PMC toolset has changed. Please keep
1555 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1559 atapci kernel module now includes only generic PCI ATA
1560 driver. AHCI driver moved to ataahci kernel module.
1561 All vendor-specific code moved into separate kernel modules:
1562 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1563 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1564 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1565 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1568 The TTY subsystem of the kernel has been replaced by a new
1569 implementation, which provides better scalability and an
1570 improved driver model. Most common drivers have been migrated to
1571 the new TTY subsystem, while others have not. The following
1572 drivers have not yet been ported to the new TTY layer:
1575 cy, digi, rc, rp, sio
1581 ng_h4, ng_tty, ppp, sl, snp
1583 Adding these drivers to your kernel configuration file shall
1584 cause compilation to fail.
1587 ntpd has been upgraded to 4.2.4p5.
1590 OpenSSH has been upgraded to 5.1p1.
1592 For many years, FreeBSD's version of OpenSSH preferred DSA
1593 over RSA for host and user authentication keys. With this
1594 upgrade, we've switched to the vendor's default of RSA over
1595 DSA. This may cause upgraded clients to warn about unknown
1596 host keys even for previously known hosts. Users should
1597 follow the usual procedure for verifying host keys before
1598 accepting the RSA key.
1600 This can be circumvented by setting the "HostKeyAlgorithms"
1601 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1604 Please note that the sequence of keys offered for
1605 authentication has been changed as well. You may want to
1606 specify IdentityFile in a different order to revert this
1610 The sio(4) driver has been removed from the i386 and amd64
1611 kernel configuration files. This means uart(4) is now the
1612 default serial port driver on those platforms as well.
1614 To prevent collisions with the sio(4) driver, the uart(4) driver
1615 uses different names for its device nodes. This means the
1616 onboard serial port will now most likely be called "ttyu0"
1617 instead of "ttyd0". You may need to reconfigure applications to
1618 use the new device names.
1620 When using the serial port as a boot console, be sure to update
1621 /boot/device.hints and /etc/ttys before booting the new kernel.
1622 If you forget to do so, you can still manually specify the hints
1623 at the loader prompt:
1625 set hint.uart.0.at="isa"
1626 set hint.uart.0.port="0x3F8"
1627 set hint.uart.0.flags="0x10"
1628 set hint.uart.0.irq="4"
1632 The gpt(8) utility has been removed. Use gpart(8) to partition
1636 The version that Linuxulator emulates was changed from 2.4.2
1637 to 2.6.16. If you experience any problems with Linux binaries
1638 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1639 if it fixes the problem contact emulation mailing list.
1642 ISDN4BSD (I4B) was removed from the src tree. You may need to
1643 update a your kernel configuration and remove relevant entries.
1646 I have checked in code to support multiple routing tables.
1647 See the man pages setfib(1) and setfib(2).
1648 This is a hopefully backwards compatible version,
1649 but to make use of it you need to compile your kernel
1650 with options ROUTETABLES=2 (or more up to 16).
1653 The 802.11 wireless support was redone to enable multi-bss
1654 operation on devices that are capable. The underlying device
1655 is no longer used directly but instead wlanX devices are
1656 cloned with ifconfig. This requires changes to rc.conf files.
1657 For example, change:
1658 ifconfig_ath0="WPA DHCP"
1661 ifconfig_wlan0="WPA DHCP"
1662 see rc.conf(5) for more details. In addition, mergemaster of
1663 /etc/rc.d is highly recommended. Simultaneous update of userland
1664 and kernel wouldn't hurt either.
1666 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1667 modules were merged into the base wlan module. All references
1668 to these modules (e.g. in kernel config files) must be removed.
1671 psm(4) has gained write(2) support in native operation level.
1672 Arbitrary commands can be written to /dev/psm%d and status can
1673 be read back from it. Therefore, an application is responsible
1674 for status validation and error recovery. It is a no-op in
1675 other operation levels.
1678 Support for KSE threading has been removed from the kernel. To
1679 run legacy applications linked against KSE libmap.conf may
1680 be used. The following libmap.conf may be used to ensure
1681 compatibility with any prior release:
1683 libpthread.so.1 libthr.so.1
1684 libpthread.so.2 libthr.so.2
1685 libkse.so.3 libthr.so.3
1688 The layout of struct vmspace has changed. This affects libkvm
1689 and any executables that link against libkvm and use the
1690 kvm_getprocs() function. In particular, but not exclusively,
1691 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1692 The effects are minimal, but it's advisable to upgrade world
1696 The latest em driver no longer has support in it for the
1697 82575 adapter, this is now moved to the igb driver. The
1698 split was done to make new features that are incompatible
1699 with older hardware easier to do.
1702 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1703 likewise the kernel option is now GEOM_LINUX_LVM.
1706 The default NFS mount mode has changed from UDP to TCP for
1707 increased reliability. If you rely on (insecurely) NFS
1708 mounting across a firewall you may need to update your
1712 Belatedly note the addition of m_collapse for compacting
1716 The fts(3) structures have been changed to use adequate
1717 integer types for their members and so to be able to cope
1718 with huge file trees. The old fts(3) ABI is preserved
1719 through symbol versioning in libc, so third-party binaries
1720 using fts(3) should still work, although they will not take
1721 advantage of the extended types. At the same time, some
1722 third-party software might fail to build after this change
1723 due to unportable assumptions made in its source code about
1724 fts(3) structure members. Such software should be fixed
1725 by its vendor or, in the worst case, in the ports tree.
1726 FreeBSD_version 800015 marks this change for the unlikely
1727 case that a portable fix is impossible.
1730 To upgrade to -current after this date, you must be running
1731 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1732 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1735 The ADAPTIVE_GIANT kernel option has been retired because its
1736 functionality is the default now.
1739 The AT keyboard emulation of sunkbd(4) has been turned on
1740 by default. In order to make the special symbols of the Sun
1741 keyboards driven by sunkbd(4) work under X these now have
1742 to be configured the same way as Sun USB keyboards driven
1743 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1745 Option "XkbLayout" "us"
1746 Option "XkbRules" "xorg"
1747 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1750 It has been decided that it is desirable to provide ABI
1751 backwards compatibility to the FreeBSD 4/5/6 versions of the
1752 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1753 broken with the introduction of PCI domain support (see the
1754 20070930 entry). Unfortunately, this required the ABI of
1755 PCIOCGETCONF to be broken again in order to be able to
1756 provide backwards compatibility to the old version of that
1757 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1758 again. As for prominent ports this affects neither pciutils
1759 nor xorg-server this time, the hal port needs to be rebuilt
1763 The misnamed kthread_create() and friends have been renamed
1764 to kproc_create() etc. Many of the callers already
1765 used kproc_start()..
1766 I will return kthread_create() and friends in a while
1767 with implementations that actually create threads, not procs.
1768 Renaming corresponds with version 800002.
1777 Avoid using make -j when upgrading. While generally safe, there are
1778 sometimes problems using -j to upgrade. If your upgrade fails with
1779 -j, please try again without -j. From time to time in the past there
1780 have been problems using -j with buildworld and/or installworld. This
1781 is especially true when upgrading between "distant" versions (eg one
1782 that cross a major release boundary or several minor releases, or when
1783 several months have passed on the -current branch).
1785 Sometimes, obscure build problems are the result of environment
1786 poisoning. This can happen because the make utility reads its
1787 environment when searching for values for global variables. To run
1788 your build attempts in an "environmental clean room", prefix all make
1789 commands with 'env -i '. See the env(1) manual page for more details.
1791 When upgrading from one major version to another it is generally best
1792 to upgrade to the latest code in the currently installed branch first,
1793 then do an upgrade to the new branch. This is the best-tested upgrade
1794 path, and has the highest probability of being successful. Please try
1795 this approach before reporting problems with a major version upgrade.
1797 When upgrading a live system, having a root shell around before
1798 installing anything can help undo problems. Not having a root shell
1799 around can lead to problems if pam has changed too much from your
1800 starting point to allow continued authentication after the upgrade.
1804 When upgrading the boot ZFS pool to a new version, always follow
1807 1.) recompile and reinstall the ZFS boot loader and boot block
1808 (this is part of "make buildworld" and "make installworld")
1810 2.) update the ZFS boot block on your boot drive
1812 The following example updates the ZFS boot block on the first
1813 partition (freebsd-boot) of a GPT partitioned drive ad0:
1814 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1816 Non-boot pools do not need these updates.
1820 If you are updating from a prior version of FreeBSD (even one just
1821 a few days old), you should follow this procedure. It is the most
1822 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1824 make kernel-toolchain
1825 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1826 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1828 To test a kernel once
1829 ---------------------
1830 If you just want to boot a kernel once (because you are not sure
1831 if it works, or if you want to boot a known bad kernel to provide
1832 debugging information) run
1833 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1834 nextboot -k testkernel
1836 To just build a kernel when you know that it won't mess you up
1837 --------------------------------------------------------------
1838 This assumes you are already running a CURRENT system. Replace
1839 ${arch} with the architecture of your machine (e.g. "i386",
1840 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1842 cd src/sys/${arch}/conf
1843 config KERNEL_NAME_HERE
1844 cd ../compile/KERNEL_NAME_HERE
1849 If this fails, go to the "To build a kernel" section.
1851 To rebuild everything and install it on the current system.
1852 -----------------------------------------------------------
1853 # Note: sometimes if you are running current you gotta do more than
1854 # is listed here if you are upgrading from a really old current.
1856 <make sure you have good level 0 dumps>
1858 make kernel KERNCONF=YOUR_KERNEL_HERE
1860 <reboot in single user> [3]
1867 To cross-install current onto a separate partition
1868 --------------------------------------------------
1869 # In this approach we use a separate partition to hold
1870 # current's root, 'usr', and 'var' directories. A partition
1871 # holding "/", "/usr" and "/var" should be about 2GB in
1874 <make sure you have good level 0 dumps>
1877 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1878 <maybe newfs current's root partition>
1879 <mount current's root partition on directory ${CURRENT_ROOT}>
1880 make installworld DESTDIR=${CURRENT_ROOT}
1881 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1882 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1883 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1884 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1885 <reboot into current>
1886 <do a "native" rebuild/install as described in the previous section>
1887 <maybe install compatibility libraries from ports/misc/compat*>
1891 To upgrade in-place from stable to current
1892 ----------------------------------------------
1893 <make sure you have good level 0 dumps>
1895 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1897 <reboot in single user> [3]
1904 Make sure that you've read the UPDATING file to understand the
1905 tweaks to various things you need. At this point in the life
1906 cycle of current, things change often and you are on your own
1907 to cope. The defaults can also change, so please read ALL of
1908 the UPDATING entries.
1910 Also, if you are tracking -current, you must be subscribed to
1911 freebsd-current@freebsd.org. Make sure that before you update
1912 your sources that you have read and understood all the recent
1913 messages there. If in doubt, please track -stable which has
1914 much fewer pitfalls.
1916 [1] If you have third party modules, such as vmware, you
1917 should disable them at this point so they don't crash your
1920 [3] From the bootblocks, boot -s, and then do
1925 adjkerntz -i # if CMOS is wall time
1926 Also, when doing a major release upgrade, it is required that
1927 you boot into single user mode to do the installworld.
1929 [4] Note: This step is non-optional. Failure to do this step
1930 can result in a significant reduction in the functionality of the
1931 system. Attempting to do it by hand is not recommended and those
1932 that pursue this avenue should read this file carefully, as well
1933 as the archives of freebsd-current and freebsd-hackers mailing lists
1934 for potential gotchas. The -U option is also useful to consider.
1935 See mergemaster(8) for more information.
1937 [5] Usually this step is a noop. However, from time to time
1938 you may need to do this if you get unknown user in the following
1939 step. It never hurts to do it all the time. You may need to
1940 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1941 install) after the buildworld before this step if you last updated
1942 from current before 20130425 or from -stable before 20130430.
1944 [6] This only deletes old files and directories. Old libraries
1945 can be deleted by "make delete-old-libs", but you have to make
1946 sure that no program is using those libraries anymore.
1948 [8] In order to have a kernel that can run the 4.x binaries needed to
1949 do an installworld, you must include the COMPAT_FREEBSD4 option in
1950 your kernel. Failure to do so may leave you with a system that is
1951 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1952 required to run the 5.x binaries on more recent kernels. And so on
1953 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1955 Make sure that you merge any new devices from GENERIC since the
1956 last time you updated your kernel config file.
1958 [9] When checking out sources, you must include the -P flag to have
1959 cvs prune empty directories.
1961 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1962 "?=" instead of the "=" assignment operator, so that buildworld can
1963 override the CPUTYPE if it needs to.
1965 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1966 not on the command line, or in /etc/make.conf. buildworld will
1967 warn if it is improperly defined.
1970 This file contains a list, in reverse chronological order, of major
1971 breakages in tracking -current. It is not guaranteed to be a complete
1972 list of such breakages, and only contains entries since October 10, 2007.
1973 If you need to see UPDATING entries from before that date, you will need
1974 to fetch an UPDATING file from an older FreeBSD release.
1976 Copyright information:
1978 Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1980 Redistribution, publication, translation and use, with or without
1981 modification, in full or in part, in any form or format of this
1982 document are permitted without further permission from the author.
1984 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1985 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1986 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1987 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1988 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1989 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1990 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1991 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1992 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1993 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1994 POSSIBILITY OF SUCH DAMAGE.
1996 Contact Warner Losh if you have any questions about your use of