From owner-doc-jp@jp.freebsd.org  Thu Oct  7 23:05:47 1999
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id XAA18758;
	Thu, 7 Oct 1999 23:05:47 +0900 (JST)
	(envelope-from owner-doc-jp@jp.FreeBSD.org)
Received: from mail.kt.rim.or.jp (root@mail.kt.rim.or.jp [202.247.130.53])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id XAA18753
	for <doc-jp@jp.freebsd.org>; Thu, 7 Oct 1999 23:05:47 +0900 (JST)
	(envelope-from kuriyama@sky.rim.or.jp)
Received: from rhea.sky.rim.or.jp (ppp379.kt.rim.or.jp [202.247.140.79])
	by mail.kt.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id XAA16617
	for <doc-jp@jp.freebsd.org>; Thu, 7 Oct 1999 23:05:41 +0900 (JST)
Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1])
	by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.1) with ESMTP id XAA22599
	for <doc-jp@jp.freebsd.org>; Thu, 7 Oct 1999 23:05:36 +0900 (JST)
Date: Thu, 07 Oct 1999 23:05:35 +0900
Message-ID: <14332.43183.237266.44342F@localhost.sky.rim.or.jp>
From: Jun Kuriyama <kuriyama@sky.rim.or.jp>
To: Japanese Documentation Project <doc-jp@jp.freebsd.org>
User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd)
MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko")
Content-Type: text/plain; charset=ISO-2022-JP
Reply-To: doc-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+990727
X-Sequence: doc-jp 6761
Subject: [doc-jp 6761] <handbook> linuxemu/chapter.sgml (1.21 -> 1.23)
Errors-To: owner-doc-jp@jp.freebsd.org
Sender: owner-doc-jp@jp.freebsd.org
X-Originator: kuriyama@sky.rim.or.jp


$B!!%?%0$NDI2C$H=gHV$NF~$lBX$($+$J!)(B


Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v
retrieving revision 1.21
retrieving revision 1.23
diff -u -r1.21 -r1.23
--- chapter.sgml	1999/09/15 18:17:19	1.21
+++ chapter.sgml	1999/09/15 19:14:24	1.23
@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.21 1999/09/15 18:17:19 obrien Exp $
+     $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/linuxemu/chapter.sgml,v 1.23 1999/09/15 19:14:24 obrien Exp $
 -->
 
 <chapter id="linuxemu">
@@ -17,7 +17,7 @@
       The Linux compatibility in the 2.1-STABLE branch is capable of running Linux
       DOOM and Mathematica; the version present in &rel.current;-RELEASE is
       vastly more capable and runs all these as well as Oracle8,
-      WordPerfect, StarOffice, Acrobat, Quake, Abuse, IDL,
+      WordPerfect, StarOffice, Acrobat, Quake, Abuse, IDL, and
       netrek for Linux and a whole host of other programs.</para>
 	
     <para>There are some Linux-specific operating system features that are not
@@ -27,88 +27,14 @@
       i386-specific calls, such as enabling virtual 8086 mode.</para>
 	
     <para>Depending on which version of FreeBSD you are running, how you get
-      Linux-mode up will vary somewhat:</para>
+      Linux mode up will vary somewhat:</para>
 	
     <sect2>
-      <title>Installing Linux Mode in 2.1-STABLE</title>
-      
-      <para>The <filename>GENERIC</filename> kernel in 2.1-STABLE is not
-	configured for Linux compatibility so you must reconfigure your kernel
-	for it.  There are two ways to do this: 1.  linking the binary compatibility
-	statically in the kernel itself and 2.  configuring your kernel to
-	dynamically load the Linux loadable kernel module (LKM).</para>
-	  
-      <para>To enable Linux binary compatibility, add the following to your configuration
-	file (c.f. <filename>/sys/i386/conf/LINT</filename>):</para>
-
-      <programlisting>
-options COMPAT_LINUX</programlisting>
-
-      <para>If you want to run doom or other applications that need shared
-	memory, also add the following.</para>
-
-      <programlisting>
-options SYSVSHM</programlisting>
-
-      <para>The Linux system calls require 4.3BSD system call compatibility.
-	So make sure you have the following.</para>
-
-      <programlisting>
-options "COMPAT_43"</programlisting>
-	  
-      <para>If you prefer to statically link the binary compatibility in the kernel rather
-	than use the loadable kernel module (LKM), then add</para>
-
-      <programlisting>
-options  LINUX</programlisting>
-
-      <para>Then run <command>config</command> and install the new kernel as described in the
-	<link linkend="kernelconfig">kernel configuration</link>
-	section.</para>
-	  
-      <para>If you decide to use the LKM you must also install the loadable
-	module.  A mismatch of versions between the kernel and loadable module
-	can cause the kernel to crash, so the safest thing to do is to
-	reinstall the LKM when you install the kernel.</para>
-
-      <screen>&prompt.root; <userinput>cd /usr/src/lkm/linux</userinput>
-&prompt.root; <userinput>make all install</userinput></screen>
-	    
-      <para>Once you have installed the kernel and the LKM, you can invoke
-	<command>linux</command> as root to load the LKM.</para>
-	    
-      <screen>&prompt.root; <userinput>linux</userinput>
-Linux emulator installed
-Module loaded as ID 0</screen>
-	    
-      <para>To see whether the LKM is loaded, run
-	<command>modstat</command>.</para>
-	  
-      <screen>&prompt.user; modstat
-Type     Id Off Loadaddr Size Info     Rev
-Module Name EXEC      0   3 f0baf000 0018 f0bb4000   1 linux_emulator</screen>
-	    
-      <para>You can cause the LKM to be loaded when the system boots in either
-	of two ways.  In FreeBSD 2.2.1-RELEASE and 2.1-STABLE enable it in
-	<filename>/etc/sysconfig</filename>
-
-	<programlisting>
-linux=YES</programlisting>
-
-	by changing it from NO to YES.  FreeBSD 2.1 RELEASE and earlier do not
-	have such a line and on those you will need to edit
-	<filename>/etc/rc.local</filename> to add the following line.</para>
-      
-      <programlisting>
-linux</programlisting>
-    </sect2>
-    
-    <sect2>
-      <title>Installing Linux Mode in 2.2.2-RELEASE and later 2.2.x versions</title>
+      <title>Installing Linux Mode in 3.0-RELEASE and later</title>
       
       <para>It is no longer necessary to specify <literal>options
 	  LINUX</literal> or <literal>options COMPAT_LINUX</literal>.  Linux
-	binary compatibility is done with an LKM (&ldquo;Loadable Kernel Module&rdquo;)
+	binary compatibility is done with an KLD object (&ldquo;Kernel LoaDable object&rdquo;)
 	so it can be installed on the fly without having to reboot.  You will
 	need the following things in your startup files, however:</para>
       
@@ -126,38 +52,38 @@
 	    <filename>/etc/rc.i386</filename>:</para>
 	  
 	  <programlisting>
-# Start the Linux binary emulation if requested.
+# Start the Linux binary compatibility if requested.
 if [ "X${linux_enable}" = X"YES" ]; then echo -n '
         linux';               linux &gt; /dev/null 2&gt;&amp;1
 fi</programlisting>
 	</listitem>
       </orderedlist>
       
-      <para>If you want to verify that the LKM is running, modstat will do that:</para>
+      <para>If you want to verify that the KLD is loaded, <command>kldstat</command> will do that:</para>
 
-      <screen>&prompt.user; modstat
-Type     Id Off Loadaddr Size Info     Rev Module Name
-EXEC      0   4 f09e6000 001c f09ec010   1 linux_mod</screen>
+      <screen>&prompt.user; kldstat
+Id Refs Address    Size     Name
+ 1    2 0xc0100000 16bdb8   kernel
+ 7    1 0xc24db000 d000     linux.ko</screen>
       
-      <para>However, there have been reports that this fails on some
-	2.2-RELEASE and later systems.  If for some reason you cannot load the
-	Linux LKM, then statically link the Linux compatibility in the kernel by
+      <para>If for some reason you do not want to or cannot load the
+	Linux KLD, then statically link the binary compatibility in the kernel by
 	adding
 
 	<programlisting>
 options  LINUX</programlisting>
 
-	to your kernel config file.  Then run config and install the new
+	to your kernel config file.  Then run <command>config</command> and install the new
 	kernel as described in the <link linkend="kernelconfig">kernel
 	  configuration</link> section.</para>
     </sect2>
     
     <sect2>
-      <title>Installing Linux Mode in 3.0-RELEASE and later</title>
+      <title>Installing Linux Mode in 2.2.2-RELEASE and later 2.2.x versions</title>
       
       <para>It is no longer necessary to specify <literal>options
 	  LINUX</literal> or <literal>options COMPAT_LINUX</literal>.  Linux
-	binary compatibility is done with an KLD object (&ldquo;Kernel LoaDable object&rdquo;)
+	binary compatibility is done with an LKM (&ldquo;Loadable Kernel Module&rdquo;)
 	so it can be installed on the fly without having to reboot.  You will
 	need the following things in your startup files, however:</para>
       
@@ -175,31 +101,105 @@
 	    <filename>/etc/rc.i386</filename>:</para>
 	  
 	  <programlisting>
-# Start the Linux binary compatibility if requested.
+# Start the Linux binary emulation if requested.
 if [ "X${linux_enable}" = X"YES" ]; then echo -n '
         linux';               linux &gt; /dev/null 2&gt;&amp;1
 fi</programlisting>
 	</listitem>
       </orderedlist>
       
-      <para>If you want to verify that the KLD is loaded, kldstat will do that:</para>
+      <para>If you want to verify that the LKM is running, <command>modstat</command> will do that:</para>
 
-      <screen>&prompt.user; kldstat
-Id Refs Address    Size     Name
- 1    2 0xc0100000 16bdb8   kernel
- 7    1 0xc24db000 d000     linux.ko</screen>
+      <screen>&prompt.user; modstat
+Type     Id Off Loadaddr Size Info     Rev Module Name
+EXEC      0   4 f09e6000 001c f09ec010   1 linux_mod</screen>
       
-      <para>If for some reason you do not want to or cannot load the
-	Linux KLD, then statically link the binary compatibility in the kernel by
+      <para>However, there have been reports that this fails on some
+	2.2-RELEASE and later systems.  If for some reason you cannot load the
+	Linux LKM, then statically link the Linux compatibility in the kernel by
 	adding
 
 	<programlisting>
 options  LINUX</programlisting>
 
-	to your kernel config file.  Then run config and install the new
+	to your kernel config file.  Then run <command>config</command> and install the new
 	kernel as described in the <link linkend="kernelconfig">kernel
 	  configuration</link> section.</para>
     </sect2>
+
+    <sect2>
+      <title>Installing Linux Mode in 2.1-STABLE</title>
+      
+      <para>The <filename>GENERIC</filename> kernel in 2.1-STABLE is not
+	configured for Linux compatibility so you must reconfigure your kernel
+	for it.  There are two ways to do this: 1.  linking the binary compatibility
+	statically in the kernel itself and 2.  configuring your kernel to
+	dynamically load the Linux loadable kernel module (LKM).</para>
+	  
+      <para>To enable Linux binary compatibility, add the following to your configuration
+	file (c.f. <filename>/sys/i386/conf/LINT</filename>):</para>
+
+      <programlisting>
+options COMPAT_LINUX</programlisting>
+
+      <para>If you want to run doom or other applications that need shared
+	memory, also add the following.</para>
+
+      <programlisting>
+options SYSVSHM</programlisting>
+
+      <para>The Linux system calls require 4.3BSD system call compatibility.
+	So make sure you have the following.</para>
+
+      <programlisting>
+options "COMPAT_43"</programlisting>
+	  
+      <para>If you prefer to statically link the binary compatibility in the kernel rather
+	than use the loadable kernel module (LKM), then add</para>
+
+      <programlisting>
+options  LINUX</programlisting>
+
+      <para>Then run <command>config</command> and install the new kernel as described in the
+	<link linkend="kernelconfig">kernel configuration</link>
+	section.</para>
+	  
+      <para>If you decide to use the LKM you must also install the loadable
+	module.  A mismatch of versions between the kernel and loadable module
+	can cause the kernel to crash, so the safest thing to do is to
+	reinstall the LKM when you install the kernel.</para>
+
+      <screen>&prompt.root; <userinput>cd /usr/src/lkm/linux</userinput>
+&prompt.root; <userinput>make all install</userinput></screen>
+	    
+      <para>Once you have installed the kernel and the LKM, you can invoke
+	<command>linux</command> as root to load the LKM.</para>
+	    
+      <screen>&prompt.root; <userinput>linux</userinput>
+Linux emulator installed
+Module loaded as ID 0</screen>
+	    
+      <para>To see whether the LKM is loaded, run
+	<command>modstat</command>.</para>
+	  
+      <screen>&prompt.user; modstat
+Type     Id Off Loadaddr Size Info     Rev
+Module Name EXEC      0   3 f0baf000 0018 f0bb4000   1 linux_emulator</screen>
+	    
+      <para>You can cause the LKM to be loaded when the system boots in either
+	of two ways.  In FreeBSD 2.2.1-RELEASE and 2.1-STABLE enable it in
+	<filename>/etc/sysconfig</filename>
+
+	<programlisting>
+linux=YES</programlisting>
+
+	by changing it from <literal>NO</literal> to <literal>YES</literal>.  FreeBSD 2.1 RELEASE and earlier do not
+	have such a line and on those you will need to edit
+	<filename>/etc/rc.local</filename> to add the following line.</para>
+      
+      <programlisting>
+linux</programlisting>
+    </sect2>
     
     <sect2>
       <title>Installing Linux Runtime Libraries</title>
@@ -384,7 +384,7 @@
 	  <filename>/compat/linux/usr/X11/lib/libX11.so</filename>, etc.) in
 	  order for the Linux ABI loader to find them.</para>
 	    
-	<para>Those running FreeBSD 2.2-RELEASE should run the Linux ldconfig
+	<para>Those running FreeBSD 2.2-RELEASE should run the Linux <command>ldconfig</command>
 	  program.</para>
 	      
 	<screen>&prompt.root <userinput>cd /compat/linux/lib</userinput>
@@ -750,15 +750,15 @@
 	    
       <para>It will ask you to enter your license number and the Wolfram
 	supplied password.  If you get them mixed up or for some reason the
-	math.install fails, that is OK; you can simply edit the file
+	<command>math.install</command> fails, that is OK; you can simply edit the file
 	<filename>mathpass</filename> in this same directory to correct the
 	info manually.</para>
 	  
-      <para>After getting past the password, math.install will ask you if you
+      <para>After getting past the password, <command>math.install</command> will ask you if you
 	accept the install defaults provided, or if you want to use your own.
 	If you are like us and distrust all install programs, you probably
 	want to specify the actual directories.  Beware. Although the
-	math.install program asks you to specify directories, it will not
+	<command>math.install</command> program asks you to specify directories, it will not
 	create them for you, so you should perhaps have a second window open
 	with another shell so that you can create them before you give them to
 	the install program.  Or, if it fails, you can create the directories
@@ -799,7 +799,7 @@
 	execute the <command>xfe.install</command> shell script.  You will
 	have to tell it where to put things, but you do not have to create any
 	directories because it will use the same directories that had been
-	created for math.install.  When it finishes, there should be a new
+	created for <command>math.install</command>.  When it finishes, there should be a new
 	shell script in <filename>/usr/local/Mathematica/bin</filename> called
 	<filename>mathematica</filename>.</para>
 	  
@@ -819,8 +819,8 @@
       
       <screen>&prompt.user; <userinput>RESOLV_HOST_CONF=/compat/linux/etc/host.conf; export RESOLV_HOST_CONF</userinput></screen>
 	    
-      <para>This tells Mathematica to use the Linux version of host.conf.
-	This file has a different syntax from FreeBSD's host.conf, so you will
+      <para>This tells Mathematica to use the Linux version of <filename>host.conf</filename>.
+	This file has a different syntax from FreeBSD's <filename>host.conf</filename>, so you will
 	get an error message about <filename>/etc/host.conf</filename> if you
 	leave this out.</para>
 	  
@@ -847,7 +847,7 @@
 	    
       <para>We have not found the cause for this, but it only affects the
 	Notebook's X Window front end, not the mathematica engine itself. So
-	the command line interface invoked by 'math' is unaffected by this
+	the command line interface invoked by <command>math</command> is unaffected by this
 	bug.</para>
     </sect2>
     
@@ -891,8 +891,7 @@
     
     <para>Later, a hack was made for &man.sh.1; to examine the first two
       characters, and if they were <literal>:\n</literal>, then it invoked the
-      &man.csh.1; shell instead (I believe SCO first made this hack, but am
-      willing to be corrected).</para>
+      &man.csh.1; shell instead (we believe SCO first made this hack).</para>
                        
     <para>What FreeBSD does now is go through a list of loaders, with a
       generic <literal>#!</literal> loader that knows about interpreters as


$B$/$j$d$^(B // kuriyama@sky.rim.or.jp
        // kuriyama@FreeBSD.org
