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