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.
20 In addition, IDE write caching is currently disabled by default
21 due to on-going concerns about disk write order and file system
22 integrity. Re-enabling write caching can substantially improve
26 Due to a compiler upgrade, the set of warnings has changed,
27 resulting in new compile failures when -Werror is set
28 inappropriately. While the set of warnings is adjusted and
29 fixed, it is recommended that you place "NO_WERROR=yes" on
30 the make line for buildworld/buildkernel, or in /etc/make.conf
34 The k5su utility installed as part of Kerberos 5 is no longer
35 installed with the set-user-ID bit set by default. Add
36 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
37 with the set-user-ID bit set.
40 Due to the way CVS works, it may not properly update src/contrib/gcc
41 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
42 and then do a cvs update.
45 When exec'ing set[ug]id executables, the kernel now ensures that the
46 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
49 New sendmail startup scripts have been installed to make it
50 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
51 variable sendmail_enable to "NO" no longer prevents any sendmail
52 daemons from starting. Instead, either set sendmail_enable to
53 "NONE" or change mta_start_script to a script for starting
54 an alternative MTA. Setting mta_start_script to "" will
55 also prevent any MTA from being started at boot.
58 UCONSOLE is no longer a valid kernel option.
61 FreeBSD 5.0 DP-1 was basically branched today.
64 Warnings are now errors in the kernel. Unless you are a developer,
65 you should add -DNO_WERROR to your make line.
68 sendmail 8.12.2 has been imported. The sendmail binary is no
69 longer a set-user-ID root binary and the infrastructure to support
70 command line mail submission has changed. Be sure to run
71 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
72 and /etc/mail) and read /etc/mail/README for more details.
74 Due to the import of sendmail 8.12.2, a new user and group are
75 required in order for sendmail to run as a set-group-ID
76 binary. A 'make installworld' will use the new user and group
77 to set the owner and group of /var/spool/clientmqueue and will
78 fail if the new user and group do not exist. The 'smmsp' user
79 and group must be merged from src/etc/group and
80 src/etc/master.passwd before using 'make installworld'.
81 'mergemaster -p' will do this. You may need to install
82 mergemaster before this will work if you are updating from a
83 very old version of current. The updating recipe has changed
87 The preferred configuration method for PAM is now /etc/pam.d/
88 rather than /etc/pam.conf. If you have an unmodified
89 pam.conf, just delete it after your next mergemaster run. If
90 you have local modifications, you can use
91 /usr/src/etc/pam.d/convert.pl to incorporate them into your
94 Please see the following url for more details:
95 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
97 If anyone here is already using the new rc.conf(5) variable
98 networkfs_types, please note that it has changed
99 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
102 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
103 started out its life in the ISDN4BSD project as an offspring
104 from sys/net/if_spppsubr.c, which eventually got a life of its
105 own. All the accumulated features and bugfixes of the i4b
106 version have now been merged back into the base system's
107 version now. The only user-visible change resulting from this
108 is that i4b's sppp(4) interfaces are to be managed with
109 spppcontrol(8) again, since ispppcontrol(8) has been retired
110 as well. (There has never been rc file support for
111 ispppcontrol in -current, but only in -stable. That will be
112 reverted by the time the changes are MFCed.)
115 The fdc(4) driver has been updated and now automatically
116 recognizes media in `standard' formats (like 1440 KB and
117 720 KB for a 3.5" high-density drive) when accessing the
118 default device node (e. g. /dev/fd0). The old variety of
119 floppy device nodes /dev/fd*.* is no longer present by
120 default, devices can be created (in DEVFS) on demand. They
121 will need to be customized then for `odd' densities using
125 The bugs in procfs' debugging support code have been fixed,
126 and truss(1) now works again.
129 Daily security checks have been split out to use the periodic(8)
130 scripts. Some change in configuration may be necessary. Please
132 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
136 sos added VCD/SVCD support to ata driver and that needs the
137 kernel and burncd to be in sync.
140 The procfs pseudo-filesystem has now been converted to use the
141 pseudofs framework. If you have 'options PROCFS' in your
142 kernel config, you'll need to add 'options PSEUDOFS' if it's
145 This change temporarily breaks truss(1); use ktrace(1) instead
146 until the issue has been resolved.
149 A security hole in OpenSSH involving `UseLogin yes' has been
153 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
154 after this date. You need to do this only once.
157 Most of the awk issues have been resolved. Some rough
158 edges may be left, but for the most part things should be
159 back to "normal." For CURRENT's usual definition of "normal."
162 Awk has been upgraded to the one true awk from bell labs. Expect
163 choppy waves in the upgrade process.
166 The asr driver problem has been resolved.
169 Due to changes in other parts of the system, the asr driver
170 now causes the system to panic on boot. Do not use it pending
171 correction. Comment it out of any kernel config file that you
172 try to use from this date forward.
175 When crossbuilding, use TARGET=xxx where you used to use
176 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
177 unless you are changing both of them. To cross build pc98 on
178 an alpha, for example, you need to set TARGET=pc98 and
182 The kernel interface that burncd depends on has changed.
183 You must recompile both the kernel and userland applications
187 When crossbuilding, please set TARGET_ARCH rather than
188 MACHINE_ARCH to indicate the target. In the future, one will
189 set TARGET_MACHINE where you set MACHINE now. At the moment,
190 setting MACHINE alone for same MACHINE_ARCH machines works
191 (eg, you can build pc98 on a i386 machine and vice versa).
194 Some weird problems result from using ACPI on some machines.
195 To disable ACPI you can add
196 hint.acpi.0.disable="1"
197 to /boot/loader.conf (or by putting set X=Y at the boot
200 Alternatively, you can remove it from /boot/kernel/acpi.ko
201 or use the MODULES_OVERRIDE function in your kernel config
202 file and not list acpi in that list.
205 The buildworld has been fixed. You may need to install
206 the 4.x compatibility libraries for some old binaries
207 to work. Add COMPAT4X=true to your /etc/make.conf to
208 get them installed on every installworld, or execute the
209 following to get them installed only once:
210 cd src/lib/compat/compat4x.<arch>
212 You will see ``__stdoutp undefined'' until you do this.
215 There's a bug in the world build process. The cross-tools
216 are build with the NEW headers, but the OLD libc.a. This
217 leads to all kinds of problems with the new libc. A temporary
219 CFLAGS="-O -pipe -D_OLD_STDIO"
220 before building world when upgrading from 4.x to current. This
221 can be removed afterwards.
223 A proper fix to the buildworld target is needed.
226 Peter has committed his new kthread nfs client/server code.
227 NFS may be unstable after this date.
230 KSE has hit the tree. Lots of things are now different in
231 the kernel. While a few problems were introduced in the
232 initial commit, most of the major ones have been found and
236 In OLDCARD, CardBus bridges appear to be stable. The work
237 arounds described in the 20010604 entry are now no longer
238 necessary and will be ignored. Most insert/remove problems
239 have been rectified around this date.
242 named now runs as user bind and group bind rather than as
243 root. If named_enable is set to YES in /etc/rc.conf, ensure
244 that user bind is available in /etc/passwd (using vipw(8))
245 and that group bind is available in /etc/group. Also make
246 sure that user or group bind has read (and not write)
247 permission for your name server configuration and that it
248 has read and write permission for your slave zone files and
251 If you wish to continue to run named as root (a less secure
252 alternative), add a line to /etc/rc.conf saying
257 The PAM libraries have had an API upgrade that is beyond
258 the ability of the shared library major number to handle.
259 It is manifested by PAM-using ports dumping core. The
260 solution is to rebuild those ports.
263 The kernel compile module has moved from src/sys/compile/FOO
264 to src/sys/${MACHINE}/compile/FOO.
267 The pccard modem issue from 20010613 has been corrected.
268 OLDCARD support is still a little weak in -current. slot 1 is
269 known not to work on some TI based cardbus bridges. Some
270 cardbus bridges do not properly detect insert/removal events.
271 IRQ configuration needs more safety belts.
274 Softupdates problems have been corrected.
277 Peter ripped out the linkerset support. You must, as always,
278 rerun config after you cvsup if you are using the traditional
279 kernel building methods.
282 pccard modems may not work with current after 20010604 date. Some
283 do, others result in panics. *MAKE*SURE* that you update your
284 config and /etc/rc.conf ala the 20010604 entry, or you will have
285 problems (this issue will be fixed, it just hasn't been yet).
288 SOFTUPDATES seem to be broken since the middle of May or so. Do not
289 use them in current. You can disable softupdates on all mounted
290 partitions, or remove SOFTUPDATES the kernel config file.
293 After Peter's commits to the hints code, people have been noticing
294 that certain devices are attached (or try to) twice. This is due
295 to having both static hints as well as a /boot/device.hints. To
296 work around this issue, please use only one or the other mechanism
297 until this bug is fixed.
299 Please note that a feature of config is that if you have config
300 file FOO and FOO.hints, it automatically adds FOO.hints to the
301 hints.c file, wheather you want it to or not.
304 Locale names have changed to match other systems better.
307 pccard support for pci cards has been committed. You must change
308 your /etc/pccard.conf irq lines. It must match the irq used by
309 pcic device. Interrupt storms may result if you fail to do this.
310 Interrupt storms look a lot like a hang.
312 You must also install a new pccardd, otherwise you will get an
313 interrupt storm at card reset time (just after it tells you what
316 pccardd_flags="-I" is necessary for the time being. It tells pccardd
317 not to ask the kernel if the interrupt is really free or not before
318 using it. You can either change the /etc/pccard.conf irq lines to
319 match pcic, or add "-i X" to the pccardd_flags.
322 INSTALL=install -C is being deprecated. If you want to do this,
323 use COPY=-C instead. The former method will be supported for only
324 a limited time. If you see
326 install: warning: the -d and -C options may not be specified together
328 in your makeworld, then you need to migrate towards using
332 It appears that vm is now stable enough to use again. However,
333 there may be other problems, so caution is still urged. alpha
334 definitely is in bad shape.
337 Minor repo damange has happened. This may cause problems
338 with cvsup of ports. If you get errors, please see
339 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
340 at the bottom for details on a workaround. The error message
342 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
345 Vm and/or swapping are busted on -current. Please be patient.
348 pccard has had much reorganizational work done to it over
349 the past few days. Everything should still work, but if
350 not, please contact imp@freebsd.org.
353 ata ioctl changed. Make sure to recompile both kernel and
354 userland at the same time.
357 New ncurses imported.
360 DEVFS is now opt out, not opt in. Barring major problems, this
361 will be the only way to go starting July 1.
364 OpenSSH has been updated to 2.9. Some defaults are different,
365 including RhostsRSAAuthentication, which changes from yes to no.
368 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
371 Building perl was broken at 02:25:25 PDT.
374 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
375 go back in the water.
378 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
379 this date, but before the correction date.
382 old fsck and new kernel interactions appear to have been fixed.
385 fsck and the kernel were changed to handle some optimizations
386 to directory layout. This breaks backward compatibility.
387 Update only if you understand that you must not use the old
388 fsck with the new kernel ever.
391 fsck has changed the meaning of the pass column in /etc/fstab.
392 Please see the cvs commit to fsck.8 or the fsck.8 man page for
393 details. It is unclear if changes to /etc/fstab are necessary.
396 portmap had changed name to rpcbind for maximum POLA in your
397 current world. /etc/hosts.{allow,deny} needs changes. nfs and
398 other rpc based programs that rely on portmapper will not work
399 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
402 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
403 and ATA_ENABEL_TAGS are no longer kernel options. They have
404 been replaced by tunables. See ata.4 for details.
407 The fxp driver was converted to use miibus. If you compile
408 fxp into your kernel statically, you will need to add miibus.
411 The wi device now defaults to BSS (infrastructure) mode
415 /dev/urandom should be a symbolic link to /dev/random now.
416 Users of current not using DEVFS need to run MAKEDEV std.
417 ssh might not work if you don't.
420 The ed driver has been updated. It now allows mii attachments,
421 which means that you must include the miibus in your kernel if
422 you use the ed driver.
425 The problems with libc have been corrected. It is now mostly
426 safe to go back into the water.
429 The size of FILE was changed. This breaks upgrading. If
430 you must upgrade, be prepared for pain. It also breaks almost
431 all binaries that you've compiled on -current. You are warned
432 that before upgrading would be a good time to do a level 0
433 dump of your system. No, really, I mean it this time.
435 To get to the new system, you'll need to use the following
436 workaround. Hopefully this can be sorted out so that we
437 don't have to move this to the updating section.
439 To get around the installworld problem, do:
440 # cd /usr/src/usr.bin/sed
444 If that doesn't work, then try:
445 # make -k installworld
449 DEVFS is now the default. If you use vinum, make sure that you
450 do not include devfs in your kernel as problems result.
453 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
454 Remove them from your config.
457 ****************************** WARNING ******************************
458 buildkernel has been changed slightly
459 ****************************** WARNING ******************************
460 KERNCONF replaces the variable KERNEL for buildkernel. You
461 should update your scripts and make.conf accordingly.
464 config has changed to allow DEV_FOO as a replacement for NFOO.
465 This requires a new config to build correctly.
468 The kerrnel option I386_CPU is now mutually exclusive with the
469 other cpu types. If you have an i386 system, be sure that it
470 only had this line. Remove it for all other configurations.
473 Changes to the kernel require it and burncd be in sync.
476 Everyone who has hw.sndunit set to something in
477 /etc/sysctl.conf, it is now hw.snd.unit.
480 ex and vi were broken by some changes to sys/queue.h. If you
481 have a bad vi, you will see make buildworld fail with a core
482 dump while building termcap. You can work around this problem
483 by adding -k to your make buildworld. This will cause the
484 build to complete and install a new vi. Once that's done, you
485 can rebuild again without the -k to pick up anything that
486 might have been ignored by the -k option.
488 Others have suggested that you can just rebuild libc if your
489 vi/ex is dynamically linked, but I've not received any reports
493 There have been some changes to libcrypt in -current. The
494 libscrypt/libdescrypt symlink sillyness is gone and the installed
495 libcrypt is fully functional. Be aware of this.
498 Linksys Fast Ethernet PCCARD cards supported by the ed driver
499 now require the addition of flag 0x80000 to their config line
500 in pccard.conf(5). This flag is not optional. These Linksys
501 cards will not be recognized without it.
504 Important new FreeBSD-version stuff: PAM support has been worked
505 in, partially from the "Unix" OpenSSH version. This requires
506 adding the following in pam.conf:
508 sshd auth sufficient pam_skey.so
509 sshd auth required pam_unix.so try_first_pass
510 sshd session required pam_permit.so
516 The random device needs more entropy, so you need to make sure
517 that you've run mergemaster to get a /etc/rc which will seed
518 /dev/random. If you don't and the system hangs after ldconfig,
519 then banging on the keyboard randomly until it unhangs is one
523 ****************************** WARNING ******************************
524 Sendmail has been updated.
525 ****************************** WARNING ******************************
526 o mail.local(8) is no longer installed as a set-user-id binary.
527 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
529 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
531 o Now using sendmail's version of vacation(1).
532 o The sendmail cf building tools (contrib/sendmail/cf) are installed
533 in /usr/share/sendmail/cf.
534 o sendmail.cw changed to local-host-names
536 More details can be found at
537 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
540 The ports tree's new layout is in place. Be sure to update
541 your entire ports tree, or you will have problems.
544 The perl build procedure no longer installs miniperl, nor uses
545 the installed miniperl. It is recommended that you delete
549 This weekend the ports tree will be updated to a new layout.
550 It will be in an inconsistent state until noted in the UPDATING
551 file, or with asami-san's message to the relevant mailing
552 lists. With this new layout, you'll need to update the whole
553 tree for anything to work.
556 There was a change in the passwd format. Need more information.
559 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
560 place. Please update boot loader (not the boot blocks) at the
561 same time as your kernel.
564 The new pmtimer device is necessary for laptops. Failure to
565 include the device will cause suspended laptops losing time
566 when they resume. Include
568 in your config file and
569 hint.pmtimer.0.at="isa"
570 to your /boot/device.hints file.
573 The random device has been turned into a (pseudo-)device,
574 rather than an option. The supplied kernel config files have
575 been updated. You will need to do something similar in your
576 own kernel config file.
581 If you prefer to load the loadable module, you need to do
585 The random device module has been renamed from randomdev.ko to
586 random.ko. You will need to edit your /boot/loader.conf to
587 reflect this if you load this module at boot time.
588 The line should read:
592 The SMPNG commit has happened. It should work, but if it
593 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
594 to be a variety of minor issues. Please see 20000905 to make
595 sure you don't have model loading problems which might at
596 first blush appear related to SMP.
599 nsswitch has been imported from NetBSD. Among other things,
600 this means that /etc/host.conf is no longer used. See
601 nsswitch.conf(5) instead. Note that at boot time rc.network
602 will attempt to produce a new nsswitch.conf file for you if you
603 don't have one, and you have host.conf.
606 The ucred structure changed size. This breaks the interface
607 that mountd uses. Trying to use an older mountd with a newer
608 kernel guarantees a panic. This means that you need to use
609 kernels newer than today only with matching mountd, but you
610 needed to do that anyway with the boot loader changes.
613 The boot loader has been updated. The new default kernel is
614 now /boot/kernel/kernel.ko. The new default module location
617 You *MUST* upgrade your boot loader and kernel at the same time.
618 The easiest way to do this is to do the buildworld/buildkernel/
619 installkernel/installworld dance.
621 Furthermore, you are urged to delete your old /modules directory
622 before booting the new kernel, since kldload will find stale
623 modules in that directory instead of finding them in the correct
624 path, /boot/kernel. The most common complaint that this cures
625 is that the linux module crashes your machine after the update.
627 if [ ! -d /boot/kernel.old ]; then
628 mv /modules.old /boot/kernel.old
629 chflags noschg /kernel.old
630 mv /kernel.old /boot/kernel.old/kernel.ko
631 chflags schg /boot/kernel.old/kernel.ko
635 A new issue with the sendmail upgrade has come to light.
636 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
637 incorrectly install the default aliases in /etc/mail rather than
638 move the old one from /etc. So you'll need to manually move the
639 file, create a symbolic link, remove the old /etc/aliases.db and
640 run newaliases. For safety sake, you should stop sendmail
641 while doing this and run the upgrade when locally sourced email
642 is not likely to be generated.
645 /boot/device.hints is now required for installkernel to
646 succeed. You should copy GENERIC.hints for your architecture
647 into /boot/device.hints. If and only if you compile hints
648 into your kernel, then this file may be empty. Please note,
649 if you have an empty or missing /boot/device.hints file and
650 you neglected to compile hints into your kernel, no boot
651 messages will appear after the boot loader tries to start the
655 If you do NOT have ``options RANDOMDEV'' in your kernel and
656 you DO want the random device then add randomdev_load="YES" to
660 suidperl is now always built and installed on the system, but
661 with permissions of 511. If you have applications that use
662 this program, you are now required to add ENABLE_SUIDPERL=true
663 to /etc/make.conf. If you forget to do this,
664 chmod 4511 /usr/bin/suidperl
665 will fix this until the next build.
668 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
669 visible changes that may immediately affect your configuration
671 - New default file locations from src/contrib/sendmail/cf/README
672 - newaliases limited to root and trusted users
673 - MSA port (587) turned on by default
674 - New queue file naming system so can't go from 8.11 -> 8.9
675 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
676 - FEATURE(`nullclient') is more full featured
677 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
678 - mail.local FreeBSD-only -b option changed to -B
679 - See src/contrib/sendmail/RELEASE_NOTES for more info
682 suidperl (aka sperl) is no longer build by default. You must
683 specifically define BUILD_SUIDPERL to "true" for it to be build.
684 Furthermore, we recommend that you remove /usr/bin/sperl* and
685 /usr/bin/suidperl files from your system unless you have a
689 Networking defaults have been tightened. Anybody upgrading
690 /etc/defaults/rc.conf needs to add the following lines to
691 /etc/rc.conf if they want to have the same setup
692 afterwards (unless the variables already are set, of course):
693 # Enable network daemons for user convenience.
696 sendmail_enable="YES"
699 If you have null_load="YES" in your /boot/loader.conf, you
700 will need to change that to nullfs_load="YES".
703 The "installkernel" target has changed slightly. Now even if
704 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
705 it will install the MYKERNEL file (built with the buildkernel
706 target) as /kernel rather than /MYKERNEL. Those who have
707 updated their /boot/loader.conf files to point to /MYKERNEL
708 should remove that entry or perform manual rename of /kernel
712 If you use CVSUP or CTM to get CVS trees, AND you used to get
713 the old crypto files from internat.freebsd.org AND you check
714 out files from the CVS tree with the cvs command, please read
715 http://people.freebsd.org/~imp/internat.txt
716 for details on potential problems that you might have and how
719 If you are merely a mirror, or don't answer yes to each of the
720 clauses above, you needn't worry.
723 /etc/security has been updated to print the inode number of
724 setuid programs that have changed. You will see a large spike
725 in the number of changed programs the first time when you run
726 mergemaster to get a new /etc/security.
729 /dev/random now has good entropy collection (from the keyboard
730 and sysmouse drivers). Please ensure that either `options
731 RANDOMDEV' is present in your kernel config file or that
732 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
733 not have the /dev/random driver, OpenSSL (and consequently
734 lots of crypto tools (like SSH)) will fail with strange
735 errors. (see below, 20000624).
737 FreeBSD-current is safe again to run Crypto.
740 phk made the malloc default options AJ. This may slow things
741 down and uncover other latent bugs in the code. If you need to
742 run at full speed, you can disable this by doing the following:
743 ln -s aj /etc/malloc.conf
746 libftpio's version was accidentally bumped a few days ago. This
747 has been corrected. You may need to remove /usr/lib/libftpio.so.6
748 before doing your next buildworld/installworld pair. It certainly
749 won't hurt to remove it before the update procedure. It will
750 break fetch until a new one is built, but ftp can be used in the
754 The crypto packages have changed for the cvsup. This has been done
755 in a backward compatible way, but the old packages will go away at
756 some point in the future. Look at /usr/share/examples/cvsup for
760 With the new sys/modules/sound/drivers/*, you will need to
761 set SYSDIR until you do an installworld after July 7th.
764 rc.shutdown and rc will now call the rc.d scripts with start
765 or stop. This may cause some harmless warnings from older
766 rc.d scripts that haven't been updated.
769 The libfetch based version of fetch has gone into the tree.
770 Minor problems may result on some of the less popular sites,
771 which should be reported to des@freebsd.org.
774 From approximately this date forward, one must have the crypto
775 system installed in order to build the system and kernel.
776 While not technically strictly true, one should treat it as
777 required and grab the crypto bits. If you are grabbing CVS
778 trees, src-all and cvs-crypto should be treated as if they
779 were required. You should check with the latest collections
780 to make sure that these haven't changed.
783 Mark Murray just committed the first parts of a cleanup of
784 /dev/zero, et al. This is also cleaning up /dev/random.
785 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
786 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
787 until Mark can merge in the fixes to this work in progress.
788 openssh and openssl should not be used to generate keys from this
789 date to the completion of the work.
791 If you must operate at this reduced level of security, add '
792 options RANDOMDEV' to your kernel or modload the randomdev
793 module. You may also need to copy a new MAKEDEV to /dev and
794 recreate the random and urandom devices.
797 The license on the softupdates is now a standard 2 clause
798 BSD license. You may need to remove your symbolic links
799 that used to be required when updating.
802 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
803 the config file update procedure.
804 http://people.freebsd.org/~imp/config-upd.html
805 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
806 isn't buildable. However, you can generate a LINT file.
809 Binutils 2.10 have hit the tree, or will shortly. As soon
810 as they do, the problem noted in 20000522 will be resolved and
811 that workaround will no longer be required.
814 phk removed the compatibility creation of wd devices in the
815 ad driver. If you haven't done so already, you must update
816 your fstab, etc to use the ad devices instead of the wd
819 In addition, you'll need to update your boot blocks to a
820 more modern version, if you haven't already done so. Modern
821 here means 4.0 release or newer (although older releases
825 Peter took an axe to config(8). Be sure that you read his mail
826 on the topic before even thinking about updating. You will
827 need to create a /boot/device.hints or add a hints directive
828 to your config file to compile them in statically. The format
829 of the config file has changed as well. Please see GENERIC or
830 NEWCARD for examples of the new format.
832 Indirectly, this also breaks USERCONFIG. Unless a newer entry
833 says that it has been fixed, assume that must use the hints mechanism
834 in the loader if you need to use a machine with very old ISA cards
838 A new set of binutils went into the tree today. Anybody
839 building a kernel after this point is advised that they need
840 to rebuild their binutils (or better yet do a
841 buildworld/installworld) before building a new kernel.
843 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
844 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
845 is recommended that you don't set this option until the problem
849 The ethernet drivers were all updated to clean up the BPF handling.
852 The problems with boot blocks on the alphas have been corrected.
853 This will require some care in updating alphas. A new libstand
854 is requires for the boot blocks to build properly.
857 Recompile all kld modules. Proper version dependency info
861 Modules have been disconnected from the buildworld tree and
862 connected to the kernel building instead.
865 You may need to build gperf
866 cd /usr/src/gnu/usr.bin/gperf && make depend all install
867 when upgrading from 4.0 -> current. The build system now uses
868 an option only in -current.
871 The method that we brand ELF binaries has changed to be more
872 acceptable to the binutils maintainers. You will need to
873 rebrand your ELF binaries that aren't native. One problem
874 binary is the Linux ldconfig. After your make world, but
875 before you reboot, you'll need to issue:
876 brandelf -t Linux /compat/linux/sbin/ldconfig
877 if you have Linux compatibility enabled on your machine.
880 If you have really bad/marginal IDE drives, you may find they
881 don't work well. Use pio mode instead. The easiest way to
882 cope if you have a problem combination is to add:
883 /sbin/sysctl hw.ata.ata_dma=0
884 to the start of /etc/rc.conf.
887 The ISA and PCI compatibility shims have been connected to the
888 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
889 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
890 include the appropriate option in your kernel config. Drivers
891 using the shims should be updated or they won't ship with
892 5.0-RELEASE, targeted for 2001.
895 We've entered the traditional post release dumping party.
896 Large kernel changes are being committed and are in the
897 works. It is important to keep the systems' klds and kernel
898 in sync as kernel interfaces and structures are changing.
899 Before reporting kernel panics, make sure that all modules
900 that you are loading are up to date.
903 If you are upgrading from an older version of FreeBSD, you
904 need to update your boot blocks as well. 'disklabel -B ad0'
905 will do the trick. This isn't critical until you remove your
906 wd device entries in /dev, at which point your system will not
910 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
911 to upgrade to 4.0 from 3.x.
917 Avoid using make -j when upgrading. From time to time in the
918 past there have been problems using -j with buildworld and/or
919 installworld. This is especially true when upgrading between
920 "distant" versions (eg one that cross a major release boundary
921 or several minor releases, or when several months have passed
922 on the -current branch).
924 Sometimes, obscure build problems are the result of environment
925 poisoning. This can happen because the make utility reads its
926 environment when searching for values for global variables.
927 To run your build attempts in an "environmental clean room",
928 prefix all make commands with 'env -i '. See the env(1) manual
929 page for more details.
933 If you are updating from a prior version of FreeBSD (even one just
934 a few days old), you should follow this procedure. With a
935 /usr/obj tree with a fresh buildworld,
936 make buildkernel KERNCONF=YOUR_KERNEL_HERE
937 make installkernel KERNCONF=YOUR_KERNEL_HERE
939 To just build a kernel when you know that it won't mess you up
940 --------------------------------------------------------------
941 cd src/sys/{i386,alpha}/conf
942 config KERNEL_NAME_HERE
943 cd ../../compile/KERNEL_NAME_HERE
948 If this fails, go to the "To build a kernel" section.
950 To rebuild everything and install it on the current system.
951 -----------------------------------------------------------
953 Build a new kernel, see above.
955 To upgrade from 4.x-stable to current
956 -------------------------------------
958 make buildkernel KERNCONF=YOUR_KERNEL_HERE
959 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
960 make installkernel KERNCONF=YOUR_KERNEL_HERE
961 reboot in single user [3]
968 Make sure that you've read the UPDATING file to understand the
969 tweaks to various things you need. At this point in the life
970 cycle of current, things change often and you are on your own
971 to cope. The defaults can also change, so please read ALL of
972 the UPDATING entries.
974 Also, if you are tracking -current, you must be subscribed to
975 freebsd-current@freebsd.org. Make sure that before you update
976 your sources that you have read and understood all the recent
977 messages there. If in doubt, please track -stable which has
980 [1] If you have third party modules, such as vmware, you
981 should disable them at this point so they don't crash your
984 [2] If you have legacy ISA devices, you may need to create
985 your own device.hints to reflect your unique hardware
988 [3] From the bootblocks, boot -s, and then do
993 adjkerntz -i # if CMOS is wall time
994 Also, when doing a major release upgrade, it is required that
995 you boot into single user mode to do the installworld.
997 [4] Note: This step is non-optional. Failure to do this step
998 can result in a significant reduction in the functionality of the
999 system. Attempting to do it by hand is not recommended and those
1000 that pursue this avenue should read this file carefully, as well
1001 as the archives of freebsd-current and freebsd-hackers mailing lists
1002 for potential gotchas.
1004 [5] Usually this step is a noop. However, from time to time
1005 you may need to do this if you get unknown user in the following
1006 step. It never hurts to do it all the time. You may need to
1007 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1008 install) after the buildworld before this step if you last updated
1009 from current before 20020224 or from -stable before 20020408.
1013 This file contains a list, in reverse chronological order, of major
1014 breakages in tracking -current. Not all things will be listed here,
1015 and it only starts on March 15, 2000. Updating files can found in
1016 previous releases if your system is older than this.
1018 Copyright information:
1020 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1022 Redistribution, publication, translation and use, with or without
1023 modification, in full or in part, in any form or format of this
1024 document are permitted without further permission from the author.
1026 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1027 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1028 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1029 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1030 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1031 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1032 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1033 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1034 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1035 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1036 POSSIBILITY OF SUCH DAMAGE.
1038 If you find this document useful, and you want to, you may buy the
1041 Contact Warner Losh if you have any questions about your use of