stevens@inuxh.UUCP (W Stevens) (02/22/84)
What is system call #66 (0x42) in 4.0BSD Unix? I have a hacked 4.0BSD binary I'm trying to run on USG Unix, and this system call causes a SIGSYS + core dump. -- Scott Stevens AT&T Consumer Products Indianapolis, Indiana, USA UUCP: inuxh!stevens
v.wales%ucla-locus@sri-unix.UUCP (02/23/84)
From: Rich Wales <v.wales@ucla-locus> Scott -- In reply to your question: What is system call #66 (0x42) in 4.0BSD Unix? I have a hacked 4.0BSD binary I'm trying to run on USG Unix, and this system call causes a SIGSYS + core dump. System call #66 is "vfork" (we have a 4.1BSD system, but I believe this call was the same in 4.0BSD). "vfork" is a special variant of "fork" in which the child shares the parent's virtual memory space. The idea was to avoid having to make a copy of a large process in cases where the child was just going to do an "exec" anyway. A "vfork" may not be equivalent to a "fork" if the child changes the values of variables, but since Berkeley's documentation specifically urged people right from the beginning not to exploit this feature, you are probably safe in simply changing the "vfork" to a "fork" (system call #2). -- Rich <v.wales@UCLA-LOCUS.ARPA>