From owner-freebsd-hackers@FreeBSD.ORG  Wed Dec 22 08:07:33 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BAA6116A4CE
	for <freebsd-hackers@freebsd.org>;
	Wed, 22 Dec 2004 08:07:33 +0000 (GMT)
Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 920CC43D31
	for <freebsd-hackers@freebsd.org>;
	Wed, 22 Dec 2004 08:07:31 +0000 (GMT)
	(envelope-from dave@horsfall.org)
Received: from localhost (dave@localhost)
	by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id iBM87Su02565
	for <freebsd-hackers@freebsd.org>;
	Wed, 22 Dec 2004 19:07:28 +1100 (EST)
Date: Wed, 22 Dec 2004 19:07:28 +1100 (EST)
From: Dave Horsfall <dave@horsfall.org>
To: FreeBSD Hackers <freebsd-hackers@freebsd.org>
In-Reply-To: <20041222075144.GN79646@cirb503493.alcatel.com.au>
Message-ID: <Pine.BSI.4.61.0412221904450.2350@dave.horsfall.org>
References: <6.2.0.7.1.20041221221529.021bb7d0@pop.phreaker.net>
 <20041222075144.GN79646@cirb503493.alcatel.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: calibrating time
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Dec 2004 08:07:33 -0000

On Wed, 22 Dec 2004, Peter Jeremy wrote:

> Out of interest, what are you expecting to demonstrate?  In FreeBSD,
> both sleep(3) and usleep(3) are implemented using nanosleep(2).
> (This differs from the traditional implementation of sleep(3) which
> used alarm(2) and pause(2)).

Or, for that matter, the traditional use of sleep(2) before that :-)

-- Dave