From: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Attila Kinali <attila-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: /etc/fstab.d yes or not
Date: Fri, 20 Jan 2012 15:59:07 +0100 [thread overview]
Message-ID: <20120120145907.GA20377@x2.net.home> (raw)
In-Reply-To: <20120120154309.3ae5f9e4a8f55c477dc423ab-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org>
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.
Karel
--
Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-20 14:59 UTC|newest]
Thread overview: 22+ 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
[not found] ` <CAPXgP10uUpSQzX0RzYY24uDBkNkRXM7NbR0H6P=dZ=+LxdX3Fw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-24 0:19 ` Boaz Harrosh
[not found] ` <4F1DF90C.5070108-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2012-01-24 9:47 ` bastien ROUCARIES
2012-01-20 14:43 ` Attila Kinali
[not found] ` <20120120154309.3ae5f9e4a8f55c477dc423ab-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org>
2012-01-20 14:59 ` Karel Zak [this message]
2012-01-20 15:03 ` Voelker, Bernhard
[not found] ` <20120120145907.GA20377-s5vVilr7EKH/9pzu0YdTqQ@public.gmane.org>
2012-01-20 15:20 ` Kay Sievers
[not found] ` <20120120140444.GC13157-s5vVilr7EKH/9pzu0YdTqQ@public.gmane.org>
2012-01-20 15:49 ` Roger Leigh
2012-01-20 16:13 ` Kay Sievers
[not found] ` <CAPXgP13a9v+f1uNdpe-c+aApLfLpgn15b1-gZxRPd0wMvU=B-Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-20 16:22 ` Roger Leigh
[not found] ` <20120120162220.GN8797-l88Q8xmqi7wqcZcGjlUOXw@public.gmane.org>
2012-01-20 17:59 ` 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
[not found] ` <CAK1hOcNget=-MjeejiYGo5Vkigq9ey1o7sD2peO+tDGdk3TU9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=20120120145907.GA20377@x2.net.home \
--to=kzak-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=attila-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).