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 Due to a new option in ipfw (versrcreach) the ipfw(8) command
22 needs to be recompiled. Normal accept/reject rules without
23 options are not affected but those with options may break until
24 ipfw(8) is recompiled.
27 Due to changes in the callout ABI, kernels compiled after this
28 date may be incompatible with kernel modules compiled prior to
32 The PCI bus power state stuff has been turned on. If this causes
33 problems for your system, please disable it using the tunable
34 hw.pci.do_powerstate=0.
37 The bulk of the pci problems have been fixed, although the floppy
38 drive is still broken.
41 A substantial update to the pci bus resource and power management
42 have been committed. Expect a bumpy ride for a few days until
43 the unanticipated problems have been resolved.
46 Due to changes in the the Yarrow initialization process,
47 /dev/random needs to be fed before operations requiring
48 temp files can succeed in single user mode. This includes
49 running "make installworld". /dev/random may be fed by running
50 "/etc/rc.d/initrandom start" or with 20040415 source by running
51 "/etc/rc.d/preseedrandom".
54 The debug.mpsafenet tunable controls whether the kernel Giant
55 lock is held across the lower levels of the network stack, and
56 by default is turned off. In the few days following 20040322,
57 the behavior of debug.mpsafenet will change such that this
58 tunable controls Giant over all levels of the network stack.
59 If you are currently setting debug.mpsafenet to 1, you should
60 set it back to 0 (the default) again during the change-over.
61 An additional note will be added to UPDATING when sufficient
62 locking is merged to permit this to take place.
65 The FreeBSD/sparc64 platform is changing time_t from 32-bits to
66 64-bits. This is a very major incompatible change, so people
67 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
68 detailed instructions on how to make this upgrade. People
69 upgrading FreeBSD on other platforms can ignore this event.
72 The packet filter (pf) is now installed with the base system. Make
73 sure to run mergemaster -p before installworld to create required
74 user account ("proxy"). If you do not want to build pf with your
75 system you can use the NO_PF knob in make.conf.
76 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
77 pf system consists of the following three devices:
79 device pflog # optional
80 device pfsync # optional
83 If you are having trouble with the libc_r -> libpthread transition
84 (see the 20040130 entry), place the following lines at the top of
87 libc_r.so.5 libpthread.so.1
88 libc_r.so libpthread.so
90 This will cause all programs and libraries linked against libc_r
91 to use libpthread instead.
94 Some sshd configuration defaults have changed: protocol version 1
95 is no longer enabled by default, and password authentication is
96 disabled by default if PAM is enabled (which it is by default).
97 OpenSSH clients should not be affected by this; other clients may
98 have to be reconfigured, upgraded or replaced.
101 The ABIs defined in <resolv.h> and <netdb.h> have been updated
102 to support improved reentrancy. Multi-threaded programs that
103 reference the "_res" or "h_errno" symbols may experience some
104 problems if they are not recompiled. Single-threaded programs
105 should remain unaffected.
108 routed has been updated in the base system from the vendor
109 sources, routed v2.27, from rhyolite.com. This change means that
110 for users who use RIP's MD5 authentication feature, FreeBSD
111 -CURRENT's routed is now incompatible with previous versions
112 of FreeBSD; however it is now compatible with implementations
113 from Sun, Cisco and other vendors.
116 The tcpcb structure has changed and makes a recompile of libkvm
117 and related userland network utilities neccessary.
120 The cdevsw structure has changed in two externally visible ways.
121 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
122 Second, the d_version field must be filled in with D_VERSION.
123 Drivers outside the tree will need to be updated.
126 The /etc/rc.d/ttys script has been removed. It is no longer
127 necessary since devfs has been mandatory for some time.
130 libkse has been renamed back to libpthread and is now the
131 default threads library. The gcc -pthread option has also
132 been changed to link to libpthread instead of libc_r. For
133 alpha and sparc64 machines, libkse is not renamed and links
134 are installed so that libpthread points to libc_r. Until
135 the ports system is updated to handle this change, it is
136 recommended that folks install an /etc/libmap.conf(5) that
137 maps libc_r to libpthread. If you have any binaries or
138 libraries linked to libkse, then it is also recommended
139 that you map libkse to libpthread. Anyone that is using
140 nvidia supplied drivers and libraries should use a libmap.conf
141 that maps libpthread to libc_r since their drivers/libraries
142 do not work with libpthread.
145 ULE has entered into its probationary period as the default scheduler
146 in GENERIC. For the average user, interactivity is reported to be
147 better in many cases. On SMP machines ULE will be able to make more
148 efficient use of the available parallel resources. If you are not
149 running it now, please switch over, replacing the kernel option
150 SCHED_4BSD with SCHED_ULE.
153 Move LongRun support out of identcpu.c, where it hardly
154 belongs, into its own file and make it opt-in, not mandatory,
155 depending on CPU_ENABLE_LONGRUN config(8) option.
158 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
159 if the login process is unable to successfully set the
160 process credentials to include all groups defined for the
161 user. The current kernel limit is 16 groups; administrators
162 may wish to check that users do not have over 16 groups
163 defined, or they will be unable to log in.
166 The ACPI module has been reactivated. It is no longer required
167 to compile ACPI support into kernels statically.
170 The statfs structure has been updated with 64-bit fields to
171 allow accurate reporting of multi-terabyte filesystem
172 sizes. You should build world, then build and boot the new kernel
173 BEFORE doing a `installworld' as the new kernel will know about
174 binaries using the old statfs structure, but an old kernel will
175 not know about the new system calls that support the new statfs
177 Note that the backwards compatibility is only present when the
178 kernel is configured with the COMPAT_FREEBSD4 option. Since
179 even /bin/sh will not run with a new kernel without said option
180 you're pretty much dead in the water without it. Make sure you
181 have COMPAT_FREEBSD4!
182 Running an old kernel after a `make world' will cause programs
183 such as `df' that do a statfs system call to fail with a bad
184 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
185 that cfsd (ports/security/cfs) needs to be recompiled after
186 these changes are installed.
188 ****************************DANGER*******************************
190 DO NOT make installworld after the buildworld w/o building and
191 installing a new kernel FIRST. You will be unable to build a
192 new kernel otherwise on a system with new binaries and an old
196 Some netgraph string length constants have been changed. This
197 change requires the netgraph kernel modules and all netgraph
198 userland components to be in sync. Especially users who require
199 netgraph to boot need to make sure to have world and kernel in
200 sync before rebooting.
203 Hyperthreading logical CPU's are no longer probed by default
204 when using the MP Table. If ACPI is being used, then logical
205 CPUs will be probed if hyperthreading is enabled in the BIOS.
206 If ACPI is not being used and hyperthreading is enabled in the
207 BIOS, logical CPUs can be enabled by building a custom kernel
208 with the option MPTABLE_FORCE_HTT enabled.
211 The i386 APIC_IO kernel option has been replaced by
212 'device apic'. The ACPI module has also been temporarily
213 disabled, so ACPI must be statically compiled into your
214 kernel using 'device acpi' if you wish to use the ACPI driver.
217 The API and ABI of struct ifnet have been changed by removing
218 the if_name and if_unit members and replacing them with
219 if_xname, if_dname, and if_dunit. All network drivers and most
220 userland programs which include net/if_var.h must be updated
221 and recompiled. __FreeBSD_version has been bumped to 501113 to
225 Changes to the cdevsw default functions have been made to remove
226 the need to specify nullopen() and nullclose() explicitly.
227 __FreeBSD_version bumpted to 501110.
230 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
231 mount_cd9660(8) need to be in sync with kernel.
234 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
235 also be explicitly configured. Previously this dependency was
236 magically handled through some cruft in net/pfil.h; but that has
237 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
238 will fail with obtuse errors in ip_fil.c.
241 Fix a bug in arplookup(), whereby a hostile party on a locally
242 attached network could exhaust kernel memory, and cause a system
243 panic, by sending a flood of spoofed ARP requests. See
244 FreeBSD-SA-03:14.arp.
247 A change to /etc/defaults/rc.conf now causes inetd to be started
248 with `-C 60' if it is not overridden in /etc/rc.conf. This
249 causes inetd to stop accepting connections from an IP address
250 that exceeds the rate of 60 connections per minute.
253 The following rc.d scripts have been removed and should be
254 deleted from your installation: atm2.sh atm3.sh devdb
255 localdaemons network1 network2 network3. Depending on when
256 you last updated world and used mergemaster(8) you may or
257 may not have problems during the rc boot sequence. The simplest
258 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
259 The atm2.sh atm3.sh and devdb scripts were removed some time
260 ago, so depending on when you installed -CURRENT these scripts
261 may or may not exist on your system.
264 ATAng has been committed. You need to build world as sys/ata.h
265 has changed, and userland atacontrol depends on it.
266 If you use ATA SW raids you need "device ataraid" in your
267 kernel config file, as it is no longer pulled in automatically.
270 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
271 Among other things, this changes the device enumeration to be
272 closer to Solaris. Be aware that, this can even cause the machine
273 to not boot without manual intervention before the fstab is adjusted.
276 All current USB and Firewire quirks in da(4) have been deprecated
277 and will be removed for 5.2. If this causes failure for your
278 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
279 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
280 so the quirk can be re-enabled.
283 Problems with entry 20030714 have been corrected and no known issues
284 with /rescue and -j exist for host systems after this point in time.
287 FPU-less support has been removed from FreeBSD. Chances are you won't
288 notice. 386+387 support should still work after this change, but
289 it is now a minimum requirement for the i386 port that you have real
293 Some people are having problems with changes related to /rescue.
294 If you are building -j N, you will need to define NO_RESCUE. Others
295 will need to define it if /rescue has issues with their environment.
296 People should report those issues to current@.
299 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
300 across this point. Further, it might be a good idea to remove
304 Remove deprecated locale names and transition period code
305 for them, finishing switching to the new scheme. Check your
306 LANG environment variable.
309 CCD has been changed to be a fully GEOMified class. Kernel
310 and ccdconfig(8) needs to be in sync, this is particularly
311 important to remember beforehand if your source tree is on
312 a ccd device. Consider making a copy of the old ccdconfig
313 into /boot/kernel.good or wherever you keep your backup
317 There was a small window in which sed(1) was broken. If you
318 happen to have sed(1) installed during that window, which is
319 evidenced by an inability to build world with the failure
320 given below, you need to manually build and install sed(1)
321 (and only sed(1)) before doing anything else. This is a one-
322 time snafu. Typical failure mode:
324 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
325 targmatch.h:7:1: null character(s) ignored
326 targmatch.h:12:1: null character(s) ignored
327 targmatch.h:16:1: null character(s) ignored
330 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
331 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
332 usr.bin/sed/process.c).
335 Kerberos 5 (Heimdal) is now built by default. Setting
336 MAKE_KERBEROS5 no longer has any effect. If you do NOT
337 want the "base" Kerberos 5, you need to set NO_KERBEROS.
340 groff has been updated. If you try to do a buildworld and
341 get an infinite loop in troff, update to May 4th or newer. If you
342 have a newer kernel than userland, you may need to set the OSRELDATE
343 to 500110 in your environment before starting a buildworld.
346 The old rc system has been removed. Please report any problems
347 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
348 Your personal versions of these files will not be removed, so you can
349 continue to use them. However, you should take great care when updating,
350 especially when using mergemaster, since the compatibility code that
351 utilizes these old scripts has also been removed.
354 A bug has been fixed in /dev/devctl which would cause devd
355 to hang on boot, were it not for a workaround in devd. The
356 work around in devd will be removed around 20030507. You
357 have until then to upgrade your kernel before updating
358 userland. In general, you should have a userland and
359 kernel that's in sync with each other. However, given the
360 effects of this bug (hang on boot when starting devd), some
364 Alphas with libc from between 20030312 and 20030329 exhibit
365 floating point exceptions (FPEs), most notably in awk(1)
366 while upgrading the system through a buildworld.
368 So, to successfully upgrade your Alpha, you must either
369 downgrade your libc.so to a pre-20030312 version, or update
370 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
371 to CFLAGS, then forcibly rebuild and install libc:
373 cd /usr/src/lib/libc && \
374 make cleandir && make obj && \
375 make -DNOMAN -DNOPROFILE all && \
376 make -DNOMAN -DNOPROFILE install
379 sendmail 8.12.7 has been imported. It has one important
380 change for IPv6 users. The default submit.mc now uses
381 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
382 used to connect to the MTA. Users on IPv6-only machines
383 will need to edit /etc/mail/submit.mc appropriately.
386 NODEVFS option has been removed and DEVFS thereby made standard.
387 This makes all references to MAKEDEV obsolete, and they should
388 be removed when convenient.
391 The name of the device for the ofw console has changed, sparc64 users
392 must run mergemaster to update their installed /etc/ttys.
395 The scheduler framework has grown a second scheduler and consequently
396 you must specify one and only one scheduler in your kernel config.
397 The cvs config files have been updated to use the old scheduler
398 which may be selected via 'options SCHED_4BSD'. If you would like
399 to try the new, much more experimental, scheduler please try
400 'options SCHED_ULE' and contribute to the arch@ discussion.
403 A new version of the wi driver has been imported into the tree.
404 One now must have device wlan in the config file for it to operate
407 In addition, there have been some changes to how wi devices are
408 configured for point to point links to bring it more in line
409 with the former way of doing things, as well as compatibility
413 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
414 used an incompatible form of ABI for returning structures and unions
415 which FreeBSD's GCC maintainers were not aware of relative to previous
416 versions of FreeBSD. We have gone back to the ABI for now, and any
417 code compiled which is required to interoperate with other code (not
418 built at the same time) returning structs or unions should be
422 A name change in /etc/netconfig has been reverted to stay
423 compatible with suns TIRPC and also with NetBSD. You need
424 to run mergemaster after make world. A new libc does still work
425 with an outdated /etc/netconfig for some time, but you'll get
426 a warning. This warning will be removed in 20030301.
429 The recent binutils upgrade marks a kernel flag day on
430 sparc64: modules built with the old binutils will not work
431 with new kernels and vice versa. Mismatches will result in
432 panics. Make sure your kernel and modules are in sync.
435 The value of IPPROTO_DIVERT has changed. Make sure to keep
436 your kernel, netstat, natd and any third-party DIVERT
440 Old, compatibility slices have been removed in GEOM kernels.
441 This means that you will have to update your /etc/fstab to
442 not use disk devices of the form /dev/ad0a. Instead, you
443 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
444 partition really is on. The old device names have gone
445 away, so if you use them anywhere else, you must also adjust
446 those uses. (This doesn't affect the disks formatted in
447 the ``dangerously-dedicated'' mode.)
450 Alphas with kernels from between 20020830 and 20021023 and/or
451 rtld (ld-elf.so.1) older than 20021023 may experience problems
452 with groff while doing a buildworld (kernel: "out of memory",
453 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
454 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
456 So, to successfully upgrade your Alpha, you must either
457 upgrade your kernel and rtld first (which might be a bit
458 tricky), or avoid running the bootstrapped groff during the
459 "transitional" buildworld. To avoid running groff during the
460 transitional upgrade run make buildworld with -DNOMAN,
461 -DNO_SHAREDOCS, and -DNO_LPR.
464 gcc has been upgraded to 3.2. It is not all binary compatible
465 with earlier versions of gcc for c++ programs. All c++
466 programs and libraries need to be recompiled.
468 Also, if you encounter g++ issues, rm /usr/include/g++/* before
469 doing an installworld to make sure that stale files are removed.
472 Our /etc/termcap now has all the entries from the XFree86 xterm
473 almost unchanged. This means xterm now supports color by default.
474 If you used TERM=xterm-color in the past you now should use
475 TERM=xterm. (xterm-color will lead to benign warnings).
478 A "bug" in gcc(1) that was hiding warning in system headers was
479 fixed. It's probably time to add -DNO_WERROR to your make line
483 COPY is being deprecated. The 20010530 change was reverted, as
484 it causes far more pain than was expected, and to always compare
485 before installing, please use INSTALL="install -C" again. The
486 -C option is now silently ignored when used with the -d option.
489 Problems with libc_r clients like KDE and GNOME have been resolved.
490 There are still some minor problems with some signals but the
491 system is stable enough for general use again. SMP is less so than UP
492 but each can successfully complete multiple buildworlds.
493 Libkvm needs to be recompiled due to KSE.
496 Now would be a bad time to upgrade. Something in or near the
497 KSE commit totally broke programs using libc_r like KDE and
501 The k5su utility installed as part of Kerberos 5 is no longer
502 installed with the set-user-ID bit set by default. Add
503 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
504 with the set-user-ID bit set.
507 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
508 Unfortunately our native GDB (at version 4.18) does not understand
509 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
510 generated debugging information for our native GDB.
513 Due to the way CVS works, it may not properly update src/contrib/gcc
514 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
515 and then do a cvs update.
518 When exec'ing set[ug]id executables, the kernel now ensures that the
519 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
522 New sendmail startup scripts have been installed to make it
523 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
524 variable sendmail_enable to "NO" no longer prevents any sendmail
525 daemons from starting. Instead, either set sendmail_enable to
526 "NONE" or change mta_start_script to a script for starting
527 an alternative MTA. Setting mta_start_script to "" will
528 also prevent any MTA from being started at boot.
531 UCONSOLE is no longer a valid kernel option.
534 FreeBSD 5.0 DP-1 was basically branched today.
537 Warnings are now errors in the kernel. Unless you are a developer,
538 you should add -DNO_WERROR to your make line.
541 sendmail 8.12.2 has been imported. The sendmail binary is no
542 longer a set-user-ID root binary and the infrastructure to support
543 command line mail submission has changed. Be sure to run
544 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
545 and /etc/mail) and read /etc/mail/README for more details.
547 Due to the import of sendmail 8.12.2, a new user and group are
548 required in order for sendmail to run as a set-group-ID
549 binary. A 'make installworld' will use the new user and group
550 to set the owner and group of /var/spool/clientmqueue and will
551 fail if the new user and group do not exist. The 'smmsp' user
552 and group must be merged from src/etc/group and
553 src/etc/master.passwd before using 'make installworld'.
554 'mergemaster -p' will do this. You may need to install
555 mergemaster before this will work if you are updating from a
556 very old version of current. The updating recipe has changed
560 The preferred configuration method for PAM is now /etc/pam.d/
561 rather than /etc/pam.conf. If you have an unmodified
562 pam.conf, just delete it after your next mergemaster run. If
563 you have local modifications, you can use
564 /usr/src/etc/pam.d/convert.pl to incorporate them into your
567 Please see the following url for more details:
568 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
570 If anyone here is already using the new rc.conf(5) variable
571 networkfs_types, please note that it has changed
572 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
575 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
576 started out its life in the ISDN4BSD project as an offspring
577 from sys/net/if_spppsubr.c, which eventually got a life of its
578 own. All the accumulated features and bugfixes of the i4b
579 version have now been merged back into the base system's
580 version now. The only user-visible change resulting from this
581 is that i4b's sppp(4) interfaces are to be managed with
582 spppcontrol(8) again, since ispppcontrol(8) has been retired
583 as well. (There has never been rc file support for
584 ispppcontrol in -current, but only in -stable. That will be
585 reverted by the time the changes are MFCed.)
588 The fdc(4) driver has been updated and now automatically
589 recognizes media in `standard' formats (like 1440 KB and
590 720 KB for a 3.5" high-density drive) when accessing the
591 default device node (e. g. /dev/fd0). The old variety of
592 floppy device nodes /dev/fd*.* is no longer present by
593 default, devices can be created (in DEVFS) on demand. They
594 will need to be customized then for `odd' densities using
598 The bugs in procfs' debugging support code have been fixed,
599 and truss(1) now works again.
602 Daily security checks have been split out to use the periodic(8)
603 scripts. Some change in configuration may be necessary. Please
605 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
609 sos added VCD/SVCD support to ata driver and that needs the
610 kernel and burncd to be in sync.
613 The procfs pseudo-filesystem has now been converted to use the
614 pseudofs framework. If you have 'options PROCFS' in your
615 kernel config, you'll need to add 'options PSEUDOFS' if it's
618 This change temporarily breaks truss(1); use ktrace(1) instead
619 until the issue has been resolved.
622 A security hole in OpenSSH involving `UseLogin yes' has been
626 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
627 after this date. You need to do this only once.
630 Most of the awk issues have been resolved. Some rough
631 edges may be left, but for the most part things should be
632 back to "normal." For CURRENT's usual definition of "normal."
635 Awk has been upgraded to the one true awk from bell labs. Expect
636 choppy waves in the upgrade process.
639 The asr driver problem has been resolved.
642 Due to changes in other parts of the system, the asr driver
643 now causes the system to panic on boot. Do not use it pending
644 correction. Comment it out of any kernel config file that you
645 try to use from this date forward.
648 When crossbuilding, use TARGET=xxx where you used to use
649 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
650 unless you are changing both of them. To cross build pc98 on
651 an alpha, for example, you need to set TARGET=pc98 and
655 The kernel interface that burncd depends on has changed.
656 You must recompile both the kernel and userland applications
660 When crossbuilding, please set TARGET_ARCH rather than
661 MACHINE_ARCH to indicate the target. In the future, one will
662 set TARGET_MACHINE where you set MACHINE now. At the moment,
663 setting MACHINE alone for same MACHINE_ARCH machines works
664 (eg, you can build pc98 on an i386 machine and vice versa).
667 Some weird problems result from using ACPI on some machines.
668 To disable ACPI you can add
669 hint.acpi.0.disabled="1"
670 to /boot/loader.conf (or by putting set X=Y at the boot
673 Alternatively, you can remove it from /boot/kernel/acpi.ko
674 or use the MODULES_OVERRIDE function in your kernel config
675 file and not list acpi in that list.
678 The buildworld has been fixed. You may need to install
679 the 4.x compatibility libraries for some old binaries
680 to work. Add COMPAT4X=true to your /etc/make.conf to
681 get them installed on every installworld, or execute the
682 following to get them installed only once:
683 cd src/lib/compat/compat4x.<arch>
685 You will see ``__stdoutp undefined'' until you do this.
688 There's a bug in the world build process. The cross-tools
689 are build with the NEW headers, but the OLD libc.a. This
690 leads to all kinds of problems with the new libc. A temporary
692 CFLAGS="-O -pipe -D_OLD_STDIO"
693 before building world when upgrading from 4.x to current. This
694 can be removed afterwards.
696 A proper fix to the buildworld target is needed.
699 Peter has committed his new kthread nfs client/server code.
700 NFS may be unstable after this date.
703 KSE has hit the tree. Lots of things are now different in
704 the kernel. While a few problems were introduced in the
705 initial commit, most of the major ones have been found and
709 In OLDCARD, CardBus bridges appear to be stable. The work
710 arounds described in the 20010604 entry are now no longer
711 necessary and will be ignored. Most insert/remove problems
712 have been rectified around this date.
715 named now runs as user bind and group bind rather than as
716 root. If named_enable is set to YES in /etc/rc.conf, ensure
717 that user bind is available in /etc/passwd (using vipw(8))
718 and that group bind is available in /etc/group. Also make
719 sure that user or group bind has read (and not write)
720 permission for your name server configuration and that it
721 has read and write permission for your slave zone files and
724 If you wish to continue to run named as root (a less secure
725 alternative), add a line to /etc/rc.conf saying
730 The PAM libraries have had an API upgrade that is beyond
731 the ability of the shared library major number to handle.
732 It is manifested by PAM-using ports dumping core. The
733 solution is to rebuild those ports.
736 The kernel compile module has moved from src/sys/compile/FOO
737 to src/sys/${MACHINE}/compile/FOO.
740 The pccard modem issue from 20010613 has been corrected.
741 OLDCARD support is still a little weak in -current. slot 1 is
742 known not to work on some TI based cardbus bridges. Some
743 cardbus bridges do not properly detect insert/removal events.
744 IRQ configuration needs more safety belts.
747 Softupdates problems have been corrected.
750 Peter ripped out the linkerset support. You must, as always,
751 rerun config after you cvsup if you are using the traditional
752 kernel building methods.
755 pccard modems may not work with current after 20010604 date. Some
756 do, others result in panics. *MAKE*SURE* that you update your
757 config and /etc/rc.conf ala the 20010604 entry, or you will have
758 problems (this issue will be fixed, it just hasn't been yet).
761 SOFTUPDATES seem to be broken since the middle of May or so. Do not
762 use them in current. You can disable softupdates on all mounted
763 partitions, or remove SOFTUPDATES the kernel config file.
766 After Peter's commits to the hints code, people have been noticing
767 that certain devices are attached (or try to) twice. This is due
768 to having both static hints as well as a /boot/device.hints. To
769 work around this issue, please use only one or the other mechanism
770 until this bug is fixed.
772 Please note that a feature of config is that if you have config
773 file FOO and FOO.hints, it automatically adds FOO.hints to the
774 hints.c file, whether you want it to or not.
777 Locale names have changed to match other systems better.
780 pccard support for pci cards has been committed. You must change
781 your /etc/pccard.conf irq lines. It must match the irq used by
782 pcic device. Interrupt storms may result if you fail to do this.
783 Interrupt storms look a lot like a hang.
785 You must also install a new pccardd, otherwise you will get an
786 interrupt storm at card reset time (just after it tells you what
789 pccardd_flags="-I" is necessary for the time being. It tells pccardd
790 not to ask the kernel if the interrupt is really free or not before
791 using it. You can either change the /etc/pccard.conf irq lines to
792 match pcic, or add "-i X" to the pccardd_flags.
795 INSTALL=install -C is being deprecated. If you want to do this,
796 use COPY=-C instead. The former method will be supported for only
797 a limited time. If you see
799 install: warning: the -d and -C options may not be specified together
801 in your makeworld, then you need to migrate towards using
805 It appears that vm is now stable enough to use again. However,
806 there may be other problems, so caution is still urged. alpha
807 definitely is in bad shape.
810 Minor repo damage has happened. This may cause problems
811 with cvsup of ports. If you get errors, please see
812 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
813 at the bottom for details on a workaround. The error message
815 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
818 Vm and/or swapping are busted on -current. Please be patient.
821 pccard has had much reorganizational work done to it over
822 the past few days. Everything should still work, but if
823 not, please contact imp@freebsd.org.
826 ata ioctl changed. Make sure to recompile both kernel and
827 userland at the same time.
830 New ncurses imported.
833 DEVFS is now opt out, not opt in. Barring major problems, this
834 will be the only way to go starting July 1.
837 OpenSSH has been updated to 2.9. Some defaults are different,
838 including RhostsRSAAuthentication, which changes from yes to no.
841 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
844 Building perl was broken at 02:25:25 PDT.
847 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
848 go back in the water.
851 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
852 this date, but before the correction date.
855 old fsck and new kernel interactions appear to have been fixed.
858 fsck and the kernel were changed to handle some optimizations
859 to directory layout. This breaks backward compatibility.
860 Update only if you understand that you must not use the old
861 fsck with the new kernel ever.
864 fsck has changed the meaning of the pass column in /etc/fstab.
865 Please see the cvs commit to fsck.8 or the fsck.8 man page for
866 details. It is unclear if changes to /etc/fstab are necessary.
869 portmap had changed name to rpcbind for maximum POLA in your
870 current world. /etc/hosts.{allow,deny} needs changes. nfs and
871 other rpc based programs that rely on portmapper will not work
872 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
875 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
876 and ATA_ENABLE_TAGS are no longer kernel options. They have
877 been replaced by tunables. See ata.4 for details.
880 The fxp driver was converted to use miibus. If you compile
881 fxp into your kernel statically, you will need to add miibus.
884 The wi device now defaults to BSS (infrastructure) mode
888 /dev/urandom should be a symbolic link to /dev/random now.
889 Users of current not using DEVFS need to run MAKEDEV std.
890 ssh might not work if you don't.
893 The ed driver has been updated. It now allows mii attachments,
894 which means that you must include the miibus in your kernel if
895 you use the ed driver.
898 The problems with libc have been corrected. It is now mostly
899 safe to go back into the water.
902 The size of FILE was changed. This breaks upgrading. If
903 you must upgrade, be prepared for pain. It also breaks almost
904 all binaries that you've compiled on -current. You are warned
905 that before upgrading would be a good time to do a level 0
906 dump of your system. No, really, I mean it this time.
908 To get to the new system, you'll need to use the following
909 workaround. Hopefully this can be sorted out so that we
910 don't have to move this to the updating section.
912 To get around the installworld problem, do:
913 # cd /usr/src/usr.bin/sed
917 If that doesn't work, then try:
918 # make -k installworld
922 DEVFS is now the default. If you use vinum, make sure that you
923 do not include devfs in your kernel as problems result.
926 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
927 Remove them from your config.
930 ****************************** WARNING ******************************
931 buildkernel has been changed slightly
932 ****************************** WARNING ******************************
933 KERNCONF replaces the variable KERNEL for buildkernel. You
934 should update your scripts and make.conf accordingly.
937 config has changed to allow DEV_FOO as a replacement for NFOO.
938 This requires a new config to build correctly.
941 The kernel option I386_CPU is now mutually exclusive with the
942 other cpu types. If you have an i386 system, be sure that it
943 only had this line. Remove it for all other configurations.
946 Changes to the kernel require it and burncd be in sync.
949 Everyone who has hw.sndunit set to something in
950 /etc/sysctl.conf, it is now hw.snd.unit.
953 ex and vi were broken by some changes to sys/queue.h. If you
954 have a bad vi, you will see make buildworld fail with a core
955 dump while building termcap. You can work around this problem
956 by adding -k to your make buildworld. This will cause the
957 build to complete and install a new vi. Once that's done, you
958 can rebuild again without the -k to pick up anything that
959 might have been ignored by the -k option.
961 Others have suggested that you can just rebuild libc if your
962 vi/ex is dynamically linked, but I've not received any reports
966 There have been some changes to libcrypt in -current. The
967 libscrypt/libdescrypt symlink silliness is gone and the installed
968 libcrypt is fully functional. Be aware of this.
971 Linksys Fast Ethernet PCCARD cards supported by the ed driver
972 now require the addition of flag 0x80000 to their config line
973 in pccard.conf(5). This flag is not optional. These Linksys
974 cards will not be recognized without it.
977 Important new FreeBSD-version stuff: PAM support has been worked
978 in, partially from the "Unix" OpenSSH version. This requires
979 adding the following in pam.conf:
981 sshd auth sufficient pam_skey.so
982 sshd auth required pam_unix.so try_first_pass
983 sshd session required pam_permit.so
989 The random device needs more entropy, so you need to make sure
990 that you've run mergemaster to get a /etc/rc which will seed
991 /dev/random. If you don't and the system hangs after ldconfig,
992 then banging on the keyboard randomly until it unhangs is one
996 ****************************** WARNING ******************************
997 Sendmail has been updated.
998 ****************************** WARNING ******************************
999 o mail.local(8) is no longer installed as a set-user-id binary.
1000 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
1002 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
1004 o Now using sendmail's version of vacation(1).
1005 o The sendmail cf building tools (contrib/sendmail/cf) are installed
1006 in /usr/share/sendmail/cf.
1007 o sendmail.cw changed to local-host-names
1009 More details can be found at
1010 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
1013 The ports tree's new layout is in place. Be sure to update
1014 your entire ports tree, or you will have problems.
1017 The perl build procedure no longer installs miniperl, nor uses
1018 the installed miniperl. It is recommended that you delete
1022 This weekend the ports tree will be updated to a new layout.
1023 It will be in an inconsistent state until noted in the UPDATING
1024 file, or with asami-san's message to the relevant mailing
1025 lists. With this new layout, you'll need to update the whole
1026 tree for anything to work.
1029 There was a change in the passwd format. Need more information.
1032 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
1033 place. Please update boot loader (not the boot blocks) at the
1034 same time as your kernel.
1037 The new pmtimer device is necessary for laptops. Failure to
1038 include the device will cause suspended laptops losing time
1039 when they resume. Include
1041 in your config file and
1042 hint.pmtimer.0.at="isa"
1043 to your /boot/device.hints file.
1046 The random device has been turned into a (pseudo-)device,
1047 rather than an option. The supplied kernel config files have
1048 been updated. You will need to do something similar in your
1049 own kernel config file.
1054 If you prefer to load the loadable module, you need to do
1058 The random device module has been renamed from randomdev.ko to
1059 random.ko. You will need to edit your /boot/loader.conf to
1060 reflect this if you load this module at boot time.
1061 The line should read:
1065 The SMPNG commit has happened. It should work, but if it
1066 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1067 to be a variety of minor issues. Please see 20000905 to make
1068 sure you don't have model loading problems which might at
1069 first blush appear related to SMP.
1072 nsswitch has been imported from NetBSD. Among other things,
1073 this means that /etc/host.conf is no longer used. See
1074 nsswitch.conf(5) instead. Note that at boot time rc.network
1075 will attempt to produce a new nsswitch.conf file for you if you
1076 don't have one, and you have host.conf.
1079 The ucred structure changed size. This breaks the interface
1080 that mountd uses. Trying to use an older mountd with a newer
1081 kernel guarantees a panic. This means that you need to use
1082 kernels newer than today only with matching mountd, but you
1083 needed to do that anyway with the boot loader changes.
1086 The boot loader has been updated. The new default kernel is
1087 now /boot/kernel/kernel.ko. The new default module location
1090 You *MUST* upgrade your boot loader and kernel at the same time.
1091 The easiest way to do this is to do the buildworld/buildkernel/
1092 installkernel/installworld dance.
1094 Furthermore, you are urged to delete your old /modules directory
1095 before booting the new kernel, since kldload will find stale
1096 modules in that directory instead of finding them in the correct
1097 path, /boot/kernel. The most common complaint that this cures
1098 is that the linux module crashes your machine after the update.
1100 if [ ! -d /boot/kernel.old ]; then
1101 mv /modules.old /boot/kernel.old
1102 chflags noschg /kernel.old
1103 mv /kernel.old /boot/kernel.old/kernel.ko
1104 chflags schg /boot/kernel.old/kernel.ko
1108 A new issue with the sendmail upgrade has come to light.
1109 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1110 incorrectly install the default aliases in /etc/mail rather than
1111 move the old one from /etc. So you'll need to manually move the
1112 file, create a symbolic link, remove the old /etc/aliases.db and
1113 run newaliases. For safety sake, you should stop sendmail
1114 while doing this and run the upgrade when locally sourced email
1115 is not likely to be generated.
1118 /boot/device.hints is now required for installkernel to
1119 succeed. You should copy GENERIC.hints for your architecture
1120 into /boot/device.hints. If and only if you compile hints
1121 into your kernel, then this file may be empty. Please note,
1122 if you have an empty or missing /boot/device.hints file and
1123 you neglected to compile hints into your kernel, no boot
1124 messages will appear after the boot loader tries to start the
1128 If you do NOT have ``options RANDOMDEV'' in your kernel and
1129 you DO want the random device then add randomdev_load="YES" to
1133 suidperl is now always built and installed on the system, but
1134 with permissions of 511. If you have applications that use
1135 this program, you are now required to add ENABLE_SUIDPERL=true
1136 to /etc/make.conf. If you forget to do this,
1137 chmod 4511 /usr/bin/suidperl
1138 will fix this until the next build.
1141 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1142 visible changes that may immediately affect your configuration
1144 - New default file locations from src/contrib/sendmail/cf/README
1145 - newaliases limited to root and trusted users
1146 - MSA port (587) turned on by default
1147 - New queue file naming system so can't go from 8.11 -> 8.9
1148 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1149 - FEATURE(`nullclient') is more full featured
1150 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1151 - mail.local FreeBSD-only -b option changed to -B
1152 - See src/contrib/sendmail/RELEASE_NOTES for more info
1155 suidperl (aka sperl) is no longer build by default. You must
1156 specifically define BUILD_SUIDPERL to "true" for it to be build.
1157 Furthermore, we recommend that you remove /usr/bin/sperl* and
1158 /usr/bin/suidperl files from your system unless you have a
1159 specific use for it.
1162 Networking defaults have been tightened. Anybody upgrading
1163 /etc/defaults/rc.conf needs to add the following lines to
1164 /etc/rc.conf if they want to have the same setup
1165 afterwards (unless the variables already are set, of course):
1166 # Enable network daemons for user convenience.
1168 portmap_enable="YES"
1169 sendmail_enable="YES"
1172 If you have null_load="YES" in your /boot/loader.conf, you
1173 will need to change that to nullfs_load="YES".
1176 The "installkernel" target has changed slightly. Now even if
1177 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1178 it will install the MYKERNEL file (built with the buildkernel
1179 target) as /kernel rather than /MYKERNEL. Those who have
1180 updated their /boot/loader.conf files to point to /MYKERNEL
1181 should remove that entry or perform manual rename of /kernel
1185 If you use CVSUP or CTM to get CVS trees, AND you used to get
1186 the old crypto files from internat.freebsd.org AND you check
1187 out files from the CVS tree with the cvs command, please read
1188 http://people.freebsd.org/~imp/internat.txt
1189 for details on potential problems that you might have and how
1192 If you are merely a mirror, or don't answer yes to each of the
1193 clauses above, you needn't worry.
1196 /etc/security has been updated to print the inode number of
1197 setuid programs that have changed. You will see a large spike
1198 in the number of changed programs the first time when you run
1199 mergemaster to get a new /etc/security.
1202 /dev/random now has good entropy collection (from the keyboard
1203 and sysmouse drivers). Please ensure that either `options
1204 RANDOMDEV' is present in your kernel config file or that
1205 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1206 not have the /dev/random driver, OpenSSL (and consequently
1207 lots of crypto tools (like SSH)) will fail with strange
1208 errors. (see below, 20000624).
1210 FreeBSD-current is safe again to run Crypto.
1213 phk made the malloc default options AJ. This may slow things
1214 down and uncover other latent bugs in the code. If you need to
1215 run at full speed, you can disable this by doing the following:
1216 ln -s aj /etc/malloc.conf
1219 libftpio's version was accidentally bumped a few days ago. This
1220 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1221 before doing your next buildworld/installworld pair. It certainly
1222 won't hurt to remove it before the update procedure. It will
1223 break fetch until a new one is built, but ftp can be used in the
1227 The crypto packages have changed for the cvsup. This has been done
1228 in a backward compatible way, but the old packages will go away at
1229 some point in the future. Look at /usr/share/examples/cvsup for
1233 With the new sys/modules/sound/drivers/*, you will need to
1234 set SYSDIR until you do an installworld after July 7th.
1237 rc.shutdown and rc will now call the rc.d scripts with start
1238 or stop. This may cause some harmless warnings from older
1239 rc.d scripts that haven't been updated.
1242 The libfetch based version of fetch has gone into the tree.
1243 Minor problems may result on some of the less popular sites,
1244 which should be reported to des@freebsd.org.
1247 From approximately this date forward, one must have the crypto
1248 system installed in order to build the system and kernel.
1249 While not technically strictly true, one should treat it as
1250 required and grab the crypto bits. If you are grabbing CVS
1251 trees, src-all and cvs-crypto should be treated as if they
1252 were required. You should check with the latest collections
1253 to make sure that these haven't changed.
1256 Mark Murray just committed the first parts of a cleanup of
1257 /dev/zero, et al. This is also cleaning up /dev/random.
1258 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1259 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1260 until Mark can merge in the fixes to this work in progress.
1261 openssh and openssl should not be used to generate keys from this
1262 date to the completion of the work.
1264 If you must operate at this reduced level of security, add '
1265 options RANDOMDEV' to your kernel or modload the randomdev
1266 module. You may also need to copy a new MAKEDEV to /dev and
1267 recreate the random and urandom devices.
1270 The license on the softupdates is now a standard 2 clause
1271 BSD license. You may need to remove your symbolic links
1272 that used to be required when updating.
1275 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1276 the config file update procedure.
1277 http://people.freebsd.org/~imp/config-upd.html
1278 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1279 isn't buildable. However, you can generate a LINT file:
1280 cd /sys/<ARCH>/conf && make LINT
1283 Binutils 2.10 have hit the tree, or will shortly. As soon
1284 as they do, the problem noted in 20000522 will be resolved and
1285 that workaround will no longer be required.
1288 phk removed the compatibility creation of wd devices in the
1289 ad driver. If you haven't done so already, you must update
1290 your fstab, etc to use the ad devices instead of the wd
1293 In addition, you'll need to update your boot blocks to a
1294 more modern version, if you haven't already done so. Modern
1295 here means 4.0 release or newer (although older releases
1299 Peter took an axe to config(8). Be sure that you read his mail
1300 on the topic before even thinking about updating. You will
1301 need to create a /boot/device.hints or add a hints directive
1302 to your config file to compile them in statically. The format
1303 of the config file has changed as well. Please see GENERIC or
1304 NEWCARD for examples of the new format.
1306 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1307 says that it has been fixed, assume that must use the hints mechanism
1308 in the loader if you need to use a machine with very old ISA cards
1312 A new set of binutils went into the tree today. Anybody
1313 building a kernel after this point is advised that they need
1314 to rebuild their binutils (or better yet do a
1315 buildworld/installworld) before building a new kernel.
1317 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1318 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1319 is recommended that you don't set this option until the problem
1323 The ethernet drivers were all updated to clean up the BPF handling.
1326 The problems with boot blocks on the alphas have been corrected.
1327 This will require some care in updating alphas. A new libstand
1328 is requires for the boot blocks to build properly.
1331 Recompile all kld modules. Proper version dependency info
1335 Modules have been disconnected from the buildworld tree and
1336 connected to the kernel building instead.
1339 You may need to build gperf
1340 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1341 when upgrading from 4.0 -> current. The build system now uses
1342 an option only in -current.
1345 The method that we brand ELF binaries has changed to be more
1346 acceptable to the binutils maintainers. You will need to
1347 rebrand your ELF binaries that aren't native. One problem
1348 binary is the Linux ldconfig. After your make world, but
1349 before you reboot, you'll need to issue:
1350 brandelf -t Linux /compat/linux/sbin/ldconfig
1351 if you have Linux compatibility enabled on your machine.
1354 If you have really bad/marginal IDE drives, you may find they
1355 don't work well. Use pio mode instead. The easiest way to
1356 cope if you have a problem combination is to add:
1357 /sbin/sysctl hw.ata.ata_dma=0
1358 to the start of /etc/rc.conf.
1361 The ISA and PCI compatibility shims have been connected to the
1362 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1363 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1364 include the appropriate option in your kernel config. Drivers
1365 using the shims should be updated or they won't ship with
1366 5.0-RELEASE, targeted for 2001.
1369 We've entered the traditional post release dumping party.
1370 Large kernel changes are being committed and are in the
1371 works. It is important to keep the systems' klds and kernel
1372 in sync as kernel interfaces and structures are changing.
1373 Before reporting kernel panics, make sure that all modules
1374 that you are loading are up to date.
1377 If you are upgrading from an older version of FreeBSD, you
1378 need to update your boot blocks as well. 'disklabel -B ad0'
1379 will do the trick. This isn't critical until you remove your
1380 wd device entries in /dev, at which point your system will not
1384 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1385 to upgrade to 4.0 from 3.x.
1391 Avoid using make -j when upgrading. From time to time in the
1392 past there have been problems using -j with buildworld and/or
1393 installworld. This is especially true when upgrading between
1394 "distant" versions (eg one that cross a major release boundary
1395 or several minor releases, or when several months have passed
1396 on the -current branch).
1398 Sometimes, obscure build problems are the result of environment
1399 poisoning. This can happen because the make utility reads its
1400 environment when searching for values for global variables.
1401 To run your build attempts in an "environmental clean room",
1402 prefix all make commands with 'env -i '. See the env(1) manual
1403 page for more details.
1407 If you are updating from a prior version of FreeBSD (even one just
1408 a few days old), you should follow this procedure. With a
1409 /usr/obj tree with a fresh buildworld,
1410 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1411 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1413 To just build a kernel when you know that it won't mess you up
1414 --------------------------------------------------------------
1415 This assumes you are already running a 5.X system. Replace
1416 ${arch} with the architecture of your machine (e.g. "i386",
1417 "alpha", "amd64", "ia64", "pc98", "sparc64", etc).
1419 cd src/sys/${arch}/conf
1420 config KERNEL_NAME_HERE
1421 cd ../compile/KERNEL_NAME_HERE
1426 If this fails, go to the "To build a kernel" section.
1428 To rebuild everything and install it on the current system.
1429 -----------------------------------------------------------
1430 # Note: sometimes if you are running current you gotta do more than
1431 # is listed here if you are upgrading from a really old current.
1433 <make sure you have good level 0 dumps>
1434 <maybe fix /etc/fstab> [7]
1436 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1437 make installkernel KERNCONF=YOUR_KERNEL_HERE
1439 <reboot in single user> [3]
1440 /etc/rc.d/preseedrandom [10]
1447 To cross-install current onto a separate partition
1448 --------------------------------------------------
1449 # In this approach we use a separate partition to hold
1450 # current's root, 'usr', and 'var' directories. A partition
1451 # holding "/", "/usr" and "/var" should be about 2GB in
1454 <make sure you have good level 0 dumps>
1457 <maybe newfs current's root partition>
1458 <mount current's root partition on directory ${CURRENT_ROOT}>
1459 make installworld DESTDIR=${CURRENT_ROOT}
1460 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1461 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1462 ${CURRENT_ROOT}/boot/device.hints # as needed
1463 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1464 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1465 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1466 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1467 <reboot into current>
1468 <do a "native" rebuild/install as described in the previous section>
1469 <maybe install compatibility libraries from /usr/src/lib/compat>
1473 To upgrade in-place from 4.x-stable to current
1474 ----------------------------------------------
1475 # 5.x uses more space than 4.x. Also, the location of kernel
1476 # modules has changed. If you are installing 5.0 onto a 4.x
1477 # system, you'll need about 30MB of free disk space on your /
1478 # partition. If you have less than this, you may encounter difficult
1479 # to back out of problems with this procedure. If /tmp is on
1480 # the / partition, you may want to completely remove all its content
1481 # before upgrading, as this can be a common source of shortage of
1484 <make sure you have good level 0 dumps>
1485 <maybe fix /etc/fstab> [7]
1487 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1488 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1489 make installkernel KERNCONF=YOUR_KERNEL_HERE
1490 cd src/sys/boot ; make install [6]
1492 <reboot in single user> [3]
1493 /etc/rc.d/preseedrandom [10]
1495 rm -rf /usr/include/g++
1500 Make sure that you've read the UPDATING file to understand the
1501 tweaks to various things you need. At this point in the life
1502 cycle of current, things change often and you are on your own
1503 to cope. The defaults can also change, so please read ALL of
1504 the UPDATING entries.
1506 Also, if you are tracking -current, you must be subscribed to
1507 freebsd-current@freebsd.org. Make sure that before you update
1508 your sources that you have read and understood all the recent
1509 messages there. If in doubt, please track -stable which has
1510 much fewer pitfalls.
1512 [1] If you have third party modules, such as vmware, you
1513 should disable them at this point so they don't crash your
1516 [2] If you have legacy ISA devices, you may need to create
1517 your own device.hints to reflect your unique hardware
1520 [3] From the bootblocks, boot -s, and then do
1525 adjkerntz -i # if CMOS is wall time
1526 Also, when doing a major release upgrade, it is required that
1527 you boot into single user mode to do the installworld.
1528 For the 4.x -> 5.0 upgrade, you will also see many messages about
1529 needing to recompile your userland. These are harmless and can
1530 be ignored while you proceed to the next step.
1532 [4] Note: This step is non-optional. Failure to do this step
1533 can result in a significant reduction in the functionality of the
1534 system. Attempting to do it by hand is not recommended and those
1535 that pursue this avenue should read this file carefully, as well
1536 as the archives of freebsd-current and freebsd-hackers mailing lists
1537 for potential gotchas.
1539 [5] Usually this step is a noop. However, from time to time
1540 you may need to do this if you get unknown user in the following
1541 step. It never hurts to do it all the time. You may need to
1542 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1543 install) after the buildworld before this step if you last updated
1544 from current before 20020224 or from -stable before 20020408.
1546 [6] 4.x boot loader can be used to boot a 5.x system, however
1547 it is difficult to do that at best. If you wish to try, then
1548 you should interrupt the boot and at the ok prompt type:
1550 ok boot /boot/kernel/kernel
1551 If this fails to work, you must install a new boot loader as
1554 [7] Before you upgrade, please make sure that you are not using
1555 compatibility slices. These are device names of the form, on i386
1556 and other architectures that use MBR slicing, /dev/ad0a without the
1557 actual slice name. Chances are excellent that these will break.
1558 You generally must update these entries to use the post FreeBSD
1559 2.x form of /dev/ad0s1a.
1561 [8] In order to have a kernel that can run the 4.x binaries
1562 needed to do an installworld, you must include the COMPAT_FREEBSD4
1563 option in your kernel. Failure to do so may leave you with a system
1564 that is hard to boot to recover.
1566 [9] When checking out sources, you must include the -P flag to have
1567 cvs prune empty directories.
1569 [10] In order to create temporary files, /dev/random must be
1570 initialized by feeding data into it. /etc/rc.d/preseedrandom
1574 This file contains a list, in reverse chronological order, of major
1575 breakages in tracking -current. Not all things will be listed here,
1576 and it only starts on March 15, 2000. Updating files can found in
1577 previous releases if your system is older than this.
1579 Copyright information:
1581 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1583 Redistribution, publication, translation and use, with or without
1584 modification, in full or in part, in any form or format of this
1585 document are permitted without further permission from the author.
1587 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1588 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1589 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1590 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1591 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1592 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1593 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1594 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1595 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1596 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1597 POSSIBILITY OF SUCH DAMAGE.
1599 If you find this document useful, and you want to, you may buy the
1602 Contact Warner Losh if you have any questions about your use of