Mailinglist Archive: opensuse (933 mails)

< Previous Next >
Re: [opensuse] openSUSE on SSD?
  • From: Rodney Baker <rodney.baker@xxxxxxxxxxxx>
  • Date: Sat, 5 Jun 2010 01:13:16 +0930
  • Message-id: <201006050113.16920.rodney.baker@xxxxxxxxxxxx>
On Sat, 5 Jun 2010 01:08:11 Greg Freemyer wrote:
On Fri, Jun 4, 2010 at 11:09 AM, Rodney Baker <rodney.baker@xxxxxxxxxxxx>
On Sat, 5 Jun 2010 00:18:06 Patrick Shanahan wrote:
* Roger Oberholtzer <roger@xxxxxx> [06-04-10 02:43]:
On Thu, 2010-06-03 at 14:52 -0400, Patrick Shanahan wrote:
Mutt "sees" the msg but it is *not* "new", access time has changed.

Exactly as I thought. So mutt is not doing this in the most robust
manner. Because from the mail reading pov, the message is indeed new.

Indeed, the mail is unread but also not "new". It *has* been accessed.
The system has no way to indicate that the access was by the intended
reader, your neighbor, the cat or another program. Computers are not
yet that "intelligent". But you are "picking hairs". Mutt has
performed in this manner for many years and that manner has been
acceptable to its users.

I haven't been following this thread since its beginning, but can you not
mount the directory containing the mail store with the noatime option?
This does not update the access time every time the file is accessed by
some process - it only updates the last modified time when mods are
actually written to the file (it also slightly speeds up performance and
reduces the number of disk writes, which could be important on SSD).


You have it backwards.

noatime is what breaks a mutt install with default config because it
depends on atime being updated when a email is read.

Totally unrelated to noatime, the atime issue highlights that lots of
tools break Mutt's assumption that atime newer than mtime means a file
has been read.

But that broken assumption is a legacy problem the Mutt appears to
have always had and it seems there are non-default config options that
allow Mutt to quit using atime as a key flagging field. As yet I
haven't seen any discussion of the work-around.


OK, thanks for the explanation. It makes sense now.

Rodney Baker VK5ZTV

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >