From: Karel Zak <kzak@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Option to create missing mount point
Date: Tue, 18 Feb 2014 16:16:50 +0100 [thread overview]
Message-ID: <20140218151650.GA32225@x2.net.home> (raw)
In-Reply-To: <53037325.3090808@ubuntu.com>
On Tue, Feb 18, 2014 at 09:50:13AM -0500, Phillip Susi wrote:
> A debian bug has requested that mount create the mount point if it
> does not exist yet. My initial reaction was no, but one use case does
> seem to be a good reason. That would be if you want to set up a tmpfs
> mount with several sub mounts in /etc/fstab. You currently can't do
> that since when the tmpfs is mounted, it is empty. Is this something
> that might be a good idea?
Yes, v2.23 release notes:
mount(8):
- supports new userspace mount option x-mount.mkdir[=<mode>] to
create mountpoints on demand
it's also in man page :)
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2014-02-18 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 14:50 Option to create missing mount point Phillip Susi
2014-02-18 15:16 ` 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=20140218151650.GA32225@x2.net.home \
--to=kzak@redhat.com \
--cc=psusi@ubuntu.com \
--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