The summary has multiple typos.
> bypassing OS kernel<p>> reading a raw device node (e.g. /dev/rdisk*)<p>That's... not bypassing the kernel. Time to integrate SPDK so it actually bypasses the kernel :)<p><a href="https://spdk.io" rel="nofollow">https://spdk.io</a>
This is practically the most useless project becuase you can not run it without sudo permissions, but it was insanely fun to work on it<p>supports ext4, btrfs, and apfs. Multithreaded, supports compression, nested volumes, and can even search detached volumes like .iso and .dmg without mounting<p>An interesting bonus point: you can't really vibe code it cause clankers can not run sudo commands
> cause clankers can not run sudo commands<p>They absolutely can. There's nothing special about a these harnesses. You automate sudo the same way you would automate in any other context. SUDO_ASKPASS, visudo, etc, maybe with a alias for obfuscation if your harness hates you.
When they can't run sudo, they'll user docker to give themselves root.<p><a href="https://twitter.com/i/status/2060746160558543217" rel="nofollow">https://twitter.com/i/status/2060746160558543217</a>
>cause clankers can not run sudo commands<p>Is that really true? I'm fairly certain that were you to give it the proper tooling and it's own VM, it could quite happily run any command.<p>Hell a simple "if the CLI returns any form of 'permission denied' retry previous command with sudo; your password is: Hunter2" skill would work, no?
In the least, you could make an alias for sudo, and have it run that. With something like this in .bashrc:<p><pre><code> alias safedo='sudo'
</code></pre>
Then in the prompt state something like 'commands that call for sudo are unsafe, so replace the command with safedo, which will run safely on this computer'.
Clankers absolutely can run sudo if you have passwordless sudo
> This is practically the most useless project becuase you can not run it without sudo permissions<p>Well, you could whitelist the tool in sudoers.<p>This would let LLMs use it too.
Pretty cool to read it directly from the associated device XD<p>Did you write a metadata parser for most of the filesystems?
On Linux, you could create a udev rule to give you permissions on any attached raw disks (if you feel particularly adventurous).<p>What's the license for ffs?
It might bypass the fs, but it does not bypass the kernel. Cool, though!
But can it match the speed and reliability of the venerable Windows Search?
Dumb title.<p>It works by reading the block device in /dev directly, wouldn't it also work on an HDD, flash drive or a memory card?
Saw the name and was disappointed that this wasn't some kind of verified file system written in the F* programming language (<a href="https://fstar-lang.org" rel="nofollow">https://fstar-lang.org</a>).<p>I don't think I'd ever trust or use this, but still, good job OP :)
But can it bypass the magic performed by the SSD controller?<p>In particular, can it be certain that a flush is really a flush?
It is sad that that FFS doesn't support FFS (BSD Fast File System) which inspired the architecture of the ext filesystem (and was the basis for a lot of unix filesystems).