linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Sergei Zhirikov <sfzhi@yahoo.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting UBIFS readonly - is it really readonly?
Date: Mon, 23 Aug 2010 15:41:23 +0300	[thread overview]
Message-ID: <1282567283.24044.35.camel@localhost> (raw)
In-Reply-To: <1282566220.24044.22.camel@localhost>

On Mon, 2010-08-23 at 15:23 +0300, Artem Bityutskiy wrote:
> On Tue, 2010-07-27 at 21:05 +0200, Sergei Zhirikov wrote:
> > As you can see, there is "ro", which causes UBIFS to be initially
> > mounted readonly. And later it is *never* remounted read-write.
> > Everything seems to work as expected (I get "Read-only file system"
> > error upon a write attempt) except one thing. Somehow the modification
> > time of /dev/console is updated every time the system boots. Note: I'm
> > not talking about the /dev/console located inside the /dev mount
> > (which is tmpfs and is obvously writable), I'm talking about
> > the /dev/console located on the root file system and accessed
> > (probably by init) before /dev is mounted. I'm really puzzled. How is
> > this possible? The root filesystem has been readonly all the time and
> > still the timestamp is somehow updated. Does anyone have an idea what
> > might be going on there?
> 
> Did you solve the issue, I'm just curious.

I think you can use inotify to verify whether the FS is ever changed?

http://en.wikipedia.org/wiki/Inotify

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2010-08-23 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 19:05 Mounting UBIFS readonly - is it really readonly? Sergei Zhirikov
2010-08-05  4:51 ` Artem Bityutskiy
2010-08-23 12:23 ` Artem Bityutskiy
2010-08-23 12:41   ` Artem Bityutskiy [this message]
2010-08-23 18:33     ` Sergei Zhirikov
2010-08-23 19:14       ` Artem Bityutskiy

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=1282567283.24044.35.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sfzhi@yahoo.com \
    /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).