From: Karel Zak <kzak@redhat.com>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
util-linux@vger.kernel.org
Cc: Masatake YAMATO <yamato@redhat.com>, Roger Leigh <rleigh@codelibre.net>
Subject: Re: /etc/fstab.d yes or not (resolved)
Date: Tue, 24 Jan 2012 12:02:18 +0100 [thread overview]
Message-ID: <20120124110218.GA28644@x2.net.home> (raw)
In-Reply-To: <20120120140444.GC13157@x2.net.home>
I have reverted the fstab.d support. The libmount will NOT read
/etc/fstab.d by default.
If you really need an additional configuration outside /etc/fstab
then you have to explicitly add the option --fstab <path> to mount(8)
command line. This option may be specified more than once and the
<path> may be a directory. This solution should be enough for
initramfs scripts.
Thanks for feedback.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-01-24 11:02 UTC|newest]
Thread overview: 29+ 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
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 12:21 ` Karel Zak
2012-01-23 13:01 ` Masatake YAMATO
2012-01-23 13:03 ` Kay Sievers
2012-01-23 13:26 ` Masatake YAMATO
2012-01-23 13:37 ` Kay Sievers
2012-01-23 14:14 ` Masatake YAMATO
2012-01-23 14:32 ` 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 ` Karel Zak [this message]
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=20120124110218.GA28644@x2.net.home \
--to=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rleigh@codelibre.net \
--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;
as well as URLs for NNTP newsgroup(s).