Users should not depend on the memory sharing semantics of vfork() as
other ways of speeding up the fork process may be developed in the
future.
as we are not planning to deprecate vfork. Besides NetBSD's
compatibility policy means we wouldn't change it anyway but introduce
something new.
Add
Portable applications should not depend on the memory sharing semantics
of vfork() as implementations exist that implement vfork() as plain
fork(2).
because this is or used to be a real hazard.
ok christos
885875e18f