News for hackers. Stuff that matters.
Re:Writing a RISC-V OS in Rust: System Calls by Koshkin on Friday January 31, 2020 @06:59PM (#22207278)
I just wonder what chances any new general-purpose OS kernel may have against Linux.
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.
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.

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?
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.
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.
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.
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.
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.
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.
Re:Writing a RISC-V OS in Rust: System Calls by blattimwind on Saturday February 01, 2020 @05:48AM (#22209855)
Qubes = Xen hypervisor
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?
Re:Writing a RISC-V OS in Rust: System Calls by Geezus42 on Friday January 31, 2020 @08:52PM (#22207983)
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.
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.
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.
Re:Writing a RISC-V OS in Rust: System Calls by pjmlp on Saturday February 01, 2020 @03:12AM (#22209389)
Only with the deep pockets of FAANG like companies.

Android or ChromeOS would never have taken off the ground without Google's keeping pushing them forward no matter what. In both OSes the kernel is hardly exposed to userspace, Google could move to something else and it would be hardly noticeable to app developers (OEMs and rooted phones is another matter).

And then there is Fuschia.

Outside general-purpose domain, the IoT world is getting full of BSD licensed OSes, RTOS, Zephyr, NuttX, Tizen RT.

Ironically Zephyr is managed by Linux Foundation, although it doesn't have anything to do with Linux code.

Re:Writing a RISC-V OS in Rust: System Calls by hhas01 on Saturday February 01, 2020 @08:46AM (#22210463)
That would be wrong battle to fight first. Pick one special-purpose market it can win and take that. Rinse, repeat.

Dog knows IoT needs something a lot better than Linux to run on; fat flabby old-school hacker-culture footguns are absolutely not an option when smart tech is being built into everything and everyone. That tech must be small, hard, absolutely focused, and take ZERO shit from NO-ONE; starting with itself.

Remember, the only code which can be 100% guaranteed impossible to compromise is code that isn’t there. Today’s Linux kernel is around 20 MILLION LOC, and counting. No prizes for figuring what any competing product’s USP must be.

..

“General-purposeness” designed into the product at the start enables it to adapt to each new market quicker and easier, but it shouldn’t be a public selling point in itself. Because the moment you start pitching it as being “everything to everyone”, everyone wants to throw their own crap into it as well—and you’re back to building ”another Linux”, in a market that already has a resident Linux and no room or need for another. Think smart. Don’t covet all the things that Linux does well and try to replicate those. Instead, identify the things Linux doesn’t do well (and CAN’T ever do well because of why and how it’s built) and knock those balls clean out of the park.

Think about how Steve Jobs finally beat Microsoft at its own game. Not by building a better PC, but by fundamentally redefining what “Personal Computing” means; and then being first to market with the perfect product for that.

Re:Writing a RISC-V OS in Rust: System Calls by msla on Friday January 31, 2020 @11:13PM (#22208607)
I agree: Trying to create a new general-purpose OS is futile. You're handicapping yourself by attempting a feat which likely can't achieve anything beyond your own satisfaction, which will be limited by the aforementioned self-handicapping. It's like sublimating your musical drive in a knock-off, unoriginal rock band in the vague hope you'll someday become the next Nickleback. Go for the gusto and put the Research in Research OS. Make something to explore an idea mainstream OSes can't pursue because it would break too much compatibility. Be Captain Beefheart, or at least Tool.
Re:Writing a RISC-V OS in Rust: System Calls by tyingq on Saturday February 01, 2020 @12:43AM (#22208928)
Fuchsia has the advantage that Google can force it onto a bunch of phones, Chromebooks, and personal assistants and get instant "market share".

I think it's likely the #1 threat to the Linux dominance in the backend, ironically by hijacking the front end first. Based on market share, it could create an expectation that AWS, Azure, etc, provide backend support. Doesn't hurt that Google owns K8S as well. See, for example, EKS. Google can manipulate Amazon in select spaces.