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 size of struct tcpcb has changed. You have to recompile
28 userland programs that read kmem for tcp sockets directly
29 (netstat, sockstat, etc.)
32 A major sweep over the tty drivers to elimnate approx 3100
33 lines of copy&pasted code have been performed. As a part of
34 this change some tty devices have changed names:
35 sio devices are now named: {tty,cua}d%d[.init,.lock]
36 ucom devices are now named: {tty,cua}U%d[.init,.lock]
37 For other drivers see the commit logs.
40 The FreeBSD keyword is no longer a requirement for a valid
41 rc.d script. The rc(8) and rc.shutdown(8) scripts no longer check
42 for the existence of this keyword when ordering rc.d scripts.
43 This change touches most of the file in /etc/rc.d; therefore,
44 if you have not modified any files in that directory it may
45 be easier to rm -rf /etc/rc.d and then use the -i switch with
49 One of the syscalls the 1:1 threading library libthr uses has
50 changed, thus breaking ABI compatibility. Make sure you rebuild
51 this library with the kernel.
54 The following libraries had their version number bumped up:
55 /lib/libm.so.2 -> libm.so.3
56 /lib/libreadline.so.4 -> libreadline.so.5
57 /usr/lib/libhistory.so.4 -> libhistory.so.5
58 /usr/lib/libopie.so.2 -> libopie.so.3
59 /usr/lib/libpcap.so.2 -> libpcap.so.3
60 FreeBSD 4.10 versions of these libraries will be added to the
61 compat4x collection. If you expect to be able to run old 4.X
62 executables you will need to remove the old versions of these
63 libraries. However note that any 5.X executables you have built
64 will stop working once you remove those old libraries. You should
65 have all your ports/packages rebuilt before removing the old
69 The pfil API has gained an additional argument to pass an inpcb.
70 You should rebuild all pfil consuming modules: ipfw, ipfilter
74 If named is enabled, the default is now to run it in a chroot
75 "sandbox." For users with existing configurations in
76 /etc/namedb the migration should be simple. Upgrade your
77 world as usual, then after installworld but before
78 mergemaster do the following:
80 If named is running: /etc/rc.d/named stop
83 mkdir -p /var/named/etc/namedb
84 cp -Rp namedb.bak/* /var/named/etc/namedb/
85 mergemaster (with your usual options)
86 If using the generated localhost* files:
87 cd /var/named/etc/namedb
88 /bin/sh make-localhost
89 rm -f localhost-v6.rev localhost.rev
90 /etc/rc.d/syslogd restart
93 If you are using a custom configuration, or if you have
94 customised the named_* variables in /etc/rc.conf[.local]
95 then you may have to adjust the instructions accordingly.
96 It is suggested that you carefully examine the new named
97 variables in /etc/defaults/rc.conf and the options in
98 /var/named/etc/namedb/named.conf to see if they might
102 BIND 9 has been imported into the base, and is now fully
103 functional. BIND 8 has now been removed. There are numerous
104 differences between BIND 8 and 9, and users with critical
105 named installations should read the migration documentation
106 in /usr/share/doc/bind9/misc/migration. There is also a
107 new instruction manual in /usr/share/doc/bind9/arm.
109 The key differences that most users will experience are in
110 how picky BIND 9 is about zone file format. If you are using
111 named as a resolving (caching) name server, you will likely
114 The following files are part of the old BIND 8 installation
115 and should be removed:
116 /usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer
117 /usr/sbin/named.restart /usr/sbin/ndc
119 The following files have moved to /usr/bin, and should be
120 removed from their old locations:
121 /usr/sbin/nslookup /usr/sbin/nsupdate
124 The format of the pflogd(8) logfile "/var/log/pflog" has changed for
125 architectures that have a 64 bit long type to make it compatible to
126 the standard pcap format. In order to prevent corruption move away
127 any old logfile before using a new pflogd(8).
130 debug.witness_* has been renamed to debug.witness.*. There are
131 compatibility tunables left in for a few days. Update loader.conf
135 The ifi_epoch change has been reverted because the ABI breakage
136 was too extensive. If you are running with a kernel/userland
137 containing the initial change (20040830), you should heed the
138 warning about ifconfig incompatibility when upgrading again.
139 With this change, 5.3 and 6.0 ifconfigs and kernels are once
143 A new variable, ifi_epoch, has been added to struct if_data
144 which is part if struct ifnet. This means all network drivers
145 and network monitoring applications need to be recompiled.
147 WARNING WARNING WARNING WARNING WARNING WARNING WARNING
149 This also breaks ifconfig compatibility. An old ifconfig will
150 not work with the new kernel and a new ifconfig will not work
151 with the old. It is strongly recommended that you make a copy
152 of your old ifconfig before installworld. If you are installing
153 remotely, you must copy over a new ifconfig before rebooting in
157 The default configuration for the network stack has been changed
158 such that it now runs without the Giant lock unless configured
159 otherwise. If you experience network-related instability, you
160 may wish to try setting "debug.mpsafenet=0" or compiling the
161 kernel with "options NET_WITH_GIANT". Details on the netperf
162 project may be found at:
164 http://www.watson.org/~robert/freebsd/netperf/
166 Including the 20040828 announcement of configuration change
170 PFIL_HOOKS are a fixed part of the network stack now and do not
171 need to be specified in the kernel configuration file anymore.
174 Netgraph changed its message format slightly to align the data
175 portion well on 64 bit machines.
176 Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
177 pppoed, bluetooth, ATM) should be recompiled when a new kernel
181 IPFW has been converted to use PFIL_HOOKS. This change is
182 transparent to userland and preserves the ipfw ABI. The ipfw
183 core packet inspection and filtering functions have not been
184 changed, only how ipfw is invoked is different. Note that
185 "option PFIL_HOOKS" is required to use IPFIREWALL compiled
186 into the kernel or as KLD.
189 The RANDOM_IP_ID option has been replaced by the sysctl
190 net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
191 you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
194 The size of 'struct ifnet' has changed due to the addition of the
195 if_carp placeholder. All kernel modules implementing network
196 interfaces must be recompiled as a result.
199 Module loading has been fixed. Some older installations will
200 drop proper module_path initialization and modules will fail to
201 load properly. If you have a line in /boot/loader.rc that says:
202 "initialize drop", do (i386 only):
203 cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
204 chown root:wheel /boot/loader.rc
205 chmod 444 /boot/loader.rc
208 making /dev/(null|zero) into a module proved to be too unpopular,
209 so this bit has been revoked from the previous (20040801) entry.
212 The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
213 so you may wish to add them to your kernel config file. See
214 GENERIC for examples.
217 System compiler has been upgraded to GCC 3.4.2-pre. As with any major
218 compiler upgrade, there are several issues to be aware of. GCC 3.4.x
219 has broken C++ ABI compatibility with previous releases yet again
220 and users will have to rebuild all their C++ programs with the new
221 compiler. If you are getting run-time error such as
222 /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
223 This entry does apply to you.
225 A new unit-at-a-time optimization mode, which is default in this
226 compiler release, is more aggressive in removing unused static
227 symbols. This is the likely cause of 'make buildworld' breakages
228 with non-default CFLAGS where optimization level is set to -O2
231 With the upgrade of the system compiler, the kernel has been upgraded
232 to match the new system compiler. This makes it impossible to build
233 a new kernel with the old compiler. Upgrade your system via
234 make buildworld and make kernel (see below) to fix this problem.
237 The size of 'struct ifnet' has changed due to the addition of
238 the IFF_NEEDSGIANT flag (and what it implies). All kernel
239 modules implementing network interfaces must be recompiled as
243 The sound device drivers are renamed. `sound' is always required,
244 while `snd_*' should be configured accordingly to your hardware.
245 Refer to NOTES for the detail of the drivers.
248 __FreeBSD_version bumped to 502122.
251 The console initialization on Alpha has been reworked and is now
252 identical to other platforms. This means that the hardcoding of
253 the serial console and the debug port has been removed. As such,
254 hints are now required for the sio(4) driver to become a console
255 or debug port. The NO_SIO option has been decommissioned because
259 A revamp of the debugging code in the kernel with some visible
260 changes beyond just the debugging experience:
261 o The DDB option is now specific to the DDB debugger backend
262 and should not be used any more for conditional compilation
263 of debugging code for when debugging is enabled. Use the KDB
265 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
266 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
267 respectively. This is in line with the first bullet.
268 o The remote GDB support has been untangled from DDB and needs
269 to be enabled separately now. Use the GDB option for this.
270 o The GDB_REMOTE_CHAT option has been removed. Support for this
271 homegrown feature is discontinued. The GDB remote protocol
272 supports console output and it makes sense to use that.
273 o The DDB_NOKLDSYM option has been removed. The DDB debugger
274 now supports both direct symbol table lookups as well as KLD
275 symbol lookups through the linker.
278 Bluetooth code has been marked as non-i386 specific.
279 __FreeBSD_version has been bumped to 502121 to mark this change.
282 The native preemption has been added to the kernel scheduler.
283 There is some report that the ULE scheduler was broken in some
284 machines and we encourage users using the ULE scheduler either
285 stick with a known good kernel, or temporarily switch to the 4BSD
286 scheduler as a workaround.
289 The netgraph ABI version number has been incremented to indicate
290 an incompatible change in the ABI. Old netgraph nodes will refuse
291 to attach until recompiled. Netgraph now uses mbuf tags to move
292 metadata and this commit removes its home-grown metadata facility.
293 Nodes should just recompile, unless they use metadata, in which
294 case the changes are simple; the file ng_ksocket.c serves as an
295 example of such changes.
297 This also broke i4b, although the compile problem has been papered
301 ACPI has been updated to disable known-bad BIOS revisions. A message
302 will be printed on the console indicating that ACPI has been disabled
303 automatically and that the user should use a newer BIOS, if possible.
304 If you think ACPI does work on your system and want to override
305 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
309 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
310 separated now. It uses the newly created "_pflogd" user/group
311 combination. If you plan to use pflogd(8) make sure to run
312 mergemaster -p or install the "_pflogd" user and group manually.
315 Network interface cloning has been overhauled. This change will
316 require a recompile of modules using cloning and modification of
317 external ones to the new API. __FreeBSD_version has been bumped
318 to 502119 to mark this change. Additionally, users creating
319 stf(4) interfaces via "ifconfig stf" will need to update their
320 scripts as this will create an interface named "stf" instead of
321 "stf0" and ifconfig will not print "stf0" to stdout.
324 On 20040524, the /etc/rc.d/nsswitch script was modified to
325 automatically create /etc/nsswitch.conf on startup if it did
326 not already exist. Unfortunately, an error in the man page
327 was carried over to the script, resulting in incorrect
328 nsswitch settings. The simplest remedy is to remove both
329 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
330 during the next reboot.
333 The return value of sema_timedwait(9) has been changed to
334 make it consistent with cv_timedwait(9). Be sure to recompile
335 the ips module and any third-party modules which call
339 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
340 Make sure to recompile modules and any userland that makes use of
341 sizeof(struct ifnet). In order to get the altq headers in place
342 please recompile and reinstall world.
345 Splitting kern_thread.c into 2 files (adding kern_kse.c)
346 requires that you re-run config after updating your tree.
349 The MIDI drivers have been removed. Until the new module-friendly
350 ones are merged, remove or comment out midi and seq from your
351 kernel configuration.
354 Due to a new option in ipfw (versrcreach) the ipfw(8) command
355 needs to be recompiled. Normal accept/reject rules without
356 options are not affected but those with options may break until
357 ipfw(8) is recompiled.
360 Due to changes in the callout ABI, kernels compiled after this
361 date may be incompatible with kernel modules compiled prior to
365 The PCI bus power state stuff has been turned on. If this causes
366 problems for your system, please disable it using the tunable
367 hw.pci.do_powerstate=0.
370 The bulk of the pci problems have been fixed, although the floppy
371 drive is still broken.
374 A substantial update to the pci bus resource and power management
375 have been committed. Expect a bumpy ride for a few days until
376 the unanticipated problems have been resolved.
379 Due to changes in the the Yarrow initialization process,
380 /dev/random needs to be fed before operations requiring
381 temp files can succeed in single user mode. This includes
382 running "make installworld". /dev/random may be fed by running
383 "/etc/rc.d/initrandom start" or with 20040415 source by running
384 "/etc/rc.d/preseedrandom".
387 The debug.mpsafenet tunable controls whether the kernel Giant
388 lock is held across the lower levels of the network stack, and
389 by default is turned off. In the few days following 20040322,
390 the behavior of debug.mpsafenet will change such that this
391 tunable controls Giant over all levels of the network stack.
392 If you are currently setting debug.mpsafenet to 1, you should
393 set it back to 0 (the default) again during the change-over.
394 An additional note will be added to UPDATING when sufficient
395 locking is merged to permit this to take place.
398 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
399 64-bits. This is a very major incompatible change, so people
400 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
401 detailed instructions on how to make this upgrade. People
402 upgrading FreeBSD on other platforms can ignore this event.
405 The packet filter (pf) is now installed with the base system. Make
406 sure to run mergemaster -p before installworld to create required
407 user account ("proxy"). If you do not want to build pf with your
408 system you can use the NO_PF knob in make.conf.
409 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
410 pf system consists of the following three devices:
412 device pflog # optional
413 device pfsync # optional
416 If you are having trouble with the libc_r -> libpthread transition
417 (see the 20040130 entry), place the following lines at the top of
420 libc_r.so.5 libpthread.so.1
421 libc_r.so libpthread.so
423 This will cause all programs and libraries linked against libc_r
424 to use libpthread instead.
427 Some sshd configuration defaults have changed: protocol version 1
428 is no longer enabled by default, and password authentication is
429 disabled by default if PAM is enabled (which it is by default).
430 OpenSSH clients should not be affected by this; other clients may
431 have to be reconfigured, upgraded or replaced.
434 The ABIs defined in <resolv.h> and <netdb.h> have been updated
435 to support improved reentrancy. Multi-threaded programs that
436 reference the "_res" or "h_errno" symbols may experience some
437 problems if they are not recompiled. Single-threaded programs
438 should remain unaffected.
441 routed has been updated in the base system from the vendor
442 sources, routed v2.27, from rhyolite.com. This change means that
443 for users who use RIP's MD5 authentication feature, FreeBSD
444 -CURRENT's routed is now incompatible with previous versions
445 of FreeBSD; however it is now compatible with implementations
446 from Sun, Cisco and other vendors.
449 The tcpcb structure has changed and makes a recompile of libkvm
450 and related userland network utilities necessary.
453 The cdevsw structure has changed in two externally visible ways.
454 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
455 Second, the d_version field must be filled in with D_VERSION.
456 Drivers outside the tree will need to be updated.
459 The /etc/rc.d/ttys script has been removed. It is no longer
460 necessary since devfs has been mandatory for some time.
463 libkse has been renamed back to libpthread and is now the
464 default threads library. The gcc -pthread option has also
465 been changed to link to libpthread instead of libc_r. For
466 alpha and sparc64 machines, libkse is not renamed and links
467 are installed so that libpthread points to libc_r. Until
468 the ports system is updated to handle this change, it is
469 recommended that folks install an /etc/libmap.conf(5) that
470 maps libc_r to libpthread. If you have any binaries or
471 libraries linked to libkse, then it is also recommended
472 that you map libkse to libpthread. Anyone that is using
473 nvidia supplied drivers and libraries should use a libmap.conf
474 that maps libpthread to libc_r since their drivers/libraries
475 do not work with libpthread.
478 ULE has entered into its probationary period as the default scheduler
479 in GENERIC. For the average user, interactivity is reported to be
480 better in many cases. On SMP machines ULE will be able to make more
481 efficient use of the available parallel resources. If you are not
482 running it now, please switch over, replacing the kernel option
483 SCHED_4BSD with SCHED_ULE.
486 Move LongRun support out of identcpu.c, where it hardly
487 belongs, into its own file and make it opt-in, not mandatory,
488 depending on CPU_ENABLE_LONGRUN config(8) option.
491 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
492 if the login process is unable to successfully set the
493 process credentials to include all groups defined for the
494 user. The current kernel limit is 16 groups; administrators
495 may wish to check that users do not have over 16 groups
496 defined, or they will be unable to log in.
499 The ACPI module has been reactivated. It is no longer required
500 to compile ACPI support into kernels statically.
503 The statfs structure has been updated with 64-bit fields to
504 allow accurate reporting of multi-terabyte filesystem
505 sizes. You should build world, then build and boot the new kernel
506 BEFORE doing a `installworld' as the new kernel will know about
507 binaries using the old statfs structure, but an old kernel will
508 not know about the new system calls that support the new statfs
510 Note that the backwards compatibility is only present when the
511 kernel is configured with the COMPAT_FREEBSD4 option. Since
512 even /bin/sh will not run with a new kernel without said option
513 you're pretty much dead in the water without it. Make sure you
514 have COMPAT_FREEBSD4!
515 Running an old kernel after a `make world' will cause programs
516 such as `df' that do a statfs system call to fail with a bad
517 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
518 that cfsd (ports/security/cfs) needs to be recompiled after
519 these changes are installed.
521 ****************************DANGER*******************************
523 DO NOT make installworld after the buildworld w/o building and
524 installing a new kernel FIRST. You will be unable to build a
525 new kernel otherwise on a system with new binaries and an old
529 Some netgraph string length constants have been changed. This
530 change requires the netgraph kernel modules and all netgraph
531 userland components to be in sync. Especially users who require
532 netgraph to boot need to make sure to have world and kernel in
533 sync before rebooting.
536 Hyperthreading logical CPU's are no longer probed by default
537 when using the MP Table. If ACPI is being used, then logical
538 CPUs will be probed if hyperthreading is enabled in the BIOS.
539 If ACPI is not being used and hyperthreading is enabled in the
540 BIOS, logical CPUs can be enabled by building a custom kernel
541 with the option MPTABLE_FORCE_HTT enabled.
544 The i386 APIC_IO kernel option has been replaced by
545 'device apic'. The ACPI module has also been temporarily
546 disabled, so ACPI must be statically compiled into your
547 kernel using 'device acpi' if you wish to use the ACPI driver.
550 The API and ABI of struct ifnet have been changed by removing
551 the if_name and if_unit members and replacing them with
552 if_xname, if_dname, and if_dunit. All network drivers and most
553 userland programs which include net/if_var.h must be updated
554 and recompiled. __FreeBSD_version has been bumped to 501113 to
558 Changes to the cdevsw default functions have been made to remove
559 the need to specify nullopen() and nullclose() explicitly.
560 __FreeBSD_version bumped to 501110.
563 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
564 mount_cd9660(8) need to be in sync with kernel.
567 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
568 also be explicitly configured. Previously this dependency was
569 magically handled through some cruft in net/pfil.h; but that has
570 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
571 will fail with obtuse errors in ip_fil.c.
574 Fix a bug in arplookup(), whereby a hostile party on a locally
575 attached network could exhaust kernel memory, and cause a system
576 panic, by sending a flood of spoofed ARP requests. See
577 FreeBSD-SA-03:14.arp.
580 A change to /etc/defaults/rc.conf now causes inetd to be started
581 with `-C 60' if it is not overridden in /etc/rc.conf. This
582 causes inetd to stop accepting connections from an IP address
583 that exceeds the rate of 60 connections per minute.
586 The following rc.d scripts have been removed and should be
587 deleted from your installation: atm2.sh atm3.sh devdb
588 localdaemons network1 network2 network3. Depending on when
589 you last updated world and used mergemaster(8) you may or
590 may not have problems during the rc boot sequence. The simplest
591 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
592 The atm2.sh atm3.sh and devdb scripts were removed some time
593 ago, so depending on when you installed -CURRENT these scripts
594 may or may not exist on your system.
597 ATAng has been committed. You need to build world as sys/ata.h
598 has changed, and userland atacontrol depends on it.
599 If you use ATA SW raids you need "device ataraid" in your
600 kernel config file, as it is no longer pulled in automatically.
603 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
604 Among other things, this changes the device enumeration to be
605 closer to Solaris. Be aware that, this can even cause the machine
606 to not boot without manual intervention before the fstab is adjusted.
609 All current USB and Firewire quirks in da(4) have been deprecated
610 and will be removed for 5.2. If this causes failure for your
611 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
612 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
613 so the quirk can be re-enabled.
616 Problems with entry 20030714 have been corrected and no known issues
617 with /rescue and -j exist for host systems after this point in time.
620 FPU-less support has been removed from FreeBSD. Chances are you won't
621 notice. 386+387 support should still work after this change, but
622 it is now a minimum requirement for the i386 port that you have real
626 Some people are having problems with changes related to /rescue.
627 If you are building -j N, you will need to define NO_RESCUE. Others
628 will need to define it if /rescue has issues with their environment.
629 People should report those issues to current@.
632 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
633 across this point. Further, it might be a good idea to remove
637 Remove deprecated locale names and transition period code
638 for them, finishing switching to the new scheme. Check your
639 LANG environment variable.
642 CCD has been changed to be a fully GEOMified class. Kernel
643 and ccdconfig(8) needs to be in sync, this is particularly
644 important to remember beforehand if your source tree is on
645 a ccd device. Consider making a copy of the old ccdconfig
646 into /boot/kernel.good or wherever you keep your backup
650 There was a small window in which sed(1) was broken. If you
651 happen to have sed(1) installed during that window, which is
652 evidenced by an inability to build world with the failure
653 given below, you need to manually build and install sed(1)
654 (and only sed(1)) before doing anything else. This is a one-
655 time snafu. Typical failure mode:
657 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
658 targmatch.h:7:1: null character(s) ignored
659 targmatch.h:12:1: null character(s) ignored
660 targmatch.h:16:1: null character(s) ignored
663 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
664 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
665 usr.bin/sed/process.c).
668 Kerberos 5 (Heimdal) is now built by default. Setting
669 MAKE_KERBEROS5 no longer has any effect. If you do NOT
670 want the "base" Kerberos 5, you need to set NO_KERBEROS.
673 groff has been updated. If you try to do a buildworld and
674 get an infinite loop in troff, update to May 4th or newer. If you
675 have a newer kernel than userland, you may need to set the OSRELDATE
676 to 500110 in your environment before starting a buildworld.
679 The old rc system has been removed. Please report any problems
680 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
681 Your personal versions of these files will not be removed, so you can
682 continue to use them. However, you should take great care when updating,
683 especially when using mergemaster, since the compatibility code that
684 utilizes these old scripts has also been removed.
687 A bug has been fixed in /dev/devctl which would cause devd
688 to hang on boot, were it not for a workaround in devd. The
689 work around in devd will be removed around 20030507. You
690 have until then to upgrade your kernel before updating
691 userland. In general, you should have a userland and
692 kernel that's in sync with each other. However, given the
693 effects of this bug (hang on boot when starting devd), some
697 Alphas with libc from between 20030312 and 20030329 exhibit
698 floating point exceptions (FPEs), most notably in awk(1)
699 while upgrading the system through a buildworld.
701 So, to successfully upgrade your Alpha, you must either
702 downgrade your libc.so to a pre-20030312 version, or update
703 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
704 to CFLAGS, then forcibly rebuild and install libc:
706 cd /usr/src/lib/libc && \
707 make cleandir && make obj && \
708 make -DNOMAN -DNOPROFILE all && \
709 make -DNOMAN -DNOPROFILE install
712 sendmail 8.12.7 has been imported. It has one important
713 change for IPv6 users. The default submit.mc now uses
714 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
715 used to connect to the MTA. Users on IPv6-only machines
716 will need to edit /etc/mail/submit.mc appropriately.
719 NODEVFS option has been removed and DEVFS thereby made standard.
720 This makes all references to MAKEDEV obsolete, and they should
721 be removed when convenient.
724 The name of the device for the ofw console has changed, sparc64 users
725 must run mergemaster to update their installed /etc/ttys.
728 The scheduler framework has grown a second scheduler and consequently
729 you must specify one and only one scheduler in your kernel config.
730 The cvs config files have been updated to use the old scheduler
731 which may be selected via 'options SCHED_4BSD'. If you would like
732 to try the new, much more experimental, scheduler please try
733 'options SCHED_ULE' and contribute to the arch@ discussion.
736 A new version of the wi driver has been imported into the tree.
737 One now must have device wlan in the config file for it to operate
740 In addition, there have been some changes to how wi devices are
741 configured for point to point links to bring it more in line
742 with the former way of doing things, as well as compatibility
746 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
747 used an incompatible form of ABI for returning structures and unions
748 which FreeBSD's GCC maintainers were not aware of relative to previous
749 versions of FreeBSD. We have gone back to the ABI for now, and any
750 code compiled which is required to interoperate with other code (not
751 built at the same time) returning structs or unions should be
755 A name change in /etc/netconfig has been reverted to stay
756 compatible with suns TIRPC and also with NetBSD. You need
757 to run mergemaster after make world. A new libc does still work
758 with an outdated /etc/netconfig for some time, but you'll get
759 a warning. This warning will be removed in 20030301.
762 The recent binutils upgrade marks a kernel flag day on
763 sparc64: modules built with the old binutils will not work
764 with new kernels and vice versa. Mismatches will result in
765 panics. Make sure your kernel and modules are in sync.
768 The value of IPPROTO_DIVERT has changed. Make sure to keep
769 your kernel, netstat, natd and any third-party DIVERT
773 Old, compatibility slices have been removed in GEOM kernels.
774 This means that you will have to update your /etc/fstab to
775 not use disk devices of the form /dev/ad0a. Instead, you
776 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
777 partition really is on. The old device names have gone
778 away, so if you use them anywhere else, you must also adjust
779 those uses. (This doesn't affect the disks formatted in
780 the ``dangerously-dedicated'' mode.)
783 Alphas with kernels from between 20020830 and 20021023 and/or
784 rtld (ld-elf.so.1) older than 20021023 may experience problems
785 with groff while doing a buildworld (kernel: "out of memory",
786 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
787 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
789 So, to successfully upgrade your Alpha, you must either
790 upgrade your kernel and rtld first (which might be a bit
791 tricky), or avoid running the bootstrapped groff during the
792 "transitional" buildworld. To avoid running groff during the
793 transitional upgrade run make buildworld with -DNOMAN,
794 -DNO_SHAREDOCS, and -DNO_LPR.
797 gcc has been upgraded to 3.2. It is not all binary compatible
798 with earlier versions of gcc for c++ programs. All c++
799 programs and libraries need to be recompiled.
801 Also, if you encounter g++ issues, rm /usr/include/g++/* before
802 doing an installworld to make sure that stale files are removed.
805 Our /etc/termcap now has all the entries from the XFree86 xterm
806 almost unchanged. This means xterm now supports color by default.
807 If you used TERM=xterm-color in the past you now should use
808 TERM=xterm. (xterm-color will lead to benign warnings).
811 A "bug" in gcc(1) that was hiding warning in system headers was
812 fixed. It's probably time to add -DNO_WERROR to your make line
816 COPY is being deprecated. The 20010530 change was reverted, as
817 it causes far more pain than was expected, and to always compare
818 before installing, please use INSTALL="install -C" again. The
819 -C option is now silently ignored when used with the -d option.
822 Problems with libc_r clients like KDE and GNOME have been resolved.
823 There are still some minor problems with some signals but the
824 system is stable enough for general use again. SMP is less so than UP
825 but each can successfully complete multiple buildworlds.
826 Libkvm needs to be recompiled due to KSE.
829 Now would be a bad time to upgrade. Something in or near the
830 KSE commit totally broke programs using libc_r like KDE and
834 The k5su utility installed as part of Kerberos 5 is no longer
835 installed with the set-user-ID bit set by default. Add
836 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
837 with the set-user-ID bit set.
840 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
841 Unfortunately our native GDB (at version 4.18) does not understand
842 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
843 generated debugging information for our native GDB.
846 Due to the way CVS works, it may not properly update src/contrib/gcc
847 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
848 and then do a cvs update.
851 When exec'ing set[ug]id executables, the kernel now ensures that the
852 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
855 New sendmail startup scripts have been installed to make it
856 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
857 variable sendmail_enable to "NO" no longer prevents any sendmail
858 daemons from starting. Instead, either set sendmail_enable to
859 "NONE" or change mta_start_script to a script for starting
860 an alternative MTA. Setting mta_start_script to "" will
861 also prevent any MTA from being started at boot.
864 UCONSOLE is no longer a valid kernel option.
867 FreeBSD 5.0 DP-1 was basically branched today.
870 Warnings are now errors in the kernel. Unless you are a developer,
871 you should add -DNO_WERROR to your make line.
874 sendmail 8.12.2 has been imported. The sendmail binary is no
875 longer a set-user-ID root binary and the infrastructure to support
876 command line mail submission has changed. Be sure to run
877 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
878 and /etc/mail) and read /etc/mail/README for more details.
880 Due to the import of sendmail 8.12.2, a new user and group are
881 required in order for sendmail to run as a set-group-ID
882 binary. A 'make installworld' will use the new user and group
883 to set the owner and group of /var/spool/clientmqueue and will
884 fail if the new user and group do not exist. The 'smmsp' user
885 and group must be merged from src/etc/group and
886 src/etc/master.passwd before using 'make installworld'.
887 'mergemaster -p' will do this. You may need to install
888 mergemaster before this will work if you are updating from a
889 very old version of current. The updating recipe has changed
893 The preferred configuration method for PAM is now /etc/pam.d/
894 rather than /etc/pam.conf. If you have an unmodified
895 pam.conf, just delete it after your next mergemaster run. If
896 you have local modifications, you can use
897 /usr/src/etc/pam.d/convert.pl to incorporate them into your
900 Please see the following url for more details:
901 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
903 If anyone here is already using the new rc.conf(5) variable
904 networkfs_types, please note that it has changed
905 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
908 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
909 started out its life in the ISDN4BSD project as an offspring
910 from sys/net/if_spppsubr.c, which eventually got a life of its
911 own. All the accumulated features and bug fixes of the i4b
912 version have now been merged back into the base system's
913 version now. The only user-visible change resulting from this
914 is that i4b's sppp(4) interfaces are to be managed with
915 spppcontrol(8) again, since ispppcontrol(8) has been retired
916 as well. (There has never been rc file support for
917 ispppcontrol in -current, but only in -stable. That will be
918 reverted by the time the changes are MFCed.)
921 The fdc(4) driver has been updated and now automatically
922 recognizes media in `standard' formats (like 1440 KB and
923 720 KB for a 3.5" high-density drive) when accessing the
924 default device node (e. g. /dev/fd0). The old variety of
925 floppy device nodes /dev/fd*.* is no longer present by
926 default, devices can be created (in DEVFS) on demand. They
927 will need to be customized then for `odd' densities using
931 The bugs in procfs' debugging support code have been fixed,
932 and truss(1) now works again.
935 Daily security checks have been split out to use the periodic(8)
936 scripts. Some change in configuration may be necessary. Please
938 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
942 sos added VCD/SVCD support to ata driver and that needs the
943 kernel and burncd to be in sync.
946 The procfs pseudo-filesystem has now been converted to use the
947 pseudofs framework. If you have 'options PROCFS' in your
948 kernel config, you'll need to add 'options PSEUDOFS' if it's
951 This change temporarily breaks truss(1); use ktrace(1) instead
952 until the issue has been resolved.
955 A security hole in OpenSSH involving `UseLogin yes' has been
959 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
960 after this date. You need to do this only once.
963 Most of the awk issues have been resolved. Some rough
964 edges may be left, but for the most part things should be
965 back to "normal." For CURRENT's usual definition of "normal."
968 Awk has been upgraded to the one true awk from bell labs. Expect
969 choppy waves in the upgrade process.
972 The asr driver problem has been resolved.
975 Due to changes in other parts of the system, the asr driver
976 now causes the system to panic on boot. Do not use it pending
977 correction. Comment it out of any kernel config file that you
978 try to use from this date forward.
981 When crossbuilding, use TARGET=xxx where you used to use
982 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
983 unless you are changing both of them. To cross build pc98 on
984 an alpha, for example, you need to set TARGET=pc98 and
988 The kernel interface that burncd depends on has changed.
989 You must recompile both the kernel and userland applications
993 When crossbuilding, please set TARGET_ARCH rather than
994 MACHINE_ARCH to indicate the target. In the future, one will
995 set TARGET_MACHINE where you set MACHINE now. At the moment,
996 setting MACHINE alone for same MACHINE_ARCH machines works
997 (eg, you can build pc98 on an i386 machine and vice versa).
1000 Some weird problems result from using ACPI on some machines.
1001 To disable ACPI you can add
1002 hint.acpi.0.disabled="1"
1003 to /boot/loader.conf (or by putting set X=Y at the boot
1004 loader "ok" prompt).
1006 Alternatively, you can remove it from /boot/kernel/acpi.ko
1007 or use the MODULES_OVERRIDE function in your kernel config
1008 file and not list acpi in that list.
1011 The buildworld has been fixed. You may need to install
1012 the 4.x compatibility libraries for some old binaries
1013 to work. Add COMPAT4X=true to your /etc/make.conf to
1014 get them installed on every installworld, or execute the
1015 following to get them installed only once:
1016 cd src/lib/compat/compat4x.<arch>
1018 You will see ``__stdoutp undefined'' until you do this.
1021 There's a bug in the world build process. The cross-tools
1022 are build with the NEW headers, but the OLD libc.a. This
1023 leads to all kinds of problems with the new libc. A temporary
1024 workaround is to add
1025 CFLAGS="-O -pipe -D_OLD_STDIO"
1026 before building world when upgrading from 4.x to current. This
1027 can be removed afterwards.
1029 A proper fix to the buildworld target is needed.
1032 Peter has committed his new kthread nfs client/server code.
1033 NFS may be unstable after this date.
1036 KSE has hit the tree. Lots of things are now different in
1037 the kernel. While a few problems were introduced in the
1038 initial commit, most of the major ones have been found and
1042 In OLDCARD, CardBus bridges appear to be stable. The work
1043 arounds described in the 20010604 entry are now no longer
1044 necessary and will be ignored. Most insert/remove problems
1045 have been rectified around this date.
1048 named now runs as user bind and group bind rather than as
1049 root. If named_enable is set to YES in /etc/rc.conf, ensure
1050 that user bind is available in /etc/passwd (using vipw(8))
1051 and that group bind is available in /etc/group. Also make
1052 sure that user or group bind has read (and not write)
1053 permission for your name server configuration and that it
1054 has read and write permission for your slave zone files and
1057 If you wish to continue to run named as root (a less secure
1058 alternative), add a line to /etc/rc.conf saying
1063 The PAM libraries have had an API upgrade that is beyond
1064 the ability of the shared library major number to handle.
1065 It is manifested by PAM-using ports dumping core. The
1066 solution is to rebuild those ports.
1069 The kernel compile module has moved from src/sys/compile/FOO
1070 to src/sys/${MACHINE}/compile/FOO.
1073 The pccard modem issue from 20010613 has been corrected.
1074 OLDCARD support is still a little weak in -current. slot 1 is
1075 known not to work on some TI based cardbus bridges. Some
1076 cardbus bridges do not properly detect insert/removal events.
1077 IRQ configuration needs more safety belts.
1080 Softupdates problems have been corrected.
1083 Peter ripped out the linkerset support. You must, as always,
1084 rerun config after you cvsup if you are using the traditional
1085 kernel building methods.
1088 pccard modems may not work with current after 20010604 date. Some
1089 do, others result in panics. *MAKE*SURE* that you update your
1090 config and /etc/rc.conf ala the 20010604 entry, or you will have
1091 problems (this issue will be fixed, it just hasn't been yet).
1094 SOFTUPDATES seem to be broken since the middle of May or so. Do not
1095 use them in current. You can disable softupdates on all mounted
1096 partitions, or remove SOFTUPDATES the kernel config file.
1099 After Peter's commits to the hints code, people have been noticing
1100 that certain devices are attached (or try to) twice. This is due
1101 to having both static hints as well as a /boot/device.hints. To
1102 work around this issue, please use only one or the other mechanism
1103 until this bug is fixed.
1105 Please note that a feature of config is that if you have config
1106 file FOO and FOO.hints, it automatically adds FOO.hints to the
1107 hints.c file, whether you want it to or not.
1110 Locale names have changed to match other systems better.
1113 pccard support for pci cards has been committed. You must change
1114 your /etc/pccard.conf irq lines. It must match the irq used by
1115 pcic device. Interrupt storms may result if you fail to do this.
1116 Interrupt storms look a lot like a hang.
1118 You must also install a new pccardd, otherwise you will get an
1119 interrupt storm at card reset time (just after it tells you what
1122 pccardd_flags="-I" is necessary for the time being. It tells pccardd
1123 not to ask the kernel if the interrupt is really free or not before
1124 using it. You can either change the /etc/pccard.conf irq lines to
1125 match pcic, or add "-i X" to the pccardd_flags.
1128 INSTALL=install -C is being deprecated. If you want to do this,
1129 use COPY=-C instead. The former method will be supported for only
1130 a limited time. If you see
1132 install: warning: the -d and -C options may not be specified together
1134 in your makeworld, then you need to migrate towards using
1138 It appears that vm is now stable enough to use again. However,
1139 there may be other problems, so caution is still urged. alpha
1140 definitely is in bad shape.
1143 Minor repo damage has happened. This may cause problems
1144 with cvsup of ports. If you get errors, please see
1145 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1146 at the bottom for details on a workaround. The error message
1148 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1151 Vm and/or swapping are busted on -current. Please be patient.
1154 pccard has had much reorganizational work done to it over
1155 the past few days. Everything should still work, but if
1156 not, please contact imp@freebsd.org.
1159 ata ioctl changed. Make sure to recompile both kernel and
1160 userland at the same time.
1163 New ncurses imported.
1166 DEVFS is now opt out, not opt in. Barring major problems, this
1167 will be the only way to go starting July 1.
1170 OpenSSH has been updated to 2.9. Some defaults are different,
1171 including RhostsRSAAuthentication, which changes from yes to no.
1174 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1177 Building perl was broken at 02:25:25 PDT.
1180 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
1181 go back in the water.
1184 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
1185 this date, but before the correction date.
1188 old fsck and new kernel interactions appear to have been fixed.
1191 fsck and the kernel were changed to handle some optimizations
1192 to directory layout. This breaks backward compatibility.
1193 Update only if you understand that you must not use the old
1194 fsck with the new kernel ever.
1197 fsck has changed the meaning of the pass column in /etc/fstab.
1198 Please see the cvs commit to fsck.8 or the fsck.8 man page for
1199 details. It is unclear if changes to /etc/fstab are necessary.
1202 portmap had changed name to rpcbind for maximum POLA in your
1203 current world. /etc/hosts.{allow,deny} needs changes. nfs and
1204 other rpc based programs that rely on portmapper will not work
1205 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
1208 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1209 and ATA_ENABLE_TAGS are no longer kernel options. They have
1210 been replaced by tunables. See ata.4 for details.
1213 The fxp driver was converted to use miibus. If you compile
1214 fxp into your kernel statically, you will need to add miibus.
1217 The wi device now defaults to BSS (infrastructure) mode
1221 /dev/urandom should be a symbolic link to /dev/random now.
1222 Users of current not using DEVFS need to run MAKEDEV std.
1223 ssh might not work if you don't.
1226 The ed driver has been updated. It now allows mii attachments,
1227 which means that you must include the miibus in your kernel if
1228 you use the ed driver.
1231 The problems with libc have been corrected. It is now mostly
1232 safe to go back into the water.
1235 The size of FILE was changed. This breaks upgrading. If
1236 you must upgrade, be prepared for pain. It also breaks almost
1237 all binaries that you've compiled on -current. You are warned
1238 that before upgrading would be a good time to do a level 0
1239 dump of your system. No, really, I mean it this time.
1241 To get to the new system, you'll need to use the following
1242 workaround. Hopefully this can be sorted out so that we
1243 don't have to move this to the updating section.
1245 To get around the installworld problem, do:
1246 # cd /usr/src/usr.bin/sed
1250 If that doesn't work, then try:
1251 # make -k installworld
1255 DEVFS is now the default. If you use vinum, make sure that you
1256 do not include devfs in your kernel as problems result.
1259 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1260 Remove them from your config.
1263 ****************************** WARNING ******************************
1264 buildkernel has been changed slightly
1265 ****************************** WARNING ******************************
1266 KERNCONF replaces the variable KERNEL for buildkernel. You
1267 should update your scripts and make.conf accordingly.
1270 config has changed to allow DEV_FOO as a replacement for NFOO.
1271 This requires a new config to build correctly.
1274 The kernel option I386_CPU is now mutually exclusive with the
1275 other cpu types. If you have an i386 system, be sure that it
1276 only had this line. Remove it for all other configurations.
1279 Changes to the kernel require it and burncd be in sync.
1282 Everyone who has hw.sndunit set to something in
1283 /etc/sysctl.conf, it is now hw.snd.unit.
1286 ex and vi were broken by some changes to sys/queue.h. If you
1287 have a bad vi, you will see make buildworld fail with a core
1288 dump while building termcap. You can work around this problem
1289 by adding -k to your make buildworld. This will cause the
1290 build to complete and install a new vi. Once that's done, you
1291 can rebuild again without the -k to pick up anything that
1292 might have been ignored by the -k option.
1294 Others have suggested that you can just rebuild libc if your
1295 vi/ex is dynamically linked, but I've not received any reports
1299 There have been some changes to libcrypt in -current. The
1300 libscrypt/libdescrypt symlink silliness is gone and the installed
1301 libcrypt is fully functional. Be aware of this.
1304 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1305 now require the addition of flag 0x80000 to their config line
1306 in pccard.conf(5). This flag is not optional. These Linksys
1307 cards will not be recognized without it.
1310 Important new FreeBSD-version stuff: PAM support has been worked
1311 in, partially from the "Unix" OpenSSH version. This requires
1312 adding the following in pam.conf:
1314 sshd auth sufficient pam_skey.so
1315 sshd auth required pam_unix.so try_first_pass
1316 sshd session required pam_permit.so
1319 cvs updated to 1.11.
1322 The random device needs more entropy, so you need to make sure
1323 that you've run mergemaster to get a /etc/rc which will seed
1324 /dev/random. If you don't and the system hangs after ldconfig,
1325 then banging on the keyboard randomly until it unhangs is one
1329 ****************************** WARNING ******************************
1330 Sendmail has been updated.
1331 ****************************** WARNING ******************************
1332 o mail.local(8) is no longer installed as a set-user-id binary.
1333 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1335 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1337 o Now using sendmail's version of vacation(1).
1338 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1339 in /usr/share/sendmail/cf.
1340 o sendmail.cw changed to local-host-names
1342 More details can be found at
1343 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1346 The ports tree's new layout is in place. Be sure to update
1347 your entire ports tree, or you will have problems.
1350 The perl build procedure no longer installs miniperl, nor uses
1351 the installed miniperl. It is recommended that you delete
1355 This weekend the ports tree will be updated to a new layout.
1356 It will be in an inconsistent state until noted in the UPDATING
1357 file, or with asami-san's message to the relevant mailing
1358 lists. With this new layout, you'll need to update the whole
1359 tree for anything to work.
1362 There was a change in the passwd format. Need more information.
1365 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1366 place. Please update boot loader (not the boot blocks) at the
1367 same time as your kernel.
1370 The new pmtimer device is necessary for laptops. Failure to
1371 include the device will cause suspended laptops losing time
1372 when they resume. Include
1374 in your config file and
1375 hint.pmtimer.0.at="isa"
1376 to your /boot/device.hints file.
1379 The random device has been turned into a (pseudo-)device,
1380 rather than an option. The supplied kernel config files have
1381 been updated. You will need to do something similar in your
1382 own kernel config file.
1387 If you prefer to load the loadable module, you need to do
1391 The random device module has been renamed from randomdev.ko to
1392 random.ko. You will need to edit your /boot/loader.conf to
1393 reflect this if you load this module at boot time.
1394 The line should read:
1398 The SMPNG commit has happened. It should work, but if it
1399 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1400 to be a variety of minor issues. Please see 20000905 to make
1401 sure you don't have model loading problems which might at
1402 first blush appear related to SMP.
1405 nsswitch has been imported from NetBSD. Among other things,
1406 this means that /etc/host.conf is no longer used. See
1407 nsswitch.conf(5) instead. Note that at boot time rc.network
1408 will attempt to produce a new nsswitch.conf file for you if you
1409 don't have one, and you have host.conf.
1412 The ucred structure changed size. This breaks the interface
1413 that mountd uses. Trying to use an older mountd with a newer
1414 kernel guarantees a panic. This means that you need to use
1415 kernels newer than today only with matching mountd, but you
1416 needed to do that anyway with the boot loader changes.
1419 The boot loader has been updated. The new default kernel is
1420 now /boot/kernel/kernel.ko. The new default module location
1423 You *MUST* upgrade your boot loader and kernel at the same time.
1424 The easiest way to do this is to do the buildworld/buildkernel/
1425 installkernel/installworld dance.
1427 Furthermore, you are urged to delete your old /modules directory
1428 before booting the new kernel, since kldload will find stale
1429 modules in that directory instead of finding them in the correct
1430 path, /boot/kernel. The most common complaint that this cures
1431 is that the linux module crashes your machine after the update.
1433 if [ ! -d /boot/kernel.old ]; then
1434 mv /modules.old /boot/kernel.old
1435 chflags noschg /kernel.old
1436 mv /kernel.old /boot/kernel.old/kernel.ko
1437 chflags schg /boot/kernel.old/kernel.ko
1441 A new issue with the sendmail upgrade has come to light.
1442 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1443 incorrectly install the default aliases in /etc/mail rather than
1444 move the old one from /etc. So you'll need to manually move the
1445 file, create a symbolic link, remove the old /etc/aliases.db and
1446 run newaliases. For safety sake, you should stop sendmail
1447 while doing this and run the upgrade when locally sourced email
1448 is not likely to be generated.
1451 /boot/device.hints is now required for installkernel to
1452 succeed. You should copy GENERIC.hints for your architecture
1453 into /boot/device.hints. If and only if you compile hints
1454 into your kernel, then this file may be empty. Please note,
1455 if you have an empty or missing /boot/device.hints file and
1456 you neglected to compile hints into your kernel, no boot
1457 messages will appear after the boot loader tries to start the
1461 If you do NOT have ``options RANDOMDEV'' in your kernel and
1462 you DO want the random device then add randomdev_load="YES" to
1466 suidperl is now always built and installed on the system, but
1467 with permissions of 511. If you have applications that use
1468 this program, you are now required to add ENABLE_SUIDPERL=true
1469 to /etc/make.conf. If you forget to do this,
1470 chmod 4511 /usr/bin/suidperl
1471 will fix this until the next build.
1474 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1475 visible changes that may immediately affect your configuration
1477 - New default file locations from src/contrib/sendmail/cf/README
1478 - newaliases limited to root and trusted users
1479 - MSA port (587) turned on by default
1480 - New queue file naming system so can't go from 8.11 -> 8.9
1481 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1482 - FEATURE(`nullclient') is more full featured
1483 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1484 - mail.local FreeBSD-only -b option changed to -B
1485 - See src/contrib/sendmail/RELEASE_NOTES for more info
1488 suidperl (aka sperl) is no longer build by default. You must
1489 specifically define BUILD_SUIDPERL to "true" for it to be build.
1490 Furthermore, we recommend that you remove /usr/bin/sperl* and
1491 /usr/bin/suidperl files from your system unless you have a
1492 specific use for it.
1495 Networking defaults have been tightened. Anybody upgrading
1496 /etc/defaults/rc.conf needs to add the following lines to
1497 /etc/rc.conf if they want to have the same setup
1498 afterwards (unless the variables already are set, of course):
1499 # Enable network daemons for user convenience.
1501 portmap_enable="YES"
1502 sendmail_enable="YES"
1505 If you have null_load="YES" in your /boot/loader.conf, you
1506 will need to change that to nullfs_load="YES".
1509 The "installkernel" target has changed slightly. Now even if
1510 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1511 it will install the MYKERNEL file (built with the buildkernel
1512 target) as /kernel rather than /MYKERNEL. Those who have
1513 updated their /boot/loader.conf files to point to /MYKERNEL
1514 should remove that entry or perform manual rename of /kernel
1518 If you use CVSUP or CTM to get CVS trees, AND you used to get
1519 the old crypto files from internat.freebsd.org AND you check
1520 out files from the CVS tree with the cvs command, please read
1521 http://people.freebsd.org/~imp/internat.txt
1522 for details on potential problems that you might have and how
1525 If you are merely a mirror, or don't answer yes to each of the
1526 clauses above, you needn't worry.
1529 /etc/security has been updated to print the inode number of
1530 setuid programs that have changed. You will see a large spike
1531 in the number of changed programs the first time when you run
1532 mergemaster to get a new /etc/security.
1535 /dev/random now has good entropy collection (from the keyboard
1536 and sysmouse drivers). Please ensure that either `options
1537 RANDOMDEV' is present in your kernel config file or that
1538 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1539 not have the /dev/random driver, OpenSSL (and consequently
1540 lots of crypto tools (like SSH)) will fail with strange
1541 errors. (see below, 20000624).
1543 FreeBSD-current is safe again to run Crypto.
1546 phk made the malloc default options AJ. This may slow things
1547 down and uncover other latent bugs in the code. If you need to
1548 run at full speed, you can disable this by doing the following:
1549 ln -s aj /etc/malloc.conf
1552 libftpio's version was accidentally bumped a few days ago. This
1553 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1554 before doing your next buildworld/installworld pair. It certainly
1555 won't hurt to remove it before the update procedure. It will
1556 break fetch until a new one is built, but ftp can be used in the
1560 The crypto packages have changed for the cvsup. This has been done
1561 in a backward compatible way, but the old packages will go away at
1562 some point in the future. Look at /usr/share/examples/cvsup for
1566 With the new sys/modules/sound/drivers/*, you will need to
1567 set SYSDIR until you do an installworld after July 7th.
1570 rc.shutdown and rc will now call the rc.d scripts with start
1571 or stop. This may cause some harmless warnings from older
1572 rc.d scripts that haven't been updated.
1575 The libfetch based version of fetch has gone into the tree.
1576 Minor problems may result on some of the less popular sites,
1577 which should be reported to des@freebsd.org.
1580 From approximately this date forward, one must have the crypto
1581 system installed in order to build the system and kernel.
1582 While not technically strictly true, one should treat it as
1583 required and grab the crypto bits. If you are grabbing CVS
1584 trees, src-all and cvs-crypto should be treated as if they
1585 were required. You should check with the latest collections
1586 to make sure that these haven't changed.
1589 Mark Murray just committed the first parts of a cleanup of
1590 /dev/zero, et al. This is also cleaning up /dev/random.
1591 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1592 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1593 until Mark can merge in the fixes to this work in progress.
1594 openssh and openssl should not be used to generate keys from this
1595 date to the completion of the work.
1597 If you must operate at this reduced level of security, add '
1598 options RANDOMDEV' to your kernel or modload the randomdev
1599 module. You may also need to copy a new MAKEDEV to /dev and
1600 recreate the random and urandom devices.
1603 The license on the softupdates is now a standard 2 clause
1604 BSD license. You may need to remove your symbolic links
1605 that used to be required when updating.
1608 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1609 the config file update procedure.
1610 http://people.freebsd.org/~imp/config-upd.html
1611 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1612 isn't buildable. However, you can generate a LINT file:
1613 cd /sys/<ARCH>/conf && make LINT
1616 Binutils 2.10 have hit the tree, or will shortly. As soon
1617 as they do, the problem noted in 20000522 will be resolved and
1618 that workaround will no longer be required.
1621 phk removed the compatibility creation of wd devices in the
1622 ad driver. If you haven't done so already, you must update
1623 your fstab, etc to use the ad devices instead of the wd
1626 In addition, you'll need to update your boot blocks to a
1627 more modern version, if you haven't already done so. Modern
1628 here means 4.0 release or newer (although older releases
1632 Peter took an axe to config(8). Be sure that you read his mail
1633 on the topic before even thinking about updating. You will
1634 need to create a /boot/device.hints or add a hints directive
1635 to your config file to compile them in statically. The format
1636 of the config file has changed as well. Please see GENERIC or
1637 NEWCARD for examples of the new format.
1639 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1640 says that it has been fixed, assume that must use the hints mechanism
1641 in the loader if you need to use a machine with very old ISA cards
1645 A new set of binutils went into the tree today. Anybody
1646 building a kernel after this point is advised that they need
1647 to rebuild their binutils (or better yet do a
1648 buildworld/installworld) before building a new kernel.
1650 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1651 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1652 is recommended that you don't set this option until the problem
1656 The ethernet drivers were all updated to clean up the BPF handling.
1659 The problems with boot blocks on the alphas have been corrected.
1660 This will require some care in updating alphas. A new libstand
1661 is requires for the boot blocks to build properly.
1664 Recompile all kld modules. Proper version dependency info
1668 Modules have been disconnected from the buildworld tree and
1669 connected to the kernel building instead.
1672 You may need to build gperf
1673 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1674 when upgrading from 4.0 -> current. The build system now uses
1675 an option only in -current.
1678 The method that we brand ELF binaries has changed to be more
1679 acceptable to the binutils maintainers. You will need to
1680 rebrand your ELF binaries that aren't native. One problem
1681 binary is the Linux ldconfig. After your make world, but
1682 before you reboot, you'll need to issue:
1683 brandelf -t Linux /compat/linux/sbin/ldconfig
1684 if you have Linux compatibility enabled on your machine.
1687 If you have really bad/marginal IDE drives, you may find they
1688 don't work well. Use pio mode instead. The easiest way to
1689 cope if you have a problem combination is to add:
1690 /sbin/sysctl hw.ata.ata_dma=0
1691 to the start of /etc/rc.conf.
1694 The ISA and PCI compatibility shims have been connected to the
1695 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1696 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1697 include the appropriate option in your kernel config. Drivers
1698 using the shims should be updated or they won't ship with
1699 5.0-RELEASE, targeted for 2001.
1702 We've entered the traditional post release dumping party.
1703 Large kernel changes are being committed and are in the
1704 works. It is important to keep the systems' klds and kernel
1705 in sync as kernel interfaces and structures are changing.
1706 Before reporting kernel panics, make sure that all modules
1707 that you are loading are up to date.
1710 If you are upgrading from an older version of FreeBSD, you
1711 need to update your boot blocks as well. 'disklabel -B ad0'
1712 will do the trick. This isn't critical until you remove your
1713 wd device entries in /dev, at which point your system will not
1717 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1718 to upgrade to 4.0 from 3.x.
1722 # NOTE: 5.x below applies to 6.0-currrent as well, for the
1723 # momemnt. 4.any -> 5.any upgrade support will remain in
1724 # place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1725 # 6.0-current upgrade path will require moving through 5.3
1730 Avoid using make -j when upgrading. From time to time in the
1731 past there have been problems using -j with buildworld and/or
1732 installworld. This is especially true when upgrading between
1733 "distant" versions (eg one that cross a major release boundary
1734 or several minor releases, or when several months have passed
1735 on the -current branch).
1737 Sometimes, obscure build problems are the result of environment
1738 poisoning. This can happen because the make utility reads its
1739 environment when searching for values for global variables.
1740 To run your build attempts in an "environmental clean room",
1741 prefix all make commands with 'env -i '. See the env(1) manual
1742 page for more details.
1746 If you are updating from a prior version of FreeBSD (even one just
1747 a few days old), you should follow this procedure. With a
1748 /usr/obj tree with a fresh buildworld,
1749 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1750 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1752 To just build a kernel when you know that it won't mess you up
1753 --------------------------------------------------------------
1754 This assumes you are already running a 5.X system. Replace
1755 ${arch} with the architecture of your machine (e.g. "i386",
1756 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1758 cd src/sys/${arch}/conf
1759 config KERNEL_NAME_HERE
1760 cd ../compile/KERNEL_NAME_HERE
1765 If this fails, go to the "To build a kernel" section.
1767 To rebuild everything and install it on the current system.
1768 -----------------------------------------------------------
1769 # Note: sometimes if you are running current you gotta do more than
1770 # is listed here if you are upgrading from a really old current.
1772 <make sure you have good level 0 dumps>
1773 <maybe fix /etc/fstab> [7]
1775 make kernel KERNCONF=YOUR_KERNEL_HERE
1777 <reboot in single user> [3]
1778 src/etc/rc.d/preseedrandom [10]
1785 To cross-install current onto a separate partition
1786 --------------------------------------------------
1787 # In this approach we use a separate partition to hold
1788 # current's root, 'usr', and 'var' directories. A partition
1789 # holding "/", "/usr" and "/var" should be about 2GB in
1792 <make sure you have good level 0 dumps>
1795 <maybe newfs current's root partition>
1796 <mount current's root partition on directory ${CURRENT_ROOT}>
1797 make installworld DESTDIR=${CURRENT_ROOT}
1798 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1799 cp src/sys/${ARCH}/conf/GENERIC.hints \
1800 ${CURRENT_ROOT}/boot/device.hints # as needed
1801 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1802 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1803 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1804 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1805 <reboot into current>
1806 <do a "native" rebuild/install as described in the previous section>
1807 <maybe install compatibility libraries from src/lib/compat>
1811 To upgrade in-place from 4.x-stable to current
1812 ----------------------------------------------
1813 # 5.x uses more space than 4.x. Also, the location of kernel
1814 # modules has changed. If you are installing 5.x onto a 4.x
1815 # system, you'll need about 30MB of free disk space on your /
1816 # partition. If you have less than this, you may encounter difficult
1817 # to back out of problems with this procedure. If /tmp is on
1818 # the / partition, you may want to completely remove all its content
1819 # before upgrading, as this can be a common source of shortage of
1822 <make sure you have good level 0 dumps>
1823 <maybe fix /etc/fstab> [7]
1825 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1826 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1827 cd sys/boot ; make STRIP="" install [6]
1829 <reboot in single user> [3]
1830 src/etc/rc.d/preseedrandom [10]
1832 rm -rf /usr/include/g++
1837 Make sure that you've read the UPDATING file to understand the
1838 tweaks to various things you need. At this point in the life
1839 cycle of current, things change often and you are on your own
1840 to cope. The defaults can also change, so please read ALL of
1841 the UPDATING entries.
1843 Also, if you are tracking -current, you must be subscribed to
1844 freebsd-current@freebsd.org. Make sure that before you update
1845 your sources that you have read and understood all the recent
1846 messages there. If in doubt, please track -stable which has
1847 much fewer pitfalls.
1849 [1] If you have third party modules, such as vmware, you
1850 should disable them at this point so they don't crash your
1853 [2] If you have legacy ISA devices, you may need to create
1854 your own device.hints to reflect your unique hardware
1857 [3] From the bootblocks, boot -s, and then do
1862 adjkerntz -i # if CMOS is wall time
1863 Also, when doing a major release upgrade, it is required that
1864 you boot into single user mode to do the installworld.
1865 For the 4.x -> 5.x upgrade, you will also see many messages about
1866 needing to recompile your userland. These are harmless and can
1867 be ignored while you proceed to the next step.
1869 [4] Note: This step is non-optional. Failure to do this step
1870 can result in a significant reduction in the functionality of the
1871 system. Attempting to do it by hand is not recommended and those
1872 that pursue this avenue should read this file carefully, as well
1873 as the archives of freebsd-current and freebsd-hackers mailing lists
1874 for potential gotchas.
1876 [5] Usually this step is a noop. However, from time to time
1877 you may need to do this if you get unknown user in the following
1878 step. It never hurts to do it all the time. You may need to
1879 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1880 install) after the buildworld before this step if you last updated
1881 from current before 20020224 or from -stable before 20020408.
1883 [6] 4.x boot loader can be used to boot a 5.x system, however
1884 it is difficult to do that at best. If you wish to try, then
1885 you should interrupt the boot and at the ok prompt type:
1887 ok boot /boot/kernel/kernel
1888 If this fails to work, you must install a new boot loader as
1891 [7] Before you upgrade, please make sure that you are not using
1892 compatibility slices. These are device names of the form /dev/ad0a
1893 without the actual slice name. These will break with 5.x and newer.
1894 You generally must update these entries to use the post FreeBSD
1895 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1898 [8] In order to have a kernel that can run the 4.x binaries
1899 needed to do an installworld, you must include the COMPAT_FREEBSD4
1900 option in your kernel. Failure to do so may leave you with a system
1901 that is hard to boot to recover.
1903 Make sure that you merge any new devices from GENERIC since the
1904 last time you updated your kernel config file.
1906 [9] When checking out sources, you must include the -P flag to have
1907 cvs prune empty directories.
1909 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1910 "?=" instead of the "=" assignment operator, so that buildworld can
1911 override the CPUTYPE if it needs to.
1913 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1914 not on the command line, or in /etc/make.conf. buildworld will
1915 warn if it is improperly defined.
1917 In case you would like to avoid installing new packages of everything,
1918 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1919 compatibility libraries are built which should allow you to continue
1920 using your existing software for a while. Alternatively, you can
1921 install the misc/compat4x port.
1923 [10] In order to create temporary files, /dev/random must be
1924 initialized by feeding data into it. src/etc/rc.d/preseedrandom
1928 This file contains a list, in reverse chronological order, of major
1929 breakages in tracking -current. Not all things will be listed here,
1930 and it only starts on March 15, 2000. Updating files can found in
1931 previous releases if your system is older than this.
1933 Copyright information:
1935 Copyright 1998-2004 M. Warner Losh. All Rights Reserved.
1937 Redistribution, publication, translation and use, with or without
1938 modification, in full or in part, in any form or format of this
1939 document are permitted without further permission from the author.
1941 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1942 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1943 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1944 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1945 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1946 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1947 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1948 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1949 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1950 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1951 POSSIBILITY OF SUCH DAMAGE.
1953 If you find this document useful, and you want to, you may buy the
1956 Contact Warner Losh if you have any questions about your use of