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 for Android: free password hash cracker in your pocket

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

Message-ID: <1f1b08da0903061456g7621f92cx8a1e251249d739ac@mail.gmail.com>
Date:	Fri, 6 Mar 2009 14:56:45 -0800
From:	john stultz <johnstul@...ibm.com>
To:	Christopher Brannon <cmbrannon@....net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] /dev/time for Linux, inspired by Plan 9

On Tue, Mar 3, 2009 at 7:06 PM, Christopher Brannon <cmbrannon@....net> 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,
> jiffies since boot, and jiffies per second.

Ehh. Why would we want to export raw kernel internal values like
jiffies and HZ?

I think the CLOCK_MONOTONIC clockid would probably be a better value to export.

thanks
-john
--
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/