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 Some sshd configuration defaults have changed: protocol version 2
22 is no longer enabled by default, and password authentication is
23 disabled by default if PAM is enabled (which it is by default).
24 OpenSSH clients should not be affected by this; other clients may
25 have to be reconfigured, upgraded or replaced.
28 routed has been updated in the base system from the vendor
29 sources, routed v2.27, from rhyolite.com. This change means that
30 for users who use RIP's MD5 authentication feature, FreeBSD
31 -CURRENT's routed is now incompatible with previous versions
32 of FreeBSD; however it is now compatible with implementations
33 from Sun, Cisco and other vendors.
36 The tcpcb structure has changed and makes a recompile of libkvm
37 and related userland network utilities neccessary.
40 The cdevsw structure has changed in two externally visible ways.
41 First, the sense of the D_GIANT flag has changed to D_NEEDSGIANT.
42 Second, the d_version field must be filled in with D_VERSION.
43 Drivers outside the tree will need to be updated.
46 The /etc/rc.d/ttys script has been removed. It is no longer
47 necessary since devfs has been mandatory for some time.
50 libkse has been renamed back to libpthread and is now the
51 default threads library. The gcc -pthread option has also
52 been changed to link to libpthread instead of libc_r. For
53 alpha and sparc64 machines, libkse is not renamed and links
54 are installed so that libpthread points to libc_r. Until
55 the ports system is updated to handle this change, it is
56 recommended that folks install an /etc/libmap.conf(5) that
57 maps libc_r to libpthread. If you have any binaries or
58 libraries linked to libkse, then it is also recommended
59 that you map libkse to libpthread. Anyone that is using
60 nvidia supplied drivers and libraries should use a libmap.conf
61 that maps libpthread to libc_r since their drivers/libraries
62 do not work with libpthread.
65 ULE has entered into its probationary period as the default scheduler
66 in GENERIC. For the average user, interactivity is reported to be
67 better in many cases. On SMP machines ULE will be able to make more
68 efficient use of the available parallel resources. If you are not
69 running it now, please switch over, replacing the kernel option
70 SCHED_4BSD with SCHED_ULE.
73 Move LongRun support out of identcpu.c, where it hardly
74 belongs, into its own file and make it opt-in, not mandatory,
75 depending on CPU_ENABLE_LONGRUN config(8) option.
78 src/lib/libc/gen/initgroups.c:1.8 now causes logins to fail
79 if the login process is unable to successfully set the
80 process credentials to include all groups defined for the
81 user. The current kernel limit is 16 groups; administrators
82 may wish to check that users do not have over 16 groups
83 defined, or they will be unable to log in.
86 The ACPI module has been reactivated. It is no longer required
87 to compile ACPI support into kernels statically.
90 The statfs structure has been updated with 64-bit fields to
91 allow accurate reporting of multi-terabyte filesystem
92 sizes. You should build world, then build and boot the new kernel
93 BEFORE doing a `installworld' as the new kernel will know about
94 binaries using the old statfs structure, but an old kernel will
95 not know about the new system calls that support the new statfs
97 Note that the backwards compatibility is only present when the
98 kernel is configured with the COMPAT_FREEBSD4 option. Since
99 even /bin/sh will not run with a new kernel without said option
100 you're pretty much dead in the water without it. Make sure you
101 have COMPAT_FREEBSD4!
102 Running an old kernel after a `make world' will cause programs
103 such as `df' that do a statfs system call to fail with a bad
104 system call. Marco Wertejuk <wertejuk@mwcis.com> also reports
105 that cfsd (ports/security/cfs) needs to be recompiled after
106 these changes are installed.
108 ****************************DANGER*******************************
110 DO NOT make installworld after the buildworld w/o building and
111 installing a new kernel FIRST. You will be unable to build a
112 new kernel otherwise on a system with new binaries and an old
116 Some netgraph string length constants have been changed. This
117 change requires the netgraph kernel modules and all netgraph
118 userland components to be in sync. Especially users who require
119 netgraph to boot need to make sure to have world and kernel in
120 sync before rebooting.
123 Hyperthreading logical CPU's are no longer probed by default
124 when using the MP Table. If ACPI is being used, then logical
125 CPUs will be probed if hyperthreading is enabled in the BIOS.
126 If ACPI is not being used and hyperthreading is enabled in the
127 BIOS, logical CPUs can be enabled by building a custom kernel
128 with the option MPTABLE_FORCE_HTT enabled.
131 The i386 APIC_IO kernel option has been replaced by
132 'device apic'. The ACPI module has also been temporarily
133 disabled, so ACPI must be statically compiled into your
134 kernel using 'device acpi' if you wish to use the ACPI driver.
137 The API and ABI of struct ifnet have been changed by removing
138 the if_name and if_unit members and replacing them with
139 if_xname, if_dname, and if_dunit. All network drivers and most
140 userland programs which include net/if_var.h must be updated
141 and recompiled. __FreeBSD_version has been bumped to 501113 to
145 Changes to the cdevsw default functions have been made to remove
146 the need to specify nullopen() and nullclose() explicitly.
147 __FreeBSD_version bumpted to 501110.
150 kiconv(3) has been added. mount_msdosfs(8), mount_ntfs(8) and
151 mount_cd9660(8) need to be in sync with kernel.
154 Configuring a system to use IPFILTER now requires that PFIL_HOOKS
155 also be explicitly configured. Previously this dependency was
156 magically handled through some cruft in net/pfil.h; but that has
157 been removed. Building a kernel with IPFILTER but not PFIL_HOOKS
158 will fail with obtuse errors in ip_fil.c.
161 Fix a bug in arplookup(), whereby a hostile party on a locally
162 attached network could exhaust kernel memory, and cause a system
163 panic, by sending a flood of spoofed ARP requests. See
164 FreeBSD-SA-03:14.arp.
167 A change to /etc/defaults/rc.conf now causes inetd to be started
168 with `-C 60' if it is not overridden in /etc/rc.conf. This
169 causes inetd to stop accepting connections from an IP address
170 that exceeds the rate of 60 connections per minute.
173 The following rc.d scripts have been removed and should be
174 deleted from your installation: atm2.sh atm3.sh devdb
175 localdaemons network1 network2 network3. Depending on when
176 you last updated world and used mergemaster(8) you may or
177 may not have problems during the rc boot sequence. The simplest
178 solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'.
179 The atm2.sh atm3.sh and devdb scripts were removed some time
180 ago, so depending on when you installed -CURRENT these scripts
181 may or may not exist on your system.
184 ATAng has been committed. You need to build world as sys/ata.h
185 has changed, and userland atacontrol depends on it.
186 If you use ATA SW raids you need "device ataraid" in your
187 kernel config file, as it is no longer pulled in automatically.
190 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
191 Among other things, this changes the device enumeration to be
192 closer to Solaris. Be aware that, this can even cause the machine
193 to not boot without manual intervention before the fstab is adjusted.
196 All current USB and Firewire quirks in da(4) have been deprecated
197 and will be removed for 5.2. If this causes failure for your
198 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
199 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
200 so the quirk can be re-enabled.
203 Problems with entry 20030714 have been corrected and no known issues
204 with /rescue and -j exist for host systems after this point in time.
207 FPU-less support has been removed from FreeBSD. Chances are you won't
208 notice. 386+387 support should still work after this change, but
209 it is now a minimum requirement for the i386 port that you have real
213 Some people are having problems with changes related to /rescue.
214 If you are building -j N, you will need to define NO_RESCUE. Others
215 will need to define it if /rescue has issues with their environment.
216 People should report those issues to current@.
219 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
220 across this point. Further, it might be a good idea to remove
224 Remove deprecated locale names and transition period code
225 for them, finishing switching to the new scheme. Check your
226 LANG environment variable.
229 CCD has been changed to be a fully GEOMified class. Kernel
230 and ccdconfig(8) needs to be in sync, this is particularly
231 important to remember beforehand if your source tree is on
232 a ccd device. Consider making a copy of the old ccdconfig
233 into /boot/kernel.good or wherever you keep your backup
237 There was a small window in which sed(1) was broken. If you
238 happen to have sed(1) installed during that window, which is
239 evidenced by an inability to build world with the failure
240 given below, you need to manually build and install sed(1)
241 (and only sed(1)) before doing anything else. This is a one-
242 time snafu. Typical failure mode:
244 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
245 targmatch.h:7:1: null character(s) ignored
246 targmatch.h:12:1: null character(s) ignored
247 targmatch.h:16:1: null character(s) ignored
250 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
251 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
252 usr.bin/sed/process.c).
255 Kerberos 5 (Heimdal) is now built by default. Setting
256 MAKE_KERBEROS5 no longer has any effect. If you do NOT
257 want the "base" Kerberos 5, you need to set NO_KERBEROS.
260 groff has been updated. If you try to do a buildworld and
261 get an infinite loop in troff, update to May 4th or newer. If you
262 have a newer kernel than userland, you may need to set the OSRELDATE
263 to 500110 in your environment before starting a buildworld.
266 The old rc system has been removed. Please report any problems
267 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
268 Your personal versions of these files will not be removed, so you can
269 continue to use them. However, you should take great care when updating,
270 especially when using mergemaster, since the compatibility code that
271 utilizes these old scripts has also been removed.
274 A bug has been fixed in /dev/devctl which would cause devd
275 to hang on boot, were it not for a workaround in devd. The
276 work around in devd will be removed around 20030507. You
277 have until then to upgrade your kernel before updating
278 userland. In general, you should have a userland and
279 kernel that's in sync with each other. However, given the
280 effects of this bug (hang on boot when starting devd), some
284 Alphas with libc from between 20030312 and 20030329 exhibit
285 floating point exceptions (FPEs), most notably in awk(1)
286 while upgrading the system through a buildworld.
288 So, to successfully upgrade your Alpha, you must either
289 downgrade your libc.so to a pre-20030312 version, or update
290 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
291 to CFLAGS, then forcibly rebuild and install libc:
293 cd /usr/src/lib/libc && \
294 make cleandir && make obj && \
295 make -DNOMAN -DNOPROFILE all && \
296 make -DNOMAN -DNOPROFILE install
299 sendmail 8.12.7 has been imported. It has one important
300 change for IPv6 users. The default submit.mc now uses
301 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
302 used to connect to the MTA. Users on IPv6-only machines
303 will need to edit /etc/mail/submit.mc appropriately.
306 NODEVFS option has been removed and DEVFS thereby made standard.
307 This makes all references to MAKEDEV obsolete, and they should
308 be removed when convenient.
311 The name of the device for the ofw console has changed, sparc64 users
312 must run mergemaster to update their installed /etc/ttys.
315 The scheduler framework has grown a second scheduler and consequently
316 you must specify one and only one scheduler in your kernel config.
317 The cvs config files have been updated to use the old scheduler
318 which may be selected via 'options SCHED_4BSD'. If you would like
319 to try the new, much more experimental, scheduler please try
320 'options SCHED_ULE' and contribute to the arch@ discussion.
323 A new version of the wi driver has been imported into the tree.
324 One now must have device wlan in the config file for it to operate
327 In addition, there have been some changes to how wi devices are
328 configured for point to point links to bring it more in line
329 with the former way of doing things, as well as compatibility
333 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
334 used an incompatible form of ABI for returning structures and unions
335 which FreeBSD's GCC maintainers were not aware of relative to previous
336 versions of FreeBSD. We have gone back to the ABI for now, and any
337 code compiled which is required to interoperate with other code (not
338 built at the same time) returning structs or unions should be
342 A name change in /etc/netconfig has been reverted to stay
343 compatible with suns TIRPC and also with NetBSD. You need
344 to run mergemaster after make world. A new libc does still work
345 with an outdated /etc/netconfig for some time, but you'll get
346 a warning. This warning will be removed in 20030301.
349 The recent binutils upgrade marks a kernel flag day on
350 sparc64: modules built with the old binutils will not work
351 with new kernels and vice versa. Mismatches will result in
352 panics. Make sure your kernel and modules are in sync.
355 The value of IPPROTO_DIVERT has changed. Make sure to keep
356 your kernel, netstat, natd and any third-party DIVERT
360 Old, compatibility slices have been removed in GEOM kernels.
361 This means that you will have to update your /etc/fstab to
362 not use disk devices of the form /dev/ad0a. Instead, you
363 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
364 partition really is on. The old device names have gone
365 away, so if you use them anywhere else, you must also adjust
366 those uses. (This doesn't affect the disks formatted in
367 the ``dangerously-dedicated'' mode.)
370 Alphas with kernels from between 20020830 and 20021023 and/or
371 rtld (ld-elf.so.1) older than 20021023 may experience problems
372 with groff while doing a buildworld (kernel: "out of memory",
373 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
374 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
376 So, to successfully upgrade your Alpha, you must either
377 upgrade your kernel and rtld first (which might be a bit
378 tricky), or avoid running the bootstrapped groff during the
379 "transitional" buildworld. To avoid running groff during the
380 transitional upgrade run make buildworld with -DNOMAN,
381 -DNO_SHAREDOCS, and -DNO_LPR.
384 gcc has been upgraded to 3.2. It is not all binary compatible
385 with earlier versions of gcc for c++ programs. All c++
386 programs and libraries need to be recompiled.
388 Also, if you encounter g++ issues, rm /usr/include/g++/* before
389 doing an installworld to make sure that stale files are removed.
392 Our /etc/termcap now has all the entries from the XFree86 xterm
393 almost unchanged. This means xterm now supports color by default.
394 If you used TERM=xterm-color in the past you now should use
395 TERM=xterm. (xterm-color will lead to benign warnings).
398 A "bug" in gcc(1) that was hiding warning in system headers was
399 fixed. It's probably time to add -DNO_WERROR to your make line
403 COPY is being deprecated. The 20010530 change was reverted, as
404 it causes far more pain than was expected, and to always compare
405 before installing, please use INSTALL="install -C" again. The
406 -C option is now silently ignored when used with the -d option.
409 Problems with libc_r clients like KDE and GNOME have been resolved.
410 There are still some minor problems with some signals but the
411 system is stable enough for general use again. SMP is less so than UP
412 but each can successfully complete multiple buildworlds.
413 Libkvm needs to be recompiled due to KSE.
416 Now would be a bad time to upgrade. Something in or near the
417 KSE commit totally broke programs using libc_r like KDE and
421 The k5su utility installed as part of Kerberos 5 is no longer
422 installed with the set-user-ID bit set by default. Add
423 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
424 with the set-user-ID bit set.
427 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
428 Unfortunately our native GDB (at version 4.18) does not understand
429 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
430 generated debugging information for our native GDB.
433 Due to the way CVS works, it may not properly update src/contrib/gcc
434 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
435 and then do a cvs update.
438 When exec'ing set[ug]id executables, the kernel now ensures that the
439 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
442 New sendmail startup scripts have been installed to make it
443 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
444 variable sendmail_enable to "NO" no longer prevents any sendmail
445 daemons from starting. Instead, either set sendmail_enable to
446 "NONE" or change mta_start_script to a script for starting
447 an alternative MTA. Setting mta_start_script to "" will
448 also prevent any MTA from being started at boot.
451 UCONSOLE is no longer a valid kernel option.
454 FreeBSD 5.0 DP-1 was basically branched today.
457 Warnings are now errors in the kernel. Unless you are a developer,
458 you should add -DNO_WERROR to your make line.
461 sendmail 8.12.2 has been imported. The sendmail binary is no
462 longer a set-user-ID root binary and the infrastructure to support
463 command line mail submission has changed. Be sure to run
464 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
465 and /etc/mail) and read /etc/mail/README for more details.
467 Due to the import of sendmail 8.12.2, a new user and group are
468 required in order for sendmail to run as a set-group-ID
469 binary. A 'make installworld' will use the new user and group
470 to set the owner and group of /var/spool/clientmqueue and will
471 fail if the new user and group do not exist. The 'smmsp' user
472 and group must be merged from src/etc/group and
473 src/etc/master.passwd before using 'make installworld'.
474 'mergemaster -p' will do this. You may need to install
475 mergemaster before this will work if you are updating from a
476 very old version of current. The updating recipe has changed
480 The preferred configuration method for PAM is now /etc/pam.d/
481 rather than /etc/pam.conf. If you have an unmodified
482 pam.conf, just delete it after your next mergemaster run. If
483 you have local modifications, you can use
484 /usr/src/etc/pam.d/convert.pl to incorporate them into your
487 Please see the following url for more details:
488 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
490 If anyone here is already using the new rc.conf(5) variable
491 networkfs_types, please note that it has changed
492 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
495 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
496 started out its life in the ISDN4BSD project as an offspring
497 from sys/net/if_spppsubr.c, which eventually got a life of its
498 own. All the accumulated features and bugfixes of the i4b
499 version have now been merged back into the base system's
500 version now. The only user-visible change resulting from this
501 is that i4b's sppp(4) interfaces are to be managed with
502 spppcontrol(8) again, since ispppcontrol(8) has been retired
503 as well. (There has never been rc file support for
504 ispppcontrol in -current, but only in -stable. That will be
505 reverted by the time the changes are MFCed.)
508 The fdc(4) driver has been updated and now automatically
509 recognizes media in `standard' formats (like 1440 KB and
510 720 KB for a 3.5" high-density drive) when accessing the
511 default device node (e. g. /dev/fd0). The old variety of
512 floppy device nodes /dev/fd*.* is no longer present by
513 default, devices can be created (in DEVFS) on demand. They
514 will need to be customized then for `odd' densities using
518 The bugs in procfs' debugging support code have been fixed,
519 and truss(1) now works again.
522 Daily security checks have been split out to use the periodic(8)
523 scripts. Some change in configuration may be necessary. Please
525 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
529 sos added VCD/SVCD support to ata driver and that needs the
530 kernel and burncd to be in sync.
533 The procfs pseudo-filesystem has now been converted to use the
534 pseudofs framework. If you have 'options PROCFS' in your
535 kernel config, you'll need to add 'options PSEUDOFS' if it's
538 This change temporarily breaks truss(1); use ktrace(1) instead
539 until the issue has been resolved.
542 A security hole in OpenSSH involving `UseLogin yes' has been
546 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
547 after this date. You need to do this only once.
550 Most of the awk issues have been resolved. Some rough
551 edges may be left, but for the most part things should be
552 back to "normal." For CURRENT's usual definition of "normal."
555 Awk has been upgraded to the one true awk from bell labs. Expect
556 choppy waves in the upgrade process.
559 The asr driver problem has been resolved.
562 Due to changes in other parts of the system, the asr driver
563 now causes the system to panic on boot. Do not use it pending
564 correction. Comment it out of any kernel config file that you
565 try to use from this date forward.
568 When crossbuilding, use TARGET=xxx where you used to use
569 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
570 unless you are changing both of them. To cross build pc98 on
571 an alpha, for example, you need to set TARGET=pc98 and
575 The kernel interface that burncd depends on has changed.
576 You must recompile both the kernel and userland applications
580 When crossbuilding, please set TARGET_ARCH rather than
581 MACHINE_ARCH to indicate the target. In the future, one will
582 set TARGET_MACHINE where you set MACHINE now. At the moment,
583 setting MACHINE alone for same MACHINE_ARCH machines works
584 (eg, you can build pc98 on an i386 machine and vice versa).
587 Some weird problems result from using ACPI on some machines.
588 To disable ACPI you can add
589 hint.acpi.0.disabled="1"
590 to /boot/loader.conf (or by putting set X=Y at the boot
593 Alternatively, you can remove it from /boot/kernel/acpi.ko
594 or use the MODULES_OVERRIDE function in your kernel config
595 file and not list acpi in that list.
598 The buildworld has been fixed. You may need to install
599 the 4.x compatibility libraries for some old binaries
600 to work. Add COMPAT4X=true to your /etc/make.conf to
601 get them installed on every installworld, or execute the
602 following to get them installed only once:
603 cd src/lib/compat/compat4x.<arch>
605 You will see ``__stdoutp undefined'' until you do this.
608 There's a bug in the world build process. The cross-tools
609 are build with the NEW headers, but the OLD libc.a. This
610 leads to all kinds of problems with the new libc. A temporary
612 CFLAGS="-O -pipe -D_OLD_STDIO"
613 before building world when upgrading from 4.x to current. This
614 can be removed afterwards.
616 A proper fix to the buildworld target is needed.
619 Peter has committed his new kthread nfs client/server code.
620 NFS may be unstable after this date.
623 KSE has hit the tree. Lots of things are now different in
624 the kernel. While a few problems were introduced in the
625 initial commit, most of the major ones have been found and
629 In OLDCARD, CardBus bridges appear to be stable. The work
630 arounds described in the 20010604 entry are now no longer
631 necessary and will be ignored. Most insert/remove problems
632 have been rectified around this date.
635 named now runs as user bind and group bind rather than as
636 root. If named_enable is set to YES in /etc/rc.conf, ensure
637 that user bind is available in /etc/passwd (using vipw(8))
638 and that group bind is available in /etc/group. Also make
639 sure that user or group bind has read (and not write)
640 permission for your name server configuration and that it
641 has read and write permission for your slave zone files and
644 If you wish to continue to run named as root (a less secure
645 alternative), add a line to /etc/rc.conf saying
650 The PAM libraries have had an API upgrade that is beyond
651 the ability of the shared library major number to handle.
652 It is manifested by PAM-using ports dumping core. The
653 solution is to rebuild those ports.
656 The kernel compile module has moved from src/sys/compile/FOO
657 to src/sys/${MACHINE}/compile/FOO.
660 The pccard modem issue from 20010613 has been corrected.
661 OLDCARD support is still a little weak in -current. slot 1 is
662 known not to work on some TI based cardbus bridges. Some
663 cardbus bridges do not properly detect insert/removal events.
664 IRQ configuration needs more safety belts.
667 Softupdates problems have been corrected.
670 Peter ripped out the linkerset support. You must, as always,
671 rerun config after you cvsup if you are using the traditional
672 kernel building methods.
675 pccard modems may not work with current after 20010604 date. Some
676 do, others result in panics. *MAKE*SURE* that you update your
677 config and /etc/rc.conf ala the 20010604 entry, or you will have
678 problems (this issue will be fixed, it just hasn't been yet).
681 SOFTUPDATES seem to be broken since the middle of May or so. Do not
682 use them in current. You can disable softupdates on all mounted
683 partitions, or remove SOFTUPDATES the kernel config file.
686 After Peter's commits to the hints code, people have been noticing
687 that certain devices are attached (or try to) twice. This is due
688 to having both static hints as well as a /boot/device.hints. To
689 work around this issue, please use only one or the other mechanism
690 until this bug is fixed.
692 Please note that a feature of config is that if you have config
693 file FOO and FOO.hints, it automatically adds FOO.hints to the
694 hints.c file, whether you want it to or not.
697 Locale names have changed to match other systems better.
700 pccard support for pci cards has been committed. You must change
701 your /etc/pccard.conf irq lines. It must match the irq used by
702 pcic device. Interrupt storms may result if you fail to do this.
703 Interrupt storms look a lot like a hang.
705 You must also install a new pccardd, otherwise you will get an
706 interrupt storm at card reset time (just after it tells you what
709 pccardd_flags="-I" is necessary for the time being. It tells pccardd
710 not to ask the kernel if the interrupt is really free or not before
711 using it. You can either change the /etc/pccard.conf irq lines to
712 match pcic, or add "-i X" to the pccardd_flags.
715 INSTALL=install -C is being deprecated. If you want to do this,
716 use COPY=-C instead. The former method will be supported for only
717 a limited time. If you see
719 install: warning: the -d and -C options may not be specified together
721 in your makeworld, then you need to migrate towards using
725 It appears that vm is now stable enough to use again. However,
726 there may be other problems, so caution is still urged. alpha
727 definitely is in bad shape.
730 Minor repo damage has happened. This may cause problems
731 with cvsup of ports. If you get errors, please see
732 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
733 at the bottom for details on a workaround. The error message
735 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
738 Vm and/or swapping are busted on -current. Please be patient.
741 pccard has had much reorganizational work done to it over
742 the past few days. Everything should still work, but if
743 not, please contact imp@freebsd.org.
746 ata ioctl changed. Make sure to recompile both kernel and
747 userland at the same time.
750 New ncurses imported.
753 DEVFS is now opt out, not opt in. Barring major problems, this
754 will be the only way to go starting July 1.
757 OpenSSH has been updated to 2.9. Some defaults are different,
758 including RhostsRSAAuthentication, which changes from yes to no.
761 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
764 Building perl was broken at 02:25:25 PDT.
767 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
768 go back in the water.
771 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
772 this date, but before the correction date.
775 old fsck and new kernel interactions appear to have been fixed.
778 fsck and the kernel were changed to handle some optimizations
779 to directory layout. This breaks backward compatibility.
780 Update only if you understand that you must not use the old
781 fsck with the new kernel ever.
784 fsck has changed the meaning of the pass column in /etc/fstab.
785 Please see the cvs commit to fsck.8 or the fsck.8 man page for
786 details. It is unclear if changes to /etc/fstab are necessary.
789 portmap had changed name to rpcbind for maximum POLA in your
790 current world. /etc/hosts.{allow,deny} needs changes. nfs and
791 other rpc based programs that rely on portmapper will not work
792 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
795 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
796 and ATA_ENABLE_TAGS are no longer kernel options. They have
797 been replaced by tunables. See ata.4 for details.
800 The fxp driver was converted to use miibus. If you compile
801 fxp into your kernel statically, you will need to add miibus.
804 The wi device now defaults to BSS (infrastructure) mode
808 /dev/urandom should be a symbolic link to /dev/random now.
809 Users of current not using DEVFS need to run MAKEDEV std.
810 ssh might not work if you don't.
813 The ed driver has been updated. It now allows mii attachments,
814 which means that you must include the miibus in your kernel if
815 you use the ed driver.
818 The problems with libc have been corrected. It is now mostly
819 safe to go back into the water.
822 The size of FILE was changed. This breaks upgrading. If
823 you must upgrade, be prepared for pain. It also breaks almost
824 all binaries that you've compiled on -current. You are warned
825 that before upgrading would be a good time to do a level 0
826 dump of your system. No, really, I mean it this time.
828 To get to the new system, you'll need to use the following
829 workaround. Hopefully this can be sorted out so that we
830 don't have to move this to the updating section.
832 To get around the installworld problem, do:
833 # cd /usr/src/usr.bin/sed
837 If that doesn't work, then try:
838 # make -k installworld
842 DEVFS is now the default. If you use vinum, make sure that you
843 do not include devfs in your kernel as problems result.
846 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
847 Remove them from your config.
850 ****************************** WARNING ******************************
851 buildkernel has been changed slightly
852 ****************************** WARNING ******************************
853 KERNCONF replaces the variable KERNEL for buildkernel. You
854 should update your scripts and make.conf accordingly.
857 config has changed to allow DEV_FOO as a replacement for NFOO.
858 This requires a new config to build correctly.
861 The kernel option I386_CPU is now mutually exclusive with the
862 other cpu types. If you have an i386 system, be sure that it
863 only had this line. Remove it for all other configurations.
866 Changes to the kernel require it and burncd be in sync.
869 Everyone who has hw.sndunit set to something in
870 /etc/sysctl.conf, it is now hw.snd.unit.
873 ex and vi were broken by some changes to sys/queue.h. If you
874 have a bad vi, you will see make buildworld fail with a core
875 dump while building termcap. You can work around this problem
876 by adding -k to your make buildworld. This will cause the
877 build to complete and install a new vi. Once that's done, you
878 can rebuild again without the -k to pick up anything that
879 might have been ignored by the -k option.
881 Others have suggested that you can just rebuild libc if your
882 vi/ex is dynamically linked, but I've not received any reports
886 There have been some changes to libcrypt in -current. The
887 libscrypt/libdescrypt symlink silliness is gone and the installed
888 libcrypt is fully functional. Be aware of this.
891 Linksys Fast Ethernet PCCARD cards supported by the ed driver
892 now require the addition of flag 0x80000 to their config line
893 in pccard.conf(5). This flag is not optional. These Linksys
894 cards will not be recognized without it.
897 Important new FreeBSD-version stuff: PAM support has been worked
898 in, partially from the "Unix" OpenSSH version. This requires
899 adding the following in pam.conf:
901 sshd auth sufficient pam_skey.so
902 sshd auth required pam_unix.so try_first_pass
903 sshd session required pam_permit.so
909 The random device needs more entropy, so you need to make sure
910 that you've run mergemaster to get a /etc/rc which will seed
911 /dev/random. If you don't and the system hangs after ldconfig,
912 then banging on the keyboard randomly until it unhangs is one
916 ****************************** WARNING ******************************
917 Sendmail has been updated.
918 ****************************** WARNING ******************************
919 o mail.local(8) is no longer installed as a set-user-id binary.
920 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
922 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
924 o Now using sendmail's version of vacation(1).
925 o The sendmail cf building tools (contrib/sendmail/cf) are installed
926 in /usr/share/sendmail/cf.
927 o sendmail.cw changed to local-host-names
929 More details can be found at
930 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
933 The ports tree's new layout is in place. Be sure to update
934 your entire ports tree, or you will have problems.
937 The perl build procedure no longer installs miniperl, nor uses
938 the installed miniperl. It is recommended that you delete
942 This weekend the ports tree will be updated to a new layout.
943 It will be in an inconsistent state until noted in the UPDATING
944 file, or with asami-san's message to the relevant mailing
945 lists. With this new layout, you'll need to update the whole
946 tree for anything to work.
949 There was a change in the passwd format. Need more information.
952 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
953 place. Please update boot loader (not the boot blocks) at the
954 same time as your kernel.
957 The new pmtimer device is necessary for laptops. Failure to
958 include the device will cause suspended laptops losing time
959 when they resume. Include
961 in your config file and
962 hint.pmtimer.0.at="isa"
963 to your /boot/device.hints file.
966 The random device has been turned into a (pseudo-)device,
967 rather than an option. The supplied kernel config files have
968 been updated. You will need to do something similar in your
969 own kernel config file.
974 If you prefer to load the loadable module, you need to do
978 The random device module has been renamed from randomdev.ko to
979 random.ko. You will need to edit your /boot/loader.conf to
980 reflect this if you load this module at boot time.
981 The line should read:
985 The SMPNG commit has happened. It should work, but if it
986 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
987 to be a variety of minor issues. Please see 20000905 to make
988 sure you don't have model loading problems which might at
989 first blush appear related to SMP.
992 nsswitch has been imported from NetBSD. Among other things,
993 this means that /etc/host.conf is no longer used. See
994 nsswitch.conf(5) instead. Note that at boot time rc.network
995 will attempt to produce a new nsswitch.conf file for you if you
996 don't have one, and you have host.conf.
999 The ucred structure changed size. This breaks the interface
1000 that mountd uses. Trying to use an older mountd with a newer
1001 kernel guarantees a panic. This means that you need to use
1002 kernels newer than today only with matching mountd, but you
1003 needed to do that anyway with the boot loader changes.
1006 The boot loader has been updated. The new default kernel is
1007 now /boot/kernel/kernel.ko. The new default module location
1010 You *MUST* upgrade your boot loader and kernel at the same time.
1011 The easiest way to do this is to do the buildworld/buildkernel/
1012 installkernel/installworld dance.
1014 Furthermore, you are urged to delete your old /modules directory
1015 before booting the new kernel, since kldload will find stale
1016 modules in that directory instead of finding them in the correct
1017 path, /boot/kernel. The most common complaint that this cures
1018 is that the linux module crashes your machine after the update.
1020 if [ ! -d /boot/kernel.old ]; then
1021 mv /modules.old /boot/kernel.old
1022 chflags noschg /kernel.old
1023 mv /kernel.old /boot/kernel.old/kernel.ko
1024 chflags schg /boot/kernel.old/kernel.ko
1028 A new issue with the sendmail upgrade has come to light.
1029 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
1030 incorrectly install the default aliases in /etc/mail rather than
1031 move the old one from /etc. So you'll need to manually move the
1032 file, create a symbolic link, remove the old /etc/aliases.db and
1033 run newaliases. For safety sake, you should stop sendmail
1034 while doing this and run the upgrade when locally sourced email
1035 is not likely to be generated.
1038 /boot/device.hints is now required for installkernel to
1039 succeed. You should copy GENERIC.hints for your architecture
1040 into /boot/device.hints. If and only if you compile hints
1041 into your kernel, then this file may be empty. Please note,
1042 if you have an empty or missing /boot/device.hints file and
1043 you neglected to compile hints into your kernel, no boot
1044 messages will appear after the boot loader tries to start the
1048 If you do NOT have ``options RANDOMDEV'' in your kernel and
1049 you DO want the random device then add randomdev_load="YES" to
1053 suidperl is now always built and installed on the system, but
1054 with permissions of 511. If you have applications that use
1055 this program, you are now required to add ENABLE_SUIDPERL=true
1056 to /etc/make.conf. If you forget to do this,
1057 chmod 4511 /usr/bin/suidperl
1058 will fix this until the next build.
1061 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
1062 visible changes that may immediately affect your configuration
1064 - New default file locations from src/contrib/sendmail/cf/README
1065 - newaliases limited to root and trusted users
1066 - MSA port (587) turned on by default
1067 - New queue file naming system so can't go from 8.11 -> 8.9
1068 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
1069 - FEATURE(`nullclient') is more full featured
1070 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
1071 - mail.local FreeBSD-only -b option changed to -B
1072 - See src/contrib/sendmail/RELEASE_NOTES for more info
1075 suidperl (aka sperl) is no longer build by default. You must
1076 specifically define BUILD_SUIDPERL to "true" for it to be build.
1077 Furthermore, we recommend that you remove /usr/bin/sperl* and
1078 /usr/bin/suidperl files from your system unless you have a
1079 specific use for it.
1082 Networking defaults have been tightened. Anybody upgrading
1083 /etc/defaults/rc.conf needs to add the following lines to
1084 /etc/rc.conf if they want to have the same setup
1085 afterwards (unless the variables already are set, of course):
1086 # Enable network daemons for user convenience.
1088 portmap_enable="YES"
1089 sendmail_enable="YES"
1092 If you have null_load="YES" in your /boot/loader.conf, you
1093 will need to change that to nullfs_load="YES".
1096 The "installkernel" target has changed slightly. Now even if
1097 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
1098 it will install the MYKERNEL file (built with the buildkernel
1099 target) as /kernel rather than /MYKERNEL. Those who have
1100 updated their /boot/loader.conf files to point to /MYKERNEL
1101 should remove that entry or perform manual rename of /kernel
1105 If you use CVSUP or CTM to get CVS trees, AND you used to get
1106 the old crypto files from internat.freebsd.org AND you check
1107 out files from the CVS tree with the cvs command, please read
1108 http://people.freebsd.org/~imp/internat.txt
1109 for details on potential problems that you might have and how
1112 If you are merely a mirror, or don't answer yes to each of the
1113 clauses above, you needn't worry.
1116 /etc/security has been updated to print the inode number of
1117 setuid programs that have changed. You will see a large spike
1118 in the number of changed programs the first time when you run
1119 mergemaster to get a new /etc/security.
1122 /dev/random now has good entropy collection (from the keyboard
1123 and sysmouse drivers). Please ensure that either `options
1124 RANDOMDEV' is present in your kernel config file or that
1125 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
1126 not have the /dev/random driver, OpenSSL (and consequently
1127 lots of crypto tools (like SSH)) will fail with strange
1128 errors. (see below, 20000624).
1130 FreeBSD-current is safe again to run Crypto.
1133 phk made the malloc default options AJ. This may slow things
1134 down and uncover other latent bugs in the code. If you need to
1135 run at full speed, you can disable this by doing the following:
1136 ln -s aj /etc/malloc.conf
1139 libftpio's version was accidentally bumped a few days ago. This
1140 has been corrected. You may need to remove /usr/lib/libftpio.so.6
1141 before doing your next buildworld/installworld pair. It certainly
1142 won't hurt to remove it before the update procedure. It will
1143 break fetch until a new one is built, but ftp can be used in the
1147 The crypto packages have changed for the cvsup. This has been done
1148 in a backward compatible way, but the old packages will go away at
1149 some point in the future. Look at /usr/share/examples/cvsup for
1153 With the new sys/modules/sound/drivers/*, you will need to
1154 set SYSDIR until you do an installworld after July 7th.
1157 rc.shutdown and rc will now call the rc.d scripts with start
1158 or stop. This may cause some harmless warnings from older
1159 rc.d scripts that haven't been updated.
1162 The libfetch based version of fetch has gone into the tree.
1163 Minor problems may result on some of the less popular sites,
1164 which should be reported to des@freebsd.org.
1167 From approximately this date forward, one must have the crypto
1168 system installed in order to build the system and kernel.
1169 While not technically strictly true, one should treat it as
1170 required and grab the crypto bits. If you are grabbing CVS
1171 trees, src-all and cvs-crypto should be treated as if they
1172 were required. You should check with the latest collections
1173 to make sure that these haven't changed.
1176 Mark Murray just committed the first parts of a cleanup of
1177 /dev/zero, et al. This is also cleaning up /dev/random.
1178 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1179 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1180 until Mark can merge in the fixes to this work in progress.
1181 openssh and openssl should not be used to generate keys from this
1182 date to the completion of the work.
1184 If you must operate at this reduced level of security, add '
1185 options RANDOMDEV' to your kernel or modload the randomdev
1186 module. You may also need to copy a new MAKEDEV to /dev and
1187 recreate the random and urandom devices.
1190 The license on the softupdates is now a standard 2 clause
1191 BSD license. You may need to remove your symbolic links
1192 that used to be required when updating.
1195 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1196 the config file update procedure.
1197 http://people.freebsd.org/~imp/config-upd.html
1198 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1199 isn't buildable. However, you can generate a LINT file:
1200 cd /sys/<ARCH>/conf && make LINT
1203 Binutils 2.10 have hit the tree, or will shortly. As soon
1204 as they do, the problem noted in 20000522 will be resolved and
1205 that workaround will no longer be required.
1208 phk removed the compatibility creation of wd devices in the
1209 ad driver. If you haven't done so already, you must update
1210 your fstab, etc to use the ad devices instead of the wd
1213 In addition, you'll need to update your boot blocks to a
1214 more modern version, if you haven't already done so. Modern
1215 here means 4.0 release or newer (although older releases
1219 Peter took an axe to config(8). Be sure that you read his mail
1220 on the topic before even thinking about updating. You will
1221 need to create a /boot/device.hints or add a hints directive
1222 to your config file to compile them in statically. The format
1223 of the config file has changed as well. Please see GENERIC or
1224 NEWCARD for examples of the new format.
1226 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1227 says that it has been fixed, assume that must use the hints mechanism
1228 in the loader if you need to use a machine with very old ISA cards
1232 A new set of binutils went into the tree today. Anybody
1233 building a kernel after this point is advised that they need
1234 to rebuild their binutils (or better yet do a
1235 buildworld/installworld) before building a new kernel.
1237 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1238 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1239 is recommended that you don't set this option until the problem
1243 The ethernet drivers were all updated to clean up the BPF handling.
1246 The problems with boot blocks on the alphas have been corrected.
1247 This will require some care in updating alphas. A new libstand
1248 is requires for the boot blocks to build properly.
1251 Recompile all kld modules. Proper version dependency info
1255 Modules have been disconnected from the buildworld tree and
1256 connected to the kernel building instead.
1259 You may need to build gperf
1260 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1261 when upgrading from 4.0 -> current. The build system now uses
1262 an option only in -current.
1265 The method that we brand ELF binaries has changed to be more
1266 acceptable to the binutils maintainers. You will need to
1267 rebrand your ELF binaries that aren't native. One problem
1268 binary is the Linux ldconfig. After your make world, but
1269 before you reboot, you'll need to issue:
1270 brandelf -t Linux /compat/linux/sbin/ldconfig
1271 if you have Linux compatibility enabled on your machine.
1274 If you have really bad/marginal IDE drives, you may find they
1275 don't work well. Use pio mode instead. The easiest way to
1276 cope if you have a problem combination is to add:
1277 /sbin/sysctl hw.ata.ata_dma=0
1278 to the start of /etc/rc.conf.
1281 The ISA and PCI compatibility shims have been connected to the
1282 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1283 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1284 include the appropriate option in your kernel config. Drivers
1285 using the shims should be updated or they won't ship with
1286 5.0-RELEASE, targeted for 2001.
1289 We've entered the traditional post release dumping party.
1290 Large kernel changes are being committed and are in the
1291 works. It is important to keep the systems' klds and kernel
1292 in sync as kernel interfaces and structures are changing.
1293 Before reporting kernel panics, make sure that all modules
1294 that you are loading are up to date.
1297 If you are upgrading from an older version of FreeBSD, you
1298 need to update your boot blocks as well. 'disklabel -B ad0'
1299 will do the trick. This isn't critical until you remove your
1300 wd device entries in /dev, at which point your system will not
1304 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1305 to upgrade to 4.0 from 3.x.
1311 Avoid using make -j when upgrading. From time to time in the
1312 past there have been problems using -j with buildworld and/or
1313 installworld. This is especially true when upgrading between
1314 "distant" versions (eg one that cross a major release boundary
1315 or several minor releases, or when several months have passed
1316 on the -current branch).
1318 Sometimes, obscure build problems are the result of environment
1319 poisoning. This can happen because the make utility reads its
1320 environment when searching for values for global variables.
1321 To run your build attempts in an "environmental clean room",
1322 prefix all make commands with 'env -i '. See the env(1) manual
1323 page for more details.
1327 If you are updating from a prior version of FreeBSD (even one just
1328 a few days old), you should follow this procedure. With a
1329 /usr/obj tree with a fresh buildworld,
1330 make -DALWAYS_CHECK_MAKE buildkernel KERNCONF=YOUR_KERNEL_HERE
1331 make -DALWAYS_CHECK_MAKE installkernel KERNCONF=YOUR_KERNEL_HERE
1333 To just build a kernel when you know that it won't mess you up
1334 --------------------------------------------------------------
1335 cd src/sys/{i386,alpha}/conf
1336 config KERNEL_NAME_HERE
1337 cd ../../compile/KERNEL_NAME_HERE
1342 If this fails, go to the "To build a kernel" section.
1344 To rebuild everything and install it on the current system.
1345 -----------------------------------------------------------
1346 # Note: sometimes if you are running current you gotta do more than
1347 # is listed here if you are upgrading from a really old current.
1349 <make sure you have good level 0 dumps>
1350 <maybe fix /etc/fstab> [7]
1352 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1353 make installkernel KERNCONF=YOUR_KERNEL_HERE
1355 <reboot in single user> [3]
1362 To cross-install current onto a separate partition
1363 --------------------------------------------------
1364 # In this approach we use a separate partition to hold
1365 # current's root, 'usr', and 'var' directories. A partition
1366 # holding "/", "/usr" and "/var" should be about 2GB in
1369 <make sure you have good level 0 dumps>
1372 <maybe newfs current's root partition>
1373 <mount current's root partition on directory ${CURRENT_ROOT}>
1374 make installworld DESTDIR=${CURRENT_ROOT}
1375 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1376 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1377 ${CURRENT_ROOT}/boot/device.hints # as needed
1378 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1379 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1380 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1381 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1382 <reboot into current>
1383 <do a "native" rebuild/install as described in the previous section>
1384 <maybe install compatibility libraries from /usr/src/lib/compat>
1388 To upgrade in-place from 4.x-stable to current
1389 ----------------------------------------------
1390 # 5.x uses more space than 4.x. Also, the location of kernel
1391 # modules has changed. If you are installing 5.0 onto a 4.x
1392 # system, you'll need about 30MB of free disk space on your /
1393 # partition. If you have less than this, you may encounter difficult
1394 # to back out of problems with this procedure. If /tmp is on
1395 # the / partition, you may want to completely remove all its content
1396 # before upgrading, as this can be a common source of shortage of
1399 <make sure you have good level 0 dumps>
1400 <maybe fix /etc/fstab> [7]
1402 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1403 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1404 make installkernel KERNCONF=YOUR_KERNEL_HERE
1405 cd src/sys/boot ; make install [6]
1407 <reboot in single user> [3]
1409 rm -rf /usr/include/g++
1414 Make sure that you've read the UPDATING file to understand the
1415 tweaks to various things you need. At this point in the life
1416 cycle of current, things change often and you are on your own
1417 to cope. The defaults can also change, so please read ALL of
1418 the UPDATING entries.
1420 Also, if you are tracking -current, you must be subscribed to
1421 freebsd-current@freebsd.org. Make sure that before you update
1422 your sources that you have read and understood all the recent
1423 messages there. If in doubt, please track -stable which has
1424 much fewer pitfalls.
1426 [1] If you have third party modules, such as vmware, you
1427 should disable them at this point so they don't crash your
1430 [2] If you have legacy ISA devices, you may need to create
1431 your own device.hints to reflect your unique hardware
1434 [3] From the bootblocks, boot -s, and then do
1439 adjkerntz -i # if CMOS is wall time
1440 Also, when doing a major release upgrade, it is required that
1441 you boot into single user mode to do the installworld.
1442 For the 4.x -> 5.0 upgrade, you will also see many messages about
1443 needing to recompile your userland. These are harmless and can
1444 be ignored while you proceed to the next step.
1446 [4] Note: This step is non-optional. Failure to do this step
1447 can result in a significant reduction in the functionality of the
1448 system. Attempting to do it by hand is not recommended and those
1449 that pursue this avenue should read this file carefully, as well
1450 as the archives of freebsd-current and freebsd-hackers mailing lists
1451 for potential gotchas.
1453 [5] Usually this step is a noop. However, from time to time
1454 you may need to do this if you get unknown user in the following
1455 step. It never hurts to do it all the time. You may need to
1456 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1457 install) after the buildworld before this step if you last updated
1458 from current before 20020224 or from -stable before 20020408.
1460 [6] 4.x boot loader can be used to boot a 5.x system, however
1461 it is difficult to do that at best. If you wish to try, then
1462 you should interrupt the boot and at the ok prompt type:
1464 ok boot /boot/kernel/kernel
1465 If this fails to work, you must install a new boot loader as
1468 [7] Before you upgrade, please make sure that you are not using
1469 compatibility slices. These are device names of the form, on i386
1470 and other architectures that use MBR slicing, /dev/ad0a without the
1471 actual slice name. Chances are excellent that these will break.
1472 You generally must update these entries to use the post FreeBSD
1473 2.x form of /dev/ad0s1a.
1475 [8] In order to have a kernel that can run the 4.x binaries
1476 needed to do an installworld, you must include the COMPAT_FREEBSD4
1477 option in your kernel. Failure to do so may leave you with a system
1478 that is hard to boot to recover.
1480 [9] When checking out sources, you must include the -P flag to have
1481 cvs prune empty directories.
1484 This file contains a list, in reverse chronological order, of major
1485 breakages in tracking -current. Not all things will be listed here,
1486 and it only starts on March 15, 2000. Updating files can found in
1487 previous releases if your system is older than this.
1489 Copyright information:
1491 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1493 Redistribution, publication, translation and use, with or without
1494 modification, in full or in part, in any form or format of this
1495 document are permitted without further permission from the author.
1497 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1498 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1499 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1500 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1501 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1502 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1503 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1504 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1505 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1506 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1507 POSSIBILITY OF SUCH DAMAGE.
1509 If you find this document useful, and you want to, you may buy the
1512 Contact Warner Losh if you have any questions about your use of