News for hackers. Stuff that matters.
Re:A future for fork(2) by chubot on Friday October 05, 2018 @11:38AM (#18148965)
It's a cleaner design, but I don't think it addresses the core of the issue.

You can still have say a "multi-threaded program" with a global mutex (the threads are created with RFMEM), and then when you want to fork (without RFMEM), you can be prone to deadlocks.

I guess the thread library has channels, and that doesn't happen? But as far as I know there are still mutexes in Go, and I would presume plan 9.

Go also has problems forking since it has a multi-threaded runtime. It only exposes os.ForkExec(), not os.Fork() and os.Execv().

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
Re:A future for fork(2) by MisterTea on Friday October 05, 2018 @03:48PM (#18151138)
> I guess the thread library has channels, and that doesn't happen? But as far as I know there are still mutexes in Go, and I would presume plan 9.

It does! Have a look at the thread man page: http://man.9front.org/2/thread

It's pretty much a wrapper/helper library built around rfork.