util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Roger Leigh <rleigh@codelibre.net>
Cc: util-linux@vger.kernel.org
Subject: Re: Using /etc/fstab.d
Date: Mon, 28 Nov 2011 10:14:35 +0100	[thread overview]
Message-ID: <20111128091435.GB29168@nb.net.home> (raw)
In-Reply-To: <20111127221956.GF17458@codelibre.net>

On Sun, Nov 27, 2011 at 10:19:56PM +0000, Roger Leigh wrote:
> I noticed that support had recently been added for /etc/fstab.d.
> In Debian, we're configuring with --enable-libmount-mount, but
> I'm not seeing it being used; strace shows no opendir/stat calls
> for it.  Is anything else necessary to enable it, or is it not
> yet actually used by mount?

 Do you really have the latest git tree (gil pull to refresh)?

> I've just created a file /etc/fstab.d/test.fstab, and then
> tried "mount /foo", where /foo would be the entry in test.fstab,
> but don't see anything happening.

 [git clone / git clean -xdf; cd util-linux]

 $ ./autogen.sh
 $ ./configure --enable-libmount-mount
 $ make -C mount/ mount

 # cat /etc/fstab.d/tests.fstab 
 /home/fs-images/ext2.img /mnt/loop      auto    defaults,noauto

 # ./mount/mount /mnt/loop

 # findmnt /mnt/loop
 TARGET    SOURCE     FSTYPE OPTIONS
 /mnt/loop /dev/loop0 ext2   rw,relatime,errors=continue


 # findmnt --fstab /mnt/loop
 TARGET    SOURCE                   FSTYPE OPTIONS
 /mnt/loop /home/fs-images/ext2.img auto   defaults,noauto


 .. so works for me ;-)

 Try 
       LIBMOUNT_DEBUG=0xffff ./mount/mount ...

 to debug the problem.

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2011-11-28  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27 22:19 Using /etc/fstab.d Roger Leigh
2011-11-28  9:14 ` Karel Zak [this message]
2011-11-28 22:52   ` Roger Leigh
2011-11-29 11:19     ` 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=20111128091435.GB29168@nb.net.home \
    --to=kzak@redhat.com \
    --cc=rleigh@codelibre.net \
    --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).