All of
 help / color / mirror / Atom feed
From: Valerie Henson <>
To: Dave Jones <>,
	Michael Kerrisk <>,
	lkml <>
Subject: Re: Documenting MS_RELATIME
Date: Mon, 12 Feb 2007 11:42:11 -0800	[thread overview]
Message-ID: <20070212194211.GA5108@nifty> (raw)
In-Reply-To: <>

On Mon, Feb 12, 2007 at 10:40:10AM -0500, Dave Jones wrote:
> The one problem with noatime is that mutt's 'new mail arrived' breaks
> as you mentioned in the relatime changelog, so I'm surprised that
> they turned it on by default.  With relatime fixing that however,
> I'm also unaware of anything that breaks.   I'd be curious to
> do a Fedora test release with relatime, but I know the answer I'll
> get when I recommend we add it to our generated fstabs..
> "If it's good enough, why isn't it the kernel default"
> Hence my current line of questioning ;-)

Okay, I have to admit I used the normal atime semantics, exactly once.
Someone hacked my laptop about 4 years ago (back when I didn't have a
firewall and a remotely exploitable samba server was on by default in
some Red Hat install).  I pulled the plug on the network (no wireless
either) and figured out which files the attacker read, which gave me
some peace of mind. :)

Personally, I'd trade that for the performance/battery life/etc. of


  parent reply	other threads:[~2007-02-12 19:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-10 17:56 Documenting MS_RELATIME Michael Kerrisk
2007-02-11  0:54 ` Dave Jones
2007-02-12  6:55   ` Valerie Henson
2007-02-12 15:40     ` Dave Jones
2007-02-12 17:49       ` Jan Engelhardt
2007-02-12 17:55         ` Jörn Engel
2007-02-12 19:53         ` Petri Kaukasoina
2007-02-12 19:57           ` Valerie Henson
2007-02-12 19:42       ` Valerie Henson [this message]
2007-02-12  6:53 ` Valerie Henson

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070212194211.GA5108@nifty \ \ \ \ \

* 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.