From: Karel Zak <kzak@redhat.com>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: umount -a
Date: Mon, 8 Aug 2011 10:54:22 +0200 [thread overview]
Message-ID: <20110808085422.GH2204@nb.net.home> (raw)
In-Reply-To: <4E387230.5060002@gmail.com>
On Tue, Aug 02, 2011 at 04:54:56PM -0500, Bruce Dubbs wrote:
> At linuxfromscratch, we've just made some changes to write bootscript
> messages to /run/var. This seems to work fine for us until shutdown
> where
>
> umaount -a
>
> unmounts /run which is mounted as a tmpfs. We can certainly work around
> the problem, but was wondering if this issue may also affect others.
>
> The man page for umount says:
>
> -a All of the file systems described in /etc/mtab are unmounted.
> (With umount version 2.7 and later: the proc filesystem is not
> unmounted.)
>
> Would it be reasonable to change umount -a to also omit /run if it is
> mounted as a tmpfs?
umount -a -t notmpfs ?
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-08-08 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 21:54 umount -a Bruce Dubbs
2011-08-08 0:35 ` Mike Frysinger
2011-08-08 8:54 ` Karel Zak [this message]
2011-08-08 9:15 ` Tom Gundersen
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=20110808085422.GH2204@nb.net.home \
--to=kzak@redhat.com \
--cc=bruce.dubbs@gmail.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