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 If enabled, the default is now to run named in a chroot
28 "sandbox." For users with existing configurations in
29 /etc/namedb the migration should be simple. Upgrade your
30 world as usual, then after installworld but before
31 mergemaster do the following:
33 If named is running: /etc/rc.d/named stop
36 mkdir -p /var/named/etc/namedb
37 cp -Rp namedb.bak/* /var/named/etc/namedb/
38 mergemaster (with your usual options)
39 If using the generated localhost* files:
40 cd /var/named/etc/namedb
41 /bin/sh make-localhost
42 rm -f localhost-v6.rev localhost.rev
45 If you are using a custom configuration, or if you have
46 customised the named_* variables in /etc/rc.conf[.local]
47 then you may have to adjust the instructions accordingly.
48 It is suggested that you carefully examine the new named
49 variables in /etc/defaults/rc.conf and the options in
50 /var/named/etc/namedb/named.conf to see if they might
54 BIND 9 has been imported into the base, and is now fully
55 functional. BIND 8 has now been removed. There are numerous
56 differences between BIND 8 and 9, and users with critical
57 named installations should read the migration documentation
58 in /usr/share/doc/bind9/misc/migration. There is also a
59 new instruction manual in /usr/share/doc/bind9/arm.
61 The key differences that most users will experience are in
62 how picky BIND 9 is about zone file format. If you are using
63 named as a resolving (caching) name server, you will likely
66 The following files are part of the old BIND 8 installation
67 and should be removed:
68 /usr/bin/dnskeygen /usr/bin/dnsquery /usr/libexec/named-xfer
69 /usr/sbin/named.restart /usr/sbin/ndc
71 The following files have moved to /usr/bin, and should be
72 removed from their old locations:
73 /usr/sbin/nslookup /usr/sbin/nsupdate
76 The format of the pflogd(8) logfile "/var/log/pflog" has changed for
77 architectures that have a 64 bit long type to make it compatible to
78 the standard pcap format. In order to prevent corruption move away
79 any old logfile before using a new pflogd(8).
82 debug.witness_* has been renamed to debug.witness.*. There are
83 compatibility tunables left in for a few days. Update loader.conf
87 The ifi_epoch change has been reverted because the ABI breakage
88 was too extensive. If you are running with a kernel/userland
89 containing the initial change (20040830), you should heed the
90 warning about ifconfig incompatibility when upgrading again.
91 With this change, 5.3 and 6.0 ifconfigs and kernels are once
95 A new variable, ifi_epoch, has been added to struct if_data
96 which is part if struct ifnet. This means all network drivers
97 and network monitoring applications need to be recompiled.
99 WARNING WARNING WARNING WARNING WARNING WARNING WARNING
101 This also breaks ifconfig compatibility. An old ifconfig will
102 not work with the new kernel and a new ifconfig will not work
103 with the old. It is strongly recommended that you make a copy
104 of your old ifconfig before installworld. If you are installing
105 remotely, you must copy over a new ifconfig before rebooting in
109 The default configuration for the network stack has been changed
110 such that it now runs without the Giant lock unless configured
111 otherwise. If you experience network-related instability, you
112 may wish to try setting "debug.mpsafenet=0" or compiling the
113 kernel with "options NET_WITH_GIANT". Details on the netperf
114 project may be found at:
116 http://www.watson.org/~robert/freebsd/netperf/
118 Including the 20040828 announcement of configuration change
122 PFIL_HOOKS are a fixed part of the network stack now and do not
123 need to be specified in the kernel configuration file anymore.
126 Netgraph changed its message format slightly to align the data
127 portion well on 64 bit machines.
128 Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
129 pppoed, bluetooth, ATM) should be recompiled when a new kernel
133 IPFW has been converted to use PFIL_HOOKS. This change is
134 transparent to userland and preserves the ipfw ABI. The ipfw
135 core packet inspection and filtering functions have not been
136 changed, only how ipfw is invoked is different. Note that
137 "option PFIL_HOOKS" is required to use IPFIREWALL compiled
138 into the kernel or as KLD.
141 The RANDOM_IP_ID option has been replaced by the sysctl
142 net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
143 you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
146 The size of 'struct ifnet' has changed due to the addition of the
147 if_carp placeholder. All kernel modules implementing network
148 interfaces must be recompiled as a result.
151 Module loading has been fixed. Some older installations will
152 drop proper module_path initialization and modules will fail to
153 load properly. If you have a line in /boot/loader.rc that says:
154 "initialize drop", do (i386 only):
155 cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
156 chown root:wheel /boot/loader.rc
157 chmod 444 /boot/loader.rc
160 making /dev/(null|zero) into a module proved to be too unpopular,
161 so this bit has been revoked from the previous (20040801) entry.
164 The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
165 so you may wish to add them to your kernel config file. See
166 GENERIC for examples.
169 System compiler has been upgraded to GCC 3.4.2-pre. As with any major
170 compiler upgrade, there are several issues to be aware of. GCC 3.4.x
171 has broken C++ ABI compatibility with previous releases yet again
172 and users will have to rebuild all their C++ programs with the new
173 compiler. If you are getting run-time error such as
174 /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
175 This entry does apply to you.
177 A new unit-at-a-time optimization mode, which is default in this
178 compiler release, is more aggressive in removing unused static
179 symbols. This is the likely cause of 'make buildworld' breakages
180 with non-default CFLAGS where optimization level is set to -O2
183 With the upgrade of the system compiler, the kernel has been upgraded
184 to match the new system compiler. This makes it impossible to build
185 a new kernel with the old compiler. Upgrade your system via
186 make buildworld and make kernel (see below) to fix this problem.
189 The size of 'struct ifnet' has changed due to the addition of
190 the IFF_NEEDSGIANT flag (and what it implies). All kernel
191 modules implementing network interfaces must be recompiled as
195 The sound device drivers are renamed. `sound' is always required,
196 while `snd_*' should be configured accordingly to your hardware.
197 Refer to NOTES for the detail of the drivers.
200 __FreeBSD_version bumped to 502122.
203 The console initialization on Alpha has been reworked and is now
204 identical to other platforms. This means that the hardcoding of
205 the serial console and the debug port has been removed. As such,
206 hints are now required for the sio(4) driver to become a console
207 or debug port. The NO_SIO option has been decommissioned because
211 A revamp of the debugging code in the kernel with some visible
212 changes beyond just the debugging experience:
213 o The DDB option is now specific to the DDB debugger backend
214 and should not be used any more for conditional compilation
215 of debugging code for when debugging is enabled. Use the KDB
217 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
218 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
219 respectively. This is in line with the first bullet.
220 o The remote GDB support has been untangled from DDB and needs
221 to be enabled separately now. Use the GDB option for this.
222 o The GDB_REMOTE_CHAT option has been removed. Support for this
223 homegrown feature is discontinued. The GDB remote protocol
224 supports console output and it makes sense to use that.
225 o The DDB_NOKLDSYM option has been removed. The DDB debugger
226 now supports both direct symbol table lookups as well as KLD
227 symbol lookups through the linker.
230 Bluetooth code has been marked as non-i386 specific.
231 __FreeBSD_version has been bumped to 502121 to mark this change.
234 The native preemption has been added to the kernel scheduler.
235 There is some report that the ULE scheduler was broken in some
236 machines and we encourage users using the ULE scheduler either
237 stick with a known good kernel, or temporarily switch to the 4BSD
238 scheduler as a workaround.
241 The netgraph ABI version number has been incremented to indicate
242 an incompatible change in the ABI. Old netgraph nodes will refuse
243 to attach until recompiled. Netgraph now uses mbuf tags to move
244 metadata and this commit removes its home-grown metadata facility.
245 Nodes should just recompile, unless they use metadata, in which
246 case the changes are simple; the file ng_ksocket.c serves as an
247 example of such changes.
249 This also broke i4b, although the compile problem has been papered
253 ACPI has been updated to disable known-bad BIOS revisions. A message
254 will be printed on the console indicating that ACPI has been disabled
255 automatically and that the user should use a newer BIOS, if possible.
256 If you think ACPI does work on your system and want to override
257 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
261 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
262 separated now. It uses the newly created "_pflogd" user/group
263 combination. If you plan to use pflogd(8) make sure to run
264 mergemaster -p or install the "_pflogd" user and group manually.
267 Network interface cloning has been overhauled. This change will
268 require a recompile of modules using cloning and modification of
269 external ones to the new API. __FreeBSD_version has been bumped
270 to 502119 to mark this change. Additionally, users creating
271 stf(4) interfaces via "ifconfig stf" will need to update their
272 scripts as this will create an interface named "stf" instead of
273 "stf0" and ifconfig will not print "stf0" to stdout.
276 On 20040524, the /etc/rc.d/nsswitch script was modified to
277 automatically create /etc/nsswitch.conf on startup if it did
278 not already exist. Unfortunately, an error in the man page
279 was carried over to the script, resulting in incorrect
280 nsswitch settings. The simplest remedy is to remove both
281 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
282 during the next reboot.
285 The return value of sema_timedwait(9) has been changed to
286 make it consistent with cv_timedwait(9). Be sure to recompile
287 the ips module and any third-party modules which call
291 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
292 Make sure to recompile modules and any userland that makes use of
293 sizeof(struct ifnet). In order to get the altq headers in place
294 please recompile and reinstall world.
297 Splitting kern_thread.c into 2 files (adding kern_kse.c)
298 requires that you re-run config after updating your tree.
301 The MIDI drivers have been removed. Until the new module-friendly
302 ones are merged, remove or comment out midi and seq from your
303 kernel configuration.
306 Due to a new option in ipfw (versrcreach) the ipfw(8) command
307 needs to be recompiled. Normal accept/reject rules without
308 options are not affected but those with options may break until
309 ipfw(8) is recompiled.
312 Due to changes in the callout ABI, kernels compiled after this
313 date may be incompatible with kernel modules compiled prior to
317 The PCI bus power state stuff has been turned on. If this causes
318 problems for your system, please disable it using the tunable
319 hw.pci.do_powerstate=0.
322 The bulk of the pci problems have been fixed, although the floppy
323 drive is still broken.
326 A substantial update to the pci bus resource and power management
327 have been committed. Expect a bumpy ride for a few days until
328 the unanticipated problems have been resolved.
331 Due to changes in the the Yarrow initialization process,
332 /dev/random needs to be fed before operations requiring
333 temp files can succeed in single user mode. This includes
334 running "make installworld". /dev/random may be fed by running
335 "/etc/rc.d/initrandom start" or with 20040415 source by running
336 "/etc/rc.d/preseedrandom".
339 The debug.mpsafenet tunable controls whether the kernel Giant
340 lock is held across the lower levels of the network stack, and
341 by default is turned off. In the few days following 20040322,
342 the behavior of debug.mpsafenet will change such that this
343 tunable controls Giant over all levels of the network stack.
344 If you are currently setting debug.mpsafenet to 1, you should
345 set it back to 0 (the default) again during the change-over.
346 An additional note will be added to UPDATING when sufficient
347 locking is merged to permit this to take place.
350 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
351 64-bits. This is a very major incompatible change, so people
352 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
353 detailed instructions on how to make this upgrade. People
354 upgrading FreeBSD on other platforms can ignore this event.
357 The packet filter (pf) is now installed with the base system. Make
358 sure to run mergemaster -p before installworld to create required
359 user account ("proxy"). If you do not want to build pf with your
360 system you can use the NO_PF knob in make.conf.
361 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
362 pf system consists of the following three devices:
364 device pflog # optional
365 device pfsync # optional
368 If you are having trouble with the libc_r -> libpthread transition
369 (see the 20040130 entry), place the following lines at the top of
372 libc_r.so.5 libpthread.so.1
373 libc_r.so libpthread.so
375 This will cause all programs and libraries linked against libc_r
376 to use libpthread instead.
379 Some sshd configuration defaults have changed: protocol version 1
380 is no longer enabled by default, and password authentication is
381 disabled by default if PAM is enabled (which it is by default).
382 OpenSSH clients should not be affected by this; other clients may
383 have to be reconfigured, upgraded or replaced.
386 The ABIs defined in <resolv.h> and <netdb.h> have been updated
387 to support improved reentrancy. Multi-threaded programs that
388 reference the "_res" or "h_errno" symbols may experience some
389 problems if they are not recompiled. Single-threaded programs
390 should remain unaffected.
393 routed has been updated in the base system from the vendor
394 sources, routed v2.27, from rhyolite.com. This change means that
395 for users who use RIP's MD5 authentication feature, FreeBSD
396 -CURRENT's routed is now incompatible with previous versions
397 of FreeBSD; however it is now compatible with implementations
398 from Sun, Cisco and other vendors.
401 The tcpcb structure has changed and makes a recompile of libkvm
402 and related userland network utilities necessary.
405 The cdevsw structure has changed in two externally visible ways.
406 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
407 Second, the d_version field must be filled in with D_VERSION.
408 Drivers outside the tree will need to be updated.
411 The /etc/rc.d/ttys script has been removed. It is no longer
412 necessary since devfs has been mandatory for some time.
415 libkse has been renamed back to libpthread and is now the
416 default threads library. The gcc -pthread option has also
417 been changed to link to libpthread instead of libc_r. For
418 alpha and sparc64 machines, libkse is not renamed and links
419 are installed so that libpthread points to libc_r. Until
420 the ports system is updated to handle this change, it is
421 recommended that folks install an /etc/libmap.conf(5) that
422 maps libc_r to libpthread. If you have any binaries or
423 libraries linked to libkse, then it is also recommended
424 that you map libkse to libpthread. Anyone that is using
425 nvidia supplied drivers and libraries should use a libmap.conf
426 that maps libpthread to libc_r since their drivers/libraries
427 do not work with libpthread.
430 ULE has entered into its probationary period as the default scheduler
431 in GENERIC. For the average user, interactivity is reported to be
432 better in many cases. On SMP machines ULE will be able to make more
433 efficient use of the available parallel resources. If you are not
434 running it now, please switch over, replacing the kernel option
435 SCHED_4BSD with SCHED_ULE.
438 Move LongRun support out of identcpu.c, where it hardly
439 belongs, into its own file and make it opt-in, not mandatory,
440 depending on CPU_ENABLE_LONGRUN config(8) option.
443 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
444 if the login process is unable to successfully set the
445 process credentials to include all groups defined for the
446 user. The current kernel limit is 16 groups; administrators
447 may wish to check that users do not have over 16 groups
448 defined, or they will be unable to log in.
451 The ACPI module has been reactivated. It is no longer required
452 to compile ACPI support into kernels statically.
455 The statfs structure has been updated with 64-bit fields to
456 allow accurate reporting of multi-terabyte filesystem
457 sizes. You should build world, then build and boot the new kernel
458 BEFORE doing a `installworld' as the new kernel will know about
459 binaries using the old statfs structure, but an old kernel will
460 not know about the new system calls that support the new statfs
462 Note that the backwards compatibility is only present when the
463 kernel is configured with the COMPAT_FREEBSD4 option. Since
464 even /bin/sh will not run with a new kernel without said option
465 you're pretty much dead in the water without it. Make sure you
466 have COMPAT_FREEBSD4!
467 Running an old kernel after a `make world' will cause programs
468 such as `df' that do a statfs system call to fail with a bad
469 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
470 that cfsd (ports/security/cfs) needs to be recompiled after
471 these changes are installed.
473 ****************************DANGER*******************************
475 DO NOT make installworld after the buildworld w/o building and
476 installing a new kernel FIRST. You will be unable to build a
477 new kernel otherwise on a system with new binaries and an old
481 Some netgraph string length constants have been changed. This
482 change requires the netgraph kernel modules and all netgraph
483 userland components to be in sync. Especially users who require
484 netgraph to boot need to make sure to have world and kernel in
485 sync before rebooting.
488 Hyperthreading logical CPU's are no longer probed by default
489 when using the MP Table. If ACPI is being used, then logical
490 CPUs will be probed if hyperthreading is enabled in the BIOS.
491 If ACPI is not being used and hyperthreading is enabled in the
492 BIOS, logical CPUs can be enabled by building a custom kernel
493 with the option MPTABLE_FORCE_HTT enabled.
496 The i386 APIC_IO kernel option has been replaced by
497 'device apic'. The ACPI module has also been temporarily
498 disabled, so ACPI must be statically compiled into your
499 kernel using 'device acpi' if you wish to use the ACPI driver.
502 The API and ABI of struct ifnet have been changed by removing
503 the if_name and if_unit members and replacing them with
504 if_xname, if_dname, and if_dunit. All network drivers and most
505 userland programs which include net/if_var.h must be updated
506 and recompiled. __FreeBSD_version has been bumped to 501113 to
510 Changes to the cdevsw default functions have been made to remove
511 the need to specify nullopen() and nullclose() explicitly.
512 __FreeBSD_version bumped to 501110.
515 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
516 mount_cd9660(8) need to be in sync with kernel.
519 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
520 also be explicitly configured. Previously this dependency was
521 magically handled through some cruft in net/pfil.h; but that has
522 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
523 will fail with obtuse errors in ip_fil.c.
526 Fix a bug in arplookup(), whereby a hostile party on a locally
527 attached network could exhaust kernel memory, and cause a system
528 panic, by sending a flood of spoofed ARP requests. See
529 FreeBSD-SA-03:14.arp.
532 A change to /etc/defaults/rc.conf now causes inetd to be started
533 with `-C 60' if it is not overridden in /etc/rc.conf. This
534 causes inetd to stop accepting connections from an IP address
535 that exceeds the rate of 60 connections per minute.
538 The following rc.d scripts have been removed and should be
539 deleted from your installation: atm2.sh atm3.sh devdb
540 localdaemons network1 network2 network3. Depending on when
541 you last updated world and used mergemaster(8) you may or
542 may not have problems during the rc boot sequence. The simplest
543 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
544 The atm2.sh atm3.sh and devdb scripts were removed some time
545 ago, so depending on when you installed -CURRENT these scripts
546 may or may not exist on your system.
549 ATAng has been committed. You need to build world as sys/ata.h
550 has changed, and userland atacontrol depends on it.
551 If you use ATA SW raids you need "device ataraid" in your
552 kernel config file, as it is no longer pulled in automatically.
555 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
556 Among other things, this changes the device enumeration to be
557 closer to Solaris. Be aware that, this can even cause the machine
558 to not boot without manual intervention before the fstab is adjusted.
561 All current USB and Firewire quirks in da(4) have been deprecated
562 and will be removed for 5.2. If this causes failure for your
563 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
564 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
565 so the quirk can be re-enabled.
568 Problems with entry 20030714 have been corrected and no known issues
569 with /rescue and -j exist for host systems after this point in time.
572 FPU-less support has been removed from FreeBSD. Chances are you won't
573 notice. 386+387 support should still work after this change, but
574 it is now a minimum requirement for the i386 port that you have real
578 Some people are having problems with changes related to /rescue.
579 If you are building -j N, you will need to define NO_RESCUE. Others
580 will need to define it if /rescue has issues with their environment.
581 People should report those issues to current@.
584 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
585 across this point. Further, it might be a good idea to remove
589 Remove deprecated locale names and transition period code
590 for them, finishing switching to the new scheme. Check your
591 LANG environment variable.
594 CCD has been changed to be a fully GEOMified class. Kernel
595 and ccdconfig(8) needs to be in sync, this is particularly
596 important to remember beforehand if your source tree is on
597 a ccd device. Consider making a copy of the old ccdconfig
598 into /boot/kernel.good or wherever you keep your backup
602 There was a small window in which sed(1) was broken. If you
603 happen to have sed(1) installed during that window, which is
604 evidenced by an inability to build world with the failure
605 given below, you need to manually build and install sed(1)
606 (and only sed(1)) before doing anything else. This is a one-
607 time snafu. Typical failure mode:
609 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
610 targmatch.h:7:1: null character(s) ignored
611 targmatch.h:12:1: null character(s) ignored
612 targmatch.h:16:1: null character(s) ignored
615 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
616 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
617 usr.bin/sed/process.c).
620 Kerberos 5 (Heimdal) is now built by default. Setting
621 MAKE_KERBEROS5 no longer has any effect. If you do NOT
622 want the "base" Kerberos 5, you need to set NO_KERBEROS.
625 groff has been updated. If you try to do a buildworld and
626 get an infinite loop in troff, update to May 4th or newer. If you
627 have a newer kernel than userland, you may need to set the OSRELDATE
628 to 500110 in your environment before starting a buildworld.
631 The old rc system has been removed. Please report any problems
632 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
633 Your personal versions of these files will not be removed, so you can
634 continue to use them. However, you should take great care when updating,
635 especially when using mergemaster, since the compatibility code that
636 utilizes these old scripts has also been removed.
639 A bug has been fixed in /dev/devctl which would cause devd
640 to hang on boot, were it not for a workaround in devd. The
641 work around in devd will be removed around 20030507. You
642 have until then to upgrade your kernel before updating
643 userland. In general, you should have a userland and
644 kernel that's in sync with each other. However, given the
645 effects of this bug (hang on boot when starting devd), some
649 Alphas with libc from between 20030312 and 20030329 exhibit
650 floating point exceptions (FPEs), most notably in awk(1)
651 while upgrading the system through a buildworld.
653 So, to successfully upgrade your Alpha, you must either
654 downgrade your libc.so to a pre-20030312 version, or update
655 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
656 to CFLAGS, then forcibly rebuild and install libc:
658 cd /usr/src/lib/libc && \
659 make cleandir && make obj && \
660 make -DNOMAN -DNOPROFILE all && \
661 make -DNOMAN -DNOPROFILE install
664 sendmail 8.12.7 has been imported. It has one important
665 change for IPv6 users. The default submit.mc now uses
666 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
667 used to connect to the MTA. Users on IPv6-only machines
668 will need to edit /etc/mail/submit.mc appropriately.
671 NODEVFS option has been removed and DEVFS thereby made standard.
672 This makes all references to MAKEDEV obsolete, and they should
673 be removed when convenient.
676 The name of the device for the ofw console has changed, sparc64 users
677 must run mergemaster to update their installed /etc/ttys.
680 The scheduler framework has grown a second scheduler and consequently
681 you must specify one and only one scheduler in your kernel config.
682 The cvs config files have been updated to use the old scheduler
683 which may be selected via 'options SCHED_4BSD'. If you would like
684 to try the new, much more experimental, scheduler please try
685 'options SCHED_ULE' and contribute to the arch@ discussion.
688 A new version of the wi driver has been imported into the tree.
689 One now must have device wlan in the config file for it to operate
692 In addition, there have been some changes to how wi devices are
693 configured for point to point links to bring it more in line
694 with the former way of doing things, as well as compatibility
698 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
699 used an incompatible form of ABI for returning structures and unions
700 which FreeBSD's GCC maintainers were not aware of relative to previous
701 versions of FreeBSD. We have gone back to the ABI for now, and any
702 code compiled which is required to interoperate with other code (not
703 built at the same time) returning structs or unions should be
707 A name change in /etc/netconfig has been reverted to stay
708 compatible with suns TIRPC and also with NetBSD. You need
709 to run mergemaster after make world. A new libc does still work
710 with an outdated /etc/netconfig for some time, but you'll get
711 a warning. This warning will be removed in 20030301.
714 The recent binutils upgrade marks a kernel flag day on
715 sparc64: modules built with the old binutils will not work
716 with new kernels and vice versa. Mismatches will result in
717 panics. Make sure your kernel and modules are in sync.
720 The value of IPPROTO_DIVERT has changed. Make sure to keep
721 your kernel, netstat, natd and any third-party DIVERT
725 Old, compatibility slices have been removed in GEOM kernels.
726 This means that you will have to update your /etc/fstab to
727 not use disk devices of the form /dev/ad0a. Instead, you
728 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
729 partition really is on. The old device names have gone
730 away, so if you use them anywhere else, you must also adjust
731 those uses. (This doesn't affect the disks formatted in
732 the ``dangerously-dedicated'' mode.)
735 Alphas with kernels from between 20020830 and 20021023 and/or
736 rtld (ld-elf.so.1) older than 20021023 may experience problems
737 with groff while doing a buildworld (kernel: "out of memory",
738 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
739 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
741 So, to successfully upgrade your Alpha, you must either
742 upgrade your kernel and rtld first (which might be a bit
743 tricky), or avoid running the bootstrapped groff during the
744 "transitional" buildworld. To avoid running groff during the
745 transitional upgrade run make buildworld with -DNOMAN,
746 -DNO_SHAREDOCS, and -DNO_LPR.
749 gcc has been upgraded to 3.2. It is not all binary compatible
750 with earlier versions of gcc for c++ programs. All c++
751 programs and libraries need to be recompiled.
753 Also, if you encounter g++ issues, rm /usr/include/g++/* before
754 doing an installworld to make sure that stale files are removed.
757 Our /etc/termcap now has all the entries from the XFree86 xterm
758 almost unchanged. This means xterm now supports color by default.
759 If you used TERM=xterm-color in the past you now should use
760 TERM=xterm. (xterm-color will lead to benign warnings).
763 A "bug" in gcc(1) that was hiding warning in system headers was
764 fixed. It's probably time to add -DNO_WERROR to your make line
768 COPY is being deprecated. The 20010530 change was reverted, as
769 it causes far more pain than was expected, and to always compare
770 before installing, please use INSTALL="install -C" again. The
771 -C option is now silently ignored when used with the -d option.
774 Problems with libc_r clients like KDE and GNOME have been resolved.
775 There are still some minor problems with some signals but the
776 system is stable enough for general use again. SMP is less so than UP
777 but each can successfully complete multiple buildworlds.
778 Libkvm needs to be recompiled due to KSE.
781 Now would be a bad time to upgrade. Something in or near the
782 KSE commit totally broke programs using libc_r like KDE and
786 The k5su utility installed as part of Kerberos 5 is no longer
787 installed with the set-user-ID bit set by default. Add
788 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
789 with the set-user-ID bit set.
792 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
793 Unfortunately our native GDB (at version 4.18) does not understand
794 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
795 generated debugging information for our native GDB.
798 Due to the way CVS works, it may not properly update src/contrib/gcc
799 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
800 and then do a cvs update.
803 When exec'ing set[ug]id executables, the kernel now ensures that the
804 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
807 New sendmail startup scripts have been installed to make it
808 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
809 variable sendmail_enable to "NO" no longer prevents any sendmail
810 daemons from starting. Instead, either set sendmail_enable to
811 "NONE" or change mta_start_script to a script for starting
812 an alternative MTA. Setting mta_start_script to "" will
813 also prevent any MTA from being started at boot.
816 UCONSOLE is no longer a valid kernel option.
819 FreeBSD 5.0 DP-1 was basically branched today.
822 Warnings are now errors in the kernel. Unless you are a developer,
823 you should add -DNO_WERROR to your make line.
826 sendmail 8.12.2 has been imported. The sendmail binary is no
827 longer a set-user-ID root binary and the infrastructure to support
828 command line mail submission has changed. Be sure to run
829 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
830 and /etc/mail) and read /etc/mail/README for more details.
832 Due to the import of sendmail 8.12.2, a new user and group are
833 required in order for sendmail to run as a set-group-ID
834 binary. A 'make installworld' will use the new user and group
835 to set the owner and group of /var/spool/clientmqueue and will
836 fail if the new user and group do not exist. The 'smmsp' user
837 and group must be merged from src/etc/group and
838 src/etc/master.passwd before using 'make installworld'.
839 'mergemaster -p' will do this. You may need to install
840 mergemaster before this will work if you are updating from a
841 very old version of current. The updating recipe has changed
845 The preferred configuration method for PAM is now /etc/pam.d/
846 rather than /etc/pam.conf. If you have an unmodified
847 pam.conf, just delete it after your next mergemaster run. If
848 you have local modifications, you can use
849 /usr/src/etc/pam.d/convert.pl to incorporate them into your
852 Please see the following url for more details:
853 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
855 If anyone here is already using the new rc.conf(5) variable
856 networkfs_types, please note that it has changed
857 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
860 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
861 started out its life in the ISDN4BSD project as an offspring
862 from sys/net/if_spppsubr.c, which eventually got a life of its
863 own. All the accumulated features and bug fixes of the i4b
864 version have now been merged back into the base system's
865 version now. The only user-visible change resulting from this
866 is that i4b's sppp(4) interfaces are to be managed with
867 spppcontrol(8) again, since ispppcontrol(8) has been retired
868 as well. (There has never been rc file support for
869 ispppcontrol in -current, but only in -stable. That will be
870 reverted by the time the changes are MFCed.)
873 The fdc(4) driver has been updated and now automatically
874 recognizes media in `standard' formats (like 1440 KB and
875 720 KB for a 3.5" high-density drive) when accessing the
876 default device node (e. g. /dev/fd0). The old variety of
877 floppy device nodes /dev/fd*.* is no longer present by
878 default, devices can be created (in DEVFS) on demand. They
879 will need to be customized then for `odd' densities using
883 The bugs in procfs' debugging support code have been fixed,
884 and truss(1) now works again.
887 Daily security checks have been split out to use the periodic(8)
888 scripts. Some change in configuration may be necessary. Please
890 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
894 sos added VCD/SVCD support to ata driver and that needs the
895 kernel and burncd to be in sync.
898 The procfs pseudo-filesystem has now been converted to use the
899 pseudofs framework. If you have 'options PROCFS' in your
900 kernel config, you'll need to add 'options PSEUDOFS' if it's
903 This change temporarily breaks truss(1); use ktrace(1) instead
904 until the issue has been resolved.
907 A security hole in OpenSSH involving `UseLogin yes' has been
911 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
912 after this date. You need to do this only once.
915 Most of the awk issues have been resolved. Some rough
916 edges may be left, but for the most part things should be
917 back to "normal." For CURRENT's usual definition of "normal."
920 Awk has been upgraded to the one true awk from bell labs. Expect
921 choppy waves in the upgrade process.
924 The asr driver problem has been resolved.
927 Due to changes in other parts of the system, the asr driver
928 now causes the system to panic on boot. Do not use it pending
929 correction. Comment it out of any kernel config file that you
930 try to use from this date forward.
933 When crossbuilding, use TARGET=xxx where you used to use
934 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
935 unless you are changing both of them. To cross build pc98 on
936 an alpha, for example, you need to set TARGET=pc98 and
940 The kernel interface that burncd depends on has changed.
941 You must recompile both the kernel and userland applications
945 When crossbuilding, please set TARGET_ARCH rather than
946 MACHINE_ARCH to indicate the target. In the future, one will
947 set TARGET_MACHINE where you set MACHINE now. At the moment,
948 setting MACHINE alone for same MACHINE_ARCH machines works
949 (eg, you can build pc98 on an i386 machine and vice versa).
952 Some weird problems result from using ACPI on some machines.
953 To disable ACPI you can add
954 hint.acpi.0.disabled="1"
955 to /boot/loader.conf (or by putting set X=Y at the boot
958 Alternatively, you can remove it from /boot/kernel/acpi.ko
959 or use the MODULES_OVERRIDE function in your kernel config
960 file and not list acpi in that list.
963 The buildworld has been fixed. You may need to install
964 the 4.x compatibility libraries for some old binaries
965 to work. Add COMPAT4X=true to your /etc/make.conf to
966 get them installed on every installworld, or execute the
967 following to get them installed only once:
968 cd src/lib/compat/compat4x.<arch>
970 You will see ``__stdoutp undefined'' until you do this.
973 There's a bug in the world build process. The cross-tools
974 are build with the NEW headers, but the OLD libc.a. This
975 leads to all kinds of problems with the new libc. A temporary
977 CFLAGS="-O -pipe -D_OLD_STDIO"
978 before building world when upgrading from 4.x to current. This
979 can be removed afterwards.
981 A proper fix to the buildworld target is needed.
984 Peter has committed his new kthread nfs client/server code.
985 NFS may be unstable after this date.
988 KSE has hit the tree. Lots of things are now different in
989 the kernel. While a few problems were introduced in the
990 initial commit, most of the major ones have been found and
994 In OLDCARD, CardBus bridges appear to be stable. The work
995 arounds described in the 20010604 entry are now no longer
996 necessary and will be ignored. Most insert/remove problems
997 have been rectified around this date.
1000 named now runs as user bind and group bind rather than as
1001 root. If named_enable is set to YES in /etc/rc.conf, ensure
1002 that user bind is available in /etc/passwd (using vipw(8))
1003 and that group bind is available in /etc/group. Also make
1004 sure that user or group bind has read (and not write)
1005 permission for your name server configuration and that it
1006 has read and write permission for your slave zone files and
1009 If you wish to continue to run named as root (a less secure
1010 alternative), add a line to /etc/rc.conf saying
1015 The PAM libraries have had an API upgrade that is beyond
1016 the ability of the shared library major number to handle.
1017 It is manifested by PAM-using ports dumping core. The
1018 solution is to rebuild those ports.
1021 The kernel compile module has moved from src/sys/compile/FOO
1022 to src/sys/${MACHINE}/compile/FOO.
1025 The pccard modem issue from 20010613 has been corrected.
1026 OLDCARD support is still a little weak in -current. slot 1 is
1027 known not to work on some TI based cardbus bridges. Some
1028 cardbus bridges do not properly detect insert/removal events.
1029 IRQ configuration needs more safety belts.
1032 Softupdates problems have been corrected.
1035 Peter ripped out the linkerset support. You must, as always,
1036 rerun config after you cvsup if you are using the traditional
1037 kernel building methods.
1040 pccard modems may not work with current after 20010604 date. Some
1041 do, others result in panics. *MAKE*SURE* that you update your
1042 config and /etc/rc.conf ala the 20010604 entry, or you will have
1043 problems (this issue will be fixed, it just hasn't been yet).
1046 SOFTUPDATES seem to be broken since the middle of May or so. Do not
1047 use them in current. You can disable softupdates on all mounted
1048 partitions, or remove SOFTUPDATES the kernel config file.
1051 After Peter's commits to the hints code, people have been noticing
1052 that certain devices are attached (or try to) twice. This is due
1053 to having both static hints as well as a /boot/device.hints. To
1054 work around this issue, please use only one or the other mechanism
1055 until this bug is fixed.
1057 Please note that a feature of config is that if you have config
1058 file FOO and FOO.hints, it automatically adds FOO.hints to the
1059 hints.c file, whether you want it to or not.
1062 Locale names have changed to match other systems better.
1065 pccard support for pci cards has been committed. You must change
1066 your /etc/pccard.conf irq lines. It must match the irq used by
1067 pcic device. Interrupt storms may result if you fail to do this.
1068 Interrupt storms look a lot like a hang.
1070 You must also install a new pccardd, otherwise you will get an
1071 interrupt storm at card reset time (just after it tells you what
1074 pccardd_flags="-I" is necessary for the time being. It tells pccardd
1075 not to ask the kernel if the interrupt is really free or not before
1076 using it. You can either change the /etc/pccard.conf irq lines to
1077 match pcic, or add "-i X" to the pccardd_flags.
1080 INSTALL=install -C is being deprecated. If you want to do this,
1081 use COPY=-C instead. The former method will be supported for only
1082 a limited time. If you see
1084 install: warning: the -d and -C options may not be specified together
1086 in your makeworld, then you need to migrate towards using
1090 It appears that vm is now stable enough to use again. However,
1091 there may be other problems, so caution is still urged. alpha
1092 definitely is in bad shape.
1095 Minor repo damage has happened. This may cause problems
1096 with cvsup of ports. If you get errors, please see
1097 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1098 at the bottom for details on a workaround. The error message
1100 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1103 Vm and/or swapping are busted on -current. Please be patient.
1106 pccard has had much reorganizational work done to it over
1107 the past few days. Everything should still work, but if
1108 not, please contact imp@freebsd.org.
1111 ata ioctl changed. Make sure to recompile both kernel and
1112 userland at the same time.
1115 New ncurses imported.
1118 DEVFS is now opt out, not opt in. Barring major problems, this
1119 will be the only way to go starting July 1.
1122 OpenSSH has been updated to 2.9. Some defaults are different,
1123 including RhostsRSAAuthentication, which changes from yes to no.
1126 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1129 Building perl was broken at 02:25:25 PDT.
1132 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
1133 go back in the water.
1136 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
1137 this date, but before the correction date.
1140 old fsck and new kernel interactions appear to have been fixed.
1143 fsck and the kernel were changed to handle some optimizations
1144 to directory layout. This breaks backward compatibility.
1145 Update only if you understand that you must not use the old
1146 fsck with the new kernel ever.
1149 fsck has changed the meaning of the pass column in /etc/fstab.
1150 Please see the cvs commit to fsck.8 or the fsck.8 man page for
1151 details. It is unclear if changes to /etc/fstab are necessary.
1154 portmap had changed name to rpcbind for maximum POLA in your
1155 current world. /etc/hosts.{allow,deny} needs changes. nfs and
1156 other rpc based programs that rely on portmapper will not work
1157 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
1160 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1161 and ATA_ENABLE_TAGS are no longer kernel options. They have
1162 been replaced by tunables. See ata.4 for details.
1165 The fxp driver was converted to use miibus. If you compile
1166 fxp into your kernel statically, you will need to add miibus.
1169 The wi device now defaults to BSS (infrastructure) mode
1173 /dev/urandom should be a symbolic link to /dev/random now.
1174 Users of current not using DEVFS need to run MAKEDEV std.
1175 ssh might not work if you don't.
1178 The ed driver has been updated. It now allows mii attachments,
1179 which means that you must include the miibus in your kernel if
1180 you use the ed driver.
1183 The problems with libc have been corrected. It is now mostly
1184 safe to go back into the water.
1187 The size of FILE was changed. This breaks upgrading. If
1188 you must upgrade, be prepared for pain. It also breaks almost
1189 all binaries that you've compiled on -current. You are warned
1190 that before upgrading would be a good time to do a level 0
1191 dump of your system. No, really, I mean it this time.
1193 To get to the new system, you'll need to use the following
1194 workaround. Hopefully this can be sorted out so that we
1195 don't have to move this to the updating section.
1197 To get around the installworld problem, do:
1198 # cd /usr/src/usr.bin/sed
1202 If that doesn't work, then try:
1203 # make -k installworld
1207 DEVFS is now the default. If you use vinum, make sure that you
1208 do not include devfs in your kernel as problems result.
1211 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1212 Remove them from your config.
1215 ****************************** WARNING ******************************
1216 buildkernel has been changed slightly
1217 ****************************** WARNING ******************************
1218 KERNCONF replaces the variable KERNEL for buildkernel. You
1219 should update your scripts and make.conf accordingly.
1222 config has changed to allow DEV_FOO as a replacement for NFOO.
1223 This requires a new config to build correctly.
1226 The kernel option I386_CPU is now mutually exclusive with the
1227 other cpu types. If you have an i386 system, be sure that it
1228 only had this line. Remove it for all other configurations.
1231 Changes to the kernel require it and burncd be in sync.
1234 Everyone who has hw.sndunit set to something in
1235 /etc/sysctl.conf, it is now hw.snd.unit.
1238 ex and vi were broken by some changes to sys/queue.h. If you
1239 have a bad vi, you will see make buildworld fail with a core
1240 dump while building termcap. You can work around this problem
1241 by adding -k to your make buildworld. This will cause the
1242 build to complete and install a new vi. Once that's done, you
1243 can rebuild again without the -k to pick up anything that
1244 might have been ignored by the -k option.
1246 Others have suggested that you can just rebuild libc if your
1247 vi/ex is dynamically linked, but I've not received any reports
1251 There have been some changes to libcrypt in -current. The
1252 libscrypt/libdescrypt symlink silliness is gone and the installed
1253 libcrypt is fully functional. Be aware of this.
1256 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1257 now require the addition of flag 0x80000 to their config line
1258 in pccard.conf(5). This flag is not optional. These Linksys
1259 cards will not be recognized without it.
1262 Important new FreeBSD-version stuff: PAM support has been worked
1263 in, partially from the "Unix" OpenSSH version. This requires
1264 adding the following in pam.conf:
1266 sshd auth sufficient pam_skey.so
1267 sshd auth required pam_unix.so try_first_pass
1268 sshd session required pam_permit.so
1271 cvs updated to 1.11.
1274 The random device needs more entropy, so you need to make sure
1275 that you've run mergemaster to get a /etc/rc which will seed
1276 /dev/random. If you don't and the system hangs after ldconfig,
1277 then banging on the keyboard randomly until it unhangs is one
1281 ****************************** WARNING ******************************
1282 Sendmail has been updated.
1283 ****************************** WARNING ******************************
1284 o mail.local(8) is no longer installed as a set-user-id binary.
1285 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1287 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1289 o Now using sendmail's version of vacation(1).
1290 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1291 in /usr/share/sendmail/cf.
1292 o sendmail.cw changed to local-host-names
1294 More details can be found at
1295 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1298 The ports tree's new layout is in place. Be sure to update
1299 your entire ports tree, or you will have problems.
1302 The perl build procedure no longer installs miniperl, nor uses
1303 the installed miniperl. It is recommended that you delete
1307 This weekend the ports tree will be updated to a new layout.
1308 It will be in an inconsistent state until noted in the UPDATING
1309 file, or with asami-san's message to the relevant mailing
1310 lists. With this new layout, you'll need to update the whole
1311 tree for anything to work.
1314 There was a change in the passwd format. Need more information.
1317 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1318 place. Please update boot loader (not the boot blocks) at the
1319 same time as your kernel.
1322 The new pmtimer device is necessary for laptops. Failure to
1323 include the device will cause suspended laptops losing time
1324 when they resume. Include
1326 in your config file and
1327 hint.pmtimer.0.at="isa"
1328 to your /boot/device.hints file.
1331 The random device has been turned into a (pseudo-)device,
1332 rather than an option. The supplied kernel config files have
1333 been updated. You will need to do something similar in your
1334 own kernel config file.
1339 If you prefer to load the loadable module, you need to do
1343 The random device module has been renamed from randomdev.ko to
1344 random.ko. You will need to edit your /boot/loader.conf to
1345 reflect this if you load this module at boot time.
1346 The line should read:
1350 The SMPNG commit has happened. It should work, but if it
1351 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1352 to be a variety of minor issues. Please see 20000905 to make
1353 sure you don't have model loading problems which might at
1354 first blush appear related to SMP.
1357 nsswitch has been imported from NetBSD. Among other things,
1358 this means that /etc/host.conf is no longer used. See
1359 nsswitch.conf(5) instead. Note that at boot time rc.network
1360 will attempt to produce a new nsswitch.conf file for you if you
1361 don't have one, and you have host.conf.
1364 The ucred structure changed size. This breaks the interface
1365 that mountd uses. Trying to use an older mountd with a newer
1366 kernel guarantees a panic. This means that you need to use
1367 kernels newer than today only with matching mountd, but you
1368 needed to do that anyway with the boot loader changes.
1371 The boot loader has been updated. The new default kernel is
1372 now /boot/kernel/kernel.ko. The new default module location
1375 You *MUST* upgrade your boot loader and kernel at the same time.
1376 The easiest way to do this is to do the buildworld/buildkernel/
1377 installkernel/installworld dance.
1379 Furthermore, you are urged to delete your old /modules directory
1380 before booting the new kernel, since kldload will find stale
1381 modules in that directory instead of finding them in the correct
1382 path, /boot/kernel. The most common complaint that this cures
1383 is that the linux module crashes your machine after the update.
1385 if [ ! -d /boot/kernel.old ]; then
1386 mv /modules.old /boot/kernel.old
1387 chflags noschg /kernel.old
1388 mv /kernel.old /boot/kernel.old/kernel.ko
1389 chflags schg /boot/kernel.old/kernel.ko
1393 A new issue with the sendmail upgrade has come to light.
1394 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1395 incorrectly install the default aliases in /etc/mail rather than
1396 move the old one from /etc. So you'll need to manually move the
1397 file, create a symbolic link, remove the old /etc/aliases.db and
1398 run newaliases. For safety sake, you should stop sendmail
1399 while doing this and run the upgrade when locally sourced email
1400 is not likely to be generated.
1403 /boot/device.hints is now required for installkernel to
1404 succeed. You should copy GENERIC.hints for your architecture
1405 into /boot/device.hints. If and only if you compile hints
1406 into your kernel, then this file may be empty. Please note,
1407 if you have an empty or missing /boot/device.hints file and
1408 you neglected to compile hints into your kernel, no boot
1409 messages will appear after the boot loader tries to start the
1413 If you do NOT have ``options RANDOMDEV'' in your kernel and
1414 you DO want the random device then add randomdev_load="YES" to
1418 suidperl is now always built and installed on the system, but
1419 with permissions of 511. If you have applications that use
1420 this program, you are now required to add ENABLE_SUIDPERL=true
1421 to /etc/make.conf. If you forget to do this,
1422 chmod 4511 /usr/bin/suidperl
1423 will fix this until the next build.
1426 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1427 visible changes that may immediately affect your configuration
1429 - New default file locations from src/contrib/sendmail/cf/README
1430 - newaliases limited to root and trusted users
1431 - MSA port (587) turned on by default
1432 - New queue file naming system so can't go from 8.11 -> 8.9
1433 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1434 - FEATURE(`nullclient') is more full featured
1435 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1436 - mail.local FreeBSD-only -b option changed to -B
1437 - See src/contrib/sendmail/RELEASE_NOTES for more info
1440 suidperl (aka sperl) is no longer build by default. You must
1441 specifically define BUILD_SUIDPERL to "true" for it to be build.
1442 Furthermore, we recommend that you remove /usr/bin/sperl* and
1443 /usr/bin/suidperl files from your system unless you have a
1444 specific use for it.
1447 Networking defaults have been tightened. Anybody upgrading
1448 /etc/defaults/rc.conf needs to add the following lines to
1449 /etc/rc.conf if they want to have the same setup
1450 afterwards (unless the variables already are set, of course):
1451 # Enable network daemons for user convenience.
1453 portmap_enable="YES"
1454 sendmail_enable="YES"
1457 If you have null_load="YES" in your /boot/loader.conf, you
1458 will need to change that to nullfs_load="YES".
1461 The "installkernel" target has changed slightly. Now even if
1462 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1463 it will install the MYKERNEL file (built with the buildkernel
1464 target) as /kernel rather than /MYKERNEL. Those who have
1465 updated their /boot/loader.conf files to point to /MYKERNEL
1466 should remove that entry or perform manual rename of /kernel
1470 If you use CVSUP or CTM to get CVS trees, AND you used to get
1471 the old crypto files from internat.freebsd.org AND you check
1472 out files from the CVS tree with the cvs command, please read
1473 http://people.freebsd.org/~imp/internat.txt
1474 for details on potential problems that you might have and how
1477 If you are merely a mirror, or don't answer yes to each of the
1478 clauses above, you needn't worry.
1481 /etc/security has been updated to print the inode number of
1482 setuid programs that have changed. You will see a large spike
1483 in the number of changed programs the first time when you run
1484 mergemaster to get a new /etc/security.
1487 /dev/random now has good entropy collection (from the keyboard
1488 and sysmouse drivers). Please ensure that either `options
1489 RANDOMDEV' is present in your kernel config file or that
1490 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1491 not have the /dev/random driver, OpenSSL (and consequently
1492 lots of crypto tools (like SSH)) will fail with strange
1493 errors. (see below, 20000624).
1495 FreeBSD-current is safe again to run Crypto.
1498 phk made the malloc default options AJ. This may slow things
1499 down and uncover other latent bugs in the code. If you need to
1500 run at full speed, you can disable this by doing the following:
1501 ln -s aj /etc/malloc.conf
1504 libftpio's version was accidentally bumped a few days ago. This
1505 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1506 before doing your next buildworld/installworld pair. It certainly
1507 won't hurt to remove it before the update procedure. It will
1508 break fetch until a new one is built, but ftp can be used in the
1512 The crypto packages have changed for the cvsup. This has been done
1513 in a backward compatible way, but the old packages will go away at
1514 some point in the future. Look at /usr/share/examples/cvsup for
1518 With the new sys/modules/sound/drivers/*, you will need to
1519 set SYSDIR until you do an installworld after July 7th.
1522 rc.shutdown and rc will now call the rc.d scripts with start
1523 or stop. This may cause some harmless warnings from older
1524 rc.d scripts that haven't been updated.
1527 The libfetch based version of fetch has gone into the tree.
1528 Minor problems may result on some of the less popular sites,
1529 which should be reported to des@freebsd.org.
1532 From approximately this date forward, one must have the crypto
1533 system installed in order to build the system and kernel.
1534 While not technically strictly true, one should treat it as
1535 required and grab the crypto bits. If you are grabbing CVS
1536 trees, src-all and cvs-crypto should be treated as if they
1537 were required. You should check with the latest collections
1538 to make sure that these haven't changed.
1541 Mark Murray just committed the first parts of a cleanup of
1542 /dev/zero, et al. This is also cleaning up /dev/random.
1543 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1544 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1545 until Mark can merge in the fixes to this work in progress.
1546 openssh and openssl should not be used to generate keys from this
1547 date to the completion of the work.
1549 If you must operate at this reduced level of security, add '
1550 options RANDOMDEV' to your kernel or modload the randomdev
1551 module. You may also need to copy a new MAKEDEV to /dev and
1552 recreate the random and urandom devices.
1555 The license on the softupdates is now a standard 2 clause
1556 BSD license. You may need to remove your symbolic links
1557 that used to be required when updating.
1560 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1561 the config file update procedure.
1562 http://people.freebsd.org/~imp/config-upd.html
1563 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1564 isn't buildable. However, you can generate a LINT file:
1565 cd /sys/<ARCH>/conf && make LINT
1568 Binutils 2.10 have hit the tree, or will shortly. As soon
1569 as they do, the problem noted in 20000522 will be resolved and
1570 that workaround will no longer be required.
1573 phk removed the compatibility creation of wd devices in the
1574 ad driver. If you haven't done so already, you must update
1575 your fstab, etc to use the ad devices instead of the wd
1578 In addition, you'll need to update your boot blocks to a
1579 more modern version, if you haven't already done so. Modern
1580 here means 4.0 release or newer (although older releases
1584 Peter took an axe to config(8). Be sure that you read his mail
1585 on the topic before even thinking about updating. You will
1586 need to create a /boot/device.hints or add a hints directive
1587 to your config file to compile them in statically. The format
1588 of the config file has changed as well. Please see GENERIC or
1589 NEWCARD for examples of the new format.
1591 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1592 says that it has been fixed, assume that must use the hints mechanism
1593 in the loader if you need to use a machine with very old ISA cards
1597 A new set of binutils went into the tree today. Anybody
1598 building a kernel after this point is advised that they need
1599 to rebuild their binutils (or better yet do a
1600 buildworld/installworld) before building a new kernel.
1602 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1603 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1604 is recommended that you don't set this option until the problem
1608 The ethernet drivers were all updated to clean up the BPF handling.
1611 The problems with boot blocks on the alphas have been corrected.
1612 This will require some care in updating alphas. A new libstand
1613 is requires for the boot blocks to build properly.
1616 Recompile all kld modules. Proper version dependency info
1620 Modules have been disconnected from the buildworld tree and
1621 connected to the kernel building instead.
1624 You may need to build gperf
1625 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1626 when upgrading from 4.0 -> current. The build system now uses
1627 an option only in -current.
1630 The method that we brand ELF binaries has changed to be more
1631 acceptable to the binutils maintainers. You will need to
1632 rebrand your ELF binaries that aren't native. One problem
1633 binary is the Linux ldconfig. After your make world, but
1634 before you reboot, you'll need to issue:
1635 brandelf -t Linux /compat/linux/sbin/ldconfig
1636 if you have Linux compatibility enabled on your machine.
1639 If you have really bad/marginal IDE drives, you may find they
1640 don't work well. Use pio mode instead. The easiest way to
1641 cope if you have a problem combination is to add:
1642 /sbin/sysctl hw.ata.ata_dma=0
1643 to the start of /etc/rc.conf.
1646 The ISA and PCI compatibility shims have been connected to the
1647 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1648 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1649 include the appropriate option in your kernel config. Drivers
1650 using the shims should be updated or they won't ship with
1651 5.0-RELEASE, targeted for 2001.
1654 We've entered the traditional post release dumping party.
1655 Large kernel changes are being committed and are in the
1656 works. It is important to keep the systems' klds and kernel
1657 in sync as kernel interfaces and structures are changing.
1658 Before reporting kernel panics, make sure that all modules
1659 that you are loading are up to date.
1662 If you are upgrading from an older version of FreeBSD, you
1663 need to update your boot blocks as well. 'disklabel -B ad0'
1664 will do the trick. This isn't critical until you remove your
1665 wd device entries in /dev, at which point your system will not
1669 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1670 to upgrade to 4.0 from 3.x.
1674 # NOTE: 5.x below applies to 6.0-currrent as well, for the
1675 # momemnt. 4.any -> 5.any upgrade support will remain in
1676 # place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1677 # 6.0-current upgrade path will require moving through 5.3
1682 Avoid using make -j when upgrading. From time to time in the
1683 past there have been problems using -j with buildworld and/or
1684 installworld. This is especially true when upgrading between
1685 "distant" versions (eg one that cross a major release boundary
1686 or several minor releases, or when several months have passed
1687 on the -current branch).
1689 Sometimes, obscure build problems are the result of environment
1690 poisoning. This can happen because the make utility reads its
1691 environment when searching for values for global variables.
1692 To run your build attempts in an "environmental clean room",
1693 prefix all make commands with 'env -i '. See the env(1) manual
1694 page for more details.
1698 If you are updating from a prior version of FreeBSD (even one just
1699 a few days old), you should follow this procedure. With a
1700 /usr/obj tree with a fresh buildworld,
1701 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1702 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1704 To just build a kernel when you know that it won't mess you up
1705 --------------------------------------------------------------
1706 This assumes you are already running a 5.X system. Replace
1707 ${arch} with the architecture of your machine (e.g. "i386",
1708 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1710 cd src/sys/${arch}/conf
1711 config KERNEL_NAME_HERE
1712 cd ../compile/KERNEL_NAME_HERE
1717 If this fails, go to the "To build a kernel" section.
1719 To rebuild everything and install it on the current system.
1720 -----------------------------------------------------------
1721 # Note: sometimes if you are running current you gotta do more than
1722 # is listed here if you are upgrading from a really old current.
1724 <make sure you have good level 0 dumps>
1725 <maybe fix /etc/fstab> [7]
1727 make kernel KERNCONF=YOUR_KERNEL_HERE
1729 <reboot in single user> [3]
1730 src/etc/rc.d/preseedrandom [10]
1737 To cross-install current onto a separate partition
1738 --------------------------------------------------
1739 # In this approach we use a separate partition to hold
1740 # current's root, 'usr', and 'var' directories. A partition
1741 # holding "/", "/usr" and "/var" should be about 2GB in
1744 <make sure you have good level 0 dumps>
1747 <maybe newfs current's root partition>
1748 <mount current's root partition on directory ${CURRENT_ROOT}>
1749 make installworld DESTDIR=${CURRENT_ROOT}
1750 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1751 cp src/sys/${ARCH}/conf/GENERIC.hints \
1752 ${CURRENT_ROOT}/boot/device.hints # as needed
1753 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1754 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1755 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1756 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1757 <reboot into current>
1758 <do a "native" rebuild/install as described in the previous section>
1759 <maybe install compatibility libraries from src/lib/compat>
1763 To upgrade in-place from 4.x-stable to current
1764 ----------------------------------------------
1765 # 5.x uses more space than 4.x. Also, the location of kernel
1766 # modules has changed. If you are installing 5.x onto a 4.x
1767 # system, you'll need about 30MB of free disk space on your /
1768 # partition. If you have less than this, you may encounter difficult
1769 # to back out of problems with this procedure. If /tmp is on
1770 # the / partition, you may want to completely remove all its content
1771 # before upgrading, as this can be a common source of shortage of
1774 <make sure you have good level 0 dumps>
1775 <maybe fix /etc/fstab> [7]
1777 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1778 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1779 cd sys/boot ; make STRIP="" install [6]
1781 <reboot in single user> [3]
1782 src/etc/rc.d/preseedrandom [10]
1784 rm -rf /usr/include/g++
1789 Make sure that you've read the UPDATING file to understand the
1790 tweaks to various things you need. At this point in the life
1791 cycle of current, things change often and you are on your own
1792 to cope. The defaults can also change, so please read ALL of
1793 the UPDATING entries.
1795 Also, if you are tracking -current, you must be subscribed to
1796 freebsd-current@freebsd.org. Make sure that before you update
1797 your sources that you have read and understood all the recent
1798 messages there. If in doubt, please track -stable which has
1799 much fewer pitfalls.
1801 [1] If you have third party modules, such as vmware, you
1802 should disable them at this point so they don't crash your
1805 [2] If you have legacy ISA devices, you may need to create
1806 your own device.hints to reflect your unique hardware
1809 [3] From the bootblocks, boot -s, and then do
1814 adjkerntz -i # if CMOS is wall time
1815 Also, when doing a major release upgrade, it is required that
1816 you boot into single user mode to do the installworld.
1817 For the 4.x -> 5.x upgrade, you will also see many messages about
1818 needing to recompile your userland. These are harmless and can
1819 be ignored while you proceed to the next step.
1821 [4] Note: This step is non-optional. Failure to do this step
1822 can result in a significant reduction in the functionality of the
1823 system. Attempting to do it by hand is not recommended and those
1824 that pursue this avenue should read this file carefully, as well
1825 as the archives of freebsd-current and freebsd-hackers mailing lists
1826 for potential gotchas.
1828 [5] Usually this step is a noop. However, from time to time
1829 you may need to do this if you get unknown user in the following
1830 step. It never hurts to do it all the time. You may need to
1831 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1832 install) after the buildworld before this step if you last updated
1833 from current before 20020224 or from -stable before 20020408.
1835 [6] 4.x boot loader can be used to boot a 5.x system, however
1836 it is difficult to do that at best. If you wish to try, then
1837 you should interrupt the boot and at the ok prompt type:
1839 ok boot /boot/kernel/kernel
1840 If this fails to work, you must install a new boot loader as
1843 [7] Before you upgrade, please make sure that you are not using
1844 compatibility slices. These are device names of the form /dev/ad0a
1845 without the actual slice name. These will break with 5.x and newer.
1846 You generally must update these entries to use the post FreeBSD
1847 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1850 [8] In order to have a kernel that can run the 4.x binaries
1851 needed to do an installworld, you must include the COMPAT_FREEBSD4
1852 option in your kernel. Failure to do so may leave you with a system
1853 that is hard to boot to recover.
1855 Make sure that you merge any new devices from GENERIC since the
1856 last time you updated your kernel config file.
1858 [9] When checking out sources, you must include the -P flag to have
1859 cvs prune empty directories.
1861 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1862 "?=" instead of the "=" assignment operator, so that buildworld can
1863 override the CPUTYPE if it needs to.
1865 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1866 not on the command line, or in /etc/make.conf. buildworld will
1867 warn if it is improperly defined.
1869 In case you would like to avoid installing new packages of everything,
1870 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1871 compatibility libraries are built which should allow you to continue
1872 using your existing software for a while. Alternatively, you can
1873 install the misc/compat4x port.
1875 [10] In order to create temporary files, /dev/random must be
1876 initialized by feeding data into it. src/etc/rc.d/preseedrandom
1880 This file contains a list, in reverse chronological order, of major
1881 breakages in tracking -current. Not all things will be listed here,
1882 and it only starts on March 15, 2000. Updating files can found in
1883 previous releases if your system is older than this.
1885 Copyright information:
1887 Copyright 1998-2004 M. Warner Losh. All Rights Reserved.
1889 Redistribution, publication, translation and use, with or without
1890 modification, in full or in part, in any form or format of this
1891 document are permitted without further permission from the author.
1893 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1894 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1895 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1896 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1897 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1898 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1899 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1900 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1901 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1902 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1903 POSSIBILITY OF SUCH DAMAGE.
1905 If you find this document useful, and you want to, you may buy the
1908 Contact Warner Losh if you have any questions about your use of