6 ms·
Writing an OS in Rust
- ramon156 2y agoThis source got me started with Rust back in 2021, and I'm very grateful that this exists.
- 3rdworldeng 2y agoNice job !
- jamesmunns 2y agoPhil's writing on OS development is always a wonderful read.
- nailer 2y agoI just came back from Rustconf and it seems there’s about five or so major OS releases, particularly focused around real time. Not all are open source though.
- jamesmunns 2y agoTock-OS, Oxid-OS (the safety version of Tock-OS, like freertos/safertos), and Hubris (from Oxide Computers) are the main three RTOSs, Embassy and RTIC are common frameworks (but not classic RTOSs) used for scheduling and resource management on bare metal systems. There are some more niche or non-public ones as well. For more classic OSs (not real time), Redox is the main one, as well as a lot of research/experimental/teaching ones, including the Blog OS from this guide/submission.
- segasuperstar 2y agoYou lost me at branch per post
- bigstrat2003 2y agoThis is just the source code for the blog. It is readable in normal fashion at os.phil-opp.com.
- vinc 2y agoI started working on MOROS[1][2] after completing the tutorial 5 years ago, and I cannot recommend it enough for anyone interested in Rust and osdev. Phil put a lot of work into it, and it shows! The project covers a lot, and after that there's the osdev wiki[3] to keep going. [1]: http://moros.cc http://moros.cc [2]: https://github.com/vinc/moros https://github.com/vinc/moros [3]: https://wiki.osdev.org https://wiki.osdev.org
- flatfuzz 2y agoim subscribed to your RSS feed since a while back, MOROS seems like a really cool project! sadly haven’t been able to try it since it wouldn’t start on QEMU for some reason, though i think that’s an issue on my side rather than the OS itself.
- vinc 2y agoThanks! If you try again and still have it don't hesitate to create an issue on GitHub and I'll look into it!
- codethief 2y agoRe [1]: No TLS? :(
- vinc 2y agoGood question, there's no TLS support inside MOROS so its website must be available over HTTP, especially when I self-host it. That's not the case currently so I could also have HTTPS but I'm using Dokku and last time I tried the Let's Encrypt plugin would redirect HTTP to HTTPS automatically, which is annoying. Edit: I set up CloudFlare in front of the server and there's now a working HTTPS version along with the HTTP version accessible from inside MOROS. This should also work when I'll use again the web server inside the OS. Thanks for prompting me to look into it!
- bigstrat2003 2y agoThere's nothing sensitive, therefore there is no reason to use TLS.
- Levitating 2y agoI especially recommend the original edition of these posts. For me the current edition does way too much hand holding, taking care of the entire bootloading process with a specialized crate.
- ok_dad 2y agoI like that there’s a way to skip all that boot loading stuff, your comment made me want to actually try this. I want to build a fun little OS for myself but I hate the part where you have to do magical incantations to get to a decent machine state to do stuff in. Not that it’s a bad thing, everybody likes different stuff. Thanks for mentioning this!
- KingOfLechia 2y ago[dead]
- xyst 2y agoThe pool of operating system penetration testers will be absolutely devastated if a rust OS becomes mainstream. Most, if not all, vulnerabilities are related to lack of memory safety. Well, guess there’s always the application/user space.
- sureglymop 2y agoRegarding your last sentence, if they move on to AI imposed security vulnerabilities there is probably a lot of bread and butter to be made there.
- aaronmdjones 2y agoDefinitely not all. Our current best estimates put the figure of (amount of security vulnerabilities due to memory safety errors) / (total amount of security vulnerabilities) at 50-70%. People will still be making logic errors & authentication errors (e.g. insecure direct object reference) in Rust code for decades to come, to name just a few. Why? Because people make mistakes.
- azhenley 2y agoAnother good resource is Making a RISC-V OS using Rust https://osblog.stephenmarz.com/ https://osblog.stephenmarz.com/
- jayd3e 2y agoFunny, I found this today after doing a deep dive on Rust and OS development. I was in awe at the quality of this content. You come out of it not only learning so much about the history and design of operating systems, but you start to pick up elements of Rust as well. Phil did an incredible job on this.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- assanineass 2y agoJokingly thought it was another one of those “I rewrote it in Rust” moments. Cool post
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- chucksmash 2y agoI completed the second edition years ago and found it illuminating. It's very well done! The explanations pertaining to OS dev are nice but it was also a useful artifact for learning more Rust after having gone through the Rust book. The author had a good grasp of the idiom of the language, so seeing how he expressed certain things in code vis a vis how I would have done was educational. The blog's explanation of how futures are implemented in Rust was especially a highlight[0], and I think it's the best I've seen on that topic anywhere. I hope Phil will find the inspiration to come back and work on the EFI-based third edition again. AFAICT, (based on commits to the git branches) that has stalled. I was a GitHub sponsor for about a year until my CC expired and was always bummed to see it left out of the "This Month In Rust OSDev" posts. Anyway, the second edition is still a great way to spend a weekend's dev time and I appreciate all the hard work that clearly went into it. Thanks Phil! [0]: https://os.phil-opp.com/async-await/#async-await-in-rust https://os.phil-opp.com/async-await/#async-await-in-rust
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- Beijinger 2y agohttps://harvey-os.org/ https://harvey-os.org/ (Retired) The team now works on this: https://github.com/r9os/r9 https://github.com/r9os/r9
- xiaodai 2y agoMakes sense but what if there are bugs in llvm? U r still exposed. So need a rust version of llvm and then rust can be self hosted
- polyaniline 2y agoI don't think that's something to be pedantic about. Even so, cranelift exists.
- recursivecaveat 2y agoIt doesn't really matter whether the compiler is memory safe. What you run is the result of the compiler. A perfectly memory safe compiler can have a correctness bug that generates unsafe assembly from a safe rust program.
- gxt 2y agoWe shouldn't write an OS in rust. We should create a data platform on which we can run DML/DDL with an SSMS++ automatic frontend.
- nineteen999 2y agoWe really should, if for no other reason than to silence those who think that every Linux/BSD box connected to a network is being rooted every 5 mins because they are written in C. That's if they ever get around to bringing such a Rust-based OS up to enterprise level rather than spouting off about this belief on HN all day every day.
- amelius 2y agoIs this project about writing a kernel or an entire OS including graphical shell, etc.?
- guofoo 2y agoHe's giving a talk at next month's GOSIM conference. https://china2024.gosim.org/speakers#philipp-oppermann https://china2024.gosim.org/speakers#philipp-oppermann It would be nice to be able to talk to him in person.
- HenryBemis 2y ago(not a professional coder) "writing an X on Y" brings in my mind the meme of Ryan Reynolds "But why?" [0]. If it is for training purposes, then by all means, go nuts!! The more one codes, the better. [0]: https://screenrant.com/ryan-reynolds-but-why-gif-harold-kumar-movie/ https://screenrant.com/ryan-reynolds-but-why-gif-harold-kuma... Sidenote on "MOROS" - cool project/page!