From: NeilBrown <neilb@suse.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Hou Tao <houtao1@huawei.com>,
linux-xfs@vger.kernel.org, david@fromorbit.com,
linux-fsdevel@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>,
Tso Ted <tytso@mit.edu>, Dmitri Pal <dpal@redhat.com>
Subject: Re: Filesystem configuration parsers - (was: Re: [RESEND][PATCH] xfs: add online uevent for mount operation)
Date: Fri, 25 Aug 2017 08:11:05 +1000 [thread overview]
Message-ID: <87a82ok45i.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20170824180441.GL27873@wotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 735 bytes --]
On Thu, Aug 24 2017, Luis R. Rodriguez wrote:
>
> Just saying, we better damn be sure this is the way we want to go.
>
Just to provide contrast, NFS has a config file which can provide
certain defaults for mounted filesystems. However it doesn't require a
udev event to achieve this.
Instead, it provides "/sbin/mount.nfs" which imposes the defaults at
mount time, rather than just after mount time.
There could, conceivably, be an "/sbin/mount.xfs" which read the config
file and set all the defaults concurrently with the mount operation.
I'm not necessarily saying this is a better way to go, but I agree with
the need to be sure, and this provides evidence that other approaches
are possible and worth considering.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-08-24 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1503582115-37220-1-git-send-email-houtao1@huawei.com>
[not found] ` <20170824171028.GF4796@magnolia>
2017-08-24 18:04 ` Filesystem configuration parsers - (was: Re: [RESEND][PATCH] xfs: add online uevent for mount operation) Luis R. Rodriguez
2017-08-24 18:13 ` Luis R. Rodriguez
2017-08-24 18:59 ` Luis R. Rodriguez
2017-08-24 22:11 ` NeilBrown [this message]
2017-08-24 22:39 ` Luis R. Rodriguez
2017-08-24 23:34 ` Theodore Ts'o
2017-08-25 0:02 ` Luis R. Rodriguez
2017-08-25 4:54 ` Darrick J. Wong
2017-08-25 1:01 ` Dave Chinner
2017-08-25 1:20 ` Luis R. Rodriguez
2017-08-25 2:18 ` Dave Chinner
2017-08-25 5:29 ` Darrick J. Wong
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=87a82ok45i.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dpal@redhat.com \
--cc=houtao1@huawei.com \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=tytso@mit.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).