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