4 ms·
Can you share more details on this ?
by ungamedplayer 5y ago
Can you share more details on this ?
- Ericson2314 5y agoWhich? Pidfds were linked in the article to a great other article. CloudABI was about making an ABI/API so capsicum violations were build-time errors. Everything as a file descriptor is necessary for capsicum. WASM's WASI is sort of the spiritual successor, but I prefer a diversity of tactics so CloudABI and WASI should both exist. CloudABI is the best way to save desktop computing that's not a complete Hail Mary.
- Ericson2314 5y agohttps://lore.kernel.org/lkml/f8457e20-c3cc-6e56-96a4-3090d7da0cb6@JohnEricson.me/T/#m6be1994668e6f34837496c86f37f9fe52bfae990 https://lore.kernel.org/lkml/f8457e20-c3cc-6e56-96a4-3090d7d... I tried to kick of more discussion of spawning processes with pidfds --- I think sticking with fork + (fanicier) exec was the weakest part of CloudABI, but understandable at the time given one was trying to be implementable by all Unix-like kernels. The response from the main pidfds person is that plan should be forthcoming this fall!