On Tue, Apr 04, 2000 at 10:05:32PM +0800, Adrian Chadd wrote:
> 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.
Thanks, I was looking at the crash dump and at the source code and frankly,
it does my head in. I'll file a PR tonight; crashdump etc are available on
request/for download. Now what I need is some docs that give me a halfway
decent understanding on how UNIONFS works so I can do some debugging myself.
The 4.4BSD book is a bit curt on it...
Timo
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
