linux-kernel - Re: [PATCH] /dev/time for Linux, inspired by Plan 9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ef1cd66f0903111449m59c3a29fq5fbd13a682cc2e8b@mail.gmail.com>
Date:	Wed, 11 Mar 2009 21:49:27 +0000
From:	Jochen Voß <jochen.voss@...glemail.com>
To:	Christopher Brannon <cmbrannon@....net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] /dev/time for Linux, inspired by Plan 9

Hi Christopher,

2009/3/11 Christopher Brannon <cmbrannon@....net>:
> +/dev/time provides a file-based interface to the system clock.
> +Using this interface, one can query or set the system clock by reading or
> +writing text strings.  A read of /dev/time yields four decimal integers:
> +seconds since start of epoch, nanoseconds since start of epoch,
> +nanoseconds since boot, and nanoseconds per second.
> [...]
> +Examples
> +--------
> +cat /dev/time
> +# Produces: 1236121128 123612012877063000 495497 300,
> +# at time of writing on a test machine.

The last two numbers in the example seem suspicous to me.  300
nanoseconds per second?

I hope this helps,
Jochen
-- 
http://seehuhn.de/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/