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 The rc.d/loclpkg script now "does the right thing" with respect
22 to ports rc.d scripts. The most disruptive change is that scripts
23 ending in *.sh are sourced in the same shell as rc.d/localpkg (as
24 opposed to a subshell) and may cause the script to end prematurely
25 if a script calls exit. Some broken scripts may not recognize the
26 'fast' prefix to a command. The first problem can be fixed by simply
27 renaming the script so that it doesn't have a '.sh' ending. Another
28 temporary work-arround is to completely remove the 'PROVIDE' line
29 from the script. If you notice a broken ports rc.d script please
30 notify the maintainer. Legacy scripts should not be affected.
31 __FreeBSD_version bumped to 502124.
34 The sound device drivers are renamed. `sound' is always required,
35 while `snd_*' should be configured accordingly to your hardware.
36 Refer to NOTES for the detail of the drivers.
39 __FreeBSD_version bumped to 502122.
42 The console initialization on Alpha has been reworked and is now
43 identical to other platforms. This means that the hardcoding of
44 the serial console and the debug port has been removed. As such,
45 hints are now required for the sio(4) driver to become a console
46 or debug port. The NO_SIO option has been decommissioned because
50 A revamp of the debugging code in the kernel with some visible
51 changes beyond just the debugging experience:
52 o The DDB option is now specific to the DDB debugger backend
53 and should not be used any more for conditional compilation
54 of debugging code for when debugging is enabled. Use the KDB
56 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
57 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
58 respectively. This is in line with the first bullet.
59 o The remote GDB support has been untangled from DDB and needs
60 to be enabled separately now. Use the GDB option for this.
61 o The GDB_REMOTE_CHAT option has been removed. Support for this
62 homegrown feature is discontinued. The GDB remote protocol
63 supports console output and it makes sense to use that.
64 o The DDB_NOKLDSYM option has been removed. The DDB debugger
65 now supports both direct symbol table lookups as well as KLD
66 symbol lookups through the linker.
69 Bluetooth code has been marked as non-i386 specific.
70 __FreeBSD_version has been bumped to 502121 to mark this change.
73 The native preemption has been added to the kernel scheduler.
74 There is some report that the ULE scheduler was broken in some
75 machines and we encourage users using the ULE scheduler either
76 stick with a known good kernel, or temporarily switch to the 4BSD
77 scheduler as a workaround.
80 The netgraph ABI version number has been incremented to indicate
81 an incompatible change in the ABI. Old netgraph nodes will refuse
82 to attach until recompiled. Netgraph now uses mbuf tags to move
83 metadata and this commit removes its home-grown metadata facility.
84 Nodes should just recompile, unless they use metadata, in which
85 case the changes are simple; the file ng_ksocket.c serves as an
86 example of such changes.
88 This also broke i4b, although the compile problem has been papered
92 ACPI has been updated to disable known-bad BIOS revisions. A message
93 will be printed on the console indicating that ACPI has been disabled
94 automatically and that the user should use a newer BIOS, if possible.
95 If you think ACPI does work on your system and want to override
96 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
100 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
101 separated now. It uses the newly created "_pflogd" user/group
102 combination. If you plan to use pflogd(8) make sure to run
103 mergemaster -p or install the "_pflogd" user and group manually.
106 Network interface cloning has been overhauled. This change will
107 require a recompile of modules using cloning and modification of
108 external ones to the new API. __FreeBSD_version has been bumped
109 to 502119 to mark this change. Additionally, users creating
110 stf(4) interfaces via "ifconfig stf" will need to update their
111 scripts as this will create an interface named "stf" instead of
112 "stf0" and ifconfig will not print "stf0" to stdout.
115 On 20040524, the /etc/rc.d/nsswitch script was modified to
116 automatically create /etc/nsswitch.conf on startup if it did
117 not already exist. Unfortunately, an error in the man page
118 was carried over to the script, resulting in incorrect
119 nsswitch settings. The simplest remedy is to remove both
120 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
121 during the next reboot.
124 The return value of sema_timedwait(9) has been changed to
125 make it consistent with cv_timedwait(9). Be sure to recompile
126 the ips module and any third-party modules which call
130 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
131 Make sure to recompile modules and any userland that makes use of
132 sizeof(struct ifnet). In order to get the altq headers in place
133 please recompile and reinstall world.
136 Splitting kern_thread.c into 2 files (adding kern_kse.c)
137 requires that you re-run config after updating your tree.
140 The MIDI drivers have been removed. Until the new module-friendly
141 ones are merged, remove or comment out midi and seq from your
142 kernel configuration.
145 Due to a new option in ipfw (versrcreach) the ipfw(8) command
146 needs to be recompiled. Normal accept/reject rules without
147 options are not affected but those with options may break until
148 ipfw(8) is recompiled.
151 Due to changes in the callout ABI, kernels compiled after this
152 date may be incompatible with kernel modules compiled prior to
156 The PCI bus power state stuff has been turned on. If this causes
157 problems for your system, please disable it using the tunable
158 hw.pci.do_powerstate=0.
161 The bulk of the pci problems have been fixed, although the floppy
162 drive is still broken.
165 A substantial update to the pci bus resource and power management
166 have been committed. Expect a bumpy ride for a few days until
167 the unanticipated problems have been resolved.
170 Due to changes in the the Yarrow initialization process,
171 /dev/random needs to be fed before operations requiring
172 temp files can succeed in single user mode. This includes
173 running "make installworld". /dev/random may be fed by running
174 "/etc/rc.d/initrandom start" or with 20040415 source by running
175 "/etc/rc.d/preseedrandom".
178 The debug.mpsafenet tunable controls whether the kernel Giant
179 lock is held across the lower levels of the network stack, and
180 by default is turned off. In the few days following 20040322,
181 the behavior of debug.mpsafenet will change such that this
182 tunable controls Giant over all levels of the network stack.
183 If you are currently setting debug.mpsafenet to 1, you should
184 set it back to 0 (the default) again during the change-over.
185 An additional note will be added to UPDATING when sufficient
186 locking is merged to permit this to take place.
189 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
190 64-bits. This is a very major incompatible change, so people
191 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
192 detailed instructions on how to make this upgrade. People
193 upgrading FreeBSD on other platforms can ignore this event.
196 The packet filter (pf) is now installed with the base system. Make
197 sure to run mergemaster -p before installworld to create required
198 user account ("proxy"). If you do not want to build pf with your
199 system you can use the NO_PF knob in make.conf.
200 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
201 pf system consists of the following three devices:
203 device pflog # optional
204 device pfsync # optional
207 If you are having trouble with the libc_r -> libpthread transition
208 (see the 20040130 entry), place the following lines at the top of
211 libc_r.so.5 libpthread.so.1
212 libc_r.so libpthread.so
214 This will cause all programs and libraries linked against libc_r
215 to use libpthread instead.
218 Some sshd configuration defaults have changed: protocol version 1
219 is no longer enabled by default, and password authentication is
220 disabled by default if PAM is enabled (which it is by default).
221 OpenSSH clients should not be affected by this; other clients may
222 have to be reconfigured, upgraded or replaced.
225 The ABIs defined in <resolv.h> and <netdb.h> have been updated
226 to support improved reentrancy. Multi-threaded programs that
227 reference the "_res" or "h_errno" symbols may experience some
228 problems if they are not recompiled. Single-threaded programs
229 should remain unaffected.
232 routed has been updated in the base system from the vendor
233 sources, routed v2.27, from rhyolite.com. This change means that
234 for users who use RIP's MD5 authentication feature, FreeBSD
235 -CURRENT's routed is now incompatible with previous versions
236 of FreeBSD; however it is now compatible with implementations
237 from Sun, Cisco and other vendors.
240 The tcpcb structure has changed and makes a recompile of libkvm
241 and related userland network utilities necessary.
244 The cdevsw structure has changed in two externally visible ways.
245 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
246 Second, the d_version field must be filled in with D_VERSION.
247 Drivers outside the tree will need to be updated.
250 The /etc/rc.d/ttys script has been removed. It is no longer
251 necessary since devfs has been mandatory for some time.
254 libkse has been renamed back to libpthread and is now the
255 default threads library. The gcc -pthread option has also
256 been changed to link to libpthread instead of libc_r. For
257 alpha and sparc64 machines, libkse is not renamed and links
258 are installed so that libpthread points to libc_r. Until
259 the ports system is updated to handle this change, it is
260 recommended that folks install an /etc/libmap.conf(5) that
261 maps libc_r to libpthread. If you have any binaries or
262 libraries linked to libkse, then it is also recommended
263 that you map libkse to libpthread. Anyone that is using
264 nvidia supplied drivers and libraries should use a libmap.conf
265 that maps libpthread to libc_r since their drivers/libraries
266 do not work with libpthread.
269 ULE has entered into its probationary period as the default scheduler
270 in GENERIC. For the average user, interactivity is reported to be
271 better in many cases. On SMP machines ULE will be able to make more
272 efficient use of the available parallel resources. If you are not
273 running it now, please switch over, replacing the kernel option
274 SCHED_4BSD with SCHED_ULE.
277 Move LongRun support out of identcpu.c, where it hardly
278 belongs, into its own file and make it opt-in, not mandatory,
279 depending on CPU_ENABLE_LONGRUN config(8) option.
282 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
283 if the login process is unable to successfully set the
284 process credentials to include all groups defined for the
285 user. The current kernel limit is 16 groups; administrators
286 may wish to check that users do not have over 16 groups
287 defined, or they will be unable to log in.
290 The ACPI module has been reactivated. It is no longer required
291 to compile ACPI support into kernels statically.
294 The statfs structure has been updated with 64-bit fields to
295 allow accurate reporting of multi-terabyte filesystem
296 sizes. You should build world, then build and boot the new kernel
297 BEFORE doing a `installworld' as the new kernel will know about
298 binaries using the old statfs structure, but an old kernel will
299 not know about the new system calls that support the new statfs
301 Note that the backwards compatibility is only present when the
302 kernel is configured with the COMPAT_FREEBSD4 option. Since
303 even /bin/sh will not run with a new kernel without said option
304 you're pretty much dead in the water without it. Make sure you
305 have COMPAT_FREEBSD4!
306 Running an old kernel after a `make world' will cause programs
307 such as `df' that do a statfs system call to fail with a bad
308 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
309 that cfsd (ports/security/cfs) needs to be recompiled after
310 these changes are installed.
312 ****************************DANGER*******************************
314 DO NOT make installworld after the buildworld w/o building and
315 installing a new kernel FIRST. You will be unable to build a
316 new kernel otherwise on a system with new binaries and an old
320 Some netgraph string length constants have been changed. This
321 change requires the netgraph kernel modules and all netgraph
322 userland components to be in sync. Especially users who require
323 netgraph to boot need to make sure to have world and kernel in
324 sync before rebooting.
327 Hyperthreading logical CPU's are no longer probed by default
328 when using the MP Table. If ACPI is being used, then logical
329 CPUs will be probed if hyperthreading is enabled in the BIOS.
330 If ACPI is not being used and hyperthreading is enabled in the
331 BIOS, logical CPUs can be enabled by building a custom kernel
332 with the option MPTABLE_FORCE_HTT enabled.
335 The i386 APIC_IO kernel option has been replaced by
336 'device apic'. The ACPI module has also been temporarily
337 disabled, so ACPI must be statically compiled into your
338 kernel using 'device acpi' if you wish to use the ACPI driver.
341 The API and ABI of struct ifnet have been changed by removing
342 the if_name and if_unit members and replacing them with
343 if_xname, if_dname, and if_dunit. All network drivers and most
344 userland programs which include net/if_var.h must be updated
345 and recompiled. __FreeBSD_version has been bumped to 501113 to
349 Changes to the cdevsw default functions have been made to remove
350 the need to specify nullopen() and nullclose() explicitly.
351 __FreeBSD_version bumped to 501110.
354 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
355 mount_cd9660(8) need to be in sync with kernel.
358 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
359 also be explicitly configured. Previously this dependency was
360 magically handled through some cruft in net/pfil.h; but that has
361 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
362 will fail with obtuse errors in ip_fil.c.
365 Fix a bug in arplookup(), whereby a hostile party on a locally
366 attached network could exhaust kernel memory, and cause a system
367 panic, by sending a flood of spoofed ARP requests. See
368 FreeBSD-SA-03:14.arp.
371 A change to /etc/defaults/rc.conf now causes inetd to be started
372 with `-C 60' if it is not overridden in /etc/rc.conf. This
373 causes inetd to stop accepting connections from an IP address
374 that exceeds the rate of 60 connections per minute.
377 The following rc.d scripts have been removed and should be
378 deleted from your installation: atm2.sh atm3.sh devdb
379 localdaemons network1 network2 network3. Depending on when
380 you last updated world and used mergemaster(8) you may or
381 may not have problems during the rc boot sequence. The simplest
382 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
383 The atm2.sh atm3.sh and devdb scripts were removed some time
384 ago, so depending on when you installed -CURRENT these scripts
385 may or may not exist on your system.
388 ATAng has been committed. You need to build world as sys/ata.h
389 has changed, and userland atacontrol depends on it.
390 If you use ATA SW raids you need "device ataraid" in your
391 kernel config file, as it is no longer pulled in automatically.
394 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
395 Among other things, this changes the device enumeration to be
396 closer to Solaris. Be aware that, this can even cause the machine
397 to not boot without manual intervention before the fstab is adjusted.
400 All current USB and Firewire quirks in da(4) have been deprecated
401 and will be removed for 5.2. If this causes failure for your
402 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
403 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
404 so the quirk can be re-enabled.
407 Problems with entry 20030714 have been corrected and no known issues
408 with /rescue and -j exist for host systems after this point in time.
411 FPU-less support has been removed from FreeBSD. Chances are you won't
412 notice. 386+387 support should still work after this change, but
413 it is now a minimum requirement for the i386 port that you have real
417 Some people are having problems with changes related to /rescue.
418 If you are building -j N, you will need to define NO_RESCUE. Others
419 will need to define it if /rescue has issues with their environment.
420 People should report those issues to current@.
423 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
424 across this point. Further, it might be a good idea to remove
428 Remove deprecated locale names and transition period code
429 for them, finishing switching to the new scheme. Check your
430 LANG environment variable.
433 CCD has been changed to be a fully GEOMified class. Kernel
434 and ccdconfig(8) needs to be in sync, this is particularly
435 important to remember beforehand if your source tree is on
436 a ccd device. Consider making a copy of the old ccdconfig
437 into /boot/kernel.good or wherever you keep your backup
441 There was a small window in which sed(1) was broken. If you
442 happen to have sed(1) installed during that window, which is
443 evidenced by an inability to build world with the failure
444 given below, you need to manually build and install sed(1)
445 (and only sed(1)) before doing anything else. This is a one-
446 time snafu. Typical failure mode:
448 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
449 targmatch.h:7:1: null character(s) ignored
450 targmatch.h:12:1: null character(s) ignored
451 targmatch.h:16:1: null character(s) ignored
454 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
455 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
456 usr.bin/sed/process.c).
459 Kerberos 5 (Heimdal) is now built by default. Setting
460 MAKE_KERBEROS5 no longer has any effect. If you do NOT
461 want the "base" Kerberos 5, you need to set NO_KERBEROS.
464 groff has been updated. If you try to do a buildworld and
465 get an infinite loop in troff, update to May 4th or newer. If you
466 have a newer kernel than userland, you may need to set the OSRELDATE
467 to 500110 in your environment before starting a buildworld.
470 The old rc system has been removed. Please report any problems
471 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
472 Your personal versions of these files will not be removed, so you can
473 continue to use them. However, you should take great care when updating,
474 especially when using mergemaster, since the compatibility code that
475 utilizes these old scripts has also been removed.
478 A bug has been fixed in /dev/devctl which would cause devd
479 to hang on boot, were it not for a workaround in devd. The
480 work around in devd will be removed around 20030507. You
481 have until then to upgrade your kernel before updating
482 userland. In general, you should have a userland and
483 kernel that's in sync with each other. However, given the
484 effects of this bug (hang on boot when starting devd), some
488 Alphas with libc from between 20030312 and 20030329 exhibit
489 floating point exceptions (FPEs), most notably in awk(1)
490 while upgrading the system through a buildworld.
492 So, to successfully upgrade your Alpha, you must either
493 downgrade your libc.so to a pre-20030312 version, or update
494 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
495 to CFLAGS, then forcibly rebuild and install libc:
497 cd /usr/src/lib/libc && \
498 make cleandir && make obj && \
499 make -DNOMAN -DNOPROFILE all && \
500 make -DNOMAN -DNOPROFILE install
503 sendmail 8.12.7 has been imported. It has one important
504 change for IPv6 users. The default submit.mc now uses
505 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
506 used to connect to the MTA. Users on IPv6-only machines
507 will need to edit /etc/mail/submit.mc appropriately.
510 NODEVFS option has been removed and DEVFS thereby made standard.
511 This makes all references to MAKEDEV obsolete, and they should
512 be removed when convenient.
515 The name of the device for the ofw console has changed, sparc64 users
516 must run mergemaster to update their installed /etc/ttys.
519 The scheduler framework has grown a second scheduler and consequently
520 you must specify one and only one scheduler in your kernel config.
521 The cvs config files have been updated to use the old scheduler
522 which may be selected via 'options SCHED_4BSD'. If you would like
523 to try the new, much more experimental, scheduler please try
524 'options SCHED_ULE' and contribute to the arch@ discussion.
527 A new version of the wi driver has been imported into the tree.
528 One now must have device wlan in the config file for it to operate
531 In addition, there have been some changes to how wi devices are
532 configured for point to point links to bring it more in line
533 with the former way of doing things, as well as compatibility
537 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
538 used an incompatible form of ABI for returning structures and unions
539 which FreeBSD's GCC maintainers were not aware of relative to previous
540 versions of FreeBSD. We have gone back to the ABI for now, and any
541 code compiled which is required to interoperate with other code (not
542 built at the same time) returning structs or unions should be
546 A name change in /etc/netconfig has been reverted to stay
547 compatible with suns TIRPC and also with NetBSD. You need
548 to run mergemaster after make world. A new libc does still work
549 with an outdated /etc/netconfig for some time, but you'll get
550 a warning. This warning will be removed in 20030301.
553 The recent binutils upgrade marks a kernel flag day on
554 sparc64: modules built with the old binutils will not work
555 with new kernels and vice versa. Mismatches will result in
556 panics. Make sure your kernel and modules are in sync.
559 The value of IPPROTO_DIVERT has changed. Make sure to keep
560 your kernel, netstat, natd and any third-party DIVERT
564 Old, compatibility slices have been removed in GEOM kernels.
565 This means that you will have to update your /etc/fstab to
566 not use disk devices of the form /dev/ad0a. Instead, you
567 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
568 partition really is on. The old device names have gone
569 away, so if you use them anywhere else, you must also adjust
570 those uses. (This doesn't affect the disks formatted in
571 the ``dangerously-dedicated'' mode.)
574 Alphas with kernels from between 20020830 and 20021023 and/or
575 rtld (ld-elf.so.1) older than 20021023 may experience problems
576 with groff while doing a buildworld (kernel: "out of memory",
577 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
578 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
580 So, to successfully upgrade your Alpha, you must either
581 upgrade your kernel and rtld first (which might be a bit
582 tricky), or avoid running the bootstrapped groff during the
583 "transitional" buildworld. To avoid running groff during the
584 transitional upgrade run make buildworld with -DNOMAN,
585 -DNO_SHAREDOCS, and -DNO_LPR.
588 gcc has been upgraded to 3.2. It is not all binary compatible
589 with earlier versions of gcc for c++ programs. All c++
590 programs and libraries need to be recompiled.
592 Also, if you encounter g++ issues, rm /usr/include/g++/* before
593 doing an installworld to make sure that stale files are removed.
596 Our /etc/termcap now has all the entries from the XFree86 xterm
597 almost unchanged. This means xterm now supports color by default.
598 If you used TERM=xterm-color in the past you now should use
599 TERM=xterm. (xterm-color will lead to benign warnings).
602 A "bug" in gcc(1) that was hiding warning in system headers was
603 fixed. It's probably time to add -DNO_WERROR to your make line
607 COPY is being deprecated. The 20010530 change was reverted, as
608 it causes far more pain than was expected, and to always compare
609 before installing, please use INSTALL="install -C" again. The
610 -C option is now silently ignored when used with the -d option.
613 Problems with libc_r clients like KDE and GNOME have been resolved.
614 There are still some minor problems with some signals but the
615 system is stable enough for general use again. SMP is less so than UP
616 but each can successfully complete multiple buildworlds.
617 Libkvm needs to be recompiled due to KSE.
620 Now would be a bad time to upgrade. Something in or near the
621 KSE commit totally broke programs using libc_r like KDE and
625 The k5su utility installed as part of Kerberos 5 is no longer
626 installed with the set-user-ID bit set by default. Add
627 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
628 with the set-user-ID bit set.
631 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
632 Unfortunately our native GDB (at version 4.18) does not understand
633 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
634 generated debugging information for our native GDB.
637 Due to the way CVS works, it may not properly update src/contrib/gcc
638 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
639 and then do a cvs update.
642 When exec'ing set[ug]id executables, the kernel now ensures that the
643 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
646 New sendmail startup scripts have been installed to make it
647 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
648 variable sendmail_enable to "NO" no longer prevents any sendmail
649 daemons from starting. Instead, either set sendmail_enable to
650 "NONE" or change mta_start_script to a script for starting
651 an alternative MTA. Setting mta_start_script to "" will
652 also prevent any MTA from being started at boot.
655 UCONSOLE is no longer a valid kernel option.
658 FreeBSD 5.0 DP-1 was basically branched today.
661 Warnings are now errors in the kernel. Unless you are a developer,
662 you should add -DNO_WERROR to your make line.
665 sendmail 8.12.2 has been imported. The sendmail binary is no
666 longer a set-user-ID root binary and the infrastructure to support
667 command line mail submission has changed. Be sure to run
668 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
669 and /etc/mail) and read /etc/mail/README for more details.
671 Due to the import of sendmail 8.12.2, a new user and group are
672 required in order for sendmail to run as a set-group-ID
673 binary. A 'make installworld' will use the new user and group
674 to set the owner and group of /var/spool/clientmqueue and will
675 fail if the new user and group do not exist. The 'smmsp' user
676 and group must be merged from src/etc/group and
677 src/etc/master.passwd before using 'make installworld'.
678 'mergemaster -p' will do this. You may need to install
679 mergemaster before this will work if you are updating from a
680 very old version of current. The updating recipe has changed
684 The preferred configuration method for PAM is now /etc/pam.d/
685 rather than /etc/pam.conf. If you have an unmodified
686 pam.conf, just delete it after your next mergemaster run. If
687 you have local modifications, you can use
688 /usr/src/etc/pam.d/convert.pl to incorporate them into your
691 Please see the following url for more details:
692 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
694 If anyone here is already using the new rc.conf(5) variable
695 networkfs_types, please note that it has changed
696 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
699 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
700 started out its life in the ISDN4BSD project as an offspring
701 from sys/net/if_spppsubr.c, which eventually got a life of its
702 own. All the accumulated features and bug fixes of the i4b
703 version have now been merged back into the base system's
704 version now. The only user-visible change resulting from this
705 is that i4b's sppp(4) interfaces are to be managed with
706 spppcontrol(8) again, since ispppcontrol(8) has been retired
707 as well. (There has never been rc file support for
708 ispppcontrol in -current, but only in -stable. That will be
709 reverted by the time the changes are MFCed.)
712 The fdc(4) driver has been updated and now automatically
713 recognizes media in `standard' formats (like 1440 KB and
714 720 KB for a 3.5" high-density drive) when accessing the
715 default device node (e. g. /dev/fd0). The old variety of
716 floppy device nodes /dev/fd*.* is no longer present by
717 default, devices can be created (in DEVFS) on demand. They
718 will need to be customized then for `odd' densities using
722 The bugs in procfs' debugging support code have been fixed,
723 and truss(1) now works again.
726 Daily security checks have been split out to use the periodic(8)
727 scripts. Some change in configuration may be necessary. Please
729 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
733 sos added VCD/SVCD support to ata driver and that needs the
734 kernel and burncd to be in sync.
737 The procfs pseudo-filesystem has now been converted to use the
738 pseudofs framework. If you have 'options PROCFS' in your
739 kernel config, you'll need to add 'options PSEUDOFS' if it's
742 This change temporarily breaks truss(1); use ktrace(1) instead
743 until the issue has been resolved.
746 A security hole in OpenSSH involving `UseLogin yes' has been
750 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
751 after this date. You need to do this only once.
754 Most of the awk issues have been resolved. Some rough
755 edges may be left, but for the most part things should be
756 back to "normal." For CURRENT's usual definition of "normal."
759 Awk has been upgraded to the one true awk from bell labs. Expect
760 choppy waves in the upgrade process.
763 The asr driver problem has been resolved.
766 Due to changes in other parts of the system, the asr driver
767 now causes the system to panic on boot. Do not use it pending
768 correction. Comment it out of any kernel config file that you
769 try to use from this date forward.
772 When crossbuilding, use TARGET=xxx where you used to use
773 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
774 unless you are changing both of them. To cross build pc98 on
775 an alpha, for example, you need to set TARGET=pc98 and
779 The kernel interface that burncd depends on has changed.
780 You must recompile both the kernel and userland applications
784 When crossbuilding, please set TARGET_ARCH rather than
785 MACHINE_ARCH to indicate the target. In the future, one will
786 set TARGET_MACHINE where you set MACHINE now. At the moment,
787 setting MACHINE alone for same MACHINE_ARCH machines works
788 (eg, you can build pc98 on an i386 machine and vice versa).
791 Some weird problems result from using ACPI on some machines.
792 To disable ACPI you can add
793 hint.acpi.0.disabled="1"
794 to /boot/loader.conf (or by putting set X=Y at the boot
797 Alternatively, you can remove it from /boot/kernel/acpi.ko
798 or use the MODULES_OVERRIDE function in your kernel config
799 file and not list acpi in that list.
802 The buildworld has been fixed. You may need to install
803 the 4.x compatibility libraries for some old binaries
804 to work. Add COMPAT4X=true to your /etc/make.conf to
805 get them installed on every installworld, or execute the
806 following to get them installed only once:
807 cd src/lib/compat/compat4x.<arch>
809 You will see ``__stdoutp undefined'' until you do this.
812 There's a bug in the world build process. The cross-tools
813 are build with the NEW headers, but the OLD libc.a. This
814 leads to all kinds of problems with the new libc. A temporary
816 CFLAGS="-O -pipe -D_OLD_STDIO"
817 before building world when upgrading from 4.x to current. This
818 can be removed afterwards.
820 A proper fix to the buildworld target is needed.
823 Peter has committed his new kthread nfs client/server code.
824 NFS may be unstable after this date.
827 KSE has hit the tree. Lots of things are now different in
828 the kernel. While a few problems were introduced in the
829 initial commit, most of the major ones have been found and
833 In OLDCARD, CardBus bridges appear to be stable. The work
834 arounds described in the 20010604 entry are now no longer
835 necessary and will be ignored. Most insert/remove problems
836 have been rectified around this date.
839 named now runs as user bind and group bind rather than as
840 root. If named_enable is set to YES in /etc/rc.conf, ensure
841 that user bind is available in /etc/passwd (using vipw(8))
842 and that group bind is available in /etc/group. Also make
843 sure that user or group bind has read (and not write)
844 permission for your name server configuration and that it
845 has read and write permission for your slave zone files and
848 If you wish to continue to run named as root (a less secure
849 alternative), add a line to /etc/rc.conf saying
854 The PAM libraries have had an API upgrade that is beyond
855 the ability of the shared library major number to handle.
856 It is manifested by PAM-using ports dumping core. The
857 solution is to rebuild those ports.
860 The kernel compile module has moved from src/sys/compile/FOO
861 to src/sys/${MACHINE}/compile/FOO.
864 The pccard modem issue from 20010613 has been corrected.
865 OLDCARD support is still a little weak in -current. slot 1 is
866 known not to work on some TI based cardbus bridges. Some
867 cardbus bridges do not properly detect insert/removal events.
868 IRQ configuration needs more safety belts.
871 Softupdates problems have been corrected.
874 Peter ripped out the linkerset support. You must, as always,
875 rerun config after you cvsup if you are using the traditional
876 kernel building methods.
879 pccard modems may not work with current after 20010604 date. Some
880 do, others result in panics. *MAKE*SURE* that you update your
881 config and /etc/rc.conf ala the 20010604 entry, or you will have
882 problems (this issue will be fixed, it just hasn't been yet).
885 SOFTUPDATES seem to be broken since the middle of May or so. Do not
886 use them in current. You can disable softupdates on all mounted
887 partitions, or remove SOFTUPDATES the kernel config file.
890 After Peter's commits to the hints code, people have been noticing
891 that certain devices are attached (or try to) twice. This is due
892 to having both static hints as well as a /boot/device.hints. To
893 work around this issue, please use only one or the other mechanism
894 until this bug is fixed.
896 Please note that a feature of config is that if you have config
897 file FOO and FOO.hints, it automatically adds FOO.hints to the
898 hints.c file, whether you want it to or not.
901 Locale names have changed to match other systems better.
904 pccard support for pci cards has been committed. You must change
905 your /etc/pccard.conf irq lines. It must match the irq used by
906 pcic device. Interrupt storms may result if you fail to do this.
907 Interrupt storms look a lot like a hang.
909 You must also install a new pccardd, otherwise you will get an
910 interrupt storm at card reset time (just after it tells you what
913 pccardd_flags="-I" is necessary for the time being. It tells pccardd
914 not to ask the kernel if the interrupt is really free or not before
915 using it. You can either change the /etc/pccard.conf irq lines to
916 match pcic, or add "-i X" to the pccardd_flags.
919 INSTALL=install -C is being deprecated. If you want to do this,
920 use COPY=-C instead. The former method will be supported for only
921 a limited time. If you see
923 install: warning: the -d and -C options may not be specified together
925 in your makeworld, then you need to migrate towards using
929 It appears that vm is now stable enough to use again. However,
930 there may be other problems, so caution is still urged. alpha
931 definitely is in bad shape.
934 Minor repo damage has happened. This may cause problems
935 with cvsup of ports. If you get errors, please see
936 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
937 at the bottom for details on a workaround. The error message
939 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
942 Vm and/or swapping are busted on -current. Please be patient.
945 pccard has had much reorganizational work done to it over
946 the past few days. Everything should still work, but if
947 not, please contact imp@freebsd.org.
950 ata ioctl changed. Make sure to recompile both kernel and
951 userland at the same time.
954 New ncurses imported.
957 DEVFS is now opt out, not opt in. Barring major problems, this
958 will be the only way to go starting July 1.
961 OpenSSH has been updated to 2.9. Some defaults are different,
962 including RhostsRSAAuthentication, which changes from yes to no.
965 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
968 Building perl was broken at 02:25:25 PDT.
971 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
972 go back in the water.
975 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
976 this date, but before the correction date.
979 old fsck and new kernel interactions appear to have been fixed.
982 fsck and the kernel were changed to handle some optimizations
983 to directory layout. This breaks backward compatibility.
984 Update only if you understand that you must not use the old
985 fsck with the new kernel ever.
988 fsck has changed the meaning of the pass column in /etc/fstab.
989 Please see the cvs commit to fsck.8 or the fsck.8 man page for
990 details. It is unclear if changes to /etc/fstab are necessary.
993 portmap had changed name to rpcbind for maximum POLA in your
994 current world. /etc/hosts.{allow,deny} needs changes. nfs and
995 other rpc based programs that rely on portmapper will not work
996 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
999 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1000 and ATA_ENABLE_TAGS are no longer kernel options. They have
1001 been replaced by tunables. See ata.4 for details.
1004 The fxp driver was converted to use miibus. If you compile
1005 fxp into your kernel statically, you will need to add miibus.
1008 The wi device now defaults to BSS (infrastructure) mode
1012 /dev/urandom should be a symbolic link to /dev/random now.
1013 Users of current not using DEVFS need to run MAKEDEV std.
1014 ssh might not work if you don't.
1017 The ed driver has been updated. It now allows mii attachments,
1018 which means that you must include the miibus in your kernel if
1019 you use the ed driver.
1022 The problems with libc have been corrected. It is now mostly
1023 safe to go back into the water.
1026 The size of FILE was changed. This breaks upgrading. If
1027 you must upgrade, be prepared for pain. It also breaks almost
1028 all binaries that you've compiled on -current. You are warned
1029 that before upgrading would be a good time to do a level 0
1030 dump of your system. No, really, I mean it this time.
1032 To get to the new system, you'll need to use the following
1033 workaround. Hopefully this can be sorted out so that we
1034 don't have to move this to the updating section.
1036 To get around the installworld problem, do:
1037 # cd /usr/src/usr.bin/sed
1041 If that doesn't work, then try:
1042 # make -k installworld
1046 DEVFS is now the default. If you use vinum, make sure that you
1047 do not include devfs in your kernel as problems result.
1050 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1051 Remove them from your config.
1054 ****************************** WARNING ******************************
1055 buildkernel has been changed slightly
1056 ****************************** WARNING ******************************
1057 KERNCONF replaces the variable KERNEL for buildkernel. You
1058 should update your scripts and make.conf accordingly.
1061 config has changed to allow DEV_FOO as a replacement for NFOO.
1062 This requires a new config to build correctly.
1065 The kernel option I386_CPU is now mutually exclusive with the
1066 other cpu types. If you have an i386 system, be sure that it
1067 only had this line. Remove it for all other configurations.
1070 Changes to the kernel require it and burncd be in sync.
1073 Everyone who has hw.sndunit set to something in
1074 /etc/sysctl.conf, it is now hw.snd.unit.
1077 ex and vi were broken by some changes to sys/queue.h. If you
1078 have a bad vi, you will see make buildworld fail with a core
1079 dump while building termcap. You can work around this problem
1080 by adding -k to your make buildworld. This will cause the
1081 build to complete and install a new vi. Once that's done, you
1082 can rebuild again without the -k to pick up anything that
1083 might have been ignored by the -k option.
1085 Others have suggested that you can just rebuild libc if your
1086 vi/ex is dynamically linked, but I've not received any reports
1090 There have been some changes to libcrypt in -current. The
1091 libscrypt/libdescrypt symlink silliness is gone and the installed
1092 libcrypt is fully functional. Be aware of this.
1095 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1096 now require the addition of flag 0x80000 to their config line
1097 in pccard.conf(5). This flag is not optional. These Linksys
1098 cards will not be recognized without it.
1101 Important new FreeBSD-version stuff: PAM support has been worked
1102 in, partially from the "Unix" OpenSSH version. This requires
1103 adding the following in pam.conf:
1105 sshd auth sufficient pam_skey.so
1106 sshd auth required pam_unix.so try_first_pass
1107 sshd session required pam_permit.so
1110 cvs updated to 1.11.
1113 The random device needs more entropy, so you need to make sure
1114 that you've run mergemaster to get a /etc/rc which will seed
1115 /dev/random. If you don't and the system hangs after ldconfig,
1116 then banging on the keyboard randomly until it unhangs is one
1120 ****************************** WARNING ******************************
1121 Sendmail has been updated.
1122 ****************************** WARNING ******************************
1123 o mail.local(8) is no longer installed as a set-user-id binary.
1124 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1126 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1128 o Now using sendmail's version of vacation(1).
1129 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1130 in /usr/share/sendmail/cf.
1131 o sendmail.cw changed to local-host-names
1133 More details can be found at
1134 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1137 The ports tree's new layout is in place. Be sure to update
1138 your entire ports tree, or you will have problems.
1141 The perl build procedure no longer installs miniperl, nor uses
1142 the installed miniperl. It is recommended that you delete
1146 This weekend the ports tree will be updated to a new layout.
1147 It will be in an inconsistent state until noted in the UPDATING
1148 file, or with asami-san's message to the relevant mailing
1149 lists. With this new layout, you'll need to update the whole
1150 tree for anything to work.
1153 There was a change in the passwd format. Need more information.
1156 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1157 place. Please update boot loader (not the boot blocks) at the
1158 same time as your kernel.
1161 The new pmtimer device is necessary for laptops. Failure to
1162 include the device will cause suspended laptops losing time
1163 when they resume. Include
1165 in your config file and
1166 hint.pmtimer.0.at="isa"
1167 to your /boot/device.hints file.
1170 The random device has been turned into a (pseudo-)device,
1171 rather than an option. The supplied kernel config files have
1172 been updated. You will need to do something similar in your
1173 own kernel config file.
1178 If you prefer to load the loadable module, you need to do
1182 The random device module has been renamed from randomdev.ko to
1183 random.ko. You will need to edit your /boot/loader.conf to
1184 reflect this if you load this module at boot time.
1185 The line should read:
1189 The SMPNG commit has happened. It should work, but if it
1190 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1191 to be a variety of minor issues. Please see 20000905 to make
1192 sure you don't have model loading problems which might at
1193 first blush appear related to SMP.
1196 nsswitch has been imported from NetBSD. Among other things,
1197 this means that /etc/host.conf is no longer used. See
1198 nsswitch.conf(5) instead. Note that at boot time rc.network
1199 will attempt to produce a new nsswitch.conf file for you if you
1200 don't have one, and you have host.conf.
1203 The ucred structure changed size. This breaks the interface
1204 that mountd uses. Trying to use an older mountd with a newer
1205 kernel guarantees a panic. This means that you need to use
1206 kernels newer than today only with matching mountd, but you
1207 needed to do that anyway with the boot loader changes.
1210 The boot loader has been updated. The new default kernel is
1211 now /boot/kernel/kernel.ko. The new default module location
1214 You *MUST* upgrade your boot loader and kernel at the same time.
1215 The easiest way to do this is to do the buildworld/buildkernel/
1216 installkernel/installworld dance.
1218 Furthermore, you are urged to delete your old /modules directory
1219 before booting the new kernel, since kldload will find stale
1220 modules in that directory instead of finding them in the correct
1221 path, /boot/kernel. The most common complaint that this cures
1222 is that the linux module crashes your machine after the update.
1224 if [ ! -d /boot/kernel.old ]; then
1225 mv /modules.old /boot/kernel.old
1226 chflags noschg /kernel.old
1227 mv /kernel.old /boot/kernel.old/kernel.ko
1228 chflags schg /boot/kernel.old/kernel.ko
1232 A new issue with the sendmail upgrade has come to light.
1233 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1234 incorrectly install the default aliases in /etc/mail rather than
1235 move the old one from /etc. So you'll need to manually move the
1236 file, create a symbolic link, remove the old /etc/aliases.db and
1237 run newaliases. For safety sake, you should stop sendmail
1238 while doing this and run the upgrade when locally sourced email
1239 is not likely to be generated.
1242 /boot/device.hints is now required for installkernel to
1243 succeed. You should copy GENERIC.hints for your architecture
1244 into /boot/device.hints. If and only if you compile hints
1245 into your kernel, then this file may be empty. Please note,
1246 if you have an empty or missing /boot/device.hints file and
1247 you neglected to compile hints into your kernel, no boot
1248 messages will appear after the boot loader tries to start the
1252 If you do NOT have ``options RANDOMDEV'' in your kernel and
1253 you DO want the random device then add randomdev_load="YES" to
1257 suidperl is now always built and installed on the system, but
1258 with permissions of 511. If you have applications that use
1259 this program, you are now required to add ENABLE_SUIDPERL=true
1260 to /etc/make.conf. If you forget to do this,
1261 chmod 4511 /usr/bin/suidperl
1262 will fix this until the next build.
1265 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1266 visible changes that may immediately affect your configuration
1268 - New default file locations from src/contrib/sendmail/cf/README
1269 - newaliases limited to root and trusted users
1270 - MSA port (587) turned on by default
1271 - New queue file naming system so can't go from 8.11 -> 8.9
1272 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1273 - FEATURE(`nullclient') is more full featured
1274 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1275 - mail.local FreeBSD-only -b option changed to -B
1276 - See src/contrib/sendmail/RELEASE_NOTES for more info
1279 suidperl (aka sperl) is no longer build by default. You must
1280 specifically define BUILD_SUIDPERL to "true" for it to be build.
1281 Furthermore, we recommend that you remove /usr/bin/sperl* and
1282 /usr/bin/suidperl files from your system unless you have a
1283 specific use for it.
1286 Networking defaults have been tightened. Anybody upgrading
1287 /etc/defaults/rc.conf needs to add the following lines to
1288 /etc/rc.conf if they want to have the same setup
1289 afterwards (unless the variables already are set, of course):
1290 # Enable network daemons for user convenience.
1292 portmap_enable="YES"
1293 sendmail_enable="YES"
1296 If you have null_load="YES" in your /boot/loader.conf, you
1297 will need to change that to nullfs_load="YES".
1300 The "installkernel" target has changed slightly. Now even if
1301 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1302 it will install the MYKERNEL file (built with the buildkernel
1303 target) as /kernel rather than /MYKERNEL. Those who have
1304 updated their /boot/loader.conf files to point to /MYKERNEL
1305 should remove that entry or perform manual rename of /kernel
1309 If you use CVSUP or CTM to get CVS trees, AND you used to get
1310 the old crypto files from internat.freebsd.org AND you check
1311 out files from the CVS tree with the cvs command, please read
1312 http://people.freebsd.org/~imp/internat.txt
1313 for details on potential problems that you might have and how
1316 If you are merely a mirror, or don't answer yes to each of the
1317 clauses above, you needn't worry.
1320 /etc/security has been updated to print the inode number of
1321 setuid programs that have changed. You will see a large spike
1322 in the number of changed programs the first time when you run
1323 mergemaster to get a new /etc/security.
1326 /dev/random now has good entropy collection (from the keyboard
1327 and sysmouse drivers). Please ensure that either `options
1328 RANDOMDEV' is present in your kernel config file or that
1329 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1330 not have the /dev/random driver, OpenSSL (and consequently
1331 lots of crypto tools (like SSH)) will fail with strange
1332 errors. (see below, 20000624).
1334 FreeBSD-current is safe again to run Crypto.
1337 phk made the malloc default options AJ. This may slow things
1338 down and uncover other latent bugs in the code. If you need to
1339 run at full speed, you can disable this by doing the following:
1340 ln -s aj /etc/malloc.conf
1343 libftpio's version was accidentally bumped a few days ago. This
1344 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1345 before doing your next buildworld/installworld pair. It certainly
1346 won't hurt to remove it before the update procedure. It will
1347 break fetch until a new one is built, but ftp can be used in the
1351 The crypto packages have changed for the cvsup. This has been done
1352 in a backward compatible way, but the old packages will go away at
1353 some point in the future. Look at /usr/share/examples/cvsup for
1357 With the new sys/modules/sound/drivers/*, you will need to
1358 set SYSDIR until you do an installworld after July 7th.
1361 rc.shutdown and rc will now call the rc.d scripts with start
1362 or stop. This may cause some harmless warnings from older
1363 rc.d scripts that haven't been updated.
1366 The libfetch based version of fetch has gone into the tree.
1367 Minor problems may result on some of the less popular sites,
1368 which should be reported to des@freebsd.org.
1371 From approximately this date forward, one must have the crypto
1372 system installed in order to build the system and kernel.
1373 While not technically strictly true, one should treat it as
1374 required and grab the crypto bits. If you are grabbing CVS
1375 trees, src-all and cvs-crypto should be treated as if they
1376 were required. You should check with the latest collections
1377 to make sure that these haven't changed.
1380 Mark Murray just committed the first parts of a cleanup of
1381 /dev/zero, et al. This is also cleaning up /dev/random.
1382 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1383 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1384 until Mark can merge in the fixes to this work in progress.
1385 openssh and openssl should not be used to generate keys from this
1386 date to the completion of the work.
1388 If you must operate at this reduced level of security, add '
1389 options RANDOMDEV' to your kernel or modload the randomdev
1390 module. You may also need to copy a new MAKEDEV to /dev and
1391 recreate the random and urandom devices.
1394 The license on the softupdates is now a standard 2 clause
1395 BSD license. You may need to remove your symbolic links
1396 that used to be required when updating.
1399 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1400 the config file update procedure.
1401 http://people.freebsd.org/~imp/config-upd.html
1402 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1403 isn't buildable. However, you can generate a LINT file:
1404 cd /sys/<ARCH>/conf && make LINT
1407 Binutils 2.10 have hit the tree, or will shortly. As soon
1408 as they do, the problem noted in 20000522 will be resolved and
1409 that workaround will no longer be required.
1412 phk removed the compatibility creation of wd devices in the
1413 ad driver. If you haven't done so already, you must update
1414 your fstab, etc to use the ad devices instead of the wd
1417 In addition, you'll need to update your boot blocks to a
1418 more modern version, if you haven't already done so. Modern
1419 here means 4.0 release or newer (although older releases
1423 Peter took an axe to config(8). Be sure that you read his mail
1424 on the topic before even thinking about updating. You will
1425 need to create a /boot/device.hints or add a hints directive
1426 to your config file to compile them in statically. The format
1427 of the config file has changed as well. Please see GENERIC or
1428 NEWCARD for examples of the new format.
1430 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1431 says that it has been fixed, assume that must use the hints mechanism
1432 in the loader if you need to use a machine with very old ISA cards
1436 A new set of binutils went into the tree today. Anybody
1437 building a kernel after this point is advised that they need
1438 to rebuild their binutils (or better yet do a
1439 buildworld/installworld) before building a new kernel.
1441 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1442 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1443 is recommended that you don't set this option until the problem
1447 The ethernet drivers were all updated to clean up the BPF handling.
1450 The problems with boot blocks on the alphas have been corrected.
1451 This will require some care in updating alphas. A new libstand
1452 is requires for the boot blocks to build properly.
1455 Recompile all kld modules. Proper version dependency info
1459 Modules have been disconnected from the buildworld tree and
1460 connected to the kernel building instead.
1463 You may need to build gperf
1464 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1465 when upgrading from 4.0 -> current. The build system now uses
1466 an option only in -current.
1469 The method that we brand ELF binaries has changed to be more
1470 acceptable to the binutils maintainers. You will need to
1471 rebrand your ELF binaries that aren't native. One problem
1472 binary is the Linux ldconfig. After your make world, but
1473 before you reboot, you'll need to issue:
1474 brandelf -t Linux /compat/linux/sbin/ldconfig
1475 if you have Linux compatibility enabled on your machine.
1478 If you have really bad/marginal IDE drives, you may find they
1479 don't work well. Use pio mode instead. The easiest way to
1480 cope if you have a problem combination is to add:
1481 /sbin/sysctl hw.ata.ata_dma=0
1482 to the start of /etc/rc.conf.
1485 The ISA and PCI compatibility shims have been connected to the
1486 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1487 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1488 include the appropriate option in your kernel config. Drivers
1489 using the shims should be updated or they won't ship with
1490 5.0-RELEASE, targeted for 2001.
1493 We've entered the traditional post release dumping party.
1494 Large kernel changes are being committed and are in the
1495 works. It is important to keep the systems' klds and kernel
1496 in sync as kernel interfaces and structures are changing.
1497 Before reporting kernel panics, make sure that all modules
1498 that you are loading are up to date.
1501 If you are upgrading from an older version of FreeBSD, you
1502 need to update your boot blocks as well. 'disklabel -B ad0'
1503 will do the trick. This isn't critical until you remove your
1504 wd device entries in /dev, at which point your system will not
1508 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1509 to upgrade to 4.0 from 3.x.
1515 Avoid using make -j when upgrading. From time to time in the
1516 past there have been problems using -j with buildworld and/or
1517 installworld. This is especially true when upgrading between
1518 "distant" versions (eg one that cross a major release boundary
1519 or several minor releases, or when several months have passed
1520 on the -current branch).
1522 Sometimes, obscure build problems are the result of environment
1523 poisoning. This can happen because the make utility reads its
1524 environment when searching for values for global variables.
1525 To run your build attempts in an "environmental clean room",
1526 prefix all make commands with 'env -i '. See the env(1) manual
1527 page for more details.
1531 If you are updating from a prior version of FreeBSD (even one just
1532 a few days old), you should follow this procedure. With a
1533 /usr/obj tree with a fresh buildworld,
1534 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1535 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1537 To just build a kernel when you know that it won't mess you up
1538 --------------------------------------------------------------
1539 This assumes you are already running a 5.X system. Replace
1540 ${arch} with the architecture of your machine (e.g. "i386",
1541 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1543 cd src/sys/${arch}/conf
1544 config KERNEL_NAME_HERE
1545 cd ../compile/KERNEL_NAME_HERE
1550 If this fails, go to the "To build a kernel" section.
1552 To rebuild everything and install it on the current system.
1553 -----------------------------------------------------------
1554 # Note: sometimes if you are running current you gotta do more than
1555 # is listed here if you are upgrading from a really old current.
1557 <make sure you have good level 0 dumps>
1558 <maybe fix /etc/fstab> [7]
1560 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1561 make installkernel KERNCONF=YOUR_KERNEL_HERE
1563 <reboot in single user> [3]
1564 /etc/rc.d/preseedrandom [10]
1571 To cross-install current onto a separate partition
1572 --------------------------------------------------
1573 # In this approach we use a separate partition to hold
1574 # current's root, 'usr', and 'var' directories. A partition
1575 # holding "/", "/usr" and "/var" should be about 2GB in
1578 <make sure you have good level 0 dumps>
1581 <maybe newfs current's root partition>
1582 <mount current's root partition on directory ${CURRENT_ROOT}>
1583 make installworld DESTDIR=${CURRENT_ROOT}
1584 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1585 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1586 ${CURRENT_ROOT}/boot/device.hints # as needed
1587 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1588 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1589 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1590 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1591 <reboot into current>
1592 <do a "native" rebuild/install as described in the previous section>
1593 <maybe install compatibility libraries from /usr/src/lib/compat>
1597 To upgrade in-place from 4.x-stable to current
1598 ----------------------------------------------
1599 # 5.x uses more space than 4.x. Also, the location of kernel
1600 # modules has changed. If you are installing 5.0 onto a 4.x
1601 # system, you'll need about 30MB of free disk space on your /
1602 # partition. If you have less than this, you may encounter difficult
1603 # to back out of problems with this procedure. If /tmp is on
1604 # the / partition, you may want to completely remove all its content
1605 # before upgrading, as this can be a common source of shortage of
1608 <make sure you have good level 0 dumps>
1609 <maybe fix /etc/fstab> [7]
1611 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1612 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1613 make installkernel KERNCONF=YOUR_KERNEL_HERE
1614 cd sys/boot ; make STRIP="" install [6]
1616 <reboot in single user> [3]
1617 /usr/src/etc/rc.d/preseedrandom [10]
1619 rm -rf /usr/include/g++
1624 Make sure that you've read the UPDATING file to understand the
1625 tweaks to various things you need. At this point in the life
1626 cycle of current, things change often and you are on your own
1627 to cope. The defaults can also change, so please read ALL of
1628 the UPDATING entries.
1630 Also, if you are tracking -current, you must be subscribed to
1631 freebsd-current@freebsd.org. Make sure that before you update
1632 your sources that you have read and understood all the recent
1633 messages there. If in doubt, please track -stable which has
1634 much fewer pitfalls.
1636 [1] If you have third party modules, such as vmware, you
1637 should disable them at this point so they don't crash your
1640 [2] If you have legacy ISA devices, you may need to create
1641 your own device.hints to reflect your unique hardware
1644 [3] From the bootblocks, boot -s, and then do
1649 adjkerntz -i # if CMOS is wall time
1650 Also, when doing a major release upgrade, it is required that
1651 you boot into single user mode to do the installworld.
1652 For the 4.x -> 5.0 upgrade, you will also see many messages about
1653 needing to recompile your userland. These are harmless and can
1654 be ignored while you proceed to the next step.
1656 [4] Note: This step is non-optional. Failure to do this step
1657 can result in a significant reduction in the functionality of the
1658 system. Attempting to do it by hand is not recommended and those
1659 that pursue this avenue should read this file carefully, as well
1660 as the archives of freebsd-current and freebsd-hackers mailing lists
1661 for potential gotchas.
1663 [5] Usually this step is a noop. However, from time to time
1664 you may need to do this if you get unknown user in the following
1665 step. It never hurts to do it all the time. You may need to
1666 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1667 install) after the buildworld before this step if you last updated
1668 from current before 20020224 or from -stable before 20020408.
1670 [6] 4.x boot loader can be used to boot a 5.x system, however
1671 it is difficult to do that at best. If you wish to try, then
1672 you should interrupt the boot and at the ok prompt type:
1674 ok boot /boot/kernel/kernel
1675 If this fails to work, you must install a new boot loader as
1678 [7] Before you upgrade, please make sure that you are not using
1679 compatibility slices. These are device names of the form, on i386
1680 and other architectures that use MBR slicing, /dev/ad0a without the
1681 actual slice name. Chances are excellent that these will break.
1682 You generally must update these entries to use the post FreeBSD
1683 2.x form of /dev/ad0s1a.
1685 [8] In order to have a kernel that can run the 4.x binaries
1686 needed to do an installworld, you must include the COMPAT_FREEBSD4
1687 option in your kernel. Failure to do so may leave you with a system
1688 that is hard to boot to recover.
1690 [9] When checking out sources, you must include the -P flag to have
1691 cvs prune empty directories. Also, if CPUTYPE is defined in your
1692 /etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1693 operator, so that buildworld can override the CPUTYPE if it needs to.
1694 In case you would like to avoid installing new packages of everything,
1695 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1696 compatibility libraries are build which should allow you to continue
1697 using your existing software for a while.
1699 [10] In order to create temporary files, /dev/random must be
1700 initialized by feeding data into it. /etc/rc.d/preseedrandom
1704 This file contains a list, in reverse chronological order, of major
1705 breakages in tracking -current. Not all things will be listed here,
1706 and it only starts on March 15, 2000. Updating files can found in
1707 previous releases if your system is older than this.
1709 Copyright information:
1711 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1713 Redistribution, publication, translation and use, with or without
1714 modification, in full or in part, in any form or format of this
1715 document are permitted without further permission from the author.
1717 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1718 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1719 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1720 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1721 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1722 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1723 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1724 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1725 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1726 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1727 POSSIBILITY OF SUCH DAMAGE.
1729 If you find this document useful, and you want to, you may buy the
1732 Contact Warner Losh if you have any questions about your use of