All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org, chuck.lever@oracle.com,
	bfields@fieldses.org, sweet_f_a@gmx.de
Subject: Re: [PATCH] manpage: add info about IPv6 configuration to exports(5) (try #3)
Date: Wed, 22 Jun 2011 18:37:15 -0400	[thread overview]
Message-ID: <4E026E9B.8050107@RedHat.com> (raw)
In-Reply-To: <1308676284-20731-1-git-send-email-jlayton@redhat.com>



On 06/21/2011 01:11 PM, Jeff Layton wrote:
> The parts of the exports(5) manpage that discuss IP addressing neglect
> IPv6 configuration. Update to include info on how to export to IPv6
> subnets and addresses, and add a line demonstrating that to the EXAMPLE
> section.
> 
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
>  utils/exportfs/exports.man |   11 +++++++----
>  1 files changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/utils/exportfs/exports.man b/utils/exportfs/exports.man
> index 241b3af..8e6f880 100644
> --- a/utils/exportfs/exports.man
> +++ b/utils/exportfs/exports.man
> @@ -47,7 +47,7 @@ NFS clients may be specified in a number of ways:
>  .IP "single host
>  This is the most common format. You may specify a host either by an
>  abbreviated name recognized be the resolver, the fully qualified domain
> -name, or an IP address.
> +name, an IPv4 address, or an IPv6 address.
>  .IP "IP networks
>  You can also export directories to all hosts on an IP (sub-) network
>  simultaneously. This is done by specifying an IP address and netmask pair
> @@ -56,8 +56,9 @@ as
>  where the netmask can be specified in dotted-decimal format, or as a
>  contiguous mask length.
>  For example, either `/255.255.252.0' or `/22' appended
> -to the network base IPv4 address results in identical subnetworks with 10 bits of
> -host. Wildcard characters generally do not work on IP addresses, though they
> +to the network base IPv4 address results in identical subnetworks with 10 bits
> +of host. IPv6 addresses must use a contiguous mask length. Wildcard characters
> +generally do not work on IP addresses, though they
>  may work by accident when reverse DNS lookups fail.
>  .IP "wildcards
>  Machine names may contain the wildcard characters \fI*\fR and \fI?\fR.
> @@ -486,6 +487,7 @@ The format for extra export tables is the same as
>  /home/joe       pc001(rw,all_squash,anonuid=150,anongid=100)
>  /pub            *(ro,insecure,all_squash)
>  /srv/www        \-sync,rw server @trusted @external(ro)
> +/foo            2001:db8:9:e54::/64(rw) 192.0.2.0/24(rw)
>  '''/pub/private    (noaccess)
>  .fi
>  .PP
> @@ -501,7 +503,8 @@ option in this entry also allows clients with NFS implementations that
>  don't use a reserved port for NFS.
>  The sixth line exports a directory read-write to the machine 'server'
>  as well as the `@trusted' netgroup, and read-only to netgroup `@external',
> -all three mounts with the `sync' option enabled.
> +all three mounts with the `sync' option enabled. The seventh line exports
> +a directory to both an IPv6 and an IPv4 subnet.
>  ''' The last line denies all NFS clients
>  '''access to the private directory.
>  '''.SH CAVEATS
Committed...

steved.

      reply	other threads:[~2011-06-22 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21 17:11 [PATCH] manpage: add info about IPv6 configuration to exports(5) (try #3) Jeff Layton
2011-06-22 22:37 ` Steve Dickson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E026E9B.8050107@RedHat.com \
    --to=steved@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sweet_f_a@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.