From owner-freebsd-current Wed Nov 4 19:14:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA05161 for freebsd-current-outgoing; Wed, 4 Nov 1998 19:14:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA05152 for ; Wed, 4 Nov 1998 19:14:23 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA25929 for ; Wed, 4 Nov 1998 22:14:18 -0500 (EST) Date: Wed, 4 Nov 1998 22:14:18 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: LinuxThreads and life with the FreeBSD kernel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I thought I'd fixed everything all up ready for LinuxThreads, but instead, I've gotten a nice unkillable process: 398 green 18 0 1068K 436K pause 2:46 0.00% 0.00% ex5 Anyway, I've gotten a full shared signal flag now, called RFSIGSHARE, so I think most of the work for LinuxThreads support _is_ done. I've got the patches here, and I need _REAL_ developers to come try this out and help me with it. The brunt of the work _is_ done, it would seem :) However, the unkillable process is strange, and LinuxThreads still does not 'work'. However, if someone has a test box, to test shared signals with RFMEM and RFSIGSHARE, I'd be grateful. And this changes struct proc, so all proc-using things MUST be compiled (libkvm, ps, top, modules), but if you don't know this you're probably not someone who should be doing this anyway. Cheers, Brian Feldman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message