svn commit: r41175 - head/en_US.ISO8859-1/books/faq

Gavin Atkinson gavin at FreeBSD.org
Tue Mar 12 13:49:25 UTC 2013


Author: gavin
Date: Tue Mar 12 13:49:24 2013
New Revision: 41175
URL: http://svnweb.freebsd.org/changeset/doc/41175

Log:
  This, mostly in order:
   - Adds a trademark attribution for NetBSD
   - Makes the spelling of DragonFly BSD consistent
   - Mention x86-64 as a common non-FreeBSD name for the amd64 platform
   - Fix several grammar and spelling issues
   - Mention that SMP support is enabled in the default kernel
   - Mention the sysv modules are default, but also available as modules
   - Default to "xterm" not "cons25", note that <9 uses "cons25"
   - Move one paragraph around so that "This" refers to the correct thing
   - Replace a reference that still existed to UserConfig (!)
   - Remove reference to the defunct "mbone" ports category
   - Remove derogatory comment about Windows, untrue for ~13 years
  
  Reviewed by:	eadler

Modified:
  head/en_US.ISO8859-1/books/faq/book.xml

Modified: head/en_US.ISO8859-1/books/faq/book.xml
==============================================================================
--- head/en_US.ISO8859-1/books/faq/book.xml	Tue Mar 12 13:30:14 2013	(r41174)
+++ head/en_US.ISO8859-1/books/faq/book.xml	Tue Mar 12 13:49:24 2013	(r41175)
@@ -67,6 +67,7 @@
       &tm-attrib.linux;
       &tm-attrib.microsoft;
       &tm-attrib.mips;
+      &tm-attrib.netbsd;
       &tm-attrib.opengroup;
       &tm-attrib.oracle;
       &tm-attrib.sgi;
@@ -333,7 +334,7 @@
 	    </listitem>
 
 	    <listitem>
-	      <para>DragonFlyBSD is a fork of &os; 4.8 that has
+	      <para>DragonFly BSD is a fork of &os; 4.8 that has
 		since developed many interesting features of its own,
 		including the HAMMER file system and support for
 		user-mode <quote>vkernels</quote>.</para>
@@ -1126,7 +1127,9 @@
 
 	<answer>
 	  <para>&arch.amd64; is the term &os; uses for 64-bit
-	    compatible x86 architectures.  Most modern computers
+	    compatible x86 architectures, sometimes referred to
+	    as <quote>x86-64</quote> by other operating systems.
+	    Most modern computers
 	    should use &arch.amd64;.  Older hardware should use
 	    &arch.i386;.  If you are installing on a
 	    non-x86-compatible architecture select the platform
@@ -1695,7 +1698,7 @@
 	  <answer>
 	    <para>Yes.  &os; divides support into multiple tiers.
 	      Tier 1 architectures, such as i386 or amd64; are
-	      fully supported.  Tiers 2 and 3 are supported on a
+	      fully supported.  Tiers 2 and 3 are supported on an
 	      if-possible basis.  A full explanation of the tier
 	      system is available in the
 	      <ulink
@@ -1721,7 +1724,8 @@
 
 	    <para>&os; will take advantage of HyperThreading (HTT)
 	      support on &intel; CPUs that support this feature.  A kernel
-	      with the <literal>options SMP</literal> feature enabled
+	      with the <literal>options SMP</literal> option, enabled
+	      by default,
 	      will automatically detect the additional logical
 	      processors.</para>
 
@@ -3861,10 +3865,6 @@ C:\="DOS"</programlisting>
 	    <command>more</command> session, <command>du</command> and
 	    <command>df</command> will agree.</para>
 
-	  <para>Note that Soft Updates can delay the freeing of disk
-	    space; you might need to wait up to 30 seconds for the
-	    change to be visible!</para>
-
 	  <para>This situation is common on web servers.  Many people
 	    set up a &os; web server and forget to rotate the log files.
 	    The access log fills up <filename class="directory">/var</filename>.  The new
@@ -3873,6 +3873,10 @@ C:\="DOS"</programlisting>
 	    restarting the web server program would free the file,
 	    allowing the system to release the disk space.  To prevent
 	    this from happening, set up &man.newsyslog.8;.</para>
+
+	  <para>Note that Soft Updates can delay the freeing of disk
+	    space; you might need to wait up to 30 seconds for the
+	    change to be visible!</para>
 	</answer>
       </qandaentry>
 
@@ -4239,7 +4243,9 @@ C:\="DOS"</programlisting>
 
 	  <para>If you intend to use a full screen editor such as
 	    &man.vi.1; or &man.emacs.1;, you may also need to run
-	    <command>export TERM=cons25</command> so that these editors
+	    <command>export TERM=xterm</command> on &os; 9.0+, or
+	    <command>export TERM=cons25</command> on &os; 8.X
+	    so that these editors
 	    can load the correct data from the &man.termcap.5;
 	    database.</para>
 
@@ -4358,9 +4364,12 @@ C:\="DOS"</programlisting>
 	<answer>
 	  <para>Yes, &os; supports System V-style IPC, including shared
 	    memory, messages and semaphores, in the
-	    <filename>GENERIC</filename> kernel.  In a custom kernel,
-	    enable this support by adding the following lines to your
-	    kernel config.</para>
+	    <filename>GENERIC</filename> kernel.  With a custom kernel,
+	    support may be loaded with the <filename>sysvshm.ko</filename>,
+	    <filename>sysvsem.ko</filename> and <filename>
+	      sysvmsg.ko</filename> kernel modules, or
+	    enabled in the custom kernel by adding the following lines to your
+	    kernel config:</para>
 
 	  <programlisting>options    SYSVSHM          # enable shared memory
 options    SYSVSEM          # enable for semaphores
@@ -5160,10 +5169,10 @@ EndSection</programlisting>
 
 	  <programlisting># Edit the existing entry for ttyv8 in /etc/ttys and change
 # "off" to "on".
-ttyv8   "/usr/libexec/getty Pc"         cons25  on secure
-ttyv9   "/usr/libexec/getty Pc"         cons25  on secure
-ttyva   "/usr/libexec/getty Pc"         cons25  on secure
-ttyvb   "/usr/libexec/getty Pc"         cons25  on secure</programlisting>
+ttyv8   "/usr/libexec/getty Pc"         xterm  on secure
+ttyv9   "/usr/libexec/getty Pc"         xterm  on secure
+ttyva   "/usr/libexec/getty Pc"         xterm  on secure
+ttyvb   "/usr/libexec/getty Pc"         xterm  on secure</programlisting>
 
 	  <para>Use as many or as few as you want.  The more virtual
 	    terminals you have, the more resources that are used; this
@@ -5171,6 +5180,14 @@ ttyvb   "/usr/libexec/getty Pc"         
 	    also want to change the <literal>secure</literal> to
 	    <literal>insecure</literal>.</para>
 
+	  <note>
+	    <para>Versions of &os; prior to 9.0 used the <quote>
+		cons25</quote> terminal type, and not <quote>
+		xterm</quote>.  Existing entries in
+	      <filename>/etc/ttys</filename> can be used on which to
+	      base new additions.</para> 
+	  </note>
+
 	  <important>
 	    <para>If you want to run an X server you
 	      <emphasis>must</emphasis> leave at least one virtual
@@ -5186,18 +5203,18 @@ ttyvb   "/usr/libexec/getty Pc"         
 	    allocation mentioned above and you wanted to run X, you
 	    would change settings for virtual terminal 12 from:</para>
 
-	  <programlisting>ttyvb   "/usr/libexec/getty Pc"         cons25  on  secure</programlisting>
+	  <programlisting>ttyvb   "/usr/libexec/getty Pc"         xterm  on  secure</programlisting>
 
 	  <para>to:</para>
 
-	  <programlisting>ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
+	  <programlisting>ttyvb   "/usr/libexec/getty Pc"         xterm  off secure</programlisting>
 
 	  <para>If your keyboard has only ten function keys, you would
 	    end up with:</para>
 
-	  <programlisting>ttyv9   "/usr/libexec/getty Pc"         cons25  off secure
-ttyva   "/usr/libexec/getty Pc"         cons25  off secure
-ttyvb   "/usr/libexec/getty Pc"         cons25  off secure</programlisting>
+	  <programlisting>ttyv9   "/usr/libexec/getty Pc"         xterm  off secure
+ttyva   "/usr/libexec/getty Pc"         xterm  off secure
+ttyvb   "/usr/libexec/getty Pc"         xterm  off secure</programlisting>
 
 	  <para>(You could also just delete these lines.)</para>
 
@@ -5349,17 +5366,9 @@ ttyvb   "/usr/libexec/getty Pc"         
 
 	  <para>If this happens, disable the synchronization check code
 	    by setting the driver flags for the PS/2 mouse driver to
-	    <literal>0x100</literal>.  Enter
-	    <emphasis>UserConfig</emphasis> by giving the
-	    <option>-c</option> option at the boot prompt:</para>
-
-	  <screen>boot: <userinput>-c</userinput></screen>
-
-	  <para>Then, in the <emphasis>UserConfig</emphasis> command
-	    line, type:</para>
-
-	  <screen>UserConfig> <userinput>flags psm0 0x100</userinput>
-UserConfig> <userinput>quit</userinput></screen>
+	    <literal>0x100</literal>.  This can be easiest achieved
+	    by adding <screen>hint.psm.0.flags="0x100"</screen> to
+	    <filename>/boot/loader.conf</filename> and rebooting.</para>
 	</answer>
       </qandaentry>
 
@@ -5718,13 +5727,6 @@ Key F15        A        A        Menu Wo
 	      programs are now available in the &os; Ports Collection as
 	      <filename role="package">net/mrouted</filename>.</para>
 	  </note>
-
-	  <para>MBONE tools are available in their own ports category,
-	    <ulink
-	      url="http://www.FreeBSD.org/ports/mbone.html">mbone</ulink>.
-	    If you are looking for the conference tools
-	    <command>vic</command> and <command>vat</command>, look
-	    there!</para>
 	</answer>
       </qandaentry>
 
@@ -6038,9 +6040,7 @@ Key F15        A        A        Menu Wo
 
 	  <para>Every &unix; process is completely firewalled off from
 	    every other &unix; process.  One process cannot modify the
-	    address space of another.  This is unlike &windows; where a
-	    process can easily overwrite the address space of any other,
-	    leading to a crash.</para>
+	    address space of another.</para>
 
 	  <para>A &unix; process is owned by a particular userid.  If
 	    the user ID is not the <username>root</username> user,
@@ -6134,7 +6134,7 @@ Key F15        A        A        Menu Wo
 	      search the archives <ulink
 		url="&url.base;/search/index.html">here</ulink> for an
 	      extensive discussion.  A more fine-grained mechanism
-	      is preffered.</para>
+	      is preferred.</para>
 	  </warning>
 	</answer>
       </qandaentry>


More information about the svn-doc-all mailing list