Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!lll-lcc!csustan!csun!aeusesef
From: aeusesef@csun.UUCP
Newsgroups: comp.unix.wizards
Subject: Vfork()
Message-ID: <566@csun.UUCP>
Date: Thu, 9-Apr-87 21:16:56 EST
Article-I.D.: csun.566
Posted: Thu Apr  9 21:16:56 1987
Date-Received: Sat, 11-Apr-87 13:17:03 EST
Organization: California State University, Northridge
Lines: 21
Keywords: vfork() fork() virtual memory

[]
In systems which use a virtual-memory version of fork (e.g., vfork in BSD),
how is the stack treated?  That is, since the basic purpose of vfork was to
allow two processes to use the same code and data spaces, until one of them
changed some part of the data (usually with an exec()) using a COPY-ON-WRITE
feature of the virtual memory handler (if available), then doesn't the exec
call force a copy of the data space, since it forces data onto the stack?
(Not being very terse, am I?)
Anyway, I would appreciate any help anybody out there could give me.
Thank you for your support.

 -----

 Sean Eric Fagan                    ------\
 Computer Center                    litvax \
 Cal State University, Northridge   rdlvax  \
 18111 Nordhoff St.                 psivax   --> !csun!aeusesef
 Northridge, CA  91330              hplabs  /
 AGTLSEF@CALSTATE.BITNET            ihnp4  /
                                    ------/
   "I drank what?!" -- Socrates | My opinions *are* facts.