From owner-freebsd-current  Thu Jul 16 09:43:16 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA07630
          for freebsd-current-outgoing; Thu, 16 Jul 1998 09:43:16 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from localhost.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07623
          for <current@freebsd.org>; Thu, 16 Jul 1998 09:43:04 -0700 (PDT)
          (envelope-from mi@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (mi@rtfm [199.232.255.52])
	by localhost.ziplink.net (8.8.8/8.8.7) with ESMTP id QAA04496;
	Thu, 16 Jul 1998 16:42:31 GMT
	(envelope-from mi@rtfm.ziplink.net)
Received: (from mi@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id MAA06432;
	Thu, 16 Jul 1998 12:42:30 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
Message-Id: <199807161642.MAA06432@rtfm.ziplink.net>
Subject: Re: tickadj -t not changing tick
In-Reply-To: <35ae253a.237736064@mail.cetlink.net> from "John Kelly" at "Jul 16, 98 04:13:26 pm"
To: current@FreeBSD.ORG
Date: Thu, 16 Jul 1998 12:42:30 -0400 (EDT)
Cc: jak@cetlink.net
X-Face: 
	%UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w<gv/&E-lL7twZCT8B~/PA4|\t$ti+22K">
		 hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"<kcG^EOVih
		 y+z3/UR{6SCQ
X-Mailer: ELM [version 2.4ME+ PL39 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Kelly once stated:

=>There is no way this nonsense is going to be required for longer then
=>a week, until one wizard or another commits a patch?
=
=Many wizards have committed many patches just to get us where we are
=today.

And today, the -current's handling of machine's clock is broken --
for some machines, at least.

=>My machine hare not only ran windoze without time problems before it
=>came to my hands
=
=That speaks for itself.

Please, explain what you are trying to say, sir... Kindly excuse
my poor English comprehension, and try to be clear and specific.

=>it also ran FreeBSD-2.2 with clock running just peachy.
=
=Clock?  You mean a little X app?  Wheeeee!  (Sorry, but one silly post
=deserves another)

No. Not a little clock. I mean, the machine's clock never used to
gain 10-20 seconds an hour until I installed the May's snapshot of
the current.  It's too bad, that the silly form of my post masked
its very serious content. I meant to ask a question:

	is the current state recognized as broken?
	what is the ETA for a fix?



		-mi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message