svn commit: r44665 - head/en_US.ISO8859-1/books/handbook/geom

[Dru Lavigne]

Author: dru
Date: Fri Apr 25 17:52:12 2014
New Revision: 44665
URL: http://svnweb.freebsd.org/changeset/doc/44665

Log:
  Editorial review of ggate chapter.
  
  Sponsored by:	iXsystems

Modified:
  head/en_US.ISO8859-1/books/handbook/geom/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/geom/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/geom/chapter.xml	Fri Apr 25 16:10:58 2014	(r44664)
+++ head/en_US.ISO8859-1/books/handbook/geom/chapter.xml	Fri Apr 25 17:52:12 2014	(r44665)
@@ -1330,48 +1330,69 @@ raid/r0  OPTIMAL  ada0 (ACTIVE (ACTIVE))
   </sect1>
 
   <sect1 xml:id="geom-ggate">
-    <title><acronym>GEOM</acronym> Gate Network Devices</title>
+    <title><acronym>GEOM</acronym> Gate Network</title>
 
-    <para><acronym>GEOM</acronym> supports the remote use of devices,
-      such as disks, CD-ROMs, and files through the use of the gate
-      utilities.  This is similar to <acronym>NFS</acronym>.</para>
-
-    <para>To begin, an exports file must be created.  This file
-      specifies who is permitted to access the exported resources and
-      what level of access they are offered.  For example, to export
-      the fourth slice on the first <acronym>SCSI</acronym> disk, the
-      following <filename>/etc/gg.exports</filename> is more than
-      adequate:</para>
-
-    <programlisting>192.168.1.0/24 RW /dev/da0s4d</programlisting>
-
-    <para>This allows all hosts inside the specified private network
-      access to the file system on the <filename>da0s4d</filename>
-      partition.</para>
+    <para><acronym>GEOM</acronym> provides a simple mechanism for
+      providing remote access to devices such as disks,
+      <acronym>CD</acronym>s, and file systems through the use
+      of the <acronym>GEOM</acronym> Gate network daemon,
+      <application>ggated</application>.  The system with the device
+      runs the server daemon which handles requests made by clients
+      using <application>ggatec</application>.  The devices should not
+      contain any sensitive data as the connection between the client
+      and the server is not encrypted.</para>
+
+    <para>Similar to <acronym>NFS</acronym>, which is discussed in
+      <xref linkend="network-nfs"/>, <application>ggated</application>
+      is configured using an exports file.  This file
+      specifies which systems are permitted to access the exported resources and
+      what level of access they are offered.  For example, to give
+      the client <systemitem
+	class="ipaddress">192.168.1.5</systemitem> read and write
+      access to the fourth slice on the first <acronym>SCSI</acronym>
+      disk, create <filename>/etc/gg.exports</filename> with this
+      line:</para>
 
-    <para>To export this device, ensure it is not currently mounted,
-      and start the &man.ggated.8; server daemon:</para>
+    <programlisting>192.168.1.5 RW /dev/da0s4d</programlisting>
 
-    <screen>&prompt.root; <userinput>ggated</userinput></screen>
+    <para>Before exporting the device, ensure it is not currently mounted.
+      Then, start <application>ggated</application>:</para>
 
-    <para>To <command>mount</command> the device on the client
-      machine, issue the following commands:</para>
+    <screen>&prompt.root; <userinput>ggated</userinput></screen>
+    
+    <para>Several options are available for specifying an alternate
+      listening port or changing the default location of the exports
+      file.  Refer to &man.ggated.8; for details.</para>
+
+    <para>To access the exported device on the client
+      machine, first use <command>ggatec</command> to specify the
+      <acronym>IP</acronym> address of the server and the device name
+      of the exported device.  If successful, this command will display
+      a <literal>ggate</literal> device name to mount.  Mount that
+      specified device name on a free mount point.  This example
+      connects to the <filename>/dev/da0s4d</filename> partition on
+      <literal>192.168.1.1</literal>, then mounts
+      <filename>/dev/ggate0</filename> on <filename>/mnt</filename>:</para>
 
     <screen>&prompt.root; <userinput>ggatec create -o rw 192.168.1.1 /dev/da0s4d</userinput>
 ggate0
 &prompt.root; <userinput>mount /dev/ggate0 /mnt</userinput></screen>
 
-    <para>The device may now be accessed through the
-      <filename>/mnt</filename> mount point.</para>
+    <para>The device on the server may now be accessed through
+      <filename>/mnt</filename> on the client.  For more
+      details about <command>ggatec</command> and a few usage
+      examples, refer to &man.ggatec.8;.</para>
 
     <note>
-      <para>However, this will fail if the device is currently mounted
-	on either the server machine or any other machine on the
-	network.</para>
+      <para>The mount will fail if the device is currently mounted
+	on either the server or any other client on the
+	network.  If simultaneous access is needed to network
+	resources, use <acronym>NFS</acronym> instead.</para>
     </note>
 
     <para>When the device is no longer needed, unmount it with
-      &man.umount.8;, similar to any other disk device.</para>
+      <command>umount</command> so that the resource is available to
+      other clients.</para>
   </sect1>
 
   <sect1 xml:id="geom-glabel">