1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. See end of file for further details. For commonly
5 done items, please see the COMMON ITEMS: section later in the file.
7 NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
8 FreeBSD 5.0-CURRENT has many debugging features turned on, in
9 both the kernel and userland. These features attempt to detect
10 incorrect use of system primitives, and encourage loud failure
11 through extra sanity checking and fail stop semantics. They
12 also substantially impact system performance. If you want to
13 do performance measurement, benchmarking, and optimization,
14 you'll want to turn them off. This includes various WITNESS-
15 related kernel options, INVARIANTS, malloc debugging flags
16 in userland, and various verbose features in the kernel. Many
17 developers choose to disable these features on build machines
18 to maximize performance.
21 The OFW_NEWPCI option has been turned on in the Sparc64 GENERIC kernel.
22 Among other things, this changes the device enumeration to be
23 closer to Solaris. Be aware that, this can even cause the machine
24 to not boot without manual intervention before the fstab is adjusted.
27 All current USB and Firewire quirks in da(4) have been deprecated
28 and will be removed for 5.2. If this causes failure for your
29 umass(4) devices, enable "options DA_OLD_QUIRKS" in your kernel
30 and send the output of "camcontrol inquiry da0" to scsi@freebsd.org
31 so the quirk can be re-enabled.
34 FPU-less support has been removed from FreeBSD. Chances are you won't
35 notice. 386+387 support should still work after this change, but
36 it is now a minimum requirement for the i386 port that you have real
40 Some people are having problems with changes related to /rescue.
41 If you are building -j N, you will need to define NO_RESCUE. Others
42 will need to define it if /rescue has issues with their environment.
43 People should report those issues to current@.
46 gcc was upgraded to 3.3. You are advised to not build -DNOCLEAN
47 across this point. Further, it might be a good idea to remove
50 20030613: [retrospective]
51 There was a small window in which sed(1) was broken. If you
52 happen to have sed(1) installed during that window, which is
53 evidenced by an inability to build world with the failure
54 given below, you need to manually build and install sed(1)
55 (and only sed(1)) before doing anything else. This is a one-
56 time snafu. Typical failure mode:
58 In file included from /usr/src/contrib/binutils/bfd/targets.c:1092:
59 targmatch.h:7:1: null character(s) ignored
60 targmatch.h:12:1: null character(s) ignored
61 targmatch.h:16:1: null character(s) ignored
64 The window of "sed(1)-uction" is from Wed Jun 4 15:31:55 2003 UTC
65 to Thu Jun 5 12:10:19 2003 UTC (from rev 1.30 to rev 1.31 of
66 usr.bin/sed/process.c).
69 Remove deprecated locale names and transition period code
70 for them, finishing switching to the new scheme. Check your
71 LANG environment variable.
74 CCD has been changed to be a fully GEOMified class. Kernel
75 and ccdconfig(8) needs to be in sync, this is particularly
76 important to remember beforehand if your source tree is on
77 a ccd device. Consider making a copy of the old ccdconfig
78 into /boot/kernel.good or wherever you keep your backup
82 Kerberos 5 (Heimdal) is now built by default. Setting
83 MAKE_KERBEROS5 no longer has any effect. If you do NOT
84 want the "base" Kerberos 5, you need to set NO_KERBEROS.
87 groff has been updated. If you try to do a buildworld and
88 get an infinite loop in troff, update to May 4th or newer. If you
89 have a newer kernel than userland, you may need to set the OSRELDATE
90 to 500110 in your environment before starting a buildworld.
93 The old rc system has been removed. Please report any problems
94 to freebsd-rc@yahoogroups.com, and/or freebsd-current@freebsd.org.
95 Your personal versions of these files will not be removed, so you can
96 continue to use them. However, you should take great care when updating,
97 especially when using mergemaster, since the compatibility code that
98 utilizes these old scripts has also been removed.
101 A bug has been fixed in /dev/devctl which would cause devd
102 to hang on boot, were it not for a workaround in devd. The
103 work around in devd will be removed around 20030507. You
104 have until then to upgrade your kernel before updating
105 userland. In general, you should have a userland and
106 kernel that's in sync with each other. However, given the
107 effects of this bug (hang on boot when starting devd), some
111 Alphas with libc from between 20030312 and 20030329 exhibit
112 floating point exceptions (FPEs), most notably in awk(1)
113 while upgrading the system through a buildworld.
115 So, to successfully upgrade your Alpha, you must either
116 downgrade your libc.so to a pre-20030312 version, or update
117 /usr/share/mk/bsd.cpu.mk to revision 1.26 which adds -mieee
118 to CFLAGS, then forcibly rebuild and install libc:
120 cd /usr/src/lib/libc && \
121 make cleandir && make obj && \
122 make -DNOMAN -DNOPROFILE all && \
123 make -DNOMAN -DNOPROFILE install
126 sendmail 8.12.7 has been imported. It has one important
127 change for IPv6 users. The default submit.mc now uses
128 '[127.0.0.1]' instead of 'localhost' meaning only IPv4 is
129 used to connect to the MTA. Users on IPv6-only machines
130 will need to edit /etc/mail/submit.mc appropriately.
133 NODEVFS option has been removed and DEVFS thereby made standard.
134 This makes all references to MAKEDEV obsolete, and they should
135 be removed when convenient.
138 The name of the device for the ofw console has changed, sparc64 users
139 must run mergemaster to update their installed /etc/ttys.
142 The scheduler framework has grown a second scheduler and consequently
143 you must specify one and only one scheduler in your kernel config.
144 The cvs config files have been updated to use the old scheduler
145 which may be selected via 'options SCHED_4BSD'. If you would like
146 to try the new, much more experimental, scheduler please try
147 'options SCHED_ULE' and contribute to the arch@ discussion.
150 A new version of the wi driver has been imported into the tree.
151 One now must have device wlan in the config file for it to operate
154 In addition, there have been some changes to how wi devices are
155 configured for point to point links to bring it more in line
156 with the former way of doing things, as well as compatibility
160 For a period after the GCC 3.2.1 import (from 12/04 to 12/22), GCC
161 used an incompatible form of ABI for returning structures and unions
162 which FreeBSD's GCC maintainers were not aware of relative to previous
163 versions of FreeBSD. We have gone back to the ABI for now, and any
164 code compiled which is required to interoperate with other code (not
165 built at the same time) returning structs or unions should be
169 A name change in /etc/netconfig has been reverted to stay
170 compatible with suns TIRPC and also with NetBSD. You need
171 to run mergemaster after make world. A new libc does still work
172 with an outdated /etc/netconfig for some time, but you'll get
173 a warning. This warning will be removed in 20030301.
176 The recent binutils upgrade marks a kernel flag day on
177 sparc64: modules built with the old binutils will not work
178 with new kernels and vice versa. Mismatches will result in
179 panics. Make sure your kernel and modules are in sync.
182 The value of IPPROTO_DIVERT has changed. Make sure to keep
183 your kernel, netstat, natd and any third-party DIVERT
187 Old, compatibility slices have been removed in GEOM kernels.
188 This means that you will have to update your /etc/fstab to
189 not use disk devices of the form /dev/ad0a. Instead, you
190 now must specify /dev/ad0s1a, or whatever slice your FreeBSD
191 partition really is on. The old device names have gone
192 away, so if you use them anywhere else, you must also adjust
193 those uses. (This doesn't affect the disks formatted in
194 the ``dangerously-dedicated'' mode.)
197 Alphas with kernels from between 20020830 and 20021023 and/or
198 rtld (ld-elf.so.1) older than 20021023 may experience problems
199 with groff while doing a buildworld (kernel: "out of memory",
200 fixed in rev 1.129 of kern/imgact_elf.c; rtld: "too few PT_LOAD
201 segments", fixed in rev 1.8 of libexec/rtld-elf/map_object.c).
203 So, to successfully upgrade your Alpha, you must either
204 upgrade your kernel and rtld first (which might be a bit
205 tricky), or avoid running the bootstrapped groff during the
206 "transitional" buildworld. To avoid running groff during the
207 transitional upgrade run make buildworld with -DNOMAN,
208 -DNO_SHAREDOCS, and -DNO_LPR.
211 gcc has been upgraded to 3.2. It is not all binary compatible
212 with earlier versions of gcc for c++ programs. All c++
213 programs and libraries need to be recompiled.
215 Also, if you encounter g++ issues, rm /usr/include/g++/* before
216 doing an installworld to make sure that stale files are removed.
219 Our /etc/termcap now has all the entries from the XFree86 xterm
220 almost unchanged. This means xterm now supports color by default.
221 If you used TERM=xterm-color in the past you now should use
222 TERM=xterm. (xterm-color will lead to benign warnings).
225 A "bug" in gcc(1) that was hiding warning in system headers was
226 fixed. It's probably time to add -DNO_WERROR to your make line
230 COPY is being deprecated. The 20010530 change was reverted, as
231 it causes far more pain than was expected, and to always compare
232 before installing, please use INSTALL="install -C" again. The
233 -C option is now silently ignored when used with the -d option.
236 Problems with libc_r clients like KDE and GNOME have been resolved.
237 There are still some minor problems with some signals but the
238 system is stable enough for general use again. SMP is less so than UP
239 but each can successfully complete multiple buildworlds.
240 Libkvm needs to be recompiled due to KSE.
243 Now would be a bad time to upgrade. Something in or near the
244 KSE commit totally broke programs using libc_r like KDE and
248 The k5su utility installed as part of Kerberos 5 is no longer
249 installed with the set-user-ID bit set by default. Add
250 ENABLE_SUID_K5SU=yes to /etc/make.conf to have it installed
251 with the set-user-ID bit set.
254 Gcc 3.1 debugging format (cc -g) has changed from STABS to DWARF2.
255 Unfortunately our native GDB (at version 4.18) does not understand
256 the DWARF2 debugging format. Thus you must use `gcc -gstabs+' to
257 generated debugging information for our native GDB.
260 Due to the way CVS works, it may not properly update src/contrib/gcc
261 to the 3.1 sources. The easiest fix is to `rm -rf' src/contrib/gcc
262 and then do a cvs update.
265 When exec'ing set[ug]id executables, the kernel now ensures that the
266 stdio file descriptors (0..2) are open. See FreeBSD-SA-02:23.stdio.
269 New sendmail startup scripts have been installed to make it
270 easier to use alternative MTAs with FreeBSD. Setting the rc.conf
271 variable sendmail_enable to "NO" no longer prevents any sendmail
272 daemons from starting. Instead, either set sendmail_enable to
273 "NONE" or change mta_start_script to a script for starting
274 an alternative MTA. Setting mta_start_script to "" will
275 also prevent any MTA from being started at boot.
278 UCONSOLE is no longer a valid kernel option.
281 FreeBSD 5.0 DP-1 was basically branched today.
284 Warnings are now errors in the kernel. Unless you are a developer,
285 you should add -DNO_WERROR to your make line.
288 sendmail 8.12.2 has been imported. The sendmail binary is no
289 longer a set-user-ID root binary and the infrastructure to support
290 command line mail submission has changed. Be sure to run
291 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
292 and /etc/mail) and read /etc/mail/README for more details.
294 Due to the import of sendmail 8.12.2, a new user and group are
295 required in order for sendmail to run as a set-group-ID
296 binary. A 'make installworld' will use the new user and group
297 to set the owner and group of /var/spool/clientmqueue and will
298 fail if the new user and group do not exist. The 'smmsp' user
299 and group must be merged from src/etc/group and
300 src/etc/master.passwd before using 'make installworld'.
301 'mergemaster -p' will do this. You may need to install
302 mergemaster before this will work if you are updating from a
303 very old version of current. The updating recipe has changed
307 The preferred configuration method for PAM is now /etc/pam.d/
308 rather than /etc/pam.conf. If you have an unmodified
309 pam.conf, just delete it after your next mergemaster run. If
310 you have local modifications, you can use
311 /usr/src/etc/pam.d/convert.pl to incorporate them into your
314 Please see the following url for more details:
315 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
317 If anyone here is already using the new rc.conf(5) variable
318 networkfs_types, please note that it has changed
319 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
322 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
323 started out its life in the ISDN4BSD project as an offspring
324 from sys/net/if_spppsubr.c, which eventually got a life of its
325 own. All the accumulated features and bugfixes of the i4b
326 version have now been merged back into the base system's
327 version now. The only user-visible change resulting from this
328 is that i4b's sppp(4) interfaces are to be managed with
329 spppcontrol(8) again, since ispppcontrol(8) has been retired
330 as well. (There has never been rc file support for
331 ispppcontrol in -current, but only in -stable. That will be
332 reverted by the time the changes are MFCed.)
335 The fdc(4) driver has been updated and now automatically
336 recognizes media in `standard' formats (like 1440 KB and
337 720 KB for a 3.5" high-density drive) when accessing the
338 default device node (e. g. /dev/fd0). The old variety of
339 floppy device nodes /dev/fd*.* is no longer present by
340 default, devices can be created (in DEVFS) on demand. They
341 will need to be customized then for `odd' densities using
345 The bugs in procfs' debugging support code have been fixed,
346 and truss(1) now works again.
349 Daily security checks have been split out to use the periodic(8)
350 scripts. Some change in configuration may be necessary. Please
352 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
356 sos added VCD/SVCD support to ata driver and that needs the
357 kernel and burncd to be in sync.
360 The procfs pseudo-filesystem has now been converted to use the
361 pseudofs framework. If you have 'options PROCFS' in your
362 kernel config, you'll need to add 'options PSEUDOFS' if it's
365 This change temporarily breaks truss(1); use ktrace(1) instead
366 until the issue has been resolved.
369 A security hole in OpenSSH involving `UseLogin yes' has been
373 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
374 after this date. You need to do this only once.
377 Most of the awk issues have been resolved. Some rough
378 edges may be left, but for the most part things should be
379 back to "normal." For CURRENT's usual definition of "normal."
382 Awk has been upgraded to the one true awk from bell labs. Expect
383 choppy waves in the upgrade process.
386 The asr driver problem has been resolved.
389 Due to changes in other parts of the system, the asr driver
390 now causes the system to panic on boot. Do not use it pending
391 correction. Comment it out of any kernel config file that you
392 try to use from this date forward.
395 When crossbuilding, use TARGET=xxx where you used to use
396 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
397 unless you are changing both of them. To cross build pc98 on
398 an alpha, for example, you need to set TARGET=pc98 and
402 The kernel interface that burncd depends on has changed.
403 You must recompile both the kernel and userland applications
407 When crossbuilding, please set TARGET_ARCH rather than
408 MACHINE_ARCH to indicate the target. In the future, one will
409 set TARGET_MACHINE where you set MACHINE now. At the moment,
410 setting MACHINE alone for same MACHINE_ARCH machines works
411 (eg, you can build pc98 on an i386 machine and vice versa).
414 Some weird problems result from using ACPI on some machines.
415 To disable ACPI you can add
416 hint.acpi.0.disabled="1"
417 to /boot/loader.conf (or by putting set X=Y at the boot
420 Alternatively, you can remove it from /boot/kernel/acpi.ko
421 or use the MODULES_OVERRIDE function in your kernel config
422 file and not list acpi in that list.
425 The buildworld has been fixed. You may need to install
426 the 4.x compatibility libraries for some old binaries
427 to work. Add COMPAT4X=true to your /etc/make.conf to
428 get them installed on every installworld, or execute the
429 following to get them installed only once:
430 cd src/lib/compat/compat4x.<arch>
432 You will see ``__stdoutp undefined'' until you do this.
435 There's a bug in the world build process. The cross-tools
436 are build with the NEW headers, but the OLD libc.a. This
437 leads to all kinds of problems with the new libc. A temporary
439 CFLAGS="-O -pipe -D_OLD_STDIO"
440 before building world when upgrading from 4.x to current. This
441 can be removed afterwards.
443 A proper fix to the buildworld target is needed.
446 Peter has committed his new kthread nfs client/server code.
447 NFS may be unstable after this date.
450 KSE has hit the tree. Lots of things are now different in
451 the kernel. While a few problems were introduced in the
452 initial commit, most of the major ones have been found and
456 In OLDCARD, CardBus bridges appear to be stable. The work
457 arounds described in the 20010604 entry are now no longer
458 necessary and will be ignored. Most insert/remove problems
459 have been rectified around this date.
462 named now runs as user bind and group bind rather than as
463 root. If named_enable is set to YES in /etc/rc.conf, ensure
464 that user bind is available in /etc/passwd (using vipw(8))
465 and that group bind is available in /etc/group. Also make
466 sure that user or group bind has read (and not write)
467 permission for your name server configuration and that it
468 has read and write permission for your slave zone files and
471 If you wish to continue to run named as root (a less secure
472 alternative), add a line to /etc/rc.conf saying
477 The PAM libraries have had an API upgrade that is beyond
478 the ability of the shared library major number to handle.
479 It is manifested by PAM-using ports dumping core. The
480 solution is to rebuild those ports.
483 The kernel compile module has moved from src/sys/compile/FOO
484 to src/sys/${MACHINE}/compile/FOO.
487 The pccard modem issue from 20010613 has been corrected.
488 OLDCARD support is still a little weak in -current. slot 1 is
489 known not to work on some TI based cardbus bridges. Some
490 cardbus bridges do not properly detect insert/removal events.
491 IRQ configuration needs more safety belts.
494 Softupdates problems have been corrected.
497 Peter ripped out the linkerset support. You must, as always,
498 rerun config after you cvsup if you are using the traditional
499 kernel building methods.
502 pccard modems may not work with current after 20010604 date. Some
503 do, others result in panics. *MAKE*SURE* that you update your
504 config and /etc/rc.conf ala the 20010604 entry, or you will have
505 problems (this issue will be fixed, it just hasn't been yet).
508 SOFTUPDATES seem to be broken since the middle of May or so. Do not
509 use them in current. You can disable softupdates on all mounted
510 partitions, or remove SOFTUPDATES the kernel config file.
513 After Peter's commits to the hints code, people have been noticing
514 that certain devices are attached (or try to) twice. This is due
515 to having both static hints as well as a /boot/device.hints. To
516 work around this issue, please use only one or the other mechanism
517 until this bug is fixed.
519 Please note that a feature of config is that if you have config
520 file FOO and FOO.hints, it automatically adds FOO.hints to the
521 hints.c file, whether you want it to or not.
524 Locale names have changed to match other systems better.
527 pccard support for pci cards has been committed. You must change
528 your /etc/pccard.conf irq lines. It must match the irq used by
529 pcic device. Interrupt storms may result if you fail to do this.
530 Interrupt storms look a lot like a hang.
532 You must also install a new pccardd, otherwise you will get an
533 interrupt storm at card reset time (just after it tells you what
536 pccardd_flags="-I" is necessary for the time being. It tells pccardd
537 not to ask the kernel if the interrupt is really free or not before
538 using it. You can either change the /etc/pccard.conf irq lines to
539 match pcic, or add "-i X" to the pccardd_flags.
542 INSTALL=install -C is being deprecated. If you want to do this,
543 use COPY=-C instead. The former method will be supported for only
544 a limited time. If you see
546 install: warning: the -d and -C options may not be specified together
548 in your makeworld, then you need to migrate towards using
552 It appears that vm is now stable enough to use again. However,
553 there may be other problems, so caution is still urged. alpha
554 definitely is in bad shape.
557 Minor repo damage has happened. This may cause problems
558 with cvsup of ports. If you get errors, please see
559 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
560 at the bottom for details on a workaround. The error message
562 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
565 Vm and/or swapping are busted on -current. Please be patient.
568 pccard has had much reorganizational work done to it over
569 the past few days. Everything should still work, but if
570 not, please contact imp@freebsd.org.
573 ata ioctl changed. Make sure to recompile both kernel and
574 userland at the same time.
577 New ncurses imported.
580 DEVFS is now opt out, not opt in. Barring major problems, this
581 will be the only way to go starting July 1.
584 OpenSSH has been updated to 2.9. Some defaults are different,
585 including RhostsRSAAuthentication, which changes from yes to no.
588 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
591 Building perl was broken at 02:25:25 PDT.
594 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
595 go back in the water.
598 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
599 this date, but before the correction date.
602 old fsck and new kernel interactions appear to have been fixed.
605 fsck and the kernel were changed to handle some optimizations
606 to directory layout. This breaks backward compatibility.
607 Update only if you understand that you must not use the old
608 fsck with the new kernel ever.
611 fsck has changed the meaning of the pass column in /etc/fstab.
612 Please see the cvs commit to fsck.8 or the fsck.8 man page for
613 details. It is unclear if changes to /etc/fstab are necessary.
616 portmap had changed name to rpcbind for maximum POLA in your
617 current world. /etc/hosts.{allow,deny} needs changes. nfs and
618 other rpc based programs that rely on portmapper will not work
619 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
622 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
623 and ATA_ENABLE_TAGS are no longer kernel options. They have
624 been replaced by tunables. See ata.4 for details.
627 The fxp driver was converted to use miibus. If you compile
628 fxp into your kernel statically, you will need to add miibus.
631 The wi device now defaults to BSS (infrastructure) mode
635 /dev/urandom should be a symbolic link to /dev/random now.
636 Users of current not using DEVFS need to run MAKEDEV std.
637 ssh might not work if you don't.
640 The ed driver has been updated. It now allows mii attachments,
641 which means that you must include the miibus in your kernel if
642 you use the ed driver.
645 The problems with libc have been corrected. It is now mostly
646 safe to go back into the water.
649 The size of FILE was changed. This breaks upgrading. If
650 you must upgrade, be prepared for pain. It also breaks almost
651 all binaries that you've compiled on -current. You are warned
652 that before upgrading would be a good time to do a level 0
653 dump of your system. No, really, I mean it this time.
655 To get to the new system, you'll need to use the following
656 workaround. Hopefully this can be sorted out so that we
657 don't have to move this to the updating section.
659 To get around the installworld problem, do:
660 # cd /usr/src/usr.bin/sed
664 If that doesn't work, then try:
665 # make -k installworld
669 DEVFS is now the default. If you use vinum, make sure that you
670 do not include devfs in your kernel as problems result.
673 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
674 Remove them from your config.
677 ****************************** WARNING ******************************
678 buildkernel has been changed slightly
679 ****************************** WARNING ******************************
680 KERNCONF replaces the variable KERNEL for buildkernel. You
681 should update your scripts and make.conf accordingly.
684 config has changed to allow DEV_FOO as a replacement for NFOO.
685 This requires a new config to build correctly.
688 The kernel option I386_CPU is now mutually exclusive with the
689 other cpu types. If you have an i386 system, be sure that it
690 only had this line. Remove it for all other configurations.
693 Changes to the kernel require it and burncd be in sync.
696 Everyone who has hw.sndunit set to something in
697 /etc/sysctl.conf, it is now hw.snd.unit.
700 ex and vi were broken by some changes to sys/queue.h. If you
701 have a bad vi, you will see make buildworld fail with a core
702 dump while building termcap. You can work around this problem
703 by adding -k to your make buildworld. This will cause the
704 build to complete and install a new vi. Once that's done, you
705 can rebuild again without the -k to pick up anything that
706 might have been ignored by the -k option.
708 Others have suggested that you can just rebuild libc if your
709 vi/ex is dynamically linked, but I've not received any reports
713 There have been some changes to libcrypt in -current. The
714 libscrypt/libdescrypt symlink silliness is gone and the installed
715 libcrypt is fully functional. Be aware of this.
718 Linksys Fast Ethernet PCCARD cards supported by the ed driver
719 now require the addition of flag 0x80000 to their config line
720 in pccard.conf(5). This flag is not optional. These Linksys
721 cards will not be recognized without it.
724 Important new FreeBSD-version stuff: PAM support has been worked
725 in, partially from the "Unix" OpenSSH version. This requires
726 adding the following in pam.conf:
728 sshd auth sufficient pam_skey.so
729 sshd auth required pam_unix.so try_first_pass
730 sshd session required pam_permit.so
736 The random device needs more entropy, so you need to make sure
737 that you've run mergemaster to get a /etc/rc which will seed
738 /dev/random. If you don't and the system hangs after ldconfig,
739 then banging on the keyboard randomly until it unhangs is one
743 ****************************** WARNING ******************************
744 Sendmail has been updated.
745 ****************************** WARNING ******************************
746 o mail.local(8) is no longer installed as a set-user-id binary.
747 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
749 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
751 o Now using sendmail's version of vacation(1).
752 o The sendmail cf building tools (contrib/sendmail/cf) are installed
753 in /usr/share/sendmail/cf.
754 o sendmail.cw changed to local-host-names
756 More details can be found at
757 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
760 The ports tree's new layout is in place. Be sure to update
761 your entire ports tree, or you will have problems.
764 The perl build procedure no longer installs miniperl, nor uses
765 the installed miniperl. It is recommended that you delete
769 This weekend the ports tree will be updated to a new layout.
770 It will be in an inconsistent state until noted in the UPDATING
771 file, or with asami-san's message to the relevant mailing
772 lists. With this new layout, you'll need to update the whole
773 tree for anything to work.
776 There was a change in the passwd format. Need more information.
779 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
780 place. Please update boot loader (not the boot blocks) at the
781 same time as your kernel.
784 The new pmtimer device is necessary for laptops. Failure to
785 include the device will cause suspended laptops losing time
786 when they resume. Include
788 in your config file and
789 hint.pmtimer.0.at="isa"
790 to your /boot/device.hints file.
793 The random device has been turned into a (pseudo-)device,
794 rather than an option. The supplied kernel config files have
795 been updated. You will need to do something similar in your
796 own kernel config file.
801 If you prefer to load the loadable module, you need to do
805 The random device module has been renamed from randomdev.ko to
806 random.ko. You will need to edit your /boot/loader.conf to
807 reflect this if you load this module at boot time.
808 The line should read:
812 The SMPNG commit has happened. It should work, but if it
813 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
814 to be a variety of minor issues. Please see 20000905 to make
815 sure you don't have model loading problems which might at
816 first blush appear related to SMP.
819 nsswitch has been imported from NetBSD. Among other things,
820 this means that /etc/host.conf is no longer used. See
821 nsswitch.conf(5) instead. Note that at boot time rc.network
822 will attempt to produce a new nsswitch.conf file for you if you
823 don't have one, and you have host.conf.
826 The ucred structure changed size. This breaks the interface
827 that mountd uses. Trying to use an older mountd with a newer
828 kernel guarantees a panic. This means that you need to use
829 kernels newer than today only with matching mountd, but you
830 needed to do that anyway with the boot loader changes.
833 The boot loader has been updated. The new default kernel is
834 now /boot/kernel/kernel.ko. The new default module location
837 You *MUST* upgrade your boot loader and kernel at the same time.
838 The easiest way to do this is to do the buildworld/buildkernel/
839 installkernel/installworld dance.
841 Furthermore, you are urged to delete your old /modules directory
842 before booting the new kernel, since kldload will find stale
843 modules in that directory instead of finding them in the correct
844 path, /boot/kernel. The most common complaint that this cures
845 is that the linux module crashes your machine after the update.
847 if [ ! -d /boot/kernel.old ]; then
848 mv /modules.old /boot/kernel.old
849 chflags noschg /kernel.old
850 mv /kernel.old /boot/kernel.old/kernel.ko
851 chflags schg /boot/kernel.old/kernel.ko
855 A new issue with the sendmail upgrade has come to light.
856 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
857 incorrectly install the default aliases in /etc/mail rather than
858 move the old one from /etc. So you'll need to manually move the
859 file, create a symbolic link, remove the old /etc/aliases.db and
860 run newaliases. For safety sake, you should stop sendmail
861 while doing this and run the upgrade when locally sourced email
862 is not likely to be generated.
865 /boot/device.hints is now required for installkernel to
866 succeed. You should copy GENERIC.hints for your architecture
867 into /boot/device.hints. If and only if you compile hints
868 into your kernel, then this file may be empty. Please note,
869 if you have an empty or missing /boot/device.hints file and
870 you neglected to compile hints into your kernel, no boot
871 messages will appear after the boot loader tries to start the
875 If you do NOT have ``options RANDOMDEV'' in your kernel and
876 you DO want the random device then add randomdev_load="YES" to
880 suidperl is now always built and installed on the system, but
881 with permissions of 511. If you have applications that use
882 this program, you are now required to add ENABLE_SUIDPERL=true
883 to /etc/make.conf. If you forget to do this,
884 chmod 4511 /usr/bin/suidperl
885 will fix this until the next build.
888 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
889 visible changes that may immediately affect your configuration
891 - New default file locations from src/contrib/sendmail/cf/README
892 - newaliases limited to root and trusted users
893 - MSA port (587) turned on by default
894 - New queue file naming system so can't go from 8.11 -> 8.9
895 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
896 - FEATURE(`nullclient') is more full featured
897 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
898 - mail.local FreeBSD-only -b option changed to -B
899 - See src/contrib/sendmail/RELEASE_NOTES for more info
902 suidperl (aka sperl) is no longer build by default. You must
903 specifically define BUILD_SUIDPERL to "true" for it to be build.
904 Furthermore, we recommend that you remove /usr/bin/sperl* and
905 /usr/bin/suidperl files from your system unless you have a
909 Networking defaults have been tightened. Anybody upgrading
910 /etc/defaults/rc.conf needs to add the following lines to
911 /etc/rc.conf if they want to have the same setup
912 afterwards (unless the variables already are set, of course):
913 # Enable network daemons for user convenience.
916 sendmail_enable="YES"
919 If you have null_load="YES" in your /boot/loader.conf, you
920 will need to change that to nullfs_load="YES".
923 The "installkernel" target has changed slightly. Now even if
924 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
925 it will install the MYKERNEL file (built with the buildkernel
926 target) as /kernel rather than /MYKERNEL. Those who have
927 updated their /boot/loader.conf files to point to /MYKERNEL
928 should remove that entry or perform manual rename of /kernel
932 If you use CVSUP or CTM to get CVS trees, AND you used to get
933 the old crypto files from internat.freebsd.org AND you check
934 out files from the CVS tree with the cvs command, please read
935 http://people.freebsd.org/~imp/internat.txt
936 for details on potential problems that you might have and how
939 If you are merely a mirror, or don't answer yes to each of the
940 clauses above, you needn't worry.
943 /etc/security has been updated to print the inode number of
944 setuid programs that have changed. You will see a large spike
945 in the number of changed programs the first time when you run
946 mergemaster to get a new /etc/security.
949 /dev/random now has good entropy collection (from the keyboard
950 and sysmouse drivers). Please ensure that either `options
951 RANDOMDEV' is present in your kernel config file or that
952 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
953 not have the /dev/random driver, OpenSSL (and consequently
954 lots of crypto tools (like SSH)) will fail with strange
955 errors. (see below, 20000624).
957 FreeBSD-current is safe again to run Crypto.
960 phk made the malloc default options AJ. This may slow things
961 down and uncover other latent bugs in the code. If you need to
962 run at full speed, you can disable this by doing the following:
963 ln -s aj /etc/malloc.conf
966 libftpio's version was accidentally bumped a few days ago. This
967 has been corrected. You may need to remove /usr/lib/libftpio.so.6
968 before doing your next buildworld/installworld pair. It certainly
969 won't hurt to remove it before the update procedure. It will
970 break fetch until a new one is built, but ftp can be used in the
974 The crypto packages have changed for the cvsup. This has been done
975 in a backward compatible way, but the old packages will go away at
976 some point in the future. Look at /usr/share/examples/cvsup for
980 With the new sys/modules/sound/drivers/*, you will need to
981 set SYSDIR until you do an installworld after July 7th.
984 rc.shutdown and rc will now call the rc.d scripts with start
985 or stop. This may cause some harmless warnings from older
986 rc.d scripts that haven't been updated.
989 The libfetch based version of fetch has gone into the tree.
990 Minor problems may result on some of the less popular sites,
991 which should be reported to des@freebsd.org.
994 From approximately this date forward, one must have the crypto
995 system installed in order to build the system and kernel.
996 While not technically strictly true, one should treat it as
997 required and grab the crypto bits. If you are grabbing CVS
998 trees, src-all and cvs-crypto should be treated as if they
999 were required. You should check with the latest collections
1000 to make sure that these haven't changed.
1003 Mark Murray just committed the first parts of a cleanup of
1004 /dev/zero, et al. This is also cleaning up /dev/random.
1005 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
1006 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
1007 until Mark can merge in the fixes to this work in progress.
1008 openssh and openssl should not be used to generate keys from this
1009 date to the completion of the work.
1011 If you must operate at this reduced level of security, add '
1012 options RANDOMDEV' to your kernel or modload the randomdev
1013 module. You may also need to copy a new MAKEDEV to /dev and
1014 recreate the random and urandom devices.
1017 The license on the softupdates is now a standard 2 clause
1018 BSD license. You may need to remove your symbolic links
1019 that used to be required when updating.
1022 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
1023 the config file update procedure.
1024 http://people.freebsd.org/~imp/config-upd.html
1025 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
1026 isn't buildable. However, you can generate a LINT file:
1027 cd /sys/<ARCH>/conf && make LINT
1030 Binutils 2.10 have hit the tree, or will shortly. As soon
1031 as they do, the problem noted in 20000522 will be resolved and
1032 that workaround will no longer be required.
1035 phk removed the compatibility creation of wd devices in the
1036 ad driver. If you haven't done so already, you must update
1037 your fstab, etc to use the ad devices instead of the wd
1040 In addition, you'll need to update your boot blocks to a
1041 more modern version, if you haven't already done so. Modern
1042 here means 4.0 release or newer (although older releases
1046 Peter took an axe to config(8). Be sure that you read his mail
1047 on the topic before even thinking about updating. You will
1048 need to create a /boot/device.hints or add a hints directive
1049 to your config file to compile them in statically. The format
1050 of the config file has changed as well. Please see GENERIC or
1051 NEWCARD for examples of the new format.
1053 Indirectly, this also breaks USERCONFIG. Unless a newer entry
1054 says that it has been fixed, assume that must use the hints mechanism
1055 in the loader if you need to use a machine with very old ISA cards
1059 A new set of binutils went into the tree today. Anybody
1060 building a kernel after this point is advised that they need
1061 to rebuild their binutils (or better yet do a
1062 buildworld/installworld) before building a new kernel.
1064 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
1065 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
1066 is recommended that you don't set this option until the problem
1070 The ethernet drivers were all updated to clean up the BPF handling.
1073 The problems with boot blocks on the alphas have been corrected.
1074 This will require some care in updating alphas. A new libstand
1075 is requires for the boot blocks to build properly.
1078 Recompile all kld modules. Proper version dependency info
1082 Modules have been disconnected from the buildworld tree and
1083 connected to the kernel building instead.
1086 You may need to build gperf
1087 cd /usr/src/gnu/usr.bin/gperf && make depend all install
1088 when upgrading from 4.0 -> current. The build system now uses
1089 an option only in -current.
1092 The method that we brand ELF binaries has changed to be more
1093 acceptable to the binutils maintainers. You will need to
1094 rebrand your ELF binaries that aren't native. One problem
1095 binary is the Linux ldconfig. After your make world, but
1096 before you reboot, you'll need to issue:
1097 brandelf -t Linux /compat/linux/sbin/ldconfig
1098 if you have Linux compatibility enabled on your machine.
1101 If you have really bad/marginal IDE drives, you may find they
1102 don't work well. Use pio mode instead. The easiest way to
1103 cope if you have a problem combination is to add:
1104 /sbin/sysctl hw.ata.ata_dma=0
1105 to the start of /etc/rc.conf.
1108 The ISA and PCI compatibility shims have been connected to the
1109 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
1110 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
1111 include the appropriate option in your kernel config. Drivers
1112 using the shims should be updated or they won't ship with
1113 5.0-RELEASE, targeted for 2001.
1116 We've entered the traditional post release dumping party.
1117 Large kernel changes are being committed and are in the
1118 works. It is important to keep the systems' klds and kernel
1119 in sync as kernel interfaces and structures are changing.
1120 Before reporting kernel panics, make sure that all modules
1121 that you are loading are up to date.
1124 If you are upgrading from an older version of FreeBSD, you
1125 need to update your boot blocks as well. 'disklabel -B ad0'
1126 will do the trick. This isn't critical until you remove your
1127 wd device entries in /dev, at which point your system will not
1131 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
1132 to upgrade to 4.0 from 3.x.
1138 Avoid using make -j when upgrading. From time to time in the
1139 past there have been problems using -j with buildworld and/or
1140 installworld. This is especially true when upgrading between
1141 "distant" versions (eg one that cross a major release boundary
1142 or several minor releases, or when several months have passed
1143 on the -current branch).
1145 Sometimes, obscure build problems are the result of environment
1146 poisoning. This can happen because the make utility reads its
1147 environment when searching for values for global variables.
1148 To run your build attempts in an "environmental clean room",
1149 prefix all make commands with 'env -i '. See the env(1) manual
1150 page for more details.
1154 If you are updating from a prior version of FreeBSD (even one just
1155 a few days old), you should follow this procedure. With a
1156 /usr/obj tree with a fresh buildworld,
1157 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1158 make installkernel KERNCONF=YOUR_KERNEL_HERE
1160 To just build a kernel when you know that it won't mess you up
1161 --------------------------------------------------------------
1162 cd src/sys/{i386,alpha}/conf
1163 config KERNEL_NAME_HERE
1164 cd ../../compile/KERNEL_NAME_HERE
1169 If this fails, go to the "To build a kernel" section.
1171 To rebuild everything and install it on the current system.
1172 -----------------------------------------------------------
1173 # Note: sometimes if you are running current you gotta do more than
1174 # is listed here if you are upgrading from a really old current.
1176 <make sure you have good level 0 dumps>
1177 <maybe fix /etc/fstab> [7]
1179 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1180 make installkernel KERNCONF=YOUR_KERNEL_HERE
1182 <reboot in single user> [3]
1189 To cross-install current onto a separate partition
1190 --------------------------------------------------
1191 # In this approach we use a separate partition to hold
1192 # current's root, 'usr', and 'var' directories. A partition
1193 # holding "/", "/usr" and "/var" should be about 2GB in
1196 <make sure you have good level 0 dumps>
1199 <maybe newfs current's root partition>
1200 <mount current's root partition on directory ${CURRENT_ROOT}>
1201 make installworld DESTDIR=${CURRENT_ROOT}
1202 make buildkernel KERNCONF=YOUR_KERNEL_HERE
1203 cp /usr/src/sys/${ARCH}/conf/GENERIC.hints \
1204 ${CURRENT_ROOT}/boot/device.hints # as needed
1205 make installkernel KERNCONF=YOUR_KERNEL_HERE DESTDIR=${CURRENT_ROOT}
1206 cd /usr/src/etc; make distribution DESTDIR=${CURRENT_ROOT} # if newfs'd
1207 cp /etc/fstab ${CURRENT_ROOT}/etc/fstab # if newfs'd
1208 <edit ${CURRENT_ROOT}/etc/fstab to mount "/" from the correct partition>
1209 <reboot into current>
1210 <do a "native" rebuild/install as described in the previous section>
1211 <maybe install compatibility libraries from /usr/src/lib/compat>
1215 To upgrade in-place from 4.x-stable to current
1216 ----------------------------------------------
1217 # 5.x uses more space than 4.x. Also, the location of kernel
1218 # modules has changed. If you are installing 5.0 onto a 4.x
1219 # system, you'll need about 30MB of free disk space on your /
1220 # partition. If you have less than this, you may encounter difficult
1221 # to back out of problems with this procedure. If /tmp is on
1222 # the / partition, you may want to completely remove all its content
1223 # before upgrading, as this can be a common source of shortage of
1226 <make sure you have good level 0 dumps>
1227 <maybe fix /etc/fstab> [7]
1229 make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
1230 cp src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints [2]
1231 make installkernel KERNCONF=YOUR_KERNEL_HERE
1232 cd src/sys/boot ; make install [6]
1234 <reboot in single user> [3]
1236 rm -rf /usr/include/g++
1241 Make sure that you've read the UPDATING file to understand the
1242 tweaks to various things you need. At this point in the life
1243 cycle of current, things change often and you are on your own
1244 to cope. The defaults can also change, so please read ALL of
1245 the UPDATING entries.
1247 Also, if you are tracking -current, you must be subscribed to
1248 freebsd-current@freebsd.org. Make sure that before you update
1249 your sources that you have read and understood all the recent
1250 messages there. If in doubt, please track -stable which has
1251 much fewer pitfalls.
1253 [1] If you have third party modules, such as vmware, you
1254 should disable them at this point so they don't crash your
1257 [2] If you have legacy ISA devices, you may need to create
1258 your own device.hints to reflect your unique hardware
1261 [3] From the bootblocks, boot -s, and then do
1266 adjkerntz -i # if CMOS is wall time
1267 Also, when doing a major release upgrade, it is required that
1268 you boot into single user mode to do the installworld.
1269 For the 4.x -> 5.0 upgrade, you will also see many messages about
1270 needing to recompile your userland. These are harmless and can
1271 be ignored while you proceed to the next step.
1273 [4] Note: This step is non-optional. Failure to do this step
1274 can result in a significant reduction in the functionality of the
1275 system. Attempting to do it by hand is not recommended and those
1276 that pursue this avenue should read this file carefully, as well
1277 as the archives of freebsd-current and freebsd-hackers mailing lists
1278 for potential gotchas.
1280 [5] Usually this step is a noop. However, from time to time
1281 you may need to do this if you get unknown user in the following
1282 step. It never hurts to do it all the time. You may need to
1283 install a new mergemaster (cd src/usr.sbin/mergemaster && make
1284 install) after the buildworld before this step if you last updated
1285 from current before 20020224 or from -stable before 20020408.
1287 [6] 4.x boot loader can be used to boot a 5.x system, however
1288 it is difficult to do that at best. If you wish to try, then
1289 you should interrupt the boot and at the ok prompt type:
1291 ok boot /boot/kernel/kernel
1292 If this fails to work, you must install a new boot loader as
1295 [7] Before you upgrade, please make sure that you are not using
1296 compatibility slices. These are device names of the form, on i386
1297 and other architectures that use MBR slicing, /dev/ad0a without the
1298 actual slice name. Chances are excellent that these will break.
1299 You generally must update these entries to use the post FreeBSD
1300 2.x form of /dev/ad0s1a.
1302 [8] In order to have a kernel that can run the 4.x binaries
1303 needed to do an installworld, you must include the COMPAT_FREEBSD4
1304 option in your kernel. Failure to do so may leave you with a system
1305 that is hard to boot to recover.
1307 [9] When checking out sources, you must include the -P flag to have
1308 cvs prune empty directories.
1311 This file contains a list, in reverse chronological order, of major
1312 breakages in tracking -current. Not all things will be listed here,
1313 and it only starts on March 15, 2000. Updating files can found in
1314 previous releases if your system is older than this.
1316 Copyright information:
1318 Copyright 1998, 2002 M. Warner Losh. All Rights Reserved.
1320 Redistribution, publication, translation and use, with or without
1321 modification, in full or in part, in any form or format of this
1322 document are permitted without further permission from the author.
1324 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
1325 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
1326 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
1327 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
1328 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
1329 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
1330 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
1331 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
1332 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
1333 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
1334 POSSIBILITY OF SUCH DAMAGE.
1336 If you find this document useful, and you want to, you may buy the
1339 Contact Warner Losh if you have any questions about your use of