|
Lines 746-752
Link Here
|
| 746 |
from the obvious benefit of making things go slightly faster, |
746 |
from the obvious benefit of making things go slightly faster, |
| 747 |
reinstalling the system will touch a lot of important system |
747 |
reinstalling the system will touch a lot of important system |
| 748 |
files, all the standard system binaries, libraries, include files |
748 |
files, all the standard system binaries, libraries, include files |
| 749 |
and so on. Changing these on a running system (particularly if |
749 |
and so on. Changing these on a running system (particularly if |
| 750 |
you have active users on the system at the time) is asking for |
750 |
you have active users on the system at the time) is asking for |
| 751 |
trouble.</para> |
751 |
trouble.</para> |
| 752 |
|
752 |
|
|
Lines 754-760
Link Here
|
| 754 |
<para>Another method is to compile the system in multi-user mode, and |
754 |
<para>Another method is to compile the system in multi-user mode, and |
| 755 |
then drop into single user mode for the installation. If you would |
755 |
then drop into single user mode for the installation. If you would |
| 756 |
like to do it this way, simply hold off on the following steps until |
756 |
like to do it this way, simply hold off on the following steps until |
| 757 |
the build has completed.</para> |
757 |
the builds have completed; drop to single-user mode before using |
|
|
758 |
<maketarget>installkernel</maketarget> or |
| 759 |
<maketarget>installworld</maketarget>.</para> |
| 758 |
|
760 |
|
| 759 |
<para>As the superuser, you can execute</para> |
761 |
<para>As the superuser, you can execute</para> |
| 760 |
|
762 |
|
|
Lines 778-784
Link Here
|
| 778 |
|
780 |
|
| 779 |
|
781 |
|
| 780 |
<note> |
782 |
<note> |
| 781 |
<para>If your CMOS clock is set to local time and not to GMT, |
783 |
<para>If your CMOS clock is set to local time and not to GMT |
|
|
784 |
(if the output of the <command>date</command> doesn't show the |
| 785 |
correct time and zone), |
| 782 |
you may also need to run the following command:</para> |
786 |
you may also need to run the following command:</para> |
| 783 |
<screen>&prompt.root; <userinput>adjkerntz -i</userinput></screen> |
787 |
<screen>&prompt.root; <userinput>adjkerntz -i</userinput></screen> |
| 784 |
|
788 |
|
|
Lines 830-838
Link Here
|
| 830 |
when the process has finished.</para> |
834 |
when the process has finished.</para> |
| 831 |
|
835 |
|
| 832 |
<screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput> |
836 |
<screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput> |
| 833 |
Script started, output file is /var/tmp/mw.out |
837 |
Script started, output file is /var/tmp/mw.out |
| 834 |
&prompt.root; <userinput>make TARGET</userinput> |
838 |
&prompt.root; <userinput>make TARGET</userinput> |
| 835 |
<emphasis>… compile, compile, compile …</emphasis> |
839 |
<emphasis>… compile, compile, compile …</emphasis> |
| 836 |
&prompt.root; <userinput>exit</userinput> |
840 |
&prompt.root; <userinput>exit</userinput> |
| 837 |
Script done, …</screen> |
841 |
Script done, …</screen> |
| 838 |
|
842 |
|
|
Lines 944-961
Link Here
|
| 944 |
|
948 |
|
| 945 |
<para>It is now possible to specify a <option>-j</option> option to |
949 |
<para>It is now possible to specify a <option>-j</option> option to |
| 946 |
<command>make</command> which will cause it to spawn several |
950 |
<command>make</command> which will cause it to spawn several |
| 947 |
simultaneous processes. This is most useful on multi-CPU machines. |
951 |
simultaneous processes. This is most useful on multi-CPU machines.</para> |
| 948 |
However, since much of the compiling process is IO bound rather |
|
|
| 949 |
than CPU bound it is also useful on single CPU machines.</para> |
| 950 |
|
952 |
|
| 951 |
<para>On a typical single-CPU machine you would run:</para> |
|
|
| 952 |
|
| 953 |
<screen>&prompt.root; <userinput>make -j4 buildworld</userinput></screen> |
| 954 |
|
| 955 |
<para>&man.make.1; will then have up to 4 processes running at any one |
| 956 |
time. Empirical evidence posted to the mailing lists shows this |
| 957 |
generally gives the best performance benefit.</para> |
| 958 |
|
| 959 |
<para>If you have a multi-CPU machine and you are using an SMP |
953 |
<para>If you have a multi-CPU machine and you are using an SMP |
| 960 |
configured kernel try values between 6 and 10 and see how they speed |
954 |
configured kernel try values between 6 and 10 and see how they speed |
| 961 |
things up.</para> |
955 |
things up.</para> |
|
Lines 1000-1006
Link Here
|
| 1000 |
system back to single user mode. This is a good test that the new |
994 |
system back to single user mode. This is a good test that the new |
| 1001 |
system works properly. After booting from |
995 |
system works properly. After booting from |
| 1002 |
<filename>GENERIC</filename> and verifying that your system works you |
996 |
<filename>GENERIC</filename> and verifying that your system works you |
| 1003 |
can then build a new kernel based on your normal kernel configuration |
997 |
can then build a new kernel based on your normal kernel configuration |
| 1004 |
file.</para> |
998 |
file.</para> |
| 1005 |
|
999 |
|
| 1006 |
<para>If you are upgrading to &os; 4.0 or above then the old |
1000 |
<para>If you are upgrading to &os; 4.0 or above then the old |
|
Lines 1008-1019
Link Here
|
| 1008 |
is deprecated. Instead, you should run these commands |
1002 |
is deprecated. Instead, you should run these commands |
| 1009 |
<emphasis>after</emphasis> you have <link |
1003 |
<emphasis>after</emphasis> you have <link |
| 1010 |
linkend="make-buildworld">built the world with |
1004 |
linkend="make-buildworld">built the world with |
| 1011 |
<maketarget>buildworld</maketarget></link>.</para> |
1005 |
<maketarget>buildworld</maketarget></link>.</para> |
| 1012 |
|
1006 |
|
|
|
1007 |
<note> |
| 1008 |
<para>If you are building in multi-user mode, you'll need to drop to |
| 1009 |
single user mode before using <command>make |
| 1010 |
installkernel</command>; details are in <xref linkend="makeworld-singleuser">.</para> |
| 1011 |
</note> |
| 1012 |
|
| 1013 |
<screen>&prompt.root; <userinput>cd /usr/src</userinput> |
1013 |
<screen>&prompt.root; <userinput>cd /usr/src</userinput> |
| 1014 |
&prompt.root; <userinput>make buildkernel</userinput> |
1014 |
&prompt.root; <userinput>make buildkernel</userinput> |
| 1015 |
&prompt.root; <userinput>make installkernel</userinput></screen> |
1015 |
&prompt.root; <userinput>make installkernel</userinput></screen> |
|
Lines 1045-1051
Link Here
|
| 1045 |
&prompt.root; <userinput>make installworld</userinput></screen> |
1049 |
&prompt.root; <userinput>make installworld</userinput></screen> |
| 1046 |
|
1050 |
|
| 1047 |
<note> |
1051 |
<note> |
| 1048 |
<para>If you specified variables on the <command>make |
1052 |
<para>If you specified variables on the <command>make |
| 1049 |
buildworld</command> command line, you must specify the same |
1053 |
buildworld</command> command line, you must specify the same |
| 1050 |
variables in the <command>make installworld</command> command |
1054 |
variables in the <command>make installworld</command> command |
| 1051 |
line. This does not necessarily hold true for other options; |
1055 |
line. This does not necessarily hold true for other options; |
|
Lines 1601-1609
Link Here
|
| 1601 |
|
1605 |
|
| 1602 |
<listitem> |
1606 |
<listitem> |
| 1603 |
<para>Pass the <option>-j<n></option> option to &man.make.1; to |
1607 |
<para>Pass the <option>-j<n></option> option to &man.make.1; to |
| 1604 |
run multiple processes in parallel. This usually helps |
1608 |
run multiple processes in parallel.</para> |
| 1605 |
regardless of whether you have a single or a multi processor |
|
|
| 1606 |
machine.</para> |
| 1607 |
</listitem> |
1609 |
</listitem> |
| 1608 |
|
1610 |
|
| 1609 |
<listitem><para>The filesystem holding |
1611 |
<listitem><para>The filesystem holding |