From owner-freebsd-current Tue Mar 7 16:19:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id B533937B620 for ; Tue, 7 Mar 2000 16:19:50 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115267>; Wed, 8 Mar 2000 11:20:37 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: when is 4.0 up for release ? In-reply-to: <20000307175207.C3611@industrial-strength.net>; from shun@mail.utexas.edu on Wed, Mar 08, 2000 at 10:38:23AM +1100 To: Dan Potter Cc: freebsd-current@FreeBSD.ORG Message-Id: <00Mar8.112037est.115267@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <200003072033.OAA00074@cs.rice.edu> <20000307152417.A86322@panzer.kdm.org> <20000307175207.C3611@industrial-strength.net> Date: Wed, 8 Mar 2000 11:20:36 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Mar-08 10:38:23 +1100, Dan Potter wrote: >Has anyone thought about the problem I posted a few days ago (getcwd() >breaks on unionfs in some conditions)? That seems like a pretty big >problem to me... maybe not too many people use unionfs though, I don't >know. LINT contains the comment: # NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be # buggy, and WILL panic your system if you attempt to do anything with # them. They are included here as an incentive for some enterprising # soul to sit down and fix them. This suggests that there are more serious problems that need fixing. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message