| UPDATING (b18a4ccab954b694b9ed6dcc83773f615c430d33) | UPDATING (8ed2d94ad6eb1ef4a649c529a76b6087ff9ebf3c) |
|---|---|
| 1 Updating Information for FreeBSD current users. 2 3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4See end of file for further details. For commonly done items, please see the 5COMMON ITEMS: section later in the file. These instructions assume that you 6basically know what you are doing. If not, then please consult the FreeBSD 7handbook: 8 --- 1887 unchanged lines hidden (view full) --- 1896 [1] If you have third party modules, such as vmware, you 1897 should disable them at this point so they don't crash your 1898 system on reboot. 1899 1900 [3] From the bootblocks, boot -s, and then do 1901 fsck -p 1902 mount -u / 1903 mount -a | 1 Updating Information for FreeBSD current users. 2 3This file is maintained and copyrighted by M. Warner Losh <imp@freebsd.org>. 4See end of file for further details. For commonly done items, please see the 5COMMON ITEMS: section later in the file. These instructions assume that you 6basically know what you are doing. If not, then please consult the FreeBSD 7handbook: 8 --- 1887 unchanged lines hidden (view full) --- 1896 [1] If you have third party modules, such as vmware, you 1897 should disable them at this point so they don't crash your 1898 system on reboot. 1899 1900 [3] From the bootblocks, boot -s, and then do 1901 fsck -p 1902 mount -u / 1903 mount -a |
| 1904 cd src | 1904 sh /etc/rc.d/zfs start # mount zfs filesystem, if needed 1905 cd src # full path to source |
| 1905 adjkerntz -i # if CMOS is wall time 1906 Also, when doing a major release upgrade, it is required that 1907 you boot into single user mode to do the installworld. 1908 1909 [4] Note: This step is non-optional. Failure to do this step 1910 can result in a significant reduction in the functionality of the 1911 system. Attempting to do it by hand is not recommended and those 1912 that pursue this avenue should read this file carefully, as well --- 13 unchanged lines hidden (view full) --- 1926 sure that no program is using those libraries anymore. 1927 1928 [8] The new kernel must be able to run existing binaries used by 1929 an installworld. When upgrading across major versions, the new 1930 kernel's configuration must include the correct COMPAT_FREEBSD<n> 1931 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x 1932 binaries). Failure to do so may leave you with a system that is 1933 hard to boot to recover. A GENERIC kernel will include suitable | 1906 adjkerntz -i # if CMOS is wall time 1907 Also, when doing a major release upgrade, it is required that 1908 you boot into single user mode to do the installworld. 1909 1910 [4] Note: This step is non-optional. Failure to do this step 1911 can result in a significant reduction in the functionality of the 1912 system. Attempting to do it by hand is not recommended and those 1913 that pursue this avenue should read this file carefully, as well --- 13 unchanged lines hidden (view full) --- 1927 sure that no program is using those libraries anymore. 1928 1929 [8] The new kernel must be able to run existing binaries used by 1930 an installworld. When upgrading across major versions, the new 1931 kernel's configuration must include the correct COMPAT_FREEBSD<n> 1932 option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x 1933 binaries). Failure to do so may leave you with a system that is 1934 hard to boot to recover. A GENERIC kernel will include suitable |
| 1934 compatibility options to run binaries from older branches. | 1935 compatibility options to run binaries from supported older branches. |
| 1935 1936 Make sure that you merge any new devices from GENERIC since the | 1936 1937 Make sure that you merge any new devices from GENERIC since the |
| 1937 last time you updated your kernel config file. | 1938 last time you updated your kernel config file. Options also 1939 change over time, so you may need to adjust your custom kernels 1940 for these as well. |
| 1938 1939 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1940 "?=" instead of the "=" assignment operator, so that buildworld can 1941 override the CPUTYPE if it needs to. 1942 1943 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1944 not on the command line, or in /etc/make.conf. buildworld will 1945 warn if it is improperly defined. --- 32 unchanged lines hidden --- | 1941 1942 [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the 1943 "?=" instead of the "=" assignment operator, so that buildworld can 1944 override the CPUTYPE if it needs to. 1945 1946 MAKEOBJDIRPREFIX must be defined in an environment variable, and 1947 not on the command line, or in /etc/make.conf. buildworld will 1948 warn if it is improperly defined. --- 32 unchanged lines hidden --- |