From owner-freebsd-current Sat Jul 6 17: 0:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9614D37B400 for ; Sat, 6 Jul 2002 17:00:12 -0700 (PDT) Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4470043E09 for ; Sat, 6 Jul 2002 17:00:12 -0700 (PDT) (envelope-from julian@elischer.org) Received: from InterJet.elischer.org ([12.232.206.8]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020707000011.SHTH8262.rwcrmhc52.attbi.com@InterJet.elischer.org> for ; Sun, 7 Jul 2002 00:00:11 +0000 Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA20531 for ; Sat, 6 Jul 2002 16:57:10 -0700 (PDT) Date: Sat, 6 Jul 2002 16:57:08 -0700 (PDT) From: Julian Elischer To: FreeBSD current users Subject: KSE M-III status & junior hacker project. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well with various hints from here and there I have fixed the ^Z/fg problem (at least it seems fixed to me and others that have tested) This basically leaves only one outstanding problem that I know of which is a problem that Warner has with a particular progam. (This may also be fixed but I don't know) If anyone knows of something that was broken by the KSE commit, (i.e. it worked just before and not after) and is STILL broken please let me know because I think I can pretty much declare that chapter finished, and I'd like to get on with "extending" KSE functionality. This will be the start of Milestone IV, which would be add support for threads to run on multiple processors. Coincident with that some work should also proceed on gradually identifying and cleaning up places in the kernel where multithreading is just not ready.. e.g. which thread status do you get when you type ^T? -------------- On that topic I'd like to suggest a "junior hacker project" for a couple of hackers that would like to sink their teeth into something but are feeling intimidated. The project would be design some options as to what 'ps' and 'top' should show for multithreaded processes, and then work up a set of patches that would allow them to do it.. This would include extending the kernel interface used by ps to handle multiple threads, using hte current interface as a guide, and altering the programs themselves. Anyone interested in this should contect me.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message