From: Kay Sievers <kay.sievers@vrfy.org>
To: Karel Zak <kzak@redhat.com>
Cc: Attila Kinali <attila@kinali.ch>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: Re: /etc/fstab.d yes or not
Date: Fri, 20 Jan 2012 16:20:56 +0100 [thread overview]
Message-ID: <CAPXgP11f_SicmxSZ1Bb5JmM4krPyNL-rXNJ6rJ2BHrNvA8LzRQ@mail.gmail.com> (raw)
In-Reply-To: <20120120145907.GA20377@x2.net.home>
On Fri, Jan 20, 2012 at 15:59, Karel Zak <kzak@redhat.com> wrote:
> On Fri, Jan 20, 2012 at 03:43:09PM +0100, Attila Kinali wrote:
>> Hence, i would like to ask you to consider not adding /etc/fstab.d
>> unless there is a very good reason to do it. And "to make it simpler
>> for people who have a lot of mountpoints" is IMHO not a good reason.
>> How many mountpoints must one use that a single file becomes a problem?
>
> Let's imagine that you have a network and you use the same configuration
> on all machines, then "*.d/" directories are very useful for you -- for
> example you can create a company.rpm with important configuration and
> distribute it to all machines.
Yeah, and all tools which read /etc/fstab with the glibc interface, to
find out the properties for the mount point, are just broken now. And
for what gain. Put a script in you RPM that merges your snippets into
the one fstab, and you get the same behaviour without any breakage.
Always remember, /etc/fstab is ABI, not a private config file, you
need a _very_ good reason to break it.
And you usually have not much problems convincing me that breakage is
justified. I just totally fail to see the benefit vs. gain in this
case.
Kay
next prev parent reply other threads:[~2012-01-20 15:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 14:04 /etc/fstab.d yes or not Karel Zak
2012-01-20 14:20 ` Masatake YAMATO
2012-01-20 14:56 ` Kay Sievers
2012-01-20 15:57 ` Roger Leigh
2012-01-20 16:08 ` Kay Sievers
2012-01-24 0:19 ` Boaz Harrosh
2012-01-24 9:47 ` bastien ROUCARIES
2012-01-20 14:43 ` Attila Kinali
2012-01-20 14:59 ` Karel Zak
2012-01-20 15:03 ` Voelker, Bernhard
2012-01-20 15:20 ` Kay Sievers [this message]
2012-01-20 15:49 ` Roger Leigh
2012-01-20 16:13 ` Kay Sievers
2012-01-20 16:22 ` Roger Leigh
2012-01-20 17:59 ` Kay Sievers
2012-01-23 12:21 ` Karel Zak
2012-01-23 13:01 ` Masatake YAMATO
2012-01-23 13:03 ` Kay Sievers
2012-01-23 13:26 ` Masatake YAMATO
2012-01-23 13:37 ` Kay Sievers
2012-01-23 14:14 ` Masatake YAMATO
2012-01-23 14:32 ` Kay Sievers
2012-01-23 13:55 ` Theodore Tso
2012-01-23 22:07 ` Alan Cox
2012-01-24 1:06 ` Ted Ts'o
2012-01-20 18:20 ` Denys Vlasenko
2012-01-20 18:29 ` Kay Sievers
2012-01-20 18:47 ` Al Viro
2012-01-24 11:02 ` /etc/fstab.d yes or not (resolved) Karel Zak
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=CAPXgP11f_SicmxSZ1Bb5JmM4krPyNL-rXNJ6rJ2BHrNvA8LzRQ@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=attila@kinali.ch \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).