[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7856072A9D04C24B82DFE2B1112FE38A0D8BB2F438@MCHP058A.global-ad.net>
Date: Fri, 20 Jan 2012 16:03:42 +0100
From: "Voelker, Bernhard" <bernhard.voelker@...mens-enterprise.com>
To: Karel Zak <kzak@...hat.com>, Attila Kinali <attila@...ali.ch>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"util-linux@...r.kernel.org" <util-linux@...r.kernel.org>
Subject: RE: /etc/fstab.d yes or not
Karel Zak 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.
Isn't this what the automounter does for decades?
Berny--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists