From: KIMURA Masaru <hiyuh.root@gmail.com>
To: util-linux@vger.kernel.org
Subject: behavior of "# mount /dev"
Date: Wed, 9 Nov 2011 19:32:02 +0900 [thread overview]
Message-ID: <CAPYQg31hpFPkXVjwfALsnsiqikDtWqXavOswfejA-UPXhFzOjA@mail.gmail.com> (raw)
In-Reply-To: <CAPYQg30QdL8evykx4tfiO+K35ZFTuKOVxY_R08nKz5F=-imsVg@mail.gmail.com>
Oops, gmail remove list address.
Forward for recording the archives.
---------- Forwarded message ----------
From: KIMURA Masaru <hiyuh.root@gmail.com>
Date: 2011/11/9
Subject: Re: behavior of "# mount /dev"
To: Karel Zak <kzak@redhat.com>
>> Summary:
>> - "# mount /dev" hides udev managed /dev.
>> - because it doesn't return a busy error.
>> - because it uses tmpfs.
>> - using tmpfs, we are not able to treat this case as error in kernel.
>
> Sure, it's not a bug.
>
> It would be nice to have mount option (VFS flag) to control this behavior,
> something like:
>
> # mount -t tmpfs none /dev -o nooverlay
>
> # mount -t tmpfs none /dev --> EBUSY
ACK.
Thank you for taking time to check my poor translation.
prev parent reply other threads:[~2011-11-09 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 8:01 behavior of "# mount /dev" KIMURA Masaru
2011-11-09 0:09 ` Davidlohr Bueso
2011-11-09 1:47 ` KIMURA Masaru
2011-11-09 9:23 ` Karel Zak
[not found] ` <CAPYQg30QdL8evykx4tfiO+K35ZFTuKOVxY_R08nKz5F=-imsVg@mail.gmail.com>
2011-11-09 10:32 ` KIMURA Masaru [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=CAPYQg31hpFPkXVjwfALsnsiqikDtWqXavOswfejA-UPXhFzOjA@mail.gmail.com \
--to=hiyuh.root@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;
as well as URLs for NNTP newsgroup(s).