Date: Mon, 17 Jun 1996 22:49:19 -0700 (PDT) From: Sujal Patel <smpatel@umiacs.umd.edu> To: Sean Eric Fagan <sef@kithrup.com> Cc: michaelh@cet.co.jp, hackers@freebsd.org Subject: Re: vfork cow? Message-ID: <Pine.NEB.3.92.960617224617.494E-100000@xi.dorm.umd.edu> In-Reply-To: <199606180449.VAA06907@kithrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Jun 1996, Sean Eric Fagan wrote: > Any such program will not work under FreeBSD, because it doesn't do this! Actually, csh still has this code enabled.. If you make vfork() share the parent's memory (trivial with the current design), it actually does do as it was intended back in the dark ages. > Also, I don't think "many" programs ever depended on this. csh did, and it > was fixed a long time ago. (The fact that the 4.2 allowed the child process > to modify its parent's memory was a bug, and was listed as such in the > manpage.) I am with you 100% on this Sean... BUT! There are problems like the dreaded "Suspended (TTY Output)" bug in csh, that will mandate that vfork() be available for the forseeable future. Sujal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.92.960617224617.494E-100000>