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 format of the pflogd(8) logfile "/var/log/pflog" has changed for
28 architectures that have a 64 bit long type to make it compatible to
29 the standard pcap format. In order to prevent corruption move away
30 any old logfile before using a new pflogd(8).
33 debug.witness_* has been renamed to debug.witness.*. There are
34 compatibility tunables left in for a few days. Update loader.conf
38 The ifi_epoch change has been reverted because the ABI breakage
39 was too extensive. If you are running with a kernel/userland
40 containing the initial change (20040830), you should heed the
41 warning about ifconfig incompatibility when upgrading again.
42 With this change, 5.3 and 6.0 ifconfigs and kernels are once
46 A new variable, ifi_epoch, has been added to struct if_data
47 which is part if struct ifnet. This means all network drivers
48 and network monitoring applications need to be recompiled.
50 WARNING WARNING WARNING WARNING WARNING WARNING WARNING
52 This also breaks ifconfig compatibility. An old ifconfig will
53 not work with the new kernel and a new ifconfig will not work
54 with the old. It is strongly recommended that you make a copy
55 of your old ifconfig before installworld. If you are installing
56 remotely, you must copy over a new ifconfig before rebooting in
60 The default configuration for the network stack has been changed
61 such that it now runs without the Giant lock unless configured
62 otherwise. If you experience network-related instability, you
63 may wish to try setting "debug.mpsafenet=0" or compiling the
64 kernel with "options NET_WITH_GIANT". Details on the netperf
65 project may be found at:
67 http://www.watson.org/~robert/freebsd/netperf/
69 Including the 20040828 announcement of configuration change
73 PFIL_HOOKS are a fixed part of the network stack now and do not
74 need to be specified in the kernel configuration file anymore.
77 Netgraph changed its message format slightly to align the data
78 portion well on 64 bit machines.
79 Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
80 pppoed, bluetooth, ATM) should be recompiled when a new kernel
84 IPFW has been converted to use PFIL_HOOKS. This change is
85 transparent to userland and preserves the ipfw ABI. The ipfw
86 core packet inspection and filtering functions have not been
87 changed, only how ipfw is invoked is different. Note that
88 "option PFIL_HOOKS" is required to use IPFIREWALL compiled
89 into the kernel or as KLD.
92 The RANDOM_IP_ID option has been replaced by the sysctl
93 net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
94 you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
97 The size of 'struct ifnet' has changed due to the addition of the
98 if_carp placeholder. All kernel modules implementing network
99 interfaces must be recompiled as a result.
102 Module loading has been fixed. Some older installations will
103 drop proper module_path initialization and modules will fail to
104 load properly. If you have a line in /boot/loader.rc that says:
105 "initialize drop", do (i386 only):
106 cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
107 chown root:wheel /boot/loader.rc
108 chmod 444 /boot/loader.rc
111 making /dev/(null|zero) into a module proved to be too unpopular,
112 so this bit has been revoked from the previous (20040801) entry.
115 The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
116 so you may wish to add them to your kernel config file. See
117 GENERIC for examples.
120 System compiler has been upgraded to GCC 3.4.2-pre. As with any major
121 compiler upgrade, there are several issues to be aware of. GCC 3.4.x
122 has broken C++ ABI compatibility with previous releases yet again
123 and users will have to rebuild all their C++ programs with the new
124 compiler. If you are getting run-time error such as
125 /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
126 This entry does apply to you.
128 A new unit-at-a-time optimization mode, which is default in this
129 compiler release, is more aggressive in removing unused static
130 symbols. This is the likely cause of 'make buildworld' breakages
131 with non-default CFLAGS where optimization level is set to -O2
134 With the upgrade of the system compiler, the kernel has been upgraded
135 to match the new system compiler. This makes it impossible to build
136 a new kernel with the old compiler. Upgrade your system via
137 make buildworld and make kernel (see below) to fix this problem.
140 The size of 'struct ifnet' has changed due to the addition of
141 the IFF_NEEDSGIANT flag (and what it implies). All kernel
142 modules implementing network interfaces must be recompiled as
146 The sound device drivers are renamed. `sound' is always required,
147 while `snd_*' should be configured accordingly to your hardware.
148 Refer to NOTES for the detail of the drivers.
151 __FreeBSD_version bumped to 502122.
154 The console initialization on Alpha has been reworked and is now
155 identical to other platforms. This means that the hardcoding of
156 the serial console and the debug port has been removed. As such,
157 hints are now required for the sio(4) driver to become a console
158 or debug port. The NO_SIO option has been decommissioned because
162 A revamp of the debugging code in the kernel with some visible
163 changes beyond just the debugging experience:
164 o The DDB option is now specific to the DDB debugger backend
165 and should not be used any more for conditional compilation
166 of debugging code for when debugging is enabled. Use the KDB
168 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
169 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
170 respectively. This is in line with the first bullet.
171 o The remote GDB support has been untangled from DDB and needs
172 to be enabled separately now. Use the GDB option for this.
173 o The GDB_REMOTE_CHAT option has been removed. Support for this
174 homegrown feature is discontinued. The GDB remote protocol
175 supports console output and it makes sense to use that.
176 o The DDB_NOKLDSYM option has been removed. The DDB debugger
177 now supports both direct symbol table lookups as well as KLD
178 symbol lookups through the linker.
181 Bluetooth code has been marked as non-i386 specific.
182 __FreeBSD_version has been bumped to 502121 to mark this change.
185 The native preemption has been added to the kernel scheduler.
186 There is some report that the ULE scheduler was broken in some
187 machines and we encourage users using the ULE scheduler either
188 stick with a known good kernel, or temporarily switch to the 4BSD
189 scheduler as a workaround.
192 The netgraph ABI version number has been incremented to indicate
193 an incompatible change in the ABI. Old netgraph nodes will refuse
194 to attach until recompiled. Netgraph now uses mbuf tags to move
195 metadata and this commit removes its home-grown metadata facility.
196 Nodes should just recompile, unless they use metadata, in which
197 case the changes are simple; the file ng_ksocket.c serves as an
198 example of such changes.
200 This also broke i4b, although the compile problem has been papered
204 ACPI has been updated to disable known-bad BIOS revisions. A message
205 will be printed on the console indicating that ACPI has been disabled
206 automatically and that the user should use a newer BIOS, if possible.
207 If you think ACPI does work on your system and want to override
208 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
212 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
213 separated now. It uses the newly created "_pflogd" user/group
214 combination. If you plan to use pflogd(8) make sure to run
215 mergemaster -p or install the "_pflogd" user and group manually.
218 Network interface cloning has been overhauled. This change will
219 require a recompile of modules using cloning and modification of
220 external ones to the new API. __FreeBSD_version has been bumped
221 to 502119 to mark this change. Additionally, users creating
222 stf(4) interfaces via "ifconfig stf" will need to update their
223 scripts as this will create an interface named "stf" instead of
224 "stf0" and ifconfig will not print "stf0" to stdout.
227 On 20040524, the /etc/rc.d/nsswitch script was modified to
228 automatically create /etc/nsswitch.conf on startup if it did
229 not already exist. Unfortunately, an error in the man page
230 was carried over to the script, resulting in incorrect
231 nsswitch settings. The simplest remedy is to remove both
232 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
233 during the next reboot.
236 The return value of sema_timedwait(9) has been changed to
237 make it consistent with cv_timedwait(9). Be sure to recompile
238 the ips module and any third-party modules which call
242 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
243 Make sure to recompile modules and any userland that makes use of
244 sizeof(struct ifnet). In order to get the altq headers in place
245 please recompile and reinstall world.
248 Splitting kern_thread.c into 2 files (adding kern_kse.c)
249 requires that you re-run config after updating your tree.
252 The MIDI drivers have been removed. Until the new module-friendly
253 ones are merged, remove or comment out midi and seq from your
254 kernel configuration.
257 Due to a new option in ipfw (versrcreach) the ipfw(8) command
258 needs to be recompiled. Normal accept/reject rules without
259 options are not affected but those with options may break until
260 ipfw(8) is recompiled.
263 Due to changes in the callout ABI, kernels compiled after this
264 date may be incompatible with kernel modules compiled prior to
268 The PCI bus power state stuff has been turned on. If this causes
269 problems for your system, please disable it using the tunable
270 hw.pci.do_powerstate=0.
273 The bulk of the pci problems have been fixed, although the floppy
274 drive is still broken.
277 A substantial update to the pci bus resource and power management
278 have been committed. Expect a bumpy ride for a few days until
279 the unanticipated problems have been resolved.
282 Due to changes in the the Yarrow initialization process,
283 /dev/random needs to be fed before operations requiring
284 temp files can succeed in single user mode. This includes
285 running "make installworld". /dev/random may be fed by running
286 "/etc/rc.d/initrandom start" or with 20040415 source by running
287 "/etc/rc.d/preseedrandom".
290 The debug.mpsafenet tunable controls whether the kernel Giant
291 lock is held across the lower levels of the network stack, and
292 by default is turned off. In the few days following 20040322,
293 the behavior of debug.mpsafenet will change such that this
294 tunable controls Giant over all levels of the network stack.
295 If you are currently setting debug.mpsafenet to 1, you should
296 set it back to 0 (the default) again during the change-over.
297 An additional note will be added to UPDATING when sufficient
298 locking is merged to permit this to take place.
301 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
302 64-bits. This is a very major incompatible change, so people
303 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
304 detailed instructions on how to make this upgrade. People
305 upgrading FreeBSD on other platforms can ignore this event.
308 The packet filter (pf) is now installed with the base system. Make
309 sure to run mergemaster -p before installworld to create required
310 user account ("proxy"). If you do not want to build pf with your
311 system you can use the NO_PF knob in make.conf.
312 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
313 pf system consists of the following three devices:
315 device pflog # optional
316 device pfsync # optional
319 If you are having trouble with the libc_r -> libpthread transition
320 (see the 20040130 entry), place the following lines at the top of
323 libc_r.so.5 libpthread.so.1
324 libc_r.so libpthread.so
326 This will cause all programs and libraries linked against libc_r
327 to use libpthread instead.
330 Some sshd configuration defaults have changed: protocol version 1
331 is no longer enabled by default, and password authentication is
332 disabled by default if PAM is enabled (which it is by default).
333 OpenSSH clients should not be affected by this; other clients may
334 have to be reconfigured, upgraded or replaced.
337 The ABIs defined in <resolv.h> and <netdb.h> have been updated
338 to support improved reentrancy. Multi-threaded programs that
339 reference the "_res" or "h_errno" symbols may experience some
340 problems if they are not recompiled. Single-threaded programs
341 should remain unaffected.
344 routed has been updated in the base system from the vendor
345 sources, routed v2.27, from rhyolite.com. This change means that
346 for users who use RIP's MD5 authentication feature, FreeBSD
347 -CURRENT's routed is now incompatible with previous versions
348 of FreeBSD; however it is now compatible with implementations
349 from Sun, Cisco and other vendors.
352 The tcpcb structure has changed and makes a recompile of libkvm
353 and related userland network utilities necessary.
356 The cdevsw structure has changed in two externally visible ways.
357 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
358 Second, the d_version field must be filled in with D_VERSION.
359 Drivers outside the tree will need to be updated.
362 The /etc/rc.d/ttys script has been removed. It is no longer
363 necessary since devfs has been mandatory for some time.
366 libkse has been renamed back to libpthread and is now the
367 default threads library. The gcc -pthread option has also
368 been changed to link to libpthread instead of libc_r. For
369 alpha and sparc64 machines, libkse is not renamed and links
370 are installed so that libpthread points to libc_r. Until
371 the ports system is updated to handle this change, it is
372 recommended that folks install an /etc/libmap.conf(5) that
373 maps libc_r to libpthread. If you have any binaries or
374 libraries linked to libkse, then it is also recommended
375 that you map libkse to libpthread. Anyone that is using
376 nvidia supplied drivers and libraries should use a libmap.conf
377 that maps libpthread to libc_r since their drivers/libraries
378 do not work with libpthread.
381 ULE has entered into its probationary period as the default scheduler
382 in GENERIC. For the average user, interactivity is reported to be
383 better in many cases. On SMP machines ULE will be able to make more
384 efficient use of the available parallel resources. If you are not
385 running it now, please switch over, replacing the kernel option
386 SCHED_4BSD with SCHED_ULE.
389 Move LongRun support out of identcpu.c, where it hardly
390 belongs, into its own file and make it opt-in, not mandatory,
391 depending on CPU_ENABLE_LONGRUN config(8) option.
394 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
395 if the login process is unable to successfully set the
396 process credentials to include all groups defined for the
397 user. The current kernel limit is 16 groups; administrators
398 may wish to check that users do not have over 16 groups
399 defined, or they will be unable to log in.
402 The ACPI module has been reactivated. It is no longer required
403 to compile ACPI support into kernels statically.
406 The statfs structure has been updated with 64-bit fields to
407 allow accurate reporting of multi-terabyte filesystem
408 sizes. You should build world, then build and boot the new kernel
409 BEFORE doing a `installworld' as the new kernel will know about
410 binaries using the old statfs structure, but an old kernel will
411 not know about the new system calls that support the new statfs
413 Note that the backwards compatibility is only present when the
414 kernel is configured with the COMPAT_FREEBSD4 option. Since
415 even /bin/sh will not run with a new kernel without said option
416 you're pretty much dead in the water without it. Make sure you
417 have COMPAT_FREEBSD4!
418 Running an old kernel after a `make world' will cause programs
419 such as `df' that do a statfs system call to fail with a bad
420 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
421 that cfsd (ports/security/cfs) needs to be recompiled after
422 these changes are installed.
424 ****************************DANGER*******************************
426 DO NOT make installworld after the buildworld w/o building and
427 installing a new kernel FIRST. You will be unable to build a
428 new kernel otherwise on a system with new binaries and an old
432 Some netgraph string length constants have been changed. This
433 change requires the netgraph kernel modules and all netgraph
434 userland components to be in sync. Especially users who require
435 netgraph to boot need to make sure to have world and kernel in
436 sync before rebooting.
439 Hyperthreading logical CPU's are no longer probed by default
440 when using the MP Table. If ACPI is being used, then logical
441 CPUs will be probed if hyperthreading is enabled in the BIOS.
442 If ACPI is not being used and hyperthreading is enabled in the
443 BIOS, logical CPUs can be enabled by building a custom kernel
444 with the option MPTABLE_FORCE_HTT enabled.
447 The i386 APIC_IO kernel option has been replaced by
448 'device apic'. The ACPI module has also been temporarily
449 disabled, so ACPI must be statically compiled into your
450 kernel using 'device acpi' if you wish to use the ACPI driver.
453 The API and ABI of struct ifnet have been changed by removing
454 the if_name and if_unit members and replacing them with
455 if_xname, if_dname, and if_dunit. All network drivers and most
456 userland programs which include net/if_var.h must be updated
457 and recompiled. __FreeBSD_version has been bumped to 501113 to
461 Changes to the cdevsw default functions have been made to remove
462 the need to specify nullopen() and nullclose() explicitly.
463 __FreeBSD_version bumped to 501110.
466 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
467 mount_cd9660(8) need to be in sync with kernel.
470 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
471 also be explicitly configured. Previously this dependency was
472 magically handled through some cruft in net/pfil.h; but that has
473 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
474 will fail with obtuse errors in ip_fil.c.
477 Fix a bug in arplookup(), whereby a hostile party on a locally
478 attached network could exhaust kernel memory, and cause a system
479 panic, by sending a flood of spoofed ARP requests. See
480 FreeBSD-SA-03:14.arp.
483 A change to /etc/defaults/rc.conf now causes inetd to be started
484 with `-C 60' if it is not overridden in /etc/rc.conf. This
485 causes inetd to stop accepting connections from an IP address
486 that exceeds the rate of 60 connections per minute.
489 The following rc.d scripts have been removed and should be
490 deleted from your installation: atm2.sh atm3.sh devdb
491 localdaemons network1 network2 network3. Depending on when
492 you last updated world and used mergemaster(8) you may or
493 may not have problems during the rc boot sequence. The simplest
494 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
495 The atm2.sh atm3.sh and devdb scripts were removed some time
496 ago, so depending on when you installed -CURRENT these scripts
497 may or may not exist on your system.
500 ATAng has been committed. You need to build world as sys/ata.h
501 has changed, and userland atacontrol depends on it.
502 If you use ATA SW raids you need "device ataraid" in your
503 kernel config file, as it is no longer pulled in automatically.
506 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
507 Among other things, this changes the device enumeration to be
508 closer to Solaris. Be aware that, this can even cause the machine
509 to not boot without manual intervention before the fstab is adjusted.
512 All current USB and Firewire quirks in da(4) have been deprecated
513 and will be removed for 5.2. If this causes failure for your
514 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
515 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
516 so the quirk can be re-enabled.
519 Problems with entry 20030714 have been corrected and no known issues
520 with /rescue and -j exist for host systems after this point in time.
523 FPU-less support has been removed from FreeBSD. Chances are you won't
524 notice. 386+387 support should still work after this change, but
525 it is now a minimum requirement for the i386 port that you have real
529 Some people are having problems with changes related to /rescue.
530 If you are building -j N, you will need to define NO_RESCUE. Others
531 will need to define it if /rescue has issues with their environment.
532 People should report those issues to current@.
535 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
536 across this point. Further, it might be a good idea to remove
540 Remove deprecated locale names and transition period code
541 for them, finishing switching to the new scheme. Check your
542 LANG environment variable.
545 CCD has been changed to be a fully GEOMified class. Kernel
546 and ccdconfig(8) needs to be in sync, this is particularly
547 important to remember beforehand if your source tree is on
548 a ccd device. Consider making a copy of the old ccdconfig
549 into /boot/kernel.good or wherever you keep your backup
553 There was a small window in which sed(1) was broken. If you
554 happen to have sed(1) installed during that window, which is
555 evidenced by an inability to build world with the failure
556 given below, you need to manually build and install sed(1)
557 (and only sed(1)) before doing anything else. This is a one-
558 time snafu. Typical failure mode:
560 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
561 targmatch.h:7:1: null character(s) ignored
562 targmatch.h:12:1: null character(s) ignored
563 targmatch.h:16:1: null character(s) ignored
566 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
567 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
568 usr.bin/sed/process.c).
571 Kerberos 5 (Heimdal) is now built by default. Setting
572 MAKE_KERBEROS5 no longer has any effect. If you do NOT
573 want the "base" Kerberos 5, you need to set NO_KERBEROS.
576 groff has been updated. If you try to do a buildworld and
577 get an infinite loop in troff, update to May 4th or newer. If you
578 have a newer kernel than userland, you may need to set the OSRELDATE
579 to 500110 in your environment before starting a buildworld.
582 The old rc system has been removed. Please report any problems
583 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
584 Your personal versions of these files will not be removed, so you can
585 continue to use them. However, you should take great care when updating,
586 especially when using mergemaster, since the compatibility code that
587 utilizes these old scripts has also been removed.
590 A bug has been fixed in /dev/devctl which would cause devd
591 to hang on boot, were it not for a workaround in devd. The
592 work around in devd will be removed around 20030507. You
593 have until then to upgrade your kernel before updating
594 userland. In general, you should have a userland and
595 kernel that's in sync with each other. However, given the
596 effects of this bug (hang on boot when starting devd), some
600 Alphas with libc from between 20030312 and 20030329 exhibit
601 floating point exceptions (FPEs), most notably in awk(1)
602 while upgrading the system through a buildworld.
604 So, to successfully upgrade your Alpha, you must either
605 downgrade your libc.so to a pre-20030312 version, or update
606 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
607 to CFLAGS, then forcibly rebuild and install libc:
609 cd /usr/src/lib/libc && \
610 make cleandir && make obj && \
611 make -DNOMAN -DNOPROFILE all && \
612 make -DNOMAN -DNOPROFILE install
615 sendmail 8.12.7 has been imported. It has one important
616 change for IPv6 users. The default submit.mc now uses
617 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
618 used to connect to the MTA. Users on IPv6-only machines
619 will need to edit /etc/mail/submit.mc appropriately.
622 NODEVFS option has been removed and DEVFS thereby made standard.
623 This makes all references to MAKEDEV obsolete, and they should
624 be removed when convenient.
627 The name of the device for the ofw console has changed, sparc64 users
628 must run mergemaster to update their installed /etc/ttys.
631 The scheduler framework has grown a second scheduler and consequently
632 you must specify one and only one scheduler in your kernel config.
633 The cvs config files have been updated to use the old scheduler
634 which may be selected via 'options SCHED_4BSD'. If you would like
635 to try the new, much more experimental, scheduler please try
636 'options SCHED_ULE' and contribute to the arch@ discussion.
639 A new version of the wi driver has been imported into the tree.
640 One now must have device wlan in the config file for it to operate
643 In addition, there have been some changes to how wi devices are
644 configured for point to point links to bring it more in line
645 with the former way of doing things, as well as compatibility
649 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
650 used an incompatible form of ABI for returning structures and unions
651 which FreeBSD's GCC maintainers were not aware of relative to previous
652 versions of FreeBSD. We have gone back to the ABI for now, and any
653 code compiled which is required to interoperate with other code (not
654 built at the same time) returning structs or unions should be
658 A name change in /etc/netconfig has been reverted to stay
659 compatible with suns TIRPC and also with NetBSD. You need
660 to run mergemaster after make world. A new libc does still work
661 with an outdated /etc/netconfig for some time, but you'll get
662 a warning. This warning will be removed in 20030301.
665 The recent binutils upgrade marks a kernel flag day on
666 sparc64: modules built with the old binutils will not work
667 with new kernels and vice versa. Mismatches will result in
668 panics. Make sure your kernel and modules are in sync.
671 The value of IPPROTO_DIVERT has changed. Make sure to keep
672 your kernel, netstat, natd and any third-party DIVERT
676 Old, compatibility slices have been removed in GEOM kernels.
677 This means that you will have to update your /etc/fstab to
678 not use disk devices of the form /dev/ad0a. Instead, you
679 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
680 partition really is on. The old device names have gone
681 away, so if you use them anywhere else, you must also adjust
682 those uses. (This doesn't affect the disks formatted in
683 the ``dangerously-dedicated'' mode.)
686 Alphas with kernels from between 20020830 and 20021023 and/or
687 rtld (ld-elf.so.1) older than 20021023 may experience problems
688 with groff while doing a buildworld (kernel: "out of memory",
689 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
690 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
692 So, to successfully upgrade your Alpha, you must either
693 upgrade your kernel and rtld first (which might be a bit
694 tricky), or avoid running the bootstrapped groff during the
695 "transitional" buildworld. To avoid running groff during the
696 transitional upgrade run make buildworld with -DNOMAN,
697 -DNO_SHAREDOCS, and -DNO_LPR.
700 gcc has been upgraded to 3.2. It is not all binary compatible
701 with earlier versions of gcc for c++ programs. All c++
702 programs and libraries need to be recompiled.
704 Also, if you encounter g++ issues, rm /usr/include/g++/* before
705 doing an installworld to make sure that stale files are removed.
708 Our /etc/termcap now has all the entries from the XFree86 xterm
709 almost unchanged. This means xterm now supports color by default.
710 If you used TERM=xterm-color in the past you now should use
711 TERM=xterm. (xterm-color will lead to benign warnings).
714 A "bug" in gcc(1) that was hiding warning in system headers was
715 fixed. It's probably time to add -DNO_WERROR to your make line
719 COPY is being deprecated. The 20010530 change was reverted, as
720 it causes far more pain than was expected, and to always compare
721 before installing, please use INSTALL="install -C" again. The
722 -C option is now silently ignored when used with the -d option.
725 Problems with libc_r clients like KDE and GNOME have been resolved.
726 There are still some minor problems with some signals but the
727 system is stable enough for general use again. SMP is less so than UP
728 but each can successfully complete multiple buildworlds.
729 Libkvm needs to be recompiled due to KSE.
732 Now would be a bad time to upgrade. Something in or near the
733 KSE commit totally broke programs using libc_r like KDE and
737 The k5su utility installed as part of Kerberos 5 is no longer
738 installed with the set-user-ID bit set by default. Add
739 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
740 with the set-user-ID bit set.
743 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
744 Unfortunately our native GDB (at version 4.18) does not understand
745 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
746 generated debugging information for our native GDB.
749 Due to the way CVS works, it may not properly update src/contrib/gcc
750 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
751 and then do a cvs update.
754 When exec'ing set[ug]id executables, the kernel now ensures that the
755 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
758 New sendmail startup scripts have been installed to make it
759 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
760 variable sendmail_enable to "NO" no longer prevents any sendmail
761 daemons from starting. Instead, either set sendmail_enable to
762 "NONE" or change mta_start_script to a script for starting
763 an alternative MTA. Setting mta_start_script to "" will
764 also prevent any MTA from being started at boot.
767 UCONSOLE is no longer a valid kernel option.
770 FreeBSD 5.0 DP-1 was basically branched today.
773 Warnings are now errors in the kernel. Unless you are a developer,
774 you should add -DNO_WERROR to your make line.
777 sendmail 8.12.2 has been imported. The sendmail binary is no
778 longer a set-user-ID root binary and the infrastructure to support
779 command line mail submission has changed. Be sure to run
780 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
781 and /etc/mail) and read /etc/mail/README for more details.
783 Due to the import of sendmail 8.12.2, a new user and group are
784 required in order for sendmail to run as a set-group-ID
785 binary. A 'make installworld' will use the new user and group
786 to set the owner and group of /var/spool/clientmqueue and will
787 fail if the new user and group do not exist. The 'smmsp' user
788 and group must be merged from src/etc/group and
789 src/etc/master.passwd before using 'make installworld'.
790 'mergemaster -p' will do this. You may need to install
791 mergemaster before this will work if you are updating from a
792 very old version of current. The updating recipe has changed
796 The preferred configuration method for PAM is now /etc/pam.d/
797 rather than /etc/pam.conf. If you have an unmodified
798 pam.conf, just delete it after your next mergemaster run. If
799 you have local modifications, you can use
800 /usr/src/etc/pam.d/convert.pl to incorporate them into your
803 Please see the following url for more details:
804 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
806 If anyone here is already using the new rc.conf(5) variable
807 networkfs_types, please note that it has changed
808 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
811 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
812 started out its life in the ISDN4BSD project as an offspring
813 from sys/net/if_spppsubr.c, which eventually got a life of its
814 own. All the accumulated features and bug fixes of the i4b
815 version have now been merged back into the base system's
816 version now. The only user-visible change resulting from this
817 is that i4b's sppp(4) interfaces are to be managed with
818 spppcontrol(8) again, since ispppcontrol(8) has been retired
819 as well. (There has never been rc file support for
820 ispppcontrol in -current, but only in -stable. That will be
821 reverted by the time the changes are MFCed.)
824 The fdc(4) driver has been updated and now automatically
825 recognizes media in `standard' formats (like 1440 KB and
826 720 KB for a 3.5" high-density drive) when accessing the
827 default device node (e. g. /dev/fd0). The old variety of
828 floppy device nodes /dev/fd*.* is no longer present by
829 default, devices can be created (in DEVFS) on demand. They
830 will need to be customized then for `odd' densities using
834 The bugs in procfs' debugging support code have been fixed,
835 and truss(1) now works again.
838 Daily security checks have been split out to use the periodic(8)
839 scripts. Some change in configuration may be necessary. Please
841 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
845 sos added VCD/SVCD support to ata driver and that needs the
846 kernel and burncd to be in sync.
849 The procfs pseudo-filesystem has now been converted to use the
850 pseudofs framework. If you have 'options PROCFS' in your
851 kernel config, you'll need to add 'options PSEUDOFS' if it's
854 This change temporarily breaks truss(1); use ktrace(1) instead
855 until the issue has been resolved.
858 A security hole in OpenSSH involving `UseLogin yes' has been
862 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
863 after this date. You need to do this only once.
866 Most of the awk issues have been resolved. Some rough
867 edges may be left, but for the most part things should be
868 back to "normal." For CURRENT's usual definition of "normal."
871 Awk has been upgraded to the one true awk from bell labs. Expect
872 choppy waves in the upgrade process.
875 The asr driver problem has been resolved.
878 Due to changes in other parts of the system, the asr driver
879 now causes the system to panic on boot. Do not use it pending
880 correction. Comment it out of any kernel config file that you
881 try to use from this date forward.
884 When crossbuilding, use TARGET=xxx where you used to use
885 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
886 unless you are changing both of them. To cross build pc98 on
887 an alpha, for example, you need to set TARGET=pc98 and
891 The kernel interface that burncd depends on has changed.
892 You must recompile both the kernel and userland applications
896 When crossbuilding, please set TARGET_ARCH rather than
897 MACHINE_ARCH to indicate the target. In the future, one will
898 set TARGET_MACHINE where you set MACHINE now. At the moment,
899 setting MACHINE alone for same MACHINE_ARCH machines works
900 (eg, you can build pc98 on an i386 machine and vice versa).
903 Some weird problems result from using ACPI on some machines.
904 To disable ACPI you can add
905 hint.acpi.0.disabled="1"
906 to /boot/loader.conf (or by putting set X=Y at the boot
909 Alternatively, you can remove it from /boot/kernel/acpi.ko
910 or use the MODULES_OVERRIDE function in your kernel config
911 file and not list acpi in that list.
914 The buildworld has been fixed. You may need to install
915 the 4.x compatibility libraries for some old binaries
916 to work. Add COMPAT4X=true to your /etc/make.conf to
917 get them installed on every installworld, or execute the
918 following to get them installed only once:
919 cd src/lib/compat/compat4x.<arch>
921 You will see ``__stdoutp undefined'' until you do this.
924 There's a bug in the world build process. The cross-tools
925 are build with the NEW headers, but the OLD libc.a. This
926 leads to all kinds of problems with the new libc. A temporary
928 CFLAGS="-O -pipe -D_OLD_STDIO"
929 before building world when upgrading from 4.x to current. This
930 can be removed afterwards.
932 A proper fix to the buildworld target is needed.
935 Peter has committed his new kthread nfs client/server code.
936 NFS may be unstable after this date.
939 KSE has hit the tree. Lots of things are now different in
940 the kernel. While a few problems were introduced in the
941 initial commit, most of the major ones have been found and
945 In OLDCARD, CardBus bridges appear to be stable. The work
946 arounds described in the 20010604 entry are now no longer
947 necessary and will be ignored. Most insert/remove problems
948 have been rectified around this date.
951 named now runs as user bind and group bind rather than as
952 root. If named_enable is set to YES in /etc/rc.conf, ensure
953 that user bind is available in /etc/passwd (using vipw(8))
954 and that group bind is available in /etc/group. Also make
955 sure that user or group bind has read (and not write)
956 permission for your name server configuration and that it
957 has read and write permission for your slave zone files and
960 If you wish to continue to run named as root (a less secure
961 alternative), add a line to /etc/rc.conf saying
966 The PAM libraries have had an API upgrade that is beyond
967 the ability of the shared library major number to handle.
968 It is manifested by PAM-using ports dumping core. The
969 solution is to rebuild those ports.
972 The kernel compile module has moved from src/sys/compile/FOO
973 to src/sys/${MACHINE}/compile/FOO.
976 The pccard modem issue from 20010613 has been corrected.
977 OLDCARD support is still a little weak in -current. slot 1 is
978 known not to work on some TI based cardbus bridges. Some
979 cardbus bridges do not properly detect insert/removal events.
980 IRQ configuration needs more safety belts.
983 Softupdates problems have been corrected.
986 Peter ripped out the linkerset support. You must, as always,
987 rerun config after you cvsup if you are using the traditional
988 kernel building methods.
991 pccard modems may not work with current after 20010604 date. Some
992 do, others result in panics. *MAKE*SURE* that you update your
993 config and /etc/rc.conf ala the 20010604 entry, or you will have
994 problems (this issue will be fixed, it just hasn't been yet).
997 SOFTUPDATES seem to be broken since the middle of May or so. Do not
998 use them in current. You can disable softupdates on all mounted
999 partitions, or remove SOFTUPDATES the kernel config file.
1002 After Peter's commits to the hints code, people have been noticing
1003 that certain devices are attached (or try to) twice. This is due
1004 to having both static hints as well as a /boot/device.hints. To
1005 work around this issue, please use only one or the other mechanism
1006 until this bug is fixed.
1008 Please note that a feature of config is that if you have config
1009 file FOO and FOO.hints, it automatically adds FOO.hints to the
1010 hints.c file, whether you want it to or not.
1013 Locale names have changed to match other systems better.
1016 pccard support for pci cards has been committed. You must change
1017 your /etc/pccard.conf irq lines. It must match the irq used by
1018 pcic device. Interrupt storms may result if you fail to do this.
1019 Interrupt storms look a lot like a hang.
1021 You must also install a new pccardd, otherwise you will get an
1022 interrupt storm at card reset time (just after it tells you what
1025 pccardd_flags="-I" is necessary for the time being. It tells pccardd
1026 not to ask the kernel if the interrupt is really free or not before
1027 using it. You can either change the /etc/pccard.conf irq lines to
1028 match pcic, or add "-i X" to the pccardd_flags.
1031 INSTALL=install -C is being deprecated. If you want to do this,
1032 use COPY=-C instead. The former method will be supported for only
1033 a limited time. If you see
1035 install: warning: the -d and -C options may not be specified together
1037 in your makeworld, then you need to migrate towards using
1041 It appears that vm is now stable enough to use again. However,
1042 there may be other problems, so caution is still urged. alpha
1043 definitely is in bad shape.
1046 Minor repo damage has happened. This may cause problems
1047 with cvsup of ports. If you get errors, please see
1048 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
1049 at the bottom for details on a workaround. The error message
1051 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1054 Vm and/or swapping are busted on -current. Please be patient.
1057 pccard has had much reorganizational work done to it over
1058 the past few days. Everything should still work, but if
1059 not, please contact imp@freebsd.org.
1062 ata ioctl changed. Make sure to recompile both kernel and
1063 userland at the same time.
1066 New ncurses imported.
1069 DEVFS is now opt out, not opt in. Barring major problems, this
1070 will be the only way to go starting July 1.
1073 OpenSSH has been updated to 2.9. Some defaults are different,
1074 including RhostsRSAAuthentication, which changes from yes to no.
1077 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1080 Building perl was broken at 02:25:25 PDT.
1083 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
1084 go back in the water.
1087 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
1088 this date, but before the correction date.
1091 old fsck and new kernel interactions appear to have been fixed.
1094 fsck and the kernel were changed to handle some optimizations
1095 to directory layout. This breaks backward compatibility.
1096 Update only if you understand that you must not use the old
1097 fsck with the new kernel ever.
1100 fsck has changed the meaning of the pass column in /etc/fstab.
1101 Please see the cvs commit to fsck.8 or the fsck.8 man page for
1102 details. It is unclear if changes to /etc/fstab are necessary.
1105 portmap had changed name to rpcbind for maximum POLA in your
1106 current world. /etc/hosts.{allow,deny} needs changes. nfs and
1107 other rpc based programs that rely on portmapper will not work
1108 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
1111 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1112 and ATA_ENABLE_TAGS are no longer kernel options. They have
1113 been replaced by tunables. See ata.4 for details.
1116 The fxp driver was converted to use miibus. If you compile
1117 fxp into your kernel statically, you will need to add miibus.
1120 The wi device now defaults to BSS (infrastructure) mode
1124 /dev/urandom should be a symbolic link to /dev/random now.
1125 Users of current not using DEVFS need to run MAKEDEV std.
1126 ssh might not work if you don't.
1129 The ed driver has been updated. It now allows mii attachments,
1130 which means that you must include the miibus in your kernel if
1131 you use the ed driver.
1134 The problems with libc have been corrected. It is now mostly
1135 safe to go back into the water.
1138 The size of FILE was changed. This breaks upgrading. If
1139 you must upgrade, be prepared for pain. It also breaks almost
1140 all binaries that you've compiled on -current. You are warned
1141 that before upgrading would be a good time to do a level 0
1142 dump of your system. No, really, I mean it this time.
1144 To get to the new system, you'll need to use the following
1145 workaround. Hopefully this can be sorted out so that we
1146 don't have to move this to the updating section.
1148 To get around the installworld problem, do:
1149 # cd /usr/src/usr.bin/sed
1153 If that doesn't work, then try:
1154 # make -k installworld
1158 DEVFS is now the default. If you use vinum, make sure that you
1159 do not include devfs in your kernel as problems result.
1162 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1163 Remove them from your config.
1166 ****************************** WARNING ******************************
1167 buildkernel has been changed slightly
1168 ****************************** WARNING ******************************
1169 KERNCONF replaces the variable KERNEL for buildkernel. You
1170 should update your scripts and make.conf accordingly.
1173 config has changed to allow DEV_FOO as a replacement for NFOO.
1174 This requires a new config to build correctly.
1177 The kernel option I386_CPU is now mutually exclusive with the
1178 other cpu types. If you have an i386 system, be sure that it
1179 only had this line. Remove it for all other configurations.
1182 Changes to the kernel require it and burncd be in sync.
1185 Everyone who has hw.sndunit set to something in
1186 /etc/sysctl.conf, it is now hw.snd.unit.
1189 ex and vi were broken by some changes to sys/queue.h. If you
1190 have a bad vi, you will see make buildworld fail with a core
1191 dump while building termcap. You can work around this problem
1192 by adding -k to your make buildworld. This will cause the
1193 build to complete and install a new vi. Once that's done, you
1194 can rebuild again without the -k to pick up anything that
1195 might have been ignored by the -k option.
1197 Others have suggested that you can just rebuild libc if your
1198 vi/ex is dynamically linked, but I've not received any reports
1202 There have been some changes to libcrypt in -current. The
1203 libscrypt/libdescrypt symlink silliness is gone and the installed
1204 libcrypt is fully functional. Be aware of this.
1207 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1208 now require the addition of flag 0x80000 to their config line
1209 in pccard.conf(5). This flag is not optional. These Linksys
1210 cards will not be recognized without it.
1213 Important new FreeBSD-version stuff: PAM support has been worked
1214 in, partially from the "Unix" OpenSSH version. This requires
1215 adding the following in pam.conf:
1217 sshd auth sufficient pam_skey.so
1218 sshd auth required pam_unix.so try_first_pass
1219 sshd session required pam_permit.so
1222 cvs updated to 1.11.
1225 The random device needs more entropy, so you need to make sure
1226 that you've run mergemaster to get a /etc/rc which will seed
1227 /dev/random. If you don't and the system hangs after ldconfig,
1228 then banging on the keyboard randomly until it unhangs is one
1232 ****************************** WARNING ******************************
1233 Sendmail has been updated.
1234 ****************************** WARNING ******************************
1235 o mail.local(8) is no longer installed as a set-user-id binary.
1236 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1238 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1240 o Now using sendmail's version of vacation(1).
1241 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1242 in /usr/share/sendmail/cf.
1243 o sendmail.cw changed to local-host-names
1245 More details can be found at
1246 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1249 The ports tree's new layout is in place. Be sure to update
1250 your entire ports tree, or you will have problems.
1253 The perl build procedure no longer installs miniperl, nor uses
1254 the installed miniperl. It is recommended that you delete
1258 This weekend the ports tree will be updated to a new layout.
1259 It will be in an inconsistent state until noted in the UPDATING
1260 file, or with asami-san's message to the relevant mailing
1261 lists. With this new layout, you'll need to update the whole
1262 tree for anything to work.
1265 There was a change in the passwd format. Need more information.
1268 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1269 place. Please update boot loader (not the boot blocks) at the
1270 same time as your kernel.
1273 The new pmtimer device is necessary for laptops. Failure to
1274 include the device will cause suspended laptops losing time
1275 when they resume. Include
1277 in your config file and
1278 hint.pmtimer.0.at="isa"
1279 to your /boot/device.hints file.
1282 The random device has been turned into a (pseudo-)device,
1283 rather than an option. The supplied kernel config files have
1284 been updated. You will need to do something similar in your
1285 own kernel config file.
1290 If you prefer to load the loadable module, you need to do
1294 The random device module has been renamed from randomdev.ko to
1295 random.ko. You will need to edit your /boot/loader.conf to
1296 reflect this if you load this module at boot time.
1297 The line should read:
1301 The SMPNG commit has happened. It should work, but if it
1302 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1303 to be a variety of minor issues. Please see 20000905 to make
1304 sure you don't have model loading problems which might at
1305 first blush appear related to SMP.
1308 nsswitch has been imported from NetBSD. Among other things,
1309 this means that /etc/host.conf is no longer used. See
1310 nsswitch.conf(5) instead. Note that at boot time rc.network
1311 will attempt to produce a new nsswitch.conf file for you if you
1312 don't have one, and you have host.conf.
1315 The ucred structure changed size. This breaks the interface
1316 that mountd uses. Trying to use an older mountd with a newer
1317 kernel guarantees a panic. This means that you need to use
1318 kernels newer than today only with matching mountd, but you
1319 needed to do that anyway with the boot loader changes.
1322 The boot loader has been updated. The new default kernel is
1323 now /boot/kernel/kernel.ko. The new default module location
1326 You *MUST* upgrade your boot loader and kernel at the same time.
1327 The easiest way to do this is to do the buildworld/buildkernel/
1328 installkernel/installworld dance.
1330 Furthermore, you are urged to delete your old /modules directory
1331 before booting the new kernel, since kldload will find stale
1332 modules in that directory instead of finding them in the correct
1333 path, /boot/kernel. The most common complaint that this cures
1334 is that the linux module crashes your machine after the update.
1336 if [ ! -d /boot/kernel.old ]; then
1337 mv /modules.old /boot/kernel.old
1338 chflags noschg /kernel.old
1339 mv /kernel.old /boot/kernel.old/kernel.ko
1340 chflags schg /boot/kernel.old/kernel.ko
1344 A new issue with the sendmail upgrade has come to light.
1345 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1346 incorrectly install the default aliases in /etc/mail rather than
1347 move the old one from /etc. So you'll need to manually move the
1348 file, create a symbolic link, remove the old /etc/aliases.db and
1349 run newaliases. For safety sake, you should stop sendmail
1350 while doing this and run the upgrade when locally sourced email
1351 is not likely to be generated.
1354 /boot/device.hints is now required for installkernel to
1355 succeed. You should copy GENERIC.hints for your architecture
1356 into /boot/device.hints. If and only if you compile hints
1357 into your kernel, then this file may be empty. Please note,
1358 if you have an empty or missing /boot/device.hints file and
1359 you neglected to compile hints into your kernel, no boot
1360 messages will appear after the boot loader tries to start the
1364 If you do NOT have ``options RANDOMDEV'' in your kernel and
1365 you DO want the random device then add randomdev_load="YES" to
1369 suidperl is now always built and installed on the system, but
1370 with permissions of 511. If you have applications that use
1371 this program, you are now required to add ENABLE_SUIDPERL=true
1372 to /etc/make.conf. If you forget to do this,
1373 chmod 4511 /usr/bin/suidperl
1374 will fix this until the next build.
1377 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1378 visible changes that may immediately affect your configuration
1380 - New default file locations from src/contrib/sendmail/cf/README
1381 - newaliases limited to root and trusted users
1382 - MSA port (587) turned on by default
1383 - New queue file naming system so can't go from 8.11 -> 8.9
1384 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1385 - FEATURE(`nullclient') is more full featured
1386 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1387 - mail.local FreeBSD-only -b option changed to -B
1388 - See src/contrib/sendmail/RELEASE_NOTES for more info
1391 suidperl (aka sperl) is no longer build by default. You must
1392 specifically define BUILD_SUIDPERL to "true" for it to be build.
1393 Furthermore, we recommend that you remove /usr/bin/sperl* and
1394 /usr/bin/suidperl files from your system unless you have a
1395 specific use for it.
1398 Networking defaults have been tightened. Anybody upgrading
1399 /etc/defaults/rc.conf needs to add the following lines to
1400 /etc/rc.conf if they want to have the same setup
1401 afterwards (unless the variables already are set, of course):
1402 # Enable network daemons for user convenience.
1404 portmap_enable="YES"
1405 sendmail_enable="YES"
1408 If you have null_load="YES" in your /boot/loader.conf, you
1409 will need to change that to nullfs_load="YES".
1412 The "installkernel" target has changed slightly. Now even if
1413 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1414 it will install the MYKERNEL file (built with the buildkernel
1415 target) as /kernel rather than /MYKERNEL. Those who have
1416 updated their /boot/loader.conf files to point to /MYKERNEL
1417 should remove that entry or perform manual rename of /kernel
1421 If you use CVSUP or CTM to get CVS trees, AND you used to get
1422 the old crypto files from internat.freebsd.org AND you check
1423 out files from the CVS tree with the cvs command, please read
1424 http://people.freebsd.org/~imp/internat.txt
1425 for details on potential problems that you might have and how
1428 If you are merely a mirror, or don't answer yes to each of the
1429 clauses above, you needn't worry.
1432 /etc/security has been updated to print the inode number of
1433 setuid programs that have changed. You will see a large spike
1434 in the number of changed programs the first time when you run
1435 mergemaster to get a new /etc/security.
1438 /dev/random now has good entropy collection (from the keyboard
1439 and sysmouse drivers). Please ensure that either `options
1440 RANDOMDEV' is present in your kernel config file or that
1441 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1442 not have the /dev/random driver, OpenSSL (and consequently
1443 lots of crypto tools (like SSH)) will fail with strange
1444 errors. (see below, 20000624).
1446 FreeBSD-current is safe again to run Crypto.
1449 phk made the malloc default options AJ. This may slow things
1450 down and uncover other latent bugs in the code. If you need to
1451 run at full speed, you can disable this by doing the following:
1452 ln -s aj /etc/malloc.conf
1455 libftpio's version was accidentally bumped a few days ago. This
1456 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1457 before doing your next buildworld/installworld pair. It certainly
1458 won't hurt to remove it before the update procedure. It will
1459 break fetch until a new one is built, but ftp can be used in the
1463 The crypto packages have changed for the cvsup. This has been done
1464 in a backward compatible way, but the old packages will go away at
1465 some point in the future. Look at /usr/share/examples/cvsup for
1469 With the new sys/modules/sound/drivers/*, you will need to
1470 set SYSDIR until you do an installworld after July 7th.
1473 rc.shutdown and rc will now call the rc.d scripts with start
1474 or stop. This may cause some harmless warnings from older
1475 rc.d scripts that haven't been updated.
1478 The libfetch based version of fetch has gone into the tree.
1479 Minor problems may result on some of the less popular sites,
1480 which should be reported to des@freebsd.org.
1483 From approximately this date forward, one must have the crypto
1484 system installed in order to build the system and kernel.
1485 While not technically strictly true, one should treat it as
1486 required and grab the crypto bits. If you are grabbing CVS
1487 trees, src-all and cvs-crypto should be treated as if they
1488 were required. You should check with the latest collections
1489 to make sure that these haven't changed.
1492 Mark Murray just committed the first parts of a cleanup of
1493 /dev/zero, et al. This is also cleaning up /dev/random.
1494 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1495 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1496 until Mark can merge in the fixes to this work in progress.
1497 openssh and openssl should not be used to generate keys from this
1498 date to the completion of the work.
1500 If you must operate at this reduced level of security, add '
1501 options RANDOMDEV' to your kernel or modload the randomdev
1502 module. You may also need to copy a new MAKEDEV to /dev and
1503 recreate the random and urandom devices.
1506 The license on the softupdates is now a standard 2 clause
1507 BSD license. You may need to remove your symbolic links
1508 that used to be required when updating.
1511 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1512 the config file update procedure.
1513 http://people.freebsd.org/~imp/config-upd.html
1514 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1515 isn't buildable. However, you can generate a LINT file:
1516 cd /sys/<ARCH>/conf && make LINT
1519 Binutils 2.10 have hit the tree, or will shortly. As soon
1520 as they do, the problem noted in 20000522 will be resolved and
1521 that workaround will no longer be required.
1524 phk removed the compatibility creation of wd devices in the
1525 ad driver. If you haven't done so already, you must update
1526 your fstab, etc to use the ad devices instead of the wd
1529 In addition, you'll need to update your boot blocks to a
1530 more modern version, if you haven't already done so. Modern
1531 here means 4.0 release or newer (although older releases
1535 Peter took an axe to config(8). Be sure that you read his mail
1536 on the topic before even thinking about updating. You will
1537 need to create a /boot/device.hints or add a hints directive
1538 to your config file to compile them in statically. The format
1539 of the config file has changed as well. Please see GENERIC or
1540 NEWCARD for examples of the new format.
1542 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1543 says that it has been fixed, assume that must use the hints mechanism
1544 in the loader if you need to use a machine with very old ISA cards
1548 A new set of binutils went into the tree today. Anybody
1549 building a kernel after this point is advised that they need
1550 to rebuild their binutils (or better yet do a
1551 buildworld/installworld) before building a new kernel.
1553 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1554 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1555 is recommended that you don't set this option until the problem
1559 The ethernet drivers were all updated to clean up the BPF handling.
1562 The problems with boot blocks on the alphas have been corrected.
1563 This will require some care in updating alphas. A new libstand
1564 is requires for the boot blocks to build properly.
1567 Recompile all kld modules. Proper version dependency info
1571 Modules have been disconnected from the buildworld tree and
1572 connected to the kernel building instead.
1575 You may need to build gperf
1576 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1577 when upgrading from 4.0 -> current. The build system now uses
1578 an option only in -current.
1581 The method that we brand ELF binaries has changed to be more
1582 acceptable to the binutils maintainers. You will need to
1583 rebrand your ELF binaries that aren't native. One problem
1584 binary is the Linux ldconfig. After your make world, but
1585 before you reboot, you'll need to issue:
1586 brandelf -t Linux /compat/linux/sbin/ldconfig
1587 if you have Linux compatibility enabled on your machine.
1590 If you have really bad/marginal IDE drives, you may find they
1591 don't work well. Use pio mode instead. The easiest way to
1592 cope if you have a problem combination is to add:
1593 /sbin/sysctl hw.ata.ata_dma=0
1594 to the start of /etc/rc.conf.
1597 The ISA and PCI compatibility shims have been connected to the
1598 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1599 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1600 include the appropriate option in your kernel config. Drivers
1601 using the shims should be updated or they won't ship with
1602 5.0-RELEASE, targeted for 2001.
1605 We've entered the traditional post release dumping party.
1606 Large kernel changes are being committed and are in the
1607 works. It is important to keep the systems' klds and kernel
1608 in sync as kernel interfaces and structures are changing.
1609 Before reporting kernel panics, make sure that all modules
1610 that you are loading are up to date.
1613 If you are upgrading from an older version of FreeBSD, you
1614 need to update your boot blocks as well. 'disklabel -B ad0'
1615 will do the trick. This isn't critical until you remove your
1616 wd device entries in /dev, at which point your system will not
1620 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1621 to upgrade to 4.0 from 3.x.
1625 # NOTE: 5.x below applies to 6.0-currrent as well, for the
1626 # momemnt. 4.any -> 5.any upgrade support will remain in
1627 # place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1628 # 6.0-current upgrade path will require moving through 5.3
1633 Avoid using make -j when upgrading. From time to time in the
1634 past there have been problems using -j with buildworld and/or
1635 installworld. This is especially true when upgrading between
1636 "distant" versions (eg one that cross a major release boundary
1637 or several minor releases, or when several months have passed
1638 on the -current branch).
1640 Sometimes, obscure build problems are the result of environment
1641 poisoning. This can happen because the make utility reads its
1642 environment when searching for values for global variables.
1643 To run your build attempts in an "environmental clean room",
1644 prefix all make commands with 'env -i '. See the env(1) manual
1645 page for more details.
1649 If you are updating from a prior version of FreeBSD (even one just
1650 a few days old), you should follow this procedure. With a
1651 /usr/obj tree with a fresh buildworld,
1652 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1653 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1655 To just build a kernel when you know that it won't mess you up
1656 --------------------------------------------------------------
1657 This assumes you are already running a 5.X system. Replace
1658 ${arch} with the architecture of your machine (e.g. "i386",
1659 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1661 cd src/sys/${arch}/conf
1662 config KERNEL_NAME_HERE
1663 cd ../compile/KERNEL_NAME_HERE
1668 If this fails, go to the "To build a kernel" section.
1670 To rebuild everything and install it on the current system.
1671 -----------------------------------------------------------
1672 # Note: sometimes if you are running current you gotta do more than
1673 # is listed here if you are upgrading from a really old current.
1675 <make sure you have good level 0 dumps>
1676 <maybe fix /etc/fstab> [7]
1678 make kernel KERNCONF=YOUR_KERNEL_HERE
1680 <reboot in single user> [3]
1681 src/etc/rc.d/preseedrandom [10]
1688 To cross-install current onto a separate partition
1689 --------------------------------------------------
1690 # In this approach we use a separate partition to hold
1691 # current's root, 'usr', and 'var' directories. A partition
1692 # holding "/", "/usr" and "/var" should be about 2GB in
1695 <make sure you have good level 0 dumps>
1698 <maybe newfs current's root partition>
1699 <mount current's root partition on directory ${CURRENT_ROOT}>
1700 make installworld DESTDIR=${CURRENT_ROOT}
1701 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1702 cp src/sys/${ARCH}/conf/GENERIC.hints \
1703 ${CURRENT_ROOT}/boot/device.hints # as needed
1704 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1705 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1706 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1707 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1708 <reboot into current>
1709 <do a "native" rebuild/install as described in the previous section>
1710 <maybe install compatibility libraries from src/lib/compat>
1714 To upgrade in-place from 4.x-stable to current
1715 ----------------------------------------------
1716 # 5.x uses more space than 4.x. Also, the location of kernel
1717 # modules has changed. If you are installing 5.x onto a 4.x
1718 # system, you'll need about 30MB of free disk space on your /
1719 # partition. If you have less than this, you may encounter difficult
1720 # to back out of problems with this procedure. If /tmp is on
1721 # the / partition, you may want to completely remove all its content
1722 # before upgrading, as this can be a common source of shortage of
1725 <make sure you have good level 0 dumps>
1726 <maybe fix /etc/fstab> [7]
1728 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1729 make kernel KERNCONF=YOUR_KERNEL_HERE [8]
1730 cd sys/boot ; make STRIP="" install [6]
1732 <reboot in single user> [3]
1733 src/etc/rc.d/preseedrandom [10]
1735 rm -rf /usr/include/g++
1740 Make sure that you've read the UPDATING file to understand the
1741 tweaks to various things you need. At this point in the life
1742 cycle of current, things change often and you are on your own
1743 to cope. The defaults can also change, so please read ALL of
1744 the UPDATING entries.
1746 Also, if you are tracking -current, you must be subscribed to
1747 freebsd-current@freebsd.org. Make sure that before you update
1748 your sources that you have read and understood all the recent
1749 messages there. If in doubt, please track -stable which has
1750 much fewer pitfalls.
1752 [1] If you have third party modules, such as vmware, you
1753 should disable them at this point so they don't crash your
1756 [2] If you have legacy ISA devices, you may need to create
1757 your own device.hints to reflect your unique hardware
1760 [3] From the bootblocks, boot -s, and then do
1765 adjkerntz -i # if CMOS is wall time
1766 Also, when doing a major release upgrade, it is required that
1767 you boot into single user mode to do the installworld.
1768 For the 4.x -> 5.x upgrade, you will also see many messages about
1769 needing to recompile your userland. These are harmless and can
1770 be ignored while you proceed to the next step.
1772 [4] Note: This step is non-optional. Failure to do this step
1773 can result in a significant reduction in the functionality of the
1774 system. Attempting to do it by hand is not recommended and those
1775 that pursue this avenue should read this file carefully, as well
1776 as the archives of freebsd-current and freebsd-hackers mailing lists
1777 for potential gotchas.
1779 [5] Usually this step is a noop. However, from time to time
1780 you may need to do this if you get unknown user in the following
1781 step. It never hurts to do it all the time. You may need to
1782 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1783 install) after the buildworld before this step if you last updated
1784 from current before 20020224 or from -stable before 20020408.
1786 [6] 4.x boot loader can be used to boot a 5.x system, however
1787 it is difficult to do that at best. If you wish to try, then
1788 you should interrupt the boot and at the ok prompt type:
1790 ok boot /boot/kernel/kernel
1791 If this fails to work, you must install a new boot loader as
1794 [7] Before you upgrade, please make sure that you are not using
1795 compatibility slices. These are device names of the form /dev/ad0a
1796 without the actual slice name. These will break with 5.x and newer.
1797 You generally must update these entries to use the post FreeBSD
1798 2.x form of /dev/ad0s1a. i386 and pc98 are affected, while alpha
1801 [8] In order to have a kernel that can run the 4.x binaries
1802 needed to do an installworld, you must include the COMPAT_FREEBSD4
1803 option in your kernel. Failure to do so may leave you with a system
1804 that is hard to boot to recover.
1806 Make sure that you merge any new devices from GENERIC since the
1807 last time you updated your kernel config file.
1809 [9] When checking out sources, you must include the -P flag to have
1810 cvs prune empty directories.
1812 If CPUTYPE is defined in your /etc/make.conf, make sure to use the
1813 "?=" instead of the "=" assignment operator, so that buildworld can
1814 override the CPUTYPE if it needs to.
1816 MAKEOBJDIRPREFIX must be defined in an environment variable, and
1817 not on the command line, or in /etc/make.conf. buildworld will
1818 warn if it is improperly defined.
1820 In case you would like to avoid installing new packages of everything,
1821 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1822 compatibility libraries are built which should allow you to continue
1823 using your existing software for a while. Alternatively, you can
1824 install the misc/compat4x port.
1826 [10] In order to create temporary files, /dev/random must be
1827 initialized by feeding data into it. src/etc/rc.d/preseedrandom
1831 This file contains a list, in reverse chronological order, of major
1832 breakages in tracking -current. Not all things will be listed here,
1833 and it only starts on March 15, 2000. Updating files can found in
1834 previous releases if your system is older than this.
1836 Copyright information:
1838 Copyright 1998-2004 M. Warner Losh. All Rights Reserved.
1840 Redistribution, publication, translation and use, with or without
1841 modification, in full or in part, in any form or format of this
1842 document are permitted without further permission from the author.
1844 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1845 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1846 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1847 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1848 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1849 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1850 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1851 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1852 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1853 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1854 POSSIBILITY OF SUCH DAMAGE.
1856 If you find this document useful, and you want to, you may buy the
1859 Contact Warner Losh if you have any questions about your use of