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 libkse has been renamed back to libpthread and is now the
22 default threads library. The gcc -pthread option has also
23 been changed to link to libpthread instead of libc_r. For
24 alpha and sparc64 machines, libkse is not renamed and links
25 are installed so that libpthread points to libc_r. Until
26 the ports system is updated to handle this change, it is
27 recommended that folks install an /etc/libmap.conf(5) that
28 maps libc_r to libpthread. If you have any binaries or
29 libraries linked to libkse, then it is also recommended
30 that you map libkse to libpthread. Anyone that is using
31 nvidia supplied drivers and libraries should use a libmap.conf
32 that maps libpthread to libc_r since their drivers/libraries
33 do not work with libpthread.
36 ULE has entered into its probationary period as the default scheduler
37 in GENERIC. For the average user, interactivity is reported to be
38 better in many cases. On SMP machines ULE will be able to make more
39 efficient use of the available parallel resources. If you are not
40 running it now, please switch over, replacing the kernel option
41 SCHED_4BSD with SCHED_ULE.
44 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
45 if the login process is unable to successfully set the
46 process credentials to include all groups defined for the
47 user. The current kernel limit is 16 groups; administrators
48 may wish to check that users do not have over 16 groups
49 defined, or they will be unable to log in.
52 The ACPI module has been reactivated. It is no longer required
53 to compile ACPI support into kernels statically.
56 The statfs structure has been updated with 64-bit fields to
57 allow accurate reporting of multi-terabyte filesystem
58 sizes. You should build world, then build and boot the new kernel
59 BEFORE doing a `installworld' as the new kernel will know about
60 binaries using the old statfs structure, but an old kernel will
61 not know about the new system calls that support the new statfs
63 Note that the backwards compatibility is only present when the
64 kernel is configured with the COMPAT_FREEBSD4 option. Since
65 even /bin/sh will not run with a new kernel without said option
66 you're pretty much dead in the water without it. Make sure you
68 Running an old kernel after a `make world' will cause programs
69 such as `df' that do a statfs system call to fail with a bad
70 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
71 that cfsd (ports/security/cfs) needs to be recompiled after
72 these changes are installed.
74 ****************************DANGER*******************************
76 DO NOT make installworld after the buildworld w/o building and
77 installing a new kernel FIRST. You will be unable to build a
78 new kernel otherwise on a system with new binaries and an old
82 Some netgraph string length constants have been changed. This
83 change requires the netgraph kernel modules and all netgraph
84 userland components to be in sync. Especially users who require
85 netgraph to boot need to make sure to have world and kernel in
86 sync before rebooting.
89 Hyperthreading logical CPU's are no longer probed by default
90 when using the MP Table. If ACPI is being used, then logical
91 CPUs will be probed if hyperthreading is enabled in the BIOS.
92 If ACPI is not being used and hyperthreading is enabled in the
93 BIOS, logical CPUs can be enabled by building a custom kernel
94 with the option MPTABLE_FORCE_HTT enabled.
97 The i386 APIC_IO kernel option has been replaced by
98 'device apic'. The ACPI module has also been temporarily
99 disabled, so ACPI must be statically compiled into your
100 kernel using 'device acpi' if you wish to use the ACPI driver.
103 The API and ABI of struct ifnet have been changed by removing
104 the if_name and if_unit members and replacing them with
105 if_xname, if_dname, and if_dunit. All network drivers and most
106 userland programs which include net/if_var.h must be updated
107 and recompiled. __FreeBSD_version has been bumped to 501113 to
111 Changes to the cdevsw default functions have been made to remove
112 the need to specify nullopen() and nullclose() explicitly.
113 __FreeBSD_version bumpted to 501110.
116 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
117 mount_cd9660(8) need to be in sync with kernel.
120 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
121 also be explicitly configured. Previously this dependency was
122 magically handled through some cruft in net/pfil.h; but that has
123 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
124 will fail with obtuse errors in ip_fil.c.
127 Fix a bug in arplookup(), whereby a hostile party on a locally
128 attached network could exhaust kernel memory, and cause a system
129 panic, by sending a flood of spoofed ARP requests. See
130 FreeBSD-SA-03:14.arp.
133 A change to /etc/defaults/rc.conf now causes inetd to be started
134 with `-C 60' if it is not overridden in /etc/rc.conf. This
135 causes inetd to stop accepting connections from an IP address
136 that exceeds the rate of 60 connections per minute.
139 The following rc.d scripts have been removed and should be
140 deleted from your installation: atm2.sh atm3.sh devdb
141 localdaemons network1 network2 network3. Depending on when
142 you last updated world and used mergemaster(8) you may or
143 may not have problems during the rc boot sequence. The simplest
144 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
145 The atm2.sh atm3.sh and devdb scripts were removed some time
146 ago, so depending on when you installed -CURRENT these scripts
147 may or may not exist on your system.
150 ATAng has been committed. You need to build world as sys/ata.h
151 has changed, and userland atacontrol depends on it.
152 If you use ATA SW raids you need "device ataraid" in your
153 kernel config file, as it is no longer pulled in automatically.
156 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
157 Among other things, this changes the device enumeration to be
158 closer to Solaris. Be aware that, this can even cause the machine
159 to not boot without manual intervention before the fstab is adjusted.
162 All current USB and Firewire quirks in da(4) have been deprecated
163 and will be removed for 5.2. If this causes failure for your
164 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
165 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
166 so the quirk can be re-enabled.
169 FPU-less support has been removed from FreeBSD. Chances are you won't
170 notice. 386+387 support should still work after this change, but
171 it is now a minimum requirement for the i386 port that you have real
175 Some people are having problems with changes related to /rescue.
176 If you are building -j N, you will need to define NO_RESCUE. Others
177 will need to define it if /rescue has issues with their environment.
178 People should report those issues to current@.
181 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
182 across this point. Further, it might be a good idea to remove
185 20030613: [retrospective]
186 There was a small window in which sed(1) was broken. If you
187 happen to have sed(1) installed during that window, which is
188 evidenced by an inability to build world with the failure
189 given below, you need to manually build and install sed(1)
190 (and only sed(1)) before doing anything else. This is a one-
191 time snafu. Typical failure mode:
193 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
194 targmatch.h:7:1: null character(s) ignored
195 targmatch.h:12:1: null character(s) ignored
196 targmatch.h:16:1: null character(s) ignored
199 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
200 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
201 usr.bin/sed/process.c).
204 Remove deprecated locale names and transition period code
205 for them, finishing switching to the new scheme. Check your
206 LANG environment variable.
209 CCD has been changed to be a fully GEOMified class. Kernel
210 and ccdconfig(8) needs to be in sync, this is particularly
211 important to remember beforehand if your source tree is on
212 a ccd device. Consider making a copy of the old ccdconfig
213 into /boot/kernel.good or wherever you keep your backup
217 Kerberos 5 (Heimdal) is now built by default. Setting
218 MAKE_KERBEROS5 no longer has any effect. If you do NOT
219 want the "base" Kerberos 5, you need to set NO_KERBEROS.
222 groff has been updated. If you try to do a buildworld and
223 get an infinite loop in troff, update to May 4th or newer. If you
224 have a newer kernel than userland, you may need to set the OSRELDATE
225 to 500110 in your environment before starting a buildworld.
228 The old rc system has been removed. Please report any problems
229 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
230 Your personal versions of these files will not be removed, so you can
231 continue to use them. However, you should take great care when updating,
232 especially when using mergemaster, since the compatibility code that
233 utilizes these old scripts has also been removed.
236 A bug has been fixed in /dev/devctl which would cause devd
237 to hang on boot, were it not for a workaround in devd. The
238 work around in devd will be removed around 20030507. You
239 have until then to upgrade your kernel before updating
240 userland. In general, you should have a userland and
241 kernel that's in sync with each other. However, given the
242 effects of this bug (hang on boot when starting devd), some
246 Alphas with libc from between 20030312 and 20030329 exhibit
247 floating point exceptions (FPEs), most notably in awk(1)
248 while upgrading the system through a buildworld.
250 So, to successfully upgrade your Alpha, you must either
251 downgrade your libc.so to a pre-20030312 version, or update
252 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
253 to CFLAGS, then forcibly rebuild and install libc:
255 cd /usr/src/lib/libc && \
256 make cleandir && make obj && \
257 make -DNOMAN -DNOPROFILE all && \
258 make -DNOMAN -DNOPROFILE install
261 sendmail 8.12.7 has been imported. It has one important
262 change for IPv6 users. The default submit.mc now uses
263 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
264 used to connect to the MTA. Users on IPv6-only machines
265 will need to edit /etc/mail/submit.mc appropriately.
268 NODEVFS option has been removed and DEVFS thereby made standard.
269 This makes all references to MAKEDEV obsolete, and they should
270 be removed when convenient.
273 The name of the device for the ofw console has changed, sparc64 users
274 must run mergemaster to update their installed /etc/ttys.
277 The scheduler framework has grown a second scheduler and consequently
278 you must specify one and only one scheduler in your kernel config.
279 The cvs config files have been updated to use the old scheduler
280 which may be selected via 'options SCHED_4BSD'. If you would like
281 to try the new, much more experimental, scheduler please try
282 'options SCHED_ULE' and contribute to the arch@ discussion.
285 A new version of the wi driver has been imported into the tree.
286 One now must have device wlan in the config file for it to operate
289 In addition, there have been some changes to how wi devices are
290 configured for point to point links to bring it more in line
291 with the former way of doing things, as well as compatibility
295 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
296 used an incompatible form of ABI for returning structures and unions
297 which FreeBSD's GCC maintainers were not aware of relative to previous
298 versions of FreeBSD. We have gone back to the ABI for now, and any
299 code compiled which is required to interoperate with other code (not
300 built at the same time) returning structs or unions should be
304 A name change in /etc/netconfig has been reverted to stay
305 compatible with suns TIRPC and also with NetBSD. You need
306 to run mergemaster after make world. A new libc does still work
307 with an outdated /etc/netconfig for some time, but you'll get
308 a warning. This warning will be removed in 20030301.
311 The recent binutils upgrade marks a kernel flag day on
312 sparc64: modules built with the old binutils will not work
313 with new kernels and vice versa. Mismatches will result in
314 panics. Make sure your kernel and modules are in sync.
317 The value of IPPROTO_DIVERT has changed. Make sure to keep
318 your kernel, netstat, natd and any third-party DIVERT
322 Old, compatibility slices have been removed in GEOM kernels.
323 This means that you will have to update your /etc/fstab to
324 not use disk devices of the form /dev/ad0a. Instead, you
325 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
326 partition really is on. The old device names have gone
327 away, so if you use them anywhere else, you must also adjust
328 those uses. (This doesn't affect the disks formatted in
329 the ``dangerously-dedicated'' mode.)
332 Alphas with kernels from between 20020830 and 20021023 and/or
333 rtld (ld-elf.so.1) older than 20021023 may experience problems
334 with groff while doing a buildworld (kernel: "out of memory",
335 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
336 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
338 So, to successfully upgrade your Alpha, you must either
339 upgrade your kernel and rtld first (which might be a bit
340 tricky), or avoid running the bootstrapped groff during the
341 "transitional" buildworld. To avoid running groff during the
342 transitional upgrade run make buildworld with -DNOMAN,
343 -DNO_SHAREDOCS, and -DNO_LPR.
346 gcc has been upgraded to 3.2. It is not all binary compatible
347 with earlier versions of gcc for c++ programs. All c++
348 programs and libraries need to be recompiled.
350 Also, if you encounter g++ issues, rm /usr/include/g++/* before
351 doing an installworld to make sure that stale files are removed.
354 Our /etc/termcap now has all the entries from the XFree86 xterm
355 almost unchanged. This means xterm now supports color by default.
356 If you used TERM=xterm-color in the past you now should use
357 TERM=xterm. (xterm-color will lead to benign warnings).
360 A "bug" in gcc(1) that was hiding warning in system headers was
361 fixed. It's probably time to add -DNO_WERROR to your make line
365 COPY is being deprecated. The 20010530 change was reverted, as
366 it causes far more pain than was expected, and to always compare
367 before installing, please use INSTALL="install -C" again. The
368 -C option is now silently ignored when used with the -d option.
371 Problems with libc_r clients like KDE and GNOME have been resolved.
372 There are still some minor problems with some signals but the
373 system is stable enough for general use again. SMP is less so than UP
374 but each can successfully complete multiple buildworlds.
375 Libkvm needs to be recompiled due to KSE.
378 Now would be a bad time to upgrade. Something in or near the
379 KSE commit totally broke programs using libc_r like KDE and
383 The k5su utility installed as part of Kerberos 5 is no longer
384 installed with the set-user-ID bit set by default. Add
385 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
386 with the set-user-ID bit set.
389 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
390 Unfortunately our native GDB (at version 4.18) does not understand
391 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
392 generated debugging information for our native GDB.
395 Due to the way CVS works, it may not properly update src/contrib/gcc
396 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
397 and then do a cvs update.
400 When exec'ing set[ug]id executables, the kernel now ensures that the
401 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
404 New sendmail startup scripts have been installed to make it
405 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
406 variable sendmail_enable to "NO" no longer prevents any sendmail
407 daemons from starting. Instead, either set sendmail_enable to
408 "NONE" or change mta_start_script to a script for starting
409 an alternative MTA. Setting mta_start_script to "" will
410 also prevent any MTA from being started at boot.
413 UCONSOLE is no longer a valid kernel option.
416 FreeBSD 5.0 DP-1 was basically branched today.
419 Warnings are now errors in the kernel. Unless you are a developer,
420 you should add -DNO_WERROR to your make line.
423 sendmail 8.12.2 has been imported. The sendmail binary is no
424 longer a set-user-ID root binary and the infrastructure to support
425 command line mail submission has changed. Be sure to run
426 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
427 and /etc/mail) and read /etc/mail/README for more details.
429 Due to the import of sendmail 8.12.2, a new user and group are
430 required in order for sendmail to run as a set-group-ID
431 binary. A 'make installworld' will use the new user and group
432 to set the owner and group of /var/spool/clientmqueue and will
433 fail if the new user and group do not exist. The 'smmsp' user
434 and group must be merged from src/etc/group and
435 src/etc/master.passwd before using 'make installworld'.
436 'mergemaster -p' will do this. You may need to install
437 mergemaster before this will work if you are updating from a
438 very old version of current. The updating recipe has changed
442 The preferred configuration method for PAM is now /etc/pam.d/
443 rather than /etc/pam.conf. If you have an unmodified
444 pam.conf, just delete it after your next mergemaster run. If
445 you have local modifications, you can use
446 /usr/src/etc/pam.d/convert.pl to incorporate them into your
449 Please see the following url for more details:
450 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
452 If anyone here is already using the new rc.conf(5) variable
453 networkfs_types, please note that it has changed
454 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
457 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
458 started out its life in the ISDN4BSD project as an offspring
459 from sys/net/if_spppsubr.c, which eventually got a life of its
460 own. All the accumulated features and bugfixes of the i4b
461 version have now been merged back into the base system's
462 version now. The only user-visible change resulting from this
463 is that i4b's sppp(4) interfaces are to be managed with
464 spppcontrol(8) again, since ispppcontrol(8) has been retired
465 as well. (There has never been rc file support for
466 ispppcontrol in -current, but only in -stable. That will be
467 reverted by the time the changes are MFCed.)
470 The fdc(4) driver has been updated and now automatically
471 recognizes media in `standard' formats (like 1440 KB and
472 720 KB for a 3.5" high-density drive) when accessing the
473 default device node (e. g. /dev/fd0). The old variety of
474 floppy device nodes /dev/fd*.* is no longer present by
475 default, devices can be created (in DEVFS) on demand. They
476 will need to be customized then for `odd' densities using
480 The bugs in procfs' debugging support code have been fixed,
481 and truss(1) now works again.
484 Daily security checks have been split out to use the periodic(8)
485 scripts. Some change in configuration may be necessary. Please
487 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
491 sos added VCD/SVCD support to ata driver and that needs the
492 kernel and burncd to be in sync.
495 The procfs pseudo-filesystem has now been converted to use the
496 pseudofs framework. If you have 'options PROCFS' in your
497 kernel config, you'll need to add 'options PSEUDOFS' if it's
500 This change temporarily breaks truss(1); use ktrace(1) instead
501 until the issue has been resolved.
504 A security hole in OpenSSH involving `UseLogin yes' has been
508 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
509 after this date. You need to do this only once.
512 Most of the awk issues have been resolved. Some rough
513 edges may be left, but for the most part things should be
514 back to "normal." For CURRENT's usual definition of "normal."
517 Awk has been upgraded to the one true awk from bell labs. Expect
518 choppy waves in the upgrade process.
521 The asr driver problem has been resolved.
524 Due to changes in other parts of the system, the asr driver
525 now causes the system to panic on boot. Do not use it pending
526 correction. Comment it out of any kernel config file that you
527 try to use from this date forward.
530 When crossbuilding, use TARGET=xxx where you used to use
531 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
532 unless you are changing both of them. To cross build pc98 on
533 an alpha, for example, you need to set TARGET=pc98 and
537 The kernel interface that burncd depends on has changed.
538 You must recompile both the kernel and userland applications
542 When crossbuilding, please set TARGET_ARCH rather than
543 MACHINE_ARCH to indicate the target. In the future, one will
544 set TARGET_MACHINE where you set MACHINE now. At the moment,
545 setting MACHINE alone for same MACHINE_ARCH machines works
546 (eg, you can build pc98 on an i386 machine and vice versa).
549 Some weird problems result from using ACPI on some machines.
550 To disable ACPI you can add
551 hint.acpi.0.disabled="1"
552 to /boot/loader.conf (or by putting set X=Y at the boot
555 Alternatively, you can remove it from /boot/kernel/acpi.ko
556 or use the MODULES_OVERRIDE function in your kernel config
557 file and not list acpi in that list.
560 The buildworld has been fixed. You may need to install
561 the 4.x compatibility libraries for some old binaries
562 to work. Add COMPAT4X=true to your /etc/make.conf to
563 get them installed on every installworld, or execute the
564 following to get them installed only once:
565 cd src/lib/compat/compat4x.<arch>
567 You will see ``__stdoutp undefined'' until you do this.
570 There's a bug in the world build process. The cross-tools
571 are build with the NEW headers, but the OLD libc.a. This
572 leads to all kinds of problems with the new libc. A temporary
574 CFLAGS="-O -pipe -D_OLD_STDIO"
575 before building world when upgrading from 4.x to current. This
576 can be removed afterwards.
578 A proper fix to the buildworld target is needed.
581 Peter has committed his new kthread nfs client/server code.
582 NFS may be unstable after this date.
585 KSE has hit the tree. Lots of things are now different in
586 the kernel. While a few problems were introduced in the
587 initial commit, most of the major ones have been found and
591 In OLDCARD, CardBus bridges appear to be stable. The work
592 arounds described in the 20010604 entry are now no longer
593 necessary and will be ignored. Most insert/remove problems
594 have been rectified around this date.
597 named now runs as user bind and group bind rather than as
598 root. If named_enable is set to YES in /etc/rc.conf, ensure
599 that user bind is available in /etc/passwd (using vipw(8))
600 and that group bind is available in /etc/group. Also make
601 sure that user or group bind has read (and not write)
602 permission for your name server configuration and that it
603 has read and write permission for your slave zone files and
606 If you wish to continue to run named as root (a less secure
607 alternative), add a line to /etc/rc.conf saying
612 The PAM libraries have had an API upgrade that is beyond
613 the ability of the shared library major number to handle.
614 It is manifested by PAM-using ports dumping core. The
615 solution is to rebuild those ports.
618 The kernel compile module has moved from src/sys/compile/FOO
619 to src/sys/${MACHINE}/compile/FOO.
622 The pccard modem issue from 20010613 has been corrected.
623 OLDCARD support is still a little weak in -current. slot 1 is
624 known not to work on some TI based cardbus bridges. Some
625 cardbus bridges do not properly detect insert/removal events.
626 IRQ configuration needs more safety belts.
629 Softupdates problems have been corrected.
632 Peter ripped out the linkerset support. You must, as always,
633 rerun config after you cvsup if you are using the traditional
634 kernel building methods.
637 pccard modems may not work with current after 20010604 date. Some
638 do, others result in panics. *MAKE*SURE* that you update your
639 config and /etc/rc.conf ala the 20010604 entry, or you will have
640 problems (this issue will be fixed, it just hasn't been yet).
643 SOFTUPDATES seem to be broken since the middle of May or so. Do not
644 use them in current. You can disable softupdates on all mounted
645 partitions, or remove SOFTUPDATES the kernel config file.
648 After Peter's commits to the hints code, people have been noticing
649 that certain devices are attached (or try to) twice. This is due
650 to having both static hints as well as a /boot/device.hints. To
651 work around this issue, please use only one or the other mechanism
652 until this bug is fixed.
654 Please note that a feature of config is that if you have config
655 file FOO and FOO.hints, it automatically adds FOO.hints to the
656 hints.c file, whether you want it to or not.
659 Locale names have changed to match other systems better.
662 pccard support for pci cards has been committed. You must change
663 your /etc/pccard.conf irq lines. It must match the irq used by
664 pcic device. Interrupt storms may result if you fail to do this.
665 Interrupt storms look a lot like a hang.
667 You must also install a new pccardd, otherwise you will get an
668 interrupt storm at card reset time (just after it tells you what
671 pccardd_flags="-I" is necessary for the time being. It tells pccardd
672 not to ask the kernel if the interrupt is really free or not before
673 using it. You can either change the /etc/pccard.conf irq lines to
674 match pcic, or add "-i X" to the pccardd_flags.
677 INSTALL=install -C is being deprecated. If you want to do this,
678 use COPY=-C instead. The former method will be supported for only
679 a limited time. If you see
681 install: warning: the -d and -C options may not be specified together
683 in your makeworld, then you need to migrate towards using
687 It appears that vm is now stable enough to use again. However,
688 there may be other problems, so caution is still urged. alpha
689 definitely is in bad shape.
692 Minor repo damage has happened. This may cause problems
693 with cvsup of ports. If you get errors, please see
694 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
695 at the bottom for details on a workaround. The error message
697 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
700 Vm and/or swapping are busted on -current. Please be patient.
703 pccard has had much reorganizational work done to it over
704 the past few days. Everything should still work, but if
705 not, please contact imp@freebsd.org.
708 ata ioctl changed. Make sure to recompile both kernel and
709 userland at the same time.
712 New ncurses imported.
715 DEVFS is now opt out, not opt in. Barring major problems, this
716 will be the only way to go starting July 1.
719 OpenSSH has been updated to 2.9. Some defaults are different,
720 including RhostsRSAAuthentication, which changes from yes to no.
723 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
726 Building perl was broken at 02:25:25 PDT.
729 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
730 go back in the water.
733 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
734 this date, but before the correction date.
737 old fsck and new kernel interactions appear to have been fixed.
740 fsck and the kernel were changed to handle some optimizations
741 to directory layout. This breaks backward compatibility.
742 Update only if you understand that you must not use the old
743 fsck with the new kernel ever.
746 fsck has changed the meaning of the pass column in /etc/fstab.
747 Please see the cvs commit to fsck.8 or the fsck.8 man page for
748 details. It is unclear if changes to /etc/fstab are necessary.
751 portmap had changed name to rpcbind for maximum POLA in your
752 current world. /etc/hosts.{allow,deny} needs changes. nfs and
753 other rpc based programs that rely on portmapper will not work
754 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
757 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
758 and ATA_ENABLE_TAGS are no longer kernel options. They have
759 been replaced by tunables. See ata.4 for details.
762 The fxp driver was converted to use miibus. If you compile
763 fxp into your kernel statically, you will need to add miibus.
766 The wi device now defaults to BSS (infrastructure) mode
770 /dev/urandom should be a symbolic link to /dev/random now.
771 Users of current not using DEVFS need to run MAKEDEV std.
772 ssh might not work if you don't.
775 The ed driver has been updated. It now allows mii attachments,
776 which means that you must include the miibus in your kernel if
777 you use the ed driver.
780 The problems with libc have been corrected. It is now mostly
781 safe to go back into the water.
784 The size of FILE was changed. This breaks upgrading. If
785 you must upgrade, be prepared for pain. It also breaks almost
786 all binaries that you've compiled on -current. You are warned
787 that before upgrading would be a good time to do a level 0
788 dump of your system. No, really, I mean it this time.
790 To get to the new system, you'll need to use the following
791 workaround. Hopefully this can be sorted out so that we
792 don't have to move this to the updating section.
794 To get around the installworld problem, do:
795 # cd /usr/src/usr.bin/sed
799 If that doesn't work, then try:
800 # make -k installworld
804 DEVFS is now the default. If you use vinum, make sure that you
805 do not include devfs in your kernel as problems result.
808 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
809 Remove them from your config.
812 ****************************** WARNING ******************************
813 buildkernel has been changed slightly
814 ****************************** WARNING ******************************
815 KERNCONF replaces the variable KERNEL for buildkernel. You
816 should update your scripts and make.conf accordingly.
819 config has changed to allow DEV_FOO as a replacement for NFOO.
820 This requires a new config to build correctly.
823 The kernel option I386_CPU is now mutually exclusive with the
824 other cpu types. If you have an i386 system, be sure that it
825 only had this line. Remove it for all other configurations.
828 Changes to the kernel require it and burncd be in sync.
831 Everyone who has hw.sndunit set to something in
832 /etc/sysctl.conf, it is now hw.snd.unit.
835 ex and vi were broken by some changes to sys/queue.h. If you
836 have a bad vi, you will see make buildworld fail with a core
837 dump while building termcap. You can work around this problem
838 by adding -k to your make buildworld. This will cause the
839 build to complete and install a new vi. Once that's done, you
840 can rebuild again without the -k to pick up anything that
841 might have been ignored by the -k option.
843 Others have suggested that you can just rebuild libc if your
844 vi/ex is dynamically linked, but I've not received any reports
848 There have been some changes to libcrypt in -current. The
849 libscrypt/libdescrypt symlink silliness is gone and the installed
850 libcrypt is fully functional. Be aware of this.
853 Linksys Fast Ethernet PCCARD cards supported by the ed driver
854 now require the addition of flag 0x80000 to their config line
855 in pccard.conf(5). This flag is not optional. These Linksys
856 cards will not be recognized without it.
859 Important new FreeBSD-version stuff: PAM support has been worked
860 in, partially from the "Unix" OpenSSH version. This requires
861 adding the following in pam.conf:
863 sshd auth sufficient pam_skey.so
864 sshd auth required pam_unix.so try_first_pass
865 sshd session required pam_permit.so
871 The random device needs more entropy, so you need to make sure
872 that you've run mergemaster to get a /etc/rc which will seed
873 /dev/random. If you don't and the system hangs after ldconfig,
874 then banging on the keyboard randomly until it unhangs is one
878 ****************************** WARNING ******************************
879 Sendmail has been updated.
880 ****************************** WARNING ******************************
881 o mail.local(8) is no longer installed as a set-user-id binary.
882 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
884 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
886 o Now using sendmail's version of vacation(1).
887 o The sendmail cf building tools (contrib/sendmail/cf) are installed
888 in /usr/share/sendmail/cf.
889 o sendmail.cw changed to local-host-names
891 More details can be found at
892 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
895 The ports tree's new layout is in place. Be sure to update
896 your entire ports tree, or you will have problems.
899 The perl build procedure no longer installs miniperl, nor uses
900 the installed miniperl. It is recommended that you delete
904 This weekend the ports tree will be updated to a new layout.
905 It will be in an inconsistent state until noted in the UPDATING
906 file, or with asami-san's message to the relevant mailing
907 lists. With this new layout, you'll need to update the whole
908 tree for anything to work.
911 There was a change in the passwd format. Need more information.
914 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
915 place. Please update boot loader (not the boot blocks) at the
916 same time as your kernel.
919 The new pmtimer device is necessary for laptops. Failure to
920 include the device will cause suspended laptops losing time
921 when they resume. Include
923 in your config file and
924 hint.pmtimer.0.at="isa"
925 to your /boot/device.hints file.
928 The random device has been turned into a (pseudo-)device,
929 rather than an option. The supplied kernel config files have
930 been updated. You will need to do something similar in your
931 own kernel config file.
936 If you prefer to load the loadable module, you need to do
940 The random device module has been renamed from randomdev.ko to
941 random.ko. You will need to edit your /boot/loader.conf to
942 reflect this if you load this module at boot time.
943 The line should read:
947 The SMPNG commit has happened. It should work, but if it
948 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
949 to be a variety of minor issues. Please see 20000905 to make
950 sure you don't have model loading problems which might at
951 first blush appear related to SMP.
954 nsswitch has been imported from NetBSD. Among other things,
955 this means that /etc/host.conf is no longer used. See
956 nsswitch.conf(5) instead. Note that at boot time rc.network
957 will attempt to produce a new nsswitch.conf file for you if you
958 don't have one, and you have host.conf.
961 The ucred structure changed size. This breaks the interface
962 that mountd uses. Trying to use an older mountd with a newer
963 kernel guarantees a panic. This means that you need to use
964 kernels newer than today only with matching mountd, but you
965 needed to do that anyway with the boot loader changes.
968 The boot loader has been updated. The new default kernel is
969 now /boot/kernel/kernel.ko. The new default module location
972 You *MUST* upgrade your boot loader and kernel at the same time.
973 The easiest way to do this is to do the buildworld/buildkernel/
974 installkernel/installworld dance.
976 Furthermore, you are urged to delete your old /modules directory
977 before booting the new kernel, since kldload will find stale
978 modules in that directory instead of finding them in the correct
979 path, /boot/kernel. The most common complaint that this cures
980 is that the linux module crashes your machine after the update.
982 if [ ! -d /boot/kernel.old ]; then
983 mv /modules.old /boot/kernel.old
984 chflags noschg /kernel.old
985 mv /kernel.old /boot/kernel.old/kernel.ko
986 chflags schg /boot/kernel.old/kernel.ko
990 A new issue with the sendmail upgrade has come to light.
991 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
992 incorrectly install the default aliases in /etc/mail rather than
993 move the old one from /etc. So you'll need to manually move the
994 file, create a symbolic link, remove the old /etc/aliases.db and
995 run newaliases. For safety sake, you should stop sendmail
996 while doing this and run the upgrade when locally sourced email
997 is not likely to be generated.
1000 /boot/device.hints is now required for installkernel to
1001 succeed. You should copy GENERIC.hints for your architecture
1002 into /boot/device.hints. If and only if you compile hints
1003 into your kernel, then this file may be empty. Please note,
1004 if you have an empty or missing /boot/device.hints file and
1005 you neglected to compile hints into your kernel, no boot
1006 messages will appear after the boot loader tries to start the
1010 If you do NOT have ``options RANDOMDEV'' in your kernel and
1011 you DO want the random device then add randomdev_load="YES" to
1015 suidperl is now always built and installed on the system, but
1016 with permissions of 511. If you have applications that use
1017 this program, you are now required to add ENABLE_SUIDPERL=true
1018 to /etc/make.conf. If you forget to do this,
1019 chmod 4511 /usr/bin/suidperl
1020 will fix this until the next build.
1023 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1024 visible changes that may immediately affect your configuration
1026 - New default file locations from src/contrib/sendmail/cf/README
1027 - newaliases limited to root and trusted users
1028 - MSA port (587) turned on by default
1029 - New queue file naming system so can't go from 8.11 -> 8.9
1030 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1031 - FEATURE(`nullclient') is more full featured
1032 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1033 - mail.local FreeBSD-only -b option changed to -B
1034 - See src/contrib/sendmail/RELEASE_NOTES for more info
1037 suidperl (aka sperl) is no longer build by default. You must
1038 specifically define BUILD_SUIDPERL to "true" for it to be build.
1039 Furthermore, we recommend that you remove /usr/bin/sperl* and
1040 /usr/bin/suidperl files from your system unless you have a
1041 specific use for it.
1044 Networking defaults have been tightened. Anybody upgrading
1045 /etc/defaults/rc.conf needs to add the following lines to
1046 /etc/rc.conf if they want to have the same setup
1047 afterwards (unless the variables already are set, of course):
1048 # Enable network daemons for user convenience.
1050 portmap_enable="YES"
1051 sendmail_enable="YES"
1054 If you have null_load="YES" in your /boot/loader.conf, you
1055 will need to change that to nullfs_load="YES".
1058 The "installkernel" target has changed slightly. Now even if
1059 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1060 it will install the MYKERNEL file (built with the buildkernel
1061 target) as /kernel rather than /MYKERNEL. Those who have
1062 updated their /boot/loader.conf files to point to /MYKERNEL
1063 should remove that entry or perform manual rename of /kernel
1067 If you use CVSUP or CTM to get CVS trees, AND you used to get
1068 the old crypto files from internat.freebsd.org AND you check
1069 out files from the CVS tree with the cvs command, please read
1070 http://people.freebsd.org/~imp/internat.txt
1071 for details on potential problems that you might have and how
1074 If you are merely a mirror, or don't answer yes to each of the
1075 clauses above, you needn't worry.
1078 /etc/security has been updated to print the inode number of
1079 setuid programs that have changed. You will see a large spike
1080 in the number of changed programs the first time when you run
1081 mergemaster to get a new /etc/security.
1084 /dev/random now has good entropy collection (from the keyboard
1085 and sysmouse drivers). Please ensure that either `options
1086 RANDOMDEV' is present in your kernel config file or that
1087 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1088 not have the /dev/random driver, OpenSSL (and consequently
1089 lots of crypto tools (like SSH)) will fail with strange
1090 errors. (see below, 20000624).
1092 FreeBSD-current is safe again to run Crypto.
1095 phk made the malloc default options AJ. This may slow things
1096 down and uncover other latent bugs in the code. If you need to
1097 run at full speed, you can disable this by doing the following:
1098 ln -s aj /etc/malloc.conf
1101 libftpio's version was accidentally bumped a few days ago. This
1102 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1103 before doing your next buildworld/installworld pair. It certainly
1104 won't hurt to remove it before the update procedure. It will
1105 break fetch until a new one is built, but ftp can be used in the
1109 The crypto packages have changed for the cvsup. This has been done
1110 in a backward compatible way, but the old packages will go away at
1111 some point in the future. Look at /usr/share/examples/cvsup for
1115 With the new sys/modules/sound/drivers/*, you will need to
1116 set SYSDIR until you do an installworld after July 7th.
1119 rc.shutdown and rc will now call the rc.d scripts with start
1120 or stop. This may cause some harmless warnings from older
1121 rc.d scripts that haven't been updated.
1124 The libfetch based version of fetch has gone into the tree.
1125 Minor problems may result on some of the less popular sites,
1126 which should be reported to des@freebsd.org.
1129 From approximately this date forward, one must have the crypto
1130 system installed in order to build the system and kernel.
1131 While not technically strictly true, one should treat it as
1132 required and grab the crypto bits. If you are grabbing CVS
1133 trees, src-all and cvs-crypto should be treated as if they
1134 were required. You should check with the latest collections
1135 to make sure that these haven't changed.
1138 Mark Murray just committed the first parts of a cleanup of
1139 /dev/zero, et al. This is also cleaning up /dev/random.
1140 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1141 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1142 until Mark can merge in the fixes to this work in progress.
1143 openssh and openssl should not be used to generate keys from this
1144 date to the completion of the work.
1146 If you must operate at this reduced level of security, add '
1147 options RANDOMDEV' to your kernel or modload the randomdev
1148 module. You may also need to copy a new MAKEDEV to /dev and
1149 recreate the random and urandom devices.
1152 The license on the softupdates is now a standard 2 clause
1153 BSD license. You may need to remove your symbolic links
1154 that used to be required when updating.
1157 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1158 the config file update procedure.
1159 http://people.freebsd.org/~imp/config-upd.html
1160 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1161 isn't buildable. However, you can generate a LINT file:
1162 cd /sys/<ARCH>/conf && make LINT
1165 Binutils 2.10 have hit the tree, or will shortly. As soon
1166 as they do, the problem noted in 20000522 will be resolved and
1167 that workaround will no longer be required.
1170 phk removed the compatibility creation of wd devices in the
1171 ad driver. If you haven't done so already, you must update
1172 your fstab, etc to use the ad devices instead of the wd
1175 In addition, you'll need to update your boot blocks to a
1176 more modern version, if you haven't already done so. Modern
1177 here means 4.0 release or newer (although older releases
1181 Peter took an axe to config(8). Be sure that you read his mail
1182 on the topic before even thinking about updating. You will
1183 need to create a /boot/device.hints or add a hints directive
1184 to your config file to compile them in statically. The format
1185 of the config file has changed as well. Please see GENERIC or
1186 NEWCARD for examples of the new format.
1188 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1189 says that it has been fixed, assume that must use the hints mechanism
1190 in the loader if you need to use a machine with very old ISA cards
1194 A new set of binutils went into the tree today. Anybody
1195 building a kernel after this point is advised that they need
1196 to rebuild their binutils (or better yet do a
1197 buildworld/installworld) before building a new kernel.
1199 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1200 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1201 is recommended that you don't set this option until the problem
1205 The ethernet drivers were all updated to clean up the BPF handling.
1208 The problems with boot blocks on the alphas have been corrected.
1209 This will require some care in updating alphas. A new libstand
1210 is requires for the boot blocks to build properly.
1213 Recompile all kld modules. Proper version dependency info
1217 Modules have been disconnected from the buildworld tree and
1218 connected to the kernel building instead.
1221 You may need to build gperf
1222 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1223 when upgrading from 4.0 -> current. The build system now uses
1224 an option only in -current.
1227 The method that we brand ELF binaries has changed to be more
1228 acceptable to the binutils maintainers. You will need to
1229 rebrand your ELF binaries that aren't native. One problem
1230 binary is the Linux ldconfig. After your make world, but
1231 before you reboot, you'll need to issue:
1232 brandelf -t Linux /compat/linux/sbin/ldconfig
1233 if you have Linux compatibility enabled on your machine.
1236 If you have really bad/marginal IDE drives, you may find they
1237 don't work well. Use pio mode instead. The easiest way to
1238 cope if you have a problem combination is to add:
1239 /sbin/sysctl hw.ata.ata_dma=0
1240 to the start of /etc/rc.conf.
1243 The ISA and PCI compatibility shims have been connected to the
1244 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1245 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1246 include the appropriate option in your kernel config. Drivers
1247 using the shims should be updated or they won't ship with
1248 5.0-RELEASE, targeted for 2001.
1251 We've entered the traditional post release dumping party.
1252 Large kernel changes are being committed and are in the
1253 works. It is important to keep the systems' klds and kernel
1254 in sync as kernel interfaces and structures are changing.
1255 Before reporting kernel panics, make sure that all modules
1256 that you are loading are up to date.
1259 If you are upgrading from an older version of FreeBSD, you
1260 need to update your boot blocks as well. 'disklabel -B ad0'
1261 will do the trick. This isn't critical until you remove your
1262 wd device entries in /dev, at which point your system will not
1266 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1267 to upgrade to 4.0 from 3.x.
1273 Avoid using make -j when upgrading. From time to time in the
1274 past there have been problems using -j with buildworld and/or
1275 installworld. This is especially true when upgrading between
1276 "distant" versions (eg one that cross a major release boundary
1277 or several minor releases, or when several months have passed
1278 on the -current branch).
1280 Sometimes, obscure build problems are the result of environment
1281 poisoning. This can happen because the make utility reads its
1282 environment when searching for values for global variables.
1283 To run your build attempts in an "environmental clean room",
1284 prefix all make commands with 'env -i '. See the env(1) manual
1285 page for more details.
1289 If you are updating from a prior version of FreeBSD (even one just
1290 a few days old), you should follow this procedure. With a
1291 /usr/obj tree with a fresh buildworld,
1292 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1293 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1295 To just build a kernel when you know that it won't mess you up
1296 --------------------------------------------------------------
1297 cd src/sys/{i386,alpha}/conf
1298 config KERNEL_NAME_HERE
1299 cd ../../compile/KERNEL_NAME_HERE
1304 If this fails, go to the "To build a kernel" section.
1306 To rebuild everything and install it on the current system.
1307 -----------------------------------------------------------
1308 # Note: sometimes if you are running current you gotta do more than
1309 # is listed here if you are upgrading from a really old current.
1311 <make sure you have good level 0 dumps>
1312 <maybe fix /etc/fstab> [7]
1314 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1315 make installkernel KERNCONF=YOUR_KERNEL_HERE
1317 <reboot in single user> [3]
1324 To cross-install current onto a separate partition
1325 --------------------------------------------------
1326 # In this approach we use a separate partition to hold
1327 # current's root, 'usr', and 'var' directories. A partition
1328 # holding "/", "/usr" and "/var" should be about 2GB in
1331 <make sure you have good level 0 dumps>
1334 <maybe newfs current's root partition>
1335 <mount current's root partition on directory ${CURRENT_ROOT}>
1336 make installworld DESTDIR=${CURRENT_ROOT}
1337 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1338 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1339 ${CURRENT_ROOT}/boot/device.hints # as needed
1340 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1341 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1342 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1343 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1344 <reboot into current>
1345 <do a "native" rebuild/install as described in the previous section>
1346 <maybe install compatibility libraries from /usr/src/lib/compat>
1350 To upgrade in-place from 4.x-stable to current
1351 ----------------------------------------------
1352 # 5.x uses more space than 4.x. Also, the location of kernel
1353 # modules has changed. If you are installing 5.0 onto a 4.x
1354 # system, you'll need about 30MB of free disk space on your /
1355 # partition. If you have less than this, you may encounter difficult
1356 # to back out of problems with this procedure. If /tmp is on
1357 # the / partition, you may want to completely remove all its content
1358 # before upgrading, as this can be a common source of shortage of
1361 <make sure you have good level 0 dumps>
1362 <maybe fix /etc/fstab> [7]
1364 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1365 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1366 make installkernel KERNCONF=YOUR_KERNEL_HERE
1367 cd src/sys/boot ; make install [6]
1369 <reboot in single user> [3]
1371 rm -rf /usr/include/g++
1376 Make sure that you've read the UPDATING file to understand the
1377 tweaks to various things you need. At this point in the life
1378 cycle of current, things change often and you are on your own
1379 to cope. The defaults can also change, so please read ALL of
1380 the UPDATING entries.
1382 Also, if you are tracking -current, you must be subscribed to
1383 freebsd-current@freebsd.org. Make sure that before you update
1384 your sources that you have read and understood all the recent
1385 messages there. If in doubt, please track -stable which has
1386 much fewer pitfalls.
1388 [1] If you have third party modules, such as vmware, you
1389 should disable them at this point so they don't crash your
1392 [2] If you have legacy ISA devices, you may need to create
1393 your own device.hints to reflect your unique hardware
1396 [3] From the bootblocks, boot -s, and then do
1401 adjkerntz -i # if CMOS is wall time
1402 Also, when doing a major release upgrade, it is required that
1403 you boot into single user mode to do the installworld.
1404 For the 4.x -> 5.0 upgrade, you will also see many messages about
1405 needing to recompile your userland. These are harmless and can
1406 be ignored while you proceed to the next step.
1408 [4] Note: This step is non-optional. Failure to do this step
1409 can result in a significant reduction in the functionality of the
1410 system. Attempting to do it by hand is not recommended and those
1411 that pursue this avenue should read this file carefully, as well
1412 as the archives of freebsd-current and freebsd-hackers mailing lists
1413 for potential gotchas.
1415 [5] Usually this step is a noop. However, from time to time
1416 you may need to do this if you get unknown user in the following
1417 step. It never hurts to do it all the time. You may need to
1418 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1419 install) after the buildworld before this step if you last updated
1420 from current before 20020224 or from -stable before 20020408.
1422 [6] 4.x boot loader can be used to boot a 5.x system, however
1423 it is difficult to do that at best. If you wish to try, then
1424 you should interrupt the boot and at the ok prompt type:
1426 ok boot /boot/kernel/kernel
1427 If this fails to work, you must install a new boot loader as
1430 [7] Before you upgrade, please make sure that you are not using
1431 compatibility slices. These are device names of the form, on i386
1432 and other architectures that use MBR slicing, /dev/ad0a without the
1433 actual slice name. Chances are excellent that these will break.
1434 You generally must update these entries to use the post FreeBSD
1435 2.x form of /dev/ad0s1a.
1437 [8] In order to have a kernel that can run the 4.x binaries
1438 needed to do an installworld, you must include the COMPAT_FREEBSD4
1439 option in your kernel. Failure to do so may leave you with a system
1440 that is hard to boot to recover.
1442 [9] When checking out sources, you must include the -P flag to have
1443 cvs prune empty directories.
1446 This file contains a list, in reverse chronological order, of major
1447 breakages in tracking -current. Not all things will be listed here,
1448 and it only starts on March 15, 2000. Updating files can found in
1449 previous releases if your system is older than this.
1451 Copyright information:
1453 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1455 Redistribution, publication, translation and use, with or without
1456 modification, in full or in part, in any form or format of this
1457 document are permitted without further permission from the author.
1459 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1460 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1461 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1462 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1463 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1464 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1465 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1466 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1467 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1468 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1469 POSSIBILITY OF SUCH DAMAGE.
1471 If you find this document useful, and you want to, you may buy the
1474 Contact Warner Losh if you have any questions about your use of