Date: Tue, 4 Apr 2000 22:05:32 +0800 From: Adrian Chadd <adrian@freebsd.org> To: Kris Kennaway <kris@FreeBSD.org> Cc: Timo Geusch <freebsd@unix-consult.com>, current@freebsd.org Subject: Re: UNIONFS Message-ID: <20000404220530.B53939@ewok.creative.net.au> In-Reply-To: <Pine.BSF.4.21.0004040211310.3724-100000@freefall.freebsd.org>; from Kris Kennaway on Tue, Apr 04, 2000 at 02:14:15AM -0700 References: <20000404074034.A290@odie.unix-consult.com> <Pine.BSF.4.21.0004040211310.3724-100000@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000404220530.B53939>