From owner-svn-doc-head@FreeBSD.ORG Fri Apr 25 17:52:12 2014 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D84F629; Fri, 25 Apr 2014 17:52:12 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D55812B9; Fri, 25 Apr 2014 17:52:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3PHqCQO057097; Fri, 25 Apr 2014 17:52:12 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3PHqCYw057096; Fri, 25 Apr 2014 17:52:12 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201404251752.s3PHqCYw057096@svn.freebsd.org> From: Dru Lavigne Date: Fri, 25 Apr 2014 17:52:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44665 - head/en_US.ISO8859-1/books/handbook/geom X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Apr 2014 17:52:12 -0000 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)) - <acronym>GEOM</acronym> Gate Network Devices + <acronym>GEOM</acronym> Gate Network - GEOM supports the remote use of devices, - such as disks, CD-ROMs, and files through the use of the gate - utilities. This is similar to NFS. - - 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 SCSI disk, the - following /etc/gg.exports is more than - adequate: - - 192.168.1.0/24 RW /dev/da0s4d - - This allows all hosts inside the specified private network - access to the file system on the da0s4d - partition. + GEOM provides a simple mechanism for + providing remote access to devices such as disks, + CDs, and file systems through the use + of the GEOM Gate network daemon, + ggated. The system with the device + runs the server daemon which handles requests made by clients + using ggatec. The devices should not + contain any sensitive data as the connection between the client + and the server is not encrypted. + + Similar to NFS, which is discussed in + , ggated + 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 192.168.1.5 read and write + access to the fourth slice on the first SCSI + disk, create /etc/gg.exports with this + line: - To export this device, ensure it is not currently mounted, - and start the &man.ggated.8; server daemon: + 192.168.1.5 RW /dev/da0s4d - &prompt.root; ggated + Before exporting the device, ensure it is not currently mounted. + Then, start ggated: - To mount the device on the client - machine, issue the following commands: + &prompt.root; ggated + + 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. + + To access the exported device on the client + machine, first use ggatec to specify the + IP address of the server and the device name + of the exported device. If successful, this command will display + a ggate device name to mount. Mount that + specified device name on a free mount point. This example + connects to the /dev/da0s4d partition on + 192.168.1.1, then mounts + /dev/ggate0 on /mnt: &prompt.root; ggatec create -o rw 192.168.1.1 /dev/da0s4d ggate0 &prompt.root; mount /dev/ggate0 /mnt - The device may now be accessed through the - /mnt mount point. + The device on the server may now be accessed through + /mnt on the client. For more + details about ggatec and a few usage + examples, refer to &man.ggatec.8;. - However, this will fail if the device is currently mounted - on either the server machine or any other machine on the - network. + 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 NFS instead. When the device is no longer needed, unmount it with - &man.umount.8;, similar to any other disk device. + umount so that the resource is available to + other clients.