From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <6e35c0620709300818h5a8ee5enc62e521fca0d3a02@mail.gmail.com> Date: Sun, 30 Sep 2007 07:18:57 -0800 From: "Jack Johnson" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Support for Mac OS X Leopard In-Reply-To: <14ec7b180709291449g3ca45fd9k6d8f2609e87e2597@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <14ec7b180709291257w6c559276la634ac18366b09@mail.gmail.com> <8ccc8ba40709291430r6c2b8327g2c34ed37fee4cf5b@mail.gmail.com> <14ec7b180709291449g3ca45fd9k6d8f2609e87e2597@mail.gmail.com> Topicbox-Message-UUID: c82e5efc-ead2-11e9-9d60-3106f5b1d025 On 9/29/07, andrey mirtchovski wrote: > > devcons.c:^writebintime forces a new clock frequency down the kernel's > > throat at the writer's behest. the writer in this case is timesync... > > perhaps it shouldn't be allowed to do so? > > i don't know a solution, i simply avoid running timesync under parallels What happens when you change the time on a running machine, and how/why is this different from what timesync is trying to do? -Jack