From owner-freebsd-current Tue Apr 4 7: 5:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 06E5537BA49 for ; Tue, 4 Apr 2000 07:05:46 -0700 (PDT) (envelope-from freebsd@ewok.creative.net.au) Received: (qmail 66040 invoked by uid 1008); 4 Apr 2000 14:05:32 -0000 Date: Tue, 4 Apr 2000 22:05:32 +0800 From: Adrian Chadd To: Kris Kennaway Cc: Timo Geusch , current@freebsd.org Subject: Re: UNIONFS Message-ID: <20000404220530.B53939@ewok.creative.net.au> References: <20000404074034.A290@odie.unix-consult.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Tue, Apr 04, 2000 at 02:14:15AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Apr 04, 2000, Kris Kennaway wrote: > On Tue, 4 Apr 2000, Timo Geusch wrote: > > > Here be dragons, I know :-). Got myself a nice juicy & reproducable > > crash here, so I thought I might as well try to track down this > > problem. But before I start,is anyone else working on this one? I'd > > hate to waste my not exactly ample time trying to duplicate somebody > > else's work. > > Frankly, unless you have the time to fix unionfs completely I wouldn't > bother. We know it's broken, whats needed is someone with a good handle on > the VFS code to sit down and spend a week or so to fix it. On the other > hand, if that's you then go for it (you'd certainly learn a lot of useful > things in the process) > I'm starting VFS hacking again :) Throw up a PR, I'll assign it to myself and I'll look at it for you. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message