News for hackers. Stuff that matters.

A comment on How the Mill CPU does fork() in a single address space. Parent comment

Re:How the Mill CPU does fork() in a single address space by bakul on Thursday April 16, 2015 @03:59PM (#9390420)
I thought a "turf" was a protection domain? Has that changed? I thought one can have a turf without a thread running in it.
[ Parent | on HN ]
Re:How the Mill CPU does fork() in a single address space by willvarfar on Friday April 17, 2015 @09:55AM (#9394277)
That's right. That hasn't changed.

Its natural for a normal OS to map their "processes" to Mill turfs. I make that jump in the explanation, but hold out hope that we can teach people to adopt a finer-grained approach where they sandbox and protect things within their program.

[ Parent | on HN ]