6 ms·
Redox OS 0.6.0
- jackpot51 6y agoI am Jeremy Soller, the creator of Redox OS, please let me know if you have questions!
- Iolaum 6y agoCan you share what are the things missing from redoxOS before it can take advantage of the full capabilities of a system76 laptop?
- jackpot51 6y agoiwlwifi, a more complete USB stack, i2c hid, graphics acceleration. What does work is pretty cool though. Ethernet, input, non-accelerated graphics, nvme and ahci storage
- mbStavola 6y agoRelated, what is the end goal for Redox in your mind? Do you plan to ship it on System76 laptops when it's eventually ready? Or do you see this more as a hobby / exploratory project?
- hiq 6y agoWhat's next for Redox OS? I couldn't find a roadmap, but maybe you have one?
- jackpot51 6y agoNext up is probably a graphical installer
- cycloptic 6y agoAny plans for what to do about GPU drivers?
- zesterer 6y agoHey Jeremy! What sort of support do you have for graphical APIs like windowing, graphics, etc.? I'd be really interested in working with you to port Veloren (https://veloren.net/ https://veloren.net/), also written in Rust, to Redox at some point in the future: if nothing else, as a demonstration of what a pure Rust tech stack can do. If you're interested in this, feel free to message me on Reddit (same username).
- schaefer 6y agoHi Jeremy, Is there a port of Redox OS which runs under xen as a guest OS (paravirtual or otherwise)? Lots of tiny OSes, such as Minix, have been ported to this environment and I think this could be a fun way to run Redox while leveraging the broad device support of a traditional Linux Kernel. Thanks!
- nateinaction 6y agoLove seeing the progress on this! Thank you for sharing!
- yjftsjthsd-h 6y ago> rmm, a complete rewrite of the kernel memory manager. This has eliminated kernel memory leaks, which became quite an issue with the previous memory manager Hang on, I thought the whole point of writing in Rust was that this didn't happen. Is there something about a memory manager that requires unsafe? (Keeping in mind that I neither know Rust nor kernel design, so there's a very good chance that I'm just missing something here)
- deleted 6y ago[deleted]
- chipsa 6y agoMemory managers are intrinsically unsafe. Rust generally passes around already allocated memory, but allocating the memory requires that you start with an undifferentiated bucket of bits, so the memory manager passes around raw pointers.
- cesarb 6y agoIn Rust, memory leaks are considered "safe"; you don't need unsafe to create a memory leak. There's even a function in the standard library (std::mem::forget) to explicitly leak a value, and it's not marked as unsafe. And even without that function, it's very easy to leak memory in safe code (just create a cycle with reference-counted values). But yes, memory managers generally require unsafe. Consider what happens when you release memory containing a value of type A, and that memory is later allocated for a value of type B. This is equivalent to a transmute between types A and B, which requires unsafe.
- jhvkjhk 6y agoThe book[1] (something like bible of Rust) wrotes: > memory leaks are memory safe in Rust [1]: https://doc.rust-lang.org/book/ch15-06-reference-cycles.html#reference-cycles-can-leak-memory https://doc.rust-lang.org/book/ch15-06-reference-cycles.html...
- retrac 6y agoThere's probably no way to guarantee that there are no memory leaks in a general purpose language where you can allocate memory dynamically. How can the allocator know if you actually need those 1 MB chunks forever, like you keep requesting?