From: Attila Kinali <attila@kinali.ch>
To: Karel Zak <kzak@redhat.com>
Cc: 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 15:43:09 +0100 [thread overview]
Message-ID: <20120120154309.3ae5f9e4a8f55c477dc423ab@kinali.ch> (raw)
In-Reply-To: <20120120140444.GC13157@x2.net.home>
On Fri, 20 Jan 2012 15:04:44 +0100
Karel Zak <kzak@redhat.com> wrote:
> I'd like to add support for /etc/fstab.d to libmount. The library is
> currently used by mount, umount and mount.nfs. The goal is to use it
> on more places.
>
> The /etc/fstab.d directory has been requested by people who maintains
> large number of mountpoints etc.
>
> The directory is not replacement for /etc/fstab, it's additional place
> where you can describe your filesystems.
It might not be my place to say anthing about this, as I am just
a mere mortal ....
But I'd like to express my concerns on this. In the years i've been
using Linux, the system has become a very complex beast. While in the
beginning I could just dig trough a couple of scripts to figure out
how a certain system worked, or more likely why it didn't work...
nowadays i have to have knowledge of a dozen of complex interacting
daemons to figure out why gedit refuses to edit a simple text file.
Complexity is added everywhere, to make a few corner cases a little
bit more simple. Making it more difficult for the 99% who do
not care about these corner cases. This in turn makes Linux this
opaque system that only a handfull of selected can understand, who
invest their whole life to the understanding of its many subsystems.
If this continues like this, in a decade or two, Linux will become
like windows. A system nobody clearly understands, which somehow works,
but sometimes not.. and nobody knows why.
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?
Attila Kinali
--
The trouble with you, Shev, is you don't say anything until you've saved
up a whole truckload of damned heavy brick arguments and then you dump
them all out and never look at the bleeding body mangled beneath the heap
-- Tirin, The Dispossessed, U. Le Guin
next prev parent reply other threads:[~2012-01-20 14:54 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 [this message]
[not found] ` <20120120154309.3ae5f9e4a8f55c477dc423ab-HB9FjVmMKa7tRgLqZ5aouw@public.gmane.org>
2012-01-20 14:59 ` Karel Zak
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=20120120154309.3ae5f9e4a8f55c477dc423ab@kinali.ch \
--to=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).