From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] gmtime() ulong
Date: Sun, 2 Jun 2013 22:28:33 -0400 [thread overview]
Message-ID: <53268623235cb5f47b2404f75532917c@kw.quanstro.net> (raw)
In-Reply-To: <9fd46f174ab35243e649a8cec6705de6@gmx.de>
> on the topic, i thought about how to handle the 2038 problem
> in general with 9p which uses unsigned 32bit integers for atime
> and mtime fields.
on the one hand one could just expect long to be always 64-bits
by 2038. but that seems timid.
i'd rather see the time base switched to nanoseconds. then the bother
of the switch might benefit us while we still use the system. :-) 2038
is still 25 years off.
a more pressing worry for me is the fact that haswell chipsets, and
newer atom motherboards only support xhci.
- erik
next prev parent reply other threads:[~2013-06-03 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-02 23:31 cinap_lenrek
2013-06-03 1:03 ` cinap_lenrek
2013-06-03 2:28 ` erik quanstrom [this message]
2013-06-03 19:09 ` Richard Miller
2013-06-03 19:11 ` erik quanstrom
2013-06-03 19:15 ` Richard Miller
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=53268623235cb5f47b2404f75532917c@kw.quanstro.net \
--to=quanstro@quanstro.net \
--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).