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.
9 The bugs in procfs' debugging support code have been fixed,
10 and truss(1) now works again.
13 Daily security checks have been split out to use the periodic(8)
14 scripts. Some change in configuration may be necessary. Please
16 http://www.freebsd.org/cgi/mid.cgi?db=mid&id=<20011207155805.R8975@blossom.cjclark.org>
20 sos added VCD/SVCD support to ata driver and that needs the
21 kernel and burncd to be in sync.
24 The procfs pseudo-filesystem has now been converted to use the
25 pseudofs framework. If you have 'options PROCFS' in your
26 kernel config, you'll need to add 'options PSEUDOFS' if it's
29 This change temporarily breaks truss(1); use ktrace(1) instead
30 until the issue has been resolved.
33 A security hole in OpenSSH involving `UseLogin yes' has been
37 You need to remove /usr/obj/.../usr.bin/tip before rebuilding
41 Most of the awk issues have been resolved. Some rough
42 edges may be left, but for the most part things should be
43 back to "normal." For CURRENT's usual definition of "normal."
46 Awk has been upgraded to the one true awk from bell labs. Expect
47 choppy waves in the upgrade process.
50 The asr driver problem has been resolved.
53 Due to changes in other parts of the system, the asr driver
54 now causes the system to panic on boot. Do not use it pending
55 correction. Comment it out of any kernel config file that you
56 try to use from this date forward.
59 When crossbuilding, use TARGET=xxx where you used to use
60 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
61 unless you are changing both of them. To cross build pc98 on
62 an alpha, for example, you need to set TARGET=pc98 and
66 The kernel interface that burncd depends on has changed.
67 You must recompile both the kernel and userland applications
71 When crossbuilding, please set TARGET_ARCH rather than
72 MACHINE_ARCH to indicate the target. In the future, one will
73 set TARGET_MACHINE where you set MACHINE now. At the moment,
74 setting MACHINE alone for same MACHINE_ARCH machines works
75 (eg, you can build pc98 on a i386 machine and vice versa).
78 Some weird problems result from using ACPI on some machines.
79 To disable ACPI you can add
80 hint.acpi.0.disable="1"
81 to /boot/loader.conf (or by putting set X=Y at the boot
84 Alternatively, you can remove it from /boot/kernel/acpi.ko
85 or use the MODULES_OVERRIDE function in your kernel config
86 file and not list acpi in that list.
89 The buildworld has been fixed. You may need to install
90 the 4.x compatibility libraries for some old binaries
91 to work. Add COMPAT4X=true to your /etc/make.conf to
92 get them installed on every installworld, or execute the
93 following to get them installed only once:
94 cd src/lib/compat/compat4x.<arch>
96 You will see ``__stdoutp undefined'' until you do this.
99 There's a bug in the world build process. The cross-tools
100 are build with the NEW headers, but the OLD libc.a. This
101 leads to all kinds of problems with the new libc. A temporary
103 CFLAGS="-O -pipe -D_OLD_STDIO"
104 before building world when upgrading from 4.x to current. This
105 can be removed afterwards.
107 A proper fix to the buildworld target is needed.
110 Peter has committed his new kthread nfs client/server code.
111 NFS may be unstable after this date.
114 KSE has hit the tree. Lots of things are now different in
115 the kernel. While a few problems were introduced in the
116 initial commit, most of the major ones have been found and
120 In OLDCARD, CardBus bridges appear to be stable. The work
121 arounds described in the 20010604 entry are now no longer
122 necessary and will be ignored. Most insert/remove problems
123 have been rectified around this date.
126 named now runs as user bind and group bind rather than as
127 root. If named_enable is set to YES in /etc/rc.conf, ensure
128 that user bind is available in /etc/passwd (using vipw(8))
129 and that group bind is available in /etc/group. Also make
130 sure that user or group bind has read (and not write)
131 permission for your name server configuration and that it
132 has read and write permission for your slave zone files and
135 If you wish to continue to run named as root (a less secure
136 alternative), add a line to /etc/rc.conf saying
141 The PAM libraries have had an API upgrade that is beyond
142 the ability of the shared library major number to handle.
143 It is manifested by PAM-using ports dumping core. The
144 solution is to rebuild those ports.
147 The kernel compile module has moved from src/sys/compile/FOO
148 to src/sys/${MACHINE}/compile/FOO.
151 The pccard modem issue from 20010613 has been corrected.
152 OLDCARD support is still a little weak in -current. slot 1 is
153 known not to work on some TI based cardbus bridges. Some
154 cardbus bridges do not properly detect insert/removal events.
155 IRQ configuration needs more safety belts.
158 Softupdates problems have been corrected.
161 Peter ripped out the linkerset support. You must, as always,
162 rerun config after you cvsup if you are using the traditional
163 kernel building methods.
166 pccard modems may not work with current after 20010604 date. Some
167 do, others result in panics. *MAKE*SURE* that you update your
168 config and /etc/rc.conf ala the 20010604 entry, or you will have
169 problems (this issue will be fixed, it just hasn't been yet).
172 SOFTUPDATES seem to be broken since the middle of May or so. Do not
173 use them in current. You can disable softupdates on all mounted
174 partitions, or remove SOFTUPDATES the kernel config file.
177 After Peter's commits to the hints code, people have been noticing
178 that certain devices are attached (or try to) twice. This is due
179 to having both static hints as well as a /boot/device.hints. To
180 work around this issue, please use only one or the other mechanism
181 until this bug is fixed.
183 Please note that a feature of config is that if you have config
184 file FOO and FOO.hints, it automatically adds FOO.hints to the
185 hints.c file, wheather you want it to or not.
188 Locale names have changed to match other systems better.
191 pccard support for pci cards has been committed. You must change
192 your /etc/pccard.conf irq lines. It must match the irq used by
193 pcic device. Interrupt storms may result if you fail to do this.
194 Interrupt storms look a lot like a hang.
196 You must also install a new pccardd, otherwise you will get an
197 interrupt storm at card reset time (just after it tells you what
200 pccardd_flags="-I" is necessary for the time being. It tells pccardd
201 not to ask the kernel if the interrupt is really free or not before
202 using it. You can either change the /etc/pccard.conf irq lines to
203 match pcic, or add "-i X" to the pccardd_flags.
206 INSTALL=install -C is being deprecated. If you want to do this,
207 use COPY=-C instead. The former method will be supported for only
208 a limited time. If you see
210 install: warning: the -d and -C options may not be specified together
212 in your makeworld, then you need to migrate towards using
216 It appears that vm is now stable enough to use again. However,
217 there may be other problems, so caution is still urged. alpha
218 definitely is in bad shape.
221 Minor repo damange has happened. This may cause problems
222 with cvsup of ports. If you get errors, please see
223 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
224 at the bottom for details on a workaround. The error message
226 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
229 Vm and/or swapping are busted on -current. Please be patient.
232 pccard has had much reorganizational work done to it over
233 the past few days. Everything should still work, but if
234 not, please contact imp@freebsd.org.
237 ata ioctl changed. Make sure to recompile both kernel and
238 userland at the same time.
241 New ncurses imported.
244 DEVFS is now opt out, not opt in. Barring major problems, this
245 will be the only way to go starting July 1.
248 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
251 Building perl was broken at 02:25:25 PDT.
254 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
255 go back in the water.
258 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
259 this date, but before the correction date.
262 old fsck and new kernel interactions appear to have been fixed.
265 fsck and the kernel were changed to handle some optimizations
266 to directory layout. This breaks backward compatibility.
267 Update only if you understand that you must not use the old
268 fsck with the new kernel ever.
271 fsck has changed the meaning of the pass column in /etc/fstab.
272 Please see the cvs commit to fsck.8 or the fsck.8 man page for
273 details. It is unclear if changes to /etc/fstab are necessary.
276 portmap had changed name to rpcbind for maximum POLA in your
277 current world. /etc/hosts.{allow,deny} needs changes. nfs and
278 other rpc based programs that rely on portmapper will not work
279 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
282 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
283 and ATA_ENABEL_TAGS are no longer kernel options. They have
284 been replaced by tunables. See ata.4 for details.
287 The fxp driver was converted to use miibus. If you compile
288 fxp into your kernel statically, you will need to add miibus.
291 The wi device now defaults to BSS (infrastructure) mode
295 /dev/urandom should be a symbolic link to /dev/random now.
296 Users of current not using DEVFS need to run MAKEDEV std.
297 ssh might not work if you don't.
300 The ed driver has been updated. It now allows mii attachments,
301 which means that you must include the miibus in your kernel if
302 you use the ed driver.
305 The problems with libc have been corrected. It is now mostly
306 safe to go back into the water.
309 The size of FILE was changed. This breaks upgrading. If
310 you must upgrade, be prepared for pain. It also breaks almost
311 all binaries that you've compiled on -current. You are warned
312 that before upgrading would be a good time to do a level 0
313 dump of your system. No, really, I mean it this time.
315 To get to the new system, you'll need to use the following
316 workaround. Hopefully this can be sorted out so that we
317 don't have to move this to the updating section.
319 To get around the installworld problem, do:
320 # cd /usr/src/usr.bin/sed
324 If that doesn't work, then try:
325 # make -k installworld
329 DEVFS is now the default. If you use vinum, make sure that you
330 do not include devfs in your kernel as problems result.
333 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
334 Remove them from your config.
337 ****************************** WARNING ******************************
338 buildkernel has been changed slightly
339 ****************************** WARNING ******************************
340 KERNCONF replaces the variable KERNEL for buildkernel. You
341 should update your scripts and make.conf accordingly.
344 config has changed to allow DEV_FOO as a replacement for NFOO.
345 This requires a new config to build correctly.
348 The kerrnel option I386_CPU is now mutually exclusive with the
349 other cpu types. If you have an i386 system, be sure that it
350 only had this line. Remove it for all other configurations.
353 Changes to the kernel require it and burncd be in sync.
356 Everyone who has hw.sndunit set to something in
357 /etc/sysctl.conf, it is now hw.snd.unit.
360 ex and vi were broken by some changes to sys/queue.h. If you
361 have a bad vi, you will see make buildworld fail with a core
362 dump while building termcap. You can work around this problem
363 by adding -k to your make buildworld. This will cause the
364 build to complete and install a new vi. Once that's done, you
365 can rebuild again without the -k to pick up anything that
366 might have been ignored by the -k option.
368 Others have suggested that you can just rebuild libc if your
369 vi/ex is dynamically linked, but I've not received any reports
373 There have been some changes to libcrypt in -current. The
374 libscrypt/libdescrypt symlink sillyness is gone and the installed
375 libcrypt is fully functional. Be aware of this.
378 Linksys Fast Ethernet PCCARD cards supported by the ed driver
379 now require the addition of flag 0x80000 to their config line
380 in pccard.conf(5). This flag is not optional. These Linksys
381 cards will not be recognized without it.
384 Important new FreeBSD-version stuff: PAM support has been worked
385 in, partially from the "Unix" OpenSSH version. This requires
386 adding the following in pam.conf:
388 sshd auth sufficient pam_skey.so
389 sshd auth required pam_unix.so try_first_pass
390 sshd session required pam_permit.so
396 The random device needs more entropy, so you need to make sure
397 that you've run mergemaster to get a /etc/rc which will seed
398 /dev/random. If you don't and the system hangs after ldconfig,
399 then banging on the keyboard randomly until it unhangs is one
403 ****************************** WARNING ******************************
404 Sendmail has been updated.
405 ****************************** WARNING ******************************
406 o mail.local(8) is no longer installed as a set-user-id binary.
407 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
409 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
411 o Now using sendmail's version of vacation(1).
412 o The sendmail cf building tools (contrib/sendmail/cf) are installed
413 in /usr/share/sendmail/cf.
414 o sendmail.cw changed to local-host-names
416 More details can be found at
417 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
420 The ports tree's new layout is in place. Be sure to update
421 your entire ports tree, or you will have problems.
424 The perl build procedure no longer installs miniperl, nor uses
425 the installed miniperl. It is recommended that you delete
429 This weekend the ports tree will be updated to a new layout.
430 It will be in an inconsistent state until noted in the UPDATING
431 file, or with asami-san's message to the relevant mailing
432 lists. With this new layout, you'll need to update the whole
433 tree for anything to work.
436 There was a change in the passwd format. Need more information.
439 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
440 place. Please update boot loader (not the boot blocks) at the
441 same time as your kernel.
444 The new pmtimer device is necessary for laptops. Failure to
445 include the device will cause suspended laptops losing time
446 when they resume. Include
448 in your config file and
449 hint.pmtimer.0.at="isa"
450 to your /boot/device.hints file.
453 The random device has been turned into a (pseudo-)device,
454 rather than an option. The supplied kernel config files have
455 been updated. You will need to do something similar in your
456 own kernel config file.
461 If you prefer to load the loadable module, you need to do
465 The random device module has been renamed from randomdev.ko to
466 random.ko. You will need to edit your /boot/loader.conf to
467 reflect this if you load this module at boot time.
468 The line should read:
472 The SMPNG commit has happened. It should work, but if it
473 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
474 to be a variety of minor issues. Please see 20000905 to make
475 sure you don't have model loading problems which might at
476 first blush appear related to SMP.
479 nsswitch has been imported from NetBSD. Among other things,
480 this means that /etc/host.conf is no longer used. See
481 nsswitch.conf(5) instead. Note that at boot time rc.network
482 will attempt to produce a new nsswitch.conf file for you if you
483 don't have one, and you have host.conf.
486 The ucred structure changed size. This breaks the interface
487 that mountd uses. Trying to use an older mountd with a newer
488 kernel guarantees a panic. This means that you need to use
489 kernels newer than today only with matching mountd, but you
490 needed to do that anyway with the boot loader changes.
493 The boot loader has been updated. The new default kernel is
494 now /boot/kernel/kernel.ko. The new default module location
497 You *MUST* upgrade your boot loader and kernel at the same time.
498 The easiest way to do this is to do the buildworld/buildkernel/
499 installkernel/installworld dance.
501 Furthermore, you are urged to delete your old /modules directory
502 before booting the new kernel, since kldload will find stale
503 modules in that directory instead of finding them in the correct
504 path, /boot/kernel. The most common complaint that this cures
505 is that the linux module crashes your machine after the update.
507 if [ ! -d /boot/kernel.old ]; then
508 mv /modules.old /boot/kernel.old
509 chflags noschg /kernel.old
510 mv /kernel.old /boot/kernel.old/kernel.ko
511 chflags schg /boot/kernel.old/kernel.ko
515 A new issue with the sendmail upgrade has come to light.
516 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
517 incorrectly install the default aliases in /etc/mail rather than
518 move the old one from /etc. So you'll need to manually move the
519 file, create a symbolic link, remove the old /etc/aliases.db and
520 run newaliases. For safety sake, you should stop sendmail
521 while doing this and run the upgrade when locally sourced email
522 is not likely to be generated.
525 /boot/device.hints is now required for installkernel to
526 succeed. You should copy GENERIC.hints for your architecture
527 into /boot/device.hints. If and only if you compile hints
528 into your kernel, then this file may be empty. Please note,
529 if you have an empty or missing /boot/device.hints file and
530 you neglected to compile hints into your kernel, no boot
531 messages will appear after the boot loader tries to start the
535 If you do NOT have ``options RANDOMDEV'' in your kernel and
536 you DO want the random device then add randomdev_load="YES" to
540 suidperl is now always built and installed on the system, but
541 with permissions of 511. If you have applications that use
542 this program, you are now required to add ENABLE_SUIDPERL=true
543 to /etc/make.conf. If you forget to do this,
544 chmod 4511 /usr/bin/suidperl
545 will fix this until the next build.
548 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
549 visible changes that may immediately affect your configuration
551 - New default file locations from src/contrib/sendmail/cf/README
552 - newaliases limited to root and trusted users
553 - MSA port (587) turned on by default
554 - New queue file naming system so can't go from 8.11 -> 8.9
555 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
556 - FEATURE(`nullclient') is more full featured
557 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
558 - mail.local FreeBSD-only -b option changed to -B
559 - See src/contrib/sendmail/RELEASE_NOTES for more info
562 suidperl (aka sperl) is no longer build by default. You must
563 specifically define BUILD_SUIDPERL to "true" for it to be build.
564 Furthermore, we recommend that you remove /usr/bin/sperl* and
565 /usr/bin/suidperl files from your system unless you have a
569 Networking defaults have been tightened. Anybody upgrading
570 /etc/defaults/rc.conf needs to add the following lines to
571 /etc/rc.conf if they want to have the same setup
572 afterwards (unless the variables already are set, of course):
573 # Enable network daemons for user convenience.
576 sendmail_enable="YES"
579 If you have null_load="YES" in your /boot/loader.conf, you
580 will need to change that to nullfs_load="YES".
583 The "installkernel" target has changed slightly. Now even if
584 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
585 it will install the MYKERNEL file (built with the buildkernel
586 target) as /kernel rather than /MYKERNEL. Those who have
587 updated their /boot/loader.conf files to point to /MYKERNEL
588 should remove that entry or perform manual rename of /kernel
592 If you use CVSUP or CTM to get CVS trees, AND you used to get
593 the old crypto files from internat.freebsd.org AND you check
594 out files from the CVS tree with the cvs command, please read
595 http://people.freebsd.org/~imp/internat.txt
596 for details on potential problems that you might have and how
599 If you are merely a mirror, or don't answer yes to each of the
600 clauses above, you needn't worry.
603 /etc/security has been updated to print the inode number of
604 setuid programs that have changed. You will see a large spike
605 in the number of changed programs the first time when you run
606 mergemaster to get a new /etc/security.
609 /dev/random now has good entropy collection (from the keyboard
610 and sysmouse drivers). Please ensure that either `options
611 RANDOMDEV' is present in your kernel config file or that
612 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
613 not have the /dev/random driver, OpenSSL (and consequently
614 lots of crypto tools (like SSH)) will fail with strange
615 errors. (see below, 20000624).
617 FreeBSD-current is safe again to run Crypto.
620 phk made the malloc default options AJ. This may slow things
621 down and uncover other latent bugs in the code. If you need to
622 run at full speed, you can disable this by doing the following:
623 ln -s aj /etc/malloc.conf
626 libftpio's version was accidentally bumped a few days ago. This
627 has been corrected. You may need to remove /usr/lib/libftpio.so.6
628 before doing your next buildworld/installworld pair. It certainly
629 won't hurt to remove it before the update procedure. It will
630 break fetch until a new one is built, but ftp can be used in the
634 The crypto packages have changed for the cvsup. This has been done
635 in a backward compatible way, but the old packages will go away at
636 some point in the future. Look at /usr/share/examples/cvsup for
640 With the new sys/modules/sound/drivers/*, you will need to
641 set SYSDIR until you do an installworld after July 7th.
644 rc.shutdown and rc will now call the rc.d scripts with start
645 or stop. This may cause some harmless warnings from older
646 rc.d scripts that haven't been updated.
649 The libfetch based version of fetch has gone into the tree.
650 Minor problems may result on some of the less popular sites,
651 which should be reported to des@freebsd.org.
654 From approximately this date forward, one must have the crypto
655 system installed in order to build the system and kernel.
656 While not technically strictly true, one should treat it as
657 required and grab the crypto bits. If you are grabbing CVS
658 trees, src-all and cvs-crypto should be treated as if they
659 were required. You should check with the latest collections
660 to make sure that these haven't changed.
663 Mark Murray just committed the first parts of a cleanup of
664 /dev/zero, et al. This is also cleaning up /dev/random.
665 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
666 -CURRENT FROM THIS POINT FORWARD for cryptographic services
667 until Mark can merge in the fixes to this work in progress.
668 openssh and openssl should not be used to generate keys from this
669 date to the completion of the work.
671 If you must operate at this reduced level of security, add '
672 options RANDOMDEV' to your kernel or modload the randomdev
673 module. You may also need to copy a new MAKEDEV to /dev and
674 recreate the random and urandom devices.
677 The license on the softupdates is now a standard 2 clause
678 BSD license. You may need to remove your symbolic links
679 that used to be required when updating.
682 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
683 the config file update procedure.
684 http://people.freebsd.org/~imp/config-upd.html
685 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
686 isn't buildable. However, you can generate a LINT file.
689 Binutils 2.10 have hit the tree, or will shortly. As soon
690 as they do, the problem noted in 20000522 will be resolved and
691 that workaround will no longer be required.
694 phk removed the compatibility creation of wd devices in the
695 ad driver. If you haven't done so already, you must update
696 your fstab, etc to use the ad devices instead of the wd
699 In addition, you'll need to update your boot blocks to a
700 more modern version, if you haven't already done so. Modern
701 here means 4.0 release or newer (although older releases
705 Peter took an axe to config(8). Be sure that you read his mail
706 on the topic before even thinking about updating. You will
707 need to create a /boot/device.hints or add a hints directive
708 to your config file to compile them in statically. The format
709 of the config file has changed as well. Please see GENERIC or
710 NEWCARD for examples of the new format.
713 A new set of binutils went into the tree today. Anybody
714 building a kernel after this point is advised that they need
715 to rebuild their binutils (or better yet do a
716 buildworld/installworld) before building a new kernel.
718 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
719 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
720 is recommended that you don't set this option until the problem
724 The ethernet drivers were all updated to clean up the BPF handling.
727 The problems with boot blocks on the alphas have been corrected.
728 This will require some care in updating alphas. A new libstand
729 is requires for the boot blocks to build properly.
732 Recompile all kld modules. Proper version dependency info
736 Modules have been disconnected from the buildworld tree and
737 connected to the kernel building instead.
740 You may need to build gperf
741 cd /usr/src/gnu/usr.bin/gperf && make depend all install
742 when upgrading from 4.0 -> current. The build system now uses
743 an option only in -current.
746 The method that we brand ELF binaries has changed to be more
747 acceptable to the binutils maintainers. You will need to
748 rebrand your ELF binaries that aren't native. One problem
749 binary is the Linux ldconfig. After your make world, but
750 before you reboot, you'll need to issue:
751 brandelf -t Linux /compat/linux/sbin/ldconfig
752 if you have Linux compatibility enabled on your machine.
755 If you have really bad/marginal IDE drives, you may find they
756 don't work well. Use pio mode instead. The easiest way to
757 cope if you have a problem combination is to add:
758 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
759 to the start of /etc/rc.conf.
762 The ISA and PCI compatibility shims have been connected to the
763 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
764 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
765 include the appropriate option in your kernel config. Drivers
766 using the shims should be updated or they won't ship with
767 5.0-RELEASE, targeted for 2001.
770 We've entered the traditional post release dumping party.
771 Large kernel changes are being committed and are in the
772 works. It is important to keep the systems' klds and kernel
773 in sync as kernel interfaces and structures are changing.
774 Before reporting kernel panics, make sure that all modules
775 that you are loading are up to date.
778 If you are upgrading from an older version of FreeBSD, you
779 need to update your boot blocks as well. 'disklabel -B ad0'
780 will do the trick. This isn't critical until you remove your
781 wd device entries in /dev, at which point your system will not
785 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
786 to upgrade to 4.0 from 3.x.
792 Avoid using make -j when upgrading. From time to time in the
793 past there have been problems using -j with buildworld and/or
794 installworld. This is especially true when upgrading between
795 "distant" versions (eg one that cross a major release boundary
796 or several minor releases, or when several months have passed
797 on the -current branch).
801 If you are updating from a prior version of FreeBSD (even one just
802 a few days old), you should follow this procedure. With a
803 /usr/obj tree with a fresh buildworld,
804 make buildkernel KERNCONF=YOUR_KERNEL_HERE
805 make installkernel KERNCONF=YOUR_KERNEL_HERE
807 To just build a kernel when you know that it won't mess you up
808 --------------------------------------------------------------
809 cd src/sys/{i386,alpha}/conf
810 config KERNEL_NAME_HERE [1]
811 cd ../../compile/KERNEL_NAME_HERE
816 [1] If in doubt, -r might help here.
818 If this fails, go to the "To build a kernel" section.
820 To rebuild everything and install it on the current system.
821 -----------------------------------------------------------
823 Build a new kernel, see above.
825 To upgrade from 4.x-stable to current
826 -------------------------------------
828 make buildkernel KERNCONF=YOUR_KERNEL_HERE
829 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
830 make installkernel KERNCONF=YOUR_KERNEL_HERE
831 reboot in single user [3]
837 Make sure that you've read the UPDATING file to understand the
838 tweaks to various things you need. At this point in the life
839 cycle of current, things change often and you are on your own
840 to cope. The defaults can also change, so please read ALL of
841 the UPDATING entries.
843 Also, if you are tracking -current, you must be subscribed to
844 freebsd-current@freebsd.org. Make sure that before you update
845 your sources that you have read and understood all the recent
846 messages there. If in doubt, please track -stable which has
849 [1] If you have third party modules, such as vmware, you
850 should disable them at this point so they don't crash your
853 [2] If you have legacy ISA devices, you may need to create
854 your own device.hints to reflect your unique hardware
857 [3] From the bootblocks, boot -s, and then do
862 adjkerntz -i # if COMS is wall time
864 [4] Note: This step is non-optional. Failure to do this step
865 can result in a significant reduction in the functionality of the
866 system. Attempting to do it by hand is not recommended and those
867 that pursue this avenue should read this file carefully, as well
868 as the archives of freebsd-current and freebsd-hackers mailing lists
869 for potential gotchas.
873 This file contains a list, in reverse chronological order, of major
874 breakages in tracking -current. Not all things will be listed here,
875 and it only starts on March 15, 2000. Updating files can found in
876 previous releases if your system is older than this.
878 Please filter your entries through Warner Losh (imp@village.org) so
879 that the style, formatting, etc of this file can be maintained.
881 Copyright information:
883 Copyright 1998, 2001 M. Warner Losh. All Rights Reserved.
885 Redistribution, publication, translation and use, with or without
886 modification, in full or in part, in any form or format of this
887 document are permitted.
889 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
890 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
891 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
892 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
893 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
894 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
895 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
896 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
897 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
898 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
899 POSSIBILITY OF SUCH DAMAGE.
901 If you find this document useful, and you want to, you may buy the
904 Contact Warner Losh if you have any questions about your use of