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
supports ext4, btrfs, and apfs. Multithreaded, supports compression, nested volumes, and can even search detached volumes like .iso and .dmg without mounting
An interesting bonus point: you can't really vibe code it cause clankers can not run sudo commands
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.
In the least, you could make an alias for sudo, and have it run that. With something like this in .bashrc:
alias safedo='sudo'
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'.
If the disk decides to falsely report a flush, there's not much you can do about it from the user side, no? (I'm not sure if `fsync` does anything in this case)
Dumb title.
It works by reading the block device in /dev directly, wouldn't it also work on an HDD, flash drive or a memory card?
I assume the author just meant SSD as a synonym for "main internal disk", since that is usually an SSD these days.
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
supports ext4, btrfs, and apfs. Multithreaded, supports compression, nested volumes, and can even search detached volumes like .iso and .dmg without mounting
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
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.
>cause clankers can not run sudo commands
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.
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:
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
When they can't run sudo, they'll user docker to give themselves root.
https://twitter.com/i/status/2060746160558543217
Pretty cool to read it directly from the associated device XD
Did you write a metadata parser for most of the filesystems?
> This is practically the most useless project becuase you can not run it without sudo permissions
Well, you could whitelist the tool in sudoers.
This would let LLMs use it too.
Y’all aren’t running your agents as root?
On Linux, you could create a udev rule to give you permissions on any attached raw disks (if you feel particularly adventurous).
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?
But can it bypass the magic performed by the SSD controller?
In particular, can it be certain that a flush is really a flush?
If the disk decides to falsely report a flush, there's not much you can do about it from the user side, no? (I'm not sure if `fsync` does anything in this case)