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 NOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
8 FreeBSD 5.x has many debugging features turned on, in
9 both the kernel and userland. These features attempt to detect
10 incorrect use of system primitives, and encourage loud failure
11 through extra sanity checking and fail stop semantics. They
12 also substantially impact system performance. If you want to
13 do performance measurement, benchmarking, and optimization,
14 you'll want to turn them off. This includes various WITNESS-
15 related kernel options, INVARIANTS, malloc debugging flags
16 in userland, and various verbose features in the kernel. Many
17 developers choose to disable these features on build machines
18 to maximize performance.
21 Network interface cloning has been overhauled. This change will
22 require a recompile of modules using cloning and modification of
23 external ones to the new API. __FreeBSD_version has been bumped
24 to 502119 to mark this change. Additionally, users creating
25 stf(4) interfaces via "ifconfig stf" will need to update their
26 scripts as this will create an interface named "stf" instead of
27 "stf0" and ifconfig will not print "stf0" to stdout.
30 On 20040524, the /etc/rc.d/nsswitch script was modified to
31 automatically create /etc/nsswitch.conf on startup if it did
32 not already exist. Unfortunately, an error in the man page
33 was carried over to the script, resulting in incorrect
34 nsswitch settings. The simplest remedy is to remove both
35 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
36 during the next reboot.
39 The return value of sema_timedwait(9) has been changed to
40 make it consistent with cv_timedwait(9). Be sure to recompile
41 the ips module and any third-party modules which call
45 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
46 Make sure to recompile modules and any userland that makes use of
47 sizeof(struct ifnet). In order to get the altq headers in place
48 please recompile and reinstall world.
51 Splitting kern_thread.c into 2 files (adding kern_kse.c)
52 requires that you re-run config after updating your tree.
55 The MIDI drivers have been removed. Until the new module-friendly
56 ones are merged, remove or comment out midi and seq from your
60 Due to a new option in ipfw (versrcreach) the ipfw(8) command
61 needs to be recompiled. Normal accept/reject rules without
62 options are not affected but those with options may break until
63 ipfw(8) is recompiled.
66 Due to changes in the callout ABI, kernels compiled after this
67 date may be incompatible with kernel modules compiled prior to
71 The PCI bus power state stuff has been turned on. If this causes
72 problems for your system, please disable it using the tunable
73 hw.pci.do_powerstate=0.
76 The bulk of the pci problems have been fixed, although the floppy
77 drive is still broken.
80 A substantial update to the pci bus resource and power management
81 have been committed. Expect a bumpy ride for a few days until
82 the unanticipated problems have been resolved.
85 Due to changes in the the Yarrow initialization process,
86 /dev/random needs to be fed before operations requiring
87 temp files can succeed in single user mode. This includes
88 running "make installworld". /dev/random may be fed by running
89 "/etc/rc.d/initrandom start" or with 20040415 source by running
90 "/etc/rc.d/preseedrandom".
93 The debug.mpsafenet tunable controls whether the kernel Giant
94 lock is held across the lower levels of the network stack, and
95 by default is turned off. In the few days following 20040322,
96 the behavior of debug.mpsafenet will change such that this
97 tunable controls Giant over all levels of the network stack.
98 If you are currently setting debug.mpsafenet to 1, you should
99 set it back to 0 (the default) again during the change-over.
100 An additional note will be added to UPDATING when sufficient
101 locking is merged to permit this to take place.
104 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
105 64-bits. This is a very major incompatible change, so people
106 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
107 detailed instructions on how to make this upgrade. People
108 upgrading FreeBSD on other platforms can ignore this event.
111 The packet filter (pf) is now installed with the base system. Make
112 sure to run mergemaster -p before installworld to create required
113 user account ("proxy"). If you do not want to build pf with your
114 system you can use the NO_PF knob in make.conf.
115 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
116 pf system consists of the following three devices:
118 device pflog # optional
119 device pfsync # optional
122 If you are having trouble with the libc_r -> libpthread transition
123 (see the 20040130 entry), place the following lines at the top of
126 libc_r.so.5 libpthread.so.1
127 libc_r.so libpthread.so
129 This will cause all programs and libraries linked against libc_r
130 to use libpthread instead.
133 Some sshd configuration defaults have changed: protocol version 1
134 is no longer enabled by default, and password authentication is
135 disabled by default if PAM is enabled (which it is by default).
136 OpenSSH clients should not be affected by this; other clients may
137 have to be reconfigured, upgraded or replaced.
140 The ABIs defined in <resolv.h> and <netdb.h> have been updated
141 to support improved reentrancy. Multi-threaded programs that
142 reference the "_res" or "h_errno" symbols may experience some
143 problems if they are not recompiled. Single-threaded programs
144 should remain unaffected.
147 routed has been updated in the base system from the vendor
148 sources, routed v2.27, from rhyolite.com. This change means that
149 for users who use RIP's MD5 authentication feature, FreeBSD
150 -CURRENT's routed is now incompatible with previous versions
151 of FreeBSD; however it is now compatible with implementations
152 from Sun, Cisco and other vendors.
155 The tcpcb structure has changed and makes a recompile of libkvm
156 and related userland network utilities neccessary.
159 The cdevsw structure has changed in two externally visible ways.
160 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
161 Second, the d_version field must be filled in with D_VERSION.
162 Drivers outside the tree will need to be updated.
165 The /etc/rc.d/ttys script has been removed. It is no longer
166 necessary since devfs has been mandatory for some time.
169 libkse has been renamed back to libpthread and is now the
170 default threads library. The gcc -pthread option has also
171 been changed to link to libpthread instead of libc_r. For
172 alpha and sparc64 machines, libkse is not renamed and links
173 are installed so that libpthread points to libc_r. Until
174 the ports system is updated to handle this change, it is
175 recommended that folks install an /etc/libmap.conf(5) that
176 maps libc_r to libpthread. If you have any binaries or
177 libraries linked to libkse, then it is also recommended
178 that you map libkse to libpthread. Anyone that is using
179 nvidia supplied drivers and libraries should use a libmap.conf
180 that maps libpthread to libc_r since their drivers/libraries
181 do not work with libpthread.
184 ULE has entered into its probationary period as the default scheduler
185 in GENERIC. For the average user, interactivity is reported to be
186 better in many cases. On SMP machines ULE will be able to make more
187 efficient use of the available parallel resources. If you are not
188 running it now, please switch over, replacing the kernel option
189 SCHED_4BSD with SCHED_ULE.
192 Move LongRun support out of identcpu.c, where it hardly
193 belongs, into its own file and make it opt-in, not mandatory,
194 depending on CPU_ENABLE_LONGRUN config(8) option.
197 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
198 if the login process is unable to successfully set the
199 process credentials to include all groups defined for the
200 user. The current kernel limit is 16 groups; administrators
201 may wish to check that users do not have over 16 groups
202 defined, or they will be unable to log in.
205 The ACPI module has been reactivated. It is no longer required
206 to compile ACPI support into kernels statically.
209 The statfs structure has been updated with 64-bit fields to
210 allow accurate reporting of multi-terabyte filesystem
211 sizes. You should build world, then build and boot the new kernel
212 BEFORE doing a `installworld' as the new kernel will know about
213 binaries using the old statfs structure, but an old kernel will
214 not know about the new system calls that support the new statfs
216 Note that the backwards compatibility is only present when the
217 kernel is configured with the COMPAT_FREEBSD4 option. Since
218 even /bin/sh will not run with a new kernel without said option
219 you're pretty much dead in the water without it. Make sure you
220 have COMPAT_FREEBSD4!
221 Running an old kernel after a `make world' will cause programs
222 such as `df' that do a statfs system call to fail with a bad
223 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
224 that cfsd (ports/security/cfs) needs to be recompiled after
225 these changes are installed.
227 ****************************DANGER*******************************
229 DO NOT make installworld after the buildworld w/o building and
230 installing a new kernel FIRST. You will be unable to build a
231 new kernel otherwise on a system with new binaries and an old
235 Some netgraph string length constants have been changed. This
236 change requires the netgraph kernel modules and all netgraph
237 userland components to be in sync. Especially users who require
238 netgraph to boot need to make sure to have world and kernel in
239 sync before rebooting.
242 Hyperthreading logical CPU's are no longer probed by default
243 when using the MP Table. If ACPI is being used, then logical
244 CPUs will be probed if hyperthreading is enabled in the BIOS.
245 If ACPI is not being used and hyperthreading is enabled in the
246 BIOS, logical CPUs can be enabled by building a custom kernel
247 with the option MPTABLE_FORCE_HTT enabled.
250 The i386 APIC_IO kernel option has been replaced by
251 'device apic'. The ACPI module has also been temporarily
252 disabled, so ACPI must be statically compiled into your
253 kernel using 'device acpi' if you wish to use the ACPI driver.
256 The API and ABI of struct ifnet have been changed by removing
257 the if_name and if_unit members and replacing them with
258 if_xname, if_dname, and if_dunit. All network drivers and most
259 userland programs which include net/if_var.h must be updated
260 and recompiled. __FreeBSD_version has been bumped to 501113 to
264 Changes to the cdevsw default functions have been made to remove
265 the need to specify nullopen() and nullclose() explicitly.
266 __FreeBSD_version bumpted to 501110.
269 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
270 mount_cd9660(8) need to be in sync with kernel.
273 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
274 also be explicitly configured. Previously this dependency was
275 magically handled through some cruft in net/pfil.h; but that has
276 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
277 will fail with obtuse errors in ip_fil.c.
280 Fix a bug in arplookup(), whereby a hostile party on a locally
281 attached network could exhaust kernel memory, and cause a system
282 panic, by sending a flood of spoofed ARP requests. See
283 FreeBSD-SA-03:14.arp.
286 A change to /etc/defaults/rc.conf now causes inetd to be started
287 with `-C 60' if it is not overridden in /etc/rc.conf. This
288 causes inetd to stop accepting connections from an IP address
289 that exceeds the rate of 60 connections per minute.
292 The following rc.d scripts have been removed and should be
293 deleted from your installation: atm2.sh atm3.sh devdb
294 localdaemons network1 network2 network3. Depending on when
295 you last updated world and used mergemaster(8) you may or
296 may not have problems during the rc boot sequence. The simplest
297 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
298 The atm2.sh atm3.sh and devdb scripts were removed some time
299 ago, so depending on when you installed -CURRENT these scripts
300 may or may not exist on your system.
303 ATAng has been committed. You need to build world as sys/ata.h
304 has changed, and userland atacontrol depends on it.
305 If you use ATA SW raids you need "device ataraid" in your
306 kernel config file, as it is no longer pulled in automatically.
309 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
310 Among other things, this changes the device enumeration to be
311 closer to Solaris. Be aware that, this can even cause the machine
312 to not boot without manual intervention before the fstab is adjusted.
315 All current USB and Firewire quirks in da(4) have been deprecated
316 and will be removed for 5.2. If this causes failure for your
317 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
318 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
319 so the quirk can be re-enabled.
322 Problems with entry 20030714 have been corrected and no known issues
323 with /rescue and -j exist for host systems after this point in time.
326 FPU-less support has been removed from FreeBSD. Chances are you won't
327 notice. 386+387 support should still work after this change, but
328 it is now a minimum requirement for the i386 port that you have real
332 Some people are having problems with changes related to /rescue.
333 If you are building -j N, you will need to define NO_RESCUE. Others
334 will need to define it if /rescue has issues with their environment.
335 People should report those issues to current@.
338 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
339 across this point. Further, it might be a good idea to remove
343 Remove deprecated locale names and transition period code
344 for them, finishing switching to the new scheme. Check your
345 LANG environment variable.
348 CCD has been changed to be a fully GEOMified class. Kernel
349 and ccdconfig(8) needs to be in sync, this is particularly
350 important to remember beforehand if your source tree is on
351 a ccd device. Consider making a copy of the old ccdconfig
352 into /boot/kernel.good or wherever you keep your backup
356 There was a small window in which sed(1) was broken. If you
357 happen to have sed(1) installed during that window, which is
358 evidenced by an inability to build world with the failure
359 given below, you need to manually build and install sed(1)
360 (and only sed(1)) before doing anything else. This is a one-
361 time snafu. Typical failure mode:
363 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
364 targmatch.h:7:1: null character(s) ignored
365 targmatch.h:12:1: null character(s) ignored
366 targmatch.h:16:1: null character(s) ignored
369 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
370 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
371 usr.bin/sed/process.c).
374 Kerberos 5 (Heimdal) is now built by default. Setting
375 MAKE_KERBEROS5 no longer has any effect. If you do NOT
376 want the "base" Kerberos 5, you need to set NO_KERBEROS.
379 groff has been updated. If you try to do a buildworld and
380 get an infinite loop in troff, update to May 4th or newer. If you
381 have a newer kernel than userland, you may need to set the OSRELDATE
382 to 500110 in your environment before starting a buildworld.
385 The old rc system has been removed. Please report any problems
386 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
387 Your personal versions of these files will not be removed, so you can
388 continue to use them. However, you should take great care when updating,
389 especially when using mergemaster, since the compatibility code that
390 utilizes these old scripts has also been removed.
393 A bug has been fixed in /dev/devctl which would cause devd
394 to hang on boot, were it not for a workaround in devd. The
395 work around in devd will be removed around 20030507. You
396 have until then to upgrade your kernel before updating
397 userland. In general, you should have a userland and
398 kernel that's in sync with each other. However, given the
399 effects of this bug (hang on boot when starting devd), some
403 Alphas with libc from between 20030312 and 20030329 exhibit
404 floating point exceptions (FPEs), most notably in awk(1)
405 while upgrading the system through a buildworld.
407 So, to successfully upgrade your Alpha, you must either
408 downgrade your libc.so to a pre-20030312 version, or update
409 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
410 to CFLAGS, then forcibly rebuild and install libc:
412 cd /usr/src/lib/libc && \
413 make cleandir && make obj && \
414 make -DNOMAN -DNOPROFILE all && \
415 make -DNOMAN -DNOPROFILE install
418 sendmail 8.12.7 has been imported. It has one important
419 change for IPv6 users. The default submit.mc now uses
420 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
421 used to connect to the MTA. Users on IPv6-only machines
422 will need to edit /etc/mail/submit.mc appropriately.
425 NODEVFS option has been removed and DEVFS thereby made standard.
426 This makes all references to MAKEDEV obsolete, and they should
427 be removed when convenient.
430 The name of the device for the ofw console has changed, sparc64 users
431 must run mergemaster to update their installed /etc/ttys.
434 The scheduler framework has grown a second scheduler and consequently
435 you must specify one and only one scheduler in your kernel config.
436 The cvs config files have been updated to use the old scheduler
437 which may be selected via 'options SCHED_4BSD'. If you would like
438 to try the new, much more experimental, scheduler please try
439 'options SCHED_ULE' and contribute to the arch@ discussion.
442 A new version of the wi driver has been imported into the tree.
443 One now must have device wlan in the config file for it to operate
446 In addition, there have been some changes to how wi devices are
447 configured for point to point links to bring it more in line
448 with the former way of doing things, as well as compatibility
452 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
453 used an incompatible form of ABI for returning structures and unions
454 which FreeBSD's GCC maintainers were not aware of relative to previous
455 versions of FreeBSD. We have gone back to the ABI for now, and any
456 code compiled which is required to interoperate with other code (not
457 built at the same time) returning structs or unions should be
461 A name change in /etc/netconfig has been reverted to stay
462 compatible with suns TIRPC and also with NetBSD. You need
463 to run mergemaster after make world. A new libc does still work
464 with an outdated /etc/netconfig for some time, but you'll get
465 a warning. This warning will be removed in 20030301.
468 The recent binutils upgrade marks a kernel flag day on
469 sparc64: modules built with the old binutils will not work
470 with new kernels and vice versa. Mismatches will result in
471 panics. Make sure your kernel and modules are in sync.
474 The value of IPPROTO_DIVERT has changed. Make sure to keep
475 your kernel, netstat, natd and any third-party DIVERT
479 Old, compatibility slices have been removed in GEOM kernels.
480 This means that you will have to update your /etc/fstab to
481 not use disk devices of the form /dev/ad0a. Instead, you
482 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
483 partition really is on. The old device names have gone
484 away, so if you use them anywhere else, you must also adjust
485 those uses. (This doesn't affect the disks formatted in
486 the ``dangerously-dedicated'' mode.)
489 Alphas with kernels from between 20020830 and 20021023 and/or
490 rtld (ld-elf.so.1) older than 20021023 may experience problems
491 with groff while doing a buildworld (kernel: "out of memory",
492 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
493 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
495 So, to successfully upgrade your Alpha, you must either
496 upgrade your kernel and rtld first (which might be a bit
497 tricky), or avoid running the bootstrapped groff during the
498 "transitional" buildworld. To avoid running groff during the
499 transitional upgrade run make buildworld with -DNOMAN,
500 -DNO_SHAREDOCS, and -DNO_LPR.
503 gcc has been upgraded to 3.2. It is not all binary compatible
504 with earlier versions of gcc for c++ programs. All c++
505 programs and libraries need to be recompiled.
507 Also, if you encounter g++ issues, rm /usr/include/g++/* before
508 doing an installworld to make sure that stale files are removed.
511 Our /etc/termcap now has all the entries from the XFree86 xterm
512 almost unchanged. This means xterm now supports color by default.
513 If you used TERM=xterm-color in the past you now should use
514 TERM=xterm. (xterm-color will lead to benign warnings).
517 A "bug" in gcc(1) that was hiding warning in system headers was
518 fixed. It's probably time to add -DNO_WERROR to your make line
522 COPY is being deprecated. The 20010530 change was reverted, as
523 it causes far more pain than was expected, and to always compare
524 before installing, please use INSTALL="install -C" again. The
525 -C option is now silently ignored when used with the -d option.
528 Problems with libc_r clients like KDE and GNOME have been resolved.
529 There are still some minor problems with some signals but the
530 system is stable enough for general use again. SMP is less so than UP
531 but each can successfully complete multiple buildworlds.
532 Libkvm needs to be recompiled due to KSE.
535 Now would be a bad time to upgrade. Something in or near the
536 KSE commit totally broke programs using libc_r like KDE and
540 The k5su utility installed as part of Kerberos 5 is no longer
541 installed with the set-user-ID bit set by default. Add
542 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
543 with the set-user-ID bit set.
546 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
547 Unfortunately our native GDB (at version 4.18) does not understand
548 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
549 generated debugging information for our native GDB.
552 Due to the way CVS works, it may not properly update src/contrib/gcc
553 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
554 and then do a cvs update.
557 When exec'ing set[ug]id executables, the kernel now ensures that the
558 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
561 New sendmail startup scripts have been installed to make it
562 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
563 variable sendmail_enable to "NO" no longer prevents any sendmail
564 daemons from starting. Instead, either set sendmail_enable to
565 "NONE" or change mta_start_script to a script for starting
566 an alternative MTA. Setting mta_start_script to "" will
567 also prevent any MTA from being started at boot.
570 UCONSOLE is no longer a valid kernel option.
573 FreeBSD 5.0 DP-1 was basically branched today.
576 Warnings are now errors in the kernel. Unless you are a developer,
577 you should add -DNO_WERROR to your make line.
580 sendmail 8.12.2 has been imported. The sendmail binary is no
581 longer a set-user-ID root binary and the infrastructure to support
582 command line mail submission has changed. Be sure to run
583 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
584 and /etc/mail) and read /etc/mail/README for more details.
586 Due to the import of sendmail 8.12.2, a new user and group are
587 required in order for sendmail to run as a set-group-ID
588 binary. A 'make installworld' will use the new user and group
589 to set the owner and group of /var/spool/clientmqueue and will
590 fail if the new user and group do not exist. The 'smmsp' user
591 and group must be merged from src/etc/group and
592 src/etc/master.passwd before using 'make installworld'.
593 'mergemaster -p' will do this. You may need to install
594 mergemaster before this will work if you are updating from a
595 very old version of current. The updating recipe has changed
599 The preferred configuration method for PAM is now /etc/pam.d/
600 rather than /etc/pam.conf. If you have an unmodified
601 pam.conf, just delete it after your next mergemaster run. If
602 you have local modifications, you can use
603 /usr/src/etc/pam.d/convert.pl to incorporate them into your
606 Please see the following url for more details:
607 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
609 If anyone here is already using the new rc.conf(5) variable
610 networkfs_types, please note that it has changed
611 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
614 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
615 started out its life in the ISDN4BSD project as an offspring
616 from sys/net/if_spppsubr.c, which eventually got a life of its
617 own. All the accumulated features and bugfixes of the i4b
618 version have now been merged back into the base system's
619 version now. The only user-visible change resulting from this
620 is that i4b's sppp(4) interfaces are to be managed with
621 spppcontrol(8) again, since ispppcontrol(8) has been retired
622 as well. (There has never been rc file support for
623 ispppcontrol in -current, but only in -stable. That will be
624 reverted by the time the changes are MFCed.)
627 The fdc(4) driver has been updated and now automatically
628 recognizes media in `standard' formats (like 1440 KB and
629 720 KB for a 3.5" high-density drive) when accessing the
630 default device node (e. g. /dev/fd0). The old variety of
631 floppy device nodes /dev/fd*.* is no longer present by
632 default, devices can be created (in DEVFS) on demand. They
633 will need to be customized then for `odd' densities using
637 The bugs in procfs' debugging support code have been fixed,
638 and truss(1) now works again.
641 Daily security checks have been split out to use the periodic(8)
642 scripts. Some change in configuration may be necessary. Please
644 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
648 sos added VCD/SVCD support to ata driver and that needs the
649 kernel and burncd to be in sync.
652 The procfs pseudo-filesystem has now been converted to use the
653 pseudofs framework. If you have 'options PROCFS' in your
654 kernel config, you'll need to add 'options PSEUDOFS' if it's
657 This change temporarily breaks truss(1); use ktrace(1) instead
658 until the issue has been resolved.
661 A security hole in OpenSSH involving `UseLogin yes' has been
665 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
666 after this date. You need to do this only once.
669 Most of the awk issues have been resolved. Some rough
670 edges may be left, but for the most part things should be
671 back to "normal." For CURRENT's usual definition of "normal."
674 Awk has been upgraded to the one true awk from bell labs. Expect
675 choppy waves in the upgrade process.
678 The asr driver problem has been resolved.
681 Due to changes in other parts of the system, the asr driver
682 now causes the system to panic on boot. Do not use it pending
683 correction. Comment it out of any kernel config file that you
684 try to use from this date forward.
687 When crossbuilding, use TARGET=xxx where you used to use
688 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
689 unless you are changing both of them. To cross build pc98 on
690 an alpha, for example, you need to set TARGET=pc98 and
694 The kernel interface that burncd depends on has changed.
695 You must recompile both the kernel and userland applications
699 When crossbuilding, please set TARGET_ARCH rather than
700 MACHINE_ARCH to indicate the target. In the future, one will
701 set TARGET_MACHINE where you set MACHINE now. At the moment,
702 setting MACHINE alone for same MACHINE_ARCH machines works
703 (eg, you can build pc98 on an i386 machine and vice versa).
706 Some weird problems result from using ACPI on some machines.
707 To disable ACPI you can add
708 hint.acpi.0.disabled="1"
709 to /boot/loader.conf (or by putting set X=Y at the boot
712 Alternatively, you can remove it from /boot/kernel/acpi.ko
713 or use the MODULES_OVERRIDE function in your kernel config
714 file and not list acpi in that list.
717 The buildworld has been fixed. You may need to install
718 the 4.x compatibility libraries for some old binaries
719 to work. Add COMPAT4X=true to your /etc/make.conf to
720 get them installed on every installworld, or execute the
721 following to get them installed only once:
722 cd src/lib/compat/compat4x.<arch>
724 You will see ``__stdoutp undefined'' until you do this.
727 There's a bug in the world build process. The cross-tools
728 are build with the NEW headers, but the OLD libc.a. This
729 leads to all kinds of problems with the new libc. A temporary
731 CFLAGS="-O -pipe -D_OLD_STDIO"
732 before building world when upgrading from 4.x to current. This
733 can be removed afterwards.
735 A proper fix to the buildworld target is needed.
738 Peter has committed his new kthread nfs client/server code.
739 NFS may be unstable after this date.
742 KSE has hit the tree. Lots of things are now different in
743 the kernel. While a few problems were introduced in the
744 initial commit, most of the major ones have been found and
748 In OLDCARD, CardBus bridges appear to be stable. The work
749 arounds described in the 20010604 entry are now no longer
750 necessary and will be ignored. Most insert/remove problems
751 have been rectified around this date.
754 named now runs as user bind and group bind rather than as
755 root. If named_enable is set to YES in /etc/rc.conf, ensure
756 that user bind is available in /etc/passwd (using vipw(8))
757 and that group bind is available in /etc/group. Also make
758 sure that user or group bind has read (and not write)
759 permission for your name server configuration and that it
760 has read and write permission for your slave zone files and
763 If you wish to continue to run named as root (a less secure
764 alternative), add a line to /etc/rc.conf saying
769 The PAM libraries have had an API upgrade that is beyond
770 the ability of the shared library major number to handle.
771 It is manifested by PAM-using ports dumping core. The
772 solution is to rebuild those ports.
775 The kernel compile module has moved from src/sys/compile/FOO
776 to src/sys/${MACHINE}/compile/FOO.
779 The pccard modem issue from 20010613 has been corrected.
780 OLDCARD support is still a little weak in -current. slot 1 is
781 known not to work on some TI based cardbus bridges. Some
782 cardbus bridges do not properly detect insert/removal events.
783 IRQ configuration needs more safety belts.
786 Softupdates problems have been corrected.
789 Peter ripped out the linkerset support. You must, as always,
790 rerun config after you cvsup if you are using the traditional
791 kernel building methods.
794 pccard modems may not work with current after 20010604 date. Some
795 do, others result in panics. *MAKE*SURE* that you update your
796 config and /etc/rc.conf ala the 20010604 entry, or you will have
797 problems (this issue will be fixed, it just hasn't been yet).
800 SOFTUPDATES seem to be broken since the middle of May or so. Do not
801 use them in current. You can disable softupdates on all mounted
802 partitions, or remove SOFTUPDATES the kernel config file.
805 After Peter's commits to the hints code, people have been noticing
806 that certain devices are attached (or try to) twice. This is due
807 to having both static hints as well as a /boot/device.hints. To
808 work around this issue, please use only one or the other mechanism
809 until this bug is fixed.
811 Please note that a feature of config is that if you have config
812 file FOO and FOO.hints, it automatically adds FOO.hints to the
813 hints.c file, whether you want it to or not.
816 Locale names have changed to match other systems better.
819 pccard support for pci cards has been committed. You must change
820 your /etc/pccard.conf irq lines. It must match the irq used by
821 pcic device. Interrupt storms may result if you fail to do this.
822 Interrupt storms look a lot like a hang.
824 You must also install a new pccardd, otherwise you will get an
825 interrupt storm at card reset time (just after it tells you what
828 pccardd_flags="-I" is necessary for the time being. It tells pccardd
829 not to ask the kernel if the interrupt is really free or not before
830 using it. You can either change the /etc/pccard.conf irq lines to
831 match pcic, or add "-i X" to the pccardd_flags.
834 INSTALL=install -C is being deprecated. If you want to do this,
835 use COPY=-C instead. The former method will be supported for only
836 a limited time. If you see
838 install: warning: the -d and -C options may not be specified together
840 in your makeworld, then you need to migrate towards using
844 It appears that vm is now stable enough to use again. However,
845 there may be other problems, so caution is still urged. alpha
846 definitely is in bad shape.
849 Minor repo damage has happened. This may cause problems
850 with cvsup of ports. If you get errors, please see
851 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
852 at the bottom for details on a workaround. The error message
854 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
857 Vm and/or swapping are busted on -current. Please be patient.
860 pccard has had much reorganizational work done to it over
861 the past few days. Everything should still work, but if
862 not, please contact imp@freebsd.org.
865 ata ioctl changed. Make sure to recompile both kernel and
866 userland at the same time.
869 New ncurses imported.
872 DEVFS is now opt out, not opt in. Barring major problems, this
873 will be the only way to go starting July 1.
876 OpenSSH has been updated to 2.9. Some defaults are different,
877 including RhostsRSAAuthentication, which changes from yes to no.
880 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
883 Building perl was broken at 02:25:25 PDT.
886 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
887 go back in the water.
890 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
891 this date, but before the correction date.
894 old fsck and new kernel interactions appear to have been fixed.
897 fsck and the kernel were changed to handle some optimizations
898 to directory layout. This breaks backward compatibility.
899 Update only if you understand that you must not use the old
900 fsck with the new kernel ever.
903 fsck has changed the meaning of the pass column in /etc/fstab.
904 Please see the cvs commit to fsck.8 or the fsck.8 man page for
905 details. It is unclear if changes to /etc/fstab are necessary.
908 portmap had changed name to rpcbind for maximum POLA in your
909 current world. /etc/hosts.{allow,deny} needs changes. nfs and
910 other rpc based programs that rely on portmapper will not work
911 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
914 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
915 and ATA_ENABLE_TAGS are no longer kernel options. They have
916 been replaced by tunables. See ata.4 for details.
919 The fxp driver was converted to use miibus. If you compile
920 fxp into your kernel statically, you will need to add miibus.
923 The wi device now defaults to BSS (infrastructure) mode
927 /dev/urandom should be a symbolic link to /dev/random now.
928 Users of current not using DEVFS need to run MAKEDEV std.
929 ssh might not work if you don't.
932 The ed driver has been updated. It now allows mii attachments,
933 which means that you must include the miibus in your kernel if
934 you use the ed driver.
937 The problems with libc have been corrected. It is now mostly
938 safe to go back into the water.
941 The size of FILE was changed. This breaks upgrading. If
942 you must upgrade, be prepared for pain. It also breaks almost
943 all binaries that you've compiled on -current. You are warned
944 that before upgrading would be a good time to do a level 0
945 dump of your system. No, really, I mean it this time.
947 To get to the new system, you'll need to use the following
948 workaround. Hopefully this can be sorted out so that we
949 don't have to move this to the updating section.
951 To get around the installworld problem, do:
952 # cd /usr/src/usr.bin/sed
956 If that doesn't work, then try:
957 # make -k installworld
961 DEVFS is now the default. If you use vinum, make sure that you
962 do not include devfs in your kernel as problems result.
965 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
966 Remove them from your config.
969 ****************************** WARNING ******************************
970 buildkernel has been changed slightly
971 ****************************** WARNING ******************************
972 KERNCONF replaces the variable KERNEL for buildkernel. You
973 should update your scripts and make.conf accordingly.
976 config has changed to allow DEV_FOO as a replacement for NFOO.
977 This requires a new config to build correctly.
980 The kernel option I386_CPU is now mutually exclusive with the
981 other cpu types. If you have an i386 system, be sure that it
982 only had this line. Remove it for all other configurations.
985 Changes to the kernel require it and burncd be in sync.
988 Everyone who has hw.sndunit set to something in
989 /etc/sysctl.conf, it is now hw.snd.unit.
992 ex and vi were broken by some changes to sys/queue.h. If you
993 have a bad vi, you will see make buildworld fail with a core
994 dump while building termcap. You can work around this problem
995 by adding -k to your make buildworld. This will cause the
996 build to complete and install a new vi. Once that's done, you
997 can rebuild again without the -k to pick up anything that
998 might have been ignored by the -k option.
1000 Others have suggested that you can just rebuild libc if your
1001 vi/ex is dynamically linked, but I've not received any reports
1005 There have been some changes to libcrypt in -current. The
1006 libscrypt/libdescrypt symlink silliness is gone and the installed
1007 libcrypt is fully functional. Be aware of this.
1010 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1011 now require the addition of flag 0x80000 to their config line
1012 in pccard.conf(5). This flag is not optional. These Linksys
1013 cards will not be recognized without it.
1016 Important new FreeBSD-version stuff: PAM support has been worked
1017 in, partially from the "Unix" OpenSSH version. This requires
1018 adding the following in pam.conf:
1020 sshd auth sufficient pam_skey.so
1021 sshd auth required pam_unix.so try_first_pass
1022 sshd session required pam_permit.so
1025 cvs updated to 1.11.
1028 The random device needs more entropy, so you need to make sure
1029 that you've run mergemaster to get a /etc/rc which will seed
1030 /dev/random. If you don't and the system hangs after ldconfig,
1031 then banging on the keyboard randomly until it unhangs is one
1035 ****************************** WARNING ******************************
1036 Sendmail has been updated.
1037 ****************************** WARNING ******************************
1038 o mail.local(8) is no longer installed as a set-user-id binary.
1039 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1041 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1043 o Now using sendmail's version of vacation(1).
1044 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1045 in /usr/share/sendmail/cf.
1046 o sendmail.cw changed to local-host-names
1048 More details can be found at
1049 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1052 The ports tree's new layout is in place. Be sure to update
1053 your entire ports tree, or you will have problems.
1056 The perl build procedure no longer installs miniperl, nor uses
1057 the installed miniperl. It is recommended that you delete
1061 This weekend the ports tree will be updated to a new layout.
1062 It will be in an inconsistent state until noted in the UPDATING
1063 file, or with asami-san's message to the relevant mailing
1064 lists. With this new layout, you'll need to update the whole
1065 tree for anything to work.
1068 There was a change in the passwd format. Need more information.
1071 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1072 place. Please update boot loader (not the boot blocks) at the
1073 same time as your kernel.
1076 The new pmtimer device is necessary for laptops. Failure to
1077 include the device will cause suspended laptops losing time
1078 when they resume. Include
1080 in your config file and
1081 hint.pmtimer.0.at="isa"
1082 to your /boot/device.hints file.
1085 The random device has been turned into a (pseudo-)device,
1086 rather than an option. The supplied kernel config files have
1087 been updated. You will need to do something similar in your
1088 own kernel config file.
1093 If you prefer to load the loadable module, you need to do
1097 The random device module has been renamed from randomdev.ko to
1098 random.ko. You will need to edit your /boot/loader.conf to
1099 reflect this if you load this module at boot time.
1100 The line should read:
1104 The SMPNG commit has happened. It should work, but if it
1105 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1106 to be a variety of minor issues. Please see 20000905 to make
1107 sure you don't have model loading problems which might at
1108 first blush appear related to SMP.
1111 nsswitch has been imported from NetBSD. Among other things,
1112 this means that /etc/host.conf is no longer used. See
1113 nsswitch.conf(5) instead. Note that at boot time rc.network
1114 will attempt to produce a new nsswitch.conf file for you if you
1115 don't have one, and you have host.conf.
1118 The ucred structure changed size. This breaks the interface
1119 that mountd uses. Trying to use an older mountd with a newer
1120 kernel guarantees a panic. This means that you need to use
1121 kernels newer than today only with matching mountd, but you
1122 needed to do that anyway with the boot loader changes.
1125 The boot loader has been updated. The new default kernel is
1126 now /boot/kernel/kernel.ko. The new default module location
1129 You *MUST* upgrade your boot loader and kernel at the same time.
1130 The easiest way to do this is to do the buildworld/buildkernel/
1131 installkernel/installworld dance.
1133 Furthermore, you are urged to delete your old /modules directory
1134 before booting the new kernel, since kldload will find stale
1135 modules in that directory instead of finding them in the correct
1136 path, /boot/kernel. The most common complaint that this cures
1137 is that the linux module crashes your machine after the update.
1139 if [ ! -d /boot/kernel.old ]; then
1140 mv /modules.old /boot/kernel.old
1141 chflags noschg /kernel.old
1142 mv /kernel.old /boot/kernel.old/kernel.ko
1143 chflags schg /boot/kernel.old/kernel.ko
1147 A new issue with the sendmail upgrade has come to light.
1148 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1149 incorrectly install the default aliases in /etc/mail rather than
1150 move the old one from /etc. So you'll need to manually move the
1151 file, create a symbolic link, remove the old /etc/aliases.db and
1152 run newaliases. For safety sake, you should stop sendmail
1153 while doing this and run the upgrade when locally sourced email
1154 is not likely to be generated.
1157 /boot/device.hints is now required for installkernel to
1158 succeed. You should copy GENERIC.hints for your architecture
1159 into /boot/device.hints. If and only if you compile hints
1160 into your kernel, then this file may be empty. Please note,
1161 if you have an empty or missing /boot/device.hints file and
1162 you neglected to compile hints into your kernel, no boot
1163 messages will appear after the boot loader tries to start the
1167 If you do NOT have ``options RANDOMDEV'' in your kernel and
1168 you DO want the random device then add randomdev_load="YES" to
1172 suidperl is now always built and installed on the system, but
1173 with permissions of 511. If you have applications that use
1174 this program, you are now required to add ENABLE_SUIDPERL=true
1175 to /etc/make.conf. If you forget to do this,
1176 chmod 4511 /usr/bin/suidperl
1177 will fix this until the next build.
1180 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1181 visible changes that may immediately affect your configuration
1183 - New default file locations from src/contrib/sendmail/cf/README
1184 - newaliases limited to root and trusted users
1185 - MSA port (587) turned on by default
1186 - New queue file naming system so can't go from 8.11 -> 8.9
1187 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1188 - FEATURE(`nullclient') is more full featured
1189 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1190 - mail.local FreeBSD-only -b option changed to -B
1191 - See src/contrib/sendmail/RELEASE_NOTES for more info
1194 suidperl (aka sperl) is no longer build by default. You must
1195 specifically define BUILD_SUIDPERL to "true" for it to be build.
1196 Furthermore, we recommend that you remove /usr/bin/sperl* and
1197 /usr/bin/suidperl files from your system unless you have a
1198 specific use for it.
1201 Networking defaults have been tightened. Anybody upgrading
1202 /etc/defaults/rc.conf needs to add the following lines to
1203 /etc/rc.conf if they want to have the same setup
1204 afterwards (unless the variables already are set, of course):
1205 # Enable network daemons for user convenience.
1207 portmap_enable="YES"
1208 sendmail_enable="YES"
1211 If you have null_load="YES" in your /boot/loader.conf, you
1212 will need to change that to nullfs_load="YES".
1215 The "installkernel" target has changed slightly. Now even if
1216 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1217 it will install the MYKERNEL file (built with the buildkernel
1218 target) as /kernel rather than /MYKERNEL. Those who have
1219 updated their /boot/loader.conf files to point to /MYKERNEL
1220 should remove that entry or perform manual rename of /kernel
1224 If you use CVSUP or CTM to get CVS trees, AND you used to get
1225 the old crypto files from internat.freebsd.org AND you check
1226 out files from the CVS tree with the cvs command, please read
1227 http://people.freebsd.org/~imp/internat.txt
1228 for details on potential problems that you might have and how
1231 If you are merely a mirror, or don't answer yes to each of the
1232 clauses above, you needn't worry.
1235 /etc/security has been updated to print the inode number of
1236 setuid programs that have changed. You will see a large spike
1237 in the number of changed programs the first time when you run
1238 mergemaster to get a new /etc/security.
1241 /dev/random now has good entropy collection (from the keyboard
1242 and sysmouse drivers). Please ensure that either `options
1243 RANDOMDEV' is present in your kernel config file or that
1244 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1245 not have the /dev/random driver, OpenSSL (and consequently
1246 lots of crypto tools (like SSH)) will fail with strange
1247 errors. (see below, 20000624).
1249 FreeBSD-current is safe again to run Crypto.
1252 phk made the malloc default options AJ. This may slow things
1253 down and uncover other latent bugs in the code. If you need to
1254 run at full speed, you can disable this by doing the following:
1255 ln -s aj /etc/malloc.conf
1258 libftpio's version was accidentally bumped a few days ago. This
1259 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1260 before doing your next buildworld/installworld pair. It certainly
1261 won't hurt to remove it before the update procedure. It will
1262 break fetch until a new one is built, but ftp can be used in the
1266 The crypto packages have changed for the cvsup. This has been done
1267 in a backward compatible way, but the old packages will go away at
1268 some point in the future. Look at /usr/share/examples/cvsup for
1272 With the new sys/modules/sound/drivers/*, you will need to
1273 set SYSDIR until you do an installworld after July 7th.
1276 rc.shutdown and rc will now call the rc.d scripts with start
1277 or stop. This may cause some harmless warnings from older
1278 rc.d scripts that haven't been updated.
1281 The libfetch based version of fetch has gone into the tree.
1282 Minor problems may result on some of the less popular sites,
1283 which should be reported to des@freebsd.org.
1286 From approximately this date forward, one must have the crypto
1287 system installed in order to build the system and kernel.
1288 While not technically strictly true, one should treat it as
1289 required and grab the crypto bits. If you are grabbing CVS
1290 trees, src-all and cvs-crypto should be treated as if they
1291 were required. You should check with the latest collections
1292 to make sure that these haven't changed.
1295 Mark Murray just committed the first parts of a cleanup of
1296 /dev/zero, et al. This is also cleaning up /dev/random.
1297 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1298 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1299 until Mark can merge in the fixes to this work in progress.
1300 openssh and openssl should not be used to generate keys from this
1301 date to the completion of the work.
1303 If you must operate at this reduced level of security, add '
1304 options RANDOMDEV' to your kernel or modload the randomdev
1305 module. You may also need to copy a new MAKEDEV to /dev and
1306 recreate the random and urandom devices.
1309 The license on the softupdates is now a standard 2 clause
1310 BSD license. You may need to remove your symbolic links
1311 that used to be required when updating.
1314 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1315 the config file update procedure.
1316 http://people.freebsd.org/~imp/config-upd.html
1317 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1318 isn't buildable. However, you can generate a LINT file:
1319 cd /sys/<ARCH>/conf && make LINT
1322 Binutils 2.10 have hit the tree, or will shortly. As soon
1323 as they do, the problem noted in 20000522 will be resolved and
1324 that workaround will no longer be required.
1327 phk removed the compatibility creation of wd devices in the
1328 ad driver. If you haven't done so already, you must update
1329 your fstab, etc to use the ad devices instead of the wd
1332 In addition, you'll need to update your boot blocks to a
1333 more modern version, if you haven't already done so. Modern
1334 here means 4.0 release or newer (although older releases
1338 Peter took an axe to config(8). Be sure that you read his mail
1339 on the topic before even thinking about updating. You will
1340 need to create a /boot/device.hints or add a hints directive
1341 to your config file to compile them in statically. The format
1342 of the config file has changed as well. Please see GENERIC or
1343 NEWCARD for examples of the new format.
1345 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1346 says that it has been fixed, assume that must use the hints mechanism
1347 in the loader if you need to use a machine with very old ISA cards
1351 A new set of binutils went into the tree today. Anybody
1352 building a kernel after this point is advised that they need
1353 to rebuild their binutils (or better yet do a
1354 buildworld/installworld) before building a new kernel.
1356 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1357 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1358 is recommended that you don't set this option until the problem
1362 The ethernet drivers were all updated to clean up the BPF handling.
1365 The problems with boot blocks on the alphas have been corrected.
1366 This will require some care in updating alphas. A new libstand
1367 is requires for the boot blocks to build properly.
1370 Recompile all kld modules. Proper version dependency info
1374 Modules have been disconnected from the buildworld tree and
1375 connected to the kernel building instead.
1378 You may need to build gperf
1379 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1380 when upgrading from 4.0 -> current. The build system now uses
1381 an option only in -current.
1384 The method that we brand ELF binaries has changed to be more
1385 acceptable to the binutils maintainers. You will need to
1386 rebrand your ELF binaries that aren't native. One problem
1387 binary is the Linux ldconfig. After your make world, but
1388 before you reboot, you'll need to issue:
1389 brandelf -t Linux /compat/linux/sbin/ldconfig
1390 if you have Linux compatibility enabled on your machine.
1393 If you have really bad/marginal IDE drives, you may find they
1394 don't work well. Use pio mode instead. The easiest way to
1395 cope if you have a problem combination is to add:
1396 /sbin/sysctl hw.ata.ata_dma=0
1397 to the start of /etc/rc.conf.
1400 The ISA and PCI compatibility shims have been connected to the
1401 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1402 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1403 include the appropriate option in your kernel config. Drivers
1404 using the shims should be updated or they won't ship with
1405 5.0-RELEASE, targeted for 2001.
1408 We've entered the traditional post release dumping party.
1409 Large kernel changes are being committed and are in the
1410 works. It is important to keep the systems' klds and kernel
1411 in sync as kernel interfaces and structures are changing.
1412 Before reporting kernel panics, make sure that all modules
1413 that you are loading are up to date.
1416 If you are upgrading from an older version of FreeBSD, you
1417 need to update your boot blocks as well. 'disklabel -B ad0'
1418 will do the trick. This isn't critical until you remove your
1419 wd device entries in /dev, at which point your system will not
1423 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1424 to upgrade to 4.0 from 3.x.
1430 Avoid using make -j when upgrading. From time to time in the
1431 past there have been problems using -j with buildworld and/or
1432 installworld. This is especially true when upgrading between
1433 "distant" versions (eg one that cross a major release boundary
1434 or several minor releases, or when several months have passed
1435 on the -current branch).
1437 Sometimes, obscure build problems are the result of environment
1438 poisoning. This can happen because the make utility reads its
1439 environment when searching for values for global variables.
1440 To run your build attempts in an "environmental clean room",
1441 prefix all make commands with 'env -i '. See the env(1) manual
1442 page for more details.
1446 If you are updating from a prior version of FreeBSD (even one just
1447 a few days old), you should follow this procedure. With a
1448 /usr/obj tree with a fresh buildworld,
1449 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1450 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1452 To just build a kernel when you know that it won't mess you up
1453 --------------------------------------------------------------
1454 This assumes you are already running a 5.X system. Replace
1455 ${arch} with the architecture of your machine (e.g. "i386",
1456 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1458 cd src/sys/${arch}/conf
1459 config KERNEL_NAME_HERE
1460 cd ../compile/KERNEL_NAME_HERE
1465 If this fails, go to the "To build a kernel" section.
1467 To rebuild everything and install it on the current system.
1468 -----------------------------------------------------------
1469 # Note: sometimes if you are running current you gotta do more than
1470 # is listed here if you are upgrading from a really old current.
1472 <make sure you have good level 0 dumps>
1473 <maybe fix /etc/fstab> [7]
1475 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1476 make installkernel KERNCONF=YOUR_KERNEL_HERE
1478 <reboot in single user> [3]
1479 /etc/rc.d/preseedrandom [10]
1486 To cross-install current onto a separate partition
1487 --------------------------------------------------
1488 # In this approach we use a separate partition to hold
1489 # current's root, 'usr', and 'var' directories. A partition
1490 # holding "/", "/usr" and "/var" should be about 2GB in
1493 <make sure you have good level 0 dumps>
1496 <maybe newfs current's root partition>
1497 <mount current's root partition on directory ${CURRENT_ROOT}>
1498 make installworld DESTDIR=${CURRENT_ROOT}
1499 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1500 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1501 ${CURRENT_ROOT}/boot/device.hints # as needed
1502 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1503 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1504 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1505 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1506 <reboot into current>
1507 <do a "native" rebuild/install as described in the previous section>
1508 <maybe install compatibility libraries from /usr/src/lib/compat>
1512 To upgrade in-place from 4.x-stable to current
1513 ----------------------------------------------
1514 # 5.x uses more space than 4.x. Also, the location of kernel
1515 # modules has changed. If you are installing 5.0 onto a 4.x
1516 # system, you'll need about 30MB of free disk space on your /
1517 # partition. If you have less than this, you may encounter difficult
1518 # to back out of problems with this procedure. If /tmp is on
1519 # the / partition, you may want to completely remove all its content
1520 # before upgrading, as this can be a common source of shortage of
1523 <make sure you have good level 0 dumps>
1524 <maybe fix /etc/fstab> [7]
1526 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1527 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1528 make installkernel KERNCONF=YOUR_KERNEL_HERE
1529 cd src/sys/boot ; make install [6]
1531 <reboot in single user> [3]
1532 /etc/rc.d/preseedrandom [10]
1534 rm -rf /usr/include/g++
1539 Make sure that you've read the UPDATING file to understand the
1540 tweaks to various things you need. At this point in the life
1541 cycle of current, things change often and you are on your own
1542 to cope. The defaults can also change, so please read ALL of
1543 the UPDATING entries.
1545 Also, if you are tracking -current, you must be subscribed to
1546 freebsd-current@freebsd.org. Make sure that before you update
1547 your sources that you have read and understood all the recent
1548 messages there. If in doubt, please track -stable which has
1549 much fewer pitfalls.
1551 [1] If you have third party modules, such as vmware, you
1552 should disable them at this point so they don't crash your
1555 [2] If you have legacy ISA devices, you may need to create
1556 your own device.hints to reflect your unique hardware
1559 [3] From the bootblocks, boot -s, and then do
1564 adjkerntz -i # if CMOS is wall time
1565 Also, when doing a major release upgrade, it is required that
1566 you boot into single user mode to do the installworld.
1567 For the 4.x -> 5.0 upgrade, you will also see many messages about
1568 needing to recompile your userland. These are harmless and can
1569 be ignored while you proceed to the next step.
1571 [4] Note: This step is non-optional. Failure to do this step
1572 can result in a significant reduction in the functionality of the
1573 system. Attempting to do it by hand is not recommended and those
1574 that pursue this avenue should read this file carefully, as well
1575 as the archives of freebsd-current and freebsd-hackers mailing lists
1576 for potential gotchas.
1578 [5] Usually this step is a noop. However, from time to time
1579 you may need to do this if you get unknown user in the following
1580 step. It never hurts to do it all the time. You may need to
1581 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1582 install) after the buildworld before this step if you last updated
1583 from current before 20020224 or from -stable before 20020408.
1585 [6] 4.x boot loader can be used to boot a 5.x system, however
1586 it is difficult to do that at best. If you wish to try, then
1587 you should interrupt the boot and at the ok prompt type:
1589 ok boot /boot/kernel/kernel
1590 If this fails to work, you must install a new boot loader as
1593 [7] Before you upgrade, please make sure that you are not using
1594 compatibility slices. These are device names of the form, on i386
1595 and other architectures that use MBR slicing, /dev/ad0a without the
1596 actual slice name. Chances are excellent that these will break.
1597 You generally must update these entries to use the post FreeBSD
1598 2.x form of /dev/ad0s1a.
1600 [8] In order to have a kernel that can run the 4.x binaries
1601 needed to do an installworld, you must include the COMPAT_FREEBSD4
1602 option in your kernel. Failure to do so may leave you with a system
1603 that is hard to boot to recover.
1605 [9] When checking out sources, you must include the -P flag to have
1606 cvs prune empty directories.
1608 [10] In order to create temporary files, /dev/random must be
1609 initialized by feeding data into it. /etc/rc.d/preseedrandom
1613 This file contains a list, in reverse chronological order, of major
1614 breakages in tracking -current. Not all things will be listed here,
1615 and it only starts on March 15, 2000. Updating files can found in
1616 previous releases if your system is older than this.
1618 Copyright information:
1620 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1622 Redistribution, publication, translation and use, with or without
1623 modification, in full or in part, in any form or format of this
1624 document are permitted without further permission from the author.
1626 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1627 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1628 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1629 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1630 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1631 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1632 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1633 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1634 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1635 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1636 POSSIBILITY OF SUCH DAMAGE.
1638 If you find this document useful, and you want to, you may buy the
1641 Contact Warner Losh if you have any questions about your use of