From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Roger Leigh <rleigh@codelibre.net>, Karel Zak <kzak@redhat.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Subject: Re: /etc/fstab.d yes or not
Date: Mon, 23 Jan 2012 22:07:20 +0000 [thread overview]
Message-ID: <20120123220720.1b2e9663@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <ACD4236E-A309-465F-8789-DA3A5B648313@mit.edu>
On Mon, 23 Jan 2012 08:55:21 -0500
Theodore Tso <tytso@MIT.EDU> wrote:
> I am extremely dubious about systemd, and would much rather it not be on any system that *I* run (and using UUID's to identify kernel notification is just whacko) , but I have to agree with Kay in that /etc/fstab.d is Just Wrong. The /etc/fstab file is parsed by many programs, shell scripts, and not just the ones in util-linux. We should consider it an ABI, and not mess with it.
Pedantically speaking /etc/fstab is not API, getmntent is API.
In practical terms though it would be very 'interesting' to implement
getmentent with an fstab.d, if not down right impossible because the
argument is a FILE *.
So with a good coding hat on - please don't consider fstab API, it's got
a programming interface 8). Otherwise I agree fstab.d is wrong.
Alan
next prev parent reply other threads:[~2012-01-23 22:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 14:04 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
2012-01-24 0:19 ` Boaz Harrosh
2012-01-24 9:47 ` bastien ROUCARIES
2012-01-20 14:43 ` Attila Kinali
2012-01-20 14:59 ` Karel Zak
2012-01-20 15:03 ` Voelker, Bernhard
2012-01-20 15:20 ` Kay Sievers
2012-01-20 15:49 ` Roger Leigh
2012-01-20 16:13 ` Kay Sievers
2012-01-20 16:22 ` Roger Leigh
2012-01-20 17:59 ` Kay Sievers
2012-01-23 13:55 ` Theodore Tso
2012-01-23 22:07 ` Alan Cox [this message]
2012-01-24 1:06 ` Ted Ts'o
2012-01-20 18:20 ` Denys Vlasenko
2012-01-20 18:29 ` Kay Sievers
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=20120123220720.1b2e9663@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=kay.sievers@vrfy.org \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rleigh@codelibre.net \
--cc=tytso@MIT.EDU \
--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
Powered by JetHome