Inferno Operating System
61–70 of 102 posts
Re: Inferno Operating System
#62Earlier quoted context omitted.
Linux containers feel like weak imitations of jails and zones found in FreeBSD and Solaris/illumos, for that matter.
Yeah zones especially, I agree.
Re: Inferno Operating System
#63Earlier quoted context omitted.
Linux containers feel like a very weak imitation of what they could be under an environment like Plan9 imo. Linux lacks a lot of core abstraction properties that would make containers elegant to implement under something like the Plan9 model, at least. Cool project inspired partially by Linux containers: https://doc.9gridchan.org/guides/spawngrid
Linux containers feel like weak imitations of jails and zones found in FreeBSD and Solaris/illumos, for that matter.
Re: Inferno Operating System
#64This OS doesn't require an MMU or protected memory. I wonder if a processor architecture that lacks those features could yield much higher performance due to less complexity, reduced memory latency or less cache miss penalty. Will it be enough to mitigate the perormance penalty of runing code in the Dis VM?
You'd have to compensate for the lack of memory protection by running all unprivileged code in a VM, which would very likely introduce its own class of complexities and performance penalties.
Re: Inferno Operating System
#65Back when I was in university we had a small course on Limbo/Inferno because of a connection my university (RIT) had to bell labs. I took the course in... 1998? and wrote a version of Tetris for limbo. The code was awful, but did find a bug in the Tk implementation. This lead me to my proudest/most embarrassing programming moment - apparently, my code ended up in front of Dennis Ritchie, who thought the code was terr…
I find it impressive you still have code you wrote for a university class in '98!
Re: Inferno Operating System
#66Earlier quoted context omitted.
CRIU should allow you to migrate a running process from one system to another, particularly in combination with a container (Docker or LXC/D).
Doesn't this work on about nothing in practice? Like nothing that has an open file, no gui apps etc.
Re: Inferno Operating System
#67This OS doesn't require an MMU or protected memory. I wonder if a processor architecture that lacks those features could yield much higher performance due to less complexity, reduced memory latency or less cache miss penalty. Will it be enough to mitigate the perormance penalty of runing code in the Dis VM?
[0] https://research.cs.wisc.edu/areas/os/Seminar/schedules/pape... [1] http://joeduffyblog.com/2015/11/03/blogging-about-midori/ [2] https://arxiv.org/abs/1902.05178
Re: Inferno Operating System
#68Namespaces: a program's view of the network is a single, coherent namespace that appears as a hierarchical file system but may represent physically separated (locally or remotely) resources Standard communication protocol: a standard protocol, called Styx, is used to access all resources, both local and remote This looks similar to Qubes Air roadmap: https://www.qubes-os.org/news/2018/01/22/qubes-air/
Except that you cannot run a Qubes CPU server without a giant overhead.
Re: Inferno Operating System
#69Back when I was in university we had a small course on Limbo/Inferno because of a connection my university (RIT) had to bell labs. I took the course in... 1998? and wrote a version of Tetris for limbo. The code was awful, but did find a bug in the Tk implementation. This lead me to my proudest/most embarrassing programming moment - apparently, my code ended up in front of Dennis Ritchie, who thought the code was terr…
I find it impressive you still have code you wrote for a university class in '98!
Re: Inferno Operating System
#70Earlier quoted context omitted.
Linux containers feel like a very weak imitation of what they could be under an environment like Plan9 imo. Linux lacks a lot of core abstraction properties that would make containers elegant to implement under something like the Plan9 model, at least. Cool project inspired partially by Linux containers: https://doc.9gridchan.org/guides/spawngrid
> Linux lacks a lot of core abstraction properties No, it's worse than that: It has too many of them, leading to a mess of special cases that you have to deal with. What happens when you have a socket in your file system, and you export it over NFS? Lacking abstraction properties is fixable -- you can add them. But removing them, especially if they're widely used, is incredibly hard.