From owner-freebsd-current Fri Aug 21 07:22:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10900 for freebsd-current-outgoing; Fri, 21 Aug 1998 07:22:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10893 for ; Fri, 21 Aug 1998 07:22:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id PAA01382; Fri, 21 Aug 1998 15:20:34 +0200 (CEST) To: Mike Smith cc: Brian Somers , Brian Feldman , Terry Lambert , bde@zeta.org.au, freebsd-current@FreeBSD.ORG, jwd@unx.sas.com Subject: Re: 13 months of user time? In-reply-to: Your message of "Fri, 21 Aug 1998 03:28:14 -0000." <199808210328.DAA07457@dingo.cdrom.com> Date: Fri, 21 Aug 1998 15:20:34 +0200 Message-ID: <1380.903705634@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >With no APM in the kernel, the BIOS is not at liberty to play with the >clock. (No connect, no enable.) > >You're welcome to check the archives, if you wish. Yes, it is at liberty to play with it, but must do so in a "transparent" way. >I also consider it a fault in our timing support if it can't handle >time moving forwards at a variable rate. "APM" doesn't send the clock >backwards, so no time interval should ever be negative. > >Please take this issue seriously. You can't just handwave and say >"it's all APM's fault". Belive me, I'm taking this very seriously, but until I can make it fail on one of my machines, I'll have a hard time fixing it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message