Date: Sun, 24 Nov 2013 19:02:23 +0000 (UTC) From: Benedict Reuschling <bcr@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43235 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs Message-ID: <201311241902.rAOJ2Npp005770@svn.freebsd.org>
index | next in thread | raw e-mail
Author: bcr Date: Sun Nov 24 19:02:22 2013 New Revision: 43235 URL: http://svnweb.freebsd.org/changeset/doc/43235 Log: Correct some sentences (typos, wrong words). Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 18:59:24 2013 (r43234) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 19:02:22 2013 (r43235) @@ -893,7 +893,7 @@ data 288G 1.53T <sect2 xml:id="zfs-zfs-volume"> <title>Creating & Destroying Volumes</title> - <para>A volume is special type of <acronym>ZFS</acronym> + <para>A volume is a special type of <acronym>ZFS</acronym> dataset. Rather than being mounted as a file system, it is exposed as a block device under <filename>/dev/zvol/<replaceable>poolname</replaceable>/<replaceable>dataset</replaceable></filename>. @@ -924,7 +924,7 @@ Filesystem Size Used Avail Cap <para>Destroying a volume is much the same as destroying a regular filesystem dataset. The operation is nearly - instantaneous, but it make take several minutes for the free + instantaneous, but it may take several minutes for the free space to be reclaimed in the background.</para> </sect2> @@ -1054,7 +1054,7 @@ tank custom:costcenter - <para><link linkend="zfs-term-quota">Dataset quotas</link> can be used to restrict the amount of space - that can be consumed by a peticular dataset. <link + that can be consumed by a particular dataset. <link linkend="zfs-term-refquota">Reference Quotas</link> work in very much the same way, except they only count the space used by the dataset it self, excluding snapshots and child @@ -1329,17 +1329,17 @@ dedup = 1.05, compress = 1.11, copies = <title>Delegated Administration</title> <para>ZFS features a comprehensive delegation system to assign - permissions to performs the various ZFS administration functions - to a regular user. For example, if each users' home directory - is a dataset, then each user could be delegated permission to - create and destroy snapshots of their home directory. A backup - user could be assigned the permissions required to make use of - the ZFS replication features without requiring root access, or - isolate a usage collection script to run as an unprivledged user - with access to only the space utilization data of all users. It - is even possible to delegate the ability to delegate - permissions. It is possible to delegate permissions over each - ZFS subcommand and most ZFS properties.</para> + permissions to perform the various ZFS administration functions + to a regular (non-root) user. For example, if each users' home + directory is a dataset, then each user could be delegated + permission to create and destroy snapshots of their home + directory. A backup user could be assigned the permissions + required to make use of the ZFS replication features without + requiring root access, or isolate a usage collection script to + run as an unprivileged user with access to only the space + utilization data of all users. It is even possible to delegate + the ability to delegate permissions. ZFS allows to delegate + permissions over each subcommand and most ZFS properties.</para> <sect2 xml:id="zfs-zfs-allow-create"> <title>Delegating Dataset Creation</title> @@ -1349,12 +1349,12 @@ dedup = 1.05, compress = 1.11, copies = <replaceable>mydataset</replaceable></userinput> command will give the indicated user the required permissions to create child datasets under the selected parent dataset. There is a - caveat, creating a new dataset involves mouting it, which - requires the <literal>vfs.usermount</literal> sysctl be + caveat: creating a new dataset involves mounting it, which + requires the <literal>vfs.usermount</literal> sysctl to be enabled in order to allow non-root users to mount a - filesystem. There is the further restriction that non-root - users must own the directory they are mounting the filesystem - to, in order to prevent abuse.</para> + filesystem. There is another restriction that non-root users + must own the directory they are mounting the filesystem to, in + order to prevent abuse.</para> </sect2> <sect2 xml:id="zfs-zfs-allow-allow">help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201311241902.rAOJ2Npp005770>