1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 Items affecting the ports and packages system can be found in
8 /usr/ports/UPDATING. Please read that file before running
9 portupgrade. Important recent entries: 20040724 (default X changes).
11 [[ The UPDATING file will be trimmed to 20040814 on or about Oct 1, 2004 ]]
13 NOTE TO PEOPLE WHO THINK THAT FreeBSD 6.x IS SLOW:
14 FreeBSD 6.x has many debugging features turned on, in
15 both the kernel and userland. These features attempt to detect
16 incorrect use of system primitives, and encourage loud failure
17 through extra sanity checking and fail stop semantics. They
18 also substantially impact system performance. If you want to
19 do performance measurement, benchmarking, and optimization,
20 you'll want to turn them off. This includes various WITNESS-
21 related kernel options, INVARIANTS, malloc debugging flags
22 in userland, and various verbose features in the kernel. Many
23 developers choose to disable these features on build machines
24 to maximize performance.
27 Netgraph changed its message format slightly to align the data
28 portion well on 64 bit machines.
29 Netgraph using utilities (e.g. ngctl, nghook, ppp, mpd,
30 pppoed, bluetooth, ATM) should be recompiled when a new kernel
34 IPFW has been converted to use PFIL_HOOKS. This change is
35 transparent to userland and preserves the ipfw ABI. The ipfw
36 core packet inspection and filtering functions have not been
37 changed, only how ipfw is invoked is different. Note that
38 "option PFIL_HOOKS" is required to use IPFIREWALL compiled
39 into the kernel or as KLD.
42 The RANDOM_IP_ID option has been replaced by the sysctl
43 net.inet.ip.random_id. If you had RANDOM_IP_ID in your kernel then
44 you may want to add "net.inet.ip.random_id=1" to /etc/sysctl.conf.
47 The size of 'struct ifnet' has changed due to the addition of the
48 if_carp placeholder. All kernel modules implementing network
49 interfaces must be recompiled as a result.
52 Module loading has been fixed. Some older installations will
53 drop proper module_path initialization and modules will fail to
54 load properly. If you have a line in /boot/loader.rc that says:
55 "initialize drop", do (i386 only):
56 cp /usr/src/sys/boot/i386/loader/loader.rc /boot/loader.rc
57 chown root:wheel /boot/loader.rc
58 chmod 444 /boot/loader.rc
61 making /dev/(null|zero) into a module proved to be too unpopular,
62 so this bit has been revoked from the previous (20040801) entry.
65 The /dev/mem, /dev/io /dev/(null/zero) devices are now modules,
66 so you may wish to add them to your kernel config file. See
70 System compiler has been upgraded to GCC 3.4.2-pre. As with any major
71 compiler upgrade, there are several issues to be aware of. GCC 3.4.x
72 has broken C++ ABI compatibility with previous releases yet again
73 and users will have to rebuild all their C++ programs with the new
74 compiler. If you are getting run-time error such as
75 /libexec/ld-elf.so.1: Undefined symbol "_ZNSs20_S_empty_rep_storageE"
76 This entry does apply to you.
78 A new unit-at-a-time optimization mode, which is default in this
79 compiler release, is more aggressive in removing unused static
80 symbols. This is the likely cause of 'make buildworld' breakages
81 with non-default CFLAGS where optimization level is set to -O2
84 With the upgrade of the system compiler, the kernel has been upgraded
85 to match the new system compiler. This makes it impossible to build
86 a new kernel with the old compiler. Upgrade your system via
87 make buildworld and make kernel (see below) to fix this problem.
90 The size of 'struct ifnet' has changed due to the addition of
91 the IFF_NEEDSGIANT flag (and what it implies). All kernel
92 modules implementing network interfaces must be recompiled as
96 The sound device drivers are renamed. `sound' is always required,
97 while `snd_*' should be configured accordingly to your hardware.
98 Refer to NOTES for the detail of the drivers.
101 __FreeBSD_version bumped to 502122.
104 The console initialization on Alpha has been reworked and is now
105 identical to other platforms. This means that the hardcoding of
106 the serial console and the debug port has been removed. As such,
107 hints are now required for the sio(4) driver to become a console
108 or debug port. The NO_SIO option has been decommissioned because
112 A revamp of the debugging code in the kernel with some visible
113 changes beyond just the debugging experience:
114 o The DDB option is now specific to the DDB debugger backend
115 and should not be used any more for conditional compilation
116 of debugging code for when debugging is enabled. Use the KDB
118 o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have
119 been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED
120 respectively. This is in line with the first bullet.
121 o The remote GDB support has been untangled from DDB and needs
122 to be enabled separately now. Use the GDB option for this.
123 o The GDB_REMOTE_CHAT option has been removed. Support for this
124 homegrown feature is discontinued. The GDB remote protocol
125 supports console output and it makes sense to use that.
126 o The DDB_NOKLDSYM option has been removed. The DDB debugger
127 now supports both direct symbol table lookups as well as KLD
128 symbol lookups through the linker.
131 Bluetooth code has been marked as non-i386 specific.
132 __FreeBSD_version has been bumped to 502121 to mark this change.
135 The native preemption has been added to the kernel scheduler.
136 There is some report that the ULE scheduler was broken in some
137 machines and we encourage users using the ULE scheduler either
138 stick with a known good kernel, or temporarily switch to the 4BSD
139 scheduler as a workaround.
142 The netgraph ABI version number has been incremented to indicate
143 an incompatible change in the ABI. Old netgraph nodes will refuse
144 to attach until recompiled. Netgraph now uses mbuf tags to move
145 metadata and this commit removes its home-grown metadata facility.
146 Nodes should just recompile, unless they use metadata, in which
147 case the changes are simple; the file ng_ksocket.c serves as an
148 example of such changes.
150 This also broke i4b, although the compile problem has been papered
154 ACPI has been updated to disable known-bad BIOS revisions. A message
155 will be printed on the console indicating that ACPI has been disabled
156 automatically and that the user should use a newer BIOS, if possible.
157 If you think ACPI does work on your system and want to override
158 this (i.e., for testing), set hint.acpi.0.disabled="0" at the
162 pf was updated to OpenBSD-stable 3.5 and pflogd(8) is privilege
163 separated now. It uses the newly created "_pflogd" user/group
164 combination. If you plan to use pflogd(8) make sure to run
165 mergemaster -p or install the "_pflogd" user and group manually.
168 Network interface cloning has been overhauled. This change will
169 require a recompile of modules using cloning and modification of
170 external ones to the new API. __FreeBSD_version has been bumped
171 to 502119 to mark this change. Additionally, users creating
172 stf(4) interfaces via "ifconfig stf" will need to update their
173 scripts as this will create an interface named "stf" instead of
174 "stf0" and ifconfig will not print "stf0" to stdout.
177 On 20040524, the /etc/rc.d/nsswitch script was modified to
178 automatically create /etc/nsswitch.conf on startup if it did
179 not already exist. Unfortunately, an error in the man page
180 was carried over to the script, resulting in incorrect
181 nsswitch settings. The simplest remedy is to remove both
182 /etc/nsswitch.conf and /etc/host.conf; they will be recreated
183 during the next reboot.
186 The return value of sema_timedwait(9) has been changed to
187 make it consistent with cv_timedwait(9). Be sure to recompile
188 the ips module and any third-party modules which call
192 ALTQ is now linked to the build. This breaks ABI for struct ifnet.
193 Make sure to recompile modules and any userland that makes use of
194 sizeof(struct ifnet). In order to get the altq headers in place
195 please recompile and reinstall world.
198 Splitting kern_thread.c into 2 files (adding kern_kse.c)
199 requires that you re-run config after updating your tree.
202 The MIDI drivers have been removed. Until the new module-friendly
203 ones are merged, remove or comment out midi and seq from your
204 kernel configuration.
207 Due to a new option in ipfw (versrcreach) the ipfw(8) command
208 needs to be recompiled. Normal accept/reject rules without
209 options are not affected but those with options may break until
210 ipfw(8) is recompiled.
213 Due to changes in the callout ABI, kernels compiled after this
214 date may be incompatible with kernel modules compiled prior to
218 The PCI bus power state stuff has been turned on. If this causes
219 problems for your system, please disable it using the tunable
220 hw.pci.do_powerstate=0.
223 The bulk of the pci problems have been fixed, although the floppy
224 drive is still broken.
227 A substantial update to the pci bus resource and power management
228 have been committed. Expect a bumpy ride for a few days until
229 the unanticipated problems have been resolved.
232 Due to changes in the the Yarrow initialization process,
233 /dev/random needs to be fed before operations requiring
234 temp files can succeed in single user mode. This includes
235 running "make installworld". /dev/random may be fed by running
236 "/etc/rc.d/initrandom start" or with 20040415 source by running
237 "/etc/rc.d/preseedrandom".
240 The debug.mpsafenet tunable controls whether the kernel Giant
241 lock is held across the lower levels of the network stack, and
242 by default is turned off. In the few days following 20040322,
243 the behavior of debug.mpsafenet will change such that this
244 tunable controls Giant over all levels of the network stack.
245 If you are currently setting debug.mpsafenet to 1, you should
246 set it back to 0 (the default) again during the change-over.
247 An additional note will be added to UPDATING when sufficient
248 locking is merged to permit this to take place.
251 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
252 64-bits. This is a very major incompatible change, so people
253 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
254 detailed instructions on how to make this upgrade. People
255 upgrading FreeBSD on other platforms can ignore this event.
258 The packet filter (pf) is now installed with the base system. Make
259 sure to run mergemaster -p before installworld to create required
260 user account ("proxy"). If you do not want to build pf with your
261 system you can use the NO_PF knob in make.conf.
262 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
263 pf system consists of the following three devices:
265 device pflog # optional
266 device pfsync # optional
269 If you are having trouble with the libc_r -> libpthread transition
270 (see the 20040130 entry), place the following lines at the top of
273 libc_r.so.5 libpthread.so.1
274 libc_r.so libpthread.so
276 This will cause all programs and libraries linked against libc_r
277 to use libpthread instead.
280 Some sshd configuration defaults have changed: protocol version 1
281 is no longer enabled by default, and password authentication is
282 disabled by default if PAM is enabled (which it is by default).
283 OpenSSH clients should not be affected by this; other clients may
284 have to be reconfigured, upgraded or replaced.
287 The ABIs defined in <resolv.h> and <netdb.h> have been updated
288 to support improved reentrancy. Multi-threaded programs that
289 reference the "_res" or "h_errno" symbols may experience some
290 problems if they are not recompiled. Single-threaded programs
291 should remain unaffected.
294 routed has been updated in the base system from the vendor
295 sources, routed v2.27, from rhyolite.com. This change means that
296 for users who use RIP's MD5 authentication feature, FreeBSD
297 -CURRENT's routed is now incompatible with previous versions
298 of FreeBSD; however it is now compatible with implementations
299 from Sun, Cisco and other vendors.
302 The tcpcb structure has changed and makes a recompile of libkvm
303 and related userland network utilities necessary.
306 The cdevsw structure has changed in two externally visible ways.
307 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
308 Second, the d_version field must be filled in with D_VERSION.
309 Drivers outside the tree will need to be updated.
312 The /etc/rc.d/ttys script has been removed. It is no longer
313 necessary since devfs has been mandatory for some time.
316 libkse has been renamed back to libpthread and is now the
317 default threads library. The gcc -pthread option has also
318 been changed to link to libpthread instead of libc_r. For
319 alpha and sparc64 machines, libkse is not renamed and links
320 are installed so that libpthread points to libc_r. Until
321 the ports system is updated to handle this change, it is
322 recommended that folks install an /etc/libmap.conf(5) that
323 maps libc_r to libpthread. If you have any binaries or
324 libraries linked to libkse, then it is also recommended
325 that you map libkse to libpthread. Anyone that is using
326 nvidia supplied drivers and libraries should use a libmap.conf
327 that maps libpthread to libc_r since their drivers/libraries
328 do not work with libpthread.
331 ULE has entered into its probationary period as the default scheduler
332 in GENERIC. For the average user, interactivity is reported to be
333 better in many cases. On SMP machines ULE will be able to make more
334 efficient use of the available parallel resources. If you are not
335 running it now, please switch over, replacing the kernel option
336 SCHED_4BSD with SCHED_ULE.
339 Move LongRun support out of identcpu.c, where it hardly
340 belongs, into its own file and make it opt-in, not mandatory,
341 depending on CPU_ENABLE_LONGRUN config(8) option.
344 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
345 if the login process is unable to successfully set the
346 process credentials to include all groups defined for the
347 user. The current kernel limit is 16 groups; administrators
348 may wish to check that users do not have over 16 groups
349 defined, or they will be unable to log in.
352 The ACPI module has been reactivated. It is no longer required
353 to compile ACPI support into kernels statically.
356 The statfs structure has been updated with 64-bit fields to
357 allow accurate reporting of multi-terabyte filesystem
358 sizes. You should build world, then build and boot the new kernel
359 BEFORE doing a `installworld' as the new kernel will know about
360 binaries using the old statfs structure, but an old kernel will
361 not know about the new system calls that support the new statfs
363 Note that the backwards compatibility is only present when the
364 kernel is configured with the COMPAT_FREEBSD4 option. Since
365 even /bin/sh will not run with a new kernel without said option
366 you're pretty much dead in the water without it. Make sure you
367 have COMPAT_FREEBSD4!
368 Running an old kernel after a `make world' will cause programs
369 such as `df' that do a statfs system call to fail with a bad
370 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
371 that cfsd (ports/security/cfs) needs to be recompiled after
372 these changes are installed.
374 ****************************DANGER*******************************
376 DO NOT make installworld after the buildworld w/o building and
377 installing a new kernel FIRST. You will be unable to build a
378 new kernel otherwise on a system with new binaries and an old
382 Some netgraph string length constants have been changed. This
383 change requires the netgraph kernel modules and all netgraph
384 userland components to be in sync. Especially users who require
385 netgraph to boot need to make sure to have world and kernel in
386 sync before rebooting.
389 Hyperthreading logical CPU's are no longer probed by default
390 when using the MP Table. If ACPI is being used, then logical
391 CPUs will be probed if hyperthreading is enabled in the BIOS.
392 If ACPI is not being used and hyperthreading is enabled in the
393 BIOS, logical CPUs can be enabled by building a custom kernel
394 with the option MPTABLE_FORCE_HTT enabled.
397 The i386 APIC_IO kernel option has been replaced by
398 'device apic'. The ACPI module has also been temporarily
399 disabled, so ACPI must be statically compiled into your
400 kernel using 'device acpi' if you wish to use the ACPI driver.
403 The API and ABI of struct ifnet have been changed by removing
404 the if_name and if_unit members and replacing them with
405 if_xname, if_dname, and if_dunit. All network drivers and most
406 userland programs which include net/if_var.h must be updated
407 and recompiled. __FreeBSD_version has been bumped to 501113 to
411 Changes to the cdevsw default functions have been made to remove
412 the need to specify nullopen() and nullclose() explicitly.
413 __FreeBSD_version bumped to 501110.
416 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
417 mount_cd9660(8) need to be in sync with kernel.
420 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
421 also be explicitly configured. Previously this dependency was
422 magically handled through some cruft in net/pfil.h; but that has
423 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
424 will fail with obtuse errors in ip_fil.c.
427 Fix a bug in arplookup(), whereby a hostile party on a locally
428 attached network could exhaust kernel memory, and cause a system
429 panic, by sending a flood of spoofed ARP requests. See
430 FreeBSD-SA-03:14.arp.
433 A change to /etc/defaults/rc.conf now causes inetd to be started
434 with `-C 60' if it is not overridden in /etc/rc.conf. This
435 causes inetd to stop accepting connections from an IP address
436 that exceeds the rate of 60 connections per minute.
439 The following rc.d scripts have been removed and should be
440 deleted from your installation: atm2.sh atm3.sh devdb
441 localdaemons network1 network2 network3. Depending on when
442 you last updated world and used mergemaster(8) you may or
443 may not have problems during the rc boot sequence. The simplest
444 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
445 The atm2.sh atm3.sh and devdb scripts were removed some time
446 ago, so depending on when you installed -CURRENT these scripts
447 may or may not exist on your system.
450 ATAng has been committed. You need to build world as sys/ata.h
451 has changed, and userland atacontrol depends on it.
452 If you use ATA SW raids you need "device ataraid" in your
453 kernel config file, as it is no longer pulled in automatically.
456 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
457 Among other things, this changes the device enumeration to be
458 closer to Solaris. Be aware that, this can even cause the machine
459 to not boot without manual intervention before the fstab is adjusted.
462 All current USB and Firewire quirks in da(4) have been deprecated
463 and will be removed for 5.2. If this causes failure for your
464 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
465 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
466 so the quirk can be re-enabled.
469 Problems with entry 20030714 have been corrected and no known issues
470 with /rescue and -j exist for host systems after this point in time.
473 FPU-less support has been removed from FreeBSD. Chances are you won't
474 notice. 386+387 support should still work after this change, but
475 it is now a minimum requirement for the i386 port that you have real
479 Some people are having problems with changes related to /rescue.
480 If you are building -j N, you will need to define NO_RESCUE. Others
481 will need to define it if /rescue has issues with their environment.
482 People should report those issues to current@.
485 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
486 across this point. Further, it might be a good idea to remove
490 Remove deprecated locale names and transition period code
491 for them, finishing switching to the new scheme. Check your
492 LANG environment variable.
495 CCD has been changed to be a fully GEOMified class. Kernel
496 and ccdconfig(8) needs to be in sync, this is particularly
497 important to remember beforehand if your source tree is on
498 a ccd device. Consider making a copy of the old ccdconfig
499 into /boot/kernel.good or wherever you keep your backup
503 There was a small window in which sed(1) was broken. If you
504 happen to have sed(1) installed during that window, which is
505 evidenced by an inability to build world with the failure
506 given below, you need to manually build and install sed(1)
507 (and only sed(1)) before doing anything else. This is a one-
508 time snafu. Typical failure mode:
510 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
511 targmatch.h:7:1: null character(s) ignored
512 targmatch.h:12:1: null character(s) ignored
513 targmatch.h:16:1: null character(s) ignored
516 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
517 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
518 usr.bin/sed/process.c).
521 Kerberos 5 (Heimdal) is now built by default. Setting
522 MAKE_KERBEROS5 no longer has any effect. If you do NOT
523 want the "base" Kerberos 5, you need to set NO_KERBEROS.
526 groff has been updated. If you try to do a buildworld and
527 get an infinite loop in troff, update to May 4th or newer. If you
528 have a newer kernel than userland, you may need to set the OSRELDATE
529 to 500110 in your environment before starting a buildworld.
532 The old rc system has been removed. Please report any problems
533 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
534 Your personal versions of these files will not be removed, so you can
535 continue to use them. However, you should take great care when updating,
536 especially when using mergemaster, since the compatibility code that
537 utilizes these old scripts has also been removed.
540 A bug has been fixed in /dev/devctl which would cause devd
541 to hang on boot, were it not for a workaround in devd. The
542 work around in devd will be removed around 20030507. You
543 have until then to upgrade your kernel before updating
544 userland. In general, you should have a userland and
545 kernel that's in sync with each other. However, given the
546 effects of this bug (hang on boot when starting devd), some
550 Alphas with libc from between 20030312 and 20030329 exhibit
551 floating point exceptions (FPEs), most notably in awk(1)
552 while upgrading the system through a buildworld.
554 So, to successfully upgrade your Alpha, you must either
555 downgrade your libc.so to a pre-20030312 version, or update
556 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
557 to CFLAGS, then forcibly rebuild and install libc:
559 cd /usr/src/lib/libc && \
560 make cleandir && make obj && \
561 make -DNOMAN -DNOPROFILE all && \
562 make -DNOMAN -DNOPROFILE install
565 sendmail 8.12.7 has been imported. It has one important
566 change for IPv6 users. The default submit.mc now uses
567 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
568 used to connect to the MTA. Users on IPv6-only machines
569 will need to edit /etc/mail/submit.mc appropriately.
572 NODEVFS option has been removed and DEVFS thereby made standard.
573 This makes all references to MAKEDEV obsolete, and they should
574 be removed when convenient.
577 The name of the device for the ofw console has changed, sparc64 users
578 must run mergemaster to update their installed /etc/ttys.
581 The scheduler framework has grown a second scheduler and consequently
582 you must specify one and only one scheduler in your kernel config.
583 The cvs config files have been updated to use the old scheduler
584 which may be selected via 'options SCHED_4BSD'. If you would like
585 to try the new, much more experimental, scheduler please try
586 'options SCHED_ULE' and contribute to the arch@ discussion.
589 A new version of the wi driver has been imported into the tree.
590 One now must have device wlan in the config file for it to operate
593 In addition, there have been some changes to how wi devices are
594 configured for point to point links to bring it more in line
595 with the former way of doing things, as well as compatibility
599 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
600 used an incompatible form of ABI for returning structures and unions
601 which FreeBSD's GCC maintainers were not aware of relative to previous
602 versions of FreeBSD. We have gone back to the ABI for now, and any
603 code compiled which is required to interoperate with other code (not
604 built at the same time) returning structs or unions should be
608 A name change in /etc/netconfig has been reverted to stay
609 compatible with suns TIRPC and also with NetBSD. You need
610 to run mergemaster after make world. A new libc does still work
611 with an outdated /etc/netconfig for some time, but you'll get
612 a warning. This warning will be removed in 20030301.
615 The recent binutils upgrade marks a kernel flag day on
616 sparc64: modules built with the old binutils will not work
617 with new kernels and vice versa. Mismatches will result in
618 panics. Make sure your kernel and modules are in sync.
621 The value of IPPROTO_DIVERT has changed. Make sure to keep
622 your kernel, netstat, natd and any third-party DIVERT
626 Old, compatibility slices have been removed in GEOM kernels.
627 This means that you will have to update your /etc/fstab to
628 not use disk devices of the form /dev/ad0a. Instead, you
629 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
630 partition really is on. The old device names have gone
631 away, so if you use them anywhere else, you must also adjust
632 those uses. (This doesn't affect the disks formatted in
633 the ``dangerously-dedicated'' mode.)
636 Alphas with kernels from between 20020830 and 20021023 and/or
637 rtld (ld-elf.so.1) older than 20021023 may experience problems
638 with groff while doing a buildworld (kernel: "out of memory",
639 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
640 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
642 So, to successfully upgrade your Alpha, you must either
643 upgrade your kernel and rtld first (which might be a bit
644 tricky), or avoid running the bootstrapped groff during the
645 "transitional" buildworld. To avoid running groff during the
646 transitional upgrade run make buildworld with -DNOMAN,
647 -DNO_SHAREDOCS, and -DNO_LPR.
650 gcc has been upgraded to 3.2. It is not all binary compatible
651 with earlier versions of gcc for c++ programs. All c++
652 programs and libraries need to be recompiled.
654 Also, if you encounter g++ issues, rm /usr/include/g++/* before
655 doing an installworld to make sure that stale files are removed.
658 Our /etc/termcap now has all the entries from the XFree86 xterm
659 almost unchanged. This means xterm now supports color by default.
660 If you used TERM=xterm-color in the past you now should use
661 TERM=xterm. (xterm-color will lead to benign warnings).
664 A "bug" in gcc(1) that was hiding warning in system headers was
665 fixed. It's probably time to add -DNO_WERROR to your make line
669 COPY is being deprecated. The 20010530 change was reverted, as
670 it causes far more pain than was expected, and to always compare
671 before installing, please use INSTALL="install -C" again. The
672 -C option is now silently ignored when used with the -d option.
675 Problems with libc_r clients like KDE and GNOME have been resolved.
676 There are still some minor problems with some signals but the
677 system is stable enough for general use again. SMP is less so than UP
678 but each can successfully complete multiple buildworlds.
679 Libkvm needs to be recompiled due to KSE.
682 Now would be a bad time to upgrade. Something in or near the
683 KSE commit totally broke programs using libc_r like KDE and
687 The k5su utility installed as part of Kerberos 5 is no longer
688 installed with the set-user-ID bit set by default. Add
689 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
690 with the set-user-ID bit set.
693 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
694 Unfortunately our native GDB (at version 4.18) does not understand
695 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
696 generated debugging information for our native GDB.
699 Due to the way CVS works, it may not properly update src/contrib/gcc
700 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
701 and then do a cvs update.
704 When exec'ing set[ug]id executables, the kernel now ensures that the
705 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
708 New sendmail startup scripts have been installed to make it
709 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
710 variable sendmail_enable to "NO" no longer prevents any sendmail
711 daemons from starting. Instead, either set sendmail_enable to
712 "NONE" or change mta_start_script to a script for starting
713 an alternative MTA. Setting mta_start_script to "" will
714 also prevent any MTA from being started at boot.
717 UCONSOLE is no longer a valid kernel option.
720 FreeBSD 5.0 DP-1 was basically branched today.
723 Warnings are now errors in the kernel. Unless you are a developer,
724 you should add -DNO_WERROR to your make line.
727 sendmail 8.12.2 has been imported. The sendmail binary is no
728 longer a set-user-ID root binary and the infrastructure to support
729 command line mail submission has changed. Be sure to run
730 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
731 and /etc/mail) and read /etc/mail/README for more details.
733 Due to the import of sendmail 8.12.2, a new user and group are
734 required in order for sendmail to run as a set-group-ID
735 binary. A 'make installworld' will use the new user and group
736 to set the owner and group of /var/spool/clientmqueue and will
737 fail if the new user and group do not exist. The 'smmsp' user
738 and group must be merged from src/etc/group and
739 src/etc/master.passwd before using 'make installworld'.
740 'mergemaster -p' will do this. You may need to install
741 mergemaster before this will work if you are updating from a
742 very old version of current. The updating recipe has changed
746 The preferred configuration method for PAM is now /etc/pam.d/
747 rather than /etc/pam.conf. If you have an unmodified
748 pam.conf, just delete it after your next mergemaster run. If
749 you have local modifications, you can use
750 /usr/src/etc/pam.d/convert.pl to incorporate them into your
753 Please see the following url for more details:
754 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
756 If anyone here is already using the new rc.conf(5) variable
757 networkfs_types, please note that it has changed
758 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
761 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
762 started out its life in the ISDN4BSD project as an offspring
763 from sys/net/if_spppsubr.c, which eventually got a life of its
764 own. All the accumulated features and bug fixes of the i4b
765 version have now been merged back into the base system's
766 version now. The only user-visible change resulting from this
767 is that i4b's sppp(4) interfaces are to be managed with
768 spppcontrol(8) again, since ispppcontrol(8) has been retired
769 as well. (There has never been rc file support for
770 ispppcontrol in -current, but only in -stable. That will be
771 reverted by the time the changes are MFCed.)
774 The fdc(4) driver has been updated and now automatically
775 recognizes media in `standard' formats (like 1440 KB and
776 720 KB for a 3.5" high-density drive) when accessing the
777 default device node (e. g. /dev/fd0). The old variety of
778 floppy device nodes /dev/fd*.* is no longer present by
779 default, devices can be created (in DEVFS) on demand. They
780 will need to be customized then for `odd' densities using
784 The bugs in procfs' debugging support code have been fixed,
785 and truss(1) now works again.
788 Daily security checks have been split out to use the periodic(8)
789 scripts. Some change in configuration may be necessary. Please
791 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
795 sos added VCD/SVCD support to ata driver and that needs the
796 kernel and burncd to be in sync.
799 The procfs pseudo-filesystem has now been converted to use the
800 pseudofs framework. If you have 'options PROCFS' in your
801 kernel config, you'll need to add 'options PSEUDOFS' if it's
804 This change temporarily breaks truss(1); use ktrace(1) instead
805 until the issue has been resolved.
808 A security hole in OpenSSH involving `UseLogin yes' has been
812 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
813 after this date. You need to do this only once.
816 Most of the awk issues have been resolved. Some rough
817 edges may be left, but for the most part things should be
818 back to "normal." For CURRENT's usual definition of "normal."
821 Awk has been upgraded to the one true awk from bell labs. Expect
822 choppy waves in the upgrade process.
825 The asr driver problem has been resolved.
828 Due to changes in other parts of the system, the asr driver
829 now causes the system to panic on boot. Do not use it pending
830 correction. Comment it out of any kernel config file that you
831 try to use from this date forward.
834 When crossbuilding, use TARGET=xxx where you used to use
835 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
836 unless you are changing both of them. To cross build pc98 on
837 an alpha, for example, you need to set TARGET=pc98 and
841 The kernel interface that burncd depends on has changed.
842 You must recompile both the kernel and userland applications
846 When crossbuilding, please set TARGET_ARCH rather than
847 MACHINE_ARCH to indicate the target. In the future, one will
848 set TARGET_MACHINE where you set MACHINE now. At the moment,
849 setting MACHINE alone for same MACHINE_ARCH machines works
850 (eg, you can build pc98 on an i386 machine and vice versa).
853 Some weird problems result from using ACPI on some machines.
854 To disable ACPI you can add
855 hint.acpi.0.disabled="1"
856 to /boot/loader.conf (or by putting set X=Y at the boot
859 Alternatively, you can remove it from /boot/kernel/acpi.ko
860 or use the MODULES_OVERRIDE function in your kernel config
861 file and not list acpi in that list.
864 The buildworld has been fixed. You may need to install
865 the 4.x compatibility libraries for some old binaries
866 to work. Add COMPAT4X=true to your /etc/make.conf to
867 get them installed on every installworld, or execute the
868 following to get them installed only once:
869 cd src/lib/compat/compat4x.<arch>
871 You will see ``__stdoutp undefined'' until you do this.
874 There's a bug in the world build process. The cross-tools
875 are build with the NEW headers, but the OLD libc.a. This
876 leads to all kinds of problems with the new libc. A temporary
878 CFLAGS="-O -pipe -D_OLD_STDIO"
879 before building world when upgrading from 4.x to current. This
880 can be removed afterwards.
882 A proper fix to the buildworld target is needed.
885 Peter has committed his new kthread nfs client/server code.
886 NFS may be unstable after this date.
889 KSE has hit the tree. Lots of things are now different in
890 the kernel. While a few problems were introduced in the
891 initial commit, most of the major ones have been found and
895 In OLDCARD, CardBus bridges appear to be stable. The work
896 arounds described in the 20010604 entry are now no longer
897 necessary and will be ignored. Most insert/remove problems
898 have been rectified around this date.
901 named now runs as user bind and group bind rather than as
902 root. If named_enable is set to YES in /etc/rc.conf, ensure
903 that user bind is available in /etc/passwd (using vipw(8))
904 and that group bind is available in /etc/group. Also make
905 sure that user or group bind has read (and not write)
906 permission for your name server configuration and that it
907 has read and write permission for your slave zone files and
910 If you wish to continue to run named as root (a less secure
911 alternative), add a line to /etc/rc.conf saying
916 The PAM libraries have had an API upgrade that is beyond
917 the ability of the shared library major number to handle.
918 It is manifested by PAM-using ports dumping core. The
919 solution is to rebuild those ports.
922 The kernel compile module has moved from src/sys/compile/FOO
923 to src/sys/${MACHINE}/compile/FOO.
926 The pccard modem issue from 20010613 has been corrected.
927 OLDCARD support is still a little weak in -current. slot 1 is
928 known not to work on some TI based cardbus bridges. Some
929 cardbus bridges do not properly detect insert/removal events.
930 IRQ configuration needs more safety belts.
933 Softupdates problems have been corrected.
936 Peter ripped out the linkerset support. You must, as always,
937 rerun config after you cvsup if you are using the traditional
938 kernel building methods.
941 pccard modems may not work with current after 20010604 date. Some
942 do, others result in panics. *MAKE*SURE* that you update your
943 config and /etc/rc.conf ala the 20010604 entry, or you will have
944 problems (this issue will be fixed, it just hasn't been yet).
947 SOFTUPDATES seem to be broken since the middle of May or so. Do not
948 use them in current. You can disable softupdates on all mounted
949 partitions, or remove SOFTUPDATES the kernel config file.
952 After Peter's commits to the hints code, people have been noticing
953 that certain devices are attached (or try to) twice. This is due
954 to having both static hints as well as a /boot/device.hints. To
955 work around this issue, please use only one or the other mechanism
956 until this bug is fixed.
958 Please note that a feature of config is that if you have config
959 file FOO and FOO.hints, it automatically adds FOO.hints to the
960 hints.c file, whether you want it to or not.
963 Locale names have changed to match other systems better.
966 pccard support for pci cards has been committed. You must change
967 your /etc/pccard.conf irq lines. It must match the irq used by
968 pcic device. Interrupt storms may result if you fail to do this.
969 Interrupt storms look a lot like a hang.
971 You must also install a new pccardd, otherwise you will get an
972 interrupt storm at card reset time (just after it tells you what
975 pccardd_flags="-I" is necessary for the time being. It tells pccardd
976 not to ask the kernel if the interrupt is really free or not before
977 using it. You can either change the /etc/pccard.conf irq lines to
978 match pcic, or add "-i X" to the pccardd_flags.
981 INSTALL=install -C is being deprecated. If you want to do this,
982 use COPY=-C instead. The former method will be supported for only
983 a limited time. If you see
985 install: warning: the -d and -C options may not be specified together
987 in your makeworld, then you need to migrate towards using
991 It appears that vm is now stable enough to use again. However,
992 there may be other problems, so caution is still urged. alpha
993 definitely is in bad shape.
996 Minor repo damage has happened. This may cause problems
997 with cvsup of ports. If you get errors, please see
998 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
999 at the bottom for details on a workaround. The error message
1001 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
1004 Vm and/or swapping are busted on -current. Please be patient.
1007 pccard has had much reorganizational work done to it over
1008 the past few days. Everything should still work, but if
1009 not, please contact imp@freebsd.org.
1012 ata ioctl changed. Make sure to recompile both kernel and
1013 userland at the same time.
1016 New ncurses imported.
1019 DEVFS is now opt out, not opt in. Barring major problems, this
1020 will be the only way to go starting July 1.
1023 OpenSSH has been updated to 2.9. Some defaults are different,
1024 including RhostsRSAAuthentication, which changes from yes to no.
1027 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
1030 Building perl was broken at 02:25:25 PDT.
1033 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
1034 go back in the water.
1037 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
1038 this date, but before the correction date.
1041 old fsck and new kernel interactions appear to have been fixed.
1044 fsck and the kernel were changed to handle some optimizations
1045 to directory layout. This breaks backward compatibility.
1046 Update only if you understand that you must not use the old
1047 fsck with the new kernel ever.
1050 fsck has changed the meaning of the pass column in /etc/fstab.
1051 Please see the cvs commit to fsck.8 or the fsck.8 man page for
1052 details. It is unclear if changes to /etc/fstab are necessary.
1055 portmap had changed name to rpcbind for maximum POLA in your
1056 current world. /etc/hosts.{allow,deny} needs changes. nfs and
1057 other rpc based programs that rely on portmapper will not work
1058 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
1061 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
1062 and ATA_ENABLE_TAGS are no longer kernel options. They have
1063 been replaced by tunables. See ata.4 for details.
1066 The fxp driver was converted to use miibus. If you compile
1067 fxp into your kernel statically, you will need to add miibus.
1070 The wi device now defaults to BSS (infrastructure) mode
1074 /dev/urandom should be a symbolic link to /dev/random now.
1075 Users of current not using DEVFS need to run MAKEDEV std.
1076 ssh might not work if you don't.
1079 The ed driver has been updated. It now allows mii attachments,
1080 which means that you must include the miibus in your kernel if
1081 you use the ed driver.
1084 The problems with libc have been corrected. It is now mostly
1085 safe to go back into the water.
1088 The size of FILE was changed. This breaks upgrading. If
1089 you must upgrade, be prepared for pain. It also breaks almost
1090 all binaries that you've compiled on -current. You are warned
1091 that before upgrading would be a good time to do a level 0
1092 dump of your system. No, really, I mean it this time.
1094 To get to the new system, you'll need to use the following
1095 workaround. Hopefully this can be sorted out so that we
1096 don't have to move this to the updating section.
1098 To get around the installworld problem, do:
1099 # cd /usr/src/usr.bin/sed
1103 If that doesn't work, then try:
1104 # make -k installworld
1108 DEVFS is now the default. If you use vinum, make sure that you
1109 do not include devfs in your kernel as problems result.
1112 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
1113 Remove them from your config.
1116 ****************************** WARNING ******************************
1117 buildkernel has been changed slightly
1118 ****************************** WARNING ******************************
1119 KERNCONF replaces the variable KERNEL for buildkernel. You
1120 should update your scripts and make.conf accordingly.
1123 config has changed to allow DEV_FOO as a replacement for NFOO.
1124 This requires a new config to build correctly.
1127 The kernel option I386_CPU is now mutually exclusive with the
1128 other cpu types. If you have an i386 system, be sure that it
1129 only had this line. Remove it for all other configurations.
1132 Changes to the kernel require it and burncd be in sync.
1135 Everyone who has hw.sndunit set to something in
1136 /etc/sysctl.conf, it is now hw.snd.unit.
1139 ex and vi were broken by some changes to sys/queue.h. If you
1140 have a bad vi, you will see make buildworld fail with a core
1141 dump while building termcap. You can work around this problem
1142 by adding -k to your make buildworld. This will cause the
1143 build to complete and install a new vi. Once that's done, you
1144 can rebuild again without the -k to pick up anything that
1145 might have been ignored by the -k option.
1147 Others have suggested that you can just rebuild libc if your
1148 vi/ex is dynamically linked, but I've not received any reports
1152 There have been some changes to libcrypt in -current. The
1153 libscrypt/libdescrypt symlink silliness is gone and the installed
1154 libcrypt is fully functional. Be aware of this.
1157 Linksys Fast Ethernet PCCARD cards supported by the ed driver
1158 now require the addition of flag 0x80000 to their config line
1159 in pccard.conf(5). This flag is not optional. These Linksys
1160 cards will not be recognized without it.
1163 Important new FreeBSD-version stuff: PAM support has been worked
1164 in, partially from the "Unix" OpenSSH version. This requires
1165 adding the following in pam.conf:
1167 sshd auth sufficient pam_skey.so
1168 sshd auth required pam_unix.so try_first_pass
1169 sshd session required pam_permit.so
1172 cvs updated to 1.11.
1175 The random device needs more entropy, so you need to make sure
1176 that you've run mergemaster to get a /etc/rc which will seed
1177 /dev/random. If you don't and the system hangs after ldconfig,
1178 then banging on the keyboard randomly until it unhangs is one
1182 ****************************** WARNING ******************************
1183 Sendmail has been updated.
1184 ****************************** WARNING ******************************
1185 o mail.local(8) is no longer installed as a set-user-id binary.
1186 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1188 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1190 o Now using sendmail's version of vacation(1).
1191 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1192 in /usr/share/sendmail/cf.
1193 o sendmail.cw changed to local-host-names
1195 More details can be found at
1196 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1199 The ports tree's new layout is in place. Be sure to update
1200 your entire ports tree, or you will have problems.
1203 The perl build procedure no longer installs miniperl, nor uses
1204 the installed miniperl. It is recommended that you delete
1208 This weekend the ports tree will be updated to a new layout.
1209 It will be in an inconsistent state until noted in the UPDATING
1210 file, or with asami-san's message to the relevant mailing
1211 lists. With this new layout, you'll need to update the whole
1212 tree for anything to work.
1215 There was a change in the passwd format. Need more information.
1218 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1219 place. Please update boot loader (not the boot blocks) at the
1220 same time as your kernel.
1223 The new pmtimer device is necessary for laptops. Failure to
1224 include the device will cause suspended laptops losing time
1225 when they resume. Include
1227 in your config file and
1228 hint.pmtimer.0.at="isa"
1229 to your /boot/device.hints file.
1232 The random device has been turned into a (pseudo-)device,
1233 rather than an option. The supplied kernel config files have
1234 been updated. You will need to do something similar in your
1235 own kernel config file.
1240 If you prefer to load the loadable module, you need to do
1244 The random device module has been renamed from randomdev.ko to
1245 random.ko. You will need to edit your /boot/loader.conf to
1246 reflect this if you load this module at boot time.
1247 The line should read:
1251 The SMPNG commit has happened. It should work, but if it
1252 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1253 to be a variety of minor issues. Please see 20000905 to make
1254 sure you don't have model loading problems which might at
1255 first blush appear related to SMP.
1258 nsswitch has been imported from NetBSD. Among other things,
1259 this means that /etc/host.conf is no longer used. See
1260 nsswitch.conf(5) instead. Note that at boot time rc.network
1261 will attempt to produce a new nsswitch.conf file for you if you
1262 don't have one, and you have host.conf.
1265 The ucred structure changed size. This breaks the interface
1266 that mountd uses. Trying to use an older mountd with a newer
1267 kernel guarantees a panic. This means that you need to use
1268 kernels newer than today only with matching mountd, but you
1269 needed to do that anyway with the boot loader changes.
1272 The boot loader has been updated. The new default kernel is
1273 now /boot/kernel/kernel.ko. The new default module location
1276 You *MUST* upgrade your boot loader and kernel at the same time.
1277 The easiest way to do this is to do the buildworld/buildkernel/
1278 installkernel/installworld dance.
1280 Furthermore, you are urged to delete your old /modules directory
1281 before booting the new kernel, since kldload will find stale
1282 modules in that directory instead of finding them in the correct
1283 path, /boot/kernel. The most common complaint that this cures
1284 is that the linux module crashes your machine after the update.
1286 if [ ! -d /boot/kernel.old ]; then
1287 mv /modules.old /boot/kernel.old
1288 chflags noschg /kernel.old
1289 mv /kernel.old /boot/kernel.old/kernel.ko
1290 chflags schg /boot/kernel.old/kernel.ko
1294 A new issue with the sendmail upgrade has come to light.
1295 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1296 incorrectly install the default aliases in /etc/mail rather than
1297 move the old one from /etc. So you'll need to manually move the
1298 file, create a symbolic link, remove the old /etc/aliases.db and
1299 run newaliases. For safety sake, you should stop sendmail
1300 while doing this and run the upgrade when locally sourced email
1301 is not likely to be generated.
1304 /boot/device.hints is now required for installkernel to
1305 succeed. You should copy GENERIC.hints for your architecture
1306 into /boot/device.hints. If and only if you compile hints
1307 into your kernel, then this file may be empty. Please note,
1308 if you have an empty or missing /boot/device.hints file and
1309 you neglected to compile hints into your kernel, no boot
1310 messages will appear after the boot loader tries to start the
1314 If you do NOT have ``options RANDOMDEV'' in your kernel and
1315 you DO want the random device then add randomdev_load="YES" to
1319 suidperl is now always built and installed on the system, but
1320 with permissions of 511. If you have applications that use
1321 this program, you are now required to add ENABLE_SUIDPERL=true
1322 to /etc/make.conf. If you forget to do this,
1323 chmod 4511 /usr/bin/suidperl
1324 will fix this until the next build.
1327 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1328 visible changes that may immediately affect your configuration
1330 - New default file locations from src/contrib/sendmail/cf/README
1331 - newaliases limited to root and trusted users
1332 - MSA port (587) turned on by default
1333 - New queue file naming system so can't go from 8.11 -> 8.9
1334 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1335 - FEATURE(`nullclient') is more full featured
1336 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1337 - mail.local FreeBSD-only -b option changed to -B
1338 - See src/contrib/sendmail/RELEASE_NOTES for more info
1341 suidperl (aka sperl) is no longer build by default. You must
1342 specifically define BUILD_SUIDPERL to "true" for it to be build.
1343 Furthermore, we recommend that you remove /usr/bin/sperl* and
1344 /usr/bin/suidperl files from your system unless you have a
1345 specific use for it.
1348 Networking defaults have been tightened. Anybody upgrading
1349 /etc/defaults/rc.conf needs to add the following lines to
1350 /etc/rc.conf if they want to have the same setup
1351 afterwards (unless the variables already are set, of course):
1352 # Enable network daemons for user convenience.
1354 portmap_enable="YES"
1355 sendmail_enable="YES"
1358 If you have null_load="YES" in your /boot/loader.conf, you
1359 will need to change that to nullfs_load="YES".
1362 The "installkernel" target has changed slightly. Now even if
1363 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1364 it will install the MYKERNEL file (built with the buildkernel
1365 target) as /kernel rather than /MYKERNEL. Those who have
1366 updated their /boot/loader.conf files to point to /MYKERNEL
1367 should remove that entry or perform manual rename of /kernel
1371 If you use CVSUP or CTM to get CVS trees, AND you used to get
1372 the old crypto files from internat.freebsd.org AND you check
1373 out files from the CVS tree with the cvs command, please read
1374 http://people.freebsd.org/~imp/internat.txt
1375 for details on potential problems that you might have and how
1378 If you are merely a mirror, or don't answer yes to each of the
1379 clauses above, you needn't worry.
1382 /etc/security has been updated to print the inode number of
1383 setuid programs that have changed. You will see a large spike
1384 in the number of changed programs the first time when you run
1385 mergemaster to get a new /etc/security.
1388 /dev/random now has good entropy collection (from the keyboard
1389 and sysmouse drivers). Please ensure that either `options
1390 RANDOMDEV' is present in your kernel config file or that
1391 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1392 not have the /dev/random driver, OpenSSL (and consequently
1393 lots of crypto tools (like SSH)) will fail with strange
1394 errors. (see below, 20000624).
1396 FreeBSD-current is safe again to run Crypto.
1399 phk made the malloc default options AJ. This may slow things
1400 down and uncover other latent bugs in the code. If you need to
1401 run at full speed, you can disable this by doing the following:
1402 ln -s aj /etc/malloc.conf
1405 libftpio's version was accidentally bumped a few days ago. This
1406 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1407 before doing your next buildworld/installworld pair. It certainly
1408 won't hurt to remove it before the update procedure. It will
1409 break fetch until a new one is built, but ftp can be used in the
1413 The crypto packages have changed for the cvsup. This has been done
1414 in a backward compatible way, but the old packages will go away at
1415 some point in the future. Look at /usr/share/examples/cvsup for
1419 With the new sys/modules/sound/drivers/*, you will need to
1420 set SYSDIR until you do an installworld after July 7th.
1423 rc.shutdown and rc will now call the rc.d scripts with start
1424 or stop. This may cause some harmless warnings from older
1425 rc.d scripts that haven't been updated.
1428 The libfetch based version of fetch has gone into the tree.
1429 Minor problems may result on some of the less popular sites,
1430 which should be reported to des@freebsd.org.
1433 From approximately this date forward, one must have the crypto
1434 system installed in order to build the system and kernel.
1435 While not technically strictly true, one should treat it as
1436 required and grab the crypto bits. If you are grabbing CVS
1437 trees, src-all and cvs-crypto should be treated as if they
1438 were required. You should check with the latest collections
1439 to make sure that these haven't changed.
1442 Mark Murray just committed the first parts of a cleanup of
1443 /dev/zero, et al. This is also cleaning up /dev/random.
1444 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1445 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1446 until Mark can merge in the fixes to this work in progress.
1447 openssh and openssl should not be used to generate keys from this
1448 date to the completion of the work.
1450 If you must operate at this reduced level of security, add '
1451 options RANDOMDEV' to your kernel or modload the randomdev
1452 module. You may also need to copy a new MAKEDEV to /dev and
1453 recreate the random and urandom devices.
1456 The license on the softupdates is now a standard 2 clause
1457 BSD license. You may need to remove your symbolic links
1458 that used to be required when updating.
1461 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1462 the config file update procedure.
1463 http://people.freebsd.org/~imp/config-upd.html
1464 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1465 isn't buildable. However, you can generate a LINT file:
1466 cd /sys/<ARCH>/conf && make LINT
1469 Binutils 2.10 have hit the tree, or will shortly. As soon
1470 as they do, the problem noted in 20000522 will be resolved and
1471 that workaround will no longer be required.
1474 phk removed the compatibility creation of wd devices in the
1475 ad driver. If you haven't done so already, you must update
1476 your fstab, etc to use the ad devices instead of the wd
1479 In addition, you'll need to update your boot blocks to a
1480 more modern version, if you haven't already done so. Modern
1481 here means 4.0 release or newer (although older releases
1485 Peter took an axe to config(8). Be sure that you read his mail
1486 on the topic before even thinking about updating. You will
1487 need to create a /boot/device.hints or add a hints directive
1488 to your config file to compile them in statically. The format
1489 of the config file has changed as well. Please see GENERIC or
1490 NEWCARD for examples of the new format.
1492 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1493 says that it has been fixed, assume that must use the hints mechanism
1494 in the loader if you need to use a machine with very old ISA cards
1498 A new set of binutils went into the tree today. Anybody
1499 building a kernel after this point is advised that they need
1500 to rebuild their binutils (or better yet do a
1501 buildworld/installworld) before building a new kernel.
1503 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1504 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1505 is recommended that you don't set this option until the problem
1509 The ethernet drivers were all updated to clean up the BPF handling.
1512 The problems with boot blocks on the alphas have been corrected.
1513 This will require some care in updating alphas. A new libstand
1514 is requires for the boot blocks to build properly.
1517 Recompile all kld modules. Proper version dependency info
1521 Modules have been disconnected from the buildworld tree and
1522 connected to the kernel building instead.
1525 You may need to build gperf
1526 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1527 when upgrading from 4.0 -> current. The build system now uses
1528 an option only in -current.
1531 The method that we brand ELF binaries has changed to be more
1532 acceptable to the binutils maintainers. You will need to
1533 rebrand your ELF binaries that aren't native. One problem
1534 binary is the Linux ldconfig. After your make world, but
1535 before you reboot, you'll need to issue:
1536 brandelf -t Linux /compat/linux/sbin/ldconfig
1537 if you have Linux compatibility enabled on your machine.
1540 If you have really bad/marginal IDE drives, you may find they
1541 don't work well. Use pio mode instead. The easiest way to
1542 cope if you have a problem combination is to add:
1543 /sbin/sysctl hw.ata.ata_dma=0
1544 to the start of /etc/rc.conf.
1547 The ISA and PCI compatibility shims have been connected to the
1548 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1549 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1550 include the appropriate option in your kernel config. Drivers
1551 using the shims should be updated or they won't ship with
1552 5.0-RELEASE, targeted for 2001.
1555 We've entered the traditional post release dumping party.
1556 Large kernel changes are being committed and are in the
1557 works. It is important to keep the systems' klds and kernel
1558 in sync as kernel interfaces and structures are changing.
1559 Before reporting kernel panics, make sure that all modules
1560 that you are loading are up to date.
1563 If you are upgrading from an older version of FreeBSD, you
1564 need to update your boot blocks as well. 'disklabel -B ad0'
1565 will do the trick. This isn't critical until you remove your
1566 wd device entries in /dev, at which point your system will not
1570 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1571 to upgrade to 4.0 from 3.x.
1575 # NOTE: 5.x below applies to 6.0-currrent as well, for the
1576 # momemnt. 4.any -> 5.any upgrade support will remain in
1577 # place for 6.0 current, but after 5.3 RELEASE, the 4.any ->
1578 # 6.0-current upgrade path will require moving through 5.3
1583 Avoid using make -j when upgrading. From time to time in the
1584 past there have been problems using -j with buildworld and/or
1585 installworld. This is especially true when upgrading between
1586 "distant" versions (eg one that cross a major release boundary
1587 or several minor releases, or when several months have passed
1588 on the -current branch).
1590 Sometimes, obscure build problems are the result of environment
1591 poisoning. This can happen because the make utility reads its
1592 environment when searching for values for global variables.
1593 To run your build attempts in an "environmental clean room",
1594 prefix all make commands with 'env -i '. See the env(1) manual
1595 page for more details.
1599 If you are updating from a prior version of FreeBSD (even one just
1600 a few days old), you should follow this procedure. With a
1601 /usr/obj tree with a fresh buildworld,
1602 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1603 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1605 To just build a kernel when you know that it won't mess you up
1606 --------------------------------------------------------------
1607 This assumes you are already running a 5.X system. Replace
1608 ${arch} with the architecture of your machine (e.g. "i386",
1609 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1611 cd src/sys/${arch}/conf
1612 config KERNEL_NAME_HERE
1613 cd ../compile/KERNEL_NAME_HERE
1618 If this fails, go to the "To build a kernel" section.
1620 To rebuild everything and install it on the current system.
1621 -----------------------------------------------------------
1622 # Note: sometimes if you are running current you gotta do more than
1623 # is listed here if you are upgrading from a really old current.
1625 <make sure you have good level 0 dumps>
1626 <maybe fix /etc/fstab> [7]
1628 make kernel KERNCONF=YOUR_KERNEL_HERE
1630 <reboot in single user> [3]
1631 src/etc/rc.d/preseedrandom [10]
1638 To cross-install current onto a separate partition
1639 --------------------------------------------------
1640 # In this approach we use a separate partition to hold
1641 # current's root, 'usr', and 'var' directories. A partition
1642 # holding "/", "/usr" and "/var" should be about 2GB in
1645 <make sure you have good level 0 dumps>
1648 <maybe newfs current's root partition>
1649 <mount current's root partition on directory ${CURRENT_ROOT}>
1650 make installworld DESTDIR=${CURRENT_ROOT}
1651 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1652 cp src/sys/${ARCH}/conf/GENERIC.hints \
1653 ${CURRENT_ROOT}/boot/device.hints # as needed
1654 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1655 cd src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1656 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1657 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1658 <reboot into current>
1659 <do a "native" rebuild/install as described in the previous section>
1660 <maybe install compatibility libraries from src/lib/compat>
1664 To upgrade in-place from 4.x-stable to current
1665 ----------------------------------------------
1666 # 5.x uses more space than 4.x. Also, the location of kernel
1667 # modules has changed. If you are installing 5.0 onto a 4.x
1668 # system, you'll need about 30MB of free disk space on your /
1669 # partition. If you have less than this, you may encounter difficult
1670 # to back out of problems with this procedure. If /tmp is on
1671 # the / partition, you may want to completely remove all its content
1672 # before upgrading, as this can be a common source of shortage of
1675 <make sure you have good level 0 dumps>
1676 <maybe fix /etc/fstab> [7]
1678 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1679 cp sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1680 make installkernel KERNCONF=YOUR_KERNEL_HERE
1681 cd sys/boot ; make STRIP="" install [6]
1683 <reboot in single user> [3]
1684 src/etc/rc.d/preseedrandom [10]
1686 rm -rf /usr/include/g++
1691 Make sure that you've read the UPDATING file to understand the
1692 tweaks to various things you need. At this point in the life
1693 cycle of current, things change often and you are on your own
1694 to cope. The defaults can also change, so please read ALL of
1695 the UPDATING entries.
1697 Also, if you are tracking -current, you must be subscribed to
1698 freebsd-current@freebsd.org. Make sure that before you update
1699 your sources that you have read and understood all the recent
1700 messages there. If in doubt, please track -stable which has
1701 much fewer pitfalls.
1703 [1] If you have third party modules, such as vmware, you
1704 should disable them at this point so they don't crash your
1707 [2] If you have legacy ISA devices, you may need to create
1708 your own device.hints to reflect your unique hardware
1711 [3] From the bootblocks, boot -s, and then do
1716 adjkerntz -i # if CMOS is wall time
1717 Also, when doing a major release upgrade, it is required that
1718 you boot into single user mode to do the installworld.
1719 For the 4.x -> 5.x upgrade, you will also see many messages about
1720 needing to recompile your userland. These are harmless and can
1721 be ignored while you proceed to the next step.
1723 [4] Note: This step is non-optional. Failure to do this step
1724 can result in a significant reduction in the functionality of the
1725 system. Attempting to do it by hand is not recommended and those
1726 that pursue this avenue should read this file carefully, as well
1727 as the archives of freebsd-current and freebsd-hackers mailing lists
1728 for potential gotchas.
1730 [5] Usually this step is a noop. However, from time to time
1731 you may need to do this if you get unknown user in the following
1732 step. It never hurts to do it all the time. You may need to
1733 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1734 install) after the buildworld before this step if you last updated
1735 from current before 20020224 or from -stable before 20020408.
1737 [6] 4.x boot loader can be used to boot a 5.x system, however
1738 it is difficult to do that at best. If you wish to try, then
1739 you should interrupt the boot and at the ok prompt type:
1741 ok boot /boot/kernel/kernel
1742 If this fails to work, you must install a new boot loader as
1745 [7] Before you upgrade, please make sure that you are not using
1746 compatibility slices. These are device names of the form, on i386
1747 and other architectures that use MBR slicing, /dev/ad0a without the
1748 actual slice name. Chances are excellent that these will break.
1749 You generally must update these entries to use the post FreeBSD
1750 2.x form of /dev/ad0s1a.
1752 [8] In order to have a kernel that can run the 4.x binaries
1753 needed to do an installworld, you must include the COMPAT_FREEBSD4
1754 option in your kernel. Failure to do so may leave you with a system
1755 that is hard to boot to recover.
1757 [9] When checking out sources, you must include the -P flag to have
1758 cvs prune empty directories. Also, if CPUTYPE is defined in your
1759 /etc/make.conf, make sure to use the "?=" instead of the "=" assignment
1760 operator, so that buildworld can override the CPUTYPE if it needs to.
1761 In case you would like to avoid installing new packages of everything,
1762 you might want to uncomment the "COMPAT4X= YES" entry, so that 4.x
1763 compatibility libraries are built which should allow you to continue
1764 using your existing software for a while.
1766 [10] In order to create temporary files, /dev/random must be
1767 initialized by feeding data into it. src/etc/rc.d/preseedrandom
1771 This file contains a list, in reverse chronological order, of major
1772 breakages in tracking -current. Not all things will be listed here,
1773 and it only starts on March 15, 2000. Updating files can found in
1774 previous releases if your system is older than this.
1776 Copyright information:
1778 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1780 Redistribution, publication, translation and use, with or without
1781 modification, in full or in part, in any form or format of this
1782 document are permitted without further permission from the author.
1784 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1785 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1786 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1787 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1788 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1789 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1790 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1791 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1792 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1793 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1794 POSSIBILITY OF SUCH DAMAGE.
1796 If you find this document useful, and you want to, you may buy the
1799 Contact Warner Losh if you have any questions about your use of