News for hackers. Stuff that matters.

A comment on Linux Namespaces and Go Don't Mix. Parent comment

Re:Linux Namespaces and Go Don't Mix by di4na on Friday June 02, 2017 @04:24PM (#14473023)
Just saying, but Erlang do not target that type of "System Programming" and the answer to that problem in Erlang would probably work through totally different way to do it. This namespace thing would not be a problem.

This is not a problem of M:N. This is a problem of Go being badly designed. Not new.

[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by dozzie on Friday June 02, 2017 @06:23PM (#14473739)
More like reification of the very old problem from the times when we got threading API, with thread safety of functions that alter process-wide state (umask(), chdir(), sleep()), except now it's calls that alter some thread-specific thing.
[ Parent | on HN ]
Re:Linux Namespaces and Go Don't Mix by wbl on Friday June 02, 2017 @10:58PM (#14474772)
It's a problem with Linux not permitting inspection of interfaces through a namespace. If I have a chroot I can look in from outside easily. Apparently not so with container interfaces.
[ Parent | on HN ]