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 5.0-CURRENT IS SLOW:
8 FreeBSD 5.0-CURRENT has many debugging features turned on, in
9 both the kernel and userland. These features attempt to detect
10 incorrect use of system primitives, and encourage loud failure
11 through extra sanity checking and fail stop semantics. They
12 also substantially impact system performance. If you want to
13 do performance measurement, benchmarking, and optimization,
14 you'll want to turn them off. This includes various WITNESS-
15 related kernel options, INVARIANTS, malloc debugging flags
16 in userland, and various verbose features in the kernel. Many
17 developers choose to disable these features on build machines
18 to maximize performance.
21 The value of IPPROTO_DIVERT has changed. Make sure to keep
22 your kernel, netstat, natd and any third-party DIVERT
26 Old, compatibility slices have been removed in GEOM kernels. This
27 means that you will have to update your /etc/fstab to not use
28 disk devices of the form /dev/ad0a. Instead, you now must
29 specify /dev/ad0s1a, or whatever slice your FreeBSD partition
30 really is on. The old device names have gone away, so if you
31 use them anywhere else, you must also adjust those uses.
34 Alphas with kernels from between 20020830 and 20021023 and/or
35 rtld (ld-elf.so.1) older than 20021023 may experience problems
36 with groff while doing a buildworld (kernel: "out of memory",
37 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
38 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
40 So, to successfully upgrade your Alpha, you must either
41 upgrade your kernel and rtld first (which might be a bit
42 tricky), or avoid running the bootstrapped groff during the
43 "transitional" buildworld. To avoid running groff during the
44 transitional upgrade run make buildworld with -DNOMAN,
45 -DNO_SHAREDOCS, and -DNO_LPR.
48 gcc has been upgraded to 3.2. It is not all binary compatible
49 with earlier versions of gcc for c++ programs. All c++
50 programs and libraries need to be recompiled.
52 Also, if you encounter g++ issues, rm /usr/include/g++/* before
53 doing an installworld to make sure that stale files are removed.
56 Our /etc/termcap now has all the entries from the XFree86 xterm
57 almost unchanged. This means xterm now supports color by default.
58 If you used TERM=xterm-color in the past you now should use
59 TERM=xterm. (xterm-color will lead to benign warnings).
62 A "bug" in gcc(1) that was hiding warning in system headers was
63 fixed. It's probably time to add -DNO_WERROR to your make line
67 COPY is being deprecated. The 20010530 change was reverted, as
68 it causes far more pain than was expected, and to always compare
69 before installing, please use INSTALL="install -C" again. The
70 -C option is now silently ignored when used with the -d option.
73 Problems with libc_r clients like KDE and GNOME have been resolved.
74 There are still some minor problems with some signals but the
75 system is stable enough for general use again. SMP is less so than UP
76 but each can successfully complete multiple buildworlds.
77 Libkvm needs to be recompiled due to KSE.
80 Now would be a bad time to upgrade. Something in or near the
81 KSE commit totally broke programs using libc_r like KDE and
85 The k5su utility installed as part of Kerberos 5 is no longer
86 installed with the set-user-ID bit set by default. Add
87 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
88 with the set-user-ID bit set.
91 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
92 Unfortunately our native GDB (at version 4.18) does not understand
93 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
94 generated debugging information for our native GDB.
97 Due to the way CVS works, it may not properly update src/contrib/gcc
98 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
99 and then do a cvs update.
102 When exec'ing set[ug]id executables, the kernel now ensures that the
103 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
106 New sendmail startup scripts have been installed to make it
107 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
108 variable sendmail_enable to "NO" no longer prevents any sendmail
109 daemons from starting. Instead, either set sendmail_enable to
110 "NONE" or change mta_start_script to a script for starting
111 an alternative MTA. Setting mta_start_script to "" will
112 also prevent any MTA from being started at boot.
115 UCONSOLE is no longer a valid kernel option.
118 FreeBSD 5.0 DP-1 was basically branched today.
121 Warnings are now errors in the kernel. Unless you are a developer,
122 you should add -DNO_WERROR to your make line.
125 sendmail 8.12.2 has been imported. The sendmail binary is no
126 longer a set-user-ID root binary and the infrastructure to support
127 command line mail submission has changed. Be sure to run
128 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
129 and /etc/mail) and read /etc/mail/README for more details.
131 Due to the import of sendmail 8.12.2, a new user and group are
132 required in order for sendmail to run as a set-group-ID
133 binary. A 'make installworld' will use the new user and group
134 to set the owner and group of /var/spool/clientmqueue and will
135 fail if the new user and group do not exist. The 'smmsp' user
136 and group must be merged from src/etc/group and
137 src/etc/master.passwd before using 'make installworld'.
138 'mergemaster -p' will do this. You may need to install
139 mergemaster before this will work if you are updating from a
140 very old version of current. The updating recipe has changed
144 The preferred configuration method for PAM is now /etc/pam.d/
145 rather than /etc/pam.conf. If you have an unmodified
146 pam.conf, just delete it after your next mergemaster run. If
147 you have local modifications, you can use
148 /usr/src/etc/pam.d/convert.pl to incorporate them into your
151 Please see the following url for more details:
152 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
154 If anyone here is already using the new rc.conf(5) variable
155 networkfs_types, please note that it has changed
156 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
159 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
160 started out its life in the ISDN4BSD project as an offspring
161 from sys/net/if_spppsubr.c, which eventually got a life of its
162 own. All the accumulated features and bugfixes of the i4b
163 version have now been merged back into the base system's
164 version now. The only user-visible change resulting from this
165 is that i4b's sppp(4) interfaces are to be managed with
166 spppcontrol(8) again, since ispppcontrol(8) has been retired
167 as well. (There has never been rc file support for
168 ispppcontrol in -current, but only in -stable. That will be
169 reverted by the time the changes are MFCed.)
172 The fdc(4) driver has been updated and now automatically
173 recognizes media in `standard' formats (like 1440 KB and
174 720 KB for a 3.5" high-density drive) when accessing the
175 default device node (e. g. /dev/fd0). The old variety of
176 floppy device nodes /dev/fd*.* is no longer present by
177 default, devices can be created (in DEVFS) on demand. They
178 will need to be customized then for `odd' densities using
182 The bugs in procfs' debugging support code have been fixed,
183 and truss(1) now works again.
186 Daily security checks have been split out to use the periodic(8)
187 scripts. Some change in configuration may be necessary. Please
189 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
193 sos added VCD/SVCD support to ata driver and that needs the
194 kernel and burncd to be in sync.
197 The procfs pseudo-filesystem has now been converted to use the
198 pseudofs framework. If you have 'options PROCFS' in your
199 kernel config, you'll need to add 'options PSEUDOFS' if it's
202 This change temporarily breaks truss(1); use ktrace(1) instead
203 until the issue has been resolved.
206 A security hole in OpenSSH involving `UseLogin yes' has been
210 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
211 after this date. You need to do this only once.
214 Most of the awk issues have been resolved. Some rough
215 edges may be left, but for the most part things should be
216 back to "normal." For CURRENT's usual definition of "normal."
219 Awk has been upgraded to the one true awk from bell labs. Expect
220 choppy waves in the upgrade process.
223 The asr driver problem has been resolved.
226 Due to changes in other parts of the system, the asr driver
227 now causes the system to panic on boot. Do not use it pending
228 correction. Comment it out of any kernel config file that you
229 try to use from this date forward.
232 When crossbuilding, use TARGET=xxx where you used to use
233 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
234 unless you are changing both of them. To cross build pc98 on
235 an alpha, for example, you need to set TARGET=pc98 and
239 The kernel interface that burncd depends on has changed.
240 You must recompile both the kernel and userland applications
244 When crossbuilding, please set TARGET_ARCH rather than
245 MACHINE_ARCH to indicate the target. In the future, one will
246 set TARGET_MACHINE where you set MACHINE now. At the moment,
247 setting MACHINE alone for same MACHINE_ARCH machines works
248 (eg, you can build pc98 on a i386 machine and vice versa).
251 Some weird problems result from using ACPI on some machines.
252 To disable ACPI you can add
253 hint.acpi.0.disable="1"
254 to /boot/loader.conf (or by putting set X=Y at the boot
257 Alternatively, you can remove it from /boot/kernel/acpi.ko
258 or use the MODULES_OVERRIDE function in your kernel config
259 file and not list acpi in that list.
262 The buildworld has been fixed. You may need to install
263 the 4.x compatibility libraries for some old binaries
264 to work. Add COMPAT4X=true to your /etc/make.conf to
265 get them installed on every installworld, or execute the
266 following to get them installed only once:
267 cd src/lib/compat/compat4x.<arch>
269 You will see ``__stdoutp undefined'' until you do this.
272 There's a bug in the world build process. The cross-tools
273 are build with the NEW headers, but the OLD libc.a. This
274 leads to all kinds of problems with the new libc. A temporary
276 CFLAGS="-O -pipe -D_OLD_STDIO"
277 before building world when upgrading from 4.x to current. This
278 can be removed afterwards.
280 A proper fix to the buildworld target is needed.
283 Peter has committed his new kthread nfs client/server code.
284 NFS may be unstable after this date.
287 KSE has hit the tree. Lots of things are now different in
288 the kernel. While a few problems were introduced in the
289 initial commit, most of the major ones have been found and
293 In OLDCARD, CardBus bridges appear to be stable. The work
294 arounds described in the 20010604 entry are now no longer
295 necessary and will be ignored. Most insert/remove problems
296 have been rectified around this date.
299 named now runs as user bind and group bind rather than as
300 root. If named_enable is set to YES in /etc/rc.conf, ensure
301 that user bind is available in /etc/passwd (using vipw(8))
302 and that group bind is available in /etc/group. Also make
303 sure that user or group bind has read (and not write)
304 permission for your name server configuration and that it
305 has read and write permission for your slave zone files and
308 If you wish to continue to run named as root (a less secure
309 alternative), add a line to /etc/rc.conf saying
314 The PAM libraries have had an API upgrade that is beyond
315 the ability of the shared library major number to handle.
316 It is manifested by PAM-using ports dumping core. The
317 solution is to rebuild those ports.
320 The kernel compile module has moved from src/sys/compile/FOO
321 to src/sys/${MACHINE}/compile/FOO.
324 The pccard modem issue from 20010613 has been corrected.
325 OLDCARD support is still a little weak in -current. slot 1 is
326 known not to work on some TI based cardbus bridges. Some
327 cardbus bridges do not properly detect insert/removal events.
328 IRQ configuration needs more safety belts.
331 Softupdates problems have been corrected.
334 Peter ripped out the linkerset support. You must, as always,
335 rerun config after you cvsup if you are using the traditional
336 kernel building methods.
339 pccard modems may not work with current after 20010604 date. Some
340 do, others result in panics. *MAKE*SURE* that you update your
341 config and /etc/rc.conf ala the 20010604 entry, or you will have
342 problems (this issue will be fixed, it just hasn't been yet).
345 SOFTUPDATES seem to be broken since the middle of May or so. Do not
346 use them in current. You can disable softupdates on all mounted
347 partitions, or remove SOFTUPDATES the kernel config file.
350 After Peter's commits to the hints code, people have been noticing
351 that certain devices are attached (or try to) twice. This is due
352 to having both static hints as well as a /boot/device.hints. To
353 work around this issue, please use only one or the other mechanism
354 until this bug is fixed.
356 Please note that a feature of config is that if you have config
357 file FOO and FOO.hints, it automatically adds FOO.hints to the
358 hints.c file, wheather you want it to or not.
361 Locale names have changed to match other systems better.
364 pccard support for pci cards has been committed. You must change
365 your /etc/pccard.conf irq lines. It must match the irq used by
366 pcic device. Interrupt storms may result if you fail to do this.
367 Interrupt storms look a lot like a hang.
369 You must also install a new pccardd, otherwise you will get an
370 interrupt storm at card reset time (just after it tells you what
373 pccardd_flags="-I" is necessary for the time being. It tells pccardd
374 not to ask the kernel if the interrupt is really free or not before
375 using it. You can either change the /etc/pccard.conf irq lines to
376 match pcic, or add "-i X" to the pccardd_flags.
379 INSTALL=install -C is being deprecated. If you want to do this,
380 use COPY=-C instead. The former method will be supported for only
381 a limited time. If you see
383 install: warning: the -d and -C options may not be specified together
385 in your makeworld, then you need to migrate towards using
389 It appears that vm is now stable enough to use again. However,
390 there may be other problems, so caution is still urged. alpha
391 definitely is in bad shape.
394 Minor repo damange has happened. This may cause problems
395 with cvsup of ports. If you get errors, please see
396 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
397 at the bottom for details on a workaround. The error message
399 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
402 Vm and/or swapping are busted on -current. Please be patient.
405 pccard has had much reorganizational work done to it over
406 the past few days. Everything should still work, but if
407 not, please contact imp@freebsd.org.
410 ata ioctl changed. Make sure to recompile both kernel and
411 userland at the same time.
414 New ncurses imported.
417 DEVFS is now opt out, not opt in. Barring major problems, this
418 will be the only way to go starting July 1.
421 OpenSSH has been updated to 2.9. Some defaults are different,
422 including RhostsRSAAuthentication, which changes from yes to no.
425 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
428 Building perl was broken at 02:25:25 PDT.
431 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
432 go back in the water.
435 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
436 this date, but before the correction date.
439 old fsck and new kernel interactions appear to have been fixed.
442 fsck and the kernel were changed to handle some optimizations
443 to directory layout. This breaks backward compatibility.
444 Update only if you understand that you must not use the old
445 fsck with the new kernel ever.
448 fsck has changed the meaning of the pass column in /etc/fstab.
449 Please see the cvs commit to fsck.8 or the fsck.8 man page for
450 details. It is unclear if changes to /etc/fstab are necessary.
453 portmap had changed name to rpcbind for maximum POLA in your
454 current world. /etc/hosts.{allow,deny} needs changes. nfs and
455 other rpc based programs that rely on portmapper will not work
456 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
459 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
460 and ATA_ENABEL_TAGS are no longer kernel options. They have
461 been replaced by tunables. See ata.4 for details.
464 The fxp driver was converted to use miibus. If you compile
465 fxp into your kernel statically, you will need to add miibus.
468 The wi device now defaults to BSS (infrastructure) mode
472 /dev/urandom should be a symbolic link to /dev/random now.
473 Users of current not using DEVFS need to run MAKEDEV std.
474 ssh might not work if you don't.
477 The ed driver has been updated. It now allows mii attachments,
478 which means that you must include the miibus in your kernel if
479 you use the ed driver.
482 The problems with libc have been corrected. It is now mostly
483 safe to go back into the water.
486 The size of FILE was changed. This breaks upgrading. If
487 you must upgrade, be prepared for pain. It also breaks almost
488 all binaries that you've compiled on -current. You are warned
489 that before upgrading would be a good time to do a level 0
490 dump of your system. No, really, I mean it this time.
492 To get to the new system, you'll need to use the following
493 workaround. Hopefully this can be sorted out so that we
494 don't have to move this to the updating section.
496 To get around the installworld problem, do:
497 # cd /usr/src/usr.bin/sed
501 If that doesn't work, then try:
502 # make -k installworld
506 DEVFS is now the default. If you use vinum, make sure that you
507 do not include devfs in your kernel as problems result.
510 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
511 Remove them from your config.
514 ****************************** WARNING ******************************
515 buildkernel has been changed slightly
516 ****************************** WARNING ******************************
517 KERNCONF replaces the variable KERNEL for buildkernel. You
518 should update your scripts and make.conf accordingly.
521 config has changed to allow DEV_FOO as a replacement for NFOO.
522 This requires a new config to build correctly.
525 The kerrnel option I386_CPU is now mutually exclusive with the
526 other cpu types. If you have an i386 system, be sure that it
527 only had this line. Remove it for all other configurations.
530 Changes to the kernel require it and burncd be in sync.
533 Everyone who has hw.sndunit set to something in
534 /etc/sysctl.conf, it is now hw.snd.unit.
537 ex and vi were broken by some changes to sys/queue.h. If you
538 have a bad vi, you will see make buildworld fail with a core
539 dump while building termcap. You can work around this problem
540 by adding -k to your make buildworld. This will cause the
541 build to complete and install a new vi. Once that's done, you
542 can rebuild again without the -k to pick up anything that
543 might have been ignored by the -k option.
545 Others have suggested that you can just rebuild libc if your
546 vi/ex is dynamically linked, but I've not received any reports
550 There have been some changes to libcrypt in -current. The
551 libscrypt/libdescrypt symlink sillyness is gone and the installed
552 libcrypt is fully functional. Be aware of this.
555 Linksys Fast Ethernet PCCARD cards supported by the ed driver
556 now require the addition of flag 0x80000 to their config line
557 in pccard.conf(5). This flag is not optional. These Linksys
558 cards will not be recognized without it.
561 Important new FreeBSD-version stuff: PAM support has been worked
562 in, partially from the "Unix" OpenSSH version. This requires
563 adding the following in pam.conf:
565 sshd auth sufficient pam_skey.so
566 sshd auth required pam_unix.so try_first_pass
567 sshd session required pam_permit.so
573 The random device needs more entropy, so you need to make sure
574 that you've run mergemaster to get a /etc/rc which will seed
575 /dev/random. If you don't and the system hangs after ldconfig,
576 then banging on the keyboard randomly until it unhangs is one
580 ****************************** WARNING ******************************
581 Sendmail has been updated.
582 ****************************** WARNING ******************************
583 o mail.local(8) is no longer installed as a set-user-id binary.
584 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
586 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
588 o Now using sendmail's version of vacation(1).
589 o The sendmail cf building tools (contrib/sendmail/cf) are installed
590 in /usr/share/sendmail/cf.
591 o sendmail.cw changed to local-host-names
593 More details can be found at
594 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
597 The ports tree's new layout is in place. Be sure to update
598 your entire ports tree, or you will have problems.
601 The perl build procedure no longer installs miniperl, nor uses
602 the installed miniperl. It is recommended that you delete
606 This weekend the ports tree will be updated to a new layout.
607 It will be in an inconsistent state until noted in the UPDATING
608 file, or with asami-san's message to the relevant mailing
609 lists. With this new layout, you'll need to update the whole
610 tree for anything to work.
613 There was a change in the passwd format. Need more information.
616 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
617 place. Please update boot loader (not the boot blocks) at the
618 same time as your kernel.
621 The new pmtimer device is necessary for laptops. Failure to
622 include the device will cause suspended laptops losing time
623 when they resume. Include
625 in your config file and
626 hint.pmtimer.0.at="isa"
627 to your /boot/device.hints file.
630 The random device has been turned into a (pseudo-)device,
631 rather than an option. The supplied kernel config files have
632 been updated. You will need to do something similar in your
633 own kernel config file.
638 If you prefer to load the loadable module, you need to do
642 The random device module has been renamed from randomdev.ko to
643 random.ko. You will need to edit your /boot/loader.conf to
644 reflect this if you load this module at boot time.
645 The line should read:
649 The SMPNG commit has happened. It should work, but if it
650 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
651 to be a variety of minor issues. Please see 20000905 to make
652 sure you don't have model loading problems which might at
653 first blush appear related to SMP.
656 nsswitch has been imported from NetBSD. Among other things,
657 this means that /etc/host.conf is no longer used. See
658 nsswitch.conf(5) instead. Note that at boot time rc.network
659 will attempt to produce a new nsswitch.conf file for you if you
660 don't have one, and you have host.conf.
663 The ucred structure changed size. This breaks the interface
664 that mountd uses. Trying to use an older mountd with a newer
665 kernel guarantees a panic. This means that you need to use
666 kernels newer than today only with matching mountd, but you
667 needed to do that anyway with the boot loader changes.
670 The boot loader has been updated. The new default kernel is
671 now /boot/kernel/kernel.ko. The new default module location
674 You *MUST* upgrade your boot loader and kernel at the same time.
675 The easiest way to do this is to do the buildworld/buildkernel/
676 installkernel/installworld dance.
678 Furthermore, you are urged to delete your old /modules directory
679 before booting the new kernel, since kldload will find stale
680 modules in that directory instead of finding them in the correct
681 path, /boot/kernel. The most common complaint that this cures
682 is that the linux module crashes your machine after the update.
684 if [ ! -d /boot/kernel.old ]; then
685 mv /modules.old /boot/kernel.old
686 chflags noschg /kernel.old
687 mv /kernel.old /boot/kernel.old/kernel.ko
688 chflags schg /boot/kernel.old/kernel.ko
692 A new issue with the sendmail upgrade has come to light.
693 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
694 incorrectly install the default aliases in /etc/mail rather than
695 move the old one from /etc. So you'll need to manually move the
696 file, create a symbolic link, remove the old /etc/aliases.db and
697 run newaliases. For safety sake, you should stop sendmail
698 while doing this and run the upgrade when locally sourced email
699 is not likely to be generated.
702 /boot/device.hints is now required for installkernel to
703 succeed. You should copy GENERIC.hints for your architecture
704 into /boot/device.hints. If and only if you compile hints
705 into your kernel, then this file may be empty. Please note,
706 if you have an empty or missing /boot/device.hints file and
707 you neglected to compile hints into your kernel, no boot
708 messages will appear after the boot loader tries to start the
712 If you do NOT have ``options RANDOMDEV'' in your kernel and
713 you DO want the random device then add randomdev_load="YES" to
717 suidperl is now always built and installed on the system, but
718 with permissions of 511. If you have applications that use
719 this program, you are now required to add ENABLE_SUIDPERL=true
720 to /etc/make.conf. If you forget to do this,
721 chmod 4511 /usr/bin/suidperl
722 will fix this until the next build.
725 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
726 visible changes that may immediately affect your configuration
728 - New default file locations from src/contrib/sendmail/cf/README
729 - newaliases limited to root and trusted users
730 - MSA port (587) turned on by default
731 - New queue file naming system so can't go from 8.11 -> 8.9
732 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
733 - FEATURE(`nullclient') is more full featured
734 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
735 - mail.local FreeBSD-only -b option changed to -B
736 - See src/contrib/sendmail/RELEASE_NOTES for more info
739 suidperl (aka sperl) is no longer build by default. You must
740 specifically define BUILD_SUIDPERL to "true" for it to be build.
741 Furthermore, we recommend that you remove /usr/bin/sperl* and
742 /usr/bin/suidperl files from your system unless you have a
746 Networking defaults have been tightened. Anybody upgrading
747 /etc/defaults/rc.conf needs to add the following lines to
748 /etc/rc.conf if they want to have the same setup
749 afterwards (unless the variables already are set, of course):
750 # Enable network daemons for user convenience.
753 sendmail_enable="YES"
756 If you have null_load="YES" in your /boot/loader.conf, you
757 will need to change that to nullfs_load="YES".
760 The "installkernel" target has changed slightly. Now even if
761 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
762 it will install the MYKERNEL file (built with the buildkernel
763 target) as /kernel rather than /MYKERNEL. Those who have
764 updated their /boot/loader.conf files to point to /MYKERNEL
765 should remove that entry or perform manual rename of /kernel
769 If you use CVSUP or CTM to get CVS trees, AND you used to get
770 the old crypto files from internat.freebsd.org AND you check
771 out files from the CVS tree with the cvs command, please read
772 http://people.freebsd.org/~imp/internat.txt
773 for details on potential problems that you might have and how
776 If you are merely a mirror, or don't answer yes to each of the
777 clauses above, you needn't worry.
780 /etc/security has been updated to print the inode number of
781 setuid programs that have changed. You will see a large spike
782 in the number of changed programs the first time when you run
783 mergemaster to get a new /etc/security.
786 /dev/random now has good entropy collection (from the keyboard
787 and sysmouse drivers). Please ensure that either `options
788 RANDOMDEV' is present in your kernel config file or that
789 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
790 not have the /dev/random driver, OpenSSL (and consequently
791 lots of crypto tools (like SSH)) will fail with strange
792 errors. (see below, 20000624).
794 FreeBSD-current is safe again to run Crypto.
797 phk made the malloc default options AJ. This may slow things
798 down and uncover other latent bugs in the code. If you need to
799 run at full speed, you can disable this by doing the following:
800 ln -s aj /etc/malloc.conf
803 libftpio's version was accidentally bumped a few days ago. This
804 has been corrected. You may need to remove /usr/lib/libftpio.so.6
805 before doing your next buildworld/installworld pair. It certainly
806 won't hurt to remove it before the update procedure. It will
807 break fetch until a new one is built, but ftp can be used in the
811 The crypto packages have changed for the cvsup. This has been done
812 in a backward compatible way, but the old packages will go away at
813 some point in the future. Look at /usr/share/examples/cvsup for
817 With the new sys/modules/sound/drivers/*, you will need to
818 set SYSDIR until you do an installworld after July 7th.
821 rc.shutdown and rc will now call the rc.d scripts with start
822 or stop. This may cause some harmless warnings from older
823 rc.d scripts that haven't been updated.
826 The libfetch based version of fetch has gone into the tree.
827 Minor problems may result on some of the less popular sites,
828 which should be reported to des@freebsd.org.
831 From approximately this date forward, one must have the crypto
832 system installed in order to build the system and kernel.
833 While not technically strictly true, one should treat it as
834 required and grab the crypto bits. If you are grabbing CVS
835 trees, src-all and cvs-crypto should be treated as if they
836 were required. You should check with the latest collections
837 to make sure that these haven't changed.
840 Mark Murray just committed the first parts of a cleanup of
841 /dev/zero, et al. This is also cleaning up /dev/random.
842 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
843 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
844 until Mark can merge in the fixes to this work in progress.
845 openssh and openssl should not be used to generate keys from this
846 date to the completion of the work.
848 If you must operate at this reduced level of security, add '
849 options RANDOMDEV' to your kernel or modload the randomdev
850 module. You may also need to copy a new MAKEDEV to /dev and
851 recreate the random and urandom devices.
854 The license on the softupdates is now a standard 2 clause
855 BSD license. You may need to remove your symbolic links
856 that used to be required when updating.
859 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
860 the config file update procedure.
861 http://people.freebsd.org/~imp/config-upd.html
862 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
863 isn't buildable. However, you can generate a LINT file.
866 Binutils 2.10 have hit the tree, or will shortly. As soon
867 as they do, the problem noted in 20000522 will be resolved and
868 that workaround will no longer be required.
871 phk removed the compatibility creation of wd devices in the
872 ad driver. If you haven't done so already, you must update
873 your fstab, etc to use the ad devices instead of the wd
876 In addition, you'll need to update your boot blocks to a
877 more modern version, if you haven't already done so. Modern
878 here means 4.0 release or newer (although older releases
882 Peter took an axe to config(8). Be sure that you read his mail
883 on the topic before even thinking about updating. You will
884 need to create a /boot/device.hints or add a hints directive
885 to your config file to compile them in statically. The format
886 of the config file has changed as well. Please see GENERIC or
887 NEWCARD for examples of the new format.
889 Indirectly, this also breaks USERCONFIG. Unless a newer entry
890 says that it has been fixed, assume that must use the hints mechanism
891 in the loader if you need to use a machine with very old ISA cards
895 A new set of binutils went into the tree today. Anybody
896 building a kernel after this point is advised that they need
897 to rebuild their binutils (or better yet do a
898 buildworld/installworld) before building a new kernel.
900 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
901 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
902 is recommended that you don't set this option until the problem
906 The ethernet drivers were all updated to clean up the BPF handling.
909 The problems with boot blocks on the alphas have been corrected.
910 This will require some care in updating alphas. A new libstand
911 is requires for the boot blocks to build properly.
914 Recompile all kld modules. Proper version dependency info
918 Modules have been disconnected from the buildworld tree and
919 connected to the kernel building instead.
922 You may need to build gperf
923 cd /usr/src/gnu/usr.bin/gperf && make depend all install
924 when upgrading from 4.0 -> current. The build system now uses
925 an option only in -current.
928 The method that we brand ELF binaries has changed to be more
929 acceptable to the binutils maintainers. You will need to
930 rebrand your ELF binaries that aren't native. One problem
931 binary is the Linux ldconfig. After your make world, but
932 before you reboot, you'll need to issue:
933 brandelf -t Linux /compat/linux/sbin/ldconfig
934 if you have Linux compatibility enabled on your machine.
937 If you have really bad/marginal IDE drives, you may find they
938 don't work well. Use pio mode instead. The easiest way to
939 cope if you have a problem combination is to add:
940 /sbin/sysctl hw.ata.ata_dma=0
941 to the start of /etc/rc.conf.
944 The ISA and PCI compatibility shims have been connected to the
945 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
946 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
947 include the appropriate option in your kernel config. Drivers
948 using the shims should be updated or they won't ship with
949 5.0-RELEASE, targeted for 2001.
952 We've entered the traditional post release dumping party.
953 Large kernel changes are being committed and are in the
954 works. It is important to keep the systems' klds and kernel
955 in sync as kernel interfaces and structures are changing.
956 Before reporting kernel panics, make sure that all modules
957 that you are loading are up to date.
960 If you are upgrading from an older version of FreeBSD, you
961 need to update your boot blocks as well. 'disklabel -B ad0'
962 will do the trick. This isn't critical until you remove your
963 wd device entries in /dev, at which point your system will not
967 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
968 to upgrade to 4.0 from 3.x.
974 Avoid using make -j when upgrading. From time to time in the
975 past there have been problems using -j with buildworld and/or
976 installworld. This is especially true when upgrading between
977 "distant" versions (eg one that cross a major release boundary
978 or several minor releases, or when several months have passed
979 on the -current branch).
981 Sometimes, obscure build problems are the result of environment
982 poisoning. This can happen because the make utility reads its
983 environment when searching for values for global variables.
984 To run your build attempts in an "environmental clean room",
985 prefix all make commands with 'env -i '. See the env(1) manual
986 page for more details.
990 If you are updating from a prior version of FreeBSD (even one just
991 a few days old), you should follow this procedure. With a
992 /usr/obj tree with a fresh buildworld,
993 make buildkernel KERNCONF=YOUR_KERNEL_HERE
994 make installkernel KERNCONF=YOUR_KERNEL_HERE
996 To just build a kernel when you know that it won't mess you up
997 --------------------------------------------------------------
998 cd src/sys/{i386,alpha}/conf
999 config KERNEL_NAME_HERE
1000 cd ../../compile/KERNEL_NAME_HERE
1005 If this fails, go to the "To build a kernel" section.
1007 To rebuild everything and install it on the current system.
1008 -----------------------------------------------------------
1009 # Note: sometimes if you are running current you gotta do more than
1010 # is listed here if you are upgrading from a really old current.
1012 <make sure you have good level 0 dumps>
1013 <maybe fix /etc/fstab> [7]
1015 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1016 make installkernel KERNCONF=YOUR_KERNEL_HERE
1018 <reboot in single user> [3]
1025 To upgrade from 4.x-stable to current
1026 -------------------------------------
1027 # 5.x uses more space than 4.x. Also, the location of kernel
1028 # modules has changed. If you are installing 5.0 onto a 4.x
1029 # system, you'll need about 30MB of free disk space on your /
1030 # partition. If you have less than this, you may encounter difficult
1031 # to back out of problems with this proceedure. If /tmp is on
1032 # the / partition, you may want to completely remove all its content
1033 # before upgrading, as this can be a common source of shortage of
1036 <make sure you have good level 0 dumps>
1037 <maybe fix /etc/fstab> [7]
1039 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1040 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1041 make installkernel KERNCONF=YOUR_KERNEL_HERE
1042 cd src/sys/boot ; make install [6]
1044 <reboot in single user> [3]
1046 rm -rf /usr/include/g++
1051 Make sure that you've read the UPDATING file to understand the
1052 tweaks to various things you need. At this point in the life
1053 cycle of current, things change often and you are on your own
1054 to cope. The defaults can also change, so please read ALL of
1055 the UPDATING entries.
1057 Also, if you are tracking -current, you must be subscribed to
1058 freebsd-current@freebsd.org. Make sure that before you update
1059 your sources that you have read and understood all the recent
1060 messages there. If in doubt, please track -stable which has
1061 much fewer pitfalls.
1063 [1] If you have third party modules, such as vmware, you
1064 should disable them at this point so they don't crash your
1067 [2] If you have legacy ISA devices, you may need to create
1068 your own device.hints to reflect your unique hardware
1071 [3] From the bootblocks, boot -s, and then do
1076 adjkerntz -i # if CMOS is wall time
1077 Also, when doing a major release upgrade, it is required that
1078 you boot into single user mode to do the installworld.
1079 For the 4.x -> 5.0 upgrade, you will also see many messages about
1080 needing to recompile your userland. These are harmless and can
1081 be ignored while you proceed to the next step.
1083 [4] Note: This step is non-optional. Failure to do this step
1084 can result in a significant reduction in the functionality of the
1085 system. Attempting to do it by hand is not recommended and those
1086 that pursue this avenue should read this file carefully, as well
1087 as the archives of freebsd-current and freebsd-hackers mailing lists
1088 for potential gotchas.
1090 [5] Usually this step is a noop. However, from time to time
1091 you may need to do this if you get unknown user in the following
1092 step. It never hurts to do it all the time. You may need to
1093 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1094 install) after the buildworld before this step if you last updated
1095 from current before 20020224 or from -stable before 20020408.
1097 [6] 4.x boot blocks can be used to boot a 5.x system, however
1098 it is difficult to do that at best. If you are concerned
1099 about being able to boot 4.x if the reboot to single user
1100 fails, then you should do something like
1103 before this step. You may be able to then boot the 4.x boot
1104 blocks if you catch boot2, and enter /boot-4x/loader rather than
1105 /boot/loader. However, this step hasn't been torture tested.
1107 [7] Before you upgrade, please make sure that you are not using
1108 compatibility slices. These are device names of the form, on i386
1109 and other architectures that use MBR slicing, /dev/ad0a without the
1110 actual slice name. Chances are excellent that these will break.
1111 You generally must update these entries to use the post FreeBSD
1112 2.x form of /dev/ad0s1a.
1114 [8] In order to have a kernel that can run the 4.x binaries
1115 needed to do an installworld, you must include the COMPAT_FREEBSD4
1116 option in your kernel. Failure to do so may leave you with a system
1117 that is hard to boot to recover.
1119 [9] When checking out sources, you must include the -P flag to have
1120 cvs prune empty directories.
1123 This file contains a list, in reverse chronological order, of major
1124 breakages in tracking -current. Not all things will be listed here,
1125 and it only starts on March 15, 2000. Updating files can found in
1126 previous releases if your system is older than this.
1128 Copyright information:
1130 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1132 Redistribution, publication, translation and use, with or without
1133 modification, in full or in part, in any form or format of this
1134 document are permitted without further permission from the author.
1136 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1137 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1138 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1139 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1140 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1141 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1142 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1143 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1144 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1145 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1146 POSSIBILITY OF SUCH DAMAGE.
1148 If you find this document useful, and you want to, you may buy the
1151 Contact Warner Losh if you have any questions about your use of