public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Masatake YAMATO <yamato@redhat.com>, <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: Tue, 24 Jan 2012 02:19:24 +0200	[thread overview]
Message-ID: <4F1DF90C.5070108@panasas.com> (raw)
In-Reply-To: <CAPXgP10uUpSQzX0RzYY24uDBkNkRXM7NbR0H6P=dZ=+LxdX3Fw@mail.gmail.com>

On 01/20/2012 04:56 PM, Kay Sievers wrote:
> 
> It's an old glibc API, and /etc/fstab is ABI, not a service config
> file, which now can read more than one file. It's a very different
> problem. It an ABI change, not a config extension.
> 

Can't we have our cake and eat it too?

I mean why not have both?

The subsystem that you currently plan to parse the /etc/fstab.d/ will
intelligently  add the /etc/fstab.d/ entries to /etc/fstab before
actually processing and mounting /etc/fstab.

So the rpm guys have their /etc/fstab.d/ convenience and the rest
of the  ABI is kept intact. (If you can't bit them join them)

Since /etc/fstab is hand edited as well. There are lots of smart
things that can be done like a remark (#) marker at the end of the
file that all /etc/fstab.d/ entries get to be added after. (And
a comment for the user) and some smart duplicate removal of, and
so on ... Even a marker per line added.

Just my $0,017
Boaz

  parent reply	other threads:[~2012-01-24  0:19 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
2012-01-24  0:19     ` Boaz Harrosh [this message]
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
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=4F1DF90C.5070108@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=kay.sievers@vrfy.org \
    --cc=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux@vger.kernel.org \
    --cc=yamato@redhat.com \
    /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