From: Pavel Machek <pavel@ucw.cz>
To: Christopher Brannon <cmbrannon@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /dev/time for Linux, inspired by Plan 9
Date: Sat, 14 Mar 2009 17:13:41 +0100 [thread overview]
Message-ID: <20090314161341.GB1496@ucw.cz> (raw)
In-Reply-To: <20090311200411.WPUP4619.eastrmmtao102.cox.net@eastrmimpo02.cox.net>
On Wed 2009-03-11 10:10:23, Christopher Brannon wrote:
> Under Plan 9 from Bell Labs, one queries or sets the system clock by
> reading or writing text strings to a special file named /dev/time.
> I implemented such a facility for Linux. A read of /dev/time produces
> four decimal numbers: epoch seconds, nanoseconds since start of epoch,
> nanoseconds since boot, and nanoseconds per second. Writing a
> decimal number
nanoseconds per second?! Just use 123.456 notation.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-03-17 13:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 15:10 [PATCH] /dev/time for Linux, inspired by Plan 9 Christopher Brannon
2009-03-11 21:49 ` Jochen Voß
2009-03-11 22:07 ` Bill Nottingham
2009-03-12 8:00 ` David Newall
2009-03-12 18:15 ` J.R. Mauro
2009-03-12 9:30 ` Giacomo A. Catenazzi
2009-03-14 16:13 ` Pavel Machek [this message]
2009-03-17 15:15 ` J.R. Mauro
2009-03-21 22:05 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 3:06 Christopher Brannon
2009-03-06 17:57 ` Greg KH
2009-03-07 5:43 ` J.R. Mauro
2009-03-07 5:54 ` Greg KH
2009-03-07 16:08 ` Chris Brannon
2009-03-08 16:03 ` J.R. Mauro
2009-03-06 22:56 ` john stultz
2009-03-07 16:23 ` Chris Brannon
2009-03-12 18:12 ` J.R. Mauro
2009-03-14 23:27 ` Chris Brannon
2009-03-10 11:22 ` Pavel Machek
2009-03-11 7:28 ` Américo Wang
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=20090314161341.GB1496@ucw.cz \
--to=pavel@ucw.cz \
--cc=cmbrannon@cox.net \
--cc=linux-kernel@vger.kernel.org \
/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 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.