lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 20 Jan 2012 15:59:07 +0100
From:	Karel Zak <kzak@...hat.com>
To:	Attila Kinali <attila@...ali.ch>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	util-linux@...r.kernel.org
Subject: Re: /etc/fstab.d yes or not

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@...hat.com>
 http://karelzak.blogspot.com
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ