Re: updating mtime for char/block devices?

From: Carl-Daniel Hailfinger (c-d.hailfinger.devel.2005_at_gmx.net)
Date: 03/01/05

  • Next message: Robert Han***: "Re: Fw: 2.6.11-rc4 doubles CPU temperature" 
    Date:	Tue, 01 Mar 2005 01:45:47 +0100
To: Arjan van de Ven <arjan@infradead.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/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Robert Han***: "Re: Fw: 2.6.11-rc4 doubles CPU temperature"