From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: linux-kernel-owner@vger.kernel.org Date: Fri, 20 Jan 2012 15:59:07 +0100 From: Karel Zak To: Attila Kinali Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, util-linux@vger.kernel.org Subject: Re: /etc/fstab.d yes or not Message-ID: <20120120145907.GA20377@x2.net.home> References: <20120120140444.GC13157@x2.net.home> <20120120154309.3ae5f9e4a8f55c477dc423ab@kinali.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20120120154309.3ae5f9e4a8f55c477dc423ab@kinali.ch> Sender: linux-kernel-owner@vger.kernel.org List-ID: 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 http://karelzak.blogspot.com