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