From owner-freebsd-current Sat Oct 31 14:08:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23321 for freebsd-current-outgoing; Sat, 31 Oct 1998 14:08:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23316 for ; Sat, 31 Oct 1998 14:08:55 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id OAA16996; Sat, 31 Oct 1998 14:08:44 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Mike Smith cc: John Birrell , lists@tar.com, current@FreeBSD.ORG Subject: Re: Kernel threading (was Re: Thread Scheduler bug) In-reply-to: Your message of "Sat, 31 Oct 1998 13:18:12 PST." <199810312118.NAA00662@dingo.cdrom.com> Date: Sat, 31 Oct 1998 14:08:43 -0800 Message-ID: <16992.909871723@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It sounds like the two of you should cooperate on it then; Richard has > clearly managed to get his head around at least some of the kernel > issues, while you're on top of the user-space stuff. I agree. While not perhaps adopting the perfect approach, at least Richard brings some very welcome *movement* to an issue which has been stalled for a regrettably long period of time. Let's try to run (cooperatively) with this and hopefully arrive at some working, architecturally clean kernel threads for FreeBSD! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message