Setting it to sys_vfork() (which is the old style vfork() called
	__vfork14 in -current is not enough to get framemaker working
	with the new suse compat libaries under 1.4.1 (at least on my
	box).


		David/absolute

On Sun, 23 Jan 2000, Matthew Orgass wrote:

> On Sun, 23 Jan 2000, Hubert Feyrer wrote:
> 
> > Whatever call 190 is, it seems that SuSE really plays some bad dirty
> > tricks here with changed kernel calls. 
> 
>   190 is vfork and was not implemented until after 1.4.  It looks like it
> just calls __vfork14, so it would probably be a good candidate for a
> pullup.
> 
> Matthew Orgass
> darkstar@pgh.net
> 
> 
>