1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
9 portupgrade. Important recent entries: 20040724 (default X changes).
11 NOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
12 FreeBSD 5.x has many debugging features turned on, in
13 both the kernel and userland. These features attempt to detect
14 incorrect use of system primitives, and encourage loud failure
15 through extra sanity checking and fail stop semantics. They
16 also substantially impact system performance. If you want to
17 do performance measurement, benchmarking, and optimization,
18 you'll want to turn them off. This includes various WITNESS-
19 related kernel options, INVARIANTS, malloc debugging flags
20 in userland, and various verbose features in the kernel. Many
21 developers choose to disable these features on build machines
22 to maximize performance.
25 System compiler has been upgraded to GCC 3.4.2-pre. As with any major
26 compiler upgrade, there are several issues to be aware of. GCC 3.4.x
27 has broken C++ ABI compatibility with previous releases yet again
28 and users will have to rebuild all their C++ programs with the new
29 compiler. A new unit-at-a-time optimization mode, which is default
30 in this compiler release, is more aggressive in removing unused
31 static symbols. This is the likely cause of 'make buildworld'
32 breakages with non-default CFLAGS where optimization level is set
36 The size of 'struct ifnet' has changed due to the addition of
37 the IFF_NEEDSGIANT flag (and what it implies). All kernel
38 modules implementing network interfaces must be recompiled as
42 The sound device drivers are renamed. `sound' is always required,
43 while `snd_*' should be configured accordingly to your hardware.
44 Refer to NOTES for the detail of the drivers.
47 __FreeBSD_version bumped to 502122.
50 The console initialization on Alpha has been reworked and is now
51 identical to other platforms. This means that the hardcoding of
52 the serial console and the debug port has been removed. As such,
53 hints are now required for the sio(4) driver to become a console
54 or debug port. The NO_SIO option has been decommissioned because
58 A revamp of the debugging code in the kernel with some visible
59 changes beyond just the debugging experience:
60 o The DDB option is now specific to the DDB debugger backend
61 and should not be used any more for conditional compilation
62 of debugging code for when debugging is enabled. Use the KDB
64 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
65 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
66 respectively. This is in line with the first bullet.
67 o The remote GDB support has been untangled from DDB and needs
68 to be enabled separately now. Use the GDB option for this.
69 o The GDB_REMOTE_CHAT option has been removed. Support for this
70 homegrown feature is discontinued. The GDB remote protocol
71 supports console output and it makes sense to use that.
72 o The DDB_NOKLDSYM option has been removed. The DDB debugger
73 now supports both direct symbol table lookups as well as KLD
74 symbol lookups through the linker.
77 Bluetooth code has been marked as non-i386 specific.
78 __FreeBSD_version has been bumped to 502121 to mark this change.
81 The native preemption has been added to the kernel scheduler.
82 There is some report that the ULE scheduler was broken in some
83 machines and we encourage users using the ULE scheduler either
84 stick with a known good kernel, or temporarily switch to the 4BSD
85 scheduler as a workaround.
88 The netgraph ABI version number has been incremented to indicate
89 an incompatible change in the ABI. Old netgraph nodes will refuse
90 to attach until recompiled. Netgraph now uses mbuf tags to move
91 metadata and this commit removes its home-grown metadata facility.
92 Nodes should just recompile, unless they use metadata, in which
93 case the changes are simple; the file ng_ksocket.c serves as an
94 example of such changes.
96 This also broke i4b, although the compile problem has been papered
100 ACPI has been updated to disable known-bad BIOS revisions. A message
101 will be printed on the console indicating that ACPI has been disabled
102 automatically and that the user should use a newer BIOS, if possible.
103 If you think ACPI does work on your system and want to override
104 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
108 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
109 separated now. It uses the newly created "_pflogd" user/group
110 combination. If you plan to use pflogd(8) make sure to run
111 mergemaster -p or install the "_pflogd" user and group manually.
114 Network interface cloning has been overhauled. This change will
115 require a recompile of modules using cloning and modification of
116 external ones to the new API. __FreeBSD_version has been bumped
117 to 502119 to mark this change. Additionally, users creating
118 stf(4) interfaces via "ifconfig stf" will need to update their
119 scripts as this will create an interface named "stf" instead of
120 "stf0" and ifconfig will not print "stf0" to stdout.
123 On 20040524, the /etc/rc.d/nsswitch script was modified to
124 automatically create /etc/nsswitch.conf on startup if it did
125 not already exist. Unfortunately, an error in the man page
126 was carried over to the script, resulting in incorrect
127 nsswitch settings. The simplest remedy is to remove both
128 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
129 during the next reboot.
132 The return value of sema_timedwait(9) has been changed to
133 make it consistent with cv_timedwait(9). Be sure to recompile
134 the ips module and any third-party modules which call
138 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
139 Make sure to recompile modules and any userland that makes use of
140 sizeof(struct ifnet). In order to get the altq headers in place
141 please recompile and reinstall world.
144 Splitting kern_thread.c into 2 files (adding kern_kse.c)
145 requires that you re-run config after updating your tree.
148 The MIDI drivers have been removed. Until the new module-friendly
149 ones are merged, remove or comment out midi and seq from your
150 kernel configuration.
153 Due to a new option in ipfw (versrcreach) the ipfw(8) command
154 needs to be recompiled. Normal accept/reject rules without
155 options are not affected but those with options may break until
156 ipfw(8) is recompiled.
159 Due to changes in the callout ABI, kernels compiled after this
160 date may be incompatible with kernel modules compiled prior to
164 The PCI bus power state stuff has been turned on. If this causes
165 problems for your system, please disable it using the tunable
166 hw.pci.do_powerstate=0.
169 The bulk of the pci problems have been fixed, although the floppy
170 drive is still broken.
173 A substantial update to the pci bus resource and power management
174 have been committed. Expect a bumpy ride for a few days until
175 the unanticipated problems have been resolved.
178 Due to changes in the the Yarrow initialization process,
179 /dev/random needs to be fed before operations requiring
180 temp files can succeed in single user mode. This includes
181 running "make installworld". /dev/random may be fed by running
182 "/etc/rc.d/initrandom start" or with 20040415 source by running
183 "/etc/rc.d/preseedrandom".
186 The debug.mpsafenet tunable controls whether the kernel Giant
187 lock is held across the lower levels of the network stack, and
188 by default is turned off. In the few days following 20040322,
189 the behavior of debug.mpsafenet will change such that this
190 tunable controls Giant over all levels of the network stack.
191 If you are currently setting debug.mpsafenet to 1, you should
192 set it back to 0 (the default) again during the change-over.
193 An additional note will be added to UPDATING when sufficient
194 locking is merged to permit this to take place.
197 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
198 64-bits. This is a very major incompatible change, so people
199 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
200 detailed instructions on how to make this upgrade. People
201 upgrading FreeBSD on other platforms can ignore this event.
204 The packet filter (pf) is now installed with the base system. Make
205 sure to run mergemaster -p before installworld to create required
206 user account ("proxy"). If you do not want to build pf with your
207 system you can use the NO_PF knob in make.conf.
208 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
209 pf system consists of the following three devices:
211 device pflog # optional
212 device pfsync # optional
215 If you are having trouble with the libc_r -> libpthread transition
216 (see the 20040130 entry), place the following lines at the top of
219 libc_r.so.5 libpthread.so.1
220 libc_r.so libpthread.so
222 This will cause all programs and libraries linked against libc_r
223 to use libpthread instead.
226 Some sshd configuration defaults have changed: protocol version 1
227 is no longer enabled by default, and password authentication is
228 disabled by default if PAM is enabled (which it is by default).
229 OpenSSH clients should not be affected by this; other clients may
230 have to be reconfigured, upgraded or replaced.
233 The ABIs defined in <resolv.h> and <netdb.h> have been updated
234 to support improved reentrancy. Multi-threaded programs that
235 reference the "_res" or "h_errno" symbols may experience some
236 problems if they are not recompiled. Single-threaded programs
237 should remain unaffected.
240 routed has been updated in the base system from the vendor
241 sources, routed v2.27, from rhyolite.com. This change means that
242 for users who use RIP's MD5 authentication feature, FreeBSD
243 -CURRENT's routed is now incompatible with previous versions
244 of FreeBSD; however it is now compatible with implementations
245 from Sun, Cisco and other vendors.
248 The tcpcb structure has changed and makes a recompile of libkvm
249 and related userland network utilities necessary.
252 The cdevsw structure has changed in two externally visible ways.
253 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
254 Second, the d_version field must be filled in with D_VERSION.
255 Drivers outside the tree will need to be updated.
258 The /etc/rc.d/ttys script has been removed. It is no longer
259 necessary since devfs has been mandatory for some time.
262 libkse has been renamed back to libpthread and is now the
263 default threads library. The gcc -pthread option has also
264 been changed to link to libpthread instead of libc_r. For
265 alpha and sparc64 machines, libkse is not renamed and links
266 are installed so that libpthread points to libc_r. Until
267 the ports system is updated to handle this change, it is
268 recommended that folks install an /etc/libmap.conf(5) that
269 maps libc_r to libpthread. If you have any binaries or
270 libraries linked to libkse, then it is also recommended
271 that you map libkse to libpthread. Anyone that is using
272 nvidia supplied drivers and libraries should use a libmap.conf
273 that maps libpthread to libc_r since their drivers/libraries
274 do not work with libpthread.
277 ULE has entered into its probationary period as the default scheduler
278 in GENERIC. For the average user, interactivity is reported to be
279 better in many cases. On SMP machines ULE will be able to make more
280 efficient use of the available parallel resources. If you are not
281 running it now, please switch over, replacing the kernel option
282 SCHED_4BSD with SCHED_ULE.
285 Move LongRun support out of identcpu.c, where it hardly
286 belongs, into its own file and make it opt-in, not mandatory,
287 depending on CPU_ENABLE_LONGRUN config(8) option.
290 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
291 if the login process is unable to successfully set the
292 process credentials to include all groups defined for the
293 user. The current kernel limit is 16 groups; administrators
294 may wish to check that users do not have over 16 groups
295 defined, or they will be unable to log in.
298 The ACPI module has been reactivated. It is no longer required
299 to compile ACPI support into kernels statically.
302 The statfs structure has been updated with 64-bit fields to
303 allow accurate reporting of multi-terabyte filesystem
304 sizes. You should build world, then build and boot the new kernel
305 BEFORE doing a `installworld' as the new kernel will know about
306 binaries using the old statfs structure, but an old kernel will
307 not know about the new system calls that support the new statfs
309 Note that the backwards compatibility is only present when the
310 kernel is configured with the COMPAT_FREEBSD4 option. Since
311 even /bin/sh will not run with a new kernel without said option
312 you're pretty much dead in the water without it. Make sure you
313 have COMPAT_FREEBSD4!
314 Running an old kernel after a `make world' will cause programs
315 such as `df' that do a statfs system call to fail with a bad
316 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
317 that cfsd (ports/security/cfs) needs to be recompiled after
318 these changes are installed.
320 ****************************DANGER*******************************
322 DO NOT make installworld after the buildworld w/o building and
323 installing a new kernel FIRST. You will be unable to build a
324 new kernel otherwise on a system with new binaries and an old
328 Some netgraph string length constants have been changed. This
329 change requires the netgraph kernel modules and all netgraph
330 userland components to be in sync. Especially users who require
331 netgraph to boot need to make sure to have world and kernel in
332 sync before rebooting.
335 Hyperthreading logical CPU's are no longer probed by default
336 when using the MP Table. If ACPI is being used, then logical
337 CPUs will be probed if hyperthreading is enabled in the BIOS.
338 If ACPI is not being used and hyperthreading is enabled in the
339 BIOS, logical CPUs can be enabled by building a custom kernel
340 with the option MPTABLE_FORCE_HTT enabled.
343 The i386 APIC_IO kernel option has been replaced by
344 'device apic'. The ACPI module has also been temporarily
345 disabled, so ACPI must be statically compiled into your
346 kernel using 'device acpi' if you wish to use the ACPI driver.
349 The API and ABI of struct ifnet have been changed by removing
350 the if_name and if_unit members and replacing them with
351 if_xname, if_dname, and if_dunit. All network drivers and most
352 userland programs which include net/if_var.h must be updated
353 and recompiled. __FreeBSD_version has been bumped to 501113 to
357 Changes to the cdevsw default functions have been made to remove
358 the need to specify nullopen() and nullclose() explicitly.
359 __FreeBSD_version bumped to 501110.
362 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
363 mount_cd9660(8) need to be in sync with kernel.
366 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
367 also be explicitly configured. Previously this dependency was
368 magically handled through some cruft in net/pfil.h; but that has
369 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
370 will fail with obtuse errors in ip_fil.c.
373 Fix a bug in arplookup(), whereby a hostile party on a locally
374 attached network could exhaust kernel memory, and cause a system
375 panic, by sending a flood of spoofed ARP requests. See
376 FreeBSD-SA-03:14.arp.
379 A change to /etc/defaults/rc.conf now causes inetd to be started
380 with `-C 60' if it is not overridden in /etc/rc.conf. This
381 causes inetd to stop accepting connections from an IP address
382 that exceeds the rate of 60 connections per minute.
385 The following rc.d scripts have been removed and should be
386 deleted from your installation: atm2.sh atm3.sh devdb
387 localdaemons network1 network2 network3. Depending on when
388 you last updated world and used mergemaster(8) you may or
389 may not have problems during the rc boot sequence. The simplest
390 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
391 The atm2.sh atm3.sh and devdb scripts were removed some time
392 ago, so depending on when you installed -CURRENT these scripts
393 may or may not exist on your system.
396 ATAng has been committed. You need to build world as sys/ata.h
397 has changed, and userland atacontrol depends on it.
398 If you use ATA SW raids you need "device ataraid" in your
399 kernel config file, as it is no longer pulled in automatically.
402 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
403 Among other things, this changes the device enumeration to be
404 closer to Solaris. Be aware that, this can even cause the machine
405 to not boot without manual intervention before the fstab is adjusted.
408 All current USB and Firewire quirks in da(4) have been deprecated
409 and will be removed for 5.2. If this causes failure for your
410 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
411 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
412 so the quirk can be re-enabled.
415 Problems with entry 20030714 have been corrected and no known issues
416 with /rescue and -j exist for host systems after this point in time.
419 FPU-less support has been removed from FreeBSD. Chances are you won't
420 notice. 386+387 support should still work after this change, but
421 it is now a minimum requirement for the i386 port that you have real
425 Some people are having problems with changes related to /rescue.
426 If you are building -j N, you will need to define NO_RESCUE. Others
427 will need to define it if /rescue has issues with their environment.
428 People should report those issues to current@.
431 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
432 across this point. Further, it might be a good idea to remove
436 Remove deprecated locale names and transition period code
437 for them, finishing switching to the new scheme. Check your
438 LANG environment variable.
441 CCD has been changed to be a fully GEOMified class. Kernel
442 and ccdconfig(8) needs to be in sync, this is particularly
443 important to remember beforehand if your source tree is on
444 a ccd device. Consider making a copy of the old ccdconfig
445 into /boot/kernel.good or wherever you keep your backup
449 There was a small window in which sed(1) was broken. If you
450 happen to have sed(1) installed during that window, which is
451 evidenced by an inability to build world with the failure
452 given below, you need to manually build and install sed(1)
453 (and only sed(1)) before doing anything else. This is a one-
454 time snafu. Typical failure mode:
456 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
457 targmatch.h:7:1: null character(s) ignored
458 targmatch.h:12:1: null character(s) ignored
459 targmatch.h:16:1: null character(s) ignored
462 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
463 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
464 usr.bin/sed/process.c).
467 Kerberos 5 (Heimdal) is now built by default. Setting
468 MAKE_KERBEROS5 no longer has any effect. If you do NOT
469 want the "base" Kerberos 5, you need to set NO_KERBEROS.
472 groff has been updated. If you try to do a buildworld and
473 get an infinite loop in troff, update to May 4th or newer. If you
474 have a newer kernel than userland, you may need to set the OSRELDATE
475 to 500110 in your environment before starting a buildworld.
478 The old rc system has been removed. Please report any problems
479 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
480 Your personal versions of these files will not be removed, so you can
481 continue to use them. However, you should take great care when updating,
482 especially when using mergemaster, since the compatibility code that
483 utilizes these old scripts has also been removed.
486 A bug has been fixed in /dev/devctl which would cause devd
487 to hang on boot, were it not for a workaround in devd. The
488 work around in devd will be removed around 20030507. You
489 have until then to upgrade your kernel before updating
490 userland. In general, you should have a userland and
491 kernel that's in sync with each other. However, given the
492 effects of this bug (hang on boot when starting devd), some
496 Alphas with libc from between 20030312 and 20030329 exhibit
497 floating point exceptions (FPEs), most notably in awk(1)
498 while upgrading the system through a buildworld.
500 So, to successfully upgrade your Alpha, you must either
501 downgrade your libc.so to a pre-20030312 version, or update
502 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
503 to CFLAGS, then forcibly rebuild and install libc:
505 cd /usr/src/lib/libc && \
506 make cleandir && make obj && \
507 make -DNOMAN -DNOPROFILE all && \
508 make -DNOMAN -DNOPROFILE install
511 sendmail 8.12.7 has been imported. It has one important
512 change for IPv6 users. The default submit.mc now uses
513 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
514 used to connect to the MTA. Users on IPv6-only machines
515 will need to edit /etc/mail/submit.mc appropriately.
518 NODEVFS option has been removed and DEVFS thereby made standard.
519 This makes all references to MAKEDEV obsolete, and they should
520 be removed when convenient.
523 The name of the device for the ofw console has changed, sparc64 users
524 must run mergemaster to update their installed /etc/ttys.
527 The scheduler framework has grown a second scheduler and consequently
528 you must specify one and only one scheduler in your kernel config.
529 The cvs config files have been updated to use the old scheduler
530 which may be selected via 'options SCHED_4BSD'. If you would like
531 to try the new, much more experimental, scheduler please try
532 'options SCHED_ULE' and contribute to the arch@ discussion.
535 A new version of the wi driver has been imported into the tree.
536 One now must have device wlan in the config file for it to operate
539 In addition, there have been some changes to how wi devices are
540 configured for point to point links to bring it more in line
541 with the former way of doing things, as well as compatibility
545 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
546 used an incompatible form of ABI for returning structures and unions
547 which FreeBSD's GCC maintainers were not aware of relative to previous
548 versions of FreeBSD. We have gone back to the ABI for now, and any
549 code compiled which is required to interoperate with other code (not
550 built at the same time) returning structs or unions should be
554 A name change in /etc/netconfig has been reverted to stay
555 compatible with suns TIRPC and also with NetBSD. You need
556 to run mergemaster after make world. A new libc does still work
557 with an outdated /etc/netconfig for some time, but you'll get
558 a warning. This warning will be removed in 20030301.
561 The recent binutils upgrade marks a kernel flag day on
562 sparc64: modules built with the old binutils will not work
563 with new kernels and vice versa. Mismatches will result in
564 panics. Make sure your kernel and modules are in sync.
567 The value of IPPROTO_DIVERT has changed. Make sure to keep
568 your kernel, netstat, natd and any third-party DIVERT
572 Old, compatibility slices have been removed in GEOM kernels.
573 This means that you will have to update your /etc/fstab to
574 not use disk devices of the form /dev/ad0a. Instead, you
575 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
576 partition really is on. The old device names have gone
577 away, so if you use them anywhere else, you must also adjust
578 those uses. (This doesn't affect the disks formatted in
579 the ``dangerously-dedicated'' mode.)
582 Alphas with kernels from between 20020830 and 20021023 and/or
583 rtld (ld-elf.so.1) older than 20021023 may experience problems
584 with groff while doing a buildworld (kernel: "out of memory",
585 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
586 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
588 So, to successfully upgrade your Alpha, you must either
589 upgrade your kernel and rtld first (which might be a bit
590 tricky), or avoid running the bootstrapped groff during the
591 "transitional" buildworld. To avoid running groff during the
592 transitional upgrade run make buildworld with -DNOMAN,
593 -DNO_SHAREDOCS, and -DNO_LPR.
596 gcc has been upgraded to 3.2. It is not all binary compatible
597 with earlier versions of gcc for c++ programs. All c++
598 programs and libraries need to be recompiled.
600 Also, if you encounter g++ issues, rm /usr/include/g++/* before
601 doing an installworld to make sure that stale files are removed.
604 Our /etc/termcap now has all the entries from the XFree86 xterm
605 almost unchanged. This means xterm now supports color by default.
606 If you used TERM=xterm-color in the past you now should use
607 TERM=xterm. (xterm-color will lead to benign warnings).
610 A "bug" in gcc(1) that was hiding warning in system headers was
611 fixed. It's probably time to add -DNO_WERROR to your make line
615 COPY is being deprecated. The 20010530 change was reverted, as
616 it causes far more pain than was expected, and to always compare
617 before installing, please use INSTALL="install -C" again. The
618 -C option is now silently ignored when used with the -d option.
621 Problems with libc_r clients like KDE and GNOME have been resolved.
622 There are still some minor problems with some signals but the
623 system is stable enough for general use again. SMP is less so than UP
624 but each can successfully complete multiple buildworlds.
625 Libkvm needs to be recompiled due to KSE.
628 Now would be a bad time to upgrade. Something in or near the
629 KSE commit totally broke programs using libc_r like KDE and
633 The k5su utility installed as part of Kerberos 5 is no longer
634 installed with the set-user-ID bit set by default. Add
635 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
636 with the set-user-ID bit set.
639 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
640 Unfortunately our native GDB (at version 4.18) does not understand
641 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
642 generated debugging information for our native GDB.
645 Due to the way CVS works, it may not properly update src/contrib/gcc
646 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
647 and then do a cvs update.
650 When exec'ing set[ug]id executables, the kernel now ensures that the
651 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
654 New sendmail startup scripts have been installed to make it
655 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
656 variable sendmail_enable to "NO" no longer prevents any sendmail
657 daemons from starting. Instead, either set sendmail_enable to
658 "NONE" or change mta_start_script to a script for starting
659 an alternative MTA. Setting mta_start_script to "" will
660 also prevent any MTA from being started at boot.
663 UCONSOLE is no longer a valid kernel option.
666 FreeBSD 5.0 DP-1 was basically branched today.
669 Warnings are now errors in the kernel. Unless you are a developer,
670 you should add -DNO_WERROR to your make line.
673 sendmail 8.12.2 has been imported. The sendmail binary is no
674 longer a set-user-ID root binary and the infrastructure to support
675 command line mail submission has changed. Be sure to run
676 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
677 and /etc/mail) and read /etc/mail/README for more details.
679 Due to the import of sendmail 8.12.2, a new user and group are
680 required in order for sendmail to run as a set-group-ID
681 binary. A 'make installworld' will use the new user and group
682 to set the owner and group of /var/spool/clientmqueue and will
683 fail if the new user and group do not exist. The 'smmsp' user
684 and group must be merged from src/etc/group and
685 src/etc/master.passwd before using 'make installworld'.
686 'mergemaster -p' will do this. You may need to install
687 mergemaster before this will work if you are updating from a
688 very old version of current. The updating recipe has changed
692 The preferred configuration method for PAM is now /etc/pam.d/
693 rather than /etc/pam.conf. If you have an unmodified
694 pam.conf, just delete it after your next mergemaster run. If
695 you have local modifications, you can use
696 /usr/src/etc/pam.d/convert.pl to incorporate them into your
699 Please see the following url for more details:
700 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
702 If anyone here is already using the new rc.conf(5) variable
703 networkfs_types, please note that it has changed
704 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
707 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
708 started out its life in the ISDN4BSD project as an offspring
709 from sys/net/if_spppsubr.c, which eventually got a life of its
710 own. All the accumulated features and bug fixes of the i4b
711 version have now been merged back into the base system's
712 version now. The only user-visible change resulting from this
713 is that i4b's sppp(4) interfaces are to be managed with
714 spppcontrol(8) again, since ispppcontrol(8) has been retired
715 as well. (There has never been rc file support for
716 ispppcontrol in -current, but only in -stable. That will be
717 reverted by the time the changes are MFCed.)
720 The fdc(4) driver has been updated and now automatically
721 recognizes media in `standard' formats (like 1440 KB and
722 720 KB for a 3.5" high-density drive) when accessing the
723 default device node (e. g. /dev/fd0). The old variety of
724 floppy device nodes /dev/fd*.* is no longer present by
725 default, devices can be created (in DEVFS) on demand. They
726 will need to be customized then for `odd' densities using
730 The bugs in procfs' debugging support code have been fixed,
731 and truss(1) now works again.
734 Daily security checks have been split out to use the periodic(8)
735 scripts. Some change in configuration may be necessary. Please
737 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
741 sos added VCD/SVCD support to ata driver and that needs the
742 kernel and burncd to be in sync.
745 The procfs pseudo-filesystem has now been converted to use the
746 pseudofs framework. If you have 'options PROCFS' in your
747 kernel config, you'll need to add 'options PSEUDOFS' if it's
750 This change temporarily breaks truss(1); use ktrace(1) instead
751 until the issue has been resolved.
754 A security hole in OpenSSH involving `UseLogin yes' has been
758 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
759 after this date. You need to do this only once.
762 Most of the awk issues have been resolved. Some rough
763 edges may be left, but for the most part things should be
764 back to "normal." For CURRENT's usual definition of "normal."
767 Awk has been upgraded to the one true awk from bell labs. Expect
768 choppy waves in the upgrade process.
771 The asr driver problem has been resolved.
774 Due to changes in other parts of the system, the asr driver
775 now causes the system to panic on boot. Do not use it pending
776 correction. Comment it out of any kernel config file that you
777 try to use from this date forward.
780 When crossbuilding, use TARGET=xxx where you used to use
781 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
782 unless you are changing both of them. To cross build pc98 on
783 an alpha, for example, you need to set TARGET=pc98 and
787 The kernel interface that burncd depends on has changed.
788 You must recompile both the kernel and userland applications
792 When crossbuilding, please set TARGET_ARCH rather than
793 MACHINE_ARCH to indicate the target. In the future, one will
794 set TARGET_MACHINE where you set MACHINE now. At the moment,
795 setting MACHINE alone for same MACHINE_ARCH machines works
796 (eg, you can build pc98 on an i386 machine and vice versa).
799 Some weird problems result from using ACPI on some machines.
800 To disable ACPI you can add
801 hint.acpi.0.disabled="1"
802 to /boot/loader.conf (or by putting set X=Y at the boot
805 Alternatively, you can remove it from /boot/kernel/acpi.ko
806 or use the MODULES_OVERRIDE function in your kernel config
807 file and not list acpi in that list.
810 The buildworld has been fixed. You may need to install
811 the 4.x compatibility libraries for some old binaries
812 to work. Add COMPAT4X=true to your /etc/make.conf to
813 get them installed on every installworld, or execute the
814 following to get them installed only once:
815 cd src/lib/compat/compat4x.<arch>
817 You will see ``__stdoutp undefined'' until you do this.
820 There's a bug in the world build process. The cross-tools
821 are build with the NEW headers, but the OLD libc.a. This
822 leads to all kinds of problems with the new libc. A temporary
824 CFLAGS="-O -pipe -D_OLD_STDIO"
825 before building world when upgrading from 4.x to current. This
826 can be removed afterwards.
828 A proper fix to the buildworld target is needed.
831 Peter has committed his new kthread nfs client/server code.
832 NFS may be unstable after this date.
835 KSE has hit the tree. Lots of things are now different in
836 the kernel. While a few problems were introduced in the
837 initial commit, most of the major ones have been found and
841 In OLDCARD, CardBus bridges appear to be stable. The work
842 arounds described in the 20010604 entry are now no longer
843 necessary and will be ignored. Most insert/remove problems
844 have been rectified around this date.
847 named now runs as user bind and group bind rather than as
848 root. If named_enable is set to YES in /etc/rc.conf, ensure
849 that user bind is available in /etc/passwd (using vipw(8))
850 and that group bind is available in /etc/group. Also make
851 sure that user or group bind has read (and not write)
852 permission for your name server configuration and that it
853 has read and write permission for your slave zone files and
856 If you wish to continue to run named as root (a less secure
857 alternative), add a line to /etc/rc.conf saying
862 The PAM libraries have had an API upgrade that is beyond
863 the ability of the shared library major number to handle.
864 It is manifested by PAM-using ports dumping core. The
865 solution is to rebuild those ports.
868 The kernel compile module has moved from src/sys/compile/FOO
869 to src/sys/${MACHINE}/compile/FOO.
872 The pccard modem issue from 20010613 has been corrected.
873 OLDCARD support is still a little weak in -current. slot 1 is
874 known not to work on some TI based cardbus bridges. Some
875 cardbus bridges do not properly detect insert/removal events.
876 IRQ configuration needs more safety belts.
879 Softupdates problems have been corrected.
882 Peter ripped out the linkerset support. You must, as always,
883 rerun config after you cvsup if you are using the traditional
884 kernel building methods.
887 pccard modems may not work with current after 20010604 date. Some
888 do, others result in panics. *MAKE*SURE* that you update your
889 config and /etc/rc.conf ala the 20010604 entry, or you will have
890 problems (this issue will be fixed, it just hasn't been yet).
893 SOFTUPDATES seem to be broken since the middle of May or so. Do not
894 use them in current. You can disable softupdates on all mounted
895 partitions, or remove SOFTUPDATES the kernel config file.
898 After Peter's commits to the hints code, people have been noticing
899 that certain devices are attached (or try to) twice. This is due
900 to having both static hints as well as a /boot/device.hints. To
901 work around this issue, please use only one or the other mechanism
902 until this bug is fixed.
904 Please note that a feature of config is that if you have config
905 file FOO and FOO.hints, it automatically adds FOO.hints to the
906 hints.c file, whether you want it to or not.
909 Locale names have changed to match other systems better.
912 pccard support for pci cards has been committed. You must change
913 your /etc/pccard.conf irq lines. It must match the irq used by
914 pcic device. Interrupt storms may result if you fail to do this.
915 Interrupt storms look a lot like a hang.
917 You must also install a new pccardd, otherwise you will get an
918 interrupt storm at card reset time (just after it tells you what
921 pccardd_flags="-I" is necessary for the time being. It tells pccardd
922 not to ask the kernel if the interrupt is really free or not before
923 using it. You can either change the /etc/pccard.conf irq lines to
924 match pcic, or add "-i X" to the pccardd_flags.
927 INSTALL=install -C is being deprecated. If you want to do this,
928 use COPY=-C instead. The former method will be supported for only
929 a limited time. If you see
931 install: warning: the -d and -C options may not be specified together
933 in your makeworld, then you need to migrate towards using
937 It appears that vm is now stable enough to use again. However,
938 there may be other problems, so caution is still urged. alpha
939 definitely is in bad shape.
942 Minor repo damage has happened. This may cause problems
943 with cvsup of ports. If you get errors, please see
944 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
945 at the bottom for details on a workaround. The error message
947 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
950 Vm and/or swapping are busted on -current. Please be patient.
953 pccard has had much reorganizational work done to it over
954 the past few days. Everything should still work, but if
955 not, please contact imp@freebsd.org.
958 ata ioctl changed. Make sure to recompile both kernel and
959 userland at the same time.
962 New ncurses imported.
965 DEVFS is now opt out, not opt in. Barring major problems, this
966 will be the only way to go starting July 1.
969 OpenSSH has been updated to 2.9. Some defaults are different,
970 including RhostsRSAAuthentication, which changes from yes to no.
973 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
976 Building perl was broken at 02:25:25 PDT.
979 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
980 go back in the water.
983 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
984 this date, but before the correction date.
987 old fsck and new kernel interactions appear to have been fixed.
990 fsck and the kernel were changed to handle some optimizations
991 to directory layout. This breaks backward compatibility.
992 Update only if you understand that you must not use the old
993 fsck with the new kernel ever.
996 fsck has changed the meaning of the pass column in /etc/fstab.
997 Please see the cvs commit to fsck.8 or the fsck.8 man page for
998 details. It is unclear if changes to /etc/fstab are necessary.
1001 portmap had changed name to rpcbind for maximum POLA in your
1002 current world. /etc/hosts.{allow,deny} needs changes. nfs and
1003 other rpc based programs that rely on portmapper will not work
1004 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
1007 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1008 and ATA_ENABLE_TAGS are no longer kernel options. They have
1009 been replaced by tunables. See ata.4 for details.
1012 The fxp driver was converted to use miibus. If you compile
1013 fxp into your kernel statically, you will need to add miibus.
1016 The wi device now defaults to BSS (infrastructure) mode
1020 /dev/urandom should be a symbolic link to /dev/random now.
1021 Users of current not using DEVFS need to run MAKEDEV std.
1022 ssh might not work if you don't.
1025 The ed driver has been updated. It now allows mii attachments,
1026 which means that you must include the miibus in your kernel if
1027 you use the ed driver.
1030 The problems with libc have been corrected. It is now mostly
1031 safe to go back into the water.
1034 The size of FILE was changed. This breaks upgrading. If
1035 you must upgrade, be prepared for pain. It also breaks almost
1036 all binaries that you've compiled on -current. You are warned
1037 that before upgrading would be a good time to do a level 0
1038 dump of your system. No, really, I mean it this time.
1040 To get to the new system, you'll need to use the following
1041 workaround. Hopefully this can be sorted out so that we
1042 don't have to move this to the updating section.
1044 To get around the installworld problem, do:
1045 # cd /usr/src/usr.bin/sed
1049 If that doesn't work, then try:
1050 # make -k installworld
1054 DEVFS is now the default. If you use vinum, make sure that you
1055 do not include devfs in your kernel as problems result.
1058 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1059 Remove them from your config.
1062 ****************************** WARNING ******************************
1063 buildkernel has been changed slightly
1064 ****************************** WARNING ******************************
1065 KERNCONF replaces the variable KERNEL for buildkernel. You
1066 should update your scripts and make.conf accordingly.
1069 config has changed to allow DEV_FOO as a replacement for NFOO.
1070 This requires a new config to build correctly.
1073 The kernel option I386_CPU is now mutually exclusive with the
1074 other cpu types. If you have an i386 system, be sure that it
1075 only had this line. Remove it for all other configurations.
1078 Changes to the kernel require it and burncd be in sync.
1081 Everyone who has hw.sndunit set to something in
1082 /etc/sysctl.conf, it is now hw.snd.unit.
1085 ex and vi were broken by some changes to sys/queue.h. If you
1086 have a bad vi, you will see make buildworld fail with a core
1087 dump while building termcap. You can work around this problem
1088 by adding -k to your make buildworld. This will cause the
1089 build to complete and install a new vi. Once that's done, you
1090 can rebuild again without the -k to pick up anything that
1091 might have been ignored by the -k option.
1093 Others have suggested that you can just rebuild libc if your
1094 vi/ex is dynamically linked, but I've not received any reports
1098 There have been some changes to libcrypt in -current. The
1099 libscrypt/libdescrypt symlink silliness is gone and the installed
1100 libcrypt is fully functional. Be aware of this.
1103 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1104 now require the addition of flag 0x80000 to their config line
1105 in pccard.conf(5). This flag is not optional. These Linksys
1106 cards will not be recognized without it.
1109 Important new FreeBSD-version stuff: PAM support has been worked
1110 in, partially from the "Unix" OpenSSH version. This requires
1111 adding the following in pam.conf:
1113 sshd auth sufficient pam_skey.so
1114 sshd auth required pam_unix.so try_first_pass
1115 sshd session required pam_permit.so
1118 cvs updated to 1.11.
1121 The random device needs more entropy, so you need to make sure
1122 that you've run mergemaster to get a /etc/rc which will seed
1123 /dev/random. If you don't and the system hangs after ldconfig,
1124 then banging on the keyboard randomly until it unhangs is one
1128 ****************************** WARNING ******************************
1129 Sendmail has been updated.
1130 ****************************** WARNING ******************************
1131 o mail.local(8) is no longer installed as a set-user-id binary.
1132 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1134 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1136 o Now using sendmail's version of vacation(1).
1137 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1138 in /usr/share/sendmail/cf.
1139 o sendmail.cw changed to local-host-names
1141 More details can be found at
1142 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1145 The ports tree's new layout is in place. Be sure to update
1146 your entire ports tree, or you will have problems.
1149 The perl build procedure no longer installs miniperl, nor uses
1150 the installed miniperl. It is recommended that you delete
1154 This weekend the ports tree will be updated to a new layout.
1155 It will be in an inconsistent state until noted in the UPDATING
1156 file, or with asami-san's message to the relevant mailing
1157 lists. With this new layout, you'll need to update the whole
1158 tree for anything to work.
1161 There was a change in the passwd format. Need more information.
1164 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1165 place. Please update boot loader (not the boot blocks) at the
1166 same time as your kernel.
1169 The new pmtimer device is necessary for laptops. Failure to
1170 include the device will cause suspended laptops losing time
1171 when they resume. Include
1173 in your config file and
1174 hint.pmtimer.0.at="isa"
1175 to your /boot/device.hints file.
1178 The random device has been turned into a (pseudo-)device,
1179 rather than an option. The supplied kernel config files have
1180 been updated. You will need to do something similar in your
1181 own kernel config file.
1186 If you prefer to load the loadable module, you need to do
1190 The random device module has been renamed from randomdev.ko to
1191 random.ko. You will need to edit your /boot/loader.conf to
1192 reflect this if you load this module at boot time.
1193 The line should read:
1197 The SMPNG commit has happened. It should work, but if it
1198 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1199 to be a variety of minor issues. Please see 20000905 to make
1200 sure you don't have model loading problems which might at
1201 first blush appear related to SMP.
1204 nsswitch has been imported from NetBSD. Among other things,
1205 this means that /etc/host.conf is no longer used. See
1206 nsswitch.conf(5) instead. Note that at boot time rc.network
1207 will attempt to produce a new nsswitch.conf file for you if you
1208 don't have one, and you have host.conf.
1211 The ucred structure changed size. This breaks the interface
1212 that mountd uses. Trying to use an older mountd with a newer
1213 kernel guarantees a panic. This means that you need to use
1214 kernels newer than today only with matching mountd, but you
1215 needed to do that anyway with the boot loader changes.
1218 The boot loader has been updated. The new default kernel is
1219 now /boot/kernel/kernel.ko. The new default module location
1222 You *MUST* upgrade your boot loader and kernel at the same time.
1223 The easiest way to do this is to do the buildworld/buildkernel/
1224 installkernel/installworld dance.
1226 Furthermore, you are urged to delete your old /modules directory
1227 before booting the new kernel, since kldload will find stale
1228 modules in that directory instead of finding them in the correct
1229 path, /boot/kernel. The most common complaint that this cures
1230 is that the linux module crashes your machine after the update.
1232 if [ ! -d /boot/kernel.old ]; then
1233 mv /modules.old /boot/kernel.old
1234 chflags noschg /kernel.old
1235 mv /kernel.old /boot/kernel.old/kernel.ko
1236 chflags schg /boot/kernel.old/kernel.ko
1240 A new issue with the sendmail upgrade has come to light.
1241 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1242 incorrectly install the default aliases in /etc/mail rather than
1243 move the old one from /etc. So you'll need to manually move the
1244 file, create a symbolic link, remove the old /etc/aliases.db and
1245 run newaliases. For safety sake, you should stop sendmail
1246 while doing this and run the upgrade when locally sourced email
1247 is not likely to be generated.
1250 /boot/device.hints is now required for installkernel to
1251 succeed. You should copy GENERIC.hints for your architecture
1252 into /boot/device.hints. If and only if you compile hints
1253 into your kernel, then this file may be empty. Please note,
1254 if you have an empty or missing /boot/device.hints file and
1255 you neglected to compile hints into your kernel, no boot
1256 messages will appear after the boot loader tries to start the
1260 If you do NOT have ``options RANDOMDEV'' in your kernel and
1261 you DO want the random device then add randomdev_load="YES" to
1265 suidperl is now always built and installed on the system, but
1266 with permissions of 511. If you have applications that use
1267 this program, you are now required to add ENABLE_SUIDPERL=true
1268 to /etc/make.conf. If you forget to do this,
1269 chmod 4511 /usr/bin/suidperl
1270 will fix this until the next build.
1273 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1274 visible changes that may immediately affect your configuration
1276 - New default file locations from src/contrib/sendmail/cf/README
1277 - newaliases limited to root and trusted users
1278 - MSA port (587) turned on by default
1279 - New queue file naming system so can't go from 8.11 -> 8.9
1280 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1281 - FEATURE(`nullclient') is more full featured
1282 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1283 - mail.local FreeBSD-only -b option changed to -B
1284 - See src/contrib/sendmail/RELEASE_NOTES for more info
1287 suidperl (aka sperl) is no longer build by default. You must
1288 specifically define BUILD_SUIDPERL to "true" for it to be build.
1289 Furthermore, we recommend that you remove /usr/bin/sperl* and
1290 /usr/bin/suidperl files from your system unless you have a
1291 specific use for it.
1294 Networking defaults have been tightened. Anybody upgrading
1295 /etc/defaults/rc.conf needs to add the following lines to
1296 /etc/rc.conf if they want to have the same setup
1297 afterwards (unless the variables already are set, of course):
1298 # Enable network daemons for user convenience.
1300 portmap_enable="YES"
1301 sendmail_enable="YES"
1304 If you have null_load="YES" in your /boot/loader.conf, you
1305 will need to change that to nullfs_load="YES".
1308 The "installkernel" target has changed slightly. Now even if
1309 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1310 it will install the MYKERNEL file (built with the buildkernel
1311 target) as /kernel rather than /MYKERNEL. Those who have
1312 updated their /boot/loader.conf files to point to /MYKERNEL
1313 should remove that entry or perform manual rename of /kernel
1317 If you use CVSUP or CTM to get CVS trees, AND you used to get
1318 the old crypto files from internat.freebsd.org AND you check
1319 out files from the CVS tree with the cvs command, please read
1320 http://people.freebsd.org/~imp/internat.txt
1321 for details on potential problems that you might have and how
1324 If you are merely a mirror, or don't answer yes to each of the
1325 clauses above, you needn't worry.
1328 /etc/security has been updated to print the inode number of
1329 setuid programs that have changed. You will see a large spike
1330 in the number of changed programs the first time when you run
1331 mergemaster to get a new /etc/security.
1334 /dev/random now has good entropy collection (from the keyboard
1335 and sysmouse drivers). Please ensure that either `options
1336 RANDOMDEV' is present in your kernel config file or that
1337 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1338 not have the /dev/random driver, OpenSSL (and consequently
1339 lots of crypto tools (like SSH)) will fail with strange
1340 errors. (see below, 20000624).
1342 FreeBSD-current is safe again to run Crypto.
1345 phk made the malloc default options AJ. This may slow things
1346 down and uncover other latent bugs in the code. If you need to
1347 run at full speed, you can disable this by doing the following:
1348 ln -s aj /etc/malloc.conf
1351 libftpio's version was accidentally bumped a few days ago. This
1352 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1353 before doing your next buildworld/installworld pair. It certainly
1354 won't hurt to remove it before the update procedure. It will
1355 break fetch until a new one is built, but ftp can be used in the
1359 The crypto packages have changed for the cvsup. This has been done
1360 in a backward compatible way, but the old packages will go away at
1361 some point in the future. Look at /usr/share/examples/cvsup for
1365 With the new sys/modules/sound/drivers/*, you will need to
1366 set SYSDIR until you do an installworld after July 7th.
1369 rc.shutdown and rc will now call the rc.d scripts with start
1370 or stop. This may cause some harmless warnings from older
1371 rc.d scripts that haven't been updated.
1374 The libfetch based version of fetch has gone into the tree.
1375 Minor problems may result on some of the less popular sites,
1376 which should be reported to des@freebsd.org.
1379 From approximately this date forward, one must have the crypto
1380 system installed in order to build the system and kernel.
1381 While not technically strictly true, one should treat it as
1382 required and grab the crypto bits. If you are grabbing CVS
1383 trees, src-all and cvs-crypto should be treated as if they
1384 were required. You should check with the latest collections
1385 to make sure that these haven't changed.
1388 Mark Murray just committed the first parts of a cleanup of
1389 /dev/zero, et al. This is also cleaning up /dev/random.
1390 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1391 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1392 until Mark can merge in the fixes to this work in progress.
1393 openssh and openssl should not be used to generate keys from this
1394 date to the completion of the work.
1396 If you must operate at this reduced level of security, add '
1397 options RANDOMDEV' to your kernel or modload the randomdev
1398 module. You may also need to copy a new MAKEDEV to /dev and
1399 recreate the random and urandom devices.
1402 The license on the softupdates is now a standard 2 clause
1403 BSD license. You may need to remove your symbolic links
1404 that used to be required when updating.
1407 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1408 the config file update procedure.
1409 http://people.freebsd.org/~imp/config-upd.html
1410 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1411 isn't buildable. However, you can generate a LINT file:
1412 cd /sys/<ARCH>/conf && make LINT
1415 Binutils 2.10 have hit the tree, or will shortly. As soon
1416 as they do, the problem noted in 20000522 will be resolved and
1417 that workaround will no longer be required.
1420 phk removed the compatibility creation of wd devices in the
1421 ad driver. If you haven't done so already, you must update
1422 your fstab, etc to use the ad devices instead of the wd
1425 In addition, you'll need to update your boot blocks to a
1426 more modern version, if you haven't already done so. Modern
1427 here means 4.0 release or newer (although older releases
1431 Peter took an axe to config(8). Be sure that you read his mail
1432 on the topic before even thinking about updating. You will
1433 need to create a /boot/device.hints or add a hints directive
1434 to your config file to compile them in statically. The format
1435 of the config file has changed as well. Please see GENERIC or
1436 NEWCARD for examples of the new format.
1438 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1439 says that it has been fixed, assume that must use the hints mechanism
1440 in the loader if you need to use a machine with very old ISA cards
1444 A new set of binutils went into the tree today. Anybody
1445 building a kernel after this point is advised that they need
1446 to rebuild their binutils (or better yet do a
1447 buildworld/installworld) before building a new kernel.
1449 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1450 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1451 is recommended that you don't set this option until the problem
1455 The ethernet drivers were all updated to clean up the BPF handling.
1458 The problems with boot blocks on the alphas have been corrected.
1459 This will require some care in updating alphas. A new libstand
1460 is requires for the boot blocks to build properly.
1463 Recompile all kld modules. Proper version dependency info
1467 Modules have been disconnected from the buildworld tree and
1468 connected to the kernel building instead.
1471 You may need to build gperf
1472 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1473 when upgrading from 4.0 -> current. The build system now uses
1474 an option only in -current.
1477 The method that we brand ELF binaries has changed to be more
1478 acceptable to the binutils maintainers. You will need to
1479 rebrand your ELF binaries that aren't native. One problem
1480 binary is the Linux ldconfig. After your make world, but
1481 before you reboot, you'll need to issue:
1482 brandelf -t Linux /compat/linux/sbin/ldconfig
1483 if you have Linux compatibility enabled on your machine.
1486 If you have really bad/marginal IDE drives, you may find they
1487 don't work well. Use pio mode instead. The easiest way to
1488 cope if you have a problem combination is to add:
1489 /sbin/sysctl hw.ata.ata_dma=0
1490 to the start of /etc/rc.conf.
1493 The ISA and PCI compatibility shims have been connected to the
1494 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1495 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1496 include the appropriate option in your kernel config. Drivers
1497 using the shims should be updated or they won't ship with
1498 5.0-RELEASE, targeted for 2001.
1501 We've entered the traditional post release dumping party.
1502 Large kernel changes are being committed and are in the
1503 works. It is important to keep the systems' klds and kernel
1504 in sync as kernel interfaces and structures are changing.
1505 Before reporting kernel panics, make sure that all modules
1506 that you are loading are up to date.
1509 If you are upgrading from an older version of FreeBSD, you
1510 need to update your boot blocks as well. 'disklabel -B ad0'
1511 will do the trick. This isn't critical until you remove your
1512 wd device entries in /dev, at which point your system will not
1516 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1517 to upgrade to 4.0 from 3.x.
1523 Avoid using make -j when upgrading. From time to time in the
1524 past there have been problems using -j with buildworld and/or
1525 installworld. This is especially true when upgrading between
1526 "distant" versions (eg one that cross a major release boundary
1527 or several minor releases, or when several months have passed
1528 on the -current branch).
1530 Sometimes, obscure build problems are the result of environment
1531 poisoning. This can happen because the make utility reads its
1532 environment when searching for values for global variables.
1533 To run your build attempts in an "environmental clean room",
1534 prefix all make commands with 'env -i '. See the env(1) manual
1535 page for more details.
1539 If you are updating from a prior version of FreeBSD (even one just
1540 a few days old), you should follow this procedure. With a
1541 /usr/obj tree with a fresh buildworld,
1542 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1543 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1545 To just build a kernel when you know that it won't mess you up
1546 --------------------------------------------------------------
1547 This assumes you are already running a 5.X system. Replace
1548 ${arch} with the architecture of your machine (e.g. "i386",
1549 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1551 cd src/sys/${arch}/conf
1552 config KERNEL_NAME_HERE
1553 cd ../compile/KERNEL_NAME_HERE
1558 If this fails, go to the "To build a kernel" section.
1560 To rebuild everything and install it on the current system.
1561 -----------------------------------------------------------
1562 # Note: sometimes if you are running current you gotta do more than
1563 # is listed here if you are upgrading from a really old current.
1565 <make sure you have good level 0 dumps>
1566 <maybe fix /etc/fstab> [7]
1568 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1569 make installkernel KERNCONF=YOUR_KERNEL_HERE
1571 <reboot in single user> [3]
1572 /etc/rc.d/preseedrandom [10]
1579 To cross-install current onto a separate partition
1580 --------------------------------------------------
1581 # In this approach we use a separate partition to hold
1582 # current's root, 'usr', and 'var' directories. A partition
1583 # holding "/", "/usr" and "/var" should be about 2GB in
1586 <make sure you have good level 0 dumps>
1589 <maybe newfs current's root partition>
1590 <mount current's root partition on directory ${CURRENT_ROOT}>
1591 make installworld DESTDIR=${CURRENT_ROOT}
1592 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1593 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1594 ${CURRENT_ROOT}/boot/device.hints # as needed
1595 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1596 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1597 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1598 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1599 <reboot into current>
1600 <do a "native" rebuild/install as described in the previous section>
1601 <maybe install compatibility libraries from /usr/src/lib/compat>
1605 To upgrade in-place from 4.x-stable to current
1606 ----------------------------------------------
1607 # 5.x uses more space than 4.x. Also, the location of kernel
1608 # modules has changed. If you are installing 5.0 onto a 4.x
1609 # system, you'll need about 30MB of free disk space on your /
1610 # partition. If you have less than this, you may encounter difficult
1611 # to back out of problems with this procedure. If /tmp is on
1612 # the / partition, you may want to completely remove all its content
1613 # before upgrading, as this can be a common source of shortage of
1616 <make sure you have good level 0 dumps>
1617 <maybe fix /etc/fstab> [7]
1619 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1620 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1621 make installkernel KERNCONF=YOUR_KERNEL_HERE
1622 cd sys/boot ; make STRIP="" install [6]
1624 <reboot in single user> [3]
1625 /usr/src/etc/rc.d/preseedrandom [10]
1627 rm -rf /usr/include/g++
1632 Make sure that you've read the UPDATING file to understand the
1633 tweaks to various things you need. At this point in the life
1634 cycle of current, things change often and you are on your own
1635 to cope. The defaults can also change, so please read ALL of
1636 the UPDATING entries.
1638 Also, if you are tracking -current, you must be subscribed to
1639 freebsd-current@freebsd.org. Make sure that before you update
1640 your sources that you have read and understood all the recent
1641 messages there. If in doubt, please track -stable which has
1642 much fewer pitfalls.
1644 [1] If you have third party modules, such as vmware, you
1645 should disable them at this point so they don't crash your
1648 [2] If you have legacy ISA devices, you may need to create
1649 your own device.hints to reflect your unique hardware
1652 [3] From the bootblocks, boot -s, and then do
1657 adjkerntz -i # if CMOS is wall time
1658 Also, when doing a major release upgrade, it is required that
1659 you boot into single user mode to do the installworld.
1660 For the 4.x -> 5.0 upgrade, you will also see many messages about
1661 needing to recompile your userland. These are harmless and can
1662 be ignored while you proceed to the next step.
1664 [4] Note: This step is non-optional. Failure to do this step
1665 can result in a significant reduction in the functionality of the
1666 system. Attempting to do it by hand is not recommended and those
1667 that pursue this avenue should read this file carefully, as well
1668 as the archives of freebsd-current and freebsd-hackers mailing lists
1669 for potential gotchas.
1671 [5] Usually this step is a noop. However, from time to time
1672 you may need to do this if you get unknown user in the following
1673 step. It never hurts to do it all the time. You may need to
1674 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1675 install) after the buildworld before this step if you last updated
1676 from current before 20020224 or from -stable before 20020408.
1678 [6] 4.x boot loader can be used to boot a 5.x system, however
1679 it is difficult to do that at best. If you wish to try, then
1680 you should interrupt the boot and at the ok prompt type:
1682 ok boot /boot/kernel/kernel
1683 If this fails to work, you must install a new boot loader as
1686 [7] Before you upgrade, please make sure that you are not using
1687 compatibility slices. These are device names of the form, on i386
1688 and other architectures that use MBR slicing, /dev/ad0a without the
1689 actual slice name. Chances are excellent that these will break.
1690 You generally must update these entries to use the post FreeBSD
1691 2.x form of /dev/ad0s1a.
1693 [8] In order to have a kernel that can run the 4.x binaries
1694 needed to do an installworld, you must include the COMPAT_FREEBSD4
1695 option in your kernel. Failure to do so may leave you with a system
1696 that is hard to boot to recover.
1698 [9] When checking out sources, you must include the -P flag to have
1699 cvs prune empty directories. Also, if CPUTYPE is defined in your
1700 /etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1701 operator, so that buildworld can override the CPUTYPE if it needs to.
1702 In case you would like to avoid installing new packages of everything,
1703 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1704 compatibility libraries are build which should allow you to continue
1705 using your existing software for a while.
1707 [10] In order to create temporary files, /dev/random must be
1708 initialized by feeding data into it. /etc/rc.d/preseedrandom
1712 This file contains a list, in reverse chronological order, of major
1713 breakages in tracking -current. Not all things will be listed here,
1714 and it only starts on March 15, 2000. Updating files can found in
1715 previous releases if your system is older than this.
1717 Copyright information:
1719 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1721 Redistribution, publication, translation and use, with or without
1722 modification, in full or in part, in any form or format of this
1723 document are permitted without further permission from the author.
1725 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1726 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1727 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1728 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1729 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1730 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1731 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1732 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1733 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1734 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1735 POSSIBILITY OF SUCH DAMAGE.
1737 If you find this document useful, and you want to, you may buy the
1740 Contact Warner Losh if you have any questions about your use of