Linked by Thom Holwerda on Mon 3rd Sep 2012 21:53 UTC
Thread beginning with comment 533784
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
Linked by Thom Holwerda on 04/14/13 18:22 UTC, submitted by MOS6510
More Features »
Sponsored Links



Member since:
2008-11-27
Yeah it's really not it's own operating system.
Considering it is based on Linux I can see why they thought this solution was the only reasonable one.
If each process would have it's own mount table (and in turn it's own view of the filesystem, including multiplexing of resources) as in Plan9 and processes could only communicate through the filesystem and not through some obscure system calls there would not have been any need for this what so ever because that together with the MMU would been enough. Chroot, as pointer out earlier would not have been a reasonable alternative either.
The overhead of the solution they came up with must be incredibly high. It is an ugly workaround, but it's nice they made it work anyway.
Edited 2012-09-04 11:12 UTC