From: Davidlohr Bueso <dave@gnu.org>
To: KIMURA Masaru <hiyuh.root@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: behavior of "# mount /dev"
Date: Wed, 09 Nov 2011 01:09:24 +0100 [thread overview]
Message-ID: <1320797364.3005.10.camel@offbook> (raw)
In-Reply-To: <CAPYQg32qP3Xb_gS45Md6ArqJGx22xZUdCg-W4z5f1ji2id7aSA@mail.gmail.com>
On Tue, 2011-11-08 at 17:01 +0900, KIMURA Masaru wrote:
> Hi,
>
> A user continues to mumble about behavior of "# mount /dev" in this list [1].
> He said, he did accidentally type
>
> # mount /dev
This will fail since /dev is immediately mounted and populated at boot
time (by udev among others).
>
> and "ls /dev" shows only initctl under /dev.
>
> "man mount" said,
>
> If only directory or device is given, for example:
>
> mount /dir
>
> then mount looks for a mountpoint and if not found then for a
> device in the /etc/fstab file.
>
> so I guess this is an undocumented behavior.
>
> Naohiro Aota explains that this is expected tmpfs' behavior in kernel. [2]
A whole lot of processes expect /dev/shm to be present; but mount(8)'s
relationship with tmpfs is no different than with any other linux
filesystem.
> And I think "just don't do such thing."
> But this user still doesn't accept this undocumented mount behavior.
>
> any thought?
All in all I'm not sure I follow this problem and Google translate isn't
helping much either. What is very strange is that /dev is not mounted at
startup, and the user should address *that* issue instead of manually
mounting /dev.
>
> [1] http://ml.gentoo.gr.jp/users/201111.month/2194.html
> [2] http://ml.gentoo.gr.jp/users/201111.month/2195.html
> --
> To unsubscribe from this list: send the line "unsubscribe util-linux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-11-09 0:09 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 [this message]
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
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=1320797364.3005.10.camel@offbook \
--to=dave@gnu.org \
--cc=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).