From owner-freebsd-hackers Tue Apr 1 15:03:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA10475 for hackers-outgoing; Tue, 1 Apr 1997 15:03:40 -0800 (PST) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA10457 for ; Tue, 1 Apr 1997 15:03:35 -0800 (PST) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id PAA27605; Tue, 1 Apr 1997 15:02:19 -0800 (PST) To: Terry Lambert cc: proff@suburbia.net, joe@pavilion.net, gbeach@cybernet.com, hackers@freebsd.org Subject: Re: Internal clock In-reply-to: Your message of "Tue, 01 Apr 1997 15:27:42 MST." <199704012227.PAA12232@phaeton.artisoft.com> Date: Tue, 01 Apr 1997 15:02:19 -0800 Message-ID: <27601.859935739@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are you worried about all of these issues simultaneously? Are you > worried about allowing concurrent readers? Implement multiple > reader/single writer locking. You forgot about: Implement virtual time generator so that Jordan & co can actually get around to building the "frozen current" mechanism from hell, with duplicate CVS tree and all, along with the new build/relesae system, the setup tool, the fancy administration/help system, the new combined package/distribution scheme and and and... So can I have those virtual time generator plans by next week please? I'm sort of in a hurry. :-) Jordan