> If that's the case, I've already tested the 2.2.4 and 2.2.5 from the > cvs, which means it's still broke :)
Sorry, I meant the broken vfork was added in 2.2.4 and was still broken in 2.2.5. With the latest cvs tree, vfork seems to work for me. > The reason I say to use the cvs is that it is always more up to date > for sparc than the Linus kernel, even tho some parts of it (like added > drivers) aren't as stable. The differences should be manageable now that we have had the big sparc merge of 2.2.4. Anton