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 9.x IS SLOW:
13 FreeBSD 9.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
2520091025:
26 The iwn(4) driver has been updated to support the 5000 and 5150 series.
27 There's one kernel module for each firmware. Adding "device iwnfw"
28 to the kernel configuration file means including all three firmware
29 images inside the kernel. If you want to include just the one for
30 your wireless card, use the the devices iwn4965fw, iwn5000fw or
31 iwn5150fw.
32
3320090926:
34 The rc.d/network_ipv6, IPv6 configuration script has been integrated
35 into rc.d/netif. The changes are the following:
36
37 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
38 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
39 Note that both variables need the "inet6" keyword at the head.
40
41 Do not set $ipv6_network_interfaces manually if you do not
42 understand what you are doing. It is not needed in most cases.
43
44 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
45 they are obsolete.
46
47 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
48 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
49
50 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
51 all configured interfaces have "inet6 accept_rtadv" in the
52 $ifconfig_IF_ipv6. These are for backward compatibility.
53
54 3. A new variable $ipv6_prefer has been added. If NO, IPv6
55 functionality of interfaces with no corresponding
56 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
57 and the default address selection policy of ip6addrctl(8)
58 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
59 Note that if you want to configure IPv6 functionality on the
60 disabled interfaces after boot, first you need to clear the flag by
61 using ifconfig(8) like:
62
63 ifconfig em0 inet6 -ifdisabled
64
65 If YES, the default address selection policy is set as
66 IPv6-preferred.
67
68 The default value of $ipv6_prefer is NO.
69
70 4. If your system need to receive Router Advertisement messages,
71 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
72 scripts automatically invoke rtsol(8) when the interface becomes
73 UP. The Router Advertisement messages are used for SLAAC
74 (State-Less Address AutoConfiguration).
75
7620090922:
77 802.11s D3.03 support was committed. This is incompatible with the
78 previous code, which was based on D3.0.
79
8020090912:
81 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
82 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
83 control whether accepting Router Advertisement messages or not.
84 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
85 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
86 The ifconfig(8) utility now supports these flags.
87
8820090910:
89 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
90 mount(8) and -a option for df(1) to see them.
91
9220090825:
93 The old tunable hw.bus.devctl_disable has been superseded by
94 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
95 replaced by hw.bus.devctl_queue=0. The default for this new tunable
96 is 1000.
97
9820090813:
99 Remove the option STOP_NMI. The default action is now to use NMI only
100 for KDB via the newly introduced function stop_cpus_hard() and
101 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
102
10320090803:
104 The stable/8 branch created in subversion. This corresponds to the
105 RELENG_8 branch in CVS.
106
10720090719:
108 Bump the shared library version numbers for all libraries that do not
109 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
110 __FreeBSD_version to 800105.
111
11220090714:
113 Due to changes in the implementation of virtual network stack support,
114 all network-related kernel modules must be recompiled. As this change
115 breaks the ABI, bump __FreeBSD_version to 800104.
116
11720090713:
118 The TOE interface to the TCP syncache has been modified to remove
119 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
120 The cxgb driver is the only TOE consumer affected by this change, and
121 needs to be recompiled along with the kernel. As this change breaks
122 the ABI, bump __FreeBSD_version to 800103.
123
12420090712:
125 Padding has been added to struct tcpcb, sackhint and tcpstat in
126 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
127 maintainig the ABI. However, this change breaks the ABI, so bump
128 __FreeBSD_version to 800102. User space tools that rely on the size of
129 any of these structs (e.g. sockstat) need to be recompiled.
130
13120090630:
132 The NFS_LEGACYRPC option has been removed along with the old kernel
133 RPC implementation that this option selected. Kernel configurations
134 may need to be adjusted.
135
13620090629:
137 The network interface device nodes at /dev/net/<interface> have been
138 removed. All ioctl operations can be performed the normal way using
139 routing sockets. The kqueue functionality can generally be replaced
140 with routing sockets.
141
14220090628:
143 The documentation from the FreeBSD Documentation Project (Handbook,
144 FAQ, etc.) is now installed via packages by sysinstall(8) and under
145 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
146
14720090624:
148 The ABI of various structures related to the SYSV IPC API have been
149 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
150 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
151 800100.
152
15320090622:
154 Layout of struct vnet has changed as routing related variables were
155 moved to their own Vimage module. Modules need to be recompiled. Bump
156 __FreeBSD_version to 800099.
157
15820090619:
159 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
160 respectively. As long as no more than 16 groups per process are used,
161 no changes should be visible. When more than 16 groups are used, old
162 binaries may fail if they call getgroups() or getgrouplist() with
163 statically sized storage. Recompiling will work around this, but
164 applications should be modified to use dynamically allocated storage
165 for group arrays as POSIX.1-2008 does not cap an implementation's
166 number of supported groups at NGROUPS_MAX+1 as previous versions did.
167
168 NFS and portalfs mounts may also be affected as the list of groups is
169 truncated to 16. Users of NFS who use more than 16 groups, should
170 take care that negative group permissions are not used on the exported
171 file systems as they will not be reliable unless a GSSAPI based
172 authentication method is used.
173
17420090616:
175 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
176 option compiles in the support for adaptive spinning for lockmgrs
177 which want to enable it. The lockinit() function now accepts the flag
178 LK_ADAPTIVE in order to make the lock object subject to adaptive
179 spinning when both held in write and read mode.
180
18120090613:
182 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
183 changed. User applications that use this ioctl need to be rebuilt.
184
18520090611:
186 The layout of struct thread has changed. Kernel and modules need to
187 be rebuilt.
188
18920090608:
190 The layout of structs ifnet, domain, protosw and vnet_net has changed.
191 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
192
19320090602:
194 window(1) has been removed from the base system. It can now be
195 installed from ports. The port is called misc/window.
196
19720090601:
198 The way we are storing and accessing `routing table' entries has
199 changed. Programs reading the FIB, like netstat, need to be
200 re-compiled.
201
20220090601:
203 A new netisr implementation has been added for FreeBSD 8. Network
204 file system modules, such as igmp, ipdivert, and others, should be
205 rebuilt.
206 Bump __FreeBSD_version to 800096.
207
20820090530:
209 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
210 more valid.
211
21220090530:
213 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
214 Bump __FreeBSD_version to 800094.
215
21620090529:
217 Add mnt_xflag field to 'struct mount'. File system modules need to be
218 rebuilt.
219 Bump __FreeBSD_version to 800093.
220
22120090528:
222 The compiling option ADAPTIVE_SX has been retired while it has been
223 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
224 The KPI for sx_init_flags() changes as accepting flags:
225 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
226 been introduced in order to handle the reversed logic.
227 Bump __FreeBSD_version to 800092.
228
22920090527:
230 Add support for hierarchical jails. Remove global securelevel.
231 Bump __FreeBSD_version to 800091.
232
23320090523:
234 The layout of struct vnet_net has changed, therefore modules
235 need to be rebuilt.
236 Bump __FreeBSD_version to 800090.
237
23820090523:
239 The newly imported zic(8) produces a new format in the output. Please
240 run tzsetup(8) to install the newly created data to /etc/localtime.
241
24220090520:
243 The sysctl tree for the usb stack has renamed from hw.usb2.* to
244 hw.usb.* and is now consistent again with previous releases.
245
24620090520:
247 802.11 monitor mode support was revised and driver api's were changed.
248 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
249 of DLT_IEEE802_11. No user-visible data structures were changed but
250 applications that use DLT_IEEE802_11 may require changes.
251 Bump __FreeBSD_version to 800088.
252
25320090430:
254 The layout of the following structs has changed: sysctl_oid,
255 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
256 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
257 panics may be experienced. World rebuild is required for
258 correctly checking networking state from userland.
259 Bump __FreeBSD_version to 800085.
260
26120090429:
262 MLDv2 and Source-Specific Multicast (SSM) have been merged
263 to the IPv6 stack. VIMAGE hooks are in but not yet used.
264 The implementation of SSM within FreeBSD's IPv6 stack closely
265 follows the IPv4 implementation.
266
267 For kernel developers:
268
269 * The most important changes are that the ip6_output() and
270 ip6_input() paths no longer take the IN6_MULTI_LOCK,
271 and this lock has been downgraded to a non-recursive mutex.
272
273 * As with the changes to the IPv4 stack to support SSM, filtering
274 of inbound multicast traffic must now be performed by transport
275 protocols within the IPv6 stack. This does not apply to TCP and
276 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
277
278 * The KPIs used by IPv6 multicast are similar to those used by
279 the IPv4 stack, with the following differences:
280 * im6o_mc_filter() is analogous to imo_multicast_filter().
281 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
282 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
283 * IN6_LOOKUP_MULTI() has been deprecated and removed.
284 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
285 for MLDv1 have an additional 'timer' argument which is used to
286 jitter the initial membership report for the solicited-node
287 multicast membership on-link.
288 * This is not strictly needed for MLDv2, which already jitters
289 its report transmissions. However, the 'timer' argument is
290 preserved in case MLDv1 is active on the interface.
291
292 * The KAME linked-list based IPv6 membership implementation has
293 been refactored to use a vector similar to that used by the IPv4
294 stack.
295 Code which maintains a list of its own multicast memberships
296 internally, e.g. carp, has been updated to reflect the new
297 semantics.
298
299 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
300 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
301 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
302 implementation constraint which needs to be addressed in HEAD.
303
304 For application developers:
305
306 * The changes are broadly similar to those made for the IPv4
307 stack.
308
309 * The use of IPv4 and IPv6 multicast socket options on the same
310 socket, using mapped addresses, HAS NOT been tested or supported.
311
312 * There are a number of issues with the implementation of various
313 IPv6 multicast APIs which need to be resolved in the API surface
314 before the implementation is fully compatible with KAME userland
315 use, and these are mostly to do with interface index treatment.
316
317 * The literature available discusses the use of either the delta / ASM
318 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
319 using setsourcefilter(3)/getsourcefilter(3). For more information
320 please refer to RFC 3768, 'Socket Interface Extensions for
321 Multicast Source Filters'.
322
323 * Applications which use the published RFC 3678 APIs should be fine.
324
325 For systems administrators:
326
327 * The mtest(8) utility has been refactored to support IPv6, in
328 addition to IPv4. Interface addresses are no longer accepted
329 as arguments, their names must be used instead. The utility
330 will map the interface name to its first IPv4 address as
331 returned by getifaddrs(3).
332
333 * The ifmcstat(8) utility has also been updated to print the MLDv2
334 endpoint state and source filter lists via sysctl(3).
335
336 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
337 loopback of IPv6 multicast datagrams by default; it defaults to 1
338 to preserve the existing behaviour. Disabling multicast loopback is
339 recommended for optimal system performance.
340
341 * The IPv6 MROUTING code has been changed to examine this sysctl
342 instead of attempting to perform a group lookup before looping
343 back forwarded datagrams.
344
345 Bump __FreeBSD_version to 800084.
346
34720090422:
348 Implement low-level Bluetooth HCI API.
349 Bump __FreeBSD_version to 800083.
350
35120090419:
352 The layout of struct malloc_type, used by modules to register new
353 memory allocation types, has changed. Most modules will need to
354 be rebuilt or panics may be experienced.
355 Bump __FreeBSD_version to 800081.
356
35720090415:
358 Anticipate overflowing inp_flags - add inp_flags2.
359 This changes most offsets in inpcb, so checking v4 connection
360 state will require a world rebuild.
361 Bump __FreeBSD_version to 800080.
362
36320090415:
364 Add an llentry to struct route and struct route_in6. Modules
365 embedding a struct route will need to be recompiled.
366 Bump __FreeBSD_version to 800079.
367
36820090414:
369 The size of rt_metrics_lite and by extension rtentry has changed.
370 Networking administration apps will need to be recompiled.
371 The route command now supports show as an alias for get, weighting
372 of routes, sticky and nostick flags to alter the behavior of stateful
373 load balancing.
374 Bump __FreeBSD_version to 800078.
375
37620090408:
377 Do not use Giant for kbdmux(4) locking. This is wrong and
378 apparently causing more problems than it solves. This will
379 re-open the issue where interrupt handlers may race with
380 kbdmux(4) in polling mode. Typical symptoms include (but
381 not limited to) duplicated and/or missing characters when
382 low level console functions (such as gets) are used while
383 interrupts are enabled (for example geli password prompt,
384 mountroot prompt etc.). Disabling kbdmux(4) may help.
385
38620090407:
387 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
388 kernel modules referencing any of the above need to be recompiled.
389 Bump __FreeBSD_version to 800075.
390
39120090320:
392 GEOM_PART has become the default partition slicer for storage devices,
393 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
394 introduces some changes:
395
396 MSDOS/EBR: the devices created from MSDOS extended partition entries
397 (EBR) can be named differently than with GEOM_MBR and are now symlinks
398 to devices with offset-based names. fstabs may need to be modified.
399
400 BSD: the "geometry does not match label" warning is harmless in most
401 cases but it points to problems in file system misalignment with
402 disk geometry. The "c" partition is now implicit, covers the whole
403 top-level drive and cannot be (mis)used by users.
404
405 General: Kernel dumps are now not allowed to be written to devices
406 whose partition types indicate they are meant to be used for file
407 systems (or, in case of MSDOS partitions, as something else than
408 the "386BSD" type).
409
410 Most of these changes date approximately from 200812.
411
41220090319:
413 The uscanner(4) driver has been removed from the kernel. This follows
414 Linux removing theirs in 2.6 and making libusb the default interface
415 (supported by sane).
416
41720090319:
418 The multicast forwarding code has been cleaned up. netstat(1)
419 only relies on KVM now for printing bandwidth upcall meters.
420 The IPv4 and IPv6 modules are split into ip_mroute_mod and
421 ip6_mroute_mod respectively. The config(5) options for statically
422 compiling this code remain the same, i.e. 'options MROUTING'.
423
42420090315:
425 Support for the IFF_NEEDSGIANT network interface flag has been
426 removed, which means that non-MPSAFE network device drivers are no
427 longer supported. In particular, if_ar, if_sr, and network device
428 drivers from the old (legacy) USB stack can no longer be built or
429 used.
430
43120090313:
432 POSIX.1 Native Language Support (NLS) has been enabled in libc and
433 a bunch of new language catalog files have also been added.
434 This means that some common libc messages are now localized and
435 they depend on the LC_MESSAGES environmental variable.
436
43720090313:
438 The k8temp(4) driver has been renamed to amdtemp(4) since
439 support for K10 and K11 CPU families was added.
440
44120090309:
442 IGMPv3 and Source-Specific Multicast (SSM) have been merged
443 to the IPv4 stack. VIMAGE hooks are in but not yet used.
444
445 For kernel developers, the most important changes are that the
446 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
447 and this lock has been downgraded to a non-recursive mutex.
448
449 Transport protocols (UDP, Raw IP) are now responsible for filtering
450 inbound multicast traffic according to group membership and source
451 filters. The imo_multicast_filter() KPI exists for this purpose.
452 Transports which do not use multicast (SCTP, TCP) already reject
453 multicast by default. Forwarding and receive performance may improve
454 as a mutex acquisition is no longer needed in the ip_input()
455 low-level input path. in_addmulti() and in_delmulti() are shimmed
456 to new KPIs which exist to support SSM in-kernel.
457
458 For application developers, it is recommended that loopback of
459 multicast datagrams be disabled for best performance, as this
460 will still cause the lock to be taken for each looped-back
461 datagram transmission. The net.inet.ip.mcast.loop sysctl may
462 be tuned to 0 to disable loopback by default; it defaults to 1
463 to preserve the existing behaviour.
464
465 For systems administrators, to obtain best performance with
466 multicast reception and multiple groups, it is always recommended
467 that a card with a suitably precise hash filter is used. Hash
468 collisions will still result in the lock being taken within the
469 transport protocol input path to check group membership.
470
471 If deploying FreeBSD in an environment with IGMP snooping switches,
472 it is recommended that the net.inet.igmp.sendlocal sysctl remain
473 enabled; this forces 224.0.0.0/24 group membership to be announced
474 via IGMP.
475
476 The size of 'struct igmpstat' has changed; netstat needs to be
477 recompiled to reflect this.
478 Bump __FreeBSD_version to 800070.
479
48020090309:
481 libusb20.so.1 is now installed as libusb.so.1 and the ports system
482 updated to use it. This requires a buildworld/installworld in order to
483 update the library and dependencies (usbconfig, etc). Its advisable to
484 rebuild all ports which uses libusb. More specific directions are given
485 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
486 libusb are no longer required and can be removed.
487
48820090302:
489 A workaround is committed to allow the creation of System V shared
490 memory segment of size > 2 GB on the 64-bit architectures.
491 Due to a limitation of the existing ABI, the shm_segsz member
492 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
493 wrong for large segments. Note that limits must be explicitly
494 raised to allow such segments to be created.
495
49620090301:
497 The layout of struct ifnet has changed, requiring a rebuild of all
498 network device driver modules.
499
50020090227:
501 The /dev handling for the new USB stack has changed, a
502 buildworld/installworld is required for libusb20.
503
50420090223:
505 The new USB2 stack has now been permanently moved in and all kernel and
506 module names reverted to their previous values (eg, usb, ehci, ohci,
507 ums, ...). The old usb stack can be compiled in by prefixing the name
508 with the letter 'o', the old usb modules have been removed.
509 Updating entry 20090216 for xorg and 20090215 for libmap may still
510 apply.
511
51220090217:
513 The rc.conf(5) option if_up_delay has been renamed to
514 defaultroute_delay to better reflect its purpose. If you have
515 customized this setting in /etc/rc.conf you need to update it to
516 use the new name.
517
51820090216:
519 xorg 7.4 wants to configure its input devices via hald which does not
520 yet work with USB2. If the keyboard/mouse does not work in xorg then
521 add
522 Option "AllowEmptyInput" "off"
523 to your ServerLayout section. This will cause X to use the configured
524 kbd and mouse sections from your xorg.conf.
525
52620090215:
527 The GENERIC kernels for all architectures now default to the new USB2
528 stack. No kernel config options or code have been removed so if a
529 problem arises please report it and optionally revert to the old USB
530 stack. If you are loading USB kernel modules or have a custom kernel
531 that includes GENERIC then ensure that usb names are also changed over,
532 eg uftdi -> usb2_serial_ftdi.
533
534 Older programs linked against the ports libusb 0.1 need to be
535 redirected to the new stack's libusb20. /etc/libmap.conf can
536 be used for this:
537 # Map old usb library to new one for usb2 stack
538 libusb-0.1.so.8 libusb20.so.1
539
54020090203:
541 The ichsmb(4) driver has been changed to require SMBus slave
542 addresses be left-justified (xxxxxxx0b) rather than right-justified.
543 All of the other SMBus controller drivers require left-justified
544 slave addresses, so this change makes all the drivers provide the
545 same interface.
546
54720090201:
548 INET6 statistics (struct ip6stat) was updated.
549 netstat(1) needs to be recompiled.
550
55120090119:
552 NTFS has been removed from GENERIC kernel on amd64 to match
553 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
554 will load ntfs.ko module automatically when NTFS support is
555 actually needed, unless ntfs.ko is not installed or security
556 level prohibits loading kernel modules. If either is the case,
557 "options NTFS" has to be added into kernel config.
558
55920090115:
560 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
561 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
562 800061. User space tools that rely on the size of struct tcpcb in
563 tcp_var.h (e.g. sockstat) need to be recompiled.
564
56520081225:
566 ng_tty(4) module updated to match the new TTY subsystem.
567 Due to API change, user-level applications must be updated.
568 New API support added to mpd5 CVS and expected to be present
569 in next mpd5.3 release.
570
57120081219:
572 With __FreeBSD_version 800060 the makefs tool is part of
573 the base system (it was a port).
574
57520081216:
576 The afdata and ifnet locks have been changed from mutexes to
577 rwlocks, network modules will need to be re-compiled.
578
57920081214:
580 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
581 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
582 The new code reduced struct rtentry{} by 16 bytes on 32-bit
583 architecture and 40 bytes on 64-bit architecture. The userland
584 applications "arp" and "ndp" have been updated accordingly.
585 The output from "netstat -r" shows only routing entries and
586 none of the L2 information.
587
58820081130:
589 __FreeBSD_version 800057 marks the switchover from the
590 binary ath hal to source code. Users must add the line:
591
592 options AH_SUPPORT_AR5416
593
594 to their kernel config files when specifying:
595
596 device ath_hal
597
598 The ath_hal module no longer exists; the code is now compiled
599 together with the driver in the ath module. It is now
600 possible to tailor chip support (i.e. reduce the set of chips
601 and thereby the code size); consult ath_hal(4) for details.
602
60320081121:
604 __FreeBSD_version 800054 adds memory barriers to
605 <machine/atomic.h>, new interfaces to ifnet to facilitate
606 multiple hardware transmit queues for cards that support
607 them, and a lock-less ring-buffer implementation to
608 enable drivers to more efficiently manage queueing of
609 packets.
610
61120081117:
612 A new version of ZFS (version 13) has been merged to -HEAD.
613 This version has zpool attribute "listsnapshots" off by
614 default, which means "zfs list" does not show snapshots,
615 and is the same as Solaris behavior.
616
61720081028:
618 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
619
62020081009:
621 The uhci, ohci, ehci and slhci USB Host controller drivers have
622 been put into separate modules. If you load the usb module
623 separately through loader.conf you will need to load the
624 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
625 controller add the following to loader.conf:
626
627 uhci_load="YES"
628 ehci_load="YES"
629
63020081009:
631 The ABI used by the PMC toolset has changed. Please keep
632 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
633 sync.
634
| 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 9.x IS SLOW:
13 FreeBSD 9.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
2520091025:
26 The iwn(4) driver has been updated to support the 5000 and 5150 series.
27 There's one kernel module for each firmware. Adding "device iwnfw"
28 to the kernel configuration file means including all three firmware
29 images inside the kernel. If you want to include just the one for
30 your wireless card, use the the devices iwn4965fw, iwn5000fw or
31 iwn5150fw.
32
3320090926:
34 The rc.d/network_ipv6, IPv6 configuration script has been integrated
35 into rc.d/netif. The changes are the following:
36
37 1. To use IPv6, simply define $ifconfig_IF_ipv6 like $ifconfig_IF
38 for IPv4. For aliases, $ifconfig_IF_aliasN should be used.
39 Note that both variables need the "inet6" keyword at the head.
40
41 Do not set $ipv6_network_interfaces manually if you do not
42 understand what you are doing. It is not needed in most cases.
43
44 $ipv6_ifconfig_IF and $ipv6_ifconfig_IF_aliasN still work, but
45 they are obsolete.
46
47 2. $ipv6_enable is obsolete. Use $ipv6_prefer and
48 "inet6 accept_rtadv" keyword in ifconfig(8) instead.
49
50 If you define $ipv6_enable=YES, it means $ipv6_prefer=YES and
51 all configured interfaces have "inet6 accept_rtadv" in the
52 $ifconfig_IF_ipv6. These are for backward compatibility.
53
54 3. A new variable $ipv6_prefer has been added. If NO, IPv6
55 functionality of interfaces with no corresponding
56 $ifconfig_IF_ipv6 is disabled by using "inet6 ifdisabled" flag,
57 and the default address selection policy of ip6addrctl(8)
58 is the IPv4-preferred one (see rc.d/ip6addrctl for more details).
59 Note that if you want to configure IPv6 functionality on the
60 disabled interfaces after boot, first you need to clear the flag by
61 using ifconfig(8) like:
62
63 ifconfig em0 inet6 -ifdisabled
64
65 If YES, the default address selection policy is set as
66 IPv6-preferred.
67
68 The default value of $ipv6_prefer is NO.
69
70 4. If your system need to receive Router Advertisement messages,
71 define "inet6 accept_rtadv" in $ifconfig_IF_ipv6. The rc(8)
72 scripts automatically invoke rtsol(8) when the interface becomes
73 UP. The Router Advertisement messages are used for SLAAC
74 (State-Less Address AutoConfiguration).
75
7620090922:
77 802.11s D3.03 support was committed. This is incompatible with the
78 previous code, which was based on D3.0.
79
8020090912:
81 A sysctl variable net.inet6.ip6.accept_rtadv now sets the default value
82 of a per-interface flag ND6_IFF_ACCEPT_RTADV, not a global knob to
83 control whether accepting Router Advertisement messages or not.
84 Also, a per-interface flag ND6_IFF_AUTO_LINKLOCAL has been added and
85 a sysctl variable net.inet6.ip6.auto_linklocal is its default value.
86 The ifconfig(8) utility now supports these flags.
87
8820090910:
89 ZFS snapshots are now mounted with MNT_IGNORE flag. Use -v option for
90 mount(8) and -a option for df(1) to see them.
91
9220090825:
93 The old tunable hw.bus.devctl_disable has been superseded by
94 hw.bus.devctl_queue. hw.bus.devctl_disable=1 in loader.conf should be
95 replaced by hw.bus.devctl_queue=0. The default for this new tunable
96 is 1000.
97
9820090813:
99 Remove the option STOP_NMI. The default action is now to use NMI only
100 for KDB via the newly introduced function stop_cpus_hard() and
101 maintain stop_cpus() to just use a normal IPI_STOP on ia32 and amd64.
102
10320090803:
104 The stable/8 branch created in subversion. This corresponds to the
105 RELENG_8 branch in CVS.
106
10720090719:
108 Bump the shared library version numbers for all libraries that do not
109 use symbol versioning as part of the 8.0-RELEASE cycle. Bump
110 __FreeBSD_version to 800105.
111
11220090714:
113 Due to changes in the implementation of virtual network stack support,
114 all network-related kernel modules must be recompiled. As this change
115 breaks the ABI, bump __FreeBSD_version to 800104.
116
11720090713:
118 The TOE interface to the TCP syncache has been modified to remove
119 struct tcpopt (<netinet/tcp_var.h>) from the ABI of the network stack.
120 The cxgb driver is the only TOE consumer affected by this change, and
121 needs to be recompiled along with the kernel. As this change breaks
122 the ABI, bump __FreeBSD_version to 800103.
123
12420090712:
125 Padding has been added to struct tcpcb, sackhint and tcpstat in
126 <netinet/tcp_var.h> to facilitate future MFCs and bug fixes whilst
127 maintainig the ABI. However, this change breaks the ABI, so bump
128 __FreeBSD_version to 800102. User space tools that rely on the size of
129 any of these structs (e.g. sockstat) need to be recompiled.
130
13120090630:
132 The NFS_LEGACYRPC option has been removed along with the old kernel
133 RPC implementation that this option selected. Kernel configurations
134 may need to be adjusted.
135
13620090629:
137 The network interface device nodes at /dev/net/<interface> have been
138 removed. All ioctl operations can be performed the normal way using
139 routing sockets. The kqueue functionality can generally be replaced
140 with routing sockets.
141
14220090628:
143 The documentation from the FreeBSD Documentation Project (Handbook,
144 FAQ, etc.) is now installed via packages by sysinstall(8) and under
145 the /usr/local/share/doc/freebsd directory instead of /usr/share/doc.
146
14720090624:
148 The ABI of various structures related to the SYSV IPC API have been
149 changed. As a result, the COMPAT_FREEBSD[456] and COMPAT_43 kernel
150 options now all require COMPAT_FREEBSD7. Bump __FreeBSD_version to
151 800100.
152
15320090622:
154 Layout of struct vnet has changed as routing related variables were
155 moved to their own Vimage module. Modules need to be recompiled. Bump
156 __FreeBSD_version to 800099.
157
15820090619:
159 NGROUPS_MAX and NGROUPS have been increased from 16 to 1023 and 1024
160 respectively. As long as no more than 16 groups per process are used,
161 no changes should be visible. When more than 16 groups are used, old
162 binaries may fail if they call getgroups() or getgrouplist() with
163 statically sized storage. Recompiling will work around this, but
164 applications should be modified to use dynamically allocated storage
165 for group arrays as POSIX.1-2008 does not cap an implementation's
166 number of supported groups at NGROUPS_MAX+1 as previous versions did.
167
168 NFS and portalfs mounts may also be affected as the list of groups is
169 truncated to 16. Users of NFS who use more than 16 groups, should
170 take care that negative group permissions are not used on the exported
171 file systems as they will not be reliable unless a GSSAPI based
172 authentication method is used.
173
17420090616:
175 The compiling option ADAPTIVE_LOCKMGRS has been introduced. This
176 option compiles in the support for adaptive spinning for lockmgrs
177 which want to enable it. The lockinit() function now accepts the flag
178 LK_ADAPTIVE in order to make the lock object subject to adaptive
179 spinning when both held in write and read mode.
180
18120090613:
182 The layout of the structure returned by IEEE80211_IOC_STA_INFO has
183 changed. User applications that use this ioctl need to be rebuilt.
184
18520090611:
186 The layout of struct thread has changed. Kernel and modules need to
187 be rebuilt.
188
18920090608:
190 The layout of structs ifnet, domain, protosw and vnet_net has changed.
191 Kernel modules need to be rebuilt. Bump __FreeBSD_version to 800097.
192
19320090602:
194 window(1) has been removed from the base system. It can now be
195 installed from ports. The port is called misc/window.
196
19720090601:
198 The way we are storing and accessing `routing table' entries has
199 changed. Programs reading the FIB, like netstat, need to be
200 re-compiled.
201
20220090601:
203 A new netisr implementation has been added for FreeBSD 8. Network
204 file system modules, such as igmp, ipdivert, and others, should be
205 rebuilt.
206 Bump __FreeBSD_version to 800096.
207
20820090530:
209 Remove the tunable/sysctl debug.mpsafevfs as its initial purpose is no
210 more valid.
211
21220090530:
213 Add VOP_ACCESSX(9). File system modules need to be rebuilt.
214 Bump __FreeBSD_version to 800094.
215
21620090529:
217 Add mnt_xflag field to 'struct mount'. File system modules need to be
218 rebuilt.
219 Bump __FreeBSD_version to 800093.
220
22120090528:
222 The compiling option ADAPTIVE_SX has been retired while it has been
223 introduced the option NO_ADAPTIVE_SX which handles the reversed logic.
224 The KPI for sx_init_flags() changes as accepting flags:
225 SX_ADAPTIVESPIN flag has been retired while the SX_NOADAPTIVE flag has
226 been introduced in order to handle the reversed logic.
227 Bump __FreeBSD_version to 800092.
228
22920090527:
230 Add support for hierarchical jails. Remove global securelevel.
231 Bump __FreeBSD_version to 800091.
232
23320090523:
234 The layout of struct vnet_net has changed, therefore modules
235 need to be rebuilt.
236 Bump __FreeBSD_version to 800090.
237
23820090523:
239 The newly imported zic(8) produces a new format in the output. Please
240 run tzsetup(8) to install the newly created data to /etc/localtime.
241
24220090520:
243 The sysctl tree for the usb stack has renamed from hw.usb2.* to
244 hw.usb.* and is now consistent again with previous releases.
245
24620090520:
247 802.11 monitor mode support was revised and driver api's were changed.
248 Drivers dependent on net80211 now support DLT_IEEE802_11_RADIO instead
249 of DLT_IEEE802_11. No user-visible data structures were changed but
250 applications that use DLT_IEEE802_11 may require changes.
251 Bump __FreeBSD_version to 800088.
252
25320090430:
254 The layout of the following structs has changed: sysctl_oid,
255 socket, ifnet, inpcbinfo, tcpcb, syncache_head, vnet_inet,
256 vnet_inet6 and vnet_ipfw. Most modules need to be rebuild or
257 panics may be experienced. World rebuild is required for
258 correctly checking networking state from userland.
259 Bump __FreeBSD_version to 800085.
260
26120090429:
262 MLDv2 and Source-Specific Multicast (SSM) have been merged
263 to the IPv6 stack. VIMAGE hooks are in but not yet used.
264 The implementation of SSM within FreeBSD's IPv6 stack closely
265 follows the IPv4 implementation.
266
267 For kernel developers:
268
269 * The most important changes are that the ip6_output() and
270 ip6_input() paths no longer take the IN6_MULTI_LOCK,
271 and this lock has been downgraded to a non-recursive mutex.
272
273 * As with the changes to the IPv4 stack to support SSM, filtering
274 of inbound multicast traffic must now be performed by transport
275 protocols within the IPv6 stack. This does not apply to TCP and
276 SCTP, however, it does apply to UDP in IPv6 and raw IPv6.
277
278 * The KPIs used by IPv6 multicast are similar to those used by
279 the IPv4 stack, with the following differences:
280 * im6o_mc_filter() is analogous to imo_multicast_filter().
281 * The legacy KAME entry points in6_joingroup and in6_leavegroup()
282 are shimmed to in6_mc_join() and in6_mc_leave() respectively.
283 * IN6_LOOKUP_MULTI() has been deprecated and removed.
284 * IPv6 relies on MLD for the DAD mechanism. KAME's internal KPIs
285 for MLDv1 have an additional 'timer' argument which is used to
286 jitter the initial membership report for the solicited-node
287 multicast membership on-link.
288 * This is not strictly needed for MLDv2, which already jitters
289 its report transmissions. However, the 'timer' argument is
290 preserved in case MLDv1 is active on the interface.
291
292 * The KAME linked-list based IPv6 membership implementation has
293 been refactored to use a vector similar to that used by the IPv4
294 stack.
295 Code which maintains a list of its own multicast memberships
296 internally, e.g. carp, has been updated to reflect the new
297 semantics.
298
299 * There is a known Lock Order Reversal (LOR) due to in6_setscope()
300 acquiring the IF_AFDATA_LOCK and being called within ip6_output().
301 Whilst MLDv2 tries to avoid this otherwise benign LOR, it is an
302 implementation constraint which needs to be addressed in HEAD.
303
304 For application developers:
305
306 * The changes are broadly similar to those made for the IPv4
307 stack.
308
309 * The use of IPv4 and IPv6 multicast socket options on the same
310 socket, using mapped addresses, HAS NOT been tested or supported.
311
312 * There are a number of issues with the implementation of various
313 IPv6 multicast APIs which need to be resolved in the API surface
314 before the implementation is fully compatible with KAME userland
315 use, and these are mostly to do with interface index treatment.
316
317 * The literature available discusses the use of either the delta / ASM
318 API with setsockopt(2)/getsockopt(2), or the full-state / ASM API
319 using setsourcefilter(3)/getsourcefilter(3). For more information
320 please refer to RFC 3768, 'Socket Interface Extensions for
321 Multicast Source Filters'.
322
323 * Applications which use the published RFC 3678 APIs should be fine.
324
325 For systems administrators:
326
327 * The mtest(8) utility has been refactored to support IPv6, in
328 addition to IPv4. Interface addresses are no longer accepted
329 as arguments, their names must be used instead. The utility
330 will map the interface name to its first IPv4 address as
331 returned by getifaddrs(3).
332
333 * The ifmcstat(8) utility has also been updated to print the MLDv2
334 endpoint state and source filter lists via sysctl(3).
335
336 * The net.inet6.ip6.mcast.loop sysctl may be tuned to 0 to disable
337 loopback of IPv6 multicast datagrams by default; it defaults to 1
338 to preserve the existing behaviour. Disabling multicast loopback is
339 recommended for optimal system performance.
340
341 * The IPv6 MROUTING code has been changed to examine this sysctl
342 instead of attempting to perform a group lookup before looping
343 back forwarded datagrams.
344
345 Bump __FreeBSD_version to 800084.
346
34720090422:
348 Implement low-level Bluetooth HCI API.
349 Bump __FreeBSD_version to 800083.
350
35120090419:
352 The layout of struct malloc_type, used by modules to register new
353 memory allocation types, has changed. Most modules will need to
354 be rebuilt or panics may be experienced.
355 Bump __FreeBSD_version to 800081.
356
35720090415:
358 Anticipate overflowing inp_flags - add inp_flags2.
359 This changes most offsets in inpcb, so checking v4 connection
360 state will require a world rebuild.
361 Bump __FreeBSD_version to 800080.
362
36320090415:
364 Add an llentry to struct route and struct route_in6. Modules
365 embedding a struct route will need to be recompiled.
366 Bump __FreeBSD_version to 800079.
367
36820090414:
369 The size of rt_metrics_lite and by extension rtentry has changed.
370 Networking administration apps will need to be recompiled.
371 The route command now supports show as an alias for get, weighting
372 of routes, sticky and nostick flags to alter the behavior of stateful
373 load balancing.
374 Bump __FreeBSD_version to 800078.
375
37620090408:
377 Do not use Giant for kbdmux(4) locking. This is wrong and
378 apparently causing more problems than it solves. This will
379 re-open the issue where interrupt handlers may race with
380 kbdmux(4) in polling mode. Typical symptoms include (but
381 not limited to) duplicated and/or missing characters when
382 low level console functions (such as gets) are used while
383 interrupts are enabled (for example geli password prompt,
384 mountroot prompt etc.). Disabling kbdmux(4) may help.
385
38620090407:
387 The size of structs vnet_net, vnet_inet and vnet_ipfw has changed;
388 kernel modules referencing any of the above need to be recompiled.
389 Bump __FreeBSD_version to 800075.
390
39120090320:
392 GEOM_PART has become the default partition slicer for storage devices,
393 replacing GEOM_MBR, GEOM_BSD, GEOM_PC98 and GEOM_GPT slicers. It
394 introduces some changes:
395
396 MSDOS/EBR: the devices created from MSDOS extended partition entries
397 (EBR) can be named differently than with GEOM_MBR and are now symlinks
398 to devices with offset-based names. fstabs may need to be modified.
399
400 BSD: the "geometry does not match label" warning is harmless in most
401 cases but it points to problems in file system misalignment with
402 disk geometry. The "c" partition is now implicit, covers the whole
403 top-level drive and cannot be (mis)used by users.
404
405 General: Kernel dumps are now not allowed to be written to devices
406 whose partition types indicate they are meant to be used for file
407 systems (or, in case of MSDOS partitions, as something else than
408 the "386BSD" type).
409
410 Most of these changes date approximately from 200812.
411
41220090319:
413 The uscanner(4) driver has been removed from the kernel. This follows
414 Linux removing theirs in 2.6 and making libusb the default interface
415 (supported by sane).
416
41720090319:
418 The multicast forwarding code has been cleaned up. netstat(1)
419 only relies on KVM now for printing bandwidth upcall meters.
420 The IPv4 and IPv6 modules are split into ip_mroute_mod and
421 ip6_mroute_mod respectively. The config(5) options for statically
422 compiling this code remain the same, i.e. 'options MROUTING'.
423
42420090315:
425 Support for the IFF_NEEDSGIANT network interface flag has been
426 removed, which means that non-MPSAFE network device drivers are no
427 longer supported. In particular, if_ar, if_sr, and network device
428 drivers from the old (legacy) USB stack can no longer be built or
429 used.
430
43120090313:
432 POSIX.1 Native Language Support (NLS) has been enabled in libc and
433 a bunch of new language catalog files have also been added.
434 This means that some common libc messages are now localized and
435 they depend on the LC_MESSAGES environmental variable.
436
43720090313:
438 The k8temp(4) driver has been renamed to amdtemp(4) since
439 support for K10 and K11 CPU families was added.
440
44120090309:
442 IGMPv3 and Source-Specific Multicast (SSM) have been merged
443 to the IPv4 stack. VIMAGE hooks are in but not yet used.
444
445 For kernel developers, the most important changes are that the
446 ip_output() and ip_input() paths no longer take the IN_MULTI_LOCK(),
447 and this lock has been downgraded to a non-recursive mutex.
448
449 Transport protocols (UDP, Raw IP) are now responsible for filtering
450 inbound multicast traffic according to group membership and source
451 filters. The imo_multicast_filter() KPI exists for this purpose.
452 Transports which do not use multicast (SCTP, TCP) already reject
453 multicast by default. Forwarding and receive performance may improve
454 as a mutex acquisition is no longer needed in the ip_input()
455 low-level input path. in_addmulti() and in_delmulti() are shimmed
456 to new KPIs which exist to support SSM in-kernel.
457
458 For application developers, it is recommended that loopback of
459 multicast datagrams be disabled for best performance, as this
460 will still cause the lock to be taken for each looped-back
461 datagram transmission. The net.inet.ip.mcast.loop sysctl may
462 be tuned to 0 to disable loopback by default; it defaults to 1
463 to preserve the existing behaviour.
464
465 For systems administrators, to obtain best performance with
466 multicast reception and multiple groups, it is always recommended
467 that a card with a suitably precise hash filter is used. Hash
468 collisions will still result in the lock being taken within the
469 transport protocol input path to check group membership.
470
471 If deploying FreeBSD in an environment with IGMP snooping switches,
472 it is recommended that the net.inet.igmp.sendlocal sysctl remain
473 enabled; this forces 224.0.0.0/24 group membership to be announced
474 via IGMP.
475
476 The size of 'struct igmpstat' has changed; netstat needs to be
477 recompiled to reflect this.
478 Bump __FreeBSD_version to 800070.
479
48020090309:
481 libusb20.so.1 is now installed as libusb.so.1 and the ports system
482 updated to use it. This requires a buildworld/installworld in order to
483 update the library and dependencies (usbconfig, etc). Its advisable to
484 rebuild all ports which uses libusb. More specific directions are given
485 in the ports collection UPDATING file. Any /etc/libmap.conf entries for
486 libusb are no longer required and can be removed.
487
48820090302:
489 A workaround is committed to allow the creation of System V shared
490 memory segment of size > 2 GB on the 64-bit architectures.
491 Due to a limitation of the existing ABI, the shm_segsz member
492 of the struct shmid_ds, returned by shmctl(IPC_STAT) call is
493 wrong for large segments. Note that limits must be explicitly
494 raised to allow such segments to be created.
495
49620090301:
497 The layout of struct ifnet has changed, requiring a rebuild of all
498 network device driver modules.
499
50020090227:
501 The /dev handling for the new USB stack has changed, a
502 buildworld/installworld is required for libusb20.
503
50420090223:
505 The new USB2 stack has now been permanently moved in and all kernel and
506 module names reverted to their previous values (eg, usb, ehci, ohci,
507 ums, ...). The old usb stack can be compiled in by prefixing the name
508 with the letter 'o', the old usb modules have been removed.
509 Updating entry 20090216 for xorg and 20090215 for libmap may still
510 apply.
511
51220090217:
513 The rc.conf(5) option if_up_delay has been renamed to
514 defaultroute_delay to better reflect its purpose. If you have
515 customized this setting in /etc/rc.conf you need to update it to
516 use the new name.
517
51820090216:
519 xorg 7.4 wants to configure its input devices via hald which does not
520 yet work with USB2. If the keyboard/mouse does not work in xorg then
521 add
522 Option "AllowEmptyInput" "off"
523 to your ServerLayout section. This will cause X to use the configured
524 kbd and mouse sections from your xorg.conf.
525
52620090215:
527 The GENERIC kernels for all architectures now default to the new USB2
528 stack. No kernel config options or code have been removed so if a
529 problem arises please report it and optionally revert to the old USB
530 stack. If you are loading USB kernel modules or have a custom kernel
531 that includes GENERIC then ensure that usb names are also changed over,
532 eg uftdi -> usb2_serial_ftdi.
533
534 Older programs linked against the ports libusb 0.1 need to be
535 redirected to the new stack's libusb20. /etc/libmap.conf can
536 be used for this:
537 # Map old usb library to new one for usb2 stack
538 libusb-0.1.so.8 libusb20.so.1
539
54020090203:
541 The ichsmb(4) driver has been changed to require SMBus slave
542 addresses be left-justified (xxxxxxx0b) rather than right-justified.
543 All of the other SMBus controller drivers require left-justified
544 slave addresses, so this change makes all the drivers provide the
545 same interface.
546
54720090201:
548 INET6 statistics (struct ip6stat) was updated.
549 netstat(1) needs to be recompiled.
550
55120090119:
552 NTFS has been removed from GENERIC kernel on amd64 to match
553 GENERIC on i386. Should not cause any issues since mount_ntfs(8)
554 will load ntfs.ko module automatically when NTFS support is
555 actually needed, unless ntfs.ko is not installed or security
556 level prohibits loading kernel modules. If either is the case,
557 "options NTFS" has to be added into kernel config.
558
55920090115:
560 TCP Appropriate Byte Counting (RFC 3465) support added to kernel.
561 New field in struct tcpcb breaks ABI, so bump __FreeBSD_version to
562 800061. User space tools that rely on the size of struct tcpcb in
563 tcp_var.h (e.g. sockstat) need to be recompiled.
564
56520081225:
566 ng_tty(4) module updated to match the new TTY subsystem.
567 Due to API change, user-level applications must be updated.
568 New API support added to mpd5 CVS and expected to be present
569 in next mpd5.3 release.
570
57120081219:
572 With __FreeBSD_version 800060 the makefs tool is part of
573 the base system (it was a port).
574
57520081216:
576 The afdata and ifnet locks have been changed from mutexes to
577 rwlocks, network modules will need to be re-compiled.
578
57920081214:
580 __FreeBSD_version 800059 incorporates the new arp-v2 rewrite.
581 RTF_CLONING, RTF_LLINFO and RTF_WASCLONED flags are eliminated.
582 The new code reduced struct rtentry{} by 16 bytes on 32-bit
583 architecture and 40 bytes on 64-bit architecture. The userland
584 applications "arp" and "ndp" have been updated accordingly.
585 The output from "netstat -r" shows only routing entries and
586 none of the L2 information.
587
58820081130:
589 __FreeBSD_version 800057 marks the switchover from the
590 binary ath hal to source code. Users must add the line:
591
592 options AH_SUPPORT_AR5416
593
594 to their kernel config files when specifying:
595
596 device ath_hal
597
598 The ath_hal module no longer exists; the code is now compiled
599 together with the driver in the ath module. It is now
600 possible to tailor chip support (i.e. reduce the set of chips
601 and thereby the code size); consult ath_hal(4) for details.
602
60320081121:
604 __FreeBSD_version 800054 adds memory barriers to
605 <machine/atomic.h>, new interfaces to ifnet to facilitate
606 multiple hardware transmit queues for cards that support
607 them, and a lock-less ring-buffer implementation to
608 enable drivers to more efficiently manage queueing of
609 packets.
610
61120081117:
612 A new version of ZFS (version 13) has been merged to -HEAD.
613 This version has zpool attribute "listsnapshots" off by
614 default, which means "zfs list" does not show snapshots,
615 and is the same as Solaris behavior.
616
61720081028:
618 dummynet(4) ABI has changed. ipfw(8) needs to be recompiled.
619
62020081009:
621 The uhci, ohci, ehci and slhci USB Host controller drivers have
622 been put into separate modules. If you load the usb module
623 separately through loader.conf you will need to load the
624 appropriate *hci module as well. E.g. for a UHCI-based USB 2.0
625 controller add the following to loader.conf:
626
627 uhci_load="YES"
628 ehci_load="YES"
629
63020081009:
631 The ABI used by the PMC toolset has changed. Please keep
632 userland (libpmc(3)) and the kernel module (hwpmc(4)) in
633 sync.
634
|
63520080820:
636 The TTY subsystem of the kernel has been replaced by a new
637 implementation, which provides better scalability and an
638 improved driver model. Most common drivers have been migrated to
639 the new TTY subsystem, while others have not. The following
640 drivers have not yet been ported to the new TTY layer:
641
642 PCI/ISA:
643 cy, digi, rc, rp, sio
644
645 USB:
646 ubser, ucycom
647
648 Line disciplines:
649 ng_h4, ng_tty, ppp, sl, snp
650
651 Adding these drivers to your kernel configuration file shall
652 cause compilation to fail.
653
65420080818:
655 ntpd has been upgraded to 4.2.4p5.
656
65720080801:
658 OpenSSH has been upgraded to 5.1p1.
659
660 For many years, FreeBSD's version of OpenSSH preferred DSA
661 over RSA for host and user authentication keys. With this
662 upgrade, we've switched to the vendor's default of RSA over
663 DSA. This may cause upgraded clients to warn about unknown
664 host keys even for previously known hosts. Users should
665 follow the usual procedure for verifying host keys before
666 accepting the RSA key.
667
668 This can be circumvented by setting the "HostKeyAlgorithms"
669 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
670 command line.
671
672 Please note that the sequence of keys offered for
673 authentication has been changed as well. You may want to
674 specify IdentityFile in a different order to revert this
675 behavior.
676
67720080713:
678 The sio(4) driver has been removed from the i386 and amd64
679 kernel configuration files. This means uart(4) is now the
680 default serial port driver on those platforms as well.
681
682 To prevent collisions with the sio(4) driver, the uart(4) driver
683 uses different names for its device nodes. This means the
684 onboard serial port will now most likely be called "ttyu0"
685 instead of "ttyd0". You may need to reconfigure applications to
686 use the new device names.
687
688 When using the serial port as a boot console, be sure to update
689 /boot/device.hints and /etc/ttys before booting the new kernel.
690 If you forget to do so, you can still manually specify the hints
691 at the loader prompt:
692
693 set hint.uart.0.at="isa"
694 set hint.uart.0.port="0x3F8"
695 set hint.uart.0.flags="0x10"
696 set hint.uart.0.irq="4"
697 boot -s
698
69920080609:
700 The gpt(8) utility has been removed. Use gpart(8) to partition
701 disks instead.
702
70320080603:
704 The version that Linuxulator emulates was changed from 2.4.2
705 to 2.6.16. If you experience any problems with Linux binaries
706 please try to set sysctl compat.linux.osrelease to 2.4.2 and
707 if it fixes the problem contact emulation mailing list.
708
70920080525:
710 ISDN4BSD (I4B) was removed from the src tree. You may need to
711 update a your kernel configuration and remove relevant entries.
712
71320080509:
714 I have checked in code to support multiple routing tables.
715 See the man pages setfib(1) and setfib(2).
716 This is a hopefully backwards compatible version,
717 but to make use of it you need to compile your kernel
718 with options ROUTETABLES=2 (or more up to 16).
719
72020080420:
721 The 802.11 wireless support was redone to enable multi-bss
722 operation on devices that are capable. The underlying device
723 is no longer used directly but instead wlanX devices are
724 cloned with ifconfig. This requires changes to rc.conf files.
725 For example, change:
726 ifconfig_ath0="WPA DHCP"
727 to
728 wlans_ath0=wlan0
729 ifconfig_wlan0="WPA DHCP"
730 see rc.conf(5) for more details. In addition, mergemaster of
731 /etc/rc.d is highly recommended. Simultaneous update of userland
732 and kernel wouldn't hurt either.
733
734 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
735 modules were merged into the base wlan module. All references
736 to these modules (e.g. in kernel config files) must be removed.
737
73820080408:
739 psm(4) has gained write(2) support in native operation level.
740 Arbitrary commands can be written to /dev/psm%d and status can
741 be read back from it. Therefore, an application is responsible
742 for status validation and error recovery. It is a no-op in
743 other operation levels.
744
74520080312:
746 Support for KSE threading has been removed from the kernel. To
747 run legacy applications linked against KSE libmap.conf may
748 be used. The following libmap.conf may be used to ensure
749 compatibility with any prior release:
750
751 libpthread.so.1 libthr.so.1
752 libpthread.so.2 libthr.so.2
753 libkse.so.3 libthr.so.3
754
75520080301:
756 The layout of struct vmspace has changed. This affects libkvm
757 and any executables that link against libkvm and use the
758 kvm_getprocs() function. In particular, but not exclusively,
759 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
760 The effects are minimal, but it's advisable to upgrade world
761 nonetheless.
762
76320080229:
764 The latest em driver no longer has support in it for the
765 82575 adapter, this is now moved to the igb driver. The
766 split was done to make new features that are incompatible
767 with older hardware easier to do.
768
76920080220:
770 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
771 likewise the kernel option is now GEOM_LINUX_LVM.
772
77320080211:
774 The default NFS mount mode has changed from UDP to TCP for
775 increased reliability. If you rely on (insecurely) NFS
776 mounting across a firewall you may need to update your
777 firewall rules.
778
77920080208:
780 Belatedly note the addition of m_collapse for compacting
781 mbuf chains.
782
78320080126:
784 The fts(3) structures have been changed to use adequate
785 integer types for their members and so to be able to cope
786 with huge file trees. The old fts(3) ABI is preserved
787 through symbol versioning in libc, so third-party binaries
788 using fts(3) should still work, although they will not take
789 advantage of the extended types. At the same time, some
790 third-party software might fail to build after this change
791 due to unportable assumptions made in its source code about
792 fts(3) structure members. Such software should be fixed
793 by its vendor or, in the worst case, in the ports tree.
794 FreeBSD_version 800015 marks this change for the unlikely
795 case that a portable fix is impossible.
796
79720080123:
798 To upgrade to -current after this date, you must be running
799 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
800 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
801
80220071128:
803 The ADAPTIVE_GIANT kernel option has been retired because its
804 functionality is the default now.
805
80620071118:
807 The AT keyboard emulation of sunkbd(4) has been turned on
808 by default. In order to make the special symbols of the Sun
809 keyboards driven by sunkbd(4) work under X these now have
810 to be configured the same way as Sun USB keyboards driven
811 by ukbd(4) (which also does AT keyboard emulation), f.e.:
812
813 Option "XkbLayout" "us"
814 Option "XkbRules" "xorg"
815 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
816
81720071024:
818 It has been decided that it is desirable to provide ABI
819 backwards compatibility to the FreeBSD 4/5/6 versions of the
820 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
821 broken with the introduction of PCI domain support (see the
822 20070930 entry). Unfortunately, this required the ABI of
823 PCIOCGETCONF to be broken again in order to be able to
824 provide backwards compatibility to the old version of that
825 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
826 again. As for prominent ports this affects neither pciutils
827 nor xorg-server this time, the hal port needs to be rebuilt
828 however.
829
83020071020:
831 The misnamed kthread_create() and friends have been renamed
832 to kproc_create() etc. Many of the callers already
833 used kproc_start()..
834 I will return kthread_create() and friends in a while
835 with implementations that actually create threads, not procs.
836 Renaming corresponds with version 800002.
837
83820071010:
839 RELENG_7 branched.
840
841COMMON ITEMS:
842
843 General Notes
844 -------------
845 Avoid using make -j when upgrading. While generally safe, there are
846 sometimes problems using -j to upgrade. If your upgrade fails with
847 -j, please try again wtihout -j. From time to time in the past there
848 have been problems using -j with buildworld and/or installworld. This
849 is especially true when upgrading between "distant" versions (eg one
850 that cross a major release boundary or several minor releases, or when
851 several months have passed on the -current branch).
852
853 Sometimes, obscure build problems are the result of environment
854 poisoning. This can happen because the make utility reads its
855 environment when searching for values for global variables. To run
856 your build attempts in an "environmental clean room", prefix all make
857 commands with 'env -i '. See the env(1) manual page for more details.
858
859 When upgrading from one major version to another it is generally best
860 to upgrade to the latest code in the currently installed branch first,
861 then do an upgrade to the new branch. This is the best-tested upgrade
862 path, and has the highest probability of being successful. Please try
863 this approach before reporting problems with a major version upgrade.
864
865 To build a kernel
866 -----------------
867 If you are updating from a prior version of FreeBSD (even one just
868 a few days old), you should follow this procedure. It is the most
869 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
870
871 make kernel-toolchain
872 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
873 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
874
875 To test a kernel once
876 ---------------------
877 If you just want to boot a kernel once (because you are not sure
878 if it works, or if you want to boot a known bad kernel to provide
879 debugging information) run
880 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
881 nextboot -k testkernel
882
883 To just build a kernel when you know that it won't mess you up
884 --------------------------------------------------------------
885 This assumes you are already running a CURRENT system. Replace
886 ${arch} with the architecture of your machine (e.g. "i386",
887 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
888
889 cd src/sys/${arch}/conf
890 config KERNEL_NAME_HERE
891 cd ../compile/KERNEL_NAME_HERE
892 make depend
893 make
894 make install
895
896 If this fails, go to the "To build a kernel" section.
897
898 To rebuild everything and install it on the current system.
899 -----------------------------------------------------------
900 # Note: sometimes if you are running current you gotta do more than
901 # is listed here if you are upgrading from a really old current.
902
903 <make sure you have good level 0 dumps>
904 make buildworld
905 make kernel KERNCONF=YOUR_KERNEL_HERE
906 [1]
907 <reboot in single user> [3]
908 mergemaster -p [5]
909 make installworld
910 make delete-old
911 mergemaster [4]
912 <reboot>
913
914
915 To cross-install current onto a separate partition
916 --------------------------------------------------
917 # In this approach we use a separate partition to hold
918 # current's root, 'usr', and 'var' directories. A partition
919 # holding "/", "/usr" and "/var" should be about 2GB in
920 # size.
921
922 <make sure you have good level 0 dumps>
923 <boot into -stable>
924 make buildworld
925 make buildkernel KERNCONF=YOUR_KERNEL_HERE
926 <maybe newfs current's root partition>
927 <mount current's root partition on directory ${CURRENT_ROOT}>
928 make installworld DESTDIR=${CURRENT_ROOT}
929 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
930 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
931 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
932 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
933 <reboot into current>
934 <do a "native" rebuild/install as described in the previous section>
935 <maybe install compatibility libraries from ports/misc/compat*>
936 <reboot>
937
938
939 To upgrade in-place from 8.x-stable to current
940 ----------------------------------------------
941 <make sure you have good level 0 dumps>
942 make buildworld [9]
943 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
944 [1]
945 <reboot in single user> [3]
946 mergemaster -p [5]
947 make installworld
948 make delete-old
949 mergemaster -i [4]
950 <reboot>
951
952 Make sure that you've read the UPDATING file to understand the
953 tweaks to various things you need. At this point in the life
954 cycle of current, things change often and you are on your own
955 to cope. The defaults can also change, so please read ALL of
956 the UPDATING entries.
957
958 Also, if you are tracking -current, you must be subscribed to
959 freebsd-current@freebsd.org. Make sure that before you update
960 your sources that you have read and understood all the recent
961 messages there. If in doubt, please track -stable which has
962 much fewer pitfalls.
963
964 [1] If you have third party modules, such as vmware, you
965 should disable them at this point so they don't crash your
966 system on reboot.
967
968 [3] From the bootblocks, boot -s, and then do
969 fsck -p
970 mount -u /
971 mount -a
972 cd src
973 adjkerntz -i # if CMOS is wall time
974 Also, when doing a major release upgrade, it is required that
975 you boot into single user mode to do the installworld.
976
977 [4] Note: This step is non-optional. Failure to do this step
978 can result in a significant reduction in the functionality of the
979 system. Attempting to do it by hand is not recommended and those
980 that pursue this avenue should read this file carefully, as well
981 as the archives of freebsd-current and freebsd-hackers mailing lists
982 for potential gotchas.
983
984 [5] Usually this step is a noop. However, from time to time
985 you may need to do this if you get unknown user in the following
986 step. It never hurts to do it all the time. You may need to
987 install a new mergemaster (cd src/usr.sbin/mergemaster && make
988 install) after the buildworld before this step if you last updated
989 from current before 20020224 or from -stable before 20020408.
990
991 [8] In order to have a kernel that can run the 4.x binaries needed to
992 do an installworld, you must include the COMPAT_FREEBSD4 option in
993 your kernel. Failure to do so may leave you with a system that is
994 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
995 required to run the 5.x binaries on more recent kernels. And so on
996 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
997
998 Make sure that you merge any new devices from GENERIC since the
999 last time you updated your kernel config file.
1000
1001 [9] When checking out sources, you must include the -P flag to have
1002 cvs prune empty directories.
1003
1004 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1005 "?=" instead of the "=" assignment operator, so that buildworld can
1006 override the CPUTYPE if it needs to.
1007
1008 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1009 not on the command line, or in /etc/make.conf. buildworld will
1010 warn if it is improperly defined.
1011FORMAT:
1012
1013This file contains a list, in reverse chronological order, of major
1014breakages in tracking -current. Not all things will be listed here,
1015and it only starts on October 16, 2004. Updating files can found in
1016previous releases if your system is older than this.
1017
1018Copyright information:
1019
1020Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1021
1022Redistribution, publication, translation and use, with or without
1023modification, in full or in part, in any form or format of this
1024document are permitted without further permission from the author.
1025
1026THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1027IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1028WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1029DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1030INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1031(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1032SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1033HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1034STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1035IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1036POSSIBILITY OF SUCH DAMAGE.
1037
1038Contact Warner Losh if you have any questions about your use of
1039this document.
1040
| 64420080820:
645 The TTY subsystem of the kernel has been replaced by a new
646 implementation, which provides better scalability and an
647 improved driver model. Most common drivers have been migrated to
648 the new TTY subsystem, while others have not. The following
649 drivers have not yet been ported to the new TTY layer:
650
651 PCI/ISA:
652 cy, digi, rc, rp, sio
653
654 USB:
655 ubser, ucycom
656
657 Line disciplines:
658 ng_h4, ng_tty, ppp, sl, snp
659
660 Adding these drivers to your kernel configuration file shall
661 cause compilation to fail.
662
66320080818:
664 ntpd has been upgraded to 4.2.4p5.
665
66620080801:
667 OpenSSH has been upgraded to 5.1p1.
668
669 For many years, FreeBSD's version of OpenSSH preferred DSA
670 over RSA for host and user authentication keys. With this
671 upgrade, we've switched to the vendor's default of RSA over
672 DSA. This may cause upgraded clients to warn about unknown
673 host keys even for previously known hosts. Users should
674 follow the usual procedure for verifying host keys before
675 accepting the RSA key.
676
677 This can be circumvented by setting the "HostKeyAlgorithms"
678 option to "ssh-dss,ssh-rsa" in ~/.ssh/config or on the ssh
679 command line.
680
681 Please note that the sequence of keys offered for
682 authentication has been changed as well. You may want to
683 specify IdentityFile in a different order to revert this
684 behavior.
685
68620080713:
687 The sio(4) driver has been removed from the i386 and amd64
688 kernel configuration files. This means uart(4) is now the
689 default serial port driver on those platforms as well.
690
691 To prevent collisions with the sio(4) driver, the uart(4) driver
692 uses different names for its device nodes. This means the
693 onboard serial port will now most likely be called "ttyu0"
694 instead of "ttyd0". You may need to reconfigure applications to
695 use the new device names.
696
697 When using the serial port as a boot console, be sure to update
698 /boot/device.hints and /etc/ttys before booting the new kernel.
699 If you forget to do so, you can still manually specify the hints
700 at the loader prompt:
701
702 set hint.uart.0.at="isa"
703 set hint.uart.0.port="0x3F8"
704 set hint.uart.0.flags="0x10"
705 set hint.uart.0.irq="4"
706 boot -s
707
70820080609:
709 The gpt(8) utility has been removed. Use gpart(8) to partition
710 disks instead.
711
71220080603:
713 The version that Linuxulator emulates was changed from 2.4.2
714 to 2.6.16. If you experience any problems with Linux binaries
715 please try to set sysctl compat.linux.osrelease to 2.4.2 and
716 if it fixes the problem contact emulation mailing list.
717
71820080525:
719 ISDN4BSD (I4B) was removed from the src tree. You may need to
720 update a your kernel configuration and remove relevant entries.
721
72220080509:
723 I have checked in code to support multiple routing tables.
724 See the man pages setfib(1) and setfib(2).
725 This is a hopefully backwards compatible version,
726 but to make use of it you need to compile your kernel
727 with options ROUTETABLES=2 (or more up to 16).
728
72920080420:
730 The 802.11 wireless support was redone to enable multi-bss
731 operation on devices that are capable. The underlying device
732 is no longer used directly but instead wlanX devices are
733 cloned with ifconfig. This requires changes to rc.conf files.
734 For example, change:
735 ifconfig_ath0="WPA DHCP"
736 to
737 wlans_ath0=wlan0
738 ifconfig_wlan0="WPA DHCP"
739 see rc.conf(5) for more details. In addition, mergemaster of
740 /etc/rc.d is highly recommended. Simultaneous update of userland
741 and kernel wouldn't hurt either.
742
743 As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta
744 modules were merged into the base wlan module. All references
745 to these modules (e.g. in kernel config files) must be removed.
746
74720080408:
748 psm(4) has gained write(2) support in native operation level.
749 Arbitrary commands can be written to /dev/psm%d and status can
750 be read back from it. Therefore, an application is responsible
751 for status validation and error recovery. It is a no-op in
752 other operation levels.
753
75420080312:
755 Support for KSE threading has been removed from the kernel. To
756 run legacy applications linked against KSE libmap.conf may
757 be used. The following libmap.conf may be used to ensure
758 compatibility with any prior release:
759
760 libpthread.so.1 libthr.so.1
761 libpthread.so.2 libthr.so.2
762 libkse.so.3 libthr.so.3
763
76420080301:
765 The layout of struct vmspace has changed. This affects libkvm
766 and any executables that link against libkvm and use the
767 kvm_getprocs() function. In particular, but not exclusively,
768 it affects ps(1), fstat(1), pkill(1), systat(1), top(1) and w(1).
769 The effects are minimal, but it's advisable to upgrade world
770 nonetheless.
771
77220080229:
773 The latest em driver no longer has support in it for the
774 82575 adapter, this is now moved to the igb driver. The
775 split was done to make new features that are incompatible
776 with older hardware easier to do.
777
77820080220:
779 The new geom_lvm(4) geom class has been renamed to geom_linux_lvm(4),
780 likewise the kernel option is now GEOM_LINUX_LVM.
781
78220080211:
783 The default NFS mount mode has changed from UDP to TCP for
784 increased reliability. If you rely on (insecurely) NFS
785 mounting across a firewall you may need to update your
786 firewall rules.
787
78820080208:
789 Belatedly note the addition of m_collapse for compacting
790 mbuf chains.
791
79220080126:
793 The fts(3) structures have been changed to use adequate
794 integer types for their members and so to be able to cope
795 with huge file trees. The old fts(3) ABI is preserved
796 through symbol versioning in libc, so third-party binaries
797 using fts(3) should still work, although they will not take
798 advantage of the extended types. At the same time, some
799 third-party software might fail to build after this change
800 due to unportable assumptions made in its source code about
801 fts(3) structure members. Such software should be fixed
802 by its vendor or, in the worst case, in the ports tree.
803 FreeBSD_version 800015 marks this change for the unlikely
804 case that a portable fix is impossible.
805
80620080123:
807 To upgrade to -current after this date, you must be running
808 FreeBSD not older than 6.0-RELEASE. Upgrading to -current
809 from 5.x now requires a stop over at RELENG_6 or RELENG_7 systems.
810
81120071128:
812 The ADAPTIVE_GIANT kernel option has been retired because its
813 functionality is the default now.
814
81520071118:
816 The AT keyboard emulation of sunkbd(4) has been turned on
817 by default. In order to make the special symbols of the Sun
818 keyboards driven by sunkbd(4) work under X these now have
819 to be configured the same way as Sun USB keyboards driven
820 by ukbd(4) (which also does AT keyboard emulation), f.e.:
821
822 Option "XkbLayout" "us"
823 Option "XkbRules" "xorg"
824 Option "XkbSymbols" "pc(pc105)+sun_vndr/usb(sun_usb)+us"
825
82620071024:
827 It has been decided that it is desirable to provide ABI
828 backwards compatibility to the FreeBSD 4/5/6 versions of the
829 PCIOCGETCONF, PCIOCREAD and PCIOCWRITE IOCTLs, which was
830 broken with the introduction of PCI domain support (see the
831 20070930 entry). Unfortunately, this required the ABI of
832 PCIOCGETCONF to be broken again in order to be able to
833 provide backwards compatibility to the old version of that
834 IOCTL. Thus consumers of PCIOCGETCONF have to be recompiled
835 again. As for prominent ports this affects neither pciutils
836 nor xorg-server this time, the hal port needs to be rebuilt
837 however.
838
83920071020:
840 The misnamed kthread_create() and friends have been renamed
841 to kproc_create() etc. Many of the callers already
842 used kproc_start()..
843 I will return kthread_create() and friends in a while
844 with implementations that actually create threads, not procs.
845 Renaming corresponds with version 800002.
846
84720071010:
848 RELENG_7 branched.
849
850COMMON ITEMS:
851
852 General Notes
853 -------------
854 Avoid using make -j when upgrading. While generally safe, there are
855 sometimes problems using -j to upgrade. If your upgrade fails with
856 -j, please try again wtihout -j. From time to time in the past there
857 have been problems using -j with buildworld and/or installworld. This
858 is especially true when upgrading between "distant" versions (eg one
859 that cross a major release boundary or several minor releases, or when
860 several months have passed on the -current branch).
861
862 Sometimes, obscure build problems are the result of environment
863 poisoning. This can happen because the make utility reads its
864 environment when searching for values for global variables. To run
865 your build attempts in an "environmental clean room", prefix all make
866 commands with 'env -i '. See the env(1) manual page for more details.
867
868 When upgrading from one major version to another it is generally best
869 to upgrade to the latest code in the currently installed branch first,
870 then do an upgrade to the new branch. This is the best-tested upgrade
871 path, and has the highest probability of being successful. Please try
872 this approach before reporting problems with a major version upgrade.
873
874 To build a kernel
875 -----------------
876 If you are updating from a prior version of FreeBSD (even one just
877 a few days old), you should follow this procedure. It is the most
878 failsafe as it uses a /usr/obj tree with a fresh mini-buildworld,
879
880 make kernel-toolchain
881 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
882 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
883
884 To test a kernel once
885 ---------------------
886 If you just want to boot a kernel once (because you are not sure
887 if it works, or if you want to boot a known bad kernel to provide
888 debugging information) run
889 make installkernel KERNCONF=YOUR_KERNEL_HERE KODIR=/boot/testkernel
890 nextboot -k testkernel
891
892 To just build a kernel when you know that it won't mess you up
893 --------------------------------------------------------------
894 This assumes you are already running a CURRENT system. Replace
895 ${arch} with the architecture of your machine (e.g. "i386",
896 "arm", "amd64", "ia64", "pc98", "sparc64", "powerpc", "mips", etc).
897
898 cd src/sys/${arch}/conf
899 config KERNEL_NAME_HERE
900 cd ../compile/KERNEL_NAME_HERE
901 make depend
902 make
903 make install
904
905 If this fails, go to the "To build a kernel" section.
906
907 To rebuild everything and install it on the current system.
908 -----------------------------------------------------------
909 # Note: sometimes if you are running current you gotta do more than
910 # is listed here if you are upgrading from a really old current.
911
912 <make sure you have good level 0 dumps>
913 make buildworld
914 make kernel KERNCONF=YOUR_KERNEL_HERE
915 [1]
916 <reboot in single user> [3]
917 mergemaster -p [5]
918 make installworld
919 make delete-old
920 mergemaster [4]
921 <reboot>
922
923
924 To cross-install current onto a separate partition
925 --------------------------------------------------
926 # In this approach we use a separate partition to hold
927 # current's root, 'usr', and 'var' directories. A partition
928 # holding "/", "/usr" and "/var" should be about 2GB in
929 # size.
930
931 <make sure you have good level 0 dumps>
932 <boot into -stable>
933 make buildworld
934 make buildkernel KERNCONF=YOUR_KERNEL_HERE
935 <maybe newfs current's root partition>
936 <mount current's root partition on directory ${CURRENT_ROOT}>
937 make installworld DESTDIR=${CURRENT_ROOT}
938 make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
939 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
940 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
941 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
942 <reboot into current>
943 <do a "native" rebuild/install as described in the previous section>
944 <maybe install compatibility libraries from ports/misc/compat*>
945 <reboot>
946
947
948 To upgrade in-place from 8.x-stable to current
949 ----------------------------------------------
950 <make sure you have good level 0 dumps>
951 make buildworld [9]
952 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
953 [1]
954 <reboot in single user> [3]
955 mergemaster -p [5]
956 make installworld
957 make delete-old
958 mergemaster -i [4]
959 <reboot>
960
961 Make sure that you've read the UPDATING file to understand the
962 tweaks to various things you need. At this point in the life
963 cycle of current, things change often and you are on your own
964 to cope. The defaults can also change, so please read ALL of
965 the UPDATING entries.
966
967 Also, if you are tracking -current, you must be subscribed to
968 freebsd-current@freebsd.org. Make sure that before you update
969 your sources that you have read and understood all the recent
970 messages there. If in doubt, please track -stable which has
971 much fewer pitfalls.
972
973 [1] If you have third party modules, such as vmware, you
974 should disable them at this point so they don't crash your
975 system on reboot.
976
977 [3] From the bootblocks, boot -s, and then do
978 fsck -p
979 mount -u /
980 mount -a
981 cd src
982 adjkerntz -i # if CMOS is wall time
983 Also, when doing a major release upgrade, it is required that
984 you boot into single user mode to do the installworld.
985
986 [4] Note: This step is non-optional. Failure to do this step
987 can result in a significant reduction in the functionality of the
988 system. Attempting to do it by hand is not recommended and those
989 that pursue this avenue should read this file carefully, as well
990 as the archives of freebsd-current and freebsd-hackers mailing lists
991 for potential gotchas.
992
993 [5] Usually this step is a noop. However, from time to time
994 you may need to do this if you get unknown user in the following
995 step. It never hurts to do it all the time. You may need to
996 install a new mergemaster (cd src/usr.sbin/mergemaster && make
997 install) after the buildworld before this step if you last updated
998 from current before 20020224 or from -stable before 20020408.
999
1000 [8] In order to have a kernel that can run the 4.x binaries needed to
1001 do an installworld, you must include the COMPAT_FREEBSD4 option in
1002 your kernel. Failure to do so may leave you with a system that is
1003 hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is
1004 required to run the 5.x binaries on more recent kernels. And so on
1005 for COMPAT_FREEBSD6 and COMPAT_FREEBSD7.
1006
1007 Make sure that you merge any new devices from GENERIC since the
1008 last time you updated your kernel config file.
1009
1010 [9] When checking out sources, you must include the -P flag to have
1011 cvs prune empty directories.
1012
1013 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1014 "?=" instead of the "=" assignment operator, so that buildworld can
1015 override the CPUTYPE if it needs to.
1016
1017 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1018 not on the command line, or in /etc/make.conf. buildworld will
1019 warn if it is improperly defined.
1020FORMAT:
1021
1022This file contains a list, in reverse chronological order, of major
1023breakages in tracking -current. Not all things will be listed here,
1024and it only starts on October 16, 2004. Updating files can found in
1025previous releases if your system is older than this.
1026
1027Copyright information:
1028
1029Copyright 1998-2009 M. Warner Losh. All Rights Reserved.
1030
1031Redistribution, publication, translation and use, with or without
1032modification, in full or in part, in any form or format of this
1033document are permitted without further permission from the author.
1034
1035THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1036IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1037WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1038DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1039INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1040(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1041SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1042HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1043STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1044IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1045POSSIBILITY OF SUCH DAMAGE.
1046
1047Contact Warner Losh if you have any questions about your use of
1048this document.
1049
|