1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 NOTE TO PEOPLE WHO THINK THAT FreeBSD 5.x IS SLOW:
8 FreeBSD 5.x has many debugging features turned on, in
9 both the kernel and userland. These features attempt to detect
10 incorrect use of system primitives, and encourage loud failure
11 through extra sanity checking and fail stop semantics. They
12 also substantially impact system performance. If you want to
13 do performance measurement, benchmarking, and optimization,
14 you'll want to turn them off. This includes various WITNESS-
15 related kernel options, INVARIANTS, malloc debugging flags
16 in userland, and various verbose features in the kernel. Many
17 developers choose to disable these features on build machines
18 to maximize performance.
21 The PCI bus power state stuff has been turned on. If this causes
22 problems for your system, please disable it using the tunable
23 hw.pci.do_powerstate=0.
26 The bulk of the pci problems have been fixed, although the floppy
27 drive is still broken.
30 A substantial update to the pci bus resource and power management
31 have been committed. Expect a bumpy ride for a few days until
32 the unanticipated problems have been resolved.
35 Due to changes in the the Yarrow initialization process,
36 /dev/random needs to be fed before operations requiring
37 temp files can succeed in single user mode. This includes
38 running "make installworld". /dev/random may be fed by running
39 "/etc/rc.d/initrandom start" or with 20040415 source by running
40 "/etc/rc.d/preseedrandom".
43 The debug.mpsafenet tunable controls whether the kernel Giant
44 lock is held across the lower levels of the network stack, and
45 by default is turned off. In the few days following 20040322,
46 the behavior of debug.mpsafenet will change such that this
47 tunable controls Giant over all levels of the network stack.
48 If you are currently setting debug.mpsafenet to 1, you should
49 set it back to 0 (the default) again during the change-over.
50 An additional note will be added to UPDATING when sufficient
51 locking is merged to permit this to take place.
54 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
55 64-bits. This is a very major incompatible change, so people
56 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
57 detailed instructions on how to make this upgrade. People
58 upgrading FreeBSD on other platforms can ignore this event.
61 The packet filter (pf) is now installed with the base system. Make
62 sure to run mergemaster -p before installworld to create required
63 user account ("proxy"). If you do not want to build pf with your
64 system you can use the NO_PF knob in make.conf.
65 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
66 pf system consists of the following three devices:
68 device pflog # optional
69 device pfsync # optional
72 If you are having trouble with the libc_r -> libpthread transition
73 (see the 20040130 entry), place the following lines at the top of
76 libc_r.so.5 libpthread.so.1
77 libc_r.so libpthread.so
79 This will cause all programs and libraries linked against libc_r
80 to use libpthread instead.
83 Some sshd configuration defaults have changed: protocol version 1
84 is no longer enabled by default, and password authentication is
85 disabled by default if PAM is enabled (which it is by default).
86 OpenSSH clients should not be affected by this; other clients may
87 have to be reconfigured, upgraded or replaced.
90 The ABIs defined in <resolv.h> and <netdb.h> have been updated
91 to support improved reentrancy. Multi-threaded programs that
92 reference the "_res" or "h_errno" symbols may experience some
93 problems if they are not recompiled. Single-threaded programs
94 should remain unaffected.
97 routed has been updated in the base system from the vendor
98 sources, routed v2.27, from rhyolite.com. This change means that
99 for users who use RIP's MD5 authentication feature, FreeBSD
100 -CURRENT's routed is now incompatible with previous versions
101 of FreeBSD; however it is now compatible with implementations
102 from Sun, Cisco and other vendors.
105 The tcpcb structure has changed and makes a recompile of libkvm
106 and related userland network utilities neccessary.
109 The cdevsw structure has changed in two externally visible ways.
110 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
111 Second, the d_version field must be filled in with D_VERSION.
112 Drivers outside the tree will need to be updated.
115 The /etc/rc.d/ttys script has been removed. It is no longer
116 necessary since devfs has been mandatory for some time.
119 libkse has been renamed back to libpthread and is now the
120 default threads library. The gcc -pthread option has also
121 been changed to link to libpthread instead of libc_r. For
122 alpha and sparc64 machines, libkse is not renamed and links
123 are installed so that libpthread points to libc_r. Until
124 the ports system is updated to handle this change, it is
125 recommended that folks install an /etc/libmap.conf(5) that
126 maps libc_r to libpthread. If you have any binaries or
127 libraries linked to libkse, then it is also recommended
128 that you map libkse to libpthread. Anyone that is using
129 nvidia supplied drivers and libraries should use a libmap.conf
130 that maps libpthread to libc_r since their drivers/libraries
131 do not work with libpthread.
134 ULE has entered into its probationary period as the default scheduler
135 in GENERIC. For the average user, interactivity is reported to be
136 better in many cases. On SMP machines ULE will be able to make more
137 efficient use of the available parallel resources. If you are not
138 running it now, please switch over, replacing the kernel option
139 SCHED_4BSD with SCHED_ULE.
142 Move LongRun support out of identcpu.c, where it hardly
143 belongs, into its own file and make it opt-in, not mandatory,
144 depending on CPU_ENABLE_LONGRUN config(8) option.
147 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
148 if the login process is unable to successfully set the
149 process credentials to include all groups defined for the
150 user. The current kernel limit is 16 groups; administrators
151 may wish to check that users do not have over 16 groups
152 defined, or they will be unable to log in.
155 The ACPI module has been reactivated. It is no longer required
156 to compile ACPI support into kernels statically.
159 The statfs structure has been updated with 64-bit fields to
160 allow accurate reporting of multi-terabyte filesystem
161 sizes. You should build world, then build and boot the new kernel
162 BEFORE doing a `installworld' as the new kernel will know about
163 binaries using the old statfs structure, but an old kernel will
164 not know about the new system calls that support the new statfs
166 Note that the backwards compatibility is only present when the
167 kernel is configured with the COMPAT_FREEBSD4 option. Since
168 even /bin/sh will not run with a new kernel without said option
169 you're pretty much dead in the water without it. Make sure you
170 have COMPAT_FREEBSD4!
171 Running an old kernel after a `make world' will cause programs
172 such as `df' that do a statfs system call to fail with a bad
173 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
174 that cfsd (ports/security/cfs) needs to be recompiled after
175 these changes are installed.
177 ****************************DANGER*******************************
179 DO NOT make installworld after the buildworld w/o building and
180 installing a new kernel FIRST. You will be unable to build a
181 new kernel otherwise on a system with new binaries and an old
185 Some netgraph string length constants have been changed. This
186 change requires the netgraph kernel modules and all netgraph
187 userland components to be in sync. Especially users who require
188 netgraph to boot need to make sure to have world and kernel in
189 sync before rebooting.
192 Hyperthreading logical CPU's are no longer probed by default
193 when using the MP Table. If ACPI is being used, then logical
194 CPUs will be probed if hyperthreading is enabled in the BIOS.
195 If ACPI is not being used and hyperthreading is enabled in the
196 BIOS, logical CPUs can be enabled by building a custom kernel
197 with the option MPTABLE_FORCE_HTT enabled.
200 The i386 APIC_IO kernel option has been replaced by
201 'device apic'. The ACPI module has also been temporarily
202 disabled, so ACPI must be statically compiled into your
203 kernel using 'device acpi' if you wish to use the ACPI driver.
206 The API and ABI of struct ifnet have been changed by removing
207 the if_name and if_unit members and replacing them with
208 if_xname, if_dname, and if_dunit. All network drivers and most
209 userland programs which include net/if_var.h must be updated
210 and recompiled. __FreeBSD_version has been bumped to 501113 to
214 Changes to the cdevsw default functions have been made to remove
215 the need to specify nullopen() and nullclose() explicitly.
216 __FreeBSD_version bumpted to 501110.
219 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
220 mount_cd9660(8) need to be in sync with kernel.
223 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
224 also be explicitly configured. Previously this dependency was
225 magically handled through some cruft in net/pfil.h; but that has
226 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
227 will fail with obtuse errors in ip_fil.c.
230 Fix a bug in arplookup(), whereby a hostile party on a locally
231 attached network could exhaust kernel memory, and cause a system
232 panic, by sending a flood of spoofed ARP requests. See
233 FreeBSD-SA-03:14.arp.
236 A change to /etc/defaults/rc.conf now causes inetd to be started
237 with `-C 60' if it is not overridden in /etc/rc.conf. This
238 causes inetd to stop accepting connections from an IP address
239 that exceeds the rate of 60 connections per minute.
242 The following rc.d scripts have been removed and should be
243 deleted from your installation: atm2.sh atm3.sh devdb
244 localdaemons network1 network2 network3. Depending on when
245 you last updated world and used mergemaster(8) you may or
246 may not have problems during the rc boot sequence. The simplest
247 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
248 The atm2.sh atm3.sh and devdb scripts were removed some time
249 ago, so depending on when you installed -CURRENT these scripts
250 may or may not exist on your system.
253 ATAng has been committed. You need to build world as sys/ata.h
254 has changed, and userland atacontrol depends on it.
255 If you use ATA SW raids you need "device ataraid" in your
256 kernel config file, as it is no longer pulled in automatically.
259 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
260 Among other things, this changes the device enumeration to be
261 closer to Solaris. Be aware that, this can even cause the machine
262 to not boot without manual intervention before the fstab is adjusted.
265 All current USB and Firewire quirks in da(4) have been deprecated
266 and will be removed for 5.2. If this causes failure for your
267 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
268 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
269 so the quirk can be re-enabled.
272 Problems with entry 20030714 have been corrected and no known issues
273 with /rescue and -j exist for host systems after this point in time.
276 FPU-less support has been removed from FreeBSD. Chances are you won't
277 notice. 386+387 support should still work after this change, but
278 it is now a minimum requirement for the i386 port that you have real
282 Some people are having problems with changes related to /rescue.
283 If you are building -j N, you will need to define NO_RESCUE. Others
284 will need to define it if /rescue has issues with their environment.
285 People should report those issues to current@.
288 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
289 across this point. Further, it might be a good idea to remove
293 Remove deprecated locale names and transition period code
294 for them, finishing switching to the new scheme. Check your
295 LANG environment variable.
298 CCD has been changed to be a fully GEOMified class. Kernel
299 and ccdconfig(8) needs to be in sync, this is particularly
300 important to remember beforehand if your source tree is on
301 a ccd device. Consider making a copy of the old ccdconfig
302 into /boot/kernel.good or wherever you keep your backup
306 There was a small window in which sed(1) was broken. If you
307 happen to have sed(1) installed during that window, which is
308 evidenced by an inability to build world with the failure
309 given below, you need to manually build and install sed(1)
310 (and only sed(1)) before doing anything else. This is a one-
311 time snafu. Typical failure mode:
313 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
314 targmatch.h:7:1: null character(s) ignored
315 targmatch.h:12:1: null character(s) ignored
316 targmatch.h:16:1: null character(s) ignored
319 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
320 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
321 usr.bin/sed/process.c).
324 Kerberos 5 (Heimdal) is now built by default. Setting
325 MAKE_KERBEROS5 no longer has any effect. If you do NOT
326 want the "base" Kerberos 5, you need to set NO_KERBEROS.
329 groff has been updated. If you try to do a buildworld and
330 get an infinite loop in troff, update to May 4th or newer. If you
331 have a newer kernel than userland, you may need to set the OSRELDATE
332 to 500110 in your environment before starting a buildworld.
335 The old rc system has been removed. Please report any problems
336 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
337 Your personal versions of these files will not be removed, so you can
338 continue to use them. However, you should take great care when updating,
339 especially when using mergemaster, since the compatibility code that
340 utilizes these old scripts has also been removed.
343 A bug has been fixed in /dev/devctl which would cause devd
344 to hang on boot, were it not for a workaround in devd. The
345 work around in devd will be removed around 20030507. You
346 have until then to upgrade your kernel before updating
347 userland. In general, you should have a userland and
348 kernel that's in sync with each other. However, given the
349 effects of this bug (hang on boot when starting devd), some
353 Alphas with libc from between 20030312 and 20030329 exhibit
354 floating point exceptions (FPEs), most notably in awk(1)
355 while upgrading the system through a buildworld.
357 So, to successfully upgrade your Alpha, you must either
358 downgrade your libc.so to a pre-20030312 version, or update
359 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
360 to CFLAGS, then forcibly rebuild and install libc:
362 cd /usr/src/lib/libc && \
363 make cleandir && make obj && \
364 make -DNOMAN -DNOPROFILE all && \
365 make -DNOMAN -DNOPROFILE install
368 sendmail 8.12.7 has been imported. It has one important
369 change for IPv6 users. The default submit.mc now uses
370 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
371 used to connect to the MTA. Users on IPv6-only machines
372 will need to edit /etc/mail/submit.mc appropriately.
375 NODEVFS option has been removed and DEVFS thereby made standard.
376 This makes all references to MAKEDEV obsolete, and they should
377 be removed when convenient.
380 The name of the device for the ofw console has changed, sparc64 users
381 must run mergemaster to update their installed /etc/ttys.
384 The scheduler framework has grown a second scheduler and consequently
385 you must specify one and only one scheduler in your kernel config.
386 The cvs config files have been updated to use the old scheduler
387 which may be selected via 'options SCHED_4BSD'. If you would like
388 to try the new, much more experimental, scheduler please try
389 'options SCHED_ULE' and contribute to the arch@ discussion.
392 A new version of the wi driver has been imported into the tree.
393 One now must have device wlan in the config file for it to operate
396 In addition, there have been some changes to how wi devices are
397 configured for point to point links to bring it more in line
398 with the former way of doing things, as well as compatibility
402 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
403 used an incompatible form of ABI for returning structures and unions
404 which FreeBSD's GCC maintainers were not aware of relative to previous
405 versions of FreeBSD. We have gone back to the ABI for now, and any
406 code compiled which is required to interoperate with other code (not
407 built at the same time) returning structs or unions should be
411 A name change in /etc/netconfig has been reverted to stay
412 compatible with suns TIRPC and also with NetBSD. You need
413 to run mergemaster after make world. A new libc does still work
414 with an outdated /etc/netconfig for some time, but you'll get
415 a warning. This warning will be removed in 20030301.
418 The recent binutils upgrade marks a kernel flag day on
419 sparc64: modules built with the old binutils will not work
420 with new kernels and vice versa. Mismatches will result in
421 panics. Make sure your kernel and modules are in sync.
424 The value of IPPROTO_DIVERT has changed. Make sure to keep
425 your kernel, netstat, natd and any third-party DIVERT
429 Old, compatibility slices have been removed in GEOM kernels.
430 This means that you will have to update your /etc/fstab to
431 not use disk devices of the form /dev/ad0a. Instead, you
432 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
433 partition really is on. The old device names have gone
434 away, so if you use them anywhere else, you must also adjust
435 those uses. (This doesn't affect the disks formatted in
436 the ``dangerously-dedicated'' mode.)
439 Alphas with kernels from between 20020830 and 20021023 and/or
440 rtld (ld-elf.so.1) older than 20021023 may experience problems
441 with groff while doing a buildworld (kernel: "out of memory",
442 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
443 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
445 So, to successfully upgrade your Alpha, you must either
446 upgrade your kernel and rtld first (which might be a bit
447 tricky), or avoid running the bootstrapped groff during the
448 "transitional" buildworld. To avoid running groff during the
449 transitional upgrade run make buildworld with -DNOMAN,
450 -DNO_SHAREDOCS, and -DNO_LPR.
453 gcc has been upgraded to 3.2. It is not all binary compatible
454 with earlier versions of gcc for c++ programs. All c++
455 programs and libraries need to be recompiled.
457 Also, if you encounter g++ issues, rm /usr/include/g++/* before
458 doing an installworld to make sure that stale files are removed.
461 Our /etc/termcap now has all the entries from the XFree86 xterm
462 almost unchanged. This means xterm now supports color by default.
463 If you used TERM=xterm-color in the past you now should use
464 TERM=xterm. (xterm-color will lead to benign warnings).
467 A "bug" in gcc(1) that was hiding warning in system headers was
468 fixed. It's probably time to add -DNO_WERROR to your make line
472 COPY is being deprecated. The 20010530 change was reverted, as
473 it causes far more pain than was expected, and to always compare
474 before installing, please use INSTALL="install -C" again. The
475 -C option is now silently ignored when used with the -d option.
478 Problems with libc_r clients like KDE and GNOME have been resolved.
479 There are still some minor problems with some signals but the
480 system is stable enough for general use again. SMP is less so than UP
481 but each can successfully complete multiple buildworlds.
482 Libkvm needs to be recompiled due to KSE.
485 Now would be a bad time to upgrade. Something in or near the
486 KSE commit totally broke programs using libc_r like KDE and
490 The k5su utility installed as part of Kerberos 5 is no longer
491 installed with the set-user-ID bit set by default. Add
492 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
493 with the set-user-ID bit set.
496 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
497 Unfortunately our native GDB (at version 4.18) does not understand
498 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
499 generated debugging information for our native GDB.
502 Due to the way CVS works, it may not properly update src/contrib/gcc
503 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
504 and then do a cvs update.
507 When exec'ing set[ug]id executables, the kernel now ensures that the
508 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
511 New sendmail startup scripts have been installed to make it
512 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
513 variable sendmail_enable to "NO" no longer prevents any sendmail
514 daemons from starting. Instead, either set sendmail_enable to
515 "NONE" or change mta_start_script to a script for starting
516 an alternative MTA. Setting mta_start_script to "" will
517 also prevent any MTA from being started at boot.
520 UCONSOLE is no longer a valid kernel option.
523 FreeBSD 5.0 DP-1 was basically branched today.
526 Warnings are now errors in the kernel. Unless you are a developer,
527 you should add -DNO_WERROR to your make line.
530 sendmail 8.12.2 has been imported. The sendmail binary is no
531 longer a set-user-ID root binary and the infrastructure to support
532 command line mail submission has changed. Be sure to run
533 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
534 and /etc/mail) and read /etc/mail/README for more details.
536 Due to the import of sendmail 8.12.2, a new user and group are
537 required in order for sendmail to run as a set-group-ID
538 binary. A 'make installworld' will use the new user and group
539 to set the owner and group of /var/spool/clientmqueue and will
540 fail if the new user and group do not exist. The 'smmsp' user
541 and group must be merged from src/etc/group and
542 src/etc/master.passwd before using 'make installworld'.
543 'mergemaster -p' will do this. You may need to install
544 mergemaster before this will work if you are updating from a
545 very old version of current. The updating recipe has changed
549 The preferred configuration method for PAM is now /etc/pam.d/
550 rather than /etc/pam.conf. If you have an unmodified
551 pam.conf, just delete it after your next mergemaster run. If
552 you have local modifications, you can use
553 /usr/src/etc/pam.d/convert.pl to incorporate them into your
556 Please see the following url for more details:
557 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
559 If anyone here is already using the new rc.conf(5) variable
560 networkfs_types, please note that it has changed
561 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
564 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
565 started out its life in the ISDN4BSD project as an offspring
566 from sys/net/if_spppsubr.c, which eventually got a life of its
567 own. All the accumulated features and bugfixes of the i4b
568 version have now been merged back into the base system's
569 version now. The only user-visible change resulting from this
570 is that i4b's sppp(4) interfaces are to be managed with
571 spppcontrol(8) again, since ispppcontrol(8) has been retired
572 as well. (There has never been rc file support for
573 ispppcontrol in -current, but only in -stable. That will be
574 reverted by the time the changes are MFCed.)
577 The fdc(4) driver has been updated and now automatically
578 recognizes media in `standard' formats (like 1440 KB and
579 720 KB for a 3.5" high-density drive) when accessing the
580 default device node (e. g. /dev/fd0). The old variety of
581 floppy device nodes /dev/fd*.* is no longer present by
582 default, devices can be created (in DEVFS) on demand. They
583 will need to be customized then for `odd' densities using
587 The bugs in procfs' debugging support code have been fixed,
588 and truss(1) now works again.
591 Daily security checks have been split out to use the periodic(8)
592 scripts. Some change in configuration may be necessary. Please
594 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
598 sos added VCD/SVCD support to ata driver and that needs the
599 kernel and burncd to be in sync.
602 The procfs pseudo-filesystem has now been converted to use the
603 pseudofs framework. If you have 'options PROCFS' in your
604 kernel config, you'll need to add 'options PSEUDOFS' if it's
607 This change temporarily breaks truss(1); use ktrace(1) instead
608 until the issue has been resolved.
611 A security hole in OpenSSH involving `UseLogin yes' has been
615 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
616 after this date. You need to do this only once.
619 Most of the awk issues have been resolved. Some rough
620 edges may be left, but for the most part things should be
621 back to "normal." For CURRENT's usual definition of "normal."
624 Awk has been upgraded to the one true awk from bell labs. Expect
625 choppy waves in the upgrade process.
628 The asr driver problem has been resolved.
631 Due to changes in other parts of the system, the asr driver
632 now causes the system to panic on boot. Do not use it pending
633 correction. Comment it out of any kernel config file that you
634 try to use from this date forward.
637 When crossbuilding, use TARGET=xxx where you used to use
638 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
639 unless you are changing both of them. To cross build pc98 on
640 an alpha, for example, you need to set TARGET=pc98 and
644 The kernel interface that burncd depends on has changed.
645 You must recompile both the kernel and userland applications
649 When crossbuilding, please set TARGET_ARCH rather than
650 MACHINE_ARCH to indicate the target. In the future, one will
651 set TARGET_MACHINE where you set MACHINE now. At the moment,
652 setting MACHINE alone for same MACHINE_ARCH machines works
653 (eg, you can build pc98 on an i386 machine and vice versa).
656 Some weird problems result from using ACPI on some machines.
657 To disable ACPI you can add
658 hint.acpi.0.disabled="1"
659 to /boot/loader.conf (or by putting set X=Y at the boot
662 Alternatively, you can remove it from /boot/kernel/acpi.ko
663 or use the MODULES_OVERRIDE function in your kernel config
664 file and not list acpi in that list.
667 The buildworld has been fixed. You may need to install
668 the 4.x compatibility libraries for some old binaries
669 to work. Add COMPAT4X=true to your /etc/make.conf to
670 get them installed on every installworld, or execute the
671 following to get them installed only once:
672 cd src/lib/compat/compat4x.<arch>
674 You will see ``__stdoutp undefined'' until you do this.
677 There's a bug in the world build process. The cross-tools
678 are build with the NEW headers, but the OLD libc.a. This
679 leads to all kinds of problems with the new libc. A temporary
681 CFLAGS="-O -pipe -D_OLD_STDIO"
682 before building world when upgrading from 4.x to current. This
683 can be removed afterwards.
685 A proper fix to the buildworld target is needed.
688 Peter has committed his new kthread nfs client/server code.
689 NFS may be unstable after this date.
692 KSE has hit the tree. Lots of things are now different in
693 the kernel. While a few problems were introduced in the
694 initial commit, most of the major ones have been found and
698 In OLDCARD, CardBus bridges appear to be stable. The work
699 arounds described in the 20010604 entry are now no longer
700 necessary and will be ignored. Most insert/remove problems
701 have been rectified around this date.
704 named now runs as user bind and group bind rather than as
705 root. If named_enable is set to YES in /etc/rc.conf, ensure
706 that user bind is available in /etc/passwd (using vipw(8))
707 and that group bind is available in /etc/group. Also make
708 sure that user or group bind has read (and not write)
709 permission for your name server configuration and that it
710 has read and write permission for your slave zone files and
713 If you wish to continue to run named as root (a less secure
714 alternative), add a line to /etc/rc.conf saying
719 The PAM libraries have had an API upgrade that is beyond
720 the ability of the shared library major number to handle.
721 It is manifested by PAM-using ports dumping core. The
722 solution is to rebuild those ports.
725 The kernel compile module has moved from src/sys/compile/FOO
726 to src/sys/${MACHINE}/compile/FOO.
729 The pccard modem issue from 20010613 has been corrected.
730 OLDCARD support is still a little weak in -current. slot 1 is
731 known not to work on some TI based cardbus bridges. Some
732 cardbus bridges do not properly detect insert/removal events.
733 IRQ configuration needs more safety belts.
736 Softupdates problems have been corrected.
739 Peter ripped out the linkerset support. You must, as always,
740 rerun config after you cvsup if you are using the traditional
741 kernel building methods.
744 pccard modems may not work with current after 20010604 date. Some
745 do, others result in panics. *MAKE*SURE* that you update your
746 config and /etc/rc.conf ala the 20010604 entry, or you will have
747 problems (this issue will be fixed, it just hasn't been yet).
750 SOFTUPDATES seem to be broken since the middle of May or so. Do not
751 use them in current. You can disable softupdates on all mounted
752 partitions, or remove SOFTUPDATES the kernel config file.
755 After Peter's commits to the hints code, people have been noticing
756 that certain devices are attached (or try to) twice. This is due
757 to having both static hints as well as a /boot/device.hints. To
758 work around this issue, please use only one or the other mechanism
759 until this bug is fixed.
761 Please note that a feature of config is that if you have config
762 file FOO and FOO.hints, it automatically adds FOO.hints to the
763 hints.c file, whether you want it to or not.
766 Locale names have changed to match other systems better.
769 pccard support for pci cards has been committed. You must change
770 your /etc/pccard.conf irq lines. It must match the irq used by
771 pcic device. Interrupt storms may result if you fail to do this.
772 Interrupt storms look a lot like a hang.
774 You must also install a new pccardd, otherwise you will get an
775 interrupt storm at card reset time (just after it tells you what
778 pccardd_flags="-I" is necessary for the time being. It tells pccardd
779 not to ask the kernel if the interrupt is really free or not before
780 using it. You can either change the /etc/pccard.conf irq lines to
781 match pcic, or add "-i X" to the pccardd_flags.
784 INSTALL=install -C is being deprecated. If you want to do this,
785 use COPY=-C instead. The former method will be supported for only
786 a limited time. If you see
788 install: warning: the -d and -C options may not be specified together
790 in your makeworld, then you need to migrate towards using
794 It appears that vm is now stable enough to use again. However,
795 there may be other problems, so caution is still urged. alpha
796 definitely is in bad shape.
799 Minor repo damage has happened. This may cause problems
800 with cvsup of ports. If you get errors, please see
801 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
802 at the bottom for details on a workaround. The error message
804 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
807 Vm and/or swapping are busted on -current. Please be patient.
810 pccard has had much reorganizational work done to it over
811 the past few days. Everything should still work, but if
812 not, please contact imp@freebsd.org.
815 ata ioctl changed. Make sure to recompile both kernel and
816 userland at the same time.
819 New ncurses imported.
822 DEVFS is now opt out, not opt in. Barring major problems, this
823 will be the only way to go starting July 1.
826 OpenSSH has been updated to 2.9. Some defaults are different,
827 including RhostsRSAAuthentication, which changes from yes to no.
830 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
833 Building perl was broken at 02:25:25 PDT.
836 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
837 go back in the water.
840 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
841 this date, but before the correction date.
844 old fsck and new kernel interactions appear to have been fixed.
847 fsck and the kernel were changed to handle some optimizations
848 to directory layout. This breaks backward compatibility.
849 Update only if you understand that you must not use the old
850 fsck with the new kernel ever.
853 fsck has changed the meaning of the pass column in /etc/fstab.
854 Please see the cvs commit to fsck.8 or the fsck.8 man page for
855 details. It is unclear if changes to /etc/fstab are necessary.
858 portmap had changed name to rpcbind for maximum POLA in your
859 current world. /etc/hosts.{allow,deny} needs changes. nfs and
860 other rpc based programs that rely on portmapper will not work
861 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
864 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
865 and ATA_ENABLE_TAGS are no longer kernel options. They have
866 been replaced by tunables. See ata.4 for details.
869 The fxp driver was converted to use miibus. If you compile
870 fxp into your kernel statically, you will need to add miibus.
873 The wi device now defaults to BSS (infrastructure) mode
877 /dev/urandom should be a symbolic link to /dev/random now.
878 Users of current not using DEVFS need to run MAKEDEV std.
879 ssh might not work if you don't.
882 The ed driver has been updated. It now allows mii attachments,
883 which means that you must include the miibus in your kernel if
884 you use the ed driver.
887 The problems with libc have been corrected. It is now mostly
888 safe to go back into the water.
891 The size of FILE was changed. This breaks upgrading. If
892 you must upgrade, be prepared for pain. It also breaks almost
893 all binaries that you've compiled on -current. You are warned
894 that before upgrading would be a good time to do a level 0
895 dump of your system. No, really, I mean it this time.
897 To get to the new system, you'll need to use the following
898 workaround. Hopefully this can be sorted out so that we
899 don't have to move this to the updating section.
901 To get around the installworld problem, do:
902 # cd /usr/src/usr.bin/sed
906 If that doesn't work, then try:
907 # make -k installworld
911 DEVFS is now the default. If you use vinum, make sure that you
912 do not include devfs in your kernel as problems result.
915 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
916 Remove them from your config.
919 ****************************** WARNING ******************************
920 buildkernel has been changed slightly
921 ****************************** WARNING ******************************
922 KERNCONF replaces the variable KERNEL for buildkernel. You
923 should update your scripts and make.conf accordingly.
926 config has changed to allow DEV_FOO as a replacement for NFOO.
927 This requires a new config to build correctly.
930 The kernel option I386_CPU is now mutually exclusive with the
931 other cpu types. If you have an i386 system, be sure that it
932 only had this line. Remove it for all other configurations.
935 Changes to the kernel require it and burncd be in sync.
938 Everyone who has hw.sndunit set to something in
939 /etc/sysctl.conf, it is now hw.snd.unit.
942 ex and vi were broken by some changes to sys/queue.h. If you
943 have a bad vi, you will see make buildworld fail with a core
944 dump while building termcap. You can work around this problem
945 by adding -k to your make buildworld. This will cause the
946 build to complete and install a new vi. Once that's done, you
947 can rebuild again without the -k to pick up anything that
948 might have been ignored by the -k option.
950 Others have suggested that you can just rebuild libc if your
951 vi/ex is dynamically linked, but I've not received any reports
955 There have been some changes to libcrypt in -current. The
956 libscrypt/libdescrypt symlink silliness is gone and the installed
957 libcrypt is fully functional. Be aware of this.
960 Linksys Fast Ethernet PCCARD cards supported by the ed driver
961 now require the addition of flag 0x80000 to their config line
962 in pccard.conf(5). This flag is not optional. These Linksys
963 cards will not be recognized without it.
966 Important new FreeBSD-version stuff: PAM support has been worked
967 in, partially from the "Unix" OpenSSH version. This requires
968 adding the following in pam.conf:
970 sshd auth sufficient pam_skey.so
971 sshd auth required pam_unix.so try_first_pass
972 sshd session required pam_permit.so
978 The random device needs more entropy, so you need to make sure
979 that you've run mergemaster to get a /etc/rc which will seed
980 /dev/random. If you don't and the system hangs after ldconfig,
981 then banging on the keyboard randomly until it unhangs is one
985 ****************************** WARNING ******************************
986 Sendmail has been updated.
987 ****************************** WARNING ******************************
988 o mail.local(8) is no longer installed as a set-user-id binary.
989 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
991 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
993 o Now using sendmail's version of vacation(1).
994 o The sendmail cf building tools (contrib/sendmail/cf) are installed
995 in /usr/share/sendmail/cf.
996 o sendmail.cw changed to local-host-names
998 More details can be found at
999 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1002 The ports tree's new layout is in place. Be sure to update
1003 your entire ports tree, or you will have problems.
1006 The perl build procedure no longer installs miniperl, nor uses
1007 the installed miniperl. It is recommended that you delete
1011 This weekend the ports tree will be updated to a new layout.
1012 It will be in an inconsistent state until noted in the UPDATING
1013 file, or with asami-san's message to the relevant mailing
1014 lists. With this new layout, you'll need to update the whole
1015 tree for anything to work.
1018 There was a change in the passwd format. Need more information.
1021 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1022 place. Please update boot loader (not the boot blocks) at the
1023 same time as your kernel.
1026 The new pmtimer device is necessary for laptops. Failure to
1027 include the device will cause suspended laptops losing time
1028 when they resume. Include
1030 in your config file and
1031 hint.pmtimer.0.at="isa"
1032 to your /boot/device.hints file.
1035 The random device has been turned into a (pseudo-)device,
1036 rather than an option. The supplied kernel config files have
1037 been updated. You will need to do something similar in your
1038 own kernel config file.
1043 If you prefer to load the loadable module, you need to do
1047 The random device module has been renamed from randomdev.ko to
1048 random.ko. You will need to edit your /boot/loader.conf to
1049 reflect this if you load this module at boot time.
1050 The line should read:
1054 The SMPNG commit has happened. It should work, but if it
1055 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1056 to be a variety of minor issues. Please see 20000905 to make
1057 sure you don't have model loading problems which might at
1058 first blush appear related to SMP.
1061 nsswitch has been imported from NetBSD. Among other things,
1062 this means that /etc/host.conf is no longer used. See
1063 nsswitch.conf(5) instead. Note that at boot time rc.network
1064 will attempt to produce a new nsswitch.conf file for you if you
1065 don't have one, and you have host.conf.
1068 The ucred structure changed size. This breaks the interface
1069 that mountd uses. Trying to use an older mountd with a newer
1070 kernel guarantees a panic. This means that you need to use
1071 kernels newer than today only with matching mountd, but you
1072 needed to do that anyway with the boot loader changes.
1075 The boot loader has been updated. The new default kernel is
1076 now /boot/kernel/kernel.ko. The new default module location
1079 You *MUST* upgrade your boot loader and kernel at the same time.
1080 The easiest way to do this is to do the buildworld/buildkernel/
1081 installkernel/installworld dance.
1083 Furthermore, you are urged to delete your old /modules directory
1084 before booting the new kernel, since kldload will find stale
1085 modules in that directory instead of finding them in the correct
1086 path, /boot/kernel. The most common complaint that this cures
1087 is that the linux module crashes your machine after the update.
1089 if [ ! -d /boot/kernel.old ]; then
1090 mv /modules.old /boot/kernel.old
1091 chflags noschg /kernel.old
1092 mv /kernel.old /boot/kernel.old/kernel.ko
1093 chflags schg /boot/kernel.old/kernel.ko
1097 A new issue with the sendmail upgrade has come to light.
1098 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1099 incorrectly install the default aliases in /etc/mail rather than
1100 move the old one from /etc. So you'll need to manually move the
1101 file, create a symbolic link, remove the old /etc/aliases.db and
1102 run newaliases. For safety sake, you should stop sendmail
1103 while doing this and run the upgrade when locally sourced email
1104 is not likely to be generated.
1107 /boot/device.hints is now required for installkernel to
1108 succeed. You should copy GENERIC.hints for your architecture
1109 into /boot/device.hints. If and only if you compile hints
1110 into your kernel, then this file may be empty. Please note,
1111 if you have an empty or missing /boot/device.hints file and
1112 you neglected to compile hints into your kernel, no boot
1113 messages will appear after the boot loader tries to start the
1117 If you do NOT have ``options RANDOMDEV'' in your kernel and
1118 you DO want the random device then add randomdev_load="YES" to
1122 suidperl is now always built and installed on the system, but
1123 with permissions of 511. If you have applications that use
1124 this program, you are now required to add ENABLE_SUIDPERL=true
1125 to /etc/make.conf. If you forget to do this,
1126 chmod 4511 /usr/bin/suidperl
1127 will fix this until the next build.
1130 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1131 visible changes that may immediately affect your configuration
1133 - New default file locations from src/contrib/sendmail/cf/README
1134 - newaliases limited to root and trusted users
1135 - MSA port (587) turned on by default
1136 - New queue file naming system so can't go from 8.11 -> 8.9
1137 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1138 - FEATURE(`nullclient') is more full featured
1139 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1140 - mail.local FreeBSD-only -b option changed to -B
1141 - See src/contrib/sendmail/RELEASE_NOTES for more info
1144 suidperl (aka sperl) is no longer build by default. You must
1145 specifically define BUILD_SUIDPERL to "true" for it to be build.
1146 Furthermore, we recommend that you remove /usr/bin/sperl* and
1147 /usr/bin/suidperl files from your system unless you have a
1148 specific use for it.
1151 Networking defaults have been tightened. Anybody upgrading
1152 /etc/defaults/rc.conf needs to add the following lines to
1153 /etc/rc.conf if they want to have the same setup
1154 afterwards (unless the variables already are set, of course):
1155 # Enable network daemons for user convenience.
1157 portmap_enable="YES"
1158 sendmail_enable="YES"
1161 If you have null_load="YES" in your /boot/loader.conf, you
1162 will need to change that to nullfs_load="YES".
1165 The "installkernel" target has changed slightly. Now even if
1166 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1167 it will install the MYKERNEL file (built with the buildkernel
1168 target) as /kernel rather than /MYKERNEL. Those who have
1169 updated their /boot/loader.conf files to point to /MYKERNEL
1170 should remove that entry or perform manual rename of /kernel
1174 If you use CVSUP or CTM to get CVS trees, AND you used to get
1175 the old crypto files from internat.freebsd.org AND you check
1176 out files from the CVS tree with the cvs command, please read
1177 http://people.freebsd.org/~imp/internat.txt
1178 for details on potential problems that you might have and how
1181 If you are merely a mirror, or don't answer yes to each of the
1182 clauses above, you needn't worry.
1185 /etc/security has been updated to print the inode number of
1186 setuid programs that have changed. You will see a large spike
1187 in the number of changed programs the first time when you run
1188 mergemaster to get a new /etc/security.
1191 /dev/random now has good entropy collection (from the keyboard
1192 and sysmouse drivers). Please ensure that either `options
1193 RANDOMDEV' is present in your kernel config file or that
1194 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1195 not have the /dev/random driver, OpenSSL (and consequently
1196 lots of crypto tools (like SSH)) will fail with strange
1197 errors. (see below, 20000624).
1199 FreeBSD-current is safe again to run Crypto.
1202 phk made the malloc default options AJ. This may slow things
1203 down and uncover other latent bugs in the code. If you need to
1204 run at full speed, you can disable this by doing the following:
1205 ln -s aj /etc/malloc.conf
1208 libftpio's version was accidentally bumped a few days ago. This
1209 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1210 before doing your next buildworld/installworld pair. It certainly
1211 won't hurt to remove it before the update procedure. It will
1212 break fetch until a new one is built, but ftp can be used in the
1216 The crypto packages have changed for the cvsup. This has been done
1217 in a backward compatible way, but the old packages will go away at
1218 some point in the future. Look at /usr/share/examples/cvsup for
1222 With the new sys/modules/sound/drivers/*, you will need to
1223 set SYSDIR until you do an installworld after July 7th.
1226 rc.shutdown and rc will now call the rc.d scripts with start
1227 or stop. This may cause some harmless warnings from older
1228 rc.d scripts that haven't been updated.
1231 The libfetch based version of fetch has gone into the tree.
1232 Minor problems may result on some of the less popular sites,
1233 which should be reported to des@freebsd.org.
1236 From approximately this date forward, one must have the crypto
1237 system installed in order to build the system and kernel.
1238 While not technically strictly true, one should treat it as
1239 required and grab the crypto bits. If you are grabbing CVS
1240 trees, src-all and cvs-crypto should be treated as if they
1241 were required. You should check with the latest collections
1242 to make sure that these haven't changed.
1245 Mark Murray just committed the first parts of a cleanup of
1246 /dev/zero, et al. This is also cleaning up /dev/random.
1247 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1248 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1249 until Mark can merge in the fixes to this work in progress.
1250 openssh and openssl should not be used to generate keys from this
1251 date to the completion of the work.
1253 If you must operate at this reduced level of security, add '
1254 options RANDOMDEV' to your kernel or modload the randomdev
1255 module. You may also need to copy a new MAKEDEV to /dev and
1256 recreate the random and urandom devices.
1259 The license on the softupdates is now a standard 2 clause
1260 BSD license. You may need to remove your symbolic links
1261 that used to be required when updating.
1264 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1265 the config file update procedure.
1266 http://people.freebsd.org/~imp/config-upd.html
1267 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1268 isn't buildable. However, you can generate a LINT file:
1269 cd /sys/<ARCH>/conf && make LINT
1272 Binutils 2.10 have hit the tree, or will shortly. As soon
1273 as they do, the problem noted in 20000522 will be resolved and
1274 that workaround will no longer be required.
1277 phk removed the compatibility creation of wd devices in the
1278 ad driver. If you haven't done so already, you must update
1279 your fstab, etc to use the ad devices instead of the wd
1282 In addition, you'll need to update your boot blocks to a
1283 more modern version, if you haven't already done so. Modern
1284 here means 4.0 release or newer (although older releases
1288 Peter took an axe to config(8). Be sure that you read his mail
1289 on the topic before even thinking about updating. You will
1290 need to create a /boot/device.hints or add a hints directive
1291 to your config file to compile them in statically. The format
1292 of the config file has changed as well. Please see GENERIC or
1293 NEWCARD for examples of the new format.
1295 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1296 says that it has been fixed, assume that must use the hints mechanism
1297 in the loader if you need to use a machine with very old ISA cards
1301 A new set of binutils went into the tree today. Anybody
1302 building a kernel after this point is advised that they need
1303 to rebuild their binutils (or better yet do a
1304 buildworld/installworld) before building a new kernel.
1306 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1307 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1308 is recommended that you don't set this option until the problem
1312 The ethernet drivers were all updated to clean up the BPF handling.
1315 The problems with boot blocks on the alphas have been corrected.
1316 This will require some care in updating alphas. A new libstand
1317 is requires for the boot blocks to build properly.
1320 Recompile all kld modules. Proper version dependency info
1324 Modules have been disconnected from the buildworld tree and
1325 connected to the kernel building instead.
1328 You may need to build gperf
1329 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1330 when upgrading from 4.0 -> current. The build system now uses
1331 an option only in -current.
1334 The method that we brand ELF binaries has changed to be more
1335 acceptable to the binutils maintainers. You will need to
1336 rebrand your ELF binaries that aren't native. One problem
1337 binary is the Linux ldconfig. After your make world, but
1338 before you reboot, you'll need to issue:
1339 brandelf -t Linux /compat/linux/sbin/ldconfig
1340 if you have Linux compatibility enabled on your machine.
1343 If you have really bad/marginal IDE drives, you may find they
1344 don't work well. Use pio mode instead. The easiest way to
1345 cope if you have a problem combination is to add:
1346 /sbin/sysctl hw.ata.ata_dma=0
1347 to the start of /etc/rc.conf.
1350 The ISA and PCI compatibility shims have been connected to the
1351 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1352 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1353 include the appropriate option in your kernel config. Drivers
1354 using the shims should be updated or they won't ship with
1355 5.0-RELEASE, targeted for 2001.
1358 We've entered the traditional post release dumping party.
1359 Large kernel changes are being committed and are in the
1360 works. It is important to keep the systems' klds and kernel
1361 in sync as kernel interfaces and structures are changing.
1362 Before reporting kernel panics, make sure that all modules
1363 that you are loading are up to date.
1366 If you are upgrading from an older version of FreeBSD, you
1367 need to update your boot blocks as well. 'disklabel -B ad0'
1368 will do the trick. This isn't critical until you remove your
1369 wd device entries in /dev, at which point your system will not
1373 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1374 to upgrade to 4.0 from 3.x.
1380 Avoid using make -j when upgrading. From time to time in the
1381 past there have been problems using -j with buildworld and/or
1382 installworld. This is especially true when upgrading between
1383 "distant" versions (eg one that cross a major release boundary
1384 or several minor releases, or when several months have passed
1385 on the -current branch).
1387 Sometimes, obscure build problems are the result of environment
1388 poisoning. This can happen because the make utility reads its
1389 environment when searching for values for global variables.
1390 To run your build attempts in an "environmental clean room",
1391 prefix all make commands with 'env -i '. See the env(1) manual
1392 page for more details.
1396 If you are updating from a prior version of FreeBSD (even one just
1397 a few days old), you should follow this procedure. With a
1398 /usr/obj tree with a fresh buildworld,
1399 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1400 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1402 To just build a kernel when you know that it won't mess you up
1403 --------------------------------------------------------------
1404 This assumes you are already running a 5.X system. Replace
1405 ${arch} with the architecture of your machine (e.g. "i386",
1406 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1408 cd src/sys/${arch}/conf
1409 config KERNEL_NAME_HERE
1410 cd ../compile/KERNEL_NAME_HERE
1415 If this fails, go to the "To build a kernel" section.
1417 To rebuild everything and install it on the current system.
1418 -----------------------------------------------------------
1419 # Note: sometimes if you are running current you gotta do more than
1420 # is listed here if you are upgrading from a really old current.
1422 <make sure you have good level 0 dumps>
1423 <maybe fix /etc/fstab> [7]
1425 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1426 make installkernel KERNCONF=YOUR_KERNEL_HERE
1428 <reboot in single user> [3]
1429 /etc/rc.d/preseedrandom [10]
1436 To cross-install current onto a separate partition
1437 --------------------------------------------------
1438 # In this approach we use a separate partition to hold
1439 # current's root, 'usr', and 'var' directories. A partition
1440 # holding "/", "/usr" and "/var" should be about 2GB in
1443 <make sure you have good level 0 dumps>
1446 <maybe newfs current's root partition>
1447 <mount current's root partition on directory ${CURRENT_ROOT}>
1448 make installworld DESTDIR=${CURRENT_ROOT}
1449 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1450 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1451 ${CURRENT_ROOT}/boot/device.hints # as needed
1452 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1453 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1454 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1455 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1456 <reboot into current>
1457 <do a "native" rebuild/install as described in the previous section>
1458 <maybe install compatibility libraries from /usr/src/lib/compat>
1462 To upgrade in-place from 4.x-stable to current
1463 ----------------------------------------------
1464 # 5.x uses more space than 4.x. Also, the location of kernel
1465 # modules has changed. If you are installing 5.0 onto a 4.x
1466 # system, you'll need about 30MB of free disk space on your /
1467 # partition. If you have less than this, you may encounter difficult
1468 # to back out of problems with this procedure. If /tmp is on
1469 # the / partition, you may want to completely remove all its content
1470 # before upgrading, as this can be a common source of shortage of
1473 <make sure you have good level 0 dumps>
1474 <maybe fix /etc/fstab> [7]
1476 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1477 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1478 make installkernel KERNCONF=YOUR_KERNEL_HERE
1479 cd src/sys/boot ; make install [6]
1481 <reboot in single user> [3]
1482 /etc/rc.d/preseedrandom [10]
1484 rm -rf /usr/include/g++
1489 Make sure that you've read the UPDATING file to understand the
1490 tweaks to various things you need. At this point in the life
1491 cycle of current, things change often and you are on your own
1492 to cope. The defaults can also change, so please read ALL of
1493 the UPDATING entries.
1495 Also, if you are tracking -current, you must be subscribed to
1496 freebsd-current@freebsd.org. Make sure that before you update
1497 your sources that you have read and understood all the recent
1498 messages there. If in doubt, please track -stable which has
1499 much fewer pitfalls.
1501 [1] If you have third party modules, such as vmware, you
1502 should disable them at this point so they don't crash your
1505 [2] If you have legacy ISA devices, you may need to create
1506 your own device.hints to reflect your unique hardware
1509 [3] From the bootblocks, boot -s, and then do
1514 adjkerntz -i # if CMOS is wall time
1515 Also, when doing a major release upgrade, it is required that
1516 you boot into single user mode to do the installworld.
1517 For the 4.x -> 5.0 upgrade, you will also see many messages about
1518 needing to recompile your userland. These are harmless and can
1519 be ignored while you proceed to the next step.
1521 [4] Note: This step is non-optional. Failure to do this step
1522 can result in a significant reduction in the functionality of the
1523 system. Attempting to do it by hand is not recommended and those
1524 that pursue this avenue should read this file carefully, as well
1525 as the archives of freebsd-current and freebsd-hackers mailing lists
1526 for potential gotchas.
1528 [5] Usually this step is a noop. However, from time to time
1529 you may need to do this if you get unknown user in the following
1530 step. It never hurts to do it all the time. You may need to
1531 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1532 install) after the buildworld before this step if you last updated
1533 from current before 20020224 or from -stable before 20020408.
1535 [6] 4.x boot loader can be used to boot a 5.x system, however
1536 it is difficult to do that at best. If you wish to try, then
1537 you should interrupt the boot and at the ok prompt type:
1539 ok boot /boot/kernel/kernel
1540 If this fails to work, you must install a new boot loader as
1543 [7] Before you upgrade, please make sure that you are not using
1544 compatibility slices. These are device names of the form, on i386
1545 and other architectures that use MBR slicing, /dev/ad0a without the
1546 actual slice name. Chances are excellent that these will break.
1547 You generally must update these entries to use the post FreeBSD
1548 2.x form of /dev/ad0s1a.
1550 [8] In order to have a kernel that can run the 4.x binaries
1551 needed to do an installworld, you must include the COMPAT_FREEBSD4
1552 option in your kernel. Failure to do so may leave you with a system
1553 that is hard to boot to recover.
1555 [9] When checking out sources, you must include the -P flag to have
1556 cvs prune empty directories.
1558 [10] In order to create temporary files, /dev/random must be
1559 initialized by feeding data into it. /etc/rc.d/preseedrandom
1563 This file contains a list, in reverse chronological order, of major
1564 breakages in tracking -current. Not all things will be listed here,
1565 and it only starts on March 15, 2000. Updating files can found in
1566 previous releases if your system is older than this.
1568 Copyright information:
1570 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1572 Redistribution, publication, translation and use, with or without
1573 modification, in full or in part, in any form or format of this
1574 document are permitted without further permission from the author.
1576 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1577 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1578 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1579 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1580 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1581 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1582 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1583 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1584 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1585 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1586 POSSIBILITY OF SUCH DAMAGE.
1588 If you find this document useful, and you want to, you may buy the
1591 Contact Warner Losh if you have any questions about your use of