From: Karel Zak <kzak@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: util-linux <util-linux@vger.kernel.org>
Subject: Re: mount existing tmpfs mounts a new tmpfs
Date: Mon, 22 Jun 2015 10:20:08 +0200 [thread overview]
Message-ID: <20150622082008.GH1992@ws.net.home> (raw)
In-Reply-To: <55876C53.7030505@ubuntu.com>
On Sun, Jun 21, 2015 at 10:00:51PM -0400, Phillip Susi wrote:
> Forwarding this from debian bug #772419: Run mount /run, and it mounts
> a new tmpfs over top of the existing one in /run ( even if /run isn't
> listed in /etc/fstab ), hiding the existing files. It should say that
> it is already mounted.
We usually don't play any policy games in userspace (exception is
mount -a). If it's supported by kernel then it's correct behaviour.
And IMHO it's really correct behaviour because it creates a *new*
filesystem.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
next prev parent reply other threads:[~2015-06-22 8:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 2:00 mount existing tmpfs mounts a new tmpfs Phillip Susi
2015-06-22 7:09 ` Tom Yan
2015-06-22 8:20 ` Karel Zak [this message]
2015-06-22 12:55 ` Ruediger Meier
2015-06-22 14:15 ` Karel Zak
2015-06-22 18:45 ` Phil Susi
2015-06-23 9:44 ` Tom Yan
2015-06-22 13:31 ` Phil Susi
2015-06-22 14:49 ` Isaac Dunham
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=20150622082008.GH1992@ws.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