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 asr driver problem has been resolved.
12 Due to changes in other parts of the system, the asr driver
13 now causes the system to panic on boot. Do not use it pending
14 correction. Comment it out of any kernel config file that you
15 try to use from this date forward.
18 When crossbuilding, use TARGET=xxx where you used to use
19 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
20 unless you are changing both of them. To cross build pc98 on
21 an alpha, for example, you need to set TARGET=pc98 and
25 The kernel interface that burncd depends on has changed.
26 You must recompile both the kernel and userland applications
30 When crossbuilding, please set TARGET_ARCH rather than
31 MACHINE_ARCH to indicate the target. In the future, one will
32 set TARGET_MACHINE where you set MACHINE now. At the moment,
33 setting MACHINE alone for same MACHINE_ARCH machines works
34 (eg, you can build pc98 on a i386 machine and vice versa).
37 Some weird problems result from using ACPI on some machines.
38 To disable ACPI you can add
39 hint.acpi.0.disable="1"
40 to /boot/loader.conf (or by putting set X=Y at the boot
43 Alternatively, you can remove it from /boot/kernel/acpi.ko
44 or use the MODULES_OVERRIDE function in your kernel config
45 file and not list acpi in that list.
48 The buildworld has been fixed. You may need to install
49 the 4.x compatibility libraries for some old binaries
51 cd src/lib/compat/compat4x.i386
55 There's a bug in the world build process. The cross-tools
56 are build with the NEW headers, but the OLD libc.a. This
57 leads to all kinds of problems with the new libc. A temporary
59 CFLAGS="-O -pipe -D_OLD_STDIO"
60 before building world when upgrading from 4.x to current. This
61 can be removed afterwards.
63 A proper fix to the buildworld target is needed.
66 Peter has committed his new kthread nfs client/server code.
67 NFS may be unstable after this date.
70 KSE has hit the tree. Lots of things are now different in
71 the kernel. While a few problems were introduced in the
72 initial commit, most of the major ones have been found and
76 In OLDCARD, CardBus bridges appear to be stable. The work
77 arounds described in the 20010604 entry are now no longer
78 necessary and will be ignored. Most insert/remove problems
79 have been rectified around this date.
82 named now runs as user bind and group bind rather than as
83 root. If named_enable is set to YES in /etc/rc.conf, ensure
84 that user bind is available in /etc/passwd (using vipw(8))
85 and that group bind is available in /etc/group. Also make
86 sure that user or group bind has read (and not write)
87 permission for your name server configuration and that it
88 has read and write permission for your slave zone files and
91 If you wish to continue to run named as root (a less secure
92 alternative), add a line to /etc/rc.conf saying
97 The PAM libraries have had an API upgrade that is beyond
98 the ability of the shared library major number to handle.
99 It is manifested by PAM-using ports dumping core. The
100 solution is to rebuild those ports.
103 The kernel compile module has moved from src/sys/compile/FOO
104 to src/sys/${MACHINE}/compile/FOO.
107 The pccard modem issue from 20010613 has been corrected.
108 OLDCARD support is still a little weak in -current. slot 1 is
109 known not to work on some TI based cardbus bridges. Some
110 cardbus bridges do not properly detect insert/removal events.
111 IRQ configuration needs more safety belts.
114 Softupdates problems have been corrected.
117 Peter ripped out the linkerset support. You must, as always,
118 rerun config after you cvsup if you are using the traditional
119 kernel building methods.
122 pccard modems may not work with current after 20010604 date. Some
123 do, others result in panics. *MAKE*SURE* that you update your
124 config and /etc/rc.conf ala the 20010604 entry, or you will have
125 problems (this issue will be fixed, it just hasn't been yet).
128 SOFTUPDATES seem to be broken since the middle of May or so. Do not
129 use them in current. You can disable softupdates on all mounted
130 partitions, or remove SOFTUPDATES the kernel config file.
133 After Peter's commits to the hints code, people have been noticing
134 that certain devices are attached (or try to) twice. This is due
135 to having both static hints as well as a /boot/device.hints. To
136 work around this issue, please use only one or the other mechanism
137 until this bug is fixed.
139 Please note that a feature of config is that if you have config
140 file FOO and FOO.hints, it automatically adds FOO.hints to the
141 hints.c file, wheather you want it to or not.
144 Locale names have changed to match other systems better.
147 pccard support for pci cards has been committed. You must change
148 your /etc/pccard.conf irq lines. It must match the irq used by
149 pcic device. Interrupt storms may result if you fail to do this.
150 Interrupt storms look a lot like a hang.
152 You must also install a new pccardd, otherwise you will get an
153 interrupt storm at card reset time (just after it tells you what
156 pccardd_flags="-I" is necessary for the time being. It tells pccardd
157 not to ask the kernel if the interrupt is really free or not before
158 using it. You can either change the /etc/pccard.conf irq lines to
159 match pcic, or add "-i X" to the pccardd_flags.
162 INSTALL=install -C is being deprecated. If you want to do this,
163 use COPY=-C instead. The former method will be supported for only
164 a limited time. If you see
166 install: warning: the -d and -C options may not be specified together
168 in your makeworld, then you need to migrate towards using
172 It appears that vm is now stable enough to use again. However,
173 there may be other problems, so caution is still urged. alpha
174 definitely is in bad shape.
177 Minor repo damange has happened. This may cause problems
178 with cvsup of ports. If you get errors, please see
179 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
180 at the bottom for details on a workaround. The error message
182 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
185 Vm and/or swapping are busted on -current. Please be patient.
188 pccard has had much reorganizational work done to it over
189 the past few days. Everything should still work, but if
190 not, please contact imp@freebsd.org.
193 ata ioctl changed. Make sure to recompile both kernel and
194 userland at the same time.
197 New ncurses imported.
200 DEVFS is now opt out, not opt in. Barring major problems, this
201 will be the only way to go starting July 1.
204 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
207 Building perl was broken at 02:25:25 PDT.
210 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
211 go back in the water.
214 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
215 this date, but before the correction date.
218 old fsck and new kernel interactions appear to have been fixed.
221 fsck and the kernel were changed to handle some optimizations
222 to directory layout. This breaks backward compatibility.
223 Update only if you understand that you must not use the old
224 fsck with the new kernel ever.
227 fsck has changed the meaning of the pass column in /etc/fstab.
228 Please see the cvs commit to fsck.8 or the fsck.8 man page for
229 details. It is unclear if changes to /etc/fstab are necessary.
232 portmap had changed name to rpcbind for maximum POLA in your
233 current world. /etc/hosts.{allow,deny} needs changes. nfs and
234 other rpc based programs that rely on portmapper will not work
235 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
238 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
239 and ATA_ENABEL_TAGS are no longer kernel options. They have
240 been replaced by tunables. See ata.4 for details.
243 The fxp driver was converted to use miibus. If you compile
244 fxp into your kernel statically, you will need to add miibus.
247 The wi device now defaults to BSS (infrastructure) mode
251 /dev/urandom should be a symbolic link to /dev/random now.
252 Users of current not using DEVFS need to run MAKEDEV std.
253 ssh might not work if you don't.
256 The ed driver has been updated. It now allows mii attachments,
257 which means that you must include the miibus in your kernel if
258 you use the ed driver.
261 The problems with libc have been corrected. It is now mostly
262 safe to go back into the water.
265 The size of FILE was changed. This breaks upgrading. If
266 you must upgrade, be prepared for pain. It also breaks almost
267 all binaries that you've compiled on -current. You are warned
268 that before upgrading would be a good time to do a level 0
269 dump of your system. No, really, I mean it this time.
271 To get to the new system, you'll need to use the following
272 workaround. Hopefully this can be sorted out so that we
273 don't have to move this to the updating section.
275 To get around the installworld problem, do:
276 # cd /usr/src/usr.bin/sed
280 If that doesn't work, then try:
281 # make -k installworld
285 DEVFS is now the default. If you use vinum, make sure that you
286 do not include devfs in your kernel as problems result.
289 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
290 Remove them from your config.
293 ****************************** WARNING ******************************
294 buildkernel has been changed slightly
295 ****************************** WARNING ******************************
296 KERNCONF replaces the variable KERNEL for buildkernel. You
297 should update your scripts and make.conf accordingly.
300 config has changed to allow DEV_FOO as a replacement for NFOO.
301 This requires a new config to build correctly.
304 The kerrnel option I386_CPU is now mutually exclusive with the
305 other cpu types. If you have an i386 system, be sure that it
306 only had this line. Remove it for all other configurations.
309 Changes to the kernel require it and burncd be in sync.
312 Everyone who has hw.sndunit set to something in
313 /etc/sysctl.conf, it is now hw.snd.unit.
316 ex and vi were broken by some changes to sys/queue.h. If you
317 have a bad vi, you will see make buildworld fail with a core
318 dump while building termcap. You can work around this problem
319 by adding -k to your make buildworld. This will cause the
320 build to complete and install a new vi. Once that's done, you
321 can rebuild again without the -k to pick up anything that
322 might have been ignored by the -k option.
324 Others have suggested that you can just rebuild libc if your
325 vi/ex is dynamically linked, but I've not received any reports
329 There have been some changes to libcrypt in -current. The
330 libscrypt/libdescrypt symlink sillyness is gone and the installed
331 libcrypt is fully functional. Be aware of this.
334 Linksys Fast Ethernet PCCARD cards supported by the ed driver
335 now require the addition of flag 0x80000 to their config line
336 in pccard.conf(5). This flag is not optional. These Linksys
337 cards will not be recognized without it.
340 Important new FreeBSD-version stuff: PAM support has been worked
341 in, partially from the "Unix" OpenSSH version. This requires
342 adding the following in pam.conf:
344 sshd auth sufficient pam_skey.so
345 sshd auth required pam_unix.so try_first_pass
346 sshd session required pam_permit.so
352 The random device needs more entropy, so you need to make sure
353 that you've run mergemaster to get a /etc/rc which will seed
354 /dev/random. If you don't and the system hangs after ldconfig,
355 then banging on the keyboard randomly until it unhangs is one
359 ****************************** WARNING ******************************
360 Sendmail has been updated.
361 ****************************** WARNING ******************************
362 o mail.local(8) is no longer installed as a set-user-id binary.
363 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
365 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
367 o Now using sendmail's version of vacation(1).
368 o The sendmail cf building tools (contrib/sendmail/cf) are installed
369 in /usr/share/sendmail/cf.
370 o sendmail.cw changed to local-host-names
372 More details can be found at
373 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
376 The ports tree's new layout is in place. Be sure to update
377 your entire ports tree, or you will have problems.
380 The perl build procedure no longer installs miniperl, nor uses
381 the installed miniperl. It is recommended that you delete
385 This weekend the ports tree will be updated to a new layout.
386 It will be in an inconsistent state until noted in the UPDATING
387 file, or with asami-san's message to the relevant mailing
388 lists. With this new layout, you'll need to update the whole
389 tree for anything to work.
392 There was a change in the passwd format. Need more information.
395 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
396 place. Please update boot loader (not the boot blocks) at the
397 same time as your kernel.
400 The new pmtimer device is necessary for laptops. Failure to
401 include the device will cause suspended laptops losing time
402 when they resume. Include
404 in your config file and
405 hint.pmtimer.0.at="isa"
406 to your /boot/device.hints file.
409 The random device has been turned into a (pseudo-)device,
410 rather than an option. The supplied kernel config files have
411 been updated. You will need to do something similar in your
412 own kernel config file.
417 If you prefer to load the loadable module, you need to do
421 The random device module has been renamed from randomdev.ko to
422 random.ko. You will need to edit your /boot/loader.conf to
423 reflect this if you load this module at boot time.
424 The line should read:
428 The SMPNG commit has happened. It should work, but if it
429 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
430 to be a variety of minor issues. Please see 20000905 to make
431 sure you don't have model loading problems which might at
432 first blush appear related to SMP.
435 nsswitch has been imported from NetBSD. Among other things,
436 this means that /etc/host.conf is no longer used. See
437 nsswitch.conf(5) instead. Note that at boot time rc.network
438 will attempt to produce a new nsswitch.conf file for you if you
439 don't have one, and you have host.conf.
442 The ucred structure changed size. This breaks the interface
443 that mountd uses. Trying to use an older mountd with a newer
444 kernel guarantees a panic. This means that you need to use
445 kernels newer than today only with matching mountd, but you
446 needed to do that anyway with the boot loader changes.
449 The boot loader has been updated. The new default kernel is
450 now /boot/kernel/kernel.ko. The new default module location
453 You *MUST* upgrade your boot loader and kernel at the same time.
454 The easiest way to do this is to do the buildworld/buildkernel/
455 installkernel/installworld dance.
457 Furthermore, you are urged to delete your old /modules directory
458 before booting the new kernel, since kldload will find stale
459 modules in that directory instead of finding them in the correct
460 path, /boot/kernel. The most common complaint that this cures
461 is that the linux module crashes your machine after the update.
463 if [ ! -d /boot/kernel.old ]; then
464 mv /modules.old /boot/kernel.old
465 chflags noschg /kernel.old
466 mv /kernel.old /boot/kernel.old/kernel.ko
467 chflags schg /boot/kernel.old/kernel.ko
471 A new issue with the sendmail upgrade has come to light.
472 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
473 incorrectly install the default aliases in /etc/mail rather than
474 move the old one from /etc. So you'll need to manually move the
475 file, create a symbolic link, remove the old /etc/aliases.db and
476 run newaliases. For safety sake, you should stop sendmail
477 while doing this and run the upgrade when locally sourced email
478 is not likely to be generated.
481 /boot/device.hints is now required for installkernel to
482 succeed. You should copy GENERIC.hints for your architecture
483 into /boot/device.hints. If and only if you compile hints
484 into your kernel, then this file may be empty. Please note,
485 if you have an empty or missing /boot/device.hints file and
486 you neglected to compile hints into your kernel, no boot
487 messages will appear after the boot loader tries to start the
491 If you do NOT have ``options RANDOMDEV'' in your kernel and
492 you DO want the random device then add randomdev_load="YES" to
496 suidperl is now always built and installed on the system, but
497 with permissions of 511. If you have applications that use
498 this program, you are now required to add ENABLE_SUIDPERL=true
499 to /etc/make.conf. If you forget to do this,
500 chmod 4511 /usr/bin/suidperl
501 will fix this until the next build.
504 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
505 visible changes that may immediately affect your configuration
507 - New default file locations from src/contrib/sendmail/cf/README
508 - newaliases limited to root and trusted users
509 - MSA port (587) turned on by default
510 - New queue file naming system so can't go from 8.11 -> 8.9
511 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
512 - FEATURE(`nullclient') is more full featured
513 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
514 - mail.local FreeBSD-only -b option changed to -B
515 - See src/contrib/sendmail/RELEASE_NOTES for more info
518 suidperl (aka sperl) is no longer build by default. You must
519 specifically define BUILD_SUIDPERL to "true" for it to be build.
520 Furthermore, we recommend that you remove /usr/bin/sperl* and
521 /usr/bin/suidperl files from your system unless you have a
525 Networking defaults have been tightened. Anybody upgrading
526 /etc/defaults/rc.conf needs to add the following lines to
527 /etc/rc.conf if they want to have the same setup
528 afterwards (unless the variables already are set, of course):
529 # Enable network daemons for user convenience.
532 sendmail_enable="YES"
535 If you have null_load="YES" in your /boot/loader.conf, you
536 will need to change that to nullfs_load="YES".
539 The "installkernel" target has changed slightly. Now even if
540 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
541 it will install the MYKERNEL file (built with the buildkernel
542 target) as /kernel rather than /MYKERNEL. Those who have
543 updated their /boot/loader.conf files to point to /MYKERNEL
544 should remove that entry or perform manual rename of /kernel
548 If you use CVSUP or CTM to get CVS trees, AND you used to get
549 the old crypto files from internat.freebsd.org AND you check
550 out files from the CVS tree with the cvs command, please read
551 http://people.freebsd.org/~imp/internat.txt
552 for details on potential problems that you might have and how
555 If you are merely a mirror, or don't answer yes to each of the
556 clauses above, you needn't worry.
559 /etc/security has been updated to print the inode number of
560 setuid programs that have changed. You will see a large spike
561 in the number of changed programs the first time when you run
562 mergemaster to get a new /etc/security.
565 /dev/random now has good entropy collection (from the keyboard
566 and sysmouse drivers). Please ensure that either `options
567 RANDOMDEV' is present in your kernel config file or that
568 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
569 not have the /dev/random driver, OpenSSL (and consequently
570 lots of crypto tools (like SSH)) will fail with strange
571 errors. (see below, 20000624).
573 FreeBSD-current is safe again to run Crypto.
576 phk made the malloc default options AJ. This may slow things
577 down and uncover other latent bugs in the code. If you need to
578 run at full speed, you can disable this by doing the following:
579 ln -s aj /etc/malloc.conf
582 libftpio's version was accidentally bumped a few days ago. This
583 has been corrected. You may need to remove /usr/lib/libftpio.so.6
584 before doing your next buildworld/installworld pair. It certainly
585 won't hurt to remove it before the update procedure. It will
586 break fetch until a new one is built, but ftp can be used in the
590 The crypto packages have changed for the cvsup. This has been done
591 in a backward compatible way, but the old packages will go away at
592 some point in the future. Look at /usr/share/examples/cvsup for
596 With the new sys/modules/sound/drivers/*, you will need to
597 set SYSDIR until you do an installworld after July 7th.
600 rc.shutdown and rc will now call the rc.d scripts with start
601 or stop. This may cause some harmless warnings from older
602 rc.d scripts that haven't been updated.
605 The libfetch based version of fetch has gone into the tree.
606 Minor problems may result on some of the less popular sites,
607 which should be reported to des@freebsd.org.
610 From approximately this date forward, one must have the crypto
611 system installed in order to build the system and kernel.
612 While not technically strictly true, one should treat it as
613 required and grab the crypto bits. If you are grabbing CVS
614 trees, src-all and cvs-crypto should be treated as if they
615 were required. You should check with the latest collections
616 to make sure that these haven't changed.
619 Mark Murray just committed the first parts of a cleanup of
620 /dev/zero, et al. This is also cleaning up /dev/random.
621 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
622 -CURRENT FROM THIS POINT FORWARD for cryptographic services
623 until Mark can merge in the fixes to this work in progress.
624 openssh and openssl should not be used to generate keys from this
625 date to the completion of the work.
627 If you must operate at this reduced level of security, add '
628 options RANDOMDEV' to your kernel or modload the randomdev
629 module. You may also need to copy a new MAKEDEV to /dev and
630 recreate the random and urandom devices.
633 The license on the softupdates is now a standard 2 clause
634 BSD license. You may need to remove your symbolic links
635 that used to be required when updating.
638 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
639 the config file update procedure.
640 http://people.freebsd.org/~imp/config-upd.html
641 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
642 isn't buildable. However, you can generate a LINT file.
645 Binutils 2.10 have hit the tree, or will shortly. As soon
646 as they do, the problem noted in 20000522 will be resolved and
647 that workaround will no longer be required.
650 phk removed the compatibility creation of wd devices in the
651 ad driver. If you haven't done so already, you must update
652 your fstab, etc to use the ad devices instead of the wd
655 In addition, you'll need to update your boot blocks to a
656 more modern version, if you haven't already done so. Modern
657 here means 4.0 release or newer (although older releases
661 Peter took an axe to config(8). Be sure that you read his mail
662 on the topic before even thinking about updating. You will
663 need to create a /boot/device.hints or add a hints directive
664 to your config file to compile them in statically. The format
665 of the config file has changed as well. Please see GENERIC or
666 NEWCARD for examples of the new format.
669 A new set of binutils went into the tree today. Anybody
670 building a kernel after this point is advised that they need
671 to rebuild their binutils (or better yet do a
672 buildworld/installworld) before building a new kernel.
674 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
675 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
676 is recommended that you don't set this option until the problem
680 The ethernet drivers were all updated to clean up the BPF handling.
683 The problems with boot blocks on the alphas have been corrected.
684 This will require some care in updating alphas. A new libstand
685 is requires for the boot blocks to build properly.
688 Recompile all kld modules. Proper version dependency info
692 Modules have been disconnected from the buildworld tree and
693 connected to the kernel building instead.
696 You may need to build gperf
697 cd /usr/src/gnu/usr.bin/gperf && make depend all install
698 when upgrading from 4.0 -> current. The build system now uses
699 an option only in -current.
702 The method that we brand ELF binaries has changed to be more
703 acceptable to the binutils maintainers. You will need to
704 rebrand your ELF binaries that aren't native. One problem
705 binary is the Linux ldconfig. After your make world, but
706 before you reboot, you'll need to issue:
707 brandelf -t Linux /compat/linux/sbin/ldconfig
708 if you have Linux compatibility enabled on your machine.
711 If you have really bad/marginal IDE drives, you may find they
712 don't work well. Use pio mode instead. The easiest way to
713 cope if you have a problem combination is to add:
714 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
715 to the start of /etc/rc.conf.
718 The ISA and PCI compatibility shims have been connected to the
719 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
720 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
721 include the appropriate option in your kernel config. Drivers
722 using the shims should be updated or they won't ship with
723 5.0-RELEASE, targeted for 2001.
726 We've entered the traditional post release dumping party.
727 Large kernel changes are being committed and are in the
728 works. It is important to keep the systems' klds and kernel
729 in sync as kernel interfaces and structures are changing.
730 Before reporting kernel panics, make sure that all modules
731 that you are loading are up to date.
734 If you are upgrading from an older version of FreeBSD, you
735 need to update your boot blocks as well. 'disklabel -B ad0'
736 will do the trick. This isn't critical until you remove your
737 wd device entries in /dev, at which point your system will not
741 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
742 to upgrade to 4.0 from 3.x.
748 Avoid using make -j when upgrading. From time to time in the
749 past there have been problems using -j with buildworld and/or
750 installworld. This is especially true when upgrading between
751 "distant" versions (eg one that cross a major release boundary
752 or several minor releases, or when several months have passed
753 on the -current branch).
757 If you are updating from a prior version of FreeBSD (even one just
758 a few days old), you should follow this procedure. With a
759 /usr/obj tree with a fresh buildworld,
760 make buildkernel KERNCONF=YOUR_KERNEL_HERE
761 make installkernel KERNCONF=YOUR_KERNEL_HERE
763 To just build a kernel when you know that it won't mess you up
764 --------------------------------------------------------------
765 cd src/sys/{i386,alpha}/conf
766 config KERNEL_NAME_HERE [1]
767 cd ../../compile/KERNEL_NAME_HERE
772 [1] If in doubt, -r might help here.
774 If this fails, go to the "To build a kernel" section.
776 To rebuild everything and install it on the current system.
777 -----------------------------------------------------------
779 Build a new kernel, see above.
781 To upgrade from 4.x-stable to current
782 -------------------------------------
784 make buildkernel KERNCONF=YOUR_KERNEL_HERE
785 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
786 make installkernel KERNCONF=YOUR_KERNEL_HERE
787 reboot in single user [3]
793 Make sure that you've read the UPDATING file to understand the
794 tweaks to various things you need. At this point in the life
795 cycle of current, things change often and you are on your own
796 to cope. The defaults can also change, so please read ALL of
797 the UPDATING entries.
799 Also, if you are tracking -current, you must be subscribed to
800 freebsd-current@freebsd.org. Make sure that before you update
801 your sources that you have read and understood all the recent
802 messages there. If in doubt, please track -stable which has
805 [1] If you have third party modules, such as vmware, you
806 should disable them at this point so they don't crash your
809 [2] If you have legacy ISA devices, you may need to create
810 your own device.hints to reflect your unique hardware
813 [3] From the bootblocks, boot -s, and then do
818 adjkerntz -i # if COMS is wall time
820 [4] Note: This step is non-optional. Failure to do this step
821 can result in a significant reduction in the functionality of the
822 system. Attempting to do it by hand is not recommended and those
823 that pursue this avenue should read this file carefully, as well
824 as the archives of freebsd-current and freebsd-hackers mailing lists
825 for potential gotchas.
829 This file contains a list, in reverse chronological order, of major
830 breakages in tracking -current. Not all things will be listed here,
831 and it only starts on March 15, 2000. Updating files can found in
832 previous releases if your system is older than this.
834 Please filter your entries through Warner Losh (imp@village.org) so
835 that the style, formatting, etc of this file can be maintained.
837 Copyright information:
839 Copyright 1998, 2001 M. Warner Losh. All Rights Reserved.
841 Redistribution, publication, translation and use, with or without
842 modification, in full or in part, in any form or format of this
843 document are permitted.
845 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
846 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
847 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
848 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
849 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
850 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
851 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
852 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
853 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
854 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
855 POSSIBILITY OF SUCH DAMAGE.
857 If you find this document useful, and you want to, you may buy the
860 Contact Warner Losh if you have any questions about your use of