From: Masatake YAMATO <yamato@redhat.com>
To: rees@umich.edu
Cc: SteveD@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Read /etc/exports.d/*.export as extra export files
Date: Sun, 06 Mar 2011 15:11:23 +0900 (JST) [thread overview]
Message-ID: <20110306.151123.1031846434411534102.yamato@redhat.com> (raw)
In-Reply-To: <20110306015106.GA23388@merit.edu>
On Sat, 5 Mar 2011 20:51:06 -0500, Jim Rees <rees@umich.edu> wrote
> Steve Dickson wrote:
>
> Now, I realize you added the ".export" explanation to the man page
> but is there a particular reason why file in that directory have
> to end with ".export"? Out of "easy of use" sake, should any
> and all files that exist in that directory be expected to
> be exports files?
>
> I don't know if that's the best way to do it, but I think it would be useful
> to have a way to keep files in the directory that don't get automatically
> read. As an analogy, I have the following files in my /etc/init:
>
> portmap.conf This is the real one that gets used
> portmap.conf~ This is a backup file produced by emacs
> portmap.conf-20100603 This is the file that came with my distro
>
> Only the first one gets used, which is what I want, because it's the only
> one ending in ".conf".
Jim, thank you for explanation. He wrote what I'd like to write.
This technique is borrowed from util-linux-ng; libmount.so reads
only *.fstab under /etc/fstab.d.
In addition, ".export" suffix tells an editor which syntax highlighter
should be used when editing .export file:P
Masatake YAMATO
next prev parent reply other threads:[~2011-03-06 6:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 12:59 [PATCH 1/2] Read /etc/exports.d/*.export as extra export files Masatake YAMATO
2011-02-17 13:03 ` [PATCH 2/2] Update man pages for /etc/exports.d Masatake YAMATO
2011-03-03 14:01 ` [PATCH 1/2] Read /etc/exports.d/*.export as extra export files Masatake YAMATO
2011-03-03 15:26 ` Ferenc Wagner
[not found] ` <87fwr4rzri.fsf-/U8DR9OPLL8grVaPS+uXcA@public.gmane.org>
2011-03-03 17:50 ` J. Bruce Fields
2011-03-03 20:52 ` Steve Dickson
2011-03-04 6:10 ` Masatake YAMATO
2011-03-04 16:21 ` Steve Dickson
2011-03-05 16:54 ` Masatake YAMATO
2011-03-05 21:42 ` Steve Dickson
2011-03-05 22:46 ` Steve Dickson
2011-03-06 1:51 ` Jim Rees
2011-03-06 6:11 ` Masatake YAMATO [this message]
2011-03-07 13:05 ` Steve Dickson
2011-03-07 13:17 ` Steve Dickson
2011-03-07 13:50 ` Masatake YAMATO
2011-03-07 14:14 ` Steve Dickson
[not found] ` <4D74E830.6020406-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2011-03-07 14:27 ` Masatake YAMATO
2011-03-07 14:02 ` Jim Rees
2011-03-07 14:17 ` Steve Dickson
2011-03-07 14:29 ` Steve Dickson
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=20110306.151123.1031846434411534102.yamato@redhat.com \
--to=yamato@redhat.com \
--cc=SteveD@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).