News for hackers. Stuff that matters.
Re:A future for fork(2) by dis-sys on Friday October 05, 2018 @11:36PM (#18153366)
> Go also has problems forking since it has a multi-threaded runtime. It only exposes os.ForkExec(), not os.Fork() and os.Execv().

true, and this is causing lots of headache for those who want to implement concurrent snapshotting using fork in Go.

Re:A future for fork(2) by dullgiulio on Saturday October 06, 2018 @04:40AM (#18154195)
I thought this was a solved issue? https://github.com/golang/go/issues/20676