9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to fix: 'arena arenas00 creation time after last write time'
Date: Tue, 28 Jul 2009 18:42:05 -0700	[thread overview]
Message-ID: <dd6fe68a0907281842t1442236cm8504c032602953c8@mail.gmail.com> (raw)
In-Reply-To: <fbd683a2adb7c247e72b9e4930686958@quanstro.net>

On Tue, Jul 28, 2009 at 3:16 PM, erik quanstrom<quanstro@quanstro.net> wrote:
> ignoring little bugs is the path to ruin.

That's why the print should just go away entirely.
The code assumes that the time from one boot
to the next only ever increases, which has been
demonstrated not to be true.  Maybe during one
boot your clock is screwed up for one reason or
another and you don't notice for a few days.
Then when you fix it, venti prints messages ad
infinitum?  That's just broken behavior.

It's not a question of time zones.  Time zones don't matter.
It's just that the clock was wrong before and later is
correct--there are many reasons this might happen--
and venti shouldn't care.

The time stamps, like the ones in a file system, are
informational.  It's okay if they're wrong.  There's no
need to print.

Or should we continue to discuss tangents?

Russ


  parent reply	other threads:[~2009-07-29  1:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <664879e97485933b3ca1bc9e37760730@quanstro.net>
2009-07-28  5:05 ` Corey
2009-07-28 13:22   ` erik quanstrom
2009-07-28 15:16     ` Russ Cox
2009-07-28 22:14       ` Dave Eckhardt
2009-07-28 22:16         ` erik quanstrom
2009-07-28 22:56           ` Corey
2009-07-29  1:42           ` Russ Cox [this message]
2009-07-29  4:24             ` Corey
2009-07-29  8:54               ` Corey
2009-07-29 14:02                 ` Steve Simon
2009-07-29 14:48               ` Russ Cox
2009-07-28 22:42     ` Corey
2009-07-28 23:50       ` erik quanstrom
     [not found] <09c88626d985457ecaa621715f4f1af0@quanstro.net>
2009-07-29  0:42 ` Corey
2009-07-29  1:04   ` erik quanstrom
     [not found] <26a2b1a9fb6ec5947c440b48b8bde174@quanstro.net>
2009-07-27 23:56 ` Corey
2009-07-28  0:35   ` erik quanstrom
2009-07-28  8:52   ` Steve Simon
2009-07-27  1:03 Corey
2009-07-27 16:28 ` Russ Cox
2009-07-27 20:31   ` Corey
2009-07-27 20:38     ` erik quanstrom
2009-07-27 20:58       ` Corey
2009-07-27 22:49       ` Corey
2009-07-27 22:52         ` erik quanstrom
2009-07-27 20:56     ` Lyndon Nerenberg
2009-07-30  4:15 ` Corey

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=dd6fe68a0907281842t1442236cm8504c032602953c8@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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).