From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] silly question
Date: Tue, 2 Sep 2014 16:04:43 -0700 [thread overview]
Message-ID: <20140902230443.0A3E9B82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 02 Sep 2014 19:00:56 EDT." <db849a10446d6804683a53529ac98cf2@ladd.quanstro.net>
On Tue, 02 Sep 2014 19:00:56 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> > > correct. plan 9 does not bother with leap seconds.
> >
> > seconds(1) "handles" leap seconds in that it will not crash
> > when it encounters them -- it accepts that sometimes there
> > are 61 seconds in a minute.
>
> i'm not sure if we're talking past each other, or making different points.
> but either way, i should clarify.
>
> by "not handling leap seconds" i mean there is no code in ctime() to add
> in leap seconds from an external source at the appropriate unix times.
> so e.g. gmtime could read e.g. /lib/leapseconds and ajust seconds similar
> to days (/sys/src/libc/9sys/ctime.c:137,138).
I was mistaken. Turns out neither do Unix systems handle
leapseconds. Now if only ITU punts on leapseconds in 2015, we
can let some future generation worry about leap minutes or
hours! Sorry for the noise.
next prev parent reply other threads:[~2014-09-02 23:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:07 Steve Simon
2014-09-02 8:27 ` lucio
2014-09-02 8:46 ` arnold
2014-09-02 9:40 ` Jens Staal
2014-09-02 14:07 ` arnold
2014-09-02 14:22 ` Steve Simon
2014-09-02 14:29 ` arnold
2014-09-02 17:02 ` erik quanstrom
2014-09-02 18:18 ` Steve Simon
2014-09-02 19:10 ` erik quanstrom
2014-09-02 20:04 ` Bakul Shah
2014-09-02 21:05 ` erik quanstrom
2014-09-02 21:50 ` Kurt H Maier
2014-09-02 23:00 ` erik quanstrom
2014-09-02 23:04 ` Bakul Shah [this message]
2014-09-02 23:19 ` erik quanstrom
2014-09-02 23:29 ` Bakul Shah
2014-09-02 21:10 ` Skip Tavakkolian
2014-09-02 21:14 ` Steve Simon
2014-09-02 21:27 ` Bakul Shah
2014-09-02 21:43 ` Skip Tavakkolian
2014-09-02 18:36 ` Kurt H Maier
2014-09-02 19:18 ` Steve Simon
2014-09-02 23:34 sl
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=20140902230443.0A3E9B82A@mail.bitblocks.com \
--to=bakul@bitblocks.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).