1Updating Information for FreeBSD current users
2
3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4See end of file for further details. For commonly done items, please see the
5COMMON ITEMS: section later in the file. These instructions assume that you
6basically know what you are doing. If not, then please consult the FreeBSD
7handbook.
8
9Items affecting the ports and packages system can be found in
10/usr/ports/UPDATING. Please read that file before running portupgrade.
11
12NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
13 FreeBSD 10.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
24
2520120229:
26 Now unix domain sockets behave "as expected" on nullfs(5). Previously
27 nullfs(5) did not pass through all behaviours to the underlying layer,
28 as a result if we bound to a socket on the lower layer we could connect
29 only to the lower path; if we bound to the upper layer we could connect
30 only to the upper path. The new behavior is one can connect to both the
31 lower and the upper paths regardless what layer path one binds to.
32
3320120211:
34 The getifaddrs upgrade path broken with 20111215 has been restored.
35 If you have upgraded in between 20111215 and 20120209 you need to
36 recompile libc again with your kernel. You still need to recompile
37 world to be able to configure CARP but this restriction already
38 comes from 20111215.
39
4020120114:
41 The set_rcvar() function has been removed from /etc/rc.subr. All
42 base and ports rc.d scripts have been updated, so if you have a
43 port installed with a script in /usr/local/etc/rc.d you can either
44 hand-edit the rcvar= line, or reinstall the port.
45
46 An easy way to handle the mass-update of /etc/rc.d:
47 rm /etc/rc.d/* && mergemaster -i
48
4920120109:
50 panic(9) now stops other CPUs in the SMP systems, disables interrupts
51 on the current CPU and prevents other threads from running.
52 This behavior can be reverted using the kern.stop_scheduler_on_panic
53 tunable/sysctl.
54 The new behavior can be incompatible with kern.sync_on_panic.
55
5620111215:
57 The carp(4) facility has been changed significantly. Configuration
58 of the CARP protocol via ifconfig(8) has changed, as well as format
59 of CARP events submitted to devd(8) has changed. See manual pages
60 for more information. The arpbalance feature of carp(4) is currently
61 not supported anymore.
62
63 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
64 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
65 need to be recompiled.
66
6720111122:
68 The acpi_wmi(4) status device /dev/wmistat has been renamed to
69 /dev/wmistat0.
70
7120111108:
72 The option VFS_ALLOW_NONMPSAFE option has been added in order to
73 explicitely support non-MPSAFE filesystems.
74 It is on by default for all supported platform at this present
75 time.
76
7720111101:
78 The broken amd(4) driver has been replaced with esp(4) in the amd64,
79 i386 and pc98 GENERIC kernel configuration files.
80
8120110930:
82 sysinstall has been removed
83
8420110923:
85 The stable/9 branch created in subversion. This corresponds to the
86 RELENG_9 branch in CVS.
87
8820110913:
89 This commit modifies vfs_register() so that it uses a hash
90 calculation to set vfc_typenum, which is enabled by default.
91 The first time a system is booted after this change, the
92 vfc_typenum values will change for all file systems. The
93 main effect of this is a change to the NFS server file handles
94 for file systems that use vfc_typenum in their fsid, such as ZFS.
95 It will, however, prevent vfc_typenum from changing when file
96 systems are loaded in a different order for subsequent reboots.
97 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
98 until you are ready to remount all NFS clients after a reboot.
99
10020110828:
101 Bump the shared library version numbers for libraries that
102 do not use symbol versioning, have changed the ABI compared
103 to stable/8 and which shared library version was not bumped.
104 Done as part of 9.0-RELEASE cycle.
105
10620110815:
107 During the merge of Capsicum features, the fget(9) KPI was modified.
108 This may require the rebuilding of out-of-tree device drivers --
109 issues have been reported specifically with the nVidia device driver.
110 __FreeBSD_version is bumped to 900041.
111
112 Also, there is a period between 20110811 and 20110814 where the
113 special devices /dev/{stdin,stdout,stderr} did not work correctly.
114 Building world from a kernel during that window may not work.
115
11620110628:
117 The packet filter (pf) code has been updated to OpenBSD 4.5.
118 You need to update userland tools to be in sync with kernel.
119 This update breaks backward compatibility with earlier pfsync(4)
120 versions. Care must be taken when updating redundant firewall setups.
121
12220110608:
123 The following sysctls and tunables are retired on x86 platforms:
124 machdep.hlt_cpus
125 machdep.hlt_logical_cpus
126 The following sysctl is retired:
127 machdep.hyperthreading_allowed
128 The sysctls were supposed to provide a way to dynamically offline and
129 online selected CPUs on x86 platforms, but the implementation has not
130 been reliable especially with SCHED_ULE scheduler.
131 machdep.hyperthreading_allowed tunable is still available to ignore
132 hyperthreading CPUs at OS level.
133 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
134 where X is an APIC ID of a CPU. Be advised, though, that disabling
135 CPUs in non-uniform fashion will result in non-uniform topology and
136 may lead to sub-optimal system performance with SCHED_ULE, which is
137 a default scheduler.
138
13920110607:
140 cpumask_t type is retired and cpuset_t is used in order to describe
141 a mask of CPUs.
142
14320110531:
144 Changes to ifconfig(8) for dynamic address family detection mandate
145 that you are running a kernel of 20110525 or later. Make sure to
146 follow the update procedure to boot a new kernel before installing
147 world.
148
14920110513:
150 Support for sun4v architecture is officially dropped
151
15220110503:
153 Several KPI breaking changes have been committed to the mii(4) layer,
154 the PHY drivers and consequently some Ethernet drivers using mii(4).
155 This means that miibus.ko and the modules of the affected Ethernet
156 drivers need to be recompiled.
157
158 Note to kernel developers: Given that the OUI bit reversion problem
159 was fixed as part of these changes all mii(4) commits related to OUIs,
160 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
161 handling, no longer can be merged verbatim to stable/8 and previous
162 branches.
163
16420110430:
165 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
166 into their kernel configurations along with 'device pci'.
167
16820110427:
169 The default NFS client is now the new NFS client, so fstype "newnfs"
170 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
171 Although mounts via fstype "nfs" will usually work without userland
172 changes, it is recommended that the mount(8) and mount_nfs(8)
173 commands be rebuilt from sources and that a link to mount_nfs called
174 mount_oldnfs be created. The new client is compiled into the
175 kernel with "options NFSCL" and this is needed for diskless root
176 file systems. The GENERIC kernel configs have been changed to use
177 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
178 To use the regular/old client, you can "mount -t oldnfs ...". For
179 a diskless root file system, you must also include a line like:
180
181 vfs.root.mountfrom="oldnfs:"
182
183 in the boot/loader.conf on the root fs on the NFS server to make
184 a diskless root fs use the old client.
185
18620110424:
187 The GENERIC kernels for all architectures now default to the new
188 CAM-based ATA stack. It means that all legacy ATA drivers were
189 removed and replaced by respective CAM drivers. If you are using
190 ATA device names in /etc/fstab or other places, make sure to update
191 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
192 where 'Y's are the sequential numbers starting from zero for each type
193 in order of detection, unless configured otherwise with tunables,
194 see cam(4)). There will be symbolic links created in /dev/ to map
195 old adX devices to the respective adaY. They should provide basic
196 compatibility for file systems mounting in most cases, but they do
197 not support old user-level APIs and do not have respective providers
198 in GEOM. Consider using updated management tools with new device names.
199
200 It is possible to load devices ahci, ata, siis and mvs as modules,
201 but option ATA_CAM should remain in kernel configuration to make ata
202 module work as CAM driver supporting legacy ATA controllers. Device ata
203 still can be used in modular fashion (atacore + ...). Modules atadisk
204 and atapi* are not used and won't affect operation in ATA_CAM mode.
205 Note that to use CAM-based ATA kernel should include CAM devices
206 scbus, pass, da (or explicitly ada), cd and optionally others. All of
207 them are parts of the cam module.
208
209 ataraid(4) functionality is now supported by the RAID GEOM class.
210 To use it you can load geom_raid kernel module and use graid(8) tool
211 for management. Instead of /dev/arX device names, use /dev/raid/rX.
212
213 No kernel config options or code have been removed, so if a problem
214 arises, please report it and optionally revert to the old ATA stack.
215 In order to do it you can remove from the kernel config:
216 options ATA_CAM
217 device ahci
218 device mvs
219 device siis
220 , and instead add back:
221 device atadisk # ATA disk drives
222 device ataraid # ATA RAID drives
223 device atapicd # ATAPI CDROM drives
224 device atapifd # ATAPI floppy drives
225 device atapist # ATAPI tape drives
226
22720110423:
228 The default NFS server has been changed to the new server, which
229 was referred to as the experimental server. If you need to switch
230 back to the old NFS server, you must now put the "-o" option on
231 both the mountd and nfsd commands. This can be done using the
232 mountd_flags and nfs_server_flags rc.conf variables until an
233 update to the rc scripts is committed, which is coming soon.
234
23520110418:
236 The GNU Objective-C runtime library (libobjc), and other Objective-C
237 related components have been removed from the base system. If you
238 require an Objective-C library, please use one of the available ports.
239
24020110331:
241 ath(4) has been split into bus- and device- modules. if_ath contains
242 the HAL, the TX rate control and the network device code. if_ath_pci
243 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
244 contains the AHB glue. Users need to load both if_ath_pci and if_ath
245 in order to use ath on everything else.
246
247 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
248 need to load if_ath and if_ath_pci for ath(4) operation.
249
25020110314:
251 As part of the replacement of sysinstall, the process of building
252 release media has changed significantly. For details, please re-read
253 release(7), which has been updated to reflect the new build process.
254
25520110218:
256 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
257 is the last available version under GPLv2. It brings a number of new
258 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
259 4.1 and SSE 4.2), better support for powerpc64, a number of new
260 directives, and lots of other small improvements. See the ChangeLog
261 file in contrib/binutils for the full details.
262
26320110218:
264 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
265 compliant, and will now use half of hash for authentication.
266 This will break interoperability with all stacks (including all
267 actual FreeBSD versions) who implement
268 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
269 authentication).
270 The only workaround with such peers is to use another HMAC
271 algorithm for IPsec ("phase 2") authentication.
272
27320110207:
274 Remove the uio_yield prototype and symbol. This function has
275 been misnamed since it was introduced and should not be
276 globally exposed with this name. The equivalent functionality
277 is now available using kern_yield(curthread->td_user_pri).
278 The function remains undocumented.
279
28020110112:
281 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
282 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
283 for scalar sysctls is defined but disabled. Code that needs
284 UQUAD to pass the type checking that must compile on older
285 systems where the define is not present can check against
286 __FreeBSD_version >= 900030.
287
288 The system dialog(1) has been replaced with a new version previously
289 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
290 with the previous version, but the libdialog associated with it has
291 a largely incompatible API. As such, the original version of libdialog
292 will be kept temporarily as libodialog, until its base system consumers
293 are replaced or updated. Bump __FreeBSD_version to 900030.
294
29520110103:
296 If you are trying to run make universe on a -stable system, and you get
297 the following warning:
298 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
299 unknown. config(8) likely too old."
300 or something similar to it, then you must upgrade your -stable system
301 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
302 stable/8) or build the config from the latest stable/8 branch and
303 install it on your system.
304
305 Prior to this date, building a current universe on 8-stable system from
306 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
307 error in the first kernel build phase. A new config on those old
308 systems will fix that problem for older versions of -current.
309
31020101228:
311 The TCP stack has been modified to allow Khelp modules to interact with
312 it via helper hook points and store per-connection data in the TCP
313 control block. Bump __FreeBSD_version to 900029. User space tools that
314 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
315 be recompiled.
316
31720101114:
318 Generic IEEE 802.3 annex 31B full duplex flow control support has been
319 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
320 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
321 to take advantage of it instead of using custom implementations. This
322 means that these drivers now no longer unconditionally advertise
323 support for flow control but only do so if flow control is a selected
324 media option. This was implemented in the generic support that way in
325 order to allow flow control to be switched on and off via ifconfig(8)
326 with the PHY specific default to typically off in order to protect
327 from unwanted effects. Consequently, if you used flow control with
328 one of the above mentioned drivers you now need to explicitly enable
329 it, for example via:
330 ifconfig bge0 media auto mediaopt flowcontrol
331
332 Along with the above mentioned changes generic support for setting
333 1000baseT master mode also has been added and brgphy(4), ciphy(4),
334 e1000phy(4) as well as ip1000phy(4) have been converted to take
335 advantage of it. This means that these drivers now no longer take the
336 link0 parameter for selecting master mode but the master media option
337 has to be used instead, for example like in the following:
338 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
339
340 Selection of master mode now is also available with all other PHY
341 drivers supporting 1000baseT.
342
34320101111:
344 The TCP stack has received a significant update to add support for
345 modularised congestion control and generally improve the clarity of
346 congestion control decisions. Bump __FreeBSD_version to 900025. User
347 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
348 sockstat) need to be recompiled.
349
35020101002:
351 The man(1) utility has been replaced by a new version that no longer
352 uses /etc/manpath.config. Please consult man.conf(5) for how to
353 migrate local entries to the new format.
354
35520100928:
356 The copyright strings printed by login(1) and sshd(8) at the time of a
357 new connection have been removed to follow other operating systems and
358 upstream sshd.
359
36020100915:
361 A workaround for a fixed ld bug has been removed in kernel code,
362 so make sure that your system ld is built from sources after
363 revision 210245 from 2010-07-19 (r211583 if building head kernel
364 on stable/8, r211584 for stable/7; both from 2010-08-21).
365 A symptom of incorrect ld version is different addresses for
366 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
367
36820100913:
369 The $ipv6_prefer variable in rc.conf(5) has been split into
370 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
371
372 The $ip6addrctl_policy is a variable to choose a pre-defined
373 address selection policy set by ip6addrctl(8). A value
374 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
375 default is "AUTO".
376
377 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
378 flag (see an entry of 20090926) is set on an interface with no
379 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
380 security reason. If you want IPv6 link-local address on all
381 interfaces by default, set this to "YES".
382
383 The old ipv6_prefer="YES" is equivalent to
384 ipv6_activate_all_interfaces="YES" and
385 ip6addrctl_policy="ipv6_prefer".
386
38720100913:
388 DTrace has grown support for userland tracing. Due to this, DTrace is
389 now i386 and amd64 only.
390 dtruss(1) is now installed by default on those systems and a new
391 kernel module is needed for userland tracing: fasttrap.
392 No changes to your kernel config file are necessary to enable
393 userland tracing, but you might consider adding 'STRIP=' and
394 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
395 to have informative userland stack traces in DTrace (ustack).
396
39720100725:
398 The acpi_aiboost(4) driver has been removed in favor of the new
399 aibs(4) driver. You should update your kernel configuration file.
400
40120100722:
402 BSD grep has been imported to the base system and it is built by
403 default. It is completely BSD licensed, highly GNU-compatible, uses
404 less memory than its GNU counterpart and has a small codebase.
405 However, it is slower than its GNU counterpart, which is mostly
406 noticeable for larger searches, for smaller ones it is measurable
407 but not significant. The reason is complex, the most important factor
408 is that we lack a modern and efficient regex library and GNU
409 overcomes this by optimizing the searches internally. Future work
410 on improving the regex performance is planned, for the meantime,
411 users that need better performance, can build GNU grep instead by
412 setting the WITH_GNU_GREP knob.
413
41420100713:
415 Due to the import of powerpc64 support, all existing powerpc kernel
416 configuration files must be updated with a machine directive like this:
417 machine powerpc powerpc
418
419 In addition, an updated config(8) is required to build powerpc kernels
420 after this change.
421
42220100713:
423 A new version of ZFS (version 15) has been merged to -HEAD.
424 This version uses a python library for the following subcommands:
425 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
426 For full functionality of these commands the following port must
427 be installed: sysutils/py-zfs
428
42920100429:
430 'vm_page's are now hashed by physical address to an array of mutexes.
431 Currently this is only used to serialize access to hold_count. Over
432 time the page queue mutex will be peeled away. This changes the size
433 of pmap on every architecture. And requires all callers of vm_page_hold
434 and vm_page_unhold to be updated.
435
43620100402:
437 WITH_CTF can now be specified in src.conf (not recommended, there
438 are some problems with static executables), make.conf (would also
439 affect ports which do not use GNU make and do not override the
440 compile targets) or in the kernel config (via "makeoptions
441 WITH_CTF=yes").
442 When WITH_CTF was specified there before this was silently ignored,
443 so make sure that WITH_CTF is not used in places which could lead
444 to unwanted behavior.
445
44620100311:
447 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
448 to allow 32-bit compatibility on non-x86 platforms. All kernel
449 configurations on amd64 and ia64 platforms using these options must
450 be modified accordingly.
451
45220100113:
453 The utmp user accounting database has been replaced with utmpx,
454 the user accounting interface standardized by POSIX.
455 Unfortunately the semantics of utmp and utmpx don't match,
456 making it practically impossible to support both interfaces.
457 The user accounting database is used by tools like finger(1),
458 last(1), talk(1), w(1) and ac(8).
459
460 All applications in the base system use utmpx. This means only
461 local binaries (e.g. from the ports tree) may still use these
462 utmp database files. These applications must be rebuilt to make
463 use of utmpx.
464
465 After the system has been upgraded, it is safe to remove the old
466 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
467 assuming their contents is of no importance anymore. Old wtmp
468 databases can only be used by last(1) and ac(8) after they have
469 been converted to the new format using wtmpcvt(1).
470
47120100108:
472 Introduce the kernel thread "deadlock resolver" (which can be enabled
473 via the DEADLKRES option, see NOTES for more details) and the
474 sleepq_type() function for sleepqueues.
475
47620091202:
477 The rc.firewall and rc.firewall6 were unified, and
478 rc.firewall6 and rc.d/ip6fw were removed.
479 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
480 variables are obsoleted. Instead, the following new rc
481 variables are added to rc.d/ipfw:
482
483 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
484 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
485 firewall_simple_onet_ipv6, firewall_trusted_ipv6
486
487 The meanings correspond to the relevant IPv4 variables.
488
48920091125:
490 8.0-RELEASE.
491
49220091113:
493 The default terminal emulation for syscons(4) has been changed
494 from cons25 to xterm on all platforms except pc98. This means
495 that the /etc/ttys file needs to be updated to ensure correct
496 operation of applications on the console.
497
498 The terminal emulation style can be toggled per window by using
499 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
500 options can be used to change the compile-time default back to
501 cons25.
502
503 To prevent graphical artifacts, make sure the TERM environment
504 variable is set to match the terminal emulation that is being
505 performed by syscons(4).
506
50720091109:
508 The layout of the structure ieee80211req_scan_result has changed.
509 Applications that require wireless scan results (e.g. ifconfig(8))
510 from net80211 need to be recompiled.
511
512 Applications such as wpa_supplicant(8) may require a full world
513 build without using NO_CLEAN in order to get synchronized with the
514 new structure.
515
51620091025:
517 The iwn(4) driver has been updated to support the 5000 and 5150 series.
518 There's one kernel module for each firmware. Adding "device iwnfw"
519 to the kernel configuration file means including all three firmware
520 images inside the kernel. If you want to include just the one for
521 your wireless card, use the devices iwn4965fw, iwn5000fw or
522 iwn5150fw.
523
52420090926:
525 The rc.d/network_ipv6, IPv6 configuration script has been integrated
526 into rc.d/netif. The changes are the following:
527
528 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
529 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
530 Note that both variables need the "inet6" keyword at the head.
531
532 Do not set $ipv6_network_interfaces manually if you do not
533 understand what you are doing. It is not needed in most cases.
534
535 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
536 they are obsolete.
537
538 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
539 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
540
541 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
542 all configured interfaces have "inet6 accept_rtadv" in the
543 $ifconfig_IF_ipv6. These are for backward compatibility.
544
545 3. A new variable $ipv6_prefer has been added. If NO, IPv6
546 functionality of interfaces with no corresponding
547 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
548 and the default address selection policy of ip6addrctl(8)
549 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
550 Note that if you want to configure IPv6 functionality on the
551 disabled interfaces after boot, first you need to clear the flag by
552 using ifconfig(8) like:
553
554 ifconfig em0 inet6 -ifdisabled
555
556 If YES, the default address selection policy is set as
557 IPv6-preferred.
558
559 The default value of $ipv6_prefer is NO.
560
561 4. If your system need to receive Router Advertisement messages,
562 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
563 scripts automatically invoke rtsol(8) when the interface becomes
564 UP. The Router Advertisement messages are used for SLAAC
565 (State-Less Address AutoConfiguration).
566
56720090922:
568 802.11s D3.03 support was committed. This is incompatible with the
569 previous code, which was based on D3.0.
570
57120090912:
572 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
573 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
574 control whether accepting Router Advertisement messages or not.
575 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
576 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
577 The ifconfig(8) utility now supports these flags.
578
57920090910:
580 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
581 mount(8) and -a option for df(1) to see them.
582
58320090825:
584 The old tunable hw.bus.devctl_disable has been superseded by
585 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
586 replaced by hw.bus.devctl_queue=0. The default for this new tunable
587 is 1000.
588
58920090813:
590 Remove the option STOP_NMI. The default action is now to use NMI only
591 for KDB via the newly introduced function stop_cpus_hard() and
592 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
593
59420090803:
595 The stable/8 branch created in subversion. This corresponds to the
596 RELENG_8 branch in CVS.
597
59820090719:
599 Bump the shared library version numbers for all libraries that do not
600 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
601 __FreeBSD_version to 800105.
602
60320090714:
604 Due to changes in the implementation of virtual network stack support,
605 all network-related kernel modules must be recompiled. As this change
606 breaks the ABI, bump __FreeBSD_version to 800104.
607
60820090713:
609 The TOE interface to the TCP syncache has been modified to remove
610 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
611 The cxgb driver is the only TOE consumer affected by this change, and
612 needs to be recompiled along with the kernel. As this change breaks
613 the ABI, bump __FreeBSD_version to 800103.
614
61520090712:
616 Padding has been added to struct tcpcb, sackhint and tcpstat in
617 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
618 maintaining the ABI. However, this change breaks the ABI, so bump
619 __FreeBSD_version to 800102. User space tools that rely on the size of
620 any of these structs (e.g. sockstat) need to be recompiled.
621
62220090630:
623 The NFS_LEGACYRPC option has been removed along with the old kernel
624 RPC implementation that this option selected. Kernel configurations
625 may need to be adjusted.
626
62720090629:
628 The network interface device nodes at /dev/net/<interface> have been
629 removed. All ioctl operations can be performed the normal way using
630 routing sockets. The kqueue functionality can generally be replaced
631 with routing sockets.
632
63320090628:
634 The documentation from the FreeBSD Documentation Project (Handbook,
635 FAQ, etc.) is now installed via packages by sysinstall(8) and under
636 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
637
63820090624:
639 The ABI of various structures related to the SYSV IPC API have been
640 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
641 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
642 800100.
643
64420090622:
645 Layout of struct vnet has changed as routing related variables were
646 moved to their own Vimage module. Modules need to be recompiled. Bump
647 __FreeBSD_version to 800099.
648
64920090619:
650 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
651 respectively. As long as no more than 16 groups per process are used,
652 no changes should be visible. When more than 16 groups are used, old
653 binaries may fail if they call getgroups() or getgrouplist() with
654 statically sized storage. Recompiling will work around this, but
655 applications should be modified to use dynamically allocated storage
656 for group arrays as POSIX.1-2008 does not cap an implementation's
657 number of supported groups at NGROUPS_MAX+1 as previous versions did.
658
659 NFS and portalfs mounts may also be affected as the list of groups is
660 truncated to 16. Users of NFS who use more than 16 groups, should
661 take care that negative group permissions are not used on the exported
662 file systems as they will not be reliable unless a GSSAPI based
663 authentication method is used.
664
66520090616:
666 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
667 option compiles in the support for adaptive spinning for lockmgrs
668 which want to enable it. The lockinit() function now accepts the flag
669 LK_ADAPTIVE in order to make the lock object subject to adaptive
670 spinning when both held in write and read mode.
671
67220090613:
673 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
674 changed. User applications that use this ioctl need to be rebuilt.
675
67620090611:
677 The layout of struct thread has changed. Kernel and modules need to
678 be rebuilt.
679
68020090608:
681 The layout of structs ifnet, domain, protosw and vnet_net has changed.
682 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
683
68420090602:
685 window(1) has been removed from the base system. It can now be
686 installed from ports. The port is called misc/window.
687
68820090601:
689 The way we are storing and accessing `routing table' entries has
690 changed. Programs reading the FIB, like netstat, need to be
691 re-compiled.
692
69320090601:
694 A new netisr implementation has been added for FreeBSD 8. Network
695 file system modules, such as igmp, ipdivert, and others, should be
696 rebuilt.
697 Bump __FreeBSD_version to 800096.
698
69920090530:
700 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
701 more valid.
702
70320090530:
704 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
705 Bump __FreeBSD_version to 800094.
706
70720090529:
708 Add mnt_xflag field to 'struct mount'. File system modules need to be
709 rebuilt.
710 Bump __FreeBSD_version to 800093.
711
71220090528:
713 The compiling option ADAPTIVE_SX has been retired while it has been
714 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
715 The KPI for sx_init_flags() changes as accepting flags:
716 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
717 been introduced in order to handle the reversed logic.
718 Bump __FreeBSD_version to 800092.
719
72020090527:
721 Add support for hierarchical jails. Remove global securelevel.
722 Bump __FreeBSD_version to 800091.
723
72420090523:
725 The layout of struct vnet_net has changed, therefore modules
726 need to be rebuilt.
727 Bump __FreeBSD_version to 800090.
728
72920090523:
730 The newly imported zic(8) produces a new format in the output. Please
731 run tzsetup(8) to install the newly created data to /etc/localtime.
732
73320090520:
734 The sysctl tree for the usb stack has renamed from hw.usb2.* to
735 hw.usb.* and is now consistent again with previous releases.
736
73720090520:
738 802.11 monitor mode support was revised and driver api's were changed.
739 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
740 of DLT_IEEE802_11. No user-visible data structures were changed but
741 applications that use DLT_IEEE802_11 may require changes.
742 Bump __FreeBSD_version to 800088.
743
74420090430:
745 The layout of the following structs has changed: sysctl_oid,
746 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
747 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
748 panics may be experienced. World rebuild is required for
749 correctly checking networking state from userland.
750 Bump __FreeBSD_version to 800085.
751
75220090429:
753 MLDv2 and Source-Specific Multicast (SSM) have been merged
754 to the IPv6 stack. VIMAGE hooks are in but not yet used.
755 The implementation of SSM within FreeBSD's IPv6 stack closely
756 follows the IPv4 implementation.
757
758 For kernel developers:
759
760 * The most important changes are that the ip6_output() and
761 ip6_input() paths no longer take the IN6_MULTI_LOCK,
762 and this lock has been downgraded to a non-recursive mutex.
763
764 * As with the changes to the IPv4 stack to support SSM, filtering
765 of inbound multicast traffic must now be performed by transport
766 protocols within the IPv6 stack. This does not apply to TCP and
767 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
768
769 * The KPIs used by IPv6 multicast are similar to those used by
770 the IPv4 stack, with the following differences:
771 * im6o_mc_filter() is analogous to imo_multicast_filter().
772 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
773 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
774 * IN6_LOOKUP_MULTI() has been deprecated and removed.
775 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
776 for MLDv1 have an additional 'timer' argument which is used to
777 jitter the initial membership report for the solicited-node
778 multicast membership on-link.
779 * This is not strictly needed for MLDv2, which already jitters
780 its report transmissions. However, the 'timer' argument is
781 preserved in case MLDv1 is active on the interface.
782
783 * The KAME linked-list based IPv6 membership implementation has
784 been refactored to use a vector similar to that used by the IPv4
785 stack.
786 Code which maintains a list of its own multicast memberships
787 internally, e.g. carp, has been updated to reflect the new
788 semantics.
789
790 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
791 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
792 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
793 implementation constraint which needs to be addressed in HEAD.
794
795 For application developers:
796
797 * The changes are broadly similar to those made for the IPv4
798 stack.
799
800 * The use of IPv4 and IPv6 multicast socket options on the same
801 socket, using mapped addresses, HAS NOT been tested or supported.
802
803 * There are a number of issues with the implementation of various
804 IPv6 multicast APIs which need to be resolved in the API surface
805 before the implementation is fully compatible with KAME userland
806 use, and these are mostly to do with interface index treatment.
807
808 * The literature available discusses the use of either the delta / ASM
809 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
810 using setsourcefilter(3)/getsourcefilter(3). For more information
811 please refer to RFC 3768, 'Socket Interface Extensions for
812 Multicast Source Filters'.
813
814 * Applications which use the published RFC 3678 APIs should be fine.
815
816 For systems administrators:
817
818 * The mtest(8) utility has been refactored to support IPv6, in
819 addition to IPv4. Interface addresses are no longer accepted
820 as arguments, their names must be used instead. The utility
821 will map the interface name to its first IPv4 address as
822 returned by getifaddrs(3).
823
824 * The ifmcstat(8) utility has also been updated to print the MLDv2
825 endpoint state and source filter lists via sysctl(3).
826
827 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
828 loopback of IPv6 multicast datagrams by default; it defaults to 1
829 to preserve the existing behaviour. Disabling multicast loopback is
830 recommended for optimal system performance.
831
832 * The IPv6 MROUTING code has been changed to examine this sysctl
833 instead of attempting to perform a group lookup before looping
834 back forwarded datagrams.
835
836 Bump __FreeBSD_version to 800084.
837
83820090422:
839 Implement low-level Bluetooth HCI API.
840 Bump __FreeBSD_version to 800083.
841
84220090419:
843 The layout of struct malloc_type, used by modules to register new
844 memory allocation types, has changed. Most modules will need to
845 be rebuilt or panics may be experienced.
846 Bump __FreeBSD_version to 800081.
847
84820090415:
849 Anticipate overflowing inp_flags - add inp_flags2.
850 This changes most offsets in inpcb, so checking v4 connection
851 state will require a world rebuild.
852 Bump __FreeBSD_version to 800080.
853
85420090415:
855 Add an llentry to struct route and struct route_in6. Modules
856 embedding a struct route will need to be recompiled.
857 Bump __FreeBSD_version to 800079.
858
85920090414:
860 The size of rt_metrics_lite and by extension rtentry has changed.
861 Networking administration apps will need to be recompiled.
862 The route command now supports show as an alias for get, weighting
863 of routes, sticky and nostick flags to alter the behavior of stateful
864 load balancing.
865 Bump __FreeBSD_version to 800078.
866
86720090408:
868 Do not use Giant for kbdmux(4) locking. This is wrong and
869 apparently causing more problems than it solves. This will
870 re-open the issue where interrupt handlers may race with
871 kbdmux(4) in polling mode. Typical symptoms include (but
872 not limited to) duplicated and/or missing characters when
873 low level console functions (such as gets) are used while
874 interrupts are enabled (for example geli password prompt,
875 mountroot prompt etc.). Disabling kbdmux(4) may help.
876
87720090407:
878 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
879 kernel modules referencing any of the above need to be recompiled.
880 Bump __FreeBSD_version to 800075.
881
88220090320:
883 GEOM_PART has become the default partition slicer for storage devices,
884 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
885 introduces some changes:
886
887 MSDOS/EBR: the devices created from MSDOS extended partition entries
888 (EBR) can be named differently than with GEOM_MBR and are now symlinks
889 to devices with offset-based names. fstabs may need to be modified.
890
891 BSD: the "geometry does not match label" warning is harmless in most
892 cases but it points to problems in file system misalignment with
893 disk geometry. The "c" partition is now implicit, covers the whole
894 top-level drive and cannot be (mis)used by users.
895
896 General: Kernel dumps are now not allowed to be written to devices
897 whose partition types indicate they are meant to be used for file
898 systems (or, in case of MSDOS partitions, as something else than
899 the "386BSD" type).
900
901 Most of these changes date approximately from 200812.
902
90320090319:
904 The uscanner(4) driver has been removed from the kernel. This follows
905 Linux removing theirs in 2.6 and making libusb the default interface
906 (supported by sane).
907
90820090319:
909 The multicast forwarding code has been cleaned up. netstat(1)
910 only relies on KVM now for printing bandwidth upcall meters.
911 The IPv4 and IPv6 modules are split into ip_mroute_mod and
912 ip6_mroute_mod respectively. The config(5) options for statically
913 compiling this code remain the same, i.e. 'options MROUTING'.
914
91520090315:
916 Support for the IFF_NEEDSGIANT network interface flag has been
917 removed, which means that non-MPSAFE network device drivers are no
918 longer supported. In particular, if_ar, if_sr, and network device
919 drivers from the old (legacy) USB stack can no longer be built or
920 used.
921
92220090313:
923 POSIX.1 Native Language Support (NLS) has been enabled in libc and
924 a bunch of new language catalog files have also been added.
925 This means that some common libc messages are now localized and
926 they depend on the LC_MESSAGES environmental variable.
927
92820090313:
929 The k8temp(4) driver has been renamed to amdtemp(4) since
930 support for Family 10 and Family 11 CPU families was added.
931
93220090309:
933 IGMPv3 and Source-Specific Multicast (SSM) have been merged
934 to the IPv4 stack. VIMAGE hooks are in but not yet used.
935
936 For kernel developers, the most important changes are that the
937 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
938 and this lock has been downgraded to a non-recursive mutex.
939
940 Transport protocols (UDP, Raw IP) are now responsible for filtering
941 inbound multicast traffic according to group membership and source
942 filters. The imo_multicast_filter() KPI exists for this purpose.
943 Transports which do not use multicast (SCTP, TCP) already reject
944 multicast by default. Forwarding and receive performance may improve
945 as a mutex acquisition is no longer needed in the ip_input()
946 low-level input path. in_addmulti() and in_delmulti() are shimmed
947 to new KPIs which exist to support SSM in-kernel.
948
949 For application developers, it is recommended that loopback of
950 multicast datagrams be disabled for best performance, as this
951 will still cause the lock to be taken for each looped-back
952 datagram transmission. The net.inet.ip.mcast.loop sysctl may
953 be tuned to 0 to disable loopback by default; it defaults to 1
954 to preserve the existing behaviour.
955
956 For systems administrators, to obtain best performance with
957 multicast reception and multiple groups, it is always recommended
958 that a card with a suitably precise hash filter is used. Hash
959 collisions will still result in the lock being taken within the
960 transport protocol input path to check group membership.
961
962 If deploying FreeBSD in an environment with IGMP snooping switches,
963 it is recommended that the net.inet.igmp.sendlocal sysctl remain
964 enabled; this forces 224.0.0.0/24 group membership to be announced
965 via IGMP.
966
967 The size of 'struct igmpstat' has changed; netstat needs to be
968 recompiled to reflect this.
969 Bump __FreeBSD_version to 800070.
970
97120090309:
972 libusb20.so.1 is now installed as libusb.so.1 and the ports system
973 updated to use it. This requires a buildworld/installworld in order to
974 update the library and dependencies (usbconfig, etc). Its advisable to
975 rebuild all ports which uses libusb. More specific directions are given
976 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
977 libusb are no longer required and can be removed.
978
97920090302:
980 A workaround is committed to allow the creation of System V shared
981 memory segment of size > 2 GB on the 64-bit architectures.
982 Due to a limitation of the existing ABI, the shm_segsz member
983 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
984 wrong for large segments. Note that limits must be explicitly
985 raised to allow such segments to be created.
986
98720090301:
988 The layout of struct ifnet has changed, requiring a rebuild of all
989 network device driver modules.
990
99120090227:
992 The /dev handling for the new USB stack has changed, a
993 buildworld/installworld is required for libusb20.
994
99520090223:
996 The new USB2 stack has now been permanently moved in and all kernel and
997 module names reverted to their previous values (eg, usb, ehci, ohci,
998 ums, ...). The old usb stack can be compiled in by prefixing the name
999 with the letter 'o', the old usb modules have been removed.
1000 Updating entry 20090216 for xorg and 20090215 for libmap may still
1001 apply.
1002
100320090217:
1004 The rc.conf(5) option if_up_delay has been renamed to
1005 defaultroute_delay to better reflect its purpose. If you have
1006 customized this setting in /etc/rc.conf you need to update it to
1007 use the new name.
1008
100920090216:
1010 xorg 7.4 wants to configure its input devices via hald which does not
1011 yet work with USB2. If the keyboard/mouse does not work in xorg then
1012 add
1013 Option "AllowEmptyInput" "off"
1014 to your ServerLayout section. This will cause X to use the configured
1015 kbd and mouse sections from your xorg.conf.
1016
101720090215:
1018 The GENERIC kernels for all architectures now default to the new USB2
1019 stack. No kernel config options or code have been removed so if a
1020 problem arises please report it and optionally revert to the old USB
1021 stack. If you are loading USB kernel modules or have a custom kernel
1022 that includes GENERIC then ensure that usb names are also changed over,
1023 eg uftdi -> usb2_serial_ftdi.
1024
1025 Older programs linked against the ports libusb 0.1 need to be
1026 redirected to the new stack's libusb20. /etc/libmap.conf can
1027 be used for this:
1028 # Map old usb library to new one for usb2 stack
1029 libusb-0.1.so.8 libusb20.so.1
1030
103120090209:
1032 All USB ethernet devices now attach as interfaces under the name ueN
1033 (eg. ue0). This is to provide a predictable name as vendors often
1034 change usb chipsets in a product without notice.
1035
103620090203:
1037 The ichsmb(4) driver has been changed to require SMBus slave
1038 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1039 All of the other SMBus controller drivers require left-justified
1040 slave addresses, so this change makes all the drivers provide the
1041 same interface.
1042
104320090201:
1044 INET6 statistics (struct ip6stat) was updated.
1045 netstat(1) needs to be recompiled.
1046
104720090119:
1048 NTFS has been removed from GENERIC kernel on amd64 to match
1049 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1050 will load ntfs.ko module automatically when NTFS support is
1051 actually needed, unless ntfs.ko is not installed or security
1052 level prohibits loading kernel modules. If either is the case,
1053 "options NTFS" has to be added into kernel config.
1054
105520090115:
1056 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1057 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1058 800061. User space tools that rely on the size of struct tcpcb in
1059 tcp_var.h (e.g. sockstat) need to be recompiled.
1060
106120081225:
1062 ng_tty(4) module updated to match the new TTY subsystem.
1063 Due to API change, user-level applications must be updated.
1064 New API support added to mpd5 CVS and expected to be present
1065 in next mpd5.3 release.
1066
106720081219:
1068 With __FreeBSD_version 800060 the makefs tool is part of
1069 the base system (it was a port).
1070
107120081216:
1072 The afdata and ifnet locks have been changed from mutexes to
1073 rwlocks, network modules will need to be re-compiled.
1074
107520081214:
1076 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1077 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1078 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1079 architecture and 40 bytes on 64-bit architecture. The userland
1080 applications "arp" and "ndp" have been updated accordingly.
1081 The output from "netstat -r" shows only routing entries and
1082 none of the L2 information.
1083
108420081130:
1085 __FreeBSD_version 800057 marks the switchover from the
1086 binary ath hal to source code. Users must add the line:
1087
1088 options AH_SUPPORT_AR5416
1089
1090 to their kernel config files when specifying:
1091
1092 device ath_hal
1093
1094 The ath_hal module no longer exists; the code is now compiled
1095 together with the driver in the ath module. It is now
1096 possible to tailor chip support (i.e. reduce the set of chips
1097 and thereby the code size); consult ath_hal(4) for details.
1098
109920081121:
1100 __FreeBSD_version 800054 adds memory barriers to
1101 <machine/atomic.h>, new interfaces to ifnet to facilitate
1102 multiple hardware transmit queues for cards that support
1103 them, and a lock-less ring-buffer implementation to
1104 enable drivers to more efficiently manage queueing of
1105 packets.
1106
110720081117:
1108 A new version of ZFS (version 13) has been merged to -HEAD.
1109 This version has zpool attribute "listsnapshots" off by
1110 default, which means "zfs list" does not show snapshots,
1111 and is the same as Solaris behavior.
1112
111320081028:
1114 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1115
111620081009:
1117 The uhci, ohci, ehci and slhci USB Host controller drivers have
1118 been put into separate modules. If you load the usb module
1119 separately through loader.conf you will need to load the
1120 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1121 controller add the following to loader.conf:
1122
1123 uhci_load="YES"
1124 ehci_load="YES"
1125
112620081009:
1127 The ABI used by the PMC toolset has changed. Please keep
1128 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1129 sync.
1130
113120081009:
1132 atapci kernel module now includes only generic PCI ATA
1133 driver. AHCI driver moved to ataahci kernel module.
1134 All vendor-specific code moved into separate kernel modules:
1135 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1136 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1137 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1138 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1139
114020080820:
1141 The TTY subsystem of the kernel has been replaced by a new
1142 implementation, which provides better scalability and an
1143 improved driver model. Most common drivers have been migrated to
1144 the new TTY subsystem, while others have not. The following
1145 drivers have not yet been ported to the new TTY layer:
1146
1147 PCI/ISA:
1148 cy, digi, rc, rp, sio
1149
1150 USB:
1151 ubser, ucycom
1152
1153 Line disciplines:
1154 ng_h4, ng_tty, ppp, sl, snp
1155
1156 Adding these drivers to your kernel configuration file shall
1157 cause compilation to fail.
1158
115920080818:
1160 ntpd has been upgraded to 4.2.4p5.
1161
116220080801:
1163 OpenSSH has been upgraded to 5.1p1.
1164
1165 For many years, FreeBSD's version of OpenSSH preferred DSA
1166 over RSA for host and user authentication keys. With this
1167 upgrade, we've switched to the vendor's default of RSA over
1168 DSA. This may cause upgraded clients to warn about unknown
1169 host keys even for previously known hosts. Users should
1170 follow the usual procedure for verifying host keys before
1171 accepting the RSA key.
1172
1173 This can be circumvented by setting the "HostKeyAlgorithms"
1174 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1175 command line.
1176
1177 Please note that the sequence of keys offered for
1178 authentication has been changed as well. You may want to
1179 specify IdentityFile in a different order to revert this
1180 behavior.
1181
118220080713:
1183 The sio(4) driver has been removed from the i386 and amd64
1184 kernel configuration files. This means uart(4) is now the
1185 default serial port driver on those platforms as well.
1186
1187 To prevent collisions with the sio(4) driver, the uart(4) driver
1188 uses different names for its device nodes. This means the
1189 onboard serial port will now most likely be called "ttyu0"
1190 instead of "ttyd0". You may need to reconfigure applications to
1191 use the new device names.
1192
1193 When using the serial port as a boot console, be sure to update
1194 /boot/device.hints and /etc/ttys before booting the new kernel.
1195 If you forget to do so, you can still manually specify the hints
1196 at the loader prompt:
1197
1198 set hint.uart.0.at="isa"
1199 set hint.uart.0.port="0x3F8"
1200 set hint.uart.0.flags="0x10"
1201 set hint.uart.0.irq="4"
1202 boot -s
1203
120420080609:
1205 The gpt(8) utility has been removed. Use gpart(8) to partition
1206 disks instead.
1207
120820080603:
1209 The version that Linuxulator emulates was changed from 2.4.2
1210 to 2.6.16. If you experience any problems with Linux binaries
1211 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1212 if it fixes the problem contact emulation mailing list.
1213
121420080525:
1215 ISDN4BSD (I4B) was removed from the src tree. You may need to
1216 update a your kernel configuration and remove relevant entries.
1217
121820080509:
1219 I have checked in code to support multiple routing tables.
1220 See the man pages setfib(1) and setfib(2).
1221 This is a hopefully backwards compatible version,
1222 but to make use of it you need to compile your kernel
1223 with options ROUTETABLES=2 (or more up to 16).
1224
122520080420:
1226 The 802.11 wireless support was redone to enable multi-bss
1227 operation on devices that are capable. The underlying device
1228 is no longer used directly but instead wlanX devices are
1229 cloned with ifconfig. This requires changes to rc.conf files.
1230 For example, change:
1231 ifconfig_ath0="WPA DHCP"
1232 to
1233 wlans_ath0=wlan0
1234 ifconfig_wlan0="WPA DHCP"
1235 see rc.conf(5) for more details. In addition, mergemaster of
1236 /etc/rc.d is highly recommended. Simultaneous update of userland
1237 and kernel wouldn't hurt either.
1238
1239 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1240 modules were merged into the base wlan module. All references
1241 to these modules (e.g. in kernel config files) must be removed.
1242
124320080408:
1244 psm(4) has gained write(2) support in native operation level.
1245 Arbitrary commands can be written to /dev/psm%d and status can
1246 be read back from it. Therefore, an application is responsible
1247 for status validation and error recovery. It is a no-op in
1248 other operation levels.
1249
125020080312:
1251 Support for KSE threading has been removed from the kernel. To
1252 run legacy applications linked against KSE libmap.conf may
1253 be used. The following libmap.conf may be used to ensure
1254 compatibility with any prior release:
1255
1256 libpthread.so.1 libthr.so.1
1257 libpthread.so.2 libthr.so.2
1258 libkse.so.3 libthr.so.3
1259
126020080301:
1261 The layout of struct vmspace has changed. This affects libkvm
1262 and any executables that link against libkvm and use the
1263 kvm_getprocs() function. In particular, but not exclusively,
1264 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1265 The effects are minimal, but it's advisable to upgrade world
1266 nonetheless.
1267
126820080229:
1269 The latest em driver no longer has support in it for the
1270 82575 adapter, this is now moved to the igb driver. The
1271 split was done to make new features that are incompatible
1272 with older hardware easier to do.
1273
127420080220:
1275 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1276 likewise the kernel option is now GEOM_LINUX_LVM.
1277
127820080211:
1279 The default NFS mount mode has changed from UDP to TCP for
1280 increased reliability. If you rely on (insecurely) NFS
1281 mounting across a firewall you may need to update your
1282 firewall rules.
1283
128420080208:
1285 Belatedly note the addition of m_collapse for compacting
1286 mbuf chains.
1287
128820080126:
1289 The fts(3) structures have been changed to use adequate
1290 integer types for their members and so to be able to cope
1291 with huge file trees. The old fts(3) ABI is preserved
1292 through symbol versioning in libc, so third-party binaries
1293 using fts(3) should still work, although they will not take
1294 advantage of the extended types. At the same time, some
1295 third-party software might fail to build after this change
1296 due to unportable assumptions made in its source code about
1297 fts(3) structure members. Such software should be fixed
1298 by its vendor or, in the worst case, in the ports tree.
1299 FreeBSD_version 800015 marks this change for the unlikely
1300 case that a portable fix is impossible.
1301
130220080123:
1303 To upgrade to -current after this date, you must be running
1304 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1305 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1306
130720071128:
1308 The ADAPTIVE_GIANT kernel option has been retired because its
1309 functionality is the default now.
1310
131120071118:
1312 The AT keyboard emulation of sunkbd(4) has been turned on
1313 by default. In order to make the special symbols of the Sun
1314 keyboards driven by sunkbd(4) work under X these now have
1315 to be configured the same way as Sun USB keyboards driven
1316 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1317
1318 Option "XkbLayout" "us"
1319 Option "XkbRules" "xorg"
1320 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1321
132220071024:
1323 It has been decided that it is desirable to provide ABI
1324 backwards compatibility to the FreeBSD 4/5/6 versions of the
1325 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1326 broken with the introduction of PCI domain support (see the
1327 20070930 entry). Unfortunately, this required the ABI of
1328 PCIOCGETCONF to be broken again in order to be able to
1329 provide backwards compatibility to the old version of that
1330 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1331 again. As for prominent ports this affects neither pciutils
1332 nor xorg-server this time, the hal port needs to be rebuilt
1333 however.
1334
133520071020:
1336 The misnamed kthread_create() and friends have been renamed
1337 to kproc_create() etc. Many of the callers already
1338 used kproc_start()..
1339 I will return kthread_create() and friends in a while
1340 with implementations that actually create threads, not procs.
1341 Renaming corresponds with version 800002.
1342
134320071010:
1344 RELENG_7 branched.
1345
1346COMMON ITEMS:
1347
1348 General Notes
1349 -------------
1350 Avoid using make -j when upgrading. While generally safe, there are
1351 sometimes problems using -j to upgrade. If your upgrade fails with
1352 -j, please try again without -j. From time to time in the past there
1353 have been problems using -j with buildworld and/or installworld. This
1354 is especially true when upgrading between "distant" versions (eg one
1355 that cross a major release boundary or several minor releases, or when
1356 several months have passed on the -current branch).
1357
1358 Sometimes, obscure build problems are the result of environment
1359 poisoning. This can happen because the make utility reads its
1360 environment when searching for values for global variables. To run
1361 your build attempts in an "environmental clean room", prefix all make
1362 commands with 'env -i '. See the env(1) manual page for more details.
1363
1364 When upgrading from one major version to another it is generally best
1365 to upgrade to the latest code in the currently installed branch first,
1366 then do an upgrade to the new branch. This is the best-tested upgrade
1367 path, and has the highest probability of being successful. Please try
1368 this approach before reporting problems with a major version upgrade.
1369
1370 ZFS notes
1371 ---------
1372 When upgrading the boot ZFS pool to a new version, always follow
1373 these two steps:
1374
1375 1.) recompile and reinstall the ZFS boot loader and boot block
1376 (this is part of "make buildworld" and "make installworld")
1377
1378 2.) update the ZFS boot block on your boot drive
1379
1380 The following example updates the ZFS boot block on the first
1381 partition (freebsd-boot) of a GPT partitioned drive ad0:
1382 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1383
1384 Non-boot pools do not need these updates.
1385
1386 To build a kernel
1387 -----------------
1388 If you are updating from a prior version of FreeBSD (even one just
1389 a few days old), you should follow this procedure. It is the most
1390 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1391
1392 make kernel-toolchain
1393 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1394 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1395
1396 To test a kernel once
1397 ---------------------
1398 If you just want to boot a kernel once (because you are not sure
1399 if it works, or if you want to boot a known bad kernel to provide
1400 debugging information) run
1401 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1402 nextboot -k testkernel
1403
1404 To just build a kernel when you know that it won't mess you up
1405 --------------------------------------------------------------
1406 This assumes you are already running a CURRENT system. Replace
1407 ${arch} with the architecture of your machine (e.g. "i386",
1408 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1409
1410 cd src/sys/${arch}/conf
1411 config KERNEL_NAME_HERE
1412 cd ../compile/KERNEL_NAME_HERE
1413 make depend
1414 make
1415 make install
1416
1417 If this fails, go to the "To build a kernel" section.
1418
1419 To rebuild everything and install it on the current system.
1420 -----------------------------------------------------------
1421 # Note: sometimes if you are running current you gotta do more than
1422 # is listed here if you are upgrading from a really old current.
1423
1424 <make sure you have good level 0 dumps>
1425 make buildworld
1426 make kernel KERNCONF=YOUR_KERNEL_HERE
1427 [1]
1428 <reboot in single user> [3]
1429 mergemaster -p [5]
1430 make installworld
1431 mergemaster -i [4]
1432 make delete-old [6]
1433 <reboot>
1434
1435
1436 To cross-install current onto a separate partition
1437 --------------------------------------------------
1438 # In this approach we use a separate partition to hold
1439 # current's root, 'usr', and 'var' directories. A partition
1440 # holding "/", "/usr" and "/var" should be about 2GB in
1441 # size.
1442
1443 <make sure you have good level 0 dumps>
1444 <boot into -stable>
1445 make buildworld
1446 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1447 <maybe newfs current's root partition>
1448 <mount current's root partition on directory ${CURRENT_ROOT}>
1449 make installworld DESTDIR=${CURRENT_ROOT}
1450 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1451 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1452 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1453 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1454 <reboot into current>
1455 <do a "native" rebuild/install as described in the previous section>
1456 <maybe install compatibility libraries from ports/misc/compat*>
1457 <reboot>
1458
1459
1460 To upgrade in-place from 8.x-stable to current
1461 ----------------------------------------------
1462 <make sure you have good level 0 dumps>
1463 make buildworld [9]
1464 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1465 [1]
1466 <reboot in single user> [3]
1467 mergemaster -p [5]
1468 make installworld
1469 mergemaster -i [4]
1470 make delete-old [6]
1471 <reboot>
1472
1473 Make sure that you've read the UPDATING file to understand the
1474 tweaks to various things you need. At this point in the life
1475 cycle of current, things change often and you are on your own
1476 to cope. The defaults can also change, so please read ALL of
1477 the UPDATING entries.
1478
1479 Also, if you are tracking -current, you must be subscribed to
1480 freebsd-current@freebsd.org. Make sure that before you update
1481 your sources that you have read and understood all the recent
1482 messages there. If in doubt, please track -stable which has
1483 much fewer pitfalls.
1484
1485 [1] If you have third party modules, such as vmware, you
1486 should disable them at this point so they don't crash your
1487 system on reboot.
1488
1489 [3] From the bootblocks, boot -s, and then do
1490 fsck -p
1491 mount -u /
1492 mount -a
1493 cd src
1494 adjkerntz -i # if CMOS is wall time
1495 Also, when doing a major release upgrade, it is required that
1496 you boot into single user mode to do the installworld.
1497
1498 [4] Note: This step is non-optional. Failure to do this step
1499 can result in a significant reduction in the functionality of the
1500 system. Attempting to do it by hand is not recommended and those
1501 that pursue this avenue should read this file carefully, as well
1502 as the archives of freebsd-current and freebsd-hackers mailing lists
1503 for potential gotchas. The -U option is also useful to consider.
1504 See mergemaster(8) for more information.
1505
1506 [5] Usually this step is a noop. However, from time to time
1507 you may need to do this if you get unknown user in the following
1508 step. It never hurts to do it all the time. You may need to
1509 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1510 install) after the buildworld before this step if you last updated
1511 from current before 20020224 or from -stable before 20020408.
1512
1513 [6] This only deletes old files and directories. Old libraries
1514 can be deleted by "make delete-old-libs", but you have to make
1515 sure that no program is using those libraries anymore.
1516
1517 [8] In order to have a kernel that can run the 4.x binaries needed to
1518 do an installworld, you must include the COMPAT_FREEBSD4 option in
1519 your kernel. Failure to do so may leave you with a system that is
1520 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1521 required to run the 5.x binaries on more recent kernels. And so on
1522 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1523
1524 Make sure that you merge any new devices from GENERIC since the
1525 last time you updated your kernel config file.
1526
1527 [9] When checking out sources, you must include the -P flag to have
1528 cvs prune empty directories.
1529
1530 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1531 "?=" instead of the "=" assignment operator, so that buildworld can
1532 override the CPUTYPE if it needs to.
1533
1534 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1535 not on the command line, or in /etc/make.conf. buildworld will
1536 warn if it is improperly defined.
1537FORMAT:
1538
1539This file contains a list, in reverse chronological order, of major
1540breakages in tracking -current. It is not guaranteed to be a complete
1541list of such breakages, and only contains entries since October 10, 2007.
1542If you need to see UPDATING entries from before that date, you will need
1543to fetch an UPDATING file from an older FreeBSD release.
1544
1545Copyright information:
1546
1547Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1548
1549Redistribution, publication, translation and use, with or without
1550modification, in full or in part, in any form or format of this
1551document are permitted without further permission from the author.
1552
1553THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1554IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1555WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1556DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1557INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1558(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1559SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1560HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1561STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1562IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1563POSSIBILITY OF SUCH DAMAGE.
1564
1565Contact Warner Losh if you have any questions about your use of
1566this document.
1567
1568$FreeBSD: head/UPDATING 232317 2012-02-29 21:38:31Z trociny $
2
3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>.
4See end of file for further details. For commonly done items, please see the
5COMMON ITEMS: section later in the file. These instructions assume that you
6basically know what you are doing. If not, then please consult the FreeBSD
7handbook.
8
9Items affecting the ports and packages system can be found in
10/usr/ports/UPDATING. Please read that file before running portupgrade.
11
12NOTE TO PEOPLE WHO THINK THAT FreeBSD 10.x IS SLOW:
13 FreeBSD 10.x has many debugging features turned on, in both the kernel
14 and userland. These features attempt to detect incorrect use of
15 system primitives, and encourage loud failure through extra sanity
16 checking and fail stop semantics. They also substantially impact
17 system performance. If you want to do performance measurement,
18 benchmarking, and optimization, you'll want to turn them off. This
19 includes various WITNESS- related kernel options, INVARIANTS, malloc
20 debugging flags in userland, and various verbose features in the
21 kernel. Many developers choose to disable these features on build
22 machines to maximize performance. (To disable malloc debugging, run
23 ln -s aj /etc/malloc.conf.)
24
2520120229:
26 Now unix domain sockets behave "as expected" on nullfs(5). Previously
27 nullfs(5) did not pass through all behaviours to the underlying layer,
28 as a result if we bound to a socket on the lower layer we could connect
29 only to the lower path; if we bound to the upper layer we could connect
30 only to the upper path. The new behavior is one can connect to both the
31 lower and the upper paths regardless what layer path one binds to.
32
3320120211:
34 The getifaddrs upgrade path broken with 20111215 has been restored.
35 If you have upgraded in between 20111215 and 20120209 you need to
36 recompile libc again with your kernel. You still need to recompile
37 world to be able to configure CARP but this restriction already
38 comes from 20111215.
39
4020120114:
41 The set_rcvar() function has been removed from /etc/rc.subr. All
42 base and ports rc.d scripts have been updated, so if you have a
43 port installed with a script in /usr/local/etc/rc.d you can either
44 hand-edit the rcvar= line, or reinstall the port.
45
46 An easy way to handle the mass-update of /etc/rc.d:
47 rm /etc/rc.d/* && mergemaster -i
48
4920120109:
50 panic(9) now stops other CPUs in the SMP systems, disables interrupts
51 on the current CPU and prevents other threads from running.
52 This behavior can be reverted using the kern.stop_scheduler_on_panic
53 tunable/sysctl.
54 The new behavior can be incompatible with kern.sync_on_panic.
55
5620111215:
57 The carp(4) facility has been changed significantly. Configuration
58 of the CARP protocol via ifconfig(8) has changed, as well as format
59 of CARP events submitted to devd(8) has changed. See manual pages
60 for more information. The arpbalance feature of carp(4) is currently
61 not supported anymore.
62
63 Size of struct in_aliasreq, struct in6_aliasreq has changed. User
64 utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8),
65 need to be recompiled.
66
6720111122:
68 The acpi_wmi(4) status device /dev/wmistat has been renamed to
69 /dev/wmistat0.
70
7120111108:
72 The option VFS_ALLOW_NONMPSAFE option has been added in order to
73 explicitely support non-MPSAFE filesystems.
74 It is on by default for all supported platform at this present
75 time.
76
7720111101:
78 The broken amd(4) driver has been replaced with esp(4) in the amd64,
79 i386 and pc98 GENERIC kernel configuration files.
80
8120110930:
82 sysinstall has been removed
83
8420110923:
85 The stable/9 branch created in subversion. This corresponds to the
86 RELENG_9 branch in CVS.
87
8820110913:
89 This commit modifies vfs_register() so that it uses a hash
90 calculation to set vfc_typenum, which is enabled by default.
91 The first time a system is booted after this change, the
92 vfc_typenum values will change for all file systems. The
93 main effect of this is a change to the NFS server file handles
94 for file systems that use vfc_typenum in their fsid, such as ZFS.
95 It will, however, prevent vfc_typenum from changing when file
96 systems are loaded in a different order for subsequent reboots.
97 To disable this, you can set vfs.typenumhash=0 in /boot/loader.conf
98 until you are ready to remount all NFS clients after a reboot.
99
10020110828:
101 Bump the shared library version numbers for libraries that
102 do not use symbol versioning, have changed the ABI compared
103 to stable/8 and which shared library version was not bumped.
104 Done as part of 9.0-RELEASE cycle.
105
10620110815:
107 During the merge of Capsicum features, the fget(9) KPI was modified.
108 This may require the rebuilding of out-of-tree device drivers --
109 issues have been reported specifically with the nVidia device driver.
110 __FreeBSD_version is bumped to 900041.
111
112 Also, there is a period between 20110811 and 20110814 where the
113 special devices /dev/{stdin,stdout,stderr} did not work correctly.
114 Building world from a kernel during that window may not work.
115
11620110628:
117 The packet filter (pf) code has been updated to OpenBSD 4.5.
118 You need to update userland tools to be in sync with kernel.
119 This update breaks backward compatibility with earlier pfsync(4)
120 versions. Care must be taken when updating redundant firewall setups.
121
12220110608:
123 The following sysctls and tunables are retired on x86 platforms:
124 machdep.hlt_cpus
125 machdep.hlt_logical_cpus
126 The following sysctl is retired:
127 machdep.hyperthreading_allowed
128 The sysctls were supposed to provide a way to dynamically offline and
129 online selected CPUs on x86 platforms, but the implementation has not
130 been reliable especially with SCHED_ULE scheduler.
131 machdep.hyperthreading_allowed tunable is still available to ignore
132 hyperthreading CPUs at OS level.
133 Individual CPUs can be disabled using hint.lapic.X.disabled tunable,
134 where X is an APIC ID of a CPU. Be advised, though, that disabling
135 CPUs in non-uniform fashion will result in non-uniform topology and
136 may lead to sub-optimal system performance with SCHED_ULE, which is
137 a default scheduler.
138
13920110607:
140 cpumask_t type is retired and cpuset_t is used in order to describe
141 a mask of CPUs.
142
14320110531:
144 Changes to ifconfig(8) for dynamic address family detection mandate
145 that you are running a kernel of 20110525 or later. Make sure to
146 follow the update procedure to boot a new kernel before installing
147 world.
148
14920110513:
150 Support for sun4v architecture is officially dropped
151
15220110503:
153 Several KPI breaking changes have been committed to the mii(4) layer,
154 the PHY drivers and consequently some Ethernet drivers using mii(4).
155 This means that miibus.ko and the modules of the affected Ethernet
156 drivers need to be recompiled.
157
158 Note to kernel developers: Given that the OUI bit reversion problem
159 was fixed as part of these changes all mii(4) commits related to OUIs,
160 i.e. to sys/dev/mii/miidevs, PHY driver probing and vendor specific
161 handling, no longer can be merged verbatim to stable/8 and previous
162 branches.
163
16420110430:
165 Users of the Atheros AR71xx SoC code now need to add 'device ar71xx_pci'
166 into their kernel configurations along with 'device pci'.
167
16820110427:
169 The default NFS client is now the new NFS client, so fstype "newnfs"
170 is now "nfs" and the regular/old NFS client is now fstype "oldnfs".
171 Although mounts via fstype "nfs" will usually work without userland
172 changes, it is recommended that the mount(8) and mount_nfs(8)
173 commands be rebuilt from sources and that a link to mount_nfs called
174 mount_oldnfs be created. The new client is compiled into the
175 kernel with "options NFSCL" and this is needed for diskless root
176 file systems. The GENERIC kernel configs have been changed to use
177 NFSCL and NFSD (the new server) instead of NFSCLIENT and NFSSERVER.
178 To use the regular/old client, you can "mount -t oldnfs ...". For
179 a diskless root file system, you must also include a line like:
180
181 vfs.root.mountfrom="oldnfs:"
182
183 in the boot/loader.conf on the root fs on the NFS server to make
184 a diskless root fs use the old client.
185
18620110424:
187 The GENERIC kernels for all architectures now default to the new
188 CAM-based ATA stack. It means that all legacy ATA drivers were
189 removed and replaced by respective CAM drivers. If you are using
190 ATA device names in /etc/fstab or other places, make sure to update
191 them respectively (adX -> adaY, acdX -> cdY, afdX -> daY, astX -> saY,
192 where 'Y's are the sequential numbers starting from zero for each type
193 in order of detection, unless configured otherwise with tunables,
194 see cam(4)). There will be symbolic links created in /dev/ to map
195 old adX devices to the respective adaY. They should provide basic
196 compatibility for file systems mounting in most cases, but they do
197 not support old user-level APIs and do not have respective providers
198 in GEOM. Consider using updated management tools with new device names.
199
200 It is possible to load devices ahci, ata, siis and mvs as modules,
201 but option ATA_CAM should remain in kernel configuration to make ata
202 module work as CAM driver supporting legacy ATA controllers. Device ata
203 still can be used in modular fashion (atacore + ...). Modules atadisk
204 and atapi* are not used and won't affect operation in ATA_CAM mode.
205 Note that to use CAM-based ATA kernel should include CAM devices
206 scbus, pass, da (or explicitly ada), cd and optionally others. All of
207 them are parts of the cam module.
208
209 ataraid(4) functionality is now supported by the RAID GEOM class.
210 To use it you can load geom_raid kernel module and use graid(8) tool
211 for management. Instead of /dev/arX device names, use /dev/raid/rX.
212
213 No kernel config options or code have been removed, so if a problem
214 arises, please report it and optionally revert to the old ATA stack.
215 In order to do it you can remove from the kernel config:
216 options ATA_CAM
217 device ahci
218 device mvs
219 device siis
220 , and instead add back:
221 device atadisk # ATA disk drives
222 device ataraid # ATA RAID drives
223 device atapicd # ATAPI CDROM drives
224 device atapifd # ATAPI floppy drives
225 device atapist # ATAPI tape drives
226
22720110423:
228 The default NFS server has been changed to the new server, which
229 was referred to as the experimental server. If you need to switch
230 back to the old NFS server, you must now put the "-o" option on
231 both the mountd and nfsd commands. This can be done using the
232 mountd_flags and nfs_server_flags rc.conf variables until an
233 update to the rc scripts is committed, which is coming soon.
234
23520110418:
236 The GNU Objective-C runtime library (libobjc), and other Objective-C
237 related components have been removed from the base system. If you
238 require an Objective-C library, please use one of the available ports.
239
24020110331:
241 ath(4) has been split into bus- and device- modules. if_ath contains
242 the HAL, the TX rate control and the network device code. if_ath_pci
243 contains the PCI bus glue. For Atheros MIPS embedded systems, if_ath_ahb
244 contains the AHB glue. Users need to load both if_ath_pci and if_ath
245 in order to use ath on everything else.
246
247 TO REPEAT: if_ath_ahb is not needed for normal users. Normal users only
248 need to load if_ath and if_ath_pci for ath(4) operation.
249
25020110314:
251 As part of the replacement of sysinstall, the process of building
252 release media has changed significantly. For details, please re-read
253 release(7), which has been updated to reflect the new build process.
254
25520110218:
256 GNU binutils 2.17.50 (as of 2007-07-03) has been merged to -HEAD. This
257 is the last available version under GPLv2. It brings a number of new
258 features, such as support for newer x86 CPU's (with SSE-3, SSSE-3, SSE
259 4.1 and SSE 4.2), better support for powerpc64, a number of new
260 directives, and lots of other small improvements. See the ChangeLog
261 file in contrib/binutils for the full details.
262
26320110218:
264 IPsec's HMAC_SHA256-512 support has been fixed to be RFC4868
265 compliant, and will now use half of hash for authentication.
266 This will break interoperability with all stacks (including all
267 actual FreeBSD versions) who implement
268 draft-ietf-ipsec-ciph-sha-256-00 (they use 96 bits of hash for
269 authentication).
270 The only workaround with such peers is to use another HMAC
271 algorithm for IPsec ("phase 2") authentication.
272
27320110207:
274 Remove the uio_yield prototype and symbol. This function has
275 been misnamed since it was introduced and should not be
276 globally exposed with this name. The equivalent functionality
277 is now available using kern_yield(curthread->td_user_pri).
278 The function remains undocumented.
279
28020110112:
281 A SYSCTL_[ADD_]UQUAD was added for unsigned uint64_t pointers,
282 symmetric with the existing SYSCTL_[ADD_]QUAD. Type checking
283 for scalar sysctls is defined but disabled. Code that needs
284 UQUAD to pass the type checking that must compile on older
285 systems where the define is not present can check against
286 __FreeBSD_version >= 900030.
287
288 The system dialog(1) has been replaced with a new version previously
289 in ports as devel/cdialog. dialog(1) is mostly command-line compatible
290 with the previous version, but the libdialog associated with it has
291 a largely incompatible API. As such, the original version of libdialog
292 will be kept temporarily as libodialog, until its base system consumers
293 are replaced or updated. Bump __FreeBSD_version to 900030.
294
29520110103:
296 If you are trying to run make universe on a -stable system, and you get
297 the following warning:
298 "Makefile", line 356: "Target architecture for i386/conf/GENERIC
299 unknown. config(8) likely too old."
300 or something similar to it, then you must upgrade your -stable system
301 to 8.2-Release or newer (really, any time after r210146 7/15/2010 in
302 stable/8) or build the config from the latest stable/8 branch and
303 install it on your system.
304
305 Prior to this date, building a current universe on 8-stable system from
306 between 7/15/2010 and 1/2/2011 would result in a weird shell parsing
307 error in the first kernel build phase. A new config on those old
308 systems will fix that problem for older versions of -current.
309
31020101228:
311 The TCP stack has been modified to allow Khelp modules to interact with
312 it via helper hook points and store per-connection data in the TCP
313 control block. Bump __FreeBSD_version to 900029. User space tools that
314 rely on the size of struct tcpcb in tcp_var.h (e.g. sockstat) need to
315 be recompiled.
316
31720101114:
318 Generic IEEE 802.3 annex 31B full duplex flow control support has been
319 added to mii(4) and bge(4), bce(4), msk(4), nfe(4) and stge(4) along
320 with brgphy(4), e1000phy(4) as well as ip1000phy() have been converted
321 to take advantage of it instead of using custom implementations. This
322 means that these drivers now no longer unconditionally advertise
323 support for flow control but only do so if flow control is a selected
324 media option. This was implemented in the generic support that way in
325 order to allow flow control to be switched on and off via ifconfig(8)
326 with the PHY specific default to typically off in order to protect
327 from unwanted effects. Consequently, if you used flow control with
328 one of the above mentioned drivers you now need to explicitly enable
329 it, for example via:
330 ifconfig bge0 media auto mediaopt flowcontrol
331
332 Along with the above mentioned changes generic support for setting
333 1000baseT master mode also has been added and brgphy(4), ciphy(4),
334 e1000phy(4) as well as ip1000phy(4) have been converted to take
335 advantage of it. This means that these drivers now no longer take the
336 link0 parameter for selecting master mode but the master media option
337 has to be used instead, for example like in the following:
338 ifconfig bge0 media 1000baseT mediaopt full-duplex,master
339
340 Selection of master mode now is also available with all other PHY
341 drivers supporting 1000baseT.
342
34320101111:
344 The TCP stack has received a significant update to add support for
345 modularised congestion control and generally improve the clarity of
346 congestion control decisions. Bump __FreeBSD_version to 900025. User
347 space tools that rely on the size of struct tcpcb in tcp_var.h (e.g.
348 sockstat) need to be recompiled.
349
35020101002:
351 The man(1) utility has been replaced by a new version that no longer
352 uses /etc/manpath.config. Please consult man.conf(5) for how to
353 migrate local entries to the new format.
354
35520100928:
356 The copyright strings printed by login(1) and sshd(8) at the time of a
357 new connection have been removed to follow other operating systems and
358 upstream sshd.
359
36020100915:
361 A workaround for a fixed ld bug has been removed in kernel code,
362 so make sure that your system ld is built from sources after
363 revision 210245 from 2010-07-19 (r211583 if building head kernel
364 on stable/8, r211584 for stable/7; both from 2010-08-21).
365 A symptom of incorrect ld version is different addresses for
366 set_pcpu section and __start_set_pcpu symbol in kernel and/or modules.
367
36820100913:
369 The $ipv6_prefer variable in rc.conf(5) has been split into
370 $ip6addrctl_policy and $ipv6_activate_all_interfaces.
371
372 The $ip6addrctl_policy is a variable to choose a pre-defined
373 address selection policy set by ip6addrctl(8). A value
374 "ipv4_prefer", "ipv6_prefer" or "AUTO" can be specified. The
375 default is "AUTO".
376
377 The $ipv6_activate_all_interfaces specifies whether IFDISABLED
378 flag (see an entry of 20090926) is set on an interface with no
379 corresponding $ifconfig_IF_ipv6 line. The default is "NO" for
380 security reason. If you want IPv6 link-local address on all
381 interfaces by default, set this to "YES".
382
383 The old ipv6_prefer="YES" is equivalent to
384 ipv6_activate_all_interfaces="YES" and
385 ip6addrctl_policy="ipv6_prefer".
386
38720100913:
388 DTrace has grown support for userland tracing. Due to this, DTrace is
389 now i386 and amd64 only.
390 dtruss(1) is now installed by default on those systems and a new
391 kernel module is needed for userland tracing: fasttrap.
392 No changes to your kernel config file are necessary to enable
393 userland tracing, but you might consider adding 'STRIP=' and
394 'CFLAGS+=-fno-omit-frame-pointer' to your make.conf if you want
395 to have informative userland stack traces in DTrace (ustack).
396
39720100725:
398 The acpi_aiboost(4) driver has been removed in favor of the new
399 aibs(4) driver. You should update your kernel configuration file.
400
40120100722:
402 BSD grep has been imported to the base system and it is built by
403 default. It is completely BSD licensed, highly GNU-compatible, uses
404 less memory than its GNU counterpart and has a small codebase.
405 However, it is slower than its GNU counterpart, which is mostly
406 noticeable for larger searches, for smaller ones it is measurable
407 but not significant. The reason is complex, the most important factor
408 is that we lack a modern and efficient regex library and GNU
409 overcomes this by optimizing the searches internally. Future work
410 on improving the regex performance is planned, for the meantime,
411 users that need better performance, can build GNU grep instead by
412 setting the WITH_GNU_GREP knob.
413
41420100713:
415 Due to the import of powerpc64 support, all existing powerpc kernel
416 configuration files must be updated with a machine directive like this:
417 machine powerpc powerpc
418
419 In addition, an updated config(8) is required to build powerpc kernels
420 after this change.
421
42220100713:
423 A new version of ZFS (version 15) has been merged to -HEAD.
424 This version uses a python library for the following subcommands:
425 zfs allow, zfs unallow, zfs groupspace, zfs userspace.
426 For full functionality of these commands the following port must
427 be installed: sysutils/py-zfs
428
42920100429:
430 'vm_page's are now hashed by physical address to an array of mutexes.
431 Currently this is only used to serialize access to hold_count. Over
432 time the page queue mutex will be peeled away. This changes the size
433 of pmap on every architecture. And requires all callers of vm_page_hold
434 and vm_page_unhold to be updated.
435
43620100402:
437 WITH_CTF can now be specified in src.conf (not recommended, there
438 are some problems with static executables), make.conf (would also
439 affect ports which do not use GNU make and do not override the
440 compile targets) or in the kernel config (via "makeoptions
441 WITH_CTF=yes").
442 When WITH_CTF was specified there before this was silently ignored,
443 so make sure that WITH_CTF is not used in places which could lead
444 to unwanted behavior.
445
44620100311:
447 The kernel option COMPAT_IA32 has been replaced with COMPAT_FREEBSD32
448 to allow 32-bit compatibility on non-x86 platforms. All kernel
449 configurations on amd64 and ia64 platforms using these options must
450 be modified accordingly.
451
45220100113:
453 The utmp user accounting database has been replaced with utmpx,
454 the user accounting interface standardized by POSIX.
455 Unfortunately the semantics of utmp and utmpx don't match,
456 making it practically impossible to support both interfaces.
457 The user accounting database is used by tools like finger(1),
458 last(1), talk(1), w(1) and ac(8).
459
460 All applications in the base system use utmpx. This means only
461 local binaries (e.g. from the ports tree) may still use these
462 utmp database files. These applications must be rebuilt to make
463 use of utmpx.
464
465 After the system has been upgraded, it is safe to remove the old
466 log files (/var/run/utmp, /var/log/lastlog and /var/log/wtmp*),
467 assuming their contents is of no importance anymore. Old wtmp
468 databases can only be used by last(1) and ac(8) after they have
469 been converted to the new format using wtmpcvt(1).
470
47120100108:
472 Introduce the kernel thread "deadlock resolver" (which can be enabled
473 via the DEADLKRES option, see NOTES for more details) and the
474 sleepq_type() function for sleepqueues.
475
47620091202:
477 The rc.firewall and rc.firewall6 were unified, and
478 rc.firewall6 and rc.d/ip6fw were removed.
479 According to the removal of rc.d/ip6fw, ipv6_firewall_* rc
480 variables are obsoleted. Instead, the following new rc
481 variables are added to rc.d/ipfw:
482
483 firewall_client_net_ipv6, firewall_simple_iif_ipv6,
484 firewall_simple_inet_ipv6, firewall_simple_oif_ipv6,
485 firewall_simple_onet_ipv6, firewall_trusted_ipv6
486
487 The meanings correspond to the relevant IPv4 variables.
488
48920091125:
490 8.0-RELEASE.
491
49220091113:
493 The default terminal emulation for syscons(4) has been changed
494 from cons25 to xterm on all platforms except pc98. This means
495 that the /etc/ttys file needs to be updated to ensure correct
496 operation of applications on the console.
497
498 The terminal emulation style can be toggled per window by using
499 vidcontrol(1)'s -T flag. The TEKEN_CONS25 kernel configuration
500 options can be used to change the compile-time default back to
501 cons25.
502
503 To prevent graphical artifacts, make sure the TERM environment
504 variable is set to match the terminal emulation that is being
505 performed by syscons(4).
506
50720091109:
508 The layout of the structure ieee80211req_scan_result has changed.
509 Applications that require wireless scan results (e.g. ifconfig(8))
510 from net80211 need to be recompiled.
511
512 Applications such as wpa_supplicant(8) may require a full world
513 build without using NO_CLEAN in order to get synchronized with the
514 new structure.
515
51620091025:
517 The iwn(4) driver has been updated to support the 5000 and 5150 series.
518 There's one kernel module for each firmware. Adding "device iwnfw"
519 to the kernel configuration file means including all three firmware
520 images inside the kernel. If you want to include just the one for
521 your wireless card, use the devices iwn4965fw, iwn5000fw or
522 iwn5150fw.
523
52420090926:
525 The rc.d/network_ipv6, IPv6 configuration script has been integrated
526 into rc.d/netif. The changes are the following:
527
528 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
529 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
530 Note that both variables need the "inet6" keyword at the head.
531
532 Do not set $ipv6_network_interfaces manually if you do not
533 understand what you are doing. It is not needed in most cases.
534
535 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
536 they are obsolete.
537
538 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
539 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
540
541 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
542 all configured interfaces have "inet6 accept_rtadv" in the
543 $ifconfig_IF_ipv6. These are for backward compatibility.
544
545 3. A new variable $ipv6_prefer has been added. If NO, IPv6
546 functionality of interfaces with no corresponding
547 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
548 and the default address selection policy of ip6addrctl(8)
549 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
550 Note that if you want to configure IPv6 functionality on the
551 disabled interfaces after boot, first you need to clear the flag by
552 using ifconfig(8) like:
553
554 ifconfig em0 inet6 -ifdisabled
555
556 If YES, the default address selection policy is set as
557 IPv6-preferred.
558
559 The default value of $ipv6_prefer is NO.
560
561 4. If your system need to receive Router Advertisement messages,
562 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
563 scripts automatically invoke rtsol(8) when the interface becomes
564 UP. The Router Advertisement messages are used for SLAAC
565 (State-Less Address AutoConfiguration).
566
56720090922:
568 802.11s D3.03 support was committed. This is incompatible with the
569 previous code, which was based on D3.0.
570
57120090912:
572 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
573 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
574 control whether accepting Router Advertisement messages or not.
575 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
576 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
577 The ifconfig(8) utility now supports these flags.
578
57920090910:
580 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
581 mount(8) and -a option for df(1) to see them.
582
58320090825:
584 The old tunable hw.bus.devctl_disable has been superseded by
585 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
586 replaced by hw.bus.devctl_queue=0. The default for this new tunable
587 is 1000.
588
58920090813:
590 Remove the option STOP_NMI. The default action is now to use NMI only
591 for KDB via the newly introduced function stop_cpus_hard() and
592 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
593
59420090803:
595 The stable/8 branch created in subversion. This corresponds to the
596 RELENG_8 branch in CVS.
597
59820090719:
599 Bump the shared library version numbers for all libraries that do not
600 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
601 __FreeBSD_version to 800105.
602
60320090714:
604 Due to changes in the implementation of virtual network stack support,
605 all network-related kernel modules must be recompiled. As this change
606 breaks the ABI, bump __FreeBSD_version to 800104.
607
60820090713:
609 The TOE interface to the TCP syncache has been modified to remove
610 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
611 The cxgb driver is the only TOE consumer affected by this change, and
612 needs to be recompiled along with the kernel. As this change breaks
613 the ABI, bump __FreeBSD_version to 800103.
614
61520090712:
616 Padding has been added to struct tcpcb, sackhint and tcpstat in
617 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
618 maintaining the ABI. However, this change breaks the ABI, so bump
619 __FreeBSD_version to 800102. User space tools that rely on the size of
620 any of these structs (e.g. sockstat) need to be recompiled.
621
62220090630:
623 The NFS_LEGACYRPC option has been removed along with the old kernel
624 RPC implementation that this option selected. Kernel configurations
625 may need to be adjusted.
626
62720090629:
628 The network interface device nodes at /dev/net/<interface> have been
629 removed. All ioctl operations can be performed the normal way using
630 routing sockets. The kqueue functionality can generally be replaced
631 with routing sockets.
632
63320090628:
634 The documentation from the FreeBSD Documentation Project (Handbook,
635 FAQ, etc.) is now installed via packages by sysinstall(8) and under
636 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
637
63820090624:
639 The ABI of various structures related to the SYSV IPC API have been
640 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
641 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
642 800100.
643
64420090622:
645 Layout of struct vnet has changed as routing related variables were
646 moved to their own Vimage module. Modules need to be recompiled. Bump
647 __FreeBSD_version to 800099.
648
64920090619:
650 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
651 respectively. As long as no more than 16 groups per process are used,
652 no changes should be visible. When more than 16 groups are used, old
653 binaries may fail if they call getgroups() or getgrouplist() with
654 statically sized storage. Recompiling will work around this, but
655 applications should be modified to use dynamically allocated storage
656 for group arrays as POSIX.1-2008 does not cap an implementation's
657 number of supported groups at NGROUPS_MAX+1 as previous versions did.
658
659 NFS and portalfs mounts may also be affected as the list of groups is
660 truncated to 16. Users of NFS who use more than 16 groups, should
661 take care that negative group permissions are not used on the exported
662 file systems as they will not be reliable unless a GSSAPI based
663 authentication method is used.
664
66520090616:
666 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
667 option compiles in the support for adaptive spinning for lockmgrs
668 which want to enable it. The lockinit() function now accepts the flag
669 LK_ADAPTIVE in order to make the lock object subject to adaptive
670 spinning when both held in write and read mode.
671
67220090613:
673 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
674 changed. User applications that use this ioctl need to be rebuilt.
675
67620090611:
677 The layout of struct thread has changed. Kernel and modules need to
678 be rebuilt.
679
68020090608:
681 The layout of structs ifnet, domain, protosw and vnet_net has changed.
682 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
683
68420090602:
685 window(1) has been removed from the base system. It can now be
686 installed from ports. The port is called misc/window.
687
68820090601:
689 The way we are storing and accessing `routing table' entries has
690 changed. Programs reading the FIB, like netstat, need to be
691 re-compiled.
692
69320090601:
694 A new netisr implementation has been added for FreeBSD 8. Network
695 file system modules, such as igmp, ipdivert, and others, should be
696 rebuilt.
697 Bump __FreeBSD_version to 800096.
698
69920090530:
700 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
701 more valid.
702
70320090530:
704 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
705 Bump __FreeBSD_version to 800094.
706
70720090529:
708 Add mnt_xflag field to 'struct mount'. File system modules need to be
709 rebuilt.
710 Bump __FreeBSD_version to 800093.
711
71220090528:
713 The compiling option ADAPTIVE_SX has been retired while it has been
714 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
715 The KPI for sx_init_flags() changes as accepting flags:
716 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
717 been introduced in order to handle the reversed logic.
718 Bump __FreeBSD_version to 800092.
719
72020090527:
721 Add support for hierarchical jails. Remove global securelevel.
722 Bump __FreeBSD_version to 800091.
723
72420090523:
725 The layout of struct vnet_net has changed, therefore modules
726 need to be rebuilt.
727 Bump __FreeBSD_version to 800090.
728
72920090523:
730 The newly imported zic(8) produces a new format in the output. Please
731 run tzsetup(8) to install the newly created data to /etc/localtime.
732
73320090520:
734 The sysctl tree for the usb stack has renamed from hw.usb2.* to
735 hw.usb.* and is now consistent again with previous releases.
736
73720090520:
738 802.11 monitor mode support was revised and driver api's were changed.
739 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
740 of DLT_IEEE802_11. No user-visible data structures were changed but
741 applications that use DLT_IEEE802_11 may require changes.
742 Bump __FreeBSD_version to 800088.
743
74420090430:
745 The layout of the following structs has changed: sysctl_oid,
746 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
747 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
748 panics may be experienced. World rebuild is required for
749 correctly checking networking state from userland.
750 Bump __FreeBSD_version to 800085.
751
75220090429:
753 MLDv2 and Source-Specific Multicast (SSM) have been merged
754 to the IPv6 stack. VIMAGE hooks are in but not yet used.
755 The implementation of SSM within FreeBSD's IPv6 stack closely
756 follows the IPv4 implementation.
757
758 For kernel developers:
759
760 * The most important changes are that the ip6_output() and
761 ip6_input() paths no longer take the IN6_MULTI_LOCK,
762 and this lock has been downgraded to a non-recursive mutex.
763
764 * As with the changes to the IPv4 stack to support SSM, filtering
765 of inbound multicast traffic must now be performed by transport
766 protocols within the IPv6 stack. This does not apply to TCP and
767 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
768
769 * The KPIs used by IPv6 multicast are similar to those used by
770 the IPv4 stack, with the following differences:
771 * im6o_mc_filter() is analogous to imo_multicast_filter().
772 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
773 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
774 * IN6_LOOKUP_MULTI() has been deprecated and removed.
775 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
776 for MLDv1 have an additional 'timer' argument which is used to
777 jitter the initial membership report for the solicited-node
778 multicast membership on-link.
779 * This is not strictly needed for MLDv2, which already jitters
780 its report transmissions. However, the 'timer' argument is
781 preserved in case MLDv1 is active on the interface.
782
783 * The KAME linked-list based IPv6 membership implementation has
784 been refactored to use a vector similar to that used by the IPv4
785 stack.
786 Code which maintains a list of its own multicast memberships
787 internally, e.g. carp, has been updated to reflect the new
788 semantics.
789
790 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
791 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
792 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
793 implementation constraint which needs to be addressed in HEAD.
794
795 For application developers:
796
797 * The changes are broadly similar to those made for the IPv4
798 stack.
799
800 * The use of IPv4 and IPv6 multicast socket options on the same
801 socket, using mapped addresses, HAS NOT been tested or supported.
802
803 * There are a number of issues with the implementation of various
804 IPv6 multicast APIs which need to be resolved in the API surface
805 before the implementation is fully compatible with KAME userland
806 use, and these are mostly to do with interface index treatment.
807
808 * The literature available discusses the use of either the delta / ASM
809 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
810 using setsourcefilter(3)/getsourcefilter(3). For more information
811 please refer to RFC 3768, 'Socket Interface Extensions for
812 Multicast Source Filters'.
813
814 * Applications which use the published RFC 3678 APIs should be fine.
815
816 For systems administrators:
817
818 * The mtest(8) utility has been refactored to support IPv6, in
819 addition to IPv4. Interface addresses are no longer accepted
820 as arguments, their names must be used instead. The utility
821 will map the interface name to its first IPv4 address as
822 returned by getifaddrs(3).
823
824 * The ifmcstat(8) utility has also been updated to print the MLDv2
825 endpoint state and source filter lists via sysctl(3).
826
827 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
828 loopback of IPv6 multicast datagrams by default; it defaults to 1
829 to preserve the existing behaviour. Disabling multicast loopback is
830 recommended for optimal system performance.
831
832 * The IPv6 MROUTING code has been changed to examine this sysctl
833 instead of attempting to perform a group lookup before looping
834 back forwarded datagrams.
835
836 Bump __FreeBSD_version to 800084.
837
83820090422:
839 Implement low-level Bluetooth HCI API.
840 Bump __FreeBSD_version to 800083.
841
84220090419:
843 The layout of struct malloc_type, used by modules to register new
844 memory allocation types, has changed. Most modules will need to
845 be rebuilt or panics may be experienced.
846 Bump __FreeBSD_version to 800081.
847
84820090415:
849 Anticipate overflowing inp_flags - add inp_flags2.
850 This changes most offsets in inpcb, so checking v4 connection
851 state will require a world rebuild.
852 Bump __FreeBSD_version to 800080.
853
85420090415:
855 Add an llentry to struct route and struct route_in6. Modules
856 embedding a struct route will need to be recompiled.
857 Bump __FreeBSD_version to 800079.
858
85920090414:
860 The size of rt_metrics_lite and by extension rtentry has changed.
861 Networking administration apps will need to be recompiled.
862 The route command now supports show as an alias for get, weighting
863 of routes, sticky and nostick flags to alter the behavior of stateful
864 load balancing.
865 Bump __FreeBSD_version to 800078.
866
86720090408:
868 Do not use Giant for kbdmux(4) locking. This is wrong and
869 apparently causing more problems than it solves. This will
870 re-open the issue where interrupt handlers may race with
871 kbdmux(4) in polling mode. Typical symptoms include (but
872 not limited to) duplicated and/or missing characters when
873 low level console functions (such as gets) are used while
874 interrupts are enabled (for example geli password prompt,
875 mountroot prompt etc.). Disabling kbdmux(4) may help.
876
87720090407:
878 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
879 kernel modules referencing any of the above need to be recompiled.
880 Bump __FreeBSD_version to 800075.
881
88220090320:
883 GEOM_PART has become the default partition slicer for storage devices,
884 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
885 introduces some changes:
886
887 MSDOS/EBR: the devices created from MSDOS extended partition entries
888 (EBR) can be named differently than with GEOM_MBR and are now symlinks
889 to devices with offset-based names. fstabs may need to be modified.
890
891 BSD: the "geometry does not match label" warning is harmless in most
892 cases but it points to problems in file system misalignment with
893 disk geometry. The "c" partition is now implicit, covers the whole
894 top-level drive and cannot be (mis)used by users.
895
896 General: Kernel dumps are now not allowed to be written to devices
897 whose partition types indicate they are meant to be used for file
898 systems (or, in case of MSDOS partitions, as something else than
899 the "386BSD" type).
900
901 Most of these changes date approximately from 200812.
902
90320090319:
904 The uscanner(4) driver has been removed from the kernel. This follows
905 Linux removing theirs in 2.6 and making libusb the default interface
906 (supported by sane).
907
90820090319:
909 The multicast forwarding code has been cleaned up. netstat(1)
910 only relies on KVM now for printing bandwidth upcall meters.
911 The IPv4 and IPv6 modules are split into ip_mroute_mod and
912 ip6_mroute_mod respectively. The config(5) options for statically
913 compiling this code remain the same, i.e. 'options MROUTING'.
914
91520090315:
916 Support for the IFF_NEEDSGIANT network interface flag has been
917 removed, which means that non-MPSAFE network device drivers are no
918 longer supported. In particular, if_ar, if_sr, and network device
919 drivers from the old (legacy) USB stack can no longer be built or
920 used.
921
92220090313:
923 POSIX.1 Native Language Support (NLS) has been enabled in libc and
924 a bunch of new language catalog files have also been added.
925 This means that some common libc messages are now localized and
926 they depend on the LC_MESSAGES environmental variable.
927
92820090313:
929 The k8temp(4) driver has been renamed to amdtemp(4) since
930 support for Family 10 and Family 11 CPU families was added.
931
93220090309:
933 IGMPv3 and Source-Specific Multicast (SSM) have been merged
934 to the IPv4 stack. VIMAGE hooks are in but not yet used.
935
936 For kernel developers, the most important changes are that the
937 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
938 and this lock has been downgraded to a non-recursive mutex.
939
940 Transport protocols (UDP, Raw IP) are now responsible for filtering
941 inbound multicast traffic according to group membership and source
942 filters. The imo_multicast_filter() KPI exists for this purpose.
943 Transports which do not use multicast (SCTP, TCP) already reject
944 multicast by default. Forwarding and receive performance may improve
945 as a mutex acquisition is no longer needed in the ip_input()
946 low-level input path. in_addmulti() and in_delmulti() are shimmed
947 to new KPIs which exist to support SSM in-kernel.
948
949 For application developers, it is recommended that loopback of
950 multicast datagrams be disabled for best performance, as this
951 will still cause the lock to be taken for each looped-back
952 datagram transmission. The net.inet.ip.mcast.loop sysctl may
953 be tuned to 0 to disable loopback by default; it defaults to 1
954 to preserve the existing behaviour.
955
956 For systems administrators, to obtain best performance with
957 multicast reception and multiple groups, it is always recommended
958 that a card with a suitably precise hash filter is used. Hash
959 collisions will still result in the lock being taken within the
960 transport protocol input path to check group membership.
961
962 If deploying FreeBSD in an environment with IGMP snooping switches,
963 it is recommended that the net.inet.igmp.sendlocal sysctl remain
964 enabled; this forces 224.0.0.0/24 group membership to be announced
965 via IGMP.
966
967 The size of 'struct igmpstat' has changed; netstat needs to be
968 recompiled to reflect this.
969 Bump __FreeBSD_version to 800070.
970
97120090309:
972 libusb20.so.1 is now installed as libusb.so.1 and the ports system
973 updated to use it. This requires a buildworld/installworld in order to
974 update the library and dependencies (usbconfig, etc). Its advisable to
975 rebuild all ports which uses libusb. More specific directions are given
976 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
977 libusb are no longer required and can be removed.
978
97920090302:
980 A workaround is committed to allow the creation of System V shared
981 memory segment of size > 2 GB on the 64-bit architectures.
982 Due to a limitation of the existing ABI, the shm_segsz member
983 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
984 wrong for large segments. Note that limits must be explicitly
985 raised to allow such segments to be created.
986
98720090301:
988 The layout of struct ifnet has changed, requiring a rebuild of all
989 network device driver modules.
990
99120090227:
992 The /dev handling for the new USB stack has changed, a
993 buildworld/installworld is required for libusb20.
994
99520090223:
996 The new USB2 stack has now been permanently moved in and all kernel and
997 module names reverted to their previous values (eg, usb, ehci, ohci,
998 ums, ...). The old usb stack can be compiled in by prefixing the name
999 with the letter 'o', the old usb modules have been removed.
1000 Updating entry 20090216 for xorg and 20090215 for libmap may still
1001 apply.
1002
100320090217:
1004 The rc.conf(5) option if_up_delay has been renamed to
1005 defaultroute_delay to better reflect its purpose. If you have
1006 customized this setting in /etc/rc.conf you need to update it to
1007 use the new name.
1008
100920090216:
1010 xorg 7.4 wants to configure its input devices via hald which does not
1011 yet work with USB2. If the keyboard/mouse does not work in xorg then
1012 add
1013 Option "AllowEmptyInput" "off"
1014 to your ServerLayout section. This will cause X to use the configured
1015 kbd and mouse sections from your xorg.conf.
1016
101720090215:
1018 The GENERIC kernels for all architectures now default to the new USB2
1019 stack. No kernel config options or code have been removed so if a
1020 problem arises please report it and optionally revert to the old USB
1021 stack. If you are loading USB kernel modules or have a custom kernel
1022 that includes GENERIC then ensure that usb names are also changed over,
1023 eg uftdi -> usb2_serial_ftdi.
1024
1025 Older programs linked against the ports libusb 0.1 need to be
1026 redirected to the new stack's libusb20. /etc/libmap.conf can
1027 be used for this:
1028 # Map old usb library to new one for usb2 stack
1029 libusb-0.1.so.8 libusb20.so.1
1030
103120090209:
1032 All USB ethernet devices now attach as interfaces under the name ueN
1033 (eg. ue0). This is to provide a predictable name as vendors often
1034 change usb chipsets in a product without notice.
1035
103620090203:
1037 The ichsmb(4) driver has been changed to require SMBus slave
1038 addresses be left-justified (xxxxxxx0b) rather than right-justified.
1039 All of the other SMBus controller drivers require left-justified
1040 slave addresses, so this change makes all the drivers provide the
1041 same interface.
1042
104320090201:
1044 INET6 statistics (struct ip6stat) was updated.
1045 netstat(1) needs to be recompiled.
1046
104720090119:
1048 NTFS has been removed from GENERIC kernel on amd64 to match
1049 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
1050 will load ntfs.ko module automatically when NTFS support is
1051 actually needed, unless ntfs.ko is not installed or security
1052 level prohibits loading kernel modules. If either is the case,
1053 "options NTFS" has to be added into kernel config.
1054
105520090115:
1056 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
1057 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
1058 800061. User space tools that rely on the size of struct tcpcb in
1059 tcp_var.h (e.g. sockstat) need to be recompiled.
1060
106120081225:
1062 ng_tty(4) module updated to match the new TTY subsystem.
1063 Due to API change, user-level applications must be updated.
1064 New API support added to mpd5 CVS and expected to be present
1065 in next mpd5.3 release.
1066
106720081219:
1068 With __FreeBSD_version 800060 the makefs tool is part of
1069 the base system (it was a port).
1070
107120081216:
1072 The afdata and ifnet locks have been changed from mutexes to
1073 rwlocks, network modules will need to be re-compiled.
1074
107520081214:
1076 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
1077 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
1078 The new code reduced struct rtentry{} by 16 bytes on 32-bit
1079 architecture and 40 bytes on 64-bit architecture. The userland
1080 applications "arp" and "ndp" have been updated accordingly.
1081 The output from "netstat -r" shows only routing entries and
1082 none of the L2 information.
1083
108420081130:
1085 __FreeBSD_version 800057 marks the switchover from the
1086 binary ath hal to source code. Users must add the line:
1087
1088 options AH_SUPPORT_AR5416
1089
1090 to their kernel config files when specifying:
1091
1092 device ath_hal
1093
1094 The ath_hal module no longer exists; the code is now compiled
1095 together with the driver in the ath module. It is now
1096 possible to tailor chip support (i.e. reduce the set of chips
1097 and thereby the code size); consult ath_hal(4) for details.
1098
109920081121:
1100 __FreeBSD_version 800054 adds memory barriers to
1101 <machine/atomic.h>, new interfaces to ifnet to facilitate
1102 multiple hardware transmit queues for cards that support
1103 them, and a lock-less ring-buffer implementation to
1104 enable drivers to more efficiently manage queueing of
1105 packets.
1106
110720081117:
1108 A new version of ZFS (version 13) has been merged to -HEAD.
1109 This version has zpool attribute "listsnapshots" off by
1110 default, which means "zfs list" does not show snapshots,
1111 and is the same as Solaris behavior.
1112
111320081028:
1114 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
1115
111620081009:
1117 The uhci, ohci, ehci and slhci USB Host controller drivers have
1118 been put into separate modules. If you load the usb module
1119 separately through loader.conf you will need to load the
1120 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
1121 controller add the following to loader.conf:
1122
1123 uhci_load="YES"
1124 ehci_load="YES"
1125
112620081009:
1127 The ABI used by the PMC toolset has changed. Please keep
1128 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
1129 sync.
1130
113120081009:
1132 atapci kernel module now includes only generic PCI ATA
1133 driver. AHCI driver moved to ataahci kernel module.
1134 All vendor-specific code moved into separate kernel modules:
1135 ataacard, ataacerlabs, ataadaptec, ataamd, ataati, atacenatek,
1136 atacypress, atacyrix, atahighpoint, ataintel, ataite, atajmicron,
1137 atamarvell, atamicron, atanational, atanetcell, atanvidia,
1138 atapromise, ataserverworks, atasiliconimage, atasis, atavia
1139
114020080820:
1141 The TTY subsystem of the kernel has been replaced by a new
1142 implementation, which provides better scalability and an
1143 improved driver model. Most common drivers have been migrated to
1144 the new TTY subsystem, while others have not. The following
1145 drivers have not yet been ported to the new TTY layer:
1146
1147 PCI/ISA:
1148 cy, digi, rc, rp, sio
1149
1150 USB:
1151 ubser, ucycom
1152
1153 Line disciplines:
1154 ng_h4, ng_tty, ppp, sl, snp
1155
1156 Adding these drivers to your kernel configuration file shall
1157 cause compilation to fail.
1158
115920080818:
1160 ntpd has been upgraded to 4.2.4p5.
1161
116220080801:
1163 OpenSSH has been upgraded to 5.1p1.
1164
1165 For many years, FreeBSD's version of OpenSSH preferred DSA
1166 over RSA for host and user authentication keys. With this
1167 upgrade, we've switched to the vendor's default of RSA over
1168 DSA. This may cause upgraded clients to warn about unknown
1169 host keys even for previously known hosts. Users should
1170 follow the usual procedure for verifying host keys before
1171 accepting the RSA key.
1172
1173 This can be circumvented by setting the "HostKeyAlgorithms"
1174 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
1175 command line.
1176
1177 Please note that the sequence of keys offered for
1178 authentication has been changed as well. You may want to
1179 specify IdentityFile in a different order to revert this
1180 behavior.
1181
118220080713:
1183 The sio(4) driver has been removed from the i386 and amd64
1184 kernel configuration files. This means uart(4) is now the
1185 default serial port driver on those platforms as well.
1186
1187 To prevent collisions with the sio(4) driver, the uart(4) driver
1188 uses different names for its device nodes. This means the
1189 onboard serial port will now most likely be called "ttyu0"
1190 instead of "ttyd0". You may need to reconfigure applications to
1191 use the new device names.
1192
1193 When using the serial port as a boot console, be sure to update
1194 /boot/device.hints and /etc/ttys before booting the new kernel.
1195 If you forget to do so, you can still manually specify the hints
1196 at the loader prompt:
1197
1198 set hint.uart.0.at="isa"
1199 set hint.uart.0.port="0x3F8"
1200 set hint.uart.0.flags="0x10"
1201 set hint.uart.0.irq="4"
1202 boot -s
1203
120420080609:
1205 The gpt(8) utility has been removed. Use gpart(8) to partition
1206 disks instead.
1207
120820080603:
1209 The version that Linuxulator emulates was changed from 2.4.2
1210 to 2.6.16. If you experience any problems with Linux binaries
1211 please try to set sysctl compat.linux.osrelease to 2.4.2 and
1212 if it fixes the problem contact emulation mailing list.
1213
121420080525:
1215 ISDN4BSD (I4B) was removed from the src tree. You may need to
1216 update a your kernel configuration and remove relevant entries.
1217
121820080509:
1219 I have checked in code to support multiple routing tables.
1220 See the man pages setfib(1) and setfib(2).
1221 This is a hopefully backwards compatible version,
1222 but to make use of it you need to compile your kernel
1223 with options ROUTETABLES=2 (or more up to 16).
1224
122520080420:
1226 The 802.11 wireless support was redone to enable multi-bss
1227 operation on devices that are capable. The underlying device
1228 is no longer used directly but instead wlanX devices are
1229 cloned with ifconfig. This requires changes to rc.conf files.
1230 For example, change:
1231 ifconfig_ath0="WPA DHCP"
1232 to
1233 wlans_ath0=wlan0
1234 ifconfig_wlan0="WPA DHCP"
1235 see rc.conf(5) for more details. In addition, mergemaster of
1236 /etc/rc.d is highly recommended. Simultaneous update of userland
1237 and kernel wouldn't hurt either.
1238
1239 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
1240 modules were merged into the base wlan module. All references
1241 to these modules (e.g. in kernel config files) must be removed.
1242
124320080408:
1244 psm(4) has gained write(2) support in native operation level.
1245 Arbitrary commands can be written to /dev/psm%d and status can
1246 be read back from it. Therefore, an application is responsible
1247 for status validation and error recovery. It is a no-op in
1248 other operation levels.
1249
125020080312:
1251 Support for KSE threading has been removed from the kernel. To
1252 run legacy applications linked against KSE libmap.conf may
1253 be used. The following libmap.conf may be used to ensure
1254 compatibility with any prior release:
1255
1256 libpthread.so.1 libthr.so.1
1257 libpthread.so.2 libthr.so.2
1258 libkse.so.3 libthr.so.3
1259
126020080301:
1261 The layout of struct vmspace has changed. This affects libkvm
1262 and any executables that link against libkvm and use the
1263 kvm_getprocs() function. In particular, but not exclusively,
1264 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
1265 The effects are minimal, but it's advisable to upgrade world
1266 nonetheless.
1267
126820080229:
1269 The latest em driver no longer has support in it for the
1270 82575 adapter, this is now moved to the igb driver. The
1271 split was done to make new features that are incompatible
1272 with older hardware easier to do.
1273
127420080220:
1275 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
1276 likewise the kernel option is now GEOM_LINUX_LVM.
1277
127820080211:
1279 The default NFS mount mode has changed from UDP to TCP for
1280 increased reliability. If you rely on (insecurely) NFS
1281 mounting across a firewall you may need to update your
1282 firewall rules.
1283
128420080208:
1285 Belatedly note the addition of m_collapse for compacting
1286 mbuf chains.
1287
128820080126:
1289 The fts(3) structures have been changed to use adequate
1290 integer types for their members and so to be able to cope
1291 with huge file trees. The old fts(3) ABI is preserved
1292 through symbol versioning in libc, so third-party binaries
1293 using fts(3) should still work, although they will not take
1294 advantage of the extended types. At the same time, some
1295 third-party software might fail to build after this change
1296 due to unportable assumptions made in its source code about
1297 fts(3) structure members. Such software should be fixed
1298 by its vendor or, in the worst case, in the ports tree.
1299 FreeBSD_version 800015 marks this change for the unlikely
1300 case that a portable fix is impossible.
1301
130220080123:
1303 To upgrade to -current after this date, you must be running
1304 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
1305 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
1306
130720071128:
1308 The ADAPTIVE_GIANT kernel option has been retired because its
1309 functionality is the default now.
1310
131120071118:
1312 The AT keyboard emulation of sunkbd(4) has been turned on
1313 by default. In order to make the special symbols of the Sun
1314 keyboards driven by sunkbd(4) work under X these now have
1315 to be configured the same way as Sun USB keyboards driven
1316 by ukbd(4) (which also does AT keyboard emulation), f.e.:
1317
1318 Option "XkbLayout" "us"
1319 Option "XkbRules" "xorg"
1320 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
1321
132220071024:
1323 It has been decided that it is desirable to provide ABI
1324 backwards compatibility to the FreeBSD 4/5/6 versions of the
1325 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
1326 broken with the introduction of PCI domain support (see the
1327 20070930 entry). Unfortunately, this required the ABI of
1328 PCIOCGETCONF to be broken again in order to be able to
1329 provide backwards compatibility to the old version of that
1330 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
1331 again. As for prominent ports this affects neither pciutils
1332 nor xorg-server this time, the hal port needs to be rebuilt
1333 however.
1334
133520071020:
1336 The misnamed kthread_create() and friends have been renamed
1337 to kproc_create() etc. Many of the callers already
1338 used kproc_start()..
1339 I will return kthread_create() and friends in a while
1340 with implementations that actually create threads, not procs.
1341 Renaming corresponds with version 800002.
1342
134320071010:
1344 RELENG_7 branched.
1345
1346COMMON ITEMS:
1347
1348 General Notes
1349 -------------
1350 Avoid using make -j when upgrading. While generally safe, there are
1351 sometimes problems using -j to upgrade. If your upgrade fails with
1352 -j, please try again without -j. From time to time in the past there
1353 have been problems using -j with buildworld and/or installworld. This
1354 is especially true when upgrading between "distant" versions (eg one
1355 that cross a major release boundary or several minor releases, or when
1356 several months have passed on the -current branch).
1357
1358 Sometimes, obscure build problems are the result of environment
1359 poisoning. This can happen because the make utility reads its
1360 environment when searching for values for global variables. To run
1361 your build attempts in an "environmental clean room", prefix all make
1362 commands with 'env -i '. See the env(1) manual page for more details.
1363
1364 When upgrading from one major version to another it is generally best
1365 to upgrade to the latest code in the currently installed branch first,
1366 then do an upgrade to the new branch. This is the best-tested upgrade
1367 path, and has the highest probability of being successful. Please try
1368 this approach before reporting problems with a major version upgrade.
1369
1370 ZFS notes
1371 ---------
1372 When upgrading the boot ZFS pool to a new version, always follow
1373 these two steps:
1374
1375 1.) recompile and reinstall the ZFS boot loader and boot block
1376 (this is part of "make buildworld" and "make installworld")
1377
1378 2.) update the ZFS boot block on your boot drive
1379
1380 The following example updates the ZFS boot block on the first
1381 partition (freebsd-boot) of a GPT partitioned drive ad0:
1382 "gpart bootcode -p /boot/gptzfsboot -i 1 ad0"
1383
1384 Non-boot pools do not need these updates.
1385
1386 To build a kernel
1387 -----------------
1388 If you are updating from a prior version of FreeBSD (even one just
1389 a few days old), you should follow this procedure. It is the most
1390 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
1391
1392 make kernel-toolchain
1393 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1394 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1395
1396 To test a kernel once
1397 ---------------------
1398 If you just want to boot a kernel once (because you are not sure
1399 if it works, or if you want to boot a known bad kernel to provide
1400 debugging information) run
1401 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
1402 nextboot -k testkernel
1403
1404 To just build a kernel when you know that it won't mess you up
1405 --------------------------------------------------------------
1406 This assumes you are already running a CURRENT system. Replace
1407 ${arch} with the architecture of your machine (e.g. "i386",
1408 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
1409
1410 cd src/sys/${arch}/conf
1411 config KERNEL_NAME_HERE
1412 cd ../compile/KERNEL_NAME_HERE
1413 make depend
1414 make
1415 make install
1416
1417 If this fails, go to the "To build a kernel" section.
1418
1419 To rebuild everything and install it on the current system.
1420 -----------------------------------------------------------
1421 # Note: sometimes if you are running current you gotta do more than
1422 # is listed here if you are upgrading from a really old current.
1423
1424 <make sure you have good level 0 dumps>
1425 make buildworld
1426 make kernel KERNCONF=YOUR_KERNEL_HERE
1427 [1]
1428 <reboot in single user> [3]
1429 mergemaster -p [5]
1430 make installworld
1431 mergemaster -i [4]
1432 make delete-old [6]
1433 <reboot>
1434
1435
1436 To cross-install current onto a separate partition
1437 --------------------------------------------------
1438 # In this approach we use a separate partition to hold
1439 # current's root, 'usr', and 'var' directories. A partition
1440 # holding "/", "/usr" and "/var" should be about 2GB in
1441 # size.
1442
1443 <make sure you have good level 0 dumps>
1444 <boot into -stable>
1445 make buildworld
1446 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1447 <maybe newfs current's root partition>
1448 <mount current's root partition on directory ${CURRENT_ROOT}>
1449 make installworld DESTDIR=${CURRENT_ROOT}
1450 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1451 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1452 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1453 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1454 <reboot into current>
1455 <do a "native" rebuild/install as described in the previous section>
1456 <maybe install compatibility libraries from ports/misc/compat*>
1457 <reboot>
1458
1459
1460 To upgrade in-place from 8.x-stable to current
1461 ----------------------------------------------
1462 <make sure you have good level 0 dumps>
1463 make buildworld [9]
1464 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1465 [1]
1466 <reboot in single user> [3]
1467 mergemaster -p [5]
1468 make installworld
1469 mergemaster -i [4]
1470 make delete-old [6]
1471 <reboot>
1472
1473 Make sure that you've read the UPDATING file to understand the
1474 tweaks to various things you need. At this point in the life
1475 cycle of current, things change often and you are on your own
1476 to cope. The defaults can also change, so please read ALL of
1477 the UPDATING entries.
1478
1479 Also, if you are tracking -current, you must be subscribed to
1480 freebsd-current@freebsd.org. Make sure that before you update
1481 your sources that you have read and understood all the recent
1482 messages there. If in doubt, please track -stable which has
1483 much fewer pitfalls.
1484
1485 [1] If you have third party modules, such as vmware, you
1486 should disable them at this point so they don't crash your
1487 system on reboot.
1488
1489 [3] From the bootblocks, boot -s, and then do
1490 fsck -p
1491 mount -u /
1492 mount -a
1493 cd src
1494 adjkerntz -i # if CMOS is wall time
1495 Also, when doing a major release upgrade, it is required that
1496 you boot into single user mode to do the installworld.
1497
1498 [4] Note: This step is non-optional. Failure to do this step
1499 can result in a significant reduction in the functionality of the
1500 system. Attempting to do it by hand is not recommended and those
1501 that pursue this avenue should read this file carefully, as well
1502 as the archives of freebsd-current and freebsd-hackers mailing lists
1503 for potential gotchas. The -U option is also useful to consider.
1504 See mergemaster(8) for more information.
1505
1506 [5] Usually this step is a noop. However, from time to time
1507 you may need to do this if you get unknown user in the following
1508 step. It never hurts to do it all the time. You may need to
1509 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1510 install) after the buildworld before this step if you last updated
1511 from current before 20020224 or from -stable before 20020408.
1512
1513 [6] This only deletes old files and directories. Old libraries
1514 can be deleted by "make delete-old-libs", but you have to make
1515 sure that no program is using those libraries anymore.
1516
1517 [8] In order to have a kernel that can run the 4.x binaries needed to
1518 do an installworld, you must include the COMPAT_FREEBSD4 option in
1519 your kernel. Failure to do so may leave you with a system that is
1520 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1521 required to run the 5.x binaries on more recent kernels. And so on
1522 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1523
1524 Make sure that you merge any new devices from GENERIC since the
1525 last time you updated your kernel config file.
1526
1527 [9] When checking out sources, you must include the -P flag to have
1528 cvs prune empty directories.
1529
1530 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1531 "?=" instead of the "=" assignment operator, so that buildworld can
1532 override the CPUTYPE if it needs to.
1533
1534 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1535 not on the command line, or in /etc/make.conf. buildworld will
1536 warn if it is improperly defined.
1537FORMAT:
1538
1539This file contains a list, in reverse chronological order, of major
1540breakages in tracking -current. It is not guaranteed to be a complete
1541list of such breakages, and only contains entries since October 10, 2007.
1542If you need to see UPDATING entries from before that date, you will need
1543to fetch an UPDATING file from an older FreeBSD release.
1544
1545Copyright information:
1546
1547Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1548
1549Redistribution, publication, translation and use, with or without
1550modification, in full or in part, in any form or format of this
1551document are permitted without further permission from the author.
1552
1553THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1554IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1555WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1556DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1557INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1558(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1559SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1560HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1561STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1562IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1563POSSIBILITY OF SUCH DAMAGE.
1564
1565Contact Warner Losh if you have any questions about your use of
1566this document.
1567
1568$FreeBSD: head/UPDATING 232317 2012-02-29 21:38:31Z trociny $