From owner-cvs-src@FreeBSD.ORG Mon Nov 17 01:45:13 2003 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1EA916A4CE; Mon, 17 Nov 2003 01:45:12 -0800 (PST) Received: from VARK.homeunix.com (adsl-68-123-40-77.dsl.pltn13.pacbell.net [68.123.40.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id C84AF43FA3; Mon, 17 Nov 2003 01:45:09 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: from VARK.homeunix.com (localhost [127.0.0.1]) by VARK.homeunix.com (8.12.9/8.12.9) with ESMTP id hAH9hOen052295; Mon, 17 Nov 2003 01:43:24 -0800 (PST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.homeunix.com (8.12.9/8.12.9/Submit) id hAH9hOMK052294; Mon, 17 Nov 2003 01:43:24 -0800 (PST) (envelope-from das@FreeBSD.ORG) Date: Mon, 17 Nov 2003 01:43:23 -0800 From: David Schultz To: "Eugene M. Kim" Message-ID: <20031117094323.GB52046@VARK.homeunix.com> Mail-Followup-To: "Eugene M. Kim" , "Marc G. Fournier" , cvs-src@FreeBSD.ORG, src-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG References: <200311140823.hAE8NDAb005015@repoman.freebsd.org> <20031114105746.M497@ganymede.hub.org> <3FB87E09.40904@astralblue.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FB87E09.40904@astralblue.net> cc: "Marc G. Fournier" cc: cvs-src@FreeBSD.ORG cc: src-committers@FreeBSD.ORG cc: cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/fs/unionfs union_vnops.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2003 09:45:13 -0000 On Sun, Nov 16, 2003, "Eugene M. Kim ??" wrote: > Does this move unionfs into the `safe for general consumption' region, > or is this particular problem just a tip of an iceberg? Aside from support for FIFOs and other special files and a few other nits, it seems to behave pretty well. On the other hand, there are still a number of underlying problems that I don't have time to address. I suggest that you try it out and determine whether it works well enough for your purposes. Check the bug database before reporting any problems, though. (Note also that several of the relevant bugs have been prematurely closed recently.)