From owner-freebsd-current Mon Jan 12 14:24:20 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA10803 for current-outgoing; Mon, 12 Jan 1998 14:24:20 -0800 (PST) (envelope-from owner-freebsd-current) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA10635 for ; Mon, 12 Jan 1998 14:23:33 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA00344 for current@freebsd.org; Mon, 12 Jan 1998 17:22:55 -0500 (EST) (envelope-from toor) Message-Id: <199801122222.RAA00344@dyson.iquest.net> Subject: Sorry, but -current still has problems To: current@freebsd.org Date: Mon, 12 Jan 1998 17:22:54 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am going to be at the Bay area for a few more days this week. Unfortunately, I don't have any resources there to work on things unless I am at work. So, it is unlikely that I'll be able to work on the problems until Friday. It looks like I have made some improvements in the object/vnode mgmt in my local tree, but it is still not good enough to commit. The problem is that the vnode/objects have to be put on the free list when they are in the right state. Unfortunately, the state transistions at unpleasant to handle times. There may also be some locking problems, but I am still researching it. I hope to be able to get a good week of work in soon, so these problems can be more easily resolved. All in all, the new code should work alot better when it is done. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig.