Article View: comp.arch
Article #3443Re: Why fork? (long, was Re: IBM PC prehistory)
From: Jeff d'Arcy
Date: Thu, 18 Jan 1990 23:20
Date: Thu, 18 Jan 1990 23:20
9 lines
824 bytes
824 bytes
peter@ficc.uu.net (Peter da Silva): . And of course once you have a VM system fork() is just fine and vfork() is . a meaningless optimisation. Just mark all the data pages copy-on-write. So . why didn't they put vfork() in 2BSD? Not all VM systems have copy-on-write. Jeff d'Arcy OS/Network Software Engineer jdarcy@encore.com Encore has provided the medium, but the message remains my own
Technical Details
Message-ID:
<10904@encore.Encore.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!husc6!encore!pinocchio.encore.comReferences:
<IC51D77xds13@ficc.uu.net>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!snorkelwacker!husc6!encore!pinocchio.encore.com From: jdarcy@pinocchio.encore.com (Jeff d'Arcy) Newsgroups: comp.arch Subject: Re: Why fork? (long, was Re: IBM PC prehistory) Message-ID: <10904@encore.Encore.COM> Date: 18 Jan 90 23:20:06 GMT References: <IC51D77xds13@ficc.uu.net> Sender: news@Encore.COM Lines: 9