From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] nfs-export-root: add explict no_subtree-check to suppress warning
Date: Sun, 7 Oct 2012 18:07:11 -0700 [thread overview]
Message-ID: <1349658431-18779-1-git-send-email-sgw@linux.intel.com> (raw)
exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
.../devel-config/nfs-export-root.bb | 2 ++
.../devel-config/nfs-export-root/exports | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/devel-config/nfs-export-root.bb b/meta/recipes-devtools/devel-config/nfs-export-root.bb
index 41259ac..fff60ca 100644
--- a/meta/recipes-devtools/devel-config/nfs-export-root.bb
+++ b/meta/recipes-devtools/devel-config/nfs-export-root.bb
@@ -3,6 +3,8 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+PR = "r1"
+
SRC_URI = "file://exports"
S = "${WORKDIR}"
diff --git a/meta/recipes-devtools/devel-config/nfs-export-root/exports b/meta/recipes-devtools/devel-config/nfs-export-root/exports
index b7257aa..1353c5a 100644
--- a/meta/recipes-devtools/devel-config/nfs-export-root/exports
+++ b/meta/recipes-devtools/devel-config/nfs-export-root/exports
@@ -1 +1 @@
-/ *(rw,no_root_squash,async)
+/ *(rw,no_root_squash,async,no_subtree_check)
--
1.7.9.5
reply other threads:[~2012-10-08 1:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1349658431-18779-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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