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 /etc/rc.d/ttys script has been removed. It is no longer
22 necessary since devfs has been mandatory for some time.
25 libkse has been renamed back to libpthread and is now the
26 default threads library. The gcc -pthread option has also
27 been changed to link to libpthread instead of libc_r. For
28 alpha and sparc64 machines, libkse is not renamed and links
29 are installed so that libpthread points to libc_r. Until
30 the ports system is updated to handle this change, it is
31 recommended that folks install an /etc/libmap.conf(5) that
32 maps libc_r to libpthread. If you have any binaries or
33 libraries linked to libkse, then it is also recommended
34 that you map libkse to libpthread. Anyone that is using
35 nvidia supplied drivers and libraries should use a libmap.conf
36 that maps libpthread to libc_r since their drivers/libraries
37 do not work with libpthread.
40 ULE has entered into its probationary period as the default scheduler
41 in GENERIC. For the average user, interactivity is reported to be
42 better in many cases. On SMP machines ULE will be able to make more
43 efficient use of the available parallel resources. If you are not
44 running it now, please switch over, replacing the kernel option
45 SCHED_4BSD with SCHED_ULE.
48 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
49 if the login process is unable to successfully set the
50 process credentials to include all groups defined for the
51 user. The current kernel limit is 16 groups; administrators
52 may wish to check that users do not have over 16 groups
53 defined, or they will be unable to log in.
56 The ACPI module has been reactivated. It is no longer required
57 to compile ACPI support into kernels statically.
60 The statfs structure has been updated with 64-bit fields to
61 allow accurate reporting of multi-terabyte filesystem
62 sizes. You should build world, then build and boot the new kernel
63 BEFORE doing a `installworld' as the new kernel will know about
64 binaries using the old statfs structure, but an old kernel will
65 not know about the new system calls that support the new statfs
67 Note that the backwards compatibility is only present when the
68 kernel is configured with the COMPAT_FREEBSD4 option. Since
69 even /bin/sh will not run with a new kernel without said option
70 you're pretty much dead in the water without it. Make sure you
72 Running an old kernel after a `make world' will cause programs
73 such as `df' that do a statfs system call to fail with a bad
74 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
75 that cfsd (ports/security/cfs) needs to be recompiled after
76 these changes are installed.
78 ****************************DANGER*******************************
80 DO NOT make installworld after the buildworld w/o building and
81 installing a new kernel FIRST. You will be unable to build a
82 new kernel otherwise on a system with new binaries and an old
86 Some netgraph string length constants have been changed. This
87 change requires the netgraph kernel modules and all netgraph
88 userland components to be in sync. Especially users who require
89 netgraph to boot need to make sure to have world and kernel in
90 sync before rebooting.
93 Hyperthreading logical CPU's are no longer probed by default
94 when using the MP Table. If ACPI is being used, then logical
95 CPUs will be probed if hyperthreading is enabled in the BIOS.
96 If ACPI is not being used and hyperthreading is enabled in the
97 BIOS, logical CPUs can be enabled by building a custom kernel
98 with the option MPTABLE_FORCE_HTT enabled.
101 The i386 APIC_IO kernel option has been replaced by
102 'device apic'. The ACPI module has also been temporarily
103 disabled, so ACPI must be statically compiled into your
104 kernel using 'device acpi' if you wish to use the ACPI driver.
107 The API and ABI of struct ifnet have been changed by removing
108 the if_name and if_unit members and replacing them with
109 if_xname, if_dname, and if_dunit. All network drivers and most
110 userland programs which include net/if_var.h must be updated
111 and recompiled. __FreeBSD_version has been bumped to 501113 to
115 Changes to the cdevsw default functions have been made to remove
116 the need to specify nullopen() and nullclose() explicitly.
117 __FreeBSD_version bumpted to 501110.
120 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
121 mount_cd9660(8) need to be in sync with kernel.
124 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
125 also be explicitly configured. Previously this dependency was
126 magically handled through some cruft in net/pfil.h; but that has
127 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
128 will fail with obtuse errors in ip_fil.c.
131 Fix a bug in arplookup(), whereby a hostile party on a locally
132 attached network could exhaust kernel memory, and cause a system
133 panic, by sending a flood of spoofed ARP requests. See
134 FreeBSD-SA-03:14.arp.
137 A change to /etc/defaults/rc.conf now causes inetd to be started
138 with `-C 60' if it is not overridden in /etc/rc.conf. This
139 causes inetd to stop accepting connections from an IP address
140 that exceeds the rate of 60 connections per minute.
143 The following rc.d scripts have been removed and should be
144 deleted from your installation: atm2.sh atm3.sh devdb
145 localdaemons network1 network2 network3. Depending on when
146 you last updated world and used mergemaster(8) you may or
147 may not have problems during the rc boot sequence. The simplest
148 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
149 The atm2.sh atm3.sh and devdb scripts were removed some time
150 ago, so depending on when you installed -CURRENT these scripts
151 may or may not exist on your system.
154 ATAng has been committed. You need to build world as sys/ata.h
155 has changed, and userland atacontrol depends on it.
156 If you use ATA SW raids you need "device ataraid" in your
157 kernel config file, as it is no longer pulled in automatically.
160 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
161 Among other things, this changes the device enumeration to be
162 closer to Solaris. Be aware that, this can even cause the machine
163 to not boot without manual intervention before the fstab is adjusted.
166 All current USB and Firewire quirks in da(4) have been deprecated
167 and will be removed for 5.2. If this causes failure for your
168 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
169 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
170 so the quirk can be re-enabled.
173 FPU-less support has been removed from FreeBSD. Chances are you won't
174 notice. 386+387 support should still work after this change, but
175 it is now a minimum requirement for the i386 port that you have real
179 Some people are having problems with changes related to /rescue.
180 If you are building -j N, you will need to define NO_RESCUE. Others
181 will need to define it if /rescue has issues with their environment.
182 People should report those issues to current@.
185 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
186 across this point. Further, it might be a good idea to remove
189 20030613: [retrospective]
190 There was a small window in which sed(1) was broken. If you
191 happen to have sed(1) installed during that window, which is
192 evidenced by an inability to build world with the failure
193 given below, you need to manually build and install sed(1)
194 (and only sed(1)) before doing anything else. This is a one-
195 time snafu. Typical failure mode:
197 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
198 targmatch.h:7:1: null character(s) ignored
199 targmatch.h:12:1: null character(s) ignored
200 targmatch.h:16:1: null character(s) ignored
203 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
204 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
205 usr.bin/sed/process.c).
208 Remove deprecated locale names and transition period code
209 for them, finishing switching to the new scheme. Check your
210 LANG environment variable.
213 CCD has been changed to be a fully GEOMified class. Kernel
214 and ccdconfig(8) needs to be in sync, this is particularly
215 important to remember beforehand if your source tree is on
216 a ccd device. Consider making a copy of the old ccdconfig
217 into /boot/kernel.good or wherever you keep your backup
221 Kerberos 5 (Heimdal) is now built by default. Setting
222 MAKE_KERBEROS5 no longer has any effect. If you do NOT
223 want the "base" Kerberos 5, you need to set NO_KERBEROS.
226 groff has been updated. If you try to do a buildworld and
227 get an infinite loop in troff, update to May 4th or newer. If you
228 have a newer kernel than userland, you may need to set the OSRELDATE
229 to 500110 in your environment before starting a buildworld.
232 The old rc system has been removed. Please report any problems
233 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
234 Your personal versions of these files will not be removed, so you can
235 continue to use them. However, you should take great care when updating,
236 especially when using mergemaster, since the compatibility code that
237 utilizes these old scripts has also been removed.
240 A bug has been fixed in /dev/devctl which would cause devd
241 to hang on boot, were it not for a workaround in devd. The
242 work around in devd will be removed around 20030507. You
243 have until then to upgrade your kernel before updating
244 userland. In general, you should have a userland and
245 kernel that's in sync with each other. However, given the
246 effects of this bug (hang on boot when starting devd), some
250 Alphas with libc from between 20030312 and 20030329 exhibit
251 floating point exceptions (FPEs), most notably in awk(1)
252 while upgrading the system through a buildworld.
254 So, to successfully upgrade your Alpha, you must either
255 downgrade your libc.so to a pre-20030312 version, or update
256 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
257 to CFLAGS, then forcibly rebuild and install libc:
259 cd /usr/src/lib/libc && \
260 make cleandir && make obj && \
261 make -DNOMAN -DNOPROFILE all && \
262 make -DNOMAN -DNOPROFILE install
265 sendmail 8.12.7 has been imported. It has one important
266 change for IPv6 users. The default submit.mc now uses
267 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
268 used to connect to the MTA. Users on IPv6-only machines
269 will need to edit /etc/mail/submit.mc appropriately.
272 NODEVFS option has been removed and DEVFS thereby made standard.
273 This makes all references to MAKEDEV obsolete, and they should
274 be removed when convenient.
277 The name of the device for the ofw console has changed, sparc64 users
278 must run mergemaster to update their installed /etc/ttys.
281 The scheduler framework has grown a second scheduler and consequently
282 you must specify one and only one scheduler in your kernel config.
283 The cvs config files have been updated to use the old scheduler
284 which may be selected via 'options SCHED_4BSD'. If you would like
285 to try the new, much more experimental, scheduler please try
286 'options SCHED_ULE' and contribute to the arch@ discussion.
289 A new version of the wi driver has been imported into the tree.
290 One now must have device wlan in the config file for it to operate
293 In addition, there have been some changes to how wi devices are
294 configured for point to point links to bring it more in line
295 with the former way of doing things, as well as compatibility
299 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
300 used an incompatible form of ABI for returning structures and unions
301 which FreeBSD's GCC maintainers were not aware of relative to previous
302 versions of FreeBSD. We have gone back to the ABI for now, and any
303 code compiled which is required to interoperate with other code (not
304 built at the same time) returning structs or unions should be
308 A name change in /etc/netconfig has been reverted to stay
309 compatible with suns TIRPC and also with NetBSD. You need
310 to run mergemaster after make world. A new libc does still work
311 with an outdated /etc/netconfig for some time, but you'll get
312 a warning. This warning will be removed in 20030301.
315 The recent binutils upgrade marks a kernel flag day on
316 sparc64: modules built with the old binutils will not work
317 with new kernels and vice versa. Mismatches will result in
318 panics. Make sure your kernel and modules are in sync.
321 The value of IPPROTO_DIVERT has changed. Make sure to keep
322 your kernel, netstat, natd and any third-party DIVERT
326 Old, compatibility slices have been removed in GEOM kernels.
327 This means that you will have to update your /etc/fstab to
328 not use disk devices of the form /dev/ad0a. Instead, you
329 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
330 partition really is on. The old device names have gone
331 away, so if you use them anywhere else, you must also adjust
332 those uses. (This doesn't affect the disks formatted in
333 the ``dangerously-dedicated'' mode.)
336 Alphas with kernels from between 20020830 and 20021023 and/or
337 rtld (ld-elf.so.1) older than 20021023 may experience problems
338 with groff while doing a buildworld (kernel: "out of memory",
339 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
340 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
342 So, to successfully upgrade your Alpha, you must either
343 upgrade your kernel and rtld first (which might be a bit
344 tricky), or avoid running the bootstrapped groff during the
345 "transitional" buildworld. To avoid running groff during the
346 transitional upgrade run make buildworld with -DNOMAN,
347 -DNO_SHAREDOCS, and -DNO_LPR.
350 gcc has been upgraded to 3.2. It is not all binary compatible
351 with earlier versions of gcc for c++ programs. All c++
352 programs and libraries need to be recompiled.
354 Also, if you encounter g++ issues, rm /usr/include/g++/* before
355 doing an installworld to make sure that stale files are removed.
358 Our /etc/termcap now has all the entries from the XFree86 xterm
359 almost unchanged. This means xterm now supports color by default.
360 If you used TERM=xterm-color in the past you now should use
361 TERM=xterm. (xterm-color will lead to benign warnings).
364 A "bug" in gcc(1) that was hiding warning in system headers was
365 fixed. It's probably time to add -DNO_WERROR to your make line
369 COPY is being deprecated. The 20010530 change was reverted, as
370 it causes far more pain than was expected, and to always compare
371 before installing, please use INSTALL="install -C" again. The
372 -C option is now silently ignored when used with the -d option.
375 Problems with libc_r clients like KDE and GNOME have been resolved.
376 There are still some minor problems with some signals but the
377 system is stable enough for general use again. SMP is less so than UP
378 but each can successfully complete multiple buildworlds.
379 Libkvm needs to be recompiled due to KSE.
382 Now would be a bad time to upgrade. Something in or near the
383 KSE commit totally broke programs using libc_r like KDE and
387 The k5su utility installed as part of Kerberos 5 is no longer
388 installed with the set-user-ID bit set by default. Add
389 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
390 with the set-user-ID bit set.
393 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
394 Unfortunately our native GDB (at version 4.18) does not understand
395 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
396 generated debugging information for our native GDB.
399 Due to the way CVS works, it may not properly update src/contrib/gcc
400 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
401 and then do a cvs update.
404 When exec'ing set[ug]id executables, the kernel now ensures that the
405 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
408 New sendmail startup scripts have been installed to make it
409 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
410 variable sendmail_enable to "NO" no longer prevents any sendmail
411 daemons from starting. Instead, either set sendmail_enable to
412 "NONE" or change mta_start_script to a script for starting
413 an alternative MTA. Setting mta_start_script to "" will
414 also prevent any MTA from being started at boot.
417 UCONSOLE is no longer a valid kernel option.
420 FreeBSD 5.0 DP-1 was basically branched today.
423 Warnings are now errors in the kernel. Unless you are a developer,
424 you should add -DNO_WERROR to your make line.
427 sendmail 8.12.2 has been imported. The sendmail binary is no
428 longer a set-user-ID root binary and the infrastructure to support
429 command line mail submission has changed. Be sure to run
430 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
431 and /etc/mail) and read /etc/mail/README for more details.
433 Due to the import of sendmail 8.12.2, a new user and group are
434 required in order for sendmail to run as a set-group-ID
435 binary. A 'make installworld' will use the new user and group
436 to set the owner and group of /var/spool/clientmqueue and will
437 fail if the new user and group do not exist. The 'smmsp' user
438 and group must be merged from src/etc/group and
439 src/etc/master.passwd before using 'make installworld'.
440 'mergemaster -p' will do this. You may need to install
441 mergemaster before this will work if you are updating from a
442 very old version of current. The updating recipe has changed
446 The preferred configuration method for PAM is now /etc/pam.d/
447 rather than /etc/pam.conf. If you have an unmodified
448 pam.conf, just delete it after your next mergemaster run. If
449 you have local modifications, you can use
450 /usr/src/etc/pam.d/convert.pl to incorporate them into your
453 Please see the following url for more details:
454 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
456 If anyone here is already using the new rc.conf(5) variable
457 networkfs_types, please note that it has changed
458 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
461 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
462 started out its life in the ISDN4BSD project as an offspring
463 from sys/net/if_spppsubr.c, which eventually got a life of its
464 own. All the accumulated features and bugfixes of the i4b
465 version have now been merged back into the base system's
466 version now. The only user-visible change resulting from this
467 is that i4b's sppp(4) interfaces are to be managed with
468 spppcontrol(8) again, since ispppcontrol(8) has been retired
469 as well. (There has never been rc file support for
470 ispppcontrol in -current, but only in -stable. That will be
471 reverted by the time the changes are MFCed.)
474 The fdc(4) driver has been updated and now automatically
475 recognizes media in `standard' formats (like 1440 KB and
476 720 KB for a 3.5" high-density drive) when accessing the
477 default device node (e. g. /dev/fd0). The old variety of
478 floppy device nodes /dev/fd*.* is no longer present by
479 default, devices can be created (in DEVFS) on demand. They
480 will need to be customized then for `odd' densities using
484 The bugs in procfs' debugging support code have been fixed,
485 and truss(1) now works again.
488 Daily security checks have been split out to use the periodic(8)
489 scripts. Some change in configuration may be necessary. Please
491 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
495 sos added VCD/SVCD support to ata driver and that needs the
496 kernel and burncd to be in sync.
499 The procfs pseudo-filesystem has now been converted to use the
500 pseudofs framework. If you have 'options PROCFS' in your
501 kernel config, you'll need to add 'options PSEUDOFS' if it's
504 This change temporarily breaks truss(1); use ktrace(1) instead
505 until the issue has been resolved.
508 A security hole in OpenSSH involving `UseLogin yes' has been
512 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
513 after this date. You need to do this only once.
516 Most of the awk issues have been resolved. Some rough
517 edges may be left, but for the most part things should be
518 back to "normal." For CURRENT's usual definition of "normal."
521 Awk has been upgraded to the one true awk from bell labs. Expect
522 choppy waves in the upgrade process.
525 The asr driver problem has been resolved.
528 Due to changes in other parts of the system, the asr driver
529 now causes the system to panic on boot. Do not use it pending
530 correction. Comment it out of any kernel config file that you
531 try to use from this date forward.
534 When crossbuilding, use TARGET=xxx where you used to use
535 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
536 unless you are changing both of them. To cross build pc98 on
537 an alpha, for example, you need to set TARGET=pc98 and
541 The kernel interface that burncd depends on has changed.
542 You must recompile both the kernel and userland applications
546 When crossbuilding, please set TARGET_ARCH rather than
547 MACHINE_ARCH to indicate the target. In the future, one will
548 set TARGET_MACHINE where you set MACHINE now. At the moment,
549 setting MACHINE alone for same MACHINE_ARCH machines works
550 (eg, you can build pc98 on an i386 machine and vice versa).
553 Some weird problems result from using ACPI on some machines.
554 To disable ACPI you can add
555 hint.acpi.0.disabled="1"
556 to /boot/loader.conf (or by putting set X=Y at the boot
559 Alternatively, you can remove it from /boot/kernel/acpi.ko
560 or use the MODULES_OVERRIDE function in your kernel config
561 file and not list acpi in that list.
564 The buildworld has been fixed. You may need to install
565 the 4.x compatibility libraries for some old binaries
566 to work. Add COMPAT4X=true to your /etc/make.conf to
567 get them installed on every installworld, or execute the
568 following to get them installed only once:
569 cd src/lib/compat/compat4x.<arch>
571 You will see ``__stdoutp undefined'' until you do this.
574 There's a bug in the world build process. The cross-tools
575 are build with the NEW headers, but the OLD libc.a. This
576 leads to all kinds of problems with the new libc. A temporary
578 CFLAGS="-O -pipe -D_OLD_STDIO"
579 before building world when upgrading from 4.x to current. This
580 can be removed afterwards.
582 A proper fix to the buildworld target is needed.
585 Peter has committed his new kthread nfs client/server code.
586 NFS may be unstable after this date.
589 KSE has hit the tree. Lots of things are now different in
590 the kernel. While a few problems were introduced in the
591 initial commit, most of the major ones have been found and
595 In OLDCARD, CardBus bridges appear to be stable. The work
596 arounds described in the 20010604 entry are now no longer
597 necessary and will be ignored. Most insert/remove problems
598 have been rectified around this date.
601 named now runs as user bind and group bind rather than as
602 root. If named_enable is set to YES in /etc/rc.conf, ensure
603 that user bind is available in /etc/passwd (using vipw(8))
604 and that group bind is available in /etc/group. Also make
605 sure that user or group bind has read (and not write)
606 permission for your name server configuration and that it
607 has read and write permission for your slave zone files and
610 If you wish to continue to run named as root (a less secure
611 alternative), add a line to /etc/rc.conf saying
616 The PAM libraries have had an API upgrade that is beyond
617 the ability of the shared library major number to handle.
618 It is manifested by PAM-using ports dumping core. The
619 solution is to rebuild those ports.
622 The kernel compile module has moved from src/sys/compile/FOO
623 to src/sys/${MACHINE}/compile/FOO.
626 The pccard modem issue from 20010613 has been corrected.
627 OLDCARD support is still a little weak in -current. slot 1 is
628 known not to work on some TI based cardbus bridges. Some
629 cardbus bridges do not properly detect insert/removal events.
630 IRQ configuration needs more safety belts.
633 Softupdates problems have been corrected.
636 Peter ripped out the linkerset support. You must, as always,
637 rerun config after you cvsup if you are using the traditional
638 kernel building methods.
641 pccard modems may not work with current after 20010604 date. Some
642 do, others result in panics. *MAKE*SURE* that you update your
643 config and /etc/rc.conf ala the 20010604 entry, or you will have
644 problems (this issue will be fixed, it just hasn't been yet).
647 SOFTUPDATES seem to be broken since the middle of May or so. Do not
648 use them in current. You can disable softupdates on all mounted
649 partitions, or remove SOFTUPDATES the kernel config file.
652 After Peter's commits to the hints code, people have been noticing
653 that certain devices are attached (or try to) twice. This is due
654 to having both static hints as well as a /boot/device.hints. To
655 work around this issue, please use only one or the other mechanism
656 until this bug is fixed.
658 Please note that a feature of config is that if you have config
659 file FOO and FOO.hints, it automatically adds FOO.hints to the
660 hints.c file, whether you want it to or not.
663 Locale names have changed to match other systems better.
666 pccard support for pci cards has been committed. You must change
667 your /etc/pccard.conf irq lines. It must match the irq used by
668 pcic device. Interrupt storms may result if you fail to do this.
669 Interrupt storms look a lot like a hang.
671 You must also install a new pccardd, otherwise you will get an
672 interrupt storm at card reset time (just after it tells you what
675 pccardd_flags="-I" is necessary for the time being. It tells pccardd
676 not to ask the kernel if the interrupt is really free or not before
677 using it. You can either change the /etc/pccard.conf irq lines to
678 match pcic, or add "-i X" to the pccardd_flags.
681 INSTALL=install -C is being deprecated. If you want to do this,
682 use COPY=-C instead. The former method will be supported for only
683 a limited time. If you see
685 install: warning: the -d and -C options may not be specified together
687 in your makeworld, then you need to migrate towards using
691 It appears that vm is now stable enough to use again. However,
692 there may be other problems, so caution is still urged. alpha
693 definitely is in bad shape.
696 Minor repo damage has happened. This may cause problems
697 with cvsup of ports. If you get errors, please see
698 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
699 at the bottom for details on a workaround. The error message
701 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
704 Vm and/or swapping are busted on -current. Please be patient.
707 pccard has had much reorganizational work done to it over
708 the past few days. Everything should still work, but if
709 not, please contact imp@freebsd.org.
712 ata ioctl changed. Make sure to recompile both kernel and
713 userland at the same time.
716 New ncurses imported.
719 DEVFS is now opt out, not opt in. Barring major problems, this
720 will be the only way to go starting July 1.
723 OpenSSH has been updated to 2.9. Some defaults are different,
724 including RhostsRSAAuthentication, which changes from yes to no.
727 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
730 Building perl was broken at 02:25:25 PDT.
733 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
734 go back in the water.
737 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
738 this date, but before the correction date.
741 old fsck and new kernel interactions appear to have been fixed.
744 fsck and the kernel were changed to handle some optimizations
745 to directory layout. This breaks backward compatibility.
746 Update only if you understand that you must not use the old
747 fsck with the new kernel ever.
750 fsck has changed the meaning of the pass column in /etc/fstab.
751 Please see the cvs commit to fsck.8 or the fsck.8 man page for
752 details. It is unclear if changes to /etc/fstab are necessary.
755 portmap had changed name to rpcbind for maximum POLA in your
756 current world. /etc/hosts.{allow,deny} needs changes. nfs and
757 other rpc based programs that rely on portmapper will not work
758 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
761 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
762 and ATA_ENABLE_TAGS are no longer kernel options. They have
763 been replaced by tunables. See ata.4 for details.
766 The fxp driver was converted to use miibus. If you compile
767 fxp into your kernel statically, you will need to add miibus.
770 The wi device now defaults to BSS (infrastructure) mode
774 /dev/urandom should be a symbolic link to /dev/random now.
775 Users of current not using DEVFS need to run MAKEDEV std.
776 ssh might not work if you don't.
779 The ed driver has been updated. It now allows mii attachments,
780 which means that you must include the miibus in your kernel if
781 you use the ed driver.
784 The problems with libc have been corrected. It is now mostly
785 safe to go back into the water.
788 The size of FILE was changed. This breaks upgrading. If
789 you must upgrade, be prepared for pain. It also breaks almost
790 all binaries that you've compiled on -current. You are warned
791 that before upgrading would be a good time to do a level 0
792 dump of your system. No, really, I mean it this time.
794 To get to the new system, you'll need to use the following
795 workaround. Hopefully this can be sorted out so that we
796 don't have to move this to the updating section.
798 To get around the installworld problem, do:
799 # cd /usr/src/usr.bin/sed
803 If that doesn't work, then try:
804 # make -k installworld
808 DEVFS is now the default. If you use vinum, make sure that you
809 do not include devfs in your kernel as problems result.
812 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
813 Remove them from your config.
816 ****************************** WARNING ******************************
817 buildkernel has been changed slightly
818 ****************************** WARNING ******************************
819 KERNCONF replaces the variable KERNEL for buildkernel. You
820 should update your scripts and make.conf accordingly.
823 config has changed to allow DEV_FOO as a replacement for NFOO.
824 This requires a new config to build correctly.
827 The kernel option I386_CPU is now mutually exclusive with the
828 other cpu types. If you have an i386 system, be sure that it
829 only had this line. Remove it for all other configurations.
832 Changes to the kernel require it and burncd be in sync.
835 Everyone who has hw.sndunit set to something in
836 /etc/sysctl.conf, it is now hw.snd.unit.
839 ex and vi were broken by some changes to sys/queue.h. If you
840 have a bad vi, you will see make buildworld fail with a core
841 dump while building termcap. You can work around this problem
842 by adding -k to your make buildworld. This will cause the
843 build to complete and install a new vi. Once that's done, you
844 can rebuild again without the -k to pick up anything that
845 might have been ignored by the -k option.
847 Others have suggested that you can just rebuild libc if your
848 vi/ex is dynamically linked, but I've not received any reports
852 There have been some changes to libcrypt in -current. The
853 libscrypt/libdescrypt symlink silliness is gone and the installed
854 libcrypt is fully functional. Be aware of this.
857 Linksys Fast Ethernet PCCARD cards supported by the ed driver
858 now require the addition of flag 0x80000 to their config line
859 in pccard.conf(5). This flag is not optional. These Linksys
860 cards will not be recognized without it.
863 Important new FreeBSD-version stuff: PAM support has been worked
864 in, partially from the "Unix" OpenSSH version. This requires
865 adding the following in pam.conf:
867 sshd auth sufficient pam_skey.so
868 sshd auth required pam_unix.so try_first_pass
869 sshd session required pam_permit.so
875 The random device needs more entropy, so you need to make sure
876 that you've run mergemaster to get a /etc/rc which will seed
877 /dev/random. If you don't and the system hangs after ldconfig,
878 then banging on the keyboard randomly until it unhangs is one
882 ****************************** WARNING ******************************
883 Sendmail has been updated.
884 ****************************** WARNING ******************************
885 o mail.local(8) is no longer installed as a set-user-id binary.
886 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
888 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
890 o Now using sendmail's version of vacation(1).
891 o The sendmail cf building tools (contrib/sendmail/cf) are installed
892 in /usr/share/sendmail/cf.
893 o sendmail.cw changed to local-host-names
895 More details can be found at
896 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
899 The ports tree's new layout is in place. Be sure to update
900 your entire ports tree, or you will have problems.
903 The perl build procedure no longer installs miniperl, nor uses
904 the installed miniperl. It is recommended that you delete
908 This weekend the ports tree will be updated to a new layout.
909 It will be in an inconsistent state until noted in the UPDATING
910 file, or with asami-san's message to the relevant mailing
911 lists. With this new layout, you'll need to update the whole
912 tree for anything to work.
915 There was a change in the passwd format. Need more information.
918 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
919 place. Please update boot loader (not the boot blocks) at the
920 same time as your kernel.
923 The new pmtimer device is necessary for laptops. Failure to
924 include the device will cause suspended laptops losing time
925 when they resume. Include
927 in your config file and
928 hint.pmtimer.0.at="isa"
929 to your /boot/device.hints file.
932 The random device has been turned into a (pseudo-)device,
933 rather than an option. The supplied kernel config files have
934 been updated. You will need to do something similar in your
935 own kernel config file.
940 If you prefer to load the loadable module, you need to do
944 The random device module has been renamed from randomdev.ko to
945 random.ko. You will need to edit your /boot/loader.conf to
946 reflect this if you load this module at boot time.
947 The line should read:
951 The SMPNG commit has happened. It should work, but if it
952 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
953 to be a variety of minor issues. Please see 20000905 to make
954 sure you don't have model loading problems which might at
955 first blush appear related to SMP.
958 nsswitch has been imported from NetBSD. Among other things,
959 this means that /etc/host.conf is no longer used. See
960 nsswitch.conf(5) instead. Note that at boot time rc.network
961 will attempt to produce a new nsswitch.conf file for you if you
962 don't have one, and you have host.conf.
965 The ucred structure changed size. This breaks the interface
966 that mountd uses. Trying to use an older mountd with a newer
967 kernel guarantees a panic. This means that you need to use
968 kernels newer than today only with matching mountd, but you
969 needed to do that anyway with the boot loader changes.
972 The boot loader has been updated. The new default kernel is
973 now /boot/kernel/kernel.ko. The new default module location
976 You *MUST* upgrade your boot loader and kernel at the same time.
977 The easiest way to do this is to do the buildworld/buildkernel/
978 installkernel/installworld dance.
980 Furthermore, you are urged to delete your old /modules directory
981 before booting the new kernel, since kldload will find stale
982 modules in that directory instead of finding them in the correct
983 path, /boot/kernel. The most common complaint that this cures
984 is that the linux module crashes your machine after the update.
986 if [ ! -d /boot/kernel.old ]; then
987 mv /modules.old /boot/kernel.old
988 chflags noschg /kernel.old
989 mv /kernel.old /boot/kernel.old/kernel.ko
990 chflags schg /boot/kernel.old/kernel.ko
994 A new issue with the sendmail upgrade has come to light.
995 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
996 incorrectly install the default aliases in /etc/mail rather than
997 move the old one from /etc. So you'll need to manually move the
998 file, create a symbolic link, remove the old /etc/aliases.db and
999 run newaliases. For safety sake, you should stop sendmail
1000 while doing this and run the upgrade when locally sourced email
1001 is not likely to be generated.
1004 /boot/device.hints is now required for installkernel to
1005 succeed. You should copy GENERIC.hints for your architecture
1006 into /boot/device.hints. If and only if you compile hints
1007 into your kernel, then this file may be empty. Please note,
1008 if you have an empty or missing /boot/device.hints file and
1009 you neglected to compile hints into your kernel, no boot
1010 messages will appear after the boot loader tries to start the
1014 If you do NOT have ``options RANDOMDEV'' in your kernel and
1015 you DO want the random device then add randomdev_load="YES" to
1019 suidperl is now always built and installed on the system, but
1020 with permissions of 511. If you have applications that use
1021 this program, you are now required to add ENABLE_SUIDPERL=true
1022 to /etc/make.conf. If you forget to do this,
1023 chmod 4511 /usr/bin/suidperl
1024 will fix this until the next build.
1027 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1028 visible changes that may immediately affect your configuration
1030 - New default file locations from src/contrib/sendmail/cf/README
1031 - newaliases limited to root and trusted users
1032 - MSA port (587) turned on by default
1033 - New queue file naming system so can't go from 8.11 -> 8.9
1034 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1035 - FEATURE(`nullclient') is more full featured
1036 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1037 - mail.local FreeBSD-only -b option changed to -B
1038 - See src/contrib/sendmail/RELEASE_NOTES for more info
1041 suidperl (aka sperl) is no longer build by default. You must
1042 specifically define BUILD_SUIDPERL to "true" for it to be build.
1043 Furthermore, we recommend that you remove /usr/bin/sperl* and
1044 /usr/bin/suidperl files from your system unless you have a
1045 specific use for it.
1048 Networking defaults have been tightened. Anybody upgrading
1049 /etc/defaults/rc.conf needs to add the following lines to
1050 /etc/rc.conf if they want to have the same setup
1051 afterwards (unless the variables already are set, of course):
1052 # Enable network daemons for user convenience.
1054 portmap_enable="YES"
1055 sendmail_enable="YES"
1058 If you have null_load="YES" in your /boot/loader.conf, you
1059 will need to change that to nullfs_load="YES".
1062 The "installkernel" target has changed slightly. Now even if
1063 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1064 it will install the MYKERNEL file (built with the buildkernel
1065 target) as /kernel rather than /MYKERNEL. Those who have
1066 updated their /boot/loader.conf files to point to /MYKERNEL
1067 should remove that entry or perform manual rename of /kernel
1071 If you use CVSUP or CTM to get CVS trees, AND you used to get
1072 the old crypto files from internat.freebsd.org AND you check
1073 out files from the CVS tree with the cvs command, please read
1074 http://people.freebsd.org/~imp/internat.txt
1075 for details on potential problems that you might have and how
1078 If you are merely a mirror, or don't answer yes to each of the
1079 clauses above, you needn't worry.
1082 /etc/security has been updated to print the inode number of
1083 setuid programs that have changed. You will see a large spike
1084 in the number of changed programs the first time when you run
1085 mergemaster to get a new /etc/security.
1088 /dev/random now has good entropy collection (from the keyboard
1089 and sysmouse drivers). Please ensure that either `options
1090 RANDOMDEV' is present in your kernel config file or that
1091 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1092 not have the /dev/random driver, OpenSSL (and consequently
1093 lots of crypto tools (like SSH)) will fail with strange
1094 errors. (see below, 20000624).
1096 FreeBSD-current is safe again to run Crypto.
1099 phk made the malloc default options AJ. This may slow things
1100 down and uncover other latent bugs in the code. If you need to
1101 run at full speed, you can disable this by doing the following:
1102 ln -s aj /etc/malloc.conf
1105 libftpio's version was accidentally bumped a few days ago. This
1106 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1107 before doing your next buildworld/installworld pair. It certainly
1108 won't hurt to remove it before the update procedure. It will
1109 break fetch until a new one is built, but ftp can be used in the
1113 The crypto packages have changed for the cvsup. This has been done
1114 in a backward compatible way, but the old packages will go away at
1115 some point in the future. Look at /usr/share/examples/cvsup for
1119 With the new sys/modules/sound/drivers/*, you will need to
1120 set SYSDIR until you do an installworld after July 7th.
1123 rc.shutdown and rc will now call the rc.d scripts with start
1124 or stop. This may cause some harmless warnings from older
1125 rc.d scripts that haven't been updated.
1128 The libfetch based version of fetch has gone into the tree.
1129 Minor problems may result on some of the less popular sites,
1130 which should be reported to des@freebsd.org.
1133 From approximately this date forward, one must have the crypto
1134 system installed in order to build the system and kernel.
1135 While not technically strictly true, one should treat it as
1136 required and grab the crypto bits. If you are grabbing CVS
1137 trees, src-all and cvs-crypto should be treated as if they
1138 were required. You should check with the latest collections
1139 to make sure that these haven't changed.
1142 Mark Murray just committed the first parts of a cleanup of
1143 /dev/zero, et al. This is also cleaning up /dev/random.
1144 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1145 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1146 until Mark can merge in the fixes to this work in progress.
1147 openssh and openssl should not be used to generate keys from this
1148 date to the completion of the work.
1150 If you must operate at this reduced level of security, add '
1151 options RANDOMDEV' to your kernel or modload the randomdev
1152 module. You may also need to copy a new MAKEDEV to /dev and
1153 recreate the random and urandom devices.
1156 The license on the softupdates is now a standard 2 clause
1157 BSD license. You may need to remove your symbolic links
1158 that used to be required when updating.
1161 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1162 the config file update procedure.
1163 http://people.freebsd.org/~imp/config-upd.html
1164 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1165 isn't buildable. However, you can generate a LINT file:
1166 cd /sys/<ARCH>/conf && make LINT
1169 Binutils 2.10 have hit the tree, or will shortly. As soon
1170 as they do, the problem noted in 20000522 will be resolved and
1171 that workaround will no longer be required.
1174 phk removed the compatibility creation of wd devices in the
1175 ad driver. If you haven't done so already, you must update
1176 your fstab, etc to use the ad devices instead of the wd
1179 In addition, you'll need to update your boot blocks to a
1180 more modern version, if you haven't already done so. Modern
1181 here means 4.0 release or newer (although older releases
1185 Peter took an axe to config(8). Be sure that you read his mail
1186 on the topic before even thinking about updating. You will
1187 need to create a /boot/device.hints or add a hints directive
1188 to your config file to compile them in statically. The format
1189 of the config file has changed as well. Please see GENERIC or
1190 NEWCARD for examples of the new format.
1192 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1193 says that it has been fixed, assume that must use the hints mechanism
1194 in the loader if you need to use a machine with very old ISA cards
1198 A new set of binutils went into the tree today. Anybody
1199 building a kernel after this point is advised that they need
1200 to rebuild their binutils (or better yet do a
1201 buildworld/installworld) before building a new kernel.
1203 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1204 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1205 is recommended that you don't set this option until the problem
1209 The ethernet drivers were all updated to clean up the BPF handling.
1212 The problems with boot blocks on the alphas have been corrected.
1213 This will require some care in updating alphas. A new libstand
1214 is requires for the boot blocks to build properly.
1217 Recompile all kld modules. Proper version dependency info
1221 Modules have been disconnected from the buildworld tree and
1222 connected to the kernel building instead.
1225 You may need to build gperf
1226 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1227 when upgrading from 4.0 -> current. The build system now uses
1228 an option only in -current.
1231 The method that we brand ELF binaries has changed to be more
1232 acceptable to the binutils maintainers. You will need to
1233 rebrand your ELF binaries that aren't native. One problem
1234 binary is the Linux ldconfig. After your make world, but
1235 before you reboot, you'll need to issue:
1236 brandelf -t Linux /compat/linux/sbin/ldconfig
1237 if you have Linux compatibility enabled on your machine.
1240 If you have really bad/marginal IDE drives, you may find they
1241 don't work well. Use pio mode instead. The easiest way to
1242 cope if you have a problem combination is to add:
1243 /sbin/sysctl hw.ata.ata_dma=0
1244 to the start of /etc/rc.conf.
1247 The ISA and PCI compatibility shims have been connected to the
1248 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1249 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1250 include the appropriate option in your kernel config. Drivers
1251 using the shims should be updated or they won't ship with
1252 5.0-RELEASE, targeted for 2001.
1255 We've entered the traditional post release dumping party.
1256 Large kernel changes are being committed and are in the
1257 works. It is important to keep the systems' klds and kernel
1258 in sync as kernel interfaces and structures are changing.
1259 Before reporting kernel panics, make sure that all modules
1260 that you are loading are up to date.
1263 If you are upgrading from an older version of FreeBSD, you
1264 need to update your boot blocks as well. 'disklabel -B ad0'
1265 will do the trick. This isn't critical until you remove your
1266 wd device entries in /dev, at which point your system will not
1270 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1271 to upgrade to 4.0 from 3.x.
1277 Avoid using make -j when upgrading. From time to time in the
1278 past there have been problems using -j with buildworld and/or
1279 installworld. This is especially true when upgrading between
1280 "distant" versions (eg one that cross a major release boundary
1281 or several minor releases, or when several months have passed
1282 on the -current branch).
1284 Sometimes, obscure build problems are the result of environment
1285 poisoning. This can happen because the make utility reads its
1286 environment when searching for values for global variables.
1287 To run your build attempts in an "environmental clean room",
1288 prefix all make commands with 'env -i '. See the env(1) manual
1289 page for more details.
1293 If you are updating from a prior version of FreeBSD (even one just
1294 a few days old), you should follow this procedure. With a
1295 /usr/obj tree with a fresh buildworld,
1296 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1297 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1299 To just build a kernel when you know that it won't mess you up
1300 --------------------------------------------------------------
1301 cd src/sys/{i386,alpha}/conf
1302 config KERNEL_NAME_HERE
1303 cd ../../compile/KERNEL_NAME_HERE
1308 If this fails, go to the "To build a kernel" section.
1310 To rebuild everything and install it on the current system.
1311 -----------------------------------------------------------
1312 # Note: sometimes if you are running current you gotta do more than
1313 # is listed here if you are upgrading from a really old current.
1315 <make sure you have good level 0 dumps>
1316 <maybe fix /etc/fstab> [7]
1318 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1319 make installkernel KERNCONF=YOUR_KERNEL_HERE
1321 <reboot in single user> [3]
1328 To cross-install current onto a separate partition
1329 --------------------------------------------------
1330 # In this approach we use a separate partition to hold
1331 # current's root, 'usr', and 'var' directories. A partition
1332 # holding "/", "/usr" and "/var" should be about 2GB in
1335 <make sure you have good level 0 dumps>
1338 <maybe newfs current's root partition>
1339 <mount current's root partition on directory ${CURRENT_ROOT}>
1340 make installworld DESTDIR=${CURRENT_ROOT}
1341 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1342 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1343 ${CURRENT_ROOT}/boot/device.hints # as needed
1344 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1345 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1346 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1347 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1348 <reboot into current>
1349 <do a "native" rebuild/install as described in the previous section>
1350 <maybe install compatibility libraries from /usr/src/lib/compat>
1354 To upgrade in-place from 4.x-stable to current
1355 ----------------------------------------------
1356 # 5.x uses more space than 4.x. Also, the location of kernel
1357 # modules has changed. If you are installing 5.0 onto a 4.x
1358 # system, you'll need about 30MB of free disk space on your /
1359 # partition. If you have less than this, you may encounter difficult
1360 # to back out of problems with this procedure. If /tmp is on
1361 # the / partition, you may want to completely remove all its content
1362 # before upgrading, as this can be a common source of shortage of
1365 <make sure you have good level 0 dumps>
1366 <maybe fix /etc/fstab> [7]
1368 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1369 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1370 make installkernel KERNCONF=YOUR_KERNEL_HERE
1371 cd src/sys/boot ; make install [6]
1373 <reboot in single user> [3]
1375 rm -rf /usr/include/g++
1380 Make sure that you've read the UPDATING file to understand the
1381 tweaks to various things you need. At this point in the life
1382 cycle of current, things change often and you are on your own
1383 to cope. The defaults can also change, so please read ALL of
1384 the UPDATING entries.
1386 Also, if you are tracking -current, you must be subscribed to
1387 freebsd-current@freebsd.org. Make sure that before you update
1388 your sources that you have read and understood all the recent
1389 messages there. If in doubt, please track -stable which has
1390 much fewer pitfalls.
1392 [1] If you have third party modules, such as vmware, you
1393 should disable them at this point so they don't crash your
1396 [2] If you have legacy ISA devices, you may need to create
1397 your own device.hints to reflect your unique hardware
1400 [3] From the bootblocks, boot -s, and then do
1405 adjkerntz -i # if CMOS is wall time
1406 Also, when doing a major release upgrade, it is required that
1407 you boot into single user mode to do the installworld.
1408 For the 4.x -> 5.0 upgrade, you will also see many messages about
1409 needing to recompile your userland. These are harmless and can
1410 be ignored while you proceed to the next step.
1412 [4] Note: This step is non-optional. Failure to do this step
1413 can result in a significant reduction in the functionality of the
1414 system. Attempting to do it by hand is not recommended and those
1415 that pursue this avenue should read this file carefully, as well
1416 as the archives of freebsd-current and freebsd-hackers mailing lists
1417 for potential gotchas.
1419 [5] Usually this step is a noop. However, from time to time
1420 you may need to do this if you get unknown user in the following
1421 step. It never hurts to do it all the time. You may need to
1422 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1423 install) after the buildworld before this step if you last updated
1424 from current before 20020224 or from -stable before 20020408.
1426 [6] 4.x boot loader can be used to boot a 5.x system, however
1427 it is difficult to do that at best. If you wish to try, then
1428 you should interrupt the boot and at the ok prompt type:
1430 ok boot /boot/kernel/kernel
1431 If this fails to work, you must install a new boot loader as
1434 [7] Before you upgrade, please make sure that you are not using
1435 compatibility slices. These are device names of the form, on i386
1436 and other architectures that use MBR slicing, /dev/ad0a without the
1437 actual slice name. Chances are excellent that these will break.
1438 You generally must update these entries to use the post FreeBSD
1439 2.x form of /dev/ad0s1a.
1441 [8] In order to have a kernel that can run the 4.x binaries
1442 needed to do an installworld, you must include the COMPAT_FREEBSD4
1443 option in your kernel. Failure to do so may leave you with a system
1444 that is hard to boot to recover.
1446 [9] When checking out sources, you must include the -P flag to have
1447 cvs prune empty directories.
1450 This file contains a list, in reverse chronological order, of major
1451 breakages in tracking -current. Not all things will be listed here,
1452 and it only starts on March 15, 2000. Updating files can found in
1453 previous releases if your system is older than this.
1455 Copyright information:
1457 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1459 Redistribution, publication, translation and use, with or without
1460 modification, in full or in part, in any form or format of this
1461 document are permitted without further permission from the author.
1463 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1464 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1465 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1466 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1467 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1468 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1469 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1470 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1471 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1472 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1473 POSSIBILITY OF SUCH DAMAGE.
1475 If you find this document useful, and you want to, you may buy the
1478 Contact Warner Losh if you have any questions about your use of