jackpot51

* We have not started on inotify but I will keep that in mind

* RedoxFS is MIT licensed

* RedoxFS supports all features with or without full disk encryption

* RedoxFS encryption includes all metadata

Transparent compression was just merged.

This year’s Redox Summer of Code program has seen us add some exciting capabilities to Redox. Our three interns each came up with their own project proposals, and delivered major new functionality. In addition to our paid internships, our volunteer contributors also made major strides this summer.

I prefer Redox OS to support as wide a set of hardware as possible.

It is unlikely. The driver models are very different, ine being a microkernel, the other monolithic.

cargo is really close to working. rustc is working.

Hello, I am Jeremy Soller, the creator of Redox OS. Let me know if you have any questions!

There is a lot missing from it. Vim is ported as well.

There isn't much more to say, and it is still in legal hell so I should not say more anyways.

rustc is working on Redox, cargo is not working yet. There are issues with cargo pulling the registry that will need to be solved.

Hello, I am Jeremy Soller, the creator of Redox OS. Let me know if you have any questions!

It is upgradeable to 64GB.

An Operating System mostly written in the Rust programming language.

Can you explain in more detail?

There is no functional installer yet.

Redox has pretty low resource requirements.

Thanks!

Yes, it is redirect on write.

I look forward to the first "distro" of Redox!

I have looked into Fuchsia, mostly into the Zircon kernel and its system calls.

Working at System76, I have mostly been developing with those devices in mind.

Namespaces on redox are probably what you are looking for. They are incredibly powerful, but difficult to describe. Processes can offer isolated filesystems called "schemes". These are usually at the default namespace (1). Processes can move to the null namespace (0) which disallows them from opening file descriptors from most schemes. Moving to a new namespace allows a process to control the view of the system for all its children. This can be used, for example, to implement chroot.

Syscalls are mostly sync, but with some syscalls for doing blocking operations asynchronously, like on Linux.

I would love to next work on the install process. Currently, there is only a very simple installer that I haven't mentioned much because it is really only good for replicating the VM image inside a VM.

Improving this so it can be used to have permanent installs of Redox OS, and then improving rustc so those installs can build software for Redox OS (self-hosted), would accelerate development so we can take on bigger, higher level projects.

Yep, all those too :D

I'd love to port Servo, but the first thing people would ask after doing that, is probably when is Firefox going to be ported ;-)

I'll add that, I would definitely have had that if something other than x86_64 was supported

Spoiler alert: I am also the maintainer of Pop!_OS and the Principal Engineer at System76 so it will be easy to guess.

I have loads of computers (which helps when doing OS work!) but my main one is my desktop. I have a System76 Thelio Mira with AMD Ryzen 9 5950X CPU, AMD Radeon RX 6900 XT GPU, 128 GB DDR4-3200 ECC RAM, a couple PCIe Gen 4 drives, and a couple larger PCIe Gen 3 drives. The most important parts of my setup, though, are my System76 Launch keyboard and 3x LG 27GL850 monitors. There's also probably a mouse somewhere.

This computer runs primarily Pop!_OS 22.04 LTS, but on those extra drives I often have some other OS's installed for testing. I also use loads of VM's, as you can probably imagine.

For apps, I mostly use Alacritty for my terminal, Firefox for my browser, and Vim for my editor.

Primarily the model is capability based. Most things are managed through file descriptors. Services usually end up in a special namespace where they can no longer open new files at runtime, except from a highly restricted set of filesystems. This essentially disallows operating on anything beyond their current set of open file descriptors. This makes runtime inspection of the capabilities of each process fairly easy, and the build time declaration of those namespaces also pretty easy.

It has been a lot of work getting to this point. Finally, the foundation is laid for more regular updates.

For fun and for knowledge, what else?