From: Karel Zak <kzak@redhat.com>
To: jon <jon@jonshouse.co.uk>
Cc: Valdis.Kletnieks@vt.edu, coreutils@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: Feature request, "create on mount" to create mount point directory on mount, implied remove on unmount
Date: Wed, 15 Jul 2015 16:38:30 +0200 [thread overview]
Message-ID: <20150715143830.GG31997@ws.net.home> (raw)
In-Reply-To: <1436050108.6501.509.camel@jonspc>
On Sat, Jul 04, 2015 at 11:48:28PM +0100, jon wrote:
> It solves these problems:
> 1) It solves the problem of processes writing data into the mount point
> when not mounted (as does, I accept a user space automounter, but as I
> explained the usage scenario differs).
>
> 2) It would be useful for embedded devices, installers etc. I do quite
> a bit of work in the embedded space, sometimes running kernel+shell+user
> process only, sometimes no udev, no systemd, not even full fat init.
>
> 3) installers or similar could use such an option for mounting install
> data. By specifying the flag user space processes can infer that the FS
> is successfully mounted by the presence of the mount point without the
> need to explicitly code against an event system or parse log files.
>
> 3) Users can use it to have a slightly improved new mount behaviour and
> also hopefully be used as a flag to indicate that "oh so clever user
> space managers" should stay away entries using it in fstab.
man mount (since util-linux v2.23, May 2013):
x-mount.mkdir[=mode] Allow to make a target directory (mountpoint).
It's userspace mount(8) option and you can use it in your fstab.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2015-07-15 14:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:01 Feature request, "create on mount" to create mount point directory on mount, implied remove on unmount jon
2015-07-04 20:56 ` Valdis.Kletnieks
2015-07-04 22:48 ` jon
2015-07-05 14:29 ` Al Viro
2015-07-05 15:46 ` jon
2015-07-05 17:39 ` Al Viro
2015-07-05 23:35 ` jon
2015-07-06 1:08 ` Al Viro
2015-07-06 2:34 ` jon
2015-07-06 3:07 ` Al Viro
2015-07-06 5:40 ` Valdis.Kletnieks
2015-07-15 14:38 ` 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=20150715143830.GG31997@ws.net.home \
--to=kzak@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=coreutils@gnu.org \
--cc=jon@jonshouse.co.uk \
--cc=linux-kernel@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