From: bastien ROUCARIES <roucaries.bastien-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
Cc: Kay Sievers <kay.sievers-tD+1rO4QERM@public.gmane.org>,
Masatake YAMATO <yamato-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: /etc/fstab.d yes or not
Date: Tue, 24 Jan 2012 10:47:41 +0100 [thread overview]
Message-ID: <201201241047.42303.roucaries.bastien@gmail.com> (raw)
In-Reply-To: <4F1DF90C.5070108-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
Le Tuesday 24 January 2012 01:19:24, Boaz Harrosh a écrit :
> 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.
I agree. And moreover extensible if they want to use xml for /etc/fstab.d/.
>
> Just my $0,017
> Boaz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-24 9:47 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 [this message]
2012-01-20 14:43 ` Attila Kinali
[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=201201241047.42303.roucaries.bastien@gmail.com \
--to=roucaries.bastien-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org \
--cc=kay.sievers-tD+1rO4QERM@public.gmane.org \
--cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yamato-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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).