all these new generation copy-on-write filesystems, and yet no one has been brave enough to name theirs simply "cowfs". then they could call the package containing its mkfs, fsck, etc. "cowtools"

tired: calling the COW-aware copy syscall "clonefile(2)"

inspired: https://mastodon.social/@digitalfx/115646121152141872

@joe i keep saying that they should have named btrfs-progs cow-tools
@joe or just stomp on mootools.
@joe I just tried to follow you for the second time
@whitequark hmm, i didn't think i had any limitations on followers turned on, is it not working for you?

@joe no no i'm already following you

good pun

@joe Nobody wants to declare war on `apt -v`

@joe I just want a cheat code, "There is no secret cow tool"

https://en.wikipedia.org/wiki/Cow_level

@joe perhaps they are still waiting for the copy-on-write technology to be truly perfected in all possible real use cases ways before giving it the blessing of the cow
@joe GNU Hurd + CowFS, all bytes initialized to DEADBEEF...
@joe They’d have to re-implement mv as moov though.
@joe That’d be a brave moove.
@joe prongling the filesystem
@joe QEMU has a qcow format…
@joe with the additional new "mv" called "moo" ("move object over")?
@joe debian already has a cowtools which are used for buildroots
@joe back in the day, there was a web framework called mootools.
@joe instead of mkfs: milkfs?