In message: <200502070810.53809.jonathan_at_fosburgh.org> Jonathan Fosburgh <jonathan_at_fosburgh.org> writes: : /usr/src/UPDATING doesn't seem too clear on this, and I can't find it in the : mailing lists. What is the current procedure to upgrade from 5-STABLE to : 6-CURRENT? Here's what I have in my tree, waiting to be committed. I've simplified out all the 4.x stuff since people still running 4.x should consider upgrading to 5.3 first. As such, I've removed all the work arounds for an imperfect evolution of the system. To upgrade in-place from 5.x-stable to current ---------------------------------------------- <make sure you have good level 0 dumps> make buildworld [9] make kernel KERNCONF=YOUR_KERNEL_HERE [8] [1] <reboot in single user> [3] mergemaster -p [5] make installworld mergemaster -i [4] <reboot> Make sure that you've read the UPDATING file to understand the tweaks to various things you need. At this point in the life cycle of current, things change often and you are on your own to cope. The defaults can also change, so please read ALL of the UPDATING entries. Also, if you are tracking -current, you must be subscribed to freebsd-current_at_freebsd.org. Make sure that before you update your sources that you have read and understood all the recent messages there. If in doubt, please track -stable which has much fewer pitfalls. [1] If you have third party modules, such as vmware, you should disable them at this point so they don't crash your system on reboot. [3] From the bootblocks, boot -s, and then do fsck -p mount -u / mount -a cd src adjkerntz -i # if CMOS is wall time Also, when doing a major release upgrade, it is required that you boot into single user mode to do the installworld. [4] Note: This step is non-optional. Failure to do this step can result in a significant reduction in the functionality of the system. Attempting to do it by hand is not recommended and those that pursue this avenue should read this file carefully, as well as the archives of freebsd-current and freebsd-hackers mailing lists for potential gotchas. [5] Usually this step is a noop. However, from time to time you may need to do this if you get unknown user in the following step. It never hurts to do it all the time. You may need to install a new mergemaster (cd src/usr.sbin/mergemaster && make install) after the buildworld before this step if you last updated from current before 20020224 or from -stable before 20020408. [8] In order to have a kernel that can run the 4.x binaries needed to do an installworld, you must include the COMPAT_FREEBSD4 option in your kernel. Failure to do so may leave you with a system that is hard to boot to recover. Make sure that you merge any new devices from GENERIC since the last time you updated your kernel config file. [9] When checking out sources, you must include the -P flag to have cvs prune empty directories. If CPUTYPE is defined in your /etc/make.conf, make sure to use the "?=" instead of the "=" assignment operator, so that buildworld can override the CPUTYPE if it needs to. MAKEOBJDIRPREFIX must be defined in an environment variable, and not on the command line, or in /etc/make.conf. buildworld will warn if it is improperly defined.Received on Mon Feb 07 2005 - 16:18:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:27 UTC