From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH v2 09/10] nfsutils: adapt package's '/var/lib' requirements
Date: Fri, 28 Jun 2019 09:43:42 +0200 [thread overview]
Message-ID: <20190628074343.6700-10-jbe@pengutronix.de> (raw)
In-Reply-To: <20190628074343.6700-2-jbe@pengutronix.de>
Signed-off-by: Juergen Borleis <jbe@pengutronix.de>
---
rules/nfsutils.in | 5 ++++-
rules/nfsutils.make | 2 +-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/rules/nfsutils.in b/rules/nfsutils.in
index bd1052ebb..ef7eb7b98 100644
--- a/rules/nfsutils.in
+++ b/rules/nfsutils.in
@@ -9,11 +9,14 @@ menuconfig NFSUTILS
select RPCBIND if RUNTIME
select LIBTIRPC if GLOBAL_IPV6
select ROOTFS_PROTOCOLS if NFSUTILS_CLIENT
+ select ROOTFS_VAR_LIB if RUNTIME
help
The Sun Network Filesystem (NFS) protocol provides transparent remote
access to shared files across networks. The NFS protocol is designed
to be portable across different machines, operating systems, network
architectures, and transport protocols.
+ Note: this package expects write permissions to '/var/lib/nfs' for
+ its state information.
if NFSUTILS
@@ -27,7 +30,7 @@ config NFSUTILS_SERVER
bool
prompt "server"
help
- Install all tools and daemons to run a NFS server.
+ Install all tools and daemons to run an NFS server.
config NFSUTILS_NFSD_STARTSCRIPT
bool
diff --git a/rules/nfsutils.make b/rules/nfsutils.make
index 929f53c72..4ce01c4e3 100644
--- a/rules/nfsutils.make
+++ b/rules/nfsutils.make
@@ -76,7 +76,7 @@ $(STATEDIR)/nfsutils.targetinstall:
@$(call install_fixup, nfsutils,PRIORITY,optional)
@$(call install_fixup, nfsutils,SECTION,base)
@$(call install_fixup, nfsutils,AUTHOR,"Robert Schwebel <r.schwebel@pengutronix.de>")
- @$(call install_fixup, nfsutils,DESCRIPTION,missing)
+ @$(call install_fixup, nfsutils,DESCRIPTION,"Network Filesystem Support")
@$(call install_copy, nfsutils, 0, 0, 0755, -, /usr/sbin/nfsstat)
@$(call install_copy, nfsutils, 0, 0, 0755, -, /usr/sbin/nfsiostat)
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-06-28 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 7:43 [ptxdist] [PATCH v2 01/10] rootfs: keep /var writable, even if the rootfs is read-only Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 02/10] conman: adapt package's '/var/lib' requirements Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 03/10] networkmanager: " Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 04/10] ntp: adapt package's '/var/lib' and '/var/log' requirements Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 05/10] dnsmasq: adapt package's '/var/lib' requirements Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 06/10] mariadb: " Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 07/10] samba: adapt package's '/var/lib' and '/var/cache' requirements Juergen Borleis
2019-06-28 7:43 ` [ptxdist] [PATCH v2 08/10] samba: show SysV related menue on demand only Juergen Borleis
2019-06-28 7:43 ` Juergen Borleis [this message]
2019-06-28 7:43 ` [ptxdist] [PATCH v2 10/10] logrotate: adapt package's '/var/lib' requirements Juergen Borleis
2019-06-28 7:46 ` [ptxdist] [PATCH v2 01/10] rootfs: keep /var writable, even if the rootfs is read-only Juergen Borleis
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=20190628074343.6700-10-jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox