On Wednesday 18 January 2012 22:16:28 starlight@xxxxxxxxxxx wrote: > Also I don't think it is unfortunate (or a bug) > that vfork() continues to exist in Linux aside > from the fact that the semantics differ from > other *nixes in subtle and potentially > confusing ways. > > As implemented in Linux vfork() is quite useful > and with the aforementioned clarifications to > the documentation, worth retaining. it also most likely won't ever be going away. a few reasons: - vfork() is really just a clone() with certain flags - clone() is never going away as it is used to create threads - vfork() is required for no-mmu systems (can't implement fork()) -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
