| ▲ | jfrei 6 days ago | |
I am working on a Rust-based ext4 driver. The idea is that it can be re-used as a FUSE-based driver as well as (Windows) kernel driver (eventually). Most of the essential features are implemented so far, but some (mandatory) features are lacking (xattrs support). My goal is to get to a full ext4 implementation that also supports ext2 and ext3 read/write. The initial motivation was to have a pet project with a use-case for Rust, as I wanted to improve my Rust coding skills, after I did some work on a game server implementation in Rust earlier [1]. My goal is to have an implementation where I have digested every line mentally, which is something that pretty much excludes slop-like use of AI for large scale code generation. And of course I want to really trust the code that touches my files via raw hard disk access. Hence, I use AI mainly for unit tests and (scoped) code rewriting when my code gets too verbose and cumbersome. In the long run I'd want to add fuzzing to the implementation, so if anyone has experience on this, I'd be interested in getting some pointers. | ||