From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <steved@redhat.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] configure.ac: Added server 4.1 support configuration option
Date: Sat, 17 Sep 2011 14:36:45 -0400 [thread overview]
Message-ID: <20110917183645.GA24278@fieldses.org> (raw)
In-Reply-To: <1316272622-4894-1-git-send-email-steved@redhat.com>
On Sat, Sep 17, 2011 at 11:17:01AM -0400, Steve Dickson wrote:
> Separate the v4.1 support in the client and server
> by creating the --enable-nfsdv4 configuration option.
I really dislike --enable-nfsdv4: people shouldn't have to rebuild
nfs-utils in order to turn on server 4.1 support. They should be able
to do that at run time.
It makes sense for something like the block client, because there we
actually have to decide whether to *build* something or not, and if
someone knows they're never going to use that daemon, maybe they don't
want to bother building and installing it.
For server 4.1 support, we're making them rebuild just to change the
value of a single constant. Why?
--b.
>
> Signed-off-by: Steve Dickson <steved@redhat.com>
> ---
> configure.ac | 19 ++++++++++++++++---
> support/include/nfs/nfs.h | 2 +-
> 2 files changed, 17 insertions(+), 4 deletions(-)
>
> diff --git a/configure.ac b/configure.ac
> index 1a28f8a..18a735d 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -75,17 +75,30 @@ AC_ARG_ENABLE(nfsv4,
>
> AC_ARG_ENABLE(nfsv41,
> [AC_HELP_STRING([--enable-nfsv41],
> - [enable support for NFSv41 @<:@default=no@:>@])],
> + [enable for NFS v4.1 client support @<:@default=yes@:>@])],
> enable_nfsv41=$enableval,
> - enable_nfsv41=no)
> + enable_nfsv41=yes)
> if test "$enable_nfsv41" = yes; then
> - AC_DEFINE(NFS41_SUPPORTED, 1, [Define this if you want NFSv41 support compiled in])
> + AC_DEFINE(NFS41_SUPPORTED, 1, [Define this if you want NFSv4.1 client support compiled in])
> else
> enable_nfsv41=
> fi
> AC_SUBST(enable_nfsv41)
> AM_CONDITIONAL(CONFIG_NFSV41, [test "$enable_nfsv41" = "yes"])
>
> +AC_ARG_ENABLE(nfsvd41,
> + [AC_HELP_STRING([--enable-nfsdv41],
> + [enable for NFS v4.1 server support @<:@default=no@:>@])],
> + enable_nfsdv41=$enableval,
> + enable_nfsvd41=no)
> + if test "$enable_nfsdv41" = yes; then
> + AC_DEFINE(NFSD41_SUPPORTED, 1, [Define this if you want NFSv4.1 server support compiled in])
> + else
> + enable_nfsdv41=
> + fi
> + AC_SUBST(enable_nfsdv41)
> + AM_CONDITIONAL(CONFIG_NFSDV41, [test "$enable_nfsdv41" = "yes"])
> +
> AC_ARG_ENABLE(gss,
> [AC_HELP_STRING([--enable-gss],
> [enable support for rpcsec_gss @<:@default=yes@:>@])],
> diff --git a/support/include/nfs/nfs.h b/support/include/nfs/nfs.h
> index c939d78..d06ac1f 100644
> --- a/support/include/nfs/nfs.h
> +++ b/support/include/nfs/nfs.h
> @@ -16,7 +16,7 @@
> #define NFSD_MAXVERS 4
>
> #define NFSD_MINMINORVERS4 1
> -#ifdef NFS41_SUPPORTED
> +#ifdef NFSD41_SUPPORTED
> #define NFSD_MAXMINORVERS4 1
> #else
> #define NFSD_MAXMINORVERS4 0
> --
> 1.7.6
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-17 18:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 15:17 [PATCH 1/2] configure.ac: Added server 4.1 support configuration option Steve Dickson
2011-09-17 15:17 ` [PATCH 2/2] configure.ac: Remove unused NFS3_SUPPORTED define Steve Dickson
2011-09-17 18:36 ` J. Bruce Fields [this message]
2011-09-19 9:51 ` [PATCH 1/2] configure.ac: Added server 4.1 support configuration option Steve Dickson
2011-09-19 13:38 ` J. Bruce Fields
2011-09-19 14:20 ` Steve Dickson
2011-09-19 14:35 ` J. Bruce Fields
2011-09-19 15:16 ` Steve Dickson
2011-09-19 15:27 ` J. Bruce Fields
2011-09-19 18:15 ` J. Bruce Fields
2011-09-20 11:43 ` Steve Dickson
[not found] ` <4E787C6E.8080104-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2011-09-20 11:47 ` J. Bruce Fields
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=20110917183645.GA24278@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).