Programming

17668 readers

190 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

FAMF: Files As Metadata Format (prma.dev)

submitted 5 months ago by prma@programming.dev to c/programming@programming.dev

44 comments fedilink hide all child comments

YAML and TOML suck. Long live the FAMF!

you are viewing a single comment's thread
view the rest of the comments

[–] Ferk@programming.dev 3 points 5 months ago* (last edited 5 months ago) (1 children)

For the record, you mention "the limitations of the number of inodes in Unix-like systems", but this is not a limit in Unix, but a limit in filesystem formats (which also extends to Windows and other systems).

So it depends more on what the filesystem is rather than the OS. A FAT32 partition can only hold 65,535 files (2^16), but both ext4 and NTFS can have up to 4,294,967,295 (2^32). If using Btrfs then it jumps to 18,446,744,073,709,551,615 (2^64).

[–] prma@programming.dev 1 points 5 months ago

You are right. Fat32 is not recommended for implementing FAMF.