Quick question, out of curiosity, about NetBSD's vfork(): In 1998, we switched vfork() back from the 4.4 semantics (Copy-on-Write until exec) to the traditional BSD semantics (shared address space between parent and child until exec()). I'm curious about the how this is used: -- was this an optimization, with code working pretty much as before, but gaining speed from not doing a bunch of unneeded Copy-on-Write setup? -- are there programs in-tree which depend on the shared address space semantics? -- are there common third-party apps which do? -- what do other systems do? Needless to say, there's no lurking change behind this question -- just wondering... -- Jim Wise jwise%draga.com@localhost
Attachment:
pgp7xYCIMfoCe.pgp
Description: PGP signature