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 The k5su utility installed as part of Kerberos 5 is no longer
27 installed with the set-user-ID bit set by default. Add
28 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
29 with the set-user-ID bit set.
32 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
33 Unfortunately our native GDB (at version 4.18) does not understand
34 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
35 generated debugging information for our native GDB.
38 Due to the way CVS works, it may not properly update src/contrib/gcc
39 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
40 and then do a cvs update.
43 When exec'ing set[ug]id executables, the kernel now ensures that the
44 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
47 New sendmail startup scripts have been installed to make it
48 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
49 variable sendmail_enable to "NO" no longer prevents any sendmail
50 daemons from starting. Instead, either set sendmail_enable to
51 "NONE" or change mta_start_script to a script for starting
52 an alternative MTA. Setting mta_start_script to "" will
53 also prevent any MTA from being started at boot.
56 UCONSOLE is no longer a valid kernel option.
59 FreeBSD 5.0 DP-1 was basically branched today.
62 Warnings are now errors in the kernel. Unless you are a developer,
63 you should add -DNO_WERROR to your make line.
66 sendmail 8.12.2 has been imported. The sendmail binary is no
67 longer a set-user-ID root binary and the infrastructure to support
68 command line mail submission has changed. Be sure to run
69 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
70 and /etc/mail) and read /etc/mail/README for more details.
72 Due to the import of sendmail 8.12.2, a new user and group are
73 required in order for sendmail to run as a set-group-ID
74 binary. A 'make installworld' will use the new user and group
75 to set the owner and group of /var/spool/clientmqueue and will
76 fail if the new user and group do not exist. The 'smmsp' user
77 and group must be merged from src/etc/group and
78 src/etc/master.passwd before using 'make installworld'.
79 'mergemaster -p' will do this. You may need to install
80 mergemaster before this will work if you are updating from a
81 very old version of current. The updating recipe has changed
85 The preferred configuration method for PAM is now /etc/pam.d/
86 rather than /etc/pam.conf. If you have an unmodified
87 pam.conf, just delete it after your next mergemaster run. If
88 you have local modifications, you can use
89 /usr/src/etc/pam.d/convert.pl to incorporate them into your
92 Please see the following url for more details:
93 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
95 If anyone here is already using the new rc.conf(5) variable
96 networkfs_types, please note that it has changed
97 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
100 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
101 started out its life in the ISDN4BSD project as an offspring
102 from sys/net/if_spppsubr.c, which eventually got a life of its
103 own. All the accumulated features and bugfixes of the i4b
104 version have now been merged back into the base system's
105 version now. The only user-visible change resulting from this
106 is that i4b's sppp(4) interfaces are to be managed with
107 spppcontrol(8) again, since ispppcontrol(8) has been retired
108 as well. (There has never been rc file support for
109 ispppcontrol in -current, but only in -stable. That will be
110 reverted by the time the changes are MFCed.)
113 The fdc(4) driver has been updated and now automatically
114 recognizes media in `standard' formats (like 1440 KB and
115 720 KB for a 3.5" high-density drive) when accessing the
116 default device node (e. g. /dev/fd0). The old variety of
117 floppy device nodes /dev/fd*.* is no longer present by
118 default, devices can be created (in DEVFS) on demand. They
119 will need to be customized then for `odd' densities using
123 The bugs in procfs' debugging support code have been fixed,
124 and truss(1) now works again.
127 Daily security checks have been split out to use the periodic(8)
128 scripts. Some change in configuration may be necessary. Please
130 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
134 sos added VCD/SVCD support to ata driver and that needs the
135 kernel and burncd to be in sync.
138 The procfs pseudo-filesystem has now been converted to use the
139 pseudofs framework. If you have 'options PROCFS' in your
140 kernel config, you'll need to add 'options PSEUDOFS' if it's
143 This change temporarily breaks truss(1); use ktrace(1) instead
144 until the issue has been resolved.
147 A security hole in OpenSSH involving `UseLogin yes' has been
151 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
152 after this date. You need to do this only once.
155 Most of the awk issues have been resolved. Some rough
156 edges may be left, but for the most part things should be
157 back to "normal." For CURRENT's usual definition of "normal."
160 Awk has been upgraded to the one true awk from bell labs. Expect
161 choppy waves in the upgrade process.
164 The asr driver problem has been resolved.
167 Due to changes in other parts of the system, the asr driver
168 now causes the system to panic on boot. Do not use it pending
169 correction. Comment it out of any kernel config file that you
170 try to use from this date forward.
173 When crossbuilding, use TARGET=xxx where you used to use
174 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
175 unless you are changing both of them. To cross build pc98 on
176 an alpha, for example, you need to set TARGET=pc98 and
180 The kernel interface that burncd depends on has changed.
181 You must recompile both the kernel and userland applications
185 When crossbuilding, please set TARGET_ARCH rather than
186 MACHINE_ARCH to indicate the target. In the future, one will
187 set TARGET_MACHINE where you set MACHINE now. At the moment,
188 setting MACHINE alone for same MACHINE_ARCH machines works
189 (eg, you can build pc98 on a i386 machine and vice versa).
192 Some weird problems result from using ACPI on some machines.
193 To disable ACPI you can add
194 hint.acpi.0.disable="1"
195 to /boot/loader.conf (or by putting set X=Y at the boot
198 Alternatively, you can remove it from /boot/kernel/acpi.ko
199 or use the MODULES_OVERRIDE function in your kernel config
200 file and not list acpi in that list.
203 The buildworld has been fixed. You may need to install
204 the 4.x compatibility libraries for some old binaries
205 to work. Add COMPAT4X=true to your /etc/make.conf to
206 get them installed on every installworld, or execute the
207 following to get them installed only once:
208 cd src/lib/compat/compat4x.<arch>
210 You will see ``__stdoutp undefined'' until you do this.
213 There's a bug in the world build process. The cross-tools
214 are build with the NEW headers, but the OLD libc.a. This
215 leads to all kinds of problems with the new libc. A temporary
217 CFLAGS="-O -pipe -D_OLD_STDIO"
218 before building world when upgrading from 4.x to current. This
219 can be removed afterwards.
221 A proper fix to the buildworld target is needed.
224 Peter has committed his new kthread nfs client/server code.
225 NFS may be unstable after this date.
228 KSE has hit the tree. Lots of things are now different in
229 the kernel. While a few problems were introduced in the
230 initial commit, most of the major ones have been found and
234 In OLDCARD, CardBus bridges appear to be stable. The work
235 arounds described in the 20010604 entry are now no longer
236 necessary and will be ignored. Most insert/remove problems
237 have been rectified around this date.
240 named now runs as user bind and group bind rather than as
241 root. If named_enable is set to YES in /etc/rc.conf, ensure
242 that user bind is available in /etc/passwd (using vipw(8))
243 and that group bind is available in /etc/group. Also make
244 sure that user or group bind has read (and not write)
245 permission for your name server configuration and that it
246 has read and write permission for your slave zone files and
249 If you wish to continue to run named as root (a less secure
250 alternative), add a line to /etc/rc.conf saying
255 The PAM libraries have had an API upgrade that is beyond
256 the ability of the shared library major number to handle.
257 It is manifested by PAM-using ports dumping core. The
258 solution is to rebuild those ports.
261 The kernel compile module has moved from src/sys/compile/FOO
262 to src/sys/${MACHINE}/compile/FOO.
265 The pccard modem issue from 20010613 has been corrected.
266 OLDCARD support is still a little weak in -current. slot 1 is
267 known not to work on some TI based cardbus bridges. Some
268 cardbus bridges do not properly detect insert/removal events.
269 IRQ configuration needs more safety belts.
272 Softupdates problems have been corrected.
275 Peter ripped out the linkerset support. You must, as always,
276 rerun config after you cvsup if you are using the traditional
277 kernel building methods.
280 pccard modems may not work with current after 20010604 date. Some
281 do, others result in panics. *MAKE*SURE* that you update your
282 config and /etc/rc.conf ala the 20010604 entry, or you will have
283 problems (this issue will be fixed, it just hasn't been yet).
286 SOFTUPDATES seem to be broken since the middle of May or so. Do not
287 use them in current. You can disable softupdates on all mounted
288 partitions, or remove SOFTUPDATES the kernel config file.
291 After Peter's commits to the hints code, people have been noticing
292 that certain devices are attached (or try to) twice. This is due
293 to having both static hints as well as a /boot/device.hints. To
294 work around this issue, please use only one or the other mechanism
295 until this bug is fixed.
297 Please note that a feature of config is that if you have config
298 file FOO and FOO.hints, it automatically adds FOO.hints to the
299 hints.c file, wheather you want it to or not.
302 Locale names have changed to match other systems better.
305 pccard support for pci cards has been committed. You must change
306 your /etc/pccard.conf irq lines. It must match the irq used by
307 pcic device. Interrupt storms may result if you fail to do this.
308 Interrupt storms look a lot like a hang.
310 You must also install a new pccardd, otherwise you will get an
311 interrupt storm at card reset time (just after it tells you what
314 pccardd_flags="-I" is necessary for the time being. It tells pccardd
315 not to ask the kernel if the interrupt is really free or not before
316 using it. You can either change the /etc/pccard.conf irq lines to
317 match pcic, or add "-i X" to the pccardd_flags.
320 INSTALL=install -C is being deprecated. If you want to do this,
321 use COPY=-C instead. The former method will be supported for only
322 a limited time. If you see
324 install: warning: the -d and -C options may not be specified together
326 in your makeworld, then you need to migrate towards using
330 It appears that vm is now stable enough to use again. However,
331 there may be other problems, so caution is still urged. alpha
332 definitely is in bad shape.
335 Minor repo damange has happened. This may cause problems
336 with cvsup of ports. If you get errors, please see
337 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
338 at the bottom for details on a workaround. The error message
340 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
343 Vm and/or swapping are busted on -current. Please be patient.
346 pccard has had much reorganizational work done to it over
347 the past few days. Everything should still work, but if
348 not, please contact imp@freebsd.org.
351 ata ioctl changed. Make sure to recompile both kernel and
352 userland at the same time.
355 New ncurses imported.
358 DEVFS is now opt out, not opt in. Barring major problems, this
359 will be the only way to go starting July 1.
362 OpenSSH has been updated to 2.9. Some defaults are different,
363 including RhostsRSAAuthentication, which changes from yes to no.
366 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
369 Building perl was broken at 02:25:25 PDT.
372 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
373 go back in the water.
376 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
377 this date, but before the correction date.
380 old fsck and new kernel interactions appear to have been fixed.
383 fsck and the kernel were changed to handle some optimizations
384 to directory layout. This breaks backward compatibility.
385 Update only if you understand that you must not use the old
386 fsck with the new kernel ever.
389 fsck has changed the meaning of the pass column in /etc/fstab.
390 Please see the cvs commit to fsck.8 or the fsck.8 man page for
391 details. It is unclear if changes to /etc/fstab are necessary.
394 portmap had changed name to rpcbind for maximum POLA in your
395 current world. /etc/hosts.{allow,deny} needs changes. nfs and
396 other rpc based programs that rely on portmapper will not work
397 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
400 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
401 and ATA_ENABEL_TAGS are no longer kernel options. They have
402 been replaced by tunables. See ata.4 for details.
405 The fxp driver was converted to use miibus. If you compile
406 fxp into your kernel statically, you will need to add miibus.
409 The wi device now defaults to BSS (infrastructure) mode
413 /dev/urandom should be a symbolic link to /dev/random now.
414 Users of current not using DEVFS need to run MAKEDEV std.
415 ssh might not work if you don't.
418 The ed driver has been updated. It now allows mii attachments,
419 which means that you must include the miibus in your kernel if
420 you use the ed driver.
423 The problems with libc have been corrected. It is now mostly
424 safe to go back into the water.
427 The size of FILE was changed. This breaks upgrading. If
428 you must upgrade, be prepared for pain. It also breaks almost
429 all binaries that you've compiled on -current. You are warned
430 that before upgrading would be a good time to do a level 0
431 dump of your system. No, really, I mean it this time.
433 To get to the new system, you'll need to use the following
434 workaround. Hopefully this can be sorted out so that we
435 don't have to move this to the updating section.
437 To get around the installworld problem, do:
438 # cd /usr/src/usr.bin/sed
442 If that doesn't work, then try:
443 # make -k installworld
447 DEVFS is now the default. If you use vinum, make sure that you
448 do not include devfs in your kernel as problems result.
451 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
452 Remove them from your config.
455 ****************************** WARNING ******************************
456 buildkernel has been changed slightly
457 ****************************** WARNING ******************************
458 KERNCONF replaces the variable KERNEL for buildkernel. You
459 should update your scripts and make.conf accordingly.
462 config has changed to allow DEV_FOO as a replacement for NFOO.
463 This requires a new config to build correctly.
466 The kerrnel option I386_CPU is now mutually exclusive with the
467 other cpu types. If you have an i386 system, be sure that it
468 only had this line. Remove it for all other configurations.
471 Changes to the kernel require it and burncd be in sync.
474 Everyone who has hw.sndunit set to something in
475 /etc/sysctl.conf, it is now hw.snd.unit.
478 ex and vi were broken by some changes to sys/queue.h. If you
479 have a bad vi, you will see make buildworld fail with a core
480 dump while building termcap. You can work around this problem
481 by adding -k to your make buildworld. This will cause the
482 build to complete and install a new vi. Once that's done, you
483 can rebuild again without the -k to pick up anything that
484 might have been ignored by the -k option.
486 Others have suggested that you can just rebuild libc if your
487 vi/ex is dynamically linked, but I've not received any reports
491 There have been some changes to libcrypt in -current. The
492 libscrypt/libdescrypt symlink sillyness is gone and the installed
493 libcrypt is fully functional. Be aware of this.
496 Linksys Fast Ethernet PCCARD cards supported by the ed driver
497 now require the addition of flag 0x80000 to their config line
498 in pccard.conf(5). This flag is not optional. These Linksys
499 cards will not be recognized without it.
502 Important new FreeBSD-version stuff: PAM support has been worked
503 in, partially from the "Unix" OpenSSH version. This requires
504 adding the following in pam.conf:
506 sshd auth sufficient pam_skey.so
507 sshd auth required pam_unix.so try_first_pass
508 sshd session required pam_permit.so
514 The random device needs more entropy, so you need to make sure
515 that you've run mergemaster to get a /etc/rc which will seed
516 /dev/random. If you don't and the system hangs after ldconfig,
517 then banging on the keyboard randomly until it unhangs is one
521 ****************************** WARNING ******************************
522 Sendmail has been updated.
523 ****************************** WARNING ******************************
524 o mail.local(8) is no longer installed as a set-user-id binary.
525 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
527 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
529 o Now using sendmail's version of vacation(1).
530 o The sendmail cf building tools (contrib/sendmail/cf) are installed
531 in /usr/share/sendmail/cf.
532 o sendmail.cw changed to local-host-names
534 More details can be found at
535 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
538 The ports tree's new layout is in place. Be sure to update
539 your entire ports tree, or you will have problems.
542 The perl build procedure no longer installs miniperl, nor uses
543 the installed miniperl. It is recommended that you delete
547 This weekend the ports tree will be updated to a new layout.
548 It will be in an inconsistent state until noted in the UPDATING
549 file, or with asami-san's message to the relevant mailing
550 lists. With this new layout, you'll need to update the whole
551 tree for anything to work.
554 There was a change in the passwd format. Need more information.
557 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
558 place. Please update boot loader (not the boot blocks) at the
559 same time as your kernel.
562 The new pmtimer device is necessary for laptops. Failure to
563 include the device will cause suspended laptops losing time
564 when they resume. Include
566 in your config file and
567 hint.pmtimer.0.at="isa"
568 to your /boot/device.hints file.
571 The random device has been turned into a (pseudo-)device,
572 rather than an option. The supplied kernel config files have
573 been updated. You will need to do something similar in your
574 own kernel config file.
579 If you prefer to load the loadable module, you need to do
583 The random device module has been renamed from randomdev.ko to
584 random.ko. You will need to edit your /boot/loader.conf to
585 reflect this if you load this module at boot time.
586 The line should read:
590 The SMPNG commit has happened. It should work, but if it
591 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
592 to be a variety of minor issues. Please see 20000905 to make
593 sure you don't have model loading problems which might at
594 first blush appear related to SMP.
597 nsswitch has been imported from NetBSD. Among other things,
598 this means that /etc/host.conf is no longer used. See
599 nsswitch.conf(5) instead. Note that at boot time rc.network
600 will attempt to produce a new nsswitch.conf file for you if you
601 don't have one, and you have host.conf.
604 The ucred structure changed size. This breaks the interface
605 that mountd uses. Trying to use an older mountd with a newer
606 kernel guarantees a panic. This means that you need to use
607 kernels newer than today only with matching mountd, but you
608 needed to do that anyway with the boot loader changes.
611 The boot loader has been updated. The new default kernel is
612 now /boot/kernel/kernel.ko. The new default module location
615 You *MUST* upgrade your boot loader and kernel at the same time.
616 The easiest way to do this is to do the buildworld/buildkernel/
617 installkernel/installworld dance.
619 Furthermore, you are urged to delete your old /modules directory
620 before booting the new kernel, since kldload will find stale
621 modules in that directory instead of finding them in the correct
622 path, /boot/kernel. The most common complaint that this cures
623 is that the linux module crashes your machine after the update.
625 if [ ! -d /boot/kernel.old ]; then
626 mv /modules.old /boot/kernel.old
627 chflags noschg /kernel.old
628 mv /kernel.old /boot/kernel.old/kernel.ko
629 chflags schg /boot/kernel.old/kernel.ko
633 A new issue with the sendmail upgrade has come to light.
634 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
635 incorrectly install the default aliases in /etc/mail rather than
636 move the old one from /etc. So you'll need to manually move the
637 file, create a symbolic link, remove the old /etc/aliases.db and
638 run newaliases. For safety sake, you should stop sendmail
639 while doing this and run the upgrade when locally sourced email
640 is not likely to be generated.
643 /boot/device.hints is now required for installkernel to
644 succeed. You should copy GENERIC.hints for your architecture
645 into /boot/device.hints. If and only if you compile hints
646 into your kernel, then this file may be empty. Please note,
647 if you have an empty or missing /boot/device.hints file and
648 you neglected to compile hints into your kernel, no boot
649 messages will appear after the boot loader tries to start the
653 If you do NOT have ``options RANDOMDEV'' in your kernel and
654 you DO want the random device then add randomdev_load="YES" to
658 suidperl is now always built and installed on the system, but
659 with permissions of 511. If you have applications that use
660 this program, you are now required to add ENABLE_SUIDPERL=true
661 to /etc/make.conf. If you forget to do this,
662 chmod 4511 /usr/bin/suidperl
663 will fix this until the next build.
666 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
667 visible changes that may immediately affect your configuration
669 - New default file locations from src/contrib/sendmail/cf/README
670 - newaliases limited to root and trusted users
671 - MSA port (587) turned on by default
672 - New queue file naming system so can't go from 8.11 -> 8.9
673 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
674 - FEATURE(`nullclient') is more full featured
675 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
676 - mail.local FreeBSD-only -b option changed to -B
677 - See src/contrib/sendmail/RELEASE_NOTES for more info
680 suidperl (aka sperl) is no longer build by default. You must
681 specifically define BUILD_SUIDPERL to "true" for it to be build.
682 Furthermore, we recommend that you remove /usr/bin/sperl* and
683 /usr/bin/suidperl files from your system unless you have a
687 Networking defaults have been tightened. Anybody upgrading
688 /etc/defaults/rc.conf needs to add the following lines to
689 /etc/rc.conf if they want to have the same setup
690 afterwards (unless the variables already are set, of course):
691 # Enable network daemons for user convenience.
694 sendmail_enable="YES"
697 If you have null_load="YES" in your /boot/loader.conf, you
698 will need to change that to nullfs_load="YES".
701 The "installkernel" target has changed slightly. Now even if
702 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
703 it will install the MYKERNEL file (built with the buildkernel
704 target) as /kernel rather than /MYKERNEL. Those who have
705 updated their /boot/loader.conf files to point to /MYKERNEL
706 should remove that entry or perform manual rename of /kernel
710 If you use CVSUP or CTM to get CVS trees, AND you used to get
711 the old crypto files from internat.freebsd.org AND you check
712 out files from the CVS tree with the cvs command, please read
713 http://people.freebsd.org/~imp/internat.txt
714 for details on potential problems that you might have and how
717 If you are merely a mirror, or don't answer yes to each of the
718 clauses above, you needn't worry.
721 /etc/security has been updated to print the inode number of
722 setuid programs that have changed. You will see a large spike
723 in the number of changed programs the first time when you run
724 mergemaster to get a new /etc/security.
727 /dev/random now has good entropy collection (from the keyboard
728 and sysmouse drivers). Please ensure that either `options
729 RANDOMDEV' is present in your kernel config file or that
730 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
731 not have the /dev/random driver, OpenSSL (and consequently
732 lots of crypto tools (like SSH)) will fail with strange
733 errors. (see below, 20000624).
735 FreeBSD-current is safe again to run Crypto.
738 phk made the malloc default options AJ. This may slow things
739 down and uncover other latent bugs in the code. If you need to
740 run at full speed, you can disable this by doing the following:
741 ln -s aj /etc/malloc.conf
744 libftpio's version was accidentally bumped a few days ago. This
745 has been corrected. You may need to remove /usr/lib/libftpio.so.6
746 before doing your next buildworld/installworld pair. It certainly
747 won't hurt to remove it before the update procedure. It will
748 break fetch until a new one is built, but ftp can be used in the
752 The crypto packages have changed for the cvsup. This has been done
753 in a backward compatible way, but the old packages will go away at
754 some point in the future. Look at /usr/share/examples/cvsup for
758 With the new sys/modules/sound/drivers/*, you will need to
759 set SYSDIR until you do an installworld after July 7th.
762 rc.shutdown and rc will now call the rc.d scripts with start
763 or stop. This may cause some harmless warnings from older
764 rc.d scripts that haven't been updated.
767 The libfetch based version of fetch has gone into the tree.
768 Minor problems may result on some of the less popular sites,
769 which should be reported to des@freebsd.org.
772 From approximately this date forward, one must have the crypto
773 system installed in order to build the system and kernel.
774 While not technically strictly true, one should treat it as
775 required and grab the crypto bits. If you are grabbing CVS
776 trees, src-all and cvs-crypto should be treated as if they
777 were required. You should check with the latest collections
778 to make sure that these haven't changed.
781 Mark Murray just committed the first parts of a cleanup of
782 /dev/zero, et al. This is also cleaning up /dev/random.
783 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
784 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
785 until Mark can merge in the fixes to this work in progress.
786 openssh and openssl should not be used to generate keys from this
787 date to the completion of the work.
789 If you must operate at this reduced level of security, add '
790 options RANDOMDEV' to your kernel or modload the randomdev
791 module. You may also need to copy a new MAKEDEV to /dev and
792 recreate the random and urandom devices.
795 The license on the softupdates is now a standard 2 clause
796 BSD license. You may need to remove your symbolic links
797 that used to be required when updating.
800 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
801 the config file update procedure.
802 http://people.freebsd.org/~imp/config-upd.html
803 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
804 isn't buildable. However, you can generate a LINT file.
807 Binutils 2.10 have hit the tree, or will shortly. As soon
808 as they do, the problem noted in 20000522 will be resolved and
809 that workaround will no longer be required.
812 phk removed the compatibility creation of wd devices in the
813 ad driver. If you haven't done so already, you must update
814 your fstab, etc to use the ad devices instead of the wd
817 In addition, you'll need to update your boot blocks to a
818 more modern version, if you haven't already done so. Modern
819 here means 4.0 release or newer (although older releases
823 Peter took an axe to config(8). Be sure that you read his mail
824 on the topic before even thinking about updating. You will
825 need to create a /boot/device.hints or add a hints directive
826 to your config file to compile them in statically. The format
827 of the config file has changed as well. Please see GENERIC or
828 NEWCARD for examples of the new format.
830 Indirectly, this also breaks USERCONFIG. Unless a newer entry
831 says that it has been fixed, assume that must use the hints mechanism
832 in the loader if you need to use a machine with very old ISA cards
836 A new set of binutils went into the tree today. Anybody
837 building a kernel after this point is advised that they need
838 to rebuild their binutils (or better yet do a
839 buildworld/installworld) before building a new kernel.
841 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
842 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
843 is recommended that you don't set this option until the problem
847 The ethernet drivers were all updated to clean up the BPF handling.
850 The problems with boot blocks on the alphas have been corrected.
851 This will require some care in updating alphas. A new libstand
852 is requires for the boot blocks to build properly.
855 Recompile all kld modules. Proper version dependency info
859 Modules have been disconnected from the buildworld tree and
860 connected to the kernel building instead.
863 You may need to build gperf
864 cd /usr/src/gnu/usr.bin/gperf && make depend all install
865 when upgrading from 4.0 -> current. The build system now uses
866 an option only in -current.
869 The method that we brand ELF binaries has changed to be more
870 acceptable to the binutils maintainers. You will need to
871 rebrand your ELF binaries that aren't native. One problem
872 binary is the Linux ldconfig. After your make world, but
873 before you reboot, you'll need to issue:
874 brandelf -t Linux /compat/linux/sbin/ldconfig
875 if you have Linux compatibility enabled on your machine.
878 If you have really bad/marginal IDE drives, you may find they
879 don't work well. Use pio mode instead. The easiest way to
880 cope if you have a problem combination is to add:
881 /sbin/sysctl hw.ata.ata_dma=0
882 to the start of /etc/rc.conf.
885 The ISA and PCI compatibility shims have been connected to the
886 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
887 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
888 include the appropriate option in your kernel config. Drivers
889 using the shims should be updated or they won't ship with
890 5.0-RELEASE, targeted for 2001.
893 We've entered the traditional post release dumping party.
894 Large kernel changes are being committed and are in the
895 works. It is important to keep the systems' klds and kernel
896 in sync as kernel interfaces and structures are changing.
897 Before reporting kernel panics, make sure that all modules
898 that you are loading are up to date.
901 If you are upgrading from an older version of FreeBSD, you
902 need to update your boot blocks as well. 'disklabel -B ad0'
903 will do the trick. This isn't critical until you remove your
904 wd device entries in /dev, at which point your system will not
908 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
909 to upgrade to 4.0 from 3.x.
915 Avoid using make -j when upgrading. From time to time in the
916 past there have been problems using -j with buildworld and/or
917 installworld. This is especially true when upgrading between
918 "distant" versions (eg one that cross a major release boundary
919 or several minor releases, or when several months have passed
920 on the -current branch).
922 Sometimes, obscure build problems are the result of environment
923 poisoning. This can happen because the make utility reads its
924 environment when searching for values for global variables.
925 To run your build attempts in an "environmental clean room",
926 prefix all make commands with 'env -i '. See the env(1) manual
927 page for more details.
931 If you are updating from a prior version of FreeBSD (even one just
932 a few days old), you should follow this procedure. With a
933 /usr/obj tree with a fresh buildworld,
934 make buildkernel KERNCONF=YOUR_KERNEL_HERE
935 make installkernel KERNCONF=YOUR_KERNEL_HERE
937 To just build a kernel when you know that it won't mess you up
938 --------------------------------------------------------------
939 cd src/sys/{i386,alpha}/conf
940 config KERNEL_NAME_HERE
941 cd ../../compile/KERNEL_NAME_HERE
946 If this fails, go to the "To build a kernel" section.
948 To rebuild everything and install it on the current system.
949 -----------------------------------------------------------
951 Build a new kernel, see above.
953 To upgrade from 4.x-stable to current
954 -------------------------------------
956 make buildkernel KERNCONF=YOUR_KERNEL_HERE
957 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
958 make installkernel KERNCONF=YOUR_KERNEL_HERE
959 reboot in single user [3]
966 Make sure that you've read the UPDATING file to understand the
967 tweaks to various things you need. At this point in the life
968 cycle of current, things change often and you are on your own
969 to cope. The defaults can also change, so please read ALL of
970 the UPDATING entries.
972 Also, if you are tracking -current, you must be subscribed to
973 freebsd-current@freebsd.org. Make sure that before you update
974 your sources that you have read and understood all the recent
975 messages there. If in doubt, please track -stable which has
978 [1] If you have third party modules, such as vmware, you
979 should disable them at this point so they don't crash your
982 [2] If you have legacy ISA devices, you may need to create
983 your own device.hints to reflect your unique hardware
986 [3] From the bootblocks, boot -s, and then do
991 adjkerntz -i # if CMOS is wall time
992 Also, when doing a major release upgrade, it is required that
993 you boot into single user mode to do the installworld.
995 [4] Note: This step is non-optional. Failure to do this step
996 can result in a significant reduction in the functionality of the
997 system. Attempting to do it by hand is not recommended and those
998 that pursue this avenue should read this file carefully, as well
999 as the archives of freebsd-current and freebsd-hackers mailing lists
1000 for potential gotchas.
1002 [5] Usually this step is a noop. However, from time to time
1003 you may need to do this if you get unknown user in the following
1004 step. It never hurts to do it all the time. You may need to
1005 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1006 install) after the buildworld before this step if you last updated
1007 from current before 20020224 or from -stable before 20020408.
1011 This file contains a list, in reverse chronological order, of major
1012 breakages in tracking -current. Not all things will be listed here,
1013 and it only starts on March 15, 2000. Updating files can found in
1014 previous releases if your system is older than this.
1016 Copyright information:
1018 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1020 Redistribution, publication, translation and use, with or without
1021 modification, in full or in part, in any form or format of this
1022 document are permitted without further permission from the author.
1024 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1025 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1026 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1027 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1028 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1029 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1030 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1031 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1032 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1033 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1034 POSSIBILITY OF SUCH DAMAGE.
1036 If you find this document useful, and you want to, you may buy the
1039 Contact Warner Losh if you have any questions about your use of