From owner-freebsd-current Mon Jan 5 17:00:59 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05321 for current-outgoing; Mon, 5 Jan 1998 17:00:59 -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 QAA04923 for ; Mon, 5 Jan 1998 16:55:40 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id TAA00500; Mon, 5 Jan 1998 19:55:35 -0500 (EST) (envelope-from toor) Message-Id: <199801060055.TAA00500@dyson.iquest.net> Subject: Re: msdogfs problems In-Reply-To: <199801052032.OAA11908@unix.tfs.net> from Jim Bryant at "Jan 5, 98 02:32:07 pm" To: jbryant@unix.tfs.net Date: Mon, 5 Jan 1998 19:55:35 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG 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 Jim Bryant said: > > i noticed someone else complaining about ms-dog problems out of recent > current, but since my symtomology is different, thought it worth > mention. > > has this problem been fixed yet, and if so, has it been committed to > CVS, and if so, on which branch? > The problems persist, and I have stated that I would annouce the fixes being committed to -current. Note that the -current mirrors have a delay, so you might have to wait until the mirror catches up, after my commits. I have the code structurally working now, and am cleaning it up, and getting rid of alot of old/unneeded cruft. (The code is actually simplified in a couple of areas.) I suspect that I'll be able to commit the fixes tonight, but I cannot promise (yet.) -- 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.