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 When exec'ing set[ug]id executables, the kernel now ensures that the
27 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
30 New sendmail startup scripts have been installed to make it
31 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
32 variable sendmail_enable to "NO" no longer prevents any sendmail
33 daemons from starting. Instead, either set sendmail_enable to
34 "NONE" or change mta_start_script to a script for starting
35 an alternative MTA. Setting mta_start_script to "" will
36 also prevent any MTA from being started at boot.
39 UCONSOLE is no longer a valid kernel option.
42 FreeBSD 5.0 DP-1 was basically branched today.
45 Warnings are now errors in the kernel. Unless you are a developer,
46 you should add -DNO_WERROR to your make line.
49 sendmail 8.12.2 has been imported. The sendmail binary is no
50 longer a set-user-ID root binary and the infrastructure to support
51 command line mail submission has changed. Be sure to run
52 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
53 and /etc/mail) and read /etc/mail/README for more details.
55 Due to the import of sendmail 8.12.2, a new user and group are
56 required in order for sendmail to run as a set-group-ID
57 binary. A 'make installworld' will use the new user and group
58 to set the owner and group of /var/spool/clientmqueue and will
59 fail if the new user and group do not exist. The 'smmsp' user
60 and group must be merged from src/etc/group and
61 src/etc/master.passwd before using 'make installworld'.
62 'mergemaster -p' will do this. You may need to install
63 mergemaster before this will work if you are updating from a
64 very old version of current. The updating recipe has changed
68 The preferred configuration method for PAM is now /etc/pam.d/
69 rather than /etc/pam.conf. If you have an unmodified
70 pam.conf, just delete it after your next mergemaster run. If
71 you have local modifications, you can use
72 /usr/src/etc/pam.d/convert.pl to incorporate them into your
75 Please see the following url for more details:
76 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
78 If anyone here is already using the new rc.conf(5) variable
79 networkfs_types, please note that it has changed
80 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
83 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
84 started out its life in the ISDN4BSD project as an offspring
85 from sys/net/if_spppsubr.c, which eventually got a life of its
86 own. All the accumulated features and bugfixes of the i4b
87 version have now been merged back into the base system's
88 version now. The only user-visible change resulting from this
89 is that i4b's sppp(4) interfaces are to be managed with
90 spppcontrol(8) again, since ispppcontrol(8) has been retired
91 as well. (There has never been rc file support for
92 ispppcontrol in -current, but only in -stable. That will be
93 reverted by the time the changes are MFCed.)
96 The fdc(4) driver has been updated and now automatically
97 recognizes media in `standard' formats (like 1440 KB and
98 720 KB for a 3.5" high-density drive) when accessing the
99 default device node (e. g. /dev/fd0). The old variety of
100 floppy device nodes /dev/fd*.* is no longer present by
101 default, devices can be created (in DEVFS) on demand. They
102 will need to be customized then for `odd' densities using
106 The bugs in procfs' debugging support code have been fixed,
107 and truss(1) now works again.
110 Daily security checks have been split out to use the periodic(8)
111 scripts. Some change in configuration may be necessary. Please
113 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
117 sos added VCD/SVCD support to ata driver and that needs the
118 kernel and burncd to be in sync.
121 The procfs pseudo-filesystem has now been converted to use the
122 pseudofs framework. If you have 'options PROCFS' in your
123 kernel config, you'll need to add 'options PSEUDOFS' if it's
126 This change temporarily breaks truss(1); use ktrace(1) instead
127 until the issue has been resolved.
130 A security hole in OpenSSH involving `UseLogin yes' has been
134 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
135 after this date. You need to do this only once.
138 Most of the awk issues have been resolved. Some rough
139 edges may be left, but for the most part things should be
140 back to "normal." For CURRENT's usual definition of "normal."
143 Awk has been upgraded to the one true awk from bell labs. Expect
144 choppy waves in the upgrade process.
147 The asr driver problem has been resolved.
150 Due to changes in other parts of the system, the asr driver
151 now causes the system to panic on boot. Do not use it pending
152 correction. Comment it out of any kernel config file that you
153 try to use from this date forward.
156 When crossbuilding, use TARGET=xxx where you used to use
157 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
158 unless you are changing both of them. To cross build pc98 on
159 an alpha, for example, you need to set TARGET=pc98 and
163 The kernel interface that burncd depends on has changed.
164 You must recompile both the kernel and userland applications
168 When crossbuilding, please set TARGET_ARCH rather than
169 MACHINE_ARCH to indicate the target. In the future, one will
170 set TARGET_MACHINE where you set MACHINE now. At the moment,
171 setting MACHINE alone for same MACHINE_ARCH machines works
172 (eg, you can build pc98 on a i386 machine and vice versa).
175 Some weird problems result from using ACPI on some machines.
176 To disable ACPI you can add
177 hint.acpi.0.disable="1"
178 to /boot/loader.conf (or by putting set X=Y at the boot
181 Alternatively, you can remove it from /boot/kernel/acpi.ko
182 or use the MODULES_OVERRIDE function in your kernel config
183 file and not list acpi in that list.
186 The buildworld has been fixed. You may need to install
187 the 4.x compatibility libraries for some old binaries
188 to work. Add COMPAT4X=true to your /etc/make.conf to
189 get them installed on every installworld, or execute the
190 following to get them installed only once:
191 cd src/lib/compat/compat4x.<arch>
193 You will see ``__stdoutp undefined'' until you do this.
196 There's a bug in the world build process. The cross-tools
197 are build with the NEW headers, but the OLD libc.a. This
198 leads to all kinds of problems with the new libc. A temporary
200 CFLAGS="-O -pipe -D_OLD_STDIO"
201 before building world when upgrading from 4.x to current. This
202 can be removed afterwards.
204 A proper fix to the buildworld target is needed.
207 Peter has committed his new kthread nfs client/server code.
208 NFS may be unstable after this date.
211 KSE has hit the tree. Lots of things are now different in
212 the kernel. While a few problems were introduced in the
213 initial commit, most of the major ones have been found and
217 In OLDCARD, CardBus bridges appear to be stable. The work
218 arounds described in the 20010604 entry are now no longer
219 necessary and will be ignored. Most insert/remove problems
220 have been rectified around this date.
223 named now runs as user bind and group bind rather than as
224 root. If named_enable is set to YES in /etc/rc.conf, ensure
225 that user bind is available in /etc/passwd (using vipw(8))
226 and that group bind is available in /etc/group. Also make
227 sure that user or group bind has read (and not write)
228 permission for your name server configuration and that it
229 has read and write permission for your slave zone files and
232 If you wish to continue to run named as root (a less secure
233 alternative), add a line to /etc/rc.conf saying
238 The PAM libraries have had an API upgrade that is beyond
239 the ability of the shared library major number to handle.
240 It is manifested by PAM-using ports dumping core. The
241 solution is to rebuild those ports.
244 The kernel compile module has moved from src/sys/compile/FOO
245 to src/sys/${MACHINE}/compile/FOO.
248 The pccard modem issue from 20010613 has been corrected.
249 OLDCARD support is still a little weak in -current. slot 1 is
250 known not to work on some TI based cardbus bridges. Some
251 cardbus bridges do not properly detect insert/removal events.
252 IRQ configuration needs more safety belts.
255 Softupdates problems have been corrected.
258 Peter ripped out the linkerset support. You must, as always,
259 rerun config after you cvsup if you are using the traditional
260 kernel building methods.
263 pccard modems may not work with current after 20010604 date. Some
264 do, others result in panics. *MAKE*SURE* that you update your
265 config and /etc/rc.conf ala the 20010604 entry, or you will have
266 problems (this issue will be fixed, it just hasn't been yet).
269 SOFTUPDATES seem to be broken since the middle of May or so. Do not
270 use them in current. You can disable softupdates on all mounted
271 partitions, or remove SOFTUPDATES the kernel config file.
274 After Peter's commits to the hints code, people have been noticing
275 that certain devices are attached (or try to) twice. This is due
276 to having both static hints as well as a /boot/device.hints. To
277 work around this issue, please use only one or the other mechanism
278 until this bug is fixed.
280 Please note that a feature of config is that if you have config
281 file FOO and FOO.hints, it automatically adds FOO.hints to the
282 hints.c file, wheather you want it to or not.
285 Locale names have changed to match other systems better.
288 pccard support for pci cards has been committed. You must change
289 your /etc/pccard.conf irq lines. It must match the irq used by
290 pcic device. Interrupt storms may result if you fail to do this.
291 Interrupt storms look a lot like a hang.
293 You must also install a new pccardd, otherwise you will get an
294 interrupt storm at card reset time (just after it tells you what
297 pccardd_flags="-I" is necessary for the time being. It tells pccardd
298 not to ask the kernel if the interrupt is really free or not before
299 using it. You can either change the /etc/pccard.conf irq lines to
300 match pcic, or add "-i X" to the pccardd_flags.
303 INSTALL=install -C is being deprecated. If you want to do this,
304 use COPY=-C instead. The former method will be supported for only
305 a limited time. If you see
307 install: warning: the -d and -C options may not be specified together
309 in your makeworld, then you need to migrate towards using
313 It appears that vm is now stable enough to use again. However,
314 there may be other problems, so caution is still urged. alpha
315 definitely is in bad shape.
318 Minor repo damange has happened. This may cause problems
319 with cvsup of ports. If you get errors, please see
320 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
321 at the bottom for details on a workaround. The error message
323 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
326 Vm and/or swapping are busted on -current. Please be patient.
329 pccard has had much reorganizational work done to it over
330 the past few days. Everything should still work, but if
331 not, please contact imp@freebsd.org.
334 ata ioctl changed. Make sure to recompile both kernel and
335 userland at the same time.
338 New ncurses imported.
341 DEVFS is now opt out, not opt in. Barring major problems, this
342 will be the only way to go starting July 1.
345 OpenSSH has been updated to 2.9. Some defaults are different,
346 including RhostsRSAAuthentication, which changes from yes to no.
349 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
352 Building perl was broken at 02:25:25 PDT.
355 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
356 go back in the water.
359 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
360 this date, but before the correction date.
363 old fsck and new kernel interactions appear to have been fixed.
366 fsck and the kernel were changed to handle some optimizations
367 to directory layout. This breaks backward compatibility.
368 Update only if you understand that you must not use the old
369 fsck with the new kernel ever.
372 fsck has changed the meaning of the pass column in /etc/fstab.
373 Please see the cvs commit to fsck.8 or the fsck.8 man page for
374 details. It is unclear if changes to /etc/fstab are necessary.
377 portmap had changed name to rpcbind for maximum POLA in your
378 current world. /etc/hosts.{allow,deny} needs changes. nfs and
379 other rpc based programs that rely on portmapper will not work
380 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
383 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
384 and ATA_ENABEL_TAGS are no longer kernel options. They have
385 been replaced by tunables. See ata.4 for details.
388 The fxp driver was converted to use miibus. If you compile
389 fxp into your kernel statically, you will need to add miibus.
392 The wi device now defaults to BSS (infrastructure) mode
396 /dev/urandom should be a symbolic link to /dev/random now.
397 Users of current not using DEVFS need to run MAKEDEV std.
398 ssh might not work if you don't.
401 The ed driver has been updated. It now allows mii attachments,
402 which means that you must include the miibus in your kernel if
403 you use the ed driver.
406 The problems with libc have been corrected. It is now mostly
407 safe to go back into the water.
410 The size of FILE was changed. This breaks upgrading. If
411 you must upgrade, be prepared for pain. It also breaks almost
412 all binaries that you've compiled on -current. You are warned
413 that before upgrading would be a good time to do a level 0
414 dump of your system. No, really, I mean it this time.
416 To get to the new system, you'll need to use the following
417 workaround. Hopefully this can be sorted out so that we
418 don't have to move this to the updating section.
420 To get around the installworld problem, do:
421 # cd /usr/src/usr.bin/sed
425 If that doesn't work, then try:
426 # make -k installworld
430 DEVFS is now the default. If you use vinum, make sure that you
431 do not include devfs in your kernel as problems result.
434 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
435 Remove them from your config.
438 ****************************** WARNING ******************************
439 buildkernel has been changed slightly
440 ****************************** WARNING ******************************
441 KERNCONF replaces the variable KERNEL for buildkernel. You
442 should update your scripts and make.conf accordingly.
445 config has changed to allow DEV_FOO as a replacement for NFOO.
446 This requires a new config to build correctly.
449 The kerrnel option I386_CPU is now mutually exclusive with the
450 other cpu types. If you have an i386 system, be sure that it
451 only had this line. Remove it for all other configurations.
454 Changes to the kernel require it and burncd be in sync.
457 Everyone who has hw.sndunit set to something in
458 /etc/sysctl.conf, it is now hw.snd.unit.
461 ex and vi were broken by some changes to sys/queue.h. If you
462 have a bad vi, you will see make buildworld fail with a core
463 dump while building termcap. You can work around this problem
464 by adding -k to your make buildworld. This will cause the
465 build to complete and install a new vi. Once that's done, you
466 can rebuild again without the -k to pick up anything that
467 might have been ignored by the -k option.
469 Others have suggested that you can just rebuild libc if your
470 vi/ex is dynamically linked, but I've not received any reports
474 There have been some changes to libcrypt in -current. The
475 libscrypt/libdescrypt symlink sillyness is gone and the installed
476 libcrypt is fully functional. Be aware of this.
479 Linksys Fast Ethernet PCCARD cards supported by the ed driver
480 now require the addition of flag 0x80000 to their config line
481 in pccard.conf(5). This flag is not optional. These Linksys
482 cards will not be recognized without it.
485 Important new FreeBSD-version stuff: PAM support has been worked
486 in, partially from the "Unix" OpenSSH version. This requires
487 adding the following in pam.conf:
489 sshd auth sufficient pam_skey.so
490 sshd auth required pam_unix.so try_first_pass
491 sshd session required pam_permit.so
497 The random device needs more entropy, so you need to make sure
498 that you've run mergemaster to get a /etc/rc which will seed
499 /dev/random. If you don't and the system hangs after ldconfig,
500 then banging on the keyboard randomly until it unhangs is one
504 ****************************** WARNING ******************************
505 Sendmail has been updated.
506 ****************************** WARNING ******************************
507 o mail.local(8) is no longer installed as a set-user-id binary.
508 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
510 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
512 o Now using sendmail's version of vacation(1).
513 o The sendmail cf building tools (contrib/sendmail/cf) are installed
514 in /usr/share/sendmail/cf.
515 o sendmail.cw changed to local-host-names
517 More details can be found at
518 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
521 The ports tree's new layout is in place. Be sure to update
522 your entire ports tree, or you will have problems.
525 The perl build procedure no longer installs miniperl, nor uses
526 the installed miniperl. It is recommended that you delete
530 This weekend the ports tree will be updated to a new layout.
531 It will be in an inconsistent state until noted in the UPDATING
532 file, or with asami-san's message to the relevant mailing
533 lists. With this new layout, you'll need to update the whole
534 tree for anything to work.
537 There was a change in the passwd format. Need more information.
540 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
541 place. Please update boot loader (not the boot blocks) at the
542 same time as your kernel.
545 The new pmtimer device is necessary for laptops. Failure to
546 include the device will cause suspended laptops losing time
547 when they resume. Include
549 in your config file and
550 hint.pmtimer.0.at="isa"
551 to your /boot/device.hints file.
554 The random device has been turned into a (pseudo-)device,
555 rather than an option. The supplied kernel config files have
556 been updated. You will need to do something similar in your
557 own kernel config file.
562 If you prefer to load the loadable module, you need to do
566 The random device module has been renamed from randomdev.ko to
567 random.ko. You will need to edit your /boot/loader.conf to
568 reflect this if you load this module at boot time.
569 The line should read:
573 The SMPNG commit has happened. It should work, but if it
574 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
575 to be a variety of minor issues. Please see 20000905 to make
576 sure you don't have model loading problems which might at
577 first blush appear related to SMP.
580 nsswitch has been imported from NetBSD. Among other things,
581 this means that /etc/host.conf is no longer used. See
582 nsswitch.conf(5) instead. Note that at boot time rc.network
583 will attempt to produce a new nsswitch.conf file for you if you
584 don't have one, and you have host.conf.
587 The ucred structure changed size. This breaks the interface
588 that mountd uses. Trying to use an older mountd with a newer
589 kernel guarantees a panic. This means that you need to use
590 kernels newer than today only with matching mountd, but you
591 needed to do that anyway with the boot loader changes.
594 The boot loader has been updated. The new default kernel is
595 now /boot/kernel/kernel.ko. The new default module location
598 You *MUST* upgrade your boot loader and kernel at the same time.
599 The easiest way to do this is to do the buildworld/buildkernel/
600 installkernel/installworld dance.
602 Furthermore, you are urged to delete your old /modules directory
603 before booting the new kernel, since kldload will find stale
604 modules in that directory instead of finding them in the correct
605 path, /boot/kernel. The most common complaint that this cures
606 is that the linux module crashes your machine after the update.
608 if [ ! -d /boot/kernel.old ]; then
609 mv /modules.old /boot/kernel.old
610 chflags noschg /kernel.old
611 mv /kernel.old /boot/kernel.old/kernel.ko
612 chflags schg /boot/kernel.old/kernel.ko
616 A new issue with the sendmail upgrade has come to light.
617 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
618 incorrectly install the default aliases in /etc/mail rather than
619 move the old one from /etc. So you'll need to manually move the
620 file, create a symbolic link, remove the old /etc/aliases.db and
621 run newaliases. For safety sake, you should stop sendmail
622 while doing this and run the upgrade when locally sourced email
623 is not likely to be generated.
626 /boot/device.hints is now required for installkernel to
627 succeed. You should copy GENERIC.hints for your architecture
628 into /boot/device.hints. If and only if you compile hints
629 into your kernel, then this file may be empty. Please note,
630 if you have an empty or missing /boot/device.hints file and
631 you neglected to compile hints into your kernel, no boot
632 messages will appear after the boot loader tries to start the
636 If you do NOT have ``options RANDOMDEV'' in your kernel and
637 you DO want the random device then add randomdev_load="YES" to
641 suidperl is now always built and installed on the system, but
642 with permissions of 511. If you have applications that use
643 this program, you are now required to add ENABLE_SUIDPERL=true
644 to /etc/make.conf. If you forget to do this,
645 chmod 4511 /usr/bin/suidperl
646 will fix this until the next build.
649 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
650 visible changes that may immediately affect your configuration
652 - New default file locations from src/contrib/sendmail/cf/README
653 - newaliases limited to root and trusted users
654 - MSA port (587) turned on by default
655 - New queue file naming system so can't go from 8.11 -> 8.9
656 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
657 - FEATURE(`nullclient') is more full featured
658 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
659 - mail.local FreeBSD-only -b option changed to -B
660 - See src/contrib/sendmail/RELEASE_NOTES for more info
663 suidperl (aka sperl) is no longer build by default. You must
664 specifically define BUILD_SUIDPERL to "true" for it to be build.
665 Furthermore, we recommend that you remove /usr/bin/sperl* and
666 /usr/bin/suidperl files from your system unless you have a
670 Networking defaults have been tightened. Anybody upgrading
671 /etc/defaults/rc.conf needs to add the following lines to
672 /etc/rc.conf if they want to have the same setup
673 afterwards (unless the variables already are set, of course):
674 # Enable network daemons for user convenience.
677 sendmail_enable="YES"
680 If you have null_load="YES" in your /boot/loader.conf, you
681 will need to change that to nullfs_load="YES".
684 The "installkernel" target has changed slightly. Now even if
685 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
686 it will install the MYKERNEL file (built with the buildkernel
687 target) as /kernel rather than /MYKERNEL. Those who have
688 updated their /boot/loader.conf files to point to /MYKERNEL
689 should remove that entry or perform manual rename of /kernel
693 If you use CVSUP or CTM to get CVS trees, AND you used to get
694 the old crypto files from internat.freebsd.org AND you check
695 out files from the CVS tree with the cvs command, please read
696 http://people.freebsd.org/~imp/internat.txt
697 for details on potential problems that you might have and how
700 If you are merely a mirror, or don't answer yes to each of the
701 clauses above, you needn't worry.
704 /etc/security has been updated to print the inode number of
705 setuid programs that have changed. You will see a large spike
706 in the number of changed programs the first time when you run
707 mergemaster to get a new /etc/security.
710 /dev/random now has good entropy collection (from the keyboard
711 and sysmouse drivers). Please ensure that either `options
712 RANDOMDEV' is present in your kernel config file or that
713 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
714 not have the /dev/random driver, OpenSSL (and consequently
715 lots of crypto tools (like SSH)) will fail with strange
716 errors. (see below, 20000624).
718 FreeBSD-current is safe again to run Crypto.
721 phk made the malloc default options AJ. This may slow things
722 down and uncover other latent bugs in the code. If you need to
723 run at full speed, you can disable this by doing the following:
724 ln -s aj /etc/malloc.conf
727 libftpio's version was accidentally bumped a few days ago. This
728 has been corrected. You may need to remove /usr/lib/libftpio.so.6
729 before doing your next buildworld/installworld pair. It certainly
730 won't hurt to remove it before the update procedure. It will
731 break fetch until a new one is built, but ftp can be used in the
735 The crypto packages have changed for the cvsup. This has been done
736 in a backward compatible way, but the old packages will go away at
737 some point in the future. Look at /usr/share/examples/cvsup for
741 With the new sys/modules/sound/drivers/*, you will need to
742 set SYSDIR until you do an installworld after July 7th.
745 rc.shutdown and rc will now call the rc.d scripts with start
746 or stop. This may cause some harmless warnings from older
747 rc.d scripts that haven't been updated.
750 The libfetch based version of fetch has gone into the tree.
751 Minor problems may result on some of the less popular sites,
752 which should be reported to des@freebsd.org.
755 From approximately this date forward, one must have the crypto
756 system installed in order to build the system and kernel.
757 While not technically strictly true, one should treat it as
758 required and grab the crypto bits. If you are grabbing CVS
759 trees, src-all and cvs-crypto should be treated as if they
760 were required. You should check with the latest collections
761 to make sure that these haven't changed.
764 Mark Murray just committed the first parts of a cleanup of
765 /dev/zero, et al. This is also cleaning up /dev/random.
766 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
767 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
768 until Mark can merge in the fixes to this work in progress.
769 openssh and openssl should not be used to generate keys from this
770 date to the completion of the work.
772 If you must operate at this reduced level of security, add '
773 options RANDOMDEV' to your kernel or modload the randomdev
774 module. You may also need to copy a new MAKEDEV to /dev and
775 recreate the random and urandom devices.
778 The license on the softupdates is now a standard 2 clause
779 BSD license. You may need to remove your symbolic links
780 that used to be required when updating.
783 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
784 the config file update procedure.
785 http://people.freebsd.org/~imp/config-upd.html
786 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
787 isn't buildable. However, you can generate a LINT file.
790 Binutils 2.10 have hit the tree, or will shortly. As soon
791 as they do, the problem noted in 20000522 will be resolved and
792 that workaround will no longer be required.
795 phk removed the compatibility creation of wd devices in the
796 ad driver. If you haven't done so already, you must update
797 your fstab, etc to use the ad devices instead of the wd
800 In addition, you'll need to update your boot blocks to a
801 more modern version, if you haven't already done so. Modern
802 here means 4.0 release or newer (although older releases
806 Peter took an axe to config(8). Be sure that you read his mail
807 on the topic before even thinking about updating. You will
808 need to create a /boot/device.hints or add a hints directive
809 to your config file to compile them in statically. The format
810 of the config file has changed as well. Please see GENERIC or
811 NEWCARD for examples of the new format.
813 Indirectly, this also breaks USERCONFIG. Unless a newer entry
814 says that it has been fixed, assume that must use the hints mechanism
815 in the loader if you need to use a machine with very old ISA cards
819 A new set of binutils went into the tree today. Anybody
820 building a kernel after this point is advised that they need
821 to rebuild their binutils (or better yet do a
822 buildworld/installworld) before building a new kernel.
824 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
825 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
826 is recommended that you don't set this option until the problem
830 The ethernet drivers were all updated to clean up the BPF handling.
833 The problems with boot blocks on the alphas have been corrected.
834 This will require some care in updating alphas. A new libstand
835 is requires for the boot blocks to build properly.
838 Recompile all kld modules. Proper version dependency info
842 Modules have been disconnected from the buildworld tree and
843 connected to the kernel building instead.
846 You may need to build gperf
847 cd /usr/src/gnu/usr.bin/gperf && make depend all install
848 when upgrading from 4.0 -> current. The build system now uses
849 an option only in -current.
852 The method that we brand ELF binaries has changed to be more
853 acceptable to the binutils maintainers. You will need to
854 rebrand your ELF binaries that aren't native. One problem
855 binary is the Linux ldconfig. After your make world, but
856 before you reboot, you'll need to issue:
857 brandelf -t Linux /compat/linux/sbin/ldconfig
858 if you have Linux compatibility enabled on your machine.
861 If you have really bad/marginal IDE drives, you may find they
862 don't work well. Use pio mode instead. The easiest way to
863 cope if you have a problem combination is to add:
864 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
865 to the start of /etc/rc.conf.
868 The ISA and PCI compatibility shims have been connected to the
869 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
870 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
871 include the appropriate option in your kernel config. Drivers
872 using the shims should be updated or they won't ship with
873 5.0-RELEASE, targeted for 2001.
876 We've entered the traditional post release dumping party.
877 Large kernel changes are being committed and are in the
878 works. It is important to keep the systems' klds and kernel
879 in sync as kernel interfaces and structures are changing.
880 Before reporting kernel panics, make sure that all modules
881 that you are loading are up to date.
884 If you are upgrading from an older version of FreeBSD, you
885 need to update your boot blocks as well. 'disklabel -B ad0'
886 will do the trick. This isn't critical until you remove your
887 wd device entries in /dev, at which point your system will not
891 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
892 to upgrade to 4.0 from 3.x.
898 Avoid using make -j when upgrading. From time to time in the
899 past there have been problems using -j with buildworld and/or
900 installworld. This is especially true when upgrading between
901 "distant" versions (eg one that cross a major release boundary
902 or several minor releases, or when several months have passed
903 on the -current branch).
905 Sometimes, obscure build problems are the result of environment
906 poisoning. This can happen because the make utility reads its
907 environment when searching for values for global variables.
908 To run your build attempts in an "environmental clean room",
909 prefix all make commands with 'env -i '. See the env(1) manual
910 page for more details.
914 If you are updating from a prior version of FreeBSD (even one just
915 a few days old), you should follow this procedure. With a
916 /usr/obj tree with a fresh buildworld,
917 make buildkernel KERNCONF=YOUR_KERNEL_HERE
918 make installkernel KERNCONF=YOUR_KERNEL_HERE
920 To just build a kernel when you know that it won't mess you up
921 --------------------------------------------------------------
922 cd src/sys/{i386,alpha}/conf
923 config KERNEL_NAME_HERE
924 cd ../../compile/KERNEL_NAME_HERE
929 If this fails, go to the "To build a kernel" section.
931 To rebuild everything and install it on the current system.
932 -----------------------------------------------------------
934 Build a new kernel, see above.
936 To upgrade from 4.x-stable to current
937 -------------------------------------
939 make buildkernel KERNCONF=YOUR_KERNEL_HERE
940 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
941 make installkernel KERNCONF=YOUR_KERNEL_HERE [6]
942 reboot in single user [3]
949 Make sure that you've read the UPDATING file to understand the
950 tweaks to various things you need. At this point in the life
951 cycle of current, things change often and you are on your own
952 to cope. The defaults can also change, so please read ALL of
953 the UPDATING entries.
955 Also, if you are tracking -current, you must be subscribed to
956 freebsd-current@freebsd.org. Make sure that before you update
957 your sources that you have read and understood all the recent
958 messages there. If in doubt, please track -stable which has
961 [1] If you have third party modules, such as vmware, you
962 should disable them at this point so they don't crash your
965 [2] If you have legacy ISA devices, you may need to create
966 your own device.hints to reflect your unique hardware
969 [3] From the bootblocks, boot -s, and then do
974 adjkerntz -i # if CMOS is wall time
975 Also, when doing a major release upgrade, it is required that
976 you boot into single user mode to do the installworld.
978 [4] Note: This step is non-optional. Failure to do this step
979 can result in a significant reduction in the functionality of the
980 system. Attempting to do it by hand is not recommended and those
981 that pursue this avenue should read this file carefully, as well
982 as the archives of freebsd-current and freebsd-hackers mailing lists
983 for potential gotchas.
985 [5] Usually this step is a noop. However, from time to time
986 you may need to do this if you get unknown user in the following
987 step. It never hurts to do it all the time. You may need to
988 install a new mergemaster (cd src/usr.sbin/mergemaster && make
989 install) after the buildworld before this step if you last updated
990 from current before 20020224 or from -stable before 20020408.
992 [6] You may get a warning from kldxref. Ignore it. It doesn't
997 This file contains a list, in reverse chronological order, of major
998 breakages in tracking -current. Not all things will be listed here,
999 and it only starts on March 15, 2000. Updating files can found in
1000 previous releases if your system is older than this.
1002 Copyright information:
1004 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1006 Redistribution, publication, translation and use, with or without
1007 modification, in full or in part, in any form or format of this
1008 document are permitted without further permission from the author.
1010 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1011 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1012 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1013 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1014 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1015 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1016 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1017 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1018 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1019 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1020 POSSIBILITY OF SUCH DAMAGE.
1022 If you find this document useful, and you want to, you may buy the
1025 Contact Warner Losh if you have any questions about your use of