Attachment 23108 Details for Bug 39858 – chapter.sgml.diff

[patch] chapter.sgml.diff

chapter.sgml.diff (text/plain), 5.05 KB, created by Chris Pepper on 2002-06-25 23:40:03 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Chris Pepper

Created: 2002-06-25 23:40:03 UTC

Size: 5.05 KB

patch

obsolete

>Index: chapter.sgml
>===================================================================
>RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v
>retrieving revision 1.127
>diff -u -r1.127 chapter.sgml
>--- chapter.sgml	2002/06/23 21:13:50	1.127
>+++ chapter.sgml	2002/06/25 21:28:30
>@@ -746,7 +746,7 @@
> 	from the obvious benefit of making things go slightly faster,
> 	reinstalling the system will touch a lot of important system
> 	files, all the standard system binaries, libraries, include files
>-	and so on.  Changing these on a  running system (particularly if
>+	and so on.  Changing these on a running system (particularly if
> 	you have active users on the system at the time) is asking for
> 	trouble.</para>
> 
>@@ -754,7 +754,9 @@
>       <para>Another method is to compile the system in multi-user mode, and
>         then drop into single user mode for the installation.  If you would
>         like to do it this way, simply hold off on the following steps until
>-        the build has completed.</para>
>+        the builds have completed; drop to single-user mode before using
>+        <maketarget>installkernel</maketarget> or
>+        <maketarget>installworld</maketarget>.</para>
> 
>       <para>As the superuser, you can execute</para>
> 
>@@ -778,7 +780,9 @@
> 
> 
>         <note>
>-          <para>If your CMOS clock is set to local time and not to GMT,
>+          <para>If your CMOS clock is set to local time and not to GMT
>+            (if the output of the <command>date</command> doesn't show the
>+            correct time and zone),
>             you may also need to run the following command:</para>
> <screen>&prompt.root; <userinput>adjkerntz -i</userinput></screen>
> 
>@@ -830,9 +834,9 @@
> 	  when the process has finished.</para>
> 
> 	<screen>&prompt.root; <userinput>script /var/tmp/mw.out</userinput>
>-Script started, output file is /var/tmp/mw.out	 
>+Script started, output file is /var/tmp/mw.out
> &prompt.root; <userinput>make TARGET</userinput>
>-<emphasis>&hellip; compile, compile, compile &hellip;</emphasis>	  
>+<emphasis>&hellip; compile, compile, compile &hellip;</emphasis>
> &prompt.root; <userinput>exit</userinput>
> Script done, &hellip;</screen>
> 
>@@ -944,18 +948,8 @@
>  
>         <para>It is now possible to specify a <option>-j</option> option to
>           <command>make</command> which will cause it to spawn several
>-          simultaneous processes.  This is most useful on multi-CPU machines.
>-          However, since much of the compiling process is IO bound rather
>-          than CPU bound it is also useful on single CPU machines.</para>
>+          simultaneous processes.  This is most useful on multi-CPU machines.</para>
> 
>-	<para>On a typical single-CPU machine you would run:</para>
>-	  
>-	  <screen>&prompt.root; <userinput>make -j4 buildworld</userinput></screen>
>-
>-	<para>&man.make.1; will then have up to 4 processes running at any one
>-	  time.  Empirical evidence posted to the mailing lists shows this
>-	  generally gives the best performance benefit.</para>
>-
> 	<para>If you have a multi-CPU machine and you are using an SMP
> 	  configured kernel try values between 6 and 10 and see how they speed
> 	  things up.</para>
>@@ -1000,7 +994,7 @@
> 	system back to single user mode.  This is a good test that the new
> 	system works properly.  After booting from
> 	<filename>GENERIC</filename> and verifying that your system works you
>-	can then build a new kernel based on your normal kernel	configuration
>+	can then build a new kernel based on your normal kernel configuration
> 	file.</para>
> 
>       <para>If you are upgrading to &os; 4.0 or above then the old
>@@ -1008,12 +1002,22 @@
> 	is deprecated.  Instead, you should run these commands
> 	<emphasis>after</emphasis> you have <link
>         linkend="make-buildworld">built the world with
>-        <maketarget>buildworld</maketarget></link>.</para> 
>+        <maketarget>buildworld</maketarget></link>.</para>
> 
>+      <note>
>+	<para>If you are building in multi-user mode, you'll need to drop to
>+	  single user mode before using <command>make
>+	  installkernel</command>; details are in <xref linkend="makeworld-singleuser">.</para>
>+      </note>
>+
>       <screen>&prompt.root; <userinput>cd /usr/src</userinput>
> &prompt.root; <userinput>make buildkernel</userinput>
> &prompt.root; <userinput>make installkernel</userinput></screen>
>@@ -1045,7 +1049,7 @@
> &prompt.root; <userinput>make installworld</userinput></screen>
> 
>       <note>
>-	<para>If you specified variables on the	  <command>make
>+	<para>If you specified variables on the <command>make
> 	    buildworld</command> command line, you must specify the same
> 	  variables in the <command>make installworld</command> command
> 	  line.  This does not necessarily hold true for other options;
>@@ -1601,9 +1605,7 @@
> 	      
> 	      <listitem>
> 		<para>Pass the <option>-j&lt;n&gt;</option> option to &man.make.1; to
>-		  run multiple processes in parallel.  This usually helps 
>-		  regardless of whether you have a single or a multi processor
>-		  machine.</para>
>+		  run multiple processes in parallel.</para>
> 	      </listitem>
> 	      
> 	      <listitem><para>The filesystem holding

Actions: View | Diff

Attachments on bug 39858: 23108