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 FreeBSD/sparc64 platform is changing time_t from 32-bits to
22 64-bits. This is a very major incompatible change, so people
23 using FreeBSD/sparc64 *must* read the UPDATING.64BTT file for
24 detailed instructions on how to make this upgrade. People
25 upgrading FreeBSD on other platforms can ignore this event.
28 The packet filter (pf) is now installed with the base system. Make
29 sure to run mergemaster -p before installworld to create required
30 user accounts. If you do not want to build pf with your system you
31 can use the NO_PF knob in make.conf.
32 Also note that pf requires "options PFIL_HOOKS" in the kernel. The
33 pf system consists of the following three devices:
35 device pflog # optional
36 device pfsync # optional
39 If you are having trouble with the libc_r -> libpthread transition
40 (see the 20040130 entry), place the following lines at the top of
43 libc_r.so.5 libpthread.so.1
44 libc_r.so libpthread.so
46 This will cause all programs and libraries linked against libc_r
47 to use libpthread instead.
50 Some sshd configuration defaults have changed: protocol version 1
51 is no longer enabled by default, and password authentication is
52 disabled by default if PAM is enabled (which it is by default).
53 OpenSSH clients should not be affected by this; other clients may
54 have to be reconfigured, upgraded or replaced.
57 The ABIs defined in <resolv.h> and <netdb.h> have been updated
58 to support improved reentrancy. Multi-threaded programs that
59 reference the "_res" or "h_errno" symbols may experience some
60 problems if they are not recompiled. Single-threaded programs
61 should remain unaffected.
64 routed has been updated in the base system from the vendor
65 sources, routed v2.27, from rhyolite.com. This change means that
66 for users who use RIP's MD5 authentication feature, FreeBSD
67 -CURRENT's routed is now incompatible with previous versions
68 of FreeBSD; however it is now compatible with implementations
69 from Sun, Cisco and other vendors.
72 The tcpcb structure has changed and makes a recompile of libkvm
73 and related userland network utilities neccessary.
76 The cdevsw structure has changed in two externally visible ways.
77 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
78 Second, the d_version field must be filled in with D_VERSION.
79 Drivers outside the tree will need to be updated.
82 The /etc/rc.d/ttys script has been removed. It is no longer
83 necessary since devfs has been mandatory for some time.
86 libkse has been renamed back to libpthread and is now the
87 default threads library. The gcc -pthread option has also
88 been changed to link to libpthread instead of libc_r. For
89 alpha and sparc64 machines, libkse is not renamed and links
90 are installed so that libpthread points to libc_r. Until
91 the ports system is updated to handle this change, it is
92 recommended that folks install an /etc/libmap.conf(5) that
93 maps libc_r to libpthread. If you have any binaries or
94 libraries linked to libkse, then it is also recommended
95 that you map libkse to libpthread. Anyone that is using
96 nvidia supplied drivers and libraries should use a libmap.conf
97 that maps libpthread to libc_r since their drivers/libraries
98 do not work with libpthread.
101 ULE has entered into its probationary period as the default scheduler
102 in GENERIC. For the average user, interactivity is reported to be
103 better in many cases. On SMP machines ULE will be able to make more
104 efficient use of the available parallel resources. If you are not
105 running it now, please switch over, replacing the kernel option
106 SCHED_4BSD with SCHED_ULE.
109 Move LongRun support out of identcpu.c, where it hardly
110 belongs, into its own file and make it opt-in, not mandatory,
111 depending on CPU_ENABLE_LONGRUN config(8) option.
114 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
115 if the login process is unable to successfully set the
116 process credentials to include all groups defined for the
117 user. The current kernel limit is 16 groups; administrators
118 may wish to check that users do not have over 16 groups
119 defined, or they will be unable to log in.
122 The ACPI module has been reactivated. It is no longer required
123 to compile ACPI support into kernels statically.
126 The statfs structure has been updated with 64-bit fields to
127 allow accurate reporting of multi-terabyte filesystem
128 sizes. You should build world, then build and boot the new kernel
129 BEFORE doing a `installworld' as the new kernel will know about
130 binaries using the old statfs structure, but an old kernel will
131 not know about the new system calls that support the new statfs
133 Note that the backwards compatibility is only present when the
134 kernel is configured with the COMPAT_FREEBSD4 option. Since
135 even /bin/sh will not run with a new kernel without said option
136 you're pretty much dead in the water without it. Make sure you
137 have COMPAT_FREEBSD4!
138 Running an old kernel after a `make world' will cause programs
139 such as `df' that do a statfs system call to fail with a bad
140 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
141 that cfsd (ports/security/cfs) needs to be recompiled after
142 these changes are installed.
144 ****************************DANGER*******************************
146 DO NOT make installworld after the buildworld w/o building and
147 installing a new kernel FIRST. You will be unable to build a
148 new kernel otherwise on a system with new binaries and an old
152 Some netgraph string length constants have been changed. This
153 change requires the netgraph kernel modules and all netgraph
154 userland components to be in sync. Especially users who require
155 netgraph to boot need to make sure to have world and kernel in
156 sync before rebooting.
159 Hyperthreading logical CPU's are no longer probed by default
160 when using the MP Table. If ACPI is being used, then logical
161 CPUs will be probed if hyperthreading is enabled in the BIOS.
162 If ACPI is not being used and hyperthreading is enabled in the
163 BIOS, logical CPUs can be enabled by building a custom kernel
164 with the option MPTABLE_FORCE_HTT enabled.
167 The i386 APIC_IO kernel option has been replaced by
168 'device apic'. The ACPI module has also been temporarily
169 disabled, so ACPI must be statically compiled into your
170 kernel using 'device acpi' if you wish to use the ACPI driver.
173 The API and ABI of struct ifnet have been changed by removing
174 the if_name and if_unit members and replacing them with
175 if_xname, if_dname, and if_dunit. All network drivers and most
176 userland programs which include net/if_var.h must be updated
177 and recompiled. __FreeBSD_version has been bumped to 501113 to
181 Changes to the cdevsw default functions have been made to remove
182 the need to specify nullopen() and nullclose() explicitly.
183 __FreeBSD_version bumpted to 501110.
186 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
187 mount_cd9660(8) need to be in sync with kernel.
190 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
191 also be explicitly configured. Previously this dependency was
192 magically handled through some cruft in net/pfil.h; but that has
193 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
194 will fail with obtuse errors in ip_fil.c.
197 Fix a bug in arplookup(), whereby a hostile party on a locally
198 attached network could exhaust kernel memory, and cause a system
199 panic, by sending a flood of spoofed ARP requests. See
200 FreeBSD-SA-03:14.arp.
203 A change to /etc/defaults/rc.conf now causes inetd to be started
204 with `-C 60' if it is not overridden in /etc/rc.conf. This
205 causes inetd to stop accepting connections from an IP address
206 that exceeds the rate of 60 connections per minute.
209 The following rc.d scripts have been removed and should be
210 deleted from your installation: atm2.sh atm3.sh devdb
211 localdaemons network1 network2 network3. Depending on when
212 you last updated world and used mergemaster(8) you may or
213 may not have problems during the rc boot sequence. The simplest
214 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
215 The atm2.sh atm3.sh and devdb scripts were removed some time
216 ago, so depending on when you installed -CURRENT these scripts
217 may or may not exist on your system.
220 ATAng has been committed. You need to build world as sys/ata.h
221 has changed, and userland atacontrol depends on it.
222 If you use ATA SW raids you need "device ataraid" in your
223 kernel config file, as it is no longer pulled in automatically.
226 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
227 Among other things, this changes the device enumeration to be
228 closer to Solaris. Be aware that, this can even cause the machine
229 to not boot without manual intervention before the fstab is adjusted.
232 All current USB and Firewire quirks in da(4) have been deprecated
233 and will be removed for 5.2. If this causes failure for your
234 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
235 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
236 so the quirk can be re-enabled.
239 Problems with entry 20030714 have been corrected and no known issues
240 with /rescue and -j exist for host systems after this point in time.
243 FPU-less support has been removed from FreeBSD. Chances are you won't
244 notice. 386+387 support should still work after this change, but
245 it is now a minimum requirement for the i386 port that you have real
249 Some people are having problems with changes related to /rescue.
250 If you are building -j N, you will need to define NO_RESCUE. Others
251 will need to define it if /rescue has issues with their environment.
252 People should report those issues to current@.
255 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
256 across this point. Further, it might be a good idea to remove
260 Remove deprecated locale names and transition period code
261 for them, finishing switching to the new scheme. Check your
262 LANG environment variable.
265 CCD has been changed to be a fully GEOMified class. Kernel
266 and ccdconfig(8) needs to be in sync, this is particularly
267 important to remember beforehand if your source tree is on
268 a ccd device. Consider making a copy of the old ccdconfig
269 into /boot/kernel.good or wherever you keep your backup
273 There was a small window in which sed(1) was broken. If you
274 happen to have sed(1) installed during that window, which is
275 evidenced by an inability to build world with the failure
276 given below, you need to manually build and install sed(1)
277 (and only sed(1)) before doing anything else. This is a one-
278 time snafu. Typical failure mode:
280 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
281 targmatch.h:7:1: null character(s) ignored
282 targmatch.h:12:1: null character(s) ignored
283 targmatch.h:16:1: null character(s) ignored
286 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
287 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
288 usr.bin/sed/process.c).
291 Kerberos 5 (Heimdal) is now built by default. Setting
292 MAKE_KERBEROS5 no longer has any effect. If you do NOT
293 want the "base" Kerberos 5, you need to set NO_KERBEROS.
296 groff has been updated. If you try to do a buildworld and
297 get an infinite loop in troff, update to May 4th or newer. If you
298 have a newer kernel than userland, you may need to set the OSRELDATE
299 to 500110 in your environment before starting a buildworld.
302 The old rc system has been removed. Please report any problems
303 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
304 Your personal versions of these files will not be removed, so you can
305 continue to use them. However, you should take great care when updating,
306 especially when using mergemaster, since the compatibility code that
307 utilizes these old scripts has also been removed.
310 A bug has been fixed in /dev/devctl which would cause devd
311 to hang on boot, were it not for a workaround in devd. The
312 work around in devd will be removed around 20030507. You
313 have until then to upgrade your kernel before updating
314 userland. In general, you should have a userland and
315 kernel that's in sync with each other. However, given the
316 effects of this bug (hang on boot when starting devd), some
320 Alphas with libc from between 20030312 and 20030329 exhibit
321 floating point exceptions (FPEs), most notably in awk(1)
322 while upgrading the system through a buildworld.
324 So, to successfully upgrade your Alpha, you must either
325 downgrade your libc.so to a pre-20030312 version, or update
326 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
327 to CFLAGS, then forcibly rebuild and install libc:
329 cd /usr/src/lib/libc && \
330 make cleandir && make obj && \
331 make -DNOMAN -DNOPROFILE all && \
332 make -DNOMAN -DNOPROFILE install
335 sendmail 8.12.7 has been imported. It has one important
336 change for IPv6 users. The default submit.mc now uses
337 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
338 used to connect to the MTA. Users on IPv6-only machines
339 will need to edit /etc/mail/submit.mc appropriately.
342 NODEVFS option has been removed and DEVFS thereby made standard.
343 This makes all references to MAKEDEV obsolete, and they should
344 be removed when convenient.
347 The name of the device for the ofw console has changed, sparc64 users
348 must run mergemaster to update their installed /etc/ttys.
351 The scheduler framework has grown a second scheduler and consequently
352 you must specify one and only one scheduler in your kernel config.
353 The cvs config files have been updated to use the old scheduler
354 which may be selected via 'options SCHED_4BSD'. If you would like
355 to try the new, much more experimental, scheduler please try
356 'options SCHED_ULE' and contribute to the arch@ discussion.
359 A new version of the wi driver has been imported into the tree.
360 One now must have device wlan in the config file for it to operate
363 In addition, there have been some changes to how wi devices are
364 configured for point to point links to bring it more in line
365 with the former way of doing things, as well as compatibility
369 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
370 used an incompatible form of ABI for returning structures and unions
371 which FreeBSD's GCC maintainers were not aware of relative to previous
372 versions of FreeBSD. We have gone back to the ABI for now, and any
373 code compiled which is required to interoperate with other code (not
374 built at the same time) returning structs or unions should be
378 A name change in /etc/netconfig has been reverted to stay
379 compatible with suns TIRPC and also with NetBSD. You need
380 to run mergemaster after make world. A new libc does still work
381 with an outdated /etc/netconfig for some time, but you'll get
382 a warning. This warning will be removed in 20030301.
385 The recent binutils upgrade marks a kernel flag day on
386 sparc64: modules built with the old binutils will not work
387 with new kernels and vice versa. Mismatches will result in
388 panics. Make sure your kernel and modules are in sync.
391 The value of IPPROTO_DIVERT has changed. Make sure to keep
392 your kernel, netstat, natd and any third-party DIVERT
396 Old, compatibility slices have been removed in GEOM kernels.
397 This means that you will have to update your /etc/fstab to
398 not use disk devices of the form /dev/ad0a. Instead, you
399 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
400 partition really is on. The old device names have gone
401 away, so if you use them anywhere else, you must also adjust
402 those uses. (This doesn't affect the disks formatted in
403 the ``dangerously-dedicated'' mode.)
406 Alphas with kernels from between 20020830 and 20021023 and/or
407 rtld (ld-elf.so.1) older than 20021023 may experience problems
408 with groff while doing a buildworld (kernel: "out of memory",
409 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
410 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
412 So, to successfully upgrade your Alpha, you must either
413 upgrade your kernel and rtld first (which might be a bit
414 tricky), or avoid running the bootstrapped groff during the
415 "transitional" buildworld. To avoid running groff during the
416 transitional upgrade run make buildworld with -DNOMAN,
417 -DNO_SHAREDOCS, and -DNO_LPR.
420 gcc has been upgraded to 3.2. It is not all binary compatible
421 with earlier versions of gcc for c++ programs. All c++
422 programs and libraries need to be recompiled.
424 Also, if you encounter g++ issues, rm /usr/include/g++/* before
425 doing an installworld to make sure that stale files are removed.
428 Our /etc/termcap now has all the entries from the XFree86 xterm
429 almost unchanged. This means xterm now supports color by default.
430 If you used TERM=xterm-color in the past you now should use
431 TERM=xterm. (xterm-color will lead to benign warnings).
434 A "bug" in gcc(1) that was hiding warning in system headers was
435 fixed. It's probably time to add -DNO_WERROR to your make line
439 COPY is being deprecated. The 20010530 change was reverted, as
440 it causes far more pain than was expected, and to always compare
441 before installing, please use INSTALL="install -C" again. The
442 -C option is now silently ignored when used with the -d option.
445 Problems with libc_r clients like KDE and GNOME have been resolved.
446 There are still some minor problems with some signals but the
447 system is stable enough for general use again. SMP is less so than UP
448 but each can successfully complete multiple buildworlds.
449 Libkvm needs to be recompiled due to KSE.
452 Now would be a bad time to upgrade. Something in or near the
453 KSE commit totally broke programs using libc_r like KDE and
457 The k5su utility installed as part of Kerberos 5 is no longer
458 installed with the set-user-ID bit set by default. Add
459 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
460 with the set-user-ID bit set.
463 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
464 Unfortunately our native GDB (at version 4.18) does not understand
465 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
466 generated debugging information for our native GDB.
469 Due to the way CVS works, it may not properly update src/contrib/gcc
470 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
471 and then do a cvs update.
474 When exec'ing set[ug]id executables, the kernel now ensures that the
475 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
478 New sendmail startup scripts have been installed to make it
479 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
480 variable sendmail_enable to "NO" no longer prevents any sendmail
481 daemons from starting. Instead, either set sendmail_enable to
482 "NONE" or change mta_start_script to a script for starting
483 an alternative MTA. Setting mta_start_script to "" will
484 also prevent any MTA from being started at boot.
487 UCONSOLE is no longer a valid kernel option.
490 FreeBSD 5.0 DP-1 was basically branched today.
493 Warnings are now errors in the kernel. Unless you are a developer,
494 you should add -DNO_WERROR to your make line.
497 sendmail 8.12.2 has been imported. The sendmail binary is no
498 longer a set-user-ID root binary and the infrastructure to support
499 command line mail submission has changed. Be sure to run
500 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
501 and /etc/mail) and read /etc/mail/README for more details.
503 Due to the import of sendmail 8.12.2, a new user and group are
504 required in order for sendmail to run as a set-group-ID
505 binary. A 'make installworld' will use the new user and group
506 to set the owner and group of /var/spool/clientmqueue and will
507 fail if the new user and group do not exist. The 'smmsp' user
508 and group must be merged from src/etc/group and
509 src/etc/master.passwd before using 'make installworld'.
510 'mergemaster -p' will do this. You may need to install
511 mergemaster before this will work if you are updating from a
512 very old version of current. The updating recipe has changed
516 The preferred configuration method for PAM is now /etc/pam.d/
517 rather than /etc/pam.conf. If you have an unmodified
518 pam.conf, just delete it after your next mergemaster run. If
519 you have local modifications, you can use
520 /usr/src/etc/pam.d/convert.pl to incorporate them into your
523 Please see the following url for more details:
524 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
526 If anyone here is already using the new rc.conf(5) variable
527 networkfs_types, please note that it has changed
528 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
531 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
532 started out its life in the ISDN4BSD project as an offspring
533 from sys/net/if_spppsubr.c, which eventually got a life of its
534 own. All the accumulated features and bugfixes of the i4b
535 version have now been merged back into the base system's
536 version now. The only user-visible change resulting from this
537 is that i4b's sppp(4) interfaces are to be managed with
538 spppcontrol(8) again, since ispppcontrol(8) has been retired
539 as well. (There has never been rc file support for
540 ispppcontrol in -current, but only in -stable. That will be
541 reverted by the time the changes are MFCed.)
544 The fdc(4) driver has been updated and now automatically
545 recognizes media in `standard' formats (like 1440 KB and
546 720 KB for a 3.5" high-density drive) when accessing the
547 default device node (e. g. /dev/fd0). The old variety of
548 floppy device nodes /dev/fd*.* is no longer present by
549 default, devices can be created (in DEVFS) on demand. They
550 will need to be customized then for `odd' densities using
554 The bugs in procfs' debugging support code have been fixed,
555 and truss(1) now works again.
558 Daily security checks have been split out to use the periodic(8)
559 scripts. Some change in configuration may be necessary. Please
561 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
565 sos added VCD/SVCD support to ata driver and that needs the
566 kernel and burncd to be in sync.
569 The procfs pseudo-filesystem has now been converted to use the
570 pseudofs framework. If you have 'options PROCFS' in your
571 kernel config, you'll need to add 'options PSEUDOFS' if it's
574 This change temporarily breaks truss(1); use ktrace(1) instead
575 until the issue has been resolved.
578 A security hole in OpenSSH involving `UseLogin yes' has been
582 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
583 after this date. You need to do this only once.
586 Most of the awk issues have been resolved. Some rough
587 edges may be left, but for the most part things should be
588 back to "normal." For CURRENT's usual definition of "normal."
591 Awk has been upgraded to the one true awk from bell labs. Expect
592 choppy waves in the upgrade process.
595 The asr driver problem has been resolved.
598 Due to changes in other parts of the system, the asr driver
599 now causes the system to panic on boot. Do not use it pending
600 correction. Comment it out of any kernel config file that you
601 try to use from this date forward.
604 When crossbuilding, use TARGET=xxx where you used to use
605 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
606 unless you are changing both of them. To cross build pc98 on
607 an alpha, for example, you need to set TARGET=pc98 and
611 The kernel interface that burncd depends on has changed.
612 You must recompile both the kernel and userland applications
616 When crossbuilding, please set TARGET_ARCH rather than
617 MACHINE_ARCH to indicate the target. In the future, one will
618 set TARGET_MACHINE where you set MACHINE now. At the moment,
619 setting MACHINE alone for same MACHINE_ARCH machines works
620 (eg, you can build pc98 on an i386 machine and vice versa).
623 Some weird problems result from using ACPI on some machines.
624 To disable ACPI you can add
625 hint.acpi.0.disabled="1"
626 to /boot/loader.conf (or by putting set X=Y at the boot
629 Alternatively, you can remove it from /boot/kernel/acpi.ko
630 or use the MODULES_OVERRIDE function in your kernel config
631 file and not list acpi in that list.
634 The buildworld has been fixed. You may need to install
635 the 4.x compatibility libraries for some old binaries
636 to work. Add COMPAT4X=true to your /etc/make.conf to
637 get them installed on every installworld, or execute the
638 following to get them installed only once:
639 cd src/lib/compat/compat4x.<arch>
641 You will see ``__stdoutp undefined'' until you do this.
644 There's a bug in the world build process. The cross-tools
645 are build with the NEW headers, but the OLD libc.a. This
646 leads to all kinds of problems with the new libc. A temporary
648 CFLAGS="-O -pipe -D_OLD_STDIO"
649 before building world when upgrading from 4.x to current. This
650 can be removed afterwards.
652 A proper fix to the buildworld target is needed.
655 Peter has committed his new kthread nfs client/server code.
656 NFS may be unstable after this date.
659 KSE has hit the tree. Lots of things are now different in
660 the kernel. While a few problems were introduced in the
661 initial commit, most of the major ones have been found and
665 In OLDCARD, CardBus bridges appear to be stable. The work
666 arounds described in the 20010604 entry are now no longer
667 necessary and will be ignored. Most insert/remove problems
668 have been rectified around this date.
671 named now runs as user bind and group bind rather than as
672 root. If named_enable is set to YES in /etc/rc.conf, ensure
673 that user bind is available in /etc/passwd (using vipw(8))
674 and that group bind is available in /etc/group. Also make
675 sure that user or group bind has read (and not write)
676 permission for your name server configuration and that it
677 has read and write permission for your slave zone files and
680 If you wish to continue to run named as root (a less secure
681 alternative), add a line to /etc/rc.conf saying
686 The PAM libraries have had an API upgrade that is beyond
687 the ability of the shared library major number to handle.
688 It is manifested by PAM-using ports dumping core. The
689 solution is to rebuild those ports.
692 The kernel compile module has moved from src/sys/compile/FOO
693 to src/sys/${MACHINE}/compile/FOO.
696 The pccard modem issue from 20010613 has been corrected.
697 OLDCARD support is still a little weak in -current. slot 1 is
698 known not to work on some TI based cardbus bridges. Some
699 cardbus bridges do not properly detect insert/removal events.
700 IRQ configuration needs more safety belts.
703 Softupdates problems have been corrected.
706 Peter ripped out the linkerset support. You must, as always,
707 rerun config after you cvsup if you are using the traditional
708 kernel building methods.
711 pccard modems may not work with current after 20010604 date. Some
712 do, others result in panics. *MAKE*SURE* that you update your
713 config and /etc/rc.conf ala the 20010604 entry, or you will have
714 problems (this issue will be fixed, it just hasn't been yet).
717 SOFTUPDATES seem to be broken since the middle of May or so. Do not
718 use them in current. You can disable softupdates on all mounted
719 partitions, or remove SOFTUPDATES the kernel config file.
722 After Peter's commits to the hints code, people have been noticing
723 that certain devices are attached (or try to) twice. This is due
724 to having both static hints as well as a /boot/device.hints. To
725 work around this issue, please use only one or the other mechanism
726 until this bug is fixed.
728 Please note that a feature of config is that if you have config
729 file FOO and FOO.hints, it automatically adds FOO.hints to the
730 hints.c file, whether you want it to or not.
733 Locale names have changed to match other systems better.
736 pccard support for pci cards has been committed. You must change
737 your /etc/pccard.conf irq lines. It must match the irq used by
738 pcic device. Interrupt storms may result if you fail to do this.
739 Interrupt storms look a lot like a hang.
741 You must also install a new pccardd, otherwise you will get an
742 interrupt storm at card reset time (just after it tells you what
745 pccardd_flags="-I" is necessary for the time being. It tells pccardd
746 not to ask the kernel if the interrupt is really free or not before
747 using it. You can either change the /etc/pccard.conf irq lines to
748 match pcic, or add "-i X" to the pccardd_flags.
751 INSTALL=install -C is being deprecated. If you want to do this,
752 use COPY=-C instead. The former method will be supported for only
753 a limited time. If you see
755 install: warning: the -d and -C options may not be specified together
757 in your makeworld, then you need to migrate towards using
761 It appears that vm is now stable enough to use again. However,
762 there may be other problems, so caution is still urged. alpha
763 definitely is in bad shape.
766 Minor repo damage has happened. This may cause problems
767 with cvsup of ports. If you get errors, please see
768 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
769 at the bottom for details on a workaround. The error message
771 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
774 Vm and/or swapping are busted on -current. Please be patient.
777 pccard has had much reorganizational work done to it over
778 the past few days. Everything should still work, but if
779 not, please contact imp@freebsd.org.
782 ata ioctl changed. Make sure to recompile both kernel and
783 userland at the same time.
786 New ncurses imported.
789 DEVFS is now opt out, not opt in. Barring major problems, this
790 will be the only way to go starting July 1.
793 OpenSSH has been updated to 2.9. Some defaults are different,
794 including RhostsRSAAuthentication, which changes from yes to no.
797 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
800 Building perl was broken at 02:25:25 PDT.
803 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
804 go back in the water.
807 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
808 this date, but before the correction date.
811 old fsck and new kernel interactions appear to have been fixed.
814 fsck and the kernel were changed to handle some optimizations
815 to directory layout. This breaks backward compatibility.
816 Update only if you understand that you must not use the old
817 fsck with the new kernel ever.
820 fsck has changed the meaning of the pass column in /etc/fstab.
821 Please see the cvs commit to fsck.8 or the fsck.8 man page for
822 details. It is unclear if changes to /etc/fstab are necessary.
825 portmap had changed name to rpcbind for maximum POLA in your
826 current world. /etc/hosts.{allow,deny} needs changes. nfs and
827 other rpc based programs that rely on portmapper will not work
828 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
831 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
832 and ATA_ENABLE_TAGS are no longer kernel options. They have
833 been replaced by tunables. See ata.4 for details.
836 The fxp driver was converted to use miibus. If you compile
837 fxp into your kernel statically, you will need to add miibus.
840 The wi device now defaults to BSS (infrastructure) mode
844 /dev/urandom should be a symbolic link to /dev/random now.
845 Users of current not using DEVFS need to run MAKEDEV std.
846 ssh might not work if you don't.
849 The ed driver has been updated. It now allows mii attachments,
850 which means that you must include the miibus in your kernel if
851 you use the ed driver.
854 The problems with libc have been corrected. It is now mostly
855 safe to go back into the water.
858 The size of FILE was changed. This breaks upgrading. If
859 you must upgrade, be prepared for pain. It also breaks almost
860 all binaries that you've compiled on -current. You are warned
861 that before upgrading would be a good time to do a level 0
862 dump of your system. No, really, I mean it this time.
864 To get to the new system, you'll need to use the following
865 workaround. Hopefully this can be sorted out so that we
866 don't have to move this to the updating section.
868 To get around the installworld problem, do:
869 # cd /usr/src/usr.bin/sed
873 If that doesn't work, then try:
874 # make -k installworld
878 DEVFS is now the default. If you use vinum, make sure that you
879 do not include devfs in your kernel as problems result.
882 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
883 Remove them from your config.
886 ****************************** WARNING ******************************
887 buildkernel has been changed slightly
888 ****************************** WARNING ******************************
889 KERNCONF replaces the variable KERNEL for buildkernel. You
890 should update your scripts and make.conf accordingly.
893 config has changed to allow DEV_FOO as a replacement for NFOO.
894 This requires a new config to build correctly.
897 The kernel option I386_CPU is now mutually exclusive with the
898 other cpu types. If you have an i386 system, be sure that it
899 only had this line. Remove it for all other configurations.
902 Changes to the kernel require it and burncd be in sync.
905 Everyone who has hw.sndunit set to something in
906 /etc/sysctl.conf, it is now hw.snd.unit.
909 ex and vi were broken by some changes to sys/queue.h. If you
910 have a bad vi, you will see make buildworld fail with a core
911 dump while building termcap. You can work around this problem
912 by adding -k to your make buildworld. This will cause the
913 build to complete and install a new vi. Once that's done, you
914 can rebuild again without the -k to pick up anything that
915 might have been ignored by the -k option.
917 Others have suggested that you can just rebuild libc if your
918 vi/ex is dynamically linked, but I've not received any reports
922 There have been some changes to libcrypt in -current. The
923 libscrypt/libdescrypt symlink silliness is gone and the installed
924 libcrypt is fully functional. Be aware of this.
927 Linksys Fast Ethernet PCCARD cards supported by the ed driver
928 now require the addition of flag 0x80000 to their config line
929 in pccard.conf(5). This flag is not optional. These Linksys
930 cards will not be recognized without it.
933 Important new FreeBSD-version stuff: PAM support has been worked
934 in, partially from the "Unix" OpenSSH version. This requires
935 adding the following in pam.conf:
937 sshd auth sufficient pam_skey.so
938 sshd auth required pam_unix.so try_first_pass
939 sshd session required pam_permit.so
945 The random device needs more entropy, so you need to make sure
946 that you've run mergemaster to get a /etc/rc which will seed
947 /dev/random. If you don't and the system hangs after ldconfig,
948 then banging on the keyboard randomly until it unhangs is one
952 ****************************** WARNING ******************************
953 Sendmail has been updated.
954 ****************************** WARNING ******************************
955 o mail.local(8) is no longer installed as a set-user-id binary.
956 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
958 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
960 o Now using sendmail's version of vacation(1).
961 o The sendmail cf building tools (contrib/sendmail/cf) are installed
962 in /usr/share/sendmail/cf.
963 o sendmail.cw changed to local-host-names
965 More details can be found at
966 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
969 The ports tree's new layout is in place. Be sure to update
970 your entire ports tree, or you will have problems.
973 The perl build procedure no longer installs miniperl, nor uses
974 the installed miniperl. It is recommended that you delete
978 This weekend the ports tree will be updated to a new layout.
979 It will be in an inconsistent state until noted in the UPDATING
980 file, or with asami-san's message to the relevant mailing
981 lists. With this new layout, you'll need to update the whole
982 tree for anything to work.
985 There was a change in the passwd format. Need more information.
988 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
989 place. Please update boot loader (not the boot blocks) at the
990 same time as your kernel.
993 The new pmtimer device is necessary for laptops. Failure to
994 include the device will cause suspended laptops losing time
995 when they resume. Include
997 in your config file and
998 hint.pmtimer.0.at="isa"
999 to your /boot/device.hints file.
1002 The random device has been turned into a (pseudo-)device,
1003 rather than an option. The supplied kernel config files have
1004 been updated. You will need to do something similar in your
1005 own kernel config file.
1010 If you prefer to load the loadable module, you need to do
1014 The random device module has been renamed from randomdev.ko to
1015 random.ko. You will need to edit your /boot/loader.conf to
1016 reflect this if you load this module at boot time.
1017 The line should read:
1021 The SMPNG commit has happened. It should work, but if it
1022 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
1023 to be a variety of minor issues. Please see 20000905 to make
1024 sure you don't have model loading problems which might at
1025 first blush appear related to SMP.
1028 nsswitch has been imported from NetBSD. Among other things,
1029 this means that /etc/host.conf is no longer used. See
1030 nsswitch.conf(5) instead. Note that at boot time rc.network
1031 will attempt to produce a new nsswitch.conf file for you if you
1032 don't have one, and you have host.conf.
1035 The ucred structure changed size. This breaks the interface
1036 that mountd uses. Trying to use an older mountd with a newer
1037 kernel guarantees a panic. This means that you need to use
1038 kernels newer than today only with matching mountd, but you
1039 needed to do that anyway with the boot loader changes.
1042 The boot loader has been updated. The new default kernel is
1043 now /boot/kernel/kernel.ko. The new default module location
1046 You *MUST* upgrade your boot loader and kernel at the same time.
1047 The easiest way to do this is to do the buildworld/buildkernel/
1048 installkernel/installworld dance.
1050 Furthermore, you are urged to delete your old /modules directory
1051 before booting the new kernel, since kldload will find stale
1052 modules in that directory instead of finding them in the correct
1053 path, /boot/kernel. The most common complaint that this cures
1054 is that the linux module crashes your machine after the update.
1056 if [ ! -d /boot/kernel.old ]; then
1057 mv /modules.old /boot/kernel.old
1058 chflags noschg /kernel.old
1059 mv /kernel.old /boot/kernel.old/kernel.ko
1060 chflags schg /boot/kernel.old/kernel.ko
1064 A new issue with the sendmail upgrade has come to light.
1065 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1066 incorrectly install the default aliases in /etc/mail rather than
1067 move the old one from /etc. So you'll need to manually move the
1068 file, create a symbolic link, remove the old /etc/aliases.db and
1069 run newaliases. For safety sake, you should stop sendmail
1070 while doing this and run the upgrade when locally sourced email
1071 is not likely to be generated.
1074 /boot/device.hints is now required for installkernel to
1075 succeed. You should copy GENERIC.hints for your architecture
1076 into /boot/device.hints. If and only if you compile hints
1077 into your kernel, then this file may be empty. Please note,
1078 if you have an empty or missing /boot/device.hints file and
1079 you neglected to compile hints into your kernel, no boot
1080 messages will appear after the boot loader tries to start the
1084 If you do NOT have ``options RANDOMDEV'' in your kernel and
1085 you DO want the random device then add randomdev_load="YES" to
1089 suidperl is now always built and installed on the system, but
1090 with permissions of 511. If you have applications that use
1091 this program, you are now required to add ENABLE_SUIDPERL=true
1092 to /etc/make.conf. If you forget to do this,
1093 chmod 4511 /usr/bin/suidperl
1094 will fix this until the next build.
1097 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1098 visible changes that may immediately affect your configuration
1100 - New default file locations from src/contrib/sendmail/cf/README
1101 - newaliases limited to root and trusted users
1102 - MSA port (587) turned on by default
1103 - New queue file naming system so can't go from 8.11 -> 8.9
1104 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1105 - FEATURE(`nullclient') is more full featured
1106 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1107 - mail.local FreeBSD-only -b option changed to -B
1108 - See src/contrib/sendmail/RELEASE_NOTES for more info
1111 suidperl (aka sperl) is no longer build by default. You must
1112 specifically define BUILD_SUIDPERL to "true" for it to be build.
1113 Furthermore, we recommend that you remove /usr/bin/sperl* and
1114 /usr/bin/suidperl files from your system unless you have a
1115 specific use for it.
1118 Networking defaults have been tightened. Anybody upgrading
1119 /etc/defaults/rc.conf needs to add the following lines to
1120 /etc/rc.conf if they want to have the same setup
1121 afterwards (unless the variables already are set, of course):
1122 # Enable network daemons for user convenience.
1124 portmap_enable="YES"
1125 sendmail_enable="YES"
1128 If you have null_load="YES" in your /boot/loader.conf, you
1129 will need to change that to nullfs_load="YES".
1132 The "installkernel" target has changed slightly. Now even if
1133 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1134 it will install the MYKERNEL file (built with the buildkernel
1135 target) as /kernel rather than /MYKERNEL. Those who have
1136 updated their /boot/loader.conf files to point to /MYKERNEL
1137 should remove that entry or perform manual rename of /kernel
1141 If you use CVSUP or CTM to get CVS trees, AND you used to get
1142 the old crypto files from internat.freebsd.org AND you check
1143 out files from the CVS tree with the cvs command, please read
1144 http://people.freebsd.org/~imp/internat.txt
1145 for details on potential problems that you might have and how
1148 If you are merely a mirror, or don't answer yes to each of the
1149 clauses above, you needn't worry.
1152 /etc/security has been updated to print the inode number of
1153 setuid programs that have changed. You will see a large spike
1154 in the number of changed programs the first time when you run
1155 mergemaster to get a new /etc/security.
1158 /dev/random now has good entropy collection (from the keyboard
1159 and sysmouse drivers). Please ensure that either `options
1160 RANDOMDEV' is present in your kernel config file or that
1161 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1162 not have the /dev/random driver, OpenSSL (and consequently
1163 lots of crypto tools (like SSH)) will fail with strange
1164 errors. (see below, 20000624).
1166 FreeBSD-current is safe again to run Crypto.
1169 phk made the malloc default options AJ. This may slow things
1170 down and uncover other latent bugs in the code. If you need to
1171 run at full speed, you can disable this by doing the following:
1172 ln -s aj /etc/malloc.conf
1175 libftpio's version was accidentally bumped a few days ago. This
1176 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1177 before doing your next buildworld/installworld pair. It certainly
1178 won't hurt to remove it before the update procedure. It will
1179 break fetch until a new one is built, but ftp can be used in the
1183 The crypto packages have changed for the cvsup. This has been done
1184 in a backward compatible way, but the old packages will go away at
1185 some point in the future. Look at /usr/share/examples/cvsup for
1189 With the new sys/modules/sound/drivers/*, you will need to
1190 set SYSDIR until you do an installworld after July 7th.
1193 rc.shutdown and rc will now call the rc.d scripts with start
1194 or stop. This may cause some harmless warnings from older
1195 rc.d scripts that haven't been updated.
1198 The libfetch based version of fetch has gone into the tree.
1199 Minor problems may result on some of the less popular sites,
1200 which should be reported to des@freebsd.org.
1203 From approximately this date forward, one must have the crypto
1204 system installed in order to build the system and kernel.
1205 While not technically strictly true, one should treat it as
1206 required and grab the crypto bits. If you are grabbing CVS
1207 trees, src-all and cvs-crypto should be treated as if they
1208 were required. You should check with the latest collections
1209 to make sure that these haven't changed.
1212 Mark Murray just committed the first parts of a cleanup of
1213 /dev/zero, et al. This is also cleaning up /dev/random.
1214 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1215 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1216 until Mark can merge in the fixes to this work in progress.
1217 openssh and openssl should not be used to generate keys from this
1218 date to the completion of the work.
1220 If you must operate at this reduced level of security, add '
1221 options RANDOMDEV' to your kernel or modload the randomdev
1222 module. You may also need to copy a new MAKEDEV to /dev and
1223 recreate the random and urandom devices.
1226 The license on the softupdates is now a standard 2 clause
1227 BSD license. You may need to remove your symbolic links
1228 that used to be required when updating.
1231 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1232 the config file update procedure.
1233 http://people.freebsd.org/~imp/config-upd.html
1234 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1235 isn't buildable. However, you can generate a LINT file:
1236 cd /sys/<ARCH>/conf && make LINT
1239 Binutils 2.10 have hit the tree, or will shortly. As soon
1240 as they do, the problem noted in 20000522 will be resolved and
1241 that workaround will no longer be required.
1244 phk removed the compatibility creation of wd devices in the
1245 ad driver. If you haven't done so already, you must update
1246 your fstab, etc to use the ad devices instead of the wd
1249 In addition, you'll need to update your boot blocks to a
1250 more modern version, if you haven't already done so. Modern
1251 here means 4.0 release or newer (although older releases
1255 Peter took an axe to config(8). Be sure that you read his mail
1256 on the topic before even thinking about updating. You will
1257 need to create a /boot/device.hints or add a hints directive
1258 to your config file to compile them in statically. The format
1259 of the config file has changed as well. Please see GENERIC or
1260 NEWCARD for examples of the new format.
1262 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1263 says that it has been fixed, assume that must use the hints mechanism
1264 in the loader if you need to use a machine with very old ISA cards
1268 A new set of binutils went into the tree today. Anybody
1269 building a kernel after this point is advised that they need
1270 to rebuild their binutils (or better yet do a
1271 buildworld/installworld) before building a new kernel.
1273 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1274 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1275 is recommended that you don't set this option until the problem
1279 The ethernet drivers were all updated to clean up the BPF handling.
1282 The problems with boot blocks on the alphas have been corrected.
1283 This will require some care in updating alphas. A new libstand
1284 is requires for the boot blocks to build properly.
1287 Recompile all kld modules. Proper version dependency info
1291 Modules have been disconnected from the buildworld tree and
1292 connected to the kernel building instead.
1295 You may need to build gperf
1296 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1297 when upgrading from 4.0 -> current. The build system now uses
1298 an option only in -current.
1301 The method that we brand ELF binaries has changed to be more
1302 acceptable to the binutils maintainers. You will need to
1303 rebrand your ELF binaries that aren't native. One problem
1304 binary is the Linux ldconfig. After your make world, but
1305 before you reboot, you'll need to issue:
1306 brandelf -t Linux /compat/linux/sbin/ldconfig
1307 if you have Linux compatibility enabled on your machine.
1310 If you have really bad/marginal IDE drives, you may find they
1311 don't work well. Use pio mode instead. The easiest way to
1312 cope if you have a problem combination is to add:
1313 /sbin/sysctl hw.ata.ata_dma=0
1314 to the start of /etc/rc.conf.
1317 The ISA and PCI compatibility shims have been connected to the
1318 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1319 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1320 include the appropriate option in your kernel config. Drivers
1321 using the shims should be updated or they won't ship with
1322 5.0-RELEASE, targeted for 2001.
1325 We've entered the traditional post release dumping party.
1326 Large kernel changes are being committed and are in the
1327 works. It is important to keep the systems' klds and kernel
1328 in sync as kernel interfaces and structures are changing.
1329 Before reporting kernel panics, make sure that all modules
1330 that you are loading are up to date.
1333 If you are upgrading from an older version of FreeBSD, you
1334 need to update your boot blocks as well. 'disklabel -B ad0'
1335 will do the trick. This isn't critical until you remove your
1336 wd device entries in /dev, at which point your system will not
1340 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1341 to upgrade to 4.0 from 3.x.
1347 Avoid using make -j when upgrading. From time to time in the
1348 past there have been problems using -j with buildworld and/or
1349 installworld. This is especially true when upgrading between
1350 "distant" versions (eg one that cross a major release boundary
1351 or several minor releases, or when several months have passed
1352 on the -current branch).
1354 Sometimes, obscure build problems are the result of environment
1355 poisoning. This can happen because the make utility reads its
1356 environment when searching for values for global variables.
1357 To run your build attempts in an "environmental clean room",
1358 prefix all make commands with 'env -i '. See the env(1) manual
1359 page for more details.
1363 If you are updating from a prior version of FreeBSD (even one just
1364 a few days old), you should follow this procedure. With a
1365 /usr/obj tree with a fresh buildworld,
1366 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1367 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1369 To just build a kernel when you know that it won't mess you up
1370 --------------------------------------------------------------
1371 cd src/sys/{i386,alpha}/conf
1372 config KERNEL_NAME_HERE
1373 cd ../../compile/KERNEL_NAME_HERE
1378 If this fails, go to the "To build a kernel" section.
1380 To rebuild everything and install it on the current system.
1381 -----------------------------------------------------------
1382 # Note: sometimes if you are running current you gotta do more than
1383 # is listed here if you are upgrading from a really old current.
1385 <make sure you have good level 0 dumps>
1386 <maybe fix /etc/fstab> [7]
1388 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1389 make installkernel KERNCONF=YOUR_KERNEL_HERE
1391 <reboot in single user> [3]
1398 To cross-install current onto a separate partition
1399 --------------------------------------------------
1400 # In this approach we use a separate partition to hold
1401 # current's root, 'usr', and 'var' directories. A partition
1402 # holding "/", "/usr" and "/var" should be about 2GB in
1405 <make sure you have good level 0 dumps>
1408 <maybe newfs current's root partition>
1409 <mount current's root partition on directory ${CURRENT_ROOT}>
1410 make installworld DESTDIR=${CURRENT_ROOT}
1411 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1412 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1413 ${CURRENT_ROOT}/boot/device.hints # as needed
1414 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1415 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1416 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1417 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1418 <reboot into current>
1419 <do a "native" rebuild/install as described in the previous section>
1420 <maybe install compatibility libraries from /usr/src/lib/compat>
1424 To upgrade in-place from 4.x-stable to current
1425 ----------------------------------------------
1426 # 5.x uses more space than 4.x. Also, the location of kernel
1427 # modules has changed. If you are installing 5.0 onto a 4.x
1428 # system, you'll need about 30MB of free disk space on your /
1429 # partition. If you have less than this, you may encounter difficult
1430 # to back out of problems with this procedure. If /tmp is on
1431 # the / partition, you may want to completely remove all its content
1432 # before upgrading, as this can be a common source of shortage of
1435 <make sure you have good level 0 dumps>
1436 <maybe fix /etc/fstab> [7]
1438 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1439 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1440 make installkernel KERNCONF=YOUR_KERNEL_HERE
1441 cd src/sys/boot ; make install [6]
1443 <reboot in single user> [3]
1445 rm -rf /usr/include/g++
1450 Make sure that you've read the UPDATING file to understand the
1451 tweaks to various things you need. At this point in the life
1452 cycle of current, things change often and you are on your own
1453 to cope. The defaults can also change, so please read ALL of
1454 the UPDATING entries.
1456 Also, if you are tracking -current, you must be subscribed to
1457 freebsd-current@freebsd.org. Make sure that before you update
1458 your sources that you have read and understood all the recent
1459 messages there. If in doubt, please track -stable which has
1460 much fewer pitfalls.
1462 [1] If you have third party modules, such as vmware, you
1463 should disable them at this point so they don't crash your
1466 [2] If you have legacy ISA devices, you may need to create
1467 your own device.hints to reflect your unique hardware
1470 [3] From the bootblocks, boot -s, and then do
1475 adjkerntz -i # if CMOS is wall time
1476 Also, when doing a major release upgrade, it is required that
1477 you boot into single user mode to do the installworld.
1478 For the 4.x -> 5.0 upgrade, you will also see many messages about
1479 needing to recompile your userland. These are harmless and can
1480 be ignored while you proceed to the next step.
1482 [4] Note: This step is non-optional. Failure to do this step
1483 can result in a significant reduction in the functionality of the
1484 system. Attempting to do it by hand is not recommended and those
1485 that pursue this avenue should read this file carefully, as well
1486 as the archives of freebsd-current and freebsd-hackers mailing lists
1487 for potential gotchas.
1489 [5] Usually this step is a noop. However, from time to time
1490 you may need to do this if you get unknown user in the following
1491 step. It never hurts to do it all the time. You may need to
1492 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1493 install) after the buildworld before this step if you last updated
1494 from current before 20020224 or from -stable before 20020408.
1496 [6] 4.x boot loader can be used to boot a 5.x system, however
1497 it is difficult to do that at best. If you wish to try, then
1498 you should interrupt the boot and at the ok prompt type:
1500 ok boot /boot/kernel/kernel
1501 If this fails to work, you must install a new boot loader as
1504 [7] Before you upgrade, please make sure that you are not using
1505 compatibility slices. These are device names of the form, on i386
1506 and other architectures that use MBR slicing, /dev/ad0a without the
1507 actual slice name. Chances are excellent that these will break.
1508 You generally must update these entries to use the post FreeBSD
1509 2.x form of /dev/ad0s1a.
1511 [8] In order to have a kernel that can run the 4.x binaries
1512 needed to do an installworld, you must include the COMPAT_FREEBSD4
1513 option in your kernel. Failure to do so may leave you with a system
1514 that is hard to boot to recover.
1516 [9] When checking out sources, you must include the -P flag to have
1517 cvs prune empty directories.
1520 This file contains a list, in reverse chronological order, of major
1521 breakages in tracking -current. Not all things will be listed here,
1522 and it only starts on March 15, 2000. Updating files can found in
1523 previous releases if your system is older than this.
1525 Copyright information:
1527 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1529 Redistribution, publication, translation and use, with or without
1530 modification, in full or in part, in any form or format of this
1531 document are permitted without further permission from the author.
1533 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1534 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1535 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1536 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1537 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1538 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1539 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1540 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1541 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1542 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1543 POSSIBILITY OF SUCH DAMAGE.
1545 If you find this document useful, and you want to, you may buy the
1548 Contact Warner Losh if you have any questions about your use of