tfs

Not exactly ZFS in Rust, but more like a replacement for ZFS in Rust: https://github.com/redox-os/tfs Worked stalled, though. Not compatible, but I was working on overlayfs for freebsd in rust, and it was not pleasant at all. Can't imagine making an entire "real" file system in Rust.

Always fun to see this type of work. I notice the usage of OsString, and it made me wonder: does the way an OS encodes it’s strings potentially make this FS non-portable between OSes? If I want to mount a drive formatted with this FS, would the OsString be potentially non-portable? There was a lot of discussion in the past around TFS https://github.com/redox-os/tfs, my understanding is that effort has kinda lost steam.

And for code there is TFS https://github.com/redox-os/tfs

There's also TFS a ZFS inspired FS in Rust https://github.com/redox-os/tfs

Thanks for the link. Interesting it looks like Redox is writing their own filesystem or at least reimplementing ZFS: https://github.com/redox-os/tfs I wonder how that effects the time horizon for maturity. I've always just assumed that a filesystem takes a good 10 years to be really stable. Maybe my assumptions are way off? Or the facts that its a reimplementation makes that matter much less? Didn't it take BTRFS around this length of be considered production stable?

I don't agree with the notion that software has to be finished to be good (which isn't exactly what you said but the implication seems to be there). Taken literally, software that is unfinished (i.e. unusable) cannot possibly be good, obviously, but software that was been theorized but didn't necessarily exist in finished form until relatively recently is pretty common. If you don't want to make a bundled mess of spaghetti design, theory/play/experimentation that doesn't necessarily turn into a functioning project is crucial, ideas are sometimes reused/refactored into a project that is completed. Maybe if none of his work was actually published at all, then that statement would make sense (since it would literally be impossible to derive value from something that doesn't exist), but he's contributed documentation, schematics, etc, it's va

Ticki was an active member of the Rust community, whose contribution was energetically and cheerfully campaigning for ambitious features. Sometimes perhaps a little too ambitious, but that's a useful kind of person to have in a community. For example, Ticki wrote an early proposal for type-level integers, which everyone knows Rust needs eventually, but hadn't been able to work up a concrete proposal for: https://github.com/ticki/rfcs/blob/pi-types/text/0000-pi-typ... Outside the core project, Ticki was involved with RedoxOS, an OS written in Rust: https://github.com/redox-os/redox#-ecosystem- Particularly the TFS filesystem: https://github.com/redox-os/tfs TFS naver came to fruition, so RedoxOS still runs on its original filesystem, RedoxFS. Why is this important? It isn't, any more so than the other 29 things currently on the front page!

See also: TFS: A file system built for performance, space efficiency, and scalability https://github.com/redox-os/tfs https://news.ycombinator.com/item?id=14386331

Some of my favorite examples: https://os.phil-opp.com https://github.com/helena-project/tock https://www.redox-os.org https://github.com/redox-os/tfs https://github.com/intermezzOS/kernel The biggest application example: https://github.com/servo/servo And some self promotion: https://github.com/bluejekyll/trust-dns ---- I encourage all programmers to check it out. You may discover like me, that Rust is a compiler and language which guards against all the hard learned lessons I've had over my career. It's an amazing language to program in.

Another future alternative TFS: https://github.com/redox-os/tfs

For what it's worth, I think you should have taken the advice of the guy you're replying to. The first result for "TFS file system" is https://github.com/redox-os/tfs.

I assume they're targeting more than just ARM and x86, given they're talking about "truely portable AES implementations" in the README[1]. That said, I'm very inclined to distrust a very young cipher... released by the NSA, no less[2]. Which is an add-rotate-xor cipher[2], for which we already have the more reviewed ChaCha20[3], suggested for TLS 1.3[4]. [1] https://github.com/redox-os/tfs/blob/master/README.rst#faq [2] https://eprint.iacr.org/2013/404 [3] https://cr.yp.to/chacha/chacha-20080128.pdf [4] https://tools.ietf.org/html/rfc7905