From owner-freebsd-hackers Mon Aug 12 00:50:32 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA06561 for hackers-outgoing; Mon, 12 Aug 1996 00:50:32 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA06554 for ; Mon, 12 Aug 1996 00:50:30 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.7.5/8.7.3) with ESMTP id AAA00372; Mon, 12 Aug 1996 00:47:27 -0700 (PDT) Message-Id: <199608120747.AAA00372@rah.star-gate.com> X-Mailer: exmh version 1.6.5 12/11/95 To: "Michael L. VanLoon -- HeadCandy.com" cc: A JOSEPH KOSHY , freebsd-hackers@freebsd.org Subject: Re: FreeBSD vs. NT Stability In-reply-to: Your message of "Mon, 12 Aug 1996 00:17:55 PDT." <199608120718.AAA14917@MindBender.HeadCandy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Aug 1996 00:47:26 -0700 From: Amancio Hasty Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From The Desk Of "Michael L. VanLoon -- HeadCandy.com" : We don't have kernel level support for threads that means that the processes context switching for threads is handle by the threads package. 2.2-current has support for *user* level threads and it shouldn't be that hard to convert the test program from using fork/exec to threads. On my last contract, I used -current's threads in a rather large large library. Not sure if the current threads package in -current is in sync with the latest from the author so you may find a bug or two which may have been fixed :( Amancio