From owner-freebsd-current Mon Dec 21 09:51:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25662 for freebsd-current-outgoing; Mon, 21 Dec 1998 09:51:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25652 for ; Mon, 21 Dec 1998 09:51:47 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id LAA05522; Mon, 21 Dec 1998 11:49:39 -0600 (CST) (envelope-from dick) Message-ID: <19981221114939.A5500@tar.com> Date: Mon, 21 Dec 1998 11:49:39 -0600 From: Richard Seaman To: Jeremy Lea Cc: Alfred Perlstein , "Brian W. Buchanan" , Joseph Lee , freebsd-current@FreeBSD.ORG Subject: Re: linking against libc_r References: <19981221093241.C546@tar.com> <19981221192734.E4060@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981221192734.E4060@shale.csir.co.za>; from Jeremy Lea on Mon, Dec 21, 1998 at 07:27:35PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 21, 1998 at 07:27:35PM +0200, Jeremy Lea wrote: > > Wine seems to want clone(), from a quick read of the man page. Does the > native LinuxThreads stuff implement this as a FreeBSD syscall? The FreeBSD "port" of Linux threads does not use nor implement a clone syscall. It uses rfork instead within pthread_create to simulate the clone call. If Wine calls "clone" directly, rather than via the phread_create call, it would be easy enough to implement a FreeBSD call, either in libc or as a syscall, that mimics clone. Actually, there are already two "clone" calls within Linux Threads right now. There is a wrapper "clone" call that wraps the clone syscall (see clone.S in the linux threads source). -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message