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