Comparison to rustix project

[Shnatsel]

Hello,

This is not actually an issue, but I see that Github discussions are disabled, so I'm posting here instead.

As far as I understand the goals of the project, it seems very similar to https://github.com/bytecodealliance/rustix I just wanted to make sure you're aware of it. Perhaps there is some opportunity for code reuse between the two.

It also might be helpful to discuss the difference from rustix in the README to clarify the project goals.

Cheers!

[bjorn3]

By the same author (@sunfishcode) there is also cap-std, a "Capability-based version of the Rust standard library", which uses rustix behind the scenes and mustang which is a libc replacement also based on rustix.

[dvdhrm]

By the same author (@sunfishcode) there is also cap-std, a "Capability-based version of the Rust standard library", which uses rustix behind the scenes and mustang which is a libc replacement also based on rustix.
[...]
It also might be helpful to discuss the difference from rustix in the README to clarify the project goals.

Thank you for the hints! I was aware of rustix, but not cap-std and mustang. I will keep an eye on them!

This is not actually an issue, but I see that Github discussions are disabled, so I'm posting here instead.

As far as I understand the goals of the project, it seems very similar to https://github.com/bytecodealliance/rustix I just wanted to make sure you're aware of it. Perhaps there is some opportunity for code reuse between the two.

The idea behind r-linux is two-fold: First of all I want raw direct kernel-API access in the style of linux-api-headers. So just a plain mapping into rust, preferably in a style that requires little discussion or human intervention. So a rule-based translation of the C-API into Rust. Additionally, I want to use it to document the APIs, their common pitfalls, their usage and applicability.
The second goal is to create capability-based linux kernel APIs based on this direct kernel access. But this is limited to the kernel-APIs. I do not intend to widen the scope to provide further integration into other crates or std.

Note that this is currently just a dumping ground. I use it for testing bus1 APIs, but most of that isn't even pushed out. If it turns out rustix or maybe even cap-std provide a suitable alternative, I will gladly drop this. But I think for now this is just a playground to test things out.

Lastly, note that I do not intend to support any cross-OS compatibility or portability. This is purely meant as a way to access linux APIs from Rust. It will make heavy use of linux-only features and behavior.