1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
9 portupgrade. Important recent entries: 20040724 (default X changes).
11 [[ The UPDATING file will be trimmed to 20040814 on or about Oct 1, 2004 ]]
13 NOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW:
14 FreeBSD 6.x has many debugging features turned on, in
15 both the kernel and userland. These features attempt to detect
16 incorrect use of system primitives, and encourage loud failure
17 through extra sanity checking and fail stop semantics. They
18 also substantially impact system performance. If you want to
19 do performance measurement, benchmarking, and optimization,
20 you'll want to turn them off. This includes various WITNESS-
21 related kernel options, INVARIANTS, malloc debugging flags
22 in userland, and various verbose features in the kernel. Many
23 developers choose to disable these features on build machines
24 to maximize performance.
27 The wlan support has been updated to split the crypto support
28 into separate modules. For static WEP you must configure the
29 wlan_wep module in your system or build and install the module
30 in place where it can be loaded (the kernel will auto-load
31 the module when a wep key is configured).
34 The ath driver has been updated to split the tx rate control
35 algorithm into a separate module. You need to include either
36 ath_rate_onoe or ath_rate_amrr when configuring the kernel.
39 Support for systems with an 80386 CPU has been removed. Please
40 use FreeBSD 5.x or earlier on systems with an 80386.
43 We have had a hack which would mount the root filesystem
44 R/W if the device were named 'md*'. As part of the vnode
45 work I'm doing I have had to remove this hack. People
46 building systems which use preloaded MD root filesystems
47 may need to insert a "/sbin/mount -u -o rw /dev/md0 /" in
48 their /etc/rc scripts.
51 The size of struct tcpcb has changed again due to the removal
52 of RFC1644 T/TCP. You have to recompile userland programs that
53 read kmem for tcp sockets directly (netstat, sockstat, etc.)
56 The size of struct tcpcb has changed. You have to recompile
57 userland programs that read kmem for tcp sockets directly
58 (netstat, sockstat, etc.)
61 A major sweep over the tty drivers to elimnate approx 3100
62 lines of copy&pasted code have been performed. As a part of
63 this change some tty devices have changed names:
64 sio devices are now named: {tty,cua}d%d[.init,.lock]
65 ucom devices are now named: {tty,cua}U%d[.init,.lock]
66 For other drivers see the commit logs.
69 The FreeBSD keyword is no longer a requirement for a valid
70 rc.d script. The rc(8) and rc.shutdown(8) scripts no longer check
71 for the existence of this keyword when ordering rc.d scripts.
72 This change touches most of the file in /etc/rc.d; therefore,
73 if you have not modified any files in that directory it may
74 be easier to rm -rf /etc/rc.d and then use the -i switch with
78 One of the syscalls the 1:1 threading library libthr uses has
79 changed, thus breaking ABI compatibility. Make sure you rebuild
80 this library with the kernel.
83 The following libraries had their version number bumped up:
84 /lib/libm.so.2 -> libm.so.3
85 /lib/libreadline.so.4 -> libreadline.so.5
86 /usr/lib/libhistory.so.4 -> libhistory.so.5
87 /usr/lib/libopie.so.2 -> libopie.so.3
88 /usr/lib/libpcap.so.2 -> libpcap.so.3
89 FreeBSD 4.10 versions of these libraries will be added to the
90 compat4x collection. If you expect to be able to run old 4.X
91 executables you will need to remove the old versions of these
92 libraries. However note that any 5.X executables you have built
93 will stop working once you remove those old libraries. You should
94 have all your ports/packages rebuilt before removing the old
98 The pfil API has gained an additional argument to pass an inpcb.
99 You should rebuild all pfil consuming modules: ipfw, ipfilter
103 If named is enabled, the default is now to run it in a chroot
104 "sandbox." For users with existing configurations in
105 /etc/namedb the migration should be simple. Upgrade your
106 world as usual, then after installworld but before
107 mergemaster do the following:
109 If named is running: /etc/rc.d/named stop
112 mkdir -p /var/named/etc/namedb
113 cp -Rp namedb.bak/* /var/named/etc/namedb/
114 mergemaster (with your usual options)
115 If using the generated localhost* files:
116 cd /var/named/etc/namedb
117 /bin/sh make-localhost
118 rm -f localhost-v6.rev localhost.rev
119 /etc/rc.d/syslogd restart
120 /etc/rc.d/named start
122 If you are using a custom configuration, or if you have
123 customised the named_* variables in /etc/rc.conf[.local]
124 then you may have to adjust the instructions accordingly.
125 It is suggested that you carefully examine the new named
126 variables in /etc/defaults/rc.conf and the options in
127 /var/named/etc/namedb/named.conf to see if they might
128 now be more suitable.
131 BIND 9 has been imported into the base, and is now fully
132 functional. BIND 8 has now been removed. There are numerous
133 differences between BIND 8 and 9, and users with critical
134 named installations should read the migration documentation
135 in /usr/share/doc/bind9/misc/migration. There is also a
136 new instruction manual in /usr/share/doc/bind9/arm.
138 The key differences that most users will experience are in
139 how picky BIND 9 is about zone file format. If you are using
140 named as a resolving (caching) name server, you will likely
143 The following files are part of the old BIND 8 installation
144 and should be removed:
145 /usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer
146 /usr/sbin/named.restart /usr/sbin/ndc
148 The following files have moved to /usr/bin, and should be
149 removed from their old locations:
150 /usr/sbin/nslookup /usr/sbin/nsupdate
153 The format of the pflogd(8) logfile "/var/log/pflog" has changed for
154 architectures that have a 64 bit long type to make it compatible to
155 the standard pcap format. In order to prevent corruption move away
156 any old logfile before using a new pflogd(8).
159 debug.witness_* has been renamed to debug.witness.*. There are
160 compatibility tunables left in for a few days. Update loader.conf
164 The ifi_epoch change has been reverted because the ABI breakage
165 was too extensive. If you are running with a kernel/userland
166 containing the initial change (20040830), you should heed the
167 warning about ifconfig incompatibility when upgrading again.
168 With this change, 5.3 and 6.0 ifconfigs and kernels are once
172 A new variable, ifi_epoch, has been added to struct if_data
173 which is part if struct ifnet. This means all network drivers
174 and network monitoring applications need to be recompiled.
176 WARNING WARNING WARNING WARNING WARNING WARNING WARNING
178 This also breaks ifconfig compatibility. An old ifconfig will
179 not work with the new kernel and a new ifconfig will not work
180 with the old. It is strongly recommended that you make a copy
181 of your old ifconfig before installworld. If you are installing
182 remotely, you must copy over a new ifconfig before rebooting in
186 The default configuration for the network stack has been changed
187 such that it now runs without the Giant lock unless configured
188 otherwise. If you experience network-related instability, you
189 may wish to try setting "debug.mpsafenet=0" or compiling the
190 kernel with "options NET_WITH_GIANT". Details on the netperf
191 project may be found at:
193 http://www.watson.org/~robert/freebsd/netperf/
195 Including the 20040828 announcement of configuration change
199 PFIL_HOOKS are a fixed part of the network stack now and do not
200 need to be specified in the kernel configuration file anymore.
203 Netgraph changed its message format slightly to align the data
204 portion well on 64 bit machines.
205 Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
206 pppoed, bluetooth, ATM) should be recompiled when a new kernel
210 IPFW has been converted to use pfil(9). This change is
211 transparent to userland and preserves the ipfw ABI. The ipfw
212 core packet inspection and filtering functions have not been
213 changed, only how ipfw is invoked is different.
216 The RANDOM_IP_ID option has been replaced by the sysctl
217 net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
218 you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
221 The size of 'struct ifnet' has changed due to the addition of the
222 if_carp placeholder. All kernel modules implementing network
223 interfaces must be recompiled as a result.
226 Module loading has been fixed. Some older installations will
227 drop proper module_path initialization and modules will fail to
228 load properly. If you have a line in /boot/loader.rc that says:
229 "initialize drop", do (i386 only):
230 cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
231 chown root:wheel /boot/loader.rc
232 chmod 444 /boot/loader.rc
235 making /dev/(null|zero) into a module proved to be too unpopular,
236 so this bit has been revoked from the previous (20040801) entry.
239 The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
240 so you may wish to add them to your kernel config file. See
241 GENERIC for examples.
244 System compiler has been upgraded to GCC 3.4.2-pre. As with any major
245 compiler upgrade, there are several issues to be aware of. GCC 3.4.x
246 has broken C++ ABI compatibility with previous releases yet again
247 and users will have to rebuild all their C++ programs with the new
248 compiler. If you are getting run-time error such as
249 /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
250 This entry does apply to you.
252 A new unit-at-a-time optimization mode, which is default in this
253 compiler release, is more aggressive in removing unused static
254 symbols. This is the likely cause of 'make buildworld' breakages
255 with non-default CFLAGS where optimization level is set to -O2
258 With the upgrade of the system compiler, the kernel has been upgraded
259 to match the new system compiler. This makes it impossible to build
260 a new kernel with the old compiler. Upgrade your system via
261 make buildworld and make kernel (see below) to fix this problem.
264 The size of 'struct ifnet' has changed due to the addition of
265 the IFF_NEEDSGIANT flag (and what it implies). All kernel
266 modules implementing network interfaces must be recompiled as
270 The sound device drivers are renamed. `sound' is always required,
271 while `snd_*' should be configured accordingly to your hardware.
272 Refer to NOTES for the detail of the drivers.
275 __FreeBSD_version bumped to 502122.
278 The console initialization on Alpha has been reworked and is now
279 identical to other platforms. This means that the hardcoding of
280 the serial console and the debug port has been removed. As such,
281 hints are now required for the sio(4) driver to become a console
282 or debug port. The NO_SIO option has been decommissioned because
286 A revamp of the debugging code in the kernel with some visible
287 changes beyond just the debugging experience:
288 o The DDB option is now specific to the DDB debugger backend
289 and should not be used any more for conditional compilation
290 of debugging code for when debugging is enabled. Use the KDB
292 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
293 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
294 respectively. This is in line with the first bullet.
295 o The remote GDB support has been untangled from DDB and needs
296 to be enabled separately now. Use the GDB option for this.
297 o The GDB_REMOTE_CHAT option has been removed. Support for this
298 homegrown feature is discontinued. The GDB remote protocol
299 supports console output and it makes sense to use that.
300 o The DDB_NOKLDSYM option has been removed. The DDB debugger
301 now supports both direct symbol table lookups as well as KLD
302 symbol lookups through the linker.
305 Bluetooth code has been marked as non-i386 specific.
306 __FreeBSD_version has been bumped to 502121 to mark this change.
309 The native preemption has been added to the kernel scheduler.
310 There is some report that the ULE scheduler was broken in some
311 machines and we encourage users using the ULE scheduler either
312 stick with a known good kernel, or temporarily switch to the 4BSD
313 scheduler as a workaround.
316 The netgraph ABI version number has been incremented to indicate
317 an incompatible change in the ABI. Old netgraph nodes will refuse
318 to attach until recompiled. Netgraph now uses mbuf tags to move
319 metadata and this commit removes its home-grown metadata facility.
320 Nodes should just recompile, unless they use metadata, in which
321 case the changes are simple; the file ng_ksocket.c serves as an
322 example of such changes.
324 This also broke i4b, although the compile problem has been papered
328 ACPI has been updated to disable known-bad BIOS revisions. A message
329 will be printed on the console indicating that ACPI has been disabled
330 automatically and that the user should use a newer BIOS, if possible.
331 If you think ACPI does work on your system and want to override
332 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
336 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
337 separated now. It uses the newly created "_pflogd" user/group
338 combination. If you plan to use pflogd(8) make sure to run
339 mergemaster -p or install the "_pflogd" user and group manually.
342 Network interface cloning has been overhauled. This change will
343 require a recompile of modules using cloning and modification of
344 external ones to the new API. __FreeBSD_version has been bumped
345 to 502119 to mark this change. Additionally, users creating
346 stf(4) interfaces via "ifconfig stf" will need to update their
347 scripts as this will create an interface named "stf" instead of
348 "stf0" and ifconfig will not print "stf0" to stdout.
351 On 20040524, the /etc/rc.d/nsswitch script was modified to
352 automatically create /etc/nsswitch.conf on startup if it did
353 not already exist. Unfortunately, an error in the man page
354 was carried over to the script, resulting in incorrect
355 nsswitch settings. The simplest remedy is to remove both
356 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
357 during the next reboot.
360 The return value of sema_timedwait(9) has been changed to
361 make it consistent with cv_timedwait(9). Be sure to recompile
362 the ips module and any third-party modules which call
366 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
367 Make sure to recompile modules and any userland that makes use of
368 sizeof(struct ifnet). In order to get the altq headers in place
369 please recompile and reinstall world.
372 Splitting kern_thread.c into 2 files (adding kern_kse.c)
373 requires that you re-run config after updating your tree.
376 The MIDI drivers have been removed. Until the new module-friendly
377 ones are merged, remove or comment out midi and seq from your
378 kernel configuration.
381 Due to a new option in ipfw (versrcreach) the ipfw(8) command
382 needs to be recompiled. Normal accept/reject rules without
383 options are not affected but those with options may break until
384 ipfw(8) is recompiled.
387 Due to changes in the callout ABI, kernels compiled after this
388 date may be incompatible with kernel modules compiled prior to
392 The PCI bus power state stuff has been turned on. If this causes
393 problems for your system, please disable it using the tunable
394 hw.pci.do_powerstate=0.
397 The bulk of the pci problems have been fixed, although the floppy
398 drive is still broken.
401 A substantial update to the pci bus resource and power management
402 have been committed. Expect a bumpy ride for a few days until
403 the unanticipated problems have been resolved.
406 Due to changes in the the Yarrow initialization process,
407 /dev/random needs to be fed before operations requiring
408 temp files can succeed in single user mode. This includes
409 running "make installworld". /dev/random may be fed by running
410 "/etc/rc.d/initrandom start" or with 20040415 source by running
411 "/etc/rc.d/preseedrandom".
414 The debug.mpsafenet tunable controls whether the kernel Giant
415 lock is held across the lower levels of the network stack, and
416 by default is turned off. In the few days following 20040322,
417 the behavior of debug.mpsafenet will change such that this
418 tunable controls Giant over all levels of the network stack.
419 If you are currently setting debug.mpsafenet to 1, you should
420 set it back to 0 (the default) again during the change-over.
421 An additional note will be added to UPDATING when sufficient
422 locking is merged to permit this to take place.
425 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
426 64-bits. This is a very major incompatible change, so people
427 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
428 detailed instructions on how to make this upgrade. People
429 upgrading FreeBSD on other platforms can ignore this event.
432 The packet filter (pf) is now installed with the base system. Make
433 sure to run mergemaster -p before installworld to create required
434 user account ("proxy"). If you do not want to build pf with your
435 system you can use the NO_PF knob in make.conf.
436 The pf system consists of the following three devices:
438 device pflog # optional
439 device pfsync # optional
442 If you are having trouble with the libc_r -> libpthread transition
443 (see the 20040130 entry), place the following lines at the top of
446 libc_r.so.5 libpthread.so.1
447 libc_r.so libpthread.so
449 This will cause all programs and libraries linked against libc_r
450 to use libpthread instead.
453 Some sshd configuration defaults have changed: protocol version 1
454 is no longer enabled by default, and password authentication is
455 disabled by default if PAM is enabled (which it is by default).
456 OpenSSH clients should not be affected by this; other clients may
457 have to be reconfigured, upgraded or replaced.
460 The ABIs defined in <resolv.h> and <netdb.h> have been updated
461 to support improved reentrancy. Multi-threaded programs that
462 reference the "_res" or "h_errno" symbols may experience some
463 problems if they are not recompiled. Single-threaded programs
464 should remain unaffected.
467 routed has been updated in the base system from the vendor
468 sources, routed v2.27, from rhyolite.com. This change means that
469 for users who use RIP's MD5 authentication feature, FreeBSD
470 -CURRENT's routed is now incompatible with previous versions
471 of FreeBSD; however it is now compatible with implementations
472 from Sun, Cisco and other vendors.
475 The tcpcb structure has changed and makes a recompile of libkvm
476 and related userland network utilities necessary.
479 The cdevsw structure has changed in two externally visible ways.
480 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
481 Second, the d_version field must be filled in with D_VERSION.
482 Drivers outside the tree will need to be updated.
485 The /etc/rc.d/ttys script has been removed. It is no longer
486 necessary since devfs has been mandatory for some time.
489 libkse has been renamed back to libpthread and is now the
490 default threads library. The gcc -pthread option has also
491 been changed to link to libpthread instead of libc_r. For
492 alpha and sparc64 machines, libkse is not renamed and links
493 are installed so that libpthread points to libc_r. Until
494 the ports system is updated to handle this change, it is
495 recommended that folks install an /etc/libmap.conf(5) that
496 maps libc_r to libpthread. If you have any binaries or
497 libraries linked to libkse, then it is also recommended
498 that you map libkse to libpthread. Anyone that is using
499 nvidia supplied drivers and libraries should use a libmap.conf
500 that maps libpthread to libc_r since their drivers/libraries
501 do not work with libpthread.
504 ULE has entered into its probationary period as the default scheduler
505 in GENERIC. For the average user, interactivity is reported to be
506 better in many cases. On SMP machines ULE will be able to make more
507 efficient use of the available parallel resources. If you are not
508 running it now, please switch over, replacing the kernel option
509 SCHED_4BSD with SCHED_ULE.
512 Move LongRun support out of identcpu.c, where it hardly
513 belongs, into its own file and make it opt-in, not mandatory,
514 depending on CPU_ENABLE_LONGRUN config(8) option.
517 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
518 if the login process is unable to successfully set the
519 process credentials to include all groups defined for the
520 user. The current kernel limit is 16 groups; administrators
521 may wish to check that users do not have over 16 groups
522 defined, or they will be unable to log in.
525 The ACPI module has been reactivated. It is no longer required
526 to compile ACPI support into kernels statically.
529 The statfs structure has been updated with 64-bit fields to
530 allow accurate reporting of multi-terabyte filesystem
531 sizes. You should build world, then build and boot the new kernel
532 BEFORE doing a `installworld' as the new kernel will know about
533 binaries using the old statfs structure, but an old kernel will
534 not know about the new system calls that support the new statfs
536 Note that the backwards compatibility is only present when the
537 kernel is configured with the COMPAT_FREEBSD4 option. Since
538 even /bin/sh will not run with a new kernel without said option
539 you're pretty much dead in the water without it. Make sure you
540 have COMPAT_FREEBSD4!
541 Running an old kernel after a `make world' will cause programs
542 such as `df' that do a statfs system call to fail with a bad
543 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
544 that cfsd (ports/security/cfs) needs to be recompiled after
545 these changes are installed.
547 ****************************DANGER*******************************
549 DO NOT make installworld after the buildworld w/o building and
550 installing a new kernel FIRST. You will be unable to build a
551 new kernel otherwise on a system with new binaries and an old
555 Some netgraph string length constants have been changed. This
556 change requires the netgraph kernel modules and all netgraph
557 userland components to be in sync. Especially users who require
558 netgraph to boot need to make sure to have world and kernel in
559 sync before rebooting.
562 Hyperthreading logical CPU's are no longer probed by default
563 when using the MP Table. If ACPI is being used, then logical
564 CPUs will be probed if hyperthreading is enabled in the BIOS.
565 If ACPI is not being used and hyperthreading is enabled in the
566 BIOS, logical CPUs can be enabled by building a custom kernel
567 with the option MPTABLE_FORCE_HTT enabled.
570 The i386 APIC_IO kernel option has been replaced by
571 'device apic'. The ACPI module has also been temporarily
572 disabled, so ACPI must be statically compiled into your
573 kernel using 'device acpi' if you wish to use the ACPI driver.
576 The API and ABI of struct ifnet have been changed by removing
577 the if_name and if_unit members and replacing them with
578 if_xname, if_dname, and if_dunit. All network drivers and most
579 userland programs which include net/if_var.h must be updated
580 and recompiled. __FreeBSD_version has been bumped to 501113 to
584 Changes to the cdevsw default functions have been made to remove
585 the need to specify nullopen() and nullclose() explicitly.
586 __FreeBSD_version bumped to 501110.
589 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
590 mount_cd9660(8) need to be in sync with kernel.
593 Fix a bug in arplookup(), whereby a hostile party on a locally
594 attached network could exhaust kernel memory, and cause a system
595 panic, by sending a flood of spoofed ARP requests. See
596 FreeBSD-SA-03:14.arp.
599 A change to /etc/defaults/rc.conf now causes inetd to be started
600 with `-C 60' if it is not overridden in /etc/rc.conf. This
601 causes inetd to stop accepting connections from an IP address
602 that exceeds the rate of 60 connections per minute.
605 The following rc.d scripts have been removed and should be
606 deleted from your installation: atm2.sh atm3.sh devdb
607 localdaemons network1 network2 network3. Depending on when
608 you last updated world and used mergemaster(8) you may or
609 may not have problems during the rc boot sequence. The simplest
610 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
611 The atm2.sh atm3.sh and devdb scripts were removed some time
612 ago, so depending on when you installed -CURRENT these scripts
613 may or may not exist on your system.
616 ATAng has been committed. You need to build world as sys/ata.h
617 has changed, and userland atacontrol depends on it.
618 If you use ATA SW raids you need "device ataraid" in your
619 kernel config file, as it is no longer pulled in automatically.
622 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
623 Among other things, this changes the device enumeration to be
624 closer to Solaris. Be aware that, this can even cause the machine
625 to not boot without manual intervention before the fstab is adjusted.
628 All current USB and Firewire quirks in da(4) have been deprecated
629 and will be removed for 5.2. If this causes failure for your
630 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
631 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
632 so the quirk can be re-enabled.
635 Problems with entry 20030714 have been corrected and no known issues
636 with /rescue and -j exist for host systems after this point in time.
639 FPU-less support has been removed from FreeBSD. Chances are you won't
640 notice. 386+387 support should still work after this change, but
641 it is now a minimum requirement for the i386 port that you have real
645 Some people are having problems with changes related to /rescue.
646 If you are building -j N, you will need to define NO_RESCUE. Others
647 will need to define it if /rescue has issues with their environment.
648 People should report those issues to current@.
651 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
652 across this point. Further, it might be a good idea to remove
656 Remove deprecated locale names and transition period code
657 for them, finishing switching to the new scheme. Check your
658 LANG environment variable.
661 CCD has been changed to be a fully GEOMified class. Kernel
662 and ccdconfig(8) needs to be in sync, this is particularly
663 important to remember beforehand if your source tree is on
664 a ccd device. Consider making a copy of the old ccdconfig
665 into /boot/kernel.good or wherever you keep your backup
669 There was a small window in which sed(1) was broken. If you
670 happen to have sed(1) installed during that window, which is
671 evidenced by an inability to build world with the failure
672 given below, you need to manually build and install sed(1)
673 (and only sed(1)) before doing anything else. This is a one-
674 time snafu. Typical failure mode:
676 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
677 targmatch.h:7:1: null character(s) ignored
678 targmatch.h:12:1: null character(s) ignored
679 targmatch.h:16:1: null character(s) ignored
682 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
683 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
684 usr.bin/sed/process.c).
687 Kerberos 5 (Heimdal) is now built by default. Setting
688 MAKE_KERBEROS5 no longer has any effect. If you do NOT
689 want the "base" Kerberos 5, you need to set NO_KERBEROS.
692 groff has been updated. If you try to do a buildworld and
693 get an infinite loop in troff, update to May 4th or newer. If you
694 have a newer kernel than userland, you may need to set the OSRELDATE
695 to 500110 in your environment before starting a buildworld.
698 The old rc system has been removed. Please report any problems
699 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
700 Your personal versions of these files will not be removed, so you can
701 continue to use them. However, you should take great care when updating,
702 especially when using mergemaster, since the compatibility code that
703 utilizes these old scripts has also been removed.
706 A bug has been fixed in /dev/devctl which would cause devd
707 to hang on boot, were it not for a workaround in devd. The
708 work around in devd will be removed around 20030507. You
709 have until then to upgrade your kernel before updating
710 userland. In general, you should have a userland and
711 kernel that's in sync with each other. However, given the
712 effects of this bug (hang on boot when starting devd), some
716 Alphas with libc from between 20030312 and 20030329 exhibit
717 floating point exceptions (FPEs), most notably in awk(1)
718 while upgrading the system through a buildworld.
720 So, to successfully upgrade your Alpha, you must either
721 downgrade your libc.so to a pre-20030312 version, or update
722 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
723 to CFLAGS, then forcibly rebuild and install libc:
725 cd /usr/src/lib/libc && \
726 make cleandir && make obj && \
727 make -DNOMAN -DNOPROFILE all && \
728 make -DNOMAN -DNOPROFILE install
731 sendmail 8.12.7 has been imported. It has one important
732 change for IPv6 users. The default submit.mc now uses
733 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
734 used to connect to the MTA. Users on IPv6-only machines
735 will need to edit /etc/mail/submit.mc appropriately.
738 NODEVFS option has been removed and DEVFS thereby made standard.
739 This makes all references to MAKEDEV obsolete, and they should
740 be removed when convenient.
743 The name of the device for the ofw console has changed, sparc64 users
744 must run mergemaster to update their installed /etc/ttys.
747 The scheduler framework has grown a second scheduler and consequently
748 you must specify one and only one scheduler in your kernel config.
749 The cvs config files have been updated to use the old scheduler
750 which may be selected via 'options SCHED_4BSD'. If you would like
751 to try the new, much more experimental, scheduler please try
752 'options SCHED_ULE' and contribute to the arch@ discussion.
755 A new version of the wi driver has been imported into the tree.
756 One now must have device wlan in the config file for it to operate
759 In addition, there have been some changes to how wi devices are
760 configured for point to point links to bring it more in line
761 with the former way of doing things, as well as compatibility
765 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
766 used an incompatible form of ABI for returning structures and unions
767 which FreeBSD's GCC maintainers were not aware of relative to previous
768 versions of FreeBSD. We have gone back to the ABI for now, and any
769 code compiled which is required to interoperate with other code (not
770 built at the same time) returning structs or unions should be
774 A name change in /etc/netconfig has been reverted to stay
775 compatible with suns TIRPC and also with NetBSD. You need
776 to run mergemaster after make world. A new libc does still work
777 with an outdated /etc/netconfig for some time, but you'll get
778 a warning. This warning will be removed in 20030301.
781 The recent binutils upgrade marks a kernel flag day on
782 sparc64: modules built with the old binutils will not work
783 with new kernels and vice versa. Mismatches will result in
784 panics. Make sure your kernel and modules are in sync.
787 The value of IPPROTO_DIVERT has changed. Make sure to keep
788 your kernel, netstat, natd and any third-party DIVERT
792 Old, compatibility slices have been removed in GEOM kernels.
793 This means that you will have to update your /etc/fstab to
794 not use disk devices of the form /dev/ad0a. Instead, you
795 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
796 partition really is on. The old device names have gone
797 away, so if you use them anywhere else, you must also adjust
798 those uses. (This doesn't affect the disks formatted in
799 the ``dangerously-dedicated'' mode.)
802 Alphas with kernels from between 20020830 and 20021023 and/or
803 rtld (ld-elf.so.1) older than 20021023 may experience problems
804 with groff while doing a buildworld (kernel: "out of memory",
805 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
806 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
808 So, to successfully upgrade your Alpha, you must either
809 upgrade your kernel and rtld first (which might be a bit
810 tricky), or avoid running the bootstrapped groff during the
811 "transitional" buildworld. To avoid running groff during the
812 transitional upgrade run make buildworld with -DNOMAN,
813 -DNO_SHAREDOCS, and -DNO_LPR.
816 gcc has been upgraded to 3.2. It is not all binary compatible
817 with earlier versions of gcc for c++ programs. All c++
818 programs and libraries need to be recompiled.
820 Also, if you encounter g++ issues, rm /usr/include/g++/* before
821 doing an installworld to make sure that stale files are removed.
824 Our /etc/termcap now has all the entries from the XFree86 xterm
825 almost unchanged. This means xterm now supports color by default.
826 If you used TERM=xterm-color in the past you now should use
827 TERM=xterm. (xterm-color will lead to benign warnings).
830 A "bug" in gcc(1) that was hiding warning in system headers was
831 fixed. It's probably time to add -DNO_WERROR to your make line
835 COPY is being deprecated. The 20010530 change was reverted, as
836 it causes far more pain than was expected, and to always compare
837 before installing, please use INSTALL="install -C" again. The
838 -C option is now silently ignored when used with the -d option.
841 Problems with libc_r clients like KDE and GNOME have been resolved.
842 There are still some minor problems with some signals but the
843 system is stable enough for general use again. SMP is less so than UP
844 but each can successfully complete multiple buildworlds.
845 Libkvm needs to be recompiled due to KSE.
848 Now would be a bad time to upgrade. Something in or near the
849 KSE commit totally broke programs using libc_r like KDE and
853 The k5su utility installed as part of Kerberos 5 is no longer
854 installed with the set-user-ID bit set by default. Add
855 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
856 with the set-user-ID bit set.
859 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
860 Unfortunately our native GDB (at version 4.18) does not understand
861 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
862 generated debugging information for our native GDB.
865 Due to the way CVS works, it may not properly update src/contrib/gcc
866 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
867 and then do a cvs update.
870 When exec'ing set[ug]id executables, the kernel now ensures that the
871 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
874 New sendmail startup scripts have been installed to make it
875 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
876 variable sendmail_enable to "NO" no longer prevents any sendmail
877 daemons from starting. Instead, either set sendmail_enable to
878 "NONE" or change mta_start_script to a script for starting
879 an alternative MTA. Setting mta_start_script to "" will
880 also prevent any MTA from being started at boot.
883 UCONSOLE is no longer a valid kernel option.
886 FreeBSD 5.0 DP-1 was basically branched today.
889 Warnings are now errors in the kernel. Unless you are a developer,
890 you should add -DNO_WERROR to your make line.
893 sendmail 8.12.2 has been imported. The sendmail binary is no
894 longer a set-user-ID root binary and the infrastructure to support
895 command line mail submission has changed. Be sure to run
896 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
897 and /etc/mail) and read /etc/mail/README for more details.
899 Due to the import of sendmail 8.12.2, a new user and group are
900 required in order for sendmail to run as a set-group-ID
901 binary. A 'make installworld' will use the new user and group
902 to set the owner and group of /var/spool/clientmqueue and will
903 fail if the new user and group do not exist. The 'smmsp' user
904 and group must be merged from src/etc/group and
905 src/etc/master.passwd before using 'make installworld'.
906 'mergemaster -p' will do this. You may need to install
907 mergemaster before this will work if you are updating from a
908 very old version of current. The updating recipe has changed
912 The preferred configuration method for PAM is now /etc/pam.d/
913 rather than /etc/pam.conf. If you have an unmodified
914 pam.conf, just delete it after your next mergemaster run. If
915 you have local modifications, you can use
916 /usr/src/etc/pam.d/convert.pl to incorporate them into your
919 Please see the following url for more details:
920 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
922 If anyone here is already using the new rc.conf(5) variable
923 networkfs_types, please note that it has changed
924 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
927 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
928 started out its life in the ISDN4BSD project as an offspring
929 from sys/net/if_spppsubr.c, which eventually got a life of its
930 own. All the accumulated features and bug fixes of the i4b
931 version have now been merged back into the base system's
932 version now. The only user-visible change resulting from this
933 is that i4b's sppp(4) interfaces are to be managed with
934 spppcontrol(8) again, since ispppcontrol(8) has been retired
935 as well. (There has never been rc file support for
936 ispppcontrol in -current, but only in -stable. That will be
937 reverted by the time the changes are MFCed.)
940 The fdc(4) driver has been updated and now automatically
941 recognizes media in `standard' formats (like 1440 KB and
942 720 KB for a 3.5" high-density drive) when accessing the
943 default device node (e. g. /dev/fd0). The old variety of
944 floppy device nodes /dev/fd*.* is no longer present by
945 default, devices can be created (in DEVFS) on demand. They
946 will need to be customized then for `odd' densities using
950 The bugs in procfs' debugging support code have been fixed,
951 and truss(1) now works again.
954 Daily security checks have been split out to use the periodic(8)
955 scripts. Some change in configuration may be necessary. Please
957 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
961 sos added VCD/SVCD support to ata driver and that needs the
962 kernel and burncd to be in sync.
965 The procfs pseudo-filesystem has now been converted to use the
966 pseudofs framework. If you have 'options PROCFS' in your
967 kernel config, you'll need to add 'options PSEUDOFS' if it's
970 This change temporarily breaks truss(1); use ktrace(1) instead
971 until the issue has been resolved.
974 A security hole in OpenSSH involving `UseLogin yes' has been
978 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
979 after this date. You need to do this only once.
982 Most of the awk issues have been resolved. Some rough
983 edges may be left, but for the most part things should be
984 back to "normal." For CURRENT's usual definition of "normal."
987 Awk has been upgraded to the one true awk from bell labs. Expect
988 choppy waves in the upgrade process.
991 The asr driver problem has been resolved.
994 Due to changes in other parts of the system, the asr driver
995 now causes the system to panic on boot. Do not use it pending
996 correction. Comment it out of any kernel config file that you
997 try to use from this date forward.
1000 When crossbuilding, use TARGET=xxx where you used to use
1001 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
1002 unless you are changing both of them. To cross build pc98 on
1003 an alpha, for example, you need to set TARGET=pc98 and
1007 The kernel interface that burncd depends on has changed.
1008 You must recompile both the kernel and userland applications
1012 When crossbuilding, please set TARGET_ARCH rather than
1013 MACHINE_ARCH to indicate the target. In the future, one will
1014 set TARGET_MACHINE where you set MACHINE now. At the moment,
1015 setting MACHINE alone for same MACHINE_ARCH machines works
1016 (eg, you can build pc98 on an i386 machine and vice versa).
1019 Some weird problems result from using ACPI on some machines.
1020 To disable ACPI you can add
1021 hint.acpi.0.disabled="1"
1022 to /boot/loader.conf (or by putting set X=Y at the boot
1023 loader "ok" prompt).
1025 Alternatively, you can remove it from /boot/kernel/acpi.ko
1026 or use the MODULES_OVERRIDE function in your kernel config
1027 file and not list acpi in that list.
1030 The buildworld has been fixed. You may need to install
1031 the 4.x compatibility libraries for some old binaries
1032 to work. Add COMPAT4X=true to your /etc/make.conf to
1033 get them installed on every installworld, or execute the
1034 following to get them installed only once:
1035 cd src/lib/compat/compat4x.<arch>
1037 You will see ``__stdoutp undefined'' until you do this.
1040 There's a bug in the world build process. The cross-tools
1041 are build with the NEW headers, but the OLD libc.a. This
1042 leads to all kinds of problems with the new libc. A temporary
1043 workaround is to add
1044 CFLAGS="-O -pipe -D_OLD_STDIO"
1045 before building world when upgrading from 4.x to current. This
1046 can be removed afterwards.
1048 A proper fix to the buildworld target is needed.
1051 Peter has committed his new kthread nfs client/server code.
1052 NFS may be unstable after this date.
1055 KSE has hit the tree. Lots of things are now different in
1056 the kernel. While a few problems were introduced in the
1057 initial commit, most of the major ones have been found and
1061 In OLDCARD, CardBus bridges appear to be stable. The work
1062 arounds described in the 20010604 entry are now no longer
1063 necessary and will be ignored. Most insert/remove problems
1064 have been rectified around this date.
1067 named now runs as user bind and group bind rather than as
1068 root. If named_enable is set to YES in /etc/rc.conf, ensure
1069 that user bind is available in /etc/passwd (using vipw(8))
1070 and that group bind is available in /etc/group. Also make
1071 sure that user or group bind has read (and not write)
1072 permission for your name server configuration and that it
1073 has read and write permission for your slave zone files and
1076 If you wish to continue to run named as root (a less secure
1077 alternative), add a line to /etc/rc.conf saying
1082 The PAM libraries have had an API upgrade that is beyond
1083 the ability of the shared library major number to handle.
1084 It is manifested by PAM-using ports dumping core. The
1085 solution is to rebuild those ports.
1088 The kernel compile module has moved from src/sys/compile/FOO
1089 to src/sys/${MACHINE}/compile/FOO.
1092 The pccard modem issue from 20010613 has been corrected.
1093 OLDCARD support is still a little weak in -current. slot 1 is
1094 known not to work on some TI based cardbus bridges. Some
1095 cardbus bridges do not properly detect insert/removal events.
1096 IRQ configuration needs more safety belts.
1099 Softupdates problems have been corrected.
1102 Peter ripped out the linkerset support. You must, as always,
1103 rerun config after you cvsup if you are using the traditional
1104 kernel building methods.
1107 pccard modems may not work with current after 20010604 date. Some
1108 do, others result in panics. *MAKE*SURE* that you update your
1109 config and /etc/rc.conf ala the 20010604 entry, or you will have
1110 problems (this issue will be fixed, it just hasn't been yet).
1113 SOFTUPDATES seem to be broken since the middle of May or so. Do not
1114 use them in current. You can disable softupdates on all mounted
1115 partitions, or remove SOFTUPDATES the kernel config file.
1118 After Peter's commits to the hints code, people have been noticing
1119 that certain devices are attached (or try to) twice. This is due
1120 to having both static hints as well as a /boot/device.hints. To
1121 work around this issue, please use only one or the other mechanism
1122 until this bug is fixed.
1124 Please note that a feature of config is that if you have config
1125 file FOO and FOO.hints, it automatically adds FOO.hints to the
1126 hints.c file, whether you want it to or not.
1129 Locale names have changed to match other systems better.
1132 pccard support for pci cards has been committed. You must change
1133 your /etc/pccard.conf irq lines. It must match the irq used by
1134 pcic device. Interrupt storms may result if you fail to do this.
1135 Interrupt storms look a lot like a hang.
1137 You must also install a new pccardd, otherwise you will get an
1138 interrupt storm at card reset time (just after it tells you what
1141 pccardd_flags="-I" is necessary for the time being. It tells pccardd
1142 not to ask the kernel if the interrupt is really free or not before
1143 using it. You can either change the /etc/pccard.conf irq lines to
1144 match pcic, or add "-i X" to the pccardd_flags.
1147 INSTALL=install -C is being deprecated. If you want to do this,
1148 use COPY=-C instead. The former method will be supported for only
1149 a limited time. If you see
1151 install: warning: the -d and -C options may not be specified together
1153 in your makeworld, then you need to migrate towards using
1157 It appears that vm is now stable enough to use again. However,
1158 there may be other problems, so caution is still urged. alpha
1159 definitely is in bad shape.
1162 Minor repo damage has happened. This may cause problems
1163 with cvsup of ports. If you get errors, please see
1164 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1165 at the bottom for details on a workaround. The error message
1167 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1170 Vm and/or swapping are busted on -current. Please be patient.
1173 pccard has had much reorganizational work done to it over
1174 the past few days. Everything should still work, but if
1175 not, please contact imp@freebsd.org.
1178 ata ioctl changed. Make sure to recompile both kernel and
1179 userland at the same time.
1182 New ncurses imported.
1185 DEVFS is now opt out, not opt in. Barring major problems, this
1186 will be the only way to go starting July 1.
1189 OpenSSH has been updated to 2.9. Some defaults are different,
1190 including RhostsRSAAuthentication, which changes from yes to no.
1193 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1196 Building perl was broken at 02:25:25 PDT.
1199 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
1200 go back in the water.
1203 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
1204 this date, but before the correction date.
1207 old fsck and new kernel interactions appear to have been fixed.
1210 fsck and the kernel were changed to handle some optimizations
1211 to directory layout. This breaks backward compatibility.
1212 Update only if you understand that you must not use the old
1213 fsck with the new kernel ever.
1216 fsck has changed the meaning of the pass column in /etc/fstab.
1217 Please see the cvs commit to fsck.8 or the fsck.8 man page for
1218 details. It is unclear if changes to /etc/fstab are necessary.
1221 portmap had changed name to rpcbind for maximum POLA in your
1222 current world. /etc/hosts.{allow,deny} needs changes. nfs and
1223 other rpc based programs that rely on portmapper will not work
1224 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
1227 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1228 and ATA_ENABLE_TAGS are no longer kernel options. They have
1229 been replaced by tunables. See ata.4 for details.
1232 The fxp driver was converted to use miibus. If you compile
1233 fxp into your kernel statically, you will need to add miibus.
1236 The wi device now defaults to BSS (infrastructure) mode
1240 /dev/urandom should be a symbolic link to /dev/random now.
1241 Users of current not using DEVFS need to run MAKEDEV std.
1242 ssh might not work if you don't.
1245 The ed driver has been updated. It now allows mii attachments,
1246 which means that you must include the miibus in your kernel if
1247 you use the ed driver.
1250 The problems with libc have been corrected. It is now mostly
1251 safe to go back into the water.
1254 The size of FILE was changed. This breaks upgrading. If
1255 you must upgrade, be prepared for pain. It also breaks almost
1256 all binaries that you've compiled on -current. You are warned
1257 that before upgrading would be a good time to do a level 0
1258 dump of your system. No, really, I mean it this time.
1260 To get to the new system, you'll need to use the following
1261 workaround. Hopefully this can be sorted out so that we
1262 don't have to move this to the updating section.
1264 To get around the installworld problem, do:
1265 # cd /usr/src/usr.bin/sed
1269 If that doesn't work, then try:
1270 # make -k installworld
1274 DEVFS is now the default. If you use vinum, make sure that you
1275 do not include devfs in your kernel as problems result.
1278 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1279 Remove them from your config.
1282 ****************************** WARNING ******************************
1283 buildkernel has been changed slightly
1284 ****************************** WARNING ******************************
1285 KERNCONF replaces the variable KERNEL for buildkernel. You
1286 should update your scripts and make.conf accordingly.
1289 config has changed to allow DEV_FOO as a replacement for NFOO.
1290 This requires a new config to build correctly.
1293 The kernel option I386_CPU is now mutually exclusive with the
1294 other cpu types. If you have an i386 system, be sure that it
1295 only had this line. Remove it for all other configurations.
1298 Changes to the kernel require it and burncd be in sync.
1301 Everyone who has hw.sndunit set to something in
1302 /etc/sysctl.conf, it is now hw.snd.unit.
1305 ex and vi were broken by some changes to sys/queue.h. If you
1306 have a bad vi, you will see make buildworld fail with a core
1307 dump while building termcap. You can work around this problem
1308 by adding -k to your make buildworld. This will cause the
1309 build to complete and install a new vi. Once that's done, you
1310 can rebuild again without the -k to pick up anything that
1311 might have been ignored by the -k option.
1313 Others have suggested that you can just rebuild libc if your
1314 vi/ex is dynamically linked, but I've not received any reports
1318 There have been some changes to libcrypt in -current. The
1319 libscrypt/libdescrypt symlink silliness is gone and the installed
1320 libcrypt is fully functional. Be aware of this.
1323 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1324 now require the addition of flag 0x80000 to their config line
1325 in pccard.conf(5). This flag is not optional. These Linksys
1326 cards will not be recognized without it.
1329 Important new FreeBSD-version stuff: PAM support has been worked
1330 in, partially from the "Unix" OpenSSH version. This requires
1331 adding the following in pam.conf:
1333 sshd auth sufficient pam_skey.so
1334 sshd auth required pam_unix.so try_first_pass
1335 sshd session required pam_permit.so
1338 cvs updated to 1.11.
1341 The random device needs more entropy, so you need to make sure
1342 that you've run mergemaster to get a /etc/rc which will seed
1343 /dev/random. If you don't and the system hangs after ldconfig,
1344 then banging on the keyboard randomly until it unhangs is one
1348 ****************************** WARNING ******************************
1349 Sendmail has been updated.
1350 ****************************** WARNING ******************************
1351 o mail.local(8) is no longer installed as a set-user-id binary.
1352 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1354 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1356 o Now using sendmail's version of vacation(1).
1357 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1358 in /usr/share/sendmail/cf.
1359 o sendmail.cw changed to local-host-names
1361 More details can be found at
1362 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1365 The ports tree's new layout is in place. Be sure to update
1366 your entire ports tree, or you will have problems.
1369 The perl build procedure no longer installs miniperl, nor uses
1370 the installed miniperl. It is recommended that you delete
1374 This weekend the ports tree will be updated to a new layout.
1375 It will be in an inconsistent state until noted in the UPDATING
1376 file, or with asami-san's message to the relevant mailing
1377 lists. With this new layout, you'll need to update the whole
1378 tree for anything to work.
1381 There was a change in the passwd format. Need more information.
1384 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1385 place. Please update boot loader (not the boot blocks) at the
1386 same time as your kernel.
1389 The new pmtimer device is necessary for laptops. Failure to
1390 include the device will cause suspended laptops losing time
1391 when they resume. Include
1393 in your config file and
1394 hint.pmtimer.0.at="isa"
1395 to your /boot/device.hints file.
1398 The random device has been turned into a (pseudo-)device,
1399 rather than an option. The supplied kernel config files have
1400 been updated. You will need to do something similar in your
1401 own kernel config file.
1406 If you prefer to load the loadable module, you need to do
1410 The random device module has been renamed from randomdev.ko to
1411 random.ko. You will need to edit your /boot/loader.conf to
1412 reflect this if you load this module at boot time.
1413 The line should read:
1417 The SMPNG commit has happened. It should work, but if it
1418 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1419 to be a variety of minor issues. Please see 20000905 to make
1420 sure you don't have model loading problems which might at
1421 first blush appear related to SMP.
1424 nsswitch has been imported from NetBSD. Among other things,
1425 this means that /etc/host.conf is no longer used. See
1426 nsswitch.conf(5) instead. Note that at boot time rc.network
1427 will attempt to produce a new nsswitch.conf file for you if you
1428 don't have one, and you have host.conf.
1431 The ucred structure changed size. This breaks the interface
1432 that mountd uses. Trying to use an older mountd with a newer
1433 kernel guarantees a panic. This means that you need to use
1434 kernels newer than today only with matching mountd, but you
1435 needed to do that anyway with the boot loader changes.
1438 The boot loader has been updated. The new default kernel is
1439 now /boot/kernel/kernel.ko. The new default module location
1442 You *MUST* upgrade your boot loader and kernel at the same time.
1443 The easiest way to do this is to do the buildworld/buildkernel/
1444 installkernel/installworld dance.
1446 Furthermore, you are urged to delete your old /modules directory
1447 before booting the new kernel, since kldload will find stale
1448 modules in that directory instead of finding them in the correct
1449 path, /boot/kernel. The most common complaint that this cures
1450 is that the linux module crashes your machine after the update.
1452 if [ ! -d /boot/kernel.old ]; then
1453 mv /modules.old /boot/kernel.old
1454 chflags noschg /kernel.old
1455 mv /kernel.old /boot/kernel.old/kernel.ko
1456 chflags schg /boot/kernel.old/kernel.ko
1460 A new issue with the sendmail upgrade has come to light.
1461 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1462 incorrectly install the default aliases in /etc/mail rather than
1463 move the old one from /etc. So you'll need to manually move the
1464 file, create a symbolic link, remove the old /etc/aliases.db and
1465 run newaliases. For safety sake, you should stop sendmail
1466 while doing this and run the upgrade when locally sourced email
1467 is not likely to be generated.
1470 /boot/device.hints is now required for installkernel to
1471 succeed. You should copy GENERIC.hints for your architecture
1472 into /boot/device.hints. If and only if you compile hints
1473 into your kernel, then this file may be empty. Please note,
1474 if you have an empty or missing /boot/device.hints file and
1475 you neglected to compile hints into your kernel, no boot
1476 messages will appear after the boot loader tries to start the
1480 If you do NOT have ``options RANDOMDEV'' in your kernel and
1481 you DO want the random device then add randomdev_load="YES" to
1485 suidperl is now always built and installed on the system, but
1486 with permissions of 511. If you have applications that use
1487 this program, you are now required to add ENABLE_SUIDPERL=true
1488 to /etc/make.conf. If you forget to do this,
1489 chmod 4511 /usr/bin/suidperl
1490 will fix this until the next build.
1493 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1494 visible changes that may immediately affect your configuration
1496 - New default file locations from src/contrib/sendmail/cf/README
1497 - newaliases limited to root and trusted users
1498 - MSA port (587) turned on by default
1499 - New queue file naming system so can't go from 8.11 -> 8.9
1500 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1501 - FEATURE(`nullclient') is more full featured
1502 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1503 - mail.local FreeBSD-only -b option changed to -B
1504 - See src/contrib/sendmail/RELEASE_NOTES for more info
1507 suidperl (aka sperl) is no longer build by default. You must
1508 specifically define BUILD_SUIDPERL to "true" for it to be build.
1509 Furthermore, we recommend that you remove /usr/bin/sperl* and
1510 /usr/bin/suidperl files from your system unless you have a
1511 specific use for it.
1514 Networking defaults have been tightened. Anybody upgrading
1515 /etc/defaults/rc.conf needs to add the following lines to
1516 /etc/rc.conf if they want to have the same setup
1517 afterwards (unless the variables already are set, of course):
1518 # Enable network daemons for user convenience.
1520 portmap_enable="YES"
1521 sendmail_enable="YES"
1524 If you have null_load="YES" in your /boot/loader.conf, you
1525 will need to change that to nullfs_load="YES".
1528 The "installkernel" target has changed slightly. Now even if
1529 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1530 it will install the MYKERNEL file (built with the buildkernel
1531 target) as /kernel rather than /MYKERNEL. Those who have
1532 updated their /boot/loader.conf files to point to /MYKERNEL
1533 should remove that entry or perform manual rename of /kernel
1537 If you use CVSUP or CTM to get CVS trees, AND you used to get
1538 the old crypto files from internat.freebsd.org AND you check
1539 out files from the CVS tree with the cvs command, please read
1540 http://people.freebsd.org/~imp/internat.txt
1541 for details on potential problems that you might have and how
1544 If you are merely a mirror, or don't answer yes to each of the
1545 clauses above, you needn't worry.
1548 /etc/security has been updated to print the inode number of
1549 setuid programs that have changed. You will see a large spike
1550 in the number of changed programs the first time when you run
1551 mergemaster to get a new /etc/security.
1554 /dev/random now has good entropy collection (from the keyboard
1555 and sysmouse drivers). Please ensure that either `options
1556 RANDOMDEV' is present in your kernel config file or that
1557 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1558 not have the /dev/random driver, OpenSSL (and consequently
1559 lots of crypto tools (like SSH)) will fail with strange
1560 errors. (see below, 20000624).
1562 FreeBSD-current is safe again to run Crypto.
1565 phk made the malloc default options AJ. This may slow things
1566 down and uncover other latent bugs in the code. If you need to
1567 run at full speed, you can disable this by doing the following:
1568 ln -s aj /etc/malloc.conf
1571 libftpio's version was accidentally bumped a few days ago. This
1572 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1573 before doing your next buildworld/installworld pair. It certainly
1574 won't hurt to remove it before the update procedure. It will
1575 break fetch until a new one is built, but ftp can be used in the
1579 The crypto packages have changed for the cvsup. This has been done
1580 in a backward compatible way, but the old packages will go away at
1581 some point in the future. Look at /usr/share/examples/cvsup for
1585 With the new sys/modules/sound/drivers/*, you will need to
1586 set SYSDIR until you do an installworld after July 7th.
1589 rc.shutdown and rc will now call the rc.d scripts with start
1590 or stop. This may cause some harmless warnings from older
1591 rc.d scripts that haven't been updated.
1594 The libfetch based version of fetch has gone into the tree.
1595 Minor problems may result on some of the less popular sites,
1596 which should be reported to des@freebsd.org.
1599 From approximately this date forward, one must have the crypto
1600 system installed in order to build the system and kernel.
1601 While not technically strictly true, one should treat it as
1602 required and grab the crypto bits. If you are grabbing CVS
1603 trees, src-all and cvs-crypto should be treated as if they
1604 were required. You should check with the latest collections
1605 to make sure that these haven't changed.
1608 Mark Murray just committed the first parts of a cleanup of
1609 /dev/zero, et al. This is also cleaning up /dev/random.
1610 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1611 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1612 until Mark can merge in the fixes to this work in progress.
1613 openssh and openssl should not be used to generate keys from this
1614 date to the completion of the work.
1616 If you must operate at this reduced level of security, add '
1617 options RANDOMDEV' to your kernel or modload the randomdev
1618 module. You may also need to copy a new MAKEDEV to /dev and
1619 recreate the random and urandom devices.
1622 The license on the softupdates is now a standard 2 clause
1623 BSD license. You may need to remove your symbolic links
1624 that used to be required when updating.
1627 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1628 the config file update procedure.
1629 http://people.freebsd.org/~imp/config-upd.html
1630 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1631 isn't buildable. However, you can generate a LINT file:
1632 cd /sys/<ARCH>/conf && make LINT
1635 Binutils 2.10 have hit the tree, or will shortly. As soon
1636 as they do, the problem noted in 20000522 will be resolved and
1637 that workaround will no longer be required.
1640 phk removed the compatibility creation of wd devices in the
1641 ad driver. If you haven't done so already, you must update
1642 your fstab, etc to use the ad devices instead of the wd
1645 In addition, you'll need to update your boot blocks to a
1646 more modern version, if you haven't already done so. Modern
1647 here means 4.0 release or newer (although older releases
1651 Peter took an axe to config(8). Be sure that you read his mail
1652 on the topic before even thinking about updating. You will
1653 need to create a /boot/device.hints or add a hints directive
1654 to your config file to compile them in statically. The format
1655 of the config file has changed as well. Please see GENERIC or
1656 NEWCARD for examples of the new format.
1658 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1659 says that it has been fixed, assume that must use the hints mechanism
1660 in the loader if you need to use a machine with very old ISA cards
1664 A new set of binutils went into the tree today. Anybody
1665 building a kernel after this point is advised that they need
1666 to rebuild their binutils (or better yet do a
1667 buildworld/installworld) before building a new kernel.
1669 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1670 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1671 is recommended that you don't set this option until the problem
1675 The ethernet drivers were all updated to clean up the BPF handling.
1678 The problems with boot blocks on the alphas have been corrected.
1679 This will require some care in updating alphas. A new libstand
1680 is requires for the boot blocks to build properly.
1683 Recompile all kld modules. Proper version dependency info
1687 Modules have been disconnected from the buildworld tree and
1688 connected to the kernel building instead.
1691 You may need to build gperf
1692 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1693 when upgrading from 4.0 -> current. The build system now uses
1694 an option only in -current.
1697 The method that we brand ELF binaries has changed to be more
1698 acceptable to the binutils maintainers. You will need to
1699 rebrand your ELF binaries that aren't native. One problem
1700 binary is the Linux ldconfig. After your make world, but
1701 before you reboot, you'll need to issue:
1702 brandelf -t Linux /compat/linux/sbin/ldconfig
1703 if you have Linux compatibility enabled on your machine.
1706 If you have really bad/marginal IDE drives, you may find they
1707 don't work well. Use pio mode instead. The easiest way to
1708 cope if you have a problem combination is to add:
1709 /sbin/sysctl hw.ata.ata_dma=0
1710 to the start of /etc/rc.conf.
1713 The ISA and PCI compatibility shims have been connected to the
1714 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1715 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1716 include the appropriate option in your kernel config. Drivers
1717 using the shims should be updated or they won't ship with
1718 5.0-RELEASE, targeted for 2001.
1721 We've entered the traditional post release dumping party.
1722 Large kernel changes are being committed and are in the
1723 works. It is important to keep the systems' klds and kernel
1724 in sync as kernel interfaces and structures are changing.
1725 Before reporting kernel panics, make sure that all modules
1726 that you are loading are up to date.
1729 If you are upgrading from an older version of FreeBSD, you
1730 need to update your boot blocks as well. 'disklabel -B ad0'
1731 will do the trick. This isn't critical until you remove your
1732 wd device entries in /dev, at which point your system will not
1736 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1737 to upgrade to 4.0 from 3.x.
1741 # NOTE: 5.x below applies to 6.0-currrent as well, for the
1742 # momemnt. 4.any -> 5.any upgrade support will remain in
1743 # place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1744 # 6.0-current upgrade path will require moving through 5.3
1749 Avoid using make -j when upgrading. From time to time in the
1750 past there have been problems using -j with buildworld and/or
1751 installworld. This is especially true when upgrading between
1752 "distant" versions (eg one that cross a major release boundary
1753 or several minor releases, or when several months have passed
1754 on the -current branch).
1756 Sometimes, obscure build problems are the result of environment
1757 poisoning. This can happen because the make utility reads its
1758 environment when searching for values for global variables.
1759 To run your build attempts in an "environmental clean room",
1760 prefix all make commands with 'env -i '. See the env(1) manual
1761 page for more details.
1765 If you are updating from a prior version of FreeBSD (even one just
1766 a few days old), you should follow this procedure. With a
1767 /usr/obj tree with a fresh buildworld,
1768 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1769 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1771 To just build a kernel when you know that it won't mess you up
1772 --------------------------------------------------------------
1773 This assumes you are already running a 5.X system. Replace
1774 ${arch} with the architecture of your machine (e.g. "i386",
1775 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1777 cd src/sys/${arch}/conf
1778 config KERNEL_NAME_HERE
1779 cd ../compile/KERNEL_NAME_HERE
1784 If this fails, go to the "To build a kernel" section.
1786 To rebuild everything and install it on the current system.
1787 -----------------------------------------------------------
1788 # Note: sometimes if you are running current you gotta do more than
1789 # is listed here if you are upgrading from a really old current.
1791 <make sure you have good level 0 dumps>
1792 <maybe fix /etc/fstab> [7]
1794 make kernel KERNCONF=YOUR_KERNEL_HERE
1796 <reboot in single user> [3]
1797 src/etc/rc.d/preseedrandom [10]
1804 To cross-install current onto a separate partition
1805 --------------------------------------------------
1806 # In this approach we use a separate partition to hold
1807 # current's root, 'usr', and 'var' directories. A partition
1808 # holding "/", "/usr" and "/var" should be about 2GB in
1811 <make sure you have good level 0 dumps>
1814 <maybe newfs current's root partition>
1815 <mount current's root partition on directory ${CURRENT_ROOT}>
1816 make installworld DESTDIR=${CURRENT_ROOT}
1817 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1818 cp src/sys/${ARCH}/conf/GENERIC.hints \
1819 ${CURRENT_ROOT}/boot/device.hints # as needed
1820 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1821 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1822 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1823 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1824 <reboot into current>
1825 <do a "native" rebuild/install as described in the previous section>
1826 <maybe install compatibility libraries from src/lib/compat>
1830 To upgrade in-place from 4.x-stable to current
1831 ----------------------------------------------
1832 # 5.x uses more space than 4.x. Also, the location of kernel
1833 # modules has changed. If you are installing 5.x onto a 4.x
1834 # system, you'll need about 30MB of free disk space on your /
1835 # partition. If you have less than this, you may encounter difficult
1836 # to back out of problems with this procedure. If /tmp is on
1837 # the / partition, you may want to completely remove all its content
1838 # before upgrading, as this can be a common source of shortage of
1841 <make sure you have good level 0 dumps>
1842 <maybe fix /etc/fstab> [7]
1844 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1845 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1846 cd sys/boot ; make STRIP="" install [6]
1848 <reboot in single user> [3]
1849 src/etc/rc.d/preseedrandom [10]
1851 rm -rf /usr/include/g++
1856 Make sure that you've read the UPDATING file to understand the
1857 tweaks to various things you need. At this point in the life
1858 cycle of current, things change often and you are on your own
1859 to cope. The defaults can also change, so please read ALL of
1860 the UPDATING entries.
1862 Also, if you are tracking -current, you must be subscribed to
1863 freebsd-current@freebsd.org. Make sure that before you update
1864 your sources that you have read and understood all the recent
1865 messages there. If in doubt, please track -stable which has
1866 much fewer pitfalls.
1868 [1] If you have third party modules, such as vmware, you
1869 should disable them at this point so they don't crash your
1872 [2] If you have legacy ISA devices, you may need to create
1873 your own device.hints to reflect your unique hardware
1876 [3] From the bootblocks, boot -s, and then do
1881 adjkerntz -i # if CMOS is wall time
1882 Also, when doing a major release upgrade, it is required that
1883 you boot into single user mode to do the installworld.
1884 For the 4.x -> 5.x upgrade, you will also see many messages about
1885 needing to recompile your userland. These are harmless and can
1886 be ignored while you proceed to the next step.
1888 [4] Note: This step is non-optional. Failure to do this step
1889 can result in a significant reduction in the functionality of the
1890 system. Attempting to do it by hand is not recommended and those
1891 that pursue this avenue should read this file carefully, as well
1892 as the archives of freebsd-current and freebsd-hackers mailing lists
1893 for potential gotchas.
1895 [5] Usually this step is a noop. However, from time to time
1896 you may need to do this if you get unknown user in the following
1897 step. It never hurts to do it all the time. You may need to
1898 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1899 install) after the buildworld before this step if you last updated
1900 from current before 20020224 or from -stable before 20020408.
1902 [6] 4.x boot loader can be used to boot a 5.x system, however
1903 it is difficult to do that at best. If you wish to try, then
1904 you should interrupt the boot and at the ok prompt type:
1906 ok boot /boot/kernel/kernel
1907 If this fails to work, you must install a new boot loader as
1910 [7] Before you upgrade, please make sure that you are not using
1911 compatibility slices. These are device names of the form /dev/ad0a
1912 without the actual slice name. These will break with 5.x and newer.
1913 You generally must update these entries to use the post FreeBSD
1914 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1917 [8] In order to have a kernel that can run the 4.x binaries
1918 needed to do an installworld, you must include the COMPAT_FREEBSD4
1919 option in your kernel. Failure to do so may leave you with a system
1920 that is hard to boot to recover.
1922 Make sure that you merge any new devices from GENERIC since the
1923 last time you updated your kernel config file.
1925 [9] When checking out sources, you must include the -P flag to have
1926 cvs prune empty directories.
1928 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1929 "?=" instead of the "=" assignment operator, so that buildworld can
1930 override the CPUTYPE if it needs to.
1932 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1933 not on the command line, or in /etc/make.conf. buildworld will
1934 warn if it is improperly defined.
1936 In case you would like to avoid installing new packages of everything,
1937 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1938 compatibility libraries are built which should allow you to continue
1939 using your existing software for a while. Alternatively, you can
1940 install the misc/compat4x port.
1942 [10] In order to create temporary files, /dev/random must be
1943 initialized by feeding data into it. src/etc/rc.d/preseedrandom
1947 This file contains a list, in reverse chronological order, of major
1948 breakages in tracking -current. Not all things will be listed here,
1949 and it only starts on March 15, 2000. Updating files can found in
1950 previous releases if your system is older than this.
1952 Copyright information:
1954 Copyright 1998-2004 M. Warner Losh. All Rights Reserved.
1956 Redistribution, publication, translation and use, with or without
1957 modification, in full or in part, in any form or format of this
1958 document are permitted without further permission from the author.
1960 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1961 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1962 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1963 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1964 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1965 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1966 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1967 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1968 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1969 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1970 POSSIBILITY OF SUCH DAMAGE.
1972 If you find this document useful, and you want to, you may buy the
1975 Contact Warner Losh if you have any questions about your use of