From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: updating mtime for char/block devices?
Date: Tue, 01 Mar 2005 01:45:47 +0100 [thread overview]
Message-ID: <4223BB3B.4060309@gmx.net> (raw)
In-Reply-To: <1109576878.6298.49.camel@laptopd505.fenrus.org>
Arjan van de Ven schrieb:
> On Mon, 2005-02-28 at 00:51 +0100, Carl-Daniel Hailfinger wrote:
>
>>Hi,
>>
>>is it intentional that
>>echo foo >/dev/hda1
>>doesn't update the mtime of the device node, but
>>echo foo >/dev/tty10
>>does update the mtime of the device node?
>>
>>And no, mounting with the noatime flag doesn't help because the
>>mtime is updated. IIRC some time ago this behaviour was different,
>>but I could easily be mistaken.
>
>
> devices are tricky in general in this respect, /dev may be mounted read
> only for example ;)
Sorry for not specifying my real problem which is preventing disk access
when my laptop is running on battery.
Can I prevent mtime updates for all device files? Mounting /dev readonly
would certainly help, but for that to work I'd have to move /dev to a
different filesystem, right?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2005-03-01 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 23:51 updating mtime for char/block devices? Carl-Daniel Hailfinger
2005-02-28 7:47 ` Arjan van de Ven
2005-03-01 0:45 ` Carl-Daniel Hailfinger [this message]
2005-03-01 1:47 ` Valdis.Kletnieks
2005-03-01 9:37 ` Russell King
2005-03-01 11:15 ` Carl-Daniel Hailfinger
2005-03-01 11:19 ` Russell King
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=4223BB3B.4060309@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--cc=arjan@infradead.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.