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 Most of the awk issues have been resolved. Some rough
10 edges may be left, but for the most part things should be
11 back to "normal." For CURRENT's usual definition of "normal.
14 Awk has been upgraded to the one true awk from bell labs. Expect
15 choppy waves in the upgrade process.
18 The asr driver problem has been resolved.
21 Due to changes in other parts of the system, the asr driver
22 now causes the system to panic on boot. Do not use it pending
23 correction. Comment it out of any kernel config file that you
24 try to use from this date forward.
27 When crossbuilding, use TARGET=xxx where you used to use
28 MACHINE=xxx. You don't need to set TARGET_ARCH and TARGET,
29 unless you are changing both of them. To cross build pc98 on
30 an alpha, for example, you need to set TARGET=pc98 and
34 The kernel interface that burncd depends on has changed.
35 You must recompile both the kernel and userland applications
39 When crossbuilding, please set TARGET_ARCH rather than
40 MACHINE_ARCH to indicate the target. In the future, one will
41 set TARGET_MACHINE where you set MACHINE now. At the moment,
42 setting MACHINE alone for same MACHINE_ARCH machines works
43 (eg, you can build pc98 on a i386 machine and vice versa).
46 Some weird problems result from using ACPI on some machines.
47 To disable ACPI you can add
48 hint.acpi.0.disable="1"
49 to /boot/loader.conf (or by putting set X=Y at the boot
52 Alternatively, you can remove it from /boot/kernel/acpi.ko
53 or use the MODULES_OVERRIDE function in your kernel config
54 file and not list acpi in that list.
57 The buildworld has been fixed. You may need to install
58 the 4.x compatibility libraries for some old binaries
60 cd src/lib/compat/compat4x.i386
64 There's a bug in the world build process. The cross-tools
65 are build with the NEW headers, but the OLD libc.a. This
66 leads to all kinds of problems with the new libc. A temporary
68 CFLAGS="-O -pipe -D_OLD_STDIO"
69 before building world when upgrading from 4.x to current. This
70 can be removed afterwards.
72 A proper fix to the buildworld target is needed.
75 Peter has committed his new kthread nfs client/server code.
76 NFS may be unstable after this date.
79 KSE has hit the tree. Lots of things are now different in
80 the kernel. While a few problems were introduced in the
81 initial commit, most of the major ones have been found and
85 In OLDCARD, CardBus bridges appear to be stable. The work
86 arounds described in the 20010604 entry are now no longer
87 necessary and will be ignored. Most insert/remove problems
88 have been rectified around this date.
91 named now runs as user bind and group bind rather than as
92 root. If named_enable is set to YES in /etc/rc.conf, ensure
93 that user bind is available in /etc/passwd (using vipw(8))
94 and that group bind is available in /etc/group. Also make
95 sure that user or group bind has read (and not write)
96 permission for your name server configuration and that it
97 has read and write permission for your slave zone files and
100 If you wish to continue to run named as root (a less secure
101 alternative), add a line to /etc/rc.conf saying
106 The PAM libraries have had an API upgrade that is beyond
107 the ability of the shared library major number to handle.
108 It is manifested by PAM-using ports dumping core. The
109 solution is to rebuild those ports.
112 The kernel compile module has moved from src/sys/compile/FOO
113 to src/sys/${MACHINE}/compile/FOO.
116 The pccard modem issue from 20010613 has been corrected.
117 OLDCARD support is still a little weak in -current. slot 1 is
118 known not to work on some TI based cardbus bridges. Some
119 cardbus bridges do not properly detect insert/removal events.
120 IRQ configuration needs more safety belts.
123 Softupdates problems have been corrected.
126 Peter ripped out the linkerset support. You must, as always,
127 rerun config after you cvsup if you are using the traditional
128 kernel building methods.
131 pccard modems may not work with current after 20010604 date. Some
132 do, others result in panics. *MAKE*SURE* that you update your
133 config and /etc/rc.conf ala the 20010604 entry, or you will have
134 problems (this issue will be fixed, it just hasn't been yet).
137 SOFTUPDATES seem to be broken since the middle of May or so. Do not
138 use them in current. You can disable softupdates on all mounted
139 partitions, or remove SOFTUPDATES the kernel config file.
142 After Peter's commits to the hints code, people have been noticing
143 that certain devices are attached (or try to) twice. This is due
144 to having both static hints as well as a /boot/device.hints. To
145 work around this issue, please use only one or the other mechanism
146 until this bug is fixed.
148 Please note that a feature of config is that if you have config
149 file FOO and FOO.hints, it automatically adds FOO.hints to the
150 hints.c file, wheather you want it to or not.
153 Locale names have changed to match other systems better.
156 pccard support for pci cards has been committed. You must change
157 your /etc/pccard.conf irq lines. It must match the irq used by
158 pcic device. Interrupt storms may result if you fail to do this.
159 Interrupt storms look a lot like a hang.
161 You must also install a new pccardd, otherwise you will get an
162 interrupt storm at card reset time (just after it tells you what
165 pccardd_flags="-I" is necessary for the time being. It tells pccardd
166 not to ask the kernel if the interrupt is really free or not before
167 using it. You can either change the /etc/pccard.conf irq lines to
168 match pcic, or add "-i X" to the pccardd_flags.
171 INSTALL=install -C is being deprecated. If you want to do this,
172 use COPY=-C instead. The former method will be supported for only
173 a limited time. If you see
175 install: warning: the -d and -C options may not be specified together
177 in your makeworld, then you need to migrate towards using
181 It appears that vm is now stable enough to use again. However,
182 there may be other problems, so caution is still urged. alpha
183 definitely is in bad shape.
186 Minor repo damange has happened. This may cause problems
187 with cvsup of ports. If you get errors, please see
188 http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27495
189 at the bottom for details on a workaround. The error message
191 Updater failed: Cannot delete "/usr/ports/www/jakarta-tomcat/files": Directory not empty
194 Vm and/or swapping are busted on -current. Please be patient.
197 pccard has had much reorganizational work done to it over
198 the past few days. Everything should still work, but if
199 not, please contact imp@freebsd.org.
202 ata ioctl changed. Make sure to recompile both kernel and
203 userland at the same time.
206 New ncurses imported.
209 DEVFS is now opt out, not opt in. Barring major problems, this
210 will be the only way to go starting July 1.
213 Perl breakage in 20010501 was corrected at 14:18:33 PDT.
216 Building perl was broken at 02:25:25 PDT.
219 The bug in 20010429 was corrected at 07:35:37 PDT. It is safe to
220 go back in the water.
223 A bad bug was committed at 04:48:42 PDT. Don't use kernels after
224 this date, but before the correction date.
227 old fsck and new kernel interactions appear to have been fixed.
230 fsck and the kernel were changed to handle some optimizations
231 to directory layout. This breaks backward compatibility.
232 Update only if you understand that you must not use the old
233 fsck with the new kernel ever.
236 fsck has changed the meaning of the pass column in /etc/fstab.
237 Please see the cvs commit to fsck.8 or the fsck.8 man page for
238 details. It is unclear if changes to /etc/fstab are necessary.
241 portmap had changed name to rpcbind for maximum POLA in your
242 current world. /etc/hosts.{allow,deny} needs changes. nfs and
243 other rpc based programs that rely on portmapper will not work
244 without updates to /etc/hosts.{allow,deny} and /etc/netconfig.
247 ata subsystem changes. ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC
248 and ATA_ENABEL_TAGS are no longer kernel options. They have
249 been replaced by tunables. See ata.4 for details.
252 The fxp driver was converted to use miibus. If you compile
253 fxp into your kernel statically, you will need to add miibus.
256 The wi device now defaults to BSS (infrastructure) mode
260 /dev/urandom should be a symbolic link to /dev/random now.
261 Users of current not using DEVFS need to run MAKEDEV std.
262 ssh might not work if you don't.
265 The ed driver has been updated. It now allows mii attachments,
266 which means that you must include the miibus in your kernel if
267 you use the ed driver.
270 The problems with libc have been corrected. It is now mostly
271 safe to go back into the water.
274 The size of FILE was changed. This breaks upgrading. If
275 you must upgrade, be prepared for pain. It also breaks almost
276 all binaries that you've compiled on -current. You are warned
277 that before upgrading would be a good time to do a level 0
278 dump of your system. No, really, I mean it this time.
280 To get to the new system, you'll need to use the following
281 workaround. Hopefully this can be sorted out so that we
282 don't have to move this to the updating section.
284 To get around the installworld problem, do:
285 # cd /usr/src/usr.bin/sed
289 If that doesn't work, then try:
290 # make -k installworld
294 DEVFS is now the default. If you use vinum, make sure that you
295 do not include devfs in your kernel as problems result.
298 FFS_ROOT and CD9660_ROOT have been removed or deprecated.
299 Remove them from your config.
302 ****************************** WARNING ******************************
303 buildkernel has been changed slightly
304 ****************************** WARNING ******************************
305 KERNCONF replaces the variable KERNEL for buildkernel. You
306 should update your scripts and make.conf accordingly.
309 config has changed to allow DEV_FOO as a replacement for NFOO.
310 This requires a new config to build correctly.
313 The kerrnel option I386_CPU is now mutually exclusive with the
314 other cpu types. If you have an i386 system, be sure that it
315 only had this line. Remove it for all other configurations.
318 Changes to the kernel require it and burncd be in sync.
321 Everyone who has hw.sndunit set to something in
322 /etc/sysctl.conf, it is now hw.snd.unit.
325 ex and vi were broken by some changes to sys/queue.h. If you
326 have a bad vi, you will see make buildworld fail with a core
327 dump while building termcap. You can work around this problem
328 by adding -k to your make buildworld. This will cause the
329 build to complete and install a new vi. Once that's done, you
330 can rebuild again without the -k to pick up anything that
331 might have been ignored by the -k option.
333 Others have suggested that you can just rebuild libc if your
334 vi/ex is dynamically linked, but I've not received any reports
338 There have been some changes to libcrypt in -current. The
339 libscrypt/libdescrypt symlink sillyness is gone and the installed
340 libcrypt is fully functional. Be aware of this.
343 Linksys Fast Ethernet PCCARD cards supported by the ed driver
344 now require the addition of flag 0x80000 to their config line
345 in pccard.conf(5). This flag is not optional. These Linksys
346 cards will not be recognized without it.
349 Important new FreeBSD-version stuff: PAM support has been worked
350 in, partially from the "Unix" OpenSSH version. This requires
351 adding the following in pam.conf:
353 sshd auth sufficient pam_skey.so
354 sshd auth required pam_unix.so try_first_pass
355 sshd session required pam_permit.so
361 The random device needs more entropy, so you need to make sure
362 that you've run mergemaster to get a /etc/rc which will seed
363 /dev/random. If you don't and the system hangs after ldconfig,
364 then banging on the keyboard randomly until it unhangs is one
368 ****************************** WARNING ******************************
369 Sendmail has been updated.
370 ****************************** WARNING ******************************
371 o mail.local(8) is no longer installed as a set-user-id binary.
372 o sendmail(8) is now built with STARTTLS support unless NO_OPENSSL
374 o The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY
376 o Now using sendmail's version of vacation(1).
377 o The sendmail cf building tools (contrib/sendmail/cf) are installed
378 in /usr/share/sendmail/cf.
379 o sendmail.cw changed to local-host-names
381 More details can be found at
382 http://people.freebsd.org/~imp/UPDATING/sendmail-20001010
385 The ports tree's new layout is in place. Be sure to update
386 your entire ports tree, or you will have problems.
389 The perl build procedure no longer installs miniperl, nor uses
390 the installed miniperl. It is recommended that you delete
394 This weekend the ports tree will be updated to a new layout.
395 It will be in an inconsistent state until noted in the UPDATING
396 file, or with asami-san's message to the relevant mailing
397 lists. With this new layout, you'll need to update the whole
398 tree for anything to work.
401 There was a change in the passwd format. Need more information.
404 /boot/kernel/kernel.ko -> /boot/kernel/kernel change has taken
405 place. Please update boot loader (not the boot blocks) at the
406 same time as your kernel.
409 The new pmtimer device is necessary for laptops. Failure to
410 include the device will cause suspended laptops losing time
411 when they resume. Include
413 in your config file and
414 hint.pmtimer.0.at="isa"
415 to your /boot/device.hints file.
418 The random device has been turned into a (pseudo-)device,
419 rather than an option. The supplied kernel config files have
420 been updated. You will need to do something similar in your
421 own kernel config file.
426 If you prefer to load the loadable module, you need to do
430 The random device module has been renamed from randomdev.ko to
431 random.ko. You will need to edit your /boot/loader.conf to
432 reflect this if you load this module at boot time.
433 The line should read:
437 The SMPNG commit has happened. It should work, but if it
438 doesn't, fallback to the PRE_SMPNG CVS tag. There are likely
439 to be a variety of minor issues. Please see 20000905 to make
440 sure you don't have model loading problems which might at
441 first blush appear related to SMP.
444 nsswitch has been imported from NetBSD. Among other things,
445 this means that /etc/host.conf is no longer used. See
446 nsswitch.conf(5) instead. Note that at boot time rc.network
447 will attempt to produce a new nsswitch.conf file for you if you
448 don't have one, and you have host.conf.
451 The ucred structure changed size. This breaks the interface
452 that mountd uses. Trying to use an older mountd with a newer
453 kernel guarantees a panic. This means that you need to use
454 kernels newer than today only with matching mountd, but you
455 needed to do that anyway with the boot loader changes.
458 The boot loader has been updated. The new default kernel is
459 now /boot/kernel/kernel.ko. The new default module location
462 You *MUST* upgrade your boot loader and kernel at the same time.
463 The easiest way to do this is to do the buildworld/buildkernel/
464 installkernel/installworld dance.
466 Furthermore, you are urged to delete your old /modules directory
467 before booting the new kernel, since kldload will find stale
468 modules in that directory instead of finding them in the correct
469 path, /boot/kernel. The most common complaint that this cures
470 is that the linux module crashes your machine after the update.
472 if [ ! -d /boot/kernel.old ]; then
473 mv /modules.old /boot/kernel.old
474 chflags noschg /kernel.old
475 mv /kernel.old /boot/kernel.old/kernel.ko
476 chflags schg /boot/kernel.old/kernel.ko
480 A new issue with the sendmail upgrade has come to light.
481 /etc/aliases has moved to /etc/mail/aliases. Mergemaster will
482 incorrectly install the default aliases in /etc/mail rather than
483 move the old one from /etc. So you'll need to manually move the
484 file, create a symbolic link, remove the old /etc/aliases.db and
485 run newaliases. For safety sake, you should stop sendmail
486 while doing this and run the upgrade when locally sourced email
487 is not likely to be generated.
490 /boot/device.hints is now required for installkernel to
491 succeed. You should copy GENERIC.hints for your architecture
492 into /boot/device.hints. If and only if you compile hints
493 into your kernel, then this file may be empty. Please note,
494 if you have an empty or missing /boot/device.hints file and
495 you neglected to compile hints into your kernel, no boot
496 messages will appear after the boot loader tries to start the
500 If you do NOT have ``options RANDOMDEV'' in your kernel and
501 you DO want the random device then add randomdev_load="YES" to
505 suidperl is now always built and installed on the system, but
506 with permissions of 511. If you have applications that use
507 this program, you are now required to add ENABLE_SUIDPERL=true
508 to /etc/make.conf. If you forget to do this,
509 chmod 4511 /usr/bin/suidperl
510 will fix this until the next build.
513 sendmail has been updated from 8.9.3 to 8.11.0. Some of the more
514 visible changes that may immediately affect your configuration
516 - New default file locations from src/contrib/sendmail/cf/README
517 - newaliases limited to root and trusted users
518 - MSA port (587) turned on by default
519 - New queue file naming system so can't go from 8.11 -> 8.9
520 - FEATURE(`rbl') renamed to FEATURE(`dnsbl')
521 - FEATURE(`nullclient') is more full featured
522 - FEATURE(`nouucp') requires an argument: `reject' or `nospecial'
523 - mail.local FreeBSD-only -b option changed to -B
524 - See src/contrib/sendmail/RELEASE_NOTES for more info
527 suidperl (aka sperl) is no longer build by default. You must
528 specifically define BUILD_SUIDPERL to "true" for it to be build.
529 Furthermore, we recommend that you remove /usr/bin/sperl* and
530 /usr/bin/suidperl files from your system unless you have a
534 Networking defaults have been tightened. Anybody upgrading
535 /etc/defaults/rc.conf needs to add the following lines to
536 /etc/rc.conf if they want to have the same setup
537 afterwards (unless the variables already are set, of course):
538 # Enable network daemons for user convenience.
541 sendmail_enable="YES"
544 If you have null_load="YES" in your /boot/loader.conf, you
545 will need to change that to nullfs_load="YES".
548 The "installkernel" target has changed slightly. Now even if
549 you override KERNEL e.g. 'make installkernel KERNEL=MYKERNEL'
550 it will install the MYKERNEL file (built with the buildkernel
551 target) as /kernel rather than /MYKERNEL. Those who have
552 updated their /boot/loader.conf files to point to /MYKERNEL
553 should remove that entry or perform manual rename of /kernel
557 If you use CVSUP or CTM to get CVS trees, AND you used to get
558 the old crypto files from internat.freebsd.org AND you check
559 out files from the CVS tree with the cvs command, please read
560 http://people.freebsd.org/~imp/internat.txt
561 for details on potential problems that you might have and how
564 If you are merely a mirror, or don't answer yes to each of the
565 clauses above, you needn't worry.
568 /etc/security has been updated to print the inode number of
569 setuid programs that have changed. You will see a large spike
570 in the number of changed programs the first time when you run
571 mergemaster to get a new /etc/security.
574 /dev/random now has good entropy collection (from the keyboard
575 and sysmouse drivers). Please ensure that either `options
576 RANDOMDEV' is present in your kernel config file or that
577 `randomdev_load="YES"' is in your /boot/loader.conf. If you do
578 not have the /dev/random driver, OpenSSL (and consequently
579 lots of crypto tools (like SSH)) will fail with strange
580 errors. (see below, 20000624).
582 FreeBSD-current is safe again to run Crypto.
585 phk made the malloc default options AJ. This may slow things
586 down and uncover other latent bugs in the code. If you need to
587 run at full speed, you can disable this by doing the following:
588 ln -s aj /etc/malloc.conf
591 libftpio's version was accidentally bumped a few days ago. This
592 has been corrected. You may need to remove /usr/lib/libftpio.so.6
593 before doing your next buildworld/installworld pair. It certainly
594 won't hurt to remove it before the update procedure. It will
595 break fetch until a new one is built, but ftp can be used in the
599 The crypto packages have changed for the cvsup. This has been done
600 in a backward compatible way, but the old packages will go away at
601 some point in the future. Look at /usr/share/examples/cvsup for
605 With the new sys/modules/sound/drivers/*, you will need to
606 set SYSDIR until you do an installworld after July 7th.
609 rc.shutdown and rc will now call the rc.d scripts with start
610 or stop. This may cause some harmless warnings from older
611 rc.d scripts that haven't been updated.
614 The libfetch based version of fetch has gone into the tree.
615 Minor problems may result on some of the less popular sites,
616 which should be reported to des@freebsd.org.
619 From approximately this date forward, one must have the crypto
620 system installed in order to build the system and kernel.
621 While not technically strictly true, one should treat it as
622 required and grab the crypto bits. If you are grabbing CVS
623 trees, src-all and cvs-crypto should be treated as if they
624 were required. You should check with the latest collections
625 to make sure that these haven't changed.
628 Mark Murray just committed the first parts of a cleanup of
629 /dev/zero, et al. This is also cleaning up /dev/random.
630 The entropy is disconnected, so DO NOT USE VERSIONS OF FREEBSD
631 -CURRENT FROM THIS POINT FORWARD for cryptographic services
632 until Mark can merge in the fixes to this work in progress.
633 openssh and openssl should not be used to generate keys from this
634 date to the completion of the work.
636 If you must operate at this reduced level of security, add '
637 options RANDOMDEV' to your kernel or modload the randomdev
638 module. You may also need to copy a new MAKEDEV to /dev and
639 recreate the random and urandom devices.
642 The license on the softupdates is now a standard 2 clause
643 BSD license. You may need to remove your symbolic links
644 that used to be required when updating.
647 Scott Flatman <sf@aracnet.com> sent in a decent write-up on
648 the config file update procedure.
649 http://people.freebsd.org/~imp/config-upd.html
650 NOTE: LINT is gone. It has been replaced with NOTES. NOTES
651 isn't buildable. However, you can generate a LINT file.
654 Binutils 2.10 have hit the tree, or will shortly. As soon
655 as they do, the problem noted in 20000522 will be resolved and
656 that workaround will no longer be required.
659 phk removed the compatibility creation of wd devices in the
660 ad driver. If you haven't done so already, you must update
661 your fstab, etc to use the ad devices instead of the wd
664 In addition, you'll need to update your boot blocks to a
665 more modern version, if you haven't already done so. Modern
666 here means 4.0 release or newer (although older releases
670 Peter took an axe to config(8). Be sure that you read his mail
671 on the topic before even thinking about updating. You will
672 need to create a /boot/device.hints or add a hints directive
673 to your config file to compile them in statically. The format
674 of the config file has changed as well. Please see GENERIC or
675 NEWCARD for examples of the new format.
678 A new set of binutils went into the tree today. Anybody
679 building a kernel after this point is advised that they need
680 to rebuild their binutils (or better yet do a
681 buildworld/installworld) before building a new kernel.
683 Due to bugs in binutils, using malloc options (eg /etc/malloc.conf
684 or MALLOC_OPTIONS env var) J will cause ld to dump core. It
685 is recommended that you don't set this option until the problem
689 The ethernet drivers were all updated to clean up the BPF handling.
692 The problems with boot blocks on the alphas have been corrected.
693 This will require some care in updating alphas. A new libstand
694 is requires for the boot blocks to build properly.
697 Recompile all kld modules. Proper version dependency info
701 Modules have been disconnected from the buildworld tree and
702 connected to the kernel building instead.
705 You may need to build gperf
706 cd /usr/src/gnu/usr.bin/gperf && make depend all install
707 when upgrading from 4.0 -> current. The build system now uses
708 an option only in -current.
711 The method that we brand ELF binaries has changed to be more
712 acceptable to the binutils maintainers. You will need to
713 rebrand your ELF binaries that aren't native. One problem
714 binary is the Linux ldconfig. After your make world, but
715 before you reboot, you'll need to issue:
716 brandelf -t Linux /compat/linux/sbin/ldconfig
717 if you have Linux compatibility enabled on your machine.
720 If you have really bad/marginal IDE drives, you may find they
721 don't work well. Use pio mode instead. The easiest way to
722 cope if you have a problem combination is to add:
723 /sbin/sysctl -w hw.atamodes=pio,pio,pio,pio
724 to the start of /etc/rc.conf.
727 The ISA and PCI compatibility shims have been connected to the
728 options COMPAT_OLDISA and COMPAT_OLDPCI. If you are using old
729 style PCI or ISA drivers (i.e. tx, voxware, etc.) you must
730 include the appropriate option in your kernel config. Drivers
731 using the shims should be updated or they won't ship with
732 5.0-RELEASE, targeted for 2001.
735 We've entered the traditional post release dumping party.
736 Large kernel changes are being committed and are in the
737 works. It is important to keep the systems' klds and kernel
738 in sync as kernel interfaces and structures are changing.
739 Before reporting kernel panics, make sure that all modules
740 that you are loading are up to date.
743 If you are upgrading from an older version of FreeBSD, you
744 need to update your boot blocks as well. 'disklabel -B ad0'
745 will do the trick. This isn't critical until you remove your
746 wd device entries in /dev, at which point your system will not
750 4.0 RELEASE shipped. Please see the 4.0 UPDATING file for how
751 to upgrade to 4.0 from 3.x.
757 Avoid using make -j when upgrading. From time to time in the
758 past there have been problems using -j with buildworld and/or
759 installworld. This is especially true when upgrading between
760 "distant" versions (eg one that cross a major release boundary
761 or several minor releases, or when several months have passed
762 on the -current branch).
766 If you are updating from a prior version of FreeBSD (even one just
767 a few days old), you should follow this procedure. With a
768 /usr/obj tree with a fresh buildworld,
769 make buildkernel KERNCONF=YOUR_KERNEL_HERE
770 make installkernel KERNCONF=YOUR_KERNEL_HERE
772 To just build a kernel when you know that it won't mess you up
773 --------------------------------------------------------------
774 cd src/sys/{i386,alpha}/conf
775 config KERNEL_NAME_HERE [1]
776 cd ../../compile/KERNEL_NAME_HERE
781 [1] If in doubt, -r might help here.
783 If this fails, go to the "To build a kernel" section.
785 To rebuild everything and install it on the current system.
786 -----------------------------------------------------------
788 Build a new kernel, see above.
790 To upgrade from 4.x-stable to current
791 -------------------------------------
793 make buildkernel KERNCONF=YOUR_KERNEL_HERE
794 cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
795 make installkernel KERNCONF=YOUR_KERNEL_HERE
796 reboot in single user [3]
802 Make sure that you've read the UPDATING file to understand the
803 tweaks to various things you need. At this point in the life
804 cycle of current, things change often and you are on your own
805 to cope. The defaults can also change, so please read ALL of
806 the UPDATING entries.
808 Also, if you are tracking -current, you must be subscribed to
809 freebsd-current@freebsd.org. Make sure that before you update
810 your sources that you have read and understood all the recent
811 messages there. If in doubt, please track -stable which has
814 [1] If you have third party modules, such as vmware, you
815 should disable them at this point so they don't crash your
818 [2] If you have legacy ISA devices, you may need to create
819 your own device.hints to reflect your unique hardware
822 [3] From the bootblocks, boot -s, and then do
827 adjkerntz -i # if COMS is wall time
829 [4] Note: This step is non-optional. Failure to do this step
830 can result in a significant reduction in the functionality of the
831 system. Attempting to do it by hand is not recommended and those
832 that pursue this avenue should read this file carefully, as well
833 as the archives of freebsd-current and freebsd-hackers mailing lists
834 for potential gotchas.
838 This file contains a list, in reverse chronological order, of major
839 breakages in tracking -current. Not all things will be listed here,
840 and it only starts on March 15, 2000. Updating files can found in
841 previous releases if your system is older than this.
843 Please filter your entries through Warner Losh (imp@village.org) so
844 that the style, formatting, etc of this file can be maintained.
846 Copyright information:
848 Copyright 1998, 2001 M. Warner Losh. All Rights Reserved.
850 Redistribution, publication, translation and use, with or without
851 modification, in full or in part, in any form or format of this
852 document are permitted.
854 THIS DOCUMENT IS PROVIDED BY WARNER LOSH ``AS IS'' AND ANY EXPRESS OR
855 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
856 WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
857 DISCLAIMED. IN NO EVENT SHALL WARNER LOSH BE LIABLE FOR ANY DIRECT,
858 INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
859 (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
860 SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
861 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
862 STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
863 IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
864 POSSIBILITY OF SUCH DAMAGE.
866 If you find this document useful, and you want to, you may buy the
869 Contact Warner Losh if you have any questions about your use of