1 Updating Information for FreeBSD current users
3 This file is maintained and copyrighted by M. Warner Losh
4 <imp@village.org>. Please send new entries directly to him. See end
5 of file for further details. For commonly done items, please see the
6 COMMON ITEMS: section later in the file.
8 NOTE TO PEOPLE WHO THINK THAT 5.0-CURRENT IS SLOW:
9 FreeBSD 5.0-CURRENT has many debugging features turned on, in
10 both the kernel and userland. These features attempt to detect
11 incorrect use of system primitives, and encourage loud failure
12 through extra sanity checking and fail stop semantics. They
13 also substantially impact system performance. If you want to
14 do performance measurement, benchmarking, and optimization,
15 you'll want to turn them off. This includes various WITNESS-
16 related kernel options, INVARIANTS, malloc debugging flags
17 in userland, and various verbose features in the kernel. Many
18 developers choose to disable these features on build machines
19 to maximize performance.
21 In addition, IDE write caching is currently disabled by default
22 due to on-going concerns about disk write order and file system
23 integrity. Re-enabling write caching can substantially improve
27 Warnings are now errors in the kernel. Unless you are a developer,
28 you should add -DNO_WERROR to your make line.
31 sendmail 8.12.2 has been imported. The sendmail binary is no
32 longer a set-user-ID root binary and the infrastructure to support
33 command line mail submission has changed. Be sure to run
34 mergemaster (especially for updating /etc/rc, /etc/defaults/rc.conf,
35 and /etc/mail) and read /etc/mail/README for more details.
38 The preferred configuration method for PAM is now /etc/pam.d/
39 rather than /etc/pam.conf. If you have an unmodified
40 pam.conf, just delete it after your next mergemaster run. If
41 you have local modifications, you can use
42 /usr/src/etc/pam.d/convert.pl to incorporate them into your
45 Please see the following url for more details:
46 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<xzp6667fyoa.fsf@flood.ping.uio.no>
49 If anyone here is already using the new rc.conf(5) variable
50 networkfs_types, please note that it has changed
51 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<9744.1009655556@axl.seasidesoftware.co.za>
54 sys/i4b/driver/i4b_ispppsubr.c has been retired. This file
55 started out its life in the ISDN4BSD project as an offspring
56 from sys/net/if_spppsubr.c, which eventually got a life of its
57 own. All the accumulated features and bugfixes of the i4b
58 version have now been merged back into the base system's
59 version now. The only user-visible change resulting from this
60 is that i4b's sppp(4) interfaces are to be managed with
61 spppcontrol(8) again, since ispppcontrol(8) has been retired
62 as well. (There has never been rc file support for
63 ispppcontrol in -current, but only in -stable. That will be
64 reverted by the time the changes are MFCed.)
67 The fdc(4) driver has been updated and now automatically
68 recognizes media in `standard' formats (like 1440 KB and
69 720 KB for a 3.5" high-density drive) when accessing the
70 default device node (e. g. /dev/fd0). The old variety of
71 floppy device nodes /dev/fd*.* is no longer present by
72 default, devices can be created (in DEVFS) on demand. They
73 will need to be customized then for `odd' densities using
77 The bugs in procfs' debugging support code have been fixed,
78 and truss(1) now works again.
81 Daily security checks have been split out to use the periodic(8)
82 scripts. Some change in configuration may be necessary. Please
84 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
88 sos added VCD/SVCD support to ata driver and that needs the
89 kernel and burncd to be in sync.
92 The procfs pseudo-filesystem has now been converted to use the
93 pseudofs framework. If you have 'options PROCFS' in your
94 kernel config, you'll need to add 'options PSEUDOFS' if it's
97 This change temporarily breaks truss(1); use ktrace(1) instead
98 until the issue has been resolved.
101 A security hole in OpenSSH involving `UseLogin yes' has been
105 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
106 after this date. You need to do this only once.
109 Most of the awk issues have been resolved. Some rough
110 edges may be left, but for the most part things should be
111 back to "normal." For CURRENT's usual definition of "normal."
114 Awk has been upgraded to the one true awk from bell labs. Expect
115 choppy waves in the upgrade process.
118 The asr driver problem has been resolved.
121 Due to changes in other parts of the system, the asr driver
122 now causes the system to panic on boot. Do not use it pending
123 correction. Comment it out of any kernel config file that you
124 try to use from this date forward.
127 When crossbuilding, use TARGET=xxx where you used to use
128 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
129 unless you are changing both of them. To cross build pc98 on
130 an alpha, for example, you need to set TARGET=pc98 and
134 The kernel interface that burncd depends on has changed.
135 You must recompile both the kernel and userland applications
139 When crossbuilding, please set TARGET_ARCH rather than
140 MACHINE_ARCH to indicate the target. In the future, one will
141 set TARGET_MACHINE where you set MACHINE now. At the moment,
142 setting MACHINE alone for same MACHINE_ARCH machines works
143 (eg, you can build pc98 on a i386 machine and vice versa).
146 Some weird problems result from using ACPI on some machines.
147 To disable ACPI you can add
148 hint.acpi.0.disable="1"
149 to /boot/loader.conf (or by putting set X=Y at the boot
152 Alternatively, you can remove it from /boot/kernel/acpi.ko
153 or use the MODULES_OVERRIDE function in your kernel config
154 file and not list acpi in that list.
157 The buildworld has been fixed. You may need to install
158 the 4.x compatibility libraries for some old binaries
159 to work. Add COMPAT4X=true to your /etc/make.conf to
160 get them installed on every installworld, or execute the
161 following to get them installed only once:
162 cd src/lib/compat/compat4x.<arch>
164 You will see ``__stdoutp undefined'' until you do this.
167 There's a bug in the world build process. The cross-tools
168 are build with the NEW headers, but the OLD libc.a. This
169 leads to all kinds of problems with the new libc. A temporary
171 CFLAGS="-O -pipe -D_OLD_STDIO"
172 before building world when upgrading from 4.x to current. This
173 can be removed afterwards.
175 A proper fix to the buildworld target is needed.
178 Peter has committed his new kthread nfs client/server code.
179 NFS may be unstable after this date.
182 KSE has hit the tree. Lots of things are now different in
183 the kernel. While a few problems were introduced in the
184 initial commit, most of the major ones have been found and
188 In OLDCARD, CardBus bridges appear to be stable. The work
189 arounds described in the 20010604 entry are now no longer
190 necessary and will be ignored. Most insert/remove problems
191 have been rectified around this date.
194 named now runs as user bind and group bind rather than as
195 root. If named_enable is set to YES in /etc/rc.conf, ensure
196 that user bind is available in /etc/passwd (using vipw(8))
197 and that group bind is available in /etc/group. Also make
198 sure that user or group bind has read (and not write)
199 permission for your name server configuration and that it
200 has read and write permission for your slave zone files and
203 If you wish to continue to run named as root (a less secure
204 alternative), add a line to /etc/rc.conf saying
209 The PAM libraries have had an API upgrade that is beyond
210 the ability of the shared library major number to handle.
211 It is manifested by PAM-using ports dumping core. The
212 solution is to rebuild those ports.
215 The kernel compile module has moved from src/sys/compile/FOO
216 to src/sys/${MACHINE}/compile/FOO.
219 The pccard modem issue from 20010613 has been corrected.
220 OLDCARD support is still a little weak in -current. slot 1 is
221 known not to work on some TI based cardbus bridges. Some
222 cardbus bridges do not properly detect insert/removal events.
223 IRQ configuration needs more safety belts.
226 Softupdates problems have been corrected.
229 Peter ripped out the linkerset support. You must, as always,
230 rerun config after you cvsup if you are using the traditional
231 kernel building methods.
234 pccard modems may not work with current after 20010604 date. Some
235 do, others result in panics. *MAKE*SURE* that you update your
236 config and /etc/rc.conf ala the 20010604 entry, or you will have
237 problems (this issue will be fixed, it just hasn't been yet).
240 SOFTUPDATES seem to be broken since the middle of May or so. Do not
241 use them in current. You can disable softupdates on all mounted
242 partitions, or remove SOFTUPDATES the kernel config file.
245 After Peter's commits to the hints code, people have been noticing
246 that certain devices are attached (or try to) twice. This is due
247 to having both static hints as well as a /boot/device.hints. To
248 work around this issue, please use only one or the other mechanism
249 until this bug is fixed.
251 Please note that a feature of config is that if you have config
252 file FOO and FOO.hints, it automatically adds FOO.hints to the
253 hints.c file, wheather you want it to or not.
256 Locale names have changed to match other systems better.
259 pccard support for pci cards has been committed. You must change
260 your /etc/pccard.conf irq lines. It must match the irq used by
261 pcic device. Interrupt storms may result if you fail to do this.
262 Interrupt storms look a lot like a hang.
264 You must also install a new pccardd, otherwise you will get an
265 interrupt storm at card reset time (just after it tells you what
268 pccardd_flags="-I" is necessary for the time being. It tells pccardd
269 not to ask the kernel if the interrupt is really free or not before
270 using it. You can either change the /etc/pccard.conf irq lines to
271 match pcic, or add "-i X" to the pccardd_flags.
274 INSTALL=install -C is being deprecated. If you want to do this,
275 use COPY=-C instead. The former method will be supported for only
276 a limited time. If you see
278 install: warning: the -d and -C options may not be specified together
280 in your makeworld, then you need to migrate towards using
284 It appears that vm is now stable enough to use again. However,
285 there may be other problems, so caution is still urged. alpha
286 definitely is in bad shape.
289 Minor repo damange has happened. This may cause problems
290 with cvsup of ports. If you get errors, please see
291 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
292 at the bottom for details on a workaround. The error message
294 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
297 Vm and/or swapping are busted on -current. Please be patient.
300 pccard has had much reorganizational work done to it over
301 the past few days. Everything should still work, but if
302 not, please contact imp@freebsd.org.
305 ata ioctl changed. Make sure to recompile both kernel and
306 userland at the same time.
309 New ncurses imported.
312 DEVFS is now opt out, not opt in. Barring major problems, this
313 will be the only way to go starting July 1.
316 OpenSSH has been updated to 2.9. Some defaults are different,
317 including RhostsRSAAuthentication, which changes from yes to no.
320 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
323 Building perl was broken at 02:25:25 PDT.
326 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
327 go back in the water.
330 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
331 this date, but before the correction date.
334 old fsck and new kernel interactions appear to have been fixed.
337 fsck and the kernel were changed to handle some optimizations
338 to directory layout. This breaks backward compatibility.
339 Update only if you understand that you must not use the old
340 fsck with the new kernel ever.
343 fsck has changed the meaning of the pass column in /etc/fstab.
344 Please see the cvs commit to fsck.8 or the fsck.8 man page for
345 details. It is unclear if changes to /etc/fstab are necessary.
348 portmap had changed name to rpcbind for maximum POLA in your
349 current world. /etc/hosts.{allow,deny} needs changes. nfs and
350 other rpc based programs that rely on portmapper will not work
351 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
354 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
355 and ATA_ENABEL_TAGS are no longer kernel options. They have
356 been replaced by tunables. See ata.4 for details.
359 The fxp driver was converted to use miibus. If you compile
360 fxp into your kernel statically, you will need to add miibus.
363 The wi device now defaults to BSS (infrastructure) mode
367 /dev/urandom should be a symbolic link to /dev/random now.
368 Users of current not using DEVFS need to run MAKEDEV std.
369 ssh might not work if you don't.
372 The ed driver has been updated. It now allows mii attachments,
373 which means that you must include the miibus in your kernel if
374 you use the ed driver.
377 The problems with libc have been corrected. It is now mostly
378 safe to go back into the water.
381 The size of FILE was changed. This breaks upgrading. If
382 you must upgrade, be prepared for pain. It also breaks almost
383 all binaries that you've compiled on -current. You are warned
384 that before upgrading would be a good time to do a level 0
385 dump of your system. No, really, I mean it this time.
387 To get to the new system, you'll need to use the following
388 workaround. Hopefully this can be sorted out so that we
389 don't have to move this to the updating section.
391 To get around the installworld problem, do:
392 # cd /usr/src/usr.bin/sed
396 If that doesn't work, then try:
397 # make -k installworld
401 DEVFS is now the default. If you use vinum, make sure that you
402 do not include devfs in your kernel as problems result.
405 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
406 Remove them from your config.
409 ****************************** WARNING ******************************
410 buildkernel has been changed slightly
411 ****************************** WARNING ******************************
412 KERNCONF replaces the variable KERNEL for buildkernel. You
413 should update your scripts and make.conf accordingly.
416 config has changed to allow DEV_FOO as a replacement for NFOO.
417 This requires a new config to build correctly.
420 The kerrnel option I386_CPU is now mutually exclusive with the
421 other cpu types. If you have an i386 system, be sure that it
422 only had this line. Remove it for all other configurations.
425 Changes to the kernel require it and burncd be in sync.
428 Everyone who has hw.sndunit set to something in
429 /etc/sysctl.conf, it is now hw.snd.unit.
432 ex and vi were broken by some changes to sys/queue.h. If you
433 have a bad vi, you will see make buildworld fail with a core
434 dump while building termcap. You can work around this problem
435 by adding -k to your make buildworld. This will cause the
436 build to complete and install a new vi. Once that's done, you
437 can rebuild again without the -k to pick up anything that
438 might have been ignored by the -k option.
440 Others have suggested that you can just rebuild libc if your
441 vi/ex is dynamically linked, but I've not received any reports
445 There have been some changes to libcrypt in -current. The
446 libscrypt/libdescrypt symlink sillyness is gone and the installed
447 libcrypt is fully functional. Be aware of this.
450 Linksys Fast Ethernet PCCARD cards supported by the ed driver
451 now require the addition of flag 0x80000 to their config line
452 in pccard.conf(5). This flag is not optional. These Linksys
453 cards will not be recognized without it.
456 Important new FreeBSD-version stuff: PAM support has been worked
457 in, partially from the "Unix" OpenSSH version. This requires
458 adding the following in pam.conf:
460 sshd auth sufficient pam_skey.so
461 sshd auth required pam_unix.so try_first_pass
462 sshd session required pam_permit.so
468 The random device needs more entropy, so you need to make sure
469 that you've run mergemaster to get a /etc/rc which will seed
470 /dev/random. If you don't and the system hangs after ldconfig,
471 then banging on the keyboard randomly until it unhangs is one
475 ****************************** WARNING ******************************
476 Sendmail has been updated.
477 ****************************** WARNING ******************************
478 o mail.local(8) is no longer installed as a set-user-id binary.
479 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
481 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
483 o Now using sendmail's version of vacation(1).
484 o The sendmail cf building tools (contrib/sendmail/cf) are installed
485 in /usr/share/sendmail/cf.
486 o sendmail.cw changed to local-host-names
488 More details can be found at
489 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
492 The ports tree's new layout is in place. Be sure to update
493 your entire ports tree, or you will have problems.
496 The perl build procedure no longer installs miniperl, nor uses
497 the installed miniperl. It is recommended that you delete
501 This weekend the ports tree will be updated to a new layout.
502 It will be in an inconsistent state until noted in the UPDATING
503 file, or with asami-san's message to the relevant mailing
504 lists. With this new layout, you'll need to update the whole
505 tree for anything to work.
508 There was a change in the passwd format. Need more information.
511 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
512 place. Please update boot loader (not the boot blocks) at the
513 same time as your kernel.
516 The new pmtimer device is necessary for laptops. Failure to
517 include the device will cause suspended laptops losing time
518 when they resume. Include
520 in your config file and
521 hint.pmtimer.0.at="isa"
522 to your /boot/device.hints file.
525 The random device has been turned into a (pseudo-)device,
526 rather than an option. The supplied kernel config files have
527 been updated. You will need to do something similar in your
528 own kernel config file.
533 If you prefer to load the loadable module, you need to do
537 The random device module has been renamed from randomdev.ko to
538 random.ko. You will need to edit your /boot/loader.conf to
539 reflect this if you load this module at boot time.
540 The line should read:
544 The SMPNG commit has happened. It should work, but if it
545 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
546 to be a variety of minor issues. Please see 20000905 to make
547 sure you don't have model loading problems which might at
548 first blush appear related to SMP.
551 nsswitch has been imported from NetBSD. Among other things,
552 this means that /etc/host.conf is no longer used. See
553 nsswitch.conf(5) instead. Note that at boot time rc.network
554 will attempt to produce a new nsswitch.conf file for you if you
555 don't have one, and you have host.conf.
558 The ucred structure changed size. This breaks the interface
559 that mountd uses. Trying to use an older mountd with a newer
560 kernel guarantees a panic. This means that you need to use
561 kernels newer than today only with matching mountd, but you
562 needed to do that anyway with the boot loader changes.
565 The boot loader has been updated. The new default kernel is
566 now /boot/kernel/kernel.ko. The new default module location
569 You *MUST* upgrade your boot loader and kernel at the same time.
570 The easiest way to do this is to do the buildworld/buildkernel/
571 installkernel/installworld dance.
573 Furthermore, you are urged to delete your old /modules directory
574 before booting the new kernel, since kldload will find stale
575 modules in that directory instead of finding them in the correct
576 path, /boot/kernel. The most common complaint that this cures
577 is that the linux module crashes your machine after the update.
579 if [ ! -d /boot/kernel.old ]; then
580 mv /modules.old /boot/kernel.old
581 chflags noschg /kernel.old
582 mv /kernel.old /boot/kernel.old/kernel.ko
583 chflags schg /boot/kernel.old/kernel.ko
587 A new issue with the sendmail upgrade has come to light.
588 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
589 incorrectly install the default aliases in /etc/mail rather than
590 move the old one from /etc. So you'll need to manually move the
591 file, create a symbolic link, remove the old /etc/aliases.db and
592 run newaliases. For safety sake, you should stop sendmail
593 while doing this and run the upgrade when locally sourced email
594 is not likely to be generated.
597 /boot/device.hints is now required for installkernel to
598 succeed. You should copy GENERIC.hints for your architecture
599 into /boot/device.hints. If and only if you compile hints
600 into your kernel, then this file may be empty. Please note,
601 if you have an empty or missing /boot/device.hints file and
602 you neglected to compile hints into your kernel, no boot
603 messages will appear after the boot loader tries to start the
607 If you do NOT have ``options RANDOMDEV'' in your kernel and
608 you DO want the random device then add randomdev_load="YES" to
612 suidperl is now always built and installed on the system, but
613 with permissions of 511. If you have applications that use
614 this program, you are now required to add ENABLE_SUIDPERL=true
615 to /etc/make.conf. If you forget to do this,
616 chmod 4511 /usr/bin/suidperl
617 will fix this until the next build.
620 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
621 visible changes that may immediately affect your configuration
623 - New default file locations from src/contrib/sendmail/cf/README
624 - newaliases limited to root and trusted users
625 - MSA port (587) turned on by default
626 - New queue file naming system so can't go from 8.11 -> 8.9
627 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
628 - FEATURE(`nullclient') is more full featured
629 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
630 - mail.local FreeBSD-only -b option changed to -B
631 - See src/contrib/sendmail/RELEASE_NOTES for more info
634 suidperl (aka sperl) is no longer build by default. You must
635 specifically define BUILD_SUIDPERL to "true" for it to be build.
636 Furthermore, we recommend that you remove /usr/bin/sperl* and
637 /usr/bin/suidperl files from your system unless you have a
641 Networking defaults have been tightened. Anybody upgrading
642 /etc/defaults/rc.conf needs to add the following lines to
643 /etc/rc.conf if they want to have the same setup
644 afterwards (unless the variables already are set, of course):
645 # Enable network daemons for user convenience.
648 sendmail_enable="YES"
651 If you have null_load="YES" in your /boot/loader.conf, you
652 will need to change that to nullfs_load="YES".
655 The "installkernel" target has changed slightly. Now even if
656 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
657 it will install the MYKERNEL file (built with the buildkernel
658 target) as /kernel rather than /MYKERNEL. Those who have
659 updated their /boot/loader.conf files to point to /MYKERNEL
660 should remove that entry or perform manual rename of /kernel
664 If you use CVSUP or CTM to get CVS trees, AND you used to get
665 the old crypto files from internat.freebsd.org AND you check
666 out files from the CVS tree with the cvs command, please read
667 http://people.freebsd.org/~imp/internat.txt
668 for details on potential problems that you might have and how
671 If you are merely a mirror, or don't answer yes to each of the
672 clauses above, you needn't worry.
675 /etc/security has been updated to print the inode number of
676 setuid programs that have changed. You will see a large spike
677 in the number of changed programs the first time when you run
678 mergemaster to get a new /etc/security.
681 /dev/random now has good entropy collection (from the keyboard
682 and sysmouse drivers). Please ensure that either `options
683 RANDOMDEV' is present in your kernel config file or that
684 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
685 not have the /dev/random driver, OpenSSL (and consequently
686 lots of crypto tools (like SSH)) will fail with strange
687 errors. (see below, 20000624).
689 FreeBSD-current is safe again to run Crypto.
692 phk made the malloc default options AJ. This may slow things
693 down and uncover other latent bugs in the code. If you need to
694 run at full speed, you can disable this by doing the following:
695 ln -s aj /etc/malloc.conf
698 libftpio's version was accidentally bumped a few days ago. This
699 has been corrected. You may need to remove /usr/lib/libftpio.so.6
700 before doing your next buildworld/installworld pair. It certainly
701 won't hurt to remove it before the update procedure. It will
702 break fetch until a new one is built, but ftp can be used in the
706 The crypto packages have changed for the cvsup. This has been done
707 in a backward compatible way, but the old packages will go away at
708 some point in the future. Look at /usr/share/examples/cvsup for
712 With the new sys/modules/sound/drivers/*, you will need to
713 set SYSDIR until you do an installworld after July 7th.
716 rc.shutdown and rc will now call the rc.d scripts with start
717 or stop. This may cause some harmless warnings from older
718 rc.d scripts that haven't been updated.
721 The libfetch based version of fetch has gone into the tree.
722 Minor problems may result on some of the less popular sites,
723 which should be reported to des@freebsd.org.
726 From approximately this date forward, one must have the crypto
727 system installed in order to build the system and kernel.
728 While not technically strictly true, one should treat it as
729 required and grab the crypto bits. If you are grabbing CVS
730 trees, src-all and cvs-crypto should be treated as if they
731 were required. You should check with the latest collections
732 to make sure that these haven't changed.
735 Mark Murray just committed the first parts of a cleanup of
736 /dev/zero, et al. This is also cleaning up /dev/random.
737 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
738 -CURRENT FROM THIS POINT to 2000710 for cryptographic services
739 until Mark can merge in the fixes to this work in progress.
740 openssh and openssl should not be used to generate keys from this
741 date to the completion of the work.
743 If you must operate at this reduced level of security, add '
744 options RANDOMDEV' to your kernel or modload the randomdev
745 module. You may also need to copy a new MAKEDEV to /dev and
746 recreate the random and urandom devices.
749 The license on the softupdates is now a standard 2 clause
750 BSD license. You may need to remove your symbolic links
751 that used to be required when updating.
754 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
755 the config file update procedure.
756 http://people.freebsd.org/~imp/config-upd.html
757 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
758 isn't buildable. However, you can generate a LINT file.
761 Binutils 2.10 have hit the tree, or will shortly. As soon
762 as they do, the problem noted in 20000522 will be resolved and
763 that workaround will no longer be required.
766 phk removed the compatibility creation of wd devices in the
767 ad driver. If you haven't done so already, you must update
768 your fstab, etc to use the ad devices instead of the wd
771 In addition, you'll need to update your boot blocks to a
772 more modern version, if you haven't already done so. Modern
773 here means 4.0 release or newer (although older releases
777 Peter took an axe to config(8). Be sure that you read his mail
778 on the topic before even thinking about updating. You will
779 need to create a /boot/device.hints or add a hints directive
780 to your config file to compile them in statically. The format
781 of the config file has changed as well. Please see GENERIC or
782 NEWCARD for examples of the new format.
785 A new set of binutils went into the tree today. Anybody
786 building a kernel after this point is advised that they need
787 to rebuild their binutils (or better yet do a
788 buildworld/installworld) before building a new kernel.
790 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
791 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
792 is recommended that you don't set this option until the problem
796 The ethernet drivers were all updated to clean up the BPF handling.
799 The problems with boot blocks on the alphas have been corrected.
800 This will require some care in updating alphas. A new libstand
801 is requires for the boot blocks to build properly.
804 Recompile all kld modules. Proper version dependency info
808 Modules have been disconnected from the buildworld tree and
809 connected to the kernel building instead.
812 You may need to build gperf
813 cd /usr/src/gnu/usr.bin/gperf && make depend all install
814 when upgrading from 4.0 -> current. The build system now uses
815 an option only in -current.
818 The method that we brand ELF binaries has changed to be more
819 acceptable to the binutils maintainers. You will need to
820 rebrand your ELF binaries that aren't native. One problem
821 binary is the Linux ldconfig. After your make world, but
822 before you reboot, you'll need to issue:
823 brandelf -t Linux /compat/linux/sbin/ldconfig
824 if you have Linux compatibility enabled on your machine.
827 If you have really bad/marginal IDE drives, you may find they
828 don't work well. Use pio mode instead. The easiest way to
829 cope if you have a problem combination is to add:
830 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
831 to the start of /etc/rc.conf.
834 The ISA and PCI compatibility shims have been connected to the
835 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
836 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
837 include the appropriate option in your kernel config. Drivers
838 using the shims should be updated or they won't ship with
839 5.0-RELEASE, targeted for 2001.
842 We've entered the traditional post release dumping party.
843 Large kernel changes are being committed and are in the
844 works. It is important to keep the systems' klds and kernel
845 in sync as kernel interfaces and structures are changing.
846 Before reporting kernel panics, make sure that all modules
847 that you are loading are up to date.
850 If you are upgrading from an older version of FreeBSD, you
851 need to update your boot blocks as well. 'disklabel -B ad0'
852 will do the trick. This isn't critical until you remove your
853 wd device entries in /dev, at which point your system will not
857 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
858 to upgrade to 4.0 from 3.x.
864 Avoid using make -j when upgrading. From time to time in the
865 past there have been problems using -j with buildworld and/or
866 installworld. This is especially true when upgrading between
867 "distant" versions (eg one that cross a major release boundary
868 or several minor releases, or when several months have passed
869 on the -current branch).
871 Sometimes, obscure build problems are the result of environment
872 poisoning. This can happen because the make utility reads its
873 environment when searching for values for global variables.
874 To run your build attempts in an "environmental clean room",
875 prefix all make commands with 'env -i '. See the env(1) manual
876 page for more details.
880 If you are updating from a prior version of FreeBSD (even one just
881 a few days old), you should follow this procedure. With a
882 /usr/obj tree with a fresh buildworld,
883 make buildkernel KERNCONF=YOUR_KERNEL_HERE
884 make installkernel KERNCONF=YOUR_KERNEL_HERE
886 To just build a kernel when you know that it won't mess you up
887 --------------------------------------------------------------
888 cd src/sys/{i386,alpha}/conf
889 config KERNEL_NAME_HERE
890 cd ../../compile/KERNEL_NAME_HERE
895 If this fails, go to the "To build a kernel" section.
897 To rebuild everything and install it on the current system.
898 -----------------------------------------------------------
900 Build a new kernel, see above.
902 To upgrade from 4.x-stable to current
903 -------------------------------------
905 make buildkernel KERNCONF=YOUR_KERNEL_HERE
906 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
907 make installkernel KERNCONF=YOUR_KERNEL_HERE
908 reboot in single user [3]
914 Make sure that you've read the UPDATING file to understand the
915 tweaks to various things you need. At this point in the life
916 cycle of current, things change often and you are on your own
917 to cope. The defaults can also change, so please read ALL of
918 the UPDATING entries.
920 Also, if you are tracking -current, you must be subscribed to
921 freebsd-current@freebsd.org. Make sure that before you update
922 your sources that you have read and understood all the recent
923 messages there. If in doubt, please track -stable which has
926 [1] If you have third party modules, such as vmware, you
927 should disable them at this point so they don't crash your
930 [2] If you have legacy ISA devices, you may need to create
931 your own device.hints to reflect your unique hardware
934 [3] From the bootblocks, boot -s, and then do
939 adjkerntz -i # if CMOS is wall time
941 [4] Note: This step is non-optional. Failure to do this step
942 can result in a significant reduction in the functionality of the
943 system. Attempting to do it by hand is not recommended and those
944 that pursue this avenue should read this file carefully, as well
945 as the archives of freebsd-current and freebsd-hackers mailing lists
946 for potential gotchas.
950 This file contains a list, in reverse chronological order, of major
951 breakages in tracking -current. Not all things will be listed here,
952 and it only starts on March 15, 2000. Updating files can found in
953 previous releases if your system is older than this.
955 Please filter your entries through Warner Losh (imp@village.org) so
956 that the style, formatting, etc of this file can be maintained.
958 Copyright information:
960 Copyright 1998, 2001 M. Warner Losh. All Rights Reserved.
962 Redistribution, publication, translation and use, with or without
963 modification, in full or in part, in any form or format of this
964 document are permitted.
966 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
967 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
968 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
969 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
970 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
971 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
972 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
973 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
974 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
975 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
976 POSSIBILITY OF SUCH DAMAGE.
978 If you find this document useful, and you want to, you may buy the
981 Contact Warner Losh if you have any questions about your use of