On Sun, 25 Jan 1998 14:56:29 +0100 (CET) 
 Tom I Helbekkmo <tih@Hamartun.Priv.NO> wrote:

 > Whoops!
 > 
 > The new vfork is definitely not a happy puppy on the VAX.  After I
 > upgraded my KA650 to -current as of about 1998-01-21, lots of things
 > are failing.  So far, I've changed vfork() calls to fork() calls in
 > /sbin/mount, /sbin/fsck and /bin/csh, which is what it took to be
 > able to boot to multi user and login as root.
 > 
 > Of course, the fix is to figure out why vfork in the VAX port is so
 > screwed up, but there's little hope that I'll figure that out; I'm
 > not very familiar with the internals of the system yet.

I had to make some changes to the VAX pmap in order to do the new vfork().
The changes were fairly straightforward ... mostly it was a rearranging
of how some data was stored.

How exactly do the programs fail?  SEGV?

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                            Home: +1 408 866 1912
NAS: M/S 258-6                                       Work: +1 650 604 0935
Moffett Field, CA 94035                             Pager: +1 415 428 6939