Writing a RISC-V OS in Rust: System Calls

Re:Writing a RISC-V OS in Rust: System Calls by beisner on Friday January 31, 2020 @07:05PM (#22207320)

I suspect that whatever replaces Linux will probably involve a paradigm shift at the lowest level. Perhaps capability-based IPC, perhaps seamlessly integrating local and networked nodes, etc. It’s going to take major major improvements to move the world off of the Linux kernel.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by monocasa on Friday January 31, 2020 @07:09PM (#22207351)

I imagine it's going to be an exokernel that can run pretty arbitrary user lands as if they were containers, built on cap based security.

If anyone agrees with me and wants to help out making that happen on an open source code base, hit me up.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by wyldfire on Friday January 31, 2020 @08:47PM (#22207950)

How different is this from the NT kernel? Or Fuchsia?

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by dnautics on Friday January 31, 2020 @07:40PM (#22207553)

I don't have time to work on this, but I highly recommend looking at using the erlang Virtual machine as your exokernel environment.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by SkyMarshal on Friday January 31, 2020 @08:03PM (#22207724)

Why BEAM? I know it’s good, just curious why this specific use case.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by dannyobrien on Friday January 31, 2020 @11:56PM (#22208777)

I'm seeing a few people heading in this direction (and wrote very provisionally about possible wider applications here: https://mastodon.social/@mala/103548286708316253 ). I think it's certainly an idea that's in the air.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by eyberg on Saturday February 01, 2020 @11:34AM (#22211387)

Have you looked at https://github.com/nanovms/nanos yet? What you are describing is fairly close and this is under active development.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by ummonk on Friday January 31, 2020 @07:42PM (#22207566)

Yes, that's definitely where things should be going. Definitely interested, though I don't have too much time to dedicate for an open source project.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by jhvkjhk on Saturday February 01, 2020 @01:44AM (#22209125)

Is Qubes OS what you are talking? I heard it can run Windows or Linux like containers on it.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by blattimwind on Saturday February 01, 2020 @05:48AM (#22209855)

Qubes = Xen hypervisor

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by Geezus42 on Friday January 31, 2020 @08:46PM (#22207943)

What kind of help do you need?

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by Geezus42 on Friday January 31, 2020 @08:52PM (#22207983)

https://geezus42.github.io/personal-website/

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by quietbritishjim on Saturday February 01, 2020 @07:46AM (#22210218)

You could be right, but it's interesting to note that Linux took off because it was actually trying not to be too ambitious. I can't find it now, but I think Linus's original email announcing it said something along the lines of it just being a toy project for experimentation, and not a "proper" OS like the one GNU is building. As you're probably aware, the kernel of the GNU OS, Hurd, involved am ambitious microkernel design, and now 30 years into its development it's still not usable.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by moron4hire on Saturday February 01, 2020 @08:20AM (#22210358)

That has more to do with the people involved than that they were microkernels.

[ Parent | on HN ]

Re:Writing a RISC-V OS in Rust: System Calls by Aloha on Saturday February 01, 2020 @02:18AM (#22209211)

You just described s hybrid of OS/400 and Plan 9.

[ Parent | on HN ]