From: Michael Tokarev <mjt@tls.msk.ru>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Greg KH <greg@kroah.com>, Jan Blunck <jblunck@suse.de>,
linux-arch@vger.kernel.org, viro@zeniv.linux.org.uk,
torvalds@osdl.org, akpm@osdl.org, adam@yggdrasil.com
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs
Date: Sun, 03 May 2009 11:29:20 +0400 [thread overview]
Message-ID: <49FD47D0.2070802@msgid.tls.msk.ru> (raw)
In-Reply-To: <9b2b86520905021504r3d32045ke1c14ffff1ffc898@mail.gmail.com>
Alan Jenkins wrote:
> On 5/2/09, Kay Sievers <kay.sievers@vrfy.org> wrote:
[]
>>> And it
>>> gives a nice clean way for new initramfs' to test for this feature -
>>> when they try to mount it, it fails. It would seem to make for a
>>> rather smoother migration path.
>> I think that is all covered just fine.
>
> Oh, I see.
>
> grep "/dev" /proc/mounts > /dev/null
Oh no. This one will match all your /dev/sda1 etc too :)
What yo want to do is either
grep -w /dev /proc/mount
or
awk '$2 == "/dev" { exit 0; } END { exit 1; }' /proc/mounts
or something similar. To distinguish between the following
two cases:
/dev/sda1 / ext3 rw,noatime,data=ordered 0 0
devfs /dev tmpfs rw,nosuid,size=512k,mode=755 0 0
/mjt
next prev parent reply other threads:[~2009-05-03 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1241097822.2516.3.camel@poy>
2009-05-02 7:16 ` [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs Christoph Hellwig
2009-05-02 11:34 ` Kay Sievers
2009-05-02 20:22 ` Alan Jenkins
2009-05-02 21:39 ` Kay Sievers
2009-05-02 22:04 ` Alan Jenkins
2009-05-03 7:29 ` Michael Tokarev [this message]
2009-05-02 21:41 ` Alan Jenkins
2009-05-02 21:54 ` Greg KH
2009-05-02 21:59 ` Kay Sievers
2009-05-02 16:59 ` Jeff Garzik
2009-05-02 17:57 ` Kay Sievers
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=49FD47D0.2070802@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=adam@yggdrasil.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jblunck@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sourcejedi.lkml@googlemail.com \
--cc=torvalds@osdl.org \
--cc=viro@zeniv.linux.org.uk \
/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